Raspberry Pi 4 32 bit compile problems

Hi,
whenever I try to compile your engine I get these errors:
Al@RPi4-SSD:~/go $ go get -u github.com/amanjpro/zahak/zahak
github.com/amanjpro/zahak/engine
src/github.com/amanjpro/zahak/engine/cache.go:32:27: syntax error: unexpected b1111111111111111111111111111 after top level declaration
src/github.com/amanjpro/zahak/engine/cache.go:33:27: syntax error: unexpected b1111111111111111 after top level declaration
src/github.com/amanjpro/zahak/engine/cache.go:34:28: syntax error: unexpected b1111111 after top level declaration
src/github.com/amanjpro/zahak/engine/cache.go:35:27: syntax error: unexpected b111 after top level declaration
src/github.com/amanjpro/zahak/engine/cache.go:36:26: syntax error: unexpected b1111111111 after top level declaration
Also I’ve tried your provided binaries for 32bit and 64bit for v5 and v6 but neither run on Raspberry Pi 4, which is completely up to date running Raspbian OS 32bit.
Thanks,
Al.

I have never tried using go get command to compile, I use make build for building, can you try this instead:
$ git clone https://github.com/amanjpro/zahak.git
$ cd zahak
$ make build

Also, I don't have RaspberryPi 4, or any ARM 64 for that matter, I have once tried running it on a friend's computer and it worked.
I am currently successfully running versions 5 and 6 on RaspberryPi 3 - 32bit... will look into this
Thanks for having interest in Zahak

Also, what version of golang are you using?

Hi,
Thanks for the quick reply, I had already tried GitHub but tried the other way because other GO engines work that way too.
However here is what you asked:
Al@RPi4-SSD:~/Engine-Source $ git clone https://github.com/amanjpro/zahak.git
Cloning into 'zahak'...
remote: Enumerating objects: 4323, done.
remote: Counting objects: 100% (886/886), done.
remote: Compressing objects: 100% (478/478), done.
remote: Total 4323 (delta 541), reused 558 (delta 376), pack-reused 3437
Receiving objects: 100% (4323/4323), 931.33 KiB | 4.00 MiB/s, done.
Resolving deltas: 100% (2903/2903), done.
Al@RPi4-SSD:~/Engine-Source $ cd zahak
Al@RPi4-SSD:~/Engine-Source/zahak $ make build
mkdir -p bin
go build -ldflags "-X 'main.version=d3d1b0fc2d8e06a518b8c8a162d0673b2db564a0'" -o bin ./...
go build: cannot use -o with multiple packages
make: *** [Makefile:6: build] Error 1
Also, here’s what I get when I try your binaries:
Al@RPi4-SSD:~ $ ./zahak-linux-arm32-5.0
ZZZZZZZZZZZZZZZZZZZ                 hhhhhhh                               kkkkkkkk
Z:::::::::::::::::Z                 h:::::h                               k::::::k
Z:::::::::::::::::Z                 h:::::h                               k::::::k
Z:::ZZZZZZZZ:::::Z                  h:::::h                               k::::::k
ZZZZZ     Z:::::Z    aaaaaaaaaaaaa   h::::h hhhhh         aaaaaaaaaaaaa    k:::::k    kkkkkkk
Z:::::Z      a::::::::::::a  h::::hh:::::hhh      a::::::::::::a   k:::::k   k:::::k
Z:::::Z       aaaaaaaaa:::::a h::::::::::::::hh    aaaaaaaaa:::::a  k:::::k  k:::::k
Z:::::Z                 a::::a h:::::::hhh::::::h            a::::a  k:::::k k:::::k
Z:::::Z           aaaaaaa:::::a h::::::h   h::::::h    aaaaaaa:::::a  k::::::k:::::k
Z:::::Z          aa::::::::::::a h:::::h     h:::::h  aa::::::::::::a  k:::::::::::k
Z:::::Z          a::::aaaa::::::a h:::::h     h:::::h a::::aaaa::::::a  k:::::::::::k
ZZZ:::::Z     ZZZZZa::::a    a:::::a h:::::h     h:::::ha::::a    a:::::a  k::::::k:::::k
Z::::::ZZZZZZZZ:::Za::::a    a:::::a h:::::h     h:::::ha::::a    a:::::a k::::::k k:::::k
Z:::::::::::::::::Za:::::aaaa::::::a h:::::h     h:::::ha:::::aaaa::::::a k::::::k  k:::::k
Z:::::::::::::::::Z a::::::::::aa:::ah:::::h     h:::::h a::::::::::aa:::ak::::::k   k:::::k
ZZZZZZZZZZZZZZZZZZZ  aaaaaaaaaa  aaaahhhhhhh     hhhhhhh  aaaaaaaaaa  aaaakkkkkkkk    kkkkkkk
uci
id name Zahak 5.0
id author Amanj
option name Ponder type check default false
option name Hash type spin default 10 min 1 max 8000
option name Pawnhash type spin default 2 min 1 max 10
option name Book type check default false
uciok
go infinite
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x1c pc=0xef700]
goroutine 6 [running]:
github.com/amanjpro/zahak/engine.(*Position).IsDraw(0x0, 0x1da8000)
/home/runner/work/zahak/zahak/engine/position.go:294 +0x14
github.com/amanjpro/zahak/search.(*Engine).alphaBeta(0x1dac000, 0x80010001, 0x7fff, 0x9dbcd2a7)
/home/runner/work/zahak/zahak/search/search.go:142 +0xb8
github.com/amanjpro/zahak/search.(*Engine).aspirationWindow(0x1dac000, 0x18001, 0x1e34000)
/home/runner/work/zahak/zahak/search/search.go:106 +0x14c
github.com/amanjpro/zahak/search.(*Engine).rootSearch(0x1dac000, 0x10ba064)
/home/runner/work/zahak/zahak/search/search.go:63 +0x208
github.com/amanjpro/zahak/search.(*Engine).Search(0x1dac000, 0xc0456864)
/home/runner/work/zahak/zahak/search/search.go:14 +0x30
github.com/amanjpro/zahak/uci.(*UCI).findMove(0x10a00e0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...)
/home/runner/work/zahak/zahak/uci/uci.go:232 +0x9c4
created by github.com/amanjpro/zahak/uci.(*UCI).Start
/home/runner/work/zahak/zahak/uci/uci.go:126 +0x81c
Al@RPi4-SSD:~ $
=============
Al@RPi4-SSD:~ $ ./zahak-linux-arm32-6.0
ZZZZZZZZZZZZZZZZZZZ                 hhhhhhh                               kkkkkkkk
Z:::::::::::::::::Z                 h:::::h                               k::::::k
Z:::::::::::::::::Z                 h:::::h                               k::::::k
Z:::ZZZZZZZZ:::::Z                  h:::::h                               k::::::k
ZZZZZ     Z:::::Z    aaaaaaaaaaaaa   h::::h hhhhh         aaaaaaaaaaaaa    k:::::k    kkkkkkk
Z:::::Z      a::::::::::::a  h::::hh:::::hhh      a::::::::::::a   k:::::k   k:::::k
Z:::::Z       aaaaaaaaa:::::a h::::::::::::::hh    aaaaaaaaa:::::a  k:::::k  k:::::k
Z:::::Z                 a::::a h:::::::hhh::::::h            a::::a  k:::::k k:::::k
Z:::::Z           aaaaaaa:::::a h::::::h   h::::::h    aaaaaaa:::::a  k::::::k:::::k
Z:::::Z          aa::::::::::::a h:::::h     h:::::h  aa::::::::::::a  k:::::::::::k
Z:::::Z          a::::aaaa::::::a h:::::h     h:::::h a::::aaaa::::::a  k:::::::::::k
ZZZ:::::Z     ZZZZZa::::a    a:::::a h:::::h     h:::::ha::::a    a:::::a  k::::::k:::::k
Z::::::ZZZZZZZZ:::Za::::a    a:::::a h:::::h     h:::::ha::::a    a:::::a k::::::k k:::::k
Z:::::::::::::::::Za:::::aaaa::::::a h:::::h     h:::::ha:::::aaaa::::::a k::::::k  k:::::k
Z:::::::::::::::::Z a::::::::::aa:::ah:::::h     h:::::h a::::::::::aa:::ak::::::k   k:::::k
ZZZZZZZZZZZZZZZZZZZ  aaaaaaaaaa  aaaahhhhhhh     hhhhhhh  aaaaaaaaaa  aaaakkkkkkkk    kkkkkkk
uci
id name Zahak 6.0
id author Amanj
option name Ponder type check default false
option name Hash type spin default 128 min 1 max 24000
option name Pawnhash type spin default 2 min 1 max 10
option name Book type check default false
option name Threads type spin default 1 min 1 max 4
uciok
go infinite
panic: unaligned 64-bit atomic operation
goroutine 17 [running]:
runtime/internal/atomic.panicUnaligned()
/opt/hostedtoolcache/go/1.16.7/x64/src/runtime/internal/atomic/unaligned.go:8 +0x24
runtime/internal/atomic.Xadd64(0x8a2024, 0x0, 0x0, 0xffffffff, 0x0)
/opt/hostedtoolcache/go/1.16.7/x64/src/runtime/internal/atomic/asm_arm.s:233 +0x14
github.com/amanjpro/zahak/search.(*Engine).ShareInfo(0x8982000)
/home/runner/work/zahak/zahak/search/types.go:55 +0x38
github.com/amanjpro/zahak/search.(*Engine).rootSearch(0x8982000, 0x10164)
/home/runner/work/zahak/zahak/search/search.go:144 +0x44c
github.com/amanjpro/zahak/search.(*Engine).Search(0x8982000, 0x64)
/home/runner/work/zahak/zahak/search/search.go:41 +0x4c
github.com/amanjpro/zahak/search.(*Runner).Search(0x8a2000, 0x64)
/home/runner/work/zahak/zahak/search/search.go:17 +0xf0
created by github.com/amanjpro/zahak/uci.(*UCI).findMove
/home/runner/work/zahak/zahak/uci/uci.go:249 +0x820
Al@RPi4-SSD:~ $
===========
Al@RPi4-SSD:~ $ ./zahak-linux-arm64-5.0
-bash: ./zahak-linux-arm64-5.0: cannot execute binary file: Exec format error
===========
Al@RPi4-SSD:~ $ ./zahak-linux-arm64-6.0
-bash: ./zahak-linux-arm64-6.0: cannot execute binary file: Exec format error
Al@RPi4-SSD:~ $
============
I’m using a Raspberry Pi4 running 32 bit Raspbian OS that is fully up to date with the latest software. I’ve compiled over 100 engines for the RPi for Picochess using lots of different Compilers.
Thanks for your time.
Al.

Hi,
Al@RPi4-SSD:~ $ go version
go version go1.10.1 linux/arm
Al.

Oh, this is very old version of GoLang, my engine has been tested with 1.16 and above
As for the version 5, it actually works if you send ucinewgame before sending go infinite, so please try that...
And I am currently trying to fix the version 6.0 issue, and will do a hotfix right after

Can you try this hotfix: https://github.com/amanjpro/zahak/releases/tag/6.1

Actually try that one instead: https://github.com/amanjpro/zahak/releases/tag/6.2

