parallel

The implementation of the progress reporter, particularly the table generation, suffers from cluttered legacy code. The functions are long, messy, and pass around long argument lists. It is hard to unit test. We should clean this module up do make it easier to extend and modify.

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

Reporting a bug

• [x]

Issue description

This issue was originally reported by @fukatani.

When I clicked the Edit on GitHub in some reference page, I got 404 errors.

This i

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