Push messaging not processed unless application is in foreground

I have the following behavior with TextSecure, using the push messaging implementation from this project: TextSecure only seems to "notice" new messages when it is in foreground, on the screen.
For example, I had my phone in stand-by for a while, and I now know that I did receive some messages during that time. I then turned on the screen and unlocked the phone. I waited for ~10-20sec, nothing happened. I started TextSecure, and now I got all the notifications about the messages that I received.

@mar-v-in Here you go, the bug report I promised ;-)

I assume a log is needed here.
Btw., see the last comments/reports in https://github.com/WhisperSystems/TextSecure/issues/970

I just received some messages while the phone was in standby, so this is not entirely reproducible either. The bug above happened while being on a highway, so maybe it is related to unreliable data connection. Still, once the device re-gains connectivity, it should get the messages and notify me.
Now, with other TextSecure messages having the same problem, maybe TextSecure is doing something suboptimal (I have no idea what they could do wrong), or maybe the Google implementation has its troubles as well.

Textsecure uses the push message for a wakeup event and notification. Getting the message only when textsecure is in foreground could mean that microg has disconnected from the gms server, I experience the same issue.
You should check your logcat if the heartbeat still occurs:
08-20 23:08:17.641 D/GmsGcmMcsSvc(5851): Incoming message: HeartbeatAck{last_stream_id_received=7}

You can also check push functionality with a small app from play store called push notification tester

You should check your logcat if the heartbeat still occurs:
08-20 23:08:17.641 D/GmsGcmMcsSvc(5851): Incoming message: HeartbeatAck{last_stream_id_received=7}

I can try that; is there a way to get the logs from the time when adb is
not connected? This often happens while I'm traveling, so I don't have
the phone attached to a laptop.

You can also check push functionality with a small app from play store called push notification tester

I don't have play store. (Otherwise, why would I even be interested in
this project ;-) ). Is there a similar app in F-Droid? I couldn't find any.

Try this one: https://f-droid.org/repository/browse/?fdfilter=catlog&fdid=com.nolanlawson.logcat

Great, that seems to work. Next time I get delayed TextSecure messages, I'll check the logs. After some more days of experience I have to say though that often, messages do arrive on time, so I'm no longer sure this issue is actually in GMS rather than in TextSecure.

I have the same problem with the newest TextSecure version released. I tried to build the newest version of android_packages_apps_GmsCore because I have hoped to fix this, but now I'm reading this issue and am not sure...
My girlfriend has the same setting, and the same error on a different device while my friends with official google-services don't have these issue in TextSecure... And Redphone doesn't show me to other Redphone-Users although I should have push-massages know...
I will check the logcat an report back...

Ok, I used the Xposed-Module "FakeGapps" but I realized that I don't need it, because I have OmniRom installed. So I uninstalled it and restarted, know everything works fine...
Except  an error in the logcat:
W/GCMRegistrarHelper(6156): GCM Not supported: java.lang.UnsupportedOperationExeption: Device does not have package com.google.android.gsf

And I could not test Redphone jet.

Can you try to use https://github.com/microg/android_packages_apps_GsfProxy ?

Ok, now I get no error or warning at all. Thank you!

After a few days (1.5 - 2) I have this problem again. The gcm haertbeat masseges in the logcat are not present then, too. After I restart the phone, everything gets back to normal.

Can you provide a full log (maybe including the period where it was still working until it failed)?

It was gone, but now it came back:
09-22 09:30:00.625 D/GmsGcmMcsSvc(2471): Heartbeat initiated, reason: Intent { act=org.microg.gms.gcm.mcs.HEARTBEAT flg=0x4 cmp=com.google.android.gms/org.microg.gms.gcm.McsService (has extras) }
09-22 09:30:00.625 D/GmsGcmMcsSvc(2471): Outgoing message: HeartbeatPing{last_stream_id_received=225}
09-22 09:30:01.170 D/GmsGcmMcsSvc(2471): Incoming message: HeartbeatAck{last_stream_id_received=225}
09-22 09:31:01.960 D/GmsGcmMcsSvc(2471): Heartbeat initiated, reason: Intent { act=org.microg.gms.gcm.mcs.HEARTBEAT flg=0x4 cmp=com.google.android.gms/org.microg.gms.gcm.McsService (has extras) }
09-22 09:31:01.960 D/GmsGcmMcsSvc(2471): Outgoing message: HeartbeatPing{last_stream_id_received=226}
09-22 09:31:02.130 D/GmsGcmMcsSvc(2471): Incoming message: HeartbeatAck{last_stream_id_received=226}
09-22 09:32:01.940 D/GmsGcmMcsSvc(2471): Heartbeat initiated, reason: Intent { act=org.microg.gms.gcm.mcs.HEARTBEAT flg=0x4 cmp=com.google.android.gms/org.microg.gms.gcm.McsService (has extras) }
09-22 09:32:01.945 D/GmsGcmMcsSvc(2471): Outgoing message: HeartbeatPing{last_stream_id_received=227}
09-22 09:32:02.090 D/GmsGcmMcsSvc(2471): Incoming message: HeartbeatAck{last_stream_id_received=227}
09-22 09:33:02.000 D/GmsGcmMcsSvc(2471): Heartbeat initiated, reason: Intent { act=org.microg.gms.gcm.mcs.HEARTBEAT flg=0x4 cmp=com.google.android.gms/org.microg.gms.gcm.McsService (has extras) }
09-22 09:33:02.005 D/GmsGcmMcsSvc(2471): Outgoing message: HeartbeatPing{last_stream_id_received=228}
09-22 09:33:02.460 D/GmsGcmMcsSvc(2471): Incoming message: HeartbeatAck{last_stream_id_received=228}
09-22 09:34:01.950 D/GmsGcmMcsSvc(2471): Heartbeat initiated, reason: Intent { act=org.microg.gms.gcm.mcs.HEARTBEAT flg=0x4 cmp=com.google.android.gms/org.microg.gms.gcm.McsService (has extras) }
09-22 09:34:01.950 D/GmsGcmMcsSvc(2471): Outgoing message: HeartbeatPing{last_stream_id_received=229}
09-22 09:34:02.390 D/GmsGcmMcsSvc(2471): Incoming message: HeartbeatAck{last_stream_id_received=229}
09-22 09:35:02.065 D/GmsGcmMcsSvc(2471): Heartbeat initiated, reason: Intent { act=org.microg.gms.gcm.mcs.HEARTBEAT flg=0x4 cmp=com.google.android.gms/org.microg.gms.gcm.McsService (has extras) }
09-22 09:35:02.065 D/GmsGcmMcsSvc(2471): Outgoing message: HeartbeatPing{last_stream_id_received=230}
09-22 09:35:02.320 D/GmsGcmMcsSvc(2471): Incoming message: HeartbeatAck{last_stream_id_received=230}
09-22 09:36:02.035 D/GmsGcmMcsSvc(2471): Heartbeat initiated, reason: Intent { act=org.microg.gms.gcm.mcs.HEARTBEAT flg=0x4 cmp=com.google.android.gms/org.microg.gms.gcm.McsService (has extras) }
09-22 09:36:02.035 D/GmsGcmMcsSvc(2471): Outgoing message: HeartbeatPing{last_stream_id_received=231}
09-22 09:36:02.260 D/GmsGcmMcsSvc(2471): Incoming message: HeartbeatAck{last_stream_id_received=231}
09-22 09:37:01.965 D/GmsGcmMcsSvc(2471): Heartbeat initiated, reason: Intent { act=org.microg.gms.gcm.mcs.HEARTBEAT flg=0x4 cmp=com.google.android.gms/org.microg.gms.gcm.McsService (has extras) }
09-22 09:37:01.970 D/GmsGcmMcsSvc(2471): Outgoing message: HeartbeatPing{last_stream_id_received=232}
09-22 09:37:02.125 D/GmsGcmMcsSvc(2471): Incoming message: HeartbeatAck{last_stream_id_received=232}
09-22 09:38:02.030 D/GmsGcmMcsSvc(2471): Heartbeat initiated, reason: Intent { act=org.microg.gms.gcm.mcs.HEARTBEAT flg=0x4 cmp=com.google.android.gms/org.microg.gms.gcm.McsService (has extras) }
09-22 09:38:02.055 D/GmsGcmMcsSvc(2471): Outgoing message: HeartbeatPing{last_stream_id_received=233}
09-22 09:38:02.600 D/GmsGcmMcsSvc(2471): Incoming message: HeartbeatAck{last_stream_id_received=233}
09-22 09:39:01.955 D/GmsGcmMcsSvc(2471): Heartbeat initiated, reason: Intent { act=org.microg.gms.gcm.mcs.HEARTBEAT flg=0x4 cmp=com.google.android.gms/org.microg.gms.gcm.McsService (has extras) }
09-22 09:39:01.955 D/GmsGcmMcsSvc(2471): Outgoing message: HeartbeatPing{last_stream_id_received=234}
09-22 09:39:02.250 D/GmsGcmMcsSvc(2471): Incoming message: HeartbeatAck{last_stream_id_received=234}
09-22 09:40:01.970 D/GmsGcmMcsSvc(2471): Heartbeat initiated, reason: Intent { act=org.microg.gms.gcm.mcs.HEARTBEAT flg=0x4 cmp=com.google.android.gms/org.microg.gms.gcm.McsService (has extras) }
09-22 09:40:01.970 D/GmsGcmMcsSvc(2471): Outgoing message: HeartbeatPing{last_stream_id_received=235}
09-22 09:40:02.160 D/GmsGcmMcsSvc(2471): Incoming message: HeartbeatAck{last_stream_id_received=235}
09-22 09:41:01.960 D/GmsGcmMcsSvc(2471): Heartbeat initiated, reason: Intent { act=org.microg.gms.gcm.mcs.HEARTBEAT flg=0x4 cmp=com.google.android.gms/org.microg.gms.gcm.McsService (has extras) }
09-22 09:41:01.960 D/GmsGcmMcsSvc(2471): Outgoing message: HeartbeatPing{last_stream_id_received=236}
09-22 09:41:02.345 D/GmsGcmMcsSvc(2471): Incoming message: HeartbeatAck{last_stream_id_received=236}
09-22 09:42:01.950 D/GmsGcmMcsSvc(2471): Heartbeat initiated, reason: Intent { act=org.microg.gms.gcm.mcs.HEARTBEAT flg=0x4 cmp=com.google.android.gms/org.microg.gms.gcm.McsService (has extras) }
09-22 09:42:01.950 D/GmsGcmMcsSvc(2471): Outgoing message: HeartbeatPing{last_stream_id_received=237}
09-22 09:42:02.330 D/GmsGcmMcsSvc(2471): Incoming message: HeartbeatAck{last_stream_id_received=237}
09-22 09:43:01.950 D/GmsGcmMcsSvc(2471): Heartbeat initiated, reason: Intent { act=org.microg.gms.gcm.mcs.HEARTBEAT flg=0x4 cmp=com.google.android.gms/org.microg.gms.gcm.McsService (has extras) }
09-22 09:43:01.950 D/GmsGcmMcsSvc(2471): Outgoing message: HeartbeatPing{last_stream_id_received=238}
09-22 09:43:02.100 D/GmsGcmMcsSvc(2471): Incoming message: HeartbeatAck{last_stream_id_received=238}
09-22 09:44:02.040 D/GmsGcmMcsSvc(2471): Heartbeat initiated, reason: Intent { act=org.microg.gms.gcm.mcs.HEARTBEAT flg=0x4 cmp=com.google.android.gms/org.microg.gms.gcm.McsService (has extras) }
09-22 09:44:02.065 D/GmsGcmMcsSvc(2471): Outgoing message: HeartbeatPing{last_stream_id_received=239}
09-22 09:44:02.220 D/GmsGcmMcsSvc(2471): Incoming message: HeartbeatAck{last_stream_id_received=239}
09-22 09:45:01.105 D/GmsGcmMcsSvc(2471): Heartbeat initiated, reason: Intent { act=org.microg.gms.gcm.mcs.HEARTBEAT flg=0x4 cmp=com.google.android.gms/org.microg.gms.gcm.McsService (has extras) }
09-22 09:45:01.105 D/GmsGcmMcsSvc(2471): Outgoing message: HeartbeatPing{last_stream_id_received=240}
09-22 09:45:01.260 D/GmsGcmMcsSvc(2471): Incoming message: HeartbeatAck{last_stream_id_received=240}
09-22 09:46:01.895 D/GmsGcmMcsSvc(2471): Heartbeat initiated, reason: Intent { act=org.microg.gms.gcm.mcs.HEARTBEAT flg=0x4 cmp=com.google.android.gms/org.microg.gms.gcm.McsService (has extras) }
09-22 09:46:01.895 D/GmsGcmMcsSvc(2471): Outgoing message: HeartbeatPing{last_stream_id_received=241}
09-22 09:46:05.655 D/GmsGcmMcsSvc(2471): Incoming message: HeartbeatAck{last_stream_id_received=241}
09-22 09:46:10.645 D/GmsGcmMcsSvc(2471): I/O error: javax.net.ssl.SSLException: Read error: ssl=0x52d597c0: I/O error during system call, Connection timed out
09-22 09:46:10.645 D/GmsGcmMcsSvc(2471): Teardown initiated, reason: javax.net.ssl.SSLException: Read error: ssl=0x52d597c0: I/O error during system call, Connection timed out
09-22 09:46:11.235 D/GmsGcmTrigger(2471): Ignoring Intent { act=org.microg.gms.gcm.RECONNECT flg=0x10 cmp=com.google.android.gms/org.microg.gms.gcm.TriggerReceiver }: network is offline
09-22 09:46:14.075 D/GmsGcmMcsSvc(2471): Connect initiated, reason: Intent { act=org.microg.gms.gcm.mcs.CONNECT cmp=com.google.android.gms/org.microg.gms.gcm.McsService (has extras) }
09-22 09:46:14.075 D/GmsGcmMcsSvc(2471): Starting MCS connection...
09-22 09:46:14.200 W/GmsGcmMcsSvc(2471): Exception while connecting!
09-22 09:46:14.200 D/GmsGcmMcsSvc(2471): Teardown initiated, reason: java.net.UnknownHostException: Unable to resolve host "mtalk.google.com": No address associated with hostname
09-22 09:46:26.650 D/GmsGcmMcsSvc(2471): Connect initiated, reason: Intent { act=org.microg.gms.gcm.mcs.CONNECT cmp=com.google.android.gms/org.microg.gms.gcm.McsService (has extras) }
09-22 09:46:26.650 D/GmsGcmMcsSvc(2471): Starting MCS connection...
09-22 09:46:26.765 W/GmsGcmMcsSvc(2471): Exception while connecting!
09-22 09:46:26.765 D/GmsGcmMcsSvc(2471): Teardown initiated, reason: java.net.UnknownHostException: Unable to resolve host "mtalk.google.com": No address associated with hostname
09-22 09:46:27.700 D/GmsGcmMcsSvc(2471): Connect initiated, reason: Intent { act=org.microg.gms.gcm.mcs.CONNECT cmp=com.google.android.gms/org.microg.gms.gcm.McsService (has extras) }
09-22 09:46:27.700 D/GmsGcmMcsSvc(2471): Starting MCS connection...
09-22 09:46:27.705 W/GmsGcmMcsSvc(2471): Exception while connecting!
09-22 09:46:27.705 D/GmsGcmMcsSvc(2471): Teardown initiated, reason: java.net.UnknownHostException: Unable to resolve host "mtalk.google.com": No address associated with hostname
09-22 09:46:27.710 I/ActivityManager(2253): Delay finish: com.google.android.gms/org.microg.gms.gcm.TriggerReceiver
09-22 14:54:51.055 W/ActivityManager(2253): Scheduling restart of crashed service org.thoughtcrime.redphone/.gcm.GCMRegistrationService in 1000ms
09-22 14:54:52.280 I/ActivityManager(2253): Start proc org.thoughtcrime.redphone for service org.thoughtcrime.redphone/.gcm.GCMRegistrationService: pid=27892 uid=10196 gids={50196, 1028, 1015, 1023, 3003, 3002}

