wasm pack test tests fail on windows master locally

I'm getting eight test failures when I try to run the tests locally against master:
failures:

---- build::build_with_and_without_wasm_bindgen_debug stdout ----
Created fixture at C:\Users\Steve Klabnik\src\wasm-pack\target\t\.tmpb6Za0F\wasm-pack
thread 'build::build_with_and_without_wasm_bindgen_debug' panicked at 'assertion failed: `(left == right)`
  left: `false`,
 right: `true`: Should only contain moved value assertions when debug assertions are enabled', tests\all\build.rs:197:9
note: Run with `RUST_BACKTRACE=1` environment variable to display a backtrace.

---- test::cdylib_not_required stdout ----
Created fixture at C:\Users\Steve Klabnik\src\wasm-pack\target\t\.tmpn1iWj2\wasm-pack
thread 'test::cdylib_not_required' panicked at 'Unexpected failure.
code-1
stderr=```[INFO]: Checking for the Wasm target...
   Compiling foo v0.1.0 (C:\Users\Steve Klabnik\src\wasm-pack\target\t\.tmpn1iWj2\wasm-pack)
    Finished dev [unoptimized + debuginfo] target(s) in 0.39s
[INFO]: Installing wasm-bindgen...
    Finished dev [unoptimized + debuginfo] target(s) in 0.06s
     Running C:\Users\Steve Klabnik\src\wasm-pack\target\wasm32-unknown-unknown\debug\deps\foo-8c3d9288e4deee31.wasm
error: could not execute process `C:\Users\Steve Klabnik\src\wasm-pack\target\test_cache\wasm-bindgen-58ea13aff44655c4\wasm-bindgen-test-runner.exe "C:\Users\Steve Klabnik\src\wasm-pack\target\wasm32-unknown-unknown\debug\deps\foo-8c3d9288e4deee31.wasm"` (never executed)

Caused by:
  The system cannot find the file specified. (os error 2)
Error: Running Wasm tests with wasm-bindgen-test failed
Caused by: failed to execute `cargo test`: exited with exit code: 101
```
command=`"C:\\Users\\Steve Klabnik\\src\\wasm-pack\\target\\debug\\wasm-pack.exe" "test" "--node"`
code=1
stdout=``````
stderr=```[INFO]: Checking for the Wasm target...
   Compiling foo v0.1.0 (C:\Users\Steve Klabnik\src\wasm-pack\target\t\.tmpn1iWj2\wasm-pack)
    Finished dev [unoptimized + debuginfo] target(s) in 0.39s
[INFO]: Installing wasm-bindgen...
    Finished dev [unoptimized + debuginfo] target(s) in 0.06s
     Running C:\Users\Steve Klabnik\src\wasm-pack\target\wasm32-unknown-unknown\debug\deps\foo-8c3d9288e4deee31.wasm
error: could not execute process `C:\Users\Steve Klabnik\src\wasm-pack\target\test_cache\wasm-bindgen-58ea13aff44655c4\wasm-bindgen-test-runner.exe "C:\Users\Steve Klabnik\src\wasm-pack\target\wasm32-unknown-unknown\debug\deps\foo-8c3d9288e4deee31.wasm"` (never executed)

Caused by:
  The system cannot find the file specified. (os error 2)
Error: Running Wasm tests with wasm-bindgen-test failed
Caused by: failed to execute `cargo test`: exited with exit code: 101
```
', C:\Users\Steve Klabnik\.cargo\registry\src\github.com-1ecc6299db9ec823\assert_cmd-0.11.1\src\assert.rs:154:13

---- test::it_can_find_a_webdriver_on_path stdout ----
Created fixture at C:\Users\Steve Klabnik\src\wasm-pack\target\t\.tmpdJZHFE\wasm-pack
thread 'test::it_can_find_a_webdriver_on_path' panicked at 'Unexpected failure.
code-1
stderr=```   Compiling wbg-test-browser v0.1.0 (C:\Users\Steve Klabnik\src\wasm-pack\target\t\.tmpdJZHFE\wasm-pack)
    Finished dev [unoptimized + debuginfo] target(s) in 0.31s
    Finished dev [unoptimized + debuginfo] target(s) in 0.06s
     Running C:\Users\Steve Klabnik\src\wasm-pack\target\wasm32-unknown-unknown\debug\deps\wbg_test_browser-24692dddaadbd2b1.wasm
error: could not execute process `C:\Users\Steve Klabnik\src\wasm-pack\target\test_cache\wasm-bindgen-de1b2fa2130aaa0c\wasm-bindgen-test-runner.exe "C:\Users\Steve Klabnik\src\wasm-pack\target\wasm32-unknown-unknown\debug\deps\wbg_test_browser-24692dddaadbd2b1.wasm"` (never executed)

Caused by:
  The system cannot find the file specified. (os error 2)
Error: Running Wasm tests with wasm-bindgen-test failed
Caused by: failed to execute `cargo test`: exited with exit code: 101
```
command=`"C:\\Users\\Steve Klabnik\\src\\wasm-pack\\target\\debug\\wasm-pack.exe" "test" "--firefox" "--headless" "--mode" "no-install"`
code=1
stdout=``````
stderr=```   Compiling wbg-test-browser v0.1.0 (C:\Users\Steve Klabnik\src\wasm-pack\target\t\.tmpdJZHFE\wasm-pack)
    Finished dev [unoptimized + debuginfo] target(s) in 0.31s
    Finished dev [unoptimized + debuginfo] target(s) in 0.06s
     Running C:\Users\Steve Klabnik\src\wasm-pack\target\wasm32-unknown-unknown\debug\deps\wbg_test_browser-24692dddaadbd2b1.wasm
error: could not execute process `C:\Users\Steve Klabnik\src\wasm-pack\target\test_cache\wasm-bindgen-de1b2fa2130aaa0c\wasm-bindgen-test-runner.exe "C:\Users\Steve Klabnik\src\wasm-pack\target\wasm32-unknown-unknown\debug\deps\wbg_test_browser-24692dddaadbd2b1.wasm"` (never executed)

Caused by:
  The system cannot find the file specified. (os error 2)
Error: Running Wasm tests with wasm-bindgen-test failed
Caused by: failed to execute `cargo test`: exited with exit code: 101
```
', C:\Users\Steve Klabnik\.cargo\registry\src\github.com-1ecc6299db9ec823\assert_cmd-0.11.1\src\assert.rs:154:13

---- test::it_can_run_browser_tests stdout ----
Created fixture at C:\Users\Steve Klabnik\src\wasm-pack\target\t\.tmptj1NdY\wasm-pack
thread 'test::it_can_run_browser_tests' panicked at 'Unexpected failure.
code-1
stderr=```[INFO]: Checking for the Wasm target...
    Finished dev [unoptimized + debuginfo] target(s) in 0.05s
[INFO]: Installing wasm-bindgen...
    Finished dev [unoptimized + debuginfo] target(s) in 0.05s
     Running C:\Users\Steve Klabnik\src\wasm-pack\target\wasm32-unknown-unknown\debug\deps\wbg_test_browser-24692dddaadbd2b1.wasm
error: could not execute process `C:\Users\Steve Klabnik\src\wasm-pack\target\test_cache\wasm-bindgen-de1b2fa2130aaa0c\wasm-bindgen-test-runner.exe "C:\Users\Steve Klabnik\src\wasm-pack\target\wasm32-unknown-unknown\debug\deps\wbg_test_browser-24692dddaadbd2b1.wasm"` (never executed)

Caused by:
  The system cannot find the file specified. (os error 2)
Error: Running Wasm tests with wasm-bindgen-test failed
Caused by: failed to execute `cargo test`: exited with exit code: 101
```
command=`"C:\\Users\\Steve Klabnik\\src\\wasm-pack\\target\\debug\\wasm-pack.exe" "test" "--headless" "--firefox"`
code=1
stdout=``````
stderr=```[INFO]: Checking for the Wasm target...
    Finished dev [unoptimized + debuginfo] target(s) in 0.05s
[INFO]: Installing wasm-bindgen...
    Finished dev [unoptimized + debuginfo] target(s) in 0.05s
     Running C:\Users\Steve Klabnik\src\wasm-pack\target\wasm32-unknown-unknown\debug\deps\wbg_test_browser-24692dddaadbd2b1.wasm
error: could not execute process `C:\Users\Steve Klabnik\src\wasm-pack\target\test_cache\wasm-bindgen-de1b2fa2130aaa0c\wasm-bindgen-test-runner.exe "C:\Users\Steve Klabnik\src\wasm-pack\target\wasm32-unknown-unknown\debug\deps\wbg_test_browser-24692dddaadbd2b1.wasm"` (never executed)

Caused by:
  The system cannot find the file specified. (os error 2)
Error: Running Wasm tests with wasm-bindgen-test failed
Caused by: failed to execute `cargo test`: exited with exit code: 101
```
', C:\Users\Steve Klabnik\.cargo\registry\src\github.com-1ecc6299db9ec823\assert_cmd-0.11.1\src\assert.rs:154:13

---- test::it_can_run_node_tests stdout ----
Created fixture at C:\Users\Steve Klabnik\src\wasm-pack\target\t\.tmpsCHZnl\wasm-pack
thread 'test::it_can_run_node_tests' panicked at 'Unexpected failure.
code-1
stderr=```[INFO]: Checking for the Wasm target...
   Compiling wbg-test-node v0.1.0 (C:\Users\Steve Klabnik\src\wasm-pack\target\t\.tmpsCHZnl\wasm-pack)
    Finished dev [unoptimized + debuginfo] target(s) in 0.33s
[INFO]: Installing wasm-bindgen...
    Finished dev [unoptimized + debuginfo] target(s) in 0.05s
     Running C:\Users\Steve Klabnik\src\wasm-pack\target\wasm32-unknown-unknown\debug\deps\wbg_test_node-d2a74f64cb9c762c.wasm
error: could not execute process `C:\Users\Steve Klabnik\src\wasm-pack\target\test_cache\wasm-bindgen-de1b2fa2130aaa0c\wasm-bindgen-test-runner.exe "C:\Users\Steve Klabnik\src\wasm-pack\target\wasm32-unknown-unknown\debug\deps\wbg_test_node-d2a74f64cb9c762c.wasm"` (never executed)

Caused by:
  The system cannot find the file specified. (os error 2)
Error: Running Wasm tests with wasm-bindgen-test failed
Caused by: failed to execute `cargo test`: exited with exit code: 101
```
command=`"C:\\Users\\Steve Klabnik\\src\\wasm-pack\\target\\debug\\wasm-pack.exe" "test" "--node"`
code=1
stdout=``````
stderr=```[INFO]: Checking for the Wasm target...
   Compiling wbg-test-node v0.1.0 (C:\Users\Steve Klabnik\src\wasm-pack\target\t\.tmpsCHZnl\wasm-pack)
    Finished dev [unoptimized + debuginfo] target(s) in 0.33s
[INFO]: Installing wasm-bindgen...
    Finished dev [unoptimized + debuginfo] target(s) in 0.05s
     Running C:\Users\Steve Klabnik\src\wasm-pack\target\wasm32-unknown-unknown\debug\deps\wbg_test_node-d2a74f64cb9c762c.wasm
error: could not execute process `C:\Users\Steve Klabnik\src\wasm-pack\target\test_cache\wasm-bindgen-de1b2fa2130aaa0c\wasm-bindgen-test-runner.exe "C:\Users\Steve Klabnik\src\wasm-pack\target\wasm32-unknown-unknown\debug\deps\wbg_test_node-d2a74f64cb9c762c.wasm"` (never executed)

Caused by:
  The system cannot find the file specified. (os error 2)
Error: Running Wasm tests with wasm-bindgen-test failed
Caused by: failed to execute `cargo test`: exited with exit code: 101
```
', C:\Users\Steve Klabnik\.cargo\registry\src\github.com-1ecc6299db9ec823\assert_cmd-0.11.1\src\assert.rs:154:13

