For running features and app
For running features and app
Bowser was not responding to messages, so I tried to connect to the docker-machine this error message was displayed when trying to enable the bowser environment:
$ eval $(docker-machine env bowser)
Error checking TLS connection: Error checking and/or regenerating the certs: There was an error validating certificates for host "126.96.36.199:2376": dial tcp 188.8.131.52:2376: connect: connection refused
You can attempt to regenerate them using 'docker-machine regenerate-certs [name]'.
Be advised that this will trigger a Docker daemon restart which might stop running containers.
I ran the suggested command
docker-machine regenerate-certs bowser, which also restarted the docker services. This could be because it has been while since the machine was started. If that is the case, these TLS certs may need to be regenerated on a regular basis.
This should be a pretty simple script that uses
docker-machine ssh to run commands that zip up the redis data, and then
docker-machine scp to transfer it back. This would be a step in the right direction for supporting scheduled automated backups.
Because manually running the update scripts is no fun.
My setup is: -Desktop Mic - blue yeti -Speakers - 5.1 surround
I think maybe the mic is always on and the sound causes looping feedback… it sounds really bad and i had to unplug my mic. DM me if you want a sound recording.
Essa issue destina-se a fazer a alteração de versão do APK automaticamente na integração automatizado.
Essa issue destina-se a refatorar o usuário, alterando o singleton dele de Player para User.
Writing down some of the thoughts regarding package separation.
Main packages: - parser: uses postcss, with additional required processing by us. - transformer: should it be a postcss js plugin? - generator: to print actual css assets - css-runtime: isomorphic runtime that stylesheets use to register themselves. It should support browser and SSR scenarios. - language services: expose diagnostics and type information about stylable stylesheets. - test-utils: helpers to test styles and target dom elements using style API.
Integrations: - webpack - node - jest transformer (?) - vscode extension (in a separate mono-repo?)
Would be great if we start using the
@stylable npm scope to group packages together in
My laptop needs about 30s to run clang-format since the script currently reindents all files regardless of whether or not they have been modified. This PR adds a new target indent-branch that only reindents files that have been modified (or added) since the last commit to master. This takes less than a second to run (with a few files changed) on my laptop.
We should document all the engine’s code.
I suggest to use Doxygen, which is widely used. Other alternatives, maybe?
Either start an emulator or connect real hardware to the CI server.
The merging and synchronizaton mechanism of the SORMAS app is very crucial and complex. We need to extend the automated tests done to make sure we have a robust mechanism and to detect problems that are introduced by new features and improvements.
The existing automated tests need to also include the push and pull mechanics to allow us to test more realistic sequences of user actions in the app.
Note: This is not about UI tests.
Functions such as
genericButton are used multiple times, and I think the
notifications file should not be kept in the root directory. We could make a
src/utils folder to house these.
travis_retry command. Sometimes code contributors have to push a commit again to restart the tests failed with server problems. Auto retrying reduces them.
We should create proper documentation for the release process. The current release process is:
That logic is wrong, in
.travis.yml. See here for a PR modifying Triangulation_2: Triangulation_3 can be ignored, but the full test of “Triangulation_2 Triangulation_3 Union_find” is ignored!
The job should be ignore only if all packages of the job are ignored.
Please fix for 4.12.1.
So we can have a way to test new PRs in an environment very similar to production. Probably we’d need to run the bot in a dry mode but even then it would be beneficial.
🌵🌵🌵 This depends on #4751, go review that first 🌵🌵🌵
As part of #4588 there will likely be some changes to the merge call-to-action, so this is laying the groundwork for some of that by extract it out into it’s own component to simplify the
Compare view a bit.
@dagood added functionality to buildtools to allow us to get auto updated based on ProdCon builds using the orchestration feeds.
I believe we would have to update our subscription as the release moves milestones which is reflected by dirs in the versions repo.
Instead of like this:
If you mess up a Nav.createLink(…) and miss an argument or accidentally give it undefined, you get an undecipherable error. We should add asserts to make mistakes clearer.
The ipynb file will still have them but the html made by
main.py will not. See: http://nbconvert.readthedocs.io/en/latest/customizing.html#Templates-using-cell-tags
Is your feature request related to a problem? Please describe. As a lot of different code metrics might become important in the future, the administrators of Delphi should be able to view and edit the list of Hermes queries that are executed by the crawlers.
Describe the solution you’d like A list view should allow the administrators to add / delete / disable queries, which should include not only the jar file implementing the query, but also a description of what the query does. On top of that, it would be nice to have the possibility to apply these new queries to the projects that have already been added to the elasticsearch database in the past.
Describe alternatives you’ve considered None
Additional context This is related to the issue https://github.com/delphi-hub/delphi/issues/5, which is aimed at the user being able to contribute queries. This issue adresses the management aspect for the administrators.
Anyone familiar with the cmake in SeqAn3? @marehr :grin:
entry-point loading should be moved into a interface where one passes the entry-point system (either pkg_resources or entry_points), the plugin-manager and the entrypoint name into a helper that facilitates registration
The index page of http://saros-build.imp.fu-berlin.de/ still points to SourceForge. This link has to be modified.
Use GitHub Plugin in SonarQube. This plugin adds issues as comment.
masterbuild rather than the latest build, but the docs aren’t quite clear on how to structure the URL, and I had to reverse-engineer what ReactiveUI has setup to get this showing. Maybe @damovisa can help when he has a moment :trollface:.
I believe you will need to make an amazon developer account, so that i can give you security roles. I’ll work this out, and task you guys when i find out what your steps are.
Come up with some easy way to automatically check the validity and/or coverage of localization files, relative to
When we’re using the localization functionality to translate pages, we should also make the language setting in HTML match the current language. Need to figure out how to do this through React.
if i do a
git clean -fdx before the docker build, then i get:
if i build lab then it works. but really, the software should all be built in the container. i think we should fix this and put the “clean” into the release doc.
Investigate doing this in Appveyor.
When done, do for EFCore.PG as well.
help wanted label means please contribute to this idea=====
What’s the problem.? The current landing page is a hackathon project. It doesn’t track anything, it doesn’t link accounts to book rides, we would ultimately burn cash serving the site the way it is. I want to minimize the cost of the prototype app, by limiting the usage of the site in the public sphere, until we feel we’re ready.
Context, research, and learnings The product is in very pre-alpha stages, and I would like to put it behind an auth wall. My hope here is that we will have a simple login to gain access to the site for testing (potentially cookie’d so we don’t re-auth constantly). Regular users will not have credentials to access the site, and will see a lamppost coming soon page or something.
How do we create a solution? I was thinking that we’d modify the root route to check for auth and grant/deny, then render accordingly. I think the complex part- is in building an MVP auth micro service, that we can scale to also serve our feature for linking accounts from service providers. I’m thinking this could be- - node api microservice. There are a bunch of boiler plate things out there. Here’s one- https://github.com/stanislav-web/ecs-auth-microservice - new auth service deployed to our Fargate cluster. Connected to our dev workflow. - token based auth (??? is there a better way these days than to validate a token on each subsequent request) - new requests route to auth microservice, gets a token, subsequent calls route to front-end web service. - Users only ever hit the front-end web service. Auth tokens between the microservice swarm are unnecessary for this MVP
<!– ESLint adheres to the JS Foundation Code of Conduct. –>
What is the purpose of this pull request? (put an “X” next to item)
[x] Other, please explain:
<!– If the item you’ve checked above has a template, please paste the template questions below and answer them. (If this pull request is addressing an issue, you can just paste a link to the issue here instead.) –>
<!– Please ensure your pull request is ready:
- Read the pull request guide (https://eslint.org/docs/developer-guide/contributing/pull-requests) - Include tests for this change - Update documentation for this change (if appropriate)
<!– The following is required for all pull requests: –>
What changes did you make? (Give an overview) replaced Browserify with parcel
Is there anything you’d like reviewers to focus on?
defaults. Is there some best pratice about it?
The patch makes use of the commenting capabilities and the recent Ubuntu support of AppVeyor.
Jenkins contains multiple jobs. Before migrating all jobs it is useful to verify whether all jobs have to be migrated.
Create job that does the same as http://saros-build.imp.fu-berlin.de/jenkins/job/Saros-Full-Gerrit/
Review code signing process and how it is configured.
MEETING NOTES Code Signing * Talk with Larry O * Get us on own server? * Does us changing servers impact users due to singing? * RXT needs code signing as well
Cert expire? * We should look into
🚀 all the things!
Micropayments in developmental contexts
With #800, we can also have a top-level document
MetadataSore that consumes
FileService and provide up-to-date metadata that’s generated from a particular language service, for example:
css.classesfor that file
Later the user triggers html class completion
metadataStore.getMetadata(doc.uri)["css.classes"]will have the relevant data
Another place that can be simplified is the current
findComponents, which provides component intellisense based on the shape of each of the depended components.
See the report at https://lgtm.com/projects/radare/radare2/alerts/?mode=list.
Moreover, this thing can be integrated in master builds and pull requests: see https://lgtm.com/help/lgtm/using-lgtm-analysis-continuous-integration
It seems like we paths floating around in different states of canonicalization. It might be good to give them different types so that we don’t accidentally file comparisons. For example, a raw path
C:\src\a.js is slash-normalized to
C:/src/a.js and canonicalized to
c:/src/a.js. None of these are equivalent using string
===, which may not be what the caller intended.
Essa issue destina-se a integrar o login ao servidor.
Currently Vetur’s file system access is scattered throughout the code. However, we also use
TextDocuments from https://github.com/Microsoft/vscode-languageserver-node to track LSP documents, and with the new FileEvents generated through VS Code file watcher, it’s time to put these all together.
Running configure takes a lot of time on windows.
Having a flag to use cached configure data for rebuilds would speed this up nicely.
I can run configure for GHC with -C myself. But adding the flag for the configure process of base is a different story. Ideally libraries would also use the same configure cache as ghc, so it would be faster even on the first build:
Here are the times for base and ghc itself on my machine. (SSD, skylake i7)
|name||./configure||./configure -C (rerun)||difference|
|base||1m 40s||31s||-1m 9s|
This is a product requirement. Since the similarity is dangerously close to google project and billing project, we need to be careful about calling these out when necessary. In the code, it may even be useful to call these “user projects” or “researcher projects” to distinguish them.
Examples: 1) Remove the Jobs and History tabs. 2) Show a “not yet implemented” modal on Share/Publish/Delete and on “windows” icon. 3) “ on Find Data/Find Code.
Geocoding requests will no longer be proxied through ORS, instead they will be directly made to the pelias backend.
Running services as root in the container means running them as root on the host! This is bad for security.<br /> Info how to fix this: https://gist.github.com/alkrauss48/2dd9f9d84ed6ebff9240ccfa49a80662
Improve coding style for
Makefile files in
When building modules in the
tools/labs/ infrastructure, the following non-critical error message is output:
dirname: missing operand Try 'dirname --help' for more information.
Update build infrastructure to prevent the message from being displayed.
Automated verification (i.e. the use of vmchecker) requires a clean slate image file, installing check scripts inside the virtual machine and extracting output files. Create documentation for this.
There is no documentation on how to use and update the
tools/labs/qemu/kernel_config.x86 file. Document the use of
make olddefconfig and
<!— Provide a general summary of the issue in the Title above –>
<!— Provide a detailed description of the change or addition you are proposing –> <!– If it’s related to a problem, give a clear and concise description of what the problem is. Ex. I’m always frustrated when […] –> Right now it’s a manual process that could be automated.
<!– A clear and concise description of what you want to happen or example of intended usage –>
Should add the new command from
help.json to our
README.md and https://sirmerr.github.io/camperbot/#/camperbot/commands
<!— Provide a general summary of the issue in the Title above –>
<!— Provide a detailed description of the change or addition you are proposing –> <!– If it’s related to a problem, give a clear and concise description of what the problem is. Ex. I’m always frustrated when […] –> Our linter is set up with single quotes as a default, but due to our bot having to respond in conversation, we have to escape single quotes a lot.
<!– A clear and concise description of what you want to happen or example of intended usage –> We should have double quotes as a default instead and replace existing single quotes
<!— Not obligatory, but suggest an idea for implementing addition or change –>
Change/Remove line in
.prettierrc depending on what prettier’s default is:
Administrators of a Delphi instance might want to automate certain management tasks or use information provided by the management interface in their own programs. By implementing a REST based API this would be possible with minimal overhead for the developers. As almost all programming languages provide some sort of support for REST, a lot of administrators could make use of this feature. The current authentication framework silhouette supports the implementation of such an interface (an example application can be found here: https://github.com/datalek/silhouette-rest-seed ).
We don’t want to be bogged down by trying to support mobile users right now, but it would be nice if we had a pattern that still functioned at smaller screen sizes (see image). @MattPutnam added a
min-width to the body as an experiment that nearly got us there.
We must define an officially supported minimum desktop screen size: __________ (see if there is guidance from FireCloud Google Analytics)
Below this width, it is appropriate to trigger scrolling rather than more complex intelligent rearrangement
More bet game variety
When at 0 bux you’re stuck. Need a way to generate them.
Timer, activity, etc Probably a timer though
It’s a PITA to maintain support for all typescript versions back to 2.4. There are also some missing tests because that would simply cost too much resources.
Here’s the plan: * support the last 3 versions * that’s approx. 6 months time for users to upgrade * keep supporting these versions until the next major version of this package * test every supported version * test typescript@next
This helps keeping the parallel tests for different typescript versions around 4. It also helps removing compatibility code and test fixtures.
Signed-off-by: Artyom Bakhtin email@example.com
<!– You will not see HTML commented line in Pull Request body –> <!– Optional sections may be omitted. Just remove them or write None –>
<!– ### Requirements –> <!– * Filling out the template is required. Any pull request that does not include enough information to be reviewed in a timely manner may be closed at the maintainers' discretion. –> <!– * All new code must have code coverage above 70% (https://docs.codecov.io/docs/about-code-coverage). –> <!– * CircleCI builds must be passed. –> <!– * Critical and blocker issues reported by Sorabot must be fixed. –> <!– * Branch must be rebased onto base branch (https://soramitsu.atlassian.net/wiki/spaces/IS/pages/11173889/Rebase+and+merge+guide). –>
Python and Java bindings for development under Windows platform <!– What benefits will be realized by the code change? –>
None <!– What are the possible side-effects or negative impacts of the code change? –> <!– If no drawbacks, explicitly mention this (write None) –>
GitHub issue organization guidelines for large issues
one can efficiently keep track even of long-term goals in a standardized way.
This issue was discovered as part of the geli development team retrospective on 2018-05-17.
It would be nice if my view was just there instead of having to wait for the spinner each time.
Show the stale data greyed out, with the spinner overlaid on top. Once the load completes the spinner goes away and the updated data is shown at full saturation.
Task: Document how repo should be used and how it integrates with its parent repo. Repo: datagov-deploy-solr
Task: Document how repo should be used and how it integrates with its parent repo. Repo: datagov-deploy-elasticsearch
Task: Copy in appropriate file and edit/or amend as needed. Repo: datagov-deploy-solr
Task: Copy in appropriate file and edit/or amend as needed. Repo: datagov-deploy-elasticsearch
Task: Build out repo structure Repo: datagov-deploy-solr
Task: Build out repo structure Repo: datagov-deploy-elasticsearch
Task: Document how repo should be used and how it integrates with its parent repo. Repo: datagov-deploy-jetty