'CSRF verification failed' when trying to login

Hi, I have tried to test your docker image on two systems now, but each time I try to log in I get the following error in my browser

Forbidden (403)
CSRF verification failed. Request aborted.

Do you have any idea what the problem is?

@paulgit Could you please provide information on how you run the docker image?
Following information would be good:

Docker version
Which image is used (hash)
Environment variables given in the docker run command

Sorry, I should have sent that in my original post!

Docker version 1.13.1, build 092cba3
Image sha256:f053f35668022c5c89e0566451e8b5e4e3f8bb3b0d16e7357cd10e2356994398
Environment variables as follows:

docker run \
    -d \
    --name=healthchecks \
    -p 80:8000 \
    -e 'HC_HOST=<IP_ADDRESS>' \
    -e 'HC_SECRET_KEY={removed}' \
    -e 'HC_PING_EMAIL_DOMAIN=mydomain.com' \
    -e 'HC_SITE_ROOT=http://mydomain.com' \
    -e 'HC_EMAIL_HOST={removed}' \
    -e 'HC_EMAIL_PORT=25' \
    -e 'HC_EMAIL_USE_TLS=True' \
    -e 'HC_EMAIL_HOST_USER={removed}' \
    -e 'HC_EMAIL_HOST_PASSWORD={removed}' \
    -e 'HC_ALLOWED_HOSTS=["*"]' \
    galexrt/healthchecks:latest

I am trying to run this on Ubuntu 16.04.4

I have also just installed the latest docker and get the same error
Client:
 Version:       17.12.1-ce
 API version:   1.35
 Go version:    go1.9.4
 Git commit:    7390fc6
 Built: Tue Feb 27 22:17:40 2018
 OS/Arch:       linux/amd64

Server:
 Engine:
  Version:      17.12.1-ce
  API version:  1.35 (minimum version 1.12)
  Go version:   go1.9.4
  Git commit:   7390fc6
  Built:        Tue Feb 27 22:16:13 2018
  OS/Arch:      linux/amd64
  Experimental: false

Some further information, if I use your 'dev' version of the docker image I can log in ok

@paulgit The problem is that Healthchecks needs to be run behind https (with proxy protocol headers passed through).
The cookies for CSRF verification are only allowed to be sent through securely through https.
So to make healthchecks work, you need to put a https proxy in front of it.
An example on how to do that is https://github.com/jwilder/nginx-proxy.
I will add a note to the README that https is required.


options on setup are ignored

i'm using lazy.nvim for setup and i'm trying to override a single keymap, however, neither lazy.nvim's  opts key nor calling neocomposer's setup in a config function seem to achieve it.
in both cases the plugin seems to already be set up and the setup function does an early return.

I think there might be an issue with how I'm handling the setup. Let me take a look.

Thank you for bringing this to my attention. I just updated the setup. I was not handling it properly. I apologize. It should be working correctly now.

no worries. however, there is another issue connected to this. i may be wrong, but it looks like you'd prefer your plugin to not need a setup() call by the user, i assume that's why there's plugin/init.lua. the specific issue the automatic setup creates for me is that i have a mapping under <M-q> which it overwrites. technically i can get around it by creating my mapping after neocomposer's setup. ultimately it's your call how you want your plugin to act, but perhaps some things to consider here around the design:

it doesn't feel polite to overwrite the users' keymaps without them first having any say in it
setting any non-default settings means an additional setup() call
asking users to add require("plugin").setup() is already an established pattern

i think with something like lazy.nvim's config = true or opts = {} it's getting called anyway

I refactored the setup, as requested. Your settings should be saved. As far as the keymaps, you have made some valid points. The only keymap that I need to explicitly setup in the plugin is the toggle_record key as I need to filter that keymap from the recorded macro.

I had an idea for an interactive keymap setup wizard. Perhaps a command like :NeoComposerKeyamaps that the use call which will open an interactive buffer that you can edit with your desired keymaps.

thank you, i feel my concerns have been addressed


Portfolio - mobile menu: module 1

Dom implementation on Html elements milestone:- module 1
This dom implementation includes the following tasks:-

Added querySelector to mobile menu selectors of CSS to my dom file of the portfolio
Added querySelector to the links selector of CSS to the dom file of the portfolio
Added querySelector to close button of CSS selector in my portfolio

https://docs.google.com/document/d/1x7SyEmCa41vbluLoYo22z_gOwKmHOGvcYYh9KuAEzb0/edit?usp=sharing


The user interface is not consistent with the OS X Human Interface Guidelines.

The build 259 has been rejected by Mac App Store reviewer due to:

The user interface is not consistent with the OS X Human Interface Guidelines.

We have found that when the user closes the main application window there is no menu item to re-open it. The app should implement a Window menu that lists the main window so it can be reopened, or provide similar functionality in another menu item. OS X Human Interface Guidelines, state that "The menu bar [a]lways contains [a] Window menu".

Alternatively, if the application is a single-window app, it might be appropriate to save data and quit the app when the main window is closed.

Anyway, I'll fix it asap.

Okay, fixed in 52a423dbbc77854c37bf394e9ac0783715eacb4e. Have a good day.


Fix missing letter and add FAQ section to README

I'm really tired, so to be honest I don't trust myself on even the simple things.

I'm really tired, so to be honest I don't trust myself on even the simple things.

I can finish this myself if you like

I can finish this myself if you like

I'm happy to finish this up as long as it's just getting these changes ready.

Thanks!


Add vgclib

