libdigidoc, libdigidocpp, qdigidoc updates

Alternative to https://github.com/NixOS/nixpkgs/pull/42321. cc @jagajaga @Mic92

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: libdigidoc, libdigidocpp, qdigidoc
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Failure on aarch64-linux (full log)
Attempted: libdigidoc, libdigidocpp, qdigidoc
Partial log (click to expand)
    Ignored 15 untranslated source text(s)
[ 78%] Generating qrc_tr.cpp
[ 79%] Generating qrc_TSL.cpp
RCC: Error in '/build/qdigidoc/build/client/TSL.qrc': Cannot find file 'EE.xml'
make[2]: *** [client/CMakeFiles/qdigidocclient.dir/build.make:87: client/qrc_TSL.cpp] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [CMakeFiles/Makefile2:468: client/CMakeFiles/qdigidocclient.dir/all] Error 2
make: *** [Makefile:130: all] Error 2
builder for '/nix/store/g51din4c9qs8hwqalacm44js65vg0wx8-qdigidoc-3.13.6.drv' failed with exit code 2
error: build of '/nix/store/g51din4c9qs8hwqalacm44js65vg0wx8-qdigidoc-3.13.6.drv' failed

Failure on x86_64-linux (full log)
Attempted: libdigidoc, libdigidocpp, qdigidoc
Partial log (click to expand)
    Ignored 22 untranslated source text(s)
[ 72%] Generating qrc_images.cpp
[ 73%] Generating qrc_tr.cpp
[ 75%] Generating qrc_TSL.cpp
RCC: Error in '/build/qdigidoc/build/client/TSL.qrc': Cannot find file 'EE.xml'
make[2]: *** [client/CMakeFiles/qdigidocclient.dir/build.make:87: client/qrc_TSL.cpp] Error 1
make[1]: *** [CMakeFiles/Makefile2:468: client/CMakeFiles/qdigidocclient.dir/all] Error 2
make: *** [Makefile:130: all] Error 2
builder for '/nix/store/phnqjkz66s6ki33zrhfsxwazxni8fpfj-qdigidoc-3.13.6.drv' failed with exit code 2
error: build of '/nix/store/phnqjkz66s6ki33zrhfsxwazxni8fpfj-qdigidoc-3.13.6.drv' failed

Looks good, compilation error should be fixed though.

@GrahamcOfBorg build qdigidoc

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: qdigidoc
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Failure on x86_64-linux (full log)
Attempted: qdigidoc
Partial log (click to expand)
[ 77%] Generating ui_SettingsDialog.h
[ 77%] Generating ui_SignatureDialog.h
[ 78%] Generating qrc_tr.cpp
[ 79%] Generating qrc_TSL.cpp
RCC: Error in '/build/qdigidoc/build/client/TSL.qrc': Cannot find file 'EE.xml'
make[2]: *** [client/CMakeFiles/qdigidocclient.dir/build.make:87: client/qrc_TSL.cpp] Error 1
make[1]: *** [CMakeFiles/Makefile2:468: client/CMakeFiles/qdigidocclient.dir/all] Error 2
make: *** [Makefile:130: all] Error 2
builder for '/nix/store/lkq2qq4qj255iv6clkn9xablaxjyfbj5-qdigidoc-3.13.6.drv' failed with exit code 2
error: build of '/nix/store/lkq2qq4qj255iv6clkn9xablaxjyfbj5-qdigidoc-3.13.6.drv' failed

Failure on aarch64-linux (full log)
Attempted: qdigidoc
Partial log (click to expand)
    Ignored 22 untranslated source text(s)
[ 78%] Generating qrc_tr.cpp
[ 79%] Generating qrc_TSL.cpp
RCC: Error in '/build/qdigidoc/build/client/TSL.qrc': Cannot find file 'EE.xml'
make[2]: *** [client/CMakeFiles/qdigidocclient.dir/build.make:87: client/qrc_TSL.cpp] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [CMakeFiles/Makefile2:468: client/CMakeFiles/qdigidocclient.dir/all] Error 2
make: *** [Makefile:130: all] Error 2
builder for '/nix/store/6v624ahcwqdrmk510bwfzss9z1xwp6j0-qdigidoc-3.13.6.drv' failed with exit code 2
error: build of '/nix/store/6v624ahcwqdrmk510bwfzss9z1xwp6j0-qdigidoc-3.13.6.drv' failed

@GrahamcOfBorg build qdigidoc

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: qdigidoc
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Failure on x86_64-linux (full log)
Attempted: qdigidoc
Partial log (click to expand)
[ 77%] Generating ui_SignatureDialog.h
[ 78%] Generating qrc_tr.cpp
[ 79%] Generating qrc_TSL.cpp
RCC: Error in '/build/qdigidoc/build/client/TSL.qrc': Cannot find file 'EE.xml'
make[2]: *** [client/CMakeFiles/qdigidocclient.dir/build.make:87: client/qrc_TSL.cpp] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [CMakeFiles/Makefile2:468: client/CMakeFiles/qdigidocclient.dir/all] Error 2
make: *** [Makefile:130: all] Error 2
builder for '/nix/store/f1cxpdv2xn5q8vhp7lhrfchwsfxq1zdx-qdigidoc-3.13.6.drv' failed with exit code 2
error: build of '/nix/store/f1cxpdv2xn5q8vhp7lhrfchwsfxq1zdx-qdigidoc-3.13.6.drv' failed

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: libdigidoc, libdigidocpp, qdigidoc
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: qdigidoc
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Failure on x86_64-linux (full log)
Attempted: qdigidoc
Partial log (click to expand)
    Ignored 22 untranslated source text(s)
[ 75%] Generating ui_MainWindow.h
RCC: Error in '/build/qdigidoc/build/client/TSL.qrc': Cannot find file 'EE.xml'
make[2]: *** [client/CMakeFiles/qdigidocclient.dir/build.make:87: client/qrc_TSL.cpp] Error 1
make[2]: *** Waiting for unfinished jobs....
[ 76%] Generating ui_MobileDialog.h
make[1]: *** [CMakeFiles/Makefile2:468: client/CMakeFiles/qdigidocclient.dir/all] Error 2
make: *** [Makefile:130: all] Error 2
builder for '/nix/store/f1cxpdv2xn5q8vhp7lhrfchwsfxq1zdx-qdigidoc-3.13.6.drv' failed with exit code 2
error: build of '/nix/store/f1cxpdv2xn5q8vhp7lhrfchwsfxq1zdx-qdigidoc-3.13.6.drv' failed

Failure on aarch64-linux (full log)
Attempted: qdigidoc
Partial log (click to expand)
    Ignored 15 untranslated source text(s)
[ 78%] Generating qrc_tr.cpp
[ 79%] Generating qrc_TSL.cpp
RCC: Error in '/build/qdigidoc/build/client/TSL.qrc': Cannot find file 'EE.xml'
make[2]: *** [client/CMakeFiles/qdigidocclient.dir/build.make:87: client/qrc_TSL.cpp] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [CMakeFiles/Makefile2:468: client/CMakeFiles/qdigidocclient.dir/all] Error 2
make: *** [Makefile:130: all] Error 2
builder for '/nix/store/yh20d02ja84v48yx86g9nlwx0ji3qpmc-qdigidoc-3.13.6.drv' failed with exit code 2
error: build of '/nix/store/yh20d02ja84v48yx86g9nlwx0ji3qpmc-qdigidoc-3.13.6.drv' failed

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: qdigidoc
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Failure on aarch64-linux (full log)
Attempted: libdigidoc, libdigidocpp, qdigidoc
Partial log (click to expand)
    Ignored 1 untranslated source text(s)
[ 78%] Generating qrc_tr.cpp
[ 79%] Generating qrc_TSL.cpp
RCC: Error in '/build/qdigidoc/build/client/TSL.qrc': Cannot find file 'EE.xml'
make[2]: *** [client/CMakeFiles/qdigidocclient.dir/build.make:87: client/qrc_TSL.cpp] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [CMakeFiles/Makefile2:468: client/CMakeFiles/qdigidocclient.dir/all] Error 2
make: *** [Makefile:130: all] Error 2
builder for '/nix/store/6v624ahcwqdrmk510bwfzss9z1xwp6j0-qdigidoc-3.13.6.drv' failed with exit code 2
error: build of '/nix/store/6v624ahcwqdrmk510bwfzss9z1xwp6j0-qdigidoc-3.13.6.drv' failed

Failure on x86_64-linux (full log)
Attempted: libdigidoc, libdigidocpp, qdigidoc
Partial log (click to expand)
    Ignored 22 untranslated source text(s)
[ 72%] Generating qrc_images.cpp
[ 73%] Generating qrc_TSL.cpp
RCC: Error in '/tmp/nix-build-qdigidoc-3.13.6.drv-0/qdigidoc/build/client/TSL.qrc': Cannot find file 'EE.xml'
make[2]: *** [client/CMakeFiles/qdigidocclient.dir/build.make:87: client/qrc_TSL.cpp] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [CMakeFiles/Makefile2:468: client/CMakeFiles/qdigidocclient.dir/all] Error 2
make: *** [Makefile:130: all] Error 2
builder for ‘/nix/store/iridivhnagxmxmrg8s7zy9xxg4qf3sa0-qdigidoc-3.13.6.drv’ failed with exit code 2
error: build of ‘/nix/store/iridivhnagxmxmrg8s7zy9xxg4qf3sa0-qdigidoc-3.13.6.drv’ failed

Failure on x86_64-linux (full log)
Attempted: qdigidoc
Partial log (click to expand)
[ 78%] Generating qrc_tr.cpp
[ 78%] Generating ui_SignatureDialog.h
[ 79%] Generating qrc_TSL.cpp
RCC: Error in '/build/qdigidoc/build/client/TSL.qrc': Cannot find file 'EE.xml'
make[2]: *** [client/CMakeFiles/qdigidocclient.dir/build.make:87: client/qrc_TSL.cpp] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [CMakeFiles/Makefile2:468: client/CMakeFiles/qdigidocclient.dir/all] Error 2
make: *** [Makefile:130: all] Error 2
builder for '/nix/store/f1cxpdv2xn5q8vhp7lhrfchwsfxq1zdx-qdigidoc-3.13.6.drv' failed with exit code 2
error: build of '/nix/store/f1cxpdv2xn5q8vhp7lhrfchwsfxq1zdx-qdigidoc-3.13.6.drv' failed

Failure on aarch64-linux (full log)
Attempted: qdigidoc
Partial log (click to expand)
    Ignored 22 untranslated source text(s)
[ 78%] Generating qrc_tr.cpp
[ 79%] Generating qrc_TSL.cpp
RCC: Error in '/build/qdigidoc/build/client/TSL.qrc': Cannot find file 'EE.xml'
make[2]: *** [client/CMakeFiles/qdigidocclient.dir/build.make:87: client/qrc_TSL.cpp] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [CMakeFiles/Makefile2:468: client/CMakeFiles/qdigidocclient.dir/all] Error 2
make: *** [Makefile:130: all] Error 2
builder for '/nix/store/yh20d02ja84v48yx86g9nlwx0ji3qpmc-qdigidoc-3.13.6.drv' failed with exit code 2
error: build of '/nix/store/yh20d02ja84v48yx86g9nlwx0ji3qpmc-qdigidoc-3.13.6.drv' failed

