Seems to have problems with Speedtest-cli.

Describe the bug
Calls to speedtest-cli don't complete with valid data sometimes. Speeds returned are 0.0 and ping times are 0, which is not possible.  Call should be executed again.  This behavior is also exhibited by Speedtest -exporter which also uses Speedtest-cli.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
Every test returns good values.
**Environment (please
Latest Docker engine and Docker compose.
Screenshots
If applicable, add screenshots to help explain your problem.
Logs
If applicable, check the logs for any error that might of occurred.
Additional context
Add any other context about the problem here.

I don't have any experience with php, but it looks like ExecSpeedtest.php is where the call is made.
Can you patch it so it re-evaluates Speedtest if there is an error returned.

I think the WAN ip address might be changing in the process and that is causing the problem. It bounces around a lot on the cube.

@DWomack I've got mine running in a swamp and haven't noticed it when a IP changed. Can you make sure the pod isn't being dropped during a test?

"Can you make sure the pod isn't being dropped during a test?"
Please explain.
This is the last 24 hours on the internet-pi app...

I had already deleted the zero entries in the one using yours.

Data pulled out of VZ Cube.  Notice how often the wan IP changes...
Data is newest first.  Cube power recycled at 5:00am

2023 Aug 21   14:27:09
[WAN.6][WDHCP] bound wan_61 IP:   <IP_ADDRESS>

2023 Aug 21 14:27:08
[WAN.6][WDHCP] deconfig wan_61

2023 Aug 21 14:12:03
[WAN.6][WDHCP] bound wan_61 IP: <IP_ADDRESS>

2023 Aug 21 14:12:03
[WAN.6][WDHCP] deconfig wan_61

2023 Aug 21 14:03:24
[WAN.6][WDHCP] ignore renew wan_62 IP: <IP_ADDRESS>

2023 Aug 21 13:56:53
[WAN.6][WDHCP] bound wan_61 IP: <IP_ADDRESS>

2023 Aug 21 13:56:53
[WAN.6][WDHCP] deconfig wan_61

2023 Aug 21 13:41:48
[WAN.6][WDHCP] bound wan_61 IP: <IP_ADDRESS>

2023 Aug 21 13:41:47
[WAN.6][WDHCP] deconfig wan_61

2023 Aug 21 13:26:43
[WAN.6][WDHCP] bound wan_61 IP: <IP_ADDRESS>

2023 Aug 21 13:26:42
[WAN.6][WDHCP] deconfig wan_61

2023 Aug 21 13:11:10
[WAN.6][WDHCP] bound wan_61 IP: <IP_ADDRESS>

2023 Aug 21 13:11:09
[WAN.6][WDHCP] deconfig wan_61

2023 Aug 21 13:03:24
[WAN.6][WDHCP] ignore renew wan_62 IP: <IP_ADDRESS>

2023 Aug 21 12:56:04
[WAN.6][WDHCP] bound wan_61 IP: <IP_ADDRESS>

2023 Aug 21 12:56:03
[WAN.6][WDHCP] deconfig wan_61

2023 Aug 21 12:40:58
[WAN.6][WDHCP] bound wan_61 IP: <IP_ADDRESS>

2023 Aug 21 12:40:58
[WAN.6][WDHCP] deconfig wan_61

2023 Aug 21 12:25:53
[WAN.6][WDHCP] bound wan_61 IP: <IP_ADDRESS>

2023 Aug 21 12:25:53
[WAN.6][WDHCP] deconfig wan_61

2023 Aug 21 12:10:49
[WAN.6][WDHCP] bound wan_61 IP: <IP_ADDRESS>

2023 Aug 21 12:10:48
[WAN.6][WDHCP] deconfig wan_61

2023 Aug 21 12:03:24
[WAN.6][WDHCP] ignore renew wan_62 IP: <IP_ADDRESS>

2023 Aug 21 11:55:43
[WAN.6][WDHCP] bound wan_61 IP: <IP_ADDRESS>

2023 Aug 21 11:55:43
[WAN.6][WDHCP] deconfig wan_61

2023 Aug 21 11:40:31
[WAN.6][WDHCP] bound wan_61 IP: <IP_ADDRESS>

2023 Aug 21 11:40:30
[WAN.6][WDHCP] deconfig wan_61

2023 Aug 21 11:25:11
[WAN.6][WDHCP] bound wan_61 IP: <IP_ADDRESS>

2023 Aug 21 11:25:10
[WAN.6][WDHCP] deconfig wan_61

2023 Aug 21 11:10:03
[WAN.6][WDHCP] bound wan_61 IP: <IP_ADDRESS>

2023 Aug 21 11:10:03
[WAN.6][WDHCP] deconfig wan_61

2023 Aug 21 11:03:24
[WAN.6][WDHCP] ignore renew wan_62 IP: <IP_ADDRESS>

2023 Aug 21 10:54:58
[WAN.6][WDHCP] bound wan_61 IP: <IP_ADDRESS>

2023 Aug 21 10:54:58
[WAN.6][WDHCP] deconfig wan_61

2023 Aug 21 10:39:53
[WAN.6][WDHCP] bound wan_61 IP: <IP_ADDRESS>

2023 Aug 21 10:39:53
[WAN.6][WDHCP] deconfig wan_61

2023 Aug 21 10:24:43
[WAN.6][WDHCP] bound wan_61 IP: <IP_ADDRESS>

2023 Aug 21 10:24:43
[WAN.6][WDHCP] deconfig wan_61

2023 Aug 21 10:09:38
[WAN.6][WDHCP] bound wan_61 IP: <IP_ADDRESS>

2023 Aug 21 10:09:37
[WAN.6][WDHCP] deconfig wan_61

2023 Aug 21 10:03:25
[WAN.6][WDHCP] ignore renew wan_62 IP: <IP_ADDRESS>

2023 Aug 21 09:54:33
[WAN.6][WDHCP] bound wan_61 IP: <IP_ADDRESS>

2023 Aug 21 09:54:32
[WAN.6][WDHCP] deconfig wan_61

2023 Aug 21 09:24:15
[WAN.6][WDHCP] bound wan_61 IP: <IP_ADDRESS>

2023 Aug 21 09:24:15
[WAN.6][WDHCP] deconfig wan_61

2023 Aug 21 09:09:09
[WAN.6][WDHCP] bound wan_61 IP: <IP_ADDRESS>

2023 Aug 21 09:09:08
[WAN.6][WDHCP] deconfig wan_61

2023 Aug 21 09:03:24
[WAN.6][WDHCP] bound wan_61 IP: <IP_ADDRESS>

2023 Aug 21 08:53:58
[WAN.6][WDHCP] deconfig wan_61

2023 Aug 21 08:53:58
[WAN.6][WDHCP] ignore renew wan_62 IP: <IP_ADDRESS>

2023 Aug 21 08:38:46
[WAN.6][WDHCP] bound wan_61 IP: <IP_ADDRESS>

2023 Aug 21 08:38:46
[WAN.6][WDHCP] deconfig wan_61

2023 Aug 21 08:23:39
[WAN.6][WDHCP] bound wan_61 IP: <IP_ADDRESS>

2023 Aug 21 08:23:38
[WAN.6][WDHCP] deconfig wan_61

2023 Aug 21 08:08:33
[WAN.6][WDHCP] bound wan_61 IP: <IP_ADDRESS>

2023 Aug 21 08:08:33
[WAN.6][WDHCP] deconfig wan_61

2023 Aug 21 08:03:24
[WAN.6][WDHCP] bound wan_61 IP: <IP_ADDRESS>

2023 Aug 21 07:53:28
[WAN.6][WDHCP] deconfig wan_61

2023 Aug 21 07:53:28
[WAN.6][WDHCP] ignore renew wan_62 IP: <IP_ADDRESS>

2023 Aug 21 07:38:23
[WAN.6][WDHCP] bound wan_61 IP: <IP_ADDRESS>

2023 Aug 21 07:38:23
[WAN.6][WDHCP] deconfig wan_61

2023 Aug 21 07:23:18
[WAN.6][WDHCP] bound wan_61 IP: <IP_ADDRESS>

2023 Aug 21 07:23:18
[WAN.6][WDHCP] deconfig wan_61

2023 Aug 21 07:08:13
[WAN.6][WDHCP] bound wan_61 IP: <IP_ADDRESS>

2023 Aug 21 07:08:13
[WAN.6][WDHCP] deconfig wan_61

2023 Aug 21 07:03:24
[WAN.6][WDHCP] bound wan_61 IP: <IP_ADDRESS>

2023 Aug 21 06:53:01
[WAN.6][WDHCP] deconfig wan_61

2023 Aug 21 06:53:00
[WAN.6][WDHCP] ignore renew wan_62 IP: <IP_ADDRESS>

2023 Aug 21 06:37:46
[WAN.6][WDHCP] bound wan_61 IP: <IP_ADDRESS>

2023 Aug 21 06:37:45
[WAN.6][WDHCP] deconfig wan_61

2023 Aug 21 06:22:31
[WAN.6][WDHCP] bound wan_61 IP: <IP_ADDRESS>

2023 Aug 21 06:22:30
[WAN.6][WDHCP] deconfig wan_61

2023 Aug 21 06:07:23
[WAN.6][WDHCP] bound wan_61 IP: <IP_ADDRESS>

2023 Aug 21 06:07:23
[WAN.6][WDHCP] deconfig wan_61

2023 Aug 21 06:03:24
[WAN.6][WDHCP] bound wan_61 IP: <IP_ADDRESS>

2023 Aug 21 05:52:18
[WAN.6][WDHCP] deconfig wan_61

2023 Aug 21 05:52:17
[WAN.6][WDHCP] ignore renew wan_62 IP: <IP_ADDRESS>

2023 Aug 21 05:36:43
[WAN.6][WDHCP] bound wan_61 IP: <IP_ADDRESS>

2023 Aug 21 05:36:42
[WAN.6][WDHCP] deconfig wan_61

2023 Aug 21 05:21:30
[WAN.6][WDHCP] bound wan_61 IP: <IP_ADDRESS>

2023 Aug 21 05:21:30
[WAN.6][WDHCP] deconfig wan_61

2023 Aug 21 05:06:22
[WAN.6][WDHCP] bound wan_61 IP: <IP_ADDRESS>

2023 Aug 21 05:06:22
[WAN.6][WDHCP] deconfig wan_61

2023 Aug 21 05:03:23
[WAN.6][WDHCP] bound wan_61 IP: <IP_ADDRESS>

2023 Aug 21 05:03:23
[WAN.6][WDHCP] deconfig wan_61

2023 Aug 21 05:03:23
[WAN.6][WDHCP] bound wan_62 IP: <IP_ADDRESS>

2023 Aug 21 05:03:22
[WDHCP] ipv4 wan up

2023 Aug 21 05:02:50
[WAN.6][WDHCP] deconfig wan_62

2023 Aug 21 05:02:49
[WDHCP] ipv6 wan up

2023 Aug 21 05:02:02
[WAN.6][WDHCP] bound wan_61 IP: <IP_ADDRESS>

The wan_61 stuff is the admin channel to manage the cube.
The wan_62 stuff is WAN address of the cube.  This is your ip address seen from the cloud.

Question: Is the Speedtest-cli code downloaded from Ookla each time just before each execution? Or when the docker is started?
Just looking of similarities with another app showing the same symptoms.
Thanks.

I have VZ 5G Home Internet via ASK Cube firmware fully patched.
The issues ie: failures are due to the way the program handles errors that are returned by speedtest cli.
Speedtest cli occasionally throws errors when on VZ.
I installed the latest speedtest cli from Ookla on a box with Ubuntu 22.04 fully patched for testing.  Running it from the command line I see it error occasionally.
I suspect the program is not catching the error and retrying the test when speedtest cli is called.

dennis@xxxx:~$ speedtest --progress=no
Speedtest by Ookla
  Server: Verizon - Nashville, TN (id: 30809)
     ISP: Verizon Wireless

Idle Latency:    33.71 ms   (jitter: 6.96ms, low: 28.28ms, high: 42.88ms)
Download:   207.42 Mbps (data used: 374.1 MB)
113.92 ms   (jitter: 37.85ms, low: 36.66ms, high: 615.84ms)
Upload:    20.35 Mbps (data used: 26.3 MB)
83.73 ms   (jitter: 18.81ms, low: 45.79ms, high: 287.21ms)
Packet Loss:     0.0%
Result URL: https://www.speedtest.net/result/c/dc596e4c-1e78-4c2f-9c9d-f9aea781045d
dennis@xxxx:~$ speedtest --progress=no
Speedtest by Ookla
  Server: Verizon - Nashville, TN (id: 30809)
     ISP: Verizon Wireless

Idle Latency:    34.34 ms   (jitter: 5.71ms, low: 29.98ms, high: 39.97ms)
Latency: FAILED
[error] Cannot read:

That to me looks like a Speedtest server failing to run a test. Can you select a different one?

Thanks for replying.  This is the sever that Speedtest selected.  It generally has the lowest ping. From the command line, I can re run the test and the test will complete.  The fail is not a permanent fail.  The problem could be with VZ’s wireless network or in Ookla’s code.  If your code detects an error returned wait 10 seconds and retry.  You might allow 5 retries.  I am not a php programmer so I can’t fix it.  There is a project called Speedtest-exporter written python.  It calls the Ookla code.  It exhibits the same problem. So the problem is Ookla code or VZ.  I am not criticizing your work, just trying to help it work in my situation.  Thank you. DennisSent from my iPhoneOn Aug 31, 2023, at 8:32 AM, Alex Justesen @.***> wrote:
That to me looks like a Speedtest server failing to run a test. Can you select a different one?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

Why am I using VZ 5G home internet?  $25 per month. Sent from my iPhoneOn Aug 31, 2023, at 9:11 AM, Dennis Womack @.> wrote:Thanks for replying.  This is the sever that Speedtest selected.  It generally has the lowest ping. From the command line, I can re run the test and the test will complete.  The fail is not a permanent fail.  The problem could be with VZ’s wireless network or in Ookla’s code.  If your code detects an error returned wait 10 seconds and retry.  You might allow 5 retries.  I am not a php programmer so I can’t fix it.  There is a project called Speedtest-exporter written python.  It calls the Ookla code.  It exhibits the same problem. So the problem is Ookla code or VZ.  I am not criticizing your work, just trying to help it work in my situation.  Thank you. DennisSent from my iPhoneOn Aug 31, 2023, at 8:32 AM, Alex Justesen @.> wrote:
That to me looks like a Speedtest server failing to run a test. Can you select a different one?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

No worries, I tried to hit the same server and got the fail as well. I think enabling some retries on failed speedtests is a good enhancement.
For future Alex or someone willing to do a PR the jobs and how to do retries can be found at the links below...

https://github.com/alexjustesen/speedtest-tracker/blob/main/app/Jobs/ExecSpeedtest.php
https://laravel.com/docs/10.x/queues#max-exceptions

Thank you, thank you.
I just updated to your latest from two hours ago.
This is docker running on UnRaid.
Dennis

This is docker running on UnRaid.

I've got unraid too so I'll verify there as well

I switched from the default VZ Nashville speedtest server to Comcast Nashville.  No errors.  The Nashville VZ server has issues as you saw.  I even see it with the Speedtest app on my phone.  On my phone I would normally use VZ Atlanta.
The reason for using a VZ server is that it stays in their network to connect to the cloud.  Anything else is going to have worse numbers.
I really appreciate your help.

While you are at it...
The selection of Speedtest server is a pulldown list of servers that Speedtest.net hands you.
It would help if you could as an alternate just enter the server id number.
As is it shows me servers around Nashville.  I would like to enter a server id that is in the Atlanta area.
Thank you.

It would help if you could as an alternate just enter the server id number.

So you actually can if you know the ID of the server you want. Just start typing it in and it'll throw a weird message [object object] but that should allow you to use any server ID.

but that should allow you to use any server ID.

We discussed this issue in an old issue: that doesn't work, it leads to a "0" entry:

The only way to add a manual server id I found is editing the mariadb record. :)

