Retry if setup-matlab fails

Does there exist an option to retry if setup-matlab fails? setup-matlab@v2-beta randomly (~not very often~) fails due to the failure of sudo apt. See the following for an example. I guess a retry would likely succeed. Thanks.

  Reading package lists...
  Building dependency tree...
  Reading state information...
  Skipping libasound2, it is already installed and upgrade is not set.
  libasound2 set to manually installed.
  Skipping libcairo-gobject2, it is already installed and upgrade is not set.
  libcairo-gobject2 set to manually installed.
  Skipping libcairo2, it is already installed and upgrade is not set.
  libcairo2 set to manually installed.
  Skipping libcap2, it is already installed and upgrade is not set.
  libcap2 set to manually installed.
  Skipping libcrypt1, it is already installed and upgrade is not set.
  libcrypt1 set to manually installed.
  Skipping libice6, it is already installed and upgrade is not set.
  libice6 set to manually installed.
  Skipping libnspr4, it is already installed and upgrade is not set.
  Skipping libodbc2, it is already installed and upgrade is not set.
  libodbc2 set to manually installed.
  Skipping libodbcinst2, it is already installed and upgrade is not set.
  libodbcinst2 set to manually installed.
  Skipping libuuid1, it is already installed and upgrade is not set.
  libuuid1 set to manually installed.
  Skipping libxcomposite1, it is already installed and upgrade is not set.
  libxcomposite1 set to manually installed.
  Skipping libxcursor1, it is already installed and upgrade is not set.
  libxcursor1 set to manually installed.
  Skipping libxdamage1, it is already installed and upgrade is not set.
  libxdamage1 set to manually installed.
  Skipping libxfixes3, it is already installed and upgrade is not set.
  libxfixes3 set to manually installed.
  Skipping libxft2, it is already installed and upgrade is not set.
  libxft2 set to manually installed.
  Skipping libxinerama1, it is already installed and upgrade is not set.
  libxinerama1 set to manually installed.
  Skipping libxrandr2, it is already installed and upgrade is not set.
  libxrandr2 set to manually installed.
  Skipping libxt6, it is already installed and upgrade is not set.
  libxt6 set to manually installed.
  Skipping libxtst6, it is already installed and upgrade is not set.
  libxtst6 set to manually installed.
  Skipping libxxf86vm1, it is already installed and upgrade is not set.
  libxxf86vm1 set to manually installed.
  Skipping procps, it is already installed and upgrade is not set.
  procps set to manually installed.
  Skipping xkb-data, it is already installed and upgrade is not set.
  xkb-data set to manually installed.
  Skipping ca-certificates, it is already installed and upgrade is not set.
  Skipping libc6, it is already installed and upgrade is not set.
  libc6 set to manually installed.
  Skipping libcups2, it is already installed and upgrade is not set.
  libcups2 set to manually installed.
  Skipping libdrm2, it is already installed and upgrade is not set.
  libdrm2 set to manually installed.
  Skipping libgbm1, it is already installed and upgrade is not set.
  libgbm1 set to manually installed.
  Skipping libgdk-pixbuf-2.0-0, it is already installed and upgrade is not set.
  libgdk-pixbuf-2.0-0 set to manually installed.
  Skipping libglib2.0-0, it is already installed and upgrade is not set.
  libglib2.0-0 set to manually installed.
  Skipping libgstreamer1.0-0, it is already installed and upgrade is not set.
  libgstreamer1.0-0 set to manually installed.
  Skipping libgtk-3-0, it is already installed and upgrade is not set.
  Skipping libnss3, it is already installed and upgrade is not set.
  Skipping libpam0g, it is already installed and upgrade is not set.
  libpam0g set to manually installed.
  Skipping libpango-1.0-0, it is already installed and upgrade is not set.
  libpango-1.0-0 set to manually installed.
  Skipping libpangocairo-1.0-0, it is already installed and upgrade is not set.
  libpangocairo-1.0-0 set to manually installed.
  Skipping libpangoft2-1.0-0, it is already installed and upgrade is not set.
  libpangoft2-1.0-0 set to manually installed.
  Skipping libpython3.[10](https://github.com/zequipe/prima/actions/runs/4982550105/jobs/8918377600#step:9:11), it is already installed and upgrade is not set.
  libpython3.10 set to manually installed.
  Skipping libwayland-client0, it is already installed and upgrade is not set.
  libwayland-client0 set to manually installed.
  Skipping locales, it is already installed and upgrade is not set.
  Skipping sudo, it is already installed and upgrade is not set.
  Skipping zlib1g, it is already installed and upgrade is not set.
  zlib1g set to manually installed.
  The following additional packages will be installed:
    libflac8 libopus0 liborc-0.4-0 libvorbisenc2
  Suggested packages:
    libvisual-0.4-plugins opus-tools
  Recommended packages:
    gstreamer1.0-plugins-base
  The following NEW packages will be installed:
    libflac8 libgstreamer-plugins-base1.0-0 libopus0 liborc-0.4-0 libsndfile1
    libvorbisenc2 locales-all
  0 upgraded, 7 newly installed, 0 to remove and 48 not upgraded.
  Need to get 12.4 MB of archives.
  After this operation, 239 MB of additional disk space will be used.
  Ign:1 http://azure.archive.ubuntu.com/ubuntu jammy-updates/main amd64 libflac8 amd64 1.3.3-2ubuntu0.1
  Ign:2 http://azure.archive.ubuntu.com/ubuntu jammy/main amd64 liborc-0.4-0 amd64 1:0.4.32-2
  Ign:3 http://azure.archive.ubuntu.com/ubuntu jammy/main amd64 libgstreamer-plugins-base1.0-0 amd64 1.20.1-1
  Ign:4 http://azure.archive.ubuntu.com/ubuntu jammy/main amd64 libopus0 amd64 1.3.1-0.1build2
  Ign:5 http://azure.archive.ubuntu.com/ubuntu jammy/main amd64 libvorbisenc2 amd64 1.3.7-1build2
  Ign:6 http://azure.archive.ubuntu.com/ubuntu jammy/main amd64 libsndfile1 amd64 1.0.31-2build1
  Ign:7 http://azure.archive.ubuntu.com/ubuntu jammy-updates/universe amd64 locales-all amd64 2.35-0ubuntu3.1
  Ign:1 http://azure.archive.ubuntu.com/ubuntu jammy-updates/main amd64 libflac8 amd64 1.3.3-2ubuntu0.1
  Ign:2 http://azure.archive.ubuntu.com/ubuntu jammy/main amd64 liborc-0.4-0 amd64 1:0.4.32-2
  Ign:3 http://azure.archive.ubuntu.com/ubuntu jammy/main amd64 libgstreamer-plugins-base1.0-0 amd64 1.20.1-1
  Ign:4 http://azure.archive.ubuntu.com/ubuntu jammy/main amd64 libopus0 amd64 1.3.1-0.1build2
  Ign:5 http://azure.archive.ubuntu.com/ubuntu jammy/main amd64 libvorbisenc2 amd64 1.3.7-1build2
  Ign:6 http://azure.archive.ubuntu.com/ubuntu jammy/main amd64 libsndfile1 amd64 1.0.31-2build1
  Ign:7 http://azure.archive.ubuntu.com/ubuntu jammy-updates/universe amd64 locales-all amd64 2.35-0ubuntu3.1
  Ign:1 http://azure.archive.ubuntu.com/ubuntu jammy-updates/main amd64 libflac8 amd64 1.3.3-2ubuntu0.1
  Ign:2 http://azure.archive.ubuntu.com/ubuntu jammy/main amd64 liborc-0.4-0 amd64 1:0.4.32-2
  Ign:3 http://azure.archive.ubuntu.com/ubuntu jammy/main amd64 libgstreamer-plugins-base1.0-0 amd64 1.20.1-1
  Ign:4 http://azure.archive.ubuntu.com/ubuntu jammy/main amd64 libopus0 amd64 1.3.1-0.1build2
  Ign:5 http://azure.archive.ubuntu.com/ubuntu jammy/main amd64 libvorbisenc2 amd64 1.3.7-1build2
  Ign:6 http://azure.archive.ubuntu.com/ubuntu jammy/main amd64 libsndfile1 amd64 1.0.31-2build1
  Ign:7 http://azure.archive.ubuntu.com/ubuntu jammy-updates/universe amd64 locales-all amd64 2.35-0ubuntu3.1
  Ign:1 http://azure.archive.ubuntu.com/ubuntu jammy-updates/main amd64 libflac8 amd64 1.3.3-2ubuntu0.1
  Err:2 http://azure.archive.ubuntu.com/ubuntu jammy/main amd64 liborc-0.4-0 amd64 1:0.4.32-2
    Unable to connect to azure.archive.ubuntu.com:http: [IP: 52.[15](https://github.com/zequipe/prima/actions/runs/4982550105/jobs/8918377600#step:9:16)4.[17](https://github.com/zequipe/prima/actions/runs/4982550105/jobs/8918377600#step:9:18)4.[20](https://github.com/zequipe/prima/actions/runs/4982550105/jobs/8918377600#step:9:21)8 80]
  Err:3 http://azure.archive.ubuntu.com/ubuntu jammy/main amd64 libgstreamer-plugins-base1.0-0 amd64 1.20.1-1
    Unable to connect to azure.archive.ubuntu.com:http: [IP: <IP_ADDRESS> 80]
  Err:4 http://azure.archive.ubuntu.com/ubuntu jammy/main amd64 libopus0 amd64 1.3.1-0.1build2
    Unable to connect to azure.archive.ubuntu.com:http: [IP: <IP_ADDRESS> 80]
  Err:5 http://azure.archive.ubuntu.com/ubuntu jammy/main amd64 libvorbisenc2 amd64 1.3.7-1build2
    Unable to connect to azure.archive.ubuntu.com:http: [IP: <IP_ADDRESS> 80]
  Err:6 http://azure.archive.ubuntu.com/ubuntu jammy/main amd64 libsndfile1 amd64 1.0.[31](https://github.com/zequipe/prima/actions/runs/4982550105/jobs/8918377600#step:9:32)-2build1
    Unable to connect to azure.archive.ubuntu.com:http: [IP: <IP_ADDRESS> 80]
  Err:7 http://azure.archive.ubuntu.com/ubuntu jammy-updates/universe amd64 locales-all amd64 2.35-0ubuntu3.1
    Unable to connect to azure.archive.ubuntu.com:http: [IP: <IP_ADDRESS> 80]
  Err:1 http://azure.archive.ubuntu.com/ubuntu jammy-updates/main amd64 libflac8 amd64 1.3.3-2ubuntu0.1
    Could not connect to azure.archive.ubuntu.com:80 (<IP_ADDRESS>), connection timed out [IP: <IP_ADDRESS> 80]
  E: Failed to fetch http://azure.archive.ubuntu.com/ubuntu/pool/main/f/flac/libflac8_1.3.3-2ubuntu0.1_amd64.deb  Could not connect to azure.archive.ubuntu.com:80 (<IP_ADDRESS>), connection timed out [IP: <IP_ADDRESS> 80]
  E: Failed to fetch http://azure.archive.ubuntu.com/ubuntu/pool/main/o/orc/liborc-0.4-0_0.4.[32](https://github.com/zequipe/prima/actions/runs/4982550105/jobs/8918377600#step:9:33)-2_amd64.deb  Unable to connect to azure.archive.ubuntu.com:http: [IP: <IP_ADDRESS> 80]
  E: Failed to fetch http://azure.archive.ubuntu.com/ubuntu/pool/main/g/gst-plugins-base1.0/libgstreamer-plugins-base1.0-0_1.20.1-1_amd64.deb  Unable to connect to azure.archive.ubuntu.com:http: [IP: <IP_ADDRESS> 80]
  E: Failed to fetch http://azure.archive.ubuntu.com/ubuntu/pool/main/o/opus/libopus0_1.3.1-0.1build2_amd64.deb  Unable to connect to azure.archive.ubuntu.com:http: [IP: <IP_ADDRESS> 80]
  E: Failed to fetch http://azure.archive.ubuntu.com/ubuntu/pool/main/libv/libvorbis/libvorbisenc2_1.3.7-1build2_amd64.deb  Unable to connect to azure.archive.ubuntu.com:http: [IP: <IP_ADDRESS> 80]
  E: Failed to fetch http://azure.archive.ubuntu.com/ubuntu/pool/main/libs/libsndfile/libsndfile1_1.0.31-2build1_amd64.deb  Unable to connect to azure.archive.ubuntu.com:http: [IP: <IP_ADDRESS> 80]
  E: Failed to fetch http://azure.archive.ubuntu.com/ubuntu/pool/universe/g/glibc/locales-all_2.[35](https://github.com/zequipe/prima/actions/runs/4982550105/jobs/8918377600#step:9:36)-0ubuntu3.1_amd64.deb  Unable to connect to azure.archive.ubuntu.com:http: [IP: [52](https://github.com/zequipe/prima/actions/runs/4982550105/jobs/8918377600#step:9:53).1[54](https://github.com/zequipe/prima/actions/runs/4982550105/jobs/8918377600#step:9:55).1[74](https://github.com/zequipe/prima/actions/runs/4982550105/jobs/8918377600#step:9:75).208 [80](https://github.com/zequipe/prima/actions/runs/4982550105/jobs/8918377600#step:9:81)]
  E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
Error: Error: The process '/usr/bin/sudo' failed with exit code [100]

Update: the error seems to occur at a much higher frequency today. See
https://github.com/libsprima/prima/actions/runs/4988072482
https://github.com/libsprima/prima/actions/runs/4988072484

Thank you @mcafaro for looking into it.


RSE time applications

should be possible to apply for RSE time in the same way as for a system allocation, attached to a project

resolved as of 58b9a865b84579d6ad01b0d4b9fbfd45f7244cbf


WRP-19306: Fixed VirtualList to warn if both minSize in itemSize and cbScrollTo are given

Checklist

[x] I have read and understand the contribution guide
[ ] A CHANGELOG entry is included
[x] At least one test case is included for this feature or bug fix
[x] Documentation was added or is not needed
[ ] This is an API breaking change

Issue Resolved / Feature Added
To support different item size, itemSize can be an object contains minSize property. When minSize is speicified, cbScrollTo is not supported and VirtualList should warn it.
Resolution
Fixed broken condition to warn unsupported combination of props.
Additional Considerations
Links
WRP-19306
WRP-4365
Comments

Note: .travis.yml is changed as this PR is depend on enactjs/enact#3158. The commit changing .travis.yml should be reverted before merging.


bundling gnulib into release tarballs

Hi,
I really wonder why gnulib is not bundled within release tarballs, besides the obvious question why luaposix is relying on gnulib anyway - but that is a different topic. The thing that bothers me more is why you are relying on cloning a remote git repository before being able to build from a release tarball? Why aren't you bundling gnulib within release tarballs, like 99.99999% of other projects that rely on that infamous piece of bloat and redundancy?
Here are some points to think about:

I think it is not quite uncommon that automatized build environments are building stuff within a chroot sandbox which has no network connectivity.
building from a release tarball also means that you will have the ability to reproduce a build later, but how is that going to work if the sources can vary depending on the mood of gnulib developers?
While looking at the 'bootstrap' script I have seen an option '--gnulib-srcdir' which is good to have, but it doesn't really solve point 2.
An author/maintainer knows best what versions of 3rd. party components he/she is using will work, and if there are no tagged releases of such a component it is wise to include exactly the version it was developed with! (Btw, I am by far not a fan of including every piece of 3rd. party library into sources!)

Short - It would be very neat if you could include exactly the version of gnulib within release tarballs you have developed/tested with.
Cheers,
Chris

@gvvaughan sorry for some kind of necroposting, but problem with inability to install luaposix in networkless environment using master tarball is still persists (despite of your answer to @morfoh).
Second thing is that your slingshot's "bootstrap" does some black magic, that it is impossible to build the package without it, using "usual" autoreconf+libtoolize+aclocal+autoconf+autoheader+automake, but only possible to build with that bootstrap (which is really pain for distro maintainers).
It is even impossible to somehow say buildsystem "you can take slingshot from here and gnulib from here, but do not try to fetch anything from the internet"

Hi Vadim,
Why not start from a release tarball, or checkout from the release branch where bootstrap has already executed and set up all the autoconfigury in advance?
cheers,
Gary

To be honest, because I'm maintain "9999" (VCS) luaposix package in Gentoo's Lua project. That means, I'm doing an ebuild (something like rockspec, but used for any package in the system), which purpose is to install "master" version. But distro (Gentoo) policy is to keep previously checked out sources (distfiles), including VCS trees, and (in case of vcs) do not checkout new commits if users ask for that (EVCS_OFFLINE=1, if any). That is allowing user to (re)build package from exactly the sources (s)he checked out before (on previous installation, or manually).
The case of offline installation is very useful and allowing users to preliminarily check out all sources, while they have internet connection and build packages later even without internet access (i.e. if user has no internet access at home, but working in the internet from, say, internet cafe, or, maybe, during flight, or half-country train traveling).

Understood.
In that case, I recommend running the bootstrap script from your ebuild file, which will call all the autotools in the correct order with the correct arguments among other things rather than reverse engineering the bootstrap process all over again for your ebuild.
Although I'll accept interim patches to the autofoo in luaposix, my medium term plan is to move away from Autotools half-megabyte if shell scripts into a Lua based build system - somewhat like the Luarocks build command, which will cut the size of luaposix distribution by 70% or so. When I finally arrive there, all of the bootstrap issues will go away entirely.
HTH,
Gary

Actually, I was tried to call "autocrap" things just in my attempt to unbind bootstrap from "internet" dependency ;)
It is no hard to call bootstrap itself (there is even hook for automatic calling bootstraps after pulling repo from distdir to builddir). It is hard to make it don't fetch anything from internet. For now I doing following hook:
    if [[ -n ${EVCS_OFFLINE} ]]; then
        die "Unfortunately, upstream uses buildsystem which depends on external submodules, so you won't be able to build package in offline mode. Sorry."
    fi

But users complaining anyway :-/
[offtop]
Talking about moving from "autocrap" to anything else — I myself, for my Lua projects do either prepared makefile (with some configurability) or CMake. Although, moving to CMake requires project internals knowledge and diving in the manuals for some time.
[/offtop]
By the way, is it okay to bootstrap in directory where luaposix checkouts, then copy source directory for building for each lua target and each processor architecture inside each lua target?
(I mean, doesn't bootstrap hardcode anything platform dependent in some hidden place?)
And if so, will it be hard to keep "prebuilt" configure in the repo, until migration from autotools?

On Sep 19, 2015, at 9:40 PM, Vadim A. Misbakh-Soloviov<EMAIL_ADDRESS>wrote:
[offtop]
Talking about moving from "autocrap" to anything else — I myself, for my Lua projects do either prepared makefile (with some configurability) or CMake. Although, moving to CMake requires project internals knowledge and diving in the manuals for some time.

I have absolutely no plans to jump out of the Autotools frying pan and into the Cmake fire... I actually find Cmake hard to understand, badly documented, and lacking in many of the things that come for free with Autotools (cross-compilation, autotest, shared sources for multi-arch builds, runnable and testable from the build tree without worrying about previous versions installed on the system library path, portable runtime loading, sanity checks and coding standards conformance checking, changelog generation from scm log messages, ability to distribute a package that requires nothing but a make, she'll, and some common UNIX utilities, automated version and release management, and on an on) - I know I can build all that stuff with Cmake, but Autotools provides it already.

:-)

By the way, is it okay to bootstrap in directory where luaposix checkouts, then copy source directory for building for each lua target and each processor architecture inside each lua target?

yes, absolutely... that's the way it is supposed to be used. The distributor runs 'bootstrap' and the installer runs './configure; make; sudo make install'.
Actually, if you start from a tagged release on master, and then run bootstrap, you will end up with the exact same set of files that are checked in at the matching tag on the release branch (or equivalently, the contents of one of the release tarballs I make available here on github)- subject to differences in the versions of Autotools you have in comparison to what I used at the time of release, of course.
In fact, I'm still surprised that you want to go to all the effort of redoing this all over again by yourself when I've done it all for you already... especially considering that the HEAD of master may have bugs, incomplete features or experiments that don't work out compared to using a stable release tarball, release tag from the release branch or Luarocks install?

(I mean, doesn't bootstrap hardcode anything platform dependent in some hidden place?)
And if so, will it be hard to keep "prebuilt" configure in the repo, until migration from autotools?

no, not hard at all... but still more effort than any of the more stable options I outlined above.

So... I'm unsure if I get you right, but if you're talking about doing bootstrap every time package builds, then answer is: some kind of distro specific (although, I'm pretty sure, Arch has same thing). It is nowhere where we can "prepare" sources once and forever.

The "package", as an essence, is just script with some shell variables and some shell functions, which runs at some build/install phase. One of the variables is the source where package manager can get sources. If we talking about release-version, then it's tarball link. But here - it is git repo url.
Then, installation process goes:

user says <package_manager> install =luaposix-9999 #from vcs.
Package manager fetches current repo state to distfiles directory (either git clone or git fetch, depnds if it already exists) as "bare" git repo (without files tree). Modification of distfiles is prohibited.
Package manager clones git repo to temp build dir
4a) enables sandboxing to prevent buildsystem to touch anything outside builddir or destdir (so called "image", empty target dir where package installs it files to)
4b) , including copying sources dir multiple times to build for each Lua target user enabled and each ABI architecture (for multilib, like known lib32-lib64-libx32 on x86, or something similar on mips ones).
after running "install" phase (with installing files not in the live system, but in the destdir), it merges "image" content in the live system (preventing file collisions).
temporary build directory cleans completely # btw, most users has it in the tmpfs

Only way to do not redo all the bootstrap work every time is to either have "configure" script in the sources tree in master's HEAD (depends on upstream) or to have it as patch and put it at preparation stage (actually counts as dirty and bad practice in maintainers manuals).
So single way to "do it right" is to run bootstrap every times user installs the package.

especially considering that the HEAD of master may have bugs, incomplete features or experiments that don't work out compared to using a stable release tarball, release tag from the release branch
My work is to give the possibility to install package's from VCS's HEAD revision to user (including myself). If user is doing so, then (s)he already manually confirmed (by putting special line in the config) that (s)he understands that it can be broken.
That is he purpose of "live", or, so called, "bleeding edge" packages: no one guarantee it will end build process successfully (since it is not a tarball that can be tested), but OTOH,
user has possibility to easily test for new feature if, say, (s)he reported bug upstream, upstream fixed it and then said "fixed in HEAD, please test". And user can just install "live" version and test that. Without making the system be like LFS (i.e. don't install anything without package manager)

or Luarocks install?
It is bad user practice to install anything systemwide with 3party packagemanagers, uncontrolled by the system one.
And talking about installing non-systemwide — as you can be noticed, Lua 5.2 and 5.3 changed modules path/cpath to prefer system-wide installed modules over locally installed ones: prooflink.

btw, actually, I've asked about bootstrap hardcoding because of the issues with:

compiling luaposix for lib32 with

export CC="x86_64-pc-linux-gnu-gcc -m32" CFLAGS=" -I/usr/include/lua5.1  -fPIC -DPIC" LDFLAGS=" -shared -fPIC"
./configure --prefix=/usr --build=i686-pc-linux-gnu --host=i686-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --disable-dependency-tracking --disable-silent-rules --libdir=/usr/lib32 --with-ncurses LUA=lua5.1 LUA_INCLUDE=-I/usr/include/lua5.1

it says:
checking whether we are cross compiling... configure: error: in `/var/tmp/portage/dev-lua/luaposix-9999/work/lua51/luaposix-9999-abi_x86_32.x86':
configure: error: cannot run C compiled programs.
If you meant to cross compile, use `--host'.

installing: by default, without any hacks from my side, buildsystem tries to install things to strange places:
a) for PUC-Rio luas: 32bit posix.so's to 64bit INSTALL_CMOD (/usr/lib64/lua/{LUA_ABI})
b) for luajit: posix.so to /usr/lib/lua/5.1 (there is no such path neither in 32bit nor 64bit pkgconfig files).

But both a and b, as I noticed, is taken from ${LUA_BIN} -e 'print(package.cpath)' (and both --libdir switch for configure and LUA_CPATH switch for make are ignored) :(

I've noticed there is posix.lua.in in the libs/, but it is never installed with default buildsystem. Is it just as planned? :)

what does the corresponding chunk of config.log say?
the configure is mainly set up for luarocks to call, though I'll take patches for it to work better standalone. Look at how the git rockspec calls configure to see how paths are passed in - either by looking at the code in the file, or running luarocks as described in the README.
Yes, exactly as planned - configure substitutes the version number into posix.lua.in to make installable posix.lua.

cheers,
Gary

nevermind, it seems, I found a way to walk around that ;)
Ok, i'll try to work on it, although, autotools is a very black magic for me ;)
I meant that posix.lua is never installed ;) Just only posix.so, posix/ and curses.lua ;)