Hi,
Your older 32 bit v5 does run, I forgot the ucinewgame which I normally try on a failure. v6 does not run as you’re aware.
I quickly tried your v6.2 but the makefile refers to your original version not the fixes.
I’m away in Scotland now, so will try any fixes and try to upgrade GO when I return next week.
thanks for your efforts,
Al aka Scally on the forums.

Don't try make, just download this binary for raspberrypi 32bit: https://github.com/amanjpro/zahak/releases/download/6.2/zahak-linux-arm32-6.2

Hi,
yes that binary works thanks.
I’ve also update to go v1.17.1
Al.

Cool, thanks for confirmation. I'll close the issue :)

Thanks again.
go v1.17.1  didn’t work for me, however go 1.14.4 works, I can run Makefile and the go get command, both provide working binaries.
Al.

I have never tried Go 1.17, will try that later

Out of curiosity, are you running it on a DGT Pi?

I will be, I’m just home after a week away, so will be trying your engine tomorrow on my DGT Pi.
Al.
Sent from Scally's iPhone 11 Pro

On 12 Sep 2021, at 21:21, Amanj Sherwany @.***> wrote:

Out of curiosity, are you running it on a DGT Pi?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.

Cool, I'm really interested in your experience, as I also want to get a DGT Pi + DGT board setup :)

Hi Amanj,
I have emailed you on your email address given on your website. I think I spelt your name wrong, apologies.
Al.


Cabal 2.5 compat

@peti Could we get this on Hackage please? Thank you.

https://hackage.haskell.org/package/jailbreak-cabal-1.3.4


How to validate list of mnemonics?

Is there a method which helps to validate a given string of mnemonics?

Try the following:
let isValid = BIP39.mnemonicsToEntropy(mnemonics, language: language) != nil


patch bullet list rendering for clap_mangen

temporary fix for clap_mangen not rendering bullet lists correctly

Related Issues

closes #5095

Not an issue with clap_mangen. Someone should verify but the section that @sylvestre referred to that isn't being parsed correctly is completed by the help_section proc macro and our own parser for markdown. This should probably be fixed up instead of using my quick fix.
> rg test.md
src/uu/test/src/test.rs
25:const ABOUT: &str = help_about!("test.md");
39:const AFTER_HELP: &str = help_section!("after help", "test.md");


Warn: circular dependency: virtual:#imports

Suddenly got this warning I hadn't seen before updating from 0.5.0 to 0.5.5.

I only use google login and a custom apple flow based on a very simplified version of the one I had seen around here but these warnings are repeated for each provider. Would appreciate some advice.
    "nuxt": "^3.14.1592",     "nuxt-auth-utils": "^0.5.5",     "vue": "3.5.13",

Do you have these warning with npx nuxt dev or npx nuxt build? I cannot reproduce it


customizer of only used functions

It would be better if a customizer that would allow us to select only functions that we use and download ramda.min.js with only those functions. It would be even awesome if that customizer if part of  Ramda documentation.

@Rafi993, are you aware of http://ramdajs.com/#partial-builds?
@MattMS, note that the navigation bar prevents the link above from working nicely.

@davidchambers  this was the script I was talking about https://github.com/ramda/ramda/pull/2026.  I have created the pull request.


[ar] Translate ar index to arabic

This PR adds the minimal translation related to the file _index.md and splitting the old https://github.com/kubernetes/website/pull/44902 to smaller PRs
Part of https://github.com/kubernetes/website/issues/37546 and https://github.com/kubernetes/website/issues/44682

/language ar

/assign @seokho-son

/lgtm

/assign @adowair

/lgtm cancel

/lgtm
/hold
Feel free to remove the hold to merge as is or with the nits addressed. Thanks!

/approve
/hold

Feel free to remove the hold to merge as is or with the nits addressed. Thanks!

Comment addressed and the lgtm label removed after pushing can you relgtm ?
/hold cancel

/lgtm
Thank you!


XDoc: fix Jenkins xdoc-server build process

Currently, we test a server that does not include examples. We need to load a sever development baseline, run examples, and if they are green, then we build a minimal server image.

No we have successful build and deployment process:

And we also eliminated the below mentioned warnings:

There is only one left that require changes in Zinc or Pharo repositories:


Check if server "server name" is online or offline

Hi i'm having a inssue with the condition of if server "hub" is online:
code:
command /test:
trigger:
if server "hub" is online:
send "server Hub is online"
Minecraft version: 1.19.2
Server version: 1.19.2-R0.1-SNAPSHOT
Skript version: 2.6.3
Skungee version: 2.0.0-BETA-4

same issue, it always returns false. Using paperspigot 1.19.2 #246, Skript 2.6.3 and Skungee 2.0.0 BETA 4, no additional skript addons

ya right, it always returns to false

same here


Master to Live

Docs Build status updates of commit d19fa43:
:clock10: Full build: the average full build time is 11 min(s) 46 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit d19fa43:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/antispam-antimalware/Set-HostedContentFilterPolicy.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/encryption-and-certificates/Set-IRMConfiguration.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/mailboxes/Set-Mailbox.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/policy-and-compliance-retention/Start-ManagedFolderAssistant.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


SW-5780 Extract hardwired ID mapping helper function

Commit 0ae61309 modified AccessionImporterTest to maintain a mapping between
hardwired IDs and the actual IDs generated by the database, so it could check
for the correct references between entities. Pull that logic out into a helper
function so it can be used in other tests.

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#2270
#2269  👈
#2268
#2267
#2266
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @sgrimm and the rest of your teammates on  Graphite

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#2270
#2269  👈
#2268
#2267
#2266
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @sgrimm and the rest of your teammates on  Graphite

Merge activity

Aug 12, 4:51 PM EDT: @sgrimm started a stack merge that includes this pull request via Graphite.


N-API Support for websocket

The recently announced Node 8 has a new experimental feature called N-API which is aimed at reducing maintenance cost for node native addons. Checkout this blog for more details on its benefits.
Module websocket is one of the top 30 native modules by dependency count, and in order to help the Node.js community make the important transition to N-API, we are hoping you will be able to work with us in order to port websocket to support N-API. Your support and feedback is important in making this effort a success.
I am part of the N-API working group and and would like to talk to you about how you can can get started with N-API and what help we might be able to provide. I'm available to talk on the phone individually if you'd like. Alternatively, if you prefer, feel free to jump in our WG meeting which happens every Thursday at 1.30 Eastern / 10.30 Pacific US time, to discuss any issues.
Here’s a video of N-API in action

I'm currently on vacation in Hawaii. Will have to check into this sometime
when I get back! :-D
Brian
On Wed, Jun 7, 2017 at 8:20 AM, Sampson Gao<EMAIL_ADDRESS>wrote:

The recently announced Node 8 has a new experimental feature called N-API
which is aimed at reducing maintenance cost for node native addons.
Checkout this blog for more details on its benefits.
Module websocket is one of the top 30 native modules by dependency count,
and in order to help the Node.js community make the important transition to
N-API, we are hoping you will be able to work with us in order to port
websocket to support N-API. Your support and feedback is important in
making this effort a success.
I am part of the N-API working group and and would like to talk to you
about how you can can get started with N-API and what help we might be able
to provide. I'm available to talk on the phone individually if you'd like.
Alternatively, if you prefer, feel free to jump in our WG meeting
https://plus.google.com/u/0/events/c0eevtrlajniu7h8cjrdk0f56c8?authkey=COH04YCalJS8Ug
which happens every Thursday at 1.30 Eastern / 10.30 Pacific US time, to
discuss any issues.
Here https://www.youtube.com/watch?v=nmXhJ88nZsk’s a video of N-API in
action
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/theturtle32/WebSocket-Node/issues/284, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AADPwOTOnpmVEbod59Sk2KxzZSTvw9YIks5sBuoEgaJpZM4NzGKM
.

Hi @theturtle32, have you come back from your vacation yet?

@sampsongao
Both native modules used in this lib are extracted from https://github.com/websockets/ws.
Today these native modules are available as packages. See https://github.com/websockets/bufferutil / https://github.com/websockets/utf-8-validate.
It would be better if this lib could be refactored to use the packages as dependencies. Instead of porting to N-API in two places.

Hi @andreek, are you managing the https://github.com/websockets/ws repo? We would happy to help porting this module to N-API.

@sampsongao No, I'm just interested in N-API and started here. I've a complete port for utf-8-validate as fork here. I'll send the websockets team later a PR asking if they may want have it as branch in their repo.

This issue can be closed.


Delete Tag Feature

Model Component Enhancement:

Added deleteTag method in Model's API
Added JUnit tests
Note: Only model component is modified; UI and Logic are both not updated to handle command

Coverage decreased (-0.2%) to 91.99% when pulling 88b4bb9917e8287764505e66d5da872a6723141d on zenghou:deleteTagFeature into 20dc7c3bcbdb36a47a059a776766fc2432bd5a51 on CS2103-F11-B4:master.

According to Prof Damith, we can ignore code coverage for the time being.


authMethods.authProviders is not iterable

Starting version 0.22.0 I get "authMethods.authProviders is not iterable" when using the manual code exchange exemple for the authentication with Oauth2. No problem with the 0.21.5.

There is no longer authMethods.authProviders field. JS SDK v0.22+ is compatible only with PocketBase v0.23+ and introduced several breaking changes. Please refer to the JS SDK release notes or JS SDK CHANGELOG for more details.
If you are using PocketBase <= v0.22.x, then you have to pin your JS SDK version to <0.22.0.
For list of the breaking changes that PocketBase v0.23+ introduced and Go/JSVM upgrade guide, please refer to the PocketBase JS SDK CHANGELOG and its related links.

Ok Thanks ! (The documentation is outdated then ^^ )

Oh, you mean for the "Manual code exchange"? I'll update it a little bit later today.


Fix/resolve merge issue

Checklist

[ ] App update process has been followed
[ ] Target branch is develop
[ ] Application version has been bumped

@Z4karia can you take a look please ?


PS4 controller buttons don’t work and no my buttons work fine on my PS4

strange, it worked for me. use a usb cable like the one to charge the controller to pc, works.

I play on iPad with keyboard and it has no USB port
On Fri, Nov 27, 2020 at 3:48 AM github10omar<EMAIL_ADDRESS>wrote:

strange, it worked for me. use a usb cable like the one to charge the
controller to pc, works.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/sm64js/sm64js/issues/150#issuecomment-734719279, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ARXLH3GMQFEISMPCVLABQ6TSR5RWJANCNFSM4UEE3MJA
.

oh. put a usb converter cable then, it's for 5 bucks on stores

Thanks for the tip!
On Sat, Nov 28, 2020 at 12:18 AM github10omar<EMAIL_ADDRESS>wrote:

oh. put a usb converter cable then, it's for 5 bucks on stores
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/sm64js/sm64js/issues/150#issuecomment-735041603, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ARXLH3APGR4QA5VJG7WXQETSSCBYVANCNFSM4UEE3MJA
.

Welcome!

Hold the share and PS button to turn on pairing mode to your DS4.

I did that
On Fri, Dec 4, 2020 at 4:20 PM Meowlithius<EMAIL_ADDRESS>wrote:

Hold the share and PS button to turn on pairing mode to your DS4.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/sm64js/sm64js/issues/150#issuecomment-739026992, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ARXLH3CCWHEIHZN2QYTYFYLSTFHBPANCNFSM4UEE3MJA
.