VZ finally fixed the issue with their Nashville Speedtest.net server.
It would help if the home page showed what server you were connecting to.

It would help if the home page showed what server you were connecting to.

So your results page will show which server was used for a successful speedtest, in the future I'll be looking to also log/show which server failed a test as well.


redis cleanup

Which problem is this PR solving?

n/a

Short description of the changes

Removing unneeded type RedisPluginStreamTypes
only import required type from redis where applicable
prefer import type where applicable

I would prefer to just add type for all imports
import type * as redisTypes from 'redis'

without really changing redisTypes into redis and be consistent everywhere so avoid things like
import type { Callback } from 'redis';

but rather have
import type * as redisTypes from 'redis'

// and then
callback: redisTypes.Callback<unknown>;

It is much more intuitive to see something like redisTypes.Callback instead of Callback or later
redisTypes.RedisClient instead of RedisClient mixed with RedisPluginClientTypes and trying to figure out which type comes from where

Alright I've adjusted as requested.


Adding headers to static files

We are using roadrunner with PHP and docker and have the following .rr.yaml:
http:
  address: :8080
  workers:
    command: "php /var/www/app/worker.php"
    pool:
      numWorkers: 4

# Additional HTTP headers and CORS control.
headers:
  # Middleware to handle CORS requests, https://www.w3.org/TR/cors/
  cors:
    # https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Allow-Origin
    allowedOrigin: "*"

    # https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Allow-Headers
    allowedHeaders: "*"

    # https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Allow-Methods
    allowedMethods: "GET,POST,PUT,DELETE"

    # https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Allow-Credentials
    allowCredentials: true

    # https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Expose-Headers
    exposedHeaders: "Cache-Control,Content-Language,Content-Type,Expires,Last-Modified,Pragma"

    # Max allowed age in seconds
    maxAge: 600

  # Automatically add headers to every request passed to PHP.
  request:
    "Example-Request-Header": "Value"

  # Automatically add headers to every response.
  response:
    "X-Powered-By": "RoadRunner"

# static file serving. remove this section to disable static file serving.
static:
  # root directory for static file (HTTP would not serve .php and .htaccess files).
  dir:   "/var/www/app/public"

  # list of extensions for forbid for serving.
  forbid: [".php", ".htaccess"]

This adds the headers to PHP requests but for static files the headers aren't added. Is there a way to do this?

@maxbaldanza no at the moment. We also have similar feature-request #335. I'll merge these two proposals in one, and we will track the feature here. Thanks.

@mqwerty https://github.com/spiral/roadrunner/issues/335#issue-627920717

I have moved our 1.8.2 milestone to the 16 of June, and I hope I would have a time to finish all included tickets.

Thank you @48d90782 much appreciated.
Sorry for the duplicate issue

@maxbaldanza In the master now. Now in the master #345


Stake pool registry validator

cardano-cli:

Drop --tracing-off -- it was implemented with a hard-to-fix bug.
Fix error printing -- it was over-quoting.

Will get to it tomorrow, on leave today.

Ok, I think we can close this PR now.
Thanks everybody for the review!
The validator now lives in https://github.com/input-output-hk/testnet-stake-pool-registry-validator

Reopening, as this has non-validator changes that almost got lost : -)


Signed-off-by: Jussi Kukkonen<EMAIL_ADDRESS>
Lint is currently broken on develop, this should fix it.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 98.312%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1179

Relevant Lines:
1195

💛  - Coveralls

closing this for #1930 1930


Librespot fails to startup due to missing entropy

I've found that librespot under Max2play on a rpi sometimes fails to start at system boot. At least a few times, I've captured a backtrace (on a Zero W) of this behaviour, which suggests that there is insufficient entropy available in the system, causing startup to fail. Restarting it manually fixes it, though I've seen that it fails again until a few minutes later when (I guess) more entropy is available.
The actual problem is of course beyond librespot's control, but I wonder if librespot could perhaps switch to a different random generated (e.g. urandom vs random, though it might be already using getrandom which AFAIU returns random values without consuming extra entropy, provided some startup entropy is available, which probably best of both).
Alternatively, librespot could perhaps wait and retry until sufficient entropy is available? That would at least allow unattended startup to complete, even after some time.
Here's the backtrace:
thread 'main' panicked at 'could not initialize thread_rng: All entropy sources failed (permanently unavailable); cause: getrandom not ready (not ready yet); c
stack backtrace:
   0:   0x9e137c - backtrace::backtrace::libunwind::trace::hb317fd79f338e9ac
                       at /cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.29/src/backtrace/libunwind.rs:88
   1:   0x9e137c - backtrace::backtrace::trace_unsynchronized::h577e08d87958ca80
                       at /cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.29/src/backtrace/mod.rs:66
   2:   0x9e137c - std::sys_common::backtrace::_print::hbfee0f6c5053d54e
                       at src/libstd/sys_common/backtrace.rs:47
   3:   0x9e137c - std::sys_common::backtrace::print::he0aac2b05fe6a451
                       at src/libstd/sys_common/backtrace.rs:36
   4:   0x9e137c - std::panicking::default_hook::{{closure}}::ha2ef00deb6db7a83
                       at src/libstd/panicking.rs:200
   5:   0x9e0f2c - std::panicking::default_hook::h641d7e1cec244c78
                       at src/libstd/panicking.rs:214
   6:   0x9e1b40 - std::panicking::rust_panic_with_hook::h4043fa8d29430a82
                       at src/libstd/panicking.rs:477
   7:   0x9e1704 - std::panicking::continue_panic_fmt::h69e00c7989848347
                       at src/libstd/panicking.rs:384
   8:   0x9e1654 - std::panicking::begin_panic_fmt::h49ff18ea78dc8817
                       at src/libstd/panicking.rs:339
   9:   0x9364c8 - rand::rngs::thread::THREAD_RNG_KEY::__init::{{closure}}::heeae17905a9999de
  10:   0x936260 - std::thread::local::lazy::LazyKeyInner<T>::initialize::h635d7ef8d9fcd6be
  11:   0x936f08 - std::thread::local::fast::Key<T>::try_initialize::hd4fc2756117a8f1a
  12:   0x936e94 - rand::rngs::thread::thread_rng::h471381a5136d3362
  13:   0x5215dc - librespot_connect::discovery::discovery::h45c1c14a868774ea
  14:   0x4f6a5c - librespot::main::h17b86eb414fa277e
  15:   0x4d13dc - std::rt::lang_start::{{closure}}::he764af215f6d223f
  16:   0x9e1568 - std::rt::lang_start_internal::{{closure}}::hfac715f2e0a14136
                       at src/libstd/rt.rs:49
  17:   0x9e1568 - std::panicking::try::do_call::h5bd3d572724ac2e1
                       at src/libstd/panicking.rs:296
  18:   0x9e8b18 - __rust_maybe_catch_panic
                       at src/libpanic_unwind/lib.rs:82
  19:   0x9e1fd0 - std::panicking::try::h3203ccbd3c7c13af
                       at src/libstd/panicking.rs:275
  20:   0x9e1fd0 - std::panic::catch_unwind::hd9cff17009151b9a
                       at src/libstd/panic.rs:394
  21:   0x9e1fd0 - std::rt::lang_start_internal::hab130c51c66092b9
                       at src/libstd/rt.rs:48
  22:   0x4f794c - main
  23: 0xb6e58678 - __libc_start_main

