tests: kernel: sched: schedule_api: increase SLICE_SIZE

tests: kernel: sched: schedule_api: increase SLICE_SIZE
Increase SLICE_SIZE in order to pass test with slow frequency:
Since merge of #29296, test was failed on some STM32 boards.
I found that boards with 'high' CPU frequency test was passed, and boards with 'low' CPU frequency test was failed.
And finally on the same board (nucleo_f746zg) when CPU freq is below 83MHz test is failed
and when CPU freq is above 84MHZ test is passed.
After some more investigation I figure out that increasing SLICE_SIZE allow to pass the test,
and I found a direct correlation between CPU frequency and SLICE_SIZE required to pass the test.
Thus SLICE_SIZE = 600 allow to pass tests with 32MHZ frequency (The lowest frequency used within STM32 boards in Zephyr).
I don't have the root cause, but maybe as said @andrewboie in #29296

in case the thread creation itself causes overhead which could affect the test

Update: Keep previous SLICE_SIZE = 200 for other boards than STM32, as buildkite detected issue on several platforms like mps2_an521, native_posix_64, nrf52_bsim ...

Update: Keep previous SLICE_SIZE = 200 for other boards than STM32, as buildkite detected issue on several platforms like mps2_an521, native_posix_64, nrf52_bsim ...

^^ @andyross @andrewboie
Could you please review ? would be nice if it could be merged before v2.5.0 merge windows close

^^ @andyross @andrewboie
Could you please review ? would be nice if it could be merged before v2.5.0 merge windows close

@ABOSTM would you mind look/test this pr https://github.com/zephyrproject-rtos/zephyr/pull/30916 ?

@ABOSTM would you mind look/test this pr https://github.com/zephyrproject-rtos/zephyr/pull/30916 ?

@ceolin yes PR #30916 fixes issues on STM32 boards. Thanks.
(sorry, I am not able to review it: I don't know zephyr kernel's inside)

@ceolin yes PR #30916 fixes issues on STM32 boards. Thanks.
(sorry, I am not able to review it: I don't know zephyr kernel's inside)

@ceolin yes PR #30916 fixes issues on STM32 boards. Thanks.
(sorry, I am not able to review it: I don't know zephyr kernel's inside)

Thank you for testing it ! Really appreciated.

@ceolin yes PR #30916 fixes issues on STM32 boards. Thanks.
(sorry, I am not able to review it: I don't know zephyr kernel's inside)

Thank you for testing it ! Really appreciated.

Fixed thanks to https://github.com/zephyrproject-rtos/zephyr/pull/30916 , which is now merged

Fixed thanks to https://github.com/zephyrproject-rtos/zephyr/pull/30916 , which is now merged


Fix vertical centering of iconmessage component in some modals

Summary
This wasn't specific enough, so was shifting some iconmessages incorrectly.
Ticket Link
Related Pull Requests

Has server changes (please link here)
Has mobile changes (please link here)

Screenshots
before:

after:

Release Note

None

Successfully triggered e2e testing!
https://git.internal.mattermost.com/qa/cypress-ui-automation/-/pipelines/219045


Library design/intent/future

This library currently defines all its own types and a bunch of specialized functions, completely independent from the rest of the spec-based web/dom libraries. Do we want to keep it as it is, or should we remove the stuff that duplicates work done elsewhere and just have it implement the Context2D interface as per https://www.w3.org/TR/2dcontext?
I'm fine with either, but if it's the latter, I'll be tempted to make a purescript-web-context2d library that is just the minimal thing, and then base this library on top of that, so at least it can share types with the rest of the web ecosystem.

The latter option sounds preferable in that it seems like it would be possible to keep the API of this library fairly constant, which I like because it is used in the book. Perhaps this library could even become a thin veneer over the web-canvas library and move back to contrib.

Ok, sounds like we have a plan then. I'll work something up and open a PR.


[WIP FEATURE] Linux Snap Install

Let's coordinate tasks needed to support Snap installation on Ubuntu (and other distros)
All changes to support this feature will go into snap branch, so please target PRs accordingly. Once it's all working alongside the traditional Windows/Linux install mechanism, we'll merge snap into main.
Some initial details (from @frenchwr), in response to this question: "Would it be possible for you to give a high level description of what the Snap installation will actually do? e.g. Will it invoke install.sh, or simply extract some bundled set of artifacts (like python virtual env.) from a previous installation?"

I am not invoking install.sh directly. That was my original aim but it just got too messy. I am, however, using setup.py and >requirements.txt to install the necessary python packages.
The snap distributes model_setup.py as an "app" within the snap that can be invoked with something like openvino-ai-plugins->gimp.model-setup. The models are installed to GIMP_OPENVINO_MODELS_PATH , if defined.
The ultimate aim is to integrate the openvino-ai-plugins-gimp snap with the gimp snap so that a user can just snap install gimp >and have the OpenVINO AI plugin support out-of-the-box.
Along these lines, I've designed the openvino-ai-plugins-gimp snap so that when a user runs gimp it will automatically invoke >complete_install.setup_python_weights so that gimp_openvino_config.json will get generated (and written to >GIMP_OPENVINO_CONFIG_PATH) on each run. In this way we check for device support (GPU, NPU, etc) at runtime. I realize this will >also copy the super resolution and semseg models each run, but since the models are relatively small it should not be a big penalty.

TODO List (This will grow):

Device lists  (i.e. CPU, GPU, NPU) should be populated at runtime (via openvino.core.available_devices) instead of at install.sh time.

Are you all open to updating the logic here for determining the Python interpreter? Some Linux distros have stopped shipping a Python interpreter named python in favor of python3. If you're open to it I can submit a PR against snap for testing.

Are you all open to updating the logic here for determining the Python interpreter? Some Linux distros have stopped shipping a Python interpreter named python in favor of python3. If you're open to it I can submit a PR against snap for testing.

Yes, I think so. Looking back at that logic, I'm actually a little bit confused why we do that (get the path, and then append the right executable name to it).. I would think that sys.executable may just give us what we want? Perhaps I'm missing something..
Anyway, yes, definitely open to any improvements here!

I would think that sys.executable may just give us what we want? Perhaps I'm missing something..
nope, not missing anything. we should be using sys.executable. this will ensure we are pointing to the same python interpreter that was used in the virtual environment.

Are you all open to updating the logic here for determining the Python interpreter? Some Linux distros have stopped shipping a Python interpreter named python in favor of python3. If you're open to it I can submit a PR against snap for testing.

Hi @frenchwr  - do you want to create the PR for this one? if not I can do it. thanks!

Hi @frenchwr - do you want to create the PR for this one? if not I can do it. thanks!

@gblong1 You can go for it! If you tag me in the PR I'm happy to test on my side.

@frenchwr PR created : https://github.com/intel/openvino-ai-plugins-gimp/pull/155

@frenchwr PR created : #155

I reviewed & merged into snap branch, @frenchwr you can test it from there if you'd like. Thanks!

A few other nice-to-haves if you're open to it:

Can we replace these lines and instead just import with something like the following? As it is written now model_setup.py can only be run from the root directory of this repo.

from  gimpopenvino.plugins.openvino_utils.tools.model_manager import ModelManger

Could we either wrap this in a try-except or (even better if we can get away with it) store these files as executable in the repo?
Are we sure this line is needed? I believe typing is built in to recent versions of libraries and this caused conflicts when it was installed in my snap, so I ended up needing to remove it.

I'm happy to help make these changes and test, but just wanted to get your thoughts first in case I'm missing something.

Also I can create a separate issue for this if you prefer, but whenever I run stable diffusion on a NPU (balanced or power efficiency mode) I'm seeing errors like the following:
File "/snap/gimp/x14/usr/lib/x86_64-linux-gnu/gimp/2.99/plug-ins/openvino_utils/tools/openvino_common/models_ov/stable_diffusion_engine.py", line 157, in load_model
    with open(os.path.join(model, f"{model_name}.blob"), "rb") as f:
         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
FileNotFoundError: [Errno 2] No such file or directory: '/home/ubuntu/openvino-ai-plugins-gimp/weights/stable-diffusion-ov/stable-diffusion-1.5/square_int8/unet_int8.blob'

I don't see those blob files after downloading the models with model_setup.py. Is there some extra step(s) to convert them to a .blob format? I've tested with square_int8 and also square_lcm. Performance mode (with GPU only) runs perfectly.

I'm happy to help make these changes and test, but just wanted to get your thoughts first in case I'm missing something.

Please feel free to make the changes and submit a PR, thanks!

I don't see those blob files after downloading the models with model_setup.py. Is there some extra step(s) to convert them to a .blob format? I've tested with square_int8 and also square_lcm. Performance mode (with GPU only) runs perfectly.

After the model download completes, the NPU .blobs should get created. For example, see step 3 of the standalone script README.
If that is not happening, let me know. Which platform are you running on?

After the model download completes, the NPU .blobs should get created. For example, see step 3 of the standalone script README.

Aha - ok all good now. I didn't realize the NPU runtime libs were needed at the model download stage.
I assume the models are compiled for the NPU at this stage because the compilation is somewhat slow?

Please feel free to make the changes and submit a PR, thanks!

I'll work on a PR tomorrow. This will get me really close to having the snap functioning without any hacks in the packaging.

I assume the models are compiled for the NPU at this stage because the compilation is somewhat slow?

Correct. We don't want to have the user waiting for the models to compile the first time they run a specific feature. So we compile them at model download time, since they are already waiting for the models to download.

@RyanMetcalfeInt8 @gblong1 I just opened a PR with the changes I mentioned yesterday: https://github.com/intel/openvino-ai-plugins-gimp/pull/156 Let me know what you think.

Thanks! We'll test it out and provide any feedback.

Hello! The snap packaging work is very close to being done on our (Canonical) side. I was hoping to share some details today for how you could test and provide feedback, but unfortunately it's not quite ready.
I'll have something to share in the new year. Happy holidays!


[dask] Segfault in prediction with DaskDMatrix + base_margin (Workaround).

We observed segfault in our CI environment https://xgboost-ci.net/blue/organizations/jenkins/xgboost/detail/master/921/pipeline with test test_predict_with_meta.
The failure hasn't been reproduced in any other environment yet.  And even to reproduce it in CI requires a very specific configuration.  It's a memory read error in MetaInfo::SetInfo when copying data from numpy into XGBoost using std::copy.  The issue is so bizarre that a slight change of build like from Rel to RelWithDebugInfo then it's no longer reproducible.  Also downgrading distributed to somewhere before https://github.com/dask/distributed/pull/4967 seems to be a solution.  To get some more weird results, replacing the std::copy with a customized loop or creating a temporary double buffer in between the copy somehow can pass the test.  Lastly copying the data explicitly in Python before passing it down to XGBoost can work around the issue too.
I will try to make a data copy for base margin to unblock the CI.  This issue is for tracking the debugging progress.

Might be related: https://xgboost-ci.net/blue/organizations/jenkins/xgboost/detail/PR-7130/5/pipeline

I believe this is a bug in GCC 7.5.


dependency cleanup

Per https://github.com/erikrose/parsimonious/issues/231, provide a way to avoid the regex package dependency and then update parsimonious to the latest.
At the same time remove six.py since it's not needed in the latest upstream

unblocked


Change google login/signup logo

We should change to Google's new branding.
See: https://design.google.com/articles/evolving-the-google-identity/
The new logo should be a monochrome version of this:

If relevant for other platforms, the icon used on Windows can be found here: https://github.com/toggl/toggldesktop/blob/master/src/ui/windows/TogglDesktop/TogglDesktop/Resources/icon-google.png


Add Satoshi Nakamoto's white paper to doc directory

Andreas made a good case here https://github.com/bitcoin/bitcoin/pull/7443 for adding the original white paper to the repo. Thoughts?

Good idea.

I don't think whitepapers belong in a repo. They are not source code, they are not part of the software, and frankly this almost-religious cult of personality is unhealthy. The whitepaper is the origin of Bitcoin, not its future. That being said, I would be all for a link in the root README, because the whitepaper is basically "Bitcoin 101".