Use fc -r instead of fzf --tac to speed up loadtime

Using fc -r instead of fzf --tac in the zsh history widget allows for faster load times and causes less screen flicker.

Merged, thanks!

@dsh2 : Hi I got problem from the change. When I pressed ctrl + r, fzf shows
fc: history events are in wrong order, aborted

Then I found it's caused by
$ fc -rl
fc: history events are in wrong order, aborted

After reverting to last version (the fc -l version), the ctrl + r function works fine.

More info:
I asked my friend for doing the same fc -rl test. They got the right output
~ ❯❯❯❯ fc -rl
16439  fc -rl
16438  fg ; /usr/local/bin/emacs --resume-layouts -nw
16437  tmux at
16436  emacs -nw

But we got the different version of zsh
zsh 5.2 (x86_64-ubuntu-linux-gnu) vs zsh 4.3.17 (x86_64-unknown-linux-gnu)
Will try to find out if related to the zsh versions 🤔

Hi, zsh 4.3.17 is very old (http://zsh.sourceforge.net/News/), you might want to consider upgrading it. Although not clearly stated, I have never tested the scripts with zsh 4, and have no plan of making them compatible with it.

After upgrade to zsh 5.4.2, still get the fc -rl problem
$ zsh --version
zsh 5.4.2 (x86_64-unknown-linux-gnu)

$ fc -rl
fc: history events are in wrong order, aborted

Maybe this is nothing about the zsh version.

You might want to check if your history file has some inconsistent, out-of-order entries as the error message suggests.

I've tried delete my ~/.zsh_history file before but still failed.
Finally I found I need to run fc -p to pop all of history data out as a force refresh.
Think the problem should be solved 👍

Update:
after fc -p, it still get broke after the next several command input ....
I think l'll need to use the fc -l version manually till I found the root cause :-/

@tokikanno I am sorry you are having trouble with the change. To me it seems the update of your outdated zsh did not succeed. The cited message is not contained in zsh for a few years, cf. https://github.com/zsh-users/zsh/commit/d60de3001#diff-4168e84085fbdc944a0837ed78337962L1656. Maybe you have parallel installations of zsh in /usr/bin and /usr/local/bin?

@dsh2 : You're damn right!!! 👍
I found I didn't update the shell configuration in tmux config. So I'm still using the old zsh under tmux.
Seems the fc -r problem did related to the zsh version, and upgrade to a newer version will fix it.
Thx for pointing out the parallel installations problem.


ssh error

Does this occur consistently?
Repro steps:

select vm
right-click -> Connect to Host via Remote SSH

Action: azureVirtualMachines.openInRemoteSsh
Error type: Error
Error Message: Internal error: Expected value to be neither null nor undefined: id
Version: 0.3.0
OS: darwin
OS Release: 20.3.0
Product: Visual Studio Code
Product Version: 1.54.1
Language: en

Call Stack
nonNullValue extension.bundle.js:16:26986
Object.nonNullValueAndProp extension.bundle.js:16:27215
VirtualMachineTreeItem.<anonymous> extension.bundle.js:16:68505
fulfilled extension.bundle.js:16:66608
processTicksAndRejections task_queues.js:97:5

I'm unable to reproduce this with those repro steps.  Could you provide more detailed repro steps and more information about your VM?  What distro are you using?
Also I would like to verify that you have the Remote - SSH extension installed.

@nturinski IMO it's on us to investigate "Internal error" regardless of if there are repro steps - since these errors are never meant to happen and never meant to be shown to users. Just look for uses of nonNullProp and id and we should be able to narrow it down.

Note:  After some investigating, I think that this is happening because when we get the IP address, we use the id.  I'm not sure why the id is not defined in this case, but that's the most likely entry point since openInRemote doesn't directly access the id.  The linked duplicate issue describes a specific VM, so use that for investigating.

Currently facing this issue due to being connected to the company's private network via VPN essentially making the extension useless as all the VMs are on a private vnet.
As @bryanburke mentioned in #273

Would adding an opt-in setting such as azureVirtualMachines.showAdvancedOptions or similar make sense? Any users who enable that setting (or who are instructed to do so by their DevOps platform team, for example) would see additional commands like Create Virtual Machine (Advanced, Private IP), Copy IP Address (Advanced, Private IP), and Connect to Host via Remote SSH (Advanced, Private IP). Perhaps some type of warning message or popup could accompany the opt-in for that setting to reduce any confusion from accidental use (e.g., "only enable this if you know what you are doing!").

This would be a great option so that users with private VMs can actually use the extension. It's surprising that this is an issue in the first place.


Unable to get the type of List/Set/Map added as parameter to a method

Hi Andy
I can see that the Parameter class has only two variable defined i.e. name and type. This works fine for any primitive data types but doesn't work well for any collection parameters as there isn't any reference for the type of collection parameter.
For e.g. if a method is defined as:
public void exampleMethod(List(String) paramStr, List(sObject) sObjects) {
// Sorry, wasn't able to specify it as List<>
}
When I'm trying to retrieve the parameters for the method using SymbolTable, I'm able to get Parameter as:
(Parameter:[name=paramStr, type=LIST],
Parameter:[name=sObjects, type=LIST])
Is there any way I can get the type of Lists (i.e. List(String) or List(sObject)) in this example? It would be really helpful if you could let me know any other property that I'm missing over here.
Thanks in advance.

Sadly the Salesforce Tooling API does not expose this, so there is nothing this wrapper can do about this. Worth raising on Ideas Exchange i would say!


Multi-Language Support

The export of multiple languages requires a lot of actions on the user sides

If I need to export multiple languages from excel files I need to create multiples copies of the same file, and convert one by one the excel files to ts files.

Suggestion

Instead of using the Translation keyword in the excel files, use directly the language codes (e.g.: en_GB, en_US, fr_FR ....)

Convert Ts to Excel

The same feature could be usefule when importing the multiple ts files to a unique excel files

I think this could be better solved with #53 . If this is implemented you can run a script for every language.
You may have the case that you have one translator for all languages. But normally you have one for each at least in my experience.
It could even be a an option like you simply specify more out files then one for each language and in the return you you just let let it run with a wildcard. like so:
$ qTsConverter ts-xlsx myfile-[ja,de].ts # convert  file myfile_ja.ts and myfile_de.ts to myfile_XX.xlsx
$ qTsConverter xlsx-ts myfile-[ja,de].xlsx # convert  file myfile_ja.xlsx and myfile_de.xlsx to myfile_XX.ts


Fix toctree warnings and render toctree in the HTML sidebar

This PR fixes a warning about the library API document not being included in the document, and also fixes the sidebar rendering (table of content shows up in the sidebar correctly).
These two issues are connected because the Sphinx html theme uses the :toctree: directive to create the sidebar.
References:

Exhale, link to generated documentation API: https://exhale.readthedocs.io/en/latest/usage.html#make-your-documentation-link-to-the-generated-api
Sphinx rtd theme, table of content options: https://sphinx-rtd-theme.readthedocs.io/en/stable/configuring.html#table-of-contents-options

Signed-off-by: Abrar Rahman Protyasha<EMAIL_ADDRESS>

@wjwwood can you merge the PR?


Update eslintrc

Description of the change
The previous PR was missing the eslint update for some reason.

Checklist:

[ ] Added the change to the changelog's "Unreleased" section with a reference to this PR (e.g. "- Made a change (#0000)")
[ ] Linked any existing issues or proposals that this pull request should close
[ ] Updated or added relevant documentation
[ ] Added a test for the contribution (if applicable)

🏓 @JordanMartinez @thomashoneyman  I think this got unnoticed due to the github outage

Yeah, looks like it.


Feature: Choose nickname when creating teacher tokens

Related user(s):
@erikmd
Related issue(s) or PR(s):
No response
Related project scope(s):
teacher dashboard
The problem:
Unlike the student token feature, the teacher dashboard does not ask for nicknames at their creation time.
Wanted solution:

Open an input dialog before proceeding to the creation of an extra teacher token?

Considered alternatives:

Open a multi-line input dialog (in CSV format or so) to take as input a list of nicknames, (optional) desired teacher tokens ?

Additional context:
No response

Closed by https://github.com/ocaml-sf/learn-ocaml/pull/549/commits/c341fcaf6d3da48edceaf37131869d9137277464 from https://github.com/ocaml-sf/learn-ocaml/pull/549


Use xdotool instead of cat when CM_OUTPUT_CLIP

This allows pasting directly in other non-terminal programs. For example a browser's address bar.

Hi there! Please maintain backwards compatibility of options :-)
It's also not acceptable to make xdotool mandatory, sorry. Please see how we already handle similar cases elsewhere.

Closing without prejudice due to lack of response to feedback.

I wouldn't do this in clipmenu itself.  You should be able to assign this to however you launch clipmenu in your WM or DE.  For XMonad, I linked the following to my desired keybinding:
spawn "clipmenu && xdotool key Ctrl+v"
Replace "Ctrl+v" with whichever key binding you use for pasting.

Thanks! ... && xdotool key Ctrl+v works flawless! I use xdotool anyway for various scripts.

For case of interesting - text typing works with xdotool type ..., just needs '\r' replaced with '\r'. Though it may cause strange problem after use - when I did it against leafpad editor, it did not react to more key presses for short time, also Ctrl+Backspace did not work few times, when I used it to delete pasted text.

I'm experimenting with clipmenu, trying to extend its own rofi-script mode with some operations. Of course, not sure if they are necessary to be right in that file.
This is snippet from case $ROFI_RETV block (in this case assigned to 2nd custom command):
11) chosen_line="$1"
        sed -E 's|(["\$])|\\\1|g
                s|$|\r|
                1s/^/xdotool type --clearmodifiers --delay 20 -- "/
                $s/$/"/' \
        < "${cache_dir}/$(printf '%s\n' "$chosen_line" | cksum)" | sh >/dev/null &
        exit;

Sure, 3rd mouse button simulation would be also useful. Or even more reliable (if any text is placed to selection - mouse paste works in far more cases).


Switch from protoc to protobuf.js

https://github.com/protobufjs/protobuf.js
https://github.com/improbable-eng/ts-protoc-gen/issues/237

Because of the incompatibility with TypeScript, we're blocked on moving to commonjs_strict. From some quick skimming, it looks like we can move to protobuf.js instead of protoc generated protobuf definitions. The downside is this looks to be a much more invasive refactor as the APIs are pretty different and the vast majority of what this SDK does is protobuf manipulations.
The good news is we actually are in the middle of a large-ish refactor of this project but it hasn't gotten a lot of attention from us lately. This is probably something that needs to be done as part of that refactoring effort.
cc @ChALkeR

This is being done in develop


Adding filter to the toString() method of KnnFloatVectorQuery

Addresses the issue #13983

Could you update the byte knn query & DiversifyingChildern* knn queries as well?

I made the changes fo DiversifyingChildren*, but by byteknn do you mean ByteVectorSimilarityQuery?

I believe that @benwtrent meant KnnByteVectorQuery.

I hope I got all of them now.

Could you update the byte knn query & DiversifyingChildern* knn queries as well?