Failure on aarch64-linux (full log)
Attempted: qdigidoc
Partial log (click to expand)
    Ignored 22 untranslated source text(s)
[ 78%] Generating qrc_tr.cpp
[ 79%] Generating qrc_TSL.cpp
RCC: Error in '/build/qdigidoc/build/client/TSL.qrc': Cannot find file 'EE.xml'
make[2]: *** [client/CMakeFiles/qdigidocclient.dir/build.make:87: client/qrc_TSL.cpp] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [CMakeFiles/Makefile2:468: client/CMakeFiles/qdigidocclient.dir/all] Error 2
make: *** [Makefile:130: all] Error 2
builder for '/nix/store/yh20d02ja84v48yx86g9nlwx0ji3qpmc-qdigidoc-3.13.6.drv' failed with exit code 2
error: build of '/nix/store/yh20d02ja84v48yx86g9nlwx0ji3qpmc-qdigidoc-3.13.6.drv' failed

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: libdigidoc, libdigidocpp, qdigidoc
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Failure on x86_64-linux (full log)
Attempted: libdigidoc, libdigidocpp, qdigidoc
Partial log (click to expand)
[ 78%] Generating qrc_tr.cpp
[ 78%] Generating ui_SignatureDialog.h
[ 79%] Generating qrc_TSL.cpp
RCC: Error in '/build/qdigidoc/build/client/TSL.qrc': Cannot find file 'EE.xml'
make[2]: *** [client/CMakeFiles/qdigidocclient.dir/build.make:87: client/qrc_TSL.cpp] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [CMakeFiles/Makefile2:468: client/CMakeFiles/qdigidocclient.dir/all] Error 2
make: *** [Makefile:130: all] Error 2
builder for '/nix/store/f1cxpdv2xn5q8vhp7lhrfchwsfxq1zdx-qdigidoc-3.13.6.drv' failed with exit code 2
error: build of '/nix/store/f1cxpdv2xn5q8vhp7lhrfchwsfxq1zdx-qdigidoc-3.13.6.drv' failed

Failure on aarch64-linux (full log)
Attempted: libdigidoc, libdigidocpp, qdigidoc
Partial log (click to expand)
    Ignored 15 untranslated source text(s)
[ 78%] Generating qrc_tr.cpp
[ 79%] Generating qrc_TSL.cpp
RCC: Error in '/build/qdigidoc/build/client/TSL.qrc': Cannot find file 'EE.xml'
make[2]: *** [client/CMakeFiles/qdigidocclient.dir/build.make:87: client/qrc_TSL.cpp] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [CMakeFiles/Makefile2:468: client/CMakeFiles/qdigidocclient.dir/all] Error 2
make: *** [Makefile:130: all] Error 2
builder for '/nix/store/yh20d02ja84v48yx86g9nlwx0ji3qpmc-qdigidoc-3.13.6.drv' failed with exit code 2
error: build of '/nix/store/yh20d02ja84v48yx86g9nlwx0ji3qpmc-qdigidoc-3.13.6.drv' failed

@GrahamcOfBorg build qdigidoc

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: qdigidoc
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Failure on x86_64-linux (full log)
Attempted: qdigidoc
Partial log (click to expand)
[ 77%] Generating ui_SignatureDialog.h
[ 77%] Generating ui_SettingsDialog.h
[ 78%] Generating qrc_tr.cpp
[ 79%] Generating qrc_TSL.cpp
RCC: Error in '/build/qdigidoc/build/client/TSL.qrc': Cannot find file 'EE.xml'
make[2]: *** [client/CMakeFiles/qdigidocclient.dir/build.make:87: client/qrc_TSL.cpp] Error 1
make[1]: *** [CMakeFiles/Makefile2:468: client/CMakeFiles/qdigidocclient.dir/all] Error 2
make: *** [Makefile:130: all] Error 2
builder for '/nix/store/2wrqz395pyka05ijcll2jv3g32sg8x1a-qdigidoc-3.13.6.drv' failed with exit code 2
error: build of '/nix/store/2wrqz395pyka05ijcll2jv3g32sg8x1a-qdigidoc-3.13.6.drv' failed

Failure on aarch64-linux (full log)
Attempted: qdigidoc
Partial log (click to expand)
    Ignored 15 untranslated source text(s)
[ 78%] Generating qrc_TSL.cpp
[ 79%] Generating qrc_tr.cpp
RCC: Error in '/build/qdigidoc/build/client/TSL.qrc': Cannot find file 'EE.xml'
make[2]: *** [client/CMakeFiles/qdigidocclient.dir/build.make:87: client/qrc_TSL.cpp] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [CMakeFiles/Makefile2:468: client/CMakeFiles/qdigidocclient.dir/all] Error 2
make: *** [Makefile:130: all] Error 2
builder for '/nix/store/27ksjqb593r73ja1rah2y6f2fr2mh651-qdigidoc-3.13.6.drv' failed with exit code 2
error: build of '/nix/store/27ksjqb593r73ja1rah2y6f2fr2mh651-qdigidoc-3.13.6.drv' failed

@GrahamcOfBorg build qdigidoc

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: qdigidoc
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Failure on x86_64-linux (full log)
Attempted: qdigidoc
Partial log (click to expand)
[ 77%] Generating ui_SignatureDialog.h
[ 78%] Generating qrc_tr.cpp
[ 79%] Generating qrc_TSL.cpp
RCC: Error in '/build/qdigidoc/build/client/TSL.qrc': Cannot find file 'EE.xml'
make[2]: *** [client/CMakeFiles/qdigidocclient.dir/build.make:87: client/qrc_TSL.cpp] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [CMakeFiles/Makefile2:468: client/CMakeFiles/qdigidocclient.dir/all] Error 2
make: *** [Makefile:130: all] Error 2
builder for '/nix/store/0lh6qgmj8q2pmc9sxg37935yc0xbh4g0-qdigidoc-3.13.6.drv' failed with exit code 2
error: build of '/nix/store/0lh6qgmj8q2pmc9sxg37935yc0xbh4g0-qdigidoc-3.13.6.drv' failed

Failure on aarch64-linux (full log)
Attempted: qdigidoc
Partial log (click to expand)
    Ignored 22 untranslated source text(s)
[ 78%] Generating qrc_TSL.cpp
[ 79%] Generating qrc_tr.cpp
RCC: Error in '/build/qdigidoc/build/client/TSL.qrc': Cannot find file 'EE.xml'
make[2]: *** [client/CMakeFiles/qdigidocclient.dir/build.make:87: client/qrc_TSL.cpp] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [CMakeFiles/Makefile2:468: client/CMakeFiles/qdigidocclient.dir/all] Error 2
make: *** [Makefile:130: all] Error 2
builder for '/nix/store/ib57pk7jjgzpcywypvpw7y58dqr8fz7n-qdigidoc-3.13.6.drv' failed with exit code 2
error: build of '/nix/store/ib57pk7jjgzpcywypvpw7y58dqr8fz7n-qdigidoc-3.13.6.drv' failed

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: libdigidoc, libdigidocpp, qdigidoc
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Failure on x86_64-linux (full log)
Attempted: libdigidoc, libdigidocpp, qdigidoc
Partial log (click to expand)
    Ignored 22 untranslated source text(s)
[ 72%] Generating qrc_images.cpp
[ 73%] Generating qrc_tr.cpp
[ 75%] Generating qrc_TSL.cpp
RCC: Error in '/build/qdigidoc/build/client/TSL.qrc': Cannot find file 'EE.xml'
make[2]: *** [client/CMakeFiles/qdigidocclient.dir/build.make:87: client/qrc_TSL.cpp] Error 1
make[1]: *** [CMakeFiles/Makefile2:468: client/CMakeFiles/qdigidocclient.dir/all] Error 2
make: *** [Makefile:130: all] Error 2
builder for '/nix/store/0lh6qgmj8q2pmc9sxg37935yc0xbh4g0-qdigidoc-3.13.6.drv' failed with exit code 2
error: build of '/nix/store/0lh6qgmj8q2pmc9sxg37935yc0xbh4g0-qdigidoc-3.13.6.drv' failed

@GrahamcOfBorg build qdigidoc

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: libdigidoc, libdigidocpp, qdigidoc
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: qdigidoc
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Failure on x86_64-linux (full log)
Attempted: libdigidoc, libdigidocpp, qdigidoc
Partial log (click to expand)
    Ignored 15 untranslated source text(s)
[ 78%] Generating ui_SignatureDialog.h
[ 78%] Generating qrc_tr.cpp
[ 79%] Generating qrc_TSL.cpp
RCC: Error in '/build/qdigidoc/build/client/TSL.qrc': Cannot find file 'EE.xml'
make[2]: *** [client/CMakeFiles/qdigidocclient.dir/build.make:87: client/qrc_TSL.cpp] Error 1
make[1]: *** [CMakeFiles/Makefile2:468: client/CMakeFiles/qdigidocclient.dir/all] Error 2
make: *** [Makefile:130: all] Error 2
builder for '/nix/store/n56qv9z74sbrdip6rcq11qs4zzsqb2i2-qdigidoc-3.13.6.drv' failed with exit code 2
error: build of '/nix/store/n56qv9z74sbrdip6rcq11qs4zzsqb2i2-qdigidoc-3.13.6.drv' failed

Failure on x86_64-linux (full log)
Attempted: qdigidoc
Partial log (click to expand)
    Ignored 22 untranslated source text(s)
[ 72%] Generating qrc_images.cpp
[ 73%] Generating qrc_tr.cpp
[ 75%] Generating qrc_TSL.cpp
RCC: Error in '/build/qdigidoc/build/client/TSL.qrc': Cannot find file 'EE.xml'
make[2]: *** [client/CMakeFiles/qdigidocclient.dir/build.make:87: client/qrc_TSL.cpp] Error 1
make[1]: *** [CMakeFiles/Makefile2:468: client/CMakeFiles/qdigidocclient.dir/all] Error 2
make: *** [Makefile:130: all] Error 2
builder for '/nix/store/n56qv9z74sbrdip6rcq11qs4zzsqb2i2-qdigidoc-3.13.6.drv' failed with exit code 2
error: build of '/nix/store/n56qv9z74sbrdip6rcq11qs4zzsqb2i2-qdigidoc-3.13.6.drv' failed

Failure on aarch64-linux (full log)
Attempted: libdigidoc, libdigidocpp, qdigidoc
Partial log (click to expand)
    Ignored 22 untranslated source text(s)