---- test::it_can_run_tests_with_different_wbg_test_and_wbg_versions stdout ----
Created fixture at C:\Users\Steve Klabnik\src\wasm-pack\target\t\.tmpxLkoPZ\wasm-pack
thread 'test::it_can_run_tests_with_different_wbg_test_and_wbg_versions' panicked at 'Unexpected failure.
code-1
stderr=```[INFO]: Checking for the Wasm target...
   Compiling wbg-test-diff-versions v0.1.0 (C:\Users\Steve Klabnik\src\wasm-pack\target\t\.tmpxLkoPZ\wasm-pack)
    Finished dev [unoptimized + debuginfo] target(s) in 0.50s
[INFO]: Installing wasm-bindgen...
    Finished dev [unoptimized + debuginfo] target(s) in 0.07s
     Running C:\Users\Steve Klabnik\src\wasm-pack\target\wasm32-unknown-unknown\debug\deps\wbg_test_diff_versions-04d7df984392f06a.wasm
error: could not execute process `C:\Users\Steve Klabnik\src\wasm-pack\target\test_cache\wasm-bindgen-58ea13aff44655c4\wasm-bindgen-test-runner.exe "C:\Users\Steve Klabnik\src\wasm-pack\target\wasm32-unknown-unknown\debug\deps\wbg_test_diff_versions-04d7df984392f06a.wasm"` (never executed)

Caused by:
  The system cannot find the file specified. (os error 2)
Error: Running Wasm tests with wasm-bindgen-test failed
Caused by: failed to execute `cargo test`: exited with exit code: 101
```
command=`"C:\\Users\\Steve Klabnik\\src\\wasm-pack\\target\\debug\\wasm-pack.exe" "test" "--node"`
code=1
stdout=``````
stderr=```[INFO]: Checking for the Wasm target...
   Compiling wbg-test-diff-versions v0.1.0 (C:\Users\Steve Klabnik\src\wasm-pack\target\t\.tmpxLkoPZ\wasm-pack)
    Finished dev [unoptimized + debuginfo] target(s) in 0.50s
[INFO]: Installing wasm-bindgen...
    Finished dev [unoptimized + debuginfo] target(s) in 0.07s
     Running C:\Users\Steve Klabnik\src\wasm-pack\target\wasm32-unknown-unknown\debug\deps\wbg_test_diff_versions-04d7df984392f06a.wasm
error: could not execute process `C:\Users\Steve Klabnik\src\wasm-pack\target\test_cache\wasm-bindgen-58ea13aff44655c4\wasm-bindgen-test-runner.exe "C:\Users\Steve Klabnik\src\wasm-pack\target\wasm32-unknown-unknown\debug\deps\wbg_test_diff_versions-04d7df984392f06a.wasm"` (never executed)

Caused by:
  The system cannot find the file specified. (os error 2)
Error: Running Wasm tests with wasm-bindgen-test failed
Caused by: failed to execute `cargo test`: exited with exit code: 101
```
', C:\Users\Steve Klabnik\.cargo\registry\src\github.com-1ecc6299db9ec823\assert_cmd-0.11.1\src\assert.rs:154:13

---- test::renamed_crate_name_works stdout ----
Created fixture at C:\Users\Steve Klabnik\src\wasm-pack\target\t\.tmpEAHv3n\wasm-pack
thread 'test::renamed_crate_name_works' panicked at 'Unexpected failure.
code-1
stderr=```[INFO]: Checking for the Wasm target...
   Compiling foo v0.1.0 (C:\Users\Steve Klabnik\src\wasm-pack\target\t\.tmpEAHv3n\wasm-pack)
    Finished dev [unoptimized + debuginfo] target(s) in 0.19s
[INFO]: Installing wasm-bindgen...
    Finished dev [unoptimized + debuginfo] target(s) in 0.05s
     Running C:\Users\Steve Klabnik\src\wasm-pack\target\wasm32-unknown-unknown\debug\deps\bar-42d251210dd2004d.wasm
error: could not execute process `C:\Users\Steve Klabnik\src\wasm-pack\target\test_cache\wasm-bindgen-58ea13aff44655c4\wasm-bindgen-test-runner.exe "C:\Users\Steve Klabnik\src\wasm-pack\target\wasm32-unknown-unknown\debug\deps\bar-42d251210dd2004d.wasm"` (never executed)

Caused by:
  The system cannot find the file specified. (os error 2)
Error: Running Wasm tests with wasm-bindgen-test failed
Caused by: failed to execute `cargo test`: exited with exit code: 101
```
command=`"C:\\Users\\Steve Klabnik\\src\\wasm-pack\\target\\debug\\wasm-pack.exe" "test" "--node"`
code=1
stdout=``````
stderr=```[INFO]: Checking for the Wasm target...
   Compiling foo v0.1.0 (C:\Users\Steve Klabnik\src\wasm-pack\target\t\.tmpEAHv3n\wasm-pack)
    Finished dev [unoptimized + debuginfo] target(s) in 0.19s
[INFO]: Installing wasm-bindgen...
    Finished dev [unoptimized + debuginfo] target(s) in 0.05s
     Running C:\Users\Steve Klabnik\src\wasm-pack\target\wasm32-unknown-unknown\debug\deps\bar-42d251210dd2004d.wasm
error: could not execute process `C:\Users\Steve Klabnik\src\wasm-pack\target\test_cache\wasm-bindgen-58ea13aff44655c4\wasm-bindgen-test-runner.exe "C:\Users\Steve Klabnik\src\wasm-pack\target\wasm32-unknown-unknown\debug\deps\bar-42d251210dd2004d.wasm"` (never executed)

Caused by:
  The system cannot find the file specified. (os error 2)
Error: Running Wasm tests with wasm-bindgen-test failed
Caused by: failed to execute `cargo test`: exited with exit code: 101
```
', C:\Users\Steve Klabnik\.cargo\registry\src\github.com-1ecc6299db9ec823\assert_cmd-0.11.1\src\assert.rs:154:13

---- test::test_output_is_printed_once_in_both_stdout_and_failures stdout ----
Created fixture at C:\Users\Steve Klabnik\src\wasm-pack\target\t\.tmpIDGnTq\wasm-pack
thread 'test::test_output_is_printed_once_in_both_stdout_and_failures' panicked at 'Unexpected stdout, failed fn(var)
└── var as str:

command=`"C:\\Users\\Steve Klabnik\\src\\wasm-pack\\target\\debug\\wasm-pack.exe" "test" "--node"`
code=1
stdout=``````
stderr=```[INFO]: Checking for the Wasm target...
   Compiling test-output-printed-once v0.1.0 (C:\Users\Steve Klabnik\src\wasm-pack\target\t\.tmpIDGnTq\wasm-pack)
    Finished dev [unoptimized + debuginfo] target(s) in 0.32s
[INFO]: Installing wasm-bindgen...
    Finished dev [unoptimized + debuginfo] target(s) in 0.05s
     Running C:\Users\Steve Klabnik\src\wasm-pack\target\wasm32-unknown-unknown\debug\deps\test_output_printed_once-979186abd982b0c1.wasm
error: could not execute process `C:\Users\Steve Klabnik\src\wasm-pack\target\test_cache\wasm-bindgen-de1b2fa2130aaa0c\wasm-bindgen-test-runner.exe "C:\Users\Steve Klabnik\src\wasm-pack\target\wasm32-unknown-unknown\debug\deps\test_output_printed_once-979186abd982b0c1.wasm"` (never executed)

Caused by:
  The system cannot find the file specified. (os error 2)
Error: Running Wasm tests with wasm-bindgen-test failed
Caused by: failed to execute `cargo test`: exited with exit code: 101
```
', C:\Users\Steve Klabnik\.cargo\registry\src\github.com-1ecc6299db9ec823\assert_cmd-0.11.1\src\assert.rs:353:17

failures:
    build::build_with_and_without_wasm_bindgen_debug
    test::cdylib_not_required
    test::it_can_find_a_webdriver_on_path
    test::it_can_run_browser_tests
    test::it_can_run_node_tests
    test::it_can_run_tests_with_different_wbg_test_and_wbg_versions
    test::renamed_crate_name_works
    test::test_output_is_printed_once_in_both_stdout_and_failures

test result: FAILED. 53 passed; 8 failed; 0 ignored; 0 measured; 0 filtered out

debug is failing on all builds- the test failures on missing files seem specific here

this may be related to #611

@rylev any chance you could try to repro this?

@ashleygwilliams sorry I didn't see this before. I cloned the repo on a test box I have and ran cargo test and got the following output: https://gist.github.com/rylev/03e58d81941c3b8eb004102d94f02b31
Not sure why the tests fail in this case...


Pervasive sloppy initialization order

Sorted and uniqed list of warnings about potentially incorrect initialization order. There are a ton of these, and while most of them are probably harmless, a few are probably bugs, and the sheer volume is masking actually problematic issues.
field_order_errors_uniq.txt

yeah, did one bacth https://github.com/GarageGames/Torque3D/pull/1805 before I started going nuts from the repetition, Haven't finished there. Apologies.

No worries, it's my hope that posting this list will inspire a bit of crowd sourcing effort rather than the burden falling on one person....


az role assignment list breaks with trailing slash

Describe the bug
When providing a --scope argument to az role assignment list, if a trailing slash is accidentally included, the CLI gives a non-descriptive error "Invalid scope. Please use --help to view the valid format."
To Reproduce
Using a valid subscription, run e.g.
$ az role assignment list --scope /subscriptions/<subscription_id>/resourceGroups/<resource_group>/
Invalid scope. Please use --help to view the valid format.

Expected behavior
Our customer expected either a clear error or this to remove the trailing slash and work as intended.
When you run the help command, it isn't entirely obvious that a trailing slash is not supported:
$ az role assignment list -h
...
    --scope                          : Scope at which the role assignment or definition applies to,
                                       e.g., /subscriptions/0b1f6471-1bf0-4dda-aec3-111122223333,
                                       /subscriptions/0b1f6471-1bf0-4dda-
                                       aec3-111122223333/resourceGroups/myGroup, or
                                       /subscriptions/0b1f6471-1bf0-4dda-aec3-111122223333/resourceG
                                       roups/myGroup/providers/Microsoft.Compute/virtualMachines/myV
                                       M.

