Bump plutus

@luigy i think we should start marrying the version of plutus to the particular tag on the plutus repo; such as plutus-starter-devcontainer/v1.0.5.
this will help because:

we'll be forced to make such a tag! this is great, because doing so pushes up a new devcontainer image ( https://github.com/input-output-hk/plutus/blob/master/.buildkite/pipeline.yml#L29 )
it'll make it so we can't be out of sync here

i'll give this a try for these changes once this pr is merged.
@michaelpj does this seem like a good idea to you?

I've pushed a new tag so that this will build properly against that tag instead of the commit
There's one more thing to change, for good measure: in ./devcontainer/devcontainer.json, we should always bump and pin the tagged version (so here, the diff is:)
-    "image": "docker.io/inputoutput/plutus-starter-devcontainer:latest",
+    "image": "docker.io/inputoutput/plutus-starter-devcontainer:v1.0.6",

this is because vscode, in it's infinite wisdom, doesn't seem to check that it's version matches 'latest', and it doesn't even seem to me to have an easy option to force pulling it!

Sounds fine to me. At some point we'll need to start doing tagged releases of the Plutus Applications libraries: then we can switch to using those tags.

@luigy sorry for the nit-pick; but this is good to go with the addition of the change to the ./devcontainer/devcontainer.json file in my above comment 😀  ( i didn't know how to make it a suggested change because it wasn't in a file in the diff! )

@silky thanks for reminding me. I was actually testing that change earlier and forgot to push :)

though  vscode devcontainer doesn't seem to use that tag and based on docker ps output it insists on using latest even after wiping ~/.vscode and docker system prune -a though I'm not familiar with docker at all so I may me missing something obvious here

@luigy that's very strange indeed ...
also, i can't see why the hyrda-eval has failed? it seems like it worked??

@luigy @silky Yeah, this also happens to me (I think it also happens in the plutus repo). The problem is that when you push a commit which doesn't change anything in the code, the hydra server doesn't rerun the CI, and returns a failed state.
Try to commit something which modifies the code in Game.hs for example.


Add the dayKey key to the DayInWeek class to make it easier to use th…

Add a field in the class DayInWeek
To make it easier to handle days in the _getSelectedWeekDays function, I added the dayKey field to the DayInWeek class.
This should facilitate the manipulation of days, especially in French for my part.
A good practice would then be to use English for the dayKey fields indicating "monday", "tuesday"… And the user remains free to use any terms he wants for the dayName field (M, Mon, Monday, Mo...).

Hey @Ben8557 , Thanks for opening a PR. Really liked your idea, going to merge this. I will ship a new version as soon as possible.


Smashing p makes the game run faster

Press p many times quickly so that the game does not end up paused. Blocks move fast!

Was fixed on main in ee0da88


Cleanup transpose, tile, take, repeat, and pad shape metafunctions

 cleanup transpose shape metafunction

 cleanup tile shape metafunction

 cleanup repeat shape metafunction

 cleanup take shape metafunction

 cleanup pad shape metafunction


grammar modifications

(sorry it's on the same branch...)

Are these intended for this impending "release"?

sure :)


add compatibility with last version of deps

fix compatibility with the last version of django-filter, django-extra-views and django-rest-framework.

/cc @auvipy and @galuszkak


command not supported for set immediate value

Hi
I upgraded to the latest version for appium 4.1.2 and I am trying to run
driver.FindElementByAccessibilityId("textBoxName").SetImmediateValue("sdfdsf");
but I get the below exception
==========================================
POST /session/CBCF9BF3-0C62-47F7-80DE-0A95C9C31566/appium/element/42.1838614/value HTTP/1.1
Accept: application/json, image/png
Content-Length: 42
Content-Type: application/json;charset=utf-8
Host: <IP_ADDRESS>:4723
User-Agent: selenium/3.141.0 (.net windows)
{"value":"AutomationBackup12495721492020"}
WinAppDriver::CommandHandler::Appium::HandleCommandAsMidPoint - Command  is not recognized
HTTP/1.1 404 Not Found
Content-Length: 168
Content-Type: application/json
{"status":9,"value":{"error":"unknown command","message":"Command not recognized: POST: /session/CBCF9BF3-0C62-47F7-80DE-0A95C9C31566/appium/element/42.1838614/value"}}
WinAppdriver needs to adapt to the latest version of appium.

@kat-y Can this be taken as an enhancement?


Existing users suddenly have no role - even though they do

