parallel

Description

There are multiple user requests of using GraphNN data (node and edge lists) as sample batches into a custom RLlib model.

https://discuss.ray.io/t/rllib-variable-length-observation-spaces-without-padding/726
https://discuss.ray.io/t/working-with-graph-neural-networks-varying-state-space/5730/2

The recommended method today is to use Repeated observation space and VariableVal

Summary

mypy shows some issues in LightGBM's Python package.

mypy \
    --exclude='python-package/compile/|python-package/build' \
    --ignore-missing-imports \
    python-package/

python-package/lightgbm/compat.py:12: error: Name 'Series' already defined (possibly by an import)
python-package

I see comments suggesting adding this to understand how loops are being handled by numba, and in the their own FAQ (https://numba.pydata.org/numba-doc/latest/user/faq.html)

from llvmlite import binding as llvm
llvm.set_option('','--debug-only=loop-vectorize')

You would then create your njit function and run it, and I believe the idea is that it prints debug information about whether

Expected behavior

GridSampler does not have a seed argument, but it randomly shuffles an evaluation order of trials. It makes optimization results unreproducible if objective functions depend on previous trials, e.g., pruning. We should add a seed argument like TPESampler and RandomSampler.

Environment

• Optuna version: 3.0.0b1.dev
• Python version: 3.8.6
• OS: macOS-10.16-x

Version of Singularity:

3.0.3

Expected behavior

Some progress or update information during the creation of the SIF file.

Actual behavior

During "Creating SIF file..." step, the console does not produce any visible output for the user - but does create the resulting file eventually.

Steps to reproduce behavior

I was executing a few “larger” builds through the bui

• I have searched issues for similar feature requests

What is this feature about (1 sentence)

Base path should be runtime configurable via the env variable.

Why is it needed? What is the value? For whom do we build it?

If one wants to expose the dashboard not on the domain root but let's say at my-domain.com/sorry-cypress/dashboard the dashboard will try to load the r

Current behavior:

root [0] TFile f("root://eospublic.cern.ch//eos/root-eos/benchmark/Run2012B_SingleMu.root")
Error in <TFile::TFile>: file /eos/root-eos/benchmark/Run2012B_SingleMu.root does not exist
(TFile &) Name: /eos/root-eos/benchmark/Run2012B_SingleMu.root Title:

Desirable behavior:

root [0] TFile f("root://eospublic.cern.ch//eos/root-eos/benchmark/Run2012B_Single