1.5.1 Failed to start whirlpool

Also noticed mixing doesn't start on it's own anymore.
2021-10-07 12:42:16,169 ERROR [Thread-9] c.s.w.c.w.d.p.ExpirablePoolSupplier [null:-1] load() failure com.samourai.wallet.api.backend.beans.HttpException: java.util.concurrent.ExecutionException: java.net.SocketTimeoutException: Connect Timeout 	at com.sparrowwallet.nightjar@0.2.18-SNAPSHOT/com.samourai.http.client.JacksonHttpClient.getJson(Unknown Source) 	at com.sparrowwallet.nightjar@0.2.18-SNAPSHOT/com.samourai.http.client.JacksonHttpClient.getJson(Unknown Source) 	at com.sparrowwallet.nightjar@0.2.18-SNAPSHOT/com.samourai.whirlpool.client.whirlpool.ServerApi.fetchPools(Unknown Source) 	at com.sparrowwallet.nightjar@0.2.18-SNAPSHOT/com.samourai.whirlpool.client.wallet.data.pool.ExpirablePoolSupplier.fetch(Unknown Source) 	at com.sparrowwallet.nightjar@0.2.18-SNAPSHOT/com.samourai.whirlpool.client.wallet.data.pool.ExpirablePoolSupplier.fetch(Unknown Source) 	at com.sparrowwallet.nightjar@0.2.18-SNAPSHOT/com.samourai.whirlpool.client.wallet.data.supplier.ExpirableSupplier$1.getOrThrow(Unknown Source) 	at com.sparrowwallet.nightjar@0.2.18-SNAPSHOT/com.zeroleak.throwingsupplier.ThrowingSupplier.get(Unknown Source) 	at com.sparrowwallet.nightjar@0.2.18-SNAPSHOT/com.zeroleak.throwingsupplier.ThrowingSupplier.get(Unknown Source) 	at com.google.common@28.2-jre/com.google.common.base.Suppliers$ExpiringMemoizingSupplier.get(Unknown Source) 	at com.sparrowwallet.nightjar@0.2.18-SNAPSHOT/com.samourai.whirlpool.client.wallet.data.supplier.ExpirableSupplier.load(Unknown Source) 	at com.sparrowwallet.nightjar@0.2.18-SNAPSHOT/com.samourai.whirlpool.client.wallet.data.dataSource.WalletResponseDataSource.load(Unknown Source) 	at com.sparrowwallet.nightjar@0.2.18-SNAPSHOT/com.samourai.whirlpool.client.wallet.data.dataSource.WalletResponseDataSource.open(Unknown Source) 	at com.sparrowwallet.sparrow/com.sparrowwallet.sparrow.whirlpool.dataSource.SparrowDataSource.open(Unknown Source) 	at com.sparrowwallet.nightjar@0.2.18-SNAPSHOT/com.samourai.whirlpool.client.wallet.WhirlpoolWallet.open(Unknown Source) 	at com.sparrowwallet.nightjar@0.2.18-SNAPSHOT/com.samourai.whirlpool.client.wallet.WhirlpoolWalletService.openWallet(Unknown Source) 	at com.sparrowwallet.sparrow/com.sparrowwallet.sparrow.whirlpool.Whirlpool.getWhirlpoolWallet(Unknown Source) 	at com.sparrowwallet.sparrow/com.sparrowwallet.sparrow.whirlpool.Whirlpool$StartupService$1.call(Unknown Source) 	at com.sparrowwallet.sparrow/com.sparrowwallet.sparrow.whirlpool.Whirlpool$StartupService$1.call(Unknown Source) 	at javafx.graphics/javafx.concurrent.Task$TaskCallable.call(Unknown Source) 	at java.base/java.util.concurrent.FutureTask.run(Unknown Source) 	at javafx.graphics/javafx.concurrent.Service.lambda$executeTask$6(Unknown Source) 	at java.base/java.security.AccessController.doPrivileged(Unknown Source) 	at javafx.graphics/javafx.concurrent.Service.lambda$executeTask$7(Unknown Source) 	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) 	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) 	at java.base/java.lang.Thread.run(Unknown Source) Caused by: java.util.concurrent.ExecutionException: java.net.SocketTimeoutException: Connect Timeout 	at com.sparrowwallet.merged.module@1.5.1/org.eclipse.jetty.client.util.FutureResponseListener.getResult(Unknown Source) 	at com.sparrowwallet.merged.module@1.5.1/org.eclipse.jetty.client.util.FutureResponseListener.get(Unknown Source) 	at com.sparrowwallet.merged.module@1.5.1/org.eclipse.jetty.client.HttpRequest.send(Unknown Source) 	at com.sparrowwallet.nightjar@0.2.18-SNAPSHOT/com.sparrowwallet.nightjar.http.JavaHttpClient.requestJson(Unknown Source) 	at com.sparrowwallet.nightjar@0.2.18-SNAPSHOT/com.sparrowwallet.nightjar.http.JavaHttpClient.requestJsonGet(Unknown Source) 	... 26 common frames omitted Caused by: java.net.SocketTimeoutException: Connect Timeout 	at com.sparrowwallet.merged.module@1.5.1/org.eclipse.jetty.io.ManagedSelector$Connect.run(Unknown Source) 	at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) 	at java.base/java.util.concurrent.FutureTask.run(Unknown Source) 	at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source) 	... 3 common frames omitted 2021-10-07 12:42:16,171 ERROR [JavaFX Application Thread] c.s.s.w.WhirlpoolServices [null:-1] Failed to start whirlpool com.sparrowwallet.sparrow.whirlpool.WhirlpoolException: Could not create whirlpool wallet  	at com.sparrowwallet.sparrow/com.sparrowwallet.sparrow.whirlpool.Whirlpool.getWhirlpoolWallet(Unknown Source) 	at com.sparrowwallet.sparrow/com.sparrowwallet.sparrow.whirlpool.Whirlpool$StartupService$1.call(Unknown Source) 	at com.sparrowwallet.sparrow/com.sparrowwallet.sparrow.whirlpool.Whirlpool$StartupService$1.call(Unknown Source) 	at javafx.graphics/javafx.concurrent.Task$TaskCallable.call(Unknown Source) 	at java.base/java.util.concurrent.FutureTask.run(Unknown Source) 	at javafx.graphics/javafx.concurrent.Service.lambda$executeTask$6(Unknown Source) 	at java.base/java.security.AccessController.doPrivileged(Unknown Source) 	at javafx.graphics/javafx.concurrent.Service.lambda$executeTask$7(Unknown Source) 	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) 	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) 	at java.base/java.lang.Thread.run(Unknown Source) Caused by: com.samourai.wallet.api.backend.beans.HttpException: java.util.concurrent.ExecutionException: java.net.SocketTimeoutException: Connect Timeout 	at com.sparrowwallet.nightjar@0.2.18-SNAPSHOT/com.samourai.http.client.JacksonHttpClient.getJson(Unknown Source) 	at com.sparrowwallet.nightjar@0.2.18-SNAPSHOT/com.samourai.http.client.JacksonHttpClient.getJson(Unknown Source) 	at com.sparrowwallet.nightjar@0.2.18-SNAPSHOT/com.samourai.whirlpool.client.whirlpool.ServerApi.fetchPools(Unknown Source) 	at com.sparrowwallet.nightjar@0.2.18-SNAPSHOT/com.samourai.whirlpool.client.wallet.data.pool.ExpirablePoolSupplier.fetch(Unknown Source) 	at com.sparrowwallet.nightjar@0.2.18-SNAPSHOT/com.samourai.whirlpool.client.wallet.data.pool.ExpirablePoolSupplier.fetch(Unknown Source) 	at com.sparrowwallet.nightjar@0.2.18-SNAPSHOT/com.samourai.whirlpool.client.wallet.data.supplier.ExpirableSupplier$1.getOrThrow(Unknown Source) 	at com.sparrowwallet.nightjar@0.2.18-SNAPSHOT/com.zeroleak.throwingsupplier.ThrowingSupplier.get(Unknown Source) 	at com.sparrowwallet.nightjar@0.2.18-SNAPSHOT/com.zeroleak.throwingsupplier.ThrowingSupplier.get(Unknown Source) 	at com.google.common@28.2-jre/com.google.common.base.Suppliers$ExpiringMemoizingSupplier.get(Unknown Source) 	at com.sparrowwallet.nightjar@0.2.18-SNAPSHOT/com.samourai.whirlpool.client.wallet.data.supplier.ExpirableSupplier.load(Unknown Source) 	at com.sparrowwallet.nightjar@0.2.18-SNAPSHOT/com.samourai.whirlpool.client.wallet.data.dataSource.WalletResponseDataSource.load(Unknown Source) 	at com.sparrowwallet.nightjar@0.2.18-SNAPSHOT/com.samourai.whirlpool.client.wallet.data.dataSource.WalletResponseDataSource.open(Unknown Source) 	at com.sparrowwallet.sparrow/com.sparrowwallet.sparrow.whirlpool.dataSource.SparrowDataSource.open(Unknown Source) 	at com.sparrowwallet.nightjar@0.2.18-SNAPSHOT/com.samourai.whirlpool.client.wallet.WhirlpoolWallet.open(Unknown Source) 	at com.sparrowwallet.nightjar@0.2.18-SNAPSHOT/com.samourai.whirlpool.client.wallet.WhirlpoolWalletService.openWallet(Unknown Source) 	... 11 common frames omitted Caused by: java.util.concurrent.ExecutionException: java.net.SocketTimeoutException: Connect Timeout 	at com.sparrowwallet.merged.module@1.5.1/org.eclipse.jetty.client.util.FutureResponseListener.getResult(Unknown Source) 	at com.sparrowwallet.merged.module@1.5.1/org.eclipse.jetty.client.util.FutureResponseListener.get(Unknown Source) 	at com.sparrowwallet.merged.module@1.5.1/org.eclipse.jetty.client.HttpRequest.send(Unknown Source) 	at com.sparrowwallet.nightjar@0.2.18-SNAPSHOT/com.sparrowwallet.nightjar.http.JavaHttpClient.requestJson(Unknown Source) 	at com.sparrowwallet.nightjar@0.2.18-SNAPSHOT/com.sparrowwallet.nightjar.http.JavaHttpClient.requestJsonGet(Unknown Source) 	... 26 common frames omitted Caused by: java.net.SocketTimeoutException: Connect Timeout 	at com.sparrowwallet.merged.module@1.5.1/org.eclipse.jetty.io.ManagedSelector$Connect.run(Unknown Source) 	at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) 	at java.base/java.util.concurrent.FutureTask.run(Unknown Source) 	at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source) 	... 3 common frames omitted 2021-10-07 12:44:21,799 ERROR [Thread-43] c.s.w.c.w.d.p.ExpirablePoolSupplier [null:-1] load() failure com.samourai.wallet.api.backend.beans.HttpException: java.lang.InterruptedException 	at com.sparrowwallet.nightjar@0.2.18-SNAPSHOT/com.samourai.http.client.JacksonHttpClient.getJson(Unknown Source) 	at com.sparrowwallet.nightjar@0.2.18-SNAPSHOT/com.samourai.http.client.JacksonHttpClient.getJson(Unknown Source) 	at com.sparrowwallet.nightjar@0.2.18-SNAPSHOT/com.samourai.whirlpool.client.whirlpool.ServerApi.fetchPools(Unknown Source) 	at com.sparrowwallet.nightjar@0.2.18-SNAPSHOT/com.samourai.whirlpool.client.wallet.data.pool.ExpirablePoolSupplier.fetch(Unknown Source) 	at com.sparrowwallet.nightjar@0.2.18-SNAPSHOT/com.samourai.whirlpool.client.wallet.data.pool.ExpirablePoolSupplier.fetch(Unknown Source) 	at com.sparrowwallet.nightjar@0.2.18-SNAPSHOT/com.samourai.whirlpool.client.wallet.data.supplier.ExpirableSupplier$1.getOrThrow(Unknown Source) 	at com.sparrowwallet.nightjar@0.2.18-SNAPSHOT/com.zeroleak.throwingsupplier.ThrowingSupplier.get(Unknown Source) 	at com.sparrowwallet.nightjar@0.2.18-SNAPSHOT/com.zeroleak.throwingsupplier.ThrowingSupplier.get(Unknown Source) 	at com.google.common@28.2-jre/com.google.common.base.Suppliers$ExpiringMemoizingSupplier.get(Unknown Source) 	at com.sparrowwallet.nightjar@0.2.18-SNAPSHOT/com.samourai.whirlpool.client.wallet.data.supplier.ExpirableSupplier.load(Unknown Source) 	at com.sparrowwallet.nightjar@0.2.18-SNAPSHOT/com.samourai.whirlpool.client.wallet.data.dataSource.WalletResponseDataSource.load(Unknown Source) 	at com.sparrowwallet.nightjar@0.2.18-SNAPSHOT/com.samourai.whirlpool.client.wallet.data.dataSource.WalletResponseDataSource.open(Unknown Source) 	at com.sparrowwallet.sparrow/com.sparrowwallet.sparrow.whirlpool.dataSource.SparrowDataSource.open(Unknown Source) 	at com.sparrowwallet.nightjar@0.2.18-SNAPSHOT/com.samourai.whirlpool.client.wallet.WhirlpoolWallet.open(Unknown Source) 	at com.sparrowwallet.nightjar@0.2.18-SNAPSHOT/com.samourai.whirlpool.client.wallet.WhirlpoolWalletService.openWallet(Unknown Source) 	at com.sparrowwallet.sparrow/com.sparrowwallet.sparrow.whirlpool.Whirlpool.getWhirlpoolWallet(Unknown Source) 	at com.sparrowwallet.sparrow/com.sparrowwallet.sparrow.whirlpool.Whirlpool$StartupService$1.call(Unknown Source) 	at com.sparrowwallet.sparrow/com.sparrowwallet.sparrow.whirlpool.Whirlpool$StartupService$1.call(Unknown Source) 	at javafx.graphics/javafx.concurrent.Task$TaskCallable.call(Unknown Source) 	at java.base/java.util.concurrent.FutureTask.run(Unknown Source) 	at javafx.graphics/javafx.concurrent.Service.lambda$executeTask$6(Unknown Source) 	at java.base/java.security.AccessController.doPrivileged(Unknown Source) 	at javafx.graphics/javafx.concurrent.Service.lambda$executeTask$7(Unknown Source) 	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) 	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) 	at java.base/java.lang.Thread.run(Unknown Source) Caused by: java.lang.InterruptedException: null 	at java.base/java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(Unknown Source) 	at java.base/java.util.concurrent.CountDownLatch.await(Unknown Source) 	at com.sparrowwallet.merged.module@1.5.1/org.eclipse.jetty.client.util.FutureResponseListener.get(Unknown Source) 	at com.sparrowwallet.merged.module@1.5.1/org.eclipse.jetty.client.HttpRequest.send(Unknown Source) 	at com.sparrowwallet.nightjar@0.2.18-SNAPSHOT/com.sparrowwallet.nightjar.http.JavaHttpClient.requestJson(Unknown Source) 	at com.sparrowwallet.nightjar@0.2.18-SNAPSHOT/com.sparrowwallet.nightjar.http.JavaHttpClient.requestJsonGet(Unknown Source) 	... 26 common frames omitted

