JobParameters.java

Hi dears,
I have issues appear on Firebase crashlytics and i couldn't find a solution for them till now as the following:-
- JobParameters.java line 273
android.app.job.JobParameters.completeWork
Fatal Exception: java.lang.RuntimeException: An error occurred while executing doInBackground()
at android.os.AsyncTask$4.done(AsyncTask.java:399)
at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:383)
at java.util.concurrent.FutureTask.setException(FutureTask.java:252)
at java.util.concurrent.FutureTask.run(FutureTask.java:271)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
at java.lang.Thread.run(Thread.java:919)
- JobParameters.java line 282
android.app.job.JobParameters.completeWork
Fatal Exception: java.lang.RuntimeException: An error occurred while executing doInBackground()
at android.os.AsyncTask$4.done(AsyncTask.java:399)
at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:383)
at java.util.concurrent.FutureTask.setException(FutureTask.java:252)
at java.util.concurrent.FutureTask.run(FutureTask.java:271)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
at java.lang.Thread.run(Thread.java:919)
Flutter version 1.20.1
Dart version 2.9.0
Engine revision c8e3b94853
Framework revision 2ae34518b8 (6 months ago), 2020-08-05 19:53:19 -0700
Android Studio (version 4.0)
• Android Studio at C:\Program Files\Android\Android Studio
• Flutter plugin version 48.0.2
• Dart plugin version 193.7361
• Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)

@BeshoyAdelHemaya
your flutter version is quite old, can you run
flutter upgrade -f

and provide your updated flutter doctor -v,  your flutter run --release -v and the list of affected devices

Hi @BeshoyAdelHemaya
Please provide what was asked in the comment above.
Thank you

[√] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
• Android SDK at C:\Users\bhemaya\AppData\Local\Android\sdk
• Platform android-30, build-tools 29.0.2
• Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
• Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)
• All Android licenses accepted.
[!] Android Studio (version 4.1.0)
• Android Studio at C:\Program Files\Android\Android Studio
X Flutter plugin not installed; this adds Flutter specific functionality.
X Dart plugin not installed; this adds Dart specific functionality.
• Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)
[√] Connected device (1 available)
• LYA L29 (mobile) • LHS7N19216018439 • android-arm64 • Android 10 (API 29)

Hi @BeshoyAdelHemaya
This does not seems to be complete!

I updated it to the latest versions
[√] Flutter (Channel stable, 1.22.6, on Microsoft Windows [Version 10.0.19042.746], locale en-US)
• Flutter version 1.22.6 at G:\Flutter\flutter_windows_v1.7.8+hotfix.3-stable00\flutter
• Framework revision 9b2d32b605 (2 weeks ago), 2021-01-22 14:36:39 -0800
• Engine revision 2f0af37152
• Dart version 2.10.5

We need

and provide your updated flutter doctor -v, your flutter run --release -v and the list of affected devices

as well.
Do you have any more crash logs information to share? This does not seems enough to find the root cause of the issue.
Are you able to reproduce the issue?

Hi @pedromassangocode we got the issues from Firebase Crashlytics as we couldn't have any device reproduce the issues so i think we will need to publish the new release and feedback you with Firebase Crashlytics results.
On the other side we run the commends you mentioned and below are the results.
G:\Flutter\flutter_windows_v1.7.8+hotfix.3-stable00\flutter\bin\flutter doctor -v
[√] Flutter (Channel stable, 1.22.6, on Microsoft Windows [Version 10.0.19042.746], locale en-US)
• Flutter version 1.22.6 at G:\Flutter\flutter_windows_v1.7.8+hotfix.3-stable00\flutter
• Framework revision 9b2d32b605 (2 weeks ago), 2021-01-22 14:36:39 -0800
• Engine revision 2f0af37152
• Dart version 2.10.5
[√] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
• Android SDK at C:\Users\bhemaya\AppData\Local\Android\sdk
• Platform android-30, build-tools 29.0.2
• Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
• Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)
• All Android licenses accepted.
[!] Android Studio (version 4.1.0)
• Android Studio at C:\Program Files\Android\Android Studio
X Flutter plugin not installed; this adds Flutter specific functionality.
X Dart plugin not installed; this adds Dart specific functionality.
• Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)
[√] Connected device (1 available)
• INE LX1 (mobile) • GVV7N18728012673 • android-arm64 • Android 9 (API 28)
! Doctor found issues in 1 category.
The Application is built successfully and release apk generated successfully too

Hi @pedromassangocode we got the issues from Firebase Crashlytics as we couldn't have any device reproduce the issues so i think we will need to publish the new release and feedback you with Firebase Crashlytics results.

Ok, since your Flutter version was too old and looks like you've upgraded to the latest version, I'm going to close this issue for now. Please write in the comments bellow if the issue start to happen again once you release a new version of your app with the latest Flutter version and I will reopen the issue.
Thank you

We updated Flutter version to the latest then we released the new update but we still face the same issues on JobParameters.java as the attached screenshot

Hi @BeshoyAdelHemaya
Can you please provide your flutter doctor -v and your pubspec.yaml?
Thank you

Sure
Flutter Doctor
[√] Flutter (Channel stable, 1.22.6, on Microsoft Windows [Version 10.0.19042.804], locale en-US)
• Flutter version 1.22.6 at G:\Flutter\flutter_windows_v1.7.8+hotfix.3-stable00\flutter
• Framework revision 9b2d32b605 (5 weeks ago), 2021-01-22 14:36:39 -0800
• Engine revision 2f0af37152
• Dart version 2.10.5
[√] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
• Android SDK at C:\Users\bhemaya\AppData\Local\Android\sdk
• Platform android-30, build-tools 29.0.2
• Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
• Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)
• All Android licenses accepted.
[!] Android Studio (version 4.1.0)
• Android Studio at C:\Program Files\Android\Android Studio
• Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)
[√] Connected device (2 available)
• INE LX1 (mobile) • GVV7N18728012673 • android-arm64 • Android 9 (API 28)
• LYA L29 (mobile) • LHS7N19216018439 • android-arm64 • Android 10 (API 29)
pubspec.yaml
name: ic_filfan
description: FilFan
environment:
sdk: ">=2.1.0 <3.0.0"
dependencies:
flutter:
sdk: flutter
json_annotation: ^2.0.0
validate: ^1.7.0
intl: ^0.16.0
The following adds the Cupertino Icons font to your application.
Use with the CupertinoIcons class for iOS style icons.
cupertino_icons: ^0.1.2
http: any
flutter_google_ad_manager: ^0.10.1 #was ^0.10.1 but had issues with iOS bec. it was referencing another pod with deprecated and unfound files
flutter_localizations:
sdk: flutter
flutter_cupertino_localizations: ^1.0.1
gradient_widgets: ^0.5.0
connectivity: ^0.3.2
share: ^0.6.3+6
shared_preferences: ^0.5.3+4
flutter_advanced_networkimage: ^0.6.4
auto_size_text: ^2.1.0
async: ^2.2.0
scroll_to_index: ^1.0.2
popup_menu: ^1.0.3
random_string: ^1.1.0
get_it: ^3.0.0+1
get_version: ^0.1.0
flutter_dialog: ^0.0.1
firebase_core : ^0.5.0+1
firebase_analytics: ^5.0.16
#firebase_crashlytics: ^0.1.4+1
firebase_crashlytics: ^0.2.1+1 #^0.1.3+3
rate_my_app: ^0.7.2 #rate_my_app: ^0.6.1+6
smooth_star_rating: ^1.1.1
netmera_flutter_sdk: ^1.0.5
uni_links: ^0.2.0
flutter_widgets: ^0.1.6
fluttertoast: ^4.0.1 #was 4.0.0 but had issues in ios
#device_info: ^0.4.0+4
flushbar: ^1.10.4 #^1.10.4 had an issue with ios build (method 'FlushbarRoute.install' has fewer positional arguments) (https://github.com/AndreHaueisen/flushbar/issues/110#issuecomment-619368001)
pull_to_refresh: ^1.5.7
flutter_inappwebview: ^4.0.0+4 #was ^3.1.0
flutter_tags: ^0.4.8
flutter_swiper: ^1.1.6
timeago: ^2.0.26
youtube_player_flutter: ^6.1.1  #was 6.1.0+7
flutter_html: ^0.11.1
photo_view: ^0.9.2
image_downloader: ^0.19.2
carousel_slider: ^2.0.0
huawei_analytics: ^4.0.4
huawei_ads:
path: ./huawei_ads/
dev_dependencies:
flutter_test:
sdk: flutter
json_serializable: ^2.0.0
flutter_lifecycle_state: ^1.0.0
build_runner: ^1.1.2
flutter_launcher_icons: ^0.7.3
url_launcher: ^5.0.2
#device_apps: ^1.0.9
flutter_icons:
image_path: "assets/app_icon.png"
android: true
ios: true
For information on the generic Dart part of this file, see the
following page: https://www.dartlang.org/tools/pub/pubspec
The following section is specific to Flutter.
flutter:
The following line ensures that the Material Icons font is
included with your application, so that you can use the icons in
the material Icons class.
uses-material-design: true
assets:
- assets/
- assets/filfan.html
An image asset can refer to one or more resolution-specific "variants", see
https://flutter.io/assets-and-images/#resolution-aware.
For details regarding adding assets from package dependencies, see
https://flutter.io/assets-and-images/#from-packages
To add custom fonts to your application, add a fonts section here,
in this "flutter" section. Each entry in this list should have a
"family" key with the font family name, and a "fonts" key with a
list giving the asset and other descriptors for the font. For
example:
fonts:
- family: Schyler
fonts:
- asset: fonts/Schyler-Regular.ttf
- asset: fonts/Schyler-Italic.ttf
style: italic
- family: Trajan Pro
fonts:
- asset: fonts/TrajanPro.ttf
- asset: fonts/TrajanPro_Bold.ttf
weight: 700

For details regarding fonts from package dependencies,
see https://flutter.io/custom-fonts/#from-packages
fonts:
- family: din
fonts:
- asset: fonts/din.otf

Can you please provide the crash logs if they are somehow different from the ones you shared in the OP?
Thank you

