Add completion for loop labels after Break/Continue

PR Summary
Adds completion for loop labels after labeled control flow statements such as Break and Continue.
The completion will look for any loops with a label that surrounds the Break/Continue keywords.
The tooltips for the completion entries shows the relevant loop.

PR Context
Tab completion is always convenient because it helps prevents typos. It also helps prevent a relatively common mistake of including a colon in the label after Break/Continue.

PR Checklist

[X] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[X] Summarized changes
[X] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[X] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.

Breaking changes

[X] None
OR
[ ] Experimental feature(s) needed

[ ] Experimental feature name(s):

User-facing changes

[X] Not Applicable
OR
[ ] Documentation needed

[ ] Issue filed:

Testing - New and feature

[ ] N/A or can only be tested interactively
OR
[X] Make sure you've added a new test if existing tests do not effectively test the code changed

Tooling

[X] I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
OR
[ ] I have considered the user experience from a tooling perspective and opened an issue in the relevant tool repository. This may include:

[ ] Impact on PowerShell Editor Services which is used in the PowerShell extension for VSCode
(which runs in a different PS Host).

[ ] Issue filed:

[ ] Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features.

[ ] Issue filed:

[ ] Impact on PSScriptAnalyzer (which provides linting & formatting in the editor extensions).

[ ] Issue filed:

[ ] Impact on EditorSyntax (which provides syntax highlighting with in VSCode, GitHub, and many other editors).

[ ] Issue filed:

Adding @daxian-dbw as area expert.

Can follow works (without closing brackets)?
:Outer do {:Inner while ($true){ break } continue ^

Can follow work (without closing brackets)? :Outer do {:Inner while ($true){ break } continue ^

Now it does :)
I doubt most people will notice though. If you are using loop labels you are almost certainly editing in an editor and using snippets to create the loops.

@adityapatwardhan This PR is ready to be merged.

@MartinGC94 Thanks for your contribution!


Updated rust-evm

What was wrong?
We were using rust-evm version 0.14, which is a few months old.
How was it fixed?
Updated to the most recent version (0.18).
To-Do

[ ] OPTIONAL: Update Spec if applicable
[x] Clean up commit history

Codecov Report

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

@@           Coverage Diff           @@
##           master     #106   +/-   ##
=======================================
  Coverage   87.04%   87.04%
=======================================
  Files          39       39
  Lines        2369     2369
=======================================
  Hits         2062     2062
  Misses        307      307

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 de661d0...864092c. Read the comment docs.


add lock settings after init

I want to:

allow click page to auto close Slidebars.
sometimes I can press one button to lock Slidebars, so Slidebars will not auto close when I click page.

I don't want to modify Slidebars, because using bower.
My currunt solution is (without modify source) using jQuery:

// save click event to tmp var
var tmp_slidebars_click_bind = $._data($('.sb-site-container')[0], "events").click;

// unbind click event
 $._data($('.sb-site-container')[0], "events").click = 0;

// if needed, rebind click event again
 $._data($('.sb-site-container')[0], "events").click = tmp_slidebars_click_bind ;

Can @adchsm add support for this feature directly in source ?

The new version of Slidebars doesn't have any lock settings, but is locked by default. I'll close this, but please raise a new issue if you continue to experience any problems.


Kitematic somehow keeps the default boot2docker VM from functioning

Kitematic kindly uses its own VM (kitematic-vm) instead of the default boot2docker-vm. However, it still makes it impossible to use the default VM through boot2docker because it takes over the default (the only?) IP address.
$ boot2docker --vm=kitematic-vm shellinit
Writing /Users/peeja/.boot2docker/certs/kitematic-vm/ca.pem
Writing /Users/peeja/.boot2docker/certs/kitematic-vm/cert.pem
Writing /Users/peeja/.boot2docker/certs/kitematic-vm/key.pem
    export DOCKER_HOST=tcp://<IP_ADDRESS>:2376
    export DOCKER_CERT_PATH=/Users/peeja/.boot2docker/certs/kitematic-vm
    export DOCKER_TLS_VERIFY=1

$ boot2docker shellinit
Writing /Users/peeja/.boot2docker/certs/boot2docker-vm/ca.pem
Writing /Users/peeja/.boot2docker/certs/boot2docker-vm/cert.pem
Writing /Users/peeja/.boot2docker/certs/boot2docker-vm/key.pem
    export DOCKER_TLS_VERIFY=1
    export DOCKER_HOST=tcp://<IP_ADDRESS>:2376
    export DOCKER_CERT_PATH=/Users/peeja/.boot2docker/certs/boot2docker-vm

Both configurations connect to Docker on tcp://<IP_ADDRESS>:2376. Thus, even though I've spun up a separate boot2docker-vm, there's no way to use it. Instead, my docker client connects to the kitematic-vm Docker server.
I think there's a way to configure a different IP for a VM, but I'm not clear on what the right way is. Assuming there is, I think Kitematic should configure a non-default IP for its VM, so the boot2docker command continues to work as expected with its default values.

just tried the latest version it it created a vm named "dev" instead of using the boot2docker-vm

Same for me. I'm not on the beta, however.

Same for me. Kitematic 0.5.10 created a VM called dev. I'm on OS X 10.10.2

I've also just delved into the world of Kitematic and am experiencing the same issue outlined above, Kitematic v. 0.5.19, Mac OS X Yosemite 10.10.3

Reopening this since it's occurring often. Diving in for a fix, thanks for the comments all.

Fixed in v0.6 - please re-open if you are still running into issues.

It's still creating a dev vm instead of using the boot2docker-vm for me.
Also the download link on kitematic is pointing to the old version.. :)

Confirming that it is still installing a separate VM on version 0.6.3.

Version 0.7.2 still uses the dev VM instead of boot2docker VM.

my 0.7.4 still installed "dev" VM.

@Fenkiou By boot2docker VM, are you referring to Kitematic using boot2docker to provision the VMs? Kitematic uses Docker-machine (latest from Docker) to provision the VMs.
@MoonStrike On Windows, Kitematic now provisions "kitematic" VM instead of "dev" VM. The reason why this is not happening for Mac yet is because we have users currently on the "dev" VM on Mac, and we will need to transition them.

@mchiang0610 No sorry, I mean that kitematic do not use the boot2docker-vm VirtualBox VM.
Anyway, I only use kitematic now as I don't use docker too much so there is no boot2docker-vm on my Mac.


Terminal statuses

Please analyze the possibility to add a note listing what are the terminal statuses.
As this functionality might not work for the Noncompliant status, it may cause misinterpretation.

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

ID: a59b6ac8-0513-2b02-ac8c-74a0300de653
Version Independent ID: 7ac6cfd5-e8dd-d32e-ed3b-115f1583f02c
Content: Recalculate SLAs in terminal status in Dynamics 365 Customer Service
Content Source: ce/customer-service/enable-sla-recalculation.md
Service: dynamics-365-customerservice
GitHub Login: @neeranelli
Microsoft Alias: nenellim

Thanks for your comment, @fmarcellino. This issue has been assigned to the doc author for review.

@fmarcellino : Updated required topics. Closing the issue.


Update getting-started-with-database-engine-permissions.md

@V0d01ey : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@V0d01ey This change looks good to me, thanks! I'll merge it in and allow @VanMSFT to make any additional modifications (if needed) after it publishes. #sign-off


feat: integrate our mempool with the account manager service

Feature Request
Now that https://github.com/kkrt-labs/kakarot-rpc/pull/1321 is merged, the mempool that is filled inside the send_raw_transaction should also be integrated properly by our account manager service for it to take and remove transactions from the mempool properly
https://github.com/kkrt-labs/kakarot-rpc/blob/f97902f15b488f4fb9db51738e23f287154033f4/src/pool/mempool.rs#L61

done, fixing the tests right now


Ban Appeal

I got banned from Xray I'm super sorry I wont do it again. I was in the server for about 2 weeks and I was unknown of this being cheating.
i will not do this again and I'm sorry.
Minecraft username- Sonictheeggnog
Discord - Hex#9691
feel free to contact me about the appeal

I've been given reason to suspect that you were aware that xray usage on the server was not allowed, but I'll give you the benefit of the doubt here. I've reduced your ban to a 1 day tempban starting from now.


MusicBrainz schema change release 2024-05-13 (29)

We're seeing the following error:
mbslave.replication.MismatchedSchemaError: Mismatched schema sequence, 28 (database) vs 29 (replication packet)

This is caused by MusicBrainz schema change release 2024-05-13

Should have been acoustid/mbslave instead, see https://github.com/acoustid/mbslave/issues/10


Why not to create a Rest Api for odysee !!

I have a list of videos that I want to upload and manage from my python script.

It's not publicly documented, but you can check out the various calls that Odysee makes in the network tab. They mirror https://twitter.com/RachelBTCsmith/status/1463890124534472712?t=mSQmpqXW6wOdJJo1MjaXrw&s=19 for the most part.

It would be better if you document it well so that new develop like me find it more easy to use.


Flaky actor test

See test run: https://github.com/itchysats/itchysats/runs/7611016167?check_suite_focus=true
First seen on PR: https://github.com/itchysats/itchysats/pull/2599
Copied logs:
 running 1 test
