HADOOP-16768. SnappyCompressor test cases wrongly assume that the compressed data is always smaller than the input data.

Description of PR
It is a clean cherry pick from commit 328eae9a146b2dd9857a17a0db6fcddb1de23a0d from trunk.
However, we manually added dependency for assertj. assertj dependency was added as part of a not small patch in HADOOP-16287 and HDFS-12665, and subsequently modified again in HADOOP-16253. Too much overhead in bringing in these PRs and thus we decided to add the dependency manually ourselves.
How was this patch tested?
mvn test -Dtest=hadoop.io.compress.TestCompressorDecompressor
mvn test -Dtest=hadoop.io.compress.snappy.TestSnappyCompressorDecompressor

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
8m 25s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 2 new or modified test files.

_ branch-2.10 Compile Tests _

+0 :ok:
mvndep
4m  7s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
14m  4s

branch-2.10 passed

+1 :green_heart:
compile
13m 17s

branch-2.10 passed with JDK Azul Systems, Inc.-1.7.0_262-b10

+1 :green_heart:
compile
11m 15s

branch-2.10 passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~18.04-b07

+1 :green_heart:
checkstyle
2m 30s

branch-2.10 passed

+1 :green_heart:
mvnsite
2m 43s

branch-2.10 passed

+1 :green_heart:
javadoc
2m 46s

branch-2.10 passed with JDK Azul Systems, Inc.-1.7.0_262-b10

+1 :green_heart:
javadoc
2m 26s

branch-2.10 passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~18.04-b07

+0 :ok:
spotbugs
1m 25s

branch/hadoop-project no spotbugs output file (spotbugsXml.xml)

-1 :x:
spotbugs
2m 24s
/branch-spotbugs-hadoop-common-project_hadoop-common-warnings.html
hadoop-common-project/hadoop-common in branch-2.10 has 2 extant spotbugs warnings.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 31s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
1m 10s

the patch passed

-1 :x:
compile
1m 24s
/patch-compile-root-jdkAzulSystems,Inc.-1.7.0_262-b10.txt
root in the patch failed with JDK Azul Systems, Inc.-1.7.0_262-b10.

-1 :x:
javac
1m 24s
/patch-compile-root-jdkAzulSystems,Inc.-1.7.0_262-b10.txt
root in the patch failed with JDK Azul Systems, Inc.-1.7.0_262-b10.

+1 :green_heart:
compile
10m 41s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~18.04-b07

+1 :green_heart:
javac
10m 41s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
2m 27s

the patch passed

+1 :green_heart:
mvnsite
2m 39s

the patch passed

+1 :green_heart:
xml
0m  2s

The patch has no ill-formed XML file.

+1 :green_heart:
javadoc
2m 40s

the patch passed with JDK Azul Systems, Inc.-1.7.0_262-b10

+1 :green_heart:
javadoc
2m 26s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~18.04-b07

+0 :ok:
spotbugs
0m 56s

hadoop-project has no data from spotbugs

_ Other Tests _

+1 :green_heart:
unit
0m 55s

hadoop-project in the patch passed.

-1 :x:
unit
9m 11s
/patch-unit-hadoop-common-project_hadoop-common.txt
hadoop-common in the patch passed.

+1 :green_heart:
asflicense
1m 17s

The patch does not generate ASF License warnings.

111m 59s

Reason
Tests

Failed junit tests
hadoop.fs.sftp.TestSFTPFileSystem

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4208/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/4208

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient codespell xml spotbugs checkstyle

uname
Linux 69947d45c445 4.15.0-156-generic #163-Ubuntu SMP Thu Aug 19 23:31:58 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
branch-2.10 / 647481a3f9b28b25dfe0f5f2400f7a9c6cd22f18

Default Java
Private Build-1.8.0_312-8u312-b07-0ubuntu1~18.04-b07

Multi-JDK versions
/usr/lib/jvm/zulu-7-amd64:Azul Systems, Inc.-1.7.0_262-b10 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_312-8u312-b07-0ubuntu1~18.04-b07

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4208/1/testReport/

Max. process+thread count
1377 (vs. ulimit of 5500)

modules
C: hadoop-project hadoop-common-project/hadoop-common U: .

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4208/1/console

versions
git=2.17.1 maven=3.6.0 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

assertj-core 3.x requires java 8 and thus we can not compile it with jdk 1.7 (java 7) for branch-2.10. Also tried assert-core at 2.9.1 (the latest 2.x release) and it did not compile neither. So, we decided not to use assertj and replaced with AssertTrue/AssertEquals().

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 39s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 2 new or modified test files.

_ branch-2.10 Compile Tests _

+0 :ok:
mvndep
4m  7s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
14m 11s

branch-2.10 passed

+1 :green_heart:
compile
13m 25s

branch-2.10 passed with JDK Azul Systems, Inc.-1.7.0_262-b10

+1 :green_heart:
compile
11m 13s

branch-2.10 passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~18.04-b07

+1 :green_heart:
checkstyle
2m 28s

branch-2.10 passed

+1 :green_heart:
mvnsite
2m 42s

branch-2.10 passed

+1 :green_heart:
javadoc
2m 42s

branch-2.10 passed with JDK Azul Systems, Inc.-1.7.0_262-b10

+1 :green_heart:
javadoc
2m 26s

branch-2.10 passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~18.04-b07

+0 :ok:
spotbugs
1m 22s

branch/hadoop-project no spotbugs output file (spotbugsXml.xml)

-1 :x:
spotbugs
2m 24s
/branch-spotbugs-hadoop-common-project_hadoop-common-warnings.html
hadoop-common-project/hadoop-common in branch-2.10 has 2 extant spotbugs warnings.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 28s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
1m 11s

the patch passed

+1 :green_heart:
compile
12m 26s

the patch passed with JDK Azul Systems, Inc.-1.7.0_262-b10

+1 :green_heart:
javac
12m 26s

the patch passed

+1 :green_heart:
compile
11m 16s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~18.04-b07

+1 :green_heart:
javac
11m 16s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
2m 25s

the patch passed

+1 :green_heart:
mvnsite
2m 40s

the patch passed

+1 :green_heart:
xml
0m  3s

The patch has no ill-formed XML file.

+1 :green_heart:
javadoc
2m 39s

the patch passed with JDK Azul Systems, Inc.-1.7.0_262-b10

+1 :green_heart:
javadoc
2m 25s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~18.04-b07

+0 :ok:
spotbugs
0m 57s

hadoop-project has no data from spotbugs

_ Other Tests _

+1 :green_heart:
unit
0m 55s

hadoop-project in the patch passed.

-1 :x:
unit
9m 11s
/patch-unit-hadoop-common-project_hadoop-common.txt
hadoop-common in the patch passed.

+1 :green_heart:
asflicense
1m 16s

The patch does not generate ASF License warnings.

115m 56s

Reason
Tests

Failed junit tests
hadoop.fs.sftp.TestSFTPFileSystem

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4208/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/4208

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient codespell xml spotbugs checkstyle

uname
Linux b28ed3a9ec3a 4.15.0-156-generic #163-Ubuntu SMP Thu Aug 19 23:31:58 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
branch-2.10 / 23d7c72915fe7c5dff5178ab5d47366e4b604315

Default Java
Private Build-1.8.0_312-8u312-b07-0ubuntu1~18.04-b07

Multi-JDK versions
/usr/lib/jvm/zulu-7-amd64:Azul Systems, Inc.-1.7.0_262-b10 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_312-8u312-b07-0ubuntu1~18.04-b07

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4208/2/testReport/

Max. process+thread count
1377 (vs. ulimit of 5500)

modules
C: hadoop-project hadoop-common-project/hadoop-common U: .

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4208/2/console

versions
git=2.17.1 maven=3.6.0 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 40s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 2 new or modified test files.

_ branch-2.10 Compile Tests _

+0 :ok:
mvndep
3m 52s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
14m 12s

branch-2.10 passed

+1 :green_heart:
compile
13m 36s

branch-2.10 passed with JDK Azul Systems, Inc.-1.7.0_262-b10

+1 :green_heart:
compile
11m 20s

branch-2.10 passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~18.04-b07

+1 :green_heart:
checkstyle
2m 29s

branch-2.10 passed

+1 :green_heart:
mvnsite
2m 45s

branch-2.10 passed

+1 :green_heart:
javadoc
2m 41s

branch-2.10 passed with JDK Azul Systems, Inc.-1.7.0_262-b10

+1 :green_heart:
javadoc
2m 22s

branch-2.10 passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~18.04-b07

+0 :ok:
spotbugs
1m 22s

branch/hadoop-project no spotbugs output file (spotbugsXml.xml)

-1 :x:
spotbugs
2m 28s
/branch-spotbugs-hadoop-common-project_hadoop-common-warnings.html
hadoop-common-project/hadoop-common in branch-2.10 has 2 extant spotbugs warnings.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 27s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
1m 13s

the patch passed

+1 :green_heart:
compile
14m 12s

the patch passed with JDK Azul Systems, Inc.-1.7.0_262-b10

+1 :green_heart:
javac
14m 12s

the patch passed

+1 :green_heart:
compile
12m  7s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~18.04-b07

+1 :green_heart:
javac
12m  7s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
2m 27s

the patch passed

+1 :green_heart:
mvnsite
2m 40s

the patch passed

+1 :green_heart:
xml
0m  2s

The patch has no ill-formed XML file.

+1 :green_heart:
javadoc
2m 40s

the patch passed with JDK Azul Systems, Inc.-1.7.0_262-b10

+1 :green_heart:
javadoc
2m 26s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~18.04-b07

+0 :ok:
spotbugs
0m 57s

hadoop-project has no data from spotbugs

_ Other Tests _

+1 :green_heart:
unit
0m 56s

hadoop-project in the patch passed.

-1 :x:
unit
9m  9s
/patch-unit-hadoop-common-project_hadoop-common.txt
hadoop-common in the patch passed.

+1 :green_heart:
asflicense
1m 17s

The patch does not generate ASF License warnings.

118m 45s

Reason
Tests

Failed junit tests
hadoop.fs.sftp.TestSFTPFileSystem

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4208/3/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/4208

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient codespell xml spotbugs checkstyle

uname
Linux 5ab0817466bc 4.15.0-156-generic #163-Ubuntu SMP Thu Aug 19 23:31:58 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
branch-2.10 / 9cc1d785b7548a9cdc8c17fa8bccf138fa749fc9

Default Java
Private Build-1.8.0_312-8u312-b07-0ubuntu1~18.04-b07

Multi-JDK versions
/usr/lib/jvm/zulu-7-amd64:Azul Systems, Inc.-1.7.0_262-b10 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_312-8u312-b07-0ubuntu1~18.04-b07

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4208/3/testReport/

Max. process+thread count
1378 (vs. ulimit of 5500)

modules
C: hadoop-project hadoop-common-project/hadoop-common U: .

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4208/3/console

versions
git=2.17.1 maven=3.6.0 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

Yetus failures unrelated. thanks for the backport @xinglin! Committing this.


'referrals' parameter does not work properly

Running latest version of puppet on Oracle Linux 7.2.
class { 'openldap':
    notify => Service['autofs'],
    referrals => false,
    tls_reqcert => 'never',
    uri => ['ldap://cr-lc-sca-01.example.com/', 'ldap://cr-lc-sca-02.example.com/'],
    base => 'dc=example,dc=com',
    tls_cacertdir => '/etc/openldap/cacerts'
}