Environment summary
$ az --version
azure-cli                         2.10.1

command-modules-nspkg              2.0.3
core                              2.10.1
nspkg                              3.0.4
telemetry                          1.0.4

...

Your CLI is up-to-date.

Additional context
An Azure Red Hat OpenShift customer encountered this issue when they needed to update role assignments on a VNet and a trailing slash was accidentally included in the commands run. The error provided was not helpful and they were not able to determine the cause of the error without support.

add to S175

This is as designed. There are many possible errors that could a user commit, it would be difficult to address them all.

I don't really agree as the URL is valid both with and without trailing slash.


Some questions and a suggestion

Hi Yunpeng, just read your paper and have a couple of quick questions:

Why do you implement batchnorm + relu before the convolution in the BN_AC_CONV3D class here?

In your paper you say: we set  the  number  of  the  first-layer  output  channels  to  be  4  times  smaller  than its  input  channels, ...
Hence, shouldn't this line be written as shown below?

# current version: num_ix = int(num_mid/4)
num_ix = int(num_in/4)

I believe self.conv_i1 and self.conv_i2 are the layers for the multiplexer. Or am I getting it wrong?

This is a theoretical question: is the role of multiplexer to rearrange information across channels so as to minimize information loss for each fiber?

Lastly, a small suggestion: since you are using PyTorch v0.4, you need not use Variable anymore. Hence you can write this line as:
data = torch.randn(1,3,16,224,224)
Thank you.

Hi @vinsis,
Thank you for the questions.

We put "batchnorm + relu" before each convolution layer since it is more clear and easier to design. It is actually following this paper from Kaiming. We haven't tried putting them after the convolution, but it should give the same or even better performamce, see here.

You are right. Please refer to the code for the correct version. We will update the paper soon. Thank you for pointing it out.

Multiplexer can pass information across fibers, so that features learned by one fiber can be seen by other fibers. It has the effect of increasing the overall learning capacity and minimize information loss.

Thank you for the suggestion.

Thank you.

Thanks @cypw for replying. Closing the issue now.


Use f2c translations of LAPACK when no Fortran compiler is available

translations done with a modified version of the f2clapack script from PRIMME (which in turn based on the one from f2clapack)
and additional hand-editing to work around use of F90 idiom in current LAPACK.

the current translation drops OpenMP parallelism from the few .F files that used it (f2c limitation, could be put back by hand)
currently omits cgbrfsx,cgerfsx,cherfsx,cporfsx,csyrfsx, zgbrfsx,zgerfsx,zherfsx,zporfsx,zsyrfsx due to TRANSFER intrinsic
LAPACK-TEST currently shows failures in ?gelsd only observed with gcc7.5.0
need to update most files to support INTERFACE64 - right now only the absolute minimum needed to run DGESVD (as used to prepare the DGEMM "kernel_regress" test in openblas_utest) is updated as a proof of concept
currently does not work with MSVC (which uses structs to represent complex numbers)
fixes  #3509 and fixes #1284

This looks awesome! Will there be support to build this with cmake too?

The last bunch of additions contained the cmake-related changes. However  I've neglected to support the INTERFACE64 option so far(which is probably the reason for the failed checks on Mac).

The last bunch of additions contained the cmake-related changes.

Ah, I overlooked the changes in cmake/lapack.cmake. Thanks! A slightly related note, currently when setting ONLY_CBLAS=ON in cmake, then system.cmake will set NO_LAPACK to 1, which disables include("${PROJECT_SOURCE_DIR}/cmake/lapack.cmake") in CMakeLists.txt.
So maybe a change is required around https://github.com/xianyi/OpenBLAS/blob/1ef97c470ccf23d06d3bb0597c52df4a2e9093b9/cmake/system.cmake#L122?
I'm not 100% certain I understand the implications of BUILD_WITHOUT_LAPACK, BUILD_WITHOUT_CBLAS, NOFORTRAN, ONLY_CBLAS and C_LAPACK well enough to propose something, but there seems to be some overlap between NOFORTRAN, ONLY_CBLAS and C_LAPACK?

In any case, I can confirm that this PR works like magic to enable use of lots of BLAS functionality on Android (cross-compiled with NDK r23b using a pure cmake build).

@emmenlau can you explain the process you used to xc and use on Android?
I tried to xc via:
export NDK=/path/to/NDK/r23b
make HOSTCC=gcc CC=$NDK/toolchains/llvm/prebuilt/linux-x86_64/bin/aarch64-linux-android28-clang NO_FORTRAN=1 TARGET=ARMV8
make PREFIX=$NDK/toolchains/llvm/prebuilt/linux-x86_64/sysroot/openblas_f2c_lapack install

But I'm not sure if I'm building with the right command or installing in a good location?

@danielcjacobs , I build using cmake. My cmake build instructions are a bit generalized because they come from a continuous integration system. But I think they should work for anyone, if you adjust the paths accordingly. My Android SDK is in /opt/android-sdk, and I have NDK 23.1.7779620 installed. The build is for arm64-v8a and platform android-31.
cmake /home/user/src/ffts -GNinja \
    -DCMAKE_INSTALL_PREFIX=/data/user/Debug \
    -DCMAKE_BUILD_TYPE=Debug \
    -DCMAKE_CXX_STANDARD=17 \
    -DCMAKE_CXX_STANDARD_REQUIRED=ON \
    -DCMAKE_POSITION_INDEPENDENT_CODE=ON \
    -DANDROID_SDK_ROOT="/opt/android-sdk" \
    -DCMAKE_TOOLCHAIN_FILE="/opt/android-sdk/ndk/23.1.7779620/build/cmake/android.toolchain.cmake" \
    -DANDROID_PLATFORM=android-31 \
    -DANDROID_ABI=arm64-v8a \
    -DBUILD_SHARED_LIBS=OFF \
    -DENABLE_SHARED=OFF \
    -DENABLE_STATIC=ON \
    -DENABLE_DOUBLE=OFF \
    -DENABLE_AVX=OFF \
    -DENABLE_NEON=OFF \
    -DENABLE_VFP=OFF \
    -DDISABLE_DYNAMIC_CODE=ON

@danielcjacobs perhaps try adding C_LAPACK=1 to your build options (I have not tried cross-compiling, or indeed compiling on Android with these changes yet, could be there is still a spot where NO_FORTRAN categorically means NO_LAPACK).
Note this is still very much a work in progress - on x86_64 it passes all tests in the LAPACK testsuite except for the GELSD functions, but I have not checked other platforms.

Ah, both NO_FORTRAN=1 and C_LAPACK=1 "work", I was just on the wrong branch lol.
Except it doesn't actually succeed, as I get the following error when running the make command I posted above:
/home/djacobs/Android/Sdk/ndk/23.1.7779620/toolchains/llvm/prebuilt/linux-x86_64/bin/aarch64-linux-android28-ranlib: No such file or directory

There is a file called llvm-ranlib, and older NDK versions have aarch64-linux-android-ranlib, but aarch64-linux-android28-ranlib doesn't exist. Is there a way to specify the RANLIB path like I do with the CC argument?

@danielcjacobs , I build using cmake. My cmake build instructions are a bit generalized because they come from a continuous integration system. But I think they should work for anyone, if you adjust the paths accordingly. My Android SDK is in /opt/android-sdk, and I have NDK 23.1.7779620 installed. The build is for arm64-v8a and platform android-31.  I tried cmake --install .., but I get CMake Error: Error processing file: /home/user/src/OpenBLAS/cmake_install.cmake

Everything works for me smoothly. I use ninja as I was saying, so after cmake I run:
ninja -j8
ninja install

and thats it. Can you share your actual commands the exact errors you're getting?

ah ninja install worked, so I'll just go with that!
Just to summarize, here's what I did:
cmake \
    /home/user/src/OpenBLAS \
    -GNinja \
    -DCMAKE_INSTALL_PREFIX=/home/user/installed_openblas \
    -DCMAKE_CXX_STANDARD=17 \
    -DCMAKE_CXX_STANDARD_REQUIRED=ON \
    -DCMAKE_POSITION_INDEPENDENT_CODE=ON \
    -DANDROID_SDK_ROOT="/path/to/Android/Sdk" \
    -DCMAKE_TOOLCHAIN_FILE="/path/to/ndk/23.1.7779620/build/cmake/android.toolchain.cmake" \
    -DANDROID_PLATFORM=android-28 \
    -DANDROID_ABI=arm64-v8a \
    -DBUILD_SHARED_LIBS=ON \
    -DBUILD_TESTING=ON \
    -DUSE_OPTIMIZED_BLAS=OFF \
    -DBUILD_WITHOUT_LAPACK=OFF \
    -DBUILD_WITHOUT_CBLAS=OFF \
    -DNOFORTRAN=ON \
    -DONLY_CBLAS=OFF \
    -DC_LAPACK=ON
~~cmake .~~
~~cmake --install .~~ # didn't work (see above error)
ninja -j8
ninja install

@martin-frbg when you get this fully working, would you be willing to add a note to the “compile for Android” docs on using clapack?

Is this change also necessary?
--- OpenBLAS-0.3.20/cmake/lapack.cmake.orig	2022-03-20 12:57:35.728321300 +0100
+++ OpenBLAS-0.3.20/cmake/lapack.cmake	2022-03-20 13:08:48.512121500 +0100
@@ -990,4 +990,8 @@
 foreach (LA_FILE ${LA_GEN_SRC})
   list(APPEND LA_SOURCES "${NETLIB_LAPACK_DIR}/TESTING/MATGEN/${LA_FILE}")
 endforeach ()
-set_source_files_properties(${LA_SOURCES} PROPERTIES COMPILE_FLAGS "${LAPACK_FFLAGS}")
+if (NOT C_LAPACK)
+  set_source_files_properties(${LA_SOURCES} PROPERTIES COMPILE_FLAGS "${LAPACK_FFLAGS}")
+else ()
+  set_source_files_properties(${LA_SOURCES} PROPERTIES COMPILE_FLAGS "${LAPACK_CFLAGS}")
+endif ()

I think so (FFLAGS not identical to CFLAGS)

I think so (FFLAGS not identical to CFLAGS)

One additional data point: Compilation with clang for Windows 32-bit i686 fails without that change. But it succeeds with it.
The error is:
clang: error: unknown argument: '-mincoming-stack-boundary=2'

Re-reading the last few comments, I realize this was kind of ambiguous. Trying again:
Would you like to amend your PR with this change?
--- OpenBLAS-0.3.20/cmake/lapack.cmake.orig	2022-03-20 12:57:35.728321300 +0100
+++ OpenBLAS-0.3.20/cmake/lapack.cmake	2022-03-20 13:08:48.512121500 +0100
@@ -990,4 +990,8 @@
 foreach (LA_FILE ${LA_GEN_SRC})
   list(APPEND LA_SOURCES "${NETLIB_LAPACK_DIR}/TESTING/MATGEN/${LA_FILE}")
 endforeach ()
