text:
nvm use won't match major version number only to installed version

Issue:

With the Linux version of nvm, one can do:
$ nvm install 15
. . .
Now using node v15.14.0 (npm v7.7.6)
$ nvm install 16
. . .
Now using node v16.15.0 (npm v8.5.5)
$ nvm use 15
Now using node v15.14.0 (npm v7.7.6)

On Windows, when you install a version it is not automatically selected.  And when you use a version, it can't be referenced by just the major version number.
> nvm use 16.5.0
Now using node v16.15.0 (64-bit)
> nvm install 15
. . .
Installation complete. If you want to use this version, type

nvm use 15.14.0
> nvm current
v16.15.0
> nvm use 15
node vv15.14.0 (64-bit) is not installed or cannot be found.

However, specifying the full version number works as expected, following the install:
> nvm use 15.14.0
Now using node v15.14.0 (64-bit)

How To Reproduce:
Run the above commands in PowerShell.
Expected Behavior:

It would be nice if nvm switched to the version being installed.  That's usually what people want to do when they install a new version.
But the main reason I came to file is that I expected when typing nvm use 15 that it would find v15.14.0 and use it.  I get the impression this was the intended functionality (when I type 15, it tells me about 15.14.0 anyway) but it appears to be failing to match the major version number to an installed version, even though there is one (or more sometimes!) that should match.

OS: Windows 11
NVM: 1.1.9

Additional context:
I am using a utility called gsudo to elevate to administrator as I run the NVM commands.  It is awkward to start PowerShell as administrator every time, and though I saw bug titles suggesting that NVM should raise UAC prompts, I find it doesn't, and both nvm install and nvm use fail without some form on intervention to make either the console or issued command run as administrator.
e.g.
> gsudo nvm use 15
node vv15.14.0 (64-bit) is not installed or cannot be found.

Duplicate of #708, already resolved in https://github.com/coreybutler/nvm-windows/pull/709.

authors: coreybutler jcairney


text:
Add CudaBytes

Would look like this:
#[derive(Debug)]
pub struct CudaBytes {
    pub(crate) cu_device_ptr: sys::CUdeviceptr,
    pub(crate) num_bytes: usize,
    pub(crate) device: ...
}

And this can be unsafely transformed into a CudaSlice

Not much, only that it wouldn't have a type generic on it. Although now that I think about it, we probably don't need this. What we really need is a way to reinterpret a CudaSlice<T> into another type.
What i'd like to do for workspaces is store a CudaSlice<u8> on Cuda, and then grab a view of those bytes as another type.
So maybe something like:
let mut workspace: CudaSlice<u8> = ...;
let _: &CudaView<f32> = workspace.reinterpretted(n)

ah ok; why not directly store it as f32 (dtype)?