okay, great!
thanks, much appreciated. I'll try to answer any questions you raise and generally be helpful.
it is installed here on my Mac, and by the Travis regression tests that run on Linux automatically for every commit. looks like you've found a bug! If you can fix it, please send a patch, otherwise please try to isolate the cause and file a new issue describing how I can reproduce it... and I will endeavor to fix it.

Cheers,
Gary

it seems, I've found workaround even for that (passing LUA_CPATH to ./configure), but there is some kind of bug (?): it looks like it somewhy uses dirname on the value of it, so if I pass LUA_CPATH=/usr/lib32/lua/5.1 (and same for lib64 and lua/5.2 and lua/5.3) — it ./configure makes it to be:

checking for lua5.1 module directory... ${exec_prefix}/lib64/lua
<...>
checking for lua5.2 module directory... ${exec_prefix}/lib64/lua
<...>
checking for lua5.3 module directory... ${exec_prefix}/lib64/lua

Exactly same thing with LUA_PATH (for LMOD).
But, if I add / to the end of LUA_PATH/LUA_CPATH values, then all goes fine. Not that it hard to add slash, but it is a bit kludgy: there is no slashes at the end in the pkg-configure files, so it requires hacks at configure stage.

are you sure? ;)
I just noticed

all/luaposix-9999/ChangeLog.old:  * Deleted posix.lua loader file not needed anymore in Lua-5.1 module system