I'd say its useful to include the whitepaper.
The argument that its not source code doesn't hold for immutable objects. Just like logos etc are in git, so can a document like the whitepaper.
While I do support the argument from Andreas about copyright, my personal reasoning is that everyone doing a clone of this bitcoin node should have access to the paper. Bitcoin as a conceptual protocol is still the best described by that paper. Which is sad in other ways (I'm working on a git repo with documentation to solve that issue).

Just for reference, there is a nice markdown version here: https://github.com/karask/shatoshi-paper/blob/master/markdown/bitcoin.md

@jojva Thanks for the link to the markdown paper. With regards to the paper not being code, you are correct, however I believe including it would serve two important purposes, namely:

It resolves the licensing issue of the original white paper, returning it to the code base where it was once included by Satoshi. This is the issue that @aantonop was most concerned about. He was able to establish the provenance and original license of the paper to satisfy his publisher, however others in the future would be well served by having a clear source and and license for the file.

I believe the intention behind Bitcoin Classic is not merely a single code change which bumps block size up to 2MB, but a reaffirmation of the vision set out by Satoshi in the original white paper. Including it will help to distinguish the project much the way the code of conduct[1] attempts to shape the tone of discourse within the project.

[1] https://github.com/bitcoinclassic/bitcoinclassic/blob/master/CONTRIBUTING.md#codeofconduct

I agree. https://github.com/bitcoinclassic/bitcoinclassic/pull/96

Closing, because done.


Remove obsolete FnMut conversion

Currently we convert the FnOnce closure to a FnMut closure. This is not
needed and there is no comment explaining why this is done. I suspect
this might have been required originally because the api or compiler was
different.

I found the original PR that added these https://github.com/crossbeam-rs/crossbeam-utils/pull/47 .
Even there it does not look like it's needed and no explanation is given.


Add basic github actions CI

Hmm. Do these only run if the PR's from the same origin initially? I'll try that to see...


Fix async invocation in Python 3

Description
Removed the encoding of the json message for SNS notification when sys.version is Python 3.
See https://github.com/Miserlou/Zappa/pull/1331
This issue and similar pull request have been open for more than three years. Please accept and merge them into Zappa.

GitHub Issues
https://github.com/Miserlou/Zappa/issues/1323

I had the same issue and confirm this solution works.

Coverage remained the same at 73.527% when pulling 798323a52915d95b9a1066a5011e19b245b5cfe4 on suriya:fix-sns-task-1 into b5b80cf096227e4eb0feb1de5ff8097711d53c88 on zappa:master.

Just hit this error today, cant wait for the merge!

I was able to build this into a wheel and test it out! Once I got it installed properly I was able to get my function to call SNS
@task_sns
def longrunner(delay, msg):
    sleep(float(delay))
    return f"testing task: {msg}"


Analyzer publicly is behind internal repo (pub publish?)

The latest analyzer package via pub still uses PrintWriter, while the latest version internally uses StringBuffer - it's hard to create code targeting some parts of the analyzer while we're out of sync.
Can be solved via pub publish perhaps?
It looks like we are synced to 60e6faa7c3357ab519fc88b3f51f39b5419eb257 internally.

We continue making breaking changes to analyzer.
So, I would not like to publish an official 0.29.0 yet.
Would publishing 0.29.0-alpha.1 suffice for your goals?
@bwilkerson

The other possibility is to revert this change until we're closer to being ready to publish.
I'm certainly fine with publishing an alpha version, though, if that works for @matanlurey.

If you can publish even a non-production version it will mean I can at least dev against what we have internally, otherwise I'll have to stop github development until it catches up :-/

OK, I published 0.29.0-alpha.0.


ANR

Broadcast of Intent { act=com.google.android.c2dm.intent.RECEIVE flg=0x11000010 pkg=com.addcn.android.house591 cmp=com.addcn.android.house591/com.google.firebase.iid.FirebaseInstanceIdReceiver (has extras) }
com.google.firebase.iid.FirebaseInstanceIdReceiver

@LiuDongCai this is not enough information to debug.  Are you getting this from Crashlytics or something?  Is this a new issue?  If so, does it correspond to an SDK update?

@samtstern
"main" prio=5 tid=1 Native
| group="main" sCount=1 dsCount=0 flags=1 obj=0x72f69730 self=0x7532ac3a00
| sysTid=17865 nice=0 cgrp=default sched=0/0 handle=0x75374189b0
| state=S schedstat=(<PHONE_NUMBER> 229007884 1067 ) utm=162 stm=26 core=1 HZ=100
| stack=0x7fea58c000-0x7fea58e000 stackSize=8MB
| held mutexes=
#00  pc<PHONE_NUMBER>068e18  /system/lib64/libc.so (__epoll_pwait+8)
#01  pc<PHONE_NUMBER>01fa98  /system/lib64/libc.so (epoll_pwait+48)
#02  pc<PHONE_NUMBER>015c1c  /system/lib64/libutils.so (_ZN7android6Looper9pollInnerEi+144)
#03  pc<PHONE_NUMBER>015b04  /system/lib64/libutils.so (_ZN7android6Looper8pollOnceEiPiS1_PPv+108)
#04  pc<PHONE_NUMBER>111de4  /system/lib64/libandroid_runtime.so (???)
#05  pc<PHONE_NUMBER>1e605c  /system/framework/arm64/boot-framework.oat (Java_android_os_MessageQueue_nativePollOnce__JI+140)
at android.os.MessageQueue.nativePollOnce (Native method)
at android.os.MessageQueue.next (MessageQueue.java:375)
at android.os.Looper.loop (Looper.java:225)
at android.app.ActivityThread.main (ActivityThread.java:6572)
at java.lang.reflect.Method.invoke (Native method)
at com.android.internal.os.Zygote$MethodAndArgsCaller.run (Zygote.java:240)
at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:767)
This is anr in Google play. It just happen at Android 8.0.
And my Firebase Version:
implementation 'com.google.firebase:firebase-core:16.0.1'
implementation 'com.google.firebase:firebase-messaging:17.1.0'
implementation 'com.google.firebase:firebase-perf:16.0.0'

@LiuDongCai while I do believe this is a real issue for you, it's not possible to begin fixing it unless we can reproduce the issue as well.
See this page for more information on how to file an actionable bug report:
https://stackoverflow.com/help/mcve

You are literally the 4th result on the first page of search results for "Broadcast of Intent { act=com.google.android.c2dm.intent.RECEIVE flg=0x11000010 ANR". It would be good of you to take on a bit of responsibility and investigate.
If you read the news group thread at search result 3 it looks like Vitalii may have already debugged it for you. https://groups.google.com/d/msg/firebase-talk/5mo7-z8gqFA/RugthckUCgAJ. I cannot overstate my disappointment with such apathy.

@nmr8acme sorry that you're disappointed.  It certainly wasn't "apathy" that led me to close this issue, it was a lack of the information we need to debug the issue.  A copy-pasted dump from a crash report just isn't enough.
Your link to the google groups post (which I hadn't seen before) contains much more information and is very helpful!  I will use this to file a more detailed bug report with the authors of the InstanceID SDK and see if they can fix it.
Looking at the source for FirebaseInstanceIdReceiver I can see that the potentially problematic code has been changed a few times since Vitali deobfuscated it, so it's possible a fix is already in. I  will report back.

Requiring a repro is a rather high bar to set for what looks like a tricky bug. Thank you for pursuing it. FWIW I am experiencing this bug on firebase-iid 16.0.0. I'll try updating, which, to complain more, would be substantially easier if InstanceIDListenerService hadn't been deprecated.

Here are some initial thoughts I got from the engineer who wrote the code involved here (slightly paraphrased to remove internal terminology).
It seems that we're aware of the general issue and we're using a number of techniques to try and avoid this, but there are still cases where the broadcast doesn't finish fast enough and we see ANRs.  We are continuing to investigate.

An FCM message broadcast comes in via the FirebaseInstanceIdReceiver which routes it to FirebaseMessagingService (and/or FirebaseInstanceIdService if it's IID related).
If the app is running on a device <O or is targeting <O we just use startService, they get a background service, virtually no chance of an ANR as the receiver will always finish quickly.
[...]
For normal priority messages, we keep the broadcast going (via goAsync), and bind to their service. This gives 60s for their service to run before the broadcast ANRs. As a fail safe we also set a 9s timer to finish the broadcast if their code is still running to avoid ANRs, at this stage there's no guarantee Android won't just kill their app even though their code is still running - they could use a foreground service, or schedule the work for later if they wanted to.
The [recent changes mean] that for high priority messages, where [the system gives] the app a short whitelist that allows them to take wake locks, hit the network, start services, etc. we use startService, similar to what we used to do which should greatly reduce the rate of ANRs. If this fails for whatever reason we fall back to using the bind approach above.
This is much more important here as for high priority messages we use a foreground broadcast that triggers an ANR in the receiver after 10s (which is why we set the timeout to 9s) - but worse than that can cause system issues as foreground broadcasts are expected to be fast.
Even with that change though I still hear some reports of ANRs, which I haven't been able to diagnose.

@nmr8acme our reccomendations right now:

Update your dependencies to the latest version if possible (partial fixes went into firebase-iid version 17.0.2).
Look for any operations your app does in response to high-priority messages that could take more than 10 seconds and consider adding a shorter timeout to avoid the operations being killed by the system.
Look out for any possibly slow operations in your Applications onCreate method, which could cause an ANR if your app takes too long to respond to a message.

same thing to me
Broadcast of Intent { act=com.google.android.c2dm.intent.RECEIVE flg=0x11000010 pkg=com.tencent.qqlivei18n cmp=com.tencent.qqlivei18n/com.google.firebase.iid.FirebaseInstanceIdReceiver (has extras) }
"main" prio=5 tid=1 Native
| group="main" sCount=1 dsCount=0 flags=1 obj=0x722f2840 self=0xa5544000
| sysTid=5909 nice=0 cgrp=default sched=0/0 handle=0xa9cbb4b8
| state=S schedstat=( 0 0 0 ) utm=21 stm=21 core=3 HZ=100
| stack=0xbe356000-0xbe358000 stackSize=8MB
| held mutexes=
#00  pc<PHONE_NUMBER>049974  /system/lib/libc.so (__epoll_pwait+20)
#01  pc<PHONE_NUMBER>01ba15  /system/lib/libc.so (epoll_pwait+60)
#02  pc<PHONE_NUMBER>01ba45  /system/lib/libc.so (epoll_wait+12)
#03  pc<PHONE_NUMBER>01002d  /system/lib/libutils.so (android::Looper::pollInner(int)+120)
#04  pc<PHONE_NUMBER>00ff1d  /system/lib/libutils.so (android::Looper::pollOnce(int, int*, int*, void**)+32)
#05  pc<PHONE_NUMBER>0ba081  /system/lib/libandroid_runtime.so (android::NativeMessageQueue::pollOnce(_JNIEnv*, _jobject*, int)+24)
#06  pc<PHONE_NUMBER>176265  /system/framework/arm/boot-framework.oat (Java_android_os_MessageQueue_nativePollOnce__JI+92)
at android.os.MessageQueue.nativePollOnce (Native method)
at android.os.MessageQueue.next (MessageQueue.java:325)
at android.os.Looper.loop (Looper.java:142)
at android.app.ActivityThread.main (ActivityThread.java:7000)
at java.lang.reflect.Method.invoke (Native method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:441)
at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1408)

@samtstern i dont understand
is necesario put this library ?
com.google.firebase:firebase-iid:18.0.0
i alway have used these librarys
com.google.firebase:firebase-messaging:18.0.0
com.google.firebase:firebase-core:16.0.9
so i need put the com.google.firebase:firebase-iid:18.0.0 to resolve this problem?

@samtstern i have some operations that could take more than 10 seconds but i use AsyncTask to execute those operations even i tried with WorkManager and the result is the same i got a lot of ARNs
this problem happens even with this library com.google.android.gms.ads
i got this similar ARN
Motorola Moto X Play (lux), Android 7.1

"main" tid=1 WaitingForGc
"main" prio=5 tid=1 WaitingForGcToComplete
  | group="main" sCount=1 dsCount=0 obj=0x73ffd700 self=0xa5504400
  | sysTid=25274 nice=-10 cgrp=default sched=0/0 handle=0xa8207534
  | state=S schedstat=(<PHONE_NUMBER>94<PHONE_NUMBER>5 444182 ) utm=29001 stm=4754 core=0 HZ=100
  | stack=0xbe37d000-0xbe37f000 stackSize=8MB
  | held mutexes=
  #00  pc<PHONE_NUMBER>0174d4  /system/lib/libc.so (syscall+28)
  #01  pc<PHONE_NUMBER>0b6fc9  /system/lib/libart.so (_ZN3art17ConditionVariable16WaitHoldingLocksEPNS_6ThreadE+92)
  #02  pc<PHONE_NUMBER>186839  /system/lib/libart.so (_ZN3art2gc4Heap25WaitForGcToCompleteLockedENS0_7GcCauseEPNS_6ThreadE+236)
  #03  pc<PHONE_NUMBER>192b79  /system/lib/libart.so (_ZN3art2gc4Heap19WaitForGcToCompleteENS0_7GcCauseEPNS_6ThreadE+172)
  #04  pc<PHONE_NUMBER>18ce8d  /system/lib/libart.so (_ZN3art2gc4Heap22AllocateInternalWithGcEPNS_6ThreadENS0_13AllocatorTypeEbjPjS5_S5_PPNS_6mirror5ClassE+84)
  #05  pc<PHONE_NUMBER>127b8d  /system/lib/libart.so (_ZN3art2gc4Heap24AllocObjectWithAllocatorILb1ELb1ENS_6mirror21SetStringCountVisitorEEEPNS3_6ObjectEPNS_6ThreadEPNS3_5ClassEjNS0_13AllocatorTypeERKT1_+2360)
  #06  pc<PHONE_NUMBER>29c9cd  /system/lib/libart.so (_ZN3art6mirror6String14AllocFromUtf16EPNS_6ThreadEiPKt+84)
  #07  pc<PHONE_NUMBER>27cdff  /system/lib/libart.so (_ZN3art3JNI9NewStringEP7_JNIEnvPKti+430)
  #08  pc<PHONE_NUMBER>09334d  /system/lib/libandroid_runtime.so (???)
  #09  pc<PHONE_NUMBER>c03db5  /data/dalvik-cache/arm/system<EMAIL_ADDRESS>(Java_android_os_Parcel_nativeReadString__J+88)
  at android.os.Parcel.nativeReadString (Native method)
  at android.os.Parcel.readString (Parcel.java:1738)
  at android.content.pm.ApplicationInfo.<init> (ApplicationInfo.java:1019)
  at android.content.pm.ApplicationInfo.<init> (ApplicationInfo.java)
  at android.content.pm.ApplicationInfo$1.createFromParcel (ApplicationInfo.java:996)
  at android.content.pm.ApplicationInfo$1.createFromParcel (ApplicationInfo.java:995)
  at android.content.pm.PackageInfo.<init> (PackageInfo.java:352)
  at android.content.pm.PackageInfo.<init> (PackageInfo.java)
  at android.content.pm.PackageInfo$1.createFromParcel (PackageInfo.java:332)
  at android.content.pm.PackageInfo$1.createFromParcel (PackageInfo.java:331)
  at android.content.pm.IPackageManager$Stub$Proxy.getPackageInfo (IPackageManager.java:2493)
  at android.app.ApplicationPackageManager.getPackageInfoAsUser (ApplicationPackageManager.java:139)
  at android.app.ApplicationPackageManager.getPackageInfo (ApplicationPackageManager.java:132)
  at com.google.android.gms.common.GooglePlayServicesUtilLight.zza (unavailable:34)
  at com.google.android.gms.common.GooglePlayServicesUtilLight.isGooglePlayServicesAvailable (unavailable:22)
  at com.google.android.gms.common.GoogleApiAvailabilityLight.isGooglePlayServicesAvailable (unavailable:5)
  at com.google.android.gms.internal.ads.zzazt.zzc (unavailable:67)
  at com.google.android.gms.internal.ads.zzys.zzd (unavailable:35)
  at com.google.android.gms.internal.ads.zzabb.zza (unavailable:100)
  at com.google.android.gms.ads.BaseAdView.loadAd (unavailable:15)
  at com.google.android.gms.ads.AdView.loadAd (unavailable:18)
  at schan.main.ChatActivity.loadAds (ChatActivity.java:614)
  at schan.main.ChatActivity.onCreate (ChatActivity.java:551)
  at android.app.Activity.performCreate (Activity.java:6687)
  at android.app.Instrumentation.callActivityOnCreate (Instrumentation.java:1140)
  at android.app.ActivityThread.performLaunchActivity (ActivityThread.java:2631)
  at android.app.ActivityThread.handleLaunchActivity (ActivityThread.java:2743)
  at android.app.ActivityThread.-wrap12 (ActivityThread.java)
  at android.app.ActivityThread$H.handleMessage (ActivityThread.java:1490)
  at android.os.Handler.dispatchMessage (Handler.java:102)
  at android.os.Looper.loop (Looper.java:154)
  at android.app.ActivityThread.main (ActivityThread.java:6165)
  at java.lang.reflect.Method.invoke! (Native method)
  at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run (ZygoteInit.java:888)
  at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:778)