It would be great to have a port of the vcglib library ( https://github.com/cnr-isti-vclab/vcglib ) .

The vcglib is also a dependency of the openMVS project, see https://github.com/Microsoft/vcpkg/issues/2952 .


SDK uses own version of Jetty and webdefault.xml for quickstart

The gcloud SDK uses a bundled version of jetty and its own copy of webdefault.xml to generate the quickstart configuration for an application.
If the image used by GAE is updated, or if a custom image is used, then the quickstart-web.xml file generated may be incorrect.

Potentially a docker cp command could be used to extract the webdefault.xml from the target image.  Potentially it could extract the jetty distribution as well.

One solution would be to select which webdefault.xml is used to do the generation rather than using the bundled file.
It looks like you are using a class called com/google/appengine/tools/development/jetty9/QuickStartGenerator.java class inside the special quickstartgenerator.jar that is part of the sdk.
I can't see the source for that class in any of the google repos I have access to but as far as I can tell using javap,  you should be able to modify it to use a remote webdefault.xml of your choosing quite easily.
Looks like you should be able to modify line 98 which calls QuickStartWebapp.setDefaultsDescriptor().
You can call this method with a url to point to a file on the local file system or a remote server.  For example:

to use a custom webdefault.xml file on the local server filesystem you can do:
webapp.setDefaultsDescriptor("file:///some/local/path/to/somewebdefault.xml");

to use a custom webdefault.xml file served by a remote server on port 8080 you can do:
webapp.setDefaultsDescriptor("http://somehost:8080/somecontext/somewebdefault.xml");

So we need to work out how to publish a webdefaults.xml that the SDK can choose based on the deployment target.  The URL to the master version of it is
https://raw.githubusercontent.com/GoogleCloudPlatform/appengine-java-vm-runtime/master/appengine-jetty-managed-runtime/src/main/docker/etc/webdefault.xml

So the SDK would just need to know a tag to target and could s/master/tag/ in that URL


Samsung Android 11: ChimeraPolicyHandler killing foreground services

After upgrading my Galaxy A51 from Android 10 to Android 11, it has started periodically (or randomly) killing my two XMPP client apps, yaxim and Bruno, despite both having a permanent (and visible) foreground service notification.
Ironically, the OS recognizes those kills as a crash and immediately restarts the app, causing a large amount of unneeded network traffic:
03-22 08:55:09.470  5028 10568 I ChimeraPolicyHandler: Killed on trigger2 : org.yaxim.bruno, freed: 34707, 10202[4548]:G2(0x20000) score=26,8(39 5 34707), pids: 4548 / stats: 4 / adjs: 200
[...]
03-22 08:55:09.585  5028 11722 I ActivityManager: Process org.yaxim.bruno (pid 4548) has died: prcp FGS (175,635)
03-22 08:55:09.586  5028 11722 W ActivityManager: Scheduling restart of crashed service org.yaxim.bruno/org.yaxim.androidclient.service.XMPPService in 1000ms for start-requested

Even more ironically, it also keeps resurrecting (auto-starting) apps that I have manually force-stopped before.
The ChimeraPolicyHandler seems to be a job running multiple times per hour in the system_server process. ps shows:
system         5028   4601 12953324 266152 0                  0 S system_server

Full log of one ChimeraPolicyHandler run:
03-22 08:55:09.288  5028 10568 I ChimeraPolicyHandler: Start executePolicy: TRIGGER_SOURCE_HOME_IDLE
03-22 08:55:09.293  5028 10568 I ChimeraPolicyHandler: memAvailable: 750256, memFreeTarget: 890880, releaseTarget:140624, protectedLruCount: 6
03-22 08:55:09.403  5028 10568 I ChimeraPolicyHandler: Start doKill, protected policy: NORMAL
03-22 08:55:09.405  5028 10568 I ChimeraPolicyHandler: Skipped by adj     : com.google.android.googlequicksearchbox, 10230[20349,14885]:G1(0x1) score=55,7(23 40 127100), pids: 20349 14885 / stats: 10 5 / adjs: 800 100
03-22 08:55:09.405  5028 10568 I ChimeraPolicyHandler: Skipped by interval: com.samsung.android.oneconnect, elapsed: 00:54:50, interval: 04:00:00, 10255[12960,13390]:G1(0x1) score=33,4(35 10 67797), pids: 12960 13390 / stats: 8 8 / adjs: 200 200
03-22 08:55:09.405  5028 10568 I ChimeraPolicyHandler: Skipped by adj     : com.android.vending, 10226[25018]:G1(0x1) score=13,0(3 5 51575), pids: 25018 / stats: 12 / adjs: 100
03-22 08:55:09.405  5028 10568 I ChimeraPolicyHandler: Skipped by adj     : com.android.systemui, 10054[10714]:G2(0x20000) score=76,0(65 10 240771), pids: 10714 / stats: 5 / adjs: -800
03-22 08:55:09.405  5028 10568 I ChimeraPolicyHandler: Skipped by adj     : com.google.android.ext.services, 10080[24237,24270]:G2(0x20000) score=48,5(43 40 27866), pids: 24237 24270 / stats: 5 5 / adjs: 100 100
03-22 08:55:09.406  5028 10568 I ChimeraPolicyHandler: Skipped by adj     : com.google.android.as, 10284[24194,24200]:G2(0x20000) score=42,9(34 40 19282), pids: 24194 24200 / stats: 5 5 / adjs: 100 100
03-22 08:55:09.406  5028 10568 I ChimeraPolicyHandler: Skipped by adj     : com.samsung.android.dynamiclock, 10070[21726]:G2(0x20000) score=34,0(15 40 18505), pids: 21726 / stats: 5 / adjs: 0
03-22 08:55:09.406  5028 10568 I ChimeraPolicyHandler: Skipped by adj     : com.samsung.android.app.telephonyui, 1001[27531]:G2(0x20002) score=31,1(48 5 36007), pids: 27531 / stats: 5 / adjs: 0
03-22 08:55:09.406  5028 10568 I ChimeraPolicyHandler: Skipped by adj     : com.sec.location.nsflp2, 5013[11278]:G2(0x20002) score=31,1(57 5 10969), pids: 11278 / stats: 5 / adjs: 100
03-22 08:55:09.406  5028 10568 I ChimeraPolicyHandler: Skipped by adj     : com.samsung.android.knox.containercore, 5250[11455]:G2(0x20002) score=28,6(53 5 6891), pids: 11455 / stats: 5 / adjs: 100
03-22 08:55:09.406  5028 10568 I ChimeraPolicyHandler: Skipped by adj     : com.samsung.android.server.wifi.mobilewips, 1000[5432]:G2(0x20002) score=28,5(50 5 14599), pids: 5432 / stats: 6 / adjs: 100
03-22 08:55:09.410  5028 10568 I ChimeraPolicyHandler: Skipped by uid     : com.samsung.android.beaconmanager, 5006[19846]:G2(0x20002) score=28,2(52 5 7092), pids: 19846 / stats: 8 / adjs: 200
03-22 08:55:09.410  5028 10568 I ChimeraPolicyHandler: Skipped by adj     : com.sec.epdg, 1000[17442]:G2(0x20002) score=27,9(49 5 13754), pids: 17442 / stats: 6 / adjs: 100
03-22 08:55:09.411  5028 10568 I ChimeraPolicyHandler: Skipped by adj     : org.kde.kdeconnect_tp, 10393[14802]:G2(0x8) score=27,8(26 20 22970), pids: 14802 / stats: 4 / adjs: 100
03-22 08:55:09.414  5028 10568 I ChimeraPolicyHandler: Skipped by uid     : com.samsung.android.themecenter, 1000[10830]:G2(0x20002) score=27,6(51 5 6306), pids: 10830 / stats: 8 / adjs: 200
03-22 08:55:09.415  5028 10568 I ChimeraPolicyHandler: Skipped by interval: org.yaxim.bruno, elapsed: 00:52:29, interval: 04:00:00, 10202[4548]:G2(0x20000) score=26,8(39 5 34707), pids: 4548 / stats: 4 / adjs: 200
03-22 08:55:09.416  5028 10568 I ChimeraPolicyHandler: Skipped by interval: com.sec.android.easyonehand, elapsed: 00:51:40, interval: 04:00:00, 10201[5926]:G2(0x20000) score=23,6(38 5 18683), pids: 5926 / stats: 8 / adjs: 200
03-22 08:55:09.425  5028 10568 I ChimeraPolicyHandler: Skipped by Normal Service condition: com.samsung.android.providers.contacts, 15010062[7334,6035]:G2(0xa0000) score=23,5(29 5 42946), pids: 7334 6035 / stats: 19 19 / adjs: 915 850  reason: ACTIVITY_TIME
03-22 08:55:09.425  5028 10568 I ChimeraPolicyHandler: Skipped by adj     : com.samsung.android.mcfserver, 1000[12405]:G2(0x20002) score=21,2(36 5 9534), pids: 12405 / stats: 6 / adjs: 100
03-22 08:55:09.426  5028 10568 I ChimeraPolicyHandler: Skipped by interval: com.samsung.android.bixby.agent, elapsed: 00:25:49, interval: 04:00:00, 5018[18287]:G2(0x20002) score=20,4(32 5 15738), pids: 18287 / stats: 10 / adjs: 800
03-22 08:55:09.426  5028 10568 I ChimeraPolicyHandler: Skipped by adj     : com.samsung.android.smartsuggestions, 10475[20029,19131]:G2(0x20000) score=18,3(22 10 13072), pids: 20029 19131 / stats: 5 5 / adjs: 100 100
03-22 08:55:09.426  5028 10568 I ChimeraPolicyHandler: Skipped by interval: android, elapsed: 00:51:40, interval: 04:00:00, 1000[19042]:G2(0x20002) score=18,3(31 5 5917), pids: 19042 / stats: 10 / adjs: 800
03-22 08:55:09.426  5028 10568 I ChimeraPolicyHandler: Skipped by interval: com.samsung.android.svcagent, elapsed: 00:51:40, interval: 04:00:00, 1000[19085]:G2(0x20002) score=17,8(30 5 5645), pids: 19085 / stats: 10 / adjs: 500
03-22 08:55:09.427  5028 10568 I ChimeraPolicyHandler: Skipped by adj     : org.yaxim.androidclient, 10409[13822]:G2(0x20000) score=15,5(4 5 64062), pids: 13822 / stats: 4 / adjs: 50
03-22 08:55:09.430  5028 10568 I ChimeraPolicyHandler: Skipped by Normal Service condition: com.samsung.android.stickercenter, 1000[16950]:G2(0x20002) score=13,8(20 5 9228), pids: 16950 / stats: 15 / adjs: 700  reason: ACTIVITY_TIME
03-22 08:55:09.434  5028 10568 I ChimeraPolicyHandler: Skipped by Normal Service condition: com.android.providers.calendar, 10102[18783]:G2(0x20000) score=13,1(19 5 8293), pids: 18783 / stats: 15 / adjs: 700  reason: ACTIVITY_TIME
03-22 08:55:09.435  5028 10568 I ChimeraPolicyHandler: Skipped by adj     : com.samsung.android.biometrics.app.setting, 1000[21738]:G2(0x20002) score=11,1(13 5 12861), pids: 21738 / stats: 5 / adjs: 100
03-22 08:55:09.435  5028 10568 I ChimeraPolicyHandler: kill complete: killed 0 apps, freed 0 KB
03-22 08:55:09.435  5028 10568 I ChimeraPolicyHandler: Start doKill, protected policy: HEAVY
03-22 08:55:09.435  5028 10568 I ChimeraPolicyHandler: Skipped by adj     : com.google.android.googlequicksearchbox, 10230[20349,14885]:G1(0x1) score=55,7(23 40 127100), pids: 20349 14885 / stats: 10 5 / adjs: 800 100
03-22 08:55:09.437  5028 10568 I ChimeraPolicyHandler: Killed on trigger2 : com.samsung.android.oneconnect, freed: 67797, 10255[12960,13390]:G1(0x1) score=33,4(35 10 67797), pids: 12960 13390 / stats: 8 8 / adjs: 200 200
03-22 08:55:09.443  5028 10568 I ChimeraPolicyHandler: Skipped by adj     : com.android.vending, 10226[25018]:G1(0x1) score=13,0(3 5 51575), pids: 25018 / stats: 12 / adjs: 100
03-22 08:55:09.443  5028 10568 I ChimeraPolicyHandler: Skipped by adj     : com.android.systemui, 10054[10714]:G2(0x20000) score=76,0(65 10 240771), pids: 10714 / stats: 5 / adjs: -800
03-22 08:55:09.450  5028 10568 I ChimeraPolicyHandler: Killed on trigger2 : com.google.android.ext.services, freed: 27866, 10080[24237,24270]:G2(0x20000) score=48,5(43 40 27866), pids: 24237 24270 / stats: 5 5 / adjs: 100 100
03-22 08:55:09.456  5028 10568 I ChimeraPolicyHandler: Killed on trigger2 : com.google.android.as, freed: 19282, 10284[24194,24200]:G2(0x20000) score=42,9(34 40 19282), pids: 24194 24200 / stats: 5 5 / adjs: 100 100
03-22 08:55:09.457  5028 10568 I ChimeraPolicyHandler: Skipped by adj     : com.samsung.android.dynamiclock, 10070[21726]:G2(0x20000) score=34,0(15 40 18505), pids: 21726 / stats: 5 / adjs: 0
03-22 08:55:09.457  5028 10568 I ChimeraPolicyHandler: Skipped by adj     : com.samsung.android.app.telephonyui, 1001[27531]:G2(0x20002) score=31,1(48 5 36007), pids: 27531 / stats: 5 / adjs: 0
03-22 08:55:09.457  5028 10568 I ChimeraPolicyHandler: Skipped by adj     : com.sec.location.nsflp2, 5013[11278]:G2(0x20002) score=31,1(57 5 10969), pids: 11278 / stats: 5 / adjs: 100
03-22 08:55:09.458  5028 10568 I ChimeraPolicyHandler: Skipped by adj     : com.samsung.android.knox.containercore, 5250[11455]:G2(0x20002) score=28,6(53 5 6891), pids: 11455 / stats: 5 / adjs: 100
03-22 08:55:09.458  5028 10568 I ChimeraPolicyHandler: Skipped by adj     : com.samsung.android.server.wifi.mobilewips, 1000[5432]:G2(0x20002) score=28,5(50 5 14599), pids: 5432 / stats: 6 / adjs: 100
03-22 08:55:09.460  5028 10568 I ChimeraPolicyHandler: Skipped by uid     : com.samsung.android.beaconmanager, 5006[19846]:G2(0x20002) score=28,2(52 5 7092), pids: 19846 / stats: 8 / adjs: 200
03-22 08:55:09.461  5028 10568 I ChimeraPolicyHandler: Skipped by adj     : com.sec.epdg, 1000[17442]:G2(0x20002) score=27,9(49 5 13754), pids: 17442 / stats: 6 / adjs: 100
03-22 08:55:09.461  5028 10568 I ChimeraPolicyHandler: Skipped by adj     : org.kde.kdeconnect_tp, 10393[14802]:G2(0x8) score=27,8(26 20 22970), pids: 14802 / stats: 4 / adjs: 100
03-22 08:55:09.465  5028 10568 I ChimeraPolicyHandler: Skipped by uid     : com.samsung.android.themecenter, 1000[10830]:G2(0x20002) score=27,6(51 5 6306), pids: 10830 / stats: 8 / adjs: 200
03-22 08:55:09.470  5028 10568 I ChimeraPolicyHandler: Killed on trigger2 : org.yaxim.bruno, freed: 34707, 10202[4548]:G2(0x20000) score=26,8(39 5 34707), pids: 4548 / stats: 4 / adjs: 200
03-22 08:55:09.509  5028 10568 I ChimeraPolicyHandler: Killed on trigger2 : com.sec.android.easyonehand, freed: 18683, 10201[5926]:G2(0x20000) score=23,6(38 5 18683), pids: 5926 / stats: 8 / adjs: 200
03-22 08:55:09.599  5028 10568 I ChimeraPolicyHandler: Killed on trigger2 : com.samsung.android.providers.contacts, freed: 42946, 15010062[7334,6035]:G2(0xa0000) score=23,5(29 5 42946), pids: 7334 6035 / stats: 19 19 / adjs: 915 850
03-22 08:55:09.635  5028 10568 I ChimeraPolicyHandler: Skipped by adj     : com.samsung.android.mcfserver, 1000[12405]:G2(0x20002) score=21,2(36 5 9534), pids: 12405 / stats: 6 / adjs: 100
03-22 08:55:09.675  5028 10568 I ChimeraPolicyHandler: Killed on trigger2 : com.samsung.android.bixby.agent, freed: 15738, 5018[18287]:G2(0x20002) score=20,4(32 5 15738), pids: 18287 / stats: 10 / adjs: 800
03-22 08:55:09.723  5028 10568 I ChimeraPolicyHandler: Skipped by adj     : com.samsung.android.smartsuggestions, 10475[20029,19131]:G2(0x20000) score=18,3(22 10 13072), pids: 20029 19131 / stats: 5 5 / adjs: 100 100
03-22 08:55:09.724  5028 10568 I ChimeraPolicyHandler: Skipped by wakelock       : android, 1000[19042]:G2(0x20002) score=18,3(31 5 5917), pids: 19042 / stats: 10 / adjs: 800
03-22 08:55:09.732  5028 10568 I ChimeraPolicyHandler: Skipped by uid     : com.samsung.android.svcagent, 1000[19085]:G2(0x20002) score=17,8(30 5 5645), pids: 19085 / stats: 10 / adjs: 500
03-22 08:55:09.732  5028 10568 I ChimeraPolicyHandler: Skipped by adj     : org.yaxim.androidclient, 10409[13822]:G2(0x20000) score=15,5(4 5 64062), pids: 13822 / stats: 4 / adjs: 50
03-22 08:55:09.743  5028 10568 I ChimeraPolicyHandler: Skipped by uid     : com.samsung.android.stickercenter, 1000[16950]:G2(0x20002) score=13,8(20 5 9228), pids: 16950 / stats: 15 / adjs: 700
03-22 08:55:09.757  5028 10568 I ChimeraPolicyHandler: Killed on trigger2 : com.android.providers.calendar, freed: 8293, 10102[18783]:G2(0x20000) score=13,1(19 5 8293), pids: 18783 / stats: 15 / adjs: 700
03-22 08:55:09.768  5028 10568 I ChimeraPolicyHandler: Skipped by adj     : com.samsung.android.biometrics.app.setting, 1000[21738]:G2(0x20002) score=11,1(13 5 12861), pids: 21738 / stats: 5 / adjs: 100
03-22 08:55:09.768  5028 10568 I ChimeraPolicyHandler: kill complete: killed 8 apps, freed 235312 KB
03-22 08:55:09.768  5028 10568 I ChimeraPolicyHandler: Processing time(ms) 480

Hello, I think this supports the theory that in fact at least of the new issues on Samsung after Android 11 could be accounted to memory management issues. So IMHO Samsung did memory leaks in their Android 11 so the memory on your phone periodically runs out and this is a standard Android feature to kill processes to regain memory. We have seen such issues especially on Moto G phones in the past which were notorious for memory leaks. This issue basically does that all services get restarted from time to time on your devcie which causes performance issues and of course apps may not work properly.. this issue is on Samsung to fix IMHO..

I've seen the OOM killer in the past, but I'm pretty sure it wasn't advertising itself as "ChimeraPolicyHandler", and I can't find any reference to "ChimeraPolicyHandler" in the AOSP, so I tend to think this is some Samsung magic at work. It also seems to have some whitelist of processes / UIDs ("Skipped by uid"), but maybe that only really whitelists the system process.

In the app I work it is happening the same. I have a Samsung 20 with the latest Android 11 (security patch 01-03-2021).
I have a foreground service and I've already put the app (org.myapp.msg.dev) in Battery optimization ignored list. I don't know what to do anymore.
I would like to know how "ChimeraPolicyHandler" selects the app to be killed. Samsung should be more transparent in this aspect.
04-06 13:31:10.486 12542 12601 I CameraPerformance: Device - StartPreviewRequest : End[1617726670486]
04-06 13:31:10.486 12542 12542 I Camera11: onStartPreviewCompleted
04-06 13:31:10.486 12542 12542 I VerificationLog: Executed
04-06 13:31:10.486 12542 12542 I CameraPerformance: Launch - LazyLoading : Start[1617726670486]
04-06 13:31:10.486   722 12691 I<EMAIL_ADDRESS>[CAMKPI] camera3->process_capture_result : X
04-06 13:31:10.486 12542 12542 I CameraPerformance: ShootingMode - onActivate(Photo) : Start[1617726670486]
04-06 13:31:10.486  1142  3027 D FreecessController: Receive signal-module info(callerPid:0,uid:10302) from freecessmonitor
04-06 13:31:10.487 12542 12542 I ZoomPresenter: refreshProperty zoomCategory: NOT_SUPPORT, supportUiSet: [], zoomPositionType:NORMAL, buttonList: [], defaultButtonValue: -1
04-06 13:31:10.487 12542 12542 I KeyScreenLayerPresenter: onShowViewRequested mBitMarker ffffffff mBitMarkerForViewVisibility ffffffff
04-06 13:31:10.488 12542 12542 I RequestQueue: addRequest : APPLY_SETTINGS, com.sec.android.app.camera.engine.-$$Lambda$CommonEngine$BFOhyHc3pFR3i5NQnW-Mb3hrQv4@7c3a324
04-06 13:31:10.488 12542 12542 I RequestQueue: addRequest : SET_PRIVATE_SETTING, enable_intelligent_guide : true
04-06 13:31:10.488 12542 12602 I RequestQueue: beforeExecute : APPLY_SETTINGS(5601)
04-06 13:31:10.488 12542 12602 I RequestQueue: [5601] [5600 ]
04-06 13:31:10.488 12542 12602 I Request : ApplySettingsRequest - Start
04-06 13:31:10.488 12542 12602 W Request : ApplySettingsRequest : Returned, no need to set maker public settings
04-06 13:31:10.488 12542 12602 I Request : ApplySettingsRequest - End
04-06 13:31:10.488 12542 12602 I RequestQueue: afterExecute : APPLY_SETTINGS(5601)
04-06 13:31:10.488 12542 12602 I RequestQueue: [  ] [5600 ]
04-06 13:31:10.488 12542 12602 I RequestQueue: beforeExecute : SET_PRIVATE_SETTING(5600)
04-06 13:31:10.488 12542 12542 I RequestQueue: addRequest : APPLY_SETTINGS, com.sec.android.app.camera.engine.-$$Lambda$CommonEngine$BKOYlYOg5vRBvBdEi-lMokuUNwg@329cd90
04-06 13:31:10.488 12542 12602 I RequestQueue: [5600] []
04-06 13:31:10.488 12542 12542 I RequestQueue: addRequest : SET_PRIVATE_SETTING, enable_sw_face_detection : true
04-06 13:31:10.488 12542 12602 I Request : SetPrivateSettingRequest - Start
04-06 13:31:10.488 12542 12542 I BroadcastUtil: notifyCameraInfo : Start
04-06 13:31:10.488 12542 12602 I Request : execute key = MakerPrivateKey(enable_intelligent_guide) value = true
04-06 13:31:10.488 12542 12602 I V1/IntelligentGuideNode: initialize - activate true, asyncInit false
04-06 13:31:10.489 12542 12542 I BroadcastUtil: notifyCameraInfo : End
04-06 13:31:10.489 12542 12542 W Camera11: There is no registered HRM Shutter listener. return.
04-06 13:31:10.489 12542 12542 I LayerManagerView: setKeyScreenLayerVisibility: true
04-06 13:31:10.489  2115 12794 D SystemUIService: summary.java-heap : 25760
04-06 13:31:10.489  2115 12794 D SystemUIService: summary.native-heap : 42764
04-06 13:31:10.489  2115 12794 D SystemUIService: summary.code : 24444
04-06 13:31:10.489  2115 12794 D SystemUIService: summary.stack : 916
04-06 13:31:10.489  2115 12794 D SystemUIService: summary.graphics : 0
04-06 13:31:10.489  2115 12794 D SystemUIService: summary.private-other : 16616
04-06 13:31:10.489  2115 12794 D SystemUIService: summary.system : 98918
04-06 13:31:10.489  2115 12794 D SystemUIService: summary.total-pss : 209418
04-06 13:31:10.489  1142  3027 D FreecessController: UFZ : org.mozilla.focus(8333)
04-06 13:31:10.489  2115 12794 D SystemUIService: summary.total-swap : 109656
04-06 13:31:10.489  2115 12794 D SystemUIService:  - View count -
04-06 13:31:10.489   698   698 D gralloc : [mali_gralloc_allocate] begin
04-06 13:31:10.489   698   698 D gralloc : buffer_descriptor: wh(2400 1080) usage_pc(0x20006 0x20006) hal_format(0x23) layer_count(1) sizes(0 0 0) strde(0) byte_stride(0) alloc_wh(0 0) internal_format(0x0) alloc_format(0x0) fd_count(1) plane_count(0)
04-06 13:31:10.489 12542 12542 I ZoomPresenter: refreshProperty zoomCategory: FOV, supportUiSet: [BUTTON], zoomPositionType:NORMAL, buttonList: [Pair{FRONT_CAMERA_ANGLE_FULL 0}, Pair{FRONT_CAMERA_ANGLE_CROP 1}], defaultButtonValue: 1
04-06 13:31:10.489  1142  3027 D FreecessController: UFZ : org.mozilla.focus(0), reason: Signal
04-06 13:31:10.490  7154  7186 W BtGatt.GattService: unfreezeScan() - No AppScanStats found with uid: 10302
04-06 13:31:10.490   678   791 E TrafficController: FREECESS
04-06 13:31:10.491   698   698 D gralloc : [mali_gralloc_allocate] allocation successful
04-06 13:31:10.492  3813  3813 I F0      : limitGPUFreq:: freq = -1
04-06 13:31:10.492  3813  3813 I F0      : limitCPUFreq:: freq = -1
04-06 13:31:10.492  1142  2818 D FreecessController: apply [LRs:false] to uid[10302]
04-06 13:31:10.492  1142  2818 W LocationManagerService: onFreezeStateChanged, uid[10302]=false
04-06 13:31:10.493  1142  2818 V AlarmManager: unblockMARsRestrictedAlarmsForUidPackage: uid = 10302, packageName = null
04-06 13:31:10.493  1142  2818 D FreecessController: send pending alarm to packageName:null, uid:10302
04-06 13:31:10.493  1142  2818 I PowerManagerService: [PWL] SetWakeLockEnableDisable uid = 10302 , disable= false
04-06 13:31:10.493  1142  2818 I PowerManagerService: [PWL] can not change uid =  10302
04-06 13:31:10.493 12542 12607 I BeautyPhotoMaker: sendDynamicShotInfoCallback - TimeStamp(59740050055731) dynamicShotInfo(processingMode = 0x200000, dsCondition = 0xCE, dsMode = SINGLE, dsExtraInfo = 0x200000, dsDeviceInfo = 0x7A10303) camDevice: CamDeviceImpl(acecf83) - id(3)
04-06 13:31:10.493 12542 12607 I BeautyPhotoMaker: sendDynamicShotCaptureDurationCallback - TimeStamp(59740050055731) dynamicShotCaptureDuration(0) camDevice: CamDeviceImpl(acecf83) - id(3)
04-06 13:31:10.494 12542 12607 I BeautyPhotoMaker: sendLightConditionCallback - TimeStamp(59740050055731) LightCondition(0x21) camDevice: CamDeviceImpl(acecf83) - id(3)
04-06 13:31:10.494 12542 12601 I CallbackManager: onLightConditionChanged : lightCondition=LLS_FLASH(33)
04-06 13:31:10.494 12542 12601 I BurstCaptureController: onBurstShotFpsChanged : burstShotFps=20
04-06 13:31:10.494 12542 12607 I BeautyPhotoMaker: sendBurstShotFpsCallback - TimeStamp(59740050055731) BurstShotFps(20) camDevice: CamDeviceImpl(acecf83) - id(3)
04-06 13:31:10.496   710  1689 I Sensors : Light_IR_Sensor irdata=7 r=245, g=132, b=63, c=12, ir_atime/ir_brightness=120, ir_again=0, time=59740302660349
04-06 13:31:10.501 12542 12542 I RequestQueue: addRequest : SET_PRIVATE_SETTING, enable_motion_photo_ppp : false
04-06 13:31:10.501 12542 12542 I RequestQueue: addRequest : SET_PRIVATE_SETTING, enable_face_shape_correction : false
04-06 13:31:10.503 12542 12542 I CameraPerformance: ShootingMode - onActivate(Photo) : End[1617726670503] [17]
04-06 13:31:10.504  2115 12794 D SystemUIService: View=2046
04-06 13:31:10.504 12542 12542 I CameraOrientationEvtMgr: orientation listener enabled 0
04-06 13:31:10.504  1142  4184 D SemContextService: lock : registerCallback
04-06 13:31:10.505  1142  4184 D SemContextService: EventInfo.sendEvent() : service = Auto Rotation, listener = com.samsung.android.hardware.context.SemContextService$Listener@cea3c76
04-06 13:31:10.505  1142  4184 W Binder  : Outgoing transactions from this process must be FLAG_ONEWAY
04-06 13:31:10.505  1142  4184 W Binder  : java.lang.Throwable
04-06 13:31:10.505  1142  4184 W Binder  : 	at android.os.BinderProxy.transact(BinderProxy.java:514)
04-06 13:31:10.505  1142  4184 W Binder  : 	at com.samsung.android.hardware.context.ISemContextCallback$Stub$Proxy.getListenerInfo(ISemContextCallback.java:162)
04-06 13:31:10.505  1142  4184 W Binder  : 	at com.samsung.android.hardware.context.SemContextService$ListenerManager.notifyListeners(SemContextService.java:1332)
04-06 13:31:10.505  1142  4184 W Binder  : 	at com.samsung.android.hardware.context.SemContextService.registerCallback(SemContextService.java:259)
04-06 13:31:10.505  1142  4184 W Binder  : 	at com.samsung.android.hardware.context.ISemContextService$Stub.onTransact(ISemContextService.java:156)
04-06 13:31:10.505  1142  4184 W Binder  : 	at android.os.Binder.execTransactInternal(Binder.java:1190)
04-06 13:31:10.505  1142  4184 W Binder  : 	at android.os.Binder.execTransact(Binder.java:1159)
04-06 13:31:10.505  1142  4184 D SemContextService: 	.registerCallback : 7, client=com.sec.android.app.camera.provider.CameraOrientationEventManager@e5f75d
04-06 13:31:10.505  1142  4184 D SemContextConnectionList: client packageName : com.sec.android.app.camera.provider.CameraOrientationEventManager@e5f75d
04-06 13:31:10.505  1142  4184 D SemContextService: unlock : registerCallback
04-06 13:31:10.505 12542 12542 I CameraExecutorManager: initialize
04-06 13:31:10.506 12542 12681 I FaceLandmarkSolution: FL Engine version : ArcSoft_FaceLandmark_2.0.125231001.371_#21049-5-B18695
04-06 13:31:10.506 12542 12681 I FaceLandmarkSolution: FL Wrapper version : 2.0.30
04-06 13:31:10.507 12542 12542 I Camera11: loadHeavyResources : Start[1617726670507]
04-06 13:31:10.507 12542 12797 I CameraExecutorManager: onShootingModeChanged : 0, 0, false
04-06 13:31:10.508 12542 12542 I Camera11: loadHeavyResources : End[1617726670508] [1]
04-06 13:31:10.508 12542 12542 I CameraPerformance: Launch - LazyLoading : End[1617726670508] [22]
04-06 13:31:10.508 12542 12542 I RequestQueue: addRequest : APPLY_SETTINGS, com.sec.android.app.camera.engine.-$$Lambda$CommonEngine$BFOhyHc3pFR3i5NQnW-Mb3hrQv4@3c950ff
04-06 13:31:10.508 12542 12542 I RequestQueue: addRequest : SET_PRIVATE_SETTING, enable_intelligent_guide : true
04-06 13:31:10.511   698   698 D gralloc : [mali_gralloc_allocate] begin
04-06 13:31:10.511   698   698 D gralloc : buffer_descriptor: wh(2400 1080) usage_pc(0x20006 0x20006) hal_format(0x23) layer_count(1) sizes(0 0 0) strde(0) byte_stride(0) alloc_wh(0 0) internal_format(0x0) alloc_format(0x0) fd_count(1) plane_count(0)
04-06 13:31:10.512   722 12790 I ExynosCameraMetadataConverterVendor: [CAM(1)][]-(translateVendorControlMetaData[4046]):[R3 F4] dynamicShotExtraInfo (0 -> 2)
04-06 13:31:10.514   698   698 D gralloc : [mali_gralloc_allocate] allocation successful
04-06 13:31:10.515   722 12755 I EDEN    : [Exynos][EDEN][v1.6.7-2][RT::EdenRuntime] ExecuteReq:345: (+) modelId=72200009, mode=0
04-06 13:31:10.519  1142 12800 D TspStateManager: update cmd=set_grip_data,1,60,10,52,162
04-06 13:31:10.522   722 12788 I EDEN    : [Exynos][EDEN][v1.6.7-2][EDEN_RT_STUB] ExecuteReq:691: (+)
04-06 13:31:10.523   766 11788 I EDEN    : [Exynos][EDEN][v1.6.7-2][RT::EdenRuntime] ExecuteReq:345: (+) modelId=76600005, mode=2
04-06 13:31:10.524   679   679 I Zygote  : Process 12013 exited due to signal 9 (Killed)
04-06 13:31:10.526  1142  2170 D StorageManagerService: getExternalStorageMountMode: uid=1000 packageName=com.samsung.android.provider.filterprovider
04-06 13:31:10.526  1142  2170 D CompatibilityChangeReporter: Compat change id reported: 135634846; UID 1000; state: DISABLED
04-06 13:31:10.527  1142  4177 I ActivityManager: Process com.samsung.android.app.routines (pid 12013) has died: cch+35 CEM (140,1876)
04-06 13:31:10.528  1142  2170 W ActivityManager: wait for provider publish: waiters=1 callerApp=ProcessRecord{6c14494 12542:com.sec.android.app.camera/u0a111} cpr=ContentProviderRecord{95a775a u0 com.samsung.android.provider.filterprovider/.FilterProvider}
04-06 13:31:10.531  1142  4184 D SensorService: Calling batch handle==2 flags=0 rate=20000000 timeout== 0
04-06 13:31:10.534  2907  2907 E HostManager: onTrimMemory [15]
04-06 13:31:10.535  3201  3201 I SAFrameworkService: onTrimMemory(15): clearing caches...
04-06 13:31:10.535 20501 20501 I [-3]oneconnect[<IP_ADDRESS>_01][CORE]: [SCMain][QCApp].onTrimMemory - ************** lvl=15 elapsed=0ms
04-06 13:31:10.535  3201  3201 W SaBufferPool: ClearCache : Current cache size is lesser than the threshold of 0
04-06 13:31:10.536  3690  3690 W DMASA[U]: [AppLogData]onTrimMemory(15):1617726670536
04-06 13:31:10.537  3690  3690 W DMASA[C]: [DiagMonAgentApplication]onTrimMemory (15)
04-06 13:31:10.537  2115  2115 D SystemUIService: onTrimMemory = 15
04-06 13:31:10.537  2115  2115 D StatusBar: onTrimMemory = 15
04-06 13:31:10.537  2115  2115 D SystemUIService: onTrimMemory : 15
04-06 13:31:10.537  2115  2115 D SystemUIService: Starting getMemoryInfo in MemoryInfoReporter thread.
04-06 13:31:10.540 20490 20490 I [-3]oneconnect[<IP_ADDRESS>_01][RECEIVER]: [SCMain][QCApp].onTrimMemory - ************** lvl=15 elapsed=0ms
04-06 13:31:10.540 12542 12542 E SeslRecyclerView: No adapter attached; skipping layout
04-06 13:31:10.540  2802  2802 W DeviceManager_FLP: onTrimMemory : 15
04-06 13:31:10.540  2802  2802 I GpsSessionManager_FLP: arrangeInvalidSessions
04-06 13:31:10.541   466   466 I lmkd    : 5(delay),0(swap), 0(freelimit) memory pressure events were skipped after a kill!
04-06 13:31:10.541 12542 12542 W Camera11: onTrimMemory : 15
04-06 13:31:10.542  2115 12805 D SystemUIService:  - Memory Information -
04-06 13:31:10.547  7610  7610 I AppBase : AppBase.onTrimMemory():781 onTrimMemory(): 15
04-06 13:31:10.549 20936 20936 I [-3]oneconnect[<IP_ADDRESS>_01][MDE]: [SCMain][QCApp].onTrimMemory - ************** lvl=15 elapsed=0ms
04-06 13:31:10.550 12542 12597 I SemDvfsHyPerManager: acquire hyper - com.sec.android.app.camera/12542@0, type = 18
04-06 13:31:10.551   718   718 I HYPER-HAL: [ResourceManager.cpp]getResourceManager(): Resouce not supported on this device - resourceID : 0x12
04-06 13:31:10.551   718   718 E HYPER-HAL: [HyPerManager.cpp]getSupportedFrequency(): mRscManager is NULL
04-06 13:31:10.552   718   718 E HYPER-HAL: [HyPer.cpp]getSupportedFrequency(): AIDL getTable is NULL
04-06 13:31:10.552   466   466 I lmkd    : cached 2, sandbox(not0) 0
04-06 13:31:10.554 12542 12597 I CallStateManager: onCallStateChanged : 0
04-06 13:31:10.558   710   710 I Sensors : batch(2) - gyro_sensor try to batching with 20000000
04-06 13:31:10.560   466   466 I lmkd    : Reclaim 'com.samsung.android.biometrics.app.setting' (11292), uid 1000, oom_adj 925, state 19 to free 175588kB; reason: low watermark is breached and swap is low (407196kB < 262140kB)
04-06 13:31:10.564 12229 12328 I ReactNativeJNI: Memory warning (pressure level: TRIM_MEMORY_RUNNING_CRITICAL) received by JS VM, running a GC
04-06 13:31:10.567   679   679 D Zygote  : Forked child process 12808
04-06 13:31:10.569  1142  1986 I ChimeraPolicyHandler: Skipped by uid     : com.samsung.android.themecenter, 1000[2247]:G2(0x20002) score=37,0(91 10 7008), pids: 2247 / stats: 8 / adjs: 200
04-06 13:31:10.569  1142  1986 I ChimeraPolicyHandler: Skipped by adj     : com.sec.location.nsflp2, 5013[2802]:G2(0x20002) score=35,5(83 10 14594), pids: 2802 / stats: 5 / adjs: 100
04-06 13:31:10.569  1142  1986 I ChimeraPolicyHandler: Skipped by adj     : com.android.keychain, 15001000[8704]:G2(0x20002) score=34,3(79 10 15172), pids: 8704 / stats: 6 / adjs: 100
04-06 13:31:10.569  1142  1986 I ChimeraPolicyHandler: Skipped by adj     : com.samsung.android.honeyboard, 10165[5825]:G2(0x20000) score=34,1(55 10 66817), pids: 5825 / stats: 7 / adjs: 100
04-06 13:31:10.574   718 12596 I HYPER-HAL: [RequestManager.cpp]releaseLocked(): Released ID : 1609321
04-06 13:31:10.586  1142  1238 W ActivityManager: Slow operation: 61ms so far, now at startProcess: returned from zygote!
04-06 13:31:10.587  1142  1238 W ActivityManager: Slow operation: 62ms so far, now at startProcess: done updating battery stats
04-06 13:31:10.587  1142  1238 W ActivityManager: Slow operation: 62ms so far, now at startProcess: building log message
04-06 13:31:10.587  1142  1238 I ActivityManager: Start proc 12808:com.samsung.android.provider.filterprovider/1000 for content provider {com.samsung.android.provider.filterprovider/com.samsung.android.provider.filterprovider.FilterProvider}
04-06 13:31:10.587  1142  1238 W ActivityManager: Slow operation: 62ms so far, now at startProcess: starting to update pids map
04-06 13:31:10.588  1142  1238 W ActivityManager: Slow operation: 62ms so far, now at startProcess: done updating pids map
04-06 13:31:10.588  1142  1986 I ChimeraPolicyHandler: Killed on trigger0 : org.myapp.msg.dev, freed: 154998, 10208[10593]:G2(0x20000) score=34,0(15 10 154998), pids: 10593 / stats: 4 / adjs: 200
04-06 13:31:10.589  1142  1986 I ChimeraPolicyHandler: kill complete: killed 4 apps, freed 255323 KB
04-06 13:31:10.589  1142  1986 I ChimeraPolicyHandler: Processing time(ms) 200

Hello, big thanks for the growing evidence on this issue.. Did you see https://issuetracker.google.com/issues/179644471 ? Does maybe disabling battery optimization on the device prevent the ChimeraPolicyHandler from killing the foreground service? Big thanks for all your feedback!

I am not an expert, but from my experience, disabling battery optimization does't stop apps from being killed. Radomly, I get crash report.
And would you mind modifying the content of samsung on DKMA website? Because it does't do the trick at all. In fact, there is no way to maintain apps running in the background.

Hm, this: https://issuetracker.google.com/issues/179644471
"Hello, there is growing evidence that Samsung uses ChimeraPolicyHandler to kill foreground services which are supposed to run in Android 11. Please check
https://github.com/urbandroid-team/dont-kill-my-app/issues/307"
and
"After implementing the ApplicationExitInfo I am getting abnormal numbers of daily reports of my foreground service being killed by Chimera on Samsung devices.
getReason returns REASON_OTHER
getDescription returns Chimera #0 / Chimera #1 / Chimera #2 / Chimera PMM
I am also getting multiple REASON_LOW_MEMORY reports mainly on Pixel devices, although my app is very moderate with the memory.
Android 11 is currently the worst Android version in my books."
By me, bug in ChimeraPolicyHandler. In S21 this must be fixed, because in it, PPP was not restarted.

@JhonHuGit Many thanks... unfortunately we are not yet sure if this is a bug on some Samsung devices (API level 30) or if this is really intended behavior by Samsung... At least on our support requests from Samsung users in wast majority of cases on API 30 the DKMA link resolves the issues. But we are updating the https://dontkillmyapp.com/samsung page with more details on this and with a link to this thread..Many thanks..

Two days ago, Samsung rolled out a new update, patch level "April 1st" , One UI 3.1.  To me, this looks like it was a genuine bug and that it's fixed now. Thanks to Samsung for listening to users and developers!

@ge0rg big thanks for the update, that would be a great news.. can others also confirm? Big thanks..

In my Galaxy S21, since february second update, this problem was solved, but in latest may update is this problem returned. Foreground services are killed. My own application and also another applications. This not kill application, but restarts foreground service (parameter intent in service onStartCommand() method is null). Notification for foreground service is removed and application must again generate it. Similar problem is in application GSam Battery monitor.

@henrichg big thanks for the valuable update. In some of my own apps when the service is critical to keep it I use an AlarmManager-based restarting of the foreground service. Nevertheless this can happen on stock Android even without ChimeraPolicyHandler.. actually when running critically low on memory Android will kill the foreground service and restart later on if STICKY with a null intent. Did you check in the logcat if this is still caused by Chimera? As I guess a memory leak is not an uncommon think on Samsung devices unfortunately and it would cause similar observations.. Big thanks..

Hm, I do not know, if it is caused by Chimera. Maybe yes. I must log it.
I'm using applications in mobile since buy it. Facebook, Twitter, Reddit, Chrome, GitHub, XDA Developers, Instagram, Google Play, Galaxy Store, F-Droid, GSam Battery monitor, Autentificator, Google Pay, .... Not any new application is added to mobile.
Also in my PhoneProfilesPlus application was not any news.
Memory usage in mobile is (by me) good: 5GB from 7.5GB. Average usage 66%.
For PhoneProfilesPlus it is 90-130MB.
And yes, I know. If system restarts service, intent parameter is null. It is in API documentation. But by me, it is not due to low memery.
Service is STICKY, is started with startForegroundService() followed by startForeground().

Hm interesting. Problem was going away. After change of Samsung battery optimizations settings:

enabled: Device care / Battery / 3-dot menu / Auto optimize daily
enabled: Device care / Battery/ Background usage limits / Put unused apps to sleep
-- Device care / Battery/ Background usage limits / Sleeping apps: Mi Home
-- Device care / Battery/ Background usage limits / Deep sleeping apps: 0
-- Device care / Battery/ Background usage limits / Never sleeping apps: 0
enabled: Device care / Battery/ Mote batter settings /  Adaptive battery

But "Optimize battery usage" for PPP is set to "Not optimized".
Interesting. :-)

