[SPARK-19761][SQL]create InMemoryFileIndex with an empty rootPaths when set PARALLEL_PARTITION_DISCOVERY_THRESHOLD to zero failed

What changes were proposed in this pull request?
If we create a InMemoryFileIndex with an empty rootPaths when set PARALLEL_PARTITION_DISCOVERY_THRESHOLD to zero, it will throw an  exception:
Positive number of slices required
java.lang.IllegalArgumentException: Positive number of slices required
        at org.apache.spark.rdd.ParallelCollectionRDD$.slice(ParallelCollectionRDD.scala:119)
        at org.apache.spark.rdd.ParallelCollectionRDD.getPartitions(ParallelCollectionRDD.scala:97)
        at org.apache.spark.rdd.RDD$$anonfun$partitions$2.apply(RDD.scala:252)
        at org.apache.spark.rdd.RDD$$anonfun$partitions$2.apply(RDD.scala:250)
        at scala.Option.getOrElse(Option.scala:121)
        at org.apache.spark.rdd.RDD.partitions(RDD.scala:250)
        at org.apache.spark.rdd.MapPartitionsRDD.getPartitions(MapPartitionsRDD.scala:35)
        at org.apache.spark.rdd.RDD$$anonfun$partitions$2.apply(RDD.scala:252)
        at org.apache.spark.rdd.RDD$$anonfun$partitions$2.apply(RDD.scala:250)
        at scala.Option.getOrElse(Option.scala:121)
        at org.apache.spark.rdd.RDD.partitions(RDD.scala:250)
        at org.apache.spark.rdd.MapPartitionsRDD.getPartitions(MapPartitionsRDD.scala:35)
        at org.apache.spark.rdd.RDD$$anonfun$partitions$2.apply(RDD.scala:252)
        at org.apache.spark.rdd.RDD$$anonfun$partitions$2.apply(RDD.scala:250)
        at scala.Option.getOrElse(Option.scala:121)
        at org.apache.spark.rdd.RDD.partitions(RDD.scala:250)
        at org.apache.spark.SparkContext.runJob(SparkContext.scala:2084)
        at org.apache.spark.rdd.RDD$$anonfun$collect$1.apply(RDD.scala:936)
        at org.apache.spark.rdd.RDDOperationScope$.withScope(RDDOperationScope.scala:151)
        at org.apache.spark.rdd.RDDOperationScope$.withScope(RDDOperationScope.scala:112)
        at org.apache.spark.rdd.RDD.withScope(RDD.scala:362)
        at org.apache.spark.rdd.RDD.collect(RDD.scala:935)
        at org.apache.spark.sql.execution.datasources.PartitioningAwareFileIndex$.org$apache$spark$sql$execution$datasources$PartitioningAwareFileIndex$$bulkListLeafFiles(PartitioningAwareFileIndex.scala:357)
        at org.apache.spark.sql.execution.datasources.PartitioningAwareFileIndex.listLeafFiles(PartitioningAwareFileIndex.scala:256)
        at org.apache.spark.sql.execution.datasources.InMemoryFileIndex.refresh0(InMemoryFileIndex.scala:74)
        at org.apache.spark.sql.execution.datasources.InMemoryFileIndex.<init>(InMemoryFileIndex.scala:50)
        at org.apache.spark.sql.execution.datasources.FileIndexSuite$$anonfun$9$$anonfun$apply$mcV$sp$2.apply$mcV$sp(FileIndexSuite.scala:186)
        at org.apache.spark.sql.test.SQLTestUtils$class.withSQLConf(SQLTestUtils.scala:105)
        at org.apache.spark.sql.execution.datasources.FileIndexSuite.withSQLConf(FileIndexSuite.scala:33)
        at org.apache.spark.sql.execution.datasources.FileIndexSuite$$anonfun$9.apply$mcV$sp(FileIndexSuite.scala:185)
        at org.apache.spark.sql.execution.datasources.FileIndexSuite$$anonfun$9.apply(FileIndexSuite.scala:185)
        at org.apache.spark.sql.execution.datasources.FileIndexSuite$$anonfun$9.apply(FileIndexSuite.scala:185)
        at org.scalatest.Transformer$$anonfun$apply$1.apply$mcV$sp(Transformer.scala:22)
        at org.scalatest.OutcomeOf$class.outcomeOf(OutcomeOf.scala:85)

How was this patch tested?
unit test added

cc @cloud-fan @gatorsmile

Test build #73552 has started for PR 17093 at commit 96898a2.

Test build #73552 has finished for PR 17093 at commit 96898a2.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/73552/
Test PASSed.

Test build #73568 has started for PR 17093 at commit a3ac29b.

Test build #73568 has finished for PR 17093 at commit a3ac29b.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/73568/
Test PASSed.

Test build #73583 has started for PR 17093 at commit ec0afac.

Test build #73583 has finished for PR 17093 at commit ec0afac.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/73583/
Test PASSed.

Test build #73633 has started for PR 17093 at commit 13b70f0.

Test build #73633 has finished for PR 17093 at commit 13b70f0.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/73633/
Test FAILed.

Merged build finished. Test FAILed.

Test build #73650 has started for PR 17093 at commit 0d2334d.

Test build #73650 has finished for PR 17093 at commit 0d2334d.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/73650/
Test FAILed.

Test build #73665 has started for PR 17093 at commit 74d08a5.

LGTM except https://github.com/apache/spark/pull/17093#discussion_r103616280

Test build #73665 has finished for PR 17093 at commit 74d08a5.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/73665/
Test PASSed.

Test build #73672 has started for PR 17093 at commit e1a9072.

Test build #73673 has started for PR 17093 at commit 3c079ff.

Test build #73672 has finished for PR 17093 at commit e1a9072.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/73672/
Test PASSed.

Test build #73673 has finished for PR 17093 at commit 3c079ff.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/73673/
Test PASSed.

Merged build finished. Test PASSed.

Thanks! Merging to master.

Thanks! Merging to master.


support discovery of abnormal states during resource synchronization

1, retrive resourceNegotiator.restmapper in setSyncResources
2, don't delete the version in groupResourceStatus when it is in cluster syncResources
3, add watchErrorHandler ErrorHandlerForResourceSynchro to customize reflector
4, add SyncStatusError status to ClusterResourceSyncCondition
#6

when the status is not changed, genClusterStatus will update resource SyncCondition LastTransitionTime in order not to update frequently.
Unknown resources cannot distinguish between custom resources and new resources for the dependency version. A new PR will be created for detailed description.
@Iceber PTAL, Thanks.

when the status is not changed, genClusterStatus will update resource SyncCondition LastTransitionTime in order not to update frequently.

Based on discussions with @Iceber , it is not recommended to do save operation groupResourceStatus.Store outside of setSyncResources, the resource SyncCondition status should dynamic compute from synchro.

In setSyncResources, will keep the resource in storageResourceSynchros even though it is not in storageResourceSyncConfigs. The resource Informer will keep running.

When user delete the custom resource in Kubernetes, we just remove the resource status from cluster, it does not need to do any process.  We are more concerned with scenarios without permissions in issue #6

In Reflector.Run, will always call watchErrorHandler, when starting and an error occurs.

It is not optimal and a better approach will be considered later.

This pr has been resolved https://github.com/clusterpedia-io/clusterpedia/issues/6, but we still need to optimize the WatchErrorHandler in the reflector.
You can also copy the original reflector.go to informer/.reflector.go for others to compare the changes.

@ycsk02 Thank you very much for contributing!


Configure dropdown border-radius, border, offset

The redesigned EMR dashboard requires the following properties of the dropdown component to be configurable: border-radius, border, offset.
Related CMS PR: https://github.com/sappira-inc/cms/pull/225

Codecov Report

Merging #17 into master will not change coverage.
The diff coverage is 0%.

@@           Coverage Diff           @@
##           master      #17   +/-   ##
=======================================
  Coverage   74.21%   74.21%
=======================================
  Files          13       13
  Lines         159      159
  Branches       24       25    +1
=======================================
  Hits          118      118
+ Misses         30       29    -1
- Partials       11       12    +1

Impacted Files
Coverage Δ

src/Dropdown/Dropdown.js
41.86% <0%> (ø)
:arrow_up:

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 e1614e4...0a791ed. Read the comment docs.

Can we just configure the dropdown styles in cms theme.js?

Thanks @kylealwyn, that's a better approach -- we can specify the styles in theme instead. An offset will still need to be passed down in order to specify how Popper.js will handle/calculate placement.


[json] schema validation in a folder of a workspace stops working when more folders are added to it

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.66.2 (Tested in Insiders 1.67.0 with same results)
OS Version: Windows 10 Education N x64 - 21H1

Steps to Reproduce:

Create a Workspace and add a simple folder with a schema for JSON files defined in the folder settings.

schema-file.json
{
    "$schema": "http://json-schema.org/draft-07/schema#",
    "title": "Test",
    "description": "An example schema",
    "type": "object",
    "properties": {
        "requiredProperty": {
            "type": "string"
        }
    },
    "required": [
        "requiredProperty"
    ]
}

Check that the test.json file is being validated correctly.

Add a second folder to the workspace. In my test I added an empty folder in the same root as the workspace. The validation still works as expected.

Reload the window or close/open VSCode. The schema validation has stopped working as if the file did not match the fileMatch in the folder settings. Removing the second folder and reloading makes it work again.

As a note, if you open folder-A directly in VSCode rather than the workspace, the validation works as expected.

The new validated by schema information is great. But this reported issue in work spaces prevents me from upgrading from 1.65. Any chance this will be addressed anytime soon?

The new validated by schema information is great. But this reported issue in work spaces prevents me from upgrading from 1.65. Any chance this will be addressed anytime soon?

Is it working correctly pre-1.65? Because this issue is very annoying here (we have to open multiple instances of vscode as workaround which is problematic for various reasons), and we could very much just ship a portable version of previous version of vscode

The new validated by schema information is great. But this reported issue in work spaces prevents me from upgrading from 1.65. Any chance this will be addressed anytime soon?

@ajcool2k
Is it working correctly pre-1.65? Because this issue is very annoying here (we have to open multiple instances of vscode as workaround which is problematic for various reasons), and we could very much just ship a portable version of previous version of vscode

Yes it worked before. So you should be good with an old release for the time being. Not a solution but at least workspaces are usable.

@ajcool2k
Looks fixed in vscode-insiders 1.71

@ajcool2k Looks fixed in vscode-insiders 1.71

Still have the bug on 1.71 on my machine.
Top: Workspace, Bottom: Folder

@ajcool2k Looks fixed in vscode-insiders 1.71

Still have the bug on 1.71 on my machine.
Top: Workspace, Bottom: Folder

Same. Still not solved for me with 1.71.

