text:
ERROR MESSAGE: An error occurred: does not match pattern "A-Z Version 1.1.1

Hello,
in 1.1.1, i have this error message when clicking on NEXT on the filling page.

Anyone has this issue?

I also get this message while opening:

shows your installation process

@francoborgia was that a question? Dependencies are correctly installed anyway

Hello, in 1.1.1, i have this error message when clicking on NEXT on the filling page.  Anyone has this issue?

weren't you too stucked on pending page? how did you get to filling page?

@Swordly81 Downgraded to 1.1.1. But isn't working too

@Alesgubbi Damn... i'm not into theese kind of things. may i ask how to downgrade? and maybe ask why i see
version 0.1.0 any time i start the project?

To be honest is really OT. I want to resolve my problems, not yours. Use the search bar

Hello, in 1.1.1, i have this error message when clicking on NEXT on the filling page.  Anyone has this issue?
Hi I saw these

in components/record-vaccination-cert-data.component.js
you can find in the line 143 "issuerCountryCode"
const vacc: VaccinationEntry = {                 tg: disease,                 vp: vaccine,                 mp: medicalProduct,                 ma: marketingHolder,                 dn: doseNumber,                 sd: totalDoseNumber,                 dt: vacLastDate!.toISOString().split('T')[0],                 co: issuerCountryCode,                 is: certificateIssuer,                 ci: ''             };
any time when you submit this be empty and that will be "IT" in case of ITALY , can't be empty try to modify it or fill it in another way

how to fix?

anyone has a solution?

anyone has a solution?

try this before to run it
yarn install
yarn start

I also get this message while opening:

If you check with the debug page (CTRL+SHIFT+I inside browser) it could be related to a GET http://localhost:3000/dgca-businessrule-service/valuesets. This is a problem already reported in other thread and no solution posted yet.

Hello, in 1.1.1, i have this error message when clicking on NEXT on the filling page.  Anyone has this issue?
Hi I saw these

in components/record-vaccination-cert-data.component.js
you can find in the line 143 "issuerCountryCode"
const vacc: VaccinationEntry = { tg: disease, vp: vaccine, mp: medicalProduct, ma: marketingHolder, dn: doseNumber, sd: totalDoseNumber, dt: vacLastDate!.toISOString().split('T')[0], co: issuerCountryCode, is: certificateIssuer, ci: '' }; any time when you submit this be empty and that will be "IT" in case of ITALY , can't be empty try to modify it or fill it in another way

how is it empty? i mean where should you write the country code in line 143?

Hello, in 1.1.1, i have this error message when clicking on NEXT on the filling page.  Anyone has this issue?

same issue here, don't know how to solve

Same problem ... first error 431, after I fill out the forms error message: does not match pattern "[A-Z]{1,10}"
Has anyone solved it?

I have the same problem.
I have install dca with npm, node versione 14.18.1
i have tried to modify the pattern in schema json, but when i clicked  next the sistem returned an error 431.

Ciao a tutti, dopo 72h full-immersion ho compilato tutto con diverse versioni (1.0.10 la migliore) "nodejs" "npm" ecc ho eseguito il docker ho creato l'anteprima del QR ....... incrocio le dita ..... apro Verifica C19  = MURO (la firma digitale non è valida) .
avranno già revocato la chiave privata , inoltre gli ID sono processati tutti come DE "tedeschi" ... spero che la mia testimonianza sia utile a molti

Ciao a tutti, dopo 72h full-immersion ho compilato tutto con diverse versioni (1.0.10 la migliore) "nodejs" "npm" ecc ho eseguito il docker ho creato l'anteprima del QR ....... incrocio le dita ..... apro Verifica C19  = MURO (la firma digitale non è valida) .
avranno già revocato la chiave privata , inoltre gli ID sono processati tutti come DE "tedeschi" ... spero che la mia testimonianza sia utile a molti

Peccato, ci speravo davvero! Se ti va apri un topic e spiegaci cosa hai fatto, sarebbe comunque interessante

Ciao,
Se ci spieghi cosa hai fatto grazie mille.

@b1tsh4rk grazie comunque, ma sai che ti dico? Sarebbe stato comunque solo un palliativo momentaneo... Questa è una guerra che dobbiamo vincere su altri fronti. Specialmente in Italia

@b1tsh4rk grazie comunque, ma sai che ti dico? Sarebbe stato solo un palliativo momentaneo... Questa è una guerra che dobbiamo vincere su altri fronti. Specialmente in Italia

Ti do ragione, ma per il mio lavoro devo avere per forza il GP quindi a suon di tamponi ogni 2 giorni mi viene la sinusite. Comunque sono convinto che se restiamo uniti ce la faremo

Ciao a tutti, dopo 72h full-immersion ho compilato tutto con diverse versioni (1.0.10 la migliore) "nodejs" "npm" ecc ho eseguito il docker ho creato l'anteprima del QR ....... incrocio le dita ..... apro Verifica C19  = MURO (la firma digitale non è valida) .
avranno già revocato la chiave privata , inoltre gli ID sono processati tutti come DE "tedeschi" ... spero che la mia testimonianza sia utile a molti

Grazie comunque per lo sforzo Bro! Dai che vinceremo questa guerra !

Ciao a tutti, dopo 72h full-immersion ho compilato tutto con diverse versioni (1.0.10 la migliore) "nodejs" "npm" ecc ho eseguito il docker ho creato l'anteprima del QR ....... incrocio le dita ..... apro Verifica C19 = MURO (la firma digitale non è valida) . avranno già revocato la chiave privata , inoltre gli ID sono processati tutti come DE "tedeschi" ... spero che la mia testimonianza sia utile a molti

Ti faccio una domanda a mero scopo intrattenitorio: come sei riuscito ad ovviare all'errore 431? A me anche con la 1.0.10 non mi fa andare oltre alla pagina "NEXT".

Ciao a tutti, dopo 72h full-immersion ho compilato tutto con diverse versioni (1.0.10 la migliore) "nodejs" "npm" ecc ho eseguito il docker ho creato l'anteprima del QR ....... incrocio le dita ..... apro Verifica C19 = MURO (la firma digitale non è valida) . avranno già revocato la chiave privata , inoltre gli ID sono processati tutti come DE "tedeschi" ... spero che la mia testimonianza sia utile a molti

Non possono revocare la chiave, pena l'invalidazione di tutti i certificati emessi fino ad ora.
Inoltre è gp è fatto per essere "locale", cioè che deve funzionare anche senza connettività

Ciao a tutti, dopo 72h full-immersion ho compilato tutto con diverse versioni (1.0.10 la migliore) "nodejs" "npm" ecc ho eseguito il docker ho creato l'anteprima del QR ....... incrocio le dita ..... apro Verifica C19 = MURO (la firma digitale non è valida) . avranno già revocato la chiave privata , inoltre gli ID sono processati tutti come DE "tedeschi" ... spero che la mia testimonianza sia utile a molti

Non possono revocare la chiave, pena l'invalidazione di tutti i certificati emessi fino ad ora. Inoltre è gp è fatto per essere "locale", cioè che deve funzionare anche senza connettività

Infatti quelli generati con Adolf H sono ancora attivi non hanno revocato nulla.

Ciao a tutti, dopo 72h full-immersion ho compilato tutto con diverse versioni (1.0.10 la migliore) "nodejs" "npm" ecc ho eseguito il docker ho creato l'anteprima del QR ....... incrocio le dita ..... apro Verifica C19 = MURO (la firma digitale non è valida) . avranno già revocato la chiave privata , inoltre gli ID sono processati tutti come DE "tedeschi" ... spero che la mia testimonianza sia utile a molti

Non possono revocare la chiave, pena l'invalidazione di tutti i certificati emessi fino ad ora. Inoltre è gp è fatto per essere "locale", cioè che deve funzionare anche senza connettività

Infatti quelli generati con Adolf H sono ancora attivi non hanno revocato nulla.

In realtà ho ricontrollato ora, e sono stati invalidati sia quello di Hitler che quello di Mickey Mouse. L'unico che non hanno invalidato è quello di Macron.
Temo che abbiano rimesso i buoi nella stalla.

Ciao a tutti, dopo 72h full-immersion ho compilato tutto con diverse versioni (1.0.10 la migliore) "nodejs" "npm" ecc ho eseguito il docker ho creato l'anteprima del QR ....... incrocio le dita ..... apro Verifica C19 = MURO (la firma digitale non è valida) . avranno già revocato la chiave privata , inoltre gli ID sono processati tutti come DE "tedeschi" ... spero che la mia testimonianza sia utile a molti

Non possono revocare la chiave, pena l'invalidazione di tutti i certificati emessi fino ad ora. Inoltre è gp è fatto per essere "locale", cioè che deve funzionare anche senza connettività

Infatti quelli generati con Adolf H sono ancora attivi non hanno revocato nulla.

Ottimo, oggi mi ci dedico ... il primo che c'è la fa magari si fa un gruppo privato

io non sono riuscito a generare il qr ancora

Ciao a tutti, dopo 72h full-immersion ho compilato tutto con diverse versioni (1.0.10 la migliore) "nodejs" "npm" ecc ho eseguito il docker ho creato l'anteprima del QR ....... incrocio le dita ..... apro Verifica C19 = MURO (la firma digitale non è valida) . avranno già revocato la chiave privata , inoltre gli ID sono processati tutti come DE "tedeschi" ... spero che la mia testimonianza sia utile a molti

Non possono revocare la chiave, pena l'invalidazione di tutti i certificati emessi fino ad ora. Inoltre è gp è fatto per essere "locale", cioè che deve funzionare anche senza connettività

Infatti quelli generati con Adolf H sono ancora attivi non hanno revocato nulla.

In realtà ho ricontrollato ora, e sono stati invalidati sia quello di Hitler che quello di Mickey Mouse. L'unico che non hanno invalidato è quello di Macron. Temo che abbiano rimesso i buoi nella stalla. La domanda però sorge spontanea: hanno annullato tutti i GP generati dalla chiave X dopo una certa data (in cui suppongono sia stata trafugata) oppure hanno manualmente rimosso i due GP in quanto palesemente falsi? nella seconda ipotesi, non sarebbe un grosso problema. Nella prima si

secondo me hanno tolto quelli palesemente falsi

a me da questo errore nella generazione del qr Versione 1.0.10

a me da questo errore nella generazione del qr Versione 1.0.10

Ti ha mai dato l'errore 431?

a me da questo errore nella generazione del qr Versione 1.0.10

Ti ha mai dato l'errore 431?

no mai solo questo errore all'anteprima del QR

Ho installato la versione 1.0.10, node 14.15.0 yarn 1.22.17, npm 8.1.2 (cambiato anche il file localhost:8080 a 3000 su package.json) ad ora mi carica tutto senza darmi errori iniziali.
Compilo i vari form e quando clicco su next, per generare il qr, esce fuori l'errore 431...oggi smanetto un pò cercando di provare con varie versioni. @b1tsh4rk riesci a dirci come hai settato il tutto? grazie...vedrete che ce la faremo!

Ho installato la versione 1.0.10, node 14.15.0 yarn 1.22.17, npm 8.1.2 (cambiato anche il file localhost:8080 a 3000 su package.json) ad ora mi carica tutto senza darmi errori iniziali. Compilo i vari form e quando clicco su next, per generare il qr, esce fuori l'errore 431...oggi smanetto un pò cercando di provare con varie versioni. @b1tsh4rk riesci a dirci come hai settato il tutto? grazie...vedrete che ce la faremo!

L'errore 431 sono riuscito a bypassarlo con questa linea di codice alla riga 62 del package.json
"start": "react-scripts --max-http-header-size 1200000 start",
Ora però mi si presenta un errore di connessione. Lo allego qui

Ho installato la versione 1.0.10, node 14.15.0 yarn 1.22.17, npm 8.1.2 (cambiato anche il file localhost:8080 a 3000 su package.json) ad ora mi carica tutto senza darmi errori iniziali. Compilo i vari form e quando clicco su next, per generare il qr, esce fuori l'errore 431...oggi smanetto un pò cercando di provare con varie versioni. @b1tsh4rk riesci a dirci come hai settato il tutto? grazie...vedrete che ce la faremo!