produces
# !!! Managed by Puppet !!!

URI                             ldap://cr-lc-sca-01.example.com/ ldap://cr-lc-sca-02.example.com/
BASE                            dc=example,dc=com
TLS_CACERTDIR                   /etc/openldap/cacerts
TLS_REQCERT                     never

Setting "referrals => true" produces
# !!! Managed by Puppet !!!

BASE                            dc=example,dc=com
REFERRALS                       on
TLS_CACERTDIR                   /etc/openldap/cacerts
TLS_REQCERT                     never

Since the default behavior is "on" there is no way off turning referrals "off" with this module.

Not a ruby expert, but I think in ldap.conf.erb:
<% if @referrals -%>

should be something like:
<% if defined?(@referrals) -%>

Good catch. The pattern I've used elsewhere in other templates is:
<% unless @referrals.nil? -%>

That means it only processes the block if @referrals is not undef rather than testing the "truthiness" of it.

I found some more instances of the same bug in that template so I've fixed those up as well, (I guess even fewer people use this with GSSAPI). Version 1.4.1 should be up on the forge with this fixed.
Thanks for the bug report!


Cannot get it to work on Mavericks

On Mavericks it crashes with:
mas signin<EMAIL_ADDRESS>"**********"
dyld: Library not loaded: /System/Library/PrivateFrameworks/StoreFoundation.framework/Versions/A/StoreFoundation
Referenced from: /Users/frasc/./mas
Reason: image not found
Trace/BPT trap: 5
Is it possible to get it to work on older OS versions ?
Thanks a lot, that's an awesome idea!

I don't have the time or resources to reverse engineer older versions of the App Store frameworks so older versions won't be supported.
—A

On 25 Aug 2016, at 02:34, Frederic Roussel<EMAIL_ADDRESS>wrote:
On Mavericks it crashes with:
mas signin<EMAIL_ADDRESS>"**********"
dyld: Library not loaded: /System/Library/PrivateFrameworks/StoreFoundation.framework/Versions/A/StoreFoundation
Referenced from: /Users/frasc/./mas
Reason: image not found
Trace/BPT trap: 5
Is it possible to get it to work on older OS versions ?
Thanks a lot, that's an awesome idea!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.


Simple algorithm to detect ambiguous situations

It seems that the character đ may be transliterated in at least three different ways:

dj in Serbian according to https://en.wikipedia.org/wiki/D_with_stroke and https://github.com/django/django/blob/master/django/contrib/admin/static/admin/js/urlify.js
gj in Macedonian according to https://en.wikipedia.org/wiki/D_with_stroke
d in Vietnamese (according to https://github.com/simov/slugify/issues/49).

Perhaps the algorithm for this (and other characters that can be transliterated in multiple ways) might be:

If the input string contains no ambiguous characters (such as đ), use the current algorithm.
Otherwise, we need to figure out the language, Naive first-pass implementation will be:

If the input string consists entirely of characters that are valid in one of the languages but not any of the others, use that language's transliteration.
Otherwise, take the list of possible languages (that is, languages for which all characters in the string are valid), and select the language with the most native speakers. (I believe in this case, the ordering would be Vietnamese, Serbian, Macedonian.) That will at least hopefully tend to guess correctly.
If there are no languages that can contain all the characters, use the transliteration from the language with the most native speakers (in this case, Vietnamese).

This can be iterated on to improve it, but something simple like this is probably better than what we have now (which is "we have Serbian, so that's what we're using"). And we probably don't need to go full machine-learning model on this.

I tried this and it's more complicated and less reliable than this suggests. I think it's best for now for the user to simply provide an override replacement string for the language they care about.

Yep, I have a locale option in the works, but it's not officially documented yet.
You can see it in the main file that I have:
var locales = JSON.parse('{"vi":{"Đ":"D","đ":"d"}}')

The idea was that the most efficient way in terms of bundle size was to have all possible characters in the main charmap, as they were added over time without regard to a specific locale, and then override only the necessary characters in locale specific JSON. The reason why is because many locales can have overlaps in the way they translate certain character, which is good.

Oh, wait, I just commented in your repo .. I was redirected from mine .. anyway

Yeah, I implemented the same thing because of the issue with Vietnamese vs. Serbian, and also because Bulgarian is transliterated different from other languages with which it shares characters.
  const locales = {
    // http://www.eki.ee/wgrs/rom1_bg.pdf
    bg: { Й: 'Y', й: 'y', X: 'H', x: 'h', Ц: 'Ts', ц: 'ts', Щ: 'Sht', щ: 'sht', Ъ: 'A', ъ: 'a', Ь: 'Y', ь: 'y' },
    // Need a reference URL for Serbian.
    sr: { đ: 'dj', Đ: 'DJ' }
  }

I see you default to Serbian and allow a Vietnamese locale. I did the opposite on the grounds that far more people speak Vietnamese than Serbian. Wasn't really sure of another "fair" way to decide which should be the default. I guess you went with Serbian because it was already there in the code so it became the default?

Yes, stuff got added over time, then people started submitting PRs about the 'correct' way to translate a character according to language X, and so that's how I ended up having locales. Though I should document that, so people can have a way to resolve those kind of issues.

Heh, now that you mention it, I didn't document it either other than including an example using locale. But it's not listed in the options or anything. Whoops!


Issue with Amazon-Mailer package

Hi there,
Just trying to setting up repman using docker, but I am getting an issue when trying to setup AWS SES using the package using DSN
MAILER_DSN=ses+api://$AWS_ACCESS_KEY:$AWS_SECRET_KEY@default?region=ap-southeast-2
I've also tried ses+https , ses+smtp and no luck
The error is
Unable to send an email: The security token included in the request is invalid. (code 0).
After doing some investigation look like the version  5.0 of amazon-mailer which is included on the latest version o repman has been deprecated.
AWS SES has changed their API while ago and all the requests should use signature V4, while this deprecated version uses V3. They now require use AsyncAws
https://github.com/symfony/amazon-mailer/blob/c880d1c0920d7dc7d63c74bfcfcddc209b4ed803/Transport/SesApiTransport.php#L24
The version 5.1 of amazon-mailer fixes this issue.
Any change to get the current version of amazon-mailer upgraded on this repo?
You can see some reference on the links below
https://github.com/symfony/symfony/issues/35468
https://github.com/symfony/symfony/pull/35992
Thank you

Hello, of course we can update mailer, I will take care of it soon. Have you tried MAILER_DSN=ses://...?
We are using it in our production instance and it works perfect.

Looks like we need to update Symfony to 5.1 ... but this issue will speed up this process :wink:

Hello, of course we can update mailer, I will take care of it soon. Have you tried MAILER_DSN=ses://...?
We are using it in our production instance and it works perfect.

Hey @akondas, thanks to getting back to me!
I've just tried to use MAILER_DSN=ses://... and didn't work, same error, maybe because I tried to pass the variable to ap-southeast-2 where is my SES setup.
Thanks to looking at this issue. Appreciated it.

Will this fix that exist in 5.1 will be merged back to 4.4?

Hey @PWalkow, hard to say. You can ask this question in any of these issues.
@nandogameiro I have a fix prepared, but I still waiting for another error to be corrected, it seems that it has already been merged (https://github.com/symfony/symfony/pull/37440) but still there was no release until then

Hey @akondas ,cool! thanks for actioning on this! Just waiting this get fixed to starting using repman! :)

Repman 0.6.0 released with symfony 5.1.5 :fireworks:
https://github.com/repman-io/repman/releases/tag/0.6.0


ModuleNotFoundError: No module named 'openlanev2.evaluation'

Thank you for your great job!
When I try to run the dist_train.py , some errors occurred:
dash:
`(openlanev2) zhangyiqing@inin:~/mmdetection3d$ ./tools/dist_train.sh projects/configs/topomlp_setA_r50_wo_yolov8.py 8 --work-dir=./work_dirs/topomlp_setA_r50_wo_yolov8
WARNING:__main__:*****************************************
Setting OMP_NUM_THREADS environment variable for each process to be 1 in default, to avoid your system being overloaded, please further tune the variable for optimal performance in your application as needed.
*****************************************
Traceback (most recent call last):
  File "./tools/train.py", line 10, in <module>
    from openlanev2.evaluation import evaluate as openlanev2_evaluate
ModuleNotFoundError: No module named 'openlanev2.evaluation'
Traceback (most recent call last):
  File "./tools/train.py", line 10, in <module>
    from openlanev2.evaluation import evaluate as openlanev2_evaluate
ModuleNotFoundError: No module named 'openlanev2.evaluation'
Traceback (most recent call last):
  File "./tools/train.py", line 10, in <module>
    from openlanev2.evaluation import evaluate as openlanev2_evaluate
ModuleNotFoundError: No module named 'openlanev2.evaluation'
Traceback (most recent call last):
  File "./tools/train.py", line 10, in <module>
    from openlanev2.evaluation import evaluate as openlanev2_evaluate
ModuleNotFoundError: No module named 'openlanev2.evaluation'
Traceback (most recent call last):
  File "./tools/train.py", line 10, in <module>
    from openlanev2.evaluation import evaluate as openlanev2_evaluate
ModuleNotFoundError: No module named 'openlanev2.evaluation'
Traceback (most recent call last):
  File "./tools/train.py", line 10, in <module>
    from openlanev2.evaluation import evaluate as openlanev2_evaluate
ModuleNotFoundError: No module named 'openlanev2.evaluation'
Traceback (most recent call last):
  File "./tools/train.py", line 10, in <module>
    from openlanev2.evaluation import evaluate as openlanev2_evaluate
ModuleNotFoundError: No module named 'openlanev2.evaluation'
Traceback (most recent call last):
  File "./tools/train.py", line 10, in <module>
    from openlanev2.evaluation import evaluate as openlanev2_evaluate
ModuleNotFoundError: No module named 'openlanev2.evaluation'
ERROR:torch.distributed.elastic.multiprocessing.api:failed (exitcode: 1) local_rank: 0 (pid: 1295863) of binary: /home/zhangyiqing/miniconda3/envs/openlanev2/bin/python
/home/zhangyiqing/miniconda3/envs/openlanev2/lib/python3.8/site-packages/torch/distributed/elastic/multiprocessing/errors/__init__.py:367: UserWarning:

**********************************************************************
               CHILD PROCESS FAILED WITH NO ERROR_FILE
**********************************************************************
CHILD PROCESS FAILED WITH NO ERROR_FILE
Child process 1295863 (local_rank 0) FAILED (exitcode 1)
Error msg: Process failed with exitcode 1
Without writing an error file to <N/A>.
While this DOES NOT affect the correctness of your application,
no trace information about the error will be available for inspection.
Consider decorating your top level entrypoint function with
torch.distributed.elastic.multiprocessing.errors.record. Example:

  from torch.distributed.elastic.multiprocessing.errors import record

  @record
  def trainer_main(args):
     # do train
**********************************************************************
  warnings.warn(_no_error_file_warning_msg(rank, failure))
Traceback (most recent call last):
  File "/home/zhangyiqing/miniconda3/envs/openlanev2/lib/python3.8/runpy.py", line 194, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "/home/zhangyiqing/miniconda3/envs/openlanev2/lib/python3.8/runpy.py", line 87, in _run_code
    exec(code, run_globals)
  File "/home/zhangyiqing/miniconda3/envs/openlanev2/lib/python3.8/site-packages/torch/distributed/run.py", line 702, in <module>
    main()
  File "/home/zhangyiqing/miniconda3/envs/openlanev2/lib/python3.8/site-packages/torch/distributed/elastic/multiprocessing/errors/__init__.py", line 361, in wrapper
    return f(*args, **kwargs)
  File "/home/zhangyiqing/miniconda3/envs/openlanev2/lib/python3.8/site-packages/torch/distributed/run.py", line 698, in main
    run(args)
  File "/home/zhangyiqing/miniconda3/envs/openlanev2/lib/python3.8/site-packages/torch/distributed/run.py", line 689, in run
    elastic_launch(
  File "/home/zhangyiqing/miniconda3/envs/openlanev2/lib/python3.8/site-packages/torch/distributed/launcher/api.py", line 116, in __call__
    return launch_agent(self._config, self._entrypoint, list(args))
  File "/home/zhangyiqing/miniconda3/envs/openlanev2/lib/python3.8/site-packages/torch/distributed/launcher/api.py", line 244, in launch_agent
    raise ChildFailedError(
torch.distributed.elastic.multiprocessing.errors.ChildFailedError:
***************************************
        ./tools/train.py FAILED
=======================================
Root Cause:
[0]:
  time: 2024-01-15_10:47:21
  rank: 0 (local_rank: 0)
  exitcode: 1 (pid: 1295863)
  error_file: <N/A>
  msg: "Process failed with exitcode 1"
=======================================
Other Failures:
[1]:
  time: 2024-01-15_10:47:21
  rank: 1 (local_rank: 1)
  exitcode: 1 (pid: 1295864)
  error_file: <N/A>
  msg: "Process failed with exitcode 1"
[2]:
  time: 2024-01-15_10:47:21
  rank: 2 (local_rank: 2)
  exitcode: 1 (pid: 1295865)
  error_file: <N/A>
  msg: "Process failed with exitcode 1"
[3]:
  time: 2024-01-15_10:47:21
  rank: 3 (local_rank: 3)
  exitcode: 1 (pid: 1295866)
  error_file: <N/A>
  msg: "Process failed with exitcode 1"
[4]:
  time: 2024-01-15_10:47:21
  rank: 4 (local_rank: 4)
  exitcode: 1 (pid: 1295867)
  error_file: <N/A>
  msg: "Process failed with exitcode 1"
[5]:
  time: 2024-01-15_10:47:21
  rank: 5 (local_rank: 5)
  exitcode: 1 (pid: 1295868)
  error_file: <N/A>
  msg: "Process failed with exitcode 1"
[6]:
  time: 2024-01-15_10:47:21
  rank: 6 (local_rank: 6)
  exitcode: 1 (pid: 1295869)
  error_file: <N/A>
  msg: "Process failed with exitcode 1"
[7]:
  time: 2024-01-15_10:47:21
  rank: 7 (local_rank: 7)
  exitcode: 1 (pid: 1295870)
  error_file: <N/A>
  msg: "Process failed with exitcode 1"
***************************************
`

My environment is :
mmcv-full                 1.5.2
mmdet                     2.26.0
mmdet3d                   1.0.0rc6             /home/zhangyiqing/mmdetection3d
mmsegmentation            0.29.1

Looking forward to your help! Thank you.
Best regards

The plugin model currently does not support the v2.x version of OpenLane-V2.
You can checkout to v1.1.0 of OpenLane-V2 repo, or install v1.1.0 from pip to fix this.

Thank you for your answer! It works for me. :)


