Artifactory focal contrib package lists error in releases.jfrog.io

Describe the bug
Running through the standard debian installation at https://jfrog.com/download-jfrog-platform/ results in a Reading package lists... Error! by apt-get for focal (Ubuntu 20.04 - Focal Fossa).
To Reproduce
wget -qO - https://releases.jfrog.io/artifactory/api/gpg/key/public | sudo apt-key add -;
echo "deb https://releases.jfrog.io/artifactory/artifactory-pro-debs focal contrib" | sudo tee -a /etc/apt/sources.list;
sudo apt-get update && sudo apt-get install jfrog-artifactory-pro

Expected behavior
Artifactory gets installed correctly and/or apt list gets updated with focal contrib list.
Observed behavior
$ apt update
Get:1 https://releases.jfrog.io/artifactory/jfrog-debs focal InRelease [2156 B]
Get:2 https://releases.jfrog.io/artifactory/jfrog-debs focal/contrib amd64 Packages [2800 B]
Fetched 4956 B in 1s (9559 B/s)
Reading package lists... Error!
E: Encountered a section with no Package: header
E: Problem with MergeList /var/lib/apt/lists/releases.jfrog.io_artifactory_jfrog-debs_dists_focal_contrib_binary-amd64_Packages
E: The package lists or status file could not be parsed or opened.

Versions

JFrog CLI version: N/A
JFrog CLI operating system: Ubuntu 20.04 Focal
Artifactory Version: N/A
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=20.04
DISTRIB_CODENAME=focal
DISTRIB_DESCRIPTION="Ubuntu 20.04.2 LTS"
NAME="Ubuntu"
VERSION="20.04.2 LTS (Focal Fossa)"

I'm also seeing this issues on Ubuntu 20.04
$ wget -qO - https://releases.jfrog.io/artifactory/api/gpg/key/public | sudo apt-key add -;
$ echo "deb https://releases.jfrog.io/artifactory/jfrog-debs focal contrib" | sudo tee jfrog.list
$ sudo apt update
Hit:1 http://archive.ubuntu.com/ubuntu focal InRelease
Hit:2 http://archive.ubuntu.com/ubuntu focal-updates InRelease
Get:3 http://archive.ubuntu.com/ubuntu focal-backports InRelease [101 kB]
Get:4 http://archive.ubuntu.com/ubuntu focal-security InRelease [114 kB]
Hit:5 https://releases.jfrog.io/artifactory/jfrog-debs focal InRelease
Fetched 214 kB in 1s (370 kB/s)
Reading package lists... Error!
E: Encountered a section with no Package: header
E: Problem with MergeList /var/lib/apt/lists/releases.jfrog.io_artifactory_jfrog-debs_dists_focal_contrib_binary-amd64_Packages
E: The package lists or status file could not be parsed or opened.

+1 (Ubuntu 18.04)

I'm also seeing this issues on Ubuntu 20.04
Reading package lists... Error!
E: Encountered a section with no Package: header
E: Problem with MergeList /var/lib/apt/lists/jfrog.bintray.com_artifactory-debs_dists_bionic_main_binary-i386_Packages
E: The package lists or status file could not be parsed or opened.

@juanrubiom, @nickbroon and @johnmlwright -
You opened this issue on the jfrog-cli GitHub repositpry, although the issue you're reporting has to do with the JFrog Platform debian installation.
To make sure this issue receives the right attention and handled quickly, will you be able to open a ticker to JFrog Support about it?

@eyalbe4

will you be able to open a ticker to JFrog Support about it?

Can you point me to it?
I've found the customer support portal, but I don't have a customer login:
https://support.jfrog.com/s/login/?ec=302&startURL=%2Fs%2F

Hi guys, you probably encounter this bug: https://www.jfrog.com/jira/browse/RTFACT-20460 which is already resolved in Artifactory versions 6.18.x/7.3.x and above. Additional information can be found both in the JIRA itself and in JFrog Release Notes: https://www.jfrog.com/confluence/display/JFROG/Artifactory+Release+Notes. Now, if you are still experiencing the issue on these versions, you may email to<EMAIL_ADDRESS>and elaborate about the use-case while adding steps to reproduce the issue. As a side note, the access to the Support Portal is restricted to entitled Support Contacts only.

The steps to reproduce are as in the initial report.
This a Debian repository created by who every owns and created https://releases.jfrog.io/artifactory/jfrog-debs
They either need to update the version artifactory they are using, or if as you suggest it's relates to missing debian/control files in their packages, they need to update those.

Hi @guy-cohen
Sorry, a bit confused, has this issue been fixed already somewhere or is there a workaround that I can apply locally? I'm trying to install artifactory oss or cpp-ce.
Thanks!

@juanrubio The workaround is to add the missing debian/control files to your packages while the permanent solution is to use newer versions of Artifactory as mentioned above / in this JIRA: https://www.jfrog.com/jira/browse/RTFACT-20460.

@guy-cohen
Thanks, I'll try one of those options.

this worked for me, just susbstitute with your distribution, i used focal running ubuntu 20.X
To determine your distribution, run lsb_release -c or cat /etc/os-release
Example:echo "deb https://releases.jfrog.io/artifactory/artifactory-pro-debs xenial main" | sudo tee -a /etc/apt/sources.list;
wget -qO - https://releases.jfrog.io/artifactory/api/gpg/key/public | sudo apt-key add -;
echo "deb https://releases.jfrog.io/artifactory/artifactory-debs {distribution} main" | sudo tee -a /etc/apt/sources.list;
sudo apt-get update && sudo apt-get install jfrog-artifactory-oss

this worked for me, just susbstitute with your distribution, i used focal running ubuntu 20.X
To determine your distribution, run lsb_release -c or cat /etc/os-release
Example:echo "deb https://releases.jfrog.io/artifactory/artifactory-pro-debs xenial main" | sudo tee -a /etc/apt/sources.list;
wget -qO - https://releases.jfrog.io/artifactory/api/gpg/key/public | sudo apt-key add -;
echo "deb https://releases.jfrog.io/artifactory/artifactory-debs {distribution} main" | sudo tee -a /etc/apt/sources.list;
sudo apt-get update && sudo apt-get install jfrog-artifactory-oss

This is still broken. https://releases.jfrog.io/artifactory/jfrog-debs is owned by JFrog so update to a newer version of Artifactory is not something that a customer or end user can do. JFrog needs to fix this.
I just double checked today. The focal Packages file is missing a few lines of the package details for jfrog-cli 1.45.1 as the following diff shows.
mstankavich@scmv-ord-ctrl-1:~$ diff /var/lib/apt/lists/releases.jfrog.io_artifactory_jfrog-debs_dists_xenial_contrib_binary-amd64_Packages /var/lib/apt/lists/releases.jfrog.io_artifactory_jfrog-debs_dists_focal_contrib_binary-amd64_Packages
417,427d416
< Package: jfrog-cli
< Version: 1.45.1
< Architecture: amd64
< Maintainer: Jfrog<EMAIL_ADDRESS>< Installed-Size: 20747
< Section: misc
< Priority: optional
< Homepage: https://www.jfrog.com/confluence/display/CLI/JFrog+CLI
< Description: Smart client that provides a simple interface that automates access to JFrog products
<  JFrog CLI is a compact and smart client that provides a simple interface that automates access to JFrog products
<  simplifying your automation scripts and making them more readable and easier to maintain.

@MikeStankavich -
I'm trying to figure out what's broken so that we can fix it.
Will you be able to share here the list of steps you're taking?