Stessa identica situazione... nel terminlae mi esce scritto:
Compiled with warnings.
src/components/pdf-generater.component.tsx
Line 464:25:   'space' is assigned a value but never used                   @typescript-eslint/no-unused-vars
Line 1070:11:  'printAsTableRow' is assigned a value but never used         @typescript-eslint/no-unused-vars
Line 1163:11:  'printAsTableRowRotated' is assigned a value but never used  @typescript-eslint/no-unused-vars
Line 1316:48:  The array literal notation [] is preferable                  @typescript-eslint/no-array-constructor
Search for the keywords to learn more about each warning.
To ignore, add // eslint-disable-next-line to the line before.

Ho installato la versione 1.0.10, node 14.15.0 yarn 1.22.17, npm 8.1.2 (cambiato anche il file localhost:8080 a 3000 su package.json) ad ora mi carica tutto senza darmi errori iniziali. Compilo i vari form e quando clicco su next, per generare il qr, esce fuori l'errore 431...oggi smanetto un pò cercando di provare con varie versioni. @b1tsh4rk riesci a dirci come hai settato il tutto? grazie...vedrete che ce la faremo!

Stessa identica situazione... nel terminlae mi esce scritto:
Compiled with warnings.
src/components/pdf-generater.component.tsx Line 464:25: 'space' is assigned a value but never used @typescript-eslint/no-unused-vars Line 1070:11: 'printAsTableRow' is assigned a value but never used @typescript-eslint/no-unused-vars Line 1163:11: 'printAsTableRowRotated' is assigned a value but never used @typescript-eslint/no-unused-vars Line 1316:48: The array literal notation [] is preferable @typescript-eslint/no-array-constructor
Search for the keywords to learn more about each warning. To ignore, add // eslint-disable-next-line to the line before.

io ho lo stesso messaggio

Ciao.  non ho il file src/components/pdf-generater.component.tsx. inesistente.
riesco a entrare nel form ma dopo aver inserito i dati e cliccato next mi da errore:
ERROR MESSAGE: An error occurred: does not match pattern "[A-Z]{1,10}"
non sono sicuro di cosa debba essere inserito nel campo --> Certificate Issuer*

da GP risulterebbe che Certificate Issuer* è: Ministero della salute
ma credo possa essere un'altra la voce da inserire

Ciao. non ho il file src/components/pdf-generater.component.tsx. inesistente. riesco a entrare nel form ma dopo aver inserito i dati e cliccato next mi da errore: ERROR MESSAGE: An error occurred: does not match pattern "[A-Z]{1,10}" non sono sicuro di cosa debba essere inserito nel campo --> Certificate Issuer*

Ti consiglio di usare una versione precedente, tipo la 1.0.10 . E' quella più promettente, anche se ancora non siamo riusciti a farla funzionare.

cosa hai inserito in Certificate Issuer*  ?

sto usando la 1.1.1

cosa hai inserito in Certificate Issuer* ?

Niente, la versione 1.0.10 ha il form di inserimento e basta selezionarlo dalla lista. Prova con "IT" comunque

stesso errore

stesso errore

lascia perdere la 1.1.1, scarica la 1.0.10 che funziona tutto alla perfezione.
Rimane solo da risolvere un problema di connessione che impedisce la generazione del QR. Potrebbe anche dipendere dal server ricevente, e li però non ci fai nulla. però stiamo tentando

mi da lo stesso errore anche con la 1.0.10

we all love italian and all, but can you write in english please ? so we can all understand, thank you !

we all love italian and all, but can you write in english please ? so we can all understand, thank you !

It's not working. We are trying to figure it out why, but IDK

I've tried 1.1.1 and 1.0.10
both gave me error after filled the form and click to next:
ERROR MESSAGE: An error occurred: does not match pattern "[A-Z]{1,10}"

yes, but at least with the version 1.0.10 i have the UI to enter data, but i have the same 431 error

i have the UI to enter data even in 1.1.1

lucky you, i have just the spinning circle in 1.1.1 version

are you using yarn?

yep

I use serve -s build
(npm)

with yarn I got the same

what was the command again with npm please ?

npm start

no luck with the last version, i think i'm gonna stick with the 1.0.10

you can try:
npm run build
...
serve -s build
-->  it will open localhost:5000
so you have to change at line 61 package.json to 5000

Ciao. non ho il file src/components/pdf-generater.component.tsx. inesistente. riesco a entrare nel form ma dopo aver inserito i dati e cliccato next mi da errore: ERROR MESSAGE: An error occurred: does not match pattern "[A-Z]{1,10}" non sono sicuro di cosa debba essere inserito nel campo --> Certificate Issuer*

Va inserito il codice iso 3166 alpha-2 che per L'italia corrisponde a IT, comunque sia puoi eliminare il pattern nel file json e premere next, ma esce fuori un errore con spinner in loop

Hello everyone ! I follow this tread very carefully! for me version 1.0.10 everything seems to work except that i have a 500 error while validating the qr code. the other versions have given me other more serious errors. are the node and yarn version really important?

Hello, in 1.1.1, i have this error message when clicking on NEXT on the filling page.  Anyone has this issue?

same issue here, don't know how to solve

Buon giorno a tutti qualcuno è riuscito a risolvere il problema del certificate issuae?

Actually in version 1.0.10 after filling the form and click next I get
Error Message
An error occured: First argument must be a string, Buffer, ArrayBuffer, Array, or array-like object.
any idea how to fix it?

Hello, in 1.1.1, i have this error message when clicking on NEXT on the filling page.  Anyone has this issue?

same issue here, don't know how to solve

Buon giorno a tutti qualcuno è riuscito a risolvere il problema del certificate issuae?

Prova a mettere CNAM

A te funziona?

Hello, in 1.1.1, i have this error message when clicking on NEXT on the filling page.  Anyone has this issue?

same issue here, don't know how to solve

Buon giorno a tutti qualcuno è riuscito a risolvere il problema del certificate issuae?

Prova a mettere CNAM

A te funziona?

No io sto provando con la versione 1.0.10

No io sto provando con la versione 1.0.10

E ha problemi anche quella?

No io sto provando con la versione 1.0.10

E ha problemi anche quella?

Si nella generazione del pdf

No io sto provando con la versione 1.0.10

E ha problemi anche quella?

Si nella generazione del pdf

Ma qualcuno è mai riuscito a farlo girare??

No io sto provando con la versione 1.0.10

E ha problemi anche quella?

Si nella generazione del pdf

Ma qualcuno è mai riuscito a farlo girare??

Non lo so

Hello, in 1.1.1, i have this error message when clicking on NEXT on the filling page.  Anyone has this issue?

same issue here, don't know how to solve

Buon giorno a tutti qualcuno è riuscito a risolvere il problema del certificate issuae?

Prova a mettere CNAM

A te funziona?

Hai un link di questo cnam? Non lo ho mai sentito

Ciao a tutti, dopo 72h full-immersion ho compilato tutto con diverse versioni (1.0.10 la migliore) "nodejs" "npm" ecc ho eseguito il docker ho creato l'anteprima del QR ....... incrocio le dita ..... apro Verifica C19 = MURO (la firma digitale non è valida) . avranno già revocato la chiave privata , inoltre gli ID sono processati tutti come DE "tedeschi" ... spero che la mia testimonianza sia utile a molti

@b1tsh4rk
Hai notato che un "tizio" il 29 Ottobre, ha modificato alcuni files ?
Che strano.... che tempismo...
E proprio quelli relativi alla password.
dgca-issuance-web/nginx/default.conf.template (Removed Standard Passwordfile)
dgca-issuance-web/Dockerfile  (Removed Standard Passwordfile)
nginx/.htpasswd  (dgca-user:$apr1$p/TIVIAC$UPG8QZSTcVd/iJ6AhzEX5/)
Hai provato a re-inserire le righe rimosse, ed il file .htpassword ?

Ciao a tutti, dopo 72h full-immersion ho compilato tutto con diverse versioni (1.0.10 la migliore) "nodejs" "npm" ecc ho eseguito il docker ho creato l'anteprima del QR ....... incrocio le dita ..... apro Verifica C19 = MURO (la firma digitale non è valida) . avranno già revocato la chiave privata , inoltre gli ID sono processati tutti come DE "tedeschi" ... spero che la mia testimonianza sia utile a molti

@b1tsh4rk Hai notato che un "tizio" il 29 Ottobre, ha modificato alcuni files ? Che strano.... che tempismo... E proprio quelli relativi alla password. dgca-issuance-web/nginx/default.conf.template (Removed Standard Passwordfile) dgca-issuance-web/Dockerfile (Removed Standard Passwordfile) nginx/.htpasswd (dgca-user:$apr1$p/TIVIAC$UPG8QZSTcVd/iJ6AhzEX5/)
Hai provato a re-inserire le righe rimosse, ed il file .htpassword ?

Cioè? spiegati meglio

Ciao a tutti, dopo 72h full-immersion ho compilato tutto con diverse versioni (1.0.10 la migliore) "nodejs" "npm" ecc ho eseguito il docker ho creato l'anteprima del QR ....... incrocio le dita ..... apro Verifica C19 = MURO (la firma digitale non è valida) . avranno già revocato la chiave privata , inoltre gli ID sono processati tutti come DE "tedeschi" ... spero che la mia testimonianza sia utile a molti

@b1tsh4rk Hai notato che un "tizio" il 29 Ottobre, ha modificato alcuni files ? Che strano.... che tempismo... E proprio quelli relativi alla password. dgca-issuance-web/nginx/default.conf.template (Removed Standard Passwordfile) dgca-issuance-web/Dockerfile (Removed Standard Passwordfile) nginx/.htpasswd (dgca-user:$apr1$p/TIVIAC$UPG8QZSTcVd/iJ6AhzEX5/)
Hai provato a re-inserire le righe rimosse, ed il file .htpassword ?

Cioè? spiegati meglio

Ciao a tutti, dopo 72h full-immersion ho compilato tutto con diverse versioni (1.0.10 la migliore) "nodejs" "npm" ecc ho eseguito il docker ho creato l'anteprima del QR ....... incrocio le dita ..... apro Verifica C19 = MURO (la firma digitale non è valida) . avranno già revocato la chiave privata , inoltre gli ID sono processati tutti come DE "tedeschi" ... spero che la mia testimonianza sia utile a molti

@b1tsh4rk Hai notato che un "tizio" il 29 Ottobre, ha modificato alcuni files ? Che strano.... che tempismo... E proprio quelli relativi alla password. dgca-issuance-web/nginx/default.conf.template (Removed Standard Passwordfile) dgca-issuance-web/Dockerfile (Removed Standard Passwordfile) nginx/.htpasswd (dgca-user:$apr1$p/TIVIAC$UPG8QZSTcVd/iJ6AhzEX5/)

Hai provato a re-inserire le righe rimosse, ed il file .htpassword ?

Cioè? spiegati meglio

Curioso in effetti.
Pero non si spiega perché anche nelle versioni più obsolete non funzioni. Anche perché gli zip delle versioni vecchie non sono toccate da mesi

Sono dell'idea che tutto questo non funzioni, oppure sono stati lasciati volutamente degli errori. In modo di non farlo usare a cani e porci.. Alcuni DEV ragionano così..

Ciao a tutti, dopo 72h full-immersion ho compilato tutto con diverse versioni (1.0.10 la migliore) "nodejs" "npm" ecc ho eseguito il docker ho creato l'anteprima del QR ....... incrocio le dita ..... apro Verifica C19 = MURO (la firma digitale non è valida) . avranno già revocato la chiave privata , inoltre gli ID sono processati tutti come DE "tedeschi" ... spero che la mia testimonianza sia utile a molti

@b1tsh4rk Hai notato che un "tizio" il 29 Ottobre, ha modificato alcuni files ? Che strano.... che tempismo... E proprio quelli relativi alla password. dgca-issuance-web/nginx/default.conf.template (Removed Standard Passwordfile) dgca-issuance-web/Dockerfile (Removed Standard Passwordfile) nginx/.htpasswd (dgca-user:$apr1$p/TIVIAC$UPG8QZSTcVd/iJ6AhzEX5/)
Hai provato a re-inserire le righe rimosse, ed il file .htpassword ?

Cioè? spiegati meglio