-set_source_files_properties(${LA_SOURCES} PROPERTIES COMPILE_FLAGS "${LAPACK_FFLAGS}")
+if (NOT C_LAPACK)
+  set_source_files_properties(${LA_SOURCES} PROPERTIES COMPILE_FLAGS "${LAPACK_FFLAGS}")
+else ()
+  set_source_files_properties(${LA_SOURCES} PROPERTIES COMPILE_FLAGS "${LAPACK_CFLAGS}")
+endif ()

My primary focus is on getting the xGELSD functions to pass their tests (on x86_64, but I expect other platforms to be mostly the same unless their lapack-test was already broken before)

I applied the changes from this PR on top of ad4598143bfbf77acd16f4ae884462edc69b496e locally with the additional change from https://github.com/xianyi/OpenBLAS/pull/3539#issuecomment-1073238003 (otherwise it wouldn't compile).
In msys2's CLANG64 build environment, configured with (similar to the configuration used for the OpenBLAS shipped by msys2):
cmake -DBUILD_SHARED_LIBS=ON -DBUILD_STATIC_LIBS=ON -DDYNAMIC_ARCH=ON -DUSE_THREAD=ON -DNUM_THREADS=64 -DTARGET=CORE2 -DBINARY=64 -DINTERFACE64=1 -DC_LAPACK=ON ..

Unfortunately, ctest still segfaults. Test log:
LastTest.log
gdb backtrace from the crash:
Thread 1 received signal SIGSEGV, Segmentation fault.
0x00007ff6899ac43e in dnrm2_k_ZEN ()
(gdb) bt
#0  0x00007ff6899ac43e in dnrm2_k_ZEN ()
#1  0x00007ff689b38c89 in dnrm2_ ()
#2  0x00007ff689b322e8 in dlarfg_ ()
#3  0x00007ff689b27dd6 in dgebd2_ ()
#4  0x00007ff688249e99 in dgebrd_ ()
#5  0x00007ff68822a6b0 in dgesvd_ ()
#6  0x00007ff6881e6d69 in LAPACKE_dgesvd_work ()
#7  0x00007ff68816d5dc in LAPACKE_dgesvd ()
#8  0x00007ff6881663ba in __ctest_kernel_regress_skx_avx_run ()
#9  0x00007ff688161f4f in ctest_main ()
#10 0x00007ff6881621fe in main ()

This was on:
PS> Get-CIMInstance -Class Win32_Processor | Select-Object -Property Name

Name
----
AMD Ryzen 7 5800X 8-Core Processor

Did I do something wrong?

No idea, may even be unrelated to the LAPACK integer size (that test uses CBLAS_DNRM2 to check the output of a round-trip calculation involving LAPACKE_DGESVD and CBLAS_DGEMM). Does it also fail with the Fortran LAPACK ?

Does it also fail with the Fortran LAPACK ?

The CLANG64 build environment doesn't have a Fortran compiler. So, I rebuild (without -DC_LAPACK=ON) in a new build tree with the MINGW64 build environment. With that configuration ctest didn't segfault, and all tests did pass.
To rule out that the segfault depends on the build tools (LLVM vs. GCC toolchain), I rebuilt in a new build tree with the MINGW64 build environment but this time with -DC_LAPACK=ON. With that configuration, the first test resulted in a segfault again. And it looks like it is now stuck indefinitely at Start  39: SSVD:_Testing_Singular_Value_Decomposition_routines. The other tests up to that point (excluding the first one that resulted in a segfault) did pass.
So, there might be an issue with the 64-bit indexing version of C_LAPACK (at least on Windows).

Fixed a few files I had missed in the big edit for INTERFACE64, but probably not the cause of the utest failure.

Built again with -DCMAKE_BUILD_TYPE=Debug after updating to your latest changes:
TEST 34/34 kernel_regress:skx_avx
Thread 6 received signal SIGSEGV, Segmentation fault.
[Switching to Thread 12812.0x3380]
0x00007ff6a72a8fb0 in dscal_kernel_8_zero (n=27111981056, alpha=0xd4de1ffa98, x=0x2b585b24020) at D:/OpenBLAS/kernel/x86_64/dscal_microk_haswell-2.c:150
150             __asm__  __volatile__
(gdb) bt
#0  0x00007ff6a72a8fb0 in dscal_kernel_8_zero (n=27111981056, alpha=0xd4de1ffa98, x=0x2b585b24020)
    at D:/OpenBLAS/kernel/x86_64/dscal_microk_haswell-2.c:150
#1  0x00007ff6a72a93b0 in dscal_k_ZEN (n=27111981056, dummy0=0, dummy1=0, da=-0, x=0x2b585b24020, inc_x=1, y=0x0, inc_y=0, dummy=0x0, dummy2=0)
    at D:/OpenBLAS/kernel/x86_64/dscal.c:217
#2  0x00007ff6a63aaa2d in legacy_exec (func=0x7ff6a72a91da <dscal_k_ZEN>, mode=32771, args=0xd4dd7fb6c8, sb=0x282bdb70000)
    at D:/OpenBLAS/driver/others/blas_server_win32.c:99
#3  0x00007ff6a63ab024 in blas_thread_server (arg=0x1) at D:/OpenBLAS/driver/others/blas_server_win32.c:318
#4  0x00007fffbb7c54e0 in KERNEL32!BaseThreadInitThunk () from C:\Windows\System32\kernel32.dll
#5  0x00007fffbc9c485b in ntdll!RtlUserThreadStart () from C:\Windows\SYSTEM32\ntdll.dll
#6  0x0000000000000000 in ?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
(gdb)

It crashes in a different function now.
That value of n looks pretty high. Is it supposed to be this large?

This took me a while. But I think I finally got it.
OS_WINDOWS and __64BIT__ are never defined in the C_LAPACK sources. I find them defined in config.h and config_kernel.h. But those aren't included in these "upstream" files.
That means that integer in those files is long (but it should be long long on Windows 64-bit).
Should the following be used instead on all files in the conditions that select how to typedef BLASLONG and BLASULONG and also for blasabs(x)?
-#if defined(OS_WINDOWS) && defined(__64BIT__)
+#if defined(__WIN64)

