[BUG] After enabling Glazes Basic Auth widgets don't work anymore

Environment
Self-Hosted (Docker)
System
Ubuntu 22.01 LTS Server RPI (8GB), Brave Version 1.41.96 Chromium: 103.0.5060.114, Firefox
Version
2.1.1
Describe the problem
After I've enabled Auth in Glazes and edited my conf.yml so Dashy can still use it, it does not work any more.
this is my config now (only a short part):
 - name: Disk
    icon: fas fa-compact-disc
    widgets:
      - type: gl-disk-space
        options:
          hostname: <my domain>
          userbame: <glances username>
          password: <password>
          useProxy: true
      - type: gl-disk-io
        options:
          hostname: <my domain>
          userbame: <glances username>
          password: <glazes password>
          useProxy: true

It did work before I enabled password Auth and it also works with and without "useProxy".
I've testes it in some Browsers and I could access the data after I entered the credentails.
Additional info
Browser Console:

Headers:
Request URL: https://dash.domain.de/cors-proxy
Request Method: GET
Status Code: 500
Remote Address: myip
Referrer Policy: strict-origin-when-cross-origin
access-control-allow-methods: GET, PUT, PATCH, POST, DELETE
access-control-allow-origin: *
content-length: 508
content-type: application/json; charset=utf-8
date: Sat, 16 Jul 2022 23:52:34 GMT
etag: W/"1fc-xtFQV1pMA6wxhc5AY/PJ48LsqbA"
server: openresty
strict-transport-security: max-age=63072000; preload
x-powered-by: Express
:authority: dash.domain.de
:method: GET
:path: /cors-proxy
:scheme: https
accept: application/json, text/plain, */*
accept-encoding: gzip, deflate, br
accept-language: de-DE,de;q=0.9
customheaders: null
referer: https://dash.domain.de/
sec-fetch-dest: empty
sec-fetch-mode: cors
sec-fetch-site: same-origin
sec-gpc: 1
target-url: https://gl.domain.de/api/3/diskio
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/103.0.5060.114 Safari/537.36

Priview:
{
    "error": {
        "message": "Request failed with status code 401",
        "name": "AxiosError",
        "config": {
            "transitional": {
                "silentJSONParsing": true,
                "forcedJSONParsing": true,
                "clarifyTimeoutError": false
            },
            "transformRequest": [
                null
            ],
            "transformResponse": [
                null
            ],
            "timeout": 0,
            "xsrfCookieName": "XSRF-TOKEN",
            "xsrfHeaderName": "X-XSRF-TOKEN",
            "maxContentLength": -1,
            "maxBodyLength": -1,
            "env": {},
            "headers": {
                "User-Agent": "axios/0.27.2"
            },
            "method": "get",
            "url": "https://gl.domain.de/api/3/diskio",
            "json": {}
        },
        "code": "ERR_BAD_REQUEST",
        "status": 401
    }
}

Response:
{"error":{"message":"Request failed with status code 401","name":"AxiosError","config":{"transitional":{"silentJSONParsing":true,"forcedJSONParsing":true,"clarifyTimeoutError":false},"transformRequest":[null],"transformResponse":[null],"timeout":0,"xsrfCookieName":"XSRF-TOKEN","xsrfHeaderName":"X-XSRF-TOKEN","maxContentLength":-1,"maxBodyLength":-1,"env":{},"headers":{"User-Agent":"axios/0.27.2"},"method":"get","url":"https://gl.domain.de/api/3/diskio","json":{}},"code":"ERR_BAD_REQUEST","status":401}}

Full Browser Console logs (Emojis are rendered in my browser, but after copieng they are gone):
InstallTrigger sollte nicht mehr verwendet werden und wird in Zukunft entfernt. dash.domain.de:1:16442

Dashy  V2.1.1 ?? CoolConsole.js:6:10
downloadable font: download failed (font-family: "Cutive Mono" style:normal weight:400 stretch:100 src index:0): status=2147746065 source: https://dash.domain.de/fonts/CutiveMono-Regular.ttf
XML-Verarbeitungsfehler: nicht wohlgeformt
Adresse: https://dash.domain.de/status-check/?&url=https%3A%2F%2Fjoplin.domain.de%2Flogin
Zeile Nr. 1, Spalte 1: status-check:1:1
XML-Verarbeitungsfehler: nicht wohlgeformt
Adresse: https://dash.domain.de/status-check/?&url=https%3A%2F%2Fytdl.domain.de%2F
Zeile Nr. 1, Spalte 1: status-check:1:1
XML-Verarbeitungsfehler: nicht wohlgeformt
Adresse: https://dash.domain.de/status-check/?&url=https%3A%2F%2Fportainer.domain.de%2F%23!%2Fauth
Zeile Nr. 1, Spalte 1: status-check:1:1
XML-Verarbeitungsfehler: nicht wohlgeformt
Adresse: https://dash.domain.de/status-check/?&url=https%3A%2F%2Fminer.domain.de%2F
Zeile Nr. 1, Spalte 1: status-check:1:1
XML-Verarbeitungsfehler: nicht wohlgeformt
Adresse: https://dash.domain.de/status-check/?&url=https%3A%2F%2Fsearch.domain.de
Zeile Nr. 1, Spalte 1: status-check:1:1
XML-Verarbeitungsfehler: nicht wohlgeformt
Adresse: https://dash.domain.de/status-check/?&url=https%3A%2F%2Fpm.domain.de%2Flogin
Zeile Nr. 1, Spalte 1: status-check:1:1
XML-Verarbeitungsfehler: nicht wohlgeformt
Adresse: https://dash.domain.de/status-check/?&url=https%3A%2F%2Fpihole.domain.de%2Fadmin%2F
Zeile Nr. 1, Spalte 1: status-check:1:1
downloadable font: download failed (font-family: "Digital" style:normal weight:400 stretch:100 src index:0): status=2147746065 source: https://dash.domain.de/fonts/Digital-Regular.ttf
downloadable font: download failed (font-family: "OpenWeatherIcons" style:normal weight:400 stretch:100 src index:0): status=2147746065 source: https://dash.domain.de/widget-resources/WeatherIcons.woff2

?? Warning ??
Unable to fetch data

This is likely not an issue with Dashy, but rather your configuration. If you think it is a bug, please open a ticket on GitHub: https://git.io/JukXk CoolConsole.js:11:10
Stack Trace
AxiosError: Request failed with status code 500 CoolConsole.js:18:12

?? Warning ??
Unable to fetch data

This is likely not an issue with Dashy, but rather your configuration. If you think it is a bug, please open a ticket on GitHub: https://git.io/JukXk CoolConsole.js:11:10
Stack Trace
AxiosError: Request failed with status code 500 CoolConsole.js:18:12

?? Warning ??
Unable to fetch data

This is likely not an issue with Dashy, but rather your configuration. If you think it is a bug, please open a ticket on GitHub: https://git.io/JukXk CoolConsole.js:11:10
Stack Trace
AxiosError: Request failed with status code 500 CoolConsole.js:18:12

?? Warning ??
Unable to fetch data

This is likely not an issue with Dashy, but rather your configuration. If you think it is a bug, please open a ticket on GitHub: https://git.io/JukXk CoolConsole.js:11:10
Stack Trace
AxiosError: Request failed with status code 500 CoolConsole.js:18:12

?? Warning ??
Unable to fetch data

This is likely not an issue with Dashy, but rather your configuration. If you think it is a bug, please open a ticket on GitHub: https://git.io/JukXk CoolConsole.js:11:10
Stack Trace
AxiosError: Request failed with status code 500 CoolConsole.js:18:12

?? Warning ??
Unable to fetch data

This is likely not an issue with Dashy, but rather your configuration. If you think it is a bug, please open a ticket on GitHub: https://git.io/JukXk CoolConsole.js:11:10
Stack Trace
AxiosError: Request failed with status code 500 CoolConsole.js:18:12
XML-Verarbeitungsfehler: nicht wohlgeformt
Adresse: https://dash.domain.de/status-check/?&url=https%3A%2F%2Fjoplin.domain.de%2Flogin
Zeile Nr. 1, Spalte 1: status-check:1:1
XML-Verarbeitungsfehler: nicht wohlgeformt
Adresse: https://dash.domain.de/status-check/?&url=https%3A%2F%2Fytdl.domain.de%2F
Zeile Nr. 1, Spalte 1: status-check:1:1
Uncaught (in promise)
Object { message: "Request failed with status code 500", name: "AxiosError", code: "ERR_BAD_RESPONSE", config: {…}, request: XMLHttpRequest, response: {…}, stack: "" }
6

?? Warning ??
Unable to fetch data

This is likely not an issue with Dashy, but rather your configuration. If you think it is a bug, please open a ticket on GitHub: https://git.io/JukXk CoolConsole.js:11:10
Stack Trace
AxiosError: Request failed with status code 500 CoolConsole.js:18:12
Request for font "Oxygen" blocked at visibility level 1 (requires 3)
frappe-charts.min.esm.js:1:1056
Request for font "Ubuntu" blocked at visibility level 1 (requires 3)
frappe-charts.min.esm.js:1:1056
Request for font "Droid Sans" blocked at visibility level 1 (requires 3)
frappe-charts.min.esm.js:1:1056
downloadable font: download failed (font-family: "OpenWeatherIcons" style:normal weight:400 stretch:100 src index:0): status=2147746065 source: https://dash.domain.de/widget-resources/WeatherIcons.woff2

?? Warning ??
Unable to fetch data

This is likely not an issue with Dashy, but rather your configuration. If you think it is a bug, please open a ticket on GitHub: https://git.io/JukXk CoolConsole.js:11:10
Stack Trace
AxiosError: Request failed with status code 500 CoolConsole.js:18:12

?? Warning ??
Unable to fetch data

This is likely not an issue with Dashy, but rather your configuration. If you think it is a bug, please open a ticket on GitHub: https://git.io/JukXk CoolConsole.js:11:10
Stack Trace
AxiosError: Request failed with status code 500 CoolConsole.js:18:12

?? Warning ??
Unable to fetch data

This is likely not an issue with Dashy, but rather your configuration. If you think it is a bug, please open a ticket on GitHub: https://git.io/JukXk CoolConsole.js:11:10
Stack Trace
AxiosError: Request failed with status code 500 CoolConsole.js:18:12

?? Warning ??
Unable to fetch data

This is likely not an issue with Dashy, but rather your configuration. If you think it is a bug, please open a ticket on GitHub: https://git.io/JukXk CoolConsole.js:11:10
Stack Trace
AxiosError: Request failed with status code 500 CoolConsole.js:18:12
XML-Verarbeitungsfehler: nicht wohlgeformt
Adresse: https://dash.domain.de/status-check/?&url=https%3A%2F%2Fportainer.domain.de%2F%23!%2Fauth
Zeile Nr. 1, Spalte 1: status-check:1:1
XML-Verarbeitungsfehler: nicht wohlgeformt
Adresse: https://dash.domain.de/status-check/?&url=https%3A%2F%2Fsearch.domain.de
Zeile Nr. 1, Spalte 1: status-check:1:1
XML-Verarbeitungsfehler: nicht wohlgeformt
Adresse: https://dash.domain.de/status-check/?&url=https%3A%2F%2Fwhoogle.domain.de%2F
Zeile Nr. 1, Spalte 1: status-check:1:1
XML-Verarbeitungsfehler: nicht wohlgeformt
Adresse: https://dash.domain.de/status-check/?&url=https%3A%2F%2Fpm.domain.de%2Flogin
Zeile Nr. 1, Spalte 1: status-check:1:1
XML-Verarbeitungsfehler: nicht wohlgeformt
Adresse: https://dash.domain.de/status-check/?&url=https%3A%2F%2Fminer.domain.de%2F
Zeile Nr. 1, Spalte 1: status-check:1:1
XML-Verarbeitungsfehler: nicht wohlgeformt
Adresse: https://dash.domain.de/status-check/?&url=https%3A%2F%2Fpihole.domain.de%2Fadmin%2F
Zeile Nr. 1, Spalte 1: status-check:1:1
Uncaught (in promise)
Object { message: "Request failed with status code 500", name: "AxiosError", code: "ERR_BAD_RESPONSE", config: {…}, request: XMLHttpRequest, response: {…}, stack: "" }

XML-Verarbeitungsfehler: nicht wohlgeformt
Adresse: https://dash.domain.de/status-check/?&url=https%3A%2F%2Fwhoogle.domain.de%2F
Zeile Nr. 1, Spalte 1: status-check:1:1
Uncaught (in promise)
Object { message: "Request failed with status code 500", name: "AxiosError", code: "ERR_BAD_RESPONSE", config: {…}, request: XMLHttpRequest, response: {…}, stack: "" }
4
Uncaught DOMException: Node.removeChild: The node to be removed is not a child of this node chunk-50f31ec3.9a136c55.js:1

?? Warning ??
Unable to fetch data

This is likely not an issue with Dashy, but rather your configuration. If you think it is a bug, please open a ticket on GitHub: https://git.io/JukXk CoolConsole.js:11:10
Stack Trace
AxiosError: Request failed with status code 500 CoolConsole.js:18:12
Uncaught (in promise)
Object { message: "Request failed with status code 500", name: "AxiosError", code: "ERR_BAD_RESPONSE", config: {…}, request: XMLHttpRequest, response: {…}, stack: "" }

?? Warning ??
Unable to fetch data

This is likely not an issue with Dashy, but rather your configuration. If you think it is a bug, please open a ticket on GitHub: https://git.io/JukXk CoolConsole.js:11:10
Stack Trace
AxiosError: Request failed with status code 500 CoolConsole.js:18:12
Uncaught (in promise)
Object { message: "Request failed with status code 500", name: "AxiosError", code: "ERR_BAD_RESPONSE", config: {…}, request: XMLHttpRequest, response: {…}, stack: "" }

?? Warning ??
Unable to fetch data

This is likely not an issue with Dashy, but rather your configuration. If you think it is a bug, please open a ticket on GitHub: https://git.io/JukXk CoolConsole.js:11:10
Stack Trace
AxiosError: Request failed with status code 500 CoolConsole.js:18:12
Uncaught (in promise)
Object { message: "Request failed with status code 500", name: "AxiosError", code: "ERR_BAD_RESPONSE", config: {…}, request: XMLHttpRequest, response: {…}, stack: "" }

?? Warning ??
Unable to fetch data

This is likely not an issue with Dashy, but rather your configuration. If you think it is a bug, please open a ticket on GitHub: https://git.io/JukXk CoolConsole.js:11:10
Stack Trace
AxiosError: Request failed with status code 500 CoolConsole.js:18:12
Uncaught (in promise)
Object { message: "Request failed with status code 500", name: "AxiosError", code: "ERR_BAD_RESPONSE", config: {…}, request: XMLHttpRequest, response: {…}, stack: "" }

XHRGEThttps://dash.domain.de/cors-proxy
[HTTP/2 500 Internal Server Error 36ms]

?? Warning ??
Unable to fetch data

This is likely not an issue with Dashy, but rather your configuration. If you think it is a bug, please open a ticket on GitHub: https://git.io/JukXk CoolConsole.js:11:10
Stack Trace
AxiosError: Request failed with status code 500 CoolConsole.js:18:12
Uncaught (in promise)
Object { message: "Request failed with status code 500", name: "AxiosError", code: "ERR_BAD_RESPONSE", config: {…}, request: XMLHttpRequest, response: {…}, stack: "" }

XHRGEThttps://dash.domain.de/cors-proxy
[HTTP/2 500 Internal Server Error 42ms]

GET
	https://dash.domain.de/cors-proxy
Status
500
Internal Server Error
VersionHTTP/2
Übertragen898 B (505 B Größe)

XHRGEThttps://dash.domain.de/cors-proxy
[HTTP/2 500 Internal Server Error 44ms]

?? Warning ??
Unable to fetch data

This is likely not an issue with Dashy, but rather your configuration. If you think it is a bug, please open a ticket on GitHub: https://git.io/JukXk CoolConsole.js:11:10
Stack Trace
AxiosError: Request failed with status code 500 CoolConsole.js:18:12
Uncaught (in promise)
Object { message: "Request failed with status code 500", name: "AxiosError", code: "ERR_BAD_RESPONSE", config: {…}, request: XMLHttpRequest, response: {…}, stack: "" }

?? Warning ??
Unable to fetch data

This is likely not an issue with Dashy, but rather your configuration. If you think it is a bug, please open a ticket on GitHub: https://git.io/JukXk CoolConsole.js:11:10
Stack Trace
AxiosError: Request failed with status code 500 CoolConsole.js:18:12
Uncaught (in promise)
Object { message: "Request failed with status code 500", name: "AxiosError", code: "ERR_BAD_RESPONSE", config: {…}, request: XMLHttpRequest, response: {…}, stack: "" }

XHRGEThttps://dash.domain.de/cors-proxy
[HTTP/2 500 Internal Server Error 36ms]

?? Warning ??
Unable to fetch data

This is likely not an issue with Dashy, but rather your configuration. If you think it is a bug, please open a ticket on GitHub: https://git.io/JukXk CoolConsole.js:11:10
Stack Trace
AxiosError: Request failed with status code 500 CoolConsole.js:18:12
Uncaught (in promise)
Object { message: "Request failed with status code 500", name: "AxiosError", code: "ERR_BAD_RESPONSE", config: {…}, request: XMLHttpRequest, response: {…}, stack: "" }

XHRGEThttps://dash.domain.de/cors-proxy
[HTTP/2 500 Internal Server Error 33ms]

?? Warning ??
Unable to fetch data

This is likely not an issue with Dashy, but rather your configuration. If you think it is a bug, please open a ticket on GitHub: https://git.io/JukXk CoolConsole.js:11:10
Stack Trace
AxiosError: Request failed with status code 500 CoolConsole.js:18:12
Uncaught (in promise)
Object { message: "Request failed with status code 500", name: "AxiosError", code: "ERR_BAD_RESPONSE", config: {…}, request: XMLHttpRequest, response: {…}, stack: "" }

XHRGEThttps://dash.domain.de/cors-proxy
[HTTP/2 500 Internal Server Error 35ms]

?? Warning ??
Unable to fetch data

This is likely not an issue with Dashy, but rather your configuration. If you think it is a bug, please open a ticket on GitHub: https://git.io/JukXk CoolConsole.js:11:10
Stack Trace
AxiosError: Request failed with status code 500 CoolConsole.js:18:12
Uncaught (in promise)
Object { message: "Request failed with status code 500", name: "AxiosError", code: "ERR_BAD_RESPONSE", config: {…}, request: XMLHttpRequest, response: {…}, stack: "" }

XHRGEThttps://dash.domain.de/cors-proxy
[HTTP/2 500 Internal Server Error 40ms]

XHRGEThttps://dash.domain.de/cors-proxy
[HTTP/2 500 Internal Server Error 37ms]

?? Warning ??
Unable to fetch data

This is likely not an issue with Dashy, but rather your configuration. If you think it is a bug, please open a ticket on GitHub: https://git.io/JukXk CoolConsole.js:11:10
Stack Trace
AxiosError: Request failed with status code 500 CoolConsole.js:18:12
Uncaught (in promise)
Object { message: "Request failed with status code 500", name: "AxiosError", code: "ERR_BAD_RESPONSE", config: {…}, request: XMLHttpRequest, response: {…}, stack: "" }

?? Warning ??
Unable to fetch data

This is likely not an issue with Dashy, but rather your configuration. If you think it is a bug, please open a ticket on GitHub: https://git.io/JukXk CoolConsole.js:11:10
Stack Trace
AxiosError: Request failed with status code 500 CoolConsole.js:18:12
Uncaught (in promise)
Object { message: "Request failed with status code 500", name: "AxiosError", code: "ERR_BAD_RESPONSE", config: {…}, request: XMLHttpRequest, response: {…}, stack: "" }

XHRGEThttps://dash.domain.de/cors-proxy
[HTTP/2 500 Internal Server Error 35ms]

?? Warning ??
Unable to fetch data

This is likely not an issue with Dashy, but rather your configuration. If you think it is a bug, please open a ticket on GitHub: https://git.io/JukXk CoolConsole.js:11:10
Stack Trace
AxiosError: Request failed with status code 500 CoolConsole.js:18:12
Uncaught (in promise)
Object { message: "Request failed with status code 500", name: "AxiosError", code: "ERR_BAD_RESPONSE", config: {…}, request: XMLHttpRequest, response: {…}, stack: "" }

XHRGEThttps://dash.domain.de/cors-proxy
[HTTP/2 500 Internal Server Error 36ms]

?? Warning ??
Unable to fetch data

This is likely not an issue with Dashy, but rather your configuration. If you think it is a bug, please open a ticket on GitHub: https://git.io/JukXk CoolConsole.js:11:10
Stack Trace
AxiosError: Request failed with status code 500 CoolConsole.js:18:12
Uncaught (in promise)
Object { message: "Request failed with status code 500", name: "AxiosError", code: "ERR_BAD_RESPONSE", config: {…}, request: XMLHttpRequest, response: {…}, stack: "" }

XHRGEThttps://dash.domain.de/cors-proxy
[HTTP/2 500 Internal Server Error 38ms]

XHRGEThttps://dash.domain.de/cors-proxy
[HTTP/2 500 Internal Server Error 41ms]

?? Warning ??
Unable to fetch data

This is likely not an issue with Dashy, but rather your configuration. If you think it is a bug, please open a ticket on GitHub: https://git.io/JukXk CoolConsole.js:11:10
Stack Trace
AxiosError: Request failed with status code 500 CoolConsole.js:18:12

?? Warning ??
Unable to fetch data

This is likely not an issue with Dashy, but rather your configuration. If you think it is a bug, please open a ticket on GitHub: https://git.io/JukXk CoolConsole.js:11:10
Stack Trace
AxiosError: Request failed with status code 500 CoolConsole.js:18:12
Uncaught (in promise)
Object { message: "Request failed with status code 500", name: "AxiosError", code: "ERR_BAD_RESPONSE", config: {…}, request: XMLHttpRequest, response: {…}, stack: "" }
2
XHRGEThttps://dash.domain.de/cors-proxy
[HTTP/2 500 Internal Server Error 38ms]

?? Warning ??
Unable to fetch data

This is likely not an issue with Dashy, but rather your configuration. If you think it is a bug, please open a ticket on GitHub: https://git.io/JukXk CoolConsole.js:11:10
Stack Trace
AxiosError: Request failed with status code 500 CoolConsole.js:18:12
Uncaught (in promise)
Object { message: "Request failed with status code 500", name: "AxiosError", code: "ERR_BAD_RESPONSE", config: {…}, request: XMLHttpRequest, response: {…}, stack: "" }

XHRGEThttps://dash.domain.de/cors-proxy
[HTTP/2 500 Internal Server Error 36ms]

?? Warning ??
Unable to fetch data

This is likely not an issue with Dashy, but rather your configuration. If you think it is a bug, please open a ticket on GitHub: https://git.io/JukXk CoolConsole.js:11:10
Stack Trace
AxiosError: Request failed with status code 500 CoolConsole.js:18:12
Uncaught (in promise)
Object { message: "Request failed with status code 500", name: "AxiosError", code: "ERR_BAD_RESPONSE", config: {…}, request: XMLHttpRequest, response: {…}, stack: "" }

XHRGEThttps://dash.domain.de/cors-proxy
[HTTP/2 500 Internal Server Error 45ms]

XHRGEThttps://dash.domain.de/cors-proxy
[HTTP/2 500 Internal Server Error 44ms]

?? Warning ??
Unable to fetch data

This is likely not an issue with Dashy, but rather your configuration. If you think it is a bug, please open a ticket on GitHub: https://git.io/JukXk CoolConsole.js:11:10
Stack Trace
AxiosError: Request failed with status code 500 CoolConsole.js:18:12
Uncaught (in promise)
Object { message: "Request failed with status code 500", name: "AxiosError", code: "ERR_BAD_RESPONSE", config: {…}, request: XMLHttpRequest, response: {…}, stack: "" }

?? Warning ??
Unable to fetch data

This is likely not an issue with Dashy, but rather your configuration. If you think it is a bug, please open a ticket on GitHub: https://git.io/JukXk CoolConsole.js:11:10
Stack Trace
AxiosError: Request failed with status code 500 CoolConsole.js:18:12
Uncaught (in promise)
Object { message: "Request failed with status code 500", name: "AxiosError", code: "ERR_BAD_RESPONSE", config: {…}, request: XMLHttpRequest, response: {…}, stack: "" }

XHRGEThttps://dash.domain.de/cors-proxy
[HTTP/2 500 Internal Server Error 41ms]

XHRGEThttps://dash.domain.de/cors-proxy
[HTTP/2 500 Internal Server Error 37ms]

?? Warning ??
Unable to fetch data

This is likely not an issue with Dashy, but rather your configuration. If you think it is a bug, please open a ticket on GitHub: https://git.io/JukXk CoolConsole.js:11:10
Stack Trace
AxiosError: Request failed with status code 500 CoolConsole.js:18:12
Uncaught (in promise)
Object { message: "Request failed with status code 500", name: "AxiosError", code: "ERR_BAD_RESPONSE", config: {…}, request: XMLHttpRequest, response: {…}, stack: "" }

?? Warning ??
Unable to fetch data

This is likely not an issue with Dashy, but rather your configuration. If you think it is a bug, please open a ticket on GitHub: https://git.io/JukXk CoolConsole.js:11:10
Stack Trace
AxiosError: Request failed with status code 500 CoolConsole.js:18:12
Uncaught (in promise)
Object { message: "Request failed with status code 500", name: "AxiosError", code: "ERR_BAD_RESPONSE", config: {…}, request: XMLHttpRequest, response: {…}, stack: "" }

XHRGEThttps://dash.domain.de/cors-proxy
[HTTP/2 500 Internal Server Error 36ms]

?? Warning ??
Unable to fetch data

This is likely not an issue with Dashy, but rather your configuration. If you think it is a bug, please open a ticket on GitHub: https://git.io/JukXk CoolConsole.js:11:10
Stack Trace
AxiosError: Request failed with status code 500 CoolConsole.js:18:12
Uncaught (in promise)
Object { message: "Request failed with status code 500", name: "AxiosError", code: "ERR_BAD_RESPONSE", config: {…}, request: XMLHttpRequest, response: {…}, stack: "" }

XHRGEThttps://dash.domain.de/cors-proxy
[HTTP/2 500 Internal Server Error 35ms]

?? Warning ??
Unable to fetch data

This is likely not an issue with Dashy, but rather your configuration. If you think it is a bug, please open a ticket on GitHub: https://git.io/JukXk CoolConsole.js:11:10
Stack Trace
AxiosError: Request failed with status code 500 CoolConsole.js:18:12
Uncaught (in promise)
Object { message: "Request failed with status code 500", name: "AxiosError", code: "ERR_BAD_RESPONSE", config: {…}, request: XMLHttpRequest, response: {…}, stack: "" }

XHRGEThttps://dash.domain.de/cors-proxy
[HTTP/2 500 Internal Server Error 36ms]

XHRGEThttps://dash.domain.de/cors-proxy
[HTTP/2 500 Internal Server Error 33ms]

?? Warning ??
Unable to fetch data

This is likely not an issue with Dashy, but rather your configuration. If you think it is a bug, please open a ticket on GitHub: https://git.io/JukXk CoolConsole.js:11:10
Stack Trace
AxiosError: Request failed with status code 500 CoolConsole.js:18:12

?? Warning ??
Unable to fetch data

This is likely not an issue with Dashy, but rather your configuration. If you think it is a bug, please open a ticket on GitHub: https://git.io/JukXk CoolConsole.js:11:10
Stack Trace
AxiosError: Request failed with status code 500 CoolConsole.js:18:12
Uncaught (in promise)
Object { message: "Request failed with status code 500", name: "AxiosError", code: "ERR_BAD_RESPONSE", config: {…}, request: XMLHttpRequest, response: {…}, stack: "" }
2
XHRGEThttps://dash.domain.de/cors-proxy
[HTTP/2 500 Internal Server Error 64ms]

GEThttps://dash.domain.de/fonts/CutiveMono-Regular.ttf
[HTTP/2 404 Not Found 38ms]

GEThttps://dash.domain.de/fonts/Digital-Regular.ttf
[HTTP/2 404 Not Found 36ms]

GEThttps://dash.domain.de/widget-resources/WeatherIcons.woff2
[HTTP/2 404 Not Found 33ms]

GEThttps://dash.domain.de/widget-resources/WeatherIcons.woff2
[HTTP/2 404 Not Found 27ms]

downloadable font: download failed (font-family: "OpenWeatherIcons" style:normal weight:400 stretch:100 src index:0): status=2147746065 source: https://dash.domain.de/widget-resources/WeatherIcons.woff2 2
downloadable font: download failed (font-family: "Digital" style:normal weight:400 stretch:100 src index:0): status=2147746065 source: https://dash.domain.de/fonts/Digital-Regular.ttf
downloadable font: download failed (font-family: "Cutive Mono" style:normal weight:400 stretch:100 src index:0): status=2147746065 source: https://dash.domain.de/fonts/CutiveMono-Regular.ttf

?? Warning ??
Unable to fetch data

This is likely not an issue with Dashy, but rather your configuration. If you think it is a bug, please open a ticket on GitHub: https://git.io/JukXk CoolConsole.js:11:10
Stack Trace
AxiosError: Request failed with status code 500 CoolConsole.js:18:12
Uncaught (in promise)
Object { message: "Request failed with status code 500", name: "AxiosError", code: "ERR_BAD_RESPONSE", config: {…}, request: XMLHttpRequest, response: {…}, stack: "" }

XHRGEThttps://dash.domain.de/cors-proxy
[HTTP/2 500 Internal Server Error 37ms]

?? Warning ??
Unable to fetch data

This is likely not an issue with Dashy, but rather your configuration. If you think it is a bug, please open a ticket on GitHub: https://git.io/JukXk CoolConsole.js:11:10
Stack Trace
AxiosError: Request failed with status code 500 CoolConsole.js:18:12
Uncaught (in promise)
Object { message: "Request failed with status code 500", name: "AxiosError", code: "ERR_BAD_RESPONSE", config: {…}, request: XMLHttpRequest, response: {…}, stack: "" }

XHRGEThttps://dash.domain.de/cors-proxy
[HTTP/2 500 Internal Server Error 43ms]

XHRGEThttps://dash.domain.de/cors-proxy
[HTTP/2 500 Internal Server Error 34ms]

?? Warning ??
Unable to fetch data

This is likely not an issue with Dashy, but rather your configuration. If you think it is a bug, please open a ticket on GitHub: https://git.io/JukXk CoolConsole.js:11:10
Stack Trace
AxiosError: Request failed with status code 500 CoolConsole.js:18:12

?? Warning ??
Unable to fetch data

This is likely not an issue with Dashy, but rather your configuration. If you think it is a bug, please open a ticket on GitHub: https://git.io/JukXk CoolConsole.js:11:10
Stack Trace
AxiosError: Request failed with status code 500 CoolConsole.js:18:12
Uncaught (in promise)
Object { message: "Request failed with status code 500", name: "AxiosError", code: "ERR_BAD_RESPONSE", config: {…}, request: XMLHttpRequest, response: {…}, stack: "" }
2
XHRGEThttps://dash.domain.de/cors-proxy
[HTTP/2 500 Internal Server Error 36ms]

?? Warning ??
Unable to fetch data

This is likely not an issue with Dashy, but rather your configuration. If you think it is a bug, please open a ticket on GitHub: https://git.io/JukXk CoolConsole.js:11:10
Stack Trace
AxiosError: Request failed with status code 500 CoolConsole.js:18:12
Uncaught (in promise)
Object { message: "Request failed with status code 500", name: "AxiosError", code: "ERR_BAD_RESPONSE", config: {…}, request: XMLHttpRequest, response: {…}, stack: "" }

XHRGEThttps://dash.domain.de/cors-proxy
[HTTP/2 500 Internal Server Error 34ms]

?? Warning ??
Unable to fetch data

This is likely not an issue with Dashy, but rather your configuration. If you think it is a bug, please open a ticket on GitHub: https://git.io/JukXk CoolConsole.js:11:10
Stack Trace
AxiosError: Request failed with status code 500 CoolConsole.js:18:12
Uncaught (in promise)
Object { message: "Request failed with status code 500", name: "AxiosError", code: "ERR_BAD_RESPONSE", config: {…}, request: XMLHttpRequest, response: {…}, stack: "" }

XHRGEThttps://dash.domain.de/cors-proxy
[HTTP/2 500 Internal Server Error 35ms]

?? Warning ??
Unable to fetch data

This is likely not an issue with Dashy, but rather your configuration. If you think it is a bug, please open a ticket on GitHub: https://git.io/JukXk CoolConsole.js:11:10
Stack Trace
AxiosError: Request failed with status code 500 CoolConsole.js:18:12
Uncaught (in promise)
Object { message: "Request failed with status code 500", name: "AxiosError", code: "ERR_BAD_RESPONSE", config: {…}, request: XMLHttpRequest, response: {…}, stack: "" }

XHRGEThttps://dash.domain.de/cors-proxy
[HTTP/2 500 Internal Server Error 44ms]

XHRGEThttps://dash.domain.de/cors-proxy
[HTTP/2 500 Internal Server Error 35ms]

?? Warning ??
Unable to fetch data

This is likely not an issue with Dashy, but rather your configuration. If you think it is a bug, please open a ticket on GitHub: https://git.io/JukXk CoolConsole.js:11:10
Stack Trace
AxiosError: Request failed with status code 500 CoolConsole.js:18:12
Uncaught (in promise)
Object { message: "Request failed with status code 500", name: "AxiosError", code: "ERR_BAD_RESPONSE", config: {…}, request: XMLHttpRequest, response: {…}, stack: "" }

?? Warning ??
Unable to fetch data

This is likely not an issue with Dashy, but rather your configuration. If you think it is a bug, please open a ticket on GitHub: https://git.io/JukXk CoolConsole.js:11:10
Stack Trace
AxiosError: Request failed with status code 500 CoolConsole.js:18:12
Uncaught (in promise)
Object { message: "Request failed with status code 500", name: "AxiosError", code: "ERR_BAD_RESPONSE", config: {…}, request: XMLHttpRequest, response: {…}, stack: "" }

XHRGEThttps://dash.domain.de/cors-proxy
[HTTP/2 500 Internal Server Error 34ms]

?? Warning ??
Unable to fetch data

This is likely not an issue with Dashy, but rather your configuration. If you think it is a bug, please open a ticket on GitHub: https://git.io/JukXk CoolConsole.js:11:10
Stack Trace
AxiosError: Request failed with status code 500 CoolConsole.js:18:12
Uncaught (in promise)
Object { message: "Request failed with status code 500", name: "AxiosError", code: "ERR_BAD_RESPONSE", config: {…}, request: XMLHttpRequest, response: {…}, stack: "" }

XHRGEThttps://dash.domain.de/cors-proxy
[HTTP/2 500 Internal Server Error 35ms]

?? Warning ??
Unable to fetch data

This is likely not an issue with Dashy, but rather your configuration. If you think it is a bug, please open a ticket on GitHub: https://git.io/JukXk CoolConsole.js:11:10
Stack Trace
AxiosError: Request failed with status code 500 CoolConsole.js:18:12
Uncaught (in promise)
Object { message: "Request failed with status code 500", name: "AxiosError", code: "ERR_BAD_RESPONSE", config: {…}, request: XMLHttpRequest, response: {…}, stack: "" }

XHRGEThttps://dash.domain.de/cors-proxy
[HTTP/2 500 Internal Server Error 43ms]

XHRGEThttps://dash.domain.de/cors-proxy
[HTTP/2 500 Internal Server Error 39ms]

?? Warning ??
Unable to fetch data

This is likely not an issue with Dashy, but rather your configuration. If you think it is a bug, please open a ticket on GitHub: https://git.io/JukXk CoolConsole.js:11:10
Stack Trace
AxiosError: Request failed with status code 500 CoolConsole.js:18:12
Uncaught (in promise)
Object { message: "Request failed with status code 500", name: "AxiosError", code: "ERR_BAD_RESPONSE", config: {…}, request: XMLHttpRequest, response: {…}, stack: "" }

?? Warning ??
Unable to fetch data

This is likely not an issue with Dashy, but rather your configuration. If you think it is a bug, please open a ticket on GitHub: https://git.io/JukXk CoolConsole.js:11:10
Stack Trace
AxiosError: Request failed with status code 500 CoolConsole.js:18:12
Uncaught (in promise)
Object { message: "Request failed with status code 500", name: "AxiosError", code: "ERR_BAD_RESPONSE", config: {…}, request: XMLHttpRequest, response: {…}, stack: "" }

XHRGEThttps://dash.domain.de/cors-proxy
[HTTP/2 500 Internal Server Error 35ms]

?? Warning ??
Unable to fetch data

This is likely not an issue with Dashy, but rather your configuration. If you think it is a bug, please open a ticket on GitHub: https://git.io/JukXk CoolConsole.js:11:10
Stack Trace
AxiosError: Request failed with status code 500 CoolConsole.js:18:12
Uncaught (in promise)
Object { message: "Request failed with status code 500", name: "AxiosError", code: "ERR_BAD_RESPONSE", config: {…}, request: XMLHttpRequest, response: {…}, stack: "" }

XHRGEThttps://dash.domain.de/cors-proxy
[HTTP/2 500 Internal Server Error 33ms]

?? Warning ??
Unable to fetch data

This is likely not an issue with Dashy, but rather your configuration. If you think it is a bug, please open a ticket on GitHub: https://git.io/JukXk CoolConsole.js:11:10
Stack Trace
AxiosError: Request failed with status code 500 CoolConsole.js:18:12
Uncaught (in promise)
Object { message: "Request failed with status code 500", name: "AxiosError", code: "ERR_BAD_RESPONSE", config: {…}, request: XMLHttpRequest, response: {…}, stack: "" }

XHRGEThttps://dash.domain.de/cors-proxy
[HTTP/2 500 Internal Server Error 75ms]

XHRGEThttps://dash.domain.de/cors-proxy
[HTTP/2 500 Internal Server Error 66ms]

XHRGEThttps://dash.domain.de/cors-proxy
[HTTP/2 500 Internal Server Error 74ms]

XHRGEThttps://dash.domain.de/cors-proxy
[HTTP/2 500 Internal Server Error 65ms]

XHRGEThttps://dash.domain.de/cors-proxy
[HTTP/2 500 Internal Server Error 54ms]

?? Warning ??
Unable to fetch data

This is likely not an issue with Dashy, but rather your configuration. If you think it is a bug, please open a ticket on GitHub: https://git.io/JukXk CoolConsole.js:11:10
Stack Trace
AxiosError: Request failed with status code 500 CoolConsole.js:18:12
Uncaught (in promise)
Object { message: "Request failed with status code 500", name: "AxiosError", code: "ERR_BAD_RESPONSE", config: {…}, request: XMLHttpRequest, response: {…}, stack: "" }

?? Warning ??
Unable to fetch data

This is likely not an issue with Dashy, but rather your configuration. If you think it is a bug, please open a ticket on GitHub: https://git.io/JukXk CoolConsole.js:11:10
Stack Trace
AxiosError: Request failed with status code 500 CoolConsole.js:18:12

?? Warning ??
Unable to fetch data

This is likely not an issue with Dashy, but rather your configuration. If you think it is a bug, please open a ticket on GitHub: https://git.io/JukXk CoolConsole.js:11:10
Stack Trace
AxiosError: Request failed with status code 500 CoolConsole.js:18:12

?? Warning ??
Unable to fetch data

This is likely not an issue with Dashy, but rather your configuration. If you think it is a bug, please open a ticket on GitHub: https://git.io/JukXk CoolConsole.js:11:10
Uncaught (in promise)
Object { message: "Request failed with status code 500", name: "AxiosError", code: "ERR_BAD_RESPONSE", config: {…}, request: XMLHttpRequest, response: {…}, stack: "" }

Stack Trace
AxiosError: Request failed with status code 500 CoolConsole.js:18:12
Uncaught (in promise)
Object { message: "Request failed with status code 500", name: "AxiosError", code: "ERR_BAD_RESPONSE", config: {…}, request: XMLHttpRequest, response: {…}, stack: "" }
2
XHRGEThttps://dash.domain.de/cors-proxy
[HTTP/2 500 Internal Server Error 35ms]

?? Warning ??
Unable to fetch data

This is likely not an issue with Dashy, but rather your configuration. If you think it is a bug, please open a ticket on GitHub: https://git.io/JukXk CoolConsole.js:11:10
Stack Trace
AxiosError: Request failed with status code 500 CoolConsole.js:18:12
Uncaught (in promise)
Object { message: "Request failed with status code 500", name: "AxiosError", code: "ERR_BAD_RESPONSE", config: {…}, request: XMLHttpRequest, response: {…}, stack: "" }

XHRGEThttps://dash.domain.de/cors-proxy
[HTTP/2 500 Internal Server Error 34ms]

?? Warning ??
Unable to fetch data

This is likely not an issue with Dashy, but rather your configuration. If you think it is a bug, please open a ticket on GitHub: https://git.io/JukXk CoolConsole.js:11:10
Stack Trace
AxiosError: Request failed with status code 500 CoolConsole.js:18:12
Uncaught (in promise)
Object { message: "Request failed with status code 500", name: "AxiosError", code: "ERR_BAD_RESPONSE", config: {…}, request: XMLHttpRequest, response: {…}, stack: "" }

?? Warning ??
Unable to fetch data

This is likely not an issue with Dashy, but rather your configuration. If you think it is a bug, please open a ticket on GitHub: https://git.io/JukXk CoolConsole.js:11:10
Stack Trace
AxiosError: Request failed with status code 500 CoolConsole.js:18:12
Uncaught (in promise)
Object { message: "Request failed with status code 500", name: "AxiosError", code: "ERR_BAD_RESPONSE", config: {…}, request: XMLHttpRequest, response: {…}, stack: "" }

XHRGEThttps://dash.domain.de/cors-proxy
[HTTP/2 500 Internal Server Error 35ms]

?? Warning ??
Unable to fetch data

This is likely not an issue with Dashy, but rather your configuration. If you think it is a bug, please open a ticket on GitHub: https://git.io/JukXk CoolConsole.js:11:10
Stack Trace
AxiosError: Request failed with status code 500 CoolConsole.js:18:12
Uncaught (in promise)
Object { message: "Request failed with status code 500", name: "AxiosError", code: "ERR_BAD_RESPONSE", config: {…}, request: XMLHttpRequest, response: {…}, stack: "" }

XHRGEThttps://dash.domain.de/cors-proxy
[HTTP/2 500 Internal Server Error 32ms]

?? Warning ??
Unable to fetch data

This is likely not an issue with Dashy, but rather your configuration. If you think it is a bug, please open a ticket on GitHub: https://git.io/JukXk CoolConsole.js:11:10
Stack Trace
AxiosError: Request failed with status code 500 CoolConsole.js:18:12
Uncaught (in promise)
Object { message: "Request failed with status code 500", name: "AxiosError", code: "ERR_BAD_RESPONSE", config: {…}, request: XMLHttpRequest, response: {…}, stack: "" }

XHRGEThttps://dash.domain.de/cors-proxy
[HTTP/2 500 Internal Server Error 35ms]

?? Warning ??
Unable to fetch data

This is likely not an issue with Dashy, but rather your configuration. If you think it is a bug, please open a ticket on GitHub: https://git.io/JukXk CoolConsole.js:11:10
Stack Trace
AxiosError: Request failed with status code 500 CoolConsole.js:18:12
Uncaught (in promise)
Object { message: "Request failed with status code 500", name: "AxiosError", code: "ERR_BAD_RESPONSE", config: {…}, request: XMLHttpRequest, response: {…}, stack: "" }

XHRGEThttps://dash.domain.de/cors-proxy
[HTTP/2 500 Internal Server Error 33ms]

?? Warning ??
Unable to fetch data

This is likely not an issue with Dashy, but rather your configuration. If you think it is a bug, please open a ticket on GitHub: https://git.io/JukXk CoolConsole.js:11:10
Stack Trace
AxiosError: Request failed with status code 500 CoolConsole.js:18:12
Uncaught (in promise)
Object { message: "Request failed with status code 500", name: "AxiosError", code: "ERR_BAD_RESPONSE", config: {…}, request: XMLHttpRequest, response: {…}, stack: "" }

XHRGEThttps://dash.domain.de/cors-proxy
[HTTP/2 500 Internal Server Error 36ms]

?? Warning ??
Unable to fetch data

This is likely not an issue with Dashy, but rather your configuration. If you think it is a bug, please open a ticket on GitHub: https://git.io/JukXk CoolConsole.js:11:10
Stack Trace
AxiosError: Request failed with status code 500 CoolConsole.js:18:12
Uncaught (in promise)
Object { message: "Request failed with status code 500", name: "AxiosError", code: "ERR_BAD_RESPONSE", config: {…}, request: XMLHttpRequest, response: {…}, stack: "" }

XHRGEThttps://dash.domain.de/cors-proxy
[HTTP/2 500 Internal Server Error 33ms]

?? Warning ??
Unable to fetch data

This is likely not an issue with Dashy, but rather your configuration. If you think it is a bug, please open a ticket on GitHub: https://git.io/JukXk CoolConsole.js:11:10
Stack Trace
AxiosError: Request failed with status code 500 CoolConsole.js:18:12
Uncaught (in promise)
Object { message: "Request failed with status code 500", name: "AxiosError", code: "ERR_BAD_RESPONSE", config: {…}, request: XMLHttpRequest, response: {…}, stack: "" }

XHRGEThttps://dash.domain.de/cors-proxy
[HTTP/2 500 Internal Server Error 40ms]

XHRGEThttps://dash.domain.de/cors-proxy
[HTTP/2 500 Internal Server Error 35ms]

?? Warning ??
Unable to fetch data

This is likely not an issue with Dashy, but rather your configuration. If you think it is a bug, please open a ticket on GitHub: https://git.io/JukXk CoolConsole.js:11:10
Stack Trace
AxiosError: Request failed with status code 500 CoolConsole.js:18:12
Uncaught (in promise)
Object { message: "Request failed with status code 500", name: "AxiosError", code: "ERR_BAD_RESPONSE", config: {…}, request: XMLHttpRequest, response: {…}, stack: "" }

?? Warning ??
Unable to fetch data

This is likely not an issue with Dashy, but rather your configuration. If you think it is a bug, please open a ticket on GitHub: https://git.io/JukXk CoolConsole.js:11:10
Stack Trace
AxiosError: Request failed with status code 500 CoolConsole.js:18:12
Uncaught (in promise)
Object { message: "Request failed with status code 500", name: "AxiosError", code: "ERR_BAD_RESPONSE", config: {…}, request: XMLHttpRequest, response: {…}, stack: "" }

XHRGEThttps://dash.domain.de/cors-proxy
[HTTP/2 500 Internal Server Error 34ms]

?? Warning ??
Unable to fetch data

This is likely not an issue with Dashy, but rather your configuration. If you think it is a bug, please open a ticket on GitHub: https://git.io/JukXk CoolConsole.js:11:10
Stack Trace
AxiosError: Request failed with status code 500 CoolConsole.js:18:12
Uncaught (in promise)
Object { message: "Request failed with status code 500", name: "AxiosError", code: "ERR_BAD_RESPONSE", config: {…}, request: XMLHttpRequest, response: {…}, stack: "" }

There are no Docker Logs
Please tick the boxes

[X] You have explained the issue clearly, and included all relevant info
[X] You are using a supported version of Dashy
[X] You've checked that this issue hasn't already been raised
[X] You've checked the docs and troubleshooting guide
[X] You agree to the code of conduct

Sorry, but Glazes isn't something I've come across before. If it's a third party authentication / authorization provider, then this would be something you'd configure independently of Dashy, so there's not going to be much I could help with.

Maybe I wasn't clear:
Dashy has this kind of auth already build in (docs):

I've set up the GLazes Password and Username and wrote it in the options of each widget and enabled "useProxy" (bc it's written there). Without password I don't even need use proxy because I've solved the cors errors earlies in NGINX PM.

And i've made a nistake while writing this: i mean glances and not glazes

And i've made a nistake while writing this: i mean glances and not glazes

Ohhh that makes a lot more sense now 🤣 I thought it was some kind of niche authorization server
The issue is likely with your config.
Replace userbame with username.


[BUG]: unknown error occurs. try again later

🐛 Describe the bug
The message shows: unknown error occurs. try again later
Environment
No response

The error details:


Documenting the various build scripts and their inputs.
https://axom.readthedocs.io/en/task-white238-document_all_the_builds/docs/sphinx/dev_guide/updating_tpls.html#build-scripts-and-their-configuration-files

Add example of where to find error logs when you reach failure.

Ready for review.  Thanks!


Release 10.1.1

10.1.1 (https:/Users/mike/projects/ui-components//compare/v10.1.0...v10.1.1) (2023-03-29)
Fixed

components: fix undefined appearing in class (51a6d28)

Includes

https://github.com/silinternational/ui-components/pull/201

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


`error: doomPrivateDir must be either a path, a derivation or a stringified store path' when using flake input

Hello!
Using the following gives me the error above, where inputs are the flake inputs; the output is an actual path, it's just not accepted:
"${inputs.doom-emacs}/test/doom.d"
# OR
toPath "${inputs.doom-emacs}/test/doom.d"

Any help in solving this would be greatly appreciated!

Actually, I seemed to have solved it using path { path = "${inputs.doom-emacs}/test/doom.d"; }!


[r] Explicitly add -I/usr/local/include and -L/usr/local/lib

This addresses #1342.

Codecov Report
Patch coverage has no change and project coverage change: -11.96 :warning:

Comparison is base (79511bb) 65.35% compared to head (7e9b285) 53.40%.

:exclamation: Current head 7e9b285 differs from pull request most recent head c40ebe4. Consider uploading reports for the commit c40ebe4 to get more accurate results

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@             Coverage Diff             @@
##             main    #1343       +/-   ##
===========================================
- Coverage   65.35%   53.40%   -11.96%
===========================================
  Files          91       61       -30
  Lines        7603     5187     -2416
===========================================
- Hits         4969     2770     -2199
+ Misses       2634     2417      -217

Flag
Coverage Δ

python
?

r
53.40% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
see 30 files with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

Yes, point taken on pkg-config.  The defining manual (here is prettier link says

One of the more tricky tasks can be to find the headers and libraries
of external software.  One tool which is increasingly available on
Unix-alikes (but not by default(3) on macOS) to do this is ‘pkg-config’.

and

(3) but it is available on the machines used to produce the CRAN
binary packages: however as Apple does not ship ‘.pc’ files for its
system libraries such as ‘expat’, ‘libcurl’, ‘libxml2’, ‘sqlite3’ and
‘zlib’, it may well not find information on these.  Some substitutes are
available from
https://github.com/R-macos/recipes/tree/master/stubs/pkgconfig-darwin
and are installed on the CRAN package builders.

I generally do test if it is present, when not it is harder to accomodate the build requirements.  Another score for having downloadable artifacts.

Closing in favor of #1361. Longer-term/contextual tracking is on #1365.


Update Travis config and fix lint/test errors

Verified that @h2kuo has signed the CLA. Thanks for the pull request!

Looks good to me


[compositorclient] Wayland: Weston update to xdg-shell stable protocol

The following commits update the Weston compositor client code in Thunder to use xdg-stable protocol. This was merged in Weston 6 so we now have a dependency on Weston 6 or above.  Tested using Weston 8 on iMX8MQ-evk board.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: pwielders:x: petegriffinYou have signed the CLA already but the status is still pending? Let us recheck it.

https://jenkins.code.rdkcentral.com/job/github-triggered/2135/ started

Copyright scan failure
Commit: 0881eb75b0cc0c3dcb3ac345538f7f06d7baa98b
Report detail: https://gist.github.com/5535c9802768e43cbb49ff4ada40f30b

https://jenkins.code.rdkcentral.com/job/github-triggered/2136/ started

Blackduck scan failure details
Summary: 0 violations, 0 files pending approval, 2 files pending identification.

Protex Server Path: /home/blackduck/github/Thunder/156/rdkcentral/Thunder

Commit: 2740ad4e005f788fe730eed9c255b513c756f6ba

Report detail: gist

Copyright scan failure
Commit: 2740ad4e005f788fe730eed9c255b513c756f6ba
Report detail: https://gist.github.com/244b03455dda316aeb9b66a18e05fd6a

Blackduck scan failure details
Summary: 0 violations, 0 files pending approval, 2 files pending identification.

Protex Server Path: /home/blackduck/github/Thunder/156/rdkcentral/Thunder

Commit: 2740ad4e005f788fe730eed9c255b513c756f6ba

Report detail: gist

@pwielders Please can you review this?
@kraj  @moorthy-bs fyi - updates to Thunder Weston wayland support

Hi Pete,
Please will you make the following change: in NOTICE at top level, add the new block of copyrights for Kristian Høgsberg down to Red Hat.  You can put this after line 9 as a new separately licensed entity:
Copyright © 2008-2013 Kristian Høgsberg
Copyright © 2013 Rafael Antognolli
Copyright © 2013 Jasper St. Pierre
Copyright © 2010-2013 Intel Corporation
Copyright © 2015-2017 Samsung Electronics Co., Ltd
Copyright © 2015-2017 Red Hat Inc.
Licensed under the MIT license
When you have made these, I will still have to clear blackduck/copyright blocking i.e. it doesn't fix itself.  But I will keep an eye on it.
Thanks, Martin
Martin Hughes RDK CMF Compliance Team

@mhughesacn I just pushed an extra commit that updates NOTICE file like you requested

Copyright scan failure
Commit: 81f7b75de9153113bbc4ad6639b664b45889ff14
Report detail: https://gist.github.com/02ed5fa8b06d751f6ebabf0d001c95b3

Blackduck scan failure details
Summary: 0 violations, 0 files pending approval, 2 files pending identification.

Protex Server Path: /home/blackduck/github/Thunder/156/rdkcentral/Thunder

Commit: 81f7b75de9153113bbc4ad6639b664b45889ff14

Report detail: gist

Copyright scan failure
Commit: 81f7b75de9153113bbc4ad6639b664b45889ff14
Report detail: https://gist.github.com/736befd4429c01840f6124b09dfedd17

Hi Pete.  Thanks for making the change.  I have done the approval work (hence all the rescanning), so these checks are clear now.  Martin


Eliminated duplicated code portion inside the for loop

Change Summary

Changed  superclass_fields.append(field) to be called outside of the if/else pair but inside the for loop, it will ensure that it is not duplicated.
Related issue number

Checklist

[ ] Unit tests for the changes exist
[ ] Tests pass on CI and coverage remains at 100%
[ ] Documentation reflects the changes where applicable
[x] changes/<pull request or issue id>-<github username>.md file added describing change
(see changes/README.md for details)

see my comment on #2726


Postpone update by 2 days if declined by user

This fixes #451 .
Should we maybe make the time configurable? I don't think it's really necessary.

I would not make it configurable, but we could debate the pros and cons of the various options. 1d, 2d, 3d or 1w ?
There are different situations to consider.

I guess this is not needed because the default update frequency is 31 days and in https://github.com/emilsvennesson/script.module.inputstreamhelper/pull/450 I changed the way last_check is set.
last_check is now set from the moment the version check is done, regardless of what the user decided or what version is installed.
So, I guess the user will only asked once a month to update.

@mediaminister Owh, I missed that because I am running official releases. However, only asking once ever 31 months is probably not a good option either.
If people on playback delay updating Widevine CDM (we all do this on ARM, I just want to watch something now, not wait 10 minutes with the family), and Widevine is revoked, your setup will fail and you may not remember it could be because you canceled the update prompt 2 weeks before.
On ARM what we could do is match the version with the x64 releases, and only ask for an update if e.g. x64 has an actual new release. (it is a cheap check anyway, although we have to cache those releases as well)
This way we can ask to update only when a new release is expected (e.g. ARM leaps behind) but not ask if we are still ahead (except every 31 days).

and Widevine is revoked, your setup will fail and you may not remember it could be because you canceled the update prompt 2 weeks before.

I understand, I'll guess I should first solve a problem in the TLS 64-bytes support PR when an older ARM version is installed.


03/27/2018 10:52 : Create Pull Request for branch master -> prTesting1_2018032710

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

split/updateTestRef1.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Nested: question

The documentation says I can do this.
nested: {
    stuff: { type: String, lowercase: true, trim: true }
  }
})

m.nested.stuff = 'good';

But can I do this?
nested: {
    type: String,
    lowercase: true,
    trim: true
    stuff: { type: String, lowercase: true, trim: true }
  }
})

m.nested = 'thats';
m.nested.stuff = 'good';

The purpose would be so that I could do.
myvalue: {
     type: String,
     trim: true,
     mycustomvalidationrequirements: {
            shouldshowonlyifsomecondition: { type: Boolean, default: false }
     }

I would rather do that that have to have a separate field value to store dependencies.
Maybe that works already and I just haven't tested it. Maybe you can do this and mongoose only parses out the reserved words?
Any thoughts? Maybe there is already an child object where you can pass arbitrary settings to the client.
I know that I could do
myvalue: {}
myvaluesettings: { required {}, color {} }

It just seems like it would be much nicer to just have those things under the field but still have the field have a value.

I have used this before to a limited extent by associating functions with paths, sorta like:
{ name: { type: String, shouldHide: function() {} } }

In other words, you won't be able to write to m.nested.stuff on a document (if you want to do that, you should use a virtual), but you can read/write to stuff in the schema itself. For instance,
var mongoose = require('mongoose');
var Schema = mongoose.Schema;

mongoose.connect('mongodb://localhost:27017/gh-1548');

var s = new Schema({
  nested: {
    type: String,
    lowercase: true,
    trim: true,
    stuff: { type: String, lowercase: true, trim: true }
  }
});

var M = mongoose.model('gh-2644', s);

var m = new M();
m.nested = 'str';
m.nested.stuff = 'bacon';

console.log(m.nested);
console.log(m.nested.stuff);

console.log('\n-------\n');
s.eachPath(function(path, properties) {
  console.log(path + ' ' + require('util').inspect(properties.options.stuff));
});

The above code outputs
str
undefined

-------

nested { type: [Function: String], lowercase: true, trim: true }
_id undefined
__v undefined


No layout in this folder

UI is built from kt files via Jetpack Compose.

This error pops up
How can this be fixed?

Gradle hasn't been updated to version 7.0-RC. I have pushed a new commit that fixes it so pull changes or update it manually.

It requires JDK 11 as well.


Misc fixes

[ ] Reenable old behavior

[ ] Refactor

Pull Request Test Coverage Report for Build 65

60 of 62 (96.77%)  changed or added relevant lines in 2 files are covered.
7 unchanged lines in 4 files lost coverage.
Overall coverage increased (+0.2%) to 99.127%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

include/lemon/parallel.hpp
52
54
96.3%

Files with Coverage Reduction
New Missed Lines
%

include/lemon/structure.hpp
1
79.88%

include/lemon/select.hpp
1
50.0%

include/lemon/deprecated/archive_run.hpp
2
76.32%

include/lemon/score.hpp
3
70.63%

Totals

Change from base Build 64:
0.2%

Covered Lines:
1589

Relevant Lines:
1603

💛  - Coveralls


Add full core testing coverage

Codecov Report

Merging #41 into master will increase coverage by 4.65%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #41      +/-   ##
==========================================
+ Coverage   83.05%   87.70%   +4.65%
==========================================
  Files          30       30
  Lines        2242     2172      -70
  Branches       43       43
==========================================
+ Hits         1862     1905      +43
+ Misses        373      260     -113
  Partials        7        7

Impacted Files
Coverage Δ

avionix/kube/apiextensions.py
100.00% <ø> (ø)

avionix/kube/core.py
77.03% <100.00%> (+9.25%)
:arrow_up:

avionix/kube/meta.py
77.96% <100.00%> (+2.54%)
:arrow_up:

Continue to review full report at Codecov.

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


Increase client body size limit to 100M from 10M

@sharat87 Sorry but why are we making this change? AFAIK server currently loads all files in-memory before use, and this change fixes nothing for that. OTOH, with just the nginx change, we're also not removing the limit on in-memory size. We should really start using InputStreams before making this change IMO. Incidentally raised an issue for this just today, #3562

@nidhi-nair, agreed. I didn't realize that the server also had a block on uploading the files currently. But your conversation on Discord yesterday hinted that this might not be as useful as I originally intended. Since the other issue you've opened will track for a more broader solution here, I'm closing this PR.

Reminder to include this in documentation before the feature goes out.


[Feature]: Stacked Funnel Chart

What problem does this feature solve?
The new funnel chart types have been amazing to show conversion funnels. Adding support for stacked bar charts would allow for visualizations to add an additional data feature. This would be especially meaningful for the evolutionGradient funnel type.

What does the proposed API look like?
API would add the following properties to the FunnelChart client component (added from BarChart component):
stack: boolean
categories: string[]
index: string

Hi @jasperdegens,  can you provide a real-world example for this? Wouldn't you rather use a custom Sankey chart for this?

Hey @severinlandolt, an example of how we would plan to use this would be showing a breakdown of conversion steps (i.e. Add credit card -> Copy invite code -> Send invite code) by UTM parameters, such as the referral source (i.e. Facebook, Twitter, Newsletter). This way, you could see your overall funnel, but also some additional details of what led to each conversion.
Sankey chart would also work, but have found the design of the tremor funnel really clean and straightforward!

Hi there! Thanks a lot for your suggestion and for providing an example!
After looking into it, we’ve decided not to implement stacked bar charts in funnel charts. Handling small stack values could make the user experience less smooth, and we haven't seen this pattern work well in funnels. We want to keep our design clean and simple for everyone.
Thanks again for your request!


Notifications and Communications  Research Parameters (Student and Institution)

Get in touch with @courtneygringras  to knowledge share!
Also see Dana's user stories around this topic in confluence.

https://app.zenhub.com/files/319429847/418ef573-880a-47b4-89b5-f1a7a6f8a15e/download


updated the content as per issue #37

Your headings are vague.  In future commits, give better headings.  It is obvious that you're updating content by the mere fact that you're making a PR in the first place.

I am going to make sure that the quality of my content is better, via my prospective commits.


return 400 bad request when fetching logs without --container option

add 400 bad request when fetching logs without --container option

@pavansokkenagaraj I know that kubectl doesn't require the -c option when fetching logs, is this an implementation detail at the API server that kubectl handles for you?
What error does this cause when using sbctl?

@pavansokkenagaraj is there a sensible default we can use to emulate that the 'standard' kubectl has -c as optional?

@xavpaice / @chris-sanders Sorry couldn't follow up quicker.
kubectl logs cmd eg: https://github.com/kubernetes/kubectl/blob/release-1.25/pkg/cmd/logs/logs.go#L54-L86
the way kubectl logs implemented after v1.23 is

first kubectl get pod cmd runs and gets the pods and validates if it is a single container pod,
then,kubectl logs is executed with below logic:
if single container pod, the logs are returned
if --container option is provided, specific container logs are returned
if --all-container=true is provided, all container logs are returned
if pod is of multi-contianer, and no --container option is given, an err is thrown requesting to choose a container from list of containers.

below v1.22 below used to return default container logs


[BUG] Can't access alternate media fields in patches views?

System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Ubuntu 20
FiftyOne installed from (pip or source): pip
FiftyOne version (run fiftyone --version): v0.17.2
Python version: 3.10.4

Describe the problem
When moved to patches_view, media_field buttons result in "This image failed to load. The file may not exist, or its type (image/png) may be unsupported"
Code to reproduce issue
my_dataset = fo.Dataset("test")
samples = []
for fod in tqdm(df.itertuples()):
    sample = fo.Sample(filepath= ...)
    sample["t_1"] = ...
    sample["t_2"] = ...
    sample["det"] = fo.Detections(
        detections=[fo.Detection(bounding_box=[top_left_x, top_left_y, width, height])])
    samples.append(sample)
my_dataset.add_samples(samples)
my_dataset.app_config.media_fields = ["filepath", "t_1", "t_2"]
session = fo.launch_app(my_dataset, port=1851, auto=False)
session.view = my_dataset.to_patches("det")

Other info / logs
Problem disappears when
session.view = my_dataset.to_patches("det", other_fields=["t_1", "t_2"])
is used.
I guess, to_patches, by default, has to consider my_dataset.app_config.media_fields list as if it is already appended to other_fields.
What areas of FiftyOne does this bug affect?

[ ] App: FiftyOne application issue
[x] Core: Core fiftyone Python library issue
[ ] Server: Fiftyone server issue

Willingness to contribute
The FiftyOne Community encourages bug fix contributions. Would you or another
member of your organization be willing to contribute a fix for this bug to the
FiftyOne codebase?

[ ] Yes. I can contribute a fix for this bug independently.
[ ] Yes. I would be willing to contribute a fix for this bug with guidance
from the FiftyOne community.
[x] No. I cannot contribute a bug fix at this time.

If you'd like your alternate media fields to be available in a patches view, you just need to include them in the other_fields argument of to_patches():
import fiftyone as fo
import fiftyone.zoo as foz
import fiftyone.utils.image as foui

dataset = foz.load_zoo_dataset("quickstart")

foui.transform_images(
    dataset,
    max_size=(-1, 64),
    output_field="thumbnail_path",
    output_dir="/tmp/thumbnails",
)

dataset.app_config.media_fields = ["filepath", "thumbnail_path"]
dataset.app_config.grid_media_field = "thumbnail_path"
dataset.save()

patches = dataset.to_patches("ground_truth", other_fields=["thumbnail_path"])

session = fo.launch_app(patches)

OK. I already explained this solution under "Other info / logs" parts, sorry if my point was not clear.
My main point is it would be better if the default behavior already includes it. But for the thumbnail case, this would not be meaningful.
Then my point becomes updating the media field in the app. Why would the media field show "thumbnail" if it is not available in patches view? (if only it is included in the other field, then displaying thumbnail under media field becomes useful)
But this would also be non applicable for some reason.
Then, my point becomes
the error "This image failed to load. The file may not exist, or its type (image/png) may be unsupported" is misleading, at least for an average user, my humble opinion.

That's a fair point. We should either include all media fields by default or remove the extra media fields from the selector unless they were specifically included.

patches = dataset.to_patches("ground_truth", other_fields=["thumbnail_path"])

@brimoor
Hey wanted to thank you for posting this. I was going nuts trying to figure out how to maintain the thumbnail view in patch view. I am having a really hard time with the performance of fiftyone, and this will help i hope


Fixing compilation issues (!) if MPI parcelport is enabled

@hkaiser I just rebased this since #4432 conflicted this. Merging now. Thanks again!


Add Legacy Fabric

Legacy Fabric is a fork of Fabric adding support for older versions of the game (currently supporting 1.12.2, 1.8.9, 1.7.10, and 1.6.4, with most development happening for 1.8.9). This PR splits Fabric into "variants" and generates independent metadata for each variant. This variant system was intended to allow future extensibility for projects like Cursed Legacy Fabric, which targets Beta 1.7.3.
I haven't added Legacy Fabric to the MultiMC GUI yet, and I'm not sure the best route to do so (automatically change Install Fabric to Install Legacy Fabric for supported versions, maybe?). However, I've tested the generated metadata and it works fine.
Additionally, Fabric Loader depends on a newer version of Guava than the default for 1.7.10. This can be installed manually, though I've submitted a PR at https://github.com/Legacy-Fabric/fabric-loader-1.8.9/pull/10 to get Guava from Maven. My meta-multimc was generated with that PR applied, so it should work without extra changes.

It would be awesome if this could get updated, now Legacy Fabric works using upstream loader, with our intermediaries.
So overall it should be easier to support.
Note:
A known issue with a fix is, versions using applets (pre-1.6) require the noapplet trait to work with fabric loader.


all: move to bakery.v2

Signed-off-by: Thomas Hipp<EMAIL_ADDRESS>

This pull request didn't trigger Jenkins as its author isn't in the whitelist.
An organization member must perform one of the following:

To have this branch tested by Jenkins, use the "ok to test" command.
To have a one time test done, use the "test this please" command.

Those commands are simple Github comments of the format: "jenkins: COMMAND"

jenkins: test this please

buildd03 looks stuck, ignoring.


Combine various webhook content pages

Summary
Combined various pages describing both incoming and outgoing webhooks into one page per topic. The previous versions of the webhook pages were moved into the archive directory.
NOTE: This PR depends on #1104 and contains its changes; those changes can be ignored. Please do not merge this PR until #1104 is merged.

Hello @neflyte,
Thanks for your pull request! A Core Committer will review your pull request soon. For code contributions, you can learn more about the review process here.

/update-branch

Error trying to update the PR.
Please do it manually.


[html] issue with the

VSCode Version: 1.0.0
OS Version: OSX 10.11.4

Steps to Reproduce:

Try to auto format the following HTML
<template>
Hello

World
</template>

I expect to get something like this
<template>
____
Hello

____
World

</template>
But it does not work. If I replace the <template> tag with
 then the auto format works correctly. This issue was not present in the previous version.
Thanks,

@aeschli do you feel responsible for HTML :-)

I can reproduce this using VSCode 1.0.0 on OSX 10.11.4 and Windows 10 with the standard Format Code shortcut (⇧⌥F) - no auto-format is required to be enabled.
As @mbergeron indicated, replacing the top-level <template/> tag with
 causes it to work as expected.
Context: I'm learning Aurelia where the html templates must be wrapped in <template/>.  I upgraded to VSCode 1.0.0 and ⇧⌥F no longer works for html templates.

We use the beautify-html library. It has a option '"html.format.unformatted" that lists all html tags that should be kept on the same line. The default value is the list of elements named here: https://www.w3.org/TR/html5/dom.html#phrasing-content.
You see that 'template' as one of the tags that should not be formatted.
To have it formatted, you have to define the setting yourself. E.g.
"html.format.unformatted": "a,b,br,i,img,input,label,span,textarea,u,text"

For the May release I list all unformatted tags in the settings default.
I also change it to only contain inline tags. template is not part of that list and will be formatted by default.


Fixes #5509 Remove suggest operations from access control policies

Describe your changes :

See #5509 for more details

Type of change :

[x] New feature
[x] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

[x] I have read the CONTRIBUTING document.
[x] I have commented on my code, particularly in hard-to-understand areas.
[x] I have added tests that prove my fix is effective or that my feature works.
[x] All new and existing tests passed.

This change is no longer required.


[21.05] onedrive: 2.4.11 -> 2.4.13

Motivation for this change
This PR backports  #126809 and  #134218 to 21.05 stable. The upstream commits apply cleanly via cherry-pick.
These backports are done, because 2.4.11 has a bug uploading modified files (https://github.com/abraunegg/onedrive/pull/1394) that is fixed in newer versions.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

@ofborg build onedrive

@ofborg eval


Lightweight image

Updated the build script so that if someone takes a stock Raspbian or Coder image, they can just run ./build and it sets everything up correctly:

Manages hardware_daemon.py with daemontools
installs all the python deps
uses apache to manage both coder (node.js) and blockly_webserver (flask) for port resolution

Also it nicely serves as a contract of everything blocky talky needs on the os to run safely.
code changes are compatible with current builds (so this is only a patch release candidate).

Trying it out and hitting hiccups not hit in the first time, going to fix those first

Awesome. Can I grab a binary?
Also, got 3min to check in via vid chat today?
On Sat, Jan 24, 2015 at 10:01 PM, Matthew Ahrens<EMAIL_ADDRESS>wrote:

Updated the build script so that if someone takes a stock Raspbian or Coder image, they can just run ./build and it sets everything up correctly:

Manages hardware_daemon.py with daemontools
installs all the python deps
uses apache to manage both coder (node.js) and blockly_webserver (flask) for port resolution
Also it nicely serves as a contract of everything blocky talky needs on the os to run safely.
code changes are compatible with current builds (so this is only a patch release candidate).
You can view, comment on, or merge this pull request online at:
https://github.com/tufts-LPC/blockytalky/pull/29
-- Commit Summary --

Fixed build script when building new line of BTUs
Updated build script to do everything I did by hand to make the new BTU image
-- File Changes --
M build (56)
A build.d/blockly_ws.conf (31)
A build.d/blockly_ws.wsgi (4)
A build.d/run (3)
-- Patch Links --
https://github.com/tufts-LPC/blockytalky/pull/29.patch
https://github.com/tufts-LPC/blockytalky/pull/29.diff

Reply to this email directly or view it on GitHub:
https://github.com/tufts-LPC/blockytalky/pull/29


using bower, gulp, etc

If i follow the instructions to use your template, there is no package.json, and not bower.json in my common folder
I want to use Gulp, Karma, Angular Modules (like ngCorodva) etc.
how do I go about this
should I just do an npm init and bower init in the common folder after following your readme instructions?
should I copy the bower.json of your template to my common folder?
am i going about this the wrong way?

you can put package.json and bower.json outside common folder, same level of common folder. treat common folder like the www cordova/ionic folder, everything inside the common folder will end up inside your app/device


Expose atoms version of prebuild atom-oniguruma

Hi,
I'm currently maintaining a grammar extension (react) for atom. I was first using atom-oniguruma for regular expressions, but ended up dropping it as a dependency for the package as building it caused problems for windows users. As a workaround I had to leverage how LanguageMode creates OnigRegExp instances for patterns trough the config apis https://github.com/atom/atom/blob/master/src/language-mode.coffee#L319. This is really hackish and causes the config keys and values to appear in the package settings page.
// when plugin is activated
atom.config.set("react.decreaseIndentForNextLinePattern", decreaseIndentForNextLinePattern)

// And then
decreaseNextLineIndentRegex = languageMode.getRegexForProperty(scopeDescriptor, 'react.decreaseIndentForNextLinePattern')

Would be nice if native atom utility packages could be exposed trough the atom global variable (atom.utils etc.) or if you have other suggestions on how to use atom-oniguruma without causing problems for windows users.
Thanks!

What were the problems that people on Windows were seeing?

Mostly problems with node-gyp (i.e. building the native code). Some of the reports are listed here https://github.com/orktes/atom-react/issues/19


Found a failing seed!

Found a failing seed! Moving this issue to https://github.com/Qiskit/qiskit-terra/issues/4194
from qiskit.quantum_info.random import random_clifford

seed =<PHONE_NUMBER>
num_qubits = 150
random_clifford(num_qubits, seed=seed)

Originally posted by @1ucian0 in https://github.com/Qiskit/qiskit-terra/issues/4126#issuecomment-616708036

Sorry. I submitted by accident while creating #4194


Wrong months in dropdowns before 1995 in iOS

When using the dropdowns options "years : true" and "months : true" i noticed that before 1995 there are issues with the months.
This only seems to happen on mobile iOS devices, i haven't been able to test on desktop Safari as i have no such device.
I have tested this on nl-BE & en-UK locales, it happens on both locales.
For example :

1987 (and a few other years) has no October, and two September's:

1950 has March twice, and no October:

Additional info :
Litepicker V1.5.4
Litepicker config :
var picker = new Litepicker({
                element: this.$refs.dateField,
                lang: app.locale,
                format: this.question.format || "DD/MM/YYYY",
                dropdowns: {
                    minYear: this.question.answers.min || 1900,
                    maxYear: this.question.answers.max || null,
                    months: true,
                    years: true,
                },
                mobileFriendly: true,
                onSelect: function (date) { self.setDate(date); }

            });

fixed in 2.0.1


Registration of first-party endpoint can take up to 6 seconds

For example, using the logging from Letro, we can see it takes 3 seconds on a Pixel 5 (Android 13):
2023-09-18 12:39:44.421 25199-25234 AwalaManager            tech.relaycorp.letro                 I  Will register first-party endpoint...
2023-09-18 12:39:46.906 25199-25199 d$2$serviceConnection$1 tech.relaycorp.letro                 I  Connected to service tech.relaycorp.gateway - tech.relaycorp.gateway.background.endpoint.EndpointPreRegistrationService
2023-09-18 12:39:47.240 25199-25305 TrafficStats            tech.relaycorp.letro                 D  tagSocket(106) with statsTag=0xffffffff, statsUid=-1
2023-09-18 12:39:47.773 25199-25234 AwalaManager            tech.relaycorp.letro                 I  First-party endpoint registered (090f82c63c49a414965797d2b3fbe31b8a540169b615c839f5eec05b2671295b0)

But we've seen around 6 seconds on a Redmi 9A (Android 11) and a Pixel 2 (Android 11). Here's the logs from a Pixel 2:
2023-09-18 13:08:48.227  8799-8910  AwalaManager            tech.relaycorp.letro                 I  Will register first-party endpoint...
2023-09-18 13:08:50.695  8799-9300  ProfileInstaller        tech.relaycorp.letro                 D  Installing profile for tech.relaycorp.letro
2023-09-18 13:08:52.616  8799-8799  d$2$serviceConnection$1 tech.relaycorp.letro                 I  Connected to service tech.relaycorp.gateway - tech.relaycorp.gateway.background.endpoint.EndpointPreRegistrationService
2023-09-18 13:08:54.105  8799-8910  AwalaManager            tech.relaycorp.letro                 I  First-party endpoint registered (02ed16dc77f3717edbe0991cf8d6f8b92d0f4eaa965e83bdfc6b06a2f4cdae574)

I did some initial profiling to assess what could be causing the delays.
On a 3.5 seconds registration the parts that took the most time were:
A) generateRSAKeyPair() ~1 second
B) preRegister sendMessage ~0.5 seconds
C) registerNode ~1 second
D) saveIdentityKey ~0.5 seconds
I feel we don't have a lot of margin to optimize here.

A we would need to lower the complexity of the keys, reducing security?
B and C are actual communications with the other app, maybe with more profiling we could figure out if we could speed up the exchanges? Do you think it's worth investing more time here?
D is probably slower if it's the first time we're setting up the folders and MasterKey, because saving the certificates afterward is quick. This also probably means that the first endpoint to be created, especially on a fresh install, is the worst-case scenario.

I'm surprised that generateRSAKeyPair() takes 1 second 🤯 That's bonkers. But googling Android + Bouncy Castle + KeyPairGenerator + slow does show that this isn't unheard of. :(
Can you please run the same profiling with the oldest Android 6+ device you have? I think that'd be useful to decide whether to spend more time on this -- for example, if the extra 3 seconds are used solely by generateRSAKeyPair(), I'd consider using a security provider other than Bouncy Castle (at least for the key pair creation).

I'm surprised that generateRSAKeyPair() takes 1 second 🤯 That's bonkers. But googling Android + Bouncy Castle + KeyPairGenerator + slow does show that this isn't unheard of. :(
Can you please run the same profiling with the oldest Android 6+ device you have? I think that'd be useful to decide whether to spend more time on this -- for example, if the extra 3 seconds are used solely by generateRSAKeyPair(), I'd consider using a security provider other than Bouncy Castle (at least for the key pair creation).

The worst device I have right now is a Nokia 3.1 with Android 10, and it took 2.5 seconds to run generateRSAKeyPair 😬. So I can imagine it gets worse on older devices. It seems to be the main culprit of the delay, although in theory other cryptographic operations could also take proportionally longer on older devices.


Accessing objects from a .tmdl file for unit tests

What are you trying to achieve?
I aim to facilitate the development of unit tests for our Power BI datasets by converting objects from a .tmdl file into a Python dictionary. This approach will enable us to execute unit tests to ensure that the dataset's model adheres to our expectation and no errors/bugs are introduced. For instance, we want to assert that the column object LOCATION_NAME in the Location table has dataType = string. This effort is crucial for preventing unexpected errors in our dataset.
# Example usage:
# Parse the .tmdl content
parsed_dict = parse_tmdl(tmdl_content)

# Assert that column 'LOCATION_NAME' in table 'Location' has dataType = string
assert parsed_dict['Location']['LOCATION_NAME']['dataType'] == 'string'

# Print the parsed dictionary (for verification)
print(parsed_dict)

What have you tried so far?
I've begun developing a Python script to convert .tmdl files into Python dictionaries. However, I'm encountering challenges with extracting the source element from tables due to multiline issues. I'm seeking guidance on whether someone has already developed a script for this purpose or if there are existing solutions online that I could utilize.

Since this is a Python question, I am not sure how this question relates to Tabular Editor? Maybe I'm missing something?

I was checking if anyone in the community has worked on something similar. I thought this would be the best medium since users familiar with TMDL files would likely be Tabular Editor users. If useful for anyone else. this is what worked for me
`class Tmdl:
def init(self, tmdl_file):
self.tmdl_file = tmdl_file
self.tmdl = self.parse_tmdl(tmdl_file)
def parse_tmdl(self, tmdl_file):
        def get_indentation(line):
            stripped_line = line.strip()
            if not stripped_line:  # Handle empty lines
                return None
            else:
                return len(line) - len(stripped_line)

        with open(tmdl_file, 'r') as file:
            lines = file.readlines()
            lines = [line for line in lines if line.strip()]
        tmdl_dict = {}
        current_level1 = None
        current_level2 = None
        i = 0

        while i < len(lines):

            line = lines[i]
            stripped_line = line.strip()

            indentation = get_indentation(line)

            if indentation == 1:
                # Level 1 - Object Declaration
                current_level1 = stripped_line
                tmdl_dict[current_level1] = {}
            elif indentation == 2:
                # Level 2 - Object Properties and Child Objects
                if stripped_line.endswith('='):
                    property_lines = []
                    property_lines.append(stripped_line)
                    i += 1
                    while i < len(lines):
                        next_line = lines[i]
                        next_stripped_line = next_line.strip()
                        if get_indentation(next_line) > indentation:
                            property_lines.append(next_stripped_line)
                        else:
                            break
                        i += 1

                    combined_property = '\n'.join(property_lines)
                    key, value = combined_property.split('=', 1)
                    tmdl_dict[current_level1][key.strip()] = value.strip()
                    i -= 1  # Step back to process the next line correctly
                elif '=' in stripped_line:
                    # Expression properties
                    key, value = stripped_line.split('=', 1)
                    if i + 1 < len(lines):
                        next_line = lines[i + 1]
                        next_stripped_line = next_line.strip()
                        if next_line.strip():
                            if get_indentation(next_line) > indentation:
                                current_level2 = key.strip()
                                tmdl_dict[current_level1][current_level2] = {}
                                tmdl_dict[current_level1][current_level2]["value"] = value.strip()
                            else:
                                tmdl_dict[current_level1][key.strip()] = value.strip()
                    else:
                        tmdl_dict[current_level1][key.strip()] = value.strip()
                elif ':' in stripped_line:
                    # Non-expression propertiesq
                    key, value = stripped_line.split(':', 1)
                    tmdl_dict[current_level1][key.strip()] = value.strip()
                else:
                    if i + 1 < len(lines):
                        next_line = lines[i + 1]
                        next_stripped_line = next_line.strip()
                        if next_line.strip():
                            if get_indentation(next_line) > indentation:
                                current_level2 = stripped_line
                                tmdl_dict[current_level1][current_level2] = {}
                            else:
                                print("unexpected behaivour")

            elif indentation == 3 and current_level2:
                # Level 3 - Child Object Properties
                if stripped_line.endswith('='):
                    property_lines = []
                    property_lines.append(stripped_line)
                    i += 1
                    while i < len(lines):
                        next_line = lines[i]
                        next_stripped_line = next_line.strip()
                        if not next_stripped_line:  # Skip empty lines
                            i += 1
                            continue
                        if next_stripped_line and get_indentation(next_line) > indentation:
                            property_lines.append(next_stripped_line)
                        else:
                            break
                        i += 1

                    combined_property = '\n'.join(property_lines)
                    key, value = combined_property.split('=', 1)
                    tmdl_dict[current_level1][current_level2][key.strip()] = value.strip()
                    i -= 1  # Step back to process the next line correctly
                elif '=' in stripped_line:
                    # Expression properties
                    key, value = stripped_line.split('=', 1)
                    tmdl_dict[current_level1][current_level2][key.strip()] = value.strip()
                elif ':' in stripped_line:
                    # Non-expression properties
                    key, value = stripped_line.split(':', 1)
                    tmdl_dict[current_level1][current_level2][key.strip()] = value.strip()

            i += 1

        return tmdl_dict

`

Thanks for sharing your solution :-)


plural support

Hi,
First thank you for the fantastic orm library. I'm from RoR background, and therefore quite picky about the correct plural format. Seems there are some words that are not supported very well. Like:
criterion => criteria
media => media
Thanks advance for the fix!

Hi @jasonzhao3
Thank you for your suggestion, just changed gorm's default plural engine to github.com/qor/inflection, which has exactly rules with the rails one.
And it provide the ability for your to change its rules.
Thank you.


[BUG] Framerate option does not uncap framerate

Acknowledgement of preliminary instructions

[X] I have read the preliminary instructions, and I am certain that my problem has not already been addressed.

What problem did you encounter?
If I try and set the framerate option to anything other than zero (I tried 9999, 999, 500, and 240) and hit save, the next time I join the game it remains capped at 60 fps despite what I have set it to.

Did you read https://github.com/pizzaboxer/bloxstrap/wiki/Roblox-is-still-capped-to-60-FPS-after-raising-the-limiter?

nor had I been able to find it when I did a quick search prior to posting the issue.

Read the preliminary instructions next time before you open an issue.


@conda-forge-admin, please add bot automerge

Additional comment:
@conda-forge-admin, please add bot automerge

Hi! This is the friendly automated conda-forge-webservice.
I just wanted to let you know that I added bot automerge in conda-forge/e3nn-feedstock#6.


Add admin nav-bar to event page

With both Edit and Reported comments already available and the need to add addtional admin-only menu items, it makes sense to move them to their own nav-bar under the attendee-facing nav-bar.
I've also added the nav-bar to the edit event page as it was missing. This meant separating the nav-bar rendering from the event header template, so I could reuse it.
Finally, for consistency, I've also moved the nav-bar on the Events listing page to below the title too and made it so that there's always a border at the bottom of a nav-bar, but never a situation where we have two borders with no text between them.

Closing as we have the admin bar coming in with 338 in any case


[stdlib] Defines a module for Move Version on chain config.

Motivation
Create a module to store the version of Libra software run by the validators.
Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan
Added test for reading and updating the config.

On the minor version question: for what it's worth the LUP proposal says:

The Association is able to upgrade all nodes to the latest binary and there is no need to interoperate among binary versions.

This makes me wonder if we want/need a Move version number that's separate from the version of the Libra binary as a whole ? I could see the motivation for a Move version number given that there may be uses of Move outside of Libra. But it seems like (a) a Move version change will always be a Libra version change, and (b) there may be Libra version changes that are not a Move version change (e.g., change to the networking protocol).

On the minor version question: for what it's worth the LUP proposal says:

The Association is able to upgrade all nodes to the latest binary and there is no need to interoperate among binary versions.

This makes me wonder if we want/need a Move version number that's separate from the version of the Libra binary as a whole ? I could see the motivation for a Move version number given that there may be uses of Move outside of Libra. But it seems like (a) a Move version change will always be a Libra version change, and (b) there may be Libra version changes that are not a Move version change (e.g., change to the networking protocol).

The main reason why I put out a separate move version number is because we want to have Move to be somewhat independent of the libra version. It seems like the difference between versions of jvm vs jre to me.

Definitely agree that the Move version should be independent from the Libra version in the sense that not all Libra updates are Move updates ((b) above).
But I do think it's the case that every update to Move that we would like to pull into Libra[1] needs to be a Libra version bump ((a) above).

Do you agree with this?
If so, does it make sense to store the Libra version on chain instead? My expectation would be that validators would keep binaries of multiple Libra versions locally and then use the on-chain version value to decide when to switch binaries. That makes sense to me if the number represents the Libra version, but I'm not sure how that would work if there are version numbers for both Libra and Move

[1] If Move is a separate project from Libra, I fully expect that there might be Move version bumps that Libra chooses not to pull in for awhile. But I don't think we need an on-chain representation of this Move version (unless I'm missing something).

are

Ah I think we are having different views on how the version flag is gonna work. In your description, versioning flag is more like a specifier that tells us which binary to run. I was thinking that this number will look more like feature flag so that we will have something like
if version > x.y {
  new feature logic
} else {
  old logic
}

Going back to the quote, we suggest that:

The Association is able to upgrade all nodes to the latest binary and there is no need to interoperate among binary versions.
One thing I'm not sure is whether this statement will stay true at all time, as if this is the case every upgrade will become stop-the-world update as we need to pause the entire network to deploy the new binary and restart back together at the same time. I would imagine that we will use the version flag so that we can do the binary updates of validators asynchronously.

One thing I'm not sure is whether this statement will stay true at all time

I think this is a key question--let's ask @zekun000?

if version > x.y {
  new feature logic
} else {
  old logic
}

FWIW: In my understanding, this is exactly how it would work if version is the protocol version for Libra. But I'm not sure what it would mean to have different on-chain version vars for Libra and Move (as discussed above).

sorry if this quote is confusing, I'll update correspondingly

The Association is able to upgrade all nodes to the latest binary and there is no need to interoperate among binary versions.

I meant to say protocols with different version don't have to interoperate, but a binary may contain two protocol implementation for smooth upgrades.
ConsensusV2 can only operate with V2, but a binary may contain both V1 and V2 and do the switch based on on-chain value.

But I do think it's the case that every update to Move that we would like to pull into Libra[1] needs to be a Libra version bump ((a) above).

I would agree with this. With that being said, it still seems pretty weird to me not having a Move version. The reason is that each Script/Module sent from a transaction will contain a Move version number and it will be pretty hard to link it to the Libra network's version number. It would also be pretty weird if we view that version number as Libra version because that implies Script's version number should be bumped when we have a protocol change on the validator side.

my take here  - and if I understand what @zekun000 was saying I agree with his statement ;) -
We can use a single version if that was better and "unify" versions as much as needed (not sure it is a need but there...).
I think however the issue is when binary changes are backward compatible and offer new behavior.
In that case we want an on-chain value that is "triggered" once you know all validators have updated.
In that sense a more reasonable upgrade story.
E.g.: you can imagine we change something over returning of references in the VM and we want to upgrade the verifier.
That obviously requires new binaries but you want a more clear point when the new behavior is started. An on-chain flag.
That is what the Move version was or it could be used for.
Or at least that is what @runtian-zhou and I concluded when we talked.
As for the major/minor it was all just a guess so if someone can think about it let's make it whatever is more proper

Update after a bunch of discussions with @sblackshear and @dariorussi , it seems to me that we definitely need one version number to perform the gatekeeping logic for the software run on the Libra validator nodes.
It is unclear to us if a separate Move version is needed, as we can derive the Move version number just by looking at the LibraVersion if we really need it.

:umbrella: The latest upstream changes (presumably d171a27b6febcf9b5476de3c265f1bbc8c51810b) made this pull request unmergeable. Please resolve the merge conflicts.

is this ready to go in?

:umbrella: The latest upstream changes (presumably 236d747f3bcd4a74beb695848adfbd12bbdc6780) made this pull request unmergeable. Please resolve the merge conflicts.

@bors-libra r=sblackshear

:pushpin: Commit 786a358 has been approved by sblackshear

:hourglass: Testing commit 786a358bdf6a5cd6d50614ef865c82459f56051f with merge ea984bcef9beead667d06b50278a9a8d8549b202...

:sunny: Test successful - checks-actions_land_blocking_test, checks-circle_commit_workflow
Approved by: sblackshear
Pushing ea984bcef9beead667d06b50278a9a8d8549b202 to master...


WW-5288 follow-up test case updates

Update:

Add a few additional tests to SecurityMemberAccessTest.
Rename some existing tests involving non-static methods to more accurately reflect that.
Add one minor optimization to SecurityMemberAccess.

Hello Apache Struts Team.
I am unsure whether I understood everything that changed with WW-5288.  However, after taking a look at the related unit tests, it seemed like a few additions and clarifications might make sense.
This PR attempts to add a few additional tests, as well a potential minor optimization.
Please review the PR and advise if it could be considered (and if any changes are recommended).
Note: Again, it seems there was a "sonar-maven-plugin" failure for the Java 11 build environment run, but the build itself seems to have completed OK.


Doc update

Site folder is generated using mkdocs build which this pr will update gh-pages branch which will be github pages https://yahoo.github.io/athenz/

👍


⚠ Adacta-fintech.com has degraded performance

In 085a8e6, Adacta-fintech.com (https://www.adacta-fintech.com) experienced degraded performance:

HTTP code: 502
Response time: 675 ms

Resolved: Adacta-fintech.com performance has improved in ced7050.