when grepped for posix.lua over build dir ;)

At least insofar as LUA_CPATH is concerned you can override the value that ax_lua.m4 guesses by setting ax_cv_lua_luaexecdir at configure time:
$ ./configure ax_cv_lua_luaexecdir=/lookee/here
...
checking for lua module directory... /lookee/here

yeah, ax_cv_lua_luadir and ax_cv_lua_luaexecdir does the trick.
Btw, a bit of offtop: I also noticed that documentation generation depends on ./configure to be executed before that (and, since ./configure runs separatelly for each lua target and multilib abi, it will be odd to generate all the same documentation for about 8 times in edge case).
So, I doing something like that:
    use doc && (
        cp build-aux/config.ld.in build-aux/config.ld
        cp lib/posix.lua.in lib/posix/init.lua
        sed -r \
            -e "s/@PACKAGE_STRING@/${P}/" \
            -i build-aux/config.ld.in lib/posix/init.lua
        mkdir -p doc
        ldoc -c build-aux/config.ld -d doc .
        rm build-aux/config.ld lib/posix/init.lua
    )

(where P is PACKAGE_NAME-PACKAGE_VERSION). Since, as diff says, only difference between .ins and "prepared" files is @PACKAGE_STRING@ replaced with luaposix 33.3.1. So, my curent behaviour here assumes, that there will not be any other things for autotools to prepare there ;) Is it okay, or do you planning to add something there someday? :)

No promises... but I can't think of anything that I might need to change; so it looks like you have a good solution there already :)


ImportError: keras.optimizers.legacy

I get this error. Calling Adam like that is not compatible anymore for Keras 3.
ImportError: keras.optimizers.legacy is not supported in Keras 3. When using tf.keras, to continue using a tf.keras.optimizers.legacy optimizer, you can install the tf_keras package (Keras 2) and set the environment variable TF_USE_LEGACY_KERAS=True to configure TensorFlow to use tf_keras when accessing tf.keras.

Hi, I am also getting this error. Tried different things, such as installing older versions of keras and tensorflow, but nothing has changed the error. Did you find a way to solve this, and use the nonlincausality package?


Tests for CASSANDRA-9961

I created two tests for CASSANDRA-9961, to describe materialized views in cqlsh.

Actually I converted one of the two tests to cover CASSANDRA-10348 as well.

These are great, thank you. Once @kishkaru drops some Doxygen knowledge on us, I'll be +1.

Never mind, Philip says it'll work. LGTM, merge away.

I've added one more test for CASSANDRA-10328 as well as more test cases for CASSANDRA-9961, which were requested during code review. Both CASSANDRA-10348 and CASSANDRA-10328 will be closed as duplicates of 9961.
Please review the latest commit as well, thanks!

Both new commits look good to me; if you like you can clean up one of the CQL strings as I mentioned in my comment. +1, thanks!

I cleaned up the quotes and squashed, thanks. You can merge now or wait for CASSANDRA-9961 to be committed (it should happen soon) and merge without the require tags.

Sorry for the delayed review. The most recent commit looks great, thank you!

Un-required and merged, thank you.


Upload to PyPI

Related to https://github.com/pbrady/fastcache/issues/47.
However, even without wheels, it would be good to upload the package to PyPI.
This solves this problem for me (and lots of others).

Thanks for opening the issue.  I'll try to do this in the next few days.

Done!


OSError: libstdc++.so.6: cannot open shared object file

