Android compatibility

Hi,
Couple days ago I tried to use your framework in my Android application and stumbled on problem of compability.  As for android, they have their java SDK, that a bit differs from standard.
Orka uses java.beans.Introspector to do it's magic and, if I am correct, it puts dependency on whole java AWT.  And the problem is, that there is no real reason to port and maintain whole AWT to android, see link. There are only few things left from java.beans, see link.
In return google proposes their implementation of most classes (except functionality that deals with AWT) from java.beans in their openbeans library , which includes Introspector.
It would be great if orika acquired android platform compatibility (there are not good alternatives for convenient mapping in Android, unfortunately).
P.S.: I guess that there is no real standard (like an interface in java library) that can describe Introspector, but still, maybe it is sensible to provide some way to swap Introspectors? For example define your own interface with default implementation from open beans or even java.beans and allow to easily swap it. That way orika will become event more independent from external libraries.

Ok, tried to replace all java.bean dependencies for openbean (there were like 8-9  imports) and it seem to compile and pass all tests. Not tested if it deploy ok on android yet.
Can I get permissions to push my branch to your repo?

This replacement may possibly solve work around that briefly saw when replaced dependencies in test classes (IntrospectorBugTestCase and SpecifiedGenericsTestCase).

Ok it looks like simple replacment to openbeans solves issue with Introspector on android.

Ok, now I am getting another error about class not being accessible
How to reproduce:
Originally was written in kotlin, translated to java by hand (still must compile).
Run as android instrumented test on emulator device:
@RunWith(AndroidJUnit4.class)
class CarMappingTest
{
    @Test
    public void testCarMapping()
    {
        MapperFactory mapperFactory = DefaultMapperFactory.Builder().build();
        MapperFacade mapperFacade = mapperFactory.getMapperFacade();

        CarDto carDto = CarDto("Ford");
        Car car = mapperFacade.map(carDto, Car.class);

        Assert.assertEquals(carDto.getModel(), car.getModel());
    }
}

public class Car
{
   String model;
   //Constructor, getters setters
}
public class CarDto
{
   String model;
   //Constructor, getters setters
}

Emulator device properties
Name: Nexus_5X_API_28
CPU/ABI: Google Play Intel Atom (x86)
Path: C:\Users\Elan-PC\.android\avd\Nexus_5X_API_28.avd
Target: google_apis_playstore [Google Play] (API level 28)
Skin: nexus_5x
SD Card: 100M
hw.dPad: no
hw.lcd.height: 1920
runtime.network.speed: full
hw.accelerometer: yes
hw.device.name: Nexus 5X
vm.heapSize: 256
skin.dynamic: yes
hw.device.manufacturer: Google
hw.lcd.width: 1080
hw.gps: yes
hw.initialOrientation: Portrait
image.androidVersion.api: 28
hw.audioInput: yes
image.sysdir.1: system-images\android-28\google_apis_playstore\x86\
tag.id: google_apis_playstore
showDeviceFrame: yes
hw.camera.back: virtualscene
hw.mainKeys: no
AvdId: Nexus_5X_API_28
hw.camera.front: emulated
hw.lcd.density: 420
avd.ini.displayname: Nexus 5X API 28
hw.arc: false
hw.gpu.mode: auto
hw.device.hash2: MD5:bc5032b2a871da511332401af3ac6bb0
hw.ramSize: 1536
hw.trackBall: no
PlayStore.enabled: true
fastboot.forceColdBoot: no
hw.battery: yes
hw.cpu.ncore: 2
hw.sdCard: yes
tag.display: Google Play
runtime.network.latency: none
hw.keyboard: yes
hw.sensors.proximity: yes
disk.dataPartition.size: 2G
hw.sensors.orientation: yes
avd.ini.encoding: UTF-8
hw.gpu.enabled: yes

Stack trace
ma.glasnost.orika.MappingException: While attempting the following mapping:
sourceType = edu.hd.elan.mom.repository.service.CarDto
destinationType = edu.hd.elan.mom.repository.service.Car
Error occurred: ma.glasnost.orika.impl.generator.CompilerStrategy$SourceCodeGenerationException: class edu.hd.elan.mom.repository.service.CarDto is not accessible
at ma.glasnost.orika.impl.generator.MapperGenerator.build(MapperGenerator.java:104)
at ma.glasnost.orika.impl.DefaultMapperFactory.buildMapper(DefaultMapperFactory.java:1478)
at ma.glasnost.orika.impl.DefaultMapperFactory.lookupMapper(DefaultMapperFactory.java:738)
at ma.glasnost.orika.impl.MapperFacadeImpl.resolveMapper(MapperFacadeImpl.java:566)
at ma.glasnost.orika.impl.MapperFacadeImpl.resolveMappingStrategy(MapperFacadeImpl.java:178)
at ma.glasnost.orika.impl.MapperFacadeImpl.map(MapperFacadeImpl.java:669)
at ma.glasnost.orika.impl.MapperFacadeImpl.map(MapperFacadeImpl.java:649)
at edu.hd.elan.mom.repository.service.EventCrudRepositoryImplTest.tmp(EventCrudRepositoryImplTest.kt:76)
at java.lang.reflect.Method.invoke(Native Method)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at android.support.test.internal.runner.junit4.statement.RunBefores.evaluate(RunBefores.java:80)
at android.support.test.internal.runner.junit4.statement.RunAfters.evaluate(RunAfters.java:61)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at android.support.test.runner.AndroidJUnit4.run(AndroidJUnit4.java:101)
at org.junit.runners.Suite.runChild(Suite.java:128)
at org.junit.runners.Suite.runChild(Suite.java:27)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
at org.junit.runner.JUnitCore.run(JUnitCore.java:115)
at android.support.test.internal.runner.TestExecutor.execute(TestExecutor.java:56)
at android.support.test.runner.AndroidJUnitRunner.onStart(AndroidJUnitRunner.java:384)
at android.app.Instrumentation$InstrumentationThread.run(Instrumentation.java:2145)
Caused by: ma.glasnost.orika.impl.generator.CompilerStrategy$SourceCodeGenerationException: class edu.hd.elan.mom.repository.service.CarDto is not accessible
at ma.glasnost.orika.impl.generator.JavassistCompilerStrategy.assureTypeIsAccessible(JavassistCompilerStrategy.java:172)
at ma.glasnost.orika.impl.generator.MapperGenerator.build(MapperGenerator.java:56)
... 37 more
Caused by: javassist.NotFoundException: edu.hd.elan.mom.repository.service.CarDto
at javassist.ClassPool.get(ClassPool.java:445)
at ma.glasnost.orika.impl.generator.JavassistCompilerStrategy.assureTypeIsAccessible(JavassistCompilerStrategy.java:170)
... 38 more

Looks like atm I won't get time to look to it closer, I will try to get back to it later.

any news on this?

@ataraxus didn't try it afterwards, done all mapping by hand in that project (at least it was only few classes).

Hello @ElanHD ,
Thanks for sharing your use case with us!
I'm contributor as you.  I'm a big advocate of orika-mapper. I used it before in Java EE setup and it saved a lot boilerplate code for us. I follow the issues and try to help with what I can.
I'm very far from Android development the recent years so I just follow your ideas. If you want to discuss more interactively you can also join our CHAT room.
I think the original authors haven't imagined the usage of orika with Andorid SDK. :)


