Getting started guide fails due to invalid url to download JDK

Hey,
Just tried out the Getting started guide (http://www.josso.org/getting-started.html).
It fails while running the "vagrant up --provider virtualbox" command. Output:
==> default: Running hooks in /etc/ca-certificates/update.d....done.
==> default: The command '/bin/sh -c DEBIAN_FRONTEND=noninteractive   apt-get update &&   apt-get install -y wget &&   wget -q --header "Cookie: oraclelicense=accept-securebackup-cookie" http://download.oracle.com/otn-pub/java/jdk/8u73-b02/jdk-8u73-linux-x64.tar.gz &&   mkdir -p /opt/jdk &&   tar -zxf jdk-8u73-linux-x64.tar.gz -C /opt/jdk &&   update-alternatives --install /usr/bin/java java /opt/jdk/jdk1.8.0_73/bin/java 100 &&   update-alternatives --install /usr/bin/javac javac /opt/jdk/jdk1.8.0_73/bin/javac 100' returned a non-zero code: 8
Trying out the url http://download.oracle.com/otn-pub/java/jdk/8u73-b02/jdk-8u73-linux-x64.tar.gz shows that the location no longer exist.
I managed to get josso-playground up'n running by cloning the repo, correcting the url in the "oracle-java8/Dockerfile" and then commenting out the following three lines in Vagrantfile:
#play_cmd << "git clone https://github.com/atricore/atricore-josso-playground.git; "
#play_cmd << "git -C atricore-josso-playground/oracle-java8 pull origin master; "
#play_cmd << "docker build -t atricore/josso:oracle-java8 atricore-josso-playground/oracle-java8; "
Then you can start up the box by running "vagrant up --provider virtualbox" from the directory.
Now, in order to fix this I would propose not just to change the url in "oracle-java8/Dockerfile" (thus relying on Oracle), but instead to rely on apt-get install for installing Java.
Question is also what the oracle-java8 docker container is used for... haven't been able to see why its needed, so another solution could be to just remove it completely.
Br.
Jakob Maaloe

Hi Jakob,
Thanks for reporting this issue. I'll have a look at that and follow up as soon as it's fixed.
Best,
Gianluca.

The oracle-java8 image is the base image of the JOSSO CE server one.  This is due to that JOSSO CE didn't play nice with early releases of OpenJDK, whereas it works fine now, so per your suggestion, I've removed this dependency.  By the way, this image was pulled and built "on the fly" due to Oracle licensing restrictions with Java.
Bear in mind that if you comment out the pull instruction for the playground project, no example configuration will be available for import. So, I'd strongly suggest you keep this unchanged.
Bottom line, the following changes/fixes have been applied :
a) Removed completely Oracle's Java dependency
b) Created Vagrant box and Docker images for latest JOSSO CE 2.4.3 and demo environment
c) Ported documentation to the latest JOSSO CE 2.4.3
d) Pushed revised vagrant box and docker images.
This kind of issues break the OOTB experience which is a showstopper for anyone kicking tires.
Thanks so much again for bringing this up ! 👍
Best,
Gianluca.


openiscsi: 2.0-873 -> 2.0-877

Motivation for this change
Update a package last updated 2 years ago.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[x] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Fits CONTRIBUTING.md.

Changelog:
https://github.com/open-iscsi/open-iscsi/blob/master/Changelog

@GrahamcOfBorg build openiscsi

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: openiscsi
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.

Unexpected error: command failed with exit code 1 on aarch64-linux (full log)
Attempted: openiscsi
Partial log (click to expand)
shrinking RPATHs of ELF executables and libraries in /nix/store/vpsn7vkig05sfaavrsk1dlnw3vj9d7b8-pkgconf-1.5.4
shrinking /nix/store/vpsn7vkig05sfaavrsk1dlnw3vj9d7b8-pkgconf-1.5.4/bin/pkgconf
shrinking /nix/store/vpsn7vkig05sfaavrsk1dlnw3vj9d7b8-pkgconf-1.5.4/lib/libpkgconf.so.3.0.0
gzipping man pages under /nix/store/vpsn7vkig05sfaavrsk1dlnw3vj9d7b8-pkgconf-1.5.4/share/man/
strip is /nix/store/6dpnd5aniypn8124mmy8f88s4mq2zl07-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/vpsn7vkig05sfaavrsk1dlnw3vj9d7b8-pkgconf-1.5.4/lib  /nix/store/vpsn7vkig05sfaavrsk1dlnw3vj9d7b8-pkgconf-1.5.4/bin
patching script interpreter paths in /nix/store/vpsn7vkig05sfaavrsk1dlnw3vj9d7b8-pkgconf-1.5.4
checking for references to /build in /nix/store/vpsn7vkig05sfaavrsk1dlnw3vj9d7b8-pkgconf-1.5.4...
cannot build derivation '/nix/store/xbh0ymznp04y6wk63abi2f1cqxzzq990-open-iscsi-2.0-877.drv': 1 dependencies couldn't be built
error: build of '/nix/store/xbh0ymznp04y6wk63abi2f1cqxzzq990-open-iscsi-2.0-877.drv' failed

Unexpected error: command failed with exit code 1 on x86_64-linux (full log)
Attempted: openiscsi
Partial log (click to expand)
trying https://github.com/open-iscsi/open-iscsi/archive/refs/tags/2.0-877.tar.gz
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   140    0   140    0     0    595      0 --:--:-- --:--:-- --:--:--   595
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
curl: (22) The requested URL returned error: 404 Not Found
error: cannot download source from any mirror
builder for '/nix/store/63c9f56j9di6nigl5kpmql90yscycjpx-source.drv' failed with exit code 1
cannot build derivation '/nix/store/k1kicj2dc70q1rw6qnnkf9vbcjiirvch-open-iscsi-2.0-877.drv': 1 dependencies couldn't be built
error: build of '/nix/store/k1kicj2dc70q1rw6qnnkf9vbcjiirvch-open-iscsi-2.0-877.drv' failed

So what's the state now? I lost track of the "requested changes". I squashed the commits.

@GrahamcOfBorg build openiscsi

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: openiscsi
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.

Unexpected error: command failed with exit code 1 on aarch64-linux (full log)
Attempted: openiscsi
Partial log (click to expand)

trying https://github.com/open-iscsi/open-iscsi/archive/2.0.877.tar.gz
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   130    0   130    0     0   1340      0 --:--:-- --:--:-- --:--:--  1340
100  590k    0  590k    0     0  2095k      0 --:--:-- --:--:-- --:--:-- 2095k
unpacking source archive /build/2.0.877.tar.gz
fixed-output derivation produced path '/nix/store/3xbg7574vw2g30xx8xwwrdadr045aizk-source' with sha256 hash '0v3dsrl34pdx0yl5jsanrpgg3vw466rl8k81hkshgq3a5mq5qhf6' instead of the expected hash '0icwgcgldildb3blib850f7kll1knyxdylk2ic33rcddr60rxib2'
cannot build derivation '/nix/store/x9f5mlpkmsbgf4vr6i0ig87q8zj32s46-open-iscsi-2.0.877.drv': 1 dependencies couldn't be built
error: build of '/nix/store/x9f5mlpkmsbgf4vr6i0ig87q8zj32s46-open-iscsi-2.0.877.drv' failed

Unexpected error: command failed with exit code 1 on x86_64-linux (full log)
Attempted: openiscsi
Partial log (click to expand)

trying https://github.com/open-iscsi/open-iscsi/archive/2.0.877.tar.gz
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   130    0   130    0     0    550      0 --:--:-- --:--:-- --:--:--   548
100  590k    0  590k    0     0   602k      0 --:--:-- --:--:-- --:--:--  602k
unpacking source archive /build/2.0.877.tar.gz
fixed-output derivation produced path '/nix/store/3xbg7574vw2g30xx8xwwrdadr045aizk-source' with sha256 hash '0v3dsrl34pdx0yl5jsanrpgg3vw466rl8k81hkshgq3a5mq5qhf6' instead of the expected hash '0icwgcgldildb3blib850f7kll1knyxdylk2ic33rcddr60rxib2'
cannot build derivation '/nix/store/insds95494j3i6chf1ihvwan2d438487-open-iscsi-2.0.877.drv': 1 dependencies couldn't be built
error: build of '/nix/store/insds95494j3i6chf1ihvwan2d438487-open-iscsi-2.0.877.drv' failed

@zaninime The changes looks good now. I just seems that the hash of the source is wrong.

Unfortunately 0ec3a81158ef32da0a2866f8e2cc2ab02f2e3662 is the first commit that builds and works fine, and it's just a couple of commits after 2.0-877, which are all build-system related. I subscribed to the repo, so I will get updates when they tag another release. I think it's still worth to merge this and have the updated package.

@GrahamcOfBorg build openiscsi

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: openiscsi
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: openiscsi
Partial log (click to expand)
/build/source/usr/iscsid.c:355: undefined reference to `sd_notifyf'
iscsid.o: In function `set_state_to_ready':
/build/source/usr/iscsid.c:347: undefined reference to `sd_notify'
/build/source/usr/iscsid.c:343: undefined reference to `sd_notify'
collect2: error: ld returned 1 exit status
make[1]: *** [Makefile:68: iscsid] Error 1
make[1]: Leaving directory '/build/source/usr'
make: *** [Makefile:53: user] Error 2
builder for '/nix/store/fhj9cy6a2g63l6qs1z3ra0il4g1in9br-open-iscsi-2.0.877.drv' failed with exit code 2
error: build of '/nix/store/fhj9cy6a2g63l6qs1z3ra0il4g1in9br-open-iscsi-2.0.877.drv' failed

Failure on x86_64-linux (full log)
Attempted: openiscsi
Partial log (click to expand)
/build/source/usr/iscsid.c:355: undefined reference to `sd_notifyf'
iscsid.o: In function `set_state_to_ready':
/build/source/usr/iscsid.c:347: undefined reference to `sd_notify'
/build/source/usr/iscsid.c:343: undefined reference to `sd_notify'
collect2: error: ld returned 1 exit status
make[1]: *** [Makefile:68: iscsid] Error 1
make[1]: Leaving directory '/build/source/usr'
make: *** [Makefile:53: user] Error 2
builder for '/nix/store/f9r3visgnn98n87i84bdns8rmc6zfyn0-open-iscsi-2.0.877.drv' failed with exit code 2
error: build of '/nix/store/f9r3visgnn98n87i84bdns8rmc6zfyn0-open-iscsi-2.0.877.drv' failed