Sure, I'll be glad to do that. It happens when you specify focal rather than xenial for the distro name in the sources.list. The example below reproduces the issue on a newly created LXD container from Ubuntu cloud images.
mstankavich@lxd-host:~/$ lxc launch ubuntu:20.04
Creating the instance
Instance name is: ample-rat
Starting ample-rat
mstankavich@lxd-host:~/$ lxc exec ample-rat bash
root@ample-rat:~# wget -qO - https://releases.jfrog.io/artifactory/api/gpg/key/public | sudo apt-key add -
OK
root@ample-rat:~# add-apt-repository 'deb https://releases.jfrog.io/artifactory/jfrog-debs focal contrib'
Get:1 http://security.ubuntu.com/ubuntu focal-security InRelease [114 kB]
Hit:2 http://archive.ubuntu.com/ubuntu focal InRelease
Get:3 https://releases.jfrog.io/artifactory/jfrog-debs focal InRelease [2156 B]
Get:4 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages [860 kB]
Get:5 http://archive.ubuntu.com/ubuntu focal-updates InRelease [114 kB]
Get:6 http://security.ubuntu.com/ubuntu focal-security/main Translation-en [166 kB]
Get:7 http://security.ubuntu.com/ubuntu focal-security/main amd64 c-n-f Metadata [8692 B]
Get:8 http://security.ubuntu.com/ubuntu focal-security/restricted amd64 Packages [405 kB]
Get:9 http://security.ubuntu.com/ubuntu focal-security/restricted Translation-en [58.1 kB]
Get:10 http://security.ubuntu.com/ubuntu focal-security/restricted amd64 c-n-f Metadata [508 B]
Get:11 http://security.ubuntu.com/ubuntu focal-security/universe amd64 Packages [639 kB]
Get:12 http://security.ubuntu.com/ubuntu focal-security/universe Translation-en [101 kB]
Get:13 http://security.ubuntu.com/ubuntu focal-security/universe amd64 c-n-f Metadata [12.4 kB]
Get:14 http://security.ubuntu.com/ubuntu focal-security/multiverse amd64 Packages [21.9 kB]
Get:15 http://security.ubuntu.com/ubuntu focal-security/multiverse Translation-en [4948 B]
Get:16 http://security.ubuntu.com/ubuntu focal-security/multiverse amd64 c-n-f Metadata [540 B]
Get:17 https://releases.jfrog.io/artifactory/jfrog-debs focal/contrib amd64 Packages [4689 B]
Get:18 http://archive.ubuntu.com/ubuntu focal-backports InRelease [101 kB]
Get:19 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages [8628 kB]
Get:20 http://archive.ubuntu.com/ubuntu focal/universe Translation-en [5124 kB]
Get:21 http://archive.ubuntu.com/ubuntu focal/universe amd64 c-n-f Metadata [265 kB]
Get:22 http://archive.ubuntu.com/ubuntu focal/multiverse amd64 Packages [144 kB]
Get:23 http://archive.ubuntu.com/ubuntu focal/multiverse Translation-en [104 kB]
Get:24 http://archive.ubuntu.com/ubuntu focal/multiverse amd64 c-n-f Metadata [9136 B]
Get:25 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages [1205 kB]
Get:26 http://archive.ubuntu.com/ubuntu focal-updates/main Translation-en [258 kB]
Get:27 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 c-n-f Metadata [14.2 kB]
Get:28 http://archive.ubuntu.com/ubuntu focal-updates/restricted amd64 Packages [442 kB]
Get:29 http://archive.ubuntu.com/ubuntu focal-updates/restricted amd64 c-n-f Metadata [504 B]
Get:30 http://archive.ubuntu.com/ubuntu focal-updates/universe amd64 Packages [855 kB]
Get:31 http://archive.ubuntu.com/ubuntu focal-updates/universe Translation-en [181 kB]
Get:32 http://archive.ubuntu.com/ubuntu focal-updates/universe amd64 c-n-f Metadata [18.8 kB]
Get:33 http://archive.ubuntu.com/ubuntu focal-updates/multiverse amd64 Packages [24.6 kB]
Get:34 http://archive.ubuntu.com/ubuntu focal-updates/multiverse Translation-en [6776 B]
Get:35 http://archive.ubuntu.com/ubuntu focal-updates/multiverse amd64 c-n-f Metadata [620 B]
Get:36 http://archive.ubuntu.com/ubuntu focal-backports/main amd64 Packages [2568 B]
Get:37 http://archive.ubuntu.com/ubuntu focal-backports/main Translation-en [1120 B]
Get:38 http://archive.ubuntu.com/ubuntu focal-backports/main amd64 c-n-f Metadata [400 B]
Get:39 http://archive.ubuntu.com/ubuntu focal-backports/restricted amd64 c-n-f Metadata [116 B]
Get:40 http://archive.ubuntu.com/ubuntu focal-backports/universe amd64 Packages [5812 B]
Get:41 http://archive.ubuntu.com/ubuntu focal-backports/universe Translation-en [2068 B]
Get:42 http://archive.ubuntu.com/ubuntu focal-backports/universe amd64 c-n-f Metadata [288 B]
Get:43 http://archive.ubuntu.com/ubuntu focal-backports/multiverse amd64 c-n-f Metadata [116 B]
Fetched 19.9 MB in 3s (6096 kB/s)
Reading package lists... Error!
E: Encountered a section with no Package: header
E: Problem with MergeList /var/lib/apt/lists/releases.jfrog.io_artifactory_jfrog-debs_dists_focal_contrib_binary-amd64_Packages
E: The package lists or status file could not be parsed or opened.
root@ample-rat:~#

same for me.

Managed to fix the issue by removing from file
/var/lib/apt/lists/releases.jfrog.io_artifactory_artifactory-debs_dists_focal_main_binary-amd64_Packages
rogue blocks looking like this
Filename: pool/jfrog-artifactory-oss/jfrog-artifactory-oss-7.24.6.deb
SHA1: efc179eb9fd9dc15e23e9f39b45c7ada9f2af69d
SHA256: 1d7fed32a6375f1b9bc5f5aa7875e158fe4272d9fc09c34d1d91713fec7f56cb
Size: 422044480

@hgjuric Thanks!

Thanks so much for the info @hgjuric!
 If anyone has an idea on how to prevent this from happening, please let us know.

I think you'll find that broken package block for 1.45.1 is in the Packages file that comes straight from
https://releases.jfrog.io/artifactory/jfrog-debs focal/contrib amd64 Packages

As I noted in my previous post I can reproduce this failure in a completely fresh build of Ubuntu by simply adding the repository into apt sources and updating. You can get the file directly from the repo at https://releases.jfrog.io/artifactory/jfrog-debs/dists/focal/contrib/binary-amd64/Packages. Have a look at line 417. You'll see that the first few lines of the package metadata for jfrog-cli 1.45.1 are missing. I found this by running a diff of the focal Packages file against the xenial Packages file.

I have the same issue on Ubuntu 20.04.3 LTS x86_64 (5.4.0-80-generic).
@hgjuric fix of deleting the file did not work for me.
Hit:1 http://archive.ubuntu.com/ubuntu focal InRelease
Hit:2 http://archive.ubuntu.com/ubuntu focal-updates InRelease
Hit:3 http://archive.ubuntu.com/ubuntu focal-backports InRelease
Ign:4 https://pkg.jenkins.io/debian-stable binary/ InRelease
Hit:5 https://pkg.jenkins.io/debian-stable binary/ Release
Hit:6 http://archive.ubuntu.com/ubuntu focal-security InRelease
Hit:8 https://jfrog.bintray.com/artifactory-debs bionic InRelease
Reading package lists... Error!
E: flAbsPath on /var/lib/dpkg/status failed - realpath (2: No such file or directory)
E: Encountered a section with no Package: header
E: Problem with MergeList /var/lib/apt/lists/jfrog.bintray.com_artifactory-debs_dists_bionic_main_binary-amd64_Packages
E: The package lists or status file could not be parsed or opened.

@mnemocron Deleting the file is not the solution. You have to delete rogue blocks from the file, not the files itself.
They have only 4 lines and look like this:
Filename: pool/jfrog-artifactory-oss/jfrog-artifactory-oss-7.24.6.deb SHA1: efc179eb9fd9dc15e23e9f39b45c7ada9f2af69d SHA256: 1d7fed32a6375f1b9bc5f5aa7875e158fe4272d9fc09c34d1d91713fec7f56cb Size: 422044480

i just left latest package, run apt update and seems ok now:
cat /etc/apt/sources.list.d/jfrog.list deb https://jfrog.bintray.com/artifactory-debs focal main
`cat /var/lib/apt/lists/jfrog.bintray.com_artifactory-debs_dists_focal_main_binary-amd64_Packages
Package: jfrog-artifactory-jcr
Version: 7.25.7
Section: misc
Priority: low
Architecture: all
Depends: net-tools
Conflicts: jfrog-artifactory-pro, jfrog-artifactory-vrcs, jfrog-artifactory-oss, jfrog-artifactory-cpp-ce
Provides: artifactory
Installed-Size: 874020
Maintainer<EMAIL_ADDRESS>Description: Artifactory is an enterprise repository for binaries. It offers advanced artifacts proxying, caching and
management facilities to provide a robust, reproducible and independent build environment when using Maven 2/3,
Gradle and Ant/Ivy.
Homepage: http://www.jfrog.com/artifactory-parent/jfrog-artifactory-jcr-parent/jfrog-artifactory-jcr/
Filename: pool/jfrog-artifactory-jcr/jfrog-artifactory-jcr-7.25.7.deb
SHA1: 52f91f4deab4ecd40bedc4dccde76b7742d73015
SHA256: d09d5ccd93ac41d36a63279f262d2e182a8eb9dcd3dbeb17c6e31b626109595c
Size: 451683192
Package: jfrog-artifactory-cpp-ce
Version: 7.25.7
Section: misc
Priority: low
Architecture: amd64
Depends: net-tools
Conflicts: jfrog-artifactory-pro, jfrog-artifactory-vrcs, jfrog-artifactory-oss, jfrog-artifactory-jcr
Provides: artifactory
Installed-Size: 854767
Maintainer<EMAIL_ADDRESS>Description: Artifactory is an enterprise repository for binaries. It offers advanced artifacts proxying, caching and
management facilities to provide a robust, reproducible and independent build environment when using Maven 2/3,
Gradle and Ant/Ivy.
Homepage: http://www.jfrog.com/artifactory-parent/jfrog-artifactory-conan-ce-parent/jfrog-artifactory-cpp-ce/
Filename: pool/jfrog-artifactory-cpp-ce/jfrog-artifactory-cpp-ce-7.25.7.deb
SHA1: ae3b385af30a0d4489a478a0afb9ddbe7d8fa42e
SHA256: 2e938d5b0a61dd6120e5851506f2da631a045f322db25ba9847583f267dfaed3
Package: jfrog-artifactory-oss
Version: 7.25.7
Section: misc
Priority: low
Architecture: amd64
Depends: net-tools
Conflicts: jfrog-artifactory-pro, jfrog-artifactory-vrcs, jfrog-artifactory-cpp-ce, jfrog-artifactory-jcr
Provides: artifactory
Installed-Size: 851865
Maintainer<EMAIL_ADDRESS>Description: Artifactory is an enterprise repository for binaries. It offers advanced artifacts proxying, caching and
management facilities to provide a robust, reproducible and independent build environment when using Maven 2/3,
Gradle and Ant/Ivy.
Homepage: http://www.jfrog.com/artifactory-parent/artifactory-distribution-parent/jfrog-artifactory-oss/
Filename: pool/jfrog-artifactory-oss/jfrog-artifactory-oss-7.25.7.deb
SHA1: 4c78f7b9bc25a064d65eb8630c26e109f024b7dd
SHA256: ba69c81bf06f74e99f3a7145fc86d28f824d2899ea9550f1f5c7611fd27df532
Size: 428922040
`
thanks!

@blka You are referencing a different repository. The issue that I ran into is with the jfrog-debs repo, not the artifactory-debs repo. I just followed the reproduction scenario that I posted earlier on this thread and confirmed that the issue still exists.

I can confirm that this is still active. Just tried to do a clean install and had to remove the rouge blocks to get it to work.

All -
Does anyone knows which installation script causes this? Is it jfrog-cli's debian installer or Artifactory's? If anyone has a suggested fix to prevent this from happening to others, please let us know and we'll gladly implement it.

It's the package metadata for jfrog-cli in the jfrog-debs repo that is generated by the repository manager. As I noted earlier on this thread you can see this by simply downloading the Packages file for Focal from https://releases.jfrog.io/artifactory/jfrog-debs/dists/focal/contrib/binary-amd64/Packages. Have a look at line 417. You'll see that the first few lines of the package metadata for jfrog-cli 1.45.1 are missing. Compare it to the same Packages file for Xenial.

