Unhandled Exception: Converting object to an encodable object failed: _Map len:6

@abom-me
I am getting this error while passing product list.
Error : Unhandled Exception: Converting object to an encodable object failed: _Map len:6
I am using the latest package thawani_payment: ^0.0.6
Product List that i am passing is given below :
[
{"name": "Product 1", "quantity": 10, "unit_amount": 10},
{"name": "Product 2", "quantity": 20, "unit_amount": 20}
]

the package updated and the issue are fixed ✅


run on custom dataset

Hello Dewei,
thank you for sharing your work!
Is it possible to run your code on a custom Dataset? If yes, how would i manage this?

Hi there,
Yes, if you have relatively clean data, you can certainly pollute it with customized noise and then try the model to denoise it. In this way, the original image can be leveraged as reference for evaluation.

From: marius9043 @.>
Sent: Thursday, July 20, 2023 8:58 AM
To: DeweiHu/OCT_DDPM @.>
Cc: Subscribed @.***>
Subject: [DeweiHu/OCT_DDPM] run on custom dataset (Issue #9)
Hello Dewei,
thank you for sharing your work!
Is it possible to run your code on a custom Dataset? If yes, how would i manage this?
—
Reply to this email directly, view it on GitHubhttps://github.com/DeweiHu/OCT_DDPM/issues/9, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AL6WZQHFBTHUCI2OU2673WLXRE2RTANCNFSM6AAAAAA2RPGMZM.
You are receiving this because you are subscribed to this thread.Message ID: @.***>


IndeterminateOffset error while running tests in a clean chroot (Arch Linux build)

Hello! I'm getting the following errors for the tests while building coreutils 0.0.17 for Arch Linux:

Log
---- test_cp::test_cp_archive stdout ----
current_directory_resolved:
thread 'test_cp::test_cp_archive' panicked at 'called `Result::unwrap()` on an `Err` value: IndeterminateOffset', tests/by-util/test_cp.rs:1189:48

---- test_cp::test_cp_no_preserve_timestamps stdout ----
current_directory_resolved:
thread 'test_cp::test_cp_no_preserve_timestamps' panicked at 'called `Result::unwrap()` on an `Err` value: IndeterminateOffset', tests/by-util/test_cp.rs:1325:48

---- test_cp::test_cp_preserve_timestamps stdout ----
current_directory_resolved:
thread 'test_cp::test_cp_preserve_timestamps' panicked at 'called `Result::unwrap()` on an `Err` value: IndeterminateOffset', tests/by-util/test_cp.rs:1292:48

---- test_mv::test_mv_update_option stdout ----
current_directory_resolved:
touch: /tmp/.tmpFXv3ix/test_mv_update_option_file_a
touch: /tmp/.tmpFXv3ix/test_mv_update_option_file_b
thread 'test_mv::test_mv_update_option' panicked at 'called `Result::unwrap()` on an `Err` value: IndeterminateOffset', tests/by-util/test_mv.rs:622:48

---- test_pr::test_with_column stdout ----
current_directory_resolved:
thread 'test_pr::test_with_column' panicked at 'called `Result::unwrap()` on an `Err` value: IndeterminateOffset', tests/by-util/test_pr.rs:21:62

---- test_pr::test_with_column_across_option stdout ----
current_directory_resolved:
thread 'test_pr::test_with_column_across_option' panicked at 'called `Result::unwrap()` on an `Err` value: IndeterminateOffset', tests/by-util/test_pr.rs:21:62

---- test_pr::test_with_column_across_option_and_column_separator stdout ----
current_directory_resolved:
thread 'test_pr::test_with_column_across_option_and_column_separator' panicked at 'called `Result::unwrap()` on an `Err` value: IndeterminateOffset', tests/by-util/test_pr.rs:21:62

---- test_pr::test_with_double_space_option stdout ----
current_directory_resolved:
thread 'test_pr::test_with_double_space_option' panicked at 'called `Result::unwrap()` on an `Err` value: IndeterminateOffset', tests/by-util/test_pr.rs:21:62

---- test_pr::test_with_mpr stdout ----
thread 'test_pr::test_with_mpr' panicked at 'called `Result::unwrap()` on an `Err` value: IndeterminateOffset', tests/by-util/test_pr.rs:324:45

---- test_pr::test_with_first_line_number_long_option stdout ----
current_directory_resolved:
thread 'test_pr::test_with_first_line_number_long_option' panicked at 'called `Result::unwrap()` on an `Err` value: IndeterminateOffset', tests/by-util/test_pr.rs:21:62

---- test_pr::test_with_long_header_option stdout ----
current_directory_resolved:
thread 'test_pr::test_with_long_header_option' panicked at 'called `Result::unwrap()` on an `Err` value: IndeterminateOffset', tests/by-util/test_pr.rs:21:62

---- test_pr::test_with_first_line_number_option stdout ----
current_directory_resolved:
thread 'test_pr::test_with_first_line_number_option' panicked at 'called `Result::unwrap()` on an `Err` value: IndeterminateOffset', tests/by-util/test_pr.rs:21:62

---- test_pr::test_with_no_header_trailer_option stdout ----
current_directory_resolved:
thread 'test_pr::test_with_no_header_trailer_option' panicked at 'called `Result::unwrap()` on an `Err` value: IndeterminateOffset', tests/by-util/test_pr.rs:21:62

---- test_pr::test_with_offset_space_option stdout ----
current_directory_resolved:
thread 'test_pr::test_with_offset_space_option' panicked at 'called `Result::unwrap()` on an `Err` value: IndeterminateOffset', tests/by-util/test_pr.rs:21:62

---- test_pr::test_with_number_option_with_custom_separator_char_and_width stdout ----
current_directory_resolved:
thread 'test_pr::test_with_number_option_with_custom_separator_char_and_width' panicked at 'called `Result::unwrap()` on an `Err` value: IndeterminateOffset', tests/by-util/test_pr.rs:21:62

---- test_pr::test_with_page_range stdout ----
current_directory_resolved:
thread 'test_pr::test_with_page_range' panicked at 'called `Result::unwrap()` on an `Err` value: IndeterminateOffset', tests/by-util/test_pr.rs:21:62

---- test_pr::test_with_numbering_option_with_number_width stdout ----
current_directory_resolved:
thread 'test_pr::test_with_numbering_option_with_number_width' panicked at 'called `Result::unwrap()` on an `Err` value: IndeterminateOffset', tests/by-util/test_pr.rs:21:62

---- test_pr::test_with_pr_core_utils_tests stdout ----
current_directory_resolved:
thread 'test_pr::test_with_pr_core_utils_tests' panicked at 'called `Result::unwrap()` on an `Err` value: IndeterminateOffset', tests/by-util/test_pr.rs:21:62

---- test_pr::test_with_join_lines_option stdout ----
current_directory_resolved:
thread 'test_pr::test_with_join_lines_option' panicked at 'called `Result::unwrap()` on an `Err` value: IndeterminateOffset', tests/by-util/test_pr.rs:450:45

---- test_pr::test_with_page_length_option stdout ----
current_directory_resolved:
thread 'test_pr::test_with_page_length_option' panicked at 'called `Result::unwrap()` on an `Err` value: IndeterminateOffset', tests/by-util/test_pr.rs:21:62

---- test_pr::test_with_number_option_with_custom_separator_char stdout ----
current_directory_resolved:
thread 'test_pr::test_with_number_option_with_custom_separator_char' panicked at 'called `Result::unwrap()` on an `Err` value: IndeterminateOffset', tests/by-util/test_pr.rs:21:62

---- test_pr::test_with_stdin stdout ----
current_directory_resolved:
thread 'test_pr::test_with_stdin' panicked at 'called `Result::unwrap()` on an `Err` value: IndeterminateOffset', tests/by-util/test_pr.rs:261:45

---- test_pr::test_without_any_options stdout ----
current_directory_resolved:
thread 'test_pr::test_without_any_options' panicked at 'called `Result::unwrap()` on an `Err` value: IndeterminateOffset', tests/by-util/test_pr.rs:21:62

---- test_touch::test_touch_mtime_dst_fails stdout ----
current_directory_resolved:
thread 'test_touch::test_touch_mtime_dst_fails' panicked at 'Error The system's UTC offset could not be determined retrieving the OffsetDateTime::now_local', tests/by-util/test_touch.rs:657:13

---- test_touch::test_touch_leap_second stdout ----
current_directory_resolved:
run: /build/uutils-coreutils/src/coreutils-0.0.17/target/release/coreutils touch -t<PHONE_NUMBER>00.60 test_touch_leap_sec
thread 'test_touch::test_touch_leap_second' panicked at 'Error The system's UTC offset could not be determined retrieving the OffsetDateTime::now_local', tests/by-util/test_touch.rs:55:13

---- test_touch::test_touch_no_dereference stdout ----
current_directory_resolved:
thread 'test_touch::test_touch_no_dereference' panicked at 'Error The system's UTC offset could not be determined retrieving the OffsetDateTime::now_local', tests/by-util/test_touch.rs:55:13

---- test_touch::test_touch_mtime_dst_succeeds stdout ----
current_directory_resolved:
run: /build/uutils-coreutils/src/coreutils-0.0.17/target/release/coreutils touch -m -t<PHONE_NUMBER>00 test_touch_set_mtime_dst_succeeds
thread 'test_touch::test_touch_mtime_dst_succeeds' panicked at 'Error The system's UTC offset could not be determined retrieving the OffsetDateTime::now_local', tests/by-util/test_touch.rs:55:13

---- test_touch::test_touch_reference stdout ----
current_directory_resolved:
thread 'test_touch::test_touch_reference' panicked at 'Error The system's UTC offset could not be determined retrieving the OffsetDateTime::now_local', tests/by-util/test_touch.rs:55:13

---- test_touch::test_touch_set_both_date_and_reference stdout ----
current_directory_resolved:
thread 'test_touch::test_touch_set_both_date_and_reference' panicked at 'Error The system's UTC offset could not be determined retrieving the OffsetDateTime::now_local', tests/by-util/test_touch.rs:55:13

---- test_touch::test_touch_set_both_time_and_reference stdout ----
current_directory_resolved:
thread 'test_touch::test_touch_set_both_time_and_reference' panicked at 'Error The system's UTC offset could not be determined retrieving the OffsetDateTime::now_local', tests/by-util/test_touch.rs:55:13

---- test_touch::test_touch_set_both stdout ----
current_directory_resolved:
run: /build/uutils-coreutils/src/coreutils-0.0.17/target/release/coreutils touch -t<PHONE_NUMBER>34 -a -m test_touch_set_both
thread 'test_touch::test_touch_set_both' panicked at 'Error The system's UTC offset could not be determined retrieving the OffsetDateTime::now_local', tests/by-util/test_touch.rs:55:13

---- test_touch::test_touch_set_cymdhm_time stdout ----
current_directory_resolved:
run: /build/uutils-coreutils/src/coreutils-0.0.17/target/release/coreutils touch -t<PHONE_NUMBER>34 test_touch_set_cymdhm_time
thread 'test_touch::test_touch_set_cymdhm_time' panicked at 'Error The system's UTC offset could not be determined retrieving the OffsetDateTime::now_local', tests/by-util/test_touch.rs:55:13

---- test_touch::test_touch_set_date stdout ----
current_directory_resolved:
run: /build/uutils-coreutils/src/coreutils-0.0.17/target/release/coreutils touch -d Thu Jan 01 12:34:00 2015 test_touch_set_date
thread 'test_touch::test_touch_set_date' panicked at 'Error The system's UTC offset could not be determined retrieving the OffsetDateTime::now_local', tests/by-util/test_touch.rs:55:13

---- test_touch::test_touch_set_date2 stdout ----
current_directory_resolved:
run: /build/uutils-coreutils/src/coreutils-0.0.17/target/release/coreutils touch -d 2000-01-23 test_touch_set_date
thread 'test_touch::test_touch_set_date2' panicked at 'Error The system's UTC offset could not be determined retrieving the OffsetDateTime::now_local', tests/by-util/test_touch.rs:55:13

---- test_touch::test_touch_set_cymdhms_time stdout ----
current_directory_resolved:
run: /build/uutils-coreutils/src/coreutils-0.0.17/target/release/coreutils touch -t<PHONE_NUMBER>34.56 test_touch_set_cymdhms_time
thread 'test_touch::test_touch_set_cymdhms_time' panicked at 'Error The system's UTC offset could not be determined retrieving the OffsetDateTime::now_local', tests/by-util/test_touch.rs:55:13

---- test_touch::test_touch_set_mdhms_time stdout ----
current_directory_resolved:
run: /build/uutils-coreutils/src/coreutils-0.0.17/target/release/coreutils touch -t 01011234.56 test_touch_set_mdhms_time
thread 'test_touch::test_touch_set_mdhms_time' panicked at 'Error The system's UTC offset could not be determined retrieving the OffsetDateTime::now_local', tests/by-util/test_touch.rs:55:13

---- test_touch::test_touch_set_mdhm_time stdout ----
current_directory_resolved:
run: /build/uutils-coreutils/src/coreutils-0.0.17/target/release/coreutils touch -t 01011234 test_touch_set_mdhm_time
thread 'test_touch::test_touch_set_mdhm_time' panicked at 'called `Result::unwrap()` on an `Err` value: IndeterminateOffset', tests/by-util/test_touch.rs:113:47

---- test_touch::test_touch_set_only_atime stdout ----
current_directory_resolved:
run: /build/uutils-coreutils/src/coreutils-0.0.17/target/release/coreutils touch -t<PHONE_NUMBER>34 -a test_touch_set_only_atime
thread 'test_touch::test_touch_set_only_atime' panicked at 'Error The system's UTC offset could not be determined retrieving the OffsetDateTime::now_local', tests/by-util/test_touch.rs:55:13

---- test_touch::test_touch_set_only_mtime stdout ----
current_directory_resolved:
run: /build/uutils-coreutils/src/coreutils-0.0.17/target/release/coreutils touch -t<PHONE_NUMBER>34 -m test_touch_set_only_mtime
thread 'test_touch::test_touch_set_only_mtime' panicked at 'Error The system's UTC offset could not be determined retrieving the OffsetDateTime::now_local', tests/by-util/test_touch.rs:55:13

---- test_touch::test_touch_set_ymdhm_time stdout ----
current_directory_resolved:
run: /build/uutils-coreutils/src/coreutils-0.0.17/target/release/coreutils touch -t<PHONE_NUMBER> test_touch_set_ymdhm_time
thread 'test_touch::test_touch_set_ymdhm_time' panicked at 'Error The system's UTC offset could not be determined retrieving the OffsetDateTime::now_local', tests/by-util/test_touch.rs:55:13

---- test_touch::test_touch_set_ymdhms_time stdout ----
current_directory_resolved:
run: /build/uutils-coreutils/src/coreutils-0.0.17/target/release/coreutils touch -t<PHONE_NUMBER>.56 test_touch_set_ymdhms_time
thread 'test_touch::test_touch_set_ymdhms_time' panicked at 'Error The system's UTC offset could not be determined retrieving the OffsetDateTime::now_local', tests/by-util/test_touch.rs:55:13

failures:
    test_cp::test_cp_archive
    test_cp::test_cp_no_preserve_timestamps
    test_cp::test_cp_preserve_timestamps
    test_mv::test_mv_update_option
    test_pr::test_with_column
    test_pr::test_with_column_across_option
    test_pr::test_with_column_across_option_and_column_separator
    test_pr::test_with_double_space_option
    test_pr::test_with_first_line_number_long_option
    test_pr::test_with_first_line_number_option
    test_pr::test_with_join_lines_option
    test_pr::test_with_long_header_option
    test_pr::test_with_mpr
    test_pr::test_with_no_header_trailer_option
    test_pr::test_with_number_option_with_custom_separator_char
    test_pr::test_with_number_option_with_custom_separator_char_and_width
    test_pr::test_with_numbering_option_with_number_width
    test_pr::test_with_offset_space_option
    test_pr::test_with_page_length_option
    test_pr::test_with_page_range
    test_pr::test_with_pr_core_utils_tests
    test_pr::test_with_stdin
    test_pr::test_without_any_options
    test_touch::test_touch_leap_second
    test_touch::test_touch_mtime_dst_fails
    test_touch::test_touch_mtime_dst_succeeds
    test_touch::test_touch_no_dereference
    test_touch::test_touch_reference
    test_touch::test_touch_set_both
    test_touch::test_touch_set_both_date_and_reference
    test_touch::test_touch_set_both_time_and_reference
    test_touch::test_touch_set_cymdhm_time
    test_touch::test_touch_set_cymdhms_time
    test_touch::test_touch_set_date
    test_touch::test_touch_set_date2
    test_touch::test_touch_set_mdhm_time
    test_touch::test_touch_set_mdhms_time
    test_touch::test_touch_set_only_atime
    test_touch::test_touch_set_only_mtime
    test_touch::test_touch_set_ymdhm_time
    test_touch::test_touch_set_ymdhms_time

test result: FAILED. 1979 passed; 41 failed; 33 ignored; 0 measured; 3 filtered out; finished in 12.47s

Currently, I'm setting RUSTFLAGS="--cfg unsound_local_offset" as a workaround but it's suboptimal. Is there a suggested way to run the tests while avoiding UTC offset errors?

Interesting. It's probably related to this: https://github.com/time-rs/time/issues/538
You might be able to work around this by downgrading the time crate in the meantime.

We've seen things before where the local offset failed in the CI. That might have been caused by the unsoundness maybe. I wonder how we could fix this, because I really don't want to serialize all the tests. I guess we could always run the tests with the unsound_local_offset flag, but that's not great either.

Already the case:
https://github.com/uutils/coreutils/blob/ab736926baad88828f30a2ac6804cd2fe430b2bc/.cargo/config#L13-L20

As far as I understand, there isn't a way to fix this other than setting the unsound_local_offset flag for now. Is that correct?

AFAIK, for now :)