"Jit thread pool worker thread 0" tid=2 Native
"FinalizerWatchdogDaemon" tid=5 Sleeping
"FinalizerDaemon" tid=6 WaitingForGc
"ReferenceQueueDaemon" tid=7 Waiting
"Binder:25274_1" tid=8 Native
"Binder:25274_2" tid=9 Native
"Profile Saver" tid=10 Native
"FirebaseInstanceId" tid=12 Waiting
"pool-2-thread-1" tid=13 Waiting
"MessengerIpcClient" tid=16 TimedWaiting
"GoogleApiHandler" tid=22 Native
"Chrome_IOThread" tid=23 Native
"PlatformServiceBridgeHandlerThread" tid=24 Native
"GAC_Executor[0]" tid=26 Waiting
"ConnectivityManager" tid=27 Native
"CleanupReference" tid=28 Waiting
"AudioThread" tid=29 Native
"Chrome_InProcRendererThread" tid=30 Native
"Chrome_InProcGpuThread" tid=31 Native
"GAC_Executor[1]" tid=33 Waiting
"Binder:25274_3" tid=34 Native
"LooperProvider" tid=38 Native
"AdWorker(NG) #1" tid=45 WaitingForGc
"RenderThread" tid=48 Native
"JavaBridge" tid=58 Native
"Signal Catcher" tid=3 Runnable
"HeapTaskDaemon" tid=4 WaitingForGc

"main" tid=1 Native
"main" prio=5 tid=1 Native
| group="main" sCount=1 dsCount=0 flags=1 obj=0x72ec1858 self=0xaee44000
| sysTid=10258 nice=0 cgrp=default sched=0/0 handle=0xb35b74b8
| state=S schedstat=( 0 0 0 ) utm=20 stm=78 core=0 HZ=100
| stack=0xbe281000-0xbe283000 stackSize=8MB
| held mutexes=
#00  pc<PHONE_NUMBER>049974  /system/lib/libc.so (__epoll_pwait+20)
#01  pc<PHONE_NUMBER>01ba15  /system/lib/libc.so (epoll_pwait+60)
#02  pc<PHONE_NUMBER>01ba45  /system/lib/libc.so (epoll_wait+12)
#03  pc<PHONE_NUMBER>01002d  /system/lib/libutils.so (android::Looper::pollInner(int)+120)
#04  pc<PHONE_NUMBER>00ff1d  /system/lib/libutils.so (android::Looper::pollOnce(int, int*, int*, void**)+32)
#05  pc<PHONE_NUMBER>0ba081  /system/lib/libandroid_runtime.so (android::NativeMessageQueue::pollOnce(_JNIEnv*, _jobject*, int)+24)
#06  pc<PHONE_NUMBER>176265  /system/framework/arm/boot-framework.oat (Java_android_os_MessageQueue_nativePollOnce__JI+92)
at android.os.MessageQueue.nativePollOnce (Native method)
at android.os.MessageQueue.next (MessageQueue.java:325)
at android.os.Looper.loop (Looper.java:142)
at android.app.ActivityThread.main (ActivityThread.java:7000)
at java.lang.reflect.Method.invoke (Native method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:441)
at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1408)

I am also facing this issue. 95% of the ANRs that are getting reported on Play Console are referring to this issue.
`"main" tid=1 Blocked
"main" prio=5 tid=1 Blocked
| group="main" sCount=1 dsCount=0 flags=1 obj=0x743a7660 self=0xe7fc9000
| sysTid=5740 nice=0 cgrp=default sched=0/0 handle=0xec9f1494
| state=S schedstat=( 792615932 491011320 1059 ) utm=14 stm=65 core=5 HZ=100
| stack=0xff077000-0xff079000 stackSize=8MB
| held mutexes=
at android.app.QueuedWork.processPendingWork (QueuedWork.java:245)

waiting to lock <0x092d20d0> (a java.lang.Object) held by thread 13
at android.app.QueuedWork.waitToFinish (QueuedWork.java:172)
at android.app.ActivityThread.handleServiceArgs (ActivityThread.java:3700)
at android.app.ActivityThread.access$1600 (ActivityThread.java:202)
at android.app.ActivityThread$H.handleMessage (ActivityThread.java:1696)
at android.os.Handler.dispatchMessage (Handler.java:107)
at android.os.Looper.loop (Looper.java:198)
at android.app.ActivityThread.main (ActivityThread.java:6729)
at java.lang.reflect.Method.invoke (Native method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:493)
at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:858)`

All these ANRs show that the main thread is either waiting or blocked.
Is there a status update on this issue?

@samtstern hi, I have the same issue.
ANR because of Broadcast of Intent { act=com.google.android.c2dm.intent.RECEIVE in FirebaseInstanceIdReceiver
"main" prio=5 tid=1 Native
| group="main" sCount=1 dsCount=0 flags=1 obj=0x73faf638 self=0xe8c77000
| sysTid=26244 nice=0 cgrp=default sched=0/0 handle=0xed1084bc
| state=S schedstat=( 718806623<PHONE_NUMBER> 1307 ) utm=34 stm=37 core=3 HZ=100
| stack=0xff0dc000-0xff0de000 stackSize=8MB
| held mutexes=
#00  pc<PHONE_NUMBER>018ebc  /system/lib/libc.so (syscall+28)
#01  pc<PHONE_NUMBER>0b380d  /system/lib/libart.so (_ZN3art17ConditionVariable16WaitHoldingLocksEPNS_6ThreadE+88)
#02  pc<PHONE_NUMBER>3bfa27  /system/lib/libart.so (_ZN3artL12GoToRunnableEPNS_6ThreadE+306)
#03  pc<PHONE_NUMBER>3bf8c5  /system/lib/libart.so (_ZN3art12JniMethodEndEjPNS_6ThreadE+8)
#04  pc<PHONE_NUMBER>81bda1  /system/framework/arm/boot-framework.oat (Java_android_os_BinderProxy_transactNative__ILandroid_os_Parcel_2Landroid_os_Parcel_2I+144)
at android.os.BinderProxy.transactNative (BinderProxy.java)
at android.os.BinderProxy.transact (BinderProxy.java:761)
at android.app.IActivityManager$Stub$Proxy.addPackageDependency (IActivityManager.java:6867)
at android.app.LoadedApk.createOrUpdateClassLoaderLocked (LoadedApk.java:613)
at android.app.LoadedApk.getClassLoader (LoadedApk.java:711)

locked <0x0fe1b24c> (a android.app.LoadedApk)
at android.app.ContextImpl.getClassLoader (ContextImpl.java:304)
at android.webkit.WebViewFactory.getProviderClass (WebViewFactory.java:409)
at android.webkit.WebViewFactory.getProvider (WebViewFactory.java:211)
locked <0x0a344295> (a java.lang.Object)
at android.webkit.WebSettings.getDefaultUserAgent (WebSettings.java:1259)
at com.mopub.network.Networking.getUserAgent (Networking.java:175)
at com.mopub.network.Networking.getRequestQueue (Networking.java:89)
locked <0x08c7efaa> (a java.lang.Class<com.mopub.network.Networking>)
at com.mopub.common.MoPub.initializeSdk (MoPub.java:189)
at com.magicv.airbrush.advertmediation.AdClientManager.initMoPub (AdClientManager.java:64)
at com.magicv.airbrush.advertmediation.AdClientManager.initializeSdk (AdClientManager.java:41)
at com.magicv.airbrush.common.AirBrushApplication.initAlbumAd (AirBrushApplication.java:274)
at com.magicv.airbrush.common.AirBrushApplication.initAds (AirBrushApplication.java:265)
at com.magicv.airbrush.common.AirBrushApplication.initialize (AirBrushApplication.java:253)
at com.magicv.airbrush.common.AirBrushApplication.onCreate (AirBrushApplication.java:136)
at android.app.Instrumentation.callApplicationOnCreate (Instrumentation.java:1126)
at android.app.ActivityThread.handleBindApplication (ActivityThread.java:6062)
at android.app.ActivityThread.-wrap1 (ActivityThread.java)
at android.app.ActivityThread$H.handleMessage (ActivityThread.java:1764)
at android.os.Handler.dispatchMessage (Handler.java:105)
at android.os.Looper.loop (Looper.java:164)
at android.app.ActivityThread.main (ActivityThread.java:6942)
at java.lang.reflect.Method.invoke (Method.java)
at com.android.internal.os.Zygote$MethodAndArgsCaller.run (Zygote.java:327)
at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1374)