Because it needs to support f16, f32, and f64 dtypes, and the device won't necessarily know which one since it doesn't have a dtype generic on it (and I'd prefer not to add it).

but doesn’t e.g. conv2d has a dtype? and the workspace would have the same dtype, wouldn’t it? or where do you plan to use it

https://github.com/coreylowman/dfdx/compare/main...workspace

hmm, ok, so everything runs on a single stream/one cudnn handle?

source: gharchive/issue

repo: coreylowman/cudarc

license_type: permissive

license_source: github-api


text:
netcdf4 is pinned to an old version 1.4.1

Based on the comment in the requirement.txt file looks like the problem is not really netcdf4 for a newer netCDF-C.
See https://github.com/Unidata/netcdf-c/issues/1299
A workaround is to add #fillmismatch at the end of the URL or to fix the metadata.

This is the solution that I need! Thanks! Will make a PR soon.

I would recommend merging #114 before any code change to avoid conflicts.
PS: how are you planning on fixing this issue? adding a f"'"{url}#fillmismatch"  workaround or fixing the offending metadata? The former is quick and easy to do here but the latter is, in theory, the "right way."

I can't change the offending metadata since that's an OOI CI issue, so I'm adding the #fillmismatch in the mean time.

authors: lsetiawan ocefpaf

repo: cormorack/yodapy

license: MIT


text:
Issue reading WW/WC value in multi frame studies

Hi guys,
Today we encountered a strange study from our modality (MRI - Philips Prodiva 1.5T). When opening it with Osimis viewer or MedDream, the WW/WC value displayed on the Web viewer is different compared to Radiant.
Here's the detailed behavior, taken from the 1st image of series SURVEY :

Osimis: WW/WC is 1431/720

MedDream: WW/WC is 1447/724

Radiant: WW/WC is 1628/937

Upon further tag inspection, I found out that this study is multiframe and it's image metadata is stored in the tag (5200,9230)(PerFrameFunctionalGroupsSequence)

From this tag, it appears that the reading in Radiant is correct. Can Cornerstone handle multiframe studies like in Radiant? Is there any way to solve this problem?
Thank you for your time.
Attached study:
ERROR_METADATA.zip
View online: https://www.dicomlibrary.com?study=1.2.826.0.1.3680043.8.1055.1.2020030292322251.187856257.98617819

The width/center is set on the created "Cornerstone Image" in a Cornerstone Image Loader:
https://github.com/cornerstonejs/cornerstoneWADOImageLoader/blob/master/src/imageLoader/createImage.js#L146-L151
This is likely where you would need to add support for this use case. You may want to consider opening a similar issue in that same repository.

repo: cornerstonejs/cornerstone

license: mit

license_source: bigquery


text:
Funktion zum Download der im Schnelltestportal erfaßten Testdaten durch Partner

Problemstellung:
Nach Beendigung des Vertrags (nach Kündigung durch den Partner oder TSI) müssen wir ihm dem Partner die von ihm erhobenen und im Schnelltestportal gespeicherten Testdaten übergeben / bereitstellen.
Diese Daten muß der Partner dann 10 Jahre vorhalten um den rechtlichen Anforderungen zur Aufbewahrung von Gesundheitsdaten zu genügen.
Um diese Anforderung umzusetzen, bekommt der Partner die Möglichkeit, die von ihm erfaßten Testdaten herunterzuladen.
Mit der Bereitstellung der Daten und der fristgerechten Löschung in unseren Systemen haben wir unsere Verpflichtungen gegenüber dem Partner erfüllt.
Vorschlag Dev zur Umsetzung: Konsolidierter Download aller Daten nach Beendigung des Vertrags. Keine Zwischendownloads während der Laufzeit.
To be discussed - ist ein Download in mehreren Etappen / Pakete nicht günstiger? Siehe Betriebsthemen und Vorschlag von Martin Mitev weiter unten.
Task für Laborstream: Kommunikationsmaßnahmen, durch die der Partner zum Download aufgefordert und / oder auf den Ablauf der Frist hingewiesen wird.
Siehe auch Diskussion hier:
https://github.com/corona-warn-app/cwa-quick-test-frontend/issues/300#issuecomment-1111988943
https://github.com/corona-warn-app/cwa-quick-test-frontend/issues/300#issuecomment-1112050238

Operations hat Bedenken, daß wir eine zu hohe Last auf unseren Systemen erzeugen, wenn

sehr viele Partner
zur gleichen Zeit
alle in ihrem Mandanten angefallenen Daten

herunterladen. (Was ein sehr realistisches Szenario ist, wenn wir irgendwann zum Laufzeitende allen Partnern gleichzeitig kündigen.)
TBD - wie können wir das vermeiden / den Download entzerren?
Ideen:

zeitlich versetzter Zugriff der Partner (tbd - wie genau könnten wir Partner dazu bringen, zeitlich gestaffelt auf die Funktion zuzugreifen?)
in mehreren Paketen (nach Monaten oder Quartalen aufgeteilt)
weitere...?
(siehe auch https://github.com/corona-warn-app/cwa-quick-test-frontend/issues/300#issuecomment-1109506318)

Die Vorgehensweise (bei konsolidiertem einmaligem Download zum Vertragsende) wäre dann folgende:

Kündigung zum Stichtag dd.mm.yyyy durch Partner oder TSI. Wir speichern das Kündigungsdatum im Backend.
Bis zum Tag vor dem Datum, an dem die Kündigung wirksam wird, kann der Partner wie gewohnt Testdaten erfassen.
Am Stichtag passiert im Schnelltestportal folgendes:

Wir deaktivieren die Funktion zur Erfassung weiterer Tests.
Wir kopieren alle noch im Kurzzeitarchiv (KZA) befindlichen Daten ins Langzeitarchiv (LZA).
Die Daten bleiben im KZA gespeichert um einen nachträglichen Zugriff zu ermöglichen. Jeweils nach Ablauf von 14 Tagen werden diese Daten (die dann normalerweise ins LZA übertragen werden würden) gelöscht (weil wir sie ja bereits ins LZA übertragen haben).
Wir aktivieren die Downloadfunktion, der Partner hat 4 Wochen Zeit, die Daten herunterzuladen.

4 Wochen nach dem Stichtag dürfen wir den Portalzugang des Partners deaktivieren und die Daten löschen
-> Vorschlag Norbert Völgyi zur effizienten Löschung: https://github.com/corona-warn-app/cwa-quick-test-frontend/issues/300#issuecomment-1109506318
To be discussed - wollen wir dem Partner doch die Möglichkeit geben, Daten während der Laufzeit herunterzuladen?

Annahmen und Anforderungen übergreifend:

Ausschließlich der vom Partner benannte Admin darf die Funktion nutzen können, keine andere Rolle.
Der Admin darf nur die Daten herunterladen, die in seinem Mandanten erfaßt wurden.
Erfolgreicher Login als Admin mit 2FA am Schnelltestportal gilt als hinreichende Autorisierung zum Download der Daten.
Einfachste Variante - Beim Download werden jeweils alle Daten bereitgestellt, die bis zum aktuellen Zeitpunkt im Mandanten gespeichert wurden. (Keine Auswahl eines Berichtszeitraums, keine Inkremente.)
Alternative: Die Dateien können nur paketweise (für Monate oder Quartale) heruntergeladen werden
Der Export erfolgt on demand getriggered durch die Aktion des Admins, es werden keine Daten zum Export paketiert/vorbereitet.
Es werden nur die Daten heruntergeladen, keine Testbelege im PDF-Format.
Geklärt mit Legal: Wir erstellen ein CSV (oder mehrere) mit den Daten.
Die Datei(en) wird/werden gezippt.
Über die zum Download bereitgestellte ZIP-Datei wird ein Hashwert erzeugt. Dieser wird mit einem Zeitstempel und der Kennung des Partners in dem System (Imagemaster?!) abgelegt, wo auch die Partnerverträge langzeitgespeichert werden). Dies kann z.B. gemeinsam mit dem Vertrag des betreffenden Partners oder in einem separaten Dokument über alle Partner erfolgen. Die Werte Hashwert / Zeitstempel / Partnerkennung werden mindestens drei Jahre aufbewahrt.
- Rückmeldung Laborstream - eine Verschlüsselung der heruntergeladenen Dateien wird nicht gefordert.
Vier Wochen nach Eintritt der Kündigung können die Daten aus dem Langzeitarchiv gelöscht werden. Hier

Anforderungen Frontend:
Startseite:

Dem Admin wird auf der Startseite ein neuer Menüpunkt "Datendownload" (Wording tbd) angezeigt.
Wurde der Vertrag gekündigt, wird außerdem ein Hinweistext in Infobox angezeigt "Bitte laden Sie unbedingt Ihre Daten herunter..." (Wording tbd).
Klick auf Button führt auf Unterseite "Datendownload"

Unterseite "Datendownload"

Auf der Unterseite "Datendownload" wird ein Download-Button angezeigt, dazu ein Erklärtext (was wird heruntergeladen, in welchem Format, was soll der Partner dann mit den Daten tun,... - Wording tbd).
Gegebenenfalls kann/muß der Admin einen Zeitraum auswählen, für den die Daten heruntergeladen werden sollen.
Klick auf den Button startet den Download. Die Dateien werden über eine HTTPS-Verbindung bereitgestellt, sind also mindestens beim Transport verschlüsselt.
Nach Abschluß des Downloads wird dem Admin eine Rückmeldung angezeigt, ob der Download erfolgreich war oder nicht. Außerdem Hinweis: "Bitte überprüfen Sie die heruntergeladenen Daten auf Korrektheit und melden Sie sich gegebenenfalls unter Technische Hotline, wenn es ein Problem gibt."
Falls wir Zwischendownloads zulassen wollen: Außerdem Hinweis "wenn in Ihren Teststellen aktuell noch weiterhin Tests durchgeführt werden, müssen Sie die Daten nach Abschluß aller Testtätigkeiten zum Vertragsende nochmals herunterladen um die Vollständigkeit zu gewährleisten". (Wording tbd)

Nach dem Download:
Wir:

Speicherung von Hash der ZIP-Datei, Zeitstempel, Kunden-ID (s.o.) im Vertrags-Archivsystem
Löschen der Daten nach Ablauf der 4-Wochen-Frist

Partner:

Partner muß nach Download prüfen, ob Datei formal ok ist (Vollständigkeit läßt sich schwer überprüfen)
Sollte der Partner Fehler finden (z.B. Datei korrupt, Daten offensichtlich unvollständig), so

Vorschlag Felix:
Kündigungsdatum in Tabelle halten, dann alle Daten ins Langzeitarchiv, danach erst Download anbieten.

Klären mit Laborstream, daß dann keine Zwischendownloads notwendig sind.
Nach dem Datum, zu dem die Kündigung in Kraft tritt darf keine Erfassung von Testdaten mehr möglich sein.

Macht es nicht sinn die Downloadpackete auf Quartal / Monate auf zu teilen damit die auf einmal zu ertellende ZIP Datei nicht zu viel Zeit und Ressourcen dauert bei Partnern die 180K - 200K an tests haben ?
--> wenn eine Aufteilung möglich is könnten die Partner schon jetzt aufgefordert werden alle Test-resultate für 2021 schon vorher herunter zu laden. Ds gibt die möglichkeit die Partner daruaf vor zu bereiten usw...
Da  wir nicht von Portal aus sagen können das der Partner die Datei wirklich heruntergeladen hat wird es keine 100% Information geben das der Download erfolgreiche war außer wenn wir das in einem Feld im Portal machen. Hat dann den Nachteil für die Partner die das nciht machen, wir keinen Nachweis haben.
Löschen würde ich nur bei abshcaltung des Services für alle auf einmal. Bei so einer großen Tabelle dauert eine Löschung Daten sehr lange und wird eventuel den DB cluster an die Limits treiben....(es ist nur 1 der Nodes read / write die anderen sind nur read) Mögliche Lösung den Langzeit DB Cluster aktiv zu nutzen und die Architabelle dahin zu migrieren, dann wird die Performenace vom Portal (wo noch Tests eingestellt werden ) nicht darunter leiden.

Um den Download zu steuern, könnte man ja auch die Daten per Mail zusenden. Der Partner startet den Download und wir verschicken innerhalb von 24h die Daten per Mail?!?!

Um den Download zu steuern, könnte man ja auch die Daten per Mail zusenden. Der Partner startet den Download und wir verschicken innerhalb von 24h die Daten per Mail?!?!

Das hatte ich auch zwischenzeitlich vorgeschlagen. Allerdings wurde der Vorschlag abgelehnt mit dem Hinweis, daß bei einer solchen Push-Lösung wir als Betreiber dafür verantwortlich wären, sicherzustellen, daß die Daten auch beim Partner ankommen. Und da kann ja einiges schiefgehen - eMail-Adresse nicht korrekt, Inbox voll,... was wir dann für mehrere tausend Partner aktiv monitoren müßten.
Vertraglich sind wir nur verpflichtet, die Daten zur Abholung bereitzustellen. Bei der hier vorgeschlagenen Pull-Variante ist der Partner dafür zuständig, die Daten herunterzuladen und muß sich aktiv bei uns melden, wenn es dabei zu Schwierigkeiten kommt.

Macht es nicht sinn die Downloadpackete auf Quartal / Monate auf zu teilen damit die auf einmal zu ertellende ZIP Datei nicht zu viel Zeit und Ressourcen dauert bei Partnern die 180K - 200K an tests haben ? --> wenn eine Aufteilung möglich is könnten die Partner schon jetzt aufgefordert werden alle Test-resultate für 2021 schon vorher herunter zu laden. Ds gibt die möglichkeit die Partner daruaf vor zu bereiten usw...
Da wir nicht von Portal aus sagen können das der Partner die Datei wirklich heruntergeladen hat wird es keine 100% Information geben das der Download erfolgreiche war außer wenn wir das in einem Feld im Portal machen. Hat dann den Nachteil für die Partner die das nciht machen, wir keinen Nachweis haben.
Löschen würde ich nur bei abshcaltung des Services für alle auf einmal. Bei so einer großen Tabelle dauert eine Löschung Daten sehr lange und wird eventuel den DB cluster an die Limits treiben....(es ist nur 1 der Nodes read / write die anderen sind nur read) Mögliche Lösung den Langzeit DB Cluster aktiv zu nutzen und die Architabelle dahin zu migrieren, dann wird die Performenace vom Portal (wo noch Tests eingestellt werden ) nicht darunter leiden.

Aussage Martin - pro Download werden nicht mehr als 1 MB Daten anfallen, wenn der Partner alle Daten gleichzeitig herunterlädt. Anzahl der möglichen parallelen Streams sollte beschränkt werden. (Z.B. ein Download pro vCore pro Zeitpunkt) Monitoring, ob die Last doch zu hoch wird, dann notfalls Maschinen zuschalten. Bottleneck wird aber höchstwahrscheinlich in der DB liegen.
Wir zippen mit ZIP-Stream.
Martin / Julius schreiben das in der kommenden Woche im Detail auf.
Z.B. Persistent View mit Vorsortierung der Daten (Clusterung auf Partner).
Nach Beendigung des Streams (ohne Fehler / I/O Exception) Dokumentation von technisch erfolgreichem Download, sonst Dokumentation von Fehler. (Funktion von TCP ermöglicht Monitoring, ob Stream erfolgreich war.)
Offene Punkte: Wie gehen wir mit Fehlern beim Download um?

Offener Punkt:

Wie informieren wir die Partner - automatisierte oder manuelle eMail, Signatur (von Wilfried?)
Optimalerweise eine einheitliche eMail an alle. Ggf. Erinnerung nur an Partner, die noch nicht heruntergeladen haben.
Outlook-Serien-eMail?
Zeitversetzter / verzögerter eMail-Versand?

Als Diskussionsgrundlage, hier die PRO/CONs für die einzelnen Möglichkeiten:
Kündigungsdatum in SNow eintragen und autom. Mail aus SNow:

individueller Text

Antworten kommen in SNow nicht gesichert an
Fehler Versand wird von SNow nicht erkannt
Mail mit Partner in BCC:

Fehler Versand wird in der FMB erkannt
schneller Versand (500 Partner pro Mail)

keine individuelle Ansprache (z.B. Partner ID)
Antwort teilweise schwierig zuzuordnen
Serien-Mail:

individuelle Mail

jeder Mailversand muss mit Enter bestätigt werden (FMB)

Signatur:
aktuelle Kommunikation aus der FMB signieren wir mit:
Mit freundlichen Grüßen
Ihr Telekom Onboarding-Service für Schnelltestzentren/Labore

Als Diskussionsgrundlage, hier die PRO/CONs für die einzelnen Möglichkeiten: Kündigungsdatum in SNow eintragen und autom. Mail aus SNow: [+] individueller Text [-] Antworten kommen in SNow nicht gesichert an [-] Fehler Versand wird von SNow nicht erkannt Mail mit Partner in BCC: [+] Fehler Versand wird in der FMB erkannt [+] schneller Versand (500 Partner pro Mail) [-] keine individuelle Ansprache (z.B. Partner ID) [-] Antwort teilweise schwierig zuzuordnen Serien-Mail: [+] individuelle Mail [-] jeder Mailversand muss mit Enter bestätigt werden (FMB)
Signatur: aktuelle Kommunikation aus der FMB signieren wir mit: Mit freundlichen Grüßen Ihr Telekom Onboarding-Service für Schnelltestzentren/Labore

Automatisierung müßte in SNow implementiert werden, dann könnten wir große Anzahlen von personalisierten eMails versenden.

authors: BrittaTSI VolBoeck novoelgy

repo: corona-warn-app/cwa-quick-test-frontend


text:
remove WORKDIR from Docker build stage

As all commands in the build stage can be executed with absolute paths, using WORKDIR or cd ${WORK_DIR} are not necessary.
This solves HaDoLint findings DL3003 and SC2164.

@CCFenner could you address linting issues?
/dev/stdin:8 SC2086 Double quote to prevent globbing and word splitting.

@stevesap ignored SC2086 findings as mvn execution will not work as expected if values is quoted.

source: gharchive/pull-request

authors: CCFenner stevesap

repo: corona-warn-app/cwa-server


text:
Test updates event registration

Continue of https://github.com/corona-warn-app/cwa-website/pull/1456

@svengabr
I ran
npm ci
npm run test:prepare
npm run test

and the test for pages/eventRegistration.js  failed. What result do you get?

Follow-up issue https://github.com/corona-warn-app/cwa-website/issues/1503 opened.

repo: corona-warn-app/cwa-website


text:
[Linux] Can't build Android

Self help steps before reporting the issue:

[x] Check Solar2D forums for a solution
[x] If Android: make sure Java8 is installed and reported when running java -version and javac -version if not, download and install Java 8

Before reporting
Install Solar2D today with snap file from Releases. Tried to build a demo project and got build error.
Platforms involved
Building on: Pop!_OS 22.04 LTS x64
Building for: Android
build.settings default from https://docs.coronalabs.com/guide/programming/08/index.html
Full build log
Picked up JAVA_TOOL_OPTIONS: -Duser.language=en

Warning:
The JKS keystore uses a proprietary format. It is recommended to migrate to PKCS12 which is an industry standard format using "keytool -importkeystore -srckeystore /snap/solar2d/x1/usr/local/bin/Solar2D/Resources/debug.keystore -destkeystore /snap/solar2d/x1/usr/local/bin/Solar2D/Resources/debug.keystore -deststoretype pkcs12".
Testing credentials for '/snap/solar2d/x1/usr/local/bin/Solar2D/Resources/debug.keystore': Picked up JAVA_TOOL_OPTIONS: -Duser.language=en
jar signed.

Warning:
The signer's certificate is self-signed.

The timestamp will expire on 2031-11-10.
The selected keystore doesn't have any aliases.

Starting Android build...
Prepackage: Compiling Lua ...Excluding specified files from build:
   excluding: LaunchScreen.storyboardc
   excluding: Icon.png
   excluding: Icon-*dpi.png
   excluding: Images.xcassets
Prepackage: Building server data filePrepackage: running: "/usr/bin/java" -Djava.class.path='/snap/solar2d/x1/usr/local/bin/Solar2D/Resources/ant.jar:/snap/solar2d/x1/usr/local/bin/Solar2D/Resources/ant-launcher.jar:/snap/solar2d/x1/usr/local/bin/Solar2D/Resources/AntLiveManifest.jar' org.apache.tools.ant.launch.Launcher -d -DTEMP_DIR='/tmp/Solar2D/CLtmpFiNvHf' -DSRC_DIR='/home/ccso/Projects/Solar2D/StarShooter' -DBUNDLE_DIR='/snap/solar2d/x1/usr/local/bin/Solar2D/Resources' -DLIVE_BUILD=NO -DLIVE_BUILD_MANIFEST_FILE= -f '/snap/solar2d/x1/usr/local/bin/Solar2D/Resources'/build.xml build-input-zip
Apache Ant version 1.8.1 compiled on April 30 2010
Buildfile: /snap/solar2d/x1/usr/local/bin/Solar2D/Resources/build.xml
Adding reference: ant.PropertyHelper
Detected Java version: 1.6 in: /snap/solar2d/x1/usr/lib/jvm/java-8-openjdk-amd64/jre
Detected OS: Linux
Adding reference: ant.ComponentHelper
Setting ro project property: LIVE_BUILD -> NO
Setting ro project property: BUNDLE_DIR -> /snap/solar2d/x1/usr/local/bin/Solar2D/Resources
Setting ro project property: SRC_DIR -> /home/ccso/Projects/Solar2D/StarShooter
Setting ro project property: TEMP_DIR -> /tmp/Solar2D/CLtmpFiNvHf
Setting ro project property: LIVE_BUILD_MANIFEST_FILE ->
Setting ro project property: ant.file -> /snap/solar2d/x1/usr/local/bin/Solar2D/Resources/build.xml
Setting ro project property: ant.file.type -> file
Adding reference: ant.projectHelper
Adding reference: ant.parsing.context
Adding reference: ant.targets
parsing buildfile /snap/solar2d/x1/usr/local/bin/Solar2D/Resources/build.xml with URI = file:/snap/solar2d/x1/usr/local/bin/Solar2D/Resources/build.xml
Setting ro project property: ant.project.name -> Corona Client Build
Adding reference: Corona Client Build
Setting ro project property: ant.project.default-target -> none
Setting ro project property: ant.file.Corona Client Build -> /snap/solar2d/x1/usr/local/bin/Solar2D/Resources/build.xml
Setting ro project property: ant.file.type.Corona Client Build -> file
Project base dir set to: /snap/solar2d/x1/usr/local/bin/Solar2D/Resources
 +Target:
 +Target: generate-live-build-manifest
 +Target: check-gradle-bundle
 +Target: setup-gradle-builds
 +Target: build-input-zip
 +Target: unzip-apk-template
 +Target: find-main-application-icons
 +Target: find-main-application-banner
 +Target: find-ouya-application-icon
 +Target: find-ouya-xiaomi-application-icon
 +Target: find-default-notification-icons
 +Target: copy-file
 +Target: can-copy-file
 +Target: delete-file
 +Target: can-delete-file
 +Target: insert-main-application-icons
 +Target: insert-main-application-banner
 +Target: insert-ouya-application-icon
 +Target: insert-ouya-xiaomi-application-icon
 +Target: insert-default-notification-icons
 +Target: insert-assets-multi-icon
 +Target: copy-apk-assets
 +Target: copy-files-to-apk
 +Target: sign-apk
 +Target: sign-apk-md5
 +Target: sign-apk-sha1
 +Target: sign-apk-auto
 +Target: build-unsigned-apk
 +Target: build-signed-apk
 +Target: build-expansion-file
 +Target: copy-apk-to
 +Target: copy-to
 +Target: build
 +Target: test-sign
Adding reference: ant.LocalProperties
parsing buildfile jar:file:/snap/solar2d/x1/usr/local/bin/Solar2D/Resources/ant.jar!/org/apache/tools/ant/antlib.xml with URI = jar:file:/snap/solar2d/x1/usr/local/bin/Solar2D/Resources/ant.jar!/org/apache/tools/ant/antlib.xml from a zip file
 [property] Loading /snap/solar2d/x1/usr/local/bin/Solar2D/Resources/build.properties
 [property] Unable to find property file: /snap/solar2d/x1/usr/local/bin/Solar2D/Resources/build.properties
Setting project property: APK_APP_NAME -> MyCoronaActivity
Class org.apache.tools.ant.taskdefs.condition.Os loaded from parent loader (parentFirst)
Condition false; not setting SCRIPT_EXT
Setting project property: SCRIPT_EXT -> sh
Condition false; not setting USE_OLD_TOUCH
Condition false; not setting onWindows
Class org.apache.tools.ant.taskdefs.condition.Equals loaded from parent loader (parentFirst)
Condition false; not setting live.build
Adding reference: asset.fileset
[available] Unable to find /snap/solar2d/x1/usr/local/bin/Solar2D/Native/Corona/android
Condition false; not setting corona.native.android
[available] Unable to find /snap/solar2d/x1/usr/local/Native/Corona/android
Condition false; not setting corona.native.android
[available] Unable to find /snap/solar2d/x1/android
Condition false; not setting corona.native.android
[available] Unable to find /home/ccso/Library/Application Support/Corona/Native/Corona/android
Condition false; not setting corona.native.android
[available] Found: Native/Corona/android
Condition true; setting corona.native.android to /snap/solar2d/x1/usr/local/bin/Solar2D/Resources/Native/Corona/android
Setting project property: corona.native.android -> /snap/solar2d/x1/usr/local/bin/Solar2D/Resources/Native/Corona/android
 +Datatype copy-res-file org.apache.tools.ant.taskdefs.MacroInstance
 [macrodef] creating macro  copy-res-file
 +Datatype copy-drawable-file org.apache.tools.ant.taskdefs.MacroInstance
 [macrodef] creating macro  copy-drawable-file
 +Datatype copy-mipmap-file org.apache.tools.ant.taskdefs.MacroInstance
 [macrodef] creating macro  copy-mipmap-file
 +Datatype copy-notification-icon org.apache.tools.ant.taskdefs.MacroInstance
 [macrodef] creating macro  copy-notification-icon
Setting ro project property: ant.project.invoked-targets -> build-input-zip
Attempting to create object of type org.apache.tools.ant.helper.DefaultExecutor
Adding reference: ant.executor
Build sequence for target(s) `build-input-zip' is [generate-live-build-manifest, check-gradle-bundle, setup-gradle-builds, build-input-zip]
Complete build sequence is [generate-live-build-manifest, check-gradle-bundle, setup-gradle-builds, build-input-zip, can-delete-file, unzip-apk-template, build-unsigned-apk, sign-apk-md5, sign-apk-sha1, can-copy-file, build-signed-apk, copy-files-to-apk, copy-apk-assets, test-sign, find-ouya-xiaomi-application-icon, insert-ouya-xiaomi-application-icon, copy-apk-to, sign-apk-auto, sign-apk, find-main-application-banner, insert-main-application-banner, find-main-application-icons, insert-main-application-icons, find-default-notification-icons, insert-default-notification-icons, insert-assets-multi-icon, build-expansion-file, copy-to, build, find-ouya-application-icon, insert-ouya-application-icon, copy-file, , delete-file]

generate-live-build-manifest:
Skipped because property 'live.build' not set.

check-gradle-bundle:
[available] Found: Native/Corona/android/resource/android-template.zip
Setting project property: gradle.bundle.exists -> true

setup-gradle-builds:
    [unzip] Expanding: /snap/solar2d/x1/usr/local/bin/Solar2D/Resources/Native/Corona/android/resource/android-template.zip into /tmp/Solar2D/CLtmpFiNvHf
    [unzip] extracting template/gradlew.bat
    [unzip] expanding template/gradlew.bat to /tmp/Solar2D/CLtmpFiNvHf/template/gradlew.bat
    [unzip] extracting template/setup.sh
    [unzip] expanding template/setup.sh to /tmp/Solar2D/CLtmpFiNvHf/template/setup.sh
    [unzip] extracting template/gradle.properties
    [unzip] expanding template/gradle.properties to /tmp/Solar2D/CLtmpFiNvHf/template/gradle.properties
    [unzip] extracting template/app/
    [unzip] expanding template/app/ to /tmp/Solar2D/CLtmpFiNvHf/template/app
    [unzip] extracting template/app/build.gradle.kts
    [unzip] expanding template/app/build.gradle.kts to /tmp/Solar2D/CLtmpFiNvHf/template/app/build.gradle.kts
    [unzip] extracting template/gradle/wrapper/gradle-wrapper.properties
    [unzip] expanding template/gradle/wrapper/gradle-wrapper.properties to /tmp/Solar2D/CLtmpFiNvHf/template/gradle/wrapper/gradle-wrapper.properties
    [unzip] extracting template/app/src/main/
    [unzip] expanding template/app/src/main/ to /tmp/Solar2D/CLtmpFiNvHf/template/app/src/main
    [unzip] extracting sdk/licenses/android-sdk-license
    [unzip] expanding sdk/licenses/android-sdk-license to /tmp/Solar2D/CLtmpFiNvHf/sdk/licenses/android-sdk-license
    [unzip] extracting template/app/buildTools/strings.xml
    [unzip] expanding template/app/buildTools/strings.xml to /tmp/Solar2D/CLtmpFiNvHf/template/app/buildTools/strings.xml
    [unzip] extracting template/app/_corona_splash_screen.png
    [unzip] expanding template/app/_corona_splash_screen.png to /tmp/Solar2D/CLtmpFiNvHf/template/app/_corona_splash_screen.png
    [unzip] extracting template/app/src/main/res/values/
    [unzip] expanding template/app/src/main/res/values/ to /tmp/Solar2D/CLtmpFiNvHf/template/app/src/main/res/values
    [unzip] extracting template/
    [unzip] expanding template/ to /tmp/Solar2D/CLtmpFiNvHf/template
    [unzip] extracting sdk/
    [unzip] expanding sdk/ to /tmp/Solar2D/CLtmpFiNvHf/sdk
    [unzip] extracting template/gradlew
    [unzip] expanding template/gradlew to /tmp/Solar2D/CLtmpFiNvHf/template/gradlew
    [unzip] extracting template/app/proguard-rules.pro
    [unzip] expanding template/app/proguard-rules.pro to /tmp/Solar2D/CLtmpFiNvHf/template/app/proguard-rules.pro
    [unzip] extracting template/app/buildTools/update_manifest.lua
    [unzip] expanding template/app/buildTools/update_manifest.lua to /tmp/Solar2D/CLtmpFiNvHf/template/app/buildTools/update_manifest.lua
    [unzip] extracting template/preloadedAssets/build.gradle.kts
    [unzip] expanding template/preloadedAssets/build.gradle.kts to /tmp/Solar2D/CLtmpFiNvHf/template/preloadedAssets/build.gradle.kts
    [unzip] extracting template/app/buildTools/convert_metadata.lua
    [unzip] expanding template/app/buildTools/convert_metadata.lua to /tmp/Solar2D/CLtmpFiNvHf/template/app/buildTools/convert_metadata.lua
    [unzip] extracting template/app/src/main/res/
    [unzip] expanding template/app/src/main/res/ to /tmp/Solar2D/CLtmpFiNvHf/template/app/src/main/res
    [unzip] extracting template/gradle/wrapper/
    [unzip] expanding template/gradle/wrapper/ to /tmp/Solar2D/CLtmpFiNvHf/template/gradle/wrapper
    [unzip] extracting template/gradle/wrapper/gradle-wrapper.jar
    [unzip] expanding template/gradle/wrapper/gradle-wrapper.jar to /tmp/Solar2D/CLtmpFiNvHf/template/gradle/wrapper/gradle-wrapper.jar
    [unzip] extracting template/settings.gradle.kts
    [unzip] expanding template/settings.gradle.kts to /tmp/Solar2D/CLtmpFiNvHf/template/settings.gradle.kts
    [unzip] extracting template/app/src/
    [unzip] expanding template/app/src/ to /tmp/Solar2D/CLtmpFiNvHf/template/app/src
    [unzip] extracting template/PAD.kts.template
    [unzip] expanding template/PAD.kts.template to /tmp/Solar2D/CLtmpFiNvHf/template/PAD.kts.template
    [unzip] extracting template/gradle/
    [unzip] expanding template/gradle/ to /tmp/Solar2D/CLtmpFiNvHf/template/gradle
    [unzip] extracting template/app/src/main/res/values/strings.xml
    [unzip] expanding template/app/src/main/res/values/strings.xml to /tmp/Solar2D/CLtmpFiNvHf/template/app/src/main/res/values/strings.xml
    [unzip] extracting template/app/buildTools/
    [unzip] expanding template/app/buildTools/ to /tmp/Solar2D/CLtmpFiNvHf/template/app/buildTools
    [unzip] extracting template/build.gradle.kts
    [unzip] expanding template/build.gradle.kts to /tmp/Solar2D/CLtmpFiNvHf/template/build.gradle.kts
    [unzip] extracting template/app/libs/licensing-google.jar
    [unzip] expanding template/app/libs/licensing-google.jar to /tmp/Solar2D/CLtmpFiNvHf/template/app/libs/licensing-google.jar
    [unzip] extracting template/app/buildTools/AndroidManifest.template.xml
    [unzip] expanding template/app/buildTools/AndroidManifest.template.xml to /tmp/Solar2D/CLtmpFiNvHf/template/app/buildTools/AndroidManifest.template.xml
    [unzip] extracting template/app/libs/
    [unzip] expanding template/app/libs/ to /tmp/Solar2D/CLtmpFiNvHf/template/app/libs
    [unzip] extracting sdk/licenses/
    [unzip] expanding sdk/licenses/ to /tmp/Solar2D/CLtmpFiNvHf/sdk/licenses
    [unzip] extracting template/setup.bat
    [unzip] expanding template/setup.bat to /tmp/Solar2D/CLtmpFiNvHf/template/setup.bat
    [unzip] extracting template/preloadedAssets/
    [unzip] expanding template/preloadedAssets/ to /tmp/Solar2D/CLtmpFiNvHf/template/preloadedAssets
    [unzip] extracting template/app/src/main/AndroidManifest.xml
    [unzip] expanding template/app/src/main/AndroidManifest.xml to /tmp/Solar2D/CLtmpFiNvHf/template/app/src/main/AndroidManifest.xml
    [unzip] expand complete
FileSet: Setup scanner in dir /tmp/Solar2D/CLtmpFiNvHf/template with patternSet{ includes: [gradlew] excludes: [] }
    [chmod] Executing 'chmod' with arguments:
    [chmod] 'a+x'
    [chmod] '/tmp/Solar2D/CLtmpFiNvHf/template/gradlew'
    [chmod]
    [chmod] The ' characters around the executable and arguments are
    [chmod] not part of the command.
Execute:Java13CommandLauncher: Executing 'chmod' with arguments:
'a+x'
'/tmp/Solar2D/CLtmpFiNvHf/template/gradlew'

The ' characters around the executable and arguments are
not part of the command.
    [chmod] Applied chmod to 1 file and 0 directories.
FileSet: Setup scanner in dir /tmp/Solar2D/CLtmpFiNvHf/template with patternSet{ includes: [setup.sh] excludes: [] }
    [chmod] Executing 'chmod' with arguments:
    [chmod] 'a+x'
    [chmod] '/tmp/Solar2D/CLtmpFiNvHf/template/setup.sh'
    [chmod]
    [chmod] The ' characters around the executable and arguments are
    [chmod] not part of the command.
Execute:Java13CommandLauncher: Executing 'chmod' with arguments:
'a+x'
'/tmp/Solar2D/CLtmpFiNvHf/template/setup.sh'

The ' characters around the executable and arguments are
not part of the command.
    [chmod] Applied chmod to 1 file and 0 directories.
fileset: Setup scanner in dir /snap/solar2d/x1/usr/local/bin/Solar2D/Resources/Native/Corona/android/lib/gradle with patternSet{ includes: [] excludes: [] }
     [copy] Corona.aar added as Corona.aar doesn't exist.
     [copy]  added as  is outdated.
     [copy] Copying 1 file to /tmp/Solar2D/CLtmpFiNvHf/template/app/libs
     [copy] Copying /snap/solar2d/x1/usr/local/bin/Solar2D/Resources/Native/Corona/android/lib/gradle/Corona.aar to /tmp/Solar2D/CLtmpFiNvHf/template/app/libs/Corona.aar

build-input-zip:
Setting project property: USER_ZIP -> /tmp/Solar2D/CLtmpFiNvHf/input.zip
fileset: Setup scanner in dir /tmp/Solar2D/CLtmpFiNvHf with patternSet{ includes: [] excludes: [resource.car] }
      [zip] Building zip: /tmp/Solar2D/CLtmpFiNvHf/input.zip
      [zip] adding directory sdk/
      [zip] adding directory sdk/licenses/
      [zip] adding directory template/
      [zip] adding directory template/app/
      [zip] adding directory template/app/buildTools/
      [zip] adding directory template/app/libs/
      [zip] adding directory template/app/src/
      [zip] adding directory template/app/src/main/
      [zip] adding directory template/app/src/main/res/
      [zip] adding directory template/app/src/main/res/values/
      [zip] adding directory template/gradle/
      [zip] adding directory template/gradle/wrapper/
      [zip] adding directory template/preloadedAssets/
      [zip] adding entry build.properties
      [zip] adding entry config.lu
      [zip] adding entry excludesfile.properties
      [zip] adding entry game.lu
      [zip] adding entry highscores.lu
      [zip] adding entry main.lu
      [zip] adding entry menu.lu
      [zip] adding entry sdk/licenses/android-sdk-license
      [zip] adding entry template/PAD.kts.template
      [zip] adding entry template/app/_corona_splash_screen.png
      [zip] adding entry template/app/build.gradle.kts
      [zip] adding entry template/app/buildTools/AndroidManifest.template.xml
      [zip] adding entry template/app/buildTools/convert_metadata.lua
      [zip] adding entry template/app/buildTools/strings.xml
      [zip] adding entry template/app/buildTools/update_manifest.lua
      [zip] adding entry template/app/libs/Corona.aar
      [zip] adding entry template/app/libs/licensing-google.jar
      [zip] adding entry template/app/proguard-rules.pro
      [zip] adding entry template/app/src/main/AndroidManifest.xml
      [zip] adding entry template/app/src/main/res/values/strings.xml
      [zip] adding entry template/build.gradle.kts
      [zip] adding entry template/gradle.properties
      [zip] adding entry template/gradle/wrapper/gradle-wrapper.jar
      [zip] adding entry template/gradle/wrapper/gradle-wrapper.properties
      [zip] adding entry template/gradlew
      [zip] adding entry template/gradlew.bat
      [zip] adding entry template/preloadedAssets/build.gradle.kts
      [zip] adding entry template/settings.gradle.kts
      [zip] adding entry template/setup.bat
      [zip] adding entry template/setup.sh

BUILD SUCCESSFUL
Total time: 1 second
DeviceBuildData: {"isLaunchPadActive":false,"targetCertType":"distribution","targetPlatformVersion":140300,"debugBuildProcess":100,"targetDevice":0,"dailyBuildRevision":9999,"clientPlatform":"Linux","targetAppStore":"google","targetPlatform":1,"clientDeviceId":"","plugins":[],"dailyBuildYear":2100,"clientProductId":"basic","appName":"StarShooter"}
Build: running: cd '/tmp/Solar2D/CLtmpFiNvHf' && cd template && ./setup.sh && JAVA_VERSION=11 ./gradlew buildCoronaApp --no-daemon -PconfigureCoronaPlugins=YES -PcoronaBuild=2100.9999 -PcoronaResourcesDir='/snap/solar2d/x1/usr/local/bin/Solar2D/Resources' -PcoronaDstDir='/home/ccso/snap/solar2d/x1/Documents/Solar2D Built Apps/StarShooter.Android' -PcoronaTmpDir='/tmp/Solar2D/CLtmpFiNvHf' -PcoronaSrcDir='/home/ccso/Projects/Solar2D/StarShooter' -PcoronaAppFileName='StarShooter' -PcoronaAppPackage='com.solar2d.ccso.StarShooter' -PcoronaVersionCode=1 -PcoronaVersionName='1' -PcoronaKeystore='/snap/solar2d/x1/usr/local/bin/Solar2D/Resources/debug.keystore' -PcoronaKeystorePassword='XXXXXX' -PcoronaKeyAlias='androiddebugkey' -PcoronaTargetStore='google' -PcoronaKeyAliasPassword='XXXXXX' -PcoronaBuildData='/tmp/Solar2D/CLtmpFiNvHf/build.data' --console=plain

Welcome to Gradle 7.5!

Here are the highlights of this release:
 - Support for Java 18
 - Support for building with Groovy 4
 - Much more responsive continuous builds
 - Improved diagnostics for dependency resolution

For more details see https://docs.gradle.org/7.5/release-notes.html

To honour the JVM settings for this build a single-use Daemon process will be forked. See https://docs.gradle.org/7.5/userguide/gradle_daemon.html#sec:disabling_the_daemon.
Daemon will be stopped at the end of the build

FAILURE: Build failed with an exception.

* What went wrong:
A problem occurred configuring root project 'Corona Android'.
> Could not resolve all files for configuration ':classpath'.
   > Could not resolve com.android.tools.build:gradle:7.4.2.
     Required by:
         project :
      > No matching variant of com.android.tools.build:gradle:7.4.2 was found. The consumer was configured to find a runtime of a library compatible with Java 8, packaged as a jar, and its dependencies declared externally, as well as attribute 'org.gradle.plugin.api-version' with value '7.5' but:
          - Variant 'apiElements' capability com.android.tools.build:gradle:7.4.2 declares a library, packaged as a jar, and its dependencies declared externally:
              - Incompatible because this component declares an API of a component compatible with Java 11 and the consumer needed a runtime of a component compatible with Java 8
              - Other compatible attribute:
                  - Doesn't say anything about org.gradle.plugin.api-version (required '7.5')
          - Variant 'javadocElements' capability com.android.tools.build:gradle:7.4.2 declares a runtime of a component, and its dependencies declared externally:
              - Incompatible because this component declares documentation and the consumer needed a library
              - Other compatible attributes:
                  - Doesn't say anything about its target Java version (required compatibility with Java 8)
                  - Doesn't say anything about its elements (required them packaged as a jar)
                  - Doesn't say anything about org.gradle.plugin.api-version (required '7.5')
          - Variant 'runtimeElements' capability com.android.tools.build:gradle:7.4.2 declares a runtime of a library, packaged as a jar, and its dependencies declared externally:
              - Incompatible because this component declares a component compatible with Java 11 and the consumer needed a component compatible with Java 8
              - Other compatible attribute:
                  - Doesn't say anything about org.gradle.plugin.api-version (required '7.5')
          - Variant 'sourcesElements' capability com.android.tools.build:gradle:7.4.2 declares a runtime of a component, and its dependencies declared externally:
              - Incompatible because this component declares documentation and the consumer needed a library
              - Other compatible attributes:
                  - Doesn't say anything about its target Java version (required compatibility with Java 8)
                  - Doesn't say anything about its elements (required them packaged as a jar)
                  - Doesn't say anything about org.gradle.plugin.api-version (required '7.5')

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.

* Get more help at https://help.gradle.org

Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0.

You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.

See https://docs.gradle.org/7.5/userguide/command_line_interface.html#sec:command_line_warnings

BUILD FAILED in 2s
Android build failed (256) after 5 seconds

Incompatible because this component declares an API of a component compatible with Java 11 and the consumer needed a runtime of a component compatible with Java 8

Try using JDK 11+.
The issue template may misleading.

ccso@home:~$ javac -version
javac 17.0.10
ccso@home:~$ java -version
openjdk version "17.0.10" 2024-01-16
OpenJDK Runtime Environment (build 17.0.10+7-Ubuntu-122.04.1)
OpenJDK 64-Bit Server VM (build 17.0.10+7-Ubuntu-122.04.1, mixed mode, sharing)

The same issue. Maybe need to upgrade Java SDK inside snap? But how?

Sorry I can't access linux right now and I'm not sure if this will fix the problem.
Can you export JAVA_HOME for your JDK installation location on your terminal, then set jdk/bin to PATH and try to open solar2d from the terminal?
It looks something like this:
# setup variable for current terminal
$ export JAVA_HOME=/somewhere/jdk11
$ export PATH=$JAVA_HOME/bin:$PATH
# start with above variables
$ solar2d

If the above settings do not build Android properly, we need to wait for the engine core to modify the JDK version on which it depends.

The same. I think that need to update sdk inside Snap filesystem, because in log:
Detected Java version: 1.6 in: /snap/solar2d/x1/usr/lib/jvm/java-8-openjdk-amd64/jre

The same. I think that need to update sdk inside Snap filesystem, because in log:
Detected Java version: 1.6 in: /snap/solar2d/x1/usr/lib/jvm/java-8-openjdk-amd64/jre

It doesn't use Java from the system :(

I had to use OpenJDK version 17 to be able to build Android in Linux.... but it is working now for me
I suggest you look at my posts and the first users posts on　　https://forums.solar2d.com/t/how-i-made-solar2d-works-on-linux/356469/13

ccso@home:~$ javac -version
javac 17.0.10
ccso@home:~$ java -version
openjdk version "17.0.10" 2024-01-16
OpenJDK Runtime Environment (build 17.0.10+7-Ubuntu-122.04.1)
OpenJDK 64-Bit Server VM (build 17.0.10+7-Ubuntu-122.04.1, mixed mode, sharing)

The same issue. Maybe need to upgrade Java SDK inside snap? But how?

@amigojapan already installed JDK 17

It suppose to use built in JDK

authors: Shchvova alchem1ster amigojapan clang-clang-clang

repo: coronalabs/corona


text:
Add guide for configuration am and ruler with mounted config maps

Context: The documentation on how to setup and run Alertmanager/Ruler is quite difficult to follow and not comprehensive. Many people have been running into issues regarding the sidecar. In fact, I was advised by some folks who contribute regularly to cortex to actually avoid using the sidecar. For this reason, I chose to add a guide on how to setup the ruler and alertmanager simply with configmaps which mount onto the container itself.
What this PR does: Adds a guide on how to configure cortex alertmanager and ruler using configmaps mounted onto the containers
Checklist

[x] CHANGELOG.md updated - the order of entries should be [CHANGE], [FEATURE], [ENHANCEMENT], [BUGFIX]

Hey @AkashSirimanna,
Thank's a lot for the great guide. However for the ruler you could also have used this https://github.com/cortexproject/cortex-helm-chart/blob/master/templates/ruler/ruler-dep.yaml#L136 which is a bit easier than manually mounting every tenant configmap.
Helm Values on how to use that for the ruler (doesn't exists for alertmanager) exist here: https://cortexproject.github.io/cortex-helm-chart/guides/configure_rules_via_configmap.html

Hi @nschad thank you for the review.
I can add a section for this as well. Maybe the user can choose between the 2, depending on what works for them.
The reason I decided to go with the mounting approach was this: We would need to define the rules under the ruler.directories.tenant key. In order to do this, we would need to have the rules defined either in the helm-chart or in a separate file which is in the same repository as the helm chart. In our case, our rules were defined elsewhere in a different repo, this is I we chose to go with the mounting approach.
If you wanted to use the directory approach, we would need to have the rules files in the same repo as the helm chart, which is usually not the case. In the mounting approach, you are able to have them maintained elsewhere.
Nonetheless, I see the benefits of both sides, possibly I could add another section to the guide with how to setup the directories method?

ruler.directories.tenant

I actually would like to

Hi @nschad thank you for the review.
I can add a section for this as well. Maybe the user can choose between the 2, depending on what works for them.
The reason I decided to go with the mounting approach was this: We would need to define the rules under the ruler.directories.tenant key. In order to do this, we would need to have the rules defined either in the helm-chart or in a separate file which is in the same repository as the helm chart. In our case, our rules were defined elsewhere in a different repo, this is I we chose to go with the mounting approach.
If you wanted to use the directory approach, we would need to have the rules files in the same repo as the helm chart, which is usually not the case. In the mounting approach, you are able to have them maintained elsewhere.
Nonetheless, I see the benefits of both sides, possibly I could add another section to the guide with how to setup the directories method?

I actually would like to deprecate ruler.directories.tenant because the alertmanager doesn't have it and I don't think its necessary thing to have

I see. If thats the case, what do you think of this guide then? If theres anything to add/remove/modify let me know.

@nschad Thank you for the suggestions, I incorporated them and also changed tenantA to tenantfoo, i realized that capital letters in config map names are invalid.
I'll squash the commits once the changes look good

Good to go 😄

Looks good however I won't get to testing it today but probably tomorrow :)

Sounds good! Im going to test it out in a bit to make sure everything is good

Tested on a local minikube cluster and it seems to be working :) I'll check back once you've got a chance to test it :)

@AkashSirimanna Cool. I fixxed the Git mess I caused. Sorry about that. You probably wanna do
git fetch origin am-ruler-configmap-guide
git reset --hard origin/am-ruler-configmap-guide

but you are done so probably no need :)

Ah no worries, I probably helped mess it up 🤣 .
Thanks for the review, hopefully this helps the community out a bit.

@AkashSirimanna Okay LOL.
I keep finding Issues but I think I got them all now (some of them have nothing to-do with you).

Thank you @kd7lxl, ill go ahead and make the changes

authors: AkashSirimanna nschad

repo: cortexproject/cortex-helm-chart


text:
Updates to axis limit resetting

This PR contains some updates (and removes some unnecessary stuff) to make axis limit updating work. The updates here functioning correctly rely on https://github.com/cosmicds/cosmicds/pull/177.

@Carifio24 The data update worked in my testing.👍
We'll need to think about how to handle complicated situations like with this slider:

The line fit needs to be updated.
With the data update, the age value will be different, which may put it in a different sort order in the slider list.

Cool, glad to hear the data update is working  :thumbsup:
The slider already has logic to handle the data update - all we need to do is call its refresh method after that happens. This was in stage 3 pre-split, but I'll take a look at the new setup and make sure it gets called when appropriate.
I'll also take a look at the line fitting. The line fit tool should listen to changes in the data that it's fitting to, but maybe things are getting updated in a way that it doesn't expect.

Stage 4 & 5 were updated appropriately in #109

authors: Carifio24 johnarban patudom

repo: cosmicds/hubbleds


text:
metamask snap support

[x] #302
[x] #303
[ ] #304
[x] Support "Avatar" component#479

Flip the logos, according to the MetaMask team

authors: pyramation twhy

repo: cosmology-tech/cosmos-kit


text:
cosmetic improvements to sidebar and li's

attempted some improvements related to consistency and readability

Resolved by #147

authors: jolesbi nylira

repo: cosmos/cosmos-ui


text:
Test and Document IBC upgrade support for genesis dump/restart

Summary
Currently IBC only supports IBC breaking change upgrades via the x/upgrade module. We should add additional support via the genesis dump state/restart mechanism.
Problem Definition
If the x/upgrade has a bug that prevents it from being used, genesis dump/restart would be required. In this case, the chain-id would need to be incremented, effectively breaking all existing IBC channels. To avoid this, the chain would need to halt and wait for the core devs to push a fix which fixes the code at the halting height and then the chain would likely want to use the upgrade module to swap binaries to something more stable.
While this scenario is unlikely, if it did ever occur, I'm sure it would cause a lot of people headaches.
Proposal
Support genesis dump/restart. Revision numbers are already handled, so we just need to rework the current design to be a little more modular and not rely solely on the x/upgrade module. Ideally we could isolate the IBC specific code into it's own proposal. Then upgrade proposals which want to do an IBC upgrade, would include the IBC proposal as well (gov proposals can have multiple changes in one).
I'll defer to @AdityaSripal on the specific design, but I think it's worthwhile to ensure IBC upgrades aren't dependent on bug-free code (by limiting the amount of code the IBC upgrades rely on)

For Admin Use

[ ] Not duplicate issue
[ ] Appropriate labels applied
[ ] Appropriate contributors tagged
[ ] Contributor assigned/self-assigned

Currently not supported:
Error: error validating genesis file /home/bartleby/.gm/network2/config/genesis.json: invalid client consensus state timestamp:<seconds:1623670799 nanos:385043798 > root:<> next_validators_hash:"Y\2631\031K\317\231.\336\300\233\204\265\264?(\335\326\003\323\331%\2432`\351\035\371\007\257\251\272"  clientID 07-tendermint-1 index 8: root cannot be empty: invalid consensus state [cosmos/ibc-go@v1.0.0-alpha2.0.20210615093027-ca070bd2c6aa/modules/light-clients/07-tendermint/types/consensus_state.go:46]

We need to loosen genesis validation since there may exist consensus states with empty roots (due to upgrades)

I'd rather we just use a sentinel root value in upgrade consensus state and keep that check. Rather than remembering to put it wherever needed.

I tested this and an upgrade + genesis restart worked fine. A genesis restart without an upgrade did not work with the relayers since the data gets reset. The trusted header could no longer be queried. When I get time I'll add documentation for this upgrade path

authors: AdityaSripal colin-axner

repo: cosmos/ibc-go


text:
e2e: adding e2e upgrade test for ibc-go/v6

Description

Adding E2E upgrade test for ibc-go/v6

Workflow

https://github.com/cosmos/ibc-go/actions/runs/3234968284

Local test setup for work-in-progress

Pull ibc-go-icad docker images

docker pull ghcr.io/cosmos/ibc-go-icad:v0.3.5
docker pull ghcr.io/cosmos/ibc-go-icad:v0.4.0

Export e2e env variables

export CHAIN_BINARY=icad
export CHAIN_IMAGE=ghcr.io/cosmos/ibc-go-icad
export CHAIN_A_TAG=v0.3.5

Run e2e upgrade test

cd e2e
make e2e-test entrypoint=TestUpgradeTestSuite test=TestV5ToV6ChainUpgrade

closes: #2188

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

[ ] Targeted PR against correct branch (see CONTRIBUTING.md)
[ ] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[ ] Code follows the module structure standards.
[ ] Wrote unit and integration tests
[ ] Updated relevant documentation (docs/) or specification (x/<module>/spec/)
[ ] Added relevant godoc comments.
[ ] Added a relevant changelog entry to the Unreleased section in CHANGELOG.md
[ ] Re-reviewed Files changed in the Github PR explorer
[ ] Review Codecov Report in the comment section below once CI passes

Codecov Report

Merging #2490 (e1d07ac) into main (6105db4) will not change coverage.
The diff coverage is n/a.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #2490   +/-   ##
=======================================
  Coverage   78.76%   78.76%
=======================================
  Files         178      178
  Lines       12298    12298
=======================================
  Hits         9687     9687
  Misses       2188     2188
  Partials      423      423

Impacted Files
Coverage Δ

modules/apps/27-interchain-accounts/types/codec.go
79.54% <0.00%> (ø)

.../apps/27-interchain-accounts/host/client/cli/tx.go
29.70% <0.00%> (ø)

authors: codecov-commenter damiannolan


text:
chore: improve error message in ics29 OnChanOpenAck version comparison

Description

closes: #858

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

[ ] Targeted PR against correct branch (see CONTRIBUTING.md)
[ ] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[ ] Code follows the module structure standards.
[ ] Wrote unit and integration tests
[ ] Updated relevant documentation (docs/) or specification (x/<module>/spec/)
[ ] Added relevant godoc comments.
[ ] Added a relevant changelog entry to the Unreleased section in CHANGELOG.md
[ ] Re-reviewed Files changed in the Github PR explorer
[ ] Review Codecov Report in the comment section below once CI passes

Codecov Report

Merging #971 (ee50fa5) into ics29-fee-middleware (6928af7) will decrease coverage by 0.00%.
The diff coverage is 100.00%.

@@                   Coverage Diff                    @@
##           ics29-fee-middleware     #971      +/-   ##
========================================================
- Coverage                 79.89%   79.89%   -0.01%
========================================================
  Files                       165      165
  Lines                     11664    11662       -2
========================================================
- Hits                       9319     9317       -2
  Misses                     1896     1896
  Partials                    449      449

Impacted Files
Coverage Δ

modules/apps/29-fee/ibc_module.go
93.87% <100.00%> (ø)

.../light-clients/07-tendermint/types/client_state.go
72.16% <0.00%> (-0.18%)
:arrow_down:

authors: codecov-commenter colin-axner


text:
Error: Cannot find module 'lodash'

truffle test --network ganache
Using network 'ganache'.
Error: Cannot find module 'lodash'
at Function.Module._resolveFilename (module.js:555:15)
at Function.Module._load (module.js:482:25)
at Module.require (module.js:604:17)
at require (internal/module.js:11:18)
at Object. (/home/wade.lee/goWorkProject/src/github.com/cosmos/peggy/ethereum-contracts/test/utils.js:3:9)
at Module._compile (module.js:660:30)
at Object.Module._extensions..js (module.js:671:10)
at Module.load (module.js:573:32)
at tryModuleLoad (module.js:513:12)
at Function.Module._load (module.js:505:3)
at Module.require (module.js:604:17)
at require (internal/module.js:11:18)
at Object. (/home/wade.lee/goWorkProject/src/github.com/cosmos/peggy/ethereum-contracts/test/cosmosERC20.js:4:15)
at Module._compile (module.js:660:30)
at Object.Module._extensions..js (module.js:671:10)
at Module.load (module.js:573:32)
at tryModuleLoad (module.js:513:12)
at Function.Module._load (module.js:505:3)
at Module.require (module.js:604:17)
at require (internal/module.js:11:18)
at /usr/local/lib/node_modules/truffle/node_modules/mocha/lib/mocha.js:231:27
at Array.forEach ()
at Mocha.loadFiles (/usr/local/lib/node_modules/truffle/node_modules/mocha/lib/mocha.js:228:14)
at Mocha.run (/usr/local/lib/node_modules/truffle/node_modules/mocha/lib/mocha.js:514:10)
at /usr/local/lib/node_modules/truffle/build/webpack:/~/truffle-core/lib/test.js:125:1
at
at process._tickCallback (internal/process/next_tick.js:160:7)

thanks a lot

The repo is being revived by Swishlabs, see this announcement and this PR. Stay tuned for an updated README and more information

repo: cosmos/peggy


text:
staking Params and Pool

Description:

Implement design to implement the view for querying Params and Pool
See PR: cosmos/cosmos-sdk#2099

[x] Endpoints
[ ] Design
[ ] Implementation

hey @fedekunze can you help explain what is required here? what is the feature? how should it work?

@jb There are 2 new staking endpoints to query info about global parameters and the staking pool. You can see the list of attributes returned here.
The new staking endpoints are GET stake/pool and GET stake/parameters.
In short, this would require a modal or new tab in staking that shows this information.

Is this on the roadmap?
I'm concerned about feature creep.  Let's consider this for Staking 2.0.

@fedekunze i am not convinced we need to show this data in voyager. do you think we should? can you make a case for it?

I think parameters for a network would be nice to show, right?

maybe - but i don't think this is a staking issue.

imo it's defenitely staking. The inflation, unbonding period, max number of validators on the Hub, etc are things that are very important for delegators to be aware of

Fede argues it is low work high value: we could have a simple modal showing with a button on the staking page showing this.

nothing is simple 😜

hahahah soooooo true

@jbibla do you have designs for this on your todo list?

very simple design: https://zpl.io/bo9WBnZ

Why is this blocked?

was blocked by an absence of designs.

@jbibla should I proceed with the comments I added to the Params Tab ?

yes! they are all great points / suggestions.

authors: NodeGuy faboweb fedekunze jbibla

repo: cosmos/voyager


text:
WIP: Add shell script diagnostics to testnets build script.

Closes #1126
Description:

❤ Thank you!

I pushed a solution proposal. Can you verify this works? And maybe explain to me, why it works this way? ^^

That is SUPER mysterious!  We're running in Docker so shouldn't be getting a "works on my machine" error like this.  I can't think of any hypothesis that explains the problem.  Your workaround is not a good one and should be unnecessary.
Please try collaborating with someone local (Billy or Fede) and see if they notice anything, otherwise we can schedule a meeting to debug it together.

Your workaround is not a good one and should be unnecessary.

Can you elaborate why this is a bad solution?

Closed in favor of https://github.com/cosmos/voyager/pull/1176.

authors: NodeGuy faboweb


text:
🛑 Mainnet [TezTools] (eu01-node.teztools.net) is down

In 723318d, Mainnet [TezTools] (eu01-node.teztools.net) (https://eu01-node.teztools.net/chains/main/blocks/head/header) was down:

HTTP code: 502
Response time: 471 ms

Resolved: Mainnet [TezTools] (eu01-node.teztools.net) is back up in 6a86210.

repo: cotezos/teznodes


text:
🛑 Mainnet Giganode [tezos Ukraine] is down

In 100c009, Mainnet Giganode [tezos Ukraine] (https://mainnet-tezos.giganode.io/chains/main/blocks/head) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Mainnet Giganode [tezos Ukraine] is back up in 5cdcc5f.


text:
Use per batch buffer in 'couchstore_save_documents'

buffer size is set to ~META_MAXLEN+DATA_MAXLEN.
DATA_MAXLEN is set as the upper bound for uniform
distribution and is set to median + 5*(standard deviation)
for normal distribution

Venu, would you please make the same change for the wrapper for LevelDB (couch_level.cc)? These changes look good to me.

Trying to resolve an imaginary issue caused some unnecessary commits. will close this and open a new pull request.

repo: couchbaselabs/ForestDB-Benchmark


text:
Auto-parse links (fixes Issue #9)

see https://api.slack.com/docs/formatting

This would also depend on removing the triple backticks from responses... maybe need a command line switch for the triple backticks?

Thank you for improving slacktee!
Yeah, having a command line switch for the triple backticks is good idea. In some cases, we don't want to show the output as pre-formatted text.
Also, I prefer to have another command line switch for 'parse=full' option which is turned-off by default. I'm a little bit worry that slacktee unexpectedly sends unnecessary notification to users a lot.
Could you implement these options?
If it's tough, please let me know. I will work on it. :)
Again, thank you so much for contributing slacksee!!

I'll have a go now. Are you happy with one merge request for both
features?? What would you like the defaults to be?
On 16 Jan 2015 18:14, "Chikashi Kato" notifications@github.com wrote:

Thank you for improving slacktee!
Yeah, having a command line switch for the triple backticks is good idea.
In some cases, we don't want to show the output as pre-formatted text.
Also, I prefer to have another command line switch for 'parse=full' option
which is turned-off by default. I'm a little bit worry that slacktee
unexpectedly sends unnecessary notification to users a lot.
Could you implement these options?
If it's tough, please let me know. I will work on it. :)
Again, thank you so much for contributing slacksee!!
—
Reply to this email directly or view it on GitHub
https://github.com/course-hero/slacktee/pull/11#issuecomment-70296300.

One merge request for both features is fine for me.
By default, I'd like to disable 'perse=full' and enable triple backticks formatting.
I really appreciate your great contribution!

Hi, I've updated the MR. you might want to tweak the names of the command line option as well as the help information printed out. I realised that if triple back-ticks was enabled, the parse option would have no effect (as slack won't try to find links inside the code block). So to avoid confusion, I have one command line option with 3 possible values that represent the 3 possible combinations that make sense.

Great implementation!! I will test it on my side quickly and merge it into master branch.
I really appreciate your contribution. It's awesome!!

I found a backward compatibility issue in the file uploading mode (with -f option).
Originally, open and download URL have been linked to the file, but they were not linked in new version.
To fix this issue, I separated out the plain text option (-p option) from the message formatting option.
Also, I added 'link_names' mode to the message formatting option.
In many cases, 'link_names' mode is more useful than 'full' mode.
If you find any issues in my code, please feel free to let me know.
Again, I really appreciate your great contribution!!!

Thanks! I hadn't noticed that slack parses URLs inside code blocks....

Yeah, it's a little bit funky behavior :stuck_out_tongue_winking_eye:

authors: Chikashi-Kato samskiter

repo: course-hero/slacktee


text:
Fixes file names based on older BIDS convention

The dataset has recently been updated to change a few file names that follow the up-to-date BIDS convention, so the processing script should also be updated to reflect those changes.
Fixes #30

Done in #33

authors: jcohenadad mathieuboudreau

repo: courtois-neuromod/anat-processing


text:
Tweaks: image alignment, responsiveness, typography

Summary

Added a WhyCard component. Note that any property you pass to this component will get applied to the v-img within

WhyCard is used on the index and pilot pages

Made typography responsive

Also all typography except webfont loading is just in typography.scss

Removed issue where first non-container item of a group of divs had no top/bottom padding (while leaving top/bottom padding removal for main container)
Separated out xs and sm sizing for columns in index.vue
Removed transitions css from index.vue

Made a few additional tweaks to /pilot to make sure there is no white margin on the right caused svg widths that don't adjust proportionally to fit smaller screen.  Appears /how-it-works still needs this treatment.

authors: alexanian jcolla-holla


text:
Scraper 599

Summary
Fixes issue #599
St. Louis County is posting most recent changes in cases on county page: https://stlouisco.com/Your-Government/County-Executive/COVID-19
Numbers from MO Health Dept have a delay.
Changes

Scrape case numbers for St. Louis County directly from linked ArcGIS map from county website.
No longer combining St. Louis County cases with St. Louis City

Additional notes
Please note, before this change we were merging case numbers of St. Louis City with St. Louis County.  I'm not sure what the reasoning was originally, but as a user of the source code I would personally prefer to keep them separate since we seem to separate city/county for other areas, such as my home town Richmond City vs Richmond County.

fixes #599

Thanks for working with me to understand the changes!

authors: lazd praging slezakbs

repo: covidatlas/coronadatascraper


text:
Refactor SCSS for buttons

Closes #253
Will do modals in a follow-up PR.

Added a small change to #progress-container in button.scss that resolves the jerky login experience.  I think this will resolve any similar jerky experiences across the app (I'm not sure if there even were any), but it may not.  If there are any ones that you're aware of, let's test them.  I tried to find them all and I didn't see any jerky element resizing upon the <CircularProgress> element loading.
Just added a simple height and margin-top to the #progress-container to be in line with <button> within any use of <PendingButtonOperation>.  Would have preferred something like align-items: center and doing away with margin-tops all together, but the committed approach worked and I think it will work across the board so I see no reason to change.
Preview of post-commit what the login experience looks like:

Looks good. I changed progress-container to a class in case there is more than one on a page.

authors: aidan-fitz jcolla-holla

repo: covidwatchorg/permission-portal


text:
keras and tensorflow and python version

Can someone point me to the right combination of keras, tensorflow and python version that this current code will work on.
Any combination of the above mentioned packages seem to throw an error when I run kitti_evaluate.py
The environment.yml file did not work for me.
Thanks

Hi, I also tried some combinations(^^;). So far I can construct my environment with the following:

remove tensorflow-gpu, cudatoolkit and cudnn from environment.yml
construct new environment with the edited environment.yml
install tensorflow-gpu 1.12.0 with conda command (this can install relevant cudatoolkit and cudnn together)
Hope this can help. :-)

authors: mahaling s-sekiguchi

repo: coxlab/prednet


text:
HTTPCORE-590 Ensure LaxConnPool doesn't leak connections

by testing that lease Future completion is successful.

@coxlinton Looks good to me. Please raise a PR against the project repository.

repo: coxlinton/httpcomponents-core


text:
Cpputest for Android

Disclaimer: I'm a complete newbie in the Android NDK scene.
I need to write C++ UTs for my Android native code which I can execute on both Windows and OSX via the command line. I would like to compile Cpputest for my requirements. Can anyone help me out with a few pointers on how to get started.
Thank you!

I think you can follow http://cpputest.github.io/ to get started

authors: cuitoldfish oargaruna

repo: cpputest/cpputest


text:
IAR 8.1 CppUTest fails to build

The project cpputest\platforms\iar\CppUTest.eww fails to build with IAR 8.1:
CommandLineArguments.cpp
Error[Pe135]: namespace "std" (declared at line 185 of "C:\Program Files (x86)\IAR Systems\Embedded Workbench 8.1\arm\inc\c\yvals.h") has no member "nullptr_t" cpputest\include\CppUTest\SimpleString.h 182
Error while running C/C++ Compiler

I have added cstddef as preinclude:
Preinclude file:
C:\Program Files (x86)\IAR Systems\Embedded Workbench 8.1\arm\inc\cpp\cstddef

But then I have these errors:
Error[Pe079]: expected a type specifier cpputest\src\CppUTest\SimpleString.cpp 548
Warning[Pe815]: type qualifier on return type is meaningless cpputest\src\CppUTest\SimpleString.cpp 548
Error[Pe018]: expected a ")" cpputest\src\CppUTest\SimpleString.cpp 548
Error while running C/C++ Compiler

Which occur here:
#if __cplusplus > 199711L && !defined __arm__
SimpleString StringFrom(const std::nullptr_t __attribute__((unused)) value)
{
    return "(null)";
}

It seems neither __arm__ nor __cplusplus is defined. So I added them as defines. I also disabled the exceptions because the library is meant to be used on embedded devices.
CPPUTEST_STD_CPP_LIB_DISABLED=1
__arm__
__cplusplus=200000L

This time the project builds without errors

IAR's compiler guide for 8.10 claims __cplusplus=199711L is defined, but I am seeing that __cplusplus is actually 201402L on my system. IARs docs are out of date. To get past this I had to add !defined __ICCARM__ to that line. That feels like a hack.

I think that this has been resolved? Can you confirm that?
Is there any reasonable way to get the IAR build in the travis CI?

authors: basvodde nowox watersne


text:
Refactor 20170611 seperate xpath

ok

Be prepared to publish v0.5.0 version,  this version is code refactor.
Seperate html parser part to a single file.

repo: cpselvis/zhihu-crawler


text:
Change the base image from java to openjdk

The Java image was deprecated in favor of the OpenJDK and it will stop being maintained at the end of the year (2016-12-31). This change addresses the issue and shouldn't affect any image as the Java image is running OpenJDK.

Thanks!


text:
buf.PartialLogMetadata always is null

I am writing a plugin for my logging system.
And I can not solve the problem.
I have large log lines, more than 16k
Logs should be split
https://github.com/cpuguy83/docker-log-driver-test/blob/master/driver.go#L106-L110
This code does not work for me. buf.PartialLogMetadata is always null
buf.Partial = true  if the line of the log is more then 16k
But I really need the value of buf.PartialLogMetadata.Last to know where the log break ends

This will depend on your version of Docker.

docker version
Client:
 Version:           18.09.4
 API version:       1.39
 Go version:        go1.10.8
 Git commit:        d14af54266
 Built:             Wed Mar 27 18:34:51 2019
 OS/Arch:           linux/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          18.09.4
  API version:      1.39 (minimum version 1.12)
  Go version:       go1.10.8
  Git commit:       d14af54
  Built:            Wed Mar 27 18:04:46 2019
  OS/Arch:          linux/amd64
  Experimental:     false

docker info
Containers: 56
 Running: 5
 Paused: 0
 Stopped: 51
Images: 8
Server Version: 18.09.4
Storage Driver: overlay2
 Backing Filesystem: xfs
 Supports d_type: true
 Native Overlay Diff: false
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge host macvlan null overlay
 Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
Swarm: active
 NodeID: ju6l17wqrqckdydjt4gmn0yxl
 Is Manager: true
 ClusterID: pchagw7bo5rxx1db9gm79ijj9
 Managers: 1
 Nodes: 1
 Default Address Pool: 10.0.0.0/8
 SubnetSize: 24
 Orchestration:
  Task History Retention Limit: 5
 Raft:
  Snapshot Interval: 10000
  Number of Old Snapshots to Retain: 0
  Heartbeat Tick: 1
  Election Tick: 10
 Dispatcher:
  Heartbeat Period: 5 seconds
 CA Configuration:
  Expiry Duration: 3 months
  Force Rotate: 0
 Autolock Managers: false
 Root Rotation In Progress: false
 Node Address: 192.168.30.11
 Manager Addresses:
  192.168.30.11:2377
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: bb71b10fd8f58240ca47fbb579b9d1028eea7c84
runc version: 2b18fe1d885ee5083ef9f0838fee39b62d653e30
init version: fec3683
Security Options:
 seccomp
  Profile: default
Kernel Version: 4.14.35-1844.0.7.el7uek.x86_64
Operating System: Oracle Linux Server 7.6
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 5.673GiB
Name: host1
ID: 5YIF:KRPU:DRHL:MA4R:WQ4P:GQL3:SYCO:FS3Q:74KU:XMAD:DQZY:RGQM
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
 127.0.0.0/8
Live Restore Enabled: false
Product License: Community Engine

I installed the nightly build and repeated the issue.
buf.PartialLogMetadata is always null
 Version:           0.0.0-20190402003748-9de3848
 API version:       1.40
 Go version:        go1.11.5
 Git commit:        9de3848
 Built:             Tue Apr  2 07:29:48 2019
 OS/Arch:           linux/amd64
 Experimental:      false

Server:
 Engine:
  Version:          0.0.0-20190402003748-9de3848
  API version:      1.40 (minimum version 1.12)
  Go version:       go1.11.5
  Git commit:       9de3848
  Built:            Tue Apr  2 07:28:31 2019
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.2.5
  GitCommit:        bb71b10fd8f58240ca47fbb579b9d1028eea7c84
 runc:
  Version:          1.0.0-rc6+dev
  GitCommit:        2b18fe1d885ee5083ef9f0838fee39b62d653e30
 docker-init:
  Version:          0.18.0
  GitCommit:        fec3683

Probably problem here
https://github.com/moby/moby/blob/master/daemon/logger/adapter.go#L38-L41


text:
Copying object in seq

Code 1:
+package sandbox
+alias stdout org.eolang.io.stdout
+alias sprintf org.eolang.txt.sprintf
+alias org.eolang.gray.cage

[] > test

[args...] > app
  cage > a
  seq > @
    a.write
      test
    stdout
      "Done!\n"

Code 2:
+package sandbox
+alias stdout org.eolang.io.stdout
+alias sprintf org.eolang.txt.sprintf
+alias org.eolang.gray.cage

[] > test

[args...] > app
  cage > a
  seq > @
    test
    stdout
      "Done!\n"

Code 1 runs without any errors.
Code 2 produces following error:
Exception in thread "main" org.eolang.Attr$StillAbstractException: The attribute is not initialized, can't read
	at org.eolang.AtFree.get(AtFree.java:83)
	at org.eolang.CachedPhi.get(CachedPhi.java:74)
	at org.eolang.PhDefault.attr(PhDefault.java:208)
	at org.eolang.Dataized.take(Dataized.java:71)
	at EOorg.EOeolang.EOseq.lambda$new$0(EOseq.java:56)
	at org.eolang.AtComposite.lambda$toData$0(AtComposite.java:88)
	at org.eolang.AtComposite.get(AtComposite.java:68)
	at org.eolang.CachedPhi.get(CachedPhi.java:74)
	at org.eolang.PhDefault.attr(PhDefault.java:208)
	at org.eolang.PhOnce.attr(PhOnce.java:96)
	at org.eolang.PhOnce.attr(PhOnce.java:96)
	at org.eolang.PhOnce.attr(PhOnce.java:96)
	at org.eolang.PhDefault.attr(PhDefault.java:208)
	at org.eolang.Dataized.take(Dataized.java:71)
	at org.eolang.Dataized.take(Dataized.java:110)
	at org.eolang.Main.run(Main.java:166)
	at org.eolang.Main.main(Main.java:91)

Why does it happen?

@someilay you can't dataize test, it doesn't have @. In the first snippet you don't dataize it, you only dataize the write object, which returns TRUE

Job gh:cqfn/eo#498 is not assigned, can't get performer

repo: cqfn/eo


text:
chore(deps): update quay.io/mytestworkload/test-renovate-updates-task-coverage:0.1 docker digest to 8685edd

This PR contains the following updates:

Package
Type
Update
Change

quay.io/mytestworkload/test-renovate-updates-task-coverage
tekton-bundle
digest
415fcd8 -> 8685edd

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

⚠ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:
File name: component-a-pipelinerun-pr.yaml
Command failed: migration-tool.py -f quay.io/mytestworkload/test-renovate-updates-task-coverage:0.1@sha256:415fcd8e3eac18bd4bba678e4acb2437ecc9ee30f88d74cece1dfbced557ba6e -t quay.io/mytestworkload/test-renovate-updates-task-coverage:0.1@sha256:8685eddb6af6fd75a6f96d97a88cf2d9b83ec88f051fe5e4ba739fb3686dd392 -m manual -p component-a-pipelinerun-pr.yaml
INFO:build.log:2024-09-10 19:54:05,545:Doing migration for task update:
INFO:build.log:2024-09-10 19:54:05,545:from: quay.io/mytestworkload/test-renovate-updates-task-coverage:0.1@sha256:415fcd8e3eac18bd4bba678e4acb2437ecc9ee30f88d74cece1dfbced557ba6e
INFO:build.log:2024-09-10 19:54:05,545:to: quay.io/mytestworkload/test-renovate-updates-task-coverage:0.1@sha256:8685eddb6af6fd75a6f96d97a88cf2d9b83ec88f051fe5e4ba739fb3686dd392
DEBUG:build.log:2024-09-10 19:54:05,545:inspect image: quay.io/mytestworkload/test-renovate-updates-task-coverage:0.1@sha256:8685eddb6af6fd75a6f96d97a88cf2d9b83ec88f051fe5e4ba739fb3686dd392
INFO:migrate_per_task:2024-09-10 19:54:06,961:[{'name': '0.1-eb8ff062320d1c53e636d50e5a3e9ee119cfb362', 'reversion': False, 'start_ts': 1725969160, 'manifest_digest': 'sha256:8685eddb6af6fd75a6f96d97a88cf2d9b83ec88f051fe5e4ba739fb3686dd392', 'is_manifest_list': False, 'size': 339, 'last_modified': 'Tue, 10 Sep 2024 11:52:40 -0000'}, {'name': '0.1-95c412fc032c26323bfd1d5ef4332a6cc8fe72f1', 'reversion': False, 'start_ts': 1725930494, 'manifest_digest': 'sha256:415fcd8e3eac18bd4bba678e4acb2437ecc9ee30f88d74cece1dfbced557ba6e', 'is_manifest_list': False, 'size': 339, 'last_modified': 'Tue, 10 Sep 2024 01:08:14 -0000'}]
INFO:migrate_per_task:2024-09-10 19:54:10,987:discovered migration file ./tasks/migrations/task-coverage-0.1.2.sh
INFO:migrate_per_task:2024-09-10 19:54:14,920:discovered migration file ./tasks/migrations/task-coverage-0.1.3.sh
INFO:migrate_per_task:2024-09-10 19:54:14,947:apply migrations ./tasks/migrations/task-coverage-0.1.2.sh to /tmp/tmpx7yaq2ag-pipeline
INFO:migrate_per_task:2024-09-10 19:54:15,015:apply migrations ./tasks/migrations/task-coverage-0.1.3.sh to /tmp/tmpx7yaq2ag-pipeline
Error: parsing expression: Lexer error: could not match text starting at 1:40 failing at 1:43.
	unmatched text: "cov"
Traceback (most recent call last):
  File "/home/cqi/.local/bin/migration-tool.py", line 236, in <module>
    main()
  File "/home/cqi/.local/bin/migration-tool.py", line 224, in main
    migrate_per_task.migrate(args.from_task_bundle, args.to_task_bundle, args.pipeline_run_file)
  File "/home/cqi/code/konflux/test-renovate-updates/migrate_per_task.py", line 129, in migrate
    subprocess.run(["bash", migration_file, pipeline_file], check=True)
  File "/usr/lib64/python3.12/subprocess.py", line 571, in run
    raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['bash', './tasks/migrations/task-coverage-0.1.3.sh', '/tmp/tmpx7yaq2ag-pipeline']' returned non-zero exit status 1.


text:
#28 Implement SecurityConfig

In this PR I implemented SecurityConfig with security methods annotations and close #28

@rultor merge

@rultor merge

@ilisau Thanks for your request; @h1alexbel please confirm this.

@rultor merge

@rultor merge

@h1alexbel OK, I'll try to merge now. You can check the progress of the merge here

@rultor merge

@h1alexbel Done! FYI, the full log is here (took me 1min)

@ilisau thanks!

authors: h1alexbel ilisau rultor

repo: cqqqt/Task-Viewer-Backend


text:
Con4m default output needs to work around JSON limitations

Right now, if you do:
m = {1 : 2}
And run that at the command line, you'll get an error about the key needing to be a string, which comes when attempting to print JSON, since object keys cannot be numbers.
Right now, you can just use --pretty to see the output, but we need to decide which approach we should take for this:

Auto-cast keys to strings.
Covert them to associative arrays to preserve type info.
Disallow non-string keys.
Ignore it, but improve the error message and/or force --pretty.

Addressed in master.  Took door #1, also dealt with new types (in keys or values) that don't have a JSON mapping.


text:
declare utf-8 encoding in crash_standalone

see #138

lgtm

authors: chaudum mfussenegger

repo: crate/crash


text:
StaticInformationSchemaQueryTest.testIsNotNull test failure

CrateDB version
branches 5.6, 5.7, 5.8
CrateDB setup information
No response
Problem description
No response
Steps to Reproduce
https://github.com/crate/crate/pull/16423
or
./mvnw -pl server test -Dtest=io.crate.integrationtests.StaticInformationSchemaQueryTest -Dtests.method=testIsNotNull -Dtests.seed=B37AA2673C72CDDE -Dtests.locale=pt-AO -Dtests.timezone=America/Nome -Dtests.iters=20
Actual Result
org.elasticsearch.ElasticsearchTimeoutException: Timeout while running create table t2 (col1 integer, col2 string) clustered into 10 shards``
See also CI failure
https://jenkins.crate.io/job/CrateDB/job/crate_on_pr/16089/testReport/junit/io.crate.integrationtests/StaticInformationSchemaQueryTest/testIsNotNull/

Test is very simple, I think it’s rather related to a combination of number of shards = 10 and specific to the seed number of data nodes. There are 3 create table statements but it always timeouts only on …10 shard

it always timeouts only on statement with …10 shards

Saw another timeout on a different table today (different test case but timeout happens on Setup statements)
https://jenkins.crate.io/blue/rest/organizations/jenkins/pipelines/CrateDB/pipelines/crate_test_hourly_stable/runs/21820/log/?start=0
[ERROR] io.crate.integrationtests.StaticInformationSchemaQueryTest.testWhereOr2 -- Time elapsed: 20.89 s <<< ERROR!
org.elasticsearch.ElasticsearchTimeoutException: Timeout while running `create table t1 (col1 integer, col2 string) clustered into 7 shards`
	at __randomizedtesting.SeedInfo.seed([816DBAFB7FB92682:CAE8484812D71B5B]:0)

I've run the tests with 200 iterations and it didn't fail.
But I've recognized that the table creation takes a lot of time, which is suspicious as this is not expected.
I verified that this issue (slow table creation) is a master as running the test at previous release like 5.8 -> 5.6 result in expected fast table creation.
I'll dive into this to figure out what has caused this.

authors: BaurzhanSakhariev seut

repo: crate/crate


text:
Replace unsafe SQLDirectExecutor with a quickExec function

The SQLDirectExecutor wasn't thread-safe as it used the Session which by
design is stateful and not thread-safe.
This could cause the portals inside the Session to be promoted to a
BulkPortal which then caused regular Bulk operation not supported for RootRelationBoundary errors during queries on sys.checks.

Codecov Report

Merging #6902 into master will increase coverage by 0.1%.
The diff coverage is 74%.

@@             Coverage Diff             @@
##             master    #6902     +/-   ##
===========================================
+ Coverage     83.06%   83.17%   +0.1%
- Complexity    13276    13299     +23
===========================================
  Files          1527     1527
  Lines         49350    49375     +25
  Branches       5938     5940      +2
===========================================
+ Hits          40992    41067     +75
+ Misses         5573     5524     -49
+ Partials       2785     2784      -1

Impacted Files
Coverage Δ
Complexity Δ

.../main/java/io/crate/planner/TableStatsService.java
89.36% <100%> (+0.23%)
9 <0> (ø)
:arrow_down:

...otocols/postgres/RetryOnFailureResultReceiver.java
88.46% <100%> (ø)
10 <0> (ø)
:arrow_down:

...java/io/crate/protocols/postgres/SimplePortal.java
87.75% <100%> (ø)
29 <1> (ø)
:arrow_down:

...e/sys/check/cluster/TablesNeedUpgradeSysCheck.java
68.57% <100%> (+9.74%)
9 <3> (+3)
:arrow_up:

...c/main/java/io/crate/action/sql/SQLOperations.java
73.07% <100%> (-8.01%)
6 <1> (ø)

...va/io/crate/execution/ddl/AlterTableOperation.java
87.59% <100%> (+0.09%)
70 <2> (+2)
:arrow_up:

sql/src/main/java/io/crate/action/sql/Session.java
77.34% <58.06%> (-3.86%)
32 <2> (+2)

...va/io/crate/execution/ddl/RenameTableResponse.java
20% <0%> (-80%)
1% <0%> (-3%)

...ava/io/crate/execution/ddl/RenameTableRequest.java
50% <0%> (-41.67%)
6% <0%> (-2%)

...main/java/io/crate/breaker/ArraySizeEstimator.java
80% <0%> (-20%)
4% <0%> (-1%)

... and 31 more

Continue to review full report at Codecov.

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

authors: codecov-io mfussenegger


text:
Adding composer metadata

I would appreciate if you could add a composer.json file and submit your bundle to http://packagist.org :)

I never tried using this composer/packagist stuff, so I'm not familiar with it. Thus, I hope you made sure that this file is correct. ;)
What does "submit" mean? At least, I don't want to maintain another kind of repository there. Or is it just like registering the bundle?
One more thing: Would you use tab indentation in that file?

You just have to register the bundle at packagist.org - notice the big green "Submit Package" button.
Looks like the indentation is correct on that commit.

@breerly: That would also require to create an account over there, and I prefer tab indentation. ;)

I have an account for packagist.org if one is needed and I could submit the package if the PR gets merged.

@daFish: Thanks for offering that, but I think it's better to let me maintain it there. Created an account and will submit it then.

@kaiwa: Thanks for contributing.
There it is: http://packagist.org/packages/craue/formflow-bundle

@craue great, thanks for adding it! Seems to work.
I noticed one minor mistake i've made with the tags:
"symfony2" tag might be added and the existing form-related packages are using "form" - not "forms" as tag. I added a note to the line if you like to adjust this.

Done. :)

