text:
Adapter keeps disconnecting / restarting.

Seems that tado is working at their servers and there is not much that can be done from adapters perspective.
I'm posting the log file anyways...
2022-06-10 20:56:09.849  - info: tado.0 (79566) Initialisation finished, connected to Tado cloud service refreshing every 62 seconds
2022-06-10 21:01:13.524  - error: tado.0 (79566) Error: connect ETIMEDOUT 52.214.244.17:443
2022-06-10 21:01:13.528  - error: tado.0 (79566) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2022-06-10 21:01:13.528  - error: tado.0 (79566) unhandled promise rejection: connect ETIMEDOUT 52.214.244.17:443
2022-06-10 21:01:13.529  - error: tado.0 (79566) Error: connect ETIMEDOUT 52.214.244.17:443
    at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1229:16)
2022-06-10 21:01:13.529  - error: tado.0 (79566) Exception-Code: ETIMEDOUT: connect ETIMEDOUT 52.214.244.17:443
2022-06-10 21:01:13.565  - info: tado.0 (79566) cleaned everything up...
2022-06-10 21:01:13.567  - info: tado.0 (79566) terminating
2022-06-10 21:01:13.568  - warn: tado.0 (79566) Terminated (UNCAUGHT_EXCEPTION): Without reason
2022-06-10 21:01:14.171  - error: host.chet Caught by controller[1]: Error: connect ETIMEDOUT 52.214.244.17:443
2022-06-10 21:01:14.172  - error: host.chet Caught by controller[1]:     at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1229:16) {
2022-06-10 21:01:14.172  - error: host.chet Caught by controller[1]:   errno: -110,
2022-06-10 21:01:14.172  - error: host.chet Caught by controller[1]:   code: 'ETIMEDOUT',
2022-06-10 21:01:14.172  - error: host.chet Caught by controller[1]:   syscall: 'connect',
2022-06-10 21:01:14.172  - error: host.chet Caught by controller[1]:   address: '52.214.244.17',
2022-06-10 21:01:14.173  - error: host.chet Caught by controller[1]:   port: 443,
2022-06-10 21:01:14.173  - error: host.chet Caught by controller[1]:   config: {
2022-06-10 21:01:14.173  - error: host.chet Caught by controller[1]:     transitional: {
2022-06-10 21:01:14.173  - error: host.chet Caught by controller[1]:       silentJSONParsing: true,
2022-06-10 21:01:14.174  - error: host.chet Caught by controller[1]:       forcedJSONParsing: true,
2022-06-10 21:01:14.174  - error: host.chet Caught by controller[1]:       clarifyTimeoutError: false
2022-06-10 21:01:14.174  - error: host.chet Caught by controller[1]:     },
2022-06-10 21:01:14.174  - error: host.chet Caught by controller[1]:     adapter: [Function: httpAdapter],
2022-06-10 21:01:14.174  - error: host.chet Caught by controller[1]:     transformRequest: [ [Function: transformRequest] ],
2022-06-10 21:01:14.174  - error: host.chet Caught by controller[1]:     transformResponse: [ [Function: transformResponse] ],
2022-06-10 21:01:14.175  - error: host.chet Caught by controller[1]:     timeout: 0,
2022-06-10 21:01:14.175  - error: host.chet Caught by controller[1]:     xsrfCookieName: 'XSRF-TOKEN',
2022-06-10 21:01:14.175  - error: host.chet Caught by controller[1]:     xsrfHeaderName: 'X-XSRF-TOKEN',
2022-06-10 21:01:14.175  - error: host.chet Caught by controller[1]:     maxContentLength: -1,
2022-06-10 21:01:14.175  - error: host.chet Caught by controller[1]:     maxBodyLength: -1,
2022-06-10 21:01:14.175  - error: host.chet Caught by controller[1]:     validateStatus: [Function: validateStatus],
2022-06-10 21:01:14.175  - error: host.chet Caught by controller[1]:     headers: {
2022-06-10 21:01:14.176  - error: host.chet Caught by controller[1]:       Accept: 'application/json, text/plain, */*',
2022-06-10 21:01:14.176  - error: host.chet Caught by controller[1]:       Authorization: 'Bearer YpQ145N1vNbcVKNUABSyKcEhivX0m1gORTRIDLR_6ULuMLZTqz5HmsaSeXAhgk4b2MnpdnIa7G9gT0ff3K7DL0fXWbJARdOLeaVLzlB8sn020_DUITZ3caSXg4FlTNkDXbBl04_E_24i4SHKxaK3ncn9br72eC_5eUXKbvj47OkEidFv5fx8OABtEGp16-adGc14MhrC_z6LcQMuFmaFiPZFLKbOJsWyJU3HhOEXyJ_ZcEXYUqbb_GIMecuJauLMXt0dwUAlXtjcWMU1QrjsXLH-dRpqnuxC_5yISOj4__QSQ96O2Om8_s1g',
2022-06-10 21:01:14.176  - error: host.chet Caught by controller[1]:       'Content-Type': 'application/json',
2022-06-10 21:01:14.176  - error: host.chet Caught by controller[1]:       'User-Agent': 'axios/0.26.1',
2022-06-10 21:01:14.176  - error: host.chet Caught by controller[1]:       'Content-Length': 2
2022-06-10 21:01:14.177  - error: host.chet Caught by controller[1]:     },
2022-06-10 21:01:14.177  - error: host.chet Caught by controller[1]:     url: 'https://my.tado.com/api/v2/devices/VA1030948096/temperatureOffset',
2022-06-10 21:01:14.177  - error: host.chet Caught by controller[1]:     method: 'get',
2022-06-10 21:01:14.177  - error: host.chet Caught by controller[1]:     data: '{}'
2022-06-10 21:01:14.177  - error: host.chet Caught by controller[1]:   },
2022-06-10 21:01:14.178  - error: host.chet Caught by controller[1]:   request: <ref *1> Writable {
2022-06-10 21:01:14.178  - error: host.chet Caught by controller[1]:     _writableState: WritableState {
2022-06-10 21:01:14.178  - error: host.chet Caught by controller[1]:       objectMode: false,
2022-06-10 21:01:14.178  - error: host.chet Caught by controller[1]:       highWaterMark: 16384,
2022-06-10 21:01:14.178  - error: host.chet Caught by controller[1]:       finalCalled: false,
2022-06-10 21:01:14.178  - error: host.chet Caught by controller[1]:       needDrain: false,
2022-06-10 21:01:14.178  - error: host.chet Caught by controller[1]:       ending: false,
2022-06-10 21:01:14.179  - error: host.chet Caught by controller[1]:       ended: false,
2022-06-10 21:01:14.179  - error: host.chet Caught by controller[1]:       finished: false,
2022-06-10 21:01:14.179  - error: host.chet Caught by controller[1]:       destroyed: false,
2022-06-10 21:01:14.179  - error: host.chet Caught by controller[1]:       decodeStrings: true,
2022-06-10 21:01:14.179  - error: host.chet Caught by controller[1]:       defaultEncoding: 'utf8',
2022-06-10 21:01:14.179  - error: host.chet Caught by controller[1]:       length: 0,
2022-06-10 21:01:14.180  - error: host.chet Caught by controller[1]:       writing: false,
2022-06-10 21:01:14.180  - error: host.chet Caught by controller[1]:       corked: 0,
2022-06-10 21:01:14.180  - error: host.chet Caught by controller[1]:       sync: true,
2022-06-10 21:01:14.180  - error: host.chet Caught by controller[1]:       bufferProcessing: false,
2022-06-10 21:01:14.180  - error: host.chet Caught by controller[1]:       onwrite: [Function: bound onwrite],
2022-06-10 21:01:14.180  - error: host.chet Caught by controller[1]:       writecb: null,
2022-06-10 21:01:14.180  - error: host.chet Caught by controller[1]:       writelen: 0,
2022-06-10 21:01:14.181  - error: host.chet Caught by controller[1]:       afterWriteTickInfo: null,
2022-06-10 21:01:14.181  - error: host.chet Caught by controller[1]:       buffered: [],
2022-06-10 21:01:14.181  - error: host.chet Caught by controller[1]:       bufferedIndex: 0,
2022-06-10 21:01:14.181  - error: host.chet Caught by controller[1]:       allBuffers: true,
2022-06-10 21:01:14.181  - error: host.chet Caught by controller[1]:       allNoop: true,
2022-06-10 21:01:14.181  - error: host.chet Caught by controller[1]:       pendingcb: 0,
2022-06-10 21:01:14.181  - error: host.chet Caught by controller[1]:       constructed: true,
2022-06-10 21:01:14.181  - error: host.chet Caught by controller[1]:       prefinished: false,
2022-06-10 21:01:14.181  - error: host.chet Caught by controller[1]:       errorEmitted: false,
2022-06-10 21:01:14.182  - error: host.chet Caught by controller[1]:       emitClose: true,
2022-06-10 21:01:14.182  - error: host.chet Caught by controller[1]:       autoDestroy: true,
2022-06-10 21:01:14.182  - error: host.chet Caught by controller[1]:       errored: null,
2022-06-10 21:01:14.182  - error: host.chet Caught by controller[1]:       closed: false,
2022-06-10 21:01:14.182  - error: host.chet Caught by controller[1]:       closeEmitted: false,
2022-06-10 21:01:14.182  - error: host.chet Caught by controller[1]:       [Symbol(kOnFinished)]: []
2022-06-10 21:01:14.182  - error: host.chet Caught by controller[1]:     },
2022-06-10 21:01:14.182  - error: host.chet Caught by controller[1]:     _events: [Object: null prototype] {
2022-06-10 21:01:14.182  - error: host.chet Caught by controller[1]:       response: [Function: handleResponse],
2022-06-10 21:01:14.183  - error: host.chet Caught by controller[1]:       error: [Function: handleRequestError],
2022-06-10 21:01:14.183  - error: host.chet Caught by controller[1]:       socket: [Function: handleRequestSocket]
2022-06-10 21:01:14.183  - error: host.chet Caught by controller[1]:     },
2022-06-10 21:01:14.183  - error: host.chet Caught by controller[1]:     _eventsCount: 3,
2022-06-10 21:01:14.183  - error: host.chet Caught by controller[1]:     _maxListeners: 100,
2022-06-10 21:01:14.183  - error: host.chet Caught by controller[1]:     _options: {
2022-06-10 21:01:14.183  - error: host.chet Caught by controller[1]:       maxRedirects: 21,
2022-06-10 21:01:14.183  - error: host.chet Caught by controller[1]:       maxBodyLength: 10485760,
2022-06-10 21:01:14.183  - error: host.chet Caught by controller[1]:       protocol: 'https:',
2022-06-10 21:01:14.183  - error: host.chet Caught by controller[1]:       path: '/api/v2/devices/VA1030948096/temperatureOffset',
2022-06-10 21:01:14.184  - error: host.chet Caught by controller[1]:       method: 'GET',
2022-06-10 21:01:14.184  - error: host.chet Caught by controller[1]:       headers: [Object],
2022-06-10 21:01:14.184  - error: host.chet Caught by controller[1]:       agent: undefined,
2022-06-10 21:01:14.184  - error: host.chet Caught by controller[1]:       agents: [Object],
2022-06-10 21:01:14.184  - error: host.chet Caught by controller[1]:       auth: undefined,
2022-06-10 21:01:14.184  - error: host.chet Caught by controller[1]:       hostname: 'my.tado.com',
2022-06-10 21:01:14.184  - error: host.chet Caught by controller[1]:       port: null,
2022-06-10 21:01:14.184  - error: host.chet Caught by controller[1]:       nativeProtocols: [Object],
2022-06-10 21:01:14.184  - error: host.chet Caught by controller[1]:       pathname: '/api/v2/devices/VA1030948096/temperatureOffset'
2022-06-10 21:01:14.184  - error: host.chet Caught by controller[1]:     },
2022-06-10 21:01:14.185  - error: host.chet Caught by controller[1]:     _ended: false,
2022-06-10 21:01:14.185  - error: host.chet Caught by controller[1]:     _ending: true,
2022-06-10 21:01:14.185  - error: host.chet Caught by controller[1]:     _redirectCount: 0,
2022-06-10 21:01:14.185  - error: host.chet Caught by controller[1]:     _redirects: [],
2022-06-10 21:01:14.185  - error: host.chet Caught by controller[1]:     _requestBodyLength: 2,
2022-06-10 21:01:14.185  - error: host.chet Caught by controller[1]:     _requestBodyBuffers: [ [Object] ],
2022-06-10 21:01:14.185  - error: host.chet Caught by controller[1]:     _onNativeResponse: [Function (anonymous)],
2022-06-10 21:01:14.185  - error: host.chet Caught by controller[1]:     _currentRequest: ClientRequest {
2022-06-10 21:01:14.185  - error: host.chet Caught by controller[1]:       _events: [Object: null prototype],
2022-06-10 21:01:14.185  - error: host.chet Caught by controller[1]:       _eventsCount: 7,
2022-06-10 21:01:14.186  - error: host.chet Caught by controller[1]:       _maxListeners: 100,
2022-06-10 21:01:14.186  - error: host.chet Caught by controller[1]:       outputData: [],
2022-06-10 21:01:14.186  - error: host.chet Caught by controller[1]:       outputSize: 0,
2022-06-10 21:01:14.186  - error: host.chet Caught by controller[1]:       writable: true,
2022-06-10 21:01:14.186  - error: host.chet Caught by controller[1]:       destroyed: false,
2022-06-10 21:01:14.186  - error: host.chet Caught by controller[1]:       _last: true,
2022-06-10 21:01:14.186  - error: host.chet Caught by controller[1]:       chunkedEncoding: false,
2022-06-10 21:01:14.186  - error: host.chet Caught by controller[1]:       shouldKeepAlive: false,
2022-06-10 21:01:14.186  - error: host.chet Caught by controller[1]:       maxRequestsOnConnectionReached: false,
2022-06-10 21:01:14.186  - error: host.chet Caught by controller[1]:       _defaultKeepAlive: true,
2022-06-10 21:01:14.187  - error: host.chet Caught by controller[1]:       useChunkedEncodingByDefault: false,
2022-06-10 21:01:14.187  - error: host.chet Caught by controller[1]:       sendDate: false,
2022-06-10 21:01:14.187  - error: host.chet Caught by controller[1]:       _removedConnection: false,
2022-06-10 21:01:14.187  - error: host.chet Caught by controller[1]:       _removedContLen: false,
2022-06-10 21:01:14.187  - error: host.chet Caught by controller[1]:       _removedTE: false,
2022-06-10 21:01:14.187  - error: host.chet Caught by controller[1]:       _contentLength: null,
2022-06-10 21:01:14.187  - error: host.chet Caught by controller[1]:       _hasBody: true,
2022-06-10 21:01:14.187  - error: host.chet Caught by controller[1]:       _trailer: '',
2022-06-10 21:01:14.187  - error: host.chet Caught by controller[1]:       finished: false,
2022-06-10 21:01:14.187  - error: host.chet Caught by controller[1]:       _headerSent: true,
2022-06-10 21:01:14.188  - error: host.chet Caught by controller[1]:       _closed: false,
2022-06-10 21:01:14.188  - error: host.chet Caught by controller[1]:       socket: [TLSSocket],
2022-06-10 21:01:14.188  - error: host.chet Caught by controller[1]:       _header: 'GET /api/v2/devices/VA1030948096/temperatureOffset HTTP/1.1\r\n' +
2022-06-10 21:01:14.188  - error: host.chet Caught by controller[1]:         'Accept: application/json, text/plain, */*\r\n' +
2022-06-10 21:01:14.188  - error: host.chet Caught by controller[1]:         'Authorization: Bearer UITZ3caSXg4FlTNkDXbBl04_E_24i4SHKxaK3ncn9br72eC_5eUXKbvj47OkEidFv5fx8OABtEGp16-adGc14MhrC_z6LcQMuFmaFiPZFLKbOJsWyJU3HhOEXyJ_ZcEXYUqbb_GIMecuJauLMXt0dwUAlXtjcWMU1QrjsXLH-dRpqnuxC_5yISOj4__QSQ96O2Om8_s1g\r\n' +
2022-06-10 21:01:14.188  - error: host.chet Caught by controller[1]:         'Content-Type: application/json\r\n' +
2022-06-10 21:01:14.188  - error: host.chet Caught by controller[1]:         'User-Agent: axios/0.26.1\r\n' +
2022-06-10 21:01:14.188  - error: host.chet Caught by controller[1]:         'Content-Length: 2\r\n' +
2022-06-10 21:01:14.188  - error: host.chet Caught by controller[1]:         'Host: my.tado.com\r\n' +
2022-06-10 21:01:14.189  - error: host.chet Caught by controller[1]:         'Connection: close\r\n' +
2022-06-10 21:01:14.189  - error: host.chet Caught by controller[1]:         '\r\n',
2022-06-10 21:01:14.189  - error: host.chet Caught by controller[1]:       _keepAliveTimeout: 0,
2022-06-10 21:01:14.189  - error: host.chet Caught by controller[1]:       _onPendingData: [Function: nop],
2022-06-10 21:01:14.189  - error: host.chet Caught by controller[1]:       agent: [Agent],
2022-06-10 21:01:14.189  - error: host.chet Caught by controller[1]:       socketPath: undefined,
2022-06-10 21:01:14.189  - error: host.chet Caught by controller[1]:       method: 'GET',
2022-06-10 21:01:14.189  - error: host.chet Caught by controller[1]:       maxHeaderSize: undefined,
2022-06-10 21:01:14.189  - error: host.chet Caught by controller[1]:       insecureHTTPParser: undefined,
2022-06-10 21:01:14.189  - error: host.chet Caught by controller[1]:       path: '/api/v2/devices/VA1030948096/temperatureOffset',
2022-06-10 21:01:14.190  - error: host.chet Caught by controller[1]:       _ended: false,
2022-06-10 21:01:14.190  - error: host.chet Caught by controller[1]:       res: null,
2022-06-10 21:01:14.190  - error: host.chet Caught by controller[1]:       aborted: false,
2022-06-10 21:01:14.190  - error: host.chet Caught by controller[1]:       timeoutCb: null,
2022-06-10 21:01:14.190  - error: host.chet Caught by controller[1]:       upgradeOrConnect: false,
2022-06-10 21:01:14.190  - error: host.chet Caught by controller[1]:       parser: null,
2022-06-10 21:01:14.190  - error: host.chet Caught by controller[1]:       maxHeadersCount: null,
2022-06-10 21:01:14.190  - error: host.chet Caught by controller[1]:       reusedSocket: false,
2022-06-10 21:01:14.190  - error: host.chet Caught by controller[1]:       host: 'my.tado.com',
2022-06-10 21:01:14.190  - error: host.chet Caught by controller[1]:       protocol: 'https:',
2022-06-10 21:01:14.191  - error: host.chet Caught by controller[1]:       _redirectable: [Circular *1],
2022-06-10 21:01:14.191  - error: host.chet Caught by controller[1]:       [Symbol(kCapture)]: false,
2022-06-10 21:01:14.191  - error: host.chet Caught by controller[1]:       [Symbol(kNeedDrain)]: false,
2022-06-10 21:01:14.191  - error: host.chet Caught by controller[1]:       [Symbol(corked)]: 0,
2022-06-10 21:01:14.191  - error: host.chet Caught by controller[1]:       [Symbol(kOutHeaders)]: [Object: null prototype],
2022-06-10 21:01:14.191  - error: host.chet Caught by controller[1]:       [Symbol(kUniqueHeaders)]: null
2022-06-10 21:01:14.191  - error: host.chet Caught by controller[1]:     },
2022-06-10 21:01:14.191  - error: host.chet Caught by controller[1]:     _currentUrl: 'https://my.tado.com/api/v2/devices/VA1030948096/temperatureOffset',
2022-06-10 21:01:14.191  - error: host.chet Caught by controller[1]:     [Symbol(kCapture)]: false
2022-06-10 21:01:14.192  - error: host.chet Caught by controller[1]:   },
2022-06-10 21:01:14.192  - error: host.chet Caught by controller[1]:   response: undefined,
2022-06-10 21:01:14.192  - error: host.chet Caught by controller[1]:   isAxiosError: true,
2022-06-10 21:01:14.192  - error: host.chet Caught by controller[1]:   toJSON: [Function: toJSON]
2022-06-10 21:01:14.192  - error: host.chet Caught by controller[1]: }
2022-06-10 21:01:14.192  - error: host.chet Caught by controller[2]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
2022-06-10 21:01:14.192  - error: host.chet Caught by controller[3]: Error: connect ETIMEDOUT 52.214.244.17:443
2022-06-10 21:01:14.192  - error: host.chet Caught by controller[3]:     at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1229:16)
2022-06-10 21:01:14.192  - error: host.chet instance system.adapter.tado.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
2022-06-10 21:01:14.193  - info: host.chet Restart adapter system.adapter.tado.0 because enabled
2022-06-10 21:01:44.327  - info: host.chet instance system.adapter.tado.0 started with pid 82102
2022-06-10 21:01:46.694  - info: tado.0 (82102) starting. Version 0.3.15 in /opt/iobroker/node_modules/iobroker.tado, node: v18.3.0, js-controller: 4.0.23
2022-06-10 21:01:46.738  - info: tado.0 (82102) Started with JSON-Explorer version 0.1.9
2022-06-10 21:01:47.459  - info: tado.0 (82102) Connected to Tado cloud, initialyzing...
2022-06-10 21:02:02.466  - info: tado.0 (82102) Initialisation finished, connected to Tado cloud service refreshing every 62 seconds
2022-06-10 21:15:48.058  - error: tado.0 (82102) Error: connect ETIMEDOUT 52.214.244.17:443
2022-06-10 21:15:48.068  - error: tado.0 (82102) Error in data refresh at step DoZones: Error: connect ETIMEDOUT 52.214.244.17:443
2022-06-10 21:15:48.070  - error: tado.0 (82102) Disconnected from Tado cloud service ..., retry in 30 seconds !
2022-06-10 21:16:18.550  - info: tado.0 (82102) Connected to Tado cloud, initialyzing...
2022-06-10 21:16:30.243  - info: tado.0 (82102) Initialisation finished, connected to Tado cloud service refreshing every 62 seconds