Still have the bug on 1.71.2

I'm on 1.73 and this is still an issue. Works ok when you open a folder and the json.schemas is at the root of it inside .vscode folder. It doesn't work in a multi-root workspace. We have a lot of JSON files and autocomplete doesn't work anymore. This used to work before.
Surprised as to why this is not getting any traction. Seems like a huge regression in functionality.

I noticed this is OS-specific too. On ubuntu 22 machine multi-root validation works fine but not on windows 10 machine it doesn't, on the same codebase.

Yeah, this is probably the reason I tricked myself it was working back then.
@aeschli , any status update on this? I am pinging, because there has been no update on the matter since its original report in April, and the issue is 100% reproducible on any vscode version since 1.65

I noticed this is OS-specific too. On ubuntu 22 machine multi-root validation works fine but not on windows 10 machine it doesn't, on the same codebase.

Can confirm this observation, the issue only occurs in windows and not on Ubuntu, have not tested macOS

Can confirm this observation, the issue only occurs in windows and not on Ubuntu, have not tested macOS

Same here using Remote-SSH to an Ubuntu workspace.

Same here using Remote-SSH to a Redhat workspace. However, it works right setting the "$schema": "url-schema" attribute in the .json file.


OpenAPI 3.1 support for deck file commands

The deck file openapi2kong currently uses kin-openapi for all it's OpenAPI requirements. This library does not support OpenAPI 3.1, which is a requirement from users.
This issue is to replace kin-openapi with https://github.com/pb33f/libopenapi, ensuring that there are no changes in the tests. This should be a transparent update for our users.

@mheap Could you clarify what all features from OpenAPI 3.1 initiative have we decided to adopt/support?

To elaborate, I wanted to properly understand what is the entire scope of this task.
After the library update, what features from 3.1 are we keeping in the scope?

@Prashansa-K Existing functionality should continue to work when present with an OpenAPI 3.1 format file, rather than returning an error.
Any OAS 3.1 specific functionality can be handled in a separate issue (we don't have any specific requests yet other than general 3.1 support)


Rewrite elasticsearch multi example to use child charts.

As a newbie to helm, I found child charts interesting. This change makes the multi example now use a single release with child charts instead of two separate helm releases.
In practice, I don't know if this is the best route, because we'll want to upgrade masters before upgrading data nodes, for example, so this PR is mostly food-for-thought.
Thoughts? :)

we'll want to upgrade masters before upgrading data nodes

I suppose in this example, we could set imageTag separately for each child chart in the values.yaml and do an upgrade that way:

set imageTag on master to new version
make install to upgrade just the masters
set imageTag on data role to new version
make install to ugprade just the data nodes

It'd be identical to the the upgrade process for current code (in master) which has two files (data + master) and separate helm releases, probably?

If you also wanted to add Kibana to this setup

Indeed! I'll share my stack chart with you after new years which includes Kibana.

Rebased!