Block direct public IP address access to internet

There's currently no good way to block direct IP access to websites.
Advertisers can exploit this to avoid ad block. It cost barely anything to switch to a new IPv6 address.
$network block access to host resolved to the IP as well. and that can cause potential incorrect blockings such as dns.proxy.block.AAAA.requests in Adguard advance settings
It can also result in privacy leak as most privacy protection app only prevent IPv6 leak by block AAAA DNS records.
Direct IPv6 address website examples
https://[2606:4700:4700::1111]/
Here's a another that can get your IPv6 address.
https://[2604:a880:800:10::e6:b001]/api/iso_code

Hello! Try this rules:
/^[htpws]+:\/\/[0-9]+.[0-9]+.[0-9]+.[0-9]+\//$all
/^[htpws]+:\/\/\[/$all

Thank you @sfionov
Doesn't regex match every single request and will cause adguard to work slowly?
Is it possible to add a dedicated option for this?

@billkewl this can only be a noticeable problem when there're thousands of regular expressions so no worries :)


Add local file embedding for SSH keys and systemd units

As described in #179 I added an option to define local SSH authorized keys alongside embedding/inlining them.
The code is mostly derived from the existing Resource translator. It would interesting to add a source translator as well that fetches SSH keys from an URL, e.g. a Github user profile. This is going to get "interesting", though, when multiple keys are defined (see travier's profile).
Additionally, all the verification checks the Resource translator maps into the Ignition equivalent would've to be inlined into butane if I am not entirely mistaken.

I'll go fix the breaking tests later today, apparently I missed those for some reason. Sorry about that.

One option is to deprecate ssh_authorized_keys and create e.g. ssh_authorized_keys_source of type SSHAuthorizedKeyResource. But looking at how Resource is defined now, it's just the underlying Ignition Resource struct with inline and local fields added. Along similar lines, we could add a new field ssh_authorized_keys_local (or ssh_authorized_key_files, depending how we want to be confusing) in the PasswdUser struct. That isn't ideal, but it's minimally invasive. I'm inclined to recommend the latter path, but open to ideas.

If we want to support multiple options like source/inline/local, then I would prefer the deprecation + new entry route.
If we think we will only add the files option, then a new option looks like the simplest solution.
I could see the "import SSH public key directly from my GitHub profile" use case having some value thus I don't have a preference.

@bgilbert thanks so much for the review and feedback. I'll go over it soon and update the pull request.
Concerning the "multiple keys per file": I can try to accommodate that and would, hence, treat each line in a file as a single key.
Concerning "keys from URL" (such as the GitHub profile link): The checks that are part of (Ignition)Resource such as TLS verification and hash comparisons would have to be either skipped because the Ignition type sshAuthorizedKeys (list of strings) doesn't support them (as it isn't a Resource) or build into butane, correct?
Given that, would the correct approach be to add something like sshAuthorizedKeysResource to the Ignition base-spec and target that with the same translation mechanism which already exists for file-resources? This would still require particular handling for "multiple keys per file" (regardless of locally or remotely sourced), though.

If we want to support remote URLs, I think it should probably be done natively in the Ignition spec, and then that schema structure should be replicated here.  If we handled URL fetching in Butane, some types of resources would be fetched when Butane runs and some when Ignition runs, which would be confusing.  For SSH keys, which are security sensitive, it's even more important that users know at what time the keys are bound to a machine.
For previous discussion on expanding the types of resources Ignition can fetch, see https://github.com/coreos/ignition/issues/884, https://github.com/coreos/ignition/pull/986, and https://github.com/coreos/ignition/issues/1097.  It would have made sense to support fetching more broadly in the original spec, but I do worry about the amount of churn it would create to add that functionality now.

For previous discussion on expanding the types of resources Ignition can fetch, see coreos/ignition#884, coreos/ignition#986, and coreos/ignition#1097. It would have made sense to support fetching more broadly in the original spec, but I do worry about the amount of churn it would create to add that functionality now.

Thanks, looks like this has been well explored before. I think it would be great to have that kind of "all resources are treated equal and you can fetch them from anywhere" but it indeed makes it much more complicated in Ignition, would be a breaking spec change and network failures could make provisioning unreliable.
Thus I'm now in favor of making a couple of smaller additions to the Butane spec only to enable local inclusions only for SSH keys and systemd units.
We could then revisit this once we decide to do an Ignition spec 4.

What this could potentially look like:
systemd:
  contents_local (object):
    - path (string):
password:
  users:
    - ssh_authorized_keys_local (list of objects):
      - path (string):

@travier Hmm, the extra objects for the _local fields are inconsistent with their non-local counterparts, and with how local is handled in Resource.  I was thinking something like this:
systemd:
  units:
    - contents_local (string):
passwd:
  users:
    - ssh_authorized_keys_local (list of strings):

I just updated the PR with a WIP implementation of the suggested changes. It doesn't work as expected because the translation set contains the wrong data and I don't know why. I'd appreciate a pointer or two if anyone of you would be so kind.

@bgilbert thank you so much for your input. For FCOS it appears to work as expected. However, the config/openshift/v4_10_Exp/translate_test.go test case for TestValidateSupport now fails because for some reason it expects:
Error:  Received unexpected error:
        Missing paths in TranslationSet:
        $.spec.config.passwd.users.0.homeDir
        $.spec.config.passwd.users.0.noCreateHome
        $.spec.config.passwd.users.0.noLogInit
        $.spec.config.passwd.users.0.noUserGroup
        $.spec.config.passwd.users.0.passwordHash
        $.spec.config.passwd.users.0.primaryGroup
        $.spec.config.passwd.users.0.shouldExist

whereas originally it tested for:
$.passwd.users.0.home_dir
$.passwd.users.0.no_create_home
$.passwd.users.0.no_log_init
$.passwd.users.0.no_user_group
$.passwd.users.0.password_hash
$.passwd.users.0.primary_group
$.passwd.users.0.should_exist

I would assume that has something to do with my changes in base/v0_5_exp/translate#translatePasswdUser where I added the translate.MergeP pieces? I assumed I had to declare them to make sure that all existing PasswdUser fields are properly added with their default translators.

I believe I have fixed all outstanding issues. Feel free to review as a whole once again.
If there is anything else to change or fix  I'll of course take another look at it. Considering that this was part of an effort for myself to better understand butane and in particular try my fingers at #179 I'd be willing to add the same functionality for systemd unit files.

I just rebased my pull request against the latest changes from the main branch. As far as I can tell from the test execution it still looks fine.

As things appear a bit stalled, I'll throw my support for this change. It would really clean up some butane based projects.

@bgilbert @travier I had some free time recently and updated this pull request to allow embedding local SSH keys as well as systemd units to cover the whole issue (#179).
I know there's a general discussion going on to refactor local file embedding overall – nevertheless, feel free to have another look at this pull request. I'd very much appreciate some feedback and an idea of whether this will be merged at some point or the generalized approach is preferred.
@abalmos FYI.

Took a quick look and this LGTM but I'm not up-to-date on Butane code and logic to do an in-depth review. I'll give it a try soon however to see if I catch anything missing/broken.

I don't think the discussion about merging config files should impact this PR as far as I understand.

Thanks once again so much for this in depth review – very helpful indeed.
I resolved (fingers crossed) everything I specifically didn't leave open this time around I hope. Will add a translation set verification similar to the SSH one to the systemd translation test as well later on.

I updated the pull request for local ssh & systemd embedding to incorporate minimal changes for Flatcar configs that were recently introduced. If there's anything else you need please let me know.

@bgilbert if there is anything I can do to speed up the review process to get the local file embeds for systemd units and SSH keys merged please let me know. I am really looking forward to getting this merged.

@travier @bgilbert I just resolved the merge conflicts for the butane "local ssh and local systemd file embedding"-PR. I am still willing to continue working on this PR, however, I would very much like to receive some general feedback here: do you have a rough idea on when you can start reviewing this again? Are there any things I should be doing differently (or at all) to help you with the review process and final merge?
I would really like to see this merged (sooner rather than later) because I have a small project myself that would benefit from this tremendously and I am certain others would like to see this as well. If you, however, already know that this won't be happening for the foreseeable future (or in the way prepared here) that's also okay – in that case close the PR, please.
It's clear that all of you have a lot on your plates and the changes here aren't exactly trivial so do take your time. If, in the mean time, you have the chance to give a little feedback – even if it's just a "yeah, still in the backlog; we'll get back to you" – I'd greatly appreciate it.

Sorry for the late reply. I really want to have this but I haven't had the time to look at it again. I'll see if we can find someone to review it.

Something else that might help with reviewing this change is splitting it into two commits, one for systemd and one for ssh keys.

Something else that might help with reviewing this change is splitting it into two commits, one for systemd and one for ssh keys.

I split this commit up into multiple semantic commits that now only contain required changes (changes to the test script beyond supplying data related to the new features have been removed). Each commit should be valid on its own and pass the test script.
To simplify the upgrade instructions I put them last and included only a single fully-fledged example for each supported platform (FCOS, Flatcar, OpenShift).
If there's anything else I can do, please let me know and I'll take a look.

Thanks for the review; I'll get these fixed shortly – if you need anything else from me to get this merged, please let me know.
In unrelated news: 🎂🥳 – happy birthday PR-289 ;-)

I noticed during local tests that parsing SSH files may break unexpectedly because of the uniqueness requirement: including newlines will mean that a newline is added to the sshAuthorizedKeys – a newline character may, because of the aforementioned requirement, only ever by present once in the sshAuthorizedKeys-list. Having multiple will cause a validation error and break the transformation. However, SSH doesn't actually care because it ignores empty lines (comments, blank newlines).
Question: how to handle that? Strip (duplicate) newline list elements silently? Issue an explicit error if they are found (otherwise it'll just say "there were 'duplicate entries'" which is kinda unhelpful)? Put a warning in the migration notices or somewhere else? Just … ignore this issue? Something else?

That got rid of the Windows test errors now for good as well. In other news … I just now learned that you had already solved that problem in a different test and prepared things for the eventuality it might happen in a different place as well.
@travier bgilbert told me he informed the team of what's supposed to happen next (now that I addressed … I think 🤞  his review findings). I don't know who exactly, though.
There is one comment where I am not entirely sure what I am supposed to change. I would kindly ask you (as a team) to go over this once more and tell me whether you'd like to defer merging this until later (or whether there is anything else I need to change).
I am totally okay with any of these options because I want to make sure that these changes are in the best possible state that they can be.

@bgilbert could you provide an update on when I can expect additional feedback? I'd really love to get this merged. Thanks!

For the record, the merge commit 9342f39c1cbfba2d12fd7460842ad36a59da3869 has some conflict fixups in it.  The GitHub web UI doesn't seem to display those, though.

I noticed during local tests that parsing SSH files may break unexpectedly because of the uniqueness requirement: including newlines will mean that a newline is added to the sshAuthorizedKeys – a newline character may, because of the aforementioned requirement, only ever by present once in the sshAuthorizedKeys-list. Having multiple will cause a validation error and break the transformation. However, SSH doesn't actually care because it ignores empty lines (comments, blank newlines).

Yeah, I'd be inclined to strip blank lines entirely when building a key list from a file.

Followup in #441.

This looks good overall. There are various small fixes, but I'm not going to ask you to handle them, since you've already been through several long review cycles here. I think we can merge this as-is, and I'll submit a separate PR with some followups. Feel free to add your thoughts there if you'd like.
Thank you so much for all your work to get this landed!

Thanks a lot for your very constructive feedback for this PR and willingness to go through so many iterations and make sure that a good implementation makes it into butane!
I'll be sure to stick around and have a look at what else you're up to here and see whether I can continue to contribute in the future.

Thanks a lot @Okeanos


Add resourceHeader to Proptypes

@jquense would you mind reviewing. also any idea when the next release might be?


Empty slides on the last page

When I have 10 slides which should show per 3 on the each page, I see only one slide on the last page. In the version 0.7.1 all works fine!
Fox example its my slider with slides on the each page:
page 1: [0, 1, 2]
page 2: [3, 4, 5]
page 3: [6, 7, 8]
page 4: [9, _, _]
Is should be like this on the 4th page:
page 4: [7, 8, 9]
When I haven't enough slides for last page, I should see few slides from previous page.

Here is example
P.S. Go to the last page

It's example from version 0.7.1 where on the last page I can see correct slides. But, there are some strange behavior, on the last page I see [7, 8, 9] slides, but when I go to the previous page I see [6, 7, 8] slides, will be better show [4, 5, 6] slides.
Logic in that, when you will able show 3 next/previous slides - you show! When there are less then 3 slides on the next/previous page you should show those slides + one or more slides from current page.

Hey @dvasyliev, thanks for detailed reporting! This is actually a bug that was introduced with the last update. There is an open issue for its resolution that you can follow here -> #215
Going to close this in favor of that, but feel free to move your comments over there :~)

@quinnlangille sure!
Hope you will fix it as soon as possible :)

