Synchronisation disabled - Android 6.0.1

Using two devices with Android 6.0.1 (N5 and N7 (2013)) I'm experiencing the synchronisation getting disabled in (random?) intervalls.
It seems I can get it enabled again by switching WIFI Off and on again.

sounds like it might be related to #857

That might be. However, I did not experience this with 6.0, but only with 6.0.1.

I have a similar problem where the next poll is showing as being 1 hour ago.

I experience no issues of K-9 under Cataclysm, Android 6.0.1.

I'm having the same problem here, Nexus 5X on Android 6.0.1 with K-9 Mail 5.007.
I've set "Background sync" on "Always" now, (was: "When 'Auto-sync' is checked"), as that is suggested in the FAQ. But time will tell if that's gonna work..

Background Sync "Always" is set in my N7, but doesn't seem to make a Differenzen.

Hmm, indeed, that didn't make any difference :sob:

Please record a debug log while this happens.

K-9 Mail 5.007 on Nexus 7 with Android 6.0.1
since the last update syncing keeps disabling itself. I trolled all the settings and tweaked here and there but nothing helps when I look again syncing is disabled. it also does not matter if we set the background sync to Always or when auto sync is enabled. the tablet does not have an auto sync global setting. my LG G3 phone has a global sync button though.running Android 5.0 and seems to work fine. so problem is probably Android 6.0.1?

Hello, this is a debug log. Actually, I enabled logging while my N7 was in the state of disabled synchronization. I synced once or twice manually and then switched Wifi off and on again. This enabled the synchronization again. I left logging on and this afternoon I realized that synchronization got disabled again somewhen. Unfortunately, I don't know the exact time. Again I manually synced once or twice and switched Wifi off and on again. Once more, synchronization got enabled afterwards.
Hope this helps debugging the issue.
k9-log.txt
k9-log_1.txt

FWIW: It is doze that is causing this issue.
The current workaround is to whitelist k9 from doze.
System Settings --> Apps
Hit the "gear" button up beside the menu button, brings you to "configure apps".
Hit "Battery Optimization", choose "all apps" from the spinner, click k9mail, and select "Don't Optimize". That will prevent doze from knocking it out.

Well, don't know for sure about that "not using much more battery" on my Nexus 5X:

OK, granted, this isn't with much extensive usage (just the occasional WhatsApp/browsing/e-mail), but I thínk K-9 Mail's unoptimized Push mail has quite the impact.

@osirisinferi For what its worth, the power consumed by k9mail can be dramatically impacted by a lot of factors, number of accounts, number of directories being synchronized, configuration of the IMAP server, etc. In the end though, it won't be drawing any more power with this workaround than it did prior to the introduction of doze.

Running Android 6.0.1 on Nexus 6.
Have two Google accounts that are accessed through GMail.
K-9 is used to access two unrelated IMAP accounts.
One of the above Google accounts is not really used on the phone. However, if I completely disable its sync then I notice this K-9 thinks that AutoSync is off system wide even though one if the Google accounts is full sync enabled.
Once I re-enable at least App Data sync on that disabled account K-9 detects that AutoSync is on again with the next sync 3 hours ago.

Just as an added data point, I see this happening on my Nexus 7 (2013), but not on my Nexus 9. Both are running 6.0.1. As far as I can tell, K-9 has not been added to the whitelist on the N9 or anything like that.

