Push to Debian

Hi!
I'm happy I found your project! The only thing holding me back from using it myself is that there aren't packages available for other Debian releases.
Is there any chance you might be interested in getting your changes integrated into the debian chromium package? These sorts of privacy enhancements are things that I think would be very useful for the broader debian audience. If you don't think that will work, an alternative would be to get ungoogled-chromium into debian as its own package. You are already making packages, it seems like maybe just a little bit more effort to try and get them into debian itself.
I think that if this were made available to Debian, it would reach a lot more people!

Thanks for your interest in my project!
Although I do build my own Debian packages, I actually don't know many details on what I would need to do as a maintainer, such as the proper procedures of submitting packages and source code, and providing support for the package. Plus, I'm pretty sure some of the things I do to the source code (namely the domain patcher and source cleaner, which are mostly automated and therefore somewhat unpredictable in what they can break) are things that would take more time to do if I were to follow Debian's rules.
Also, I'm currently in the process of creating a flexible and extensible cross-platform Python build system that will take care of downloading, patching, configuring, and building Chromium for a certain platform or distribution. The debian directory used for building will become pretty simple; it will just run the build command and bundle up the build artifacts into .deb packages. There are several reasons why I'm switching to this system, but one major reason is that it makes supporting other platforms such as Mac OSX and Windows easier. Perhaps Debian and other distributions would be fine with my unconventional method of building packages for their distributions, but I don't think I have the time right now to learn what I need to know to become a package maintainer.
I could just propose to include a subset of the patches that aren't too dependent on a specific build configuration, but I'm fairly certain that my patches don't meet the standards of "good" patches. Also, I haven't been able to consistently keep up-to-date with the latest stable of Chromium, so Debian may not be happy with that.
In essence, I don't have a lot of time, and I use ways of saving time that others may not like very much.

Just a remark: For less experienced users it is a bit unclear how to install this browser. I was struggling with the process (even if I studied the github description). I found some install instructions in a forum of the debian based distro called bunsenlabs helpful.
For Stretch, amd64:
mkdir ~/src && cd ~/src && wget https://github.com/Eloston/ungoogled-chromium-binaries/releases/download/58.0.3029.110-1/chromium_58.0.3029.110-1_amd64.deb && wget https://github.com/Eloston/ungoogled-chromium-binaries/releases/download/58.0.3029.110-1/chromium-widevine_58.0.3029.110-1_amd64.deb && wget https://github.com/Eloston/ungoogled-chromium-binaries/releases/download/58.0.3029.110-1/chromium-shell_58.0.3029.110-1_amd64.deb && wget https://github.com/Eloston/ungoogled-chromium-binaries/releases/download/58.0.3029.110-1/chromium-l10n_58.0.3029.110-1_all.deb && wget https://github.com/Eloston/ungoogled-chromium-binaries/releases/download/58.0.3029.110-1/chromium-driver_58.0.3029.110-1_amd64.deb && sudo gdebi chromium_58.0.3029.110-1_amd64.deb && sudo gdebi chromium-driver_58.0.3029.110-1_amd64.deb && sudo gdebi chromium-widevine_58.0.3029.110-1_amd64.deb && sudo gdebi chromium-l10n_58.0.3029.110-1_all.deb && sudo gdebi chromium-shell_58.0.3029.110-1_amd64.deb
This requires wget and gdebi and it downloads the packages in a folder called src and installs them. Those packages are older than the packages in the repos, so apt upgrade tries to replace them. To avoid upgrading the following command helps:
sudo apt-mark hold chromium chromium-driver chromium-l10n chromium-shell
As I mentioned this is for less experienced users but it might be helpful to point out such steps in the description. Great work btw, it's striking how less resources this browser uses when all the junk has been removed.

@macandchief You make a point about package versions, but hopefully 62 comes out soon enough so that doesn't continue to be an issue. In develop, the packages have already been renamed with a ungoogled- suffix due to the inconvenience of package holding.
I don't think it is necessary to have instructions for installing Debian package files here because many other software do not post instructions either. So, methods to install should be easy to find.

Ok, thank you for the details, that's great with ungoogled-. I'm looking forward to give version 62 a try.

v62 got released, fantastic! If there is v58 already installed, is simply running the following a proper way to update?
mkdir ~/src && cd ~/src && wget https://github.com/Eloston/ungoogled-chromium-binaries/releases/download/62.0.3202.94-1/ungoogled-chromium_62.0.3202.94-1_amd64.deb && wget https://github.com/Eloston/ungoogled-chromium-binaries/releases/download/62.0.3202.94-1/ungoogled-chromium-widevine_62.0.3202.94-1_amd64.deb && wget https://github.com/Eloston/ungoogled-chromium-binaries/releases/download/62.0.3202.94-1/ungoogled-chromium-shell_62.0.3202.94-1_amd64.deb && wget https://github.com/Eloston/ungoogled-chromium-binaries/releases/download/62.0.3202.94-1/ungoogled-chromium-l10n_62.0.3202.94-1_all.deb && wget https://github.com/Eloston/ungoogled-chromium-binaries/releases/download/62.0.3202.94-1/ungoogled-chromium-driver_62.0.3202.94-1_amd64.deb && wget https://github.com/Eloston/ungoogled-chromium-binaries/releases/download/62.0.3202.94-1/ungoogled-chromium-common_62.0.3202.94-1_amd64.deb && sudo gdebi ungoogled-chromium_62.0.3202.94-1_amd64.deb && sudo gdebi ungoogled-chromium-common_62.0.3202.94-1_amd64.deb && sudo gdebi ungoogled-chromium-driver_62.0.3202.94-1_amd64.deb && sudo gdebi ungoogled-chromium-widevine_62.0.3202.94-1_amd64.deb && sudo gdebi ungoogled-chromium-l10n_62.0.3202.94-1_all.deb && sudo gdebi ungoogled-chromium-shell_62.0.3202.94-1_amd64.deb

@macandchief I think that installation method is fine. We should move this discussion elsewhere if you still have questions.

@Eloston Yes, indeed, the part from my post might be more useful elsewhere as the topic clearly changed and does not suit to Push to Debian.
So this is how the update v58 -> v62 went:
First I run (although it might not be necessary as I removed these packages later):
apt-mark unhold chromium chromium-driver chromium-l10n chromium-shell
After that I tried the one-liner I posted, but:
This package is uninstallable Dependency is not satisfiable: ungoogled-chromium-common (= 62.0.3202.94-1)
I was thinking about installing ungoogled-chromium-common first and the package ungoogled-chromium after that, but: dpkg: error processing archive ungoogled-chromium-common_62.0.3202.94-1_amd64.deb (--install): trying to overwrite '/usr/lib/chromium/natives_blob.bin', which is also in package chromium 58.0.3029.110-1
At this point I simply removed the installed packages (first I used this command without the chromium-shell package, but it needs to be removed. otherwise it gives an error message while installing ungoogled-chromium-shell):
apt remove chromium chromium-shell
And after that:
sudo gdebi ungoogled-chromium-common_62.0.3202.94-1_amd64.deb && sudo gdebi ungoogled-chromium_62.0.3202.94-1_amd64.deb && sudo gdebi ungoogled-chromium-driver_62.0.3202.94-1_amd64.deb && sudo gdebi ungoogled-chromium-widevine_62.0.3202.94-1_amd64.deb && sudo gdebi ungoogled-chromium-l10n_62.0.3202.94-1_all.deb && sudo gdebi ungoogled-chromium-shell_62.0.3202.94-1_amd64.deb
There is an error message if chromium-shell wasn't removed, but I mentioned it already above:
dpkg: dependency problems prevent configuration of chromium-shell:  ungoogled-chromium-shell (62.0.3202.94-1) breaks chromium-shell and is installed.
If I'm not mistaken apt-mark hold is not necessary anymore.
Update done. The browser is working fine! Some extensions needs to be updated (re-installed too). Fantastic work, well done.
According to these steps I guess this is how an update v58 -> v62 should work as a one liner:
mkdir ~/src && cd ~/src && wget https://github.com/Eloston/ungoogled-chromium-binaries/releases/download/62.0.3202.94-1/ungoogled-chromium_62.0.3202.94-1_amd64.deb && wget https://github.com/Eloston/ungoogled-chromium-binaries/releases/download/62.0.3202.94-1/ungoogled-chromium-widevine_62.0.3202.94-1_amd64.deb && wget https://github.com/Eloston/ungoogled-chromium-binaries/releases/download/62.0.3202.94-1/ungoogled-chromium-shell_62.0.3202.94-1_amd64.deb && wget https://github.com/Eloston/ungoogled-chromium-binaries/releases/download/62.0.3202.94-1/ungoogled-chromium-l10n_62.0.3202.94-1_all.deb && wget https://github.com/Eloston/ungoogled-chromium-binaries/releases/download/62.0.3202.94-1/ungoogled-chromium-driver_62.0.3202.94-1_amd64.deb && wget https://github.com/Eloston/ungoogled-chromium-binaries/releases/download/62.0.3202.94-1/ungoogled-chromium-common_62.0.3202.94-1_amd64.deb && sudo apt-mark unhold chromium chromium-driver chromium-l10n chromium-shell && sudo apt remove chromium chromium-shell && sudo gdebi ungoogled-chromium-common_62.0.3202.94-1_amd64.deb && sudo gdebi ungoogled-chromium_62.0.3202.94-1_amd64.deb && sudo gdebi ungoogled-chromium-driver_62.0.3202.94-1_amd64.deb && sudo gdebi ungoogled-chromium-widevine_62.0.3202.94-1_amd64.deb && sudo gdebi ungoogled-chromium-l10n_62.0.3202.94-1_all.deb && sudo gdebi ungoogled-chromium-shell_62.0.3202.94-1_amd64.deb
There will be the packages left in the (root) /src directory but after the update these can be also removed.

Well it seems that the disable signin patch was included in Debian's 63.0.3239.40-1. That's kinda neat.

Please add instructions of how to add ungoogled-chromium package to Debian on main Read.me
thx

as an alternative to adding instructions, point to https://github.com/ungoogled-software/ungoogled-chromium-debian

Thanks.
Is there no server which can be added to sources.list for simple apt-get usage?

@pannous Nope, see #37

seems all of you are waste effors.. eevent works in join with debian...

i filled a new bug on debian to suggest use ungoogled.chromiun event chromiun itselft at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939406 or https://bugs.debian.org/939406.. so if both project work together can be a great benefit for both, so then winbuntu, mx-linux and mint the most popular distributions will use then thist browser as primary solution

I would like this also. It will allow me to get the latest version easier and quicker as long as it is updated as much as other browsers are in the repo.

This is an old issue, that didn't show much activity recently — closing.
If you have any more information to add, let us know.


Adding documentation about using agent only for metrics

:grey_exclamation: Build Aborted

There is a new build on-going so the previous on-going builds have been aborted.

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

Build Cause: Pull request #1691 opened

Reason: Aborted from #2

Start Time: 2021-03-08T17:16:39.185+0000

Duration: 36 min 23 sec

Commit: e00769eec88d7f75f3a82d0b8c07208dfa4b42ee

Test stats :test_tube:

Test
Results

Failed
0

Passed
1792

Skipped
14

Total
1806

Trends :test_tube:

Steps errors
Expand to view the steps failures

mvn install

Took 2 min 47 sec . View more details on here
Description: ./mvnw clean install -DskipTests=true -Dmaven.javadoc.skip=true