Unrelated: I noticed that the DiversifyingChildren* queries don't use the filter to evaluate the query, is this a bug?

Unrelated: I noticed that the DiversifyingChildren* queries don't use the filter to evaluate the query, is this a bug?

I am unsure what you mean by this? The filter is utilized when building the accepted docs set in the super() classes.

I think a CHANGES entry is in order. This seems like a nice little bug fix to aid folks in debugging issues.
@viswanathk once you add the changes entry, I can merge and backport to 10.x

@benwtrent Added in CHANGES for 10.1. Also corrected some git history mess up.


Added Animals script for Swift.

Swift does not have abstract classes or methods, so here is my first go at it.

I like it, nice job.


Package page: a white page and multiple errors in the browser console

It happened when I tried to open https://constructs.dev/packages/@pahud/cdktf-aws-eks. It redirected me to: https://constructs.dev/packages/@pahud/cdktf-aws-eks/v/0.2.42?lang=dotnet and then all the errors appeared .
When I refreshed the page the page was displayed without any issues. I guess it's related to the caching problem

Not able to currently reproduce the white page issue. Some of these errors appear to be related to our analytics, and the other errors for "Invalid content type: text/html" are expected errors that we explicitly throw when documentation is not available for a given language:
https://github.com/cdklabs/construct-hub-webapp/blob/579f570fe1fe14226dd7bd4dc24d9f1bc7283c1f/src/api/package/docs.ts#L33

Based on my understanding, the only reason this could happen is if the backend is somehow updating the catalog.json to include a version of a package before the docs have been made available - I don' think this could be a result of caching. Additional investigation needed

Going to close this as I haven't been able to repro the blank page either


Autoshrink for Label doesn't work.

It's very cool label.
but I have a problem, Autoshrink(minimumFontScale) doesn't work. It shows fixed font size.

+1

Is this feature implemented is some other branch or is still in TODO list?

Sorry, I'm not working on this. Maybe next month. :smile:

@lexrus That would be nice. Please let me know. Thanks!

Yeah this is a great little project I want to use in my app but can't because of the lack of sizing change. I'm fairly competent, what are people's thoughts on the matter? I tried doing something like
let size: CGSize = (myLabel.text! as String).boundingRectWithSize(
	CGSize(width: self.view.frame.size.width, height: 999999.0),
	options: NSStringDrawingOptions.UsesLineFragmentOrigin,
	attributes: [NSFontAttributeName: self.myLabel.font],
	context: nil).size

if (size.width > self.myLabel.bounds.size.width) {

	print("Yep")
}

And this works (the code with do with some tweaking); It checks whether the size of the string is larger than the frame to be putting it in. How to change the font until it's small enough to fit is a bit trickier. I tried using a for loop to constantly check but this gets rid of the animation for some reason. Hopefully this speeds up the process ;) and thanks again for making this, really cool project!

@SunburstEnzo Thank you for your advice.
But how does the OS figure out which FontScale value properly fit in current rect?
I guess we can take the advantage of CoreText which has some great functions to deal with properties of each character of a attributed string. But it'll be a breaking change.
See also:
https://github.com/overboming/ZCAnimatedLabel/blob/master/ZCAnimatedLabel/ZCAnimatedLabel/ZCCoreTextLayout.m

Any progress on this issue?

Forgot about this so gave it another go just now
var size: CGSize = myLabel.text.boundingRectWithSize(CGSize(width: CGFloat.max, height: myLabel.bounds.height), options: NSStringDrawingOptions.UsesLineFragmentOrigin, attributes: [NSFontAttributeName: myLabel.font], context: nil).size
		`if (size.width > myLabel.bounds.width) {

			print("Yep")

			while size.width > myLabel.bounds.width {

				myLabel.font = myLabel.font.fontWithSize(myLabel.font.pointSize - 1)

				size = myLabel.text.boundingRectWithSize(
				CGSize(width: CGFloat.max, height: myLabel.bounds.height),
				options: NSStringDrawingOptions.UsesLineFragmentOrigin,
				attributes: [NSFontAttributeName: myLabel.font],
				context: nil).size

				myLabel.setNeedsLayout()
			}
		}
		else {

			print("No")
		}`

So what this does is reduce the font size so that it fits inside the label's width. I need to add a way to go back up to a larger font size instead of staying at tiny when going from long string to short 😜 this should get you by for now

I'm still waiting that "label.adjustsFontSizeToFitWidth = true" is working with LTMorphingLabel :dancers:

+1

Okay this is what I ended up temporarily doing.
This doesn't support shrinking space between letters, and doesn't work correctly if you set text anywhere before viewDidLoad. I have only tested it with .Evaporate effect.
//
//  ShrinkingLTMortphingLabel.swift
//

import Foundation
import LTMorphingLabel

// LTMorphingLabel doens't support autoshrink natively.
// BUG: https://github.com/lexrus/LTMorphingLabel/issues/14
// Emulate the behaviour manually.
// Will take minimumScaleFactor in consideration.
class ShrinkingLTMortphingLabel: LTMorphingLabel {

	// MARK: - Properties

	/// Original font for the label before any adjustment took place
	var originalFont: UIFont? = nil

	/// Trigger font-resize on text change
	override var text: String? {
		get {
			return super.text
		}
		set {

			// You do not want to change the order of next two strings
			if newValue != nil {
				adjustFontSizeToFitText(newValue!)
			}

			super.text = newValue
		}
	}

	// MARK: - Init
	// Save original font size.

	override init(frame: CGRect) {
		super.init(frame: frame)

		originalFont = font
	}

	required init?(coder aDecoder: NSCoder) {
		super.init(coder: aDecoder)

		originalFont = font
	}

	// MARK: - View Lifecycle
	override func layoutSubviews() {
		super.layoutSubviews()

		if text != nil {
			adjustFontSizeToFitText(text!)
		}
	}

	// MARK: - Methods

	/**
	Does the actual adjustment work.
	*/
	private func adjustFontSizeToFitText(newText: String){

		guard adjustsFontSizeToFitWidth, let originalFont = originalFont else { return }

		let desiredWidth = getDesiredWidthForText(newText)

		if frame.width < desiredWidth {
			// The text does not fit!
			let scaleFactor = max(frame.width / desiredWidth, minimumScaleFactor)

			font = UIFont(name: originalFont.fontName, size: originalFont.pointSize * scaleFactor)
		}
		else{
			// Revert to normal
			font = originalFont
		}
	}

	/**
	Calculates what the width of the label should be to fit the text.

	- parameter text:	Text to fit.
	*/
	private func getDesiredWidthForText(text: String) -> CGFloat {
		let size = text.boundingRectWithSize(
			CGSize(width: CGFloat.max, height: frame.height),
			options: [NSStringDrawingOptions.UsesLineFragmentOrigin],
			attributes: [NSFontAttributeName: originalFont!],
			context: nil).size

		return ceil(size.width)
	}
}

+1 ~~~waiting too


Port to Reanimated v2

This is a complete rewrite to take advantage of Reanimated v2, and to extract logic into separate hooks and components.
To be published as 3.0.0.

[x] Item can be dragged
[x] Spacer is inserted with correct size/index
[x] Placeholder is inserted at spacer index with correct size if renderPlaceholder exists on props
[x] Item animates to correct place on drag end
[x] List updates in response to dragged data
[ ] List autoscrolls when at top/bottom edge
[ ] Correct types
[ ] Performance: Clean up context state—create separate providers for things that change + things that don't

Bugfixes:

[ ] Fix flicker + buggy animations on next render after drag end
[x] Fix placeholder flicker on start drag
[ ] Fix sporadic undefined item

v2 migration may be blocked until android performance issues are addressed: https://github.com/software-mansion/react-native-reanimated/discussions/1632

v2 migration may be blocked until android performance issues are addressed: software-mansion/react-native-reanimated#1632

v2 migration may be blocked until android performance issues are addressed: software-mansion/react-native-reanimated#1632

I'd still be happy to help testing v3-beta 👍

@nelsonprsousa thanks! I'll let you know when it's ready to start testing.

quick update here, I'm giving priority to a v2-compatible rewrite in v1 before circling back to this: https://github.com/computerjazz/react-native-draggable-flatlist/pull/281
Besides v2 having some perf issues, the v1 update will lay the groundwork for most of the architectural changes here.

@computerjazz , please can you tell me if this new branch (which I understand would become the v3.0) will remove the warning "ReactNativeFiberHostComponent: Calling getNode() on the ref of an Animated component is no longer necessary. ...".
And sorry for the newbie question: can I install this branch to test it in advance ?
Many thanks


Question: how to best run globally installed npm module?

Hi,
I know this is not exactly the main use case for nodenv (quite the contrary), but I'm wondering what is the best way to run a globally installed npm module for local dev?
Say I do npm install -g foobar
Assuming I'm currently using global node 16.3.0, this will make foobar executable available under ~/.nodenv/versions/16.3.0/bin/foobar.

As a workaround, I could either npx foobar or create a bash function that does cat ~/.nodenv/version in subshell to locate the good folder, but I'm wondering if there's a built-in way to do just this that I missed?

I won't hold up any of these options as "best" but I'll share a couple options.
Firstly I'll reiterate the assumption that global packages should be rare. The only packages (IMO) that should be installed globally are those that expose CLIs meant to be used outside of a project. That is, generally only project scaffolding tools. CLI utilities that are used within a project should generally still be added as development dependencies. Then you can add the projects node_modules/.bin/ to your PATH (within that project) to make those CLIs available.
But to the original question...

One option is to install these (hopefully few) global packages in every nodenv version. This is reasonable if you don't typically run a lot of different nodes, and/or you have a very limited set of global packages. There is a plugin that facilitates this flow, such that each time you install a new node, it will automatically install a list of selected global packages: https://github.com/nodenv/nodenv-default-packages

Another option is to install a system node outside of nodenv, and use this node for all global packages. I use this flow myself, with a node installed via homebrew. I have nodenv configured such that system is my default node; and all my global packages are installed via NODENV_VERSION=system npm i -g foo

There's also a third option that I think is the "correct" approach, despite it being experimental and definitely not battle-tested. The theoretically "pure" approach is that global node packages represent system utilities. As such, they should technically be managed by your system dependency manager (ie, homebrew on macOS). IMO, it's a bit of a hack for these global packages to be installed through npm. The ruby community had this same problem over a decade ago with rubygems being used to distribute "system" packages. https://github.com/sportngin/brew-gem was built as a "hack" to leverage homebrew to be the package manager, even though installation was through rubygems. I forked this and modified it to use npm, though I haven't really ironed out the kinks or "publicized" it. https://github.com/jasonkarns/brew-npm Might be worth a look.

Thanks for a detailed writeup! All options are interesting and have their advantages. I feel like option 2 is the simplest.
I feel like your writeup deserves to be added to the docs.

What if nodenv used symlinks so that the bin directory of the current version of npm for that shell, or at least the global one, resided at some fixed path? E.g., it could exist at shims/bin, and then one just needs to add ~/.nodenv/shims/bin to the path, or else have it automatically added in nodenv init -

@michaeleisel If I understand you correctly, you're proposing that a single directory (~/.nodenv/shims/bin) point to dynamic path. So in that case, when the "active node" changes, the symlink would be modified to point to a different node's global modules?
A couple problems with that (assuming I interpreted the suggestion correctly):

