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

Main Menu

pandapaul/crypto

Game Title (Crypto? Colossus?)

Button –> Freelance –> ?? Story Mode Jobs vs. Player Created Jobs

Button –> Agency Eyes Only –> Insert Text to be sent to other player

Button –> Debriefing –> Info on game, How To

Updated 15/12/2017 01:46

Player to Player Messaging

pandapaul/crypto

In the Agency Eyes Only Mode, a player will be able to insert a message that will be turned into a cipher and sent to another player (in app? in email? in messanger?). The player sending the message has the option to make it easy (help solve function?) or hard (self destructs after time up?/snap chat for texts?). If this person doesn’t have the app, a message will be sent to ask them to download the app (?).

Updated 15/12/2017 01:38

Option for Boolean metadata on dashboard

transloadit/uppy

I’m developing a web app where users will be able to have their uploads be public or private on the website. I think it would be a useful feature for the metadata plugin to have an option for fields to be boolean (checkbox) instead of text input. In my case, public : true or public : false.

Updated 15/12/2017 03:46 2 Comments

Quote Database

pandapaul/crypto

The ciphers in the packs/jobs will be quotes and popular sayings that are added and updated so a database of these quotes needs to be made. I can create a list of quotes to be used, but need someone else to magic this database into creation.

Updated 15/12/2017 01:53 3 Comments

Implement command `ks registry add`

ksonnet/ksonnet

Fixes #226

Currently users are unable to add their own registries through the CLI. This limits them to a small subset of prototypes found in the default incubator registry.

This commit will add the command ks registry add, that allows users to add registries supporting the github protocol.

It will be of the form ks registry add <registry-name> <registry-uri> [--version]. If a version is not specified, latest will be used.

Updated 15/12/2017 00:09 1 Comments

Continuous category Gaussian Process (sensu McElreath, 2016:410)

paul-buerkner/brms

A feature request, following discussion with Paul by email.

Richard McElreath in Statistical Rethinking implements a very useful varying intercept where categories covary based on a continuous variable. In his example he uses the Euclidean distance among the geographic coordinates of the groups where data were measured to model the covariance.

In bf() formula syntax it might be:

y ~ (1 | continuousCategoricalVariable)

where groups would be defined on the fly as elements that have the same value of continuousCategoricalVariable, and a distance matrix among these automatically assembled. I can imagine that this might be the default behaviour when a non factor is supplied as the grouping variable after the |. There would also need to be a way of specifying the model for covariance.

Just an idea. Thanks for considering.

Updated 14/12/2017 23:43

(complib) Add alert and spinner icons

Opentrons/opentrons

overview

Restructures the icon component slightly and adds ALERT and SPINNER. Spinner SVG pulled from FontAwesome v5 free for now.

How to make a spinning spinner (note: spin attribute works with any icon 💸):

import {Icon, SPINNER} from '@opentrons/components'

export default function SomeComponent () {
  return (
    <Icon name={SPINNER} spin />
  )
}

Put the spinner in the UploadStatus page just to make sure it works:

2017-12-14 18 09 54

This PR includes:

  • [ ] Chore work
  • [ ] Bug fixes
  • [X] Backwards-compatible feature additions
  • [ ] Breaking changes
  • [X] Documentation updates
  • [X] Test updates

review requests

What do we think of the icons directory structure? I learned a few things about importing and exporting flow types so that was fun.

Updated 14/12/2017 23:35 1 Comments

As an IM system it shall login an existing user

actframework/a-im

1. Description

Provides a RESTful API for user login through HTTP(s). After the API called a authentication token shall be generated and respond back to caller.

1.1 Implementation

The system shall implement authentication token using JWT (JSON Web Token).

Note security concern applied to this API

2. Acceptance criteria

2.1 Normal path

  • Calling the endpoints with proper username/password shall respond with a JWT token
  • Use the JWT token to access other authenticated API shall not trigger 401 Unauthorized response

2.2 Invalid username/password

  • Calling the endpoints with invalid username/password combination shall get a response with 401 Unauthorized response
Updated 14/12/2017 22:56

[MIRROR] All-In-One grinder results are now defined by type, not by huge lists

Citadel-Station-13/Citadel-Station-13

Original PR: https://github.com/tgstation/tgstation/pull/33181