Log output
Expand to view the last 100 lines of log output

[2021-03-08T17:52:51.108Z] script returned exit code 143
[2021-03-08T17:52:51.942Z] 2021-03-08 17:52:51,614 [docker-java-stream-1967679493] DEBUG com.github.dockerjava.api.command.PullImageResultCallback - ResponseItem(stream=null, status=Extracting, progressDetail=ResponseItem.ProgressDetail(current=231735296, total=314579837, start=null), progress=[====================================>              ]  231.7MB/314.6MB, id=8f1960d89fa8, from=null, time=null, errorDetail=null, error=null, aux=null)
[2021-03-08T17:52:51.942Z] 2021-03-08 17:52:51,739 [docker-java-stream-1967679493] DEBUG com.github.dockerjava.api.command.PullImageResultCallback - ResponseItem(stream=null, status=Extracting, progressDetail=ResponseItem.ProgressDetail(current=233963520, total=314579837, start=null), progress=[=====================================>             ]    234MB/314.6MB, id=8f1960d89fa8, from=null, time=null, errorDetail=null, error=null, aux=null)
[2021-03-08T17:52:51.942Z] 2021-03-08 17:52:51,851 [docker-java-stream-1967679493] DEBUG com.github.dockerjava.api.command.PullImageResultCallback - ResponseItem(stream=null, status=Extracting, progressDetail=ResponseItem.ProgressDetail(current=236748800, total=314579837, start=null), progress=[=====================================>             ]  236.7MB/314.6MB, id=8f1960d89fa8, from=null, time=null, errorDetail=null, error=null, aux=null)
[2021-03-08T17:52:52.207Z] 2021-03-08 17:52:51,972 [docker-java-stream-1967679493] DEBUG com.github.dockerjava.api.command.PullImageResultCallback - ResponseItem(stream=null, status=Extracting, progressDetail=ResponseItem.ProgressDetail(current=238977024, total=314579837, start=null), progress=[=====================================>             ]    239MB/314.6MB, id=8f1960d89fa8, from=null, time=null, errorDetail=null, error=null, aux=null)
[2021-03-08T17:52:52.207Z] 2021-03-08 17:52:52,080 [docker-java-stream-1967679493] DEBUG com.github.dockerjava.api.command.PullImageResultCallback - ResponseItem(stream=null, status=Extracting, progressDetail=ResponseItem.ProgressDetail(current=240648192, total=314579837, start=null), progress=[======================================>            ]  240.6MB/314.6MB, id=8f1960d89fa8, from=null, time=null, errorDetail=null, error=null, aux=null)
[2021-03-08T17:52:52.468Z] 2021-03-08 17:52:52,189 [docker-java-stream-1967679493] DEBUG com.github.dockerjava.api.command.PullImageResultCallback - ResponseItem(stream=null, status=Extracting, progressDetail=ResponseItem.ProgressDetail(current=242319360, total=314579837, start=null), progress=[======================================>            ]  242.3MB/314.6MB, id=8f1960d89fa8, from=null, time=null, errorDetail=null, error=null, aux=null)
[2021-03-08T17:52:52.468Z] 2021-03-08 17:52:52,308 [docker-java-stream-1967679493] DEBUG com.github.dockerjava.api.command.PullImageResultCallback - ResponseItem(stream=null, status=Extracting, progressDetail=ResponseItem.ProgressDetail(current=244547584, total=314579837, start=null), progress=[======================================>            ]  244.5MB/314.6MB, id=8f1960d89fa8, from=null, time=null, errorDetail=null, error=null, aux=null)
[2021-03-08T17:52:52.468Z] 2021-03-08 17:52:52,413 [docker-java-stream-1967679493] DEBUG com.github.dockerjava.api.command.PullImageResultCallback - ResponseItem(stream=null, status=Extracting, progressDetail=ResponseItem.ProgressDetail(current=247889920, total=314579837, start=null), progress=[=======================================>           ]  247.9MB/314.6MB, id=8f1960d89fa8, from=null, time=null, errorDetail=null, error=null, aux=null)
[2021-03-08T17:52:52.728Z] 2021-03-08 17:52:52,519 [docker-java-stream-1967679493] DEBUG com.github.dockerjava.api.command.PullImageResultCallback - ResponseItem(stream=null, status=Extracting, progressDetail=ResponseItem.ProgressDetail(current=251789312, total=314579837, start=null), progress=[========================================>          ]  251.8MB/314.6MB, id=8f1960d89fa8, from=null, time=null, errorDetail=null, error=null, aux=null)
[2021-03-08T17:52:52.728Z] 2021-03-08 17:52:52,634 [docker-java-stream-1967679493] DEBUG com.github.dockerjava.api.command.PullImageResultCallback - ResponseItem(stream=null, status=Extracting, progressDetail=ResponseItem.ProgressDetail(current=259031040, total=314579837, start=null), progress=[=========================================>         ]    259MB/314.6MB, id=8f1960d89fa8, from=null, time=null, errorDetail=null, error=null, aux=null)
[2021-03-08T17:52:52.991Z] 2021-03-08 17:52:52,743 [docker-java-stream-1967679493] DEBUG com.github.dockerjava.api.command.PullImageResultCallback - ResponseItem(stream=null, status=Extracting, progressDetail=ResponseItem.ProgressDetail(current=261816320, total=314579837, start=null), progress=[=========================================>         ]  261.8MB/314.6MB, id=8f1960d89fa8, from=null, time=null, errorDetail=null, error=null, aux=null)
[2021-03-08T17:52:52.991Z] 2021-03-08 17:52:52,846 [docker-java-stream-1967679493] DEBUG com.github.dockerjava.api.command.PullImageResultCallback - ResponseItem(stream=null, status=Extracting, progressDetail=ResponseItem.ProgressDetail(current=264601600, total=314579837, start=null), progress=[==========================================>        ]  264.6MB/314.6MB, id=8f1960d89fa8, from=null, time=null, errorDetail=null, error=null, aux=null)
[2021-03-08T17:52:52.991Z] 2021-03-08 17:52:52,946 [Thread-4] DEBUG org.testcontainers.shaded.com.github.dockerjava.core.command.AbstrDockerCmd - Cmd: testcontainers/29yqz2zwpcqojmw2,true,<null>
[2021-03-08T17:52:53.254Z] 2021-03-08 17:52:52,958 [docker-java-stream-1967679493] DEBUG com.github.dockerjava.api.command.PullImageResultCallback - ResponseItem(stream=null, status=Extracting, progressDetail=ResponseItem.ProgressDetail(current=266829824, total=314579837, start=null), progress=[==========================================>        ]  266.8MB/314.6MB, id=8f1960d89fa8, from=null, time=null, errorDetail=null, error=null, aux=null)
[2021-03-08T17:52:53.254Z] 2021-03-08 17:52:53,005 [Thread-4] DEBUG org.testcontainers.shaded.com.github.dockerjava.core.command.AbstrDockerCmd - Cmd: testcontainers/915uhpsfqsrfwu9d,true,<null>
[2021-03-08T17:52:53.254Z] 2021-03-08 17:52:53,086 [docker-java-stream-1967679493] DEBUG com.github.dockerjava.api.command.PullImageResultCallback - ResponseItem(stream=null, status=Extracting, progressDetail=ResponseItem.ProgressDetail(current=267943936, total=314579837, start=null), progress=[==========================================>        ]  267.9MB/314.6MB, id=8f1960d89fa8, from=null, time=null, errorDetail=null, error=null, aux=null)
[2021-03-08T17:52:53.868Z] script returned exit code 143
[2021-03-08T17:52:55.174Z] Post stage
[2021-03-08T17:52:55.224Z] Post stage
[2021-03-08T17:52:55.285Z] Recording test results
[2021-03-08T17:52:55.320Z] Recording test results
[2021-03-08T17:52:56.844Z] [Checks API] No suitable checks publisher found.
[2021-03-08T17:52:56.918Z] [Checks API] No suitable checks publisher found.
[2021-03-08T17:52:56.994Z] Running in /var/lib/jenkins/workspace/_java_apm-agent-java-mbp_PR-1691/src/github.com/elastic/apm-agent-java
[2021-03-08T17:52:57.017Z] Running in /var/lib/jenkins/workspace/_java_apm-agent-java-mbp_PR-1691/src/github.com/elastic/apm-agent-java
[2021-03-08T17:52:57.055Z] [INFO] Codecov: Getting branch ref...
[2021-03-08T17:52:57.073Z] [INFO] Codecov: Getting branch ref...
[2021-03-08T17:52:57.217Z] Masking supported pattern matches of $GITHUB_TOKEN
[2021-03-08T17:52:57.333Z] Masking supported pattern matches of $GITHUB_TOKEN
[2021-03-08T17:52:57.544Z] [INFO] Codecov: Sending data...
[2021-03-08T17:52:57.930Z] [INFO] Codecov: Sending data...
[2021-03-08T17:52:58.162Z] + curl -sSLo codecov.sh https://codecov.io/bash
[2021-03-08T17:52:58.482Z] + curl -sSLo codecov.sh https://codecov.io/bash
[2021-03-08T17:52:58.647Z] + bash codecov.sh
[2021-03-08T17:52:58.648Z]
[2021-03-08T17:52:58.648Z]   _____          _
[2021-03-08T17:52:58.648Z]  / ____|        | |
[2021-03-08T17:52:58.648Z] | |     ___   __| | ___  ___ _____   __
[2021-03-08T17:52:58.648Z] | |    / _ \ / _` |/ _ \/ __/ _ \ \ / /
[2021-03-08T17:52:58.648Z] | |___| (_) | (_| |  __/ (_| (_) \ V /
[2021-03-08T17:52:58.648Z]  \_____\___/ \__,_|\___|\___\___/ \_/
[2021-03-08T17:52:58.648Z]                               Bash-20210226-7100762
[2021-03-08T17:52:58.648Z]
[2021-03-08T17:52:58.648Z]
[2021-03-08T17:52:58.648Z] ==> git version 2.17.1 found
[2021-03-08T17:52:58.648Z] ==> curl 7.58.0 (x86_64-pc-linux-gnu) libcurl/7.58.0 OpenSSL/1.1.1 zlib/1.2.11 libidn2/2.0.4 libpsl/0.19.1 (+libidn2/2.0.4) nghttp2/1.30.0 librtmp/2.3
[2021-03-08T17:52:58.648Z] Release-Date: 2018-01-24
[2021-03-08T17:52:58.648Z] Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3 pop3s rtmp rtsp smb smbs smtp smtps telnet tftp
[2021-03-08T17:52:58.648Z] Features: AsynchDNS IDN IPv6 Largefile GSS-API Kerberos SPNEGO NTLM NTLM_WB SSL libz TLS-SRP HTTP2 UnixSockets HTTPS-proxy PSL
[2021-03-08T17:52:58.648Z] ==> Jenkins CI detected.
[2021-03-08T17:52:58.648Z]     project root: .
[2021-03-08T17:52:58.648Z] --> token set from env
[2021-03-08T17:52:58.648Z]     Yaml not found, that's ok! Learn more at http://docs.codecov.io/docs/codecov-yaml
[2021-03-08T17:52:58.648Z] ==> Running gcov in . (disable via -X gcov)
[2021-03-08T17:52:58.909Z] ==> Python coveragepy not found
[2021-03-08T17:52:58.910Z] ==> Searching for coverage reports in:
[2021-03-08T17:52:58.910Z]     + .
[2021-03-08T17:52:59.138Z] + bash codecov.sh
[2021-03-08T17:52:59.138Z]
[2021-03-08T17:52:59.138Z]   _____          _
[2021-03-08T17:52:59.138Z]  / ____|        | |
[2021-03-08T17:52:59.138Z] | |     ___   __| | ___  ___ _____   __
[2021-03-08T17:52:59.138Z] | |    / _ \ / _` |/ _ \/ __/ _ \ \ / /
[2021-03-08T17:52:59.138Z] | |___| (_) | (_| |  __/ (_| (_) \ V /
[2021-03-08T17:52:59.138Z]  \_____\___/ \__,_|\___|\___\___/ \_/
[2021-03-08T17:52:59.138Z]                               Bash-20210226-7100762
[2021-03-08T17:52:59.138Z]
[2021-03-08T17:52:59.138Z]
[2021-03-08T17:52:59.138Z] ==> git version 2.17.1 found
[2021-03-08T17:52:59.138Z] ==> curl 7.58.0 (x86_64-pc-linux-gnu) libcurl/7.58.0 OpenSSL/1.1.1 zlib/1.2.11 libidn2/2.0.4 libpsl/0.19.1 (+libidn2/2.0.4) nghttp2/1.30.0 librtmp/2.3
[2021-03-08T17:52:59.138Z] Release-Date: 2018-01-24
[2021-03-08T17:52:59.138Z] Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3 pop3s rtmp rtsp smb smbs smtp smtps telnet tftp
[2021-03-08T17:52:59.138Z] Features: AsynchDNS IDN IPv6 Largefile GSS-API Kerberos SPNEGO NTLM NTLM_WB SSL libz TLS-SRP HTTP2 UnixSockets HTTPS-proxy PSL
[2021-03-08T17:52:59.138Z] ==> Jenkins CI detected.
[2021-03-08T17:52:59.138Z]     project root: .
[2021-03-08T17:52:59.138Z] --> token set from env
[2021-03-08T17:52:59.138Z]     Yaml not found, that's ok! Learn more at http://docs.codecov.io/docs/codecov-yaml
[2021-03-08T17:52:59.138Z] ==> Running gcov in . (disable via -X gcov)
[2021-03-08T17:52:59.170Z] --> No coverage report found.
[2021-03-08T17:52:59.170Z]     Please visit http://docs.codecov.io/docs/supported-languages
[2021-03-08T17:52:59.399Z] ==> Python coveragepy not found
[2021-03-08T17:52:59.399Z] ==> Searching for coverage reports in:
[2021-03-08T17:52:59.399Z]     + .
[2021-03-08T17:52:59.583Z] Failed in branch Smoke Tests 01
[2021-03-08T17:52:59.619Z] Sending interrupt signal to process
[2021-03-08T17:52:59.660Z] --> No coverage report found.
[2021-03-08T17:52:59.660Z]     Please visit http://docs.codecov.io/docs/supported-languages
[2021-03-08T17:53:00.085Z] Failed in branch Smoke Tests 02
[2021-03-08T17:53:00.414Z] Stage "Integration Tests" skipped due to earlier failure(s)
[2021-03-08T17:53:00.524Z] Stage "AfterRelease" skipped due to earlier failure(s)
[2021-03-08T17:53:00.576Z] Stage "AfterRelease" skipped due to earlier failure(s)
[2021-03-08T17:53:01.018Z] Running on Jenkins in /var/lib/jenkins/workspace/_java_apm-agent-java-mbp_PR-1691
[2021-03-08T17:53:01.131Z] [INFO] getVaultSecret: Getting secrets
[2021-03-08T17:53:01.400Z] Masking supported pattern matches of $VAULT_ADDR or $VAULT_ROLE_ID or $VAULT_SECRET_ID
[2021-03-08T17:53:02.086Z] Click here to forcibly terminate running steps
[2021-03-08T17:53:02.468Z] + chmod 755 generate-build-data.sh
[2021-03-08T17:53:02.468Z] + ./generate-build-data.sh https://apm-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/apm-agent-java/apm-agent-java-mbp/PR-1691/ https://apm-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/apm-agent-java/apm-agent-java-mbp/PR-1691/runs/1 ABORTED 2183007
[2021-03-08T17:53:02.719Z] INFO: curl https://apm-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/apm-agent-java/apm-agent-java-mbp/PR-1691/runs/1/steps/?limit=10000 -o steps-info.json
[2021-03-08T17:53:03.270Z] INFO: curl https://apm-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/apm-agent-java/apm-agent-java-mbp/PR-1691/runs/1/tests/?status=FAILED -o tests-errors.json


Fix CentOS 7 example in README

For CentOS 7 I encountered the following issues:

Upstart needs to be disabled
nginx user is not www-data

As there is only upstart and systemd to choose from maybe it makes more sense to put this in a single boolean.
This pull request just fixes the example from the README to be a working example. (tested with vagrant and the included test.yml file)

thanks!


fix tty mode

For tty mode, this fixes the following issues after the refactoring

adds optional sound
enable raw-mode to support keys

You turned on the audio in the tty, but the reason why I turned off the audio is that I want to be able to compile and run the emulator normally without an audio device (for example, via ssh), what do you think?

Hi, SSH will still work with this since audio is disabled by default.
My feeling is that the functionality will still be usefull in other cases.

On computers without audio equipment (such as Linux server), cpal cannot be compiled. I hope to support this by adding tty mode.

:ok_hand:, Here is a proposal (see previous commit):
add an "audio" flag, enabled by default.
If one wants tty without audio, compile with:
--no-default-features --features tty
I one wants tty with audio, compile with:
--no-default-features --features tty,audio

Great!


On Pressing shift tab or tab key focus moves to adress bar in browser

Hi,
I am using<EMAIL_ADDRESS>modal component in one of our projects.
Our requirement is to trap the focus inside the modal however the focus is moving outside of the modal on tabbing. It then stays outside the modal until it traverses all the tabs on the page.
Is there a way you could keep the focus trapped inside the modal until the modal is closed? Or in other words it should continue looping with focus being within the modal.
Expected behavior – Focus should be trapped inside the modal window and on closing it focus should move to the element which triggers the modal window.
This is critical interaction for AX users. Appreciate any support you can provide with regards to this.

I think this request is out of scope, as it alters the default behavior of the browser. This is probably something you'd have to implement yourself by adding traps to the keyboard event and setting tabindex inside the modal.

Hi wartab,
Thanks for the reply. Initially I thought it was out of scope but when I look in to w3.org website modal focus is trapped inside the modal and even in bootstrap & angular material implementation they  are trapping  focus inside the modal itself  and here are few examples Which I have collected.
https://www.w3.org/TR/2017/NOTE-wai-aria-practices-1.1-20171214/examples/dialog-modal/dialog.html
https://material.angular.io/components/dialog/overview
https://getbootstrap.com/docs/3.3/javascript/


fix(docs): Fix grammar overall

Fix grammar in the documentation files.

Squashed the commits together.

Thanks, please change the commit message to docs: .. as fix is reserved for actual code fixes.

@dignifiedquire: Sorry for the inconvenience. If not mistaken, all the comments you had provided are solved and the commit message has been changed. Hope this is how it should be.

Thanks :octocat:


Property 'pageParam' does not exist on type '{ queryKey: QueryKey; signal: AbortSignal; meta: Record<string, unknown> | undefined;

Hi
I'm trying to use createQueryKeys with useInfiniteQuery
when use ctx.pageParam type error occurred
Error Message
Property 'pageParam' does not exist on type '{ queryKey: QueryKey; signal: AbortSignal; meta: Record<string, unknown> | undefined; }'.ts(2339)

my Code is here
  mails: (params) => ({
    queryKey: [params],
    queryFn: (ctx) =>
      getRequest({ ...params, page: ctx.pageParam }),
  }),

is there any way to  use createQueryKeys with useInfiniteQuery

Any updates?

Also experiencing this error. I believe the type definitions of QueryKeyFactory need to be updated to have signal be optional

I'm facing the same bug

This is causing issues with other config properties (mutationKey and queryKey) when using any typed or common meta. Has anyone made any progress on investigating?

I fixed the problem migrating to the latest version of RQ. the v5

@apenab could you show your RQ and query-key-factory versions please?


Use of extra single quotes results in errors copying the files from tmp dir

$ sudo -u root -i bash -c "'cp -R /tmp/project-1457472418137 ~/'"

bash: cp -R /tmp/project-1457472418137 ~/: No such file or directory
● failed (127)
● Command exited abnormally on xxxxxxxxxxx

The error arises because "'cp -R /tmp/project-1457472418137 ~/'"
has too many quotes.
Removing the single quotes will solve the problem.
The problem is not there using version 0.6.11

@pstadler @chrene This is the same as #123. Flightplan has been broken for me since this "improvement" got into the picture.

https://github.com/pstadler/flightplan/releases/tag/0.6.13


ATOM Error immediately after installing particle-dev ver 0.1.3

Error compiling Less stylesheet:
.../.atom/packages/particle-dev/styles/particle-dev.less
Line number: 8
'utilities.less' wasn't found
Failed to load the particle-dev package
'utilities.less' wasn't found in /home/justin/.atom/packages/particle-dev/styles/particle-dev.less:8:0
Hide Stack Trace
LessError: 'utilities.less' wasn't found
at /home//.atom/packages/particle-dev/styles/particle-dev.less:8:0
The error was thrown from the particle-dev package. You can help by creating an issue. Please explain what actions triggered this error.
This occurred immediately after installing particle-dev ver 0.1.3

same here...
`Atom Version: 1.10.0
Electron Version: 0.37.8
System: Mac OS X 10.12
Thrown From: particle-dev package, v0.1.3
Stack Trace
Failed to load the particle-dev package
At 'utilities.less' wasn't found in /Users/rgilmore/.atom/packages/particle-dev/styles/particle-dev.less:8:0

LessError: 'utilities.less' wasn't found
  at /Users/rgilmore/.atom/packages/particle-dev/styles/particle-dev.less:8:0`

Oh it looks like One theme doesn't have utilities.less file. You can avoid this error by switching to Atom  Dark/Light theme for now.

is this an issue with particle-dev or the atom one themes? should it be reported to them instead?

It's particle-dev issue. We need to remove the dependency on the utilities.less file.

I was having this problem and changed the theme in Atom from "One Dark"(default) to "Atom Dark"(mentioned in particle-dev.less file) and it installed without a problem.


cdk deploy issue

Hi,
I am getting the below error on cdk deploy.
would you please replicate it?
--app is required either in command-line, in cdk.json or in ~/.cdk.json

Hi 👋🏻
Thanks for raising this issue. I've reviewed the README and it looks like I missed a step - there should have been a cdk bootstrap step.
Can you try going into the infrastructure folder and then calling cdk bootstrap followed by cdk deploy ?
Please update this ticket to let me know if it works (or doesn't!)

Asked me when I run cdk bootstrap :
'**' is not an environment name. Run in app directory to glob or specify an environment name like 'aws://123456789012/us-east-1'.
I have entered my own instance id:
 cdk bootstrap aws://*********/eu-west-2^C
Then I got this :
 ⏳  Bootstrapping environment aws://507898586009/eu-west-2...  ✅  Environment aws://507898586009/eu-west-2 bootstrapped (no changes).
and finally when I run cdk deploy
I get this
--app is required either in command-line, in cdk.json or in ~/.cdk.json

Many thanks for coming back with such detail. I've merged a couple of fixes - #7 and #6 . Could you pull the main branch and give it another try?

Thanks for fixing some issues, I've tried, still seems to have an issue.
Please have a look at the screenshot, I have gotten after executing cdk bootsratp.

Hey!
Thanks for the screenshot. In future, could you copy and paste the text in? It's easier for me to read that way.
I think it looks like you've not changed the runtime/.chalice/example_config.json supplied with the software. Can you take another look at the draft README and make sure you're following all the instructions?

Hey,
Thanks, sure I will share the text, I was reading this
https://github.com/nwspk/twitter-list-follower/blob/main/README.rst

That would be great if you explain to me, what is each line?
I am totally blind there.
{
  "version": "2.0",
  "app_name": "twitter-list-follower",
  "automatic_layer": true,
  "stages": {
    "dev": {
      "environment_variables": {
        "CONSUMER_KEY": "consumer-key", // ??? I think we should get it from Twitter??
        "CONSUMER_SECRET": "consumer-secret", // ???  I think we should get it from Twitter??
        "CALLBACK_URL": "callback-url", // ??? I think we should get it from Twitter??
        "APP_TABLE_NAME": "AppTable", // this going to use Dynamo ?
        "APP_DO_NOW_QUEUE_NAME": "", //
        "APP_DO_LATER_QUEUE_NAME": ""
      },
      "api_gateway_stage": "api",
      "lambda_functions": {
        "api_handler": {
        }
      }
    }
  }
}

Yes! your CONSUMER_KEY should be the key from your twitter app, and likewise your CONSUMER_SECRET should be your secret key, also from the twitter app.
the CALLBACK_URL is one that you write into your twitter app, and is where users should be redirected to. I'll update the docs around that, as it's more complicated than I realised.
Thank you so much for highlighting these issues!

I've updated the draft docs (#4 ) to add a bit more explanation of the config file. Let me know how you get on.

Please have a look :
sudo cdk bootstrap aws://*************/eu-west-2 --aws-region=eu-west-2
/usr/lib/python3/dist-packages/requests/__init__.py:91: RequestsDependencyWarning: urllib3 (1.26.4) or chardet (3.0.4) doesn't match a supported version!
  RequestsDependencyWarning)
Traceback (most recent call last):
  File "app.py", line 6, in <module>
    ChaliceApp(app, 'cdk-list-follower')
  File "/usr/local/lib/python3.7/dist-packages/jsii/_runtime.py", line 83, in __call__
    inst = super().__call__(*args, **kwargs)
  File "/opt/projects/twitter-list-follower/infrastructure/stacks/chaliceapp.py", line 30, in __init__
    'APP_PROCESS_QUEUE_NAME': self.process_queue.queue_name,
  File "/usr/local/lib/python3.7/dist-packages/jsii/_runtime.py", line 83, in __call__
    inst = super().__call__(*args, **kwargs)
  File "/usr/local/lib/python3.7/dist-packages/chalice/cdk/construct.py", line 69, in __init__
    self._package_app()
  File "/usr/local/lib/python3.7/dist-packages/chalice/cdk/construct.py", line 89, in _package_app
    chalice_config=self.stage_config,
  File "/usr/local/lib/python3.7/dist-packages/chalice/api/__init__.py", line 24, in package_app
    packager.package_app(config, output_dir, stage)
  File "/usr/local/lib/python3.7/dist-packages/chalice/package.py", line 1235, in package_app
    config, chalice_stage_name)
  File "/usr/local/lib/python3.7/dist-packages/chalice/package.py", line 115, in construct_resources
    config, chalice_stage_name)
  File "/usr/local/lib/python3.7/dist-packages/chalice/deploy/appgraph.py", line 31, in build
    for function in config.chalice_app.pure_lambda_functions:
  File "/usr/local/lib/python3.7/dist-packages/chalice/config.py", line 141, in chalice_app
    app = v()
  File "/usr/local/lib/python3.7/dist-packages/chalice/cli/factory.py", line 277, in load_chalice_app
    app = importlib.import_module('app')
  File "/usr/lib/python3.7/importlib/__init__.py", line 127, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 1006, in _gcd_import
  File "<frozen importlib._bootstrap>", line 983, in _find_and_load
  File "<frozen importlib._bootstrap>", line 967, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 677, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 728, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/opt/projects/twitter-list-follower/runtime/app.py", line 11, in <module>
    from chalicelib.utils import queues
  File "/opt/projects/twitter-list-follower/runtime/chalicelib/utils.py", line 5, in <module>
    sqs = boto3.resource('sqs')
  File "/usr/local/lib/python3.7/dist-packages/boto3/__init__.py", line 102, in resource
    return _get_default_session().resource(*args, **kwargs)
  File "/usr/local/lib/python3.7/dist-packages/boto3/session.py", line 389, in resource
    aws_session_token=aws_session_token, config=config)
  File "/usr/local/lib/python3.7/dist-packages/boto3/session.py", line 263, in client
    aws_session_token=aws_session_token, config=config)
  File "/usr/local/lib/python3.7/dist-packages/botocore/session.py", line 851, in create_client
    client_config=config, api_version=api_version)
  File "/usr/local/lib/python3.7/dist-packages/botocore/client.py", line 87, in create_client
    verify, credentials, scoped_config, client_config, endpoint_bridge)
  File "/usr/local/lib/python3.7/dist-packages/botocore/client.py", line 328, in _get_client_args
    verify, credentials, scoped_config, client_config, endpoint_bridge)
  File "/usr/local/lib/python3.7/dist-packages/botocore/args.py", line 73, in get_client_args
    endpoint_url, is_secure, scoped_config)
  File "/usr/local/lib/python3.7/dist-packages/botocore/args.py", line 154, in compute_client_args
    s3_config=s3_config,
  File "/usr/local/lib/python3.7/dist-packages/botocore/args.py", line 220, in _compute_endpoint_config
    return self._resolve_endpoint(**resolve_endpoint_kwargs)
  File "/usr/local/lib/python3.7/dist-packages/botocore/args.py", line 303, in _resolve_endpoint
    service_name, region_name, endpoint_url, is_secure)
  File "/usr/local/lib/python3.7/dist-packages/botocore/client.py", line 402, in resolve
    service_name, region_name)
  File "/usr/local/lib/python3.7/dist-packages/botocore/regions.py", line 134, in construct_endpoint
    partition, service_name, region_name)
  File "/usr/local/lib/python3.7/dist-packages/botocore/regions.py", line 148, in _endpoint_for_partition
    raise NoRegionError()