user has two terminals open. terminal 1 is using node 14, terminal 2 is using node 16. which one does the symlink point to? (remember, symlinks are on disk. they can't have different states based on environment variables)
even if ^^ were possible to resolve, this presumes there is some hook that triggers nodenv to "switch nodes". That's not the way nodenv works. In fact, it intentionally does not use hooks of any kind precisely because of their buggy nature.

rvm was notoriosly buggy and super complex because it relied on "hooking" into directory-change events to switch versions. note, bash doesn't actually have cd hooks, they are approximated by wrapping the cd builtin with a function that could then do things. wrapping builtins is brittle. Which is why rbenv was written with a different architecture: shims. Instead of pre-emptively changing environment variables when you change directories, rbenv (and hence, nodenv as its fork) does nothing! Instead, nodenv's shims (for node, npm, npx, etc) are first in your PATH. When you invoke node, the node shim invokes nodenv to ask "what version should be active?". nodenv at that point, consults (in order) NODE_VERSION env var, .node-version files (up ancestors to / root), any plugins, and finally $(nodenv root)/version. After it has determined which node version is active, it essentially proxies the command over to that node.
Since everything is done at the moment you invoke the shim, there isn't any moment in advance of that which could modify the symlink.
However, this does hit on a hint of an idea. Nodenv already shims all globally-installed modules. It's that very shim that is being invoked when you run, say, ember, and when nodenv resolves what node version is active, it delegates to that version's node_modules/bin/ directory. If ember isn't installed in that version, you get the error.
So let's say we write a nodenv-plugin that, while nodenv is figuring out which node version to use, the plugin is able to inspect what the command is (ember), and override the node version if ember isn't installed? This is only a half-thought because I'm pretty sure the current exec and which hooks short-circuit the plugins (which means the plugin might not have a chance to alter the version by the time the plugin runs). But it's been a while since I was poking at the hook code. So @michaeleisel , if you want to pull a little harder on that thread, we might have a nodenv-floating-globals plugin!


ER/T terminators sometimes spin when connected to controller cluster

Sometimes ER/T terminators seem to get caught in a create/delete loop when in a cluster. Seems to happen when creates/deletes are against the cluster leader.

Being fixed in #2121


Specify a different name for each ALZ Monitor Resource Group?

Check for previous/existing GitHub issues

[X] I have checked for previous/existing GitHub issues

Description
Currently in the alzArm.param.json file, we are able to provide a value for "ALZMonitorResourceGroupName".
This sets the name of all ALZ Monitor resource groups, meaning that each RG has the same name across all subscriptions.
Is it possible to provide a different name for each subscription or each management group at least?

Hello @Greg-Court ,
thanks for your feedback. We will look at your request and let you know.
Thanks,
Bruno.

@arjenhuitema could you please comment

Hi @Greg-Court,
Thank you for your input. We have considered it and while the adaptability of this proposal is interesting, it's not possible for us to adopt it.
Implementing a different resource group name for each subscription or management group would necessitate the programmatic inclusion of the subscription or management group name, or ID, into the name of the resource group. Although technically possible, it may not be favored by all users.
Each organization has different naming standards, abbreviations and practices, it is impossible for us to align with all standards, this is why we usually use and default to CAF naming conventions and abbreviations  for resources.
I am going to close this issue now. Thank you again for your feedback, and if there are any more questions, please feel free to ask.


SSL Options on supervisor connection

Because of this line I can't pass the valid ssl_opts keyword list to Rihanna, making it impossible to be used with ssl for myself.
IMHO the fix would simply be to add :ssl_opts here since you already take :ssl option. This would work for MY scenario, but it is important to notice that there are several other options that Postgrex accepts for starting a connection. So, the proper fix here might be to add all of them.
Without this I can't use Rihanna. Since we are not actually testing Rihanna with all possible connection setups, I can open a PR only adding the key if desired. Though it would be better if a maintainer could do it because, if possible, I'd need that on a PATCH or MINOR release.
Thanks for your work!

Thanks for the report! Let's get this fixed.

Hi @lpil ! Me again. Sorry for all the trouble.
The SSL configuration is properly working now, but with taking all the options, I now have to exclude the pool configuration when I am running tests. Otherwise it tries to start with Ecto.Adapters.SQL.Sandbox which won't work on this line. It tries to create a connection with the pool being Ecto.Adapters.SQL.Sandbox though Sandbox does not implement a child_spec function. In the end it fails here.
Anyway, all I am currently doing is:
    Supervisor.start_link(
      [
        MyApp.Repo,
        {Rihanna.Supervisor, [postgrex: MyAppRepo.config() |> Keyword.drop([:pool])]}
      ],
      strategy: :one_for_one,
      name: MyApp.Supervisor
    )

In my humble opinion, the way things are now is the right approach, but people might get surprised for their tests failing because of this change. So, here I am trying to warn you people. Maybe the best approach would be to ONLY take extra :ssl_opts for this not to be a breaking change.
I'd advise to rollback this solution to the one only taking the :ssl_opts and retire version 1.3.3 from hex as it will break current setups.
Once again, sorry for all this trouble. If you need any help with setting things up for a SSL test setup then I'd be glad to help with it.

Just to let know that I find it very awkward that Ecto.Adapters.SQL.Sandbox does NOT implement a child_spec and that this fails at all... not sure we should bring this to the Ecto people.
Thanks!

Makes sense. Could you supply a PR please? :)

We could always drop the pool in the supervisor- don't want to ever use a pool as that would break Rihanna.

I'm okay with droping the pool.


Fix on month change firstDay issue

When month firstDay attributes wasn't pass to buildMonth() function, this cause a reset of this settings.

Thanks @Daaru00 !


GSD Request

--- GSD JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from v5.5 to before v5.10.84",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=a0a62ee15a829ebf8aeec55a4f1688230439b3e0",
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=77731fede297a23d26f2d169b4269466b2c82529"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "a0a62ee15a829ebf8aeec55a4f1688230439b3e0",
      "note": "introduced"
    },
    {
      "type": "commit",
      "value": "77731fede297a23d26f2d169b4269466b2c82529",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "net/smc: fix wrong list_del in smc_lgr_cleanup_early\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v5.10.84 by commit 77731fede297a23d26f2d169b4269466b2c82529, it was introduced in version v5.5 by commit a0a62ee15a829ebf8aeec55a4f1688230439b3e0. For more details please see the references link."
}
--- GSD JSON ---

This issue has been assigned GSD-2021-1002497


Recent update breaks zotxt

Debug log ID
ICIP9EVP-euc/6.7.143-6
What happened?
Thank you for your wonderful work.
I believe a new release of better bibtext has broken something in zotxt. The key issue seems it might be TypeError: zotero.BetterBibTeX.KeyManager.keys.findOne is not a function.
My setup:
Zotero 6.0.30
Better BibTex for Zotero 6.7.143
zotxt 6.0.2
I am accessing zotxt through the pandoc-zotxt.lua filter in emacs 29.1 on Windows 10.
The filter should find entries in Zotero from their citekeys in my markdown file, and generate a bibliography. Now the debug log says that it is unable to find any entries.
Here is the debug log:
(5)(+0062999): GET /zotxt/items?betterbibtexkey=yerushalmi_Introduction_2013 HTTP/1.1 Host: localhost:23119 Accept-Encoding: gzip

(3)(+0000004): TypeError: zotero.BetterBibTeX.KeyManager.keys.findOne is not a function findByBBTKey@chrome://zotxt/content/modules/Core.jsm:217:18 itemsEndpoint/<@resource://gre/modules/addons/XPIProvider.jsm -> jar:file:///C:/Users/alexanderkaye/AppData/Roaming/Zotero/Zotero/Profiles/79uiu4p8.default/extensions/zotxt@e6h.org.xpi!/bootstrap.js:420:24 itemsEndpoint@resource://gre/modules/addons/XPIProvider.jsm -> jar:file:///C:/Users/alexanderkaye/AppData/Roaming/Zotero/Zotero/Profiles/79uiu4p8.default/extensions/zotxt@e6h.org.xpi!/bootstrap.js:419:13 handleErrors/<@resource://gre/modules/addons/XPIProvider.jsm -> jar:file:///C:/Users/alexanderkaye/AppData/Roaming/Zotero/Zotero/Profiles/79uiu4p8.default/extensions/zotxt@e6h.org.xpi!/bootstrap.js:300:18 Zotero.Server.DataListener.prototype._processEndpoint<@chrome://zotero/content/xpcom/server.js:526:26 Zotero.Server.DataListener.prototype._headerFinished@chrome://zotero/content/xpcom/server.js:302:5 Zotero.Server.DataListener.prototype.onDataAvailable@chrome://zotero/content/xpcom/server.js:208:7

(5)(+0000002): HTTP/1.0 500 Internal Server Error X-Zotero-Version: 6.0.30 X-Zotero-Connector-API-Version: 2 Content-Length: 0

I apologize because I think this might be something that the zotxt developer needs to fix. I posted an issue there too and have not had a reply from the developer yet. Someone did post a suggestion in that thread, but I have been unable to fix the problem myself by modifying the zotxt xpi package. I am posting here in case you are able to fix the problem on your end.
Very many thanks.

If the code is just trying to get the citation key, use this:
try {
  return item.getField('citationKey')
} catch (err) {
  return undefined
}

Sorry for the disruption. This code is future-proof and will also automatically work with the formal citation key field when it comes to Zotero.

I will look tomorrow whether I can put a shim in place. But it'd be better to use the future-proof code.

Thank you so much for the very quick response.
Could you advise on how to implement the code your recommendation?
As far as I can tell, the problematic line in zotxt is in extension/content/modules/Core.jsm (here).
The relevant line at 215 is:
function findByBBTKey(citekey, zotero) {
    let libraryID = zotero.Libraries.userLibraryID;
    let itemId = zotero.BetterBibTeX.KeyManager.keys.findOne({ libraryID, citekey }).itemID;
    return zotero.Items.getAsync(itemId);
}

Which part do you recommend I replace with your code?
Thank you for the more detailed advice.

Ah that's different. I will have something tomorrow.

See https://github.com/egh/zotxt/pull/42

Thanks again for working on this. I am still having trouble.
See debug log M6IRRXC2-euc/6.7.143-6
The key lines are:
(5)(+0091297): GET /zotxt/items?betterbibxkey=yerushalmi_Introduction_2013 HTTP/1.1 Host: localhost:23119 Accept-Encoding: gzip

(5)(+0000002): HTTP/1.0 400 Bad Request X-Zotero-Version: 6.0.30 X-Zotero-Connector-API-Version: 2 Content-Type: application/json; charset=UTF-8 "No param supplied!"

It could be I am doing something wrong. I took your pull request and compressed the extension directory into a zip file, then changed the extension to xpi and loaded it as an add-on to Zotero. If I am doing something wrong, please let me know and I will retry.

zotxt doesn't work for me at all, it's not installing the HTTP endpoint. I built it using make notest, but all that does is zip things up. But we should continue the conversation on the zotxt project, there's nothing to change about BBT to fix the problem, and the zotxt author will have to get involved, if only to merge the PR.

betterbibxkey=yerushalmi_Introduction_2013