Hello @henrichg .. big thanks for the update.. which of the settings do you think has effect on the foreground services? Do I understand correctly that you enabled some of the background usage limits?

I was all settings disabled (look my previous post). And foreground service was restarted. After enabled all (except "Optimize battery usage", it keeps set to "Not optimize") yesterday, not any restart of service occurs.

Very strange :).. big thanks for the update..

I can confirm it does the same on the note 10 and the galaxy a01

The same for me, the foreground service for my looping music player is killed after some time when the phone goes off.

@XomaDev incredible.. many thanks for the update.. we still hope this is bug rather than a feature..

Greetings,
I have the same issue on my good old Galaxy S5 running Lineage 18.1 (Android 11). The problems of Sleep as Android being killed while running in foreground started after the upgrade from Lineage 17.1.
I've noticed two things:

The problem goes away in airplane mode (or turning off wifi and mobile data)
The Goole Play Store now is radically killing all kinds of apps while searching for updates (not only the ones actually being updated).

So, just a guess that those two could be related. Prevent the Play Store from doing its thing by killing all data connections.
Regards,
Zy.

Hello folks, I have been contacted by Android Team recently and they are asking for developers willing to contribute tests as part of their CTS (Compatibility Test Suite)...
I have reimplemented the DontKillMyApp Benchmark as part of Android's CTS Verifier tool which is now in review as a pull request under https://android-review.googlesource.com/c/platform/cts/+/1799749
I would like to ask you, are there any devs who would be willing to help and contribute their tests to the CTS Verifier so that we can help Google put further pressure on misbehaving OEMs?
Big thanks.
Regards,
Petr