Questo tizio nell'ultima revisione ha rimosso 2 righe dal file
dgca-issuance-web/nginx/default.conf.template
Poi ha fatto altrettanto nel file
dgca-issuance-web/Dockerfile
E poi ha cancellato il file  .htpasswd dalla cartella dgca-issuance-web/nginx/
PS il file .htpassword puoi crearlo rapidamente, perche' conteneva solo questa riga
dgca-user:$apr1$p/TIVIAC$UPG8QZSTcVd/iJ6AhzEX5/

Sono dell'idea che tutto questo non funzioni, oppure sono stati lasciati volutamente degli errori. In modo di non farlo usare a cani e porci.. Alcuni DEV ragionano così..

Ma non si spiega perché il 29 Ottobre è intervenuto qualcuno a cancellare proprio i riferimenti alla password.
Appena qualche giorno dopo che la bolla è scoppiata sui media.
Se il repository contiene file che non funzionano, tanto valeva lasciare tutto al suo posto.

Ciao a tutti, dopo 72h full-immersion ho compilato tutto con diverse versioni (1.0.10 la migliore) "nodejs" "npm" ecc ho eseguito il docker ho creato l'anteprima del QR ....... incrocio le dita ..... apro Verifica C19 = MURO (la firma digitale non è valida) . avranno già revocato la chiave privata , inoltre gli ID sono processati tutti come DE "tedeschi" ... spero che la mia testimonianza sia utile a molti

@b1tsh4rk Hai notato che un "tizio" il 29 Ottobre, ha modificato alcuni files ? Che strano.... che tempismo... E proprio quelli relativi alla password. dgca-issuance-web/nginx/default.conf.template (Removed Standard Passwordfile) dgca-issuance-web/Dockerfile (Removed Standard Passwordfile) nginx/.htpasswd (dgca-user:$apr1$p/TIVIAC$UPG8QZSTcVd/iJ6AhzEX5/)
Hai provato a re-inserire le righe rimosse, ed il file .htpassword ?

Cioè? spiegati meglio

Questo tizio nell'ultima revisione ha rimosso 2 righe dal file dgca-issuance-web/nginx/default.conf.template
Poi ha fatto altrettanto nel file dgca-issuance-web/Dockerfile
E poi ha cancellato il file .htpasswd dalla cartella dgca-issuance-web/nginx/
PS il file .htpassword puoi crearlo rapidamente, perche' conteneva solo questa riga dgca-user:$apr1$p/TIVIAC$UPG8QZSTcVd/iJ6AhzEX5/

Ho fatto, ma ancora non funziona. Temo il problema sia altrove sai...

@ABC010101 puoi spiegare il passaggio di gitignore? Mi sfugge

Hello, in 1.1.1, i have this error message when clicking on NEXT on the filling page.  Anyone has this issue?

same issue here, don't know how to solve

Buon giorno a tutti qualcuno è riuscito a risolvere il problema del certificate issuae?

Prova a mettere CNAM

A te funziona?

Hai un link di questo cnam? Non lo ho mai sentito

questo si risolve facile dal debugger del browser... ti metti in debug qua e gli passi eudgc.v[0].co = 'IT' ma poi ho un errore

ho un errore di An error occured: Request failed with status code 500 quando invia la richiesta...

Magari sbaglio, ma non è che manca la parte di "back-end" che risponde alla chiamata dgca-issuance-service ? https://github.com/eu-digital-green-certificates/dgca-issuance-service

Magari sbaglio, ma non è che manca la parte di "back-end" che risponde alla chiamata dgca-issuance-service ? https://github.com/eu-digital-green-certificates/dgca-issuance-service

Giusto!
Vedete qui: https://github.com/eu-digital-green-certificates/dgca-issuance-service/blob/main/docs/configuration.md

Ho installato la versione 1.0.10, node 14.15.0 yarn 1.22.17, npm 8.1.2 (cambiato anche il file localhost:8080 a 3000 su package.json) ad ora mi carica tutto senza darmi errori iniziali. Compilo i vari form e quando clicco su next, per generare il qr, esce fuori l'errore 431...oggi smanetto un pò cercando di provare con varie versioni. @b1tsh4rk riesci a dirci come hai settato il tutto? grazie...vedrete che ce la faremo!

L'errore 431 sono riuscito a bypassarlo con questa linea di codice alla riga 62 del package.json "start": "react-scripts --max-http-header-size 1200000 start",
Ora però mi si presenta un errore di connessione. Lo allego qui

Stessa cosa avevo pensato anche ad incrementare http-header-size ma niente, hai risolto in altro modo?

mi da ancora errore a-z 1,10 con la 1.1.1. . trovato qualche rimedio?

Magari sbaglio, ma non è che manca la parte di "back-end" che risponde alla chiamata dgca-issuance-service ? https://github.com/eu-digital-green-certificates/dgca-issuance-service

io ci sono riuscito e fatto, vi spiego il passaggio
vi scaricate la versione 1.0.10
poi aprite il pompt dei comandi
entrate nella cartella del progetto
cd <nome-progetto>
una volta dentro , assicuratevi di avere docker installato, altrimenti scaricatelo
una volta installato docker il passaggio successivo sarà quello di creare VM con docker
quindi digiterete questo:
docker-compose up -d
aspettate un pò perché vi dovrà scaricare tutta la roba sul container virtuale che vi creerà.
una volta fatto questo aprite la dashaboard di docker e andate su Containers/APP
lì troverete un contenitore chiamato dgca-issuance-web-1010
se siete arrivati fin qui ... bene! siamo a metà strada.
se cliccate sul contenitore vi si aprira una lista di sub contenitori .
e ci concentreremo su dgca-issuance-web e vedrete delle icone, premete sull'icona >_ , vi si aprirà il terminale.
se provate ad accedere su localhost:8080 vi renderete conto che non vi fa entrare perché vi chiederà una password.
che faremo noi? beh, creeremo un nuovo utente quindi nel terminale che vi si è aperto in precedenza cliccando su >_ dobbiamo installare questo apache2-utils e lo installeremo con i comandi di linux, in questo modo :
apt-get install apache2-utils
molto bene!
ora basterà creare un utente nostro .
sul terminale scrivete questo :
htpasswd -c /etc/nginx/.htpasswd nome-utente
ovviamente il nome-utente va sostituito con quello che voi volete , ok ?
una volta fatto partire il comando vi chiederà di inserire una password, e vi richiederà di inserirla nuovamente.
fatto ciò , ragazzi è fatta! potete accedere a localhost:8080 e inserirete i vostri dati utente come le avete creati , accedete e il piatto è pronto, purtroppo il codice qr non è valido , qualcuno ha delle idee?


text:
Standard Deviation formula is wrong

    return Math.sqrt(standardDeviation / length);

needs to be
    return Math.sqrt(standardDeviation / length - 1);

Cross-check with Wolframalpha: https://www.wolframalpha.com/input?i=standard+deviation+(25.0%2C+5.0%2C+45.0%2C+68.0%2C+61.0%2C+46.0%2C+24.0%2C+95.0)

Hey, @Atemu.
Assuming this article: https://www.baeldung.com/java-calculate-standard-deviation
It uses population standard deviation.
We'll update the article to make this clear.

source: gharchive/issue

authors: Atemu ulisseslima

repo: eugenp/tutorials

license: MIT

license_type: permissive

license_source: github-api


text:
Develop a simple IntelliJ plugin

Template project is growing in the number of Gradle tasks about deployment processes. It is necessary to review if we could develop some kind of IntelliJ plugin for the project.
Many thanks @miguelcordovam
Related issue:
https://github.com/miguelcordovam/leJOS_plugin/issues/11

Please don't forget us Eclipse users!
With classic LeJOS I was happy to use their Eclipse Plugin. It would be great if ev3dev could provide one too.

Hi @robl0377,
Yes, but remember that it is a Open Source project we are collaborating in this project with our spare time. In 2018, you could see that Java developers choose IntelliJ as the main Java IDE. This is the reason to start with IntelliJ.
I paste some links:
https://www.improgrammer.net/10-best-java-ides-for-programmers/
https://www.slant.co/topics/607/~best-java-ides-or-editors
I propose something:
Why not participate in the project creating a Plugin for eclipse?
It could be nice, isn't it?

Hmm, I'm an old hand with Eclipse, Java 6, ANT, and Subversion. Eclipse always was the best free Java IDE and until 2013 (in my last Java job) I used it professionally for application development.
Some hint from one of your links above about IntelliJ:

David Poulet's Experience
It's not really a free IDE. The community edition is quite limited compared to Eclipse or even Netbeans. There are lots of plugins but many of them are not available in the free edition. If you spend the money though, the commercial very is probably the best IDE out there.

So real Open Source developers should use a free IDE, don't you think? ;-)
About creating an Eclipse plugin myself: It would be quite a challenge and I don't know whether I could finish it. I think about it, though. No promises.
Actually, originally I wanted to port a program for a 2-wheel balancing robot for the Lego NXT controller from 2009, written in LeJOS NXT to some modern platform on the EV3 as a hobby. However, I'm still struggling with the development environment of ev3dev.
So the first step of porting this program still is classic LeJOS EV3 v0.9.1beta for me: Eclipse & Plugin. Faster development turnaround time. Faster start time of the program on the brick (even with only 300MHz EV3 brick).

I have created a repository at https://github.com/ev3dev-lang-java/intellij-plugin.

@miguelcordovam, @robl0377, we have a new repo about the plugin. You are invited to participate!!!
Merry Christmas

Related repository:
https://github.com/ev3dev-lang-java/intellij-plugin

Reorganize the project

authors: JakubVanek jabrena robl0377

license: mit

license_source: bigquery


text:
More flexible dependencies

When scheduling systems with chains of dependencies, you need to keep a references to the system structs:
local systemBStruct = {
	system = systemB,
	after = { systemA }
}

local systemCStruct = {
	system = systemC,
	after = { systemBStruct }
}

loop:scheduleSystems({
	systemA,
	systemBStruct,
	systemCStruct,
	{
		system = systemD,
		after = { systemCStruct }
	}
})

That's kind of inconvenient (and also isn't documented anywhere, and also wasn't how I would expect this API to work!), so this change makes it such that you can just use the function, instead of the struct:
loop:scheduleSystems({
	systemA,
	{
		system = systemB,
		after = { systemA },
	},
	{
		system = systemC,
		after = { systemB },
	},
	{
		system = systemD,
		after = { systemC },
	},
})

source: gharchive/pull-request

repo: evaera/matter


text:
01-button.elm has syntax errors

When I try to compile the Buttons example, I get this:
$ sudo elm-make Buttons.elm --output=Buttons.html
-- SYNTAX PROBLEM -------------------------------------------------- Buttons.elm

The = operator is reserved for defining variables. Maybe you want == instead? Or
maybe you are defining a variable, but there is whitespace before it?

32|       model = 0
                ^
Maybe <http://elm-lang.org/docs/syntax> can help you figure it out.

Detected errors in 1 module.

When I open the example in the online editor, it's different and compiles. Maybe the example on the page is not intended to be copied verbatim and compiled?
Apologies if I am misunderstanding something, I am a complete Elm beginner.

OS: macOS Sierra 10.12.4
Elm version: 0.18.0

@zky829 Could you post and point to the actual code (the one on your machine)? It'd be obvious if we see the copied code. The error message is obvious though.

I am assuming you are doing the exercise in the Elm Guide to implement "Reset". You are attempting to redefine the value of model.
Try this instead:
...
    Reset ->
      model - model

Also works:
...
    Reset ->
      0

It looks like @sr-ix has a good theory of the root cause here. The example works for me, so I am not able to reproduce with the information here.

repo: evancz/elm-architecture-tutorial


text:
Documented ESM Import Usage

Hello @evanplaice i've documented the usage of jquery-csv in ECMAScript and
i also provided a useful example that users can use to write their own code.

closes #93

authors: evanplaice ghost

repo: evanplaice/jquery-csv


text:
🛑 www.actionherojs.com is down

