Excess shard-aware port connection for shard

When running this code inside caching_session somewhere (and enable debug logging) this code:
#[tokio::test(flavor = "multi_thread")]
async fn test_full() {
    let session = create_caching_session().await;

    tokio::time::sleep(tokio::time::Duration::from_secs(10)).await;
}

produces endlessly the following logging:
ov 11 20:35:53.568 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Excess shard-aware port connection for shard 0; will retry with non-shard-aware port
Nov 11 20:35:53.568 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Excess shard-aware port connection for shard 0; will retry with non-shard-aware port
Nov 11 20:35:53.580 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Scheduling next refill in 50 ms
Nov 11 20:35:53.642 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Excess shard-aware port connection for shard 2; will retry with non-shard-aware port
Nov 11 20:35:53.643 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Excess shard-aware port connection for shard 0; will retry with non-shard-aware port
Nov 11 20:35:54.658 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Scheduling next refill in 50 ms
Nov 11 20:35:54.717 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Excess shard-aware port connection for shard 2; will retry with non-shard-aware port
Nov 11 20:35:54.718 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Excess shard-aware port connection for shard 0; will retry with non-shard-aware port
Nov 11 20:35:54.725 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Scheduling next refill in 50 ms
Nov 11 20:35:54.787 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Excess shard-aware port connection for shard 2; will retry with non-shard-aware port
Nov 11 20:35:54.788 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Excess shard-aware port connection for shard 0; will retry with non-shard-aware port
Nov 11 20:35:54.798 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Scheduling next refill in 50 ms
Nov 11 20:35:54.858 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Excess shard-aware port connection for shard 2; will retry with non-shard-aware port
Nov 11 20:35:54.860 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Excess shard-aware port connection for shard 0; will retry with non-shard-aware port
Nov 11 20:35:54.870 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Scheduling next refill in 50 ms
Nov 11 20:35:54.933 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Excess shard-aware port connection for shard 2; will retry with non-shard-aware port
Nov 11 20:35:54.934 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Excess shard-aware port connection for shard 0; will retry with non-shard-aware port
Nov 11 20:35:54.944 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Scheduling next refill in 50 ms
Nov 11 20:35:55.005 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Excess shard-aware port connection for shard 0; will retry with non-shard-aware port
Nov 11 20:35:55.005 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Excess shard-aware port connection for shard 2; will retry with non-shard-aware port
Nov 11 20:35:55.011 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Scheduling next refill in 50 ms
Nov 11 20:35:55.073 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Excess shard-aware port connection for shard 2; will retry with non-shard-aware port
Nov 11 20:35:55.073 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Excess shard-aware port connection for shard 0; will retry with non-shard-aware port
Nov 11 20:35:55.081 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Scheduling next refill in 50 ms
Nov 11 20:35:55.143 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Excess shard-aware port connection for shard 2; will retry with non-shard-aware port
Nov 11 20:35:55.144 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Excess shard-aware port connection for shard 0; will retry with non-shard-aware port
Nov 11 20:35:55.154 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Scheduling next refill in 50 ms
Nov 11 20:35:55.215 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Excess shard-aware port connection for shard 0; will retry with non-shard-aware port
Nov 11 20:35:55.215 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Excess shard-aware port connection for shard 2; will retry with non-shard-aware port
Nov 11 20:35:55.222 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Scheduling next refill in 50 ms

I am running a single node Scylla in Docker, nothing fancy.

Its even worse with docker-compose when running multiple nodes. It starts with this logging:
Nov 11 16:22:53.783  INFO common::database: Trying to connect to node
Nov 11 16:22:53.785 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Started asynchronous pool worker
Nov 11 16:22:53.785 DEBUG scylla::transport::cluster: Requesting topology refresh
Nov 11 16:22:53.797 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] New sharder: Some(Sharder { nr_shards: 4, msb_ignore: 12 }), clearing all connections
Nov 11 16:22:53.797 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Updating shard aware port: Some(19042)
Nov 11 16:22:53.797 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Pool is full, clearing 0 excess connections
Nov 11 16:22:53.806 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Started asynchronous pool worker
Nov 11 16:22:53.807 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Started asynchronous pool worker
Nov 11 16:22:53.807 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Started asynchronous pool worker
Nov 11 16:22:53.816 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] New sharder: Some(Sharder { nr_shards: 4, msb_ignore: 12 }), clearing all connections
Nov 11 16:22:53.816 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Updating shard aware port: Some(19042)
Nov 11 16:22:53.816 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Scheduling next refill in 50 ms
Nov 11 16:22:53.819 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Failed to open connection to the non-shard-aware port: IoError(Os { code: 61, kind: ConnectionRefused, message: "Connection refused" })
Nov 11 16:22:53.819 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Scheduling next refill in 100 ms
Nov 11 16:22:53.880 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Excess shard-aware port connection for shard 2; will retry with non-shard-aware port
Nov 11 16:22:53.880 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Excess shard-aware port connection for shard 2; will retry with non-shard-aware port
Nov 11 16:22:53.892 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Scheduling next refill in 50 ms
Nov 11 16:22:53.953 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Excess shard-aware port connection for shard 0; will retry with non-shard-aware port
Nov 11 16:22:53.957 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Excess shard-aware port connection for shard 2; will retry with non-shard-aware port
Nov 11 16:22:53.965 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Scheduling next refill in 50 ms
Nov 11 16:22:54.028 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Excess shard-aware port connection for shard 0; will retry with non-shard-aware port
Nov 11 16:22:54.033 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Excess shard-aware port connection for shard 2; will retry with non-shard-aware port
Nov 11 16:22:54.044 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Scheduling next refill in 50 ms
Nov 11 16:22:54.105 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Excess shard-aware port connection for shard 0; will retry with non-shard-aware port
Nov 11 16:22:54.109 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Excess shard-aware port connection for shard 2; will retry with non-shard-aware port
Nov 11 16:22:54.117 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Scheduling next refill in 50 ms
Nov 11 16:22:54.180 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Excess shard-aware port connection for shard 0; will retry with non-shard-aware port
Nov 11 16:22:54.182 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Excess shard-aware port connection for shard 2; will retry with non-shard-aware port
Nov 11 16:22:54.190 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Scheduling next refill in 50 ms
Nov 11 16:22:54.252 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Excess shard-aware port connection for shard 0; will retry with non-shard-aware port
Nov 11 16:22:54.253 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Excess shard-aware port connection for shard 2; will retry with non-shard-aware port
Nov 11 16:22:54.264 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Scheduling next refill in 50 ms
Nov 11 16:22:54.324 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Excess shard-aware port connection for shard 0; will retry with non-shard-aware port
Nov 11 16:22:54.324 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Excess shard-aware port connection for shard 2; will retry with non-shard-aware port
Nov 11 16:22:54.333 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Scheduling next refill in 50 ms
Nov 11 16:22:54.394 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Excess shard-aware port connection for shard 2; will retry with non-shard-aware port
Nov 11 16:22:54.402 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Excess shard-aware port connection for shard 0; will retry with non-shard-aware port
Nov 11 16:22:54.410 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Scheduling next refill in 50 ms
Nov 11 16:22:54.469 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Excess shard-aware port connection for shard 0; will retry with non-shard-aware port
Nov 11 16:22:54.471 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Excess shard-aware port connection for shard 2; will retry with non-shard-aware port
Nov 11 16:22:54.487 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Scheduling next refill in 50 ms
Nov 11 16:22:54.548 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Excess shard-aware port connection for shard 0; will retry with non-shard-aware port
Nov 11 16:22:54.550 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Excess shard-aware port connection for shard 2; will retry with non-shard-aware port
Nov 11 16:22:54.558 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Scheduling next refill in 50 ms
Nov 11 16:22:54.619 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Excess shard-aware port connection for shard 0; will retry with non-shard-aware port
Nov 11 16:22:54.623 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Excess shard-aware port connection for shard 2; will retry with non-shard-aware port
Nov 11 16:22:54.631 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Scheduling next refill in 50 ms
Nov 11 16:22:54.694 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Excess shard-aware port connection for shard 0; will retry with non-shard-aware port
Nov 11 16:22:54.697 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Excess shard-aware port connection for shard 2; will retry with non-shard-aware port
Nov 11 16:22:54.707 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Scheduling next refill in 50 ms
Nov 11 16:22:54.768 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Excess shard-aware port connection for shard 0; will retry with non-shard-aware port
Nov 11 16:22:54.773 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Excess shard-aware port connection for shard 2; will retry with non-shard-aware port
Nov 11 16:22:54.784 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Scheduling next refill in 50 ms
Nov 11 16:22:54.849 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Excess shard-aware port connection for shard 0; will retry with non-shard-aware port
Nov 11 16:22:54.854 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Excess shard-aware port connection for shard 2; will retry with non-shard-aware port
Nov 11 16:22:54.863 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Scheduling next refill in 50 ms
Nov 11 16:22:54.885 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Failed to open connection to the non-shard-aware port: IoError(Os { code: 61, kind: ConnectionRefused, message: "Connection refused" })
Nov 11 16:22:54.885 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Scheduling next refill in 100 ms
Nov 11 16:22:54.885 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Requested keyspace change: keyspacee
Nov 11 16:22:54.885 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Requested keyspace change: keyspacee
Nov 11 16:22:54.885 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Requested keyspace change: keyspacee
Nov 11 16:22:54.885 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Successfully changed current keyspace
Nov 11 16:22:54.885 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Successfully changed current keyspace
Nov 11 16:22:54.887 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Successfully changed current keyspace