authors: breerly craue daFish kaiwa

repo: craue/CraueFormFlowBundle


text:
Extension request: gd on Windows

Not urgent, but wanted to get this on the list.
I don't have a Windows machine, but I have access to a free month of a Windows 365 cloud PC, so I can potentially poke around to do stuff.
(Though I would need some guidance)

Now we have full-feature gd support on Windows. After CI we can merge it. #484

authors: crazywhalecc simonhamp

repo: crazywhalecc/static-php-cli


text:
Fix image count when result set is over 10K images

There's been a change to the CC Catalog API in which a search query result set over 10.000 images will have a capped result_count of 10000, when in reality there's more than 10.000 images in the catalog.  For example: https://api.creativecommons.engineering/image/search?q=cat

We need to change the display of the image count in the UI, which now tells users that there are exactly 10.000 images, to something like Over 10.000 images or More than 10.000 images or 10.000+ images.

@annatuma which one do you think is best?
Over 10.000 images
More than 10.000 images
10.000+ images
Something else?

Assigned to @annatuma to respond.

Hi there, I'd love to work on this issue.

@madewithkode we're still deciding on the correct language here. Once we decide and we remove the Question label, you're welcome to work on this.

This is more complex than it looks because the thousands separator varies by country and region. (See examples. This is an opportunity to fix our previous styling with the thousands separator.
I suggest we go with the SI style, and refer to "results" rather than "images":
Suggested language: Over 10 000 results
We are only showing the first 10 000 results in these cases, correct?
@kgodey @brenoferreira let me know what you think of the suggested language.

sounds good to me.

Actually, since we're not localized yet and we use American English, maybe we should stick to the English separators since the rest of the UI is in English? Once we localize, we can support other separators based on the language of the UI. That seems most consistent to me.

@madewithkode we're still deciding on the correct language here. Once we decide and we remove the Question label, you're welcome to work on this.

@brenoferreira Alright. Looking forward to the final decision.

Yeah, since nothing is localised in CC Search, it's all American English, including numbers, I would say that it's not worth worrying about that at the moment. If we use , to separate decimals, let's continue using that and keep this ticket focused on the text for the result set over 10K images.
PS: There's already a ticket about localization, which should include localized numbers in CC Search: #487

All valid points. Decimal separator it is, in keeping with American English conventions.
"Over 10,000 results" will be the new text then!
@madewithkode I believe this is ready to be worked on now.

@madewithkode marked as "in progress" assuming you're still interested in working on it.

on it!
On Thu, Dec 19, 2019, 22:54 Anna T. notifications@github.com wrote:

Assigned #540
https://github.com/creativecommons/cccatalog-frontend/issues/540 to
@madewithkode https://github.com/madewithkode.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/creativecommons/cccatalog-frontend/issues/540?email_source=notifications&email_token=AGFLMYCDIQL6DVOBLYP5S4TQZPUPXA5CNFSM4JVI5CL2YY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOVTEKX2Y#event-2898832363,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGFLMYDOPD6Q5FTVWH2SE2LQZPUPXANCNFSM4JVI5CLQ
.

Was away for a while, currently on it.
On Wed, Dec 18, 2019, 01:34 Kriti Godey notifications@github.com wrote:

@madewithkode https://github.com/madewithkode marked as "in progress"
assuming you're still interested in working on it.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/creativecommons/cccatalog-frontend/issues/540?email_source=notifications&email_token=AGFLMYAKAPH7H2TY2N2AQUDQZFVY7A5CNFSM4JVI5CL2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHEN7TA#issuecomment-566812620,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGFLMYEW2DHSBUMJ5SFDCZDQZFVY7ANCNFSM4JVI5CLQ
.

Hey there, just so I'm cleared, I hope we all know that results below 10k currently appear as " images" where  equals the number of fetched images.
So if we're going to change the phrase for results over 10K to "Over 10,000 results" don't you think in pursuit of homogeneity, it's either "images" is entirely replaced with "results" or the latter replaces the former for results below 10K too.
Looking forward to your feedbacks before I proceed.

Good catch. I think we should keep it as Over 10,000 images for now

authors: annatuma brenoferreira kgodey madewithkode

repo: creativecommons/cccatalog-frontend


text:
Fonts: font-medium doesn't work when installing and configuring material-tailwind in my application

Hi 👋
I have an application using Next 13 with app directory, and before installing material-tailwind all my fonts and colors were working normally. After installing the library I noticed in the browser that font-normal and font-medium stopped differentiating.
before installation

after installation

my tailwind.config.js
/** @type {import('tailwindcss').Config} */
const withMT = require('@material-tailwind/react/utils/withMT')

module.exports = withMT({
  content: [
    './src/pages/**/*.{js,ts,jsx,tsx,mdx}',
    './src/components/**/*.{js,ts,jsx,tsx,mdx}',
    './src/app/**/*.{js,ts,jsx,tsx,mdx}',
  ],
  theme: {
    fontFamily: {
      sans: ['Open Sans', 'sans-serif'],
    },
    extend: {
      backgroundColor: {
        radio: '#DCDCDC',
      },
      colors: {
        'white-50': '#FCFCFC',
        'white-100': '#F4F4F4',
        'white-300': '#E8E8E8',
        'black-300': '#545454',
        'red-light': '#E8C5C2',
        'red-dark': '#88322B',
      },
    },
  },
  daisyui: {
    themes: [
      {
        mytheme: {
          primary: '#B5433A',
          'base-100': '#FCFCFC',
          success: '#56AB5E',
        },
      },
    ],
    styled: true,
    base: true,
    utils: true,
    logs: true,
    rtl: false,
    prefix: '',
    darkTheme: 'dark',
  },
  plugins: [require('daisyui')],
})

All help is welcome 👋

up!

I had this problem and solved it by using Googles Instructions to add the font to my app:
https://fonts.google.com/knowledge/using_type/using_web_fonts_from_a_font_delivery_service
And made sure that the URL is requesting the relevant weights. For example:
https://fonts.googleapis.com/css2?family=Roboto:wght@400;500;700&display=swap
I don't know exactly which weights Material Tailwind uses, but I think medium is usually 500.

authors: AKK9 jovemdan namevug

repo: creativetimofficial/material-tailwind


text:
design file

Hello I have purchased Vue UI Kit Professional Edition before
I thought I bought the design file, but no
Can I purchase design files separately?

Hi, @ChaBen! Thank you for using our products. Unfortunately, the designer files come with the product only if you bought the product with the startup license and above.
Regards,
Dragos

repo: creativetimofficial/vue-now-ui-kit


text:
Data assess reporting

Created dataset assessment visualization and reporting and embedded in Lens

I don't quite know how to visualize the overall proxy score as it is just one number and also adding it to any of the current plots could become misleading. Seems to better be accommodated through extending pdf generators to display text/tables too.

I'd put it as one large number. I think standard text can work for this. But I think we can talk about this within the broader context of "executive summary" section of our reports - with big numbers reflecting things and won't block this merge

authors: IanAtCredo amrasekh


text:
unproper layout on mobile view

Hello,
I got an unproper layout on mobile view while using Customizer plugin.
The board view on mobile is taking like 30% to 50% of view port width.
Chrome inspector is reporting that html/body are 414px width. I can't figure out what's causing the vertical white space.
I tried with an uploaded CSS theme file to force html/body width:100vw!important, but it didnt fixed the issue.
App/Plugin version used to reproduce the issue:

kanboard v1.2.18/Customizer v1.13.6 (production)
kanboard v1.2.20/Customizer v1.13.7 (test)

Devices/Browsers used to reproduce the issue:

Samsung Galaxy S8/Chrome browser
Samsung Galaxy S8/Samsung Internet browser
Emulated mobile (dev tools)/Chrome browser

Here are screenshots to illustrate the issue.
I've colored background on the fly using chrome dev tools for more visibility.

html {background-color: red;}
body {background-color: aqua;}

Screenshot without Customizer:

Screenshot with Customizer:

Hi, I was off of kanboard for a while.
Today I played a bit with the customizer overriding layout.php
I fixed the issue by editing (at the head tag) the following line:
<meta name="viewport" content="width=device-width">
by:
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no">
I hope this can help others. And thanks @creecros for the hint!

thanks, I see @creecros implemented this, and it is included is 1.13.8 now: https://github.com/creecros/Customizer/commit/96ad9a6972ab176b8390969978c0c8ce127c59f2

repo: creecros/Customizer


text:
adds balanced accuracy score

I also need to figure out how to use correction in BalancedAccuracy so as to make the metric similar to adjusted in scikit-learn.

LGTM! Good work :)

LGTM! Good work :)

Thanks :)

authors: MaxHalford sinAshish

repo: creme-ml/creme