This is just a connection problem. Connect Timeout at....
In general you have many issues related to your connection. I would consider looking at that before filing more issues here.

Connection seems impossible again, no matter what I do.
2021-10-09 01:16:54,713 WARN [Thread-1672] c.s.s.n.TcpTransport [null:-1] No response from server, setting read timeout to 34 secs 2021-10-09 01:17:06,831 WARN [Thread-1506] c.s.s.n.SimpleElectrumServerRpc [null:-1] Failed to retrieve fee rate for target blocks: 4 (Retries exhausted) 2021-10-09 01:17:10,626 WARN [Thread-1506] c.s.s.n.SimpleElectrumServerRpc [null:-1] Failed to retrieve fee rate for target blocks: 5 (Retries exhausted) 2021-10-09 01:17:13,664 WARN [Thread-1506] c.s.s.n.SimpleElectrumServerRpc [null:-1] Failed to retrieve fee rate for target blocks: 10 (Retries exhausted) 2021-10-09 01:17:16,876 WARN [Thread-1506] c.s.s.n.SimpleElectrumServerRpc [null:-1] Failed to retrieve fee rate for target blocks: 25 (Retries exhausted) 2021-10-09 01:17:18,932 ERROR [ElectrumServerReadThread] c.s.s.n.TcpTransport [null:-1] Error opening socket inputstream java.net.SocketException: Socket is closed 	at java.base/sun.security.ssl.SSLSocketImpl.getInputStream(Unknown Source) 	at com.sparrowwallet.sparrow/com.sparrowwallet.sparrow.net.TcpTransport.readInputLoop(Unknown Source) 	at com.sparrowwallet.sparrow/com.sparrowwallet.sparrow.net.ElectrumServer$ReadRunnable.run(Unknown Source) 	at java.base/java.lang.Thread.run(Unknown Source) 2021-10-09 01:17:23,716 ERROR [JavaFX Application Thread] c.s.s.p.ServerPreferencesController [null:-1] Connection error com.sparrowwallet.sparrow.net.ElectrumServerRpcException: Error getting fee rate histogram 	at com.sparrowwallet.sparrow/com.sparrowwallet.sparrow.net.SimpleElectrumServerRpc.getFeeRateHistogram(Unknown Source) 	at com.sparrowwallet.sparrow/com.sparrowwallet.sparrow.net.ElectrumServer.getMempoolRateSizes(Unknown Source) 	at com.sparrowwallet.sparrow/com.sparrowwallet.sparrow.net.ElectrumServer$ConnectionService$1.call(Unknown Source) 	at com.sparrowwallet.sparrow/com.sparrowwallet.sparrow.net.ElectrumServer$ConnectionService$1.call(Unknown Source) 	at javafx.graphics/javafx.concurrent.Task$TaskCallable.call(Unknown Source) 	at java.base/java.util.concurrent.FutureTask.run(Unknown Source) 	at javafx.graphics/javafx.concurrent.Service.lambda$executeTask$6(Unknown Source) 	at java.base/java.security.AccessController.doPrivileged(Unknown Source) 	at javafx.graphics/javafx.concurrent.Service.lambda$executeTask$7(Unknown Source) 	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) 	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) 	at java.base/java.lang.Thread.run(Unknown Source) Caused by: com.sparrowwallet.sparrow.net.ServerException: Retries exhausted 	at com.sparrowwallet.sparrow/com.sparrowwallet.sparrow.net.RetryLogic.getResult(Unknown Source) 	... 12 common frames omitted Caused by: java.lang.IllegalStateException: I/O error during a request processing 	at simple.json.rpc.client@1.0/com.github.arteam.simplejsonrpc.client.builder.RequestBuilder.executeRequest(Unknown Source) 	at simple.json.rpc.client@1.0/com.github.arteam.simplejsonrpc.client.builder.RequestBuilder.executeAndConvert(Unknown Source) 	at simple.json.rpc.client@1.0/com.github.arteam.simplejsonrpc.client.builder.RequestBuilder.execute(Unknown Source) 	at com.sparrowwallet.sparrow/com.sparrowwallet.sparrow.net.SimpleElectrumServerRpc.lambda$getFeeRateHistogram$13(Unknown Source) 	... 13 common frames omitted Caused by: java.net.SocketException: Socket is closed 	at java.base/sun.security.ssl.SSLSocketImpl.getOutputStream(Unknown Source) 	at com.sparrowwallet.sparrow/com.sparrowwallet.sparrow.net.TcpTransport.writeRequest(Unknown Source) 	at com.sparrowwallet.sparrow/com.sparrowwallet.sparrow.net.TcpTransport.pass(Unknown Source) 	... 17 common frames omitted

Connecting or connected

Blockstream's server does often have these kind of issues. It appears that when it is overloaded it disconnects clients and prevents them from reconnecting (as far as I can tell).
Agreed the tooltip should reflect this state better.

While I didn't try another server I tried disconnecting and reconnecting many times over 15min. I went in the connection box and tried testing connection with BS server. Nothing would happen. It really felt like nothing at all could be done to get any connection from sparrow over this long 15 block off time.
Restarting sparrow acheived connection instantly.


Initializing SVG element doesn't always work

My code looks like this:
var drawingPad = SVG('drawingPad').size('100%', '100%');
Usually, when I get to the page where I use this, the svg element just remains empty and uninitialized. Once I reload it always works.
Can anyone help me figure out what is going on?

Are you calling that within a window.onloadblock or similar (jQuery $( function() { ... } )) that makes sure the DOM has finished loading?
Not sure if that's the problem here - just asking what's the context where your line gets called.

yes, I'm calling it from within $document.ready.

var drawingPad = $document[0].getElementById('drawingPad');
var temp = drawingPad;

$document.ready(function () {
    drawingPad = SVG('drawingPad').size('100%', '100%');
    console.log(temp);
    console.log(drawingPad.parent);
    console.log(angular.equals(drawingPad.parent, temp));
    if ($routeParams.screenshotURL) {
      drawingPad.image(decodeURIComponent($routeParams.screenshotURL)).loaded(function (loader) {
        drawingPad.attr({
          width: loader.width
        });
        drawingPad.attr({
          height: loader.height
        });
      });
    }
  });

So, when it works, the comparison returns true, but when it fails I have this situation:
temp gets logged as <svg id="drawingPad"></svg> while drawingPad is this:
<svg id="drawingPad" xmlns="http://www.w3.org/2000/svg" version="1.1" width="960" height="946" xmlns:xlink="http://www.w3.org/1999/xlink">[...]</svg>
Then, a reload fixes it.
It seems like a weird cross between a loading issue and the DOM not getting updated...

I have added more debug output, which just shows me that I fundamentally don't understand something involved here:
  var drawingPad;
  var temp = drawingPad;
  console.log('temp');
  console.log(temp);
  $document.ready(function () {
    console.log('before initialization, in .ready');
    console.log($document[0].getElementById('drawingPad'));
    drawingPad = SVG('drawingPad').size('100%', '100%');
    console.log('drawingPad after .get');
    console.log(drawingPad.parent);
    console.log('document element');
    console.log($document[0].getElementById('drawingPad'));
    if ($routeParams.screenshotURL) {
      drawingPad.image(decodeURIComponent($routeParams.screenshotURL)).loaded(function (loader) {
        drawingPad.attr({
          width: loader.width
        });
        drawingPad.attr({
          height: loader.height
        });
      });
    }
  });

In the failed case, the log looks like so:
temp: undefined
before initialization and document element after init: simple svg as in .html file
drawingPad: svg element with image child
Seems like $document doesn't get updated...
In the working case, all the output except for temp (which is still undefined) is the SVG element that SVG('drawingPad') should generate!
Including the log from before actually constructing the SVG.js element!
Sorry for the multiple posts, but I hope this gives you enough info to figure it out.

I shouldn't have asked for more details, without suggesting to take this to StackOverflow.
It looks like belonging there - for generous helpful answers. Now it's in the projects GitHub Issues, which is where one would normally take reproducible bugs. So something discussed in SO that turns out really to be a bug should end up here.
I'm not one of svg.js authors, just tracking the project. So what I write here is just my own suggestion, not a project guideline.
If you copy-paste the above to StackOverflow, add the svg.js tag to it. There are currently 52 questions with such tag.

That is a good idea and I will do so.
However, I would like to ask you to try and reproduce it. To me, it does look like a bug where svg.js fails to properly initialize its doc element and I'm not sure what I could even be doing wrong to produce such inconsistent behavior.

Since adding a timeout in AngularJS fixed the issue, I apologize for opening this here.
It seems it was some really weird behavior in AngularJS.

Adding a timeout also solves issues around initializing existing svg elements, and getting them by id in Ember.js


add documentation on how to add different tracker stores to rasa core

is this still relevant?

I think it is not to important as long as the code is well documented.


Unpin backports-datetime-fromisoformat again

About
This patch intends to verify our observations shared at https://github.com/conda-forge/wetterdienst-feedstock/pull/102#issuecomment-1751357548, checking again that the recently released package backports-datetime-fromisoformat: 2.0.0-pyh0c530f3_1 is indeed broken in one way or another.
References

https://github.com/conda-forge/wetterdienst-feedstock/pull/102#issuecomment-1751357548
https://github.com/conda-forge/wetterdienst-feedstock/pull/104

Should be fixed by https://github.com/conda-forge/backports-datetime-fromisoformat-feedstock/pull/14.  I will restart CI as soon as those packages are available.