In 4ad53ef, www.actionherojs.com (https://www.actionherojs.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: www.actionherojs.com is back up in 6a80917.

repo: evantahler/upptime


text:
EVCC not starting after update to 0.127.0

Describe the bug
EVCC is not starting after having updated to 0.127.0
Steps to reproduce

Update to 0.127.0
Have a look at the logs

Configuration details
# open evcc at http://evcc.local:7070
network:
  schema: http
  host: evcc.local # .local suffix announces the hostname on MDNS
  port: 7070

log: info
levels:
  cache: error

# unique installation id
plant: XXX

interval: 30s # control cycle interval

meters:
  - type: template
    template: varta
    usage: grid
    host: XXX.XXX.XXX.XXX
    port: 502
    name: gridVarta

chargers:
  - name: wallboxElli
    type: template
    template: ellipro
    ip: XXX.XXX.XXX.XXX
    ski: XXX

loadpoints:
  - title: Carport
    charger: wallboxElli

tariffs:
  co2:
    type: grünstromindex
    zip: XXXXX
  currency: EUR
  grid:
    type: fixed
    price: 0.2999

site:
  title: Mein Zuhause
  meters:
    grid: gridVarta
  residualPower: 100

eebus:
  certificate:
    private: |
      -----BEGIN EC PRIVATE KEY-----
Xxx
      -----END EC PRIVATE KEY-----
    public: |
      -----BEGIN CERTIFICATE-----
Xxx
      -----END CERTIFICATE-----

Log details
Using config file: /config/custom_yaml/evcc.yaml
starting evcc: 'EVCC_DATABASE_DSN=/data/evcc.db evcc --config /config/custom_yaml/evcc.yaml'
[main  ] INFO 2024/06/12 22:03:14 evcc 0.127.0
[main  ] INFO 2024/06/12 22:03:14 using config file: /config/custom_yaml/evcc.yaml
[db    ] INFO 2024/06/12 22:03:14 using sqlite database: /data/evcc.db
[main  ] INFO 2024/06/12 22:03:14 listening at :7070
[main  ] FATAL 2024/06/12 22:03:14 cannot create charger 'wallboxElli': cannot create charger type 'template': cannot create charger type 'eebus': eebus not configured
[main  ] FATAL 2024/06/12 22:03:14 will attempt restart in: 15m0s

What type of operating system are you running?
HomeAssistant Add-on
Version
0.127.0

btw.

will attempt restart in: 15m0s

From the logs it looks like he is trying to restart every 3 minutes. Maybe you want to put the correct var in that text.

Referring to the changelog, I would check the fix applied for EEBUS maybe the bug is in there.

Same error here just upgraded from working system version 0.126.6
Using config file: /config/evcc.yaml
starting evcc: 'EVCC_DATABASE_DSN=/data/evcc.db evcc --config /config/evcc.yaml'
[main  ] INFO 2024/06/12 22:14:13 evcc 0.127.0
[main  ] INFO 2024/06/12 22:14:13 using config file: /config/evcc.yaml
[db    ] INFO 2024/06/12 22:14:14 using sqlite database: /data/evcc.db
[mqtt  ] INFO 2024/06/12 22:14:14 connecting evcc-2062920207 at tcp://localhost:1883
[main  ] INFO 2024/06/12 22:14:14 listening at :7070
[main  ] FATAL 2024/06/12 22:14:17 cannot create charger 'connect_pro': cannot create charger type 'template': cannot create charger type 'eebus': eebus not configured
[main  ] FATAL 2024/06/12 22:14:17 will attempt restart in: 15m0s

Same issue here after upgrading working system from 0.126.6 to 0.127 on Raspbian bullseye.
[main ] INFO 2024/06/12 22:39:21 evcc 0.127.0
[main ] INFO 2024/06/12 22:39:21 using config file: /etc/evcc.yaml
[db ] INFO 2024/06/12 22:39:25 using sqlite database: /var/lib/evcc/evcc.db
[mqtt ] INFO 2024/06/12 22:39:26 connecting evcc-354576817 at tcp://xxxxx:1883
[mqtt ] DEBUG 2024/06/12 22:39:26 tcp://xxxxx:1883 connected
[main ] INFO 2024/06/12 22:39:26 listening at :7070
[main ] FATAL 2024/06/12 22:39:26 cannot create charger 'wallbox2': cannot create charger type 'template': cannot create charger type 'eebus': eebus not configured
[main ] FATAL 2024/06/12 22:39:26 will attempt restart in: 15m0s

Same issue too after upgrading from 0.126.6 to 0.127
Jun 13 06:35:07 csc-evcc evcc[273886]: [main  ] FATAL 2024/06/13 06:35:07 cannot create charger 'Links': cannot create charger type 'template': cannot create charger type 'eebus': eebus not configured
The config itself contains the eebus configuration
  certificate:
    public: |
      -----BEGIN CERTIFICATE-----
    XYZ
      -----END CERTIFICATE-----

    private: |
      -----BEGIN EC PRIVATE KEY-----
      XYZ
      -----END EC PRIVATE KEY-----```

Same here, upgrading from working 0.125.0 to 0.127.0

Just to add my voice: same here after upgrading from 0.126.5 to 0.127.0

Same here, upgrading from not working 0.126.6 to 0.127.0

Ich denke, ihr könnt aufhören mit "bei mir auch". ;-)

Funktioniert immer noch nicht.
[main  ] INFO 2024/06/13 05:40:57 evcc 0.127.0
[main  ] INFO 2024/06/13 05:40:57 using config file: /config/mydockerdata/evcc/yaml/evcc.yaml
[db    ] INFO 2024/06/13 05:40:58 using sqlite database: /config/mydockerdata/evcc/sql/evcc.db
[mqtt  ] INFO 2024/06/13 05:40:58 connecting evcc at tcp://192.168.10.132:1884
[main  ] INFO 2024/06/13 05:40:58 listening at :7070
[main  ] FATAL 2024/06/13 05:40:58 cannot create charger 'wallbox': cannot create charger type 'template': cannot create charger type 'eebus': eebus not configured
[main  ] FATAL 2024/06/13 05:40:58 will attempt restart in: 15m0s
Using config file: /config/mydockerdata/evcc/yaml/evcc.yaml
starting evcc: 'EVCC_DATABASE_DSN=/config/mydockerdata/evcc/sql/evcc.db evcc --config /config/mydockerdata/evcc/yaml/evcc.yaml'
[main  ] INFO 2024/06/14 08:02:14 evcc 0.127.1
[main  ] INFO 2024/06/14 08:02:14 using config file: /config/mydockerdata/evcc/yaml/evcc.yaml
[db    ] INFO 2024/06/14 08:02:14 using sqlite database: /config/mydockerdata/evcc/sql/evcc.db
[mqtt  ] INFO 2024/06/14 08:02:14 connecting evcc at tcp://192.168.10.132:1884
[eebus ] INFO 2024/06/14 08:02:14 Local SKI:  d7138aeb02b47ae2a6f10eebeb83e3d87dca63b1
[main  ] INFO 2024/06/14 08:02:14 listening at :7070
[main  ] FATAL 2024/06/14 08:03:44 cannot create charger 'wallbox': cannot create charger type 'template': cannot

Scheint aber kein prinzipielles Problem mehr mit EEBus zu sein: Bei mir startet das Image 0.127.1 wieder sauber auf (Das war mal ein schneller BugFix).
Wenn Logs und YAML weiter helfen kann ich die auf Anfrage gerne posten...

I/o timeout hat nix hiermit zu tun.

wenn ich heute Abend Zuhause bin, schalte ich die Wallbox vom Strom.
Mal sehn, ob es danach geht. Das hatte ich früher schon mal.
Die Elli Box ist echt Scheiße.

Bei mir funktioniert alles. Auch mit Elli Box, 0.127.1 und Enyaq über MySkoda.
Danke für den schnellen fix.

Dito - alles super und vielen Dank für das Release. Klasse, dass das so schnell gefixed wurde! :D

Bei mir kommt auch mit dem Update 127.1  die Meldung, dass der Server nicht konfiguriert ist

@Marty56: Restart via the Elli App should fix the problem too ;)

@Oberfranke: Can you provide a screenshot or log, sound to me like a different problem.

authors: MarcusLindemann Marty56 Oberfranke Uhrenradio VolkerK62 andig cschnatz dennisfisch eny34 kloeppb mattbalzer pandamouse84 pencoe

repo: evcc-io/evcc


text:
Loadpoint enable delay skipped

Describe the bug
Hallo,
in den letzten Wochen ist mir manchmal aufgefallen, dass der enable-delay nicht abgewartet wird und evcc sofort die Ladung startet, nach nur einem Update mit genug Überschussleistung.
Solange kein Fahrzeug angeschlossen ist frage ich auch keine Daten vom Wechselrichter ab und leite stattdessen über MQTT jeweils den Wert 0 an evcc weiter für grid / pv / battery / soc.
Sobald ein Auto angeschlossen ist (tagsüber & Ladeziel nicht erreicht) bekommt evcc aktuelle Messwerte vom Wechselrichter.
MaxCurrent, residualPower und die enable- / disableThresholds passe ich ebenfalls über MQTT an das ausgewählte Fahrzeug an, da deren tatsächliche Ladeleistung sich um mehrere 100 Watt unterscheidet (das sieht man in dem Log-Abschnitt den ich reinkopiert habe). In dem Fall wurde manuell auf Gastfahrzeug umgestellt und kurz darauf passen sich per MQTT die genannten Werte an und evcc bekommt danach echte Wechselrichter-Messwerte.
Anstatt nun die eingestellten 119s zu warten legt evcc sofort mit der Ladung los. Evtl. ist das Überschreiben des enableThresholds über MQTT schuld? Kann das leider heute nicht mehr überprüfen...
Steps to reproduce

...
Configuration details
network:
  port: 7070

interval: 10s

sponsortoken: -

meters:
- name: my_grid
  type: custom
  power:
    source: mqtt
    topic: grid/power
    scale: -1
    timeout: 3s
- name: my_pv
  type: custom
  power:
    source: mqtt
    topic: pv/power
    timeout: 3s
- name: my_battery
  type: custom
  power:
    source: mqtt
    topic: battery/power
    timeout: 3s
  soc:
    source: mqtt
    topic: battery/soc
    timeout: 3s
  capacity: 9.83

chargers:
- name: mennekes_amtron_charge_control
  type: template
  template: bender
  host: 192.168.178.44
  port: 502

vehicles:
- name: opel_corsa_e
  type: template
  template: flobz
  title: Corsa-e
  url: http://127.0.0.1:5000
  vin: -
  capacity: 43.5

site:
- title: Home
  meters:
    grid: my_grid
    pv: my_pv
    battery: my_battery
  residualPower: 200

loadpoints:
- title: Wallbox
  charger: mennekes_amtron_charge_control
  vehicle: opel_corsa_e
  mode: pv
  soc:
    poll:
      mode: charging
      interval: 1000h
    estimate: true
  enable:
    threshold: -3800
    delay: 119s
  disable:
    threshold: 199
    delay: 89s
  guardduration: 299s

mqtt:
  broker: 127.0.0.1:1883
  topic: evcc
  user: -
  password: -

log: debug

Log details
[site  ] DEBUG 2024/07/11 12:08:45 ----
[lp-1  ] DEBUG 2024/07/11 12:08:45 charge power: 0W
[lp-1  ] DEBUG 2024/07/11 12:08:45 charge currents: [0.004 0.004 0.003]A
[site  ] DEBUG 2024/07/11 12:08:45 pv power: 0W
[site  ] DEBUG 2024/07/11 12:08:45 battery soc: 0%
[site  ] DEBUG 2024/07/11 12:08:45 battery power: 0W
[site  ] DEBUG 2024/07/11 12:08:45 grid meter: -0W
[site  ] DEBUG 2024/07/11 12:08:45 site power: 200W
[lp-1  ] DEBUG 2024/07/11 12:08:45 charge voltages: [235 236 236]V
[lp-1  ] DEBUG 2024/07/11 12:08:45 detected connected phases: 3p
[lp-1  ] DEBUG 2024/07/11 12:08:45 charge total import: 4833.881kWh
[lp-1  ] DEBUG 2024/07/11 12:08:45 charger status: B
[lp-1  ] DEBUG 2024/07/11 12:08:45 limitSoc reached: 85.0% > 60%
[lp-1  ] INFO 2024/07/11 12:08:52 vehicle updated: Corsa-e -> unknown
[lp-1  ] DEBUG 2024/07/11 12:08:52 !! active phases: 3p = min(0p measured 0p vehicle 3p physical 0p charger)
[lp-1  ] DEBUG 2024/07/11 12:08:52 set enable threshold: -4200
[lp-1  ] DEBUG 2024/07/11 12:08:53 set max current: 16
[site  ] DEBUG 2024/07/11 12:08:55 ----
[lp-1  ] DEBUG 2024/07/11 12:08:55 charge power: 0W
[lp-1  ] DEBUG 2024/07/11 12:08:55 charge currents: [0.001 0.004 0.003]A
[site  ] DEBUG 2024/07/11 12:08:55 pv power: 14759W
[site  ] DEBUG 2024/07/11 12:08:55 battery soc: 100%
[site  ] DEBUG 2024/07/11 12:08:55 battery power: 0W
[site  ] DEBUG 2024/07/11 12:08:55 grid meter: -13842W
[site  ] DEBUG 2024/07/11 12:08:55 site power: -13642W
[lp-1  ] DEBUG 2024/07/11 12:08:55 charge voltages: [235 236 236]V
[lp-1  ] DEBUG 2024/07/11 12:08:55 detected connected phases: 3p
[lp-1  ] DEBUG 2024/07/11 12:08:55 charge total import: 4833.881kWh
[lp-1  ] DEBUG 2024/07/11 12:08:55 charger status: B
[lp-1  ] DEBUG 2024/07/11 12:08:55 !! active phases: 3p = min(0p measured 0p vehicle 3p physical 0p charger)
[lp-1  ] DEBUG 2024/07/11 12:08:55 pv charge current: 19.8A = 0A + 19.8A (-13642W @ 3p)
[lp-1  ] DEBUG 2024/07/11 12:08:55 site power -13642W <= -4200W enable threshold
[lp-1  ] DEBUG 2024/07/11 12:08:55 pv enable in 0s
[lp-1  ] DEBUG 2024/07/11 12:08:55 pv enable timer elapsed
[lp-1  ] DEBUG 2024/07/11 12:08:55 max charge current: 6A
[lp-1  ] DEBUG 2024/07/11 12:08:55 charger enable
[lp-1  ] DEBUG 2024/07/11 12:08:55 wake-up timer: start

What type of operating system are you running?
HomeAssistant Add-on
Version
0.128.2

Hi, um das bearbeiten zu können, müssen wir das reproduzierbar haben. Wäre gut, wenn du den Effekt isolieren könntest. Gerade weil dein Setup mit MQTT und externer Steuerung ja etwas spezieller ist. Ich mach hier daher erstmal zu. Aber füg gerne neuen Infos an, wenn du hast und dann machen wir den wieder auf.

Ja, ich werde versuchen, das ganze noch weiter zu beobachten. Problematisch ist nur, dass über Home Assistant immer nur die letzten 1-2 Minuten des Logs abrufbar sind, also muss ich live dabei sein...
Mir ist aufgefallen, dass seit ein paar Versionen die 0en im UI auch als 0en angezeigt werden. "Früher" wurde da "keine Messwerte" o.ä. angezeigt, könnte zeitlich hinkommen mit dem übersprungenem enable-Delay Fehler.
Andererseits überschreibe ich auch erst seit einigen Wochen u.a. den enable-Threshold, das könnte halt auch passen.

Problematisch ist nur, dass über Home Assistant immer nur die letzten 1-2 Minuten des Logs abrufbar sind, also muss ich live dabei sein...

Über den evcc Log Viewer müsstest du deutlich mehr (10k Einträge) bekommen.

Problematisch ist nur, dass über Home Assistant immer nur die letzten 1-2 Minuten des Logs abrufbar sind, also muss ich live dabei sein...

Über den evcc Log Viewer müsstest du deutlich mehr (10k Einträge) bekommen.

Den Log Viewer habe ich noch gar nicht bemerkt, danke für den Tipp. Gerade mal geschaut, reicht etwa 25 Minuten zurück, das ist schonmal wesentlich angenehmer als die 1,x Minuten über Home Assistant ;D

Möglicherweise handelt es sich nur um ein Initialisierungsproblem des pvTimers. Es kann gut sein, dass jedes Mal, wo bei mir das Problem aufgetaucht ist evcc vorher kein einziges Mal die resetPVTimer()-Funktion aufgerufen hat, da das Standardfahrzeug sein Ladelimit erreicht hatte und das Gastfahrzeug dann sofort beim ersten Refresh zur Mittagszeit genug Leistung zur Verfügung hatte.
Hatte zuletzt auch häufiger evcc neu gestartet, wegen Änderungen der Config und evcc-Updates, deswegen könnte der Fall tatsächlich öfter aufgetreten sein. Wenn's stimmt, ist es natürlich nur ein relativ irrelevantes Problem, aber vielleicht lässt sich der Timer ja beim Start von evcc resetten und selbst dieser Fall wäre dann abgedeckt.
Im folgenden Log sieht man, wie beim ersten Wechsel aufs Gastfahrzeug der Timer resettet wird, beim zweiten Wechsel dann nicht mehr, weil die resetPVTimer()-Funktion einfach sofort returned.

[main  ] INFO 2024/07/12 00:54:34 evcc 0.128.2
[main  ] INFO 2024/07/12 00:54:34 using config file: /config/evcc.yaml
[db    ] INFO 2024/07/12 00:54:34 using sqlite database: /data/evcc.db
[mqtt  ] INFO 2024/07/12 00:54:34 connecting evcc-1150975679 at tcp://127.0.0.1:1883
[mqtt  ] DEBUG 2024/07/12 00:54:35 tcp://127.0.0.1:1883 connected
[main  ] INFO 2024/07/12 00:54:35 listening at :7070
[lp-1  ] DEBUG 2024/07/12 00:54:35 charge total import: 4846.524kWh
[site  ] INFO 2024/07/12 00:54:36 site config:
[site  ] INFO 2024/07/12 00:54:36   meters:      grid ✓ pv ✓ battery ✓
[site  ] INFO 2024/07/12 00:54:36     grid:      power ✓ energy ✗ currents ✗
[site  ] INFO 2024/07/12 00:54:36     pv 1:      power ✓ energy ✗ currents ✗
[site  ] INFO 2024/07/12 00:54:36     battery 1: power ✓ energy ✗ currents ✗ soc ✓ capacity ✓
[site  ] INFO 2024/07/12 00:54:36   vehicles:
[site  ] INFO 2024/07/12 00:54:36     vehicle 1: range ✓ finish ✗ status ✓ climate ✓ wakeup ✓
[lp-1  ] INFO 2024/07/12 00:54:36 loadpoint 1:
[lp-1  ] INFO 2024/07/12 00:54:36   mode:        pv
[lp-1  ] INFO 2024/07/12 00:54:36   charger:     power ✓ energy ✓ currents ✓ phases ✗ wakeup ✗
[lp-1  ] INFO 2024/07/12 00:54:36   meters:      charge ✓
[lp-1  ] INFO 2024/07/12 00:54:36     charge:    power ✓ energy ✓ currents ✓
[site  ] DEBUG 2024/07/12 00:54:36 set buffer soc: 95
[site  ] DEBUG 2024/07/12 00:54:36 set buffer start soc: 0
[site  ] DEBUG 2024/07/12 00:54:36 set priority soc: 30
[site  ] DEBUG 2024/07/12 00:54:36 set residual power: 100
[lp-1  ] DEBUG 2024/07/12 00:54:36 !! active phases: 3p = min(0p measured 0p vehicle 3p physical 0p charger)
[lp-1  ] DEBUG 2024/07/12 00:54:36 phase timer inactive
[lp-1  ] DEBUG 2024/07/12 00:54:36 pv timer inactive
[lp-1  ] INFO 2024/07/12 00:54:36 vehicle updated: unknown -> Corsa-e
[lp-1  ] DEBUG 2024/07/12 00:54:36 !! active phases: 3p = min(0p measured 0p vehicle 3p physical 0p charger)
[site  ] WARN 2024/07/12 00:54:36 interval <30s can lead to unexpected behavior, see https://docs.evcc.io/docs/reference/configuration/interval
[site  ] DEBUG 2024/07/12 00:54:36 ----
[lp-1  ] DEBUG 2024/07/12 00:54:36 charge power: 0W
[lp-1  ] DEBUG 2024/07/12 00:54:36 charge currents: [0.004 0.004 0.004]A
[site  ] DEBUG 2024/07/12 00:54:36 pv power: 0W
[site  ] DEBUG 2024/07/12 00:54:36 battery soc: 0%
[site  ] DEBUG 2024/07/12 00:54:36 battery power: 0W
[site  ] DEBUG 2024/07/12 00:54:36 grid meter: -0W
[site  ] DEBUG 2024/07/12 00:54:36 site power: 100W
[lp-1  ] DEBUG 2024/07/12 00:54:36 vehicle odometer: 17277km
[lp-1  ] DEBUG 2024/07/12 00:54:36 charge voltages: [232 232 231]V
[lp-1  ] DEBUG 2024/07/12 00:54:36 detected connected phases: 3p
[lp-1  ] DEBUG 2024/07/12 00:54:36 charge total import: 4846.524kWh
[lp-1  ] DEBUG 2024/07/12 00:54:36 charger status: B
[lp-1  ] DEBUG 2024/07/12 00:54:36 charge start energy: 4.85e+03kWh
[lp-1  ] INFO 2024/07/12 00:54:36 car connected
[lp-1  ] DEBUG 2024/07/12 00:54:36 pv timer elapse
[lp-1  ] DEBUG 2024/07/12 00:54:36 pv timer inactive
[lp-1  ] DEBUG 2024/07/12 00:54:36 charge total import: 4846.524kWh
[lp-1  ] DEBUG 2024/07/12 00:54:36 vehicle status: A
[lp-1  ] DEBUG 2024/07/12 00:54:36 vehicle soc: 80%
[lp-1  ] DEBUG 2024/07/12 00:54:36 vehicle range: 248km
[lp-1  ] DEBUG 2024/07/12 00:54:36 limitSoc reached: 80.0% > 60%
[lp-1  ] DEBUG 2024/07/12 00:54:37 set max current: 15
[lp-1  ] INFO 2024/07/12 00:54:41 vehicle updated: Corsa-e -> unknown
[lp-1  ] DEBUG 2024/07/12 00:54:41 !! active phases: 3p = min(0p measured 0p vehicle 3p physical 0p charger)
[lp-1  ] DEBUG 2024/07/12 00:54:41 set enable threshold: -4300
[lp-1  ] DEBUG 2024/07/12 00:54:41 set max current: 16
[site  ] DEBUG 2024/07/12 00:54:45 ----
[lp-1  ] DEBUG 2024/07/12 00:54:45 charge power: 0W
[lp-1  ] DEBUG 2024/07/12 00:54:45 charge currents: [0.003 0.004 0.004]A
[site  ] DEBUG 2024/07/12 00:54:45 pv power: 0W
[site  ] DEBUG 2024/07/12 00:54:45 battery soc: 0%
[site  ] DEBUG 2024/07/12 00:54:45 battery power: 0W
[site  ] DEBUG 2024/07/12 00:54:45 grid meter: -0W
[site  ] DEBUG 2024/07/12 00:54:45 site power: 100W
[lp-1  ] DEBUG 2024/07/12 00:54:45 charge voltages: [232 232 232]V
[lp-1  ] DEBUG 2024/07/12 00:54:45 detected connected phases: 3p
[lp-1  ] DEBUG 2024/07/12 00:54:45 charge total import: 4846.524kWh
[lp-1  ] DEBUG 2024/07/12 00:54:45 charger status: B
[lp-1  ] DEBUG 2024/07/12 00:54:45 !! active phases: 3p = min(0p measured 0p vehicle 3p physical 0p charger)
[lp-1  ] DEBUG 2024/07/12 00:54:45 pv charge current: 0A = 0A + -0.145A (100W @ 3p)
[lp-1  ] DEBUG 2024/07/12 00:54:45 pv enable timer reset
[lp-1  ] DEBUG 2024/07/12 00:54:45 pv timer inactive
[lp-1  ] INFO 2024/07/12 00:54:49 vehicle updated: unknown -> Corsa-e
[lp-1  ] DEBUG 2024/07/12 00:54:49 !! active phases: 3p = min(0p measured 0p vehicle 3p physical 0p charger)
[lp-1  ] DEBUG 2024/07/12 00:54:49 set enable threshold: -3900
[lp-1  ] DEBUG 2024/07/12 00:54:50 set max current: 15
[site  ] DEBUG 2024/07/12 00:54:54 ----
[lp-1  ] DEBUG 2024/07/12 00:54:54 charge power: 0W
[lp-1  ] DEBUG 2024/07/12 00:54:54 charge currents: [0.003 0.003 0.004]A
[site  ] DEBUG 2024/07/12 00:54:54 pv power: 0W
[site  ] DEBUG 2024/07/12 00:54:54 battery soc: 0%
[site  ] DEBUG 2024/07/12 00:54:54 battery power: 0W
[site  ] DEBUG 2024/07/12 00:54:54 grid meter: -0W
[site  ] DEBUG 2024/07/12 00:54:54 site power: 100W
[lp-1  ] DEBUG 2024/07/12 00:54:54 vehicle odometer: 17277km
[lp-1  ] DEBUG 2024/07/12 00:54:54 charge voltages: [232 232 231]V
[lp-1  ] DEBUG 2024/07/12 00:54:54 detected connected phases: 3p
[lp-1  ] DEBUG 2024/07/12 00:54:54 charge total import: 4846.524kWh
[lp-1  ] DEBUG 2024/07/12 00:54:54 charger status: B
[lp-1  ] DEBUG 2024/07/12 00:54:54 vehicle status: A
[lp-1  ] DEBUG 2024/07/12 00:54:54 vehicle soc: 80%
[lp-1  ] DEBUG 2024/07/12 00:54:54 vehicle range: 248km
[lp-1  ] DEBUG 2024/07/12 00:54:54 limitSoc reached: 80.0% > 60%
[lp-1  ] INFO 2024/07/12 00:54:59 vehicle updated: Corsa-e -> unknown
[lp-1  ] DEBUG 2024/07/12 00:54:59 !! active phases: 3p = min(0p measured 0p vehicle 3p physical 0p charger)
[lp-1  ] DEBUG 2024/07/12 00:54:59 set enable threshold: -4300
[lp-1  ] DEBUG 2024/07/12 00:55:00 set max current: 16
[site  ] DEBUG 2024/07/12 00:55:03 ----
[lp-1  ] DEBUG 2024/07/12 00:55:03 charge power: 0W
[lp-1  ] DEBUG 2024/07/12 00:55:03 charge currents: [0.005 0.004 0.003]A
[site  ] DEBUG 2024/07/12 00:55:03 pv power: 0W
[site  ] DEBUG 2024/07/12 00:55:03 battery soc: 0%
[site  ] DEBUG 2024/07/12 00:55:03 battery power: 0W
[site  ] DEBUG 2024/07/12 00:55:03 grid meter: -0W
[site  ] DEBUG 2024/07/12 00:55:03 site power: 100W
[lp-1  ] DEBUG 2024/07/12 00:55:03 charge voltages: [232 232 231]V
[lp-1  ] DEBUG 2024/07/12 00:55:03 detected connected phases: 3p
[lp-1  ] DEBUG 2024/07/12 00:55:03 charge total import: 4846.524kWh
[lp-1  ] DEBUG 2024/07/12 00:55:03 charger status: B
[lp-1  ] DEBUG 2024/07/12 00:55:03 !! active phases: 3p = min(0p measured 0p vehicle 3p physical 0p charger)
[lp-1  ] DEBUG 2024/07/12 00:55:03 pv charge current: 0A = 0A + -0.145A (100W @ 3p)

Ich lag falsch, denn heute hat die Ladung wieder sofort begonnen, ohne dass evcc vorher keine Gelegenheit gehabt hätte den pvTimer zu resetten. Stattdessen ist mir sowohl im Log als auch im Code aufgefallen, dass das Verhalten offenbar beabsichtigt ist. Die Zeilen 488 und 489 in loadpoint.go deuten klar darauf hin:
// immediately allow pv mode activity
lp.elapsePVTimer()
Dann wäre meine Frage, aus welchem Grund ist das so? Die Absicht hinter den (enable & disable) Delays ist es Schaltvorgänge bei sehr wechselhaftem PV-Überschuss zu vermeiden, wozu braucht man da diese Ausnahme von der Regel?

authors: naltatis waynistan


text:
update no-noninteractive-element-to-interactive-role rule to support role='tablist' on 's

Hello everyone!
Thanks for creating an awesome set of guidelines to help improve accessibility!
I do have one piece of feedback that I think might lead to a better change for the rule no-noninteractive-element-to-interactive-role . It appears that this rule fails when you add role='tablist' to a <ul>. While <ul> is non interactive, tablist is also non-interactive and its only the tabs inside the tablist which receive action. This can cause problems in interfaces where graceful fallback is preferred and the author intended to use a <ul> as a tablist instead of a generic div in the case that the users assistive technology does not support HTML5 roles.

@jbadan why close this?

@ljharb Hi 👋 I had missed the section of the docs that shows how to allow this behavior. See: https://github.com/evcohen/eslint-plugin-jsx-a11y/blob/master/docs/rules/no-noninteractive-element-to-interactive-role.md#rule-details

authors: jbadan ljharb


text:
Back to top works only once on Chrome

Just a minor thing.... I can't find a way to solve this so I'll just leave the comment here.
Pressing "Back to top" on any link will work just once.
I think that happens because we are adding a '#' to the url that makes the page go to the top... but after that nothing will work because the '#' is still there.

Yeah, not sure what we can do here. If you click it and don't click any other links, the hash (#) isn't actually gonna change. It's the limitation of markdown and what we can do here in Github.
Gonna close this out.

authors: BenAtEventbrite LucasPadovan

repo: eventbrite/javascript


text:
I have created a scheduled jobs using this :

Before posting an issue, please check the following:

Do you have a question? Please take a look at the samples and read the FAQ first.
** https://github.com/evernote/android-job#usage
** https://github.com/evernote/android-job/wiki/FAQ

Does the library crash for you? Please provide the version of the library, a log, stacktrace and even better a sample.

Do your jobs not run as expected or do you see another weird behavior? A full log is necessary. Also keep in mind how Doze works and maintenance windows can delay your job.
** https://developer.android.com/training/monitoring-device-state/doze-standby.html
** https://speakerdeck.com/vrallev/scheduling-background-job-on-android-at-the-right-time-1?slide=59

    mApplication = application;
    new JobRequest.Builder(BackgroundJob.TAG)
            .setPeriodic(TimeUnit.MINUTES.toMillis(20), TimeUnit.MINUTES.toMillis(5))
            .setUpdateCurrent(true)
            .build()
            .schedule();

So this job is a never-ending job. Our offices' system admin is using a mobile device as a server which is run 247365. So clients basically send SMS to this device, and when Wifi is disconnected and service is interrupted the SMS is saved to SQLite database, after every 15 minutes the Scheduled job is started and it's retry to send the SMS to the SQL server through WebAPI.
My problem is when the device sleep mode, basically, standby or doze mode the job is not working. So, it's unable retry to send the SMS to SQL server. According to your documentation, you said the job will always run every 15 mins or specific scheduled time.
What should I do now, is there any way to solve this issue? Please, help me.

I definitely didn't say that. Please read the FAQ and documentation about how Doze and App Standby work: https://github.com/evernote/android-job/wiki/FAQ#why-arent-my-periodic-jobs-running-as-expected-on-android-5-or-higher

Okay sorry for that, is there any way to do this?

repo: evernote/android-job


text:
Docs for deployment to Squarespace

Make sure it works well and probably place the instructions in wiki, linked from README; can use wix instructions as an example

Done!

authors: martinbianchi osdiab

repo: everydotorg/donate-button


text:
:bug: Fix: Broken changeset

Description
Concise description of proposed changes
Testing
Explain the quality checks that have been done on the code changes
Additional Information

[ ] I read the contributing docs (if this is your first contribution)

Your ENS/address:

Current dependencies on/for this PR:

main

PR #902   👈

This stack of pull requests is managed by Graphite.

repo: evmts/tevm-monorepo


text:
Update sbt to 1.7.0

Updates org.scala-sbt:sbt from 1.6.2 to 1.7.0.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-sbt", artifactId = "sbt" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "@monthly" },
  dependency = { groupId = "org.scala-sbt", artifactId = "sbt" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, commit-count:1

Superseded by #362.

repo: evolution-gaming/kafka-flow


text:
Update cats-effect to 3.4.9

About this PR
📦 Updates org.typelevel:cats-effect from 3.3.14 to 3.4.9
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.typelevel", artifactId = "cats-effect" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.typelevel", artifactId = "cats-effect" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, version-scheme:early-semver, commit-count:1

Superseded by #266.

repo: evolution-gaming/stracer


text:
chore(site): isolated playground base code

Example of usage:
<uip-root>
  <script type="text/html" uip-snippet label="Mixin example">
    The time is: <time time-inject-mixin></time>
  </script>
  <script type="text/html" uip-js-snippet label="Mixin example">
    import {ESLMixinElement} from '@exadel/esl';

    class TimeInjectMixin extends ESLMixinElement {
      static get is() {
        return 'time-inject-mixin';
      }

      connectedCallback() {
        super.connectedCallback();
        this.update();
      }

      update() {
        this.$host.innerHTML = new Date().toLocaleTimeString();
        this._timeout = setTimeout(() => this.update(), 1000);
      }
    }
    TimeInjectMixin.register();
  </script>

  <uip-snippets class="uip-toolbar" dropdown-view="@xs"></uip-snippets>
  <uip-preview isolation style="height: 50px"></uip-preview>
  <uip-editor label="Source code (HTML)" collapsible copy></uip-editor>
  <uip-editor script label="Source code (JS)" collapsible copy></uip-editor>
</uip-root>

:tada: This PR is included in version 4.15.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

repo: exadel-inc/esl


text:
fix: toggleable and panel animation fixes

ESLPanel: fix reflow on show animation
ESLToggelable: implement discussed approach for outside listener handler
Doc fixes. Note: there is one more item to discuss in https://github.com/exadel-inc/esl/issues/357
Add overall and update fallback time for gh-pages header menu

:tada: This PR is included in version 3.0.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


text:
fix(esl-utils): scrollIntoViewAsync() method signature

Corrects the scrollIntoViewAsync() method signature so that it exactly matches the native one.

:tada: This PR is included in version 3.4.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

authors: ala-n dshovchko


text:
🛑 Portfolio is down

In ba34f5d, Portfolio ($SECRET_P_SITE) was down:

HTTP code: 404
Response time: 549 ms

Resolved: Portfolio is back up in 1774f45.

repo: exand/upptime


text:
add check if workspace exists before init

This PR adds a warning and requires confirmation if one tries to reinit an existing workspace.

format!

repo: exasim-project/OBR


text:
[docs]【Ansible-Driver】passphraseが設定されている秘密鍵ファイルの対応

【Ansible-Driver】passphraseが設定されている秘密鍵ファイルの対応

完了

authors: enoman ooif

repo: exastro-suite/it-automation-docs


text:
Display the current filename somewhere in the UI

RE: #1668 I just realized that to help the user decide whether they need to hit "Save" or "Save as" button, we might want to display the current filename somewhere in the UI if it's not there already -- I don't remember seeing it -- maybe browser tab title on desktop, not sure about mobile.
CC @tomayac

Please see /src/actions/actionExport.tsx from https://github.com/excalidraw/excalidraw/pull/1709. My idea was something along the lines of…
<ToolButton
    type="button"
    icon={save}
    title={t("buttons.save")}
    aria-label={t("buttons.save")}
    showAriaLabel={useIsMobile()}
    onClick={() => updateData(null)}
    onPointerOver={() => {
      this.props.title = `${
        (window as any).handle
        ? ' (' + (window as any).handle.name + ')'
        : ''}`
    }
/>

…but I'm too much of a React n00b 🙈 and this wouldn't compile. I made ToolButton aware of onPointerOver, but didn't know how to access this from within the function.
Anyway, the idea essentially would be to dynamically change the title attribute onpointerover and make it show the current file name (window as any).handle.name. Help wanted.

Hello! Working on this task (unless someone tells me it's not ideal).

@sompylasar @tomayac Hello, is this issue still open? can I be assigned to it? would like to try as a good first issue.

Hey @yogeshwara-krishna, thanks! I've assigned you.
To spec this out a bit more, let's do this:

show the filename next to the main menu button like this:

only show this when the appState.fileHandle is defined and use its file name

on click, save back to the file

@dwelle Hello, I have a doubt, how should it be displayed in the mobile view screen?

@yogeshwara-krishna good question. I'd either not display it anywhere, or suffix it to the save to current file menu item:

But it would almost always not fit, so perhaps it's fine not to put it anywhere on mobile.

On mobile, the problem doesn’t arise, since you can’t save to the same file, but need to download to a new file. This is because the File System Access API doesn’t exist on mobile. So on mobile it doesn’t make sense to show a file name.

@dwelle @tomayac Hello, I have made a PR, please review it. Feedback and suggestions are welcome 😄

@tomayac you can also review #6985 , I haven't touched the mobile screen

authors: Ayush-Porwal chenjefferson dwelle sompylasar tomayac yogeshwara-krishna

repo: excalidraw/excalidraw


text:
Shortcuts not working

A lot of shortcuts don't work currently. For example it doesn't matter if I hit "r" or "R" or 2, I just don't get a rectangle but the page refreshes instead.
for the PWA these shortcuts don't work either

Hey, it works well for me. What OS, Browser are you using?


text:
编辑器api

请问有提供undo,redo copy，delete的编辑器api吗

Undo / redo is not exposed, but history is, so it should be trivial exposing it (assuming you would fork it, or prepare a PR).
Copy is not exposed, when forking you could get to it through the actionManager and actionCopy.
Delete could be implemented with updateScene, marking all items with isDeleted: true.

authors: Mrazator handsome-xiaowang


text:
feat: tweak toolbar shortcuts & remove library shortcut

freedraw: remove X shortcut, and change Shift-P to P. While Shift-P for freedraw is used in vector editors (where P is used for the vector pen tool), for low-precision, freedraw editors like Excalidraw it makes more sense to use just the P shortcut.
remove 0 shortcut for toggling the library, as there would now be conflict with the eraser tool

Still unsure of showing the letter labels instead of numbers in the toolbar, so kept as is.

I found it very convenient for X to be bonded to the pen tool.
Especially when using the right hand for a pen tablet and the left hand for shortcuts like E to erase, and X to draw.
Now I have to look at the keyboard each time to use the new shortcut, it's a regression for me.
Why old shortcut can't be left along with the new one?

I found it very convenient for X to be bonded to the pen tool. Especially when using the right hand for a pen tablet and the left hand for shortcuts like E to erase, and X to draw. Now I have to look at the keyboard each time to use the new shortcut, it's a regression for me.
Why old shortcut can't be left along with the new one?

x shortcut for freedraw tool is non-standard, and we may potentially want to use it for something else  in the future.
For now, I've reintroduced it in https://github.com/excalidraw/excalidraw/pull/5840, but keeping it undocumented, and we'll likely remove it in the future — but I assume not before we support keyboard customization.

Thanks @dwelle!

authors: adrianbienias dwelle


text:
pullToRefresh method not working when pull

I can't set page variable to 0 and cant print 'refreshed' to console when i pull.Beause of that every time i'm getting next page when im refresh.But i want to refresh all from first page.Am i doing something wrong ?
fetch and refresh methods
 Future<List<Entry>> fetchPage(int offset) async {
    page++;
    String url = craw.BASE + currentHref + pageText();
    print(url);
    EntryPageModel model = await craw.crawEntryPage(url);
    pageModel = model;

    return pageModel.entries;
  }

  Future<List<Entry>> refresh(int offset) async {
    print('refreshed');
    page = 0;
    return fetchPage(offset);
  }

This is my pagination_view
PaginationView<Entry>(
                    key: paginationKey,
                    shrinkWrap: true,
                    separatorBuilder: (context, index) {
                      if (index % 9 == 0 && index != 0)
                        return TextDivider(
                            text: '${(index / 10).round()}. sayfa sonu');
                      else
                        return Divider(color: Colors.white30, thickness: 1);
                    },
                    preloadedItems: [],
                    paginationViewType: PaginationViewType.listView,
                    pageFetch: this.fetchPage,
                    pageRefresh: this.refresh,
                    pullToRefresh: true,
                    onError: (dynamic error) => Center(
                      child: Text('Some error occured'),
                    ),
                    onEmpty: Center(
                      child: Text('Sorry! This is empty'),
                    ),
                    bottomLoader: Center(
                      child: CircularProgressIndicator(),
                    ),
                    itemBuilder: (context, entry, index) {
                      return AnimationConfiguration.staggeredList(
                        position: index,
                        child: SlideAnimation(
                          horizontalOffset: 25,
                          duration: Duration(milliseconds: 100),
                          child: EntryWidget(
                            entry: entry,
                          ),
                        ),
                      );
                    },
                  )

I'm facing the same issue

I'm facing the same issue

@oguzhan2142
are you solve it ?

@Moujarkash
are you solve it ?

@Ahmedhassan50  no I'm not using it anymore

Yes solved, but I had to clone the project into my project and update the code
I don't have time to make a pull request

@Moujarkash can you send me it and I will make pull request ?

I have removed the pageRefresh attribute. Now you can enable refresh by setting pullToRefresh to true. And to reset your page variable use the offset.
For example, if you are fetching 20 items every time then you page number will be offset/20
Future<List<User>> pageFetch(int offset) async {
    page = (offset / 20).round(); // like this
    // Make you API call here with page
  }


text:
Add prerequisites for practice exercises

This PR is related to #983 , it will deal with the following exercises :
meetup

hamming

raindrops

nucleotide-count

In order to evaluate the prerequisites in the best way, I'm doing the exercise then I'm reviewing the exercise's proof of work and the submitted solutions.

Left my thoughts on the exercises in the PR. The issue description also mentions "meetup". Not sure what's up with that. thinking

Oops, looks like I forgot to push this one's commit. It's done now :)

repo: exercism/javascript


text:
Add exercise sublist

A port of the EcmaScript version.
BTW re-pushed this bc I forgot to update the README for JS testing...

OK @rchavarria thank you for the suggestions.  Let me know what you think!

Awesome, let's wait a little bit just in case any @exercism/ecmascripts wants to add some comments.
But, definitely, it should be merged before modifying config.json with core/non-core and so on.

Let's merge this and start working at #382

authors: matthewmorgan rchavarria


text:
Override probot/stale defaults, if necessary

Per the discussion in https://github.com/exercism/discussions/issues/128 we
will be installing the probot/stale integration on the Exercism organization on
April 10th, 2017.
By default, probot will comment on issues that are older than 60 days, warning
that they are stale. If there is no movement in 7 days, the bot will close the issue.
By default, anything with the labels security or pinned will not be closed by
probot.
If you wish to override these settings, create a .github/stale.yml file as described
in https://github.com/probot/stale#usage, and make sure that it is merged
before April 10th.
If the defaults are fine for this repository, then there is nothing further to do.
You may close this issue.

@ryanplusplus I've created a pinned label to use in the future if there are any long running issues, otherwise close this when you want.

@robphoenix thanks, I think we're good to close.

I made a mistake.
This was not explicitly documented in the README, but probot/stale requires the presence of a .github/stale.yml file.
If you want the default behavior, you need to add an empty .github/stale.yml file to this repo, otherwise the bot will not be active.

authors: kytrinyx robphoenix ryanplusplus

repo: exercism/xlua


text:
first pass at updating docs for SPM

Documentation update for #233 #142

We could also update /docs/INSTALLATION.md to include the Linux installation steps, but I only use a mac so I wasn't sure of the steps.

lets keep the xcode documentation for now for people who want to use xcode manualy.
lets add a new section on top for the package manager commans or links to official documentation.
people can also easily create an xcode project from the command line using the package manager.
what do you think?

@masters3d  I can certainly add that in also so there are three possible paths (manually-created Xcode project, SPM-generated project, or just CLI + text editor), but it might be confusing for new users, who should probably just generate a project for each exercise

i was thinking we could include a little bash script that can generate and open an xcode project.
we cant include the genereted project because the package manager creates hard links in the project so the project should not be checked into git.

something like this?
swift package generate-xcodeproj |  grep -oE "[^ ]+$" | xargs open

although that may not be significantly easier than generating the project yourself :man_shrugging:

sounds good. documentation is tricky.

added the TLDR — let me know if there are other changes or confusing steps 😃.  If we want to do the project generation bash script, that probably makes sense as a separate PR

repo: exercism/xswift


text:
Fix links to Checkstyle DTDs

Fixed broken links to Checkstyle DTDs.
See also the source of DTDs on the Github:
https://github.com/checkstyle/checkstyle/tree/master/src/main/resources/com/puppycrawl/tools/checkstyle

Coverage remained the same at 86.717% when pulling f89cc075b6984c8754c431ed81ba698a07b4ef46 on dmitry-timofeev:fix-dtd-link into 642ca6f8777eec4ddc88fd762c45f437e66c2ceb on exonum:master.

Mac build stuck for 10 mins+, restarted. Full log here just in case

authors: coveralls dmitry-timofeev vitvakatu

repo: exonum/exonum-java-binding


text:
Fixed error in the promise code for the header

I think it was just a typo. :-)

Thanks for this and sorry for the delay!
Yes, there was a typo and there's still is one. We fixed it in the latest commit.
Cheers!

authors: Pupix ahmed-masud

repo: expandjs/xp-request


text:
link for backend.h5 doesn't work

I almost have this model working, but the link to download backend.h5 at https://1drv.ms/u/s!ApLdDEW3ut5fgQXa7GzSlG-mdza6 says "This item might not exist or is no longer available" on the OneDrive.live.com page after I sign in.  Is anyone else having this issue?  I have tried with a couple of different browsers.

Thanks!

This issue was solved by using the link here:
https://github.com/experiencor/keras-yolo3/issues/79


text:
Cyiopt

Use conda to install cyipopt and then install the rest of the requirements into the base conda env with pip.

Mistakenly submitted a PR on the wrong repo. Sorry!

repo: experimental-design/bofire


text:
Make it harder to delete batteries + experiments.

Maybe "deletion" will be more of an archiving. Or at the very least will result in an automatic file based dump of relevant database fields for posterity.

Batteries have an inactive status now. Setting this value and then hiding the batteries and their related objects still needs to be implemented.

repo: expfactory/expfactory-deploy


text:
Additional run fields

On the front page, besides run ID, Name, Last modified, let's also add:

[x]  Owner i.e. the user who created it
[x]  Status example statuses = ["in progress" (default), "signed", "witnessed"].
[x]  Created date/time similar to "Last modified".

Also need to add:

[ ] An editable field in <RunEditorPage>

repo: explorablelabs/labflow


text:
[eas-cli] allow modification of provisioning profile in CI, add --freeze-credentials flag

TODO
replace the TODO doc markers
Why
We currently support passing in an ASC Api Key to eas build through environment variables. However, we've barred modifying iOS credentials automatically in CI. For many credentials like a Push Key, revoking/generating them in CI is a bad idea since an account has a very low limit on how many keys they are allowed to generate and revoking a push key can have a large impact on production. However, modifying provisioning profiles are relatively safe and needed on a semi-regular basis (ie) annual profile expiration
How
This PR allows for the creation and modification of app store and enterprise Provisioning Profiles in CI. Apple resigns app store provisioning profiles when it is distributed, so this should be relatively safe. For users that want to ensure their credentials don't get modified in CI, I've added a --freeze-credentials flag.
Test Plan

[ ] added + amended a bunch of tests
[ ] --non-interactive, wrong authentication method, expect to fail with helpful error message
[ ] ASC api key auth, --freeze-credentials, expect to fail with helpful error message
[ ] --non-interactive, ASC api key auth, succeed

/changelog-entry breaking-change  Allow modification of provisioning profile in CI, add --freeze-credentials flag

repo: expo/eas-cli


text:
Add note about responsiveness

I think would be better no make a note that this carousel is responsive and best-suited right for images, not fixed-width/height content. It was not clear from demos and readme.

That information is in there already.  Perhaps we can add a bullet point to the intro at the top of the documentation.

Actually, there already is a bullet point in the intro.

repo: express-labs/pure-react-carousel


text:
Fixed issue #2832.

While require a module like const x = require(variable);, Webpack will
print this warning Critical dependency: the request of a dependency is an expression.
Based on https://github.com/webpack/webpack/issues/196#issuecomment-354900072.

Hm, I am not sure I agree @dougwilson.  This is perfectly valid commonjs.  Reading that entire linked issue report on webpack, the authors concern is for browsers, because webpack made the decision (a bad decision) to include all possible require'd files if it is dynamic require like this.  They also expressed a future concern with compatibility with es modules, which is also a non-issue for us and maybe a non-issue entirely because there is now a spec for dynamic imports.
That all being said, I would love to hear more about the use case @chenhaihong has for bundling express with webpack.  I used to bundle it with browserfiy and it worked great, so I know there are use cases to bundle server side code.  But this is the first time I have herd of people using webpack to do this.

I can't speak for OP but I personally compile my serverside bundles with webpack when I want to share SSR and browser rendering compile stacks. I can elaborate if you like, but I suspect I'm not the only one using webpack to compile serverside code.

I too don't agree with this. What about other bundlers like Rollup or Parcel? A patch can't be done for any specific bundler.

Yes, I should add my reasoning behind not liking this change.  It is as @r0mflip mentions, would we add a patch for any bundler that does not support valid commonjs patterns?  We wouldn't, and the popularity of webpack should not make it an exception.
@jleclanche Is webpack the correct tool for this?  I use Babel directly for SRR react components, and Babel does not have any issue here.  The reason webpack complains is because it's focus is front-end bundling, which is a different use case with different constraints.  IMO you would be better off using babel then something which specifically does commonjs bundling than trying to shoehorn every library into the mold of front-end blunder requirements.

Is webpack the correct tool for this?

In a vacuum no it's not, but in the context of a web-app which already has an extensive webpack configuration and where it's important that SSR produces an as-identical-as-possible output as possible, it makes a lot of sense. Webpack does support this, so it's not a bad tool for it either.
For added context, this is a for create-react-app SPA, which reproduces the build script and pulls in the original webpack config. No mess in having to duplicate all their config in babel (which I attempted at first and it led me to visit hell).

which I attempted at first and it led me to visit hell

HAHAHA, I know this feeling quite keenly.
I fully understand the reasoning to try to keep your tooling consistent, it is complicated enough as it is that having two separate build pipelines would be a bad decision for most projects.
That being said, this does not mean express should specifically add code to circumvent a decision made by maintainers of an unrelated project.
I think a better long term solution would be for webpack to deal with all of the people in that issue making complaints.  It is fully valid for users to want their bundler to handle node side code, and node side code is commonjs.  Commonjs supports dynamic imports, so IMO, webpack should support dynamic imports.

An aside:
At my last company I was responsible for our entire FE infrastructure as we built it up (it was a startup so very "exciting").  At the time, webpack hadn't fully caught on and gulp was still the tool du'jour.  Gulp was a disaster in our earlier usage, so we looked at what would be the best way forward on bundling.  Browserify stood out because of its simplicity, support for the tools we needed (babel, minification, commonjs) and my trust in its author.  I have not once looked back from this decision.  I still use browserify in my projects today.  It is simple, reliable and does everything I need.
My teammates at my current job all had gotten on the webpack train at one point or another.  They complain about it almost every week.  I have to use it because I inherited some projects with it seutp.  I complain about it every time I have to make a change, because my changes never work they way I expect them to.  CRA has inherited this mess because somehow react and webpack's communities got bundled (intentional wording) together.
JUST BECAUSE IT IS POPULAR DOES NOT MAKE IT GOOD!

It is quite possible that my dislike for this tool clouds my judgement on this issue, but I think that when enough good engineers complain about something someone will come along and invent something better.  So adding a webpack exception here is a decision we will come to regret.

Yeah I mean, I have no opinion on webpack or any of that; CRA uses webpack internally, so I have to follow that.
Point is though, people do use webpack to compile to node targets and it's not unreasonable. The fix here is for a webpack quirk which basically warns that if the import cannot be fully predicted by webpack, then webpack cannot guarantee the sanity of the build. It's a reasonable warning, regardless of the build tool (although I don't believe it's surfaced by other builders).
I don't think the PR is necessarily the correct fix but I'm not familiar enough with Express' codebase to be the judge. If I were more familiar with it, I'd probably look for a way to rewrite this part that doesn't involve the dynamic import (or at least, such a highly dynamic import. Webpack is fine with partial-path imports such as "foo/bar/" + name + ".js).

although I don't believe it's surfaced by other builders

It warns because the behavior of webpack is to include all possible targets.  At least that was the behavior the last time I checked (and it is also mentioned in that thread).  Other bundlers don't do this and error at runtime if it is missing.

But is it? I'm not actually sure what the definitely-correct behaviour is there. IMO it should be configurable but that's kind of out of scope of this issue...

Agreed it is a bit out of scope here.  But it helps to understand why webpack specifically has this issue when trying to bundle dynamic imports.  Either way, the situation stands, webpack complains when it bundles Express, and we have three options:

Ignore it.  Putting the burden on the users. 👎
Specifically include a work around. Putting the burden on us, the maintainers of Express. 👎
Convince webpack to change.  Burden on the original authors of the problematic feature. 👍

I'am not a webpack user but the issue seems like more of a warning than an error. My understanding is that the dynamic require just stays there and works fine even with the warning. If anyone is seriously considering to bundle their whole code (without the dynamic stuff) into a single file they might want to have a look at https://github.com/zeit/ncc
I tried to bundle express with rollup. It just did what I expected, left the require alone, as if it had to be handled by the environment. I think it's best to leave it alone to webpack users and it's authors to fix this issue. Just like Sindre made a workaround around the issue (because he uses webpack in all of his projects).

My thumbs up was to the "it works in rollup".  I still think leaving it to the users is not the best solution, and that putting pressure on webpack to change is the right way.

Considering the age of the issue Iam not surprised by users building custom solution. It even led to this PR which is directly from require-fool-webpack. Don't consider me wrong Iam not suggesting users to build their own solution but Iam just saying it happens out of desperation.

If you can get the webpack devs to do something about this I'm all for it, but it also means you're going the "ignore" route for everyone using past, current and future versions of webpack up-and-until the version that has a theoretical fix to all this.
Having a workaround isn't crazy imo.

@jleclanche: If you can get the webpack devs to do something about this I'm all for it, but it also means you're going the "ignore" route for everyone using past, current and future versions of webpack up-and-until the version that has a theoretical fix to all this.

Webpack has the bug, it needs to be fixed somehow. The "theatrical" fix is one that needs to be done.

@jleclanche: Having a workaround isn't crazy imo.

It's unhealthy

Ok, seeing as this is both old and has negative sentiment for landing, I'm going to close this for now. Perhaps we can revisit in the future, or even dynamic require will not be part of Express at some point, who knows 🤔

authors: chenhaihong dougwilson jleclanche r0mflip wesleytodd

repo: expressjs/express


text:
refactor: replace ts-jest to @swc/jest

The @swc/jest is a test runner based in Rust
Before (using ts-jest)

After (using @swc/jest)

@rodrigocode4 thanks for submitting this request. I am going to run some tests and validate, if all pass I will definitely replace ts-jest for the rust jest version as it is way more faster. Keep your eye on it. Thanks for the recommendation

Hi @rodrigocode4 this is a great suggestion, we analyzed thoroughly but we will push migrating to swc jest later on in the pipeline. The reason is that, when we tested, there is not a good support for decorators. I even looked for many threads and couldn't find an easy solution. Works really well with simple tests, but E2E mock and using reflection it adds complications that the normal jest doesn't. I hope that they fix these issues than we will be more than happy to migrate as it is faster

repo: expressots/expressots


text:
Using nightly or other toolchains

In the Makevars file, it appears that the cargo build step is hardcoded
cargo build --lib --release --manifest-path=./rust/Cargo.toml --target-dir $(TARGET_DIR)

By adding the +<toolchain> flag to the cargo command a different toolchain can be selected.
It would be cool to dynamically read the toolchain specified for the crate or workspace -- e.g. in the rust-toolchain.toml file -- or allow the user to set it manually somehow.

The thing is, if you have a rust-toolchain.toml file, that setting will override, and that will be the toolchain of choice even for that "hardcoded" cargo call.

Sorry, I should have specified further. This issue was occurring for me when trying to install my package with devtools::install or install.packages.

I will note that the crate is a part of a workspace, so the rust-toolchain.toml file is outside of the crate's directory.

I might be misunderstanding.
I just would like to point out, that you can see what toolchain is taken
effect,
by calling rustup show, and it will tell you, in a particular crate, if a
rust-toolchain.toml
is overriding the default behavior.
On Mon, Apr 17, 2023 at 12:02 AM bicarlsen @.***> wrote:

I will note that the crate is a part of a workspace, so the
rust-toolchain.toml file is outside of the crate's directory.
—
Reply to this email directly, view it on GitHub
https://github.com/extendr/extendr/issues/533#issuecomment-1510500300,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAIDVSGEZTKIPO4B3TRVJH3XBRT7PANCNFSM6AAAAAAXAMKM54
.
You are receiving this because you commented.Message ID:
@.***>

authors: CGMossa bicarlsen

repo: extendr/extendr


text:
ESO Stable release for Oracle Vault

Hello All we would like to use ESO with Oracle Vault for OKE.
But we have observed that ESO does not have a stable release for OKE and Oracle Vault. it is alpha release.
I would like to know about the Stable release for ESO for oracle vault.

We can promote providers like oracle to a more mature level. To do that there needs to be decent unit & e2e test coverage and production burn time.
However, we (from a maintainers perspective) do not have plans to put a lot of effort into this provider at this point in time. It is community maintained and open for collaboration. We try to avoid breaking changes where possible even on community maintained providers.
We do to provide support for all providers on a best-effort basis and patch SDK versions weekly.
If the background of your question is whether or not you can/should use this in production i'd say: yes, please do it but please test it properly (just like with any other OSS) - and please contribute back to the project :wink: If there's better test coverage all users benefit from that.

repo: external-secrets/external-secrets


text:
Allow IAM role names instead of only full ARNs for AWS SecretStore provider

Describe the solution you'd like
In a SecretStore resource using the aws provider, I must pass a full IAM role ARN to the role field. If I only pass the role name, it fails with
Warning  ValidationFailed  3m29s  secret-store  ValidationError: <RoleName> is invalid

It would be simple enough for it to use a default value for the AWS account ID and figure out the ARN from that. ExternalSecret objects are able to find AWS secrets from just their names.
What is the added value?
Simplifies helm templates a bit.

The aws sdk does not allow to pass in a simple role name as it does not necessarily know in which account it runs in.

The aws sdk does not allow to pass in a simple role name as it does not necessarily know in which account it runs in.

How is the ESO able to accept just names for AWS secrets rather than full ARNs then?

How is the ESO able to accept just names for AWS secrets rather than full ARNs then?

If you happen to know a way to implement this, feel free to open a PR! 😁
IMO, it is a lot of code to omit something we should not omit, since the role Field is for ESO to do a sts:AssumeRole.

How is the ESO able to accept just names for AWS secrets rather than full ARNs then?

That's how the aws-sdk is designed. see: https://github.com/aws/aws-sdk-go/blob/v1.43.33/service/secretsmanager/api.go#L4011-L4017 and https://github.com/aws/aws-sdk-go/blob/v1.43.33/service/sts/api.go#L1458-L1461

authors: calebwoofenden gusfcarvalho moolen


text:
Fix #156, add new default background

I played with a couple repeating patterns but I always came back to this one.  Smaller repeating tiles sometimes made text appear blurry; this larger pattern doesn't have that problem.  I also think it's subtle enough to not be distracting, but that's subjective.
If you don't like this background then you can close this Pull Request.  No one ever commented when I offered suggestions so I decided to just go ahead and commit this one.

Hey @keforbes ! Sorry I just saw I missed your comment on #156
Thanks for going through and finding a good background to use. The background looks great to me.
Just a couple of minor comments on the code-

Done.

Awesome, thanks @keforbes !