botocore.exceptions.NoRegionError: You must specify a region.
Subprocess exited with error 1

and FYI I've configured env by below :
export AWS_DEFAULT_REGION=eu-west-2
export AWS_REGION=eu-west-2
sudo cat  ~/.aws/config =====>  [default] region = eu-west-2

Good morning!
I'm not sure why you're using sudo - I don't think it's in any of the instructions. Can I check you've set up a virtual environment?
I'm also not sure you need to add all those arguments to cdk bootstrap - it should read them from your ~/.aws/config

Actually, I just used empty cdk bootstrap, not worked.
I was googling and tried those ways, also I've used sudo because of a permission error.
Yes, of course, I will share with you in private.

I think this is fixed. I've updated the documentation in #4 to reflect this conversation and will now close this


[WIP] Workflow refactor

In preparation for merging the dask/cudf workflow objects this is a first step
at simplifying some workflow implementation details:

Removes the OperatorRegistry class, and the 'ops_args' member on the workflow
Moves the master_task_list and task_sets from being member variables of the workflow class to being local variables of the load_config method
Removes the operator registration code and stat_ops/df_ops/feat_ops  members
Removes the 'to_cpu' parameter on the workflow class

rerun tests

It's not related to any change you made, but one thing I noticed while looking this over is that the config argument seems to be a missed opportunity. It might be nice to consolidate the load_stats and load_config functionality so that the user can pass in a single file (as config) to specify both the workflow configuration and known statistics. An obvious application would be "online-only" preprocessing.