[ 78%] Generating qrc_tr.cpp
[ 79%] Generating qrc_TSL.cpp
RCC: Error in '/build/qdigidoc/build/client/TSL.qrc': Cannot find file 'EE.xml'
make[2]: *** [client/CMakeFiles/qdigidocclient.dir/build.make:87: client/qrc_TSL.cpp] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [CMakeFiles/Makefile2:468: client/CMakeFiles/qdigidocclient.dir/all] Error 2
make: *** [Makefile:130: all] Error 2
builder for '/nix/store/8fcx9pql51kxpc16ck41y8by63rhbvk8-qdigidoc-3.13.6.drv' failed with exit code 2
error: build of '/nix/store/8fcx9pql51kxpc16ck41y8by63rhbvk8-qdigidoc-3.13.6.drv' failed

Failure on aarch64-linux (full log)
Attempted: qdigidoc
Partial log (click to expand)
    Ignored 22 untranslated source text(s)
[ 78%] Generating qrc_tr.cpp
[ 79%] Generating qrc_TSL.cpp
RCC: Error in '/build/qdigidoc/build/client/TSL.qrc': Cannot find file 'EE.xml'
make[2]: *** [client/CMakeFiles/qdigidocclient.dir/build.make:87: client/qrc_TSL.cpp] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [CMakeFiles/Makefile2:468: client/CMakeFiles/qdigidocclient.dir/all] Error 2
make: *** [Makefile:130: all] Error 2
builder for '/nix/store/8fcx9pql51kxpc16ck41y8by63rhbvk8-qdigidoc-3.13.6.drv' failed with exit code 2
error: build of '/nix/store/8fcx9pql51kxpc16ck41y8by63rhbvk8-qdigidoc-3.13.6.drv' failed

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: libdigidoc, libdigidocpp, qdigidoc
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Success on aarch64-linux (full log)
Attempted: libdigidoc, libdigidocpp, qdigidoc
Partial log (click to expand)
shrinking /nix/store/9nqsa9b6zsdh02385f8nxkl96v3a1pj7-qdigidoc-3.13.6/bin/.qdigidocclient-wrapped
gzipping man pages under /nix/store/9nqsa9b6zsdh02385f8nxkl96v3a1pj7-qdigidoc-3.13.6/share/man/
strip is /nix/store/ah0va6j4cnwj9nx4j6rwcfc8nh785jwm-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/9nqsa9b6zsdh02385f8nxkl96v3a1pj7-qdigidoc-3.13.6/bin
patching script interpreter paths in /nix/store/9nqsa9b6zsdh02385f8nxkl96v3a1pj7-qdigidoc-3.13.6
checking for references to /build in /nix/store/9nqsa9b6zsdh02385f8nxkl96v3a1pj7-qdigidoc-3.13.6...
postPatchMkspecs
/nix/store/h10bynjxzjhab4z8dzh4pfz3cpdryk4h-libdigidoc-3.10.4
/nix/store/a8hlk4rn4cnlnr5rnvf8jk4nwfdia7k6-libdigidocpp-3.13.6
/nix/store/9nqsa9b6zsdh02385f8nxkl96v3a1pj7-qdigidoc-3.13.6

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: libdigidoc, libdigidocpp, qdigidoc
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Success on aarch64-linux (full log)
Attempted: libdigidoc, libdigidocpp, qdigidoc
Partial log (click to expand)
shrinking /nix/store/fyymq7b3mad0sscv2rj11chzwxcay2f9-qdigidoc-3.13.6/bin/.qdigidocclient-wrapped
gzipping man pages under /nix/store/fyymq7b3mad0sscv2rj11chzwxcay2f9-qdigidoc-3.13.6/share/man/
strip is /nix/store/ah0va6j4cnwj9nx4j6rwcfc8nh785jwm-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/fyymq7b3mad0sscv2rj11chzwxcay2f9-qdigidoc-3.13.6/bin
patching script interpreter paths in /nix/store/fyymq7b3mad0sscv2rj11chzwxcay2f9-qdigidoc-3.13.6
checking for references to /build in /nix/store/fyymq7b3mad0sscv2rj11chzwxcay2f9-qdigidoc-3.13.6...
postPatchMkspecs
/nix/store/h10bynjxzjhab4z8dzh4pfz3cpdryk4h-libdigidoc-3.10.4
/nix/store/a8hlk4rn4cnlnr5rnvf8jk4nwfdia7k6-libdigidocpp-3.13.6
/nix/store/fyymq7b3mad0sscv2rj11chzwxcay2f9-qdigidoc-3.13.6


when >1 cred in wallet matching proof req, allow for names in request…

…ed attrs
Signed-off-by: sklump<EMAIL_ADDRESS>

Addresses https://github.com/hyperledger/aries-cloudagent-python/issues/704

Codecov Report

Merging #706 into master will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master     #706   +/-   ##
=======================================
  Coverage   99.02%   99.02%
=======================================
  Files         253      253
  Lines       13686    13686
=======================================
  Hits        13552    13552
  Misses        134      134


Refactor realtime presence spec

Link to internal discussion https://ably-real-time.slack.com/archives/C030C5YLY/p1693863972631609

About this https://github.com/ably/specification/pull/166#discussion_r1320075332, yeah it's confusing either way, because you have to consider server presencemap and not local presencemap while referring to the statement : (


[4.0][Bug] Installation apparently fails at elFinder step on Windows

Bug report
What I did
As reported here, the user ran php artisan backpack:install, and apparently for the "Install elFinder?" prompt they just hit Enter.
What I expected to happen
Install with no elFinder.
What happened
The installation process stopped - but in a weird frustrating way, with no extra info, it just says "Aborted".

What I've already tried to fix it
I've tested on my machine (Mac OS, Laravel Valet), at it worked fine:

I'm wondering if it's environment-related. I see they're using Windows & WAMP.
@pxpm can you please test the installation in Windows and see if you get the same thing?
Backpack, Laravel, PHP, DB version
"I'm running backpack 4.0 on Laravel 6"

Hello guys.
I am sorry i could not reproduce this issue in Win7, Wamp, PHP 7.2.
After running php artisan backpack:install, when asking for el-finder I just pressed enter and it worked fine.
Any more tests i should be running ?
Best,
Pedro

Well then, I'm pretty sure something's wrong with the dev environment. I saw there are quite a few mentions online of other Artisan commands (non-backpack) that are greeted with an "Abort" out of the blue. No solutions there either. So it doesn't look backpack-related, more likely env-related.
Let's close this. Thanks @pxpm !

Same issue here.
Windows 10, Wamp, PHP 7.4, backpack 4.0, Laravel 6.
php artisan migrate is working well but php artisan backpack:install is not.

Solution 1
I tried to skip the error by replacing the line:
https://github.com/Laravel-Backpack/CRUD/blob/fc29b4237a96e547882cceed24fc99b62700ff64/src/app/Console/Commands/Install.php#L44
by:
$shouldInstallElfinder = true;
And now the installer is working fine :)
update
You can skip the error by using: php artisan backpack:install --elfinder yes

Hmmm thank you for the update @mamprogr . Does this help you track down the issue and fix it on Windows @pxpm ?

@tabacitu I don't have win 10 machine. On windows 7 is not happening.
You can check my SS at #2517

@mamprogr I see you've gotten around this issue, and have reached the elfinder:publish step. How did you get around the Aborted problem? It could save some people A LOT of frustration if you share.
Cheers!

@sergeev so you're still having this issue? And @mamprogr 's trick fixed it for you?

It look like the issue hasn't happened in one month, so I'm going to close it. If anybody has this problem again, please let us know and we'll reopen it. Please also let us know the output of your php artisan backpack:version.


Cannot get report for non-covered parts of conditions