I use Ubuntu on WSL2 and followed the installation guide in README but bumped following runtime errors.
winjii@DESKTOP-V3I03EF:~/sgmse$ python -m venv .venv
winjii@DESKTOP-V3I03EF:~/sgmse$ source .venv/bin/activate
(.venv) winjii@DESKTOP-V3I03EF:~/sgmse$ pip install -r requirements.txt
Requirement already satisfied: h5py==3.6.0 in ./.venv/lib/python3.8/site-packages (from -r requirements.txt (line 1)) (3.6.0)
Requirement already satisfied: ipympl==0.8.8 in ./.venv/lib/python3.8/site-packages (from -r requirements.txt (line 2)) (0.8.8)
Requirement already satisfied: ipywidgets==7.6.5 in ./.venv/lib/python3.8/site-packages (from -r requirements.txt (line 3)) (7.6.5)
Requirement already satisfied: jupyter==1.0.0 in ./.venv/lib/python3.8/site-packages (from -r requirements.txt (line 4)) (1.0.0)
Requirement already satisfied: jupyter-client==6.1.12 in ./.venv/lib/python3.8/site-packages (from -r requirements.txt (line 5)) (6.1.12)
Requirement already satisfied: jupyter-console==6.4.0 in ./.venv/lib/python3.8/site-packages (from -r requirements.txt (line 6)) (6.4.0)
Requirement already satisfied: jupyter-core==4.7.1 in ./.venv/lib/python3.8/site-packages (from -r requirements.txt (line 7)) (4.7.1)
Requirement already satisfied: jupyterlab-pygments==0.1.2 in ./.venv/lib/python3.8/site-packages (from -r requirements.txt (line 8)) (0.1.2)
Requirement already satisfied: jupyterlab-widgets==1.0.2 in ./.venv/lib/python3.8/site-packages (from -r requirements.txt (line 9)) (1.0.2)
Requirement already satisfied: librosa==0.9.1 in ./.venv/lib/python3.8/site-packages (from -r requirements.txt (line 10)) (0.9.1)
Requirement already satisfied: Ninja==<IP_ADDRESS> in ./.venv/lib/python3.8/site-packages (from -r requirements.txt (line 11)) (<IP_ADDRESS>)
Requirement already satisfied: numpy==1.22.2 in ./.venv/lib/python3.8/site-packages (from -r requirements.txt (line 12)) (1.22.2)
Requirement already satisfied: pandas==1.4.0 in ./.venv/lib/python3.8/site-packages (from -r requirements.txt (line 13)) (1.4.0)
Requirement already satisfied: pesq==0.0.4 in ./.venv/lib/python3.8/site-packages (from -r requirements.txt (line 14)) (0.0.4)
Requirement already satisfied: Pillow==9.0.1 in ./.venv/lib/python3.8/site-packages (from -r requirements.txt (line 15)) (9.0.1)
Requirement already satisfied: protobuf==3.19.4 in ./.venv/lib/python3.8/site-packages (from -r requirements.txt (line 16)) (3.19.4)
Requirement already satisfied: pyroomacoustics==0.6.0 in ./.venv/lib/python3.8/site-packages (from -r requirements.txt (line 17)) (0.6.0)
Requirement already satisfied: pystoi==0.3.3 in ./.venv/lib/python3.8/site-packages (from -r requirements.txt (line 18)) (0.3.3)
Requirement already satisfied: pytorch-lightning==1.6.5 in ./.venv/lib/python3.8/site-packages (from -r requirements.txt (line 19)) (1.6.5)
Requirement already satisfied: scipy==1.8.0 in ./.venv/lib/python3.8/site-packages (from -r requirements.txt (line 20)) (1.8.0)
Requirement already satisfied: sdeint==0.2.4 in ./.venv/lib/python3.8/site-packages (from -r requirements.txt (line 21)) (0.2.4)
Requirement already satisfied: setuptools==59.5.0 in ./.venv/lib/python3.8/site-packages (from -r requirements.txt (line 22)) (59.5.0)
Requirement already satisfied: seaborn==0.11.2 in ./.venv/lib/python3.8/site-packages (from -r requirements.txt (line 23)) (0.11.2)
Requirement already satisfied: torch==1.12.0 in ./.venv/lib/python3.8/site-packages (from -r requirements.txt (line 24)) (1.12.0)
Requirement already satisfied: torch-ema==0.3 in ./.venv/lib/python3.8/site-packages (from -r requirements.txt (line 25)) (0.3)
Requirement already satisfied: torchaudio==0.12.0 in ./.venv/lib/python3.8/site-packages (from -r requirements.txt (line 26)) (0.12.0)
Requirement already satisfied: torchvision==0.13.0 in ./.venv/lib/python3.8/site-packages (from -r requirements.txt (line 27)) (0.13.0)
Requirement already satisfied: torchinfo==1.6.3 in ./.venv/lib/python3.8/site-packages (from -r requirements.txt (line 28)) (1.6.3)
Requirement already satisfied: torchsde==0.2.5 in ./.venv/lib/python3.8/site-packages (from -r requirements.txt (line 29)) (0.2.5)
Requirement already satisfied: tqdm==4.63.0 in ./.venv/lib/python3.8/site-packages (from -r requirements.txt (line 30)) (4.63.0)
Requirement already satisfied: wandb==0.12.11 in ./.venv/lib/python3.8/site-packages (from -r requirements.txt (line 31)) (0.12.11)
Requirement already satisfied: matplotlib<4,>=2.0.0 in ./.venv/lib/python3.8/site-packages (from ipympl==0.8.8->-r requirements.txt (line 2)) (3.7.3)
Requirement already satisfied: traitlets<6 in ./.venv/lib/python3.8/site-packages (from ipympl==0.8.8->-r requirements.txt (line 2)) (5.10.0)
Requirement already satisfied: ipython<9 in ./.venv/lib/python3.8/site-packages (from ipympl==0.8.8->-r requirements.txt (line 2)) (8.12.2)
Requirement already satisfied: ipython-genutils in ./.venv/lib/python3.8/site-packages (from ipympl==0.8.8->-r requirements.txt (line 2)) (0.2.0)
Requirement already satisfied: nbformat>=4.2.0 in ./.venv/lib/python3.8/site-packages (from ipywidgets==7.6.5->-r requirements.txt (line 3)) (5.9.2)
Requirement already satisfied: widgetsnbextension~=3.5.0 in ./.venv/lib/python3.8/site-packages (from ipywidgets==7.6.5->-r requirements.txt (line 3)) (3.5.2)
Requirement already satisfied: ipykernel>=4.5.1 in ./.venv/lib/python3.8/site-packages (from ipywidgets==7.6.5->-r requirements.txt (line 3)) (6.20.2)
Requirement already satisfied: qtconsole in ./.venv/lib/python3.8/site-packages (from jupyter==1.0.0->-r requirements.txt (line 4)) (5.4.4)
Requirement already satisfied: nbconvert in ./.venv/lib/python3.8/site-packages (from jupyter==1.0.0->-r requirements.txt (line 4)) (7.8.0)
Requirement already satisfied: notebook in ./.venv/lib/python3.8/site-packages (from jupyter==1.0.0->-r requirements.txt (line 4)) (6.5.5)
Requirement already satisfied: python-dateutil>=2.1 in ./.venv/lib/python3.8/site-packages (from jupyter-client==6.1.12->-r requirements.txt (line 5)) (2.8.2)
Requirement already satisfied: pyzmq>=13 in ./.venv/lib/python3.8/site-packages (from jupyter-client==6.1.12->-r requirements.txt (line 5)) (24.0.1)
Requirement already satisfied: tornado>=4.1 in ./.venv/lib/python3.8/site-packages (from jupyter-client==6.1.12->-r requirements.txt (line 5)) (6.3.3)
Requirement already satisfied: pygments in ./.venv/lib/python3.8/site-packages (from jupyter-console==6.4.0->-r requirements.txt (line 6)) (2.16.1)
Requirement already satisfied: prompt-toolkit!=3.0.0,!=3.0.1,<3.1.0,>=2.0.0 in ./.venv/lib/python3.8/site-packages (from jupyter-console==6.4.0->-r requirements.txt (line 6)) (3.0.39)
Requirement already satisfied: audioread>=2.1.5 in ./.venv/lib/python3.8/site-packages (from librosa==0.9.1->-r requirements.txt (line 10)) (3.0.0)
Requirement already satisfied: decorator>=4.0.10 in ./.venv/lib/python3.8/site-packages (from librosa==0.9.1->-r requirements.txt (line 10)) (5.1.1)
Requirement already satisfied: pooch>=1.0 in ./.venv/lib/python3.8/site-packages (from librosa==0.9.1->-r requirements.txt (line 10)) (1.7.0)
Requirement already satisfied: packaging>=20.0 in ./.venv/lib/python3.8/site-packages (from librosa==0.9.1->-r requirements.txt (line 10)) (23.1)
Requirement already satisfied: joblib>=0.14 in ./.venv/lib/python3.8/site-packages (from librosa==0.9.1->-r requirements.txt (line 10)) (1.3.2)
Requirement already satisfied: soundfile>=0.10.2 in ./.venv/lib/python3.8/site-packages (from librosa==0.9.1->-r requirements.txt (line 10)) (0.12.1)
Requirement already satisfied: numba>=0.45.1 in ./.venv/lib/python3.8/site-packages (from librosa==0.9.1->-r requirements.txt (line 10)) (0.57.1)
Requirement already satisfied: scikit-learn>=0.19.1 in ./.venv/lib/python3.8/site-packages (from librosa==0.9.1->-r requirements.txt (line 10)) (1.3.0)
Requirement already satisfied: resampy>=0.2.2 in ./.venv/lib/python3.8/site-packages (from librosa==0.9.1->-r requirements.txt (line 10)) (0.4.2)
Requirement already satisfied: pytz>=2020.1 in ./.venv/lib/python3.8/site-packages (from pandas==1.4.0->-r requirements.txt (line 13)) (2023.3.post1)
Requirement already satisfied: Cython in ./.venv/lib/python3.8/site-packages (from pyroomacoustics==0.6.0->-r requirements.txt (line 17)) (3.0.2)
Requirement already satisfied: pybind11>=2.2 in ./.venv/lib/python3.8/site-packages (from pyroomacoustics==0.6.0->-r requirements.txt (line 17)) (2.11.1)
Requirement already satisfied: PyYAML>=5.4 in ./.venv/lib/python3.8/site-packages (from pytorch-lightning==1.6.5->-r requirements.txt (line 19)) (6.0.1)
Requirement already satisfied: typing-extensions>=4.0.0 in ./.venv/lib/python3.8/site-packages (from pytorch-lightning==1.6.5->-r requirements.txt (line 19)) (4.8.0)
Requirement already satisfied: tensorboard>=2.2.0 in ./.venv/lib/python3.8/site-packages (from pytorch-lightning==1.6.5->-r requirements.txt (line 19)) (2.11.2)
Requirement already satisfied: torchmetrics>=0.4.1 in ./.venv/lib/python3.8/site-packages (from pytorch-lightning==1.6.5->-r requirements.txt (line 19)) (1.1.2)
Requirement already satisfied: pyDeprecate>=0.3.1 in ./.venv/lib/python3.8/site-packages (from pytorch-lightning==1.6.5->-r requirements.txt (line 19)) (0.3.2)
Requirement already satisfied: fsspec[http]!=2021.06.0,>=2021.05.0 in ./.venv/lib/python3.8/site-packages (from pytorch-lightning==1.6.5->-r requirements.txt (line 19)) (2023.9.1)
Requirement already satisfied: requests in ./.venv/lib/python3.8/site-packages (from torchvision==0.13.0->-r requirements.txt (line 27)) (2.31.0)
Requirement already satisfied: boltons>=20.2.1 in ./.venv/lib/python3.8/site-packages (from torchsde==0.2.5->-r requirements.txt (line 29)) (23.0.0)
Requirement already satisfied: trampoline>=0.1.2 in ./.venv/lib/python3.8/site-packages (from torchsde==0.2.5->-r requirements.txt (line 29)) (0.1.2)
Requirement already satisfied: Click!=8.0.0,>=7.0 in ./.venv/lib/python3.8/site-packages (from wandb==0.12.11->-r requirements.txt (line 31)) (8.1.7)
Requirement already satisfied: pathtools in ./.venv/lib/python3.8/site-packages (from wandb==0.12.11->-r requirements.txt (line 31)) (0.1.2)
Requirement already satisfied: promise<3,>=2.0 in ./.venv/lib/python3.8/site-packages (from wandb==0.12.11->-r requirements.txt (line 31)) (2.3)
Requirement already satisfied: yaspin>=1.0.0 in ./.venv/lib/python3.8/site-packages (from wandb==0.12.11->-r requirements.txt (line 31)) (2.5.0)
Requirement already satisfied: psutil>=5.0.0 in ./.venv/lib/python3.8/site-packages (from wandb==0.12.11->-r requirements.txt (line 31)) (5.9.5)
Requirement already satisfied: setproctitle in ./.venv/lib/python3.8/site-packages (from wandb==0.12.11->-r requirements.txt (line 31)) (1.3.2)
Requirement already satisfied: GitPython>=1.0.0 in ./.venv/lib/python3.8/site-packages (from wandb==0.12.11->-r requirements.txt (line 31)) (3.1.36)
Requirement already satisfied: shortuuid>=0.5.0 in ./.venv/lib/python3.8/site-packages (from wandb==0.12.11->-r requirements.txt (line 31)) (1.0.11)
Requirement already satisfied: six>=1.13.0 in ./.venv/lib/python3.8/site-packages (from wandb==0.12.11->-r requirements.txt (line 31)) (1.16.0)
Requirement already satisfied: sentry-sdk>=1.0.0 in ./.venv/lib/python3.8/site-packages (from wandb==0.12.11->-r requirements.txt (line 31)) (1.31.0)
Requirement already satisfied: docker-pycreds>=0.4.0 in ./.venv/lib/python3.8/site-packages (from wandb==0.12.11->-r requirements.txt (line 31)) (0.4.0)
Requirement already satisfied: aiohttp!=4.0.0a0,!=4.0.0a1 in ./.venv/lib/python3.8/site-packages (from fsspec[http]!=2021.06.0,>=2021.05.0->pytorch-lightning==1.6.5->-r requirements.txt (line 19)) (3.8.5)
Requirement already satisfied: gitdb<5,>=4.0.1 in ./.venv/lib/python3.8/site-packages (from GitPython>=1.0.0->wandb==0.12.11->-r requirements.txt (line 31)) (4.0.10)
Requirement already satisfied: debugpy>=1.0 in ./.venv/lib/python3.8/site-packages (from ipykernel>=4.5.1->ipywidgets==7.6.5->-r requirements.txt (line 3)) (1.8.0)
Requirement already satisfied: nest-asyncio in ./.venv/lib/python3.8/site-packages (from ipykernel>=4.5.1->ipywidgets==7.6.5->-r requirements.txt (line 3)) (1.5.8)
Requirement already satisfied: comm>=0.1.1 in ./.venv/lib/python3.8/site-packages (from ipykernel>=4.5.1->ipywidgets==7.6.5->-r requirements.txt (line 3)) (0.1.4)
Requirement already satisfied: matplotlib-inline>=0.1 in ./.venv/lib/python3.8/site-packages (from ipykernel>=4.5.1->ipywidgets==7.6.5->-r requirements.txt (line 3)) (0.1.6)
Requirement already satisfied: backcall in ./.venv/lib/python3.8/site-packages (from ipython<9->ipympl==0.8.8->-r requirements.txt (line 2)) (0.2.0)
Requirement already satisfied: stack-data in ./.venv/lib/python3.8/site-packages (from ipython<9->ipympl==0.8.8->-r requirements.txt (line 2)) (0.6.2)
Requirement already satisfied: pickleshare in ./.venv/lib/python3.8/site-packages (from ipython<9->ipympl==0.8.8->-r requirements.txt (line 2)) (0.7.5)
Requirement already satisfied: pexpect>4.3 in ./.venv/lib/python3.8/site-packages (from ipython<9->ipympl==0.8.8->-r requirements.txt (line 2)) (4.8.0)
Requirement already satisfied: jedi>=0.16 in ./.venv/lib/python3.8/site-packages (from ipython<9->ipympl==0.8.8->-r requirements.txt (line 2)) (0.19.0)
Requirement already satisfied: contourpy>=1.0.1 in ./.venv/lib/python3.8/site-packages (from matplotlib<4,>=2.0.0->ipympl==0.8.8->-r requirements.txt (line 2)) (1.1.1)
Requirement already satisfied: fonttools>=4.22.0 in ./.venv/lib/python3.8/site-packages (from matplotlib<4,>=2.0.0->ipympl==0.8.8->-r requirements.txt (line 2)) (4.42.1)
Requirement already satisfied: pyparsing>=2.3.1 in ./.venv/lib/python3.8/site-packages (from matplotlib<4,>=2.0.0->ipympl==0.8.8->-r requirements.txt (line 2)) (3.1.1)
Requirement already satisfied: kiwisolver>=1.0.1 in ./.venv/lib/python3.8/site-packages (from matplotlib<4,>=2.0.0->ipympl==0.8.8->-r requirements.txt (line 2)) (1.4.5)
Requirement already satisfied: cycler>=0.10 in ./.venv/lib/python3.8/site-packages (from matplotlib<4,>=2.0.0->ipympl==0.8.8->-r requirements.txt (line 2)) (0.11.0)
Requirement already satisfied: importlib-resources>=3.2.0 in ./.venv/lib/python3.8/site-packages (from matplotlib<4,>=2.0.0->ipympl==0.8.8->-r requirements.txt (line 2)) (6.0.1)
Requirement already satisfied: jsonschema>=2.6 in ./.venv/lib/python3.8/site-packages (from nbformat>=4.2.0->ipywidgets==7.6.5->-r requirements.txt (line 3)) (4.19.0)
Requirement already satisfied: fastjsonschema in ./.venv/lib/python3.8/site-packages (from nbformat>=4.2.0->ipywidgets==7.6.5->-r requirements.txt (line 3)) (2.18.0)
Requirement already satisfied: importlib-metadata in ./.venv/lib/python3.8/site-packages (from numba>=0.45.1->librosa==0.9.1->-r requirements.txt (line 10)) (6.8.0)
Requirement already satisfied: llvmlite<0.41,>=0.40.0dev0 in ./.venv/lib/python3.8/site-packages (from numba>=0.45.1->librosa==0.9.1->-r requirements.txt (line 10)) (0.40.1)
Requirement already satisfied: platformdirs>=2.5.0 in ./.venv/lib/python3.8/site-packages (from pooch>=1.0->librosa==0.9.1->-r requirements.txt (line 10)) (3.10.0)
Requirement already satisfied: wcwidth in ./.venv/lib/python3.8/site-packages (from prompt-toolkit!=3.0.0,!=3.0.1,<3.1.0,>=2.0.0->jupyter-console==6.4.0->-r requirements.txt (line 6)) (0.2.6)
Requirement already satisfied: certifi>=2017.4.17 in ./.venv/lib/python3.8/site-packages (from requests->torchvision==0.13.0->-r requirements.txt (line 27)) (2023.7.22)
Requirement already satisfied: idna<4,>=2.5 in ./.venv/lib/python3.8/site-packages (from requests->torchvision==0.13.0->-r requirements.txt (line 27)) (3.4)
Requirement already satisfied: urllib3<3,>=1.21.1 in ./.venv/lib/python3.8/site-packages (from requests->torchvision==0.13.0->-r requirements.txt (line 27)) (1.26.16)
Requirement already satisfied: charset-normalizer<4,>=2 in ./.venv/lib/python3.8/site-packages (from requests->torchvision==0.13.0->-r requirements.txt (line 27)) (3.2.0)
Requirement already satisfied: threadpoolctl>=2.0.0 in ./.venv/lib/python3.8/site-packages (from scikit-learn>=0.19.1->librosa==0.9.1->-r requirements.txt (line 10)) (3.2.0)
Requirement already satisfied: cffi>=1.0 in ./.venv/lib/python3.8/site-packages (from soundfile>=0.10.2->librosa==0.9.1->-r requirements.txt (line 10)) (1.15.1)
Requirement already satisfied: grpcio>=1.24.3 in ./.venv/lib/python3.8/site-packages (from tensorboard>=2.2.0->pytorch-lightning==1.6.5->-r requirements.txt (line 19)) (1.58.0)
Requirement already satisfied: markdown>=2.6.8 in ./.venv/lib/python3.8/site-packages (from tensorboard>=2.2.0->pytorch-lightning==1.6.5->-r requirements.txt (line 19)) (3.4.4)
Requirement already satisfied: google-auth<3,>=1.6.3 in ./.venv/lib/python3.8/site-packages (from tensorboard>=2.2.0->pytorch-lightning==1.6.5->-r requirements.txt (line 19)) (2.23.0)
Requirement already satisfied: tensorboard-data-server<0.7.0,>=0.6.0 in ./.venv/lib/python3.8/site-packages (from tensorboard>=2.2.0->pytorch-lightning==1.6.5->-r requirements.txt (line 19)) (0.6.1)
Requirement already satisfied: google-auth-oauthlib<0.5,>=0.4.1 in ./.venv/lib/python3.8/site-packages (from tensorboard>=2.2.0->pytorch-lightning==1.6.5->-r requirements.txt (line 19)) (0.4.6)
Requirement already satisfied: absl-py>=0.4 in ./.venv/lib/python3.8/site-packages (from tensorboard>=2.2.0->pytorch-lightning==1.6.5->-r requirements.txt (line 19)) (1.4.0)
Requirement already satisfied: tensorboard-plugin-wit>=1.6.0 in ./.venv/lib/python3.8/site-packages (from tensorboard>=2.2.0->pytorch-lightning==1.6.5->-r requirements.txt (line 19)) (1.8.1)
Requirement already satisfied: werkzeug>=1.0.1 in ./.venv/lib/python3.8/site-packages (from tensorboard>=2.2.0->pytorch-lightning==1.6.5->-r requirements.txt (line 19)) (2.3.7)
Requirement already satisfied: wheel>=0.26 in ./.venv/lib/python3.8/site-packages (from tensorboard>=2.2.0->pytorch-lightning==1.6.5->-r requirements.txt (line 19)) (0.41.2)
Requirement already satisfied: lightning-utilities>=0.8.0 in ./.venv/lib/python3.8/site-packages (from torchmetrics>=0.4.1->pytorch-lightning==1.6.5->-r requirements.txt (line 19)) (0.9.0)
Requirement already satisfied: argon2-cffi in ./.venv/lib/python3.8/site-packages (from notebook->jupyter==1.0.0->-r requirements.txt (line 4)) (23.1.0)
Requirement already satisfied: nbclassic>=0.4.7 in ./.venv/lib/python3.8/site-packages (from notebook->jupyter==1.0.0->-r requirements.txt (line 4)) (1.0.0)
Requirement already satisfied: Send2Trash>=1.8.0 in ./.venv/lib/python3.8/site-packages (from notebook->jupyter==1.0.0->-r requirements.txt (line 4)) (1.8.2)
Requirement already satisfied: prometheus-client in ./.venv/lib/python3.8/site-packages (from notebook->jupyter==1.0.0->-r requirements.txt (line 4)) (0.17.1)
Requirement already satisfied: terminado>=0.8.3 in ./.venv/lib/python3.8/site-packages (from notebook->jupyter==1.0.0->-r requirements.txt (line 4)) (0.17.1)
Requirement already satisfied: jinja2 in ./.venv/lib/python3.8/site-packages (from notebook->jupyter==1.0.0->-r requirements.txt (line 4)) (3.1.2)
Requirement already satisfied: markupsafe>=2.0 in ./.venv/lib/python3.8/site-packages (from nbconvert->jupyter==1.0.0->-r requirements.txt (line 4)) (2.1.3)
Requirement already satisfied: beautifulsoup4 in ./.venv/lib/python3.8/site-packages (from nbconvert->jupyter==1.0.0->-r requirements.txt (line 4)) (4.12.2)
Requirement already satisfied: mistune<4,>=2.0.3 in ./.venv/lib/python3.8/site-packages (from nbconvert->jupyter==1.0.0->-r requirements.txt (line 4)) (3.0.1)
Requirement already satisfied: defusedxml in ./.venv/lib/python3.8/site-packages (from nbconvert->jupyter==1.0.0->-r requirements.txt (line 4)) (0.7.1)
Requirement already satisfied: pandocfilters>=1.4.1 in ./.venv/lib/python3.8/site-packages (from nbconvert->jupyter==1.0.0->-r requirements.txt (line 4)) (1.5.0)
Requirement already satisfied: tinycss2 in ./.venv/lib/python3.8/site-packages (from nbconvert->jupyter==1.0.0->-r requirements.txt (line 4)) (1.2.1)
Requirement already satisfied: bleach!=5.0.0 in ./.venv/lib/python3.8/site-packages (from nbconvert->jupyter==1.0.0->-r requirements.txt (line 4)) (6.0.0)
Requirement already satisfied: nbclient>=0.5.0 in ./.venv/lib/python3.8/site-packages (from nbconvert->jupyter==1.0.0->-r requirements.txt (line 4)) (0.7.0)
Requirement already satisfied: termcolor<3.0,>=2.3 in ./.venv/lib/python3.8/site-packages (from yaspin>=1.0.0->wandb==0.12.11->-r requirements.txt (line 31)) (2.3.0)
Requirement already satisfied: qtpy>=2.4.0 in ./.venv/lib/python3.8/site-packages (from qtconsole->jupyter==1.0.0->-r requirements.txt (line 4)) (2.4.0)
Requirement already satisfied: frozenlist>=1.1.1 in ./.venv/lib/python3.8/site-packages (from aiohttp!=4.0.0a0,!=4.0.0a1->fsspec[http]!=2021.06.0,>=2021.05.0->pytorch-lightning==1.6.5->-r requirements.txt (line 19)) (1.4.0)
Requirement already satisfied: attrs>=17.3.0 in ./.venv/lib/python3.8/site-packages (from aiohttp!=4.0.0a0,!=4.0.0a1->fsspec[http]!=2021.06.0,>=2021.05.0->pytorch-lightning==1.6.5->-r requirements.txt (line 19)) (23.1.0)
Requirement already satisfied: aiosignal>=1.1.2 in ./.venv/lib/python3.8/site-packages (from aiohttp!=4.0.0a0,!=4.0.0a1->fsspec[http]!=2021.06.0,>=2021.05.0->pytorch-lightning==1.6.5->-r requirements.txt (line 19)) (1.3.1)
Requirement already satisfied: async-timeout<5.0,>=4.0.0a3 in ./.venv/lib/python3.8/site-packages (from aiohttp!=4.0.0a0,!=4.0.0a1->fsspec[http]!=2021.06.0,>=2021.05.0->pytorch-lightning==1.6.5->-r requirements.txt (line 19)) (4.0.3)
Requirement already satisfied: yarl<2.0,>=1.0 in ./.venv/lib/python3.8/site-packages (from aiohttp!=4.0.0a0,!=4.0.0a1->fsspec[http]!=2021.06.0,>=2021.05.0->pytorch-lightning==1.6.5->-r requirements.txt (line 19)) (1.9.2)
Requirement already satisfied: multidict<7.0,>=4.5 in ./.venv/lib/python3.8/site-packages (from aiohttp!=4.0.0a0,!=4.0.0a1->fsspec[http]!=2021.06.0,>=2021.05.0->pytorch-lightning==1.6.5->-r requirements.txt (line 19)) (6.0.4)
Requirement already satisfied: webencodings in ./.venv/lib/python3.8/site-packages (from bleach!=5.0.0->nbconvert->jupyter==1.0.0->-r requirements.txt (line 4)) (0.5.1)
Requirement already satisfied: pycparser in ./.venv/lib/python3.8/site-packages (from cffi>=1.0->soundfile>=0.10.2->librosa==0.9.1->-r requirements.txt (line 10)) (2.21)
Requirement already satisfied: smmap<6,>=3.0.1 in ./.venv/lib/python3.8/site-packages (from gitdb<5,>=4.0.1->GitPython>=1.0.0->wandb==0.12.11->-r requirements.txt (line 31)) (5.0.1)
Requirement already satisfied: rsa<5,>=3.1.4 in ./.venv/lib/python3.8/site-packages (from google-auth<3,>=1.6.3->tensorboard>=2.2.0->pytorch-lightning==1.6.5->-r requirements.txt (line 19)) (4.9)
Requirement already satisfied: pyasn1-modules>=0.2.1 in ./.venv/lib/python3.8/site-packages (from google-auth<3,>=1.6.3->tensorboard>=2.2.0->pytorch-lightning==1.6.5->-r requirements.txt (line 19)) (0.3.0)
Requirement already satisfied: cachetools<6.0,>=2.0.0 in ./.venv/lib/python3.8/site-packages (from google-auth<3,>=1.6.3->tensorboard>=2.2.0->pytorch-lightning==1.6.5->-r requirements.txt (line 19)) (5.3.1)
Requirement already satisfied: requests-oauthlib>=0.7.0 in ./.venv/lib/python3.8/site-packages (from google-auth-oauthlib<0.5,>=0.4.1->tensorboard>=2.2.0->pytorch-lightning==1.6.5->-r requirements.txt (line 19)) (1.3.1)
Requirement already satisfied: zipp>=0.5 in ./.venv/lib/python3.8/site-packages (from importlib-metadata->numba>=0.45.1->librosa==0.9.1->-r requirements.txt (line 10)) (3.16.2)
Requirement already satisfied: parso<0.9.0,>=0.8.3 in ./.venv/lib/python3.8/site-packages (from jedi>=0.16->ipython<9->ipympl==0.8.8->-r requirements.txt (line 2)) (0.8.3)
Requirement already satisfied: jsonschema-specifications>=2023.03.6 in ./.venv/lib/python3.8/site-packages (from jsonschema>=2.6->nbformat>=4.2.0->ipywidgets==7.6.5->-r requirements.txt (line 3)) (2023.7.1)
Requirement already satisfied: rpds-py>=0.7.1 in ./.venv/lib/python3.8/site-packages (from jsonschema>=2.6->nbformat>=4.2.0->ipywidgets==7.6.5->-r requirements.txt (line 3)) (0.10.3)
Requirement already satisfied: referencing>=0.28.4 in ./.venv/lib/python3.8/site-packages (from jsonschema>=2.6->nbformat>=4.2.0->ipywidgets==7.6.5->-r requirements.txt (line 3)) (0.30.2)
Requirement already satisfied: pkgutil-resolve-name>=1.3.10 in ./.venv/lib/python3.8/site-packages (from jsonschema>=2.6->nbformat>=4.2.0->ipywidgets==7.6.5->-r requirements.txt (line 3)) (1.3.10)
Requirement already satisfied: notebook-shim>=0.2.3 in ./.venv/lib/python3.8/site-packages (from nbclassic>=0.4.7->notebook->jupyter==1.0.0->-r requirements.txt (line 4)) (0.2.3)
Requirement already satisfied: jupyter-server>=1.8 in ./.venv/lib/python3.8/site-packages (from nbclassic>=0.4.7->notebook->jupyter==1.0.0->-r requirements.txt (line 4)) (1.23.4)
Requirement already satisfied: ptyprocess>=0.5 in ./.venv/lib/python3.8/site-packages (from pexpect>4.3->ipython<9->ipympl==0.8.8->-r requirements.txt (line 2)) (0.7.0)
Requirement already satisfied: argon2-cffi-bindings in ./.venv/lib/python3.8/site-packages (from argon2-cffi->notebook->jupyter==1.0.0->-r requirements.txt (line 4)) (21.2.0)
Requirement already satisfied: soupsieve>1.2 in ./.venv/lib/python3.8/site-packages (from beautifulsoup4->nbconvert->jupyter==1.0.0->-r requirements.txt (line 4)) (2.5)
Requirement already satisfied: asttokens>=2.1.0 in ./.venv/lib/python3.8/site-packages (from stack-data->ipython<9->ipympl==0.8.8->-r requirements.txt (line 2)) (2.4.0)
Requirement already satisfied: pure-eval in ./.venv/lib/python3.8/site-packages (from stack-data->ipython<9->ipympl==0.8.8->-r requirements.txt (line 2)) (0.2.2)
Requirement already satisfied: executing>=1.2.0 in ./.venv/lib/python3.8/site-packages (from stack-data->ipython<9->ipympl==0.8.8->-r requirements.txt (line 2)) (1.2.0)
Requirement already satisfied: websocket-client in ./.venv/lib/python3.8/site-packages (from jupyter-server>=1.8->nbclassic>=0.4.7->notebook->jupyter==1.0.0->-r requirements.txt (line 4)) (1.6.3)
Requirement already satisfied: anyio<4,>=3.1.0 in ./.venv/lib/python3.8/site-packages (from jupyter-server>=1.8->nbclassic>=0.4.7->notebook->jupyter==1.0.0->-r requirements.txt (line 4)) (3.7.1)
Requirement already satisfied: pyasn1<0.6.0,>=0.4.6 in ./.venv/lib/python3.8/site-packages (from pyasn1-modules>=0.2.1->google-auth<3,>=1.6.3->tensorboard>=2.2.0->pytorch-lightning==1.6.5->-r requirements.txt (line 19)) (0.5.0)
Requirement already satisfied: oauthlib>=3.0.0 in ./.venv/lib/python3.8/site-packages (from requests-oauthlib>=0.7.0->google-auth-oauthlib<0.5,>=0.4.1->tensorboard>=2.2.0->pytorch-lightning==1.6.5->-r requirements.txt (line 19)) (3.2.2)
Requirement already satisfied: exceptiongroup in ./.venv/lib/python3.8/site-packages (from anyio<4,>=3.1.0->jupyter-server>=1.8->nbclassic>=0.4.7->notebook->jupyter==1.0.0->-r requirements.txt (line 4)) (1.1.3)
Requirement already satisfied: sniffio>=1.1 in ./.venv/lib/python3.8/site-packages (from anyio<4,>=3.1.0->jupyter-server>=1.8->nbclassic>=0.4.7->notebook->jupyter==1.0.0->-r requirements.txt (line 4)) (1.3.0)

