python312Packages.goodwe: 0.2.33 -> 0.3.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python312Packages.goodwe is: Python library for connecting to GoodWe inverter
meta.homepage for python312Packages.goodwe is: https://github.com/marcelblijleven/goodwe
meta.changelog for python312Packages.goodwe is: https://github.com/marcelblijleven/goodwe/releases/tag/v0.3.0
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.3.0 with grep in /nix/store/bs1qbvnkzns7kqql8zkv95yg36ky7rsz-python3.12-goodwe-0.3.0
found 0.3.0 in filename of file in /nix/store/bs1qbvnkzns7kqql8zkv95yg36ky7rsz-python3.12-goodwe-0.3.0

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

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
home-assistant-component-tests.goodwe
python311Packages.goodwe
python312Packages.goodwe

Instructions to test this update (click to expand)

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

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

Or:
nix build github:r-ryantm/nixpkgs/9bda5eb6107f3690bdd02e0b6fba885bd5e5478e#python312Packages.goodwe

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/bs1qbvnkzns7kqql8zkv95yg36ky7rsz-python3.12-goodwe-0.3.0
ls -la /nix/store/bs1qbvnkzns7kqql8zkv95yg36ky7rsz-python3.12-goodwe-0.3.0/bin

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

2 packages built:

python311Packages.goodwe
python312Packages.goodwe

Maintainer pings
cc @fabaff for testing.

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

5 packages built:

home-assistant-component-tests.goodwe
python311Packages.goodwe
python311Packages.goodwe.dist
python312Packages.goodwe
python312Packages.goodwe.dist


fix: Add missing node tag to kubernetes_state.pod.count metric

What does this PR do?
Add missing node label to the pod.count aggregator in the kubernetes_state_core check.
Motivation
the kubernetes_state.pod.count metric is computed from the kube_pod_info
that contains the label node. to be able to map the kube_pod_info
to the host, the pod.count aggregator need to use the node label.
Additional Notes
Possible Drawbacks / Trade-offs
increase the number of kubernetes_state.pod.count by the number of node in a k8s cluster.
But it was already the case with the legacy kubernetes_state python check.
Describe how to test/QA your changes

Deploy the agent, cluster-agent in a kubernetes environment with the helm chart or the operator.
Enable the kubernetes_state_core check.
the metric kubernetes_state.pod.count should have the node and host tags present.

Reviewer's Checklist

[ ] If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
[ ] The appropriate team/.. label has been applied, if known.
[ ] A release note has been added or the changelog/no-changelog label has been applied.
[ ] Changed code has automated tests for its functionality.
[ ] Adequate QA/testing plan information is provided if the qa/skip-qa label is not applied.
[ ] If applicable, docs team has been notified or an issue has been opened on the documentation repo.
[ ] If applicable, the need-change/operator and need-change/helm labels have been applied.
[ ] If applicable, the config template has been updated.

Let's update the documentation here https://github.com/DataDog/datadog-agent/blob/main/pkg/collector/corechecks/cluster/ksm/kubernetes_state.md

I thought it was auto generated 😄


Replace paper-icon-button and cleanup styles

Connected to #59

replace paper-icon-button
adjust styles for dialogs
replace iron-icons import with custom iconset
cleanup unused styles
add stylelint and fix some warnings

This change is

Reviewed 15 of 15 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

Review status: :shipit: all files reviewed at latest revision, all discussions resolved, all commit checks successful.

Comments from Reviewable

Reviewed 13 of 15 files at r1, 2 of 2 files at r2.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

Reviewed 1 of 1 files at r3.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


signature verification failed

Hi!
I have problem with broadcasting Tx, using @xchainjs/xchain-thorchain.
When I broadcasted transaction to node URL, I got error " signature verification failed; please verify account number and chian-id(thorchain-mainnet-v1) : unauthorized"
Is there any proper way to solve this? Or what is the exact cause of this?
please check ASAP.
thanky you

Please make sure your phrase is correct, that is a cryptographic related error when intitializing the client.

Hi
I found that transfer() method is wrong while adding signature in TxBuilder.

Make sure your xchain-thorchain is the right version number. It appears to be already fixed.


chore(v2): replace few Lodash methods with native counterparts

Motivation
Same motivation like in previous PRs.
This is the initial step in getting rid of main lodash package in core v2 Docusaurus package. In this PR _.compact and _.flatten methods has been replaced with their native counterparts.
Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan
Same test results before and after code refactor.
Related PRs

#2460
#2519

I think I'd stick with the Lodash versions given they are more readable. Sorry about that.

@yangshun I think that it's not a good approach. This means that v2 core will have two more packages (lodash.concat and lodash.flatten) and two more dev packages (@types/lodash.concat and  @types/lodash.flatten) just because of personal preferences.

@lex111 what do you think? Do you agree?

Also compact + flatten replacement could be extracted to the separate util/helper method if you think this improve readability, but I have no idea where this kind of code should be placed (in which package, which path).

I have updated the reworked PR and removed also assign and isArray methods. All commits has been squashed. Current version can be seen here: https://github.com/Simek/docusaurus/commit/2084e9981cf682772bd63604a6478c0aee6a0c6f
After applying those changes only has, isPlainObject and isString packages are needed in the core. I have a finishing commit stashed, which removes lodash dependency and adds listed above single method packages and typing for them.
Let me know if I should commit those changes in the separate PR after this part will be resolved or add them in reworked version of this PR.

Ok let's do this. Could you reopen a new PR? I can't seem to reopen the PR now because it has been force pushed

Hey, was wondering what is the motivation to use lodash es exactly?
Personnally I find it highly annoying to have to update package.json everywhere I need a new lodash method.
What's the problem with a regular lodash available in node?
I understand we want to optimize client code, but don't really see the value for node code.
Btw, nothing will enforce the rule of "only lodash ES imports" over time. In fact, some code of mine was already merged and does not use lodash es but regular lodash, so wonder what to do about this?
If there are striong reasons to use lodash ES then we should enforce it with an ESLint import rule, but honnestly I'm not convinced by the value of enforcing such rule (at least for node code)

What I'd suggest is:

prevent lodash import in client code by a nested .eslintrc in client code folders, with import rules preventing import from lodash
allow using lodash in any server code, not necessarily from ES imports like this refactor introduced


As a user, I expect the Contact's Home Phone to stay syncronized with the Household Account's Home Phone.

Hub thread: https://powerofus.force.com/0D58000001SJCBW

more comments from the Hub:
Mark Westwind (EarthTeam)
As a user, I would like NPSP to link the HH Account Phone to the Contact Home Phone instead of a separate Household Phone formula field. This would bring the HH Phone into the purview of the Preferred Phone functionality. Otherwise, there's a risk that the Phone field may end up empty if the HH Phone is not copied to the Home Phone field. This also complicates reporting - by design, the Preferred Phone is supposed to be the only phone field needed in reports. I grant that there may be HHs where the primary HH phone is different from a Contact's "preferred home phone" ... but I can't imagine that it's common enough to require two fields as the default. I also understand that the current HH Phone formula field is an easier implementation, but unless I'm missing something, it sure would be great to see this change in a future revision.

**lurch: attach W-007336

Tracking W-007336

Is this item being worked on?

@Jeffissenberg No, not yet.


Cast function

I think this function is required to use fp16.

LGTM except comment.

I fixed the test.

Please add testing.run_module(__name__, __file__) to end of test file.

i fixe it

OK!


Clarify what is needed for single packaging

Doc currently says:

Windows App SDK 0.8 and C# version of 1.0 Preview 3: You must install the single-project MSIX packaging tools extension separately.

Then with a list of VSIX installers. It sounds like if you're not on Preview 3 any longer, it isn't needed, but I'm finding it is. Could this phrasing be updated to be more clear around what is needed with VS2022 and WinAppSDK1.0 final?

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

ID: 0401c948-1dda-c819-ee88-902ac6fcbbd9
Version Independent ID: c1748244-0f46-8dec-a88e-020f12d9a387
Content: Package your app using single-project MSIX - Windows apps
Content Source: hub/apps/windows-app-sdk/single-project-msix.md
Product: reunion
Technology: get-started
GitHub Login: @stevewhims
Microsoft Alias: stwhi

Thanks, @dotMorten! I'll investigate.
-Steve

So, the single-project MSIX packaging tools are always needed if you want to work with single project solutions. The tools are usually bundled with the Windows App SDK VSIX. But the exception is if you're on the versions mentioned in the topic. In those cases you need to install the single-project MSIX packaging tools explicitly.
I've added this clarification to the topic.
Thanks!
-Steve

There is no windows app Sdk vsix any longer. Project templates ship with VS2022 now but doesn’t (for whatever reason) install the single project vsix


NGG-70 | create grunt task 'npm-verify'

@shahata and @ranzwix - here's my (first) ng-guild task, see NGG-70.

Thanks! I want to experiment with this a bit, so for now added it with FT


jenkins-plugin: add retry layer/adapter for REST invocations

Bug 1454485
Bugzilla link https://bugzilla.redhat.com/show_bug.cgi?id=1454485
Detailed explanation
Implement a general retry mechanism for failing HTTP REST operations
against the OpenShift master

@bparees @oatmealraisin FYI

Ah ... the httpGet path needs some work

ok tests are clean now with some more tweaks to the error handling .. have 1 more mod I'm about to try

interesting ... a concurrent mod in this run uncovered a NPE ... will address NPE, and investigate if there is a deeper issue wrt retry

ah yes ... the master sends back an HTTP rc 409, which the restclient does not deal with specifically ... we already had retry for this higher up the plugin stack
IMO simply addressing the NPE in the new logic is sufficient  ... will push momentarily

OK ... tests are looking good.
@bparees - any more suggestions before merging?

lgtm


test: add MutationObserver polyfill test

refs #368

ah, this was moved to https://github.com/skatejs/polyfill-mutation-observer - closing.


Optimize the prestack parameter for Itto's Burst

Currently, if itto does NA > Q, he gets a strStack. This should be changed to
"Itto by default doesn't get any prestacks when doing NA > Q, and the parameter should be used if one wishes to pefrom the prestack technique."
This is because in-game, you need to time the burst in a delibirate manner if you want to perform the prestack technique, so this should be reflected in gcsim too.

this will be fixed by #729. you'll have a parameter called "prestack" on itto's burst that is 0 by default and if it's not 0, it'll add a stack if you did N1 -> Q


bug: Multiple clear icons in searchbar

When using the ion-searchbar like so, <ion-searchbar id="main-search" show-cancel-button="never" animated></ion-searchbar>
There are 2 clear icons shown like this when typing into the searchbar like this:

After digging in, I understood that one of the icons was given by the browser because input type="search" is being used by ionic with inputmode as search thereby the browser gives a default clearing icon by itself.
In addition to this, Ionic also adds a clear icon when using searchbar making it 2 clear icons.
In any case, only one clear icon must be displayed. Any ideas on how I can go ahead with this?
Currently, I am solving this by explicitly setting the type as text like this:
<ion-searchbar id="main-search" inputmode="search" type="text" show-cancel-button="never" animated></ion-searchbar>

Thanks.

Thanks for the issue. Which browser/version are you seeing this in?