CI tests are failing because helm isn't initialised.
22:54:45 make[1]: Entering directory `/app/elasticsearch/examples/multi'
22:54:45 helm dep update
22:54:45 Error: Couldn't load repositories file (/app/.helm/repository/repositories.yaml).
22:54:45 You might need to run `helm init` (or `helm init --client-only` if tiller is already installed)

I think adding the helm init --client-only into the testing Dockerfile would be the cleanest way to fix it. That is defined in helpers/terraform/Dockerfile

@rendhalver I have some other ideas to make this chart style even more useful (so that settings can be inherited across parent->child chart values). Hopefully will have a PR to demo it this week. After that, we can discuss any future support for this style.
And thank you for testing! :)

That sounds pretty cool!
Tag me on your new PR. :)

@Crazybus I think this is ready for another round of reviews. CI tests failure seems unrelated (timeout waiting for the GKE cluster to come online)

Any update? Do you need help on this one?

Any update? Do you need help on this one? I can help bringing a multi example with several node groups (hot/warm/cold)

Pleas do! (In a separate PR).

I think having it as a separate example is a better idea.

I agree with @rendhalver and think that we should add this is a example to the existing multi one that is being used for testing.


Menu: Menu underlines accelerator keys when opened with mouse but they don't work

#52854

Open Help menu
Notice the W in Welcome is underlines
Press W

Nothing happens.

dupe of #52368


sbt-dependency-graph 0.10.0-RC1

@raboof cool these proposed edits, never seen that before

do you plan to release this so we can fix https://github.com/akka/alpakka/issues/2145 ?

Yes, I'll try to make it happen.


Store propagated version status in template resources

This issue supercedes #108.
Propagated version status is used to determine whether target resources need to be updated without having to consider the content of the target resource.  The content of target resources may vary between member clusters due to new field additions for which default values are supplied.
Currently propagated version status for a federated resource is tracked in resources separate from the template (PropagatedVersion and ClusterPropagatedVersion) due to the use of the resourceVersion field as the version of a given template.   The resourceVersion field changes with any change to a resource, including the status, and any change to the status would force an update to target resources even if the content used to determine target resource state had not changed.
It would be preferable to store propagated version status in template resources, and this suggests switching from the resourceVersion field to content-based hashing (e.g. hashing the json of the template's spec field).
Tasks:

[x] implement content-based hashing for template versioning (#527)
[ ] store propagated version status on the template

Given recent conversations about scalability concerns, I'm less sure that it makes sense to store propagated version in federated resources rather than separately.  Keeping them separate ensures that the version accounting doesn't have to compete for etcd object space with the definition of a federated resource for large numbers of clusters.


Add --verbose during pod update when releasing

https://github.com/Moya/Moya/issues/888#issuecomment-270403554

Current coverage is 73.72% (diff: 100%)

Merging #903 into master will not change coverage

@@             master       #903   diff @@
==========================================
  Files            22         22
  Lines           723        723
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits            533        533
  Misses          190        190
  Partials          0          0

Powered by Codecov. Last update 917997f...f4263be


SimpleCache IllegalStateException when bundle reloading via CodePush

Describe the Bug
When a bundle is reloaded on Android devices via react-native-code-push (A very popular react-native library created by Microsoft and used by many organisations), TrackPlayer fails to reset the SimpleCache lock.
This occurs because while the app is technically restarted, the underlying native code is not. Since the .destroy() functionality is no longer exposed to the application via the native module, we can no longer workaround this problem by manually clearing up resources on Code-Push.
Any attempt to reload Android via Code-Push after calling setupPlayer results in the following error:
FATAL EXCEPTION: main
Process: <PACKAGE_NAME>, PID: 32249
java.lang.IllegalStateException: Another SimpleCache instance uses the folder: /data/user/0/<PACKAGE_NAME>/cache/TrackPlayer
    at com.google.android.exoplayer2.upstream.cache.SimpleCache.<init>(SimpleCache.java:249)
    at com.google.android.exoplayer2.upstream.cache.SimpleCache.<init>(SimpleCache.java:229)
    at com.google.android.exoplayer2.upstream.cache.SimpleCache.<init>(SimpleCache.java:194)
    at com.doublesymmetry.kotlinaudio.players.BaseAudioPlayer.<init>(BaseAudioPlayer.kt:153)
    at com.doublesymmetry.kotlinaudio.players.QueuedAudioPlayer.<init>(QueuedAudioPlayer.kt:14)
    at com.doublesymmetry.trackplayer.service.MusicService.setupPlayer(MusicService.kt:92)
    at com.doublesymmetry.trackplayer.module.MusicModule$onServiceConnected$1.invokeSuspend(MusicModule.kt:56)
    at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
    at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106)
    at android.os.Handler.handleCallback(Handler.java:789)
    at android.os.Handler.dispatchMessage(Handler.java:98)
    at android.os.Looper.loop(Looper.java:164)
    at android.app.ActivityThread.main(ActivityThread.java:6944)

Steps To Reproduce

Spin up the React Native Track Player Example App
Implement react-native-code-push
Attempt to install an update via Code-Push after setupPlayer has been called (Even with the appropriate try {} catch {} in place around await TrackPlayer.getCurrentTrack();)
Wait for CodePush to finish installing the new bundle
App crashes
Upon restarting the app, it all works fine again with the new bundle, as the native code has released the cache

Code To Reproduce

Spin up React Native Track Player Example App
Perform Code Push Android Installation (Steps 1 to 4)

Environment Info:
System:
    OS: macOS 12.6
    CPU: (10) arm64 Apple M1 Max
    Memory: 535.66 MB / 32.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 16.17.0 - ~/.nvm/versions/node/v16.17.0/bin/node
    Yarn: 1.22.19 - ~/.nvm/versions/node/v16.17.0/bin/yarn
    npm: 8.15.0 - ~/.nvm/versions/node/v16.17.0/bin/npm
    Watchman: 2<IP_ADDRESS> - /opt/homebrew/bin/watchman
  Managers:
    CocoaPods: 1.11.3 - /opt/homebrew/lib/ruby/gems/3.1.0/bin/pod
  SDKs:
    iOS SDK:
      Platforms: DriverKit 21.4, iOS 16.0, macOS 12.3, tvOS 16.0, watchOS 9.0
    Android SDK:
      API Levels: 28, 30, 31, 33
      Build Tools: 29.0.2, 30.0.3, 31.0.0, 33.0.0
      System Images: android-31 | Google Play ARM 64 v8a, android-33 | Google APIs ARM 64 v8a
      Android NDK: Not Found
  IDEs:
    Android Studio: Electric Eel 2022.1.1 Beta 1 Electric Eel 2022.1.1 Beta 1
    Xcode: 14.0.1/14A400 - /usr/bin/xcodebuild
  Languages:
    Java: 11.0.13 - /usr/bin/javac
  npmPackages:
    @react-native-community/cli: Not Found
    react: 18.1.0 => 18.1.0
    react-native: 0.70.1 => 0.70.1
    react-native-macos: Not Found
  npmGlobalPackages:
    *react-native*: Not Found

Using<EMAIL_ADDRESS>Using<EMAIL_ADDRESS>Running on a real Samsung Galaxy s7 (API 26)
Device: Android 8.0 / Samsung Experience 9.0

How I can help
Since the .destroy() mechanism was removed in a previous release, I don't want to raise a PR here that might directly conflict with the intentions of the library; that being said, we do need some way to resolve this caching issue and exposing this mechanism directly to the consuming developers seems like the least troublesome solution to this issue.
Relates to
While the issues listed below are related, they do not correlate 1:1 with this issue:

https://github.com/doublesymmetry/react-native-track-player/issues/1745
https://github.com/doublesymmetry/react-native-track-player/issues/1718
https://github.com/doublesymmetry/react-native-track-player/issues/296

Im facing the same problem, and from what I can tell, your CodePush problem correlates with the hot reload problem. It seems like it was fixed in this pr, but seeing that this comment has not received any updates yet, I guess we just got to wait 🤷♂ Maybe this issue will make some more traction to get an ETA on the next release?

Closing as a duplicate
https://github.com/doublesymmetry/react-native-track-player/issues/296#issuecomment-1259598282

@jspizziri I mentioned in the issue, that we ARE using the most recent version of KotlinAudio (At the time of writing, it's v1.2.4) and this issue has still not been resolved -- Makes sense if the fix hasn't been released yet (Merged circa 17 days ago).
If this resolution is still to come in a future release of KotlinAudio and RNTP could you specify what version of RNTP you expect to contain this targeted fix so I can track when to perform the upgrade on my side?
As of right now, this is still a breaking change for many applications, and until the release is done, I believe the Issue should remain open for tracking purposes, unless you have a different definition of "Done".
Some information on an ETA would be very useful to those of us who have to report to Business Analysts why we've got regression in our application that requires hacky workarounds on Android that ultimately degrades UX.

@rossyman this fix will go out in the next patch release. If you need a workaround before then please look at the above comments.
We track work via our GitHub project board. This issue will remain closed based on our process. Thanks.


Macro Keyboard Not Working

I made a macro keyboard (Pi Pico + CircuitPython) with a single button outputting "CTRL+ENTER" to spin the wheel, however inside the wheel spinner app it will not accept this input. I have confirmed the macro is outputting correctly via showkey, and it works on other pages in chromium. In the wheel spinner app, it does not take any input at all, even on the list entry for the wheel. Any clue why this might be happening? I would really like to set up a single button to initiate the wheel spin.
Thanks,
James

Sorry, managed to get this working myself by changing the event listener from keyup to keydown in spinningwheel.vue


Habana to main

Closes: #1450
Description

Merging Habana Feature into main.
How Has This Been Tested?

How I am testing Habana

Ability to create accelerator profile and see it in all locations in the UI: workbench, jupyter spawner, model serving, and in both add and edit mode
Model server details shows correct accelerator name and number of accelerators
Resources and tolerations are successfully added and removed for new and edited workbenches and serving runtimes
Existing settings keeps accelerator settings for both runtimes and workbenches
Auto detect Nvidia gpu works when tolerations and resource identifier match
Setting accelerator to none removes the identifier from the resources and tolerations are removed as well

In the case of existing settings -> tolerations are not removed because we don’t know which ones to remove

Workbench and serving runtimes will show that images/runtimes/accelerators are recommended if the identifier and annotation match
Error and warning cases are correct based on recommended annotation
Can update the count without changing the accelerator

NOTE
Migration and accelerator detection cannot be tested without a gpu cluster
Test Impact

Tests will be coming after the feature is merged
Request review criteria:

Self checklist (all need to be checked):

[x] The developer has manually tested the changes and verified that the changes work
[x] Commits have been squashed into descriptive, self-contained units of work (e.g. 'WIP' and 'Implements feedback' style messages have been removed)
[x] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[x] The developer has added tests or explained why testing cannot be added (unit tests & storybook for related changes)

If you have UI changes:

[ ] Included any necessary screenshots or gifs if it was a UI change.
[ ] Included tags to the UX team if it was a UI/UX change (find relevant UX in the SMEs section).

After the PR is posted & before it merges:

[ ] The developer has tested their solution on a cluster by using the image produced by the PR to main

@andrewballantyne added testing instructions

/lgtm

/approve
Going ahead with the merge. We'll have another week before code freeze / release. We can adjust small efforts along the way. QE has been verifying the feature for the past couple weeks.


Ingest recently released missing 30m SRTM data

Looks like the remaining SRTM 30m data has been released. Let's get it and ingest, perhaps filling any remaining small gaps with Aster as before.

This data has been ingested to s3://mrgeo/images/srtm-v3-30m however it still needs some massaging because the min value after ingest is -11600 meters and the max value is 22830 meters. Tim took a look at the areas with data above the real min/max elevations on the earth, and it's concentrated to a specific area and just looks wrong. In that area, the old v2 SRTM layer had nodata there.
So we propose running a "con" statement to set any pixels to nodata if their value below the true min elevation or above the true max elevation.


buildFHSUserEnv: Allow having custom /opt in the FHS environment

Motivation for this change
buildFHSUserEnv is meant primarily for running 3rd-party software
which is difficult to patch for NixOS. Such software is often built to
run from /opt. Currently, running such a software from FHS environment
is difficult for two reasons:

If the host system has the /opt directory, it gets bind-mounted to
the FHSEnv. If that directory is not accessible for non-root
users (which is what docker's containerd does with /opt :-(), the
user running the FHSEnv cannot use it.
With the change in chrootenv.c, /opt is not bind-mounted to the
container, but instead created as user-modifiable symlink to
/host/opt (see the init attribute in
build-fhs-userenv/default.nix). If needed, the user can remove this
symlink and create an empty /opt directory which is under his/her
control.

If the 3rd-party software is put into the Nix store via a simple
derivation (with e.g. installPhase = "dpkg-deb -x $src $out"), the
content of /opt directory of that derivation does not appear in the
FHSEnv even if the derivation is specified in targetPkgs. This is
why we change env.nix.

Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Relase 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

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 128126 at e5299631 run on x86_64-linux 1

1 package marked as broken and skipped:

ovftool

1 package failed to build:

quartus-prime-lite

2 packages skipped due to time constraints:

houdini
plex

28 packages built successfully:

appimage-run
arduino-ci
arduino-cli
bitscope.chart
bitscope.console
bitscope.display
bitscope.dso
bitscope.logic
bitscope.meter
bitscope.proto
bitscope.server
clonehero
conda
dropbox
dropbox-cli
esphome
fahclient
flutter (flutterPackages.stable)
hover
left4gore-bin
lightworks
mate.caja-dropbox
platformio
shticker-book-unwritten
sidequest
unvanquished
vmware-horizon-client
zulip

Note that build failures may predate this PR, and could be nondeterministic or hardware dependent.
Please exercise your independent judgement. Does something look off? Please file an issue or reach out on IRC.

Most new packages should be using the bubblewrap version, which I believe buildFHSUserEnv now points to. This is the buildFHSUserChroot helper.

buildFHSUserEnv still points to buildFHSUserChroot. Nevertheless, I updated buildFHSUserEnvBubblewrap in the same way and updated the commit message accordingly.

@SuperSandro2000 Is there anything more needed to get this merged?

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

3 packages marked as broken and skipped:

minetime
ovftool
timedoctor

1 package blacklisted:

appimage-run-tests

2 packages failed to build:

houdini
quartus-prime-lite

88 packages built:

Sylk
altair
android-studio (androidStudioPackages.stable)
androidStudioPackages.beta
androidStudioPackages.canary
androidStudioPackages.dev
anki-bin
appimage-run
apple-music-electron
arduino-ci
arduino-cli
betterdiscord-installer
bitscope.chart
bitscope.console
bitscope.display
bitscope.dso
bitscope.logic
bitscope.meter
bitscope.proto
bitscope.server
bottles
chrysalis
clonehero
conda
crypto-org-wallet
deltachat-electron
devdocs-desktop
dropbox
dropbox-cli
electron-mail
electronplayer
esphome
fahclient
flexoptix-app
flutter (flutterPackages.stable)
hover
irccloud
joplin-desktop
keeweb
kodiPackages.steam-launcher
lbry
ledger-live-desktop
left4gore-bin
lens
lightworks
losslesscut-bin
lunar-client
lutris
lutris-free
marktext
mate.caja-dropbox
mathpix-snipping-tool
molotov
mycrypto
neo4j-desktop
notable
nuclear
octant-desktop
p3x-onenote
platformio
playonlinux
plex
plexamp
protontricks
radicle-upstream
rambox-pro
shticker-book-unwritten
sidequest
ssb-patchwork
standardnotes
station
steam
steam-run
steam-run-native
steam-tui
steamcmd
timeular
trezor-suite
tusk
unityhub
unvanquished
vmware-horizon-client
vscode-fhs
vscodium-fhs
wootility
ytmdesktop
zettlr
zulip


zeek: 5.2.0 -> 6.0.1

Description of changes
https://github.com/zeek/zeek/blob/v6.0.1/NEWS
Does not work with system spicy, so it must use the bundled one now.
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] 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/)
23.11 Release Notes (or backporting 23.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

[x] Fits CONTRIBUTING.md.

Resolves #258954.

Result of nixpkgs-review pr 261203 run on aarch64-darwin 1

3 packages built:

python310Packages.zeek (python310Packages.zeek.py)
python311Packages.zeek (python311Packages.zeek.py)
zeek

@tobim After this merge zkg and zeekctl also becomes available through the PATH, but the zkg and zeekctl are missing their dependencies. I would very much like to see these packages worked and also maybe if zkg works the corresponding standalone package should be dropped. I suspect that the standalone-zkg nixpkg would conflict with this now.
So far I've got zeekctl to work by just adding python3 to the buildInputs, but I still have some issues with zkg.
zkg error message:
error: zkg failed to import one or more dependencies:

* GitPython:        https://pypi.org/project/GitPython
* semantic-version: https://pypi.org/project/semantic-version

If you use 'pip', they can be installed like:

     pip3 install GitPython semantic-version

Also check the following exception output for possible alternate explanations:

ModuleNotFoundError: No module named 'git'

I agree that a dedicated zkg package doesn't make much sense, but I'm not sure of its value when Zeek itself is managed via Nix. Fixes are welcome though.

Would you mind trying the following?
--- a/pkgs/applications/networking/ids/zeek/default.nix
+++ b/pkgs/applications/networking/ids/zeek/default.nix
@@ -22,6 +22,7 @@

 let
   broker = callPackage ./broker { };
+  python = python3.withPackages (p: [ p.gitpython p.semantic-version ]);
 in
 stdenv.mkDerivation rec {
   pname = "zeek";
@@ -43,7 +44,6 @@ stdenv.mkDerivation rec {
     cmake
     file
     flex
-    python3
   ];

   buildInputs = [
@@ -54,13 +54,13 @@ stdenv.mkDerivation rec {
     libpcap
     ncurses
     openssl
+    python
     swig
     zlib
   ] ++ lib.optionals stdenv.isLinux [
     libkqueue
   ] ++ lib.optionals stdenv.isDarwin [
     gettext
-    python3
   ];

That indeed did the trick!


ESP32-C3 returns wakeup cause that is for light sleep when leaving deep sleep? (IDFGH-8064)

Environment

Development Kit:      esp32-c3-devkitm-1
Module or chip used:  ESP32-C3
IDF version (run git describe --tags to find it): 4.4.1
Compiler version (run xtensa-esp32-elf-gcc --version to find it): 8.4.0+2021r2-patch3

Problem Description
ESP32-C3 wakes up from deep sleep by using a GPIO. esp_sleep_get_wakeup_cause returns 7 which stands for ESP_SLEEP_WAKEUP_GPIO which is documented as "light sleep only".
Is this a documentation issue or is this the wrong wakeup cause?

Hi,
You are right, the docs are wrong here. C3/C2 do support ESP_SLEEP_WAKEUP_GPIO from deep sleep (see SOC_GPIO_SUPPORT_DEEPSLEEP_WAKEUP)
I'll update the docs to reflect this.


Support Advanced Queueing

https://odpi-c.readthedocs.io/en/latest/functions/dpiQueue.html

I tried implementing it, but after firing below query:
BEGIN
   DBMS_AQADM.CREATE_QUEUE_TABLE(
      queue_table        => 'my_queue_table',
      queue_payload_type => 'SYS.AQ$_JMS_TEXT_MESSAGE'
   );
END;

It throws below error:
SQL Error [6550] [65000]: ORA-06550: line 2, column 4:
PLS-00201: identifier 'DBMS_AQADM' must be declared
ORA-06550: line 2, column 4:
PL/SQL: Statement ignored

Seems like DBMS_AQADM package is not part of gvenzl/oracle-free:23 does not contain Advanced queuing package.
SELECT object_name, object_type
FROM all_objects
WHERE object_name IN ('DBMS_AQ', 'DBMS_AQADM')
  AND object_type = 'PACKAGE';

Above query's output is empty


[kie-issues#1610] Remove WorkItemDefinition mechanism

Closes https://github.com/apache/incubator-kie-issues/issues/1610
Remove WorkItemDefinition mechanism from the Workflow engine (.wid) files support on the BPMN Editor / engine.

@josedee  Thank you for applying the changes!
@josedee @elguardian @pefernan @martinweiler  I noticed we have a lot of wid files in the repo (eg apache/incubator-kie-kogito-runtimes/jbpm/jbpm-flow-builder/src/test/resources/org/jbpm/process/workitem/repositorysingledir/repowid.wid), should we remove them all?

follow up issue: we need a mechanism in place to replace WID files https://github.com/apache/incubator-kie-issues/issues/1676


remove dead links

Removes dead links as specified in https://github.com/Leaflet/Leaflet/issues/9291.

Removes dead links as specified in:
https://github.com/Leaflet/Leaflet/issues/8373.

@Hubda987 this looks good, did you close the PR accidentally?

@Hubda987 this looks good, did you close the PR accidentally?

Yeah, I didn't mean to close it permanently. I submitted a new PR for it


Update how-to-select-update-package.md

Update the Azure Percept devkit release table to include May service release.

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

#sign off

#sign-off

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

@mimcco I edited the update for grammar and Microsoft style. Before we merge the PR, would you check my edit to make sure that I captured the meaning?

I'm going to go ahead and merge this. If edits are needed, let me know and I'll apply them in a new PR. Thanks.


Add a periodic task for psutil stats

Look into using this at some point: https://github.com/giampaolo/psutil.

Implemented here: https://github.com/vkottler/conntextual/commit/6b2472b49aa057f1534439d96f150255bc393972.


Does anyone have experience getting viewport radius?

I been struggling for few weeks now.

I've done this with point-geometry and turf libraries. Get your viewport width / 2 (x) and viewport height / 2 (y) for the center then...
const point = map.unproject(new Point(x, y));
const center = map.getCenter();
const distanceInMetres = turf.distance(
  [point.lng, point.lat],
  [center.lng, center.lat],
  'meters',
);

This should return the distance from edge of the screen to the center in meters.

@alex3165 @4xDMG I was able to calculate radius. But for the data i am working with, viewport based polyon is better option for me. How do i get lat:lng of 4 corners of the viewport screen?

I think you can use mapbox gl-js's map.getBounds() method to get SW and NE lngLat of the viewport.
To get the remaining two corners you can just take the lng from SW and the lat from NE for the SE point and the opposite for the NW point.

@4xDMG THAT WORKED GREAT. THANKS.
Now how do i get the center of Polygon ? haha sorry

@suyesh, You can use the turf.js  centerOfMass function to get the centerOfMass of a polygon.

I've done this with point-geometry and turf libraries. Get your viewport width (x) and viewport height / 2 (y) for the edge then...
const point = map.unproject(new Point(x, y));
const center = map.getCenter();
const distanceInMetres = turf.distance(
  [point.lng, point.lat],
  [center.lng, center.lat],
  'meters',
);

This should return the distance from edge of the screen to the center in meters.

In case anyone comes across this, the third parameter for the distance() method in the latest version of turf is an options object, so you'll want to replace miles with { units: 'miles' }.


merge and ad-hoc UDP source

I've run into an issue when merging an UDP source didn't quite work if the UDP source goes offline and then comes back. TSP needs to be restarted so that the playout continues correctly.
Here's my source:
ffmpeg.exe -re -i D:\SW\input1.mp4 -c:a copy -c:v copy -f mpegts -mpegts_service_id 3 -mpegts_pmt_start_pid 5002 -mpegts_start_pid 2001 -metadata service_name="CH-3" -muxrate 9000000.0 "udp://<IP_ADDRESS>:10000?pkt_size=1316&bitrate=9000000"
And this is my tsp command:
tsp -v --bitrate 30000000 -I null -P regulate -P merge "tsp -I ip 10000 -P pcrbitrate -P regulate" -O dektec --device 0 --modulation DVB-S --convolutional-rate 7/8 --lnb 5150 --satellite-frequency<PHONE_NUMBER> --level -390 --stuffing --bitrate 30000000
As output I've also done UDP to test with VLC.
Both run on the same machine (<IP_ADDRESS>).
When I stop the source and then run it again, the player isn't working properly - if streaming to VLC, only some frames from video are shown. If modulating and playing on a Dreambox satellite receiver, video works but there's no audio. After restarting tsp (while ffmpeg keeps running), it works, so something that's done at the merge start is missing when UDP source resumes.
If I use the ffmpeg UDP source directly as tsp input, not merging, it works - after stopping and starting ffmpeg again, the player works fine. This is why I think it's related to merging and looks like I need some additional parameters in my command but I'm not sure what that could be.

Hi Jan,
I bet a beer at next IBC that the problem would be solved by removing -P pcrbitrate -P regulate from the merged command (the one with -I ip) :beers:
Let me explain why.
The plugins pcrbitrate and regulate are not panaceas. They serve very specific purposes
A stream has a rendering speed (the speed of the audio / video) and a transmission speed (the speed at which packets go through tsp). The plugin pcrbitrate is designed to evaluate the rendering speed. The plugin regulate is designed to alter the transmission speed.
Real-time streams, from broadcast or multicast, have identical transmission and rendering speeds because they are transmitted to watch TV.
Files, on the other hand, have a very high transmission speed, maybe 1 Gb/s or more on SSD. Consider that you have recorded a 6 Mb/s single program transport stream. Then, using tsp -I file, you read it and send it to -O ip. The effective reading speed of the file will be 500 M/b for instance. So, on a gigabit network, you send a 6 Mb/s video stream at 1 Gb/s, 166 times faster as it should be. Thus, a 15 mn video is received in 5 seconds and the player displays almost nothing.
In this case, you must use the plugin regulate between -I file and -O ip. The plugin acts as a bottleneck and lets packets flow out at 6 Mb/s only.
But, when the source has the same transmission and rendering speeds, regulate is useless. At best, it does nothing. At worst, it introduces undesirable artifacts.
In your main command, -P regulate is necessary because -I null produces packets at an infinite speed (at CPU speed in fact). But, in the merged command, -I ip produces packets when they arrive, with identical transmission and rendering speeds, and -P regulate is useless.
So, why does it fail in your case? Because of the behaviour of -P pcrbitrate between -I ip and -P regulate when the transmission is interrupted and restarted.
How does regulate know the regulation speed? First, it can be specified in its command line options. Otherwise, it is transmitted from the previous plugin. As a general rule, tsp collects the input bitrate, either from the input plugin itself which extracts the bitrate from a hardware input device (this is the case for ASI cards for instance) or, if the input plugin is not able to report a bitrate, tsp automatically analyzes PCR's at the output of the input plugin and computes the corresponding bitrate (which implies, by the way, that specifying -P pcrbitrate immediately after the input plugin is redundant).
Then, the bitrate is transmitted from plugin to plugin. Some plugins may inadvertently propagate incorrect bitrates while some plugins may force a (correct) recomputation of the bitrate. To illustrate the first case, consider -I file ... -P zap ... using sample bitrate values. You reads a complete 36 Mb/s input and tsp evaluates this bitrate. Then, -P zap extracts a 4 Mb/s service and removes everthing else. But it does not recomputes the TS bitrate. So, the propagated bitrate information is still 36 Mb/s. If this information is not used downstream in others plugins, we don't care. But if we use the bitrate information in -P regulate -O ip ..., we will regulate at 36 Mb/s a stream which should be played at 4 Mb/s. This is why, in specific situations like this, we need to recompute the bitrate using -P pcrbitrate before -P regulate.
OK, I wrote this to re-explain the principles of bitrate propagation / computation in the tsp chain.
Now, back to your issue, -I ip reads packets and tsp computes the bitrate based on PCR's (let's ignore the next -P pcrbirate which is redundant). Then, -P regulate uses the evaluated bitrate to alter the transmission speed.
As long as your IP source produces packets (with identical rendering and transmission speeds), so far so good. But note that -P regulate is useless since it changes the transmission speed at the rendering speed, which are identical anyway.
When your IP source stops transmitting packets, the evaluated bitrate (or rendering speed) is ... zero. This information is propagated to -P regulate which sets the transmission speed to ... zero. And when the source restarts, packets are stopped by regulate (in fact they are regulated at speed zero). In practice, since new packets are received, PCR's are extracted and a non zero bitrate is evaluated and transmitted to regulate. But it increases slowly. Since packets are arriving faster, the buffer is full and packets are dropped. And the evaluated bitrate is incorrect. And so on...
As a conclusion, use the plugins pcrbitrate and regulate when necessary only.

thanks for great explanation of pcrbitrate and regulate plugins, which certainly helps to understand better when I really should use these... but despite removing the plugins, I don't really see any improvement... my command is now this:
tsp --bitrate 30000000 -I null -P regulate -P merge -p 0 -p 17 "tsp -v -I ip 10005" -O ip <IP_ADDRESS>:22000
but if I restart ffmpeg, VLC won't resume playback, not even after reopening the stream, it just shows 1st frame

OK, so I lost the beer...
I suggest to replace VLC with another instance of tsp -I ip.... In this instance, use plugin analyze to create multiple analysis file names every 20 or 30 seconds. Also save the output in a .ts file. Looking at the various analysis files, you can see what is received at various periods of time, before, during and after the interruption.

nah, you still deserve the beer, that's the least I could do :)
anyway I did try analyze but don't really see much in there... I'm adding 3 logs, one from fresh start, another with merge source offline and another after resuming ffmpeg source
analyze_out_20180608_192306_Running.txt
analyze_out_20180608_192346_Stopped.txt
analyze_out_20180608_192426_Restarted.txt
I think the next test for me will be trying merging the UDP stream into something else than null packets, which is what you were doing in your example, I'll just use UDP instead of files

No change even when merging into a file input instead of null. But it looks like this might be a network issue. There are some warning messages related to network traffic - screenshot attached. These warnings appear at the moment when the UDP (ffmpeg) source is restarted.

Do not worry about the warning. It says that two distinct sources were detected sending packets to the same destination (the one we are listening to). This is a warning because if two distinct sources are sending packets simultaneously, we get a mixture of the two, resulting in garbage. But here, you stopped the first source and restarted it later (using another client port, being identified as a second source). So, no problem in your case.
I looked at the 3 files. They looked perfectly OK. After restart, you receive the same service, using the same PID's, etc.
You mentioned that it worked when using the IP stream as direct source for tsp, but not when it is merged. The only difference I see is the vast amount of stuffing which is dropped into VLC. During the time where the source is stopped, VLC receives 30 Mb/s of pure stuffing without anything to play. Does this disturb VLC? It shouldn't.
Anyway, just to retry without this difference between the working and non-working cases, you may add -P filter -n -p 0x1FFF just before the final -O ip. Thus, VLC receives no stuffing, just like the working case.
Let us know the result.

I tried streaming without stuffing but don't see any difference.
tsp -v --bitrate 30000000 -I null -P regulate -P merge -p 0 -p 17 "tsp -v -I ip 10005" -P filter -n -p 0x1FFF -O ip <IP_ADDRESS>:22000
I've also tried streaming stuffing only (30 Mbps) by simply running tsp before running ffmpeg, which worked fine (VLC showing 30 Mbps incoming bitrate but no stream yet), and then I started the ffmpeg - this works, the stream is merged and VLC plays it just fine. The issue only comes when the merged UDP stream stops and starts again. If I use the same stream as input, the player is able to continue after ffmpeg restarts.

I've done a test with another UDP source, other than ffmpeg, and it works. So the problem is not caused by TSDuck, therefore this ticket can probably be closed. However, I'd like to find out how to configure ffmpeg output to work with the merge plugin. The only difference I see with ffmpeg and D9854 UDP output stream is that with D9854, I don't get the IP warning messages when rebooting the receiver.

The IP warning indicates that distinct pairs of source address:port are detected for the same destination. When you run ffmpeg (or any other similar application program) on a desktop/server O/S, it uses a new port number each time. On the contrary, I would not be surprised if an embedded equipment such as an IRD Pro explicitly reuses the same port number for the same purpose.
I let you close this issue when you consider it can be.

VLC's UDP output stream also works if it's restarted, so it looks like it's ffmpeg related. I'll test some other UDP sources later.

...and not working with astra-sm output, same symptoms like ffmpeg


Warn about using deprecated jsnext:main package.json fields

Ref #78
We may keep this deprecation for a while and then start to deprecate jsnext option.

Is the idea to get everyone to use module rather? I'm just wondering if we should try and wait until it is clear what Node will be doing here to avoid churn?

module is widely used right now. I just would like to prevent using even older stuff which everyone should omit.

I just think deprecations should always have clear and stable upgrade paths. And until the NodeJS modules story is set this is not a stable upgrade path. So I would rather leave something working and stale than constantly asking people to change something and build resentment over time.

I believe this is now obsolete after introduction of the mainfields option (that basically deprecated jsnext as well).


Recofix

Add missing stanzas for KinKal track fits

Hi @brownd1978,
You have proposed changes to files in these packages:

JobConfig

which require these tests: build.
@Mu2e/write, @Mu2e/fnalbuild-users have access to CI actions on main.
:hourglass: The following tests have been triggered for 308e21b4ff96802057732c7d6db908dad3db5963: build  (Build queue is empty)
About FNALbuild. Code review on Mu2e/Offline.

:umbrella: The build tests failed for 308e21b4ff96802057732c7d6db908dad3db5963.

Test
Result
Details

test with
:white_check_mark:
Command did not list any other PRs to include

merge
:white_check_mark:
Merged 308e21b4ff96802057732c7d6db908dad3db5963 at d7836d67c9e6cf4be37d8ec640a995d2b4e2d070

build (prof)
:white_check_mark:
Log file. Build time: 12 min 29 sec

ceSimReco
:x:
Log file. Return Code 90.

g4test_03MT
:white_check_mark:
Log file.

transportOnly
:white_check_mark:
Log file.

POT
:white_check_mark:
Log file.

g4study
:white_check_mark:
Log file.

cosmicSimReco
:x:
Log file. Return Code 90.

cosmicOffSpill
:white_check_mark:
Log file.

ceSteps
:white_check_mark:
Log file.

ceDigi
:white_check_mark:
Log file.

muDauSteps
:white_check_mark:
Log file.

ceMix
:white_check_mark:
Log file.

rootOverlaps
:white_check_mark:
Log file.

g4surfaceCheck
:white_check_mark:
Log file.

FIXME, TODO
:white_check_mark:
TODO (0) FIXME (0) in 0 files

clang-tidy
:white_check_mark:
0 errors 0 warnings

N.B. These results were obtained from a build of this Pull Request at 308e21b4ff96802057732c7d6db908dad3db5963 after being merged into the base branch at d7836d67c9e6cf4be37d8ec640a995d2b4e2d070.
For more information, please check the job page here.
Build artifacts are deleted after 5 days. If this is not desired, select Keep this build forever on the job page.

:hourglass: The following tests have been triggered for 308e21b4ff96802057732c7d6db908dad3db5963: build  (Build queue has 1 jobs)

:sunny: The build tests passed at 308e21b4ff96802057732c7d6db908dad3db5963.

Test
Result
Details

test with
:white_check_mark:
Included Mu2e/Offline#850 @ 60c37c06ec8bd0c5ab7839ef6cb6299aba10dc8a by merge

merge
:white_check_mark:
Merged 308e21b4ff96802057732c7d6db908dad3db5963 at d7836d67c9e6cf4be37d8ec640a995d2b4e2d070

build (prof)
:white_check_mark:
Log file. Build time: 22 min 35 sec

ceSimReco
:white_check_mark:
Log file.

g4test_03MT
:white_check_mark:
Log file.

transportOnly
:white_check_mark:
Log file.

POT
:white_check_mark:
Log file.

g4study
:white_check_mark:
Log file.

cosmicSimReco
:white_check_mark:
Log file.

cosmicOffSpill
:white_check_mark:
Log file.

ceSteps
:white_check_mark:
Log file.

ceDigi
:white_check_mark:
Log file.

muDauSteps
:white_check_mark:
Log file.

ceMix
:white_check_mark:
Log file.

rootOverlaps
:white_check_mark:
Log file.

g4surfaceCheck
:white_check_mark:
Log file.

FIXME, TODO
:white_check_mark:
TODO (0) FIXME (0) in 0 files

clang-tidy
:white_check_mark:
0 errors 0 warnings

N.B. These results were obtained from a build of this Pull Request at 308e21b4ff96802057732c7d6db908dad3db5963 after being merged into the base branch at d7836d67c9e6cf4be37d8ec640a995d2b4e2d070.
For more information, please check the job page here.
Build artifacts are deleted after 5 days. If this is not desired, select Keep this build forever on the job page.

Hi Rob,
The equivalent of BTrk final fit is the Kinal drift fit.
cheers, Dave
On Thu, Sep 15, 2022 at 12:44 PM Rob Kutschke @.***>
wrote:

@.**** approved this pull request.
One thing I noticed is that you changed these from *SeedFit to *DriftFit.
I presume this is returning to the original intent?
—
Reply to this email directly, view it on GitHub
https://github.com/Mu2e/Production/pull/202#pullrequestreview-1109750260,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABAH573LR6K43GVALTDEZITV6N4AJANCNFSM6AAAAAAQM46AUU
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
David Brown            @.***
Office Phone<PHONE_NUMBER>
Lawrence Berkeley National Lab
M/S 50R5008 (50-6026C)  Berkeley, CA 94720


Provide best practice plans

https://appscode.slack.com/archives/CGDV0U52R/p1552000499011800

Dup https://github.com/appscode/service-broker/issues/48


Getting this error a lot for my lambda: "it does not seem like sst dev is running"

https://github.com/sst/sst/issues/3856

same here with a python function and local mac m1

Could fix it for my case.
It seems this error was related with missing python dependencies. While I made a prod deployment I saw that "command uv not found". So I installed uv on my machine and now dev is working!
BUT: When I call the python function after prod deployment, I get a 500 with following message in the logs Error importing numpy: you should not try to import numpy from         its source directory; please exit the numpy source tree, and relaunch         your python interpreter from there.

Could fix it for my case.
It seems this error was related with missing python dependencies. While I made a prod deployment I saw that "command uv not found". So I installed uv on my machine and now dev is working!
BUT: When I call the python function after prod deployment, I get a 500 with following message in the logs Error importing numpy: you should not try to import numpy from its source directory; please exit the numpy source tree, and relaunch your python interpreter from there.

Numpy has native dependencies, I would recommend using the container runtime by setting python:  { container: true } on your python function. Packages that require native dependencies can sometimes not build properly when using the zip archive deployment that is enabled by default

I'm running into this issue as well, unrelated to Python. I maybe be calling a function multiple times but after a few minutes this message would start coming up from any functions deployed while on dev.

we're going to rework our live lambda implementation this week - streaming over IoT seems like it's not very stable, going to go back to api gateway ws

The development of my project had to completely stop because of this issue. I tried rolling back to multiple previous versions, clear .sst, disable auto-attach debugging, but nothing helped. All Trpc calls I was making to lambda were throwing this error.
All until I ran sst remove once, earlier today. Since then, I haven't seen more errors.
Let's see if this proves to be a reliable workaround.

To add some context, I see the same problem with a classical typescript node lambda function. It appears randomly from time to time but seems like it happens more often when the lambda gets "hammered" ;) and I run a big Playwright testsuite against it.

All until I ran sst remove once, earlier today. Since then, I haven't seen more errors. Let's see if this proves to be a reliable workaround.

To be clear: sst remove is a temporary fix. It makes it possible to keep developing my project, as long as I run sst remove once in a while. I also have keep the auto-attach off as it seems that the error is triggered way more often when the debugger is running.


Add badges for GHA workflows to README

To provide better visibility into the status of the test/release
automation of the repo.
Signed-off-by: Daniel Farrell<EMAIL_ADDRESS>

Broken link is fixed in https://github.com/submariner-io/submariner-operator/pull/801.


[SPARK-37087][SQL] Merge three relation resolutions into one

What changes were proposed in this pull request?

Today, Spark has 3 analyzer rules to resolve relations: ResolveTempViews, ResolveTables and ResolveRelations. This leads to duplicated code, and also makes it harder to figure out the resolution logic, as you need to look at three rules and think about their interactions.
This PR merges these three rules into one.
Why are the changes needed?

code simplification
Does this PR introduce any user-facing change?

no
How was this patch tested?

existing tests

Test build #144510 has started for PR 34358 at commit 80b4a9f.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/48982/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/144510/


Added additional functional tests for ElementalValueProvider

Issue - #1823.
Ported some tests from http://aspnetwebstack.codeplex.com/SourceControl/changeset/0e974218e12a67d4b1f25422119e40cfe6953e46#file_diff_test/System.Web.Http.Test/ModelBinding/ModelBindingEndToEndTests.cs
@pranavkm @yishaigalatzer

:watch:

:shipit: from me. @pranavkm any more comments?

:shipit:


Monitoring screen responsiveness

Signed-off-by: Tushar3099<EMAIL_ADDRESS>Fixes:  #346
Type of change

[x] 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 not to work as expected)

[ ] This change requires a documentation update

Changes

Earlier monitoring screen was static and didn't change size with changing window size.
Now, the monitoring screen shrinks according to the window size up to a given limit (till all columns are visible).

Screenshot

Hi @Harkishen-Singh, please review my PR and let me know if it needs some changes.


I noticed P2300R10 renames get_delegatee_scheduler to get_delegation_schduler

This does that rename leaving deprecated names.

/ok to test

thanks, ben!


Macast: Add version 0.7

Closes to #7758

[-] I have read the Contributing Guide.

Is Macast-Windows-v0.7.exe an installer or a direct executable?

it is a direct executable file

/verify


Adding test for redirects in sw-precaching

R: @jeffposnick @addyosmani
This adds redirects for testing the sw-precache.

Note: The redirect: 'follow' doesn't seem to add anything in terms of browser support for browsers today. Still worth having for older browsers, but it would be good to confirm it actually has an affect on a browser somewhere.

@jeffposnick happy to merge this?


CVE-2024-27280

The Azure CPI seems to be affected by https://www.ruby-lang.org/en/news/2024/03/21/buffer-overread-cve-2024-27280
Even though the issue doesn't seem to be critical we should update the used Ruby version to 3.2.3

fixed with https://github.com/cloudfoundry/bosh-azure-cpi-release/pull/692


Update variables.tf

Corrected Some minor spelling corrections in descriptions.

Hi @CCOSTAN,
Never too late ? Thanks for the PR, I just merged it. I did not notice this before, really sorry.


Prediction result automatically closes on Nvidia jetson xavier AGX

Hello,
I tried to run the image recognition tutorial and when I run
./imagenet.py images/orange_0.jpg images/test/output_0.jpg
The system starts processing and then the output windows automatically closes. Any idea why?

Hi @tulbureandreit ,
Can you share some more details on the hardware which you are using and which JP is it?
Also, is the output image getting saved in your images/test/output_0.jpg
The most relatable answer to your query is that since you are just processing 1 input image, the tiler/display window opens up and closes after processing the inference.
Thanks

The most relatable answer to your query is that since you are just processing 1 input image, the tiler/display window opens up and closes after processing the inference.

Thanks @rajeshroy402, I also believe this to be the correct answer.
If you want it to stay open forever, you can keep looping the image with --input-loop=-1
https://github.com/dusty-nv/jetson-inference/blob/master/docs/aux-streaming.md#input-options


Migrate coordinator-worker protocol from json to a binary format

Binary formats often have better space-efficiency. Msgpack and bincode are under consideration.

Closed by 3d7f237176c4af1a6cac001b0f1ced429d58d3fc


wrong APK at latest tag?

Looks like the APK at v2.61.17 is the same one as that on v2.61.14 (identifies with the same versionCode and is even binary identical). Could it be you accidentally attached the wrong file? Could you please replace it with the correct one? Thanks in advance!

@watea any chance? Or shall I rather disable update-checks for your app in my repo to avoid the error being reported over and again? :wink:

@IzzySoft Sorry for late answer, was not so available those last days. Fixed; should be fine now.

Confirmed – thanks!


Increase webhook sync timeout to 20

Created second const variable WEBHOOK_SYNC_TIMEOUT = 20 for sync webhooks. Variable is passing as a function parameter in send_webhook_using_http where default value is a previous timeout (WEBHOOK_TIMEOUT). Both consts have been moved to the settings.py file.

Impact

[ ] New migrations
[ ] New/Updated API fields or mutations
[ ] Deprecated API fields or mutations
[ ] Removed API types, fields, or mutations
[ ] Documentation needs to be updated

Pull Request Checklist

[ ] Privileged queries and mutations are guarded by proper permission checks
[ ] Database queries are optimized and the number of queries is constant
[ ] Database migration files are up to date
[ ] The changes are tested
[ ] GraphQL schema and type definitions are up to date
[ ] Changes are mentioned in the changelog

Task linked: SALEOR-4422 Increase timeout for sync webhooks

We need this change on master as well.


Support NetmapSnapshot request

Related and blocked by https://github.com/nspcc-dev/neofs-api/pull/228.

Closed via #337.


Instruction to install PowerShellGet without Install-Module

Summary of the new feature / enhancement
Alpine Linux now has a powershell package but it does not come with Install-Module, so there is no way to install PowerShellGet using existing instructions.
Could we document instructions on how to install PowerShellGet without a prior installation?
Proposed technical implementation details (optional)
E.g.

Identify library path of PowerShell installation
Drop binary/source file in library path

What you are suggesting would ultimately mean that every package maintainer who makes modules for powershell would have to provide bespoke instructions for alpine linux. It would be much more efficient if the maintainer for powershell under alpine would just provide those instructions, or implement install-module themselves.
It seems this is also mentioned here:
https://github.com/PowerShell/PowerShell/issues/20143
Though, to answer where you could install the modules, you could put them in this location according to some sources online:
~/.local/share/powershell/Modules

Instructions for installing Package Managers for a program language runtime is extremely common:

PIP offers instructions to install on Python install without PIP
Composer offers instruction to install on PHP
NPM used to offer ways to install itself on Node.js before it was fully bundled with Node.js.

Package Manager should figure figure out which path it takes:

If it expects itself to be bundled with the language runtime, it should be available in all major distribution channels language runtime is available.
If it expects itself to not be bundled with the language runtime, it should have curl-esque instructions on how to install itself on a bare language runtime.

The instructions are in readme.md already.
Your issue is due to a bug with the version of powershell distributed on alpine, which is documented in the link in my previous comment.
The manual instructions are:
Get PowerShellGet Source
Steps

Obtain the source
Download the latest source code from the release page (https://github.com/PowerShell/PowerShellGet/releases) OR Clone the repository (needs git)

git clone https://github.com/PowerShell/PowerShellGet

Navigate to the source directory

cd path/to/PowerShellGet

Import the module

Import-Module src/PowerShellGet -Force

If import-module is also missing on your distro, this needs to be brought up with the maintainer of powershell for your distro, not here.
Those commands are supposed to be usable by default, as stated in the issue I linked earlier.

The problem is due to lack of Import-Module.

If import-module is also missing on your distro, this needs to be brought up with the maintainer of powershell for your distro, not here.

Love your open source passion. However, I am simply a user here to report a compatibility issue between 2 major pieces of open source software. It is not user's job to facilitate communications between software projects.
In similar vein, if Photoshop has compatibility issues with Windows, do you expect a hobbyist designer to travel between Redmond and San Jose facilitate communication between Microsoft and Adobe?


Fix Path3D picking working incorrectly when viewport is in half resolution

Fixes https://github.com/godotengine/godot/issues/89885
Have to use some Node3DEditorViewport 's functionality so that requires expose three camera related private functions.

Thanks!

Cherry-picked for 4.2.2.


AWS Lambda does not work

I just cloned aws sample project. packaged as jar.
https://github.com/spring-cloud/spring-cloud-function/tree/master/spring-cloud-function-samples/function-sample-aws
	@Bean
	public Function<String, String> uppercase() {
		return value -> value.toUpperCase();
	}

This is what I get when I use the handler as org.springframework.cloud.function.adapter.aws.FunctionInvoker::handleRequest
FunctionInspector is deprecated. There is no need to access FunctionRegistration directly since you can interogate the actual looked-up function (see FunctionInvocationWrapper.: java.lang.UnsupportedOperationException
java.lang.UnsupportedOperationException: FunctionInspector is deprecated. There is no need to access FunctionRegistration directly since you can interogate the actual looked-up function (see FunctionInvocationWrapper.
    at org.springframework.cloud.function.context.catalog.SimpleFunctionRegistry.getRegistration(SimpleFunctionRegistry.java:138)
    at org.springframework.cloud.function.adapter.aws.FunctionInvoker.start(FunctionInvoker.java:137)

What is the alternative for SpringBootRequestHandler ? It says deprecated. but does not provide info what else to use?
It would be great if the doc provides detailed steps. I can also update the doc If I know the steps!! :(
it will be deployable in AWS if you get the JAR file laid out right.

This is actually a regression on the master due to the recent improvements in FunctionCatalog implementation. We will address it before the release. That said you should not have any issues 3.0.12.RELEASE

@olegz i am really sorry to say this - take a look at this https://github.com/spring-cloud/spring-cloud-function/issues/619
It still does not work.
Please do not mistake me with my question. Have you tried running yourself in recent times? Can you share the dependencies and sample code you had used.


Aliases doesn't work when explicitly invoked as bash

Hello @sachaos
I've followed this comment to test alias support in bash. And my minimal .profile looks like
if [ -f "/home/linuxbrew/.linuxbrew/bin/brew" ]; then
    eval "$(/home/linuxbrew/.linuxbrew/bin/brew shellenv)"
fi
alias k='kubectl'

When I try to call viddy in interactive shell like following
viddy --shell sh --shell-options "-l" k get all

the alias works. But when I invoke it as a bash
viddy --shell bash --shell-options "-l" k get all

I'm getting this error

Environment
$ uname -srvmpio
Linux <IP_ADDRESS>-microsoft-standard-WSL2 #1 SMP Thu Jan 11 04:09:03 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=22.04
DISTRIB_CODENAME=jammy
DISTRIB_DESCRIPTION="Ubuntu 22.04.3 LTS"
$ bash --version
GNU bash, version 5.1.16(1)-release (x86_64-pc-linux-gnu)

@eshepelyuk Hi. Thank you for using this tool.
Do you have ~/.bash_profile ~/.bash_login?

After reading that file, it looks for ~/.bash_profile, ~/.bash_login, and ~/.profile, in that order, and reads and executes commands from the first one that exists and is readable.

https://linux.die.net/man/1/bash

@eshepelyuk Hi. Thank you for using this tool.
Do you have ~/.bash_profile or ~/.bash_login?

After reading that file, it looks for ~/.bash_profile, ~/.bash_login, and ~/.profile, in that order, and reads and executes commands from the first one that exists and is readable.

https://linux.die.net/man/1/bash

i only have ~/.profile

@eshepelyuk
Thank you. I could reproduce the problem.
I found the solution.
Please try with the -i option (viddy --shell bash --shell-options "-li" k get all).
We are running the command in viddy with the -c option (bash -c "k get all").
However, aliases are not expanded in bash non-interactive mode.
So, we should set bash to interactive mode to expand aliases.
Alternatively, if you set shopt -s expand_aliases in .profile, that would work as well.

Ahh, so bash doesn't expand aliases in non-interqctive mode, but [da]sh does, right?

@eshepelyuk Yes, I think so.

@eshepelyuk Yes, I think so.

thanks for the explanation.


Debug output in log

Since the last changes I get any dump() output on console
{
	place = {
		["pie:brpd_0"] = 2,
		__total = 12,
		["mtg_plus:harddiamondblock"] = 1,
		["farming:scarecrow_bottom"] = 9
	},
	name = "Alex",
	unlocked = {

	},
	death = {
		unknown = 0,
		__total = 0
	},
	join = 21,
	dig = {
		__total = 11,
		["default:dirt_with_snow"] = 1,
		["default:tree"] = 5,
		["default:pine_tree"] = 4,
		["farming:scarecrow_bottom"] = 1
	},
	craft = {
		["farming:scarecrow_bottom"] = 1,
		["default:pine_wood"] = 4,
		__total = 21,
		["default:stick"] = 16
	},
	chat = 0
}

Yeah, left in from debugging


Set up AWS EC2 instance for generating Debian packages nightly

Checklist

[X] I've read the contribution guidelines.
[X] I've searched other issues and no duplicate issues were found.
[X] I've agreed with the maintainers that I can plan this task.

Description
With the latest changes in the Debian builder GitHub action and the fixes in Autoware, it is now possible to build Debian packages in a GitHub action. However, the process takes longer than 6 hours, and so GitHub cancels the job (see https://github.com/esteve/autoware_packages/actions/runs/4640002506/jobs/8211476529 for a failing job).
The limits for GitHub-hosted runners can be found in https://docs.github.com/en/actions/learn-github-actions/usage-limits-billing-and-administration#usage-limits
Whereas the limits for self-hosted runners (e.g. AWS) can be consulted in https://docs.github.com/en/actions/hosting-your-own-runners/about-self-hosted-runners#usage-limits
Purpose
Being able to generate Debian packages every night.
Possible approaches
Integrate the on-demand self-hosted AWS EC2 runner action (https://github.com/marketplace/actions/on-demand-self-hosted-aws-ec2-runner-for-github-actions) to start an EC2 instance, generate the Debian packages and then shut down the EC2 instance.
Alternatively, there are some speedups that could be accomplished in the GitHub action, but those may require significant rewrites. Nevertheless, the GitHub-hosted runners are quite resource limited so having an AWS EC2 instance generating the Debian packages is still a sensible approach.
Definition of done
Debian packages for all the buildable packages (i.e. no CUDA for now) are generated nightly.

I ran into an issue in the action that spawns EC2 instances on demand (see https://github.com/machulav/ec2-github-runner/pull/122 for context), but I fixed the issues in my fork (https://github.com/esteve/ec2-github-runner/tree/Optionally-execute-runner-as-a-service) and successfully ran a whole build of the 2023.04 release in https://github.com/esteve/autoware_packages/actions/runs/4977821022 and the packages can be downloaded from https://github.com/esteve/autoware_packages/tree/jammy-humble

@esteve can we close this issue since this is being tracked by:

https://github.com/autowarefoundation/autoware/issues/3222

Or is this issue for setting this up in the AWF organization?

@xmfcx this ticket can be closed, thank for the heads up.


Follow system theme?

Is there a way to be able to make catpuccin follow the system's theme?
I saw this user that I guess wanted to do it https://github.com/catppuccin/tmux/issues/83
There's a user that wrote a tmux plugin that would use dark-notify (macOS) to detect when the system preference changes and would update the a symlink to a theme that .tmux.conf reads from and then would re-source the .tmux.conf again, but it seems catpuccin is not as simple.
It would be very nice to have a theme hot-swap in catpuccin's tmux flavor (set -g @catppuccin_flavour 'latte' for light and moccha for dark).
Thanks for the super great themes and organization 🙏

While the idea seems interesting, this is out of scope for now.
The plugin you mentioned looks to do exactly what you are asking.


Create insertionsort.cpp

insertion sort algo cpp file

insertion sort

You must have to add your algorithms to the respective directories. Follow the contributing guidelines.
Thank you


Add qt5network

Weird, why does it link to /usr/lib64/libk5crypto.so.3 on fedora

I helped a lot SirLynix, it should be fixed now !

I think there should be built-in ssl library in qt sdk, like qtlibpng, zlib, qtharfbuzz ..

/usr/bin/ld: /usr/lib64/libk5crypto.so.3: undefined reference to EVP_KDF_ctrl@OPENSSL_1_1_1b' /usr/bin/ld: /usr/lib64/libk5crypto.so.3: undefined reference to EVP_KDF_CTX_free@OPENSSL_1_1_1b'
/usr/bin/ld: /usr/lib64/libk5crypto.so.3: undefined reference to `EVP_KDF_CTX_new_id@OPENSSL_1_1_1b'

