Should we consider add example to each topics?
How to use it and best practice to use it!

I.e: for helloworld demo the example would be http://localhost:8080/demo/hello?who=ibrahim

There are some interesting algorithms in simulation from Physics, Chemistry, and Engineering especially regarding Monte Carlo simulation: Heat Bath algorithm, Metro-Police algorithm, Markov Chain Monte Carlo, etc.

In raising this issue, I confirm the following: {please fill the checkboxes, e.g: [X]}

• I have read and understood the contributors guide.
• The issue I am reporting can be replicated.
• The issue I am reporting isn't a duplicate (see FAQs, [closed issues](htt

• We have BFS and DFS images in both Breadth First Traversal and Depth First Traversal. We should have illustrations in the respective sections.

The current README in the repo is huge and could be more fashioned. I'm a believer that README's should be straightforward and for developers, not documentation.

There are a couple of options to build an actual documentation and leave the README clean and concise. Here are some:

• Use GitHub Wiki - Simple and easy, but not too Pythonic or good for Python libraries.
• Use Sphinx - reST based

When using Viper in a client application, it can be useful to log configuration registries as a diagnostic, to understand what the client did. In situations where we don't want to log to stdout, it would be nice to be able to provide an io.Writer for Viper to use instead.

I cloned Ventoy but then failed to find documentation on how to build Ventoy. I would assume in the top level directory there would be some documentation that explains how to build Ventoy.

  /Users/travis/build/ray-project/ray/python/ray/node.py:533: DeprecationWarning: Redis.hmset() is deprecated. Use Redis.hset() instead.
    redis_client.hmset("webui", {"url": self._webui_url})
  /Users/travis/build/ray-project/ray/python/ray/worker.py:358: DeprecationWarning: Redis.hmset() is deprecated. Use Redis.hset() instead.
    "run_on_other_drivers": str(run_on_other_drivers),
  

Let's enable loading weights from a URL directly

Option 1:

Automate it with our current API

Trainer.load_from_checkpoint('http://')

Option 2:

Have a separate method

Trainer.load_from_checkpoint_at_url('http://')

Resources

We can use this under the hood:
(https://pytorch.org/docs/stable/hub.html#torch.hub.load_state_dict_from_url)

Any tho