Hi.
I can confirm that the issue with Android 10/11 killing foreground processes is still happening and not exclusive to Samsung devices.
I noticed the issue with an autoclicker app I've used for months. Then, maybe since july, it started closing misteriously after about 1 hour of un-attended use (screen on and device active). It happens on both my android devices: a Samsung S20+ (SM-986B) with Android 11 and a Huawei Media Pad M6 (SCM-W09) with Android 10.
I did assume that it was related to some new Android battery conserving intrusive policy but until yesterday I didn't get serious about trying to fix it.
I decided to unlock my S20+ in order to try some custom ROMs and see if the problem persisted. It does.
Then I found @petrnalevka about Android killing apps on samsung devices  (https://dontkillmyapp.com/samsung, very informative, thank you).
I did follow all advise there on both devices, but the issue still occurs.
I have focused on just the one device for now, so I can do proper tests.
The thing I'm inclined to think now is that the issue is related to excesive App power consumption since I've noticed that if I load a script with, let's say, 1 click every 10ms, the app is closed so much sooner (maybe after 5 minutes) that if I test with 1 click every 100ms (maybe it gets closed after 1 hour).
I would like to investigate the android logs now to check who is doing the killing. I have to research that since I've never done it before, but I will update results here when I do.
Thanks all for the information and I hope we can get to the bottom of it and force Google or whomever to fix it.

@jurrabi many thanks for your investigation. I'm little skeptical that there would be a common mechanism across Android 11 and 10 and Samsung and Huawei. IMHO I do not think this is something in AOSP and I'm not seeing this behavior on my Pixel phones. IMHO it is more likely that those are two independent mechanisms as both vendors are problematic / or it may also be a memory management issue - memory leak as Android standard policy is to kill even foreground services if critically low on memory. But if you can investigate the logcat it would be great if you would share some hints on what is happening.. many thanks..

Thanks foryour response. I'll share the logs. But first I'm gonna check if a can find a stable AOSP for my S20+ and try to reproduce the issue. I'm guessing if it does it would probably mean as you said an issue with memory management on the app itself...

Hello @petrnalevka, first of all thanks for your input in the https://dontkillmyapp.com/samsung, really good website that shows the configurations that are needed to not have android kill my app.
But my client has Samsung A20 devices and ever since he got Android 11 update, 1 may patch, he keeps telling me the app restarts or crashes.
I've implementented a service that registers the logcat of the android, but without any luck, there's no crashes being registered, simply put the log ends, and the app restarts without any crash, at least from the app, idk if there's any system crash, but even if there was, it should show a popup saying the app is crashing, but it's not showing anything.
The app closes and when he launches the app again, it has been restarted...
My problem right now, is that I cannot reproduce this, I have a A20 device, same app version, same 1 may security patch.

Does anyone have input on Android 12 on Samsung S21? The users of my app (read aloud with TTS, often with screen off) report similar issues, while it somehow worked well on Android 11, after applying the settings from dontkillmyapp.com site... Please share, thank you!

Hello @petrnalevka, first of all thanks for your input in the https://dontkillmyapp.com/samsung, really good website that shows the configurations that are needed to not have android kill my app.
But my client has Samsung A20 devices and ever since he got Android 11 update, 1 may patch, he keeps telling me the app restarts or crashes.
I've implementented a service that registers the logcat of the android, but without any luck, there's no crashes being registered, simply put the log ends, and the app restarts without any crash, at least from the app, idk if there's any system crash, but even if there was, it should show a popup saying the app is crashing, but it's not showing anything.
The app closes and when he launches the app again, it has been restarted...
My problem right now, is that I cannot reproduce this, I have a A20 device, same app version, same 1 may security patch.

Do you know how much is the total RAM is on the client's device and how much is the RAM available for the apps to run? This is a memory issue so you need to hit that limit.

Do you know how much is the total RAM is on the client's device and how much is the RAM available for the apps to run? This is a memory issue so you need to hit that limit in order to reproduce the issue.

Well, it has 3gb total ram, and well I can supply a bit of log that I have on these devices and this issue occurs
11-19 06:42:16.774 I/shuttle.releas(15023): Background young concurrent copying GC freed 156003(7607KB) AllocSpace objects, 14(472KB) LOS objects, 57% free, 6358KB/14MB, paused 379us total 120.578ms
...
11-19 06:44:14.067 I/System.out(15023): Thread-50 calls detatch()
11-19 06:44:14.067 V/beware.WSSendCoordinates(15023): RESPONSE: Done!
11-19 06:44:14.067 V/beware.WSSendCoordinates(15023): 1 coordinates sent to server.
11-19 06:44:14.070 I/beware.WSSendCoordinates(15023): send Coordinates
--------- beginning of main
11-19 06:52:17.616 E/Terminal(25096): 2021-11-19 06:52:17 # Battery Level = 98%
11-19 06:52:17.616 E/Logger  (25096): Last GC:<PHONE_NUMBER>659
11-19 06:52:17.616 E/Logger  (25096): Time between last GC: 762957
11-19 06:52:17.616 E/Logger  (25096): Time between GC: 120000
11-19 06:52:17.616 E/Memory  (25096): Max JVM memory = 524288 KB # Current JVM memory = 3697 KB # Free JVM memory = 1533 KB # JVM memory being used = 2164 KB # Available JVM memory = 522124 KB
11-19 06:52:17.647 I/shuttle.releas(25096): Explicit concurrent copying GC freed 2544(184KB) AllocSpace objects, 2(40KB) LOS objects, 24% free, 1939KB/2586KB, paused 145us total 30.530ms

I have App under development that runs as a foreground service OK on Samsung A10 One UI V3.1 Android version 11. It is not killed when the phone is asleep. Needed to put a permanent 'Partial WakeLock' command in the code to acheive this. Without the WakeLock, the App gets killed almost as soon as the phone sleeps!  OK with battery optimizations on as well.

I think most of us are well past placing the wake locks and the apps still get stopped or killed on many phones. The phone makers don't respect wake locks, they just want to brag in their ads about the "great battery life" their devices have. On Samsung Android 11 and UI 3.1, the settings described at dontkillmyapp.com work. Android 12 on Samsung devices is still not documented, for many devices its still not available either.

Tried the settings descriped at dontkillmyapp.com, and they don't work on my Samsung A10! As a developer, have tried pretty well everything with the power management settings in that phone and the App still gets killed! The only thing that has worked reliably on the Samsung A10 is the use of a Partial WakeLock in the App code to keep the CPU running when the phone is asleep. Sofar, that is the only thing I have found that works. In due course will test the App on other manufactures phones and see what happens.

Setting the correct wake lock is THE CORRECT thing to do, on any phone, for cases when the app must work in background or with screen off. The whole point of dontkillmyapp.com pages is that many device makers modify the system to kill or put to sleep, or otherwise stop the app working in background, DESPITE setting the correct wake locks.

I will find out in due coarse whether that is the case with my App, and will test it on different phones over the next few months. There are many reasons why Apps will not work properly with the latest Android operating systems. Samsung phones, have been cited as being problematic, but I have not found that to be the case with my App that is running 24/7 in the background successfully. Conversley, I found the suggestions on dontkillmyapp.com did not work. Power management issues are not the only reason Apps will not work successfully in the background. It is possible that the cause of failure for the Apps to run properly, is due to something else.
Incidently, the dontkillmyapp App from Google Playstore did not work either!

One further comment. I'm wondering whether manufactures may stop background Apps running if the power consumption figure is too high. My App consumes 6% of the battery over a 12 hour period. It runs OK as a 'power optimised' App and runs OK with all combinations of the power management choices in the phone.  Will be interesting to know what the phone manaufactures have to say about these issues. Must not lose sight of the fact that there could be many reasons Apps don't run properly in the background, apart from the power management stuff.

I have an A71 and Tab S6 Lite, both running One UI 3.1, security patch Oct 1 2021. I use Sleep as Android on the foreground to track my sleep, and in the recent 2 weeks, I noticed that it got killed on both my devices.
My alarms don't go off on Sleep as Android and Google Clock, but the built-in clock app works fine. Sleep tracking does not seem to run when I check the app, but there is no notification that the app crashed, so I think it got actively killed.
I tried both the battery optimization and device care methods but they don't seem to do anything.

Gut

Grasie

Brao

My Tab S6 Lite just got an update on Jan 19, currently on security level Jan 1. My alarms seem to work properly now.
I'll wait for the update for my A71 and bump this thread again.

@Whatnoww A lot of issues with Signal are related to Signal itself, though.
I stumbled across this issue because I develop an app that runs exclusively on Z Flip 3 devices. The app should always be available through a foreground service. I have received three separate reports describing the same behavior. They have all said the app "randomly stops running and requires a full reboot to run again."
I have been able to personally confirm that the app was being randomly killed off. I was able to stop that (temporarily, read on) by adding the app to "Never sleeping apps" list. What I found interesting is that the app randomly disappears from the list, either in the process of an update or simply after a few days. It would seem they are still overriding manual configuration.

Anybody here got any experience of a Moto G5 Android 8.1 killing foreground services? I have one that on a specific App, does that from time to time, even with battery optimisation disabled. However the Samsung A10 with Android 11 is fine even with battery optimisation enabled.  So far 100% reliable.

Anybody here got any experience of a Moto G5 Android 8.1 killing foreground services? I have one that on a specific App, does that from time to time, even with battery optimisation disabled. However the Samsung A10 with Android 11 is fine even with battery optimisation enabled. So far 100% reliable.

This issue is specifically for Samsung Android 11.

As well as Samsung Android 12 (One UI 4.0, 4.1)

There may be a solution if implemented please add to android 12 , One ui 4.1.
This has occurred to me and I have found this is usually implemented when restarting phone but not necessarily. I like too use my home network through my data connection to my cellphone I first make a connection to my phones data and start up VPN'S with credentials then login to then addhome wifi allowing me to secure both my devices as it should be able to detect added information at either point between the devices connected. But when they do this to me I usually have to input new credentials logged on to a browser in safe mode. Then logon to phone normally with data as a hot spot then use both data to Hotspot. Usually I have to pick a random location from phone then logon to other device and logon to VPN but using the fastest location to make connection there-bye tunneling connection between devices. When one of my devices is hacked this is my default response as I am unable to use my credentials. So, I don't know how simple this solution would be to implement but when someone logs you off of an app and doesn't allow you to logon again you could setup the website to recognize you have logged on under safe mode and then simply send a command to automatically log you on to your phone vpn under your default sellection as you have proven your credentials are proper and the monitor OS for any indication as to who has hacked your device to further the intervention protecting the app User from further being  compromised.

Thanks

I've got the Android 13 update on my Samsung S20+ 5G and foreground services are not getting killed anymore.

@AndroidPat big thanks for the message, this sounds like a good news, hopefully more people can confirm this?

i have been my S22 (Android 13, OneUI 5) for months, and my background apps have been running for months, was not forced to re-enable accesibility either.
i used to suffer from auto-kill on Android 12 Samsung and companies devices.

@Pleasantless big thanks for the udpate.

Have been testing a foreground service App on Samsung A10 (Android 11) and Samsung A04E (Android 12)  The Samsung A10 occassionally kills the App but it immediately restarts! This occurs when the phone is doing something else intensively ie when playing YouTube video's etc!   No problems with the Samsung A04E. The A10 seems to have other bugs as well. The newer A04E is considerably better. Also notifications occassionally delayed on A10, but not on A04.

i suffered from auto-kill on Android 11/12, tried Samsung Xiaomi OnePlus

@Pleasantless did U suffer from auto-kill on all those phone EVEN AFTER trying everything recommended on www.dontkillmyapp.com ? Only Samsung seemed to be the one for which nothing helped but regarding others it's not clear whether following all tips help on Android 11/12 or not?

@TEhala42
yes. im a very techy person. i tried all manner of settings and guides for those devices. Nothing helped.
now, im too worried to update my S22+ because im afraid the functionality may break.

@Pleasantless I would like to know on the www.dontkillmyapp.com website on which devices following their recommendations helps to SOLVE the auto-kill problem vs not or only just makes the killing happen less often. And there should be 2 different ratings, how they behave on DEFAULT settings and how they behave AFTER trying everything possible.
There also seems to be difference between BACKGROUND services and FOREGROUND services. Samsung was highlighted with red text because of them also killing FOREGROUND services. I'm not just I entierly understand that but some apps got around the auto-killing by creating foreground services and on Samsung THOSE are killed as well.
Are FOREGROUND services also killed on your other non-Samsung devices?
Thanks for sharing info

Hello!
I've got the Android 13 update on my Tab S6 Lite and foreground services are got killed.
After turning off the screen, after 2 hours the app is killed:
ActivityManager    I  Killing 32118:com.my.app/u0a283 (adj 200): BarTender
I whitelisted it everywhere the battery was mentioned.
There might be something wrong with my foreground services but on android 11 and 12 it worked. Does anyone have an example of correct implementation of foreground services for android 13?

اعلان: برنامه پس زمینه مسدود شد، چیست؟

03-22 8:55:09.470  5028 10568 I himraPolicyHandler: Killed on trigger2 : orgyaxim.bruno, freed: 34707, 1202[4548]:G2(0x20000) score=26,8(39 5 34707), pids: 4548 / stats: 4 / adjs: 200
[...]
03-2 08:55:09.585  5028 11722 I ActivityManager: Process org.yaxim.bruno (pid 4548) has died: prcp FS (175,635)
03- 08:55:09.586  5028 11722 W ActivityManag: Scheduling restart of crashed service org.yaxim.bruno/org.yaxim.androidclient.service.XMPPService in 100s for start-requested

Después de actualizar mi Galaxy A51 de Android 10 a Android 11, comenzó a eliminar periódicamente (o aleatoriamente) mis dos aplicaciones cliente XMPP, yaxim y Bruno, a pesar de que ambas tienen una notificación de servicio en primer plano permanente (y visible).
Irónicamente, el sistema operativo reconoce esas muertes como un bloqueo e inmediatamente reinicia la aplicación, lo que provoca una gran cantidad de tráfico de red innecesario:
03-22 08:55:09.470  5028 10568 I ChimeraPolicyHandler: Killed on trigger2 : org.yaxim.bruno, freed: 34707, 10202[4548]:G2(0x20000) score=26,8(39 5 34707), pids: 4548 / stats: 4 / adjs: 200
[...]
03-22 08:55:09.585  5028 11722 I ActivityManager: Process org.yaxim.bruno (pid 4548) has died: prcp FGS (175,635)
03-22 08:55:09.586  5028 11722 W ActivityManager: Scheduling restart of crashed service org.yaxim.bruno/org.yaxim.androidclient.service.XMPPService in 1000ms for start-requested

Aún más irónico es que también sigue resucitando (iniciando automáticamente) aplicaciones que he detenido manualmente antes.
ChimeraPolicyHandler parece ser un trabajo que se ejecuta varias veces por hora durante el system_serverproceso. PD muestra:
system         5028   4601 12953324 266152 0                  0 S system_server

Registro completo de una ejecución de ChimeraPolicyHandler:
03-22 08:55:09.288  5028 10568 I ChimeraPolicyHandler: Start executePolicy: TRIGGER_SOURCE_HOME_IDLE
03-22 08:55:09.293  5028 10568 I ChimeraPolicyHandler: memAvailable: 750256, memFreeTarget: 890880, releaseTarget:140624, protectedLruCount: 6
03-22 08:55:09.403  5028 10568 I ChimeraPolicyHandler: Start doKill, protected policy: NORMAL
03-22 08:55:09.405  5028 10568 I ChimeraPolicyHandler: Skipped by adj     : com.google.android.googlequicksearchbox, 10230[20349,14885]:G1(0x1) score=55,7(23 40 127100), pids: 20349 14885 / stats: 10 5 / adjs: 800 100
03-22 08:55:09.405  5028 10568 I ChimeraPolicyHandler: Skipped by interval: com.samsung.android.oneconnect, elapsed: 00:54:50, interval: 04:00:00, 10255[12960,13390]:G1(0x1) score=33,4(35 10 67797), pids: 12960 13390 / stats: 8 8 / adjs: 200 200
03-22 08:55:09.405  5028 10568 I ChimeraPolicyHandler: Skipped by adj     : com.android.vending, 10226[25018]:G1(0x1) score=13,0(3 5 51575), pids: 25018 / stats: 12 / adjs: 100
03-22 08:55:09.405  5028 10568 I ChimeraPolicyHandler: Skipped by adj     : com.android.systemui, 10054[10714]:G2(0x20000) score=76,0(65 10 240771), pids: 10714 / stats: 5 / adjs: -800
03-22 08:55:09.405  5028 10568 I ChimeraPolicyHandler: Skipped by adj     : com.google.android.ext.services, 10080[24237,24270]:G2(0x20000) score=48,5(43 40 27866), pids: 24237 24270 / stats: 5 5 / adjs: 100 100
03-22 08:55:09.406  5028 10568 I ChimeraPolicyHandler: Skipped by adj     : com.google.android.as, 10284[24194,24200]:G2(0x20000) score=42,9(34 40 19282), pids: 24194 24200 / stats: 5 5 / adjs: 100 100
03-22 08:55:09.406  5028 10568 I ChimeraPolicyHandler: Skipped by adj     : com.samsung.android.dynamiclock, 10070[21726]:G2(0x20000) score=34,0(15 40 18505), pids: 21726 / stats: 5 / adjs: 0
03-22 08:55:09.406  5028 10568 I ChimeraPolicyHandler: Skipped by adj     : com.samsung.android.app.telephonyui, 1001[27531]:G2(0x20002) score=31,1(48 5 36007), pids: 27531 / stats: 5 / adjs: 0
03-22 08:55:09.406  5028 10568 I ChimeraPolicyHandler: Skipped by adj     : com.sec.location.nsflp2, 5013[11278]:G2(0x20002) score=31,1(57 5 10969), pids: 11278 / stats: 5 / adjs: 100
03-22 08:55:09.406  5028 10568 I ChimeraPolicyHandler: Skipped by adj     : com.samsung.android.knox.containercore, 5250[11455]:G2(0x20002) score=28,6(53 5 6891), pids: 11455 / stats: 5 / adjs: 100
03-22 08:55:09.406  5028 10568 I ChimeraPolicyHandler: Skipped by adj     : com.samsung.android.server.wifi.mobilewips, 1000[5432]:G2(0x20002) score=28,5(50 5 14599), pids: 5432 / stats: 6 / adjs: 100
03-22 08:55:09.410  5028 10568 I ChimeraPolicyHandler: Skipped by uid     : com.samsung.android.beaconmanager, 5006[19846]:G2(0x20002) score=28,2(52 5 7092), pids: 19846 / stats: 8 / adjs: 200
03-22 08:55:09.410  5028 10568 I ChimeraPolicyHandler: Skipped by adj     : com.sec.epdg, 1000[17442]:G2(0x20002) score=27,9(49 5 13754), pids: 17442 / stats: 6 / adjs: 100
03-22 08:55:09.411  5028 10568 I ChimeraPolicyHandler: Skipped by adj     : org.kde.kdeconnect_tp, 10393[14802]:G2(0x8) score=27,8(26 20 22970), pids: 14802 / stats: 4 / adjs: 100
03-22 08:55:09.414  5028 10568 I ChimeraPolicyHandler: Skipped by uid     : com.samsung.android.themecenter, 1000[10830]:G2(0x20002) score=27,6(51 5 6306), pids: 10830 / stats: 8 / adjs: 200
03-22 08:55:09.415  5028 10568 I ChimeraPolicyHandler: Skipped by interval: org.yaxim.bruno, elapsed: 00:52:29, interval: 04:00:00, 10202[4548]:G2(0x20000) score=26,8(39 5 34707), pids: 4548 / stats: 4 / adjs: 200
03-22 08:55:09.416  5028 10568 I ChimeraPolicyHandler: Skipped by interval: com.sec.android.easyonehand, elapsed: 00:51:40, interval: 04:00:00, 10201[5926]:G2(0x20000) score=23,6(38 5 18683), pids: 5926 / stats: 8 / adjs: 200
03-22 08:55:09.425  5028 10568 I ChimeraPolicyHandler: Skipped by Normal Service condition: com.samsung.android.providers.contacts, 15010062[7334,6035]:G2(0xa0000) score=23,5(29 5 42946), pids: 7334 6035 / stats: 19 19 / adjs: 915 850  reason: ACTIVITY_TIME
03-22 08:55:09.425  5028 10568 I ChimeraPolicyHandler: Skipped by adj     : com.samsung.android.mcfserver, 1000[12405]:G2(0x20002) score=21,2(36 5 9534), pids: 12405 / stats: 6 / adjs: 100
03-22 08:55:09.426  5028 10568 I ChimeraPolicyHandler: Skipped by interval: com.samsung.android.bixby.agent, elapsed: 00:25:49, interval: 04:00:00, 5018[18287]:G2(0x20002) score=20,4(32 5 15738), pids: 18287 / stats: 10 / adjs: 800
03-22 08:55:09.426  5028 10568 I ChimeraPolicyHandler: Skipped by adj     : com.samsung.android.smartsuggestions, 10475[20029,19131]:G2(0x20000) score=18,3(22 10 13072), pids: 20029 19131 / stats: 5 5 / adjs: 100 100
03-22 08:55:09.426  5028 10568 I ChimeraPolicyHandler: Skipped by interval: android, elapsed: 00:51:40, interval: 04:00:00, 1000[19042]:G2(0x20002) score=18,3(31 5 5917), pids: 19042 / stats: 10 / adjs: 800
03-22 08:55:09.426  5028 10568 I ChimeraPolicyHandler: Skipped by interval: com.samsung.android.svcagent, elapsed: 00:51:40, interval: 04:00:00, 1000[19085]:G2(0x20002) score=17,8(30 5 5645), pids: 19085 / stats: 10 / adjs: 500
03-22 08:55:09.427  5028 10568 I ChimeraPolicyHandler: Skipped by adj     : org.yaxim.androidclient, 10409[13822]:G2(0x20000) score=15,5(4 5 64062), pids: 13822 / stats: 4 / adjs: 50
03-22 08:55:09.430  5028 10568 I ChimeraPolicyHandler: Skipped by Normal Service condition: com.samsung.android.stickercenter, 1000[16950]:G2(0x20002) score=13,8(20 5 9228), pids: 16950 / stats: 15 / adjs: 700  reason: ACTIVITY_TIME
03-22 08:55:09.434  5028 10568 I ChimeraPolicyHandler: Skipped by Normal Service condition: com.android.providers.calendar, 10102[18783]:G2(0x20000) score=13,1(19 5 8293), pids: 18783 / stats: 15 / adjs: 700  reason: ACTIVITY_TIME
03-22 08:55:09.435  5028 10568 I ChimeraPolicyHandler: Skipped by adj     : com.samsung.android.biometrics.app.setting, 1000[21738]:G2(0x20002) score=11,1(13 5 12861), pids: 21738 / stats: 5 / adjs: 100
03-22 08:55:09.435  5028 10568 I ChimeraPolicyHandler: kill complete: killed 0 apps, freed 0 KB
03-22 08:55:09.435  5028 10568 I ChimeraPolicyHandler: Start doKill, protected policy: HEAVY
03-22 08:55:09.435  5028 10568 I ChimeraPolicyHandler: Skipped by adj     : com.google.android.googlequicksearchbox, 10230[20349,14885]:G1(0x1) score=55,7(23 40 127100), pids: 20349 14885 / stats: 10 5 / adjs: 800 100
03-22 08:55:09.437  5028 10568 I ChimeraPolicyHandler: Killed on trigger2 : com.samsung.android.oneconnect, freed: 67797, 10255[12960,13390]:G1(0x1) score=33,4(35 10 67797), pids: 12960 13390 / stats: 8 8 / adjs: 200 200
03-22 08:55:09.443  5028 10568 I ChimeraPolicyHandler: Skipped by adj     : com.android.vending, 10226[25018]:G1(0x1) score=13,0(3 5 51575), pids: 25018 / stats: 12 / adjs: 100
03-22 08:55:09.443  5028 10568 I ChimeraPolicyHandler: Skipped by adj     : com.android.systemui, 10054[10714]:G2(0x20000) score=76,0(65 10 240771), pids: 10714 / stats: 5 / adjs: -800
03-22 08:55:09.450  5028 10568 I ChimeraPolicyHandler: Killed on trigger2 : com.google.android.ext.services, freed: 27866, 10080[24237,24270]:G2(0x20000) score=48,5(43 40 27866), pids: 24237 24270 / stats: 5 5 / adjs: 100 100
03-22 08:55:09.456  5028 10568 I ChimeraPolicyHandler: Killed on trigger2 : com.google.android.as, freed: 19282, 10284[24194,24200]:G2(0x20000) score=42,9(34 40 19282), pids: 24194 24200 / stats: 5 5 / adjs: 100 100
03-22 08:55:09.457  5028 10568 I ChimeraPolicyHandler: Skipped by adj     : com.samsung.android.dynamiclock, 10070[21726]:G2(0x20000) score=34,0(15 40 18505), pids: 21726 / stats: 5 / adjs: 0
03-22 08:55:09.457  5028 10568 I ChimeraPolicyHandler: Skipped by adj     : com.samsung.android.app.telephonyui, 1001[27531]:G2(0x20002) score=31,1(48 5 36007), pids: 27531 / stats: 5 / adjs: 0
03-22 08:55:09.457  5028 10568 I ChimeraPolicyHandler: Skipped by adj     : com.sec.location.nsflp2, 5013[11278]:G2(0x20002) score=31,1(57 5 10969), pids: 11278 / stats: 5 / adjs: 100
03-22 08:55:09.458  5028 10568 I ChimeraPolicyHandler: Skipped by adj     : com.samsung.android.knox.containercore, 5250[11455]:G2(0x20002) score=28,6(53 5 6891), pids: 11455 / stats: 5 / adjs: 100
03-22 08:55:09.458  5028 10568 I ChimeraPolicyHandler: Skipped by adj     : com.samsung.android.server.wifi.mobilewips, 1000[5432]:G2(0x20002) score=28,5(50 5 14599), pids: 5432 / stats: 6 / adjs: 100
03-22 08:55:09.460  5028 10568 I ChimeraPolicyHandler: Skipped by uid     : com.samsung.android.beaconmanager, 5006[19846]:G2(0x20002) score=28,2(52 5 7092), pids: 19846 / stats: 8 / adjs: 200
03-22 08:55:09.461  5028 10568 I ChimeraPolicyHandler: Skipped by adj     : com.sec.epdg, 1000[17442]:G2(0x20002) score=27,9(49 5 13754), pids: 17442 / stats: 6 / adjs: 100
03-22 08:55:09.461  5028 10568 I ChimeraPolicyHandler: Skipped by adj     : org.kde.kdeconnect_tp, 10393[14802]:G2(0x8) score=27,8(26 20 22970), pids: 14802 / stats: 4 / adjs: 100
03-22 08:55:09.465  5028 10568 I ChimeraPolicyHandler: Skipped by uid     : com.samsung.android.themecenter, 1000[10830]:G2(0x20002) score=27,6(51 5 6306), pids: 10830 / stats: 8 / adjs: 200
03-22 08:55:09.470  5028 10568 I ChimeraPolicyHandler: Killed on trigger2 : org.yaxim.bruno, freed: 34707, 10202[4548]:G2(0x20000) score=26,8(39 5 34707), pids: 4548 / stats: 4 / adjs: 200
03-22 08:55:09.509  5028 10568 I ChimeraPolicyHandler: Killed on trigger2 : com.sec.android.easyonehand, freed: 18683, 10201[5926]:G2(0x20000) score=23,6(38 5 18683), pids: 5926 / stats: 8 / adjs: 200
03-22 08:55:09.599  5028 10568 I ChimeraPolicyHandler: Killed on trigger2 : com.samsung.android.providers.contacts, freed: 42946, 15010062[7334,6035]:G2(0xa0000) score=23,5(29 5 42946), pids: 7334 6035 / stats: 19 19 / adjs: 915 850
03-22 08:55:09.635  5028 10568 I ChimeraPolicyHandler: Skipped by adj     : com.samsung.android.mcfserver, 1000[12405]:G2(0x20002) score=21,2(36 5 9534), pids: 12405 / stats: 6 / adjs: 100
03-22 08:55:09.675  5028 10568 I ChimeraPolicyHandler: Killed on trigger2 : com.samsung.android.bixby.agent, freed: 15738, 5018[18287]:G2(0x20002) score=20,4(32 5 15738), pids: 18287 / stats: 10 / adjs: 800
03-22 08:55:09.723  5028 10568 I ChimeraPolicyHandler: Skipped by adj     : com.samsung.android.smartsuggestions, 10475[20029,19131]:G2(0x20000) score=18,3(22 10 13072), pids: 20029 19131 / stats: 5 5 / adjs: 100 100
03-22 08:55:09.724  5028 10568 I ChimeraPolicyHandler: Skipped by wakelock       : android, 1000[19042]:G2(0x20002) score=18,3(31 5 5917), pids: 19042 / stats: 10 / adjs: 800
03-22 08:55:09.732  5028 10568 I ChimeraPolicyHandler: Skipped by uid     : com.samsung.android.svcagent, 1000[19085]:G2(0x20002) score=17,8(30 5 5645), pids: 19085 / stats: 10 / adjs: 500
03-22 08:55:09.732  5028 10568 I ChimeraPolicyHandler: Skipped by adj     : org.yaxim.androidclient, 10409[13822]:G2(0x20000) score=15,5(4 5 64062), pids: 13822 / stats: 4 / adjs: 50
03-22 08:55:09.743  5028 10568 I ChimeraPolicyHandler: Skipped by uid     : com.samsung.android.stickercenter, 1000[16950]:G2(0x20002) score=13,8(20 5 9228), pids: 16950 / stats: 15 / adjs: 700
03-22 08:55:09.757  5028 10568 I ChimeraPolicyHandler: Killed on trigger2 : com.android.providers.calendar, freed: 8293, 10102[18783]:G2(0x20000) score=13,1(19 5 8293), pids: 18783 / stats: 15 / adjs: 700
03-22 08:55:09.768  5028 10568 I ChimeraPolicyHandler: Skipped by adj     : com.samsung.android.biometrics.app.setting, 1000[21738]:G2(0x20002) score=11,1(13 5 12861), pids: 21738 / stats: 5 / adjs: 100
03-22 08:55:09.768  5028 10568 I ChimeraPolicyHandler: kill complete: killed 8 apps, freed 235312 KB
03-22 08:55:09.768  5028 10568 I ChimeraPolicyHandler: Processing time(ms) 480

https://github.com/urbandroid-team/dont-kill-my-app/assets/143532383/7d7b82fc-cdbc-46ed-85b9-6189f70397c4

<EMAIL_ADDRESS>

Vnc connect

Why is this issue getting spam?

ارجو أصبح الجهاز

Does anyone know where the class is for ChimeraPolicyHandler? Like which jar/apk holds the class?

Does anyone know where the class is for ChimeraPolicyHandler? Like which jar/apk holds the class?

Replying for myself in the future when I will probably need this again. But I found it.
/system/framework/service.jar -> com.android.server.chimera.PolicyHandler/.AggressivePolicyHandler. These classes have the killing stuff in it. Might be more. I've modded mine and disabled it. It kept killing things that were "idle" too long despite me literally using them. I guess it was telling me to stop procrastinating lol
I may upload the smali code for people to browse if they like


docs(fix)

Fixed "Configure Armory Enterpris eusing Kustomize patches" row in the table

Resolves GitHub issue:

Resolves Jira: [JIRAPROJECT-123]

The title of this Pull Request needs to be changed to match the format:
<type>(<scope>): <subject>

See more details here: https://www.spinnaker.io/community/contributing/submitting/#commit-message-conventions
Some common examples are:
feat(armory.io): add docs.armory.io
fix(parser): grammar and spelling
style(loadingPage): made it super pretty!
refactor(helpMessages): changed order to make more sense


mod infrastructures

Codecov Report

Merging #26 (9dcfafe) into main (e87a788) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##               main      #26   +/-   ##
=========================================
  Coverage     95.11%   95.11%
  Complexity      468      468
=========================================
  Files           131      131
  Lines          1207     1207
  Branches         58       58
=========================================
  Hits           1148     1148
  Misses           50       50
  Partials          9        9

Continue to review full report at Codecov.

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


PowerToys Run crashed on open

ℹ Computer information

PowerToys version: v0.33.1
PowerToy Utility: PowerToys Run
Running PowerToys as Admin: Yes
Windows build number: 19042.804

📝 Provide detailed reproduction steps (if any)

Press alt+space to open PowerToys Run

✔ Expected result
The PowerToys Run search box opens.
❌ Actual result
It crashed, showing 2 separate error windows, but pointing to the same log file
📷 Screenshots

Log file
2021-03-17.txt

Hi @Ghoelian
Are you still experiencing the issue with the latest version of PowerToys?
/needinfo

Sorry, but I have largely moved away from using Windows, so I also don't use PowerToys anymore.


How add Authorization token in axios header?

When I login, I'm get from remote API server user token. When I get token, I'm set him on store and local storage. If I reload my app I want get my token from local storage and set on store. But local storage not defined if I call them on my store:
import Vue from 'vue'
import Vuex from 'vuex'

Vue.use(Vuex)

const store = () => new Vuex.Store({
  user: {
    token: localStorage.getItem('userToken')
  }
})

or ~plugins/axios.js:
import axios from 'axios'

export default axios.create({
  baseURL: process.env.baseApiUrl,
  headers: {
    'Authorization': 'Bearer '+localStorage.getItem('userToken')
  }
})

How can I resolve this problem?
P.S. sorry for my English

localStorage is a client side API, you can determine if the code should run using the context passed to plugins eg.
export default ({ isClient }) => {
  // do codez
}

Or a better solution would probably be to use the nuxt-modules/axios library which optimises axios for use within nuxt.

Hi @vUdav,
I recommend you to use the nuxt-community/axios-module which allows you to set axios header easily.


custom marker drop animation or any alternative ?

https://plnkr.co/edit/hVk3YSB6m997oIZDYI7T?p=preview
See the custom marker doesn't animate the same way as <marker>. Is it not supported or missing?
Should I add a class to animate it ? Any example you can show maybe?

It's not supported and. Please create a css class to animate. There is no example for it though. If you create an example and share it with others, it would be great.


bug: CocoaPods could not find compatible versions for pod "GoogleMLKit/Translate"

Plugin(s)

[ ] Barcode Scanning
[ ] Face Detection
[ ] Face Mesh Detection
[ ] Selfie Segmentation
[X] Translation

Version
7.0.0-next.2
Platform(s)

[ ] Android
[X] iOS
[ ] Web

Current behavior
npx cap sync fails to sync iOS
✖ Updating iOS native dependencies with pod install - failed!
✖ update ios
[error] Analyzing dependencies
[!] CocoaPods could not find compatible versions for pod "GoogleMLKit/Translate":
In Podfile:
CapacitorMlkitTranslation (from ../../node_modules/@capacitor-mlkit/translation) was resolved to 7.0.0-next.2,
which depends on
GoogleMLKit/Translate (= 7.0.0)
    Specs satisfying the `GoogleMLKit/Translate (= 7.0.0)` dependency were found, but they required a higher minimum
    deployment target.

Expected behavior
It should be able to sync
Reproduction
https://github.com/capawesome-team/.capacitor-app
Steps to reproduce
npm install @capacitor-mlkit/translation@next
npx cap sync
Other information
No response
Capacitor doctor
💊   Capacitor Doctor  💊
Latest Dependencies:
@capacitor/cli: 6.2.0
@capacitor/core: 6.2.0
@capacitor/android: 6.2.0
@capacitor/ios: 6.2.0
Installed Dependencies:
@capacitor/cli: 6.1.2
@capacitor/core: 6.1.2
@capacitor/android: 6.1.2
@capacitor/ios: 6.1.2
[success] iOS looking great! 👌
[success] Android looking great! 👌
Before submitting

[X] I have read and followed the bug report guidelines.
[X] I have attached links to possibly related issues and discussions.
[X] I understand that incomplete issues (e.g. without reproduction) are closed.

You need to set a higher minimum deployment target, see Minimum Deployment Target.

@robingenz yes sorry I've passed on this too quickly


File missing?

python server.py
Using TensorFlow backend.
Traceback (most recent call last):
File "server.py", line 178, in
chainer.serializers.load_npz('google_net.net', google_net)
File "/usr/local/lib/python2.7/dist-packages/chainer/serializers/npz.py", line 132, in load_npz
with numpy.load(filename) as f:
File "/usr/local/lib/python2.7/dist-packages/numpy/lib/npyio.py", line 370, in load
fid = open(file, "rb")
IOError: [Errno 2] No such file or directory: 'google_net.net'

Model
Models are avaliable in 'release' page.
base_generator.net all rights reserved 2017 style2paints
paintschainer.net from paintschainer
google_net.net from nico-opendata

The models are updating and it will be able to be downloaded soon.

Update finished. Models are avaliable now.
Closed.


prompt when encounter error or no recipes found when generate recipes

oooh very good idea didnt think of this, i just ran and it looks pretty good. nice work!

Ohh this is much better!


[a11y] Add focus state changes on Edit Profile screen

Description
LEARNER-6764
All interactable/clickable items on Edit Profile should be focusable using a Bluetooth Keyboard.
Testing

Connect a BlueTooth keyboard.
Log into the edX app
Click on Profile button
Click on Edit button
Press the Tab key repeatedly.

FYI @wittjeff


[Clarification] End of Life for MI25

Does the end of life apply to all Vega 10 cards?
for example, my:
  Name:                    gfx900
  Marketing Name:          Vega 10 XTX [Radeon Vega Frontier Edition]

Thank you.

Hi @ianzur
Thanks for reaching out.
Yes, its the same for Vega10 also. Thank you.


feat: Provide currentRow access in the table widget select column typ…

…e's selectOptions property
Description

Now app developers have access to the currentRow variable in the selectOptions property of the select columns in the table widget. This enables them to create different select options for each row in the table.

Fixes #18148
Type of change

New feature (non-breaking change which adds functionality)

How Has This Been Tested?

Manual
Jest
Cypress

Test Plan

Add Testsmith test cases links that relate to this PR

Issues raised during DP testing

Link issues raised during DP testing for better visiblity and tracking (copy link from comments dropped on this PR)

Checklist:
Dev activity

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[ ] PR is being merged under a feature flag

QA activity:

[ ] Test plan has been approved by relevant developers
[ ] Test plan has been peer reviewed by QA
[ ] Cypress test cases have been added and approved by either SDET or manual QA
[ ] Organized project review call with relevant stakeholders after Round 1/2 of QA
[ ] Added Test Plan Approved label after reveiwing all Cypress test

/ok-to-test sha=e8f93b2

The DP link is broken/failed in this PR and also branch has some conflicts. Please check @sbalaji1192

/ok-to-test sha=32f9a2b

@sbalaji1192 The table widget is crashing on using currentRow within a select column. Can you please check? https://ivP6ez0lJB.vmaker.com/record/ScL3BURRhLnxYBzc

/ok-to-test sha=8703b94

/ok-to-test sha=f69b44c

/ok-to-test sha=87338bf

/ok-to-test sha=a62cbd8

/ok-to-test sha=4ffb0e2


perfectDrawEnabled property missing in typescript def

The perfectDrawEnabled property https://konvajs.github.io/api/Konva.Circle.html#perfectDrawEnabled__anchor is missing on the Circle component (and I'm assuming on other shapes aswell). I'm not sure if this is missing on the side of konva or react-konva, since I'm not sure what they provide in typescript definitions

Fixed in konva repo.


Tag webhook support

Issue: https://github.com/rancher/rio/issues/542
First commit also adds shorthand -n to rio up.
Testing scenarios, I already tested all but need to go through again:

tags on or off, ie: tag-only vs commit-only webhooks
using the tag-query and tag-exclude params
tags on a non master branch still deploy - don't really need to test as long as tags work in general, this would just be testing github functionality
Using CLI to try to make a service with tag and branch or tag without webhook should fail
tags on a templated service should still work
using riofile (see below)
tags and filters on a riofile stack rio up -n demo --build-tag=true --build-tag-include=^v --build-tag-exclude=alpha  https://github.com/....

Testing instructions:

setup cluster
rio secret add --github-webhook
rio run -p 8080 -n tag-demo --build-webhook-secret=githubtoken --build-tag=true --build-tag-include="^v" --build-tag-exclude="alpha" https://github.com/cbron/mybusybox
push new tag or new commit, see that new pod is created for that service

For using local cluster, between steps 2 and 3 above do:

expose your local machine
rio domain register external_endpoint rio-system:webhook
Do step 3
update webhook to point to your external_endpoint

Example riofile:
services:
  demo:
    build:
      repo: https://github.com/cbron/mybusybox
      branch: master
      webhookSecretName: githubtoken
      tag: true
      tagInclude: ^v
      tagExclude: rc
    ports:
    - 8080

@rancher-max ping me if you need help testing, and try to review docs as you go, I think I got everything but not positive.


figure out better name for game

Geometry Runner?

Swift Shapes

Polygonal Pace

Becky suggested "Shape Up" or "Square^2"

Sam: Geometry Dash, It's not Easy being Green

Peter: Shape Escape

Geometry Jealousy (Sam)

I like Square Squared the best


Variant type VT_ARRAY_UI1 returns null on toJava but should return byte array

Trying to get the objectGUID from an object in LDAP through  the ado20 typelib, but com4j does not implement a conversion from native to java for the type VT_ARRAY_UI1 (array of bytes).
I suspect that the com4j.Variant class toJava method  ends up in the safearray.cpp class calling SafeArrayXducer::toJava but this class does not handle the VT_ARRAY_UI1 type and falls through to return null.

I'm having the same problem; did you ever find a work-around?


Now moved the ECG Graph and BPM reading in python

Now Since we need to process both ECG graoh and BPM correctly we need better hardware thus achived this using python running locally on PC

Done


Update spec for emacs pre-release 29.0.92 from 06/15/2023

Provides a bump on building emacs pre-release tag 29.0.92 (See emacs mirror tags) that builds fine on FC37 and FC38. Main reason for the bump is that the previous mirror commit a27b0f7f307ccf54fd5910a0655bd72b23e69fcf is not existing anymore.

Thanks, lets see if it builds


Hydro Turbines doesn't generate after installing v33

Description (Required)
Recently, a friend of mine has a survival slimefun server. He updated it to v(ersion) 33 of DynaTech and all hydro turbines stopped working. This caused the community to basically rage. I've tested this on my own server and it seemed to have stopped turbines from working.

Steps to reproduce the Issue (Required)

Get a Purpur 1.20.4 (2176) server
Install Java 21
Install Slimefun 4 (Dev 1148)
Install DynaTech v33
Get Hydro Turbines
Place them down
They don't generate power

Expected behavior (Required)
Generating power
Server Log / Error Report
https://mclo.gs/dSt3Lax
Environment (Required)

Minecraft Version: 1.20.4
CS-CoreLib Version: don't have it
Slimefun Version: Dev - 1148
Plugin Version: v33

This is intended behavior. please look for the new water mills in the experimental section


FLPROD-796: Register snippet and snippet_rules resources

Depends on cloudflare/cloudflare-go#3596 and https://github.com/cloudflare/cloudflare-go/pull/3669

cloudflare_snippet looks fine
TF_ACC=1 go test ./internal/framework/service/snippets/ -run "^TestAcc" -count 1 -v
=== RUN   TestAccCloudflareSnippet
=== PAUSE TestAccCloudflareSnippet
=== CONT  TestAccCloudflareSnippet
--- PASS: TestAccCloudflareSnippet (5.15s)
PASS
ok  	github.com/cloudflare/terraform-provider-cloudflare/internal/framework/service/snippets	6.389s

however, cloudflare_snippet_rules is having issues with the decoding of the json
=== RUN   TestAccCloudflareSnippetRules
=== PAUSE TestAccCloudflareSnippetRules
=== CONT  TestAccCloudflareSnippetRules
    resource_test.go:55: Step 1/2 error: Error running apply: exit status 1

        Error: failed to create snippet rules

          with cloudflare_snippet_rules.qciadqjjip,
          on terraform_plugin_test.tf line 12, in resource "cloudflare_snippet_rules" "qciadqjjip":
          12:   resource "cloudflare_snippet_rules" "qciadqjjip" {

        can not decode parameters json
--- FAIL: TestAccCloudflareSnippetRules (0.90s)
FAIL
FAIL	github.com/cloudflare/terraform-provider-cloudflare/internal/framework/service/snippet_rules	2.144s
FAIL

Yeah, it's the answer from snippets-api service. Should be fixed with: https://github.com/cloudflare/cloudflare-go/pull/3669

ah, so there is another dependent PR. sorry, missed that.

Now that https://github.com/cloudflare/cloudflare-go/pull/3669 is merged, can we roll this out? :D

acceptance tests all passing here
=== RUN   TestAccCloudflareSnippetRules
=== PAUSE TestAccCloudflareSnippetRules
=== CONT  TestAccCloudflareSnippetRules
--- PASS: TestAccCloudflareSnippetRules (14.26s)
PASS
ok  	github.com/cloudflare/terraform-provider-cloudflare/internal/framework/service/snippet_rules	15.629s


octant hangs on remote, headless Linux servers

When I run octact on a remote, headless server, octant hangs in the browser.

octant is launched with: $ OCTANT_LISTENER_ADDR=<IP_ADDRESS>:8900 octant -vvv
octant logs only show DEBUG and INFO, no ERROR or WARN (other than the expected unable to open browser because xdg-open is not found).
Logs
I've tried with a single-node kind cluster as well as a multi-node kind cluster locally and on the remote server. Octant works fine locally.

You can add the OCTANT_DISABLE_OPEN_BROWSER=1 flag to prevent the xdg-open error.
Also I believe this might be related to #152 (fixed in master). Our next release is ~ August 20th and will have that fix in it.


Large files (8GB or above usually) frequently fail to transfer midway.

What exactly happens when the files fail? Do other app functions continue to work after this fails?


Rename all BackProp to Backprop for consistency.

Resolving issue #12515.
First attempt to start contributing to tensorflow.

Can one of the admins verify this patch?

@googlebot I signed.

Jenkins, test this please.

Mac fails on
//tensorflow/cc:gradients_nn_grad_test and //tensorflow/go:test. Trying again.
Jenkins, test this please.


Question: Make it easier to checkout & build & contribute

Current obstacles:

[x] Generated sources are missing

Use gradle generateMappers if connecting directly to the swagger-springfox projects; the recommended approach is to publish to a local maven repo (see bottom)

[x] Troubles with the Logger (Logback vs. slf4j)

Only exists when connecting directly to the swagger-springfox projects

[x] Deploy gradle artificats into maven repository (for reuse with maven-based projects) (/)

see replies at the bottom

[ ]  Default IDE is idea: Eclipse will be added by @dilipkrish to the gradle buildfile

Generated sources are missing
Currently, after checkout & build using gradle, it is not possible to start the springfox modules with the springfox demos, because the generated sources are missing completely.
(see my comment at #1088 regarding ServiceModelToSwagger2MapperImpl).
One has to find out that the ServiceModelToSwagger2MapperImpl has to be generated & the generated-src/main folder has to be added to the buildpath in order to use the Springfox libraries.
So it would be nice if the generateSrc target is also added to the build.gradle build options.
The sources should be generated & added to the buildpath automatically.
Then it would be possible to checkout & build and immediately reuse the sources with the springfox-demos (for analyzing/contribution).
Troubles with the Logger (Logback vs. slf4j)
I couldn't start my project connected to the Springfox-sources due to troubles with multiple loggers.
After removing all dependencies in the Springfox-modules to logback manually, I was able to start the Spring Boot server eventually.
Log output after cleaning up:
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/c:/mymavenrepo/ch/qos/logback/logback-classic/1.1.5/logback-classic-1.1.5.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/C:/Users/MyUser/.gradle/caches/modules-2/files-2.1/org.slf4j/slf4j-simple/1.7.13/8f0d8b5bf0ff295162360a0a5ebb9c945bd2b685/slf4j-simple-1.7.13.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [ch.qos.logback.classic.util.ContextSelectorStaticBinder]

Deploy gradle artificats into maven repository
It would be nice to give hints how to deploy the gradle artifacts into a maven-repository, so they can be reused easily in maven-based projects (for now I added the springfox-modules directly as referenced projects).
Default-IDE is idea
Maybe it would make sense to use a non-commercial IDE as default (i.e. eclipse)

@jfiala Sorry Ive been  a lil busy.

Currently, after checkout & build using gradle, it is not possible to start the springfox modules with the springfox demos, because the generated sources are missing completely.

This doesn't seem right. Everything should build just fine o/w the CI builds would be failing. Are you perhaps referring to IDE specific issues?

So it would be nice if the generateSrc target is also added to the build.gradle build options.
The sources should be generated & added to the buildpath automatically.

This is exactly what this does. Now this could be improved perhaps.

It would be nice to give hints how to deploy the gradle artifacts into a maven-repository, so they can be reused easily in maven-based projects (for now I added the springfox-modules directly as referenced projects).

I'll add notes on how to do that. Basically you'd need to run, to publish to you local maven
    ./gradlew clean build publishToMavenLocal

Maybe it would make sense to use a non-commercial IDE as default (i.e. eclipse)

👍 for that. Only that I don't use Eclipse and don't have the time to invest in figuring out or supporting eclipse configurations. Would applying the eclipse plugin work? Would be great if you could perhaps chip in.

This doesn't seem right. Everything should build just fine o/w the CI builds would be failing. Are you perhaps referring to IDE specific issues?
I can start the Springfox demos (directly connected to the Springfox sources) only if I run gradle generateMappers. If I don't do so, I'm missing the generated sources (and get "No qualifying bean of type [springfox.documentation.swagger2.mappers.ServiceModelToSwagger2Mapper]").

This is exactly what this does. Now this could be improved perhaps.
Yes, but generateMappers is not part of the default build (running simply gradle with no tasks specified)

Would applying the eclipse plugin work?
I'm using Eclipse and all I had to do so far was adding "apply plugin: 'eclipse'" to the subprojects root build.gradle file:

subprojects {
  apply plugin: "com.ofg.uptodate"
  //Not strictly groovy projects but useful for the IDE to recognise groovy test sources
  apply plugin: 'groovy' //gradle groovy plugin extends the java plugin
  apply plugin: 'com.github.adrianbk.jvmsrc'
  apply plugin: 'checkstyle'
// this is all to get eclipse to work
apply plugin: 'eclipse'

Then I run "gradle eclipse" and the eclipse specific project files are generated correctly (.project, .classpath).

Not sure I follow your comment about the springfox demos. Your workflow should be to build springfox locally and use the SNAPSHOT published to your maven local repo as a dependency. i.e.

Build springfox ./gradlew clean build publishToMavenLocal
update the springfox-demos to use the snapshot version in this case currently it is 2.4.1-SNAPSHOT
Build demos using ./gradlew clean build

There is no default gradle task. Just like in maven you need to run mvn clean install in gradle you need to run ./gradle clean build
I'll add eclipse plugin to the projects so that its easier and update these instructions in the documentation. Thanks for that feedback! 👍

Great thank you, the problem only exists if I'm connecting directly to the swagger-springfox projects, and using generateMappers it's easy to fix that. So all tasks except the eclipse plugin are resolved.

The last point has been addressed as well


Metadata and subkey column family share a singleblock cache

By default, metadata Column Family and subkey Column Family have their own block cache, so block cache must be allocated in advance for the two CFs.
It is not possible to predict the usage of the two CFs and allocate the optimal capacity for the two block caches, so we can provide a configuration item that specifies whether the two CFs should share a single block cache (see rocksdb Wiki).
Regarding this configuration item, although it is not an item for Rocksdb Option, it is related to Rocksdb, so I gave it a name prefixed with rocksdb..

wow, really a good feature.


Move bootloader main to examples

This should remove some confusion around embassy-boot-* being a library
vs. a binary. The binary is now an example bootloader instead.

bors r+


Unable to load models

Clean install on Ubuntu 22.04 LTS, and it's not finding the models, or letting me install a backend. Am I missing a backendlist.yaml?
******************* Building Personality from main Process *************************
Couldn't build model
unsupported operand type(s) for /: 'PosixPath' and 'NoneType'
When I try to install a backend I get this error:
(env) zino@dev2:~/apps/gpt4all-ui$ python3 installations/install_backend.py
Traceback (most recent call last):
File "/home/zino/apps/gpt4all-ui/installations/install_backend.py", line 51, in
with open('backendlist.yaml', 'r') as f:
FileNotFoundError: [Errno 2] No such file or directory: 'backendlist.yaml'

Where is Model Zoo in the settings?

Its  old UI.      NEW UI  have Model Zoo.
NEW UI  change  "GPT4All\configs\local_default.yaml"  use_new_ui: true .

@ParisNeo I cant load models through the model zoo. When I select the desired model, it does not download. Download speed stuck at 0 B/s. Any suggestions?