Lets examine this in a future PR - I agree that we probably want to make online-only / inference support seamless, but have some concerns about serializing the ops that are part of the current config object.


getReplyToMessageId is Not available in the Message object ( when getting the emails) , can you please add it

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Thanks for opening the issue @rohitpandit we will look into this and provide you with an update as soon as we can.

 Are you looking for an ID to reply to with a new message or do you want the ID of the message this message is replying to? Thanks!

Closing this ticket due to inactivity, please reopen if this issue comes up again.


🌱 Add Lennart as reviewer

With this I would have 10 commits in the repo.

/test-ubuntu-integration-main

/approve
Thanks a lot @lentzi90
/test-ubuntu-integration-main

We need to cherry-pick this so that your labels are considered in release branches as well
/cherry-pick release-1.3
/cherry-pick release-1.2

/cherry-pick release-1.3
/cherry-pick release-1.2

/cherry-pick release-1.2


Feature Req: Pull values for Light Mode, Light Opening/Closing Level, Open/Close Delay, etc.

First up, many thanks for making this integration and sharing it with the community!
I'm sure you have a list of things you are working on, but I just wanted to add a few things to it (if not already on it).
Is it possible to pull the current values for:

Autodoor Mode (i.e. Manual, Time, or Light)
Current Time
Light Opening Level (if Autodoor in Light Mode) in lx (or is it % given the values range from 0 to 100?)
Light Closing Level (if Autodoor in Light Mode) in lx (or is it % given the values range from 0 to 100?)
Opening Time (if Autodoor in Time Mode)
Closing Time (if Autodoor in Time Mode)
Door Opening Delay (in minutes)
Door Closing Delay (in minutes)
Door State Information (History tracking)
Door Error Information (History tracking)

Hi Anthony,
Thanks for your input. The next release is a bit of an overhaul and introduces new features and entities, including some configuration controls.
We're only just getting started, but your list looks achievable and aligned with our own goals. In fact, some of it is already in the next release and the rest shouldn't be far behind - check out the dev branch if you'd like a sneak peek.
Kind Regards,
Dave

Thanks Dave!!


Translation when importing components after translations

Vite compiler is puking when I try to add translations before the button component.
<script>
  import { t } from "$lib/translations";
  import Button from "../components/base/Button.svelte";

</script>

<Button>{$t("common.menu.booking")}</Button>

This is my lang file setup
import i18n from "sveltekit-i18n";
import lang from "./lang.json";
export const config = {
  translations: {
    en: { lang },
    da: { lang },
    se: { lang },
  },
  loaders: [
    {
      locale: "en",
      key: "common",
      loader: async () => (await import("./en/common.json")).default,
    },
    {
      locale: "da",
      key: "common",
      loader: async () => (await import("./da/common.json")).default,
    },
    {
      locale: "se",
      key: "common",
      loader: async () => (await import("./se/common.json")).default,
    },
  ],
};

export const { t, locale, locales, loading, loadTranslations } = new i18n(
  config
);

loading.subscribe(
  ($loading) => $loading && console.log("Loading translations...")
);

Vite error:
Internal server error: Cannot find module 'C:\Projects\projectname\package.json' imported from 'C:\Projects\projectname\node_modules\vite\dist\node\chunks\dep-f5552faa.js'
I'm using sveltekit with svelte add and Tailwind