Yeah there are a few people who have already mentioned they're working on solutions, so we'll hopefully see some contributions for it over the weekend


CI: RateLimit for GitHub API

Many CI runs fail, because of the RateLimit for GitHub API.
Maybe someone can help with this problem.
 HTTP/1.1 403 rate limit exceeded returned for "https://api.github.com/repos
  /mozilla/geckodriver/releases/latest".

Hi @Chris53897, thanks for the report. This is a known issue, duplicate of https://github.com/dbrekelmans/browser-driver-installer/issues/70


SoftDelete

Hello.
I think you can get error here, isn't it ? https://github.com/cloudcreativity/laravel-json-api/blame/v1.3.0/src/Eloquent/Concerns/SoftDeletesModels.php#L153
Something like
Call to undefined method ........::getDeletedAtColumn()
Maybe you should make checking for trait or something else...
isset(class_uses($model)[\Illuminate\Database\Eloquent\SoftDeletes::class])

I don't think that's necessary as use of the SoftDeletesModels is completely optional... i.e. you shouldn't be adding it to an adapter for a model that cant be soft deleted.

Just like you only add the Eloquent SoftDeletes trait to the models that actually have a soft delete column

Thanks. Forgot it's optional)

No problem!


Split up Cookies

Estimate: 18 hours
Expressing interest: 4Science
Required cookies must be separated from tracking (statistics) cookies

Atmire's interested in this one as well. It makes sense to do it in a single PR with #735

@artlowel : Sounds good. I've assigned this to you.


DllReferencePlugin doesn't explain string form for 'manifest' parameter

The manifest parameter for DllReferencePlugin also supports the ability to pass a string (as an absolute path) rather than an object.   The logic is implementation here.
This has been supported since this commit.
The documentation should clearly indicate that the manifest parameter can also be specified as an absolute path string.

Thanks for pointing this out. Would you be interested in submitting a PR to resolve this issue?


Google refresh token no longer works

Known issue, the google refresh token method no longer works.

Google refresh token method has been deprecated. Updated source files in v0.1.0 removes this and adds the Google cookie token method


Problem with es6

Hi folks,
since my page is not rendered probably on prerender.io I tried debugging using the local server.
I realized that it seems to have some problems with es6 data structures, since i get
2016-04-13T18:34:04.493Z getting https://localhost:8047/
Error: Can't find variable: Map
which seems to break everything.
Is there a way to use prerender with es6 structures? I am already using babel to transcompile the code back to es5 (es2015 preset) but that only affects functions. I also have tried adding the polyfill in my project, but it does not seem to fix the issue above.
Any good idea would be appreciated pretty much.

Sorry! The latest version of PhantomJS does not support those features so you'd want to add a polyfill. If you are having trouble getting a polyfill to work, feel free to send us an email at<EMAIL_ADDRESS>and we'd be happy to help.


Fix the last argument not to be discarded in dry run mode

In the example below, the last 3 should be included, but not.
irb(main):006:0> Frontkick::Command.exec(['echo', '1', '2', '3'], :dry_run => 1).stdout
=> "echo 1 2"

thanks!

0.4.4 is released!

Thank you:)


Weird Crash; Objective-C; Realm 0.96.2; "Object has been deleted or invalidated."

I have been searching everywhere to find a solution to a weird problem I can’t seem to solve. The Realm tag on Stackoverflow has not revealed anything useful and I haven’t found anything in the documentation (yet) that can point me in the right direction.
For context: We are building an application that gets the best restaurants in your area from Foursquare and saves them to Realm. The application then gets a randomised index from the Realm array storing the restaurants to display “a random best restaurant near you”. We also have an object for the User which stores the user’s preferences locally in Realm.
I am trying to implement a button on the settings panel that deletes all of the data in Realm and brings the user back to our on boarding flow to provide new preferences and a clean slate for the restaurants object. When the user taps the button, a UIAlertController is presented with a destructive action. The following code is in the handler upon pressing that confirmation button:
RLMRealm *realm = [RLMRealm defaultRealm];

[realm beginWriteTransaction];
[realm deleteAllObjects];
[realm commitWriteTransaction];

[[NSUserDefaults standardUserDefaults] removeObjectForKey:kUserCreatedFlag];
[self performSegueWithIdentifier:kSegueToOnboardingFlowAfterDestruction sender:self];

My thought process:

Delete all objects in the default Realm.
Remove the NSUserDefaults flag that is used to check if a user exists/which storyboard to present.
Perform a segue to the onboarding flow.

But unfortunately we I can not get around this crash:
2015-11-18 11:10:17.218 Lunchtime[8629:3384811] *** Terminating app due to uncaught exception 'RLMException', reason: 'Object has been deleted or invalidated.'
*** First throw call stack:
(0x18433cf48 0x1997e7f80 0x10011e0b0 0x1000980cc 0x100097e48 0x100180fcc 0x100181568 0x100092158 0x189d357d8 0x189d35f70 0x189c24ba4 0x189c27d9c 0x1899ff668 0x18990b240 0x18990ad3c 0x18990abc4 0x1890d1c2c 0x101df1c68 0x101df7710 0x1842f41f8 0x1842f2060 0x184220ca0 0x18f7a4088 0x189938ffc 0x100097b34 0x19a02a8b8)
libc++abi.dylib: terminating with uncaught exception of type NSException

I have confirmed in the Realm Browser that all of the data has been removed from Realm but I am still receiving this crash for some reason. I would really appreciate it if someone could offer some insight into why this is happening. My instructors are also having a hard time figuring out what the issue is. Could this be an undefined/incorrectly defined exception in Realm?
Looking forward to hearing from someone. :)

The exception you're seeing, "Object has been deleted or invalidated", is thrown if you attempt to access properties of an object that has been deleted from the Realm or explicitly invalidated via a call to -invalidate. After your call to -[RLMRealm deleteAllObjects], all RLMObjects that you have previously retrieved from the the Realm are invalid and cannot be accessed. To understand where this is happening in your application, you can add a breakpoint when Objective-C exceptions are thrown. This will drop you into Xcode's debugger at the point when the exception is thrown, which should help you pinpoint where in your application you're accessing the deleted object.

Ouch.  Thanks @bdash for mentioning the Objective-C exception breakpoint. I did turn this on before but it was disabled for Objective-C for some reason. After fixing that issue, I quickly tuned into what was causing this.
In my case, I was using a RLMNotificationBlock to update the UI whenever a change was made to the Restaurant model.
self.token = [[RLMRealm defaultRealm] addNotificationBlock:^(NSString *notification, RLMRealm *realm) {
    [self updateUI];
}];

