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

We don't put email-addresses into emailField when logging in with OAuth

Openki/Openki

We do get the email-address when logging in with googles OAuth but we store it in the wrong place so users are not contactable. According to a comment in the issue #100 we don’t get/take email neither when logging in with GitHub. And it’s probable we don’t put it into correct field when user logs in with Facebook neither.

Now that organizers start to use the notification-feature more and more this field is essential. I propose to write a db update as well.

Imported users mail-addresses should be marked as verified, as google and Facebook and GitHub have already done this job for us. (new issue: So shall we write a welcome-mail without verification-part? #749)

Updated 29/04/2017 16:49

Impossible to add proposals

socialappslab/appcivist

@cdparra

Something is not working right with the platform and the add a proposal option. When you save the new proposal you have created and you go on the working group, nothing appears. Same if you publish directly the proposal, it does not appear in the platform.

I have this issue, and one user too, and I think it is the same for everyone.

Updated 30/04/2017 16:22 6 Comments

Le code de l'application suit le guide de style

Kozea/AlphaBet

@Maellepnt @Romlie

L'application fonctionne, mais de nombreuses entorses au guide de style sont à corriger.

Pour vous aider, vous pouvez installer des outils dans votre environnement virtuel, par exemple : - Flake8 et - isort.

N'oubliez pas non plus d'enlever les lignes qui servent à debugger, en particulier les prints. Vous avez également beaucoup de choses que vous pouvez simplifier dans le HTML en privilégiant la syntaxe objet.attribut plutôt que objet['attribut'].

Concentrez-vous sur la forme, nous parlerons du fond ensuite :wink:.

Updated 27/04/2017 21:57

Fix Fix hostname used by client app

ocsigen/eliom

Sadly, https://github.com/ocsigen/eliom/pull/488 makes BeSport’s app fully unusable: it makes the page displayed by the webview be https?://hostname/index.html instead of {file:///blabla/index.html and then file:///blabla/eliom.html}! (and of course, https?://hostname/index.html is a 404…)

Updated 28/04/2017 08:57 5 Comments

Change objective variables to a consistent and simple system

NeonRD1/team327website

Although this would not be pretty on the server side, it may make it easier to change the objectives to simple variable names like “objective1”, “objective2”, etc. This would make changing from year to year less intensive, as only things displayed to the user would have to be changed. However, a mapping of what each objective is would be necessary.

Updated 26/04/2017 23:40

Relevance for animal/person find simple

bobintetley/asm3

We’ve had a problem recently with a customer having an animal called “Ross”. The name was a component of “Crossbreed”, which all their animals where so when doing an embedded animal search via animal find simple, you couldn’t see the relevant result as there were hundreds of other animals first.

The find simple methods should sort the results according to relevancy of a direct match on import fields like name and code just like the search module does (does it always do a/z - what is the sort for simple searches?).

Updated 26/04/2017 17:26

Add method `.hasProperty` (and the opposite one)

parzh/check
let object = {
    prop1: { foo: { bar: 5 } },
    prop2: { foo: { bar: undefined } },
    prop3: 42
};

// alias: check.prop()
check.hasProperty(object, "prop1"); // true
check.hasProperty(object, "prop5"); // false
check.hasProperty(object, "bar"); // false

check.hasProperty(object, ["prop1", "bar"]); // false
check.hasProperty(object, ["prop1", "foo", "bar"]); // true
check.hasProperty(object, ["prop2", "foo", "bar"]); // true (!)
check.hasProperty(object, ["prop3", "foo", "bar"]); // false

// alias: check.noprop()
check.hasNoProperty(object, "prop1"); // false
check.hasNoProperty(object, "prop5"); // true
check.hasNoProperty(object, "bar"); // true

check.hasNoProperty(object, ["prop1", "bar"]); // true
check.hasNoProperty(object, ["prop1", "foo", "bar"]); // false
check.hasNoProperty(object, ["prop2", "foo", "bar"]); // false (!)
check.hasNoProperty(object, ["prop3", "foo", "bar"]); // true
Updated 27/04/2017 13:17

Delete person/animal/lost/found/waitinglist/incident auditing

bobintetley/asm3

When a top level record is deleted like this, only the top level record itself is audited. There’s no way to know what satellite records the record had on deletion as they’re gone forever.

Each deleted satellite record should be audited after the top level record on deletion - use each module’s delete_x function which does this instead of using direct DELETE queries.

Updated 25/04/2017 09:09 1 Comments

dialogs._FlexButtons creates button name from button label.

trin5tensa/pigjar

The user seen button label can be customized via internationalization of the config.ini file. It is not a reliable identifier of the button which has been clicked. Action: Separate names and labels. Labels should always come from the config.ini file except for the simplified OKAlert and YesNoDialog. Button names should always be assigned by the caller.

Updated 28/04/2017 13:53

Explicações sobre issues, labels e milestones

drbeco/tgit

Issues

Crie vários issues, um para cada problema.

Eles servem para ajudar na organização do código e no cumprimento dos milestones.

Lembre-se

todo issue deve ter:

  • Título claro
  • Boa descrição do problema
  • Pelo menos um label
  • Um nome marcado como responsável (assignee)
  • Um milestone associado

Quando e como fechar

Antes de fechar:

  • resolva o problema e avise no issue

Não feche simplesmente, à seco, sem dar uma palavra de satisfação! Deixe uma pequena mensagem dizendo que resolveu, e se possível explique como foi solucionado (inclua commits ou números de linhas de código para clareza).

Fechando:

  • Se você criou um issue, feche-o somente após resolver o problema.
  • Se foi o professor que o criou, entenda o que está sendo pedido e resolva. Feche-o apenas após resolver o problema.

Os issues são parte importante da organização do código. Eles servem como lembretes do que precisa ser feito. Se fechados antes da solução implementada, você estaria contando com sua memória para lembrar do que precisa ser feito. Isso não é viável quando se tem muitos projetos em andamento. Deixe o issue aberto até que realmente tenha solucionado o problema, tenha feito um commit com a solução ou realizado a tarefa indicada.

Para fechar, após 1. resolver o problema, e 2. escrever uma pequena mensagem no issue dizendo que está solucionado (e como), você pode usar um método automático:

No alto da tela, onde está o issue, tem o número dele. Ao fazer um commit, inclua ao final da mensagem de commit os termos fix #X, onde X é o número do issue.

Por exemplo, se você quer fechar o issue número 1 que tratava de um erro de sintaxe, diretamente de um commit, faça uma mensagem assim:

git cm "erro de sintaxe: faltou um ; fix #1"

Isso irá fechar o commit automaticamente após o push. Faça isso no develop, claro. Sempre trabalhe no develop, compile e teste, e só então passe para o master.

Labels

Criar labels, se ainda nao tiver criado:

  • Label “task” : amarelo (para uso exclusivo do professor)
  • Label “urgent” : vermelho
  • Label “late” : azul

Não marque nada como “task”. O label “task” será usado pelo professor para indicar tarefas e sub-objetivos durante o projeto. Assim ficará fácil pesquisar os issues que o professor marcou.

Milestones

Criar milestones se ainda nao tiver criado.

Veja com o professor os títulos, os prazos e a descrição de cada milestone.

Como padrão, o título do milestone será sempre vX.Y, onde:

  • v significa versão
  • X é o número “MAJOR”, ou seja, o número “maior” da versão
  • Y é o número “MINOR”, ou seja, um número que acompanha pequenos ajustes no código.

Bom trabalho!

@drbeco


Este issue foi criado automaticamente. Após ler e resolver o que está acima detalhado, pode fechar. Se já fez as tarefas aqui descritas, desconsiderei-o e feche-o.

Updated 23/04/2017 05:58

Explicações sobre issues, labels e milestones

drbeco/tgit

Issues

Crie vários issues, um para cada problema.

Eles servem para ajudar na organização do código e no cumprimento dos milestones.

Lembre-se

todo issue deve ter:

  • Título claro
  • Boa descrição do problema
  • Pelo menos um label
  • Um nome marcado como responsável (assignee)
  • Um milestone associado

Quando e como fechar

Antes de fechar:

  • resolva o problema e avise no issue

Não feche simplesmente, à seco, sem dar uma palavra de satisfação! Deixe uma pequena mensagem dizendo que resolveu, e se possível explique como foi solucionado (inclua commits ou números de linhas de código para clareza).

Fechando:

  • Se você criou um issue, feche-o somente após resolver o problema.
  • Se foi o professor que o criou, entenda o que está sendo pedido e resolva. Feche-o apenas após resolver o problema.

Os issues são parte importante da organização do código. Eles servem como lembretes do que precisa ser feito. Se fechados antes da solução implementada, você estaria contando com sua memória para lembrar do que precisa ser feito. Isso não é viável quando se tem muitos projetos em andamento. Deixe o issue aberto até que realmente tenha solucionado o problema, tenha feito um commit com a solução ou realizado a tarefa indicada.

Para fechar, após 1. resolver o problema, e 2. escrever uma pequena mensagem no issue dizendo que está solucionado (e como), você pode usar um método automático:

No alto da tela, onde está o issue, tem o número dele. Ao fazer um commit, inclua ao final da mensagem de commit os termos fix #X, onde X é o número do issue.

Por exemplo, se você quer fechar o issue número 1 que tratava de um erro de sintaxe, diretamente de um commit, faça uma mensagem assim:

git cm "erro de sintaxe: faltou um ; fix #1"

Isso irá fechar o commit automaticamente após o push. Faça isso no develop, claro. Sempre trabalhe no develop, compile e teste, e só então passe para o master.

Labels

Criar labels, se ainda nao tiver criado:

  • Label “task” : amarelo (para uso exclusivo do professor)
  • Label “urgent” : vermelho
  • Label “late” : azul

Não marque nada como “task”. O label “task” será usado pelo professor para indicar tarefas e sub-objetivos durante o projeto. Assim ficará fácil pesquisar os issues que o professor marcou.

Milestones

Criar milestones se ainda nao tiver criado.

Veja com o professor os títulos, os prazos e a descrição de cada milestone.

Como padrão, o título do milestone será sempre vX.Y, onde:

  • v significa versão
  • X é o número “MAJOR”, ou seja, o número “maior” da versão
  • Y é o número “MINOR”, ou seja, um número que acompanha pequenos ajustes no código.

Bom trabalho!

@drbeco


Este issue foi criado automaticamente. Após ler e resolver o que está acima detalhado, pode fechar. Se já fez as tarefas aqui descritas, desconsiderei-o e feche-o.

Updated 23/04/2017 05:25

Disallow multiple parents for a workitem during link creation

almighty/almighty-core

Expected behavior

When you select a “parent of” or “child of” link type in the UI, the core needs to check if a parent for the current work item already exists. Currently the decision on whether a parent link exists or not shall be made analog to the list children action that @baijum created.

If a parent exists, the core’s workitem/link/type_repository.go needs to return an error from the Create function.

Actual behavior

Currently you can create links without any restriction.

Updated 25/04/2017 08:44 2 Comments

Install: Client install script does not work

ISISComputingGroup/IBEX

The client install script no longer works. It errors with:

Z:\3.2.0\Client>if exist "Z:\3.2.0\Client\..\genie_python" (
set GENIE_PYTHON_TOP=Z:\3.2.0\Client\..\genie_python
 call \genie_python_install.bat
)  else (
set GENIE_PYTHON_TOP=Z:\3.2.0\Client\..\..\genie_python
 for /F %I in (\LATEST_BUILD.txt) DO SET LATEST_BUILD=%I
 call \BUILD-\genie_python_install.bat
)
'\genie_python_install.bat' is not recognized as an internal or external command

The reason is that the varibales in the if are replaced early not during the if evaluation so this does not work.

Updated 26/04/2017 13:10 5 Comments

App crash : colorizing

lybros/Appa

the app crashes if we are retrieving colors from the image, which is not in the root of IMAGES_LOCATION directory, but elsewhere (we’re loosing some parts of the file when concatenating IMAGES_LOCATION and IMAGE_NAME)

must be fixed.

Updated 15/04/2017 23:00

個人頁面的喜愛文章於分頁上的不會更新

internlens-tw/InternLens

在主頁點一則經驗後,會另外跳出單則經驗,點選該則經驗的 “喜愛文章"後。 於經驗的分頁點navigation bar 上的個人頁面連結,在個人頁面不會看到新增的喜愛文章。 除非點回那個分頁 navigation bar 上的Internlens ,回到首頁在點回個人頁面後,再點回個人頁面才會呈現新的喜愛文章。 只是這時假如又重新整理分頁,個人頁面又會回到新增前的狀態。

然後假如從一開始點開的透視鏡主頁點去個人頁面,是馬上會有新增的喜愛文章。 只是在分頁的話就不會有了

Updated 18/04/2017 07:20

Polaris jaws: various minor changes

ISISComputingGroup/IBEX

After discussion with Ron Smith;

  • Change readback value boxes on jaws OPI “animations” to use a non-etched border (Ron’s comment was that it was unclear which one was the setpoint and which one was a readback)
  • Add a “centre” option to the OPI + Jaws db records (this is always just an offset for each jaw set, there is nothing fancy needed here, functionality for calculating centres already exists in the jaws db records it just needs passing down from the jawset db record)
  • Put setpoints (gaps/centres) at the top of the OPI and readbacks at the bottom. This is just a rearrangement, should be very quick and easy.
  • In the OPI, add a message if manager mode is disabled and you can’t set values. Ron’s comment was that it wasn’t obvious enough why you couldn’t set values.
  • Output the calculated values for jaw set 5, without actually causing the jaws to move. This might involve a bit of changing how the DB records work; check that the functionality is unchanged.
  • Two decimal places is plenty. Can we just display 2 d.p. throughout the OPIs?
  • Double check that the script used to “animate” the northern jaw in jaws manager works properly. When we demoed it the northern jaw didn’t appear to move until we reloaded the OPI.
Updated 28/04/2017 16:07 1 Comments

Class 3s

nitrodragon/ThunderingSky

Well, as I’m sure we’ve all noticed (all 3 of us), Class 3s happen to have no base stats.

That’s kinda lame.

All the Class 3s (Paladin and onward) need base stats, and Jared, if you’ve got the time, I’m gonna assign that to you (see? there’s an assign thing next to the Issues things :smile: )

Updated 18/04/2017 05:32 3 Comments

Add shared ride type Shared-Vehicle

TIXI24/sfitixi

Scenario: - Shared rides can be of type shared-start or shared-target - The type shared-vehicle is missing (gap) but part of the original specs - Improve flexibility and usibility - Murphy: „Anything that can go wrong will go wrong.“

bildschirmfoto 2017-04-10 um 18 53 35

Note: - For detailed information see DropBox/TIXI24/design/usecases/sharedRideRevisted.pptx

Updated 11/04/2017 12:22 1 Comments

Failed to build hstr-0.22 against ncurses-6.0

dvorka/hstr

Hi,

I failed to build hstr-0.22 against ncurses-6.0 on CentOS 7 with gcc-4.8.5. ncurses-6.0 comes from Spack package manager which works well with other packages. The error messages are as follows, could you check it at your earliest convenience?

In file included from include/hstr_curses.h:25:0,
                 from hstr_curses.c:20:
/lustre/spack/sandybridge/linux-centos7-x86_64/gcc-4.8.5/ncurses-6.0-75hnzrecoib5eqdvfchl6n2jgcxc6dgo/include/unctrl.h:60:38: error: conflicting types for ‘unctrl’
 NCURSES_EXPORT(NCURSES_CONST char *) NCURSES_SP_NAME(unctrl) (SCREEN*, chtype);
                                      ^
In file included from /usr/include/curses.h:1989:0,
                 from include/hstr_curses.h:25,
                 from hstr_curses.c:20:
/lustre/spack/sandybridge/linux-centos7-x86_64/gcc-4.8.5/ncurses-6.0-75hnzrecoib5eqdvfchl6n2jgcxc6dgo/include/unctrl.h:57:38: note: previous declaration of ‘unctrl’ was here
 NCURSES_EXPORT(NCURSES_CONST char *) unctrl (chtype);
                                      ^
make[1]: *** [hstr_curses.o] Error 1
make[1]: *** Waiting for unfinished jobs....
In file included from hstr.c:26:0:
/lustre/spack/sandybridge/linux-centos7-x86_64/gcc-4.8.5/ncurses-6.0-75hnzrecoib5eqdvfchl6n2jgcxc6dgo/include/unctrl.h:60:38: error: conflicting types for ‘unctrl’
 NCURSES_EXPORT(NCURSES_CONST char *) NCURSES_SP_NAME(unctrl) (SCREEN*, chtype);
                                      ^
In file included from /usr/include/curses.h:1989:0,
                 from hstr.c:26:
/lustre/spack/sandybridge/linux-centos7-x86_64/gcc-4.8.5/ncurses-6.0-75hnzrecoib5eqdvfchl6n2jgcxc6dgo/include/unctrl.h:57:38: note: previous declaration of ‘unctrl’ was here
 NCURSES_EXPORT(NCURSES_CONST char *) unctrl (chtype);
                                      ^
mv -f .deps/hstr_regexp.Tpo .deps/hstr_regexp.Po
make[1]: *** [hstr.o] Error 1
mv -f .deps/hstr_blacklist.Tpo .deps/hstr_blacklist.Po
mv -f .deps/hstr_utils.Tpo .deps/hstr_utils.Po
mv -f .deps/hashset.Tpo .deps/hashset.Po
mv -f .deps/hstr_favorites.Tpo .deps/hstr_favorites.Po
mv -f .deps/radixsort.Tpo .deps/radixsort.Po
mv -f .deps/hstr_history.Tpo .deps/hstr_history.Po
make[1]: Leaving directory `/tmp/pytest-of-rpm/pytest-43/test_keep_exceptions0/tmp/spack-stage/spack-stage-d8BDjC/hstr-1.22/src'
make: *** [all-recursive] Error 1
Updated 09/04/2017 18:58

Include CIR in release files

cadeath/Dalton

When creating a release file, include the following: 1. Installer 2. Memorandum (.doc/.jpg) 3. .cir file base on the Memorandum included

Please provide the latest deployed Installer, Memorandum and CIR files This is to eliminate error in deployments

@cloudNine09 @marzxxx90 @jayr

Updated 08/04/2017 14:56

Add Support for WooCommerce Gallery

presscustomizr/customizr

Hi,

With reference to the following forum thread. https://wordpress.org/support/topic/product-photo-gallery-2/

WooCommerce removed the product gallery feature and need themes to use add_theme_support https://woocommerce.wordpress.com/2017/02/28/adding-support-for-woocommerce-2-7s-new-gallery-feature-to-your-theme/

Please consider adding back support for this feature.

Thank you

Updated 06/04/2017 08:25 1 Comments

Technically a Excel Injection

Bribberish/auto-form

Technically you can inject code into excel, this would have the worst effect of being able to uncover peoples infomation using codes such as =A1:D10, this would set its value to those. If this was not humanly checked and a automatic email was sent it could be an issue as it would email out all of their infomation. However I do not belive you could inject VBA code.

This can be exploited in the Organisation input and the Team name input.

Updated 05/04/2017 08:46

Prix négatifs

covoiturage-libre/covoiturage-libre

Comportement actuel

Il est possible de tomber sur une annonce qui affiche un prix négatif, ce prix devient nul (0 €) lors de l'accès à la fiche du trajet. capture d ecran_2017-04-03_23-45-41 capture d ecran_2017-04-03_23-45-58

Comportement attendu

Le prix devrait être positif.

Étapes pour reproduire le problème

Chercher un trajet, mais cela dépend de l'annonce. Pour le cas présent : - Ville de départ : Bordeaux - Ville d'arrivée : Douvaine - Date : 08/04/2017

[] Développement [X] Production

Updated 05/04/2017 14:56 2 Comments

problems creating a directory with deploy.py

McIndi/mast.installer

One of our customers is having a problem with deploy.py, when attempting to create a directory mast issues a get-filestore request which fails with a 500 and a message “Internal error (from client)”. I tracked this down to a parameter being passed to get-filestore which included the filename. I was not able to determine why this happened, but I am setting this up in my lab and will update this issue when I have more details.

Updated 30/03/2017 21:13

New steps needed to install Linuxbrew

gvlproject/microgvl.ansible.filesystem

The order is important.

unset HOMEBREW_DEVELOPER
export PATH=/home/linuxbrew/.linuxbrew/bin:$PATH

git clone https://github.com/Linuxbrew/brew.git /home/linuxbrew/.linuxbrew

brew install hello ruby # will install glibc etc
brew test hello

cd /home/linuxbrew/.linuxbrew/Cellar/glibc/2.19/lib   # check correct version!
ln -s ../../../gcc/5.3.0/lib/libgcc_s.so.1 .

brew install python python3 r

brew tap homebrew/science
brew install bwa
brew test bwa
Updated 29/03/2017 05:03

Do subtyping.

ThoughtWorksInc/DeepDarkFantasy

Why: DBI (Term DBI) should entail DBI (Term Lang) so need some subtyping crtieria.

But Why Term? Dynamic Eval. If a Term need to be diff and evaled under different context, simply use Comp that return pair of different repr

How? Generic Solver returning constraint list, search through it by only climbing the class hierarchy, using a list to keep track of all alternative. Cannot solve instance of unknown <: C => unknown <: D, when C is subtype of D, though, but can always be resolved when in the concrete registeration. Also need registering and is a bit slow, a bit hard to write. Maybe manually saving instance with overlapping instance/incoherent instance would help.

Other solution: specialize into sub. Do not have such problem but create ton of similar Class. Also need to manually impl subtyping hierarchy registration for each new type. Could probably use Template Haskell to help ths.

Updated 29/04/2017 05:22 3 Comments

Fatal error after update 3.5.9 : OptimizePress related

presscustomizr/customizr

After uploading the latest update from customizr (3.5.9) I can’t use the plugin Optimize Press anymore. The following fatal error appears in my screen:

Fatal error: Call to a member function czr_fn_is_front_help_enabled() on null in /public/sites/www.goedomgaanmetgeld.nl/wp-content/themes/customizr/inc/czr-init.php on line 7412

Pages I have already created will stil show on my website, but I can’t change them anymore and I can’t create new ones.

Please let me know if this bug can be fixt any time soon.

I tried in both Google Chrome and Firefox.

Updated 23/03/2017 10:22

Consistent Driving

Team612/612-2017

So an issue we were having at competition at the past two competitions is that because of differences in the drive train, both sides don’t drive exactly the same way when the same amount of voltage is applied to each side. This not only affects the drivers' ability to drive but also our autonomous reliability, as with this issue unsolved, our simple drive forward auto can barely place a gear because it doesn’t drive forward consistently.

The current solution is just applying an arbitrary dampener to the faster side. Not only does this not work well, its just bad code.

What we want to do, hopefully before District Champs, is use PID to set both sides to the same speed. With the practice bot, we’re not limited by 6 hours of unbag time/time being used by other subteams to work on it. Given the sheer amount of stuff that we need to do, expect extended programming meetings.

Anyway, back to the issue, what we want to do is:

  • [x] Create a branch for tuning drive train PID

  • [ ] Find full speed in native encoder units

  • [ ] Find PIDf constants that work

  • [ ] Implement on master by modifying existing DriveProfile class and Drivetrain methods

AIM Robotics does something similar, but they use position instead of speed.

If we can get this to work, we can replace almost all the throttle mode stuff being used with driving by RPM.

Updated 31/03/2017 02:02

Fork me on GitHub