It seems to depend on a modified version of openssl (with evp-kdf)
https://github.com/sailfishos/openssl/blob/master/rpm/openssl-1.1.1-evp-kdf.patch

It's possible but I find it weird, how does it work when you install Qt on Fedora normally?

It's possible but I find it weird, how does it work when you install Qt on Fedora normally?

It works if the system openssl (with evp-kdf) is installed on fedora.
sudo dnf install openssl-devel

It's possible but I find it weird, how does it work when you install Qt on Fedora normally?

It works if the system openssl (with evp-kdf) is installed on fedora.
sudo dnf install openssl-devel
$ nm -D /usr/lib64/libcrypto.so | grep EVP_KDF_ctrl
0000000000126190 T EVP_KDF_ctrl@@OPENSSL_1_1_1b
0000000000126280 T EVP_KDF_ctrl_str@@OPENSSL_1_1_1b

Thanks for checking, what's the best way to handle this here? Change openssl package to include KDF on Fedora? Or require qt5network to have system-wide openssl on Fedora?

Or require qt5network to have system-wide openssl on Fedora?

right, we use this solution now. In the future we can also improve openssl to support evp-kdf


NextJS Support

Does this library officially support NextJS, or have any plans to? When trying to integrate it to a larger existing NextJS codebase, I received the following error:
Unhandled Runtime Error
TypeError: react__WEBPACK_IMPORTED_MODULE_0__.useId is not a function