And because [self updateUI] accessed several objects that were deleted beforehand, I was receiving that crash. Adding a quick check to see if [RLMRealm defaultRealm] is empty fixed the issue.
Thank you! :dancer:


16 minor updates to fields based

Thanks for getting this started! input type="textentry" doesn't quite work. https://developer.mozilla.org/en-US/docs/Web/HTML/Element/textarea has examples. Fixed things up


Search fields in Frontend ListView (DataTableMixin is not compatible)

Hello!
It's possible to add search fields in frontend listview? I think that there is a problem in DataTableMixin or in ListView.html js code. I am a pro user.
I have been doing tests with Datatable, for example enabling searching' : true in datatable_config, but it does not work. It seems to be a problem with data pagination or similar (not sure sorry)
I'm right? Are you planning to resolve this? I think search fields is a must have feature in this great app.
Thank you in advance

I, see no problem with searching: true option
django-material uses ajax server-side datatable rendering mode. You've got search value in request.GET['datatable-search[value]'] and should process in your view


Secret storage

Currently the config has a single storage option which is used to store all data.  Devs should optionally be able to provide a separate storage adapter so that keys can be stored separately from auth data.
This is a good security measure because if your database has a SQL injection vulnerability, for example, it doesn't compromise the private key.
Example providers would be AWS Secrets Manager or Cloudflare Secrets Store.

this is in support of stepping towards something like #54

@thdxr I think this would be for storing public/private oauth keys


Settings/Preferences "General" > "d/l updates" checkbox doesn't stick

Describe the bug
Checking the Automatically download updates checkbox doesn't stick when navigating preferences.
To Reproduce

Open Preferences (Settings)
See that Automatically download updates is unchecked
Check Automatically download updates
Click on another tab (e.g., System)
Click back to General tab

Expected behavior
Automatically download updates stays checked.
Actual behavior
Automatically download updates is unchecked.
Note: checking Automatically download updates, then closing the window, then reopening it shows it remaining checked. However, clicking over to another tab (e.g., System) unchecks the setting again.
Other
I also noticed "glitchiness" when initially using the Settings dialog: couldn't change tabs until I closed and reopened the dialog. Am unable to recreate this issue reliably, though.
Orb Report
OrbStack info:
  Version: 0.13.0 (130000)
  Commit: ba57f21d6c60d45e0469196f4a67c79ec9911eea (v0.13.0)

System info:
  macOS: 12.6.7 (21G651)
  CPU: amd64, 16 cores
  CPU model: Intel(R) Core(TM) i7-10700K CPU @ 3.80GHz

Additional context
I didn't include logs since this is (purely?) a GUI issue and didn't see anything relevant. Can still provide if needed.

Fixed for the next version. Thanks for reporting! Seems like this bug is specific to macOS 12.
The tab switching issue sounds like a SwiftUI bug in macOS 12 that we may not be able to do much about, unfortunately.
Just curious: is there a specific reason you haven't updated to macOS 13? (helpful to know for version distribution/support purposes)

specific reason you haven't updated to macOS 13

Yeah, there's music software I use that doesn't work well with 13 (yet?). I'll probably upgrade to 13 when Sonoma (14) is released, though.


AU Localisation

unable to test locally but would like review given some big changes. E.g.

remove “it’s complicated” option in Rights
collapse licence and waiver

Changes Unknown when pulling c10f24276e5f96b8828895b6b19600ca45bc484d on Stephen-Gates:AU-Localisation into ** on theodi:staging**.

I have drafted the Privacy questions to add to the localisation. I have an XML version ready to add. If #1409 can be resolved, I would prefer to test these locally to ensure they're technically correct and acceptable to stakeholders before adding them to this PR.

Coverage remained the same at 81.003% when pulling a4be33f787ee0e972099a730b36495352cf597b1 on Stephen-Gates:AU-Localisation into 658ae69892b85940e0910e60ff23abbf6c7476d8 on theodi:staging.

OK @Stephen-Gates I've generated the ruby/yaml (and improved the docs slightly). You'll want to rerun docker-compose run web bundle exec rake surveyor:build_changed_survey FILE=surveys/generated/surveyor/odc_questionnaire.AU.rb to load the new version.

If you have saxon installed, you just need to run saxon -s:prototype/jurisdictions/ -xsl:surveys/transform/surveyor.xsl -o:surveys/ to compile changes in the XML to the right place.

That command will change a whole LOAD of things, but ignore anything non-AU.

Coverage remained the same at 81.003% when pulling a6e5cb6c5f69030ac44216e2474c4dfb0b165dff on Stephen-Gates:AU-Localisation into 658ae69892b85940e0910e60ff23abbf6c7476d8 on theodi:staging.

@JeniT a question for you here; @Stephen-Gates has combined the license and waiver questions into one. What impact do you think that will have in terms of the "correctness" of it all, as well as technically, and if it's OK, is it something we can use to simplify other jurisdictions as well?

see Australian Open Data Certificate Help for line of questioning

@Stephen-Gates I can't see where you've collapsed licence and waiver?

Coverage remained the same at 81.871% when pulling 486d7bee30ef31c3fc64745af15a9d28785a2a27 on Stephen-Gates:AU-Localisation into 6bf793fdf998bdf4371810e4468af1e1cd051e1c on theodi:staging.

This will be replaced by another PR


[BUG] rancher 2.6-2.7 metric dashboard memory monitoring information about Replicaset

Rancher Server Setup

Rancher version: 2.6.11
Installation option (Docker install/Helm Chart): Helm Chart

If Helm Chart, Kubernetes Cluster and version (RKE1, RKE2, k3s, EKS, etc): v1.22.15 -aliyun.1

Information about the Cluster

Kubernetes version: 1.22
Cluster Type (Local/Downstream): K3S/ACK/GKE

If downstream, what type of cluster? (Custom/Imported or specify provider for Hosted/Infrastructure Provider):

Describe the bug

The original monitoring Replicaset's memory prometheus sql shows inaccurate information, the value is twice the actual value, after investigation because of inaccurate filtering of pod information in sql, resulting in double the memory value of repeat pass a pod

Subsequent change of sql to "(sum(container_memory_working_set_bytes{namespace=~"$namespace",container!=""} OR windows_container_memory_ usage_commit_bytes{namespace=~"$namespace",container!=""}) by (pod)) * on(pod) kube_pod_info{namespace=~"$namespace", created_by_kind="$ kind", created_by_name="$workload"}"
The grafana information is then accurate, but the rancher's embedded metrics dashboard incorrectly displays other workloads when showing the Replicaset's resource usage

To Reproduce

Result
Expected Result

Screenshots

Additional context

me too

@fishermenInPuqian Hello, has it been fixed?


Add docker-compose.yml

Added docker-compose.yml to allow an easier build and management of the docker environment.

Excuse me, could you explain the purpose of this PR, please?
There is a Dockerfile already. So your PR does not make sense to me.

At first: thanks a lot for your blazingly fast reply!
Yes, there is already a Dockerfile, which specifies how to build the eml_analyzer container. Docker-compose is going one-step further and helps to easily manage and share setups of multiple containers.
I'm aware that we are only talking about one single container in this case, but for me the existance of the docker-compose.yml makes things easier and I'd thought to share this with the community.
Cheers
Andreas