JobParameters.java line 273
Fatal Exception: java.lang.RuntimeException: An error occurred while executing doInBackground()
at android.os.AsyncTask$AsyncFutureTask.done(AsyncTask.java:429)
at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:383)
at java.util.concurrent.FutureTask.setException(FutureTask.java:252)
at java.util.concurrent.FutureTask.run(FutureTask.java:271)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
at java.lang.Thread.run(Thread.java:929)
Caused by java.lang.IllegalArgumentException: Given work is not active: JobWorkItem{id=2 intent=Intent { act=onPushRegister (has extras) } dcount=1}
at android.app.job.JobParameters.completeWork(JobParameters.java:273)
at androidx.core.app.JobIntentService$JobServiceEngineImpl$WrapperWorkItem.complete(JobIntentService.java:268)
at androidx.core.app.JobIntentService$CommandProcessor.doInBackground(JobIntentService.java:394)
at androidx.core.app.JobIntentService$CommandProcessor.doInBackground(JobIntentService.java:383)
at android.os.AsyncTask$3.call(AsyncTask.java:389)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
at java.lang.Thread.run(Thread.java:929)
JobParameters.java line 282
Fatal Exception: java.lang.RuntimeException: An error occurred while executing doInBackground()
at android.os.AsyncTask$4.done(AsyncTask.java:399)
at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:383)
at java.util.concurrent.FutureTask.setException(FutureTask.java:252)
at java.util.concurrent.FutureTask.run(FutureTask.java:271)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
at java.lang.Thread.run(Thread.java:919)
Caused by java.lang.IllegalArgumentException: Given work is not active: JobWorkItem{id=1 intent=Intent { act=onPushReceive (has extras) } dcount=1}
at android.app.job.JobParameters.completeWork(JobParameters.java:282)
at androidx.core.app.JobIntentService$JobServiceEngineImpl$WrapperWorkItem.complete(JobIntentService.java:268)
at androidx.core.app.JobIntentService$CommandProcessor.doInBackground(JobIntentService.java:394)
at androidx.core.app.JobIntentService$CommandProcessor.doInBackground(JobIntentService.java:383)
at android.os.AsyncTask$3.call(AsyncTask.java:378)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
at java.lang.Thread.run(Thread.java:919)
JobParameters.java line 268
Fatal Exception: java.lang.RuntimeException: An error occurred while executing doInBackground()
at android.os.AsyncTask$3.done(AsyncTask.java:354)
at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:383)
at java.util.concurrent.FutureTask.setException(FutureTask.java:252)
at java.util.concurrent.FutureTask.run(FutureTask.java:271)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
at java.lang.Thread.run(Thread.java:764)
Caused by java.lang.IllegalArgumentException: Given work is not active: JobWorkItem{id=1 intent=Intent { act=onPushReceive (has extras) } dcount=1}
at android.app.job.JobParameters.completeWork(JobParameters.java:268)
at androidx.core.app.JobIntentService$JobServiceEngineImpl$WrapperWorkItem.complete(JobIntentService.java:268)
at androidx.core.app.JobIntentService$CommandProcessor.doInBackground(JobIntentService.java:394)
at androidx.core.app.JobIntentService$CommandProcessor.doInBackground(JobIntentService.java:383)
at android.os.AsyncTask$2.call(AsyncTask.java:333)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
at java.lang.Thread.run(Thread.java:764)
JobParameters.java line 316
Fatal Exception: java.lang.RuntimeException: An error occurred while executing doInBackground()
at android.os.AsyncTask$4.done(AsyncTask.java:415)
at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:383)
at java.util.concurrent.FutureTask.setException(FutureTask.java:252)
at java.util.concurrent.FutureTask.run(FutureTask.java:271)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
at java.lang.Thread.run(Thread.java:923)
Caused by java.lang.IllegalArgumentException: Given work is not active: JobWorkItem{id=2 intent=Intent { act=onPushDismiss (has extras) } dcount=1}
at android.app.job.JobParameters.completeWork(JobParameters.java:316)
at androidx.core.app.JobIntentService$JobServiceEngineImpl$WrapperWorkItem.complete(JobIntentService.java:268)
at androidx.core.app.JobIntentService$CommandProcessor.doInBackground(JobIntentService.java:394)
at androidx.core.app.JobIntentService$CommandProcessor.doInBackground(JobIntentService.java:383)
at android.os.AsyncTask$3.call(AsyncTask.java:394)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
at java.lang.Thread.run(Thread.java:923)
JobParameters.java line 312
Fatal Exception: java.lang.RuntimeException: An error occurred while executing doInBackground()
at android.os.AsyncTask$4.done(AsyncTask.java:415)
at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:383)
at java.util.concurrent.FutureTask.setException(FutureTask.java:252)
at java.util.concurrent.FutureTask.run(FutureTask.java:271)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
at java.lang.Thread.run(Thread.java:923)
Caused by java.lang.IllegalArgumentException: Given work is not active: JobWorkItem{id=1 intent=Intent { act=onPushRegister (has extras) } dcount=2}
at android.app.job.JobParameters.completeWork(JobParameters.java:312)
at androidx.core.app.JobIntentService$JobServiceEngineImpl$WrapperWorkItem.complete(JobIntentService.java:268)
at androidx.core.app.JobIntentService$CommandProcessor.doInBackground(JobIntentService.java:394)
at androidx.core.app.JobIntentService$CommandProcessor.doInBackground(JobIntentService.java:383)
at android.os.AsyncTask$3.call(AsyncTask.java:394)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
at java.lang.Thread.run(Thread.java:923)
JobParameters.java line 233
Fatal Exception: java.lang.RuntimeException: An error occurred while executing doInBackground()
at android.os.AsyncTask$3.done(AsyncTask.java:365)
at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:383)
at java.util.concurrent.FutureTask.setException(FutureTask.java:252)
at java.util.concurrent.FutureTask.run(FutureTask.java:271)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
at java.lang.Thread.run(Thread.java:784)
Caused by java.lang.IllegalArgumentException: Given work is not active: JobWorkItem{id=1 intent=Intent { act=onPushReceive (has extras) } dcount=1}
at android.app.job.JobParameters.completeWork(JobParameters.java:233)
at androidx.core.app.JobIntentService$JobServiceEngineImpl$WrapperWorkItem.complete(JobIntentService.java:268)
at androidx.core.app.JobIntentService$CommandProcessor.doInBackground(JobIntentService.java:394)
at androidx.core.app.JobIntentService$CommandProcessor.doInBackground(JobIntentService.java:383)
at android.os.AsyncTask$2.call(AsyncTask.java:345)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
at java.lang.Thread.run(Thread.java:784)
I mentioned all crash logs we faced on our two Apps.

It would help a bit if could provide your pubspec.yaml. This may be something to do with any Android plugin. You can share both pubspec files of the two apps crashing.
Thank you

Both Apps have same sdks. I sent you yaml of one of them above. Most of these crashes appear with high percentage on background. I am not sure if these issues related to push notifications that we implement using Flutter_netmera sdk or not.

Hi @pedromassangocode , Do you need any inputs from my side ?

Hi @pedromassangocode , Do you need any inputs from my side ?

No, thank you!

There is no Flutter frame in any of the backtraces, JobParameters is not used by directly by the engine, and there is no reproducible test case. This issue is not actionable in its current state.
Looks like @pedromassango is still working on finding the responsible plugin. If that is not successful, we'll need a reproducible test case.

JobParameters is not used by directly by the engine

So I fear that there is nothing the Flutter team can do about this issue.

I am not sure if these issues related to push notifications that we implement using Flutter_netmera sdk or not.

I was not able to find the responsible plugin. @BeshoyAdelHemaya can you please try to remove it and see if the issue still happening without it? I would suggest to do the same with all other plugins until you find the responsible plugin.
If by any chance you find the steps to reproduce please let me know.
Thank you

@pedromassangocode I will try your suggestion but i am not sure if i will success or not.

Without additional information, we are unfortunately not sure how to resolve this issue.
We are therefore reluctantly going to close this bug for now.
Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.
Could everyone who still has this problem please file a new issue with the exact description of what happens, logs, and the output of flutter doctor -v.
All system setups can be slightly different, so it's always better to open new issues and reference related issues.


received a notification for a version that does not currently exist in the npm registry

version 0.21.0 does not exist in the registry, see http://registry.npmjs.org/cheerio
greenkeeper PR here: https://github.com/npm/docs/pull/707
revert PR here: https://github.com/npm/docs/pull/711
i see version 0.21.0 in the package.json on github: https://github.com/cheeriojs/cheerio/blob/master/package.json
but history.md only has 0.20.0: https://github.com/cheeriojs/cheerio/blob/master/History.md
anyways. weird stuff. lemme know if you need any more info!

looks like 0.21.0 was published "0.21.0": "2016-06-12T05:34:11.519Z" ... and unpublished?

Hey Ashley 👋
thanks for reporting this.
The whole behavior reminds of this issue we had before: https://github.com/greenkeeperio/greenkeeper/issues/156
My stance from back then (March 31) was this:

I just tried to publish a completely new package and to unpublish a few versions to see what the metadata looks like, but unpublish is completely broken for me right now. First I couldn't unpublish anything at all and then I managed to unpublish something, but it was possible to republish the exact same version again.

When looking at the metadata while the version was still unpublished it didn't show up in versions at all.

I suspect that these bugs are caused by some internal restructurings npm is currently performing in order to implement their new unpublish policy.

#157 seems a bit drastic to me, especially given that<EMAIL_ADDRESS>apparently wasn't unpublished, but an npm bug. Given the new policy we will see far less unpublishes in the future. With the old policy in place this problem hasn't occurred for Greenkeeper even once.

Here is my current stance on this: No action required. npm will fix these bugs. Unpublishes will occur very, very rarely. If so they aren't necessarily for newest versions that Greenkeeper acts upon. Delaying the entire service for 24hours does not seem appropriate to me.

Happy to change my mind if we see these things happen again.

Thanks for reporting and your feedback everyone! We're sorry for any inconveniences.

Could you comment on whether this evaluation still seems appropriate?
Thanks a lot,
Stephan

We should probably also await a comment here: https://github.com/cheeriojs/cheerio/issues/888

hey @boennemann - so npm isn't doing anything with the metadata due to the new unpublish policy, but i'm open to the idea that we should.
https://github.com/greenkeeperio/greenkeeper/issues/157 <- this makes a lot of sense given our unpublish policy.
https://github.com/greenkeeperio/greenkeeper/issues/156<- if you look at http://registry.npmjs.org/color you'll see that 0.12.0 shows up in the time object, but not the versions object. this is what an unpublished package looks like on npm- so it isn't an error, but actually behaving as expected

so yeah, not entirely sure what should be done, but if greenkeeper doesn't wait 24hrs after publish, it will make PRs that could potentially be invalid as the package can be unpublished within that window. does greenkeeper follow unpublish events? this is another way to avoid waiting 24hrs.

(also as always: yay greenkeeper is awesome keep up the awesome work)
this issue isn't a huge deal as people rarely unpublish, but it's probably worth thinking about (basically this is not a :fire: so no rush)

I suspected some bugs back then, because I managed to republish and the color maintainer commented that they haven't unpublished anything.
In the current cheerio case it looks like a regular (accidental maybe?) unpublish.
In this case I think the best experience would be to close these PRs as soon as we know a version was unpublished. We currently keep track of all versions we have previously processed, so it should be possible to detect unpublishes as soon as we see a version that was previously processed but is no longer in the versions object.
I can't promise the highest priority for this, but it's something we should add in the future.
Thanks for your lovely words! We <3 your work, too ✨

This is also happening to me. More info here: https://github.com/mysterycommand/fartts/pull/15#issuecomment-372787964

We talked to the npm team and they suggest adding a delay on our end to account for variability on theirs. This is a change in policy and guidance from the last time we discussed this with them. We’ll implement the delay shortly.

This is currently being tested in our staging environment and will be deployed with the next roll-out to production.


Fixes memory leak due to not deleting freertos socket set

This is an issue that probably went over the top of the head of everyone as this transport was added before the "ping" util was added.
However, when using the "Ping" it'd create a socket and a socket set to do Select, to later never release the socket set.

How soon can we expect this PR to be backported to galactic (foxy)? We can run with the custom change for now, but we'd prefer to use the CI-generated library we have.

As soon as this is merged it will be in foxy and galactic.
@Acuadros95 take a look here please


Docusaurus pages aren't working

https://hms-networks.github.io/sc-ewon-flexy-extensions-lib/ is dead

Hi @TomKimsey,
I was able to replicate the issue and have implemented a fix. You should now be able to access the documentation website as expected.

@alexjhawk