@GrahamcOfBorg build openiscsi

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: openiscsi
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 x86_64-linux (full log)
Attempted: openiscsi
Partial log (click to expand)
strip is /nix/store/rpbg8gmqxhz8g61p1plz5d2srs84pvmv-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/ch6cvnvk80bqhnf08fp5yjd3g16xbirv-open-iscsi-2.0.877/lib  /nix/store/ch6cvnvk80bqhnf08fp5yjd3g16xbirv-open-iscsi-2.0.877/sbin
patching script interpreter paths in /nix/store/ch6cvnvk80bqhnf08fp5yjd3g16xbirv-open-iscsi-2.0.877
/nix/store/ch6cvnvk80bqhnf08fp5yjd3g16xbirv-open-iscsi-2.0.877/sbin/iscsi_offload: interpreter directive changed from "/bin/bash" to "/nix/store/n2hjbpkf4c0m48945ivxs3lmsczzw2rg-bash-4.4-p23/bin/bash"
/nix/store/ch6cvnvk80bqhnf08fp5yjd3g16xbirv-open-iscsi-2.0.877/sbin/iscsi_discovery: interpreter directive changed from "/bin/bash" to "/nix/store/n2hjbpkf4c0m48945ivxs3lmsczzw2rg-bash-4.4-p23/bin/bash"
/nix/store/ch6cvnvk80bqhnf08fp5yjd3g16xbirv-open-iscsi-2.0.877/sbin/iscsi-gen-initiatorname: interpreter directive changed from "/bin/bash" to "/nix/store/n2hjbpkf4c0m48945ivxs3lmsczzw2rg-bash-4.4-p23/bin/bash"
/nix/store/ch6cvnvk80bqhnf08fp5yjd3g16xbirv-open-iscsi-2.0.877/sbin/iscsi_fw_login: interpreter directive changed from "/bin/bash" to "/nix/store/n2hjbpkf4c0m48945ivxs3lmsczzw2rg-bash-4.4-p23/bin/bash"
checking for references to /build in /nix/store/ch6cvnvk80bqhnf08fp5yjd3g16xbirv-open-iscsi-2.0.877...
moving /nix/store/ch6cvnvk80bqhnf08fp5yjd3g16xbirv-open-iscsi-2.0.877/sbin/* to /nix/store/ch6cvnvk80bqhnf08fp5yjd3g16xbirv-open-iscsi-2.0.877/bin
/nix/store/ch6cvnvk80bqhnf08fp5yjd3g16xbirv-open-iscsi-2.0.877

Success on aarch64-linux (full log)
Attempted: openiscsi
Partial log (click to expand)
strip is /nix/store/6dpnd5aniypn8124mmy8f88s4mq2zl07-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/ni3jgzkzlwlrrx9kll9h7z7xbr20m6sc-open-iscsi-2.0.877/lib  /nix/store/ni3jgzkzlwlrrx9kll9h7z7xbr20m6sc-open-iscsi-2.0.877/sbin
patching script interpreter paths in /nix/store/ni3jgzkzlwlrrx9kll9h7z7xbr20m6sc-open-iscsi-2.0.877
/nix/store/ni3jgzkzlwlrrx9kll9h7z7xbr20m6sc-open-iscsi-2.0.877/sbin/iscsi-gen-initiatorname: interpreter directive changed from "/bin/bash" to "/nix/store/n1kfdl37qpzh3xn6klbym1ay6xpxvmw1-bash-4.4-p23/bin/bash"
/nix/store/ni3jgzkzlwlrrx9kll9h7z7xbr20m6sc-open-iscsi-2.0.877/sbin/iscsi_offload: interpreter directive changed from "/bin/bash" to "/nix/store/n1kfdl37qpzh3xn6klbym1ay6xpxvmw1-bash-4.4-p23/bin/bash"
/nix/store/ni3jgzkzlwlrrx9kll9h7z7xbr20m6sc-open-iscsi-2.0.877/sbin/iscsi_fw_login: interpreter directive changed from "/bin/bash" to "/nix/store/n1kfdl37qpzh3xn6klbym1ay6xpxvmw1-bash-4.4-p23/bin/bash"
/nix/store/ni3jgzkzlwlrrx9kll9h7z7xbr20m6sc-open-iscsi-2.0.877/sbin/iscsi_discovery: interpreter directive changed from "/bin/bash" to "/nix/store/n1kfdl37qpzh3xn6klbym1ay6xpxvmw1-bash-4.4-p23/bin/bash"
checking for references to /build in /nix/store/ni3jgzkzlwlrrx9kll9h7z7xbr20m6sc-open-iscsi-2.0.877...
moving /nix/store/ni3jgzkzlwlrrx9kll9h7z7xbr20m6sc-open-iscsi-2.0.877/sbin/* to /nix/store/ni3jgzkzlwlrrx9kll9h7z7xbr20m6sc-open-iscsi-2.0.877/bin
/nix/store/ni3jgzkzlwlrrx9kll9h7z7xbr20m6sc-open-iscsi-2.0.877

Thanks for cleaning up the derivation!


Update to official HA Goodwe integration

First of all, thanks for great integration.
Are there any plans to update the official HA Goodwe integration, esp. with the new "Eco charge mode" and "Eco discharge mode"?
I recently saw a facebook discussion (in Czech HomeAssistant users group) where people got confused about not having those two new states while others have them.
Or should I ask on Home Assistant side in the issues there?

It would be greate if HA Goodwe integration were upgraded to latest version in HACS

Well, the Eco charge/discharge are still considered experimental, there are problems with it on ES inverters, so it will remain in HACS only for a while.

Cool, thanks for letting us know. I'll switch to HACS for now.


How to implement in class component

Any tutorial how to implement it in class component? I'm already write lot of my codes with class component and its kinda hard to implement this while this code written in hooks

Hi, you will need to do something like:

useRef variable to this.xxx
useState to normal state.
useEffect to componentDidMount and don't forget to remove the listener in componentWillUnmount

Hi, you will need to do something like:

useRef variable to this.xxx
useState to normal state.
useEffect to componentDidMount and don't forget to remove the listener in componentWillUnmount

thank you 👍


[DISCUSS] Swap tailwindcss from NPM to pytailwindcss to remove the need for package.json and package-lock.json

Currently the build steps for web are to run tailwindcss to compile tailwind from the template.
There is a package pytailwindcss that can compile tailwind via python.

I wouldn't oppose this change, the main benefit being ease of development, especially for new contributors. Tailwind's own announcement about the CLI says

If on the other hand you’re working on a project where you don’t otherwise need Node.js or npm, the standalone build can be a great choice. If Tailwind was the only reason you had a package.json file, this is probably going to feel like a nicer solution.

Which seems like it fits our use case pretty well.
(Note that this is not actually Python, it's just a Python wrapper that helps install the CLI binary. This doesn't change its usefulness, just pointing out that it isn't a Tailwind reimplementation or anything like that.)

Resolved in #90


404 Handler

Fixes #25
Test URLs:

Before: https://main--servicenow--hlxsites.hlx.live/blogs
After: https://issue25--servicenow--hlxsites.hlx.live/blogs

if the PSI checks go against the actual 404, they check the redirection target and that's failing, which is why the test URLs point somewhere else


Tensor conversion improvements

New half::f16 half-precision floating point support. It can be enabled by additional half-precision feature.
Reduce the usage of macros and use traits instead.
Add conversions from both owned and borrowed types impl From<T> for Tensor and impl From<&T> for Tensor
New Tensor::{from_shape_fn, from_shape_slice} to create tensors with ease.

The PR is based on #196. It should be blocked until the changes of #196 is final.

I realized the refactoring work is non-trivial. I'm WIP on re-writing the conversion again based on master branch. There are several design decision to make and I need others' options to make it clear.

Does From<Tensor> for Vec<_> assume the tensor is one-dimensional? If yes, times to refactor tests. If not, it's inconsistent with the semantic of From<Tensor> for Vec<Vec<...>> and it's better to move to Tensor::to_shape_vec().
Some conversions, likei64::from(non_scalar_tensor), could panic. Suppose we implement TryFrom instead? If yes, the refactoring is going. If not, how could we provide an alternative interface that does not kill my program? Note that From<_> and TryFrom<_> will conflict with each other.
i64::from(tensor)  implicitly converts a non-i64 tensor to an integer. It incurs undesired side-effect if the precision of tensor is critical (such as loss). I observed such errors in several tests. Perhaps we can make is strict.

Apart from issues above, some improvements are already done.

Given we have tch::kind::T, some conversions can be defined using generics instead of macros. From<Tensor> for $primitive can be done this way.
The conversion of ndarray::Array can be more generic, and is not restricted to ArrayN.

I pushed new commits and the CI passes. It's ready for review.

Sorry this PR tweaked lots of things in various ways so I never got around reviewing it. If you still have bits that you feel would be useful, please create an issue first with a scope as limited as possible so that it can be discussed there first.


Calculate the actual delay based on the message timestamp

Delayed messages are counted as executed so are counted in concurrency limit, so backlog grows.
With this we don't delay messages statically, but instead calculate the actual delay based on when the message was created, not dequeued.
cc @wikimedia/services

Coverage decreased (-0.8%) to 92.824% when pulling 52a000debf41d82796def364df505ce57b97357f on Pchelolo:retry_delay into b64e88362335feb8c40a0dee977104ba865a61aa on wikimedia:master.

Coverage decreased (-0.8%) to 92.824% when pulling 52a000debf41d82796def364df505ce57b97357f on Pchelolo:retry_delay into b64e88362335feb8c40a0dee977104ba865a61aa on wikimedia:master.


Fix HBS template to comply with Ghost 1.x rules

i hope this is not a duplicate pull request, as you've closed the previous pull request about the same thing

Closed in favor of #187


Added formats to MeshVertexAttribute constant's docstrings

Objective
Fixes #11653
Solution

Just added the formats to the docstring, I played around with having the format appear in the type somehow so that it didn't need to be written manually in the docstring but it ended up being more trouble than it was worth.

There seems to be a failing build but I don't think it is related, it seems to be because of the same thing causing #11702


180-Added sql ingestion for census tract to ward/cluster weight mapping

Part 1 for https://github.com/codefordc/housing-insights/issues/180 - ingestion of census tract to ward and cluster population weights.

Thank you for feedback and merging!


Training Code

Really Great Work!
I wonder if you'll make training scripts available or not. If yes, are there any plans about when you'll make it available?
Thanks

We currently do not plan to make the training scripts available, although you can base training off of the implementation in guided-diffusion. The main part that is changed is data loading, which you will need to setup yourself with your own text-image dataset. We currently don't plan to release our dataset or data loader for this project.

That's fine and your right as the intellectual property creators, but if you're not going to be open, don't call yourselves "Open."

We currently do not plan to make the training scripts available, although you can base training off of the implementation in guided-diffusion. The main part that is changed is data loading, which you will need to setup yourself with your own text-image dataset. We currently don't plan to release our dataset or data loader for this project.

Hey @unixpickle,
Are the data loading strategies well defined in paper so that I might be able to reproduce it?
Best,
Rakesh

We currently do not plan to make the training scripts available, although you can base training off of the implementation in guided-diffusion. The main part that is changed is data loading, which you will need to setup yourself with your own text-image dataset. We currently don't plan to release our dataset or data loader for this project.

May I ask for the training code for inpainting? Or can you provide me some hints for implementing a training script for inpainting?


Bug: adding colors to cells breaks cell width sync between header & body

I wanted to have colored text in cells using chalk, which adds this type of unicode chars: \x1B[32m<text>\x1B[39m. The coloring works alright, but it breaks the column width sync between headers & body:
Sample output when all the words in the first column are colored green with chalk.green('text'):
+----------------------+--------+---------+
|       Package        | Compat | Version |
+----------------------+--------+---------+
| coveralls  | >=6    | 3.1.1   |
| mocha      | N/A    | N/A     |
| nyc        | >=8.9  | 15.1.0  |
| release-it | >=10   | 14.11.8 |
+----------------------+--------+---------+

Should be fixed in 0.7.0. Had to replace standard string handling functions... :)
I still need to add more unit tests to make sure it doesn't break anything when word wrapping or truncating for colouring cases.


Stuck on Waiting for download to start

Looks like several people (including me) have an issue where the installer is stuck on waiting for download. I've tried running as admin, fresh installs, and restarting steam with no change

same by me and many other

Chiming in with the same issue

Fixed by #9


drivers: hci: stm32_ipm: Add possibility to work on LSI

Allow to work on LSI of LSE failed to start (or absent)
Also adding compile time switch for LSE, this nucleo_wb55 board will be extended with
select CLOCK_STM32_LSE

Still needs to update the message for first commit, otherwise LGTM

D'oh, Done


full link ID   based on TLS ?

In order to achieve full link ID tracking, based on TLS in go, in order to avoid function calls need to pass the context param .In the same coroutine, it is OK to get the link ID according to the coroutine ID, but how can one coroutine start another coroutine without obvious the passing link ID?

I guess you are asking for a feature like "goroutine ID inherence", which requires a child goroutine knows the information of its parent. It's not possible to implement it right now from my understanding.
It's recommended to use Context explicitly instead of using such hack way to implement full link ID tracking. The hack way is so fragile.


How can i realize reconstruction

hello, i want to know that how i can put your correspondences into colmap, thanks

hello, i want to know that how i can put your correspondences into colmap, thanks

COLMAP requires steady keypoints across images, I'd use the code example in guided matching to obtain matches with consistent keypoints.

Thanks! But I still have a problem, how to speed up the matching process, it is too slow, despite tuning the relevant parameters.

Yes, currently we are also working on the speed problem, but still in progress.

Sorry to bother you again, how did you get your.npy file

Which .npy do you mean?
If you are referring to the camera poses, we obtained it from the ground truth of MegaDepth dataset.


Software Verification & Validation

@rhpvorderman er staat nog een change request open. die had ik al wel geincludeerd.

One or two lines about automated tests do not need a report as stated by @hwmvandeutekom and I think it is good to go.

zie regel 28: In case of automated testing, there must be a procedure of how the results are checked. I.e. a merge request is not possible when automated testing fails, or registering the passing of all automated testing among other verification results.

Looks good to me.


How to get the selected value?

How can I get the selected value?
I have tried some way:
    var comboTree1;
    jQuery(document).ready(function($) {
        comboTree1 = $('#justAnInputBox').comboTree({
            source : SampleJSONData,
            isMultiple: true,
            cascadeSelect: true,
            collapse: true,
            selectableLastNode: true,
            selected: selectedItem
        });
        var selectedTitles = comboTree1.getSelectedItemsTitle();
        console.log('selectedTitles: ' , selectedTitles);
        var selectedIds = comboTree1.getSelectedItemsId();
        console.log('selectedIds: ' , selectedIds);
    });

    Getting error as:
    jQuery.Deferred exception: comboTree1.getSelectedItemsTitle is not a function TypeError: comboTree1.getSelectedItemsTitle is not a function

Is there any way to get the selected value/ids ?

Also tried this according to docs. But getting similar errors:
comboTree1 = $('#justAnInputBox').comboTree({
source : SampleJSONData,
isMultiple: true,
cascadeSelect: true,
selected: ['0']
});
// Array, One title/id, or False value return
var selectedTitles = comboTree1.getSelectedItemsTitle();
var selectedIds = comboTree1.getSelectedItemsId();
// To remove plugin
comboTree1.destroy();

THANK YOU. Docs are definitely lacking on this part.

Thank you for explaining this. It could not work it out by myself from the documentation. I was trying to do
comboTree2.onChange(function() { updatecontent( alert("Yeaaahhh maaannn"); ) });
which was not working as desired.


Error message contains EUII (login_hint) which compromises Microsoft Privacy Policy

Please follow the issue template below. Failure to do so will result in a delay in answering your question.

Library

[x]<EMAIL_ADDRESS>
Description
We have noticed that in one particular error message, the login_hint is present and that compromises the privacy policy, please take a look into it and see what fix can be done in MSAL.js for that.
Error msg: "URL navigated to is https://login.microsoftonline.com/common/oauth2/v2.0/authorize?response_type=id_token token&scope=394866fc-eedb-4f01-8536-3ff84b16be2a%2F.default%20openid%20profile&client_id=b23dd4db-9142-4734-867f-3577f640ad0c&redirect_uri=https%3A%2F%2Fword-edit.officeapps.live.com%2Fwe%2FWacOAuth.html&state=f382f9de-8979-4d06-9ed8-70b12e2c783d&nonce=b303cd2b-a76d-4484-9e6d-68ee4d2fbe4e&client_info=1&x-client-SKU=MSAL.JS&x-client-Ver=1.2.1&login_hint=&client-request-id=53f30bd6-7f70-48e8-9c1c-00c01f459fe9&prompt=none&response_mode=fragment, Token renewal operation failed due to timeout."
Security
This issue is Privacy related, should have high priority.
Reproduction steps

This error message is tied to timeout.

Expected behavior
In the error message, login_hint or any other value contains user identifier should be removed.

@jasonnutter Probably you are already taking care of the extra check here, but I want to confirm that as part of this bug fix, we are also looking at other possible places where a login_hint or any other EUII can be in an unexpected presence. Thank you!

@muying-cui Yes, a couple other messages have been adjusted.


Incorrect port on compose and Docker run docs

Bug Report
Description
Bug Summary:
You are forwarding the wrong port on compose and docker run i the docs. For example, in your docs you have:
docker run -d -p 3000:8080 -v ollama:/root/.ollama -v open-webui:/app/backend/data --name open-webui --restart always ghcr.io/open-webui/open-webui:ollama

The correct command should be:
docker run -d -p 8080:8080 -v ollama:/root/.ollama -v open-webui:/app/backend/data --name open-webui --restart always ghcr.io/open-webui/open-webui:ollama

Perhaps you changed the uvicorn port in Docker at a certain point. Anyhow updating documentation and Docker compose should fix this. Alternatively you could configure uvicorn to port 3000.

No, the docs are correct. I'm afraid it's you who is mistaken. Please refer to Docker documentation regarding "Published Ports".


Release v2.0.0

What this PR does / why we need it:
Contains the Readme, package.json and related files with respect to the release version 2.0.0
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?

Additional documentation, usage docs, etc.:

We can hold this PR till all the commits are merged.


do not remove NETAVARK_FORWARD rule on teardown

When we have two containers on different networks running and stop one
of them we still need the NETAVARK_FORWARD rule in the FORWARD chain.
If this rule is removed the containers lose connections if the default
FORWARD policy is DROP.
test: add iptables rule check
Add tests to check the exact iptables rules.

@baude @mheon PTAL

LGTM

/lgtm


on Credentials adding modal, send user to create infra first before letting user to create credential

Otherwise - user types in all the data but then is blocked by the need for the infra at the form validation time, and then needs to restart the process from scratch.

... subtype "[registry]" is a bit too programmatic error message. Change it to something more UI-friendly, e.g. ... type Registry.


Changed openblas build to ILP64

Issue
OpenBLAS uses 32-bit integers by default . But DAAL_INT is 64-bit integer type. This causes errors during LAPACK calls, where the argument is expected to be a pointer to 32-bit integer, but a pointer to 64-bit integer is given. This causes many examples that use LAPACK to fail.
Fix
Build openBLAS with ILP64 interface by adding BINARY=64 and INTERFACE64=1 while building. An option to switch ILP64 interface has been added to the openblas build script (by default ILP64 interface is built).
This change fixes the following examples which have been removed from the exclude list.

out_detect_mult_dense_batch
pca_cor_dense_batch
pca_cor_dense_distr
pca_cor_dense_online
qr_dense_batch
qr_dense_distr
qr_dense_online
svd_dense_batch

Changes were tested on Graviton3 (openblas+gcc build).

/intelci: run

This PR requires rebuilding openblas. Examples will fail if the cached version of openblas is used.

This PR requires rebuilding openblas. Examples will fail if the cached version of openblas is used.

You can create new input to the cache key and include LP mode state - https://github.com/oneapi-src/oneDAL/blob/main/.ci/pipeline/ci.yml#L117

@keeranroth  - FYI

@napetrov thanks for the heads up. This is a great catch, and good to see that so many tests are able to be cleared as well (from looking at the exclude lists being cleaned). CI will also need to have the key updated in the cached builds of OpenBLAS, as these will still pull down the 32-bit builds. That's likely the cause of the errors in CI pipelines

Looks like the QEMU package has moved again. Can you set
qemu_deb=qemu-user-static_8.2.1+ds-1~bpo12+1_amd64.deb
in the script .ci/env/apt.sh? That has been up there since February, and should be good enough for us to use. Not sure why 8.2.3 should have vanished ¯_(ツ)_/¯

/intelci: run


Flexbox Helper Document Fix

The docs read to pass in any horizontal value with an example "bottom", but the function is requiring a vertical alignment (so 'bottom' would work but 'left, center, right' would not.)
Referencing https://github.com/zurb/foundation-sites/blob/develop/scss/util/_flex.scss#L55

Thank you @lesliedoherty


chore(deps): upgrade angular beta.17 -> rc.4

ƪ(΄◞ิ۝◟ิ‵)ʃ
upgraaaaade! this one was quite a doozy. this currently isnt the latest rc (rc.6 came out 8/31) but there was a huuuge change in structure from rc.4 to rc.5 so i thought id take things slow
changes include (for documentation purposes):

getting rid of the angular2 module in favor of @angular/*
add<EMAIL_ADDRESS>to move to the new way forms are being handled

add disableDeprecatedForms and provideForms to boot.ts
add name attributes to the any input element we had ngModel on

ngSwitchWhen ➡ ngSwitchCase
upgrade angulartics2 from v1.0.10 to v1.1.5 though i still dont think page view tracking works, only event tracking. i think when we stop using the deprecated router, it will work again, but thatll be coming in another pr
pass around an html sanitizer so that we dont get a bunch of dumb warnings in the console. this was caused because we are using [innerHTML]. i think we can actually get rid of all this stuff when we upgrade to rc.5 because of this commit but well see
upgrade the polyfill url from beta.12 to beta.17. i forgot to do this in the last upgrade pr but it looks like there arent hosted polyfill files for the rcs. i think we can use this starter repo to correctly load the polyfills/dependencies without the need of angular2-polyfills.js

before moving on to the other rcs, i wanna move to the new router cause i think the old deprecated one doesnt work with all the new stuff
@ami same as before, all you need to do is checkout the branch, rm -rf node_modules, npm i, npm start, and see if all of the pages/functionality still works!

LGTM


[Help] Set headers row

Hey!
I check the documentation to find if there is an option to define row number of headers for the readFile method, and can't find one.
For example, I have a file with the first two rows empty (or include some unused data), and the 3rd row includes the headers.
I want to be able to:
XLSX.readFile(file, { header: 3 }

Is there a way to do so?
Thanks!

Will want to use the utils function XLSX.utils.sheet_to_json
The following should get the output you are looking for:
let sheet = workbook.Sheets["SheetWithData"]
let read_data = XLSX.utils.sheet_to_json(sheet, {header: 3})

Thanks again @harmon25 !
@eyalcohen4 there are two ways to do it: at the function level (like what @harmon25 showed) or at the worksheet level.
You can directly modify the worksheet range:
var range = XLSX.utils.decode_range(worksheet['!ref']);
range.s.r = 2; // or XLSX.utils.decode_row("3");
worksheet['!ref'] = XLSX.utils.encode_range(range);

Ok! Tnx a lot


Make Cursor compatible with Collection[Dict[str, Any]]

from pymongo.cursor import Cursor
from typing import Collection, Dict, Any

class MyCursor(Collection[Dict[str, Any]], Cursor):  # error: Definition of "__iter__" in base class "Iterable" is incompatible with definition in base class "Cursor"  [misc]
  ...

This is because Cursor.__iter__ returns a Cursor which isn't an Iterator[...] (and therefore is incompatible).

Thanks for reporting this! I would expect mypy to consider Cursor an Iterator because it has the appropriate __next__ and __iter__ methods which should satisfy the iterator protocol: https://docs.python.org/3/library/stdtypes.html#iterator.iter
This is an easy fix though. We'll need to change Cursor/CommandCursor like this:
-    def __iter__(self) -> Cursor: ...
+    def __iter__(self) -> Iterator[_DocumentOut]: ...

Yes I was checking the source in cursor.py and I came to the same conclusion, but I was surprised that Cursor doesn't explicitely inherit from Sequence/Collection/Iterator¹ so these issues could be detected by directly running mypy on this project (I don't know how you're testing pymongo-stubs).
Also, I noticed _DocumentOut is an alias for Any, when it should really be something like
JSON = Union[Dict[str, "JSON"], List["JSON"], str, int, float, bool, None]

although that's not supported yet (I guess you already know that), but I believe we could make a compromise and type it at least as Dict[str, Any]. Unless I'm missing something?
¹: Sequence makes the most sense but the signature for .count() doesn't seem to be compatible

We don't directly inherit from Iterator because pymongo-stubs uses structural subtyping not nominal subtyping: https://docs.python.org/3/library/typing.html#nominal-vs-structural-subtyping
The _DocumentOut=Any issue is described in https://jira.mongodb.org/browse/PYTHON-2427. We could change it to MutableMaping[str, Any] but that would be incorrect because clients can be configured to return RawBSONDocument which is immutable. Please let me know your thoughts.

I wasn't aware that you could configure clients to return raw BSON. I understand the Any now. Okay then I guess it's not worth the trouble (and can't be considered part of the current issue anyway).
One would have to make the CodecOptions, MongoClient, Database, et al. be generic over document_class ...

One would have to make the CodecOptions, MongoClient, Database, et al. be generic over document_class ...

Yes, unfortunately I was unable to implement the "generic over document_class" idea. I don't remember exactly what the blocker was, maybe something about namedtuple+generics. Typing/mypy support is ever improving so it may be more feasible now. It could be more feasible to make Collection generic but default dict (the most common document_class). However as far as I know typing does not allow for default types for generics, ie. if the generic type is omitted it always becomes Any.
Going back to the Cursor __iter__ issue, would you like to work on a PR to fix the bug? We'll need to change both Cursor and CommandCursor like this:
-    def __iter__(self) -> Cursor: ...
+    def __iter__(self) -> Iterator[_DocumentOut]: ...

I'm going to close this since I think the original issue was either a bug in mypy itself or a bug in the app code. It would be great if you could report the issue to mypy. I opened https://github.com/mongodb-labs/pymongo-stubs/issues/15 to investigate if there is a better alternative for _DocumentOut that we can use.


Incorrect integer token

When my test file had 1.0 it created a Token object with the value 1.0 and not 3 separate Tokens.
E.g.

RecievedShould be

integer Token 1.0
integer Token 1

---terminator Token .

---integer Token 0

 Issue: 1.0 was called an int token


What does Table 1 (t=1 and t=0.9) refer to in the paper? It doesn't seem to be mentioned in the text.

(t=1 and t=0.9) ,Which hyperparameter do these two experimental configurations refer to?

This is referring to the temperature parameter :)

This is referring to the temperature parameter :)

Tanks, i can see the description(temperature), but i don't know what it means. I didn't find this hyperparameter in the code.

You'll see this defined under H.temp for the hyperparmeter objects a lot of the time! For example here:
https://github.com/samb-t/unleashing-transformers/blob/master/hparams/defaults/sampler_defaults.py#L15
Searching for ".temp" in the codebase should show all the places temperature is used.

Thank you very much! Finally, I'd like to ask you, is there any research after this work?

Not from myself, but you can see some of Sam's great work here and citations for the Unleashing Transformers paper here that should give you some ideas for other research to explore 😀

Thanks. That's really helpful！

------------------ 原始邮件 ------------------
发件人: "Peter @.>;
发送时间: 2024年12月20日(星期五) 下午5:51
收件人: @.>;
抄送: @.>; @.>;
主题: Re: [samb-t/unleashing-transformers] What does Table 1 (t=1 and t=0.9) refer to in the paper? It doesn't seem to be mentioned in the text. (Issue #22)
Not from myself, but you can see some of Sam's great work here and citations for the Unleashing Transformers paper here that should give you some ideas for other research to explore 😀
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>


If no structures are given, do not allow structural aligners

Description of feature
Like 3d coffee (one needs to check the command line??)

maybe add in the handling of conflicting parameters

Not necessary, this is implicitily handled by the channels building. No channel will arrive as input to structural aligners if there are no structures.


Lightning 1.6 official

@jjhong922 I think we should get this in staged for 0.16.0. There will be more weird messages from this lightning release we will have to handle as we work on other 0.16.0 changes


Export data file for the graphs

It would be nice if the plotting process exported a data file (perhaps JSON) containing the all the datapoints created by the training run.  Ideally the plotting code could be used to replot the graphs from the data file.

@mikhailnikolaev @msdmkats are the data files that the graphs are plotted from currently uploaded to the web server?

@mikhailnikolaev @msdmkats are the data files that the graphs are plotted from currently uploaded to the web server?

No, they aren't. Actually, only PNG and HTML files (i.e. static and plotly graphs) are uploaded to the blob container in the current version. Moreover, the plotting process still doesn't collect all time info into the one JSON file.

@tomjaguarpaw, I think, we can close this issue due to the PR #183 and #186 (that are parts of #180). What do you think?

I would say either

Don't close this until JSON export functionality is added to the Azure CI and Batch job, or
Close this and create a new issue for the case above


Command line option '-v' should stand for --verbosity

This is the only application where -v stands for --version and not --verbosity.  I suggest to change this.
https://github.com/gammasim/gammasim-tools/blob/f95ea3c4a6b4170bdd08c46ca5b725dc91bfead1/applications/get_parameter.py#L35
Would also suggestion to replace version by simprod or something similar. I always expect that the software version is printed to the screen when using a --version command line argument.

Two updates here:

(important) correction: -V and --version are equivalent in general in python
new argparser provides the following functionality:

% python applications/derive_mirror_rnda.py -V
derive_mirror_rnda 0.1.0

--> Prints the application and the version number.
Unfortunately, the version number is hardwired in version.py.
Two tasks follow here:

[ ] propagate printing of application name plus version to all application (related to using the new argeparser, see issue #248)
[ ] find a better solution than hardwire version number

With the implementation of the new argparser in the branch CI-unittests, this has been consistently solved.
(issue will automatically close with merge request #266


the way I make it is like this

the way I make it is like this

in the _meta.json file, include
"--":  {
"type": "separator",
"title": "Name displayed"
}

for additional customization, check out the customization guide provided by the official documentation


Upgrade to s3 3.0.1.

Upgrade to s3 3.0.1.
closes #13

:tada: This PR is included in version 1.1.5 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Allow experimenting with live migration compression modes

What this PR does / why we need it:
This PR allows enabling and tuning compression parameters for live migration.
Using compression with live migration is one of the methods to reduce the network traffic during live migration.
However, it comes at an expense of other resources such as memory and CPU on the host.
Compression isn't a useful method in the general case as it depends on the application workload and the availability of resources on the node. Often, it will not be beneficial.
This PR will allow experimenting with live migration compression.
It exposes a set of tunables that can be set as annotations on the VMI object.
In the simple case, to enable compression, it's enough to set the LiveMigrationCompressionMethod
kubevirt.io/LiveMigrationCompressionMethod - accepts values mt for multi-threaded compression or xbzrle
kubevirt.io/LiveMigrationThreadedCompressionLevel - accepts values between 0 and 9. 0 is no compression, 1 is maximum speed and 9 is maximum compression.
kubevirt.io/LiveMigrationThreadedCompressionThreads - the number of compression threads for multithread compression
kubevirt.io/LiveMigrationThreadedDeCompressionThreads - the number of de-compression threads for multithread compression
kubevirt.io/LiveMigrationXBZRLECompressionCache - the size of page cache for xbzrle compression
allow enabling and tuning live migration compression modes

if someone were to use this, woudl they need to manually account for the memory overhead?

if someone were to use this, woudl they need to manually account for the memory overhead?

if someone were to use this, woudl they need to manually account for the memory overhead?

yes, in the case when xbzrle is being used. But depends on the application, so it has to be manually adjusted, or at least to keep in mind that there is an overhead.
With multithreaded compression, there is a large CPU overhead, not much memory.

if someone were to use this, woudl they need to manually account for the memory overhead?

yes, in the case when xbzrle is being used. But depends on the application, so it has to be manually adjusted, or at least to keep in mind that there is an overhead.
With multithreaded compression, there is a large CPU overhead, not much memory.

yes, in the case when xbzrle is being used. But depends on the application, so it has to be manually adjusted, or at least to keep in mind that there is an overhead.
With multithreaded compression, there is a large CPU overhead, not much memory.

Maybe we should reopen discussions about a general more flexible architecture on the libvirt/qemu side. On the long run we need an architecture where we can "outsource" specific actions to infra-cgroups. I find this more and more alarming the longer we don't have flexibility in that area.

yes, in the case when xbzrle is being used. But depends on the application, so it has to be manually adjusted, or at least to keep in mind that there is an overhead.
With multithreaded compression, there is a large CPU overhead, not much memory.

Maybe we should reopen discussions about a general more flexible architecture on the libvirt/qemu side. On the long run we need an architecture where we can "outsource" specific actions to infra-cgroups. I find this more and more alarming the longer we don't have flexibility in that area.

@vladikr It's nice idea to expose compression optimization.
I think that if we expect users to use such low level tuning parameters we should probably also expose some performance/utilization matrices that will allow them to understand/see the impact of the different compression methods.  For example: GB transferred, transfer time, etc..
Compression impacts only the memory transfer phase of live migration and therefore it's hard to measure this accurately from outside of KubeVirt as these timing events are exposed only through qemu/libvirt (the overall migration process as seen from outside also includes parts that are not related to data transfer, like NW setup, re-attachments of volumes, etc..)

@vladikr It's nice idea to expose compression optimization.
I think that if we expect users to use such low level tuning parameters we should probably also expose some performance/utilization matrices that will allow them to understand/see the impact of the different compression methods.  For example: GB transferred, transfer time, etc..
Compression impacts only the memory transfer phase of live migration and therefore it's hard to measure this accurately from outside of KubeVirt as these timing events are exposed only through qemu/libvirt (the overall migration process as seen from outside also includes parts that are not related to data transfer, like NW setup, re-attachments of volumes, etc..)

yes, in the case when xbzrle is being used. But depends on the application, so it has to be manually adjusted, or at least to keep in mind that there is an overhead.
With multithreaded compression, there is a large CPU overhead, not much memory.

Maybe we should reopen discussions about a general more flexible architecture on the libvirt/qemu side. On the long run we need an architecture where we can "outsource" specific actions to infra-cgroups. I find this more and more alarming the longer we don't have flexibility in that area.

We probably should. However, this PR is simply to allow experimenting with compression. This is not about adding this as a recommended migration option.
Running the migrations in our environment is obviously much different and more limiting than running it with just QEMU running feely on the node.
I guess that's the reason why I'm not adding this option to our CR, but just exposing this as a set of annotations.

yes, in the case when xbzrle is being used. But depends on the application, so it has to be manually adjusted, or at least to keep in mind that there is an overhead.
With multithreaded compression, there is a large CPU overhead, not much memory.

Maybe we should reopen discussions about a general more flexible architecture on the libvirt/qemu side. On the long run we need an architecture where we can "outsource" specific actions to infra-cgroups. I find this more and more alarming the longer we don't have flexibility in that area.

We probably should. However, this PR is simply to allow experimenting with compression. This is not about adding this as a recommended migration option.
Running the migrations in our environment is obviously much different and more limiting than running it with just QEMU running feely on the node.
I guess that's the reason why I'm not adding this option to our CR, but just exposing this as a set of annotations.

Maybe we should reopen discussions about a general more flexible architecture on the libvirt/qemu side. On the long run we need an architecture where we can "outsource" specific actions to infra-cgroups. I find this more and more alarming the longer we don't have flexibility in that area.

I agree something needs to be done here. Swap support might help memory overhead, but we still have the issue that our components eat cpu cycles that are shared with the VM which impacts performance.
I think that's an important discussion. It can probably happen independently of this pr though
@vladikr what's the goal of enabling compression.  Is this something we're wanting to have available to us primarily in order to benchmark? Can we use a dev branch for that or do we really need this logic merged?
One concern I have on this PR is that the tunings all exist on the VMI as annotations. If we merged something like this, normal users could enable this behavior on their VM/VMI. This seems more like an admin field similar to the other migration tunings we have on the kubevirt cr. What would you think about allowing these tunings to exist on the KubeVirt CR as annotations which then get applied globally?

Maybe we should reopen discussions about a general more flexible architecture on the libvirt/qemu side. On the long run we need an architecture where we can "outsource" specific actions to infra-cgroups. I find this more and more alarming the longer we don't have flexibility in that area.

I agree something needs to be done here. Swap support might help memory overhead, but we still have the issue that our components eat cpu cycles that are shared with the VM which impacts performance.
I think that's an important discussion. It can probably happen independently of this pr though
@vladikr what's the goal of enabling compression. Is this something we're wanting to have available to us primarily in order to benchmark? Can we use a dev branch for that or do we really need this logic merged?
One concern I have on this PR is that the tunings all exist on the VMI as annotations. If we merged something like this, normal users could enable this behavior on their VM/VMI. This seems more like an admin field similar to the other migration tunings we have on the kubevirt cr. What would you think about allowing these tunings to exist on the KubeVirt CR as annotations which then get applied globally?

@davidvossel I've added a feature gate to control the addition of the compression annotations.
As we spoke offline, enabling the compression makes sense mostly per application and not in the general case.

/retest

@vladikr is this something we want to revive?

/cc


Add vulkan pastel for mesa 22.0.3

Fix CtsDeqpTestCases in user build
Tests are filing with :
avc: denied { read } for name="vulkan.pastel.so"
Most of below tests are failing.
dEQP-VK.info.*
dEQP-VK.api.*
Tracked-On: OAM-103857
Signed-off-by: vdanix<EMAIL_ADDRESS>

Improper Affects version


JavaScript error when hitting enter on a search result.

Steps to reproduce:

Search for something.
Use the keyboard to select a result and hit enter.
Go back.
Hit enter
💥


英文 bold 字体难看

Similar to this issue:
https://github.com/valaxyjs/valaxy-theme-starter/issues/11
Tried to change the font according to https://github.com/valaxyjs/valaxy-theme-starter/commit/ce33d46b8161dd4d9be09047e34d8e284e73d487
But doesn't really work for English Bold

奇怪在linux上又显示正常

用的是这个：https://github.com/YunYouJun/valaxy/blob/ab0efd5dd7c5d15055d46788211c5842b67a36b9/packages/valaxy/client/styles/vars.scss#L19

能截图看下你那边效果吗？

It seems works well.


add set_use_delta_encoding() to Options

can you add a test using this option?

you can also ignore the security audit build issue for now. I'll work on fixing that separately

I'm not sure there's a reasonable unit test here since there's no error
feedback on the call. To know if Delta Encoding is enabled/disabled we
could create a db with some entries, flush them, and try to check the table
properties, but that rings a bit over the top for a single bit api wrapper
surface no?
On Tue, Dec 17, 2024, 10:34 Zaidoon Abd Al Hadi @.***>
wrote:

can you add a test using this option?
—
Reply to this email directly, view it on GitHub
https://github.com/zaidoon1/rust-rocksdb/pull/118#issuecomment-2549292437,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABDXHUURAFGFPL3XEKQOAFL2GBVCXAVCNFSM6AAAAABTXOWEEWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNBZGI4TENBTG4
.
You are receiving this because you authored the thread.Message ID:
@.***>

should be fine as is. If you have time to make a follow up pr to add some sort of test, that would be good.


Crash when offsetting

Hey - this library crashes for me when using the offsetting features. This seems to happen pretty consistently for any offsetting as far as I can tell.
Sandbox reproduction
As far as I can tell, this happens because the _normals array is constructed wrong. I'll submit a PR with a fix.

Would really appreciate merging @PontusHorn's fix, this is causing issues for us as well!

Sorry for the delay.  Update 1.2.4 contains the PR fix


Made the NorthwindInitializer thread friendly for unit testing

Hi Jason,
Another PR. This one addresses the issue when unit tests are running parallel and they are trying to use NorthwindInitializer. I removed all of the static parts but still kept the same style of initialization.
NorthwindInitializer.Initialize(context);

Behind the scenes, it creates a new instance of NorthwindInitializer and seeds the data from that local instance. This allows me to run unit tests in parallel. :)
I hope this small tweak might help you out in the future.

Thank you


Fix compilation with CDT develop

Change Description

Backport fix from develop. Without this, 1.9.x can't build with the develop version of CDT.
Deployment Changes

[ ] Deployment Changes

API Changes

[ ] API Changes

Documentation Additions

[ ] Documentation Additions

CI failure will be fixed once this CDT PR is merged https://github.com/EOSIO/eosio.cdt/pull/943
The last build on 1.7.x failed due to the timeout, so this CI pipeline was unable to pull a deb image to use for building the contracts.


[BEAM-5272] Randomize the reduced splits in BigtableIO so that multiple workers may not hit the same tablet server

Randomize the reduced splits in BigtableIO so that multiple workers may not hit the same tablet server.

Lang
SDK
Apex
Dataflow
Flink
Gearpump
Samza
Spark

Go

---
---
---
---
---
---

Java

Python

---

---
---
---

@chamikaramj, could you take a look? Thanks!

Thanks!


make slam3d packages use their actual ros package names for autoproj too

Currently autoproj doesn't install the dependencies from slam3d_ros2 package.xml file, maybe because they were overridden in the autobuild definition of the package.
With this patch we delete these dependencies and have autoproj read the deps from the package.xml file. This however leads to the problem that the slam3d dependency is not found, because it is declared as slam/slam3d, here. Therefore we have the packages here declare their actual package name to autoproj, and move them to the desired path in the workspace afterwards.
Not sure, if this is the cleanest approach to address this problem. Any alternatives that would achieve this better would be welcome.

I generally approve using the actual package-names instead of autoproj's checkout locations. But I cannot overview all implications of this and do not currently use any autoproj-ros2 workspace, so I cannot verify that this is working as intended.
Does autoproj need the package.xml? Because I was actually planning to remove it at least from slam3d, because colcon can get package-name and dependencies directly from CMake.

Currently autoproj does not use the package.xml for slam3d.
With this change it would read the deps from the package.xml for slam3d_ros2.

because colcon can get package-name and dependencies directly from CMake.

I'm not so sure about that. I think it still needs the package.xml to determine the build order.

I think it still needs the package.xml to determine the build order.

Or would autoproj generate one for an import package?

I added metapackage statements (aliases). Now the "old" autoproj package names should still work after renaming the packages.
If you delete the package.xml, we need to adjust the autobuild package type here, please ping us if you proceed to actually do this, that we can coordinate this.
Thanks for your feedback!

I'll try to address the requested changes tomorrow.


feat(semantic_tokens): link readonly variables to Constant

Forgot one :)

Can you use @constant instead?
And probably better to drop @lsp.mod.readonly?

hmm, I'm actually not sure about what you suggest to change. Can you show me a before/after of what you are trying to fix?
In typescript for example ReadOnly<string> is not the same as a constant

Can you use @constant instead?

Sure

And probably better to drop @lsp.mod.readonly?

Tbh, I'm not too super familiar with the new semantic_tokens but I found a gist that seems to give me a rough idea, agreeing with what you said:

Then, if you want everything which is read-only to be italic:
hi @lsp.mod.readonly gui=italic
If you only want parameters which are read-only to be italic:
hi @lsp.typemod.parameter.readonly gui=italic

So, I agree with removing the @lsp.mod.readonly as that seems to indicate any identifiers with modifiers that are readonly
The problem I want to fix (before and after):

I applied your suggestions now, let me know how ReadOnly<string> looks after that

I see what you mean. But the actual bug is actualy that the @variable doesn't have a proper fg. Check the Inspect output below:

Fixed it by setting the fg prop for @variable. Won't be orange now, but white as it should be. Otherwise emost things would have been orange in typescript :)

Wow! That fixed another bug I always wondered about but didn't bother to look into:

Before your fix, variables would just be highlighted to whatever was the capture above it if any (white by default usually as it wouldn't' be inside a capture, just a node). So before, var would be green like the string, which I didn't notice happen in other themes.
However...

Builtin vars such as console in js lose their highlights...tragically

console doesn't seem to get the proper semantic tokens it seems

console highlighting (treesitter) is now back, but so is that initial thing you wanted to fix.
tbh, I kinda like how that highlights. The const declaration is shown as a constant and using it variable shows it as variable. It's actually better that it's two colors. Makes it easier to read.

console highlighting (treesitter) is now back, but so is that initial thing you wanted to fix.
tbh, I kinda like how that highlights. The const declaration is shown as a constant and using it variable shows it as variable. It's actually better that it's two colors. Makes it easier to read.

In fact, I'd like your opinion here then.. as I introduced that separate highlighting change (I am not a big JS/TS user)
https://github.com/nvim-treesitter/nvim-treesitter/issues/4466


Plugins

Coverage remained the same at 100.0% when pulling ab8b3a2302498990e6fb46739dcbec80739ded79 on plugins into 8edffcf937e28b18e2f2bcde9dd2bd7828490025 on master.

Coverage remained the same at 100.0% when pulling ab8b3a2302498990e6fb46739dcbec80739ded79 on plugins into 8edffcf937e28b18e2f2bcde9dd2bd7828490025 on master.

Coverage remained the same at 100.0% when pulling 25f6a8a739d7dd24035a0762c6834432d41de981 on plugins into 8edffcf937e28b18e2f2bcde9dd2bd7828490025 on master.

Coverage remained the same at 100.0% when pulling 25f6a8a739d7dd24035a0762c6834432d41de981 on plugins into 8edffcf937e28b18e2f2bcde9dd2bd7828490025 on master.

Coverage decreased (-3.8%) to 96.214% when pulling 0f932f1e825ebf2e41cfb8f6788d9ff04e62fed8 on plugins into 8edffcf937e28b18e2f2bcde9dd2bd7828490025 on master.

Coverage decreased (-3.8%) to 96.214% when pulling 0f932f1e825ebf2e41cfb8f6788d9ff04e62fed8 on plugins into 8edffcf937e28b18e2f2bcde9dd2bd7828490025 on master.

Coverage decreased (-3.6%) to 96.362% when pulling 58f6731a0c939ec9be7194bcad37ecbdaa7c056c on plugins into 8edffcf937e28b18e2f2bcde9dd2bd7828490025 on master.

Coverage decreased (-3.6%) to 96.362% when pulling 58f6731a0c939ec9be7194bcad37ecbdaa7c056c on plugins into 8edffcf937e28b18e2f2bcde9dd2bd7828490025 on master.

Coverage decreased (-3.6%) to 96.362% when pulling 58f6731a0c939ec9be7194bcad37ecbdaa7c056c on plugins into 8edffcf937e28b18e2f2bcde9dd2bd7828490025 on master.

Coverage decreased (-3.6%) to 96.362% when pulling 7b6bd0e6cb2560b110766ec45f7f3b507c0a7e8c on plugins into 8edffcf937e28b18e2f2bcde9dd2bd7828490025 on master.

Coverage remained the same at 100.0% when pulling 852fdfb70cb0ecfc6baea050018cd602ae05e272 on plugins into 8edffcf937e28b18e2f2bcde9dd2bd7828490025 on master.

Coverage remained the same at 100.0% when pulling 852fdfb70cb0ecfc6baea050018cd602ae05e272 on plugins into 8edffcf937e28b18e2f2bcde9dd2bd7828490025 on master.

Coverage decreased (-1.5%) to 98.529% when pulling dbe40089a5219ea9631e4cd890f1a34a0be3047b on plugins into 8edffcf937e28b18e2f2bcde9dd2bd7828490025 on master.

Coverage decreased (-1.5%) to 98.529% when pulling 1bb713112aa8b0faadbc60e9a98b29cbade59da1 on plugins into 8edffcf937e28b18e2f2bcde9dd2bd7828490025 on master.


[WIP] Support Patch reboot info for advisories update

## Secure Coding Practices Checklist GitHub Link
- https://github.com/RedHatInsights/secure-coding-checklist

## Secure Coding Checklist
- [ ] Input Validation
- [ ] Output Encoding
- [ ] Authentication and Password Management
- [ ] Session Management
- [ ] Access Control
- [ ] Cryptographic Practices
- [ ] Error Handling and Logging
- [ ] Data Protection
- [ ] Communication Security
- [ ] System Configuration
- [ ] Database Security
- [ ] File Management
- [ ] Memory Management
- [ ] General Coding Practices

I've just tried to run tests in ci.


Devour Magic

Blizzard recently changed Devour Magic to not work on Anti Magic Shield. This creates a unique issue for Scourge in Legacies as they do not have access to any other form of Dispel magic.
Should we make a custom Devour Magic to circumvent this or put regular AOE dispel on a unit.

@Technopig1992 Yeah good call logging this. Do you think it can wait until a dev release or is it more on the urgent side?

@Technopig1992 Yeah good call logging this. Do you think it can wait until a dev release or is it more on the urgent side?

I would of thought it to be more urgent but there hasnt been much noise around it (perhaps they think we cant fix it).
I suppose it would depend on rough eta of the dev release (not exactly an easy one to answer)

Easily months for the Old God patch.
Ok, sounds like this is worth doing sooner rather than later so we'll do it into main. Note this is breaking the guideline as the fix is not going to be simple. But, high priority enough.

Okay cool sounds good. So we will be going the route of having a custom version of Devour Magic that works on AMS, sounds ideal to me.

On further investigation, fixing this is going to be somewhere in between extremely difficult and outright impossible.
We've decided to just accept the new behaviour for now. I'm updating the ticket to say the tooltip needs to be updated to reflect the new behaviour.

give scourge/fel horde/warsong normal dispel too?


Extensional maps

Replace the non-extensional and semi-maintained FMaps with the extensional and recent Std++ finite maps described here:

https://coq-workshop.gitlab.io/2023/abstracts/coq2023_finmap-stdpp.pdf
https://coq-workshop.gitlab.io/2023/slides/coq2023_krebbers.pdf

But I think we still diverged from the Ott definition, right? Maybe that should be a new issue, or what do you think?

Right now we do not diverge.
In the last commit on #18, abs_defs.v is directly generated from abs.ott and compiles.
 I think this would be better if Ott generated Notation instead of Definitions, but it is okay.


Is res50h pertained  on ImageNet?

In your experiment using res50h model, do you use image-net pretrained weights or randomly initialized weights?

How did you set the hyperparameter when training the baseline res50 model? I apply your method to SSD and it works. But in faster-rcnn case, I replace the vgg in your code with pretrained resnet50 and distill it with a resnet101 model on VOC2007 for 7 epoch, batch-size 1, 0.001 lr decay 1/10 at epoch 5. The final mAP of res50 model is 72.2 which is close to your paper. But without kd, the mAP can reach 74.0.


instructions on cufflinks page for building boost are incorrect

the boost build system for 1.5.5 (the version we need to use currently) doesn't recognize address_mode=# as a valid input

it needs a dash instead of an underscore, that rectified it.


Model Convergence Indicator

Hi,
During the training, how the number of epochs are getting decided ?
As I see, no part of training data has been reserved for evaluation during training of model. So, how can I be assured that model has converged during training ?

Correct. As in word2vec, there is no such validation set built into the training process, but indeed it would probably be useful to have this (as done when training language models, etc.). I guess that if the train set is large enough then you can look at the train error without too much of a risk of over-fitting.


Support for Topologyspread constraints for Serving/Eventing.

Problem
Currently only nodeSelector, tolerations, and affinity are supported by the Operator.
Exit Criteria
Added support for Topologyspread constraits for Serving/Eventing resources
Time Estimate (optional):
unknown
Additional context (optional)
I feel like having the possibility to spread out Serving/Eventing components by zone/region etc would be really helpful, unless there is a specific reason why this is not supported?

Additional information on Topology spread constraints https://github.com/kubernetes/enhancements/tree/master/keps/sig-scheduling/895-pod-topology-spread#impact-to-other-features

Knative Serving and Eventing CRs only work on a cluster based. One CR is only responsible for the installation of serving or eventing on one cluster.
Could you elaborate on how to install knative serving or eventing across different zones or regions? What is the use case?


Added cython to requirements.txt

:+1:

The requirements.txt file lists runtime requirements, so I don't think we should put Cython in there.

Maybe we can just mention it in the installation instructions

Should I add it to the conda create ... command?

Again, this should only be in the developer instructions.  Normal users would not need to compile anything if they install using pip.  But wherever we put the "Installation from source" instructions should contain this.

Got it, thanks!


cafile or who .npmrc ignored

Hei there.
We are using our own registry, which requires our own CA and intermediate certificates. That's why we configure our own registry and cafile in .npmrc.
I can run npm info <mypackage> and yarn info <mypackage> without issues, but if I run yarn-check, every package is giving the following error:

Registry error unable to verify the first certificate

I verified with --verbose if npm is actually using our registry, and it's alright.
yarn-check --debug doesn't give me any hint on the used registry. I'm concluding the tool is either ignoring .npmrc altogether, or the ̀ cafile`.

Have you checked if it works in the npm-check ?

Why would an alternative to npm use .npmrc? Try making a .yarnrc.

Well as far as I remember, in a minimal config mindset, you can use .npmrc with yarn. If that's the case, the config file should be respected in it's entirety, otherwise that feature is broken.
I'm sorry to not being able to reproduce or help resolving the issue, I don't work on that project any more.


dahsbaord not working for My bot

it only works for your bot

no reply in a week

i was busy trying to fix it


Pretrained Xception

Hi there! Thanks for the great work!!
But I ran into trouble when Xception pretrained weights. I uncomment some codes in the model, like the bn stuff, and also change some 1536 to 2048, but the problem is still not solved.
`
RuntimeError: Error(s) in loading state_dict for Xception:
Unexpected key(s) in state_dict: "bn3.weight", "bn3.bias", "bn3.running_mean", "bn3.running_var", "bn4.weight", "bn4.bias", "bn4.running_mean", "bn4.running_var", "fc.weight", "fc.bias", "block1.rep.0.conv1.weight", "block1.rep.0.pointwise.weight", "block1.rep.1.weight", "block1.rep.1.bias", "block1.rep.1.running_mean", "block1.rep.1.running_var", "block1.rep.3.conv1.weight", "block1.rep.3.pointwise.weight", "block1.rep.4.weight", "block1.rep.4.bias", "block1.rep.4.running_mean", "block1.rep.4.running_var", "block2.rep.1.conv1.weight", "block2.rep.1.pointwise.weight", "block2.rep.2.weight", "block2.rep.2.bias", "block2.rep.2.running_mean", "block2.rep.2.running_var", "block2.rep.4.conv1.weight", "block2.rep.4.pointwise.weight", "block2.rep.5.weight", "block2.rep.5.bias", "block2.rep.5.running_mean", "block2.rep.5.running_var", "block3.rep.1.conv1.weight", "block3.rep.1.pointwise.weight", "block3.rep.2.weight", "block3.rep.2.bias", "block3.rep.2.running_mean", "block3.rep.2.running_var", "block3.rep.4.conv1.weight", "block3.rep.4.pointwise.weight", "block3.rep.5.weight", "block3.rep.5.bias", "block3.rep.5.running_mean", "block3.rep.5.running_var", "block4.rep.1.conv1.weight", "block4.rep.1.pointwise.weight", "block4.rep.2.weight", "block4.rep.2.bias", "block4.rep.2.running_mean", "block4.rep.2.running_var", "block4.rep.4.conv1.weight", "block4.rep.4.pointwise.weight", "block4.rep.5.weight", "block4.rep.5.bias", "block4.rep.5.running_mean", "block4.rep.5.running_var", "block4.rep.7.conv1.weight", "block4.rep.7.pointwise.weight", "block4.rep.8.weight", "block4.rep.8.bias", "block4.rep.8.running_mean", "block4.rep.8.running_var", "block5.rep.1.conv1.weight", "block5.rep.1.pointwise.weight", "block5.rep.2.weight", "block5.rep.2.bias", "block5.rep.2.running_mean", "block5.rep.2.running_var", "block5.rep.4.conv1.weight", "block5.rep.4.pointwise.weight", "block5.rep.5.weight", "block5.rep.5.bias", "block5.rep.5.running_mean", "block5.rep.5.running_var", "block5.rep.7.conv1.weight", "block5.rep.7.pointwise.weight", "block5.rep.8.weight", "block5.rep.8.bias", "block5.rep.8.running_mean", "block5.rep.8.running_var", "block6.rep.1.conv1.weight", "block6.rep.1.pointwise.weight", "block6.rep.2.weight", "block6.rep.2.bias", "block6.rep.2.running_mean", "block6.rep.2.running_var", "block6.rep.4.conv1.weight", "block6.rep.4.pointwise.weight", "block6.rep.5.weight", "block6.rep.5.bias", "block6.rep.5.running_mean", "block6.rep.5.running_var", "block6.rep.7.conv1.weight", "block6.rep.7.pointwise.weight", "block6.rep.8.weight", "block6.rep.8.bias", "block6.rep.8.running_mean", "block6.rep.8.running_var", "block7.rep.1.conv1.weight", "block7.rep.1.pointwise.weight", "block7.rep.2.weight", "block7.rep.2.bias", "block7.rep.2.running_mean", "block7.rep.2.running_var", "block7.rep.4.conv1.weight", "block7.rep.4.pointwise.weight", "block7.rep.5.weight", "block7.rep.5.bias", "block7.rep.5.running_mean", "block7.rep.5.running_var", "block7.rep.7.conv1.weight", "block7.rep.7.pointwise.weight", "block7.rep.8.weight", "block7.rep.8.bias", "block7.rep.8.running_mean", "block7.rep.8.running_var", "block8.rep.1.conv1.weight", "block8.rep.1.pointwise.weight", "block8.rep.2.weight", "block8.rep.2.bias", "block8.rep.2.running_mean", "block8.rep.2.running_var", "block8.rep.4.conv1.weight", "block8.rep.4.pointwise.weight", "block8.rep.5.weight", "block8.rep.5.bias", "block8.rep.5.running_mean", "block8.rep.5.running_var", "block8.rep.7.conv1.weight", "block8.rep.7.pointwise.weight", "block8.rep.8.weight", "block8.rep.8.bias", "block8.rep.8.running_mean", "block8.rep.8.running_var", "block9.rep.1.conv1.weight", "block9.rep.1.pointwise.weight", "block9.rep.2.weight", "block9.rep.2.bias", "block9.rep.2.running_mean", "block9.rep.2.running_var", "block9.rep.4.conv1.weight", "block9.rep.4.pointwise.weight", "block9.rep.5.weight", "block9.rep.5.bias", "block9.rep.5.running_mean", "block9.rep.5.running_var", "block9.rep.7.conv1.weight", "block9.rep.7.pointwise.weight", "block9.rep.8.weight", "block9.rep.8.bias", "block9.rep.8.running_mean", "block9.rep.8.running_var", "block10.rep.1.conv1.weight", "block10.rep.1.pointwise.weight", "block10.rep.2.weight", "block10.rep.2.bias", "block10.rep.2.running_mean", "block10.rep.2.running_var", "block10.rep.4.conv1.weight", "block10.rep.4.pointwise.weight", "block10.rep.5.weight", "block10.rep.5.bias", "block10.rep.5.running_mean", "block10.rep.5.running_var", "block10.rep.7.conv1.weight", "block10.rep.7.pointwise.weight", "block10.rep.8.weight", "block10.rep.8.bias", "block10.rep.8.running_mean", "block10.rep.8.running_var", "block11.rep.1.conv1.weight", "block11.rep.1.pointwise.weight", "block11.rep.2.weight", "block11.rep.2.bias", "block11.rep.2.running_mean", "block11.rep.2.running_var", "block11.rep.4.conv1.weight", "block11.rep.4.pointwise.weight", "block11.rep.5.weight", "block11.rep.5.bias", "block11.rep.5.running_mean", "block11.rep.5.running_var", "block11.rep.7.conv1.weight", "block11.rep.7.pointwise.weight", "block11.rep.8.weight", "block11.rep.8.bias", "block11.rep.8.running_mean", "block11.rep.8.running_var", "block12.skip.weight", "block12.skipbn.weight", "block12.skipbn.bias", "block12.skipbn.running_mean", "block12.skipbn.running_var", "block12.rep.1.conv1.weight", "block12.rep.1.pointwise.weight", "block12.rep.2.weight", "block12.rep.2.bias", "block12.rep.2.running_mean", "block12.rep.2.running_var", "block12.rep.4.conv1.weight", "block12.rep.4.pointwise.weight", "block12.rep.5.weight", "block12.rep.5.bias", "block12.rep.5.running_mean", "block12.rep.5.running_var", "conv3.conv1.weight", "conv4.conv1.weight".
size mismatch for conv3.pointwise.weight: copying a param with shape torch.Size([1536, 1024]) from checkpoint, the shape in current model is torch.Size([1536, 1024, 1, 1]).
size mismatch for conv4.pointwise.weight: copying a param with shape torch.Size([2048, 1536]) from checkpoint, the shape in current model is torch.Size([1536, 1536, 1, 1]).
`
Can anyone help? Thanks a lot!!

Hi there! I somehow find some workaround.
In the pretrained condition, here is the modified code.
if pretrained:
# old_dict = torch.load(model_urls['xception'])
old_dict = model_zoo.load_url(model_urls['xception'])
for name, weights in old_dict.items():
if 'pointwise' in name:
old_dict[name] = weights.unsqueeze(-1).unsqueeze(-1)
model_dict = model.state_dict()
old_dict = {k: v for k,v in old_dict.items() if ('itr' not in k and 'tmp' not in k and 'track' not in k)}
model_dict.update(old_dict)
model.load_state_dict(model_dict,strict=False)
I uncommented the code with "model_zoo" blablabla. And change the con4 and conv5 to
self.conv4 = SeparableConv2d(1536,2048,3,1,1rate,dilation=rate,activate_first=False)
self.conv5 = SeparableConv2d(2048,2048,3,1,1rate,dilation=rate,activate_first=False)
And then, load the model in an unstrict mode. (Otherwise, there will be a kit if unexpected keys.)
Please correct me! Thanks again for the great work!

Ahh I think the correct link for xception weights is in the readme file... Sorry

Can you tell me that how do you solve that?Thank you so much,I meet the same question as yours

Hi there
Actually the author has changed the architecture of the Xception net a lot. Therefore, loading weights of the normal Xception network does not work. Luckily, the author has provided the pretrained weights for his/her own version, which is included her:

I remembered it will still prompt out an error saying size mismatch, but for this time you can easily change it. If you need any help regarding this, pleas attach a capture. (I forgot what I exactly have done.)

Hi there Actually the author has changed the architecture of the Xception net a lot. Therefore, loading weights of the normal Xception network does not work. Luckily, the author has provided the pretrained weights for his/her own version, which is included here:
I remembered it will still prompt out an error saying size mismatch, but for this time you can easily change it. If you need any help regarding this, pleas attach a capture. (I forgot what I exactly have done.)

Sincerely thank you for your reply. According to your instructions my problem has been solved。Thank you so much

You are welcome~


Please install Dokan 1.0.1 to use this application

Hi,
i have installed ACDDokanNet 1.6.4 to solve "Object reference not set to an instance of an object", this version (1.6.4) ask to me "Please install Dokan 1.0.1 to use this application" but i already have this installed on my PC.
i tried to uninstall and reinstall Dokan <IP_ADDRESS> without result.
How can i solve this?
BR
Giuseppe.

no-one have a fix for this?

Please help me i tried many time to uninstall and reinstall all packages without results.


Add helper pack_path to avoid calling asset_path

The pack_path is the same as the asset_pack_path except that the
Rails asset_path is not called on the file name. This is used by
server rendering, as the asset_path is designed for browsers to access
assets.

This change is

looks good to me 👍

LGTM


Fix actions

Noticed by @bilalshaikh42. The actions are expecting this package to be in a different location. I think this just requires installing this package with the editable option (-e).

I think the actions should be correctly configured now. I tested one job. Admittedly, I haven't checked every combination of options.

All command-line arguments are now exposed to the actions.


y2038: tests should not be failing if system date is set to after 2038

To test the readiness of Yocto stack for Y2038 we run qemu virtual machines with RTC set to some day in 2040. This causes a few of openssl's tests to fail on both 32 bit and 64 bit systems: the reason is that test data, certificates in particular, seem to set their expiry date to 2035 or so.
I would propose to set the expiry date to far enough in the future that it won't have to be tweaked in our lifetimes: this way real Y2038 issues in openssl (or in things it depends on) can be exposed and fixed (it's well possible there are none, but that needs confirmation too).
Failures seen:
Test Summary Report
-------------------
80-test_cmp_http.t               (Wstat: 1280 (exited 5) Tests: 6 Failed: 5)
  Failed tests:  1-5
  Non-zero exit status: 5
80-test_cms.t                    (Wstat: 256 (exited 1) Tests: 16 Failed: 1)
  Failed test:  1
  Non-zero exit status: 1
90-test_sslapi.t                 (Wstat: 256 (exited 1) Tests: 3 Failed: 1)
  Failed test:  1
  Non-zero exit status: 1

If there's agreement on this, I can prepare the patch, but I need guidance as to how to regenerate the data correctly (there seem to be no way of doing it with a script from metadata, rather the data is simply stored in git).

Ping, please.

For anything that's in test/certs, it should be quite easy, just do this:
$ cd test/certs
$ ./setup.sh

Although, I'm not sure that it should be necessary, as the expiry has been set to 100 years forward, and the files in there weren't generated that long ago...
Regarding test_cmp_http and test_cms, it's a different story.  The diverse certs are in test/recipes/80-test_cmp_http_data/Mock and test/recipes/80-test_cms_data, unfortunately without a script to recreate those files.  @DDvO, you created those, right?  Would you mind adding a script to recreate them?

Can you provide verbose test output for the sslapi test failure?
make TESTS=test_sslapi V=1 test

Can you provide verbose test output for the sslapi test failure?
make TESTS=test_sslapi V=1 test

We package the tests into the target image, and use ./test/run_tests.pl directly. With that, I get:
90-test_sslapi.t ........................
    # INFO:  @ /usr/src/debug/openssl/3.2.0/test/helpers/ssltestlib.c:1246
    # SSL_connect() failed -1, 12
    # INFO:  @ /usr/src/debug/openssl/3.2.0/test/helpers/ssltestlib.c:1246
    # SSL_connect() failed -1, 1
    # 403726FFFE7E0000:error:0A000086:SSL routines:tls_post_process_server_certificate:certificate verify failed:/usr/src/debug/openssl/3.2.0/ssl/statem/statem_clnt.c:2091:
    # INFO:  @ /usr/src/debug/openssl/3.2.0/test/helpers/ssltestlib.c:1280
    # SSL_accept() failed -1, 1
    # 403726FFFE7E0000:error:0A000415:SSL routines:ssl3_read_bytes:ssl/tls alert certificate expired:/usr/src/debug/openssl/3.2.0/ssl/record/rec_layer_s3.c:861:SSL alert number 45
    # ERROR: (bool) 'create_ssl_connection(serverssl, clientssl, SSL_ERROR_NONE) == true' failed @ /usr/src/debug/openssl/3.2.0/test/sslapitest.c:613
    # false
    # 403726FFFE7E0000:error:0A000197:SSL routines:SSL_shutdown:shutdown while in init:/usr/src/debug/openssl/3.2.0/ssl/ssl_lib.c:2766:
    # 403726FFFE7E0000:error:0A000197:SSL routines:SSL_shutdown:shutdown while in init:/usr/src/debug/openssl/3.2.0/ssl/ssl_lib.c:2766:
    # OPENSSL_TEST_RAND_SEED=-2083212775
    not ok 23 - test_client_cert_verify_cb
# ------------------------------------------------------------------------------
    # ERROR: (bool) 'SSL_build_cert_chain(ssl, SSL_BUILD_CHAIN_FLAG_NO_ROOT | SSL_BUILD_CHAIN_FLAG_CHECK) == true' failed @ /usr/src/debug/openssl/3.2.0/test/sslapitest.c:659
    # false
    # 403726FFFE7E0000:error:0A000086:SSL routines:ssl_build_cert_chain:certificate verify failed:/usr/src/debug/openssl/3.2.0/ssl/ssl_cert.c:1050:Verify error:certificate has expired
    # OPENSSL_TEST_RAND_SEED=-2083212775
    not ok 24 - test_ssl_build_cert_chain
# ------------------------------------------------------------------------------
    # ERROR: (bool) 'SSL_CTX_build_cert_chain(ctx, SSL_BUILD_CHAIN_FLAG_NO_ROOT | SSL_BUILD_CHAIN_FLAG_CHECK) == true' failed @ /usr/src/debug/openssl/3.2.0/test/sslapitest.c:698
    # false
    # 403726FFFE7E0000:error:0A000086:SSL routines:ssl_build_cert_chain:certificate verify failed:/usr/src/debug/openssl/3.2.0/ssl/ssl_cert.c:1050:Verify error:certificate has expired
    # OPENSSL_TEST_RAND_SEED=-2083212775
    not ok 25 - test_ssl_ctx_build_cert_chain
# ------------------------------------------------------------------------------
../../util/wrap.pl ../../test/sslapitest ../../test/certs ../../test/recipes/90-test_sslapi_data/passwd.txt /tmp/yk2HQq8yoQ default ../../test/default.cnf ../../test/recipes/90-test_sslapi_data/dhparams.pem => 1
not ok 1 - running sslapitest
90-test_sslapi.t ........................ 1/? ----------------------------------
90-test_sslapi.t ........................ Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/4 subtests
	(less 2 skipped subtests: 1 okay)

If that's not verbose enough, I can try again with extra verbosity if you tell me how.


Contrib folder missing

Hello, awesome work making our lives easy with this library! I am struggled trying to use RDConfig.RDContribDir in my project.
I create this function to import sascorer (it is no so nice, I know :-) )
def import_sascorer():
    # In order to import sascorer from RDConfig.RDContribDir
    from rdkit.Chem import RDConfig
    import os, importlib.util as importlib_util
    spec=importlib_util.spec_from_file_location('sascorer', os.path.join(RDConfig.RDContribDir, 'SA_Score', 'sascorer.py'))
    sascorer = importlib_util.module_from_spec(spec)
    spec.loader.exec_module(sascorer)
    return sascorer

When I use conda install rdkit, everything works fine. But when I use python -m pip install rdkit (as recomended in PyPi). I get:
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "<stdin>", line 7, in import_sascorer
  File "<frozen importlib._bootstrap_external>", line 879, in exec_module
  File "<frozen importlib._bootstrap_external>", line 1016, in get_code
  File "<frozen importlib._bootstrap_external>", line 1073, in get_data
FileNotFoundError: [Errno 2] No such file or directory: '/home/ale/anaconda3/envs/test/lib/python3.10/site-packages/rdkit/Contrib/SA_Score/sascorer.py'

And indeed the file doesn’t exist. So, how could I install the contribute directory via pip? A lot of thanks in advance!

Can this be re-opened? Or have you ruled out including the Contrib folder in the wheels, @kuelumbus ?
At least I think it should be clearly documented what the wheels does not include, as of now I assume that I get the same thing with pip and conda installations (but I don't).

Yes, you are right. The next version should include the contrib directory.

This is fixed in version 2022.3.5.


Remove http server running on a public port.

A webserver was started by the workbench.
It is unclear why it would be needed.
It could be a possible security risk.

In QA we don't use that supervisor cluster anymore, so we are not affected by the change.
However I don't see anything wrong with running that http server. The http server serves pools metadata on address:port that each pool announced during pool registration, so it's desirable to keep it there.

@deepfire The PR has already been prepared and we have a confirmation from Martin that the http server is not used by the QA team any longer.
I suggest that we merge this PR and remove it.

Closing this. Please re-open this PR if it is still relevant.


Automator: update common-files@master in istio/istio@master

Generated by Automator - 2021-01-20T18:32:07+00:00

@istio-testing: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-multicluster-tests_istio
d6f73038e1d3227a03449d1da921532c22c2118e
link
/test integ-pilot-multicluster-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-multicluster-tests_istio
d6f73038e1d3227a03449d1da921532c22c2118e
link
/test integ-pilot-multicluster-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

/retest


Price updates sent to client even after viewport is removed

When a datagrid component is closed in the UI a REMOVE_VP message is sent to Vuu and server ACKS with REMOVE_VP_SUCCESS.
However, if viewport has ticking prices, eg Prices table, updates continue to be sent to client even after viewport is removed.

Cool, thanks. Will take a look.
On Thu, 1 Dec 2022 at 17:20, heswell @.***> wrote:

They appear to continue indefinately.
Disabling the viewport suspends updates, not removing it though.
—
Reply to this email directly, view it on GitHub
https://github.com/finos/vuu/issues/366#issuecomment-1334020435, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AED5EUKI2VNDCC4CNQHQ633WLDF5VANCNFSM6AAAAAASQ6HECA
.
You are receiving this because you were mentioned.Message ID:
@.***>


Add sentence to export docs on nullable columns

Fixes DOC-7861
This PR adds a brief sentence to the EXPORT docs following a new internal implementation which results in all columns being written as nullable.

@jayshrivastava Just a friendly ping for review on this small PR. Thanks!


Roman

👷 Deploy Preview for adoring-leavitt-e31a11 processing.

Name
Link

🔨 Latest commit
6995795412bec5a4033bbdf085764104f2838868

🔍 Latest deploy log
https://app.netlify.com/sites/adoring-leavitt-e31a11/deploys/628d1f2421a2ec0008abbd7a


bngblaster: 0.9.2 -> 0.9.5

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/rtbrick/bngblaster/releases.
meta.description for bngblaster is: Network tester for access and routing protocols
meta.homepage for bngblaster is: https://github.com/rtbrick/bngblaster/
meta.changelog for bngblaster is: https://github.com/rtbrick/bngblaster/releases/tag/0.9.3
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.9.3 with grep in /nix/store/p82shlivp2hv547psk1mkkd117impi27-bngblaster-0.9.3
found 0.9.3 in filename of file in /nix/store/p82shlivp2hv547psk1mkkd117impi27-bngblaster-0.9.3

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

bngblaster

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/p82shlivp2hv547psk1mkkd117impi27-bngblaster-0.9.3 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A bngblaster https://github.com/r-ryantm/nixpkgs/archive/47b01f81e9c89d591146787aaa92ebd8527a7cd8.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/47b01f81e9c89d591146787aaa92ebd8527a7cd8#bngblaster

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/p82shlivp2hv547psk1mkkd117impi27-bngblaster-0.9.3
ls -la /nix/store/p82shlivp2hv547psk1mkkd117impi27-bngblaster-0.9.3/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

bngblaster

Maintainer pings
cc @n0emis @vidister @johannwagner @yu-re-ka for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/rtbrick/bngblaster/releases.
meta.description for bngblaster is: Network tester for access and routing protocols
meta.homepage for bngblaster is: https://github.com/rtbrick/bngblaster/
meta.changelog for bngblaster is: https://github.com/rtbrick/bngblaster/releases/tag/0.9.4
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.9.4 with grep in /nix/store/5j1gv5jnac9qfwgv92dany3cqd8w7z29-bngblaster-0.9.4
found 0.9.4 in filename of file in /nix/store/5j1gv5jnac9qfwgv92dany3cqd8w7z29-bngblaster-0.9.4

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

bngblaster

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/5j1gv5jnac9qfwgv92dany3cqd8w7z29-bngblaster-0.9.4 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A bngblaster https://github.com/r-ryantm/nixpkgs/archive/7bc2451385341e1956f151f4fb1644cee53a1b99.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/7bc2451385341e1956f151f4fb1644cee53a1b99#bngblaster

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/5j1gv5jnac9qfwgv92dany3cqd8w7z29-bngblaster-0.9.4
ls -la /nix/store/5j1gv5jnac9qfwgv92dany3cqd8w7z29-bngblaster-0.9.4/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

bngblaster

Maintainer pings
cc @n0emis @vidister @johannwagner @yu-re-ka for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/rtbrick/bngblaster/releases.
meta.description for bngblaster is: Network tester for access and routing protocols
meta.homepage for bngblaster is: https://github.com/rtbrick/bngblaster/
meta.changelog for bngblaster is: https://github.com/rtbrick/bngblaster/releases/tag/0.9.5
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.9.5 with grep in /nix/store/d37fapg5295phi2y5d091jn1lv5z0lcy-bngblaster-0.9.5
found 0.9.5 in filename of file in /nix/store/d37fapg5295phi2y5d091jn1lv5z0lcy-bngblaster-0.9.5

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

bngblaster

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/d37fapg5295phi2y5d091jn1lv5z0lcy-bngblaster-0.9.5 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A bngblaster https://github.com/r-ryantm/nixpkgs/archive/323fe572abceefca2d79e244f39675b2ba53fe62.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/323fe572abceefca2d79e244f39675b2ba53fe62#bngblaster

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/d37fapg5295phi2y5d091jn1lv5z0lcy-bngblaster-0.9.5
ls -la /nix/store/d37fapg5295phi2y5d091jn1lv5z0lcy-bngblaster-0.9.5/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

bngblaster

Maintainer pings
cc @n0emis @vidister @johannwagner @yu-re-ka for testing.