On a first look, It seems to me like some error in Vite compiler, but I’ll try to replicate (or if you have some repro? - would be useful) and let you know..)

I created this repo, so you can test it. The primary problem happens in the payment route.
https://github.com/Slepzs/Translations_error

Your repro looks fine, only one thing - you are missing lang init:
<script context="module">
  import { locale,  loadTranslations } from '$lib/translations';

  export const load = async ({ url }) => {
    const { pathname } = url;

    const lang = locale.get() || 'en';

    await loadTranslations(lang, pathname);

    return {};
  }
</script>

I wasn't able to replicate your error, though.. Have you tried to update your deps to latest versions?

Try now at this fork https://github.com/Alexnortung/Translations_error
to reproduce the error run npm run dev, then go to localhost:3000/booking and there will be errors.
However if you start npm run dev then go to localhsot:3000/ and then to localhost:3000/booking there won't be any errors.

@Alexnortung thanks for your repro, but still no errors in server nor client console on my side even if i directly go to /booking – what OS do you use? I'm trying on macOS – maybe this issue is OS related...🤔

Ok, this error is caused by imports in __layout.svelte from your repro:
  // This throws me the error:
  import { lang } from "$lib/stores/lang";
  import { t, locales, locale, loadTranslations } from "$lib/translations";

  // This seems to be ok:
  import { t, locales, locale, loadTranslations } from "$lib/translations";
  import { lang } from "$lib/stores/lang";

But it does not seem to be related directly to this library – it seems to be more like SvelteKit / Vite / preprocessor related bug...


Fixing flexbox aside

Preview environment created!
The preview environment has been deployed to the cluster.
Client URL: https://pr-1919--epp.elifesciences.org
Storybook URL: https://pr-1919--epp-storybook.elifesciences.org
Note: If this is a new environment, it can take a few minutes for DNS to update.

Preview environment images deployed!
The preview environment has been updated:
client image tag: preview-1919-48caa76586976f74b0ffb168782d40315175be6f-20240521.1210
storybook image tag: preview-1919-48caa76586976f74b0ffb168782d40315175be6f-20240521.1210
Client URL: https://pr-1919--epp.elifesciences.org
Storybook URL: https://pr-1919--epp-storybook.elifesciences.org
Note: Updated images can take a few minutes to roll out.


.nss variables accessible from code

Hi again :)
This time I was thinking about access to variables defined in .nss in code. Very useful in cases, where you need to obtain some global vars, so you won't be having two files with same palette, for example:
/* nss file*/
@color-primary: #123456;

/* constants file */
#define kColorPrimary  @"color-primary";

/* some UI file */
- (void)someSetupMethod
{
    CALayer *border = [CALayer layer];
    bottomBorder.frame = CGRectMake(whatever);
    bottomBorder.backgroundColor = [[NUISettings getColorFromVar:kColorPrimary] CGColor];
    [self.myTextField.layer addSublayer:border];
}

Why would you do that instead of merely doing:
/* nss file*/
MyTextField {
    border-color: #123456;
}

/* some UI file */
- (void)someSetupMethod
{
    self.myTextField.nuiClass = @"MyTextField";
}

By using CALayer I wanted to point out, that not everything is stylable by NUI. Some custom controls would still require manual approach.
Point is, that I still need to access my styles (color palette for example) and since they are moved to .nss file and I don't want to have two files defining same styles (MyTheme.nss and MyTheme.h) it would be nice to do it via NUI.

Can this sort of thing can be addressed by render customization? It has currently been partially implemented at a very granular level, but as per the discussion it needs to be re-architected.

Partially maybe.
I can think of some other scenarios, where you don't have rendering element, like if you need some padding values from .nss file to include them in layout calculations.
Also accessing variables might be much easier to implement and use.

Fair enough. I'd like to hear your thoughts on this @timbodeit.

@Emailrus, while I agree feature is useful, you could you workaround, add dummy style colors you need,
App {     background-color: @minor;     foreground-color: @main; }
then in code use
NUISettings.getColor("background-color", withClass: "App")

@Stunner I'm sorry, I have been inactive for a little while.
I would suggest the same thing as @alexeyt820. We have "Colors" classes for various components of our app. I don't think we need new API in NUI for this.
I do like the idea of a constants file however. It would be awesome to have a code-generating script, that automatically extracts constants for the different Classes and attributes to make accessing them from code safer and a little bit more convenient.


Add an issue template for new tools

In the past, multiple developers either submitted a PR or requested a tool in issues. I would like to have an issue template (in addition to feature and bug templates) that developers can use when requesting a new tool.
I think it should have the following fields but let's discuss more:

Tool Name
Tool Description
List of Proposed Activities
Examples w/ Griptape Agents

Related to #459

@andrewfrench do we still need this with the latest contributing guidelines?

Closing as per https://github.com/griptape-ai/griptape/pull/459


Runs on Multimeric Structures

First of all thank you for making this repo available.
I was wondering if you tested the algorithm on multimeric structures (having more than chain in the PDB file/Structure) or if you have any intuition regarding this possibility.
Best.
Liv

Take a look here:
https://colab.research.google.com/github/sokrypton/ColabDesign/blob/main/af/examples/AF2Rank.ipynb
We got an implementation that works on both monomer and multimer.

@sokrypton thank you for pointing me to the colab. I am currently bench-marking a few scoring methods for multimers. So far the average inference time for a trimeric hetero-oligomer is 50sec.


Release 1.2.0 🚀🚀🚀

:tada: This issue has been resolved in version 1.2.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Bump jQuery from 1.8.2 to 3.6.1

I basically hit same vuln reporting by Mend as reported in https://github.com/IBM/ibm-cos-sdk-go/issues/8.
Looking at this repo, I found https://github.com/IBM/ibm-cos-sdk-go/blob/89c32eab4d1c25c051d2c23d0afcf77b5602dfc1/doc-src/aws-godoc/templates/jquery.js being at old version 1.8.2 (wget https://code.jquery.com/jquery-1.8.2.min.js), while latest is 3.6.1 (wget https://code.jquery.com/jquery-3.6.1.min.js).
Not sure if one can just replace it 1:1, it seems there have been some breaking changes over the years, see https://jquery.com/upgrade-guide/.
Kindly consider this PR as a proposal to address the vulns, but let's take due diligence to test the related doc pages still work. And please also take a cross-check if same licensing is still applicable. Thank you.
In general this piece of the SDK is not a key component, i.e. it won't break the Go SDK itself. Nevertheless, we should address these vulns and not ship some old piece. Thanks.

With the release of https://github.com/IBM/ibm-cos-sdk-go/releases/tag/v1.9.3 on Dec 8, 2022, we should be good to close this PR.


Publish V4 Core Tools Images

Publish Core Tools images for all the supported languages
Update readme to include right tags for V4 core tools images

Also need to investigate why few core-tools images are using devcontainer as base image: https://github.com/Azure/azure-functions-docker/blob/dev/host/4/bullseye/amd64/python/python38/python38-core-tools.Dockerfile#L6 vs language sdk / runtime as base image: https://github.com/Azure/azure-functions-docker/blob/dev/host/4/bullseye/amd64/java/java8/java8-core-tools.Dockerfile#L6
We need to use a consistent approach

@vrdmr  - is there any reason to use devcontainer as base image : https://github.com/Azure/azure-functions-docker/blob/dev/host/4/bullseye/amd64/python/python38/python38-core-tools.Dockerfile#L6 instead of python:3.9-bullseye similar to Java and dotnet core-tools images?

I identify the issue by the python 3.8 v4 core tools image fails to build. I suppose bullseye deb package might not published.
Let me explain.  We search /etc/apt/sources.list.d directory and find the sources.  dotnet in-proc (success), java (success), python 3.8 (Unable to locate azure-functions-core-tools-4) Let's double check if apt publish the bullseye source.
Issue
$ apt install azure-functions-core-tools-4
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package azure-functions-core-tools-4

dotnet in-proc
root@efa347042129:/etc/apt/sources.list.d# cat microsoft-prod.list
deb [arch=amd64] https://packages.microsoft.com/debian/9/prod stretch main

java8
root@46fb8774b408:/etc/apt/sources.list.d# cat dotnetdev.list
deb [arch=amd64] https://packages.microsoft.com/repos/microsoft-debian-buster-prod buster main

##python3.8
root ➜ /etc/apt/sources.list.d $ cat dotnetdev.list
deb [arch=amd64] https://packages.microsoft.com/repos/microsoft-debian-bullseye-prod bullseye main

cc @anthonychu

@TsuyoshiUshio  - Java and dotnet core tools images should be using bullseye deb package as well?

It looks core-tools not supported yet.  https://github.com/Azure/azure-functions-core-tools/issues/2702
It is confusing since the Dockerfile is under bullseye. However, for dotnet and java and others might be decided not to go with bullseye. Let's check the context. @balag0  Do you know about it?

It might be easier to move python/powershell image from 3.8 to 3.8-buster
https://github.com/microsoft/vscode-dev-containers/blob/main/containers/python-3/.devcontainer/base.Dockerfile#L1
https://github.com/Azure/azure-functions-docker/blob/dev/host/4/bullseye/amd64/python/python38/python38-core-tools.Dockerfile#L6

Powershell using dotnet/sdk:6.0.100. We might use 6.0.100-focal (Ubuntu 20.04) instead, if it is ok. It is supported. https://github.com/Azure/azure-functions-core-tools#ubuntu-2004
https://mcr.microsoft.com/v2/dotnet/sdk/tags/list
https://github.com/Azure/azure-functions-docker/blob/dev/host/4/bullseye/amd64/powershell/powershell7-core-tools.Dockerfile#L1

@pragnagopa Did you see that the packages are now available for bullseye as well see

@RiaanVR - We are working on publishing images. Should be avaialble soon.

I'm working on it on the PR. All of them becomes bullseye. However, Java base image doesn't support bullseye, so that we are stop publishing the java. I created an issue. https://github.com/Azure/azure-functions-core-tools/issues/2878
Once Java base image available, I'll update the pipeline and publish it.


Manylinux ARM builds

Hey, it would be great if you could supply manylinux arm builds for pyrage. For example for M1 Docker builds or Raspberry Pi.

Thanks for the request. I can look into this in the upcoming days. Alternatively, if you feel like it, I'd be happy to review a PR that updates the current CI/build matrix to add ARM wheels.

I took a quick look at this, and it looks like this won't be super straightforward: GitHub's arm64 Linux runners are in GA, but they're only available to paying orgs/enterprises.
The alternative is to cross-compile or use something like QEMU. For the former, maturin-action looks to be the most promising approach.

Used qemu in other projects with the official action, that did the matrix stuff on qemu. Sadly do not have the time to contribute currently.


Prohibiting Certain Attributes on Property and Event Accessors