this isn't right in any case, zotxt supports betterbibtexkey and citekey for citation key search

I know that's not conventional better bibtext or citekey syntax but if I am reading the manual correctly, (perhaps I'm not,) zotxt should recognize it if I have pinned the key. In any case, I agree that I don't think this is the fundamental issue. I'll continue on the zotxt issues site as you suggest.

No I mean your URL has betterbibxkey where it should be betterbibtexkey.

But other than that yeah I really can't do much, zotxt will need to be updated. I don't know why it doesn't initialize properly for me, I see no errors.


Fix test runner expectation failure handling

The integration test runner incorrectly reports the test as a pass if a failing expectation is followed by a success.
I've tidied up the output if multiple expectations fail too.

Pull Request Test Coverage Report for Build 833

0 of 0   changed or added relevant lines in 0 files are covered.
6 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.4%) to 68.136%

Files with Coverage Reduction
New Missed Lines
%

terraform_compliance/common/defaults.py
6
80.65%

Totals

Change from base Build 830:
0.4%

Covered Lines:
1005

Relevant Lines:
1475

💛  - Coveralls


Handle creating many counterparts and synchronizing groups

Any review?

LGTM

Thank you for the review @fredj.


Simplify hops-template-react

This PR removes graphql and flow type annotations from the hops-template-react.
Related: #276 #277

@dmbch done - please take a look.


feat: add telemetry commands

Fixes DEVX-1480
Adds new wrangler telemetry disable and wrangler telemetry enable commands which globally toggle telemetry collection across all projects on that machine.
Adds a new wrangler telemetry status command which shows the current telemetry setting, resolved to the current project.
With send_metrics set in wrangler.toml

With WRANGLER_SEND_METRICS environment variable set

Without either send_metrics or WRANGLER_SEND_METRICS set

We prioritise env var > wrangler.toml > global setting via command.
NB we're using a feature branch so will add one changeset when we merge that in.

Tests

[ ] TODO (before merge)
[x] Tests included
[ ] Tests not necessary because:

E2E Tests CI Job required? (Use "e2e" label or ask maintainer to run separately)

[ ] I don't know
[ ] Required
[x] Not required because:  no existing e2e's, adequately covered by unit tests

Public documentation

[ ] TODO (before merge)
[ ] Cloudflare docs PR(s):
[x] Documentation not necessary because: currently hidden. Will add later.

For posterity, there is no changeset as this is merged only into a feature branch.


MINOR: removed code duplicates from several files (KafkaStreams)

This PR offers following to KafkaStreams project:

removed code duplication from TopologyBuilder's function makeNodeGroups (extract function)
removed code duplication from GlobalProcessorContextImpl and from ProcessorContextImpl to parent class AbstractProcessorContext (move method to parent)

Any updates on this PR?

@wlsc sorry for being late on reviews, could you rebase your code on latest trunk?

@guozhangwang hi. thank you for the review, but my copy/branch of Kafka was already deleted.
If you don't mind, I could create another PR and link it here.
Would be that ok for you?

@guozhangwang I've created another PR for this. Please check the https://github.com/apache/kafka/pull/4357 PR.

@mjsax sorry, I had to close this actually. I will do your PR changes also in the second PR.


README - comment for Join example

I found "Join" to be a tad confusing for something that basically unbundles collections. Your other references to Linq equivalents are helpful, so I thought this might be helpful here. Thanks!

I like where you're head is at here, but I'm worried that it could be confusing?
It's less an analog for .SelectMany() and more closely related to DataFlow batching and joining.
I'll reconsider adding more clarity around what .Join does.

I made some more updates to the Readme in the master branch.
Thanks for the feedback. :)

Great additions, added some much needed clarity!

Thanks for caring and chiming in with your ideas. :)


Any single label is considered a TLD

Is there a rationale behind this behavior? Why not use the existing TLD list instead of a match-all rule[1]?
I'm not sure the following statement holds truth: psl_is_public_suffix(ctx, "localhost")
Currently, that means that libcurl drops any cookies from localhost etc.[2] when built with libpsl support.
[1] https://github.com/rockdaboot/libpsl/blob/master/src/psl.c#L810
[2] https://github.com/curl/curl/blob/master/lib/cookie.c#L801
/cc @remicollet, @bagder

According to the documentation: "This function checks if domain is a public suffix by the means of the Mozilla Public Suffix List." and "localhost" is not a public suffix, so I would argue that the function should then return false.

Algorithm , Point 2. Says if no rules match, the prevailing rule is "*".
Do I interpret this sentence wrong ?

Hi, which document are you referring to?
Thank you!

The more I think about all that, it seems that such an API should only be used with FQDNs.
Say, you query a host named com in the domain local and e.g. local is in your DNS search path, how should anything but the caller know that we actually mean com.local?
...and would the server send a cookie with domain=com? Could be if some server-side logic detects, that we're accessing com and not com.local or maybe it doesn't even send a domain, so how's that usually (with regards to cookies) handled?
/cc @bagder

In cookies the domain attribute is tail matched with the host name used in the URL and I don't think there's ever any guarantee that it is in fact a FQDN. It is even not that easy to figure out since the name resolving functions etc don't tell us that very easily. But yes, the PSL matching pretty much assume that we give it a true and global domain name. Which, if we access public URLs, we will - but in private circumstances we may not always...

Looking at the provided test data, it seems that single-label names do not match at all:
https://raw.githubusercontent.com/publicsuffix/list/master/tests/test_psl.txt

Hi, sorry for latency... (and short answer from mobile phone)

Looking at the provided test data, it seems that single-label names do not match at all
What exactly (e.g .line number) lets you assume this ?

Hi, which document are you referring to?
https://publicsuffix.org/list/

@bagder What you say. In a private area the PSL might not always do the right thing.
Is there a curl CLI option (and/or API) to switch PSL on and off ?

What exactly (e.g .line number) lets you assume this ?

Any check of a single label.

 I think it hasn't been that widely used yet.
But can you elaborate on why the function should return TRUE on a domain that clearly is not listed as a public suffix list? I don't understand how that can be the job of this function.

Point 2. Says if no rules match, the prevailing rule is "*".

but "*" is not part of the public_list ;)
while all TLD are, including the recent exotic ones (beer, pizza...)
Quick test from a browser, cookie from non qualified domain are accepted, which is very common.

@bagder looking at other consumer of libpsl (e.g. wget), it seems using psl_is_cookie_domain_acceptable could be a better solution.
psl_is_cookie_domain_acceptable(psl, localhost, localhost) => 1

Maybe, yes. The irony here is of course that @rockdaboot himself wrote the libcurl adaption that uses libpsl =)

Ex: http://git.savannah.gnu.org/cgit/wget.git/tree/src/cookies.c#n527

We could certainly work around this issue in curl that way, but that won't make psl_is_public_suffix work as documented, which this bug report is about... The curl bug is here: https://github.com/curl/curl/issues/658

@bagder There must have been a reason for using psl_is_public_suffix at the time I wrote the patch. Sadly, I hardly remember and do not have the time to investigate right now. But today, I would use psl_is_cookie_domain_acceptable() in a cookie context, as @remicollect correctly found out. I am willing to have a look at curl code the next days, if that is fine for you.

but that won't make psl_is_public_suffix work as documented, which this bug report is about

The documentation has to be clearer. I won't work against the proposed PSL... if there is something wrong or unclear in those rules, we have to open an issue at https://github.com/publicsuffix/list, asking for clarification. There are a few points unclear, see https://github.com/publicsuffix/list/issues/145.
BTW, ..foo.bar is explicitely allowed for the PSL. But that breaks current Chromium and libpsl implementations that allow only one wildcard at the left position. @weppos already reverted a commit with ..githubcloudusercontent.com due to this.

psl_is_cookie_domain_acceptable(psl, localhost, localhost) => 1

@remicollect, this is of course accepted and circumvents a check against the PSL (due to localhost==localhost). The real question is if xyz.localhost may set a cookie for localhost. The PSL rulez say NO. I personally would say default=NO, but YES if user allows it explicitely. But that is beyond libpsl and should be handled at application level.
IMO, there are these TODOs:

fix libpsl documentation
fix curl code to use psl_is_cookie_domain_acceptable()
add curl CLI options for finer user control about the PSL (optional)
open an issue at https://github.com/publicsuffix/list for clarification (optional)

The real question is if xyz.localhost may set a cookie for localhost. The PSL rulez say NO

Why? "localhost" is not a public suffix, so why does the PSL rules limit non-PSL domains?

@m6w6

Looking at the provided test data, it seems that single-label names do not match at all:

What exactly (e.g .line number) lets you assume this ?

Any check of a single label.

The 'checkPublicSuffix' function checks for the 'shortest registrable domain part' of a given input domain, e.g. checkPublicSuffix('COM', null); means '.com' is not registrable (it is a public suffix).
checkPublicSuffix('a.b.example.example', 'example.example'); means '.example.example' is the shortest domain part that is not a PS (.example is a PS because it is a single label domain / TLD).

.example is a PS because it is a single label domain

Ugh. I find that very counter-intuitive and strange. But sure, it explains the functionality.

Point 2. Says if no rules match, the prevailing rule is "*".

but "*" is not part of the public_list ;)

Yes, it is implicit. Because of the rule mentioned above.

The real question is if xyz.localhost may set a cookie for localhost. The PSL rulez say NO

Why? "localhost" is not a public suffix, so why does the PSL rules limit non-PSL domains?

"localhost" is a PS, same explanation as above (prevailing * rule). Please look at https://publicsuffix.org/list/ if you don't believe me. I am not aware of a list of exception (e.g. private domains). Why not opening an issue or PR to add "!localhost" to the PSL ? An official decision is beyond libpsl.
But I am fine to discuss adding libpsl functionality regarding private PSL rules. E.g. having a second, private list of rules that can be added/removed from the PSL. A user could simply add e.g. "!localhost" or for testing, remove/overwrite existing rules. So we cover all kinds of private and 'exotic' PSL usages. WDYT ? If you like, open another issue just for this... I guess some details have to be discussed there.

My surprise is not that "localhost" specifically isn't listed as a PSL. My surprise is that an API for PSL (being "Public Suffix List" - a list of public suffixes) gives back a response about a domain that is clearly not specified as a PSL. I think it is outside of PSL's jurisdiction. I would claim that the limitations on a "single label domain" is not a PSL job to enforce. If you're just following the PSL guidelines than my beef is with the PSL guidelines and I'm just here barking up the wrong tree.
I'm thankful for your work and your library, don't mistake my complaining for anything else.

As already mentioned on the PSL site, this "algorithm" is merely a plumber-ed list.
I found an old HTML-WG thread about that, too: http://lists.w3.org/Archives/Public/public-html/2009Jan/0529.html
For me the key question remains, why would any implementation say, "yes, foo is a public suffix", despite foo not being listed in the PSL?

"localhost" is a PS, same explanation as above (prevailing * rule)

Then any single-label rule from the PSL could be spared.
Anyway, thanks for your time! ;)

Why? "localhost" is not a public suffix, so why does the PSL rules limit non-PSL domains?

My surprise is that an API for PSL (being "Public Suffix List" - a list of public suffixes) gives back a response about a domain that is clearly not specified as a PSL. I think it is outside of PSL's jurisdiction.