[notice] A new release of pip is available: 23.0.1 -> 23.2.1
[notice] To update, run: pip install --upgrade pip
(.venv) winjii@DESKTOP-V3I03EF:~/sgmse$ python enhancement.py --test_dir . --enhanced_dir clean --ckpt checkpoints/train
_vb_29nqe0uh_epoch=115.ckpt
Traceback (most recent call last):
  File "enhancement.py", line 5, in <module>
    import torch
  File "/home/winjii/sgmse/.venv/lib/python3.8/site-packages/torch/__init__.py", line 201, in <module>
    _load_global_deps()
  File "/home/winjii/sgmse/.venv/lib/python3.8/site-packages/torch/__init__.py", line 154, in _load_global_deps
    ctypes.CDLL(lib_path, mode=ctypes.RTLD_GLOBAL)
  File "/nix/store/p4d6y5cic9070wyv4z508mpvdrn5f4yp-python3-3.8.18/lib/python3.8/ctypes/__init__.py", line 373, in __init__
    self._handle = _dlopen(self._name, mode)
OSError: libstdc++.so.6: cannot open shared object file: No such file or directory

After adding libraries that include libstdc++.so.6, another error occurs.
(.venv) winjii@DESKTOP-V3I03EF:~/sgmse$ ls $LD_LIBRARY_PATH
libasan.la          libgomp.la        liblsan.so.0          libssp_nonshared.la         libtsan.so.2
libasan.so          libgomp.so        liblsan.so.0.0.0      libstdc++.la                libtsan.so.2.0.0
libasan.so.8        libgomp.so.1      libquadmath.la        libstdc++.so                libubsan.la
libasan.so.8.0.0    libgomp.so.1.0.0  libquadmath.so        libstdc++.so.6              libubsan.so
libatomic.la        libitm.la         libquadmath.so.0      libstdc++.so.6.0.30         libubsan.so.1
libatomic.so        libitm.so         libquadmath.so.0.0.0  libstdc++.so.6.0.30-gdb.py  libubsan.so.1.0.0
libatomic.so.1      libitm.so.1       libssp.la             libstdc++fs.la
libatomic.so.1.2.0  libitm.so.1.0.0   libssp.so             libsupc++.la
libgcc_s.so         liblsan.la        libssp.so.0           libtsan.la
libgcc_s.so.1       liblsan.so        libssp.so.0.0.0       libtsan.so
(.venv) winjii@DESKTOP-V3I03EF:~/sgmse$ python enhancement.py --test_dir . --enhanced_dir clean --ckpt checkpoints/train_vb_29nqe0uh_epoch=115.ckpt
Traceback (most recent call last):
  File "enhancement.py", line 10, in <module>
    from sgmse.model import ScoreModel
  File "/home/winjii/sgmse/sgmse/model.py", line 6, in <module>
    import pytorch_lightning as pl
  File "/home/winjii/sgmse/.venv/lib/python3.8/site-packages/pytorch_lightning/__init__.py", line 30, in <module>
    from pytorch_lightning.callbacks import Callback  # noqa: E402
  File "/home/winjii/sgmse/.venv/lib/python3.8/site-packages/pytorch_lightning/callbacks/__init__.py", line 14, in <module>
    from pytorch_lightning.callbacks.base import Callback
  File "/home/winjii/sgmse/.venv/lib/python3.8/site-packages/pytorch_lightning/callbacks/base.py", line 25, in <module>
    from pytorch_lightning.utilities.types import STEP_OUTPUT
  File "/home/winjii/sgmse/.venv/lib/python3.8/site-packages/pytorch_lightning/utilities/types.py", line 26, in <module>
    from torchmetrics import Metric
  File "/home/winjii/sgmse/.venv/lib/python3.8/site-packages/torchmetrics/__init__.py", line 14, in <module>
    from torchmetrics import functional  # noqa: E402
  File "/home/winjii/sgmse/.venv/lib/python3.8/site-packages/torchmetrics/functional/__init__.py", line 14, in <module>
    from torchmetrics.functional.audio._deprecated import _permutation_invariant_training as permutation_invariant_training
  File "/home/winjii/sgmse/.venv/lib/python3.8/site-packages/torchmetrics/functional/audio/__init__.py", line 45, in <module>
    from torchmetrics.functional.audio.pesq import perceptual_evaluation_speech_quality  # noqa: F401
  File "/home/winjii/sgmse/.venv/lib/python3.8/site-packages/torchmetrics/functional/audio/pesq.py", line 22, in <module>
    import pesq as pesq_backend
  File "/home/winjii/sgmse/.venv/lib/python3.8/site-packages/pesq/__init__.py", line 5, in <module>
    from ._pesq import pesq, pesq_batch
  File "/home/winjii/sgmse/.venv/lib/python3.8/site-packages/pesq/_pesq.py", line 8, in <module>
    from .cypesq import cypesq, cypesq_retvals, cypesq_error_message as pesq_error_message
  File "pesq/cypesq.pyx", line 1, in init cypesq