V8 removes a restriction on the Obsolete attribute by allowing it on property and event accessors. However, I don’t see that this was ever disallowed in early versions.
@Gafter challenges this assertion in Roslyn Issue 32472 (https://github.com/dotnet/roslyn/issues/32472#issuecomment-455355480), by stating

The language spec says

The attribute Obsolete is used to mark types and members of types that should no longer be used.
A property accessor is neither a type nor a member of a type. So the current implementation is as required by the specification. Arguably, the attribute could be permitted on accessors but ignored on uses of the accessor. Either way, changing this would require a change to the specification.

I disagree; in an attribute context, accessors are treated like methods (which are members). I deduce that from the fact that for an attribute to be allowed on an accessor, the attribute type must have System.AttributeUsage(…  System.AttributeTargets.Method …).
While researching this, I also found that the Conditional attribute is also disallowed on accessors, but, again, the spec does not say so. This type has [System.AttributeUsage(System.AttributeTargets.Class | System.AttributeTargets.Method, AllowMultiple=true)]. <IP_ADDRESS>, “Conditional methods”, https://github.com/dotnet/csharpstandard/blob/draft-v6/standard/attributes.md#22532-conditional-methods, has no statement analogous to the one Neal cited for Obsolete.
I propose that we modify the spec where property and event accessors are defined, adding prohibitions on the use of these two attributes. And then add Notes in the Attribute chapter where these attributes are spec’d, pointing back to those prohibitions.
Then for V8, we'll remove the prohibition on Obsolete.

Further to Rex’s deduction we find in the second bulleted list in §22.3:

method — a constructor, finalizer, method, operator, property get and set accessors, indexer get and set accessors, and event add and remove accessors. A field-like event (i.e., one without accessors) can also have an attribute with this target.

To me it looks like the wording around ObsoleteAttribtute; §22.5.1, “used to mark a member as obsolete”; is just unfortunate and wasn’t intended to exclude accessors at all. In Ecma-355 §21.2.2 the attribute “Indicates that an element is not to be used” – “element” not “member”.
Given the loose language I don’t think is a Standard or compiler bug per se, I do wonder what the compiler does when importing a CLS compliant property accessor with this attribute (its a CLS requirement).
I think we just punt on this one, not worth changing the Standard now, but leave a note to make things clear come v8.

Closing as per comment above.


can not run basic.py

TypeError: 'int' object is not iterable

Same issue as  https://github.com/skriegman/evosoro/issues/3


[image_picker] On iOS pickVideo(source: ImageSource.camera) returns video file in mono - even on stereo able device.

We have created a pretty simple app to record video and upload the file to our server using ImagePicker.pickVideo(source: ImageSource.camera). Everything works as expected except that on iOS the uploaded file is always mono - even on devices where the native Camera app records in stereo.

Hi @fideldonson
can you please provide your flutter doctor -v ,
your pubspec.yaml
and a reproducible minimal code sample.
Thank you

flutter doctor -v
[√] Flutter (Channel stable, v1.12.13+hotfix.9, on Microsoft Windows [Version 10.0.18362.778], locale en-DK)
• Flutter version 1.12.13+hotfix.9 at C:\src\flutter
• Framework revision f139b11009 (4 weeks ago), 2020-03-30 13:57:30 -0700
• Engine revision af51afceb8
• Dart version 2.7.2
[√] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
• Android SDK at C:\Users\denni\AppData\Local\Android\sdk
• Android NDK location not configured (optional; useful for native profiling support)
• Platform android-29, build-tools 29.0.3
• Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
• Java version OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b04)
• All Android licenses accepted.
[√] Android Studio (version 3.6)
• Android Studio at C:\Program Files\Android\Android Studio
• Flutter plugin version 45.1.1
• Dart plugin version 192.7761
• Java version OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b04)
[√] VS Code (version 1.44.2)
• VS Code at C:\Users\denni\AppData\Local\Programs\Microsoft VS Code
• Flutter extension version 3.9.1
[!] Connected device
! No devices available
! Doctor found issues in 1 category.

pubspec.yaml:
name: waffle_app
description: A new Flutter project.
The following defines the version and build number for your application.
A version number is three numbers separated by dots, like 1.2.43
followed by an optional build number separated by a +.
Both the version and the builder number may be overridden in flutter
build by specifying --build-name and --build-number, respectively.
In Android, build-name is used as versionName while build-number used as versionCode.
Read more about Android versioning at https://developer.android.com/studio/publish/versioning
In iOS, build-name is used as CFBundleShortVersionString while build-number used as CFBundleVersion.
Read more about iOS versioning at
https://developer.apple.com/library/archive/documentation/General/Reference/InfoPlistKeyReference/Articles/CoreFoundationKeys.html
version: 1.0.3+3
environment:
sdk: ">=2.1.0 <3.0.0"
dependencies:
flutter:
sdk: flutter
The following adds the Cupertino Icons font to your application.
Use with the CupertinoIcons class for iOS style icons.
cupertino_icons: ^0.1.2
image_picker: ^0.6.3
http: ^0.12.0+4
provider: ^4.0.4
flutter_webview_plugin: ^0.3.10+1
dev_dependencies:
flutter_test:
sdk: flutter
For information on the generic Dart part of this file, see the
following page: https://dart.dev/tools/pub/pubspec
The following section is specific to Flutter.
flutter:
The following line ensures that the Material Icons font is
included with your application, so that you can use the icons in
the material Icons class.
uses-material-design: true

pubspec.yaml:
name: app
description: A new Flutter project.
The following defines the version and build number for your application.
A version number is three numbers separated by dots, like 1.2.43
followed by an optional build number separated by a +.
Both the version and the builder number may be overridden in flutter
build by specifying --build-name and --build-number, respectively.
In Android, build-name is used as versionName while build-number used as versionCode.
Read more about Android versioning at https://developer.android.com/studio/publish/versioning
In iOS, build-name is used as CFBundleShortVersionString while build-number used as CFBundleVersion.
Read more about iOS versioning at
https://developer.apple.com/library/archive/documentation/General/Reference/InfoPlistKeyReference/Articles/CoreFoundationKeys.html
version: 1.0.3+3
environment:
sdk: ">=2.1.0 <3.0.0"
dependencies:
flutter:
sdk: flutter
The following adds the Cupertino Icons font to your application.
Use with the CupertinoIcons class for iOS style icons.
cupertino_icons: ^0.1.2
image_picker: ^0.6.3
http: ^0.12.0+4
provider: ^4.0.4
flutter_webview_plugin: ^0.3.10+1
dev_dependencies:
flutter_test:
sdk: flutter
For information on the generic Dart part of this file, see the
following page: https://dart.dev/tools/pub/pubspec
The following section is specific to Flutter.
flutter:
The following line ensures that the Material Icons font is
included with your application, so that you can use the icons in
the material Icons class.
uses-material-design: true

pubspec.yaml:
name: waffle_app
description: A new Flutter project.
The following defines the version and build number for your application.
A version number is three numbers separated by dots, like 1.2.43
followed by an optional build number separated by a +.
Both the version and the builder number may be overridden in flutter
build by specifying --build-name and --build-number, respectively.
In Android, build-name is used as versionName while build-number used as versionCode.
Read more about Android versioning at https://developer.android.com/studio/publish/versioning
In iOS, build-name is used as CFBundleShortVersionString while build-number used as CFBundleVersion.
Read more about iOS versioning at
https://developer.apple.com/library/archive/documentation/General/Reference/InfoPlistKeyReference/Articles/CoreFoundationKeys.html
version: 1.0.3+3
environment:
sdk: ">=2.1.0 <3.0.0"
dependencies:
flutter:
sdk: flutter
The following adds the Cupertino Icons font to your application.
Use with the CupertinoIcons class for iOS style icons.
cupertino_icons: ^0.1.2
image_picker: ^0.6.3
http: ^0.12.0+4
provider: ^4.0.4
flutter_webview_plugin: ^0.3.10+1
dev_dependencies:
flutter_test:
sdk: flutter
For information on the generic Dart part of this file, see the
following page: https://dart.dev/tools/pub/pubspec
The following section is specific to Flutter.
flutter:
The following line ensures that the Material Icons font is
included with your application, so that you can use the icons in
the material Icons class.
uses-material-design: true

I cant share a reproducible minimal code sample because the problem is only apparent once the video is uploaded to a server.
But here is the code in question:
`Future getVideo(String sceneID, bool doRecord) async{
print("start recording");
_sceneID = sceneID;
var video;
if(doRecord){
  video = await ImagePicker.pickVideo(source: ImageSource.camera);
}else{
  video = await ImagePicker.pickVideo(source: ImageSource.gallery);
}

if(video == null) {
  print("no file selected");
}else{
  print("file selected");
  _video = video;
  videoPath = _video.path;

  sendVideo();
}

}
Future sendVideo() async{
print("send video");
String jspEndPoint = 'upload-ajax.jsp?id='+_sceneID+"&action=scenefileform";
var request = http.MultipartRequest('POST', Uri.parse(jspEndPoint));
request.files.add(
  await http.MultipartFile.fromPath(
    'video',
    _video.path
  )
);
var res = await request.send();
print("finished status:");
print(res.statusCode);

}`

Since iOS 11 UIImagePickerController has the property videoExportPreset which can be set to AVAssetExportPresetPassthrough to get the original uncompressed and unmodified file... I suspect this is not set on the image_picker plugin. any help in pinpointing if this is the case would be greatly appreciated.

Looks like it would be a case of updating ios/Classes/FLTImagePickerPlugin.m line 100 with:
if (@available(iOS 11.0, *)) {
_imagePickerController.videoExportPreset = AVAssetExportPresetPassthrough;
}

Hi @fideldonson
Is there any way to reproduce this issue while exporting to local storage or uploading to firebase_storage?
Can you please provide your flutter doctor -v and flutter run --verbose logs, and a minimal complete reproducible code sample?
Thank you

Hi @fideldonson
Is there any way to reproduce this issue while exporting to local storage or uploading to firebase_storage?
Can you please provide your flutter doctor -v and flutter run --verbose logs, and a minimal complete reproducible code sample?
Thank you

Without additional information, we are unfortunately not sure how to resolve this issue.
We are therefore reluctantly going to close this bug for now.
Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.
Could everyone who still has this problem please file a new issue with the exact description of what happens, logs, and the output of flutter doctor -v.
All system setups can be slightly different, so it's always better to open new issues and reference related issues.


Disable Splash Color

Is there a way to disable the splash color when an item is tapped?

Thanks

I'm waiting, too. It's the ripple effect when you press the navigation bar, right?

Would be nice if this is updated in the pub registry. I am new to PR's, but is there any way I can help with that?


Think about populating used_by from weights instead of all_indicators

I'm not sure about the feasibility of this at this point. Some questions are used in indicators but do not have weights, so don't show up in the weights table. For example, F1 is used in am_fun(), but not listed in the weights table - presumable because it is just used as a condition, not a weighted calculation?


Add socat back.

io.Copy doesn't work for us. The main problem is that:

When one side (either pod side or user side) of portforward is closed, we should stop port forwarding.
When one side is closed, the io.Copy use that side as source will close, but the io.Copy use that side as dest won't. (io.Copy doesn't stop when dest is closed until there is new input from source)
However, we can't simply forcibly stop the hanging io.Copy by closing the source. Because TCP is bi-direction, even though one direction is closed (we know because one io.Copy stops), the other direction may not, and that io.Copy might be working. There is no way for us to know it now.

There should be some solution for this problem, and socat must have implemented that. We need more time to investigate it.
So let's switch back to socat for this release.
@abhi
Signed-off-by: Lantao Liu<EMAIL_ADDRESS>

There should be some solution for this problem, and socat must have implemented that. We need more time to investigate it.

Could you open a github issue for tracking this?

@AkihiroSuda Done. https://github.com/containerd/cri/issues/730
Apply LGTM based on https://github.com/containerd/cri/pull/729#pullrequestreview-111076363