Build state to image from?

Hi I was wondering if these workstations should theoretically be possible to image and redeploy? I love building initial infrastructure with this, but ideally our team would deploy new workstations to ec2 from image via lambda/boto.
Currently, without any modifications after the terraform build, if I make an AMI from it, boot it into the same subnet-ws, and add it to CAM, when I go to connect in PCoiP client it only ever says "restarting remote workstation" and didnt does anything in EC2. Is there a guide for this? Our team had deployed a PCoIP solution earlier that imaged fine but was pointing to aws-marketplace-subscription— was hoping to emulate the same with CAM.
Thank you for any info, I really have appreciated your past help

Hi infintropy,
Thanks for using our scripts again.  These scripts are great for initial green field deployments and also to show you how it's done (by inspecting the terraform code and startup scripts).  The best way to expand number of workstations on top of the initially deployed ones are:

Go into the terraform.tfvars and increase the number of workstations you want (e.g. win_gfx_instance_count), then run terraform apply again.
Go to CAM at cam.teradici.com, under Workstations, click on the + sign and "Create new remote workstation".  If you want to deploy using code, you can also consider using CAM APIs, documented here: https://cam.teradici.com/api/docs.

Making AMIs out of deployed workstations is not going to work, because those workstations are already domain-joined and have their PCoIP agent registered with a PCoIP Registration Code.  What you could do to create an AMI is look at our provisioning scripts to understand what they do. Then:

Create a VM manually
Manually or through a user-data script, do the same setup as our provisioning.sh.tmpl file for that type of workstation, EXCEPT do NOT actually join the domain and install but do NOT register the PCoIP Agent.
Install any additional software / applications you want to be in the image.
If it is a windows instance, run sysprep to prepare it for snapshot.  Not sure if there is a CentOS equivalent.
Create an image/AMI from the instance
for new VMs created using the image, you will have to manually / have startup scripts to join the domain with the Domain Controller and register the PCoIP Agent with registration code.

May I ask which organization this is for?
Hope that helps.

Very sorry for not responding sooner.
This is for Nexodus vfx workstations. This helps tremendously!


[Feature] Block heartbeat coroutine & pending transaction

Component
providers, rpc-client
Describe the feature you would like
A task that subscribes to block headers, and allows watching blocks for confirmed transactions, and notifying subscribers
Task should

contains a subscription to block headers
contain a tx_hash_receiver: tokio::sync::mpsc::Receiver<(B256, broadcast::Sender<()>)>
contain a tx_senders: HashMap<B256, tokio::sync::broadcast::Sender<()>>
retrieve each block as the header notification occurs
detect missing block header notifications and retrieve those blocks as well
iterate over all txn hashes in the block
dispatch a notification to the appropriate channel, if necessary.

maybe feature

store txns and rebroadcast them every N seconds?

Pending Transaction

contains an RpcClient ref
thin wrapper around tokio::sync::broadcast::Receiver
on receipt of notification, retrieves the receipt via eth_getTransactionReceipt
impl Future { type Output = RpcResult<Receipt>; }

Modify RpcClient

hold a tokio::sync::mpsc called tx_hash_sender which communicates tx hashes to watch for to the co-routine

Provider method

modify send_transaction and send_raw_transaction to send hashes via the tx_hash_sender AFTER broadcast

Additional context

done in https://github.com/alloy-rs/alloy/pull/179 I think


Fix labels on links in advertisement models ( too much information)

Remove long unreadable labels from links in derived topology ad models

Fixed in #72 by not printing the label in the vis.


Design Documentation

We should come up with some kind of technical documentation describing the structure of our mvc application.

Ongoing, to be continued in each sprint.


New version: Oracle.JDK.17 version 17.0.8

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?

[x] Does your manifest conform to the 1.4 schema?

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

Microsoft Reviewers: codeflow:open?pullrequest=https://github.com/microsoft/winget-pkgs/pull/112813&drop=dogfoodAlpha

@jacobgelling Please mark the above conversations as "resolved" for auto-merge process to merge this PR after the pipeline checks pass

@jacobgelling Please mark the above conversations as "resolved" for auto-merge process to merge this PR after the pipeline checks pass

cc @jacobgelling


Clean up connections after websocket close

Title:
Clean up connections after WebSocket close
Description:
Make sure we clean up connections by just going through the map and
cleaning all the verkeys that match the connection. This is a suboptimal
solution, but a connection close is not something happening often.
Fixes https://github.com/hyperledger/aries-framework-go/issues/3349

If you like the approach, or if it's acceptable, then I can try to add tests.