Than after a clutter of 'Excess shard-aware port connection for shard' logs, I get this error which takes my test down
Nov 11 16:22:57.377 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Excess shard-aware port connection for shard 0; will retry with non-shard-aware port
Nov 11 16:22:57.383 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Excess shard-aware port connection for shard 2; will retry with non-shard-aware port
Nov 11 16:22:57.397 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Scheduling next refill in 50 ms
Nov 11 16:22:57.421 DEBUG rustls::session: Sending warning alert CloseNotify

called `Result::unwrap()` on an `Err` value: IoError(Custom { kind: Other, error: "No connections in the pool" })
thread 'mytest' panicked at 'called `Result::unwrap()` on an `Err` value: IoError(Custom { kind: Other, error: "No connections in the pool" })', /Users/me/CLionProjects/migrationtest/test.rs:80:45

@Jasperav could you try re-running your test with logging level set to trace for the scylla crate and paste the results?
In the meantime, my wild guess would be that you are using the 19042 port (the shard-aware port) to connect and switching to 9042 (non-shard-aware port) will help. Could you try that?
Generally, with the new connection pool implementation, you should use the non-shard-aware port when connecting to the cluster. The driver detects the shard-aware port automatically and tries to use it if possible. However, if you are using Docker either on Windows or MacOS, then the driver might not be able to connect to some shards using the shard-aware port because of the specifics of Docker's networking implementation (see my comment here). Normally, in this situation the driver will fall back to the non-shard-aware port which doesn't suffer from this issue, however it's not able to detect that port automatically and assumes that the port you used to connect is the non-shard-aware port. If you pass the shard-aware port when connecting, the connection pool will always use the shard-aware port for connections and will get stuck in a retry loop because it will never manage to reach some of the shards.

@piodul Alright that is too bad of Docker. Are there reasons to explicitly give the shard port to the driver? Because the driver automatically checks if the shard port is available.
This is the trace logging. Switching to the non-shard port works.
Nov 12 06:30:33.606 DEBUG scylla::transport::cluster: Requesting topology refresh
Nov 12 06:30:33.606 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Started asynchronous pool worker
Nov 12 06:30:33.609 TRACE scylla::transport::connection_pool: [<IP_ADDRESS>] Will open the first connection to the node
Nov 12 06:30:33.609 TRACE mio::poll: registering event source with poller: token=Token(0), interests=READABLE | WRITABLE
Nov 12 06:30:33.618 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] New sharder: Some(Sharder { nr_shards: 4, msb_ignore: 12 }), clearing all connections
Nov 12 06:30:33.618 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Updating shard aware port: Some(19042)
Nov 12 06:30:33.618 TRACE scylla::transport::connection_pool: [<IP_ADDRESS>] Adding connection 0x7fd80bb05090 to shard 2 pool, now there are 1 for the shard, total 1
Nov 12 06:30:33.618 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Pool is full, clearing 0 excess connections
Nov 12 06:30:33.629 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Started asynchronous pool worker
Nov 12 06:30:33.630 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Started asynchronous pool worker
Nov 12 06:30:33.630 TRACE scylla::transport::connection_pool: [<IP_ADDRESS>] Will open the first connection to the node
Nov 12 06:30:33.631 TRACE mio::poll: registering event source with poller: token=Token(1), interests=READABLE | WRITABLE
Nov 12 06:30:33.631 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Started asynchronous pool worker
Nov 12 06:30:33.632 TRACE scylla::transport::connection_pool: [<IP_ADDRESS>] Will open the first connection to the node
Nov 12 06:30:33.632 TRACE mio::poll: registering event source with poller: token=Token(2), interests=READABLE | WRITABLE
Nov 12 06:30:33.632 TRACE scylla::transport::connection_pool: [<IP_ADDRESS>] Will open the first connection to the node
Nov 12 06:30:33.632 TRACE mio::poll: registering event source with poller: token=Token(3), interests=READABLE | WRITABLE
Nov 12 06:30:33.643 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] New sharder: Some(Sharder { nr_shards: 4, msb_ignore: 12 }), clearing all connections
Nov 12 06:30:33.643 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Updating shard aware port: Some(19042)
Nov 12 06:30:33.643 TRACE scylla::transport::connection_pool: [<IP_ADDRESS>] Adding connection 0x7fd80a50b760 to shard 2 pool, now there are 1 for the shard, total 1
Nov 12 06:30:33.643 TRACE mio::poll: deregistering event source from poller
Nov 12 06:30:33.643 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Scheduling next refill in 50 ms
Nov 12 06:30:33.643 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Failed to open connection to the non-shard-aware port: IoError(Os { code: 61, kind: ConnectionRefused, message: "Connection refused" })
Nov 12 06:30:33.643 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Scheduling next refill in 100 ms
Nov 12 06:30:33.699 TRACE scylla::transport::connection_pool: [<IP_ADDRESS>] Will open 1 connections to shard 0
Nov 12 06:30:33.699 TRACE scylla::transport::connection_pool: [<IP_ADDRESS>] Will open 1 connections to shard 1
Nov 12 06:30:33.699 TRACE scylla::transport::connection_pool: [<IP_ADDRESS>] Will open 1 connections to shard 3
Nov 12 06:30:33.700 TRACE mio::poll: registering event source with poller: token=Token(16777217), interests=READABLE | WRITABLE
Nov 12 06:30:33.700 TRACE mio::poll: registering event source with poller: token=Token(4), interests=READABLE | WRITABLE
Nov 12 06:30:33.701 TRACE mio::poll: registering event source with poller: token=Token(5), interests=READABLE | WRITABLE
Nov 12 06:30:33.709 TRACE scylla::transport::connection_pool: [<IP_ADDRESS>] Adding connection 0x7fd80ba09670 to shard 0 pool, now there are 1 for the shard, total 2
Nov 12 06:30:33.711 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Excess shard-aware port connection for shard 2; will retry with non-shard-aware port
Nov 12 06:30:33.711 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Excess shard-aware port connection for shard 2; will retry with non-shard-aware port
Nov 12 06:30:33.711 TRACE mio::poll: deregistering event source from poller
Nov 12 06:30:33.711 TRACE mio::poll: registering event source with poller: token=Token(6), interests=READABLE | WRITABLE
Nov 12 06:30:33.711 TRACE mio::poll: registering event source with poller: token=Token(16777220), interests=READABLE | WRITABLE
Nov 12 06:30:33.712 TRACE mio::poll: deregistering event source from poller
Nov 12 06:30:33.718 TRACE scylla::transport::connection_pool: [<IP_ADDRESS>] Storing excess connection 0x7fd80ba09cf0 for shard 0
Nov 12 06:30:33.721 TRACE scylla::transport::connection_pool: [<IP_ADDRESS>] Storing excess connection 0x7fd80b806b70 for shard 2
Nov 12 06:30:33.721 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Scheduling next refill in 50 ms
Nov 12 06:30:33.745 TRACE scylla::transport::connection_pool: [<IP_ADDRESS>] Will open the first connection to the node
Nov 12 06:30:33.745 TRACE mio::poll: registering event source with poller: token=Token(33554433), interests=READABLE | WRITABLE
Nov 12 06:30:33.776 TRACE scylla::transport::connection_pool: [<IP_ADDRESS>] Will open 1 connections to shard 1
Nov 12 06:30:33.776 TRACE scylla::transport::connection_pool: [<IP_ADDRESS>] Will open 1 connections to shard 3
Nov 12 06:30:33.776 TRACE mio::poll: registering event source with poller: token=Token(7), interests=READABLE | WRITABLE
Nov 12 06:30:33.776 TRACE mio::poll: registering event source with poller: token=Token(8), interests=READABLE | WRITABLE
Nov 12 06:30:33.783 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Excess shard-aware port connection for shard 0; will retry with non-shard-aware port
Nov 12 06:30:33.784 TRACE mio::poll: registering event source with poller: token=Token(9), interests=READABLE | WRITABLE
Nov 12 06:30:33.784 TRACE mio::poll: deregistering event source from poller
Nov 12 06:30:33.789 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Excess shard-aware port connection for shard 2; will retry with non-shard-aware port
Nov 12 06:30:33.789 TRACE mio::poll: registering event source with poller: token=Token(16777223), interests=READABLE | WRITABLE

@piodul Alright that is too bad of Docker. Are there reasons to explicitly give the shard port to the driver? Because the driver automatically checks if the shard port is available.

@Jasperav At the moment, it's better to give the non-shard-aware port to the driver, let it detect the shard-aware port and let it choose which port to use. In older versions the driver behaved better if you passed the shard-aware port, but that's no longer the case.


The correct approach to enable RandomAdminPassword is very confusing