Openephys check consistency experiments

This PR improves the checks the OpenEphysBinaryRawIO by:

pre-mapping folder structure in terms of recording nodes, experiments, and recordings
assigning block_index and seg_index after pre-mappping (it is possible that some experiments/recordings are deleted by the user because of errors etc.)
adds checks to ensure that:

experiments (blocks) are consistent acrosse multiple nodes (if present)
streams are consistent across recordings (segments)
the same streams are present in all experiments (blocks)
In case the latter check fails, there is a new option to use the argument experiment_names to select a subset of experiments with consistent streams to be loaded.

Hello @alejoe91! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file neo/rawio/openephysbinaryrawio.py:

Line 34:100: E501 line too long (108 > 99 characters)
Line 34:109: W291 trailing whitespace
Line 40:100: E501 line too long (113 > 99 characters)
Line 40:114: W291 trailing whitespace
Line 68:100: E501 line too long (104 > 99 characters)
Line 69:100: E501 line too long (113 > 99 characters)
Line 410:100: E501 line too long (120 > 99 characters)
Line 412:100: E501 line too long (102 > 99 characters)
Line 445:100: E501 line too long (106 > 99 characters)
Line 451:100: E501 line too long (105 > 99 characters)
Line 455:100: E501 line too long (110 > 99 characters)
Line 466:100: E501 line too long (118 > 99 characters)
Line 467:100: E501 line too long (111 > 99 characters)

@samuelgarcia i don't know why core tests failed! I only change one rawio file... can you check and in case retrigger?

Thanks Alessio.
This is really cool.
For me this OK to be merge.
@JuliaSprenger : I don't known if you want to have a look.
We need it for the release.

Test fails from something unrelated (neurlynx) I re run the test to check.
Unfortunatly the entire dataset will be download again (because test did not finish...)


run Web  Error: Dart library 'dart:ffi' is not available on this platform

$ flutter run
Connected devices:
macOS (desktop) • macos  • darwin-arm64   • macOS 13.5 22G74 darwin-arm64
Chrome (web)    • chrome • web-javascript • Google Chrome 123.0.6312.122

Checking for wireless devices...

[1]: macOS (macos)
[2]: Chrome (chrome)
Please choose one (or "q" to quit): 2
Launching lib/main.dart on Chrome in debug mode...
../../../../.pub-cache/hosted/pub.flutter-io.cn/win32_registry-1.1.2/lib/src/registry.dart:5:8: Error: Dart library 'dart:ffi' is not
available on this platform.
import 'dart:ffi';
       ^
Context: The unavailable library 'dart:ffi' is imported through these packages:

    web_entrypoint.dart => package:gan_flutter_demo => package:win32_registry => package:win32 => dart:ffi
    web_entrypoint.dart => package:gan_flutter_demo => package:win32_registry => package:win32 => package:ffi => dart:ffi
    ...

Detailed import paths for (some of) the these imports:

    web_entrypoint.dart => package:gan_flutter_demo/main.dart => package:win32_registry/win32_registry.dart =>
    package:win32_registry/src/models/models.dart => package:win32_registry/src/models/access_rights.dart => package:win32/win32.dart
    => package:win32/src/bstr.dart => dart:ffi

When I delete the following import, this error disappears, but if I want to run it on Windows, I need to import it again, which makes it troublesome for me to compile back and forth into a Web or Windows application.
import 'package:win32_registry/win32_registry.dart';

You need to conditionally import or export library files.
Check out Conditionally importing and exporting library files.


Include all metric sets from metric-jvm

Include all the metrics sets from metrics-jvm-3.1.0

Coverage increased (+0.02%) to 67.29% when pulling 5f7843539bdd9d6ab78e557cec71febbf0facce6 on mattnelson:master into c6b4c3257b22d47c1fc11890fdb5ea323e34ab81 on dropwizard:master.

Coverage increased (+0.02%) to 67.29% when pulling 5f7843539bdd9d6ab78e557cec71febbf0facce6 on mattnelson:master into c6b4c3257b22d47c1fc11890fdb5ea323e34ab81 on dropwizard:master.

Thanks!


feat(atomic): category Facet

KIT-467
https://coveord.atlassian.net/browse/KIT-467

Currently the facet values aren't accessible with the Tab key

I think the show more should have a margin so its at the same level of the facet it expands.
Some other details, for all the facets before I would consider them as "done" for the first version, they should be as good UX-wise as the JSUI DynamicFacets (which were designed by our UX team Anne-Catherine & Karen)

Search should have a placeholder and an icon
Count should be paler than values, between parentheses and aligned to the left, left of the arrow for category
Show more/less should be capitalized, add +/- if possible
Collapse feature could be a nice addition, but perhaps wait UX decides how to handle it

I think the show more should have a margin so its at the same level of the facet it expands.
Some other details, for all the facets before I would consider them as "done" for the first version, they should be as good UX-wise as the JSUI DynamicFacets (which were designed by our UX team Anne-Catherine & Karen)

Search should have a placeholder and an icon
Count should be paler than values, between parentheses and aligned to the left, left of the arrow for category
Show more/less should be capitalized, add +/- if possible
Collapse feature could be a nice addition, but perhaps wait UX decides how to handle it

Will do, updating the PR.
Updating it to the same colour as JSUI but I put the number of values at the end because it's how they had them in the Coveo doc facets https://docs.coveo.com/en/search/#q=test&t=All&sort=relevancy, I personally found it a bit cleaner but I'm fine with either).
This is a localized string so it'll be addressed in that PR
Yeah I avoided this for now, I wanted UX input about collapsing before I added it


Migrate basic families to the new Tray Publisher

This move all the families that don't require a custom collector from standalone publisher to the new Tray publisher GUI. This is a first step in getting rid of the old standalone publisher.
Testing should be as easy as running the tray publisher from the OpenPype tray menu and trying to publish some families that are available by default.
This is really just a change in the default settings, to have some reasonable defaults.

Not sure how much of these issues are related to this PR :)

Mov file was showing review toggle on but it was not adding it into instance data so no reviewable was generated.

This looks like a bug of the collector plugin.

Tested render family only with exr sequence and mov file. EXR was not able to finish the publishing at all. It was freezed on integrate new plugin at coppying temp files process.

This is strange, but again not related to this PR.

Tested render family only with exr sequence and mov file. EXR was not able to finish the publishing at all. It was freezed on integrate new plugin at coppying temp files process.
Mov file was showing review toggle on but it was not adding it into instance data so no reviewable was generated.

Was that publishing both at the same time as two representations or two individual publishes? I managed to publish just fine.


vector: (x2, y2) should represent a control point rather than the destination point

See https://developer.mozilla.org/en-US/docs/Web/API/CanvasRenderingContext2D/arcTo

Though this is a breaking-change, vector is still an experimental package. It's ok to change the spec.


Add Medicine (Yu) by NexoXP

Song Name
Medicine (Yu)
Artist Name
NexoXP
Source
Youtube
Youtube Link
https://www.youtube.com/watch?v=hDza-lf_dN4
Direct File Link
No response
Song ID
658430
Start Offset [ms]
0
Extra
Created from Auto Nong.
Created for level: 110662932
Downloaded: Si

accept


store somewhere else than setings.json

would this be possible and feasible?

similar to https://github.com/osxzxso/extension-bookmarker/issues/3


Update tcell to the latest 2.x version

Changelog: https://github.com/gdamore/tcell/blob/master/CHANGESv2.adoc
And while we are at it, we can also consider making tcell the default in all code examples.

@dyc3 I got some prep work done (making tcell default, updating documentation), but didn't get to create the PR that updates to 2.x yet.
The next steps should be something like:

update the dependency
update all import paths
verify that none of the breaking changes actually break our build and functionality. The only one that looks worrying is the change of mouse button handling. We may need to use or modify one of the demos to verify the new behavior.

If you have the time to prepare the PR with at least the first two steps (and anything I might have missed), that would help a lot. Alternatively I can get to it a few days from now. I will be of course happy to help with the testing step, maybe we can both poke at it - more eyes gives us a better chance of catching anything that broke.

@dyc3 if you choose to work on the PR, please fork from the devel branch to avoid conflicts and include the latest changes we made.

I'll take a look at it tomorrow. It's currently 3 am where I am and I need sleep haha

We seem to be in the same timezone, so I can relate...

So far I've only updated the import path for tcell to reference v2, and all the tests pass. Seems like a good sign.

While that is good news, it is likely that it only gives a false sense of security. The unit tests in termdash only verify its own logic and only reach up to the terminalapi. The terminal drivers themselves are abstracted behind a fake terminal implementation in the tests.
If I remember correctly, we don't have a single integration test with either termbox or tcell, so the only way to tell if this works correctly may be by running the demos and exercising the functionality.

Cell options are broken. Nothing has color, and I'm not exactly sure why. Font modifiers still work though. I think the way colors were represented was changed?

Thanks for catching that, I do remember reading something about color palette changes in the v2 changelog. We may need to update our tcell library to do any necessary translation.
Let me know if you get tired of looking at it, I can check out your branch and try to propose some solutions.

I'm kinda stumped.
I think fixColor needs to add tcell.ColorValid to the color value? When I try that, I get colors back, but they are all wrong.

I will take a look a bit later tonight and update here. I need to spend some time understanding the change they did to v2.

I think I understand the problem now and I am fairly convinced this is a bug in our tcell library. I will send you a PR branched off your branch that will fix that and also align our color definitions with the standard tcell is using. Since that is the official standard. I just need to figure out how to make this backward compatible for the termbox users out there.

The following PR is addressing the color problem: https://github.com/dyc3/termdash/pull/1
The issue was that our tcell library was depending on the values of tcell's color constants. We shouldn't have done that, those are internal to their implementation and they did change them when upgrading to v2.
Feel free to merge these commits into your PR, we can push it into the devel branch altogether.
Did you find any other incompatible or breaking changes? Any concerns about the change related to the middle mouse button?

I'll go ahead and merge that in.
I haven't tested the mouse button stuff yet. I'll look at it in a bit, I'm currently fighting fires on another project.

Take your time and feel free to let me know if you would like me to take point on this.

I've tested mouse inputs on Linux, and they work as expected. I don't have an easy way to test on windows currently.
The function keys also work as expected, however modifiers are not passed along at all. Is this intentional?

Thank you for testing it, I will give it a go too to confirm later today.
Can you give me a few more details about the modifiers? Do you mean that some of our keys don't work, e.g. KeyCtrlA:
https://github.com/mum4k/termdash/blob/2a7dafa3a835dbe45d9a6eaa2f22e184666c8065/keyboard/keyboard.go#L59
Or do you mean that the new support for modifiers added by tcell in v2 isn't reflected in our API?
https://github.com/gdamore/tcell/blob/7d87d8188c8d3a236c778107d4925a9b2465a5f6/key.go#L73-L79
In other words - did any existing functionality change after upgrading tcell to v2 or are we just missing new functionality?
Additionally is #260 ready for review or do we still need to add something?

Oh wait, I see.
The keys like KeyCtrlA work, but Shift+F1 gives KeyF1.
We're just missing new functionality. #260 is ready to review

Yes that would be a missing functionality and is tracked in #262.
The PR looks good, please let me know if you are planning to send one more PR to add italic and strikethrough before we push the release.

Resolved by #266.