Ah, sorry, I copied that block from common.h but it would need config.h to see OS_WINDOWS... no wonder I could not reproduce this on Linux. (I'm still trying to track down the xGELSD bug)

I don't see the failure in xGELSD. Is that part of the tests run by ctest?

Yes, the LAPACK testsuite - but only available if you have a Fortran compiler installed as the testsuite is not translated. I'm currently working with a gmake build, but I guess with ctest you would see e.g. one test in the 40s or 50s range failing (SLS)

Oh sh... it is a gcc problem. Present with 7.5 (suse 15.x default) and absent from at least 10.2 onwards. I really need to take some time off as soon as possible.

Now I wonder why MSVC's inability to handle _Complex has not come up earlier...

This would already be very useful for the CLANG* build environments in MSYS2 in its current state.
Do you think it could make sense to disable C_LAPACK for MSVC for now (and maybe fix that in a follow up)?

Thanks for the recent changes regarding MSVC and C_LAPACK (or rather their mutual exclusivity for the time being).
I noticed the last couple of changes were related to an issue with clang-cl (MSVC) & flang on Windows. IIUC, that is probably because some tests are run now (after #3595 has landed) that have been skipped previously.
Are those failing tests a blocker for this PR?

not a blocker, i just noticed them in the context and wanted to make sure they are unrelated. different pr for that now, will clean up here later when i have time

translations done with a modified version of the f2clapack script from PRIMME (which in turn based on the one from f2clapack)
and additional hand-editing to work around use of F90 idiom in current LAPACK.

@martin-frbg in case you still your modified f2clapack script easy accessible, I would be interested to take a look at it. I am guessing the PRIMME script you started from is https://github.com/primme/primme/blame/master/R/f2clapack.sh?
In a Pyodide context I have been trying to use OpenBLAS (see https://github.com/pyodide/pyodide/pull/3331 for more details). Being able to look at the f2c conversion script (or even run it if possible) you used for OpenBLAS, may help in some cases to reduce the discrepancy we are seeing between some f2c'ed scipy files and OpenBLAS.

yes that is what I started from, need to  clean up a few hacks that I hand-corrected in the converted files afterwards... mostly fixing some of the fortran function macros from the header part of the primme script that had bad variable types and adding implementations for some complex functions

OK so you changed mostly the header part of the primme script and then modified by hand?
I was wondering whether you changed the lex part too, in order to fix some signatures (full disclosure I don't understand what the lex part of the script does).

This should be it - sorry for the delay. Obviously some of the changes are OpenBLAS-specific (like the "blasint" typedef) and some of the (complex function) declarations will lead to "unused function" warnings during compilation, so there is certainly still room for improvement
f2clapack.sh.txt

Thanks a lot for the update!


Multiple streams from one device?

I'm building a media server that uses castnow for playback and was wondering if there is a way to have 2 streams run from the same device. When I try to cast to the second device i get a address already in use error. Is there anyway around this? I know its possible, but i'm not sure if it's supported by castnow.
It appears the error is because the port is already being used. I can't seem to find a way to specify a port.

Damn, so that's why I can't play to more than one Chromecast Audio at a time?
Is there likely to be a fix for this?

Pull request #165 which has been merged to master allows for the specification of port numbers.  You can run each instance of castnow on a different port, which would prevent your address already in use errors.

That's fantastic! Thank you!
On Oct 27, 2016 11:33 AM, "Jim Finn"<EMAIL_ADDRESS>wrote:

Pull request #165 https://github.com/xat/castnow/pull/165 which has
been merged to master allows for the specification of port numbers. You can
run each instance of castnow on a different port, which would prevent your
address already in use errors.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/xat/castnow/issues/156#issuecomment-256698539, or mute
the thread
https://github.com/notifications/unsubscribe-auth/APlTiU2q0pd3Esbl7u-ChTUGQGNrxztJks5q4NJegaJpZM4JI6s7
.


When i am importing the project it is giving error Error:(7, 1) A problem occurred evaluating project ':sample'. > Missing youtube.properties, check the youtube.properties.sample file. please tell how to solve it.

@GauravPandey123 I've updated the README.md in the PR #8
Let me know if this helps out, or if you need more information.


input ( type="DatePicker") don't show on ios 17.0（Xcode Simulator）

The almost identical code on different drives has different displays.
mabye it's a bug or just i written a wrong code.

  def render(assigns, %{"target" => "ios"}) do
     ...
     <HStack spacing={12}>
                <.button phx-click="previous_date" style="padding(.horizontal, 10);padding(.vertical, 5)">
                  previous
                </.button>
              <.simple_form for={@date_form} id="date-form" phx-change="change_date">
              <.input
                field={@date_form[:selected_date]}
                type="DatePicker"
                selection={@selected_date |> Date.to_iso8601()}
                displayedComponents={"date"}

              />
              </.simple_form>

                <.button phx-click="next_date" style="padding(.horizontal, 10);padding(.vertical, 5)">
                  next
                </.button>
              </HStack>
       ....
  end

  def render(assigns, _interface) do
...

 <HStack spacing={12}>
                <Button phx-click="previous_date">
                  <Text>previous</Text>
                </Button>
              <.simple_form for={@date_form} id="date-form" phx-change="change_date">
              <.input
                field={@date_form[:selected_date]}
                type="DatePicker"
                selection={@selected_date |> Date.to_iso8601()}
                displayedComponents={"date"}
                style="frame(width: 250)"

              />
            </.simple_form>

                <Button phx-click="next_date">
                  <Text>next</Text>
                </Button>
              </HStack>
...
end

Library Version
0.3
Xcode Version
Version 15.4 (15F31d)
Swift Version
swift-driver version: <IP_ADDRESS> Apple Swift version 5.10 (swiftlang-<IP_ADDRESS> clang-15<IP_ADDRESS>) Target: arm64-apple-macosx14.0
On which device or simulator are you running into the problem?
MacOS
Target Device Operating System Version
macos 14.2.1 (23C71)

2 things you may want to check:

Try using a <.form> component instead of <.simple_form>. My guess is you're seeing the Form element's List UI on iOS there, and you'd have to scroll down in that little box to find the date picker.
If you're passing field to the <.input> component, there's no reason to pass selection as well since the core component will do that for you.

Here's what the layout you provided looks like when I render it locally:

You can see the Form element's list interface in the middle. You probably want to just use <.form> if you don't want any styling applied. Or you can customize the <.simple_form> component.

Here's what the layout you provided looks like when I render it locally:

You can see the `Form` element's list interface in the middle. You probably want to just use `<.form>` if you don't want any styling applied. Or you can customize the `<.simple_form>` component.

when i use .form instead .simple_form .it fix.

2 things you may want to check:

Try using a <.form> component instead of <.simple_form>. My guess is you're seeing the Form element's List UI on iOS there, and you'd have to scroll down in that little box to find the date picker.
If you're passing field to the <.input> component, there's no reason to pass selection as well since the core component will do that for you.

I do this because I need local time zone data. If I delete this line, it will pass UTC time zone data. Maybe there's a problem with my OS time zone settings? I am not sure about that.

I would suggest moving the logic to the handle_event.


tx_byte_pool service fragmentation problem

Test method:

Thread A allocate memory blocks in a 1ms cycle (size takes a random value of 1~1024).  When allocate fails, the thread is suspended; 2. Thread B release memory blocks in a 1~10ms cycle. When all memory blocks are released, Restore thread A.

As shown in the above test results,
tx_byte_allocate fail, rt:0x10 size:859 frag:208 available:2068
memory msg, frag:208 available:50184
memory msg, frag:208 available:98276
all memory be release, frag:208 available:102392
All memory blocks have been released, why is the frag field not reduced? Are memory blocks at adjacent addresses not merged?
Looking forward to your reply, thank you.

Adjacent free memory blocks are merged together during a subsequent allocation search for a large enough free memory block. This process is called defragmentation.

https://learn.microsoft.com/en-us/azure/rtos/threadx/chapter3#memory-byte-pools

As @xray-bit says, the defragmentation happens upon allocation scheme and not free scheme.
This is because in free time there is no need to waste time to look on other blocks, while in allocation time we anyway go block after block to find one that is big enough so meanwhile we also merge consecutive free blocks till we find big enough block and stop.

OK, thanks for your reply.


FLEX-4856 ~ Updates Spring Data JPA to 1.11.21.RELEASE.

https://mvnrepository.com/artifact/org.springframework.data/spring-data-jpa/1.11.21.RELEASE

retest this please


Meeting some problem when tuning

Hello, thank you for your sharing!
When I try to run tuning, I found there was something unclear in README.
/path/to/precomputed_optical_flow/
/path/to/output_file
/path/to/tmp_folder/
/path/to/mots_eval/
association_type
num_iterations
Could you explain these paths more in detail?
thank you, very much!

Hey!
Sorry for the missing explanation! I have updated the Readme with more information, see also issue #12 . In addition, association_type should be ´reid´ and ´num_iterations´ should be ´1000´ to have the default configuration from the paper. For ´/path/to/mots_eval´, check out the mots_eval repository and supply the path here.
Please reopen if there are further questions.


kubecfg: 0.26.0 -> 0.27.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/kubecfg/kubecfg/releases.
meta.description for kubecfg is: "A tool for managing Kubernetes resources as code"
meta.homepage for kubecfg is: "https://github.com/kubecfg/kubecfg"
meta.changelog for kubecfg is: ""
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.27.0 with grep in /nix/store/mnjyvcpvcr2wlj5xwy3hhck5ksmxrn73-kubecfg-0.27.0
found 0.27.0 in filename of file in /nix/store/mnjyvcpvcr2wlj5xwy3hhck5ksmxrn73-kubecfg-0.27.0

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
kubecfg

Instructions to test this update (click to expand)

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

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

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

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

kubecfg

Maintainer pings
cc @benley for testing.

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

1 package built:

kubecfg


Improve ITI-67 to ITI-18 conversion

https://github.com/i4mi/MobileAccessGateway/blob/6363161b8e2b890137ee3b043a85d7c843476329/src/main/java/ch/bfh/ti/i4mi/mag/mhd/iti67/Iti67RequestConverter.java#L63-L75
In the ITI-67 request processing, if the id or identifier search parameter is used, all others are ignored.
id is not an official ITI-67 search parameter.
identifier is then mapped to uniqueId or entryUuid depending on if it's a UUID or an OID, which is suspicious because the uniqueId can be both a UUID or an OID. We should do two GetDocuments queries to make sure we get all documents.

@unixoid : we need to look at this because the mapping for fhir resource.id to XDS.DocumentEntry.logicalId


Add link for KituraLimiter to the "Other Middlewares" section of the API docs

Not sure if you guys accept pull requests from people outside IBM, but I made a SwiftRedis-based middleware to rate limit client requests. You can check out my repo here. Is there any interest in merging a link to it on kitura.io? Someone might find it useful 👍

Hi @teechap yes we do welcome PRs and I'd be happy to merge this.  We do need a CLA though - this is a one-time thing.  Would you be willing to email one to us?  Thanks!

Sure, I'll email you the CLA later today...

@ianpartridge it says to physically mail the CLA--I don't see an email. What email should I send the scanned CLA to?

@ianpartridge oops, I just saw the email. My bad!

Thanks!


Codeblock generate cow with empty rows

With the new data (2023-10-20) Cow nr 12 in prolonged problematic behaviour got 0 events when data is printed with the below codeblock. This then cause failure by division by 0 in the next step..

periods = [1, 2]
# fetch enough data points from lactation period 1&2
# mean_totalTimeCost_1 = 0
# mean_totalTimeCost_2 = 0
Path(dataDir/'prolonged_problematic_targetCows').mkdir(parents=True, exist_ok=True)
for p in periods:
    Path(dataDir/'prolonged_problematic_targetCows'/str(p)).mkdir(parents=True, exist_ok=True)

# save target cows tables to directory
for i, cow_id in enumerate(cow_list):
    for p in periods:
        single_cow_merge = data_collector(traffic, gigacow, lactation, cow_id, [p])
        single_cow_merge = single_cow_merge.loc[(single_cow_merge.DaysInMilk < 40)]

        single_cow_merge["id"] = i+1
        # Check if the DataFrame has rows before saving
        fileName = 'prolonged_problematic_targetCows/' + str(p) + '/cow_' + str(i) + '.csv'
        single_cow_merge.to_csv(dataDir/fileName)
    #fileName = 'memory_targetCows/cow_' + str(i) + '.csv'
    #single_cow_merge.to_csv(dataDir/fileName, index=False)

print("num of cows: ", len(cow_list))
# print("Mean of total time cost at lactation period 1: ", mean_totalTimeCost_1/len(cow_list))
# print("Mean of total time cost at lactation period 2: ", mean_totalTimeCost_2/len(cow_list))

I solved it with the merged clean version of the repository.


Create separate migration user for Prod DB

Please create separate DB accounts on the production "ComplaintTracking" database for cts_app_user with only DML rights and cts_migrations with DDL rights (plus select and insert). The changes should be the same as what was recently done on Dev (#738) and UAT (#767). Please keep the password for cts_app_user unchanged.

@dougwaldron requested is completed. Please verify at your connivence.
for cts_migrations password https://github.com/gaepdit/app-config/blob/main/sql-server-accounts.md

Everything looks good 👍🏼


Why do the categorical features need to be encoded as non-negative integers?

I understand LightGBM can deal with categorical features in an efficiency way. However, the document says that the categorical features must be encoded as non-negative integers. Why?
Thanks!

Please refer to https://lightgbm.readthedocs.io/en/latest/Parameters.html#categorical_feature

Note: using large values could be memory consuming. Tree decision rule works best when categorical features are presented by consecutive integers starting from zero
Note: all negative values will be treated as missing values

and to #1636.

Please refer to https://lightgbm.readthedocs.io/en/latest/Parameters.html#categorical_feature

Note: using large values could be memory consuming. Tree decision rule works best when categorical features are presented by consecutive integers starting from zero
Note: all negative values will be treated as missing values

and to #1636.

Thanks!


[BEAM-1319] Add conflict resolution to the PipelineOptions internal argparse.

In some instances where a PipelineOptions subclass was defined in the
main session and save_main_session option is enabled, that subclass may
appear multiple times in the PipelineOptions.subclassess() list.
This is causing problems with the argparse because options are not
unique any more.
This changes filter the subclasses by name, and pick the last unique
instance of each subclass.
As an alternative option, we could use the conflict_handler='resolve' of
the argparse. However, the drawback of this approach would be that allowing
accidental overriding of the same option name in two different PipelineOptions
subclasses.
Also moves wordcount example to use PipelineOptions. This both serves as an
example of using PipelineOptions, also it is already integrated with
tests and will continue to test this case.

R: @chamikaramj


Fix normalize-send when sending object data, add test

This should close https://github.com/thoov/mock-socket/issues/245
However...I am not sure if this is actually desired behavior for non-socketIO clients - but I'm pretty sure the native browser WebSocket spec only supports sending stringified messages, so this is probably OK to merge

Thanks for putting this pull up, @viggyfresh


GooglePlus Bridge images

Are images in the post stripped by this bridge? I only see text but no images.

Yes, they are indeed stripped by the bridge:
https://github.com/RSS-Bridge/rss-bridge/blob/ce896b424775ad3c629b391bede1c63472e10bd6/bridges/GooglePlusPostBridge.php#L98
I can see how this would make it useless for some feeds. Would it be okay to attach the images via enclosures or is it necessary to have them in the text?

TBH I am not sure how enclosures work. To ppi eyes how would enclosure vs "in the text"  look/work?

If the use of enclosures make the feed more "flexible" (i.e.: feed having multiple resolution pics), then I guess use of enclosures would be best for general purpose?
Sent from Mailspring (https://getmailspring.com/), the best free email app for work
On Jul 29 2018, at 4:24 pm, LogMANOriginal<EMAIL_ADDRESS>wrote:

Here is an example of how a combined solution looks (notice the 'Attachments' section under the picture):
-- action=display&bridge=Flickr&q=bird&format=Html
In this particular example, a smaller sized version is inlined (because there is no other content). This is a good solution when pictures are made available in multiple resolutions. The original size is made available via enclosures.
This is the HTML version, where enclosures are listed under 'Attachments'. Here is the same feed in ATOM:
I took both screen-shots in Firefox. A "real" feed reader is very likely to use enclosures for previews.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub (https://github.com/RSS-Bridge/rss-bridge/issues/600#issuecomment-408681288), or mute the thread (https://github.com/notifications/unsubscribe-auth/ANZ6uokblNeLNKbLXFmAhBfSCwV-mR1cks5uLcW7gaJpZM4QnSqu).

Generally yes. The question is: Do you need the picture in the text as well?
Right now the pictures are removed by the bridge. One solution is to just have the pictures made available via enclosures and still not have them displayed in the text. Depending on the contents you want to generate feeds for, this could improve readability or make it worse...
Now that I think about it, an option to enable/disable that behavior is likely the best way to go about it.

If you can toggle the behaviour that would be great!
Thanks much for looking into this :)
Sent from Mailspring (https://getmailspring.com/), the best free email app for work
On Jul 29 2018, at 4:40 pm, LogMANOriginal<EMAIL_ADDRESS>wrote:

Generally yes. The question is: Do you need the picture in the text as well?
Right now the pictures are removed by the bridge. One solution is to just have the pictures made available via enclosures and still not have them displayed in the text. Depending on the contents you want to generate feeds for, this could improve readability or make it worse...
Now that I think about it, an option to enable/disable that behavior is likely the best way to go about it.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub (https://github.com/RSS-Bridge/rss-bridge/issues/600#issuecomment-408682240), or mute the thread (https://github.com/notifications/unsubscribe-auth/ANZ6uojZVjbttSnAVwkoZSyKOnOuBtqqks5uLcligaJpZM4QnSqu).


Independent UI scaling

Hey smart people, I have no idea how to code but would love a plugin that lets us scale the UI for the chatbox and inventory separately. Is this even possible? Thanks <3

Duplicate of #6749


Major literal optimization refactoring.

The principle change in this commit is a complete rewrite of how
literals are detected from a regular expression. In particular, we now
traverse the abstract syntax to discover literals instead of the
compiled byte code. This permits more tuneable control over which and
how many literals are extracted, and is now exposed in the
regex-syntax crate so that others can benefit from it.
Other changes in this commit:

The Boyer-Moore algorithm was rewritten to use my own concoction based
on frequency analysis. We end up regressing on a couple benchmarks
slightly because of this, but gain in some others and in general should
be faster in a broader number of cases. (Principally because we try to
run memchr on the rarest byte in a literal.) This should also greatly
improve handling of non-Western text.
A "reverse suffix" literal optimization was added. That is, if suffix
literals exist but no prefix literals exist, then we can quickly scan
for suffix matches and then run the DFA in reverse to find matches.
(I'm not aware of any other regex engine that does this.)
The mutex-based pool has been replaced with a spinlock-based pool
(from the new mempool crate). This reduces some amount of constant
overhead and improves several benchmarks that either search short
haystacks or find many matches in long haystacks.
Search parameters have been refactored.
RegexSet can now contain 0 or more regular expressions (previously, it
could only contain 2 or more). The InvalidSet error variant is now
deprecated.
A bug in computing start states was fixed. Namely, the DFA assumed the
start states was always the first instruction, which is trivially
wrong for an expression like ^☃$. This bug persisted because it
typically occurred when a literal optimization would otherwise run.
A new CLI tool, regex-debug, has been added as a non-published
sub-crate. The CLI tool can answer various facts about regular
expressions, such as printing its AST, its compiled byte code or its
detected literals.
A new public method on Regex, shortest_match, was added for
providing is_match performance with some location information.

 I can't really find a downside here, so r=me whenever you're ready to go :)

A new CLI tool, regex-debug, has been added as a non-published sub-crate

I love how this is just, you know, casually tossed in there. Amazing stuff, @BurntSushi! :sushi:

Thanks! :)

This is on crates.io in 0.1.59.


Update giveaway.js

Changed entrees to user

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


fix(api): return proper json response on 409 conflict with plugins

The plugin schema returned the wrong error format which was not rendered as json.

updated two tests to match the fix
added a test to check for json content

Fix #2014

Sweet, manually merged with

proper style
proper git commit messages
proper Changelog format


How can i have only one instance of

Be sure to search for your issue before opening a new one.
Most likely more a doubt than a issue itself
Current Behavior
When frontend changes route creates a new instance of <ReactPlayer /> and it starts to stack instances playing multiple sounds

Expected Behavior
I would like to have a single instance of <ReactPlayer /> along all frontend routes and when the route changes, use the same instance instead of recreating a new ones

Environment

URL attempting to play: /, /projects, /articles
Browser: Chrome
Operating system: Mac OS

Other Information

Project: using Nextjs

Sounds like something weird is going on with your implementation if videos continue playing after the route is unmounted.
If you still wanted one instance you would have to render <ReactPlayer /> outside of your route system somehow, and update the props when the route changes. How this works exactly will depend on your implementation and routing library used.


[FLINK-2083] [docs] [ml]  Ensure high quality docs for FlinkML in 0.9

Various fixes and additions to the docs for FlinkML

We could turn this into a WIP PR, and keep it open until 0.9 is released, in case we want to make more changes to the docs.

Looks good modulo some minor comments.
I think we can merge this PR once the comments are addressed. We can then simply open new PRs for new changes.

LGTM. Will merge it.


enhance(mainnet conf): add an lnd.conf entry for bitcoin.mainnet

Commented out as testnet is still our default.

👏 ayyy
utACK


ERROR: No suitable staging package found | do_populate_sysroot_setscene

Hello, I'm trying to build a SD card for a Microzed, but it doesn't work .
I did execute the setup_host.sh from the 2.6 branch from the xilinx github, and I have installed Vitis and Petalinux in 2020.1 version (and I used "source" before executing buildfast.sh).
However, my build fails. It succeeds building the default overlay, but when it comes to build the PYNQ SD Image, it doesn't.
The failure is due to an incapacity to find a sstate file :
NOTE: Sstate package /home/guillaume/Documents/Microzed-PYNQ-master/PYNQ-git/sdbuild/build/microzed-7020/petalinux_project/build/sstate-cache/universal/6a/e3/sstate:python3-setuptools-native:x86_64-linux:41.2.0:r0:x86_64:3:6ae3c70d422fd7132a2f013fe7a53f7a6da3303d96b54a0fb14ef662d446333d_populate_sysroot.tgz does not exist
ERROR: No suitable staging package found
DEBUG: Python function do_populate_sysroot_setscene finished
In the report log file, it can be seen that the script try to access to the .tgz file through internet, but an error 403 occurs :
Connecting to petalinux.xilinx.com|<IP_ADDRESS>|:80... connected.
HTTP request sent, awaiting response... 403 Forbidden
2023-04-21 12:46:44 ERROR 403: Forbidden.
And that for the .tgz.file it does the smae thing, but it works :
Connecting to petalinux.xilinx.com|<IP_ADDRESS>|:80... connected.
HTTP request sent, awaiting response... 200 OK
But what is strangiest, is that when I'm looking, after this failed build, in the repository /home/guillaume/Documents/Microzed-PYNQ-master/PYNQ-git/sdbuild/build/microzed-7020/petalinux_project/build/sstate-cache/universal , I find the 2 files required (the .tgz and .tgz.siginfo).
I have also try to download those files before executing buildfast.sh , but I haven't find a repository nor a path that would help the sccript to find those.
Do you have any ideas how to resolve this problem ?
Thanks,
Guillaume.

Hi Guillaume,  I have build these myself more than a few times and no issues for me but let's dig a little deeper.
First, can you try the buildfast.sh I've attached here?  I've modified it to make sure wget validates the files that are downloaded.
If the issue still exists after ensuring the integrity of the downloaded files.  Can you try to build the bsp by itself?  The bsp can be found from where buildfast.sh puts it, you can also find the bsp in the Release section of this github: https://github.com/FredKellerman/Microzed-PYNQ/releases/download/v2.6.0/microzed.bsp
Once you have the bsp file you can extract it's contents using tar -xvf ./microzed.bsp
dd into the new dir, make sure you source settings.sh for PetaLinux 2020.1 and then you should be able to just enter and execute petalinux-build.  Let me know if that has the same issue.
Kind regards,
-Fred
buildfast.zip

Hi Fred,
Somehow the building work 2h after my mail !
I think that my issue was in part due to my firewall who didn't like
downloading files from xilinx without analysing them. I retried to do the
building at 17:20 and it worked without the error that I have mentionned, I
guess that the firewall whitelisted xilinx after a few analysis, and
without this control, the building was free to complete.
However in order to understand what's going on during the building, I will
try your advices next monday.
Thanks for your reactivity,
Have a great week-end.
Guillaume
Le ven. 21 avr. 2023 à 17:27, Fred Kellerman @.***> a
écrit :

Hi Guillaume, I have build these myself more than a few times and no
issues for me but let's dig a little deeper.
First, can you try the buildfast.sh I've attached here? I've modified it
to make sure wget validates the files that are downloaded.
If the issue still exists after ensuring the integrity of the downloaded
files. Can you try to build the bsp by itself? The bsp can be found from
where buildfast.sh puts it, you can also find the bsp in the Release
section of this github:
https://github.com/FredKellerman/Microzed-PYNQ/releases/download/v2.6.0/microzed.bsp
Once you have the bsp file you can extract it's contents using tar -xvf
./microzed.bsp
dd into the new dir, make sure you source settings.sh for PetaLinux 2020.1
and then you should be able to just enter and execute petalinux-build. Let
me know if that has the same issue.
Kind regards,
-Fred
buildfast.zip
https://github.com/FredKellerman/Microzed-PYNQ/files/11297155/buildfast.zip
—
Reply to this email directly, view it on GitHub
https://github.com/FredKellerman/Microzed-PYNQ/issues/7#issuecomment-1517999806,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A4WUSUCG22BB6M45NQPXCYLXCKRNZANCNFSM6AAAAAAXG4MANM
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

:-)  That is good news!  PetaLinux fetches a lot of files from the internet and sometimes the servers can't keep up.  There is a way to setup to pre-download the sstate files but it has it's own downsides.
No need to try anything if you are up and running, you probably have more important work to do since you are customizing the image.
I cannot promise a fast turn around but we could update this to v3.0.1 PYNQ if needed.  If there are additional features you would like to see, don't hesitate to reach out.
-Fred

Hi Guillaume,
I replied and closed the github issue.
Do let me know if you cannot get it to build.  I can probably upload an SD
image to the releases tab just for you and then take it down.  I don't have
a lot of extra time and I'm not able to support a pre-built SD image for
the world.
Also keep in mind the Ethernet MAC is random each power cycle, this may
cause your DHCP server to issue a different IP address each time.  I may
have a fix for that and try it out someday, basically it needs a bsp change
in uboot to have the MAC address read from the eeprom.
Kind regards,
-Fred
On Fri, Apr 21, 2023 at 1:03 PM GuillaumeLamottedIncamps <
@.***> wrote:

Hi Fred,
Somehow the building work 2h after my mail !
I think that my issue was in part due to my firewall who didn't like
downloading files from xilinx without analysing them. I retried to do the
building at 17:20 and it worked without the error that I have mentionned, I
guess that the firewall whitelisted xilinx after a few analysis, and
without this control, the building was free to complete.
However in order to understand what's going on during the building, I will
try your advices next monday.
Thanks for your reactivity,
Have a great week-end.
Guillaume
Le ven. 21 avr. 2023 à 17:27, Fred Kellerman @.***> a
écrit :

Hi Guillaume, I have build these myself more than a few times and no
issues for me but let's dig a little deeper.
First, can you try the buildfast.sh I've attached here? I've modified it
to make sure wget validates the files that are downloaded.
If the issue still exists after ensuring the integrity of the downloaded
files. Can you try to build the bsp by itself? The bsp can be found from
where buildfast.sh puts it, you can also find the bsp in the Release
section of this github:

https://github.com/FredKellerman/Microzed-PYNQ/releases/download/v2.6.0/microzed.bsp

Once you have the bsp file you can extract it's contents using tar -xvf
./microzed.bsp
dd into the new dir, make sure you source settings.sh for PetaLinux
2020.1
and then you should be able to just enter and execute petalinux-build.
Let
me know if that has the same issue.
Kind regards,
-Fred
buildfast.zip
<
https://github.com/FredKellerman/Microzed-PYNQ/files/11297155/buildfast.zip
—
Reply to this email directly, view it on GitHub
<
https://github.com/FredKellerman/Microzed-PYNQ/issues/7#issuecomment-1517999806
,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/A4WUSUCG22BB6M45NQPXCYLXCKRNZANCNFSM6AAAAAAXG4MANM
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

—
Reply to this email directly, view it on GitHub
https://github.com/FredKellerman/Microzed-PYNQ/issues/7#issuecomment-1518107040,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALQ2MXTKUTJXUVQWIZKQAHTXCK4VHANCNFSM6AAAAAAXG4MANM
.
You are receiving this because you commented.Message ID:
@.***>

Hi Fred,
Since my last email I succeeded to build the image for an SD card, and I
have been exploring the capacities of PYNQ with the microzed.
Now I'm trying to boot PYNQ from the QSPI Flash memory (booting from the SD
Card is fine for testing but not for the expected utilisation), but I can't
find any solution that is working. Indeed I have seen that Avnet has
published a document explaining how to boot a new image of a linux kernel
(that you will find in the attachments), however I fail to generate the
.mcs file.
I have understood that the image of the linux kernel is in the "image.ub"
file generated by your script, and that it is not the only component of
this file (there is also the Flattened Device Tree Blob and the
configuration). I have try to extract those components with mkimage or dd
(OS : Ubuntu 18.0, the one that generated the PYNQ build) but I get the
feeling that it is not working.
Have you ever tried to boot PYNQ without the SD card ? Do you already know
the solution to my problem ?
Have a great day,
Guillaume
Le ven. 21 avr. 2023 à 20:34, Fred Kellerman @.***> a
écrit :

Hi Guillaume,
I replied and closed the github issue.
Do let me know if you cannot get it to build. I can probably upload an SD
image to the releases tab just for you and then take it down. I don't have
a lot of extra time and I'm not able to support a pre-built SD image for
the world.
Also keep in mind the Ethernet MAC is random each power cycle, this may
cause your DHCP server to issue a different IP address each time. I may
have a fix for that and try it out someday, basically it needs a bsp change
in uboot to have the MAC address read from the eeprom.
Kind regards,
-Fred
On Fri, Apr 21, 2023 at 1:03 PM GuillaumeLamottedIncamps <
@.***> wrote:

Hi Fred,
Somehow the building work 2h after my mail !
I think that my issue was in part due to my firewall who didn't like
downloading files from xilinx without analysing them. I retried to do the
building at 17:20 and it worked without the error that I have
mentionned, I
guess that the firewall whitelisted xilinx after a few analysis, and
without this control, the building was free to complete.
However in order to understand what's going on during the building, I
will
try your advices next monday.
Thanks for your reactivity,
Have a great week-end.
Guillaume
Le ven. 21 avr. 2023 à 17:27, Fred Kellerman @.***> a
écrit :

Hi Guillaume, I have build these myself more than a few times and no
issues for me but let's dig a little deeper.
First, can you try the buildfast.sh I've attached here? I've modified
it
to make sure wget validates the files that are downloaded.
If the issue still exists after ensuring the integrity of the
downloaded
files. Can you try to build the bsp by itself? The bsp can be found
from
where buildfast.sh puts it, you can also find the bsp in the Release
section of this github:

https://github.com/FredKellerman/Microzed-PYNQ/releases/download/v2.6.0/microzed.bsp

Once you have the bsp file you can extract it's contents using tar -xvf
./microzed.bsp
dd into the new dir, make sure you source settings.sh for PetaLinux
2020.1
and then you should be able to just enter and execute petalinux-build.
Let
me know if that has the same issue.
Kind regards,
-Fred
buildfast.zip
<

https://github.com/FredKellerman/Microzed-PYNQ/files/11297155/buildfast.zip

—
Reply to this email directly, view it on GitHub
<

https://github.com/FredKellerman/Microzed-PYNQ/issues/7#issuecomment-1517999806

,
or unsubscribe
<

https://github.com/notifications/unsubscribe-auth/A4WUSUCG22BB6M45NQPXCYLXCKRNZANCNFSM6AAAAAAXG4MANM

.
You are receiving this because you are subscribed to this
thread.Message
ID: @.***>

—
Reply to this email directly, view it on GitHub
<
https://github.com/FredKellerman/Microzed-PYNQ/issues/7#issuecomment-1518107040
,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/ALQ2MXTKUTJXUVQWIZKQAHTXCK4VHANCNFSM6AAAAAAXG4MANM
.
You are receiving this because you commented.Message ID:
@.***>

—
Reply to this email directly, view it on GitHub
https://github.com/FredKellerman/Microzed-PYNQ/issues/7#issuecomment-1518201211,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A4WUSUCKERUOVKXFYZW6Z7TXCLHKFANCNFSM6AAAAAAXG4MANM
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Hi Guillaume,
I have never attempted this as many, perhaps most ZYNQ boards do not have
enough QSPI or flash memory to accommodate PYNQ with the Ubuntu rootfs.
The older images were about 7GB and the latest 3.0.1 is around 9GB now.  Do
keep in mind that 16GB minimum is recommended for PYNQ.  The QSPI on the
Microzed is not that large.
In theory you could host fsbl, u-boot and maybe the kernel on the QSPI and
use the SD card for the rootfs.  Basically you would move what is on the
fat32 partition of the PYNQ SD card to QSPI.  But this is not
straightforward, you also need to change the linker map settings and boot
code to be correct for starting up on the QSPI as well.  To do the latter
you could study the AMD pynq makefile that builds it all and either
override that or manually do it post build.
Kind regards,
-Fred
On Tue, Jun 6, 2023 at 9:18 AM GuillaumeLamottedIncamps <
@.***> wrote:

Hi Fred,
Since my last email I succeeded to build the image for an SD card, and I
have been exploring the capacities of PYNQ with the microzed.
Now I'm trying to boot PYNQ from the QSPI Flash memory (booting from the SD
Card is fine for testing but not for the expected utilisation), but I can't
find any solution that is working. Indeed I have seen that Avnet has
published a document explaining how to boot a new image of a linux kernel
(that you will find in the attachments), however I fail to generate the
.mcs file.
I have understood that the image of the linux kernel is in the "image.ub"
file generated by your script, and that it is not the only component of
this file (there is also the Flattened Device Tree Blob and the
configuration). I have try to extract those components with mkimage or dd
(OS : Ubuntu 18.0, the one that generated the PYNQ build) but I get the
feeling that it is not working.
Have you ever tried to boot PYNQ without the SD card ? Do you already know
the solution to my problem ?
Have a great day,
Guillaume
Le ven. 21 avr. 2023 à 20:34, Fred Kellerman @.***> a
écrit :

Hi Guillaume,
I replied and closed the github issue.
Do let me know if you cannot get it to build. I can probably upload an SD
image to the releases tab just for you and then take it down. I don't
have
a lot of extra time and I'm not able to support a pre-built SD image for
the world.
Also keep in mind the Ethernet MAC is random each power cycle, this may
cause your DHCP server to issue a different IP address each time. I may
have a fix for that and try it out someday, basically it needs a bsp
change
in uboot to have the MAC address read from the eeprom.
Kind regards,
-Fred
On Fri, Apr 21, 2023 at 1:03 PM GuillaumeLamottedIncamps <
@.***> wrote:

Hi Fred,
Somehow the building work 2h after my mail !
I think that my issue was in part due to my firewall who didn't like
downloading files from xilinx without analysing them. I retried to do
the
building at 17:20 and it worked without the error that I have
mentionned, I
guess that the firewall whitelisted xilinx after a few analysis, and
without this control, the building was free to complete.
However in order to understand what's going on during the building, I
will
try your advices next monday.
Thanks for your reactivity,
Have a great week-end.
Guillaume
Le ven. 21 avr. 2023 à 17:27, Fred Kellerman @.***> a
écrit :

Hi Guillaume, I have build these myself more than a few times and no
issues for me but let's dig a little deeper.
First, can you try the buildfast.sh I've attached here? I've modified
it
to make sure wget validates the files that are downloaded.
If the issue still exists after ensuring the integrity of the
downloaded
files. Can you try to build the bsp by itself? The bsp can be found
from
where buildfast.sh puts it, you can also find the bsp in the Release
section of this github:

https://github.com/FredKellerman/Microzed-PYNQ/releases/download/v2.6.0/microzed.bsp

Once you have the bsp file you can extract it's contents using tar
-xvf
./microzed.bsp
dd into the new dir, make sure you source settings.sh for PetaLinux
2020.1
and then you should be able to just enter and execute
petalinux-build.
Let
me know if that has the same issue.
Kind regards,
-Fred
buildfast.zip
<

https://github.com/FredKellerman/Microzed-PYNQ/files/11297155/buildfast.zip

—
Reply to this email directly, view it on GitHub
<

https://github.com/FredKellerman/Microzed-PYNQ/issues/7#issuecomment-1517999806

,
or unsubscribe
<

https://github.com/notifications/unsubscribe-auth/A4WUSUCG22BB6M45NQPXCYLXCKRNZANCNFSM6AAAAAAXG4MANM

.
You are receiving this because you are subscribed to this
thread.Message
ID: @.***>

—
Reply to this email directly, view it on GitHub
<

https://github.com/FredKellerman/Microzed-PYNQ/issues/7#issuecomment-1518107040

,
or unsubscribe
<

https://github.com/notifications/unsubscribe-auth/ALQ2MXTKUTJXUVQWIZKQAHTXCK4VHANCNFSM6AAAAAAXG4MANM

.
You are receiving this because you commented.Message ID:
@.***>

—
Reply to this email directly, view it on GitHub
<
https://github.com/FredKellerman/Microzed-PYNQ/issues/7#issuecomment-1518201211
,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/A4WUSUCKERUOVKXFYZW6Z7TXCLHKFANCNFSM6AAAAAAXG4MANM
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

—
Reply to this email directly, view it on GitHub
https://github.com/FredKellerman/Microzed-PYNQ/issues/7#issuecomment-1578754108,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALQ2MXTSXAGJR4WYEF42PMDXJ4U2TANCNFSM6AAAAAAXG4MANM
.
You are receiving this because you modified the open/close state.Message
ID: @.***>

Hi Fred,
Thanks for you answer, it opened my eyes on the subject (I'm discovering
customed Linux while working on them).
I have understood that if I want to boot PYNQ without the micro SD card, I
will need to add some eMMC to my system in order to host the /dev/root
which weights 6.2GB (which indeed won't fit in the QSPI memory).
It's quite a challenge for me as I am still a student, but I will try my
best.
I will let you know if it works out.
Have a good day,
Guillaume
Le mar. 6 juin 2023 à 20:08, Fred Kellerman @.***> a
écrit :

Hi Guillaume,
I have never attempted this as many, perhaps most ZYNQ boards do not have
enough QSPI or flash memory to accommodate PYNQ with the Ubuntu rootfs.
The older images were about 7GB and the latest 3.0.1 is around 9GB now. Do
keep in mind that 16GB minimum is recommended for PYNQ. The QSPI on the
Microzed is not that large.
In theory you could host fsbl, u-boot and maybe the kernel on the QSPI and
use the SD card for the rootfs. Basically you would move what is on the
fat32 partition of the PYNQ SD card to QSPI. But this is not
straightforward, you also need to change the linker map settings and boot
code to be correct for starting up on the QSPI as well. To do the latter
you could study the AMD pynq makefile that builds it all and either
override that or manually do it post build.
Kind regards,
-Fred
On Tue, Jun 6, 2023 at 9:18 AM GuillaumeLamottedIncamps <
@.***> wrote:

Hi Fred,
Since my last email I succeeded to build the image for an SD card, and I
have been exploring the capacities of PYNQ with the microzed.
Now I'm trying to boot PYNQ from the QSPI Flash memory (booting from the
SD
Card is fine for testing but not for the expected utilisation), but I
can't
find any solution that is working. Indeed I have seen that Avnet has
published a document explaining how to boot a new image of a linux kernel
(that you will find in the attachments), however I fail to generate the
.mcs file.
I have understood that the image of the linux kernel is in the "image.ub"
file generated by your script, and that it is not the only component of
this file (there is also the Flattened Device Tree Blob and the
configuration). I have try to extract those components with mkimage or dd
(OS : Ubuntu 18.0, the one that generated the PYNQ build) but I get the
feeling that it is not working.
Have you ever tried to boot PYNQ without the SD card ? Do you already
know
the solution to my problem ?
Have a great day,
Guillaume
Le ven. 21 avr. 2023 à 20:34, Fred Kellerman @.***> a
écrit :

Hi Guillaume,
I replied and closed the github issue.
Do let me know if you cannot get it to build. I can probably upload an
SD
image to the releases tab just for you and then take it down. I don't
have
a lot of extra time and I'm not able to support a pre-built SD image
for
the world.
Also keep in mind the Ethernet MAC is random each power cycle, this may
cause your DHCP server to issue a different IP address each time. I may
have a fix for that and try it out someday, basically it needs a bsp
change
in uboot to have the MAC address read from the eeprom.
Kind regards,
-Fred
On Fri, Apr 21, 2023 at 1:03 PM GuillaumeLamottedIncamps <
@.***> wrote:

Hi Fred,
Somehow the building work 2h after my mail !
I think that my issue was in part due to my firewall who didn't like
downloading files from xilinx without analysing them. I retried to do
the
building at 17:20 and it worked without the error that I have
mentionned, I
guess that the firewall whitelisted xilinx after a few analysis, and
without this control, the building was free to complete.
However in order to understand what's going on during the building, I
will
try your advices next monday.
Thanks for your reactivity,
Have a great week-end.
Guillaume
Le ven. 21 avr. 2023 à 17:27, Fred Kellerman @.***> a
écrit :

Hi Guillaume, I have build these myself more than a few times and
no
issues for me but let's dig a little deeper.
First, can you try the buildfast.sh I've attached here? I've
modified
it
to make sure wget validates the files that are downloaded.
If the issue still exists after ensuring the integrity of the
downloaded
files. Can you try to build the bsp by itself? The bsp can be found
from
where buildfast.sh puts it, you can also find the bsp in the
Release
section of this github:

https://github.com/FredKellerman/Microzed-PYNQ/releases/download/v2.6.0/microzed.bsp

Once you have the bsp file you can extract it's contents using tar
-xvf
./microzed.bsp
dd into the new dir, make sure you source settings.sh for PetaLinux
2020.1
and then you should be able to just enter and execute
petalinux-build.
Let
me know if that has the same issue.
Kind regards,
-Fred
buildfast.zip
<

https://github.com/FredKellerman/Microzed-PYNQ/files/11297155/buildfast.zip

—
Reply to this email directly, view it on GitHub
<

https://github.com/FredKellerman/Microzed-PYNQ/issues/7#issuecomment-1517999806

,
or unsubscribe
<

https://github.com/notifications/unsubscribe-auth/A4WUSUCG22BB6M45NQPXCYLXCKRNZANCNFSM6AAAAAAXG4MANM

.
You are receiving this because you are subscribed to this
thread.Message
ID: @.***>

—
Reply to this email directly, view it on GitHub
<

https://github.com/FredKellerman/Microzed-PYNQ/issues/7#issuecomment-1518107040

,
or unsubscribe
<

https://github.com/notifications/unsubscribe-auth/ALQ2MXTKUTJXUVQWIZKQAHTXCK4VHANCNFSM6AAAAAAXG4MANM

.
You are receiving this because you commented.Message ID:
@.***>

—
Reply to this email directly, view it on GitHub
<

https://github.com/FredKellerman/Microzed-PYNQ/issues/7#issuecomment-1518201211

,
or unsubscribe
<

https://github.com/notifications/unsubscribe-auth/A4WUSUCKERUOVKXFYZW6Z7TXCLHKFANCNFSM6AAAAAAXG4MANM

.
You are receiving this because you are subscribed to this
thread.Message
ID: @.***>

—
Reply to this email directly, view it on GitHub
<
https://github.com/FredKellerman/Microzed-PYNQ/issues/7#issuecomment-1578754108
,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/ALQ2MXTSXAGJR4WYEF42PMDXJ4U2TANCNFSM6AAAAAAXG4MANM
.
You are receiving this because you modified the open/close state.Message
ID: @.***>

—
Reply to this email directly, view it on GitHub
https://github.com/FredKellerman/Microzed-PYNQ/issues/7#issuecomment-1579233599,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A4WUSUGC7PEOIAVVE5Y6RLDXJ5W25ANCNFSM6AAAAAAXG4MANM
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Hey Cadia. What are the results?

I was wondering if you have the data over which network was the best at punctuating text. The bidirectional RNN or BERT based one?
I am interested in starting a project of my own and I would like to know which direction is the right one to look in.
Best regards Johan

Hi Johan
I see that we need to add a results file. The BERT model was better. But we
also tested simulating ASR errors and saw that Punctuator2 was more robust
against distorted sentence structures, so that is something to consider if
you are going to use this with ASR results.
Best, Inga
On Tue, Jan 19, 2021 at 11:16 PM johanub<EMAIL_ADDRESS>wrote:

I was wondering if you have the data over which network was the best at
punctuating text. The bidirectional RNN or BERT based one?
I am interested in starting a project of my own and I would like to know
which direction is the right one to look in.
Best regards Johan
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/cadia-lvl/punctuation-prediction/issues/8, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AHHJ6GC4U3HVEAODFUI5OALS2YHFRANCNFSM4WJWEYJQ
.

Hi Johan
I see that we need to add a results file. The BERT model was better. But we
also tested simulating ASR errors and saw that Punctuator2 was more robust
against distorted sentence structures, so that is something to consider if
you are going to use this with ASR results.
Best, Inga
On Tue, Jan 19, 2021 at 11:16 PM johanub<EMAIL_ADDRESS>wrote:

I was wondering if you have the data over which network was the best at
punctuating text. The bidirectional RNN or BERT based one?
I am interested in starting a project of my own and I would like to know
which direction is the right one to look in.
Best regards Johan
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/cadia-lvl/punctuation-prediction/issues/8, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AHHJ6GC4U3HVEAODFUI5OALS2YHFRANCNFSM4WJWEYJQ
.

Thanks for the answer. Looking forward to the results file!

Thanks for the answer. Looking forward to the results file!


python312Packages.scikit-build-core: 0.9.6 -> 0.10.5; python312Packages.nanobind: use tensorflow-bin

https://github.com/scikit-build/scikit-build-core/releases/tag/v0.9.7
https://github.com/scikit-build/scikit-build-core/releases/tag/v0.9.8
https://github.com/scikit-build/scikit-build-core/releases/tag/v0.9.9
https://github.com/scikit-build/scikit-build-core/releases/tag/v0.9.10
https://github.com/scikit-build/scikit-build-core/releases/tag/v0.10.0
https://github.com/scikit-build/scikit-build-core/releases/tag/v0.10.1
https://github.com/scikit-build/scikit-build-core/releases/tag/v0.10.2
https://github.com/scikit-build/scikit-build-core/releases/tag/v0.10.3
https://github.com/scikit-build/scikit-build-core/releases/tag/v0.10.4
https://github.com/scikit-build/scikit-build-core/releases/tag/v0.10.5
Description of changes

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

[ ] Fits CONTRIBUTING.md.

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


⭐ Add an option to not use avatar or to use title

Is your feature request related to a problem? Please describe.
All videos have avatars even when you don't want, same for title, there is never a title, add an option to choose
Describe the solution you'd like
Add options in the UI

Wrong project, closing