Sieht danach aus das die api nicht reagiert, issue nog aktuell ?

Hab den Adapter über Nacht ausgeschaltet, die Meldungen sind aber heute Vormittag unverändert wieder da.

My Tado-adapter works fine without any errors or warning.
I suggest to check your network, maybe a router/server restart will help.
I do not think that I can improve something on the adapter side.

Ich bin blöd!
Ich habe eine zweiten ioBroker-Installation auf einem anderen Host als 'Digitalen Zwilling'. Da ist eigentlich der Auto-Start beim boot ausgeschaltet, damit der nicht herumspukt. Nach einem 'iobroker fix' war der service aber auf enabled und spukte herum.
Hab den jetzt wieder auf Eis gelegt, läuft wieder.
Sorry für das dämliche Issue von mir!

Sorry für das dämliche Issue von mir!

no worries, ich marke das issue mal as "Good First" andere werden bestimmt auch mal eine derartige situation haben :)

Sorry für das dämliche Issue von mir!

no worries, ich marke das issue mal as "Good First" andere werden bestimmt auch mal eine derartige situation haben :)


text:
Installing the official plugins

Hi, I want to install the borders-plus-plus and csgo-vulkan-fix official plugins. What would be the correct approach to using hyprload for this. I tried to add "hyprwm/hyprland-plugins" to the hyprload.toml file, but I get an error saying that there is no manifest file for hyprland-plugins.

I figured it out, I had to specify which plugin to install using this:
{ git = "https://github.com/hyprwm/hyprland-plugins.git", branch = "main", name = "borders-plus-plus" }

source: gharchive/issue

repo: Duckonaut/hyprload

license_type: permissive

license_source: github-api


text:
Dena bhai for import

Description
Using  dena bhai  for importing any thing
Domain
Bhai Lang
Type of Contribution
Enhancement
Code of Conduct

[X] I follow Contributing Guidelines & Code of conduct of bhai-lang.

Alternate Syntax for imports at #97

No current plans to add this feature in this language as this will lead to more complexities in this toy language.

repo: DulLabs/bhai-lang

license: MIT


text:
[FEATURE] Smoother animation when showing the results

What would you like to share?
Make the slide animation of the results more smoother
Additional information
No response

It's great having you contribute to this project by creating an issue Make sure you are assigned to this before you work on it and you read the Contributing.md file, Thank you! Welcome to the community :nerd_face:

Can i work on this one thanks

Let's see a preview first🙌🏽

Done I've added a video preview

Done I've added a video preview

I fail to see the difference 🙂 did you just increase the time?

Oh you mean the one where i changed it
Here:
https://user-images.githubusercontent.com/79793867/193443745-5ca0f811-2b80-4372-8b86-8fccbfac111c.mp4

Oh you mean the one where i changed it
Here:
https://user-images.githubusercontent.com/79793867/193443757-80bb4f41-391a-448b-a12f-16cee51fa2c4.mp4

Oh you mean the one where i changed it
Here:
https://user-images.githubusercontent.com/79793867/193443757-80bb4f41-391a-448b-a12f-16cee51fa2c4.mp4

Yes I meant your change lol

Looks good make a pr

Alright coming up, thanks!

:tada: This issue has been resolved in version 2.2.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

authors: Dun-sin alicalimli

repo: Dun-sin/Code-Magic


text:
Fix Module Names

Some modules fail to autoload on case-sensative linux or mac servers. Change the __autoload function to include a string to lower function, and move all files to a lowercase format.

If / when you merge my outgauge branch the strtolower() part will be patched.
Filenames of modules are already in lower case.

Fixed with merge from VictorVanV's branch.

authors: Dygear VictorVanV

repo: Dygear/PRISM

license: mit

license_source: bigquery


text:
Custom Resource - metdata name

I have copied the example Custom Resource, While applying the CR's on OpenShift the 'metadata: name:' must be dynakube.
If you change the name, the CR will not create the DaemonSets.
This was discovered while trying to deploy the multiDynakube.yaml, the metdata/name have  dynakube-application-monitoring and dynakube-cloud-native. If you apply the CR, nothing happens.
I applied cloudNativeFullStack.yaml, DaemonSet is created. Change the metadata/name to dynatrace-full, nothing happens, no DaemonSet or additional Pods. (dynakube-oneagent)