2022-08-01T12:33:26.229461Z DEBUG given_rollover_when_oracle_attests_long_liquidation_price_can_liquidate:start_both:Start maker: maker::actor_system: Maker actor system ready
2022-08-01T12:33:26.233879Z  INFO maker::connection: Listening on <IP_ADDRESS>:41673
2022-08-01T12:33:26.245047Z  INFO Handle NewListenAddress: xtra_libp2p::endpoint: Listen address added address=/ip4/<IP_ADDRESS>/tcp/35813
2022-08-01T12:33:26.718108Z  INFO given_rollover_when_oracle_attests_long_liquidation_price_can_liquidate:start_both:Start taker: daemon_tests: Connecting to maker /ip4/<IP_ADDRESS>/tcp/35813/p2p/12D3KooWRyHFsHo72WWsFqBkeN1m1R9CvWPApu9dEwmMqVdXEyk1
2022-08-01T12:33:26.719799Z DEBUG given_rollover_when_oracle_attests_long_liquidation_price_can_liquidate:start_both:Start taker:Create TakerActorSystem{n_payouts=200 connect_timeout_secs=10 environment=Test}: daemon: Taker actor system ready
2022-08-01T12:33:26.723040Z DEBUG online_status::Actor started: daemon::online_status: Online status watch actor started. Monitoring for peer id changes: PeerId("12D3KooWRyHFsHo72WWsFqBkeN1m1R9CvWPApu9dEwmMqVdXEyk1")
2022-08-01T12:33:26.723743Z DEBUG Start dialer actor: xtra_libp2p::dialer: Starting dialer actor
2022-08-01T12:33:26.725844Z DEBUG connect: daemon::connection: No connection to the maker
2022-08-01T12:33:26.727049Z DEBUG connect:Handle Connect: daemon::connection: Connecting to maker address=<IP_ADDRESS>:41673
2022-08-01T12:33:26.748658Z DEBUG maker::connection: Upgrade new connection taker_address=<IP_ADDRESS>:45102
2022-08-01T12:33:26.762425Z DEBUG responder_handshake: daemon::noise: Noise protocol responder handshake is complete
2022-08-01T12:33:26.767026Z DEBUG connect:Handle Connect:initiator_handshake: daemon::noise: Noise protocol initiator handshake is complete
2022-08-01T12:33:26.781836Z  INFO Handle ConnectionReady: maker::connection: Connection is ready taker_id=98bfe1af2c3dae9187c47f7ded06428c334924a61518bf78a17cf6077224ba14 taker_address=<IP_ADDRESS>:45102 wire_version=2.1.0 daemon_version=0.1.0 environment=Test peer_id=Some(12D3KooWE2ond2RuV7xb16E7NwmABUx6McmuvSXWVZefWveZpC5P)
2022-08-01T12:33:26.784219Z TRACE Handle SendHeartbeat: wire: Sending taker_id=98bfe1af2c3dae9187c47f7ded06428c334924a61518bf78a17cf6077224ba14 msg_name="MakerToTaker::Heartbeat"
2022-08-01T12:33:26.784954Z TRACE Handle TakerConnected:Handle TakerMessage: wire: Sending taker_id=98bfe1af2c3dae9187c47f7ded06428c334924a61518bf78a17cf6077224ba14 msg_name="MakerToTaker::CurrentOffers"
2022-08-01T12:33:26.790300Z  INFO connect:Handle Connect: daemon::connection: Received Hello message from maker maker_identity=11ad505a586a5f4d64ed3164589e3adc206f5dd4434cab7f8a668ef2ac481221 actual_version=2.1.0
2022-08-01T12:33:26.790451Z  INFO connect:Handle Connect: daemon::connection: Established connection to maker address=<IP_ADDRESS>:41673
2022-08-01T12:33:26.796300Z TRACE Forward MakerStreamMessage:Handle MakerStreamMessage: wire: Received msg_name="MakerToTaker::Heartbeat"
2022-08-01T12:33:26.796710Z TRACE Forward MakerStreamMessage:Handle MakerStreamMessage: wire: Received msg_name="MakerToTaker::CurrentOffers"
2022-08-01T12:33:26.799617Z  INFO Handle NewConnection: xtra_libp2p::endpoint: Connection established peer=12D3KooWE2ond2RuV7xb16E7NwmABUx6McmuvSXWVZefWveZpC5P
2022-08-01T12:33:26.804075Z  INFO Start dialer actor:Handle Dial:dial:connect:Handle Connect:Dial new connection:Handle NewConnection: xtra_libp2p::endpoint: Connection established peer=12D3KooWRyHFsHo72WWsFqBkeN1m1R9CvWPApu9dEwmMqVdXEyk1
2022-08-01T12:33:26.807373Z DEBUG Start dialer actor:Handle Dial:dial:connect:Handle Connect:Dial new connection:Handle NewConnection:Handle endpoint :: ConnectionEstablished: daemon::online_status: Adding newly established connection to online_status: PeerId("12D3KooWRyHFsHo72WWsFqBkeN1m1R9CvWPApu9dEwmMqVdXEyk1")
2022-08-01T12:33:26.859714Z  INFO Handle IdentifyMsgReceived: daemon::identify::dialer: New identify message received peer_id=12D3KooWE2ond2RuV7xb16E7NwmABUx6McmuvSXWVZefWveZpC5P daemon_version=0.1.0 environment=Test wire_version=0.3.0
2022-08-01T12:33:26.905144Z  INFO Handle IdentifyMsgReceived: daemon::identify::dialer: New identify message received peer_id=12D3KooWRyHFsHo72WWsFqBkeN1m1R9CvWPApu9dEwmMqVdXEyk1 daemon_version=0.1.0 environment=Unknown wire_version=0.3.0
2022-08-01T12:33:26.907114Z TRACE given_rollover_when_oracle_attests_long_liquidation_price_can_liquidate:Handle OfferParams:Handle BroadcastOffers:Broadcast offers to taker: wire: Sending taker_id=98bfe1af2c3dae9187c47f7ded06428c334924a61518bf78a17cf6077224ba14 msg_name="MakerToTaker::CurrentOffers"
2022-08-01T12:33:26.911344Z TRACE Forward MakerStreamMessage:Handle MakerStreamMessage: wire: Received msg_name="MakerToTaker::CurrentOffers"
2022-08-01T12:33:26.951925Z  INFO daemon::order::taker: Placing order order=PlaceOrder { id: OrderId(0695310d-3c2e-4ef6-a7ab-048812029579), offer: Offer { id: OrderId(0a91af5e-cb56-496d-ab93-2cb228b3be88), trading_pair: BtcUsd, position_maker: Short, price: Price(394096), min_quantity: Usd(100), max_quantity: Usd(1000), leverage_taker: Leverage(2), leverage_choices: [Leverage(2)], creation_timestamp_maker: Timestamp(1659357206), settlement_interval: Duration { seconds: 86400, nanoseconds: 0 }, origin: Theirs, oracle_event_id: BitMexPriceEventId { timestamp: OffsetDateTime { utc_datetime: PrimitiveDateTime { date: Date { year: 2022, ordinal: 214 }, time: Time { hour: 13, minute: 0, second: 0, nanosecond: 0 } }, offset: UtcOffset { hours: 0, minutes: 0, seconds: 0 } }, digits: 20 }, tx_fee_rate: TxFeeRate(1), funding_rate: FundingRate(0.00024), opening_fee: OpeningFee { fee: Amount(0.00000002 BTC) } }, quantity: Usd(100), leverage: Leverage(2), maker_peer_id: PeerId("12D3KooWRyHFsHo72WWsFqBkeN1m1R9CvWPApu9dEwmMqVdXEyk1"), maker_identity: Identity(PublicKey(MontgomeryPoint([17, 173, 80, 90, 88, 106, 95, 77, 100, 237, 49, 100, 88, 158, 58, 220, 32, 111, 93, 212, 67, 76, 171, 127, 138, 102, 142, 242, 172, 72, 18, 33]))) }
2022-08-01T12:33:26.985964Z  INFO Register new inbound substream{substream=NewInboundSubstream { peer: PeerId("12D3KooWE2ond2RuV7xb16E7NwmABUx6McmuvSXWVZefWveZpC5P"), stream: Substream { inner: Negotiated { state: Completed { io: Stream { id: 3, connection: b168fa15 } } } } }}:Handle NewInboundSubstream: daemon::order::maker: Taker wants to place an order taker=12D3KooWE2ond2RuV7xb16E7NwmABUx6McmuvSXWVZefWveZpC5P quantity=100 order_id=0695310d-3c2e-4ef6-a7ab-048812029579
2022-08-01T12:33:27.014527Z DEBUG given_rollover_when_oracle_attests_long_liquidation_price_can_liquidate:Handle AcceptOrder:Handle Decision: daemon::order::maker: Instructed to Accept order 0695310d-3c2e-4ef6-a7ab-048812029579
2022-08-01T12:33:27.014782Z  INFO daemon::order::maker: Order accepted taker=12D3KooWE2ond2RuV7xb16E7NwmABUx6McmuvSXWVZefWveZpC5P quantity=100 order_id=0695310d-3c2e-4ef6-a7ab-048812029579
2022-08-01T12:33:27.016040Z  INFO daemon::order::taker: Order accepted order_id=0695310d-3c2e-4ef6-a7ab-048812029579 maker_peer_id=12D3KooWRyHFsHo72WWsFqBkeN1m1R9CvWPApu9dEwmMqVdXEyk1
2022-08-01T12:33:27.049775Z DEBUG Setup contract: daemon::setup_contract: setup_params=SetupParams { margin: Amount(0.00025375 BTC), counterparty_margin: Amount(0.00012687 BTC), counterparty_identity: Identity(PublicKey(MontgomeryPoint([104, 101, 108, 108, 111, 32, 119, 111, 114, 108, 100, 44, 32, 111, 104, 32, 119, 104, 97, 116, 32, 97, 32, 98, 101, 97, 117, 116, 105, 102, 117, 108]))), price: Price(394096), quantity: Usd(100), long_leverage: Leverage(2), short_leverage: Leverage(1), refund_timelock: 216, tx_fee_rate: TxFeeRate(1), fee_account: FeeAccount { balance: SignedAmount(-0.00000009 BTC), position: Short, role: Maker } } role=Maker position=Short n_payouts=200
2022-08-01T12:33:27.131288Z DEBUG Setup contract: daemon::setup_contract: setup_params=SetupParams { margin: Amount(0.00012687 BTC), counterparty_margin: Amount(0.00025375 BTC), counterparty_identity: Identity(PublicKey(MontgomeryPoint([17, 173, 80, 90, 88, 106, 95, 77, 100, 237, 49, 100, 88, 158, 58, 220, 32, 111, 93, 212, 67, 76, 171, 127, 138, 102, 142, 242, 172, 72, 18, 33]))), price: Price(394096), quantity: Usd(100), long_leverage: Leverage(2), short_leverage: Leverage(1), refund_timelock: 216, tx_fee_rate: TxFeeRate(1), fee_account: FeeAccount { balance: SignedAmount(0.00000009 BTC), position: Long, role: Taker } } role=Taker position=Long n_payouts=200
2022-08-01T12:33:27.207427Z  INFO Setup contract: daemon::setup_contract: Exchanged setup parameters
2022-08-01T12:33:27.277790Z  INFO Setup contract: daemon::setup_contract: Exchanged setup parameters
2022-08-01T12:33:31.788961Z TRACE Handle SendHeartbeat: wire: Sending taker_id=98bfe1af2c3dae9187c47f7ded06428c334924a61518bf78a17cf6077224ba14 msg_name="MakerToTaker::Heartbeat"
2022-08-01T12:33:31.791090Z TRACE Forward MakerStreamMessage:Handle MakerStreamMessage: wire: Received msg_name="MakerToTaker::Heartbeat"
2022-08-01T12:33:36.791383Z TRACE Handle SendHeartbeat: wire: Sending taker_id=98bfe1af2c3dae9187c47f7ded06428c334924a61518bf78a17cf6077224ba14 msg_name="MakerToTaker::Heartbeat"
2022-08-01T12:33:36.793192Z TRACE Forward MakerStreamMessage:Handle MakerStreamMessage: wire: Received msg_name="MakerToTaker::Heartbeat"
2022-08-01T12:33:36.894416Z  INFO Setup contract: daemon::setup_contract: Created CFD transactions
2022-08-01T12:33:37.346299Z  INFO Setup contract: daemon::setup_contract: Created CFD transactions
2022-08-01T12:33:51.670651Z  INFO Setup contract: daemon::setup_contract: Exchanged CFD transactions
2022-08-01T12:34:10.451381Z  INFO Setup contract: daemon::setup_contract: Exchanged CFD transactions
2022-08-01T12:34:10.470615Z TRACE Handle SendHeartbeat: wire: Sending taker_id=98bfe1af2c3dae9187c47f7ded06428c334924a61518bf78a17cf6077224ba14 msg_name="MakerToTaker::Heartbeat"
2022-08-01T12:34:10.473807Z TRACE Forward MakerStreamMessage:Handle MakerStreamMessage: wire: Received msg_name="MakerToTaker::Heartbeat"
2022-08-01T12:34:15.473556Z TRACE Handle SendHeartbeat: wire: Sending taker_id=98bfe1af2c3dae9187c47f7ded06428c334924a61518bf78a17cf6077224ba14 msg_name="MakerToTaker::Heartbeat"
2022-08-01T12:34:15.475264Z TRACE Forward MakerStreamMessage:Handle MakerStreamMessage: wire: Received msg_name="MakerToTaker::Heartbeat"
2022-08-01T12:34:20.476044Z TRACE Handle SendHeartbeat: wire: Sending taker_id=98bfe1af2c3dae9187c47f7ded06428c334924a61518bf78a17cf6077224ba14 msg_name="MakerToTaker::Heartbeat"
2022-08-01T12:34:20.477294Z TRACE Forward MakerStreamMessage:Handle MakerStreamMessage: wire: Received msg_name="MakerToTaker::Heartbeat"
2022-08-01T12:34:25.478042Z TRACE Handle SendHeartbeat: wire: Sending taker_id=98bfe1af2c3dae9187c47f7ded06428c334924a61518bf78a17cf6077224ba14 msg_name="MakerToTaker::Heartbeat"
2022-08-01T12:34:25.479503Z TRACE Forward MakerStreamMessage:Handle MakerStreamMessage: wire: Received msg_name="MakerToTaker::Heartbeat"
test given_rollover_when_oracle_attests_long_liquidation_price_can_liquidate has been running for over 60 seconds
2022-08-01T12:34:26.181055Z  INFO Setup contract: daemon::setup_contract: Verified all signatures
2022-08-01T12:34:26.321390Z  INFO Setup contract: daemon::setup_contract: Verified all signatures
2022-08-01T12:34:26.324338Z  INFO Setup contract: daemon::setup_contract: Exchanged signed lock transaction
2022-08-01T12:34:26.379857Z  INFO Setup contract: daemon::setup_contract: Exchanged signed lock transaction
2022-08-01T12:34:28.635311Z  INFO model::cfd: Contract setup was completed order_id=0695310d-3c2e-4ef6-a7ab-048812029579
2022-08-01T12:34:29.027184Z  INFO model::cfd: Contract setup was completed order_id=0695310d-3c2e-4ef6-a7ab-048812029579
2022-08-01T12:34:30.545696Z TRACE Handle SendHeartbeat: wire: Sending taker_id=98bfe1af2c3dae9187c47f7ded06428c334924a61518bf78a17cf6077224ba14 msg_name="MakerToTaker::Heartbeat"
2022-08-01T12:34:30.549829Z TRACE Forward MakerStreamMessage:Handle MakerStreamMessage: wire: Received msg_name="MakerToTaker::Heartbeat"
2022-08-01T12:34:31.001906Z DEBUG maker::connection: Connection got dropped taker_id=98bfe1af2c3dae9187c47f7ded06428c334924a61518bf78a17cf6077224ba14
test given_rollover_when_oracle_attests_long_liquidation_price_can_liquidate ... FAILED