[GSSOC'23] [Hovering of send button is blending Button ]

What happened?
when the send button in contact section is hovered its blending with the background here are images:
before hovering:

while hovering:

Please assign me this issue to fix and contribute under gssoc'23.
I would like to have any suggestions if you have any specific colors in your mind  to replace for that button 's hovering color
How can we reproduce this bug?

open the contact section

click on send button

Desktop Information (Optional)
No response
Urgency (Optional)
None

I want to resolve this bug, Can you please assigned me this task?

Too easy issue


Add the Contributor Covenant Code of Conduct v2.1

Things added/changed.

Add the Contributor Covenant Code of Conduct v2.1.

Sir


VSTS Extension - How to get selected suite data from test suites table on loading of custom tab

I'm developing a VSTS extension in Javascript. In one of my tasks, I develop a custom tab and need to load data on an HTML page on behalf of the selected Test Suite.
How can I get data(like SuiteID, Testplan ID) of the selected Test Suite?

I am trying to implement the same feature with a custom extension . Could you please update if you have found some solution around this @sachin5531 .


What is the "project keyfile"?

You mention in the installation instructions to:
<your project key file location>' //REQUIRED

What is this?
All I have are:
secret.json
resources/tokens.js

Also:
What is the difference between the simple version and full version configurations?

@E3V3A
stt section is speech to text, - Google Cloud speech API.
You should have to make or assign project to use Google APIs in Google Cloud Platform. Then you should obtain project key file with right permission of using Google APIs for your project. You can download that keyfile in Credentials section of your project in Google Cloud Platform.
Put that file under your MMM-Assistant directory or below, and describe that path.

The difference is... nothing. the full version is filled with default values, so simple version and full version are identically same. However, you can modify detail values with full version configuration.

Sorry, I simply don't understand. Is that file different from the 2 i mentioned above?
I went through the procedure and have only those two files.
What is is called? Where is it generated?

Oh, is it the one containing your private key??

Let's meet in chat room in magicmirror forum.

Ok, this is the story. Following the steps in the WIki.
These are very unclear:
detailed steps for Google Cloud Speech API

    Back to API & Services > Dashboard again.
    Select ENABLE APIS AND SERVICES
    Search Google Cloud Speech API and dive into.
    Press ENABLE.
    Select Create Credentials and Service Account Key. (It's obvious to be able to use secret.json again.
For safe, I'll create another key file for Google Cloud Speech)
    Set the details (anything for service account name, Project>Owner for Role, anything for
service account id, JSON for key type. After set, you can download your key file.
    It will be used in config.stt.auth

Tip : You can obtain keyfiles more than one if you can make another account. It could be helpful for
saving money. (Google Speech API is very cheap, but not free. It allows you 60 minutes for free per
month. But every recognition request is considered as minimum 15 seconds. So exactly 240 requests
would be available for free. Additional request will be charged $0.006 per request. Anyway, if you create
an account at the first time, about $300 for 1 year will be given freely.)

After you have added and enabled the two API's and services in your Dashboard:

Google Cloud Speech API
Google Assistant API

You will have at least 2 types of credentials under your Credentials part of the Dashboard, if you followed the previous steps. But there are 3 different types of credentials:

API keys
OAuth 2.0 client IDs
Service account keys

If you don't already have a Service Account showing up there, you need to create one.  Click on the Create credentials drop-down button. There you select the Service account key option.  The next page will ask you the account to use, and what key type for the file to use. Select JSON, and save this key.  The filename of this key will be something like: PROJNAME-a1b2c3d4e5f6.json. This is the "key-file" you need to save and add in your simple config.js.

NOTE: This is the private API key for this account, and project. It means that any one with
this key can use tools to obtain info you have here. (I'm not sure if this is sandboxed from you email etc.)

If you already have one:

Click on the [Manage service accounts](https://console.developers.google.com/iam-admin/serviceaccounts) text.
Then you should already have a key somewhere, but if you lost it, you can create a new one by selecting the "3-dots" menu at the far right of the account. Clicking on it, there is the option Create key,
elect it and (as above) save the resulting file. Just remember that you now will have two accounts, so that you match the key with the account id later. (???)

more to come

Thanks.  You can modify it by yourself because wiki is opened for everyone.

@eouia

because wiki is opened for everyone

Nope, first thing I checked!

Sorry. It was restricted as you've said. I modified that option now.


Support of DES for Microsoft Dataverse environment

If the Data Export Service is only supported for the environments with D365 customer engagement apps installed and not for pure Microsoft Dataverse environment at the moment, it would be great if that fact is mentioned in the document specifically until it is supported for all Dataverse environments.
E.g. At the moment, you cannot install the Data Export Service in the Microsoft Dataverse environments without customer engagement apps.

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

ID: 3d51ad6f-b7a7-7abd-f1d1-1d7963dd3d49
Version Independent ID: 4612ff88-8457-2f49-8222-4fd110fd72f6
Content: Replicate data to Azure SQL Database using Data Export Service - Power Platform
Content Source: power-platform/admin/replicate-data-microsoft-azure-sql-database.md
Service: power-platform
GitHub Login: @jimholtz
Microsoft Alias: jimholtz

DES is an add-on for CE. WE also cover this under pre-requisites - https://docs.microsoft.com/en-us/power-platform/admin/replicate-data-microsoft-azure-sql-database#prerequisites-for-using-
For exporting Dataverse table data to data lake, we recommend 'Export to data lake' -
https://docs.microsoft.com/en-us/powerapps/maker/common-data-service/export-to-data-lake#:~:text=Transporting an Export to Data Lake configuration across,to Data Lake configuration. ... 4 See also


Upgrade versions and readme

SBT to 1.2.8
Scala to 0.14.0-RC1
sbt-dotty to 0.3.1

LGTM, thanks @fermiyon


Exposure logging is not possible / Exposure logging active

Describe the bug
Status bar below the title bar tells me "EXPOSURE LOGGING ACTIVE". The main content of the app tells me

Exposure logging is not possible. Your exposure logging could not be updated for more than 24 hours. Updated: 16 Jun, 11:30.
ACTIVATE EXPOSURE LOGGING

Pressing on ACTIVATE EXPOSURE LOGGING brings me to a screen which tells me Exposure Logging is already active. (checkbox is set to 'Active', subtext says "Exposure logging has been active for 2 days. [...]". I also tried disabling and re-enabling it.
Going back to the main screen (or killing the app and reopening it) yields the same state.
When initially installing it on Tuesday, 16.06. it seemed to work fine (Unsure about version, possibly 1.0.0?) and on Wednesday gave me a status of "Low Risk", so it seemed to be working. Yesterday afternoon I also updated to 1.0.2 via Google Play Store. However, I cannot tell if it is really due to the updated version or some other cause.
Expected behaviour
Exposure logging works or consistently tells me it doesn't work and for what reason. I'm getting mixed signals here.
Steps to reproduce the issue
Screenshots are disabled in the app.
Technical details

App version: 1.0.2
Phone model: Xiaomi Mi 9T (Snapdragon 730)
Android MIUI <IP_ADDRESS> (Android 10)

Additional context
Bluetooth and location services are enabled. The phone supports BLE.

Update: seems to work again. Backend server issues?

Hi @mueslo,
thank you very much for reporting this! We are currently investigating this issue and will come back to you as soon as possible. If you can provide us with additional details, it might help a lot to identify the root cause for this behavior:
Did you change your phone date & time setting recently, disable background activity for the Corona-Warn-App or change the battery optimization settings for the Corona-Warn-App?
Thank you very much and best,
Marc

Same problem here with a Xiaomi Mi 9 Lite. Mine is showing "Risk calculation not possible", "Last updated on Monday", but the update should have happened yesterday see also #590

@mbw83 thanks for the reporting this and the follow-up, it's much appreciated and
I am glad to hear that it is now working for you!
Nevertheless we are currently monitoring this and can hopefully provide an update soon.

Have the same issue with Huawei Mate 20 Pro (installed since tuesday, info widget that risk calculation is inactive, please activate, but on second screen is still active (since 2 days)). Probably caused by the battery settings for the app. I have reinstalled the app and deactivated auto settings. I will report tomorrow

I have the exact same issue on a Samsung Galaxy S7, Stock Android 8.0.0.
App installed from Google Play.
Last night it was still snowing me "low risk".
Trying to activate or deactivate the power saving mode doesn't affect this issue.

Hi @mueslo,
thank you very much for reporting this! We are currently investigating this issue and will come back to you as soon as possible. If you can provide us with additional details, it might help a lot to identify the root cause for this behavior:
Did you change your phone date & time setting recently, disable background activity for the Corona-Warn-App or change the battery optimization settings for the Corona-Warn-App?
Thank you very much and best,
Marc

None of the above. However, I do know that MIUI has very strict battery saving behaviour by default (i.e. apps in the background will be killed after a while, e.g. if you want to use a GPS logging app you need to manually set exceptions so your GPS tracing doesn't suddenly stop after 5 minutes). Can you tell me more about what you believe error means? Does the app need to stay on for logging to work? (I was under the impression BLE public key collection is handled in the background by the Android system itself) Or does the error mean it could not get the newest compromised public keys from the backend? If you like I can keep my phone with my current settings and see if it reoccurs, and then manually disable "MIUI optimized battery saving"

I have the same issue with a Samsung Galaxy S10,
Android 10. The recording stopped on the 16th at 9:25 am.
I have added the App to the list of apps, that shall not be put into standby. I have been in energy-saving-mode.
If you need any more info, im happy to provide it.
Best regards

@all
Thank you lots for the detailed reports, we highly value your contributions to find and fix existing errors!
We have identified this issue and are working on a fix that should be rolled out soon. I will keep you posted once this is resolved.
Thanks again to all of you!
Best,
Marc

I can also confirm.
Device: Huawei P smart+ with Android <IP_ADDRESS>7
My first guess would be that the strict battery manager stops the background functions. But I see you guys are already on the issue.

Same issue here on a Huawei Honor 20 Lite.
Installed Tuesday morning, on Wednesday morning it showed me "Low Risk", when I looked this evening, I noticed the problem.
I first thought it was due to the GoPro app yesterday fiddling around with Bluetooth settings.
But then I noticed "RISIKO-ERMITTLUNG AKTIV", "Risiko-Ermittlung nicht möglich" and a button "RISIKO-ERMITTLUNG AKTIVIEREN" on the same screen, which is contradicting itself and thus very bad UX.
Version is still 1.0.0, I will update now.

Same issue here with redmi note 7. I already tried the suggestions you mentioned but I still can't see my infection risk.

Same on Xiaomi Mi Note 10 Lite/Pro.
Reboot does not fix the issue.

Same here iPhone 7 Plus.
Reboot and changing Corona App "Risko-Ermittlung" off and on, doesnt solve the problem.
Background Update is for the Corona App kind of light green (not as usual full green) and is not changeable under settings.

@ all
Thank you lots for the detailed reports, we highly value your contributions to find and fix existing errors!
We have identified this issue and are working on a fix that should be rolled out soon. I will keep you posted once this is resolved.
Thanks again to all of you!
Best,
Marc

Hi @marcmuschko, would it be possible to say what the problem is in a few words and reference the branch (if public) that you are working on?

Hi @marcmuschko, would it be possible to say what the problem is in a few words and reference the branch (if public) that you are working on? It's nice for the community to be in the loop and not just get notified once the fix is rolled out.

It sounds to me like the background key lists are not retrieved if the app is put to sleep or killed. https://github.com/corona-warn-app/cwa-app-android/tree/feature/key-retrieval-on-resume
I really hope key broadcast and collection are still working though...
So yeah, I too would appreciate a short outline of what the current working theory is.

Same Problem with Xiaomi Mi 9 running Android 10.

I have the same problem with a Xiaomi Redmi Note 8T running Androidversion 9PKQ1.190616.001.
MIUI-Version:  MIUI Global 11.0.9 Stable <IP_ADDRESS> (PCXEUXM)

Sry, i found my problem.
The App Version was 1.0.0.
I thought, the app will updateing automaticy, but the app wasn't.
Now i updatet the app manually by the Google play store to 1.0.2 and that solved the problem for me. :)

Hi @mueslo,
thank you very much for reporting this! We are currently investigating this issue and will come back to you as soon as possible. If you can provide us with additional details, it might help a lot to identify the root cause for this behavior:
Did you change your phone date & time setting recently, disable background activity for the Corona-Warn-App or change the battery optimization settings for the Corona-Warn-App?
Thank you very much and best,
Marc

The issue is also found here on a fully updated Huawei Mate 10 Pro (Android 10, EMUI 10.0.0, Play Services 20.18.17)  with CWA V1.0.2. It is fully unclear whether the App is actually working or not. Nothing changed.
Maybe of interest:

The issue persists despite re-boot
turning on/off tracing does not help either

Same issue with Galaxy S10e (Android 10, One UI Version 2.1, SecurityPatch 1.6.2020)

Same problem with Huawei p20 pro.

Quelle: https://basic-tutorials.de/corona-warn-app-ihre-risiko-ermittlung-konnte-seit-mehr-als-24-stunden-nicht-aktualisiert-werden/

Same problem here with my Huawei P30 Pro.
Even the workaround https://basic-tutorials.de/corona-warn-app-ihre-risiko-ermittlung-konnte-seit-mehr-als-24-stunden-nicht-aktualisiert-werden/
didn't solve it.

Same problem on Mi 9T running Android 9.
Reboot and Blogpost did not fix it.

Worked for me (Huawei Honor 20 Lite), but "einige" Minuten was definitely > 15.

Same issue here on Xiaomi 9T, Andorid 10, MIUI 11.0.5. Only way to get the app to update its status once is a reboot. For the next update I have to reboot another time at least 24h later.
Intuitively without any evidence I assume it has something to do with the energy saving mode of MIUI, maybe disabling some aspects of the app.

P30 Pro here, having the same issue. It worked fine on the first day, but it didnt refresh yesterday and today it said "Risikoermittlung nicht möglich"

Same issue here on a Huawei Honor 7. First day no issues. Now the error message everyone has already reported despite logging being shown as active.

Same here. Xiaomi Note 7. Also i can't make Screenshots of the app.

Same here on Xiaomi Mi 9.

Same on Huawei Mate 9 Pro, latest OS patch level

Solved the issue on Xiaomi Mi9, MIUI 11, Android 10, by turning off all energy savings for the Corona App.

Gleiches Problem bei
Mi 9t(MIUI Global 11.0.5)
Redmi note 6
Redmi note 7

Hey,
same problem on Honor 20 with Android 10.
Risk couldnt be determined since June 17, 2020.
Btw: Thanks for your work 👍

Same with my Huawei Mate 10 pro, Android 9 including newest Patches.

Same here on Xiaomi Mi 9.

Same here on Xiaomi Redmi Note 8

thanks Freche17 - same with my Xiaomi Redmi Note 8 - Android 9 !!!!  A call with a member of the hp of coronawarn.app: pls delete app and new download - haha!!! no result. SAP hotline gives me the same number so no-one could help!!! 3 days app on the phone, no green block. till now: Ungekanntes Risiko Da Sie die Risiko-Ermittlung noch nicht lange genug aktiv... blabla!!! F...k - no trial bevore release?!

Huhu! Sprichst Du deutsch?
birgit-xy<EMAIL_ADDRESS>schrieb am Fr., 19. Juni 2020, 17:31:

thanks Freche17 - same with my Xiaomi Redmi Note 8 - Android 9 !!!! A call
with a member of the hp of coronawarn.app: pls delete app and new download

haha!!! no result. SAP hotline gives me the same number so no-one could
help!!! 3 days app on the phone, no green block. till now: Ungekanntes
Risiko Da Sie die Risiko-Ermittlung noch nicht lange genug aktiv...
blabla!!! F...k - no trial bevore release?!

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/corona-warn-app/cwa-app-android/issues/637#issuecomment-646699353,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQAL4XXRCZRTCNBTXT3LKZTRXOAGFANCNFSM4OBP5J5A
.

 Hier noch einmal zum Nachlesen die Anleitung
https://www.androidpit.de/corona-warn-app-probleme-loesungen-fehler-bugs?amp=true

I think I have the solution: You have to turn on the autostart in the app settings for the Corona app, then it works at least for the Xiaomi Redmi Note 8. Here you can read the instructions again
https://www.androidpit.de/corona-warn-app-probleme-loesungen-fehler-bugs?amp=true

Hallo Freche17, klar spreche ich Deutsch. Bei mir funktioniert es leider so nicht.... aber vielleicht habe ich etwas übersehen... danke dir!

@Freche17 ... bei mir steht trotz aller mehrfachen Versuche (Auto start ein, wieder aus, jedesmal Handy neu gestartet) immer noch, dass die App aktiv ist - aber darunterdass sie seit 0 Tagen aktiv sei! Widerspricht sich. In einem anderen Blog heißt es, dass man extra den Auto Start ausschalten soll, dann würde es funktionieren. https://basic-tutorials.de/forum/threads/corona-warn-app-ihre-risiko-ermittlung-konnte-seit-mehr-als-24-stunden-nicht-aktualisiert-werden.4149/ -Wie auch immer - es geht einfach nicht

@birgit-xy
Achtung! Hier ist evtl. etwas mehr Geduld gefragt.  Nur neu starten reichte jedenfalls nicht aus.
Insgesamt ist dieser Fehler trotzdem völlig überflüssig und v.a. schädigt er der Akzeptanz der App. Die Anmerkung "Google Play Services" noch neuerer Bauart zu installieren ist ein Witz, denn die aktuell installierte Version ist weniger als drei Wochen alt und externe Pakete einzubinden ist dem Sicherheitsstandard nicht zuträglich.

 Das hat nichts gebracht. Dann Energiesparen ausgeschaltet, Neustart, und dann ging's.

Same problem with my huawei p20 pro. Bugfix haevn't worked yet.

Have you tried it with setting the app on autostart?
FraumitKlasse<EMAIL_ADDRESS>schrieb am Fr., 19. Juni 2020,
23:08:

Same problem with my huawei p20 pro. Bugfix haevn't worked yet.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/corona-warn-app/cwa-app-android/issues/637#issuecomment-646861125,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQAL4XSN3WIAAIWAJJC5IX3RXPHVLANCNFSM4OBP5J5A
.

Same problem here on a Oneplus 3T, OygenOS 9.06.
Workarounds like restart of the phone and disbaling energy saving did not work.

Same here with Asus zenfone 6, Android 10

Bug appears on current iOS as well (iPhone X).

Mine is again not updating. It still says that it was updated the day before yesterday, but it think this afternoon it will turn again to "Risk calculation not possible". I think this bug is also related to #621.

Hi @marcmuschko, would it be possible to say what the problem is in a few words and reference the branch (if public) that you are working on? It's nice for the community to be in the loop and not just get notified once the fix is rolled out.

@marcmuschko would it be possible to give a small update? For me it must not be the branch, just a short status update would be good. This would also prevent, these weird things going on here in this thread. As far as I understand, the big advantage of using the Google/Apple API is, that the app doesn't have to be running the whole day, just because the logging is made by the API. The only thing the app has to do is to download the infected keys from a server every 24 hours. So why setting some settings in regard to autostart or battery saving?
Nevertheless, even my instant messaging and email apps are able to work without setting these options.

I've been successfully by using Einstellungen (settings) --> Akku (battery?) --> App-Start --> Corona-Warn --> Manuell verwalten (manage manually?) --> turned of every button manually --> turned on every button manually --> restarted my mobile --> repeated a fiew times
Today in the morning the app looks like working.
I't would be fine to fix the bug, some people I know would have given up yet.
Thanks!

Have you tried it with setting the app on autostart? FraumitKlasse<EMAIL_ADDRESS>schrieb am Fr., 19. Juni 2020, 23:08:
…
Same problem with my huawei p20 pro. Bugfix haevn't worked yet. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#637 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQAL4XSN3WIAAIWAJJC5IX3RXPHVLANCNFSM4OBP5J5A .

Having the same issue on a honor 9 (SFT-L09) smartphone.
None of the "Tipps and Tricks" above worked so far.

I've got a case here with a HUAWEI P smart (2018) that's showing the same problems; I've just deactivated the startup management, but it at least didn't lead to an immediate update. Software versions are current.
Maybe have a (rate limited) force update button, to circumvent that the app is only doing an update every 24h or so?

Same issue with Galaxy A3 (2017) and Android version 8.

At first, my risk level was not updated as described in #621, thus I turned off energy saving (Switch "Energiesparmodus" to "Keine Beschränkungen"). 48 hours after last update I received a new one, but a few hours later my risk level changed to unknown and the situation became as described by @mueslo in this issue. After restarting my phone for approximately 5 times the risk level is back again.

Same here, Huawei P10, Android 9, active since 4 days but no status update. Already did set permissions in App-Start to manual management, but did not know that i should restart. Will see if restart will fix the issue now...

Same here Huawei P20 lite, all automatic energy-management settings disabled for CWA. Sayys "Risiko-Ermittlung aktiv" and then "Risiko-Ermittlung nicht möglich: Ihre Risiko-Ermittlung konnte seit mehr als 24 Stunden nicht aktualisiert werden."

das selbe Problem seit heute auf mein Huawei P30 Pro.. keine Aktualisierung möglich trotz eingeschalteter Risikoüberwachung..

Same Problem with Huawei P20

Same on my Honor 10 with Android 9 (Kernel 4.9.148)
Was working initially, but not any longer.....

Von: martinhd<EMAIL_ADDRESS>Gesendet: Samstag, 20. Juni 2020 18:13
An: corona-warn-app/cwa-app-android
Cc: birgit-xy; Mention
Betreff: Re: [corona-warn-app/cwa-app-android] Exposure logging is not possible / Exposure logging active (#637)
Same on my Honor 10 with Android 9 (Kernel 4.9.148)
Was working initially, but not any longer.....
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/corona-warn-app/cwa-app-android/issues/637#issuecomment-647014986 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AQAMM7FTMWZ5A2GFOKHLQZTRXTNZ5ANCNFSM4OBP5J5A .  https://github.com/notifications/beacon/AQAMM7A543JXCXT557SOTW3RXTNZ5A5CNFSM4OBP5J5KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOE2IKUSQ.gif

Same issue here with an Honor 8x with Android 10 and latest SW and security patches installed. Installed the app right after it was released on Tuesday, it worked as intented first and showed me a green status on Wednesday, on Thursday it said exposure logging was not working. Restart of the app or phone did not work, updating the app in the play store neither. I ended up uninstalling and reinstalling the app. It worked on Friday, but today on Saturday it was the same again. Seems it works for 2 days (48 hours?) and then stops. Will try to change battery saving settings for the app and see if that makes a difference, but the issue should be solved for non tech savvy users.

I have now had battery saver disabled and autostart enabled for around a
day, and the bug remains.
On Sat, 20 Jun 2020, 19:08 cant-think-of-aname<EMAIL_ADDRESS>wrote:

Same issue here with an Honor 8x with Android 10 and latest SW and
security patches installed. Installed the app right after it was released
on Tuesday, it worked as intented first and showed me a green status on
Wednesday, on Thursday it said exposure logging was not working. Restart of
the app or phone did not work, updating the app in the play store neither.
I ended up uninstalling and reinstalling the app. It worked on Friday, but
today on Saturday it was the same again. Seems it works for 2 days (48
hours?) and then stops. Will try to change battery saving settings for the
app and see if that makes a difference, but the issue should be solved for
non tech savvy users.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/corona-warn-app/cwa-app-android/issues/637#issuecomment-647021852,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAGO7B3UCVKLC4YY7AX7AWLRXTUJNANCNFSM4OBP5J5A
.

Same problem:

Exposure Logging is not possible
Your exposure logging could not be udpated for more than 24 hours.
Last exposure logging: Low Risk
Updated 17 Jun, xx:xx

Click on:

Activate Exposure Logging

Exposure Logging Active( *)
Exposure logging has been active for 4 days. An exposure check can only be reliable if exposure logging is permanently activated.

When I go back, I see the same.
Disabling battery saver did not help.
Reactivating GPS, Bluetooth, and settings in the app did not help.
Version 1.0.2
Releasd on 12 Jun 2020
Android 7.1.2 N2G47H
MIUI version  MIUI Global 11.0.2 | Stable <IP_ADDRESS>(NAMMIXM)
Xiaomi Redmi 4X

Have the same issue with Huawei Mate 20 Pro (installed since tuesday, info widget that risk calculation is inactive, please activate, but on second screen is still active (since 2 days)). Probably caused by the battery settings for the app. I have reinstalled the app and deactivated auto settings. I will report tomorrow

fixed by changing app battery settings (disable auto mode and leave the sub-settings unchanged = all active). But after that it takes up to 24 hours for the error to go away

fixed by changing app battery settings (disable auto mode and leave the sub-settings unchanged = all active). But after that it takes up to 24 hours for the error to go away

Yes, I can confirm this. Disable auto and keep the then shown settings does the trick. I use an Honor 8X with Android 10.
Just to mention it: It seems to me that Honor (and most likely Huawei, i.e. their EMUI) have these strict battery saving settings. Does anyone know if this feature of rigid battery saving options is EMUI specific? Reading the thread here one could get this impression.
BTW: I needed to do set manual battery settings also for Threema and Podcast Addict. Unfortunately I don't remember exactly, what kind of problem exactly I had with these apps. For Threema I can remeber, that I was not notified about newly received messages correctly/in time.

To whom it may concern. I have the same issue. Opened the app and the "Exposure Logging not possible" screen is displayed. When I click on "Activate Exposure Logging" I get send to the activation menu in which the exposure Logging toggle is activated.
Device: Xiaomi Mi 9T Pro

Gleiches Problem mit Samsung Galaxy M20, Android 10

Same issue on Xiaomi Redmi Note 7. None of the fixes with Autostart or Akku - App-Energiesparen work for me.

Huawei PSmart FIG - LX 1 Google Services enabled Auto start Change from Automatic to manual and back, restart made ,behat may be interesting that from from 17.6. to 19.6. it worked and showed low risk and now ( letzte Aktualisierung 18.6. 18:06) since I assume yesterday it went back to Risikoermittlung nicht möglich and none of the suggested changes in settings ( Autostart enabled manually and back to automatic / Google Services running) gets Risikoermittlung back to work. Wo kann man verlässliche Updates finden wie weit sap mit der Fehlerbehebung ist. In den Medien ist nirgends was verlässliches zu finden?  VG

having the same issue with an iPhone XR. The app showed me a "low risk" notification the first day. Since then it is showing "exposure logging is not possible". Tried app and phone restarting as well as revoking and granting exposure logging permissions

To whom it may concern. I have the same issue. Opened the app and the "Exposure Logging not possible" screen is displayed. When I click on "Activate Exposure Logging" I get send to the activation menu in which the exposure Logging toggle is activated. Setting it off then on does not solve the issue.
Device: Xiaomi Mi 9T Pro
No battery optimization setting enabled.
edit: what I now see is that I did not toggle on the "autostart" feature in Xiaomi miui which prevents apps to start during system startup and run in background. I will now switch the feature on and report back if the error persists.

My error has now gone and my state returned to the nominal state "Low Risk".I will continue monitor, if the error reappears.
My working assumption is that my xiaomis "autostart" feature closed the app on system start (restart) so that the Bluetooth connections weren't monitored. After I enabled "Autostart" and the app, the app required some more logging time to return to the default "Low Risk" state.
2nd possiblility: Maybe the error is connected with the recent update closing the application and interrupting the logging (together with disabled "autostart")

Same in Samsung Galaxy A3 (2017)

In the meantime, the team identified a workaround that solved the problem at least for some users: https://www.coronawarn.app/de/faq/#no_risk_update. Would be great if you can let us know whether it worked for you as well.
Of course, the team is nevertheless still working on a proper solution for the issue.

Unfortunatly, the generic workaround has not worked for me. After restarting my phone (Huawei P30) and opening the CWA the problem still persists.

Hey @tkowark
Thanks for your reply. I forgot to mention that I am running the app on a iOS device. Do you have a workaround or a fix for iPhones?
Regards

In the meantime, the team identified a workaround that solved the problem at least for some users: https://www.coronawarn.app/de/faq/#no_risk_update. Would be great if you can let us know whether it worked for you as well.
Of course, the team is nevertheless still working on a proper solution for the issue.

The workaround hasn't worked for me either
Xiaomi Mi 9/MIUI 11.0.9

Just to be sure. if you disable the battery saver mode after receiving the error. Make sure to wait a day until the logging has received enough data to trigger the low risk status. Disable batter saver modes doesn't instantly triggers the low risk status.
I guess most people know that. But just to be safe.

In the meantime, the team identified a workaround that solved the problem at least for some users: https://www.coronawarn.app/de/faq/#no_risk_update. Would be great if you can let us know whether it worked for you as well.
Of course, the team is nevertheless still working on a proper solution for the issue.

I still can not see the point, why setting this (weird) options should help solving the problem. As pointed out by @mh- in this thread of the cwa-documentation#236 three attemps within 1 minute are done to get the data from the server. If this fails (this can also be because the internet is not available), the next attempt will be done 24 hours later.
And as I also said before, my messaging (Signal, Telegram, WhatsApp, ...) and eMail (K-9 Mail, GMail, ...) apps are also able to retrieve the data on my phone without adjusting any energy options.
I do not want to offend anybody, I'm just trying to understand why this should help.

@alxy Just to be sure. if you disable the battery saver mode after receiving the error. Make sure to wait a day until the logging has received enough data to trigger the low risk status. Disableing batter saver mode doesn't instantly triggers the low risk status.
That confused me initially when I applied the error fix. But it makes sense given how the functionality works.
I guess most people know that. But just to be safe.

I indeed wasn't aware of this. I will see if the problem is gone tomorrow then and report if that is the case. For the FAQ I thnik it would make sense to clearly mention that it takes some time for the app to go back to green status again. As said, I expected it to work immediatly, as the last step in the FAQ workaround is to open the CWA.

@alxy Just to be sure. if you disable the battery saver mode after receiving the error. Make sure to wait a day until the logging has received enough data to trigger the low risk status. Disableing batter saver mode doesn't instantly triggers the low risk status.
That confused me initially when I applied the error fix. But it makes sense given how the functionality works.
I guess most people know that. But just to be safe.

I indeed wasn't aware of this. I will see if the problem is gone tomorrow then and report if that is the case. For the FAQ I thnik it would make sense to clearly mention that it takes some time for the app to go back to green status again. As said, I expected it to work immediatly, as the last step in the FAQ workaround is to open the CWA.
Edit: I just reopened the app and can confirm it is working now! So the workaround worked for me.

Ok great to here. I am obviously not 100% sure how all the functions work. So not 100% sure about the 24hrs . :) But what I think is definitely reasonable for people is to wait at least a while after applying the bug fix. If it didnt't work immediately after applying the bug fix, one can't assume the bug fix didn't work. :)

Auf dem Samsung A3 2017 funktioniert für mich folgendes:
Einstellungen => Apps => Corona-Warn => Akku => Akkuverbrauch optimieren => Alle Apps => Corona-Warn deaktivieren.
Nach dem Ändern dieser Einstellung wurde direkt wieder ein Risiko angezeigt. Davor ging es zwei Tage lang nicht.

The same Problem with Honor 8x.

Same problem here with Huawei Mate 10 Pro (device already mentioned). Also thought deactivating battery save functions for corona warn might help but this doesnt resolved the issue for me. Some days ago my phone was updatet to Android 10. I'm unsure if the update to EMUI 10 was installed right before i first had the issue described above.
Is the function of receiving and sending tokens affected by this issue?
Thanks

And as I also said before, my messaging (Signal, Telegram, WhatsApp, ...) and eMail (K-9 Mail, GMail, ...) apps are also able to retrieve the data on my phone without adjusting any energy options.

These apps are most likely using push notification services while CWA is not. The server is not pushing the list, the app is asking for it (at least that's how it was explained in UKW podcast).
Like others before me I'd like to ask the developers for more information about this issue:

Is only the retrieval of the positives list affected or also the logging?
Is it already sure that energy management is the (only) reason for this issue?
Was the topic of possible energy management issues discussed in development?
Is the fix you are working on only the in-app configuration of energy options or are there other things you are doing about this?

Similar problem on Samsung A3 2017 Android 9. No Risk-Update since 18.6.2020 7:48. Shows button to enable Risk-Assessment, but when clicked, shows the enable switch in on position.
Today i had the app open around update time, did not fix it.  Have no power saving enabled, excempted CWA from data-volume  or power limitations. I am almost always in a Wifi at update time.

I had the same problem on Samsung Galaxy S10+. However, found that an update was available in Google Play store (from 20 June, had apparently not updated automatically), and now the issue is gone and everything working again.

Related to https://www.coronawarn.app/en/faq/#no_risk_update
Afaik it is possible to show a dialog to the user to disable battery optimization: https://developer.android.com/reference/android/provider/Settings.html#ACTION_REQUEST_IGNORE_BATTERY_OPTIMIZATIONS
However, the setting does not "help" with vendor-specific battery optimizers.

Von: Robert Redl<EMAIL_ADDRESS>Gesendet: Sonntag, 21. Juni 2020 18:08
An: corona-warn-app/cwa-app-android
Cc: gbhajda; Comment
Betreff: Re: [corona-warn-app/cwa-app-android] Exposure logging is not possible / Exposure logging active (#637)
Auf dem Samsung A3 2017 funktioniert für mich folgendes:
Einstellungen => Apps => Corona-Warn => Akku => Akkuverbrauch optimieren => Alle Apps => Corona-Warn deaktivieren.
Nach dem Ändern dieser Einstellung wurde direkt wieder ein Risiko angezeigt. Davor ging es zwei Tage lang nicht.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/corona-warn-app/cwa-app-android/issues/637#issuecomment-647147439 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AQA3WLI53EGTQ3HUQNCSOELRXYV6DANCNFSM4OBP5J5A .  https://github.com/notifications/beacon/AQA3WLIBM3PUONIDHWWCNZTRXYV6DA5CNFSM4OBP5J5KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOE2JK7LY.gif

It exists an unresolved Android bug for this issue that is being ignored by Google for more than 1.5 Years now: https://issuetracker.google.com/issues/122098785
Please see also: https://dontkillmyapp.com/

Hi,
I'm facing the same issue. I'm using a Huawei P30 Pro. Please let me know if you need more details.
Kind regards
Jens

cschoenle wrote:

I had the same problem on Samsung Galaxy S10+. However, found that an update was available in Google Play store (from 20 June, had apparently not updated automatically), and now the issue is gone and everything working again.

Found this update today, didn't install automatically on my phone, but did the trick after installing it manually!
Thanks to cschoenle!
Thanks to all the other people, but the app was already exempted from Standby! That did not help in my case, but may be its needed... who knows...

Samsung Galaxy A3 (2017) with android 8: I tried all the workarounds with the battery standby mode and disabling the optimization, update to version 1.0.2, none of this worked. I now manually updated the app to the latest version 1.0.4 (the app did not update automtically), and now it's working again.

I now manually updated the app to the latest version 1.0.4 (the app did not update automatically), and now it's working again.

Probably because with 1.0.3+ the app is getting updates also on app start (https://github.com/corona-warn-app/cwa-app-android/pull/660). It's possible that the problem still exists, if the app is not opened manually. Does anyone know which downsides this approach has?

In the meantime, the team identified a workaround that solved the problem at least for some users: https://www.coronawarn.app/de/faq/#no_risk_update. Would be great if you can let us know whether it worked for you as well.
Of course, the team is nevertheless still working on a proper solution for the issue.

to Change the battery Settings didn't work for me. Today I had the Chance to update the app to the newest Version, it was not possible before, now the app works again

Same on Samsung Galaxy Note 9
Workaround not relevant for Note 9 Android 10, as settings have different names, tried to adapt the workflow as shown below, but this did not work either...bug remains
Öffne die Geräte-Einstellungen.
Wähle 'Apps' bzw. 'Apps & Benachrichtigungen'.
Wähle 'Corona-Warn'.
Wähle 'Akkuverbrauch optimieren'.
Wahle alle
Wähle 'Corona-Warn'. --> umstellen, dass optimieren NICHT mehr gewaehlt ist
Neustart

[Info:] „Risiko-Ermittlung nicht möglich“ und „Risiko-Ermittlung einschalten“ bei „Risiko-Ermittlung Aktiv“…
"Android one - Nokia 7.1", Android 10 mit Sicherheitspatch vom 01. Mai 2020, CWA 1.0.4.
 Nach Ausschalten der Option „Datensparer“ und erneutem Aufruf der CWA funktioniert die Risikoermittlung wieder; d.h. das ermittelte Risiko wird angezeigt.

[Info:] "Risk determination not possible" and "Activate risk determination" when "Risk determination active" ...
"Android one - Nokia 7.1", Android 10 with security patch from May 1st 2020, CWA 1.0.4.
Apparently the activated option "Data saver" („Datensparer“) prevents the correct risk determination. After switching off the "Data saver" („Datensparer“) option and opening the CWA again, the risk determination works again; i.e. the determined risk is displayed.

Fix for iPhone users (I am using iPhone XS Max)

Go to "Settings"
Go to "General"
Go to "Background App Refresh"
Turn "Background App Refresh" on
Find the Corona-Warn App in the list and enable Background App Refresh
Restart Corona-Warn App
It will work now

I confirm that svengabr's comment fixes the issue for iPhone users. I had this issue since day one when the app was released; it rendered the app useless for me and it wasn't fixed until now (I have the latest version of the app). The average user would not attempt to find a solution for this issue here on Github. This requires an immediate fix with a warning message that redirects to the correct settings menu (as detailed above), if background app refresh is disabled. Currently, the warning message redirects to the general app settings, where background app refresh is enabled, but greyed out, since the global background app refresh was turned off. This is misleading.

@FabianFalck agreed. I see quite a few users still experiencing this issue. It seems to get tracked here currently btw 🙂.

This issue has been fixed (Release 1.3) and will be closed now.


Incorrectly and non-idempotently modifies .. in macro

Start with this:
fn a() {
    a!(b {
        c: d,
        //
        ..
    });
}

Rust rustfmt, and you get this:
fn a() {
    a!(b {
        c: d,
        //
        ..
        ..
    });
}

Run it a third time, and you get this:
fn a() {
    a!(b {
        c: d,
        //
        ....
    });
}

And then we have a fixed point.
This can cause rustfmt to break certain macro-using code. The behavior still exists if you substitute a rather than a!, and I guess it's weird if it's not idempotent, but it's a bit of an edge case since that is not syntactically valid rust anyway. But you can write fully-compilable code that exhibits this behavior when formatted with rustfmt, if you're using certain macros like assert_matches!.

it seem like this bug is present only for non-doc comments, and it triggers with just struct construction: /// seems like doc comments don't trigger the bug   const B: b =  b {     c: d,     /* block comment, has bug */     // line comment, has bug     ..   };


Helm Repo documentation and/or hosting the chart

First, I'd like to say I'm ecstatic to see this project as I think this type of work will help bring Orthanc in view of many other enterprises.
One thing I think would help provide clarity to users that are used to running "helm repo add" commands would be to document the steps of cloning the repo and then setting changing the directory to it before running the "helm dependency update" command.
The other alternative that I think would be better would be to use GitHub Pages to create a public helm repo. Here  is an article I've used in the past to do this if there is interest.
If the documentation route is preferred, I'd be happy to submit a PR detailing those steps.

Hi @am-rpa  Thanks for the comment. For background, my original approach is to build my own Helm Chart to reference dependency resources such as postgres-ha as child chart.
As I decided to add Istio, I ran into a number of issues when trying to expand the original Helm chart, which led to a rethinking of the role of Helm in this project.
Going forward, two deployment approaches will be included:

Helm package (as-is, and to your point, the git clone step will be explicitly spelled out) for installation without Istio.
GitOps approach using FlexCD (currently a WIP) that installs istio as well.
Any further comments, expectations will be appreciated.

Documentation has been updated with detail on where to run the commands. closing issue.


1.4.3 still says NOR

Thanks for the release, however it seems that the NOR ~> OR didn't make it.
>>> cysystemd.__version__
'1.4.3'

>>> dir(cysystemd.reader.MatchOperation)
['AND', 'NOR', '__class__', '__doc__', '__members__', '__module__']

file = "cysystemd-1.4.3-cp37-cp37m-manylinux2014_x86_64.whl", hash = "sha256:5c246ecd2a262e18aa49146a52221c44941a87998962348b6446fc908fbd8f7f"

My mistake. I will fix it as soon as possible.

Should be fixed in already released 1.4.4.

@mosquito much better indeed. Thanks for the quick follow up!


Allow external contributions to add a property/function to all "Views"

Currently it is not possible to a new property to all widgets hat have a visual representation ("Views"). It is only possible to add properties a know widget directly. Therefore when creating a third party contribution it is not possible to add property to all "Views" while also supporting upcoming new "Views".

@mpost Is this a dup of #673?

yes. closing as dup since #673 sounds more understandable.


Export API / Periodic Export?

First of all, thank you for creating the cla-assistant. I've evaluated many of these tools and this is definitely the best available option in my experience.
I'm wondering if there is any way to periodically export the contributor CSV other than manually logging in through the web UI? It seems like exposing an API endpoint that I could fetch an export from would be the easiest path, but I wasn't able to find anything that like that from a quick look through the code.

Thank you for your positive feedback!
There is an API that gives you the list of signed CLAs (not in csv format, but as JSON). The only Problem is: you need a Session ID.
I'll rewrite the authentication part to provide the possibility to access APIs with username and github token.

Now you can use the POST API /api/cla/getAll to collect all signed CLAs for your repo. You have to provide following parameters in the request body:
repoId and gist.gist_url as json e.g.:
{
"repoId":"51002973",
"gist":{
		"gist_url": "https://gist.github.com/96ef0a16f11c8f11b41c"
	   }
}

For authentication you can use a valid github token. You can provide it either as a body-field token or as a header-field x-token.
Would this solution help you?

The API request makes sense, though I'm not sure how I would go about getting the GitHub token. I'm assuming that you specifically mean a token for the cla-assistant OAuth application? Could the cla-assistant web UI expose that somewhere?

You can use your "personal github token". If you go to settings in your github profile you can generate a github token under "Developer settings -> Personal access token". We use it only for identification towards GitHub.

I didn't even realize you could choose the scopes when you created a personal access token and I used to work at GitHub. Derp! Yes, this will work great. Thanks so much!

Actually, one more question @KharitonOff -- can I use orgId instead of repoId?

Nevermind, tested it for myself and it works great. I really appreciate it!


Build wheels with pre-compiled CUDA kernels

Resolves: https://github.com/turboderp/exllamav2/issues/56

This makes JIT compiling optional and can be opted into by setting the EXLLAMA_NOCOMPILE environment variable on install.
This also includes 4 workflows:

build-wheels.yml

This workflow will build wheels and sdist and upload them as workflow artifacts.
Useful for testing as you don't need to worry about overwriting working wheels with broken ones.
Calls build-wheels-rocm.yml to build ROCm wheels at the end.

build-wheels-release.yml

This workflow will do the same as the first and will also upload them to GitHub releases that it will create if needed.
Parses setup.py to determine package version that it will then use as the release tag to upload to.
Currently configured to overwrite wheels already uploaded in a release.
Also uploads to PyPI. Current code for this is based on the info here:
https://packaging.python.org/en/latest/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows/
This may need to be adjusted as I have no experience working with PyPI and typically just make my own package indices.
Regardless, an option is provided when running the workflow to not upload to PyPI.
Calls build-wheels-release-rocm.yml to build ROCm wheels just before building the sdist and JIT compile wheel.

build-wheels-rocm.yml

This workflow will build wheels using ROCm 5.6. This version can be changed by editing the variable in the SDK installation step.

build-wheels-release-rocm.yml

The same as the previous but also includes the upload functionality of build-wheels-release.yml.

I'm not sure how to go about uploading the pre-compiled wheels to PyPI without requiring that users specify the exact version to install: pip install exllamav2==0.0.3+cu118
pip will view any version tags like that as being a newer version and will consequently prefer to install that wheel unless explicitly told what wheel version to install.
With these wheels available in the same place:

exllamav2-0.0.3-py3-none-any.whl
exllamav2-0.0.3+cu117-cp310-cp310-win_amd64.whl
exllamav2-0.0.3+cu118-cp310-cp310-win_amd64.whl

This will install the JIT compile version: pip install exllamav2===0.0.3
This will install the pre-compiled CUDA 11.7 version: pip install exllamav2==0.0.3+cu117
All of these will install the pre-compiled CUDA 11.8 version:

pip install exllamav2==0.0.3+cu118
pip install exllamav2==0.0.3
pip install exllamav2

Currently still testing building ROCm wheels and can I add them to this PR when done.

I've done a bit of research, by which I mean I asked ChatGPT, and it seems convinced that pip simply ignores local version identifiers by default. So unless explicitly stated, "0.0.3", "0.0.3+cu117" and "0.0.3+cu118" would all match "==0.0.3", and pip will install whatever version has a more recent timestamp.
If it's not hallucinating, a fix could be to simply make sure the "0.0.3" is always uploaded last. If that's doable.

Should be possible. Also, having some issues getting exllamav2 to build with ROCm 5.4.2. Is there a minimum ROCm version that this is compatible with?

Local testing shows that the file time doesn't change what pip selects, but this may only apply to --find-links.

That sounds great, yeah.

Added ROCm workflows that the main 2 workflows will execute. They can also be used on their own if needed.
If they cause issues with the build process in the future, then you may want to remove the workflow call from the main workflow.

I'll try it out.

The build actions seem to work great. Thank you for the contribution.
Sadder news is that it looks like an uphill battle with PyPI. For one thing, linux_x86_64 is an unsupported platform tag. According to auditwheel the "manylinux_2_27_x86_64" tag would work instead, so maybe it could resolved that way. But  the local version identifiers aren't supported either.

That's unfortunate. The manylinux tag could be done without too much issue, but the lack of local version identifier support greatly complicates things.

Yeah, it's a shame. It looks like it was supported at some point but not anymore? Idk, pip versioning is a whole thing apparently.
I guess the next best thing would be dividing the wheels up into separate directories. One for cu117, one for cu118 and so on. Like Torch does (https://download.pytorch.org/whl/cu118 etc.) I'll experiment later to see if github can accommodate something like that for releases. Not sure how much of a hack this is, but it looks interesting.
At any rate, at least the PyPI package that I can upload will now build and install exllamav2-ext by default, which seems to be preferred, and there are prebuilt wheels in the releases. Which is still progress.

A GitHub-hosted package index is exactly what I do in this repo and several others:
https://github.com/jllllll/llama-cpp-python-cuBLAS-wheels
https://jllllll.github.io/llama-cpp-python-cuBLAS-wheels
It is needed in that repo in particular due to the distribution of literally thousands of wheels.

I'm not sure how to go about uploading the pre-compiled wheels to PyPI without requiring that users specify the exact version to install: pip install exllamav2==0.0.3+cu118
pip will view any version tags like that as being a newer version and will consequently prefer to install that wheel unless explicitly told what wheel version to install.
With these wheels available in the same place:

exllamav2-0.0.3-py3-none-any.whl
exllamav2-0.0.3+cu117-cp310-cp310-win_amd64.whl
exllamav2-0.0.3+cu118-cp310-cp310-win_amd64.whl

This will install the JIT compile version: pip install exllamav2===0.0.3 This will install the pre-compiled CUDA 11.7 version: pip install exllamav2==0.0.3+cu117
All of these will install the pre-compiled CUDA 11.8 version:

pip install exllamav2==0.0.3+cu118
pip install exllamav2==0.0.3
pip install exllamav2

is there any pre-compiled version for linux_x86_64 ?

Some additional info when i compile exllama v2
these are the env i can successfully run
Driver Version: 530.41.03    CUDA Version: 12.1
Driver Version: 535.54.03    CUDA Version: 12.2
these are the env i fail to run
Driver Version: 510.47.03    CUDA Version: 11.6 ([CUDA initialization: Unexpected error from cudaGetDeviceCount())
Driver Version: 510.47.03    CUDA Version: 12.1 (identifier "__hmul" is undefined]

is there any pre-compiled version for linux_x86_64 ?

Yes. The prebuilt wheels are currently available here: https://github.com/turboderp/exllamav2/releases/


CORE-8041: Use ConcurrentHashMap in the VirtualNodeInfoProcessor

If the VirtualNodeInfoProcessor is closed at the same time as it gets an update, a ConcurrentModificationException could occur as an iteration over a synchronizedMap occurs at the same time as trying to clear it. The map has been changed to a ConcurrentHashMap, which should guard against this exception in this case.

LGTM. Related. I was going to ask you if you know the reason we have this callback functionality for CpiInfo and VnodeInfo. This doesn't seem to be used anywhere (except the tests). I don't know what the history is, but it may just have been put in "just in case", in which case I call YAGNI and propose to remove it (in a separate PR).

Not sure why it's there to be honest - let's kill it off.


was working recently, updated to the latest version and just timesouts client = creator.start()

was working recently, updated to the latest version and just timesouts client = creator.start()

Send all logs and error

the first time it works, after its linked, if I run it I get that

Error say that qrcode not load
May be

you use Firefox without headless mode, Firefox take long time to do action and need tab to be focus
You can use chromium or other than Firefox
try start with async no time out

I use chromium . it doesn't work after the first run.

What version you used

thanks updating that worked


Different movement types

Walking
Flying
Swimming

Requires #33

Flying might not be performant with an A* algorithm (3d space)


if service suspends due to high load or too many jobs add log entry

fixed in https://github.com/magemojo/m2-ce-cron/commit/bd433ae292f25abccb63bae1fb21c94cdbbf2f75


Login and Signup page UI improvement

Is your feature request related to a problem? Please describe.
No
Describe the solution you'd like.
The login and Signup pages do not match the other page's UI. Can be improved.
3D illustrations can be used in place of 2D. The box effect that other pages follow can be implemented here. And the background effect can be added.
Describe alternatives you've considered.
No response
Additional context.
No response
Show us the magic with screenshots
No response
Checklist

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[X] I want to work on this issue. (optional)

@Yash636261 can u plz assign me this under gssoc'24.

assigning to you @Annu117, you can start working on it.


feature gate: add activate with authority instruction

This PR adds the ActivateFeatureWithAuthority instruction to the Feature Gate program.
This instruction is the activation process that will support multi-sig authorities for activations, as discussed in this comment on #5510.

Current dependencies on/for this PR:

master

PR #5510

PR #5541

PR #5566   👈

This comment was auto-generated by Graphite.

I was envisioning this as additional logic in the existing ActivateFeature instruction, based on whether an optional activation authority was passed into the processor (account slice len 3 vs 2). Is there a reason that's a bad idea?

I was envisioning this as additional logic in the existing ActivateFeature instruction, based on whether an optional activation authority was passed into the processor (account slice len 3 vs 2). Is there a reason that's a bad idea?

No I think that would be ok, but we will now have feature, payer, authority as per this comment.
I'll add a commit for it and we can check it out.

Closing for now, since whenever SIMD talks conclude, we'll want to upgrade the program one feature at a time, starting with the existing RevokePendingActivation instruction.


Upgrade alpha CNI dependency

github.com/containernetworking/cni v0.7.0-alpha1

is current version used. We should probably be on a stable version. I tried to upgrade but got all sorts of failures
cc @stewartbutler @bcheung

I can take a look

I should mention this is pretty low priority, just something I noticed. Ideally we aren't depending on alpha versions

I upgraded github.com/containernetworking/cni to v0.7.0 and fixed an error due to this change. All tests pass, but I checked the releases and noticed that all versions following v0.7.0-alpha1 use CNI spec v4.0.0 which replaces the GET command with CHECK: https://github.com/containernetworking/cni/pull/579
It seems like Istio CNI still uses CNI spec v0.3.1 but the GET command isn't implemented at all: https://github.com/istio/istio/blob/d110604aabdd4204829005634652928c92aabc3b/cni/cmd/istio-cni/main.go#L262-L266
Would this be a safe upgrade?
Also, upgrading to github.com/containernetworking/cni v0.7.1 may also require upgrading github.com/containernetworking/plugins v0.7.3 (which is the current version) to v0.8.0 or later to support CNI spec v4.0.0.

Oh, very interesting -- the mechanics of CHECK may remove the need for the cni validation init container. We'll need to experiment with this a bit. If we implement a CHECK call that properly checks the pod internal iptables and terminates the pod if unhealthy, that may remove the need for the repair container (See https://github.com/containernetworking/cni/blob/spec-v0.4.0/SPEC.md). It may even fix the race condition entirely, depending on how k8s reacts to chained CNI plugins. I'd need more time to investigate than I can devote now, but it just moved way up in priority for me.
@howardjohn The change to CNI spec v4.0.0 is going to be a big enough change that I think it may require a decent chunk of rewriting of CNI. Would you object to us deferring this until 1.8 (or 1.9 depending on time budget)? We definitely need to adopt this and do some experimentation, but I don't want to distract from the other efforts to move CNI to beta in 1.7.
@bcheung As stated, I'd prefer to defer this. It looks like the side effects of the upgrade may be a lot more complicated than they seem at first glance. Good catch on calling it out.

@stewartbutler no concerns here, I merely saw we were using an alpha version which "feels" wrong - but not actually causing issues. I didn't realize the extent of the changes.

@stewartbutler the CHECK calls seems optional and called at any time during the lifecycle. Did you see anywhere that guarantees the

CHECK will be called regularly
CHECK will evict a failing pod

Its sort of implied but I didn't see anything explicit?

not stale
On Tue, Dec 29, 2020, 9:04 PM Istio Policy Bot<EMAIL_ADDRESS>wrote:

🧭 This issue or pull request has been automatically marked as stale
because it has not had activity from an Istio team member since 2020-09-28.
It will be closed on 2021-01-11 unless an Istio team member takes action.
Please see this wiki page
https://github.com/istio/istio/wiki/Issue-and-Pull-Request-Lifecycle-Manager
for more information. Thank you for your contributions.
Created by the issue and PR lifecycle manager.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/25847#issuecomment-752328661, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXPFLZVXXS7TAN7QFULSXKYEBANCNFSM4PG7AIPQ
.

not stale
On Mon, Mar 29, 2021, 10:11 PM Istio Policy Bot @.***>
wrote:

🧭 This issue or pull request has been automatically marked as stale
because it has not had activity from an Istio team member since 2020-12-30.
It will be closed on 2021-04-14 unless an Istio team member takes action.
Please see this wiki page
https://github.com/istio/istio/wiki/Issue-and-Pull-Request-Lifecycle-Manager
for more information. Thank you for your contributions.
Created by the issue and PR lifecycle manager.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/25847#issuecomment-809913862, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXIFCAWNCGDEIJITFRLTGFMPDANCNFSM4PG7AIPQ
.

not stale
On Sun, Jun 27, 2021 at 11:02 PM Istio Policy Bot @.***>
wrote:

🧭 This issue or pull request has been automatically marked as stale
because it has not had activity from an Istio team member since 2021-03-30.
It will be closed on 2021-07-13 unless an Istio team member takes action.
Please see this wiki page
https://github.com/istio/istio/wiki/Issue-and-Pull-Request-Lifecycle-Manager
for more information. Thank you for your contributions.
Created by the issue and PR lifecycle manager.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/25847#issuecomment-869381660, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXJPYYWDGAT4NWUVLWLTVAGA5ANCNFSM4PG7AIPQ
.

Check is called immediately after add, so it is not going to help with the race.


Test SR HIV results locally

Problem Statement
Before sending test messages to CA in staging and making any transforms, we want to test messages locally to ensure they are getting through the UP as we'd expect.
What you need to know

1/17, Victor to communicate back to SR on how to accept gender of sexual partner in the test result
Then SR will need to make the necessary changes on their end (still waiting on SR as of 2/9, check with LaFreda for update)
SR has confirmed that they will populate the fields, but need to send a test message

Acceptance Criteria

[ ] HIV test message is submitted from SR and is processed through the UP "losslessly"

Victor will send me the questions we have for LA county and I will email them.

Email sent on 1/26/24:
Good morning Mike and Rebecca,
Happy Friday! I am a project manager on CDC's Reportstream project. I have a couple of questions for you as we work on sending you HIV results with our sister product, SimpleReport. Please provide answers to the questions below:
SimpleReport is going to start sending patient's gender identity for HIV results. Is there a specific field in HL7 where LAC expects this field to be mapped under? By looking at the HL7 v2 for PID, there doesn't seem to be a field to map this to.
SR is also planning to start sending the sexual partner's gender identity. We are planning to send this data as an NTE segment. Does that work for LAC?
If we need to hop on a call to discuss this, please let me know; I am happy to schedule a meeting.

Message to Merethe:
Hi @Merethe Hansen! As we plan for our upcoming Sprint, I want to make sure we include any HIV work if needed. Do you have a general timeline of when we can expect the new test message with all of the populated fields? Thanks!!

Response from Merethe:
We’re planning on pulling the tickets to update the HIV fhir message into the coming sprint (starting Wednesday). I would anticipate we can send test messages by the end of that sprint

Per Slack, HIV message from SR may not be ready until the end of next week

Update from Jayna:

Finished per Victor


gradlew/gradlew.bat should not be gitignored according to official doc

Close https://github.com/flutter/flutter/issues/109749
Pre-launch Checklist

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

If you need help, consider asking for advice on the #hackers-new channel on Discord.

This is the repo's gitignore, not a template file gitignore.

I know. The problem is, maybe flutter repo itself also need to follow gradle's official suggestion?

We've done this historically because the tool can handle re-generating this and to avoid churn in the repo when the contents of this file changes.

I'm going to close this PR, as we don't intend to accept this change. If something changes we can always reconsider

I see. Thanks all the same


Update LAB_02L05_Create_and_manage_session_host_images_ADDS.md

Module: 00
Lab/Demo: 00
Fixes # .
Changes proposed in this pull request:

Submitted by ParamRamki on behalf of MOC Labs Review

updated separately (conflicts)


Remove empty-attestation-name test

After https://github.com/slsa-framework/slsa-github-generator/pull/777, an empty attestation-name indicates that the default behavior should be used.
Signed-off-by: Ian Lewis<EMAIL_ADDRESS>

@laurentsimon FYI


Default directory

In case, no path provided for the link storage, $HOME/.ark-shelf must be used.

Spoken about using the platform defaults instead elsewhere but otherwise this is a quick change from the current folder layout:

I'd also say drop the .ark as a hidden folder or perhaps even altogether as it doesn't really serve much purpose

@mberry .ark subfolder is essential at the moment since it allows us to sync user metadata to other devices.. Technically, user might have different folders with different links, each one should contain .ark subfolder. These folders are used as indicators of user folders on mobile, during filesystem scanning. We might get rid of the hidden subfolder when we implement syncing library. So far we just utilize Syncthing as imitation of it, it works with files only, so we create .ark folder right next to the data itself because user can choose syncing only that folder.
Sorry, I haven't mentioned this before. The issue is about location of the folder for storing links itself.

$HOME/.ark-shelf

This folder was suggested for the case when user doesn't really care about syncing etc. If nothing is specified, we need to use some default location. But we must allow user override this choice. The problem is that in main links are stored in the working dir of the calling process.


Support both Carbon and CarbonImmutable

When settings the Carbon class used globally throughout Laravel to CarbonImmutable (Date::use(CarbonImmutable::class)), the command fails:
Indeev\LaravelScheduleCalendar\Console\Commands\ScheduleCalendarCommand::printHourLine(): Argument #1 ($startHour) must be of type Carbon\Carbon, Carbon\CarbonImmutable given, called in [...]/Laravel-Schedule-Calendar/src/Console/Commands/ScheduleCalendarCommand.php on line 293
This is because $this->option('date') will return the date as an instance of CarbonImmutable, while the mapTasks() and printHourLine() functions expects an instance of Carbon.
This PR changes the Carbon type hints to use CarbonInterface instead, supporting both Carbon and CarbonImmutable.

Nice job, thank you!


Question / Clarification on license configuration

Hello,
I'm new to setting up arcGIS via Chef and have only some experience with chef.  I'm trying to understand how to put the license file and SSL files in place.  In other cookbooks I've worked with, I put files onto the servers with cookbook_file or template_file but I'm not seeing either option in the cookbooks.  I've been trying to find where to store the license and SSL files so everything is licensed appropriately.
I've also been following the guide at:
https://github.com/Esri/arcgis-cookbook/wiki/Automate-a-multi-machine-ArcGIS-Enterprise-deployment-on-Linux-using-Chef-Server
Unfortunately, the link for  arcgis-enterprise-linux-roles.zip does not exist and I'm not able to locate them anywhere.  It seems like it may be part of webgis-ubuntu.json role but I wanted to confirm.
To recap:

Where do I store the license file in Chef to ensure appropriately licensed products.
Where do I put the SSL files in Chef to ensure a properly secure site.
Where are the roles for the demo environment (arcgis-enterprise-linux-roles.zip) or is there an updated wiki page for the installation.

If I recall correctly, all you need to do is put the files into a location that is accessible to Chef and with proper permissions so that Chef can read them and then the recipes will deal with putting them where they belong in the installation folders as it progresses with the installation.
I have not done a Linux install of an ArcGIS Enterprise setup but I don't know why it would be any different in regards to the your provisioning and SSL files.
It does occur to me though, that you might need to install your SSL cert as you normally would for any server prior to running the cookbook.  Similarly, you need to manually open any ports in your firewalls prior to cooking things up.
I would suggest that you look at the provided Json examples and try to emulate the file structure you see in there as much as you can.  The reason for this is that as upgrades come out, the less you have to tweak the Json files, the quicker and easier it is to get upgrades up and running.  Ditto really for the initial install also.  Obviously, it's pretty easy to use a good text editor and make all the changes you need regarding folder/file paths.  But I have found over time, that the more I can emulate  the setups as published by Pavel, the easier my life is in terms of running Chef and especially down the road as upgrades of both the cookbooks and the Esri AGS Enterprise packages.
Hope this made sense and helps.
I would have to dig into some installations and wade through the cobwebs to find details about the SLL certs and their installation.  But of course it can't hurt to have already installed them on the server anyway.
BTW - I just found this note from Pavel from 2015 regarding certificates:
Things might have changed since 2015 and if so I imagine you'll hear tomorrow.

The arcgis cookbook works with SSL certificates like this:
1.If HTTPS is already configured in IIS - it does not touch it.
2.If SSL certificate file (.pfx) and password are provided in the json attributes - it uses the certificate to configure HTTPS.
3.Otherwise, it generates a self-signed SSL certificate and configures HTTPS in IIS using that certificate (WARNING the certificate expires next day).
I will say this, do everything you can do to avoid using self-signed certs. I recall being anxious to get going and doing an initial install with the self signed until our domain cert came in.  That was a mistake.  I've found that the self-signed certs give me nothing but trouble over time.  It's like they weasel their way into places they don't really belong and then can be difficult to find them all and get rid of them, or rather replace them with the proper certs.  FWIW - we use a domain cert here rather than individual certs per server.  (*.ourdomain.org)  This allows me to use one cert file for all the servers in the setup.  I  believe some argue that this is not the most secure (probably not) but given our setup, it's probably plenty adequate and sure makes administration of the certs easier.
In thinking this over, I do believe I typically have applied the cert to IIS prior to cooking things up but not always.  I have taken advantage of item #2 above to let Chef configure the web adapters and IIS for me.  But it also occurs to me that there have been times when I have had to tweak the setup after the fact to get things just right.
My experience is that the cleaner the setup I can start with, the closer to scratch that I can have the server setup before running Chef, the more consistent and successful the install will be.  Typically I  will clone the VM and if I have to tweak things as I install, depending on the tweak, I'll often go back to the clean VM or modified VM and repeat the install from scratch until I get it to run start to finish without any hiccups.  This gives me a rather pure server provisioned as expected by chef without any hacks of my own to get past a hiccup.  My experience is that doing this makes my life to support and upgrade the server down the road a lot easier.  And makes my servers and server environments much more consistent and hence easier to support and work on.
Best of luck.

Hello,
Have you found out where the roles.zip for demo environment is located?  I am following the wiki for the Windows version, and stuck at the same place. I can't find "arcgis-enterprise-windows-roles.zip" and thus don't have access to "environments\demo.json".
Thanks for your help!
Yeon

Where are the roles for the demo environment (arcgis-enterprise-linux-roles.zip) or is there an updated wiki page for the installation.

@yeonkim
The "arcgis-enterprise-windows-roles.zip" can be found here.
Looks like the equivalent Linux files were not uploaded as they should also belong in the same place.

Thank you so much @cameronkroeker!!


Set local git user name and email after initializing exercise repo

Set local git user name and email after initializing exercise repo (to distinguish commits).

I think we should use a value for user.email that looks more like a valid email address for pedagogical reasons. maybe something like<EMAIL_ADDRESS>?

I can use this .

Also, I am pretty sure that we need a clean-up step as well that does a git config --local --unset user.... to remove the value again so future commits are made with the users own identity.
As far as I can work out, this will require that every single kata is then modified with a call to the clean-up function - but once that is done, we can easily add more setup/clean code if we find later needs.

I feel, unless missing any other point, it's not necessary. These two statements are executed as part of the 'exercise' repo that's created using makerepo() in respective katas' setup scripts.
Configured values are stored under 'exercise/.git/config', so this is fail-proof in 2 scenarios -

if one wants to redo the same exercise, executing setup script ensures it first deletes the 'exercise' folder before initing a new one, and
since those were local configs, it won't affect values at any other level.

Clearly, it needs an efficient plan on how cleanup or tearing down part should be handled. Or implement this in setup scripts of every kata.

I am thoroughly confused by the GH user interface this morning, and can't find my original review comments on this issue.
I am happy with the email change, but as far as I can tell, we haven't yet addressed the cleanup issue. If we don't unset the "bot user", then all the following commits made by the "student" will also be made with that identity, and that sort of defeats the whole purpose of separating the two.
@schiluveri If this is too big a change, please let me know, and I will make a stab at it myself (at least in the Bash version).

By the titel of this PR, cleanup is not included, but then we need a second PR to fulfill #195 and in my opinion, one doesn't make sense without the other.

I think this is broken without the clean up. It is also a potentially breaking change :)
I will go through the exercises and perhaps add the cleanup to this. I should be able to find some time for this this week.

I am thoroughly confused by the GH user interface this morning, and can't find my original review comments on this issue.

Perhaps, you might want to go back to your comments on the issue itself. We're discussing this on PR review page :)

I am happy with the email change, but as far as I can tell, we haven't yet addressed the cleanup issue. If we don't unset the "bot user", then all the following commits made by the "student" will also be made with that identity, and that sort of defeats the whole purpose of separating the two.
@schiluveri If this is too big a change, please let me know, and I will make a stab at it myself (at least in the Bash version).

Yes, clean-up part can be added; I'm on that now. Agreed with @sofusalbertsen now that, initially, configuring local trainer username and then clean-up can be added to few katas from here https://github.com/praqma-training/git-katas/blob/master/Overview.md
For extensibility and easier maintenance, I use your suggested methods for this:
setup()
-- a separate function to in utils to configure local user name and email
and teardown()
-- to unset the values.

I have approved, but I would still prefer a 👍 from either @RandomSort or @sofusalbertsen before merging.


Use a size Vector for adjusting the size of Rectangles and Boxes

Currently, to adjust the size of a RectangleShape2D or a BoxShape3D you modify the extents, which are half the size of the rectangle or box. This is confusing for the user. Furthermore, although a BoxMesh3D (a CubeMesh in 3.2) uses a Vector3 for size, a CSGBox3D uses three floats: width, height and depth.
This PR allows a users to adjust the size of a RectangleShape, a BoxShape, a BoxMesh and a CSGBox consistently using a Vector property called size.
Part of #16863.

It still says "Extents" in the corner when dragging the handles, I think this is not intentional:

For CSG, it says the name of which handle you are manipulating, but then the value is the size vector:

Updated to correctly display "Size" and the Vector3 in the corners.

This code looks good, and I agree that having a size property makes sense. It's 100% an improvement for CSG.
However, there is an argument for having both size and extents properties. There are a lot of places in this code where size / 2 is used. More importantly, while a Rect2 and AABB have their position defined as the negative corner (top-left for Rect2, bottom-north-west for AABB), the position for BoxShape3D, RectangleShape2D, and CSG nodes is defined as the center, not the corner. To find the edges/corners of a Rect2 or AABB, you can take the position for one edge/corner, and the position plus size for the others. To do the same with BoxShape3D, RectangleShape2D, and CSG nodes, you would need to take the position and add/subtract the extents (half the size). So BoxShape3D currently behaves like Unity's Bounds.
Anyway, I would like @akien-mga's feedback on this (and anyone else who wants to chime in).

Thanks!


Use constants for plum_convert_color switch cases

The other functions in this file use the PLUM_COLOR_* constants, I really think this should too.

You beat me to this change. I'm closing the pull simply because I'm making a very similar change on my side.


fix-issue-enum-paging

Description
Fix an issue about the __str__ function of the DatabaseOrder class with made it incompatible with python3.11
Self Check:
Strike through any lines that are not applicable (~~line~~) then check the box

[ ] Attached issue to pull request
[x] Changelog entry
[ ] Type annotations are present
[x] Code is clear and sufficiently documented
[x] No (preventable) type errors (check using make mypy or make mypy-diff)
[x] Sufficient test cases (reproduces the bug/tests the requested feature)
[x] Correct, in line with design
[ ] End user documentation is included or an issue is created for end-user documentation (add ref to issue here: )

Processing this pull request

Failed to merge changes into iso4 due to merge conflict. Please open a pull request for these branches separately by cherry-picking the commit that was made on the branch master (git cherry-pick 58b755d3df3103f27571834a9e234d91aac08666).

Merged into branches master in 58b755d3df3103f27571834a9e234d91aac08666

Not closing this pull request due to previously commented issues for some of the destination branches. Please open a separate pull request for those branches by cherry-picking the relevant commit. You can safely close this pull request and delete the source branch.

This branch was not deleted as it seems to still be in use.

Processing #5173.


continuous benchmarking

We need to keep track of optd's performance.
Tasks

[ ] https://github.com/cmu-db/optd/pull/262
[ ] CI + pages setup via https://github.com/benchmark-action/github-action-benchmark

@yliang412 if you are looking to use Criterion + github-action-benchmark, you will need to run in compat mode: https://github.com/benchmark-action/github-action-benchmark/issues/8
Depending on your use case this may not be desirable.
I'm more than happy to help answer any questions to get you all set up with Bencher, which has full Criterion support.


KeyError: Item DOI

Hi all,
when i tried to upload and merge csv file using litstudy, I got this error Item DOI, however, the csv file I downloaded it from Scopus

Can you provide a snippet of your code, the error message, and the input file?

scopus.csv
FMEA IEEE.csv
Hi @isazi thanks for your reply, I have attached the two file data one from IEEE and the other from Scopus, However, I have fixed the error of (Item DOI) by changing load_springer_csv to load_csv. in the meanwhile another error was raised and I have attached a snap of the error, the error is regarding plot_affiliation_histogram and plot_author_histogram, I have tried to use the power of Bard AI and GPT to help me to fix the error but it still, i cant fix it, it will be very grateful if you could help me in that

One of the entries in the IEEE file, i.e. the paper titled "Statistical Model for a Failure Mode and Effects Analysis and its Application to Computer Fault-Tracing", uses semicolons as separators for the different fields on the affiliation, and that is wrongly parsed. As a workaround, you could try to manually modify that entry to remove the unnecessary semicolons.

Indeed, as @isazi said, there is an error in this CSV file for the affiliations for one row. You can remove this row from the CSV file.
We have also updated litstudy to better handle such corner cases. You can update to the latest version of litstudy using the following command:
pip install git+https://github.com/NLeSC/litstudy

This has been fixed in the latest release (1.0.6)


InstallCDT no longer is accurate

It says "For InstallCDT to work properly, /Library/Application Support/Developer/XCode/Shared/Specifications must be writable, and we detect that it isn't."
/Library/Application Support/Developer/ doesn't even exist!
OS: macOS Sierra 10.12 (Beta 4, but there's not much difference)

Xcode version is 8.2.1 (8C1002)

just for an extra note: the projects included in this repo do open, without errors, in this version of XCode.


Implementation in Python

Is there Python version of this work?

For now, we don't have a Python version of STARE.


Slight confusion with version requirements

Hello All,
Please help and clarify this requirement.
Most of us have probably come to this helm chart via:
https://rancher.com/docs/rancher/v2.5/en/monitoring-alerting/windows-clusters/#cluster-requirements
And the need to upgrade to a wins version >= v0.1.0.
The helm Readme requirements state:
"A Windows Service called rancher-wins is currently running on each Windows host that is running a wins server version of v0.1.0+."
I have a wins version of 0.0.4 running on my nodes.. so please confirm if it's possible for me to use this Helm chart or not.
Thank you

@aiyengar2

@edward-bear it is possible to use the Helm chart in your situation.
The wins-upgrader Helm chart cannot be used to upgrade to older versions of wins (e.g. upgrade 0.0.3 to 0.0.4) since the newer version of wins you are planning to upgrade to should be v1.0.0+ (as it must support ./wins upgrade to perform the upgrade).
However, upgrading from an older version of wins like 0.0.4 to wins 1.0.0+ should be supported since we only rely on the existing wins server having the capability to run the upgrade command on the provided wins binary.
The reason why this isn’t explicitly called out in the README is because upgrading from 0.4.0 to 1.0.0+ is a special exception, as in most situations you will have to turn on masquerading to get wins deployed (which is a special process, as noted in the README).
However, I’d be open to updating the README to clarify this requirement.
cc: @phillipsj


Auto-generate documentation on Python classes and interface.

Migrated from GitLab: https://gitlab.com/meltano/sdk/-/issues/15
Originally created by @aaronsteers on 2021-01-05 23:49:49

Spun off from this discussion.

View 2 previous comments from the original issue on GitLab


python3Packages.pyairvisual: 5.0.8 -> 5.0.9

Motivation for this change
Update to latest upstream release 5.0.9
Change log: https://github.com/bachya/pyairvisual/releases/tag/5.0.9
Things done

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

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

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Relase notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 131882 at 6a91cf75 run on aarch64-linux 1

3 packages failed to build:

home-assistant
python38Packages.pyairvisual
python39Packages.pyairvisual

Note that build failures may predate this PR, and could be nondeterministic or hardware dependent.
Please exercise your independent judgement. Does something look off? Please file an issue or reach out on IRC.

I can't test this with home-assistant because python-magic is currently fails with
======================================================================
FAIL: test_descriptions (__main__.MagicTest)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/build/source/test/test.py", line 108, in test_descriptions
    self.assert_values(m, {
  File "/build/source/test/test.py", line 53, in assert_values
    self.assertIn(value, expected_value)
AssertionError: 'PDF document, version 1.2, 2 pages' not found in ('PDF document, version 1.2',)

----------------------------------------------------------------------
Ran 16 tests in 0.029s

@mweinelt

Starting with a update for python-magic in #132000...

Result of nixpkgs-review pr 131882 run on x86_64-linux 1

1 package failed to build:

home-assistant

2 packages built:

python38Packages.pyairvisual
python39Packages.pyairvisual


Support rotating the layouts

Brought up by @kwcantrell in https://github.com/kwcantrell/empress/pull/49#issuecomment-674294457 and https://github.com/kwcantrell/empress/pull/49#issuecomment-674299580.
This would be really nice for the rectangular layout (since it'd let users draw the tree going from top to bottom, which is a common way of representing them) and for the circular layout (if the user wants the "start point" of the circle to be at an angle other than 0 radians).
This might break the "maximum displacement" computations for rectangular barplots a bit, but fixing it probably won't be too bad. (It might be easier to just support increments of 90 degrees for the rectangular layouts; not sure right now.)

Actually, we would not need to modify anything. The rotation will be done in the shades so as far as empress is concerned, the tree will not actually change.

Oh wow. That makes life even easier! So this would automatically rotate the barplots buffer, as well?

Yupe, it will rotate everything! On top of that, it is a "free operation" in the sense that no extra computation resources are needed. WebGl will be doing the same amount of work whether or not the tree is rotated.