bob issueshttps://gitlab.idiap.ch/groups/bob/-/issues2021-10-29T15:34:56Zhttps://gitlab.idiap.ch/bob/bob.devtools/-/issues/70Removing `llvm-tools` from build dependencies in `bdt create` is undesirable2021-10-29T15:34:56ZAndré AnjosRemoving `llvm-tools` from build dependencies in `bdt create` is undesirableThis was done to overcome another issue regarding `llvm-tools` and its dependence to `libllvm10`.
One of the (build) packages we depend on wants to have `libllvm10=10.0.0`, but "llvm-tools" requires `libllvm10=10.0.1`. This creates a c...This was done to overcome another issue regarding `llvm-tools` and its dependence to `libllvm10`.
One of the (build) packages we depend on wants to have `libllvm10=10.0.0`, but "llvm-tools" requires `libllvm10=10.0.1`. This creates a conflict. Build requirements from our packages will end-up bringing in the requirement for "llvm-tools".
To test this, on a macOS system, try the following:
```sh
$ conda create --dry-run --name xxx --override-channels --channel=http://www.idiap.ch/software/bob/conda/label/beta --channel=http://www.idiap.ch/software/bob/conda --channel=defaults --dry-run 'bob-devel=2021.01.28.*' clang llvm-tools
```
The problem is, possibly, that our own bob-devel brings in dependencies that make the above build tools conflict. Removing any of the 3 packages listed above from the command-line makes the command-line work again. Once that command (or a variant with a newer version of bob-devel) works, the problem is fixed and a patch is no longer required.André AnjosAndré Anjoshttps://gitlab.idiap.ch/bob/bob.devtools/-/issues/69Pin of `smmap<4` is undesirable2021-04-10T11:28:22ZAndré AnjosPin of `smmap<4` is undesirableThis pin was put in place to fix a dependency issue with package `gitdb`, which we don't provide, but depend on.
This can be undone when this (https://github.com/ContinuumIO/anaconda-issues/issues/12255) is fixed.
To undo this work, ju...This pin was put in place to fix a dependency issue with package `gitdb`, which we don't provide, but depend on.
This can be undone when this (https://github.com/ContinuumIO/anaconda-issues/issues/12255) is fixed.
To undo this work, just revert !205.André AnjosAndré Anjoshttps://gitlab.idiap.ch/bob/nightlies/-/issues/59Nightlies MacOS SegFault2021-01-22T07:05:43ZTiago de Freitas PereiraNightlies MacOS SegFaultWith this MR https://gitlab.idiap.ch/bob/bob.devtools/-/merge_requests/203 the Seg.fault was solved for individual packages.
However, the problem still remains with nightly builds.
https://gitlab.idiap.ch/bob/nightlies/-/jobs/221664
Lo...With this MR https://gitlab.idiap.ch/bob/bob.devtools/-/merge_requests/203 the Seg.fault was solved for individual packages.
However, the problem still remains with nightly builds.
https://gitlab.idiap.ch/bob/nightlies/-/jobs/221664
Looking at the logs there are still some references pointing to 10.9 `sdk`.
```
creating build/temp.macosx-10.9-x86_64-3.7/bob/blitz
x86_64-apple-darwin13.4.0-clang -fno-strict-aliasing -Wsign-compare -Wunreachable-code -DNDEBUG -fwrapv -O3 -Wall -march=core2 -mtune=haswell -mssse3 -ftree-vectorize -fPIC -fPIE -fstack-protector-strong -O3 -pipe -fdebug-prefix-map=${SRC_DIR}=/usr/local/src/conda/${PKG_NAME}-${PKG_VERSION} -fdebug-prefix-map=$PREFIX=/usr/local/src/conda-prefix -flto -Wl,-export_dynamic -march=core2 -mtune=haswell -mssse3 -ftree-vectorize -fPIC -fPIE -fstack-protector-strong -O3 -march=core2 -mtune=haswell -mssse3 -ftree-vectorize -fPIC -fPIE -fstack-protector-strong -O2 -pipe -isystem $PREFIX/include -fdebug-prefix-map=$SRC_DIR=/usr/local/src/conda/bob.blitz-2.0.23b0 -fdebug-prefix-map=$PREFIX=/usr/local/src/conda-prefix -D_FORTIFY_SOURCE=2 -mmacosx-version-min=10.9 -isystem $PREFIX/include -Wno-strict-aliasing -DBOB_EXT_MODULE_PREFIX="bob.blitz" -DBOB_EXT_MODULE_NAME="version" -DBOB_EXT_ENTRY_NAME=PyInit_version -DBOB_EXT_MODULE_VERSION="2.0.23b0" -DHAVE_BOOST=1 -DHAVE_BLITZ=1 -DPY_ARRAY_UNIQUE_SYMBOL=BOB_BLITZ_NUMPY_C_API -DNO_IMPORT_ARRAY=1 -DNPY_NO_DEPRECATED_API=NPY_1_7_API_VERSION -I/Users/gitlab/builds/b6d3167a/0/bob/nightlies/src/bob/bob.blitz/bob/blitz/include -I$PREFIX/lib/python3.7/site-packages/bob/extension/include -I$PREFIX/include/python3.7m -c bob/blitz/version.cpp -o build/temp.macosx-10.9-x86_64-3.7/bob/blitz/version.o -mmacosx-version-min=10.10 -isysroot /opt/MacOSX10.10.sdk -march=core2 -mtune=haswell -mssse3 -ftree-vectorize -fPIC -fPIE -fstack-protector-strong -O2 -pipe -stdlib=libc++ -fvisibility-inlines-hidden -std=c++14 -fmessage-length=0 -fdebug-prefix-map=$SRC_DIR=/usr/local/src/conda/bob.blitz-2.0.23b0 -fdebug-prefix-map=$PREFIX=/usr/local/src/conda-prefix -Wno-#warnings -pthread -isystem $PREFIX/lib/python3.7/site-packages/numpy/core/include -isystem $PREFIX/include
```
or
```
+CPPFLAGS=-D_FORTIFY_SOURCE=2 -mmacosx-version-min=10.9 -isystem $PREFIX/include
```
I don't know if these lines have a major impact. However, I don't know where the 10.9 come from.https://gitlab.idiap.ch/bob/bob.devtools/-/issues/68CI is not working2021-01-19T10:54:42ZTiago de Freitas PereiraCI is not workingFrom today, builds are not working.
https://gitlab.idiap.ch/bob/bob.buildout/-/jobs/221383
What happened with `conda-build`?
Thanks
```
------------------------------------------------------------------------------------------------...From today, builds are not working.
https://gitlab.idiap.ch/bob/bob.buildout/-/jobs/221383
What happened with `conda-build`?
Thanks
```
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
TOTAL 862 649 25%
Coverage HTML written to dir /scratch/builds/bob/bob.buildout/conda/../sphinx/coverage
Coverage XML written to file /scratch/builds/bob/bob.buildout/conda/../coverage.xml
============================== 8 passed in 0.90s ===============================
+ conda inspect linkages -p /scratch/builds/bob/bob.buildout/miniconda/conda-bld/bob.buildout_1610543493742/_test_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_pla bob.buildout
Traceback (most recent call last):
File "/scratch/builds/bob/bob.buildout/miniconda/bin/conda-inspect", line 7, in <module>
from conda_build.cli.main_inspect import main
ModuleNotFoundError: No module named 'conda_build'
Tests failed for bob.buildout-2.2.6b0-py37ha12b548_43.conda - moving package to /scratch/builds/bob/bob.buildout/miniconda/conda-bld/broken
TESTS FAILED: bob.buildout-2.2.6b0-py37ha12b548_43.conda
Uploading artifacts for failed job
00:01
Uploading artifacts...
coverage.xml: found 1 matching files and directories
Uploading artifacts as "cobertura" to coordinator... ok id=221383 responseStatus=201 Created token=cHw11iVi
Cleaning up file based variables
00:02
ERROR: Job failed: exit code 1
```https://gitlab.idiap.ch/bob/bob.devtools/-/issues/67Moving from macOS 10.13 to a newer version2021-01-05T14:37:42ZAndré AnjosMoving from macOS 10.13 to a newer versionWhile trying to upgrade some packages on the mac ci (black tower), I got this message today:
```
Warning: You are using macOS 10.13.
We (and Apple) do not provide support for this old version.
You will encounter build failures with some...While trying to upgrade some packages on the mac ci (black tower), I got this message today:
```
Warning: You are using macOS 10.13.
We (and Apple) do not provide support for this old version.
You will encounter build failures with some formulae.
Please create pull requests instead of asking for help on Homebrew's GitHub,
Twitter or any other official channels. You are responsible for resolving
any issues you experience while you are running this
old version.
```
We need to consider an OS upgrade for both machines. This should be OK as we will still be able to compile for an older version of macOS as we currently do.
I propose we bump the OS *directly* to version 10.15 (Catalina).André AnjosAndré Anjoshttps://gitlab.idiap.ch/bob/bob.devtools/-/issues/66Location of miniconda install script2021-01-08T14:37:57ZVincent POLLETLocation of miniconda install scriptI am getting a 302 error when running [bootstrap.py](https://gitlab.idiap.ch/bob/bob.devtools/-/blob/master/bob/devtools/bootstrap.py), in the [request](https://gitlab.idiap.ch/bob/bob.devtools/-/blob/master/bob/devtools/bootstrap.py#L24...I am getting a 302 error when running [bootstrap.py](https://gitlab.idiap.ch/bob/bob.devtools/-/blob/master/bob/devtools/bootstrap.py), in the [request](https://gitlab.idiap.ch/bob/bob.devtools/-/blob/master/bob/devtools/bootstrap.py#L241) for the miniconda install script.
The url of the request is `http://www.idiap.ch/miniconda/Miniconda3-py37_4.8.2-Linux-x86_64.sh` and the url of the re-direction is the same, but https instead of http. However, I get a 404 at the https url. Is the ressource missing or am I doing something wrong ?
For context, I am trying to find out why the [build of the opencv package in bob/conda](https://gitlab.idiap.ch/bob/conda/-/jobs/220377) is failing in the CI, but working fine locally. So I am trying to run the build steps of [base-build.yaml](https://gitlab.idiap.ch/bob/bob.devtools/-/blob/master/bob/devtools/data/gitlab-ci/base-build.yaml) in a docker with the c3i-linux-64 image.https://gitlab.idiap.ch/bob/bob.bio.face/-/issues/39[LGBPHS] wrong tempfiles path when running on the grid2020-12-22T17:20:39ZLaurent COLBOIS[LGBPHS] wrong tempfiles path when running on the gridHi,
I have an issue when running the LGBPHS baseline, e.g.
```bob bio vanilla-biometrics pipeline mobio-male lgbphs -vv -l sge```
where it fails with the following traceback :
<details><summary> Click to see traceback </summary>
```
...Hi,
I have an issue when running the LGBPHS baseline, e.g.
```bob bio vanilla-biometrics pipeline mobio-male lgbphs -vv -l sge```
where it fails with the following traceback :
<details><summary> Click to see traceback </summary>
```
Traceback (most recent call last):
File "./bin/bob", line 47, in <module>
sys.exit(bob.extension.scripts.main_cli())
File "/idiap/temp/lcolbois/miniconda3/envs/bob_tf2/lib/python3.7/site-packages/click/core.py", line 829, in __call__
return self.main(*args, **kwargs)
File "/idiap/temp/lcolbois/miniconda3/envs/bob_tf2/lib/python3.7/site-packages/click/core.py", line 782, in main
rv = self.invoke(ctx)
File "/idiap/temp/lcolbois/miniconda3/envs/bob_tf2/lib/python3.7/site-packages/click/core.py", line 1259, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
File "/idiap/temp/lcolbois/miniconda3/envs/bob_tf2/lib/python3.7/site-packages/click/core.py", line 1259, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
File "/idiap/temp/lcolbois/miniconda3/envs/bob_tf2/lib/python3.7/site-packages/click/core.py", line 1259, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
File "/idiap/temp/lcolbois/miniconda3/envs/bob_tf2/lib/python3.7/site-packages/click/core.py", line 1066, in invoke
return ctx.invoke(self.callback, **ctx.params)
File "/idiap/temp/lcolbois/miniconda3/envs/bob_tf2/lib/python3.7/site-packages/click/core.py", line 610, in invoke
return callback(*args, **kwargs)
File "/remote/idiap.svm/temp.biometric03/lcolbois/bob.bio.face/src/bob.bio.base/bob/bio/base/script/vanilla_biometrics.py", line 215, in vanilla_biometrics
**kwargs,
File "/remote/idiap.svm/temp.biometric03/lcolbois/bob.bio.face/src/bob.bio.base/bob/bio/base/pipelines/vanilla_biometrics/vanilla_biometrics.py", line 143, in execute_vanilla_biometrics
_ = compute_scores(post_processed_scores, dask_client)
File "/remote/idiap.svm/temp.biometric03/lcolbois/bob.bio.face/src/bob.bio.base/bob/bio/base/pipelines/vanilla_biometrics/vanilla_biometrics.py", line 23, in compute_scores
result = result.compute(scheduler=dask_client)
File "/remote/idiap.svm/temp.biometric03/lcolbois/bob.bio.face/eggs/dask-2.30.0-py3.7.egg/dask/base.py", line 167, in compute
(result,) = compute(self, traverse=False, **kwargs)
File "/remote/idiap.svm/temp.biometric03/lcolbois/bob.bio.face/eggs/dask-2.30.0-py3.7.egg/dask/base.py", line 452, in compute
results = schedule(dsk, keys, **kwargs)
File "/remote/idiap.svm/temp.biometric03/lcolbois/bob.bio.face/eggs/distributed-2.30.1-py3.7.egg/distributed/client.py", line 2725, in get
results = self.gather(packed, asynchronous=asynchronous, direct=direct)
File "/remote/idiap.svm/temp.biometric03/lcolbois/bob.bio.face/eggs/distributed-2.30.1-py3.7.egg/distributed/client.py", line 1992, in gather
asynchronous=asynchronous,
File "/remote/idiap.svm/temp.biometric03/lcolbois/bob.bio.face/eggs/distributed-2.30.1-py3.7.egg/distributed/client.py", line 833, in sync
self.loop, func, *args, callback_timeout=callback_timeout, **kwargs
File "/remote/idiap.svm/temp.biometric03/lcolbois/bob.bio.face/eggs/distributed-2.30.1-py3.7.egg/distributed/utils.py", line 340, in sync
raise exc.with_traceback(tb)
File "/remote/idiap.svm/temp.biometric03/lcolbois/bob.bio.face/eggs/distributed-2.30.1-py3.7.egg/distributed/utils.py", line 324, in f
result[0] = yield future
File "/idiap/temp/lcolbois/miniconda3/envs/bob_tf2/lib/python3.7/site-packages/tornado/gen.py", line 735, in run
value = future.result()
File "/remote/idiap.svm/temp.biometric03/lcolbois/bob.bio.face/eggs/distributed-2.30.1-py3.7.egg/distributed/client.py", line 1851, in _gather
raise exception.with_traceback(traceback)
File "/remote/idiap.svm/temp.biometric03/lcolbois/bob.bio.face/src/bob.bio.base/bob/bio/base/pipelines/vanilla_biometrics/pipelines.py", line 175, in write_scores
return self.score_writer.write(scores)
File "/remote/idiap.svm/temp.biometric03/lcolbois/bob.bio.face/src/bob.bio.base/bob/bio/base/pipelines/vanilla_biometrics/score_writers.py", line 56, in write
return _write(probe_sampleset)
File "/remote/idiap.svm/temp.biometric03/lcolbois/bob.bio.face/src/bob.bio.base/bob/bio/base/pipelines/vanilla_biometrics/score_writers.py", line 35, in _write
if isinstance(probe[0], DelayedSample):
File "/remote/idiap.svm/temp.biometric03/lcolbois/bob.bio.face/src/bob.pipelines/bob/pipelines/sample.py", line 165, in __getitem__
return self.samples.__getitem__(item)
File "/remote/idiap.svm/temp.biometric03/lcolbois/bob.bio.face/src/bob.pipelines/bob/pipelines/sample.py", line 187, in samples
return self._load()
File "/remote/idiap.svm/temp.biometric03/lcolbois/bob.bio.face/src/bob.bio.base/bob/bio/base/pipelines/vanilla_biometrics/legacy.py", line 364, in _load
return joblib.load("/tmp/" + path)
File "/remote/idiap.svm/temp.biometric03/lcolbois/bob.bio.face/eggs/joblib-0.17.0-py3.7.egg/joblib/numpy_pickle.py", line 577, in load
with open(filename, 'rb') as f:
FileNotFoundError: [Errno 2] No such file or directory: '/tmp//tmp/tmp1dt8ulg0/scores/uman/m103/02_mobile/m103_02_f12_i0_0uman/m103/01_mobile/m103_01_p01_i0_0_uman/m104/01_mobile/m104_01_p01_i0_0_uman/m106/01_mobile/m106_01_p01_i0_0.joblib'
```
</details>
Looks like there is an error when computing the path of some temporary files. Note that the issue:
+ Is specific to LGBPHS (Gabor graph for example works flawlessly)
+ Does not happen when running in local
+ Does not happen when using checkpointing (`-c`)
I am unsure how to start tracking down the root cause.
ping @tiago.pereira @ydayerhttps://gitlab.idiap.ch/bob/bob.bio.base/-/issues/151verify.py --create-configuration-file crashes for local file2021-05-19T17:10:10ZManuel Günthersiebenkopf@googlemail.comverify.py --create-configuration-file crashes for local fileWhen running
```
verify.py --create-configuration-file config.py
```
this crashes with the error:
```
File "miniconda/envs/bob/bin/verify.py", line 11, in <module>
sys.exit(main())
File "miniconda/envs/bob/lib/python3.7/site-p...When running
```
verify.py --create-configuration-file config.py
```
this crashes with the error:
```
File "miniconda/envs/bob/bin/verify.py", line 11, in <module>
sys.exit(main())
File "miniconda/envs/bob/lib/python3.7/site-packages/bob/bio/base/script/verify.py", line 432, in main
args = parse_arguments(command_line_parameters)
File "miniconda/envs/bob/lib/python3.7/site-packages/bob/bio/base/script/verify.py", line 34, in parse_arguments
skips = ['preprocessing', 'extractor-training', 'extraction', 'projector-training', 'projection', 'enroller-training', 'enrollment', 'score-computation', 'concatenation', 'calibration'])
File "miniconda/envs/bob/lib/python3.7/site-packages/bob/bio/base/tools/command_line.py", line 425, in initialize
args = parse_config_file(parsers, args, args_dictionary, keywords, skips)
File "miniconda/envs/bob/lib/python3.7/site-packages/bob/bio/base/tools/command_line.py", line 284, in parse_config_file
create_configuration_file(parsers, args)
File "miniconda/envs/bob/lib/python3.7/site-packages/bob/bio/base/tools/command_line.py", line 578, in create_configuration_file
bob.io.base.create_directories_safe(os.path.dirname(args.create_configuration_file))
File "miniconda/envs/bob/lib/python3.7/site-packages/numpy/lib/utils.py", line 100, in newfunc
return func(*args, **kwds)
File "miniconda/envs/bob/lib/python3.7/site-packages/bob/io/base/__init__.py", line 104, in create_directories_safe
os.makedirs(directory, exist_ok=True)
File "miniconda/envs/bob/lib/python3.7/os.py", line 223, in makedirs
mkdir(name, mode)
FileNotFoundError: [Errno 2] No such file or directory: ''
```
The issue is that `bob.io.base.create_directories_safe(os.path.dirname(args.create_configuration_file))` is called without checking whether `os.path.dirname(args.create_configuration_file)` isn't empty.
There are two solutions to this issue:
1. We add this check here.
2. We correct this in `bob.io.base.create_directories_safe` and just skip empty strings.
Which option would you prefer?https://gitlab.idiap.ch/bob/bob.devtools/-/issues/65Switch to pytest in Bob echosystem2021-09-09T07:08:06ZAmir MOHAMMADISwitch to pytest in Bob echosystem* [ ] Use pytest in all conda recipes and add it as a test requirement
* [x] Install pytest by default when invoking `bdt create`* [ ] Use pytest in all conda recipes and add it as a test requirement
* [x] Install pytest by default when invoking `bdt create`https://gitlab.idiap.ch/bob/docs/-/issues/10Installation default instructions2023-03-15T19:47:51ZTiago de Freitas PereiraInstallation default instructionsWe need to discuss how's going to be the default installation 'modus-operandi' for individual packages.
We were discussing to make the default installation via `buildout`, something along these lines:
```shell
$ git clone https://gitla...We need to discuss how's going to be the default installation 'modus-operandi' for individual packages.
We were discussing to make the default installation via `buildout`, something along these lines:
```shell
$ git clone https://gitlab.idiap.ch/bob/[MY-PACKAGE]
$ cd [MY-PACKAGE]
$ bdt create -vv [MY-PACKAGE] .
$ conda activate [MY-PACKAGE]
$ buildout
$ echo "HAVE FUN"
```
What do you think? ping @andre.anjos @amohammadi @ydayer @lcolboishttps://gitlab.idiap.ch/bob/bob.devtools/-/issues/64Use pytorch model-zoo style file uploads for `bdt dav upload`2021-03-23T14:45:30ZAndré AnjosUse pytorch model-zoo style file uploads for `bdt dav upload`As discussed during the Bob meeting yesterday afternoon, it would be nice to have an option in the `upload` command for `bdt dav` that would handle filename hashing automatically, à là pytorch's model zoo implementation (https://pytorch....As discussed during the Bob meeting yesterday afternoon, it would be nice to have an option in the `upload` command for `bdt dav` that would handle filename hashing automatically, à là pytorch's model zoo implementation (https://pytorch.org/docs/stable/model_zoo.html). This procedure would have to take a file and ensure it is uploaded to the destination URL with a slightly modified name:
```
if name is file.ext and url is http://example.com/dir/
file is uploaded as http://example.com/dir/file-deadbeef.ext
where `deadbeaf` is the first 8 characters of the original file's sha256 sum.
```
Similarly, an option in bob/bob.extension's `get_data` should be able to handle automatic hash checking, if the user specifies the said option, or automatically, based on the filename (e.g. via regular expression matching).
This mechanism provides a way to handle file versions and automatic checking for the completeness of existing cached downloads.Amir MOHAMMADIAmir MOHAMMADIhttps://gitlab.idiap.ch/bob/bob.db.siw/-/issues/2Is this a candidate for the new DB interface?2020-12-12T10:20:48ZTiago de Freitas PereiraIs this a candidate for the new DB interface?ping @amohammadi @ydayerping @amohammadi @ydayerhttps://gitlab.idiap.ch/bob/bob.pad.base/-/issues/35Follow-up from "Dask pipelines Improvements"2020-12-09T10:24:37ZTiago de Freitas PereiraFollow-up from "Dask pipelines Improvements"The following discussion from !78 should be addressed:
- [ ] @tiago.pereira started a [discussion](https://gitlab.idiap.ch/bob/bob.pad.base/-/merge_requests/78#note_59143):
> Hi,
>
> Would be nice to have this functionali...The following discussion from !78 should be addressed:
- [ ] @tiago.pereira started a [discussion](https://gitlab.idiap.ch/bob/bob.pad.base/-/merge_requests/78#note_59143):
> Hi,
>
> Would be nice to have this functionality on `bob.pipelines`
Would be nice to have a functionality that saves the pipeline steps in a `.txt` file for the record.https://gitlab.idiap.ch/bob/bob.bio.face/-/issues/38Follow-up from "Sample Loaders able to handle certain type of annotations..."2020-12-15T17:44:30ZTiago de Freitas PereiraFollow-up from "Sample Loaders able to handle certain type of annotations..."The following discussion from !81 should be addressed:
- [ ] @amohammadi started a [discussion](https://gitlab.idiap.ch/bob/bob.bio.face/-/merge_requests/81#note_59087):
> you can remove this now.
I need to do some minor clean-up...The following discussion from !81 should be addressed:
- [ ] @amohammadi started a [discussion](https://gitlab.idiap.ch/bob/bob.bio.face/-/merge_requests/81#note_59087):
> you can remove this now.
I need to do some minor clean-up on MEDS dataset.Tiago de Freitas PereiraTiago de Freitas Pereirahttps://gitlab.idiap.ch/bob/bob.bio.face/-/issues/37Follow-up from "Sample Loaders able to handle certain type of annotations..."2020-12-05T20:18:47ZTiago de Freitas PereiraFollow-up from "Sample Loaders able to handle certain type of annotations..."The following discussion from !81 should be addressed:
- [ ] @amohammadi started a [discussion](https://gitlab.idiap.ch/bob/bob.bio.face/-/merge_requests/81#note_59086):
> I suggest creating a base class for this or some kind of d...The following discussion from !81 should be addressed:
- [ ] @amohammadi started a [discussion](https://gitlab.idiap.ch/bob/bob.bio.face/-/merge_requests/81#note_59086):
> I suggest creating a base class for this or some kind of documentation or tests to make sure all face dbs have these attributes.Tiago de Freitas PereiraTiago de Freitas Pereirahttps://gitlab.idiap.ch/bob/bob.devtools/-/issues/63Add pre-commit checks to the CI2021-10-01T13:45:46ZAmir MOHAMMADIAdd pre-commit checks to the CISome packages are starting to ship a `.pre-commit-config.yaml` file. It would be a good idea to check for this file and run the hooks automatically in the CI.Some packages are starting to ship a `.pre-commit-config.yaml` file. It would be a good idea to check for this file and run the hooks automatically in the CI.https://gitlab.idiap.ch/bob/bob.devtools/-/issues/62Replace use of gitlab-ci skip with git push option2021-10-06T08:20:35ZSamuel GAISTReplace use of gitlab-ci skip with git push optionWhile on the hunt for GitLab token related information I stumbled across https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/15643 which provides a way to avoid "polluting" commit messages with skip-ci tags using `git push -o ci.s...While on the hunt for GitLab token related information I stumbled across https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/15643 which provides a way to avoid "polluting" commit messages with skip-ci tags using `git push -o ci.skip` in place.
Might be of interest for the automatic new version update workflow in the BOB/BEAT packages.https://gitlab.idiap.ch/bob/bob.pipelines/-/issues/25Better handling of file structures with CheckpointWrapper2021-08-13T11:13:09ZTiago de Freitas PereiraBetter handling of file structures with CheckpointWrapperSome databases have file structures very flat (with more than 30k files in a directory).
This is not good for the Idiap file structure and can let our I/O super slow.
We should implement a hash function in `CheckpointWrapper.make_path` ...Some databases have file structures very flat (with more than 30k files in a directory).
This is not good for the Idiap file structure and can let our I/O super slow.
We should implement a hash function in `CheckpointWrapper.make_path` that generates directory names given `sample.key` to limit the number of files in a directory to 1000 files.
ping @lcolbois (this touches experiments with IJB-C)https://gitlab.idiap.ch/bob/bob.bio.vein/-/issues/24MaximumCurvature Config file2020-12-03T08:36:47ZHatef OTROSHIMaximumCurvature Config fileI was looking at the MaximumCurvature config file and I noticed that at
[#L41](https://gitlab.idiap.ch/bob/bob.bio.vein/-/blob/master/bob/bio/vein/config/maximum_curvature.py#L41) the subdirectory is defined `rlt`. I think it should be...I was looking at the MaximumCurvature config file and I noticed that at
[#L41](https://gitlab.idiap.ch/bob/bob.bio.vein/-/blob/master/bob/bio/vein/config/maximum_curvature.py#L41) the subdirectory is defined `rlt`. I think it should be `mc`, because it is for Maximum Curvature (MC) method.https://gitlab.idiap.ch/bob/bob.ip.optflow.liu/-/issues/2DEPRECATION2020-11-06T15:35:00ZTiago de Freitas PereiraDEPRECATIONThis package will go away too
ping @ydayer @amohammadiThis package will go away too
ping @ydayer @amohammadi