Remarks：the resources that reference firebase are as follows：
classpath 'com.google.gms:google-services:4.0.1'
//firebase remoteconfig
implementation 'com.google.firebase:firebase-core:16.0.4'
implementation 'com.google.firebase:firebase-config:16.0.1'
implementation 'com.google.firebase:firebase-messaging:18.0.0'
implementation 'com.google.firebase:firebase-ads:16.0.1'
compileSdkVersion: 28,
buildToolsVersion: "28.0.3",
targetSdkVersion : 26,

hi Everyone,
I have also the same issue.
ANR because of Broadcast of Intent { act=com.google.android.c2dm.intent.RECEIVE in FirebaseInstanceIdReceiver
"main" prio=5 tid=1 Waiting
| group="main" sCount=1 dsCount=0 obj=0x751a5000 self=0xb8d3a630
| sysTid=29578 nice=-4 cgrp=apps sched=0/0 handle=0xb6fb6ec8
| state=S schedstat=(<PHONE_NUMBER> 710641375 2251 ) utm=96 stm=30 core=0 HZ=100
| stack=0xbe31d000-0xbe31f000 stackSize=8MB
| held mutexes=
at java.lang.Object.wait! (Native method)

waiting on <0x13be0a86> (a java.lang.Object)
at java.lang.Thread.parkFor (Thread.java:1220)
locked <0x13be0a86> (a java.lang.Object)
at sun.misc.Unsafe.park (Unsafe.java:299)
at java.util.concurrent.locks.LockSupport.park (LockSupport.java:157)
at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt (AbstractQueuedSynchronizer.java:813)
at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly (AbstractQueuedSynchronizer.java:973)
at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly (AbstractQueuedSynchronizer.java:1281)
at java.util.concurrent.CountDownLatch.await (CountDownLatch.java:202)
at android.app.SharedPreferencesImpl$EditorImpl$1.run (SharedPreferencesImpl.java:363)
at android.app.QueuedWork.waitToFinish (QueuedWork.java:88)
at android.app.ActivityThread.handleServiceArgs (ActivityThread.java:3272)
at android.app.ActivityThread.access$2200 (ActivityThread.java:168)
at android.app.ActivityThread$H.handleMessage (ActivityThread.java:1491)
at android.os.Handler.dispatchMessage (Handler.java:102)
at android.os.Looper.loop (Looper.java:135)
at android.app.ActivityThread.main (ActivityThread.java:5753)
at java.lang.reflect.Method.invoke! (Native method)
at java.lang.reflect.Method.invoke (Method.java:372)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run (ZygoteInit.java:1405)
at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1200)

//firebase remoteconfig
implementation 'com.google.firebase:firebase-messaging:19.0.1'
implementation 'com.google.firebase:firebase-core:17.0.0'
implementation 'com.google.firebase:firebase-appindexing:19.0.0'
implementation 'com.google.firebase:firebase-config:18.0.0'
    compileSdkVersion = 28
    minSdkVersion = 17
    targetSdkVersion = 28

Please help me on it if anyone of you are having solution of this.
Thanks in advance.

Hi, we also got many report on play console with same error.
We already updated to firebase 17.0.1
I also profiled our app start cpu call and no operation blocking more than 10 second.
Any other advice what we should do about it ?

@samtstern
hi , i think the anr it doesn't matter with firebase. broadcastReceiver anr time is application oncreate  time consuming and onRecive time consuming . in some Performance is poor phone, application oncreate is Very time consuming. but i think OrderedBroadcast is have anr time , and non-serialized broadcasts don't have anr time. can firebase send non-serialized broadcasts to our ?

Facing the same issue after upgrade FCM to 17.+ and targetSDKVertion to 28

Is there any fix for this? Got the same ANR in Android 9 only

Any solutions? Lots of same ANRs in my google play console ANR list
firebase version 17.2.1

@google-oss-bot please have a look on this thread.
Thanks

have same problem with firebase 18.2.0

any update?

@samtstern

triggers an ANR in the receiver after 10s (which is why we set the timeout to 9s)

Correct me if i am wrong, the 9s timer is started in FirebaseInstanceIdReceiver#onReceive(before binding FirebaseMessagingService), but the 10s ANR timer is started before Application#onCreate(which is called before FirebaseInstanceIdReceiver#onReceive). So if Application#onCreate consumes more than 1 second, the 9s timer may not be triggered before the 10s ANR timeout.

Our app is also facing a lot of ANRs from this

is there any update?

Migrate from Fabric ?

Reason: Broadcast of Intent { act=com.google.android.c2dm.intent.RECEIVE flg=0x11000010 com.google.firebase.iid.FirebaseInstanceIdReceiver (has extras) }
Our app is  facing a ANR issue like this.what is the solution?

still encounter this ANR frequently.  we suspected that finishReceiver is not invoke correctly, but not find the root cause yet.  And another doubt maybe the app startup cost if broadcast when the app is not alive

Maybe the QueueWork blocked by heavy work?

@RijoshEnfin  @smilewaver Have you tried upgrading your firebase-messaging to the latest version:
com.google.firebase:firebase-messaging:20.1.7 ?
They said the ANR issues were fixed.

BTW, beside the ANR log that everybody else has already shared, here is an extra log I got regarding this ANR:
"ActivityManager" prio=5 tid=12 Native   | group="main" sCount=1 dsCount=0 flags=1 obj=0x12cc7548 self=0x75f9f4d800   | sysTid=5921 nice=-2 cgrp=default sched=0/0 handle=0x75da0ba4f0   | state=S schedstat=(<PHONE_NUMBER>928<PHONE_NUMBER>396 6169400 ) utm=237405 stm=298619 core=6 HZ=100   | stack=0x75d9fb7000-0x75d9fb9000 stackSize=1041KB   | held mutexes=   kernel: (couldn't read /proc/self/task/5921/stack)   native: #00 pc<PHONE_NUMBER>071448  /system/lib64/libc.so (recvfrom+8)   native: #01 pc<PHONE_NUMBER>001c54  /system/lib64/libdebuggerd_client.so (debuggerd_trigger_dump(int, DebuggerdDumpType, unsigned int, android::base::unique_fd_impl<android::base::DefaultCloser>)+1252)   native: #02 pc<PHONE_NUMBER>002868  /system/lib64/libdebuggerd_client.so (dump_backtrace_to_file_timeout(int, DebuggerdDumpType, int, int)+104)   native: #03 pc<PHONE_NUMBER>11e760  /system/lib64/libandroid_runtime.so (android::dumpTraces(_JNIEnv*, int, _jstring*, int, DebuggerdDumpType)+124)   native: #04 pc<PHONE_NUMBER>11dff8  /system/lib64/libandroid_runtime.so (android::android_os_Debug_dumpJavaBacktraceToFileTimeout(_JNIEnv*, _jobject*, int, _jstring*, int)+28)   at android.os.Debug.dumpJavaBacktraceToFileTimeout(Native method)   at com.android.server.am.ActivityManagerService.dumpJavaTracesTombstoned(ActivityManagerService.java:8292)   at com.android.server.am.ActivityManagerService.dumpStackTraces(ActivityManagerService.java:8382)   at com.android.server.am.ActivityManagerService.dumpStackTraces(ActivityManagerService.java:8169)   at com.android.server.am.AppErrors.appNotResponding(AppErrors.java:1216)   at com.android.server.am.BroadcastQueue$AppNotResponding.run(BroadcastQueue.java:318)   at android.os.Handler.handleCallback(Handler.java:873)   at android.os.Handler.dispatchMessage(Handler.java:99)   at android.os.Looper.loop(Looper.java:216)   at android.os.HandlerThread.run(HandlerThread.java:65)   at com.android.server.ServiceThread.run(ServiceThread.java:44)

i am using 20.1.5 version of firebase-messaging and still encountering the same issue. This anr is frequently reported on play console.

i am using 20.1.5 version of firebase-messaging and still encountering the same issue. This anr is frequently reported on play console.

Hi @zainForAndro , how about 20.1.7 ?

@samtstern & Support team,
Did you get any fix for the above reported issue, seems keep increasing the cases?
#need-attention
Thanks

My earlier comments on this bug are, unfortunately, the best I will be able to offer.  If anyone is able to find a minimal reproducible example for this there may be more to discuss:
https://stackoverflow.com/help/minimal-reproducible-example

@samtstern
Please find the details log if this is helpful for now, It is difficult to reproduce. But this is being logged in Google play console.
"main" prio=5 tid=1 Native
| group="main" sCount=1 dsCount=0 obj=0x741a22a0 self=0xb7a48590
| sysTid=29991 nice=0 cgrp=default sched=0/0 handle=0xb6f62b34
| state=S schedstat=( 0 0 0 ) utm=9 stm=35 core=0 HZ=100
| stack=0xbe6ac000-0xbe6ae000 stackSize=8MB
| held mutexes=
#00  pc<PHONE_NUMBER>042908  /system/lib/libc.so (__ioctl+8)
#01  pc<PHONE_NUMBER>04966d  /system/lib/libc.so (ioctl+14)
#02  pc<PHONE_NUMBER>01ea21  /system/lib/libbinder.so (android::IPCThreadState::talkWithDriver(bool)+132)
#03  pc<PHONE_NUMBER>01f087  /system/lib/libbinder.so (android::IPCThreadState::waitForResponse(android::Parcel*, int*)+38)
#04  pc<PHONE_NUMBER>01f23d  /system/lib/libbinder.so (android::IPCThreadState::transact(int, unsigned int, android::Parcel const&, android::Parcel*, unsigned int)+124)
#05  pc<PHONE_NUMBER>01a1cf  /system/lib/libbinder.so (android::BpBinder::transact(unsigned int, android::Parcel const&, android::Parcel*, unsigned int)+30)
#06  pc<PHONE_NUMBER>088e21  /system/lib/libandroid_runtime.so (???)
#07  pc<PHONE_NUMBER>d93f01  /data/dalvik-cache/arm/system<EMAIL_ADDRESS>(Java_android_os_BinderProxy_transactNative__ILandroid_os_Parcel_2Landroid_os_Parcel_2I+140)
at android.os.BinderProxy.transactNative (BinderProxy.java)
at android.os.BinderProxy.transact (BinderProxy.java:503)
at android.content.pm.IPackageManager$Stub$Proxy.getApplicationInfo (IPackageManager.java:2319)
at android.app.ApplicationPackageManager.getApplicationInfo (ApplicationPackageManager.java:292)
at com.google.android.gms.common.wrappers.PackageManagerWrapper.getApplicationInfo (PackageManagerWrapper.java:4)
at com.google.android.gms.internal.measurement.zzx.zza (zzx.java:232)
at com.google.android.gms.internal.measurement.zzx.zzi (zzx.java:185)

locked <0x05669729> (a java.lang.Class<com.google.android.gms.internal.measurement.zzx>)
at com.google.android.gms.internal.measurement.zzx.zzb (zzx.java:205)
at com.google.firebase.analytics.FirebaseAnalytics.getScionFrontendApiImplementation (FirebaseAnalytics.java:98)
at java.lang.reflect.Method.invoke! (Native method)
at com.google.android.gms.measurement.AppMeasurement.zzb (AppMeasurement.java:30)
at com.google.android.gms.measurement.AppMeasurement.zza (AppMeasurement.java:17)
locked <0x01730aae> (a java.lang.Class<com.google.android.gms.measurement.AppMeasurement>)
at com.google.firebase.analytics.connector.AnalyticsConnectorImpl.getInstance (AnalyticsConnectorImpl.java:20)
locked <0x0bd0c04f> (a java.lang.Class<com.google.firebase.analytics.connector.AnalyticsConnectorImpl>)
at com.google.firebase.analytics.connector.internal.zzc.create (zzc.java:6)
at com.google.firebase.components.ComponentRuntime.lambda$new$0 (ComponentRuntime.java:69)
at com.google.firebase.components.ComponentRuntime$$Lambda$1.get (ComponentRuntime.java)
at com.google.firebase.components.Lazy.get (Lazy.java:53)
locked <0x0e9423dc> (a com.google.firebase.components.Lazy)
at com.google.firebase.components.ComponentRuntime.initializeEagerComponents (ComponentRuntime.java:158)
at com.google.firebase.FirebaseApp.initializeAllApis (FirebaseApp.java:563)
at com.google.firebase.FirebaseApp.initializeApp (FirebaseApp.java:304)
at com.google.firebase.FirebaseApp.initializeApp (FirebaseApp.java:268)
at com.google.firebase.FirebaseApp.initializeApp (FirebaseApp.java:253)
locked <0x00287ce5> (a java.lang.Object)
at com.google.firebase.provider.FirebaseInitProvider.onCreate (FirebaseInitProvider.java:51)
at android.content.ContentProvider.attachInfo (ContentProvider.java:1748)
at android.content.ContentProvider.attachInfo (ContentProvider.java:1723)
at com.google.firebase.provider.FirebaseInitProvider.attachInfo (FirebaseInitProvider.java:45)
at android.app.ActivityThread.installProvider (ActivityThread.java:5174)
at android.app.ActivityThread.installContentProviders (ActivityThread.java:4769)
at android.app.ActivityThread.handleBindApplication (ActivityThread.java:4709)
at android.app.ActivityThread.-wrap1 (ActivityThread.java)
at android.app.ActivityThread$H.handleMessage (ActivityThread.java:1415)
at android.os.Handler.dispatchMessage (Handler.java:102)
at android.os.Looper.loop (Looper.java:148)
at android.app.ActivityThread.main (ActivityThread.java:5443)
at java.lang.reflect.Method.invoke! (Native method)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run (ZygoteInit.java:728)
at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:618)