@liamdebeasi Google Chrome - Version 79.0.3945.79 (Official Build) (64-bit) when running in browser via capacitor.

Thanks for the follow up. Are you testing this on an Android device? If so, which model/version?

@liamdebeasi I remember getting this error in the browser (when running serving the app directly from www folder). Don't remember if the same occured in the android device.

Which OS are you running? I'm running Chrome 79 on macOS and am not seeing this additional clear button.

@liamdebeasi Ubuntu 19.10
Details:
Linux vignesh-predator 5.3.0-24-generic #26-Ubuntu SMP Thu Nov 14 01:33:18 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux


CI Failures when compiling wasi-common

On several recent pull requests there appear to be CI failures unrelated to the change ... namely https://github.com/bytecodealliance/wasmtime/pull/625, https://github.com/bytecodealliance/wasmtime/pull/360, https://github.com/bytecodealliance/wasmtime/pull/627.
are a few that I've noticed. I have not been able to reproduce locally. Failure usually occurs on nightly though I believe I've seen similar error reported with a different configuration.

Will see if I can determine something more but anyone have an idea?

I believe this is a regression in rustc itself

I see. Thanks! Looks like https://github.com/bytecodealliance/wasmtime/pull/635 has been merged to address this.
@alexcrichton @kubkon BTW is there a way to re-trigger CI without doing a force push?
Thanks.

@jlb6740 you should be able to do that from the “checks” tab in your PR. There, you should see the summary of all Github Actions jobs, and in the top right corner, there should be a “Re-run all checks” button that should do what you’re after.


Replace Audio with the recorded data

Description
I would like to use a music file as the audio track of the recorded video
Steps to reproduce
Here is a failure case I have tried
let music_track = new videojs.AudioTrack({
  id: "bgm",
  label: "Pre-set music",
  kind: "main"
})
player.audioTracks().addTrack(music_track);
player.record().stop();

player.on('finishRecord', function() {
    console.log('finished recording:', player.recordedData);
    upload(player.recordedData);
});

<audio id="CutMusic">
  <source id="bgm" src="XXXX.wav">
</audio>

I wonder whether changing the audio track would affect the audio in player.recordedData?
If no, is there any way to change the audio in recordedData?
browsers
Chrome

No this is not possible (yet). You could play the music file using your internal audiocard instead of the microphone and record that, e.g.

Looks like the captureStream() API allows you to do this, see #288.
Marking this as a duplicate of #288.


MicroModal not triggering modal, says Please specify at least one 'micromodal-trigger' – "data attribute."

I have imported the MicroModal JS and basic CSS to an existing, older style project. The MicroModal initialisation I placed on the page...

...seems to work fine as I am getting the console log error:

However I HAVE added such attributes, i.e. here:
Lookup

Why is the MicroModal module seemingly unable to identify the data-attribute ?
When I try to trigger the modal manually with MicroModal.show('modal-1');  it works fine.
This is an older project I am extending and it's using jQuery, in case that matters.

Not sure if you fixed this already, your configuration is saying look for an element with "data-custom-open" attribute to trigger the opening but your element is using an attribute named "data-micromodal-trigger".
So you either need to update your span to use the attribute you specified "data-custom-open".
Or remove the setting and use whatever the default is for MicroModal (ie. "data-micromodal-trigger")

I ended up triggering the modals manually - but your comment makes perfect sense, I obviously didn't understand the meaning of the openTrigger and closeTrigger options. Thank you for getting back on this.


boards: seeed: doc: fix links to the device tree files

Fix links to the device tree file in the documentation.

should be addressed with https://github.com/zephyrproject-rtos/zephyr/pull/70152 but it looks like I might have missed a file on my side?

Sorry, my bad. This was fixed in the https://github.com/zephyrproject-rtos/zephyr/pull/70152.

Dear, @kartben and @nordicjm, as that issue is already addressed with https://github.com/zephyrproject-rtos/zephyr/pull/70152, should I close this PR?

Dear, @kartben and @nordicjm, as that issue is already addressed with #70152, should I close this PR?

Yes

Close because this issue is already addressed by https://github.com/zephyrproject-rtos/zephyr/pull/70152.


Log hashing algorithm of incoming assertions

This issue is imported from pivotal - Originaly created at Dec 23, 2015 by Thijs Kinkhorst
As a federation operator, in order to phase out the deprecated hashing algorithm SHA1, I want to know which of our IdPs still use this hashing algorithm. Therefore it would be nice to log this information. This should both be assertions and signed authn requests.
https://github.com/OpenConext/OpenConext-engineblock/issues/202

Logging should be as simple as possible. The Response contains a signature which contains a signature method. It might be required to create an accessor for the signing method. (Daan van Renterghem - Jan 6, 2016)


Android Test Failed with unexpected '('

Trying to test a React-Native project using detox.
I am able to:

Execute Detox build and test with iOS
Execute Emulators on Android Studio
Execute detox build with Android