Expected Behavior
Less than 100% coverage.
Observed Behavior
100% coverage.
Forensic Information
Operating System: MacOS 12.12.2
Environment Information: node v7.7.1, nyc 10.1.2
(I moved this case from https://github.com/gotwarlost/istanbul/issues/784)
Hi,
I use mocha & istanbul nyc for some projects and lab for some others.
For the very simplified example below nyc reported 100% coverage whereas lab reported less than 100%.
nyc
$ istanbul cover _mocha
const Code    = require('code');
const expect  = Code.expect;

const util = require('../util');

describe('deneme', () => {
  it('should return true', (done) => {
    expect(util.deneme('a')).to.true();
    done();
  });

  it('should return false', (done) => {
    expect(util.deneme()).to.false();
    done();
  });
});

lab
$ lab --coverage --reporter html > report.html
const Lab  = require('lab');
const Code = require('code');

const lab      = Lab.script();
const describe = lab.describe;
const it       = lab.it;
const expect   = Code.expect;

const util = require('../util');

exports.lab = lab;
describe('deneme', () => {
  it('should return true', (done) => {
    expect(util.deneme('a')).to.true();
    done();
  });

  it('should return false', (done) => {
    expect(util.deneme('b')).to.false();
    done();
  });
});

Function
// util.js file
function deneme(a) {
  return (a && a.startsWith('a')) ? true : false;
}

module.exports = {
  deneme
};

Although two branches are executed by tests and as a result tests seem to cover 100% of the code, second part of the condition is never tested/executed.
lab reported that first part of the condition a is always true, so that second part a.startWith('a') is never executed. Please see screenshot below:

A third test should be added for this case:
  it('should return false for undefined', (done) => {
    expect(util.deneme()).to.false();
    done();
  });

Not in this simple example, but in more complex situations it helped me hunt some hard to catch bugs.
Is it possible to detect condition coverage in nyc?
Kind Regards,

Sorry for the delayed response @ozum but nyc does not do static analysis, just instruments and reports code coverage. Thanks for the issue!

@JaKXz No problem for the late.
Isn't my case related to code coverage, because in that tests do not cover second part of the condition?

Yes branches, statements, functions, and line coverage are measured and reported.

In that case, nyc should report below 100%. However it is reporting 100%.
return (a && a.startsWith('a')) ? true : false; (false condition never executed in tests).


add remix-solidity-analyzer as a separate package

looks like we are keeping remix-analyzer for now


Sync to chrome account?

https://developer.chrome.com/docs/extensions/reference/storage/#:~:text=If syncing is enabled%2C the,syncing when it's back online.

Using Google Firestore instead


linux kernel notice

ubuntu 20.04
linux-image-5.4.0-54-generic        rocm-dkms,it's work
linux-image-5.4.0-57-generic        rocm-dkms,it does't work

Hi @clzstc123
Thanks for reaching out.
ROCm is working with 5.4.0-42 and 5.4.0-54 kernels. Not sure about 5.4.0-56, need to check.
Whats the output you are getting?
Request you to share more details for better understanding of the problem.

`diff --git a/amd/amdgpu/amdgpu_bios.c b/amd/amdgpu/amdgpu_bios.c
index 50dff69..b1172d9 100644
--- a/amd/amdgpu/amdgpu_bios.c
+++ b/amd/amdgpu/amdgpu_bios.c
@@ -192,30 +192,35 @@ static bool amdgpu_read_bios_from_rom(struct amdgpu_device *adev)
static bool amdgpu_read_platform_bios(struct amdgpu_device *adev)
{

  uint8_t __iomem *bios;

  size_t size;

  phys_addr_t rom = adev->pdev->rom;

  size_t romlen = adev->pdev->romlen;

  void __iomem *bios;

  adev->bios = NULL;

  bios = pci_platform_rom(adev->pdev, &size);

  if (!bios) {

  if (!rom || romlen == 0)
          return false;

  }

  adev->bios = kzalloc(size, GFP_KERNEL);

  if (adev->bios == NULL)

  adev->bios = kzalloc(romlen, GFP_KERNEL);

  if (!adev->bios)
          return false;

  memcpy_fromio(adev->bios, bios, size);

  bios = ioremap(rom, romlen);

  if (!bios)

          goto free_bios;

  if (!check_atom_bios(adev->bios, size)) {

          kfree(adev->bios);

          return false;

  }

  memcpy_fromio(adev->bios, bios, romlen);

  iounmap(bios);

  adev->bios_size = size;

  if (!check_atom_bios(adev->bios, romlen))

          goto free_bios;

  adev->bios_size = romlen;

  return true;

+free_bios:

  kfree(adev->bios);

  return false;

}
#ifdef CONFIG_ACPI
`
This should fix the compile error for 5.4.0-56+

Thanks @ddobreff for the workaround.
Hi @clzstc123, can you please give a try as above and update.
Thank you.

encountered 5.4.0-56 issue when trying to install 3.10. @ROCmSupport could you roll out 3.10.1 to get this issue fixed?

Hi @clzstc123 and @ye-luo
I, myself, saw this issue, I mean able to reproduce this problem locally with 5.4.0-56. I am working with Kernel team for the fix.
I will update once the fix is available.

Here is the dkms crash dump rock-dkms-firmware.0.txt

Yes @Dantali0n
I found the same crash and our kernel team is working on it.
Thank you.

Hi @clzstc123 and @ye-luo
I, myself, saw this issue, I mean able to reproduce this problem locally with 5.4.0-56. I am working with Kernel team for the fix.
I will update once the fix is available.

sadly, ubuntu update to 5.4.0-57.

Just leaving a note that this same issue cropped up with 4.15.0-126 on Ubuntu 18.04 LTS. The diff above worked to fix it though.

Thanks @darsnack for trying a new kernel for time-being.

Hi All,
Until the fix is available, we recommend to install ROCm on 5.4.0-54 kernel or hwe kernels.
Thank you.

Hi All,
Fix for 5.4.0-56 is ready and pushed too. Updated Documentation accordingly.
Request to try the new packages.
Note: AMD ROCm v3.10 fails to install on Ubuntu kernel v5.4.0-56. To resolve the installation issue, new packages for 'rock-dkms' and 'rock-dkms-firmware' are created and replaced. It is recommended to perform a clean and fresh installation with the new packages.
Thank you.

@ROCmSupport  So let me get this straight, is it fixed now? Will installing it on a fresh Ubuntu w/ kernel v5.4.0-56 result in failure or not? Where do we get the new packages?

Hi @josarv
The kernel packages which have fix, are kept in the same 3.10 repo location.
You can uninstall any existing ROCm and do a fresh & clean install of 3.10 and it works now.

@ROCmSupport  I am sorry for the spam, but it still is not perfectly clear to me (i need sleep). I have performed a clean fresh Ubuntu 20.04 installation (ships with 5.4.0-56) without anything else driver related. Will following these instructions here, result in a failure, or am I good to go and install as per usual following the link?

Hi @josarv
Yon can use the same repo as we have not changed the repo.
We have kept packages with fix into the same repo, I mean we replaced old kernel packages with new set of packages in the same space and so same instructions should work perfect.
Thank you.

Hi All,
Until the fix is available, we recommend to install ROCm on 5.4.0-54 kernel or hwe kernels.
Thank you.

20.04's hwe is 5.8 which doesn't work either

Hi @heuripedes
Request you to wait for ROCm 4.1.
Thanks.

Hi @heuripedes
Request you to wait for ROCm 4.1.
Thanks.

Is there already an approximate date of release? I try to get my Radeon RX570 to work on a 5.8.0-44 kernel with ROCM 4.0, but for already well described reasons this task remains unaccomplished. Using older kernels with ROCM 3.5 caused unforeseen system instability and I really do not want to switch, for several reasons, the brand of my GPU.

Hi @ChrisAi89
It will be released anytime in this month. Please stay tuned.
Thank you.

@ChrisAi89
If you can downgrade linux kernel to 5.4.0, rocm-dkms from ROCm-4.0 can install successfully.
But since RX570, aka gfx803, had been removed from offcial support. It will be some issues when you use it on ROCm-4.0. Please refer here : https://github.com/xuhuisheng/rocm-build/tree/develop/gfx803


absent sesamoid bone of gastrocnemius

Add new term:
absent sesamoid bone of gastrocnemius (a child of abnormal sesamoid bone of gastrocnemius morphology MP:0009005)
DEF: missing the small sesamoid bones situated behind the condyles of the femur
SYN: absent fabella
SYN: absent fabellae
SYN: absent medial sesamoid bone of the knee
Annotations in J:14980, J:52671, J:176532

Added new term:
absent sesamoid bone of gastrocnemius MP:0030859


Update semver major npm modules

No code changes, but we did have to disable random test ordering in jasmine since Cesium's unit tests unfortunately do not work when ran in a random order.
I'll write up an issue to re-enable random test running (and fix broken tests).

@mramato, thanks for the pull request! Maintainers, we have a signed CLA from @mramato, so you can review this at any time.
:warning: I noticed that CHANGES.md has not been updated. If this change updates the public API in any way, fixes a bug, or makes any non-trivial update, please add a bullet point to CHANGES.md and comment on this pull request so we know it was updated. For more info, see the Pull Request Guidelines.

I am a bot who helps you make Cesium awesome! Contributions to my configuration are welcome.
:earth_africa: :earth_americas: :earth_asia:

Whoops, looks like there was some unexpected breakage (probably do to globby update), Looking at it now.

Turns out globby 8.x is fundamentally broken (negated globs don't work): https://github.com/sindresorhus/globby/issues/75
I rolled back to 7.x for now, which is still a newer version, just not the latest.

Looks good, thanks @mramato!


Fix a couple of typos.

Signed-off-by: Henner Zeller<EMAIL_ADDRESS>

Codecov Report

Merging #1274 (dcc3732) into master (bd656bc) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1274   +/-   ##
=======================================
  Coverage   92.80%   92.80%
=======================================
  Files         339      339
  Lines       23526    23526
=======================================
  Hits        21834    21834
  Misses       1692     1692

Impacted Files
Coverage Δ

verilog/analysis/verilog_analyzer.cc
94.40% <ø> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update c4958f6...dcc3732. Read the comment docs.


jQuery error when trying to edit a post

Summary
Write a post, save it and then go to admin/posts, try to click on any post, nothing happens.
The following error gets displayed in developer console.
lib.bundle.js:120 Uncaught TypeError: $(...).selectable is not a function
at HTMLDocument. (lib.bundle.js:120)
at f (lib.bundle.js:80)
at d (lib.bundle.js:80)
Additional info

Postleaf version: using master
Node version: 0.7
Affected browsers: chrome
Operating system: mac os.

What steps have you taken to build Postleaf?

Here are the steps:
git clone https://github.com/Postleaf/postleaf.git
git clone https://github.com/Postleaf/empower-theme.git themes/empower-theme
Copied .env.example to .env and added localhost
vim package.json
edited and saved as per https://github.com/Postleaf/postleaf/issues/78#issuecomment-361139100
npm install
sudo npm install -g gulp-cli
gulp build
node app.js
The app launches fine and I am able to make a post, however, start getting jQuery errors on other interactions as mentioned above.

I have a feeling this has something to do with the latest update to the selectable plugin. You could try forcing the previous release in package.json. Not positive until I have time to test this out though.

Pinning claviska/jquery-selectable to 1.0.6 seems to fix the issue.


Global DNS installation fails to install on rancher with local k8s 1.22.4-rancher1-1

Information about the Cluster
Rancher Server Setup

Rancher version: v2.6-head ed77b51
Installation option (Docker install/Helm Chart): Helm Chart

If Helm Chart, Kubernetes Cluster and version (RKE1, RKE2, k3s, EKS, etc): RKE1, v1.22.4-rancher1-1, 1.3.3-rc6

Proxy/Cert Details: Selfsigned

Information about the Cluster

Kubernetes version: v1.22.4-rancher1-1
Cluster Type (Local/Downstream): Local 3  worker + etcd + cp RKE1

Describe the bug
Installing global DNS from ember UI by navigating to url/g fails with an error. The workload pod systemapp-anu-dns-rancher-external-dns is not deployed and the app is stuck in installing
To Reproduce

Create a rancher server on local k8s 1.22.4-rancher1-1 on an RKE1 cluster with 3 worker + cp + etcd
From URL/g --> Tools --> Global DNS providers --> provide the following details and create

name: test-dns
domain, AWS_Access, aws_secret

Result
The installation fails with the error :
Failed to install app systemapp-anu-dns. Error: validation failed: [unable to recognize "": no matches for kind "ClusterRole" in version "rbac.authorization.k8s.io/v1beta1", unable to recognize "": no matches for kind "ClusterRoleBinding" in version "rbac.authorization.k8s.io/v1beta1"]

Expected Result
Expected the installation to go through without any errors.
Additional context
Installation goes through if the local cluster is on version v1.21

no matches for kind "ClusterRole" in version "rbac.authorization.k8s.io/v1beta1", unable to recognize "": no matches for kind "ClusterRoleBinding" in version "rbac.authorization.k8s.io/v1beta1"
Seems this system-chart needs to be updated to use ClusterRole/v1 and not ClusterRole/v1beta1. Same update  ClusterRoleBinding/v1beta1 to ClusterRoleBinding/v1

This has been worked on, and is likely fixed. Sending to QA for validation with a low priority.

per conversation with @ronhorton this is a team 2 bug.

QA TEST PLAN
Scenarios

Scenario
Test Case

1
As an admin user, create a Global DNS provider and validate that it is able to be created successfully

Validated this is addressed in v2.6-head https://github.com/rancher/rancher/commit/4485a0d6aaef024bb54e700d073394034b638a98.
ENVIRONMENT DETAILS

Rancher install: Helm
Rancher version: v2.6-head https://github.com/rancher/rancher/commit/4485a0d6aaef024bb54e700d073394034b638a98
RKE version: v1.3.19
Browser: Chrome

TEST RESULT

Scenario
Test Case
Result

1
As an admin user, create a Global DNS provider and validate that it is able to be created successfully
:white_check_mark:

VALIDATION STEPS
Scenario 1

Setup Rancher with local K8s cluster using RKE1 v1.24.10-rancher1-1 and RKE v1.3.19.
Created a Global DNS provider with my root domain and AWS credentials.
Created a Global DNS entry using the global DNS provider that I previously created.
On the local cluster, deployed a test ingress with my Rancher FQDN and annotation with key:rancher.io/Global DNS entry, value: Rancher FQDN.
Validated that the Ingress was created successfully and came up Active.


Failed to install plugin

Hi,
i did try to install the plugin, however it fails.
Any idea why it does not work ?
Using 9.4.7 on proxmox.
regards

@malosaa Do you have any other community plugins installed on this Grafana instance?
I have not used proxmox, can it be permission issues?
Check the Grafana logs for more information what happened.

@malosaa You can see the logs in the container's output.
Please review them and let us know if you see any installation issues. I just successfully installed the latest version 3.1.0 to the Grafana Cloud.


travis-ci access error at pull request

fatal: unable to access 'https://github.com/ioBroker/ioBroker.repositories.git/':
see:
https://travis-ci.org/github/ioBroker/ioBroker.repositories/builds/686515803

failed with pull request from minukodu/ioBroker.repositories
passed with pull request from svallant/ioBroker.repositories
pull request from svallant did not check with travis-ci
maybe because minukodu is an organisation ...

today every is fine :-|


Implemented new-style checkboxes with inline SVG and no selection JS, general dependency update

Checkbox-unselected.svg is no longer needed. It can be removed from the src/img/ folder.

With firefox, there's an issue with the checkbox hover/focus style:

Use mouse hover or keyboard focus to land on a checkbox, the hover/focus style is correct as:

Use mouse or keyboard to check the checkbox. The external border of the hover/focus style moves and looks like:

At the step 2, the border should remain still and not move.
This issue only happens with Firefox, not with Chrome and Safari.


Possible compilation of transitions with a missing stage parameter

culling: this only happened during development of massive blend tree


Integrate an EnergyOptimizationSystem as Plugin

It would be cool to have some kind of optimization system that can handle with hourly changing prices, respect solar prediction to build a charging discharging + keep load state for the battery.
for forecast source we could use api.akkudoktor
so what needs to be done

[ ] get hourly prices
[ ] get hourly forecast
[ ] analyse the data
[ ] find the best battery-state plan 6 different times (fort the time of use)
[ ] set those plans using the existing time of use implementation

i have a private project doing this. it works once a day 0:01 it runs and sets my states.
how can i send you my code to review and maybe porting this to a plugin?
@kbialek would be awesome to have such a plugin
questions welcome cheers
Andy

hi! If you want to make your plugin public, then well, make it public :smile: at github or any other platform of your choice. Then send me a link and I will add it here https://github.com/kbialek/deye-inverter-mqtt?tab=readme-ov-file#list-of-public-plugins

well its not a plugin at the moment, its some kind of spaghetti-code, but its working. i was hoping you will find some time to make it a plugin and we can optimize it together.

I can maybe review your code and provide some feedback, but will not
actively participate in coding for sure. Sorry, I have no time for that.
On Tue, Dec 10, 2024 at 9:57 PM finfin82 @.***> wrote:

well its not a plugin at the moment, its some kind of spaghetti-code, but
its working. i was hoping you will find some time to make it a plugin and
we can optimize it together.
—
Reply to this email directly, view it on GitHub
https://github.com/kbialek/deye-inverter-mqtt/issues/216#issuecomment-2532874893,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAMQMXEUPWX3FFACU7HSVOD2E5ISPAVCNFSM6AAAAABTJPDM2WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMZSHA3TIOBZGM
.
You are receiving this because you were mentioned.Message ID:
@.***>

Thx for your feedback, I will give it a try.


More nuanced error message when internal id can't be found

The error No source non-global ID value could be fetched from the source object (from absinthe_relay/lib/absinthe/relay/node.ex) can mean different things, including

you forgot to add a matching pattern to node field
you're asking for the id of an associated sub-field, but you've forgotten to call preload before returning a result (info.source is Ecto.Association.NotLoaded)

... a more verbose error message (and one that goes out to Logger.warn at the very least) would be helpful.

Could also mean (as a generalization of your second):

The source object doesn't have an id field as expected by the default id fetcher

Yep, true! I'd actually be okay if you simply logged the content of info.source. That would be enough to nudge me in the right direction as I'm bug hunting.


Update golang Dockerfile reference

PR Summary
Commit d73576e0fa64410c458dbb330013b45018fe9aca moved the location of Dockerfile.golang. This PR adjusts sources to changes.

@smythp please merge if possible

Hey, my apologies, but we're making some changes on how these files are generated and since the file is generated elsewhere, we won't be able to merge the PR. Thanks for the contribution and hope you're having a good week.


add gentx Wanderer

Please make sure your node is up and running. Join #validators Discord for help: https://discord.gg/QeJWCrE.


Fixes #5934

This fixes the issue at https://github.com/facebook/react-native/issues/5934; basically ListView on Android may crash when adding elements that are rendered off-screen.
As the default settings for ListView was requiring action to be taken on the result returned by renderRow to avoid a crash, I've changed the default to false in the hopes that users changing the prop will read the docs first.
Test plan (required)
See failure at https://github.com/npomfret/react-native-bug-reports/tree/master/ListViewUpdatingBug

@vjeux would you mind taking a look at this pull request? It's been a while since the last commit was reviewed.

Hey, thanks for the pull request and sorry it took so look to look at it. Unfortunately, this is not the right fix. We need to make sure that the feature works correctly and not just straight disable it

Any other methods to fix this problem?


Make toggling work

@teonlamont let me know if this does it for you

omg, yes! it works!! thanks @mainakjas :)


Redundant "out-side" label and final model training.

Hi,
When using a labeled data where "non-entity" words are already labeled with "O", 'tag_ouside' variable set to "O" adds a label and makes the input tensor dimensions incorrect (by 1 unit).
Also, when training final model after hyperparameter tuning on full data, is there a way to disable validation set while training?

Hi @danbogu
First and foremost - thanks for the feedback, it is much appreciated :)