linting with js/wasm..
Error: pkg/didcomm/transport/ws/pool.go:74:20: func `(*connPool).remove` is unused (unused)
func (d *connPool) remove(verKey string) {
                   ^
make: *** [lint] Error 1
Makefile:37: recipe for target 'lint' failed
Error: Process completed with exit code 2.

The unused check is incorrect (or possibly incomplete as it doesn't take the regular server into account), it's used here https://github.com/hyperledger/aries-framework-go/blob/b1decdfed852057fe64660b40ac705953b4d6d0f/pkg/didcomm/transport/ws/upgrade_srv.go#L28-L35


Fix type checking for the error reason specified in the error constructor

Purpose
Fix type checking for the error reason specified in the error constructor.
Fixes https://github.com/ballerina-platform/ballerina-lang/issues/13654
Automation tests

Unit tests
Added.

Codecov Report

Merging #13660 into master will increase coverage by 0.03%.
The diff coverage is 75%.

@@             Coverage Diff              @@
##             master   #13660      +/-   ##
============================================
+ Coverage     65.02%   65.06%   +0.03%
  Complexity      426      426
============================================
  Files          2116     2116
  Lines         93575    93587      +12
  Branches      12352    12353       +1
============================================
+ Hits          60851    60896      +45
+ Misses        27809    27779      -30
+ Partials       4915     4912       -3

Impacted Files
Coverage Δ
Complexity Δ

...alang/compiler/semantics/analyzer/TypeChecker.java
86.08% <100%> (ø)
0 <0> (ø)
:arrow_down:

...g/wso2/ballerinalang/compiler/desugar/Desugar.java
91.98% <66.66%> (-0.04%)
0 <0> (ø)

...org/ballerinalang/bre/bvm/WaitCallbackHandler.java
81.08% <0%> (-1.81%)
0% <0%> (ø)

...llerinalang/stdlib/socket/tcp/SelectorManager.java
70.08% <0%> (-1.71%)
0% <0%> (ø)

...java/org/ballerinalang/bre/bvm/BLangVMStructs.java
50% <0%> (-1.67%)
0% <0%> (ø)

...a/org/ballerinalang/bre/bvm/GlobalMemoryBlock.java
78.43% <0%> (-0.99%)
0% <0%> (ø)

...rg/ballerinalang/database/sql/SQLDataIterator.java
63.43% <0%> (-0.72%)
0% <0%> (ø)

.../ballerinalang/util/codegen/PackageInfoReader.java
91.35% <0%> (+0.09%)
0% <0%> (ø)
:arrow_down:

...llerinalang/compiler/semantics/analyzer/Types.java
73.24% <0%> (+0.1%)
0% <0%> (ø)
:arrow_down:

...ng/compiler/semantics/analyzer/SymbolResolver.java
85.05% <0%> (+0.19%)
0% <0%> (ø)
:arrow_down:

... and 4 more

Continue to review full report at Codecov.

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


Shields' trims don't show up in third person

although I can see the trim in the first person, it isn't here in third person, even if it is a vanilla trim and vanilla material

here is my modlist

Strange, I'll take a look at this, it's definitely an incompatibility though.


[SP-5809] Backport of PDI-18792 - Performance of the "Write to log" step when the "Print headers" checkbox is activated 5x slower since 5.4 release (8.3 Suite)

Original PRs:

https://github.com/pentaho/pentaho-kettle/pull/7667 (3 commits)
https://github.com/pentaho/pentaho-kettle/pull/7719 (2 commits)

Please merge commit!
@pentaho-lmartins @ssamora @bcostahitachivantara

:warning: Build finished in 32m 48s
Build command:
mvn clean verify -B -e -Daudit -amd -pl engine,ui

:no_entry: Failed Tests
:cloud_with_lightning_and_rain: 2 test(s) failed:
org.pentaho.di.trans.SubtransExecutorTest.testRunsATrans (click to expand)

Argument(s) are different! Wanted:
logChannel.logBasic(
    "
------------> Linenr 1------------------------------
name = Pentaho
sum = 10

===================="
);
-> at org.pentaho.di.trans.SubtransExecutorTest.testRunsATrans(SubtransExecutorTest.java:125)
Actual invocation has different arguments:
logChannel.logBasic(
    "Finished processing (I=0, O=0, R=4, W=4, U=0, E=0)"
);
-> at org.pentaho.di.trans.step.RunThread.run(RunThread.java:108)

org.pentaho.di.trans.step.jms.context.ActiveMQProviderTest.testFullCircle (click to expand)
${result.errorDetails}

Tests run: 3634, Failures: 2, Skipped: 7    Test Results

:information_source:  This is an automatic message

:warning: Build finished in 37m 13s
Build command:
mvn clean verify -B -e -Daudit -amd

:no_entry: Failed Tests
:cloud_with_lightning_and_rain: 2 test(s) failed:
org.pentaho.di.trans.SubtransExecutorTest.testRunsATrans (click to expand)

Argument(s) are different! Wanted:
logChannel.logBasic(
    "
------------> Linenr 1------------------------------
name = Pentaho
sum = 10

===================="
);
-> at org.pentaho.di.trans.SubtransExecutorTest.testRunsATrans(SubtransExecutorTest.java:125)
Actual invocation has different arguments:
logChannel.logBasic(
    "Finished processing (I=0, O=0, R=4, W=4, U=0, E=0)"
);
-> at org.pentaho.di.trans.step.RunThread.run(RunThread.java:108)

org.pentaho.di.trans.step.jms.context.ActiveMQProviderTest.testFullCircle (click to expand)
${result.errorDetails}

Tests run: 4797, Failures: 2, Skipped: 7    Test Results

:information_source:  This is an automatic message

:white_check_mark: Build finished in 31m 5s
Build command:
mvn clean verify -B -e -Daudit -amd -pl \
engine,plugins/streaming/impls/jms,ui

:ok_hand: All tests passed!
Tests run: 3634, Failures: 0, Skipped: 7    Test Results

:information_source:  This is an automatic message


What does this have to do with WASM?

What is the actual goal of this crate.
What do they have to do with each other?

Ah I think the actual goal was to check whether performing minimization using rust to wasm was faster than the same implementation using JS alone when doing the stuff in the browser locally. Probably should hide that stuff behind a feature flag


Space bar not being input

PS we should get a Matrix channel together for this for easy discussion of topics.
Expected behavior
Space bar input in test when qt_send_key "space" is used
Actual behavior
No matter how many qt_send_key "space" I enter it doesn't appear to toggle the radio button I'm on top of. I even tested in quickemu to ensure it will accept a space input
Steps to reproduce the behavior
Use qt_send_key "space" on an installer to try a full install test. Note: Installer is calamares and does support this.
Additional context
Quicktest output
System Information
----------------------------------
        Quickemu 4.9.6
----------------------------------
Distro: Solus 4.5 Resilience
Kernel: Linux 6.10.9-302.current x86_64
Memory: 31G
GPU:
 - Advanced Micro Devices, Inc. [AMD/ATI] Renoir [Radeon Vega Series / Radeon Vega Mobile Series] (rev d1)
----------------------------------
            curl 8.10.0
----------------------------------
Libraries: libcurl/8.10.0 OpenSSL/3.3.2 zlib/1.3.1.zlib-ng brotli/1.1.0 zstd/1.5.6 libidn2/2.3.7 libssh2/1.11.0 nghttp2/1.63.0 nghttp3/1.5.0
Protocols: dict file ftp ftps gopher gophers http https imap imaps ipfs ipns mqtt pop3 pop3s rtsp scp sftp smb smbs smtp smtps telnet tftp
Features:  alt-svc AsynchDNS brotli GSS-API HSTS HTTP2 HTTP3 HTTPS-proxy IDN IPv6 Kerberos Largefile libz NTLM SPNEGO SSL threadsafe TLS-SRP UnixSockets zstd
----------------------------------
            QEMU 9.1.0
----------------------------------
Available CPUs:
  486                   (alias configured by machine type)
  486-v1
  Broadwell             (alias configured by machine type)
  Broadwell-IBRS        (alias of Broadwell-v3)
  Broadwell-noTSX       (alias of Broadwell-v2)
  Broadwell-noTSX-IBRS  (alias of Broadwell-v4)
  Broadwell-v1          Intel Core Processor (Broadwell)
  Broadwell-v2          Intel Core Processor (Broadwell, no TSX)
  Broadwell-v3          Intel Core Processor (Broadwell, IBRS)
  Broadwell-v4          Intel Core Processor (Broadwell, no TSX, IBRS)
  Cascadelake-Server    (alias configured by machine type)
  Cascadelake-Server-noTSX  (alias of Cascadelake-Server-v3)
  Cascadelake-Server-v1  Intel Xeon Processor (Cascadelake)
  Cascadelake-Server-v2  Intel Xeon Processor (Cascadelake) [ARCH_CAPABILITIES]
  Cascadelake-Server-v3  Intel Xeon Processor (Cascadelake) [ARCH_CAPABILITIES, no TSX]
  Cascadelake-Server-v4  Intel Xeon Processor (Cascadelake) [ARCH_CAPABILITIES, no TSX]
  Cascadelake-Server-v5  Intel Xeon Processor (Cascadelake) [ARCH_CAPABILITIES, EPT switching, XSAVES, no TSX]
  Conroe                (alias configured by machine type)
  Conroe-v1             Intel Celeron_4x0 (Conroe/Merom Class Core 2)
  Cooperlake            (alias configured by machine type)
  Cooperlake-v1         Intel Xeon Processor (Cooperlake)
  Cooperlake-v2         Intel Xeon Processor (Cooperlake) [XSAVES]
  Denverton             (alias configured by machine type)
  Denverton-v1          Intel Atom Processor (Denverton)
  Denverton-v2          Intel Atom Processor (Denverton) [no MPX, no MONITOR]
  Denverton-v3          Intel Atom Processor (Denverton) [XSAVES, no MPX, no MONITOR]
  Dhyana                (alias configured by machine type)
  Dhyana-v1             Hygon Dhyana Processor
  Dhyana-v2             Hygon Dhyana Processor [XSAVES]
  EPYC                  (alias configured by machine type)
  EPYC-Genoa            (alias configured by machine type)
  EPYC-Genoa-v1         AMD EPYC-Genoa Processor
  EPYC-IBPB             (alias of EPYC-v2)
  EPYC-Milan            (alias configured by machine type)
  EPYC-Milan-v1         AMD EPYC-Milan Processor
  EPYC-Milan-v2         AMD EPYC-Milan-v2 Processor
  EPYC-Rome             (alias configured by machine type)
  EPYC-Rome-v1          AMD EPYC-Rome Processor
  EPYC-Rome-v2          AMD EPYC-Rome Processor
  EPYC-Rome-v3          AMD EPYC-Rome-v3 Processor
  EPYC-Rome-v4          AMD EPYC-Rome-v4 Processor (no XSAVES)
  EPYC-v1               AMD EPYC Processor
  EPYC-v2               AMD EPYC Processor (with IBPB)
  EPYC-v3               AMD EPYC Processor
  EPYC-v4               AMD EPYC-v4 Processor
  GraniteRapids         (alias configured by machine type)
  GraniteRapids-v1      Intel Xeon Processor (GraniteRapids)
  Haswell               (alias configured by machine type)
  Haswell-IBRS          (alias of Haswell-v3)
  Haswell-noTSX         (alias of Haswell-v2)
  Haswell-noTSX-IBRS    (alias of Haswell-v4)
  Haswell-v1            Intel Core Processor (Haswell)
  Haswell-v2            Intel Core Processor (Haswell, no TSX)
  Haswell-v3            Intel Core Processor (Haswell, IBRS)
  Haswell-v4            Intel Core Processor (Haswell, no TSX, IBRS)
  Icelake-Server        (alias configured by machine type)
  Icelake-Server-noTSX  (alias of Icelake-Server-v2)
  Icelake-Server-v1     Intel Xeon Processor (Icelake)
  Icelake-Server-v2     Intel Xeon Processor (Icelake) [no TSX]
  Icelake-Server-v3     Intel Xeon Processor (Icelake)
  Icelake-Server-v4     Intel Xeon Processor (Icelake)
  Icelake-Server-v5     Intel Xeon Processor (Icelake) [XSAVES]
  Icelake-Server-v6     Intel Xeon Processor (Icelake) [5-level EPT]
  Icelake-Server-v7     Intel Xeon Processor (Icelake) [TSX, taa-no]
  IvyBridge             (alias configured by machine type)
  IvyBridge-IBRS        (alias of IvyBridge-v2)
  IvyBridge-v1          Intel Xeon E3-12xx v2 (Ivy Bridge)
  IvyBridge-v2          Intel Xeon E3-12xx v2 (Ivy Bridge, IBRS)
  KnightsMill           (alias configured by machine type)
  KnightsMill-v1        Intel Xeon Phi Processor (Knights Mill)
  Nehalem               (alias configured by machine type)
  Nehalem-IBRS          (alias of Nehalem-v2)
  Nehalem-v1            Intel Core i7 9xx (Nehalem Class Core i7)
  Nehalem-v2            Intel Core i7 9xx (Nehalem Core i7, IBRS update)
  Opteron_G1            (alias configured by machine type)
  Opteron_G1-v1         AMD Opteron 240 (Gen 1 Class Opteron)
  Opteron_G2            (alias configured by machine type)
  Opteron_G2-v1         AMD Opteron 22xx (Gen 2 Class Opteron)
  Opteron_G3            (alias configured by machine type)
  Opteron_G3-v1         AMD Opteron 23xx (Gen 3 Class Opteron)
  Opteron_G4            (alias configured by machine type)
  Opteron_G4-v1         AMD Opteron 62xx class CPU
  Opteron_G5            (alias configured by machine type)
  Opteron_G5-v1         AMD Opteron 63xx class CPU
  Penryn                (alias configured by machine type)
  Penryn-v1             Intel Core 2 Duo P9xxx (Penryn Class Core 2)
  SandyBridge           (alias configured by machine type)
  SandyBridge-IBRS      (alias of SandyBridge-v2)
  SandyBridge-v1        Intel Xeon E312xx (Sandy Bridge)
  SandyBridge-v2        Intel Xeon E312xx (Sandy Bridge, IBRS update)
  SapphireRapids        (alias configured by machine type)
  SapphireRapids-v1     Intel Xeon Processor (SapphireRapids)
  SapphireRapids-v2     Intel Xeon Processor (SapphireRapids)
  SapphireRapids-v3     Intel Xeon Processor (SapphireRapids)
  SierraForest          (alias configured by machine type)
  SierraForest-v1       Intel Xeon Processor (SierraForest)
  Skylake-Client        (alias configured by machine type)
  Skylake-Client-IBRS   (alias of Skylake-Client-v2)
  Skylake-Client-noTSX-IBRS  (alias of Skylake-Client-v3)
  Skylake-Client-v1     Intel Core Processor (Skylake)
  Skylake-Client-v2     Intel Core Processor (Skylake, IBRS)
  Skylake-Client-v3     Intel Core Processor (Skylake, IBRS, no TSX)
  Skylake-Client-v4     Intel Core Processor (Skylake, IBRS, no TSX) [IBRS, XSAVES, no TSX]
  Skylake-Server        (alias configured by machine type)
  Skylake-Server-IBRS   (alias of Skylake-Server-v2)
  Skylake-Server-noTSX-IBRS  (alias of Skylake-Server-v3)
  Skylake-Server-v1     Intel Xeon Processor (Skylake)
  Skylake-Server-v2     Intel Xeon Processor (Skylake, IBRS)
  Skylake-Server-v3     Intel Xeon Processor (Skylake, IBRS, no TSX)
  Skylake-Server-v4     Intel Xeon Processor (Skylake, IBRS, no TSX)
  Skylake-Server-v5     Intel Xeon Processor (Skylake, IBRS, no TSX) [IBRS, XSAVES, EPT switching, no TSX]
  Snowridge             (alias configured by machine type)
  Snowridge-v1          Intel Atom Processor (SnowRidge)
  Snowridge-v2          Intel Atom Processor (Snowridge, no MPX)
  Snowridge-v3          Intel Atom Processor (Snowridge, no MPX) [XSAVES, no MPX]
  Snowridge-v4          Intel Atom Processor (Snowridge, no MPX) [no split lock detect, no core-capability]
  Westmere              (alias configured by machine type)
  Westmere-IBRS         (alias of Westmere-v2)
  Westmere-v1           Westmere E56xx/L56xx/X56xx (Nehalem-C)
  Westmere-v2           Westmere E56xx/L56xx/X56xx (IBRS update)
  athlon                (alias configured by machine type)
  athlon-v1             QEMU Virtual CPU version 2.5+
  core2duo              (alias configured by machine type)
  core2duo-v1           Intel(R) Core(TM)2 Duo CPU     T7700  @ 2.40GHz
  coreduo               (alias configured by machine type)
  coreduo-v1            Genuine Intel(R) CPU           T2600  @ 2.16GHz
  kvm32                 (alias configured by machine type)
  kvm32-v1              Common 32-bit KVM processor
  kvm64                 (alias configured by machine type)
  kvm64-v1              Common KVM processor
  n270                  (alias configured by machine type)
  n270-v1               Intel(R) Atom(TM) CPU N270   @ 1.60GHz
  pentium               (alias configured by machine type)
  pentium-v1
  pentium2              (alias configured by machine type)
  pentium2-v1
  pentium3              (alias configured by machine type)
  pentium3-v1
  phenom                (alias configured by machine type)
  phenom-v1             AMD Phenom(tm) 9550 Quad-Core Processor
  qemu32                (alias configured by machine type)
  qemu32-v1             QEMU Virtual CPU version 2.5+
  qemu64                (alias configured by machine type)
  qemu64-v1             QEMU Virtual CPU version 2.5+
  base                  base CPU model type with no features enabled
  host                  processor with all supported host features
  max                   Enables all features supported by the accelerator in the current host

Recognized CPUID flags:
  3dnow 3dnowext 3dnowprefetch abm ace2 ace2-en acpi adx aes amd-no-ssb
  amd-psfd amd-ssbd amd-stibp amx-bf16 amx-complex amx-fp16 amx-int8
  amx-tile apic arat arch-capabilities arch-lbr auto-ibrs avic avx avx-ifma
  avx-ne-convert avx-vnni avx-vnni-int16 avx-vnni-int8 avx2 avx512-4fmaps
  avx512-4vnniw avx512-bf16 avx512-fp16 avx512-vp2intersect
  avx512-vpopcntdq avx512bitalg avx512bw avx512cd avx512dq avx512er avx512f
  avx512ifma avx512pf avx512vbmi avx512vbmi2 avx512vl avx512vnni bmi1 bmi2
  bus-lock-detect cid cldemote clflush clflushopt clwb clzero cmov
  cmp-legacy cmpccxadd core-capability cr8legacy cx16 cx8 dca de
  decodeassists ds ds-cpl dtes64 erms est extapic f16c fb-clear fbsdp-no
  flush-l1d flushbyasid fma fma4 fpu fred fsgsbase fsrc fsrm fsrs
  full-width-write fxsr fxsr-opt fzrm gds-no gfni hle ht hypervisor ia64
  ibpb ibrs ibrs-all ibs intel-pt intel-pt-lip invpcid invtsc kvm-asyncpf
  kvm-asyncpf-int kvm-asyncpf-vmexit kvm-hint-dedicated kvm-mmu
  kvm-msi-ext-dest-id kvm-nopiodelay kvm-poll-control kvm-pv-eoi kvm-pv-ipi
  kvm-pv-sched-yield kvm-pv-tlb-flush kvm-pv-unhalt kvm-steal-time kvmclock
  kvmclock kvmclock-stable-bit la57 lahf-lm lam lbrv
  lfence-always-serializing lkgs lm lwp mca mcdt-no mce md-clear mds-no
  misalignsse mmx mmxext monitor movbe movdir64b movdiri mpx msr mtrr
  no-nested-data-bp nodeid-msr npt nrip-save null-sel-clr-base nx osvw
  overflow-recov pae pat pause-filter pbe pbrsb-no pcid pclmulqdq pcommit
  pdcm pdpe1gb perfctr-core perfctr-nb pfthreshold pge phe phe-en pks pku
  pmm pmm-en pn pni popcnt prefetchiti pschange-mc-no psdp-no pse pse36
  rdctl-no rdpid rdrand rdseed rdtscp rfds-clear rfds-no rsba rtm
  sbdr-ssdp-no sep serialize sgx sgx-aex-notify sgx-debug sgx-edeccssa
  sgx-exinfo sgx-kss sgx-mode64 sgx-provisionkey sgx-tokenkey sgx1 sgx2
  sgxlc sha-ni skinit skip-l1dfl-vmentry smap smep smx spec-ctrl
  split-lock-detect ss ssb-no ssbd sse sse2 sse4.1 sse4.2 sse4a ssse3 stibp
  stibp-always-on succor svm svm-lock svme-addr-chk syscall taa-no tbm tce
  tm tm2 topoext tsc tsc-adjust tsc-deadline tsc-scale tsx-ctrl tsx-ldtrk
  umip v-vmsave-vmload vaes vgif virt-ssbd vmcb-clean vme vmx
  vmx-activity-hlt vmx-activity-shutdown vmx-activity-wait-sipi
  vmx-any-errcode vmx-apicv-register vmx-apicv-vid vmx-apicv-x2apic
  vmx-apicv-xapic vmx-cr3-load-noexit vmx-cr3-store-noexit
  vmx-cr8-load-exit vmx-cr8-store-exit vmx-desc-exit
  vmx-enable-user-wait-pause vmx-encls-exit vmx-entry-ia32e-mode
  vmx-entry-load-bndcfgs vmx-entry-load-efer vmx-entry-load-pat
  vmx-entry-load-perf-global-ctrl vmx-entry-load-pkrs
  vmx-entry-load-rtit-ctl vmx-entry-noload-debugctl vmx-ept vmx-ept-1gb
  vmx-ept-2mb vmx-ept-advanced-exitinfo vmx-ept-execonly vmx-eptad
  vmx-eptp-switching vmx-exit-ack-intr vmx-exit-clear-bndcfgs
  vmx-exit-clear-rtit-ctl vmx-exit-load-efer vmx-exit-load-pat
  vmx-exit-load-perf-global-ctrl vmx-exit-load-pkrs
  vmx-exit-nosave-debugctl vmx-exit-save-efer vmx-exit-save-pat
  vmx-exit-save-preemption-timer vmx-flexpriority vmx-hlt-exit vmx-ins-outs
  vmx-intr-exit vmx-invept vmx-invept-all-context vmx-invept-single-context
  vmx-invept-single-context vmx-invept-single-context-noglobals
  vmx-invlpg-exit vmx-invpcid-exit vmx-invvpid vmx-invvpid-all-context
  vmx-invvpid-single-addr vmx-io-bitmap vmx-io-exit vmx-monitor-exit
  vmx-movdr-exit vmx-msr-bitmap vmx-mtf vmx-mwait-exit vmx-nested-exception
  vmx-nmi-exit vmx-page-walk-4 vmx-page-walk-5 vmx-pause-exit vmx-ple
  vmx-pml vmx-posted-intr vmx-preemption-timer vmx-rdpmc-exit
  vmx-rdrand-exit vmx-rdseed-exit vmx-rdtsc-exit vmx-rdtscp-exit
  vmx-secondary-ctls vmx-shadow-vmcs vmx-store-lma vmx-true-ctls
  vmx-tsc-offset vmx-tsc-scaling vmx-unrestricted-guest vmx-vintr-pending
  vmx-vmfunc vmx-vmwrite-vmexit-fields vmx-vnmi vmx-vnmi-pending vmx-vpid
  vmx-wbinvd-exit vmx-xsaves vmx-zero-len-inject vnmi vpclmulqdq waitpkg
  wbnoinvd wdt wrmsrns x2apic xcrypt xcrypt-en xfd xgetbv1 xop xsave xsavec
  xsaveerptr xsaveopt xsaves xstore xstore-en xtpr

----------------------------------
               CPU
----------------------------------
Architecture:                         x86_64
CPU op-mode(s):                       32-bit, 64-bit
Address sizes:                        48 bits physical, 48 bits virtual
Byte Order:                           Little Endian
CPU(s):                               16
On-line CPU(s) list:                  0-15
Vendor ID:                            AuthenticAMD
Model name:                           AMD Ryzen 7 PRO 4750U with Radeon Graphics
CPU family:                           23
Model:                                96
Thread(s) per core:                   2
Core(s) per socket:                   8
Socket(s):                            1
Stepping:                             1
Frequency boost:                      enabled
CPU(s) scaling MHz:                   94%
CPU max MHz:                          1700.0000
CPU min MHz:                          1400.0000
BogoMIPS:                             3393.38
Flags:                                fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl xtopology nonstop_tsc cpuid extd_apicid aperfmperf rapl pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt tce topoext perfctr_core perfctr_nb bpext perfctr_llc mwaitx cpb cat_l3 cdp_l3 hw_pstate ssbd mba ibrs ibpb stibp vmmcall fsgsbase bmi1 avx2 smep bmi2 cqm rdt_a rdseed adx smap clflushopt clwb sha_ni xsaveopt xsavec xgetbv1 cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local clzero irperf xsaveerptr rdpru wbnoinvd cppc arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif v_spec_ctrl umip rdpid overflow_recov succor smca
Virtualization:                       AMD-V
L1d cache:                            256 KiB (8 instances)
L1i cache:                            256 KiB (8 instances)
L2 cache:                             4 MiB (8 instances)
L3 cache:                             8 MiB (2 instances)
NUMA node(s):                         1
NUMA node0 CPU(s):                    0-15
Vulnerability Gather data sampling:   Not affected
Vulnerability Itlb multihit:          Not affected
Vulnerability L1tf:                   Not affected
Vulnerability Mds:                    Not affected
Vulnerability Meltdown:               Not affected
Vulnerability Mmio stale data:        Not affected
Vulnerability Reg file data sampling: Not affected
Vulnerability Retbleed:               Mitigation; untrained return thunk; SMT enabled with STIBP protection
Vulnerability Spec rstack overflow:   Mitigation; Safe RET
Vulnerability Spec store bypass:      Mitigation; Speculative Store Bypass disabled via prctl
Vulnerability Spectre v1:             Mitigation; usercopy/swapgs barriers and __user pointer sanitization
Vulnerability Spectre v2:             Mitigation; Retpolines; IBPB conditional; STIBP always-on; RSB filling; PBRSB-eIBRS Not affected; BHI Not affected
Vulnerability Srbds:                  Not affected
Vulnerability Tsx async abort:        Not affected

Spacebar is a literal   blank space. Just in case anyone is wondering. Like so:
qt_send_key " "


How to get the vm nic name,example eth0,or vm-nic-1 and so on

Describe the bug
I can not get the nic name
Reproduction steps
1. # Loop through all the VMs
    for child in children:
        # get all the vm name
        vmName = child.summary.config.name
        if vmName != "lanjing":
            continue
        for dev in child.config.hardware.device:
2.
3.
...

Expected behavior
Get the vm nic name
Additional context
No response

May be this line will help you to find an answer: https://github.com/vmware/pyvmomi-community-samples/pull/710/files#diff-b0253e78a2fcda842b484b0a78585928c1b7cdf3507871a87c4bfff6abc44823R76 ?


Fix new ArrayBuffer(length) for various input

Currently new ArrayBuffer(length) does not conform to ES2015.
For example, new ArrayBuffer(length) should not throw RangeError
for length = NaN, undefined, negative number, floating point, and so on.
JerryScript-DCO-1.0-Signed-off-by: Sanggyu Lee<EMAIL_ADDRESS>

@jiangzidong Could you review this patch?

@glistening I dont think ES2015 allow the length could be NaN, undefined, negative number, floating point.
http://www.ecma-international.org/ecma-262/6.0/#sec-arraybuffer-length see step 5
If SameValueZero(numberLength, byteLength) is false, throw a RangeError exception.

If the length is NaN, undefined, negative number, floating point. they will fail the samevaluezero check
But interesting part is V8 supports  NaN, undefined, negative number (-1, 0), floating point. I don't know why.
Correct me if I miss sth in the spec.

@jiangzidong Please see ToLength in step 3. Please see ToInteger also, which is called from ToLength. It specifies the handling of NaN, negative number, and so on. My tests check like Test262 testcases, and major JS runtime (node, jsc, ...) passes the tests.

@glistening Yes, I know that ToInteger will turn "negative number, NaN and floating number" into non-negative integer. But then it will fail the step5.
for example, var a = new ArrayBuffer(3.4);

Let numberLength be ToNumber(length).

the numberLength  is 3.4

Let byteLength be ToLength(numberLength).

the byteLength is 3

If SameValueZero(numberLength, byteLength) is false, throw a RangeError exception.

3 !== 3.4, so it will throw RangeError .
I don't know why test262/v8/spidermonkey don't follow it.

@jiangzidong Thank you for correcting me. The first sentence in this PR was wrong.
Test262 and major engines (v8, spidermonkey and JavaScriptCore) seems to follow ES2017, not ES2015. ES2017 uses ToIndex to describe the expected behaviour of ArrayBuffer(length). You can see it in test26 test case comment also.

esid: sec-arraybuffer-length
description: >
The length parameter is converted to a value numeric index value.
info: |
ArrayBuffer( length )

If NewTarget is undefined, throw a TypeError exception.
Let byteLength be ? ToIndex(length).
Return ? AllocateArrayBuffer(NewTarget, byteLength).

ToIndex( value )

If value is undefined, then
a. Let index be 0.
Else,
a. Let integerIndex be ? ToInteger(value).
b. If integerIndex < 0, throw a RangeError exception.
c. Let index be ! ToLength(integerIndex).
d. If SameValueZero(integerIndex, index) is false, throw a RangeError exception.
Return index.

I will raise this as Issue to get opinion.

@glistening Wow, I didn't notice that it's ES2017. Thanks for pointing out.

(I wouldn't create subsets for such differences, just use the latest standard)


Improve best/worst decile noise filtering

When considering best/worst decile measures for a practice, measures where a practice is in the 0th percentile persistently (with large denominator) are currently treated as noise and filtered out - e.g. ace.
The current noise-detection is completely wrong.
We should compile a list of practice-level measures which should not trigger alerts, and come up with a decent algorithm for detecting these.
Resolving this will probably resolve #451.

As an example, Vitamin B for that practice should arguably never trigger alerts, as the denominator is very low, leading to much jaggedness.


Add per-task cancellation?

I deliberately did not include a cancel scope with every ResultCapture object because cancel scopes are not free and, anyway, it goes against the spirit of the library: aioresult is intended for where you're happy with Trio's control flow, but just want to make a note of a return value. But I've realised it would be easy to add a cancel scope to a task by deriving a new class from ResultCapture, which would only be a few lines of code. It would even work with the start_soon() function because this is a class method.
Most importantly, it would be optional for callers, so it wouldn't burden those that don't need it, so I could be persuaded to add it to aioresult. Would it be of interest to anyone?
class CancellableCapture(ResultCapture):
    def __init__(self, routine, *args, suppress_exception: bool = False):
        super().__init__(routine, suppress_exception)
        self._cancel_scope = trio.CancelScope()

    async def run(self, **kwargs):
        with self._cancel_scope:
            await super().run(**kwargs)

    def cancel(self):
        self._cancel_scope.cancel()

    @property
    def cancel_scope(self):
        return self._cancel_scope

This does not attempt to deal with automatic cancellation where there are complex interdependencies between tasks (e.g. as discussed in python-trio/trio#892 and elsewhere) – that is definitely out of scope for this library. But at least it gives you a tool to help solve that manually at the application level.
One difficult aspect to the interface is what result() and exception() should return when a task has been cancelled. With the above implementation you would get the Cancelled exception (assuming that it successfully propagated all the way out of the routine).  This is a bit odd because the exception would not be propagated to the containing nursery. The caller could check whether the exception was due to their own cancellation by inspecting my_capture.cancel_scope.cancelled_caught.
(An earlier draft of this code also optionally allowed you to pass in an existing cancel scope to the constructor, perhaps so that you could use the same cancel scope in multiple tasks. But then I remembered that cancel scopes are not reusable in Trio: see python-trio/trio#886.)

I think it would be interesting. I suggested something similar in AnyIO, and Asphat v5.0 will have a TaskHandle that allows cancelling a single task.


Deprecation advice for navigationDestination(store:destination) on macOS

Description
This is about a SwiftUI bug that happens on macOS. I report it here because the deprecation advices to use this code.
In NavigationDestination.swift it says:
  @available(
    macOS, deprecated: 9999,
    message:
      "Pass a binding of a store to 'navigationDestination(item:)' instead. For more information, see the following article: https://pointfreeco.github.io/swift-composable-architecture/main/documentation/composablearchitecture/migratingto1.7#Replacing-navigation-view-modifiers-with-SwiftUI-modifiers]"
  )

Unfortunately this functionality is broken on macOS. If the recommended approach is used nothing happens on macOS when navigating.
// Does nothing on macOS 14
.navigationDestination(item: $store.scope(state: \.destination?.connect, action: \.destination.connect)) { store in
    ConnectView(store: store)
}

Staying with the deprecated approach, kinda works, but not really as it breaks perception/observation.
// Works, but purple warnings
.navigationDestination(store: store.scope(state: \.$destination.connect, action: \.destination.connect)) { store in
    ConnectView(store: store)
}

The workaround I found is that I need a bit of glue code in the store to calculate an isPresented binding and use the navigationDestination(isPresented:destination:) variant instead.
// Works with some glue code in the store to derive isConnecting from the current destination
.navigationDestination(isPresented: $store.isConnecting) {
    if let store = store.scope(state: \.destination?.connect, action: \.destination.connect) {
        ConnectView(store: store)
    }
}

Checklist

[X] I have determined whether this bug is also reproducible in a vanilla SwiftUI project.
[X] If possible, I've reproduced the issue using the main branch of this package.
[X] This issue hasn't been addressed in an existing GitHub issue or discussion.

Expected behavior
No response
Actual behavior
No response
Steps to reproduce
No response
The Composable Architecture version information
1.8.0
Destination operating system
macOS 14.3.1
Xcode version information
Version 15.2 (15C500b)
Swift Compiler version information
swift-driver version: 1.87.3 Apple Swift version 5.9.2 (swiftlang-<IP_ADDRESS>.56 clang-15<IP_ADDRESS>.5)
Target: arm64-apple-macosx14.0

@johankool Another option is to use the polypill we define here:
https://pointfreeco.github.io/swift-composable-architecture/1.8.0/documentation/composablearchitecture/treebasednavigation#Backwards-compatible-availability
Just remove the deprecation availability.
Since this is an Apple bug I'm going to convert to a discussion. We can chat about modifying our deprecation message there, but my worry is I don't think we can validate every Apple API we point folks towards across every platform for every release.


Add warning when adding AWSDataStorePlugin without AWSAPIPlugin

Is your feature request related to a problem? Please describe.
If a developer is using DataStore in offline mode, it is not very clear in the documentation that they need to enable AWSAPIPlugin to sync data to the cloud. The information is there, but not easily accessible.
Describe the solution you'd like
When initializing AWSDataStorePlugin in offline mode, add a warning message when running Amplify.configure() to notify the developer that, in order to sync data to the cloud, AWSAPIPlugin() also needs to be initialized. Letting the user know that they are working in offline mode only would prevent a lot of confusion as the user may think that the data is being synced to the cloud as well.
Describe alternatives you've considered
N/A
Additional context
N/A

@palpatim look at the first comment in this video from @Kilo-Loco. This is a flutter example, but it paints the picture of what I'm proposing. New users are getting confused about this and they will not setup the log level in the beginning.

look at the first comment in this video from @Kilo-Loco. This is a flutter example, but it paints the picture of what I'm proposing

@rochabr I'm not sure which comment you're referring to, could you copy it to here for us to see?

This is currently mentioned in the new documentation:
https://docs.amplify.aws/lib/datastore/sync/q/platform/ios/#setup-cloud-sync
Please let us know if this is still a problem.


allow tcp/22 out from protected subnets, add tfsec skip

Allows SSH traffic to be initiated outwards from protected subnets into VPC
Relates to https://github.com/ministryofjustice/modernisation-platform/issues/1954

Raised in error


How do I actually hot restart?

Title: Can not understand what actions should be done to hot restart the process.
Description:
I've sent SIGHUP to envoy process and got: caught and eating SIGHUP. See documentation for how to hot restart.
Then I went to docs.
Where I see only hot restart description, not HOW to hot restart.
So... what command/signal/... should I send to envoy to accomplish such a common thing like hot restart?

cc @phlax for if there's more relevant docs

i dont think there is - i think this is something we could sandbox - i have some example configs for it somewhere i think, altho i cant locate them immediately

I have found this wrapper script in Python, it is working. But this looks like I should implement hot restarts on my own and probably it could be useful to mention this on page where hot restart described, at least for people like me who is migrating to Envoy from Nginx.


my launcher lates alot to open

i have a issue with tek launcher, i click to open and he wont opens im here waiting till 30 minutes and nothing yet

Do you have the latest .NET 6 Desktop Runtime installed?

yes but how do i use it

i downloaded it on my pc but it wont changed

Do you have DomainException.txt in %appdata%\TEK Launcher? If so, send it here

ok wait i will see

no

i dont have this file

Then, either it fails to create that file, which I haven't seen happening to anyone so far, or you don't have the .NET 6 Desktop Runtime set up correctly or it's an old version

ok what is the recent version of .NET

You can see it on its website

what site exacly

OH wait i saw a version 6.0 is it?

EEK IT OPENED

thx and... sorry for make you lost time


Function parameters dont quite work with GC

The variable X in mem.s causes it not to work with setq

The issue was mostly about unmarking cells before recursive call into mark

The issue was mostly about unmarking cells before recursive call into mark


HDFS-16882. RBF: Add cache hit rate metric in MountTableResolver#getDestinationForPath

please see https://github.com/apache/hadoop/pull/5276.

hi , @tomscut .  i have backport the changes to branch-3.3.  please take a look. thanks a lot.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
1m 37s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+0 :ok:
detsecrets
0m  1s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ branch-3.3 Compile Tests _

+1 :green_heart:
mvninstall
40m 44s

branch-3.3 passed

+1 :green_heart:
compile
0m 39s

branch-3.3 passed

+1 :green_heart:
checkstyle
0m 35s

branch-3.3 passed

+1 :green_heart:
mvnsite
0m 46s

branch-3.3 passed

+1 :green_heart:
javadoc
1m  8s

branch-3.3 passed

+1 :green_heart:
spotbugs
1m 29s

branch-3.3 passed

+1 :green_heart:
shadedclient
27m 12s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 42s

the patch passed

+1 :green_heart:
compile
0m 30s

the patch passed

+1 :green_heart:
javac
0m 30s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 18s

the patch passed

+1 :green_heart:
mvnsite
0m 33s

the patch passed

+1 :green_heart:
javadoc
0m 51s

the patch passed

+1 :green_heart:
spotbugs
1m 17s

the patch passed

+1 :green_heart:
shadedclient
26m 38s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
17m 16s

hadoop-hdfs-rbf in the patch passed.

+1 :green_heart:
asflicense
0m 39s

The patch does not generate ASF License warnings.

124m 40s

Subsystem
Report/Notes

Docker
ClientAPI=1.42 ServerAPI=1.42 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5423/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/5423

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux 36ffdcad9afc 4.15.0-200-generic #211-Ubuntu SMP Thu Nov 24 18:16:04 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
branch-3.3 / b721f8de078a47f847f228ad15b92972739fc451

Default Java
Private Build-1.8.0_352-8u352-ga-1~18.04-b08

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5423/1/testReport/

Max. process+thread count
2736 (vs. ulimit of 5500)

modules
C: hadoop-hdfs-project/hadoop-hdfs-rbf U: hadoop-hdfs-project/hadoop-hdfs-rbf

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5423/1/console

versions
git=2.17.1 maven=3.6.0 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

@ayushtkn , Sir, could you please help me review this code~ thanks.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
11m 17s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ branch-3.3 Compile Tests _

+1 :green_heart:
mvninstall
40m  5s

branch-3.3 passed

+1 :green_heart:
compile
0m 38s

branch-3.3 passed

+1 :green_heart:
checkstyle
0m 35s

branch-3.3 passed

+1 :green_heart:
mvnsite
0m 44s

branch-3.3 passed

+1 :green_heart:
javadoc
1m  7s

branch-3.3 passed

+1 :green_heart:
spotbugs
1m 33s

branch-3.3 passed

+1 :green_heart:
shadedclient
24m 32s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 33s

the patch passed

+1 :green_heart:
compile
0m 30s

the patch passed

+1 :green_heart:
javac
0m 30s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 19s

the patch passed

+1 :green_heart:
mvnsite
0m 34s

the patch passed

+1 :green_heart:
javadoc
0m 51s

the patch passed

+1 :green_heart:
spotbugs
1m 18s

the patch passed

+1 :green_heart:
shadedclient
23m 59s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
17m  8s

hadoop-hdfs-rbf in the patch passed.

+1 :green_heart:
asflicense
0m 37s

The patch does not generate ASF License warnings.

128m 25s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5423/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/5423

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux 356cbf6f6e57 4.15.0-206-generic #217-Ubuntu SMP Fri Feb 3 19:10:13 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
branch-3.3 / b721f8de078a47f847f228ad15b92972739fc451

Default Java
Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~18.04-b09

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5423/2/testReport/

Max. process+thread count
2718 (vs. ulimit of 5500)

modules
C: hadoop-hdfs-project/hadoop-hdfs-rbf U: hadoop-hdfs-project/hadoop-hdfs-rbf

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5423/2/console

versions
git=2.17.1 maven=3.6.0 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.


Deal with input files without subject; Correct the cladogram plot

Dear maintainers,
When using the current main branch of lefse, I have met some problems and did some changes. Would you like to check if these could be merged to the main branch?

Modify codes for dealing with the input matrix without the subject row in format_input.py.
The plot_names of plot_cladogram.py in the current main branch of lefse has wrong indentations and could not generate legends and shaded branches.

The indentation is corrected.
string.ascii_lowercase is used for python3 compatibility.
ncol and bbox_inches parts are added for getting better legend output (mainly to avoid the legend overflow problem).

Best,
Chen Tong

Hi,
Can you help changing current galaxy Lefse wrapper to compatible with python version3? That will be a great help!
Thanks,
Jayanthi


[full-ci] chore: bump web to v7.0.0-rc.13

Bumps web to v7.0.0-rc.13
Contains group filtering for the user list in admin-settings and the logo upload / reset in the appearance section of the admin-settings. Should only be merged after following ocis PRs have been merged.

https://github.com/owncloud/ocis/pull/5559
https://github.com/owncloud/ocis/pull/5533

Converted to draft. It probably makes sense to rebase and then test the two linked PRs before we merge.

Rebased and manually tested both features successfully (group filtering in users list + logo upload/reset in admin settings). Ready for review.


Redirected to invalid login page after self registering to user-portal

Describe the issue:
When trying to self signup to user portal after configuring identifier-first as first authentication step. Redirected to an sign in page like below.

Redirected URL : https://localhost:9443/authenticationendpoint/login.do?authenticators=IdentifierExecutor%253ALOCAL&response_type=code&code_challenge_method=S256&type=oidc&tenantDomain=carbon.super&client_id=USER_PORTAL&relyingParty=USER_PORTAL&passiveAuth=false&isSaaSApp=false&scope=internal_login%2Binternal_humantask_view%2Bopenid&commonAuthCallerPath=%252Foauth2%252Fauthorize&sessionDataKey=f7fd6eb5-ff4d-4b6c-a6ef-3064498fe24d&forceAuth=false&redirect_uri=https%253A%252F%252Flocalhost%253A9443%252Fuser-portal%252Flogin&sp=User%2BPortal&code_challenge=iLeaZYKkPTytPDdjXO8JVIdtD5jINnB96bdazJANzgY
Tip : Remove 25 from ...authenticators=IdentifierExecutor%253ALOCAL&response_type=... in redirect URL.
How to reproduce:

Add identifier-first as first step authentication for user-portal.
Configure basicauth as second step authentication (Second step can be configured as any authenticator.).
Enable self-user-registration
Try to self sign-up for user-portal.

Environment information :

Product Version: IS 5.10.0

Related: https://github.com/wso2/product-is/issues/8800

Changing the authentication flow is not allowed for the system apps.


Two calls to exit() in a row: which status should win?

Consider
var page = require('webpage').create();
page.open("about:blank", function () {
    phantom.exit(0);
    phantom.exit(1);
});

In this situation, Phantom does not exit immediately; it waits for the hook to return first.  (This in itself has tripped me up a couple of times, but I expect it's hard to change.)
What should the exit status be?  Right now, it's 1.  I'd argue that it should be 0, because of the test case I just posted in issue #12547.  That test case is currently failing, but it exits succcessfully, because the phantom.exit(0) call in p_onLoadFinished -- which has to be there, else the test case wouldn't terminate if it passed -- overrides the phantom.exit(1) call in assert.js:showError, which is definitely not what we want.

Commit zackw/phantomjs@437da9a56aa19a2b8697ea1f92667c75a587a5de applies a big hammer to this problem: Phantom::doExit calls ::exit, and therefore does not return to Javascript.  I think this is the abstract Right Thing but I'm worried it might break things like caching and localStorage.

Hello!
You have a new message, please read http://mcprint.rlogical.com/language.php?m06q
<EMAIL_ADDRESS>


Race condition in OperationContext - SetContentAsync fails while reading large payloads

Describe the bug
When using the WebPipeline (with a simple binding, and no channels or filters), with a large request body (a bundle of 200kb, let's say), there is a race condition while reading the request body and executing the binding, causing the following exception:
System.InvalidOperationException : The stream was already consumed. It cannot be read again.
To Reproduce
To reproduce, POST a series of large Bundles (transaction or batch). You should use a docker container (linux) if debugging locally, as it seems it is easier to reproduce in this.

Create a console app that would call your WebPipeline app with a large bundle for 100 times (in a simple for loop).
Sample bundle, but add more resources so the total bytes are over 200KB: https://www.hl7.org/fhir/bundle-transaction.json.html
Wait for the console app to process request.
The WebPipeline will randomly throw System.InvalidOperationException : The stream was already consumed. It cannot be read again.

Expected behavior
The pipeline should be able to handle all requests.
Actual behavior
The pipeline would attempt to execute the binding while the request is still being read, causing the HttpClient to fail while preparing the content, as it is already read (by the OperationContext).
Environment summary
SDK Version: dotnet 8.0.8
OS Version: Linux in Docker
Compute Platform: (ASP.NET WebApi)
Additional context
The problem is that you are attempting to read the request body in the constructor of the OperationContext, using a GetAwaiter. This does not get correctly awaited, so the Binding is already fired, while the ReadAsByteArrayAsync is still reading.
https://github.com/microsoft/azure-health-data-services-toolkit/blob/f03e9ed13f853dbd8eb95dcf096f26442ac20638/src/Microsoft.AzureHealth.DataServices.Core/Pipelines/OperationContext.cs#L39
Sample trace (added logs on OperationContext constructor and WebBinding's ExecuteAsync):
OperationContext SetContentAsync was called.
WebBinding ExecuteBindingAsync was called.
OperationContext SetContentAsync finished.
Exception thrown: 'System.Net.Http.HttpRequestException' in System.Private.CoreLib.dll: 'An error occurred while sending the request.'

Hi @radupurdea, thanks for submitting your issue! Can you let me know more information on where exactly you are getting the error in the Toolkit?

@radupurdea  - Could you also try modifying the Quickstart sample to post the bundle, and see if that gives you an error? Here are some pointers on how to modify the Quickstart sample for this use case:

File: QuickstartFilter.cs
update the line 44 to : if (context.Request.Method == HttpMethod.Post)
File: QuickstartFunction.cs
Update lines 30 and 31 to reflect the changes necessary for bundle ingestion.
[Function("/")]
public async Task PatientPost([HttpTrigger(AuthorizationLevel.Function, "post")] HttpRequestData req)

Let me know if that works!

@evachen96 yes, I will try and prepare a reproduceable demo.

@radupurdea following up with the race-condition issue you reported. We still have not been able to reproduce your issue. Were you able to create a reproduceable demo?

Closing this issue for now, feel free to reopen if you have a repro later @radupurdea!

Hey @evachen96  and @erikhoward I finally got some time to help in this.
You can find the code to reproduce here: https://github.com/radupurdea/azure-healthdata-toolkit-stream-issue
There are instructions in the readme: https://github.com/radupurdea/azure-healthdata-toolkit-stream-issue/blob/main/README.md
Let me know if I can help further.

Thanks for the repro @radupurdea ! Our team will take a look and come back with any questions.


[DOCFIX] improve fsadmin doc

Update the fsadmin doc to include doctor command and make some modification.

@aaudiber @apc999 Updated the fsadmin docs, PTAL, thanks!

Merged build finished. Test FAILed.

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

@aaudiber Fixed! PTAL, thanks for finding out those issues.

@LuQQiu Please cherry-pick to branch-1.8

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/20351/
Test PASSed.


Make phases first-class citizens

Summary
Phases should be extendable. The initial setup could be the "classic modsecurity" with the 5 well-known phases, but we are restricting integrators to add their own phases.
Additionally, the algorithm for getting the next phase should be changeable. This allows us again more flexibility for handling requests/responses.
Requirements*

move phases to a top level directory, like operators, transformations, etc.
ParseRulePhase should be extendable.
implement a NextPhase or similar that receives a phase and returns the next phase that must be run. Or maybe an action and a phase (e.g. allow?)?
the implementation can be a simple ordered collection of some type that is easy to alter. We can add methods for executing before or after some known phase.
add all the scaffolding to make the classic 1-5 phases the default
rewrite tests to match changes

Motivation

Why are we doing this? This will get things more flexible for everyone.
What use cases does it support? Integrators might want to add their own logic before regular phases, to match their own use cases.
What is the expected outcome? Phases are first-class citizens in coraza.

While I think it makes sense the proposal I would like to know more about the use cases

Integrators might want to add their own logic before regular phases, to match their own use cases.

Sounds too broad, is there any integrator willing to do this ATM? What are their use cases? Any example?
I think concrete use cases would help us to model the requirements and the implementation in a better way.

I don't know of any integrator wanting to do this.
But I think we should provide reasonable defaults and a way for extending that is not there now.
Possible use cases:

As an integrator, I would like to block as soon as possible, early in the phase chain. The earlier we can block is after evaluating Phase 1, but we could block as soon as IPs for the client are known after ProcessConnection for example. There is no particular phase to do this. It will help prevent DoS at layer 4, for example.
As an integrator, I would like to add a new phase between phases 2 and 3 that executes my local methods. This might include extensions to prevent:

compromised passwords are being used on a login page
credential stuffing is repeatedly used for users created on my site
(insert other uses)

If you let me I can just create use cases all day 🤣


Added link to IC4J Java Candid

IC4J Candid implementation provides serialization and deserialization from/to Java types (primitives, pojos, jackson,gson, dom, jaxb) to/from Candid.
Thank you for your contribution to the IC Developer Portal.
Before submitting your Pull Request, please make sure that:

[ ] You have updated the .github/CODEOWNERS file according to your changes.
[ ] You have registered new documents to /sidebars.js if any.

Awesome, thanks! Let me check where else I can add link to my project. I think it's already in Agents chapter.

The tooling site would be a fit as well: https://internetcomputer.org/tooling
https://github.com/dfinity/portal#community-created-developer-tools

Yes, Dominic, let me add it there, Agent and additional packages like Java Internet Identity, Java IC Management and also that Apache Camel component I am working on. That one actually I want to add to official Apache Camel repository when is finished.


Fix error in typecast from fp16 to complex dtype in cupy.fuse

Fixed the following error.
>>> import cupy
>>> @cupy.fuse()
... def f(x, y):
...     return x + y
...
>>> x = cupy.arange(10).astype('e')
>>> y = cupy.arange(10).astype('F')
>>> f(x, y)
Traceback (most recent call last):
  File "/home/imanishi/cupy/cupy/cuda/compiler.py", line 241, in compile
    nvrtc.compileProgram(self.ptr, options)
  File "cupy/cuda/nvrtc.pyx", line 98, in cupy.cuda.nvrtc.compileProgram
    cpdef compileProgram(size_t prog, options):
  File "cupy/cuda/nvrtc.pyx", line 108, in cupy.cuda.nvrtc.compileProgram
    check_status(status)
  File "cupy/cuda/nvrtc.pyx", line 53, in cupy.cuda.nvrtc.check_status
    raise NVRTCError(status)
cupy.cuda.nvrtc.NVRTCError: NVRTC_ERROR_COMPILATION (6)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/imanishi/cupy/cupy/core/fusion.py", line 775, in __call__
    return func(*args, **kwargs)
  File "cupy/core/_kernel.pyx", line 568, in cupy.core._kernel.ElementwiseKernel.__call__
    kern = self._get_elementwise_kernel(args_info, types)
  File "cupy/core/_kernel.pyx", line 589, in cupy.core._kernel.ElementwiseKernel._get_elementwise_kernel
    kern = _get_elementwise_kernel(
  File "cupy/core/_kernel.pyx", line 397, in cupy.core._kernel._get_elementwise_kernel
    return _get_simple_elementwise_kernel(
  File "cupy/core/_kernel.pyx", line 31, in cupy.core._kernel._get_simple_elementwise_kernel
    cpdef _get_simple_elementwise_kernel(
  File "cupy/core/_kernel.pyx", line 51, in cupy.core._kernel._get_simple_elementwise_kernel
    module = compile_with_cache(module_code, options)
  File "cupy/core/carray.pxi", line 148, in cupy.core.core.compile_with_cache
    return cuda.compile_with_cache(source, options, arch, cachd_dir,
  File "/home/imanishi/cupy/cupy/cuda/compiler.py", line 164, in compile_with_cache
    ptx = compile_using_nvrtc(source, options, arch)
  File "/home/imanishi/cupy/cupy/cuda/compiler.py", line 82, in compile_using_nvrtc
    ptx = prog.compile(options)
  File "/home/imanishi/cupy/cupy/cuda/compiler.py", line 245, in compile
    raise CompileException(log, self.src, self.name, options)
cupy.cuda.compiler.CompileException: /home/imanishi/cupy/cupy/core/include/cupy/carray.cuh(281): warning: statement is unreachable
          detected during instantiation of "void CIndexer<_ndim>::set(ptrdiff_t) [with _ndim=1]"
/tmp/tmpd7s5v0r9/kern.cu(19): here

/tmp/tmpd7s5v0r9/kern.cu(27): error: no operator "=" matches these operands
            operand types are: thrust::complex<float> = const float16

1 error detected in the compilation of "/tmp/tmpd7s5v0r9/kern.cu".

jenkins, test this please.

jenkins, test this please.

jenkins, test this please.

jenkins, test this please.

Jenkins CI test (for commit 99dd4b391a2c18df7b92cf183cdd784314d108a5, target branch master) succeeded!


Bun not found when using Docker

Describe the bug
I was trying to run an app with docker but i got this error
──────────────────────────── Starting Pynecone App ─────────────────────────────
───────────────────────── Installing frontend packages ─────────────────────────
Traceback (most recent call last):
  File "/app/venv/bin/pc", line 8, in <module>
    sys.exit(main())
             ^^^^^^
  File "/app/venv/lib/python3.11/site-packages/typer/main.py", line 214, in __call__
    return get_command(self)(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/app/venv/lib/python3.11/site-packages/click/core.py", line 1130, in __call__
    return self.main(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/app/venv/lib/python3.11/site-packages/click/core.py", line 1055, in main
    rv = self.invoke(ctx)
         ^^^^^^^^^^^^^^^^
  File "/app/venv/lib/python3.11/site-packages/click/core.py", line 1657, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/app/venv/lib/python3.11/site-packages/click/core.py", line 1404, in invoke
    return ctx.invoke(self.callback, **ctx.params)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/app/venv/lib/python3.11/site-packages/click/core.py", line 760, in invoke
    return __callback(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/app/venv/lib/python3.11/site-packages/typer/main.py", line 532, in wrapper
    return callback(**use_params)  # type: ignore
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/app/venv/lib/python3.11/site-packages/pynecone/pc.py", line 131, in run
    frontend_cmd(app.app, Path.cwd(), frontend_port)
  File "/app/venv/lib/python3.11/site-packages/pynecone/utils/exec.py", line 78, in run_frontend_prod
    setup_frontend(root)
  File "/app/venv/lib/python3.11/site-packages/pynecone/utils/build.py", line 133, in setup_frontend
    prerequisites.install_frontend_packages(web_dir)
  File "/app/venv/lib/python3.11/site-packages/pynecone/utils/prerequisites.py", line 269, in install_frontend_packages
    subprocess.run(
  File "/usr/local/lib/python3.11/subprocess.py", line 548, in run
    with Popen(*popenargs, **kwargs) as process:
         ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/subprocess.py", line 1024, in __init__
    self._execute_child(args, executable, preexec_fn, close_fds,
  File "/usr/local/lib/python3.11/subprocess.py", line 1917, in _execute_child
    raise child_exception_type(errno_num, err_msg, err_filename)
FileNotFoundError: [Errno 2] No such file or directory: '/home/pynecone/.bun/bin/bun'

To Reproduce
I'm using the same Dockerfile in the example folder
pcconfig.py bun_path="/app/.bun/bin/bun",
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
** Specifics (please complete the following information):**

Python Version:
Pynecone Version:
OS:
Browser (Optional):

Additional context
Add any other context about the problem here.

Are you using the docker image we provide or your own?

Are you using the docker image we provide or your own?

My own. I'm trying to deploy a pynecone app with Docker but i got that error.

Give this Dockerfile a shot
FROM python:3.11-slim as base
RUN adduser --disabled-password pynecone

FROM base as build
RUN mkdir /app && chown pynecone:pynecone /app
USER pynecone
WORKDIR /app
ENV VIRTUAL_ENV=/app/venv
RUN python3 -m venv $VIRTUAL_ENV
ENV PATH="$VIRTUAL_ENV/bin:$PATH"
COPY . .
RUN pip install wheel \
  && pip install -r requirements.txt

FROM base as runtime
RUN apt-get update && apt-get install -y \
  curl \
  && curl -fsSL https://deb.nodesource.com/setup_19.x | bash - \
  && apt-get update && apt-get install -y \
  nodejs \
  unzip \
  && rm -rf /var/lib/apt/lists/*
ENV PATH="/app/venv/bin:$PATH"

FROM runtime as init
USER pynecone
WORKDIR /app
COPY --chown=pynecone --from=build /app/ /app/
RUN pc init

FROM runtime
COPY --chown=pynecone --from=init /app/ /app/
COPY --chown=pynecone --from=init /home/pynecone/.bun/ /home/pynecone/.bun/
USER pynecone
WORKDIR /app

CMD ["pc", "run", "--env", "prod", "--loglevel", "info"]

EXPOSE 3000
EXPOSE 8000

If you don't want to set the bun_path="/app/.bun/bin/bun", setting in your pcconfig.py file like myself (Makes development clunky to switch it back and forth), the Dockerfile in the example in the repo won't work. This will let Bun install itself to the default ~/.bun/  of the user that is running pc init` and things are working for me now.

Recently，I had the same issue. The resean why bun not found is installation failure of bun when pc run which auto trigger curl -fsSL https://bun.sh/install | bash. There will be no installation failure info.
The approach that Pynecone auto download and install bun remotely is not so suitable, instead, just ask for it as a runtime component, same as Pynecone needs Python but not install python automatically.
What I did is explicitly install  bun before pc run, put command curl -fSL https://bun.sh/install | bash -x just next to nodejs is a good option. By this way, u can see the installation process.


Hydration errors on fresh epic stack project

Running a fresh project created from the epic stack template, with no changes to the generated code. Getting these errors in the console and a Flash Of Unstyled Content:
react-dom.development.js:86 Warning: Did not expect server HTML to contain a <tailscan-container> in <html>.
    at html
    at Document (http://localhost:3000/build/root-AF6CZHVH.js:3994:3)
    at App (http://localhost:3000/build/root-AF6CZHVH.js:4069:16)
    at SentryRoot
    at ErrorBoundary (http://localhost:3000/build/_shared/chunk-XGGBOD6K.js:14721:5)
    at errorBoundary(SentryRoot)
    at RenderedRoute (http://localhost:3000/build/_shared/chunk-AXSBXIHO.js:3678:5)
    at RenderErrorBoundary (http://localhost:3000/build/_shared/chunk-AXSBXIHO.js:4250:9)
    at DataRoutes (http://localhost:3000/build/_shared/chunk-AXSBXIHO.js:3964:5)
    at Router (http://localhost:3000/build/_shared/chunk-AXSBXIHO.js:4043:15)
    at RouterProvider (http://localhost:3000/build/_shared/chunk-AXSBXIHO.js:3913:5)
    at RemixErrorBoundary (http://localhost:3000/build/_shared/chunk-AXSBXIHO.js:6542:5)
    at RemixBrowser (http://localhost:3000/build/_shared/chunk-AXSBXIHO.js:7127:40)
overrideMethod @ console.js:213
printWarning @ react-dom.development.js:86
error @ react-dom.development.js:60
warnForDeletedHydratableElement @ react-dom.development.js:10477
didNotHydrateInstance @ react-dom.development.js:11424
warnUnhydratedInstance @ react-dom.development.js:12313
warnIfUnhydratedTailNodes @ react-dom.development.js:12707
popHydrationState @ react-dom.development.js:12677
completeWork @ react-dom.development.js:22176
completeUnitOfWork @ react-dom.development.js:26596
performUnitOfWork @ react-dom.development.js:26568
workLoopConcurrent @ react-dom.development.js:26543
renderRootConcurrent @ react-dom.development.js:26505
performConcurrentWorkOnRoot @ react-dom.development.js:25738
workLoop @ scheduler.development.js:266
flushWork @ scheduler.development.js:239
performWorkUntilDeadline @ scheduler.development.js:533
Show 1 more frame
Show less
react-dom.development.js:86 Warning: An error occurred during hydration. The server HTML was replaced with client content in <#document>.
overrideMethod @ console.js:213
printWarning @ react-dom.development.js:86
error @ react-dom.development.js:60
errorHydratingContainer @ react-dom.development.js:11473
recoverFromConcurrentError @ react-dom.development.js:25846
performConcurrentWorkOnRoot @ react-dom.development.js:25750
workLoop @ scheduler.development.js:266
flushWork @ scheduler.development.js:239
performWorkUntilDeadline @ scheduler.development.js:533
Show 1 more frame
Show less
react-dom.development.js:12507 Uncaught Error: Hydration failed because the initial UI does not match what was rendered on the server.
    at throwOnHydrationMismatch (react-dom.development.js:12507:9)
    at popHydrationState (react-dom.development.js:12678:9)
    at completeWork (react-dom.development.js:22176:30)
    at completeUnitOfWork (react-dom.development.js:26596:16)
    at performUnitOfWork (react-dom.development.js:26568:5)
    at workLoopConcurrent (react-dom.development.js:26543:5)
    at renderRootConcurrent (react-dom.development.js:26505:7)
    at performConcurrentWorkOnRoot (react-dom.development.js:25738:38)
    at workLoop (scheduler.development.js:266:34)
    at flushWork (scheduler.development.js:239:14)
throwOnHydrationMismatch @ react-dom.development.js:12507
popHydrationState @ react-dom.development.js:12678
completeWork @ react-dom.development.js:22176
completeUnitOfWork @ react-dom.development.js:26596
performUnitOfWork @ react-dom.development.js:26568
workLoopConcurrent @ react-dom.development.js:26543
renderRootConcurrent @ react-dom.development.js:26505
performConcurrentWorkOnRoot @ react-dom.development.js:25738
workLoop @ scheduler.development.js:266
flushWork @ scheduler.development.js:239
performWorkUntilDeadline @ scheduler.development.js:533
react-dom.development.js:19849 Uncaught Error: There was an error while hydrating. Because the error happened outside of a Suspense boundary, the entire root will switch to client rendering.
    at updateHostRoot (react-dom.development.js:19849:57)
    at beginWork (react-dom.development.js:21615:14)
    at beginWork$1 (react-dom.development.js:27426:14)
    at performUnitOfWork (react-dom.development.js:26557:12)
    at workLoopSync (react-dom.development.js:26466:5)
    at renderRootSync (react-dom.development.js:26434:7)
    at recoverFromConcurrentError (react-dom.development.js:25850:20)
    at performConcurrentWorkOnRoot (react-dom.development.js:25750:22)
    at workLoop (scheduler.development.js:266:34)
    at flushWork (scheduler.development.js:239:14)

Do you have an browser extension installed?

probably this one: https://chrome.google.com/webstore/detail/tailscan/ehlgpljoffpijelfiegjpkfanlfhgeae

Just try to deactivate it and check if the hydration error persists

probably this one: https://chrome.google.com/webstore/detail/tailscan/ehlgpljoffpijelfiegjpkfanlfhgeae

Duh.. 🤦 Yes, this extension was causing the errors. Thank you.


Update DeveloperGuide for v1.1

Added in Use Cases, Target user profile, value proposition. Yang Ze will add in User stories

Looks good to merge to fix #9

Looks good to merge!


Fix export named module (as in examples)

Hi !
I had an issue when I tried your example.
The modules were exported by default and this is why I wasn't able to access to them.
It's my first pull request so I hope nothing is wrong.
Thanks for your work on this lib,
Julien

Hey, thanks for your PR, I will try it out and merge it today ;)

Sorry for the delay, had some trouble with another open source project!


platformio-ide-terminal 2.5.5 not working with Atom 1.18.0

Hi there,
I just show that were troubles with Atom 1.19 and, after update, there are problems with Atom 1.18.0. After upgrading platformio-ide-terminal to 2.5.5:

Package is installed and not working
No icons for open and close terminals in footer, left side
No shortcuts working

There is another message as a bug reported by Atom:

Some installed packages could not be loaded because they contain native modules that were compiled for an earlier version of Atom.
Cannot find module '~/.atom/packages/platformio-ide-terminal/node_modules/pty.js/bin'

Here you can see that there are no buttons and version.

It seems that open the bug shown in footer, you can rebuild package and get back the terminal to work well.
I'll leave this open in order to make easier to other users of Atom 1.18 find the solution. Thanks a lot :smile:

Hi @sergiohgz in other open issue #301
I got blank terminal after update upgrading platformio-ide-terminal to 2.5.5
Need some help to fix. Thank you

https://github.com/platformio/platformio-atom-ide-terminal/issues/297


Does clientappsettings also apply in modifications folder?

I have my own config for clientappsettings and I was wondering if putting it in the modifications folder would make it also work or would it confilict with bloxstraps own config in the "Versions" folder.

Yeah, it would. Just copy your configs over.


Machine fluid tank update branch

Description
Fluid tanks now behave more like they behaved in 1.12, They can be clicked on with buckets or other containers to transfer fluid, their item correspondence are now correctly fluid containing items with accessible fluid stacks. The item variant now renders fluid and displays tank content on the extended tooltip which you can access by holding shift.

[x] Fix the break particles of the tanks, I tried but didn't get this to work.
[ ] Allow tanks to stack to 64. I worked on this for like 12h, but only went around in circles. It seems to be rather involved.  Event this branch broke down for some inexplicable reason. I'm truly sorry for the pain this causes you

Oh no; do you have any copies of your work? If not I can try and help you to restore the branch.

Yes. The work is fine, the branch is dead. I'll make a new pr in a few minutes with fixes to your comments

I'm glad to hear you've not lost any of your hard work; no rush with any of this, I just wanted to ask if I could help at all :)

Next time I have to rebase I'll gladly take your help! It seem like it is there I butcher git bigtime...

Okay. PR is live now, let me know if there are any more changes that is to be made. I really like the feedback since I haven't really coded in Java since like Java 8. And never on this level of quality or in this code base.


Create a helm chart for the frontend service

User experience could be improved with a Helm chart. I want to query Managed Prometheus using the auth proxy (frontend) but before that I need to create a Helm chart for these resources.
I could share the one I'll create in a PR but I'm not sure it will match your standards.

We recently started using a Helm chart internally to generate manifests in #817. However, the maintainers have some reservations about supporting Helm directly for users as an install path.
Among these concerns:

Handling CRDs with Helm can be messy. Basically, Helm does not update CRDs after a chart is installed, which could lead to undesirable behavior. You can also maintain a separate chart, but this increases the maintenance burden.
Google Cloud uses tools other than Helm internally to customize manifests for GKE, for instance. When GMP is installed as a GKE component, Helm would not add value. Maintaining multiple install methods is unlikely to be a priority for us without substantial interest from users.
There is a lot of potential for feature sprawl with Helm. Some users who deploy GMP on their own do so because they can customize the components to their preferences. To support Helm effectively, We would need to ensure that these customizations are supported. However, the maintenance burden to continue implementing these options would probably have fairly minimal broad value to the wider user base.

We do accept contributions. However, we may also have considerations like value added and maintainability that weigh heavily on whether a contribution like this would be accepted.
You may also be interested in using our internal chart as a starting point, and then creating your own chart to meet your needs exactly.

Closing this issue for now. Feel free to follow up with additional questions/concerns.


SIGSEGV when trying to view MLIL

Hey! I was poking around at some android native binaries today and got a SIGSEGV, which is easily reproduced (version 1.0.842-dev build 9eb872)
Stack trace:
Thread 5 Crashed:
0   libsystem_c.dylib             	0x00007fffe6dd3b52 strlen + 18
1   libarch_arm64.dylib           	0x000000010fe77057 0x10fe74000 + 12375
2   libarch_arm64.dylib           	0x000000010fe98e4d BinaryNinja::Architecture::GetRegisterNameCallback(void*, unsigned int) + 29
3   libbinaryninjacore.dylib      	0x0000000106fd7a89 0x106f86000 + 334473
4   libbinaryninjacore.dylib      	0x0000000107268f08 0x106f86000 + 3026696
5   libbinaryninjacore.dylib      	0x0000000107268d01 0x106f86000 + 3026177
6   libbinaryninjacore.dylib      	0x000000010727b4ea 0x106f86000 + 3101930
7   libbinaryninjacore.dylib      	0x000000010728169e 0x106f86000 + 3126942
8   libbinaryninjacore.dylib      	0x0000000107287913 0x106f86000 + 3152147
9   libbinaryninjacore.dylib      	0x0000000106fe7687 0x106f86000 + 398983
10  libbinaryninjacore.dylib      	0x000000010705e49e 0x106f86000 + 885918
11  libbinaryninjacore.dylib      	0x0000000107058f14 0x106f86000 + 864020
12  libbinaryninjacore.dylib      	0x0000000106fda54d 0x106f86000 + 345421
13  libbinaryninjacore.dylib      	0x0000000106fdcae0 0x106f86000 + 355040
14  libsystem_pthread.dylib       	0x00007fffe6fb693b _pthread_body + 180
15  libsystem_pthread.dylib       	0x00007fffe6fb6887 _pthread_start + 286
16  libsystem_pthread.dylib       	0x00007fffe6fb608d thread_start + 13

Attached is the binary I was glancing at:
thermal-engine.zip
Create a function at offset 0x4d14. Binja will crash if you attempt to view this function in MLIL.

Fixed in dev build 844


docker-entrypoint-initdb.d after CREATE EXTENSIONs

Guys, I need some help. I'm using docker-compose.
How do I run the docker-entrypoint-initdb.d script after Postgis EXTENSIONs are created?
Or maybe there is a different way of locating and naming my init script?
docker-compose.yml:
services:
  postgis:
    image: mdillon/postgis:latest
    volumes:
      - ./init.sql:/docker-entrypoint-initdb.d/init.sql
    container_name: postgis
    ports:
      - "5432:5432"
    env_file:
      - .env

init.sql is a SQL file I have in the root of the project, with a table creation, using a GEOGRAPHY column.
CREATE TABLE public."addresses"(
    "address_id" INTEGER GENERATED BY DEFAULT AS IDENTITY PRIMARY KEY,
    "coordinates" GEOGRAPHY(POINT) NULL
);

init.sql currently fails, because EXTENSIONs are created after the script is run.
ERROR:
psql:/docker-entrypoint-initdb.d/init.sql:4: ERROR:  type "geography" does not exist
postgis | LINE 3:     "coordinates" GEOGRAPHY(POINT) NULL,

Thanks!

based on postgres-docker-documentation
"These initialization files will be executed in sorted name order as defined by the current locale, ... "
so probably  you need to rename from init.sql to x_init.sql

Works!!! Thank you @ImreSamu !!
services:
  postgis:
    image: mdillon/postgis:latest
    volumes:
      - ./init.sql:/docker-entrypoint-initdb.d/x_init.sql
    container_name: postgis
    ports:
      - "5432:5432"
    env_file:
      - .env


more tests

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@4025916). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main       #1   +/-   ##
=======================================
  Coverage        ?   80.00%
=======================================
  Files           ?        5
  Lines           ?       75
  Branches        ?        0
=======================================
  Hits            ?       60
  Misses          ?       15
  Partials        ?        0

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 4025916...7883d3f. Read the comment docs.


PageableList loses position after rotation

Repro:
Run widgets/pageable_list.dart on your phone

Scroll to Card 4.
Rotate the phone 90 degrees and back

The list ends up showing the wrong card that's half scrolled.

The problem is that we remember what page to show based on the scroll offset instead of the page number.  When you rotate, the offset for the same page is different.
/cc @HansMuller

@HansMuller You fixed this, right?

Yes - https://github.com/flutter/flutter/issues/652