Contribute to Open Source. Search issue labels to find the right project for you!

Spec RFC: Allow interfaces to implement other interfaces


<!–Issue Labels

While not necessary, you can help organize our issues by labeling this issue when you open it. To add a label automatically, simply [x] mark the appropriate box below:

  • [ ] has-reproduction
  • [x] feature
  • [ ] docs
  • [ ] blocking
  • [ ] good first issue

To add a label not listed above, simply place /label another-label-name on a line by itself. –>

Per our discussion in the 2018-03-22 GraphQL WG meeting, I’m looking to explore change costs associated with the “Allow interfaces to implement other interfaces” RFC. @evans noted that we might start here. Any insight from the team at Apollo would be awesome!

  • (Spec Issue)[])
  • (Spec RFC)[]
  • (graphql.js PR)[]
Updated 22/03/2018 23:09

Object labels and custom names for items


I would really like to see objects with labels on them, e.g., when I walk up to a tree, it would be nice to see what kind of tree it is before I start chopping it - same with different types of ores and plants. I suppose even animals (or possibly after it’s been killed).

Also, the ability to name items such as storage chests, buildings with the same idea in mind. I walk up to a stack of 5 chests and before I have to rummage through them all to find what I’m looking for, each one could be named and I’d see that name label on each one if I stand in front of it. “Food”, “Finished Items”, “Raw Mats”, etc.

Updated 22/03/2018 22:54

Add 'spawn-pos' mod to search for suitable biomes


WIP some stuff to add like README and license, some comments are temporarily left in for testing, but code is complete and works.

Suitable biomes are currently those with plenty of wood supply from trees, if spawn on a small savanna island with no wood is a problem savanna could be removed.

Search is done once on first new player spawn during a server session, then that position is stored and used for later new player spawns. If search fails the new player spawn position falls back to the default engine spawn point, which may not be in a desired biome. Search is a square-spiral working outwards from (0, 0) checking every point in a grid with spacing ‘res’ (resolution of the grid). ‘res’ could be tuned as a way to optimise the search. The total number of checks could be tuned to balance the maximum search time against chance of success, it is probably set a little too high currently (10000) and could be minimised.

Updated 22/03/2018 22:40

New User setup


When signing up, we now present users with a wizard to enroll in institutions and register for programs. You can also get to this wizard from the profile page.

The only thing I’m not happy about is the sizing for the reveal for institutions and programs is fixed, I haven’t found a way to dynamically calculate it but I’m open to ideas.

Fixes #34.

Updated 22/03/2018 23:35 1 Comments

ns 'ERROR" // "неймспейс" для улавливания post-ERROR-сообщений от СМЭВ3


оформить пред-определенный ns для получения ошибок от СМЭВ по схеме остальных ns в рамках группы (для каждой группы свой такой ns)

думаю описывать как обычны ns - только имя элемента ns_error

со всеми атрибутами обычного ns, кроме собственно имени ns,: <ns_error name=‘ERROR’ nick=‘ERROR_TSMEV’ group=‘TSMEV’ > <active>1</active> - должен работать как обычно <urgent>1</urgent> - должен работать как обычно

        _<is_skipped>0</is_skipped> -- не используется_

        <send_ack>1</send_ack> -- должен работать как обычно

<namespace></namespace> – не используется

        <root_element_local_name>Request</root_element_local_name> -- не знаю
        <count_parallel_max>1</count_parallel_max> -- не знаю

        <urgent_script_path>.\urgent_script.TSMEV\parser-3.4.4u-xml.xc_qm_om\parser3.exe .\urgent_script.TSMEV\ns_sezt3\index.html TSMEV</urgent_script_path> - должен работать как обычно

        <!-- 1 if signature from incoming message should be extracted, serialized and passed to urgent script -->
        <sign_extract>0</sign_extract> - должен работать как обычно

        <!-- Ammound of time before non-respinding urgent script wolud be terminated and message reception would be considered a failure -->
        <urgent_script_timeout unit="min">5</urgent_script_timeout> - должен работать как обычно

Updated 22/03/2018 22:32

WIP Display configuration


Signed-off-by: Gianfranco Manganiello

Changes description

<!– Describe results, user mentions, screenshots, screencast (gif) –>


Please check if your PR fulfills the following specifications:

  • [ ] Tests for the changes have been added
  • [ ] Docs have been added/updated


<!– issues related (for reference or to be closed) and/or links of discuss –>

Close: #523

Updated 22/03/2018 22:43

If repeated invitations are sent to a single email address, revoke only removes one

  • Specific code commit: 07fa2fc
  • Version of the web browser and OS: Mac FF
  • Environment where the error occurred (Vagrant VM and site conf mode or AWS instance): prod test

Steps to reproduce

Please list all the actions and the input data used:

  1. Send multiple invitations to a single email address
  2. Think better of it, and revoke one invitation

Observed behavior

  • Only that one invitation is revoked

    Expected behavior

  • All invitations to that email for this group are revoked
Updated 22/03/2018 22:06

Feature - DICT protocol "source" with configurable servers