is it possible that at this point the internet connection was lost? Were you connected via mobile internet or WiFi?

I think it could be a problem with my DNS. I was connected via wifi. But it did not reconnect

Hey there,
it works for long times for me with 5.1.1, thats why I did not comment for long time, but I put on the airplane mode last night and when I put it off gcm did not reconnect. So the problem seems to be that it does not reconnect if there is no internet access for too long.

I can confirm the issue with flight mode. I guess my wish concerning "reconnect on connectivity change" would solve this problem as well.

Oh, so this is the issue I'm experiencing! I've described it in #23. Tested with Push Notifications tester. Sometimes it wont receive push messages, so I restart my phone and the messages arrive immediately. Now I know why. I've set wifi sleep policy to off, so when my phone is in deep sleep, wifi is off. This obviously affects microG.

This issue should be mostly done with 766a6a1. For nightly/git users: if problems persist, please report back here.

After the installation of GsfProxy, Threema crashes when it receives a c2dm.intent.RECEIVE, i.e. a notification by GmsCore. The main difference after the installation of GsfProxy seems that Threema is no longer permanently running in the background: its messaging service is inactive, and the app simply waits to be waked up by GCM.
The logcat:
10-20 16:10:35.903 E/AndroidRuntime(17532): FATAL EXCEPTION: main
10-20 16:10:35.903 E/AndroidRuntime(17532): java.lang.RuntimeException: Unable to start receiver ch.threema.app.receivers.GcmBroadcastReceiver: java.lang.NullPointerException
10-20 16:10:35.903 E/AndroidRuntime(17532): 	at android.app.ActivityThread.handleReceiver(ActivityThread.java:2520)
10-20 16:10:35.903 E/AndroidRuntime(17532): 	at de.robv.android.xposed.XposedBridge.invokeOriginalMethodNative(Native Method)
10-20 16:10:35.903 E/AndroidRuntime(17532): 	at de.robv.android.xposed.XposedBridge.handleHookedMethod(XposedBridge.java:631)
10-20 16:10:35.903 E/AndroidRuntime(17532): 	at android.app.ActivityThread.handleReceiver(Native Method)
10-20 16:10:35.903 E/AndroidRuntime(17532): 	at android.app.ActivityThread.access$1500(ActivityThread.java:156)
10-20 16:10:35.903 E/AndroidRuntime(17532): 	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1416)
10-20 16:10:35.903 E/AndroidRuntime(17532): 	at android.os.Handler.dispatchMessage(Handler.java:99)
10-20 16:10:35.903 E/AndroidRuntime(17532): 	at android.os.Looper.loop(Looper.java:153)
10-20 16:10:35.903 E/AndroidRuntime(17532): 	at android.app.ActivityThread.main(ActivityThread.java:5299)
10-20 16:10:35.903 E/AndroidRuntime(17532): 	at java.lang.reflect.Method.invokeNative(Native Method)
10-20 16:10:35.903 E/AndroidRuntime(17532): 	at java.lang.reflect.Method.invoke(Method.java:511)
10-20 16:10:35.903 E/AndroidRuntime(17532): 	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:833)
10-20 16:10:35.903 E/AndroidRuntime(17532): 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:600)
10-20 16:10:35.903 E/AndroidRuntime(17532): 	at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:132)
10-20 16:10:35.903 E/AndroidRuntime(17532): 	at dalvik.system.NativeStart.main(Native Method)
10-20 16:10:35.903 E/AndroidRuntime(17532): Caused by: java.lang.NullPointerException
10-20 16:10:35.903 E/AndroidRuntime(17532): 	at ch.threema.app.receivers.GcmBroadcastReceiver.onReceive(SourceFile:34)
10-20 16:10:35.903 E/AndroidRuntime(17532): 	at android.app.ActivityThread.handleReceiver(ActivityThread.java:2513)
10-20 16:10:35.903 E/AndroidRuntime(17532): 	... 14 more
10-20 16:10:35.935 E/AppErrorDialog(573): Failed to get ILowStorageHandle instance
10-20 16:10:43.799 D/libc-netbsd(126): getaddrinfo: reports.crashlytics.com NO result from proxy
10-20 16:10:43.800 D/libc-netbsd(126): res_queryN name = reports.crashlytics.com, class = 1, type = 1
10-20 16:10:43.831 D/libc-netbsd(126): res_queryN name = reports.crashlytics.com succeed
10-20 16:10:43.860 D/libc-netbsd(869): getaddrinfo: reports.crashlytics.com get result from proxy >>
10-20 16:10:43.923 E/Crashlytics(869): Error occurred sending report com.crashlytics.android.Z@41a8a090```
Reading the logcat, I am not sure whether GMS core is really responsible for the problem. It may be a Threema bug? It should also be noted that I have restricted parts of Threema with XPrivacy, so this may be the reason for the crash. (On the other hand, the only activity XPrivacy has listed when Threema received the c2dm.intent.RECEIVE was in fact c2dm.intent.RECEIVE.)

Did you reinstall Threema after installing GsfProxy?

I did a re-install without deinstalling it. I will try a proper re-install.

Unfortunately, it still crashes. As far as I can tell, the logcat is still the same as above.

Looking through the exception stack trace, this seems not to be related to GmsCore, however, as Threema is obfuscated non-free software, one can't say for sure. Can you try to disable XPrivacy for Threema?

I have deactivated XPrivacy for Threema, and the crash still occurs. Since the installation of GsfProxy coincided with the release of a new Threema sub-version, this may be a bug of Threema that happens in my constellation. I will also take a look at the internal Threema log.

Thanks for the note on the Threema update. Threema 2.52 does not work with GmsCore right now, as they use some undocumented features of the deprecated C2DM API. Threema 2.51 should still work. I will provide a fix for the problem soon.

Excellent, @mar-v-in . 2.51 worked without problems, but I also had not GsfProxy installed. I will see how Threema 2.51 behaves with GsfProxy and GmsCore both installed.

It seems that @mar-v-in is right: 2.51 seems to work with both GsfProxy and GmsCore installed.

Until the new version (v0.02 I guess – any estimate when it's due?) is released: what are known actions to revive GCM?

reboot (solved it 100% for me, but is not the preferred action)
dialing *#*#CHECKIN#*#* (as mentioned in #23 – is this a reliable fix? can it be automated e.g. via Tasker? if so, does it hurt to simply run it e.g. once per hour/day via automated task?)
other options? (e.g. force-stop/restart the responsible process (which? how to?))
is it recommended to use one of those "Push Notifications Fixer" apps – and if so, which one(s)? Any side-effects to expect from those?

Apart from that: is there a way for non-devs (like me) to get hold of the "current dev APK" – something like a "nightly/weekly build"? That way we might help confirming whether a certain bug/misbehavior/other_strange_thing (count me in with this one, happens to me about once per week) was fixed or is having other side-effects.

@SWW13 provides automated builds here: http://files.brnmod.rocks/apps/GmsCore/Latest/

v0.02 will be published soon (maybe next week) and I will start to provide "official" signed builds on a regular base afterwards (including updates through a f-droid repository)

Thanks @julienschmidt – and of course @mar-v-in ! With that announcement, I guess I'll wait that little time and go with the official builds (they'll be more frequent then I take it?) due to signature and automatic updates (F-Droid). Looking forward to that announcement :)
@mar-v-in might be useful to link those automated builds from the README.md? And if I understood you correctly, you'll setup a separate repo for this "dev branch". I'll happily include it in my list of F-Droid Repos :smiley_cat:

Since the upgrade to Threema 2.6, there seems to be again an issue with GCM. I am not sure whether this is (again) related to some undocumented command of GCM/C2DM that Threema uses or to a bug in Threema itself. (In the latter, maybe a version 2.61 will fix this. Note that I have indeed seen some reports about Push problems with Threema 2.6 and the official Google Play Services, but they may or may not be related to my problem. The general userbase does not seem to have any major problems.)
The problem: Threema no longer seems to be able to register at the GCM service (com.google.android.c2dm.intent.REGISTRATION) nor does it receive any messages (com.google.android.c2dm.intent.RECEIVE - this is probably related to the failed registration).
Threema offers the possibility to force a new REGISTRATION action ("Reset push token", see https://threema.ch/en/faq/push_andr ). The Threema log of Version 2.53 then reports:
Wed Jan 27 13:46:16 MEZ 2016	 acquireConnection: source = activityResumed, refCount = 1
Wed Jan 27 13:46:17 MEZ 2016 	GCM register forced.
Wed Jan 27 13:46:17 MEZ 2016	GCM register in background.
Wed Jan 27 13:46:18 MEZ 2016	 GCM registered, token = APA***E
Wed Jan 27 13:46:18 MEZ 2016	Sent push token to server.
Wed Jan 27 13:46:20 MEZ 2016	 releaseConnectionLinger: source = activityPaused, timeout = 60000
Wed Jan 27 13:46:20 MEZ 2016	releaseConnection: source = activityPaused, refCount = 0
Wed Jan 27 13:46:20 MEZ 2016	onTrimMemory: 20

XPrivacy shows that a REGISTRATION was executed, and the logcat (captured with catlog) shows that GMS Core connected to the Google push server. Receiving messages works as expected.
This does not happen with version 2.6. The Threema log only shows
Wed Jan 27 11:54:50 MEZ 2016	acquireConnection: source = activityResumed, refCount = 1
Wed Jan 27 11:54:51 MEZ 2016	 GCM Registration Token: APA***E
Wed Jan 27 11:54:53 MEZ 2016	 releaseConnectionLinger: source = activityPaused, timeout = 60000
Wed Jan 27 11:54:53 MEZ 2016	releaseConnection: source = activityPaused, refCount = 0
Wed Jan 27 11:54:53 MEZ 2016	onTrimMemory: 20

XPrivacy does not show a REGISTRATION action, and the logcat does not show anything either (not even an error).
The only REGISTRATION that seems to happen is after the installation of Threema 2.6 (which is also intercepted - and allowed - by XPrivacy). It does not seem to have any effect because push messages do not arrive. (As mentioned, resetting the push token should again lead to a new REGISTRATION, which does not happen.)
I am aware that this description (with a logcat that does not show anything special...) does not really help. To begin, I therefore can only ask:
Does anyone use Threema 2.6 with the newest version of GMS Core, and it works?
Should a developer want to look into this and not have a Threema licence, just send me a message, I will gladly sponsor one.
To conclude, my system:
Android 4.2.2
Version 0.2.0 of GMS Core (downloaded at http://files.brnmod.rocks/apps/GmsCore/Latest)
Signature spoofing with the FakeGapps Xposed module
Push works with WhatsApp & Push Notification Tester

Just a little feedback: Heartbeat was just dead again here (still with the 0.01 of GmsCore installed). Did an adb install -r for the 0.2.0, immediately got a lot of noise (all the missed notifications came up at once and were immediately dismissed as already noticed elsewhere), and the heart started beating again – no reboot required at all :) Will watch this a little longer, but that looks very promising. :+1:

Threema has been updated to 2.61. The good news is that the app now gets a com.google.android.c2dm.intent.RECEIVE if a new message has been sent to me. Unfortunately, Threema does not seem to process this, i.e. the app does nothing. Moreover, the manual renewal of the push registration token (i.e. the triggering of a com.google.android.c2dm.intent.REGISTER action) still does not seem to work (with the possible exception once after the installation of the update).
I will have to further look into this, but my logcat still does not contain anything special (at least if viewed with catlog).

Using 6.0.1 and the current nightlies installed as system apps.
This time the heartbeat wasn't issued for several hours until I opened WhatsApp.
Here is the log: http://hastebin.com/oyoyugeyup.avrasm.
This issue might be connected to #100.

@xsmile answered in #100. This is very likely related.
@Tentos Please create a separate issue for Threema if the problem still persists with log output
Everyone having issues with push notifications on Android 6.0: Please ensure that "Battery optimization" is disabled for microG Services Core in System Settings -> Battery -> Menu -> Battery optimization. Note that this is the case for original Play Services as it is required to keep a stable background connection.
As far as I can tell from now, problems with GCM do not occur widely and/or are specific to certain apps and custom ROMs. I am closing this issue now. If you encounter a similar issue, please create a separate issue with all details.


Plugin is not found after following installation instructions

I am getting this error from mkdocs:
ERROR    -  Config value: 'plugins'. Error: The "print-site" plugin is not installed
after installing
$ pip3 install mkdocs-print-site-plugin
Collecting mkdocs-print-site-plugin
  Downloading mkdocs_print_site_plugin-2.4.1-py3-none-any.whl (31 kB)
How do I debug this situation?
Where is the plugin installed?
Where is mkdocs looking for plugins?
PS. I am using poetry to run mkdocs if this is relevant.
poetry run mkdocs build

Try poetry install mkdocs-print-site-plugin. See
https://python-poetry.org/docs/basic-usage/#installing-dependencies


UNet2D Implementation On HipMRI

I've implemented UNet2D on the HipMRI dataset.
This submission has the clutter in the root folder then the actual python files in a folder called 2DUnet_47454822.
To get this to work, create a folder in 2DUnet_47454822 called 'data', then add the training, validation and test folders inside the HipMRI dataset to this. After that install the requirements as specified in the ReadMe.
This solution has an average Dice coefficient of 0.97.
Any/all feedback welcome!
Student number: 47454822

This is an initial inspection, no action is required at this point

Solves problem: The model reached 0.96 DICE score. The model was trained for 2 epochs. There were 2 test/s.py files and one empty predict.py, not sure which one was used for testing. Part of training log was pasted, but no loss plot or prediction figures.
Implementation: In modules.py, batch size argument was not used. Inconsistent and inappropriate usage of dice loss, here the dice loss was used as dice, but here used (1 - loss) as dice. No data augmentation. Overall messy.
Design: Not good, too many similar or empty files. Unused code were not deleted. A bit messy.
Comment: Not structured well, some functions do not have coomments
Difficulty: Easy

Note

The pull request should be created to topic-recognition branch not main.
Your project should be under PatternAnalysis-2024/recognition/<student_constructed_folder>, otherwise it will fail to be merged.
pycache should not be commited.

Marking

Good/OK/Fair Practice (Design/Commenting, TF/Torch Usage)
No design and implementation. Unused code present. Design needs cleanup.-2
Spacing and comments.
No Header blocks. -1
Recognition Problem
OK solution to problem. Inconsistant code segments.-2
Driver Script present.
File structure present.
Good Usage & Demo & Visualisation & Data usage.
Module present.
Commenting missing. Lacks structure.-1
No Data leakage found.
Difficulty : Easy. UNet2D (Easy Difficulty)-10
Commit Log
Good Meaningful commit messages.
Some/Adequate Progressive commits. -1
Documentation
Readme :Good.
Model/technical explanation :Good.
Description and Comments :Acceptable. No references.-1
Markdown used and PDF submitted. PDF checked.
Pull Request
Pull Request has problems: Submitted on time. Wrong branch.-2
Feedback action required: Feedback marks possible +2 if the requested changes are made. Correct PR branch for merge. Remove cache files and unwanted files.-2
Request Description is adequate. -1
TOTAL-23

Marked as per the due date and changes after which aren't necessarily allowed to contribute to grade for fairness.
Subject to approval from Shakes

Feedback marks possible +2 if the requested changes are made (see above).


hello, does ii support quic protocol?

This is a layer 4 module, that is agnostic of application-layer protocols. It just shuttles bytes over TCP or UDP.


es-lint fixes

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

8 of 8 (100.0%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
982

Relevant Lines:
982

💛  - Coveralls


Compatibility pass on flutter/scheduler tests for JavaScript compilation. (2)

Description
Flags certain test cases in scheduler using package:test tags in order to facilitate landing support for running all framework tests in a browser.
Requires: https://github.com/flutter/flutter/pull/33349

Updated with feedback and to run on CI


Caption comes as "verified"

I tried to crawl a verified profile and all the captions came as "verified". Is there a way we can get the action caption instead?

I might add that I once get the right caption, but then all I had after that was Verified.
Seems like something might have changed.


Addining a new provider

I'd love to see Hostman on the list of cloud hosting providers. It'd be interesting for me and other users to compare it to DO or Render, for example. Please let me know if you need some additional info from me.
Thank you in advance

@alena-ko looks great. Didn't know about this provider. Will be working on this next week.
Thanks!

@alena-ko already implemented :)

Thank you! It's great to work with you:)
ср, 21 июл. 2021 г. в 05:17, Nacho Anaya @.***>:

@alena-ko https://github.com/alena-ko already implemented :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/checkly/jamstack-deploy/issues/5#issuecomment-883788673,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AS3KDNZNCEANMR4LGBYA4BLTYYGX7ANCNFSM5APUOLOQ
.


Fixed a bug in index.html

@Abirpal202049 Link?

@swati2603 I had made a little change you just approve it

@swati2603 I had made a little change you just approve it

I know but we have asked the participants to share, it applies to us too. That's why I said.


Fix typos in non-production code

Found with codespell **/*.rb **/*.md plus some manual fixes and manual findings.
Didn't fix discernable because it can be considered production code
and introduce a breaking change.

Many thanks 🙏


HDFS-16023.Improve blockReportLeaseId acquisition to avoid repeated FBR.

NOTICE
Please create an issue in ASF JIRA before opening a pull request,
and you need to set the title of the pull request which starts with
the corresponding JIRA issue number. (e.g. HADOOP-XXXXX. Fix a typo in YYY.)
For more details, please see https://cwiki.apache.org/confluence/display/HADOOP/How+To+Contribute

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 35s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

-1 :x:
mvninstall
9m 48s
/branch-mvninstall-root.txt
root in trunk failed.

+1 :green_heart:
compile
1m 17s

trunk passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
compile
1m  9s

trunk passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
checkstyle
0m 57s

trunk passed

+1 :green_heart:
mvnsite
1m 17s

trunk passed

+1 :green_heart:
javadoc
0m 52s

trunk passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javadoc
1m 21s

trunk passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
spotbugs
3m  0s

trunk passed

+1 :green_heart:
shadedclient
16m 35s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
1m 13s

the patch passed

+1 :green_heart:
compile
1m 14s

the patch passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javac
1m 14s

the patch passed

+1 :green_heart:
compile
1m  8s

the patch passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
javac
1m  8s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 56s

the patch passed

+1 :green_heart:
mvnsite
1m 13s

the patch passed

+1 :green_heart:
javadoc
0m 46s

the patch passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javadoc
1m 19s

the patch passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
spotbugs
3m  7s

the patch passed

+1 :green_heart:
shadedclient
16m  4s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

-1 :x:
unit
242m 31s
/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in the patch passed.

+1 :green_heart:
asflicense
0m 43s

The patch does not generate ASF License warnings.

305m 20s

Reason
Tests

Failed junit tests
hadoop.hdfs.server.blockmanagement.TestBlockReportLease

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3091/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/3091

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell

uname
Linux 697925ec8657 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / ff39e4aba55fb868d9f689ddf75f5a175ddf2fa7

Default Java
Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3091/1/testReport/

Max. process+thread count
3092 (vs. ulimit of 5500)

modules
C: hadoop-hdfs-project/hadoop-hdfs U: hadoop-hdfs-project/hadoop-hdfs

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3091/1/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 36s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
31m 28s

trunk passed

+1 :green_heart:
compile
1m 23s

trunk passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
compile
1m 20s

trunk passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
checkstyle
1m  0s

trunk passed

+1 :green_heart:
mvnsite
1m 25s

trunk passed

+1 :green_heart:
javadoc
0m 59s

trunk passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javadoc
1m 31s

trunk passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
spotbugs
3m 22s

trunk passed

+1 :green_heart:
shadedclient
16m 41s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
1m 15s

the patch passed

+1 :green_heart:
compile
1m 19s

the patch passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javac
1m 19s

the patch passed

+1 :green_heart:
compile
1m 11s

the patch passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
javac
1m 11s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
1m  2s

the patch passed

+1 :green_heart:
mvnsite
1m 14s

the patch passed

+1 :green_heart:
javadoc
0m 50s

the patch passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javadoc
1m 27s

the patch passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
spotbugs
3m  5s

the patch passed

+1 :green_heart:
shadedclient
15m 57s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

-1 :x:
unit
249m 26s
/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in the patch passed.

+1 :green_heart:
asflicense
0m 47s

The patch does not generate ASF License warnings.

335m 17s

Reason
Tests

Failed junit tests
hadoop.hdfs.server.namenode.ha.TestBootstrapAliasmap

hadoop.hdfs.TestFileChecksum

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3091/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/3091

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell

uname
Linux da722c292617 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 917dc482186cc690a16304032aedb194cf9dc1ed

Default Java
Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3091/2/testReport/

Max. process+thread count
3163 (vs. ulimit of 5500)

modules
C: hadoop-hdfs-project/hadoop-hdfs U: hadoop-hdfs-project/hadoop-hdfs

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3091/2/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.


GEOMESA-989 Fixing query stats hits for bin queries

Signed-off-by: Emilio Lahr-Vivaz<EMAIL_ADDRESS>

I'm going to close this PR in favor of #728, which has a duplicate commit.


Add 1.0x Songselect overlay and rescale all element

This is fix issues from #32 to fix ui issues.
also, i decided to add 1.0x screen scale and rescale all element to match with 1.0x UI Scale but still working on it
This issues has been close after completely added
issues image

Done!
i rescale completely
Note : i found issuse in songselect still rescale
1.song name in songselect has overlapping with long beatmaps name in bottom section

2. about sort by. in 0.80x has show all but in 1.00x has not show all anyway if your not worry this it's ok but if you worry you can organize by yourself

Main Menu
0.80x

1.00x

Gameplay
0.80x

1.00x

Anyway this issuse has close now


Created pricing card 5 black

Closes #1939
This is the screenshot of the component

This is the screenshot of the component in a smaller view

@SakshiShah29 Make it with fixed width and give slate-900 shade instead of 800

yes sure

@RavindraP04 I have updated the component


Error when starting build of gameplay

I get this error please helpme!!!
pi@raspberrypi:root/gameboygameplay/gameplay$ scripts/build build settings/release.json
Extracting JavaScript...
Traceback (most recent call last):
File "scripts/build", line 290, in
main()
File "scripts/build", line 287, in main
options.fn(options)
File "scripts/build", line 176, in build
script += extract_tags(html, "//script[@type='text/javascript']", "src", paths.SOURCE_DIR)
File "scripts/build", line 60, in extract_tags
with open(src) as script:
IOError: [Errno 2] No such file or directory: '/home/pi/gameboygameplay/gameplay/src/../cores/GameBoy-Online/js/other/swfobject.js'
pi@raspberrypi:root/gameboygameplay/gameplay$

For all I know, there is no file called 'swfobject.js', and that is what is throwing the error. I have no answer on how to fix it.

indeed. i also tried building it and it works fine. did you do the submodules part in the readme? or maybe you changed the path to get gameboy-online from somewhere else, and its not correct, or different version that moved that file..


7.1.17 release: updates dependencies

As mentioned in the CHANGELOG.md, please consider the breaking changes underlined here.

Closing for now as I did not fully tested that update and because other dependencies (such as flutter_keyboard_visibility) would also required an update…


Migrating buildSrc Jsoup plugin from Groovy to Kotlin

As a test I ran ./gradlew :docs:docs and everything worked fine.

Feedback build https://builds.gradle.org/viewQueued.html?itemId=11125006


Remove false positive

Please remove these false positive sites from hosts

onesignal.com
rebrand.ly

False positive for: vivaldi.com
This is a browser

Done in commit c962b4a285a22f150353eab9598f847643ed70e4


Update Composer dependencies (2021-10-19-00-08)

Visual regression test passed!
View the visual regression test report


Add java.sysl and relocate json.sysl

Please issue PRs from your fork at https://github.com/anzdaddy/sysl into upstream [master]((https://github.com/anz-bank/sysl/) for the following reasons:

We (the @anz-bank/sysl-developers) work the same way as any potential open source contributor and find difficulties that way (there are some with CI and security related configs)
We don't have to think about branch naming conventions to avoid naming conflicts
We keep the branches of upstream  clean.

BTW, CI is borked. This line in e2e testing is the culprit - unrelated to this PR, it's my bad I forgot to delete it when updating the svg output tests in a haste. You can either fix it yourself or I can create another PR.

As per our discussion

let's not worry about docs for now
let's merge these branches into master and work with a
origin:branch -> upstream:master PR model from here onwards

@anzdaddy - I'm still wondering about the missing *, but happy I'm happy for you to merge anyway.


AVRO-3957: [C] Fix typos in docs and examples

What is the purpose of the change
This fixes typos in docs and examples
Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Documentation
No new features are added

Thank you, @SahilKang !


Minor Changes to project.xml

change Build.yml

I updated Build.yml and added another build script (for debug builds) so yea :)

remove brandon


Issues with sending notifications

Hi! I'm not sure if this is the right forum (I also commented in the ExLibris Developers Network), but in my testing, the notification part did not work & I'd like insight as to where I may have gone wrong. My suggestion is that the app calendar link to the library calendar to reflect open/closed days/times to avoid allowing appointments on those off days/times. Thanks! Linda :)

I think I have a similar problem: the notification part doesn't work. When you save it schedules OK, but a message appears: "An error ocurred", and the email is not sent.
In the sandbox everything works ok, scheduling and emailing, but in the production environment there's the email error. So maybe it has to do with the configuration of the production environment, but I can't guess what it is.

Hi @vallu  and @lparker15atavc . Thanks for your question. Regarding the suggestion to display an indication if the library is closed according to the library configuration, can I trouble you to open a separate issue?
Regarding the issue sending notifications, a few things could go wrong:

I noticed we had a failure sending SMS notifications in Spain, so we now allow that.
Can you confirm the user has a preferred email address specified and that it's a valid email format?

If all else fails, you can also take a look at the browser console (View->Developer->JavaScript Console in Chrome) to see what the error message is.
Thanks for your help in troubleshooting this.

Hi there! Yes, the user had the preferred email address specified and it was in a valid email format. Is it possible there is some other type of configuration that needs to take place in Alma? I took a look at the browser console and noted the following errors:

Failure to load resource the server responded with a status of 404 (Not Found)
Error trying to send notification Domain contains main.75e66c1113799255bd4e.js:1 control or whitespace
Thank you!
Linda :)

Thanks for the error messages. That second one does indicate that there is something about the email address that it doesn't like. We added some additional error logging so you can try again, or you can try with a different user to see if that works.

Hello Josh,
The preferred mail address of the user was ok and I don't think it's a problem with SMS, because I didn't check that option when I configured the Appointment Scheduler for our institution as we don't have all the phone numbers of our users.
I get these error messages in the browser console:

Failed to load resource: the server responded with a status of 401 (Unauthorized)        /almaws/v1/users/0641115250:1
main.75e66c1113799255bd4e.js:1 Error saving event t            main.75e66c1113799255bd4e.js:1

When I click on the first error, I get this information:
{"web_service_result":{"errorsExist":true,"errorList":{"error":{"errorCode":4022150,"errorMessage":"El acceso directo al uso de las APIs REST está bloqueado para este usuario. Por favor, use la API del portal.","trackingId":"E05-0312080536-ZSO4N-AWAE2086367015"}}}}
Also, the app behaves perfectly well when I'm logged in Alma as Administrator, the error comes if I'm logged in as a Circulation Desk Operator.
And finally, the app has problems in finding the user: when I type the name, it doesn't find it, but if I type de primary identifier, it finds it ok.
Thank you!

Hi @vallu -
To use the app you need permissions to view full user information. Today these roles have access:

Trial Manager
Trial Operator
User Administrator
User Manager Full
Administrator

Starting with the December release (in the sandbox already), these roles will also have access:

Circulation Desk Manager
Circulation Desk Operator
Repository Manager

It's interesting because the app should warn you if you don't have the necessary roles. But in any event you can check in the sandbox (or in production on Monday) to confirm that it works with the new roles.
Thanks.

Hello Josh:
Before installing the app in our Alma, we tried it in the sandbox and it worked ok, then I tried it in the production environment with my administrator role, and it worked ok. It was when we tried it in the production environment with the circulation desk operator role that we got the error message.
The app does warn when you don't have the necessary role: we have also tried in the production environment with staff with acquisition or cataloging roles, but no circulation desk role, and it will say you don't have the appropiate roles to use the app, and won't let you in.
With the circulation desk operator roles, it lets you in, but you get the error message.
So we'll try it in production on monday and see what happens. We will tell you.
Thanks

OK, now the app is working with the "circulation desk operator" rol.
Anyway, there's a couple of problems we get using the Appoinment Scheduler:
1.- The type to search option for searching the users doesn't work with blank spaces. For example, if I'm looking for José García Pombo, when I type García, it will show me all the García (there's hundreds), but as soon as I type the blank space and the "P", it will stop working. We can avoid this by searching the user in Alma, copying the primary identifier, and searching in the Appointment Scheduler by the primary identifier.
2.- The message the user gets by mail in our library is this:

Hola,
Le comunicamos que la cita para el préstamo / devolución de libros en la Biblioteca de Medicina. Mostrador de préstamo es el  Tuesday, December 8th 2020, 08:30.
Atentamente
Servicio de Bibliotecas
Universidad de Salamanca

¿Would it be possible to get the date in spanish, and also with the am/pm after the hour?:  martes, 8 de diciembre de 2020, a las 8:30 am., instead of Tuesday, December 8th 2020, 8:30
3.- The user gets an email when a date is appointed or modified, but not when its deleted. ¿Could it be possible to send a message also when a date is cancelled?
Thank you very much

Hi @vallu . We were able to implement the changes you requested:

Support searching for names with spaces (for now, only the full name is supported, not wildcards)
Support configuration for date formatting (see docs)
Send cancellation message (see docs

Let us know how that works for you.

Hello Josh,

The search for names with spaces works but only with one space, for example, if I'm searching for "Marta de La Mano González", it works if I type "Mano González" (one blank space) but it won't work if I try "La Mano González" (two blank spaces). In Spain we have long names, I'm Francisco José Sáenz de Valluerca López.

I have introduced the language code "es", and the message is ok for a new appointment:

Le comunicamos que la cita para el préstamo / devolución de libros en la Biblioteca de Medicina. Mostrador de préstamo es el  jueves, 10 de diciembre de 2020 13:40.
But if we change the appointment we get this message:
Le comunicamos que la cita para el préstamo / devolución de libros en la Biblioteca de Medicina. Mostrador de préstamo es el  2020-12-10T11:10:00.000Z.
And if we cancel an appointment we now receive a message, but with a wrong date format:
Su cita para la Biblioteca de Medicina. Mostrador de préstamo, el 2020-12-10T11:10:00.000Z ha sido cancelada
Thank you very much

Thanks for checking on this @vallu ! Now I know about long Spanish names : ) We released a small fix which I hope addresses both of these issues.

Thanks again for pointing this out @vallu . This should be fixed as well.

Ok., now everything is working perfectly. We're testing the app in two libraries with real appointments, and we are getting some  suggestions from the libraries:
1.- If it would be possible that each library (location) could have its own email address to receive the feedback from the users if they want to change or cancel an appointment. I see your have an enhancement about the send from email address, I don't know if this is what you have in mind.
2.- If it would be possible to print the list of expected appointments of the day in order to cancel those that haven't come.
Thank you very much.

Great to hear that it’s working for you now. Can I ask you to open new issues for the additional enhancement requests? That will allow us to better track them. Thanks!
-Josh

On 15 Dec 2020, at 15:22, vallu<EMAIL_ADDRESS>wrote:

Ok., now everything is working perfectly. We're testing the app in two libraries with real appointments, and we are getting some suggestions from the libraries:
1.- If it would be possible that each library (location) could have its own email address to receive the feedback from the users if they want to change or cancel an appointment. I see your have an enhancement about the send from email address, I don't know if this is what you have in mind.
2.- If it would be possible to print the list of expected appointments of the day in order to cancel those that haven't come.
Thank you very much.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or unsubscribe.

Hi Josh!
I’ve continued to try numerous times and cannot get the notifications part functioning. All appears to work otherwise, I make the appointment, get the message a notification was sent, but still nothing shows up in my inbox or spam or anywhere. I’ve used different email addresses, different browsers, and adjusted settings to no avail. I appreciate any insight you can offer - thanks! Linda

Hi Josh!
I’ve continued to try numerous times and cannot get the notifications part functioning. All appears to work otherwise, I make the appointment, get the message a notification was sent, but still nothing shows up in my inbox or spam or anywhere. I’ve used different email addresses, different browsers, and adjusted settings to no avail. I appreciate any insight you can offer - thanks! Linda

Hi @lparker15atavc - sorry you're still having trouble with notifications. Can you take a look in your browser console again and let us know if there are any errors there? Thanks.

Hi @lparker15atavc - sorry you're still having trouble with notifications. Can you take a look in your browser console again and let us know if there are any errors there? Thanks.

Hi Josh - You'll be pleased to know that I got our issue figured out! In the "Reply-To Address" section, I had included an email AND a phone number which was causing the problem. Once I removed the extra information and kept it strictly to an email address, all notifications went through without any trouble! Woohoo! :) Thanks for your guidance along the way - I'm excited to share this with my co-workers.
Linda :)

Hi Josh - You'll be pleased to know that I got our issue figured out! In the "Reply-To Address" section, I had included an email AND a phone number which was causing the problem. Once I removed the extra information and kept it strictly to an email address, all notifications went through without any trouble! Woohoo! :) Thanks for your guidance along the way - I'm excited to share this with my co-workers.
Linda :)

Thanks for the feedback @lparker15atavc ! We'll add validation to the field to prevent this from happening to someone else : )

Thanks for the feedback @lparker15atavc ! We'll add validation to the field to prevent this from happening to someone else : )

Thank you, Josh! I appreciate your efforts in making these apps accessible
and user friendly for all.
Linda 😄
On Mon, Jan 25, 2021 at 4:18 AM Josh Weisman<EMAIL_ADDRESS>wrote:

Thanks for the feedback @lparker15atavc
https://github.com/lparker15atavc ! We'll add validation to the field
to prevent this from happening to someone else : )
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ExLibrisGroup/alma-scheduler/issues/11#issuecomment-766776943,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AR4UBFB2NQQNQB54WWEVQS3S3VOQRANCNFSM4UIFZBAQ
.

--
Linda Parker, M.L.I.S.
Systems Librarian / Instructor
Antelope Valley College | Library
3041 West Avenue K
Lancaster, CA 93536
661.722.6300, ext. 6063 |<EMAIL_ADDRESS>

Thank you, Josh! I appreciate your efforts in making these apps accessible
and user friendly for all.
Linda 😄
On Mon, Jan 25, 2021 at 4:18 AM Josh Weisman<EMAIL_ADDRESS>wrote:

Thanks for the feedback @lparker15atavc
https://github.com/lparker15atavc ! We'll add validation to the field
to prevent this from happening to someone else : )
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ExLibrisGroup/alma-scheduler/issues/11#issuecomment-766776943,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AR4UBFB2NQQNQB54WWEVQS3S3VOQRANCNFSM4UIFZBAQ
.

--
Linda Parker, M.L.I.S.
Systems Librarian / Instructor
Antelope Valley College | Library
3041 West Avenue K
Lancaster, CA 93536
661.722.6300, ext. 6063 |<EMAIL_ADDRESS>


size mismatch for PPE.pe

when I prepare the environment by using pip24.2  all package successfully installed except torchsde:
pip install torchsde==0.2.5
Looking in indexes: https://mirrors.aliyun.com/pypi/simple/
Collecting torchsde==0.2.5
Using cached https://mirrors.aliyun.com/pypi/packages/73/8d/efd3e7b31ea854d0bd6886aa3cf44914adce113a6d460850af41ac1dd4dd/torchsde-0.2.5-py3-none-any.whl (59 kB)
WARNING: Ignoring version 0.2.5 of torchsde since it has invalid metadata:
Requested torchsde==0.2.5 from https://mirrors.aliyun.com/pypi/packages/73/8d/efd3e7b31ea854d0bd6886aa3cf44914adce113a6d460850af41ac1dd4dd/torchsde-0.2.5-py3-none-any.whl#sha256=4c34373a94a357bdf60bbfee00c850f3563d634491555820b900c9a4f7eff300 has invalid metadata: .* suffix can only be used with == or != operators
numpy (>=1.19.*) ; python_version >= "3.7"
~~~~~~~^
Please use pip<24.1 if you need to use this version.
ERROR: Could not find a version that satisfies the requirement torchsde==0.2.5 (from versions: 0.2.5, 0.2.6)
ERROR: No matching distribution found for torchsde==0.2.5
so I remove the version specification of torchsde in requirement.txt, and pip install -r requirement successfully completed.
when I run 'python -m scripts.app', the following error occurs:
(anip) D:\gitrepos\AniPortrait>python -m scripts.app
Some weights of the model checkpoint at ./pretrained_model/wav2vec2-base-960h were not used when initializing Wav2Vec2Model: ['lm_head.weight', 'lm_head.bias']

This IS expected if you are initializing Wav2Vec2Model from the checkpoint of a model trained on another task or with another architecture (e.g. initializing a BertForSequenceClassification model from a BertForPreTraining model).
This IS NOT expected if you are initializing Wav2Vec2Model from the checkpoint of a model that you expect to be exactly identical (initializing a BertForSequenceClassification model from a BertForSequenceClassification model).
Some weights of Wav2Vec2Model were not initialized from the model checkpoint at ./pretrained_model/wav2vec2-base-960h and are newly initialized: ['wav2vec2.masked_spec_embed']
You should probably TRAIN this model on a down-stream task to be able to use it for predictions and inference.
Some weights of the model checkpoint at ./pretrained_model/wav2vec2-base-960h were not used when initializing Wav2Vec2Model: ['lm_head.weight', 'lm_head.bias']
This IS expected if you are initializing Wav2Vec2Model from the checkpoint of a model trained on another task or with another architecture (e.g. initializing a BertForSequenceClassification model from a BertForPreTraining model).
This IS NOT expected if you are initializing Wav2Vec2Model from the checkpoint of a model that you expect to be exactly identical (initializing a BertForSequenceClassification model from a BertForSequenceClassification model).
Some weights of Wav2Vec2Model were not initialized from the model checkpoint at ./pretrained_model/wav2vec2-base-960h and are newly initialized: ['wav2vec2.masked_spec_embed']
You should probably TRAIN this model on a down-stream task to be able to use it for predictions and inference.
Traceback (most recent call last):
File "D:\pinokio\bin\miniconda\envs\anip\lib\runpy.py", line 196, in _run_module_as_main
return _run_code(code, main_globals, None,
File "D:\pinokio\bin\miniconda\envs\anip\lib\runpy.py", line 86, in _run_code
exec(code, run_globals)
File "D:\gitrepos\AniPortrait\scripts\app.py", line 49, in
a2p_model.load_state_dict(torch.load(audio_infer_config['pretrained_model']['a2p_ckpt']), strict=False)
File "D:\pinokio\bin\miniconda\envs\anip\lib\site-packages\torch\nn\modules\module.py", line 2041, in load_state_dict
raise RuntimeError('Error(s) in loading state_dict for {}:\n\t{}'.format(
RuntimeError: Error(s) in loading state_dict for Audio2PoseModel:
size mismatch for PPE.pe: copying a param with shape torch.Size([1, 630, 512]) from checkpoint, the shape in current model is torch.Size([1, 600, 512]).

is this a torchsde version problem?

I encountered the same problem, how did you solve it?

+1

+1

I fixed this problem by changing the initialization length of pose embedding in the code. The specific location is on line 43 of the file https://github.com/Zejun-Yang/AniPortrait/blob/main/src/audio_models/pose_model.py. I fixed this by changing max_len to 630. But I'm not sure this is as required


remove old code

I removed commented code, which are not used more.

@googlebot I signed it!
On Tue, Sep 1, 2020 at 11:20 PM google-cla[bot]<EMAIL_ADDRESS>wrote:

Thanks for your pull request. It looks like this may be your first
contribution to a Google open source project (if not, look below for help).
Before we can look at your pull request, you'll need to sign a Contributor
License Agreement (CLA).
📝 Please visit https://cla.developers.google.com/
https://cla.developers.google.com/ to sign.
Once you've signed (or fixed any issues), please reply here with @googlebot
I signed it! and we'll verify it.

What to do if you already signed the CLA
Individual signers

It's possible we don't have your GitHub username or you're using a
different email address on your commit. Check your existing CLA data
https://cla.developers.google.com/clas and verify that your email is
set on your git commits
https://help.github.com/articles/setting-your-email-in-git/.

Corporate signers

Your company has a Point of Contact who decides which employees are
authorized to participate. Ask your POC to be added to the group of
authorized contributors. If you don't know who your Point of Contact is,
direct the Google project maintainer to go/cla#troubleshoot (Public
version https://opensource.google/docs/cla/#troubleshoot).

The email used to register you as an authorized contributor must be
the email used for the Git commit. Check your existing CLA data
https://cla.developers.google.com/clas and verify that your email is
set on your git commits
https://help.github.com/articles/setting-your-email-in-git/.

The email used to register you as an authorized contributor must
also be attached to your GitHub account
https://github.com/settings/emails.

ℹ Googlers: Go here
https://goto.google.com/prinfo/https%3A%2F%2Fgithub.com%2Fgoogleinterns%2Fintern2020_cocal%2Fpull%2F1
for more info.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/googleinterns/intern2020_cocal/pull/1#issuecomment-685284825,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABW4EM2LHZJNBY2UJY4P2QTSDXBYDANCNFSM4QSRNGUA
.


CHN update for 2.5

Summary and Scope
This PR updates 2.5.11 docs for the updated CHN configuration method.
Issues and Related PRs

Resolves CASMUSER-3184
Resolves CASMUSER-3185

Testing
List the environments in which these changes were tested.
Tested on:

hela

Test description:
Rebooted the UAN on hela after configuring the image to enable cray-ifconf and updating the uan_interfaces role with the new code.
Risks and Mitigations
Low risk
Pull Request Checklist

[X] Version number(s) incremented, if applicable
[X] Copyrights updated
[X] License file intact
[X] Target branch correct
[X] CHANGELOG.md updated
X ] Testing is appropriate and complete, if applicable
[ ] HPC Product Announcement prepared, if applicable

Update ditamap files for the next version.


After click on checkbox moving page one pixel on register page

Which area(s) of Podkrepi.bg are affected?
Desktop layout, Mobile layout
Describe the Bug
https://github.com/podkrepi-bg/frontend/assets/16596102/01c8551f-bcfb-475c-954e-7780b7902b61
Why page moving with one pixel after click checkbox?
To Reproduce

Open https://podkrepi.bg/en/register
Click F5 from keyboard
Click checkbox for "I understand and I agree to the [General Data Protection Regulation (GDPR)]"
Why whole page move with one pixel?

Expected Behavior
After click checkbox no moving of bottom of the page
Which browser are you using? (if relevant)
Floorp

At first sight, the issue should be resolved if we set the margin-top of the text error to 0:


forever doesn't start because of wrong arguments parsing

When forever starts it assumes the name of the script is start.
sh-3.2# forever start script.js
The "sys" module is now called "util". It should have a similar interface.
info:   Running action: start
info:   Forever processing file: start
error:  Cannot start forever
error:  script /Users/user/projects/start does not exist.

This happens on Node v0.6.2 and OSX v10.6.8

This has since been fixed. Please update forever.
Also, forever doesn't work on node 0.6. Please see #163.


[release-1.6] Fix networking.HTTPMatchRequest.WithoutHeaders conflict detect

This is an automated cherry-pick of #26058

@istio-testing: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio_release-1.6
889b7583667f42a6acfe3c65fecdf676571d2a07
link
/test unit-tests_istio_release-1.6

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@googlebot I consent
/retest

@istio-testing: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio_release-1.6
889b7583667f42a6acfe3c65fecdf676571d2a07
link
/test unit-tests_istio_release-1.6

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@googlebot I consent.

/retest

Thanks


Get the BT ALIAS from env

Simple PR that moves the bluetooth adapter alias from variable inside code to get it from env variable. The default value if the var is not set keeps the same.
# Export the variable to use the BT alias.
export ADAPTER_ALIAS=NewBtAlias

With #72, we have to use special bluetooth name in case of dongle mode. Let's wait for that one and we can see how we can customise that works for both dongle more and non-dongle modes?

With #72, we have to use special bluetooth name in case of dongle mode. Let's wait for that one and we can see how we can customise that works for both dongle more and non-dongle modes?

I saw the PR and I thought it did not matter... for sure we can wait :) anyway, on the latest commit added a bool to test if we are in dongle mode or not...

In dongle mode, the BT name needs to be AndroidAuto-* and needs to be different when not in dongle mode.
Should we just specify a suffix that can change based on the config? Or can we simply set the name based on some MAC address always? Would that work for your scenarios?


Web: Uncaught Error: Exception: webOnlyScheduleFrameCallback must be initialized first.

After upgrading flutter to latest master channel I am getting following error. Sometime I also get error 404 for not finding manifest.json and icon file.

Here is the output of flutter doctor -v

I have downloaded the stable version again then changed the channel to master. After upgrading flutter I have created a new app. The app is working again but I am still getting these errors in console.
A bad HTTP response code (404) was received when fetching the script.
manifest.json:1 GET http://localhost:42317/manifest.json 404 (Not Found)
manifest.json:1 Manifest: Line: 1, column: 1, Syntax error.
:42317/#/:1 Uncaught (in promise) TypeError: Failed to register a ServiceWorker for scope ('http://localhost:42317/') with script ('http://localhost:42317/flutter_service_worker.js'): A bad HTTP response code (404) was received when fetching the script.

Fixed via https://github.com/flutter/flutter/pull/50036
The other issue is https://github.com/flutter/flutter/issues/49479


Cannot update array of array in broker load

Steps to reproduce the behavior (Required)
We have a large table with 1000 columns. When we used broker load to update 40 columns of it, in which inlcudes array of array, then the process failed, showing the following error message:
ErrorMsg: type: ETL_RUN_FAIL; msg_Cannot cast '<slot 4>' from VARCHAR to ARRAY<VARCHAR(100)>
Expected behavior (Required)
Expected the array of array to be sucessfully imported without errors.
Real behavior (Required)
ErrorMsg: type: ETL_RUN_FAIL; msg_Cannot cast '<slot 4>' from VARCHAR to ARRAY<VARCHAR(100)>
StarRocks version (Required)
2.3
My question is:

Does starrocks support array of array updating?
Is there any configuration that need to adjusted before loading array of array?

It has been addressed in 2.3.3. @sxhysj , which version do you install?

@chaoyli Does SR support loading data of Array of Array?

@jaogoy It's array not array


Add support for verified routes

This a a work in progress; feel free to test and report issues on this PR.

Pull Request Test Coverage Report for Build b59dfe9e8e648f2f7ab3379ef2c21dc679a12389-PR-10

18 of 50 (36.0%)  changed or added relevant lines in 5 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-14.6%) to 85.398%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

lib/localized_routes.ex
11
14
78.57%

lib/localized_routes/helpers.ex
1
10
10.0%

lib/localized_routes/router.ex
3
23
13.04%

Files with Coverage Reduction
New Missed Lines
%

lib/localized_routes/helpers.ex
1
73.68%

Totals

Change from base Build e4021028caa3cb09ecea0f8fe77020c665358774:
-14.6%

Covered Lines:
193

Relevant Lines:
226

💛  - Coveralls

Pull Request Test Coverage Report for Build b59dfe9e8e648f2f7ab3379ef2c21dc679a12389-PR-10

18 of 50 (36.0%)  changed or added relevant lines in 5 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-14.2%) to 85.841%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

lib/localized_routes.ex
11
14
78.57%

lib/localized_routes/helpers.ex
1
10
10.0%

lib/localized_routes/router.ex
3
23
13.04%

Totals

Change from base Build e4021028caa3cb09ecea0f8fe77020c665358774:
-14.2%

Covered Lines:
194

Relevant Lines:
226

💛  - Coveralls


win, test: fix fs_event_watch_dir_recursive

Under Windows uv_fs_event_start with UV_FS_EVENT_RECURSIVE will report new file creation and file deletion twice - once with the name of the file, and second time with the name of the directory itself. This will filter out callbacks with directory name, making observed callbacks count match expected values.
This test fails on Windows 10 and works most of the times on 2012 because of order of callbacks being called. In 2012 the test is flaky, when it passes it is because the callbacks for entire directory come after the ones for files. Under Windows 10, directory callback is called after each file modification.
Fixes: https://github.com/libuv/libuv/issues/1009

Wrapped the fix in ifdef for _WIN32, PTAL.

CI: https://ci.nodejs.org/view/libuv/job/libuv-test-commit/138/

We have a green Windows build! :tada: :tada: Thanks a ton Bartosz! Landed in :sparkles: 468d446 :sparkles:


Current bundle in deployer:list

When the concept of a "current bundle" is added, it would be nice to indicate which one that is in deployer:list (perhaps with an asterisk).

Fixed by #22.


🐞 calc() with unit awareness doesn't work in group syntax

Description
Group

Normal

🎉 Released in https://github.com/master-co/css/releases/tag/v2.0.0-beta.113


8vim's github description has errors.

https://github.com/flide/8VIM/
"The application was started essentially as a clone of 8pen, which for some reason they have stopped distributing. (I can no longer install it even though when I paid for it!!!)"
even though when is incorrect. I think it would be correct if when was deleted.
"The application at first was created as a clone of 8pen, which for some reason they have stopped distributing. (I can no longer install it even though I paid for it!!!)"

taking the issue forward with #109


Moar descriptive pull request titles when single files are added/removed/changed

Reimagines #13 for a post-#14 world.

oh brave new world that has such pull requests in it


Who should use KLT and who should use Keptn v1

Create summary of why one should use KLT and why one should use Keptn v1
Part of https://github.com/keptn/lifecycle-toolkit/issues/1499

I will rise PR for this .Please confirm in which file we want to put this content


Native assets: package in framework on iOS and MacOS

Packages the native assets for iOS and MacOS in frameworks.
Issue:

https://github.com/flutter/flutter/issues/140544
https://github.com/flutter/flutter/issues/129757

Details

[x] This packages dylibs from the native assets feature in frameworks. It packages every dylib in a separate framework.
[x] The dylib name is updated to use @rpath instead of @executable_path.
[x] The dylibs for flutter-tester are no longer modified to change the install name. (Previously it was wrongly updating the install name to the location the dylib would have once deployed in an app.)
[x] Use symlinking on MacOS.

Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I signed the CLA.
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is test-exempt.
[x] All existing and new tests are passing.

@jmagman @vashworth Friendly ping!

Friendly ping @jmagman.

Apologies for the delay on this. @dcharkes can you point me to an example of how to generate these frameworks? I try it out and see if the bundle format looks correct with a manual test.

You can run test/integration.shard/native_assets_test.dart locally and stop it from deleting the temp folders.
Or you can do the steps manually, flutter create --template=package_ffi --target=macos,ios and use flutter build macos.

LGTM, thanks for tackling all this!

 And thanks for pointing me in the right direction!
Thanks @SKKbySSK for reporting the problem!

Not sure about that overall_experience_test failure, I filed https://github.com/flutter/flutter/issues/141892 to investigate.  Re-running.

@dcharkes
I've confirmed that the framework was built as expected on the latest master.
Thanks for handling the issue!

@dcharkes I've confirmed that the framework was built as expected on the latest master. Thanks for handling the issue!

Thanks for double checking! 🙏


[Workflow] Unable to git push: Healthcheck error listing buckets

Hello,
I deployed Deis on an AWS multizone Kubernetes cluster. Trying to git push an app, the builder logs:
2016/08/19 16:32:41 Healthcheck error listing buckets (s3aws: NoSuchBucket: The specified bucket does not exist.
	status code: 404, request id: YDHA2ALY44G4WMX5)

Here is my deis builder config (describe pods)
Name:		deis-builder-2602787563-viu9x
Namespace:	deis
Node:		ip-172-20-0-5.eu-west-1.compute.internal/<IP_ADDRESS>
Start Time:	Thu, 18 Aug 2016 18:03:01 +0200
Labels:		app=deis-builder
		pod-template-hash=2602787563
Status:		Running
IP:		<IP_ADDRESS>
Controllers:	ReplicaSet/deis-builder-2602787563
Containers:
  deis-builder:
    Container ID:	docker://0a113f324c84b70898e54ca980d2b1196dd53ca1f984fc7931201db2e41f9c4a
    Image:		quay.io/deis/builder:v2.3.0
    Image ID:		docker://sha256:a9393d8e3e52e64b83337c04f8e5fd1292fcac19219b1306548b2636ad681de5
    Ports:		2223/TCP, 8092/TCP
    State:		Running
      Started:		Thu, 18 Aug 2016 23:12:03 +0200
    Last State:		Terminated
      Reason:		Error
      Exit Code:	2
      Started:		Thu, 18 Aug 2016 23:10:51 +0200
      Finished:		Thu, 18 Aug 2016 23:11:21 +0200
    Ready:		True
    Restart Count:	6
    Liveness:		http-get http://:8092/healthz delay=30s timeout=1s period=10s #success=1 #failure=3
    Readiness:		http-get http://:8092/readiness delay=30s timeout=1s period=10s #success=1 #failure=3
    Environment Variables:
      DEIS_REGISTRY_SERVICE_HOST:	localhost
      DEIS_REGISTRY_SERVICE_PORT:	5555
      HEALTH_SERVER_PORT:		8092
      EXTERNAL_PORT:			2223
      BUILDER_STORAGE:			minio
      DEIS_REGISTRY_LOCATION:		on-cluster
      DEIS_REGISTRY_SECRET_PREFIX:	private-registry
      GIT_LOCK_TIMEOUT:			60
      SLUGBUILDER_IMAGE_NAME:		quay.io/deis/slugbuilder:v2.3.0
      DOCKERBUILDER_IMAGE_NAME:		quay.io/deis/dockerbuilder:v2.3.0
      DOCKERIMAGE:			1
      DEIS_DEBUG:			false
      POD_NAMESPACE:			deis (v1:metadata.namespace)
      DEIS_BUILDER_KEY:			<set to the key 'builder-key' in secret 'builder-key-auth'>
Conditions:
  Type		Status
  Initialized 	True
  Ready 	True
  PodScheduled 	True
Volumes:
  builder-key-auth:
    Type:	Secret (a volume populated by a Secret)
    SecretName:	builder-key-auth
  builder-ssh-private-keys:
    Type:	Secret (a volume populated by a Secret)
    SecretName:	builder-ssh-private-keys
  objectstore-creds:
    Type:	Secret (a volume populated by a Secret)
    SecretName:	objectstorage-keyfile
  deis-builder-token-zxwbb:
    Type:	Secret (a volume populated by a Secret)
    SecretName:	deis-builder-token-zxwbb
QoS Tier:	BestEffort
Events:
  FirstSeen	LastSeen	Count	From							SubobjectPath			Type		Reason		Message
  ---------	--------	-----	----							-------------			--------	------		-------
  29m		3m		17	{kubelet ip-172-20-0-5.eu-west-1.compute.internal}	spec.containers{deis-builder}	Warning		Unhealthy	Liveness probe failed: HTTP probe failed with statuscode: 503

Any pointers on what could be wrong would be nice.
Regards,
Robin

hey @robinmonjo, would you mind posting the logs from minio? Sounds to me like there was an error creating the bucket, which could be resolved by restarting the builder via kubectl delete pod deis-builder-2602787563-viu9x (the replica set will create a new one).

Thank you for your answer. I restarted the builder and the minio. Got the same error. Here are the logs:
minio:
2016/08/19 17:09:46 starting Minio server
2016/08/19 17:09:46 starting health check server on <IP_ADDRESS>:8082
minio server /home/minio/
Migration from version ‘2’ to ‘3’ completed successfully.
Migration from version ‘3’ to ‘4’ completed successfully.

AccessKey: 8TZRY2JRWMPT6UMXR6I5  SecretKey: gbstrOvotMMcg2sMfGUhA5a6Et/EI5ALtIHsobYk  Region: us-east-1

Minio Object Storage:
    http://<IP_ADDRESS>:9000
    http://<IP_ADDRESS>:9000

Minio Browser:
    http://<IP_ADDRESS>:9000
    http://<IP_ADDRESS>:9000

To configure Minio Client:
    $ wget https://dl.minio.io/client/mc/release/linux-amd64/mc
    $ chmod 755 mc
    $ ./mc config host add myminio http://<IP_ADDRESS>:9000 8TZRY2JRWMPT6UMXR6I5 gbstrOvotMMcg2sMfGUhA5a6Et/EI5ALtIHsobYk

builder:
2016/08/19 17:10:24 Starting health check server on port 8092
2016/08/19 17:10:24 Starting deleted app cleaner
2016/08/19 17:10:24 Starting SSH server on <IP_ADDRESS>:2223
Listening on <IP_ADDRESS>:2223
Accepting new connections.
Accepted connection.
Starting ssh authentication
Channel type: session

Key='LC_CTYPE', Value='UTF-8'

receiving git repo name: mobicheckin.git, operation: git-receive-pack, fingerprint: e7:e7:75:50:72:ca:de:32:d8:96:5b:4f:12:65:f1:30, user: robin
creating repo directory /home/git/mobicheckin.git
writing pre-receive hook under /home/git/mobicheckin.git
git-shell -c git-receive-pack 'mobicheckin.git'
Waiting for git-receive to run.
Waiting for deploy.
---> ---> ---> ---> ---> ---> ---> ---> ---> ---> 2016/08/19 17:35:13 Healthcheck error listing buckets (s3aws: NoSuchBucket: The specified bucket does not exist.
	status code: 404, request id: JWXQ9H1IPOBC7YAQ)
2016/08/19 17:35:23 Healthcheck error listing buckets (s3aws: NoSuchBucket: The specified bucket does not exist.
	status code: 404, request id: KXISRSPF1C4Z6EOC)
2016/08/19 17:35:33 Healthcheck error listing buckets (s3aws: NoSuchBucket: The specified bucket does not exist.
	status code: 404, request id: IZUKL8APWVOF00YI)

ping @kmala, any ideas on how to dive down into this? I don't see any errors that would indicate that creating the bucket failed. :confused:

what does kubectl exec -it deis-minio-<> ls /home/minio --namespace=deis  say?
Also does this happen on a git push only because when the livenessprobe fails the builder will automatically restart and check to see if it has to create a new bucket. Did the builder fully start before doing a push?

From the logs in the OP, I see that the builder recently crashed, so maybe it's up for only a few seconds before it crashes.

Last State:     Terminated Reason:       Error Exit Code:    2 Started:      Thu, 18 Aug 2016 23:10:51 +0200 Finished:     Thu, 18 Aug 2016 23:11:21 +0200

@kmala
kubectl exec -it deis-minio-h7w2p ls /home/minio --namespace=deis
git  registry

This happens on a git push (havent tried the dockerfile way to deploy yet). Looks like that the builder was fully started according to the logs:
2016/08/19 17:10:24 Starting health check server on port 8092
2016/08/19 17:10:24 Starting deleted app cleaner
2016/08/19 17:10:24 Starting SSH server on <IP_ADDRESS>:2223
Listening on <IP_ADDRESS>:2223
Accepting new connections.
[...]

I left the system running during the night and this morning I had:
NAME                                      READY     STATUS             RESTARTS   AGE
deis-builder-2602787563-vc0jr             0/1       CrashLoopBackOff   165        16h
deis-controller-2433499717-rcny3          0/1       CrashLoopBackOff   111        1d
deis-database-9hvwo                       0/1       CrashLoopBackOff   77         1d
deis-logger-redis-0dd4b                   1/1       Running            0          1d
deis-logger-zsnjl                         1/1       Running            3          1d
deis-minio-h7w2p                          1/1       Running            0          16h
deis-monitor-grafana-wz6xw                1/1       Running            0          1d
deis-monitor-influxdb-v8yfj               1/1       Running            0          1d
deis-nsqd-w0dee                           1/1       Running            0          1d
deis-registry-3758253254-sme48            0/1       CrashLoopBackOff   170        1d
deis-router-1357759721-1lkb3              1/1       Running            0          1d
deis-workflow-manager-2813554381-wmwz9    1/1       Running            0          1d
slugbuild-mobicheckin-9e69a4d0-5e180cfe   0/1       ImagePullBackOff   0          16h
slugbuild-mobicheckin-9e69a4d0-e517b057   0/1       ImagePullBackOff   0          17h

Two pods from my two attempts to push were created (slugbuild-mobicheckin-9e69a4d0-5e180cfe and slugbuild-mobicheckin-9e69a4d0-e517b057). That surprised me as I thought the builder was responsible to build the slug. But anyway, I deleted those two pods and the others not in the "running" state, and end up with this:
NAME                                     READY     STATUS             RESTARTS   AGE
deis-builder-2602787563-y4uh6            0/1       Pending            0          35m
deis-controller-2433499717-1856l         0/1       Pending            0          37m
deis-database-c3enr                      0/1       CrashLoopBackOff   11         36m
deis-logger-redis-3czxr                  0/1       Pending            0          37m
deis-logger-zsnjl                        1/1       Running            3          1d
deis-minio-h7w2p                         1/1       Running            0          17h
deis-monitor-grafana-wz6xw               1/1       Running            0          1d
deis-monitor-influxdb-v8yfj              1/1       Running            0          1d
deis-nsqd-w0dee                          1/1       Running            0          1d
deis-registry-3758253254-ecihl           0/1       CrashLoopBackOff   11         36m
deis-router-1357759721-1lkb3             1/1       Running            0          1d
deis-workflow-manager-2813554381-wmwz9   1/1       Running            0          1d

Logs of the registry:
2016/08/20 10:37:34 INFO: Starting registry...
2016/08/20 10:37:34 INFO: using minio as the backend
panic: XMinioStorageFull: Storage backend has reached its minimum free disk threshold. Please delete few objects to proceed.
	status code: 500, request id: C1CDNB6W88L261Z7

goroutine 1 [running]:
panic(0xe1c2c0, 0xc8204141b0)
	/usr/lib/go-1.6/src/runtime/panic.go:481 +0x3e6
github.com/docker/distribution/registry/handlers.NewApp(0x7f55993f6298, 0xc820354060, 0xc8200718c0, 0x7f55993f6298)
	/go/src/github.com/docker/distribution/registry/handlers/app.go:121 +0x619
github.com/docker/distribution/registry.NewRegistry(0x7f55993f62d8, 0xc820354060, 0xc8200718c0, 0xc8200718c0, 0x0, 0x0)
	/go/src/github.com/docker/distribution/registry/registry.go:84 +0x2b0
github.com/docker/distribution/registry.glob.func1(0x13e7320, 0xc820332040, 0x1, 0x1)
	/go/src/github.com/docker/distribution/registry/registry.go:53 +0x2a9
github.com/docker/distribution/vendor/github.com/spf13/cobra.(*Command).execute(0x13e7320, 0xc8202ddff0, 0x1, 0x1, 0x0, 0x0)
	/go/src/github.com/docker/distribution/vendor/github.com/spf13/cobra/command.go:495 +0x6d4
github.com/docker/distribution/vendor/github.com/spf13/cobra.(*Command).Execute(0x13e74c0, 0x0, 0x0)
	/go/src/github.com/docker/distribution/vendor/github.com/spf13/cobra/command.go:560 +0x180
main.main()
	/go/src/github.com/docker/distribution/cmd/registry/main.go:23 +0x23
2016/08/20 10:37:34 Error starting the registryexit status 2

So the minio has reached its storage limit (the project I try to deploy is quite big slug after buildpack is aout 650 Mb).
And the logs of the database:
LOG:  MultiXact member wraparound protections are now enabled
LOG:  database system is ready to accept connections
LOG:  autovacuum launcher started
 done
server started
CREATE DATABASE

CREATE ROLE

/docker-entrypoint.sh: running /docker-entrypoint-initdb.d/001_setup_envdir.sh

/docker-entrypoint.sh: running /docker-entrypoint-initdb.d/002_create_bucket.sh
Traceback (most recent call last):
  File "/bin/create_bucket", line 73, in <module>
    conn.meta.client.head_bucket(Bucket=bucket_name)
  File "/usr/local/lib/python2.7/dist-packages/botocore/client.py", line 278, in _api_call
    return self._make_api_call(operation_name, kwargs)
  File "/usr/local/lib/python2.7/dist-packages/botocore/client.py", line 572, in _make_api_call
    raise ClientError(parsed_response, operation_name)
botocore.exceptions.ClientError: An error occurred (500) when calling the HeadBucket operation: Internal Server Error

So my questions are:

why does a pod get created for each build ? Does the builder is only responsible for receiving push and run the build in an other pod ?
why the minio is out of storage ? Should I override something to have a bigger volume ? I have plenty of disk space on my k8s nodes.
what's going on with the database pod ?
why do I had S3 bucket issues during my build, knowing that I haven't configured object storage as explained in this doc ?

Sorry for the long post really need to level up on Deis and know how to fix these kinds of issues before using it in production in my company.
Regards,
Robin

why does a pod get created for each build ? Does the builder is only responsible for receiving push and run the build in an other pod ?

Yes builder just runs a git server and is responsible for receiving the push and run the build in another pod(slugbuilder/dockerbuild) depending on the type of the app being deployed.This way multiple users can deploy different apps simultaneously.

why the minio is out of storage ? Should I override something to have a bigger volume ? I have plenty of disk space on my k8s nodes.

I think this an issue with the kubernetes not giving enough volume to the docker file system.
https://github.com/kubernetes/kubernetes/issues/14276
https://github.com/kubernetes/kubernetes/issues/25174

what's going on with the database pod ?

Database is trying to create a bucket for storing the backup but for some reason is failing and i think this might be because of the disk space issue.

why do I had S3 bucket issues during my build, knowing that I haven't configured object storage as explained in this doc ?

we use minio(https://github.com/deis/minio) for storage which has an s3 compatible api and you see s3 bucket issues as we use s3 api's for interacting with it.
You can check here for some of the prerequisites  https://deis.com/docs/workflow/quickstart/provider/aws/boot/

Thank you very much for all the information. Does Workflow recommend a k8s version ? I see in the article you sent, they say to use k8s 1.2.4. I'm running 1.3.4 right now. I don't see any doc about this.

you should be able to run on k8s 1.3.4 also.It is mentioned in https://deis.com/docs/workflow/installing-workflow/ but i think it needs to be mentioned in the individual docs also

Thank you, I will redeploy my k8s cluster with the option DOCKER_STORAGE=aufs-nolvm. This should prevent the short disk storage for docker. Plus, I dont really see the point of this disk ...
I'll keep you posted

On 21 Aug 2016, at 02:31, Keerthan Reddy Mala<EMAIL_ADDRESS>wrote:
you should be able to run on k8s 1.3.4 also.It is mentioned in https://deis.com/docs/workflow/installing-workflow/ but i think it needs to be mentioned in the individual docs also
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Ok so I redeploy my k8s cluster and have what I want (full disk for docker). I retried to git push but still have the same error (this time using workflow v2.4.1).
Builder logs:
2016/08/22 12:00:46 Starting health check server on port 8092
2016/08/22 12:00:46 Starting deleted app cleaner
2016/08/22 12:00:46 Starting SSH server on <IP_ADDRESS>:2223
Listening on <IP_ADDRESS>:2223
Accepting new connections.
---> ---> 2016/08/22 12:01:05 Readinesscheck endpoint timed out after 10s
2016/08/22 12:01:15 Readinesscheck endpoint timed out after 10s
2016/08/22 12:01:25 Readinesscheck endpoint timed out after 10s
2016/08/22 12:01:35 Readinesscheck endpoint timed out after 10s
2016/08/22 12:01:45 Readinesscheck endpoint timed out after 10s
2016/08/22 12:01:55 Readinesscheck endpoint timed out after 10s
2016/08/22 12:02:05 Readinesscheck endpoint timed out after 10s
2016/08/22 12:02:15 Readinesscheck endpoint timed out after 10s
Accepted connection.
Starting ssh authentication
Failed to authenticate user ssh key ... with the controller: Not Found
---> ---> ---> [ERROR] Failed handshake: EOF
Accepted connection.
Starting ssh authentication
Channel type: session

Key='LC_CTYPE', Value='UTF-8'

receiving git repo name: app.git, operation: git-receive-pack, fingerprint: ..., user: ...
creating repo directory /home/git/app.git
writing pre-receive hook under /home/git/app.git
git-shell -c git-receive-pack 'app.git'
Waiting for git-receive to run.
Waiting for deploy.
---> ---> ---> ---> ---> ---> ---> ---> 2016/08/22 12:58:45 Healthcheck error listing buckets (s3aws: NoSuchBucket: The specified bucket does not exist.
	status code: 404, request id: W5OXG2SA8KYP5RAT)
2016/08/22 12:58:55 Healthcheck error listing buckets (s3aws: NoSuchBucket: The specified bucket does not exist.
	status code: 404, request id: 4DOALIXLZIUCANIN)
2016/08/22 13:00:05 Healthcheck error listing buckets (s3aws: NoSuchBucket: The specified bucket does not exist.
	status code: 404, request id: VOTX93T1STH1LWWZ)
2016/08/22 13:00:45 Healthcheck error listing buckets (s3aws: NoSuchBucket: The specified bucket does not exist.
	status code: 404, request id: 4HGAJWKXV4505R0O)
2016/08/22 13:00:55 Healthcheck error listing buckets (s3aws: NoSuchBucket: The specified bucket does not exist.
	status code: 404, request id: LCLZ66S7AGBNMJR9)
2016/08/22 13:01:55 Healthcheck error listing buckets (s3aws: NoSuchBucket: The specified bucket does not exist.
	status code: 404, request id: 2R4MH7GN22HIRQBU)
2016/08/22 13:04:05 Healthcheck error listing buckets (s3aws: NoSuchBucket: The specified bucket does not exist.
	status code: 404, request id: X20S5V9DR2XQCSFA)

Minio logs:
2016/08/22 12:00:04 starting Minio server
2016/08/22 12:00:04 starting health check server on <IP_ADDRESS>:8082
minio server /home/minio/
Migration from version ‘2’ to ‘3’ completed successfully.
Migration from version ‘3’ to ‘4’ completed successfully.

AccessKey: ...  SecretKey: ...  Region: us-east-1

Minio Object Storage:
    http://<IP_ADDRESS>:9000
    http://<IP_ADDRESS>:9000

Minio Browser:
    http://<IP_ADDRESS>:9000
    http://<IP_ADDRESS>:9000

To configure Minio Client:
    $ wget https://dl.minio.io/client/mc/release/linux-amd64/mc
    $ chmod 755 mc
    $ ./mc config host add myminio http://<IP_ADDRESS>:9000 ... ...

Pods state:
NAME                                      READY     STATUS             RESTARTS   AGE
deis-builder-3309200110-air2i             1/1       Running            1          1h
deis-controller-2744468038-3zp19          1/1       Running            2          1h
deis-database-2hm2x                       1/1       Running            0          1h
deis-logger-fluentd-7ond2                 1/1       Running            0          1h
deis-logger-redis-tpd60                   1/1       Running            0          1h
deis-logger-tx4z5                         1/1       Running            3          1h
deis-minio-kf4z6                          1/1       Running            0          1h
deis-monitor-grafana-9qh6y                1/1       Running            0          1h
deis-monitor-influxdb-mew2w               1/1       Running            0          1h
deis-monitor-telegraf-b8pdb               1/1       Running            1          1h
deis-nsqd-fonb5                           1/1       Running            0          1h
deis-registry-3758253254-7dtuh            1/1       Running            4          1h
deis-router-1536869610-tlety              1/1       Running            0          1h
deis-workflow-manager-2813685453-x0zxb    1/1       Running            0          1h
slugbuild-app-be153528-51335b3b   0/1       ImagePullBackOff   0          15m

I checked minio manifests files but don't see anything related to a S3 bucket (can't we configure at leat the region ?). If it can help, my cluster is running in eu-west-1. Note that the slugbuild pod is in the ImagePullBackOff state ...

And after some times, the builder and the registry enter the CrashLoopBackOff state and tells me
Builder:
2016/08/22 13:22:03 Error creating storage driver (XMinioStorageFull: Storage backend has reached its minimum free disk threshold. Please delete few objects to proceed.
	status code: 500, request id: 46LD07EH9TCXIORP)

Registry:
2016/08/22 13:22:41 INFO: Starting registry...
2016/08/22 13:22:41 INFO: using minio as the backend
panic: XMinioStorageFull: Storage backend has reached its minimum free disk threshold. Please delete few objects to proceed.
	status code: 500, request id: IGQBBBC2PIQJ4347

goroutine 1 [running]:
panic(0xe1c2c0, 0xc8204141e0)
	/usr/lib/go-1.6/src/runtime/panic.go:481 +0x3e6
github.com/docker/distribution/registry/handlers.NewApp(0x7fb9add1d298, 0xc820352090, 0xc8200718c0, 0x7fb9add1d298)
	/go/src/github.com/docker/distribution/registry/handlers/app.go:121 +0x619
github.com/docker/distribution/registry.NewRegistry(0x7fb9add1d2d8, 0xc820352090, 0xc8200718c0, 0xc8200718c0, 0x0, 0x0)
	/go/src/github.com/docker/distribution/registry/registry.go:84 +0x2b0
github.com/docker/distribution/registry.glob.func1(0x13e7320, 0xc820330020, 0x1, 0x1)
	/go/src/github.com/docker/distribution/registry/registry.go:53 +0x2a9
github.com/docker/distribution/vendor/github.com/spf13/cobra.(*Command).execute(0x13e7320, 0xc8202ddfd0, 0x1, 0x1, 0x0, 0x0)
	/go/src/github.com/docker/distribution/vendor/github.com/spf13/cobra/command.go:495 +0x6d4
github.com/docker/distribution/vendor/github.com/spf13/cobra.(*Command).Execute(0x13e74c0, 0x0, 0x0)
	/go/src/github.com/docker/distribution/vendor/github.com/spf13/cobra/command.go:560 +0x180
main.main()
	/go/src/github.com/docker/distribution/cmd/registry/main.go:23 +0x23
2016/08/22 13:22:41 Error starting the registryexit status 2

while minio is still running and doesn't say more. However after double-ckecking, the disk space thing is still the same issue, docker root-dir is still on a tiny ephemeral 4Gb disk.

Ok using m3.large instances, I've got 32 Gb for docker storage and all the issues I experienced are gone. Thank you for your support.


DO NOT MERGE! Fast Forward stable to f83cee0533cbdea7fa229b06aac8719b1b59703f.

This PR will be merged automatically once checks are successful.

Jenkins job istio-testing/pr-stable passed


Correct improper usage and absence of try prefix

Functions that have partial variants should be prefixed with try; i.e., plookup is total and returns a PMaybe, whereas ptryLookup is partial and errors.
There are some functions in LPE that currently don't adhere to this, including pfromInlineDatum (which errors) and ptryFromOutputDatum (which returns a maybe).

moved to notion: https://www.notion.so/liqwid/Correct-improper-usage-and-absence-of-try-prefix-36448d9905cf4ec2bb46d0f81291a3a8


update deployed link & Linked In Pages

Type of Change

[ ] New feature
[X ] Refactoring / Bug fix
[ ] Documentation update

Going to do the same the same with the BE, there doesn't seem to be a readME at the moment!


Nobody can build when not in "admin" group

Hi,
i just installed vane on an already running server and now i have the problem that no one can build something in user/verified group, only if i add them to admin. At first i thought it has something todo with the Region plugin so i've set it to enabled: false but still only admins can build stuff. Do i miss something here?
I use the standard groups:
groups:
default:
- bukkit.command.help
- bukkit.broadcast
- bukkit.broadcast.user
verified:
- vane.permissions.groups.user
- vane.permissions.commands.vouch
admin:
- vane.permissions.groups.verified
- vane.admin.bypass_spawn_protection
- vane..commands.
user:
- vane.permissions.groups.default
- vane.admin.commands.spawn
- vane.admin.modify_world
- vane.regions.commands.region
- vane.trifles.commands.heads
No other plugins installed.

My first guess would be that you are within the spawn protection radius of 64 blocks around 0,0. Only admins can build in the spawn protected area. It is defined in vane-admin, so you can disable it in plugins/vane-admin/config.yml.