ImportError: numpy.core.multiarray failed to import (auto-generated because you didn't call 'numpy.import_array()' after cimporting numpy; use '<void>numpy._import_array' to disable if you are certain you don't need it).

What requirements are missing in my environment?
versions:
winjii@DESKTOP-V3I03EF:~/sgmse$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 18.04.6 LTS
Release:        18.04
Codename:       bionic
winjii@DESKTOP-V3I03EF:~/sgmse$ python --version
Python 3.8.18

Hi there, thank you for your interest in our work! Unfortunately I don't have a direct answer for you, this has never occurred for us and is not directly related to our code. There don't seem to be any missing dependencies. I'd suggest searching the internet for the last error message

ImportError: numpy.core.multiarray failed to import

One guess on where the problem arose is that you installed the libraries containing libstd++.so.6 after installing the Python dependencies, so they may now be incompatible with the system libraries. You could try fixing it by setting up the entire venv again after you've installed the libraries containing libstd++.so.6, making sure that they're in your LD_LIBRARY_PATH while running any pip or python commands used for dependency installation.

I experienced the same error and upgrading numpy to the latest version fixed the error.

Thanks your cooperation.
It went to the same error to try re-installing python and pip after putting libstd++.so.6.
Updating numpy to 1.23.0 from 1.22.2, and the error message changed.
(.venv) winjii@DESKTOP-V3I03EF:~/sgmse$ python enhancement.py --test_dir . --enhanced_dir clean --ckpt checkpoints/train_vb_29nqe0uh_epoch=115.ckpt
/home/winjii/sgmse/.venv/lib/python3.8/site-packages/ninja/data/bin/ninja: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by /nix/store/xpxln7rqi3pq4m0xpnawhxb2gs0mn1s0-gcc-12.3.0-lib/lib/libstdc++.so.6)
/home/winjii/sgmse/.venv/lib/python3.8/site-packages/ninja/data/bin/ninja: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by /nix/store/xpxln7rqi3pq4m0xpnawhxb2gs0mn1s0-gcc-12.3.0-lib/lib/libstdc++.so.6)
/home/winjii/sgmse/.venv/lib/python3.8/site-packages/ninja/data/bin/ninja: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.36' not found (required by /nix/store/xpxln7rqi3pq4m0xpnawhxb2gs0mn1s0-gcc-12.3.0-lib/lib/libstdc++.so.6)
/home/winjii/sgmse/.venv/lib/python3.8/site-packages/ninja/data/bin/ninja: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /nix/store/xpxln7rqi3pq4m0xpnawhxb2gs0mn1s0-gcc-12.3.0-lib/lib/libstdc++.so.6)
/home/winjii/sgmse/.venv/lib/python3.8/site-packages/ninja/data/bin/ninja: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.35' not found (required by /nix/store/xpxln7rqi3pq4m0xpnawhxb2gs0mn1s0-gcc-12.3.0-lib/lib/libgcc_s.so.1)
/home/winjii/sgmse/.venv/lib/python3.8/site-packages/ninja/data/bin/ninja: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /nix/store/xpxln7rqi3pq4m0xpnawhxb2gs0mn1s0-gcc-12.3.0-lib/lib/libgcc_s.so.1)
Traceback (most recent call last):
  File "enhancement.py", line 10, in <module>
    from sgmse.model import ScoreModel
  File "/home/winjii/sgmse/sgmse/model.py", line 11, in <module>
    from sgmse.backbones import BackboneRegistry
  File "/home/winjii/sgmse/sgmse/backbones/__init__.py", line 2, in <module>
    from .ncsnpp import NCSNpp
  File "/home/winjii/sgmse/sgmse/backbones/ncsnpp.py", line 18, in <module>
    from .ncsnpp_utils import layers, layerspp, normalization
  File "/home/winjii/sgmse/sgmse/backbones/ncsnpp_utils/layerspp.py", line 20, in <module>
    from . import up_or_down_sampling
  File "/home/winjii/sgmse/sgmse/backbones/ncsnpp_utils/up_or_down_sampling.py", line 10, in <module>
    from .op import upfirdn2d
  File "/home/winjii/sgmse/sgmse/backbones/ncsnpp_utils/op/__init__.py", line 1, in <module>
    from .fused_act import FusedLeakyReLU, fused_leaky_relu
  File "/home/winjii/sgmse/sgmse/backbones/ncsnpp_utils/op/fused_act.py", line 11, in <module>
    fused = load(
  File "/home/winjii/sgmse/.venv/lib/python3.8/site-packages/torch/utils/cpp_extension.py", line 1202, in load
    return _jit_compile(
  File "/home/winjii/sgmse/.venv/lib/python3.8/site-packages/torch/utils/cpp_extension.py", line 1425, in _jit_compile
    _write_ninja_file_and_build_library(
  File "/home/winjii/sgmse/.venv/lib/python3.8/site-packages/torch/utils/cpp_extension.py", line 1506, in _write_ninja_file_and_build_library
    verify_ninja_availability()
  File "/home/winjii/sgmse/.venv/lib/python3.8/site-packages/torch/utils/cpp_extension.py", line 1562, in verify_ninja_availability
    raise RuntimeError("Ninja is required to load C++ extensions")
RuntimeError: Ninja is required to load C++ extensions

Ninja is already contained by requirements.txt so I have no idea to resolve this error.
I notify progress if it would made.

Hi, the top few lines in your output suggest that GLIBC is not properly installed / not accessible by Ninja. I'm afraid I'm not able to help you with this as it seems like a problem specific to the build system set up in your WSL install, or specific to WSL in general. You may have more luck asking in pytorch/pytorch GitHub issues or PyTorch-related channels/forums, or in the repos where the relevant code originates:

Yang Song's score_sde_pytorch https://github.com/yang-song/score_sde_pytorch
StyleGAN2 https://github.com/NVlabs/stylegan2

Just to let you know, we have updated the code to PyTorch 2.X and Lightning 2.X to ensure support for newer GPUs. In the updated requirements.txt file, we haven't specified fixed versions for the required packages to allow pip to handle resolution autonomously. Please run the code again after you have created a virtual environment with the new requirements.


[Bug]: Add a CodeQL Workflow

Give a brief about the bug ✍
The repository has javascript code, but it lacks workflow for code inspection.
What is the expected behavior? 🤔
The codeql.yml workflow file will be added by me to automate security checks.
CodeQL is a code analysis tool, to find vulnerabilities in programs.
Provide step by step information reproduce the bug 📄
The code will be examined, and the results will be presented as code scanning alerts.
Every push, commit, and pull request that uses GitHub actions will have it enabled.
I want to work on this issue under GSSoC'23
Select program in which you are contributing
GSSoC23
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

Hey @abhinav-m22 !
Thank you for raising an issue 💗
You can self assign the issue by commenting /assign in comment 😀
Make sure you follow CODE OF CONDUCT and CONTRIBUTING GUIDELINES 🚀
Don’t Forget to ⭐ our GameZone🎮
Make sure you join our Discord🕹

Hey @abhinav-m22 ! Thank you so much for your raising the issue💗
It’s all yours, you can come anytime again and make some contributions! 🚀
Alone, we can do little, but together we can do so much! 😇


Exception in thread "main" java.lang.UnsatisfiedLinkError: C:\Users\Luke\AppData\Local\Temp\tensorflow_native_libraries-1529547871141-0\tensorflow_jni.dll:  U

I have search on SO what could be the reason why i am having this issue, but have not reached on the right answer.
My System Info:
Windows 7 6bit
Jdk 8u111
I have created a Maven Project and added dependencies  for tensorflow
	<dependency> 		<groupId>org.tensorflow</groupId> 		<artifactId>tensorflow</artifactId> 		<version>1.8.0</version> 	</dependency>    		<dependency> 		    <groupId>org.tensorflow</groupId> 		    <artifactId>libtensorflow_jni</artifactId> 		    <version>1.8.0</version>      </dependency>
and when i clean and build the application
i run the program
`  public static void main(String[] args) throws Exception {
try (Graph g = new Graph()) {

  final String value = "Hello from " + TensorFlow.version();

  // Construct the computation graph with a single operation, a constant

  // named "MyConst" with a value "value".

  try (Tensor t = Tensor.create(value.getBytes("UTF-8"))) {

    // The Java API doesn't yet include convenience functions for adding operations.

    g.opBuilder("Const", "MyConst").setAttr("dtype", t.dataType()).setAttr("value", t).build();

  }

  // Execute the "MyConst" operation in a Session.

  try (Session s = new Session(g);

       Tensor output = s.runner().fetch("MyConst").run().get(0)) {

    System.out.println(new String(output.bytesValue(), "UTF-8"));

  }

}

}the error i am having is this:Exception in thread "main" java.lang.UnsatisfiedLinkError: C:\Users\Luke\AppData\Local\Temp\tensorflow_native_libraries-1529547871141-0\tensorflow_jni.dll:  U`

Thank you for your post. We noticed you have not filled out the following field in the issue template. Could you update them if they are relevant in your case, or leave them as N/A? Thanks.
Have I written custom code
OS Platform and Distribution
TensorFlow installed from
TensorFlow version
Bazel version
CUDA/cuDNN version
GPU model and memory
Exact command to reproduce

the issue template.
Sir you can help with the statement above.
I really understand what you mean,
OS Platform and Distribution :  I am using Windows 7 Professional 64bit mode.
TensorFlow installed from: I have tried  the Tensorflow basic HelloTF  example by creating a maven project in eclipse oxygen and have added Tensorflow 1.8.0 version in the dependencies and i end up getting Main Class HelloTF not found error.
I also tried adding the DLL  file in my MV Options in a same Netbeans project and putting the jar file in my classpath and got the error which is the subject of this issue.
Bazel Version: I don't have it installed on my system
CUDA/cuDNN version:  I don't have it installed on my system
GPU model and memory: No idea about it
Exact command to reproduce: No command

I am sorry if i have not answered correctly though.

Nagging Assignee @rohan100jain: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @rohan100jain: It has been 16 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.


Minor fix antialias arg

Description:
Antialias was defined as None in the public API as we deal with Pillow and Tensor backend. Pillow applies unconditionally the anti-aliasing and there is no way to disable it. Thus for Pillow we keep antialias=None. For Tensors, we can do antialias=True or False, None->False.
The purpose of this PR is to make antialias argument's default value and type hint more explcit in proto's resize_image_tensor signature and in private resize methods. Mainly, for tensors antialias=None does not make much sense.

Closing as outdated


Automated Package Upgrade

:tada: This PR is included in version 7.7.104 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add ARM64 support to eBPF

This PR adds ARM64 to eBPF for the build strategies below:

docker build . -t mizutest:arm64v8-cross --build-arg BUILDARCH=amd64 --build-arg TARGETARCH=arm64v8
docker build . -t mizutest:arm64v8-native --build-arg BUILDARCH=arm64v8 --build-arg TARGETARCH=arm64v8

It builds and loads the BPF without any issues on both x86_64 and ARM64. I couldn't verify the capture's itself on an Amazon EC2 A1 instance because of the issue below:
bpf_get_current_pid_tgid() >> 32 returns an incorrect PID on ARM64 minikube Docker driver, the problem does not exist on x86_64 minikube VirtualBox driver. It's either specific to minikube ARM64 or minikube Docker driver. It seems like a bug of either minikube or libbpf.
So, it needs to be tested on a cluster with ARM64 nodes using a cloud provider.

I have observed entries sourced from OpenSSL on ARM64 with minikube none driver. But didn't see any Go TLS. Therefore Go implementation needs further improvement after this PR. Probably related to these lines.
Apparently, the incorrect PID issue of bpf_get_current_pid_tgid() >> 32 is specific to minikube docker driver on ARM64.


Newly created workspaces are not always placed in the right most workspace

What did you expect to happen?
I expect a new workspace to always be added to the right most space, so that already existing workspaces do not get shifted up.
In other words, if the current workspace list is [#1] then SPC tab n should yield a workspace list of ``, [#1, #2].
What actually happened?
Newly created workspaces can sometimes be added to the first entry, shifting already existing workspaces (the workspace accessed by SPC tab 1 can be shifted up and accessed by SPC tab 2).
In other words, if the current workspace list is [#1] then SPC tab n actually yields a workspace list of [#2, #1].
Additional details:
This is reproducible in the sandbox with doom + modules
Steps to reproduce:
Steps to reproduce with sandbox doom instance (doom + modules).
SPC tab n ;; Creates workspace #1 in place 2
SPC tab 1 ;; Switch to workspace main in place 1
SPC tab d ;; delete workspace main, workspace #1 is now in place 1
SPC tab n ;; Creates workspace #2 (should be in place 2, takes place 1)
SPC tab tab ;; [#2, #1]
SPC tab n ;; Creates workspace #3 in place 3
SPC tab tab ;; [#2, #1, #3]

Shows that the workspace list is [#2, #1, #3]. i.e. the second SPC tab n created workspace #2 on the left most side, instead of the right most side. But then, workspace #3 was created on the right most side as desired.
System information:

emacs   version    27.0.50
        features   XPM JPEG TIFF GIF PNG RSVG SOUND GPM DBUS GSETTINGS GLIB NOTIFY INOTIFY ACL LIBSELINUX GNUTLS LIBXML2 FREETYPE HARFBUZZ M17N_FLT LIBOTF XFT ZLIB TOOLKIT_SCROLL_BARS GTK3 X11 XDBE XIM MODULES THREADS PDUMPER LCMS2 GMP
        build      Dec 02, 2019
        buildopts  (--with-modules --with-rsvg)
        windowsys  x
        daemonp    daemon
doom    version    2.0.9
        build      HEAD -> develop, origin/develop, origin/HEAD 1575300ad 2020-02-04 13:58:43 -0500
        dir        ~/.dotfiles/emacs/.doom.d/
system  type       gnu/linux
        config     x86_64-pc-linux-gnu
        shell      zsh
        uname      Linux 4.15.0-76-generic #86-Ubuntu SMP Fri Jan 17 17:24:28 UTC 2020 x86_64
        path       (~/anaconda3/bin ~/anaconda3/condabin ~/.emacs.d/bin ~/gems/bin ~/bin /usr/bin/applets /usr/local/bin /usr/bin /bin /opt/bin ~/.local/bin ~/.local/bin ~/bin /usr/local/sbin /usr/local/bin /usr/sbin /usr/bin /sbin /bin /usr/games /usr/local/games /snap/bin /usr/local/libexec/emacs/27.0.50/x86_64-pc-linux-gnu)
config  envfile    nil
        elc-files  4
        modules    (:completion company (ivy +childframe) :ui doom doom-dashboard hl-todo hydra modeline nav-flash ophints (popup +all +defaults) pretty-code treemacs vc-gutter vi-tilde-fringe window-select workspaces :editor (evil +everywhere) file-templates fold format multiple-cursors rotate-text snippets :emacs dired electric ibuffer vc :term eshell term vterm :tools editorconfig (eval +overlay) :checkers syntax :tools (lookup +docsets) lsp magit pdf :lang data emacs-lisp julia (latex +latexmk) markdown (org +dragndrop +journal +pandoc +present) python sh :config (default +bindings +smartparens))
        packages   ((anaconda-mode :recipe (:host github :repo falloutphil/anaconda-mode)) (eshell-prompt-extras :recipe (:host github :repo AlexLewandowski/eshell-prompt-extras)) (org-gcal :recipe (:host github :repo kidd/org-gcal.el)) (yapfify) (pcomplete-extension) (pcmpl-git) (org-ref-arxiv :recipe (:host github :repo AlexLewandowski/org-ref :files (org-ref-arxiv.el org-ref-utils.el org-ref-pdf.el))) (doom-themes) (company-posframe) (org-indent :disable t) (org-babel :disable t) (exec-path-from-shell) (lsp-julia :recipe (:host github :repo non-Jedi/lsp-julia)) (material-theme))
        elpa       (n/a)
        unpin      (n/a)

Doom doesn't do anything to affect or ensure order of workspaces, and can't, at the moment. We use persp-mode which doesn't give us that capability. It'd either need to be implemented upstream, or we'd have to abstract workspace order (and perhaps their names) from their underlying representation.
I'm currently swamped with other urgent work, so I cannot work on this. A PR is welcome, or better, a PR for persp-mode.

No worries, thank you for Doom!

As of 3ab70d7 this issue should be fixed. A slightly more systemic solution was needed than #2488. Let me know if the issue resurfaces and I'll reopen this. Thanks for bringing it to my attention!


incorrect mapping behavior by column number.

zero column is skipped because 0 == 'string' is always the true

Your PR conflicts with the current master. So i can't merge it.


Add diesel migration check(s) to CI

We are currently not checking that the diesel migration can be re-done (i.e. reverted and run again) without prorblems.
We should make sure that diesel migration redo --all passes without migrations failing.

Note that for the coordinator we have to spin up the db container and run the command like this:
diesel migration redo --all --database-url=postgres://postgres:mysecretpassword@localhost:5432/orderbook --migration-dir ./coordinator/migrations

for the app we can use a tempfile:
DATABASE_URL="sqlite:///tmp/database.sql" diesel migration redo --all --migration-dir ./mobile/native/migrations

I guess we should then check whether schema.rs would change after running such check on the CI?

I guess we should then check whether schema.rs would change after running such check on the CI?

Yes, this should be an additional check.
Additionally we should add a check that runs without errors for run the migrations and then redo --all for both coordinator and app. That way we make sure everything works properly.


SwaggerDocument.ToJson() is calling unexisting JsonSchemaSerializationContext

"Could not load type 'NJsonSchema.Infrastructure.JsonSchemaSerializationContext' from assembly 'NJsonSchema, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=c2f9c3bdfae56102'."
JsonSchemaSerializationContext exists on version <IP_ADDRESS>
Only JsonSchemaSerialization exists <IP_ADDRESS>

For now you need to downgrade to v9.10.41 until the next version of nswag is released. Sorry for the breaking change.

Ok. Thanks for your work.


Bugfix: return hit count in incrementLoginAttempts function

return the value returned by the hit function of limiter like it is documented in phpdoc
in 5.1 is the first occurrence of this bug. wanted in #17288

It's just the PHP doc that is wrong. Please send to 5.4.


API-1835: heavy refactor to use library-go and make downstream command building easier

Need to start from somewhere
/test all


Can I use FBO on front buffer layer to achieve post-processing effects

I want to render content into my own fbo by glBindFramebuffer, but it seems to have no effect:
GLES30.glBindFramebuffer(GLES30.GL_FRAMEBUFFER,  frameBufferId);
drawContent();
...
GLES30.glBindFramebuffer(GLES30.GL_FRAMEBUFFER,  0);
drawEffects();

Fixed by reading the source code, we can use the frameBufferId instead.

cloased


improve profiles and registry support

change log

allow to register custom datapackage and resource classes

the core datapackage classes were modified to use this dynamic loading functionality internally

added composer update_registry script that downloads the latest spec files and updates the registry accordingly (you then have to review and commit the changes this script makes manually)
added Registry class which handles the core profiles and classes and the registering of custom classes

Related Issues

#7

known problems

see #14

Coverage increased (+1.0%) to 89.583% when pulling ec82007bb73d955699d153aa9d2353a8434f89c5 on OriHoch:7-should-support-all-required-datapackage-validation-profile-registry into ca4fdd68471fb3dd4f3762fe2ad625b077281a3f on frictionlessdata:master.

Coverage increased (+1.0%) to 89.583% when pulling ec82007bb73d955699d153aa9d2353a8434f89c5 on OriHoch:7-should-support-all-required-datapackage-validation-profile-registry into ca4fdd68471fb3dd4f3762fe2ad625b077281a3f on frictionlessdata:master.

Coverage increased (+0.8%) to 89.387% when pulling 780f36a28cda22bd84af5c0902351b966aaaaa80 on OriHoch:7-should-support-all-required-datapackage-validation-profile-registry into ca4fdd68471fb3dd4f3762fe2ad625b077281a3f on frictionlessdata:master.

Coverage increased (+1.8%) to 90.376% when pulling b874669bbaa5a4d136a56adca0aec93f0361d82c on OriHoch:7-should-support-all-required-datapackage-validation-profile-registry into ca4fdd68471fb3dd4f3762fe2ad625b077281a3f on frictionlessdata:master.

Coverage increased (+1.8%) to 90.376% when pulling b874669bbaa5a4d136a56adca0aec93f0361d82c on OriHoch:7-should-support-all-required-datapackage-validation-profile-registry into ca4fdd68471fb3dd4f3762fe2ad625b077281a3f on frictionlessdata:master.

Coverage increased (+1.8%) to 90.376% when pulling b874669bbaa5a4d136a56adca0aec93f0361d82c on OriHoch:7-should-support-all-required-datapackage-validation-profile-registry into ca4fdd68471fb3dd4f3762fe2ad625b077281a3f on frictionlessdata:master.

Coverage increased (+1.8%) to 90.376% when pulling b874669bbaa5a4d136a56adca0aec93f0361d82c on OriHoch:7-should-support-all-required-datapackage-validation-profile-registry into ca4fdd68471fb3dd4f3762fe2ad625b077281a3f on frictionlessdata:master.

Coverage increased (+1.8%) to 90.376% when pulling b874669bbaa5a4d136a56adca0aec93f0361d82c on OriHoch:7-should-support-all-required-datapackage-validation-profile-registry into ca4fdd68471fb3dd4f3762fe2ad625b077281a3f on frictionlessdata:master.

Coverage increased (+1.9%) to 90.476% when pulling 71b1ab0958741e822ae896389ede6ac8b4b2d70c on OriHoch:7-should-support-all-required-datapackage-validation-profile-registry into ca4fdd68471fb3dd4f3762fe2ad625b077281a3f on frictionlessdata:master.

Coverage increased (+1.9%) to 90.476% when pulling 6735762ba681124e9d1547a74d0a90f52d96db5d on OriHoch:7-should-support-all-required-datapackage-validation-profile-registry into ca4fdd68471fb3dd4f3762fe2ad625b077281a3f on frictionlessdata:master.


Add policy-related features tracking in Cilium agent as prometheus metrics

Follow up of https://github.com/cilium/cilium/pull/35852 for more features. I've split in multiple commits so it's easier for each sig to review their section.
Note for reviewers: Review on a per-commit basis to make sure the feature of your sig is being detected correctly.
Features Checklist

[ ] Enable L3 policy (@cilium/sig-policy)
[ ] Enable Host Network Policies (@cilium/sig-policy)
[ ] Enable DNS rules (@cilium/sig-policy)
[ ] Enable HTTP and HTTPHeaderMatches Network Policies (@cilium/sig-policy)
[ ] Enable other L7 Network Policies (@cilium/sig-policy)
[ ] Enable Deny Network Policies (@cilium/sig-policy)
[ ] Enable IngressCIDR Network Policies (@cilium/sig-policy)
[x] Enable Mutual Auth Network Policies (@cilium/sig-servicemesh)
[x] Enable TLS and SNI Network Policies (@cilium/sig-servicemesh)
[ ] Enable Default Deny Network Policies (@cilium/sig-policy)
[ ] Enable Local Redirect Policies (@cilium/sig-datapath)
[ ] Enable Service Internal Traffic Policy (@cilium/sig-datapath)
[x] Enable CiliumEnvoyConfig (@cilium/sig-servicemesh)
[ ] Enable CiliumNetworkPolicy (@cilium/sig-policy)
[ ] Enable Host Network Policies (@cilium/sig-policy)
[ ] Enable ToFQDNs (@cilium/sig-policy)

/test

/test

/test

/test


Miss 'Open Folder' in Activities for downloading one disk

Storage Explorer Version: 1.10.0
Platform/OS: Windows 10
Architecture: x64
Commit: f06deb7a6
Regression From: Not a regression
Steps to reproduce:

Expand 'Disks' -> Right click one resource group.
Select one disk -> Download this disk -> Check the message in Activities.

Expect Experience:
'Open Folder' shows in Activities after downloading this disk successfully.
Actual Experience:
No 'Open Folder' shows in Activities after downloading this disk.

I am adding the speed summary to the activity log for managed disk commands as well.


[oneDNN] Enable Conv2D+FBNV2/V3+activation fusion for bf16

This PR enables the fusion disabled by PR-53867
This PR adds attribute U to FusedConv2D so as to account for FusedBatchNormV2/V3 inputs that are of type U. With that, the graph generated after remapper is valid and all grappler optimizations stay after MetaOptimizer is executed.

@elfringham : do you know why ARM CI failed for this PR?

Hi @ezhulenev Can you please review this PR ? Thank you!

Hi @ezhulenev Can you please review this PR ? Thank you!

Hi @ezhulenev Can you please review this PR ? Thank you!

@ezhulenev - can you please re-approve this PR?
I had to merge master to this PR to address some unit-test failure fixed in master. So, it needs re-approval. Thanks!

Hi @ezhulenev Can you please review this PR ? Thank you!

I am working to resolve conflicts

@penpornk - it shows the Py+CPP Internal CI build failed. I looked at the public invocation log, the failures don't seem related to my changes. Are these known issues? Can you please point me if there's any failure that needs to be fixed?

Hi @gaurides Can you please rebase and resolve conflicts? Thank you!

Hi @penpornk Can you please review this PR ? Thank you!

Hi @penpornk Can you please review this PR ? Thank you!

Hi @penpornk Can you please review this PR ? Thank you!

Hi @penpornk Can you please review this PR ? Thank you!

Hi @penpornk Can you please review this PR ? Thank you!

Hi @penpornk Can you please review this PR ? Thank you!

Hi @penpornk Can you please review this PR ? Thank you!

Hi @penpornk Can you please review this PR ? Thank you!

Hi @gaurides Can you please rebase your branch and resolve conflicts? Thank you!

Hi @gaurides Can you please rebase your branch and resolve the conflicts? Thank you!

Hi @gaurides Can you please rebase your branch and resolve the conflicts? Thank you!

thanks @gbaned. I just rebase the branch and resolved the conflict.

Hi @ezhulenev Can you please review this PR ? Thank you!

Hi @ezhulenev Can you please review this PR ? Thank you!

Hi @ezhulenev Can you please review this PR ? Thank you!

Hi @ezhulenev Can you please review this PR ? Thank you!

Hi @ezhulenev Can you please review this PR ? Thank you!

Hi @gaurides Can you please confirm if this PR is still valid? Thank you!

Hi @gaurides Can you please confirm if this PR is still valid? Thank you!

As of now, it looks like it is not required. So I will close this PR.


Missing features from original Notepad

[ ] Printing options;
[ ]  Search a word with Bing;
[x]  Zoom in/out;
[ ] Find, replace, go to section.

Implementing zoom is very easy with a Scroll Viewer, if you need help with this let me know.

For searching with Bing would you like in the right click content menu? Here is a screenshot of how its done in Quick Pad.

Yeah, that’s awesome


[incubator/etcd] Fixed rejoining and discovery

:warning: Supersedes #2864 as it's stale :warning:
Based upon:

https://github.com/kubernetes/charts/pull/2864
https://github.com/rtluckie/kubernetes-charts/commit/5a2777c21593ceca13169de8e2dadf97fce4b8c8

Changes:

rejoining and discovery fixes
peer TLS support
anti-affinity rules
other best practices

@hiddeco Thanks for all the work on this! I am happy to help test this out in happy/sad paths. This is critical for us with Service Catalog deployments, and we would like to get away from the old chart + internal fixes we've already made like you have done here.

/assign

@unguiculus business priorities got me distracted from this but I am planning to continue working on it.

@unguiculus did you get a chance to work on this?


Separation of default values and unset fields in MonitorSelect object .

The RFC 7047 defines that if any of the MonitorSelect parameters is not set,
it equals to 'true'.
For example, for "Insert" - 'If "insert" is omitted or true, "update"
notifications are sent for rows newly inserted into the table.'
The current implementation uses bools for the MonitorSelect fields,
so unset fields get the default value -"false", which violates the RFC
definition.
Another small change here is a replacement of the Select field in MonitorRequest
from the MonitorSelect struct by a pointer to the struct.
The Select field has the "omitempty" tag, but the tag doesn't make sense for
structs and Json marshaling adds empty struct (Select[]) for unset Select field.
Signed-off-by: Alexey Roytman<EMAIL_ADDRESS>

@roytman take a look at how I handled a similar problem in #112
https://github.com/ovn-org/libovsdb/blob/880a08af7b448e716e5305725721eab5bf5d5309/ovsdb/schema.go#L374
In summary:

Use *bool in the struct and make sure that omitempty is in the struct tag
Provide a function like func (ms MonitorSelect) Initial() bool for each *bool field that implements the RFC-defined handling of defaults (i.e if nil then return true)
To make the user-facing API cleaner, we can have a NewMonitorSelect function that takes bool arguments (not *bool) to avoid having to expose a helper function to convert bools to bool pointers.

@dave-tucker , I reimplemented it according to your suggestion with a specific type (with some changes), can you take a look. (Is it not over-complicated ?)
Your comment above (with *bool) is very similar to my previous implementation, so what is your preference ?

Addressed in #119


Minor suggestions for "Get started with JBoss EAP 7 using a Helm Chart" quick start

Hi @jmesnil,
Minor suggestions for "Get started with JBoss EAP 7 using a Helm Chart" quick start:

Replace all occurrences of quickstart with quick start

Get started with JBoss EAP 7 using a Helm Chart

In the overview page, do we want to give link to Customer portal or Redhat.com:
Red Hat® JBoss® Enterprise Application Platform (EAP)

In this quick start, you will complete 6 tasks:
In this quick start, you will complete the following tasks:

Task - Create a JBoss EAP7 application with Helm

In the Helm Charts catalog, search for JBoss EAP 7.4.

Add step 5:

Click the Eap74 Helm chart card.
The side panel displays information about the JBoss EAP 7 Helm chart

In existing step 5 full stop missing:
Click Install Helm Chart**.**
The details about the Jakarta EE application that you are building and deploying are specified in the build.uri field:
Add full stops at the end:
When the build is complete, a checkmark and the following message is displayed: Build #1 was complete**.**
When the second build is complete, a checkmark and the following message are displayed: Build #2 was complete .

Task View the associated code 3 of 6

In the Topology view, the eap74 deployment displays a code icon in the bottom right-hand corner. This icon either represents a Git repository that contains the associated code, or if the appropriate operators are installed, it represents the IDEs installed in your system.
@jmesnil Does this read correct?^

Click the icon to view the code associated with the application.

If the icon represents CodeReady Workspaces or Eclipse Che, clicking the icon opens the associated code in your IDE.
If the icon represents a Git repository, clicking the icon opens the associated Git repository.

Task - View the build status - (Change Build to build)

The two builds ~for~ eap74-build-artifacts and eap74 may take a few minutes to complete.

Task - View the pod status - (Change Pod to pod)

In the Details tab, -> Make "Details" bold

Note: In the Topology view, the dark outer circle ~D eap74 deployment~ indicates the pod status. -> Remove "D eap74 deployment"

In the overview page, do we want to give link to Customer portal or Redhat.com:
Red Hat® JBoss® Enterprise Application Platform (EAP)

When we discussed, it agreed the intro would link to redhat.com and the conclusion would link to customer portal. Do you want to revisit that decision?

In the Topology view, the eap74 deployment displays a code icon in the bottom right-hand corner. This icon either represents a Git repository that contains the associated code, or if the appropriate operators are installed, it represents the IDEs installed in your system.

Yes, this is correct. The behaviour depends on the operators that are installed in the openshift cluster.
However that these 2 points, I've addressed all your other suggestions in #5.


wscript build fedora

wscript downloads wrong llvm archive on non-ubuntu systems:
if sys.platform == 'darwin':
  CLANG_TARBALL_NAME = 'clang+llvm-$version-x86_64-apple-darwin'
elif sys.platform.startswith('freebsd'):
  CLANG_TARBALL_NAME = 'clang+llvm-$version-amd64-unknown-freebsd10'
# It is either 'linux2' or 'linux3' before Python 3.3
elif sys.platform.startswith('linux'):
  # These executable depend on libtinfo.so.5
  CLANG_TARBALL_NAME = 'clang+llvm-$version-x86_64-linux-gnu-ubuntu-14.04'
elif sys.platform == 'win32':
  CLANG_TARBALL_NAME = 'LLVM-$version-win64'
  CLANG_TARBALL_EXT = '.exe'

Yes, there is also Fedora and SuSe prebuilt binary. http://releases.llvm.org/download.html#5.0.1 Clang for x86_64 Ubuntu 14.04 should also work on Arch Linux if ncurses5-compat-libs is installed. And I think it likely also works on other distributions

It best case it worth to detect current linux distribution and try to download appropriate archive or at least have a parameter to control that.

I agree. Do you happen to run SuSe, Fedora or Ubuntu 16.04 or newer and can verify whether the prebuilt binary works? I'll be happy to merge your PR :)
The download link also varies among 4.0.0 4.0.1 and 5.0.1 (e.g. 4.0.1 ones does not mention "gnu"). I really hope the links can be stable

I have fedora -so will try to add check for it

No Fedora in https://releases.llvm.org/download.html#6.0.0 .....

clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04.tar.xz works for me on Fedora 27 after installing ncurses-compat-libs :)

thank you @jhasse ! It works fine on Fedora 27 + bundled llvm6 works fine for me, hence closed.


[WIP] Carousel

Related issue
#117
Scope of work

Screenshots of visual changes

Checklist

[ ] I followed composition rules for my component
[ ] I tested the component in most common device sizes (can be tested in Storybook from viewport addon in top menu)

Hey, please check designs again, arrow looks a bit different on hover ;)

@filrak ok now I see it, thanks


Add more test coverage, implement integration testing

At present, the critical parts of the library have decent unit test coverage (not that it shows because Coveralls integration is still missing), but more should be added. Furthermore the library could use some integration testing.

Good afternoon! You mind if I contribute to this?

Good afternoon! You mind if I contribute to this?

Sure, go right on ahead!

Thanks! So I was a little confused on what needed to be covered so I just looked at the the top of the test file to see what methods were being imported that wasn't used yet, compared the function being tested to what it was checking for from the original file, and just ran a few assertions.
It was my first time make a real contribution to a project, so thank you for the opportunity and I apologize if I wasn't really any help!

That confusion is entirely my fault, I haven't had time to write proper documentation or detailed issues yet as for the last few months I've been razor-focused on an issue with the CI/CD build system, which I finally managed to fix today (for now).
I'm not fussy about what assertions people add, everything helps as long as it's not just duplicating existing cases.
I'll be sure to read through your pull request and approve it unless there's something really weird going on, and thank you for your time! Feel free to contribute in other ways if you see something that interests you.