Hi @MikeStankavich ,
Thanks for the detailed description.
There was indeed a corruption in the packages file as you stated, I reindexed the repository and it fixed the issue.
We will inspect it deeper to understand the root cause which led to this state.
As for now, here is a simple docker run command to show that it is now fixed.
docker run ubuntu:20.04 /bin/bash -c 'apt-get update ; apt-get install -y wget gnupg2 ; wget -qO - https://releases.jfrog.io/artifactory/api/gpg/key/public | apt-key add -; echo "deb https://releases.jfrog.io/artifactory/jfrog-debs focal contrib" | tee -a /etc/apt/sources.list; apt-get update ; apt-get install -y jfrog-cli=1.45.1 ; jfrog --version'

Looks like there's a similar issue with a different repository. Thanks to @matankatz for his handy docker repo script. I was able to update the repository from "deb https://releases.jfrog.io/artifactory/jfrog-debs focal contrib" to "deb https://jfrog.bintray.com/artifactory-debs bionic main" and recreate the error that @rhmltrbch reported. Hopefully that repo can also be reindexed.
docker run ubuntu:18.04 /bin/bash -c 'apt-get update ; apt-get install -y wget gnupg2 ; wget -qO - https://releases.jfrog.io/artifactory/api/gpg/key/public | apt-key add -; echo "deb https://jfrog.bintray.com/artifactory-debs bionic main" | tee -a /etc/apt/sources.list; apt-get update ; apt-get install -y jfrog-cli=1.45.1 ; jfrog --version'

Reading package lists...
E: Encountered a section with no Package: header
E: Problem with MergeList /var/lib/apt/lists/jfrog.bintray.com_artifactory-debs_dists_bionic_main_binary-amd64_Packages.lz4
E: The package lists or status file could not be parsed or opened.
Reading package lists...
E: Encountered a section with no Package: header
E: Problem with MergeList /var/lib/apt/lists/jfrog.bintray.com_artifactory-debs_dists_bionic_main_binary-amd64_Packages.lz4

It's also worth noting bintray has been deprecated. See https://jfrog.com/blog/into-the-sunset-bintray-jcenter-gocenter-and-chartcenter/. So that jfrog.bintray.com repo may not be maintained going forward.

@hgjuric So how do I fix this? I did not find any 4 line entries in that file. apt update is still broken. If I delete the file, it is just generated again by apt update. I don't really need jfrog. Is there a way to just remove it. I need my apt working again.

@hgjuric https://jfrog.bintray.com is still functioning and maintained, as this redirects to https://releases.jfrog.io/artifactory so nothing to worry about there.
I reindexed the malfunctioned repository and now it works, simply doing apt-get update should replace the corrupted file exists locally on your machine with the fixed one.

@matankatz Could you als reindex the https://jfrog.bintray.com/artifactory-debs buster repo since I have the same issue there
`...
Hit:4 https://jfrog.bintray.com/artifactory-debs buster InRelease
...
Encountered a section with no Package: header
Problem with MergeList /var/lib/apt/lists/jfrog.bintray.com_artifactory-debs_dists_buster_main_binary-amd64_Packages
The package lists or status file could not be parsed or opened.
Can't call method "policy" on an undefined value at /usr/bin/apt-show-versions line 53.
Reading package lists... Error!
E: Problem executing scripts APT::Update::Post-Invoke-Success 'test -x /usr/bin/apt-show-versions || exit 0 ; apt-show-versions -i'
E: Sub-process returned an error code
E: Encountered a section with no Package: header
E: Problem with MergeList /var/lib/apt/lists/jfrog.bintray.com_artifactory-debs_dists_buster_main_binary-amd64_Packages
E: The package lists or status file could not be parsed or opened.
`

And same for ubuntu bionic I guess
Get:15 https://releases.jfrog.io/artifactory/jfrog-debs bionic/contrib amd64 Packages [4719 B]
Fetched 4262 kB in 1s (3053 kB/s)
Reading package lists... Error!
W: Skipping acquire of configured file 'main/binary-amd64/Packages' as repository 'https://releases.jfrog.io/artifactory/jfrog-debs bionic InRelease' doesn't have the component 'main' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'main/i18n/Translation-en' as repository 'https://releases.jfrog.io/artifactory/jfrog-debs bionic InRelease' doesn't have the component 'main' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'main/cnf/Commands-amd64' as repository 'https://releases.jfrog.io/artifactory/jfrog-debs bionic InRelease' doesn't have the component 'main' (component misspelt in sources.list?)
E: Encountered a section with no Package: header
E: Problem with MergeList /var/lib/apt/lists/jfrog.bintray.com_artifactory-debs_dists_bionic_main_binary-amd64_Packages
E: The package lists or status file could not be parsed or opened.

Same in Focal
E: Encountered a section with no Package: header
E: Problem with MergeList /var/lib/apt/lists/releases.jfrog.io_artifactory_artifactory-debs_dists_focal_main_binary-amd64_Packages
E: The package lists or status file could not be parsed or opened.

yup, it was fixed yesterday but it's back today, on bionic. issue appears on 7.25.5 for me
Filename: pool/jfrog-artifactory-cpp-ce/jfrog-artifactory-cpp-ce-7.25.5.deb
SHA1: c248aee5e89334da2aa00054e2767d099ae772ae
SHA256: 2d2276e860240105006f874454bf310d8cf03a628222adb4b9fbb19d09958802
Size: 431898980

Filename: pool/jfrog-artifactory-oss/jfrog-artifactory-oss-7.25.5.deb
SHA1: 780c117b7f0de93a9c0cde86f740d4cbe4fbc3b4
SHA256: 43a7462bb56392133aac227985bb2dc33835d58b0b1d1db209bdb341087f4c9f
Size: 428920066

Filename: pool/jfrog-artifactory-cpp-ce/jfrog-artifactory-cpp-ce-7.25.5.deb
SHA1: c248aee5e89334da2aa00054e2767d099ae772ae
SHA256: 2d2276e860240105006f874454bf310d8cf03a628222adb4b9fbb19d09958802
Size: 431898980

I see this problem today for xenial