To be honest, I don't see a value to run single container with Docker Compose.
But the Dockerfile uses a (little bit) dirty hack to run Uvicorn and SpamAssasin in the same container.
So using Docker Compose to fix this hack makes sense to me.
I implemented that my self. (#152)
So now you can use EML analyzer with Docker Compose. Thank you for your suggestion.


Code example in paper

There are a few details i don't understand in the code example:

In[4]: when we assume the X-ray is positive, why does it correspond to Dict(7 => 0)
In[7]: the phrasing is a bit ambiguous, there is only one most probable outcome which has several variables (and by the way, variables 3 and 4 are zero in this one)

https://github.com/openjournals/joss-reviews/issues/5700

Thanks for spotting these! You are right in both cases. We fixed them in the repo's example (https://github.com/TensorBFS/TensorInference.jl/commit/457960f9e1f7589e2f78f522d85e64dcbb11e493)
and in the paper (https://github.com/TensorBFS/TensorInference.jl/commit/8457c6f992a214d5c24f63060faa7bb03a57c786).


[Bug fix] Fix empty properties WebSocket.

@Sotam what was the problem here?

did it not understand how to map the numbers?

@dougdellolio correct, it didn't understand how to map the numbers.


TestAdapter: Wrongly grouped DataTestMethod

Describe the bug
DataTestMethods are wrongly grouped with MSTest.TestAdapter in version 3.0.x
(Grouping in VS is by Traits)
Wrong grouping:

Expected grouping (achieved with MSTest.TestAdapter 2.2.x):

Steps To Reproduce
Explore tests in this class:
using Microsoft.VisualStudio.TestTools.UnitTesting;

namespace TestProject
{
    [TestClass]
    [TestCategory("L3")]
    public class BasicUnitTest : UnitTestBase
    {
        public override int TypeCount => 3;
    }

    [TestClass]
    [TestCategory("L3")]
    public class ExtendedUnitTest : UnitTestBase
    {
        public override int TypeCount => 8;
    }

    [TestClass]
    [TestCategory("L3")]
    public class UnitTestBase
    {
        public virtual int TypeCount => 5;

        [DataRow(1)]
        [DataRow(2)]
        [DataTestMethod]
        public void DocumentCostCurrentDataFunctions(int count)
        {
            Assert.IsTrue(count < TypeCount);
        }
    }
}

Expected behavior
Expected grouping (achieved with MSTest.TestAdapter 2.2.x):

Actual behavior
Wrong grouping:

Additional context
We also run tests in Azure DevOps wth vstest.console.exe  "C:\abc.dll" /TestCaseFilter:"TestCategory=L3" "/logger:trx;LogFileName=C:\abc.trx" /TestAdapterPath:"C:\UnitTests\Tests" command. The test report file has changed after the libraries update.

Hi @HightowerCZ,
Thanks for reporting this bug. I can also reproduce the issue, we will need to investigate to understand what changed.
As for the report file being changed, are you talking about the change of ID or are you referring to something else?

Hi @Evangelink,
We have two issues. One is showing in Visual Studio; the second is with trx reporting file. I am including the correct report and the incorrect report. It is difficult to find which test failed since the name of the test is the same for all runs.
TestResults.zip
We noticed the issue because we are upgrading our solution from .Net Framework 4.8 to .NET 7.0.
Newest findings:

vstest.console.exe produce grouped results only for MSTest.Adapter 2.2.3, but this version shows tests in VisualStudio incorrectly
vstest.console.exe in different versions of MSTest.Adapter than 2.2.3 shows mostly correctly in VisualStudio, but produce the ungrouped report

Is this what you asked for?

Hi @HightowerCZ,
I am waiting for a little more info about the change of behaviour in VS because it's not yet fully clear if this is coming from a change caused by MSTest or VS Test Explorer. I will let you know more when I have some news.
Regarding the change in the trx, this is not linked to traits grouping but linked to a change of behavior (breaking change) that was introduced in 2.2.4. This is unfortunate but sadly we cannot easily change this on our side because we need to synchronize with Azure DevOps team to ensure the UI will reflect the change. To get more information about this change, I encourage you to refer to https://github.com/microsoft/testfx/issues/1024.

In MSTest v3+ we have started using some new features from newer versions of Test Platform and one of them is causing this change of display in VS. The Test Explorer team (cc @peterwald) told me that if you update your grouping to be "Traits" + "Class" you will have an output similar to the previous one:

I will update the release notes to specify that change of behaviour and this "workaround".
I hope this new display is convenient enough for you?!


Using CPU when resume training from checkpoint @ patch 2024.7

Hi guys! I got the following error when using Unsloth patch 2024.7 to resume training from checkpoint.
RuntimeError: Expected all tensors to be on the same device, but found at least two devices, cpu and cuda:0! (when checking argument for argument mat2 in method wrapper_CUDA_mm)

I did not occur this error when using the older version.
Just curious, is it possible to install and use the older version of Unsloth?

Edit
Here is the full error:
---------------------------------------------------------------------------
RuntimeError                              Traceback (most recent call last)
Cell In[13], line 1
----> 1 trainer_stats = trainer.train("/kaggle/working/outputs/checkpoint-525")
      2 # trainer_stats = trainer.train()

File <string>:123, in train(self, resume_from_checkpoint, trial, ignore_keys_for_eval, **kwargs)

File <string>:422, in _fast_inner_training_loop(self, batch_size, args, resume_from_checkpoint, trial, ignore_keys_for_eval)

File /opt/conda/lib/python3.10/site-packages/accelerate/optimizer.py:157, in AcceleratedOptimizer.step(self, closure)
    154 if self.scaler is not None:
    155     self.optimizer.step = self._optimizer_patched_step_method
--> 157     self.scaler.step(self.optimizer, closure)
    158     self.scaler.update()
    160     if not self._accelerate_step_called:
    161         # If the optimizer step was skipped, gradient overflow was detected.

File /opt/conda/lib/python3.10/site-packages/torch/cuda/amp/grad_scaler.py:452, in GradScaler.step(self, optimizer, *args, **kwargs)
    446     self.unscale_(optimizer)
    448 assert (
    449     len(optimizer_state["found_inf_per_device"]) > 0
    450 ), "No inf checks were recorded for this optimizer."
--> 452 retval = self._maybe_opt_step(optimizer, optimizer_state, *args, **kwargs)
    454 optimizer_state["stage"] = OptState.STEPPED
    456 return retval

File /opt/conda/lib/python3.10/site-packages/torch/cuda/amp/grad_scaler.py:350, in GradScaler._maybe_opt_step(self, optimizer, optimizer_state, *args, **kwargs)
    348 retval: Optional[float] = None
    349 if not sum(v.item() for v in optimizer_state["found_inf_per_device"].values()):
--> 350     retval = optimizer.step(*args, **kwargs)
    351 return retval

File /opt/conda/lib/python3.10/site-packages/accelerate/optimizer.py:212, in patch_optimizer_step.<locals>.patched_step(*args, **kwargs)
    210 def patched_step(*args, **kwargs):
    211     accelerated_optimizer._accelerate_step_called = True
--> 212     return method(*args, **kwargs)

File /opt/conda/lib/python3.10/site-packages/torch/optim/lr_scheduler.py:75, in LRScheduler.__init__.<locals>.with_counter.<locals>.wrapper(*args, **kwargs)
     73 instance._step_count += 1
     74 wrapped = func.__get__(instance, cls)
---> 75 return wrapped(*args, **kwargs)

File /opt/conda/lib/python3.10/site-packages/torch/optim/optimizer.py:385, in Optimizer.profile_hook_step.<locals>.wrapper(*args, **kwargs)
    380         else:
    381             raise RuntimeError(
    382                 f"{func} must return None or a tuple of (new_args, new_kwargs), but got {result}."
    383             )
--> 385 out = func(*args, **kwargs)
    386 self._optimizer_step_code()
    388 # call optimizer step post hooks

File /opt/conda/lib/python3.10/site-packages/torch/utils/_contextlib.py:115, in context_decorator.<locals>.decorate_context(*args, **kwargs)
    112 @functools.wraps(func)
    113 def decorate_context(*args, **kwargs):
    114     with ctx_factory():
--> 115         return func(*args, **kwargs)

File /opt/conda/lib/python3.10/site-packages/galore_torch/adamw8bit.py:52, in AdamW8bit.step(self, closure)
     49     group['weight_decay_saved'] = group['weight_decay']
     50     group['weight_decay'] = 0
---> 52 grad = state["projector"].project(p.grad, state["step"])
     54 # suboptimal implementation
     55 p.saved_data = p.data.clone()

File /opt/conda/lib/python3.10/site-packages/galore_torch/galore_projector.py:22, in GaLoreProjector.project(self, full_rank_grad, iter)
     20         if self.ortho_matrix is None or iter % self.update_proj_gap == 0:
     21             self.ortho_matrix = self.get_orthogonal_matrix(full_rank_grad, self.rank, type='left')
---> 22         low_rank_grad = torch.matmul(self.ortho_matrix.t(), full_rank_grad)
     23 elif self.proj_type == 'reverse_std':
     24     if full_rank_grad.shape[0] >= full_rank_grad.shape[1]:

RuntimeError: Expected all tensors to be on the same device, but found at least two devices, cpu and cuda:0! (when checking argument for argument mat2 in method wrapper_CUDA_mm)

Oh is this for Galore?

Yeah

@avcode-exe hopefully the issue is now resolved when you update to the latest version of Unsloth? Please let us know if not!! Thank you :)


Check only relevant resource APIs via discovery client at the controller-manager startup

This PR is a

[ ] Feature Implementation
[x] Bug Fix
[ ] Documentation

What this PR does / why we need it:
Make controller-manager not fail to startup when unrelated API server is down.
Which issue(s) this PR fixes

Fixes #2418
Please leave this checklist in the PR comment so that maintainers can ensure a good PR.
Merge Checklist:

[ ] New feature

[ ] Tests
[ ] Documentation

[ ] SVCat CLI flag
[ ] Server Flag for config

[ ] Chart changes
[ ] removing a flag by marking deprecated and hiding to avoid
breaking the chart release and existing clients who provide a
flag that will get an error when they try to update

Since this is mostly a follow-up fix for #2412, I will merge it without waiting for more approvals.
/lgtm
/approve

/lgtm


Reduce actor timer test to 500 qps.

Description
Reduce actor timer test to 500 qps.
Issue reference
We strive to have all PR being opened based on an issue, where the problem or feature have been discussed prior to implementation.
Please reference the issue this PR will close: #2299
Checklist
Please make sure you've  completed the relevant tasks for this PR, out of the following list:

[ ] Code compiles correctly
[X] Created/updated tests
[ ] Unit tests passing
[ ] End-to-end tests passing
[ ] Extended the documentation / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]
[ ] Specification has been updated / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]
[ ] Provided sample for the feature / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]

/ok-to-perf


feat: add workaround to make podman-machine work by default OOB

This just adds gvisor-tap-vsock and makes it so virtiofsd is on $PATH by default, that way podman machine will work out of the box. This fixes #1825

Thank you for the issue and the PR!
Do you have any idea when this problem began?

Honestly, no idea, podman machine never worked on my machine, I installed Bluefin-dx on F40, about 2 or 3 months ago and, on 40 it didnt work, now on 41 it also doesnt work (OOB i mean).

FYI - this does bring in a bunch of dependencies for multi-arch

Added:
  SLOF-20220719-5.git6b6c16b4.fc41.noarch
  edk2-aarch64-20240813-2.fc41.noarch
  edk2-arm-20240813-2.fc41.noarch
  edk2-riscv64-20240813-2.fc41.noarch
  gvisor-tap-vsock-6:0.7.5-1.fc41.x86_64
  gvisor-tap-vsock-gvforwarder-6:0.7.5-1.fc41.x86_64
  openbios-1:20230126-4.gitaf97fd7.fc41.noarch
  podman-machine-5:5.2.5-1.fc41.x86_64
  qemu-2:9.1.1-1.fc41.x86_64
  qemu-system-aarch64-2:9.1.1-1.fc41.x86_64
  qemu-system-aarch64-core-2:9.1.1-1.fc41.x86_64
  qemu-system-alpha-2:9.1.1-1.fc41.x86_64
  qemu-system-alpha-core-2:9.1.1-1.fc41.x86_64
  qemu-system-arm-2:9.1.1-1.fc41.x86_64
  qemu-system-arm-core-2:9.1.1-1.fc41.x86_64
  qemu-system-avr-2:9.1.1-1.fc41.x86_64
  qemu-system-avr-core-2:9.1.1-1.fc41.x86_64
  qemu-system-cris-2:9.1.1-1.fc41.x86_64
  qemu-system-cris-core-2:9.1.1-1.fc41.x86_64
  qemu-system-loongarch64-2:9.1.1-1.fc41.x86_64
  qemu-system-loongarch64-core-2:9.1.1-1.fc41.x86_64
  qemu-system-m68k-2:9.1.1-1.fc41.x86_64
  qemu-system-m68k-core-2:9.1.1-1.fc41.x86_64
  qemu-system-microblaze-2:9.1.1-1.fc41.x86_64
  qemu-system-microblaze-core-2:9.1.1-1.fc41.x86_64
  qemu-system-mips-2:9.1.1-1.fc41.x86_64
  qemu-system-mips-core-2:9.1.1-1.fc41.x86_64
  qemu-system-or1k-2:9.1.1-1.fc41.x86_64
  qemu-system-or1k-core-2:9.1.1-1.fc41.x86_64
  qemu-system-ppc-2:9.1.1-1.fc41.x86_64
  qemu-system-ppc-core-2:9.1.1-1.fc41.x86_64
  qemu-system-riscv-2:9.1.1-1.fc41.x86_64
  qemu-system-riscv-core-2:9.1.1-1.fc41.x86_64
  qemu-system-rx-2:9.1.1-1.fc41.x86_64
  qemu-system-rx-core-2:9.1.1-1.fc41.x86_64
  qemu-system-s390x-2:9.1.1-1.fc41.x86_64
  qemu-system-s390x-core-2:9.1.1-1.fc41.x86_64
  qemu-system-sh4-2:9.1.1-1.fc41.x86_64
  qemu-system-sh4-core-2:9.1.1-1.fc41.x86_64
  qemu-system-sparc-2:9.1.1-1.fc41.x86_64
  qemu-system-sparc-core-2:9.1.1-1.fc41.x86_64
  qemu-system-tricore-2:9.1.1-1.fc41.x86_64
  qemu-system-tricore-core-2:9.1.1-1.fc41.x86_64
  qemu-system-xtensa-2:9.1.1-1.fc41.x86_64
  qemu-system-xtensa-core-2:9.1.1-1.fc41.x86_64
  qemu-tools-2:9.1.1-1.fc41.x86_64
  qemu-user-2:9.1.1-1.fc41.x86_64

Don't think this is an issue.  Just something to be aware of.

FYI - this does bring in a bunch of dependencies for multi-arch
Don't think this is an issue since podman-machine is quite important. Just something to be aware of.

Hmm... good point @p5 I'd missed that in my testing since I already had those deps installed.
I 100% believe we want change in bluefin-dx ...
Given we have gcc in bluefin (non dx) I think it's hard to argue against podman-machine in bluefin, too.
I'm torn here... would want @castrojo and @m2Giles to weigh in.