@bagder as @rockdaboot correctly mentioned, there is a specific rule in the PSL algorithm that says:

If no rules match, the prevailing rule is "*".

And there are corresponding tests:
// Unlisted TLD.
checkPublicSuffix('example', null);
checkPublicSuffix('example.example', 'example.example');
checkPublicSuffix('b.example.example', 'example.example');
checkPublicSuffix('a.b.example.example', 'example.example');

Which means, if a TLD is not listed, it should be considered a "standard" TLD. I did not make that rule, hence I can't share the exact initial motivations, however my assumption is that it was done because the PSL is considered "a list of specific configuration" to be applied on top of the standard practice where the domain is third-level.second-level.tld.
This potentially makes possible to clear from the list all standard suffixes (e.g. in a pre-processing phase). Moreover, the list will not cause any denial of service to new TLDs (think about all the new GTLDs) or to TLDs that for one reason or another were not listed (although I'm quite sure we currently include all the TLDs that were available at ICANN before the newGLTD phase).
I agree that this rule is very centric to the idea of public web and it may cause conflicts when the PSL is used within a local network context. However, it's also dependent on the specific usage and implementation that the library makes of the list. For e.g., the libpsl (or any other lib) may decide to provide a flag to use * or not if there is no match.
I hope this provides a little bit of extra context. If you should decide to suggest some specific changes to the PSL, I agree with @rockdaboot that the best thing to do is to open a ticket in the PSL repo itself.

I still disagree. A single label is indeed a TLD, but if it isn't listed in the PSL I disagree that it should be returned as such.

Same feeling here.

So you opened an issue (discussion) at https://github.com/publicsuffix/list, where it belongs !?
Background is that the PSL is an (optional) tool to prevent leaking of privacy via cookies AND that not all TLDs are listed in the PSL (e.g. when new ones come, it will take a while before an updated PSL is spread around everywhere). In some scenarios (e.g. secured local network, testing purposes), the PSL isn't appropriate and you don't want to use it.
You will know when it isn't the right tool and should have a switch (e.g. command line option) to turn it off.
Also, libpsl supports loading your own version of a PSL - you could bring in your own exceptions, thus have a very fine grained control (this also needs some support via curl).
If you think, there are other - automated - possibilities to detection when the PSL should be use and when not, you could give us a hint. But I believe such measurements (e.g. DNS lookup to see if IP is private) belong to the application level.

@rockdaboot ultimately it's your decision on how to tweak the lib, but what about a flag that allows the developer to optionally decide (or switch) the behavior when a rule doesn't match?
This is for example what I did here:
https://github.com/weppos/publicsuffix-ruby/blob/master/lib/public_suffix/list.rb#L245-L251
By default, I return a "*" rule in case of no match. However, a developer can either return nil or a different rule to customize the behavior. If I correctly interpreted the request here, returning nil in my Ruby implementation, for example, will match the behavior proposed by @bagder

Back to start. As I understand, @m6w6 had the problem that server 'localhost' was not able to set a cookie for domain 'localhost'. That was a bug due to not calling psl_is_cookie_domain_acceptable(). I provided a patch for curl to get this fixed (https://github.com/curl/curl/issues/658).
The questions that remains is if 'host1.localhost' may set a cookie for 'localhost' - this is called a super-cookie. If this cookie will be accepted, the next request to 'host2.localhost' will contain it. Information is transfered from host1 to host2.
IMO, If you explicitly want this behavior, just switch PSL off via e.g. a command line switch.
BTW, you can play around with the PSL using the 'psl' command from libpsl, e.g.:
$ psl --is-cookie-domain-acceptable localhost host1.localhost
host1.localhost: 0
$ psl --is-cookie-domain-acceptable localhost localhost
localhost: 1

I have to add that the reason that 'host1.localhost' MUST NOT set a cookie for 'localhost' has nothing to do with the PSL. It is the RFC 6265 that disallows it.
The code in the function psl_is_cookie_domain_acceptable() is:
	cookie_domain_length = strlen(cookie_domain);
	hostname_length = strlen(hostname);

	if (cookie_domain_length >= hostname_length)
		return 0; /* cookie_domain is too long */


[Feature-8530][API] add system default timezone if no user timezone when get userInfo

issue: #8530
Purpose of the pull request

Brief change log

Verify this pull request

This pull request is code cleanup without any test coverage.
(or)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:

PTAL @devosend @songjianet

Codecov Report

Merging #8899 (c92f01c) into dev (db64dca) will decrease coverage by 5.52%.
The diff coverage is 27.30%.

:exclamation: Current head c92f01c differs from pull request most recent head 18ba3c0. Consider uploading reports for the commit 18ba3c0 to get more accurate results

@@             Coverage Diff              @@
##                dev    #8899      +/-   ##
============================================
- Coverage     45.30%   39.77%   -5.53%
- Complexity     4082     4262     +180
============================================
  Files           702      808     +106
  Lines         27177    32544    +5367
  Branches       2907     3647     +740
============================================
+ Hits          12312    12946     +634
- Misses        13704    18372    +4668
- Partials       1161     1226      +65

Impacted Files
Coverage Δ

...cheduler/api/controller/AccessTokenController.java
88.23% <ø> (ø)

...uler/api/controller/ProcessInstanceController.java
72.09% <ø> (ø)

.../api/controller/ProcessTaskRelationController.java
21.42% <ø> (ø)

...hinscheduler/api/controller/ProjectController.java
68.00% <ø> (ø)

...nscheduler/api/controller/ResourcesController.java
57.89% <0.00%> (-1.04%)
:arrow_down:

...duler/api/controller/TaskDefinitionController.java
3.22% <ø> (ø)

...nscheduler/api/controller/TaskGroupController.java
81.81% <ø> (ø)

...heduler/api/controller/TaskInstanceController.java
55.55% <ø> (ø)

...inscheduler/api/controller/UiPluginController.java
100.00% <ø> (ø)

...lphinscheduler/api/controller/UsersController.java
61.53% <ø> (ø)

... and 374 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update db64dca...18ba3c0. Read the comment docs.


[EVENT CHANGE] T121 "Purch. Rcpt. Line" OnAfterInsertInvLineFromRcptLine

Can you please change the signature of the following publisher to expose the NextLineNo by var
[IntegrationEvent(false, false)]
local procedure OnAfterInsertInvLineFromRcptLine(var PurchLine: Record "Purchase Line"; PurchOrderLine: Record "Purchase Line"; NextLineNo: Integer; PurchRcptLine: Record "Purch. Rcpt. Line")
begin
end;

to
[IntegrationEvent(false, false)]
local procedure OnAfterInsertInvLineFromRcptLine(var PurchLine: Record "Purchase Line"; PurchOrderLine: Record "Purchase Line"; var NextLineNo: Integer; PurchRcptLine: Record "Purch. Rcpt. Line")
begin
end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 51294.


Query Prefetch OrderedMerge

Description
During an orderby query, more pages than necessary were being prefetched causing extra roundtrips in some cases. The default prefetch would grab 256 pages. It was changed to 1, so now the expected behavior is that for each physical partition one page will be prefetched.

API change check
API changes are not detected in this pull request.

/azp run java - cosmos - tests

/azp run java - cosmos - tests

/azp run java - cosmos

/azp run java - cosmos - tests

/azp run java - cosmos - tests

/azp run java - cosmos - tests


Unexpected warnings

Bug Report
Hi guys, I see some warnings in my console
Please check proptypes or your dependencies's proptypes
And also it would be great if I could pass an array to value without Json stringify for avoid one more warning or disable this warning

But the value i passed is

And don't know what is that Failed prop type: Invalid prop options[0].valuesupplied toDropdown.
Steps
A clear and concise description of steps to reproduce the problem.
import moment from 'moment'

const graphFormat = 'YYYY-MM-DD'

const graphTimes = [
    { key: 'День', text: 'День', value: [moment().subtract(1, 'days').format(graphFormat), moment().format(graphFormat)] },
    { key: 'Неделю', text: 'Неделю', value: [moment().subtract(7, 'days').format(graphFormat), moment().format(graphFormat)] },
    { key: 'Месяц', text: 'Месяц', value: [moment().subtract(1, 'months').format(graphFormat), moment().format(graphFormat)] },
    { key: 'Год', text: 'Год', value: [moment().subtract(1, 'years').format(graphFormat), moment().format(graphFormat)] },
]

export default {
    graphTimes,
}

my values
<Dropdown
                            onChange={(e, d) => setDateRange(d.value)}
                            value={JSON.stringify(dateRange)}
                            options={graphTimes}
                            selection
                        />

my component
Expected Result
No warnings
Actual Result
The actual result that happened 💣
warnings
Version
x.y.z
Testcase
no testcase

value for Dropdown's option should be string, in your case it's an array.

value for Dropdown's option should be string, in your case it's an array.
See these issues and others:
#3460
#3153
We don't plan to change something in short-term.

Oh nooo
In my case it is a string
https://user-images.githubusercontent.com/24671211/56327979-78fe7f00-6185-11e9-97e8-e94c8b28b24f.png

@layershifter Please take a look again
You did not read the issue carefully enough

Please use CodeSandbox instead of screenshots.
As I see graphTimes as options while graphTimes[0].value is array, correct? But, it should be string...

Okay...
Testcase
https://codesandbox.io/embed/92oo3xoy9y

Okay...
@layershifter
Here is testcase
https://codesandbox.io/embed/92oo3xoy9y

console.log(Array.isArray(graphTimes[0].value)) // true :(

Sorry
Guess miss something

Nevermind 🐱
I want to relax propTypes for value/option.value, but as I mentioned before it's not so easy 😭

Yep
warnings happened because I passed array to the options.value
😭


only 3 images are accepted in associated products

I have installed your extension on <IP_ADDRESS>. Everything is working fine except that when I add more than 3 product images to associated product (while creating a configurable product) while switching only the base image changes and rest of the images are not visible, I have already configured the extension for changing entire media block and not just main image.
Please help
Great extension
Thanks in advance

@lalitvohra I tried to reproduce this, but I cannot. Check if your custom theme is not the problem. See if it works on the default theme.


Unable to retrieve the predictions (i.e low confidence Mosaic)

Hello.
When i used MF in 2021, upon the genotype prediction steps, i was able to see the prediction to have such categories:-

cat $file.genotype.predictions.refined.300721.bed | cut -f35 | sort | uniq -c
23578 het
> 682 mosaic
> 1 mosaic;cautious:AF<0.01;low-confidence:extra-high-coverage
19 mosaic;cautious:only-1-altallele
39 mosaic;cautious:only-1-altallele;low-confidence:extra-high-coverage
1136 mosaic;low-confidence:extra-high-coverage
50 mosaic;low-confidence:extra-high-coverage;low-confidence:likelyCNV
1 prediction
6 refhom
1562 repeat

But, i redownloaded the software in March 2022, and the same sample do not give the same predictions for mosaic. It categorised every mosaic as "mosaic" instead providing the information whether it is low confidence as previously. and i have been using the same commands since 2021. The number of "mosaic" is still the same for both "outputs". i just need to filter out the low confident mosaic calls in my analysis.

cat 003P.genotype.predictions.refined.bed | cut -f35 | sort | uniq -c
23579 het
>  1927 mosaic
1 prediction
6 refhom
1562 repeat

Command Used:
singularity run -B /hpcfs /hpcfs/users/$USER/mosaicforecast_0.0.1.sif Prediction.R $DIR/${sample[$SLURM_ARRAY_TASK_ID]}.features.bed $MFORECAST/models_trained/50xRFmodel_addRMSK_Refine.rds Refined $DIR/${sample[$SLURM_ARRAY_TASK_ID]}.genotype.predictions.refined.bed
I am not sure how to retrieve back the original classification, although i can do that manually in R. But, do let me know if there is additional settings that i am not aware of.
Thank you.

Hello.
When i used MF in 2021, upon the genotype prediction steps, i was able to see the prediction to have such categories:-

cat $file.genotype.predictions.refined.300721.bed | cut -f35 | sort | uniq -c
23578 het
> 682 mosaic
> 1 mosaic;cautious:AF<0.01;low-confidence:extra-high-coverage
19 mosaic;cautious:only-1-altallele
39 mosaic;cautious:only-1-altallele;low-confidence:extra-high-coverage
1136 mosaic;low-confidence:extra-high-coverage
50 mosaic;low-confidence:extra-high-coverage;low-confidence:likelyCNV
1 prediction
6 refhom
1562 repeat

But, i redownloaded the software in March 2022, and the same sample do not give the same predictions for mosaic. It categorised every mosaic as "mosaic" instead providing the information whether it is low confidence as previously. and i have been using the same commands since 2021. The number of "mosaic" is still the same for both "outputs". i just need to filter out the low confident mosaic calls in my analysis.

cat 003P.genotype.predictions.refined.bed | cut -f35 | sort | uniq -c
23579 het
>  1927 mosaic
1 prediction
6 refhom
1562 repeat

Command Used: singularity run -B /hpcfs /hpcfs/users/$USER/mosaicforecast_0.0.1.sif Prediction.R DIR/{sample[$SLURM_ARRAY_TASK_ID]}.features.bed $MFORECAST/models_trained/50xRFmodel_addRMSK_Refine.rds Refined DIR/{sample[$SLURM_ARRAY_TASK_ID]}.genotype.predictions.refined.bed
I am not sure how to retrieve back the original classification, although i can do that manually in R. But, do let me know if there is additional settings that i am not aware of.
Thank you.

Hi @ngs1810 ,
Thanks for your message. I checked "https://github.com/parklab/MosaicForecast/blob/master/Prediction.R" and confirmed that the "low-confidence" predictions are still there. Is it possible that your input lines happen to not contain the low-confidence mutations?
best wishes,
Y.


[WIP] Enable 'Back' links for crop and meta screens

https://trello.com/c/5qBQd1ko/654-allow-users-to-crop-inline-images-in-the-context-of-a-modal
This also requires changing the blur style for the normal 'Back' link,
so that it's scoped to apply only within the main page content.
TODO:

Apply this to the meta page once it's merged
Consider refactoring the action handlers (lots of repetition now)

Superseded by https://github.com/alphagov/content-publisher/pull/815.


Allow wss:// in the onprem URL.

What is the current behavior?
The Python SDK requires the onprem URL to be https://... and if the user tries to set it as wss://... because they are using streaming, the connection fails.
Steps to reproduce
Set the URL to wss://... rather than https://.... You can use wss://api.deepgram.com rather than an onprem URL to reproduce.
Expected behavior
The wss protocol should be accepted, in addition to https.
Please tell us about your environment
Reproducible in any env.
Other information

You should be able to set the URL to wss://<your IP or domain>. If you omit the protocol, the default https is added because the config object doesn't know which API the object is destined for.
Only options would be to:

create an HTTP and WS specific ClientOptions classes similar to what I did in .NET (this will break compatibility). this explicitly then states which connection you intent to use
or don't append the https and just error out if http(s) or ws(s) is missing

We could do a combination of those options.

create DeepgramWsClientOptions and DeepgramHttpClientOptions classes
keep the older DeepgramClientOptions and remove appending https to preserve the backwards compatibility

Longer term, this might be more sustainable.

The reason why I separated the classes out because it implies the options are the same for both REST and WS connections and that it's true. For example, KeepAlive can be set and passed into PreRecorded Client but it doesn't do/mean anything.

I think we're talking about different things here. The DeepgramClientOptions class is a higher level class than the streaming/prerecorded configuration classes. I'm pretty sure a short 2-line if statement will work.

Yea, we are talking about the same thing. DeepgramClientOptions can be passed into LiveClient and PreRecorded/Speak/Manage/Analyze Clients.

Will have something in a bit

this slipped my mind... will have something for tomorrow.

This fix is available in: https://github.com/deepgram/deepgram-python-sdk/releases/tag/v3.2.7


onQuestionChanged fires twice on first question

Dear all
I have my Widget using Embed React as bellow, and the onQuestionChanged fired twice on the first question
Do you have any idea about this?
<Widget
    id={ENQUIRY_FORM_ID}
    onReady={() => {
      console.log('form ready');
    }}
    onQuestionChanged={(data) => {
      console.log('question changed to ref:', data.ref);
      const matchedEvent = eventData.find((item) => item.id === data.ref);
      if (matchedEvent) {
        gtag.track(matchedEvent.name, matchedEvent);
      }
    }}
    onSubmit={(data) => {
      console.log('forms submitted with id:', data.responseId);
      const formSubmitPayload = {
        eventName: 'TypeformSubmit',
        elementId: data.responseId,
      };
      gtag.track('typeform_submit', formSubmitPayload);
    }}
    style={{ position: 'inherit', height: '100vh' }}
  />

Thank you very much

Thank you for reporting this, we will look into it. I can confirm this is fired twice for forms with welcome screen.


vscode-extensions.ms-dotnettools.csharp: 2.39.29 -> 2.55.29

Description of Changes
Update the C# extension from 2.39.29 to 2.55.29
Changelog: https://marketplace.visualstudio.com/items/ms-dotnettools.csharp/changelog
Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

I've already opened https://github.com/NixOS/nixpkgs/pull/363156
I'll be closing this in favor of that as a duplicate.


Add /debug/health route for vtctld

It could be nice to have a /debug/health route for vtctld like we have for vttablet and vtgate. Right now it's serving a HTTP 302 to Location: /app2/. The health check should probably only make sure that connection with the topology service is ✅

Closed by #3080


Do not swallow unknown options

Since package xcolor is used by many other packages that commonly pass several options to it, it might be sensible to report unfamiliar options as a warning and not as an easily overlooked info.
https://github.com/latex3/xcolor/blob/a24ee00a71316e382a2c198580c35bb7835ffc5b/xcolor.dtx#L4092-L4093

Starting with version 3.00  xcolor behaves like (most) other packages and errors with unknown options:
\documentclass{article}
\usepackage[blub]{xcolor}
\begin{document}
blub
\end{document}

! LaTeX Error: Unknown option 'blub' for package xcolor.


Bounding rect does not automatically update when using an ImmediateMesh with MeshInstance2D

Tested versions

Reproducible in: 4.3.dev [ec02d406ca], 4.2.2.stable, 4.0.4.stable.
Not applicable in 3.x because ImmediateMesh doesn't exist yet, and ImmediateGeometry is a Spatial node.

System information
Godot v4.2.2.stable - macOS 14.5.0 - GLES3 (Compatibility) - Apple M2 Max - Apple M2 Max (12 Threads)
Issue description
Problem
When using ImmediateMesh with MeshInstance2D, the node's bounding rect is not automatically updated when the mesh's surfaces are cleared and re-generated in a different shape. Since CanvasItem nodes are culled when their bounding rect is entirely outside of the viewport, this can cause the mesh to "disappear" in cases where it should actually be visible.
The animation below demonstrates the problem. The white rectangle is a MeshInstance2D whose position is animated to move around the viewport. It has an ImmediateMesh that is re-generated each frame with its vertices in a different location with respect to its own origin. The blue rectangle is identical except that its mesh is never updated after the first frame, so it shows the initial pose of the white rectangle's mesh for reference.
Notice how whenever the blue rectangle is fully outside the viewport (meaning the cached bounding rect for the white rectangle is outside the viewport), the white rectangle is culled from the view:

Obviously this is a contrived example, but the real-world situation where I ran into this problem was creating a Snake-style game where the snake's body is a procedurally-generated mesh. In order to allow the player's snake to leave one side of the screen and enter from the opposite side, I need to render snake meshes that are partly outside the viewport. In most cases this means the snake mesh's initial bounding rect fully leaves the viewport before the mesh does, causing the mesh to suddenly disappear.
Workaround
Invoking queue_redraw() whenever the mesh changes shape avoids the problem because it causes the node's bounding rect to be marked as dirty. But this is awkward since there are no drawing commands, and perhaps also inefficient due to causing additional work that otherwise would not need to be done.
Expected behavior
The expected behavior is that the node's bounding rect would be marked as dirty whenever the ImmediateMesh changes shape, i.e. whenever a surface is added or the surfaces are cleared.
Alternatively, if the queue_redraw() workaround is the intended way get the bounding rect to be updated, then that should be mentioned in the documentation.
Other notes

I suspect the same issue exists if using an ArrayMesh with MeshInstance2D, but I haven't tried it yet.
Based on a very brief test, this issue does not seem to occur when using ImmediateMesh with MeshInstance3D. But I cannot be sure that my test was valid.

Steps to reproduce

Create a MeshInstance2D and set its mesh to an ImmediateMesh.
Create a mesh surface in the ImmediateMesh and allow it to be rendered for at least one frame.
Re-generate the mesh in a new shape/orientation that extends outside the initial mesh's bounding rect.
Change the position of the MeshInstance2D node such that it's initial bounding rect is outside of the viewport, but part of the mesh should still be visible inside the viewport. Observe that the mesh disappears as soon as it's initial bounding rect is fully outside the viewport.

The attached MRP demonstrates these steps.
Minimal reproduction project (MRP)
immediatemesh_bug_mrp.zip

Invoking queue_redraw() whenever the mesh changes shape avoids the problem because it causes the node's bounding rect to be marked as dirty.

May I ask where did you add the queue_redraw() draw? I can reproduce the issue but adding queue_redraw() to _update_immediatemesh does not solve the issue.

@jsjtxietian Apologies, you're right I wan't specific about the queue_redraw() workaround. You need to invoke it on the MeshInstance2D whose mesh was updated.
So in my MRP project, you can apply the workaround by adding the line white_mesh.queue_redraw() in the _process() function.
I'll update my description above to be clearer about that.


Update install-gwms-frontend.md

Update Frontend installation with some corrections

@llobato could you fix the merge conflicts?


Determine if Git Subrepo justifies using multiple repositories

Initially I thought a monolith repository's benefits were more sustainable than multiple repositories with submodules -- the overhead for maintaining many repositories and keeping them up to modern standards is far more difficult with multiple repositories (even if release management is much easier for each component).
Git subrepo is designed to make the multiple repository system easier.
For this ticket, determine if the sub-repo workflow makes it easy enough to develop across repositories to justify its workflow.

Description
Status

Works across all operating systems
n/a

Automatically tested and passing
n/a

Updated developer documentation
:white_check_mark: - links (doc/working_with_subrepos.md)

Updated creator documentation, tutorials
n/a