Same today on Debian 10 :
rm -r /var/lib/apt/lists/*
apt clean && apt update

[...]
Get:12 https://releases.jfrog.io/artifactory/artifactory-debs stretch InRelease [2928 B]
Get:13 https://releases.jfrog.io/artifactory/artifactory-debs stretch/main amd64 Packages [43.0 kB]
Fetched 14.7 MB in 3s (4767 kB/s)
Reading package lists... Error!
 Error!
W: Target Packages (contrib/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:60 and /etc/apt/sources.list:61
W: Target Packages (contrib/binary-i386/Packages) is configured multiple times in /etc/apt/sources.list:60 and /etc/apt/sources.list:61
W: Target Packages (contrib/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:60 and /etc/apt/sources.list:61
W: Target Translations (contrib/i18n/Translation-en_US) is configured multiple times in /etc/apt/sources.list:60 and /etc/apt/sources.list:61
W: Target Translations (contrib/i18n/Translation-en) is configured multiple times in /etc/apt/sources.list:60 and /etc/apt/sources.list:61
W: Target CNF (contrib/cnf/Commands-amd64) is configured multiple times in /etc/apt/sources.list:60 and /etc/apt/sources.list:61
W: Target CNF (contrib/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list:60 and /etc/apt/sources.list:61
W: Target Packages (contrib/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:60 and /etc/apt/sources.list:62
W: Target Packages (contrib/binary-i386/Packages) is configured multiple times in /etc/apt/sources.list:60 and /etc/apt/sources.list:62
W: Target Packages (contrib/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:60 and /etc/apt/sources.list:62
W: Target Translations (contrib/i18n/Translation-en_US) is configured multiple times in /etc/apt/sources.list:60 and /etc/apt/sources.list:62
W: Target Translations (contrib/i18n/Translation-en) is configured multiple times in /etc/apt/sources.list:60 and /etc/apt/sources.list:62
W: Target CNF (contrib/cnf/Commands-amd64) is configured multiple times in /etc/apt/sources.list:60 and /etc/apt/sources.list:62
W: Target CNF (contrib/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list:60 and /etc/apt/sources.list:62
W: Target Packages (contrib/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:60 and /etc/apt/sources.list:61
W: Target Packages (contrib/binary-i386/Packages) is configured multiple times in /etc/apt/sources.list:60 and /etc/apt/sources.list:61
W: Target Packages (contrib/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:60 and /etc/apt/sources.list:61
W: Target Translations (contrib/i18n/Translation-en_US) is configured multiple times in /etc/apt/sources.list:60 and /etc/apt/sources.list:61
W: Target Translations (contrib/i18n/Translation-en) is configured multiple times in /etc/apt/sources.list:60 and /etc/apt/sources.list:61
W: Target CNF (contrib/cnf/Commands-amd64) is configured multiple times in /etc/apt/sources.list:60 and /etc/apt/sources.list:61
W: Target CNF (contrib/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list:60 and /etc/apt/sources.list:61
W: Target Packages (contrib/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:60 and /etc/apt/sources.list:62
W: Target Packages (contrib/binary-i386/Packages) is configured multiple times in /etc/apt/sources.list:60 and /etc/apt/sources.list:62
W: Target Packages (contrib/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:60 and /etc/apt/sources.list:62
W: Target Translations (contrib/i18n/Translation-en_US) is configured multiple times in /etc/apt/sources.list:60 and /etc/apt/sources.list:62
W: Target Translations (contrib/i18n/Translation-en) is configured multiple times in /etc/apt/sources.list:60 and /etc/apt/sources.list:62
W: Target CNF (contrib/cnf/Commands-amd64) is configured multiple times in /etc/apt/sources.list:60 and /etc/apt/sources.list:62
W: Target CNF (contrib/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list:60 and /etc/apt/sources.list:62
E: Encountered a section with no Package: header
E: Problem with MergeList /var/lib/apt/lists/jfrog.bintray.com_artifactory-debs_dists_bionic_main_binary-amd64_Packages
E: The package lists or status file could not be parsed or opened.`
Can you please advise how to fix this? I have spent two days trying to resolve this issue reading blogs etc.
Thank you

All -
Updating here that a permanent was created and will be deployed soon.
We'll send out another update soon.

Hi All,
We have upgraded Artifactory with the version containing the fix.
I was able to install Artifactory from artifactory-debs repository.
The entire issue is resolved now and shouldn't re-appear again.

@matankatz you know the instructions still specify to use xenial .... a distribution that has been End of Life for a year, right? https://www.jfrog.com/confluence/display/CLI/JFrog+CLI#JFrogCLI-Downloadandinstallation

@matankatz you know the instructions still specify to use xenial .... a distribution that has been End of Life for a year, right? https://www.jfrog.com/confluence/display/CLI/JFrog+CLI#JFrogCLI-Downloadandinstallation

Still says xenial in Mar 2023


Upgrade osv-scanner to 1.7.4

Upgrading osv-scanner to version 1.7.4. I just copied how #17 did the upgrade last time. We need this in order to run this CI job against our gradle verification-metadata files.
The tool hal the following complete changelog:
Features:

Support scanning gradle/verification-metadata.xml files.

Misc:

Hide unimportant Debian vulnerabilities to reduce noise.

I'm not going to sign a CLA for such a trivial change. I'll just leave this here. Hope you bring the upgrade upstream one way or another :)


Does this use sketchtool for exporting

Hey thanks for making this tool. Have you tried using the sketch tool for exporting the layers.
http://bohemiancoders.tumblr.com/post/89354240665/making-a-toolchain-not-just-a-tool

Thank you for your information. wow... I dont know this tool.
I guess sketchtool dump [file] is very useful and fast. I'll think this can use.


cifs.ko in kernel modules

Is your feature request related to a problem? Please describe
Can somebody tell me where I can find cifs.ko module compatible with this kernel or implement it to core? I want to mount smb share directly into file system using cifsMenager but I need cifs.ko in kernel to do it.
Describe the solution you'd like
Implement cifs.ko into a kernel
Describe alternatives you've considered
Provide compatible cifs.ko file, so I can ismod it into kernel file myself
Please specify the version of Windows Subsystem for Android
2303.40000.5.0

We're working on a solution for file sharing, so you shouldn't need to mount an SMB share when that's ready.  We don't support modifying the kernel.

We're working on a solution for file sharing, so you shouldn't need to mount an SMB share when that's ready. We don't support modifying the kernel.

But I need my app to think it has access to a normal folder when looking at smb share


Zend_Controller_Action :: render does not work properly with alternative suffixes

In an action controller when you do :
$this->render('index');

in an action method that has not the same name as the controller, and use an alternative suffix, views are resolved with the action name, and phtml suffix.
This is because render() calls directly viewRenderer->render(), and Oops ViewResolver operates on preDispatch.
It seems that the best solution is to rewrite the ViewResolver.

Completely rewritten dispatching and view rendering
Commit to come...

Fixed in last release with custom ViewRenderer


Spec and implement StableHLO Quantization with verifiers

Parent ticket to track any open/ new quantization verifier tasks
### Tasks
- [ ] https://github.com/openxla/stablehlo/issues/2074
- [ ] https://github.com/openxla/stablehlo/issues/2145
- [x] Update the status.md to reflect that type inference for quantized operations are mostly infeasible.

@abhigunj Can we close this?


Connect to Mobile

Think about tab (after Wallet item) in profile page where it can offer QR code and/or quicker ways to connect account to eSteem Mobile

Implemented @feruzm
@fildunsky maybe we can make more stylish app qr codes?

Cool! Maybe something like this? I've checked. QRs seems to be readable anyway.

@fildunsky looking great!


⚠ AGEG website (prod) has degraded performance

In 69f3eab, AGEG website (prod) (https://www.ageg.ca/) experienced degraded performance:

HTTP code: 200
Response time: 1840 ms

Resolved: AGEG website (prod) performance has improved in 2da09c8.


Time to modernize csproj and drop old TargetFramework entries

Looks like we need to make some updates to the CSPROJ. It's surprising that sl5 is still a supported target in there! Time to modernize :-)
Originally posted by @nblumhardt in https://github.com/sprache/Sprache/issues/162#issuecomment-857194276

Which targets should be supported? Only .net standard 2.x?

Thanks! 👍
I think netstandard2.0 and net5.0 would be my picks; it's largely a matter of opinion, though.
For netstandard2.0, null checking can be enabled with some fiddling around, and this would keep (newer) .NET Framework versions supported, while not requiring .NET Framework to be installed during development.
net5.0 has a lower deployment footprint and will be a better fit for newer apps.

.net core 3.1 is LTS and has netstandard2.1 support. Does this bring any benefit over netstandard2.0 when using the lib in .net core 3.1 project?

Would guess there's some modest benefit, but, also some advantages to starting fresh without additional targets to carry forwards :-)

I would go with netstandard2.0 (classic .net framework, Xamarin.Android with VS2017 and UWP), netstandard2.1 (Xamarin.Android with VS2019 and .net core 3.1) and net5.0 to have best compatibility.

I could live with that! :-) 👍

Do you already had some time?

Thanks for the nudge! Sorry, no, not looking good for the next few weeks - all help appreciated.

all help appreciated.

I made a quick fix in PR #173 .
You should look later in code for old hacks that can be removed.

what about .net 6 support and final release of version 3 of the lib? @nblumhardt


Adding V1 and V2 types

As per @bladyjoker 's note, I found out some valid concerns about deprecating legacy ledger api types: old ledger types can used as datum to some data-providing scripts like oracles. In these cases, user might need to write their own types representing older ledger types.
To address, we need to add back V1 and V2 scripts to plutrach-ledger-api.

I think as part of this issue, we might as well mirror the structure of plutus-ledger-api. I'm already doing it for #655, just with fewer public modules.

Yeah..
We are circling back

Thanks folks! @kozross I think it would be convenient to mirror PLA structure, but I don't find it incredibly important as long as we have all the types implemented.

Why not make it automatically derived from upstream

We don't have funds for that

Done with #690.


Is the network 'fixed' by dataset?

Hello, thank you for your amazing job!
I have a question about your work.
Is the network 'fixed' by dataset?
I mean if I use kitti_pth to my own dataset(the params of cameras are different with kitti cameras totally), can I get the right depth?
Thank you!

This network only predicts the disparity of between left & right views. Afterwards, you can compute the depth using the well-known formula based on the disparity and your camera parameters.

@aeolusguan thank you for your reply!
I mean the baseline of my setero camera is totally different with kitti, can I get the correct disparity by kitti_pth?
And according your answear, why do we distinguish between kitti_pth and other_pth, can't we just use one pth to detect all?

The difference between kitty_pth and other_pth lies the different training set we use. It would be a promising way to mix different datasets and get a single model to detect all.
The disparity prediction is not highly correlated with the baseline of stereo camera. If your custom data is also from autonomous driving scenarios like KITTI, and not too large (I recommend the stereo image <720p), I think you would get good disparity regardless of the difference in baseline.

@aeolusguan Thank you!


"leak" as in "memory leak" filtered out as profanity

Closed by 04cc66016d2746569191a5b5e93580f331f93f66, thanks @tdykstra.


Add development roadmap link

@mrtavor could you please add to the footer the Development roadmap link? Of course, with adding the tr_key to the Crowdin.

Okay 👍


Add support for message escape and cancel in MessageModel

Hoist P/R Checklist
Pull request authors: Review and check off the below. Items that do not apply can also be
checked off to indicate they have been considered. If unclear if a step is relevant, please leave
unchecked and note in comments.

[x] Caught up with develop branch as of last change.
[x] Added CHANGELOG entry.
[x] Reviewed for breaking changes.
[x] Update doc comments / prop-types not required.
[x] Reviewed and tested on Mobile.
[x] Toolbox branch / PR determined not required.

If your change is still a WIP, please use the "Create draft pull request" option in the split
button below to indicate it is not ready yet for a final review.

Pull request reviewers: when merging this P/R, please consider using a squash commit to
collapse multiple intermediate commits into a single commit representing the overall feature
change. This helps keep the commit log clean and easy to scan across releases. PRs containing a
single commit should be rebased when possible.

Can we add some buttons to our toolbox example that illustrate?   No need to over do it, but one or two uses would be great.

Toolbox PR created to add two example buttons demonstrating the cancelOnEscape prop on the popups example panel. Refer to: https://github.com/xh/toolbox/pull/593


What about storing data for password-less access ?

Hey, great work on this.
I am currently using some HMD data for my work, and would really like to be able to store datasets directly into the packages (i.e. without asking end users for credentials). Taking a look at your code, I wander if you considered this option: did you saw somewhere a clause that does not allow you to redistribute the datas ?
I could for example think of a routine check in CI, ran say weekly or monthly, that would download and store the main zip file in some artefact dependency.
What do you think ?

Edit: From their user agreement, it looks like the datasets are CC BY 4.0, which means that we are free to redistribute them.

Hi Oskar
Thanks for the note.
Yeah that would definitely doable and rather pull from an archive up on GitHub. I'll look at what Alec did for his packages that distribute datasets. I initially did the password version to keep everything on their servers + access control.
I'll look at an automated runner to check once a month and then flag if they add new countries or tables that aren't considered yet.

Patrick,
For the moment, I drafted a script to download offline what i need in https://github.com/JuliaSurv/RateTables.jl (look in the data folder) but of course if I can depend directly on HMD.jl to obtain these datas that would be much cleaner :)
This would also require that HMD is registered.


Kill HRGN

Summary of the Pull Request
My understanding is that the XAML framework uses another way of getting mouse input that doesn't work with WM_SYSCOMMAND with SC_MOVE. It looks like it "steals" our mouse messages like WM_LBUTTONDOWN.
Before, we were cutting (with HRGNs) the drag bar part of the XAML islands window in order to catch mouse messages and be able to implement the drag bar that can move the window. However this "cut" doesn't only apply to input (mouse messages) but also to the graphics so we had to paint behind with the same color as the drag bar using GDI to hide the fact that we were cutting the window.
The main issue with this is that we have to replicate exactly the rendering on the XAML drag bar using GDI and this is bad because:

it's hard to keep track of the right color: if a dialog is open, it will cover the whole window including the drag bar with a transparent white layer and it's hard to keep track of those things.
we can't do acrylic with GDI

So I found another method, which is to instead put a "drag window" exactly where the drag bar is, but on top of the XAML islands window (in Z order). I've found that this makes us receive the WM_LBUTTONDOWN messages. That window has to have the WS_EX_LAYERED style and I don't know why. Also we have to recreate the window on every resize (see comments).
References
PR Checklist

[x] Closes #4744. Closes #2100.
[x] CLA signed. If not, go over here and sign the CLA
[x] I've discussed this with core contributors already. If not checked, I'm ready to accept this work might be rejected in favor of a different grand plan. Issue number where discussion took place: #4744

Detailed Description of the Pull Request / Additional comments
Validation Steps Performed

!!!!

It works but I wouldn't be that happy about it because it's very hacky:

I have to recreate a window on every resize because otherwise it mysteriously doesn't receive mouse messages  and I don't understand why.
I have to use WS_EX_LAYERED on a child window and I don't understand why.

I mean, I really like this. I'm certainly always hesitant about changes to our window, so I'd want to keep a careful eye on this, but just playing with this, it doesn't seem like anything else has regressed.
I'm definitely curious about why we need to remake a new HWND every time the window resizes. That's certainly really odd. Maybe the island window is placing itself on top of the draw window on a resize, and we just need to move the drag window back on top of the island window (in the z-order)? I'm no expert here so that's just a guess.

Would this also probably fix #4166 (by virtue of just not having a grab bar at all)?
@DHowett-MSFT and I spoke about it, and if it doesn't end up working, and creates more issues that are less solvable, it's easy enough to revert before 1.0. I've played with this and I honestly don't think it's bad. @greg904 If you're okay with this going in, I think we're okay with this change.

It doesn't fix #4166. Now the big gray rectangle that covers the min/max controls is "invisible" when the bug happens but it's still "there" and catches mouse input:

@greg904 If you're okay with this going in, I think we're okay with this change.

OK, I'm OK.

I absolutely love that this lets us hit test even over the tab bar and do, largely, whatever the heck we want. In the future, we could even make it ask XAML "what is underneath the cursor" before doing anything. I am so excited about this.

@DHowett-MSFT

I'd prefer we preserve the color -- it's more uniform-looking 😄

Ok. I will do this later when I have time.

I absolutely love that this lets us hit test even over the tab bar and do, largely, whatever the heck we want. In the future, we could even make it ask XAML "what is underneath the cursor" before doing anything. I am so excited about this.

I'm not sure that this is true. Right now, either the XAML islands window receives the input either it's the "drag window" that is put on top of the drag bar.
Maybe you got that impression from the fact that I said this originally:

I got this idea by using looking at the Settings UWP app's window using a tool called Spy++.
It looks like it does something similar to this (but not exactly this because the window's size is not exactly the same as the title bar's size) with a window called ApplicationFrameInputSinkWindow that only receive messages when I put my mouse on the drag bar:

Unfortunately I was not able to replicate the behavior from ApplicationFrameHost.exe. It looks like it's able to somehow control when either the ApplicationFrameInputSinkWindow window receives the message or when the window for XAML receives the messages. I don't understand how it works.
Another mystery is that for UWP apps, this ApplicationFrameInputSinkWindow window is not actually on the drag bar. It's below the drag bar and covers the whole window yet it still receives messages only when I move my cursor on the drag bar and those messages have negative Y coordinates because the cursor is not actually on the window... except it's not always the case. I have an UWP app where I called the title bar API to set everything as draggable and now this ApplicationFrameInputSinkWindow window doesn't even receive messages anymore when hovering over the title bar but I can still drag the window. This is very weird!

Nah, I was being more wishful/hopeful :smile: like, if we could get input on the drag bar window we could push it down into Xaml land ourselves, or some-other-how reflect it into the input queue. That's a problem for future-us.

I'd prefer we preserve the color -- it's more uniform-looking 😄

done

Please note that this fixes #2100 but because I use the drag bar color to fill the background while resizing, then while resizing, if the about dialog is open the resized area will have the background color of the title bar, ignoring the fact that the dialog is open.
This is not worse than before: the bug already existed before. The bug is basically the same as #2100 but for the window background while resizing but because #2100 only mentions "the title bar" then this PR does close #2100.
I don't think that this is really important because when this is fixed: https://github.com/microsoft/microsoft-ui-xaml/issues/759, we will be able to get rid of this workaround.
So I don't think it's necessary to open an issue for this small thing.

@msftbot make sure @zadjii-msft and @DHowett-MSFT sign off

I'm tempted to let this one sit until we've got a fix for #4166, simply from the fact that it'll be easier to debug #4166 without this fix 😄
At the same time, I also really like this fix for what doors it opens for us, so ¯\_(ツ)_/¯

I bet there's a way to get it working without having to recreate the
window every time.

I hope too. I have not found a way to do it unfortunately.

I tried briefly to do the resizing thing, and yeah -- I was having
some Z order issues and couldn't even get the window to reliably paint
(i tried making it red so that i could see what was happening)
Weirdly, adding a WM_PAINT handler made the window totally
hit-testable even when it was resized... perhaps there's something
interesting here?

I have tried adding a WM_PAINT handler in the drag window that does:
case WM_PAINT:
{
    PAINTSTRUCT ps;
    BeginPaint(window, &ps);
    EndPaint(window, &ps);
    return 0;
}

And using MoveWindow to move the drag window in _RecreateDragBarWindow instead of recreating.
But it doesn't work.

The drag region is still hit testable when the application has been
fullscreened; maybe we should suppress it?

Fixed in c3759587.

It doesn't feel incorrect; the window can be interacted with just like
normal.

Yes.

Should we be trying to get the WM_NC events inside this window
instead of tunneling normal events through to the parent window as NC
events? I'm not sure on this one at all. 😄

I think that in the drag window proc, either:

We tunnel the normal events through to the parent window as NC
events so that DefWindowProc will be called with the window parent HWND and will handle the dragging/resizing for us.
We could call DefWindowProc directly with the window parent HWND instead of SendMessage.
We could try to handle resizing/dragging ourselves by sending WM_SYSCOMMAND with SC_MOVE/SC_SIZE. It's probably what DefWindowProc already does.

But I think that in all cases, we have to tunnel something to the parent window: initially, I tried to send WM_SYSCOMMAND events with SC_MOVE to the drag bar window and what happened was that when I clicked on the drag bar, it would drag the drag bar instead of the whole window. So I made it send the message to the parent window instead. I'm no expert at this.

Wow so now (maybe before too?) the drag bar is broken in Release mode but works in Debug. This is bad. I don't know why.

BTW I'm not sure how to use the spell checker bot. I ran the command to accept the changes but it created the .github/actions/spell-check/whitelist/c3759587195744a3a2e01e2be4ee44ef1f6ab100.txt file and I don't see any file with the same weird name in that directory so I don't really understand.

@greg904 The filename it suggests is not specific to this project (it's based on a git sha) -- When there's only one file, it just suggests that file, but when there are multiple, it doesn't really know which to pick.
It would be better if you picked one of the existing files. A future run of the checker (when you merge again) would include a bit better advice. You could put your changes into the whitelist file, or maybe the api file (when it arrives). Or wherever a reviewer suggests.

@greg904 I love this pull request so much that I pulled it into a testing branch over here on our repo and made a couple changes. I got it working without recreating the window, in both debug and release mode. I'm going to submit a pull request from that branch and you will, of course, get full credit on the merge. :)

#5485

Ok so I should probably close this PR then. It's cool that you found a way to make it work. When I saw that it didn't work in Release mode I was mad 🤣, I thought it was going to be impossible to debug because I don't even understand how some parts of the code I wrote work.


I can't import LEED 1301

for sem 3 LEED 1301 from CELPAD is not showing

Hi @WandererProgrammer, which section?


Fix: Check that the _startTextArray variable isn't null (nil) before …

…trying to access it.
This can cause errors when for example, one team has start text and the other doesn't, in which case players on the team without start text would receive an error.

module should be rewritten and with a call to separate function that simply has an exitwith

module should be rewritten and with a call to separate function that simply has an exitwith

I can't commit to rewriting a module entirely (not even sure what that means?). Can you give an example of a call to a function that simply calls exitWith()? Does this function already exist? If not where should it live?

I am doing so for cover_map

I am doing so for cover_map

Shall we leave this PR open til after startup has been done then? I'm actually not sure how much refactoring it needs it's relatively small and not alot going on?

can merge this in the meantime until someone revamps starttext module


Regular Expression for "Accepted Filename" Not Working as Expected

It seems like the regular express for Accepted Filename is not working as expected. Using the default regex some of my games are missing and some of the extensions I add to the expression does not take.
Example
File structure
Dreamcast
|->Cannon Spike (USA)
  |>Cannon Spike (USA) (Track 1).bin
  |>Cannon Spike (USA) (Track 2).bin
  |>Cannon Spike (USA) (Track 3).bin
  |>Cannon Spike (USA).gdi
|>Illbleed (USA)
  |>Illbleed v1.002 (2001)(AIA)(NTSC)(US)[!].gdi
  |> track01.bin
  |> track02.raw
  |> track03.bin
|> Power Stoner 2 (USA)
  |> Power Stone 2 v1.000 (2000)(Capcom)(NTSC)(US)[!].gdi
  |> track01.bin
  |> track02.raw
  |> track03.bin
|>Dreamcast.backup.dat

Accepted filename regex: ^(?! (? :\. _|\.).*).*(?<!bin)(?<!iso)(?<!raw)(?<!dat)$
Resulting Games List:
Cannon Spike
Dreamcast.backup
Expected Games List:
Cannon Spike
Illbleed
Power Stone 2
I tested the regex at regex101.com and it works with those filenames.

Hello you can try to use the whitelist regex below
^(?!(?:._|.).).(?<!bin|gdi)$

Nothing shows up in the game list now

Ah soooory. I used black list regex which is wrong.
This one(whitelist) should work.
^(?!(?:\._|\.).*).*gdi$
Or this one(blacklist)
^(?!(?:\._|\.).*).*(?<!bin|iso|raw|dat)$

Sadly neither worked. I getting the game list I originally got.

How about the whitelist one? Thanks.

How about the whitelist one? Thanks.

I did and but got got the same results as the blacklist: Cannon Spike is the only game to show up and the Dreamcast.backup file doesn't come up.

Hmmm. That is weird. 🤔

Just came across something.  When I have the file structure, the Illbeed GDI file name shows up under the scraper keywords for Virtua Fighter 3tb:
File structure
Dreamcast
|->Cannon Spike (USA)
  |>Cannon Spike (USA) (Track 1).bin
  |>Cannon Spike (USA) (Track 2).bin
  |>Cannon Spike (USA) (Track 3).bin
  |>Cannon Spike (USA).gdi
|>Illbleed (USA)
  |>Illbleed v1.002 (2001)(AIA)(NTSC)(US)[!].gdi
  |> track01.bin
  |> track02.raw
  |> track03.bin
|> Power Stoner 2 (USA)
  |> Power Stone 2 v1.000 (2000)(Capcom)(NTSC)(US)[!].gdi
  |> track01.bin
  |> track02.raw
  |> track03.bin
|>Dreamcast.backup.dat
|> Virtua Fighter 3tb (USA)
  |> track01.bin
  |> track02.raw
  |> track03.bin
  |> Viruta Fighter 3tb v1.002 (1999)(Sega)(NTSC)(US)[!].gdi

Hmmm. So after you added virtual fighter. All gdi files showed up?

No. The GDI file names showed up as scraper keywords. The files do not show up in the game list.

I understand what's happening now. Probably because those gdi files has same hashes. Daijishō merge those files into a single game. Thus regex is actually working. But the same hashes make those file merged together.

Hello. I've inspected my own dreamcast collection. For example:

And the .gdi file opened by text editor is like:
21  1      0 4 2352 "Reel Fishing + Wild (USA) (Track 01).bin" 0  2   5375 0 2352 "Reel Fishing + Wild (USA) (Track 02).bin" 0  3  45000 4 2352 "Reel Fishing + Wild (USA) (Track 03).bin" 0  4 266479 0 2352 "Reel Fishing + Wild (USA) (Track 04).bin" 0  5 271946 0 2352 "Reel Fishing + Wild (USA) (Track 05).bin" 0  6 281165 0 2352 "Reel Fishing + Wild (USA) (Track 06).bin" 0  7 292119 0 2352 "Reel Fishing + Wild (USA) (Track 07).bin" 0  8 303214 0 2352 "Reel Fishing + Wild (USA) (Track 08).bin" 0  9 313998 0 2352 "Reel Fishing + Wild (USA) (Track 09).bin" 0 10 323975 0 2352 "Reel Fishing + Wild (USA) (Track 10).bin" 0 11 335050 0 2352 "Reel Fishing + Wild (USA) (Track 11).bin" 0 12 346376 0 2352 "Reel Fishing + Wild (USA) (Track 12).bin" 0 13 356515 0 2352 "Reel Fishing + Wild (USA) (Track 13).bin" 0 14 367231 0 2352 "Reel Fishing + Wild (USA) (Track 14).bin" 0 15 380789 0 2352 "Reel Fishing + Wild (USA) (Track 15).bin" 0 16 389376 0 2352 "Reel Fishing + Wild (USA) (Track 16).bin" 0 17 401058 0 2352 "Reel Fishing + Wild (USA) (Track 17).bin" 0 18 413479 0 2352 "Reel Fishing + Wild (USA) (Track 18).bin" 0 19 423898 0 2352 "Reel Fishing + Wild (USA) (Track 19).bin" 0 20 435468 0 2352 "Reel Fishing + Wild (USA) (Track 20).bin" 0 21 447906 4 2352 "Reel Fishing + Wild (USA) (Track 21).bin" 0
Which naturally generate different MD5 checksum. You can manually modify them to make it works.

Hello. I've inspected my own dreamcast collection. For example:  And the .gdi file opened by text editor is like:
 1      0 4 2352 "Reel Fishing + Wild (USA) (Track 01).bin" 0
 2   5375 0 2352 "Reel Fishing + Wild (USA) (Track 02).bin" 0
 3  45000 4 2352 "Reel Fishing + Wild (USA) (Track 03).bin" 0
 4 266479 0 2352 "Reel Fishing + Wild (USA) (Track 04).bin" 0
 5 271946 0 2352 "Reel Fishing + Wild (USA) (Track 05).bin" 0
 6 281165 0 2352 "Reel Fishing + Wild (USA) (Track 06).bin" 0
 7 292119 0 2352 "Reel Fishing + Wild (USA) (Track 07).bin" 0
 8 303214 0 2352 "Reel Fishing + Wild (USA) (Track 08).bin" 0
 9 313998 0 2352 "Reel Fishing + Wild (USA) (Track 09).bin" 0
10 323975 0 2352 "Reel Fishing + Wild (USA) (Track 10).bin" 0
11 335050 0 2352 "Reel Fishing + Wild (USA) (Track 11).bin" 0
12 346376 0 2352 "Reel Fishing + Wild (USA) (Track 12).bin" 0
13 356515 0 2352 "Reel Fishing + Wild (USA) (Track 13).bin" 0
14 367231 0 2352 "Reel Fishing + Wild (USA) (Track 14).bin" 0
15 380789 0 2352 "Reel Fishing + Wild (USA) (Track 15).bin" 0
16 389376 0 2352 "Reel Fishing + Wild (USA) (Track 16).bin" 0
17 401058 0 2352 "Reel Fishing + Wild (USA) (Track 17).bin" 0
18 413479 0 2352 "Reel Fishing + Wild (USA) (Track 18).bin" 0
19 423898 0 2352 "Reel Fishing + Wild (USA) (Track 19).bin" 0
20 435468 0 2352 "Reel Fishing + Wild (USA) (Track 20).bin" 0
21 447906 4 2352 "Reel Fishing + Wild (USA) (Track 21).bin" 0

Which naturally generate different MD5 checksum. You can manually modify them to make it works.

I have a much of dreamcast games that puts hands to edit. Sadly I won't be able to use this front-end


Klima Playgrounds Logo Image

We need a logo image based on the original Playgrounds logo but tailored for the Klima deployment

Done!


LightGBMError: b'Wrong size of feature_names'

Hello there, when i run my dataset with lgb, following errors occur:
_Data: X_train: (314954, 76), X_test: (78739, 76)
Training on: (314954, 76)
Traceback (most recent call last):
File "", line 80, in
model = lgb.train(params, train_lgb, num_boost_round=ROUNDS)
File "C:\Users\User\Anaconda3\lib\site-packages\lightgbm\engine.py", line 213, in train
booster._load_model_from_string(booster._save_model_to_string())
File "C:\Users\User\Anaconda3\lib\site-packages\lightgbm\basic.py", line 1554, in _load_model_from_string
ctypes.byref(self.handle)))
File "C:\Users\User\Anaconda3\lib\site-packages\lightgbm\basic.py", line 48, in _safe_call
raise LightGBMError(_LIB.LGBM_GetLastError())
LightGBMError: b'Wrong size of feature_names'_
Does somebody know how to deal with this issues? thanks.

ping @wxchan @StrikerRUS

@ahbon123 Please provide reproducible example or at least the params and the head of train_lgb.

@ahbon123 what's the type of X_train and X_test? and what's the value of ROUNDS?

Thanks for your reply @StrikerRUS @wxchan @guolinke. The bugs come from the features' titles. When I delete the row of titles, there is no more errors.


Support for multicast messages

According to the FCM HTTP API reference, it is possible to send multicast messages. You can send up to 1000 push notifications in one request by specifying the registration ids inside an array with the key "registration_ids".
When I try to add more than one device to a message I get the following error:
when sending to single devices only one recipient is allowed
Could we make it possible to add multiple recipents to a message and if there are more than recipient, the registration tokens are put inside a "registration_ids" array?
Would really like it as we are sending multiple thousand messages to individual recipients. We can´t use topics because we have some internal code that decides what message gets sent to whom which was too complex to do with topics and conditions in FCM.

Added a Pull Request #7

Thanks for your pull request. Merged, tagged and composer ready.


[Other] Change Phone Info 📲

I want to change the ANDROID_ID which is at: android.provider.Settings.Secure
Can I do it in BuildProxy.kt or do I have to create a new file + specific settings?
Could you give an example of how I can do it?
I am taking the BuildProxy.kt as an example to do this, but it is not working.
PS. Sorry for this, I am a beginner learning Android now.

U might wanna try APPENV. hope this may can help u

U might wanna try APPENV. hope this may can help u

Please, could you explain better?

It's a xposed module, allows u to simulate ur phone information for each app.

It's a xposed module, allows u to simulate ur phone information for each app.

Thanks bro 🖒


Failed to configure policies for 'customized_snat'

Module version 1.0.4 -

When applying/modifying NAT on single spoke g/w (i.e. non HA) the following error is seen (see attached screenshot below)

Modifying module local variable in variables.tf  addresses the issue/error:

FROM:
locals {
is_ha = var.spoke_gw_object.ha_gw_size != null
}
TO:
locals {
is_ha = var.spoke_gw_object.ha_gw_size != ""
}

Fix has been merged. Needs testing and validation before releasing a new version and closing the issue.

Adding only this line resolved the above error:
locals {
is_ha = var.spoke_gw_object.ha_gw_size != ""
}
The following resulted in same error:
is_ha = var.spoke_gw_object.ha_gw_size != null || var.spoke_gw_object.ha_gw_size != ""
or
is_ha = var.spoke_gw_object.ha_gw_size != "" || var.spoke_gw_object.ha_gw_size != null

Addressed in 1.0.6


Regeneration is also triggered when moving main task date

Hello again, yesterday I moved a main task with @Regen_all tag from one day to another after completing a few (but not all) subtasks. To my surprise, the completed subtasks were regenerated even though I didn't complete the recurring main task.
Is this by design? I would expect that the subtasks are only regenerated when I complete (= tick off) the main task. Or is it a problem to distinguish if a recurring task as just been moved or completed?

Hi, this is indeed not the intended behavior. In any case, for the next release the current implementation of this regeneration feature will likely be removed, since Todoist now natively supports this.
Even so, it's still not working exactly as I would like. So perhaps in the future I will try to supplement the workings with Autodoist, but for now I will close this issue.


Unknown model (mobilenetv3_100)

@rwightman
thanks.
However, I'm trying to load the model in kaggle kernel, but faced following error
!pip install timm
import timm
m = timm.create_model('mobilenetv3_100', pretrained=True, num_classes=3)
ERROR
RuntimeError: Unknown model (mobilenetv3_100)

Model name changed, readme is out of date, look at the code for the current model variants or use list_models() to find them


Build failure on OSX

System information:

OSX: 12.5
Chip: Apple M1 Max
Apple clang version 13.1.6 (clang-13<IP_ADDRESS>.5)
Target: arm64-apple-darwin21.6.0
Thread model: posix
Python 3.10.2

$ pip3 install nmslib
Results in clang: error: the clang compiler does not support '-march=native'

...
Installing collected packages: nmslib
Running setup.py install for nmslib ... error
error: subprocess-exited-with-error
× Running setup.py install for nmslib did not run successfully.
│ exit code: 1
╰─> [20 lines of output]
Dependence list: ['pybind11<2.6.2', 'psutil', "numpy>=1.10.0,<1.17 ; python_version=='2.7'", "numpy>=1.10.0 ; python_version>='3.5'"]
/Users/cwelton/.pyenv/versions/3.10.2/lib/python3.10/site-packages/setuptools/dist.py:717: UserWarning: Usage of dash-separated 'description-file' will not be supported in future versions. Please use the underscore name 'description_file' instead
warnings.warn(
running install
running build
running build_ext
clang -Wno-unused-result -Wsign-compare -Wunreachable-code -DNDEBUG -g -fwrapv -O3 -Wall -I/Library/Developer/CommandLineTools/SDKs/MacOSX12.1.sdk/usr/include -I/Library/Developer/CommandLineTools/SDKs/MacOSX12.1.sdk/usr/include -I/Users/cwelton/.pyenv/versions/3.10.2/include/python3.10 -c /var/folders/zm/wl2cwllx1y3gv5m_5bw6ngy80000gn/T/tmpeqcxm6js.cpp -o var/folders/zm/wl2cwllx1y3gv5m_5bw6ngy80000gn/T/tmpeqcxm6js.o -std=c++14
clang -Wno-unused-result -Wsign-compare -Wunreachable-code -DNDEBUG -g -fwrapv -O3 -Wall -I/Library/Developer/CommandLineTools/SDKs/MacOSX12.1.sdk/usr/include -I/Library/Developer/CommandLineTools/SDKs/MacOSX12.1.sdk/usr/include -I/Users/cwelton/.pyenv/versions/3.10.2/include/python3.10 -c /var/folders/zm/wl2cwllx1y3gv5m_5bw6ngy80000gn/T/tmpzf2wt8g1.cpp -o var/folders/zm/wl2cwllx1y3gv5m_5bw6ngy80000gn/T/tmpzf2wt8g1.o -fvisibility=hidden
Extra compilation arguments: ['-O3', '-march=native', '-stdlib=libc++', '-mmacosx-version-min=10.7', '-DVERSION_INFO="2.1.1"', '-std=c++14', '-fvisibility=hidden']
building 'nmslib' extension
creating build
creating build/temp.macosx-12.1-arm64-3.10
creating build/temp.macosx-12.1-arm64-3.10/similarity_search
creating build/temp.macosx-12.1-arm64-3.10/similarity_search/src
creating build/temp.macosx-12.1-arm64-3.10/similarity_search/src/method
creating build/temp.macosx-12.1-arm64-3.10/similarity_search/src/space
creating build/temp.macosx-12.1-arm64-3.10/tensorflow
clang -Wno-unused-result -Wsign-compare -Wunreachable-code -DNDEBUG -g -fwrapv -O3 -Wall -I/Library/Developer/CommandLineTools/SDKs/MacOSX12.1.sdk/usr/include -I/Library/Developer/CommandLineTools/SDKs/MacOSX12.1.sdk/usr/include -I./similarity_search/include -Itensorflow -I/Users/cwelton/.pyenv/versions/3.10.2/lib/python3.10/site-packages/pybind11/include -I/Users/cwelton/.pyenv/versions/3.10.2/lib/python3.10/site-packages/pybind11/include -I/Users/cwelton/.pyenv/versions/3.10.2/lib/python3.10/site-packages/pybind11/include -I/Users/cwelton/.pyenv/versions/3.10.2/lib/python3.10/site-packages/pybind11/include -I/Users/cwelton/.pyenv/versions/3.10.2/lib/python3.10/site-packages/numpy/core/include -I/Users/cwelton/.pyenv/versions/3.10.2/include/python3.10 -c ./similarity_search/src/distcomp_bregman.cc -o build/temp.macosx-12.1-arm64-3.10/./similarity_search/src/distcomp_bregman.o -O3 -march=native -stdlib=libc++ -mmacosx-version-min=10.7 -DVERSION_INFO="2.1.1" -std=c++14 -fvisibility=hidden
clang: error: the clang compiler does not support '-march=native'
error: command '/usr/bin/clang' failed with exit code 1
[end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
error: legacy-install-failure
× Encountered error while trying to install package.
╰─> nmslib

This looks like a dup of #476, I'll add some comments there.

Hi @cwelton it should be fixed in the master, but it's taking me a while to produce a release due to issues with CI.
Could you try installing directly from github, this would be a nice test to see if the fix is actually working. Many thanks and you could use something like:
pip install git+https://github.com/nmslib/nmslib.git

@searchivarius Tried to install directly from GH, but got this error.
$ pip install git+https://github.com/nmslib/nmslib.git
Collecting git+https://github.com/nmslib/nmslib.git
  Cloning https://github.com/nmslib/nmslib.git to /private/var/folders/ff/xz3x_2sd5rlcr9fy627mqn6w0000gn/T/pip-req-build-5tl92hfx
  Running command git clone --filter=blob:none --quiet https://github.com/nmslib/nmslib.git /private/var/folders/ff/xz3x_2sd5rlcr9fy627mqn6w0000gn/T/pip-req-build-5tl92hfx
  Resolved https://github.com/nmslib/nmslib.git to commit ade4bcdc9dd3719990de2503871450b8a62df4a5
ERROR: git+https://github.com/nmslib/nmslib.git does not appear to be a Python project: neither 'setup.py' nor 'pyproject.toml' found.

@atwoodjw aaargh, sorry, setup.py is currently not in the root folder, but in the python_bindings directory. Something to fix in the future. You can clone, cd to python_bindings and do python setup.py


Feature Request/Improvement: Add 'usage:' to all scripts that don't already have it

Support incorrect usages in regex and give feedback back to user

I'm taking care of this, also fixing the regex re: trailing characters (e.g. !catch calling !cat).

Closing this as !help should take care of it. Also, the move to pybot removed regexs

On second thought, I think it might be necessary. I like @MaxwellBo's idea in #312 to just print back the doc, we should use that elsewhere

Can probably add it to on_command and add a UsageSyntaxException to automate it :^)


After victims login the password and username name don't show it give me link and I don't how to the the details  please I need help

Before you submit this bug report check that you have ran the required setup correctly. Follow the steps on the wiki.
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

Leave solution here: https://github.com/UndeadSec/SocialFish/issues/278#issuecomment-840444976


Rewrite should probably be a trait

Just ran into this again. We can probably use iteration instead of materializing substitutions while searching. This could save some time, but would also allow more flexible limit checking


Should with_prefix be used for Unit type enums?

I have a special use case where I use an Enum as a way to define fields of a map which is dynamically build. Since serde can represent the value MyEnum::Field as "Field" I was also looking for a way to use a prefix for that field.
Right now this examples doesn't compile
serde_with::with_prefix!(my_enum_prefix "myEnum.");

#[derive(Debug, Serialize, Deserialize)]
enum MyEnum {
    #[serde(with = "my_enum_prefix")]
    Field,
    #[serde(with = "my_enum_prefix")]
    Field2
}

Compile error:
error[E0061]: this function takes 2 arguments but 1 argument was supplied
   --> src/lib.rs:157:40
    |
9   | serde_with::with_prefix!(adview_prefix "adView.");
    | -------------------------------------------------- defined here
...
157 |     #[derive(Hash, Copy, Clone, Debug, Serialize, Deserialize, Eq, PartialEq)]
    |                                        ^^^^^^^^^
    |                                        |
    |                                        supplied 1 argument
    |                                        expected 2 arguments
    |
    = note: this error originates in a derive macro (in Nightly builds, run with -Z macro-backtrace for more info)

I also tried to add it to the enum of fields:
#[derive(Debug, Serialize, Deserialize)]
#[serde(untagged)]
pub enum Field {
        AdView(#[serde(with = "...")] AdView),
....
}

However this results to the prefix not being accounted for.

The with_prefix! macro is meant to be used to add prefixes to a struct/enum, if you cannot fully control the Serialize implementation or if you need different prefixes. Something like this:
struct SomeStruct {
	// ...
	#[serde(with = "my_enum_prefix")]
	my_enum: MyEnum,
	// ..
}

I don't think with_prefix! can really be used to rename the fields of a struct or unit variants without such a wrapping struct/enum. The field name / unit variant already gets emitted before the with part runs, so it cannot change those values.
The solution right now is to use #[serde(rename = "myEnum....")] on every enum variant.
Alternatively, it should be possible to provide a proc-macro which performs this step. It could be used like:
#[serde_with::prefix_all("my_enum")]
enum MyEnum {
	// ...
}

Ideally it would work on enum variants and struct fields.

Thanks for the feedback and indeed a proc-macro could work.
I am ok with what I can use right now, but I thought I would ask anyway


[Doc]  show alter statement does not support "show alter cluster"

What type of PR is this：

[ ] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Which issues of this PR fixes ：

Fixes #
Problem Summary(Required) ：

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] I have added user document for my new feature or new function

starrocks_be_unittest succeeded.

run starrocks_admit_test

@mergify backport 2.4

@mergify backport 2.3

@mergify backport branch-2.4

@mergify backport branch-2.3


polyfill Worker in chrome runtime

references https://github.com/penumbra-zone/web/issues/1795
this PR creates a package implementing a polyfill of the DOM Worker interface for chrome extension workers, and applies that polyfill to consumed packages from penumbra-zone.
pending https://github.com/penumbra-zone/web/pull/1769

managed to discover some lies within the chrome runtime api about the offscreen lifecycle, so i have to work around that, but this is nearly ready for review.

this is pretty close, but i had other tasks today and now i'm out of time. tl;dr:
a transaction build can take place successfully, but it seems like sessions live a bit too long.
workers should be redesigned to terminate themselves when possible.
be aware that when the createDocument method returns, offscreen is not ready.
this does not yet support use from multiple scripts - different global contexts will track offscreen use independently, and kill the shared document early.
it might be good to check if terminating the offscreen document actually kills the web workers, or if it's cleaned up too fast to issue termination commands.
this tool when complete would be incredibly useful to extension developers in general, so i'm likely to publish this polyfill independently to NPM.

chrome-offscreen-worker package in this PR will be replaced with https://github.com/turbocrime/chrome-offscreen-worker/tree/main/package

advocating to close the intermediate polyfill step in favor of proceeding directly with the migration.


Documentation: Does it stop bleeding through of CSS?

Please add this to the README if it is the case or not.

Sorry, while the README states that the selectors are not polyfilled I suppose it should also state that the CSS scoping is also not polyfilled. Thanks for bringing this up!


Texture import path multiple error

Hi i did everythig as explained, but i get this error after importing

don't know why. And the plane is all white.
Those textures paths in the errors are crazy. "KITTYHAWK/TOBURN"... ecc...

I'm getting this as well, with the Asobo F/A-18.

Clearly it's imposing more directories where it shouldn't be, or perhaps I'm doing the process wrong. I selected FA18E_LOD00.gltf, and I can see that it contains these references:
    "images": [
        {
            "uri": "ASOBO_FA18E_SUPERHORNET\\MODEL\\FA18E_AIRFRAME_FRONTGEAR_ALBD.PNG.DDS",
            "extras": "ASOBO_image_converted_meta"
        },

These references to SUPERHORNET are literally the only such references in the entire Official directory and subdirectories. I made a copy of the GLTF file, erased all references to ASOBO_FA18E_SUPERHORNET\\MODEL\\, and imported that file. It errored out on some misc textures like frost, but it actually worked for the base livery.


resolution for issue #8

Making install_requires to read requirements.txt. This makes dependencies more explicit and fixes an issue of faulty build of quicksectx on Apple M1 ARM silicone


Intel compiler error with 9.1.x branch

When comping with the intel compiler we got this error.
Http2SessionAccept.o -MD -MP -MF $depbase.Tpo -c -o Http2SessionAccept.o ../../../../../../_scm/trafficserver9.1/proxy/http2/Http2SessionAccept.cc &&\ mv -f $depbase.Tpo $depbase.Po ../../../../../../_scm/trafficserver9.1/proxy/http2/HPACK.cc(102): error: expression must have a constant value   constexpr HpackHeaderField STATIC_TABLE[] = {{"", ""},                                               ^ ../../../../../../_scm/trafficserver9.1/proxy/http2/HPACK.cc(102): note: attempt to access run-time storage   constexpr HpackHeaderField STATIC_TABLE[] = {{"", ""},
@shinrich requested I report this issue here.

@dragon512 do you know what branch or commit was being compiled when this error occurred?

it should be 9.1

Jason do you maybe just need to download icc from the "main" branch instead of the "cursed" branch?
https://godbolt.org/z/shG9rx3jf

@dragon512 Do you know if this is still an issue?

Jason car reopen if there's still anything to do here.


Spelling PagingAndSortingRepository

@DmitrySandalov Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.

@DmitrySandalov Thank you for signing the Contributor License Agreement!


fix: failing to parse response from npm dist-tag add

see: https://github.com/npm/npme-installer/issues/153

LGTM :+1: but what is it about the payload that causes json parsing to fail?

Coverage remained the same at 100.0% when pulling e58ffe162b7ace5137d4e47772ed31c32afb5a4a on dist-tag-fix into 583f5f4f14720695cf0b40ce2f7410867d803de5 on master.

strict mode for JSON body parsing requires [] or {} this breaks our version lookup, which returns "46.10.0".


[BUG] All relayer addresses are displaying the exact same address

Overview
I am not entirely sure if this is a BUG or not but it seems odd that the relayer selection component is displaying the same address for all relayers even though each of those relayers have different keys. You can replicate this by reviewing the deployment preview or checking out the branch and running the dApp locally from this PR.
Screenshot

Task Checklist

[ ] Investigate why all relayers are displaying the same address

I guess because all these relayers are using the same private key, you can check by the route /api/v1/info and check the beneficiary values, they're the same right now.


Fix Member Authentication Edgecase

There exists a scenario in which:

You've successfully authenticated to the CMS
You haven't accessed the CMS for more than 3 days
You don't have a Default Admin user configured in your environment

In this scenario, trying to re-authenticate via the provided CMS dialog will result in a Fatal Error as of the tip of the SilverStripe 3 branch. This PR shifts the Default Admin authentication attempt inside a conditional to avoid comparing a null email address to a null default admin username.
This was discussed in #6361.
Test coverage included. 👍

I believe the issue has be fixed by #7012
However, this has tests, and I like tests. so I'll update this PR just to have the test in it :)


Setting enabled to false causes transparency to stack

Problem description
When setting enabled to false on a Composite containing a TextView, the TextView is grayed out. Setting enabled to false on the TextView as well causes the disabled visualization to stack, making it "even more disabled".
Expected behavior
Setting enabled to false state should be consistent no matter how often it is applied in the layout hierarchy. The initial disabled state is also rather faint making it not directly obvious that the widget is disabled.
Environment

Tabris.js version: 2.0.0
Device: iPad Pro 9.5
OS: 10.3.3

Code snippet
Both TextViews should have the same visual disabled appearance.
const {TextView, Composite, ui} = require('tabris');

let composite = new Composite({
  left: 0, right: 0, top: 0, bottom: 0,
  enabled: false
}).appendTo(ui.contentView);

new TextView({
  left: 16, top: 16, right: 16,
  text: 'TextView',
}).appendTo(composite);

new TextView({
  left: 16, top: 'prev() 16', right: 16,
  text: 'TextView',
  enabled: false
}).appendTo(composite);

I think that in order to fix this correctly we would have implement our "greying out" mechanism. I did not found a way to prevent children from multiplying alpha with their parent's alpha.


Fix issue with parquet partitioned reads

This fixes #718
It also fixes a few other things I found while in the code.
It acquires the GPU Semaphore in cases where we are returning a batch, even if it is just row counts.
It updates the tests to use the new small file config.  I noticed it when I checked if my new test would fail without the fix in place, and it failed all 4 cases instead of just half of them that I thought it should.

build

python udf window tests are failing here too now.  Not sure how they passed for the original PR. Because this is a P1 I am going to merge this in as is, and then we can decide how to fix the test separately.


h264dec: check read beyond boundary for every bit

We need check read beyond boundary. To make sure we can detect error bitstream as early as possible.
If we do not check this, maybe we will encounter a serious error.
#495 is good example

Hi @chivakker @YuJiankang @wudping
Please help to review this.

Hi @chivakker
This patch will check every read operation to make sure it not read beyond boundary.
Return a reasonable value is not enough for some case.
https://github.com/01org/libyami/pull/514 is good example.
Here is original code from NalReader::readUe
for (uint32_t b = 0; !b; leadingZeroBits++) {
  b = read(1);

We will return 0 if read(1) read beyond boundary.But this will make this loop trap to a infinite loop. This why we need change this code to this
https://github.com/01org/libyami/pull/514/files#diff-7409028df9bce563cd348eb36025945fR67
Same check need apply to codec parser too.
This why I submit this patch.
However, for codec parser, we’d better not add “if else” branch for every read. It is will be too many places. Therefore, I use a macro to do all return check.

I don't want to start a discussion between inline and macros in C++.  Let's keep the macros then.  The only comment I have then is that it would be better to make the change across the board to avoid the future renaming.

inline function is not a replacement for macro. The vp8 parser use similar macro too.You can refer to https://github.com/01org/libyami/blob/apache/codecparsers/vp8_parser.cpp#L54

@xuguangxin the vp8 parser example is also a good data point that it is fine to do it that way.  Pardon the confusion.

@chivakker @YuJiankang
Please +1 for me. if you think it's ok

+1

Can we hold on merging this patch until we have the other codecs fixed?

Hi @chivakker
Why? This will not have side effects to other codec.

verify + 1

merged as 2844dcfb5c1c80f6c78d50ad8aa298fc849cb3ee


MOSIP logo trimed in VC card

Describe the bug
MOSIP logo got trimed in both VC's preview in home page and VC details page
To Reproduce

Open app and head to home page
click on add ID and download VC
Go back to home

Expected behavior
The mosip logo should placed fully and properly aligned with the structure
Current behavior
MOSIP logo got trimed in both VC's preview in home page and VC details page
Screenshots

Smartphone (please complete the following information):
Device: android
MOSIP Version: 121
MOSIP server: qa-121.mosip.net

Verified this issue in qa-1201-b2 environment, the issue is fixed, we are getting full logo of MOSIP in VC card, I am attaching the screenshot and the device details below for reference. Hence closing this bug.
Screenshots: -

Tested in: -
Device: Redmi 7A
Android Version: 10
BLE version: 4.2
Inji app link: https://github.com/mosip/inji/actions/runs/4447486079
Mimoto version: <IP_ADDRESS>
MOSIP Version: qa-1201-b2.mosip.net