Hi,
We've been successfully using AuthLDAP for a number of years, and this week an odd issue has appeared. Some users seem to be able to log in okay, but others can't log in and this is the error we see in the Apache error log (it's anonymised, but otherwise as it is in the log).
[AuthLDAP] User<EMAIL_ADDRESS>logging in, referer: https://example.com
[AuthLDAP] about to do LDAP authentication, referer: https://example.com
[AuthLDAP] connect to LDAP server, referer: https://example.com
[AuthLDAP] LDAP authentication successfull, referer: https://example.com
[AuthLDAP] no role yet, set default role, referer: https://example.com
[AuthLDAP] The LDAP user does not have an entry in the WP-Database, a new WP account will be created, referer: https://example.com
[AuthLDAP] Error creating user : Sorry, that email address is already used!, referer: https://example.com
I've checked the users who are being rejected and they do have an existing WordPress account and they do have a role. These are all established users who have been in the system for some time. There is no consistency between the roles these users have.
Other users with the same roles are being authenticated without issue.
New users are being created without issue.
I'd be grateful for any suggestions in resolving or debugging this.
We're currently on WordPress 5.9.1, plugin version 2.4.10, PHP 7.4.13.
Thanks

Ultimately we resolved this by deleting and recreating the users.


LD fails after upgrading v0.18 to v0.19

Bug Description
Hi,
I have a repository which builds perfectly on pyo3 v0.18. When upgrading to v0.19. Build failds on the container with LD problems.
The command that drives to fail is:
docker run --rm -t -e CARGO_HOME=.project_cargo \
    -v $(pwd)/:/io ghcr.io/pyo3/maturin:latest \
    build --release -i python3.9 --manylinux 2014

with fail
error: linking with `cc` failed: exit status: 1
= note: /opt/rh/devtoolset-10/root/usr/libexec/gcc/x86_64-redhat-linux/10/ld: cannot find -lpython3.9
         collect2: error: ld returned 1 exit status

it does not find libpython when using the container invocation on pyo3 v0.19 (and it does find it when using v0.18 inside the container).
I solved local execution for tests by specifying export LD_LIBRARY_PATH=#libpython directory#, but it keeps failing on CICD pipelines at the container., where I did not manage to find libpython3.9.so.1.0  to provided explicitly as LD_LIBRARY_PATH.  Something looks broken on ld definitions on v0.19.
The fail raises when upgrading in the Cargo.toml to:
[dependencies]
pyo3-ffi = "0.19"
[dependencies.pyo3]
version = "0.19"

This is the cargo toml:
[package]
...
edition = "2021"
...

[dependencies]
ahash =  { version = "0.8", features = ["serde"] }
regex = "1.8"
regex-syntax = "0.7"
unicode-segmentation = "1.10"
aho-corasick = "1.0"
fancy-regex = "0.11"
rayon = "1.7"
lazy_static = "1.4"
# indicatif = "0.16"
log = "0.4"
serde = { version = "1", features = ["derive"] }
serde_json = "1.0"
pyo3-log = "0.8"
pyo3-ffi = "0.19"
bencher = "0.1"
env_logger = "0.10"
chrono = "0.4"
bincode = "1.3"
# fst = "0.4"
# memmap = "0.7"
# abomonation = "0.7"

[lib]
name = ...
crate-type = ["cdylib", "rlib"]

[dependencies.pyo3]
version = "0.19"
features = ["extension-module", "multiple-pymethods"]

Steps to Reproduce

Backtrace
error: linking with `cc` failed: exit status: 1
  |
  = note: LC_ALL="C" PATH="/root/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/bin:/io/.project_cargo/bin:/opt/python/cp37-cp37m/bin:/opt/python/cp38-cp38/bin:/opt/python/cp39-cp39/bin:/opt/python/cp310-cp310/bin:/opt/python/cp311-cp311/bin:/root/.cargo/bin:/opt/rh/devtoolset-10/root/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin" VSLANG="1033" "cc" "-Wl,--version-script=/tmp/rustc8goOWk/list" "-Wl,--no-undefined-version" "-m64" "/tmp/rustc8goOWk/symbols.o" "/io/target/release/deps/pytextrust.pytextrust.223a05e0-cgu.0.rcgu.o" "/io/target/release/deps/pytextrust.pytextrust.223a05e0-cgu.1.rcgu.o" "/io/target/release/deps/pytextrust.pytextrust.223a05e0-cgu.10.rcgu.o" "/io/target/release/deps/pytextrust.pytextrust.223a05e0-cgu.11.rcgu.o" "/io/target/release/deps/pytextrust.pytextrust.223a05e0-cgu.12.rcgu.o" "/io/target/release/deps/pytextrust.pytextrust.223a05e0-cgu.13.rcgu.o" "/io/target/release/deps/pytextrust.pytextrust.223a05e0-cgu.14.rcgu.o" "/io/target/release/deps/pytextrust.pytextrust.223a05e0-cgu.15.rcgu.o" "/io/target/release/deps/pytextrust.pytextrust.223a05e0-cgu.2.rcgu.o" "/io/target/release/deps/pytextrust.pytextrust.223a05e0-cgu.3.rcgu.o" "/io/target/release/deps/pytextrust.pytextrust.223a05e0-cgu.4.rcgu.o" "/io/target/release/deps/pytextrust.pytextrust.223a05e0-cgu.5.rcgu.o" "/io/target/release/deps/pytextrust.pytextrust.223a05e0-cgu.6.rcgu.o" "/io/target/release/deps/pytextrust.pytextrust.223a05e0-cgu.7.rcgu.o" "/io/target/release/deps/pytextrust.pytextrust.223a05e0-cgu.8.rcgu.o" "/io/target/release/deps/pytextrust.pytextrust.223a05e0-cgu.9.rcgu.o" "/io/target/release/deps/pytextrust.3pw609witrtkasvv.rcgu.o" "-Wl,--as-needed" "-L" "/io/target/release/deps" "-L" "/opt/_internal/cpython-3.9.17/lib" "-L" "/root/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib" "-Wl,-Bstatic" "/io/target/release/deps/libpyo3_log-18d989d0df156d94.rlib" "/io/target/release/deps/libpyo3-fbf68dd1b0cad6bd.rlib" "/io/target/release/deps/libparking_lot-ec8904799a30e388.rlib" "/io/target/release/deps/libparking_lot_core-7fade888247caa8a.rlib" "/io/target/release/deps/libinstant-f65a3617ad2916e7.rlib" "/io/target/release/deps/libarc_swap-3316aaccbed8c5b5.rlib" "/io/target/release/deps/libserde_json-cacb006ec5172c6c.rlib" "/io/target/release/deps/libryu-8f18defb0e80acf6.rlib" "/io/target/release/deps/libitoa-f1ad732e3dc54287.rlib" "/io/target/release/deps/libpyo3-14047d380107d6e7.rlib" "/io/target/release/deps/libmemoffset-901034f0d6bf20f9.rlib" "/io/target/release/deps/libparking_lot-25415cb428a6aa3e.rlib" "/io/target/release/deps/libparking_lot_core-b514dd1f7a299942.rlib" "/io/target/release/deps/libsmallvec-ca8366caef5e3934.rlib" "/io/target/release/deps/liblock_api-8e589d8598aee77d.rlib" "/io/target/release/deps/libpyo3_ffi-43b2ba77d5307eca.rlib" "/io/target/release/deps/libinventory-656eb4b050048770.rlib" "/io/target/release/deps/libunindent-a99f53b699b9b49d.rlib" "/io/target/release/deps/libunicode_segmentation-8c3090c5b171538a.rlib" "/io/target/release/deps/libbincode-4e55497fa9f6b7d3.rlib" "/io/target/release/deps/libenv_logger-753e83d45d7bd8aa.rlib" "/io/target/release/deps/libtermcolor-517f0b96abd75861.rlib" "/io/target/release/deps/libis_terminal-fd262b2932fb5e80.rlib" "/io/target/release/deps/librustix-857b1a202a14482e.rlib" "/io/target/release/deps/libbitflags-ed1146e934fe3b36.rlib" "/io/target/release/deps/liblinux_raw_sys-494fdeba104f7e43.rlib" "/io/target/release/deps/libio_lifetimes-413ec2f95b7eaaf7.rlib" "/io/target/release/deps/libhumantime-7de5d1150ec811ea.rlib" "/io/target/release/deps/libchrono-0e545c058a1efc1e.rlib" "/io/target/release/deps/libiana_time_zone-083708a588390bd6.rlib" "/io/target/release/deps/libnum_integer-2df3e5097ac7e8de.rlib" "/io/target/release/deps/libnum_traits-12fbfdaf95dcb5c8.rlib" "/io/target/release/deps/libtime-5f07f77aa5005f0f.rlib" "/io/target/release/deps/liblazy_static-340011eba8b2d628.rlib" "/io/target/release/deps/librayon-ce3021b7a3016ac1.rlib" "/io/target/release/deps/librayon_core-42ffd8fa2050eae7.rlib" "/io/target/release/deps/libnum_cpus-3d9eddf9cac55fac.rlib" "/io/target/release/deps/libcrossbeam_deque-7c52b9857af0d630.rlib" "/io/target/release/deps/libcrossbeam_epoch-2b83bf3a2954de64.rlib" "/io/target/release/deps/libmemoffset-97e87728d02156f7.rlib" "/io/target/release/deps/libscopeguard-831ea9d9cd38b868.rlib" "/io/target/release/deps/libcrossbeam_channel-f587f7e7bd1948b8.rlib" "/io/target/release/deps/libcrossbeam_utils-ace150b50c657604.rlib" "/io/target/release/deps/libeither-bded5cc6bed1e2d9.rlib" "/io/target/release/deps/liblog-517d9c8159ecbe27.rlib" "/io/target/release/deps/libfancy_regex-f71efc9b18ab5fb1.rlib" "/io/target/release/deps/libregex-134bc75dbeda3746.rlib" "/io/target/release/deps/libaho_corasick-1bcd749c3be1081e.rlib" "/io/target/release/deps/libmemchr-6178b05fdcb6c618.rlib" "/io/target/release/deps/libregex_syntax-5a3db13ff19465bc.rlib" "/io/target/release/deps/libbit_set-18c8de7bf2a0b923.rlib" "/io/target/release/deps/libbit_vec-9f2b9822f39382d1.rlib" "/io/target/release/deps/libahash-421c9f5dd88e8cfc.rlib" "/io/target/release/deps/libgetrandom-51d75a94b7ea549f.rlib" "/io/target/release/deps/liblibc-1bcb2da32dbdd6bc.rlib" "/io/target/release/deps/libonce_cell-f4fc1a6098aad5e2.rlib" "/io/target/release/deps/libserde-3d6c4fad709433e7.rlib" "/io/target/release/deps/libcfg_if-a7d3f62713af2583.rlib" "/root/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib/libstd-8389830094602f5a.rlib" "/root/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib/libpanic_unwind-41c1085b8c701d6f.rlib" "/root/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib/libobject-f733fcc57ce38b99.rlib" "/root/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib/libmemchr-6495ec9d4ce4f37d.rlib" "/root/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib/libaddr2line-1e3796360cca5b49.rlib" "/root/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib/libgimli-2e7f329b154436e1.rlib" "/root/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib/librustc_demangle-1e1f5b8a84008aa8.rlib" "/root/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib/libstd_detect-cbcb223c64b13cf3.rlib" "/root/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib/libhashbrown-b40bc72e060a8196.rlib" "/root/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib/libminiz_oxide-1eb33ae9877d3c0f.rlib" "/root/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib/libadler-0335d894dd05bed7.rlib" "/root/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib/librustc_std_workspace_alloc-076a893ead7e7ab5.rlib" "/root/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib/libunwind-2e924dd85b2e9d95.rlib" "/root/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib/libcfg_if-7975ffb5e62386c4.rlib" "/root/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib/liblibc-285425b7cea12024.rlib" "/root/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib/liballoc-38694d775e998991.rlib" "/root/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib/librustc_std_workspace_core-914eb40be05d8663.rlib" "/root/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib/libcore-27094fcca7e14863.rlib" "/root/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib/libcompiler_builtins-919e055b306699ae.rlib" "-Wl,-Bdynamic" "-lpython3.9" "-lgcc_s" "-lutil" "-lrt" "-lpthread" "-lm" "-ldl" "-lc" "-Wl,--eh-frame-hdr" "-Wl,-z,noexecstack" "-L" "/root/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib" "-o" "/io/target/release/deps/libpytextrust.so" "-Wl,--gc-sections" "-shared" "-Wl,-z,relro,-z,now" "-Wl,-O1" "-nodefaultlibs"
  = note: /opt/rh/devtoolset-10/root/usr/libexec/gcc/x86_64-redhat-linux/10/ld: cannot find -lpython3.9
          collect2: error: ld returned 1 exit status

error: could not compile `pytextrust` (lib) due to previous error
💥 maturin failed
  Caused by: Failed to build a native library through cargo
  Caused by: Cargo build finished with "exit status: 101": `PYO3_ENVIRONMENT_SIGNATURE="cpython-3.9-64bit" PYO3_PYTHON="/opt/python/cp39-cp39/bin/python3.9" PYTHON_SYS_EXECUTABLE="/opt/python/cp39-cp39/bin/python3.9" "cargo" "rustc" "--message-format" "json-render-diagnostics" "--manifest-path" "/io/Cargo.toml" "--release" "--lib" "--crate-type" "cdylib"`

Your operating system and version
irrelevant
Your Python version (python --version)
python3.9
Your Rust version (rustc --version)
1.70 (maturin container latest)
Your PyO3 version
0.19
How did you install python? Did you use a virtualenv?
container...
Additional Info

I can only reproduce this error if I remove the use of extension-module feature from the Cargo.toml you provided. Without that flag it's expected that PyO3 will attempt to link.
Usually these days I recommend to insert the extension-module feature via maturin configuration. This ensures that running cargo test will link libpython and so be able to run tests, but building the Python module will not link.
Try adding this section to your pyproject.toml:
[tool.maturin]
features = ["pyo3/extension-module"]

and remove all mention of extension-module feature from your Cargo.toml.

hi @davidhewitt , thanks for the tip.
Changed on pyproject.toml adding this feature "pyo3/extension-module"  to tool.maturin section, but stills fails to LD both locally in my machine, and in the container build.
Just putting on the cargo toml back to v0.18 on pyo3, gives successfull builds both locally and on the container (ld works fine in this  case)
I am afraid if there is some migration step missed here? https://pyo3.rs/main/migration.html#from-018-to-019

There are not expected to be any changes between 0.18 and 0.19 that would cause this.
Would you please provide a complete minimally reproducing example which demonstrates the failure in the container build when compiled? (e.g. Cargo.toml, pyproject.toml, lib.rs)? Ideally as a separate Github repo so I can clone it and observe the same failure.

mmm, picking a subset of the repo and changing to v0.19 does not break ld on a mock that i just created:
https://gitlab.com/g6313/pyo3-ld-mock
It needs to be something in other .rs or .py files that I have that is trying to link to python lib desesperately and breaks on build.
The weird thing is that it does not break for v0.18 and it does for v0.19, this drives me mad.

hi  @davidhewitt , found the issue that was kicking me out.
To allow a clean migration of  older pyo3 versions to new ones, deleting Cargo.lock first is recommended, otherwise it can have problems with LD both on test and build.
It would be great to have this previous tip on https://pyo3.rs/main/migration.html#migrating-from-older-pyo3-versions.
I guess you could reproduce this issue with a proper repository where you first build using v0.18 then you change in Cargo.toml to v0.19 , without deleting Cargo.lock.
Kind regards.

Ah great! Potentially the pyo3-log transitive dependency on PyO3 had not updated to a newer version or some other similar issue. A bit surprising but altogether not a difficult solution.
Thanks for sharing!


How to enable-migrations for Microsoft.Bot.Builder.Azure SqlBotContext

We installed the Microsoft.Bot.Builder.Azure package and i knew inside the package have a SqlBotDataStore , a sql version of IBotDataStore.
However i tried to enable-migrations in my web api project but it shows "No context type was found in the assembly xxxx"
Do someone know how to do it properly? Or I need to make my own implementation just copy and paste Microsoft one?

There's a script here you can run to create the table: https://github.com/Microsoft/BotBuilder-Azure/blob/master/CSharp/AzureSql-CreateTable.sql

Also, the entity framework nuget package contains a file named "migrate.exe" that can be used from the command line. https://msdn.microsoft.com/en-us/library/jj618307(v=vs.113).aspx

Thanks, it's very helpful, I solved the problem.

You can put this script into a empty migration which will not break your current project design (all tables are created by migration which might ease the devops progress)
https://stackoverflow.com/questions/32125937/can-we-run-sql-script-using-code-first-migrations/32125959


Add loading screen in network bound view

When there is a connection issue (long latency or whatever), it should display a loading screen:

when displaying matrix data (in detailed view), also if possible, loading should wait for complete table render
when fetching the study information (in SingleStudy.tsx), display placeholder loader (see https://github.com/zalog/placeholder-loading or other similar lib)

Also add a default view (large icon) when the matrix has no data

And in the variant edition view


Add types for useState, useCallback, useMemo functions

Solves https://github.com/shelegdmitriy/near-social-vm-types/issues/2

@shelegdmitriy please merge it and publish the new version of the package to NPM if the change looks good to you


misleading error message in safe_open

System Info
safetensors 0.4.3

transformers version: 4.39.3
Platform: Linux-5.15.0-1048-aws-x86_64-with-glibc2.31
Python version: 3.10.13
Huggingface_hub version: 0.23.1
Safetensors version: 0.4.3
Accelerate version: 0.25.0
Accelerate config:    not found
PyTorch version (GPU?): 2.1.0 (True)
Tensorflow version (GPU?): not installed (NA)
Flax version (CPU?/GPU?/TPU?): not installed (NA)
Jax version: not installed
JaxLib version: not installed
Using GPU in script?:
Using distributed or parallel set-up in script?:

Information

[ ] The official example scripts
[X] My own modified scripts

Reproduction

mkdir some_folder/
safe_open("some_folder", "pt")

this produces the error OSError: No such device (os error 19)
Expected behavior
instead of an error mentioning a missing device, it should say that the path passed does not point to a safetensors file, or am I missing something?

thanks for reporting @Clement-Lelievre

same error

It appears that safetensors model files stored in certain mounted directories, such as Ceph, may encounter this issue. Copying the model to the local hard drive (" ~/ ") allows it to load correctly. Additionally, saving it as a .bin model file does not encounter this issue.
Maybe the same problem here

same here. change ckpt_path to .safetensors file path not folder path is all right.


[SPARK-25299] ShuffleLocation/FetchFailed integrations with scheduler

I followed the SPIP reader specs for the implementation:

If FetchFailed's shuffleLocations is not defined, then only that mapId's status gets removed, so only that mapper is recomputed (used in the async case, where you might only want one mapper recomputed because it didn't upload in time)
If FetchFailed's ShuffleLocations is defined, then it's removed everywhere from the MapOutputTracker (used in the individual file server case)
To prevent removal of a location, don't set a FetchFailed exception (used in the DFS case)

The main differences between this and the previous implementation is that it's opinionated about the shuffle location being a host/port combo and that a particular partition may have multiple locations. This makes it a lot easier to integrate with the scheduler.
There's a bit of convoluted logic in the DAGScheduler code when processing the shuffleLocation for what to remove from the MapOutputTracker because I needed to check the epoch failure before removing any location. I didn't special case the execId logic for only default implementation because 1) there could be other implementations that check for FetchFailed from a particular execId, like in the async case, so you'd want to be able to remove all blocks that have been written to that execId, and 2) I don't completely understand the implications of removing the failedEpoch check for a fetch failure that happened on a particular executor. For remote locations, I figured the epoch matters less since individual remote servers can't really be re-added as readily as executors?
I also wasn't sure exactly when to use Arrays and when to use Seqs. I figured when returning them from MapOutputTracker, we'd want to use Seq since it's not keyed by the specific object like Arrays are... but maybe it's expensive to have to convert from array to seq for every call?

@mccheah @ifilonenko for initial comments?

Added a few unit tests for the cases of Async and individual file server implementations. Here's a brief explanation of how I expect them to work. Keep in mind that when a FetchFailure returns, it returns with all the locations that it failed to fetch from.
The individual file server situation is pretty straightforward.  Each MapShuffleLocation keeps a list of lists: the outer list is for each partition, and the inner list is the shuffle locations (primary + backup) for each partition block. It lists a MapStatus as missing when there's a missing partition within that MapStatus. The FetchFailed will return the list of hosts to remove from every single MapStatus. The tests demonstrate a case where a FetchFailed for one partition causes other partitions to disappear too, and a case where a FetchFailed removes locations for other partitions, but those partitions have backups so it's ok.
The Async case is more complicated. In the Async case, the location is made up of one Executor location and one remote DFS location. (We need to keep around the DFS location because otherwise, if you want to mark one executor as missing, and we delete it from other MapStatuses that executor could have written, it'll delete the entire MapStutus entry even though it could have a backup in the DFS). When a FetchFailed happens, it returns both the executor and DFS location. It then uses those two locations to remove the two locations from that mapper's mapStatus, thus depleting that MapStatus of all locations, and deleting that entry from the MapOutputTracker. It will then also use the execId information given by the Executor location to delete all local locations written by that executor since that executor is down and it can no longer service its shuffle files. However, it has the setting spark.files.fetchFailure.unRegisterOutputOnHost set to false so it doesn't delete the DFS host from all the entries, meaning that other partitions can still be serviced by the DFS.
The Async case confused me a bit when I was writing this. I think the most confusing part is having to keep track of two different types of locations, and setting spark.files.fetchFailure.unRegisterOutputOnHost to false. It would be ideal if we just removed the failed mapId's MapStatus entry regardless of the ShuffleLocations passed into the FetchFailure (right now, we delete the shuffleLocations one by one and only delete the MapStatus entry if all the locations are gone), but I don't think we should delete without checking the location (in case of speculative execution with the reducers, and if a reducer returns with an obsolete shuffleLocation, we don't want to delete that MapStatus entry). I can think more about how we can simplify the Async case...


SPM support

Consider to add Swift Package Manager support for your cool library.

Thanks, bro. I tried to do that but can't.
I got this error.

I think swift package doesn't support mixing Swift and Objective-c code. Refer to here

Correct me if I am wrong.

Yep, that's right
Seems you need to separate C sources into dependent SPM target

I see. Thanks.
Others also want to use this lib in SPM https://github.com/623637646/SwiftHook/issues/7
I am not familiar with SPM. I would appreciate if you could help to implement it and make a PR.

I have investigated the solution. It's blocked by this issue: https://forums.swift.org/t/custom-build-configuration-names/29167
Will continue this feature since the issue be fixed by Apple.


Integrate with an existing custom error-monitoring tool

Options:

Skylight
New relic
Airbrake
Scoutapp

@saurabhnanda
I found helics for New Relic (https://hackage.haskell.org/package/helics)
Airbrake :: https://hackage.haskell.org/package/airbrake

@sras would you like to take a shot at this while I review the email sprint?


Report Test Results step of Functional Tests workflow should not run on forks

Steps to reproduce
Report Test Results step of Functional Tests workflow is running on forks. I noticed that when I received an email for the failure of that step in my fork repository.
Observed behavior

Desired behavior
This step should not run on forks like the other steps of the same workflow.
Workaround
No response
rad Version
edge
Operating system
No response
Additional context
No response
Would you like to support us?

[ ] Yes, I would like to support you

cc/ @nithyatsu


404 for OSM tile-source list

The tile-source parameter description in README.md links to a list of OSM tile sources. It's link is currently broken.
https://github.com/sharedstreets/sharedstreets-api lists planet-181224 as last available versioned OSM data source. Is there a newer data source available?

An up-to-date list has been on my wishlist for a while now. Flagging as a priority.

We are also wondering about this; we started using SharedStreets for stable reference IDs, etc, but would like to know if there will ever be further updates since 2018.


Add start functional test

I am not satisfied with starting Shower on load event: it will be excessively delayed in the wild.
MS Edge does not support navigating to Data URIs.
shower.js should be hosted separately: passing it in Data URI is inefficient and crashes sauce-connect.

The most straightforward solution is to setup simple Node.js echo HTTP server and pass search params. Luckily, lengthy URLs is not an issue nowadays.

@shvaikalesh what’s the status of this one? I was wondering if we should just push 3.0 release as it is and move testing and other possible improvements to 3.0.1.

We check document.currentScript to start right away in async scripts.
Tests use echo query parameter instead of Data URIs.

Failed test (key press emitting issue in Safari, see 95134bc849ff67d9567b2cfaf1df1bc250787c36) is not connected to the changes.


Add support for custom boundary conditions

Now, for a given model, a user can also add custom boundary conditions like so:
Es, xs, vs, t = Plasma.get_vars(plasma; dim=1)
ic = [Es[1](0, xs...) ~ g(xs...)]
bc = [Es[1](t,0.4) ~ f(t)]

sol = Plasma.solve(plasma, dim=1, GPU=false, conditions = [ic;bc])

This gives the interface more flexibility to support different simulations.
Additionally, I also added boundary conditions to E in accordance to this

So now, in addition to the boundary and initial conditions every model has to have:
vlasov_ics = [fs[i](time_lb,xs...,vs...) ~ Ps[i](xs,vs) * geometry(xs) for i in eachindex(fs)]
div_E_ic = div_E0 ~ sum([qs[i] * _I(fs[i](time_lb,xs...,vs...)) for i in eachindex(qs)])/ϵ_0 * geometry(xs)
E_bcs = [get_boundaries(t, xs, Es, lb);get_boundaries(t, xs, Es, ub)]

one can also add custom ones.

cc @SebastianM-C
I think this starts to address what we talked about.

Refactored a bit. Now we have the ability to add custom boundaries to E, B, and f, but I didn't add this to the interface, as this is more of an advanced use case.
But one could this like so
"""
Get plasma variables to generate custom boundary and initial conditions.

Use get_vars to get variables to set custom initial and boundary conditions like so:

fs, Es, xs, vs, t = Plasma.get_vars(plasma; dim=1)
ic = [Es[1](0, xs...) ~ cos(xs[1])]
bc = [Es[1](t,0.4) ~ cos(t)]

sol = Plasma.solve(plasma, dim=1, GPU=false, E_bcs = [Dirichlet(t, xs, Es, lb);ic;bc])

This is only advised for more advanced models with custom currents. For simpler models, set a custom boundary for E with E_bcs or initial condition for f.
"""

function get_vars(plasma; dim=3)
    # get E
    Es = Symbolics.variables(:E, 1:dim; T=SymbolicUtils.FnType{Tuple,Real})

    # get fs
    dis = plasma.distributions
    species = [d.species for d in dis]
    fs = Symbolics.variables(:f, eachindex(species); T=SymbolicUtils.FnType{Tuple,Real})

    # get parameters
    @parameters t
    xs,vs = Symbolics.variables(:x, 1:dim), Symbolics.variables(:v, 1:dim)

    # return values
    if plasma isa ElectrostaticPlasma
        return fs, Es, xs, vs, t
    else
        Bs = Symbolics.variables(:B, 1:dim; T=SymbolicUtils.FnType{Tuple,Real})
        return fs, Es, Bs, xs, vs, t
    end
end

Hi, sorry for the delay. I'm looking now over the code and I'm a bit confused by the above E_bcs  = [Dirichlet(t, xs, Es, lb);ic;bc] example. Shouldn't  it be more like E_bcs = Dirichlet or E_bcs = Neumann (which is the default in the code)?
I tried to test this with
TD = 30000
D = species.D
D_D = Distribution(Maxwellian(TD, D.m), D)
G = Geometry()
plasma = ElectrostaticPlasma([D_D], G)

fs, Es, xs, vs, t = get_vars(plasma; dim = 1)
ic = [Es[1](0, xs...) ~ cos(xs[1])]
bc = [Es[1](t, 0.4) ~ cos(t)]

sol = Plasma.solve(plasma, dim = 1, GPU = false, E_bcs = Dirichlet)

but I'm getting some NaNs showing up in the pde_losses and bcs_losses, but I'm not sure to what does it correspond.
Current loss is: NaN
pde_losses: [3.356915290562938e11, NaN]
bcs_losses: [5.334357060395836, NaN, 0.11948624599487331, 0.14394644995372455, 0.0, 0.0]
Current loss is: NaN
pde_losses: [3.356915290562938e11, NaN]
bcs_losses: [5.334357060395836, NaN, 0.11948624599487331, 0.14394644995372455, 0.0, 0.0]
Current loss is: NaN
pde_losses: [NaN, NaN]
bcs_losses: [NaN, NaN, NaN, NaN, NaN, NaN]

I'm not sure if I'm not missing something on my side, I'll let you know if I find anything.
Also, as a diagnostic, I usually just simulate a laser without the plasma before simulating the whole system in order to check for correctness. Do you think that would be possible as an edge case (i.e. no plasma and just EM wave propagation)? I was wondering if this would be useful to debug the above NaNs (by looking just at the external electric field).

@SebastianM-C the NaN is due to an error in NeuralPDE (an upstream package of Plasma.jl). I will fix the problem in NeuralPDE and then merge this branch (this is the only thing holding it up).

Shouldn't it be more like E_bcs = Dirichlet or E_bcs = Neumann

It is like that now. I refactored the code after I left the comment.

Also, as a diagnostic, I usually just simulate a laser without the plasma before simulating the whole system in order to check for correctness. Do you think that would be possible as an edge case (i.e. no plasma and just EM wave propagation)? I was wondering if this would be useful to debug the above NaNs (by looking just at the external electric field).

We can support that in the future (feel free to open an issue), but for now I will try to just get the benchmarks working.

Hi.  I am interested in trying out this package, but I am having trouble understanding the code and examples.  It looks like the naming convention for the equations and variables are lifted out of some physics text or document, from which one excerpt is provided above.  I get E and B, but it is not 100% obvious to me what beta, f, x, and v are, or assumptions about their form or units.  Can you document this information in the readme or other appropriate location?

Hi @fluffynukeit, what particularly are you having trouble understanding? I am happy to answer more specific questions or help you with your code if you share it. Feel free to open an issue. The beta in that case just means a certain species of particle.
And f is the distribution, x is the configuration space coordinates and v is the velocity space coordinates.

I would appreciate having proper definitions for the terms used in the equations, or a link to the reference material you are sourcing from.  For instance, f is the "distribution".  Distribution of what?  I'm guessing here, so maybe something like "f_beta is the probability density function for a particle of species beta at 3D configuration coordinates x and 3D velocity v."  I don't know if that's correct for f_beta or not, but is along the lines of specificity that I think would help in understanding the code.

Take a look at our read me and at this here https://en.m.wikipedia.org/wiki/Vlasov_equation
it will give you some information about Plasma physics. Make sure to also check out PlasmaBenchmarks.jl (that is still a WIP, but there are a few examples there we will use as benchmarks for the package)


Hook to inject render-dependent data for SSR?

Helmetand redux stores are two examples of render-dependent data, in that they require a full render pass through renderToString to populate the store | enable rewind. These are currently being used to that effect in this project, but there aren't any hooks exposed to interact with this step of the render pipeline.
I'm using a css-in-js library which offers the same functionality: a render pass will populate its stylesheets, and you can call getCss to render a string version into the <head> for SSR.
I'm having trouble finding any hooks available that would enable me to do this. My best guess, the html.head() method, is unfortunately called before renderToString.
If there's somewhere I could inject this during SSR, please let me know. Otherwise, could you expose a post-render method to allow this sort of pattern?

I didn't understand what you're trying to say here

I think I get what you mean.
https://github.com/halt-hammerzeit/react-isomorphic-render/blob/122c2e82ef9a41ed971cc4f8edc8e7c7e146bf14/source/page-server/render.js#L68-L77
head is evaluated before the page is rendered:
https://github.com/halt-hammerzeit/react-isomorphic-render/blob/e55b9a29effb956f389f961a8b3080bb83448820/source/redux/server/render.js#L76
I could move head evaluation to render_webpage():
https://github.com/halt-hammerzeit/react-isomorphic-render/blob/122c2e82ef9a41ed971cc4f8edc8e7c7e146bf14/source/page-server/render.js#L132
In this case it will be evaluated after the React page has been rendered.
Would that solve this issue.
Or did you choose a different approach.

Yeah deferring the head evaluation would work great.

Done in https://github.com/halt-hammerzeit/react-isomorphic-render/commit/1c2ad469e03535fcd72232012e218d47a4f94d98

All this rewind machinery is not thread safe by the way.
https://github.com/nfl/react-helmet/issues/240
So if using alternative react renderers (like streaming ones) all those "side effects" won't work.

It seems this still isn't resolved. Looking at the code, it's an easy fix.
https://github.com/halt-hammerzeit/react-isomorphic-render/blob/master/source/page-server/render.js:151
content needs to be resolved at line 125, right before head is executed.
Like this:
render_webpage(content)
		{
				...

				// Render the HTML
				return Html
				({
					...parameters,
					extension_javascript: typeof extension_javascript === 'function' ? extension_javascript() : extension_javascript,
					assets,
					locale,
					locale_messages_json: messagesJSON,
					head,
					body_start,
					body_end,
					authentication_token,
					content
				})
		}

Yeah, that will do.
Released<EMAIL_ADDRESS>

That appears to have done the trick :+1:


Caffeine does not seem to work on Samsung devices

When I press on the Caffeine tile, I receive the following 05_12-23-27-49_560.log and it does not seem to work at all.
Android 12. Samsung Galaxy A31.

hey @Terkyz, this project isn't being maintained in a long time, as you can see from its history. And I don't intend to port it over to newer versions of Android. You're very welcome to fork and work on it yourself :)


Use of both variable and variable_a causes initialized error in pythonizer

Use of both variable and variable_a causes uninitialized error in pythonizer, for example using both %nte and $nte_a causes:
Use of uninitialized value in string eq at ../Perlscan.pm line 6971, <SYSIN> line N

also, bad code may be generated depending on what other variables with the same basename are used.

Fixed in v1.013


Change the DI Microsoft to use 'RemoveOrUpdate` when it becomes available

if list empty remove contract entirely
https://github.com/reactiveui/splat/blob/5c73294dfeaede78353e0694758198f9403298d7/src/Splat.Microsoft.Extensions.DependencyInjection/MicrosoftDependencyResolver.cs#L327-L332

This comment was generated by todo based on a TODO comment in 5c73294dfeaede78353e0694758198f9403298d7 in #370. cc @weitzhandler.
Originally posted by @todo in https://github.com/reactiveui/splat/pull/370#issuecomment-518169994

We are waiting on https://github.com/dotnet/corefx/issues/24246


Warning: Could not access graphql-client.

Environment
Nuxt project info:                                                                                - Operating System: Windows_NT

Node Version:     v18.16.0
Nuxt Version:     3.12.4
CLI Version:      3.12.0
Nitro Version:    2.9.7
Package Manager<EMAIL_ADDRESS>Builder:          -
User Config:      modules, formkit, i18n, sitemap, pinia, runtimeConfig, css, nitro, routeRules, compatibilityDate
Runtime Modules<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Build Modules:    -

Describe the bug
I can't get rid of this warning:

Expected behaviour
Startup without warning
Reproduction
My config is:
export default defineNuxtConfig({
  :
  runtimeConfig: {
    public: {
      'graphql-client': {
        clients: {
          default: {
            :
            # my host settings
          },
        },
        codegen: {
          silent: false,
        },
      },
      :
      # other public configs
    },

  },
  :
  # other server configs
})

Additional context
System is working (as far as I can see); I'm just a little unsettled by this warning.
Logs
No response

I encountered the same issue.

This is the line that causes the warning:
https://github.com/Diizzayy/nuxt-graphql-client/blob/b512fa0670a10a24e658a108379263363892e2ac/src/runtime/plugin.ts#L16
Seems like config?.["graphql-client"] never worked on client side but with Nuxt 3.12 we now get a warning for this.
Simple check for process.server could solve this easily.

I'm having the same issue, any solutions?


Option to set CTA button text and click listener in SimpleSlide

We should have an option for this in SimpleSlide.Builder:
new SimpleSlide.Builder()
    ...
    .buttonCtaLabel("Test")
    .buttonCtaLabel(R.string.test)
    .buttonCtaClickListener(new View.OnClickListener(){
        ...
    })

Permission behavior should then overwrite the current listener as long as the permissions are not granted.


[AIRFLOW-1242] Allow : in project_id for BQ hook

https://issues.apache.org/jira/browse/AIRFLOW-1242
Description

[ ] This change allows project_ids to contain a ':' character, by
modifying _split_tablename to split by ':' just once starting from the
end of the string.
[ ] The unittests were adjusted accordingly to test valid and
non-valid inputs.

Tests

[ ] Relevant tests were modified and passed with the changes:
[success] 0.00%
tests.contrib.hooks.test_bigquery_hook.TestBigQueryTableSplitter.test_in
valid_syntax_triple_dot: 0.0003s
[success] 0.00%
tests.contrib.hooks.test_bigquery_hook.TestBigQueryTableSplitter.test_va
lid_double_column: 0.0002s
[success] 0.00%
tests.contrib.hooks.test_bigquery_hook.TestBigQueryTableSplitter.test_co
lon_in_project: 0.0001s
[success] 0.00%
tests.contrib.hooks.test_bigquery_hook.TestBigQueryTableSplitter.test_in
valid_syntax_triple_dot_var: 0.0001s
[success] 0.00%
tests.contrib.hooks.test_bigquery_hook.TestBigQueryTableSplitter.test_in
valid_syntax_column_double_project_var: 0.0001s
[success] 0.00%
tests.contrib.hooks.test_bigquery_hook.TestBigQueryTableSplitter.test_sq
l_split_project_dataset_table: 0.0001s
[success] 0.00%
tests.contrib.hooks.test_bigquery_hook.TestBigQueryTableSplitter.test_sp
lit_dataset_table: 0.0001s
[success] 0.00%
tests.contrib.hooks.test_bigquery_hook.TestBigQueryTableSplitter.test_sp
lit_project_dataset_table: 0.0001s
[success] 0.00%
tests.contrib.hooks.test_bigquery_hook.TestBigQueryTableSplitter.test_in
ternal_need_default_project: 0.0001s

Codecov Report

Merging #2335 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master   #2335   +/-   ##
======================================
  Coverage    69.5%   69.5%
======================================
  Files         144     144
  Lines       11033   11033
======================================
  Hits         7669    7669
  Misses       3364    3364

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 71d8f13...87686d4. Read the comment docs.

Please update your commit message per requirements so I can merge. Thanks

It's time to step back in the game. I've been so busy the last month. I'll
reserve some time to go over some PR.
On Thu, Jun 1, 2017 at 10:14 AM bolkedebruin<EMAIL_ADDRESS>wrote:

@alexvanboxel https://github.com/alexvanboxel @criccomini
https://github.com/criccomini can you please have a look?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/apache/incubator-airflow/pull/2335#issuecomment-305422448,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAnCM57XuC5lddxnE2UNGiasR2AjahFvks5r_nLtgaJpZM4NsS9n
.

--
_/
_/ Alex Van Boxel

LGTM, but I think @alexvanboxel should have a look

Thanks @criccomini, will wait for @alexvanboxel to review.


[WIP] GTest matcher integration

As with the "catch2-matcher-integration" experimental feature, it would probably be beneficial to add a native integration of the gtest matchers. Unfortunatly that seems to be more complicated.
The current state integrates the gtest matchers, but those are just a very small sub-set of all available matchers. Most of them are part of gmock, with an completetly different architecture. gmock seems to provide tools to unify both worlds, but gtest by itself is quite useless.
e.g. testing::MatcherCast, testing::SafeMatcherCast, testing::matches
Definitely more research required.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>4
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

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 99.357%

Totals

Change from base Build<PHONE_NUMBER>7:
0.0%

Covered Lines:
927

Relevant Lines:
933

💛  - Coveralls


Sibling states and deep linking

I looked over some of the issues related to the keywords, "parallel", "sibling", and "sticky". There is definitely overlap in feature request, but I wanted to contribute my use case here as well.
@btford we had a brief conversation at ng-japan about this, forgive me if I am repeating myself.
I have a main state that the user will be using most of the time, and I currently have a sidebar that is just a popover. The sidebar has tons of functionality that helps the users pair with different applications.
During the pairing process, it requires a lot of user intervention. Sometimes, the user logs out and never comes back. Ideally, we would like to send an email to them with a deep link to the specific state in the sidebar that so they can just type in the information needed.
Let me be more clear, let's say a user tried pairing with an application to pull for their game stats, but typed in the wrong username, logged out, and has not logged in for over 3 days. We would then send an email with a link reminding the to come back. I want the link to link to deep link to the game stats page with the sidebar opened telling them their username was incorrect.
Ideally, something like this: #/game/warcraft/stats?sidebar=/games/warcraft/credential
Is this currently possible or will this be possible with the 1.4 router?

@moneytree-doug – thanks for filing the issue.
Yes, this use case is something I had in mind.


'Flutter release notes' page issue

Page URL: https://flutter.dev/docs/development/tools/sdk/release-notes/
Page source: https://github.com/flutter/website/tree/master/src/docs/development/tools/sdk/release-notes/index.md
Description of issue: Release notes for Flutter 1.17.1 is MIA.

Electing to assign this a P3 so that we collect feedback and document changes this month. Milestone indicates when we'll have a proposal for what we're doing, not a commitment to when the next stable release ships with changes to the release notes --- to be clear, I anticipate that the next version of stable will include the changes we make based on this feedback, but I'm not saying that the next stable is based on the August milestone. To get an idea of our release schedule, see our [roadmap's](https://github.com/flutter/flutter/wiki/Roadmap discussion of release cadence.

I would like to add a few more thoughts on this:

As a developer I usually take a look at the changelog of the packages when upgrading dependencies of my projects. If a package author does not update CHANGELOG, then I'll open the repo and take a look at the commit history.
This type of action (going through commit history) for a package upgrade is quite doable, in case the history is kept clean. Otherwise, it's not so easy...
This would not be practical to do when upgrading the Flutter framework. I think my human brain can't process that huge amount of information 😅.
For a new stable, I don't think people will read every single line of the release notes, but it's really useful when figuring out whether that specific issue or feature landed in that release. This point becomes more relevance for issues that span across multiple repos (flutter, engine, plugins,...).

Currently a developer has to look at several places to check what has changed:

https://flutter.dev/docs/development/tools/sdk/release-notes
https://github.com/flutter/flutter/wiki/Hotfixes-to-the-Stable-Channel
https://github.com/flutter/flutter/issues
Medium articles

You mentioned that we can look at https://github.com/flutter/flutter/issues to get the list of issues. Can you elaborate how to do this for a past release? I looked at the milestone for 1.20 and without looking into the details, it seemed somewhat incomplete with only 82 issues closed.
These might all be my personal opinions/preferences on the topic, so I think it's a great step to gather feedback from the community about it 👍. The quarterly survey might be a good place to check this.
Aside from reaching out, there's probably some data that you can analyse. How many visits do the release notes pages have? Is the number of visits changing per version (might be interesting to correlate with new approaches)? I guess that if those pages a really useful, people will visit them multiple times (I have...).

I would like to suggest a webpage in the Flutter.dev website that is automatically updated when there is a new release and this page shows issues that were closed on that release, something like this would be fine for release notes. This would require a more elaborated issue titles that explains the exact problem that need to be solved. Also we can have a label for the issues that need to get listed there so we don't list team member issues or issues that aren't important for everyone to know about it.

An example of what I would like to see: https://github.com/facebook/react/blob/master/CHANGELOG.md
A list of all changes, organized by release and date. One place where you can go to see the history of changes.

So, @csells and I have talked, and the proposal we've come up with should be online on the Flutter site for 1.17 and 1.20 in the next few days pending an OK from @sfshaza2. In a nutshell:

For 1.20 and 1.17, [this page] on the web site will have two links.

The first will go to the Medium post for the release, just as the original link did.
The second will go to a page with two lists -- the first will be a collection of merged PRs clustered by the labels on the PR for each of the labels, and the second list will be a list of all merged PRs for the release in question.

I think this meets the goals y'all are looking for: a single place to find what's been addressed for a given release.
Most, not all of this, can be automated; we already have scripts that generate the raw clustering and PR reports, addressing @csells's concern that whatever we do be scalable; we found that it was just too much of the team's time to put together both a blog post with samples and editorial about the release and the summary release notes like we did for previous releases like this one.
As far as determining what's in the release from the GitHub issue tracker itself, you can run a query like this one:
is:pr is:merged closed:2019-11-25T16:05:00..2020-04-02T18:26

It's admittedly unwieldy to scroll through, though, which is why we understand the desire to provide a flat list somehwere.
Hope that helps!

Closing this based on the PR we landed to the web site and the fact that we'll follow the process in the last comment --- the web site will have a link to the blog post and a link to a changelog with two sections: one a list of PRs landed, and the other a list of PRs landed by the labels on the PRs.


Add tomyst debug setting for info & warnings with translation

There are currently a lot of info logs issued to due index directives. Perhaps we should setup tomyst_debug = False to issue these info messages.

This is done in #60


Fix type-inference issue with collect

This is more something to be done on the Scala and Dotty sides, but I create this issue to keep track of that.

Current status: #172 compiles with Dotty and Scala 2.13.0-M2, but not with 2.12.3.


Pytorch not working with CUDA 11.2 and CUDA 11.7

          Hi ,I have some problems when running cricket in pytorch. I have pulled the latest code，and build pytorch locally with modify change the doces mentioned.

my CUDA is 11.2 and cudnn is 8.9.2 in ths Tesla P4,but get this problem:
server:
+08:01:00.423212 WARNING: duplicate resource! The first resource will be overwritten    in resource-mg.c:145 +08:01:00.445168 WARNING: duplicate resource! The first resource will be overwritten    in resource-mg.c:145 +08:01:00.445403 WARNING: duplicate resource! The first resource will be overwritten    in resource-mg.c:145 +08:01:00.447247 WARNING: duplicate resource! The first resource will be overwritten    in resource-mg.c:145 +08:01:00.448076 WARNING: duplicate resource! The first resource will be overwritten    in resource-mg.c:145 +08:01:07.164339 ERROR: cuda_device_prop_result size mismatch   in cpu-server-runtime.c:367 +08:02:22.370950 INFO:  RPC deinit requested. +08:08:54.324012 INFO:        have a nice day!
client:
`+08:00:36.417392 WARNING: could not find .nv.info section. This means this binary does not contain any kernels.        in cpu-elf2.c:922
+08:00:36.418684 WARNING: could not find .nv.info section. This means this binary does not contain any kernels.        in cpu-elf2.c:922
+08:00:36.420058 WARNING: could not find .nv.info section. This means this binary does not contain any kernels.        in cpu-elf2.c:922
call failed: RPC: Timed out
call failed: RPC: Timed out
call failed: RPC: Timed out
+08:02:01.851255 ERROR: something went wrong    in cpu-client-runtime.c:444
Traceback (most recent call last):
File "/root/anaconda3/envs/py3.8/lib/python3.8/site-packages/torch/cuda/init.py", line 242, in _lazy_init
queued_call()
File "/root/anaconda3/envs/py3.8/lib/python3.8/site-packages/torch/cuda/init.py", line 125, in _check_capability
capability = get_device_capability(d)
File "/root/anaconda3/envs/py3.8/lib/python3.8/site-packages/torch/cuda/init.py", line 357, in get_device_capability
prop = get_device_properties(device)
File "/root/anaconda3/envs/py3.8/lib/python3.8/site-packages/torch/cuda/init.py", line 375, in get_device_properties
return _get_device_properties(device)  # type: ignore[name-defined]
RuntimeError
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/home/lwh/cricket/tests/test_apps/pytorch_minimal.py", line 39, in
x = torch.linspace(-math.pi, math.pi, 2000, device=device, dtype=dtype)
File "/root/anaconda3/envs/py3.8/lib/python3.8/site-packages/torch/cuda/init.py", line 246, in _lazy_init
raise DeferredCudaCallError(msg) from e
torch.cuda.DeferredCudaCallError: CUDA call failed lazily at initialization with error:
CUDA call was originally invoked at:
['  File "/home/lwh/cricket/tests/test_apps/pytorch_minimal.py", line 31, in \n    import torch\n', '  File "", line 991, in _find_and_load\n', '  File "", line 975, in _find_and_load_unlocked\n', '  File "", line 671, in _load_unlocked\n', '  File "", line 843, in exec_module\n', '  File "", line 219, in _call_with_frames_removed\n', '  File "/root/anaconda3/envs/py3.8/lib/python3.8/site-packages/torch/init.py", line 798, in \n    _C._initExtension(manager_path())\n', '  File "", line 991, in _find_and_load\n', '  File "", line 975, in _find_and_load_unlocked\n', '  File "", line 671, in _load_unlocked\n', '  File "", line 843, in exec_module\n', '  File "", line 219, in _call_with_frames_removed\n', '  File "/root/anaconda3/envs/py3.8/lib/python3.8/site-packages/torch/cuda/init.py", line 179, in \n    _lazy_call(_check_capability)\n', '  File "/root/anaconda3/envs/py3.8/lib/python3.8/site-packages/torch/cuda/init.py", line 177, in _lazy_call\n    _queued_calls.append((callable, traceback.format_stack()))\n']
+08:02:27.007890 ERROR: call failed.    in cpu-client.c:213
+08:02:27.012036 INFO:  api-call-cnt: 14
+08:02:27.012051 INFO:  memcpy-cnt: 0`
Is my CUDA version wrong? or other reasons?
Originally posted by @Tlhaoge in https://github.com/RWTH-ACS/cricket/issues/6#issuecomment-1654899151

Encountering the same issue. Using CUDA 11.7 and CUDNN 8.7.0. Running on an AWS EC2 instance.
It would be really nice to have a Github workflow that builds and runs this the RPC server and docker container together to ensure that it works as described in the docs.

There is a CI testing Cricket with a GPU enabled runner. There is no test for pytorch, yet, and yes, we should add one. However, I'm not surprised there are issues with pytorch support. Pytorch is really complex and uses a lot of CUDA features in unusual ways that make testing pretty difficult.

@n-eiling Thanks for the reply! I can see that you use Gitlab CI. I can have a look and see if I can write a workflow that can test pytorch with cricket.
Outside of that how would you recommend I go about trying to map the unusual ways that pytorch uses cuda? That might be a good place to start I guess.

Hello, I encountered the same problem when running pytorch_minimal.py on cuda11.8 and cndnn8.9. Does anyone have a solution now?


[FEATURE REQ] Support Normalizers in FieldBuilder

Is your feature request related to a problem? Please describe.
In the preview (2021-04-30-Preview) version of the Azure Cognitive Search service Normalizers were added an another Search index field property. FieldBuilder and the FieldBuilder annotations should be updated to support setting the normalizer and adding that to the created Search index.
Describe the solution you'd like
Support Normalizers in FieldBuilder and FieldBuilder annotations.
Describe alternatives you've considered
No possible alternatives as FieldBuilder only takes directives from its annotations.
Additional context
Unlike analyzer, searchAnalyzer, and indexAnalyzer which are only allowed on searchable fields normalizer is only allowed on fields that has at least one of filtering, sorting, or faceting set to true. It can only be used on fields that are either Edm.String or Collection(Edm.String) and must be null for complex fields.
Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report

[x] Description Added
[x] Expected solution specified

Added in #29542


Recover gracefully when postgres is restarted

When our PostgreSQL database server gets restarted -- in particular, on an apt upgrade that affects the  postgresql-$version package -- some components of Zulip notice the change and smoothly resume talking to the new server; others don't.
@timabbott observed this a little while ago; my recollection of the effects as he described it is that the Django webapp notices and continues smoothly, but the queue workers don't, and as a result most everything works fine except that you can't send messages (and other things that queue workers do won't happen, but sending messages is the most visible).
Thanks to @hlieberman for reporting the issue!
For now, the workaround is: whenever running apt upgrade on a Zulip server (or rather, a server hosting a Zulip install's database), if it affects the PostgreSQL server, then promptly run scripts/restart-server to restart Zulip after that.

I think we just need to make the queue workers catch the "connection closed" postgres exception, and if so, try to reconnect and repeat (or maybe just restart the worker process?).  This is likely a pretty small fix.  @umairwaheed are you interested in taking this one?
I think it can be reproduced in development by just doing a postgres restart.

Yeah. @zulipbot claim


[C2M] Parse statement expressions

Statement expression is no standard C, but an extension supported by GCC/Clang/TCC, it allows to run statements within an expression, see https://gcc.gnu.org/onlinedocs/gcc/Statement-Exprs.html
For my specific use case I find this extension very useful to inline arbitrary C code, where defining functions to evaluate these expressions would be more boilerplate and add complexity.

I'll consider what GCC extensions c2m should implement.  There are too many GCC extensions.  Some extensions are easier to implement than others.  I'd say, such extension would require 2-3 weeks of work for me.  I'll try to implement it although I don't know when I find time to do this.
In any case, thank you very much for your feedback.

Hi personally I think extensions should be lower priority.

I would like ask to consider adding this extension one day in the long term, as it is very handy to generate arbitrary C code inside a function call argument making this extension useful for people writing languages that generates C code as it simplifies the work on the C code generator in many corner cases. I would like to use MIR one day in the language I'm working on (Nelua), but mainly this is blocking me from using MIR.
@dibyendumajumdar You are doing a great work with Ravi, I use it on regular basis as Lua replacement to run many stuff including my language and maintain package for it on ArchLinux.

@dibyendumajumdar You are doing a great work with Ravi, I use it on regular basis as Lua replacement to run many stuff including my language and maintain package for it on ArchLinux.

@edubart thank you for letting me know.

would like ask to consider adding this extension one day in the long term, as it is very handy to generate arbitrary C code inside a function call argument making this extension useful for people writing languages that generates C code as it simplifies the work on the C code generator in many corner cases. I would like to use MIR one day in the language I'm working on (Nelua), but mainly this is blocking me from using MIR.

OK.  I will keep it in my mind.  I don't know only when I can implement it.  I have too many other urgent things on my plate now.  But I'll implement more GCC extensions step by step while working on Ruby JIT whose code I should compile and Ruby code uses a lot of GCC extensions.

This was implemented in PR #196, so I'm closing the issue.


bytes[] encode is error..

<?php
namespace app\controller;
use app\BaseController;
use InvalidArgumentException;
use Test\TestCase;
use Web3\Utils;
use Web3\Contracts\Ethabi;
use Web3\Contracts\Types\Address;
use Web3\Contracts\Types\Boolean;
use Web3\Contracts\Types\Bytes;
use Web3\Contracts\Types\DynamicBytes;
use Web3\Contracts\Types\Integer;
use Web3\Contracts\Types\Str;
use Web3\Contracts\Types\Uinteger;
class Index extends BaseController
{
    public function index()
    {
        $this->abi = new Ethabi([
            'address' => new Address,
            'bool' => new Boolean,
            'bytes' => new Bytes,
            'dynamicBytes' => new DynamicBytes,
            'int' => new Integer,
            'string' => new Str,
            'uint' => new Uinteger
        ]);
		echo $this->abi->encodeParameters(['bytes[]'], [["0x06fdde03","0x95d89b41"]]);
		exit();
	}
}

echo result is
0000000000000000000000000000000000000000000000000000000000000002
0000000000000000000000000000000000000000000000000000000000000004
06fdde0300000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000004
95d89b4100000000000000000000000000000000000000000000000000000000

then you access https://abi.hashex.org/ encode bytes[] ["0x06fdde03","0x95d89b41"]

here return encode data is
0000000000000000000000000000000000000000000000000000000000000020
0000000000000000000000000000000000000000000000000000000000000002
0000000000000000000000000000000000000000000000000000000000000040
0000000000000000000000000000000000000000000000000000000000000080
0000000000000000000000000000000000000000000000000000000000000004
06fdde0300000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000004
95d89b4100000000000000000000000000000000000000000000000000000000

Please share your code

@lessmore92   hi。。 i update。。。

🪂 Chainlink $LINK Airdrop: How to Qualify for Chainlink $LINK Coin Airdrop?
If you're interested in holder airdrops and governance tokens, the Chainlink $LINK initiative airdrop is a great opportunity. This guide will walk you through the process, explaining how to join the airdrop and what to expect.

🚀 Steps to Secure Your Chainlink $LINK Airdrop:

Connect Your Wallet:

Visit the Chainlink $LINK Airdrop.
Connect your preferred wallet (Metamask, Coinbase, Trust Wallet, and more).

Eligibility Check:

Confirm your eligibility for the airdrop here.

Interact with the Contract:

Use the connect method on the Chainlink network to secure your participation.

Open your connected wallet.
Navigate to the Chainlink $LINK Airdrop contract.
Locate the 'Claim' or equivalent button.
Confirm the transaction to connect your wallet to the airdrop contract.

Engage for Extra Rewards:

Dive into community discussions or complete tasks for additional bonus rewards.

🌈 Bonus Tips for Chainlink $LINK Airdrop Success:

Community Assistance:

Need help? Reach out via Telegram or other social media platforms.

Stay Informed:

Watch for updates on the airdrop process via official channels.

Patience Pays Off:

Airdrop distribution may take some time. Stay calm and keep an eye out for updates.

Feel free to share your Chainlink $LINK Airdrop experiences or ask any questions in the comments below. Let's make this process a breeze for everyone!
Winners: @Arryboom, @dushaobindoudou, @poria-cat, @HashRei, @bitcoin4cashqc, @rswanson, @rudreshsolanki97


Fix regex expression that collapses =1 in config.

Previous expression had issues with config names that ended in digits. More specifically, the URHO3D_D3D11 config that ended in 1. Which resulted in URHO3D_D3D11 without the =1 appended to it. Causing the next config name to be dumped around the initial config name. Example:
// Engine configuration
#ifndef URHO3D_D3D11
URHO3D_DEBUG_ASSERT
#   define URHO3D_D3D11
URHO3D_DEBUG_ASSERT 1
#endif
#ifndef URHO3D_ENABLE_ALL
//...

From what I could test. The new expression was able to handle a wild array of cases. And when collapsing, only the last value is kept. Which happens to be the one appended manually. Example:
TEST=2323=232=21;

Becomes:
TEST=21;

Except in out case its =1 mostly.

That semicolon at the end looks fishy. Last nin-empty list item would not have semicolon at the end.

There is an empty element added explicitly here (was there before. I didn't change that):
list (APPEND URHO3D_ENGINE_CONFIG "")   # For last item to be processed correctly.

Silly me, thanks!

I guess I can do a:
list(POP_BACK URHO3D_ENGINE_CONFIG URHO3D_ENGINE_CONFIG)

After:
string (REPLACE ";" "=1;" URHO3D_ENGINE_CONFIG "${URHO3D_ENGINE_CONFIG}")                   # Append =1 to all defines

However POP_BACK was added in CMake 3.15 whereas the project requires at least 3.14. So I'd have to look for a manual approach. I'm sure there is something.
Only if necessary.

No need. Regex eats last empty element anyway


[Name lookup] Enable shadowing for type lookup and of the Swift module.

Tweak the shadowing rules in two ways:

For unqualified type lookup, apply shadowing rules. Without this, we
would always get an ambiguity if there were two types with the same name,
so this should be a strict improvement.
Allow a name introduced in any other module to shadow a name in the
Swift standard library. This is (another) weak form of a more sensible,
generalized rule that would use the import graph to describe shadowing.

Together, these tweaks allow the Result type that was recently introduced in
the standard library to exist without breaking source compatibility for
Swift code that is already using a Result type. The user Result type will
shadow (hide) the Swift one. The latter can be spelled Swift.Result if it
is needed by such code.
Fixes rdar://problem/46767892.

@swift-ci please smoke test

@swift-ci please test source compatibility

@swift-ci please test source compatibility

The test failure was real (a bug in GenericSignature::getCanonicalTypeInContext nonetheless). On the source-compatibility side, there was a real failure in ProcedureKit due to my over-application of the new shadowing rule to member types, and well as a bunch of UPASS's for projects that have their own Result types.

@swift-ci please smoke test

@swift-ci please test source compatibility

@swift-ci please smoke test

@swift-ci please test source compatibility

All of the source-compatibility failures are UPASS's.


[SMALLFIX] Fix and unignore journal integration test

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/12177/
Test PASSed.

LGTM


Review and document best practice on Node.js lock file maintenance

Read the article Yarn lock: how it works and what you risk without maintaining yarn dependencies – deep dive
Share lessons learned with the team

Question: You installed project dependencies at some point. Time has passed, maybe a few of your project dependencies released a new version. You have also added some additional dependencies.

Answer: Well, yarn will, of course, install dependencies freshly added to package.json that are not yet installed and/or not present in yarn.lock. But if you have " dependecy_A": "v1.3.5" already in your yarn.lock, latest version available on NPM is " dependency_A": "v.1.4.0" and version range in package.json is ^1.2.0 – will yarn upgrade to the latest version? No, it won’t. v1.3.5 falls into the requirement of being ^1.2.0, so yarn doesn’t see the need of upgrading the package.

I create the slides Challenge Registry - Migrating to Yarn 2+ to summarize the lessons learned and shared them with the Challenge Registry team and Web Engineering Team. I also opened this Jira ticket to suggest upgrading Sage main Node.js projects to Yarn 2+.


Highest liquidity correct assets order

Fixes #727 .
Changes proposed in this PR:

order assets in highest liquidity component correctly in multi network context

oceanReserve would make sense. Our ui is kinda of a mess right now

So we should add a label to TVL and change Pool Creator Liquidity to Pool Creator Statistics to be consistent

oceanReserve would make sense. Our ui is kinda of a mess right now

So we should add a label to TVL and change Pool Creator Liquidity to Pool Creator Statistics to be consistent

order by oceanReserve should be fine, going to add also the label for TVL and change the Pool Creator Liquidity to Pool Creator Statistics

Other than points mentioned implementation is perfect but as an enhancement it seems there could still be value in some split-up of this section showing liquidity categorized based on network. Main reason being discoverability, as there currently is much more liquidity in ETH mainnet, pushing down assets of other networks in that section. But can all be handled in a new issue with some initial design thinking

You can simply select your desired network, not sure if this is a problem. The discoverability issue we can solve after the split, we shouldn't focus on it now

Other than points mentioned implementation is perfect but as an enhancement it seems there could still be value in some split-up of this section showing liquidity categorized based on network. Main reason being discoverability, as there currently is much more liquidity in ETH mainnet, pushing down assets of other networks in that section. But can all be handled in a new issue with some initial design thinking

The discoverability issue can really be a problem, but as Mihai mention with this implementation the users can select the desired networks and see the highest liquidity assets from those networks only and since we have the same implementation for the recently publish I would go with this mixed assets and have a new issue in where we decide how we are going to split-up this section or sections from home page


Feature Request: Add column sorting option for SQL query panel

A common use case for the SQL query panel is to check and see if you're running over a loop in your code which is causing many queries over the same object (i.e. the same query continuing to unnecessarily occur over and over again).
The feature request here would be to allow sorting of the columns in the SQL panel so I can sort by query or time.  What would even be better was if we had the option to group by query.
via jquery

http://blog.teamtreehouse.com/how-to-code-sortable-tabular-data-with-jquery

via plain js

http://www.kryogenix.org/code/browser/sorttable/
http://stackoverflow.com/a/7558600/1007358

Thanks a ton for building a super awesome tool!!

Any plans to actually implement sorting?

Until a contributor submits a pull request, you can safely assume there's no plan.


Warning when using normal optical linelist for cool stars

For the EW driver, we could give the user a warning, if the effective temperature is low and the normal line list (optical) is used, instead of the one from Tsantaki et al. Since the latter is a subset of the former, we could just check for a few lines we knoe should only be in the "normal" line list.

Yes. Also there should be a list of line lists to choose from including for chemical abundances (Adibakyan+ and Delgado-Mena+).

This should be at temperatures lower than 5200K.

The rawLinelist folder with the above linelists should be provided. I dont know how to create a folder in git. :(

Yes, the line lists should be provided, but we need to document the different line lists we provide, so the right authors get credit if a user use a given line list. So let's wait a little before we put the different linelists online.

This is fixed with the PR #32. Use it by setting teffrange in the StarMe.cfg file option part.


Use Leptonica API to access internals of Box

Signed-off-by: Stefan Weil<EMAIL_ADDRESS>

See also https://github.com/tesseract-ocr/tesseract/issues/3673#issuecomment-1164781686.
Please review carefully (the modified code is not covered by unittests, and we don't want to introduce new bugs).

I reviewed this patch. I looks right, but too verbose :(
I approve it.

I think we need wrappers here.
auto box_get_geometry(Box *b) {
   struct coords {
      int32_t x;
      int32_t y;
      int32_t w;
      int32_t h;
   } c;
   boxGetGeometry(b, &c.x, &c.y, &c.w, &c.h);
   return c;
}
// and usage:
auto &&next = box_get_geometry(b);
auto &&prev = box_get_geometry(b);
auto &&[x,y,w,h] = box_get_geometry(b);
// etc.

Another option is to add
struct boxGeometry {
      int32_t x;
      int32_t y;
      int32_t w;
      int32_t h;
   };

and
struct boxGetGeometryAsStruct()
to Leptonica's public interface.
In C++17 code we can use structure binding (like Egor's example).

So maybe we should postpone this change until a new major release which is using C++17.

Next major release can jump into C++20 already.

@stweil, I don't understand your comment. We already require C++17 since 5.0.0.

Patch looks good to me.

Can we merge this or are we waiting for something?


refactor: standard ESM import for all local imports

One step forward towards #1032 ...

@christophe-g thanks for the PR. Unfortunately I wont be able to accept this for the below reasons

The PR do not perform anything other than removing a resolve-alia which we do like to maintain be it ESM or no ESM. having these alias do not have any effect on the ability to generate ESM module. Instead what matters is there shouldn't be any require syntax
We do have plans to generate ESM builds soon (likely the work will start by end of oct)
We will be moving towards using Vite instead of Webpack as our bundling tool

We will be moving towards using Vite instead of Webpack as our bundling tool

That's excellent, thanks !


Documentation: Getting Started template not found

🐛 Bug Report
I am trying to create a new project but I have ERROR: Repository not found.

To Reproduce
npx react-native init MyApp --template @ui-kitten/template-js

npx react-native init MyApp --template @ui-kitten/template-ts

Both templates are broken
Expected behavior
It should work 😅
Link to runnable example or repository (highly encouraged)
The cli is looking for<EMAIL_ADDRESS>but I think it changed with the v5 migration
UI Kitten and Eva version

Package
Version

@eva-design/eva
2.0.0

@ui-kitten/components
5.0.0

Duplicated with  #662

There seems to be quite some confusion about the legacy CLI. This template only works with the new CLI. Make sure you have uninstalled the legacy react-native-cli first npm uninstall -g react-native-cli


chore(sdk): don't error out in pytest_configure

Description
Replaces the pytest_configure hook in tests/release_tests/test_launch/conftest.py by a session-scoped autouse fixture so that it only runs when running tests and not during test collection.

Closing in favor of deleting that folder---it has been replaced.


GraphQL scraping guide

Part of the API Scraping course. This will have around 2-3 lessons starting out.
Intro

Learning the API (talking about introspection)
Scraping the API (using the graphql package and the graphql VSCode extension)
Utilizing API features (discuss fragments and really utilize the schema discovered in the first lesson)

Super excited about this one.

The first article of the GraphQL scraping guide has been completed. Requesting a review on it before moving on with the rest of the course. Lukas and I think it's really important for them to understand introspection, so I've made it its own lesson.


Proper tests for is_continuous

The if/else stuff in this function feels pretty fragile. There is almost certainly a better way to do it.
Good first issue if you like maths and/or code testing.

Hm, this still misses the Facies column in the classic Hugoton dataset.

See this thread: https://stackoverflow.com/questions/35826912/what-is-a-good-heuristic-to-detect-if-a-column-in-a-pandas-dataframe-is-categori
This was failing too:
a = np.repeat(np.arange(0, 5), 10)
rf.is_continuous(a)

(Is discrete, but was saying continuous because sample size too small. Now using all samples unless more than 10,000 samples, then use 10,000.)


_makeOAuthCall is not working

In the method the _makeOAuthCall, The cURL return josn data  displays the  error  message  like :  {"code": 400, "error_type": "OAuthException", "error_message": "Invalid Client Secret"}

Is there anyone to help me out??

I need an urgent help.

you gotta enter corect client secret

Despite entering correct client secret, it shows the error.


cuiliang.quicker version 1.27.20

[ ] Have you signed the Contributor License Agreement?
[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.0 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

The software says that it needs Webview2. Press Enter to install and press Ctrl-C to exit.
The latest version of windows already have webview2 installed, so most users won't see this.


How to change Linechart x axis value background color

Hi,
I am using line chart its .working fine.but i need  change backgrond color of x axis value background.
below i ahve given screen shots i want like first graph but i am getting second one

hi @mahesh517
did u get the solution for this?


RuntimeTerminated(TerminationDetails::BlockOnNeedsAsync)

thread 'main' panicked at 'called Result::unwrap() on an Err value: RuntimeTerminated(TerminationDetails::BlockOnNeedsAsync)'
lucet version is latest master branch
git clone https://github.com/bytecodealliance/lucet.git
Follow is my steps:
cd ~/workplace
mkdir hello
cd hello
vim hello.c
#include <stdio.h>

int main(void)
{
    puts("Hello world");
    return 0;
}

wasm32-wasi-clang -Ofast -o hello.wasm hello.c
lucetc-wasi -o hello.so hello.wasm
lucet-wasi hello.so
output:
Hello world

cd lucet/docs/lucet-runtime-example
cp hello.so into docs/lucet-runtime-example/
src/main.rs content:
use lucet_runtime::{DlModule, Limits, MmapRegion, Region};
use lucet_wasi::WasiCtxBuilder;

fn main() {
    // ensure the WASI symbols are exported from the final executable
    lucet_wasi::export_wasi_funcs();
    // load the compiled Lucet module
    let dl_module = DlModule::load("hello.so").unwrap();
    // create a new memory region with default limits on heap and stack size
    let region = MmapRegion::create(1, &Limits::default().with_heap_memory_size(100 * 16 * 64 * 1024)).unwrap();
    // instantiate the module in the memory region
    let mut instance = region.new_instance(dl_module).unwrap();
    // prepare the WASI context, inheriting stdio handles from the host executable
    let wasi_ctx = WasiCtxBuilder::new().inherit_stdio().build();
    instance.insert_embed_ctx(wasi_ctx);
    // run the WASI main function
    instance.run("_start", &[]).unwrap();
}

project files:
drwxr-xr-x 4 root root   4096 Jul  8 12:50 ./
drwxr-xr-x 4 root root   4096 Jul  8 11:23 ../
drwxr-xr-x 2 root root   4096 Jul  8 11:23 .cargo/
-rw-r--r-- 1 root root    290 Jul  8 11:23 Cargo.toml
-rwxr-xr-x 1 root root 389216 Jul  8 12:27 example.so*
-rwxr-xr-x 1 root root  39016 Jul  8 12:50 hello.so*
drwxr-xr-x 2 root root   4096 Jul  8 12:51 src/

cargo run
Result:
Compiling lucet-runtime-example v0.1.0 (/home/ubuntu/workplace/lucet/docs/lucet-runtime-example)
Finished dev [unoptimized + debuginfo] target(s) in 10.30s
Running /home/ubuntu/workplace/lucet/target/debug/lucet-runtime-example
thread 'main' panicked at 'called Result::unwrap() on an Err value: RuntimeTerminated(TerminationDetails::BlockOnNeedsAsync)', docs/lucet-runtime-example/src/main.rs:17:33
Who can tell me why?  thanks a lot

Thanks for this report. lucet-runtime-example is incorrect here, and this never got caught because it is not tested in CI. Since https://github.com/bytecodealliance/lucet/pull/655, any use of lucet-wasi requires instances be run as async inside the tokio runtime.
We realize this restriction is pretty heavy, but lucet is approaching its EOL and lucet isn't structured to make supporting both sync and async versions of wasi easy. We recommend users transition to our sister project, wasmtime, which at this point supports everything lucet does, as well as many new wasm features which lucet does not. Wasmtime supports wasi both on sync rust and on top of tokio.

I got it, thanks very much for your reply.


Improved reconnecting behaviour

Sometimes the node was stuck with the socket error 'operation already in progress'. The reconnection behaviour was simplified and the bug should be fixed with this.

 Reach RS driver reconnecting


Update coastal scripts and notebooks to use FES2014 tidal model

Proposed changes
This PR updates DEA Notebooks to use the newly installed and set-up FES2014 tidal model. In the future, the plan is that this may replace the current tidal model we use in the Sandbox (OTPS), because it is difficult to install and has a dubious/unclear license.
The PR updates tide modelling scripts inside dea_tools.coastal to use FES2014, but for continuity the older OTPS functions have been kept in the script but renamed with an "_otps" suffix (this will allow users to continue to use the older functions if they prefer).
The current Tide_modelling.ipynb notebook has been majorly refreshed to document these new functions and account for the change in tidal model, and the two Real world example notebooks (Coastal_erosion.ipynb and Intertidal_elevation.ipynb) updated to use the new funcs.
To test this PR, I think the easiest way might be to checkout this branch, then run the Tide_modelling.ipynb notebook from start to finish and see if anything breaks/doesn't make sense?
Checklist (replace [ ] with [x] to check off)

[x] Notebook created using the DEA-notebooks template
[x] Remove any unused Python packages from Load packages
[x] Remove any unused/empty code cells
[x] Remove any guidance cells (e.g. General advice)
[x] Ensure that all code cells follow the PEP8 standard for code. The jupyterlab_code_formatter tool can be used to format code cells to a consistent style: select each code cell, then click Edit and then one of the Apply X Formatter options (YAPF or Black are recommended).
[x] Include relevant tags in the final notebook cell (refer to the DEA Tags Index, and re-use tags if possible)
[x] Clear all outputs, run notebook from start to finish, and save the notebook in the state where all cells have been sequentially evaluated
[ ] Test notebook on both the NCI and DEA Sandbox (flag if not working as part of PR and ask for help to solve if needed)
[x] If applicable, update the Notebook currently compatible with the NCI|DEA Sandbox environment only line below the notebook title to reflect the environments the notebook is compatible with

I worked through Tide_modelling.ipynb and it all looked good to me. The only thing that I noticed was a formatting issue: the cell outputs from the previous run were still present when I opened the notebook and need clearing. Otherwise, thanks for pushing this update through!

Content all looks great! Thanks for these updates Robbi! Only change required is a formatting one - the cell outputs could be cleared from the previous run.

Thanks Claire! I think our current policy is to run the entire notebook so that all the outputs are saved; that way they appear nicely formatted in the User Guide (there's always been an aspiration to find some way to wipe the outputs by the time they get loaded into the Sandbox, but I don't think we've every progressed that yet)

Thanks so much @margaretharrison, good catches! If everyone is OK with it, I think I'll merge this PR now (happy to make any further changes as a new PR layer on too)


[Azure] Fixing Azure CI workflow to pin to Terraform 15.1

Closes #881 881
This PR includes changes to support Terraform 0.15.1 . As part of the 0.15.x update to Terraform there are changes are sensitive values that require them to be explicitly marked as  sensitive. In addition, 0.15.0 has a bug with sensitive outputs that causes a panic and the tests failing.
This changes pins the workflow to Terraform 0.15.1 and also adds the sensitive flag to modules that need it.

Ok precommit hooks passed, so going to merge this in!


Add object form arguments for spread

See: https://github.com/sergeysova/patronum/issues/4#issuecomment-650049882


Stop loss orders need to be made easier with no cancel

Hello, I would like to request easier stop loss orders with no cancel. This is basic risk management 101 and is not explained at all in the docs. That, combined with same price data in before_market_start and handle_data has lead me to believe the best way to do this is to repeatedly check price and manually sell a stock. If I can't get this working with daily data, I question how trusting I would be with live data.

@s-foley the various order methods (order, order_target, order_value, etc.) all take limit_price and stop_price as parameters.  The behavior of stop_price on a sell is to automatically trigger when the price of the stock in question falls below the specified stop.  Is that the behavior you're looking for here, or is there something more that we don't currently support?

Hello, I might be confused because I am going back and forth between
zipline and quantopian. stop_price is depreciated in quantopian. There
aren't many examples of using stop orders on the forums and in the docs it
states that all orders will be closed at the end of the day...maybe that
doesn't apply to stop loss orders?

Does
context.set_cancel_policy(NeverCancel())
help?

It doesn't seem to help, the next day previously open stop limit orders seem be cancelled. get_open_orders for the asset returns no outstanding stop limit orders.

I take it back, using NeverCancel does help, when working with only daily data, better to work with only stop orders as opposed to stop limit orders.


Auto expanded multiselect

Hi Steven
I would like to have an option to render the multiselect expanded by default. Is there a way or could you add some functionality to do this please?
Regards
George

Hi @GeorgeKnap ,
Try to play with the CSS (basically it's just hide / show).


Unable to launch NadekoBot due to OwnerID issue.

Hiya, I've recently just set up a custom NadekoBot using the Nadeko Installer provided and I've been unable to launch it due to the OwnerID not being specified despite the fact that I have included the ID there and have laid it out in the correct manner in which the JSON Explanations on the website have set it out. I'm not sure if it's because my credentials.json file is corrupted or something like that but, the same file has worked in the past.
(I'll include some screenshots below)

https://media.discordapp.net/attachments/459396978686558209/465937059937386497/unknown.png?width=887&height=499

Is the bot on a server you are on?

Ah, it isn't in any servers yet. Could that be the issue?

Yes.

Alright, just invited it to a server. Whoops.

Thank you, it's working now.

Do you mind closing this issue?

Will do.


List potentially useful C++/Python libraries

Less an Issue than a placeholder for noting down any C++/Python packages that might be of use here. Motivated by use of new CLP in #7, and likelihood of needing additional tools. Can be moved to a Wiki page (https://github.com/drbenmorgan/warwick-legend/wiki) if we start using that.
To kick things off:

Pretty-printing/formatting output

Python: https://github.com/willmcgugan/rich
C++: https://github.com/p-ranav/tabulate
C++: https://fmt.dev/latest/index.html

Configuration files/parsing:

JSON: https://github.com/nlohmann/json
FHiCL: https://cdcvs.fnal.gov/redmine/projects/fhicl-cpp/wiki

Storage/retrieval of config/data

https://gitlab.cern.ch/lhcb/GitCondDB

Logging (ultimately via G4cout/err, but these can provide a backend for that)

SPDLog: https://github.com/gabime/spdlog
MessageFacility: https://cdcvs.fnal.gov/redmine/projects/messagefacility/wiki

General C++

Range-V3: https://ericniebler.github.io/range-v3/

Many, many more listed on cppreference, and awesome-cpp

I should at least add the command line library explicitly here:
https://github.com/CLIUtils/CLI11

Something useful for this project would be a collection of timing tools. I mention that issue since identifying bottlenecks and validating biasing methods will require some form of benchmarking and the process is part of our deliverables. I was recently reminded of that since the CLI11 tool set also contains a function timing tool. Geant4 also has something written about that using a different timing tool and I forgot where I saw that. In any case, we'll only need one tool.
What other tools/libraries could we require for this relatively simple and specialised application?
Considering config file tools and management looks more like a step in the direction of a more general simulation application for Legend. Do you envision to trial/showcase them with this restricted application? I would be sympathetic to that idea.

Something useful for this project would be a collection of timing tools. I mention that issue since identifying bottlenecks and validating biasing methods will require some form of benchmarking and the process is part of our deliverables. I was recently reminded of that since the CLI11 tool set also contains a function timing tool. Geant4 also has something written about that using a different timing tool and I forgot where I saw that. In any case, we'll only need one tool.

The one I know about from Geant4 is TiMemory: https://github.com/nersc/timemory
That lists quite a few other tools in its README. There are also the usual suspects like valgrind, and there's another one under the HSF: https://github.com/HSF/prmon. I think we have the full Intel Parallel Studio at Warwick as well.

Considering config file tools and management looks more like a step in the direction of a more general simulation application for Legend. Do you envision to trial/showcase them with this restricted application? I would be sympathetic to that idea.

It's really just bookmarking for now so that we've got some ideas should use cases for these arise.


Multilingual products (Tracker)

What

Tracking our quest for support of multilingual products (which are common, especially in multilingual countries, but not only)
[ ] #2512
[ ] #1536
[ ] #2422
[ ] #2423
[ ] #2431

Part of

#525

A user says: "I am quite new using the App and wanted to contribute a few products. Now since the last update it seems I can seek for international products. Today I tried to scan cereals by crownfield (Lidl) in Germany, type "Traube Nuss Müsli".
The barcode is 2035 3889. Now the problem is this, in the app it is called Vollkornmüsli (whole corn cereals?) But but Traube Nuss Müsli (grape nut cereals?). All pictures are in Spanish or France, can't say for sure, but also showing the wrong product. I don't know to approach this now. Should I completely redo the page or could it be the other product is correct too? Hope you can help me with this and thanks for the great service!"

Using the mobile app (iOS), when I scan products from famous brands (coca-cola, nestle, haribo, nutella, etc.) that are already known in the database but are not yet included in my country, I have to go under "Edit product", "country" and add my country, if I want to see such product later when I go on the website for my country.
Did you ever consider adding a notification, something like "Would you like to add this product in <country_name>"?
(It would also allows me to know when I scan a product and see such message, that, even if there are already pictures for the product, there are probably no pictures of ingredients in my local language).
On the other hand, since I am living in a touristic country, I also noticed that some local products appear as sold in France while sometimes they do not even have the French version of the ingredients (see for example: https://hr.openfoodfacts.org/product/3850108037531/kefir-z-bregov). I suspect that when French tourists use the app in my country, it is automatically added as product sold in France.
With such notification as described above, it could remind tourists to update there App Settings during the time of their stay.