Use the spec.tokens field (described in the samples) if the Secret containing the tokens has a different name than the Dynakube.

authors: chrismuellner tony-advent

repo: Dynatrace/dynatrace-operator


text:
Replace CDAT

https://github.com/conda-forge/cdtime-feedstock/pull/52 mentions that we need to replace CDAT in zppy. Note that we already have #80, which is specifically about cdscan.

@tomvothecoder I'm not quite sure what needs to be done for zppy.
$ git grep -n cdscan
docs/source/dev_guide/new_diags_set.rst:100:        cdscan -x ${xml_name} ${rofDir}/${v}_*.nc
zppy/templates/e3sm_diags.bash:104:        # Add this time series file to the list of files for cdscan to use
zppy/templates/e3sm_diags.bash:111:    cdscan -x ${xml_name} -f ${v}_files.txt
zppy/templates/e3sm_diags.bash:132:  cdscan -x ${xml_name} ${ts_rof_dir_source}/${v}_*.nc
zppy/templates/global_time_series.bash:46:cdscan -x glb.xml *.nc
zppy/templates/global_time_series.bash:70:    cdscan -x glb.xml mpaso.glb*.nc

$ git grep -n cdat
# No matches

$ git grep -n cdms
zppy/templates/readTS.py:1:import cdms2
zppy/templates/readTS.py:10:        self.f = cdms2.open(filename)

$ emacs conda/dev.yml
# No dependencies appear obviously related to cdat

$ emacs conda/meta.yml
# No dependencies appear obviously related to cdat

@forsyth2 I don't have familiarity with the zppy codebase to give input on what needs to be done specifically.
My general approach to refactoring is to identify what needs to be refactored, understand the implementation, and find alternative solutions that would reproduce the same/similar results.

It looks like you identified the CDAT modules that are used in zppy, which is a good first step. Luckily, the dependency is not that significant from what I can tell.

Ok, great!
https://cdat.llnl.gov/ lists "specific CDAT packages (cdms2, cdat_info, cdutil, cdtime, genutil, libcdms)". Out of those, it looks like zppy has:
$ git grep -n cdms2
zppy/templates/readTS.py:1:import cdms2
zppy/templates/readTS.py:10:        self.f = cdms2.open(filename)

$ git grep -n cdutil
zppy/templates/readTS.py:2:import cdutil
zppy/templates/readTS.py:65:            v = cdutil.YEAR(v)

So, basically I just need replacements for cdcscan, cdms2.open, and cdutil.YEAR.

Those are the packages who's dependencies are being maintained until end of CY2023.
I doubt zppy uses other modules from CDAT. It might be a good idea to check other modules that operate on cdms2 objects, like MV2.

Example from e3sm_diags:  https://github.com/E3SM-Project/e3sm_diags/discussions/607
Complete list of CDAT modules: https://anaconda.org/cdat/repo

Thanks, out of the list at https://anaconda.org/cdat/repo, we just have:
$ git grep -n cdms2
zppy/templates/readTS.py:1:import cdms2
zppy/templates/readTS.py:10:        self.f = cdms2.open(filename)

$ git grep -n cdutil
zppy/templates/readTS.py:2:import cdutil
zppy/templates/readTS.py:65:            v = cdutil.YEAR(v)

We can probably use xarray to replace cdms2.open, and an XML reader to replace cdscan (mfopen to open multiple files). May have to replace with multiple tools.

@tomvothecoder What's the timeline/deadline for this issue? Are we trying not to have anything CDAT-related by the next Unified release?

@forsyth2 Just CC'd you in an email chain with Xylar. He gave us 6-9 months to refactor any E3SM packages from CDAT to alternative solutions so they can work in E3SM Unified.
It looks like zppy's CDAT dependency is minimal and much more straightforward to refactor compared to e3sm_diags.

@tomvothecoder Sounds good; I've moved this issue up in priority, so it can be completed by the next release (February/March of 2024)

@tomvothecoder I apologize if this is a naive question, but are there xCDAT equivalents for all the CDAT commands? That seems like it would most simplify this change.
It looks like we need to change 3 things here:

Replace cdms2.open; I'm assuming this would be done with xarray.open_dataset (https://docs.xarray.dev/en/stable/generated/xarray.open_dataset.html) or perhaps xcdat.open_dataset (https://xcdat.readthedocs.io/en/stable/generated/xcdat.open_dataset.html#xcdat.open_dataset).
Replace cdscan -x; is there a recommended XML reader that could handle this?
Replace cdutil.YEAR; this seems trickiest. Looking at the file where it's defined, https://github.com/CDAT/cdutil/blob/master/cdutil/times.py, there is quite a bit of functionality. Would the best option be to determine which functionality is needed by zppy and write that myself??

Replace cdms2.open; I'm assuming this would be done with xarray.open_dataset (docs.xarray.dev/en/stable/generated/xarray.open_dataset.html) or perhaps xcdat.open_dataset (xcdat.readthedocs.io/en/stable/generated/xcdat.open_dataset.html#xcdat.open_dataset).

Yes, you can use either API if a single dataset is being opened. xcdat.open_dataset() has some additional capabilities listed in the docs. If you don't need them, xr.open_dataset() will work fine.

Replace cdscan -x; is there a recommended XML reader that could handle this?

In #80, Jill says "cdscan is used to concatenate files before running e3sm-diags and global mean time-series. One possibility is to use xarray's IO to read-in multiple files."
Since you'll be moving to xarray/xCDAT, I suggest exploring xarray.open_mfdataset() or xcdat.open_mfdataset(). These APIs can read a glob or list of .nc file paths and combine them into a single xr.Dataset.

Replace cdutil.YEAR; this seems trickiest. Looking at the file where it's defined, CDAT/cdutil@master/cdutil/times.py, there is quite a bit of functionality. Would the best option be to determine which functionality is needed by zppy and write that myself??

xCDAT has APIs for temporal averaging. The equivalent to cdutil.YEAR should be the xCDAT accessor method, xr.Dataset.temporal.group_average(...freq="year"). The docs include examples on how to use it.

Here's a CDAT to xCDAT mapping table (not all features are 1:1): https://xcdat.readthedocs.io/en/stable/api.html#cdat-mapping-table

Reopening since #519 was a partial resolution.


text:
[support]: Trilinos Develop Nightly CI with Tpetra at gitlab.e4s.io

Name of Software
Trilinos
Issue Description
This is to document an issue resolved through direct documentation. Nightly Trilinos Develop CI runs using the Tpetra test on gitlab.e4s.io began failing with the following errors:
[ 33%] Building CXX object CMakeFiles/iallreduce.dir/Teuchos_StandardParallelUnitTestMain.cpp.o

[ 66%] Building CXX object CMakeFiles/iallreduce.dir/iallreduce.cpp.o

/spack/opt/spack/linux-ubuntu20.04-x86_64/gcc-9.4.0/trilinos-develop-pzycskk3ryfenj6lpgg2oogyherqg4le/include/Kokkos_View.hpp(19): error: static assertion failed with "Including non-public Kokkos header files is not allowed."

/spack/opt/spack/linux-ubuntu20.04-x86_64/gcc-9.4.0/trilinos-develop-pzycskk3ryfenj6lpgg2oogyherqg4le/include/Kokkos_HostSpace.hpp(19): error: static assertion failed with "Including non-public Kokkos header files is not allowed."

/spack/opt/spack/linux-ubuntu20.04-x86_64/gcc-9.4.0/trilinos-develop-pzycskk3ryfenj6lpgg2oogyherqg4le/include/Kokkos_Concepts.hpp(19): error: static assertion failed with "Including non-public Kokkos header files is not allowed."

/spack/opt/spack/linux-ubuntu20.04-x86_64/gcc-9.4.0/trilinos-develop-pzycskk3ryfenj6lpgg2oogyherqg4le/include/Kokkos_MemoryTraits.hpp(19): error: static assertion failed with "Including non-public Kokkos header files is not allowed."

/spack/opt/spack/linux-ubuntu20.04-x86_64/gcc-9.4.0/trilinos-develop-pzycskk3ryfenj6lpgg2oogyherqg4le/include/Kokkos_MemoryTraits.hpp(19): error: static assertion failed with "Including non-public Kokkos header files is not allowed."

The Tpetra test giving rise to this error is here:

https://github.com/E4S-Project/testsuite/tree/master/validation_tests/trilinos-tpetra

By direct communication with the Trilinos Team we determined that header files that used be OK to include needed to be replaced now by other header files. These changes were made here:

https://github.com/E4S-Project/testsuite/commit/c9f57e6f2f37e7067054102cd43fcc16a90f96bb

This issue was initially detected on March 7th and was resolved on March 9th.
CC @jwillenbring

This was a retrospective documentation for an issue resolved by direct communication. It is resolved.


text:
EVA-739 Generate coordinate list for Open Target

Added allowed clinical significances to coordinate outputting

Coverage remained the same at 78.217% when pulling b565e9cb1fcc50b7a84a39989ad1b0bad1eb48c4 on tomdcsmith:add_clin_sig_coord_output into 8c20e1a5fc94b30e6e447d7fd141feb2e6af38b7 on EBIvariation:master.

source: gharchive/pull-request

authors: coveralls tomdcsmith

repo: EBIvariation/eva-cttv-pipeline


text:
Cmake Error when trying to build

I receive these two errors when running catkin_make on the simulator:
CMake Error at plugins_pkgs/car_plugin/CMakeLists.txt:29 (add_dependencies):  add_dependencies called with incorrect number of arguments
https://github.com/ECC-BFMC/Simulator/blob/6a3023d89e67509ec0c5e08d77e5eaec759755f5/src/plugins_pkgs/car_plugin/CMakeLists.txt#L29
CMake Error at /opt/ros/noetic/share/genmsg/cmake/genmsg-extras.cmake:94 (message):
add_message_files() directory not found:
/home/bz/Documents/Simulator/src/traffic_light_pkg/msg
Call Stack (most recent call first):
traffic_light_pkg/CMakeLists.txt:9 (add_message_files)

I think I've solved the second error ('directory not found') by creating the msg directory inside traffic_light_pkg.

Hello Beniamin,
The issue should be fixed by the latest commit (I don't know how that command slipped in)

Indeed, after the last commit, the second error doesn't appear anymore. But still, this line causes an error that states
[...] add_dependencies called with incorrect number of arguments
https://github.com/ECC-BFMC/Simulator/blob/6a3023d89e67509ec0c5e08d77e5eaec759755f5/src/plugins_pkgs/car_plugin/CMakeLists.txt#L29
It seems to me that there is no argument that specifies the dependencies to be added - that may be the reason for which the error arises.
After commenting that line the build completes with no error.

Fixed with latest commit. Somehow a previous commit was not submitted to git and therefore the errors came along. Should be all good now! :)

authors: BFMC-Rares-Lemnariu ZeicBeniamin

repo: ECC-BFMC/Simulator


text:
Fix typo cmdDatabaseSchema -> cdmDatabaseSchema.

Closes EHDEN/CdmInspection#30.

Thanks for the fix

Thanks for the fix

authors: PRijnbeek ncittm

repo: EHDEN/CdmInspection


text:
Unable to optimize microsoft/deberta-v3-small model

Here's command and error message. Please advise and help fix it. Thanks!
sudo docker run -it --rm --gpus all   -v $PWD:/project ghcr.io/els-rd/transformer-deploy:latest   bash -c "cd /project &&
convert_model -m "microsoft/deberta-v3-small"
--backend tensorrt onnx
--seq-len 16 128 128
--task classification"

Hi @pommedeterresautee, I have the same problem trying to optimize DeBERTa.
Do you think it's possible to fix this with a reasonable amount of effort? In my experience DeBERTa is the best encoder-style model right now so this would be super useful to have.

Currently it s not on our todo

repo: ELS-RD/transformer-deploy


text:
New TableDoc class providing a table interface for data documentation

Description
Added the TableDoc class providing a table interface for data documentation.
This PR builds on top of PR #272. Merge that one first.
Type of change

[ ] Bug fix and code cleanup
[x] New feature
[ ] Documentation update
[ ] Testing

Checklist for the reviewer
This checklist should be used as a help for the reviewer.

[ ] Is the change limited to one issue?
[ ] Does this PR close the issue?
[ ] Is the code easy to read and understand?
[ ] Do all new feature have an accompanying new test?
[ ] Has the documentation been updated as necessary?
[ ] Is the code properly tested?

addnested(d, "a.b", 2)

The result of the above is
{'a': {'b': [1, 2]}}

with the current implementation of addnested(). The purpose is to allow adding multiple of the same (nested) data.

repo: EMMC-ASBL/tripper


text:
cleos/keosd enhancements to catch common user errors with updating permissions