Because I just had the last 2 builds of backports-datetime-fromisoformat marked as broken:
https://github.com/conda-forge/admin-requests/pull/840
it is now a pretty high priority to get this in because the package produced in #102 will not be installable.

I am fixing the "quirk" in grayskull so that we will get python-eccodes instead of eccodes here:
https://github.com/conda/grayskull/pull/501


[BUG] - Node Process Killed When Calculating Next Epoch's Leadership Schedule

Internal/External
External   otherwise.
Area
Other   Any other topic (Delegation, Ranking, ...).
Summary
Node process killed when calculating next epoch's leadership schedule
Steps to reproduce
Steps to reproduce the behavior:

Start a node with

/usr/local/bin/cardano-node run +RTS -N -A16m -qg -qb -RTS --topology ${TOPOLOGY} --database-path ${DB_PATH} --socket-path ${SOCKET_PATH} --host-addr ${HOSTADDR} --port ${PORT} --config ${CONFIG} --shelley-kes-key ${KES} --shelley-vrf-key ${VRF} --shelley-operational-certificate ${CERT}

Calculate the next epoch's leadership schedule with

--mainnet \
--genesis $NODE_HOME/shelley-genesis.json \
--stake-pool-id $(cat $NODE_HOME/stakepoolid.txt) \
--vrf-signing-key-file $NODE_HOME/vrf.skey \
--next
--socket-path db/socket

The node process is killed a few minutes after execute step 2, and the node is restarted automatically
The output of step 2 pop out during the restarting of the node process and is empty:

SlotNo                          UTC Time
-------------------------------------------------------------

The Restarting of the node takes time longer than usual

Expected behavior
The output should looks like below
SlotNo                          UTC Time
-------------------------------------------------------------
     4073                   2021-12-29 17:26:54.998001755 UTC
     4126                   2021-12-29 17:27:00.298001755 UTC
     4206                   2021-12-29 17:27:08.298001755 UTC

System info (please complete the following information):

OS Name: Ubuntu

OS Version: 20.04

Node version:
cardano-node 8.9.2 - linux-x86_64 - ghc-8.10
git rev 424983fa186786397f5a99539f51710abf62c37b

CLI version:
cardano-cli <IP_ADDRESS> - linux-x86_64 - ghc-8.10
git rev 424983fa186786397f5a99539f51710abf62c37b

CPU: 8 core / 2.0 GHz

RAM: 32 GiB

Disk: 400 GiB