setConfigurableConstants Error

What version of fuels-ts are you using?
0.89.1
Steps to Reproduce
"configurables": [
{
"name": "MAX_SUPPLY",
"configurableType": {
"name": "",
"type": 20,
"typeArguments": null
},
"offset": 38352
}
] --- configurables in abi
const configurableConstants = {
MAX_SUPPLY: maxSupply,
};
const factory = new ContractFactory(bytecode, NativeAssetContractAbi__factory.abi, wallet)
factory.setConfigurableConstants(configurableConstants)
Expected Behavior
no exception
Actual Behavior
node_modules/@fuel-ts/contract/src/contract-factory.ts:197
throw new FuelError(
^
_FuelError: Error setting configurable constants on contract: offset is out of bounds.
at ContractFactory.setConfigurableConstants (/home/cherideal/work/ShareWin/fuel-swap/Play-Ground/node_modules/@fuel-ts/contract/src/contract-factory.ts:197:13)
at /home/cherideal/work/ShareWin/fuel-swap/Play-Ground/src/index.ts:62:13
at step (/home/cherideal/work/ShareWin/fuel-swap/Play-Ground/src/index.ts:33:23)
at Object.next (/home/cherideal/work/ShareWin/fuel-swap/Play-Ground/src/index.ts:14:53)
at /home/cherideal/work/ShareWin/fuel-swap/Play-Ground/src/index.ts:8:71
at new Promise ()
at __awaiter (/home/cherideal/work/ShareWin/fuel-swap/Play-Ground/src/index.ts:4:12)
at deploy_token_contract (/home/cherideal/work/ShareWin/fuel-swap/Play-Ground/src/index.ts:53:72)
at /home/cherideal/work/ShareWin/fuel-swap/Play-Ground/src/index.ts:83:11
at step (/home/cherideal/work/ShareWin/fuel-swap/Play-Ground/src/index.ts:33:23) {
VERSIONS: { FORC: '0.60.0', FUEL_CORE: '0.27.0', FUELS: '0.89.1' },
metadata: {},
code: 'invalid-configurable-constants'
}

@danielbate Could it be something related to encoding?

Hmm it is likely a mismatch between the ABI and the bytecode being called, @cherideal could you share more info please such as the forc and fuel-core version you are using. An emaple repo would be really helpful.

[toolchain]
channel = "nightly-2024-05-28"
[components]
forc = "0.60.0+nightly.20240528.4fe6f1ed51"
fuel-core = "0.26.0"
cherideal@ubuntu:~$ forc --version
forc 0.60.0+nightly.20240604.0e567287b4
cherideal@ubuntu:~$ fuel-core --version
fuel-core 0.27.0+nightly.20240604.0463dfd8bb
cherideal@ubuntu:~$ npm fules --version
10.7.0

Would it be possible to get a minimal repo example containing the built ABI and bytecode?

https://github.com/bookswapxyz/fuel-swap/tree/main
I have change forc/fuel-core version and work fine now, you need change the version back.

Okay, good yes any mismatch in the forc version will mean a mismatch in the deployed bytecode vs the offsets in the ABI. Please could you close the issue if this is fixed.


gateway-api: Add owning gateway namespace label

Description
This commit is to add owning gateway namespace label for generated LB service, the main reason is to avoid wrong status update for gateways having the same name, but belonged to different namespace.
Testing was done locally as per below:
Before the fix:
$ kg gateway -A
NAMESPACE   NAME         CLASS    ADDRESS          PROGRAMMED   AGE
another     my-gateway   cilium   <IP_ADDRESS>   True         4s
default     my-gateway   cilium   <IP_ADDRESS>   True         56s

After the fix:
$ kg gateway -A
NAMESPACE   NAME         CLASS    ADDRESS          PROGRAMMED   AGE
another     my-gateway   cilium   <IP_ADDRESS>   True         14m
default     my-gateway   cilium   <IP_ADDRESS>   True         14m

$ kg services -A
NAMESPACE     NAME                           TYPE           CLUSTER-IP       EXTERNAL-IP      PORT(S)                      AGE
another       cilium-gateway-my-gateway      LoadBalancer   <IP_ADDRESS>   <IP_ADDRESS>   80:31424/TCP                 15m
default       cilium-gateway-my-gateway      LoadBalancer   <IP_ADDRESS>   <IP_ADDRESS>   80:31889/TCP                 15m
...

Fixes: https://github.com/cilium/cilium/issues/31270

/test

/test

/test

/test


Folder structure in find references view

If a pretty large project is opened in vs.code, and references are found, they are displayed in a linear view. It would be nice to have an option to display them in a folder view, i.e. only relevant folders and files are shown, and usages are shown as children of file nodes.
I think I am capable of implementing it myself. Do you think it's a useful thing to do? Can I expect some directions on this from somebody on the team?

The same can be done in the changes view as well.

@jrieken I implemented it myself. See the issue automatically referenced by github here.


Provide completion for Runtime IDs (RIDs)

According to https://docs.microsoft.com/en-us/dotnet/core/rid-catalog we shouldn't attempt to build RIDs programmatically, and we should treat them as black boxes.
Should we provide completion for them anyway, by parsing the keys in https://github.com/dotnet/runtime/blob/master/src/libraries/pkg/Microsoft.NETCore.Platforms/runtime.json?

Added completion in 819eca67d02c70f2c00cf0a23a105930d004170c.
Need to double check it does nothing if it can't reach the site 🤔  (yes I'm thinking aloud after submitting the code...)


Delete User Error: This operation is sensitive and requires recent authentication. Log in again before retrying this request.

Description
I've configured Apple as a sign-in provider with Firebase, and provided all necessary information on the console to enable OAuth code flow.
When deleting a user account, I exactly followed the docs example here:
func authorizationController(controller: ASAuthorizationController,
                             didCompleteWithAuthorization authorization: ASAuthorization) {
  guard let appleIDCredential = authorization.credential as? ASAuthorizationAppleIDCredential
  else {
    print("Unable to retrieve AppleIDCredential")
    return
  }

  guard let _ = currentNonce else {
    fatalError("Invalid state: A login callback was received, but no login request was sent.")
  }

  guard let appleAuthCode = appleIDCredential.authorizationCode else {
    print("Unable to fetch authorization code")
    return
  }

  guard let authCodeString = String(data: appleAuthCode, encoding: .utf8) else {
    print("Unable to serialize auth code string from data: \(appleAuthCode.debugDescription)")
    return
  }

  Task {
    do {
      try await Auth.auth().revokeToken(withAuthorizationCode: authCodeString)
      try await user?.delete()
      self.updateUI()
    } catch {
      self.displayError(error)
    }
  }
}

The flow is:

The user requests deletion of their account.
I ask the user to Sign in with Apple again.
If the sign-in was successful (see above code), first revoke the token, then delete the Firebase account.

After the third step, I got this error:
This operation is sensitive and requires recent authentication. Log in again before retrying this request.

I know this error is being thrown by this line:
try await user?.delete()

I know this because I got an email from Apple Support notifying me that my app has revoked my tokens, and that I will need to sign in again the next time I try to use the app.
The docs mention that the user needs to have re-authenticated within 5 minutes:

FIRAuthErrorCodeRequiresRecentLogin
Indicates the user has attempted to change email or password more than 5 minutes after signing in.

In the case of my app, it was within seconds.
Reproducing the issue
Please see the code above for a minimal reproducible example.
Firebase SDK Version
11.3.0
Xcode Version
16.0
Installation Method
Swift Package Manager
Firebase Product(s)
Authentication
Targeted Platforms
iOS
Relevant Log Output
This operation is sensitive and requires recent authentication. Log in again before retrying this request.

If using Swift Package Manager, the project's Package.resolved

Expand Package.resolved snippet

Replace this line with the contents of your Package.resolved.

If using CocoaPods, the project's Podfile.lock

Expand Podfile.lock snippet

Replace this line with the contents of your Podfile.lock!

Hi @occassionally, is this a flow you are implementing for the first time, or something that was working in a previous Firebase version before upgrading to 11.3?

@ncooke3 Thanks for the quick response! This is the first time I've attempted it, so unfortunately I'm not sure if it was working before or not.

I got it to work, but I didn't do anything differently.
I didn't think it could be the case, but I thought maybe there is an issue with trying to delete a user after the tokens have been revoked.
try await Auth.auth().revokeToken(withAuthorizationCode: authCodeString)
try await user?.delete()

I tested it with only revokeToken, and it worked. Then I tested it with only delete, and it worked.
Then, just to confirm, I tested it again with both, and to my surprise, it worked. I tested it a few more times and it's worked each time since.
I made no changes at all, though. It's great that its working, but it's a little concerning still, since I don't know if or when it could happen again.

@occassionally, glad to hear it's working now. I'm unsure what was going wrong earlier.
I tested this with a test app and didn't run into this. The implementation is a little different from the sample code

https://github.com/firebase/firebase-ios-sdk/blob/a366d6c4982df6d724c95f4ed399fe444593e9e5/FirebaseAuth/Tests/SampleSwift/AuthenticationExample/ViewControllers/UserViewController.swift#L229-L627
https://github.com/firebase/firebase-ios-sdk/blob/main/FirebaseAuth/Tests/SampleSwift/AuthenticationExample/ViewControllers/UserViewController.swift#L357-L381

Mainly, the reauthentication gets called right before the delete request:
https://github.com/firebase/firebase-ios-sdk/blob/a366d6c4982df6d724c95f4ed399fe444593e9e5/FirebaseAuth/Tests/SampleSwift/AuthenticationExample/ViewControllers/UserViewController.swift#L255C1-L262C32


[sqlite-orm] update to 1.7.1

Describe the pull request

What does your PR fix?

Yes

All features are tested successfully in the following triplet:

x86-windows
x64-windows
x64-windows-static

Thanks for the update!


Have Portable Executables

I wanted to have a single portable executable.
How to package used dlls into the executable changed somewhere from VS2013 to VS2019 …
Now the costura fody package is obsolete and the Visual Studio "Publish" functionality should be used.
Also I wanted to have an executable that can be used in command line as well as a GUI application.
This appears to be more difficult than expected.
Either you have A) an exe that flashes a commandline windows quickly on start of the gui if launched without arguments.
Or you have B) no output on console or (if attached to the console) C) the call is non-blocking and output comes too late.

I decided to now provide separate GUI and CLI exes.
The "normal" exe only contains the GUI (using the library functionality).
The CLI exe is using option A): It supports command line arguments as well as showing the gui … but has the ugly cmd window in gui mode.
Solved with commit 1c63f34c0e39d57d99e46772d7bbd62f25669c92


BUAA-VisNir data are not aligned

Hi, I downloaded the BUAA-VisNir data from the given link (Baidu Drive). But I found that the data in the compressed file are still raw images with a shape of 640x480.
Could you please upload an aligned version of this dataset? Thank you!

Is this problem solved? Thanks

Hi. Can you let me know, how to download the database? I dont have the "entry code" to avail the download option.

entry code is xmbc

entry code seems incorrect, has it been changed?

entry code seems incorrect, has it been changed?

do you know the entry code?   dataset download from irip.buaa.edu.cn/system/_content/download.jsp?urltype=news.DownloadAttachUrl&owner=1240132834&wbfileid=1277824  has error


adjusted Service principal login flow doc steps

added detailed steps for Service principal login flow

@TomGeske LGTM, let me know when you'd like to merge it

