cmd/compile: internal compiler error: arg 0 of value v4 = Load  v19 v8 does not dominate (with ssacheck)

$ go version
go version go1.17 linux/amd64

$ gotip version
go version devel go1.18-6a35e07512 Fri Aug 27 16:41:29 2021 +0000 linux/amd64

package p

var i int

type t struct {
	a, b, c, d, e int
}

func f(p t, q int) int {
	var a, b, c, d, e, f, g int
	var h, i, j, k, l, m int
	_, _, _, _, _, _, _ = a, b, c, d, e, f, g
	_, _, _, _, _, _ = h, i, j, k, l, m
	return 0
}

func g() int {
	var v t
	return f(v, 1<<i)
}

$ go build -gcflags=-d=ssa/check/seed=1 crash.go

# command-line-arguments
./crash.go:19:14: internal compiler error: 'g': arg 0 of value v4 = Load <int> v20 v9 does not dominate, arg=v20 = OffPtr <*int> [8] v10

Please file a bug report including a short program that triggers the error.

Go 1.16 is not affected.
cc @randall77 @josharian

The problem seems to be in storeOneLoad, we emit OffPtr in the input b, but the do the Load in source.Block.


Thank you

Thanks for this software. It is so cool :)
Actually, very useful. I did not now about its existence, it works so great. I combine it with synchronized panes and it is wonderful.
Sorry, I know issues are not always for random comments like this one.
If we don't close this issue, can people share the use cases for what you guys use it?
ZZC^ad

If we don't close this issue, can people share the use cases for what you guys use it?
Excellent, I am also curious about use cases.

Good god man, this is brilliant, cheers!
I use it to open a terminal (Alacritty) and SSH in to all my machines after logging in to X.

I've been using this for a couple of years, ssh into all servers (or a bunch of them based on node selectors) of a Kubernetes cluster. Wanted to share it with you guys
xpanes -c "ssh root@{}" $(kubectl get nodes -l GPUType=V100 -o jsonpath='{.items[*].status.addresses[?(@.type=="InternalIP")].address}')


Units

It should be good to read the step, detect the units, and write the STL in same unit system. or if you want to keep the output in only one unit, can you rename the output with the unit?
picture shows the units in two steps

STL files contain no scale information, so it's up to interpretation what the output units should be. I found this dicussion which suggests that OpenCascade converts geometry to millimeters.


Slow deployment on Sophon testnet

Component
Forge
Have you ensured that all of these are up to date?

[X] Foundry
[X] Foundryup

What version of Foundry are you on?
forge 0.0.2 (e2e2d57 2024-09-23T00:23:48.096721400Z)
What command(s) is the bug in?
No response
Operating System
Linux
Describe the bug
When trying to deploy the standard Counter contract on Sophon Testnet, intermittently the deployment takes a long time (can be 1h+). Sometimes the transaction is dropped from the mempool.
As we never encountered this issue on zkSync Sepolia, I wonder if this is due to the chain having a custom base token. This issue has been encountered by other devs as well.
We use no VPN/SSH, we are simply accessing the rpc
To reproduce:
Create the default Counter repo and run (you will need some testnet tokens):
source .env && ZK_DEBUG_HISTORICAL_BLOCK_HASHES=0 forge script ./script/Counter.s.sol --rpc-url https://rpc.testnet.sophon.xyz/ --private-key $PRIVATE_KEY --zksync --broadcast
Below the log with RUST_LOG=trace:
slow_deployment.txt
Alternatively as gist: https://gist.github.com/lutr0/c25cc2655a6eb72b3b6f11a4501e32e2