:cl: Xhuis add: Grinding runed metal and brass now produces iron/blood and iron/teslium, respectively. balance: As part of some code-side improvements, the amount of reagents you get from grinding some objects might be slightly different. fix: Some grinding recipes that didn’t work, like dead mice and glowsticks, now do. fix: All-In-One grinders now correctly grind up everything, instead of one thing at a time. /:cl:

Fixes #32532. (I think!) Fixes #32369.

I had some time free, and noticed how awful the reagent grinder code was - it used huge static lists containing types and their associated reagents from grinding.

This is now split into two new vars on /obj/item - var/list/grind_results and var/list/juice_results, as well as two new helper procs, on_grind() and on_juice() to allow those to change based on conditions like plant potency. Such checks and the like have been moved to that. If any of these procs return -1, the operation is canceled.

I also fixed some of the recipes that didn’t work. The reagent IDs for them didn’t exist, leading me to believe that they weren’t tested. I corrected that! (I’ve tested every single recipe in this PR, with the exception of a few juicing-related ones.)

Updated 14/12/2017 22:24

[MIRROR] All-In-One grinder results are now defined by type, not by huge lists

HippieStation/HippieStation

Original PR: https://github.com/tgstation/tgstation/pull/33181

:cl: Xhuis add: Grinding runed metal and brass now produces iron/blood and iron/teslium, respectively. balance: As part of some code-side improvements, the amount of reagents you get from grinding some objects might be slightly different. fix: Some grinding recipes that didn’t work, like dead mice and glowsticks, now do. fix: All-In-One grinders now correctly grind up everything, instead of one thing at a time. /:cl:

Fixes #32532. (I think!) Fixes #32369.

I had some time free, and noticed how awful the reagent grinder code was - it used huge static lists containing types and their associated reagents from grinding.

This is now split into two new vars on /obj/item - var/list/grind_results and var/list/juice_results, as well as two new helper procs, on_grind() and on_juice() to allow those to change based on conditions like plant potency. Such checks and the like have been moved to that. If any of these procs return -1, the operation is canceled.

I also fixed some of the recipes that didn’t work. The reagent IDs for them didn’t exist, leading me to believe that they weren’t tested. I corrected that! (I’ve tested every single recipe in this PR, with the exception of a few juicing-related ones.)

Updated 14/12/2017 21:48

As an IM system it shall be able to provision user profile

actframework/a-im

1. Description

Provides a RESTful API for user provisioning. After the API called an new user profile shall be created in the system.

Note security concern applied to this API

1.1 Data structure

A IM user profile shall contains the following fields

1.2 Data validation

2. Acceptance criteria

  • If valid data is provided for the API, an new user profile shall be created in the system
  • If any piece of data is invalid then 400 Bad Request with proper information shall be returned
  • A functional testcase be implemented
Updated 14/12/2017 21:50

Configuración de la integración continua

Proyecto-EGC-G1/Autenticacion-EGC-G1

La configuración continua está activada para nuestro repositorio, pero hay que crear el archivo Yamel de configuración. De momento no tenemos pruebas, así que sólo se encargará de coger el código, instalar las dependencias del proyecto, montar el mysql, y ejecutar el controllers.py.

La integración continua solo se realizará sobre las ramas master y develop

Updated 14/12/2017 21:53

[WIP] Adds the ability to dip foodstuffs and sharp objects in reagents via a new component

tgstation/tgstation

:cl: Y0SH1_M4S73R add: Food and sharp objects can be dipped in reagents. Sharp dipped objects will transfer some of their reagents to their victims when attacking. /:cl:

This adds the “dippable” component, whose parameters are explained in the comments at the top of dippable.dm.

Before this is ready for merge, I just need feedback on what should be added, changed, or removed, particularly with respect to balance.

Updated 15/12/2017 01:02 11 Comments

Create readme base

OddlyDoddly/salem-gdk

Salem-GDK needs a proper readme file which should include:

  • A well flushed out project description
  • Linux Setup & Build Instructions
  • Windows Setup & Build Instructions
  • List of Dependencies
  • List of Third Party Libraries and contributor links
Updated 14/12/2017 20:19

(complib, app) Add PageTabs and use it for pip. selection

Opentrons/opentrons

overview

Incremental PR of ongoing calibration screen alignment. I’ve added a PageTabs component (“Structure / Page / Tabs” in Sketch) and wired it to the pipette selection for instrument calibration:

2017-12-14 14 20 06