I'm thinking -dx only.
gcc in normal bluefin is a known compromise we hate, so let's keep this in dx imo.


Terminals launched via extensions are sometimes blank

VSCode Version: Code 1.17.0 (be377c0faf7574a59f84940f593a6849f12e4de7, 2017-10-05T06:07:51.906Z)
OS Version: Darwin x64 16.7.0
Extensions:

Extension
Author (truncated)
Version

vscode-paste-and-indent
Rub
0.0.8

vscode-color
ans
0.4.5

python
don
0.7.0

vscode-babel-coloring
dza
0.0.4

vscode-auto-open-markdown-preview
hnw
0.0.4

vscode-filesize
mkx
1.0.0

vscode-open
san
0.1.0

todotasks
san
0.5.0

vscode-todo-highlight
way
0.5.11

Steps to Reproduce:

Once VS Code open, open Integrated Terminal. Shows up blank but still interactive.

Reproduces without extensions: Yes

@derekmiranda what version of macOS are you on?

Sierra 10.12.6

@Tyriar It happens to me as well, steps to reproduce:

Open a terminal
Spawn another one via Terminals
Go to the newly created terminal
It's blank

If the terminal gets resized, or the whole window gets resized it shows up.

@fabiospampinato Hmm it doesn't show up for me at all even after resizing...

@derekmiranda Maybe they are unrelated bugs then, I'm not sure 🤔

Update: The problem still persists on the computer previously mentioned but on my personal Macbook, which is also on Sierra 10.12.6, the terminal works fine. Not sure what might be causing this, is it possibly hardware-related?

Related: https://github.com/Microsoft/vscode/issues/34554

@Tyriar I've ran into the same issue when working on the npm-script-runner extension. I've added a repro extension to #34554.

Duplicate https://github.com/Microsoft/vscode/issues/34554


NuGet package authors should be "XmlUnit Contributors"

In xmlunit.nuspec
Change Authors element to "XmlUnit Contributors"
Remove owners element or set to empty element

resoved by #9


Make TIME_ZONE and LANGUAGE_CODE configurable via env vars

(Thank you so much for your great work, I really love saleor!)
What I'm trying to achieve
I would like to configure TIME_ZONE and LANGUAGE_CODE via env vars
Describe a proposed solution
https://github.com/mirumee/saleor/pull/6209

@maersu Hi there! Thanks for your PR and your kind words. We'll be happy to review it as soon as we can.

Closing as we continued the discussion in the PR.


Enums not quoted

Bug report
Description
When using a member of class(Enum) or class(str, Enum) in a query, I expect the underlying .value of the member to be used when constructing a query so that the result is the same as if I had passed the literal value explicitly.
Example
from pypika import Query, Table
from enum import Enum

class Status(Enum):
    ON = 'on'
    OFF = 'off'

t = Table('tab')
q = Query.from_(t).select(t.col1).where(t.status == Status.ON)

Actual behavior
>>> q.get_sql()
SELECT "col1" FROM "tab" WHERE "status"=on

Expected behavior
>>> q.get_sql()
SELECT "col1" FROM "tab" WHERE "status"='on'

Version info
Python 3.7.9
PyPika 0.47.7

Might this work #561?

Hey @cbows, thanks for the PR but after reviewing it once again, I believe the complexity it adds doesn't pay off. I think your use case is valid, however for custom enum like yours you have already two alternatives, which are pretty solid. The most naive one would be to call value directly in your queries:
q = Query.from_(t).select(t.col1).where(t.status == Status.ON.value)

I understand that you are however expecting something more convenient. For such you could create a custom Enum that always wrap LiteralValue around your custom values, such as:
class LiteralEnum(Enum):
    def __new__(cls, value):
            obj = object.__new__(cls)
            obj._value_ = LiteralValue(value)
            return obj

class Status(LiteralEnum):
    ON = 'on'
    OFF = 'off'

Hi, thanks for reviewing!
However, I think the second solution does not solve the problem that I tried to address initially.
The problem I see very generally is that ValueWrapper treats enum values different from normal values. So a date that is passed literally will be transformed to string and then quoted, but a date passed as a member of an enum is just unpacked and neither converted to string nor is it quoted (the same goes for booleans, strings etc.). So actually enum values are treated kind of like LiteralValues, which felt unintuitive to me and is not what I expected. This was fixed in https://github.com/kayak/pypika/pull/561/commits/145145434e8fd38db56cb64b36cfcea724164c3d and this was my actual concern.
The other problem (and I think this is what your second solution refers to) is something unrelated, but surfaced after running the tests with the corrected enum behavior. And I still think this is a bug, which I fixed in https://github.com/kayak/pypika/pull/561/commits/d20e3aba2812eefea14cee3f9c14ee40848054a2
So the complexity you mention, does it refer to the changes in the first or second commit?

Some more thoughts:
from pypika import Table, Query
from datetime import date
from enum import Enum

class E(Enum):
    STR='foo'
    DATE=date.today()

t = Table('t')
q1 = Query().from_(t).select(t.col).where(t.col == E.STR)
q2 = Query().from_(t).select(t.col).where(t.col == E.STR)

print(q1)
# prints SELECT "col" FROM "t" WHERE "col"=foo
# expected SELECT "col" FROM "t" WHERE "col"='foo'

print(q2)
# prints SELECT "col" FROM "t" WHERE "col"=2021-03-11
# expected SELECT "col" FROM "t" WHERE "col"='2021-03-11'

With the solution provided in https://github.com/kayak/pypika/commit/145145434e8fd38db56cb64b36cfcea724164c3d the above script would print the expected results.
The solution you provided has a couple of issues. First of all, it is arguably more complex, since not everyone is aware of the behavior of __new__ and since you overwrite standard enum behavior in a significant way, I'd expect the application to break in other places. Also the solution has a serious flaw, because the first value would overwrite all other values, e.g.
class LiteralEnum(Enum):
    def __new__(cls, value):
            obj = object.__new__(cls)
            obj._value_ = LiteralValue(value)
            return obj

class F(LiteralEnum):
    foo='foo'
    bar='bar'
    baz='baz'

print(F.foo) # prints <F.foo: <pypika.terms.LiteralValue object at 0xABC>>
print(F.bar) # prints <F.foo: <pypika.terms.LiteralValue object at 0xABC>>
print(F.baz) # prints <F.foo: <pypika.terms.LiteralValue object at 0xABC>>

To make it work you'd either create your own Enum with EnumMeta or do something else, but I wouldn't consider it less complex.

The complexity I mention refers to the fact that you make a DatePart also inherit from str, just to support your use case. And DatePart would be the only enum in our codebase that would rely on that. Something I doubt anyone will find standard/intuitive. Nothing against how you've made the Enum value be evaluated recursively though.
That said, you have a fair point about my initial LiteralEnum implementation not rightly formatting non basic types (e.g. dates). That said, if you use ValueWrapper instead of LiteralValue, that would behave as expected. Regarding the overwriting of all other values that is definitely undesired. An alternative such as would be more appropriate:
from enum import Enum, DynamicClassAttribute

class ValueWrapperEnum(Enum):
   @DynamicClassAttribute
   def value(self):
      return ValueWrapper(self._value_)

So my suggestion for a custom Enum, which you would maintain in your code, still holds.

Ok great. I think then we are on the same page. My use case is the enum quoting (handled recursively). The DatePart thing I don't care about as much and I can remove it from the PR, but I genuinely think this is a bug and we can discuss about it in another issue.
The important change is https://github.com/kayak/pypika/commit/145145434e8fd38db56cb64b36cfcea724164c3d which I don't find too complex and I think is the 'more correct' behavior.


✨[Feature Request]: Enhancing Scroll Bar Appearance for Improved User Experience

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
The scroll bars on web pages or applications often have a standard appearance, which may not align with the overall design aesthetic or provide an engaging user experience. Enhancing the appearance of scroll bars can significantly contribute to improving the overall usability and attractiveness of the interface.
Use Case
Custom Design:
Implement custom-designed scroll bars that match the theme and style of the website or application.
Smooth Animation:
Add interactive hover effects to the scroll bars to provide visual feedback to users.
Responsive Design:
Ensure that the custom scroll bars are responsive and adapt well to different screen sizes and devices.
Benefits
By implementing these suggestions, we can enhance the appearance of scroll bars for improved user experience, creating interfaces that are both visually appealing and user-friendly. This enhancement would contribute to creating a more engaging and enjoyable browsing experience for our users.
Add ScreenShots

Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I have starred the repository

I'm excited about taking the lead on the RAPIDOC Healthcare Website project. With my proficiency in HTML, CSS, JavaScript, and ReactJS, I'm confident in my ability to drive significant progress on this initiative. Please assign me to this project via GSSOC.


Include eventgrid in CI for knack conversion

View a preview at https://prompt.ws/r/Azure/azure-cli/5057
This is an experimental preview for @microsoft.com users.
(It may take a minute or two for your instance to be ready)
Email feedback to 'azfeedback' with subject 'Prompt Feedback'.

The change was already made to .flake8. Also, I fixed the test_static.sh.


Enrich Dependency telemetry with optional request/response logging

Hi,
what we have found missing and would be absolutely useful to have is the ability to opt-in for logging request/response of the egress requests on demand (by means of some configuration switch). Logging request/response is an essential feature when debugging your distributed systems and Dependency telemetry makes a perfect home for that. Request and response as strings could be homed under dedicated properties of customDimensions.
I am cognizant it is most useful for text payloads, so it could apply only to selected content types such as application/json, or application/xml. Still, knowing those two cover quite a lot of the "integration market", the value proposition seems to be very compelling.

@przemos we store the request and response objects and are available in Telemetry Processors inside context parameter, you must be able to add your telemetry processor, read the context values and store whatever property is useful for you in the telemetry event.

The problem is though reading those streams are asynchronous, so you cannot make them onto Dependency Telemetry since these callbacks are unrelated


Web Feature Service Support (WFS)

Context
Add basic preliminary support for portions of the WFS 2.0.0 spec as defined here: http://www.opengeospatial.org/standards/wfs

Initial goal is to allow QGIS to download and interact with features stored in hecate.
Future goal is to support all or part of the WFS-T (Transactional) model to allow QGIS to natively support editing Hecate Datastores.

Progress

[ ]  Add support for GetCapabilities

[x] Define Data & Extent
[ ] Remove all unsupported operations, ensuring all capabilities claimed are supported
[ ] Read and expose metadata about data provider
[ ] Edit metadata via admin web ui

[x] Add support for DescribeFeatureType

[x] HecatePointData
[x] HecateMultiPointData
[x] HecateLineStringData
[x] HecateMultiLineStringData
[x] HecatePolygonData
[x] HecateMultiPolygonData

[x] Add support for GetFeature

[x] Version output
[x] Key output
[x] Arbitrary Properties
[x] Point Geometry
[x] MultiPoint Geometry
[x] LineString Geometry
[x] MultiLineString Geometry
[x] Polygon Geometry
[x] MultiPolygon Geometry

[ ] Compile and Test with OGC WFS Compliance Library: http://cite.opengeospatial.org/teamengine/about/wfs/2.0.0/site/

cc/ @ingalls

MultiPolygon geometries are now supported:

This is being worked on here: https://github.com/Hecate/Hecate/pull/9


Corrupted database where a document has 2 root revisions