It definitely happens on N9 (we have two N9's). Yours is probably not getting all the way to sleep. Possibly something is holding a wakelock.

My mistake. Putting the N7 and N9 next to each other and leaving them both alone for the same amount of time did show that behavior on the N9.
I'll have to do further testing to see if there's something keeping the N9 out of Doze or if it's actually restarting the syncing on its own somehow.  Just odd that this would be the first time I've noticed the problem on the N9.

Just bumping the things around can keep them out of doze. I'm not actually sure if the 7 has a low power motion sensor that it can be used for this purpose, so it could have a greater tendency to go into doze, whereas the 9 will reset its timers by being moved slightly.

Having the same problem with a HTC One M9 since having upgraded to Android 6.0 (the latest version available from HTC). Before updating to Android 6.0, on 5.xx everything was o.k.
As suggested, I tried to disable all 'power saving' functions, no luck...

Please record a new debug log if this is still happening with whitelisting disabled @Rhenania

Here‘s the requested bug report with all power saving options disabled.
Rgds
From: Philip<EMAIL_ADDRESS>Sent: Freitag, 15. April 2016 12:07
To: k9mail/k-9<EMAIL_ADDRESS>Cc: Rhenania<EMAIL_ADDRESS>Subject: Re: [k9mail/k-9] Synchronisation disabled - Android 6.0.1 (#970)
Please record a new debug log if this is still happening with whitelisting disabled @Rhenania https://github.com/Rhenania
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub https://github.com/k9mail/k-9/issues/970#issuecomment-210399272 https://github.com/notifications/beacon/ARn8KRAf2DBZ9r_iJnY7YFyPHvYS2--Lks5p32NAgaJpZM4G5UKJ.gif

Debug log as referenced above
debugLog.txt

Why is this bug still labeled as "needs info"? This is a matter of doze kicking in. No info is needed -- the cause is well established.

There's a bug for Doze - #857. I believe this bug was for issues despite disabling Doze. We still need to get to the bottom of those.

In my case, K9's periodical sync works but push doesn't work in Doze on Sony xperia z5 with 6.0 Marshmallow. K9 is whitelisted and notification is set as "High priority" (←GCM setting?).
Though it's Doze caused problem, can next update of K9 solve this???
So far I put "Android system" app into whitelist, then the push seems working fine.
But im not sure if it's just temporal behavior....

About the same symptoms I also observe on my HTC M9. Was waiting for either an Android update or a K9 fix. Being fed up with waiting, now also considering installing an alternative ROM.
From: takaox<EMAIL_ADDRESS>Sent: Tuesday, June 07, 2016 3:22 AM
To: k9mail/k-9<EMAIL_ADDRESS>Cc: Rhenania<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [k9mail/k-9] Synchronisation disabled - Android 6.0.1 (#970)
In my case, K9's periodical sync works but push doesn't work in Doze on Sony xperia z5 with 6.0 Marshmallow. K9 is whitelisted and notification is set as "High priority" (←GCM setting?).
Though it's Doze caused problem, can next update of K9 solve this???
So far I put "Android system" app into whitelist, then the push seems working fine.
But im not sure if it's just temporal behavior....
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/k9mail/k-9/issues/970#issuecomment-224135977 , or mute the thread https://github.com/notifications/unsubscribe/ARn8KQNs14oJUWVIU0tphSiWjUSCeP0Iks5qJMe5gaJpZM4G5UKJ .  https://github.com/notifications/beacon/ARn8KUzqUBhv0h0QCH_iIbM0MEIaSxonks5qJMe5gaJpZM4G5UKJ.gif

As Rhenania said above, yes, we are waiting for "either an Android update or a K9 fix".
Hope both are aware of this to make out a fix. Whether push works or not, it's very fatal issue for some users.

I just want to add that I have the same problem with latest OmniROM and had it with CM13. Sometimes push is working, and sometimes not.

On my Nexus 5x (rooted and running 6.0.1), the solution/workaround @lbdroid posted has worked fine since I used it a few months ago.

All what I have done didn't work, even the way @lbdroid mentioned...
Or if I would root my phone, will there be more options to do?
So far I set K9 poll frequency as every minute.

Is all info need available? I still get the issue - disabling K-9 in app optimising doesn't help. Nor changing sync to "always". It seems log gets truncated - not sure if there's enough infor here:
k9-log.txt
Please let me know if additional info is required, I gladly try to help out.
I don't want to be forced to abandon this app ;-(

I realise that if "Power saving mode" is completely disabled syncing works.

Recently my Xperia Z5 Compact had updated to [Android 6.01 - 32.2.A.0.224].
The doze mode seems to have gone and Sony's Stamina mode is back now.
But point is that no matter whether I use Stamina mode, K9's push got recovered to
properly work now as it has been on old Android versions except for [6.0].
(Of course, if you use Stamina mode on, then K9 still needs to be whitelisted)
Now it's proved that after all the problem was obviously being caused by Doze,
Doze's [Optimize] even didn't work, it almost has killed core functions.
Not sure how other users with similar phones would be now....?
Hope this update helped many like us.

I believe I have this problem; let me know if a log would be useful.
Samsung Note 4, 6.0.1; global sync enabled. On wifi.
k-9 beta 5.109
IMAP account; polling disabled for all folders. push enabled ("1st class") for one folder (not INBOX).
Background sync when Auto-sync.
After a few hours, k-9 reports "syncing disabled". In settings, that folder is still set to push: 1st class. Changing push to none, then back to 1st class, seems to temporarily sort the issue, for a few hours, then back to "syncing disabled".
I don't think this is Doze, since:

I have it disabled entirely: Settings - Battery - app power saving - OFF. Assuming that is what Samsung call Doze? Both other power saving modes (regular, and Ultra) are disabled)

Doze is supposed to kick in after 3 days, minimum, not just a few hours.

are my symptoms in line with this bug, now that Doze is being treated separately?
please let me know if it more data would be helpful, or a log (some have said that the log is truncated and it doesn't happen for several hours).
thanks much.

I have a Samsung Galaxy Note 4.  After my phone's last software update, K-9 mail has been so erratic.  Sometimes it works fine and the next thing I know syncing is disabled.  ...or it will tell me the next sync is some hour or more in the past.  I did find that when I turned on WiFi and then turned it off again, syncing was disabled.  Now that I know shutting WiFi off causes K-9 to stop syncing, I can immediately check it to get it started again.  However, I don't know why it decides to stop syncing otherwise.  I went into my settings and made sure that K-9 was not set to doze to save battery life.  That has not helped.  What's more, sometimes it's a crap-shoot whether I can get it to start syncing again.  Frankly, I'm frustrated.  I need my email notifications.  I have a business and I need to know when my clients have sent mail.  This needs to get fixed.

Also having same problem. Syncing disabled shows up if I set Global settings -> Network -> Background sync -> Always. When I set the option to 'When auto-sync is checked' everything worked fine again.
Samsung Galaxy S5, official 6.0 ROM, battery optimization was enabled (default system settings, didn't touch that), K9 5.010

S7 Edge here and K9 is pretty much incapable of notifying me of new mail. It's configured for IMAP push and is working fine on my old S3 Neo. Setting it to poll doesn't help.
:(

same Problem on Nexus 5X Android 7.0
any solution ??

I have found that white listing the app solved the problem. You have to white list it in the correct place though.
http://www.tech-recipes.com/rx/58206/set-battery-optimization-samsung-galaxy-s7/
While you're there consider white listing GMail, Calendar and Contacts sync since they were suffering as well.

i have "white listed" k9mail now,
thank you for your answer,
will report if this helps
found that "tasker" app was  whitlisted automaticaly
maybe k9mail can do this also?

Using IMAP settings for email (yahoo in my case) k-9 working perfect on android 6.0, the same with pop3 settings are not syncing when phone is in standby, otherwise is work fine

I'm still having occasional issues. Sometimes the idle IMAP connection is being allowed to terminate. Just now I ended up with the draft monitoring still active but my INBOX terminated. I've adjusted the K-9 keep-alive to 12 minutes to see if that helps but obviously that's going to increase battery usage :-/

Same here on Nexus 5x with Android 7.0.

Mine has been a lot better since installing Disable Doze.
Curiously the two apps I use to turn things on and off on a schedule sometimes fail to turn wifi on but otherwise my phone is now scheduling events like it should. Battery life isn't much affected either.

It's strange, because synchronisation works randomly, and I can't figure out what causing it starts to work again (for some time of course).

I've been looking at causes of sync failures recently. I may have some changes to go in for the future surrounding better handling of network disconnection.
I've been playing around with my device sending it in and out of aeroplane mode and onto a captive portal (which K-9 is not a fan of because it thinks it has a network connection but it doesn't in practice).
Also there's a permanent sync disabling function which prevents sync until the app is actually killed. It was added because of some bad behaviour where we didn't reflect an error case. But I'm no longer convinced that case is justified and if it is we could do better.
I don't want to delay the current stuff though (it's been a large 'merge window'), so I'll work on it and get it ready for a future release after the current (large) release is done.

syncthing is having similar problems:  https://github.com/syncthing/syncthing-android/issues/543
I have K-9 whitelisted; before that it was not reliable.  For me, the syncthing happens after doze and from the debug logs syncthing thinks it doesn't have working WiFi.  Turning WiFi off/on causes it to get a WiFi OK notification and then things work.   So my theory is that in coming out of doze (probably, or maybe just some othertimes) somehow a notification to the apps about WiFi is wrong/missed.

One thing that has helped my phone immensely is Disable Doze. But I'm still getting times when one of the IMAP connections (usually Inbox) dies and is never recovered. The other one 'drafts' will remain connected.
I don't see anything particularly in my server logs. Just a note that a connection timed out and was closed.

I put the idle timeout back to the default BTW. 12 minutes didn't help any. Interestingly it seems that the dropped connection only happens on wifi. It also seems to relate to the switch over from data to wifi when I get home. I'm not compeltely sure but I don't think I've ever had the phone lose a connection at work. It seems to always be the evening when I'm at home.
For what it's worth my scheduling app does the following:
2300 - turn off wifi and syncing.
0700 - turn on syncing.
1715 (roughly when I get home) turn on wifi.

Indeed,  disconnecting WiFi restores synchronisation in k9. Perhaps programmers of k9 should use this as a solution.

I am having the same issue with Samsung Galaxy Note 4. I have power saver on, but whitelisted (turned off) K-9 Mail. But after some time, the sync shows disabled. I have sync always set in global settings. When I turn off power saving it works.

Same issue, Nexus 5, 7.1.1

Getting this on Samsung Galaxy S5

Same problem with my Samsung Galaxy Tab S2 (Android 6.0.1) and Wileyfox Swift with Lineageos 14.1: sync is disabled and IMAP push doesn't work any longer. In Lineageos 14.1 I can't find any power saving options described as workaround above...

Did you try installing Disable Doze as per my link above?
This seemed to be the cure for me. At least until the next major release of Android where apparently the Doze functionality is even more aggressive :(

On my Samsung Galaxy Tab S2 it works by setting background sync in K9 global settings to "always".
On my Wileyfox with Lineageos it doesn't work with this setting. Additionally there doesn't exist a doze function to disable (or I cannot find it: it isn't in the app settings menu, nor in the battery settings...).

I don't think the Android OS respects the app specific settings if the power saver is turned on with background data restriction enabled. Could be more of an OS behavior than app specific.

Yes, you are right: I have completely disabled any power saving function on my Samsung tablet in the menu. Additionally I had to enable the "always" option K9 mail the get push working again. Only to disable the power saving hasn't solved the problem...
On wileyfox with Android 7 (lineageos) I haven't found a solution. With CM13 (Android 6.0.1) it works...
Other apps than K9 are working well in background... How they have solved it? Isn't there any solution to get K9 working again with IMAP push?

I have found the energy saving option under lineageos 14. It was my fault, sorry. It's the same way, described in your link. I need some glasses ;-)

Just thinking about the theory that the os is incorrectly signaling availability of WiFi... I've noticed that a couple of apps will flash up a warning on my phone sometimes (Samsung s6) saying that there's no internet connection, but then proceed to function just fine.

On 12/02/2017 07:01, Bugsbane wrote:

Just thinking about the theory that the os is incorrectly signaling
availability of WiFi... I've noticed that a couple of apps will flash up
a warning on my phone sometimes (Samsung s6) saying that there's no
internet connection, but then proceed to function just fine.

Yes, my S7e (Nougat) does the same: regularly gets an icon that
indicates “no internet” despite everything working perfectly. Resolves
itself after a few minutes, often.

Can a button be added that manually re-enables sync without having to kill and restart k9 completely?

The refresh button already does that for me.

Yeah, I just tap the sync button whenever I want to see new emails.

Syncing stays disabled if i refresh. I don't see a sync button.

When "background sync is enable" is selected. This seems to work for me.
Always on = syncing disabled.
Lineage OS 14.1.

Edit. Same problem.

Back on modified stock oneplus 3T rom, no issues .

I can unfortunately confirm the same problem on a Samsung Galaxy S7 with Android 7.0. Prior to Android 7.0 (don't remember the old version) it worked, but since I got the upgrade, K9 disables sync sporadically. It's already whitelisted, but I'll try to switch the setting in K-9 to sync always.

Okay, I did one more debug session and did find this one here, containing a NPE:
...
03-31 23:44:10.160 V/k9      (10378): LockableDatabase: Transaction ended, took 40ms / com.fsck.k9.mailstore.LocalFolder.appendMessages(LocalFolder.java:1255)
03-31 23:44:10.166 V/k9      (10378): syncFolder(INBOX) got latch release
03-31 23:44:10.166 I/k9      (10378): About to IDLE for XXX:INBOX/Thread-14
03-31 23:44:10.167 V/k9      (10378): TracingWakeLock for tag ImapFolderPusher XXX:INBOX / id 135 for 60000 ms: acquired
03-31 23:44:10.168 E/k9      (10378): Got exception while closing for exception for XXX:INBOX/Thread-14
03-31 23:44:10.168 E/k9      (10378): java.lang.NullPointerException: Attempt to invoke virtual method 'void com.fsck.k9.mail.store.imap.ImapConnection.close()' on a null object reference
03-31 23:44:10.168 E/k9      (10378): 	at com.fsck.k9.mail.store.imap.ImapFolderPusher$PushRunnable.reacquireWakeLockAndCleanUp(ImapFolderPusher.java:252)
03-31 23:44:10.168 E/k9      (10378): 	at com.fsck.k9.mail.store.imap.ImapFolderPusher$PushRunnable.run(ImapFolderPusher.java:202)
03-31 23:44:10.168 E/k9      (10378): 	at java.lang.Thread.run(Thread.java:762)
03-31 23:44:10.168 E/k9      (10378): Failed synchronizing folder XXX:INBOX @ Fri Mar 31 23:44:10 GMT+02:00 2017
03-31 23:44:10.168 I/k9      (10378):  Command 'synchronizeMailbox' completed
03-31 23:44:10.170 E/k9      (10378): Got exception while idling for XXX:INBOX/Thread-14
03-31 23:44:10.170 E/k9      (10378): java.lang.NullPointerException: Attempt to invoke virtual method 'void com.fsck.k9.mail.store.imap.ImapConnection.setReadTimeout(int)' on a null object reference
03-31 23:44:10.170 E/k9      (10378): 	at com.fsck.k9.mail.store.imap.ImapFolderPusher$PushRunnable.setReadTimeoutForIdle(ImapFolderPusher.java:362)
03-31 23:44:10.170 E/k9      (10378): 	at com.fsck.k9.mail.store.imap.ImapFolderPusher$PushRunnable.run(ImapFolderPusher.java:187)
03-31 23:44:10.170 E/k9      (10378): 	at java.lang.Thread.run(Thread.java:762)
03-31 23:44:10.170 D/k9      (10378): SleepService Preparing CountDownLatch with id = 33, thread Thread-14
03-31 23:44:10.171 I/k9      (10378): BootReceiver Got request to schedule alarmedIntent com.fsck.k9.service.SleepService.ALARM_FIRED.33
03-31 23:44:10.176 V/k9      (10378): TracingWakeLock for tag ImapFolderPusher XXX:INBOX / id 135: releasing after 5639 ms, timeout = 60000 ms
03-31 23:44:10.183 E/k9      (10378): Got exception while idling for XXX:Drafts/Thread-13
03-31 23:44:10.183 E/k9      (10378): javax.net.ssl.SSLException: Write error: ssl=0x6fb0beee00: I/O error during system call, Software caused connection abort
03-31 23:44:10.183 E/k9      (10378): 	at com.android.org.conscrypt.NativeCrypto.SSL_write(Native Method)
03-31 23:44:10.183 E/k9      (10378): 	at com.android.org.conscrypt.OpenSSLSocketImpl$SSLOutputStream.write(OpenSSLSocketImpl.java:824)
...

Interesting enough, the same NPE happened later with the DRAFT folder. Perhaps this messes up sync and afterwards it fails?
I could paste more, but somebody needs to hint me into anonymizing these files.

Something I noticed was when I'm on mobile data (at work or out and about) I get all my work emails via IMAP Idle.  When I get home and my Pixel connects to wifi I stop getting emails.  This was with Doze optimization disabled or enabled.  I also see the inverse when I reboot my phone at home and it starts out with a wifi connection.  It seems as if when switching from mobile to wifi data and vice versa the IMAP idle connection isn't reestablished with the new IP address.

If this is related to doze, I was reading about disable doze completely through this app and script.
I am going to try it later when I am at said phone.
"dumpsys deviceidle disable"
https://forum.xda-developers.com/android/apps-games/root-doze-settings-editor-android-t3235130/page138

@cketti does this issue still needs to be labeled with "needs info"? I've posted some debug log entries here. Either remove that label or state what more information you need and how to retrieve it. Thanks!

Seems pretty obvious; not all of the code in ImapFolderPusher.java checks if connection is null.

ImapFolderPusher.java
Line 185:
                        ImapConnection conn = connection;
                        setReadTimeoutForIdle(conn);
                        sendIdle(conn);

Line 249:
            try {
                connection.close();
            } catch (Exception me) {
                Timber.e(me, "Got exception while closing for exception for %s", getLogId());
            }

@nyetwurk
Sure but we catch the exception. It's not the reason.

Any update on this topic? Can I help with any further information you need for analysis?

I have a Galaxy S8, running Android 7.0.  Here are the steps I took to solve the K9 app syncing problem:
K9 > Settings > Global Settings > Network > Background sync:  change it  to "When 'Auto-sync' is checked".  It might work with Background sync set to "Always", but I haven't tried it.
Android Setting > Device Maintenance > Battery, K9 did not appear in the App power monitor section.  If you see K9 here, make sure it is not checked.
Android Setting > Device Maintenance > Battery > Unmonitored apps (at very bottom of Battery screen) add K9 to  "Unmonitored apps"
Android Setting > Device Maintenance > Battery > Battery Usage (right below "Estimated battery life" at top of screen).  Then click on 3 vertical dots at top right and select "optimize battery usage".   Select "All apps" and  turn off optimization for K9.

@Newbie1980 I have been disabling doze ever since it stopped viber from working properly. Does not help with k9 though

This issue (for me) seems to be entirely linked from connecting initially to my work mail server (imap idle) on mobile data, which works fine, and then getting home and the phone connects to wifi.  At that point I get no more emails until I leave my home and get back on mobile data.
It is as if the connection to the mail server needs to be reset when switching from mobile to wifi (or more to the point when the ip address changes).

Just wanted to let people know that fivemail's post 3 above this one fixed the issue for me on my S6. Please try it.

FWIW, I also noticed that I sometimes (I haven't figured out exact circumstances) don't receive any notifications on WiFi (and when I checked, it did say "Synchonisation disabled"), but as soon as I go out and switch to mobile connection, K-9 suddenly decides to check e-mail.
Android 7.1.2 (LineageOS 14.1), Redmi Note 4, K-9 5.208.
I've just did the workaround mentioned above, I will update this post if it actually helps.

I had to switch mine to 'synchronise always' at the weekend because it just couldn't keep a connection at home over wifi. I refreshed it three times and it still kept dropping out. I don't know where that came from as it's been fine since the end of Summer. I've noticed though that the old 'background sync' option seems to have gone from my S7 Edge. I don't know when that happened but it's at least a month since my phone firmware was last updated.
So far 'synchronise always' has solved the problem for me though.

I can confirm the behavior @WGH- and @drhill have reported: Often e-mails don't get fetched when the device is connected to WiFi, but as soon as it changes to mobile connection e-mails are synchronized again.
I will try the instructions @fivemail has written. The last setting was not set as in the comment.

[x] power saving is disabled for that app
[x] background mobile data is enabled for that app
[x] background synchronization in K-9 Mail is set to 'always'
Android 7.0
K-9 Mail 5.600

Duplicate of #3950

I will try the instructions @fivemail has written. The last setting was not set as in the comment.
* [x]  power saving is disabled for that app

* [x]  background mobile data is enabled for that app

* [x]  background synchronization in K-9 Mail is set to 'always'

* Android 7.0

* K-9 Mail 5.600

Since I tried the recommendations I did not observe the issue any more.


ESP32-S3: Permanently disabling USB-JTAG controller (IDFGH-12995)

Answers checklist.

[X] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

General issue report
Following problem:
On some Win11 machines, the USB-OTG interface is kicked out, because of the sudden changes between the USB-OTG & USB-JTAG/serial interfaces in the ESP32-S3.
So I thought disabling it via eFuses:

DIS_USB_JTAG
DIS_USB_SERIAL_JTAG

But: since then, my chip is bricked. Entering the UART0 download mode results in an immediate core panic, without the possibility to recover:
ESP-ROM:esp32s3-20210327
Build:Mar 27 2021
rst:0x1 (POWERON),boot:0x0 (DOWNLOAD(USB/UART0))
waiting for download
uru Meditation Error: Core 0 panic'ed (LoadProhibited)
Core 0 register dump:
PC      : 0x400511b1  PS      : 0x00060330  A0      : 0x80049188  A1      : 0x3fceb640
A2      : 0x00000000  A3      : 0x3ff1e3fb  A4      : 0x00000001  A5      : 0x00000000
A6      : 0x00000000  A7      : 0x00000088  A8      : 0x800533dc  A9      : 0x3fceb620
A10     : 0xfffffffb  A11     : 0x3fceeebc  A12     : 0x3fceefbc  A13     : 0x00000000
A14     : 0x00000000  A15     : 0x00000006  SAR     : 0x0000001f  EXCCAUSE: 0x0000001c
EXCVADDR: 0x00000000  LBEG    : 0x400570e8  LEND   : 0x400570f3  LCOUNT  : 0x00000000

Backtrace: 0x400511b1:0x3fceb640 0x40049185:0x3fceb670 0x400491e5:0x3fceb690 0x40043917:0x3fceb6b0 0x4004392a:0x3fceb6d0 0x40043c33:0x3fceb6f0 0x40034c45:0x3fceb710

I found no information in the documentation that this setting can brick my chip, maybe this is just related to the bootloader code.
Please provide instructions how to permanently disable the USB Serial/JTAG controller in the chip and if possible how to unbrick my ESP32-S3.
Thank you very much, keep up with the good work!

Hi @benjaminaigner, so far I can only say that this indeed seems to be a bug in the boot ROM. We do have an internal issue report about it, but we only met this once and didn't pursue debugging the issue.
I'm afraid there probably isn't a way to get the chip back to the working state, you'll have to use a new one.
We'll confirm which eFuse is sufficient to disable USB Serial/JTAG and get back to you.

@igrr
Can you kindly confirm the correct efuse to burn please, Thanks

Hi, for anybody who may find themselves here,
DIS_USB_JTAG will not stop the USB JTAG from appearing when the mcu boots!
To prevent USB/JTAG from appearing at all, use the following command:
python espefuse.py --port <COM_PORT> burn_efuse USB_PHY_SEL
Running this command will stop the MCU from appearing at all forever, as the internal PHY selector will always be in OTG mode
If you want to enable USB CDC to flash again, you must hold down the Boot button when connecting the device to your computer; otherwise, your microcontroller won't show up. Please note that USB JTAG functionality will be permanently disabled.

You can find more details about this topic in the documentation at: Espressif USB PHY Documentation.

Note: For ESP32-S3 modules and development boards produced before DateCode 2219 (PW No. earlier than PW-2022-06-XXXX), because EFUSE_DIS_USB_OTG_DOWNLOAD_MODE (BLK0 B19[7]) has already been burned to 1 (USB OTG download disabled), if users burn the efuse_usb_phy_sel bit to 1, it will result in both USB-Serial-JTAG and USB-OTG download functionalities being disabled when the chip enters Boot mode.

@benjaminaigner
Here is your fix, :)


Bug🐛: Docs Page is not responsive for Mobile Devices

Describe the bug.
The Docs page is not responsive on the mobile device, it is occupying some extra space on the right-hand side of the page
Describe the steps to reproduce the behavior

go to the site
go to the docs page
use chrome dev tools to switch between different mobile screens !!

Expected behavior.
the page should be responsive
Screenshots.

Operating environment
Windows 11
Additional context
No response

@joewxboy can I work on it ?

It looks like this is related to https://github.com/open-horizon/open-horizon.github.io/issues/135 and the conversation in the chat room about Jekyll templates: https://matrix.to/#/!tUVxmZVqTyIhSrlIjN:chat.lfx.linuxfoundation.org/$m88-vwWE7VELf0lz1fvQRV8MIK2zc7e4n4gD6qF-nkw?via=chat.lfx.linuxfoundation.org&via=matrix.org
All three should be fix-able by replacing the current tactile template. Is Subhro Majumder actively working on that effort, and is there an issue for it?  If so, then this issue and issue 135 should be listed as dependencies of that one.

It looks like this is related to #135 and the conversation in the chat room about Jekyll templates: https://matrix.to/#/!tUVxmZVqTyIhSrlIjN:chat.lfx.linuxfoundation.org/$m88-vwWE7VELf0lz1fvQRV8MIK2zc7e4n4gD6qF-nkw?via=chat.lfx.linuxfoundation.org&via=matrix.org
All three should be fix-able by replacing the current tactile template. Is Subhro Majumder actively working on that effort, and is there an issue for it? If so, then this issue and issue 135 should be listed as dependencies of that one.

ok will look into that :)

Hi @Abhijay007 Can I work on this Issue?

Can I work on this issue?

@03amir Take a look at the code and discussion and let me know what approach you'd like to take.

@joewxboy  We can use media query and add a custom font size for the element which is causing this issue. And there is an extra margin, we can also remove that by a media query.

Great suggestion @03amir - Which files would need to be modified to do the media query?

@johnwalicki I think it would be the cynman.css file. Can we add some new classes to the element?

@03amir OK, great. Yes, add more classes.

@johnwalicki  Can you please assign me the issue?

https://github.com/open-horizon/open-horizon.github.io/blob/master/css/cayman.css

Closed by PR #310


Start writing tests

This application needs tests, dang it. Controller tests, feature tests, integration tests, unit tests. All the tests.

Probably also add test coverage to make sure >80% of the app is covered: https://github.com/colszowka/simplecov


Fix bug in useContextBridge

The issue is that the identity of values changes everytime.
The use case was to bring the safearea values into the canvas.
Our implementation is slightly different from drei: https://github.com/pmndrs/drei/blob/cce70ae77b5151601089114259fbffab8747c8fa/src/core/useContextBridge.tsx
It is not clear to me however how the Canvas context providers get notified of value changes in the original implementation

superseded by #1281


Results of training using Functional API is different from Sequential for the same model

I implemented a model in both of sequential and API in Keras and the results are different. I appreciate if someone helps me to figure out why the training results are not the same.
Here is the sequential model:
`
# build CNN/LSTM and train it.
#
model = Sequential()

# build CNN/LSTM and train it.

model.add(TimeDistributed(Conv2D(16, (3, 3), padding='same', kernel_initializer='Orthogonal'), input_shape=(210, 22, 26, 1)))
model.add(Activation('elu'))
model.add(TimeDistributed(MaxPooling2D(pool_size=(2, 2))))
model.add(Dropout(0.2))

model.add(TimeDistributed(Conv2D(32, (3, 3), padding='same', kernel_initializer='Orthogonal')))
model.add(Activation('elu'))
model.add(TimeDistributed(MaxPooling2D(pool_size=(2, 2))))
model.add(Dropout(0.2))

model.add(TimeDistributed(Conv2D(64, (3, 3), padding='same', kernel_initializer='Orthogonal')))
model.add(Activation('elu'))
model.add(TimeDistributed(MaxPooling2D(pool_size=(2, 2))))

model.add(TimeDistributed(Flatten()))

model.add(Conv1D(16, 3, padding='same', kernel_initializer='Orthogonal'))
model.add(Activation('elu'))
model.add(MaxPooling1D(pool_size=8))

model.add(Bidirectional(LSTM(64, return_sequences=True, kernel_initializer='Orthogonal')))
model.add(Activation('elu'))
model.add(Bidirectional(LSTM(128, return_sequences=False, kernel_initializer='Orthogonal')))
model.add(Activation('elu'))
model.add(Dense(1, activation='sigmoid'))
adammgm = keras.optimizers.Adam(lr=0.0005, beta_1=0.9, beta_2=0.999, epsilon=1e-08, decay=0.0001)
model.compile(loss='mean_squared_error', optimizer=adammgm, metrics=['accuracy'])
print(model.summary())`

Here is functional API model:
`
# This returns a tensor
#
inputs = Input(shape=(210, 22, 26, 1))

# a layer instance is callable on a tensor, and returns a tensor
#
x = TimeDistributed(Conv2D(16, (3, 3), padding='same', kernel_initializer='Orthogonal'))(inputs)
x = Activation('elu')(x)
x = TimeDistributed(MaxPooling2D(pool_size=(2, 2)))(x)
x = Dropout(0.2)(x)

x = TimeDistributed(Conv2D(32, (3, 3), padding='same', kernel_initializer='Orthogonal'))(x)
x = Activation('elu')(x)
x = TimeDistributed(MaxPooling2D(pool_size=(2, 2)))(x)
x = Dropout(0.2)(x)

x = TimeDistributed(Conv2D(64, (3, 3), padding='same', kernel_initializer='Orthogonal'))(x)
x = Activation('elu')(x)
x = TimeDistributed(MaxPooling2D(pool_size=(2, 2)))(x)

x = TimeDistributed(Flatten())(x)

x = Conv1D(16, 3, padding='same', kernel_initializer='Orthogonal')(x)
x = Activation('elu')(x)
x = MaxPooling1D(pool_size=8)(x)

x = Bidirectional(LSTM(64, return_sequences=True, kernel_initializer='Orthogonal'))(x)
x = Activation('elu')(x)
x = Bidirectional(LSTM(128, return_sequences=False, kernel_initializer='Orthogonal'))(x)
x = Activation('elu')(x)

predictions = Dense(1, activation='sigmoid')(x)`

I made mistake. I ran one of them on CPU and another one on GPU. The results are the same if we run both of them on GPU.

Is it right that it makes a difference?
In my understanding it does not matter if you run it on CPU or GPU. Just the time is different.

Computations on GPU are not deterministic (order of computation does matter and it is not enforced) and CPU it can be deterministic. Hence, the discrepancy.


Wrong width in prompt

This icon has a width 2 but occupies only half width in prompt.

Seems that it falls within the "emoji" range of b240fb39f18c8ff5f21238af7ed26089f1828437.

@xiaq

still buggy.

Can you paste the symbol in the issue?

There should be a space between > and the cursor. What‘s more, the e at the end of rprompt is out of the terminal.

~/.elvish on master ◦ / ~>                                              huiyiqun@edge

If you run echo x ◦ xx, how does ◦ occupy 1 column (like x) or two (like xx)?

I mean put x ◦ xx.

This character ◦ just ocuppy two space in my terminal.

Then it is weird that it didn't use to work, because before the "fix" wcswidth would return 2 for the symbol. Hmm.

What about put x ◦x xx? How many columns does ◦ occupy then?

Before fix I run elvish in PC of my lab while currently in my laptop.

Confirmed by reporter to be terminal's bug.


What is the encoder of this model?

In this article, you said you use a pixel-level encoder, could you please tell me what is this encoder?

I think it is the default encoder from pix2struct

Yes, we have fine-tuned the pre-trained encoder from P2S.

Thanks a lot


UI/dataset page

Visual fixes for timeseries in dataset view. Fixed navigator on top. Prevented lowest timeseries from being hidden.

The scrollbar on top is not entirely on the screen on my setup:


Bot Builder for NodeJs - error in example

Hi,
I apologize if I'm reporting in the wrong place - but this had be stumble when I first tried out the code.
The example on: http://docs.botframework.com/builder/node/guides/core-concepts/#publishing-to-the-bot-connector-service
has an error in the code: it uses a textBot even though it should be using a BotConnectorBot.
The text states this correctly, however, the coding example doesn't

Thanks for the fix... I merged it :)


code coverage workflow is failing

We don't see coverage info on PRs anymore
It's possible to see the failure here https://github.com/vacp2p/nim-libp2p/actions/runs/10958882042/job/30430060780?pr=1183

The reason why coverage is failing is because we've reached the rate limit.
I recall adding a prevention measure during the CI refactor but it was disregarded. That being said, I think we would've reached the limit anyway.
The solution would be to go for a paid solution so we have a broader rate limit. Although maybe we won't hit the limit next month.

Which plan is best for me? Collapse
Developer - this plan is best for open-source projects and offers unlimited uploads or for single-user teams with small private repos and up to 250 coverage uploads per month.

Which plan is best for me? Developer - this plan is best for open-source projects and offers unlimited uploads or for single-user teams with small private repos and up to 250 coverage uploads per month.

I don't think I follow your point. If you're trying to suggest 250 should be enough, that's exactly what I implied with my "maybe we won't hit the limit next month".


Crandall - ngsQC and assemblyQC for Listeria monocytogenes - FDA ARGOS BioProject

[ ] Please complete ngsQC for the following organisms and all SRRs associated with each Biosample using the HIVE ngsQC protocol.
[ ] Please complete assemblyQC for the following genome assembly IDs
[ ] Once data is ready to be added to datasets, Check with @Jgergely11 for ngsQC and @penningtonea for assemblyQC

Organism
Bioproject
Biosample
Genome Assembly ID

Listeria monocytogenes
PRJNA231221
SAMN16357249
GCA_016728025.1

Listeria monocytogenes
PRJNA231221
SAMN03255437
GCA_001188045.2

Listeria monocytogenes
PRJNA231221
SAMN11056493
GCA_006364655.1

Listeria monocytogenes
PRJNA231221
SAMN10346771
GCA_006364035.1

Listeria monocytogenes
PRJNA231221
SAMN10163247
GCA_003812565.1

Listeria monocytogenes
PRJNA231221
SAMN10163248
GCA_003812545.1

Listeria monocytogenes
PRJNA231221
SAMN03255438
GCA_001188025.2

Listeria monocytogenes
PRJNA231221
SAMN06173364
GCA_002206565.2

Listeria monocytogenes
PRJNA231221
SAMN07312449
GCA_002557645.1

Additional QC is on hold for the time being. Moving to the backlog.

REFERENCE GENOME INFORMATION
Infraspecific name: Strain: FDAARGOS_1080
BioSample: SAMN16357249
BioProject: PRJNA231221
Reference proteome: UP000000817
Reference assembly: GCA_000196035.1
SRA files: SRR12933226, SRR12933227

@Keillyzhang and @emdelattre checking in - how's your progress? Any issues with HIVE or info we provided?

Complete


[Security] Workflow validate.yml is using vulnerable action wagoid/commitlint-github-action

The workflow validate.yml is referencing action wagoid/commitlint-github-action using references v2. However this reference is missing the commit bf83d2b35c4177779d047f464b48d9907f2c5201 which may contain fix to the some vulnerability.
The vulnerability fix that is missing by actions version could be related to:
(1) CVE fix
(2) upgrade of vulnerable dependency
(3) fix to secret leak and others.
Please consider to update the reference to the action.

Thanks for flagging this; it has been updated now!


Upgrade from 3.1.2 to 4 has broken message delivery

Environment:

Node.js Version: 17
Redis Server Version: v=6.2.3
Node Redis Version: 4.1.0
Platform: Release Linux Mint 20.3 Una 64-bit

This is a continuation from https://github.com/redis/node-redis/issues/1870 (@leibale you were working on that). We had to release with version 3.1.2 (our existing version) as we couldn't keep consumers waiting any longer. Now circling back to work out what the actual issue is in hope that we can upgrade node redis.
At this stage it's hard to tell. We're not getting any errors. We've upgraded node redis to the latest now (4.1.0), read the Changelog again, been over the v3 to v4 MIgration Guide many times and made the required changes, also in line with createClient configuration.
This is our consolidated diff between the code that works with 3.1.2 (main branch) and the upgraded code to satisfy 4.1.0 requirements (binarymist/upgrade-incl-redis branch).
The most obvious place to be focussing on is in the testerWatcher.
We have two different communication techniques from our CLI to the orchestrator (Server Sent Events (sse), and long polling (lp)). The sse appears to be working fine with the upgrade of node redis, but the lp is not.
The change you see in the get.js is only applicable to sse so I don't think there's any issue in get.js.
We have multiple Test Sessions (each relly on their specific redis channel. The first one seems to work). The changes to the orchestrator.js are unlikely to be an issue if one of the redis channels is working, which leaves our foucs to the testerWatcher... and specifically pollTesterMessages.
There is either something we've somehow missed changing with the upgrade, although I can't see this being the case as we've gone over your upgrade path a good number of times over the last few months. Or there is a bug in node redis. Either way it needs to be fixed in order for us to upgrade node redis.
A high level overview of our architecture can be seen here.
Thanks.

@binarymist what's the issue? you are getting an error? not getting messages?

No error, but only getting messages for the tls tester. In saying that, occasionally we get messages for the app tester as well. Just FYI: We currently have two testers implemented app and tls.

OK, so our changes to update the node redis client are all good? But something is broken.
Have spent about a week on this all up so far...
The three areas we narrowed down to and investigated:

Test that the callback to subscribe in the function pollTesterMessages of testerWatcher.js is being invoked for every message and channel we expect.
It seems right. Also when we have a break point on line 93 only of testerWatcher.js, that's the following code:
await nonBlockingClients[channel].rPush(redisList, message);
The Test Run seems to run fine.
This tells us that the redis pubSub channels are fine and it tells us that our messages are attempted at being rPushed onto the redis lists,
but when I inspect the nonBlockingClients[channel] (via consol.log rather than a break point) for the messages in it, many are missing.
Why is this? Point 3 answers this?
Without the break point, often we don't get any messages back to the CLI, but occasionally we do.
If we run the CLI again, we then get the messages back. I think fixing point 3 also explains this?

Test that getTesterMessages in the function pollTesterMessages of testerWatcher.js is getting the testerMessageSet's that we expect.
It's not.
Sometimes we get all the expected messages, sometimes we don't. I think that point 3 answers this?
Sometimes we get duplicate messages. Don't think point 3 answers this @leibale?

Work out why call to function getTesterMessages from pollTesterMessages of testerWatcher.js does not return correct testerMessageSet that we expect
It appears that blpop now returns an object with key and element rather than the expected and documented (https://redis.io/commands/blpop/#return) array? @leibale did we miss this change being documented somewhere?
Next: Potentially debug code in following block of getTesterMessages of testerWatcher.js:
if (curListLen > 0) {
Although I'm pretty sure this is fine

Are there other undocumented changes or possibly documented changes we've missed?
Thanks.

Would be good to get some feedback on this?

@binarymist sorry it took so long, but I was on vacation...
regarding point 3 - some commands have transformReply function that transforms the raw reply (which in some cases is hard to use/parse) into more convenient data structures. if you want to get the raw reply - use client.sendCommand directly.
In order to see what a command returns you can:

trust your IDE, it uses the built-in TypeScript declarations.
checkout the transformReply function in the command file (for example, here is the BLPOP file)
use the docs (https://redis.js.org/documentation/client/)

if you want, I would like to try and debug those bugs with you on Monday (around 12 pm NYC time)


Final resource count

I will rebase this PR content once the linting PR (#56 ) is merged, so the first three commits will disappear.
I moved the final resource count to its own function.
There were some problems with the brainstone that were fixed. For example, it didn't check the brainstone position, it only checked against constants. It didn't test if there was at least 1 power token in area 2 before seeing if the brainstone could be moved up to area 3.

I was a bit worried of the future, when taklons have an action to decide where the brainstone area will land on burn/etc. But you're right, it's nicer.

Changes done.
Thinking about it, free actions can only be taken during a player's turn. We'll probably have to move the burning power phase and conversion to credits to the final "Pass" action of a player.


Failed to open DB: Internal: Failed to open LevelDB database [FSTFirestoreClient initializeWithUser:settings:]

Describe your environment
Xcode version: Version 10.3(10G8)
Firebase Component: Firestore
Using Firebase (6.5.0)
Using FirebaseAnalytics (6.0.4)
Using FirebaseAuthInterop (1.0.0)
Using FirebaseCore (6.1.0)
Using FirebaseFirestore (1.4.2)
Using FirebaseInstanceID (4.2.2)
Describe the problem
An app on a certain device was crashed by HARD_ASSERT in this code repeatedly. I couldn't find a way to handle or recover this error except uninstalling the app once to delete persistent data.

[READ] Step 1: Are you in the right place?
  Fatal Exception: NSInternalInconsistencyException
0  (Missing)                      0x1b992698c (Missing)
1  (Missing)                      0x1b8aff9f8 (Missing)
2  (Missing)                      0x1b9830bc0 (Missing)
3  Fernsnpetals                   0x102a60180 -[FSTFirestoreClient initializeWithUser:settings:] + 1406 (string:1406)
4  Fernsnpetals                   0x102a6303c std::__1::__function::__func<-[FSTFirestoreClient initWithDatabaseInfo:settings:credentialsProvider:userExecutor:workerQueue:]::$_2, std::__1::allocator<-[FSTFirestoreClient initWithDatabaseInfo:settings:credentialsProvider:userExecutor:workerQueue:]::$_2>, void ()>::operator()() + 1406 (string:1406)
5  Fernsnpetals                   0x102a29448 firebase::firestore::util::AsyncQueue::ExecuteBlocking(std::__1::function<void ()> const&) + 921 (atomic:921)
6  Fernsnpetals                   0x102a3884c firebase::firestore::util::internal::DispatchAsync(NSObject<OS_dispatch_queue>*, std::__1::function<void ()>&&)::$_0::__invoke(void*) + 1862 (functional:1862)
7  (Missing)                      0x1b93657d4 (Missing)
8  (Missing)                      0x1b9340dec (Missing)
9  (Missing)                      0x1b934192c (Missing)
10 (Missing)                      0x1b9349e08 (Missing)
11 (Missing)                      0x1b9546114 (Missing)
12 (Missing)                      0x1b9548cd4 (Missing)

How Do i solve this Crash It happens When Firebase failed to setup DB usually i got crash for once a user

@avinashkumarmishra can you include the full symbolicated stack trace along with the exception message and repro steps? Please also share your pod versions.

Also posted on https://stackoverflow.com/q/57802098, but let's keep follow up here.

Based on the exception, there's something about the device or your app that's preventing us from creating the database that Firestore uses. The I/O error in the error message is "Operation Not Permitted", which is otherwise known as EPERM and indicates some kind of permission problem creating or opening files.
In the past we've seen such an error occur after the app was put in the background when developers set the com.apple.developer.default-data-protection entitlement to NSFileProtectionComplete (see #2846 for details).
Your case seems different because we're failing to create/open the database in the first place.
Are you doing anything that might influence filesystem permissions?

@wilhuff  No in background i am not doing anything let me show you how i am calling it from
`
func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?) -> Bool {
self.enableFirestoreData()
return true
}
private func enableFirestoreData(){
let db = Firestore.firestore()
let settings = db.settings
settings.areTimestampsInSnapshotsEnabled = true
db.settings = settings
db.collection("appconfiguration").document("cacheAPIList")
.addSnapshotListener { documentSnapshot, error in
guard let document = documentSnapshot else {
print("Error fetching document: (error!)")
return
}
guard let data = document.data() else {
print("Document data was empty.")
return
}
FNPAppUtility.saveTempCachedData(cacheDetails: data as Dictionary<String, AnyObject>)
let cacheData = FNPAppUtility.getCachedData()
if cacheData.count <= 0{
FNPAppUtility.saveCachedData(cacheDetails: data as Dictionary<String, AnyObject>)
}
}
}`
This is How I am calling It

@avinashkumarmishra Sorry to hear about your trouble!
Are you able to reproduce this on a second device or a simulator? If this is reproducible on a simulator, it would help us if you provided a small sample app. Since we don't know the exact state of your device, it will likely be difficult for us to find a root cause without a reproduction.

No I am not able to Produce it this is why I am Getting Stuck In  I got More than 1k  crash for this incidents only inside My app   and average is once per User  some time it is twice per User Please Look Into it. it is not tolerable now earlier we used to get lesser  crash on this issue

So the problem here is that we've never seen this issue before and don't know how it can happen that the filesystem is denying Firestore's request to open a database. This also doesn't seem to be widespread: nobody else is reporting this issue. Together these mean our options are pretty limited.
If you can't reproduce the issue then really the only thing we have left is to reason about what is different about your specific application or your users' devices that could cause this crash.
So these are the things to answer:

Have you changed any entitlements?
Can you think of anything else you're doing on startup before calling Firestore for the first time that might also be accessing or changing the filesystem?
Are you using anything else in your application that accesses the local filesystem?
Is there any pattern to the devices that are seeing the failures? For example:

Are they older devices?
Are they running older versions of iOS?
Are they jailbroken?
Are they 32-bit?
etc.

None of these are currently known to have this kind of problem but if you have a pool of devices that are failing this way then that might give us some avenue for investigation. Also if there's a pattern to the failures that might give us some clues as to how we might reproduce this problem.

Here I attached the craslitics Image Which Says all you Need To know

Looks like there's no clear pattern to which devices or OSes are experiencing the crash. Are you able to answer any of the other questions?

Have you changed any entitlements?
Can you think of anything else you're doing on startup before calling Firestore for the first time that might also be accessing or changing the filesystem?
Are you using anything else in your application that accesses the local filesystem?

@ChristianVinterly your case is different. Somehow you've managed to open Firestore more than once in a single process and the second one failed to open its database because the first one still had the database locked.
Normally, the Firestore SDK keeps a map of active instances so that [FIRFirestore firestore] will return the same instance. The only way I can think of that you might have encountered this is if you deleted FIRApp and then managed to create a new one and a new Firestore instance before the old one shut down.
If you're at all able to reproduce this, please create a new issue with the details of what you're doing--this is unrelated to the "Operation Not Permitted" issue going on in this discussion.

@avinashkumarmishra We haven't ever seen this happen and recent testing we've done still hasn't shown it. Yours has been the only report of this error so there's some specific about your project configuration or your application that's interfering with Firestore's startup. Without further information we can't help you figure out what this, though.

I am also seeing this error, but can't provide any other information that would be helpful other than what is provided here.


Move/copy storage volumes between projects

Resolves #8236

This pull request didn't trigger Jenkins as its author isn't in the whitelist.
An organization member must perform one of the following:

To have this branch tested by Jenkins, use the "ok to test" command.
To have a one time test done, use the "test this please" command.

Those commands are simple Github comments of the format: "jenkins: COMMAND"

Thanks for this, it's looking pretty close to what we want I think!
The bulk of my review was done comparing this to what we've already got in place for instances and the comments above are meant to reduce the differences and use the same approach whenever possible (there are a few cases where we can't).

@stgraber, maybe I missed something but it turns out that modification in lxc/storage_volumes.go is the only change which we need. It looks that UseProject is doing the whole job. I've tested this on single node and between remotes. Every copy/move request with target-project flag specified is performed as a migration (Source type equal migration value). Is it OK? Can it be so easy?

So that certainly works but it's also very wasteful.
Instead I'd expect the same behavior as for instances, so:

lxc storage volume copy foo default/abc default/def --target-project foo

Should send a StorageVolumesPost to /1.0/storage-pools/default/volumes?project=foo with a StorageVolumeSource containing:

Name: abc
Project: default
Type: copy

The main thing needed here is:

StorageVolumeSource needs a new Project field just as we added to InstanceSource
client/lxd_storage_volumes.go needs updating to detect that the source and target remote is the same but that the project differ and if so, use the new code path, just as we're doing in https://github.com/lxc/lxd/blob/master/client/lxd_instances.go#L449
doVolumeCreateOrCopy in lxd/storage_volumes.go needs updating to support copying across projects

So that LXD can perform the copy directly at the storage backend level and not have to send everything over the network to itself, duplicating the entire volume.

@stgraber, thanks for the clarification. I think I'm close to final solution regarding copying. But still not quite sure about moving volumes at the same node. We should have a way to pass info about source project to storagePoolVolumeTypePostMove but you said that we shouldn't add Project field to StorageVolumePost struct so what will be the best approach?

@presztak you're absolutely right that we'll need to do something about StorageVolumePost and InstancePost to optimize server-side move. The initial goal is parity with instances where this isn't currently possible and so they rely on server-side copy and followed by a delete operation on the original.
I'll make a note that once we have this issue resolved we should consider extending the server-side move API for both instance and volumes to allow this.

@stgraber so what we need to finish this issue? copy is ready for review. move also works but is not optimal when performed on single node.

jenkins: test this please

Looking good, thanks!


adds a health service for determining the status of the workers

This commit adds a health service which ensures that at least
one worker is active. Uses isActive() to determine if the
worker is ready. The health service runs on a seperate address.
Will return a HTTP 200 if health, HTTP 500 otherwise.
Fixes #192
Signed-off-by: Alex Price<EMAIL_ADDRESS>

Perfect. This goes into next release!

I’ll do few extra checks and fixes by myself if needed, but so far it looks great.

@wolfy-j Thanks mate! A couple of the tests seem to be intermittently failing in Travis, but not on my dev machine, so I may raise a second PR just to ensure they work properly.

Travis does not release ports immediatelly all the time, they have to be rotated between tests. This is something I need help in a long term, not code issue.

Ah makes sense. All good then.

Would you mind sharing some of your exp about Kubernetes or service confirmation in docs?

I've changed the DeadWorker test a bit. My machine managed to handle worker failure and recreated it before the health request has arrived. :) Still, I'm not sure how reliable this test since RR will try to repair workers ASAP.

Yep agree on the reliability of the test - I found it hard to find a good way to test it going unhealthy. Any suggestions?

Not sure, trying to test exceptional situations when the server is trying it's best to avoid this situation is pretty tricky.
I think slowing down clients is the most realistic scenario (wait for DB connection for example).

It's a bit "timing programming", but to be honest we are testing timing issue...


CDN mount seems to fail mounting contents if running in the background

Only tested on macOS

No longer seems to happen. Maybe this came when the CDN mount was rewritten.


How to apply post quantization on any object detectors?

Hi, I am currently working on post quantize an object detection model. I can find only resource for guiding beginners to post quantize an object classification model.
I request you to help me with a sample code such that I can learn from that.

Hi @Midhilesh29. If you look in our examples, you'll see examples for post-training quantization on various types of workloads - image classification, language model, translation and recommendation systems. Indeed, for object detection we only have sample code for pruning.
Unfortunately, we don't have the bandwidth to add an object detection quantization tutorial.
The next best thing I could offer you is to take a look specifically at the language model and/or GNMT examples, which are give as Jupyter notebook tutorials. These are presented in fairly step-by-step fashion, so they might give you a good starting point.
If you have any specific questions, you can always open another issue.


please upgrade use of crate quick-xml to v0.36, to match oxigraph

This project uses crate quick-xml v0.28.
The quick-xml project has seen a slew of bugfixes, and oxigraph has also shifted to using a newer release v0.36 in its newest release v0.4.0-alpha8.
(less of a concern for you, perhaps, but for me in packaging for Debian there is also an issue of wanting to limit the amount of concurrent versions of each project)
I am not strong at coding rust, but have tried to provide a patch:
--- a/xml/Cargo.toml
+++ b/xml/Cargo.toml
@@ -22,4 +22,4 @@
 oxilangtag = "0.1"
 oxiri = "0.2"
 rio_api = { version = "0.8", path="../api" }
-quick-xml = "0.28"
+quick-xml = ">= 0.28, <= 0.36"
--- a/xml/src/error.rs
+++ b/xml/src/error.rs
@@ -99,7 +99,7 @@
         match error.kind {
             RdfXmlErrorKind::Xml(error) => match error {
                 quick_xml::Error::Io(error) => io::Error::new(error.kind(), error),
-                quick_xml::Error::UnexpectedEof(error) => {
+                quick_xml::Error::IllFormed(error) => {
                     io::Error::new(io::ErrorKind::UnexpectedEof, error)
                 }
                 error => io::Error::new(io::ErrorKind::InvalidData, error),
--- a/xml/src/parser.rs
+++ b/xml/src/parser.rs
@@ -63,7 +63,7 @@
     /// Builds the parser from a `BufRead` implementation, and a base IRI for relative IRI resolution.
     pub fn new(reader: R, base_iri: Option<Iri<String>>) -> Self {
         let mut reader = NsReader::from_reader(reader);
-        reader.expand_empty_elements(true);
+        reader.config_mut().expand_empty_elements = true;
         Self {
             reader: RdfXmlReader {
                 reader,
@@ -79,7 +79,7 @@
     }

     /// The current byte position in the input data.
-    pub fn buffer_position(&self) -> usize {
+    pub fn buffer_position(&self) -> u64 {
         self.reader.reader.buffer_position()
     }
 }
@@ -1021,7 +1021,7 @@

     fn convert_attribute(&self, attribute: Attribute) -> Result<String, RdfXmlError> {
         Ok(attribute
-            .decode_and_unescape_value_with(&self.reader, |e| self.resolve_entity(e))?
+            .decode_and_unescape_value_with(self.reader.decoder(), |e| self.resolve_entity(e))?
             .to_string())
     }

With the patch applied, the build succeeds but one test fails:
 Running tests/roundtrip.rs (target/x86_64-unknown-linux-gnu/debug/deps/roundtrip-311d9100fcca5190)

running 1 test
test simple_roundtrip ... FAILED
failures:
---- simple_roundtrip stdout ----
Error: RdfXmlError { kind: Xml(EscapeError(UnrecognizedEntity(4..8, "quot"))) }
failures:
simple_roundtrip
test result: FAILED. 0 passed; 1 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s

I am working on packaging Atomic Server, Sophia, Manas, all still using rio_* crates, as far as I am aware (but that said, I had missed that Oxigraph had moved away from those crates - thanks for bringing it to my attention, I've corrected that just now - sp I migh be mistaken about some of the others as well.
So if not too much trouble, I would indeed appreciate your modernizing the rdf_xml crate - and while at it, it you consider them deprecated then perhaps make that explicit by mentioning it at the top of the README.md fine (and whatever cargo tagging might be relevant as well).

Done v0.8.5


Link HlSearchNear to CurSearch instead

This better matches the way search works without the plugin. For some themes they're the same, for others not (e.g. Catppuccin)
Could also potentially link the virtual text too to match.

No CurSearch in the built-in highlight group.

This is the one I'm referring to:
:h hl-CurSearch

https://github.com/vim/vim/commit/a43993897aa372159f682df37562
It's a new group in Neovim 0.8, need to wait for a while. You can link by yourself for now.


[release-v1.95] Fix etcd alerts for the virtual Garden cluster

How to categorize this PR?

/area monitoring
/kind regression
What this PR does / why we need it:
This is an automated cherry-pick of #9963
/assign @vicwicker
Fix a regression where etcd alerts for the virtual Garden cluster did not work.

/lgtm
I ran the unit tests locally and made sure they broke if I change some values. I also deployed it in the local setup and check the alert was not coming for a standalone deployment.

/approve


Object visible with a camera but invisible in the 3D World

Porting the ros_ign_gazebo_demos I found this issue. The cone is visible with the camera but it's invisible in the 3D world.

I'm compiling from source dome.
@iche033 or @chapulina any thoughts?

Not sure. The world is sensors_demo.sdf from ign-gazebo right? I just tested that world in ign-gazebo2, 3, 4 but the cone is shown in both 3d window and sensors. Is it visible for you if you just launch the world using ign instead of ros2?

I am facing the same problem in Ubuntu 18.04 after installing dome from source and launching the world with ign gazebo.
I've also tried to launch some more models and it happens exactly the same. It seems that meshes in .obj like this one will work, but .dae or .stl like this one won't.

I can't reproduce this issue using ros_ign_gazebo_demos with:

Ubuntu Focal (Docker)
Either Citadel from debs or Dome from source
Foxy from debs

Do you see any errors / warnings when running verbose?
Also, when you expand the "Construction" entity on the tree, does it show that it has a visual?

I don't see any errors or warnings related.
The Construction entity does have a visual in the tree, but I can't see any difference between visuals of the different models when using the Component Inspector.

Using this env variable fix the issue
export LC_NUMERIC="C"

can you confirm this @mcres ?

export LC_NUMERIC="C"

Ohhhh locales strike back! Nice catch!

should we need to add any reference to this issue in the installation guide or the troubleshooting sections?

I think we should be able to fix this programmatically. Were you able to pin-point the place where the locale made a difference? Is is when parsing the COLLADA files, when loading them into rendering...?


tests: fix ngx.req field count

It seems that https://github.com/openresty/stream-lua-nginx-module/pull/190 and https://github.com/openresty/meta-lua-nginx-module/pull/75 should be merged.
@doujiang24 @rainingmaster


HTM-249: Use new API/models for layer tree

Before this can be merged this PR needs to be merged: https://github.com/B3Partners/tailormap-api/pull/86

Codecov Report

Merging #74 (fad041e) into main (d7aa9f2) will increase coverage by 0.81%.
The diff coverage is 59.35%.

@@            Coverage Diff             @@
##             main      #74      +/-   ##
==========================================
+ Coverage   62.89%   63.70%   +0.81%
==========================================
  Files         102      107       +5
  Lines        2148     2254     +106
  Branches      311      352      +41
==========================================
+ Hits         1351     1436      +85
- Misses        729      748      +19
- Partials       68       70       +2

Flag
Coverage Δ

unittests
63.70% <59.35%> (+0.81%)
:arrow_up:

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

Impacted Files
Coverage Δ

...s/api/src/lib/services/tailormap-api-v1.service.ts
100.00% <ø> (ø)

...ure-info-dialog/feature-info-dialog.component.html
100.00% <ø> (ø)

...core/src/lib/components/toc/toc/toc.component.html
100.00% <ø> (ø)

...nts/tree-node-layer/tree-node-layer.component.html
100.00% <ø> (ø)

projects/core/src/lib/state/core.actions.ts
100.00% <ø> (ø)

...rc/lib/openlayers-map/open-layers-layer-manager.ts
6.36% <0.00%> (-0.05%)
:arrow_down:

...ed/src/lib/components/dialog/dialog.component.html
100.00% <ø> (ø)

.../components/tree/mock-data/tree-model.mock-data.ts
100.00% <ø> (ø)

...shared/src/lib/components/tree/tree.component.html
100.00% <ø> (ø)

projects/shared/src/lib/shared-imports.module.ts
100.00% <ø> (ø)

... and 22 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 d7aa9f2...fad041e. Read the comment docs.


Add rubocop and rspec as runtime dependencies

Repro:

gem uninstall rubocop rspec
gem install github_changelog_generator

Building native extensions.  This could take a while...
ERROR:  Error installing github_changelog_generator:
	ERROR: Failed to build gem native extension.

    current directory: /usr/local/var/rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/github_changelog_generator-1.11.0
/usr/local/var/rbenv/versions/2.2.3/bin/ruby -rubygems /usr/local/var/rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/rake-10.5.0/bin/rake RUBYARCHDIR=/usr/local/var/rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/extensions/x86_64-darwin-15/2.2.0-static/github_changelog_generator-1.11.0 RUBYLIBDIR=/usr/local/var/rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/extensions/x86_64-darwin-15/2.2.0-static/github_changelog_generator-1.11.0
rake aborted!
LoadError: cannot load such file -- rubocop/rake_task

Should fix #329

@skywinder also, yanking gems leaves them on rubygems universe for a while, so we are still failing due to it bringing in the yanked 1.11.0. How do you feel about releasing this as 1.11.1 so that gem install github_changelog_generator picks that up? gem install github_changelog_generator will still have this bug for most people until a gem > 1.11.0 is released unfortunately.

This follows on the tail of all the other things we did to mitigate issues with "Rakefile as extensions in gemspec". It had a long shadow. :+1: from me

@olleolleolle @skywinder given all this, is it possible we could be more permissive about the versions? Projects that include github_changelog_generator and have their own rspec and rubocop may want a higher major version when it comes out. Can we change ~> to >= on all the rakefile-related deps so people don't get frustrated?

Full agreement from me.

Please go ahead in this PR, should you feel like.

@olleolleolle done!

Thanks guys, will release 1.11.1 shortly!

Good luck, @skywinder!

Thanks, @jkeiser for caring and patching!

1.11.1 released


Change default Hello! document

How do I change the content of this document for all users?
I've found the WELCOME.md but the changes made to this file doesn't affect the default welcome message.

Please use yarn start in the v5.


Roadmap

Not a issue per say...
Would operator be a long term work incorporated into Kubernetes as I am seeing Apache Spark (Databrick) have a different way of working Spark on K8s.

Sorry excuse me for the brevity. I tested Apache Spark on K8s earlier using this
bin/spark-submit --master k8s://https://<IP_ADDRESS>:8443 --deploy-mode cluster --name spark-pi --class org.apache.spark.examples.SparkPi --conf spark.executor.instances=5 --conf spark.kubernetes.authenticate.driver.serviceAccountName=spark --conf spark.kubernetes.container.image=gcr.io/thbeh-kube/spark:k8s-spark-2.3 --conf spark.kubernetes.driver.pod.name=spark-pi-driver local:///opt/spark/examples/jars/spark-examples_2.11-2.3.0.jar 1000
but it looks like using SparkOperator is way much easier. So my question is there will eventually be 2 ways of running Spark on k8s and whether the SparkOperator way will be the preferred way?

Got it. The Spark Operator is the more Kubernetes idiomatic and cloud-native way of running Spark applications on Kubernetes than spark-submit. So I would say if you don't have heavy investment into tooling around spark-submit or are new to Spark on Kubernetes and would like to make Spark integrate better with the rest of your stack on Kubernetes, the operator is definitely the more idiomatic way and it offers much more than just submitting your applications to run. With that being said, however, spark-submit is definitely not going away and is still the Spark native way of submitting applications. In the long term, the operator will not semantically nor functionally diverge from spark-submit and will use it under the hood. So I wouldn't say there will be two ways. Instead, it's a matter of if you prefer a more Kubernetes idiomatic way or a Spark native way. Hope this answers your question.

Closing this and feel free to reopen if you have further questions.


charting state sustain note thing i did (kinda)

Describe your problem here.
hey @ShadowMario or @bbpanzu
i want some help with this code im doing
the sustain note's size is a little crooked
	function setupSusNote(i:Array<Dynamic>, note:Note):Note {
		var daNoteInfo = i[1];
		var daStrumTime = i[0];
		var daSus:Dynamic = i[2];
		var funnySize = Std.int(GRID_SIZE / 3);

		var height:Int = Math.floor(FlxMath.remapToRange(note.sustainLength, 0, Conductor.stepCrochet * 16, 0, (gridBG.height / gridMult))
			+ (GRID_SIZE * zoomList[curZoom])
			- GRID_SIZE / 2);
		var minHeight:Int = Std.int((GRID_SIZE * zoomList[curZoom] / 2) + GRID_SIZE / 2);
		if (height < minHeight)
			height = minHeight;
		if (height < 1)
			height = 1; // Prevents error of invalid height

		var sustainNote:Note = new Note(daStrumTime + (Conductor.stepCrochet * daSus) + Conductor.stepCrochet, daNoteInfo % 4, note, true, true);
		if (daSus != null) { // Common note
			if(!Std.isOfType(i[3], String)) //Convert old note type to new note type format
			{
				i[3] = noteTypeIntMap.get(i[3]);
			}
			if(i.length > 3 && (i[3] == null || i[3].length < 1))
			{
				i.remove(i[3]);
			}
			note.sustainLength = daSus;
			note.noteType = i[3];
		}
		sustainNote.setGraphicSize(funnySize, height);
		sustainNote.updateHitbox();
		sustainNote.x = note.x + funnySize;
		sustainNote.y = note.y + (GRID_SIZE / 2);
		sustainNote.flipY = false;

		return sustainNote;
	}

Are you modding a build from source or with Lua?
Source
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
yes but i dont remember exactly

@bbpanzu help please


Investigate adding ClojureScript support

Closed via https://github.com/eerohele/pp/commit/f07371042c601fb27ba16c02d0ebc682d76ccbbb.


Reconsider/fix Catalog related CRD resources and what we store

Created from https://github.com/rancher/rancher/issues/14322.

Discuss if we want to change the way we store catalog related CRD resources
Security check stuff that is downloaded and don't store the retrieved content 1-on-1.

Any updates on this? Would highly appreciate a solution here - looks like @StrongMonkey came up with something #16473 back in November?
It would really help if the Enable/Disable toggle of the catalog would be permanent. Currently the Library Catalog gets re-enabled everytime we restart the rancher server workload... and thus the etcd gets filled up again.

This is maybe fixed as part of rancher/rancher/issues/14322 PR (https://github.com/rancher/rancher/pull/17596), everything is now cached to disk and the icons are checked for media type. There are probably extra security checks we can do for verifying Helm tarballs.

It sounds like the caching was introduced in Rancher 2.2.


Hyprland stutters when switching to a workspace with Kitty or resizing with mouse

Hyprland Version
 System/Version info
Hyprland, built from branch  at commit d20ee312108d0e7879011cfffa3a83d06e48d29e  ().
Date: 2024-04-28
Tag: , commits: @COMMITS@

flags: (if any)

System Information:
System name: Linux
Node name: nixos
Release: 6.8.7
Version: #1-NixOS SMP PREEMPT_DYNAMIC Wed Apr 17 09:23:43 UTC 2024

GPU information:
09:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Navi 21 [Radeon RX 6800/6800 XT / 6900 XT] [1002:73bf] (rev c3) (prog-if 00 [VGA controller])

os-release: ANSI_COLOR="1;34"
BUG_REPORT_URL="https://github.com/NixOS/nixpkgs/issues"
BUILD_ID="24.05.20240427.58a1abd"
DOCUMENTATION_URL="https://nixos.org/learn.html"
HOME_URL="https://nixos.org/"
ID=nixos
IMAGE_ID=""
IMAGE_VERSION=""
LOGO="nix-snowflake"
NAME=NixOS
PRETTY_NAME="NixOS 24.05 (Uakari)"
SUPPORT_URL="https://nixos.org/community.html"
VERSION="24.05 (Uakari)"
VERSION_CODENAME=uakari
VERSION_ID="24.05"

plugins:
  hyprsplit by shezdy ver 1.0

Bug or Regression?
Bug
Description
When you switch workspaces to a work space with a Kitty window open the animation will stutter slightly, when switching to a workspace without a Kitty window it is perfectly smooth. Also, if you resize a Kitty window next to another window with the mouse it will cause the desktop to lock up randomly until the Kitty window crashes
How to reproduce

Open a Kitty (native Wayland) window
Switch workspace
Open another window that isn't Kitty e.g. Firefox (native Wayland)
Switch between them rapidly
Observe the slight stutter

Crash reports, logs, images, videos
It isn't noticeable at 60Hz so I have recorded with my phone using slow motion, it still isn't very noticeable. But if you look closely it appears to skip a few frames when switching to Firefox to Kitty unlike what I showed at the beginning of the video which is me switching between Firefox (native Wayland) and Prism launcher which is QT (native Wayland)
https://github.com/hyprwm/Hyprland/assets/45698918/1a3e8782-86c8-4f34-9034-ca4a3e46b188
The other likely related issue is very noticeable on recording so I used a screen recording
https://github.com/hyprwm/Hyprland/assets/45698918/31e54108-d012-4aa8-ade8-f0d15c1b4fd5
Here it errors out with
[3.455] [glfw error 65544]: Wayland: fatal display error: Broken pipe

Seems fixed now whatever it was


Automatically detect new Robot Framework version

If there is new version of Robot Framework released, open new issue in Robocop with title "Check compatibility with Robot Framework X" (X = version) or similar. Link to release notes in content of issue.
This will allow us to detect new version and prepare Robocop for them.
It's up to discussion if we should detect official versions (such as 4.1.1) or release candidates (4.1.1rc1) so we have extra time before release go live.

Since this task doesn't require extensive knowledge about our codebase - it's just providing way of quering/callbacks when there is new version of Robot Framework and then optionally creating issue in our project - I will set 'good first issue' label.
RF release notes are located there:
https://github.com/robotframework/robotframework/tree/master/doc/releasenotes

I would like to work on this issue

I would like to work on this issue

Let Me know if you need any extra information. Testing could be tricky (since it depends on release of particular package, in this case robot Framework). But I could create demo Python package that could be released on demand with incremented version and then we could switch from demo to robotframework when everything is ready.
What I have in mind would be for example github action triggerred on schedule (ie daily) and checking package version and if its new, create the issue. If you have other ideas then of course you can try it instead

well I was thinking something like: dependabot
see demo: https://github.com/MalikMlitat/demo/blob/main/.github/dependabot.yml
dependabot.yml checks (daily) via pip the newest version of robotframework and creates automatically  a pull-request :)
https://github.com/MalikMlitat/demo/pulls
see also: https://github.com/MalikMlitat/demo/network/updates
what do you think? should I go for it?

That's good idea - didn't thought about using dependabot but it will be perfect (and with PR it will run our tests on new version so even better).
We don't want to update our official dependencies (let them stay at robotframework>=3.2.2) but we should update dependencies used for testing. See there for our github action: https://github.com/MarketSquare/robotframework-robocop/blob/master/.github/workflows/unit-tests.yml
We're using matrix with previous major version (only 3.2.2 for now) and then most recent one. We would need to change the logic here and move packages to separate requirements file (in separate directories and only for robotframework for now so dependabot will not pick up anything extra).
For example we could create stable3 (for robotframework=3.2.2) and recent (with recent robotframework version) directories, both with requirements.txt file. Then in https://github.com/MarketSquare/robotframework-robocop/blob/master/.github/workflows/unit-tests.yml :
(...)
        include:
          - os: 'ubuntu-latest'
            python-version: 3.6
            rf-version: 'stable3'
          - os: 'windows-latest'
            python-version: 3.9
            rf-version: 'recent'
          - os: 'ubuntu-latest'
            python-version: 3.7
            rf-version: 'recent'
(...)
      run: |
        python -m pip install --upgrade pip
        pip install -r {{ matrix.rf-version }}/requirements.txt
(...)

(and like always, it's proposal and I welcome better ideas)

@bhirsz thank you for the suggestion, since you have this matrix configuration, made it easy to adapt :
https://github.com/MalikMlitat/robotframework-robocop/commit/bcc060ec5fa3f2f6aa5c875a3abd72e6cb0aeb7e
but I could'nt verify that tests still running, dependabot works fine and detected the new version and created new PR

@bhirsz thank you for the suggestion, since you have this matrix configuration, made it easy to adapt : MalikMlitat@bcc060e but I could'nt verify that tests still running, dependabot works fine and detected the new version and created new PR

I saw PR - nicely done. There is typo (also in my example above with missing $) but it should be easy to fix. Unfortunately github action limits checks for first time contributors and we need to approve workflows for first PRs - later PRs will have automatically triggered builds.


Remove the unmaintained Batect in favor of using a GitHub action container

Please ensure that your pull request adheres to our contribution guidelines. Thank you!

I've split out the first three commits to https://github.com/oss-review-toolkit/ort/pull/7894 in case we want to discuss the last two commits of this PR further.

@heliocastro please don't force-push to branches owned by others without discussing this first! Not even if it's a simple rebase.

@heliocastro please don't force-push to branches owned by others without discussing this first! Not even if it's a simple rebase.

Sorry for that. I didn't think that would be an issue.

I didn't think that would be an issue.

It breaks my checks which of my local branches are not in-sync with the remotes.

As discussed on Slack I am approving that now despite my concerns as @heliocastro committed to making another PR that runs the functional tests with an image that matches the PR again.


Error during deploy of  BC Standard from ARM template

When using aka.ms/getbc we get an error at the end of the deployment.
We tested this with a couple of different scenario's.

Standard with aka.ms/getbc
From a release pipeline using the ARM templates
And creating a new container on a new environment with SetupNAVContainer.ps1

All result in the same error.
3:08:03 PM at , C:\demo\setupVm.ps1: line 384
3:08:03 PM at , C:\demo\SetupNavContainer.ps1: line 422
3:08:03 PM at Publish-BcContainerApp, C:\Program Files\WindowsPowerShell\Modules\bccontainerhelper\4.0.6\AppHandling\Publish-NavContainerApp.ps1: line 144
3:08:03 PM at , C:\Program Files\WindowsPowerShell\Modules\bccontainerhelper\4.0.6\AppHandling\Publish-NavContainerApp.ps1: line 293
3:08:03 PM at Invoke-ScriptInBcContainer, C:\Program Files\WindowsPowerShell\Modules\bccontainerhelper\4.0.6\ContainerHandling\Invoke-ScriptInNavContainer.ps1: line 112
3:08:03 PM The tenant 'default' is not accessible, because it is in state Mounting.
2:49:38 PM Running container (this might take some time)
2:49:38 PM Locale nl-NL
2:49:38 PM Version 21.1.48363.49129
2:49:38 PM Country nl
When investigating this issue, we found out the the problem is in the SetupNAVContainer.ps1.
On the Publish-NavContainerApp. If we addd a start-sleep before the publish-navcontainerapp it will continue without an error.

settings.txt

This was fixed shortly after


[Feature Request] Retro OS support

Kind of a strange request, I know, but I think it would be neat if there was support for building for Windows 9x. It would most definitely require that the game use the old fashioned MiniGL/OpenGL 1.x implementations from back in the day as well as targeting old architecture, likely i586. Then we could have a period-accurate PC port to play around with alongside the original PC port of Turok.

I definitely want to drop the GL requirement to 2.1 with optional extensions, since there's not many reasons why the game requires GL3+.
 Maybe someday.


Coming soon

Add future plans to make phone number or email unique, as requested in previous pr.
Do let me know if I can make it look more visually appealing!

Shift new features to coming soon section as requested :)

Ok conflicts should be resolved :)

Ok conflicts should be resolved :)


tsdb: remove duplicate values set to reduce memory usage(map overhead)

When we have millions of series, the values map will consume a lot of memory, the overhead comes from golang's map.
We have found out the MemPostings.m is the superset of values map, and they both protected by head.symMtx, it seems to have no side effects if we remove values map.
@codesome, @krasi-georgiev, @bwplotka

also could you have a look if there is a bench test that can show the difference in the memory usage and run it with funcbench
https://github.com/prometheus/test-infra/tree/master/funcbench

@krasi-georgiev  I can't find such a bench test, but I think we can use the following test case:
package main

import (
	"strconv"
	"testing"
)

var kvs = map[string]string{}

func init() {
	for i := 0; i < 1000000; i++ {
		s := strconv.Itoa(i)
		kvs[s] = s
	}
}

func BenchmarkX(b *testing.B) {
	for i := 0; i < b.N; i++ {
		valuesmap := map[string]map[string]struct{}{}
		for k, v := range kvs {
			values, ok := valuesmap[k]
			if !ok {
				values = map[string]struct{}{}
				valuesmap[k] = values
			}
			values[v] = struct{}{}
		}
	}
}

go version go1.14.3 darwin/amd64

BenchmarkX-12                  2         682587608 ns/op        315833308 B/op   2038232 allocs/op

I don't expect much difference in memory consumption as I see the string was shared between the removed map and the postings.

@codesome you are right, but the map overhead cloud be very large if we have millions of labels, our profiling results show the memory usage of the map could up to ~500MB. (the above benchmark has ignored those strings)

Let's get this merged this after fixing the reviews :muscle:

the map overhead cloud be very large if we have millions of labels, our profiling results show the memory usage of the map could up to ~500MB

That doesn't sound right, the overhead of a Go map is about 11 bytes per entry at the margin. How do you have tens of millions of label names? Even an extreme case should have no more than a few hundred.

I am new to this area, maybe I set up my testing environment in the wrong way, but a few hundred seems too little to me since users can use whatever label names they want.

There could be tens of millions of label values (in a benchmark at least)


Filter Azure computes

Filter computes in the Azure Attach Dialog.
The following SKUs will fail for our current image models (or are close).
Small GPU SKUs:

Standard_NC6 12GB RAM
Standard_NV6 8GB RAM
Standard_NV12s_v3 8GB RAM
Standard_NV4as_v4 2GB RAM
Standard_NV8as_v4 4GB RAM
Standard_NV16as_v4 8GB RAM

[Yesterday 2:08 PM] Justin Ormont
If you have access to details of each compute target, you can filter dynamically by removing (vm.gpuMemory <= 14GB)

STANDARD_NV6 is still showing up in the list.

User program failed with RuntimeError: CUDA out of memory. Tried to allocate 124.00 MiB (GPU 0; 7.94 GiB total capacity; 7.38 GiB already allocated; 61.00 MiB free; 54.97 MiB cached)


Reduced ops build as part of ORT is broken if not using an external repo for extensions

The extensions source is not available until cmake runs and populates it here:
https://github.com/microsoft/onnxruntime/blob/096307c64b789354e2c20e915e918e66d911dd3e/cmake/external/extensions.cmake#L40-L52
Due to that, gen_selectedops.py will fail as it requires the extensions source to exist, but we're attempting to run it when setting up the arguments to call cmake.
https://github.com/microsoft/onnxruntime/blob/096307c64b789354e2c20e915e918e66d911dd3e/tools/ci_build/build.py#L1335-L1340

Directly download this gen_selectedops.py from github, instead of cmake doing that? This script has been decoupled from any other content in ort-extensions since day 1.


Unable to access account data.

I am unable to access acount data currently, the market data endpoints are functioning as expected.
It was working for me earlier this week. Possible Schwab made some changes on their end.
logs:
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): api.schwabapi.com:443
DEBUG:urllib3.connectionpool:https://api.schwabapi.com:443 "POST /v1/oauth/token HTTP/11" 200 705
INFO:schwab_client:Schwab client initialized
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): api.schwabapi.com:443
DEBUG:urllib3.connectionpool:https://api.schwabapi.com:443 "GET /trader/v1/accounts/accountNumbers HTTP/11" 404 94
ERROR:schwab_client:Failed to retrieve linked accounts. Status code: 404
ERROR:schwab_client:Response content: 404 Not Found: Requested route ('traderapi-accounts.apigx-origin.schwab.com') does not exist.
ERROR:schwab_order_manager:Failed to retrieve linked accounts.
Traceback (most recent call last):
File "d:\CodeProjects\SchwabDashboard\main.py", line 121, in
asyncio.run(main())
File "C:\Users\GARRE.conda\envs\openbb_env\Lib\asyncio\runners.py", line 190, in run
return runner.run(main)
^^^^^^^^^^^^^^^^
File "C:\Users\GARRE.conda\envs\openbb_env\Lib\asyncio\runners.py", line 118, in run
return self._loop.run_until_complete(task)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\GARRE.conda\envs\openbb_env\Lib\asyncio\base_events.py", line 654, in run_until_complete
return future.result()
^^^^^^^^^^^^^^^
File "d:\CodeProjects\SchwabDashboard\main.py", line 24, in main
await order_manager.initialize()
File "d:\CodeProjects\SchwabDashboard\order_manager.py", line 18, in initialize
self.account_hash = await self.get_account_hash()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "d:\CodeProjects\SchwabDashboard\order_manager.py", line 42, in get_account_hash
raise Exception("Failed to retrieve linked accounts.")
Exception: Failed to retrieve linked accounts.

Around 11pm est last night the api was down (probably for some maintenence). As you can see "404 Not Found: Requested route ('traderapi-accounts.apigx-origin.schwab.com') does not exist."
It is now working.


⚠ Bofrost.com has degraded performance

In e339a21, Bofrost.com (https://www.bofrost.com) experienced degraded performance:

HTTP code: 200
Response time: 1022 ms

Resolved: Bofrost.com performance has improved in 986e471.


Better support for exams without grade

State labels for exams without grade (using common abbreviations):

AN (angemeldet) for registered exams
BE (bestanden) for passed exams
NB (nicht bestanden) for failed exams
EN (entgültig nicht bestanden) for permanently failed exams

Grades in overview coloured (optional)

Hey @eltos,
thank you for your pull request! I like the idea and I'm quite sure we are going to merge this. I quickly skimmed through the implementation and it also looks good.
There's only a minor thing I would like to change. It's possible that some people don't like the colors, so a setting where you could toggle them would be nice. One single on/off switch for all of them would be sufficient I guess. The color codes could be on as a default. If you want I can implement the setting, but feel free if you want to do it. ;)
We're quite busy at the moment so please give us some time to properly test, merge and publish it. I suppose it may take at least another month.
Cheers. :)

Thanks for the fast response.
An option to disable the colors is quickly done - I'll push a commit shortly ;)

Thanks for the quick patch @eltos! Due to our incredibly slow internet service providers, I still have no internet connection at home to test this and publish a new version, so I'm afraid it will take another couple of weeks.

Hey there,
this is a friendly reminder that this request has now been open for over four months.
Will there be a new release anytime soon?
Cheers

Hi @eltos,
my apologies for being so slow. It took my internet provider 2.5 months to provide me an internet connection, luckily that is resolved since the beginning of this year, so that excuse is now invalid. As I am not a student anymore, I am currently waiting for a friend to provide me temporary access to his account, so I can test and merge this. I actually set up Android Studio yesterday. ;)
I hope it will not take longer then another week.
Cheers.

I have successfully tested it with my personal student account before opening the merge request (which I think is needless to say) and been using my "debug"-version since. But I can understand that you want to test it yourself before publishing.
Thank's for your effort

Hi,
I just published a new version 1.2.1 to the Play Store. It should be available in a couple of hours. Thanks again for the pull request and sorry for the long delay!
Cheers :)


feat(ExploreBy): fix and add missing tracking

This PR resolves DIA-863
Description
Fixes home view tracking and add missing pieces of tracking to the Explore By and Discover Something New.
PR Checklist

[x] I have tested my changes on iOS and Android.
[x] I hid my changes behind a feature flag, or they don't need one.
[x] I have included screenshots or videos, or I have not changed the UI.
[x] I have added tests, or my changes don't require any.
[x] I added an app state migration, or my changes do not require one.
[x] I have documented any follow-up work that this PR will require, or it does not require any.
[x] I have added a changelog entry below, or my changes do not require one.

To the reviewers 👀

[ ] I would like at least one of the reviewers to run this PR on the simulator or device.

Changelog updates
Changelog updates

Cross-platform user-facing changes

feat: fixes home view tracking and add missing pieces on Discover/Explore sections

iOS user-facing changes

Android user-facing changes

Dev changes

Need help with something? Have a look at our docs, or get in touch with us.

This PR contains the following changes:

Cross-platform user-facing changes (feat: fixes home view tracking and add missing pieces on Discover/Explore sections - araujobarret)

  Generated by :no_entry_sign: dangerJS against b61f5c779939ef8f99700a4d38dcba12082e3b14


pythonPackages.apprise: 0.8.9 -> 0.9.0

Motivation for this change
https://github.com/caronc/apprise/releases/tag/v0.9.0
Things done

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

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

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 108758 run on x86_64-linux 1

3 packages built:

apprise (python38Packages.apprise)
python37Packages.apprise
python39Packages.apprise

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 108758 run on x86_64-linux 1

3 packages built:

apprise (python38Packages.apprise)
python37Packages.apprise
python39Packages.apprise

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 108758 run on x86_64-darwin 1

3 packages built:

apprise (python38Packages.apprise)
python37Packages.apprise
python39Packages.apprise

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 108758 run on x86_64-darwin 1

3 packages built:

apprise (python38Packages.apprise)
python37Packages.apprise
python39Packages.apprise