There exists a standard protocol for accessing remote dictionary services. While it’s quite old in design, it was purposefully designed for clients/applications such as define.

A generic DICT protocol “source”/provider could potentially be added to define with a configurable list of servers, depending on how complex the access and data parsing (into structures) would be.

More info here (for later reference):

Updated 22/03/2018 22:04 1 Comments

Feature - Local macOS dictionary as a source


Currently, define uses all remote (online) sources. A local, expandable dictionary is available on macOS, which would be a great source if it was accessible.

Unfortunately, it seems that the only way to access the dictionary’s data is through Core Services, which would require Cocoa bindings to Go and native-compilation (think cgo). There may be another way around this, though.

Also, the only public APIs that exist return the definition in a formatted string format, not in a structured model, which would be a nightmare (if not potentially impossible) to consistently parse.

More information here (for later reference):

Updated 22/03/2018 22:01

Support non-ascii email addresses for invitations

  • Specific code commit: 07fa2fc90223e14336c5547c4d8238ec03fd648b
  • Version of the web browser and OS: Mac FF
  • Environment where the error occurred (Vagrant VM and site conf mode or AWS instance): prod test

Steps to reproduce

Please list all the actions and the input data used:

  1. Try to send an invite to an email address including non-ascii characters (For example, your own gmail with the suffix: +üñîçø∂é)

Observed behavior

  • It does not validate.

Expected behavior

  • It validates, and sends the invitation.
Updated 22/03/2018 21:55

Uploads management area


The admin area should get a management view for the uploaded files. Took first step.

  • [x] list a number of uploaded images in a table matrix
  • [x] every item has a checkbox to select it for removal
  • [x] the view has a header, a no-uploads-info and a label for the checkboxes (german, english, english in all other languages (translation todo))
  • [ ] setting for the number of items per page (is hardcoded at the moment)
  • [ ] pagination for viewing further images if there is more than a pages limit
  • [ ] removal of the images from the file system after submitting the form
  • [ ] additional-information-view

This is not ready for merging, it’s actually a work in progress.

Updated 22/03/2018 21:52

Display configuration


<!– File a GitHub issue only for bugs or feature requests related to the code in this repository. For other topics you can get more information in the README file. –>

Observed Results:

<!– This could be a description, error output, steps to reproduce, a feature missed, etc. –>

captura de pantalla 2018-03-22 a la s 5 34 09 p m

Expected behavior:

<!– What did you expect to happen? –> Use the display configuration to edit the home page of the dashboard

Updated 22/03/2018 21:42

feat(911): support subdirectory



To support Subdirectory, scm plugin getChangedFiles will return an array of files that were changed. The API will pass this extra field to model (what this PR is doing). The model will do the logic to figure out whether to start jobs or not.

Blocked by: - - - scm change


Updated 22/03/2018 23:22

Error inviting new users to groups with non-ascii names?

  • Specific code commit: 07fa2fc90223e14336c5547c4d8238ec03fd648b
  • Version of the web browser and OS: mac ff
  • Environment where the error occurred (Vagrant VM and site conf mode or AWS instance): test production

Steps to reproduce

Please list all the actions and the input data used:

  1. Create a group with a name like “cräzy unîçødé”
  2. Try to invite an email to the group

Observed behavior

Error message:

Error, invitiation could not be sent <img width=“807” alt=“screen shot 2018-03-22 at 5 31 14 pm” src=“”>

… but if I refresh, there is a pending invitation, but nothing has actually arrived in my inbox.

Expected behavior

  • Invitation can be sent
  • Error message has space before email
Updated 22/03/2018 22:04

Normalize spaces within Names

  • Specific code commit: 07fa2fc90223e14336c5547c4d8238ec03fd648b
  • Version of the web browser and OS: Mac FF
  • Environment where the error occurred (Vagrant VM and site conf mode or AWS instance): Prod test

Steps to reproduce

Please list all the actions and the input data used:

If there is already one group with a space in its name, ie “Shivdasani Lab”, you can create another one, superficially identical, by entering multiple spaces between the words. <img width=“345” alt=“screen shot 2018-03-22 at 5 16 46 pm” src=“”>

Expected behavior

Currently, leading or trailing spaces are stripped: That might be extended to normalize internal spaces in a name.

Updated 22/03/2018 21:26

Updated win_disk_facts module

  • Added trimmed option to module win_disk_facts
  • Removed required administrator privileges