A few things to note:

  • Currently hardwired in CSS to two tabs (with width: 50%;)
    • Pipette calibration is the only place we use this component for now
    • Talked this through with UI/UX and everyone thought this was fine
  • We’re handling active manually rather than using react-router NavLinks
    • State tracking with NavLink has been super flaky for us
    • Happy to revisit if/when we figure out the flakiness
    • For now manual tracking is completely reliable
  • I started an app/components/setup-instruments directory
    • For instrument setup specific components, naturally

This PR includes:

  • [ ] Chore work
  • [ ] Bug fixes
  • [X] Backwards-compatible feature additions
  • [ ] Breaking changes
  • [X] Documentation updates
  • [X] Test updates

changelog

  • (Feature, docs, tests) Added PageTabs component to library
  • (Refactor) Replace PipetteConfig titles in app with InstrumentTabs (container wrapper around PageTabs)

review requests

Standard review. I just installed linter-markdown in Atom so I apologize for the README diff noise…

Updated 14/12/2017 21:07 2 Comments

New customer groups visible for all users until customer group is linked to password account

nuxsmin/sysPass

Hi,

I add multiple users in my syspass. Admin User A User B User C Then I added multiple groups, each for every customer. Group A Group B Group C I linked each user and the admin to the relevant group. Group A - User A - Admin Group B - User B - Admin Group C - User C - Admin Finally I added multiple customer groups, each for every customer. Customer A Customer B Customer C But when a customer logs in, he can see every customer group added after I added his account in the customer filter of his dashboard. Admin sees all customer groups in the filter -> correct User A sees Customer A, Customer B and Customer C on the dashboard -> not correct, needs only able to filter on Customer A User B sees Customer B and Customer C on the dashboard -> not correct, needs only able to filter on Customer B User C sees Customer C on the dashboard -> correct

Is this a bug, or how to solve?

Kind Regards Nick Geoffroy

Updated 14/12/2017 22:09 4 Comments

depot/create: skip rebuild when FORCE=1 but version remains unchanged

genodelabs/genode

When calling the depot/create tool for a binary archive with FORCE=1, the underlying source archives are re-extracted and the binary archive is rebuilt. This is usually done after local changes in the source tree to apply version updates to depot archives as needed. However, the implicit rebuild is superfluous whenever the source-version remains the same. This is particular inconvenient when re-creating pkg archives that refer to a large number of src archives. Here, all binaries referenced by the pkg archive are rebuilt.

Updated 14/12/2017 19:29 2 Comments

Enable router timeout configuration and parameters object

CorfuDB/CorfuDB

Overview

Description: This PR moves all settings of the runtime into the CorfuRuntimeParameters object, and allows RPC timeouts to be set at construction time if the user generates a runtime with a CorfuRuntimeParameters object. Previously, a NettyClientRouter would be created as soon as the runtime connected, inheriting the defaults rather than the user-defined settings.

Why should this be merged: This PR enables setting of timeouts on the router, which allows users to reconfigure for a slow network. It also prevents race conditions where the runtime is active while settings are being changed.

Related issue(s) (if applicable): Fixes #995, Fixes #991, Closes #1027

Checklist (Definition of Done):

  • [x] There are no TODOs left in the code
  • [x] Coding conventions (e.g. for logging, unit tests) have been followed
  • [x] Change is covered by automated tests
  • [x] Public API has Javadoc
Updated 14/12/2017 19:27 2 Comments

Create UDP MMO Network

OddlyDoddly/salem-gdk

Salem needs an MMO Network Interface. A basic implementation should meet the following requirements:

  • Sockets run on UDP Protocol
  • A client and server class usable by the test project.
  • Should have atleast 1 default packet type for chat messages
  • Should be able to send and receive chat message (you can just console log the messages)
  • Should support an interface to allow custom packet types defined in projects using Salem
  • Needs to support multiple users.
Updated 14/12/2017 19:07 1 Comments

Add "testing" module to support test execution and coverage generation

squaresLab/blameandshame

Each version of a project should have an associated TestSuite. We should be able to execute tests individually and to collect their line coverage, LineCoverage, information.

class Test(object):
   ...

  def coverage(self) -> LineCoverage:
    ...


class TestSuite(object):

  def __init__(self, tests: Dict[str, Test]):
    self.__tests = tests

  def __getitem__(self, name):
    return self.__tests[name]
Updated 14/12/2017 19:09

Fork me on GitHub