@weinong: let's merge it. I will issue another PR for addtional changes.


create datafusion 6.0.0, ballista 0.6.0 and python 0.4.0 releases

Rationale for this change
Prepare for the 6.0.0 release.
We have way more changes than I initially expected :D
Also cc @rdettai
What changes are included in this PR?

New changelogs
Improve release automations

Are there any user-facing changes?
no

I am quite comfortable with the release automation tools and documentation now, I think next time, any committer should be able to run the release so I won't be the only one who is running the releases.

thanks for the update @houqp - i guess i can help with releasing next time (or a minor one, like 6.1)

Looking forward to being a committer and running the release, LOL 😁

Do you plan a release blog? I would love to help make one.

Please go ahead @alamb ! I won't have time to do this until the release has been cut and voted. We can all collaborate to the blog like the last one @andygrove wrote.

oh by the way after this is cut and release i will help with the homebrew formula update

Going to wait for @xudong963 's set changes for 6.0.0 release since those PRs look pretty complete and mostly ready to merge :)

Please go ahead @alamb ! I won't have time to do this until the release has been cut and voted. We can all collaborate to the blog like the last one @andygrove wrote.

Here is an initial shot: https://github.com/apache/arrow-site/pull/160
I may have missed something

@houqp Maybe README also need update: https://github.com/apache/arrow-datafusion/blob/master/README.md#using-datafusion-as-a-library
[dependencies]
datafusion = "5.0.0"

to
[dependencies]
datafusion = "6.0.0"

Thanks @xudong963 for catching that, I have updated the version bump automation to cover README.md going forward.

🎉


improve cloud selection ui

cloudlens $ go run .

At the top keep it "CloudLens" and use "Select Cloud"


"Tame Mobs" Stage Bug

Quests V:3.3.4
Whenever you add a "Tame Mobs" stage to a quest, upon doing /questadmin reload, any quest with this stage automatically gets deleted. I created a new quest and set up all the required stuff for a quest. I set the first stage to Tame Mobs (14) and set it to tame cows x2, and pigs x2. Upon saving and reloading, the quest was deleted. I decided to try and edit a pre-existing quest to add this stage. Same steps, tame mobs, cow x2/pig x2, save, /questadmin reload. This caused the other quest to get deleted as well. There are no console errors that I have found so far.
Found the issue. Any sort of normal mobs are not listed as tamable mobs.

These are the only mobs that work:

That's because cows and pigs are not tamable mobs. How were you able to add them? Did the in-game menu accept "Pig" even though it's not in the list, or did you edit the config?

I guess I confused tamable with breedable, but to answer your question, it did allow me to input cow in the in-game editor. If I had an animal already set, then switched it to cow, it would automatically switch back, but if I added the stage for the first time and picked cow, it would accept the input then automatically delete the quest upon saving.


Fixed interaction with the server share in the auto annotation plugin

Resolved #466
We also need to create the new release

@bsekachev, hotfix branch should be forked from master and contain only "minor changes" to fix a specific issue. It seems you forked it from develop. Nobody has tested develop well yet.

@nmanovic
Actually I did the changes in the develop branch, next I checkout to the master and forked the hotfix branch from it. Finally I cherry-picted the commit with changes from the develop branch. It seems to be github considers such case like fork from develop whereas my local git application shows me all as expected.
It is confusing, but anyway I'll fix it.

@nmanovic  Done


Hot to convert []byte to float?

As I understand, the one way to get document field values is VisitStoredFields. Callback retrive value as []byte.
So, text fields is simply converted via string(value).
But how to convert Numeric (float64) fields?
I tried
func Float64frombytes(bytes []byte) float64 {
	bits := binary.BigEndian.Uint32(bytes)
	float := math.Float32frombits(bits)
	return float64(float)
}

and
func Float64frombytes(bytes []byte) float64 {
	bits := binary.BigEndian.Uint64(bytes)
	float := math.Float64frombits(bits)
	return float
}

But both of them does not works correct.
I tried LittleEndian - still no result.

I don't know why, but when I "just try to found solution" - it does not work.
But if I write issue - I'll found solution in 5 second.
There is function bluge.DecodeNumericFloat64(value []byte) (float64, error) which can decode value to float64.
May be you can add this to docs?

In the future I'll wait a few minutes before spending time on it.
Yes this is the correct answer to your question.

Sorry :)
But I think this issue will help someone in future.


Setting up the UI of sudoku solver boxes in the front page

I have a good idea to make the sudoku solver boxes look attractive.
Kindly assign me this issue under JWoC'24.
@Spandan-Bhattacharya

Which boxes are you mentioning here?

@Spandan-Bhattacharya  pls assign me this issue under JWOC


[codeql] Updated rules

What does this PR do?
Updated codeql github worflow to follow these rules:

run on PR, allowed to fail
not run on merge queue
run on main (mandatory)

Motivation

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

/merge


code optimization

Signed-off-by: Dmitry Shmulevich<EMAIL_ADDRESS>I've been running performance Prometheus performance profiling and noticed excessive CPU usage by labels.New() function.
This simple optimization has improved CPU usage by 5% in my tests.

@krasi-georgiev would you be able to restart the test? From the logs it seems some infra issue, not related to the code change. Are you the right person for this type of requests?


TypeError: Object of type 'ndarray' is not JSON serializable

WORKER 0 seed:<PHONE_NUMBER>
Traceback (most recent call last):
File "./pytorch/train.py", line 306, in train
ret_dict = net_parallel(example_torch)
File "/home/chi_zhang/anaconda3/envs/second_alpha/lib/python3.6/site-packages/torch/nn/modules/module.py", line 489, in call
result = self.forward(*input, **kwargs)
File "/home/chi_zhang/yz/second_alpha/second.pytorch/second/pytorch/models/voxelnet.py", line 363, in forward
preds_dict = self.network_forward(voxels, num_points, coors, batch_size_dev)
File "/home/chi_zhang/yz/second_alpha/second.pytorch/second/pytorch/models/voxelnet.py", line 335, in network_forward
preds_dict = self.rpn(spatial_features)
File "/home/chi_zhang/anaconda3/envs/second_alpha/lib/python3.6/site-packages/torch/nn/modules/module.py", line 489, in call
result = self.forward(*input, **kwargs)
File "/home/chi_zhang/yz/second_alpha/second.pytorch/second/pytorch/models/rpn.py", line 394, in forward
res = super().forward(x)
File "/home/chi_zhang/yz/second_alpha/second.pytorch/second/pytorch/models/rpn.py", line 318, in forward
x = self.blocksi
File "/home/chi_zhang/anaconda3/envs/second_alpha/lib/python3.6/site-packages/torch/nn/modules/module.py", line 489, in call
result = self.forward(*input, **kwargs)
File "/home/chi_zhang/yz/second_alpha/second.pytorch/torchplus/nn/modules/common.py", line 89, in forward
input = module(input)
File "/home/chi_zhang/anaconda3/envs/second_alpha/lib/python3.6/site-packages/torch/nn/modules/module.py", line 489, in call
result = self.forward(*input, **kwargs)
File "/home/chi_zhang/anaconda3/envs/second_alpha/lib/python3.6/site-packages/torch/nn/modules/conv.py", line 320, in forward
self.padding, self.dilation, self.groups)
RuntimeError: CUDA out of memory. Tried to allocate 34.38 MiB (GPU 0; 11.75 GiB total capacity; 780.10 MiB already allocated; 7.81 MiB free; 11.03 MiB cached)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "./pytorch/train.py", line 663, in
fire.Fire()
File "/home/chi_zhang/anaconda3/envs/second_alpha/lib/python3.6/site-packages/fire/core.py", line 138, in Fire
component_trace = _Fire(component, args, parsed_flag_args, context, name)
File "/home/chi_zhang/anaconda3/envs/second_alpha/lib/python3.6/site-packages/fire/core.py", line 471, in _Fire
target=component.name)
File "/home/chi_zhang/anaconda3/envs/second_alpha/lib/python3.6/site-packages/fire/core.py", line 675, in _CallAndUpdateTrace
component = fn(*varargs, **kwargs)
File "./pytorch/train.py", line 421, in train
print(json.dumps(example["metadata"], indent=2))
File "/home/chi_zhang/anaconda3/envs/second_alpha/lib/python3.6/json/init.py", line 238, in dumps
**kw).encode(obj)
File "/home/chi_zhang/anaconda3/envs/second_alpha/lib/python3.6/json/encoder.py", line 201, in encode
chunks = list(chunks)
File "/home/chi_zhang/anaconda3/envs/second_alpha/lib/python3.6/json/encoder.py", line 428, in _iterencode
yield from _iterencode_list(o, _current_indent_level)
File "/home/chi_zhang/anaconda3/envs/second_alpha/lib/python3.6/json/encoder.py", line 325, in _iterencode_list
yield from chunks
File "/home/chi_zhang/anaconda3/envs/second_alpha/lib/python3.6/json/encoder.py", line 404, in _iterencode_dict
yield from chunks
File "/home/chi_zhang/anaconda3/envs/second_alpha/lib/python3.6/json/encoder.py", line 437, in _iterencode
o = _default(o)
File "/home/chi_zhang/anaconda3/envs/second_alpha/lib/python3.6/json/encoder.py", line 180, in default
o.class.name)
TypeError: Object of type 'ndarray' is not JSON serializable
i have reduce the batch size to 2, but the error is still there. i use the titan v which has 12G gpu memory.

CUDA_VISIBLE_DEVICES=7 python ./pytorch/train.py train --config_path=./configs/car.fhd.onestage.config --model_dir=logs-test/

RuntimeError: CUDA out of memory. Tried to allocate 34.38 MiB (GPU 0; 11.75 GiB total capacity; 780.10 MiB already allocated; 7.81 MiB free; 11.03 MiB cached)

@forvd I change to the former version which use the spconv1.0

Im getting this error when running on a AWS, but not when running local... any insight on how to solve it?

please try to add those words  torch.backends.cudnn.enabled=False at the head of train.py

please try to add those words torch.backends.cudnn.enabled=False at the head of train.py

it didn't work for me


Remove Skype for Business Server 2019 from all the 'Applies To" sub-header/section.

Extensible Messaging and Presence Protocol (XMPP) proxy on the Edge Server and an XMPP Gateway on the Front End Server or Front End pool used to be available only on Lync Server 2013 and Skype for Business Server 2015, however, in Skype for Business Server 2019 this component is deprecated. The docs article is showing the cmdlet in this article is applicable to Skype for Business Server 2019 as well which is incorrect. It must be either removed under “Applies To” sub header / section or put an Note as below.
Note : The XMPP in Skype for Business 2019 is deprecated and this cmdlet is only applicable to Lync Server 2013 / Skype for Business Server 2015 pools/servers when you have the Co-Existence environment with Skype for Business 2019.

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

ID: 4c262047-4f88-fd45-f1b1-814fe581bd47
Version Independent ID: e89e9da2-7020-4549-3ca6-2f64b6bc0bef
Content: New-CsXmppAllowedPartner (skype)
Content Source: skype/skype-ps/skype/New-CsXmppAllowedPartner.md
Service: skypeforbusiness-powershell
GitHub Login: @kenwith
Microsoft Alias: kenwith

@NeeranjanShettar Thank you for this feedback
I will get this information to the PowerShell Team for investigation.
The team will get this prioritized into a sprint plan. Thank you for reporting and making the docs better. Much appreciated.
I made a note to request the team to update this when the work is complete.