Description
I don't know what happened, but I have a database where some documents are in a very weird state. Let's take one of those documents:
$ curl -s "http://couch:5984/cozyxxxxxxxxxxxxxxxxxxxxxxx%2Fio-cozy-files/78ca2b76808dd591f1b64f1f137bfe48?meta=true&revs=true&open_revs=all"
--41adad57f1b406a22332b1bc52b378c4
Content-Type: application/json

{"_id":"78ca2b76808dd591f1b64f1f137bfe48","_rev":"5-bc7fe0c9fec74c7d857d17e97121aebe","cozyMetadata":{"doctypeVersion":"1","metadataVersion":1,"createdAt":"2020-01-10T17:18:59.681880993Z","createdByApp":"cozy-desktop","createdByAppVersion":"3.17.0","updatedAt":"2020-01-10T17:20:02.966474161Z","createdOn":"https://xxxxxx.mycozy.cloud/"},"created_at":"2020-01-10T17:18:59Z","dir_id":"3ec8cdd199d7081a9361f46c22615721","name":"[REDACTED]","path":"/[REDACTED]","tags":[],"type":"directory","updated_at":"2020-01-10T17:18:59Z","_revisions":{"start":5,"ids":["bc7fe0c9fec74c7d857d17e97121aebe","ed6c725a3249ce90ce4155d0180d3c07","9e0c917a7719b181293c22207a54e195","cf252a1dfa81712e140c3b9b2fa25347","90d8ea315491928e8f3199360a0a48bd"]}}
--41adad57f1b406a22332b1bc52b378c4
Content-Type: application/json

{"_id":"78ca2b76808dd591f1b64f1f137bfe48","_rev":"11-9236dbe8f2baf8e5a1384fa64bd61545","_deleted":true,"_revisions":{"start":11,"ids":["9236dbe8f2baf8e5a1384fa64bd61545","62ceec92c6557ab036ec6a808dba8b8a","b5c87beae0e88912edcfab866d32fd6f","a0e1231615202ba37adb60179e8373d0","e7cadf01aae5cab26d71b6e7405f0e35","2a0151e2c632e15f7584d94ea2520449","bc7fe0c9fec74c7d857d17e97121aebe","ed6c725a3249ce90ce4155d0180d3c07","9e0c917a7719b181293c22207a54e195","cf252a1dfa81712e140c3b9b2fa25347","845faf29d2ab2d455c8f47948062676b"]}}
--41adad57f1b406a22332b1bc52b378c4--

CouchDB tells me that there is a conflict on this document, with 2 branches. The branch for 11-9236dbe8f2baf8e5a1384fa64bd61545 has lost the conflict, as it is marked as _deleted. And the other branch ends with 5-bc7fe0c9fec74c7d857d17e97121aebe.
But, when looking at the _revisions, we can see that 5-bc7fe0c9fec74c7d857d17e97121aebe is an ancestor of 11-9236dbe8f2baf8e5a1384fa64bd61545. So, there should be no conflict.
And, the really weird thing: both branches have the same revisions 5, 4, 3, and 2, but their first revisions are not the same: 90d8ea315491928e8f3199360a0a48bd and 845faf29d2ab2d455c8f47948062676b. I don't understand how the internal structures of CouchDB for storing the revisions tree can give us two roots.
By the way, I also got:
  "_revs_info": [
    {
      "rev": "5-bc7fe0c9fec74c7d857d17e97121aebe",
      "status": "missing"
    },

I think that this revision was compacted on some nodes of the cluster, but not on others.
Steps to Reproduce
I don't know how to reproduce. I understand that without a way to reproduce, it would be very hard to fix the bug. For the moment, I'd like to understand how it is possible that CouchDB sees two roots in a revision tree, and why a revision that is ancestor of another revision can be seen as a leaf.
Expected Behaviour
Well, first, I would have expected that CouchDB enforces that the revisions for a document are a tree. And, that a revision listed in _revisions for another revision cannot be seen as a leaf. And that leaf revisions cannot be missing (compacted).
Your Environment

CouchDB version used: 2.3.0
Operating system and version: Debian 9.11

{"couchdb":"Welcome","version":"2.3.0","git_sha":"07ea0c7","uuid":"b3ac19e755fb8720ec0be49b61086e87","features":["pluggable-storage-engines","scheduler"],"vendor":{"name":"The Apache Software Foundation"}}

Additional Context
To fix a document, we can go this way:

Add a new revision to the _deleted branch
Compact the database
Purge the old revisions
Delete again the document

But it's a manual operation. And it doesn't explain how we were in this situation.

Hiya @nono,
This looks like either something was creating its own revisions or there was an accidental copying of revisions between documents that were then inserted using new_edits=false. A subtlety of the tree is that the the revision identifiers only have to be unique at the node level. Generally they're unique to the tree unless we get into shenangians around using new_edits=false in which case the actual constraints of the tree are much looser than what normally happens. And unfortunately a lot of the traversal algorithms assume unique revisions so when you specify them for some operations you may not be getting the one you expect.
Your best bet would be to purge the 11- revision so that you're back to a linear history and then move on. In the future I'd avoid using new_edits=false in application code.
Paul


Virtual Desktops

I would like virtual desktops to be added.
Each virtual desktop would be a parent to a set of workspaces.
I have 6 monitors so a considerable amount of workspaces are already used up, I would like to have an independent and separate “workspace 1” on both desktop 1,2 and …
Maybe default key binds for desktops could be mod+Ctrl+1-0
edit>
or mod+Ctrl+pgup/dn
Moving windows between desktops could be mod+Ctrl+shift+1-0
And similar to using arrow keys for quick navigation and moving windows you could have pgup and pgdn round robin through the desktops
With mod+Ctrl+shift+pgup/dn to quickly move windows
</edit
If you’re worried it’d be too confusing or complicated for most users and would cause them to lose windows just disable it with a simple true false flag in the config by default

I looked up Hyprsome  and it’s not quite the functionality I’m looking for, it’s emulating awesome WM and using each monitor as a parent to a set of workspaces.  But I do also think that it would be valuable to have this type of functionality natively implemented rather than relying on, possibly findable mods in add-ons that may or may not continue to be maintained throughout the life of the window manager

"I’m a big dumb dumb with coding" is not a reason to expect a feature to be added.
I am not planning on adding this as a core feature - it's a method of managing workspaces Hyprland was not made for, and will not be.
It is easily scriptable, and Hyprsome is just an example of the fact that you can manage workspaces with scripts. IIRC someone already made it into a plugin if the relatively slower speed of scripts is an issue somehow.
The point of the scripting API and plugins is exactly this - obscure or lesser used features.

Maybe I’m not just a dummy with coding but the only plugins I could find were the ones made by you in the official repo.
please don’t be offended but perhaps a donation of monetary value could be made to ease the burden of implementing such an “obscure” feature


Fix block indentation

This pull request updates how a handful of blocks are indented to line up with the indentation of the line that contains the starting begin.

Closing as inactive. Feel free to reopen and merge. :)


kcl: 0.10.0 -> 0.10.9

Updating version of kcl from version 0.10.0 to version 0.10.9

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[x] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[x] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Duplicated. Please review the already opened PR:
https://github.com/NixOS/nixpkgs/pull/353108

Duplicate of #353108


[BUG]: After creating a sketch on an existing model face, sketch ends up on wrong plane, produces internal error

Describe the bug
If I select an existing face on a model, for example a face of the example shelf bracket, and then create a simple line sketch on that face, then exit the sketch, I see that the polygon sketch I created has been place on the XY plane instead of the face, and also there's an internal error showing in the code view.
Steps to Reproduce

Open the existing shelf bracket model
click sketch
select a planar face of the shelf bracket
sketch a simple polygon
exit sketch
notice location of sketch (not on bracket face), and  internal error showing in code view

Expected Behavior
I expected that the sketch will be on the chosen face
Screenshots and Recordings
Screencast from 2024-05-24 16-45-15.webm
Desktop OS
Fedora 39
Browser
Firefox 126.0
Version
0.21.9
Additional Context
No response

Work-around for now is to comment out the revolve() call, edit the sketch, then uncomment it again.

Yeah revolve hasn’t been pulled thru to click and point yet, you can track what is pulled thru where here https://github.com/KittyCAD/modeling-app/issues/729

Yeah revolve hasn’t been pulled thru to click and point yet, you can track what is pulled thru where here #729

I think this comment may be on the wrong issue.  There's no revolve in this example.

im sorry it was! i moved it!

hmm I cant tell if this is engine side or not but its curious, the other annoying thing is did it not zoom you automatically on click to the face when you said you wanted to sketch on it?

i opened a seperate issue for the zoom thing, its giving "this this a sketch for ants" vibes

I assigned @Irev-Dev only to rule out the front end selecting the wrong face? but this could also be kcl, or even engine

hmm I cant tell if this is engine side or not but its curious

Back in the day before we had sketches on non-XY planes working, when we would try to sketch on XZ it would successfully sketch but then render on the XY plane. This looks similar to me, that something like the face ID is invalid or missing, so when we exit sketch mode and submit it to the engine it quietly fails and bails out to rendering the sketch as if on the XY plane.

if i get rid of the fillets it works, this is an order of operations thing we need to do the fillets last in the executor since they eat ids.

related to https://github.com/KittyCAD/modeling-app/issues/2227


Flipstogram headers don't have '?' next to heading

"User Power", "Top Hashtags", "Top Sites" don't have the '?' next to the heading on staging, but they do on production

Disregard, opened on the wrong repo


Add dockerfile configuration and instructions of use

Added docker configuration to run the application. fixes #4
ps: kindly evaluate and please tag the labels for hacktoberfest, thank u :P

how you run the compose, following the instructions in the README? Seems you don't have permissions to the directory.
https://user-images.githubusercontent.com/20842252/195617611-347bb45f-30c1-4705-bdf8-74379798c615.mp4

Sorry for taking some time to answer @rodgeraraujo.
Yes i ran exactly as expected.

As you can see the user inside the container can't do anything. I belive it works for you because the UID e GID used are both the same of the user in your machine

Sorry for taking some time to answer @rodgeraraujo. Yes i ran exactly as expected.
 As you can see the user inside the container can't do anything. I belive it works for you because the UID e GID used are both the same of the user in your machine

I will try to check this.

Can you try test again @christianfds? I remove the non root user from the Dockerfile

Nice, now its running as expected, thank you


[cljs] Adding ClojureScript support

Minor tweaks necessary to add ClojureScript support.
Possibly not the best approach ever, but should meet minimum expected requirements.

(also note that the travis check here has failed because travis is incorrectly inferring that this is a ruby project)

Thanks for this! I assume you have run the tests locally with these changes. I'll work on setting up Travis correctly.

Can you merge master into this? Travis should be set up correctly now, and I did some basic cljc conversion without your specific code fixes.

Bleh, I just pushed to my branch with an old version of this from the wrong machine. Don't merge this; it needs to be cleaned up with the source on my machine at home.

PR is now up to date, though I'd like clarification on whether you really want str over the original pr-str you had.

Changes look good to me! Curious what you think about the str/pr-str switch.

Feel free to merge whenever you want. I don't know how you're running the ClojureScript tests though.

(I tried lein cljsbuild test and it told me it couldn't locate the doo.runner namespace)

You can run them with lein doo [rhino|nashorn|phantom] test once.

Ah, great. In that case we're all good here boss :)

Thanks @venantius

Changes released with 1.1.0.