@tuancoltech
we have try com.google.firebase:firebase-messaging:20.1.7 in a small release. which has no effect.
and we guess that one possible scene is, AMS call client to deal the broadcast, and the client maybe blocked by any time cost op in main thread. when the block pass, AMS already assume the client ANR.

@LiuDongCai while I do believe this is a real issue for you, it's not possible to begin fixing it unless we can reproduce the issue as well.

I'm glad you're not working for Boeing.

We meet the same thing in the project and update it to 20.1.7 is useless. This problem seems to have existed for at least a year, do you have the plan to solve it?

Same issue

+1

Same issue,do you have the plan to solve it?

@RoyJing I am using  implementation 'com.google.firebase:firebase-messaging:20.2.3'
and it is fixed there check release notes.

@RoyJing I am using implementation 'com.google.firebase:firebase-messaging:20.2.3'
and it is fixed there check release notes.

Hi，bro. Did you see after the app was released that the GooglePlay console didn't have this problem?
And can you tell me about your app's DAU? Thank you very much!

My app use a lot of high priority fcm notification with only payload.I wonder if this happens when user click the notification to open the app or when user receive the notification then the app is process is started?
About 70% ANR are from the FirebaseInstanceIdReceiver.

I've tried to change the fcm notification priority from high to normal, all the ANRS caused by FirebaseInstanceIdReceiver disapeared, except one which has a stacktrace that I think could be resolved. But the notification recieve rate dropped about 10%.

I've also tried to change the fcm notification priority from high to normal, the ANRS caused by FirebaseInstanceIdReceiver decreased a lot. But the notification receive. rate dropped about 30%, which has a huge affect to our app...

@RoyJing I am using implementation 'com.google.firebase:firebase-messaging:20.2.3'
and it is fixed there check release notes.

Hi, @mwshubham, I check the release note and  it says "Fixed an issue that caused an app to crash when a user tapped on a received notification." I'm aware that it solves the crash instead of ANR issues. I just want to confirm if the updates will help to reduce ANR.
Also, I read the comments from @samtstern which says the devices with >26 will trigger more ANRs instead of <26'devices. But as I see in the play console, many ANRs are reported every day from Android 6 devices with SDK 23.  And it's been a year since last suggestion. Do we have any updates on this issue?
Looking forward to your reply :)

I checked the play console. We didnt get the ANR from the last two releases. @Bradmrhong Looks like this is fixed in the latest versions.

We are still getting this error even after

I checked the play console. We didnt get the ANR from the last two releases. @Bradmrhong Looks like this is fixed in the latest versions.

It is still coming in the latest version "com.google.firebase:firebase-messaging:20.2.4"
Anyone else still getting this ANR? The Play Console is filled with this ANR. It is affecting our play store listing.

Same as @arsundram. We have already updated to 20.2.4 but still getting this kind of ANRs at the same high rate.
I checked again in StackOverflow and someone says need to update play-service too? Any more ideas about this?

ANR +1
too many .

I updated to com.google.firebase:firebase-messaging:20.2.4 but the ANRs continue.
Broadcast of Intent { act=com.google.android.c2dm.intent.RECEIVE flg=0x11000010 pkg=xxx cmp=xxx/com.google.firebase.iid.FirebaseInstanceIdReceiver (has extras) }

in com.google.firebase.iid.FirebaseInstanceIdReceiver

I was also getting the same ANR(as it mentioned in early comments).
Memory Leak can be one reason for emitting this com.google.firebase.iid.firebaseinstanceidreceiver ANR.
So you can verify on Android profiler for memory leak, If memory leak issue is fixed then this ANR automatically come DOWN.
Hope this help to all you guys.

ir

@pratyesh Interesting.
Can you please explain in more detail how memory leak can lead to com.google.firebase.iid.firebaseinstanceidreceiver ANR?
Thanks.

This issue is closed and is not asigned to anyone. I think that the best is continue comments in this issue:
https://github.com/firebase/firebase-android-sdk/issues/2014
Thanks 👍

@tuancoltech
I had identified in my case the context of Activity/Fragment was being stored in somewhere within ViewModel or some Sdk CallBack(i.e. Google In App Update) is registered with the current context and it never been cleared from memory till to kill the app.
So same way if you guys start looking on your Memory Leak issue and after fixing this then surly your ANR will get reduce.
Thanks.


Dissertation: "Authors & Editors" tab should be renamed to "Authors & Supervisors"

Describe the improvement
When editing / viewing a "dissertation" publication, the contributors tab is called "Authors & Editors" instead of "Authors & Supervisors".
Expected behavior
When editing / viewing a "dissertation" publication, the contributors tab is called "Authors & Supervisors".

@mietcls those are the roles in use for a dissertation, there's the author of the thesis and then one or more supervisors/promoters

Affiliations (relevant to people, institutions, ...)
People & Organisations (a bit more specific but long, very dummy proof)

Will be replaced by https://github.com/ugent-library/biblio-backend/issues/670 for now, after discussing this with the test group. Affiliations is the shortest, and leaves space for projects (controversial but it might be an option).


[Question]: Can I use query engine with batch?

Question Validation

[X] I have searched both the documentation and discord for an answer.

Question
Hi, thank you for your nice work. I left the question to ask the availability of batch generation for query engine.
My code is like below. I hope I can find the answer.
Thank you :)

query_engine = index.as_query_engine(similarity_top_k=3)
for nl in tqdm(test_nl['query'], desc="Processing Queries"):
response = query_engine.query(f"""Find the relavant relation with the given plain text question. Question: {nl}""")

Thank you for commenting. I also want to ask that using batch inference with the ReActAgent.
My code is like below. I hope I can find the answer.
Thank you :)

entity_engine = entity_index.as_query_engine(similarity_top_k=3)
kg_engine = kg_index.as_query_engine(similarity_top_k=3)
query_engine_tools = [
QueryEngineTool(
query_engine=entity_engine,
metadata=ToolMetadata(
name="entity_list",
description=(
"Provides information about enities in the Knowledge Graph. "
"Use an entity which observed in plain text question as input to the tool."
),
),
),
QueryEngineTool(
query_engine=kg_engine,
metadata=ToolMetadata(
name="kg_data",
description=(
"Provides information about Knowledge Graph structure formed by triple."
"Use a triplet which extracted from detailed plain text question as input to the tool. And find the answer entity as an answer of the plain text question. The answer can be multiple. Finish your chain-of-thought in at most 10 steps"
),
),
),
]
agent = ReActAgent.from_tools(
query_engine_tools,
llm=llm,
verbose=True,
)
answer_list = []
all_response = []
for nl in tqdm(test_nl['query'], desc="Processing Queries"):
response = agent.chat(f"""Question: {nl}""")
print(response.response.split('\n')[0])
answer_list.append(response.response.split('\n')[0])
all_response.append(response.response)

@dosu
My model code is like below.
llm = HuggingFaceLLM(
model_name="meta-llama/Meta-Llama-3-8B-Instruct",
model_kwargs={
"torch_dtype": torch.bfloat16,  # comment this line and uncomment below to use 4bit
# "quantization_config": quantization_config
},
generate_kwargs={
"do_sample": False,
"temperature": 0,
"top_k": 1,
},
tokenizer_name="meta-llama/Meta-Llama-3-8B-Instruct",
stopping_ids=stopping_ids,
)
entity_docs = SimpleDirectoryReader(
input_files=["ent_descript_candy.txt"]
).load_data()
kg_docs = SimpleDirectoryReader(
input_files=["data/train_kg_txt_v2.txt"]
).load_data()
embed_model = HuggingFaceEmbedding(model_name="BAAI/bge-small-en-v1.5")
bge embedding model
Settings.embed_model = embed_model
Llama-3-8B-Instruct model
Settings.llm = llm


Device class initialization fails

the script below freezes and nothing happens. I could not Ctrl-C the shell so I had to completely close it.
In [1]: import intel_realsense_devices
   ...:
   ...: print(f"current version of the library is {intel_realsense_devices.__version__}")
   ...: from intel_realsense_devices.device import Device
   ...:
   ...: conf_filename = r"C:\Users\AR-VR lab W1\Documents\Valentyn\custom_python_libraries\instrumentation\intel-realse
   ...: nse-depth-camera\L515_config.yaml"
   ...: device = Device(config_filename=conf_filename, h5py_filename="YOUR H5PY/HDPY FILE NAME")
   ...: device.init()
current version of the library is 0.post90.dev0+gb8ea2c5

with config file
name: 'augemented reality setup'
model: 'Intel RealSense L515'
serial_number: "f1231322"
serial_number2: "139522074713"
imgs_to_collect: 100