Preliminary investigation suggests the node is silently dropping the tx. From the following log 0x751a138032a08914c876973c97a61302fefb784f219129f8e27469115c2d57e2 was the hash returned after the tx was submitted, but the subsequent calls for retrieving the receipt always return null - hence the slowdown. The tx isn't visible on the block explorer either.
2024-09-18T11:35:34.325865Z TRACE alloy_rpc_client::call: serialized request request={"method":"eth_sendRawTransaction","params":["0x71f904362c8085e6c6a23fc08305910e94000000000000000000000000000000000001000080b8843cda33513100000000000000000000000000000....0000000000000000bd16851548ac6f2945a2d7d191ca4e3639c8b220705dcd98c48fb36b7e29a248b8410859232f2dfdb6b12bdf1b13a5da8f8db7bc2017d891c8ba9d8ed59fe970905d58e247d6eb6571e944c9b7d218d5c52390edd2314739b32e206e610aefa589051bc0"],"id":3,"jsonrpc":"2.0"}

2024-09-18T11:35:34.692784Z TRACE ReqwestTransport{url=https://rpc.testnet.sophon.xyz/}: alloy_transport_http::reqwest_transport: response body body={"jsonrpc":"2.0","result":"0x751a138032a08914c876973c97a61302fefb784f219129f8e27469115c2d57e2","id":3}

2024-09-18T11:35:35.338202Z TRACE alloy_rpc_client::call: serialized request request={"method":"eth_getTransactionReceipt","params":["0x751a138032a08914c876973c97a61302fefb784f219129f8e27469115c2d57e2"],"id":7,"jsonrpc":"2.0"}
2024-09-18T11:35:35.828215Z TRACE ReqwestTransport{url=https://rpc.testnet.sophon.xyz/}: alloy_transport_http::reqwest_transport: response body body={"jsonrpc":"2.0","result":null,"id":7}
...
<repeats>
...
2024-09-18T11:36:45.717753Z TRACE ReqwestTransport{url=https://rpc.testnet.sophon.xyz/}: alloy_transport_http::reqwest_transport: response body body={"jsonrpc":"2.0","result":null,"id":28}


Fixed insertNewMember doesn't commit (#665)

By the way, I think we should make importList() call this function (insertNewMember) instead of having similar logic at multiple places which is problem-prone.

Fixes #665


The endpoint Types description table has a broken link

Description:
The endpoint Types description table [1] has a broken link to "Adding Dynamic Endpoints" which should link to [2].
[1] - Endpoint Types¶
[2] - https://apim.docs.wso2.com/en/4.2.0/design/api-policies/regular-gateway-policies/adding-dynamic-endpoints/

Effected Versions:
4.1.0, 4.2.0

Already fixed

need to fix it for 4.1.0


Button to download all the data

Nikolai:
The limitation to comparing two genes or one gene and its homoeologues is quite strict. I imagine I can compare more genes by downloading the data and then merging files. Is there an easy way to do this, i.e. are the factors always in the same order so that I can simply paste new gene columns onto another dataset?
UAUY: We will have the option of downloading all the data so this would be one way of doing it. We should have a button somewhere that opens up a new page with Documentation and how to download the complete data.

I think this addressed now with the heat map.


when adding a goshape, in _enter_tree, toggle on _edit_group

This is to not make the children (meshes, collider, etc) of the Goshape's selectable from the 3D scene viewer when a new node is added. I think this makes sense, since it's almost never the case that you want to select a child (since these are re-created over and over) when clicking a Goshape.

https://github.com/user-attachments/assets/a47ccc57-9d59-4f8d-8918-077ea5f24e5c

Thanks for merging 🙏🏼


Cache the requests of kubernetes resources in REST API Server

Recently a new middleware layer was included in the API Server to query the resources from k8s API and be able to get the kind of a resource given the pluralized name, the group and the version.
K8s go client include a CachedDiscoveryClient that we should use instead of the current one to reduce the ammount of queries done to the kubernetes API

I would like to see proof of this, do you have any idea how to measure this?

EDIT: I posted the disk cached but I would like to try first the mem cache client, this one
What do you mean about proof?
To expand a little more this topic, IIUC, that objet would keep in memory a map with the same information returned by the K8S API when we do kubectl api-resources.
That information is very unlikely to change, so if this is stored in memory, it should potentially not be refreshed in a long time. If it does not found the groupversion being asked, then a request is done to kubernetes (and maybe retried depending on the error received)

Maybe you were referring to track performance of the k8s API? Something like this?

By proof I meant that we have a way in which we can compare how its calling less the Kubernetes API. My first guess is to compare the logs of the K8s API before and after the change, given that these requests can be seen in that log.

Maybe you were referring to track performance of the k8s API? Something like this?

Nothing that complex, just looking at logs or something similar.

We don't have logs for the http client embedded in the k8s client that we are using for the kubearchive rest api server.
I've created https://github.com/kubearchive/kubearchive/issues/202 to address that

Ah, didn't think of that but sounds good to be able to follow traces to services we call.


Get CloudFormation deployment to use pre-built image

The override file docker-compose-prod.yml should be used in infrastructure deployments so that we use a pre-built Docker image instead of building on the fly. This will save 5-10 minutes for startup.

Hey @dominicschaff shall we discuss here?

We can.
I added up-prod that can do that. So if I make a setup-prod then it can use that instead of the current build and up

Sounds good to me  👍
I can tweak the Docker image dependencies and make sure it builds happily. There were a couple of libs conflicting when I built on AWS just now.

I didn't notice any conflicts when I was testing. What conflicts were they? I probably missed something

ERROR: botocore 1.15.32 has requirement urllib3<1.26,>=1.20; python_version != "3.4", but you'll have urllib3 1.26.6 which is incompatible.
ERROR: awscli 1.18.32 has requirement PyYAML<5.4,>=3.10; python_version != "3.4", but you'll have pyyaml 5.4.1 which is incompatible.
ERROR: pystac-client 0.2.0 has requirement requests~=2.25.1, but you'll have requests 2.26.0 which is incompatible.
ERROR: jupyter-ui-poll 0.1.3 has requirement ipykernel<6, but you'll have ipykernel 6.3.1 which is incompatible.

Python dependencies are a real pain

Ah, that is something I did skip.


OrFeed Testnet Deployments Out-Of-Date

Let's admit: Various aspects of this codebase are a mess, as it was conceived during a hackathon and then iterated on.
But it's an amazing opportunity in the art of the renovation, as we proceed. This renovation starts with tests and testnet redeployments.
The goal is to redeploy the Rinkeby and Kovan contracts for the main contract (orfeed.sol), linking it to the appropriate testnet contracts for Kyber, Uniswap, Synthetix, Chainlink etc, and then deploying the proxy OrFeed contracts that the main contract interfaces with (a lot) on testnets as well  (the registry system, events registry, premium/advanced data feeds, arbitrage smart contracts)
Basically, the functionality that you can observe and test here: https://www.orfeed.org/explorer   using examples from orfeed.org/docs will work the same on testnet as they do on mainnet/the current explorer.
The best part, explaining how all these link together and work, as a part of a new README section!
This is a lot to ask, and the bounty is really meant for someone who can feel the mission vs. just-another-bounty sort of thing.
What is this and how exactly does it work? Here are a series of videos that pretty much take you on a tour as OrFeed tries to aggregate oracles for various DeFi projects into one cohesive, standardized, consumable protocol. https://www.youtube.com/playlist?list=PLkA8kdGfX8nYGlfS40BYY43Hdzy3ZzC8H
Have questions? Here's the discord (https://discord.gg/byCPVsY). In the issues channel, maybe someone has already even wondered a similar thing. Feel free to reach out!

Are token addresses in Rinkeby/ and Kovan/ like
    freeRateTokenSymbols['DAI'] = 0x2448eE2641d78CC42D7AD76498917359D961A783;

already correct? Or each address needs to be checked?

Is it a good idea to autogenerate all of orfeed.sol, Rinkeby/orfeed.sol and Kovan/orfeed.sol from one source file?
If yes, what to use to generate it? make?

@vporton yes I belive, for example, the new DAI/SAI was after the original deployment, so yes, those would need to be updated. Also, regarding the autogeneration, whatever works :)

@vporton yes I believe, for example, the new DAI/SAI was after the original deployment, so yes, those would need to be updated. Also, regarding the autogeneration, whatever works :)

Where to gather the information about the contract addresses?

@vporton exactly. Etherscan/each project's website has their rinkeby and other testnet contract data. That is why this is so difficult to do at the moment as far as testnets go...

There exists multiple versions of testnet DAI. I have no idea which of them is the "true".
I will stop work.

are the testnet contracts going to be updated?


An unexpected error occurred: Resolv::ResolvError: DNS result has no information for

Hey nice work!
So looks like I'm running into a bunch of unhandled exceptions for DNS entries that don't resolve on this particular domain. They have a messy environment, so makes sense.  It errored on a variety of sub-domain entries, not just one.  Tried the --ignore-private flag as well. How about an --ignore-errors flag? Thoughts?
Identifying nameservers for xxxx.com ... An unexpected error occurred: Resolv::ResolvError: DNS result has no information for xxxx.domain.local
C:/Ruby24-x64/lib/ruby/2.4.0/resolv.rb:384:in `getaddress'
C:/Ruby24-x64/lib/ruby/gems/2.4.0/gems/aquatone-0.1.1/lib/aquatone/domain.rb:20:in `block (2 levels) in nameservers'
C:/Ruby24-x64/lib/ruby/gems/2.4.0/gems/aquatone-0.1.1/lib/aquatone/domain.rb:20:in `map'
C:/Ruby24-x64/lib/ruby/gems/2.4.0/gems/aquatone-0.1.1/lib/aquatone/domain.rb:20:in `block in nameservers'
C:/Ruby24-x64/lib/ruby/gems/2.4.0/gems/aquatone-0.1.1/lib/aquatone/domain.rb:16:in `times'
C:/Ruby24-x64/lib/ruby/gems/2.4.0/gems/aquatone-0.1.1/lib/aquatone/domain.rb:16:in `nameservers'
C:/Ruby24-x64/lib/ruby/gems/2.4.0/gems/aquatone-0.1.1/lib/aquatone/commands/discover.rb:33:in `setup_resolver'
C:/Ruby24-x64/lib/ruby/gems/2.4.0/gems/aquatone-0.1.1/lib/aquatone/commands/discover.rb:16:in `execute!'
C:/Ruby24-x64/lib/ruby/gems/2.4.0/gems/aquatone-0.1.1/lib/aquatone/command.rb:10:in `run'
C:/Ruby24-x64/lib/ruby/gems/2.4.0/gems/aquatone-0.1.1/exe/aquatone-discover:129:in `<top (required)>'
C:/Ruby24-x64/bin/aquatone-discover:22:in `load'
C:/Ruby24-x64/bin/aquatone-discover:22:in `<main>'

i am having this issue as well, just installed newest version
Identifying nameservers for llmhq.com... An unexpected error occurred: Resolv::ResolvError: DNS result has no information for adc01.***.com
C:/Ruby31-x64/lib/ruby/3.1.0/resolv.rb:379:in getaddress' C:/Ruby31-x64/lib/ruby/gems/3.1.0/gems/aquatone-0.5.0/lib/aquatone/domain.rb:20:in block (2 levels) in nameservers'
C:/Ruby31-x64/lib/ruby/gems/3.1.0/gems/aquatone-0.5.0/lib/aquatone/domain.rb:20:in map' C:/Ruby31-x64/lib/ruby/gems/3.1.0/gems/aquatone-0.5.0/lib/aquatone/domain.rb:20:in block in nameservers'
C:/Ruby31-x64/lib/ruby/gems/3.1.0/gems/aquatone-0.5.0/lib/aquatone/domain.rb:16:in times' C:/Ruby31-x64/lib/ruby/gems/3.1.0/gems/aquatone-0.5.0/lib/aquatone/domain.rb:16:in nameservers'
C:/Ruby31-x64/lib/ruby/gems/3.1.0/gems/aquatone-0.5.0/lib/aquatone/commands/discover.rb:33:in setup_resolver' C:/Ruby31-x64/lib/ruby/gems/3.1.0/gems/aquatone-0.5.0/lib/aquatone/commands/discover.rb:16:in execute!'
C:/Ruby31-x64/lib/ruby/gems/3.1.0/gems/aquatone-0.5.0/lib/aquatone/command.rb:10:in run' C:/Ruby31-x64/lib/ruby/gems/3.1.0/gems/aquatone-0.5.0/exe/aquatone-discover:138:in <top (required)>'
C:/Ruby31-x64/bin/aquatone-discover:32:in load' C:/Ruby31-x64/bin/aquatone-discover:32:in '


liburcu: 0.12.2 -> 0.13.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/liburcu/versions.
meta.description for liburcu is: "Userspace RCU (read-copy-update) library"
meta.homepage for liburcu is: "https://lttng.org/urcu"
meta.changelog for liburcu is: ""
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 0.13.0 with grep in /nix/store/w9rka7yhy9hclzf5jwif0yiplp5fnik6-liburcu-0.13.0

found 0.13.0 in filename of file in /nix/store/w9rka7yhy9hclzf5jwif0yiplp5fnik6-liburcu-0.13.0

directory tree listing: https://gist.github.com/2cba4c27c18e174dc3ed9528f01abb16

du listing: https://gist.github.com/b6ff989bfbdc63ff198443c721713363

Rebuild report (if merged into master) (click to expand)

102 total rebuild path(s)

47 package rebuild(s)

47 x86_64-linux rebuild(s)
21 i686-linux rebuild(s)
9 x86_64-darwin rebuild(s)
25 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
appgate-sdp
aws-workspaces
bareos
bcachefs-tools
ceph
ceph-client
ceph-csi
ceph-dev
codeql
coreclr
github-runner
glusterfs
knot-dns
knot-resolver
libceph
liburcu
libvmi
lttng-tools
lttng-ust
multipath-tools
netsniff-ng
nfs-ganesha
ntirpc
osu-lazer
powershell
qemu_full
qemu_xen
qemu_xen-light
qemu_xen_4_10
qemu_xen_4_10-light
qubes-core-vchan-xen
samba4Full
sambaFull
vscode-extensions.ms-python.python
vscode-extensions.ms-vsliveshare.vsliveshare
xen
xen-light
xen-slim
xenPackages.xen-light
xenPackages.xen-slim
xenPackages.xen-vanilla
xenPackages.xen_4_10-light
xenPackages.xen_4_10-slim
xenPackages.xen_4_10-vanilla
xen_4_10
xen_4_10-light
xen_4_10-slim

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/w9rka7yhy9hclzf5jwif0yiplp5fnik6-liburcu-0.13.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A liburcu https://github.com/r-ryantm/nixpkgs/archive/eea9d67bb189d9a241384ce667914539bb4579e5.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/w9rka7yhy9hclzf5jwif0yiplp5fnik6-liburcu-0.13.0
ls -la /nix/store/w9rka7yhy9hclzf5jwif0yiplp5fnik6-liburcu-0.13.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review took longer than 45m and timed out

Maintainer pings
cc @bjornfor for testing.

On nixos x86_64:
builder for '/nix/store/vd4vav525qn63hx2rkv398dn8fnppw7a-lttng-ust-2.10.5.drv' failed with exit code 1; last 10 log lines:
  checking for pthread_setname_np in -lpthread... yes
  checking for dlfcn.h... (cached) yes
  checking whether RTLD_DI_LINKMAP is declared... yes
  checking urcu-bp.h usability... yes
  checking urcu-bp.h presence... yes
  checking for urcu-bp.h... yes
  checking for _cds_lfht_new in -lurcu-cds... yes
  checking caa_likely()... yes
  checking for synchronize_rcu_bp in -lurcu-bp... no
  configure: error: Cannot find liburcu-bp lib. Use LDFLAGS=-Ldir to specify its location.

(though nixpkgs-review reveals no new failures on macos 10.15)

Result of nixpkgs-review pr 134049 at eea9d67b run on x86_64-linux 1

12 packages failed to build:

appgate-sdp
aws-workspaces
codeql
coreclr
github-runner
libcamera
lttng-tools
lttng-ust
osu-lazer
powershell
vscode-extensions.ms-python.python
vscode-extensions.ms-vsliveshare.vsliveshare

7 packages skipped due to time constraints:

bareos
ceph (ceph-dev)
ceph-client
ceph-csi
libceph
qemu_full
sambaFull (samba4Full)

16 packages built successfully:

bcachefs-tools
glusterfs
knot-dns
knot-resolver
liburcu
libvmi
multipath-tools
netsniff-ng
nfs-ganesha
ntirpc
qemu_xen (qemu_xen_4_10)
qemu_xen-light (qemu_xen_4_10-light)
qubes-core-vchan-xen
xen (xenPackages.xen-vanilla ,xenPackages.xen_4_10-vanilla ,xen_4_10)
xen-light (xenPackages.xen-light ,xenPackages.xen_4_10-light ,xen_4_10-light)
xen-slim (xenPackages.xen-slim ,xenPackages.xen_4_10-slim ,xen_4_10-slim)

Note that build failures may predate this PR, and could be nondeterministic or hardware dependent.
Please exercise your independent judgement. Does something look off? Please file an issue or reach out on IRC.


Attempting to re-deploy with insufficient creds fails with an irrelevant error

Describe the bug
We deployed to a BOSH director using a comprehensive admin user, then tried to deploy over that authenticated as a more fine-grained user (CI Bot). The resultant error message does not in any way indicate that the issue is permissions-based.
To Reproduce
Steps to reproduce the behavior (example):

Deploy (anything) using the root admin user.
Attempt to re-deploy while authenticated as a user with permissions to create deployments.
Observe the error:

Fetching diff result:
  Performing request POST 'https://director-host:25555/deployments/depl-name/diff?redact=true':
    Performing POST request:
      Retry: Post https://director-host:25555/deployments/depl-name/diff?redact=true: http: ContentLength=7485 with Body length 0

Expected behavior
Consistent with trying to delete-deployment with the same creds. Http response code 401 indicating insufficient authorization.
Versions (please complete the following information):

BOSH version 266.7
BOSH CLI version 5.1.1

Thanks - this should be fixed as of v5.3.1.


Send May newsletter

Summary

With the next community meet-up happening soon, we want to send out a newsletter in advance to make sure folks know about it. We should have some general updates as well as a contributor spotlight.
Deadline
May 26
What needs to be done?

[ ] Pick topics
[ ] Draft newsletter
[ ] Put into tinyletter & test
[ ] Send out the week before the meetup

Who can help?

@GeorgiaHCA
@mastoffel

Potential topics to cover

Georgia at C*Sci conference, link to poster
Contributor spotlight: Last month we suggested @mastoffel, if he's still up for it!
Next community meet-up, June 1st

A draft of the newsletter is here: https://hackmd.io/t2x2cmjESAq3iBnhWPwfdw
@mastoffel Are you still up to answer that little interview? I put your name in for now, but if the timing doesn't fit  (early next week would be great!) then we could gently ask @llewelld instead 😉

Cool! Done :)

Perfect, thanks so much! I'll send it out later today!

And sent, Newsletter is archived here: https://github.com/alan-turing-institute/AutSPACEs/blob/main/00-project-documentation/communication/newsletters/newsletter-2023-05.md