When using a labeled data where "non-entity" words are already labeled with "O", 'tag_ouside' variable set to "O" adds a label and makes the input tensor dimensions incorrect (by 1 unit).

Can you provide a reproducible example? It would make it much easier for me to investigate the matter. Besides from that, the tags of named entities should definitely be different from the special outside tag.

Also, when training final model after hyperparameter tuning on full data, is there a way to disable validation set while training?

Unfortunately not, but I am certainly open to the idea, and if you make a pull request on this, I will be happy to inspect it and merge it in :) Are you interested in this?

Hey @smaakage85,
About the first topic, at a later stage, I realized that I just need to omit 'O' from the tag_scheme I provide to solve the dimension exception.
If you still want me to provide a more detailed example I would be happy to do so.
Also, I am surely interested to try to resolve the second thing I mentioned. I have a few simple solutions implementations in my head. let's do it :)

Sounds good @danbogu
Looking forward to your pull request :D


Missing Microsoft.DotNet.ILCompiler package on s390x

When running an iterated source-build on s390x (i.e. using the output of the previous source-build as input set of package instead of the tarball), building the SDK fails due to a missing package Microsoft.DotNet.ILCompiler.
On Intel, this package is generated by the runtime repository, but on s390x this does not happen due to a check in eng/Subsets.props:
        <ProjectToBuild Condition="'$(NativeAotSupported)' == 'true' and '$(RuntimeFlavor)' != 'Mono'" Include="$(InstallerProjectRoot)\pkg\projects\nativeaot-packages.proj" Category="packs" />