Call Stack
eval
node_modules/cmdk/dist/index.mjs (1:719)

However, when trying to make a minimal reproduction, I failed to get it to load at all, with Next complaining of a missing webpack loader -- not sure what loader is required in this instance.
See codesandbox here: https://codesandbox.io/s/charming-darkness-gw9ezm
TL;DR - Library doesn't seem to work with NextJS right now.

Sounds like you're not using React 18, which is required and mentioned explicitly.


Temporarily ignore rustsec warning for unmaintained instant

Via https://github.com/kube-rs/kube/issues/1635
Should ideally upgrade out the library or find a replacement, but it's not super serious. Making builds green for now.

This should be fine, instant is a pretty trivial crate (especially if you don't care about wasm). It does mean it will trigger the same warning for downstream users though.


how to get the eosjs error ???

   try {
      this.$gobal.eos.transaction("liontoken",con=>{
        con.transfer("liontoken","eosio","10 LON","transfer")

      }).then(function (value){
        console.log(value);
        return value;
      });
    }
    catch (e) {
      console.log(e);
    }

Error: {"code":500,"message":"Internal Service Error","error":{"code":3060002,"name":"account_query_exception","what":"Account Query Exception","details":[{"message":"Fail to retrieve account for eosio.token","file":"chain_plugin.cpp","line_number":561,"method":"get_abi"}]}}
at eval (webpack-internal:///./node_modules/eosjs-api/lib/apigen.js:115:23)
(anonymous function)
callback
(anonymous function)
Uncaught (in promise) Error: {"code":500,"message":"Internal Service Error","error":{"code":3060002,"name":"account_query_exception","what":"Account Query Exception","details":[{"message":"Fail to retrieve account for eosio.token","file":"chain_plugin.cpp","line_number":561,"method":"get_abi"}]}}
(anonymous function)
# console output error,how to get the error in program,the catch and value can't get???

I would also like to know this. Did you figure it out?

this.$gobal.eos.transaction("liontoken",con=>{
        con.transfer("liontoken","eosio","10 LON","transfer")

      }).then(function (value){
        console.log(value);
        return value;
      }).catch(function (e) {
      console.log(e);
    })


Fix documentation rake task to support v1-style autocorrect

Seen in https://github.com/rubocop-hq/rubocop-rails/pull/299
This PR modifies generate_cops_documentation rake to support v1-style autocorrect by extending AutoCorrector.
Fix taken from rubocop: https://github.com/rubocop-hq/rubocop/blob/343f62e4555be0470326f47af219689e21c61a37/tasks/cops_documentation.rake#L50

Before submitting the PR make sure the following are checked:

[x] Wrote good commit messages.
[ ] Commit message starts with [Fix #issue-number] (if the related issue exists).
[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[ ] Added tests.
[ ] Added an entry to the Changelog if the new code introduces user-observable changes. See changelog entry format.
[ ] If this is a new cop, consider making a corresponding update to the Rails Style Guide.
[x] The PR relates to only one subject with a clear title
and description in grammatically correct, complete sentences.
[x] Run bundle exec rake default. It executes all tests and RuboCop for itself, and generates the documentation.

Thanks!


docs: k8s application module support

Changelog: Title
Ticket: MEN-6803

@TheMeaningfulEngineer I followed almost exactly the chapter on docker update module, so basically this is following your lead. @tranchitella fyi.

@TheMeaningfulEngineer  I will follow up with whatever comments you may have.


Master Category Toggle disappeared!

One of my favorite and most used Toolkit features is the Master Category Toggle (by the way, I think it should be renamed to Categroy Group toggle, since that's what the "Masters" are called now).
But after the recent Toolkit updates, it's totally missing from my budget page.  I have double checked I have it enabled in Toolkit and I have refreshed YNAB.

I just updated the release notes but this feature was modified to take up less visual space in the UI.
It's now just an expand/collapse arrow in the header of your budget table! You can right-click to toggle on/off Solo Mode as well.

Ok, I see the tiny little arrow  (good lord could it be tinier??) - next to the word "Category", but it apparently only collapses and does not expand all the categories when clicked again.
The Solo Mode function also doesn't appear to work correctly.  I don't really use that function and turned it off back when it was its own thing, but if I have all of my categories collapsed and then right click that arrow, it opens my top-most category group, but then if I expand another group it just leaves both that one and the top-most group expanded, so apparently not actually closing the former group as per how you'd expect Solo Mode to function.

Actually, @joshmadewell
It IS being kinda buggy.  It gets locked up and won't work properly after I edit a Target or otherwise mess around in the budget and I have to go to an account page or All Accounts and then back to Budget page and then the arrow functions properly again.

Okay, that definitely sounds like a bug! I'll try to have a look at it some time this week!

Actually, what do you mean by "Edit A Target" -- I changed a budgeted value and I'm not seeing anything lock up after.

I wasn't sure what exactly triggered the arrow to stop working right, but one thing I did between it working and then realizing it wasn't working was editing the Target of one of my categories, so I just mentioned it in case maybe that was the trigger.  I'll see if I can recreate the issue and let you know.  It's been twice now that I go to use the arrow and it has stopped working.

Aha!  I found it - It's when I went to a future month.  And it happens again when trying to go back to current month.
So it appears changing the month (in either direction) breaks the Arrow function.
Currently, it's a quick fix to go to All Accounts and then jump back to Budget no matter what month you're in, but switching back to the other month breaks it again.

Ah, got it -- I see that now as well! I'll get this fixed in our next release! Thanks for debugging for me!

You bet!  Thanks!


SQL Editor: keep database and schema after disconnect

Description
When SQL Editor for Snowflake has a selected schema, it disappears from the selector after disconnecting and connecting again (it doesn't happen with invalidate tool)
DBeaver Version
DBeaver CE 24.3.0 ea
Operating System
Win11
Database and driver
Snowflake
Steps to reproduce

Connect to Snowflake, open SQL Editor and select a schema in it, execute a selelect query
Disconnect from the database
Connect again

AR: the schema disappears from the top toolbar, the query can't be executed again because of missed schema
ER: the selected schema is restored after connect, the select query can be executed for it
Note: PostgreSQL and Cockroach keep the database, but change a custom schema on public in the same case.
Additional context
No response

It is reproducible only when Open separate connection is set to false for SQL Editor. It seems to have always worked this way. I checked 21.3.0, and the behavior is the same there.

Also it's reproducible only when schema is not set in the connection configuration

We decided that it's not the bug

Also it's reproducible only when schema is not set in the connection configuration

And the default schema "PUBLIC" doesn't exist


feat: Only git push if we have a remote

But we do a release to crates.io anyways even if the user did not configure any GitHub related settings.
Resolves #116

:+1: – I can take care of the failing tests

So we could change the test:
diff --git i/tests/integration/integration.bats w/tests/integration/integration.bats
index d9ab632..ef9e060 100644
--- i/tests/integration/integration.bats
+++ w/tests/integration/integration.bats
@@ -150,12 +150,12 @@ setup_dirs() {
   [[ "$output" =~ "Current branch is 'master', releases are only done from branch 'hamster'" ]]
 }

-@test "Does not fail when project has no remote" {
+@test "Still tries to publish on crates.io without git remote" {
   cd has-no-remote
   setup_dirs

   CARGO_TOKEN=1234 run semantic-rs --write=yes

-  [ "$status" -eq 0 ]
-  [[ "$output" =~ "semantic-rs can't push changes or create a release on GitHub" ]]
+  [ "$status" -eq 1 ]
+  [[ "$output" =~ "Failed to publish on crates.io" ]]
 }

But then we would hit the crates.io API anyway, which I'd like to avoid.
Two possibilities:

we delete this test (but then we don't test this branch at all)
we call cargo publish with --dry-run in test mode to avoid hitting the API

What do you think?

Coming back to this one. I'd like to keep this test to have this case covered. About (not) hitting crates.io during test I see a couple of options:

We have some sort of switch integrated where when activated the application behaves as it would talk to crates.io but has the corresponding lines shortcircuited (disabled with an ifdef equivalent.
We could do some research if there's anything like VCR available for a test environment we have. Then we would do a crates.io request once and just check it into version control.
We have a fake service in place which pretends to be crates.io. Sebastian once wrote a blog post about that.

WDYT?

Implemented in #128


Leveraging Evolu for Privacy-First AI and Machine Learning Development

I believe Privacy-First AI is a thing, but it will take time to have reliable and fast models working directly on the device.
The ability to run AI/ML models directly on the device without needing constant cloud connectivity enhances privacy and improves performance and reliability, especially in scenarios with limited internet access.
Meanwhile, we need a true local-first and private-first platform and the everything app to collect user data securely, and that's what I am focused on right now.
Let's talk about it.

AI is fuzzy; human reasoning is not. Sure, humans don't have all available data, but we can describe (at least some of us) our decision trees. I know that I don't know everything. AI doesn't know that it doesn't know everything. The future AI has to have emotions and passion. That's what drives our thinking.


Debug doc

Weird, I guess github gets confused now if the branch name has been used before?  It thought there was a conflict, but there wasn't... merged


Shaded region for case stats offset from optimum position

Describe the bug
A clear and concise description of what the bug is. If your issue is regarding an error in the data, it's best reported through this form.
To Reproduce
Steps to reproduce the behavior:

Go to 'https://www.covid19india.org'
Click on 'Confirmed'
Click on 'Active'

Expected behavior
A clear and concise description of what you expected to happen.
Shaded region should match with the shaded part on hover.
Screenshots
If applicable, add screenshots to help explain your problem.
on Hover

Active State

Desktop (please complete the following information):

OS: [macOS]
Browser [Safari]
Version [Catalina]

Additional context
How do I take up this issue?

@JapneetSingh5 I'm not able to reproduce the issue using the steps you provided. I have tried both in Safari and Chrome Canary and is using the same device specs and OS version. 😕

I can confirm that the issue still exists, Safari 13.1 is what I am using.


Update service-r-packages-support.md to include R runtime version

Update the doc to include the R runtime version supported in the service

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

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


AXIS and Spine

The latest commit, https://github.com/adxeproject/adxe/commit/555f847c1f4890ebcab0af75feb0cc32b358f93a, which changed the sampler names, causes graphical issues when using the official Spine runtime.  I realise the built-in Spine code in ADXE was modified to work, but this really should be ported over to the official runtime.
I personally don't use the Spine version that is bundled with ADXE; the one I use is a slightly modified version of the runtime that is available from the official Spine runtime repo.
@halx99 is there any chance you could have a chat to the developers of Spine, and request that they add a new ADXE-specific folder to their runtime repo? This project has diverged from Cocos2d-x, and will continue to do so, and using the cocos2d-x runtime for ADXE no longer makes sense, and will just cause more problems down the line.
If they do agree to add a new runtime folder specific to ADXE, then changes can be pushed to the official runtime, and we won't have to deal with Cocos2d-x related compatibility.

The commit https://github.com/adxeproject/adxe/commit/91e57e7dd32e4c489a93426228d58d35791e0f37 will let user can continue use official spine runtime after post a merge-request to use backend defination sampler name for SkeletonBatch

Oh, that's excellent!
I thought that SkeletonTwoColorBatch.cpp would be affected too, but it is referring to its own shader, and not the backend shader, so that one isn't an issue.

Oh, that's excellent!
I thought that SkeletonTwoColorBatch.cpp would be affected too, but it is referring to its own shader, and not the backend shader, so that one isn't an issue.

Yes

Refer to this PR: https://github.com/EsotericSoftware/spine-runtimes/pull/2104

All good, thank you.

Oh, Axis looks awesome!


DLT-15030 Prepare sample application of ScalarDB Analytics with Spark

Description
This PR adds a sample application of https://github.com/scalar-labs/scalardb-analytics-spark
Related issues and/or PRs
https://scalar-labs.atlassian.net/browse/DLT-15305
Changes made

Added a scalardb-analytics-spark subdirectory, which contains a sample application of ScalarDB Analytics with Spark on Docker environment

Checklist

The following is a best-effort checklist. If any items in this checklist are not applicable to this PR or are dependent on other, unmerged PRs, please still mark the checkboxes after you have read and understood each item.

[x] I have commented my code, particularly in hard-to-understand areas.
[x] I have updated the documentation to reflect the changes.
[x] Any remaining open issues linked to this PR are documented and up-to-date (Jira, GitHub, etc.).
[ ] Tests (unit, integration, etc.) have been added for the changes.
[ ] My changes generate no new warnings.
[ ] Any dependent changes in other PRs have been merged and published.

Additional notes (optional)
None

@josh-wong Thank you for your revision! I've applied those.

@choplin Are you working on this? Just checking since it's been here without changes for a while.

@feeblefakie Sorry for the delay in getting back to reviewers. Yes, I'm working on this along with other documentation-related PRs to keep them consistent. I'll push the updates of this PR as well soon.

@reddikih @kota2and3kan Sorry for the late reply. Yes, the reason why the spark service doesn't run is because the scalardb-analytics-spark has not been released to Maven Central yet. Once https://github.com/scalar-labs/scalardb-analytics-spark/pull/16 is merged, this docker-compose.yaml will work without an error. Or, you can build and publish to the local Maven repository if you want to run ahead.

For reviewers, I created a PR that adds a document on how to run this sample application in https://github.com/scalar-labs/docs-internal-scalardb/pull/31. Please refer to it as well. Note that we cannot run the sample application as it is for now because of ScalarDB Analytics with Spark to Maven Central. I'll let you know once it's published.

For reviewers, since ScalarDB Analytics with Spark has been published to Maven Central, this sample application would work as it is. Regarding how to run this, please refer to this PR (Please review this one, too!).


[SYSTEMML-1373] toString now prints NaN & Infinity like how as.scalar prints them

Fix for inconsistent print for NaN & Infinity from toString.
https://issues.apache.org/jira/browse/SYSTEMML-1373.

@niketanpansare - Could you please take a look?

LGTM :+1:
Thanks @nakul02

Thanks, I'll merge.