Screenshots and attachments
Part of the log related this issue is shown below, before and after the node process is killed:
May 28 13:31:36 ada-node cardano-node[1118012]: [ada-node:cardano.node.ChainDB:Notice:14260] [2024-05-28 13:31:36.23 UTC] Chain extended, new tip: 5a5299bed0f203b79e62eb5a23ac1a9d4b3a249e69bfd90cc40b6dea276ab027 at slot 1>
May 28 13:31:37 ada-node cardano-node[1118012]: [ada-node:cardano.node.LeadershipCheck:Info:14276] [2024-05-28 13:31:37.00 UTC] {"chainDensity":4.6852283e-2,"credentials":"Cardano","delegMapSize":1344902,"kind":"TraceStar>
May 28 13:31:37 ada-node cardano-node[1118012]: [ada-node:cardano.node.Forge:Info:14276] [2024-05-28 13:31:37.05 UTC] fromList [("credentials",String "Cardano"),("val",Object (fromList [("kind",String "TraceNodeNotLeader">
May 28 13:31:38 ada-node cardano-node[1118012]: [ada-node:cardano.node.LeadershipCheck:Info:14276] [2024-05-28 13:31:38.00 UTC] {"chainDensity":4.6852283e-2,"credentials":"Cardano","delegMapSize":1344902,"kind":"TraceStar>
May 28 13:31:38 ada-node cardano-node[1118012]: [ada-node:cardano.node.Forge:Info:14276] [2024-05-28 13:31:38.05 UTC] fromList [("credentials",String "Cardano"),("val",Object (fromList [("kind",String "TraceNodeNotLeader">
May 28 13:31:39 ada-node cardano-node[1118012]: [ada-node:cardano.node.LeadershipCheck:Info:14276] [2024-05-28 13:31:39.00 UTC] {"chainDensity":4.6852283e-2,"credentials":"Cardano","delegMapSize":1344902,"kind":"TraceStar>
May 28 13:31:39 ada-node cardano-node[1118012]: [ada-node:cardano.node.Forge:Info:14276] [2024-05-28 13:31:39.04 UTC] fromList [("credentials",String "Cardano"),("val",Object (fromList [("kind",String "TraceNodeNotLeader">
May 28 13:31:40 ada-node cardano-node[1118012]: [ada-node:cardano.node.LeadershipCheck:Info:14276] [2024-05-28 13:31:40.00 UTC] {"chainDensity":4.6852283e-2,"credentials":"Cardano","delegMapSize":1344902,"kind":"TraceStar>
May 28 13:31:40 ada-node cardano-node[1118012]: [ada-node:cardano.node.Forge:Info:14276] [2024-05-28 13:31:40.04 UTC] fromList [("credentials",String "Cardano"),("val",Object (fromList [("kind",String "TraceNodeNotLeader">
May 28 13:31:41 ada-node cardano-node[1118012]: [ada-node:cardano.node.LeadershipCheck:Info:14276] [2024-05-28 13:31:41.00 UTC] {"chainDensity":4.6852283e-2,"credentials":"Cardano","delegMapSize":1344902,"kind":"TraceStar>
May 28 13:31:41 ada-node cardano-node[1118012]: [ada-node:cardano.node.Forge:Info:14276] [2024-05-28 13:31:41.05 UTC] fromList [("credentials",String "Cardano"),("val",Object (fromList [("kind",String "TraceNodeNotLeader">
May 28 13:31:42 ada-node cardano-node[1118012]: [ada-node:cardano.node.LeadershipCheck:Info:14276] [2024-05-28 13:31:42.00 UTC] {"chainDensity":4.6852283e-2,"credentials":"Cardano","delegMapSize":1344902,"kind":"TraceStar>
May 28 13:31:42 ada-node cardano-node[1118012]: [ada-node:cardano.node.Forge:Info:14276] [2024-05-28 13:31:42.05 UTC] fromList [("credentials",String "Cardano"),("val",Object (fromList [("kind",String "TraceNodeNotLeader">
May 28 13:31:43 ada-node cardano-node[1118012]: [ada-node:cardano.node.LeadershipCheck:Info:14276] [2024-05-28 13:31:43.00 UTC] {"chainDensity":4.6852283e-2,"credentials":"Cardano","delegMapSize":1344902,"kind":"TraceStar>
May 28 13:31:43 ada-node cardano-node[1118012]: [ada-node:cardano.node.Forge:Info:14276] [2024-05-28 13:31:43.05 UTC] fromList [("credentials",String "Cardano"),("val",Object (fromList [("kind",String "TraceNodeNotLeader">
May 28 13:31:44 ada-node cardano-node[1118012]: [ada-node:cardano.node.LeadershipCheck:Info:14276] [2024-05-28 13:31:44.00 UTC] {"chainDensity":4.6852283e-2,"credentials":"Cardano","delegMapSize":1344902,"kind":"TraceStar>
May 28 13:31:44 ada-node cardano-node[1118012]: [ada-node:cardano.node.Forge:Info:14276] [2024-05-28 13:31:44.05 UTC] fromList [("credentials",String "Cardano"),("val",Object (fromList [("kind",String "TraceNodeNotLeader">
May 28 13:31:45 ada-node cardano-node[1118012]: [ada-node:cardano.node.LeadershipCheck:Info:14276] [2024-05-28 13:31:45.00 UTC] {"chainDensity":4.6852283e-2,"credentials":"Cardano","delegMapSize":1344902,"kind":"TraceStar>
May 28 13:31:45 ada-node cardano-node[1118012]: [ada-node:cardano.node.Forge:Info:14276] [2024-05-28 13:31:45.05 UTC] fromList [("credentials",String "Cardano"),("val",Object (fromList [("kind",String "TraceNodeNotLeader">
May 28 13:31:46 ada-node cardano-node[1118012]: [ada-node:cardano.node.LeadershipCheck:Info:14276] [2024-05-28 13:31:46.00 UTC] {"chainDensity":4.6852283e-2,"credentials":"Cardano","delegMapSize":1344902,"kind":"TraceStar>
May 28 13:31:46 ada-node cardano-node[1118012]: [ada-node:cardano.node.Forge:Info:14276] [2024-05-28 13:31:46.05 UTC] fromList [("credentials",String "Cardano"),("val",Object (fromList [("kind",String "TraceNodeNotLeader">
May 28 13:31:47 ada-node cardano-node[1118012]: [ada-node:cardano.node.LeadershipCheck:Info:14276] [2024-05-28 13:31:47.00 UTC] {"chainDensity":4.6852283e-2,"credentials":"Cardano","delegMapSize":1344902,"kind":"TraceStar>
May 28 13:31:47 ada-node cardano-node[1118012]: [ada-node:cardano.node.Forge:Info:14276] [2024-05-28 13:31:47.05 UTC] fromList [("credentials",String "Cardano"),("val",Object (fromList [("kind",String "TraceNodeNotLeader">
May 28 13:31:48 ada-node cardano-node[1118012]: [ada-node:cardano.node.LeadershipCheck:Info:14276] [2024-05-28 13:31:48.00 UTC] {"chainDensity":4.6852283e-2,"credentials":"Cardano","delegMapSize":1344902,"kind":"TraceStar>
May 28 13:31:48 ada-node cardano-node[1118012]: [ada-node:cardano.node.Forge:Info:14276] [2024-05-28 13:31:48.05 UTC] fromList [("credentials",String "Cardano"),("val",Object (fromList [("kind",String "TraceNodeNotLeader">
May 28 13:31:49 ada-node cardano-node[1118012]: [ada-node:cardano.node.LeadershipCheck:Info:14276] [2024-05-28 13:31:49.00 UTC] {"chainDensity":4.6852283e-2,"credentials":"Cardano","delegMapSize":1344902,"kind":"TraceStar>
May 28 13:31:49 ada-node cardano-node[1118012]: [ada-node:cardano.node.Forge:Info:14276] [2024-05-28 13:31:49.06 UTC] fromList [("credentials",String "Cardano"),("val",Object (fromList [("kind",String "TraceNodeNotLeader">
May 28 13:31:50 ada-node cardano-node[1118012]: [ada-node:cardano.node.LeadershipCheck:Info:14276] [2024-05-28 13:31:50.00 UTC] {"chainDensity":4.6852283e-2,"credentials":"Cardano","delegMapSize":1344902,"kind":"TraceStar>
May 28 13:31:50 ada-node cardano-node[1118012]: [ada-node:cardano.node.Forge:Info:14276] [2024-05-28 13:31:50.08 UTC] fromList [("credentials",String "Cardano"),("val",Object (fromList [("kind",String "TraceNodeNotLeader">
May 28 13:31:51 ada-node cardano-node[1118012]: [ada-node:cardano.node.LeadershipCheck:Info:14276] [2024-05-28 13:31:51.00 UTC] {"chainDensity":4.6852283e-2,"credentials":"Cardano","delegMapSize":1344902,"kind":"TraceStar>
May 28 13:31:51 ada-node cardano-node[1118012]: [ada-node:cardano.node.Forge:Info:14276] [2024-05-28 13:31:51.05 UTC] fromList [("credentials",String "Cardano"),("val",Object (fromList [("kind",String "TraceNodeNotLeader">
May 28 13:31:51 ada-node cardano-node[1118012]: [ada-node:cardano.node.ChainDB:Notice:14260] [2024-05-28 13:31:51.39 UTC] Chain extended, new tip: 22c923a0aab9b9656f877a87ad47d3635c31aeb30a3d2f724ad3afd7b47a3dd3 at slot 1>
May 28 13:31:52 ada-node cardano-node[1118012]: [ada-node:cardano.node.LeadershipCheck:Info:14276] [2024-05-28 13:31:52.00 UTC] {"chainDensity":4.6877716e-2,"credentials":"Cardano","delegMapSize":1344902,"kind":"TraceStar>
May 28 13:31:52 ada-node cardano-node[1118012]: [ada-node:cardano.node.Forge:Info:14276] [2024-05-28 13:31:52.05 UTC] fromList [("credentials",String "Cardano"),("val",Object (fromList [("kind",String "TraceNodeNotLeader">
May 28 13:31:53 ada-node cardano-node[1118012]: [ada-node:cardano.node.LeadershipCheck:Info:14276] [2024-05-28 13:31:53.00 UTC] {"chainDensity":4.6877716e-2,"credentials":"Cardano","delegMapSize":1344902,"kind":"TraceStar>
May 28 13:31:53 ada-node cardano-node[1118012]: [ada-node:cardano.node.Forge:Info:14276] [2024-05-28 13:31:53.05 UTC] fromList [("credentials",String "Cardano"),("val",Object (fromList [("kind",String "TraceNodeNotLeader">
May 28 13:31:54 ada-node cardano-node[1118012]: [ada-node:cardano.node.LeadershipCheck:Info:14276] [2024-05-28 13:31:54.00 UTC] {"chainDensity":4.6877716e-2,"credentials":"Cardano","delegMapSize":1344902,"kind":"TraceStar>
May 28 13:31:54 ada-node cardano-node[1118012]: [ada-node:cardano.node.Forge:Info:14276] [2024-05-28 13:31:54.06 UTC] fromList [("credentials",String "Cardano"),("val",Object (fromList [("kind",String "TraceNodeNotLeader">
May 28 13:31:55 ada-node cardano-node[1118012]: [ada-node:cardano.node.LeadershipCheck:Info:14276] [2024-05-28 13:31:55.00 UTC] {"chainDensity":4.6877716e-2,"credentials":"Cardano","delegMapSize":1344902,"kind":"TraceStar>
May 28 13:31:55 ada-node cardano-node[1118012]: [ada-node:cardano.node.Forge:Info:14276] [2024-05-28 13:31:55.06 UTC] fromList [("credentials",String "Cardano"),("val",Object (fromList [("kind",String "TraceNodeNotLeader">
May 28 13:31:56 ada-node cardano-node[1118012]: [ada-node:cardano.node.LeadershipCheck:Info:14276] [2024-05-28 13:31:56.00 UTC] {"chainDensity":4.6877716e-2,"credentials":"Cardano","delegMapSize":1344902,"kind":"TraceStar>
May 28 13:31:56 ada-node cardano-node[1118012]: [ada-node:cardano.node.Forge:Info:14276] [2024-05-28 13:31:56.05 UTC] fromList [("credentials",String "Cardano"),("val",Object (fromList [("kind",String "TraceNodeNotLeader">
May 28 13:31:57 ada-node cardano-node[1118012]: [ada-node:cardano.node.LeadershipCheck:Info:14276] [2024-05-28 13:31:57.00 UTC] {"chainDensity":4.6877716e-2,"credentials":"Cardano","delegMapSize":1344902,"kind":"TraceStar>
May 28 13:31:57 ada-node cardano-node[1118012]: [ada-node:cardano.node.Forge:Info:14276] [2024-05-28 13:31:57.04 UTC] fromList [("credentials",String "Cardano"),("val",Object (fromList [("kind",String "TraceNodeNotLeader">
May 28 13:31:58 ada-node cardano-node[1118012]: [ada-node:cardano.node.LeadershipCheck:Info:14276] [2024-05-28 13:31:58.00 UTC] {"chainDensity":4.6877716e-2,"credentials":"Cardano","delegMapSize":1344902,"kind":"TraceStar>
May 28 13:31:58 ada-node cardano-node[1118012]: [ada-node:cardano.node.Forge:Info:14276] [2024-05-28 13:31:58.04 UTC] fromList [("credentials",String "Cardano"),("val",Object (fromList [("kind",String "TraceNodeNotLeader">
May 28 13:31:59 ada-node cardano-node[1118012]: [ada-node:cardano.node.LeadershipCheck:Info:14276] [2024-05-28 13:31:59.00 UTC] {"chainDensity":4.6877716e-2,"credentials":"Cardano","delegMapSize":1344902,"kind":"TraceStar>
May 28 13:31:59 ada-node cardano-node[1118012]: [ada-node:cardano.node.Forge:Info:14276] [2024-05-28 13:31:59.05 UTC] fromList [("credentials",String "Cardano"),("val",Object (fromList [("kind",String "TraceNodeNotLeader">
May 28 13:32:01 ada-node cardano-node[1117999]: /home/ada/cardano-my-node/startCardanoNode.sh: line 11: 1118012 Killed                  /usr/local/bin/cardano-node run +RTS -N -A16m -qg -qb -RTS --topology ${TOPOLOGY} --d>
May 28 13:32:07 ada-node cardano-node[2985725]: Node configuration: NodeConfiguration {ncSocketConfig = SocketConfig {ncNodeIPv4Addr = Last {getLast = Just <IP_ADDRESS>}, ncNodeIPv6Addr = Last {getLast = Nothing}, ncNodePortNu>
May 28 13:32:07 ada-node cardano-node[2985725]: Listening on http://<IP_ADDRESS>:12798
May 28 13:32:07 ada-node cardano-node[2985725]: [ada-node:cardano.node.basicInfo.protocol:Notice:11] [2024-05-28 13:32:07.54 UTC] Byron; Shelley
May 28 13:32:07 ada-node cardano-node[2985725]: [ada-node:cardano.node.basicInfo.version:Notice:11] [2024-05-28 13:32:07.54 UTC] 8.9.1
May 28 13:32:07 ada-node cardano-node[2985725]: [ada-node:cardano.node.basicInfo.commit:Notice:11] [2024-05-28 13:32:07.54 UTC] da945ea983d4722a9ffe54250edba9a193a57cf0
May 28 13:32:07 ada-node cardano-node[2985725]: [ada-node:cardano.node.basicInfo.nodeStartTime:Notice:11] [2024-05-28 13:32:07.54 UTC] 2024-05-28 13:32:07.541878989 UTC
May 28 13:32:08 ada-node cardano-node[2985725]: [ada-node:cardano.node.basicInfo.systemStartTime:Notice:11] [2024-05-28 13:32:07.54 UTC] 2017-09-23 21:44:51 UTC
May 28 13:32:08 ada-node cardano-node[2985725]: [ada-node:cardano.node.basicInfo.slotLengthByron:Notice:11] [2024-05-28 13:32:07.54 UTC] 20s
May 28 13:32:08 ada-node cardano-node[2985725]: [ada-node:cardano.node.basicInfo.epochLengthByron:Notice:11] [2024-05-28 13:32:07.54 UTC] 21600
May 28 13:32:08 ada-node cardano-node[2985725]: [ada-node:cardano.node.basicInfo.slotLengthShelley:Notice:11] [2024-05-28 13:32:07.54 UTC] 1s
May 28 13:32:08 ada-node cardano-node[2985725]: [ada-node:cardano.node.basicInfo.epochLengthShelley:Notice:11] [2024-05-28 13:32:07.54 UTC] 432000
May 28 13:32:08 ada-node cardano-node[2985725]: [ada-node:cardano.node.basicInfo.slotsPerKESPeriodShelley:Notice:11] [2024-05-28 13:32:07.54 UTC] 129600
May 28 13:32:08 ada-node cardano-node[2985725]: [ada-node:cardano.node.basicInfo.slotLengthAllegra:Notice:11] [2024-05-28 13:32:07.54 UTC] 1s
May 28 13:32:08 ada-node cardano-node[2985725]: [ada-node:cardano.node.basicInfo.epochLengthAllegra:Notice:11] [2024-05-28 13:32:07.54 UTC] 432000
May 28 13:32:08 ada-node cardano-node[2985725]: [ada-node:cardano.node.basicInfo.slotsPerKESPeriodAllegra:Notice:11] [2024-05-28 13:32:07.54 UTC] 129600
May 28 13:32:08 ada-node cardano-node[2985725]: [ada-node:cardano.node.basicInfo.slotLengthMary:Notice:11] [2024-05-28 13:32:07.54 UTC] 1s
May 28 13:32:08 ada-node cardano-node[2985725]: [ada-node:cardano.node.basicInfo.epochLengthMary:Notice:11] [2024-05-28 13:32:07.54 UTC] 432000
May 28 13:32:08 ada-node cardano-node[2985725]: [ada-node:cardano.node.basicInfo.slotsPerKESPeriodMary:Notice:11] [2024-05-28 13:32:07.54 UTC] 129600
May 28 13:32:08 ada-node cardano-node[2985725]: [ada-node:cardano.node.basicInfo.slotLengthAlonzo:Notice:11] [2024-05-28 13:32:07.54 UTC] 1s
May 28 13:32:08 ada-node cardano-node[2985725]: [ada-node:cardano.node.basicInfo.epochLengthAlonzo:Notice:11] [2024-05-28 13:32:07.54 UTC] 432000
May 28 13:32:08 ada-node cardano-node[2985725]: [ada-node:cardano.node.basicInfo.slotsPerKESPeriodAlonzo:Notice:11] [2024-05-28 13:32:07.54 UTC] 129600
May 28 13:32:08 ada-node cardano-node[2985725]: [ada-node:cardano.node.basicInfo.slotLengthBabbage:Notice:11] [2024-05-28 13:32:07.54 UTC] 1s
May 28 13:32:08 ada-node cardano-node[2985725]: [ada-node:cardano.node.basicInfo.epochLengthBabbage:Notice:11] [2024-05-28 13:32:07.54 UTC] 432000
May 28 13:32:08 ada-node cardano-node[2985725]: [ada-node:cardano.node.basicInfo.slotsPerKESPeriodBabbage:Notice:11] [2024-05-28 13:32:07.54 UTC] 129600
May 28 13:32:08 ada-node cardano-node[2985725]: [ada-node:cardano.node.basicInfo.slotLengthConway:Notice:11] [2024-05-28 13:32:07.54 UTC] 1s
May 28 13:32:08 ada-node cardano-node[2985725]: [ada-node:cardano.node.basicInfo.epochLengthConway:Notice:11] [2024-05-28 13:32:07.54 UTC] 432000
May 28 13:32:08 ada-node cardano-node[2985725]: [ada-node:cardano.node.basicInfo.slotsPerKESPeriodConway:Notice:11] [2024-05-28 13:32:07.54 UTC] 129600
May 28 13:32:08 ada-node cardano-node[2985725]: [ada-node:cardano.node.startup:Info:11] [2024-05-28 13:32:08.22 UTC] Config path /home/ada/cardano-my-node/config.json, Network magic NetworkMagic {unNetworkMagic = 76482407>
May 28 13:32:08 ada-node cardano-node[2985725]: [ada-node:cardano.node.startup:Info:11] [2024-05-28 13:32:08.22 UTC] Era Byron, Slot length 20s, Epoch length 21600
May 28 13:32:08 ada-node cardano-node[2985725]: [ada-node:cardano.node.startup:Info:11] [2024-05-28 13:32:08.23 UTC] Era Shelley, Slot length 1s, Epoch length 432000, Slots per KESPeriod 129600
May 28 13:32:08 ada-node cardano-node[2985725]: [ada-node:cardano.node.startup:Info:11] [2024-05-28 13:32:08.23 UTC] Era Allegra, Slot length 1s, Epoch length 432000, Slots per KESPeriod 129600
May 28 13:32:08 ada-node cardano-node[2985725]: [ada-node:cardano.node.startup:Info:11] [2024-05-28 13:32:08.23 UTC] Era Mary, Slot length 1s, Epoch length 432000, Slots per KESPeriod 129600
May 28 13:32:08 ada-node cardano-node[2985725]: [ada-node:cardano.node.startup:Info:11] [2024-05-28 13:32:08.23 UTC] Era Alonzo, Slot length 1s, Epoch length 432000, Slots per KESPeriod 129600
May 28 13:32:08 ada-node cardano-node[2985725]: [ada-node:cardano.node.startup:Info:11] [2024-05-28 13:32:08.23 UTC] Era Babbage, Slot length 1s, Epoch length 432000, Slots per KESPeriod 129600
May 28 13:32:08 ada-node cardano-node[2985725]: [ada-node:cardano.node.startup:Info:11] [2024-05-28 13:32:08.23 UTC] Era Conway, Slot length 1s, Epoch length 432000, Slots per KESPeriod 129600
May 28 13:32:08 ada-node cardano-node[2985725]: [ada-node:cardano.node.startup:Warning:11] [2024-05-28 13:32:08.23 UTC] You are using an early release of peer-to-peer capabilities, please report any issues.
May 28 13:32:08 ada-node cardano-node[2985725]: [ada-node:cardano.node.startup:Info:11] [2024-05-28 13:32:08.23 UTC] startup time:<PHONE_NUMBER>
May 28 13:32:08 ada-node cardano-node[2985725]: [ada-node:cardano.node.startup:Info:11] [2024-05-28 13:32:08.23 UTC]
May 28 13:32:08 ada-node cardano-node[2985725]: node addresses:          <IP_ADDRESS>:6000
May 28 13:32:08 ada-node cardano-node[2985725]: local socket:            /home/ada/cardano-my-node/db/socket
May 28 13:32:08 ada-node cardano-node[2985725]: node-to-node versions:   [7,8,9,10,11,12,13]
May 28 13:32:08 ada-node cardano-node[2985725]: node-to-client versions: [9,10,11,12,13,14,15]
May 28 13:32:08 ada-node cardano-node[2985725]: [ada-node:cardano.node.startup:Info:11] [2024-05-28 13:32:08.23 UTC] initiator and responder diffusion mode
May 28 13:32:08 ada-node cardano-node[2985725]: [ada-node:cardano.node.startup:Info:11] [2024-05-28 13:32:08.23 UTC]
May 28 13:32:08 ada-node cardano-node[2985725]: Local Root Groups:
May 28 13:32:08 ada-node cardano-node[2985725]:   (HotValency {getHotValency = 1},WarmValency {getWarmValency = 1},[(RelayAccessAddress "<IP_ADDRESS>" 6000,(DoNotAdvertisePeer,IsNotTrustable))])
May 28 13:32:08 ada-node cardano-node[2985725]: Public Roots:
May 28 13:32:08 ada-node cardano-node[2985725]:
May 28 13:32:08 ada-node cardano-node[2985725]: Don't use ledger to get root peers.
May 28 13:32:08 ada-node cardano-node[2985725]: [ada-node:cardano.node.ChainDB:Info:11] [2024-05-28 13:32:08.23 UTC] Started opening Chain DB
May 28 13:32:08 ada-node cardano-node[2985725]: [ada-node:cardano.node.ChainDB:Info:11] [2024-05-28 13:32:08.23 UTC] Started opening Immutable DB
May 28 13:32:08 ada-node cardano-node[2985725]: [ada-node:cardano.node.ChainDB:Info:11] [2024-05-28 13:32:08.55 UTC] Validating chunk no. 0 out of 5800. Progress: 0.00%
May 28 13:32:09 ada-node cardano-node[2985725]: [ada-node:cardano.node.ChainDB:Info:11] [2024-05-28 13:32:09.26 UTC] Validated chunk no. 0 out of 5800. Progress: 0.02%
May 28 13:32:09 ada-node cardano-node[2985725]: [ada-node:cardano.node.ChainDB:Info:11] [2024-05-28 13:32:09.26 UTC] Validating chunk no. 1 out of 5800. Progress: 0.02%
May 28 13:32:10 ada-node cardano-node[2985725]: [ada-node:cardano.node.ChainDB:Info:11] [2024-05-28 13:32:10.22 UTC] Validated chunk no. 1 out of 5800. Progress: 0.03%
May 28 13:32:10 ada-node cardano-node[2985725]: [ada-node:cardano.node.ChainDB:Info:11] [2024-05-28 13:32:10.22 UTC] Validating chunk no. 2 out of 5800. Progress: 0.03%
May 28 13:32:11 ada-node cardano-node[2985725]: [ada-node:cardano.node.ChainDB:Info:11] [2024-05-28 13:32:11.17 UTC] Validated chunk no. 2 out of 5800. Progress: 0.05%
May 28 13:32:11 ada-node cardano-node[2985725]: [ada-node:cardano.node.ChainDB:Info:11] [2024-05-28 13:32:11.17 UTC] Validating chunk no. 3 out of 5800. Progress: 0.05%
May 28 13:32:12 ada-node cardano-node[2985725]: [ada-node:cardano.node.ChainDB:Info:11] [2024-05-28 13:32:12.18 UTC] Validated chunk no. 3 out of 5800. Progress: 0.07%
May 28 13:32:12 ada-node cardano-node[2985725]: [ada-node:cardano.node.ChainDB:Info:11] [2024-05-28 13:32:12.18 UTC] Validating chunk no. 4 out of 5800. Progress: 0.07%

Additional context
I noticed this issue recently, the epoch leader calculation was fine in April this year.

You likely ran out of memory, on a typical system you can check dmesg -T | grep [c]ardano-node

You likely ran out of memory, on a typical system you can check dmesg -T | grep [c]ardano-node

Thanks for the comment, the command you suggested gives the following output, which indicates that the node process was killed due to OOM:
[Tue May 28 18:03:19 2024] [2985725]  1000 2985725 268450990  4969040 39989248        0             0 cardano-node
[Tue May 28 18:03:19 2024] oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=/,mems_allowed=0,global_oom,task_memcg=/system.slice/cardano-node.service,task=cardano-node,pid=2985725,uid=1000
[Tue May 28 18:03:19 2024] Out of memory: Killed process 2985725 (cardano-node) total-vm:1073803960kB, anon-rss:19876160kB, file-rss:0kB, shmem-rss:0kB, UID:1000 pgtables:39052kB oom_score_adj:0

However, this is unexpected since the server I am using has RAM larger than suggested by Cardano official docs, and the server is purely used for Cardano node operating.
Would you suggest any solutions other than upgrade RAM space?

If you're using -xn for any RTS options for your cardano-node run command, that might be the issue. I have to remove that option before running leaderlogs or node will crash with OOM.


dx serve fails with wasm*-unknown-unknown

Dependencies do not compile with wasm*-unknown-unknown
dx serve
[WARN] You appear to be creating a Dioxus project from scratch; we will use the default config
[INFO] 🚅 Running build command...
Error: 🚫 Serving project failed: error: the wasm*-unknown-unknown targets are not supported by default, you may need to enable the "js" feature. For more information see: https://docs.rs/getrandom/#webassembly-support
   --> /SDKs/rust/cargo/registry/src/index.crates.io-6f17d22bba15001f/getrandom-0.2.10/src/lib.rs:285:9
    |
285 | /         compile_error!("the wasm*-unknown-unknown targets are not supported by \
286 | |                         default, you may need to enable the \"js\" feature. \
287 | |                         For more information see: \
288 | |                         https://docs.rs/getrandom/#webassembly-support");
    | |________________________________________________________________________^

Steps To Reproduce
Steps to reproduce the behavior:
cargo new --bin dioxusdemo
cd dioxusdemo
rustup target add wasm32-unknown-unknown
cargo install dioxus-cli --locked
cargo add dioxus
cargo add dioxus-web

edit src/main.rs
#![allow(non_snake_case)]
use dioxus::prelude::*;

fn main() {
    println!("Hello, world!");
    dioxus_web::launch(App);
}

fn App(cx: Scope) -> Element {
    cx.render(rsx! {
        div {
            "Hello, world!"
        }
    })
}

run dx serve
dx serve

Expected behavior
launch web service on <IP_ADDRESS>
Environment:

Dioxus version: 0.4.0
Rust version: 1.70
OS info: [e.g. MacOS]
App platform: [e.g. web, desktop]

i was in the process of writing out my steps when i hit ctrl enter instead of shift enter, submitting this issue before it was ready.
replaying all the steps a second time worked.
if you cargo add dioxus-cli instead of cargo install dioxus-cli everything breaks.


unable to get ./namebench binary on gnu-linux.

Dear tstromberg,
I tried with your notes and was unable to get a namebench binary in my directory :-
~/games/namebench$ export GOPATH=pwd
~/games/namebench$ git clone https://github.com/google/namebench.git src/github.com/google/namebench
Cloning into 'src/github.com/google/namebench'...
remote: Reusing existing pack: 5588, done.
remote: Total 5588 (delta 0), reused 0 (delta 0)
Receiving objects: 100% (5588/5588), 25.80 MiB | 28.00 KiB/s, done.
Resolving deltas: 100% (3951/3951), done.
Checking connectivity... done.
~/games/namebench$ go get github.com/mattn/go-sqlite3
~/games/namebench$ go get code.google.com/p/go.net/publicsuffix
~/games/namebench$ go get github.com/miekg/dns
~/games/namebench$ ls
pkg  src
$ cd src/github.com/google/namebench/
~/games/namebench/src/github.com/google/namebench$ go build namebench.go
~/games/namebench/src/github.com/google/namebench$ ./namebench
2014/06/19 02:51:05 URL: http://<IP_ADDRESS>:55168/
2014/06/19 02:51:05 error running /Applications/node-webkit.app/Contents/MacOS/node-webkit ./ui/app.nw: exec: "/Applications/node-webkit.app/Contents/MacOS/node-webkit": stat /Applications/node-webkit.app/Contents/MacOS/node-webkit: no such file or directory
As can be seen the webserver is up but no UI. I was able to browse via the browser. It just has the browser 'google chrome' and the states stuck as 'United States of America' there is no drop-down list or anything.

Same as above after following qgnox instructions. I fiddled and got the UI to appear. The drop down lists have only one item.


[7.x] Make soft delete use DateTime

Make soft delete use DateTime instead of checking on null value only. "Future Auto Delete"

I don't think using the server time to determine future deletes in that way is a good idea. The time might not be exactly correct, or may differ between different servers.

You should ask the database to determine the current time, and not do it in PHP.

Thanks for your pull request to Laravel!
Unfortunately, I'm going to delay merging this code for now. To preserve our ability to adequately maintain the framework, we need to be very careful regarding the amount of code we include.
If possible, please consider releasing your code as a package so that the community can still take advantage of your contributions!
If you feel absolutely certain that this code corrects a bug in the framework, please "@" mention me in a follow-up comment with further explanation so that GitHub will send me a notification of your response.


first pass: scheduled rules + queries

Background
First pass at Scheduled Queries for snowflake monitoring.  This is a subset of the recs from snowflake for monitoring your own snowflake instance.
Changes

Added new queries + rules for basic snowflake monitoring.

Testing

manual testing
make test ci

awesome, excited to see snowflake coverage

Tested these in the snowflake staging environment, and it appears we need some additional newlines to get the comments to parse correctly out of YAML.  Additionally, both the brute force detections are failing for this reason:
Lambda error returned: panther-snowflake-api: Column name 'array_agg(distinct error_code)' contains characters not allowed in a scheduled query. Please choose names without spaces or : . , - " ( )

It appears to be unhappy with the space in distinct error_code. Not sure what the fix is here just calling it  out.

Tested these in the snowflake staging environment, and it appears we need some additional newlines to get the comments to parse correctly out of YAML. Additionally, both the brute force detections are failing for this reason:

Whoops, sorry - I had fixed this by removing the comments and putting them in the description (But hadn't pushed that version up).  Did you get it to work with fixing the spacing?  If so I won't try to merge my changes.

Whoops, sorry - I had fixed this by removing the comments and putting them in the description (But hadn't pushed that version up). Did you get it to work with fixing the spacing? If so I won't try to merge my changes. For example:

Yes, the extra new lines I added allowed the bulk upload to complete successfully with the comments in the query itself.

Is this in the backend? I can run the brute force versions I have successfully (just bulk uploaded and ran manually)

I tried uploading them with panther_analysis_tool zip and the bulk upload page in the v1.20 release environment. If you go to saved queries there you'll see they're disabled since they wouldn't save as enabled. Would you like me to  check the dynamo table for their values?

Tested these in the snowflake staging environment, and it appears we need some additional newlines to get the comments to parse correctly out of YAML. Additionally, both the brute force detections are failing for this reason:
Lambda error returned: panther-snowflake-api: Column name 'array_agg(distinct error_code)' contains characters not allowed in a scheduled query. Please choose names without spaces or : . , - " ( )

It appears to be unhappy with the space in distinct error_code. Not sure what the fix is here just calling it out.

I let the suggested fix. You should always use column aliases with aggregate functions for saved queries.

That fixed it, thanks @rleighton!


Automatic PR from RestAPI-PR456

Generated from RestAPI PR: https://github.com/Azure/azure-rest-api-specs/pull/456

Coverage decreased (-0.07%) to 58.302% when pulling 518fa15219e679f92e378ac946063773a60ed894 on AutorestCI:RestAPI-PR456 into 1c6ff68159c41bad57dfa1ffc5557cd50a198cfd on Azure:dev.


Suggestions

I've tried this for about an hour by now, really impressive.
One suggestions that i have would be Autoshoot Damage calculation:
I've seen a few cheats have this. Basically when autoshoot "visible only" is disabled, make sure that you're at least causing damage to the target and not just attempting to shoot through all walls
and the only issue i've had so far is that triggerbot seems to be broken in arms race mode, but it was working in aim training map

Added wall penetration system.


ci: improve handling of public-key-check

Currently, in order to publish ig-k8s image / gadget images on a fork users will have to:

Set secrets for cosign (COSIGN_PRIVATE_KEY/COSIGN_PASSWORD)
Update the public key in source (pkg/resources/inspektor-gadget.pub)

Otherwise public-key-check job will fail and ig-k8s image /gadgets images won't be published. The idea of this PR is to improve this workflow by not signing images by default on forks. public-key-check is removed from the needs of both the image publishing steps, allowing images to be published but not signed on forks. Having said that, public-key-check is moved to release to ensure if incorrect keys are configured we won't be able to release. So it isn't a fatal job for CI runs on main but only for releases.
Also tests need to be adapted to allow running without verification on a fork!
Testing Done

A CI run in fork with Actions secrets configured (not Dependabot secrets) checks the public key: https://github.com/mqasimsarfraz/inspektor-gadget/actions/runs/9595327823/job/26459837791
A CI run in fork without Actions secrets configured skips the public key checking: https://github.com/mqasimsarfraz/inspektor-gadget/actions/runs/9594669084

Please open an issue indicating further steps to improve this PR.

I opened https://github.com/inspektor-gadget/inspektor-gadget/issues/3045. Please feel free to add if I missed something.
Also, I will keep the PR open for now so we can get more reviews (cc: @eiffel-fl)

If I understand correctly, now we only check the correspondence between the in-source public key and secret private key before releasing.

Yes, but the check will run for all the changes to main (even if we remove the secrets) and CI will be marked red if there is a mismatch. I know it isn't ideal but should help us catch it early!

Is my understanding of all the consequences correct?

Yeah, sounds complete to me.
(not related to this PR but I feel we need to think/document a way in case we want to rotate our private key)

Please, open an issue for this, I would need to check how this is normally handled before writing anything.

Done, https://github.com/inspektor-gadget/inspektor-gadget/issues/3048

Thanks for the reviews!


Inline stats functions to be generic

Attempt to address issue https://github.com/fslaborg/Deedle/issues/410

In order to change functions to be inline, I have to remove internal attribute for StatsHelper function. Otherwise I got error message. "error FS1113: The value 'mean' was marked inline but its implementation makes use of an internal or private function which is not sufficiently accessible" It's similar to https://github.com/hedgehogqa/fsharp-hedgehog/blob/master/src/Hedgehog/Range.fs#L94. Hence I renamed StatsHelper to be StatsInternal.
Basic stats functions and level stats functions shall work for int, decimal and float now. The function outputs are still float no matter what input type is.
I cannot make expanding window and moving window functions work. Both cases call applySeriesProj. But applySeriesProj has to be internal as it's calling other internal functions. I assume it's because of series.VectorBuilder as it's an internal member. @tpetricek Any idea how to get around it?

I've figured out how to make expanding/moving window function inline. I removed both internal and inline attribute for applySeriesProj and it works smooth afterwards.


OneDrive personal account unable to aquire offline_access scope

I am trying to acquire an offline access/refresh token pair on my web api server using the on behalf of flow
https://docs.microsoft.com/en-us/azure/active-directory/develop/v2-oauth2-on-behalf-of-flow
I am acquiring the id token for the assertion on the client side and sending to the server. My flow works correctly for OneDrive for business account, but for personal OneDrive I get an error trying to get an access token.
const endpoint = 'https://login.microsoftonline.com/common/oauth2/v2.0/token';
{
  client_id            : config.msgraph.clientId,
  client_assertion_type: 'urn:ietf:params:oauth:client-assertion-type:jwt-bearer',
  scope                : ['Files.Read.All', 'Files.ReadWrite.All', 'User.Read', 'offline_access'].join(' '),
  grant_type         : 'urn:ietf:params:oauth:grant-type:jwt-bearer',
  requested_token_use: 'on_behalf_of',
  client_assertion: CreateJWT()
};

{
  "error": "invalid_grant",
  "error_description": "AADSTS70000: The request was denied because one or more scopes requested are unauthorized or expired. The user must first sign in and grant the client application access to the requested scope.\\r\\nTrace ID: 38a5157b-23ee-4112-8833-18036d524a00\\r\\nCorrelation ID: 85e47fe8-8c8a-45ae-83c6-94d785af1ff8\\r\\nTimestamp: 2021-02-28 23:29:51Z",
  "error_codes": [70000],
  "timestamp": "2021-02-28 23:29:51Z",
  "trace_id": "38a5157b-23ee-4112-8833-18036d524a00",
  "correlation_id": "85e47fe8-8c8a-45ae-83c6-94d785af1ff8",
  "error_uri": "https://login.microsoftonline.com/error?code=70000",
  "suberror": "consent_required"
}

Is offline_access supported for OneDrive Personal? I haven't found anything documented to suggest otherwise.
Library

[ x ]<EMAIL_ADDRESS>or<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>
Framework

[ ] Angular
[ ] React
[ ] Other

Description
Error Message

MSAL Configuration
// Provide configuration values here.
// For Azure B2C issues, please include your policies.

Reproduction steps
// Provide relevant code snippets here.
// For Azure B2C issues, please include your policies.

Expected behavior
Identity Provider

[ ] Azure AD
[ ] Azure B2C Basic Policy
[ ] Azure B2C Custom Policy
[ ] ADFS
[ ] Other

Browsers/Environment

[ ] Chrome
[ ] Firefox
[ ] Edge
[ ] Safari
[ ] IE
[ ] Other (Please add browser name here)

Regression

[ ] Did this behavior work before?
Version:

Security

[ ] Is this issue security related?

Source

[ ] Internal (Microsoft)
[ ] Customer request

@arsnyder16 This looks like it is an expected error, it needs to be handled with an interactive call with the same set of scopes to allow the user to consent.
It looks like you are using msal 1.x to acquire tokens, I don't think you need to send offline_access for this? I will double check to make sure.

@pkanher617 Just so i am clear. This is expected behavior for personal accounts but not for business accounts? My flow is working fine for non personal accounts.
I have tried requesting offline_access on the client, and i had no change in behavior.  I am trying to establish on_behalf_of on my web server. Currently to do that i am just sending the users idToken retrieved from msal to the server and from there I can establish an access token/refresh token pair for the server to use

I tracked down the issue within the onedrive picker there is code that is prepending https://graph.microsoft.com/ to any scope passed, but https://graph.microsoft.com/offline_access is an invalid scope.
I notice that the picker automatically passes profile, openid. I would be nice if this were to also pass offline_access or not prepend graph.microsoft.com
case c.default.AADv2:
t = (i = "profile openid https://graph.microsoft.com/User.Read " + (r = e).scopes.map(function(e) {
return "https://graph.microsoft.com/" + e
}).join(" "),

Could you share a link to that code? We'll track it down internally.

@hpsin  I have not been able to find an repo that hosts this code but maybe you can find based on this information
https://docs.microsoft.com/en-us/onedrive/developer/controls/file-pickers/js-v72/save-file?view=odsp-graph-online
hosted here: https://js.live.net/v7.2/OneDrive.js
I have also logged: https://github.com/OneDrive/onedrive-api-docs/issues/1445
@KevinTCoughlin @VesaJuvonen @JeremyKelley @chackman can any of you assist?

just some more information related.
I manually modified the OneDrive.js file and added offline_access beside profile openid and everything worked as expected.  As a side note the first thing i tried to do was remove the prepending of https://graph.microsoft.com/ but that actually failed to show the correct consent page.   So it appears either the library properly filter out profile , openid, offline_accesss and not prepend graph.microsoft.
One other odd behavior i notice with this library is i can't just use my scopes that i use for msal
['profile', 'openid', 'offline_access', 'Files.Read.All', 'Files.ReadWrite.All', 'People.Read', 'Contacts.Read', 'User.ReadBasic.All']
The library is expecting to append All to Files.Read and Files.ReadWrite so i have to actually pass `'Files.Read', Files.ReadWrite' instead

This is useful information about the offline_access scope, @arsnyder16. Thanks for posting your workaround!


Harden flaky atb integration tests

Task/Issue URL: https://app.asana.com/0/361428290920652/1109730748569886
Description:
Harden flaky atb integrations tests:

now backgrounding rather than killing app (which causes issues)
separating statistics request and search request queues as the atb and search requests are fired at the same time so order is non-deterministic. We still keep all the statistics (atb and exti together) as order there is defined and important.

Steps to test this PR:

Check CI to ensure tests are passing there
Also, run the tests locally and make sure they pass!

Internal references:
Software Engineering Expectations
Technical Design Template

@brindy I have run this 10 times locally and 10 times on CI and it has passed (on CI there was a failed & stalled build but those died after the tests had passed so I'm counting them as successes).


Wrong user returned in API: GET /repos/{owner}/{repo}/pulls/{index}/reviews/{id}/comments

Gitea version (or commit ref): v1.13.5
Git version: 2.29.2
Operating system: Debian/buster
Release from https://dl.gitea.io/gitea/1.13.5/gitea-1.13.5-linux-amd64
Also tried self-built v1.13.5
Database (use [x]):

[ ] PostgreSQL
[X] MySQL
[ ] MSSQL
[ ] SQLite

Description
I use the API to download the comments of a review.
In the returned json all comments have the the same user, although the comments were done by different users (as can be seen in the web frontend).
In modules/convert/pull_review.go ToPullReviewCommentList uses the reviewer, but I think it should use the poster of the comment. This fixes it for me:
--- a/modules/convert/pull_review.go
+++ b/modules/convert/pull_review.go
@@ -94,7 +94,7 @@ func ToPullReviewCommentList(review *models.Review, doer *models.User) ([]*api.P
                apiComment := &api.PullReviewComment{
                    ID:           comment.ID,
                    Body:         comment.Content,
-                   Reviewer:     ToUser(review.Reviewer, doer != nil, auth),
+                   Reviewer:     ToUser(comment.Poster, doer != nil, auth),
                    ReviewID:     review.ID,
                    Created:      comment.CreatedUnix.AsTime(),
                    Updated:      comment.UpdatedUnix.AsTime(),

@sotho Hello, Thanks for your response, would you please send a pull request to fix it?Thanks.

Pull request #15139 opened


Print content

The way how widget is being sent to print is beautiful, but there is missing one important  thing - widget header. Without it, it's kind of useless and very confusing.

Please create redmine issue. I added you as reporter to DSW project.


Use decode_int63 for reading old offsets

Fixing existing stores 0 and existing stores 2.
While this fixes the test, I think we should move to using the new IO in traverse_pack_file instead of the legacy_io, as the legacy_io cannot read files in V3.

I think these changes also (partially?) fix test_RW_no_version_bump (which also hits the read_offset_from_legacy_file issue)


Fixes typo in Readme.md

While reading the Readme.md file I found a typo in the word "installed" which was written as "instealled".

Thanks for taking the time to submit a fix @jonathadv! 🙏🏼


include files with password in .gitignore

for security reasons:
create .env.local and add to .gitignore, move all config with passwords to .env.local
add cookiecutter-config-file.yml to .gitignore

Yep, you can definitely do that! Nevertheless, that would be directly on your repo, not in this one that is the template with the defaults to get something runnable right after cloning. Thanks for the interest! :coffee:


feat: cannot add repeated and invalids URL on the list

Hello!
i added a feature to prevent repeated urls and invalid URL in list

Thank you @fatekkl
I loved your idea! I commented on some changes you can make before implementing it in FocusPocus.
💛 thanks! I'm glad you liked it, I'm traveling but when I get back I'll sort everything out


Can't run minecraft with plugin's armour

hey there ik u said the problem was my setup but i in fact tested on other devices and the error continued, sorry to be so annoying but it seems to be a recurring issue
as seen in these
https://mcreator.net/forum/93978/why-my-game-doesnt-open-geckolib-plugin
https://www.reddit.com/r/MCreator/comments/1e29luu/comment/ld3v9vs/
these r the 2 i found
this guy actually finds a way by changing the export mode on blockbench plugin idk if u r the owner of that one tho
https://mcreator.net/forum/109386/game-freezes-loading-screen#google_vignette
couldnt find the "logs he mentioned"

I can't solve issues with speculation. I need your crashlog.

.

I could send the Minecraft crash log, the mcreator graddle js doesnt load

more than likely an issue with your model file as all these cases end up being. blockbench just loves to dish out broken models every now and then.


feat: support use listener port as containerPort

What type of PR is this?

What this PR does / why we need it:
Which issue(s) this PR fixes:

support use listener port as containerPort, allow users to difine container port via listener port, for direct access scenarios.

close for duplicated with https://github.com/envoyproxy/gateway/pull/3333


Change crossbeam-channel's license to MIT OR Apache-2.0

Fixes #536
Was there breaking changes since the last published versions? it looks like it was 5 months ago so it sounds likely. If so I suspect you'll want to wait for other potential changes before making a 0.5 release, would it be possible to create a 0.4 branch and change publish the license update there on top of 0.4.2's revision?
That would allow me to use crossbeam-channel in WebRender.

The CI doesn't provide much information about the failing tests. They had been pending for a long long time so I suppose the backlog was just canceled/timed-out at some point.

Published a new patch version of crossbeam-channel that includes this PR.

Thanks a lot !

Hm, the master branch was supposed to contain breaking changes... But does the compile seem to succeed?
Either way, I think we need to create the v0.7 branch and backport this and publish a new version of crossbeam-channel. (0.4.3 has UB (there is no UB in versions 0.4.2 or less), and adding default-feature is technically a breaking change)
(I did the same thing in crossbeam-queue before, but I pushed only the tag without pushing the branch; https://github.com/crossbeam-rs/crossbeam/issues/523#issuecomment-642347864)

Published crossbeam-channel v0.4.4, and yanked crossbeam-channel v0.4.3.


[Bug] elasticstack_fleet_integration_policy render consistent diff for policy secret

Describe the bug
When configuring policy secret via integration policy resource, the provider and terraform always renders a diff even though the value is not changed.
I'm trying to configure the universal profiler integration.
To Reproduce
Steps to reproduce the behavior:
resource "elasticstack_fleet_integration_policy" "profiling" {
  name      = "profiling"

  agent_policy_id     = elasticstack_fleet_agent_policy.this.policy_id
  integration_name    = data.elasticstack_fleet_integration.profiling.name
  integration_version = data.elasticstack_fleet_integration.profiling.version

  input {
    input_id     = "universal_profiling_agent-pf-host-agent"
    streams_json = jsonencode({})
    vars_json = jsonencode({
      "profiler.collector"    = "cloud-es.io"
      "profiler.secret_token" = "Hunter2"
      "profiler.disable_tls"  = false
    })
  }
}

Apply once, then make a plan.
Expected behavior
There should not be any diff in the second plan.
Versions (please complete the following information):

OS: MacOS
Terraform Version: v1.7.5
Provider version 0.1.4
Elasticsearch Version 8.14.3

CC @Kushmaro. Maybe related to #617.

We are affected by this issue as well. In our case, it is with the Azure Logs integration where the connection_string and storage_account_key values in the vars_json are now replaced with something like:
{
  id = "oJo..."
  isSecretRef = true
}

when the old value was just a string.
Now it is unclear how to continue, since executing our Terraform would overwrite the referrences to the secret values (and we don't know, if this is safe to do), but on the other hand we do not have a way to manage and import the secret values either.

I looked at this problem again and I wonder, what the plan is at Elastic on this.
Based on secrets.md the idea is to prevent Kibana and Fleet users from having read access to the secrets, that are part of the fleet integrations. So far, so good. But now it looks like there is no API left that could be used by e.g. Terraform to manage this as Iaas.
I would be thankful, if someone from Elastic could elaborate on this problem and provide some more details on the plan forward and if possible on a timeline.

provide some more details on the plan forward

To be clear, there's no definitive plan here at the moment. This is just based on similar issues in other resources. Some options though:

Having write only attributes. For example API keys will not detect 'drift' in the actual API Key, it's read during the create request and assumed to be static as it's not returned during subsequent read operations. Technically the key could be deleted and recreated outside of Terraform and we wouldn't detect the change. This works well for concrete attributes (i.e not part of a homogeneous JSON blob, which we're not dealing with in this case.
lifecycle.ignore_changes. This obviously isn't ideal since Terraform wouldn't correct any legitimate drift within vars_json.

In the providers current state, we can't easily apply 1 in this case since there's just a JSON bag of properties that is used for a variety of input types, and 2 is far from ideal for practitioners. To properly address this issue, we'd need to make some changes to how this resource is implemented, but that's a larger chunk of work and something that will likely be addressed as part of https://github.com/elastic/terraform-provider-elasticstack/issues/617. There's no timeframe on either of these issues at the moment sorry.

@tobio Thanks for your reply. The current situation is really unfortunate for us. We have a paid subscription of Elasticsearch in the Elastic Cloud. We use terraform to manage the Elastic Cloud deployment as well as the configuration of Elasticsearch including the Fleet integrations.
This worked until we updated our Elasticsearch instance to 8.14.3 and now, we are basically in a dead end, since we can not update our Terraform configuration to compensate for the drift cause by the updates of the fleet integrations, which became necessary due to the update of Elasticsearch.
Already before this change, it was not simple to keep the drift under control, which is caused by the updates of the Fleet integrations. But we managed to do so using tfreveal which showed us the differences in the nested json values (which are additionally marked as sensitive).
But with this recent change, I feel like we are in a dead end.
At some point I read something about a setting, which would allow to disable the new behavior for secrets. Do you have any information about this and how we could enable this in our Elasticsearch instance on Elastic Cloud?

@Kushmaro , @kpollich I would appreciate a short update on this issue after your internal sync. Thanks.

Hi @kpollich
Thanks for the insights you shared in your post above. I understand the underlying need to better protect the secrets, that are stored within Elasticsearch.
That being said, the whole situation is very unfortunate for us. We invested significantly in managing our Elastic Stack infrastructure with Terraform. Now we learn, that this is an afterthought for Elastic and it might break at any time, to the extend, where one is forced to lock down versions, basically leading to a situation, where one can no longer update Elasticsearch and Kibana. This is pretty problematic in my opinion and I am now really unsure, how I can sell / explain this to my managers.
Having a situation, where one half of the setup is handled as Iaas (configured with Terraform) and the other half is done manually basically renders the whole Iaas approach useless, since the setup will still be manual and error prone and it can not be automated with CI/CD systems, since there are manual steps involved.
Above, you mentioned the API call PUT /api/fleet/package_policies/:id. Is this API documented somewhere?

One solution to this is to migrate this resource to the framework from sdk-v2, and use the privatestate.ProviderData to store a map of var/key to secretRef. Then when doing a read, iterate the vars and replace anything that has a stored ref.  Should work in theory, I haven't had the time to fully test out the bit I've been working on though.

I'm pretty sure I've got a working solution for this, its tentative on getting in #785 , otherwise I'm going to have to play whack-a-mole on some changes again. I'll open up a draft if you'd like to get some early eyes on it.

Hi @kpollich
Thanks for coming back to me and providing the additional context.

Above, you mentioned the API call PUT /api/fleet/package_policies/:id. Is this API documented somewhere?

The API is documented here: https://www.elastic.co/docs/api/doc/kibana/operation/operation-get-package-policies. These are sourced from an OpenAPI spec available here: https://github.com/elastic/kibana/blob/main/x-pack/plugins/fleet/common/openapi/bundled.yaml.

The way I understand the above mentioned API, this is the one, that is used by Kibana and therefore it does not provide a way to get the secrets back. This is the whole goal of the new design described in secrets.md. That being said, in the architecture diagram (in secrets.md) there also exists the Fleet Server, which actually does read the secrets and adds them to the agent policy, which is sent to the agent. So in order to be able to create some sort of workaround with scripting, we would need to be able to access a respective API on the Fleet Server to get the plain text secrets. I don't know, if such an API does even exist, but from my understanding, the Fleet API in Kibana is of no help.

In short, the team that develops Fleet has no knowledge or insight into Elastic's terraform provider. Describing it as an afterthought is perhaps a little harsh, but probably fair at least as it relates to the Fleet team itself, which is made up of primarily JavaScript engineers working in Kibana.

I apologize for having been harsh. This came out of frustration about the situation and basically being help- and clueless on how to move forward.

We'll continue to discuss our options for getting a change into the provider to work with the Fleet policy secrets, and in the meantime we are absolutely open to ideas or proofs of concept from the community like @daemitus has suggested above.

I looked into @daemitus solution today and I feel, this approach is promising. Basically the plain text secret as well as the ID of the secret ref are stored in the private data of the Terraform state, which allows to translate back an forth between the two representations as needed within Terraform. This sound good to me.
I have several questions about this approach:

@kpollich: My observation is, that with updates for Fleet integrations, often the policies are updated as well. Can you confirm, that in these cases, the ID of the secrets are maintained (stay untouched)? This is very important for the approach of @daemitus to work, since this approach maintains the link between the plain text secret and the ID of the secret reference on the client side (in Terraform) and therefore this ID must not be changed, if the value of the secret is not changed.
@kpollich: How does this behave, if a manual update of the fleet policy configuration (without changing the secrets) is performed in Kibana, are the ID of the secret values maintained in this case?
@daemitus: Since we now already have a Terraform configuration used to maintain the Fleet integrations and we therefore also already have a Terraform state (but without the link information in the private prorvider data in the Terraform state), I wonder about the update of the provider and the necessary "migration" of the information in the state. Have you already thought about that scenario as well?

@kpollich , both @tobio and @dimuon might be able to help review, I hope.

Thank you all (@daemitus, @tobio, @kpollich) for looking into this issue and providing a fix, even though, we have not yet been able to really test and use the new functionality, since we are affected by #820.


feature request: pipe generator output to chat

It would be very convenient for support to be able to run something like this:
~zod:dojo> talk|post [our %my-channel] +vats

or
~zod:dojo> talk|post [our %my-channel] +vat %base

and have the result be copied into a new post in a chat channel.  I think dojo syntax supports this sort of thing -- if not, we should think hard about how to make that work.
(Maybe I got the syntax wrong and it would be more like talk!post ..., I don't remember offhand)

Cosigned. I'll track down some estimates.


RadioManager: Cannot set radio state of Mobile Broadband device. DeniedBySystem

        public RadioModel(Radio radio, UIElement parent)
        {
            this.radio = radio;
            // Controlling the mobile broadband radio requires a restricted capability.
            this.isEnabled = (radio.Kind != RadioKind.MobileBroadband);
            this.parent = parent;
            this.radio.StateChanged += Radio_StateChanged;
        }

In this source code, restricted capabilities are required to control MobileBroadband.
    <Capabilities>
        <Capability Name="internetClient" />
        <DeviceCapability Name="radios" />
    </Capabilities>

This app already has "capabilities" for "radios". What does "restricted capability" means and what configuration do I need to get it?

we need control Radio Power for Mobile Broadband, but we are keep getting denied even with cellularDeviceControl capability, can you provide manifest example which should work?

This sounds like a platform issue, not a sample issue. You can follow the instructions on Windows developer support for support options. (Click "Forums and community".)


fix: upgrade cloud-init to v23.4.1

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

[x] The toolchain has been rebuilt successfully (or no changes were made to it)
[x] The toolchain/worker package manifests are up-to-date
[x] Any updated packages successfully build (or no packages were changed)
[x] Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
[x] Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
[x] All package sources are available
[x] cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
[x] LICENSE-MAP files are up-to-date (./SPECS/LICENSES-AND-NOTICES/data/licenses.json, ./SPECS/LICENSES-AND-NOTICES/LICENSES-MAP.md, ./SPECS/LICENSES-AND-NOTICES/LICENSE-EXCEPTIONS.PHOTON)
[x] All source files have up-to-date hashes in the *.signatures.json files
[x] sudo make go-tidy-all and sudo make go-test-coverage pass
[x] Documentation has been updated to match any changes to the build system
[x] Ready to merge

Summary

This change upgrades cloud-init to v23.4.1. This version contains fixes for an issue where some Azure Stack implementations do not support IMDS. Also this cloud-init version has the override data source patch integrated so we can drop the patch from our packaging.
Signed-off-by: Chris Co<EMAIL_ADDRESS>Does this affect the toolchain?

NO
Associated issues

Fixes #7064
Removes patch from #6279

Links to CVEs
Test Methodology

Pipeline build id: https://dev.azure.com/mariner-org/mariner/_build/results?buildId=471826&view=results

Marketplace smoke test passed and able to deploy on Azure VM
azureuser@cbl-mariner [ ~ ]$ rpm -qa | grep cloud-init
cloud-init-23.4.1-1.cm2.noarch
cloud-init-azure-kvp-23.4.1-1.cm2.noarch

Penguinator LISAv3 tests on Marketplace image with this cloud-init update also succeeded - https://penguinatorstarter.powerappsportals.com/mytests/myjobs/results/?id=0031226a-54a1-ee11-92bd-000d3a7e5c4a


(refactor) use snake_case consistently

Tests are passing locally
 make test
PATH=/Users/byq461/homebrew/opt/mithril/nginx/sbin:$PATH prove -I../test-nginx/lib -r t
t/sanity.t .. ok
All tests successful.
Files=1, Tests=78, 12 wallclock secs ( 0.03 usr  0.02 sys +  0.41 cusr  0.38 csys =  0.84 CPU)
Result: PASS

I have travis CI working on diff. branch will submit PR for that separately


Make VFE / WME / conditional records work even with ObjC interop and with reflection metadata, take #2

@swift-ci please test macOS platform


Add utf8

Before adding new features and new modules, please go to issues to submit the relevant feature description first.
Write good commit messages and use the same coding conventions as the rest of the project.
Please commit code to dev branch and we will merge into master branch in feature
Ensure your edited codes with four spaces instead of TAB.

增加新特性和新模块之前，请先到issues提交相关特性说明，经过讨论评估确认后，再进行相应的代码提交，避免做无用工作。
编写友好可读的提交信息，并使用与工程代码相同的代码规范，代码请用4个空格字符代替tab缩进。
请提交代码到dev分支，如果通过，我们会在特定时间合并到master分支上。
为了规范化提交日志的格式，commit消息，不要用中文，请用英文描述。

utf8 is maybe a bit too much generic for a package name

utf8 is maybe a bit too much generic for a package name

it's package name is branchless-utf8, not utf8


Added implementation of replace method for String type

The conditions should be like this
if (condition) {
    statement;
}

The styles are different, doing a
ant checkstyle

in home directory will help.

thanks

thanks..working on changes

@sipah00 have you considered the idea I mentioned earlier of using Pattern.quote and String.replaceFirst for implementing the replace method?
Please consider it, I'd like to know if it's really the case that we can't use it, because this code is quite complicated and it will be much better for everyone if this can be done in a simpler way.
You should also use Pattern.quote in the other methods -- anytime you want to use a regular string meant to be literal inside a regular expression you have to quote it, otherwise it will fail when user provides a regex metacharacter as an argument.
Example case that fails with the code in this PR:
>>> '[oi]'.lstrip('[')
Exception in thread "main" RuntimeError: Unclosed character class near index 4
^[[]+
    ^
	at org.python.types.Function.invoke(Function.java:412)
	at org.python.types.Method.invoke(Method.java:47)
	at python._tempfile.__init__.module$import(_tempfile.py:1)
	at python._tempfile.__init__.main(_tempfile.py)

Please be very thorough in your tests when you use regular expressions.

@eliasdorneles ,thank you very much..for review,I had considered replaceFirst method but i was facing problem in some case ..so i thought to do on my own way..but i will again try to implement replace method by your suggestion(replaceFirst)..

Can you please make this pull request only about the replace method.
Rstrip and Lstrip were implemented on https://github.com/pybee/voc/pull/439
An implementation of strip() should be equivalent to s.rstrip().lstrip(), but it's best done in a separate PR.
Regarding the idea of using replaceFirst, you can drop it -- I've realized it wouldn't work for the following case:
>>> 'abccabccabcc'.replace('abc', 'ab', 2)
'abcabcabcc'

An implementation w/ replaceFirst would render a result equivalent to:
>>> 'abccabccabcc'.replace('abc', 'ab', 1).replace('abc', 'ab', 1)
'ababccabcc'

It's a good idea to add a test for both above cases.


400 add tests for broadcasttransactionrequest

The tests work locally, but here I'm getting
expected [Function] to throw error including 'broadcast failed' but got 'crypto is not defined'

#400


AccessControlListNotSupported: The bucket does not allow ACLs

AWS disabled creating buckets with ACL, this should be updated to use Policies instead.

+1 for this - ran into this today. Workaround was to create a bucket manually and pass it with the following vars
  create_loki_storage                     = false
  loki_storage_s3_bucket_name   = "loki-storage-new-cluster-bucket"
  loki_storage_kms_key_arn          = "arn:aws:kms:us-west-2:123456789:key/some-key-id"


Purge Host/Container should clean up database

Got a couple issues with node cleanup in Rancher.
If for whatever reason I deactivate a host and purge it, the DB still holds references to it. This prevented me from adding a host on the same machine (same IP, same hostname) back to the cluster.
It seems to manifest itself as ping timeouts from agent to server.
Is it possible to clear purged machines from the DB?

Can you share the version you are running?  Just click the cow in the upper left of the UI.  When you deleted the host from the UI was it in a "reconnecting" state?

CATTLE_RANCHER_SERVER_IMAGE=v0.24.0
DEFAULT_CATTLE_API_UI_INDEX=//releases.rancher.com/ui/0.28.0
The host was indeed in reconnecting state. It got a bit messed up while experimenting with SSL termination, and the agent got a bit confuses as to where to find the server. Figured turning it on and off again would be a good idea. Didn't expect state to get in the way though :D

I should probably mention a few changes to the DB were done via the API :
change websocket protocol to wss instead of ws and change api.host setting so it doesn't include the protocol (http/https)
The agent was started with the protocol being implicit but even then it would register, then ping timeout and reregister over and over again. I have nginx in front of it rewriting http://{rancherURI} to https://{rancherURI} and I can see the register and wss connections succeeding fine.

Looks like my main issue (ping timeout) was related to Nginx after all. However i notices DB bloat (got like 10 hosts and the DB is already 600+ mb in size... ) which seems to come from event storage. Is this eventually cleaned up?

@sepiroth887 We have some other known issue with deleting hosts that weren't fixed until v0.26.0, but glad to hear you resolved your issue.
Honestly, our database can get massive quickly.  There's a couple tables that grow fast and we don't purge them.  We should and we should create an issue for that to make sure we get that done soon.
@deniseschannon Is there an existing issue for the DB size?

Created a new issue for database cleanup. #1525. Closing this issue in favor of that one.


use named port for pgbouncer

The services(s) call for targetPort: pgbouncer but the sts does not currently define that name. This leads to the endpoint not getting computed, and it causes issues with service loadbalancers.

Thanks for the PR, this is part of https://github.com/timescale/timescaledb-kubernetes/pull/218 now (including this commit).
We cannot merge this PR directly, as this commit is now a bugfix on top of 0.7.0, whereas master has diverged a lot already.


OTP Not Received During Signup

When trying to sign up, the OTP isn’t being sent, stopping users from completing the signup. Please check the OTP system to make sure it’s working.

Mailer pass updated and issue solved, refer to new .env file in teams for further reference.


PVNet2

Pull Request
Updates for work done under PVNet2
Description

Updates to use pvnet datapipe from ocf_datapipes
Write a datamodule which uses DataLoader2 and multiprocessing. Can either construct batches on the fly or load from premade batches
Some model architecture upgrades (mainly around activation function, batchnorm, skip connections)
Refactor the model so it is is composable and different model components can be plugged in and out

Include encoders module for model components which take 3D satellite/NWP data and encode it down to 1D vector
Include linear_networks module for model components which accept multiple 1D feature vectors from different sources and fuse them together into a prediction

Add variations on the overall model skeleton

multimodal - Original model skeleton. Encodes satellite and NWP and fuses them together with GSP history, solar coordinates, and ID embedding.
deep_supervision - Adds additional prediction heads to make predictions of GSP future based only on satellite and only on NWP
weather residual - Separates data sources so that GSP history, ID and solar coords are used to make initial prediction, and satellite and NWP are used to refine this prediction.
nwp_weighting - Completely different architecture where the prediction is a learned weighted mean of the dwsrf channel

Improved logging during model training

Checklist:

[ ] My code follows OCF's coding style guidelines
[x] I have performed a self-review of my own code
[x] I have made corresponding changes to the documentation
[x] I have added tests that prove my fix is effective or that my feature works
[x] I have checked my code and corrected any misspellings

Ive left a few comments, but in general looks really good

I would try to get this merged, and then work on production as a separate branch

are the tests running automatically? Can you fix the pre-commit.ci?

Could you also add a readme.md for the latest experiment you have done, doesnt have to be much text, but I find it really useful to have it near the code,
see example here


hyprland active workspace(one having windows open but not focused) and focused workspaces  different color

I dont know if its the right place to ask but how to have hyprland active but not focused workspace i.e one having windows open but not focused different color. i have windows opened in work space 5 and workspace 3 . i could not figure out how to change that workspace color. thank you

At some point, the CSS class was just #workspaces button. That stopped working a couple of months ago and I still don't know how to fix it.

There are a bunch of #workspaces button classes in https://github.com/Alexays/Waybar/wiki/Module:-Hyprland now that might help you here. Though granted it's a bit late. Please close this issue if this helps.

There are a bunch of #workspaces button classes in https://github.com/Alexays/Waybar/wiki/Module:-Hyprland now that might help you here. Though granted it's a bit late. Please close this issue if this helps.

Black white no colors ever never ever use Stocks online and GIF is a different knows me so boom bang. I’m more of a $brand that Apollo Kenya.


fix (build): Comment out Connector, to avoid (supposed) Dependency Cycle

This works around (by disabling) https://github.com/enola-dev/enola/issues/431,
but it does not fix https://github.com/salesforce/bazel-vscode-java/issues/114.

==> https://github.com/enola-dev/enola/pull/642


Updating Toolpad breaks the app in https://github.com/mui/mui-private/tree/master/tools-private

Steps to reproduce 🕹
Steps:

Go to https://github.com/mui/mui-private/tree/master/tools-private
Update Toolpad from 0.1.24 to 0.1.38
See how http://localhost:3000/_toolpad/app/pages/f303n5n is broken

The date displayed is wrong

Queries can't be added anymore, on a new page, it shows 500

The date object was introduced in 0.1.28 => Date objects aren't transferred from the server to the client. Looks like right now it can only transfer JSON.

The 500 was introduced in 0.1.34: Running with NODE_OPTIONS=--enable-source-maps to get proper stack traces gives me:
Error: Detected property constructor. This is a prototype pollution risk, please remove it from your object.
    at <anonymous> (/Users/janpotoms/Projects/mui-private/tools-private/node_modules/node_modules/superjson/src/plainer.ts:224:13)
    at <anonymous> (/Users/janpotoms/Projects/mui-private/tools-private/node_modules/node_modules/superjson/src/util.ts:45:52)
    at Array.forEach (<anonymous>)
    at forEach (/Users/janpotoms/Projects/mui-private/tools-private/node_modules/node_modules/superjson/src/util.ts:45:26)
    at walker (/Users/janpotoms/Projects/mui-private/tools-private/node_modules/node_modules/superjson/src/plainer.ts:218:3)
    at <anonymous> (/Users/janpotoms/Projects/mui-private/tools-private/node_modules/node_modules/superjson/src/plainer.ts:229:29)
    at <anonymous> (/Users/janpotoms/Projects/mui-private/tools-private/node_modules/node_modules/superjson/src/util.ts:45:52)
    at Array.forEach (<anonymous>)
    at forEach (/Users/janpotoms/Projects/mui-private/tools-private/node_modules/node_modules/superjson/src/util.ts:45:26)
    at walker (/Users/janpotoms/Projects/mui-private/tools-private/node_modules/node_modules/superjson/src/plainer.ts:218:3)

Looks to be around the same area, in serialization/deserialization.

Will investigate further on Monday

Ok, for the 500 we are having trouble transferring the typescript interface that describes the MySQL result. it contains a "constructor" property.
I don't immediately have a way to fix this besides reverting the update or writing our own smart serialization logic. I'm opening some issues in the hope thatw e can fix this without dropping a serialization library:

https://github.com/Rich-Harris/devalue/issues/71
https://github.com/blitz-js/superjson/issues/279

Fixes in:

https://github.com/mui/mui-toolpad/pull/2941
https://github.com/mui/mui-toolpad/pull/2942