Both the NativeAotSupported check and the RuntimeFlavor check fail on s390x.
Fixing this in the runtime build seems non-trivial since the actual artifacts to be packaged in that package are only created as part of the CoreCLR build, which doesn't happen on s390x.
Also, given that this package - while it itself seems to be platform-agnostic - simply adds support to the SDK to pull in various other packages needed for the NativeAOT build, and those are not available on s390x either, it seems this package shouldn't be really needed on s390x.   We accept that the NativeAOT feature will not be available on the platform.
I thought this would be a simple matter of making the Microsoft.DotNet.ILCompiler line in src/Layout/redist/targets/BundledSdks.targets in the SDK repo conditional on the platform.  But it turns out this isn't easily possible as the SDK repo build as part of the source-build process doesn't appear to even be aware which platform is being targeted.  None of the Architecture, TargetRid or Platform properties (or any other property I could identify) are set to indicate a s390x target architecture.
We could disable the line for building with source-build generally, but I understand this is undesirable, as there is supposed to be NativeAOT support on Intel (even though the compiler packages aren't build with source-build, they would be pulled in from nuget at runtime if the SDK support is available).
@crummel any suggestions on how to best address this problem?
FYI - @tmds @omajid @janani66

None of the Architecture, TargetRid or Platform properties (or any other property I could identify) are set to indicate a s390x target architecture.

I built .NET from source last week for x64 using mono runtime. I had to apply some simple patches here and there.
From that, I think it would be good if we have a single way of passing the build is with mono runtime to the repositories from source-build.
Suggestion for name: '$(UseMonoRuntime)' == 'true'.
For separate repo builds, the repositories can still set this to true, for example when the see the architecture is s390x.
@crummel @MichaelSimons how does that sound?
I can look into implementing this.

Same issue is being faced on the ppc64le source-build

@MichaelSimons how does that sound?

I am in favor of that.

@janani66 @tmds @uweigand Is there any remaining work here or can this be closed?

Closing as I believe this has been resolved, feel free to reopen if not.


don't zoom out after organising

After organizing the symbols, the canvas is automatically zoomed out to show an overview of all symbols.
This is really absolutely never helpful. It's just annoying, because I always have to zoom back in and find the position where I duplicated some symbols with drag+Alt and wanted them to be organized.
And since I usually have many symbols, finding the previous position is quite an effort.
So PLEASE... just remove it. Organize the symbols, but do not zoom out. Thank you!

@UsernameWasAlreadyTaken, thanks for the feedback. This feature was added in response to some people wondering why everything disappeared from their view (not realizing they needed to zoom out and back in to see where their symbols were moved to). So your preference isn't universal. That being said, it's something that might be useful to add as an option, so I will consider it as a possible enhancement.

Ok, it might be helpful if you only have 10 symbols and no idea what happens when you run the plugin.
In my current project there are >450 symbols in >160 rows...
It's definitely useful to add as an option. Thanks a lot!

+1. The zooming back in navigation a huge design system library is killing me.

Hello i prefer to zoom back (which is not working now). Is it possible to make this an option in configuration?

@UsernameWasAlreadyTaken, @aentan, @ozgurgunes you will all be happy to know that Zoom Out is an option you can disable, in version 15.8 which I just published.

Thanks a lot! I was already happy when it was removed in one of the previous updates :D


Use Appveyor for Continuous Integration

It is free for open-source projects, that way we could test each pull requests for compilation and execute all Tests (probably only DotNet45 but maybe also WinRT/UWP)
https://www.appveyor.com/

Done! Amazing tool... thanks


Can get userIds from a CSV

Hey there 👋
A great and simple script. Love it.
I've added the ability to read from a csv. So that if you follow a lot of people, you don't need to add the list add the end of the command, you can just read it from a csv.

Hello 👋
Is there any difference between doing this and using @file.txt?
Given if an user ID starts with @ it will be treated as a file, with one account per line.
Except from a CSV file having a header, wouldn't it give the same result? 🤔

I somehow completely missed this functionality XD My mistake. Thanks 👍

Hey there! Thanks. I somehow completely missed this functionality XD I'll close the PR


chore(deps): upgrade dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-main" workflow

Codecov Report

Merging #497 (7506790) into main (4a56e6a) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #497   +/-   ##
=======================================
  Coverage   95.69%   95.69%
=======================================
  Files           1        1
  Lines         395      395
  Branches       53       53
=======================================
  Hits          378      378
  Misses         17       17

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Update netAs.cpp

Here's more informations about that ASN:
https://ipinfo.io/AS47674

Merged as 6863d3e9f45867a71f84365bb76c335f1e660ab0.


Added channel argument for Octopus Deploy Release.

Added the channel argument for the OctopusDeploy tool when deploying releases, as detailed in #1587.

@islopma,
Thanks for your contribution.
To ensure that the project team has proper rights to use your work, please complete the Contribution License Agreement at https://cla2.dotnetfoundation.org.
It will cover your contributions to all .NET Foundation-managed open source projects.
Thanks,
.NET Foundation Pull Request Bot

@islopma, thanks for signing the contribution license agreement. We will now validate the agreement and then the pull request.
Thanks, .NET Foundation Pull Request Bot

@mholo65 I have added the test.
Thanks for your reviews.

@islopma  your changes have been merged, thanks for your contribution 👍


Don't overwrite Promise if it already exists in the global scope

Fixed the issue discussed here : https://github.com/oliver-moran/jimp/pull/113
Currently, the Promise object is always replaced by the es6-promise Promise implementation.
This PR fixes the issue (we need to explicitly use the global node object).

I don't understand why it the Promise variable "escaped" from its closure and overwrote the other promise.

es6-promise automatically polyfill some Promise implementations (bluebird for example).
See here for more details : https://github.com/stefanpenner/es6-promise/issues/163

Beautiful!
Thank you. It will be in the next release, which will be going out shortly.


[wip] fix sporadic order failure

We said in https://github.com/ManageIQ/manageiq/pull/17716 that this failure would be fixed with a splat but I'm pretty sure that's wrong, the "entries" order is still making this test fail sporadically.

@agrare Please review.

I mean, @agrare, please don't, this won't work, I just couldn't reproduce locally. I don't know what the right way to do this is. It's only failing on travis.

Yeah so I don't think the contains_exactly(*) is the issue because it isn't the order of the top-level array that is wrong.  Since it is the child "entries" array that is failing I think we need to change let(:tag_export_test) to have: "entries" => array_including([{"description"  => "Test Entry",

@d-m-u can you also updated tag_default_export_test?


Create GetQuotesHistoryDraw-v1.2.ring

GetQuotesHistoryDraw-v1.2.ring  --- Version 1.2
NEW updated version to handle changes in finance.yahoo.com

Uses Ring Curl to get Cookies and Crumbs
Yahoo uses new URL type interface, with epoch time and different parameters.
Yahoo returns data in a different format

Please remove OLD vesion 1.0 and replace it with this version 1.2

Thanks for the update


Add to conda-forge

It would be nice to also have IRIS-HEP tools available on conda-forge.
For servicex there's some additional work in other areas though that would be required as using grayskull to check we find
$ grayskull pypi --list-missing-deps --strict-conda-forge 'servicex==3.0.0a12'

#### Initializing recipe for servicex==3.0.0a12 (pypi) ####

Recovering metadata from pypi...
Starting the download of the sdist package servicex
servicex 100% Time:  0:00:00   1.7 MiB/s|#################################################################################################################################################################|
Checking for pyproject.toml
pyproject.toml found in /tmp/grayskull-servicex-u73ng_33/servicex-3.0.0a12/pyproject.toml
Recovering information from setup.py
Executing injected distutils...
Checking >> types-pyyaml 100% |####################################################################################################################################################|[Elapsed Time: 0:00:06]
Recovering license info from spdx.org ...
Matching license file with database from Grayskull...
Match percentage of the license is 97%. Low match percentage could mean that the license was modified.
License type: BSD-3-Clause
License file: ['LICENSE']
Build requirements:
  <none>
Host requirements:
  - python >=3.8
  - hatchling >=1.13.0
  - pip
Run requirements:
  - python >=3.8
  - qastle >=0.17
  - func-adl >=3.2.6
  - requests >=2.31
  - pydantic >=1.10,<2.0
  - httpx >=0.24
  - miniopy-async >=1.15
  - tinydb >=4.7
  - google-auth >=2.17
  - typer >=0.9.0
  - pyyaml >=6.0
  - types-pyyaml >=6.0
  - rich >=13.0.0
  - nest-asyncio >=1.5.7
  - aiofile
  - make-it-sync

RED: Missing packages
GREEN: Packages available on conda-forge
Missing dependencies: qastle, make-it-sync, func-adl, miniopy-async

Maintainers:
   - matthewfeickert

#### Recipe generated on /tmp for servicex==3.0.0a12 ####

that qastle, make-it-sync, func-adl, miniopy-async are all missing from conda-forge.
I can follow up with @gordonwatts and @masonproffitt on if they're okay with me packaging func-adl, qastle, and make-it-sync for conda-forge. miniopy-async isn't missing any packages, so we could ask if they would consider distributing on conda-forge too. (Done in https://github.com/hlf20010508/miniopy-async/issues/25)

https://github.com/conda-forge/staged-recipes/pull/25848 added https://github.com/conda-forge/miniopy-async-feedstock so miniopy-async is now packaged on conda-forge.

Now just missing func-adl and qastle
$ grayskull pypi --list-missing-deps --strict-conda-forge 'servicex==3.0.0a15'

#### Initializing recipe for servicex==3.0.0a15 (pypi) ####

Recovering metadata from pypi...
Starting the download of the sdist package servicex
servicex 100% Time:  0:00:00   4.9 MiB/s|#################################################################################################################################################################|
Checking for pyproject.toml
pyproject.toml found in /tmp/grayskull-servicex-w83ffbke/servicex-3.0.0a15/pyproject.toml
Recovering information from setup.py
Executing injected distutils...
Checking >> types-pyyaml 100% |####################################################################################################################################################|[Elapsed Time: 0:00:06]
Recovering license info from spdx.org ...
Matching license file with database from Grayskull...
Match percentage of the license is 97%. Low match percentage could mean that the license was modified.
License type: BSD-3-Clause
License file: ['LICENSE']
Build requirements:
  <none>
Host requirements:
  - python >=3.8
  - hatchling >=1.13.0
  - pip
Run requirements:
  - python >=3.8
  - qastle >=0.17
  - func-adl >=3.2.6
  - requests >=2.31
  - pydantic >=1.10,<2.0
  - httpx >=0.24
  - miniopy-async >=1.15
  - tinydb >=4.7
  - google-auth >=2.17
  - typer >=0.9.0
  - pyyaml >=6.0
  - types-pyyaml >=6.0
  - rich >=13.0.0
  - aiofile
  - make-it-sync

RED: Missing packages
GREEN: Packages available on conda-forge
Missing dependencies: func-adl, qastle

Maintainers:
   - matthewfeickert

#### Recipe generated on /tmp for servicex==3.0.0a15 ####

$

with PRs opened to help address this:

https://github.com/iris-hep/func_adl/pull/144
https://github.com/conda-forge/staged-recipes/pull/26178

Quick question about this, @matthewfeickert - these are pure python packages - what is the advantage of also maintaining a package there, vs. just having them in pypi and pulling them from there (which I think conda's various package managers can now)? I'm asking because the more moving parts there are, the more likely it is things will get out of sync.

@gordonwatts Good questions.

these are pure python packages - what is the advantage of also maintaining a package there, vs. just having them in pypi and pulling them from there (which I think conda's various package managers can now)?

Conda requires all dependency packages to already exist somewhere as conda-packages for you to be able to package something as a conda package. So to be able to package the serviceX client you need all its dependencies on conda-forge.
As to "why package the serviceX client on conda-forge at all if it is pure-Python?", the only conda package manager that truly resolves things with equal parity between conda package indexes (e.g. conda-forge) and pip package indexes (e.g. PyPI) is pixi, so in general if you have people using a conda family tool, you want them to be able to interact with conda-forge as much as possible and only fall back to PyPI when needed.
It is true that in most situations in which you're dealing with things on PyPI you're not going to run into problems, but providing these simple repackagings also cuts down on the package resolution that your package manager of choice needs to do between the different metadata trees.
So this is not necessary, but it does makes things easier, especially the more complex an environment gets where incorrect solves can start to happen.

I'm asking because the more moving parts there are, the more likely it is things will get out of sync.

Not really (though I mean, yes, that is just a true statement about things). Even if the human in the loop reviewing the autogenerated PRs is considered the problem/blocker here you can enable automerge so that conda-forge just keeps your tools updated as long as they build. It is perhaps better to think about having a package feedstock on conda-forge being controls that you hook into the conda-forge framework than what we do with distributing packages to PyPI where you have to come with your own packaging system and then just distribute the resulting artifacts.
I will give you though that if you have a complex system like scikit-hep/fastjet that is forced to use older build systems then adding initial support to conda-forge can be a huge pain. Though, as you noted, for these pure-Python packages it is basically a single command line call and you're good to go.

https://github.com/conda-forge/staged-recipes/pull/26178 has been merged and so there is now https://github.com/conda-forge/qastle-feedstock. The only remaining thing is for @gordonwatts to make a new func_adl release with the license packaged (https://github.com/iris-hep/func_adl/pull/144#issuecomment-2192272358).

Now everything is on conda-forge, but ruamel_yaml is abandoned and so way behind the required versions (c.f. https://github.com/conda-forge/ruamel_yaml-feedstock/issues/107).

Adding with https://github.com/conda-forge/staged-recipes/pull/27997


Unable to install the latest version 0.1.6

I receive an error with the new version: 0.1.6 with Python version 3.8.6.
When I try to install dm-tree:
pip install dm-tree

I receive this error:
unable to execute 'bazel': No such file or directory
error: command 'bazel' failed with exit status 1

I cannot install the latest version. But it works with 0.1.5.
Python version: 3.8.6
dm-tree version: 0.1.6

The same issue arose for me. Behaviour appears to b somewhat unpredictable. When pip downloads
dm_tree-0.1.6-cp36-cp36m-manylinux2014_x86_64.whl, it works, but when attempting to build from dm-tree-0.1.6.tar.gz, it fails. Don't know why it chooses differently in different cases of doing essentially the same pip install -v --no-cache-dir -r requirements.txt. Doing this within a Docker FROM tensorflow/tensorflow:2.3.0-gpu.

@NastasiaSaby, are you running linux by any chance?
I originally released the wheels with (a fairly recent) manylinux_2_4 tag which, I assume, does not work on some distros. I've since uploaded manylinux2014 wheels. Could you try installing dm-tree again?
@KeithWM interesting! I've tried uninstalling and installing dm-tree locally but couldn't reproduce the behavior you're describing. Could you confirm that the behavior persists if you upgrade pip prior to doing pip install -v ...?

@superbobry yes, I'm using Linux. It's working this morning when I install dm-tree. Thank you for your help!
@superbobry @KeithWM Can I close the issue?

Thank you very much for the quick response! My builds are now passing again, presumably due to the change by the changes you mention. I was surprised yesterday evening when it worked, but it was the "I can close my laptop now" moment so I ddin't bother thinking why or revisiting this post.
Thanks again.
Yes, @NastasiaSaby, you can close the issue.


Could not upload annotation

My actions before raising this issue

[ ] Read/searched the docs
[ ] Searched past issues

Steps to Reproduce (for bugs)

Created a project and upload images locally
Uploaded COCO annotations .json using this guide

Expected Behaviour

I expected that the annotations upload and create masks
Current Behaviour

When I upload annotation.json I get this error:

how can I upload annotated data to CVAT?

docker logs cvat_server?

@aligh97
Check your annotations file to correspond the specification.
Stacktrace says:
cvat.apps.dataset_manager.bindings.CvatImportError:
Image 325993751_557047063027508_8450010938490438274_nH4GU0RW9AJG39POKEFGZ_39e3: can't import annotation #1 (polygon): annotation has no label

@aligh97 Does CVAT task contains these categories in labels specification?

@zhiltsov-max  Maybe you have an idea?

I solved it.
When I create a new task with different labels, CVAT gives them id like 21, 22, ...(that's because the last label category id from the last task we created is 20). if we assign these label ids to our category ids in annotation.json, it will upload properly.

I get that error again.
this is the content of annotation.json:

...
"categories": [
        {
            "id": 0,
            "name": "COAT"
        },
...
"id": 5,
"image_id": 2,
"category_id": 0,

The reason is probably that the category ids are starting from 0 in the annotation file. CVAT follows the original format and expects category ids starting from 1. As a simple workaround, I can suggest changing the category id to some other positive number in the category definitions and in the following annotations.

@zhiltsov-max
Yes. I changed the category ids in the annotation file and it worked. thanks.

@zhiltsov-max 我的错误是 "can't import annotation #0 (bbox): annotation has no label"，根据你的提示最终解决了问题，谢谢！


Enable WINE support for Linux

This PR adds code to automatically detect if the JVM host is not running Windows and then pass all Valve SDK tools through WINE accordingly.
A new function was created to handle this since Unix-family systems parse command arguments a little differently when called by the JVM directly, passing it through bash instead can work around this:
public static ProcessBuilder createProcessCrossPlatform(String path) throws IOException {
        ProcessBuilder pb;
        if (!System.getProperty("os.name").contains("Windows")) { // UNIX - run all exes through WINE
            String[] pcmd = new String[] {"bash", "-c", "wine" + " \"" + path};
            pb = new ProcessBuilder(pcmd);
            pb.redirectErrorStream(true);

            // debug
            String s = "";
            for (String st : pcmd) {
                s = s + " " + st;
            }
            System.out.println(s);

            return pb;
        } else { // WinNT - native
            pb = new ProcessBuilder(path);
            pb.redirectErrorStream(true);
            return pb;
        }
    }

This method is tried and tested in my own Firestar mod manager.

this is cool as, I'll be sure to release it as soon as possible, though I'd like to rewrite a bit of my own code before doing that


Add hipDrvOccupancyMaxActiveBlocksPerMultiprocessor

Equivalent to cuOccupancyMaxActiveBlocksPerMultiprocessor.

Following the occupancy APIs provided through CUDA, we need to rename the existing hipOccupancyMaxActiveBlocksPerMultiprocessor @ line 2950 to the one you proposed instead of adding a new one. Adding new one won't solve the issue. In addition, PyTorch's hipifying script needs to replace cuOccupancyMaxActiveBlocksPerMulitprocessor with the one you proposed.
Furthermore, the similar renaming should be applied to hipOccupancyMaxActiveBlocksPerMultiprocessorWithFlags as well.

Following the occupancy APIs provided through CUDA, we need to rename the existing hipOccupancyMaxActiveBlocksPerMultiprocessor @ line 2950 to the one you proposed instead of adding a new one. Adding new one won't solve the issue. In addition, PyTorch's hipifying script needs to replace cuOccupancyMaxActiveBlocksPerMulitprocessor with the one you proposed.
Furthermore, the similar renaming should be applied to hipOccupancyMaxActiveBlocksPerMultiprocessorWithFlags as well.

Existing one is equivalent for __host____device__cudaError_t cudaOccupancyMaxActiveBlocksPerMultiprocessor ( int* numBlocks, const void* func, int  blockSize, size_t dynamicSMemSize )

The one corresponding to cudaOccupancyMaxActiveBlocksPerMultiprocessor is already provided at line 3374. The implementation on line 3376 needs to use the new API you proposed. cudaOccupancyMaxActiveBlocksPerMultiprocessor is a C++ interface and provided as function template.

LGTM


Automated snapshot publishing for guardrail modules

Currently snapshots are not published in between releases, it would be neat to have them for early adoption of new features.
Looking at the release process, I do not think it is possible to implement snapshots without changes to it, because each module being released separately does not play well with automation of tools like sbt-ci-release and sbt-dynver, because it is difficult to determine which modules in the sbt project change and which of them require version bumps in an automated way.
Having this in mind, I see only two ways to implement snapshots:

Release whole repository under a single version.

Use https://github.com/sbt/sbt-ci-release and https://github.com/scalacenter/sbt-version-policy to set it all up

https://github.com/scalacenter/sbt-version-policy#how-to-integrate-with-sbt-ci-release
https://github.com/scalacenter/sbt-version-policy#how-to-integrate-with-sbt-dynver

This is likely how all Scala OSS projects that have automated publishing of both releases and snapshots do it.
Version policy becomes project-wide, kind of looses its meaning.

Split modules up to their own repos.

Implement separate release processes with https://github.com/sbt/sbt-ci-release and https://github.com/scalacenter/sbt-version-policy.
Too much of a hassle during development.

Might work okay with git submodules.

Not my personally preferred route.

Since there are tradeoffs in proposed changes, I guess the question is - manual release process with correctly enforced version policy for all modules or having automated snapshot publishing, which of these is more beneficial? I am obviously leaning towards the latter, but I might be missing some details on why release process for guardrail is the way it is now.
Thoughts?

Thank you for the writeup!
A single version was causing unnecessary version bumps and CI hours wasted for users, bumping a Java module shouldn't cause a version bump PR for Scala users and vice versa.
Split modules may be coming soon, but I'm still holding on as long as I can, since loading the entire project int a single sbt instance is still very convenient. (It may be possible to still load them all into a single runtime by way of ProjectRef, but I haven't attempted that yet).
All that being said, however, reading through your links got me to realize that I think we were only limited by useReadableConsoleGit (until https://github.com/sbt/sbt-git/pull/238 is merged, at least!) as well as a parameter to the release action. We're already using sbt-ci-release, and I've done all the work to get the module version derived by tag, so it might just work.

Hmm. I didn't close that intentionally.

Ok. Manual snapshots cut, for now at least.
[info] guardrail-core / version
[info] 	0.75.3-SNAPSHOT
[info] guardrail-scala-support / version
[info] 	0.75.3-SNAPSHOT
[info] guardrail-scala-http4s / version
[info] 	0.76.1-SNAPSHOT
[info] guardrail-scala-akka-http / version
[info] 	0.76.0-SNAPSHOT

NB: You need to explicitly libraryDependencies ++= Seq(...) all of these in your project/guardrail.sbt, since the ABI has been broken as we work up to 1.0.
Closing this for now, after confirming that the snapshot for guardrail-core was published to s01.oss.sonatype.org.


General Usability Issues

This is a placeholder/container issue to track bugs, UX, etc issues discovered during hackweek
Low value bugs (fixes should be straight forward)

(BUG) Rancher Backups / Backups / Create - Schedule placeholder suggests @midnight yet when entered we say this is an Invalid cron schedule
(BUG) Persistent Volume Detail Page (default Config tab)- Border box  showing the associated PVC grows crazy high when the 'Customise` tab is selected

(BUG/UX) Detail Masthead - Age field is not live

Screenshot taken many minutes after creation. Given that our table age is live, this seems a bit misleading

(BUG) Setup Page has no vertical scroll bar

Note - Would Sean's changes to a responsive log in page fix this?

High Value UX

(UX) K9S Comparison - There's no way to see an overview of which pods are consuming high CPU/Memory. This is useful when your tiny node can't hack it, made worse when it can't handle monitoring app. The info is shown in k9s, but didn't see it in kubectl get pod -n cattle-system -o wide
(UX)  Resource Finalizers - It's not obvious if a resource has a finalizer. We should make this more prominent (it doesn't have to be in-your-face obvious). As a secondary issue we should then think about how to help the user remove this, as a last resort, to remove a resource. This would help in situations where a cluster was now getting deleted.
(UX) Cluster Tools List - When one is installed we show associated resources. If you click on the card it takes you through to app details page with the Resource list showing by default. If a NS filter is set (like the default) the resource list is empty (which jars when we've just said there are 'x' resources. Generally should detail page resource lists be fitlered by the NS values?
(UX) Mistakes when installing helm apps are costly

If a mistake leads to a condition that will never succeed the user has to wait 10 minutes for the helm operation to fail before deleting/updating the helm app with a fix
There are helm operation pods in progress... but it's hard to align when multiple operations are running
(i tried to install a chart requiring a PVC, then made a mistake when installing longhorn)

Medium Value UX

(UX) Cluster Tools List - Clicking on Install takes user straight to install wizard. I wanted to learn more before installed (via chart detail page)
(UX) Create Custom Cluster / Cluster Details Page / Registration Tab - Confusing text shown

Unclear what this refers to, specifically when the command isn't shown (windows nodes can't initially be applied)
Suggestion - change both references to Run the command below....

(UX) Install/Edit/Upgrade Chart Step 2 (yaml)

This page really needs an 'overrides' view. Currently you have to find values in default template
If an error occurs user has to restart wizard  (longhorn sets itself as default... without unsetting existing default... causes helm error)

(BUG) Explorer side nav highlight weirdness

Starred group is highlighted when workload is selected
Item is double highlighted (not possible to work around)?

General (known, issues somewhere)

(UX) Creating namespaces in the same context as create project would be very handy
(UX) Explorer side nav - Collapsing groups are a pain when switching back and forth between two resources

Can this be separated into different issues for triage purposes?
I don't think any of these items already have issues except for the last one, which is tracked here https://github.com/rancher/dashboard/issues/6658

They can be split out when we commit to them

I'm saying they'd be more likely to get done if we didn't have to commit to all of them at once.


Implementation for method "DatasetIterator_ImageText" cannot be found

When running the method extract_visual_features in file FLIP.py, method DatasetIterator_ImageText is called in line 562. However, this method has not been defined anywhere in the repo. Could you add the implementation for DatasetIterator_ImageText?

Thanks for raising this issue. The function should have been DatasetIterator_FLIP instead of DatasetIterator_ImageText. I have now altered FLIP.py. Please let me know if you face any other problem.

This is now fixed, thank you.


Player timestamp syntax for YouTube

For me to get the links to work for YouTube, they need to be with an "?" (insted of an "x") and have to be a non-decimal. Is there a way to modify the timestamp syntax?

Apologies for the long period of inactivity on this project. I wanted to inform you that the plugin has been fully rewritten for the v3 release, which has addressed this issue. I'm currently preparing for the beta release. Once it's available, if you encounter similar issues, please don't hesitate to open a new issue. Thank you for your understanding.


http status?

In past teams I have worked on we always seemed to find existing tracing tools lacking.  Specifically we required one log msg at the end of a request that contained the HTTP status, latency, inbound msg, outbound response, HTTP path (with templated path params, e.g. /some/rest/path/{id} ), trace/span/parent_span ID's, HTTP method, and app name.
As such we have always had to roll our own solution.  Is there a way to add HTTP status, inbound msg, outbound response, path with templated path params, app name, and parent_span ID to Spring Sleuth?  With all this data we were able to easily troubleshoot issues quickly.

Can you describe what you mean by:

Is there a way to add HTTP status, inbound msg, outbound response, path with templated path params, app name, and parent_span ID to Spring Sleuth?

With the 2.0 version and Brave support you can provide your own bean of HttpTracing and log whatever message you want whenever an HTTP span is created.
Example for the legacy Sleuth approach with Brave: https://github.com/spring-cloud/spring-cloud-sleuth/blob/master/spring-cloud-sleuth-core/src/main/java/org/springframework/cloud/sleuth/instrument/web/TraceHttpAutoConfiguration.java#L53-L62
Here you can log whatever you want:
https://github.com/spring-cloud/spring-cloud-sleuth/blob/master/spring-cloud-sleuth-core/src/main/java/org/springframework/cloud/sleuth/instrument/web/SleuthHttpServerParser.java#L62-L80

Can you describe what you mean by:
Is there a way to add HTTP status, inbound msg, outbound response, path with templated path
params, app name, and parent_span ID to Spring Sleuth?

So we use ELK.  It is important that all the items are provided on the same log msg... similar to having it all on the same row in a DB.  So when Spring Sleuth sends log message to ELK it would need to have all those items.

With the 2.0 version and Brave support you can provide your own bean of HttpTracing and log whatever message you want whenever an HTTP span is created.

Hey pretty cool.  The HTTP status, and response, and latency need to be logged at the end of a request.  And they need to be added to the same log msg that was mentioned in my paragraph.  So can we use HttpTracing to decorate the one final log msg with that missing items?

Here you can log whatever you want:
https://github.com/spring-cloud/spring-cloud-sleuth/blob/master/spring-cloud-sleuth-core/src/main/java/org/springframework/cloud/sleuth/instrument/web/SleuthHttpServerParser.java#L62-L80

This looks promising.  Its funny how it has the check for 200 OK and error != null cause I remember having to write that same code in the custom Servlet Filter to accomplish same.
Would it be possible to have a few days to process and test this out before closing the issue?

The default data policy can be overridden to include response code always.
Why are you replicating so much span data in elasticsearch vs just sending
zipkin data there and correlating the rest with trace and span ID?
On 5 Mar 2018 6:09 am, "Jose Martinez"<EMAIL_ADDRESS>wrote:
Can you describe what you mean by:
Is there a way to add HTTP status, inbound msg, outbound response, path
with templated path
params, app name, and parent_span ID to Spring Sleuth?
So we use ELK. It is important that all the items are provided on the same
log msg... similar to having it all on the same row in a DB. So when Spring
Sleuth sends log message to ELK it would need to have all those items.
With the 2.0 version and Brave support you can provide your own bean of
HttpTracing and log whatever message you want whenever an HTTP span is
created.
Hey pretty cool. The HTTP status, and response, and latency need to be
logged at the end of a request. And they need to be added to the same log
msg that was mentioned in my paragraph. So can we use HttpTracing to
decorate the one final log msg with that missing items?
Here you can log whatever you want:
https://github.com/spring-cloud/spring-cloud-sleuth/
blob/master/spring-cloud-sleuth-core/src/main/java/org/
springframework/cloud/sleuth/instrument/web/SleuthHttpServerParser.java#
L62-L80
This looks promising. Its funny how it has the check for 200 OK and error
!= null cause I remember having to write that same code in the custom
Servlet Filter to accomplish same.
Would it be possible to have a few days to process and test this out before
closing the issue?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/spring-cloud/spring-cloud-sleuth/issues/882#issuecomment-370268868,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAD61_LkA00jGsGlWm_QnP_OjdaUSq_Fks5tbGYUgaJpZM4Sbg5S
.

Ping @jmart1 ?

Why are you replicating so much span data in elasticsearch vs just sending
zipkin data there and correlating the rest with trace and span ID?

So we like to send data to ElasticSearch (ES) so that it can then be queried, graphed, trended, monitored, reported, etc.  We do all of the above based on HTTP status, API, application, latency.  We also need the request bodies and response bodies of everything coming in and out.  By having all this data on one ES entry, it makes very easy to troubleshoot.  As you know ES has amazing and powerful querying features, especially when used with Kibana.
I am working right now on following the steps detailed int he links that @marcingrzejszczak  provided.

How exactly am I suppose to get my own HttpServerParser implementation to get used?  I noticed that TraceHttpAutoConfiguration.httpTracing() is conditional on missing.  So does that mean if I add my own HttpTracing that TraceHttpAutoConfiguration.httpTracing() will not get executed?
I tried creating my own SleuthHttpServerParser impl and putting it into the Spring context, but it was not taken up by TraceHttpAutoConfiguration.  My apologies for not getting it.  It seems like what I want to do, send the tracing information with HTTP access information to Elastic (via logback/logstash encoder), should be doable.

So I went ahead and added my own HttpTracing to the Spring context.  And as I suspected that one from TraceHttpAutoConfiguration is no longer in the Spring context and not being used... so my traces do not show up in Zipkin.
  @Bean
   HttpTracing httpTracing(Tracing tracing) {
       return HttpTracing.newBuilder(tracing)
               .serverParser(serverParser)
               .build();
   }

I take it back.  I was able to add my own HttpTracing and implement my own HttpServerParser.  Matt, thank you for the help!  And thank you for all the amazing code you wrote for this project.... we rely on it.

Ps next milestone you can just provide a bean for the parser instead of
overriding everything. This was also needed for GCP


Wont install on laravel 5.2

$ composer require echo-it/laravel-jsonapi
Using version ^2.4 for echo-it/laravel-jsonapi
./composer.json has been updated
> php artisan clear-compiled
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Conclusion: remove laravel/framework v5.2.10
    - Conclusion: don't install laravel/framework v5.2.10
    - echo-it/laravel-jsonapi 2.4.1 requires illuminate/pagination 5.1.* -> satisfiable by illuminate/pagination[v5.1.1, v5.1.13, v5.1.16, v5.1.2, v5.1.20, v5.1.22, v5.1.25, v5.1.28, v5.1.6, v5.1.8].
    - echo-it/laravel-jsonapi v2.4 requires illuminate/pagination 5.1.* -> satisfiable by illuminate/pagination[v5.1.1, v5.1.13, v5.1.16, v5.1.2, v5.1.20, v5.1.22, v5.1.25, v5.1.28, v5.1.6, v5.1.8].
    - echo-it/laravel-jsonapi v2.4.2 requires illuminate/pagination 5.1.* -> satisfiable by illuminate/pagination[v5.1.1, v5.1.13, v5.1.16, v5.1.2, v5.1.20, v5.1.22, v5.1.25, v5.1.28, v5.1.6, v5.1.8].
    - don't install illuminate/pagination v5.1.1|don't install laravel/framework v5.2.10
    - don't install illuminate/pagination v5.1.13|don't install laravel/framework v5.2.10
    - don't install illuminate/pagination v5.1.16|don't install laravel/framework v5.2.10
    - don't install illuminate/pagination v5.1.2|don't install laravel/framework v5.2.10
    - don't install illuminate/pagination v5.1.20|don't install laravel/framework v5.2.10
    - don't install illuminate/pagination v5.1.22|don't install laravel/framework v5.2.10
    - don't install illuminate/pagination v5.1.25|don't install laravel/framework v5.2.10
    - don't install illuminate/pagination v5.1.28|don't install laravel/framework v5.2.10
    - don't install illuminate/pagination v5.1.6|don't install laravel/framework v5.2.10
    - don't install illuminate/pagination v5.1.8|don't install laravel/framework v5.2.10
    - Installation request for laravel/framework == <IP_ADDRESS> -> satisfiable by laravel/framework[v5.2.10].
    - Installation request for echo-it/laravel-jsonapi ^2.4 -> satisfiable by echo-it/laravel-jsonapi[2.4.1, v2.4, v2.4.2].

Installation failed, reverting ./composer.json to its original content.

Looks like you fixed this in dev-master, but haven't tagged a release.

+1

Using "echo-it/laravel-jsonapi": "dev-master" in composer.json worked for me.

I'm unfortunately not actively maintaining til lib anymore. Anyone want to take over the ownership?

@egeriis I will maintain the library. I made it compilant with jsonapi 1.0, but is not finished yet.

@IAmJulianAcosta Would you be o.k. with me transferring the ownership then?

FWIW http://openopensource.org/


File system event handling?

Do you plan to add (emulation of) file system events and event handlers?

only by implementing #25, if it permits, if you need that functionality please comment on that issue.

only by implementing #25, if it permits, if you need that functionality please comment on that issue.


Ros transforms fix

Fix for the default lidar frame, apparently it is "os_sensor" and not "os_lidar", which is pretty vital since "os_lidar" seems to be rotated 180* in the z axis, which screws much stuff up as you can imagine. Also forgot 1 more ROS transform, between base_link and lidar frame that we need to listen to

little bastard merge directly


Pass request body and headers to logger after method

Might want to rename headers to request_headers for consistency.  Response also has headers, so it's ambiguous.

Thank you both!


Roll engine 931d3cbbc250..f3ef31aa8c2c (1 commits)

https://github.com/flutter/engine/compare/931d3cbbc250...f3ef31aa8c2c
git log 931d3cbbc250..f3ef31aa8c2c --no-merges --oneline
f3ef31aa8 Roll src/third_party/skia 46a5f6c28a34..637c06aec7b1 (1 commits) (flutter/engine#6246)
The AutoRoll server is located here: https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md
If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.

@rmistry @liyuqian : New roll has been created by https://autoroll.skia.org/r/flutter-engine-flutter-autoroll

Auto-roller completed checks. About to merge.