Do we have any updates here, it's been long time there are no updates/response. thanks in advance

@get-itips Could you please investigate this?

Skype For Business 2019 has already been removed from the doc https://github.com/MicrosoftDocs/office-docs-powershell/commit/b0174cacde851ee7e032eeb891bc74693ece2a7d#diff-6355e6342fda7a72057106ac6b0af2b5 Thanks @AndreaBarr @NeeranjanShettar


Android: createEventWithPrompt without permissions

Hi @ebarooni,
Thanks a lot for this great plugin! In our app, we only have a single use-case of adding events to the users calendars. For this, we use createEventWithPrompt.
On iOS this does not require any permissions.
On Android, the current implementation needs READ_CALENDAR permission. This should not be necessary.
The problem is the following line:
https://github.com/ebarooni/capacitor-calendar/blob/469e0827577ab72e6a63933b5d0dff7d0db298c7/android/src/main/java/dev/barooni/capacitor/calendar/CapacitorCalendarPlugin.kt#L49
If we comment it out, everything works as expected. The app requires no permissions and the user can add events to their calendar. If I understand it correctly, the only downside is that we cannot retrieve the resulting event IDs.
Could you wrap fetchCalendarEventIDs in a try/catch or return an empty array of event IDs if no permission has been granted?

Hi @theigl , thanks for the suggestion! I will think about it a bit and will probably provide a way to have the ability to opt out of receiving the id of the generated event in exchange of not having to request read access to the calendar.

Thanks a lot @ebarooni! 🙏


Deposits always show 0 confirmations

User wallet seems to has no other issues. Deposits show up in the deposit history in user's wallet but the transaction never updates the confirmations, so then the deposit doesn't get credited to the user's wallet. What could cause this to happen? Where would be the first place to look to try to resolve this issue?
Any help would be greatly appreciated