failures:

failures:
    given_rollover_when_oracle_attests_long_liquidation_price_can_liquidate

test result: FAILED. 0 passed; 1 failed; 0 ignored; 0 measured; 1 filtered out; finished in 65.26s

--- TRY 3 STDERR:                         daemon-tests::liquidation given_rollover_when_oracle_attests_long_liquidation_price_can_liquidate ---
thread 'given_rollover_when_oracle_attests_long_liquidation_price_can_liquidate' panicked at 'called `Option::unwrap()` on a `None` value', daemon-tests/tests/liquidation.rs:92:10
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

I am a bit confused by
panicked at 'called `Option::unwrap()` on a `None` value'

because I don't think that we might have just run into a timeout?
Maybe you can have a look @luckysori

The unwrap is
    let attestation = oracle_data_rollover
        .attestation_for_event(first_liquidation_event)
        .unwrap();

So I guess there's no attestation at that point ?

Yeah, that is where it panics and you are right that this must be the problem!
I thought we would also see the panic in the test logs but since it panics in the test code this is expected behavior.
It appears that there is no attestation for the given first event. This is odd because the event is fixed, I would not know how this can fail. I think the problem might be that we are not awaiting the DLC to actually change, so the latest_dlc might still be the previous one.

Happens to me sometimes locally too :/
protip: cargo nextest run --retries=1 typically solves the problem on local machine, it will re-run flaky tests once :)


OCI-CommitmentDiscountCategory

Not applicable.
Comment:

The OCI Universal Credit annual commitment model typically involves a discretionary discount percentage, categorized as a negotiated discount rather than a commitment-based discount.


Expand/collapse icon show condition

I would like to have some external way to change the condition at which the expand/collapse icon is shown, and maybe this is useful for the library as well.
The current renderTreeDataColumn in the MTableBodyRow class component has the static condition:
 (props.data.tableData.childRows &&       props.data.tableData.childRows.length > 0)
This static condition may be not be satisfied if the childRows that I want to show on collapsing icon need to be fetched and reallocated in the table following the parentChildData criteria.
Another cool thing may be the action dispatched when clicking the expand/collapse icon, which at current version is static.
onClick={(event) => {   props.onTreeExpandChanged(props.path, props.data);   event.stopPropagation(); }}
I hope I was clear here.
And sorry for possible english mistakes.

I would like to implement this if i'm allowed to make a PR

Of course you can make a PR!!!

I made the PR


Have a way to add to existing quantity if item exist

if an item has the same name and same value, we can add it to the quantity instead of creating a new item

probably should be the default without option to opt out

implemented in 0.7


fix: unable to build issues

Unable to build because it cannot compile Editor codes

This has already been resolved


Bouncy dev

Needs a new ros2 branch.

there is no CI solution in place for ros2 yet

I created a new branch bouncy_dev_ros2 and changed the target branch of this PR

How should we proceed CI-wise? Remove the Travis files for now and ask @ipa-mdl about ROS2 plans for industrial-ci?

Yes, @ipa-jba I agree with that procedure regarding CI.

@ipa-jba what are we going to do with this pr?
is this still relevant? or should it be adjusted to dashing?

ROS2 support in CI (beta): https://github.com/ros-industrial/industrial_ci/pull/361

works on my machine now (dashing). Is there some instruction/example on how to use industrial-ci for dashing?

Is there some instruction/example on how to use industrial-ci for dashing?

https://github.com/ros-industrial/industrial_ci/tree/master#for-travis-ci with ROS_DISTRO=dashing
I will announce it soon.

https://github.com/ros-industrial/industrial_ci/tree/master#for-travis-ci with ROS_DISTRO=dashing
I will announce it soon.

:+1: I thougt there might be more "getting into the hidden expert ros2 mode.." involved

not planned - use foxy branch - is released to humble


[Input] Add connected input fields

Hello,
Like a label or action attached to an input I would like inputs attached to other inputs or inputs with a label in between and attached to each other.
Here's a small example of what I mean https://codepen.io/Traverse/pen/JNaYyZ
I would love some feedback because my example was put together in a short amount of time so I'm sure there's a better way to do this.

This is something I've been missing desperately in Semantic-UI. To me, it feels natural to include this option the same way as it is done for buttons.


readFrame :: using string as column data type

(How) is it currently possible to load a dataframe with string as column type?
According to https://daphne-eu.github.io/daphne/FileMetaDataFormat/, there is only numeric data possible?
can we have support for valueType: string?
data.csv
Algiers,3.4
St. John's,4.3
Dodoma,26.3
Toliara,17.0
Yellowknife,4.0
Batumi,24.5
Istanbul,31.9
Tampa,41.6
Gjoa Haven,-1.3
Paris,18.2

data.csv.meta
{
  "numRows": 10,
  "numCols": 2,
  "schema": [
    {
      "label": "city",
      "valueType": "string"
    },
    {
      "label": "temperature",
      "valueType": "f64"
    }
  ]
}

daphne script:
path = "data.csv";
data = readFrame(path);
print(data);

Hi @auge, it is currently not possible to read string data from files, but this feature is already WIP and will be added soon.
PR #797, which is about to be finalized and merged, will bring support for reading CSV files into matrices of string value type. These matrices (or individual columns) can then be processed with some basic string operations (e.g., concatenation, lower/upper case) or converted to numerical data (e.g., through number parsing, dictionary coding, or one-hot encoding).
As a follow-up, we're already working on support for frames with string columns and reading CSV files with string columns into a frame directly.
In the meantime, a work-around can be to convert the string data to numbers with some external tool/script (e.g., through dictionary coding) and to read just the numerical data into DAPHNE.

This issue is closed now. In the meta data file, one has to specify "valueType": "str" for string columns. The documentation will be updated shortly.


Burundi localization follow ups

Follows up https://github.com/TIP-Global-Health/eheza-app/issues/798

Ubudehe:

Resilience kick off survey - ubudehe question for Nurse.
Mother Fbf - logic for distribution (ubudehe 1 or 2 receive Fbf, others do not).

Wording at Translate.elm (specific mentions of Rwanda):

@adamhstewart please advice how these should be handled.

English translations:

Remove the second sentence of the Rotavirus vaccine to eliminate specific reference to Rwanda
Change Covid question to remove "in Rwanda"
Stock supplier values: we need to be able to make the suppliers list configurable by an admin. We will (eventually) also need this for some other functionalities as well (for example, lists of medications, which may be different in different countries. Out of scope for this issue, but in a new issue we should consider:

A backend admin section for custom select lists
A way to integrate that wire that to the frontend question.

Overall this last issue is not a blocker for creating and releasing multisite capability because these sections will not be used by test audience in Burundi.

@adamhstewart

we need to be able to make the suppliers list configurable by an admin. We will (eventually) also need this for some other functionalities as well (for example, lists of medications, which may be different in different countries. Out of scope for this issue, but in a new issue we should consider:

A backend admin section for custom select lists
A way to integrate that wire that to the frontend question.

Well, supporting such type of configuration at the App seems to me as a pandora box we better not open.
Considering suppliers list configurable, we'll need to  resolve several issues, which don't have easy solutions.
Main issue:

How do we configure the content type to be able to store these configured values.
We could take an approach where we define generic options for response (ans1, ans2, ..., ans10), and then the configuration that is sent, only specifies the labels for the options (note that these need to be translated to all languages), but then, if configuration changes over time, it will be hard to know what ansX was representing at the time it was set.

If we consider making medicine configurable, it's even more problematic, as it's not only medication name, but also all kind of instructions that come with it and shown on form.
So, as I see it, best approach is to expand medication set, and suggest medication based on current site.
Besides, it's very likely that prescription logic will need changing, so there's no way to avoid adding code to support it.
Therefore, I think we should be handling such change requests by developing small releases with needed changes. Don't think it will be required too often.
//cc @amitaibu

These were confirmed in QA for https://github.com/TIP-Global-Health/eheza-app/issues/798


Feature Request/Bugfix: Icon Folder compatibility

Using Obsidian Icon Folder doesn't replace the existing icon but adds addition icon next to folders/files. I realize there is an option to disable the default icons, but it would be nice to have both default set and additional icons for special items.

Hi! Obsidian Icon Folder being a plugin, it adds a custom class in order to place an icon before any folder. This method is not possible in native obsidian, hence why I use a different CSS trick to achieve the same result.
If you're hoping for more compatibility besides my Style Settings option to disable icons, I'd advise you to submit a feature request on Obsidian Icon Folder's repository. Sanctum being a simple theme, there's only so much one can achieve with CSS only, and plugins having quite a bit more options, it might be possible for the developer to disable ::before CSS pseudo-elements of a specific folder, if that folder has a custom icon. Hope that makes sense!
Having said this, although I can't do much on my end regarding the theme, there are ways you can target specific icons with CSS snippets, in case you have the patience for it. Here's an example CSS snippet that should work:
.nav-folder-title[data-path='FOLDER-NAME'] .nav-folder-title-content::before {
	display: none;
}

Again, if you're hoping for a more user-friendly or streamlined way, the only option I see is through the plugin itself.


[fuchsia_ctl] Add pre-submit testing

To improve the stability of fuchsia_ctl, we plan to add pre-submit testing. We will add a new recipe that builds and uploads fuchsia_ctl CIPD package (without tagging), then triggers the Linux Fuchsia builder to run with the new version of fuchsia_ctl CIPD package.
This is a sub task of FlutterFuchsiaImprovements.

The next step is adding a webhook (https://flutter-dashboard.appspot.com/api/github-webhook-pullrequest) to the https://github.com/flutter/packages repo.
@godofredoc can you help with that? I don't have the permission.

I don't have permissions to that repo we'll need to ask @kf6gpe for help.

@kf6gpe Hi Ray, could you help us add a webhook (https://flutter-dashboard.appspot.com/api/github-webhook-pullrequest) to the https://github.com/flutter/packages repo?

Ray helped us to update the webhook yesterday.

A successful run end to end: https://ci.chromium.org/p/flutter/builders/try/fuchsia_ctl/4


InfluxDB - Admin Interface advertising InfluxDB v0.9.3

I have a nightly 0.9.5 installed. Is this by design or just a mere oversight.
Also, Admin Interface is using Bootstrap v3.3.4 while Bootstrap v3.3.5 is already available since June.

It's an oversight. The version string will be updated by PR https://github.com/influxdb/influxdb/pull/4776.
The bootstrap version still needs to be updated so leaving this issue open for now.

Would you be ok with a pull request. I can help with the Admin UI. There are a few things that can be improved.

Absolutely. See your name in the CHANGELOG!
Larger changes should be discussed on a ticket first.
On Friday, November 13, 2015, Ionel Roiban<EMAIL_ADDRESS>wrote:

Would you be ok with a pull request. I can help with the Admin UI. There
are a few things that can be improved.
—
Reply to this email directly or view it on GitHub
https://github.com/influxdb/influxdb/issues/4780#issuecomment-156451434.


[Release] post-05-js.sh is not publishing JS packages for 13.0.0

Describe the bug, including details regarding any error messages, version, and platform.
After executing:
dev/release/post-05-js.sh 13.0.0

I can see that no packages are being published:
[13:07:24] Finished 'test' after 8.18 min
[13:07:24] Finished 'default' after 9.13 min
Done in 548.93s.
yarn run v1.22.19
$ lerna exec --concurrency 1 --no-bail 'npm publish'
lerna notice cli v7.0.0
lerna info Executing command in 0 packages: "npm publish"
lerna success exec Executed command in 0 packages: "npm publish"
Done in 0.99s.
~/code/arrow
Success! The released npm packages are available here:
  https://www.npmjs.com/package/apache-arrow/v/13.0.0

The full log:
$ dev/release/post-05-js.sh 13.0.0
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 19.5M  100 19.5M    0     0  6774k      0  0:00:02  0:00:02 --:--:-- 6775k
~/code/arrow/apache-arrow-13.0.0/js ~/code/arrow
yarn install v1.22.19
[1/5] Validating package.json...
[2/5] Resolving packages...
[3/5] Fetching packages...
warning Pattern<EMAIL_ADDRESS>is trying to unpack in the same destination "/home/raulcd/.cache/yarn/v6/npm-wrap-ansi-cjs-7.0.0-67e145cff510a6a6984bdf1152911d69d2eb9e43-integrity/node_modules/wrap-ansi-cjs" as pattern ["wrap-ansi-cjs<EMAIL_ADDRESS>This could result in non-deterministic behavior, skipping.
[4/5] Linking dependencies...
[5/5] Building fresh packages...
Done in 3.19s.
yarn run v1.22.19
$ /home/raulcd/code/arrow/apache-arrow-13.0.0/js/node_modules/.bin/gulp
[12:58:16] Using gulpfile ~/code/arrow/apache-arrow-13.0.0/js/gulpfile.js
[12:58:16] Starting 'default'...
[12:58:16] Starting 'clean'...
[12:58:16] Starting 'clean:ts'...
[12:58:16] Starting 'clean:apache-arrow'...
[12:58:16] Starting 'clean:es5:cjs'...
[12:58:16] Starting 'clean:es2015:cjs'...
[12:58:16] Starting 'clean:esnext:cjs'...
[12:58:16] Starting 'clean:es5:esm'...
[12:58:16] Starting 'clean:es2015:esm'...
[12:58:16] Starting 'clean:esnext:esm'...
[12:58:16] Starting 'clean:es5:cls'...
[12:58:16] Starting 'clean:es2015:cls'...
[12:58:16] Starting 'clean:esnext:cls'...
[12:58:16] Starting 'clean:es5:umd'...
[12:58:16] Starting 'clean:es2015:umd'...
[12:58:16] Starting 'clean:esnext:umd'...
[12:58:16] Finished 'clean:ts' after 18 ms
[12:58:16] Finished 'clean:apache-arrow' after 19 ms
[12:58:16] Finished 'clean:es5:cjs' after 19 ms
[12:58:16] Finished 'clean:es2015:cjs' after 20 ms
[12:58:16] Finished 'clean:esnext:cjs' after 20 ms
[12:58:16] Finished 'clean:es5:esm' after 20 ms
[12:58:16] Finished 'clean:es2015:esm' after 20 ms
[12:58:16] Finished 'clean:esnext:esm' after 21 ms
[12:58:16] Finished 'clean:es5:cls' after 21 ms
[12:58:16] Finished 'clean:es2015:cls' after 21 ms
[12:58:16] Finished 'clean:esnext:cls' after 22 ms
[12:58:16] Finished 'clean:es5:umd' after 22 ms
[12:58:16] Finished 'clean:es2015:umd' after 22 ms
[12:58:16] Finished 'clean:esnext:umd' after 22 ms
[12:58:16] Finished 'clean' after 24 ms
[12:58:16] Starting 'build'...
[12:58:16] Starting 'build:ts'...
[12:58:16] Starting 'build:apache-arrow'...
[12:58:16] Starting 'build:es5:cjs'...
[12:58:16] Starting 'build:es2015:cjs'...
[12:58:16] Starting 'build:esnext:cjs'...
[12:58:16] Starting 'build:es5:esm'...
[12:58:16] Starting 'build:es2015:esm'...
[12:58:16] Starting 'build:esnext:esm'...
[12:58:16] Starting 'clean:ts'...
[12:58:16] Starting 'clean:es5:cjs'...
[12:58:16] Starting 'clean:es2015:cjs'...
[12:58:16] Starting 'clean:esnext:cjs'...
[12:58:16] Starting 'clean:es5:esm'...
[12:58:16] Starting 'clean:es2015:esm'...
[12:58:16] Starting 'clean:esnext:esm'...
[12:58:16] Starting 'build:es2015:umd'...
[12:58:16] Starting 'build:es2015:cjs'...
[12:58:16] Starting 'build:es2015:esm'...
[12:58:16] Starting 'build:esnext:umd'...
[12:58:16] Starting 'build:es2015:cls'...
[12:58:16] Starting 'clean:es2015:cjs'...
[12:58:16] Starting 'clean:es2015:esm'...
[12:58:16] Starting 'build:esnext:cls'...
[12:58:16] Starting 'clean:es2015:cls'...
[12:58:16] Starting 'clean:esnext:cls'...
[12:58:16] Finished 'clean:ts' after 1.48 ms
[12:58:16] Starting 'compile:ts'...
[12:58:16] Finished 'clean:es5:cjs' after 1.49 ms
[12:58:16] Starting 'compile:es5:cjs'...
[12:58:16] Finished 'clean:es2015:cjs' after 1.46 ms
[12:58:16] Starting 'compile:es2015:cjs'...
[12:58:16] Finished 'clean:esnext:cjs' after 1.46 ms
[12:58:16] Starting 'compile:esnext:cjs'...
[12:58:16] Finished 'clean:es5:esm' after 1.47 ms
[12:58:16] Starting 'compile:es5:esm'...
[12:58:16] Finished 'clean:es2015:esm' after 1.49 ms
[12:58:16] Starting 'compile:es2015:esm'...
[12:58:16] Finished 'clean:esnext:esm' after 1.56 ms
[12:58:16] Starting 'compile:esnext:esm'...
[12:58:16] Finished 'clean:es2015:cjs' after 1.15 ms
[12:58:16] Starting 'compile:es2015:cjs'...
[12:58:16] Finished 'clean:es2015:esm' after 1.17 ms
[12:58:16] Starting 'compile:es2015:esm'...
[12:58:16] Finished 'clean:es2015:cls' after 1.14 ms
[12:58:16] Starting 'compile:es2015:cls'...
[12:58:16] Finished 'clean:esnext:cls' after 1.11 ms
[12:58:16] Starting 'compile:esnext:cls'...
[12:58:16] Finished 'compile:ts' after 255 ms
[12:58:16] Starting 'package:ts'...
[12:58:16] Finished 'package:ts' after 14 ms
[12:58:16] Finished 'build:ts' after 271 ms
[12:58:16] Starting 'build:es5:cls'...
[12:58:16] Starting 'clean:es5:cls'...
[12:58:16] Finished 'clean:es5:cls' after 168 μs
[12:58:16] Starting 'compile:es5:cls'...
[12:58:51] Finished 'compile:es2015:cls' after 35 s
[12:58:51] Starting 'package:es2015:cls'...
[12:58:51] Finished 'package:es2015:cls' after 41 ms
[12:58:51] Finished 'build:es2015:cls' after 35 s
[12:58:51] Starting 'clean:es2015:umd'...
[12:58:51] Finished 'clean:es2015:umd' after 604 μs
[12:58:51] Starting 'compile:es2015:umd'...
[12:58:52] Finished 'compile:esnext:cls' after 37 s
[12:58:52] Starting 'package:esnext:cls'...
[12:58:53] Finished 'package:esnext:cls' after 56 ms
[12:58:53] Finished 'build:esnext:cls' after 37 s
[12:58:53] Starting 'clean:esnext:umd'...
[12:58:53] Finished 'clean:esnext:umd' after 564 μs
[12:58:53] Starting 'compile:esnext:umd'...
[12:58:53] Finished 'compile:es2015:esm' after 37 s
[12:58:53] Starting 'package:es2015:esm'...
[12:58:53] Finished 'compile:es2015:esm' after 37 s
[12:58:53] Starting 'package:es2015:esm'...
[12:58:53] Finished 'package:es2015:esm' after 70 ms
[12:58:53] Finished 'build:es2015:esm' after 37 s
[12:58:53] Starting 'build:es2015:cls'...
[12:58:53] Finished 'package:es2015:esm' after 70 ms
[12:58:53] Finished 'build:es2015:esm' after 37 s
[12:58:53] Starting 'clean:es2015:cls'...
[12:58:53] Finished 'clean:es2015:cls' after 410 μs
[12:58:53] Starting 'compile:es2015:cls'...
[12:58:53] Finished 'compile:es2015:cls' after 233 μs
[12:58:53] Starting 'package:es2015:cls'...
[12:58:53] Finished 'package:es2015:cls' after 279 μs
[12:58:53] Finished 'build:es2015:cls' after 1.97 ms
[12:58:53] Starting 'build:esnext:cls'...
[12:58:53] Starting 'clean:esnext:cls'...
[12:58:53] Finished 'clean:esnext:cls' after 259 μs
[12:58:53] Starting 'compile:esnext:cls'...
[12:58:53] Finished 'compile:esnext:cls' after 225 μs
[12:58:53] Starting 'package:esnext:cls'...
[12:58:53] Finished 'package:esnext:cls' after 229 μs
[12:58:53] Finished 'build:esnext:cls' after 1.53 ms
[12:58:53] Starting 'build:es5:umd'...
[12:58:53] Starting 'build:es5:cls'...
[12:58:53] Starting 'clean:es5:cls'...
[12:58:53] Finished 'clean:es5:cls' after 219 μs
[12:58:53] Starting 'compile:es5:cls'...
[12:58:54] Finished 'compile:es5:cls' after 38 s
[12:58:54] Starting 'package:es5:cls'...
[12:58:54] Finished 'compile:es5:cls' after 499 ms
[12:58:54] Starting 'package:es5:cls'...
[12:58:54] Finished 'package:es5:cls' after 24 ms
[12:58:54] Finished 'build:es5:cls' after 38 s
[12:58:54] Starting 'build:es2015:umd'...
[12:58:54] Finished 'package:es5:cls' after 25 ms
[12:58:54] Finished 'build:es5:cls' after 525 ms
[12:58:54] Starting 'clean:es5:umd'...
[12:58:54] Starting 'build:es2015:cls'...
[12:58:54] Starting 'clean:es2015:cls'...
[12:58:54] Finished 'clean:es5:umd' after 1.21 ms
[12:58:54] Starting 'compile:es5:umd'...
[12:58:54] Finished 'clean:es2015:cls' after 668 μs
[12:58:54] Starting 'compile:es2015:cls'...
[12:58:54] Finished 'compile:es2015:cls' after 24 ms
[12:58:54] Starting 'package:es2015:cls'...
[12:58:54] Finished 'package:es2015:cls' after 438 μs
[12:58:54] Finished 'build:es2015:cls' after 26 ms
[12:58:54] Starting 'clean:es2015:umd'...
[12:58:54] Finished 'clean:es2015:umd' after 401 μs
[12:58:54] Starting 'compile:es2015:umd'...
[12:58:54] Finished 'compile:es5:esm' after 38 s
[12:58:54] Starting 'package:es5:esm'...
[12:58:54] Finished 'package:es5:esm' after 18 ms
[12:58:54] Finished 'build:es5:esm' after 38 s
[12:58:54] Starting 'build:esnext:umd'...
[12:58:54] Starting 'build:esnext:cls'...
[12:58:54] Starting 'clean:esnext:cls'...
[12:58:54] Finished 'clean:esnext:cls' after 376 μs
[12:58:54] Starting 'compile:esnext:cls'...
[12:58:54] Finished 'compile:esnext:cls' after 332 μs
[12:58:54] Starting 'package:esnext:cls'...
[12:58:54] Finished 'package:esnext:cls' after 316 μs
[12:58:54] Finished 'build:esnext:cls' after 3.78 ms
[12:58:54] Starting 'clean:esnext:umd'...
[12:58:54] Finished 'clean:esnext:umd' after 349 μs
[12:58:54] Starting 'compile:esnext:umd'...
[12:58:55] Finished 'compile:es5:cjs' after 39 s
[12:58:55] Starting 'package:es5:cjs'...
[12:58:55] Finished 'package:es5:cjs' after 16 ms
[12:58:55] Finished 'build:es5:cjs' after 39 s
[12:58:55] Finished 'compile:es2015:cjs' after 39 s
[12:58:55] Starting 'package:es2015:cjs'...
[12:58:55] Finished 'compile:es2015:cjs' after 39 s
[12:58:55] Starting 'package:es2015:cjs'...
[12:58:55] Finished 'package:es2015:cjs' after 14 ms
[12:58:55] Finished 'build:es2015:cjs' after 39 s
[12:58:55] Finished 'package:es2015:cjs' after 14 ms
[12:58:55] Finished 'build:es2015:cjs' after 39 s
[12:58:55] Finished 'compile:esnext:cjs' after 39 s
[12:58:55] Starting 'package:esnext:cjs'...
[12:58:55] Finished 'package:esnext:cjs' after 21 ms
[12:58:55] Finished 'build:esnext:cjs' after 39 s
[12:58:55] Finished 'compile:esnext:esm' after 39 s
[12:58:55] Starting 'package:esnext:esm'...
[12:58:55] Finished 'package:esnext:esm' after 23 ms
[12:58:55] Finished 'build:esnext:esm' after 39 s
[12:59:10] Finished 'compile:es2015:umd' after 19 s
[12:59:10] Starting 'package:es2015:umd'...
[12:59:10] Finished 'compile:es2015:umd' after 16 s
[12:59:10] Starting 'package:es2015:umd'...
[12:59:10] Finished 'package:es2015:umd' after 9.78 ms
[12:59:10] Starting 'remove_closure_tmp_files'...
[12:59:10] Finished 'package:es2015:umd' after 9.84 ms
[12:59:10] Starting 'remove_closure_tmp_files'...
[12:59:10] Finished 'remove_closure_tmp_files' after 42 ms
[12:59:10] Finished 'build:es2015:umd' after 54 s
[12:59:10] Finished 'remove_closure_tmp_files' after 42 ms
[12:59:10] Finished 'build:es2015:umd' after 16 s
[12:59:10] Finished 'compile:esnext:umd' after 18 s
[12:59:10] Starting 'package:esnext:umd'...
[12:59:10] Finished 'compile:esnext:umd' after 16 s
[12:59:10] Starting 'package:esnext:umd'...
[12:59:10] Finished 'package:esnext:umd' after 8.46 ms
[12:59:10] Starting 'remove_closure_tmp_files'...
[12:59:10] Finished 'package:esnext:umd' after 8.49 ms
[12:59:10] Starting 'remove_closure_tmp_files'...
[12:59:10] Finished 'remove_closure_tmp_files' after 33 ms
[12:59:10] Finished 'build:esnext:umd' after 16 s
[12:59:10] Finished 'remove_closure_tmp_files' after 33 ms
[12:59:10] Finished 'build:esnext:umd' after 54 s
[12:59:10] Starting 'clean:apache-arrow'...
[12:59:10] Finished 'clean:apache-arrow' after 157 μs
[12:59:10] Starting 'compile:apache-arrow'...
[12:59:11] Finished 'compile:apache-arrow' after 572 ms
[12:59:11] Starting 'package:apache-arrow'...
[12:59:11] Finished 'package:apache-arrow' after 5.79 ms
[12:59:11] Finished 'build:apache-arrow' after 55 s
[12:59:12] Finished 'compile:es5:umd' after 18 s
[12:59:12] Starting 'package:es5:umd'...
[12:59:12] Finished 'package:es5:umd' after 5.37 ms
[12:59:12] Starting 'remove_closure_tmp_files'...
[12:59:12] Finished 'remove_closure_tmp_files' after 11 ms
[12:59:12] Finished 'build:es5:umd' after 19 s
[12:59:12] Finished 'build' after 56 s
[12:59:12] Starting 'test'...
[12:59:12] Starting 'test:ts'...
[12:59:12] Starting 'test:src'...
[12:59:12] Starting 'test:apache-arrow'...
[12:59:12] Starting 'test:es5:cjs'...
[12:59:12] Starting 'test:es2015:cjs'...
[12:59:12] Starting 'test:esnext:cjs'...
[12:59:12] Starting 'test:es5:esm'...
[12:59:12] Starting 'test:es2015:esm'...
[13:04:00] Finished 'test:esnext:cjs' after 4.8 min
[13:04:00] Starting 'test:esnext:esm'...
[13:04:03] Finished 'test:es2015:cjs' after 4.83 min
[13:04:03] Starting 'test:es5:umd'...
[13:04:25] Finished 'test:es5:cjs' after 5.2 min
[13:04:25] Starting 'test:es2015:umd'...
[13:04:31] Finished 'test:apache-arrow' after 5.32 min
[13:04:31] Starting 'test:esnext:umd'...
[13:04:40] Finished 'test:es2015:esm' after 5.47 min
[13:04:54] Finished 'test:es5:esm' after 5.68 min
[13:04:55] Finished 'test:ts' after 5.7 min
[13:05:15] Finished 'test:src' after 6.05 min
[13:06:57] Finished 'test:es5:umd' after 2.9 min
[13:07:03] Finished 'test:esnext:umd' after 2.52 min
[13:07:05] Finished 'test:es2015:umd' after 2.67 min
[13:07:24] Finished 'test:esnext:esm' after 3.38 min
[13:07:24] Finished 'test' after 8.18 min
[13:07:24] Finished 'default' after 9.13 min
Done in 548.93s.
yarn run v1.22.19
$ lerna exec --concurrency 1 --no-bail 'npm publish'
lerna notice cli v7.0.0
lerna info Executing command in 0 packages: "npm publish"
lerna success exec Executed command in 0 packages: "npm publish"
Done in 0.99s.
~/code/arrow
Success! The released npm packages are available here:
  https://www.npmjs.com/package/apache-arrow/v/13.0.0

Component(s)
Release

@trxcllnt @domoritz @abetomo Could you take a look at this?
FYI: https://github.com/apache/arrow/blob/main/js/npm-release.sh is executed internally.

Seems like<EMAIL_ADDRESS>is broken. Downgrading to<EMAIL_ADDRESS>fixes it.

This is part of the pinned dependencies on the release, does that mean we should do a hotfix release for this? I can manually change the packages.json locally before publishing and execute the npm tasks. Those are a post-release task and not sure if they count as a deliverable for the release but I am not sure if we want to do that.

We don't need a hotfix release because NPM packages aren't the "official" releases. (We don't vote NPM packages.)
So we can release NPM packages with<EMAIL_ADDRESS>by changing packages.json locally.

I've published the npm packages modifying lerna locally to 6.6.2 (I also had to update yarn.lock): https://www.npmjs.com/package/apache-arrow/v/13.0.0
@trxcllnt should we change it back on main for the future? https://github.com/apache/arrow/blob/main/js/package.json#L102

We're looking into removing lerna entirely.

Will be done in https://github.com/apache/arrow/pull/37393.


Add support for providing a nonce when signing in with IdP credentials

Implements #654
:octocat:

TIL "nonce" 🧐


ARROW-2782: [Plasma] Fix huge pages Plasma test

If it works, this should replace https://github.com/apache/arrow/pull/2207

The test failed on Travis-CI with "object does not fit in the plasma store".

This test hasn't failed in a while. I'm going to close this PR for now and we can revisit if it comes up again


add support for button entities

title says it all really :)
i use a lot of button entities to trigger stuff, would be awesome if i could press them on my watch!

Hi @Nattfisk,
I added that already to this PR https://github.com/smirko-dev/fitbit-homeassistant/tree/feature/refactoring. Since my HA is not running it'll take some time to test and merge that.

Cool!
Thank you!


Problems with jQuery 3

What happend?
Please update the deprecated method calls.
e.g.
sample.load(fn()) to sample.on('load', fn())
How can we reproduce this bug?

Use Foundation 5 in a project via NodeJs
--> dependency in package.json: jQuery >= 2.x.x
----> jQuery 3.0.0 is installed (breaking changes)

What did you expect to happen?
Foundation should not throw any error. Please update the code so that it don't use deprecated  methods.
What happened instead?
Foundation throws error.
Thanks

This is also happening in Foundation 6.  Thanks!

Same thing happened to me. Update would be very nice :)

Further verification using https://github.com/jquery/jquery-migrate (sorry for the screen grab).

I am running into the same problem, does anyone from foundation team know the best way to solve this problem?

I guess this could be solved by adding a jQuery 3 Test, collect the JQMIGRATE Warnings and migrate/change the code step by step.

I got the problem with the deprecated load function in foundation.util.triggers.js, too. It would be really nice to have a fix here with the next version.
If you guys want to include a patch on your side you can change line 65 from:
$(window).load(function () {
to:
$(window).on('load', function () {
and the triggers util can be used until the fix is coming from Zurb :)

Just making some noise here. I have the same problem, inside init in foundation.ks:345, there is a call to .load that ends up here. Foundation 5.5.3, jQuery 3.1.0.
Hotfixing the file in bower_components in my project for now.

I am having the same issue when bootstrapping it to aurelia.  can we get these load(callback) changed to .on('load', callback)

should be fixed by https://github.com/zurb/foundation-sites/pull/8923

@tobias-kutter can you confirm this has been fixed?

it still occurs in Foundation 6 for site.

It's also not fixed in Foundation 5.5.3...

@max8hine what version are you using?

@Owlbertz I am using 6.2.3 i caught it from npm foundation-sites. and binding the main js file with jQuery 3 by using webpack. but i didn't do any testing on this error, but i found the error in Console  panel.

Same as @max8hine, tried to use jQuery 3.1 with Foundation (Sites) 6.2.2, which produces the following error:

I have the exact same problem.
Any thoughts to fix it?

This is fixed in 6.2.4, which will be released TOMORROW. :)

Do you also release a fixed version for Foundation 5? We don't migrate to 6 till now...

@kball is this really fixed with 6.2.4? Can´t find anything about this issue in the release notes
https://github.com/zurb/foundation-sites/releases/

@Baedda It should be. I just update the release notes highlighting this for the PR in question that fixed it.
We decided not to change the default to jQuery 3 until the minor release, but projects using 3 should now work.

It doesn't work with the latest jQuery 3.1.1 I made this pen to prove it.

@h0r0man you are using 6.2.3 in your pen. Changing it to 6.2.4 fixes the errors.

I noted that 6.3 still didn't bump to jQuery 3 yet. Was this delayed for some reason?

@memoht I think jQuery 3 is supported, but package was not changed. But minimum version should still be jQuery 2

After upgrading my test project to latest jquery
bower i --save jquery

and FS 6.3.0
bower i --save foundation-sites

verifying
bower list
    bower check-new     Checking for new versions of the project dependencies...
    test-site /srv/www/test
    ├── foundation-icon-fonts#afed003521
    ├─┬ foundation-sites#6.3.0
    │ ├── jquery#3.1.1 incompatible with ~2.2.0 (2.2.4 available, latest is 3.1.1)
    │ └── what-input#4.0.4
    └── jquery#3.1.1

updating the project still warns about "Code incompatibilities" re: jquery 3 "vs" FS6
bower update
    bower not-cached    https://github.com/zurb/foundation-icon-fonts.git#*
    bower resolve       https://github.com/zurb/foundation-icon-fonts.git#*
    bower cached        https://github.com/zurb/foundation-sites.git#6.3.0
    bower validate      6.3.0 against https://github.com/zurb/foundation-sites.git#^6.3.0
    bower cached        https://github.com/jquery/jquery-dist.git#3.1.1
    bower validate      3.1.1 against https://github.com/jquery/jquery-dist.git#^3.1.1
    bower download      https://github.com/zurb/foundation-icon-fonts/archive/master.tar.gz
    bower cached        https://github.com/jquery/jquery-dist.git#2.2.4
    bower validate      2.2.4 against https://github.com/jquery/jquery-dist.git#~2.2.0
    bower cached        https://github.com/ten1seven/what-input.git#4.0.4
    bower validate      4.0.4 against https://github.com/ten1seven/what-input.git#~4.0.3
    bower extract       foundation-icon-fonts#* archive.tar.gz
    bower resolved      https://github.com/zurb/foundation-icon-fonts.git#afed003521

    Please note that,
        foundation-sites#6.3.0 depends on jquery#~2.2.0 which resolved to jquery#2.2.4
        test-site depends on jquery#^3.1.1 which resolved to jquery#3.1.1
    Resort to using jquery#^3.1.1 which resolved to jquery#3.1.1
    Code incompatibilities may occur.

What's the current 'official' stance on jQuery?
If it's 'supported', what about these errors/warnings?
If it's NOT supported, what's the target version of FS to get full support?

Considering 6.3 was more than a minor release, I am not comfortable implementing jQuery 3 with Foundation until it gets official support. Still, it would be nice to move forward. This is literally the only thing in my app tied to jQuery 2 still.

@memoht Some combination of posts, including
https://github.com/zurb/foundation-sites/issues/8834
led me to understand that it's "Fine(tm)" to use ... and was even kinda-sorta-maybe supported.  ish.  And would be more so with FS >= v630
But since still seeing these warning/complaints, looking for some clarification.

@ kball @colin-marshall @Owlbertz
ping?

It should "Just work" - all known conflicts have been removed.  It looks like the bower.json dependency spec got missed (It's at ~2.2.0, and should be ^2.2.0 like in package.json).  I'll submit a PR to fix.

err, should be >= not ^

@kball @rafibomb
great, thanks.
if this could get merged to release tag, and updates pushed to pkg managers, it'll help with rollout -- without the need for intervention.

This is not fixed.
$(window).on("load", function (e) {}) currently does not work with jQuery 3.2.1

@kball I have a Foundation 5 project that's very hard to move to Foundation 6 and latest jQuery 2 (v2.2.4) has security issues.
You basically just have to replace:
$(window).load(function() { ... });
with
$(window).on('load', function() { ... });
Could you release af version of Foundation 5 with the fix, please?

@kball I have a Foundation 5 project that's very hard to move to Foundation 6 and latest jQuery 2 (v2.2.4) has security issues.
You basically just have to replace:
$(window).load(function() { ... });
with
$(window).on('load', function() { ... });
Could you release af version of Foundation 5 with the fix, please?


CupertinoPageRoute RTL

The direction of the animation and gesture should depend on the TextDirection.
If a drag is in progress when TextDirection changes, the drag should continue in the old direction until the drag is finished.

https://github.com/flutter/flutter/pull/13273


[staging-23.11] bluez: cherry-pick upstream fix for devices not pairing sometimes

Description of changes
Backport a fix for pairing devices, ref upstream issue
https://github.com/bluez/bluez/issues/614 ("PS5 controller will no longer pair
with bluetoothd").
(cherry picked from commit c583ee748a91b1da9ef36e8da5e565b7f114703f)

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

Rebased to trigger new ofborg eval (I don't trust the negative result).
I rebuilt my NixOS 23.11 system with this patch and it got my PS5 DualSense controller pairing again :tada:

ofborg-eval-lib-tests has this log tail:
[...]
ran test tests/timeout.sh... [PASS]
ran test tests/gc-auto.sh... [PASS]
building '/nix/store/v0h8b60jmyjv4yj77y4lb627axx174w4-lib-path-tests.drv'...
Running unit tests lib/path/tests/unit.nix
"Unit tests successful"
Running property tests lib/path/tests/prop.sh
Using seed 10002, use `lib/path/tests/prop.sh 10002` to reproduce this result
tests ok
error: 1 dependencies of derivation '/nix/store/7krcvymf1s8lp8q2kx6755yrp050zay7-nixpkgs-lib-tests-nix-2.3.17.drv' failed to build
building '/nix/store/6lzh5sz41qxi67k60axaylyl1hxwll1s-nixpkgs-lib-tests-nix-2.18.1.drv'...
Running lib/tests/modules.sh
====== module tests ======
227 Pass
0 Fail
Running lib/tests/filesystem.sh
tests ok
Running lib/tests/sources.sh
tests ok
Running lib/fileset/tests.sh
tests ok
Running lib/tests/systems.nix
[ ]
error: 1 dependencies of derivation '/nix/store/0wfws9x4479y2lmcfr9y93zyx4a9wqq1-nixpkgs-lib-tests.drv' failed to build

Further up in the log, the only thing I think is relevant is error: builder for '/nix/store/cj63hxm459md54fv6sx8rkclpqld1z96-nix-2.3.17.drv' failed with exit code 2; -- but that cannot be related to this PR.

I see the same ofborg issue in https://github.com/NixOS/nixpkgs/pull/279423, but not https://github.com/NixOS/nixpkgs/pull/281775. Hm...

@ofborg eval

An extra/explicit @ofborg eval comment fixed it.


Add "Last Cancelled" column to Permit and Marketplace signatures

Users often get confused about cancelling signatures since the list does not get updated. Showing a "Last Cancelled" date/time will hopefully prevent people from cancelling repeatedly.
We could do this by looking at "Approval" events to "0x000...0001" for 0 amount, since that is what we sign when cancelling signatures. If we want to be entirely accurate, we might still want to verify that this "Approval" event happened in a "permit()" call (and not in a regular approval).
This date should automatically get updated when a user cancels a potential signature

Hello @rkalis , I'd like to pick this up if still open. If yes, please give me the necessary details that could aid the fix and/or save time.

Hey @bobeu thank you for your interest!
To start, what I would recommend doing is the following:
In the PermitsEntry.tsx file it displays a row in the permits table. Here we can call the useAddressEvents() hook to get the most recent "Approval" events.
const { events, isLoading, error } = useAddressEvents();

Then from there, you can filter the events.approval events so that you only find the ones where the contract address is the token's address, the spender address (topic 2) is equal to DUMMY_ADDRESS (0x000...0001) and the value (event data) is 0.
When you have this list of events, you want to look at the most recent one (looking at timestamp if the event has it, or blockNumber if it doesn't have a timestamp).
If the event already has a timestamp, then you can use that timestamp to display a "Last Cancelled" date/time. If it does not have a timestamp, then you'll have to retrieve it first with await blocksDB.getBlockTimestamp(publicClient, blockNumber).
This isn't the full complete explanation of how to implement this functionality, but hopefully it can point you in the right direction. If you have any specific questions, let me know!

Hey @bobeu thank you for your interest!
To start, what I would recommend doing is the following:
In the PermitsEntry.tsx file it displays a row in the permits table. Here we can call the useAddressEvents() hook to get the most recent "Approval" events.
const { events, isLoading, error } = useAddressEvents();

Then from there, you can filter the events.approval events so that you only find the ones where the contract address is the token's address, the spender address (topic 2) is equal to DUMMY_ADDRESS (0x000...0001) and the value (event data) is 0.
When you have this list of events, you want to look at the most recent one (looking at timestamp if the event has it, or blockNumber if it doesn't have a timestamp).
If the event already has a timestamp, then you can use that timestamp to display a "Last Cancelled" date/time. If it does not have a timestamp, then you'll have to retrieve it first with await blocksDB.getBlockTimestamp(publicClient, blockNumber).
This isn't the full complete explanation of how to implement this functionality, but hopefully it can point you in the right direction. If you have any specific questions, let me know!

Thank you for the information. I'll get started as soon as possible. By now, I have an idea of what to do and how to go about it. I'll definitely let you know if I need any help.

@rkalis Is there a special way to clone this project? I am getting EOF errors even when I switched to using Linux OS. I tried switching between networks but the same issue persists.

Git bash

Ubuntu

Hmm that's strange. I just tried to clone it with both SSH and HTTPS and it both worked for me. Perhaps you could try to clone with SSH to see if that fixes the issue?

Hmm that's strange. I just tried to clone it with both SSH and HTTPS and it both worked for me. Perhaps you could try to clone with SSH to see if that fixes the issue?

Ok, thank you. I noticed my data provider strength is weak. No worries. I will fix the issue shortly.

Hmm that's strange. I just tried to clone it with both SSH and HTTPS and it both worked for me. Perhaps you could try to clone with SSH to see if that fixes the issue?

It worked now.

@rkalis Are you expecting to see something like this

If yes, I am unable to update the lastCancelled key to the 'columnHelper'.

@rkalis I just made a PR at https://github.com/RevokeCash/revoke.cash/pull/187. Hope this is what you expect? Please let me know anything that needs to be fixed.

Thanks to @bobeu this is now deployed in production 💪

Thank you @rkalis. Great work.


cyclic dependency between simulator and arrive event

Hello! Has anyone else encountered a cyclic dependency issue like this? Mine appears to be Arrive -> Event -> Simulator -> Event or Arrive -> Simulator -> Arrive if i am interpreting this correctly. But i don't really know how to work around this since my simulator creates arrive events and i have an abstract class Event that has a runEvent method that takes in a simulator.
Any help is appreciated! Thank you :)

May I ask what your Event.java does? My Event.java is just a abstract class for Serve/Arrival/etc events to inherit from. My simulator does not create any Event, only Arrival events. In my opinion, there is no need for events to take in Simulator as the events only need to take in specific arguments such as Customer and (double) time in, the events do not need to know anything else from the Simulator class.

May I ask what your Event.java does? My Event.java is just a abstract class for Serve/Arrival/etc events to inherit from. My simulator does not create any Event, only Arrival events. In my opinion, there is no need for events to take in Simulator as the events only need to take in specific arguments such as Customer and (double) time in, the events do not need to know anything else from the Simulator class.

I took in the simulator for my runEvent method to update the different statistics! like for arrive i have to reference the list of servers that's in my simulator to decide if arrive will lead to wait leave or serve.

May I ask what your Event.java does? My Event.java is just a abstract class for Serve/Arrival/etc events to inherit from. My simulator does not create any Event, only Arrival events. In my opinion, there is no need for events to take in Simulator as the events only need to take in specific arguments such as Customer and (double) time in, the events do not need to know anything else from the Simulator class.

I took in the simulator for my runEvent method to update the different statistics! like for arrive i have to reference the list of servers that's in my simulator to decide if arrive will lead to wait leave or serve.

Oh, how about passing the list of servers directly to your events to call the next event, instead of passing in the whole simulator? For keeping track of statistics, I created another Statistics.java for the purpose. I think these will eliminate the cyclic problem.

You probably wouldn't want to have the method runEvent inside your Event class. Think of it this way – when you want to update the statistics, whose job is that? Is that part of the event's jobs, or is that the responsibility of the simulator? If you assign some of the simulator's jobs to the event class, then the classes are sharing responsibilities. That would be a violation of the single responsibility principle.
Usually, circular dependency signals tight coupling, which is often bad in software design. That is because a change in one implies changes in many other classes that are coupled to the class. Decoupling will help.

You probably wouldn't want to have the method runEvent inside your Event class. Think of it this way – whose job is it to run some event and update the statistics? Is that part of the event's jobs, or is that the responsibility of the simulator? If you assign some of the simulator's jobs to the event class, then the classes are sharing responsibilities. That would be a violation of the single responsibility principle.
Usually, circular dependency signals tight coupling, which is often bad in software design. One of the reasons is that a change in one implies changes in many other classes that are coupled to the class. In my opinion, events, as building bricks of the simulator, do not really need to depend on the simulator class. Rather, the simulator should be dependent on the events. So, decoupling them will help.

May I ask what your Event.java does? My Event.java is just a abstract class for Serve/Arrival/etc events to inherit from. My simulator does not create any Event, only Arrival events. In my opinion, there is no need for events to take in Simulator as the events only need to take in specific arguments such as Customer and (double) time in, the events do not need to know anything else from the Simulator class.

I took in the simulator for my runEvent method to update the different statistics! like for arrive i have to reference the list of servers that's in my simulator to decide if arrive will lead to wait leave or serve.

Oh, how about passing the list of servers directly to your events to call the next event, instead of passing in the whole simulator? For keeping track of statistics, I created another Statistics.java for the purpose. I think these will eliminate the cyclic problem.

Thanks so much for the insights guys! I manage to resolve it! :D


Tidy up the zh-CHS translation for "irank" - the translators apparent…

…ly looked at the comment in

irank {0}
Isotope rank for transition node

and came up with
针对离子对节点的同位素排名 {0}
which is literally "Isotope rank for transition node {0}" where what we really want is
i排名 {0}
which is literally "irank {0}" (note the Roman "i" in "i排名")
One question in my mind - in the Japanese version of this, there is no blank between "irank" and the value. Is that also appropriate in Chinese?

I do think we want to make this change. The word "irank" only appears in our tutorials in the "PRM" tutorial, where it is accompanied by a screenshot showing the text that gets highlighted in this PR. Strangely the word "irank" does not get ranslated in either the Chinese or the Japanese tutorial text. I will update this PR to include an update to the tutorials.

In general Chinese (and I think Japanese as well) doesn't have whitespace between words. So I wouldn't expect them to have whitespace between a label and its value. Korean does have whitespace between words.

It is a number and our translators have control of this. If they chose to leave that space, I am inclined to leave it for now. If you look at the translation, there are places where they have spaces around insertion points and places where they do not. It may be that all spaces are mistakes, like the use of a three-period ellipsis versus the single-character Asian ellipsis. Always a mistake when the former is used, and translators do make this mistake. In this case, though, we would need to ask our translators to weigh in.

It is not an easy case, since we are going to include the Roman i and the text itself will be enclosed in Anglo/Euro parentheses, instead of Asian parentheses.

I would ask an application-knowledgeable Chinese Skyline user to confirm whether putting the i- suffix in front of a Chinese word makes sense to them, especially with the proportional font making the i barely visible. That looks weird to me. They may prefer a Chinese character or word for intensity there.
Chinese don't typically put whitespace in their writing, but if someone did it for them, AFAIK they'd read it with out noticing any difference. So I suspect that whether the whitespace is there or not is not a matter of being wrong or right, but just not mattering at all.

It is pretty subtle where this shows up in the UI.

To all users now there are two ranking categories distinguished only by an "i". They are also positionally distinct and one is all "precursor" labeled. So, it is a very learnable pattern.
Japanese:

English:

Our localization contact agreed to this change. Though, it is not clear how much she consulted native Chinese localizers in doing so.


No different icons in notifications screen

Only issues icon is shown. No matter it is a real issue, or pull request, or branch.
Before:

Now:

Introduced by #589, and #610 contains fix of it.


GetConvoyItemSlot returning -1 for items in the supply

GetConvoyItemSlot(ITEM_VULNERARY)  returns -1 even when a Vulnerary is in the supply. I've tried with several other items and the result has been the same. Am I missing something?

Oh so it was a bug. Gotcha


Issues with CommonServiceLocator >2.0.2

I've just updated the MVVM Nuget to v5.4.1.
In the process the new CommonServiceLocator was updated to 2.0.2. All that went fine.
But there is now a 2.0.3 of CommonServiceLocator available. When updating to that version the app doesn't run anymore throwing this:
System.IO.FileNotFoundException: Could not load file or assembly 'CommonServiceLocator, Version=<IP_ADDRESS>
So I guess, despite the Nuget dependency mentioning CommonServiceLocator (>= 2.0.2) the package it's not actually that happy when using something above 2.0.2...

@josesimoes I've experienced the same problem today. I added MVVM Light to a new WPF project, using the Package Manager Console, but when I went to build the app it complained about Microsoft.Practices.ServiceLocation not being found. Looking up that error I found that I should install the CommonServiceLocator package 2.0.3, which I did. But that had no effect on the problem. Would it be better to uninstall 2.0.3 and install some previous version, perhaps 2.0.1?

I posted a message on the MSDN WPF Forum about this. Got a reply, telling me that the issue was likely due to the version 2.0.3 of MVVMLight package. I was told to downgrade the CommonServiceLocator package from version 2.0.3 to 1.3.0, which would downgrade MVVMLight to a version where they would both "play nice" with each other.

Hi
At this point, given how many issues the ComonServiceLocator is causing, I would recommend moving you app to the. Net standard version of MVVM Light, where I got rid of the CommonServiceLocator. See http://mvvmlight.net/std10

Thank you @lbugnion for that suggestion!

@lbugnion, I got to thinking more about your recommendation. If I understand this link on Microsoft's documentation, I will probably not be able to use the .NET Standard version. We have a large Windows 7 user base that, unfortunately, will be with us for quite a while. 😞

I have a separate project with ViewModels and a WPF app. I had to install MvvmLightLibsStd10 and CommonServiceLocator to both of them in order to get this error fixed.

@lbugnion Please can you comment on this. It seems to be a common problem for quite a few people, and is causing serious issues.
As I commented, your recommendation of moving to .NET core is not an option for a mature application. We need to maintain our current code, not rewrite it all.

@lbugnion And MvvmLightLibsStd doesn't support .NET4, which we need to. Please fix this.

We now have 27 may 2021, and this issue is still not resolved.
This means MVVMLight is the cause for the single nuget package
in my company's application, that I have to keep permanently locked at version 2.0.2,
because MVVMLight is not maintained.
If I could only figure out what MVVMLight  is actually used for,
what problem it is trying to solve, I could port our application away from it.
But when I look at the documentation, I have not been able to figure out
what it is MVVMLight actually DOES, the documentation seems to
sort of assume I already know why I need/want MVVMLight,
and instead focuses on spreading the gospel.
Does anyone know what it is MVVMLight does, that I can't already do without it?
Thanks, Jakob.

@pylgrym If you look at the commits for the project, you'll see that there haven't been any updates to the code for two and a half years, so I think you are wasting your time expecting this to be fixed.
As for what MVVMLight is for, the main page here links you to the MVVMLight web site, which gives plenty of information about the library. I assume you understand MVVM in the first place, as if you don't, then you need to understand that first. Once you do, MVVMLight becomes fairly simple, as it just does the plumbing for you.
However, If I were you, I would look at moving to another library, as I don't think this one is going anywhere. It's been a couple of years since I did any MVVM, so I can't recommend any other framework specifically, but if you search around, I'm sure you'll find people discussing it, and people who are willing to advise.
Hope that helps.

@pylgrym recently a friend of mine, whose knowledgeable on these things, informed me that MVVMLight is no longer being supported. He recommends using Windows Community Toolkit, which he said is taking over from MVVMLight. Looking at that repo I see that it is actively supported; there was an update only 10 days ago. I've yet to try it myself, but my friend is someone I trust to know what he's talking about. Looks like there's various versions of the Windows Community Toolkit on NuGet as well.

There is even documentation on how to migrate

I didn't know that @robinTsl, thanks!

Thank you -

As for what MVVMLight is for, the main page here links you to the MVVMLight web site, which gives plenty of information about the library.

I may be looking in the wrong place, because the links to its documentation seem to just funnel into a 6-part Pluralsight course, which appears to be on MVVM in general, and not MVVM Light.
I would expect the pitch to be a diff pinpointing what MVVM-Light does right that WPF got wrong.
I have been lost there before, with its phrases like
"...  The main purpose of the toolkit is to accelerate the creation and development of MVVM applications in Windows Universal, WPF, Silverlight, Xamarin.iOS, Xamarin.Android and Xamarin.Forms. The MVVM Light Toolkit helps you to separate your View from your Model which creates applications that are cleaner and easier to maintain and extend.
..."
which I find give little insight - everybody already separates their views and models, so why-how does MVVMLight do this better than default WPF..
But you are right, and I will migrate away from it - thanks.


conformance: initial commit

cc: @SteveLasker

Partly addresses issue #22

This PR intended only as a first step.


Enable shift-tab to unindent comment fields

Closes https://github.com/sindresorhus/refined-github/issues/2490
Finally I completed https://github.com/fregante/indent-textarea/pull/6 so tab-to-indent now also includes shift-tab support (as well as a tab behavior that matches editors more closely)
Have a look and see if it behaves correctly. I modeled it after VS Code. Sublime Text seems to add a tab with shift-tab if no text is selected. Weird.

The behavior when just with whitespace is weird:

It skips going back to the start of the second line.

Good catch! This is one of those edge cases I was hoping to find before merging.
// `|` is the cursor
undindent('\n|\t')

	expected: '\n|'
	actual: '|\n'

This is harder than I thought.
Anyway.
unindent or outdent? VSCode seems to use outdent but elsewhere I found unindent

This should be fixed now.


Metal content scale / Retina

Related to https://github.com/bkaradzic/bgfx/issues/1704
BGFX_RESET_HIDPI flag seems to be not used at all in the metal renderer and  the metal renderer also seems to not set layer.contentsScale on the CAMetalLayer
Resulting in retina displays not being supported properly.
I guess this is kinda the answer too https://github.com/bkaradzic/bgfx/issues/370
I really want to avoid to write platform specific code.. or I would not use bgfx in the first place :)

I ended up adjusting the backbuffer resolution by the main display scale in order to make it look crisp on Mac's retina screen. Also had to scale all the further draws accordingly.

I don't have access to a Mac with retina display, so @Archie3d you can send PR to make it work.
On iOS there is this: https://github.com/bkaradzic/bgfx/blob/master/examples/common/entry/entry_ios.mm#L330
We can try to move this into renderer, but it seems it needs access to view, which is not always available. Right now you can init with only passing layer. https://github.com/bkaradzic/bgfx/blob/master/examples/common/entry/entry_ios.mm#L206

Thanks @attilaz , Hmm I admit I didn't check iOS.
Looks like that maybe macos could just use as well [m_view setContentScaleFactor: scaleFactor ]; basically somehow.
BGFX_RESET_HIDPI is not really strictly necessary I guess, just for consistency maybe.

@attilaz, I am not sure how this should be implemented correctly. Currently I adjust for the scale from outside of bgfx when calling init() or reset(). I assume the same could be achieved from within bgfx in SwapChainMtl::init() and especially in SwapChainMtl::resize() where drawable size must be scaled (not sure though about iOS):
    float scaleFactor = 1.0f;
#if BX_PLATFORM_IOS
    scaleFactor = [[UIScreen mainScreen] scale];
    [m_metalLayer setContentScaleFactor: scaleFactor];
#elif BX_PLATFORM_OSX
    scaleFactor = [[NSScreen mainScreen] backingScaleFactor];
    [m_metalLayer setContentsScale: scaleFactor];
#endif // BX_PLATFORM_*

    m_metalLayer.drawableSize = CGSizeMake(_width * scaleFactor, _height * scaleFactor);

However this will further need to be updated every time the underlying view's been moved between retina and non-retina displays.
Also all the pixel-perfect rendering (e.g. nanovg) will need to be scaled appropriately.


legion-18.05.0 : /.../threads.cc:1413:5: error: hwloc_linux_parse_cpumap_file was not declared in this scope

/var/tmp/portage/sys-cluster/legion-18.05.0/work/legion-legion-18.05.0/runtime/realm/threads.cc: In function ‘bool Realm::get_bd_sibling_id(int, int, std::set<int>&)’:
/var/tmp/portage/sys-cluster/legion-18.05.0/work/legion-legion-18.05.0/runtime/realm/threads.cc:1413:5: error: ‘hwloc_linux_parse_cpumap_file’ was not declared in this scope
     hwloc_linux_parse_cpumap_file(f, set);
     ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/var/tmp/portage/sys-cluster/legion-18.05.0/work/legion-legion-18.05.0/runtime/realm/threads.cc:1413:5: note: suggested alternative: ‘hwloc_linux_set_tid_cpubind’

Details here: https://bugs.gentoo.org/677616

@junghans what version of hwloc is this build attempting to use?  The realm code here hasn't changed in a very long time.

hwloc-2.0.2

A version bump to 18.12.0 might fix the issue!

I doubt changing the Legion version will help.  As I mentioned, the code in question hasn't changed in a long time.  However, what has changed is the hwloc API.  Version 2.x appears to have a number of backwards-incompatible changes compared to 1.x.  Can you build Legion against a 1.x version of hwloc instead?

Well, Gentoo is in the process of rolling out hwloc-2! So, we could disable the support for hwloc or drop legion from Gentoo completely.
However, Fedora and others will roll out hwloc-2 in not too long as well.

Ok, I required <hwloc-2 in Gentoo now:
https://github.com/gentoo/gentoo/commit/f3f448a49d7354b32e32005308fbaad34bb72404
So I leave this issue for a future release to be fixed!


Fix InfluxDB storage-plugin Metrics#multiGet issue

[x] If this pull request closes/resolves/fixes an existing issue, replace the issue number. Closes #7228.
[x] Update the CHANGES log.

Coordinators & Storage (zk, influxdb)  failed


Fix invalid syntax in graph.css

With https://jigsaw.w3.org/css-validator, graph.css is regarded as invalid.
In my deployment environment, invalid css syntax causes deployment failure. Thus I want to fix this.

Please run make assets to update the binary representation as well.

Oops, done!

My understanding of CSS is limited, but looks good to me. @stuartnelson3 wdyt?

looks fine to me, but the ins and outs of the pseudo selectors aren't my forte.

@grobie ping? I'm maintaining fork in our environment and I want to use upstream.

I'll merge it, and if something is wrong it's easy enough to fix


Getting Fields out of json

Support plan

Which support plan is this issue covered by? (Community, Sponsor, Enterprise): Community
Currently blocking your project/work? (yes/no): yes
Affecting a production system? (yes/no): yes

Context

Node.js version: 16.x.x
Release Line of Formidable (Legacy, Current, Next): Current
Formidable exact version: v2
Environment (node, browser, native, OS): MacOS
Used with (popular names of modules): Express

What are you trying to achieve or the steps to reproduce?

I get a very badly formatted json when i try logging files, I want to access the path of the file, But it's getting impossible i tried console.log(files.'') which wont actually work tried console.log(files[0]) but that too didnt work.

app.post('/upload', async (req, res) => {
    const form = new formidable.IncomingForm()
    form.parse(req, (error: any, fields: any, files: any) => {
        if(error) throw new Error(error)
        console.log(files)
        // imageDataURI.encodeFromFile(files.filepath).then((res: any) => console.log(res)).catch((e: any) => console.log(e))
    })
})

What was the result you got?
{
  '': PersistentFile {
    _events: [Object: null prototype] { error: [Function (anonymous)] },
    _eventsCount: 1,
    _maxListeners: undefined,
    lastModifiedDate: 2022-01-07T08:18:45.682Z,
    filepath: '/var/folders/sw/g7tk44p50dl3n_kgss8y6bwr0000gn/T/351263a04127c47c7bf9c2800',
    newFilename: '351263a04127c47c7bf9c2800',
    originalFilename: 'Screenshot_2022-01-01_at_10.36.58_AM-removebg-preview.png',
    mimetype: 'image/png',
    hashAlgorithm: false,
    size: 51200,
    _writeStream: WriteStream {
      fd: 25,
      path: '/var/folders/sw/g7tk44p50dl3n_kgss8y6bwr0000gn/T/351263a04127c47c7bf9c2800',
      flags: 'w',
      mode: 438,
      start: undefined,
      pos: undefined,
      bytesWritten: 51200,
      closed: false,
      _writableState: [WritableState],
      _events: [Object: null prototype],
      _eventsCount: 1,
      _maxListeners: undefined,
      [Symbol(kFs)]: [Object],
      [Symbol(kIsPerformingIO)]: false,
      [Symbol(kCapture)]: false
    },
    hash: null,
    [Symbol(kCapture)]: false
  }
}

What result did you expect?

A Good Formatted JSON.

The <input type="file"> should have a name property  like <input type="file" name="something">
you well then be able to access it like so console.log(files.something?.filepath)
Also you are miss-using the word JSON

@GrosSacASac true.
But definitely we should check against such case. :rocket: :ship:

Check what ?

Ah, probably nothing.


⚠ Jenkins Plugins Artifactory has degraded performance

In 44bf78d, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 1786 ms

Resolved: Jenkins Plugins Artifactory performance has improved in 101fe1e after 12 minutes.


Implement BigInt support for REST client

caused by https://github.com/qdrant/qdrant/issues/3669
relates to https://github.com/qdrant/openapi-typescript-fetch/issues/6
casually closes https://github.com/qdrant/qdrant-js/issues/48
Add support for BigInt on REST client via<EMAIL_ADDRESS>Also pins dependencies to prevent dep updates from breaking a working version.

Though previous versions point to<EMAIL_ADDRESS>and will receive the dependency update, this PR formalizes support in our SDK. It also adds correct TS typings.

TypeScript types for REST
The generator isn't generating bigint types by itself, see: https://github.com/drwpow/openapi-typescript/issues/1439
WIP (todo)

[ ] Generate correct types for bigint with transform option: https://openapi-ts.pages.dev/6.x/node#options

In order to finalise this PR, we have to generate new TS types that include bigint | number where relevant. For that we need to fix the OAS definitions which will affect the C-Sharp and Python clients. Perhaps it won't break anything, but that's the next step, to check.


I am getting the  ServiceBroker is stopped successfully error

Node version: 8.0.0
[2017-10-10T11:14:44.828Z] INFO  notebook/BROKER: Moleculer v0.11.0 is starting...
[2017-10-10T11:14:44.829Z] INFO  notebook/BROKER: Node ID: kuya-hp-notebook
[2017-10-10T11:14:44.829Z] INFO  notebook/BROKER: Namespace:
[2017-10-10T11:14:44.843Z] INFO  notebook/REGISTRY: '$node' service is registered.
[2017-10-10T11:14:44.849Z] INFO  notebook/BROKER: ServiceBroker with 1 service(s) is started successfully.
[2017-10-10T11:14:44.851Z] INFO  notebook/BROKER: ServiceBroker is stopped successfully. Good bye.

Because you don't have any service which does something. Or define transporter.

Thanks for the reply. But in the https://github.com/ice-services/moleculer-examples/tree/master/blog i can see there are some services

if you are using Runner you should set service folder. https://github.com/ice-services/moleculer-examples/blob/master/blog/package.json#L7
How did you run the Moleculer?

using the npm start

Hmm... I'm going to try it.

The problem is that README is not precise
npm start script is correct, just you should set services via SERVICEDIR or SERVICES env var
If you see mono in docker folder it set SERVICEDIR=service which is same as npm run dev.
But in micro, every container loads only one service with SERVICES=xy env var.
So try to start with
$ SERVICEDIR=services npm start

Thanks it works :+1:

using the npm start. But when i am running in npm run dev its ran successfully

it seem to be run mongod  first before you run blog


Patch Memory-Corruption vulnerability in URL decoding

cpp-netlib#501
Patch introduces checking distance to end of string and avoiding NULL Pointer dereference.
It's important security improvement

Thanks @zeroinside -- do you have a test case that you can add to the URI tests to make sure this is catching the issue?

Ping @zeroinside on the test case...

Sorry @zeroinside -- I need a test case in the test suite before I can merge this. Please re-open when you have one ready and updated for this PR.


feat(*): Post render hooks for Helm

This adds post-rendering hooks for Helm. See the proposal issue for full details

@technosophos um...

My understanding is that the purpose of this design is to make it super easy for an operator to do one-off shell commands that pipe data through some other existing tool ad hoc, not every single time.

So, if two people go to upgrade the same application one does it with the script and the other doesn't you can end up with differences.
If the one off case is the expectation than we shouldn't link it into the plugin system at all. If the plugin system is used it should be intentional. If the use case is one-off shall command not regularly used than there is no need for plugins.
I expect this to be abused.

@mattfarina yeah, essentially that is what we are enabling: An opportunity for a chart user to take the output of Helm, pipe it through something like Kustomize, and then install it with Helm. And we do think we want that to be the decision of the individual operator.
I imagine that it could be abused by people doing things like embedding other template languages in their charts. But (a) that can be done today, and (b) I don't think we're in the business of preventing people from making poor life choices.
My argument for including this feature is that it gives a happy path to people who want to use external patch managers like Kustomize. They can still take advantage of the rest of Helm's tooling instead of having to choose whether they want to patch their YAML or whether they want Helm-based installation management.


Import file structure and passport functionality

Import the file structure provided to us for a jumping off point for our project.

Done.  Interesting that the .travis and .lint files didn't copy over.


fix: handle error on wrong token

Pull Request Title
Handle error on wrong token
Description
Added description
Related Issue(s)
This PR addresses issue #727
/closes #727
/claim #727

@RS-labhub I'm sensing you didn't even test these changes nor read the description of the issue fully 😄
Closing the PR because it does not address what the issue outlines. You need to fix the 500 error that happens when you run daytona gp new and enter a token that is wrong.


Lidarr integration

Hi, great work for this new tool guys! It's great to have the chance to integrate aMule also on Sonarr and Radarr. I'm wondering if it could work also under Lidarr, that's the music collection manager, brother of Sonarr/Radarr.
Since for italian music, there's little less avaiability on the torrent's world, while on the emule/amule side there more chance to find this kind of shares. So, if possibile, the combination between Lidarr - Amarr would be great imho!
Thanks!

Hello @toketin , it should already work. Please try it with the readme the same way you would for radarr or sonarr, and if it doesn't work report here and I'll look into it (There's some issues at the moment that prevent this to work with radarr but I'm looking to fix them)

Closing for inactivity, in case feel free to reopen.


Selected tags list customisation

Is it currently possible to customise the how the selected tags list is rendered? Maybe it can be done using renderRoot?
If not, would it be possible to add a renderSelectedTagsList prop?
Thank you!

Thanks for your question @ellunium.
That sounds like a good idea, I'd welcome any contributions to support this request.

Thanks for the reply @i-like-robots !
I'm not sure I can do it or if I have enough knowledge to make the contribution myself, but I will give it a try in a fork and share.

Resolved via #71

Released as v.7.3.0