There are several ways one can lock themselves out of their own account. One user (#4033) unfortunately came across one of these ways. In that particular case, it is obvious that no reasonable user would have ever intended for that permission update to occur. So ideally cleos (or any other wallet app) should have detected it and rejected. In fact these class of mistakes can even be detected and rejected by producer / API nodes that are running the appropriate plugin.
However, there is a legitimate need for users to be able to intentionally lock themselves out of their account. One example is deploying an immutable smart contract. Cleos should still support a few standard ways to lock out access of an account; although it should print a warning message and ask for confirmation again from the user.
Then there are nearly limitless ways that a user can lock themselves out of their account that may be perfectly legitimate actions but that the wallet app cannot tell if it is legitimate or a user mistake. The simplest example of this class of mistakes is changing an owner key to a public key that the user does not have the private key for.
One way to help the user catch mistakes is for cleos to warn and require confirmation from the user when modifying a permission to something that keosd cannot satisfy. But it should not disallow the change entirely because there are legitimate use cases for such actions, for example:

Transferring ownership of the account to another user.
Transitioning from a single owner key to a 2-of-3 multisig where each wallet only has one of the keys. (In this case you aren't actually locked out if you have access to at least two of the three keys, but from the perspective of a cleos/keosd which only has access to one of the keys it cannot possibly know this at the time it is signing the transaction to change the owner permission.)

Sometimes such cases is not mistake. E.g. we want to do locked account for smart contracts, which cannot change code or get funds and so on. So, if you are going to add the protection, please, add a flag like --force or --unprotect also to disable protection.

In order to focus our efforts on issues that are currently creating difficulty for the community we are closing tickets that were created prior to the EOSIO 2.0 release.  If you believe this issue is still relevant please feel free to reopen it or create a new one.  Thank you for your continued support of EOSIO!

authors: ValeryDubrava aclark-b1 arhag

repo: EOSIO/eos


text:
keosd Wallet unlock JSON RPC works only localhost, not external

Hi,
I tried to execute unlock API external but it runs only localhost.
Environment: Ubuntu 16.04, EOSIO v1.2.1
keosd is running as the below.
keosd --plugin eosio::http_plugin --http-server-address 0.0.0.0:8900 --access-control-allow-origin 0.0.0.0 --verbose-http-errors

With cURL in localhost, it works well.
curl --request POST   --url http://127.0.0.1:8900/v1/wallet/unlock --data '["default", "passcode"]'
{}

curl --request POST   --url http://127.0.0.1:8900/v1/wallet/unlock --data '["default", "wrong_password"]'
{"code":500,"message":"Internal Service Error","error":{"code":3120005,"name":"wallet_invalid_password_exception","what":"Invalid wallet password","details":[]}}

But in postman of my laptop, it only response 400.

Does it block every external connection from v1.2.1, or unencrypted(HTTP, not HTTPS) request?

to help mitigate DNS rebinding and blind CSRF attacks, we validate the HTTP level Host: header against a set of expected values.  By default, this only includes literal URL that keosd is configured to listen on and any direct IP values when that IP address is the IP bound to the listening device (which is why 127.0.0.1 works)
For all other host values you should append the argument(s) --http-alias=hostname[:port-if-not-default]
judging by your postman image, you should add --http-alias=etos.ciceron.xyz:8900
I will also caution that the HTTP RPC for wallets does no authentication outside of unlocking wallets so, any client able to successfully submit an HTTP RPC command to your external endpoint can use the wallets.  Please deploy such a configuration very carefully

I had add the header, but also return 400, my log below:
root@eosnode:~# curl -v --header 'Host: 127.0.0.1:8900' --request POST --url http://127.0.0.1:8900/v1/wallet/list_wallets
*   Trying 127.0.0.1...
* Connected to 127.0.0.1 (127.0.0.1) port 8900 (#0)
> POST /v1/wallet/list_wallets HTTP/1.1
> Host: 127.0.0.1:8900
> User-Agent: curl/7.47.0
> Accept: */*
>
< HTTP/1.1 400 Bad Request
< Connection: close
< Server: WebSocket++/0.7.0
<
* Closing connection 0

where is my problem? thanks.

sorry, I found the problem, I bound keosd server as 0.0.0.0:8900, so I also set header as Host: 0.0.0.0:8900.

authors: oslivan psy2848048 wanderingbort


text:
mongo_db_plugin ->  how to filter special account blockchain data?

question : how to filter special account blockchain data? I'm try use mongodb-filter-on option, mongodb-filter-on option value is "anxinganxin1:transfer:", but this option don't work.
anybody here, what are you do filter special account blockchain data?

What do you mean it doesn't work. It filters action_trace and transaction_trace data.

@heifner yes, you are right! I misunderstood... thank of you reply

authors: heifner zhongjixiuxing


text:
[do not merge] Typedoc->Gitbook Implementation for Typescript

Sample typedoc/gitbook implementation for an EOS typescript repository.
Typescript implementations are a bit more difficult due to lack of support for static files (tutorials, guides, explainer docs, etc). Solution would appear to be copying the files and then prepending the SUMMARY.md file dynamically based on files in docs/static, some ugly psuedocode
filesInStatic.each
  str += "[{{url.replace('-', ' ') }}]({{url}})"
Summary.prepend str

The above is not presently implemented due to a desire to maintain a separation of concerns between the repository and the documentation generation itself. There's some obvious solutions to this, from unideal and easy to ideal and difficult.

[unideal] Bash script in docs directory to handle copying and prepending generated SUMMARY.md. This is unideal because there's non-eosjs2 logic that needs to be maintained in the directory. Having the bash script executed in-line as an npm script has similar drawbacks
[acceptable] Write a typedoc plugin to make typedoc do what we want to do or modify typedoc-plugin-markdown (likely easier) There's a possibility this isn't possible with the Typedoc API and it creates maintenance overhead
[ideal] Create a standalone cli utility that generates documentation for any EOS repository for supported languages, removing any implementation requirements from the repository. This is probably the ideal route because then absolutely no documentation logic needs to exist in the repository outside of an optional configuration file. The tool simply takes arguments or reads a config file, parses files based on config and then places documentation into a directory

TODO:

Skin [This is a todo for all these implementations]

#45

Most pieces are in place, next I need to modularize some components used in here so they are reusable.

@dskvr This is looking great. I ran the build-serve-docs script, and the resulting documentation looks very nice.
After this is settled and merged, we can follow up with improvements to the documentation, itself. For example, in the API documentation, it's listing all of the API constructor params in a single block of text. We can improve this by moving those out into an ApiArgs interface. Will generate much nicer documentation.
Anyway, I'm in favor of proceeding with this approach after a fixup/squash of the commits herein. Nice work!

Closing in favor of #69

authors: brandonfancher dskvr jeffreyssmith2nd


text:
Fixing global attributes for recipe_martin18grl

Describe the bug
Due to a change in iris, global attributes can be transformed into variables attributes during preprocessing for some models. droughtindex/diag_save_spi.R does so far only write the global attributes in the resulting files. Therefor, recipe_martin18grl.yml fails, because the following python diagnostics (through ancestors) relay on the existence of the attributes. The fastest way to solve that would be to write the variable attributes in the files resulting from droughtindex/diag_save_spi.R. A better solution would be to improve also the way, information is transferred from R to python (but I don't know if I have time for this and it should be finished for the release).
See also #3616

I suspect that transforming global attributes to variable attributes happens in the concatenate preprocessor function since we started using this difference introduced in iris 3.8 in https://github.com/ESMValGroup/ESMValCore/pull/2398. Could you try if https://github.com/ESMValGroup/ESMValCore/pull/2449 solves the issue?

This recipe passes on DKRZ using the latest versions of the ESMValCore v2.11.x release branch and the ESMValTool v2.11.x release branch (the versions dated "Jun 26, 2024"). I'll update the webpage once I have completed testing using ESMValCore v2.11.0rc2 😊

authors: bouweandela ehogan katjaweigel

repo: ESMValGroup/ESMValTool


text:
Make results of recipes schlund20jgr_*.yml deterministic

Description
Major changes

Introduction of the option random_state to the MLR diagnostics which can be used to make the results of the recipe deterministic, i.e., the numerical results are identical across runs now.
Coordinate ordering in mlr/postprocess.py is now fixed to make the output of this diagnostic reproducible (see https://github.com/ESMValGroup/ESMValTool/discussions/2901).

--> As a result, all plots and most netCDF files can now be compared correctly with the recipe comparison tool. Note that some netCDF files are still not comparable (mainly due to differing attributes, see https://github.com/ESMValGroup/ESMValTool/discussions/2901).
Minor changes
In addition, this PR removes the usage of deprecated features and solves a bunch of Codacy issues:

Removal of deprecated sklearn.utils.metaestimators.if_delegate_has_method
Removal of deprecated sklearn.inspection.plot_partial_dependence
Removal of deprecated pandas.DataFrame.append
Removal of deprecated verbose argument for SimpleImputer
Fixed code that lead to warning about X does not have valid feature names, but SimpleImputer was fitted with feature names
Removal of GradientBoostingRegressor.loss_
Fixed Codacy issue about using raise Exception from ...
Fixed Codacy issue about using f-strings

Closes #2889
Link to documentation: https://esmvaltool--2900.org.readthedocs.build/en/2900/api/esmvaltool.diag_scripts.mlr/models.html#optional-parameters-for-class-initialization

Before you get started

[x] ☝ Create an issue to discuss what you are going to do

Checklist
It is the responsibility of the author to make sure the pull request is ready to review. The icons indicate whether the item will be subject to the 🛠 Technical or 🧪 Scientific review.

[x] 🛠 This pull request has a descriptive title
[x] 🛠 Code is written according to the code quality guidelines
[x] 🛠 Documentation is available
[x] 🛠 Tests run successfully
[x] 🛠 The list of authors is up to date
[x] 🛠 Any changed dependencies have been added or removed correctly
[x] 🛠 All checks below this pull request were successful

New or updated recipe/diagnostic

[x] 🧪 Recipe runs successfully
[x] 🧪 Recipe is well documented
[x] 🧪 Figure(s) and data look as expected from literature
[x] 🛠 Provenance information has been added

To help with the number of pull requests:

🙏 We kindly ask you to review two other open pull requests in this repository

Thanks V for reviewing!

Regarding the Codacy issue: this one is different to the ones that I fixed. I think in this case it's fine (and necessary) to catch a general exception. It is properly re-raised or reported depending on the settings:

https://github.com/ESMValGroup/ESMValTool/blob/c75565559b666343fb229dc839f203bb750e0131/esmvaltool/diag_scripts/mlr/custom_sklearn.py#L409-L423

I ran the comparison tool on both critical recipes. In both cases no plots are affected, only netcdf mainly because of differing attributes (never because of differing data). A complete list of these issues is given here: https://github.com/ESMValGroup/ESMValTool/discussions/2901. Below you find a detailed list of files that still differ:

recipe_schlund20jgr_gpp_abs_rcp85.yml
Comparing recipe run(s) in:
/home/b/b309141/scratch/esmvaltool_output/recipe_schlund20jgr_gpp_abs_rcp85_20221031_190907
to reference in /home/b/b309141/scratch/esmvaltool_output/recipe_schlund20jgr_gpp_abs_rcp85_20221031_163845

recipe_schlund20jgr_gpp_abs_rcp85.yml: results differ from reference run
Reference run: /home/b/b309141/scratch/esmvaltool_output/recipe_schlund20jgr_gpp_abs_rcp85_20221031_163845
Current run: /home/b/b309141/scratch/esmvaltool_output/recipe_schlund20jgr_gpp_abs_rcp85_20221031_190907
Missing files:
  - work/diag_plot_cmip5_gbrt/preprocess_plot/mmm_GPP_prediction_prediction_output_20221031_165943090559.nc
  - work/diag_plot_cmip5_gbrt/preprocess_plot/mmm_GPP_prediction_prediction_output_20221031_165943107197.nc
  - work/diag_plot_cmip5_gbrt/preprocess_plot/mmm_GPP_squared_prediction_error_prediction_output_error_20221031_165943262598.nc
  - work/diag_plot_cmip5_gbrt/preprocess_plot/mmm_GPP_squared_prediction_error_prediction_output_error_20221031_165943289763.nc
  - work/diag_plot_mlr_models/preprocess_plot/gbr_sklearn_GPP_prediction_for_prediction_OBS_prediction_output_20221031_165950942347.nc
  - work/diag_plot_mlr_models/preprocess_plot/gbr_sklearn_GPP_prediction_squared_mlr_model_error_estim_for_prediction_OBS_prediction_output_error_20221031_165951100339.nc
  - work/diag_plot_mlr_models/preprocess_plot/gbr_sklearn_GPP_prediction_squared_propagated_input_error_for_prediction_OBS_prediction_output_error_20221031_165951127932.nc
  - work/diag_plot_mlr_models/preprocess_plot/lasso_cv_GPP_prediction_for_prediction_OBS_prediction_output_20221031_165950973044.nc
  - work/diag_plot_mlr_models/preprocess_plot/lasso_cv_GPP_prediction_squared_mlr_model_error_estim_for_prediction_OBS_prediction_output_error_20221031_165951237551.nc
  - work/diag_plot_mlr_models/preprocess_plot/lasso_cv_GPP_prediction_squared_propagated_input_error_for_prediction_OBS_prediction_output_error_20221031_165951273227.nc
  - work/diag_plot_mlr_models/preprocess_plot/mmm_GPP_prediction_prediction_output_20221031_165951010923.nc
  - work/diag_plot_mlr_models/preprocess_plot/mmm_GPP_squared_prediction_error_prediction_output_error_20221031_165951576160.nc
  - work/diag_plot_mlr_models/preprocess_plot/standard_error_of_emergent_constraint_prediction_output_error_20221031_165951364207.nc
  - work/diag_plot_mlr_models/preprocess_plot/standard_error_of_emergent_constraint_prediction_output_error_20221031_165951402733.nc
  - work/diag_plot_mlr_models/preprocess_plot/standard_error_of_emergent_constraint_prediction_output_error_20221031_165951445472.nc
  - work/diag_plot_mlr_models/preprocess_plot/standard_error_of_emergent_constraint_prediction_output_error_20221031_165951487461.nc
Extra files:
  - work/diag_plot_cmip5_gbrt/preprocess_plot/mmm_GPP_prediction_prediction_output_20221031_194139740115.nc
  - work/diag_plot_cmip5_gbrt/preprocess_plot/mmm_GPP_prediction_prediction_output_20221031_194139756298.nc
  - work/diag_plot_cmip5_gbrt/preprocess_plot/mmm_GPP_squared_prediction_error_prediction_output_error_20221031_194139866639.nc
  - work/diag_plot_cmip5_gbrt/preprocess_plot/mmm_GPP_squared_prediction_error_prediction_output_error_20221031_194139893839.nc
  - work/diag_plot_mlr_models/preprocess_plot/gbr_sklearn_GPP_prediction_for_prediction_OBS_prediction_output_20221031_194159894326.nc
  - work/diag_plot_mlr_models/preprocess_plot/gbr_sklearn_GPP_prediction_squared_mlr_model_error_estim_for_prediction_OBS_prediction_output_error_20221031_194200075453.nc
  - work/diag_plot_mlr_models/preprocess_plot/gbr_sklearn_GPP_prediction_squared_propagated_input_error_for_prediction_OBS_prediction_output_error_20221031_194200116252.nc
  - work/diag_plot_mlr_models/preprocess_plot/lasso_cv_GPP_prediction_for_prediction_OBS_prediction_output_20221031_194159939901.nc
  - work/diag_plot_mlr_models/preprocess_plot/lasso_cv_GPP_prediction_squared_mlr_model_error_estim_for_prediction_OBS_prediction_output_error_20221031_194200236226.nc
  - work/diag_plot_mlr_models/preprocess_plot/lasso_cv_GPP_prediction_squared_propagated_input_error_for_prediction_OBS_prediction_output_error_20221031_194200290363.nc
  - work/diag_plot_mlr_models/preprocess_plot/mmm_GPP_prediction_prediction_output_20221031_194159974934.nc
  - work/diag_plot_mlr_models/preprocess_plot/mmm_GPP_squared_prediction_error_prediction_output_error_20221031_194200583571.nc
  - work/diag_plot_mlr_models/preprocess_plot/standard_error_of_emergent_constraint_prediction_output_error_20221031_194200363593.nc
  - work/diag_plot_mlr_models/preprocess_plot/standard_error_of_emergent_constraint_prediction_output_error_20221031_194200414215.nc
  - work/diag_plot_mlr_models/preprocess_plot/standard_error_of_emergent_constraint_prediction_output_error_20221031_194200454019.nc
  - work/diag_plot_mlr_models/preprocess_plot/standard_error_of_emergent_constraint_prediction_output_error_20221031_194200495287.nc
Differing files:
  - work/diag_co2_amplitude_sensitivity/plot_co2_amplitudes/xy_feature___CESM1-BGC.nc
  - work/diag_co2_amplitude_sensitivity/plot_co2_amplitudes/xy_feature___GFDL-ESM2M.nc
  - work/diag_co2_amplitude_sensitivity/preprocess/CMIP5_CESM1-BGC_Amon_esmHistorical-esmrcp85_r1i1p1_co2s_trend_relative_to_ref_1979-2019_feature.nc
  - work/diag_co2_amplitude_sensitivity/preprocess/CMIP5_GFDL-ESM2M_Amon_esmHistorical-esmrcp85_r1i1p1_co2s_trend_relative_to_ref_1979-2019_feature.nc
  - work/diag_co2_amplitude_sensitivity/preprocess_for_plot/CMIP5_CESM1-BGC_Amon_esmHistorical-esmrcp85_r1i1p1_co2s_1979-2019_feature.nc
  - work/diag_co2_amplitude_sensitivity/preprocess_for_plot/CMIP5_GFDL-ESM2M_Amon_esmHistorical-esmrcp85_r1i1p1_co2s_1979-2019_feature.nc
  - work/diag_co2_cycle/plot_cycle/xy_feature___CESM1-BGC.nc
  - work/diag_co2_cycle/plot_cycle/xy_feature___GFDL-ESM2M.nc
  - work/diag_gbrt_1d/mlr/gbr_sklearn_GPP_prediction_for_prediction_OBS.nc
  - work/diag_gbrt_1d/mlr/gbr_sklearn_GPP_prediction_squared_mlr_model_error_estim_for_prediction_OBS.nc
  - work/diag_gbrt_1d/mlr/gbr_sklearn_GPP_prediction_squared_propagated_input_error_for_prediction_OBS.nc
  - work/diag_gbrt_1d/postprocess/gbr_sklearn_GPP_prediction_for_prediction_OBS.nc
  - work/diag_gbrt_1d/postprocess/gbr_sklearn_GPP_prediction_for_prediction_OBS_error_estimated.nc
  - work/diag_gbrt_1d/postprocess/gbr_sklearn_GPP_prediction_for_prediction_OBS_error_lower_bound.nc
  - work/diag_gbrt_1d/postprocess/gbr_sklearn_GPP_prediction_for_prediction_OBS_error_upper_bound.nc
  - work/diag_gbrt_1d_pseudo_reality/mlr_pseudo_reality/CESM1-BGC/gbr_sklearn_GPP_prediction_for_prediction_CESM1-BGC_of_group_CESM1-BGC.nc
  - work/diag_gbrt_1d_pseudo_reality/mlr_pseudo_reality/CESM1-BGC/gbr_sklearn_GPP_prediction_for_prediction_OBS_of_group_CESM1-BGC.nc
  - work/diag_gbrt_1d_pseudo_reality/mlr_pseudo_reality/CESM1-BGC/gbr_sklearn_GPP_prediction_residual_for_prediction_CESM1-BGC_of_group_CESM1-BGC.nc
  - work/diag_gbrt_1d_pseudo_reality/mlr_pseudo_reality/CanESM2/gbr_sklearn_GPP_prediction_for_prediction_CanESM2_of_group_CanESM2.nc
  - work/diag_gbrt_1d_pseudo_reality/mlr_pseudo_reality/CanESM2/gbr_sklearn_GPP_prediction_for_prediction_OBS_of_group_CanESM2.nc
  - work/diag_gbrt_1d_pseudo_reality/mlr_pseudo_reality/CanESM2/gbr_sklearn_GPP_prediction_residual_for_prediction_CanESM2_of_group_CanESM2.nc
  - work/diag_gbrt_1d_pseudo_reality/mlr_pseudo_reality/GFDL-ESM2M/gbr_sklearn_GPP_prediction_for_prediction_GFDL-ESM2M_of_group_GFDL-ESM2M.nc
  - work/diag_gbrt_1d_pseudo_reality/mlr_pseudo_reality/GFDL-ESM2M/gbr_sklearn_GPP_prediction_for_prediction_OBS_of_group_GFDL-ESM2M.nc
  - work/diag_gbrt_1d_pseudo_reality/mlr_pseudo_reality/GFDL-ESM2M/gbr_sklearn_GPP_prediction_residual_for_prediction_GFDL-ESM2M_of_group_GFDL-ESM2M.nc
  - work/diag_gbrt_1d_pseudo_reality/mlr_pseudo_reality/HadGEM2-ES/gbr_sklearn_GPP_prediction_for_prediction_HadGEM2-ES_of_group_HadGEM2-ES.nc
  - work/diag_gbrt_1d_pseudo_reality/mlr_pseudo_reality/HadGEM2-ES/gbr_sklearn_GPP_prediction_for_prediction_OBS_of_group_HadGEM2-ES.nc
  - work/diag_gbrt_1d_pseudo_reality/mlr_pseudo_reality/HadGEM2-ES/gbr_sklearn_GPP_prediction_residual_for_prediction_HadGEM2-ES_of_group_HadGEM2-ES.nc
  - work/diag_gbrt_1d_pseudo_reality/mlr_pseudo_reality/MIROC-ESM/gbr_sklearn_GPP_prediction_for_prediction_MIROC-ESM_of_group_MIROC-ESM.nc
  - work/diag_gbrt_1d_pseudo_reality/mlr_pseudo_reality/MIROC-ESM/gbr_sklearn_GPP_prediction_for_prediction_OBS_of_group_MIROC-ESM.nc
  - work/diag_gbrt_1d_pseudo_reality/mlr_pseudo_reality/MIROC-ESM/gbr_sklearn_GPP_prediction_residual_for_prediction_MIROC-ESM_of_group_MIROC-ESM.nc
  - work/diag_gbrt_1d_pseudo_reality/mlr_pseudo_reality/MPI-ESM-LR/gbr_sklearn_GPP_prediction_for_prediction_MPI-ESM-LR_of_group_MPI-ESM-LR.nc
  - work/diag_gbrt_1d_pseudo_reality/mlr_pseudo_reality/MPI-ESM-LR/gbr_sklearn_GPP_prediction_for_prediction_OBS_of_group_MPI-ESM-LR.nc
  - work/diag_gbrt_1d_pseudo_reality/mlr_pseudo_reality/MPI-ESM-LR/gbr_sklearn_GPP_prediction_residual_for_prediction_MPI-ESM-LR_of_group_MPI-ESM-LR.nc
  - work/diag_gbrt_1d_pseudo_reality/mlr_pseudo_reality/NorESM1-ME/gbr_sklearn_GPP_prediction_for_prediction_NorESM1-ME_of_group_NorESM1-ME.nc
  - work/diag_gbrt_1d_pseudo_reality/mlr_pseudo_reality/NorESM1-ME/gbr_sklearn_GPP_prediction_for_prediction_OBS_of_group_NorESM1-ME.nc
  - work/diag_gbrt_1d_pseudo_reality/mlr_pseudo_reality/NorESM1-ME/gbr_sklearn_GPP_prediction_residual_for_prediction_NorESM1-ME_of_group_NorESM1-ME.nc
  - work/diag_lasso/mlr/lasso_cv_GPP_prediction_for_prediction_OBS.nc
  - work/diag_lasso/mlr/lasso_cv_GPP_prediction_squared_mlr_model_error_estim_for_prediction_OBS.nc
  - work/diag_lasso/mlr/lasso_cv_GPP_prediction_squared_propagated_input_error_for_prediction_OBS.nc
  - work/diag_lasso/postprocess/lasso_cv_GPP_prediction_for_prediction_OBS.nc
  - work/diag_lasso/postprocess/lasso_cv_GPP_prediction_for_prediction_OBS_error_estimated.nc
  - work/diag_lasso/postprocess/lasso_cv_GPP_prediction_for_prediction_OBS_error_lower_bound.nc
  - work/diag_lasso/postprocess/lasso_cv_GPP_prediction_for_prediction_OBS_error_upper_bound.nc
  - work/diag_plot_mlr_models/plot/map_abs_bias_prediction_output___GBRT-1D-prediction_output___GBRT.nc
  - work/diag_plot_mlr_models/plot/map_abs_bias_prediction_output___GBRT-1D-prediction_output___LASSO-1D.nc
  - work/diag_plot_mlr_models/plot/map_abs_bias_prediction_output___GBRT-1D-prediction_output___LASSO.nc
  - work/diag_plot_mlr_models/plot/map_abs_bias_prediction_output___GBRT-1D-prediction_output___MMM.nc
  - work/diag_plot_mlr_models/plot/map_abs_bias_prediction_output___GBRT-1D-prediction_output___rMMM.nc
  - work/diag_plot_mlr_models/plot/map_abs_bias_prediction_output___LASSO-prediction_output___GBRT-1D.nc
  - work/diag_plot_mlr_models/plot/map_abs_bias_prediction_output___LASSO-prediction_output___GBRT.nc
  - work/diag_plot_mlr_models/plot/map_abs_bias_prediction_output___LASSO-prediction_output___LASSO-1D.nc
  - work/diag_plot_mlr_models/plot/map_abs_bias_prediction_output___LASSO-prediction_output___MMM.nc
  - work/diag_plot_mlr_models/plot/map_abs_bias_prediction_output___LASSO-prediction_output___rMMM.nc
  - work/diag_plot_mlr_models/plot/map_prediction_output___GBRT-1D.nc
  - work/diag_plot_mlr_models/plot/map_prediction_output___LASSO.nc
  - work/diag_plot_mlr_models/plot/map_ratio_prediction_output___GBRT-1D-prediction_output___GBRT.nc
  - work/diag_plot_mlr_models/plot/map_ratio_prediction_output___GBRT-1D-prediction_output___LASSO-1D.nc
  - work/diag_plot_mlr_models/plot/map_ratio_prediction_output___GBRT-1D-prediction_output___LASSO.nc
  - work/diag_plot_mlr_models/plot/map_ratio_prediction_output___GBRT-1D-prediction_output___MMM.nc
  - work/diag_plot_mlr_models/plot/map_ratio_prediction_output___GBRT-1D-prediction_output___rMMM.nc
  - work/diag_plot_mlr_models/plot/map_ratio_prediction_output___LASSO-prediction_output___GBRT-1D.nc
  - work/diag_plot_mlr_models/plot/map_ratio_prediction_output___LASSO-prediction_output___GBRT.nc
  - work/diag_plot_mlr_models/plot/map_ratio_prediction_output___LASSO-prediction_output___LASSO-1D.nc
  - work/diag_plot_mlr_models/plot/map_ratio_prediction_output___LASSO-prediction_output___MMM.nc
  - work/diag_plot_mlr_models/plot/map_ratio_prediction_output___LASSO-prediction_output___rMMM.nc
  - work/diag_plot_mlr_models/plot/map_rel_bias_prediction_output___GBRT-1D-prediction_output___GBRT.nc
  - work/diag_plot_mlr_models/plot/map_rel_bias_prediction_output___GBRT-1D-prediction_output___LASSO-1D.nc
  - work/diag_plot_mlr_models/plot/map_rel_bias_prediction_output___GBRT-1D-prediction_output___LASSO.nc
  - work/diag_plot_mlr_models/plot/map_rel_bias_prediction_output___GBRT-1D-prediction_output___MMM.nc
  - work/diag_plot_mlr_models/plot/map_rel_bias_prediction_output___GBRT-1D-prediction_output___rMMM.nc
  - work/diag_plot_mlr_models/plot/map_rel_bias_prediction_output___LASSO-prediction_output___GBRT-1D.nc
  - work/diag_plot_mlr_models/plot/map_rel_bias_prediction_output___LASSO-prediction_output___GBRT.nc
  - work/diag_plot_mlr_models/plot/map_rel_bias_prediction_output___LASSO-prediction_output___LASSO-1D.nc
  - work/diag_plot_mlr_models/plot/map_rel_bias_prediction_output___LASSO-prediction_output___MMM.nc
  - work/diag_plot_mlr_models/plot/map_rel_bias_prediction_output___LASSO-prediction_output___rMMM.nc
  - work/diag_plot_mlr_models/plot_errors/map_abs_bias_prediction_output_error___GBRT-1D-prediction_output_error___GBRT.nc
  - work/diag_plot_mlr_models/plot_errors/map_abs_bias_prediction_output_error___GBRT-1D-prediction_output_error___LASSO-1D.nc
  - work/diag_plot_mlr_models/plot_errors/map_abs_bias_prediction_output_error___GBRT-1D-prediction_output_error___LASSO.nc
  - work/diag_plot_mlr_models/plot_errors/map_abs_bias_prediction_output_error___GBRT-1D-prediction_output_error___MMM.nc
  - work/diag_plot_mlr_models/plot_errors/map_abs_bias_prediction_output_error___GBRT-1D-prediction_output_error___rMMM.nc
  - work/diag_plot_mlr_models/plot_errors/map_abs_bias_prediction_output_error___LASSO-prediction_output_error___GBRT-1D.nc
  - work/diag_plot_mlr_models/plot_errors/map_abs_bias_prediction_output_error___LASSO-prediction_output_error___GBRT.nc
  - work/diag_plot_mlr_models/plot_errors/map_abs_bias_prediction_output_error___LASSO-prediction_output_error___LASSO-1D.nc
  - work/diag_plot_mlr_models/plot_errors/map_abs_bias_prediction_output_error___LASSO-prediction_output_error___MMM.nc
  - work/diag_plot_mlr_models/plot_errors/map_abs_bias_prediction_output_error___LASSO-prediction_output_error___rMMM.nc
  - work/diag_plot_mlr_models/plot_errors/map_prediction_output_error___GBRT-1D.nc
  - work/diag_plot_mlr_models/plot_errors/map_prediction_output_error___LASSO.nc
  - work/diag_plot_mlr_models/plot_errors/map_rel_bias_prediction_output_error___GBRT-1D-prediction_output_error___GBRT.nc
  - work/diag_plot_mlr_models/plot_errors/map_rel_bias_prediction_output_error___GBRT-1D-prediction_output_error___LASSO-1D.nc
  - work/diag_plot_mlr_models/plot_errors/map_rel_bias_prediction_output_error___GBRT-1D-prediction_output_error___LASSO.nc
  - work/diag_plot_mlr_models/plot_errors/map_rel_bias_prediction_output_error___GBRT-1D-prediction_output_error___MMM.nc
  - work/diag_plot_mlr_models/plot_errors/map_rel_bias_prediction_output_error___GBRT-1D-prediction_output_error___rMMM.nc
  - work/diag_plot_mlr_models/plot_errors/map_rel_bias_prediction_output_error___LASSO-prediction_output_error___GBRT-1D.nc
  - work/diag_plot_mlr_models/plot_errors/map_rel_bias_prediction_output_error___LASSO-prediction_output_error___GBRT.nc
  - work/diag_plot_mlr_models/plot_errors/map_rel_bias_prediction_output_error___LASSO-prediction_output_error___LASSO-1D.nc
  - work/diag_plot_mlr_models/plot_errors/map_rel_bias_prediction_output_error___LASSO-prediction_output_error___MMM.nc
  - work/diag_plot_mlr_models/plot_errors/map_rel_bias_prediction_output_error___LASSO-prediction_output_error___rMMM.nc
  - work/diag_plot_mlr_models/preprocess_plot/lasso_cv_GPP_prediction_for_prediction_OBS_prediction_output.nc
  - work/diag_plot_mlr_models/preprocess_plot/lasso_cv_GPP_prediction_squared_mlr_model_error_estim_for_prediction_OBS_prediction_output_error.nc
  - work/diag_plot_mlr_models/preprocess_plot/lasso_cv_GPP_prediction_squared_propagated_input_error_for_prediction_OBS_prediction_output_error.nc

recipe_schlund20jgr_gpp_change_rcp85.yml
Comparing recipe run(s) in:
/home/b/b309141/scratch/esmvaltool_output/recipe_schlund20jgr_gpp_change_rcp85_20221031_165555
to reference in /home/b/b309141/scratch/esmvaltool_output/recipe_schlund20jgr_gpp_change_rcp85_20221031_164134

recipe_schlund20jgr_gpp_change_rcp85.yml: results differ from reference run
Reference run: /home/b/b309141/scratch/esmvaltool_output/recipe_schlund20jgr_gpp_change_rcp85_20221031_164134
Current run: /home/b/b309141/scratch/esmvaltool_output/recipe_schlund20jgr_gpp_change_rcp85_20221031_165555
Differing files:
  - work/diag_co2_amplitude_sensitivity/plot_co2_amplitudes/xy_feature___CanESM2.nc
  - work/diag_co2_amplitude_sensitivity/plot_co2_amplitudes/xy_feature___MIROC-ESM.nc
  - work/diag_co2_amplitude_sensitivity/plot_co2_amplitudes/xy_feature___MPI-ESM-LR.nc
  - work/diag_co2_amplitude_sensitivity/preprocess/CMIP5_CanESM2_Amon_esmHistorical-esmrcp85_r1i1p1_co2s_trend_relative_to_ref_1979-2019_feature.nc
  - work/diag_co2_amplitude_sensitivity/preprocess/CMIP5_MIROC-ESM_Amon_esmHistorical-esmrcp85_r1i1p1_co2s_trend_relative_to_ref_1979-2019_feature.nc
  - work/diag_co2_amplitude_sensitivity/preprocess/CMIP5_MPI-ESM-LR_Amon_esmHistorical-esmrcp85_r1i1p1_co2s_trend_relative_to_ref_1979-2019_feature.nc
  - work/diag_co2_amplitude_sensitivity/preprocess_for_plot/CMIP5_CanESM2_Amon_esmHistorical-esmrcp85_r1i1p1_co2s_1979-2019_feature.nc
  - work/diag_co2_amplitude_sensitivity/preprocess_for_plot/CMIP5_MIROC-ESM_Amon_esmHistorical-esmrcp85_r1i1p1_co2s_1979-2019_feature.nc
  - work/diag_co2_amplitude_sensitivity/preprocess_for_plot/CMIP5_MPI-ESM-LR_Amon_esmHistorical-esmrcp85_r1i1p1_co2s_1979-2019_feature.nc
  - work/diag_co2_cycle/plot_cycle/xy_feature___CanESM2.nc
  - work/diag_co2_cycle/plot_cycle/xy_feature___MIROC-ESM.nc
  - work/diag_co2_cycle/plot_cycle/xy_feature___MPI-ESM-LR.nc
  - work/diag_gbrt/mlr/gbr_sklearn_GPP_change_prediction_squared_propagated_input_error_for_prediction_OBS.nc
  - work/diag_gbrt/postprocess/gbr_sklearn_GPP_change_prediction_for_prediction_OBS_error_estimated.nc
  - work/diag_gbrt/postprocess/gbr_sklearn_GPP_change_prediction_for_prediction_OBS_error_lower_bound.nc
  - work/diag_gbrt/postprocess/gbr_sklearn_GPP_change_prediction_for_prediction_OBS_error_upper_bound.nc
  - work/diag_gbrt_pseudo_reality/mlr_pseudo_reality/CESM1-BGC/gbr_sklearn_GPP_change_prediction_for_prediction_CESM1-BGC_of_group_CESM1-BGC.nc
  - work/diag_gbrt_pseudo_reality/mlr_pseudo_reality/CESM1-BGC/gbr_sklearn_GPP_change_prediction_for_prediction_OBS_of_group_CESM1-BGC.nc
  - work/diag_gbrt_pseudo_reality/mlr_pseudo_reality/CESM1-BGC/gbr_sklearn_GPP_change_prediction_residual_for_prediction_CESM1-BGC_of_group_CESM1-BGC.nc
  - work/diag_gbrt_pseudo_reality/mlr_pseudo_reality/CanESM2/gbr_sklearn_GPP_change_prediction_for_prediction_CanESM2_of_group_CanESM2.nc
  - work/diag_gbrt_pseudo_reality/mlr_pseudo_reality/CanESM2/gbr_sklearn_GPP_change_prediction_for_prediction_OBS_of_group_CanESM2.nc
  - work/diag_gbrt_pseudo_reality/mlr_pseudo_reality/CanESM2/gbr_sklearn_GPP_change_prediction_residual_for_prediction_CanESM2_of_group_CanESM2.nc
  - work/diag_gbrt_pseudo_reality/mlr_pseudo_reality/GFDL-ESM2M/gbr_sklearn_GPP_change_prediction_for_prediction_GFDL-ESM2M_of_group_GFDL-ESM2M.nc
  - work/diag_gbrt_pseudo_reality/mlr_pseudo_reality/GFDL-ESM2M/gbr_sklearn_GPP_change_prediction_for_prediction_OBS_of_group_GFDL-ESM2M.nc
  - work/diag_gbrt_pseudo_reality/mlr_pseudo_reality/GFDL-ESM2M/gbr_sklearn_GPP_change_prediction_residual_for_prediction_GFDL-ESM2M_of_group_GFDL-ESM2M.nc
  - work/diag_gbrt_pseudo_reality/mlr_pseudo_reality/HadGEM2-ES/gbr_sklearn_GPP_change_prediction_for_prediction_HadGEM2-ES_of_group_HadGEM2-ES.nc
  - work/diag_gbrt_pseudo_reality/mlr_pseudo_reality/HadGEM2-ES/gbr_sklearn_GPP_change_prediction_for_prediction_OBS_of_group_HadGEM2-ES.nc
  - work/diag_gbrt_pseudo_reality/mlr_pseudo_reality/HadGEM2-ES/gbr_sklearn_GPP_change_prediction_residual_for_prediction_HadGEM2-ES_of_group_HadGEM2-ES.nc
  - work/diag_gbrt_pseudo_reality/mlr_pseudo_reality/MIROC-ESM/gbr_sklearn_GPP_change_prediction_for_prediction_MIROC-ESM_of_group_MIROC-ESM.nc
  - work/diag_gbrt_pseudo_reality/mlr_pseudo_reality/MIROC-ESM/gbr_sklearn_GPP_change_prediction_for_prediction_OBS_of_group_MIROC-ESM.nc
  - work/diag_gbrt_pseudo_reality/mlr_pseudo_reality/MIROC-ESM/gbr_sklearn_GPP_change_prediction_residual_for_prediction_MIROC-ESM_of_group_MIROC-ESM.nc
  - work/diag_gbrt_pseudo_reality/mlr_pseudo_reality/MPI-ESM-LR/gbr_sklearn_GPP_change_prediction_for_prediction_MPI-ESM-LR_of_group_MPI-ESM-LR.nc
  - work/diag_gbrt_pseudo_reality/mlr_pseudo_reality/MPI-ESM-LR/gbr_sklearn_GPP_change_prediction_for_prediction_OBS_of_group_MPI-ESM-LR.nc
  - work/diag_gbrt_pseudo_reality/mlr_pseudo_reality/MPI-ESM-LR/gbr_sklearn_GPP_change_prediction_residual_for_prediction_MPI-ESM-LR_of_group_MPI-ESM-LR.nc
  - work/diag_gbrt_pseudo_reality/mlr_pseudo_reality/NorESM1-ME/gbr_sklearn_GPP_change_prediction_for_prediction_NorESM1-ME_of_group_NorESM1-ME.nc
  - work/diag_gbrt_pseudo_reality/mlr_pseudo_reality/NorESM1-ME/gbr_sklearn_GPP_change_prediction_for_prediction_OBS_of_group_NorESM1-ME.nc
  - work/diag_gbrt_pseudo_reality/mlr_pseudo_reality/NorESM1-ME/gbr_sklearn_GPP_change_prediction_residual_for_prediction_NorESM1-ME_of_group_NorESM1-ME.nc
  - work/diag_lasso/mlr/lasso_cv_GPP_change_prediction_for_prediction_OBS.nc
  - work/diag_lasso/mlr/lasso_cv_GPP_change_prediction_lime_importance___GPP_for_prediction_OBS.nc
  - work/diag_lasso/mlr/lasso_cv_GPP_change_prediction_lime_importance___LAI_for_prediction_OBS.nc
  - work/diag_lasso/mlr/lasso_cv_GPP_change_prediction_lime_importance___PR_for_prediction_OBS.nc
  - work/diag_lasso/mlr/lasso_cv_GPP_change_prediction_lime_importance___RSDS_for_prediction_OBS.nc
  - work/diag_lasso/mlr/lasso_cv_GPP_change_prediction_lime_importance___T_for_prediction_OBS.nc
  - work/diag_lasso/mlr/lasso_cv_GPP_change_prediction_squared_mlr_model_error_estim_for_prediction_OBS.nc
  - work/diag_lasso/mlr/lasso_cv_GPP_change_prediction_squared_propagated_input_error_for_prediction_OBS.nc
  - work/diag_lasso/postprocess/lasso_cv_GPP_change_prediction_for_prediction_OBS.nc
  - work/diag_lasso/postprocess/lasso_cv_GPP_change_prediction_for_prediction_OBS_error_estimated.nc
  - work/diag_lasso/postprocess/lasso_cv_GPP_change_prediction_for_prediction_OBS_error_lower_bound.nc
  - work/diag_lasso/postprocess/lasso_cv_GPP_change_prediction_for_prediction_OBS_error_upper_bound.nc
  - work/diag_lasso_pseudo_reality/mlr_pseudo_reality/HadGEM2-ES/lasso_cv_GPP_change_prediction_for_prediction_HadGEM2-ES_of_group_HadGEM2-ES.nc
  - work/diag_lasso_pseudo_reality/mlr_pseudo_reality/HadGEM2-ES/lasso_cv_GPP_change_prediction_for_prediction_OBS_of_group_HadGEM2-ES.nc
  - work/diag_lasso_pseudo_reality/mlr_pseudo_reality/HadGEM2-ES/lasso_cv_GPP_change_prediction_residual_for_prediction_HadGEM2-ES_of_group_HadGEM2-ES.nc
  - work/diag_lasso_pseudo_reality/mlr_pseudo_reality/MIROC-ESM/lasso_cv_GPP_change_prediction_for_prediction_MIROC-ESM_of_group_MIROC-ESM.nc
  - work/diag_lasso_pseudo_reality/mlr_pseudo_reality/MIROC-ESM/lasso_cv_GPP_change_prediction_for_prediction_OBS_of_group_MIROC-ESM.nc
  - work/diag_lasso_pseudo_reality/mlr_pseudo_reality/MIROC-ESM/lasso_cv_GPP_change_prediction_residual_for_prediction_MIROC-ESM_of_group_MIROC-ESM.nc
  - work/diag_lasso_pseudo_reality/mlr_pseudo_reality/MPI-ESM-LR/lasso_cv_GPP_change_prediction_for_prediction_MPI-ESM-LR_of_group_MPI-ESM-LR.nc
  - work/diag_lasso_pseudo_reality/mlr_pseudo_reality/MPI-ESM-LR/lasso_cv_GPP_change_prediction_for_prediction_OBS_of_group_MPI-ESM-LR.nc
  - work/diag_lasso_pseudo_reality/mlr_pseudo_reality/MPI-ESM-LR/lasso_cv_GPP_change_prediction_residual_for_prediction_MPI-ESM-LR_of_group_MPI-ESM-LR.nc
  - work/diag_lasso_pseudo_reality/mlr_pseudo_reality/NorESM1-ME/lasso_cv_GPP_change_prediction_for_prediction_NorESM1-ME_of_group_NorESM1-ME.nc
  - work/diag_lasso_pseudo_reality/mlr_pseudo_reality/NorESM1-ME/lasso_cv_GPP_change_prediction_for_prediction_OBS_of_group_NorESM1-ME.nc
  - work/diag_lasso_pseudo_reality/mlr_pseudo_reality/NorESM1-ME/lasso_cv_GPP_change_prediction_residual_for_prediction_NorESM1-ME_of_group_NorESM1-ME.nc
  - work/diag_plot_mlr_models/plot/map_abs_bias_prediction_output___LASSO-prediction_output___GBRT.nc
  - work/diag_plot_mlr_models/plot/map_abs_bias_prediction_output___LASSO-prediction_output___MMM.nc
  - work/diag_plot_mlr_models/plot/map_abs_bias_prediction_output___LASSO-prediction_output___rMMM.nc
  - work/diag_plot_mlr_models/plot/map_prediction_output___LASSO.nc
  - work/diag_plot_mlr_models/plot/map_ratio_prediction_output___LASSO-prediction_output___GBRT.nc
  - work/diag_plot_mlr_models/plot/map_ratio_prediction_output___LASSO-prediction_output___MMM.nc
  - work/diag_plot_mlr_models/plot/map_ratio_prediction_output___LASSO-prediction_output___rMMM.nc
  - work/diag_plot_mlr_models/plot/map_rel_bias_prediction_output___LASSO-prediction_output___GBRT.nc
  - work/diag_plot_mlr_models/plot/map_rel_bias_prediction_output___LASSO-prediction_output___MMM.nc
  - work/diag_plot_mlr_models/plot/map_rel_bias_prediction_output___LASSO-prediction_output___rMMM.nc
  - work/diag_plot_mlr_models/plot_errors/map_prediction_output_error___GBRT.nc
  - work/diag_plot_mlr_models/plot_errors/map_prediction_output_error___LASSO.nc

perfect, many thanks, Manu! All fine by me then, cheers :beer: Do you need a sci reviewer too? I don't think so since you're the jack of all trades for these recipes, if I'm enough for the review then pls let me know and I'll merge this beast :grin:

Cheers :beers:  no need for a scientific review, results look exactly like expected!

BTW - forgot about it - you reckon any documentation is warranted for the new behaviour?

Documentation has been added in the form of a docstring that is shown on RTD. Just search for "random_state" here (https://esmvaltool--2900.org.readthedocs.build/en/2900/api/esmvaltool.diag_scripts.mlr/models.html#optional-parameters-for-class-initialization) :grin:

perfect, cheers, bud! :beer: I'll merge when tests have finished :+1:

authors: schlunma valeriupredoi


text:
Filename Check

Hi,
I am running the script on Windows.
I have some wired page title ( ':' and '&' characters ). This causes the script to either fail or miss opening the file.
Could there be filename check being added ?
Could there be folder creation as well ? I need to manually create the Markdown folder at the beginning.

Yes, please. This is like Programming 101 :/

I have the same issue.
It seems someone fixed it in his fork: https://github.com/meridius/confluence-to-markdown (atleast I tried and it works).

authors: Sryther m-cat sbertrand-witekio


text:
Add support for network and data flow diagrams

This mimics the existing behavior for Authorization Boundaries
Closes: #222
Closes: #223

Because of some formatting changes, the diff for this may be slightly better if the "ignore whitespace" option is applied.

repo: EasyDynamics/oscal-react-library


text:
Combine multiple key paths into one property

I have data like this:
[
    {
    "id" : 1,
    "data" : "some data"
    "locale" : "en",
    "name" : "foo"
    }, ...
]

I need to create two model objects from this. One should link to another: object -> object translation
object : { "object id": 1, "data" : "some data" }
object translation : { "object translation id" : "1_en", "name" : "foo"}

So for object translation id I should combine two key paths from dictionary id + locale . I can't understand how to do it with existing methods of EKObjectMapping :(

Seems like you have two options:

Use mapKeyPathToProperty:withValueBlock:
Override initWithProperties:, and just create your object as usual.

I understand both of those are not really convenient, however with that JSON structure it's really hard to propose something different, even with different mappers, not only EasyMapping =)

authors: DenHeadless Rusik

repo: EasyMapping/EasyMapping


text:
Update free-programming-books.md

C Elements of Style was published by M&T books in 1992. This book covers only the C language and is a bit out dated. However it still contains a lot of good advice.
Ref.: http://www.oualline.com/books.free/style/index.html

Nice! Would you like to add the author name? #2383

"C elements of style" - Book by Steve Oualline

authors: dishantrathi eshellman

repo: EbookFoundation/free-programming-books


text:
Add a very good and comprehensive Verilog tutorial

What does this PR do?
Add resource(s)
For resources
Description
A very good and comprehensive tutorial to get into learning and using Verilog
Why is this valuable (or not)?
It not only teaches the language but also good practices in HW design in general, such as formal verification and simulation using freely available tools.
How do we know it's really free?
Nothing states otherwise afaict. There is no apparent license neither on the website nor in the course material.
Checklist:

[x] Read our contributing guidelines
[x] Search for duplicates.
[x] Include author(s) and platform where appropriate.
[x] Put lists  in alphabetical order, correct spacing.
[x] Add needed indications (PDF, access notes, under construction)

Followup

Check the output of Travis-CI for linter errors!

Thanks, and welcome to free-programming-books!

Thanks, and welcome to free-programming-books!

authors: eshellman tcdude


text:
Add Hebrew online courses

What does this PR do?
Add Hebrew courses by campus.gov.il
Checklist:

[x] Read our contributing guidelines
[X] Search for duplicates.
[x] Include author(s) and platform where appropriate.
[X] Put lists in alphabetical order, correct spacing.
[x] Add needed indications (PDF, access notes, under construction)

Followup

Check the output of Travis-CI for linter errors!

love it.
Thanks, and welcome to free-programming-books!

authors: eshellman tomer


text:
Add Implementing Regular Expressions by Russ Cox

What does this PR do?
Add resource(s) | Remove resource(s) | Add info | Improve repo
For resources
Description
Why is this valuable (or not)?
In-depth regex implementation guide by the man that made google codesearch
How do we know it's really free?
It's hosted for free on his website
For book lists, is it a book? For course lists, is it a course? etc.
Checklist:

[x] Read our contributing guidelines.
[x] Search for duplicates.
[x] Include author(s) and platform where appropriate.
[x] Put lists in alphabetical order, correct spacing.
[x] Add needed indications (PDF, access notes, under construction).
[x] Used an informative name for this pull request.

Follow-up

Check the status of GitHub Actions and resolve any reported warnings!

not a book


text:
Estonian books

What does this PR do?
Add resource(s) for Estonian
For resources
Description
Estonian resources in Javascript, databases and SQL
Why is this valuable (or not)?
It is valuable because it increases the list of valuable resources to anyone wanting to learn programming in Estonian.
How do we know it's really free?
You can access all the links yourself and they are university resources.
For book lists, is it a book? For course lists, is it a course? etc.
There is a course and student files
Checklist:

[x] Read our contributing guidelines.
[x] Search for duplicates.
[x] Include author(s) and platform where appropriate.
[x] Put lists in alphabetical order, correct spacing.
[x] Add needed indications (PDF, access notes, under construction).
[x] Used an informative name for this pull request.

Follow-up

Check the status of GitHub Actions and resolve any reported warnings!

resource appear to have been updated already

authors: TriinK eshellman


text:
added cloud computing book

What does this PR do?
Add resource(s) | Remove resource(s) | Add info | Improve repo
For resources
Description
Why is this valuable (or not)?
How do we know it's really free?
For book lists, is it a book? For course lists, is it a course? etc.
Checklist:

[ ] Read our contributing guidelines.
[ ] Search for duplicates.
[ ] Include author(s) and platform where appropriate.
[ ] Put lists in alphabetical order, correct spacing.
[ ] Add needed indications (PDF, access notes, under construction).
[ ] Used an informative name for this pull request.

Follow-up

Check the status of GitHub Actions and resolve any reported warnings!

@eshellman sir, I have checked this book online for a more reliable source. The book is available as individual chapters from the publishers, but that should be accessed from the website's parent directory, which is not feasible. Can we add this?

With just a few exceptions, we don't accept entries for books which require a working email address and account.

With just a few exceptions, we don't accept entries for books which require a working email address and account.

Did you meant to comment here @eshellman sir? This book does not require a working account. The Pascal book here requires: #9459

With just a few exceptions, we don't accept entries for books which require a working email address and account.

Did you meant to comment here @eshellman sir? This book does not require a working account. The Pascal book here requires: #9459

The book does not require a working account

I attached the comment to the wrong line, sorry about that.

authors: eshellman innovation-machine jokoyoski


text:
[FIF-164] Catch when tokens expire

Login to the buzz site with a registered user.
In the dev tools console

Go to Application / SessionStorage.
Modify the validatingToken key
Set an invalid key or an expired key.

If the key is expired or invalid, redirect to the login screen

I am still getting an error when I navigate to another page. Here is what I did.
1. Log in as [projectedfibuzzdemo@gmail.com](mailto:projectedfibuzzdemo@gmail.com)

2. Navigate to a student's detail page.

3. Alter the validating token - switch the case of the last character.

4. Click the navigation link back to roster.

5. I expected to be redirected back to login, but instead it threw this exception.

I updated the JWT validation. You must include REACT_APP_URI_DISCOVERY=https://accounts.google.com/.well-known/openid-configuration in your UI .env file.

REACT_APP_URI_DISCOVERY=https://accounts.google.com/.well-known/openid-configuration

I will update FIF-299 to make sure we use this URL to create the .env file in UI.

authors: jleiva-gap kurtjohnson-HS

repo: Ed-Fi-Exchange-OSS/EdFi-Project-Buzz


text:
Implement streamlit dashboard

leaving it here as a backlog. it runs with docker compose up dashboard and implements

traefik labels
docker image
a basic streamlit dashboard (no auth)

I will be adding more commits, aiming to cover #10

I merged this branch onto #12 so I'm closing this PR


text:
Github Link Opens In New Tab

Fixes Issues
Closes #2159
Proposed Changes

Makes Github link open in new tab by setting target to "_blank"

Check List (Check all the applicable boxes)

[X] My code follows the code style of this project.
[ ] My change requires changes to the documentation.
[ ] I have updated the documentation accordingly.
[X] All new and existing tests passed.
[X] This PR does not contain plagiarized content.
[X] The title of my pull request is a short description of the requested changes.

Screenshots
N/A

Note to reviewers

Should be fixed the indentation now. I have tested and it opens. noopener shows that's it's an outdated rel thingy and wouldn't allow me to commit.

repo: EddieHubCommunity/LinkFree


text:
Issue#4514 login button

Fixes Issue #4514

Changes proposed

Check List (Check all the applicable boxes)

[ ] My code follows the code style of this project.
[ ] My change requires changes to the documentation.
[ ] I have updated the documentation accordingly.
[ ] All new and existing tests passed.
[ ] This PR does not contain plagiarized content.
[ ] The title of my pull request is a short description of the requested changes.

Screenshots

Note to reviewers

Thank you for your contribution but this issue has already been assigned and has an open PR https://github.com/EddieHubCommunity/LinkFree/pull/4575


text:
Bug Fixes

Fixes Issue

Changes proposed

Check List (Check all the applicable boxes)

[ ] My code follows the code style of this project.
[ ] My change requires changes to the documentation.
[ ] I have updated the documentation accordingly.
[ ] All new and existing tests passed.
[ ] This PR does not contain plagiarized content.
[ ] The title of my pull request is a short description of the requested changes.

Screenshots

Note to reviewers

hi you created already a PR before. You don't need to create another one. YOu can close one.
Your existing PR #5263

Since this one looks good to merge with the same changes as #5263. I'm merging this one and closing the last one.


text:
RKC3000

Related issue

What changes does this PR do?
Screenshots (If any)
Questions

@E-fais
I have only added my name
Can you tell me what I am doing wrong.
I have to only add README file and push?

@E-fais I have only added my name
Can you tell me what I am doing wrong. I have to only add README file and push?
I hope you are committing from your local machine.
*Create a new branch
*Add your name in the correct alphabetical order in the README
*commit
*push branch
*Sync your forked repository with original repository
*Create pull request

@RKC3000 You can view in the Files changed section the codes taht you have been modified to.

There are a lot of supportive people here 👍
Feel free to for any help, let’s learn together ❤

@RKC3000 What is the status.. are you still working on this.?  do not hesitate to ask if you need any help. :)

Sorry @E-fais I was busy in Diwali work and all.
I will work on this tomorrow.

authors: AbbeyIT E-fais RKC3000


text:
Update README.md

Commit Changes
Related issue

Adding name
Screenshots (If any)
Questions

hey @Sandeep277 , please follow @Panquesito7 's comment.


text:
[OTHER][DOCS] Update links at bottom of README

What would you like to share?
Proposed change
-On line 80 and 81 at the bottom of the README
Discord Link Change
-Join our Discord community.
or
-Join our Discord community.
Youtube Link Change
-Subscribe to our YouTube channel.
or
-Subscribe to our YouTube channel.
This is in order to make the links a little more concise and help the flow of the document.
-Please post your thoughts to this update below
Additional information
No response

@Nithin108 go on for it :)

yes

any one review my pull request

@schmelto review my pull request and merge it

Hello @Nithin108 , Are you still working on this??

@TheRemyD @schmelto If this issue is not closed, can I work on it?

@schmelto @krshkodes here the PR for review - https://github.com/EddieHubCommunity/support/pull/3940

repo: EddieHubCommunity/support


text:
Please invite me to the GitHub Community Organization

Name
Muhammad Arham
Discord Username (if applicable)
muhammadarham_08040
Additional Context
I want to become the Part of this community!

Thanks!


text:
Please invite me to the GitHub Community Organisation.

Name: Onyeocha Melody
Additional Context:
Where did you meet Eddie?
Found his channel on youtube and i immediately liked his teaching pattern. I'm still very new to open source and i see this as an opportunity to start my journey into open source.
What do you like about this community/ why do you want to join?
I like how contribution from everyone matters and how people get to learn from each other and help each other grows.
I also love how the community has a mix of people from every level of expertise from noob to pro that means i get to learn from different people and their experiences

Invitation sent for the GitHub Organisation. Welcome to the community 🎉
Don't forget after accepting to make it public so it appears on your GitHub profile for everyone else to see, you can do this by finding your name in the GitHub organisation list and change the dropdown to public https://github.com/orgs/EddieJaoudeCommunity/people
Tips for practising:
Customise your GitHub profile, here is a live stream on it https://www.youtube.com/watch?v=cT6GXCuS0Zo
Practice repo, instructions on how to add your name to the README in the README https://github.com/EddieJaoudeCommunity/hacktoberfest-practice
Remember contributing to open source is not just about code, its about collaboration, communication and adding value
I hope that helps

Invitation sent for the GitHub Organisation. Welcome to the community 🎉
Don't forget after accepting to make it public so it appears on your GitHub profile for everyone else to see, you can do this by finding your name in the GitHub organisation list and change the dropdown to public https://github.com/orgs/EddieJaoudeCommunity/people
Tips for practising:
Customise your GitHub profile, here is a live stream on it https://www.youtube.com/watch?v=cT6GXCuS0Zo
Practice repo, instructions on how to add your name to the README in the README https://github.com/EddieJaoudeCommunity/hacktoberfest-practice
Remember contributing to open source is not just about code, its about collaboration, communication and adding value
I hope that helps

authors: Melocoder eddiejaoude

repo: EddieJaoudeCommunity/support


text:
Req. #029 - Reporte de Productos Más Vendidos

Descripción:
Quién: El administrador accede a la aplicación web con sus credenciales.
Qué: Genera un reporte de los productos más vendidos desde la opción "Reporte de Productos Más Vendidos" en la aplicación.
Por qué: Para identificar los productos populares y tomar decisiones informadas sobre el inventario y estrategias de ventas.

Criterios de Aceptación 1:
Dado: Un administrador dentro de la aplicación web de la tienda.
Cuando: Acceda a la opción "Reporte de Productos Más Vendidos".
Entonces: La aplicación web le mostrará una lista de los productos más vendidos, ordenados por cantidad vendida, con detalles como nombre del producto, cantidad vendida y categoría

Criterios de Aceptación 2:
Dado: Un administrador dentro de la aplicación web de la tienda.
Cuando: Acceda a la opción "Reporte de Productos Más Vendidos".
Entonces: La aplicación web permitirá al administrador seleccionar un rango de fechas para el período de ventas a analizar.

Criterios de Aceptación 3:
Dado: Un administrador dentro de la aplicación web de la tienda.
Cuando: Acceda a la opción "Reporte de Productos Más Vendidos".
Entonces: La aplicación web generará un informe descargable en formato PDF o CSV que contendrá la información de los productos más vendidos durante el período seleccionado.

Criterios de Aceptación 4:
Dado: Un administrador dentro de la aplicación web de la tienda.
Cuando: Acceda a la opción "Reporte de Productos Más Vendidos".
Entonces: La aplicación web enviará una notificación al administrador cuando el informe esté listo para su descarga, con un enlace directo para acceder al informe generado.

authors: ChristianCRJ EddyEscalanteU


text:
Few questions and one suggestion

Hello
I am using vue-tel-input as a child component.
My Main component is PhoneRegistrationModel.

                    <vue-tel-input
                        v-model="tel"
                        wrapperClasses="h-12 border-b-1 border-red-500 w-96"
                        autocomplete="mobile"
                        inputClasses="w-full"/>

                    {{phoneError}}
                    required

Using latest Chrome on Mac.
Now let me explain problems:

autocomplete="mobile" - whatevever i set as autocomplete, always shows my email.
autocomplete="off" - shows my email
I can enter anything i want in input field, does not shows me if field is valid  as on example.
On v-model i see the number as i type it, but there is not like in example where i can see country code as well: +66 956789...
Questions:
How can i display if phone is valid
How can i get full number with country code?

TO mention, i see all of these things in Vue dev tools, inside vue-tel-input component. The problem is i dont see them in parent (PhoneRegisterModal)
Less important: How i can stop input field to be populated with email instead to be empty or prepoluted with a phone number. To mention, i have tried: autocomplete="off", both on form and field, atucomplete="tel" autocomplete="mobile"
SUGGESTION:
Not bale to see i its implemented, but would be great when form validation fails, and user start typing to remove existing error message.
Thanks
V

@nezaboravi Sorry for the delay.

If you want to see what is the value of country, validation or full number, you can use the @input event, the second argument will be the PhoneNumber object from awesome-phonenumber.

Also, to prevent users from typing letters, you can set the prop valid-characters-only: true.

authors: iamstevendao nezaboravi

repo: EducationLink/vue-tel-input


text:
Options onlyCountries seems to change listing order

Hello,
Using option "onlyCountries" seems to change the order of the country displayed.
I wanted to select only some countries but keep the default alphabetic order but instead it keep the order specified inside onlyCountries options.
I think this is not the behaviour that should be used.
What do you think about it ?
Thanks
See : https://github.com/Yummy123123/vue-tel-input/commit/e6bca9db4918568e5fd9d56bbee99c39172a327d#diff-8f0933bb907db7c1cbc31e8b649644a0

Fixed in v4.4.1.


text:
SyntaxWarning with python 3.8+

In preparation for python 3.8+ compatibility, a number of is and is not checks in poly.py and basis.py need replacing. See below...
The compiler now produces a SyntaxWarning when identity checks (is and is not) are used with certain types of literals (e.g. strings, numbers). These can often work by accident in CPython, but are not guaranteed by the language spec. The warning advises users to use equality tests (== and !=) instead. (Contributed by Serhiy Storchaka in bpo-34850.)

This has been fixed in the latest push to develop (commit https://github.com/Effective-Quadratures/equadratures/commit/952983f4fece27f8b022e994ec96f381b9df47e9).

This has been fixed in the latest push to develop (commit https://github.com/Effective-Quadratures/equadratures/commit/952983f4fece27f8b022e994ec96f381b9df47e9).

repo: Effective-Quadratures/equadratures


text:
feat: add selfControlled prop to Pagination for indication of outside page control

SUMMARY:
Currently, the page would be redirected back to 1 if component rerender due to size change, and what will happen is, when we pass in value 2 to currentPage prop, on initial render of the component, it will trigger the onCurrentChange function automatically due to useEffect -> onSizeChangeHandler -> handleCurrentChange(1).
The new added prop will skip the handleCurrentChange(1) step
This changes is helpful for implementation like using url param to store page state from the outside.
GITHUB ISSUE (Open Source Contributors)
JIRA TASK (Eightfold Employees Only):
https://eightfoldai.atlassian.net/jira/software/c/projects/ENG/boards/29?modal=detail&selectedIssue=ENG-26836
https://eightfoldai.atlassian.net/jira/software/c/projects/ENG/boards/29?modal=detail&selectedIssue=ENG-27695
CHANGE TYPE:

[ ] Bugfix Pull Request
[x] Feature Pull Request

TEST COVERAGE:

[ ] Tests for this change already exist
[ ] I have added unittests for this change

TEST PLAN:

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@ba20e6b). Click here to learn what that means.
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #330   +/-   ##
=======================================
  Coverage        ?   88.33%
=======================================
  Files           ?      402
  Lines           ?    10803
  Branches        ?     3667
=======================================
  Hits            ?     9543
  Misses          ?     1237
  Partials        ?       23

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

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

authors: codecov-commenter szhang-eightfold

repo: EightfoldAI/octuple