I get this error in the log: payment_transaction.rb.output
Error on PaymentTransaction::Normal: undefined local variable or method `c' for #Deposits::Mobitglobal:0x00560b86fb7c90


Update search.json

Added missing translations
Got some code for us? Awesome 🎊!
Please include a description of your change & check your PR against this list, thanks!

[x] There's a clear use-case for this code change, explained below
[x] Commit message has a short title & references relevant issues
[x] The build will pass (run yarn test:all and yarn lint)

We appreciate your contribution!

Question:  ChatGPT suggests that the verb tenses should be imperative rather than infinitive ( cerca vs cercar , cancel-la vs cancel-lar), since these are UI actions or buttons.  I know that's broadly true for some related languages, but I don't know how Catalan does it.  A quick reply that you've considered it and infinitive is correct would be appreciated.

Hi @Zagur ! Do you have a moment to review these Catalan refinements?

Question: ChatGPT suggests that the verb tenses should be imperative rather than infinitive ( cerca vs cercar , cancel-la vs cancel-lar), since these are UI actions or buttons. I know that's broadly true for some related languages, but I don't know how Catalan does it. A quick reply that you've considered it and infinitive is correct would be appreciated.

Yeah, it's a country-wide issue. According to Softcatalà seems like Imperative is preferred although infinitive is correct. I like infinitive more because it doesn't offer the tu vs vostè debate (Cercar is more inclusive than "cerca" or "cerqueu") but I know we're just a minority thinking like that.
I'll adapt to infinitive for the time being, and leave this discussion for future debate if need be.


[FEATURE] @snowpack/plugin-webpack support webpack 5

The problem that you want to solve.
To be able to use @snowpack/plugin-webpack with webpack 5
Are you willing to submit a pull request to implement this change?
Probably

@snowpack/plugin-webpack now has v5 support thanks to @mcha-dev! 🎉
Since this could be a big change, I’ve created a new prerelease at @snowpack/plugin-webpack@next. Would love to get feedback on this and see if any initial bugs are present before releasing a stable version.
cc @mcha-dev @ludofischer


Added scalatests for tokenService and loginService in example

Fixes #68

Current coverage is 86.14%

Merging #69 into master will increase coverage by +6.14% as of c948010

@@            master     #69   diff @@
======================================
  Files           37      21    -16
  Stmts          460     267   -193
  Branches        14      14
  Methods          0       0
======================================
- Hit            368     230   -138
  Partial          0       0
+ Missed          92      37    -55

Review entire Coverage Diff as of c948010

Powered by Codecov. Updated on successful CI builds.

@trane did you get a chance to review this?

No plans to merge this. As this was just a work in progress and already replaced by new code.


[W7.7][W09-B4] Bamboo

Updated the following sections of Developer Guide:

Use Cases

User Stories

NFR

Glossary

@cjianhui @Procrastinatus @nassy93 some comments added. please read and ack; please retain the PR without closing.

@cjianhui @Procrastinatus @nassy93
Would like to draw your attention to this PR immediately.
Please merge all changes to your org's master branch and make a new PR to AB-L4; I cannot see the changes made to other documents or the code now, hence will be unable to provide any feedback


RestTemplateEurekaHttpClient not closing HttpClient on shutdown

Spring Cloud 2021.0.0
Spring Boot 2.6.8
Bug Description:
RestTemplateEurekaHttpClient is not closing HttpClient on shutdown. This leads to TCP CLOSE_WAIT connections to eureka server.
EurekaClient will shutdown when an exception occurs on an http request, but not shutdown HttpClient
This bug is related to https://github.com/spring-cloud/spring-cloud-netflix/blob/27ac3379f6b391ccd605d212512f15c439825ecb/spring-cloud-netflix-eureka-client/src/main/java/org/springframework/cloud/netflix/eureka/http/RestTemplateEurekaHttpClient.java#L203
In case of exception here:
https://github.com/Netflix/eureka/blob/ed0da19ca1c049c87e3dbf75b6015c1861d5c2d0/eureka-client/src/main/java/com/netflix/discovery/shared/transport/decorator/RedirectingEurekaHttpClient.java#L96
new HttpClient will be created without closing the existing one - this causes CLOSE_WAIT connections
This supplier creates new CloseableHttpClient for every call to https://github.com/spring-cloud/spring-cloud-netflix/blob/27ac3379f6b391ccd605d212512f15c439825ecb/spring-cloud-netflix-eureka-client/src/main/java/org/springframework/cloud/netflix/eureka/http/RestTemplateTransportClientFactory.java#L103
public class DefaultEurekaClientHttpRequestFactorySupplier implements EurekaClientHttpRequestFactorySupplier {

	@Override
	public ClientHttpRequestFactory get(SSLContext sslContext, @Nullable HostnameVerifier hostnameVerifier) {
		HttpClientBuilder httpClientBuilder = HttpClients.custom();
		if (sslContext != null) {
			httpClientBuilder = httpClientBuilder.setSSLContext(sslContext);
		}
		if (hostnameVerifier != null) {
			httpClientBuilder = httpClientBuilder.setSSLHostnameVerifier(hostnameVerifier);
		}
		CloseableHttpClient httpClient = httpClientBuilder.build();
		HttpComponentsClientHttpRequestFactory requestFactory = new HttpComponentsClientHttpRequestFactory();
		requestFactory.setHttpClient(httpClient);
		return requestFactory;
	}

}

so in case of shutdown, currentEurekaClient shutdown don't closes connections:
https://github.com/spring-cloud/spring-cloud-netflix/blob/27ac3379f6b391ccd605d212512f15c439825ecb/spring-cloud-netflix-eureka-client/src/main/java/org/springframework/cloud/netflix/eureka/http/RestTemplateEurekaHttpClient.java#L203
possible solution will be trying to close the HttpClient:
shutdown could be
public void shutdown() {
        Optional.of(unwrapRequestFactoryIfNecessary(restTemplate.getRequestFactory()))
                .filter(HttpComponentsClientHttpRequestFactory.class::isInstance)
                .map(HttpComponentsClientHttpRequestFactory.class::cast)
                .ifPresent(requestFactory-> {
                    try {
                        requestFactory.destroy();
                    } catch (Exception e) {
                    }
                });
    }

unwrapRequestFactoryIfNecessary
https://github.com/spring-projects/spring-boot/blob/47516b50c39bd6ea924a1f6720ce6d4a71088651/spring-boot-project/spring-boot/src/main/java/org/springframework/boot/web/client/RestTemplateBuilder.java#L746
spring-projects/spring-boot#31075
As you can see process open files increases over time until GC occurred

We can also create EurekaClientHttpRequestFactorySupplier which return the same ClientHttpRequestFactory, but it not a stable solution since we can't control eureka client code, maybe in case of exceptions connections not closes (hence not returns to PoolingHttpClientConnectionManager) - this can lead to no available connections in pool. In that case, restart is required
Original Issue:
https://github.com/spring-cloud/spring-cloud-netflix/issues/4062

https://github.com/spring-projects/spring-boot/issues/31075#issuecomment-1128766582

the piece code instantiating the request factory should be in charge of closing resources properly

Hello, @BenEfrati , thanks for reporting it. Looks like a bug.

Recently, I encountered this problem in the production environment. I found that the httpclient was created many times. The httpclient connection pool did not enable the thread for clearing expired connections. The problem was solved by sharing one httpclient and enabling the IdleConnectionEvaluator thread. The code is as follows:
`
@Configuration
public class EurekaConfig {
private final AtomicReference<CloseableHttpClient> ref = new AtomicReference<>();

@Bean
public EurekaClientHttpRequestFactorySupplier defaultEurekaClientHttpRequestFactorySupplier() {
    return (sslContext, hostnameVerifier) -> {
        HttpComponentsClientHttpRequestFactory requestFactory = new HttpComponentsClientHttpRequestFactory();
        HttpClientBuilder httpClientBuilder = HttpClients
                .custom()
                .evictExpiredConnections()
                .evictIdleConnections(30L, TimeUnit.SECONDS);
        if (sslContext != null) {
            httpClientBuilder = httpClientBuilder.setSSLContext(sslContext);
        }
        if (hostnameVerifier != null) {
            httpClientBuilder = httpClientBuilder.setSSLHostnameVerifier(hostnameVerifier);
        }
        if (ref.get() == null) {
            ref.compareAndSet(null, httpClientBuilder.build());
        }
        requestFactory.setHttpClient(ref.get());
        return requestFactory;
    };
}

}
`

Hello @sdzx3783 - thanks for your comment. Would you like to submit a PR with a fix?

I provide a temporary solution without changing the source code

Hi @OlgaMaciaszek , may I know which version will include the fix?

@dangkhoaphung  if the issue is added to an active backlog, it will be assigned a milestone. We're now prioritising  tasks for the upcoming release and will circle back to non-blocking issues later on. However, feel free to create a PR, and we will definitely review it.

Initial fix reverted due to https://github.com/spring-cloud/spring-cloud-netflix/issues/4275. Reopening.


Running tests changes original data (Guid number)

Must find which test affects original Guid number and rewrite it.

Also - passing test depends on names of files in data folder - need to fix that too.

Not only guid number is affected by tests


Some video links are returning 'Forbidden'

Some video links are returning '403 Forbidden' when I try to open them. After sending one more request to get video information, it fixes but it wasting time.
Here is my code:
def get_tiktok_media(tiktok_username: str, max_count: int):
    try:
        result = []
        with TikTokAPI() as api:
            user = api.user(tiktok_username, max_count)
            for video in user.videos:
                result_video = video
                while result_video.video.play_addr.endswith("chain_token") and result_video.video.download_addr.endswith("chain_token"):
                    result_video =<EMAIL_ADDRESS>
                result.append(result_video)
        return result
    except Exception as e:
        return e

I realize patterns between working videos and not working videos.
Sample working video link:
https://v16-webapp.tiktok.com/612dc7b3bd400a2ccd84af58fdbba950/63d15716/video/tos/useast2a/tos-useast2a-pve-0037c001-aiso/o8DYgoPAliHy5aGSOe2Erh0KfZrfkOEQAHGZeC/?a=1988&ch=0&cr=0&dr=0&lr=tiktok&cd=0%7C0%7C1%7C0&cv=1&br=4260&bt=2130&cs=0&ds=3&ft=4b~OyMlh8Zmo0Cd6I64jVhLWypWrKsdm&mime_type=video_mp4&qs=0&rc=MzY7NmY4OGZnZjY8ZzxmZkBpam87NWU6ZnA6aTMzZjgzM0A0YGIyM182XjExLWExNDUvYSNhLmwzcjRnMTVgLS1kL2Nzcw%3D%3D&l=20230125102117B681AB00030843ACF23F&btag=80000
Sample not working video link:
https://v16-webapp-prime.tiktok.com/video/tos/useast2a/tos-useast2a-pve-0037-aiso/oEbqy7f2KjVLQQDyUec8GCmnBHD80oVhnWPAgD/?a=1988&ch=0&cr=0&dr=0&lr=tiktok&cd=0%7C0%7C1%7C0&cv=1&br=2520&bt=1260&cs=0&ds=3&ft=4fUEKMlh8Zmo03d6I64jVVO1ZpWrKsdm&mime_type=video_mp4&qs=0&rc=NmY4NjNlZDM3M2VnOGU3aUBpM3d2czg6ZnRkaTMzZjgzM0BfMl9gLl9hXzQxMzUxXzQzYSNzcF9kcjRnZzVgLS1kL2Nzcw%3D%3D&btag=80000&expire=1674663675&l=202301251021026E4C2DACC26490AAE1A6&ply_type=2&policy=2&signature=e303281836dfc4b2b8d8acfe4beb9963&tk=tt_chain_token
not working videos are ends with chain_token
I'll be happy if anybody can help me about this.
tiktokapipy version is 0.1.10.post1

This isn't something I've encountered in my testing. It's possible you may need to use a proxy, which should be doable in version 0.1.11. It's worth noting that these links do go stale after a time. I've seen them go stale after anywhere from 30 minutes to 2 hours.

It seems to be permanently blocked probably by some anti-bot mechanisms. 1-2 weeks ago I was able to download some videos (not all of them due to Forbidden issue) but now all videos I'm trying to grab, are blocked. Even if I re-generate link (multiple trials) like @Enes-Kayiklik

Again, I'm not having this problem, so I don't have a good way to debug it. I need some more information:

How soon are you trying to download the video after getting the address with TikTokPy? Are you saving the address somewhere to be used later?
What country/region are you in?
Are you able to access TikTok and watch videos normally through a desktop browser?

If someone experiencing this issue can answer all of these questions I'll be better able to address the issue.

Also experiencing this issue, I tried re-generating the link multiple times with no luck.

Immediately, I've tried downloading the videos using aiohttp demonstrated in the documentation and also manually accessing the URL with no luck.
UK
Yes

import asyncio
import aiofiles
import aiohttp
from tiktokapipy.async_api import AsyncTikTokAPI
from tiktokapipy.models.video import Video

hashtag = "technews"

async def save_video(video: Video):
    async with aiohttp.ClientSession() as session:
        async with session.get(video.video.download_addr) as resp:
            content = await resp.content.read()
            async with aiofiles.open("video.mp4", mode="wb") as f:
                await f.write(content)

async def main():
    async with AsyncTikTokAPI() as api:
        challenge = await api.challenge(hashtag)
        async for video in challenge.videos:
            creator = await video.creator()
            print("===================================")
            print("Username:", creator.unique_id)
            print("Caption:", video.desc)
            await save_video(video)
            break

if __name__ == '__main__':
    asyncio.run(main())

Immediately after URL retrieval. I also checked expiration parameter in URL and it's around 6h but I tried to download video at most after seconds from URL generation.
Poland
It depends. I can access videos (from web browser) via the following URL: https://www.tiktok.com/tag/funnyvideos but when I try to search (https://www.tiktok.com/search/user?q=%23funnyvideos&t=1676928433374) and I click on Videos or The best tab, TikTok requires signing in.
It's one of simple examples but I tried also in different ways. All with the same results: 403 - Forbidden.

    from tiktokapipy.api import TikTokAPI
    import urllib.request as req

    with TikTokAPI() as api:
        videos_wrapper = api.challenge("funnyvideos", video_limit=1)
        for video_el in videos_wrapper.videos:
            link =<EMAIL_ADDRESS>            video = api.video(link)
            req.urlretrieve(video.video.download_addr, "output.mp4")

@papayyg found a solution that works for them in #35. Hopefully this can work for you. I'll add it to the documentation soon.

Yes #35 worked for me. Thank you for your response.


Create snake-water-gun.py

hope you like it

Add snapshots of working project

Rules:-
1)Follow @shubham7668 and add star in this repository
2)No c++/c file will be accepted
3)Add snapshots of working project
Follow all rules in order to get hacktoberfest-accepted tag


Error: Expected int for street

Hi,
I get the following error when entering my data:
Invalid config for [sensor.abfallplus]: expected int for dictionary value @ data['street']. Got '2593bauernschaften'. (See /config/configuration.yaml, line 66). Please check the docs at https://github.com/Bouni/abfallplus
My configuration:
  - platform: abfallplus
    name: "Restmuell"
    key: e21758b9c711463552fb9c70ac7d4273
    municipality: 2593
    street: 2593bauernschaften
    trash_ids: "161, 53, 31, 169"

According to Payload it is the right street:

Version: 0.1.4
regards

Please post the link to your municipalitys waste management website so that I can check what data the send to the API.

Google lead me to assume that your waste management is https://www.egst.de/de/abfallabholung/
I just figured out its Altenberge, Aussenbereich, Bauernschaften, ?? which gave me this:

{
	"4c232c12bfcff69c46ab9b618ee064c4": "5f15a1bf658b84a4e8341a22751b8fa2",
	"f_id_kommune": "2593",
	"f_posts_json[]": [
		"a:4:{s:32:\"4c232c12bfcff69c46ab9b618ee064c4\";s:32:\"5f15a1bf658b84a4e8341a22751b8fa2\";s:12:\"f_id_kommune\";s:4:\"2593\";s:12:\"f_posts_json\";a:0:{}s:12:\"f_id_strasse\";s:1:\"0\";}",
		"a:4:{s:32:\"4c232c12bfcff69c46ab9b618ee064c4\";s:32:\"5f15a1bf658b84a4e8341a22751b8fa2\";s:12:\"f_id_kommune\";s:4:\"2593\";s:12:\"f_posts_json\";a:0:{}s:11:\"f_id_bezirk\";s:7:\"492,493\";}",
		"a:5:{s:32:\"4c232c12bfcff69c46ab9b618ee064c4\";s:32:\"5f15a1bf658b84a4e8341a22751b8fa2\";s:12:\"f_id_kommune\";s:4:\"2593\";s:12:\"f_posts_json\";a:1:{i:0;s:171:\"a:4:{s:32:\"4c232c12bfcff69c46ab9b618ee064c4\";s:32:\"5f15a1bf658b84a4e8341a22751b8fa2\";s:12:\"f_id_kommune\";s:4:\"2593\";s:12:\"f_posts_json\";a:0:{}s:12:\"f_id_strasse\";s:1:\"0\";}\";}s:11:\"f_id_bezirk\";s:7:\"492,493\";s:12:\"f_id_strasse\";s:18:\"2593bauernschaften\";}"
	],
	"f_id_bezirk": "492,493",
	"f_id_strasse": "2593bauernschaften",
	"f_id_strasse_hnr": "496"
}

I've never had a layout like this with Hausnummer and a combination of id/name for f_id_strasse and a f_id_strasse_hnr.
That need serious changes on the integartion to get that to work.

Sorry for my very late response.
Yes you googled it right. Is there any chance to get it work?

@dtoenies I have to look into it but the AbfallPlus "API" is a fu***ing mess 🤯
I guess they prepare a new API under the hood because of these f_posts_json[] stuff that was not there when I started with this plugin.
Just be patient, I have too many side projects that need attention 😅

I did not want to rush you and can understand if it takes. Unfortunately, I also do not have time to familiarize myself ;)

Hello guys!
I had this problem too.
Solved it by using f_id_strasse_hnr as street  Setting.
Works well!

@Dielee 🥳 Nice find!

But yes, the AbfallPlus is really a mess....
And thanks for this component! :)

I extended the README with @Dielee finding and close this as its kind of resolved


Use require instead of requireNode

In the early days of Ghost Desktop, I liked to use requireNode to be explicit about the difference between Ember's require and the Node require. However, ember-electron abstracts this perfectly away and there's no real reason to make this more difficult for developers - we can just call it require.

It appears that this was a bad idea - let's close this for now.


Updating integration test script and adding additional logging.

This PR updates the integration-test script to match the vscode one. It also prints all the children processes after running each test suite.
Hopefully, it helps us figure out what exactly is happening here:  https://github.com/microsoft/azuredatastudio/issues/20593
Subprocess tree:

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.01%) to 42.421%

Totals

Change from base Build<PHONE_NUMBER>:
0.01%

Covered Lines:
29301

Relevant Lines:
64273

💛  - Coveralls


ERROR: Could not build wheels for mmhash3, which is required to install pyproject.toml-based projects

Apache Iceberg version
0.6.0 (latest release)
Please describe the bug 🐞
During the installation of pyiceberg, I always get this error:
Building wheels for collected packages: mmhash3
Building wheel for mmhash3 (pyproject.toml) ... error
error: subprocess-exited-with-error
× Building wheel for mmhash3 (pyproject.toml) did not run successfully.
│ exit code: 1
╰─> [11 lines of output]
running bdist_wheel
running build
running build_ext
building 'mmh3' extension
creating build
creating build\temp.win-amd64-cpython-312
creating build\temp.win-amd64-cpython-312\Release
"C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools\VC\Tools\MSVC\14.29.30133\bin\HostX86\x64\cl.exe" /c /nologo /O2 /W3 /GL /DNDEBUG /MD -IC:\path\venv\include -IC:\path\venv\Scripts\include -IC:\path\venv\Scripts\Include "-IC:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools\VC\Tools\MSVC\14.29.30133\include" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.19041.0\ucrt" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.19041.0\shared" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.19041.0\um" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.19041.0\winrt" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.19041.0\cppwinrt" /EHsc /TpMurmurHash3.cpp /Fobuild\temp.win-amd64-cpython-312\Release\MurmurHash3.obj
MurmurHash3.cpp
C:\Users\e549326\AppData\Local\Temp\pip-install-lrlg3_pd\mmhash3_b96a2f2aab1a4eb3b72cc9c8c1915858\MurmurHash3.h(12): fatal error C1083: Cannot open include file: 'Python.h': No such file or directory
error: command 'C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools\VC\Tools\MSVC\14.29.30133\bin\HostX86\x64\cl.exe' failed with exit code 2
[end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
ERROR: Failed building wheel for mmhash3
Failed to build mmhash3
ERROR: Could not build wheels for mmhash3, which is required to install pyproject.toml-based projects

@makssyz Thanks for reaching out here. The main branch should be fixed, since we went back to the original package mmh3 that has Python 3.12 wheels: https://pypi.org/project/mmh3/#files
@MehulBatra is looking into officially supporting 3.12, but there are some packages (looking at you Ray), that are not there yet. Most of it works with 3.12, but so you know.
You can try to install it directly from source:
pip install "git+https://github.com/apache/iceberg-python.git#egg=pyiceberg[s3fs,gcsfs,hive,sql-sqlite,duckdb,pandas]"

This will install mmh3 with the wheel package, but still try to compile the Avro decoder that PyIceberg comes with.

mmh3 even has 3.13 support now :)


Unexpected msg "ERROR - The chosen retrieval type remains outside the supported scope." if retrieval_type = 'default'

line45 should be elif

could be fix via https://github.com/intel/intel-extension-for-transformers/pull/1313
same issue for https://github.com/intel/intel-extension-for-transformers/issues/1315

already fixed in PR


Fix a test failure (org.java_websocket.issues.Issue677Test#testIssue)

The flaky test failure is resolved with my fixes. I run the test 10,000 times, and every time the test passes.
Description

I only added the following code snippet at Line 898 of WebSocketClient.java
try {
Thread.sleep(100);
} catch(InterruptedException e) {}
Related Issue
https://github.com/TooTallNate/Java-WebSocket/issues/1291

Motivation and Context

After the code inspection, I found that the test was failing because some threads could not finish its task. On the other hand, another thread finishes countDownLatch() and starts assertion execution. This solution will wait which lets other threads finish their task before the assertion execution.
How Has This Been Tested?

With my solution, I run the test 10,000 times with the following command, and the test is never failed.
mvn test -Dtest=org.java_websocket.issues.Issue677Test#testIssue
Types of changes

[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 to change)

Checklist:

[X] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.
I used mvn clean install -DskipTests -Dcheckstyle.skip
Then I run the  mvn test -Dtest=org.java_websocket.issues.Issue677Test#testIssue

Need to fix checkstyle of this project. Hence, I submit another pull request, which will preserves the checkstyle


No Boot response from CS in 1.6 Docker?

I've just tried to use https://github.com/voltbras/go-ocpp with the CS docker image. When CP sends BootNotification, it never receives a response. Could you confirm if that is the expected behavior?

This is definitely not intended. Can you confirm whether the CS received the request and also sent the response correctly?
I have never tested this with eduhenke's implementation, but I can confirm the whole flow was working fine with other commercial implementations (tested during OCPP 1.6 plugfest last July).
If you can provide me with some logs/setup info I can look into it.

I'm currently not sure if eduhenke is really functional. I'll retry with a client based on this repo and will double-check. Sorry for the noise.

Closing until I can repro with cp from this repo. Thank you!


The test TestDatabaseConnection is flaky

Sometimes it fails and sometimes passes. I think the problem is with the logs of Kubernetes, which seem not to refresh when a new container is created. For example in https://github.com/kubearchive/kubearchive/actions/runs/10723346226/job/29736419010?pr=378 you can see that after 10 retries with jitter, which take approx 50 seconds, the sink did not try to connect to the database a second time. That looks like the log, for whatever reason, is not refreshed.

I think we could solve the race condition of logs by not upscaling and downscaling our deployments during testing. I think the goal of the test is to check that the retry operation is occuring, in other words we are testing that our usage of the retry library is correct.
When I first encountered this test I tried to unit test the underlying function instead, but it is difficult because of how its designed. The function is mostly glue, with not much logic, so I would try to refactor the test to make it easier to test.

I haven't seen this a while, I think the recent changes we made to it (using Fence) prevented the problem from appearing again. Closing


Create Hello-WorldBR.java

What does the program do ?
Prints a hello world in java
In what programming language it is written?
Java

Thank you for participating  in hacktoberfest ❣ if you liked working on this repo you can share it with friends and star this project for helping others


add new model in power-infer2

Hi, I want to know how to adapt my own model to power-infer2? Do I have to create a sparse model? Can my own dense model be adapted to power-infer2 without revision?

PowerInfer2 does not seem to be open source yet.


feat: cancel pipeline run on SIGINT/SIGTERM

Changes

:gift: Cancel pipeline run on SIGINT/SIGTERM (without this func deploy --remove was uncancellable).

/kind enhancement
feat: cancel pipeline run on SIGINT/SIGTERM

PTAL @zroubalik

/override codecov/patch


defines an alias for Ravindra Kumar Kumawat

In production: http://contributors.rubyonrails.org/contributors/ravindra-kumar-kumawat/commits.

Thanks @fxn :heart:


Fix dependabot codeowner syntax

Seems CODEOWNERS are broken by github, nothing we can do about it

https://github.com/github/feedback/discussions/8959


When emacs stratup first time, it gives a lot off errors.

A lot of errors generated when emacs starts first time from scratch. Some packages missing and maybe problem with archives.
Restart emacs 2-3 times to get rid of all errors. After that it starts normal again.
Unknown cause right now.

custom.el contains stuff that might cause the problem. Move that to emacs.org.


Array binary search

[x] Read all of these instructions carefully. Name things exactly as described.
[x] Do all your work in a public repository called data-structures-and-algorithms.
[x] Do all your work in a public repository called data-structures-and-algorithms.
[x] Your top-level readme should contain a “Table of Contents” navigation to all of your challenges and implementations so far. (Don’t forget to update it!)
[x] This assignment should be completed within the challenges subdirectory of the repository.
[x] On your branch, create a folder named arrayBinarySearch which contains a file called array-binary-search.js
[x] Write a function called BinarySearch which takes in 2 parameters: a sorted array and the search key. Without utilizing any of the built-in methods available to your language, return the index of the array’s element that is equal to the search key, or -1 if the element does not exist.
[x] Copy your photo into an /assets directory in your repo
[x] Give the image file the same name as the branch you are working on
[x] Embed the image in your README.md documentation
[x] Create a pull request from your branch to your master branch
[x] In your open pull request, leave as a comment a checklist of the specifications and tasks above, with the actual steps that you completed checked off
Submitting your complete work to Canvas:
[x] Copy the link to your open pull request and paste it into the corresponding Canvas assignment
[x] Leave a description of how long this assignment took you in the comments box
[x] Add any additional comments you like about your process or any difficulties you may have had with the assignment
[x] Merge your branch into master, and delete your branch (don’t worry, the PR link will still work)

This lab took 3 hours to complete.


Remove old CCDB landing page template

Now that the Consumer Complaint Database landing page is a standard Wagtail page with no special content, we can get rid of all the old templates and assets that powered the old, custom landing page. See GHE/CFGOV/platform/issues/4325 for more details.
@anselmbradford, @flacoman91: I deleted front-end assets for the old tile map kind of willy-nilly. Do you see anything I missed? Or anything I deleted that I shouldn't have?
@higs4281, @willbarton: I think I excised all the back-end bits we don't need any more, but let me know if you spot anything else.

Removals

ComplaintLandingView
Old landing page images
Old landing page template
CSS that styled the old landing page
JS that powered the tile map on the old landing page
JS unit tests that tested the tile map
CCDB_TECHNICAL_ISSUES feature flag

Changes

Re-enabled the CCDB functional tests. Right now they will pass with production data; I still need to add a CCDB landing page to the test database so they'll pass in GitHub actions (see todos below).

How to test this PR

Run all the automated unit and functional tests. Everything should pass.
Fire up the site locally. Everything should still work, especially /data-research/consumer-complaints/.

Notes and todos
One thing still left to do in this PR:

As part of this PR, I want to add a CCDB landing page to the test database so functional tests will pass in Github actions. A couple of other people are working on adding data to that test database now, though. I'm going to wait until their changes are in main so I don't create any conflicts.

And some post-PR todos:

Once this PR is deployed, we can remove the CCDB_TECHNICAL_ISSUES feature flag from the database (just deleting the setting won't delete it from the database)
Add the complaint data outage banner that was part of the old template to the Wagtail banner manager
Move the CCDB search view and tests out of the legacy app, since they aren't legacy any more now that they're no longer combined with the old CCDB landing page stuff.

Checklist

[x] PR has an informative and human-readable title

PR titles are used to generate the change log in releases; good ones make that easier to scan.
Consider prefixing, e.g., "Mega Menu: fix layout bug", or "Docs: Update Docker installation instructions".

[x] Changes are limited to a single goal (no scope creep)
[x] Code follows the standards laid out in the CFPB development guidelines
[x] Future todos are captured in comments and/or tickets
[x] Project documentation has been updated, potentially one or more of:

This repo’s docs (edit the files in the /docs folder) – for basic, close-to-the-code docs on working with this repo
CFGOV/platform wiki on GHE – for internal CFPB developer guidance
CFPB/hubcap wiki on GHE – for internal CFPB design and content guidance

Search the codebase for ccdb-landing-map and there's a transformIgnorePatterns in jest.config.js that looks like it can go --> https://github.com/cfpb/consumerfinance.gov/blob/main/jest.config.js#L31-L33

I think we want to keep the CCDB_TECHNICAL_ISSUES flag. It's how we raise an alert on the complaint search page.

Good call, @higs4281, I forgot the alert in the CCDB interface can be enabled manually by that flag in addition to being turned on automatically by the staleness checks.
The bummer here is that I'd like to make that banner on the CCDB landing page into one that's managed in our normal Wagtail banner manager, which doesn't use feature flags at all. So that means we'd have to turn on two things—the flag and the banner—if we ever run into data issues and want an alert to show up on all CCDB-related pages. That doesn't seem like too big of a pain to me. What do you think? Is there a better way to approach the bannering of CCDB pages (keeping in mind I'd like to keep the new CCDB landing page a standard sub-landing page with no custom code to maintain).

Search the codebase for ccdb-landing-map and there's a transformIgnorePatterns in jest.config.js that looks like it can go --> https://github.com/cfpb/consumerfinance.gov/blob/main/jest.config.js#L31-L33

Thanks, @anselmbradford. Fixed in d253ce3.

Thanks, @anselmbradford. Fixed in d253ce3.

Actually, @anselmbradford, I guess it's fixed in a55551e? Removing transformIgnorePatterns  wholesale caused unit tests to fail to run, so now it's just a blank array. Does that seem right? As is obvious by now, I don't actually understand what that Jest config is doing 😄 .

@niqjohnson
The banner takes a regex argument, so couldn't we apply it to /data-research/consumer-complaints/.+ to capture the landing page and any variation of the downstream search page?

@niqjohnson The banner takes a regex argument, so couldn't we apply it to /data-research/consumer-complaints/.+ to capture the landing page and any variation of the downstream search page? Or does the page have to be a Wagtail page?

@higs4281, yeah, right now banners in the Wagtail banner manager will only show up on CFGOVPage pages. We have an old issue to expand  banner manager banners to any page (GHE/CFGOV/platform/issues/3742), but I don't see that getting picked up any time soon. In the interim I'm fine with having to toggle on two things if we want a stale data alert to show up on all CCDB related pages given how much code complexity that would eliminate—especially since I don't get the sense that this is an alert we need to show often (but I'm not sure if I'm wrong about that assumption). What do you think?

@niqjohnson
I agree the two-banner solution seems acceptable until we get address expanding banners to any page.
Banners have been relatively rare in my experience, and the warnings that the search page currently raises for either stale data or the flag appear right with the search results, which I think is more likely to be noticed than the thin page-topper.

@higs4281, sounds good. I reverted the removal of the CCDB_TECHNICAL_ISSUES flag in b81fc6b.

Actually, @anselmbradford, I guess it's fixed in https://github.com/cfpb/consumerfinance.gov/commit/a55551eb5baf9e60797d1f086453996bb66a9123? Removing transformIgnorePatterns wholesale caused unit tests to fail to run, so now it's just a blank array. Does that seem right? As is obvious by now, I don't actually understand what that Jest config is doing 😄 .

Hmm very weird. I don't understand how the errors shown relate to removing transformIgnorePatterns but ok.


fix: type definition for TweetRetweetedOrLikedByV2Params

X API endpoints for:

https://developer.x.com/en/docs/x-api/tweets/retweets/api-reference/get-tweets-id-retweeted_by
https://developer.x.com/en/docs/x-api/tweets/likes/api-reference/get-tweets-id-liking_users
has max_results and pagination_token fields but they're not typed correctly in the implementation.

Indeed, thank you and sorry for the (really long) delay, i missed it

Published in 1.19.0


WIP: Perform validation of object definitions

Each separate change is separated by commits.
This also adds locking when the discovery information is refreshed to avoid race conditions when concurrency is enabled.
This causes a policy to be non-compliant when the objectDefinition fails
OpenAPI validation to prevent an infinite enforce loop where fields are
ignored by the Kubernetes API when the object is created/updated and
in the next loop, the ConfigurationPolicy sees that the object from the
API doesn't match what's in the policy and enforces again.
Relates:
https://github.com/stolostron/backlog/issues/24973
https://bugzilla.redhat.com/show_bug.cgi?id=2116528

@JustinKuli could you please double check where I placed the locking? Note that I chose not to use defer to unlock the lock to reduce the time that the lock is taken up and avoiding potential mistakes where a method that has a read lock calls a method with a read/write lock.

This is marked WIP since I need to add this validation on create as well and also fix the CI.


[WIP] Inference base class

This creates a NeuralInference abstract base class taking up much of the argument checking of the children.
Warning - changes across the board Help me merge this quickly to prevent blocking/merge conflicts.
As of now:

feedback welcome on the comments XXX raised in NeuralInference
sbi_posterior substantially edited for better documentation
input checks should be at the level of NeuralInference's __init__. We can implement now consensus in #89 or post-PR. Same for naming of parameters/observations, #100.

Pending

instantiation of the neural_posterior could be done at the parent if we adequately dispatch based on child class name on the PotentialFunctionProvider (awaiting @jan-matthis for final say on Pyro vs. slice_np) /and/ if we either split SRE from AALR or pass the classifier loss. Could the loss go with the classifier_nn? (note to future self).
entering / exiting train mode in Posterior is confusing - either fix here or separate issue.
refactor directory structure
Further refactoring of the inference classes themselves should be the object of separate PRs.

There a couple of open questions, but we will be able to solve them in the meeting tmr, I hope.

Tests are passing thanks to your bug fix. and we all approved, so ready to merge I would say!

Allright, there goes the merge. Note that all tasks marked as pending above have been indeed deferred to further, separate PRs. Let's have these after upcoming pervasive renames and input checking PRs!


Reactivate stylistic rules for TypeScript

ESLint Stylistics TypeScript still rely on typescript-eslint@^7 which in turn requires ESLint 8.x, which conflicts with our requirement of ESLint 9.x, hence we deactivated it in https://github.com/neostandard/neostandard/pull/36 to fix #35
When https://github.com/eslint-stylistic/eslint-stylistic/issues/414 has been fixed we can reintroduce them without getting peer dependency errors again (and as such get predictable outcomes)
Maybe we could fork ESLint Stylistics TypeScript until they officially release with typescript 8.x support and release it as @neostandard/eslint-stylistic-ts or something, to get support earlier
Originally posted by @voxpelli in https://github.com/neostandard/neostandard/issues/35#issuecomment-2156625238

Instead of forming we could of course also simply vendor it, that could be even better / simpler probably, but may be harder to keep in sync with upstream (unless we do git-subtree magic, which I happen to be quite proficient in 😎)

Instead of forming we could of course also simply vendor it, that could be even better / simpler probably, but may be harder to keep in sync with upstream (unless we do git-subtree magic, which I happen to be quite proficient in 😎)

It depends on the bandwidth the maintainers have to maintain it. But I think avoiding to put more maintenance work is wise: upstream will at some point in time officially support the upcoming typescript-eslint version.


Covscan defects

I've fixed multiple defects reported by covscan as a part of https://github.com/FreeRDP/FreeRDP/pull/4813. However, there are still some remaining defects which I am unsure about their solution and thus I am not going to propose any fixes for them. Some of them look like false-positives, but some of them seem to be worth looking at, e.g. the one with USE_AFTER_FREE. Here is the list of important defects on top of the mentioned pull request: scan-results-imp.err.

Btw there is also a list containing much more issues, which are not marked as important: scan-results.err. There is also a lot of interesting defects, e.g. NO_EFFECT, DEADCODE. If I find some time I will propose a fix for some of those also.

@ondrejholy We've fixed a lot of warnings (and bugs) in the last weeks, so I assume we can close this one?

The scan based on the current master (commit d3c1db1746b99c05d515de626d2c515e49debfdd) revealed more issues than the previous one. There is still the USE_AFTER_FREE defect, which would be nice to fix, but I am not sure how. I don't see anything else very important. See scan-results-imp.err and scan-results.err for details.

@ondrejholy looks like there were some socket leaks handling error cases of tcp_connect.
The USE_AFTER_FREE is currently harmless, but @hardening is changing the return there to a seat ID to avoid the confusion (both, developer and compiler)

Thanks that you took look at those defects. The seat id defect is not still fixed, see my comment on https://github.com/FreeRDP/FreeRDP/pull/4970. I can confirm that some socket leaks disappeared. If you are interested see updated scan-results-imp.err and scan-results.err.

Ok, the wayland related stuff is merged and we're currently fixing some remaining scanbuild warnings.
closing this for now.


(chore) update packages to resolve security vulnerabilities

Updating packages to help resolve the numerous security vulnerabilities reported by npm i

Thank you very much for your contribution. However your updates seem to drop support for older node versions.
@adrai Maybe it is time to drop support for Node < 6 ?

@nanov this is strange...

@nanov just picked this: https://github.com/adrai/node-eventstore/commit/320034a7d55a17b72f68307db9755c0cb2683fc4

@adrai I think it was a honest mistake, he probably is maintaining a fork for his own needs.


SublimeLinter-eslint not working when eslint es installed locally

As suggested by @roadhump in issue 23 of SublimeLinter-eslint (https://github.com/roadhump/SublimeLinter-eslint/issues/23) I open this issue here.
I just noticed, that when eslint is also installed locally the following error is reported:
SublimeLinter: eslint: ods.ui.form.js ['D:\\MyDev\\ljs_app\\trunk\\periscope\\build\\node_modules\\.bin\\eslint', '--format=compact', '--stdin']
SublimeLinter: ERROR: could not launch ['D:\\MyDev\\ljs_app\\trunk\\periscope\\build\\node_modules\\.bin\\eslint', '--format=compact', '--stdin']
SublimeLinter: reason: [WinError 193] %1 is not a valid Win32 application

I'm running ST3 Build 3065 on a Windows 7 x64 system and when eslint is only installed globally, the linter plugin works as expected. I'm using eslint 0.14.0.
I also noticed that (other than the jscs and jshint) plugins eslint is not shown when loading ST.
I just wanted to mention it but it actually should not be related to this problem as it is also not shown when eslint is only installed globally and the plugin is working:
SublimeLinter: jscs version query: C:\Users\doberkofler.LBITS\AppData\Roaming\npm\jscs.cmd --version
SublimeLinter: jscs version: 1.10.0
SublimeLinter: jscs: (>= 1.0.10) satisfied by 1.10.0
SublimeLinter: jscs activated: C:\Users\doberkofler.LBITS\AppData\Roaming\npm\jscs.cmd
SublimeLinter: jshint version query: C:\Users\doberkofler.LBITS\AppData\Roaming\npm\jshint.cmd --version
SublimeLinter: jshint version: 2.6.0
SublimeLinter: jshint: (>= 2.5.0) satisfied by 2.6.0
SublimeLinter: jshint activated: C:\Users\doberkofler.LBITS\AppData\Roaming\npm\jshint.cmd
SublimeLinter: found existing HTML syntax, version 3
SublimeLinter: found existing Rails syntax, version 1

I'm having a hard time replicating this. So you have eslint installed locally but not globally?

I actually have it installed globally and locally. Until now I did not even know that SublimeLinter3
is able to access a local installation.
The error happens when there is a local installation. If I remove the local installation everything works as expected.

I figured out what the problem is, there is no .cmd at the end of the command. When python searches D:\\MyDev\\ljs_app\\trunk\\periscope\\build\\node_modules\\.bin it finds the first file that satisfies eslint but that isn't actually a windows executable. the actual file it wanted was the second one, eslint.cmd
I'll try to resolve this but don't really use node or eslint so give me a bit, unless you would like to contribute of course!

I'm happy to help, if I can be of any assistance!
Looking at the python code, I would guess that the problem is in the function find_local_cmd_path in lint/node_linter.py. Am I right ?

I'm sure there is better ways to code this, but generally speaking, the following 3 lines of code in the function find_local_cmd_path in the file lint/node_linter.py after the line binary = path.join(node_modules_bin, cmd) would solve the problem:
        import sys
        if sys.platform.startswith('win'):
            binary += '.cmd'

On the road, so may not work but there is sublime.platform() should return 'windows'

+1

it's ugly as hell and you should definitely use sublime.platform() but the code I posted does actually solve the problem, if you need a quick fix.

This has been released and should be visible in 30 minutes.
Thanks!

I actually have the same problem -eslint installed both locally and globally-, but I'm on OSX (10.9 and 10.10). ST3 build 3073. The linter works again if I move ./node_modules/.bin/eslint
SublimeLinter: json activated: <builtin>
reloading Packages/User/SublimeLinter.sublime-settings
SublimeLinter: eslint: index.jsx ['/Users/myUserName/path/to/myProject/node_modules/.bin/eslint', '--format=compact', '--stdin']
SublimeLinter: eslint output:
module.js:338
    throw err;
          ^
Error: Cannot find module 'concat-stream'
    at Function.Module._resolveFilename (module.js:336:15)
    at Function.Module._load (module.js:278:25)
    at Module.require (module.js:365:17)
    at require (module.js:384:17)
    at Object.<anonymous> (/Users/myUserName/path/to/myProject/node_modules/.bin/eslint:2:14)
    at Module._compile (module.js:460:26)
    at Object.Module._extensions..js (module.js:478:10)
    at Module.load (module.js:355:32)
    at Function.Module._load (module.js:310:12)
    at Function.Module.runMain (module.js:501:10)

Actually this doesn't look like the same problem. Yours is working and loaded into sublime. The problem seems to exist in your version of Eslint. The error in the console is a JavaScript error, for which SL doesn't have any JavaScript code. So that error is being produced by Eslint.