AdminPassword: "This property must be set, but it is ignored if the RandomAdminPassword property is set to e". RandomAdminPassword is a boolean. I'm guessing that it needs to be true and that AdminPassword cannot be null(?)

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: ab30ff5a-8bc6-f4a0-f92a-0a1d805ca4e8
Version Independent ID: f366d2cb-7f1a-0ecd-2bdb-c8eada68934c
Content: SMS_TaskSequence_ApplyWindowsSettingsAction Class - Configuration Manager
Content Source: sccm/develop/reference/osd/sms_tasksequence_applywindowssettingsaction-server-wmi-class.md
Product: configuration-manager
GitHub Login: @aczechowski
Microsoft Alias: aaroncz

Thanks @oyvsi for catching this. Yes, it should be true instead of e.

Closing this issue as it will be fixed later today with the linked pull request.


Implement PEP 518 support

https://www.python.org/dev/peps/pep-0518/
pyproject.toml, if it exists, should be used like setup_requires.
See also https://github.com/pypa/pip/issues/3691

This seems to be supported in the forthcoming pip 10.0.
What is there to support on setuptools side? python setup.py install?
What is the plan in general - easy_install seems more or less deprecated, and pip install . (or pip install -e .) has pretty much replaced python setup.py install (or python setup.py develop). Pip seems to be the blessed tool these days so is there any benefit in supporting two different ways for the same thing?
Even pyproject.toml seems to be slowly emerging and (while very limited at the moment) might even replace setup.py and setuptools altogether?

@jaraco @benoit-pierre Is the plan here to have all PEP 518 go through pip? If so, I think we can close this as it's fixed in pip.
For the most part, PEP 518 support is difficult or impossible to achieve using the current approach, but I have created #1515 proposing a possible way forward that doesn't completely drop support for custom setup commands.


Spago config for PureScript v0.14.1

Thanks for this library! I hope you're planning to re-add it to package sets? https://github.com/purescript/package-sets/blob/master/src/groups/jacereda.dhall

Thanks, LGTM, @athanclark ?


Waybar becomes unresponsive after some time

As title says, it just stops responding to clicks and also stops updating displayed information. It happens randomly, but always after some time of running, not right away.

It'll be complicated to debug :/

All I can say, it began after updating to 0.6.6.

I've just caught the moment it becomes unresponsive. I stopped redrawing bus still responded to clicks for several seconds and then hanged completely.

Now after I updated sway to 1.1.1, waybar never becomes unresponsive, but just stops redrawing itself.

Never got the pb, are there any common points when it becomes unresponsive?

I haven't noticed any. Just after some time of normal workflow it stops updating its appearance. I.e. when I switch workspaces, it keeps highlighting the old one, clock stops, window title does not change, etc.
The only thing I noticed, it's always works normal right after I unlock screen after PC stayed Idle for some time if it worked normal before screen was locked. So it doesn't hang while idle, but hangs at some point when I'm working.

Do you have some custom modules?

Yes, I do. Two of them actually.

Experiencing the same problem, but I'm not using any custom modules.

This happens for me as well, but only with custom modules running.
The modules in question are two instances of https://git.revreso.de/gigadoc2/waybar-scripts/blob/master/battery.py in case this is relevant.

Correction: it did just happen without custom modules. It just took longer.

Can you test with test branch :)

So anyone tested with the test branch? :)

I just started running it :sweat_smile:
So far I can't see the bug, but I've only been running the test branch for 2 hours or so, the bug sometimes took longer.

For me the bug did not happen since I updated to 0.6.8. But it does not matter, because that's totally normal for this bug. Sometimes I do not see it for several days, sometime it happens several times a day.

Will close this issue if no one has the bug again when 0.7.0 will be released :)

Now, after this time I can say: this really does not happen anymore. If nobody has objections, I think it's safe to close the issue.

Yeah, seems fine now.

I've been running the test branch until now, and I did not encounter the bug anymore. Will now change to 0.6.8 and see what happens there.


feat: allow having custom fields to format

not completely done yet
I need to add annotations and rewrite parts of the docs
but the code should be done like this
and it works
I used it for months now

Sorry. I don't want to add a custom fields. Because I don't know real use-case.
I think left/right padding can be merged.

you need custom fields if you want to have more than three different highlight groups
and what would be a reason to not add them?
they bring and advantage and no problems with them

For the people who see this and don't realize what this does:
Before you had the kind, abbr and menu fields.
You could define the highlights and text of those.
So you only could have three different types of style in the completion menu.
if you e.g. wanted kind icon, kind name text and source at least two had to have the same color (next to each other).
This is also useful when you don't want to have more than three things but e.g. a separator which needs to have the foreground color highlighted like the background color of the field next to it.
If you wanted to do this before you could only have two fields because you "lost" one highlight to the separator.
Things like this are fixed with this pr.
Now you can have as many different fields as you want and therefore you aren't limited when customizing the menu.

I do not, at the moment, see a use case for myself. With that said - @hrsh7th I believe reason you ditched native pum and implemented custom one was lack of configurability and overall limitations of native solution. Based on @max397574's above explanation I believe that PR follows up in the same spirit.
(in terms of configurability, I would love to be able to right align items on the right hand side of my menu. :)
      label                              [LSP] Variable
    廓 local                              [LSP] Keyword

would become
      label                              [LSP] Variable
    廓 local                               [LSP] Keyword

And since all my abbrs are three letters long I would put them at the end of the line.

Apparently, many people agree with this request, as expressed in the down vote.
First, who adds custom fields?
Does the source define it? If so, should it be a clear specification instead of custom fields?
We don't want a world that returns arbitrary values for each source.
Or is it intended for the user to display free values via formatting.format ?

the user can put any fields he wants into formatting.format
he'd just need to define the field text and the field hl (both have default values)
he's completely free to use them
they can be anything from additional icons to text etc
those things can come from sources but aren't strictly defined by them

I'm away for the next few days but I can try to type out some documentation for this so my idea would be clear.
Or how do you think this should be handled?

No specific use cases have emerged at this stage.
"Users are free to add custom fields."
This is a functional description, not a purpose or use case.
I think kind/menu is enough.
Because it has the advantage of being compatible with vim's completion items. (That is, it can handle returning items from any source, and can be properly typed and documented.)
I don't see why you would need an extra field to throw this compatibility away.
google translated


(bug) The 'task' event has not been registered in the plugins file. You must register it before using cy.task()

Describe the bug
Hi @meinaart,
I have the following error when I'm trying to use cypress-plugin-snapshots:
cy.task('cypress-plugin-snapshot:getFile') failed with the following error:

The 'task' event has not been registered in the plugins file. You must register it before using cy.task()

Fix this in your plugins file here:
false

https://on.cypress.io/api/task

Because this error occurred during a before all hook we are skipping all of the remaining tests.

To Reproduce
Steps to reproduce the behavior:

Install cypress-plugin-snapshots
Add to one of my test (show.spec.js):

  it('Compare screenshots', () => {
    cy.get(`[data-cy="screenshot-offers"]`)
      .toMatchImageSnapshot()
  })

Expected behavior
I'm expecting to not have this error I guess
Screenshots

Desktop (please complete the following information):

OS: macOS Mojave 10.14.6 (18G95)
Cypress Version 4.7.0

Additional context
Thank you for your support!

@CyrilKrylatov Don't know if you've figured this out already, but i had this issue and looks like the reason was that i had 2 module.exports statements in the plugins/index.js file. So i moved everything to one module.exports statement.
This was before:
const { initPlugin } = require('cypress-plugin-snapshots/plugin');

module.exports = (on, config) => {
  initPlugin(on, config);
  return config;
};

module.exports = (on, config) => {
    on('before:browser:launch', (browser = {}, launchOptions) => {
      if (browser.family === 'chromium' && browser.name !== 'electron') {
        launchOptions.args.push('--disable-dev-shm-usage');
      };
      return launchOptions
    });
  };

And this is after:
const { initPlugin } = require('cypress-plugin-snapshots/plugin');

module.exports = (on, config) => {
    on('before:browser:launch', (browser = {}, launchOptions) => {
      if (browser.family === 'chromium' && browser.name !== 'electron') {
        launchOptions.args.push('--disable-dev-shm-usage');
      };
      return launchOptions
    });

    initPlugin(on, config);
    return config;
  };

After doing that, the issue disappeared.

@adesko  - Thank you so much, that also worked for me!


TD-1325: My Learning record disappearing after session completed

JIRA link
https://hee-tis.atlassian.net/browse/TD-1325
Description
https://hee-tis.atlassian.net/browse/TD-1325
Screenshots
Before code changes:

Disappeared after complete

Appeared again after window close

After code fix:

Developer checks
(Leave tasks unticked if they haven't been appropriate for your ticket.)
I have:

[x] Run the formatter and made sure there are no IDE errors
[ ] Written appropriate unit tests for the changes, including:

accessibility tests for new views
tests for new controller methods
tests for new or modified API endpoints

[x] Manually tested my work with and without JavaScript
[ ] Tested any Views or partials created or changed with Wave Chrome plugin and addressed any valid accessibility issues
[ ] Updated/added documentation in Confluence and/or GitHub Readme. List of documentation links added/changed:

doc_1_here

[x] Updated my Jira ticket with information about other parts of the system that were touched as part of the MR and have to be sanity tested to ensure nothing is broken
[ ] Scanned over my pull request in GitHub and addressed any warnings from the GitHub Build and Test checks.

@sarathlal-sarangadharan   this ticket is part of Pheonix release. Can you merge changes to LHPheonix Branch?

@sarathlal-sarangadharan this ticket is part of Pheonix release. Can you merge changes to LHPheonix Branch?

Changed the target branch to LHPhoenix. There is 2 file changes.


Screen brightness

Great library, thanks for taking the time to create this.
Is there any info on how to adjust the screen brightness?
Thanks

bump


Can't run scripts in MAX 2017

Type error: CreateDialogue requires RolloutClass, got: undefined
I've tried each of the revisions from 1.3 all the way to 1.6,  trying to select any of the options in the Tools Menu brings this up

Got the same issue in 3ds Max 2021.
Anyway to fix this?


Added check for hourly permissions and version >= 37 before querying …

https://gus.my.salesforce.com/apex/adm_userstorydetail?id=a07B000000222TQIAY&sfdc.override=1
We now have hourly event log files and daily event log files. We now check for hourly permissions at login. When users query event log files, we display the hourly event log files along with additional headers (sequence and interval) if they have hourly turned on. If not, we display only daily event log files.

The build is failing at "go fmt" @sangitamohan can you run
go fmt

on your code and add that change to the pull request?

@dcarroll
I've made the fix. Please review.
Thanks
Sangita

Waiting on Travis CI now, thanks for the PR!
On Mon, Nov 28, 2016 at 4:09 PM, sangitamohan<EMAIL_ADDRESS>wrote:

@dcarroll https://github.com/dcarroll
I've made the fix. Please review.
Thanks
Sangita
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/heroku/force/pull/351#issuecomment-263435943, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAHGHvZVWAOValkw-n2E5AwdFxlJn2sgks5rC206gaJpZM4K68UW
.

--
Thanks,
Dave

Publishing new release now. This will cause new binaries to be generated and available for download from [Developer Site](https://developer.salesforce.com/tools/forcecli}.

@dcarroll
Thank you so much.


⚠ Bofrost.at has degraded performance

In d6d869a, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1533 ms

Resolved: Bofrost.at performance has improved in 758ee80.


Legal Status

none, 501c3, 501c6, ?

I have reached out to Jonathan re: DGRI as a sponsoring 501c3

Going the way of 501c3. Have submitted non profit incorporation paperwork with the State of Michigan.

Have submitted Form 1023EZ for 501c3


fix(BabelParser): Support parsing modules

I would suggest merging this as a bugfix because we thought this worked but we never tested it.


"text/template" template.Must(template.New("test").Funcs(newTempFuncs).ParseFiles("1.temp")) not work

What version of Go are you using (go version)?

$ go version
1.12.2 darwin/adm64

Does this issue reproduce with the latest release?
What operating system and processor architecture are you using (go env)?
go env Output
$ go env

What did you do?
template.Must(template.New("test").Funcs(newTempFuncs).ParseFiles("test.temp"))
will do nothing, seems that parsefiles does not suport funcs;
template.Must(template.New("test").Funcs(newTempFuncs).Parse(templatetest))
the templatetest has the some content as test.temp and works as expect...
if i change template.Must(template.New("test").Funcs(newTempFuncs).ParseFiles("test.temp")); to template.Must(template.ParseFiles("test.temp")) and  remove funcs in tempfile, everythings seems fine...so I am confused...

What did you expect to see?
template.Must(template.New("test").Funcs(newTempFuncs).ParseFiles("test.temp"))
should render template
What did you see instead?
do nothing until i change to template.Must(template.ParseFiles("test.temp")) and work as expect

package main

import (
	"text/template"
	"os"
	"strings"
)

func main() {

	tmpl1 := template.Must(template.New("test").Funcs(template.FuncMap{"trim": strings.TrimSpace,}).ParseFiles("/Users/fengshuo/go/src/cliTest/go-template/foo.tmpl"))

	tmpl1.Execute(os.Stdout, " string contains spaces both ")
}

foo.tmpl
{{.}}

here i write a simple one, you could try it ...

.......
tmpl1 := template.Must(template.New("foo.tmpl").Funcs(template.FuncMap{"trim": strings.TrimSpace,}).ParseFiles("foo.tmpl")) worked.... new must use filename...


Ni line in 6767 (the helioseismology GONG/MDI line)

Hi
I get the message below when I try to compute the broadening coefficients for the Ni line in 6767 that is used in GONG/MDI for helioseismology and magnetic field measurements.
_!!! Outside range of tables! (p-d)
Unable to get xsection for line at  6767.772A
for above reason.
n* are   1.53 ->   1.85
Output written to file!_
Input line is
$$$ Ni I GONG line
Ni 1    6767.772        14728.840       61619.77        29500.674      61619.77          2  1  0    1
Any help is much appreciated.
Valentin

Hi Valentin
This just means the lines lie outside the bounds of the tabulated data where interpolation can be done.  I'll look next week what can be done - perhaps a special calculation.  There is usually a way to get an estimate at least.
Paul

Hi Valentin
In this case the lower state has n* = 1.53, and this is too low for the use of Coulomb wavefunctions for d states (n*-l must be >0 for hydrogenic Coulomb wavefunctions to be defined).  There are two possible approaches here which don't involve me writing new code, and probably give good  estimates (i.e. similar uncertainties to any other line calculated with ABO theory):

Ignore the lower state.  A specific calculation gives sigma = 322, alpha = 0.286.
Include an estimate of the effect of the lower state by regarding it as an s-state.  You could do this by just switching "l=2" to "l=0" for the lower state in your input.  I did a specific calculation (i.e. I didn't use abo-cross, and thus there is no interpolation involved) and get sigma = 301, alpha = 0.244.

My expectation is that 2 would be better than 1, since it gives an estimate of the interference between the two states (that's why there is a slight decrease).  But 1 gives you an idea of the uncertainty.
Cheers, Paul


set MetaspaceSize

Codecov Report
Base: 98.63% // Head: 98.63% // No change to project coverage :thumbsup:

Coverage data is based on head (2d9210f) compared to base (c7a8520).
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #64   +/-   ##
=======================================
  Coverage   98.63%   98.63%
=======================================
  Files          16       16
  Lines         292      292
  Branches       23       23
=======================================
  Hits          288      288
  Misses          4        4

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


[AIRFLOW-149] Task Dependency Engine + Blocked Task Instance Explainer

Please accept this PR that addresses the following issues:

https://issues.apache.org/jira/browse/AIRFLOW-149

Here is the original PR with Max's LGTM: https://github.com/aoen/incubator-airflow/pull/1
Since then I have made some fixes but this PR is essentially the same. It could definitely use more
eyes as there are likely still issues.
Goals

Simplify, consolidate, and make consistent the logic of whether or not a task should be run
Provide a view/better logging that gives insight into why a task instance is not currently running
(no more viewing the scheduler logs to find out why a task instance isn't running for the majority
of cases):

Notable Functional Changes

Webserver view + task_failing_deps CLI command to explain why a given task instance isn't being
run by the scheduler
Running a backfill in the command line and running a task in the UI will now display detailed
error messages based on which dependencies were not met for a task instead of appearing to succeed
but actually failing silently
Maximum task concurrency and pools are not respected by backfills
Backfill now has the equivalent of the old force flag to run even for successful tasks
This will break one use case:
Using pools to restrict some resource on airflow executors themselves (rather than an externa
l resource like a DB), e.g. some task uses 60% of cpu on a worker so we restrict that task's pool
size to 1 to prevent two of the tasks from running on the same host. When backfilling a task of
this type, now the backfill will wait on the pool to have slots open up before running the task
even though we don't need to do this if backfilling on a different host outside of the pool. I
think breaking this use case is OK since the use case is a hack due to not having a proper
resource isolation solution (e.g. mesos should be used in this case instead).
To make things less confusing for users, there is now a "ignore all dependencies" option for
running tasks, "ignore dependencies" has been renamed to "ignore task dependencies", and "force"
has been renamed to "ignore task instance state". The new "Ignore all dependencies" flag will
ignore the following:

task instance's pool being full
execution date for a task instance being in the future
a task instance being in the retry waiting period
the task instance's task ending prior to the task instance's execution date
task instance is already queued
task instance has already completed
task instance is in the shutdown state
WILL NOT IGNORE task instance is already running

SLA miss emails will now include all tasks that did not finish for a particular DAG run, even if
the tasks didn't run because depends_on_past was not met for a task
Tasks with pools won't get queued automatically the first time they reach a worker; if
they are ready to run they will be run immediately
Running a task via the UI or via the command line (backfill/run commands) will now log why a task
could not get run if one if it's dependencies isn't met. For tasks kicked off via the web UI this
means that tasks don't silently fail to get queued despite a successful message in the UI.
Queuing a task into a pool that doesn't exist will now get stopped in the scheduler instead of a
worker

TODO

Fix test that is failing for mysql/postgres (not sure that it is related)

Follow Up Items

Update the docs to reference the new explainer views/CLI command

Testing Done

New unit tests
Running in airbnb production for 2 days (will have been more by the time this is merged)
Make sure blocked deps are all shown in UI, including dagrun doesn't exist dep
Logs look good
Make sure ui throws error when ti_deps aren't met when you try to schedule a task
No delay/load issues
Test celery worker starting a task via the UI with various flags (on Bronze), and make sure the
task actually completed by checking start_date changed
Run a task that has already succeeded in the UI and make sure it's state gets changed
(including in the UI)
Make sure can backfill overtop of failed tasks
Make sure tasks still get queued when e.g. concurrency is reached or pool is reached (can test one
don't have to test both)
Make sure backfill flags still work (because they aren't passed to tasks anymore right?)
-a, --include_adhoc Include dags with the adhoc parameter.
-i, --ignore_dependencies
Skip upstream tasks, run only the tasks matching the
regexp. Only works in conjunction with task_regex
-I, --ignore_first_depends_on_past
Test airflow backfill and run commands with some flags
Tasks that should have been deadlocked are still deadlocked after this change.
Made sure that the right failing dependencies were shown on the task instance page.
Tested new CLI command by running it
Ui still works with all the various force flag combos (ignore_task_deps especially)
Backfill before a task's start date should work
Make sure that for the TI pop up dialog in tree view all buttons that are links work
Make sure logs aren't too crazy (logging a lot more e.g. in scheduler)

@jlowin @mistercrunch @artwr

@aoen interesting side effect: the debug logs seem to be swamping Travis (my browser is choking trying to load the logs in order to see what tests failed). Maybe you could add an env-var switch to turn off dependency logging, if only for testing?

This output can actually be pretty useful (I used it to debug some failing tests for the original PR). I think the right solution would be to modularize the travis-ci code (e.g. getting a test overview and then being able to drill down into the output of each test/module), or maybe suppress output from successful tests in CI. I also think there was talk about trying not to add unimportant flags to reduce branching complexity since it is already fairly high. @jlowin @mistercrunch what do you think?

Current coverage is 65.05% (diff: 86.57%)

Merging #1729 into master will increase coverage by 0.31%

@@             master      #1729   diff @@
==========================================
  Files           127        141    +14
  Lines          9498       9752   +254
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits           6149       6344   +195
- Misses         3349       3408    +59
  Partials          0          0

Powered by Codecov. Last update 821bdb5...036a4ac

LGTM!

🎆

@aoen there seems to be an issue with retries not executing. See also: https://issues.apache.org/jira/browse/AIRFLOW-695 . Will try to dive in but might need help

@bolkedebruin I will take a look hopefully today

@bolkedebruin I couldn't repro on that version albeit with the SequentialExecutor (the task retried successfully). I feel if there was a bug though it would be with the dagrun logic, not the task dependency logic (dagruns should not be getting set to failed when there is an up_for_retry task ).
Does that make sense to you?


GPII-3670: Enable Istio add-on

This PR installs Istio GKE Add-on.
Note: This will not change behaviour of existing application in any way, as Istio sidecar has to be injected manually or by labelling the namespace with istio-injection=enabled.
Requires gpii-ops/exekube/pull/44.

LGTM


Machine translation is converting "regular expressions" incorrectly.

Machine translation  convert "regular expressions" incorrectly.
In English
"[a-zA-Z0-9_]"*
In Japanese
"[zA-A-za-z0-9_]"*

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: f13895a3-a0d7-77b6-0c6a-5431dfae2413
Version Independent ID: 347e4a7e-7607-6e9d-bc21-358b70792852
Content: Regular Expressions (C++)
Content Source: docs/standard-library/regular-expressions-cpp.md
Product: visual-cpp
Technology: cpp-standard-libraries
GitHub Login: @TylerMSFT
Microsoft Alias: twhitney

Hi @maoutokagura,
I have fixed this. It should be live in a couple days. Thank you for pointing out the issue so we could address it.


fix: fix formatting of Debug Splunk Connect for SNMP documentation

Description
fix formatting of Debug Splunk Connect for SNMP documentation
Fixes # (issue)
Type of change
Please delete options that are not relevant.

[x] Refactor/improvement

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Checklist

[x] My commit message is conventional
[x] I have run pre-commit on all files before creating the PR
[x] I have commented my code, particularly in hard-to-understand areas
[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] New and existing unit tests pass locally with my changes
[x] I have checked my code and corrected any misspellings

:tada: This PR is included in version 1.11.0-beta.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Write documentation for "global" role

Closing, this is part of the emacs role, and no longer necessary.


Rebuild Models in U8StarterKit.Web.Models.Umbraco Using Models Builder 8.1.0

After an upgrade to 8.1.0 the site renders with the error
Cannot bind source content type Umbraco.Web.PublishedCache.NuCache.PublishedContent to model type U8StarterKit.Web.Models.Umbraco.Home

I believe, due to updates in Umbraco IPublishedContent and Bulma Starter Kit's custom models approach, all the custom models will need to be regenerated against the new ModelsBuilder and IPublishedContent in Umbraco 8.1.0.
There may be other places where updates will be required as well as 8.1.0 introduced a number of breaking changes:
https://our.umbraco.com/documentation/Getting-Started/Setup/Upgrading/v81-ipublishedcontent-changes
I'll try to get to this, but wanted to capture the issue in case others had input or want to get started on the updates.

Is this issue Also related to this post
https://our.umbraco.com/packages/starter-kits/bulma-starter-kit/bulma-starter-kit-for-v8/98417-falink-does-not-work

For my team, the kit as distributed in the kit was never going to work for us, as we need the modelsbuilder to work and could not do so with the distributed model/dll version.
I downloaded source files from this repo, used the models builder in the AppData mode, and we've not had any issues upgrading to 8.1.0. For us, the repo version has worked much better than the package on umbraco. But our skill set is more frontend.
That said, falink gave us lots of fits at first due to not having null checks. As we changed the templates for !=null everywhere, falink has been fine.
Hope you don't mind my 2cents. When we went with Umbraco 8 a few months back, this was the most robust kit to start from and it is serving us weel.

Hi @cherylcarpenter -
That sounds like a solid approach...along the lines of what I've been considering as well. Would you be willing to create a new branch and send a PR to this repo with your changes? Perhaps that could jumpstart the process to get the starterkit moved over to models builder by default. I'd love to see that for one:
https://twitter.com/paulsterling/status/1136377896006590465

Would you be willing to create a new branch and send a PR to this repo with your changes?

oh hah, i can try given a day or two-- I'm really a hack :) I liked the 3-projects in one solution seen here, and kept fiddling til it worked with a blank database lol.
Here's my webconfig

And yes just search and replace the namespaces throughout. My goal being to get to my blank install Admin side to push the models builder button. I'll see what i can branch to here.

PS--

oh yeah, AND make sure the FaLinks dll is 'Included' in the VS project.

I found the gotcha, i apologize for the rabbit hole. I had indeed updated to 8.1 and everything worked. It breaks when generating any new models with the updated ModelsBuilder. Reading through the breaking changes (in minor revision numbers again) on IPublishedContent. I'm guessing there is needed updates in the GetFaLinks as HasValue() no longer works on the FaLinks object.
And that's the extent of my skill level and I will downgrade to v8, until the FaLinks rewritten or we work round.
Thanks.

Thanks guys, I've updated the Starter Kit to work with Umbraco version v8.2.0, also the models mode is now set to DLL, so the models are no longer included in the main project Dll and can be regenerated as required. Thanks for using my starter kit! :)

Hi there,
I am getting this error
<EMAIL_ADDRESS><EMAIL_ADDRESS>Shahid Mahmood Hussain
Senior Solution Architect, Dynamics 365
Mobile: +45 26 85 74 97
Abakion A/S | Vibenshuset, Lyngbyvej 2 | 2100 København Ø | Danmark | + 45 70 23 23 17
Abakion.dkhttps://abakion.dk | Abakion.comhttps://abakion.com | Facebookhttps://www.facebook.com/abakion.dk | LinkedInhttps://www.linkedin.com/company/abakion-as
From: mjbarlow<EMAIL_ADDRESS>Sent: 24. oktober 2019 18:18
To: mjbarlow/Umbraco-8-Bulma-Starter-Kit<EMAIL_ADDRESS>Cc: Shahid M. Hussain<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [mjbarlow/Umbraco-8-Bulma-Starter-Kit] Rebuild Models in U8StarterKit.Web.Models.Umbraco Using Models Builder 8.1.0 (#2)
Thanks guys, I've updated the Starter Kit to work with Umbraco version v8.2.0, also the models mode is now set to DLL, so the models are no longer included in the main project Dll and can be regenerated as required. Thanks for using my starter kit! :)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmjbarlow%2FUmbraco-8-Bulma-Starter-Kit%2Fissues%2F2%3Femail_source%3Dnotifications%26email_token%3DACN7T3LRBN4N5RZURKSFL2LQQHDDHA5CNFSM4IE6DAO2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECFTIRY%23issuecomment-545993799&data=01|01|smh%40abakion.com|0caa63a051454ff0ea8e08d7589dbed0|c004bd17f2d6493b8e5ec275adeed22f|0&sdata=7aNp9KN7gNKcths7zTcDERwZpQ%2BkUicPfk9YaLe5F%2FU%3D&reserved=0, or unsubscribehttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FACN7T3I2IHSASJCD2YN5DOLQQHDDHANCNFSM4IE6DAOQ&data=01|01|smh%40abakion.com|0caa63a051454ff0ea8e08d7589dbed0|c004bd17f2d6493b8e5ec275adeed22f|0&sdata=l0IZbZkAOzoVKHvlaOu046tiM3PNmcomU6OIC%2BmbuNs%3D&reserved=0.

Hi There,
i am getting this error


[hotfix][docs] fix error in Process Function Doc

What is the purpose of the change
In the example given,it used the ProcessFunction on a keyed stream. But in the new version, it has been deprecated and it has been replaced with KeyedProcessFunction. The example code also has some errors in the Scala snippet. Using the original scala example can cause unnecessary problems for users.
Brief change log

Replace the deprecated ProcessFunction with KeyedProcessFunction And fix some errors in the Scala snippet

Thanks for the PR @zsq12138!
The changes look good to me.
@flinkbot approve description consensus architecture quality
I'll merge this PR.
Thanks, Fabian

@flinkbot approve all


GRPC can allocate lot of memory and cause OOM

Development Task
Here is a memory profile:
a.svg.zip

It looks like bytes::Bytes in protobuf is not released.

What's the fix solution?


inventory ignore does not allow different values in same category

The ignore dictionary for systest inventory should be a list or similar.  As currently implemented
its a dictionary,  and Python uses a unique Key in dictionaries.    For example,  we cannot tell systest inventory to ignore network:enabled and network:speed.

Gerrit review
https://gerrit.openbmc-project.xyz/5989


Weird jetpack fall damage behavior

While trying to troubleshoot an issue with fall damage not applying properly, after doing some testing it seems like the issue was linked to the JetpackHandling mod.
After doing some more testing fall damage was finally applying properly, so then what was left was to check if it was also working while using a jetpack, but unfortunately there seems to be a very odd behavior happening as you can see in the following video:
https://github.com/Hamunii/JetpackFallFix/assets/3759901/be20447c-35a7-4e70-b54e-2e3a7397b474
The damage is applying both "downwards" and "upwards" in the sense that sometimes the applied damage actually ends up "healing" the amount of HP instead of taking away from it.
Currently suspecting that the issue may stem from some weird interaction between JetpackFallFix and the following installed mods:

LC-LethalWeight
LC-DynamicFallDamage

UPDATE:
After some more testing I am actually able to rule out JetpackFallFix as the cause of the issue.
It seems to actually be related to an issue when both LC-LethalWeight & LC-DynamicFallDamage are used in tandem.


Update DB dump for distro-event related changes

new tables distro_events etc.
extend locations table (type, latitude, longitude, description)
extend stock table (FK for distro event)

 Mobile Distro: Needed DB Migrations - Round 1

I just finished the first adaptions to python code in the Mobile Distro prototyping branch and checked whether it overall works. Looks really good so far! :)
Confidence/insights should increase during this week.


Periodic jobs are ran for forked repos

It's usually not needed, and needlessly consumes shared resources. The jobs are usually needed only for the original repo since they help keeping the action wrappers up-to-date.

Original, schedule: yes
Original, not schedule: yes
Fork, schedule: no
Fork, not schedule: yes
Run if original or not schedule.

TODO: ask fork owners to update the forks.

@Goooler the fix is merged, could you please sync your fork and check if these workflows aren't run on schedule?

Synced.

Next step: check tomorrow here https://github.com/Goooler/github-actions-kotlin-dsl/actions?query=event%3A schedule if the jobs are still ran.

@aSemy
@cybernetics
@ema987
@jmfayard
@LeoColman
@LouisCAD
@madhead
@NikkyAI
@polarene
@scottbisaillon
@uweschaefer
@Vampire
Please sync your forks with the newest commit on parent's main branch. The goal is to save GitHub resources by not running periodic jobs in the forks.
Once you do so, please give me a :+1: under this comment. Thanks!

Thanks for that, it was a bit annoying!

synced

I don't have workflows enabled, they are disabled by default for forks.

I just deleted the fork, I don't remember why I made it in the first place. Thanks for pointing this out.


data:NimishKashyap

Changes proposed

Added profile for Nimish Kashyap

Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[x] My change requires changes to the documentation.
[x] I have updated the documentation accordingly.
[x] All new and existing tests passed.
[x] This PR does not contain plagiarized content.
[x] The title of my pull request is a short description of the requested changes.

Thank you so much!


[Linux] Bun extension is not running after build

Hi @hschneider, i'm testing the code yesterday and after the neu build i run the binary from dist folder but return this error ./dist/ext-bun/extensions/bun/run: line 5: ./dist/ext-bun/extensions/bun/_runtime/bin/bun: No such file or directory. In my understand the neu build is not copy the _runtime folder. I'm running the program with the host bun runtime.
I'm already trying to fix this and open a pull request with the fix later.

It's my fault, i forget to run the install.sh before build the app.

No prob :-)


Fix toggle subscription

See https://github.com/TryGhost/Ghost/issues/12996

Thanks for the issue and the PR @nehalist


[API 7.2] Issues with Mixed-Format Sticker Packs

Hi!
I'm one of the nutgram mantainers, while upgrading the framework to support the latest changes, we noticed a bunch of issues related to the new mixed format stickers:

Added the field format to the class InputSticker.

Backwards compatibility has been broken:

Idk, might intented to be this way, but if yes, than doesnt make any sense why is not required while adding a sticker to a set:

But a bigger issue is that the API accepts stickers that doesn't match the specified format (are also displayed correctly):

So, seems the API does not care what format contains, but only requires the format parameter to be present in the request 🤔

Added the parameter format to the method setStickerSetThumbnail.

Same here, backwards compatibility has been broken, and a bunch of random errors are given for different combinations of input parameters:

But when format is specified, seems to work fine:

cc @Lukasss93

Backward compatibility wasn't broken. Since Bot API 7.2 the field format in InputSticker is mandatory and must be always specified, but you don't pass it. Previously, createNewStickerSet had mandatory parameter sticker_format. You don't pass it either, therefore the request is invalid and isn't expected to succeed.
The format field is required in all methods, including addStickerToSet and setStickerSetThumbnail. If you failed to specify it or specified an incorrect value, then it is hardly possible to predict effect of the request. It can succeed, fail, or succeed, but add a broken sticker to the set.

Okay, I see what you mean.

If an old bot has always used the createNewStickerSet method with the sticker_format field, the API will continue to work the same way.
The important thing is that either the sticker_format field or the format field is set inside the InputSticker.
As for the addStickerToSet method, even though the format parameter is mandatory as you say, it actually works even if it is not passed.
Finally, the setStickerSetThumbnail method no longer works for old bots that use this method, because the format parameter is now mandatory, which is a breaking change.

Method
API 7.1
API 7.2
Breaking change?

createNewStickerSet

sticker_format:✅
stickers.*.format:❌

sticker_format:❌
stickers.*.format:✅

NO

addStickerToSet
sticker.format:❌
sticker.format:❔optional
NO

setStickerSetThumbnail
format:❌
format:✅
⚠ YES

Backward compatibility wasn't broken. Since Bot API 7.2 the field format in InputSticker is mandatory and must be always specified, but you don't pass it. Previously, createNewStickerSet had mandatory parameter sticker_format. You don't pass it either, therefore the request is invalid and isn't expected to succeed.
The format field is required in all methods, including addStickerToSet and setStickerSetThumbnail. If you failed to specify it or specified an incorrect value, then it is hardly possible to predict effect of the request. It can succeed, fail, or succeed, but add a broken sticker to the set.

Yep you right about the the createNewStickerSet call, my bad.
But the other stuff is still valid, so in addition the the @Lukasss93 's summary above, what I wanted to point out are the misleading error messages that the api returns in these cases, as well as the lack of validation with respect to the consistency between the uploaded file and the format field.

As for the addStickerToSet method, even though the format parameter is mandatory as you say, it actually works even if it is not passed.

It doesn't always work. It can work in some cases for backward compatibility for old bots. The parameter format is mandatory in InputSticker and must be always passed to ensure that the bot correctly works with mixed-format sticker packs.
setStickerSetThumbnail works for old bots as it worked previously. Backward compatibility is enforced by Bot API and there were no backward compatibility breaking changes for requests in Bot API 7.2.

Yesterday the Telegram team released Bot API 7.2. This update brings many changes, which we are already working on implementing.
However there is one major backward incompatible change, which is the removal of the fields StickerSet.is_animated/is_video. This unfortunately breaks the method Bot.get_sticker_set and affects all versions of our library.  The current workaround for this if you have v20.8+ is to directly call
await bot.do_api_request("get_sticker_set", {"name": sticker_set_name})
and parse the resulting JSON return value. The upcoming version of the library will address this incompatibility.
Thank you for understanding and being patient.


Getting access to usage tokens

We might implement a limit to the number of calls being made (based on user account).
Also, we would like to measure/track the usage of LLM calls.
For that, I would like to get the usage response (number of tokens used by LLM) from the LLM call, accessible in the API response, or possibly stored in the /conversations collection.

hi Eric,
Good idea. I think this is something worth including natively in the framework b/c i could imagine the use case is fairly generic + many if not most LLM APIs include token usage info in the response so it'd be a low-cost thing to add.
However, just FYI, i don't think we're going to be able to get to this in the immediate future given some other features we're working on.


Log status of port before starting server with SelfHostDeployer

I'm trying to make it easier to determine if EADDRINUSE errors in our integration tests are caused because the port truly is in use or because there is some libuv problem binding to addresses.
cref https://github.com/aspnet/Entropy/issues/209

Sample of the output?

macOS with and without port in use

Windows with and without port in use

@natemcmaster: Looks like this is failing in our CI builds:
| ResponseFormats:WebListener:Clr:x64:Portable Warning: Failed to check port status. Executed: cmd /C netstat -nq | find "5087"
|                                                       Error: System.InvalidOperationException: The Process object must have the UseShellExecute property set to false in order to redirect IO streams.
|                                                          at System.Diagnostics.Process.StartWithShellExecuteEx(ProcessStartInfo startInfo)
|                                                          at System.Diagnostics.Process.Start()
|                                                          at Microsoft.AspNetCore.Server.IntegrationTesting.PortHelper.LogPortStatus(ILogger logger, Int32 port)

I'm going to revert this. It was an attempt to figure out what was causing port conflicts in tests, but it didn't help enough. I think we'll have more success if use dynamic ports.


problem with Process killed because out of memory and validation callback timed out before we could respond

Hello,
in the past era and in Encore, the node itself begins to lag behind the high block
helps to restart the node.
I understand that I will overload and everything will be ok but this is not normal
now block 6603
I seem to understand what happened, at first  Process killed because out of memory
then validation callback timed out before we could respond....
but the status of the node has not changed uptime node more than 4 days
I have a server 16cpu and 32gb memory

mina.zip
pay attention to the time  - 2021-02-12 14:52:13.849152
thanks.

This sounds like issue #7555: the verifier should have attempted to restart after being killed, but because of that issue it doesn't restart and the node gets stuck. We're currently testing a fix for this issue.
Closing as duplicate of #7555.


Can't destroy/place blocks

I cannot seem to figure out how to break a block...

In the http://maxogden.github.io/voxel-engine/ demo you left-click to break blocks, and control-left-click to place blocks. In the ndarray/stackgl branch (https://github.com/maxogden/voxel-engine/pull/103) this functionality is split out into several distinct plugins (for use with voxel-plugins):

https://github.com/deathcap/voxel-mine - provides variable-length mining whilst holding down the left mouse button, plus a block break overlay decal
https://github.com/deathcap/voxel-harvest - adds broken blocks as items to the player's inventory
https://github.com/deathcap/voxel-reach - low-level plugin to raycast voxels within each and send mining/use events to other plugins
https://github.com/deathcap/voxel-use - handles right-clicking with blocks (and items) = placement

@deathcap Super Informative.... lets add this to the wiki (which I am just going to go ahead and make because we definitely need one :smile)


[Question] profile picture

Hello i want to know where is stocked the default picture for profile, because i want to edit it to modify one with my own profile picture thanks.
I have tested to add with the curent name of my picture in local state (before open the browser) it didn't work
I have tested to add the picture in default/Avatars (created folder) it didn't work either.

I see this has been closed as "completed", am I missing something?
It would be quite handy to be able to change the profile picture when using multiple profiles, is there a way to do it now?

I see this has been closed as "completed", am I missing something?

Yes, it seems that the user simply closed their own issue (maybe due to a lack of any response). The whole "completed" thing is something that GitHub added much later, i.e. the issue was originally just "closed" (without any "as").
When it comes to the profile pictures themselves, unfortunately there is still no easy way to use custom images. It does seem possible with some hackery, e.g. see https://superuser.com/questions/449244/how-do-i-access-edit-the-chrome-user-avatar-images/639248#639248, although I haven't tested the method myself.

Thank you for the explanation and help, will definately checkout the hacky way for now.


coffee-file: Changed yocto image from balena-image to balena-image-flasher

Changelog-entry: Changed yocto image from balena-image to balena-image-flasher
Signed-off-by: joris-bright<EMAIL_ADDRESS>

Hi, can you rebase this PR please?

@resin-jenkins test this please

@resin-jenkins retest this please

Superseded by https://github.com/balena-os/balena-kontron-mx8mm/pull/53 which also updates the deploy artifact name


Running BGP health test on switch wihthout multi-agent

On switches that do not have "service routing protocols model multi-agent" configured, the cmd "show bgp {afi} {safi} summary  is not supported. When using VerifyBGPSpecificPeers or VerifyBGPHealth tests, it seems to only work if the switch in question is using mulit-agent. For switches that have "service routing protocols model ribd" configured, there should be a way for the test to run "show ip bgp sum'
It seems the problem may be here, as "show bgp {afi} sum' is not a valid EOS command:
commands: ClassVar[list[AntaCommand | AntaTemplate]] = [
    AntaTemplate(template="show bgp {afi} {safi} summary vrf {vrf}", revision=3),
    AntaTemplate(template="show bgp {afi} summary", revision=3),

From a switch running 4.31.5M, 'summary' is not an option
switch#sh bgp ipv4 ?
access-list      Named access-list
labeled-unicast  Display labeled-unicast information
multicast        Display multicast information
unicast          Display unicast information
Also from a switch not running multi-agent:
switch#sh bgp ipv4 unicast sum
% Not supported

Hi @kosichd,
These tests are indeed only supported on switches running with multi-agent. Multi-agent has been the default since 4.30.1, and starting with 4.32, you cannot configure ribd at all. Therefore, we don't have any plans to support ribd for these tests.
The show bgp {afi} summary command template is only used when the AFI is not IPv4 or IPv6 (e.g., evpn, vpn-ipv4, etc.). VRF is not needed here since these AFIs operate at a global level and do not use the VRF concept in the same way as IPv4/IPv6. On the other hand, show bgp {afi} {safi} summary vrf {vrf} template is used with IPv4 and IPv6 AFIs, where a SAFI is also needed with an optional VRF.
We have simpified the logic of this in PR #888, where we now use show bgp summary vrf all and show bgp neighbors vrf all commands instead, without impacting test inputs.

Thanks for the quick reply @carl-baillargeon

Anytime @kosichd. I will add a note in our documentation around this.
Thanks!


The Dice of BTras is different from the paper!

Dear  @Amshaker ,
（1）I have downloaded all the data sets and training plans you provided for Synapse, ACDC, Decathlon-Lung and BRaTs. The Dice of Synapse and ACDC differs from the paper by about 1%, but the Dice of brat is very low. I will paste my debug and Dice later, could you please solve my questions? Training is performed on a P40 graphics card
（2）I debug the code in unetr_pp_traniner_Synapse.py, but I don't see self_embedding_dim, self_embedding_patch_size, and self_window_size used. Can I delete it? If yes, can you tell him to override the parameters there? Thank you very much.
（3）In (2), there is also an argument self.num_heads=[6,12,24,48], but in network_architecture.synapse num_heads is an int variable, =4, Is self.num_heads=[6,12,24,48] valid?

debug.json

Dear  @Amshaker @mmaaz60 @AbdelrahmanShakerYousef
(1)I looked at you and it seems that you need to deduce the desired result from imagesTs, but I ran into a problem with the same evalution command line error, as follows:
Total trainable parameters: 42.65 M
using the following model files(pre-training weights):  ['../output_tumor/unetr_pp/3d_fullres/Task003_tumor/unetr_pp_trainer_tumor__unetr_pp_Plansv2.d_0/model_final_checkpoint.model']
....
File "/home/hpc/LAB-data/disk-3.6T/X/unetr_plus_plus/training_scripts/../unetr_pp/inference/predict_simple.py", line 229, in main
predict_from_folder(model_folder_name, input_folder, output_folder, folds, save_npz, num_threads_preprocessing,
File "/home/hpc/LAB-data/disk-3.6T/X/unetr_plus_plus/unetr_pp/inference/predict.py", line 620, in predict_from_folder
return predict_cases(model, list_of_lists[part_id::num_parts], output_files[part_id::num_parts], folds,
File "/home/hpc/LAB-data/disk-3.6T/X/unetr_plus_plus/unetr_pp/inference/predict.py", line 193, in predict_cases
for preprocessed in preprocessing:
File "/home/hpc/LAB-data/disk-3.6T/X/unetr_plus_plus/unetr_pp/inference/predict.py", line 89, in preprocess_multithreaded
assert isinstance(trainer, Trainer_acdc) or isinstance(trainer, Trainer_synapse)
AssertionError

Dear @Amshaker ,
Sorry for the inconvenience. I have read your paper again to solve my doubts (1). Could you please answer my questions (2) and (3)


chore: Add basic auth env vars to regression tests

Addresses DBTP-1018

Checklist:
Title:

[x] Scope included as per conventional commits
[] Ticket reference included (unless it's a quick out of ticket thing)

Description:

[x] Link to ticket included (unless it's a quick out of ticket thing)
[x] Includes tests (or an explanation for why it doesn't)
[ ] If the work includes user interface changes, before and after screenshots included in description
[ ] Includes any applicable changes to the documentation in this code base
[ ] Includes link(s) to any applicable changes to the documentation in the DBT Platform Documentation (can be to a pull request)

Tasks:

[x] Trigger the pull request regression tests for this branch and confirm that they are passing

Does the CodeBuildRegressionPipelinePolicy get managed anywhere outside of the aws console? I'm looking to grant the smoke tests access to a couple of ssm parameters in platform-sandbox
I've hacked something into the policy to give toolspr the right perms for now, but would like to fix properly


Create zh_cn.long

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Thank you!
Have you looked at the existing PR for the same language? #14
Maybe you could work together with them.

Please work directly with #14 for now.

If you were still interested in continuing your work on a Chinese translation, you should work with the author of PR #23 instead I think.


docs: remove advanced section

(Closes https://github.com/inveniosoftware/invenio-oauthclient/issues/162)
Signed-off-by: Dinos Kousidis<EMAIL_ADDRESS>

I hope I understood correctly and we wanted just to remove the section.


Refactor pythonify_logs and add custom fit integration tests.

Fix #20371
The issue is resolved by applying pythonify_logs to all entry points in CallbackList.
Additionally, this PR moves the implementation of pythonify_logs to keras.src.utils.python_utils and adds integration tests for all backends.

Codecov Report
Attention: Patch coverage is 74.19355% with 8 lines in your changes missing coverage. Please review.

Project coverage is 57.50%. Comparing base (c03eccc) to head (f98cf4a).

Files with missing lines
Patch %
Lines

keras/src/callbacks/callback_list.py
52.94%
8 Missing :warning:

:exclamation:  There is a different number of reports uploaded between BASE (c03eccc) and HEAD (f98cf4a). Click for more details.
HEAD has 4 uploads less than BASE

Flag
BASE (c03eccc)
HEAD (f98cf4a)

keras
3
1

keras-tensorflow
1
0

keras-jax
1
0

Additional details and impacted files
@@             Coverage Diff             @@
##           master   #20380       +/-   ##
===========================================
- Coverage   73.46%   57.50%   -15.97%
===========================================
  Files         513      513
  Lines       49328    49316       -12
  Branches     7954     7952        -2
===========================================
- Hits        36241    28361     -7880
- Misses      11285    19153     +7868
  Partials     1802     1802

Flag
Coverage Δ

keras
57.50% <74.19%> (-15.90%)
:arrow_down:

keras-jax
?

keras-numpy
57.50% <74.19%> (+<0.01%)
:arrow_up:

keras-tensorflow
?

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Undefined symbol NET_BUFFER_LIST

these are my all header files included:
#include <ntddk.h>
#include <wdf.h>
#include <fwpsk.h>
#include <fwpmk.h>
Then build failed, Undefined symbol NET_BUFFER_LIST

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 4d23ce87-c3ae-4e2b-ce12-ecb66c8065c0
Version Independent ID: 6b57dfbb-a5e7-c018-6770-446451c58c5a
Content: Registering Callouts with the Filter Engine - Windows drivers
Content Source: windows-driver-docs-pr/network/registering-callouts-with-the-filter-engine.md
Product: windows-hardware
GitHub Login: @tedhudek
Microsoft Alias: windowsdriverdev

Hi @GreatFireWall,
For this kind of error, I'd recommend that you not only make sure to include the correct headers in your project's include directories, but include the correct libraries in your project's lib directories.
Other than that, I'm sorry you're having an issue but unfortunately we don’t have the resources to offer individual technical advice to the broad array of customers who use the driver documentation.
You may have success posting your question in the following forums, where other driver developers and Microsoft engineers can be found. The community there is quite responsive.
• Windows Hardware WDK and Driver Development
• NTDEV forum at OSR Online
Again, thanks for reaching out. Best of luck with this issue.


Restoration Finish Unreachable

Release
Operating System
Cause

1.4.1
Windows & OSX & Linux)
Unknown

Context

One of our exchange has ran into the following issue at the very end of a wallet restoration:
Exception during restoration of walletHdRootId Ae2tdP../GVTU when starting from BlockContext { slotId 888th slot of 99th epoch, hash   21badd8184a0b27b, prev   a4e7eae10efebf6e} with target BlockContext { slotId 10489th slot of 98th epoch, hash   bd5eca8ea93b4149, prev   7ca1d6ef5978cbe5}.
Exception: RestorationFinishUnreachable bd5eca8ea93b4149 5669397ee61cc285

This is rather... exceptional and caused the node to hang at 100% restored without being eventually synced.
Steps to Reproduce

Unclear. To be determined.
Some possible tracks:

They were restoring multiple wallets at the same time (6 to be exact)
The restoration was started by the migration mechanism embedded in 1.4 (so, restoring wallets coming from <1.3)
They may have started the restoration while the node was still syncing with the blockchain

Expected behavior

A wallet can finalize its restoration successfully, or, at the very least, give some clearer information about the failure.
Actual behavior

The wallet doesn't finalize the restoration and a rather not helpful exception is raised.

Resolution Plan

PR

Number
Base

#?
develop

QA

I am so far unable to get the RestorationFinishUnreachable exception.
Restoring wallet while in recovery mode
I did get the wallet to fail by starting a restore from backup phrase while in recovery mode. If the chain is fully synced, the same restore does not fail.
What happens is that the wallet restore process finishes, but the node never exits recovery mode (absence of "Recovery mode exited gracefully") in log.
Furthermore, the /api/v1/node-info endpoint stops returning data.
I reproduced this with mainnet and testnet. On testnet, the wallet restore was able to finish. On mainnet, I could not finish the wallet restore because it consumed 23GB of RAM and I had to kill the process.
After triggering this error condition, I killed cardano-node and started it again. The restored wallet was present, but the chain sync% went back to where it was before recovery mode was entered last time.
Upgrading from 1.3.2 -> 2.0.1 and wallet restoration
I synced the testnet chain and created a wallet using the 1.3.2 release. Then I stopped the node.
Then ~80 slots later (~25 mins), I started the 2.0.1 wallet on the same state directory. For good measure, I also tried beginning a wallet restore before it was able to exit recovery mode.
In this case, I could not reproduce any bugs. Both wallets restored successfully (the first restore due to upgrade), and the node exited recovery mode.
Conflicts between epoch consolidation and wallet restoration
An exchange were getting exceptions because the epoch consolidation and wallet restoration processes were trying to flock the same files in the blocks db. I think this could be a possible cause of RestorationFinishUnreachable, but haven't yet been able to try testing this.

One thing I'd like to clarify @rvl; were you able to reproduce the restoration finish unreachable with the first case? or is it another case of failure :thinking: ?

One thing I'd like to clarify @rvl; were you able to reproduce the restoration finish unreachable with the first case? or is it another case of failure  ?

In the first case, it was another case of failure, not RestorationFinishUnreachable.
It occurred to me later that this RestorationFinishUnreachable exception is unlikely to be related to upgrading from 1.3.2 -> 2.0.1 (second case) because I asked our user to update by deleting the state directory and restoring the wallet with 2.0.1, rather than migrating the DBs.


rename set methods

In order to avoid collisions with Property.set, the dot "set" methods like Vector2.set, Bounds2.set, etc. should be renamed.
We should have
Vector2.set=>setXY
Vector3.set=>setXYZ
Vector4.set=>setXYZ
Quaternion.set=>setXYZW
Bounds2.set=>setMinMax
Transform.set=>setMatrix

Looks like this was done >1.5 years ago, but no request was made to review. Since it hasn't resulted in problems, I'll close this issue.


Need to writelist the Rails DB

File: compose/rails.md
To be able to connect to the database you need to add a whitelist inside ApplicationController.rb
module Myapp
  class Application < Rails::Application
    # Settings in config/environments/* take precedence over those specified here.
    # Application configuration should go into files in config/initializers
    # -- all .rb files in that directory are automatically loaded.
    config.web_console.whitelisted_ips = '<IP_ADDRESS>/16'
  end
end

Claimed.

This does not hinder the compose and rails quickstart tutorial. I was able to follow the tutorial and load the welcome page without any issues. Since the tutorial works without this config setting it seems best to not introduce an additional step to the quickstart.

Thanks @alfonso-cabrera


Remove rent_exempt constraint

Solana removed the ability to create accounts are not rent exempt, so we can get rid of the rent_exempt=false constraint option.
Not sure if removing it will be beneficial or not. Ideally less code is better so long as it doesn't complicate existing implementations.

But dont you think that removing the rent_exempt might cause a breaking change?