One more note, this was with a self-compiled git master version (https://github.com/librespot-org/librespot/commit/4e3576ba7c6146cf68e1953daeec929d619b26b1).

The error itself seems completely contradictory:
thread 'main' panicked at 'could not initialize thread_rng: All entropy sources failed (permanently unavailable); cause: getrandom not ready (not ready yet); c
The version you link doesn't have getrandom in Cargo.lock so must have been making the syscall from the rand crate. I suspect the use of the cross-platform getrandom crate, as rand does now will improve things.
As far as I can tell getrandom is supposed to block until it can get the requested bytes. And should only panic if it can't ever return random bytes - or is interrupted by the OS.
Have you seen this issue with a newer build of librespot?

Have you seen this issue with a newer build of librespot?

I have not been using librespot since I reported this (I needed it for a specific event, I'm not using it daily currently).


Set version 0.8.0 to main

Features

Set version 0.8.0 to main

Feature Docs

Influence

Result

Other

LGTM


Improve codegen

Currently the generated virtual code is hard to read due for lack of indentations. I'd like to add some indentation to make the output more readable.
If you don't have much time on this, I can contribute.

Thanks for the suggestion, but I'd prefer to avoid making codegen more complicated.
In order to debug TS, I suggest you use the "Volar (Debug): Write Virtual Files" command to write virtual files to the project, and format the written virtual file.
Please note that you need to disable "TypeScirpt Vue Plugin", and in current version (1.8.0) you also need to add __VLS_types to tsconfig include option.


Sidebar overlaps with body content

Describe the bug
I've noticed that the right sidebar sometimes partially overlaps with the body content.
To Reproduce
Visit this page and scroll down to almost bottom.
Expected behavior
There should be no overlaps.
Screenshots

There has been a number of CSS improvements since this issue was reported and I can no longer reproduce this issue. Feel free to reopen if you have another reproduction


Toolchain isn't compatible with playgrounds

Hi,
I installed pre-built package for Xcode as per info here: https://github.com/tensorflow/swift/blob/master/Installation.md#pre-built-packages
Has anyone faced the issue highlighted in 👇:

Please note I'm using Xcode9.2.

Try restarting Xcode.

you should notice that the swift for tensorflow is suitable only in Mac playground. you can check your playground whether that is for macOS.

Playground for macOS does the trick. Thanks @kfchyc. 👍


Trimming metadata

Sundry changes that together shave about half a megabyte off the dylibs in a relwithdebinfo build.

Nice!
65,536 generic parameters ought to be enough for anybody, right?

@swift-ci Please smoke test

Is a variable size ULEB style encoding reasonable here, or do you want fixed sizes to allow indexing across these records?

The old data structures in Swift 4 and before had the same limit and nobody seemed to notice. These sizes aren’t particularly speed sensitive so we could reserve space for larger argument counts if we really needed to.

I don't care about > 64K.  I was suggestion variable size so that the vastly most common case only uses one byte :)

That'd be clever. Going from 32 -> 16 bits only really saved 4KB across the stdlib and overlays, so we'd see at most another 2KB benefit in return.

@swift-ci Please smoke test


[ISSUE #2523]support pushConsumer get serviceState

Make sure set the target branch to develop
What is the purpose of the change
#2523
Brief changelog
1.In DefaultMQPushConsumerImpl,change makeSureStateOK from private to public.
2.In DefaultMQPushConsumer, add a method makeSureStateOK.
Verifying this change
XXXX
Follow this checklist to help us incorporate your contribution quickly and easily. Notice, it would be helpful if you could finish the following 5 checklist(the last one is not necessary)before request the community to review your PR.

[x] Make sure there is a Github issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a Github issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[x] Format the pull request title like [ISSUE #123] Fix UnknownException when host config not exist. Each commit in the pull request should have a meaningful subject line and body.
[x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[x] Write necessary unit-test(over 80% coverage) to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add integration-test in test module.
[x] Run mvn -B clean apache-rat:check findbugs:findbugs checkstyle:checkstyle to make sure basic checks pass. Run mvn clean install -DskipITs to make sure unit-test pass. Run mvn clean test-compile failsafe:integration-test  to make sure integration-test pass.
[x] If this contribution is large, please file an Apache Individual Contributor License Agreement.

Coverage decreased (-0.1%) to 51.795% when pulling 3a6831b15611a33337a64cbf127a90324cdf9b8e on wyf224:feature-consumer into 0239421fa59b67c423cf9fcabf5cd6edda0c2076 on apache:develop.

Codecov Report

Merging #2524 (3a6831b) into develop (0239421) will increase coverage by 0.06%.
The diff coverage is 0.00%.

@@              Coverage Diff              @@
##             develop    #2524      +/-   ##
=============================================
+ Coverage      45.95%   46.01%   +0.06%
- Complexity      4316     4320       +4
=============================================
  Files            547      547
  Lines          36236    36238       +2
  Branches        4808     4808
=============================================
+ Hits           16651    16675      +24
+ Misses         17497    17470      -27
- Partials        2088     2093       +5

Impacted Files
Coverage Δ
Complexity Δ

...ocketmq/client/consumer/DefaultMQPushConsumer.java
54.00% <0.00%> (-0.55%)
46.00 <0.00> (ø)

...lient/impl/consumer/DefaultMQPushConsumerImpl.java
8.86% <ø> (ø)
11.00 <0.00> (ø)

...he/rocketmq/client/impl/consumer/ProcessQueue.java
58.60% <0.00%> (-3.26%)
31.00% <0.00%> (-1.00%)

...ava/org/apache/rocketmq/filter/util/BitsArray.java
58.11% <0.00%> (-1.71%)
29.00% <0.00%> (-1.00%)

...org/apache/rocketmq/common/stats/StatsItemSet.java
41.79% <0.00%> (-1.50%)
16.00% <0.00%> (-1.00%)

...nt/impl/consumer/ConsumeMessageOrderlyService.java
42.96% <0.00%> (+0.36%)
19.00% <0.00%> (+3.00%)

...ava/org/apache/rocketmq/store/ha/HAConnection.java
75.00% <0.00%> (+0.46%)
5.00% <0.00%> (ø%)

...a/org/apache/rocketmq/store/StoreStatsService.java
29.50% <0.00%> (+0.65%)
26.00% <0.00%> (+1.00%)

...rocketmq/client/impl/factory/MQClientInstance.java
50.14% <0.00%> (+0.73%)
90.00% <0.00%> (+1.00%)

...e/rocketmq/client/impl/consumer/RebalanceImpl.java
54.58% <0.00%> (+7.96%)
35.00% <0.00%> (+2.00%)

... and 1 more

Continue to review full report at Codecov.

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


add TextBox for Tag

Adding a tag with textbox is much better than a button
we can add tags with ; or space
also The tag that is selected must also have the option for unselected

I hope you also consider this feature when rewriting the tag panel (tag container)
so I close this PR

I hope you also consider this feature when rewriting the tag panel (tag container)
so I close this PR

fine


Add timeout and print response when status fails

As @loicbachelot suggests:

Add a timeout as exit condition in (2 minutes should be enough):

https://github.com/CMCC-Foundation/bluecloud-mockup_method/blob/fc9efaa1ec9e3c224a337dfbad4468d442b3471f/download/wekeo/functions.py#L205

add 'json.loads(response.text)['message']' to log when the status is fail

2. add 'json.loads(response.text)['message']' to log when the status is fail

I think it's better to raise an exception that reads the error message from json.loads(response.text)['message'], the exception will be caught by the try-catch in the mockup that prints the message and adds it in the log file

2. add 'json.loads(response.text)['message']' to log when the status is fail

I think it's better to raise an exception that reads the error message from json.loads(response.text)['message'], the exception will be caught by the try-catch in the mockup that prints the message and adds it in the log file

Yes, that seems like a perfect solution! The wekeo error message is clear enough to be used as-is.
In the case the request fails, what would be the ideal handling? Exit the method and still create all the output files?

In the case the request fails, what would be the ideal handling? Exit the method and still create all the output files?

Yes, we use this approach:
When there is an error, the method creates all output files (also empty files are ok), then put the right error code in the json and then exit correctly.
Then, to know the result of the method you have to read the error.code in json file.
If the error.code = 0 it means that the execution is ok, otherwise the code indicates the type of error (for example -1 indicates a problem with the format of input_parameters string, -2 an error in download procedure and so on)

With the last commit I added a check if the status is failed, in that case the code raise an Exception try to print the message received.
I added also a 2 minute timeout.
Let me know it is all ok

After the 2 fixes, everything is working for me both using a key or the proxy. Thanks!


Black window after update

On two machines, both running Debian Bullseye and Gnome shell, the tor browser windows (main window, and the startup window when the connection to the tor network is made) are solid black. Only the outline and the window's title is visible (i.e. only the controls, none of the content).
Launching from command line gives no error messages
user@machine:~$ torbrowser-launcher
Tor Browser Launcher
By Micah Lee, licensed under MIT
version 0.3.2
https://github.com/micahflee/torbrowser-launcher
Launching Tor Browser.
Running /home/user/.local/share/torbrowser/tbb/x86_64/tor-browser_en-US/start-tor-browser.desktop
Launching './Browser/start-tor-browser --detach'...
user@machine:~$

The issue appeared after updating tor browser from within tor browser, without any OS update at the same time.
Edit:
The problem seems to be with torbrowser-launcher, and not with torb-browser, because the most recent tor browser from torproject.org works fine.

Till Junge:

On two machines, both running Debian Bullseye and Gnome shell, the tor browser windows (main window, and the startup window when the connection to the tor network is made) are solid black. Only the outline and the window's title is visible (i.e. only the controls, none of the content).

This is tracked as https://bugs.debian.org/942901 in Debian.
I believe this was fixed upstream with https://github.com/micahflee/torbrowser-launcher/pull/426.

@intrigeri Thanks!

the same error happens to me both in the stable version and in the current alpha version, and edited the pull file by putting the same thing and nothing remains black when starting

@carlosnewmusic run sudo service apparmor force-reload, in general you need to do that every time you edit an apparmor file


Refine typography. #287.

Ticket
Closes #287 .
Reviewers
@MillenniumFalconMechanic .
Changes

Updated theme with responsive typography and any site specific typography overrides.
Modified theme from a constant to a function with parameter customTheme.
Removed any unnecessary reference to colour 'ink' in "touched" components.
Added Din font.

Outstanding

To be able to "switch" between site configs for SB.

@MillenniumFalconMechanic new fonts downloaded for both HCA and AnVIL build and the typography overrides for HCA work as expected.


Fix ignore functionality (especially for 'version' rules)

Fixes #130
By extending the SemanticVersion class with rich comparison magic methods, the ignore rules for versions can be more easily checked.
An extended test ensures some more specific ignore rules are respected as intended.
Dependency version ranges are still not properly respected.
For example if >=1.0.0,<2 is specified, but the latest version is 2.3.1, then the result (with no ignore rules) will be >=2.3.1,<2, which makes no sense.
This should be remedied in another issue/PR.
Edit: This issue has now been reported in #141

This looks good although update_deps.py is (in my opinion) too long to understand and review efficiently. Perhaps it could be worth to clarify its central operational loop and move the logic functions into one or more separate files?

Completely fair.
I'll create an issue to follow-up on this, as I think it's out-of-scope for the current PR.

Also, Codecov generates a number of warnings about non-covered lines. Do these need to be addressed before merging?

Right. I'll have a look at the lot of them and see how easy it would be to check some of the non-covered lines.
The one that immediately sprung out at me was that the __hash__ function was not checked. Perhaps it can be removed altogether...

I think I got most of the codecov messages now. Unfortunately, it seems codecov has not uploaded the checks for the latest commit. But as far as I know, there is only one left, which concerns a < resolve based on pre-release information. I think that's fine, to be honest.


Cannot interact with villagers

I have found several structures with villagers in them, but none of the villagers will interact with me. I've tried right clicking on them to talk to them but nothing happens. Am I doing something wrong?

No you are doint nothing wrong.
Interacting with villagers is simply not implemented yet :)

With VSQuest there is now the possibility to interact with villagers


esp8266 crash when callback fires too much

Hi all,
I'm currently using mqtt client (Pubsubclient lib) on my ESP8266 and i have installed a local mosquitto broker on my PC.
ESP still work fine until i try to send many commands rapidly from my app (3 commands each time). The callback function fires continuously cause esp8266 hangout then reset.
Can someone help me with this please?
Thanks.

Try calling client.loop at the end of your callback function. That will allow the code to continue to service the network if there's more work to be done.

I tried to add client.loop at the end of my callback func, but nothing changed. After several time receiving command, it crashed.

OK, i added a list to queue commands then handle it later. It is a bit slow but at least no more hang out. Thanks.


[model] reference model for consensus calling

Add a reference model for DL polishing to VW reference models.

The reference RNN model was added in #120 . Closing.


Adding Treeview Widget

Hello Jakob,
Thanks for your hard work on this project, I often think about ways I could use it in my development efforts. Anyway, I've added a Treeview widget, demo, and tests to a fork of your repo under keithknott26/termdash.  I felt I should contribute something hopefully useful to this effort.
Let me know if you'd like me to make any changes, the test coverage is not ideal given I wasn't too familiar with writing them for a UI type application. Mutex locks are in place so there are currently no race conditions as far as I know. Mouse and keyboard integration are included.
Cheers,
Keith Knott

Hello @keithknott26 and thank you, this looks great! Thank you for adding a new widget and including solid test coverage. It will take me a bit to review this. I will get back to you if I see any points we need to address.

I just had some time to play with the demo, the treeview widget looks really cool, thank you @keithknott26!
Going to start reviewing it shortly.

@keithknott26, while I am reviewing this - do you want to update this PR adding a screenshot of this widget and its capabilities to the main README? It doesn't have to be a moving gif like the other ones, but can be if you want to.

Thanks!
I've incorporated your suggestions and updated the following:
Treeview to TreeView
Added missing comments to types
Changed node to tv
Updates to mutex locking
Added more tests
README.md file was updated with an animated gif
Let me know if you think anything else should be updated.
Cheers,
Keith


Bevy game occasionally crashes VS Code after being closed if it was launched from VS Code integrated terminal

Bevy version
0.13.2
[Optional] Relevant system information
OS: Windows 10
VS Code version: 1.89.1
AdapterInfo { name: "NVIDIA GeForce RTX 4050 Laptop GPU", vendor: 4318, device: 10465, device_type: DiscreteGpu, driver: "NVIDIA", driver_info: "552.44", backend: Vulkan }

What you did
I usually launch my games from integrated VS Code terminal with cargo run.
What went wrong
Upon closure of the game VS Code program starts to increase its CPU usage and RAM consumption until it crashes with "Out Of Memory" error. I haven't found any additional information in VS Code logs. There is only that "Out Of Memory" message. This crash happens occasionally once per many launches and I can not reliably reproduce it. The only thing I can tell is that it doesn't matter if the game is run the first time after it's recompiled or not.
cargo build never fails, the crash happens only after the app was closed.
I'm sorry I cannot provide any additional information. This issue might not even be related to Bevy but it is the only app that ever caused it. I will provide any additional information that is necessary and can be gathered.
Additional information
I use dynamic_linking feature and opt-level = 3 package-specific override. Linking is done with lld. I followed Bevy Setup guide.

Encountered a VS Code crash after launching the game from external terminal. It required way more tries but I think at that point it's not on bevy.


Multiplication result converted to larger type

To address the potential overflow issue in the multiplication of w * h * (bit16 ? 8 : 4) and casting it to size_t, I had perform the multiplication using size_t directly to avoid the overflow.
patch link: https://issuetracker.google.com/issues/322327444
Code modification ensures that the multiplication is done using the larger integer type (size_t) before casting the result to unsigned char*. Using size_t for the multiplication helps prevent overflow issues, as size_t is typically large enough to accommodate the size of memory in the system.

Hi @lvandeve Could You Please Review Above PR
Thanks & Regards

Hi @enh-google Could You Please Review Above PR
Thanks & Regards

(i only maintain Android's copy of this code, and we only use this file on the host, where we don't enable intsan anyway. i've forwarded this -- and the bug -- to the real zopfli maintainers internally though.)

Hi @enh-google Okay Thanks 👍

Hi @lvandeve Could You Please Review Above PR
Thanks & Regards

I pulled https://github.com/google/zopfli/pull/198 which does the same, so this now has a conflict. Does https://github.com/google/zopfli/pull/198 solve it?

I pulled #198 which does the same, so this now has a conflict. Does #198 solve it?
Hi
Yes You are Right  both are same
My mistake
Thanks


Comment on WebServer/qodly-studio.md (20-R3)

Qodly Studio can be used offline.
But we could comment that a couple of features are not available in Qodly Studio for 4D without an internet access:

Templates: the template library will be empty withou internet connection
UI tips

I added this paragraph:
https://doc4d.github.io/docs/WebServer/qodly-studio/#offline-use


Fix missing ignore section in bower.json

This fixes:
bower invalid-meta  skatejs is missing "ignore" entry in bower.json
and also prevents downloading unnecessary files & folders

We could also think about excluding docs and README.md if a bower install is considered being a production install.

@joscha thanks for the PR! Yeah, I think all we really need to expose in a bower install is dist/, lib/ and src/.

@treshugart cool, I'll add docs and README.md to the commit. One rebase coming up.


Do we want to add an example in doc showing how to Deploy a Test Workload

Description
@thesteve0
Do we want to add an example in doc showing how to Deploy a Test Workload.
If so do we want to reuse one of the ones listed here or provide something new
Here is a simple example that @thesteve0 tested that works:
https://docs.vmware.com/en/VMware-vSphere/7.0/vmware-vsphere-with-tanzu/GUID-5DFC347C-694B-4288-96DA-EAEB5818D951.html
Here is another example that needs a load balancer
https://docs.vmware.com/en/VMware-Tanzu-Kubernetes-Grid/1.4/vmware-tanzu-kubernetes-grid-14/GUID-tanzu-k8s-clusters-tutorial.html
Location

Additional Context

Sounds great. Can we introduce a Guide for Deploying a sample app and link it at the end of our getting started guide.
Something like "Next Steps", perhaps?

I see it as a test that your workload or unmanaged cluster is actually working.

This won't happen this release. Sorry ya'll. Help-wanted still out there. For now, moving to v0.12.0

@thesteve0 - when you tested this: https://docs.vmware.com/en/VMware-vSphere/7.0/vmware-vsphere-with-tanzu/GUID-5DFC347C-694B-4288-96DA-EAEB5818D951.html
Did you test on vSphere? the prerequisite section links to vsphere doc which references the supervisor cluster. Is this prereq required, or can this example work on the other cloud providers?

Sorry - just saw this. Did not test on anything but AWS and unmanaged


vueify can not support async components pattern

Hi, I can use following pattern without using vueify toolchain:
Vue.component('alerts',function(resolve, reject) {
    this.$http.get('/alerts').then(
        function (resp) {
            resolve({
	    props: ['list'],
            template: '#alerts-template'
	});
     });
})

but after using vueif pattern,
var Vue = require('vue');
Vue.use(require('vue-resource'));
import Alerts from './components/Alerts.vue';
new Vue({
	el: '#app',
components: { Alerts: Alerts },
data: {
    alerts: []
}
}
});

always tell me
Cannot set property 'template' of undefined

Is this a bug of vueify tool or the manner i use is wrong?

You cannot use async format inside a *.vue component. The bundler you are using (Browserify/Webpack) needs to know how to split them.
http://router.vuejs.org/zh-cn/lazy.html


Add option to configure multiple PostgreSQL instances

Summary
This PR enables service users to configure multi-instance Postgres clusters as well as allows them to choose the replication mode. We don't expose  role or groups of stackgres as it introduces complexity and doesn't really provide any benefits for clusters up to three nodes that we support.
Further this PR removes two possible footguns

We automatically set the replication mode to async if the user only requests a single instance. Stackgres will simply fail if one chooses sync or strict-sync with only one replica
We automatically set the syncInstances to instances - 1 .  There is really no point in setting this to anything else for clusters up to three nodes and misconfiguring this can lead to fail-over issues.

Checklist

[x] Categorize the PR by setting a good title and adding one of the labels:
bug, enhancement, documentation, change, breaking, dependency
as they show up in the changelog
[x] Update tests.

One thing that just came to my mind: we're reducing the memory for the cluster-controller container. Did you notice any issues regarding that? I assume the cluster controller probably has a bit more load now that it has to manage more nodes.

I didn't notice any issues, but good input. I'll double check that it doesn't use too much memory before deploying this.


Running into limits with describes

We are running into describe limits for fields with more than 100 picklists, any suggestions on how to deal with that?

As of the Summer '14 release the describe limits were removed so this should no longer be a problem.
From the release notes:

Limits for all Apex describe calls have been removed for all API versions. Describe calls include describes for sObjects, fields, field sets, child relationships, picklists, and record types.
You’re no longer limited to describing 100 objects or to executing 100 describe statements.

Feel free to reopen the issue if you're still seeing a problem.


fix: minor typo fixes and formatting improvements

- What I did
Fix a couple of minor typos, and make code block indentations consistent.
- How I did it
See above.
- How to verify it
Proofreading is appreciated.
- Description for the changelog

A few minor typo fixes/formatting improvements.

Thanks @syncom


Try to fix api validator

What does the pull request do?

What is the current behavior?

What is the updated/expected behavior with this PR?

How was the solution implemented (if it's not obvious)?

Checklist

[ ] Added unit tests (if possible)?
[ ] Added XML documentation to any related classes?
[ ] Consider submitting a PR to https://github.com/AvaloniaUI/avalonia-docs with user documentation

Breaking changes

Obsoletions / Deprecations

Fixed issues

You can test this PR using the following package version. 11.0.999-cibuild0040697-beta. (feed url: https://nuget-feed-all.avaloniaui.net/v3/index.json) [PRBUILDID]

You can test this PR using the following package version. 11.0.999-cibuild0040723-beta. (feed url: https://nuget-feed-all.avaloniaui.net/v3/index.json) [PRBUILDID]


Improvement/docker latest tag

Based on that we should probably go with a different approach: https://vsupalov.com/docker-latest-tag/


Lab211

created s3 bucket using the cli

Good work! I like the use of Session in your script instead of just opening a client (which I often do). For short-lived scripts there isn't really a "right" answer, but for frequently-invoked Lambdas it's often good to open a Session like you did. There's some good discussion here: https://twitter.com/ben11kehoe/status/1341378055319633920
And here is some Stelligent discussion about the topic as well: https://stelligent.slack.com/archives/C0AEFD4TB/p1605539751111200

LGTM!


Create pos file directory if it doesn't exist

We recently encountered an issue where the subdirectory the pos_file should be written to didn't exist, causing the in_tail plugin to emit an exception and crash fluentd, resulting in a crash loop. The process had permission to write to the parent directory so it could have easily created the directory and avoided an outage. This change adds a mkdir_p call to create the directory if it detects that the directory the pos_file is in doesn't exist.
/cc @repeatedly

Thanks!


Section 508 compliance

Tony Grecius has completed a section 508 scan of the Infirmary ReST API.
Why a ReST API needs a 508 scan is beyond me, but welcome to the US Government.
Here's the report:
Infirmary report.docx
Let Tony know when this is fixed

Re-scan passes


python312Packages.flax: 0.8.5 -> 0.9.0

Description of changes
Changelog: https://github.com/google/flax/releases/tag/v0.9.0
cc @ndl

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

Result of nixpkgs-review pr 342970 run on x86_64-darwin 1

4 packages marked as broken and skipped:

python311Packages.treescope
python311Packages.treescope.dist
python312Packages.treescope
python312Packages.treescope.dist

Result of nixpkgs-review pr 342970 run on aarch64-darwin 1

20 packages marked as broken and skipped:

python311Packages.dalle-mini
python311Packages.dalle-mini.dist
python311Packages.distrax
python311Packages.distrax.dist
python311Packages.dm-haiku
python311Packages.dm-haiku.dist
python311Packages.elegy
python311Packages.elegy.dist
python311Packages.evosax
python311Packages.evosax.dist
python311Packages.flax
python311Packages.flax.dist
python311Packages.flowmc
python311Packages.flowmc.dist
python311Packages.rlax
python311Packages.rlax.dist
python311Packages.treex
python311Packages.treex.dist
python311Packages.vqgan-jax
python311Packages.vqgan-jax.dist

4 packages built:

python311Packages.treescope
python311Packages.treescope.dist
python312Packages.treescope
python312Packages.treescope.dist

Result of nixpkgs-review pr 342970 run on aarch64-linux 1

4 packages built:

python311Packages.treescope
python311Packages.treescope.dist
python312Packages.treescope
python312Packages.treescope.dist

Result of nixpkgs-review pr 342970 run on x86_64-linux 1

8 packages marked as broken and skipped:

python311Packages.distrax
python311Packages.distrax.dist
python311Packages.elegy
python311Packages.elegy.dist
python311Packages.rlax
python311Packages.rlax.dist
python311Packages.treex
python311Packages.treex.dist

16 packages built:

python311Packages.dalle-mini
python311Packages.dalle-mini.dist
python311Packages.dm-haiku
python311Packages.dm-haiku.dist
python311Packages.evosax
python311Packages.evosax.dist
python311Packages.flax
python311Packages.flax.dist
python311Packages.flowmc
python311Packages.flowmc.dist
python311Packages.treescope
python311Packages.treescope.dist
python311Packages.vqgan-jax
python311Packages.vqgan-jax.dist
python312Packages.treescope
python312Packages.treescope.dist


Set default indent size for *.{cpp,hpp,c,h,mm} to 4 spaces

GitHub respect the indent size set by an .editorconfig file in the repository. This will make working with diffs a little bit easier for the majority of the PRs, as tabs will no longer be set to their default value of tabs of 8 spaces.
I set the style to tabs, and spaces to 4, which is currently the standard for the project for those files.
Here's an example of the tabs in diff currently (set as 8 spaces), it actively hinders the ability to review well PRs as so much whitespace is added.
Here's how it currently look on Chrome:

There's a bug on Firefox that makes it 16 characters!

Finally, replace tabs with spaces and there will be no more problems with formatting :)


[MNT] Remove keras bound

Reference Issues/PRs
fixes #1724
What does this implement/fix? Explain your changes.
Removes the version bound on keras (if CI passes).

so good news keras fixed the loading issue and they are waiting for it to be released in keras 3.4.2 https://github.com/keras-team/keras/issues/19976
first issue that mentioned it: https://github.com/keras-team/keras/issues/19921
first pr that tried to fix it: https://github.com/keras-team/keras/pull/19924
second pr that tried to fix it: https://github.com/keras-team/keras/pull/19927
and now the new release is pr is still open once its in main we can re-run your pr on keras bound

can we try this now @MatthewMiddlehurst  ?

feel free to make any changes you want


tf.enable_eager_execution() bug?

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow):
OS Platform and Distribution (e.g., Linux Ubuntu 16.04):window10
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device:
TensorFlow installed from (source or binary): source
TensorFlow version (use command below): 1.10
Python version:3.6
Bazel version (if compiling from source):
GCC/Compiler version (if compiling from source):
CUDA/cuDNN version:
GPU model and memory:
Exact command to reproduce:

Describe the problem
i used the tf.enable_eager_execution() and create InceptionResNetV2 mode will be error and only InceptionResNetV2 have. I need use  tf.enable_eager_execution() can't without.
how to fix it?
Source code / logs
import tensorflow as tf
tf.enable_eager_execution()
image_model =tf.keras.applications.InceptionResNetV2(include_top=False, weights='imagenet')
--error---
TypeError                                 Traceback (most recent call last)
 in ()
----> 1 image_model =tf.keras.applications.InceptionResNetV2(include_top=False, weights='imagenet')
D:\anaconda\lib\site-packages\tensorflow\python\keras\applications\inception_resnet_v2.py in InceptionResNetV2(include_top, weights, input_tensor, input_shape, pooling, classes)
304   for block_idx in range(1, 11):
305     x = inception_resnet_block(
--> 306         x, scale=0.17, block_type='block35', block_idx=block_idx)
307
308   # Mixed 6a (Reduction-A block): 17 x 17 x 1088
D:\anaconda\lib\site-packages\tensorflow\python\keras\applications\inception_resnet_v2.py in inception_resnet_block(x, scale, block_type, block_idx, activation)
187       output_shape=K.int_shape(x)[1:],
188       arguments={'scale': scale},
--> 189       name=block_name)([x, up])
190   if activation is not None:
191     x = Activation(activation, name=block_name + '_ac')(x)
D:\anaconda\lib\site-packages\tensorflow\python\keras\engine\base_layer.py in call(self, inputs, *args, **kwargs)
745           input_shapes = nest.map_structure(lambda x: x.shape, inputs)
746
--> 747         output_shapes = self.compute_output_shape(input_shapes)
748         output_shapes = nest.flatten(output_shapes)
749         outputs = [
D:\anaconda\lib\site-packages\tensorflow\python\keras\layers\core.py in compute_output_shape(self, input_shape)
678
679   def compute_output_shape(self, input_shape):
--> 680     input_shape = tuple(tensor_shape.TensorShape(input_shape).as_list())
681
682     if self._output_shape is None:
D:\anaconda\lib\site-packages\tensorflow\python\framework\tensor_shape.py in init(self, dims)
539       else:
540         # Got a list of dimensions
--> 541         self._dims = [as_dimension(d) for d in dims_iter]
542     self._ndims = None
543
D:\anaconda\lib\site-packages\tensorflow\python\framework\tensor_shape.py in (.0)
539       else:
540         # Got a list of dimensions
--> 541         self._dims = [as_dimension(d) for d in dims_iter]
542     self._ndims = None
543
D:\anaconda\lib\site-packages\tensorflow\python\framework\tensor_shape.py in as_dimension(value)
480     return value
481   else:
--> 482     return Dimension(value)
483
484
D:\anaconda\lib\site-packages\tensorflow\python\framework\tensor_shape.py in init(self, value)
35       raise TypeError("Cannot convert %s to Dimension" % value)
36     else:
---> 37       self._value = int(value)
38       if (not isinstance(value, compat.bytes_or_text_types) and
39           self._value != value):
TypeError: int() argument must be a string, a bytes-like object or a number, not 'TensorShape'

@Q82822 I am able to reproduce with 1.10 but not the latest nightly build. Can you try with tf-nightly and see if the issue has been resolved?

it is still not work
have the same problem

I am working on a Linux machine. With tf-nightly (1.11.0-dev20180826) it seems to be working:
# python
Python 2.7.12 (default, Dec  4 2017, 14:50:18)
[GCC 5.4.0 20160609] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import tensorflow as tf
>>> tf.VERSION
'1.11.0-dev20180826'
>>> tf.enable_eager_execution()
>>> image_model =tf.keras.applications.InceptionResNetV2(include_top=False, weights='imagenet')
2018-08-26 17:47:03.515629: I tensorflow/core/platform/cpu_feature_guard.cc:141] Your CPU supports instructions that this TensorFlow binary was not compiled to use: AVX2 FMA
Downloading data from https://github.com/fchollet/deep-learning-models/releases/download/v0.7/inception_resnet_v2_weights_tf_dim_ordering_tf_kernels_notop.h5
219062272/219055592 [==============================] - 2s 0us/step
219070464/219055592 [==============================] - 2s 0us/step
>>>

@Q82822 Which version are you using? Can you check:
>>> import tensorflow as tf
>>> tf.VERSION
'1.11.0-dev20180826'

my tensorflow version is 1.10 and  CUDA/cuDNN version: 9.2/7.1
>>> import tensorflow as tf
>>> print(tf.__version__)
1.10.1

@Q82822 Can you uninstall tensorflow and reinstall with pip install tf-nightly to get the nightly build?

very appreciate you help. i can build mode now

@yongtang thank you for helping out!
@Q82822 closing since it seems that you have a solution.


Re-adjust WalletListOptions dropdown vertical position to prevent cutoff

The purpose of this task is to prevent the WalletListOptions dropdown menu from going off the screen when the wallet item is toward the bottom of the screen.
Asana Task: https://app.asana.com/0/361770107085503/553039148202323/f

@thehobbit85 Thank you for clarification. Changes have been made.


interop_matrix: add gcloud debug info

To debug a gcloud docker pull authentication flake.

Known failures:
https://github.com/grpc/grpc/issues/17794
https://github.com/grpc/grpc/issues/17851
https://github.com/grpc/grpc/issues/17335


[Bug] JDBC Catalog column data-type[tinyint(1)] mapping wrong to [boolean]

Search before asking

[X] I had searched in the issues and found no similar issues.

Version
1.2.6-rc03
What's Wrong?
the mysql ddl
CREATE TABLE `table1` (
`id` int NOT NULL AUTO_INCREMENT,
`type` tinyint(1) NOT NULL COMMENT 'type [1,2,3]'
PRIMARY KEY (`id`) USING BTREE
) ENGINE = InnoDB AUTO_INCREMENT = 1 DEFAULT CHARSET = utf8mb3 COMMENT = ''

show create table through doris jdbc catalog
show create table mysql_catalog.db1.table1;
-- result as below
CREATE TABLE `table1` (
  `id` int(11) NOT NULL,
  `type` boolean NOT NULL COMMENT 'type [1,2,3]'
) ENGINE=JDBC_EXTERNAL_TABLE;

The tinyint(1) become boolean. And the query result is also wrong.
query on mysql
select distinct type from table1;
-- result is 2

query on doris jdbc catalog
select distinct type from mysql_catalog.db1.table1;
-- result is 1

What You Expected?
jdbc catalog
As the docs describe, the mysql [tinyint] should be mapping to doris [tinyint].
The tinyint(1) should be mapping to doris [tinyint] too.Then the query result wouldn't be wrong.
How to Reproduce?
No response
Anything Else?
I hope this can be fixed on 1.2.x version.
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

It's fix by https://github.com/apache/doris/pull/22091


how to use .yaml files

LatentDiffusion: Running in eps-prediction mode
DiffusionWrapper has 859.52 M params.
Downloading100% 1.71G/1.71G [00:29<00:00, 57.5MB/s]
Loading weights [4bdfc29c] from /content/gdrive/MyDrive/sd/stable-diffusion-webui/models/Stable-diffusion/v2-1_768-ema-pruned.ckpt
loading stable diffusion model: RuntimeError
Traceback (most recent call last):
File "/content/gdrive/MyDrive/sd/stable-diffusion-webui/webui.py", line 66, in initialize
modules.sd_models.load_model()
File "/content/gdrive/MyDrive/sd/stable-diffusion-webui/modules/sd_models.py", line 321, in load_model
load_model_weights(sd_model, checkpoint_info)
File "/content/gdrive/MyDrive/sd/stable-diffusion-webui/modules/sd_models.py", line 203, in load_model_weights
model.load_state_dict(sd, strict=False)
File "/usr/local/lib/python3.8/dist-packages/torch/nn/modules/module.py", line 1667, in load_state_dict
raise RuntimeError('Error(s) in loading state_dict for {}:\n\t{}'.format(
RuntimeError: Error(s) in loading state_dict for LatentDiffusion:
size mismatch for model.diffusion_model.input_blocks.1.1.proj_in.weight: copying a param with shape torch.Size([320, 320]) from checkpoint, the shape in current model is torch.Size([320, 320, 1, 1]).
size mismatch for model.diffusion_model.input_blocks.1.1.transformer_blocks.0.attn2.to_k.weight: copying a param with shape torch.Size([320, 1024]) from checkpoint, the shape in current model is torch.Size([320, 768]).
size mismatch for model.diffusion_model.input_blocks.1.1.transformer_blocks.0.attn2.to_v.weight: copying a param with shape torch.Size([320, 1024]) from checkpoint, the shape in current model is torch.Size([320, 768]).
size mismatch for model.diffusion_model.input_blocks.1.1.proj_out.weight: copying a param with shape torch.Size([320, 320]) from checkpoint, the shape in current model is torch.Size([320, 320, 1, 1]).
size mismatch for model.diffusion_model.input_blocks.2.1.proj_in.weight: copying a param with shape torch.Size([320, 320]) from checkpoint, the shape in current model is torch.Size([320, 320, 1, 1]).
size mismatch for model.diffusion_model.input_blocks.2.1.transformer_blocks.0.attn2.to_k.weight: copying a param with shape torch.Size([320, 1024]) from checkpoint, the shape in current model is torch.Size([320, 768]).
size mismatch for model.diffusion_model.input_blocks.2.1.transformer_blocks.0.attn2.to_v.weight: copying a param with shape torch.Size([320, 1024]) from checkpoint, the shape in current model is torch.Size([320, 768]).
size mismatch for model.diffusion_model.input_blocks.2.1.proj_out.weight: copying a param with shape torch.Size([320, 320]) from checkpoint, the shape in current model is torch.Size([320, 320, 1, 1]).
size mismatch for model.diffusion_model.input_blocks.4.1.proj_in.weight: copying a param with shape torch.Size([640, 640]) from checkpoint, the shape in current model is torch.Size([640, 640, 1, 1]).
size mismatch for model.diffusion_model.input_blocks.4.1.transformer_blocks.0.attn2.to_k.weight: copying a param with shape torch.Size([640, 1024]) from checkpoint, the shape in current model is torch.Size([640, 768]).
size mismatch for model.diffusion_model.input_blocks.4.1.transformer_blocks.0.attn2.to_v.weight: copying a param with shape torch.Size([640, 1024]) from checkpoint, the shape in current model is torch.Size([640, 768]).
size mismatch for model.diffusion_model.input_blocks.4.1.proj_out.weight: copying a param with shape torch.Size([640, 640]) from checkpoint, the shape in current model is torch.Size([640, 640, 1, 1]).
size mismatch for model.diffusion_model.input_blocks.5.1.proj_in.weight: copying a param with shape torch.Size([640, 640]) from checkpoint, the shape in current model is torch.Size([640, 640, 1, 1]).
size mismatch for model.diffusion_model.input_blocks.5.1.transformer_blocks.0.attn2.to_k.weight: copying a param with shape torch.Size([640, 1024]) from checkpoint, the shape in current model is torch.Size([640, 768]).
size mismatch for model.diffusion_model.input_blocks.5.1.transformer_blocks.0.attn2.to_v.weight: copying a param with shape torch.Size([640, 1024]) from checkpoint, the shape in current model is torch.Size([640, 768]).
size mismatch for model.diffusion_model.input_blocks.5.1.proj_out.weight: copying a param with shape torch.Size([640, 640]) from checkpoint, the shape in current model is torch.Size([640, 640, 1, 1]).
size mismatch for model.diffusion_model.input_blocks.7.1.proj_in.weight: copying a param with shape torch.Size([1280, 1280]) from checkpoint, the shape in current model is torch.Size([1280, 1280, 1, 1]).
size mismatch for model.diffusion_model.input_blocks.7.1.transformer_blocks.0.attn2.to_k.weight: copying a param with shape torch.Size([1280, 1024]) from checkpoint, the shape in current model is torch.Size([1280, 768]).
size mismatch for model.diffusion_model.input_blocks.7.1.transformer_blocks.0.attn2.to_v.weight: copying a param with shape torch.Size([1280, 1024]) from checkpoint, the shape in current model is torch.Size([1280, 768]).
size mismatch for model.diffusion_model.input_blocks.7.1.proj_out.weight: copying a param with shape torch.Size([1280, 1280]) from checkpoint, the shape in current model is torch.Size([1280, 1280, 1, 1]).
size mismatch for model.diffusion_model.input_blocks.8.1.proj_in.weight: copying a param with shape torch.Size([1280, 1280]) from checkpoint, the shape in current model is torch.Size([1280, 1280, 1, 1]).
size mismatch for model.diffusion_model.input_blocks.8.1.transformer_blocks.0.attn2.to_k.weight: copying a param with shape torch.Size([1280, 1024]) from checkpoint, the shape in current model is torch.Size([1280, 768]).
size mismatch for model.diffusion_model.input_blocks.8.1.transformer_blocks.0.attn2.to_v.weight: copying a param with shape torch.Size([1280, 1024]) from checkpoint, the shape in current model is torch.Size([1280, 768]).
size mismatch for model.diffusion_model.input_blocks.8.1.proj_out.weight: copying a param with shape torch.Size([1280, 1280]) from checkpoint, the shape in current model is torch.Size([1280, 1280, 1, 1]).
size mismatch for model.diffusion_model.middle_block.1.proj_in.weight: copying a param with shape torch.Size([1280, 1280]) from checkpoint, the shape in current model is torch.Size([1280, 1280, 1, 1]).
size mismatch for model.diffusion_model.middle_block.1.transformer_blocks.0.attn2.to_k.weight: copying a param with shape torch.Size([1280, 1024]) from checkpoint, the shape in current model is torch.Size([1280, 768]).
size mismatch for model.diffusion_model.middle_block.1.transformer_blocks.0.attn2.to_v.weight: copying a param with shape torch.Size([1280, 1024]) from checkpoint, the shape in current model is torch.Size([1280, 768]).
size mismatch for model.diffusion_model.middle_block.1.proj_out.weight: copying a param with shape torch.Size([1280, 1280]) from checkpoint, the shape in current model is torch.Size([1280, 1280, 1, 1]).
size mismatch for model.diffusion_model.output_blocks.3.1.proj_in.weight: copying a param with shape torch.Size([1280, 1280]) from checkpoint, the shape in current model is torch.Size([1280, 1280, 1, 1]).
size mismatch for model.diffusion_model.output_blocks.3.1.transformer_blocks.0.attn2.to_k.weight: copying a param with shape torch.Size([1280, 1024]) from checkpoint, the shape in current model is torch.Size([1280, 768]).
size mismatch for model.diffusion_model.output_blocks.3.1.transformer_blocks.0.attn2.to_v.weight: copying a param with shape torch.Size([1280, 1024]) from checkpoint, the shape in current model is torch.Size([1280, 768]).
size mismatch for model.diffusion_model.output_blocks.3.1.proj_out.weight: copying a param with shape torch.Size([1280, 1280]) from checkpoint, the shape in current model is torch.Size([1280, 1280, 1, 1]).
size mismatch for model.diffusion_model.output_blocks.4.1.proj_in.weight: copying a param with shape torch.Size([1280, 1280]) from checkpoint, the shape in current model is torch.Size([1280, 1280, 1, 1]).
size mismatch for model.diffusion_model.output_blocks.4.1.transformer_blocks.0.attn2.to_k.weight: copying a param with shape torch.Size([1280, 1024]) from checkpoint, the shape in current model is torch.Size([1280, 768]).
size mismatch for model.diffusion_model.output_blocks.4.1.transformer_blocks.0.attn2.to_v.weight: copying a param with shape torch.Size([1280, 1024]) from checkpoint, the shape in current model is torch.Size([1280, 768]).
size mismatch for model.diffusion_model.output_blocks.4.1.proj_out.weight: copying a param with shape torch.Size([1280, 1280]) from checkpoint, the shape in current model is torch.Size([1280, 1280, 1, 1]).
size mismatch for model.diffusion_model.output_blocks.5.1.proj_in.weight: copying a param with shape torch.Size([1280, 1280]) from checkpoint, the shape in current model is torch.Size([1280, 1280, 1, 1]).
size mismatch for model.diffusion_model.output_blocks.5.1.transformer_blocks.0.attn2.to_k.weight: copying a param with shape torch.Size([1280, 1024]) from checkpoint, the shape in current model is torch.Size([1280, 768]).
size mismatch for model.diffusion_model.output_blocks.5.1.transformer_blocks.0.attn2.to_v.weight: copying a param with shape torch.Size([1280, 1024]) from checkpoint, the shape in current model is torch.Size([1280, 768]).
size mismatch for model.diffusion_model.output_blocks.5.1.proj_out.weight: copying a param with shape torch.Size([1280, 1280]) from checkpoint, the shape in current model is torch.Size([1280, 1280, 1, 1]).
size mismatch for model.diffusion_model.output_blocks.6.1.proj_in.weight: copying a param with shape torch.Size([640, 640]) from checkpoint, the shape in current model is torch.Size([640, 640, 1, 1]).
size mismatch for model.diffusion_model.output_blocks.6.1.transformer_blocks.0.attn2.to_k.weight: copying a param with shape torch.Size([640, 1024]) from checkpoint, the shape in current model is torch.Size([640, 768]).
size mismatch for model.diffusion_model.output_blocks.6.1.transformer_blocks.0.attn2.to_v.weight: copying a param with shape torch.Size([640, 1024]) from checkpoint, the shape in current model is torch.Size([640, 768]).
size mismatch for model.diffusion_model.output_blocks.6.1.proj_out.weight: copying a param with shape torch.Size([640, 640]) from checkpoint, the shape in current model is torch.Size([640, 640, 1, 1]).
size mismatch for model.diffusion_model.output_blocks.7.1.proj_in.weight: copying a param with shape torch.Size([640, 640]) from checkpoint, the shape in current model is torch.Size([640, 640, 1, 1]).
size mismatch for model.diffusion_model.output_blocks.7.1.transformer_blocks.0.attn2.to_k.weight: copying a param with shape torch.Size([640, 1024]) from checkpoint, the shape in current model is torch.Size([640, 768]).
size mismatch for model.diffusion_model.output_blocks.7.1.transformer_blocks.0.attn2.to_v.weight: copying a param with shape torch.Size([640, 1024]) from checkpoint, the shape in current model is torch.Size([640, 768]).
size mismatch for model.diffusion_model.output_blocks.7.1.proj_out.weight: copying a param with shape torch.Size([640, 640]) from checkpoint, the shape in current model is torch.Size([640, 640, 1, 1]).
size mismatch for model.diffusion_model.output_blocks.8.1.proj_in.weight: copying a param with shape torch.Size([640, 640]) from checkpoint, the shape in current model is torch.Size([640, 640, 1, 1]).
size mismatch for model.diffusion_model.output_blocks.8.1.transformer_blocks.0.attn2.to_k.weight: copying a param with shape torch.Size([640, 1024]) from checkpoint, the shape in current model is torch.Size([640, 768]).
size mismatch for model.diffusion_model.output_blocks.8.1.transformer_blocks.0.attn2.to_v.weight: copying a param with shape torch.Size([640, 1024]) from checkpoint, the shape in current model is torch.Size([640, 768]).
size mismatch for model.diffusion_model.output_blocks.8.1.proj_out.weight: copying a param with shape torch.Size([640, 640]) from checkpoint, the shape in current model is torch.Size([640, 640, 1, 1]).
size mismatch for model.diffusion_model.output_blocks.9.1.proj_in.weight: copying a param with shape torch.Size([320, 320]) from checkpoint, the shape in current model is torch.Size([320, 320, 1, 1]).
size mismatch for model.diffusion_model.output_blocks.9.1.transformer_blocks.0.attn2.to_k.weight: copying a param with shape torch.Size([320, 1024]) from checkpoint, the shape in current model is torch.Size([320, 768]).
size mismatch for model.diffusion_model.output_blocks.9.1.transformer_blocks.0.attn2.to_v.weight: copying a param with shape torch.Size([320, 1024]) from checkpoint, the shape in current model is torch.Size([320, 768]).
size mismatch for model.diffusion_model.output_blocks.9.1.proj_out.weight: copying a param with shape torch.Size([320, 320]) from checkpoint, the shape in current model is torch.Size([320, 320, 1, 1]).
size mismatch for model.diffusion_model.output_blocks.10.1.proj_in.weight: copying a param with shape torch.Size([320, 320]) from checkpoint, the shape in current model is torch.Size([320, 320, 1, 1]).
size mismatch for model.diffusion_model.output_blocks.10.1.transformer_blocks.0.attn2.to_k.weight: copying a param with shape torch.Size([320, 1024]) from checkpoint, the shape in current model is torch.Size([320, 768]).
size mismatch for model.diffusion_model.output_blocks.10.1.transformer_blocks.0.attn2.to_v.weight: copying a param with shape torch.Size([320, 1024]) from checkpoint, the shape in current model is torch.Size([320, 768]).
size mismatch for model.diffusion_model.output_blocks.10.1.proj_out.weight: copying a param with shape torch.Size([320, 320]) from checkpoint, the shape in current model is torch.Size([320, 320, 1, 1]).
size mismatch for model.diffusion_model.output_blocks.11.1.proj_in.weight: copying a param with shape torch.Size([320, 320]) from checkpoint, the shape in current model is torch.Size([320, 320, 1, 1]).
size mismatch for model.diffusion_model.output_blocks.11.1.transformer_blocks.0.attn2.to_k.weight: copying a param with shape torch.Size([320, 1024]) from checkpoint, the shape in current model is torch.Size([320, 768]).
size mismatch for model.diffusion_model.output_blocks.11.1.transformer_blocks.0.attn2.to_v.weight: copying a param with shape torch.Size([320, 1024]) from checkpoint, the shape in current model is torch.Size([320, 768]).
size mismatch for model.diffusion_model.output_blocks.11.1.proj_out.weight: copying a param with shape torch.Size([320, 320]) from checkpoint, the shape in current model is torch.Size([320, 320, 1, 1]).
=======================================================================================================================
The most likely cause of this is you are trying to load Stable Diffusion 2.0 model without specifying its connfig file.
See https://github.com/AUTOMATIC1111/stable-diffusion-webui/wiki/Features#stable-diffusion-20 for how to solve this.
Stable diffusion model failed to load, exiting

No need for the yaml file, just choose the right version in the dropdown menu

ok
thanks


Pattern: Content block - segmented QA testing - Production level version

User Story

As a [user role below]:
developer using the ibm.com Library Content block - segmented

I need to:
have a version of the pattern or component that has been tested for accessibility compliance as well as on multiple browsers and platforms

so that I can:
be confident that my ibm.com web site users will have a good experience

Additional information

Browser Stack link
Browser Standard
Browser versions to be tested:  Tier 1 browsers will be tested with defects created as Sev 1 or Sev 2.  Tier 2 browser defects will be created as Sev 3 defects.
Platforms to be tested, by priority:  1)  Desktop  2)  Mobile  3)  Tablet
Mobile & Tablet iOS versions: 13.1 and 13.3
Mobile & Tablet Android versions: 9.0 Pie and 8.1 Oreo
Browsers to be tested:  Desktop: Chrome, Firefox, Safari, Edge, Mobile: Chrome, Safari, Samsung Internet, UC Browser, Tablet: Safari, Chrome, Android
Accessibility Checklist
Creating a QA bug
Design specs issue (#1988)
[Design specs link TBD]
Functional specs were created before the designs were delivered.  The designs are scheduled to be delivered in sprint 20-09.
Functional specs issues (#1821) and (#2051)
Functional specs Box link
Storybook
Code [React] [Styles]
Design QA testing issue (#2260 )
Changes summary:  Add the CTA text link, update the documentation to include the CTA on the content group level in the item array structure

Acceptance criteria

[ ] Accessibility testing is complete.  Pattern is compliant.
[ ] All browser versions are tested
[ ] All operating systems are tested
[ ] All devices are tested
[ ] Defects are recorded and retested when fixed

@Praveen-sr @chetankan I am starting to create the testing issues for the Solutions page template patterns. This issue is scheduled to be done in sprint 20-11 (May 25 - June 5). It is blocked by the development issue, but the work may begin as soon as the development is finished. You should get a notification from the developer when their work is finished.

@Praveen-sr @chetankan Development is finished.  QA testing can begin once the regression testing for the May release is finished.
Deploy preview created for package React:
https://ibmdotcom-react.s3.us-south.cloud-object-storage.appdomain.cloud/deploy-previews/2396/index.html
Built with commit: 12e7c2b27cd18980b68b2aa0bc742543852a395f

@RaphaelAmadeu Can you provide the storybook link for the Design QA tester?  Thanks.

http://ibmdotcom-react-canary.mybluemix.net/?path=/story/patterns-blocks-contentblocksegmented--default
Here it is

5/27/2020:  Function testing is finished.   Transferred for Accessibility testing.

All QA and Accessibility testing is finished.


M4 PSU screws must be button head

Documentation does not specify.

Updated BOM and assembly documentation for this.


StickyKeys

Description of the new feature / enhancement
DSCResource name: Keyboard
(Foreach property)
Property name: EnableStickyKeys
TypeOrEnum: nullable[bool]
EnumItems:
Registry path: HKEY_CURRENT_USER\Control Panel\Accessibility\StickyKeys
Registry key name: Flags
Registry key type: Reg_SZ

26 - off
511 - on

(This is apparently a keymap)
Get method name: GetEnableStickyKeys
Proposed technical implementation details
No response

https://learn.microsoft.com/en-us/windows/win32/api/winuser/ns-winuser-stickykeys


More logs for forge build

Component
Forge
Describe the feature you would like
It takes a while running forge build and somtimes it got broken by http requests on my machine, so better to add more logs to it that users can get known they're stucking in which step
btw it would be nice providing --verbose for this command as well
Additional context
No response

somtimes it got broken by http requests on my machine

Can you expand on what you mean here?
Also if it helps, you can use something like RUST_LOG=ethers_solc forge build or RUST_LOG=ethers,ethers_solc,forge forge build to see more logs when building. Most likely it's just that sometimes solc can take a while to compile, I'm not sure how verbose solc is with logs as to why though, but maybe @mattsse will know

installing from the internet should always go with logs since it spends more time than compiling lots of time

agree!
will add some

related to global verbose flag support https://github.com/foundry-rs/foundry/pull/9273


Jest.mock calls are not hoisted to the top

Issue

Jest.mock('foo') calls are not hoisted to the top of the module as they're meant to, unless allowSyntheticDefaults is set to true.
This is because in jest, they are hoisted automatically by babel-jest:
https://github.com/facebook/jest/blob/master/packages/babel-jest/src/index.js
line 68
 presets: ((options && options.presets) || []).concat([jestPreset]),

and the jestPreset is:
https://github.com/facebook/jest/blob/master/packages/babel-preset-jest/index.js
https://github.com/facebook/jest/blob/master/packages/babel-preset-jest/index.js

I suggest we always run the transpiled code through babel-jest, but we only add the plugin 'transform-es2015-modules-commonjs' if allowSyntheticDefaults is set to true.
This will align with the expected behaviour of vanilla jest.
I think this will also indirectly fix things like #120 which currently only work when allowSyntheticDefaults is set to true, and fixes the workaround needed in #90

Currently blocked by #211  - running everything through babel will break coverage for everyone

Just adding a note to remove the check for allowSyntheticDefaultImports when using babel to hoist mock calls

Yes. I have this almost finished in a local branch. Would love if someone had time to do a few extra process-regression tests, just with snapshots.

I added regression tests. Work is ongoing in https://github.com/kulshekhar/ts-jest/tree/hoist-mock-calls

I am unsure as to how to test whether the sourcemaps actually line up. Do you have any suggestions @kulshekhar ?

I had the same problem at the beginning. Here's how I approached it. Write a test in typescript that results in an error (in the test or in the part that the test is testing). See if the line number in the final output matches the actual source file.
So in the current setup, if the tests that check the line numbers pass, the sourcemaps are working properly.
Also, you might want to update your editor settings to add a new line character at the end of the files because it is currently removing it.

Is checking transpiled code against a snapshot is a good idea? I've seen the outputs vary across transpiler versions and it might cause hard to debug failures in CI

Is checking transpiled code against a snapshot is a good idea? I've seen the outputs vary across transpiler versions and it might cause hard to debug failures in CI

Hm, that makes sense. I see that the current changes result in the line numbers being right, but the character offset being off. It makes sense as a strategy I guess, although it seems a little hacky.
I'll get the editor fixed.
I'm not sure, don't you think it'll be fine if we pin our dependencies? If there's minor differences between transpiler versions we should just be able to update them.  Are there other alternatives?

I see that the current changes result in the line numbers being right, but the character offset being off

I think that's a known issue with babel jest. Currently we're checking the line and column number in the tests. With babel jest, we should probably only check the line number.

Are there other alternatives?

I think a test that actually uses hoisting would be less brittle. So something that would break if hoisting didn't work but would pass if it did.

I think you're thinking of #230 maybe?

I have some tests lying around that uses hoisting, but I haven't comitted them yet. I'm mostly just a little scared that if we start playing with hooks that we don't have a way of sanity checking refactors. Does it matter the tests are brittle if they're easy to update? I'm on the fence about this atm.

found it - I had read that in babel's documentation for retainLines.

I'm mostly just a little scared that if we start playing with hooks that we don't have a way of sanity checking refactors.

That's the advantage of testing like we're currently doing - by running jest on mini projects (that's what the tests essentially are). It doesn't matter what we have inside as long as the external behavior is what we want.

Does it matter the tests are brittle if they're easy to update? I'm on the fence about this atm.

The test for hoisting should be as simple as the simplest test we have. It's just that the code in that mini-project (test) will use something that needs hoisting.

That's the advantage of testing like we're currently doing - by running jest on mini projects (that's what the tests essentially are). It doesn't matter what we have inside as long as the external behavior is what we want.

Hm, yeah alright. It just seems a little hacky to check the sourcemaps via error lines, but I guess it could work.

The test for hoisting should be as simple as the simplest test we have. It's just that the code in that mini-project (test) will use something that needs hoisting.

Yeah definitely. I did all of that on another pc and forgot to push.. 😭

nice catch with the babel documentation.
Should be resolved in #239 - i ended up removing the regression tests, I think you were right.


Convert to Astro Bookshop

This PR migrates this template from using vanilla JS live editing + data-bindings to using Astro Bookshop(beta)

Readme could be updated to say "...with bookshop" somewhere

Otherwise looks pretty good


Fix some titles and meta descriptions

This change fixes up some titles and meta descriptions, in hopes
that it'll have a positive impact on our SEO (and SERP summary).

Ensure all pages have titles and meaningful meta descriptions.

Error out if pages lack a meta description. Also add the ability
to write nosummary: true if it's intentionally omitted.

I'd like to error out if pages lack a title too. Unfortunately,
the Python API docs are missing titles (pulumi/docs#1127), so this
check is not currently enabled (easy to uncomment out later).

I also made the possibly-controversial change to stop emitting an
automatic - Pulumi at the end of page titles. This

Leads to illy things -- like About Pulumi - Pulumi.

Might make it more difficult for Google to extract a good title for
our SERP summary; is that why "Documentation" is currently
awkwardly labeled simply "Pulumi" on Google at the moment?

Probably has a net negative effect on things like blog articles,
which we would like to index naturally based on the content.

I propose that anywhere we want Pulumi in the title, we manually add it.

While we're on the topic of .Summary, yesterday I had mentioned to @erinhyperplane that using it for the meta description leads to some unusual meta descriptions for pages. For example:
https://www.pulumi.com/docs/reference/install/
        <meta name="description" content="This page contains detailed instructions on installing Pulumi.
For a streamlined walkthrough of getting started with Pulumi, including installing Pulumi and prerequisites, see the Get Started guide.
 var oses = [ "unknown", "linux", "macos", "windows" ]; function showInstall(os) { // Show the div and select it in the dropdown. var e = document.getElementById(os + "_installation"); if (e) { e.style.display = "block"; var s = document.getElementById("os"); if (s) { for (var i = 0; i Operating system: (choose one) Linux macOS Windows">

She was wondering if we should stop using .Summary for meta description, and let people write meta_desc so they can write whatever they want in the first paragraph (or above <!--more-->) and not have to worry about having meta descriptions like this. She was going to open an issue with a proposal this week when she started diving in on improving our meta descriptions.

Yeah, I was just looking at those summaries. All of them are terrible, with few exceptions. (Setting summaryLength = 30 in the config seems to make them slightly more appealing, but not by much.) Let me see how bad it is to just plow through and tidy this up.

She was going to open an issue with a proposal this week when she started diving in on improving our meta descriptions.

Ok, I am admitting defeat 😉 This sounds like a better course of action. I'll clean up the PR based on comments above and leave it to a deeper exercise to figure out what to do with the rest.

By the way, if it wasn't evident why I was focused on only a smattering of pages, it began with me wondering about Google's SERP/summary for us:

I still wish I knew how and why Google is selecting those pages -- as they aren't what I would choose! -- and it will be interesting to see if these changes help with the nested "Pulumi".

it is a myth to me how google are showing those cards - it looks different on my machine, and it looks different from just a week before (it used to have docs, pricing, why pulumi, etc.)


Sanity rework effort - Retag all Sanity tests with Tier1 task

Retag all Sanity tests with Tier1 (should have both tags)
CI: rhods-ci-pr-test/2395/

CI: rhods-ci-pr-test/2395/ succeded


Split FullNode class. Move base code to FullNodeBase.

Updated FullNode.cs to remove all references to the below features. The modified code becomes FullNodeBase.cs. Re-introduce the removals via a new FullNode.cs (derived from FullNodeBase.cs).
 using Stratis.Bitcoin.Features.BlockStore;
 using Stratis.Bitcoin.Features.Consensus;
 using Stratis.Bitcoin.Features.Consensus.CoinViews;
 using Stratis.Bitcoin.Features.MemoryPool;
 using Stratis.Bitcoin.Features.Wallet;

Next step may be to add a project for the FullNode: Stratis.Bitcoin.FullNode

Hi this was not exactly how I planned it, ideally the fullnode should not have any dependency on any feature (maybe base feature).
So we can solve it on two ways.
Creating a interfaces for features that will live in the fullnode or removing the dependency.
I prefer the second option:
The fullnode exposes a property called IFullNodeServiceProvider, it should be possible for any external component to use this provider to get the service it needs.
Maybe instead of a base class we just delete the dependencies and expose a method as such
Public T NodeService<T>()
{
    var service = this.Services.ServiceProvider.GetService<T>()
    if(service == null)
      throw ...
}


Fixed error in example 8

resolves #1742

Hello, @shivtorov Can you change the target branch of the PR to master from live? Thank you.

@e0i done

@dariomws306 @get-itips @tseward
Peer review needed for this PR. Thanks.

You should be able to use `Get-Content -Encoding Byte -Path /path/to/file.svc' instead of the class directly, no?

As the example is converting a plain text portion of the certsrv url in the go to bytes, I think Get-Content won't be of use here.
I am ok with the change.


Basic Blueprint functionality

This PR adds Blueprints to Sanic, solving issue #7.
Tests, documentation, and examples are included.

Merge conflicts from latest changes to master are resolved.

Awesome work, it's merged!


Build issue with cuda 11.0 and current master

Issue Description:
Please describe our issue, along with:
Compilation Error
Version Information
Please indicate relevant versions, including, if relevant:
Deeplearning4j version:
CURRENT SNAPSHOT
Platform information (OS, etc):
Windows 10 Pro 20H2 (64Bit)
AMD Ryzen 5 5600X 6-Core Processor
GeForce RTX 3070
CUDA version, if used:
v11.0
NVIDIA driver version, if in use:
v496.76 (DCH)
Additional Information:
gcc.exe (Rev1, Built by MSYS2 project) 11.2.0
cmake version 3.22.1
Visual Studio 2019 (Community)
Full log or exception stack trace (ideally in a Gist: gist.github.com):
cd /c/Users/Administrator/Downloads/deeplearning4j
export JAVA_HOME=/c/Program\ Files/Java/jdk1.8.0_281
./change-cuda-versions.sh 11.0
cd libnd4j
export LIBND4J_HOME=$(pwd)
./buildnativeoperations.sh -a native -c cpu -e avx2 -h openblas -p msi -j 12 clean true

.
.
.
[100%] Linking CXX shared library libnd4jcpu.dll
cd /C/Users/Administrator/Downloads/deeplearning4j/libnd4j/blasbuild/cpu/blas && /C/MSys64/mingw64/bin/cmake.exe -E rm -f CMakeFiles/nd4jcpu.dir/objects.a
cd /C/Users/Administrator/Downloads/deeplearning4j/libnd4j/blasbuild/cpu/blas && /C/MSys64/mingw64/bin/ar.exe qc CMakeFiles/nd4jcpu.dir/objects.a @CMakeFiles/nd4jcpu.dir/objects1.rsp
cd /C/Users/Administrator/Downloads/deeplearning4j/libnd4j/blasbuild/cpu/blas && /C/MSys64/mingw64/bin/g++.exe  -DSD_WINDOWS_BUILD=true -Wa,-mbig-obj -mmmx -msse -msse2 -msse3 -msse4.1 -msse4.2 -mavx -mavx2 -mfma -mf16c -mprefetchwt1 -DSD_F16C=true -DF_AVX2=true -mno-avx256-split-unaligned-load -mno-avx256-split-unaligned-store -fmax-errors=3  -fopenmp -O3 -fPIC -D_RELEASE=true  -Wl,-rpath,RIGIN/ -shared -o libnd4jcpu.dll -Wl,--out-implib,libnd4jcpu.dll.a -Wl,--major-image-version,0,--minor-image-version,0 -Wl,--whole-archive CMakeFiles/nd4jcpu.dir/objects.a -Wl,--no-whole-archive @CMakeFiles/nd4jcpu.dir/linklibs.rsp
C:/MSys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/11.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe: CMakeFiles/nd4jcpu.dir/objects.a(activations.cpp.obj):activations.cpp:(.text+0x463): undefined reference to shape::subArrayIndex(long long, long long const*, long long const*, int const*, int)' C:/MSys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/11.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe: CMakeFiles/nd4jcpu.dir/objects.a(activations.cpp.obj):activations.cpp:(.text+0xad7): undefined reference to shape::subArrayIndex(long long, long long const*, long long const*, int const*, int)'
C:/MSys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/11.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe: CMakeFiles/nd4jcpu.dir/objects.a(tile.cpp.obj):tile.cpp:(.text+0x763): undefined reference to shape::subArrayIndex(long long, long long const*, long long const*, int const*, int)' C:/MSys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/11.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe: CMakeFiles/nd4jcpu.dir/objects.a(tile.cpp.obj):tile.cpp:(.text+0x9c3): undefined reference to shape::subArrayIndex(long long, long long const*, long long const*, int const*, int)'
C:/MSys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/11.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe: CMakeFiles/nd4jcpu.dir/objects.a(tile.cpp.obj):tile.cpp:(.text+0xbd3): undefined reference to shape::subArrayIndex(long long, long long const*, long long const*, int const*, int)' C:/MSys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/11.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe: CMakeFiles/nd4jcpu.dir/objects.a(tile.cpp.obj):tile.cpp:(.text+0xd63): more undefined references to shape::subArrayIndex(long long, long long const*, long long const*, int const*, int)' follow
collect2.exe: error: ld returned 1 exit status
.
.
.

@baedaron could you please ensure this is working with cuda 11.2? I literally just compiled this fine with your exact environment not too long ago. If something is missing on at least cuda 11.2 (which is the version we're supporting alongside cuda 11.4) I can take a quick look. I suspect I know what the problem might be but would like to make sure it's reproducible for us. Thanks! cc @quickwritereader

@baedaron you are having a problem building CPU or Cuda?

I confirm the problem on the cpu build

@quickwritereader
My mistake! sorry.
It's about CPU.
./buildnativeoperations.sh -a native -c cpu -e avx2 -h openblas -p msi -j 12 clean true


Rewrite UI and add jest tests

As the title says:

We added jest tests everywhere
We rewrote the UI following designs by @mateotk
We converted class component to functional components
We added the ImportMapOverridesContext to simplify handling of state

Cool UI :sparkles: !


What is the meaning of the result?

Sorry the dumb question, but what is the meaning of the result? Initially I though it was some buggy doc, but just installed and confirmed
var dataset = [
    [1,1],[0,1],[1,0],
    [10,10],[10,13],[13,13],
    [54,54],[55,55],[89,89],[57,55]
];

var clustering = require('density-clustering');
var dbscan = new clustering.DBSCAN();
// parameters: 5 - neighborhood radius, 2 - number of points in neighborhood to form a cluster
var clusters = dbscan.run(dataset, 5, 2);
console.log(clusters, dbscan.noise);

/*
RESULT:
[
    [0,1,2],
    [3,4,5],
    [6,7,9],
    [8]
]

NOISE: [ 8 ]
*/

Why 3 different clusters of points in 2D have as result a 3x3 matrix?

WTF, it's the indexes of the array :)

lol thank you. New to this stuff and I had no idea how to figure out which vectors were included in the arrays. I thought the result was a vector in itself.


Crawl stops on non-www URLs

What is the current behavior?
If I specify a domain like eg. "http://www.domainname.com/"
but the preferred domain settings on the server are without "www." then the crawling process stops.
The REVERSE is also valid unfortunately if I specify a DOMAIN that has "www" but I do not specify it eg. "http://domainname.com/" the crawling also STOPS.
If the current behavior is a bug, please provide the steps to reproduce
What is the expected behavior?
Normally I expect it to recognize the domain name without "www"
What is the motivation / use case for changing the behavior?
Please tell us about your environment:

Version: latest
Platform / OS version: mac OS X
Node.js version:  latest

hey cosmiXs I made an npm package to fix this. It's called 'redirect-chain'. You give it your entrypoint url and then it gives you the domain redirect chain. Then use this array as allowedDomains.
https://www.npmjs.com/package/redirect-chain

I'm having the same problem. I get a timeout when visiting a non www url. I can visit it on the browser just fine.
I tried using @simlevesque's solution but I sill get the same problem.
await crawler.queue({
   url,
   allowedDomains: redirectChain.domains(url);
});

@cosmiXs @vycoder could you provide a full code example to reproduce the issue?


no error message for faulty imports in index.js of content script

If I add code like:
  import * as Z from 'messeddup';

on the top of:
 src/pages/Content/index.js

and run:
npm run build

the build directory is not created and there is no error message.  Seems like error message are swallowed.
Note messeddup is not a real module - it is not in package.json or in node_modules

Anyone figure out how to output error messages for situations like this?

+1 I am having the same issue.  No error message and no output.  npm run start hangs and never finishes the bundle.


Formatting doesn't work

Hello
October Code v0.28.00
An error occurs when trying to format code
2024-06-25 19:27:51.247 [error] [Extension Host] Error: printer.embed has too many parameters. The API changed in Prettier v3. Please update your plugin. See https://prettier.io/docs/en/plugins.html#optional-embed     at Fn (/home/metallizzer/.vscode/extensions/sergeykasyanov.october-code-0.28.0/dist/extension.js:2:939448)     at Pn (/home/metallizzer/.vscode/extensions/sergeykasyanov.october-code-0.28.0/dist/extension.js:2:940562)     at qn (/home/metallizzer/.vscode/extensions/sergeykasyanov.october-code-0.28.0/dist/extension.js:2:946406)     at Jn (/home/metallizzer/.vscode/extensions/sergeykasyanov.october-code-0.28.0/dist/extension.js:2:948994)     at Object.Dr (/home/metallizzer/.vscode/extensions/sergeykasyanov.october-code-0.28.0/dist/extension.js:2:952664)     at t.formatTwig (/home/metallizzer/.vscode/extensions/sergeykasyanov.october-code-0.28.0/dist/extension.js:2:1297214)     at t.OctoberTplDocumentFormatting.provideDocumentFormattingEdits (/home/metallizzer/.vscode/extensions/sergeykasyanov.october-code-0.28.0/dist/extension.js:2:1299223)     at F.provideDocumentFormattingEdits (/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:153:107334)

Hello. Thanks for reporting. Try new version 0.28.1

Hello. Thanks for reporting. Try new version 0.28.1

Thanks. It works now
Can you please look at #14 issue


globals.css Variant cannot be generated because selector contains no classes.

Hello,
i get this error
/Users/kloetzchengrafik/Documents/Stade/renderer/styles/globals.css Variant cannot be generated because selector contains no classes.
I added daisyui using yarn add daisyui.
Tailwind config:
module.exports = {
darkMode: false, // or 'media' or 'class'
theme: {
extend: {
boxShadow: {
"lg": "0 10px 15px -3px #F1E0AC, 0 4px 6px -4px #F1E0AC"
}
},
},
variants: {
extend: {},
},
plugins: [require("daisyui")],
};
(I'm using nextjs with typescript)

@PixelPage-YT Can you provide a small repo so I can reproduce this issue?

Sure!
https://github.com/PixelPage-YT/daisyui-error

Updating to Tailwind CSS 3.0 will fix the error. however, your app doesn't seem to generate styles when I install Tailwind CSS 3.0
I'm not sure which package is no compatible but If you want to use Tailwind CSS 2.x, use daisyui 1.x with it.