[md:error] (13)Permission denied: AH10056: processing {DOMAIN}

I have been using mod_md for a few months without issues. I have a handful of managed domains and the first one is up for renewal. Apache is throwing the following error:
[md:error] (13)Permission denied: AH10056: processing {DOMAIN}
I researched this error but found issues where other error messages accompanied this one. This is the only error being thrown. I ran a LogLevel md:trace1 and the output is below:
[Fri Mar 15 20:02:31 2019] [mpm_event:notice] AH00492: caught SIGWINCH, shutting down gracefully
[Fri Mar 15 20:02:34 2019] [md:debug] mod_md.c(1013): AH10070: initializing post config dry run
[Fri Mar 15 20:02:34 2019] [md:debug] mod_md.c(361): AH10037: server seems reachable via http: (port 80->80) and reachable via https: (port 443->443)
[Fri Mar 15 20:02:34 2019] [md:debug] mod_md.c(221): AH10041: Server {DOMAIN}:0 matches md {DOMAIN} (config {DOMAIN}[default, default])
[Fri Mar 15 20:02:34 2019] [md:debug] mod_md.c(251): AH10043: Managed Domain {DOMAIN} applies to vhost {DOMAIN}:0
[Fri Mar 15 20:02:34 2019] [md:debug] mod_md.c(221): AH10041: Server {DOMAIN}:0 matches md {DOMAIN} (config {DOMAIN}[default, default])
[Fri Mar 15 20:02:34 2019] [md:debug] mod_md.c(251): AH10043: Managed Domain {DOMAIN} applies to vhost {DOMAIN}:0
[Fri Mar 15 20:02:34 2019] [md:debug] mod_md.c(281): AH10044: {DOMAIN}: added contact mailto:{EMAIL}
[Fri Mar 15 20:02:34 2019] [md:debug] mod_md.c(392): AH10039: Completed MD[{DOMAIN}, CA=https://acme-v01.api.letsencrypt.org/directory, Proto=ACME, Agreement=https://letsencrypt.org/documents/LE-SA-v1.2-November-15-2017.pdf, Drive=1, renew=2592000000000]
[Fri Mar 15 20:02:34 2019] [md:debug] md_reg.c(793): {DOMAIN}: update renew norm=7776000000000, window=2592000000000
[Fri Mar 15 20:02:34 2019] [md:debug] md_reg.c(245): md{{DOMAIN}}: is complete
[Fri Mar 15 20:02:34 2019] [md:debug] md_reg.c(488): update md {DOMAIN}
[Fri Mar 15 20:02:34 2019] [md:trace1] md_reg.c(528): update renew-window: {DOMAIN}
[Fri Mar 15 20:02:34 2019] [md:trace1] md_reg.c(549): update transitive: {DOMAIN}
[Fri Mar 15 20:02:34 2019] [md:debug] md_reg.c(245): md{{DOMAIN}}: is complete
[Fri Mar 15 20:02:34 2019] [md:debug] md_reg.c(830): md {DOMAIN} updated
[Fri Mar 15 20:02:34 2019] [md:debug] md_reg.c(245): md{{DOMAIN}}: is complete
[Fri Mar 15 20:02:34 2019] [md:info] AH10071: mod_md (v1.1.17), initializing...
[Fri Mar 15 20:02:34 2019] [md:debug] mod_md.c(361): AH10037: server seems reachable via http: (port 80->80) and reachable via https: (port 443->443)
[Fri Mar 15 20:02:34 2019] [md:debug] mod_md.c(221): AH10041: Server {DOMAIN}:0 matches md {DOMAIN} (config {DOMAIN}[default, default])
[Fri Mar 15 20:02:34 2019] [md:debug] mod_md.c(251): AH10043: Managed Domain {DOMAIN} applies to vhost {DOMAIN}:0
[Fri Mar 15 20:02:34 2019] [md:debug] mod_md.c(221): AH10041: Server {DOMAIN}:0 matches md {DOMAIN} (config {DOMAIN}[default, default])
[Fri Mar 15 20:02:34 2019] [md:debug] mod_md.c(251): AH10043: Managed Domain {DOMAIN} applies to vhost {DOMAIN}:0
[Fri Mar 15 20:02:34 2019] [md:debug] mod_md.c(281): AH10044: {DOMAIN}: added contact mailto:{EMAIL}
[Fri Mar 15 20:02:34 2019] [md:debug] mod_md.c(392): AH10039: Completed MD[{DOMAIN}, CA=https://acme-v01.api.letsencrypt.org/directory, Proto=ACME, Agreement=https://letsencrypt.org/documents/LE-SA-v1.2-November-15-2017.pdf, Drive=1, renew=2592000000000]
[Fri Mar 15 20:02:34 2019] [md:debug] md_reg.c(793): {DOMAIN}: update renew norm=7776000000000, window=2592000000000
[Fri Mar 15 20:02:34 2019] [md:debug] md_reg.c(245): md{{DOMAIN}}: is complete
[Fri Mar 15 20:02:34 2019] [md:debug] md_reg.c(488): update md {DOMAIN}
[Fri Mar 15 20:02:34 2019] [md:trace1] md_reg.c(528): update renew-window: {DOMAIN}
[Fri Mar 15 20:02:34 2019] [md:trace1] md_reg.c(549): update transitive: {DOMAIN}
[Fri Mar 15 20:02:34 2019] [md:debug] md_reg.c(245): md{{DOMAIN}}: is complete
[Fri Mar 15 20:02:34 2019] [md:debug] md_reg.c(830): md {DOMAIN} updated
[Fri Mar 15 20:02:34 2019] [md:debug] md_reg.c(245): md{{DOMAIN}}: is complete
[Fri Mar 15 20:02:34 2019] [md:trace1] md_acme_drive.c(671): {DOMAIN}: init driver
[Fri Mar 15 20:02:34 2019] [md:debug] md_reg.c(974): {DOMAIN}: run load
[Fri Mar 15 20:02:34 2019] [md:debug] md_acme_drive.c(926): {DOMAIN}: preload start
[Fri Mar 15 20:02:34 2019] [md:debug] md_acme_drive.c(941): (2)No such file or directory: {DOMAIN}: loading staging private key
[Fri Mar 15 20:02:34 2019] [md:debug] md_acme_drive.c(1010): (2)No such file or directory: {DOMAIN}: ACME, ACME preload
[Fri Mar 15 20:02:34 2019] [md:debug] md_reg.c(996): (2)No such file or directory: {DOMAIN}: load done
[Fri Mar 15 20:02:34 2019] [md:debug] md_reg.c(245): md{{DOMAIN}}: is complete
[Fri Mar 15 20:02:34 2019] [md:debug] mod_md.c(927): AH10064: md({DOMAIN}): state=2, driving
[Fri Mar 15 20:02:34 2019] [md:debug] md_store_fs.c(688): purge staging/{DOMAIN} (/WAMP/apache/md/staging/{DOMAIN})
[Fri Mar 15 20:02:34 2019] [md:debug] md_store_fs.c(688): (2)No such file or directory: purge challenges/{DOMAIN} (/WAMP/apache/md/challenges/{DOMAIN})
[Fri Mar 15 20:02:34 2019] [md:debug] mod_md.c(959): AH10067: register md watchdog(_md_)
[Fri Mar 15 20:02:34 2019] [md:debug] md_reg.c(245): md{{DOMAIN}}: is complete
[Fri Mar 15 20:02:34 2019] [mpm_event:notice] AH00489: Apache/2.4.38 (Unix) OpenSSL/1.1.1 configured -- resuming normal operations
[Fri Mar 15 20:02:34 2019] [core:notice] AH00094: Command line: '/WAMP/apache/bin/httpd -D PROD'
[Fri Mar 15 20:02:34 2019] [md:debug] mod_md.c(749): AH10054: md watchdog start, auto drive 3 mds
[Fri Mar 15 20:02:34 2019] [md:debug] mod_md.c(761): AH10055: md watchdog run, auto drive 3 mds
[Fri Mar 15 20:02:34 2019] [md:debug] mod_md.c(690): AH10052: md({DOMAIN}): state=2, driving
[Fri Mar 15 20:02:34 2019] [md:trace1] md_acme_drive.c(671): {DOMAIN}: init driver
[Fri Mar 15 20:02:34 2019] [md:debug] md_reg.c(902): {DOMAIN}: run staging
[Fri Mar 15 20:02:34 2019] [md:debug] md_acme_drive.c(687): {DOMAIN}: staging started, state=2, can_http=1, can_https=1, challenges='http-01 tls-sni-01'
[Fri Mar 15 20:02:34 2019] [md:trace1] md_acme_drive.c(705): {DOMAIN}: checked staging area, will reset
[Fri Mar 15 20:02:34 2019] [md:debug] md_store_fs.c(688): (2)No such file or directory: purge staging/{DOMAIN} (/WAMP/apache/md/staging/{DOMAIN})
[Fri Mar 15 20:02:34 2019] [md:debug] md_acme.c(145): get directory from https://acme-v01.api.letsencrypt.org/directory
[Fri Mar 15 20:02:34 2019] [md:trace1] md_acme.c(488): add acme GET: https://acme-v01.api.letsencrypt.org/directory
[Fri Mar 15 20:02:34 2019] [md:debug] md_acme.c(422): req: POST https://acme-v01.api.letsencrypt.org/directory
[Fri Mar 15 20:02:34 2019] [md:trace1] md_curl.c(239): request 0 --> GET https://acme-v01.api.letsencrypt.org/directory
[Fri Mar 15 20:02:35 2019] [md:trace1] md_curl.c(255): request 0 <-- 200
[Fri Mar 15 20:02:35 2019] [md:trace1] md_acme.c(331): response: 200
[Fri Mar 15 20:02:35 2019] [md:trace2] md_acme.c(342): response: {\n  "Txe5rG-uWMc": "https://community.letsencrypt.org/t/adding-random-entries-to-the-directory/33417",\n  "key-change": "https://acme-v01.api.letsencrypt.org/acme/key-change",\n  "meta": {\n    "caaIdentities": [\n      "letsencrypt.org"\n    ],\n    "terms-of-service": "https://letsencrypt.org/documents/LE-SA-v1.2-November-15-2017.pdf",\n    "website": "https://letsencrypt.org"\n  },\n  "new-authz": "https://acme-v01.api.letsencrypt.org/acme/new-authz",\n  "new-cert": "https://acme-v01.api.letsencrypt.org/acme/new-cert",\n  "new-reg": "https://acme-v01.api.letsencrypt.org/acme/new-reg",\n  "revoke-cert": "https://acme-v01.api.letsencrypt.org/acme/revoke-cert"\n}
[Fri Mar 15 20:02:35 2019] [md:debug] md_acme.c(440): req sent
[Fri Mar 15 20:02:35 2019] [md:info] {DOMAIN}: setup staging
[Fri Mar 15 20:02:35 2019] [md:debug] md_store_fs.c(688): (2)No such file or directory: purge staging/{DOMAIN} (/WAMP/apache/md/staging/{DOMAIN})
[Fri Mar 15 20:02:35 2019] [md:debug] md_acme_drive.c(757): {DOMAIN}: save staged md
[Fri Mar 15 20:02:35 2019] [md:info] {DOMAIN}: need certificate
[Fri Mar 15 20:02:35 2019] [md:debug] md_acme_drive.c(95): re-use account 'ACME-.letsencrypt.org-0000'
[Fri Mar 15 20:02:35 2019] [md:debug] md_acme_acct.c(192): (13)Permission denied: error reading account: ACME-.letsencrypt.org-0000
[Fri Mar 15 20:02:35 2019] [md:debug] md_acme_drive.c(909): (13)Permission denied: {DOMAIN}: ACME, choose account
[Fri Mar 15 20:02:35 2019] [md:debug] md_reg.c(909): (13)Permission denied: {DOMAIN}: staging done
[Fri Mar 15 20:02:35 2019] [md:error] (13)Permission denied: AH10056: processing {DOMAIN}
[Fri Mar 15 20:02:35 2019] [md:info] AH10057: {DOMAIN}: encountered error for the 13. time, next run in  1:00:00 hours
[Fri Mar 15 20:02:35 2019] [md:trace1] mod_md.c(730): {DOMAIN}: saving job props
[Fri Mar 15 20:02:35 2019] [md:debug] mod_md.c(783): AH10107: next run in  0:59:59 hours

Any help would be appreciated.

Here is a summary of directory and file permissions:

Path
Permission

md/accounts
rwxr-xr-x

md/accounts/ACME-.letsencrypt.org-0000
rwxr-xr-x

md/accounts/ACME-.letsencrypt.org-0000/account.json
rw-r----

md/accounts/ACME-.letsencrypt.org-0000/account.pem
rw-r----

I changed account.json and account.pem to rw-r--r-- and the certificate was successfully renewed:
[md:notice] AH10051: {DOMAIN}: has been renewed successfully and should be activated at Sun, 17 Mar 2019 00:11:27 GMT (this requires a server restart latest in 22:59:58 hours)
So the remaining question is why were the perms wrong to begin with?

Thanks for the detailed report and analysis. Will look at it on Monday. mod_md needs some sort of fix to accomodate for such umask settings, I‘d say.

Am 16.03.2019 um 07:19 schrieb Jerry Martinez<EMAIL_ADDRESS>I believe I found the culprit.
In my /etc/init.d/ startup script I have the following line immediately before calling apachectl:
umask 007
I can't remember why but that mask has been there for ages. @icing, can (and should) mod_md break the mask and force file permissions? Or, can (and should) mod_md assign a different owner/group just like it does for the md/challenges and md/staging directories?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

My test suite will not catch this as it does not run as root and httpd only switches users then.
I committed a change that hopefully addresses this issue and sets the file permissions explicitly. Are you able to clone the current master here, build and verify easily? I could also apply the change to the Apache subversion tree in case you want to avoid all the new things here.

Thanks for fixing this! As the readme states, patching mod_ssl is not my cup of tea. I would much rather run mod_md that is bundled with the Apache distro. I am currently running 2.4.38. What version will receive your fix, 2.4.39? Also, what permissions should I set to the existing managed domains?
Thanks again!

Made you a v1.1.18 for testing.

I downloaded 1.1.18, unzipped it on the server and ran the following:
./configure.ac --with-apxs=/WAMP/apache/bin/apxs --enable-werror
Then, the following error was thrown:
./configure.ac: line 16: syntax error near unexpected token `[2.69]'
./configure.ac: line 16: `AC_PREREQ([2.69])'

A few things to note:

Don't mind the reference to WAMP. Its actually running on CentOS.
./configure did not work as written in the 2.4x installation section of the Wiki. So, I changed it to ./configure.ac.

The configure.ac is the file for autoconf to generate the ./configure among other things. You cannot run it directly.
But autoconf/automake is not the lightest of topics. You can just take the *.c and *.h files from src, copy them into your 2.4.38 source at modules/mdand build and install.

mod_md 1.1.18 has been compiled as you suggested. Now, how do I test?

Hmm, assuming you do not want to interrupt you working domains...take a another domain or subdomain and configure the staging environment of Lets Encrypt, like
<MDomainSet blabla.your-domain>
  MDDriveMode always
  MDCertificateAuthority https://acme-staging.api.letsencrypt.org/directory
</MDomainSet>

If you have no staging account yet, this should create a new one with the right permissions. If you have one, move it aside temporarily (or just remove it). A staging account should how in its JSON:
    "url": "https://acme-staging.api.letsencrypt.org/acme/reg/NNNNN"

where NNNNN is some number.
Hope this helps.

I followed your directions and it appears the permissions are still not being set correctly. Here is what I did:

Added a new subdomain to my public DNS (test.MYDOMAIN.COM)
Added the following to my main server config

<MDomainSet test.MYDOMAIN.COM>
  MDDriveMode always
  MDCertificateAuthority https://acme-staging.api.letsencrypt.org/directory
</MDomainSet>

Executed /etc/init.d/apache graceful two times
Observed the following permissions in the new /accounts/ directory (same as before):

Path
Permission
Owner/Group

md/accounts
rwxr-xr-x
root/root

md/accounts/ACME-.letsencrypt.org-0003
rwxr-xr-x
root/root

md/accounts/ACME-.letsencrypt.org-0003/account.json
rw-r----
root/root

md/accounts/ACME-.letsencrypt.org-0003/account.pem
rw-r----
root/root

Wouldn't it be better to just change the group/owner just as done for /challenges and /staging?

No, the files really belong to the one starting the server and should be readable by everyone.
I made v1.1.19 with more permission setting goodness. Could you give this a try? (You can just remove all staging related information in the store and start over) Thanks!

Good job - that did the trick! Now, what httpd release will this patch be included?

We are about to tag, I think. So, it will be too late for that. I will bring it into the one after that.


Improve cacheability of .zipline files

We’re currently caching .zipline files that start out as .js files produced by the Kotlin/JS compiler.
Unused symbols in these .js files are unconditionally pruned via doStaticMembersLowering() in IrModuleToJsTransformerTmp.kt.
Two bad things come of this:

If we introduce or remove the only call to a library function, that changes the generated .js for that library and causes it to be rebuilt.
Two applications generally can’t share generated code.

It’s theoretically (but not practically) possible to prevent this behavior by supplying an exhaustive list of symbols to the -Xir-keep function. A better solution would be a change to the Kotlin/JS compiler to add an option that disables this lowering step. In practice such an option would change Keeper.shouldKeep() to unconditionally return true.

https://youtrack.jetbrains.com/issue/KT-54159/KotlinJS-Compiler-option-like-Xir-keep-everything

No action to take on this.


feat(cli): pretty-print cargo loco routes

This add cleaner formatting to the cargo loco routes command.

Thank you, @AngelOnFira, for this PR!
We aim to minimize the number of external crates to reduce the binary size and compilation time.
If you can think of an alternative implementation that doesn’t rely on an external crate, that would be fantastic. Looking forward to your thoughts!

Thanks for the quick reply! I mainly wanted to just give this a test first with the dependency, but I can definitely slim it down to not use anything external. I'll ping you once I get that in order!

Alright, I think I'm happy with this version

I think ordering could be discussed if it's not the best, since seeing GET, POST, GET, POST, DELETE might seem out of order, but it's due to it being the same endpoint used by multiple request types. I tried to separate that visually as well as I could.

This should be ready now @kaplanelad! 🦀

@AngelOnFira this is beautiful, thanks!

Thanks, @AngelOnFira, it looks much better! The event from the table is also great! :)
Could you please take a look at my comment and also address the CI issue?
By the way, we have a few more commands (beyond prints) that could benefit from a design update:

Scheduler: cargo loco scheduler --list
Tasks: cargo loco task
For testing, head over to examples/demo and run the following command.

We’d really appreciate it if you could open another PR (no need in this PR) to apply your magic to these as well!

beautiful! merging!


Help with problem SCRCPY

System: Win10 22H2
Android 9 (Samsung A8 2018)

Do you use the official zip release? It should use the dll from the local folder, but instead it attempts to use FFmpeg dlls from your system. Did you install FFmpeg separately?


When using Misa Texture Pack it consumes all the RAM on the computer until it crashes

Describe the bug
It runs fine on vanilla texture pack, If i add the texture pack that i use "Misa 64x" https://www.patreon.com/file?h=75386242&i=12445894 it consumes all the ram on the computer, I allocated 4GB of RAM, and my computer have 32GB.
That does happen on the 1.19.2 and 1.19 too, that does not happen on normal fabric instance or vanilla, Only on fabulously Optimized ones.
Tested on 1.18.2 and it works fine.
Here is the log:
https://paste.ee/p/NOvL3

Using the Modrinth version on MultiMC.
Modpack version
4.6.0 alpha 12
Launcher
MultiMC
Other things

[X] I updated FO to a newer version (mention, what version to what version)
[ ] I added/removed some mods or resource packs (mention, which ones)

Additional context
No response

since it's a high res RP try with 6GB of ram instead
+ this RP does seem to require very strict OF features
and in addition, this pack uses broken path which is a very bad thing
i think it can't even work on 1.19.3 FO due to missing required features

I set 6GB on Allocation, but it does NOT matter, It still consumes ALL my RAM. I mean every single megabyte until it crashes, for some reason the memory allocation/limit is not being respected if I enable this resource pack on this mod pack.

as i said due to missing features in FO 1.19.3 (which is alpha) this RP can't work currently

I don't think this is quite what is meant to happen; What the OP is referring is that FO has a possibility of causing actual memory leaks when using the resource pack, and yet there is no concrete evidence of what causes that to happen out of thin air.

I don't think this is quite what is meant to happen; What the OP is referring is that FO has a possibility of causing actual memory leaks when using the resource pack, and yet there is no concrete evidence of what causes that to happen out of thin air.

what i'm saying is that what happen is expected since every required feature to correctly load this pack isn't present and by so this modpack has problems loading which causes OoM

Well if it truly that then it would be resource pack creator's issue and not this, But if it was FO's alpha build then the only question i can throw out is: Does 4.5.5 fix anything?

Well if it is truly that then it would be resource pack creator's issue and not this, But if it was FO's alpha build then the only question i can throw out is: Does 4.5.5 fix anything?

he said 1.18.2 work fine

Well if it is truly that then it would be resource pack creator's issue and not this, But if it was FO's alpha build then the only question i can throw out is: Does 4.5.5 fix anything?

he said 1.18.2 work fine

Not even 4.5.5 works?!, Now i am actually curious to see where the problem really lays at.

Well if it is truly that then it would be resource pack creator's issue and not this, But if it was FO's alpha build then the only question i can throw out is: Does 4.5.5 fix anything?

he said 1.18.2 work fine

Not even 4.5.5 works?!, Now i am actually curious to see where the problem really lays at.

It runs fine on vanilla texture pack, If i add the texture pack that i use "Misa 64x" https://www.patreon.com/file?h=75386242&i=12445894 it consumes all the ram on the computer, I allocated 4GB of RAM, and my computer have 32GB.
That does happen on the 1.19.2 and 1.19 too, that does not happen on normal fabric instance or vanilla, Only on fabulously Optimized ones.

Tested on 1.18.2 and it works fine.

Well if it is truly that then it would be resource pack creator's issue and not this, But if it was FO's alpha build then the only question i can throw out is: Does 4.5.5 fix anything?

he said 1.18.2 work fine

Not even 4.5.5 works?!, Now i am actually curious to see where the problem really lays at.

It runs fine on vanilla texture pack, If i add the texture pack that i use "Misa 64x" patreon.com/file?h=75386242&i=12445894 it consumes all the ram on the computer, I allocated 4GB of RAM, and my computer have 32GB.
That does happen on the 1.19.2 and 1.19 too, that does not happen on normal fabric instance or vanilla, Only on fabulously Optimized ones.

Tested on 1.18.2 and it works fine.

That is not what i am referring to, I was asking about 4.5.5 which is 1.19.2 itself; Not the alpha and not 1.18.2, Please re-read my comment one more time just to be sure.

wait sry i'm f blind

work fine on FO 1.19.2
i just tested

Then from what i can tell; Either the OP's java arguments are doing weird shenanigans or the alpha build has issues working properly with high-resolution packs at the moment.

To me it does not work on 1.19.2: https://paste.ee/p/f8kkH

ok wait
it seems to crash half of the time on pure FO
i got it running once but now it crash

it seems like with my modified FO i can get it running consistently tho

Can you provide the mods you have used to get it to run?

it uses 10GB on 4 allocated but at least it work XD

wait i have a F idea it may be due to the java arg i'm using to force the game to not crash when i encounter an error with the nvidia drivers

ok yes

Cannot reproduce (specs here):

use the arg
-XX:-CriticalJNINatives
in your java args to force the game to not crash

Cannot reproduce (specs here):

i can

I have used JDK 19.0.1 with the shenandoahgc set and it works fine, guessing G1GC / default java arguments bombs it?

if i clean the memory with the system management app from my pc, the ram is able to stay within limits
it just go to 10GB when loading

take note that the java arg i provided don't work with the vanilla launcher

That is because the vanilla launcher is known for bricking newer java installations as the javacheck.jar program is badly programmed by Mojang themselves, This can be checked upon in MCL-18306.

So, to recap, to use this pack you must use this java arg -XX:-CriticalJNINatives and expect the game to go to 10GB when loading
if you have an app like this by example, you can use it to clear the memory and it'll go down to a normal amount and stay like that

I see this as in being a morely hacky method than anything virtually fixable in practice and should be furtherly checked upon - Worst case scenario would be that windows in general has terrible memory management in first place if valid.

I see this as in being a morely hacky method than anything virtually fixable in practice and should be furtherly checked upon - Worst case scenario would be that windows in general has terrible memory management in first place if valid.

this is an hacky method yes but the RP seems to have a LOT of issues of missing parts and also has very bad things like wrong number of tiles for CTM, bad naming scheme (broken paths), etc

this issue come from the pack creator not doing things properly which end up causing issues with FO
i tested with 1.19.3 and this method work too

little info of why i know this ARG
(just so you know, i use and know this arg because NVIDIA drivers recents updates are so bad that they introduced a lot of crash bugs and BSoD that i have to force the game to not crahs)

What i can confirm for sure that the issue is with Fabulously Optimized +this texture pack "Misa 64x 1.19". I tested Clarity, FaithfulHDx512 and Epic Adventures, all worked fine, Maybe @Julienraptor01 is right and there is a lot of wrong things on this texture pack, I don't know, I don't understand how a texture pack is made.
I don't use any custom java args, only the defaults from MultiMC, and even if you managed to it to work, Using 10GB when you say to use only 4GB confirms the memory leak.
Maybe the issue is the size of the texture pack, Even the 512x is 27MB while Misa is 161MB. Misa is very rich, have a lot of Custom Mob Models.
The texture pack version of the 1.18.2 is a different file than 1.19+.
https://mega.nz/file/pt8hgSaK#XWH3dKAnk62BpErY2M3bGyo2ojMtnWk_9lXYph-fKe4
Maybe there is something new on the texture pack or maybe a new mod or an updated mod is the issue.
I don't know, But the texture pack should work here, It works on 1.18.2 and Vanilla, Optifine or Standard Fabric (Non Mod Pack).
If you guys managed to fix it, would be great, if not, well, thanks anyway.

What i can confirm for sure that the issue is with Fabulously Optimized +this texture pack "Misa 64x 1.19". I tested Clarity, FaithfulHDx512 and Epic Adventures, all worked fine, Maybe @Julienraptor01 is right and there is a lot of wrong things on this texture pack, I don't know, I don't understand how a texture pack is made.
I don't use any custom java args, only the defaults from MultiMC, and even if you managed to it to work, Using 10GB when you say to use only 4GB confirms the memory leak.
Maybe the issue is the size of the texture pack, Even the 512x is 27MB while Misa is 161MB. Misa is very rich, have a lot of Custom Mob Models.
The texture pack version of the 1.18.2 is a different file than 1.19+. https://mega.nz/file/pt8hgSaK#XWH3dKAnk62BpErY2M3bGyo2ojMtnWk_9lXYph-fKe4
Maybe there is something new on the texture pack or maybe a new mod or an updated mod is the issue. I don't know, But the texture pack should work here, It works on 1.18.2 and Vanilla, Optifine or Standard Fabric (Non Mod Pack).

what do you mean standard fabric ? fabric but whit no mods loaded ?
(it surely work on OF because OF has support for a lot of broken thing and it work on vanilla because vanilla doesn't try to load OF features
it's broken here because FO has all the mods to support proper non broken OF features and this RP use broken features that OF support)
TL;DR says to the creator to fix the RP and if he does that it should work properly too

If you guys managed to fix it, would be great, if not, well, thanks anyway.

the "leak" only come from the RP being broken i think
it isnt really a leak and more like this RP does need 10GB of RAM, aka if you put 12GB of RAM, the game will use 10 and not be OoM
you can add the java arg i provided here like this

to temporarily fix the issue but it would be better if the pack was fixed by its creator instead
as i said if you then use a tool to clear the system memorey (mine is provided by my pc manufacturer) you can clear the memory once the game is loaded and it'll stay at a normal amount

Lack of response, so I presume this is fixed.

Nope, not fixed. Didn't said anything because there was nothing i could contribute with. The response above is very hacky workaround not a definite, good fix.

Nope, not fixed. Didn't said anything because there was nothing i could contribute with. The response above is very hacky workaround not a definite, good fix.

did you report to the RP creator that the pack has many problems in itself ? because i think it's actually the biggest source of problems i think

No i didn't, What is EXACTLY the problems with this pack? What is broken paths?

No i didn't, What is EXACTLY the problems with this pack? What is broken paths?

Broken path is when you use characters that aren't allowed to exist.
The game don't support them in vanilla, but for some reason OptiFine decided it would be a good idea to add support for it ! Except that it tend to break and that some OF parity mods have a very hard time to support it so it cause even more problems in fabric

Legal characters :
Namespaces, paths and other folder and file names in the resource/data pack should only contain the following symbols:
0123456789 Numbers
abcdefghijklmnopqrstuvwxyz Lowercase letters
_ Underscore
- Hyphen/minus
/ Forward Slash/Directory separator (Can't be used in namespace)
. Period

The preferred naming convention is lower_case_with_underscores, called lower snake case.

and i also noted other problems that i mentioned here

https://github.com/Fabulously-Optimized/fabulously-optimized/issues/554#issuecomment-1364726772
this is an hacky method yes but the RP seems to have a LOT of issues of missing parts and also has very bad things like wrong number of tiles for CTM, bad naming scheme (broken paths), etc

from what i said up there the RP sometimes is missing some files or have a wrong number of files mentioned in properties files which surely induce even more problems


[labs/react] Custom element property detection doesn't match React 19

Which package(s) are affected?
React (@lit-labs/react)
Description
React 19's custom element support does an in check on a component instance, after creating it, and without any filtering of properties in HTMLElement.prototype.
We should try to match this behavior as closely as we can.
Reproduction
n/a
Workaround
n/a
Is this a regression?
No or unsure. This never worked, or I haven't tried before.
Affected versions
all
Browser/OS/Node environment
all

See this table that we can use to derive tests: https://josepharhar.github.io/react-custom-elements/

@justinfagnani would this be covered in the recent #3128 submission?

Closing with #3128 submission.
Can always reopen if behavior does not match React 19


SunnyValley.php under src/script/firmware/repos folder. This folder's…

… owner is opnsense core. Goal is, if zenarmor installed on opnsense, set to repo link with nodeuuid.

Merged, thanks!

@ureyni 993a69436a8f should improve resilience a little more and clean up unused bits
if you want this current state released in 23.7.12 please let me know until Monday.


Vue3 kebab-case events.

hello! I hope you are well!
how did you solve the problem of vue3 with the events in camelCase from stencil https://github.com/ionic-team/stencil/issues/2804?
I'm trying not to use defineCustomElements and trying to implement a solution similar to ionic framework https://github.com/ionic-team/ionic-framework/commit/dc48a9f1a2dff8a2d644112bbe1df8b0b6811848#diff-8cee275a9cf24f29120acc6b18432e1b43901e53e260a64bd180c97a64bd180
but, my helpers never run.

Summary
Relevant information

@abe-modyo hi we are using our own output generator => https://github.com/baloise/stencil-ds-output-targets
hope that helps with your issue


refactor: simplify async timer logic

Description
What is changing?
Simplifying the logic so that we can reason more easily about the async scheduler.
The previous code was relying on the NaN timeSinceLastWake correctly falling through on first wake, this refactor makes it so we rely on a more straightforward boolean cannotBeExpedited instead.
Updating tests to use synchronous assertions since sinon fake timers don't require async callbacks to execute.
Is there new documentation needed for these changes?
No
What is the motivation for this change?
Hopefully reduce chance of accidental bugs
Double check the following

[x] Ran npm run check:lint script
[x] Self-review completed using the steps outlined here
[N/A] PR title follows the correct format: <type>(NODE-xxxx)<!>: <description>
[x] Changes are covered by tests
[N/A] New TODOs have a related JIRA ticket

CI run here: https://spruce.mongodb.com/version/618530727742ae7aae00b3b3/tasks?sorts=STATUS%3AASC%3BBASE_STATUS%3ADESC


Players getting stucked up Fire Resistant Potion Effect.

Describe the bug
Most players are getting stuck in Fire Resistant Effect and can't get rid of it.
Screenshots or logs
If applicable, add screenshots or logs to help explain your problem. For logs please use pastebin, hastebin or something alike.
Additional information

Server version (/versio): 1.15.2 Git-Paper-245
Plugin version (/dcaves): Dcaves v2.1.9 c15
Server core name (Spigot, Paper etc.): Paper
Plugins list (if possible)

What exactly do you mean? Players are getting Fire Resistant effect?

It was actually fixed on 2.2.0 https://github.com/imDaniX/Dangerous-Caves-2/commit/fd826662a65909e6687dc14c46e4df0d568530fd
Please update and close the issue if everything is fine.


[Suggestion/request] Permit branch parameters to be entered as Inductance/Capacitance/Ic

Would be nice to be able to define branch parameters using the physical value of the circuit element. That is to say, inductance for inductors, capacitance for capacitors, and junction critical current for junctions.
Why?

Physical simulation software (Ansys, FastHenry, COMSOL) will report results using these units, and physical simulation is a critical part of the circuit design process.
Fabrication facilities usually define their junction process using two parameters, critical current density, $J_c$ (uA/um2), and junction specific capacitance, $c_j$ (in units of fF/um).
Min/max width limits in a fabrication facility will determine junction sizes, which are almost always referred to in units of critical current.

I realize pretty much all of the literature refers to these circuit elements in the energy formalism, but day-to-day work often requires thinking in inductance, capacitance, and critical current units.

@QuantumWitness That's a fine suggestion and reminder that physics is not just what happens in a theorist's head.
I can see a solution to this with two components:

provide a helper function that does unit conversion to frequency units
extend parsing of yaml descriptions to include numbers with units attached (& internally employ 1 to go back to frequency units)

Internally, use of alternative units should be strictly limited to the yaml and the helper function. (No overloading of existing functions etc.)

I think that makes sense, and I believe that users should be OK with scqubits internals purely using frequency units, and it will be good for them to start thinking in this way, as well.
Some more options for units:

set a global scqubits flag for units for each type of circuit element, so the YAMLs remain unchanged in formatting.
add a 'header' line to the YAML that specifies the units so that you can add functionality to look for that line and then parse the rest of the YAML without worrying about handling the various kinds of attached units?

As a circuit designer who has to bounce back and forth between physical simulation (ANSYS, etc) and Hamiltonian simulations, I second this request. We think in capacitances and critical currents, and allowing physical units instead of energy units would be very useful.
Additionally, I would suggest sticking to standard SPICE netlist syntax as much as possible, rather than developing a new one. This could allow for compatibility with other simulator tools, and is also quite scalable as it allows for nesting of components through sub-circuits, which may be useful for composite and multi-qubit systems.


Add a simple method to switch headless mode.

Just a thought as to how we could make switching in/out of headless mode a little easier. Might be more worthy of a Dusk PR than doing it here.

Coverage decreased (-2.4%) to 81.746% when pulling d67b62edaa78bd04a69446f1272c333159c998a4 on feature/headless-switch into 0b3611692c38af7079a8abf53ef16b7527418ed4 on 3.5.

I agree with all of those @crynobone, will take a look at the --disable-gpu option as I'm not sure on that at the moment.

If we have this, we could suggest developer to use bootstrap file for phpunit to make this configuration.

Based on my reading around --disable-gpu I agree it appears to only be required with --headless, so I have altered as required.


ionic-app-base depends on non-existent ionic-bower version

(Opening here because ionic-app-base's readme says to submit issues to the main Ionic repository.)
Creating a new project with e.g. ionic start my-app uses ionic-app-base as the starting project.
Its bower.json currently references driftyco/ionic-bower#1.2.4 in devDependencies.
However there's no 1.2.4 tag for the ionic-bower repo.
As a result trying to add any bower component to the new project fails with e.g.
$ ionic add ngCordova
Failed to find the bower component "ngCordova".

$ bower install ngCordova --save
bower ionic#1.2.4         ENORESTARGET No tag found that was able to satisfy 1.2.4

Should be fixed with https://github.com/driftyco/ionic-bower/releases/tag/v1.2.4
right?

Yes that fixes it, thanks!

Nono, thank you


Inject css into the DOM like style loader in development mode

What problem does this feature solve?
https://github.com/webpack-contrib/css-loader#recommend like css loader recommends, in development mode inject css into DOM works faster, but currently rspack extract css in any mode
What does the proposed API of configuration look like?
Keep the present behavior in production mode, but inject css into DOM like style loader's behavior in development mode.

this behavior should be left to framework like cra or modernjs on top of rspack

I think you don't need style-loader, it should be done by frameworks/your application, in future webpack CSS also will be "extracted" in any mode

What makes me wonder is why the css-loader recommend users use style loader in development mode, is it outdate?And does rspack have any options to control whether extract css or inject it into dom.

minicss-extract-plugin has some hmr problem when used in development mode https://github.com/web-infra-dev/rspack-website/issues/294

@faga295 Because CSS is still under experiments, in future it will be recommended pipeline


Implement SpecAugment's Time Warping and SpecAugment wrapper

🚀 The feature
TimeStretch is not in SpecAugment. It should be Time Warping instead. Time Warping does not change the spectrogram shape, but "warp" the content.
I want to propose the following changes:

Remove the note that TimeStretch is proposed in SpecAugment. I think it is not correct.
Implement Time Warping.
Implement a SpecAugment wrapper that contains Time Warping, Frequency Masking, and Time masking, and accepts the same parameters as noted in the original paper (W, F, mF, T, p, mT). Perhaps the parameter name can be changed for better clarity.

Furthermore, we can also include SpecAugment policies as given by the paper i.e. LibriSpeech basic (LB), LibriSpeech double (LD), Switchboard mild (SM) and Switchboard strong (SS), so that the users can just call SpecAugment(policy="LB") for example.
Motivation, pitch
As stated above.
Alternatives
No response
Additional context
No response

Agree, according to the SpecAugment paper it should do sparse image warping on a spectrogram, but it seems to do quite a different thing


bro help please.

I'm surprised where you got the sources from, please fix the keg crash and flickering effects when drinking beer from the mod, and porting to 1.19.2 Forge please!

Can you give more info on the keg crash and when it happens?


Hey Emad

I'm trying to get in touch with you but can't find anywhere to chat, can you give me somewhere I can reach you?

Didn't realize my email was private, my bad. You can reach me at<EMAIL_ADDRESS>


latlng.LatLng type mapping to GeoPoint extrange behaiviour

(delete this for feature requests)
Client
Firestore golang library
Describe Your Environment
The backend is running in GAE flexible
Expected Behavior
import "google.golang.org/genproto/googleapis/type/latlng"
type Location struct{
Name string
Point latlng.LatLng
}
I do:
_, err := store.Collection("users").Doc(userId).Update(ctx, []firestore.Update{{Path: "last_known_location", Value: user.Location}})

I expect to see the point document as type GeoPoint.
In other place, I have:
type Address struct {
Street string,
City string,
Latitude float64,
Longitude float64
}
When I do:
_, err := doc.Collection("sections").Doc(new-id).Set(ctx, section) //section has an Address
I expect to see the "address" as type object with all its properties (street, city, latitude, longitude...)
Actual Behavior
I see the "address" document with type GeoPoint!!! And I have street and city values missing!

I tried to reproduce this, but I realized I don't have enough information.

I expect to see the point document as type GeoPoint.

What do you mean by "see"? When I run
    dr := client.Collection("users").Doc(userId)
    if _, err := dr.Set(ctx, map[string]interface{}{
        "last_known_location": Location{
            Name:  "L",
            Point: latlng.LatLng{Latitude: 18, Longitude: 71},
        },
    }); err != nil {
        log.Fatal(err)
    }
    if err != nil {
        log.Fatal(err)
    }
    doc, err := dr.Get(ctx)
    if err != nil {
        log.Fatal(err)
    }
    var data struct {
        L Location `firestore:"last_known_location"`
    }
    if err := doc.DataTo(&data); err != nil {
        log.Fatal(err)
    }
    fmt.Printf("%#v\n", data)
    fmt.Printf("%#v\n", doc.Data())

I see
struct { L main.Location "firestore:\"last_known_location\"" }{L:main.Location{Name:"L", Point:latlng.LatLng{Latitude:18, Longitude:71}}}
map[string]interface {}{"last_known_location":map[string]interface {}{"Name":"L", "Point":map[string]interface {}{"Longitude":71, "Latitude":18}}}

which is the expected output.
GeoPoint isn't even a type in the Go client, so I'm confused.
Can you give me a program that reproduces this problem, and also the problem with Address?

I'm trying to think how to reproduce in a program, perhaps it could help to understand:
When I say "I expect to see the point document as type GeoPoint.", I refer to documentation:

latlng.LatLng converts to GeoPoint. latlng is the package
"google.golang.org/genproto/googleapis/type/latlng".

When I insert a doc with a latlng.LatLng field, I see it as a pair of booleans.
And when I insert a doc with a Latitude, Longitude float64 pair, I see them as a GeoPoint.
When I say "I see" I'm talking about de firestore console: https://console.firebase.google.com/project//database/firestore/

I see, I didn't realize you were looking at the data with the console.
When I use the console, I see what I would expect to. The document I set in the code above, using your Location struct, looks like this:

When I use your Address struct and this code:
    _, err = dr2.Set(ctx, map[string]interface{}{
        "addr": Address{
            Street:    "S",
            City:      "C",
            Latitude:  32.5,
            Longitude: 18.2,
        },
    })

the console shows

I can't figure out why, but actually, I'm seeing the same for the Address case (the latitude&longitude floats pair, and the rest of the struct values as expected.
I did some changes to my model, but I can't understand what fixed that.
By other hand, I still see last_known_location.Point as a pair of floats (same as you) instead of seeing it as a GeoPoint... it is confusing, the console showed me that for the previous case (Address):
addr: GeoPoint(32W 18N)
I would like to understand that, because in the future I'll need to make some geolocation searchs... And I supose it should be correctly modeled...
Regards,
Matías.

OK, I understand what's happening with Location. You need to use *latlng.LatLng to get a GeoPoint. I consider that a bug and will fix.
What happened with Address I have no idea. Is it possible an earlier version of that struct used *latlng.LatLng?

Ohh, great news! I'll try that.
By sure, Address never had *latlng.LatLng, just the pair of floats, and several other fields (it is mapped to the android Address object)... I can swear it was represented by a GeoPoint missing all other fields.
If I can reproduce it, I'll back...
Anyway, I'll try changing my field to a pointer and will be confirming it here!
Thanks a lot!


[CET-845] Upgrade to<EMAIL_ADDRESS>

How did you learn that the plugin was broken?
Also, is there an actual changelog somewhere for the npm package? All the links just seem to point to backstage.io 😞

How did you learn that the plugin was broken?
Also, is there an actual changelog somewhere for the backstage-cli npm package? All the links just seem to point to backstage.io 😞

right here! https://github.com/backstage/backstage/blob/master/packages/cli/CHANGELOG.md
and had a hunch it was a versioning issue from a customer finding it broken with backstage version 1.2.1


Improve dependency graph generator

$subject since it is recommended to only use platform level URL to identify packages repositories. Because of this, we cannot identify dependencies based on the repository URL.
The script is improved to parse the gradle.properties file to identify the version key of each modules' dependencies.
Default version_key is stdlib + Capitalised artifact Name + Version
This can be overridden in the modules.json.
Improvement because of https://github.com/ballerina-platform/ballerina-release/issues/547

We should ask the repo owners to clean up the gradle.properties file after this. I think there are places where gradle.properties file has versions that aren't used in the build, and some of the gradle.properties files may not follow the naming convention too. (Especially we have to check the cases like OAuth2).

We should ask the repo owners to clean up the gradle.properties file after this. I think there are places where gradle.properties file has versions that aren't used in the build, and some of the gradle.properties files may not follow the naming convention too. (Especially we have to check the cases like OAuth2).

@ThisaruGuruge Tracked it here, https://github.com/ballerina-platform/ballerina-release/issues/547#issuecomment-860365346


Servers Demo ActiveTab UI issue

When demo is open for the first time in a new tab of your browser.
The v-tabs-slider is not correctly placed.

:point_up:  the active tab is CLIENTS but the slider is somewhere between SERVER and SECURITY.
This affects leshan-server-demo and leshan-bsserver-demo web UI.

We finally go with using eager as this is not dependent of the image size, hoping there is no hidden drawback.

eager seems to not really work :confounded: ... I will try with width=164 ...

width=164 solves this issue but I find some other issues with v-tabs-slider.
I guess this is mainly because of all the usage of display breakpoints in LeshanNavBar, I guess the issue come from those lines.
Here a codepen to reproduce it replacing display breakpoints by a boolean control by a button : https://codepen.io/sbernard31/pen/XWaVLOm
I guess I will just stop using v-tabs-slider and replace it by some css.

#1139 should fix the issue (v-tabs-slider replaced by css animation).


Does it will work on unseen data also? will it be able to convert voice of unseen speaker with different content than that of data in training, will we obtain the disentanglement?

I have the same doubt, can someone please clarify.
Thanks in advance.

I have the same question.

You can make it generalize to unseen speakers by training it the same way as AutoVC.

@skol101 it means training with generalized speaker embeddings instead of one-hot embeddings

I had to remove validation part because I couldn’t figure out yet how to create my validatation pkl  file yet based on vctk plus my custom voices.
On 7 Feb 2022, 21:07 +0200, Kaizhi Qian @.***>, wrote:

sounds correct, but you don't need to remove the validation part
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you were mentioned.Message ID: @.***>


Multiline and renaming

I suppose we don't even need SignalManager anymore

Yes, the only reason I left it was to avoid breaking the Pong demo. But it has to be redone anyways as the blocks changed, categories changed, etc.


There is a way to output response in json format?

Hi have you found a solution?

using curl:
`$curl = curl_init();
curl_setopt_array($curl, array(
CURLOPT_RETURNTRANSFER => 1,
CURLOPT_URL => 'http://date.nager.at/api/v1/get/AT/2017'
));
$result = curl_exec($curl);
echo $result;`

Thank you for sharing your code.


Construction of Binary Tree From it's preorder and inorder traversal in C

🚀 Feature
Constructing a binary tree given it's preorder and inorder traversal in c
Have you read the Contributing Guidelines on Pull Requests?
yes
Motivation
(Please outline the motivation for the proposal.)
Pitch
It is a classic problem in data structures and is asked in many coding interviews
I would like to implement this in C as a part of GSSOC'21. Please assign me this

Hi I am GSSoC'21 participant
i would like to contribute in Construction of Binary Tree From it's preorder and inorder traversal using C
i will write the clean code with  brief commenting and algorithm.
so i would like @HarshCasper  to please assign this project to me :)


Ability to configure serving from https ssl by default

Not sure if this already exists but it would be nice to be able to configure the cloudinary gem to serve everything from https / ssl by default. I am aware of the cl_image_tag, but having this config would be a lot more convenient when using something like CarrierWave.

Wrong project =(


Cannot access [Model] before initialization

Versions

sequelize: 4.44.4
sequelize-typescript: 1.1.0
typescript: 3.9.2

I'm submitting a ...

[X] bug report
[ ] feature request
Actual behavior:
$ ./node_modules/.bin/ts-node test.ts
ReferenceError: Cannot access 'Team' before initialization
Expected behavior:
No error.
Steps to reproduce:
Use (basically) the code from the README (https://github.com/RobinBuschmann/sequelize-typescript#one-to-many) as test.ts:
import {BelongsTo, Column, ForeignKey, HasMany, Model, Table} from "sequelize-typescript";

@Table
export class Player extends Model<Player> {

  @Column
  name!: string;

  @Column
  num!: number;

  @ForeignKey(() => Team)
  @Column
  teamId!: number;

  @BelongsTo(() => Team)
  team!: Team;
}

@Table
export class Team extends Model<Team> {

  @Column
  name!: string;

  @HasMany(() => Player)
  players!: Player[];
}

tsconfig.json:
{
  "compilerOptions": {
    "emitDecoratorMetadata": true,
    "esModuleInterop": true,
    "experimentalDecorators": true,
    "forceConsistentCasingInFileNames": true,
    "lib": ["es2019", "es2020.promise", "es2020.bigint", "es2020.string"],
    "noImplicitAny": true,
    "module": "commonjs",
    "outDir": "_dist",
    "rootDir": ".",
    "skipLibCheck": true,
    "sourceMap": false,
    "strict": true,
    "strictNullChecks": true,
    "target": "ES2019"
  }
}

Switching to Sequelize({config: {models: ... } }) seems to work around this but I'm not sure why/how?

I resolved that just putting each model in different files. It is not a sequelize issue, seems like the problem is on typescript compilation with emitDecoratorMetadata: true option.

I resolved that just putting each model in different files. It is not a sequelize issue, seems like the problem is on typescript compilation with emitDecoratorMetadata: true option.

I am also facing the same issue

Error = ReferenceError: Cannot access 'Conversation' before initialization
sequelize version 6.50

I Have a contact model that has a belongsTo association with a Conversation Model.
import sequelize from "sequelize";
import database from "../config/database.js";
import Conversation from "./conversation.js"

const { DataTypes } = sequelize;

const Contact = database.define("contact", {
  opted_in: {
    default: false,
    type: DataTypes.BOOLEAN,
  },
  uuid: {
    type: DataTypes.STRING,
  },
  country_code: {
    type: DataTypes.STRING,
    allowNull: false,
  },
  mobile_number: {
    type: DataTypes.STRING,
    allowNull: false,
  },
  name: {
    type: DataTypes.STRING,
  },
  email: {
    type: DataTypes.STRING,
    isEmail: true,
  },
});

Contact.hasOne(models.Conversation);

export default Contact;

import sequelize from "sequelize";
import database from "../config/database.js";
import Contact from "./contact.js";

const { DataTypes } = sequelize;

const Conversation = database.define("conversation", {
  uuid: {
    type: DataTypes.STRING,
  },
  last_message_created_at: {
    type: DataTypes.DATE,
  },
  last_inbound_message_created_at: {
    type: DataTypes.DATE,
  },
  unread_messages_count: {
    type: DataTypes.INTEGER,
  },
  status: {
    type: DataTypes.INTEGER,
    // values: ['unattended', 'attended', 'inprocess'],
    default: 1,
  },
});

Conversation.belongsTo(Contact, {
    allowNull: false,
    foreignKey: {
      name: "user_contact_id",
    },
    as: "user",
});

export default Conversation;

I have all my entities in different files but I'm getting the same issue?!

Hi,
I have the same issue and it's really blocking me. The weird part is that it seems very inconsistent.

Models are all in different files
I use Sequelize({config: {models: ... } })

Yet I still have this error. Please help :-/

The issue still happens when models are in different files but only when target in tsconfig.json is set to any ES version. It does not happen when targeting CommonJS. Maybe @TPME and @EdByrnee can confirm whether they're also targeting ESM. It seems like using the  () => Model as a workaround for avoiding circular dependencies only works in CommonJS.

I'm having the same issue. Trying the hardest to get it resolved but can't get it working. I'm also using @nestjs/sequelize which does not make it easier because sequelize is encapsulated in there.
Any process or new info on how to resolve this issue?

I was using @nestjs/sequelize. Got same error. Updating module:es2020 and target:es2015 to module: commonjs and target: es2017 solved the issue.

I was using @nestjs/sequelize. Got same error. Updating module:es2020 and target:es2015 to module: commonjs and target: es2017 solved the issue.

It does not because changes the target type to commonjs instead of ESM which is not what we want. If you want to build an ESM module that is not a solution!

I am not providing a solution to this issue. I am confirming that it solves when used commonjs is used instead of ESM.

so there is no future for this project with the now more and more coming ESM projects?

TL;DR: see workaround code snippet.
Without in-depth knowledge of the code I'm not sure if this could work but I'm suggesting it anyways if someone wants to try to implement it.
One way of solving the issue might be to allow passing just the model name on one side of the association and keep passing the model getter on the other (basically a TS overload + a typeof modelGetter === 'string' check). This way the circular dependency would be avoided (no import required on one side in emitted JS code) and sequelize-typescript could resolve the model constructor from its name from the already registered models.
One problem with this approach is what would happen if the model associating by name is defined before the one associating by getter: in that case sequelize-typescript wouldn't have any constructor to resolve yet... And this isn't really under the user's control since the import order is established by Node.
With that said unfortunately I don't have the time to create a PR myself at the moment but I might do it some time in the future since I will also need this feature. In the meantime maybe @RobinBuschmann has some suggestions on the feasibility of this approach/other possible solutions...
For now though I also suggest a workaround I'm planning on using myself:
It's possible to associate model A with model B normally in A.ts (using the import + decorator). Then leave out the association completely in B.ts and add the association for B in A.ts using regular old sequelize.
Here's an example:
// A.ts
import B from './B';

class A extends Model {
  @HasMany(() => B)
  foo!: B[];
}
// Put association in A.ts
B.belongsTo(A);

export default A;

// B.ts
import A from './A';

class B extends Model {
  // Omit association. TS compiler should omit import for A in emitted JS since it's only used as type.
  // @BelongsTo(() => A)
  baz!: A;
}

export default B;

It's not super pretty but it should work.
Let me know what do you think/any possible issue with either approach.

What should be happening to avoid this is to call the @ForeignKey, @HasMany etc function with the models object after sequelize model loading so this could function after static initialization and before sync.
I don't buy the whole circular references can't be avoided or don't matter argument. They do matter and they can be avoided.
I always used this snippet before trying the typescript annotation approach, using a static associate function on each model that deals with association for that model. No circular dependencies necessary.
`
const sequelize = new Sequelize(dbConnectString, options);
const models = loadModels(sequelize); // dynamic model file reading and static initialization
Object.keys(models).forEach(key => {
// simplified version
const model = models[key];
if (model.associate) {
model.associate(models);
}
});
// Model snippet
static associate = models => {
Account.hasMany(models.AccountTenant, {
foreignKey: 'accountId',
onDelete: 'cascade',
as: 'roles',
});
}
`

The root cause of all these issues is the requirement of recursive imports. This PR (https://github.com/RobinBuschmann/sequelize-typescript/pull/1206) solve that in part. But in order to completely solve this, I think the returned reference from an association should be a generic model based on the interface.
So, the final solution could look something like this:

@Table
export class Player extends Model<IPlayer> {

  @Column
  name!: string;

  @Column
  num!: number;

  @ForeignKey(models => models.Team)
  @Column
  teamId!: number;

  @BelongsTo(models => models.Team)
  team!: Model<ITeam>;
}

@Table
export class Team extends Model<ITeam> {

  @Column
  name!: string;

  @HasMany(models => models.Player)
  players!: Model<IPlayer>[];
}

I'm trying to remove emitDecoratorMetadata option. If you set types/table names manually it can be a solution as well

I've got another workaround.
I've noticed that it is possible to reference classes declared later when defining arrays
  // this works
  @HasMany(() => AuctionBid)
  public bids: AuctionBid[];

  // this does not work
  @HasOne(() => AuctionBid)
  public lastBid: AuctionBid;
                  ^ ReferenceError: Cannot access 'AuctionBid' before initialization

Which brought me to this:
  @HasOne(() => AuctionBid)
  public usersBid: ReturnType<() => AuctionBid>;

Compiles without errors.

Nice find @strrife!
The following alternative works too.
  @HasOne(() => AuctionBid)
  public usersBid: Awaited<AuctionBid>;

I've got another workaround.
I've noticed that it is possible to reference classes declared later when defining arrays
  // this works
  @HasMany(() => AuctionBid)
  public bids: AuctionBid[];

  // this does not work
  @HasOne(() => AuctionBid)
  public lastBid: AuctionBid;
                  ^ ReferenceError: Cannot access 'AuctionBid' before initialization

Which brought me to this:
  @HasOne(() => AuctionBid)
  public usersBid: ReturnType<() => AuctionBid>;

Compiles without errors.

i did change the Model to Model[] and it works..

In my case changing the order of how you import these models on the same file you use new Sequelize() solved the problem, I'd suggest having a look at this repo's example because it does the exact same thing and their version works even though it needs updating to the latest version.

I don't believe ESLINT is not screaming: "ESLint: Dependency cycle detected. (import/no-cycle)" on "import" lines on these last workarounds!

In my case changing the order of how you import these models on the same file you use new Sequelize() solved the problem, I'd suggest having a look at this repo's example because it does the exact same thing and their version works even though it needs updating to the latest version.

I was getting the same issue, with this change worked fine to me, thanks!

En caso alguien lea este issue, yo utilicé

To me the most 'natural' workaround for this is to type related models as union with null.
  @BelongsTo(() => Model)
  model?: Model | null;

as it is logically sound. this will either be included in the query result or not.

The solution is explained directly in the readme under the heading "Why () => Model?".


handle the keyboard event properly in hyperlink

This PR fixes #15857
fixes the issue that pressing enter on the context menu button to open the context menu will cause the dialog to be closed
fixes the outline style of the context menu button

before:

after:

fixes the issue that pressing enter on the close button will cause the dialog to be reopened

for 1 and 2, I think the issue is probably coming from the recent chromium upgrade, for button and hyperlink, the keydown event when enter is pressed is not stopped when it is handled as mouse click and caused it to bubble up. I have to handle the keyboard event to stop the propagation.
for 4, i changed it to use keydown event to be consistent with the dialog and buttons to avoid needing to handle keyup events too.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 1 (0.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.002%) to 42.477%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/sql/workbench/browser/modal/modal.ts
0
1
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.002%

Covered Lines:
26786

Relevant Lines:
57120

💛  - Coveralls


Feature gates page mentions Docker runtime

This is a Bug Report

Problem:
Some of the feature gates mention Docker.
Docker integration (via dockershim) is deprecated
Proposed Solution:
For the one deprecated gate where the description mentions Docker:

Accelerators (deprecated)

then revise the feature gate description to explain that it provided an early form of device plugin support, that it's no longer available, and link to https://kubernetes.io/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins/
For each other gate name where the docs mention Docker:

AppArmor (beta)
ExperimentalHostUserNamespaceDefaulting (beta)

establish whether the feature gate makes sense after the dockershim is removed.
If the feature gate still makes sense, reword the description to be neutral to the container runtime. If the gate is in use but no longer makes sense, file an issue against Kubernetes itself to make sure that the gate is removed.
:information_source:  Note that in the feature gates page, deprecated really means “out of use”.  Many “deprecated” feature gates aren't settable at all in current Kubernetes.
Page to Update:
https://kubernetes.io/docs/reference/command-line-tools-reference/feature-gates/

Additional Information:
/sig node

/triage accepted

/assign

In order to proceed with the dockershim removal for the next release, the docker mentions in the feature gates  specifically
ExperimentalHostUserNamespaceDefaulting (beta) shows an obsolete feature flag, see #76982, to be able to use this particular feature, this issue must be addressed.

Hey @SubhasmitaSw the last message is a little confusing to me. If they're ripping out ExperimentalHostUserNamespaceDefaulting at some point in the future, can we just add 'beta/to be obsoleted' to the docs or should we wait on engineers to pull the docs out at the appropriate time?
cc @nate-double-u @sftim

ExperimentalHostUserNamespaceDefaulting still has this description that, yep, still mentions Docker:

Enabling the defaulting user namespace to host. This is for containers that are using other host namespaces, host mounts, or containers that are privileged or using specific non-namespaced capabilities (e.g. MKNODE, SYS_MODULE etc.). This should only be enabled if user namespace remapping is enabled in the Docker daemon.

Can I check if somebody is working on this?

One more thing to fix, as far as I can see:
`ExperimentalHostUserNamespaceDefaulting`: Enabling the defaulting user namespace
to host. This is for containers that are using other host namespaces, host mounts, or
containers that are privileged or using specific non-namespaced capabilities
(e.g. `MKNODE`, `SYS_MODULE` etc.). This should only be enabled if user namespace
remapping is enabled in the Docker daemon.

I think the fix is to change “Docker daemon” to “container runtime”, but I'm not sure.

/remove-lifecycle stale

@SubhasmitaSw Are you still working on this issue?

@vaibhav2107 You can take it up, not having the bandwidth to come back to this.
/unassign

Help is welcome.

For App Armor I think the AppArmor(beta) can be removed. This feature is still in use and is stable from this release.

For ExperimentalHostUserNamespaceDefaulting feature flag, I see that there is an issue raised through which a PR to deprecate the flag has been merged. So, I think it is safe to remove it as well.
I can work on this issue @sftim  once the issue for this flag has been closed. It will be a confirmation for me. I can confirm in sig node as well if you suggest.

/assign

This issue is no longer relevant for the latest documentation as it does not mention docker anywhere. Also 2 of the feature gates mentioned have been removed.
Documentation for version before v1.30 still mention docker daemon. If changes need to be done in previous docs then I can do it. Otherwise the issue can be closed as well.

/close
Nothing to fix. We rarely prioritize docs backports.


Get-ADDBAccount output is empty and does not throw an error

I  am using a fully patched version of Windows Server 2022 (10.0.20348.1607), PowerShell 5.1, and DSInternals v4.9.
I am not getting any output or any errors when running Get-ADDBAccount against a copy of the ntds.dit file.
The procedure I am using is:

Create a snapshot:C:\>diskshadow
DISKSHADOW> SET CONTEXT PERSISTENT
DISKSHADOW> SET METADATA c:\Windows\TEMP\metadata
DISKSHADOW> WRITER VERIFY {afbab4a2-367d-4d15-a586-71dbb18f8485}
DISKSHADOW> WRITER VERIFY {b2014c9e-8711-4c5c-a5a9-3cf384484757}
DISKSHADOW> BEGIN BACKUP
DISKSHADOW> ADD VOLUME C: ALIAS shadow_vol_c
DISKSHADOW> CREATE
DISKSHADOW> EXPOSE %shadow_vol_c% Z:
DISKSHADOW> END BACKUP
DISKSHADOW> EXIT

Copy the ntds.dit and system registry file:C:\dump> copy Z:\Windows\System32\ntds.dit .
C:\dump> copy Z:\Windows\System32\config\SYSTEM .

Execute the cmdletPS C:\dump> $key = Get-BootKey -SystemHiveFilePath .\SYSTEM
PS C:\dump> Get-ADDBAccount -All -BootKey $key -DatabasePath .\ntds.dit

There is no output nor any error produced by the cmdlet, any ideas as to what I can check?

Hi @jcasale , you are doing several mistakes here:

You have copied the initial database (template used by DC installer), which only contains the schema, but no user accounts. The database you are looking for is located in the C:\Windows\NTDS directory by default.
You are not copying the corresponding transaction log files.
If you are on a DC, create an IFM backup instead of a plain volume shadow copy.


⚠ Samsung has degraded performance

In db9ec9d, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2468 ms

Resolved: Samsung performance has improved in 3f519b7.


tests/functional/setup: change mount options

In the CI jobs we can change the mount options of the main partition
to avoid extra operations on disk.
Signed-off-by: Dimitri Savineau<EMAIL_ADDRESS>

jenkins test dev-centos-non_container-update

CI failure, merging anyway


USER-JDk4t error when calling v2beta human user import

Preflight Checklist

[X] I could not find a solution in the documentation, the existing issues or discussions
[X] I have joined the ZITADEL chat

Environment
Self-hosted
Version
v2.50.1
Database
PostgreSQL
Database Version
v16.1
Describe the problem caused by this bug
I am attempting migrate our data from keycloak into Zitadel and wanted to use the v2beta human user import endpoint as it has more functionality such as adding metadata when importing the user.
Unfortunately this error is thrown when I attempt to do a post to v2beta/users/human:
{
  code: 3,
  message: 'Password hash encoding not supported (USER-JDk4t)',
  details: [
    {
      '@type': 'type.googleapis.com/zitadel.v1.ErrorDetail',
      id: 'USER-JDk4t',
      message: 'Password hash encoding not supported'
    }
  ]
}

I am following the steps to do the keycloak migration found in the documentation, but as the v2beta human import route takes in a differently shaped object I also do some mapping to convert the zitadel-tools output into a v2beta import format.
Here is the user I'm attempting to import:
const res = await fetch(`${ZITADEL_DOMAIN}/v2beta/users/human`, {
    method: 'POST',
    headers: {
      'Content-Type': 'application/json',
      Authorization: `Bearer ${ZITADEL_SERVICE_USER_ACCESS_TOKEN}`,
    },
    body: JSON.stringify({
      userId: '13c45e05-83c0-4732-8047-940bcf9da4ef',
      profile: {
        givenName: 'Bonnie',
        familyName: 'Em',
      },
      email: {
        email<EMAIL_ADDRESS>        isEmailVerified: true,
      },
      hashedPassword: {
        hash: '$pbkdf2-sha256$27500$i0VOYMZPRzCZoJHtQqssEQ==$1BnCbQ7q6OYC/qI8xSOAYEBSUmh8ZqwcOo1ABqI2PiA=',
        changeRequired: false,
      },
    }),
  });

The same hash value works on the v1 human user import, and looking at the docs for passwap it also looks correct, so I don't think the error being thrown is actually the problem. I even attempted to use the hash from the passwap examples/tests but that threw an error also.
To reproduce

Spin up a zitadel instance
Create a machine service account with the 'Org User Manager' role
Create a secret key for that machine service account
Make the following POST request, changing the ZITADEL_DOMAIN and ZITADEL_SERVICE_USER_ACCESS_TOKEN to your own values. This example is sent via node, but any other method will be fine too.

const res = await fetch(`${ZITADEL_DOMAIN}/v2beta/users/human`, {
    method: 'POST',
    headers: {
      'Content-Type': 'application/json',
      Authorization: `Bearer ${ZITADEL_SERVICE_USER_ACCESS_TOKEN}`,
    },
    body: JSON.stringify({
      userId: '13c45e05-83c0-4732-8047-940bcf9da4ef',
      profile: {
        givenName: 'Bonnie',
        familyName: 'Em',
      },
      email: {
        email<EMAIL_ADDRESS>        isEmailVerified: true,
      },
      hashedPassword: {
        hash: '$pbkdf2-sha256$27500$i0VOYMZPRzCZoJHtQqssEQ==$1BnCbQ7q6OYC/qI8xSOAYEBSUmh8ZqwcOo1ABqI2PiA=',
        changeRequired: false,
      },
    }),
  });

Observe the following error in the response:

{
  code: 3,
  message: 'Password hash encoding not supported (USER-JDk4t)',
  details: [
    {
      '@type': 'type.googleapis.com/zitadel.v1.ErrorDetail',
      id: 'USER-JDk4t',
      message: 'Password hash encoding not supported'
    }
  ]
}

Screenshots
No response
Expected behavior
I expect the pbkdf2 hash format to work with human user import on the v2beta endpoints like the docs say it will and like the v1 endpoints.
Operating System
OS: Ubuntu 20.04.6 LTS x86_64
Host: 20ST001CGE ThinkPad P15 Gen 1
Kernel: 5.15.0-102-generic
Relevant Configuration
I think I have a fairly normal zitadel set up, but here's my docker compose with the other services stripped out:
version: '3.8'

volumes:
  nn-db:
    name: nn-db

services:
  nn-db:
    container_name: nn-db
    image: postgres:16
    shm_size: 1gb
    restart: unless-stopped
    env_file:
      - ./.env
    environment:
      - POSTGRES_DB=${NN_POSTGRES_DB}
      - POSTGRES_HOST=${NN_POSTGRES_HOST}
      - POSTGRES_USER=${NN_POSTGRES_USER}
      - POSTGRES_PASSWORD=${NN_POSTGRES_PASSWORD}
      - POSTGRES_SCHEMA=${NN_POSTGRES_SCHEMA}
    ports:
      - ${NN_POSTGRES_PORT}:${NN_POSTGRES_PORT}
    volumes:
      - nn-db:/var/lib/postgresql/data
    networks:
      - nn-backend-network
    healthcheck:
      test: ['CMD', 'pg_isready', '-U', '$NN_POSTGRES_USER']
      interval: 5s
      timeout: 5s
      retries: 5

  nn-zitadel:
    container_name: nn-zitadel
    image: 'ghcr.io/zitadel/zitadel:latest'
    command: 'start-from-init --masterkey "MasterkeyNeedsToHave32Characters" --tlsMode disabled'
    environment:
      - 'ZITADEL_DATABASE_POSTGRES_HOST=nn-db'
      - 'ZITADEL_DATABASE_POSTGRES_PORT=5432'
      - 'ZITADEL_DATABASE_POSTGRES_DATABASE=zitadel'
      - 'ZITADEL_DATABASE_POSTGRES_USER_USERNAME=zitadel'
      - 'ZITADEL_DATABASE_POSTGRES_USER_PASSWORD=zitadel'
      - 'ZITADEL_DATABASE_POSTGRES_USER_SSL_MODE=disable'
      - 'ZITADEL_DATABASE_POSTGRES_ADMIN_USERNAME=postgres'
      - 'ZITADEL_DATABASE_POSTGRES_ADMIN_PASSWORD=postgres'
      - 'ZITADEL_DATABASE_POSTGRES_ADMIN_SSL_MODE=disable'
      - 'ZITADEL_EXTERNALSECURE=false'
      - 'ZITADEL_PORT=8080'
      - 'ZITADEL_EXTERNALPORT=8081'

      - 'ZITADEL_DEFAULTINSTANCE_ORG_NAME=MatterHive'

      - 'ZITADEL_DEFAULTINSTANCE_ORG_HUMAN_USERNAME=zitadel-admin' #UserName: zitadel-admin # ZITADEL_DEFAULTINSTANCE_ORG_HUMAN_USERNAME
      - 'ZITADEL_DEFAULTINSTANCE_ORG_HUMAN_EMAIL_VERIFIED=true' #  Verified: false # ZITADEL_DEFAULTINSTANCE_ORG_HUMAN_EMAIL_VERIFIED
      - 'ZITADEL_DEFAULTINSTANCE_ORG_HUMAN_PREFERREDLANGUAGE=en' #PreferredLanguage: en # ZITADEL_DEFAULTINSTANCE_ORG_HUMAN_PREFERREDLANGUAGE

    restart: unless-stopped
    ports:
      - '8081:8080'
    networks:
      - nn-backend-network
    depends_on:
      nn-db:
        condition: 'service_healthy'

networks:
  nn-backend-network:
    name: nn-backend-network

Additional Context
No response

After moving forward using the v1 import I discovered that I need to add pbkdf2 as a Verifier in order to rehash those passwords on user login.
After setting pbkdf2 as a verifier, the v2beta endpoint also works now! It seems that setting being missing is what was causing the error. Either a clearer error message, or a mention somewhere in the docs that this could be a problem will likely be a good enough fix :)

A customer just reach out with the same problem. We should also mention this in the docs: https://zitadel.com/docs/concepts/architecture/secrets#hashed-secrets


Remove all !important directives from css/less files

AdminLTE is a basis from which to build fantastic admin web interfaces. However, layering styles over it has some issues with a number of !important directives I've found.

Most of the rules that use !important are there to override Bootstrap components that otherwise would require a full path to the element. If all !important statements were removed, some elements would look and perhaps behave differently than what's intended. I am sure there are a few that are possibly not needed and are there by mistake, but most of them are required.
Thanks.

I understand why it was done, and how it works, but I'd much prefer verbose css paths to using !important. Using !important is a shortcut and every developer after you must also use !important to override affected styles. Defeats the purpose of having "cascading" styles, doesn't it? Any changes have to use a trump card to function.

I will look into this further with the next major release.
Thanks.

+1 I've been using the admin lte stylesheet but am now considering dropping it for this reason.

Removed unnecessary !important statements and edited some to not use it. Background contextual classes have !important statements because they are needed in many cases to override default backgrounds. An example of that can be found in the timeline. Thanks.


node-wcag tests failing

The node-wcag tests seem to be failing for many (if not all) cf components. Here's the output:

Since the errors aren't specified, it's hard to diagnose what the problem is. @contolini any ideas?

With cf-buttons, it's because the demo page has buttons that include links without content. This violates WCAG-AA guidelines.
The proper way to do compound buttons would be to add visually hidden text:

    Dropdown

Testing file still exists in https://github.com/cfpb/capital-framework/blob/canary/test/accessibility/wcag.js
But the command to run it was removed in https://github.com/cfpb/capital-framework/commit/927006327fb78a098e93474560c01972dc02f22b

Closing this issue. Thanks @anselmbradford!


feat(dropdown): Make Auto-Close Dropdowns optional. Fix #2218

Introduces an auto-close option which - when specified - works as follows:

outsideClick - closes the dropdown automatically only when the user clicks any element outside the dropdown.
disabled - disables the auto close. You can then control the open/close status of the dropdown manually, by using is-open.

+1

@chrisirhc I noticed you mentioned in #2218 about being willing to review a PR if someone implements the feature.  This PR looks pretty good to me, but I'd like a second pair of eyes since I'm too tired at the moment.
That this is an optional feature makes this ok IMO.

Great work. I did a review. This looks good. Just styling and a suggestion.

I'll make the edits as soon as I have 5 minutes. Thanks for reviewing!

@chrisirhc Merged with upstream and addressed all the comments.

Can you clean up the history?  The merge commit should not be there.

Done (and merged with latest commits)

Thanks for the work here, this will make it in 0.13.0!


Unable to fetch versions for a  Cocoapods package

The cocoapods gets the list of versions by parsing the html for the page where cocoapods specs are stored. Example : https://github.com/CocoaPods/Specs/tree/master/Specs/8/2/7/RandomKit
The html page is changed and hence the query selectors used to fetch version data no more exists on the page, as a result causing it to fail.

Yep, looks like the GitHub page content changed, so maybe something like div.react-directory-truncate => title or something like that?

I wonder if we could make this more robust by switching to libgit2sharp rather than parsing the html representation of the git repo.
I'll test the workaround @scovetta  suggested today first.

The version numbers are no longer included as actual HTML elements at all.  Looking at the HTML that we get back it contains the below script tag with embedded data for react. I rewrote the parser to extract this json data, then parse it as a JObject, then use JSONPath to fetch just the version numbers, then we can add those to the version list.  See #439.
<script type="application/json" data-target="react-app.embeddedData">{"payload":{"allShortcutsEnabled":false,"path":"Specs/8/2/7/RandomKit","repo":{"id":2365549,"defaultBranch":"master","name":"Specs","ownerLogin":"CocoaPods","currentUserCanPush":false,"isFork":false,"isEmpty":false,"createdAt":"2011-09-11T13:47:10.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/1189714?v=4","public":true,"private":false,"isOrgOwned":true},"currentUser":null,"refInfo":{"name":"master","listCacheKey":"v0:1613410512.605122","canEdit":false,"refType":"branch","currentOid":"ca3c3c1cc74a81418ff7a5ba96cea3b1e9cec9dd"},"tree":{"items":[{"name":"1.0.0","path":"Specs/8/2/7/RandomKit/1.0.0","contentType":"directory"},{"name":"1.1.0","path":"Specs/8/2/7/RandomKit/1.1.0","contentType":"directory"},{"name":"1.2.0","path":"Specs/8/2/7/RandomKit/1.2.0","contentType":"directory"},{"name":"1.3.0","path":"Specs/8/2/7/RandomKit/1.3.0","contentType":"directory"},{"name":"1.4.0","path":"Specs/8/2/7/RandomKit/1.4.0","contentType":"directory"},{"name":"1.5.0","path":"Specs/8/2/7/RandomKit/1.5.0","contentType":"directory"},{"name":"1.6.0","path":"Specs/8/2/7/RandomKit/1.6.0","contentType":"directory"},{"name":"2.0.0","path":"Specs/8/2/7/RandomKit/2.0.0","contentType":"directory"},{"name":"2.1.0","path":"Specs/8/2/7/RandomKit/2.1.0","contentType":"directory"},{"name":"2.2.0","path":"Specs/8/2/7/RandomKit/2.2.0","contentType":"directory"},{"name":"2.2.1","path":"Specs/8/2/7/RandomKit/2.2.1","contentType":"directory"},{"name":"2.3.0","path":"Specs/8/2/7/RandomKit/2.3.0","contentType":"directory"},{"name":"3.0.0","path":"Specs/8/2/7/RandomKit/3.0.0","contentType":"directory"},{"name":"4.0.0","path":"Specs/8/2/7/RandomKit/4.0.0","contentType":"directory"},{"name":"4.1.0","path":"Specs/8/2/7/RandomKit/4.1.0","contentType":"directory"},{"name":"4.2.0","path":"Specs/8/2/7/RandomKit/4.2.0","contentType":"directory"},{"name":"4.3.0","path":"Specs/8/2/7/RandomKit/4.3.0","contentType":"directory"},{"name":"4.3.1","path":"Specs/8/2/7/RandomKit/4.3.1","contentType":"directory"},{"name":"4.4.0","path":"Specs/8/2/7/RandomKit/4.4.0","contentType":"directory"},{"name":"4.4.1","path":"Specs/8/2/7/RandomKit/4.4.1","contentType":"directory"},{"name":"4.5.0","path":"Specs/8/2/7/RandomKit/4.5.0","contentType":"directory"},{"name":"4.5.1","path":"Specs/8/2/7/RandomKit/4.5.1","contentType":"directory"},{"name":"4.5.2","path":"Specs/8/2/7/RandomKit/4.5.2","contentType":"directory"},{"name":"5.0.0","path":"Specs/8/2/7/RandomKit/5.0.0","contentType":"directory"},{"name":"5.1.0","path":"Specs/8/2/7/RandomKit/5.1.0","contentType":"directory"},{"name":"5.2.0","path":"Specs/8/2/7/RandomKit/5.2.0","contentType":"directory"},{"name":"5.2.1","path":"Specs/8/2/7/RandomKit/5.2.1","contentType":"directory"},{"name":"5.2.2","path":"Specs/8/2/7/RandomKit/5.2.2","contentType":"directory"},{"name":"5.2.3","path":"Specs/8/2/7/RandomKit/5.2.3","contentType":"directory"}],"templateDirectorySuggestionUrl":null,"readme":null,"totalCount":29,"showBranchInfobar":false},"fileTree":{"Specs/8/2/7":{"items":[{"name":"BBUtils","path":"Specs/8/2/7/BBUtils","contentType":"directory"},{"name":"BadgeLabel","path":"Specs/8/2/7/BadgeLabel","contentType":"directory"},{"name":"EMSpinnerButton","path":"Specs/8/2/7/EMSpinnerButton","contentType":"directory"},{"name":"ExpandableTextView","path":"Specs/8/2/7/ExpandableTextView","contentType":"directory"},{"name":"FCModel","path":"Specs/8/2/7/FCModel","contentType":"directory"},{"name":"FSDiary","path":"Specs/8/2/7/FSDiary","contentType":"directory"},{"name":"JBTestZhenNiuB","path":"Specs/8/2/7/JBTestZhenNiuB","contentType":"directory"},{"name":"JavenKit","path":"Specs/8/2/7/JavenKit","contentType":"directory"},{"name":"NSURL-RandValue","path":"Specs/8/2/7/NSURL-RandValue","contentType":"directory"},{"name":"NativeCSS","path":"Specs/8/2/7/NativeCSS","contentType":"directory"},{"name":"PRTabWithBadgeAnimation","path":"Specs/8/2/7/PRTabWithBadgeAnimation","contentType":"directory"},{"name":"RandomKit","path":"Specs/8/2/7/RandomKit","contentType":"directory"},{"name":"SNKeyboard","path":"Specs/8/2/7/SNKeyboard","contentType":"directory"},{"name":"Scheme","path":"Specs/8/2/7/Scheme","contentType":"directory"},{"name":"SobotCallSDK","path":"Specs/8/2/7/SobotCallSDK","contentType":"directory"},{"name":"SpringButton","path":"Specs/8/2/7/SpringButton","contentType":"directory"},{"name":"TrackingHelper","path":"Specs/8/2/7/TrackingHelper","contentType":"directory"},{"name":"YUGLTransition","path":"Specs/8/2/7/YUGLTransition","contentType":"directory"},{"name":"ZDAFNetWorkHelper","path":"Specs/8/2/7/ZDAFNetWorkHelper","contentType":"directory"},{"name":"yapo-transport","path":"Specs/8/2/7/yapo-transport","contentType":"directory"}],"totalCount":20},"Specs/8/2":{"items":[{"name":"0","path":"Specs/8/2/0","contentType":"directory"},{"name":"1","path":"Specs/8/2/1","contentType":"directory"},{"name":"2","path":"Specs/8/2/2","contentType":"directory"},{"name":"3","path":"Specs/8/2/3","contentType":"directory"},{"name":"4","path":"Specs/8/2/4","contentType":"directory"},{"name":"5","path":"Specs/8/2/5","contentType":"directory"},{"name":"6","path":"Specs/8/2/6","contentType":"directory"},{"name":"7","path":"Specs/8/2/7","contentType":"directory"},{"name":"8","path":"Specs/8/2/8","contentType":"directory"},{"name":"9","path":"Specs/8/2/9","contentType":"directory"},{"name":"a","path":"Specs/8/2/a","contentType":"directory"},{"name":"b","path":"Specs/8/2/b","contentType":"directory"},{"name":"c","path":"Specs/8/2/c","contentType":"directory"},{"name":"d","path":"Specs/8/2/d","contentType":"directory"},{"name":"e","path":"Specs/8/2/e","contentType":"directory"},{"name":"f","path":"Specs/8/2/f","contentType":"directory"}],"totalCount":16},"Specs/8":{"items":[{"name":"0","path":"Specs/8/0","contentType":"directory"},{"name":"1","path":"Specs/8/1","contentType":"directory"},{"name":"2","path":"Specs/8/2","contentType":"directory"},{"name":"3","path":"Specs/8/3","contentType":"directory"},{"name":"4","path":"Specs/8/4","contentType":"directory"},{"name":"5","path":"Specs/8/5","contentType":"directory"},{"name":"6","path":"Specs/8/6","contentType":"directory"},{"name":"7","path":"Specs/8/7","contentType":"directory"},{"name":"8","path":"Specs/8/8","contentType":"directory"},{"name":"9","path":"Specs/8/9","contentType":"directory"},{"name":"a","path":"Specs/8/a","contentType":"directory"},{"name":"b","path":"Specs/8/b","contentType":"directory"},{"name":"c","path":"Specs/8/c","contentType":"directory"},{"name":"d","path":"Specs/8/d","contentType":"directory"},{"name":"e","path":"Specs/8/e","contentType":"directory"},{"name":"f","path":"Specs/8/f","contentType":"directory"}],"totalCount":16},"Specs":{"items":[{"name":"0","path":"Specs/0","contentType":"directory"},{"name":"1","path":"Specs/1","contentType":"directory"},{"name":"2","path":"Specs/2","contentType":"directory"},{"name":"3","path":"Specs/3","contentType":"directory"},{"name":"4","path":"Specs/4","contentType":"directory"},{"name":"5","path":"Specs/5","contentType":"directory"},{"name":"6","path":"Specs/6","contentType":"directory"},{"name":"7","path":"Specs/7","contentType":"directory"},{"name":"8","path":"Specs/8","contentType":"directory"},{"name":"9","path":"Specs/9","contentType":"directory"},{"name":"a","path":"Specs/a","contentType":"directory"},{"name":"b","path":"Specs/b","contentType":"directory"},{"name":"c","path":"Specs/c","contentType":"directory"},{"name":"d","path":"Specs/d","contentType":"directory"},{"name":"e","path":"Specs/e","contentType":"directory"},{"name":"f","path":"Specs/f","contentType":"directory"},{"name":".gitkeep","path":"Specs/.gitkeep","contentType":"file"}],"totalCount":17},"":{"items":[{"name":".github","path":".github","contentType":"directory"},{"name":"Scripts","path":"Scripts","contentType":"directory"},{"name":"Specs","path":"Specs","contentType":"directory"},{"name":".gitignore","path":".gitignore","contentType":"file"},{"name":".rubocop.yml","path":".rubocop.yml","contentType":"file"},{"name":"AlgoliaSearch.yml","path":"AlgoliaSearch.yml","contentType":"file"},{"name":"CocoaPods-version.yml","path":"CocoaPods-version.yml","contentType":"file"},{"name":"Gemfile","path":"Gemfile","contentType":"file"},{"name":"Gemfile.lock","path":"Gemfile.lock","contentType":"file"},{"name":"README.md","path":"README.md","contentType":"file"},{"name":"netlify.toml","path":"netlify.toml","contentType":"file"}],"totalCount":11}},"fileTreeProcessingTime":30.031953,"foldersToFetch":[],"showSurveyBanner":false,"showCodeNavSurvey":false,"csrf_tokens":{"/CocoaPods/Specs/branches":{"post":"3io837AB6d-fdf5TCaeBvZefdJ61sK2UvJOxT0KrwWhgDrpBgYMXFIQHy70GH1baVoxdScj02QvhWeXf_ZwDhA"},"/CocoaPods/Specs/branches/fetch_and_merge/master":{"post":"BgJKof6DgIhiHYBr0eYoIpONxbTTlKe0XhUVsUvksrJg8laVxfHqr9Wsm5StinZtrfv6LsuKWso0s0g30FxAkA"},"/CocoaPods/Specs/branches/fetch_and_merge/master?discard_changes=true":{"post":"qkw7zAALxLXyaPL44l0V4kDgLeFYfB45zulz26fsHp_MvCf4O3mukkXZ6QeeMUutfpYSe0Bi40ekTy5dPFTsvQ"}}},"title":"Specs/Specs/8/2/7/RandomKit at master · CocoaPods/Specs","locale":"en","appPayload":{"helpUrl":"https://docs.github.com","findFileWorkerPath":"/assets-cdn/worker/find-file-worker-848bb9a5da17.js","findInFileWorkerPath":"/assets-cdn/worker/find-in-file-worker-5155f0e7ee32.js","githubDevUrl":null,"enabled_features":{"virtualize_file_tree":true,"react_repos_overview":false,"repos_new_shortcut_enabled":true,"blob_navigation_cursor":true,"code_nav_ui_events":false,"ref_selector_v2":false,"codeview_codemirror_next_editors":false,"blob_firefox_separate_characters":true,"column_symbol_auto_select":false,"copilot_conversational_ux":false}}}</script>


InvalidMixinException in 20w15a

Describe the bug
Using LibCD version 2.3.1+20w15a crashes the game when loading the world with an InvalidMixinException.
To Reproduce
Steps to reproduce the behavior:

Load a world on 20w15a with LibCD 2.3.1+20w15a is installed

Expected behavior
The world loads
Version of the (please complete the following information):

LibCD 20w15a
Fabric API 0.5.9+build.319-1.16
Minecraft 20w15a

Additional context
Game log: latest.log
This seems to occur because MixinTagBuilder shadows a field called entries that is assumed to be a Set<Tag.Entry>, but the field in Tag.Builder is of type List<Tag.class_5145>.

Sounds like a remapping error. I'll talk to @draylar about it.

20w15a adds a new Tag (class_5145) with information (a string) on the resource pack's name. It has a private constructor, and I can't figure out access wideners, so it might be a little bit until a fix.

Can't you use an invoker mixin for the private constructor?

Opening up a PR now.

@bluebear94 Can we confirm that this is fixed?


Dracula for Mantine

Hey!
I made a Dracula color scheme for Mantine components library.
Here is my repository: https://github.com/zeretkk/mantine-dracula

Hey, that's very cool! ✨
I just sent you an invitation to join the organization.
I also cloned your repository for Dracula's organization, so you can go ahead and delete or archive yours:

Your repository.
New repository.

Thanks for building this! 🎉


Populated and updated the definitions using text observation distributions.

Generated the text observation distributions and fixed any inconsistencies.
Changed the way to define the descriptions, action spaces, and action exclusiveness. (Refer to README.md.)

We don't have to define the descriptions for all environments. If there is no environment name in DESCRIPTIONS, the text observation is used as the environment name and description.
We don't have to define the action spaces for all environments. We can define a single action space called "default" to be shared for all environments.
We don't have to define the action exclusiveness for all environments. We can define a single action exclusiveness called "default" to be shared for all environments.

lgtm, great work!


Add another app

Thanks!

Hi @fmaussion
Thanks for the contribution. The files you have changed are actually updated from the file application\config\resources.py and application\config\authors.py.
Regarding the Simulator I was just not sure it was a Panel app as it states its a Bokeh app. Can you confirm its a Panel app?

The updates I believe I should make are
OGGM_EDU = Author(
    name="OGGM EDU",
    url="https://edu.oggm.org",
    github_url="https://github.com/OGGM",
    github_avatar_url="https://avatars2.githubusercontent.com/u/14758186",
)

and
Resource(
        name="World Glaciers Explorer",
        url="https://edu.oggm.org/en/latest/explorer.html",
        thumbnail_png_path=THUMBNAILS_ROOT + "",
        is_awesome=True,
        tags=[tags.APP, tags.CODE],
        author=authors.OGGM_EDU,
    ),
    Resource(
        name="Glacier Simulator",
        url="https://edu.oggm.org/en/latest/simulator.html",
        thumbnail_png_path=THUMBNAILS_ROOT + "",
        is_awesome=True,
        tags=[tags.APP, tags.CODE],
        author=authors.OGGM_EDU,
    ),

Can you confirm?¨
Thanks again.

Can you confirm its a Panel app?

Yes! We call it "bokeh app" because we serve it on our server which is called https://bokeh.oggm.org -> in the end the engine which runs it all is Bokeh, but we use panel extensively. Here is the app's code: https://github.com/OGGM/glacier_simulator

Can you confirm?¨

Perfect thanks!


Add extension integration tests support for packaged .vsix file.

I'm trying to write some integration tests for an extension. From the document I learned that it's possible to start the tests by using the project's root path as the extensionDevelopmentPath parameter, like the code in the demo:
import * as path from 'path';

import { runTests } from 'vscode-test';

async function main() {
  try {
    // The folder containing the Extension Manifest package.json
    // Passed to `--extensionDevelopmentPath`
    const extensionDevelopmentPath = path.resolve(__dirname, '../../../');

    // The path to the extension test runner script
    // Passed to --extensionTestsPath
    const extensionTestsPath = path.resolve(__dirname, './suite/index');

    // Download VS Code, unzip it and run the integration test
    await runTests({ extensionDevelopmentPath, extensionTestsPath });
  } catch (err) {
    console.error(err);
    console.error('Failed to run tests');
    process.exit(1);
  }
}

main();

But my question is that how can I start the tests for an extension packaged as .vsix file. Because it may be different after the webpack process, and I want to make sure it does not break. Any idea is welcome.

We have seen issue after webpack obfuscation, which causes extension to malfunction after packaging into vsix.


hotfix(all): merge changes from interrupted 2.43.0 pipeline into main

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: 5a553fb47b195512de6084f3b34dc57ceef3e8dd
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository


[ARC-525] Wrap run in check

initializing result accumulator at start of run and reporting at the end
of it.
branch: feature/ARC-525-report-build-progress

Stage BUILD
2023-02-22 05:58:55.100132 - job - Stage.BUILD - success: True
2023-02-22 05:58:55.100132 - service - Stage.BUILD - success: True
Stage DEPLOY
2023-02-22 05:58:55.100132 - job - Stage.DEPLOY - success: True
2023-02-22 05:58:55.100132 - service - Stage.DEPLOY - success: True


Transaction is not fully success

I copy this code and deployed it as your instruction. But transaction is not performed complete successfully, Tx information as this link : https://ropsten.etherscan.io/tx/0xdaf800d40de5a469f07f16f030a04c194f7aca099e7422876ea388580aed9aac
Why is it happened? Could you help me to make it clear ?
Thanks you.

Yes, I redeployed a contract , repeat your process. It shows interesting result: 5 transactions , 3 are reverted, 2 are all success...
https://ropsten.etherscan.io/address/0x002951299cbd9a373cc9f8e96661858031d332b6
I think contract of uniswap or sushi in ropsten net might be not working reliably

I had a transaction "Success" but 2 executions were reverted. I followed @fifikobayashi instructions above precisely. I'm not finding any hints in the transaction log on etherscan nor the remix logs. The contract still have plenty of ether left. Tried 2 times with same result:
[First Attempt]
(https://ropsten.etherscan.io/tx/0x83d344a3f6ce8122fe2ab8d4cda2e4326c6a3fc1ba791f7f0b556cc16da697e6)
Second attempt
Mind having a look?


Breadcrumb selection is broken

VSCode Version: 1.27.1
OS Version: Linux x64

Steps to Reproduce

Focus on the breadcrumbs menu
Use the up/down arrow keys to select any item in the list
Press the Enter key

Expected result
Upon pressing the Enter key, the breadcrumbs menu should close and the editor should jump to the selected item.
Actual result
Upon pressing the Enter key, the breadcrumbs menu stays open and the selection jumps back to the initial item (i.e. the one that is already highlighted at the time the menu is opened).
Additional info

Does this issue occur when all extensions are disabled?: Yes
The bug is also present on 1.27.1-insider (commit 5944e81f3).

Can confirm this is also the case on Windows x64.
Pressing Ctrl+Enter does open the selected item in a new vertical split editor.

Pressing Ctrl+Enter works as expected for me as well.
As with Enter, pressing Space sends me back to the initial item but closes the breadcrumbs menu.
I can only make the Enter key work by first typing the first few letters of the symbol I want to jump to.

Upon pressing the Enter key, the breadcrumbs menu should close and the editor should jump to the selected item.

Hm, I can't reproduce this. On what element are you pressing enter? A document symbol, a file, or a folder?

Do you have any special keybindings configured?

No, I try to stick as much as possible to the default keybindings so I have very few custom ones. Here they are :
[
    {
        "key": "ctrl+k ctrl+b",
        "command": "workbench.action.toggleSidebarVisibility"
    },
    {
        "key": "ctrl+k ctrl+j",
        "command": "workbench.action.togglePanel"
    },
    {
        "key": "ctrl+[Slash]",
        "command": "workbench.action.terminal.focus"
    }
]

I just made a test on a different computer with the same OS (Manjaro 17.1.12 KDE edition) and could reproduce the exact same problem. It was the first time VSCode was installed on this computer so there was no extension or custom settings.
When I have a bit more time, I'll try on a different OS.

I did a fresh install of Debian 9.5.0 with the Gnome desktop and VSCode 1.27.1 (no extension or custom settings) in a VirtualBox machine and got the same problem.
It might well be a Linux only problem but it is really easy to reproduce.

@bpasero this happens because on linux the list service doesn't 'eat' the enter (and then some other command happens)

Nah, not the list service but we somehow think that enter produces a printable character. That reveals the input box and moves focus. Then the list service, correctly, doesn't handle the enter anymore...

Yeah, not so cool. Some background: It's quite hard to know what buttons on a keyboard and what combinations of those produce what character on screen. Therefore we have a little native node module that basically presses all buttons with all modifiers and returns the outcome "on screen". We build a lookup table from that information and us for this like this. That also explains why it is different on each OS, on each language, and keyboard. It seems that mac and windows don't produce a printable character but that linux produces \n (13) (which looks pretty correct to me).
I will update to logic to ignore certain outcomes... @swatteau @sambhare Thanks for the issue and please, please use Insiders. I have made the change that caused this already a month ago and I would have loved that insider-usages would have caught this...

I'm not sure if I understand all the details of your investigation but just to let you know : at some point I tried to change the keybinding of the breadcrumbs.selectFocused action from Enter to something else (just in case there was something special about the Enter key). The result was still the same so I'm not sure if the fact that the character is printable has anything to do with this.

This is fixed is todays insiders: https://code.visualstudio.com/insiders/

Assigned to August Recovery for discussion.

Cherry picked the fix to the release/1.27 branch

@swatteau @sambhare You guys try this with latest https://code.visualstudio.com/insiders/. Thanks

Tested on latest insiders, works great! Thanks for the quick fix!