[Volunteer] fix typo in engine_conn_plugin_installation.md

There are some text errors in engine_conn_plugin_installation.md and need to be corrected

Update engine_conn_plugin_installation.md #182


[WFLY-10181] Deadlock for threads executing org.jboss.jca.adapters.jdbc.xa.XAManagedConnectionFactory.isEqual - WildFly Part

Jira: https://issues.jboss.org/browse/WFLY-10181
Please NOTE: this needs upgrade ironjacamar 1.4.9.Final to compile.

I am going to close this for now. I recently sent an email to wildfly-dev about PR's that add failing tests, and this is pretty much a similar situation. PR's like this should be coordinated with the upgrade, so they are either submitted with the component upgrade or after it is merged.


HHH-11721 - PreInsertEventListener that just vetoed ends up throwing NullPointerException because the entity is still managed

https://hibernate.atlassian.net/browse/HHH-11721

@Naros This is a replacement for this Pull Request which only provided a test case. If you have time, let me know if you agree with the proposed fix.
I checked it for PRE_UPDATE, and if a Listener vetoes, the update will be skipped while the rest of actions will proceed just fine.

@gbadner If you have time, would you mind taking a look at this issue. The idea is that if an EventListener vetoes the InsertAction we should throw an exception.


Pull cuda image from NVCR and change to ubi8 base

Switch to ubi8 base cuda image
The ubuntu image does not support ppc64le arch. We are now building (Semeru)
on ppc64le in the cent7 container and require the cuda libs.
Related https://github.com/ibmruntimes/ci-jenkins-pipelines/pull/228
Pull cuda image from nvcr Nvidia
Sometimes pulls fail because DockerHub is rate limited. We are
also facing pull restrictions from DockerHub for Semeru.
Related https://github.com/eclipse-openj9/openj9/pull/20622
Signed-off-by: Adam Brousseau<EMAIL_ADDRESS>

@sxa for review please.


Send SMS notification via twilio

Description
Adds:

phone # validation via Twilio's free api
SMS notifications via Twilio for conversations with SMS source
tests!

Issue
Closes #676
Checklist

[x] Everything passes when running mix test
[x] Ran mix format
[x] No frontend compilation warnings

@reichert621 addressed comments!


nav-underline with disabled button is not grayed

Prerequisites

[X] I have searched for duplicate or closed issues
[X] I have validated any HTML to avoid common problems
[X] I have read the contributing guidelines

Describe the issue
When using nav-underline as described in section Underline of "Navs & tabs" but using a button element instead of an anchor a disabled button still has the primary color.
Reduced test cases

    <button class="nav-link" disabled>Disabled</button>

What operating system(s) are you seeing the problem on?
Windows
What browser(s) are you seeing the problem on?
Chrome, Firefox
What version of Bootstrap are you using?
5.3.0

Can't create a live demo without creating an account there. Closing this issue due to formal error. Bug still exists.

We have this as a class now to your point, but not the pseudo state. https://getbootstrap.com/docs/5.3/components/navs-tabs/#underline
Re-opening so we can tackle.

As far as I understand the button documentation for disabled state the class disabled is only a workaround for anchors, because they ignore the disabled attribute. So buttons should be fine without the class. It's also written there that aria-disabled="true" should be set for these disabled anchors, which is also not the case for the examples in both Navs & tabs and Navbar.

@patrickhlauke I've tried something to tackle the initial issue in https://github.com/twbs/bootstrap/pull/38774. I'd like your thoughts on the aria-disabled="true" mentioned in the previous comment in order to see if I need to update my PR or create another one to tackle this topic separately.

@julien-deramond sorry, coming in late, will have a look at this soon

for the aria-disabled aspect, we should follow-through in our examples with what we say in the actual documentation, so yes we'd need a PR that backfills this to our docs examples

Fixed by #38774


SOLR-16595: second attempt to rationalize time values

Redoing previous PR, this time attempting to commit often and leverage Crave build...

Closing now that we found out my test failure was my environment specific...


@expressjs/triagers lack ability to add labels in express-paginate

The team appears to only have Read instead of Triage permission level.

@dougwilson @wesleytodd I can't add repos to the team permissions, but someone with admin perms can go here to do it https://github.com/orgs/expressjs/teams/triagers/repositories

This repo falls outside of the Express TC, hence why the permissions are missing.


Export interrupt indices as well

There are some use cases where the interrupt indices (interrupt vector numbers) are needed, e.g. when working with the NVIC on Cortex-M chips. The indices could in theory be generated on the application side (or in Microzig) by processing the VectorTable structure at comptime, but it seems a bit easier to just generate something like const VectorIndices = enum(..) { right away via regz.

One regression in the rewrite were the generated system registers for ARM. They would explicitly name a bit position after its interrupt for NVIC registers. Would fixing that regression be enough, or should we still communicate this info regardless?

That sounds reasonable! I'll close this then, I can anyways work around this until the regression is fixed.


docs: 日常文档走查, 层级处理

Checklist

[ ] npm test passes
[ ] tests and/or benchmarks are included
[ ] commit message follows commit guidelines

Description of change

Pull Request Test Coverage Report for Build 545016818

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 93.51%

Totals

Change from base Build 539488498:
0.0%

Covered Lines:
10834

Relevant Lines:
11240

💛  - Coveralls


PR: integrate padatious NER and intent parser into Rasa framework

Description of Problem:
The existing intent and/or NER parsers in Rasa work not so well with little data. Especially NER is difficult with the existing toolbox. For proof-of-concept or rapid prototyping as well as "small" development projects it would be great to have easy-to-use and more or less out-of-the-box solutions which can be adapted by the user/developer directly.
Overview of the Solution:
I would like to integrate a PR which makes use of padatious, an intent parser from the well-known project MyCroft. It uses a NN architecture for intent parsing which is already very acurate with a small number of intent examples and uses regular expression for NER - this makes it fast, easy to adapt and very useful for the task, in my opinion.
So the request is to integrate padatious as an additional combined NER and intent parser into the Rasa framework so that people can choose if they need these features.
Examples (if relevant):
References:
https://mycroft-ai.gitbook.io/docs/mycroft-technologies/padatious
https://github.com/MycroftAI/padatious
Blockers (if relevant):
none that I know of
Definition of Done:

[ ] Code merged from fork
[ ] Tests are added
[ ] Feature described in the docs
[ ] Feature mentioned in the changelog

Thanks for submitting this feature request 🚀 @koaning will get back to you about it soon! ✨

Just from glancing at it is seems that padatious depends on FANN, a neural network library that did not receive an update for nearly two years.

I understand. It does not seem to be the most fancy NN-Toolkit on the planet, but it works really well! What you mention as an alternative is not really a full substitute, you do neither have to come up with a regex yourself (done by padatious) nor to really train on lots of data -- as said, really a few examples suffice and results are really good compared to this.
I didn't benchmark yet, but used it in my own project where it worked just perfect for my understanding. The code (padatious) is a bit hard to read and it's not clear if the original developers are willing to change that... so reimplementing the FANN model in TF or similar may sound like a great idea, but probably takes a lot of efforts.
I can only recommend to try out for yourself - it really beats the existing Rasa tooling in my opinion for this matter (small amount of data, works out of the box, high accuracy).

I'm interested in exploring the tool, but it seems there's too many issues for it to support direct here. The padatious requirements.txt file suggests that it using FANN2 as opposed to FANN which is listed on the mycroft docs page. Inspecting the pypi repo of that project suggest only python 2.6-3.6 are supported while here at Rasa we also support 3.7, 3.8.
I've created a ticket over at the examples repo so that I have it in the back of my mind for experimentation. For now though, it seems like we cannot support the tool directly here.

OK, I understand. Fair enough. If I have some news (maybe I once try to reimplement it in TF or similar) I will get back to you.


possible to use native websockets?

Is it possible to use native websockets instead of socket.io?

Sorry, but not. It's only working with socket.io

The package name is kinda misleading then as native websocket differs from socketio

I second this, it should be called vue-socketio or similar. People looking to use (or even make) a vue-websocket plugin that utilises the native websocket would be disappointed. Either way I don't believe vue-websocket is a good name for this package.

How to use this websocket? There is no specific use

Please rename this github repo to vue-socketio as this is very misleading. I was looking for a native browser JS websocket integration with vue, not socket.io.

I also wasted time with this library when i was looking for native websockets. By the way there is also https://github.com/MetinSeylan/Vue-Socket.io

Thanks a lot, let me see
2017-12-21 0:55 GMT+08:00 flip111<EMAIL_ADDRESS>
I also wasted time with this library when i was looking for native
websockets. By the way there is also https://github.com/
MetinSeylan/Vue-Socket.io
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/icebob/vue-websocket/issues/2#issuecomment-353119469,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AXPl96hAtTiXN-n-Iakkz3KQs4FGFQO9ks5tCTvxgaJpZM4LJv_z
.

I'm unlocking this issue so I can gather feedback.
It seems as though vue-websocket will be this package name, and the owner isn't interested in changing it. So, end of discussion on that particular point I'm afraid.
However, I would like to introduce and supplement the socketio implementation with a native websockets implementation, and in a way that doesn't break backwards compatibility with people who do depend on this package for socketio.
I wanted to see what public opinion was on this change, and whether or not it would be outside the scope of this project. I don't want to remove or break any functionality for those who do use this package for socket.io. Looking forward to hearing your thoughts!

I would be interested in native sockets instead of socket.io You could always fork it and make the change. vue-websocket-native

nope. that's why i gave up.

Apologies while I get up to speed, I've just taken over as the lead maintainer for a while.
I'll test out the example at some point in the next few days and update it

Thanks for the head up @sam3d it's not your fault. I'm getting very frustrated, I've started using VueJs for a personnal project 2 weeks ago and so far it looks like only roadblocks ahead.
None of the tutorial I've followed worked for any project, or seldom. I've used modules where the start function isn't starting anything and most of the time when you link up in GH the usual answer is : provide a demo project if you want us to trust you that's an issue.
I'm not sure if I will ever recommend the VueJS ecosystem.... Or am I alone in the universe?

@Nolaan you are probably alone in that universe. the VueJS ecosystem is perfectly fine, functional, and growing. If you're looking for a native websocket implementation, I suggest you to try going with simply just the websocket api documentation from https://developer.mozilla.org/en-US/docs/Web/API/WebSockets_API ; that's what I ended up doing.

perfectly fine is a little bit meh especially when I think about backward compatibility and dependencies... But probably you're right, don't get me wrong I can communicate with my server over the dev console of Chrome/Firefox (using SSL) just the module won't connect.

@Nolaan Thank you for saying that 🙂 I'm a huge fan of the Vue.js ecosystem - it's definitely still got its fair share of teething problems that's for sure, but on the whole it's actually growing up really well.
I'm sorry to hear you're getting frustrated getting into Vue, I totally get it. I updated the README not too long ago with other alternatives to using this package for native websockets, let me know if there's anything I can do!

Vue eco-system may not be as extensive or mature as React, but between the two, it is easier for me to dive in to Vue to fix things, rather than wait for someone to implement the feature...


Toggle button not working on mobile

Whenever I click darkmode toggle button, a new tab for git project opens. Maybe the reason for this is that toggle button is not properly aligned with github corner button.
Any way to remove github fork button or align toggle button ?

To avoid the overlap of GitHub corner. Now theme switcher will move to left on mobile screen.