detox: 19.4.2,
react-native: 0.66.3
Node: v14.17.3
Device: Android Studio emulator: Samsung_Galaxy_8_API_24
OS: Mac
Gradle Plugin VErsion: 4.2.2
Gradle Version: 6.9
command:
detox test -c android.emu.debug --loglevel trace
While running the detox test I am getting only in Android there errors:
detox[34161] DEBUG: [SPAWN_CMD, #34205] ~/Library/Android/sdk/platform-tools/adb -s emulator-5554 shell am instrument -w -r -e detoxServer ws://localhost:51122 -e detoxSessionId f6f50cfb-917d-0fea-4e2c-f76610c4454b -e detoxURLBlacklistRegex ("https://clientstream.{hide_service}.com/*") -e debug false io.app.{app_name_hide}.test/androidx.test.runner.AndroidJUnitRunner
detox[34161] ERROR: [SPAWN_STDERR, #34205] /system/bin/sh: syntax error: unexpected '('

detox[34161] DEBUG: [SPAWN_END, #34205] ~/Library/Android/sdk/platform-tools/adb -s emulator-5554 shell am instrument -w -r -e detoxServer ws://localhost:51122 -e detoxSessionId f6f50cfb-917d-0fea-4e2c-f76610c4454b -e detoxURLBlacklistRegex ("https://clientstream.{hide_service}.com/*") -e debug false io.app.{app_name_hide}.test/androidx.test.runner.AndroidJUnitRunner finished with code = 1
detox[34161] DEBUG: [EXEC_CMD, #27] "~/Library/Android/sdk/platform-tools/adb" -s emulator-5554 reverse --remove tcp:51122

detox[34161] TRACE: [EXEC_SUCCESS, #27]
detox[34161] DEBUG: [EXEC_CMD, #28] "~/Library/Android/sdk/platform-tools/adb" -s emulator-5554 shell "ps | grep \"io\{app_name_hide}$\""
detox[34161] ERROR: [EXEC_FAIL, #28] ""~/Library/Android/sdk/platform-tools/adb" -s emulator-5554 shell "ps | grep \"io\.app\{app_name_hide}$\""" failed with error = ChildProcessError: Command failed: "~/Library/Android/sdk/platform-tools/adb" -s emulator-5554 shell "ps | grep \"io\.app\{app_name_hide}$\""
 `"~/Library/Android/sdk/platform-tools/adb" -s emulator-5554 shell "ps | grep \"io\.app\{app_name_hide}\""` (exited with error code 1) (code=1), stdout and stderr:

I can see the logtrace pointing to 2 errors:
/system/bin/sh: syntax error: unexpected '('
and
failed with error = ChildProcessError:
I added to my bash_profile
export PATH=”~/Library/Android/sdk/emulator:${PATH}”
following => THIS
iOS is working fine, I think I have some strange configuration in Android Emulator but any log available is helping me to get more information.
From --loglevel trace I have the first 26 EXEC_SUCCESS:
detox[34161] DEBUG: [EXEC_CMD, #1] "~/Library/Android/sdk/emulator/emulator" -version
detox[34161] TRACE: [EXEC_SUCCESS, #1] Android emulator version <IP_ADDRESS> (build_id 8100890) (CL:N/A)

detox[34161] DEBUG: [EXEC_CMD, #2] "~/Library/Android/sdk/platform-tools/adb"  devices
detox[34161] DEBUG: [EXEC_SUCCESS, #2] List of devices attached

detox[34161] DEBUG: [EXEC_CMD, #3] "~/Library/Android/sdk/platform-tools/adb" -s emulator-5554 shell "getprop dev.bootcomplete"
detox[34161] TRACE: [EXEC_SUCCESS, #3] 1
detox[34161] TRACE: [ARTIFACTS_LIFECYCLE] artifactsManager.onBootDevice({ deviceId: 'emulator-5554', type: 'Pixel_5_API_31', coldBoot: false })

detox[34161] DEBUG: [EXEC_CMD, #4] "~/Library/Android/sdk/platform-tools/adb" -s emulator-5554 shell "getprop ro.build.version.sdk"
detox[34161] TRACE: [EXEC_SUCCESS, #4] 31

detox[34161] DEBUG: [EXEC_CMD, #5] "~/Library/Android/sdk/platform-tools/adb" -s emulator-5554 shell "settings put global animator_duration_scale 0"
detox[34161] TRACE: [EXEC_SUCCESS, #5]

detox[34161] DEBUG: [EXEC_CMD, #6] "~/Library/Android/sdk/platform-tools/adb" -s emulator-5554 shell "settings put global window_animation_scale 0"
detox[34161] TRACE: [EXEC_SUCCESS, #6]

detox[34161] DEBUG: [EXEC_CMD, #7] "~/Library/Android/sdk/platform-tools/adb" -s emulator-5554 shell "settings put global transition_animation_scale 0"
detox[34161] TRACE: [EXEC_SUCCESS, #7]

detox[34161] DEBUG: [EXEC_CMD, #8] "~/Library/Android/sdk/platform-tools/adb" -s emulator-5554 shell "dumpsys power | grep \"^[ ]*m[UW].*=\""
detox[34161] TRACE: [EXEC_SUCCESS, #8]   mWakefulness=Awake

detox[34161] DEBUG: [EXEC_CMD, #9] "~/Library/Android/sdk/build-tools/32.1.0-rc1/aapt" dump badging "~/android/app/build/outputs/apk/debug/app-debug.apk"
detox[34161] TRACE: [EXEC_SUCCESS, #9] package: name='io.app.{app_name_hide}' versionCode='115' versionName='2.0.0' platformBuildVersionName='11' platformBuildVersionCode.....{build infos}

detox[34161] DEBUG: [EXEC_CMD, #10] "~/Library/Android/sdk/platform-tools/adb" -s emulator-5554 shell "am force-stop io.app.{hide_app_name}"
detox[34161] TRACE: [EXEC_SUCCESS, #10]

detox[34161] DEBUG: [EXEC_CMD, #11] "~/Library/Android/sdk/platform-tools/adb" -s emulator-5554 shell "pm list packages io.app.{hide_app_name}"
detox[34161] TRACE: [EXEC_SUCCESS, #11] package:io.app.{hide_app_name}
package:io.app.{hide_app_name}.test

detox[34161] DEBUG: [EXEC_CMD, #12] "~/Library/Android/sdk/platform-tools/adb" -s emulator-5554 uninstall io.app.{hide_app_name}
detox[34161] TRACE: [EXEC_SUCCESS, #12] Success

detox[34161] DEBUG: [EXEC_CMD, #13] "~/Library/Android/sdk/platform-tools/adb" -s emulator-5554 shell "pm list packages io.app.{hide_app_name}.test"
detox[34161] TRACE: [EXEC_SUCCESS, #13] package:io.app.{hide_app_name}.test

detox[34161] DEBUG: [EXEC_CMD, #14] "/~/Library/Android/sdk/platform-tools/adb" -s emulator-5554 uninstall io.app.{hide_app_name}.test
detox[34161] TRACE: [EXEC_SUCCESS, #14] Success

detox[34161] DEBUG: [EXEC_CMD, #15] "~/Library/Android/sdk/build-tools/32.1.0-rc1/aapt" dump xmlstrings "~/android/app/build/outputs/apk/debug/app-debug.apk" AndroidManifest.xml
detox[34161] TRACE: [EXEC_SUCCESS, #15] String pool of 151 unique UTF-16 non-sorted strings, 151 entries and 0 styles using 10476 bytes:

detox[34161] DEBUG: [EXEC_CMD, #16] "~/Library/Android/sdk/build-tools/32.1.0-rc1/aapt" dump xmlstrings "~/android/app/build/outputs/apk/androidTest/debug/app-debug-androidTest.apk" AndroidManifest.xml
detox[34161] TRACE: [EXEC_SUCCESS, #16] String pool of 41 unique UTF-16 non-sorted strings, 41 entries and 0 styles using 2128 bytes:

detox[34161] DEBUG: [EXEC_CMD, #17] "~/Library/Android/sdk/platform-tools/adb" -s emulator-5554 shell "rm -fr /data/local/tmp/detox"
detox[34161] TRACE: [EXEC_SUCCESS, #17]
detox[34161] DEBUG: [EXEC_CMD, #18] "~/Library/Android/sdk/platform-tools/adb" -s emulator-5554 shell "mkdir -p /data/local/tmp/detox"
detox[34161] TRACE: [EXEC_SUCCESS, #18]
detox[34161] DEBUG: [EXEC_CMD, #19] "~/Library/Android/sdk/platform-tools/adb" -s emulator-5554 push "~/android/app/build/outputs/apk/debug/app-debug.apk" "/data/local/tmp/detox/Application.apk"
detox[34161] TRACE: [EXEC_SUCCESS, #19] ~/android/app/build/outputs/apk/debug/app-debug.apk: 1 file pushed, 0 skipped. 23.1 MB/s (98901702 bytes in 4.088s)

detox[34161] DEBUG: [EXEC_CMD, #20] "~/Library/Android/sdk/platform-tools/adb" -s emulator-5554 shell "pm install -r -g -t /data/local/tmp/detox/Application.apk"
detox[34161] TRACE: [EXEC_SUCCESS, #20] Success

detox[34161] DEBUG: [EXEC_CMD, #21] "~/Library/Android/sdk/platform-tools/adb" -s emulator-5554 push "~/android/app/build/outputs/apk/androidTest/debug/app-debug-androidTest.apk" "/data/local/tmp/detox/Test.apk"
detox[34161] TRACE: [EXEC_SUCCESS, #21] ~/android/app/build/outputs/apk/androidTest/debug/app-debug-androidTest.apk: 1 file pushed, 0 skipped. 81.8 MB/s (3360146 bytes in 0.039s)

detox[34161] DEBUG: [EXEC_CMD, #22] "~/Library/Android/sdk/platform-tools/adb" -s emulator-5554 shell "pm install -r -g -t /data/local/tmp/detox/Test.apk"
detox[34161] TRACE: [EXEC_SUCCESS, #22] Success

detox[34161] TRACE: [ARTIFACTS_LIFECYCLE] artifactsManager.onBeforeTerminateApp({
  deviceId: 'emulator-5554',
  bundleId: 'io.app.{hide_app_name}'
})
detox[34161] DEBUG: [EXEC_CMD, #23] "~Library/Android/sdk/platform-tools/adb" -s emulator-5554 shell "am force-stop io.app.{hide_app_name}"
detox[34161] TRACE: [EXEC_SUCCESS, #23]
detox[34161] TRACE: [ARTIFACTS_LIFECYCLE] artifactsManager.onTerminateApp({
  deviceId: 'emulator-5554',
  bundleId: 'io.app.{hide_app_name}'
})
detox[34161] TRACE: [ARTIFACTS_LIFECYCLE] artifactsManager.onBeforeLaunchApp({
  deviceId: 'emulator-5554',
  bundleId: 'io.app.{hide_app_name}',
  launchArgs: {
    detoxServer: 'ws://localhost:51122',
    detoxSessionId: 'f6f50cfb-917d-0fea-4e2c-f76610c4454b',
    detoxURLBlacklistRegex: '("https://clientstream.{hide_service}.com/*")'
  }
})
detox[34161] DEBUG: [EXEC_CMD, #24] "~/Library/Android/sdk/platform-tools/adb" -s emulator-5554 shell "date +\"%m-%d %T.000\""
detox[34161] TRACE: [EXEC_SUCCESS, #24] 01-28 16:08:10.000

detox[34161] DEBUG: [EXEC_CMD, #25] "~/Library/Android/sdk/platform-tools/adb" -s emulator-5554 reverse tcp:51122 tcp:51122
detox[34161] TRACE: [EXEC_SUCCESS, #25] 51122

detox[34161] DEBUG: [EXEC_CMD, #26] "~/Library/Android/sdk/platform-tools/adb" -s emulator-5554 shell "pm list instrumentation"
detox[34161] TRACE: [EXEC_SUCCESS, #26] instrumentation:io.app.{hide_app_name}.test/androidx.test.runner.AndroidJUnitRunner (target=io.app.{hide_app_name})

then the Test is crashing as report before with the next lines:
detox[34161] DEBUG: [SPAWN_CMD, #34205] ~/Android/sdk/platform-tools/adb -s emulator-5554 shell am instrument -w -r -e detoxServer ws://localhost:51122 -e detoxSessionId f6f50cfb-917d-0fea-4e2c-f76610c4454b -e detoxURLBlacklistRegex ("https://clientstream.{hide_service}.com/*") -e debug false io.app.{app_name:hide}/androidx.test.runner.AndroidJUnitRunner

detox[34161] ERROR: [SPAWN_STDERR, #34205] /system/bin/sh: syntax error: unexpected '('

Debug and Release in Android are not working and this is the .detoxrc.json:
{
  "testRunner": "jest",
  "runnerConfig": "e2e/config.json",
  "skipLegacyWorkersInjection": true,
  "apps": {
    "android.debug": {
      "type": "android.apk",
      "binaryPath": "android/app/build/outputs/apk/debug/app-debug.apk",
      "build": "cd android && RN_SRC_EXT='e2e.tsx,e2e.ts' && ./gradlew assembleDebug assembleAndroidTest -DtestBuildType=debug && cd .."
    },
    "android.release": {
      "type": "android.apk",
      "binaryPath": "android/app/build/outputs/apk/release/app-release.apk",
      "build": "cd android && RN_SRC_EXT='e2e.tsx,e2e.ts' ./gradlew assembleRelease assembleAndroidTest -DtestBuildType=release && cd .."
    }
  },
  "devices": {
    "emulator": {
      "type": "android.emulator",
      "device": {
        "avdName": "Samsung_Galaxy_8_API_24"
      }
    }
  },
  "configurations": {
    "android.emu.debug": {
      "device": "emulator",
      "app": "android.debug"
    },
    "android.emu.release": {
      "device": "emulator",
      "app": "android.release"
    }
  }
}

Hi,
please try to align your usage of detoxURLBlacklistRegex with this reference. Namely, add backslashes before the enclosing parentheses, or - since you only have one expression in your case, remove them altogether 🙏🏻

@d4vidi you got the point! thanks

Happy to hear!

How did you solve the failed with error = ChildProcessError: error?

How did you solve the failed with error = ChildProcessError: error?
@GualbertoVannini


No more http and inbound-http interfaces

Resolves #1871 (marking as a daft until that PR is merged)
What's going on here?
Instead of having two interfaces (wasi-http and http) that both do the same thing, we are removing the http interface (and the inbound-http interface) in favor of only using wasi-http. This only impacts the guest - the host continues to support the http interface for older apps.
This has little impact on the user's actual programming experience (at least for Rust) as the Rust SDK continues to allow a Request -> Response style handler even though wasi-http is built on a Request and ResponseOutParam style. This should make it considerably less confusing for users interacting with Spin WebAssembly components directly as they won't have to wonder why there is both wasi-http and http.
Concerns
For other languages with less ability to neatly hide implementation details, we are forcing users to use the considerably more complex wasi-http (which is more complex because it supports streaming HTTP bodies), but I don't see why even languages like C shouldn't be able to put a simpler non-streaming-body API in front of the wasi-http API.
Open Questions

Instead of the macro being #[wasi_http_component], we could keep it as #[http_component] since there is no longer another http style to contend with. Should we?
Should the manifest v2 default to executor = { type = "wasi" }?
Should the SDK's module be http instead of wasi_http? We originally used the name wasi_http to differentiate from the Spin http interface but this is no longer necessary. Perhaps the shorter http is better?

Instead of the macro being #[wasi_http_component], we could keep it as #[http_component] since there is no longer another http style to contend with. Should we?

The wasi sure feels redundant if it's not being contrasted with another macro.  For me one consideration is the upgrade experience:

If we remove http_component and have only wasi_http_component, upgrading the SDK immediately breaks the code with a "macro not found" error.  What detail does the user see?  Does the error steer them in the right direction to fix it?
If we keep the http_component name but change the behaviour to be the current wasi_http_component, upgrading the SDK... does what?  Does the app continue to work as before because we still support the request-response paradigm?  Or does it break in subtle ("hey this needs to return a Whatsit instead of a Doodad") or unsubtle (weird error, runtime malfeasance) ways?

A similar comment about wasi being redundant applies to the third open question.  It seems like it has value if contrasting with something else, but not if "this is just how we do HTTP now."

Decision and new status quo
@itowlson I've switched to having everything called http as I agree that the name wasi_http works best when its in contrast but when there is only module related to http, it should just be called http.
As for what the upgrade experience is like - unfortunately the SDK has several breaking changes in it so users will most likely just get type errors. We should make sure we have docs on the changes to the SDK so that users know how to upgrade. That being said, the changes are mostly small and trivial and the overall "shape" of handlers remains the same. I was able to upgrade one of my apps very quickly just following Rust compiler errors.
Once the user has fixed the type errors, there is one runtime issue that they will run into:
Error processing request: no fermyon:spin/inbound-http instance found

They must update the [component.trigger] config to include executor = { type = "wasi" }. I've added more detail to the error if we encounter that they indeed have a wasi-http handler exported but are still configured to use fermyon:spin/inbound-http:
Error processing request: no fermyon:spin/inbound-http instance found but wasi:http/incoming-handler was found instead.
Make sure to put `executor = { type = "wasi" }` under [component.trigger] in the spin.toml manifest.

How can we improve?
There are two ways we can make this better:

Default to executor = { type = "wasi" } for manifest v2. Unfortunately, I don't this is possible right now since that config is shared between both manifest versions. I'm not sure how hard this would be to change so that the config could have a different default depending on the version. cc @lann
My preferred solution: we remove executor = { type = "wasi" } completely and rely on inspecting the component binary to know whether to use fermyon:spin/inbound-http or wasi:http/incoming-handler (with a default to wasi:http/incoming-handler should both be present). cc @dicej

Thoughts?

@rylev "follow the compiler errors" is what I hoped for - delighted to see this and +1 to inspecting the binary if we can

Tests are failing because we haven't implemented the outbound http calls to the same service yet in wasi-http. I'll do that tomorrow.


VRAM usage with adding and removing WorldObjects

I've been looking into VRAM usage with adding and removing WorldObjects, here's some things that I found:
With a Qt canvas it seems like WorldObjects are garbage collected and GPU VRAM is freed only after mouse movements on the canvas even after the WorldObject has visibly been removed from the scene.
This example uses nvidia-smi:

Creates a 4096x4096 image when you double click on the canvas.
Click on the image to remove it from the scene and call del on it. GPU VRAM is not freed.
Make a mouse movement on the canvas after the image has been removed, GPU VRAM gets freed. But the GPU VRAM remains utilized until you make this mouse event.

import numpy as np
from wgpu.gui.auto import WgpuCanvas, run
import pygfx as gfx
import subprocess

canvas = WgpuCanvas()
renderer = gfx.WgpuRenderer(canvas)
scene = gfx.Scene()
camera = gfx.OrthographicCamera(5000, 5000)
camera.position.x = 2048
camera.position.y = 2048

def make_image():
    data = np.random.rand(4096, 4096).astype(np.float32)

    return gfx.Image(
        gfx.Geometry(grid=gfx.Texture(data, dim=2)),
        gfx.ImageBasicMaterial(clim=(0, 1)),
    )

def draw():
    renderer.render(scene, camera)
    canvas.request_draw()

def print_nvidia(msg=""):
    print(msg)
    print(
        subprocess.check_output(["nvidia-smi", "--format=csv", "--query-gpu=memory.used"]).decode().split("\n")[1]
    )
    print()

def add_img(*args):
    print_nvidia("Before creating image")
    img = make_image()
    print_nvidia("After creating image")
    scene.add(img)
    img.add_event_handler(remove_img, "click")
    draw()
    print_nvidia("After add image to scene")

def remove_img(*args):
    img = scene.children[0]
    scene.remove(img)
    draw()
    print_nvidia("After remove image from scene")
    del img
    draw()
    print_nvidia("After del image")
    renderer.add_event_handler(print_nvidia, "pointer_move")

renderer.add_event_handler(add_img, "double_click")

draw()
run()

This outputs:
Before creating image
73 MiB

After creating image
73 MiB

After add image to scene
137 MiB

After remove image from scene
137 MiB

After del image
137 MiB

<pygfx.objects._events.PointerEvent object at 0x7fa186d8f970>
73 MiB

<pygfx.objects._events.PointerEvent object at 0x7fa186d8f5e0>
73 MiB

To follow up from #382 , with jupyter the situation is more messy. As Korijn mentioned here: https://github.com/pygfx/pygfx/issues/382#issuecomment-1310186390
If anyone runs into issues with jupyter in the future, in fastplotlib I'm working on a workaround where all WorldObjects are stored in a dict that fastplotlib uses internally, and only weakref proxies are used to access the WorldObject so that they are never directly exposed to any references on the jupyter side: https://github.com/kushalkolar/fastplotlib/pull/160

BTW: If anyone knows how to get the GPU memory consumption on MacOS, that'd be great :)

Or for any GPU that is not NVidia, for that matter!

If I use this then the VRAM is cleared immediately after the object is removed from the scene:
renderer.request_draw(draw)
run()

However with this it requires an event to clear, otherwise VRAM will linger even for minutes:
draw()
run()

The same code also works with garbage collection in jupyter. However if you run a jupyter cell such that it ends with a WorldObject (calls the __repr__), then it does not get garbage collected.
I can help create a note in the jupyter-rfb repo with some examples and suggest using weakreferences if you need to interact with WorldObjects on the jupyter side (unless you think there's a better way?). Anyways I'll open up an issue there.

However with this it requires an event to clear, otherwise VRAM will linger even for minutes:

During that time, are there any new draws? I suspect it's more related to a draw being performed (which then triggers GPU''s GC in some way), rather than events.

However if you run a jupyter cell such that it ends with a WorldObject (calls the __repr__), then it does not get garbage collected.

I can help create a note in the jupyter-rfb repo with some examples and suggest using weakreferences if you need to interact with WorldObjects on the jupyter side (unless you think there's a better way?). Anyways I'll open up an issue there.

Yeah, a PR or issue would be nice. I think explaining the gotcha's and some ways to prevent that would be nice, but suggestion weakrefs in user code may be a bit much? :)

BTW: If anyone knows how to get the GPU memory consumption on MacOS, that'd be great :)

Or for any GPU that is not NVidia, for that matter!

nvtop works for AMD GPUs on linux at least!

And I just learned that I actually have an RX 570 not a 470. :laughing:


Encode files based on their encoding

/kind feature
Describe the solution you'd like
with the addition of https://github.com/kubernetes-sigs/cluster-api-bootstrap-provider-kubeadm/pull/204 users have a choice of file encoding. It would be nice if we automatically encoded files for them if the content was not encoded. This is tricky though because how can we tell if the content is encoded or not?
Anything else you would like to add:
/milestone v0.1.x
/priority longterm-important

Hi @chuckha,
You could possibly do something like this.

This might actually help with userdata size limits, especially if we ensure base64 and gzip as the output by default.

The issue becomes the interpolation by cloud-init. However, I once did some tests, and it's much more efficient to leave everything plain-text and encode the bootstrap data than double-encoding the contents and the envelope

This is from last year, but the results should still be relevant. It was even regarding cloud-configs.

-rw-r--r--@  1 akutz  staff    94K Aug 28 11:39 cc.base64.base64
-rw-r--r--@  1 akutz  staff    32K Aug 28 11:40 cc.base64.gzip
-rw-r--r--@  1 akutz  staff    51K Aug 28 11:38 cc.gzip.base64
-rw-r--r--@  1 akutz  staff    31K Aug 28 11:41 cc.gzip.gzip
-rw-r--r--@  1 akutz  staff    22K Aug 28 11:49 cc.plaintext.gzip
-rw-r--r--@  1 akutz  staff    23K Aug 28 11:49 cc.urlencode.gzip

Each file is cloud config data. The first extension indicates how the child documents are encoded. The second extension indicates how the outer document is encoded. As you can see from comparing cc.gzip.gzip and cc.base64.gzip, there is a very minor improvement if child content is compressed prior to being included in the outer content. But it’s very minor.
Now, cc.plaintext.gzip is of course the most compressed. Unfortunately it represents the inner-content as plain-text. This is not possible in production thanks to the outer content’s rules about valid characters.
However, it occurred to me to consider using URL encoding for the inner content instead of base64 encoding. The URL encoding should make the characters safe for YAML-transport, and look at the results! Only fractionally worse than the inner-content as plain-text.
And yet, unfortunately once more, cloud config doesn’t support URL encoding for its file content (https://cloudinit.readthedocs.io/en/latest/topics/examples.html#writing-out-arbitrary-files):

encoding can be given b64 or gzip or (gz+b64).

In the end it looks like gzip+gzip is the best solution for the situational constraints. Without those restrictions in the way, keeping the inner content as plain-text offers the best compression.

/priority important-longterm


jCarouselLite - v1.1 - width not getting auto adjust while resize the browser

Hi,
I’m using jCarouselLite - v1.1 framework for carousel. Width of the carousel not getting auto adjust while doing resize the browser. Please help me to resolve this issue
Thanks in advance,
Rcoyajee

Hello, I got the same issue. Even the height of the  elements changes while resizing. Is this responsive?


Roll Flutter Engine from 2ed05f0068e2 to 82d7c1b2c268 (2 revisions)

https://github.com/flutter/engine/compare/2ed05f0068e2...82d7c1b2c268
2024-12-08<EMAIL_ADDRESS>Roll Fuchsia Linux SDK from __h1RRphItwU5H0tL... to BFJjwUVtBDA2mqqpH... (flutter/engine#57050)
2024-12-07<EMAIL_ADDRESS>Roll Skia from d1e261ca7f6f to 76c51c6e13df (3 revisions) (flutter/engine#57042)
Also rolling transitive DEPS:
fuchsia/sdk/core/linux-amd64 from __h1RRphItwU to BFJjwUVtBDA2
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC bdero<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Commit queue failed; closing this roll.


link to paper

hi, do you have the link to your paper ?

The paper will be published in ICASSP 2022, and will be available after conference ends.

got it, thanks ! i've also indicated interest to network with you over email. do let me know if you're coming over for icassp 2022 !


Runtime POI sprite colors

With #764 merged, we can now set the color of monochrome icons at runtime without a loss in quality. This PR enables such functionality for POI icons. This comes with a number of advantages as we build out the POI layer:

Managing colors is much easier when they're defined by variables rather than in dozens of individual SVG files
We could use the same icon in different colors without adding more sprites (e.g. RV park vs. RV dealership)
We could support multiple color schemes with a single sprite sheet (e.g. dark theme or high contrast)

I was able to generalize some code from the shield-drawing for this. I'm definitely open to suggestions around the implementation, I'm not very picky about what code lives where.

I believe we need an update in the contributor's guide with this change. Currently it instructs POI contributors to color their SVG icons, whereas now they need to make black and white icons but assign them to one of the POI categories.

I believe we need an update in the contributor's guide with this change.

Done. Let me know if anything needs clarity.


[FEAT] Improve SASS Linting Rules

:bulb: Feature request
Feature Name
Improve SASS Linting Rules. These rules have breaking errors and will need to be addressed one by one.
Possible implementation of: https://github.com/sasstools/sass-lint/blob/develop/docs/rules/property-units.md
The Desired Behavior
"brace-style": [
      2,
      {
        "style":"stroustrup"
      }
      ],
"border-zero": 2,
"clean-import-paths": 2,
"max-line-length": 2,
"no-color-literals": [
      2,
      {
        "allow-rgba": true
      }
    ],
"no-duplicate-properties": 2,
"no-empty-rulesets": 2,
"no-trailing-whitespace": 2,
"no-transition-all": 2,
"quotes": [
      2,
      {
        "style": "single"
      }
    ]
"space-around-operator": 2,
"variable-name-format": [
      2,
      {
        "allow-leading-underscore": false
      }
    ]
"zero-unit": 2

Your Use Case
As a developer, I would like the codebase to be consistent and neat.
Prior Work

Environment

Daffodil version: X.Y.Z
Angular version: X.Y.Z

For Tooling issues:
- Node version: XX
- Platform:

Others:

Depends on #310


Torque sensor implementation + iiwa example

@ivanbergonzani @jbmouret after our private discussions, I think this is ok to be merged, no?


Security testing... Please ignore z ogmrjx

Security testing... Please ignore z ogmrjx

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


Dark mode has issues

dark-mode has some issues
Originally posted by @toratalet in https://github.com/T-Ev/TwitterSearchTokenTest/issues/5#issuecomment-1326074415

I believe it is a racing condition.
The search.listBox() was not ready to add class for it.
When I debug, it is working fine

https://github.com/T-Ev/TwitterSearchTokenTest/blob/7a172b6247ff9ba41955805bfe6d23aefb63ed78/script.js#L74
  listBox: () => document.querySelector("[role=listbox]") || document.querySelector("[role=search] div.r-zchlnj"),
is failing
css class name might be random?!

Can you give the fixed script in my PR a try and see if it works for you?

Awesome Thanks <3 You rock!


Plots: Ability to zoom and maybe pan

Is it possible to zoom the metrics plots within a selected local rectangular window as in TensorBoard? I couldn't figure out how if. Selecting a rectangular zoom window and zooming out again fully via a simple interaction (e.g., double click as in TensorBoard) would be quite useful. Also being able to then pan that window would be nice (SHIFT + left click drag in TensorBoard).

This is not currently possible.
@daavoo @dberenbaum is this behaviour something that Plotly will be able to provide?

It looks to be possible: https://plotly.com/chart-studio-help/zoom-pan-hover-controls/

@dberenbaum do we have an epic / story for the Plotly migration? so that we can put the requirements like this into that story.

Added a tasklist in https://github.com/iterative/dvc-render/issues/7 to keep track, although I think the first step will be just trying to reach parity with the current vega-lite implementation.

We can do this with a simple update to the Vega template. The plot can be zoomed in with the mouse wheel. For the extension, I would suppress the behaviour unless the plot is focused/zoomed:
https://github.com/iterative/vscode-dvc/assets/37993418/31c404a5-328a-423b-8402-c1f2d5d35c24
WDYT?
cc @daavoo
Note: I cannot currently get the zooming behaviour to work for the smooth template but I will spend a little bit of time trying to make it work before raising a PR.

Further demos available at https://github.com/iterative/vscode-dvc/pull/4629

Great, thanks for adding this!
Unfortunately it isn't yet working for me when using a custom template based on https://github.com/iterative/vscode-dvc/issues/4532#issuecomment-1685483245. Even after I commented the stages.<stage>.metrics.template line in the dvc.yaml in the workspace, it is still using the previously used template. I guess it's cached somewhere as part of an experiment run?

If you can share your template with some dummy data in a Vega editor then I should be able to get it working for you.

If you can share your template with some dummy data in a Vega editor then I should be able to get it working for you.

I believe I figured out the tooltip related issue (cf. https://github.com/iterative/vscode-dvc/issues/4532#issuecomment-1711518022). Will need to wait until I run another experiment it seems before I can get DVC CLI to use the updated template and test out the zoom and pan feature within the extension. Unless there is another way I can tell DVC which template to use? It ignores the template specified in the dvc.yaml of the workspace, even after committing it with Git.

It ignores the template specified in the dvc.yaml of the workspace, even after committing it with Git.

It it the same in the DVC - dvc plots show?

It it the same in the DVC - dvc plots show?

Yes, this was also the case when using the CLI.

FYI With the template provided by @mattseddon at https://github.com/iterative/vscode-dvc/issues/4532#issuecomment-1712964405 and zoom and pan works like a charm!


[Bug] "unexpected end of file - ; expected" when trying to iterate over loadedMods

Issue Description:
Trying to get a list of all mods doesn't work.
What happens:
[INITIALIZATION][CLIENT][ERROR] :1 > unexpected end of file - ; expected
What you expected to happen:
List all mods in the log.
Script used:
script file
import crafttweaker.mods.ILoadedMods;

print("listing mods...");

for mod in loadedMods {
    print( mod.id ~ " + " ~ mod.name );
}

print("done!");

crafttweaker.log file:
crafttweaker.log

Affected Versions:

Minecraft: 1.12.2
Forge: <IP_ADDRESS>76
Crafttweaker: 4.1.15
Using a server: no

Transfered to ZS because that's a (known) ZS issue.
Fixed in an upcoming PR


Add Projects link to the navbar

Is your feature request related to a problem? Please describe.
The projects section is the main part of the page, but it is present down in the footer
Describe the solution you'd like
I want to add the projects bar to the navbar so that users can access it easily

@AnirudhPanda This would be a good feature if added, so that users can go to the project section from the navbar. Have a look at it


Min attribute works only on the first digit

I have an input number with a min value, 5:
<form action="myPage" method="post" novalidate data-parsley-validate>
    <input name="frequency" value="5" type="number" min="5" required />
</form>

When I set the value 10, I have the error "This value should be greater than or equal to 5.". When I set the value between 5 and 9, or a value greater than 50, it works fine.
It seems that the check is only on the first digit.
Is it a bug?

Could be yes. Could you please provide a quick jsfiddle to show the bug in action?
Th

I don't reach to reproduce the problem on a jsfiddle.
Never mind, I will use my js code.
Thanks!


Use one linter from language A in another language B (phpcs in js and css files)

The phpcs linter supports PHP, JS and CSS files, the wordpress standard have rules to sniff JS and CSS files also, is there a way to use phpcs in this files from ale?

Does it require a flag for checking JS and CSS files? If so, someone should add JS and CSS linter definitions for phpcs.

No, looks like it doesn't require a custom flag.
JavaScript File:
$ phpcs --standard=WordPress-Extra -s wp-content/plugins/foo/js/foo.js

FILE: .../wp-content/plugins/foo/js/foo.js
--------------------------------------------------------------------------------------------------------
FOUND 15 ERRORS AND 2 WARNINGS AFFECTING 10 LINES
--------------------------------------------------------------------------------------------------------
  4 | ERROR   | [x] Expected 1 spaces after opening bracket; 0 found
    |         |     (PEAR.Functions.FunctionCallSignature.SpaceAfterOpenBracket)
  4 | ERROR   | [x] Expected 1 spaces before closing bracket; 0 found
    |         |     (PEAR.Functions.FunctionCallSignature.SpaceBeforeCloseBracket)
  5 | ERROR   | [x] Empty lines are not allowed in multi-line function calls
    |         |     (PEAR.Functions.FunctionCallSignature.EmptyLine)
  9 | WARNING | [x] Equals sign not aligned with surrounding assignments; expected 5 spaces but found 1
    |         |     space (Generic.Formatting.MultipleStatementAlignment.NotSameWarning)
...
--------------------------------------------------------------------------------------------------------
PHPCBF CAN FIX THE 17 MARKED SNIFF VIOLATIONS AUTOMATICALLY
--------------------------------------------------------------------------------------------------------

Time: 72ms; Memory: 6Mb

PHP file:
$ phpcs --standard=WordPress-Extra -s wp-content/plugins/foo/foo.php

FILE: .../wp-content/plugins/foo/foo.php
--------------------------------------------------------------------------------------------------------
FOUND 7 ERRORS AND 12 WARNINGS AFFECTING 16 LINES
--------------------------------------------------------------------------------------------------------
   1 | ERROR   | [ ] Class file names should be based on the class name with "class-" prepended. Expected
     |         |     class-plugin.php, but found foo.php.
     |         |     (WordPress.Files.FileName.InvalidClassFileName)
  84 | ERROR   | [ ] Processing form data without nonce verification.
     |         |     (WordPress.CSRF.NonceVerification.NoNonceVerification)
  85 | ERROR   | [ ] Processing form data without nonce verification.
     |         |     (WordPress.CSRF.NonceVerification.NoNonceVerification)
 114 | WARNING | [ ] Processing form data without nonce verification.
     |         |     (WordPress.CSRF.NonceVerification.NoNonceVerification)
 115 | WARNING | [ ] Processing form data without nonce verification.
...
--------------------------------------------------------------------------------------------------------
PHPCBF CAN FIX THE 2 MARKED SNIFF VIOLATIONS AUTOMATICALLY
--------------------------------------------------------------------------------------------------------

Time: 113ms; Memory: 8Mb

CSS file:
$ phpcs --standard=WordPress-Extra -s wp-content/themes/bar/css/owl.theme.css

FILE: .../wp-content/themes/bar/css/owl.theme.css
---------------------------------------------------------------------------------------------------
FOUND 2 ERRORS AFFECTING 2 LINES
---------------------------------------------------------------------------------------------------
  2 | ERROR | [x] Whitespace found at end of line (Squiz.WhiteSpace.SuperfluousWhitespace.EndLine)
 79 | ERROR | [x] File must end with a newline character (Generic.Files.EndFileNewline.NotFound)
---------------------------------------------------------------------------------------------------
PHPCBF CAN FIX THE 2 MARKED SNIFF VIOLATIONS AUTOMATICALLY
---------------------------------------------------------------------------------------------------

Time: 53ms; Memory: 8Mb

One thing you can do easily is alias the filetype and set the linters for the aliased filetype.
" Use css and php linters for CSS files.
let g:ale_linter_aliases = {'css': ['css', 'php']}
" Use only phpcs for CSS files.
let g:ale_linters = {'css': ['phpcs']}

See :help g:ale_linter_aliases and :help g:ale_linters for more information.

Thanks, that did the trick!


Line chart: focus on a single point tooltip should be possible. Not every point should light up on mouseover / mouse click.

Don't think this is supported by ChartJS, although you could try editing the TooltipTemplate.. Not sure if you get enough context/data on which point is selected.

This is not possible in ChartJS


added post for DeCOr-MDS

@wxli0 : there seems to be some conflict associated with two files. Can you check before re-submitting the PR?


Error during training of SYMNet with Oasis data set

Hi,
I really enjoyed reading your paper and I want to reproduce the results.
I am currently trying to train the model with the OASIS data set using the example file you provided ("Train_sym_neurite_oasis.py").
However I am hindered by two major problems:
Problem 1:
The validation scores are not even close to your results. Also the value doesn't seem to change at all, which is really confusing to me.
My validation scores:
0:0.554038160843976
5000:0.585584165076553
10000:0.585584165076553
15000:0.585584165076553
20000:0.585584165076553
25000:0.585584165076553
30000:0.585584165076553
35000:0.585584165076553
Your validation scores:
0:0.570166888906167
5000:0.7349817233331957
10000:0.7674420857250869
15000:0.7831680992948633
20000:0.7861187128159433
25000:0.7941986866278279
30000:0.792603563494231
35000:0.7965674164395773
Problem 2:
At some point the overall loss becomes negative infinity and then NaN.

Afterwards the next validation will always cause an division-by-zero-error.

This seems to happen every time. I am using the default parameters of the file.

Do you have any idea how to solve this problems? I would really appreciate your help on this issues.
Best regards
Marcel

Hi Marcel,
This is weird. I tested this script many times and it works well with the preprocessed OASIS dataset in https://github.com/adalca/medical-datasets/blob/master/neurite-oasis.md.
I notice that your Dice score at iteration 0 is different from mine. Where did you download your OASIS dataset? Could you print out the training and validation files you used in Train_sym_neurite_oasis.py? (Lines 87 and 148-152)
Regards,
Tony

Hi Tony,
thank you for the quick reply. I downloaded the dataset from the link https://github.com/adalca/medical-datasets/blob/master/neurite-oasis.md. There seems to be only one version with 3D images ("neurite-oasis.v1.0").
Output of training files:
(Line 87)   names = sorted(glob.glob(datapath + '/OASIS_OAS1_*_MR1/aligned_norm.nii.gz'))[0:255]

...

Output of validation files:
(Line 149)   fixed_img = sorted(glob.glob(datapath + '/OASIS_OAS1_MR1/aligned_norm.nii.gz'))[255]
(Line 150)   fixed_label = sorted(glob.glob(datapath + '/OASIS_OAS1MR1/aligned_seg35.nii.gz'))[255]
(Line 151)   imgs = sorted(glob.glob(datapath + '/OASIS_OAS1MR1/aligned_norm.nii.gz'))[256:261]
(Line 152)   labels = sorted(glob.glob(datapath + '/OASIS_OAS1_MR1/aligned_seg35.nii.gz'))[256:261]

You also mentioned the difference in dice score in iteration 0. Isn't that somewhat expected because the initialization of weights in the network is random? (Correct me if I'm wrong here. ) I get different dice scores in iteration 0 every time I start the script. The values are usually between 0.4 and 0.6.
Thank you for your help.
Best regards
Marcel

Quick additional information:
This warning comes up every time when I run the scripts for training or inference.

Does this have any significance to the model?

You also mentioned the difference in dice score in iteration 0. Isn't that somewhat expected because the initialization of weights in the network is random? (Correct me if I'm wrong here. )

Yes, you are correct. I just want to make sure we are using the same data source.

This warning comes up every time when I run the scripts for training or inference.

This is a minor user warning and should not make a big difference in the result.
I cannot reproduce your result. Could you send me the "Functions.py", "Models.py" and "Train_sym_neurite_oasis.py" you used to see whether I can reproduce the same error?

Here you go.
SymNet_Files.zip

Hi @Tranquillar ,
I tried the code you provided, and it seems there is no problem at all.
Here is the log using your code:
Validation Dice log for SYMNet_neurite_oasis:
0:0.5447214704388855
1000:0.6589802244014441
2000:0.6850653705911428
Here is the log using the source code on Github:
Validation Dice log for SYMNet_neurite_oasis:
0:0.5297590205219744
1000:0.6597511465193313
Yet, I spotted two discrepancies between your code and the original one.

Left: your modified code (Train_sym_neurite_oasis.py) Right: the original code (Train_sym_neurite_oasis.py)
Since we use "tab" for indentation, the extra spaces in line 133 may cause an issue for some python compilers.
Try to remove the extra spaces as mentioned above, or re-download the training script and try again.
If the problem persists, I think it would be a non-trivial environmental problem and you may try it with another machine, if possible.

Thank you very much for looking into it.
I will try it on a different machine.

Do you mind telling me which cuda and pytorch versions you are using? I want to make really sure that there are as little differences as possible.
Thanks in advance 😊

Sure. I am using Ubuntu 16.04 LTS + Pytorch 1.9.0+cu111.
The code is tested with an NVIDIA RTX 3080 GPU (Driver version: 460.84, CUDA Version: 11.2).

Hi Tony,
the situation is resolved. I ran the code in a docker container with the exact pytorch and cuda version you used.

Ubuntu 16.04 LTS + Pytorch 1.9.0+cu111.

Everything looks a lot better now. This is the validation score log after 55k iterations:
0 : 0.4097486243230383
5000 : 0.7047512729914296
10000 : 0.7209373161013326
15000 : 0.7476094422734847
20000 : 0.7573324792065288
25000 : 0.76341926686527
30000 : 0.7683853719520911
35000 : 0.7717567312637159
40000 : 0.7773653384358569
45000 : 0.7856832570252698
50000 : 0.7811629084686469
55000 : 0.783746416889304
Thanks again for your help. 👍
I will now start training the network with my own data.

Quick summary of the issue and solution in case anyone else experiences this:
My Setup

GPU: NVIDIA GeForce RTX 3090
PyTorch: 1.10.2
Cuda: 11.3

Symptoms:

The dice scores stay constant over multiple checkpoints or sometimes even fall close to zero.
The overall training loss becomes negative infinity or NaN.
The overall training loss starts at -0.25 then jumps up to about 4.0 within the first 1000 iterations and then slowly approaches -0.3 without ever getting better than that.

Solution:

Run the code in a docker environment with pytorch version 1.9.0 and cuda version 11.1. (The docker image I used is "pytorch/pytorch:1.9.0-cuda11.1-cudnn8-devel").

Good to hear that. Thanks for your summary. 👍
If you are looking for a state-of-art registration method, you may also check out our latest image registration framework for medical images at https://github.com/cwmok/Conditional_LapIRN.


Separate Tutorial Videos, add check

Is your feature request related to a problem with the curriculum? Please describe.
For the hands-on tutorials in each section, create a more clear part, (separate section) in the curriculum
Describe the solution you'd like
See the Curriculum embedded in the pages
IPFS- https://protocol-labs.gitbook.io/launchpad-curriculum/launchpad-learning-resources/ipfs#tutorials
IPLD- https://protocol-labs.gitbook.io/launchpad-curriculum/launchpad-learning-resources/ipld#tutorials
libp2p- https://protocol-labs.gitbook.io/launchpad-curriculum/launchpad-learning-resources/libp2p#tutorials
Create a separate section, with 1 or two questions after as a check to see if they did the tutorials
Also, come up with a planned time to do these with cadets
Where Can we find out more about this topic?
How can you contribute and help create this content?
Additional context
Add any other context or screenshots about the feature request here.

Being done in different ticket


get attribute return value

How to obtain multi-attribute value returned from the server

I belive you can not. If xml returned by CAS/p3/serviceValidate contains more than one value, only the last one is availeble in cas_response.attributes, problem is here(?):
'''
for key in xml_document.documentElement.attributes.keys():
result[str(key)] = str(xml_document.documentElement.getAttribute(key))
'''


feat(sqlcon): Cleanup test db docker images

Test databases in docker images are now cleaned up automatically after the test finishes with t.Cleanup().
Previously, databases started with the dockertest.RunTest{DB}(*testing.T) functions could not be cleaned up.
Related Issue or Design Document
Closes Issue #460
Checklist

[x] I have read the contributing guidelines
and signed the CLA.
[x] I have referenced an issue containing the design document if my change
introduces a new feature.
[x] I have read the security policy.
[x] I confirm that this pull request does not address a security
vulnerability. If this pull request addresses a security vulnerability, I
confirm that I got green light (please contact
<EMAIL_ADDRESS>from the maintainers to push
the changes.
[x] I have added tests that prove my fix is effective or that my feature
works.
[x] I have added necessary documentation within the code base (if
appropriate).

Further comments

The Run{DB}() (string, error) family of functions still do not return something to be cleaned up by, but adding a cleanup return function would change the API.

@aeneasr could you take a look?


Update CI workflow - molecule scenarios

Change Summary
Update CI workflow - molecule scenarios

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes)
[ ] Documentation content changes
[x] Other (please describe): Update CI Workflow

Related Issue(s)
Component(s) name
arista.avd
Proposed changes

Update Molecule scenario list

Add eos_designs_unit_test to MOLECULE_SCENARIOS.txt to be included in make refresh-facts
Remove eos_l3ls_evpn-twodc-5stage-clos from MOLECULE_SCENARIOS.txt (Scenario has a new name)
Add evpn_underlay_rfc5549_overlay_ebgp to eos_designs CI workflow to ensure test coverage

Update CI triggers

Avoid eos_cli_config_gen tests to be triggered by any other molecule update
Simplify list of triggers for eos_cli_config_gen

How to test

Checklist:

[ ] My code has been rebased from devel before I start
[ ] I have read the CONTRIBUTING document.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have updated molecule CI testing accordingly
[ ] All new and existing tests passed (pre-commit, make linting and make sanity-lint).

@titom73 please review this one


og tag date fixed and jquery selector duplicated warning comments fix

duplicated comments fix by phpstorm
og description date string fix

It will close because of PR process conflicted


Track recipe burn times separately

This will avert the need for the global cook time and the prevention of smelting recipes with longer than the default cook time.
It will also fix a behavior where reducing the global cook time config prevents vanilla recipes from being smelted.

Implemented in 1.21


Validate image update

Description
Add validation if we can generate the update image based on current distribution
Fixes # (issue)
Type of change
What is it?

[ ] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Documentation update
[ ] Tests update
[ ] Refactor

Checklist:

[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[X] I have added tests that prove my fix is effective or that my feature works
[X] New and existing unit tests pass locally with my changes
[ ] I run make pre-commit to check fmt/vet/lint/test-no-fdo

Test results are available in Ibutsu:
https://url.corp.redhat.com/ibutsu-runs-d0eefe78-1f0a-4209-b2ab-d2aff5e58e09


Base64: add @lazy and fix linter

prettier wants to remove indentation for lines bellow @lazy  but eslint wants to add indentation.
Technical solution: "VariableDeclarator": 0, in file .eslintrc

we will see if the problem persist after solving https://github.com/massalabs/massa-as-sdk/issues/53

close it because won't fix: https://github.com/massalabs/massa-as-sdk/issues/53#issuecomment-1322241489


Add Task 2 description and indicate as bonus / optional.

Added Task 2 (bonus task) description using Biodmedusum's description with some edits . Please check.


service discovery: Remove use of zap logger

What does this PR do?
Remove a use of a custom logger, and instead use the agent's log package.

Motivation
Redundant fork in logging.

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

/merge


Pin Markdown2 and BeautifulSoup Versions

Description
Pin the versions of markdown2 and BeautifulSoup4 to ensure that implicit version changes don't break the task to convert our README.md files into HTML files that are included in the Javadoc JARs.
All SDK Contribution checklist:

[x] The pull request does not introduce [breaking changes]
[x] CHANGELOG is updated for new features, bug fixes or other significant changes.
[x] I have read the contribution guidelines.

General Guidelines and Best Practices

[x] Title of the pull request is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[x] Pull request includes test coverage for the included changes.

/azp run java - cosmos

/azp run java - cosmos

/check-enforcer override

PR doesn't affect testing steps, validation complete in build steps.


Lack of documentation

I am not sure why you deleted usage examples from the README but now, as an end-user, I do not know how to use the component in my applications.

I think at least should have documentation about what you can do with the vue-component on a Wiki.
What do you think?

I agree guys, it's just finding time to do it.
When I changed to using webpack, I rebuilt the repo from the ground up. This is why we have lost the demo files and the old readme.
I intend to add the old readme back in and also to create a live demo area somewhere either in github.io of jsfiddle.net or something.
Hold tight, but don't hold your breath!

Thanks @charliekassel.

Thanks @charliekassel
El El mar, 20 de septiembre de 2016 a la(s) 23:52, Konstantin Komelin <
<EMAIL_ADDRESS>escribió:

Thanks @charliekassel https://github.com/charliekassel.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/charliekassel/vuejs-datepicker/issues/17#issuecomment-248511158,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB0C2TrWiWsxCVC_6bVxpm43GqecZ4-qks5qsLgAgaJpZM4J6e9-
.

--
Saludos cordiales,
Ing. Javier Díaz Chamorro
<EMAIL_ADDRESS>Desarrollador web y entuasiasta de VueJS / Typescript
Teléfono: +521 (753) 116-53-64
Web: http://coderdiaz.me

@coderdiaz what is this?

I've returned the old readme in lieu of proper documentation.


Carefully consider the overloads we want for DownloadObject

There are four choices the user can make for a download call:

The source, which may be specified as an Object or a bucket/name pair
The target, which may be specified a local file name or a Stream
Sync/async
Whether or not there are options (including progress reporting)

That naturally leads to 16 overloads (or two pairs of 8 overloads, in that the sync and async methods have different names). This feels like overkill.
We can avoid overloads for the first two choices if we say that it's always to a Stream (forcing callers to call File.OpenWrite themselves) or force the bucket/sourceName to be specified (forcing callers to use obj.Bucket, obj.Name if they have an Object already). For the latter case, we could force callers to create an Object if they don't have one already instead. Both cases feel a little odd to me.
I'll probably code up all 16 methods for the moment but without documentation, and we can pick which ones to cull.

Oh, and if we ever have the ability to get a return value of a stream, that's presumably another set of methods (although not a doubling...)

Have you considered the fluent pattern?
service.Download().withSource(...).withTarget(...).withOptions(...).ExecuteAsync()...
Actually, I think 16 overloads are better.
On Mon, Nov 30, 2015 at 9:27 AM, Jon Skeet<EMAIL_ADDRESS>wrote:

Oh, and if we ever have the ability to get a return value of a stream,
that's presumably another set of methods (although not a doubling...)
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/gcloud-dotnet/issues/21#issuecomment-160696582
.

// cc @ivannaranjo @mmdriley @chrsmith @csells

I would say that the target being a stream is a good compromise, having the user open the file is probably best since they know exactly how to do so, that is, permissions, whether to overwrite, append, etc, etc... So we could remove that overload right there.
As for the source, yes I think that we will have to bite the bullet and have both the object and one accepting the bucket and name, since it is going to be quite common to get objects, from listing them, and create the names directly, programmatically. I would like us to have also objects paths like gs://bucket/name/of/object.jpg similar to what gsutil allows, but that is probably a completely different discussion, and this would also add an extra overload :).
options/not-options I think are also necessary, this is where perhaps having default arguments might help? If we were to deviate from the TAP pattern perhaps?
Async/async I think are necessary and unavoidable. Although this said, one could just built it on the other.

What do the .NET file operations do here?

@SurferJeffAtGoogle A fluent pattern would help in this situation, but I don't believe that is idiomatic C#. e.g. I don't think there are any BCL classes that use a fluent approach.
@jskeet There is precident for having a method with a bazillion overloads. e.g. Console.WriteLine or MessageBox.Show. But I don't think we should be super-liberal in creating overloads. Why not just keep the simple case simple, i.e. don't allow custom options or an async variant for the most common download-to-file case? e.g.:

void DownloadFile(GcsObject gcsObject, string filePath)
Stream Download(GcsObject gcsObject, GcsOptions)
Task DownloadAsync(GcsObject gcsObject, GcsOptions)

This way the common case is simple and more advanced users can use the Async/Option-enabled variants to create some middle ground as needed.
Feel free to shoot this down out of principle. But I personally would optimize for reducing the number of methods we expose in total.

Unfortunately we can't currently have a method to return a stream to read from - we'd like to, but the download functionality in the core library isn't based on that idea, and we should add it there rather than in a wrapper.
In terms of asyncness - it would be pretty odd not to provide an async option these days.

We can always add more overloads later. :)

But we can't remove so we have to think about this carefully. I would agree that erring on the side of fewer overloads is the way to go. Later we can add more based on usage, and specifically issues/complaints.

Agree that we can't remove overloads after 1.0, although we've got plenty of opportunity for feedback before that. We'll want to get feedback on using optional parameters to remove a bunch of overloads too.

I think we're reasonably happy with where we are now.


adds title to plot_haplotype_clustering function

Adding a title to plot_haplotype_clustering() function with information on selected sample set/sample query, the genomic region and the number of SNPs found in that window.
I added a line for sample query, similar to H12/H1X functions. Not sure if that is really desirable, let me know and ill change it. Also have added prefix to title like sample query: or number of SNPs:, happy to remove if preferred.
Currently looks like this:

awesome, thanks!

Actually, an issue with this is it leads to titles with four lines, which end up encroaching the plot. I had previously put sample set and sample query on the same line if they are both specified. thoughts? could move the number of SNPs to the same line as genomic region? this might be nicer than having three lines for title anyway

for example:

pushed the change but happy to modify if preferred.

THanks @sanjaynagi, three line solution looks good to me. Very minor suggestion would be to put number of SNPs in brackets so it stands out a little more, e.g.:
genomic region: 2L:2,410-000-2,430,000 (3,351 SNPs)
Also note that the sample sets list can get very long, but can figure out how to deal with that later.

Thanks! did think it needed to stand out more. Done.

Thanks @sanjaynagi :sunglasses:


Memory fences and general improvements

Quoted from u/TDplay from this comment.
Todo

[x] Weak::to_trc race condition
[ ] Weak::clone race condition
[ ] impl Clone for SharedTrc
[x] Support no_std
[x] Trc::cmp documentation
[x] Fix Pointer behavior
[x] Use different Layout API.
[x] Use ptr::drop_in_place instead of ptr::read

Quote
https://github.com/EricLBuehler/trc/blob/89f3eb2ffec4f860b13620c82cd0f443ed6dcfeb/src/trc.rs#L245
Not entirely sure about this part. You seem to decrement and check the weak count, and then construct and drop a Weak (thus calling Weak::drop, which should also decrement and check the weak count).
It also seems like you only drop the data when the weak count reaches zero, which seems to defeat the point of supporting Weak pointers.
Another point is to perhaps consider using ptr::drop_in_place instead of ptr::read. It makes the intent more obvious, and it can make some optimisations more obvious to the compiler (since it doesn't need to reason about removing the copy). I think this would also allow you to support dynamically-sized types.
Trc::drop looks fine.
https://github.com/EricLBuehler/trc/blob/89f3eb2ffec4f860b13620c82cd0f443ed6dcfeb/src/trc.rs#L1148
Weak::to_trc has a race condition, leading to a possible use-after-free.
Initial state: We have a SharedTrc in thread A and a Weak in thread B.
Thread B calls Weak::to_trc
Weak::to_trc checks the strong count, and reads 1
Thread A drops the SharedTrc, decrementing the strong count.
SharedTrc::drop notices that the strong count is now zero, so it deallocates the data.
Weak::to_trc increments the strong count and constructs a Trc.
The Trc is now passed to user code, which access the contents, causing a use-after-free.
To resolve this, the zero-check and the increment need to be one atomic operation, and the increment needs to not happen if the zero check fails. fetch_update is perfect for this. Sadly, this is slower than fetch_add, but I can't see a way to avoid it, and it seems the standard library developers couldn't either.
https://github.com/EricLBuehler/trc/blob/89f3eb2ffec4f860b13620c82cd0f443ed6dcfeb/src/trc.rs#L1191
Clone for Weak technically has a race condition: if a program clones an absurd number of Weaks in different threads, with thread being pre-empted before it can call abort, it may be possible to overflow the weak count. In practice, I don't think any real program will ever do this, and the actual likelihood of this behaviour is slim.
That's the big stuff out of the way, on to the small nitpicks:
Clone is not implemented for SharedTrc, this feels like an oversight.
You might be able to support no_std. Add this to your lib.rs:
#![cfg_attr(not(test), no_std)]

extern crate alloc;
#[cfg(feature = "force_lock")]
extern crate std;

It will then throw errors at every use of std. Replace these with either core or alloc.
https://github.com/EricLBuehler/trc/blob/89f3eb2ffec4f860b13620c82cd0f443ed6dcfeb/src/trc.rs#L899
Documentation for Trc::cmp doesn't seem right.
https://github.com/EricLBuehler/trc/blob/89f3eb2ffec4f860b13620c82cd0f443ed6dcfeb/src/trc.rs#L793
Behaviour of the Pointer formatting seems a little strange. Trc is a pointer, so it should probably print the address the Trc points to. This would also be in-line with what the standard library smart pointers do: Arc, Rc, Box, &T, and &mut T all implement Pointer unconditionally.
https://github.com/EricLBuehler/trc/blob/89f3eb2ffec4f860b13620c82cd0f443ed6dcfeb/src/trc.rs#L1043
There is no need for the unsafe call to Layout::from_size_align_unchecked, you can just use:
Layout::new::<SharedTrcInternal<T>>()

If you choose to support dynamically sized types, then you can instead use:
Layout::for_value

impl Clone for SharedTrc: Clones do not need any special sync because they can only be created from existing objects. However, refcount bounds checking is necessary.

Closed as all problems are fixed.


Missing checkpoints of pretrained models

Thanks for great works, will the weight files be  released?

Hi, we have released part of the weight files.


charts/osm: remove deprecated validating webhook config

Description:
The validating webhook was deprecated as a part of #3041

Affected area:

Functional Area

Install
[X]

CLI Tool
[ ]

Please answer the following questions with yes/no.

Does this change contain code from or inspired by another project? no

Did you notify the maintainers and provide attribution?

Is this a breaking change? no

Codecov Report

Merging #3398 (5df9754) into main (785de28) will decrease coverage by 0.03%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #3398      +/-   ##
==========================================
- Coverage   65.90%   65.86%   -0.04%
==========================================
  Files         169      169
  Lines        7839     7839
==========================================
- Hits         5166     5163       -3
- Misses       2643     2646       +3
  Partials       30       30

Flag
Coverage Δ

unittests
65.86% <ø> (-0.04%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/kubernetes/announcement_handlers.go
71.42% <0.00%> (-5.72%)
:arrow_down:

pkg/endpoint/providers/kube/client.go
78.21% <0.00%> (-1.00%)
:arrow_down:

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 785de28...5df9754. Read the comment docs.


double compliance check timeout for grc metrics test

Signed-off-by: Will Kutler<EMAIL_ADDRESS>https://github.com/open-cluster-management/backlog/issues/16546

/lgtm


gitlab-runner: Fix marshalling of TOML datetimes

Things done
As described in #356717, gitlab-runner now uses TOML date-time values in its configuration (namely the token_obtained_at and token_expires_at keys). As there is no JSON syntax for such values, remarshal refuses to serialise them without the --stringify flag. Thankfully, gitlab-runner seems to accept the stringified values without any complaints, so we can side-step this issue readily.
Fixes #356717.

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

I can confirm that this allows gitlab-runner can be started and restarted after this change.

Works on my machine (: thanks!


Adding check to make sure expected element in XML is present in config

We were seeing null reference exceptions when the wrong file was used.  This change should allow users to better diagnose the configuration issue.

Hi @jascam, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

It looks like you're a Microsoft contributor (Jason Campbell (MTPG)). If you're full-time, we DON'T require a Contribution License Agreement. If you are a vendor, please DO sign the electronic Contribution License Agreement. It will take 2 minutes and there's no faxing! https://cla.microsoft.com.

TTYL, MSBOT;

@johnballard please take a look

You will need to bump the version in the the task.json or else agents that already have the task won't get the updated version

:shipit:

@jmyersmsft good catch.  It should be updated now


feat: add pose stamped to psim

Related Issue(required)
#222
Description(required)
add or remove pose stamped topic from psim
candidate

/localization/pose_estimator/debug_pose
/localization/pose_estimator/fake_pose
/simulation/simple_planning_simulator/fake_pose

Review Procedure(required)
see node info current_pose
/simulation/simple_planning_simulator
  Subscribers:
    /control/command/control_cmd: autoware_auto_control_msgs/msg/AckermannControlCommand
    /control/command/gear_cmd: autoware_auto_vehicle_msgs/msg/GearCommand
    /control/command/hazard_lights_cmd: autoware_auto_vehicle_msgs/msg/HazardLightsCommand
    /control/command/turn_indicators_cmd: autoware_auto_vehicle_msgs/msg/TurnIndicatorsCommand
    /initialpose: geometry_msgs/msg/PoseWithCovarianceStamped
    /parameter_events: rcl_interfaces/msg/ParameterEvent
    /planning/scenario_planning/trajectory: autoware_auto_planning_msgs/msg/Trajectory
    /tf: tf2_msgs/msg/TFMessage
    /tf_static: tf2_msgs/msg/TFMessage
  Publishers:
    /localization/pose_estimator/fake_pose geometry_msgs/msg/PoseStamped
    /localization/kinematic_state: nav_msgs/msg/Odometry
....
  Service Clients:

  Action Servers:

  Action Clients:

Related PR(optional)
this can also be tested with pose2twist
ros2 launch pose2twist pose2twist.launch.xml input_pose_topic:=/curernt_pose

Pre-Review Checklist for the PR Author
PR Author should check the checkboxes below when creating the PR.

[x] Read commit-guidelines
[x] Assign PR to reviewer

If you are adding new package following items are required:

[ ] Documentation with description of the package is available
[ ] A sample launch file and parameter file are available if the package contains executable nodes

Checklist for the PR Reviewer
Reviewers should check the checkboxes below before approval.

[ ] Commits are properly organized and messages are according to the guideline
[ ] PR title describes the changes

Post-Review Checklist for the PR Author
PR Author should check the checkboxes below before merging.

[ ] All open points are addressed and tracked via issues or tickets

CI Checks

Build and test for PR / build-and-test-pr: Required to pass before the merge.
Build and test for PR / clang-tidy-pr: NOT required to pass before the merge. It is up to the reviewer(s). Found false positives? See the [guidelines][clang-tidy-guidelines].
Check spelling: NOT required to pass before the merge. It is up to the reviewer(s). See here if you want to add some words to the spell check dictionary.

@yukkysaito @kenji-miyake cc: @TakaHoribe
I mentioned this pr in .auto sync and approved to add.
I choose /localization/pose_estimator/debug_pose  instead of  /curent_pose

@taikitanaka3 Could you explain why /localization/kinematic_state isn't enough?
(Anyway, /current_pose should be removed.)

@kenji-miyake
pose2twist package assumes pose stamped topic from ndt scan matcher and there is no package that use pose topic from /localization/kinematic_state so it's not enough to it will be better to add odom2twist package or add pose publisher node.
https://github.com/autowarefoundation/autoware.universe/blob/tier4/proposal/localization/pose2twist/launch/pose2twist.launch.xml

For what use case do you need to run pose2twist in the planning simulation? :thinking:

@kenji-miyake
when testing calibration tools like steering offset estimation which needs ndt's pose because ekf needs parameter tuning
or testing pose2twitst node with simulation. so in case mocking ndt pose out put is necessary this topic is necessary.

when testing calibration tools like steering offset estimation which needs ndt's pose

Please link the design document of the calibration tool?

testing pose2twitst node with simulation

I believe this should be done with integration tests like launch_testing.

@kenji-miyake

Please link the design document of the calibration tool?
Ok I'm going to create it later.

close this now for low priority


Multiple round-trips to IDP when session_state is included in response

When using Keycloak, the session_state is included in the response by default.  That appears to cause oidc-react (or oidc-react-js?) to make multiple authentication requests in the background under Firefox at least.  Keycloak has an option under OpenID Connect Compatibility Modes to Exclude Session State From Authentication Response.  If I set that to "On", then it works as expected.
I've prepared a reproducer using the sample app and a keycloak docker image with a realm already set up.  The repos are here:
Dockerfile: https://github.com/jeblair/keycloak-sample
Sample app: https://github.com/jeblair/example-oidc-react
Here's how to run the reproducer:

add <IP_ADDRESS> keycloak to /etc/hosts
docker run -p8082:8082 jeblair/keycloak-sample
git clone https://github.com/jeblair/example-oidc-react
cd example-oidc-react
yarn start

You can log in to the app with user admin password admin.
You can log into the keycloak admin console at http://keycloak/ with user admin password kcadmin.
The login will work, but you should see multiple requests to keycloak after logging in.  It's also easy to see by looking at network traffic in devtools.
The sample app/reproducer breaks reliably for me in Firefox, but not Chromium.  However, in the actual application I'm working on, I also see the behavior in Chromium (perhaps a race condition with the session state and storage is involved).

Thanks for posting this, and with awesome detail too!
Unfortunately, I'm busy with a few launches at the moment (which is also the reason it has taken so much time to answer you). I have this on my list, and hope to get to it very soon!
Thank you for your patience, and feel free to do research/debugging and open pull requests!

Did you have any chance to look at this? I think i'm running into a similar issue

Does anyone want to help out on this?

Closing this as stale :)


refactor: change authorization description

Change:
Server should answer with status code 201 and corresponding message if dto is valid => Server should answer with status code 201 and newly created record if dto is valid - according to tests
Feat:
Server should answer with status code 409 and corresponding message if user with such login already exist
Need to edit tests according to this post

Please consider to add corresponding tests to template repo :)
After that please reopen this PR


[libvirt_manager] Update domain.xml.j2 to support baremetal instance

This patch:

Adds support to enable the bootmenu
Adds early RNG entropy[1], without this baremetal instance vms can fail with "Jitter RNG permanent health test failure" errors [2]
Update docs with disk_file_name: "blank" example using bootmenu_enable

[1] https://libvirt.org/formatdomain.html#id109
[2] Jira: OSPRH-1967
Jira: OSPRH-6841
As a pull request owner and reviewers, I checked that:

[x] Appropriate testing is done and actually running
[x] Appropriate documentation exists and/or is up-to-date:

[x] README in the role
[x] Content of the docs/source is reflecting the changes

/approve


Bug: Firefox "whitespace: nowrap" issue with the content editable element

Short description: "whitespace: nowrap" doesn't work correctly on Firefox with lexical.
Full description:
I was trying to built a "one-line" input with lexical so that it was similar to a usual input. For that I added properties "whitespace: nowrap" and "overflow: hidden" to the content editable element. (I have also tried to leave the content editable element and apply those properties to children. Didn't help neither.)
The problem appears only on Firefox (tested Chrome, was fine). The problem: you cannot type more than one "space" when your caret is at the end of the editor input. Another problem: when you type "Hi", press space and type "there" it becomes "Hithere" without a space in between.
It will work if you first press the space, then go to the beginning of the input and type. But if you leave your caret at the end of the input, it'll stop working. It just won't add any new spaces for some reason.
Lexical version: 0.9.2
Steps To Reproduce

Just open my example and try to type words separating them by "space"

Link to code example: https://codesandbox.io/s/solitary-morning-rg9j6c?file=/src/App.tsx
Here's the video that demonstrates that strange behavior:
https://user-images.githubusercontent.com/80093436/232549188-a82aa618-a901-4e49-b29a-9c0ddcbe107d.mp4
The expected behavior
I'm expecting to work just as a normal input. Without cutting spaces.
If you need further explanation, just let me know. I wish I had more time to dive into the source and find this problem, but I really don't have time for it now so I hope you'll understand where the problem is.

It's worth mentioning that I tried to make just a simple div with contenteditable="true", applying the styles I mentioned to it and put inside it another div and type the same text. It works fine. So... seems to be the library issue.

BTW, I checked the issue in the new version (0.10.0)
It is still there

I am seeing this in 10.0 as well.

I have created a branch and I will be attempting a fix here: https://github.com/rgathmann/lexical/tree/whitespace-nowrap-bugfix
So far, I have the nowrap feature to the playground and will be creating a test case shortly.

Just an update, I have figured out the issue I believe, still working on the correct place to put the fix.
In a content editable in Chromium, when multiple spaces are added, chrome will alternate between using a space character and using   as seen here:

-- Write your     own name here

However in Firefox doing the same thing, Firefox will only uses spaces like this:

-- Write your     own name here

With that in mind lets look at how this plays out inside Lexical in the playground with no wrap turned on. In both of these examples I have placed a console.log inside the $flushMutations function inside LexicalMutations.ts. To show the defect I type "a a" and look at the mutations which are fired.
In Chrome:

"a": The initial character does not trigger any mutations

span content: a

" ": The space character triggers two mutations, 'characterData' and 'characterData'

span content: a

"a": The final character also fires two mutations 'characterData' and 'characterData'

span content: a a

In Firefox:

"a": The initial character does not trigger any mutations

span content: a

" ": The space character triggers two mutations, 'characterData', 'childList', and 'characterData'

span content: a

"a": The final character also fires two mutations 'characterData' and 'characterData'

span content: aa

Here we can see that during the addition of the space character, Chromium sets the span contents to be a&nbspc;' however when I dig deeper, Firefox is actually trying to set the the contents of span to be a . To my understanding right now, Lexical is receiving that input, then firing the 'ChildList' mutation to remove the br tag. You can validate this is the issue by commenting out line 212 in LexicalMutations.ts which contains parentDOM.removeChild(addedDOM);`. While this is certainly not the fix, it shows that this is indeed the issue and Firefox spaces will work as intended.
I will continue working on a fix for this issue, but this should help others see the root cause.

I found another another issue that also involves the same whitespace: nowrap. This one occurs on Chrome.
This can be reproduced using the playground:

Edit the html and assign a custom element style to the p that wraps the span with white-space: nowrap;
Type "a a"
Hit backspace to delete the last "a"

The expected behavior is that it should show "a " on screen however it the cursor jumps back two spaces and it only shows "a". Further more, if you look at the contents of the span, it is showing "a " and the root->paragraph->text value is also showing "a " in the debug down below.

@rasulomaroff Have you tried? using white-space: pre instead of white-space: nowrap? This is working for me without any fixes to Lexical. Firefox may actually be working as intended because nowrap should collapse all whitespaces down. Where as pre will preserve the white spaces.

Interesting observations! Do you think this is intended behavior from Firefox?
Yes, I tried using pre and other possible options and everything worked as I expected them to.

I think this can be closed since it appears Firefox is behaving according to spec