The trimmed option can be used to reduce the output of the module. Then only the disk fact details will be displayed but no detailed information about the partitions and volumes of the disk.

  • Feature Pull Request


  config file = /etc/ansible/ansible.cfg
  configured module search path = [u'/root/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/lib/python2.7/dist-packages/ansible
  executable location = /usr/bin/ansible
  python version = 2.7.12 (default, Nov 20 2017, 18:23:56) [GCC 5.4.0 20160609]
Updated 22/03/2018 22:14 3 Comments

show policies feedback


Add UI in the plugin to monitor how are applied the policies o n the devices

  • a new tab on the agents to show the list of task statuses.
  • update the agents tab to show a bar with several colors, each per status
    • statuses specific to some policies (deployment) should be merged into a single color
Updated 22/03/2018 21:02

Add support for human-curated lists


I’m submitting a:
- [ ] bug report - [x] feature request


Create a template/ system to serve human-curated lists :book:.

The list will be in json formats and will contain a list of links along with title and description. There will be sub-sections and each sub-section will contain links. There may be several such lists. Consider a list for “best resources to learn Go” denoted by learn_go.json file. For this, sub-sections may be “websites”, “youtube”, “free tutorials”, “paid courses” and others.

The list must be available at In fact, it follows the following pattern:{list_name}.

Sample JSON format: { "title": "", "id": "", "tags": [], "link": "", "credit_link": "", "short_description": [], "long_description": [], "date": "", "authors": ["",""], "section": [ { "sub_section": "", "id": "1.1", "short_description": "", "long_description": "", "tags": [], "grand_section": [ { "title": "", "id": "1.1.1", "short_description": "", "long_description": "", "link": "", "tags" [], }, ... ] }, ... ] } You are free to use another JSON format as well.

This includes creating a template and routing for such a sample list. From the UI point of view, the sub-sections must be presented to the user. When the user clicks on a sub-section title, it must expand and the contents must be visible.

This will greatly enhance the user experience and reduce searching time by providing human curated links and knowledge. These lists will be presented as search results. This will form the basis for further exciting updates that will pave the way to a faster search. :+1:

Updated 22/03/2018 20:59

Customer feedback for policies


Related to:

We need to collect feedback from users of devices.

We need a new relation between a computer (a device hardware, inventoried) and a policy containing a boolean (is_success) and maybe a comment

Updated 22/03/2018 20:14

Order events on calendar page chronology


As a user on the calendar page

I want to see events in chronological order

So that I see the soonest events first


The query method should now take an orderBy parameter, which should be date by default.

You may need to add a date field on events in the database, which should be populated on event submission.

Blocked by #37

Updated 22/03/2018 20:00

Adding support for graphql@0.12.0 and graphql@0.13.0


Also added some infra to make sure we run tests against all possible versions.

This is a major breaking change — it fails a few tests and its not worth diverging the tests based on version to avoid the major bump. There’s also some complications with libraries like graphql-config not properly supporting custom named “Query” types, but shouldn’t affect a large amount of people.

<!– Thanks for filing a pull request on eslint-plugin-graphql!

Please look at the following checklist to ensure that your PR can be accepted quickly: –>


  • [x] Make sure all of the significant new logic is covered by tests
  • [x] Rebase your changes on master so that they can be merged easily
  • [x] Make sure all tests pass
  • [ ] Update with your change
  • [ ] If this was a change that affects the external API, update the README

Pull Request Labels

<!– While not necessary, you can help organize our pull request by labeling this pull request when you open it. To add a label automatically, simply [x] mark the appropriate box below: –>

  • [x] feature
  • [ ] blocking
  • [ ] docs

<!– You are also able to add labels by placing /label on a new line followed by the label you would like to add. ex: /label discussion –>

Updated 22/03/2018 20:26

Prototype Positional Arguments


Prototype positional arguments for group delete.

Required - [x] Core modifications - [ ] Telemetry - [x] Changes to help system - [ ] Evaluate error message - should be more clear, distinct… - [x] Tab completion support - [ ] Interactive support - works, but tab completion definitely DOES NOT. - [ ] Reference docs - [ ] Tests

Optional - [ ] migrate commands - [x] optional positional args - this works using nargs='*'. It treats it like empty string. - [x] nargs positional args

Updated 22/03/2018 22:58

Allow builds to tag event



In a pipeline events page GIT SHA and commit message is what uniquely identifies an event. It would be helpful for users to quickly identify an event using a key->value pair which a build can set to identify a specific event rather than going through the SHA and commit message.

For example a build in a release pipeline can set value RELEASE_VERSION=1.5.1 to identify an event which built Version 1.5.1 and use that to quickly identify the event. In a roll back scenario this helps users to quickly identify the event from which they need to invoke roll back.


  1. Expose an sd command to tag an event.
  2. UI should display the tag for the event.
Updated 22/03/2018 18:04

Support for various ChildPolicy on Cadence server


StartWorkflowExecution allows user to specify the following 3 type of ChildPolicy: enum ChildPolicy { TERMINATE, REQUEST_CANCEL, ABANDON, }

Current server implementation only supports ABANDON and does not have support for TERMINATE and REQUEST_CANCEL ChildPolicy for child workflow executions.
This issue is to implement support for all types of ChildPolicy on Cadence server.

Updated 22/03/2018 17:42

Add "bug coverage {bug-id} [*test-id]" CLI command


We should add a simple CLI command that can print coverage information for a given bug to the terminal. As its arguments, the command should accept the ID of the bug, along with an optional list of tests (given by their identifiers) for which it should show coverage information. If no list of test IDs is provided, then coverage information for the entire test suite should be shown.

It may also be useful to add a --restrict-to-file method that could allow the user to only print coverage information for a particular file.

Updated 22/03/2018 17:17

Fork me on GitHub