@AbdelRahmanNasser20, We need to introduce logging to the codes to try to understand what is going on. I am going to add few examples of logging and how to use it. I would like if you can take a lead and work on the rest of the codes and introduce logging capabilities where it is necessary.
Here is a good reference for logging: https://realpython.com/python-logging/
see driver class as an example. if you test the driver class by itself you would see that there is a new file created in the temporary directory that is constantly updated with information from this process. Use notepad++ and enable dynamic update (https://superuser.com/questions/274961/how-to-automatically-reload-modified-files-in-notepad) to see most recent changes in the log file
To find temp directory:
From the Start menu, open the Run dialog box or you can Press the "Window + R" key to open the RUN window. Type "%temp%" and click on the OK button. Note: And, you can also find the temporary files in the "Temp" folder by typing the "temp" command or by typing the "C:\Windows\Temp" path in the Run window.

Here is the code example and the error I get. @AbdelRahmanNasser20
C:\Users\AR-VR lab W1>ipython3
Python 3.8.8rc1 (tags/v3.8.8rc1:dfd7d68, Feb 17 2021, 11:01:21) [MSC v.1928 64 bit (AMD64)]
Type 'copyright', 'credits' or 'license' for more information
IPython 8.0.1 -- An enhanced Interactive Python. Type '?' for help.

In [1]: config_filename = r"C:\Users\AR-VR lab W1\Documents\Valentyn\custom_python_libraries\instrumentation\devices\co
   ...: nfig_D455_215122256135.yaml"

In [2]: import intel_realsense_devices
   ...:
   ...: print(f"current version of the library is {intel_realsense_devices.__version__}")
   ...: from intel_realsense_devices.device import Device
   ...:
   ...: device = Device(
   ...:     config_filename=config_filename, h5py_filename="YOUR H5PY/HDPY FILE NAME"
   ...: )
   ...: device.init()
current version of the library is 0.post100+g4e48381
---------------------------------------------------------------------------
RuntimeError                              Traceback (most recent call last)
Input In [2], in <module>
      4 from intel_realsense_devices.device import Device
      6 device = Device(
      7     config_filename=config_filename, h5py_filename="YOUR H5PY/HDPY FILE NAME"
      8 )
----> 9 device.init()

File c:\users\ar-vr lab w1\documents\valentyn\custom_python_libraries\intel-realsense-devices\intel_realsense_devices\device.py:63, in Device.init(self)
     61 from intel_realsense_devices.driver import Driver
     62 self.driver = Driver()
---> 63 self.driver.init(self.serial_number)
     65 # if the config dict is empty
     66 if "imgs_to_collect" not in self.config_dict.keys():

File c:\users\ar-vr lab w1\documents\valentyn\custom_python_libraries\intel-realsense-devices\intel_realsense_devices\driver.py:62, in Driver.init(self, serial_number)
     60 self.print_device_info()
     61 self.configure() # calls method to configure the device
---> 62 self.start()

File c:\users\ar-vr lab w1\documents\valentyn\custom_python_libraries\intel-realsense-devices\intel_realsense_devices\driver.py:112, in Driver.start(self)
    108 """
    109 starts the pipelines
    110 """
    111 self.profile[ACCEL] = self.pipeline[ACCEL].start(self.conf[ACCEL])
--> 112 self.profile[GYRO] = self.pipeline[GYRO].start(self.conf[GYRO])
    113 self.profile[IMAGE] = self.pipeline[IMAGE].start(self.conf[IMAGE])

RuntimeError: Couldn't resolve requests


Add RSS support

Looking at the blog infrastructure for evidence.dev (It'd be amazing if you could point to it being generated by evidence.dev), there aren't any rss feeds referenced in the page metadata. Considering your audience, I suspect not everyone is particularly inclined to give out an email.

@Denubis That's a great idea.
Our website is an evidence project (except the docs, but we'll migrate them eventually).
I am going to update this to track adding RSS support to evidence in general, rather than just our blog.

I think this would be very useful.
I can give it a try, but am not familiar with the stack. Is there an hook/callback to get the parsed markdown? Getting the list of files and their frontmatter annotations would make it trivial to generate the feed.

You may find the files here instructive: https://github.com/evidence-dev/evidence/tree/next/packages/lib/preprocess/src/frontmatter


MultiApi EventHub

(message created by the CI based on PR content)

Codecov Report

Merging #4492 into master will decrease coverage by 3.91%.
The diff coverage is 64.58%.

@@            Coverage Diff             @@
##           master    #4492      +/-   ##
==========================================
- Coverage   53.38%   49.47%   -3.92%
==========================================
  Files       10464     6280    -4184
  Lines      219586   176153   -43433
==========================================
- Hits       117229    87144   -30085
+ Misses     102357    89009   -13348

Impacted Files
Coverage Δ

...e/mgmt/eventhub/v2017_04_01/models/eventhub_py3.py
100% <ø> (ø)

...e/mgmt/eventhub/v2017_04_01/models/resource_py3.py
100% <ø> (ø)

...gmt/eventhub/v2017_04_01/models/access_keys_py3.py
100% <ø> (ø)

.../v2017_04_01/models/arm_disaster_recovery_paged.py
80% <ø> (ø)

...gmt/eventhub/v2017_04_01/models/destination_py3.py
100% <ø> (ø)

...nthub/v2017_04_01/models/authorization_rule_py3.py
100% <ø> (ø)

.../eventhub/v2017_04_01/models/error_response_py3.py
63.63% <ø> (ø)

...ub/v2017_04_01/models/arm_disaster_recovery_py3.py
45.45% <ø> (ø)

.../eventhub/v2017_04_01/models/consumer_group_py3.py
100% <ø> (ø)

...venthub/v2017_04_01/models/tracked_resource_py3.py
100% <ø> (ø)

... and 4315 more

Continue to review full report at Codecov.

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


How to use markdown mode?

Has it been removed?

Yes

Yup, it was removed as it was too buggy and hard to maintain. We recommend you stick to only one format in your strings anyway, for usability purposes.


CVE-2021-44228 (Apache log4j) tracking issue

I used nix-locate to find instances of log4j v2 (possibly affected by CVE-2021-44228).
nix-locate -1 log4j-core-2 | uniq | tr '\n' ' '
nix-locate -1 log4j-api-2 | uniq | tr '\n' ' '

Packages listed below contain a log4j jar. Note that shipping the log4j jar does not imply vulnerability nor exploitability. This list is not exhaustive for many reasons (using 21.11 as nix-locate index; packages not cached thus not indexed).
Not vulnerable means I believe 21.05/21.11/unstable is not affected.

Package
Status

apache-jena
Fixed https://github.com/NixOS/nixpkgs/pull/150610 https://github.com/NixOS/nixpkgs/pull/150650 - 21.05?

arduino-core
Upstream fix released, not packaged

arduino
Upstream fix released, not packaged

elasticsearch7
Fixed #150879 #150986

elasticsearch6
Fixed #150879 #150986

elasticsearch6-oss
Fixed #150879 #150986

flink
Upstream fix released - https://github.com/NixOS/nixpkgs/pull/151776

ghidra-bin
Fixed https://github.com/NixOS/nixpkgs/pull/150154 https://github.com/NixOS/nixpkgs/pull/150159 https://github.com/NixOS/nixpkgs/pull/150211

graylog
Fixed https://github.com/NixOS/nixpkgs/pull/150511 https://github.com/NixOS/nixpkgs/pull/150594 https://github.com/NixOS/nixpkgs/pull/150904

igv
Upstream fixed, not packaged

jitsi-videobridge
Not vulnerable https://github.com/NixOS/nixpkgs/pull/150021 https://github.com/NixOS/nixpkgs/pull/150027 (missing 21.05 backport) Upstream: Jitsi-videobridge instances older than 2.1-504 (May 2021) with callstats enabled should be updated to 2.1-504 or newer (source)

jmeter
Fixed #151080 #151087

logstash6
Fixed #150879 #150986

logstash7
Fixed #150879 #150986

logstash6-oss
Fixed #150879 #150986

logstash7-oss
Fixed #150879 #150986

signald
Fixed #150479 #150523 #150526

solr
8.11.1 released (2.16.0), not packaged - mitigated by adding services.solr.extraJavaOptions = [ "-Dlog4j.formatMsgNoLookups=true" ]; to your configuration

storm
Upstream fixed (2.17.0), but unreleased

xmlbeans
Upstream fixed (2.17.0)  but unreleased

zap
Fixed (2.15.0) #150289 #150406 #150295 (no 2.17.0 released planned source)

keycloak
Not vulnerable source

unifi[6]
Mitigated https://github.com/NixOS/nixpkgs/pull/150329 https://github.com/NixOS/nixpkgs/pull/150329 https://github.com/NixOS/nixpkgs/pull/150425 https://github.com/NixOS/nixpkgs/pull/151145 https://github.com/NixOS/nixpkgs/pull/151179 https://github.com/NixOS/nixpkgs/pull/151178

May as well add metabase. This was already fixed on master, backport waits for being merged: #150310.

Actually, it may be a good idea to take a look at EVERYTHING that directly depends on jdk/jre (whatever the version). Log4J is a very popular library.

Will patch pkgs.signald tonight.

Would it be possible to hook a scanner like https://github.com/mergebase/log4j-detector into some postIntall-Hook for all packages depending JDK? Or maybe directly into Hydra?

As soon as a new release of Jmeter is released, I'm going to update it.

Note that the Log4J maintainers have made additional releases (2.16.0 and 2.12.2) which are now listed as the fix for CVE-2021-44228 (instead of 2.15).
It fixes a (less severe) denial of service (CVE-2021-45046) and disables JNDI by default.
Most downstream consumers will probably make yet another release...

I'm working on updating ELK 7 and should have a PR ready soon.

PR for Jmeter already submitted (#151080).

I currently don't have time to go through all pull requests and update the table, but it's important to note that the second CVE has had its severity raised and various bypasses for the fixes in 2.15 have surfaced; version 2.15 still appears to be susceptible to RCE depending on the exact configuration/deployment.
Packages should be upgraded to log4j2 2.16 (or 2.12.2) to be considered fixed.
Also note upstream recommendations for mitigation have been updated (deleting the JNDI class instead of disabling lookups through configuration).
Additional reference: Log4Shell Update: Severity Upgraded 3.7 -> 9.0 for Second log4j Vulnerability (CVE-2021-45046)

Well, we will probably need to update all again soon:

https://twitter.com/theprincessxena/status/1472074075304562689
https://issues.apache.org/jira/browse/LOG4J2-3230
https://lists.apache.org/thread/w7kob4v6f3wm63g5j48wvcbj7l9y343q

Related MRs:
gradle

https://github.com/NixOS/nixpkgs/pull/150866
https://github.com/NixOS/nixpkgs/pull/151790

pdftk

https://github.com/NixOS/nixpkgs/pull/151791

Another PR for Jmeter:
https://github.com/NixOS/nixpkgs/pull/152176

mediathekview might be affected, the latest version 13.8.1 patched the distributed log4j version https://mediathekview.de/changelog/13-8-1/
As it also updated compatibility to Java 17, and no working Java 17 distribution is in 21.11 or master atm, I'm still working on how to best address this.
See issue #152259 for now.

@ius @antono @auntie @robberer @bjornfor @bergey A new version of arduino with log4j fixes has been released

@ius @mimame Fixes for log4j have been released for igv too.

Can we close this issue or is there any open task?

Can we close this issue or is there any open task?

From a quick look seems that Solr is the main one missing.

Let's close this. Packages should either be patched by now, otherwise they're likely to be orphaned and suffer from other issues as well.
In case of Solr it looks like it has plenty of vulnerability tags slapped onto it.


[Enhance] Allow using custom fps or input fps in video demo

Motivation
Users can set the fps of the output video, or use the fps of the input video.
Modification
Modify

demo/restoration_video_demo.py
mmedit/apis/restoration_video_inference.py

Should we continue to merge this?

@wangruohui Let me double check.

@wangruohui ok to merge~

This pull request is closed because it has been open for 30 days with no activity.


AssetGroup

This is for #222 .
A few notes:

members is protected so it can be accessed by the protected asset() and delayedAsset() inline functions. There's also an internal @PublishedApi for it so it can be used for the unloadAllSafely() inline function. But I thought in some cases someone might want to customize the asset()/delayedAsset() functions and therefore need a way to directly add to the set.
I added toString() for the two types of assets so reacting to caught exceptions in unloadAllSafely()  gives you something that is useful to log. Otherwise, you have very little clue as to which asset threw the exception.
I made MockAsset throw an exception if disposed twice, which is something some Gdx classes do, so I thought it would help effectively test safe unloading.

It just occurred to me, finishLoading() possibly could prioritize the group's members if we hung onto the asset file names and used manager.finishLoadingAsset<Any>(filename) on each of them. We wouldn't be using the return value of that method. This could be done by making members into an ObjectMap<Asset<*>, String> or by promoting assetDescriptor to part of the Asset interface.

It just occurred to me, finishLoading() possibly could prioritize the group's members if we hung onto the asset file names and used manager.finishLoadingAsset<Any>(filename) on each of them.

That's only partially true, because AFAIR it does not affect loading scheduling at all - you just happen to break early if the asset was loaded sooner than later. I think we could leverage that, since asset descriptors already store the names and could possibly be parts of the Asset APIs.

OK, I implemented that change. it looks like a cleaner way to do it, because we don't have to repeatedly check isLoaded() for the whole set of assets over and over
It's technically breaking for anybody that wrote their own Asset implementation, although I can't think of a reason anyone would have done that.

Yeah, it's unlikely to be an issue.

Thanks for the contribution.


Params: remove stage deps and --all option

Params:

No dependencies to stage files anymore
--all option for diff

Per iterative/dvc/pull/3631

@dmpetrov @efiop it looks we haven't updated completion scripts for params
@efiop should we make a checkbox after all?

@dmpetrov @efiop it looks we haven't updated completion scripts for params

@shcheklein could you please clarify?

@dmpetrov disregard it here, please, I'll create a ticket on the dvc repo. it's not related to docs.


Feat: Building for production guide - Vite

PR Summary
Reading the Vite building for production guide I found these two ideas which would enhance the download performance and resilience of the application.

By splitting the JS file into 2 smaller files (vendor and our actual code) the loading time of the page should get improved, rather than having a huge file with all code.
Regarding the event added:

Vite emits vite:preloadError event when it fails to load dynamic imports. event.payload contains the original import error. If you call event.preventDefault(), the error will not be thrown.
When a new deployment occurs, the hosting service may delete the assets from previous deployments. As a result, a user who visited your site before the new deployment might encounter an import error. This error happens because the assets running on that user's device are outdated and it tries to import the corresponding old chunk, which is deleted. This event is useful for addressing this situation.

Demo link:

Store
Editor

Checklist:

[x] Added PR summary for release notes
[x] Followed theme code principles
[x] Linted with Theme Check
[x] Tested on mobile
[x] Tested on multiple browsers
[x] Tested for accessibility

@thiguet have we checked the actual performance savings we'd see from this change?

@thiguet have we checked the actual performance savings we'd see from this change?

@thiguet there is a conflict. can we remove this?


added undertext under promo video, and made the default video be the …

…video of the last admission

The undertext should be more visible, and the link should be on a word.


[Feature Request] Option to show actor/token title when displaying image?

It would be great to be able to optionally show an actor or token's name along with the image when you display it to players in fullscreen or windowed modes. Even if it was a module config setting, that would be very useful. Often I want to show NPC portraits to players, and it's helpful to show the names at the same time so I don't have to spell the name aloud for players' notes. I like the fullscreen display in this module better than what Theatre Inserts provides, except for not having the names. Thanks for considering the request, this is a great module!

Hello @JulieWinchester
Thank you for taking an interest in Share Media.
Your request is now implemented with 0.0.31


Adding support for Country Code and Currency Extended Scalars

Pull Request type

[ ] Bugfix
[x] Feature
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Other (please describe):

Changes in this PR
Issue #1405
This PR adds support for CountryCodeScalar and CurrencyScalar, which were both introduced in December, 2022 in 20.0 of graphql-java-extended-scalars here.
I introduced new groups for country and currency since these didn't seem to fit well under any existing groupings, but of course am open to groupings that people think make more sense.
The documentation update is in a separate PR, here.

Resolves: https://github.com/Netflix/dgs-framework/issues/1405

Thanks for submitting @ArvindR12! We will take a look and get back to you ASAP.


suggestion to simplify by removing the submit time command

IMO users will be quite confused when they see the two command "Track Time" and "Submit Time", especially as they look nearly identical and perform exactly the same action.
I think we can simplify this by only keeping the "Track Time" command. When testing the extension to check if it is ready for release I noticed that I really missed the caching feature of the "Track Time" command when I was using the "Submit Time" command. One use case I could see here is when you want to track a time for yesterday for example, you might want to quit raycast to find out when you stopped working at that day and of course would want to keep the start data which you filled in before.
Also, caching does not interfere with any submission of attendances as they always get reset when you submit an attendance.
Suggested Changes

remove "Submit Time" command
rephrase description and readme of "Track Time" command
keep cache for "Track Time" command, maybe even include "End Time" for caching (you might want to quit raycast to quickly check whether your times are correct, this could include the end time)

What do you think about this @Boosteblume? We should decide about this before updating the PR at raycast.

we decided to rename the command to "Add Past Times" which more accurately reflects what it does. This removed the ambiguity between the two commands.


Add return type to HTML5DOMDocument::loadHTML to fix runtime on PHP 8.3

This turned out to be an easy fix. It was a PHP version issue, not a Kirby version issue. Closes #21.

Thanks!


Booksearch - Frontmatter and content setting keeps being close  after being selected

Hi,
Frontmatter and content setting keeps being close  after being selected..... So i cannot use the command [Create  Book Note] as it does not popup for us to enter a book name... In version 4.1 everything works fine
By the way thanks a lot for having created this very useful plugin...
Robert

Same as per Issue #35

This issue is fixed in version 0.5.5.
@robert-canuel @ceccadroid thank you.


fix: disable deploy to staging CI job as staging is off

:tada: This PR is included in version 5.8.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Birddog quad can only change 1 decode source

On the birddog quad when trying to change the decode source I'm only able to switch the decode source for the first SDI port and not the other 3 ports. Is this a limitation to the API or something in the module?

It looks like it might just be an oversight, as the API lists "Range 1 to 4", butI don't have a Quad to test with myself. I will take a look and see if I can workshop a version for you to test

It looks like you can address ports 2-4 via query string arguments; if no query string argument is present it defaults to ChNum=1
/connectTo?ChNum=1
{
  "sourceName": "IN-TABBY (HDMI)"
}

On devices that don't have more than a single encode/decode channel:
/connectTo?ChNum=2
{
  "status": "File Not Found!"
}

(it did return error code 404 as well).
I'll put one of my Quad's up on the network shortly and grab some captures for you.


⚠ Samsung has degraded performance

In 66f663a, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2672 ms

Resolved: Samsung performance has improved in 8f3e46b.


Small change to make connaisseur running under OpenShift / OKD 4

This is needed for OpenShift / OKD 4
If we want to make connoisseur runnable under OpenShift / OKD 4, the easiest way is:

disable securityContext in deployments completely.

Fixes #
Description
Create a variable, which can disable securityContexts.
Checklist

[ ] PR is rebased to/aimed at branch develop
[ ] PR follows Contributing Guide
[ ] Added tests (if necessary)
[X ] Extended README/Documentation (if necessary)
[ ] Adjusted versions of image and Helm chart in values.yaml and Chart.yaml (if necessary)

Codecov Report

Merging #663 (ec92f33) into master (37d8533) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #663   +/-   ##
=======================================
  Coverage   96.81%   96.81%
=======================================
  Files          22       22
  Lines        1226     1226
=======================================
  Hits         1187     1187
  Misses         39       39

Continue to review full report at Codecov.

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

@pflaeging shouldn't it be sufficient to just remove contents of securityContext and pass an empty list?
Or we could allow just removing it by deleting the whole section, including securityContext by allowing no securityContext to be configured at the following: https://github.com/sse-secure-systems/connaisseur/blob/master/helm/templates/deployment.yaml#L88
I am not so much in favor of creating a non-native flag simply for one flavor of k8s.

@pflaeging shouldn't it be sufficient to just remove contents of securityContext and pass an empty list? Or we could allow just removing it by deleting the whole section, including securityContext by allowing no securityContext to be configured at the following: https://github.com/sse-secure-systems/connaisseur/blob/master/helm/templates/deployment.yaml#L88
I am not so much in favor of creating a non-native flag simply for one flavor of k8s.

I can try this manually and give you feedback. For me it's OK with an empty list, lets see what OPenShift says ;-)

@pflaeging is there a way to get direct feedback from openshift? would be interesting to get their take. Happy to support making the overall entry of securityContext optional. Let me know if I should contribute.

@pflaeging nevermind, I got the point. There is no helm-native way to remove a set value, so this seems like the most at hand solution to the issue. Will move it forward.
Thanks for pointing this out :pray:

@pflaeging I proposed a minor rewording. Currently, testing fails because we are setting securityContext.enabled with your change and that field is not allowed. A better way maybe as done in the cloudone but that is a breaking change for us and I'd rather not have that. We could add disableSecurityContext field before securityContext which is also "not nice" or allow setting it to empty. What do you think?

@pflaeging I proposed a fix to simply set securityContext: null which should remove the context, is compatible with helm-native configuration and hopefully fixes the problem for OKD/Openshift. Could you test and let me know?
Also please rebase to develop so it can be merged or let me know if I should do it (just a bit hesitant since it is your master branch) :slightly_smiling_face:

@pflaeging any feedback on this? Otherwise, I'd like to go ahead and merge next week 🙂

Sorry, I'm back from Covid right now and check ist back, ...

OK, we can cancel the pull request. I've tried the following and it works ;-):
In your values.yaml set:
  securityContext: null
  podSecurityPolicy:
    enabled: false
    name: ["connaisseur-psp"]

Then I'm rolling the helm chart out with:
helm install connaisseur connaisseur/helm --atomic --namespace infra-connaisseur -f values.yaml
And it run's without patching anything.
If you show me the place I can give a small advice in the documentation how to install clean on OKD / OCP (we are using cosign).
Greetings
:peter


Root ca

Motivation

Please give a brief description for the background of this change.
We should not validate code while parsing. We have a separate method Validate for this purpose.
Device Client should fail only if invalid RootCA file path is passed. Since it is not an mandatory field anymore, we should should not fail if the user fails to pass value for it.

Modifications
Change summary
Please describe what changes are included in this pull request.

Removed redundant code and moved it to Validate method in config.cpp
Updated the CONFIG.md documentation file.

Revision diff summary
If there is more than one revision, please explain what has been changed since the last revision.
Testing
Is your change tested? If not, please justify the reason.
Please list your testing steps and test results.

Added enough unit tests for testing my changes.
CI test run result:

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

I made all these changes so that Greengrass Secure Tunneling component would work. I agree we should update the README but the rest of the changes are just undoing the changes that make fixed Greengrass.


Calculate Difficulty

Implement the calculate_difficulty method in src/blockchain.py so that difficulty scales as hashing power of the network goes up. This will require implementing timestamps to the data model as well (#12). We can take inspiration from bitcoins a block every 10 minutes approach.

Faiyaz's implementation of calculate_difficulty requires an index, which we can't directly get from the protobuf repeated message field. Should implement a way to make it not use an index as a parameter.


no default check on multisig with conffig

@bee344 would it be possible to have this pr rereviewed and the logic added in.
the idea with this PR was that the system would read the config file first and use the values in the config file for the prompts 'default' value when displayed.  in that way the data on the prompt would be the final data used (either as default from the config or overridden by user at run time)

@achamely sure, I'll take a look at this and it will probably go in on Monday, thanks for the interest!


WCSimWCDigi::RemoveDigitizedGate()

This fixes some bugs in WCSimWCDigi::RemoveDigitizedGate() concerning the digitized composition vector of pairs, which is the cause of #114

This seems reasonable and fixes the NDigits2 trigger option without affecting the output of the default NDigits trigger. I'll go ahead and merge this in.


Can't run app from Store, but could from Visual Studio

Describe the bug
I recently published app to Store, but found out app could not launch. So I try run app from Visual Studio and everything is okay. App is WinUI 3 packaged, C#, desktop type.
Event viewer report:
Faulting application name: CloudCash.Client.exe, version: <IP_ADDRESS>, time stamp: 0x61e1d74c
Faulting module name: Microsoft.ui.xaml.dll, version: <IP_ADDRESS>3, time stamp: 0x18fd9864
Exception code: 0xc000027b
Fault offset: 0x00237ca9
Faulting process id: 0x0x58C8
Faulting application start time: 0x0x1D83C764D801E4D
Faulting application path: C:\Program Files\WindowsApps\ParaBellumSoftware.CloudCash_<IP_ADDRESS>_x86__gt9edag94s58j\CloudCash.Client\CloudCash.Client.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.WindowsAppRuntime.1.0_1.440.209.0_x86__8wekyb3d8bbwe\Microsoft.ui.xaml.dll
Report Id: 1c662a86-1d75-48ba-8144-bd62db652af1
Faulting package full name: ParaBellumSoftware.CloudCash_<IP_ADDRESS>_x86__gt9edag94s58j
Faulting package-relative application ID: App
Partner Center exception classification: stowed_exception_80131040_winrt.runtime.dll!unknown
Stack trace from Partner Center related to app:
Frame	Image	Function	Offset
0	combase.dll	RoOriginateLanguageException	0x0000000000000038
1	WinRT.Runtime.dll	undefined	0x00000000000391FE
2	Microsoft.WinUI.dll	global::Microsoft.UI.Xaml.Controls.ITabViewStatics.get_CanDragTabsPropertyt	0x0000000000000003
3	Microsoft.ui.xaml.dll	DirectUI::FrameworkApplicationFactory::Start	0x000000000000018E
4	Microsoft.WinUI.dll	undefined	0x0000000000320DBC
5	CloudCash.Client.dll	undefined	0x0000000000023092
6	coreclr.dll	CallDescrWorkerInternal	0x0000000000000034
7	coreclr.dll	CallDescrWorkerWithHandler	0x0000000000000066
8	coreclr.dll	MethodDescCallSite::CallTargetWorker	0x00000000000000E7
9	coreclr.dll	RunMainInternal	0x00000000000000E4
10	coreclr.dll	RunMain	0x000000000000009F
11	coreclr.dll	Assembly::ExecuteMainMethod	0x000000000000017C
12	coreclr.dll	CorHost2::ExecuteAssembly	0x000000000000013D
13	coreclr.dll	coreclr_execute_assembly	0x00000000000000C6
14	hostpolicy.dll	run_app_for_context	0x0000000000000414
15	hostpolicy.dll	run_app	0x0000000000000052
16	hostpolicy.dll	corehost_main	0x00000000000000F5
17	hostfxr.dll	execute_app	0x0000000000000253
18	hostfxr.dll	`anonymous namespace'::read_config_and_execute	0x00000000000000B9
19	hostfxr.dll	fx_muxer_t::handle_exec_host_command	0x0000000000000104
20	hostfxr.dll	fx_muxer_t::execute	0x0000000000000238
21	hostfxr.dll	hostfxr_main_startupinfo	0x000000000000008B
22	CloudCash.Client.exe	exe_start	0x000000000000079A
23	CloudCash.Client.exe	wmain	0x000000000000008A
24	CloudCash.Client.exe	__scrt_common_main_seh	0x00000000000000FA
25	kernel32.dll	BaseThreadInitThunk	0x0000000000000019
26	ntdll.dll	__RtlUserThreadStart	0x000000000000002B
27	ntdll.dll	_RtlUserThreadStart	0x000000000000001B
I have no idea, where to look, what to try, ... Simply how to debug.
Steps to reproduce the bug

Run app

Expected behavior
App is launching
Screenshots
No response
NuGet package version
No response
Windows app type

[ ] UWP
[X] Win32

Device form factor
Desktop
Windows version
Windows Insider Build (xxxxx)
Additional context
No response

@JanRajnoha Are you able to launch the app via sideloading by creating an MSIX package? Are you able to share a crash dump?

@ojhad Nothing is working, just launching from Visual Studio, so official package through store or installing via PowerShell script (sideloading) is same -> not working. Crash dump I'll try to find

I don't know, where to find dump file, but I could provide file from WinDbg.

WinDbgReport.txt

It is problem in Microsoft.UI.Xaml, but fyi @danielayala94 @Scottj1s maybe you will know more

@JanRajnoha Here are some instructions on how you can collect a crash dump: https://github.com/microsoft/microsoft-ui-xaml/blob/main/docs/debugging_crashes.md

I found solution for this problem. I have wrong entry point in package manifest.

I found solution for this problem. I ahve bad entry point in package manifest and therefore app could not start properly

I'm seeing the same issue but with an unpackaged Windows App SDK 1.0.2 + WinUI 3 app installed with the setup program created from this extension: https://marketplace.visualstudio.com/items?itemName=VisualStudioClient.MicrosoftVisualStudio2022InstallerProjects
I can't get the exe to launch at all when installed, but I can run it from VS 2022. All I see in the event viewer is this:

@dannyr-git good luck, it's a nightmare to debug this. For me it was because I was using WebView2 which was broken in unpackaged apps since you couldn't configure the user data directory  (there might be a workaround for that now), but I didn't see any reference to that in your app

@dannyr-git good luck, it's a nightmare to debug this. For me it was because I was using WebView2 which was broken in unpackaged apps since you couldn't configure the user data directory (there might be a workaround for that now), but I didn't see any reference to that in your app

Haha, yes I had to debug quite a few 'broken for unpackaged' things so far myself.  things like ApplicationData are only available for packaged, etc.
But this is different.  This app will work on the box I wrote it on, but no one else's.  I'm pretty sure it is because the actual SDK is installed and not just the runtime environment for Windows Apps.

Looks like the original issue was addressed by fixing the entry point in the manifest.  Closing it out.


actor contacts API in BFF

Codecov Report

Merging #572 (2883229) into main (0851394) will decrease coverage by 0.99%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main     #572      +/-   ##
==========================================
- Coverage   66.32%   65.32%   -1.00%
==========================================
  Files          11       11
  Lines         196      199       +3
  Branches       19       19
==========================================
  Hits          130      130
- Misses         61       64       +3
  Partials        5        5

Impacted Files
Coverage Δ

....WebApi/Controllers/MarketParticipantController.cs
0.00% <0.00%> (ø)

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more


Questions for CMUNeXt Training

Hello author, your article CMUNeXt is great. We have some questions about training with this repository and would like to get your answer:

we divide the dataset and train CMUNeXt according to the readme document, however the best results obtained are much lower than the results in the paper as follows:
epoch [212/300]  train_loss : 0.1227, train_iou: 0.8474 - val_loss 0.2993 - val_iou 0.6664 - val_SE 0.7741 - val_PC 0.8161 - val_F1 0.7900 - val_ACC 0.9667
We believe this may be a problem due to inconsistent dataset partitioning. So if you can could you send me a list of the training set and test set if possible, thank you very much! Email: liuweifeng0327@gmail.com!!!

Thanks for using our code.
Split file on BUSI I have sent to your email.

I also meetthe same problem, can you share the data set  if possible,Email<EMAIL_ADDRESS>


Implement dependency service

Hello,
I think It would be nice to follow best practices and implement dependency service.
As it is implemented here: https://developer.xamarin.com/guides/xamarin-forms/dependency-service/battery-info/

What would you delegate to the dependency service?

I think at least maprenderer is s good candidate

How would it simplify something? (I don't know if it is a good or bad thing, just trying to understand :) )
I would just avoid linking the X.F.GoogleMaps.Android to the main .Droid project? (and same for iOS)

Advantage it would be easier to test
You dont need have instance of object DI will provide to you.

Hum I thought it was the same as in ASP.Net, where you need to register the type, but it seems in Xamarin it autoregisters with the class attribute
[assembly: Dependency(typeof(BatteryImplementation))]
But I believe the reason why Maps is beeing loaded is because of the linker, that would not load link the types otherwise. I haven't tried, but are you sure it would not be an issue if moved to DI? (as moving to DI would be, I guess, to move the init code to the common project). Also still need to handle differently the initiation for Android and iOS (iOS requires a key?)

I don't know different from battery-info to current implementation.
DependencyService is already used in X.F.GoogleMaps.
https://github.com/amay077/Xamarin.Forms.GoogleMaps/blob/master/Xamarin.Forms.GoogleMaps/Xamarin.Forms.GoogleMaps.Android/Properties/AssemblyInfo.cs#L23
What is the point of your suggestion?


Cubic root

Merge changes for version 1.2-0 (added cbrt() function)

My first pull request!
Closes #1


PHP VCR is not supporting Laravel 7.0

We are using php-vcr in Laravel 6.0. Trying to upgrade 7.0 and getting below error.

symfony/event-dispatcher v2.6.0 conflicts with symfony/console[v5.0.8].

Below packages needs to update latest version and support.
"symfony/yaml": "~2.1|^3.0|^4.0",
"symfony/event-dispatcher": "^2.4|^3.0|^4.0"
I have tried to fetch latest versions like below
"symfony/yaml": "~2.1|^3.0|^4.0|^5.0",
"symfony/event-dispatcher": "^2.4|^3.0|^4.0|^5.0"
But VCR http calls getting failed. Can anyone check this?

I would suggest adding support for Symfony 5 to PHP-VCR, as that is what is the core problem.

Yes, support for Symfony 5 is main problem with PHP 7.3.
For upgrade PHP-VCR is not working on PHP 7.4.
Regards,
Srini

On May 20, 2020, at 3:58 AM, Jeroen van Oort<EMAIL_ADDRESS>wrote:
I would suggest adding support for Symfony 5 to PHP-VCR, as that is what is the core problem.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/php-vcr/php-vcr/issues/303#issuecomment-631403428, or unsubscribe https://github.com/notifications/unsubscribe-auth/APM553FDQXWVVWE3NOEMLRTRSOZXHANCNFSM4NBWNQNA.

Resolved by https://github.com/php-vcr/php-vcr/issues/320 in 1.5.0.


Updating link to rewrite-http-headers-portal.md

In rewrite-http-headers-url.md, there should be a link to rewrite-http-headers-portal.md in the header sections instead of link to rewrite-url-portal.md.

Learn Build status updates of commit 3089f2e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/application-gateway/rewrite-http-headers-url.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

@greg-lindsay

Can you review this PR?
IMPORTANT: When this content is ready to merge, you must add #sign-off in a comment or the approval may get overlooked.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off


DB cannot be loaded

Hi,
thank you for this very useful tool.
I have been using it for a few weeks now and it works very well.
I have a dataset for which it doesn't seem to run properly though, and I did not manage to figure out why.
Basically the workflow starts but then it seems to not be able to load the DB:
Loading database information... done.
0 sequences (0.00 Mbp) processed in 0.001s (0.0 Kseq/m, 0.00 Mbp/m).
  0 sequences classified (-nan%)
  0 sequences unclassified (-nan%)
Waiting at most 250 seconds for missing files.

MissingOutputException in line 77 of /software/envs/phanta/Snakefile:
Job Missing files after 250 seconds. This might be due to filesystem latency. If that is the case, consider to increase the wait time with --latency-wait:
/scratch/phanta/classification/D_clean_conc_SE.krak completed successfully, but some output files are missing. 125

I am  not sure why this is the case, and I double checked all the paths and all is where is supposed to be.
Do you guys have any tips on how to go around this?
Thank you
Stefano

Hi Stefano,
Thank you for the question, glad the tool is working well for you! Just to ask the first question that comes to mind, how many reads are in the sample you are trying to classify?

Hi,
thank you so much for the message and sorry for the late reply. Indeed there were issues with my input files. Two names were merged and one file was huge and another empty. I fixed this and now all worked well.
Thank you!
I will close this
Stefano


Tuist 0.13.0 release

Adding a post to highlight some of the new features of Tuist 0.13.0
Introduced new .posts__post-screenshot css class to help style screenshots

Preview: https://deploy-preview-30--peaceful-fermat-c0d5d7.netlify.com/blog/2019/04/01/version-0.13.0/

too much shadows perhaps?
Without styling it looked a little bland:

@kwridan I like the shadows, nice touch.


Expiration labels fix

Description
Changes proposed in this pull request:

changes to the code introduced in #1972 with accordance to the established labels

Related issue(s)

/hold

/unhold