This is a(n):

• New algorithm
• Update to an existing algorithm
• Error
• Proposal to the Repository

Details:

We can make a file may be READ.

This would have made my life easier when investigating iterative/dvc#4570.

Another question to ask is that dvc version can only have a limited amount of information. Should there be dvc version --json?

Problem

Right now, the option to change availability status is hidden in profile settings. People might not realize that they have an option offline. To improve this UX, provide a setting right on the sidebar to change the status

Design

<img width="391" alt="Screenshot 2020-09-14 at 5 24 24 PM" src="https://user-images.githubusercontent.com/2246121/93082974-73c19e80-f6af-11ea-90da

Since #378 is waiting for release, we can add an option to the console.

My suggestion would be, to have an account to be blocked, as a requirement.
So, that accidents are less likely to happen.

🚀 Feature

When we run baseline configuration :

python -m torch.distributed.launch --nproc 2 --use_env -m py_config_runner ./code/scripts/training.py ./configs/train/baseline_resnet101.py

When model is instantiated, it downloads ImageNet pretrained weights for ResNet backbone. In above case, it downloads twice the same file. Let's set up the model such that we run the training

What happened:
Tried running Regression test using command ./test/run_regression_tests.sh $PWD/build.
The test

The Jenkins project now uses "agent"and "controller" as official terms. See https://issues.jenkins-ci.org/browse/JENKINS-42816 and https://groups.google.com/forum/#!topic/jenkinsci-dev/CLR55wMZwZ8 for the reference. There are some occurrences which could be cleaned up:

• Docker image names
• Configuration entries for plugins which now support "agent"/"controller" aliases.
• Documentation tex

Right now we only set the ip and last_seen_at fields when a customer record is created. Let's update the customer update_metadata endpoint (https://github.com/papercups-io/papercups/blob/master/lib/chat_api_web/controllers/customer_controller.ex#L58) so that it also handles this.

(I think we can just default the last_seen_at field to the current timestamp for now.)

Is your feature request related to a problem? Please describe.
cState is only a frontend, a backend monitor bot should be provided.

Describe the solution you'd like
I've wrote a very simple bot myself at https://github.com/thuhole/status-probe, with these features:

• Monitor websites and automatically publish incidents using GitHub API.
• In case of GitHub API downtime, the bot wo

Context

There is a use case for creating a timer that has a variable duration. For example, if you wanted to randomly space events during a game.

Proposal

Add the ability to specify a range (min and max) of time and allow the timer to randomly choose a duration within that range.

During an upgrade of the Kubernetes package versions in PR #636 a bunch of context.TODO() function call parameters were added. We should go through and plug these into any existing contexts we have and implement new contexts for the others.