dondi
dondi
@ntran18 will review where we left off here (looks like mainly a PPI question and not GRN) to determine next steps. However, we will not wait on this issue for...
Effectively updated the database as of v7.1.1 release
Possibly prepending text or looking into `optgroup` may make this low-hanging fruit
Dependency issue: https://medium.com/@alex.birsan/dependency-confusion-4a5d60fec610
I looked into how we integrate with Coveralls and it turns out that it is through a script that Travis runs. That script is currently reporting an error and that’s...
I started exploring why the script now fails when it used to succeed. First stop was dependency versions…I tried to update to a newer version of `coveralls` but the error...
We clarified at the 4/23 meeting that we can go ahead and have the warning appear each time. A “don’t show this again” option might be something for the future
After reviewing the deployment on `beta`, it was noted that: * The node coloring options only appear in the menu bar and not the sidebar after activation * Node coloring...
@ceciliazaragoza will also move the warning message outside of the network-opening routine so that it will only open at the point that node coloring is enabled. This will result in...
No definitive response yet, plus now there is an announcement regarding change of SSH keys. For now, consistently running the test suite will serve as a workaround