Text wrapping for languages without space between words.

Some languages don't have a space character between words and that breaks text wrapping.
Affected languages: chinese, japanese, korean
Likely affect custom languages like Thai as well.

Since this is theoretically an issue in all languages - German, even English could have a single word that's too long for one line - there should be a fallback to character breaking when that happens.
Normally this involves hyphenation, but I have a suspicion that CJK shouldn't hyphenate, just break. Is that correct?

Yes CJK should not hyphenate.


Minimal POC of SSE support

I'm not actually a developer, least of all in Go. Also, I just chose the interval semi-randomly from some reference implementation of SSE in Go.
Apart from that the protocol stipulates that the Accept header isn't exactly mandatory, but the response must have a Content-Type of type/event-stream, though I have a feeling that would be too late in the process to define the FlushBuffer.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.


Module restructure

Moves the files to conform the Maven standard layout.
Previously the subprojects folder contained merely the build.gradles and build dirs.

I have re-added group, version and archivesBaseName to gradle.properties. Is this what you meant?

yes, thanks 👍

It seems my PR has broken the CircleCI builds. The solution should be to remove the test block


VS Code recommends extensions even if already installing via settings sync

This is a duplicate of https://github.com/microsoft/vscode/issues/173141 (which was automatically closed) with the requested info from that issue added

Version: 1.75.0-insider
Commit: e2816fe719a4026ffa1ee0189dc89bdfdbafb164
Date: 2023-02-01T15:16:00.736Z
Electron: 19.1.9
Chromium: 102.0.5005.194
Node.js: 16.14.2
V8: <IP_ADDRESS>-electron.0
OS: Darwin arm64 22.3.0
Sandboxed: Yes
Steps to Reproduce:

Install a remote extension that's recommended via .vscode/extensions.json locally and sync extensions via Settings Sync
Create a new Codespace (might also happen with dev containers in other contexts) but happens on every new Codespace in our use case
Observe toast asking to install recommended extensions
When looking at the extensions via "Show Recommendations", they are all either installing or already installed via settings sync

Remote Server logs

2023-02-10 07:18:33.341 [trace] Remote configuration data at /home/vscode/.vscode-remote
2023-02-10 07:18:33.341 [trace] process arguments: {"_":[],"host":"<IP_ADDRESS>","port":"0","connection-token-file":"/home/vscode/.vscode-remote/data/Machine/.connection-token-853b32bad26ed5ffe2d29b95be45adc7f753e35a-insider","without-connection-token":false,"disable-websocket-compression":false,"print-startup-performance":false,"print-ip-address":false,"accept-server-license-terms":true,"server-data-dir":"/home/vscode/.vscode-remote","enable-smoke-test-driver":false,"disable-telemetry":false,"disable-workspace-trust":false,"log":["trace"],"force-disable-user-env":true,"enable-sync":false,"extensions-download-dir":"/home/vscode/.vscode-remote/extensionsCache","install-extension":["ms-azuretools.vscode-docker","/home/vscode/hello-githug.vsix","dbaeumer.vscode-eslint","ethan-reesor.vscode-byebug","github.copilot","misogi.ruby-rubocop","manuelpuyol.erb-linter","mutantdino.resourcemonitor","rebornix.ruby","wingrunr21.vscode-ruby","craigmaslowski.erb","jasonnutter.vscode-codeowners","eamodio.gitlens","graphql.vscode-graphql","miguel-savignano.ruby-symbols","markis.code-coverage","meta.relay","KoichiSasada.vscode-rdbg","sorbet.sorbet-vscode-extension"],"install-builtin-extension":["GitHub.codespaces","GitHub.vscode-pull-request-github"],"list-extensions":false,"show-versions":false,"force":false,"do-not-sync":true,"pre-release":false,"start-server":true,"enable-remote-auto-shutdown":true,"remote-auto-shutdown-without-delay":false,"use-host-proxy":false,"without-browser-env-var":false,"help":false,"version":false,"compatibility":"1.63","user-data-dir":"/home/vscode/.vscode-remote/data","builtin-extensions-dir":"/vscode/bin/linux-x64/853b32bad26ed5ffe2d29b95be45adc7f753e35a-insider/extensions","extensions-dir":"/home/vscode/.vscode-remote/extensions","logsPath":"/home/vscode/.vscode-remote/data/logs/20230210T071833"}
2023-02-10 07:18:33.341 [info]
2023-02-10 07:18:33.341 [trace] [File Watcher (node.js)] Request to start watching: /home/vscode/.vscode-remote/data/Machine (excludes: , includes: ),/home/vscode/.vscode-remote/data/Machine/settings.json (excludes: , includes: )
2023-02-10 07:18:33.351 [trace] resolveShellEnv(): running (macOS/Linux)
2023-02-10 07:18:33.352 [trace] getUnixShellEnvironment#runAsNode undefined
2023-02-10 07:18:33.352 [trace] getUnixShellEnvironment#noAttach undefined
2023-02-10 07:18:33.352 [trace] getUnixShellEnvironment#env
2023-02-10 07:18:33.359 [trace] Started scanning user extensions {"$mid":1,"external":"file:///home/vscode/.vscode-remote/extensions/extensions.json","path":"/home/vscode/.vscode-remote/extensions/extensions.json","scheme":"file"}
2023-02-10 07:18:33.361 [trace] ExtensionManagementService#cleanUp
2023-02-10 07:18:33.361 [trace] getUnixShellEnvironment#shell /bin/bash
2023-02-10 07:18:33.361 [trace] getUnixShellEnvironment#spawn ["-i","-l","-c"] '/vscode/bin/linux-x64/853b32bad26ed5ffe2d29b95be45adc7f753e35a-insider/node'  -p '"97b419d2192c" + JSON.stringify(process.env) + "97b419d2192c"'
2023-02-10 07:18:33.366 [info] Extension host agent started.
2023-02-10 07:18:33.394 [debug] Removing uninstalled extensions: []
2023-02-10 07:18:33.394 [trace] Started scanning user extensions {"$mid":1,"fsPath":"/home/vscode/.vscode-remote/extensions","external":"file:///home/vscode/.vscode-remote/extensions","path":"/home/vscode/.vscode-remote/extensions","scheme":"file"}
2023-02-10 07:18:33.395 [trace] [File Watcher (node.js)] Request to start watching: /home/vscode/.vscode-remote/extensions (excludes: , includes: )
2023-02-10 07:18:33.396 [trace] [File Watcher (node.js)] Started watching: '/home/vscode/.vscode-remote/data/Machine'
2023-02-10 07:18:33.397 [trace] [File Watcher (node.js)] Started watching: '/home/vscode/.vscode-remote/data/Machine/settings.json'
2023-02-10 07:18:33.398 [info] Started initializing default profile extensions in extensions installation folder. file:///home/vscode/.vscode-remote/extensions
2023-02-10 07:18:33.398 [trace] Started scanning user extensions {"$mid":1,"fsPath":"/home/vscode/.vscode-remote/extensions","external":"file:///home/vscode/.vscode-remote/extensions","path":"/home/vscode/.vscode-remote/extensions","scheme":"file"}
2023-02-10 07:18:33.402 [trace] Deleting from cache /home/vscode/.vscode-remote/extensionsCache/ritwickdey.liveserver-5.7.9
2023-02-10 07:18:33.402 [trace] Deleting from cache /home/vscode/.vscode-remote/extensionsCache/ms-python.python-2023.3.10411009
2023-02-10 07:18:33.404 [trace] Scanned user extensions: 0
2023-02-10 07:18:33.405 [trace] ExtensionManagementService#removeGeneratedFolders
2023-02-10 07:18:33.406 [trace] [File Watcher (node.js)] Started watching: '/home/vscode/.vscode-remote/extensions'
2023-02-10 07:18:33.408 [debug] ComputeTargetPlatform: linux-x64
2023-02-10 07:18:33.408 [trace] Scanned user extensions: 0
2023-02-10 07:18:33.414 [trace] [File Watcher (node.js)] [raw] ["rename"] extensions.json
2023-02-10 07:18:33.414 [trace] [File Watcher (node.js)] [raw] ["change"] extensions.json
2023-02-10 07:18:33.415 [trace] [File Watcher (node.js)] [ADDED] /home/vscode/.vscode-remote/extensions/extensions.json
2023-02-10 07:18:33.455 [info] Completed initializing default profile extensions in extensions installation folder. file:///home/vscode/.vscode-remote/extensions
2023-02-10 07:18:33.456 [trace] [File Watcher (node.js)] Request to start watching: /home/vscode/.vscode-remote/extensions/extensions.json (excludes: , includes: )
2023-02-10 07:18:33.457 [trace] Scanned user extensions: 0
2023-02-10 07:18:33.458 [trace] RequestService#request (node) - begin https://marketplace.visualstudio.com/_apis/public/gallery/extensionquery
2023-02-10 07:18:33.458 [trace] resolveShellEnv(): skipped (--force-disable-user-env)
2023-02-10 07:18:33.471 [trace] Started scanning user extensions {"$mid":1,"fsPath":"/home/vscode/.vscode-remote/extensions","external":"file:///home/vscode/.vscode-remote/extensions","path":"/home/vscode/.vscode-remote/extensions","scheme":"file"}
2023-02-10 07:18:33.471 [trace] [File Watcher (node.js)] Started watching: '/home/vscode/.vscode-remote/extensions/extensions.json'
2023-02-10 07:18:33.472 [trace] Scanned user extensions: 0
2023-02-10 07:18:33.490 [trace] [File Watcher (node.js)] >> normalized [ADDED] /home/vscode/.vscode-remote/extensions/extensions.json
2023-02-10 07:18:33.515 [trace] [File Watcher (node.js)] [CHANGED] /home/vscode/.vscode-remote/extensions/extensions.json
2023-02-10 07:18:33.590 [trace] [File Watcher (node.js)] >> normalized [CHANGED] /home/vscode/.vscode-remote/extensions/extensions.json
2023-02-10 07:18:33.607 [trace] RequestService#request (node) - success https://marketplace.visualstudio.com/_apis/public/gallery/extensionquery
2023-02-10 07:18:33.611 [trace] RequestService#request (node) - begin https://marketplace.visualstudio.com/_apis/public/gallery/extensionquery
2023-02-10 07:18:33.612 [trace] resolveShellEnv(): skipped (--force-disable-user-env)
2023-02-10 07:18:33.708 [info] [<IP_ADDRESS>][e5e321a0][ManagementConnection] New connection established.
2023-02-10 07:18:33.751 [trace] getUnixShellEnvironment#raw
2023-02-10 07:18:33.751 [trace] getUnixShellEnvironment#stderr bash: cannot set terminal process group (-1): Inappropriate ioctl for device
bash: no job control in this shell
2023-02-10 07:18:33.752 [trace] getUnixShellEnvironment#result
2023-02-10 07:18:33.782 [trace] Started scanning system extensions
2023-02-10 07:18:33.782 [trace] Started scanning user extensions {"$mid":1,"fsPath":"/home/vscode/.vscode-remote/extensions/extensions.json","external":"file:///home/vscode/.vscode-remote/extensions/extensions.json","path":"/home/vscode/.vscode-remote/extensions/extensions.json","scheme":"file"}
2023-02-10 07:18:33.782 [trace] ExtensionManagementService.refreshReportedCache
2023-02-10 07:18:33.783 [trace] RequestService#request (node) - begin https://az764295.vo.msecnd.net/extensions/marketplace.json
2023-02-10 07:18:33.783 [trace] resolveShellEnv(): skipped (--force-disable-user-env)
2023-02-10 07:18:33.783 [trace] Started scanning user extensions {"$mid":1,"fsPath":"/home/vscode/.vscode-remote/extensions/extensions.json","external":"file:///home/vscode/.vscode-remote/extensions/extensions.json","path":"/home/vscode/.vscode-remote/extensions/extensions.json","scheme":"file"}
2023-02-10 07:18:33.861 [info] [<IP_ADDRESS>][d23ddb36][ExtensionHostConnection] New connection established.
2023-02-10 07:18:33.865 [info] [<IP_ADDRESS>][d23ddb36][ExtensionHostConnection] <3687> Launched Extension Host Process.
2023-02-10 07:18:33.926 [info] Getting Manifest... github.vscode-pull-request-github
2023-02-10 07:18:33.927 [info] Getting Manifest... github.codespaces
2023-02-10 07:18:33.949 [info] Installing extension: github.codespaces
2023-02-10 07:18:33.950 [info] Installing extension: github.vscode-pull-request-github
2023-02-10 07:18:35.530 [info] Extension signature verification: github.codespaces. Verification status: Verified.
2023-02-10 07:18:35.664 [info] Extension signature verification: github.vscode-pull-request-github.  Verification status: Verified.
2023-02-10 07:18:40.389 [info] Extension installed successfully: misogi.ruby-rubocop
2023-02-10 07:18:40.423 [info] Renamed to /home/vscode/.vscode-remote/extensions/wingrunr21.vscode-ruby-0.28.0
2023-02-10 07:18:40.423 [info] Renamed to /home/vscode/.vscode-remote/extensions/markis.code-coverage-1.8.6
2023-02-10 07:18:40.428 [info] Extracting extension completed. wingrunr21.vscode-ruby
2023-02-10 07:18:40.428 [info] Extracting extension completed. markis.code-coverage
2023-02-10 07:18:40.433 [info] Extracted extension to /home/vscode/.vscode-remote/extensions/.ab3711c9-b089-401a-a129-916b93d079b4: mutantdino.resourcemonitor
2023-02-10 07:18:40.458 [info] Extension installed successfully: ethan-reesor.vscode-byebug
2023-02-10 07:18:40.475 [info] Extracted extension to /home/vscode/.vscode-remote/extensions/.7b58a005-9ac4-41d1-adc5-4c9b0534c0c5: dbaeumer.vscode-eslint
2023-02-10 07:18:40.493 [info] Renamed to /home/vscode/.vscode-remote/extensions/mutantdino.resourcemonitor-1.0.7
2023-02-10 07:18:40.496 [info] Extracting extension completed. mutantdino.resourcemonitor
2023-02-10 07:18:40.536 [info] Extracted extension to /home/vscode/.vscode-remote/extensions/.5b9ec9a9-4272-4aa6-a322-55102b679c52: rebornix.ruby
2023-02-10 07:18:40.558 [info] Extension installed successfully: manuelpuyol.erb-linter
2023-02-10 07:18:40.559 [info] Renamed to /home/vscode/.vscode-remote/extensions/dbaeumer.vscode-eslint-2.4.0
2023-02-10 07:18:40.562 [info] Extracting extension completed. dbaeumer.vscode-eslint
2023-02-10 07:18:40.588 [info] Extension signature verification: craigmaslowski.erb. Verification status: Verified.
2023-02-10 07:18:40.598 [info] Extracted extension to /home/vscode/.vscode-remote/extensions/.141f64ab-160b-4233-a606-5b731be9a364: craigmaslowski.erb
2023-02-10 07:18:40.629 [info] Extension installed successfully: wingrunr21.vscode-ruby
2023-02-10 07:18:40.644 [info] Finished waiting for already requested installing extension wingrunr21.vscode-ruby rebornix.ruby
2023-02-10 07:18:40.645 [info] Renamed to /home/vscode/.vscode-remote/extensions/rebornix.ruby-0.28.1
2023-02-10 07:18:40.648 [info] Extracting extension completed. rebornix.ruby
2023-02-10 07:18:40.672 [info] Extension signature verification: ms-azuretools.vscode-docker. Verification status: Verified.
2023-02-10 07:18:40.699 [info] Extension signature verification: github.copilot. Verification status: Verified.
2023-02-10 07:18:40.702 [info] Extension signature verification: jasonnutter.vscode-codeowners. Verification status: Verified.
2023-02-10 07:18:40.713 [info] Renamed to /home/vscode/.vscode-remote/extensions/craigmaslowski.erb-0.0.1
2023-02-10 07:18:40.717 [info] Extracting extension completed. craigmaslowski.erb
2023-02-10 07:18:40.718 [info] Extension signature verification: koichisasada.vscode-rdbg. Verification status: Verified.
2023-02-10 07:18:40.749 [info] Extracted extension to /home/vscode/.vscode-remote/extensions/.8f02c4cb-f30e-420a-879d-121130bff1e3: koichisasada.vscode-rdbg
2023-02-10 07:18:40.782 [info] Extension installed successfully: markis.code-coverage
2023-02-10 07:18:40.833 [info] Renamed to /home/vscode/.vscode-remote/extensions/koichisasada.vscode-rdbg-0.1.0
2023-02-10 07:18:40.836 [info] Extracting extension completed. koichisasada.vscode-rdbg
2023-02-10 07:18:40.897 [info] Extension installed successfully: mutantdino.resourcemonitor
2023-02-10 07:18:40.913 [info] Extension signature verification: miguel-savignano.ruby-symbols. Verification status: Verified.
2023-02-10 07:18:40.969 [info] Extension signature verification: graphql.vscode-graphql-syntax. Verification status: Verified.
2023-02-10 07:18:40.980 [info] Extracted extension to /home/vscode/.vscode-remote/extensions/.5e4af896-10cc-4f0d-b57c-d656daa15e4b: ms-azuretools.vscode-docker
2023-02-10 07:18:40.993 [info] Extracted extension to /home/vscode/.vscode-remote/extensions/.f7f2ac83-1c3c-49a0-9877-880f8b9bdc24: miguel-savignano.ruby-symbols
2023-02-10 07:18:41.001 [info] Extracted extension to /home/vscode/.vscode-remote/extensions/.c1a24e6d-a2fb-4177-a198-a0aef4ff30c4: graphql.vscode-graphql-syntax
2023-02-10 07:18:41.047 [info] Extension signature verification: eamodio.gitlens. Verification status: Verified.
2023-02-10 07:18:41.068 [info] Extension installed successfully: dbaeumer.vscode-eslint
2023-02-10 07:18:41.146 [info] Renamed to /home/vscode/.vscode-remote/extensions/ms-azuretools.vscode-docker-1.23.3
2023-02-10 07:18:41.146 [info] Renamed to /home/vscode/.vscode-remote/extensions/miguel-savignano.ruby-symbols-0.1.8
2023-02-10 07:18:41.146 [info] Renamed to /home/vscode/.vscode-remote/extensions/graphql.vscode-graphql-syntax-1.0.6
2023-02-10 07:18:41.153 [info] Extracting extension completed. miguel-savignano.ruby-symbols
2023-02-10 07:18:41.153 [info] Extracting extension completed. graphql.vscode-graphql-syntax
2023-02-10 07:18:41.155 [info] Extracting extension completed. ms-azuretools.vscode-docker
2023-02-10 07:18:41.174 [info] Extracted extension to /home/vscode/.vscode-remote/extensions/.6ec0931b-b94d-4ef5-bf52-9abb771cd50f: jasonnutter.vscode-codeowners
2023-02-10 07:18:41.182 [info] Extracted extension to /home/vscode/.vscode-remote/extensions/.4aa64f8a-3202-4428-a30f-20bbdbed5672: github.copilot
2023-02-10 07:18:41.206 [info] Extension installed successfully: rebornix.ruby
2023-02-10 07:18:41.291 [info] Renamed to /home/vscode/.vscode-remote/extensions/jasonnutter.vscode-codeowners-1.1.1
2023-02-10 07:18:41.292 [info] Renamed to /home/vscode/.vscode-remote/extensions/github.copilot-1.72.8614
2023-02-10 07:18:41.295 [info] Extracting extension completed. jasonnutter.vscode-codeowners
2023-02-10 07:18:41.295 [info] Extracting extension completed. github.copilot
2023-02-10 07:18:41.328 [info] Extracted extension to /home/vscode/.vscode-remote/extensions/.a911cc56-ff7f-466f-a113-83d23bd28e83: meta.relay
2023-02-10 07:18:41.383 [info] Extension installed successfully: craigmaslowski.erb
2023-02-10 07:18:41.409 [info] Renamed to /home/vscode/.vscode-remote/extensions/meta.relay-1.0.2
2023-02-10 07:18:41.411 [info] Extracting extension completed. meta.relay
2023-02-10 07:18:41.446 [info] Extension installed successfully: koichisasada.vscode-rdbg
2023-02-10 07:18:41.582 [info] Extension installed successfully: miguel-savignano.ruby-symbols
2023-02-10 07:18:41.588 [info] Extracted extension to /home/vscode/.vscode-remote/extensions/.18130ff0-7166-4bc0-9adc-035664051ef3: eamodio.gitlens
2023-02-10 07:18:41.758 [info] Renamed to /home/vscode/.vscode-remote/extensions/eamodio.gitlens-13.2.0
2023-02-10 07:18:41.774 [info] Extracting extension completed. eamodio.gitlens
2023-02-10 07:18:41.899 [info] Extension installed successfully: ms-azuretools.vscode-docker
2023-02-10 07:18:42.019 [info] Extracted extension to /home/vscode/.vscode-remote/extensions/.7dd2616e-8d52-47a9-b413-afa44d401869: sorbet.sorbet-vscode-extension
2023-02-10 07:18:42.131 [info] Extension installed successfully: jasonnutter.vscode-codeowners
2023-02-10 07:18:42.294 [info] Renamed to /home/vscode/.vscode-remote/extensions/sorbet.sorbet-vscode-extension-0.3.18
2023-02-10 07:18:42.295 [info] Extracting extension completed. sorbet.sorbet-vscode-extension
2023-02-10 07:18:42.392 [info] Extension installed successfully: github.copilot
2023-02-10 07:18:42.607 [info] Extension installed successfully: meta.relay
2023-02-10 07:18:42.810 [info] Extension installed successfully: eamodio.gitlens
2023-02-10 07:18:42.986 [info] Extension installed successfully: sorbet.sorbet-vscode-extension
2023-02-10 07:18:43.249 [info] Extension signature verification: graphql.vscode-graphql. Verification status: Verified.
2023-02-10 07:18:43.410 [info] Extracted extension to /home/vscode/.vscode-remote/extensions/.96e6e3dd-4f54-4468-bc99-f79f6e2d6550: graphql.vscode-graphql
2023-02-10 07:18:43.658 [info] Renamed to /home/vscode/.vscode-remote/extensions/graphql.vscode-graphql-0.8.5
2023-02-10 07:18:43.659 [info] Extracting extension completed. graphql.vscode-graphql
2023-02-10 07:18:43.894 [info] Extension installed successfully: graphql.vscode-graphql-syntax
2023-02-10 07:18:43.894 [info] Extension installed successfully: graphql.vscode-graphql

Reopened the other issue. Lets continue over there.


Which API supports which Authentication Mechanism?

Looking at the description in: https://docs.microsoft.com/en-us/azure/cosmos-db/database-security
It is not clear which API: Core(SQL) API, API for MongoDB, Cassandra API, Gremlin API, Table API
Supports which authentication mechanism: Primary/Secondary Key, Resource Token, Active Directory
Can you please clarify?

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

ID: 6b791922-4cff-59b3-ea11-e13d5c55ffe4
Version Independent ID: d1e2e03c-ad04-f570-b122-c0382ae4bf65
Content: Database security - Azure Cosmos DB
Content Source: articles/cosmos-db/database-security.md
Service: cosmos-db
GitHub Login: @markjbrown
Microsoft Alias: mjbrown

@becke-ch-s0-v1 We are currently looking into this and will get back to you shortly.

All database API's support master key authentication.
Only SQL API supports Azure AD authentication and RBAC. and currently only in the .NET and Java SDKs. SQL API also supports resource tokens via it's REST API.

Hi @markjbrown , Thank you for your feedback. Question - isn't it a security risk to store the master key, which gives the user unrestricted access to the DB, at the client side? (most other azure DBs support a more fine granular access control).

Yes, it absolutely is a security risk. You should use the same care with the master key that you would for any key-based authentication and never build applications which require storing the database's master keys on a client device.

If no further questions will close this.
#please-close

Hi @markjbrown , Thank you for your feedback and yes this issue can be closed.


Web Docs are not formated correctly in Firefox.

✖ USAGE QUESTIONS → Use these dedicated resources:
Docs - http://react.semantic-ui.com
Chat - https://gitter.im/Semantic-Org/Semantic-UI-React
SO - http://stackoverflow.com/search?q=semantic-ui-react
✔ BUGS → This form is required:
Steps
Use Firefox.
Go to ANY semantic react component such as:
https://react.semantic-ui.com/views/card#card-example-groups
And click view code Sample.
Expected Result
Expect the code window to be fully expanded to the container.
Actual Result
Does not expand and you have to scroll to see it all.
Version
Sorry, I do not know where to put this. It is a website error.
https://i.imgur.com/X1Yf816.png

Duplicate, #1912.


BibIndex: add possibility to transliterate phrases

Originally on 2012-06-13

It will be useful to add a possibility to transliterate phrases upon indexing time, especially for author names.  This will read string stored in the DB and will optionally generate more terms to index, quite like stemming does, depending on index configuration.

We may want to separate generated terms into different indexes though, in case one would like to search for exact value as opposed to 'fuzzy' transliterated value.  Kind of like Xapian does with its Z forms for stemming, so that people could search for both stemmed or non-stemmed version. This could be also applied to stemming, we've had such requests in the past.

We could use unidecode for this.  Theodoros writes:

From all(?) the packages, I found that Uridecode
(http://pypi.python.org/pypi/Unidecode) supports most of the languages
that could be transliterated (although, for Greek it does not support
the standard ISO 843 but a 'custom' one which is not very good as a
practice. More details for the official transliteration standards for
Greek, here: http://transliteration.eki.ee/pdf/Greek.pdf)

The usage is very simple and I run an example with the following VERY
complex Unicode string (with Hebrew, Hindi, Chinese and Greek):
---------------
The decomposition mapping is <츠, U+11B8>, and not <0x110E, ᅳ, 11B8>.

The title says פעילות הבינאום, W3C in Hebrew

abcáßçकखी國際𐎄𐎔𐎘
Ελληνικά
---------------

and is converted to:

---------------
The decomposition mapping is <ceu, b>, and not <c, eu, 11B8>.

The title says p`ylvt hbynvm, W3C in Hebrew

abcassckkhiiGuo Ji
Ellenika
---------------

As for per-index configuration of the transliteration, see also #852.

Superseded by icu support in ES and Invenio 3


Highlight last block navigated to in page view

JIRA: https://openedx.atlassian.net/browse/MA-1349

@mikekatz please review

@mikekatz anything else?

:+1:


Ninject DI with SignalR in AspNetCore

Hi, I have been trying out Ninject.Web.AspNetCore in combination with Microsoft.AspNetCore.SignalR to handle websockets and I've stumbled upon an issue which I haven't been able to figure out yet.
SignalR
SignalR hubs
SignalR works by adding SignalR.Hubs to your server project. These hubs allow you to call methods on connected clients. The currently connected clients to each hub is managed by SignalR via a context object for each type of hub. Inside the scope of a hub, you have access to the matching context so you are able to send messages to the connected clients.
SignalR hubs context
It is also possible to communicate with connected clients outside of said hubs by injecting the context of a hub in a component of your choosing. This is achieved by requesting IHubContext<THub> from the DI container.
SignalR strongly typed hubs
The downside of using the regular IHubContext is that it relies on magic strings. To overcome this, SignalR provides a base class for strongly typed hubs: public abstract class Hub<T> : Microsoft.AspNetCore.SignalR.Hub where T : class.
Using this in combination with an interface, the hub (and also the context) become strongly typed.
Requesting typed hubs from from the DI container is done by requesting IHubContext<THub, T>.
This is the part where I'm experiencing difficulties to achieve with Ninject.
Retrieving IHubContext<THub> instances works out of the box but I've been unsuccessful in requesting a IHubContext<THub, T> instance.
Project
Hub setup
public interface IHubTest
{
    Task Push();
}

public class HubTest : Hub<IHubTest>
{
}

Application (Program.cs)
var kernel = new AspNetCoreKernel(new NinjectSettings { LoadExtensions = false }, new AspNetCoreModule());
var builder = WebApplication.CreateBuilder(args);
builder.Host.UseServiceProviderFactory(new NinjectServiceProviderFactory(kernel));
builder.Services.AddSignalR();

var app = builder.Build();
app.UseEndpoints(endpoints =>
{
    endpoints.MapHub<HubTest>("/test");
});
app.RunAsync();

Retrieving hub context
Right after the app.RunAsync():
// The following statement provides to correct IHubContext
var simpleContext = kernel.Get<IHubContext<HubTest>>();

However
// The following statement throws Ninject.ActivationException: "No matching bindings are available, and the type is not self-bindable."
var typedContext = kernel.Get<IHubContext<HubTest, IHubTest>>();

By removing builder.Host.UseServiceProviderFactory(new NinjectServiceProviderFactory(kernel)); (so using the default AspNetCore DI), the context is successfully retrieved:
// var typedContext = kernel.Get<IHubContext<HubTest, IHubTest>>();
var typedContext = app.Services.GetService<IHubContext<HubTest, IHubTest>>();

What I've tried so far
When adding the IHubContext<THub, T> to the builder.Services in any ServiceLifeTime, the Ninject.ActivationException is changed to "No constructor was available to create an instance of the implementation type."
builder.Services.AddTransient<IHubContext<HubTest, IHubTest>>();

Or explicitly binding in Ninject does give an instance of the context but it seems to give a copy of a singleton so no clients are connected to the resolved context:
kernel.Bind<IHubContext<HubTest, IHubTest>>()
    .ToMethod(ctx => builder.Services.BuildServiceProvider().GetService<IHubContext<HubTest, IHubTest>>());

for which the IDE already gives a warning by this diagnostics.
Explicit binding in Ninject to app.Services.GetService<IHubContext<HubTest, IHubTest>>() puts Ninject in a binding loop (or at least that is what I suspect is happening).
The question
I'm in the dark on how to set this up properly.
Am I missing something trivial or could I get a pointer to any direction on where the problem might be?
Is it possible to setup Ninject to also use the default DI instead of completely replacing it? Can the SignalR items be resolved via the default container through Ninject?
Please do request extra information if not all is clear.
Thanks in advance.
Resources:
SignalR hub: https://docs.microsoft.com/en-us/aspnet/core/signalr/hubs?view=aspnetcore-6.0
SignalR stronly typed hubs: https://docs.microsoft.com/en-us/aspnet/core/signalr/hubs?view=aspnetcore-6.0#strongly-typed-hubs
SignalR hub context injection: https://docs.microsoft.com/en-us/aspnet/core/signalr/hubcontext?view=aspnetcore-6.0#inject-a-strongly-typed-hubcontext
I used the Blazor example to setup my Program.cs: https://github.com/lord-executor/Ninject.Web.AspNetCore/blob/main/src/SampleBlazorApplication/Program.cs
Used nuget packages and version
Ninject.Web.AspNetCore: 6.0.0
Microsoft.AspNetCore.SignalR: 1.1.0

Well... that took a while. Sorry about that 😬.
I'm writing to let you know that I am currently looking into that issue. I can reproduce it and as of right now it doesn't make a lot of sense to me since open generic bindings should work just fine and pretty much the same for a single and two open generic types.
A "Ninject-only" example with a similar setup of interfaces and implementations seems to work just fine
kernel.Bind(typeof(IFoo<>)).To(typeof(TheFoo<>)).InSingletonScope();
kernel.Bind(typeof(IFoo<,>)).To(typeof(TheFoo<,>)).InSingletonScope();

kernel.Get<IFoo<Exception>>();
kernel.Get<IFoo<Exception, IEnumerable>>();

Cool, thanks for taking a look at it! Glad you found the cause.
Out of curiosity, I've tried what you mentioned and I think I can confirm:

a "Ninject-only" setup does work as expected
when skipping the filtering on the available bindings in ConstrainedGenericBindingResolver, the request could successfully resolve

A solution to the problem would be nice so I can clean up my current workaround but there is no pressure 👍
I have already looked at it as well but that's been unsuccessful so far.

I've already got a solution now. Just working on cleaning it up a bit and adding your scenario to my sample project in addition to the tests that I have already added.
 The constrained generic binding resolver is required to be compliant with Microsoft.Extensions.DependencyInjection which allows multiple services to be registered for the same interface (with open generics) which is substantially differnt from what Ninject normally does.
If you're interested, the relevant "compliance" tests can be found in Microsofts dotnet/runtime repo under

DependencyInjectionSpecificationTests.cs

ConstrainedOpenGenericServicesCanBeResolved
AbstractClassConstrainedOpenGenericServicesCanBeResolved
OpenGenericServicesCanBeResolved
ResolvesMixedOpenClosedGenericsAsEnumerable
InterfaceConstrainedOpenGenericServicesCanBeResolved

ServiceProviderIsServiceSpecificationTests.cs

OpenGenericsWithIsService

@toondedo The latest release v6.1.2 should now work without any workarounds and fully support strongly typed SignalR hubs with IHubContext<THub, T>. Please let me know if this works for you or if you run into other issues. Eventually I will add a better SignalR sample to the demo application, but for that I'll need to get a bit deeper into SignalR itself first.

I've had some time to test the v6.1.2. This release works as expected 👍
Thanks for solving the issue!

Excellent. And thank you @toondedo for taking the time to create an issue and following-up on it!


fontFamily and fontSize don't get correct attribute names

The attribute names in the SVG should be:
font-family
font-size
These are the only ones I tried, probably plenty more that need converting from camelCase to kebab-case.

Yeah, the weird thing (to me) about the svg spec is that some are kebab and others are camelCase. My understanding is kebab-case is for attributes that can be affected by CSS, while camelCase attributes cannot. Anyway, thanks for the catch.


[All] (COM to web add-in mapping) Fix typo - change ProgID > ProgId throughout.

Docs Build status updates of commit 25ab30e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/develop/make-office-add-in-compatible-with-existing-com-add-in.md
:white_check_mark:Succeeded

docs/excel/make-custom-functions-compatible-with-xll-udf.md
:white_check_mark:Succeeded

docs/reference/manifest/equivalentaddin.md
:white_check_mark:Succeeded

docs/reference/manifest/progid.md
:white_check_mark:Succeeded

docs/toc.yml
:white_check_mark:Succeeded

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

Docs Build status updates of commit e845d1f:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/develop/make-office-add-in-compatible-with-existing-com-add-in.md
:white_check_mark:Succeeded

docs/excel/make-custom-functions-compatible-with-xll-udf.md
:white_check_mark:Succeeded

docs/reference/manifest/equivalentaddin.md
:white_check_mark:Succeeded

docs/reference/manifest/progid.md
:white_check_mark:Succeeded

docs/toc.yml
:white_check_mark:Succeeded

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


Prevent users from creating 0-d tensors

Feature description

Panic when a user's trying to create an 0-d tensor.
Feature motivation

I am a beginner and try to create a scalar. I thought it should be 0-d (with shape []). However, this doesn't really work. I spent a lot of time debugging due to lack of hints.
Suggest a Solution
In Tensor's constructors:
assert!(D != 0)

Linking #1689

Yes, I agree we should prevent 0d tensors and instead create Scalar type outlined in #1689.


Revert "Docs/v2/update"

Reverts openproblems-bio/website#199. Tests were failing

Please don't this :)
The problem is caused by me having merged a PR in the V2 repo where the create_skeleton component was renamed to create_conponent.
We'll fix it asap.

fixed in #213


fix: incorrect data type when construct_path in chain

A incorrect data type error happened when executing _construct_path in chain.py as follows:
Error with message replace() argument 2 must be str, not int

The path is always a string. But the result of args.pop(param, "") is undefined.

thanks @Undertone0809!


Hot to use Alexa Cast

I installed AVS on my Raspberry Pi 3 to cast audio from my Amazon Music app, but the Pi doesn't appear as available device for audio casting in the app.
What can I do ?
What is the expected behavior?
The Pi should appear as available for audio casting in the Amazon Music app, like any other Alexa-enabled devices.
What behavior are you observing?
The Alexa-enabled Pi doesn't appear ready to cast from the Amazon Music app.
Tell us about your environment:
What version of the AVS Device SDK are you using?

Latest

Tell us what hardware you're using:

Raspberry Pi 3B

Tell us about your OS (Type & version):

Latest Raspbian

Hi,
Can you explain which version of the SDK you are using? Also, please provide any DEBUG9 logs so that we can better assist you.

I follow the tutorial available here: https://developer.amazon.com/en-US/docs/alexa/avs-device-sdk/raspberry-pi-script.html
The SDK used by the script should be the latest.
The DEBUG9 log is attached:
DEBUG9.txt
Thanks!

Any idea?

Hi @CyberSinh,
This feature should now be available. If you have an AVS SDK instance on the Raspberry Pi that can support music playback, registering it to the same account as your Amazon Music account will allow you to connect to the Raspberry Pi and play from that device. To do this, please enter the Amazon Music app and click the gear icon for settings, and click "Connect to a Device".
However, note that your Raspberry Pi AVS SDK product must support music playback.

Thanks @kjkh.
I did some more tests with the latest version of the SDK, but using the official script, the SampleApplication compilation fails. It seems that the problem is related to the lack of audio capture device, which is desired because it is not necessary for the intended use (audio streaming from the Amazon Music app). The Alexa device has been configured as "mic-less" in capabilities.
If my understanding of the compilation logs is correct, how do I compile SampleApplication on a device without a microphone?

Compiling the Alexa SDK on a Raspberry is a real pain. Why not provide directly precompiled binary?

It appears that compilation has not failed, but that instead this is a runtime failure.
SampleApplication specifically is intended to be used with a microphone implementation. If you do not wish to have one, and are familiar with C++, you can modify SampleApplication to bypass this behavior.
The quick and dirty way would be to no-op / return false in all of the methods in PortAudioMicrophoneWrapper.cpp: https://github.com/alexa/avs-device-sdk/blob/v1.26.0/SampleApp/src/PortAudioMicrophoneWrapper.cpp.
A more involved alternative would be to implement a NoOpMicrophoneWrapper implementation.

Hello @CyberSinh,
Due to the inactivity of this ticket, this ticket will be closed. Please feel free to re-open the ticket if you have more questions or feel that your question has not been answered fully.

I finally gave up on the idea of using Alexa Cast to stream Amazon Music with a Raspberry Pi.
It's a real hell: no pre-compiled binary, compilation that crashes the Pi (temperature too high, lack of memory to complete the compilation,...) and lasts for hours, no responsive technical support, no native mic-less support...
I've wasted enough time for an obviously unsupported scenario.


Dev rq 1094

Good point, Jad. I'm actually thinking about the same. Let me remove it.
On Wed, Mar 2, 2022 at 2:28 PM jadmsaadaot @.***> wrote:

@.**** commented on this pull request.
In request-management-api/request_api/models/FOIRawRequests.py
https://github.com/bcgov/foi-flow/pull/1616#discussion_r818156744:

@@ -245,6 +245,21 @@ def getbasequery(cls, additionalfilter=None, userid=None):
literal(None)),
],
else_ = FOIRawRequest.requestrawdata['dueDate'].astext).label('duedate')

   anotherfirstname = case([

                       (FOIRawRequest.status == 'Unopened' and FOIRawRequest.requestrawdata['anotherInformation']['firstName'] is not None,

Since Flex team will only see ministry requests, do we need to pull this
field from FOIRawRequests. Will this field be needed before that stage?
—
Reply to this email directly, view it on GitHub
https://github.com/bcgov/foi-flow/pull/1616#pullrequestreview-898248343,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AVTSVKIZATE3MP5BKMS2BN3U57TSDANCNFSM5PYYNBNQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID:
@.***>


[WIP] Fix adis16448 not starting

Describe problem solved by this pull request
I have finally figured out why our imu won't start with the upstream PX4 adis16448 driver.
Here is what I found

There has been CRC checks added in between our private PX4 and upstream PX4. The failure comes from a CRC check in

https://github.com/PX4/PX4-Autopilot/blob/a002a07ed52897dfd1082100b0af24f9b247916e/src/drivers/imu/adis16448/ADIS16448.cpp#L470-L474

This is because the IMU we are using is ADIS16448AMLZ. In 2015, the datasheet was updated to ADIS16448BMLZ, which included the burst read CRC functionality. (Check datasheet) It seems like you cannot do CRC checks on ADIS16448AMLZ although it is not explicitly stated.
All our vehicles seem to use the ADIS16448AMLZ.

Describe your solution
Disabling the CRC checks result in the imu drivers working / reading properly. In this PR, I have commented the CRC checks out.
I don't think the current state should be merged as it is, but not sure how we can work around this problem yet
Describe possible alternatives
It would be "nicer" if we could detect whether the imu plugged in is either ADIS16448AMLZ or ADIS16448BMLZ
In principle it should be better to have the CRC checks available, but since we can't replace all the IMUs, probably specifying manually to disable CRC checks could be an option
Test data / coverage
Connect to the mavlink shell (e.g. Tools/mavlink_shell.py)
adis16448 -S start

Additional context

Upstream issue: https://github.com/PX4/PX4-Autopilot/issues/16839
Thanks @weixuanzhang for helping on debugging the issue!
@tstastny Is there anyway that there are ADIS16448BMLZ imus that are available in the lab?

Codecov Report

:exclamation: No coverage uploaded for pull request base (develop@c25e7e2). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             develop       #9   +/-   ##
==========================================
  Coverage           ?   35.16%
==========================================
  Files              ?      724
  Lines              ?    56758
  Branches           ?        0
==========================================
  Hits               ?    19960
  Misses             ?    36798
  Partials           ?        0

Flag
Coverage Δ

unittests
35.16% <0.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

Continue to review full report at Codecov.

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

I think since Daniel did submit a PR upstream we just wait until that one is merged in, right?

@acfloria Yes, I will swing by the office today to test the upstream PR.

Closing, since this is to be replaced by https://github.com/PX4/PX4-Autopilot/pull/16855


Build image styles

[ ] Header hero
[ ] Header hero with caption
[ ] Inline image with caption

Added hero/inline images with captions. Original designs show reversed-out caption text over the image. I haven't implemented this because of accessibility and tech considerations. Currently, the hero image style is the same as the inline images, but the image is full-bleed.

Here's an example of an image without a caption: https://next.wellcomecollection.org/articles/fly-sugar-crystals

remove camera icon
remove extra space for caption


:14 - Invalid set index 'text' (on base: 'Nil') with value of type 'String

Godot version:
3.2.0
OS/device including version:
Windows 10 pro education 64 bit
Issue description:
onready vars doesn't guarantee a the tree will be ready for getting a nodepath
Steps to reproduce:

make 2x2 square of buttons
add tool script to root
use onready to store references to the buttons
use export string property to set and get text from all buttons.
try to edit property in editor.
see error.

Expected result

onready should only trigger when all child controls are ready
onready and _ready should retrigger on script edit.

Minimal reproduction project:
OnReadyBug.zip

onready var Control1A = $Control1/Control1A
onready var Control1B = $Control1/Control1B
onready var Control2A = $Control1/Control2A # - Control1 -> Control2
onready var Control2B = $Control1/Control2B #- Control1 -> Control2

I probably didn't understand something, but if you fix the code:
onready var Control2A = $Control1/Control2A;
onready var Control2B = $Control1/Control2B;

to:
onready var Control2A = $Control2/Control2A;
onready var Control2B = $Control2/Control2B;

You see no errors.

@akien-mga  reopen this please it was a typo but the bug still exists
OnReadyBug.zip
@DmDerbin next time try fixing the error before you report back that it wasn't a bug

This is weird. Setting the all_text variable will correctly set the button texts, but saving the scene always throws the mentioned error. Also the all_text variable is lost upon reload.
From my experience, it's better to use get_node() directly in the tool scripts instead of relying on onready variables. They don't work well with tool scripts.

this should be fixed then because we should be able to declare our nodes at the top of the script instead of having to retype them out every time we want to use them

Setters of exported variables (tool or not) can get called while the node is being instanced and before its children have been instanced. This means that it can happen before get_node() is even able to find the buttons.
Changing the script to check for is_inside_tree before trying to use the onready variables and using _ready to call the setter:
func _ready():
	_set_all_text(_all_text)

func _set_all_text(value):
	if is_inside_tree():
		Control1A.text = value;
		# …
	_all_text = value;

this is bad it though on ready should only be triggered when it "ready" this includes its children.
its compleatly defies what its suppost to be for.
no one is going to want to do something before its ready that doesn't even make sense

Tried reproducing in v4.3-dev6. It wasn't reproducible.
@Shadowblitz16 or someone else can confirm maybe.
4.3 auto-converted project: OnReadyBug.v4.3-dev6.zip

The error still appears when you reload the scene.
Though that's expected, because setters run before onready: https://github.com/godotengine/godot-proposals/issues/325


Discuss/Outline Follow Up Longitudinal Usability Study

As discussed in the weekly meeting, it might be helpful to conduct a longitudinal usability study with a banner and non-banner to better gauge which people relatively prefer, when made explicitly aware of both possibilities.
The need for this usability study will depend on the feedback from our paper submission, but in the meantime we may want to solidify a plan for conducting it.

[ ] technical hurdle -- clarify mechanics of the transition period from scheme 3 to scheme 7
[ ] clarify number of people
[ ] draft survey and get it approved by IRB

I am closing this issue as we won't be doing a longitudinal study for the time being.


Pagination with offset and limit

I did some research on this issue, so as far as I understand, it's not possible to create pagination with dynamoose.
As an example, I want to use GET /client/items?offset=10&limit=10.
Thank you for the help

@YevheniiHerasymchuk There isn't quite a straight forward way to do this. There are workarounds tho depending on how you structure things.
Of course the limit portion is easy. There is a method for Scan.limit and Query.limit.
In terms of the offset. You are going to need to pass in some form of last key. This is where it gets a little complicated. If you have a system where your primary key's are numbered sequentially 0 or 1 upward you can just pass in the offset as the last key. Problem is that isn't really standard, and not super common. In SQL databases it will happily count up for each row in your tables. But NoSQL is more document storage so it's not totally designed for that as much.
Maybe someone will have some more thoughts on this or a better way to achieve this, but that is the summary of the problem.

Closing this issue due to inactivity.

Sure, I got your point. Thank you


sync to Neo.SmartContract.Framework v3.0.0-CI00300

@chenzhitong @shargon

Duplicate of #43

Duplicate of #43

We can iterate examples if any code style changes but not do anything together before release, it could help developers to know the changes step by step.

Duplicate of #43

We can iterate examples if any code style changes but not do anything together before release, it could help developers to know the changes step by step.

Agree, it's good for me. I'm wirting sc on neo and it makes the example more clear and these methods are all compatible with the latest compiler as what I tested.

The NEP-17 example should inherit Nep17Token.

The NEP-17 example should inherit Nep17Token.
Please update to 3.0.0-rc2
All done.

@erikzhang pls review again.

@shargon pls review again.

@erikzhang Merge?


[Bug] [hazelcast] During the execution of hazelcast, an error has been reported when operating the keyboard Ctrl+c, please handle it gracefully

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened
During the execution of hazelcast, an error has been reported when operating the keyboard Ctrl+c, please handle it gracefully.
SeaTunnel Version
apache-seatunnel-incubating-2.3.1
SeaTunnel Config
env {
  # You can set flink configuration here
  execution.parallelism = 1
  job.mode = "STREAMING"
  #checkpoint.interval = 2000
  #execution.checkpoint.interval = 10000
  #execution.checkpoint.data-uri = "hdfs://localhost:9000/checkpoint"
}

source {
  # This is a example source plugin **only for test and demonstrate the feature source plugin**
  FakeSource {
    parallelism = 2
    result_table_name = "fake"
    row.num = 2000
    schema = {
      fields {
        name = "string"
        age = "int"
      }
    }
  }

  # If you would like to get more information about how to configure Seatunnel and see full list of source plugins,
  # please go to https://seatunnel.apache.org/docs/category/source-v2
}

sink {
  Console {
  }

  # If you would like to get more information about how to configure Seatunnel and see full list of sink plugins,
  # please go to https://seatunnel.apache.org/docs/category/sink-v2
}

Running Command
apache-seatunnel-incubating-2.3.1$ ./bin/seatunnel.sh --config config/v2.streaming.conf.template -e local

Error Exception
^C2023-06-09 20:12:29,554 INFO  com.hazelcast.instance.impl.Node - [localhost]:5801 [seatunnel-117476] [5.1] Running shutdown hook... Current state: ACTIVE
2023-06-09 20:12:29,554 INFO  org.apache.seatunnel.core.starter.seatunnel.command.ClientExecuteCommand - run shutdown hook because get close signal
2023-06-09 20:12:29,554 WARN  org.apache.seatunnel.core.starter.seatunnel.command.ClientExecuteCommand - Task will be closed due to client shutdown.
2023-06-09 20:12:29,555 INFO  com.hazelcast.core.LifecycleService - [localhost]:5801 [seatunnel-117476] [5.1] [localhost]:5801 is SHUTTING_DOWN
2023-06-09 20:12:29,557 WARN  com.hazelcast.instance.impl.Node - [localhost]:5801 [seatunnel-117476] [5.1] Terminating forcefully...
2023-06-09 20:12:29,557 INFO  com.hazelcast.instance.impl.Node - [localhost]:5801 [seatunnel-117476] [5.1] Shutting down connection manager...
2023-06-09 20:12:29,558 INFO  org.apache.seatunnel.engine.server.dag.physical.PhysicalPlan - Job SeaTunnel_Job<PHONE_NUMBER>11323905) turn from state RUNNING to CANCELLING.
2023-06-09 20:12:29,558 INFO  com.hazelcast.internal.server.tcp.TcpServerConnection - [localhost]:5801 [seatunnel-117476] [5.1] Connection[id=1, /<IP_ADDRESS>:5801->/<IP_ADDRESS>:37131, qualifier=null, endpoint=[<IP_ADDRESS>]:37131, remoteUuid=20b90a13-d9a3-4360-a0f5-acb6da8f0fc2, alive=false, connectionType=JVM, planeIndex=-1] closed. Reason: TcpServer is stopping
2023-06-09 20:12:29,560 INFO  com.hazelcast.client.impl.connection.tcp.TcpClientConnection - hz.client_1 [seatunnel-117476] [5.1] ClientConnection{alive=false, connectionId=1, channel=NioChannel{/<IP_ADDRESS>:37131->localhost/<IP_ADDRESS>:5801}, remoteAddress=[localhost]:5801, lastReadTime=2023-06-09 20:12:26.756, lastWriteTime=2023-06-09 20:12:29.555, closedTime=2023-06-09 20:12:29.559, connected server version=5.1} closed. Reason: Connection closed by the other side
2023-06-09 20:12:29,561 INFO  com.hazelcast.client.impl.connection.ClientConnectionManager - hz.client_1 [seatunnel-117476] [5.1] Removed connection to endpoint: [localhost]:5801:75173497-1595-41a7-828a-b9a92cdbb9d2, connection: ClientConnection{alive=false, connectionId=1, channel=NioChannel{/<IP_ADDRESS>:37131->localhost/<IP_ADDRESS>:5801}, remoteAddress=[localhost]:5801, lastReadTime=2023-06-09 20:12:26.756, lastWriteTime=2023-06-09 20:12:29.555, closedTime=2023-06-09 20:12:29.559, connected server version=5.1}
2023-06-09 20:12:29,561 INFO  com.hazelcast.core.LifecycleService - hz.client_1 [seatunnel-117476] [5.1] HazelcastClient 5.1 (20220228 - 21f20e7) is CLIENT_DISCONNECTED
2023-06-09 20:12:29,562 INFO  com.hazelcast.client.impl.connection.ClientConnectionManager - hz.client_1 [seatunnel-117476] [5.1] Trying to connect to cluster: seatunnel-117476
2023-06-09 20:12:29,562 INFO  com.hazelcast.client.impl.connection.ClientConnectionManager - hz.client_1 [seatunnel-117476] [5.1] Trying to connect to Member [localhost]:5801 - 75173497-1595-41a7-828a-b9a92cdbb9d2
2023-06-09 20:12:29,562 INFO  com.hazelcast.instance.impl.Node - [localhost]:5801 [seatunnel-117476] [5.1] Shutting down node engine...
2023-06-09 20:12:29,563 WARN  com.hazelcast.client.impl.connection.ClientConnectionManager - hz.client_1 [seatunnel-117476] [5.1] Exception during initial connection to Member [localhost]:5801 - 75173497-1595-41a7-828a-b9a92cdbb9d2: com.hazelcast.core.HazelcastException: java.io.IOException: Connection refused to address localhost/<IP_ADDRESS>:5801
2023-06-09 20:12:29,564 WARN  com.hazelcast.client.impl.connection.ClientConnectionManager - hz.client_1 [seatunnel-117476] [5.1] Unable to get live cluster connection, retry in 1000 ms, attempt: 1, cluster connect timeout: 3000 ms, max backoff: 30000 ms
2023-06-09 20:12:29,576 WARN  org.apache.seatunnel.engine.server.TaskExecutionService - [localhost]:5801 [seatunnel-117476] [5.1] Interrupted task 40000 - org.apache.seatunnel.engine.server.task.SourceSeaTunnelTask@1f63548f
2023-06-09 20:12:29,576 WARN  org.apache.seatunnel.engine.server.TaskExecutionService - [localhost]:5801 [seatunnel-117476] [5.1] Interrupted task 40001 - org.apache.seatunnel.engine.server.task.SourceSeaTunnelTask@3a32440f
2023-06-09 20:12:29,576 WARN  org.apache.seatunnel.engine.server.TaskExecutionService - [localhost]:5801 [seatunnel-117476] [5.1] Interrupted task 20000 - org.apache.seatunnel.engine.server.task.SourceSplitEnumeratorTask@c275b79
2023-06-09 20:12:29,576 INFO  org.apache.seatunnel.engine.server.TaskExecutionService - [localhost]:5801 [seatunnel-117476] [5.1] taskDone, taskId = 20000, taskGroup = TaskGroupLocation{jobId=719524197411323905, pipelineId=1, taskGroupId=1}
2023-06-09 20:12:29,576 INFO  org.apache.seatunnel.engine.server.TaskExecutionService - [localhost]:5801 [seatunnel-117476] [5.1] taskDone, taskId = 40001, taskGroup = TaskGroupLocation{jobId=719524197411323905, pipelineId=1, taskGroupId=30001}
2023-06-09 20:12:29,576 INFO  org.apache.seatunnel.engine.server.TaskExecutionService - [localhost]:5801 [seatunnel-117476] [5.1] taskDone, taskId = 40000, taskGroup = TaskGroupLocation{jobId=719524197411323905, pipelineId=1, taskGroupId=30000}
2023-06-09 20:12:29,577 INFO  org.apache.seatunnel.engine.server.TaskExecutionService - [localhost]:5801 [seatunnel-117476] [5.1] Task TaskGroupLocation{jobId=719524197411323905, pipelineId=1, taskGroupId=1} complete with state FAILED
2023-06-09 20:12:29,576 WARN  org.apache.seatunnel.engine.server.TaskExecutionService - [localhost]:5801 [seatunnel-117476] [5.1] Interrupted task 50001 - org.apache.seatunnel.engine.server.task.TransformSeaTunnelTask@51d89cda
2023-06-09 20:12:29,576 WARN  org.apache.seatunnel.engine.server.TaskExecutionService - [localhost]:5801 [seatunnel-117476] [5.1] Interrupted task 50000 - org.apache.seatunnel.engine.server.task.TransformSeaTunnelTask@4e368447
2023-06-09 20:12:29,585 INFO  org.apache.seatunnel.engine.server.TaskExecutionService - [localhost]:5801 [seatunnel-117476] [5.1] taskDone, taskId = 50001, taskGroup = TaskGroupLocation{jobId=719524197411323905, pipelineId=1, taskGroupId=30001}
2023-06-09 20:12:29,585 INFO  org.apache.seatunnel.engine.server.TaskExecutionService - [localhost]:5801 [seatunnel-117476] [5.1] taskDone, taskId = 50000, taskGroup = TaskGroupLocation{jobId=719524197411323905, pipelineId=1, taskGroupId=30000}
2023-06-09 20:12:29,586 INFO  org.apache.seatunnel.engine.server.TaskExecutionService - [localhost]:5801 [seatunnel-117476] [5.1] Task TaskGroupLocation{jobId=719524197411323905, pipelineId=1, taskGroupId=30001} complete with state FAILED
2023-06-09 20:12:29,586 INFO  org.apache.seatunnel.engine.server.TaskExecutionService - [localhost]:5801 [seatunnel-117476] [5.1] Task TaskGroupLocation{jobId=719524197411323905, pipelineId=1, taskGroupId=30000} complete with state FAILED
2023-06-09 20:12:29,609 INFO  com.hazelcast.instance.impl.NodeExtension - [localhost]:5801 [seatunnel-117476] [5.1] Destroying node NodeExtension.
2023-06-09 20:12:29,609 INFO  com.hazelcast.instance.impl.Node - [localhost]:5801 [seatunnel-117476] [5.1] Hazelcast Shutdown is completed in 52 ms.
2023-06-09 20:12:29,610 INFO  com.hazelcast.core.LifecycleService - [localhost]:5801 [seatunnel-117476] [5.1] [localhost]:5801 is SHUTDOWN
2023-06-09 20:12:29,739 WARN  com.hazelcast.client.impl.connection.ClientConnectionManager - hz.client_1 [seatunnel-117476] [5.1] Could not connect to member 75173497-1595-41a7-828a-b9a92cdbb9d2, reason com.hazelcast.core.HazelcastException: java.io.IOException: Connection refused to address localhost/<IP_ADDRESS>:5801
2023-06-09 20:12:30,564 INFO  com.hazelcast.client.impl.connection.ClientConnectionManager - hz.client_1 [seatunnel-117476] [5.1] Trying to connect to Member [localhost]:5801 - 75173497-1595-41a7-828a-b9a92cdbb9d2
2023-06-09 20:12:30,565 WARN  com.hazelcast.client.impl.connection.ClientConnectionManager - hz.client_1 [seatunnel-117476] [5.1] Exception during initial connection to Member [localhost]:5801 - 75173497-1595-41a7-828a-b9a92cdbb9d2: com.hazelcast.core.HazelcastException: java.io.IOException: Connection refused to address localhost/<IP_ADDRESS>:5801
2023-06-09 20:12:30,565 WARN  com.hazelcast.client.impl.connection.ClientConnectionManager - hz.client_1 [seatunnel-117476] [5.1] Unable to get live cluster connection, retry in 1050 ms, attempt: 2, cluster connect timeout: 3000 ms, max backoff: 30000 ms
2023-06-09 20:12:30,740 WARN  com.hazelcast.client.impl.connection.ClientConnectionManager - hz.client_1 [seatunnel-117476] [5.1] Could not connect to member 75173497-1595-41a7-828a-b9a92cdbb9d2, reason com.hazelcast.core.HazelcastException: java.io.IOException: Connection refused to address localhost/<IP_ADDRESS>:5801
2023-06-09 20:12:31,615 INFO  com.hazelcast.client.impl.connection.ClientConnectionManager - hz.client_1 [seatunnel-117476] [5.1] Trying to connect to Member [localhost]:5801 - 75173497-1595-41a7-828a-b9a92cdbb9d2
2023-06-09 20:12:31,616 WARN  com.hazelcast.client.impl.connection.ClientConnectionManager - hz.client_1 [seatunnel-117476] [5.1] Exception during initial connection to Member [localhost]:5801 - 75173497-1595-41a7-828a-b9a92cdbb9d2: com.hazelcast.core.HazelcastException: java.io.IOException: Connection refused to address localhost/<IP_ADDRESS>:5801
2023-06-09 20:12:31,616 WARN  com.hazelcast.client.impl.connection.ClientConnectionManager - hz.client_1 [seatunnel-117476] [5.1] Unable to get live cluster connection, retry in 946 ms, attempt: 3, cluster connect timeout: 3000 ms, max backoff: 30000 ms
2023-06-09 20:12:31,740 WARN  com.hazelcast.client.impl.connection.ClientConnectionManager - hz.client_1 [seatunnel-117476] [5.1] Could not connect to member 75173497-1595-41a7-828a-b9a92cdbb9d2, reason com.hazelcast.core.HazelcastException: java.io.IOException: Connection refused to address localhost/<IP_ADDRESS>:5801
2023-06-09 20:12:32,562 INFO  com.hazelcast.client.impl.connection.ClientConnectionManager - hz.client_1 [seatunnel-117476] [5.1] Trying to connect to Member [localhost]:5801 - 75173497-1595-41a7-828a-b9a92cdbb9d2
2023-06-09 20:12:32,563 WARN  com.hazelcast.client.impl.connection.ClientConnectionManager - hz.client_1 [seatunnel-117476] [5.1] Exception during initial connection to Member [localhost]:5801 - 75173497-1595-41a7-828a-b9a92cdbb9d2: com.hazelcast.core.HazelcastException: java.io.IOException: Connection refused to address localhost/<IP_ADDRESS>:5801
2023-06-09 20:12:32,563 WARN  com.hazelcast.client.impl.connection.ClientConnectionManager - hz.client_1 [seatunnel-117476] [5.1] Unable to get live cluster connection, cluster connect timeout (3000 ms) is reached. Attempt 4.
2023-06-09 20:12:32,563 INFO  com.hazelcast.client.impl.connection.ClientConnectionManager - hz.client_1 [seatunnel-117476] [5.1] Unable to connect to any address from the cluster with name: seatunnel-117476. The following addresses were tried: [[localhost]:5801]
2023-06-09 20:12:32,563 WARN  com.hazelcast.client.impl.connection.ClientConnectionManager - hz.client_1 [seatunnel-117476] [5.1] Could not connect to any cluster, shutting down the client: Unable to connect to any cluster.
2023-06-09 20:12:32,564 INFO  com.hazelcast.core.LifecycleService - hz.client_1 [seatunnel-117476] [5.1] HazelcastClient 5.1 (20220228 - 21f20e7) is SHUTTING_DOWN
2023-06-09 20:12:32,596 INFO  org.apache.seatunnel.engine.client.job.ClientJobProxy - Job<PHONE_NUMBER>11323905) end with unknown state, and throw Exception: java.util.concurrent.ExecutionException: com.hazelcast.client.HazelcastClientNotActiveException: Client is shutting down
        at java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:357)
        at java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1908)
        at org.apache.seatunnel.engine.client.job.ClientJobProxy.lambda$waitForJobComplete$0(ClientJobProxy.java:97)
        at org.apache.seatunnel.common.utils.RetryUtils.retryWithException(RetryUtils.java:48)
        at org.apache.seatunnel.engine.client.job.ClientJobProxy.waitForJobComplete(ClientJobProxy.java:93)
        at org.apache.seatunnel.core.starter.seatunnel.command.ClientExecuteCommand.execute(ClientExecuteCommand.java:174)
        at org.apache.seatunnel.core.starter.SeaTunnel.run(SeaTunnel.java:40)
        at org.apache.seatunnel.core.starter.seatunnel.SeaTunnelClient.main(SeaTunnelClient.java:34)
Caused by: com.hazelcast.client.HazelcastClientNotActiveException: Client is shutting down
        at com.hazelcast.client.impl.spi.impl.ClientInvocation.notifyExceptionWithOwnedPermission(ClientInvocation.java:316)
        at com.hazelcast.client.impl.spi.impl.ClientInvocation.invokeOnSelection(ClientInvocation.java:209)
        at com.hazelcast.client.impl.spi.impl.ClientInvocation.retry(ClientInvocation.java:235)
        at com.hazelcast.client.impl.spi.impl.ClientInvocation.run(ClientInvocation.java:216)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at java.lang.Thread.run(Thread.java:750)
        at com.hazelcast.internal.util.executor.HazelcastManagedThread.executeRun(HazelcastManagedThread.java:76)
        at com.hazelcast.internal.util.executor.HazelcastManagedThread.run(HazelcastManagedThread.java:102)
Caused by: java.io.IOException: No connection found to cluster.
        at com.hazelcast.client.impl.connection.tcp.TcpClientConnectionManager.checkInvocationAllowed(TcpClientConnectionManager.java:548)
        at com.hazelcast.client.impl.spi.impl.ClientInvocationServiceImpl.checkInvocationAllowed(ClientInvocationServiceImpl.java:294)
        at com.hazelcast.client.impl.spi.impl.ClientInvocation.invokeOnSelection(ClientInvocation.java:178)
        ... 11 more

2023-06-09 20:12:32,597 INFO  com.hazelcast.core.LifecycleService - hz.client_1 [seatunnel-117476] [5.1] HazelcastClient 5.1 (20220228 - 21f20e7) is SHUTDOWN
2023-06-09 20:12:32,597 INFO  org.apache.seatunnel.core.starter.seatunnel.command.ClientExecuteCommand - Closed SeaTunnel client......
2023-06-09 20:12:32,598 INFO  org.apache.seatunnel.core.starter.seatunnel.command.ClientExecuteCommand - Closed HazelcastInstance ......
2023-06-09 20:12:32,598 INFO  org.apache.seatunnel.core.starter.seatunnel.command.ClientExecuteCommand - Closed metrics executor service ......
2023-06-09 20:12:32,598 ERROR org.apache.seatunnel.core.starter.SeaTunnel -

===============================================================================

2023-06-09 20:12:32,598 ERROR org.apache.seatunnel.core.starter.SeaTunnel - Fatal Error,

2023-06-09 20:12:32,598 ERROR org.apache.seatunnel.core.starter.SeaTunnel - Please submit bug report in https://github.com/apache/incubator-seatunnel/issues

2023-06-09 20:12:32,598 ERROR org.apache.seatunnel.core.starter.SeaTunnel - Reason:SeaTunnel job executed failed

2023-06-09 20:12:32,599 ERROR org.apache.seatunnel.core.starter.SeaTunnel - Exception StackTrace:org.apache.seatunnel.core.starter.exception.CommandExecuteException: SeaTunnel job executed failed
        at org.apache.seatunnel.core.starter.seatunnel.command.ClientExecuteCommand.execute(ClientExecuteCommand.java:181)
        at org.apache.seatunnel.core.starter.SeaTunnel.run(SeaTunnel.java:40)
        at org.apache.seatunnel.core.starter.seatunnel.SeaTunnelClient.main(SeaTunnelClient.java:34)
Caused by: java.lang.RuntimeException: java.util.concurrent.ExecutionException: com.hazelcast.client.HazelcastClientNotActiveException: Client is shutting down
        at org.apache.seatunnel.engine.client.job.ClientJobProxy.waitForJobComplete(ClientJobProxy.java:114)
        at org.apache.seatunnel.core.starter.seatunnel.command.ClientExecuteCommand.execute(ClientExecuteCommand.java:174)
        ... 2 more
Caused by: java.util.concurrent.ExecutionException: com.hazelcast.client.HazelcastClientNotActiveException: Client is shutting down
        at java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:357)
        at java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1908)
        at org.apache.seatunnel.engine.client.job.ClientJobProxy.lambda$waitForJobComplete$0(ClientJobProxy.java:97)
        at org.apache.seatunnel.common.utils.RetryUtils.retryWithException(RetryUtils.java:48)
        at org.apache.seatunnel.engine.client.job.ClientJobProxy.waitForJobComplete(ClientJobProxy.java:93)
        ... 3 more
Caused by: com.hazelcast.client.HazelcastClientNotActiveException: Client is shutting down
        at com.hazelcast.client.impl.spi.impl.ClientInvocation.notifyExceptionWithOwnedPermission(ClientInvocation.java:316)
        at com.hazelcast.client.impl.spi.impl.ClientInvocation.invokeOnSelection(ClientInvocation.java:209)
        at com.hazelcast.client.impl.spi.impl.ClientInvocation.retry(ClientInvocation.java:235)
        at com.hazelcast.client.impl.spi.impl.ClientInvocation.run(ClientInvocation.java:216)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at java.lang.Thread.run(Thread.java:750)
        at com.hazelcast.internal.util.executor.HazelcastManagedThread.executeRun(HazelcastManagedThread.java:76)
        at com.hazelcast.internal.util.executor.HazelcastManagedThread.run(HazelcastManagedThread.java:102)
Caused by: java.io.IOException: No connection found to cluster.
        at com.hazelcast.client.impl.connection.tcp.TcpClientConnectionManager.checkInvocationAllowed(TcpClientConnectionManager.java:548)
        at com.hazelcast.client.impl.spi.impl.ClientInvocationServiceImpl.checkInvocationAllowed(ClientInvocationServiceImpl.java:294)
        at com.hazelcast.client.impl.spi.impl.ClientInvocation.invokeOnSelection(ClientInvocation.java:178)
        ... 11 more

2023-06-09 20:12:32,599 ERROR org.apache.seatunnel.core.starter.SeaTunnel -
===============================================================================

Exception in thread "main" org.apache.seatunnel.core.starter.exception.CommandExecuteException: SeaTunnel job executed failed
        at org.apache.seatunnel.core.starter.seatunnel.command.ClientExecuteCommand.execute(ClientExecuteCommand.java:181)
        at org.apache.seatunnel.core.starter.SeaTunnel.run(SeaTunnel.java:40)
        at org.apache.seatunnel.core.starter.seatunnel.SeaTunnelClient.main(SeaTunnelClient.java:34)
Caused by: java.lang.RuntimeException: java.util.concurrent.ExecutionException: com.hazelcast.client.HazelcastClientNotActiveException: Client is shutting down
        at org.apache.seatunnel.engine.client.job.ClientJobProxy.waitForJobComplete(ClientJobProxy.java:114)
        at org.apache.seatunnel.core.starter.seatunnel.command.ClientExecuteCommand.execute(ClientExecuteCommand.java:174)
        ... 2 more
Caused by: java.util.concurrent.ExecutionException: com.hazelcast.client.HazelcastClientNotActiveException: Client is shutting down
        at java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:357)
        at java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1908)
        at org.apache.seatunnel.engine.client.job.ClientJobProxy.lambda$waitForJobComplete$0(ClientJobProxy.java:97)
        at org.apache.seatunnel.common.utils.RetryUtils.retryWithException(RetryUtils.java:48)
        at org.apache.seatunnel.engine.client.job.ClientJobProxy.waitForJobComplete(ClientJobProxy.java:93)
        ... 3 more
Caused by: com.hazelcast.client.HazelcastClientNotActiveException: Client is shutting down
        at com.hazelcast.client.impl.spi.impl.ClientInvocation.notifyExceptionWithOwnedPermission(ClientInvocation.java:316)
        at com.hazelcast.client.impl.spi.impl.ClientInvocation.invokeOnSelection(ClientInvocation.java:209)
        at com.hazelcast.client.impl.spi.impl.ClientInvocation.retry(ClientInvocation.java:235)
        at com.hazelcast.client.impl.spi.impl.ClientInvocation.run(ClientInvocation.java:216)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at java.lang.Thread.run(Thread.java:750)
        at com.hazelcast.internal.util.executor.HazelcastManagedThread.executeRun(HazelcastManagedThread.java:76)
        at com.hazelcast.internal.util.executor.HazelcastManagedThread.run(HazelcastManagedThread.java:102)
Caused by: java.io.IOException: No connection found to cluster.
        at com.hazelcast.client.impl.connection.tcp.TcpClientConnectionManager.checkInvocationAllowed(TcpClientConnectionManager.java:548)
        at com.hazelcast.client.impl.spi.impl.ClientInvocationServiceImpl.checkInvocationAllowed(ClientInvocationServiceImpl.java:294)
        at com.hazelcast.client.impl.spi.impl.ClientInvocation.invokeOnSelection(ClientInvocation.java:178)
        ... 11 more
2023-06-09 20:12:32,595 ERROR org.apache.seatunnel.core.starter.seatunnel.command.ClientExecuteCommand - Cancel job failed.
java.util.concurrent.ExecutionException: com.hazelcast.client.HazelcastClientNotActiveException: Client is shutting down
        at java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:357) ~[?:1.8.0_362]
        at java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1928) ~[?:1.8.0_362]
        at org.apache.seatunnel.core.starter.seatunnel.command.ClientExecuteCommand.lambda$execute$1(ClientExecuteCommand.java:154) ~[seatunnel-starter.jar:2.3.1]
        at java.lang.Thread.run(Thread.java:750) [?:1.8.0_362]
Caused by: com.hazelcast.client.HazelcastClientNotActiveException: Client is shutting down
        at com.hazelcast.client.impl.spi.impl.ClientInvocation.notifyExceptionWithOwnedPermission(ClientInvocation.java:316) ~[seatunnel-starter.jar:2.3.1]
        at com.hazelcast.client.impl.spi.impl.ClientInvocation.invokeOnSelection(ClientInvocation.java:209) ~[seatunnel-starter.jar:2.3.1]
        at com.hazelcast.client.impl.spi.impl.ClientInvocation.retry(ClientInvocation.java:235) ~[seatunnel-starter.jar:2.3.1]
        at com.hazelcast.client.impl.spi.impl.ClientInvocation.run(ClientInvocation.java:216) ~[seatunnel-starter.jar:2.3.1]
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) ~[?:1.8.0_362]
        at java.util.concurrent.FutureTask.run(FutureTask.java:266) ~[?:1.8.0_362]
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) ~[?:1.8.0_362]
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) ~[?:1.8.0_362]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) ~[?:1.8.0_362]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) ~[?:1.8.0_362]
        at java.lang.Thread.run(Thread.java:750) ~[?:1.8.0_362]
        at com.hazelcast.internal.util.executor.HazelcastManagedThread.executeRun(HazelcastManagedThread.java:76) ~[seatunnel-starter.jar:2.3.1]
        at com.hazelcast.internal.util.executor.HazelcastManagedThread.run(HazelcastManagedThread.java:102) ~[seatunnel-starter.jar:2.3.1]
Caused by: java.io.IOException: No connection found to cluster.
        at com.hazelcast.client.impl.connection.tcp.TcpClientConnectionManager.checkInvocationAllowed(TcpClientConnectionManager.java:548) ~[seatunnel-starter.jar:2.3.1]
        at com.hazelcast.client.impl.spi.impl.ClientInvocationServiceImpl.checkInvocationAllowed(ClientInvocationServiceImpl.java:294) ~[seatunnel-starter.jar:2.3.1]
        at com.hazelcast.client.impl.spi.impl.ClientInvocation.invokeOnSelection(ClientInvocation.java:178) ~[seatunnel-starter.jar:2.3.1]
        at com.hazelcast.client.impl.spi.impl.ClientInvocation.retry(ClientInvocation.java:235) ~[seatunnel-starter.jar:2.3.1]
        at com.hazelcast.client.impl.spi.impl.ClientInvocation.run(ClientInvocation.java:216) ~[seatunnel-starter.jar:2.3.1]
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) ~[?:1.8.0_362]
        at java.util.concurrent.FutureTask.run(FutureTask.java:266) ~[?:1.8.0_362]
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) ~[?:1.8.0_362]
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) ~[?:1.8.0_362]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) ~[?:1.8.0_362]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) ~[?:1.8.0_362]
        at java.lang.Thread.run(Thread.java:750) ~[?:1.8.0_362]
        at com.hazelcast.internal.util.executor.HazelcastManagedThread.executeRun(HazelcastManagedThread.java:76) ~[seatunnel-starter.jar:2.3.1]
        at com.hazelcast.internal.util.executor.HazelcastManagedThread.run(HazelcastManagedThread.java:102) ~[seatunnel-starter.jar:2.3.1]
wangdachui@007-NC01:~/apache-seatunnel-incubating-2.3.1$ cat config/v2.streaming.conf.template

Flink or Spark Version
no
Java or Scala Version
no
Screenshots
No response
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

This exception is normal because it is a streaming task. Do you have any suggestions?

At the end of pressing Ctrl+c, there are too many Java stack error messages, thinking that an error was encountered during deactivation, and it is recommended to print a more elegant stop log.

At the end of pressing Ctrl+c, there are too many Java stack error messages, thinking that an error was encountered during deactivation, and it is recommended to print a more elegant stop log.

Great suggestion. Can you provide a pr to fix this?


Unit tests for LLP/BaseAddress

Added unit tests for LLP/BaseAddress which covers some of the functionality of the class (not all yet) Some of the tests currently fail because of a bug in IsIPV4() and IsLocal()

@beuschl little pedantic formatting things, just for consistency with the rest of the codebase. Can you use parenthesis when initializing objects i.e. LLP::BaseAddress addr(ip); we usually use brackets only for static initializer lists when in the constructor

Thank you for the Pull Request! Merged!


Missing deye_2mppt.yaml

Hi,
i miss the file deye_2mppt.yaml. I have version 1.4.3. Installed and reloaded a few times. It's still missing, but it's in the repository.

I added the entry to the /solarman/const file and copied the deye_2mppt.yaml file as well. I was able to select the file now, but I don't get any readings. The status is N/A and Disconnected.
Could something else be missing? Another entry somewhere?

Great, Thanks for letting me know. :)

This happened to me too, fresh install of homeassistant,
i will add i manually, just wanted you to know it's happening.


Calyptia-fluentd with Ruby 3

Hello,
Would be possible to make this module compliant with calyptia-fluentd as refered here ?
https://docs.fluentd.org/installation/install-by-rpm
We have some trouble with fluent-plugin-amqp2 : last versions are built for Ruby 3.x, and basically Ruby 2.7 is still the one embedded with td-agent, which can causes build problems during plugins install.
Thank you!
Regards,

@NapoSky I don't have a problem with this, would you be interested in putting together the PR to support this install method?
I believe you would want to modify fluentd::repo here: https://github.com/EncoreTechnologies/puppet-fluentd/blob/master/manifests/repo.pp
Thanks,
Nick


Add a feature to toggle direct display of file's checksum if checksum files exist

Greetings,
Thanks for the great work on Bootstrap-Listr
I would like to add an option to allow direct display of checksum string in table if checksum file exists
Set process_checksum to true to enable
Also modify checksum_files to include any other checksum file extension names
the logic is simple - if this feature is enabled, matching checksum files will not be added into file list but its content will be read out and append to the master file info
when constructing html table, check and append to table entry
the checksum string contains href tag to original checksum file for downloading
Screenshot - http://imgur.com/I8A7zOW
Please take a look if you are interested
Thx

First of all thank you for the pull request, sounds like a good idea. I haven't worked on this for some time, but hope to be able to pick up again early next year. The plan is to release one last 2.x version to pave the way for the transition to 3.x. That means I will mostly remove code, rather than add new something. I will gladly merge your code when I'm starting to work on 3.x. I hope your fork serves you well until then!

I grabbed the new dev branch with this in it, but how exactly does it work? I have it enabled in the config file, but not sure how to get it display the checksum. I ran md5sum filename > outfile but nothing shows up in the directory listing except the outfile.

The md5 checksum file shall be generated with name 'filename.md5sum' in this case, if related codes haven't been changed since this merge. 'sha1sum' for sha1.
Also, need to add 'md5sum' in config.json like this-
"checksum_files": [
"sha1sum",
"md5sum"
],

@momogentoo That worked! Thanks :)


Pick a reasonable default for number of threads

stack2nix is quite IO bound, but we could use threads to parallelize it and we'd have to come up with a good default, since specifying -j X it tedious.

Happy with https://github.com/input-output-hk/stack2nix/pull/44 for now.


Cover Art from Bluetooth?

Is there a way to get the images for the cover art from the sink? I see in the espressif docs there's flags like ESP_AVRC_FEAT_FLAG_COVER_ART_GET_IMAGE and another one ESP_AVRC_FEAT_FLAG_COVER_ART_GET_LINKED_THUMBNAIL. If I could pluck these out to get the images in the same way you can grab the title and artist it'd take my project to the next level.

https://github.com/pschatzmann/ESP32-A2DP#support
I don't understand why you report this as a bug.
This is clearly not supported by my library!
If you double check the IDF documentation you will also not find any method that would support the esp_avrc_feature_flag_t enum.


Pass the feature's name to a step

Hi @l3pp4rd!
Is there a way to pass the current scenario/feature definition to a step? I would like to log each HTTP requests that we send to our API and I need to attach the current feature name and scenario name. I was thinking to use the hooks somehow but I think if I run the tests parallel that couldn't work.

Hi, yes currently when parallel it will not work, I'm planning to at some point change the gherkin so that each node could have a parent node. that would be a good solution to many cases we have

Thanks for this quick answer. May I know approximately when do you plan to do it, in weeks or in months or in the far future? :)

I cannot know that, since this project is not related to my daily work. if that is important for you, you can run through the gherkin package and make the change in PR. I think, that can be accepted since that is useful for many parts of code.


Implement short code support

This PR is not intended to be approved in its current state. It is neither complete, nor clean. Just looking for feedback on how to move forward.

I'd love to have this functionality as well, is there any way I can help move this along?


Imprecise basis merging for nonfix declarations

test/fail/basis-merging-nonfix.mlb should fail, but currently it succeeds without error.
The problem: nonfix declarations should override previous infix declarations when merging bases. Currently, they do not.
Suggested solution: while parsing SML source, keep two separate InfixDicts around: one for infix declarations, and one for nonfix declarations. They can cancel each other out when there is any overlap. This allows us to cancel infix/nonfix across source files, as needed for the above test.

Thinking about this some more:

I don't think this example should fail to parse. It will fail to type-check, though (similar to as discussed in #6)
The suggested solution is messy. Much better is to map each identifier to one of Infix or Nonfix, depending on how it's been set.
Is there a good example to demonstrate this? Or does it really not matter?

Update: I got rid of that test case. Still trying to think of a good example where this issue actually causes a problem.


ng-form support

Any chance you could support ng-form directive instead of requriing the form tag?

+1

@sagimann Can you post how you were using the ng-form?   I'm trying to use the code above but I don't think I using the editable with  ng-form correctly.  I'm not able to submit the form.


fix: Throw error on trying to access non-existent unpublished action

Fixes #11751
Type of change

Bug fix (non-breaking change which fixes an issue)

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes

Few things we might want to think about:

Should we add similar check in other action related flows as well - update, rename, copy, move etc.
Should we add a JUnit TC for this ? If it is difficult due to the nature of code flow, we may as well skip it for now.

/ok-to-test sha=fb95b34

Merging since all tests have passed and test result is not updating.


Steam VR Issue with Button Alias Configuration

Using Version 3.1.0 from the Asset store, The same type of configuration worked as expected in version 3.0.1
Unity 5.5.1f1
Vive hardware
SteamVR Version 1.2.0
Steps to reproduce
Start with Scene: 036_Controller_CustomCompoundPointer
Under VRTK->RightController->VRTK_ControllerEvents
change Pointer Toggle Press from TouchPad_Press to Button_One_Press
change Pointer Set Button from TouchPad_Press to Button_One_Press
Under VRTK->RightController->VRTK_Pointer
Change Activation Button to Button_One_Press
Change Selection Button to Button_One_Press
(having to change both of these seems redundant, I've tried changing both individually, with no success, and only list it here to cover everything.)
Expected behavior
Using the Application Button should now teleport
Current behavior
Changing Only  VRTK->RightController->VRTK_ControllerEvents
Doesn't affect what button the action is bound to.
Changing  VRTK->RightController->VRTK_Pointer
makes it so the Bezier teleport no longer functions at all.

The controller button aliases have now been deprecated. If you use Github master version then this will no longer be an issue.

Issue resolved. As a side note I should of been using button two above, not button one, that's just here for anyone else that reads this issue later.

Thanks for the quick response btw


Send Broacast List and Status not working

Describe the bug
I'm trying to simulate broadcast submissions as documented but without success
To Reproduce
-- trying to update status:

await waSocketService.sock.sendMessage(
    'status@broadcast',
    { text: 'This is a test' }, {
    backgroundColor: '#315575',
    font: 3,
    statusJidList<EMAIL_ADDRESS>    broadcast: true });

-- trying to send to broadcast list(it was created on the device):

await waSocketService.sock.sendMessage('{timestamp}@broadcast',
                { text: 'hello world' }, { broadcast: true });

I did my tests based on this example in the documentation:
sock.sendMessage(jid, {image: {url: url}, caption: caption}, {backgroundColor : backgroundColor, font : font, statusJidList: statusJidList, broadcast : true})

Is the feature actually broken or am I implementing something wrong?

Is the feature actually broken or am I implementing something wrong?

Everything is fine, just little thing is messed

you must need to put your own jid in statusJidList

let users_Jid = [user1,user2,user3,...]           // Jids for Users to Send your status
let Bot_Jid = conn.decodJid(conn.user.id)       // Get Jid for Bot Number

statusJidList: [ Bot_Jid ,  ...users_Jid ],  // Must need to put "Bot_Jid" in array, OtherWise you can't see your status

status'll be updated but you can't see it, If Bot_Number_Jid is not Present in statusJidList

HOPE IT'LL HELP!

@SuhailTechInfo Thanks !!
You're right, I actually redid the test and the status update worked as expected, but what about sending it to the broadcast list, is there also something I did wrong?

what about sending it to the broadcast list, is there also something I did wrong?

Basicaly Theres no option to get directly broadcast list
You Can store USers Jid By Following Steps:

You can get Contact List Using Store

global.users = Object.keys ( store.contacts || {})  // Getinng Contacts jid into USERS Array

You can Create a an Array to store all message senders jid

if(! global.users )  global.users = []  // Initialize an Array
else {  global.users.push( message.sender )   } // Storing sender jid in USERS Array

AFTER THAT
statusJidList: [ Bot_Jid ,  ...global.users],

@SuhailTechInfo I understood perfectly and I'm grateful for your valuable tips, but I still have problems trying to send messages to a broadcast list, as it is in the resource documentation where it says:
"You can send messages to broadcast lists the same way you send messages to groups & individual chats"
"Right now, WA Web does not support creating broadcast lists, but you can still delete them"
"Broadcast IDs are in the format 12345678@broadcast"
Using status@broadcast is ok for me, I only send it to broadcast lists that aren't.
Does this no longer work for you?

You can fetch the status contacts list via privacy fetch

Will implement

I have same problem, PENDING.

I have same problem

I have same problem

having same issue here


Add void transform that always produces null

This adds a new transform function, void, that always produces a null value. Because void and null are Java keywords, the PartitionSpecBuilder is configured using alwaysNull.
The purpose of this transform is to be a stand-in for partition transforms that are removed from a spec. In the v1 table format, IDs for partition fields are not tracked by PartitionSpec. Instead, they are assigned starting at 1000 for each spec. Because tables may have more than one spec, manifest files could have incompatible partition field structs. This is not a problem for job planning because each manifest is read independently, but it can break metadata tables that show a union of all manifest data files or entries.
The void transform can be used to avoid a problem with ID assignment. If a table has two partition fields, 1000: categorical string, 1001: ts_day int, then removing the categorical partition will create a new partition spec with 1000: ts_day int. That would create a problem in the metadata tables. Instead of deleting the categorical partition, it should be replaced with a void partition to keep the IDs aligned: 1000: always_null string, 1001: ts_day int.

@jun-he, FYI. This is related to #922. Instead of deleting partitions in v1, we can replace them with the void transform.

One minor comment, but +1 (pending checks)


[INF-1599] Enterprise Checks

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


[HDInsight] Add Incoming BREAKING CHANGE for removing default value of --workernode-size and  --headnode-size

Description

Add Incoming BREAKING CHANGE information in advance. In the next CLI version, we will remove the default value of the parameters  --workernode-size and --headnode-size.
Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change.
[Component Name 2] az command b: Add some customer-facing feature.

This checklist is used to make sure that common guidelines for a pull request are followed.

[x] The PR title and description has followed the guideline in Submitting Pull Requests.

[x] I adhere to the Command Guidelines.

[x] I adhere to the Error Handling Guidelines.

HDInsight


Remote desktop bug when using scaling

Describe the bug
When client changes the size of text to 125%, remote desktop won't be able to see all the screen.
To Reproduce
Steps to reproduce the behavior (at client computer)

Right click on desktop
Click on 'Display settings'
Scroll down to 'Scale and layout'
'Change the size of text, apps and other items' -> 125%
See error

Expected behavior
Remote desktop should be able to capture the whole desktop
Screenshots

System

Server OS: Windows 10
Client OS: Windows 10
Server installed .NET Framework version: 4.8
Client installed .NET Framework version: 4.8
Quasar Version: <IP_ADDRESS>
Build configuration: Release

Please use the latest quasar version. Updating is explained here: https://github.com/quasar/Quasar/wiki/Updating-a-Client


basic webpack typescript compile question (ts-loader)

hi there,
i've just recognised that after running npm run dev every change to my src*.js -files will reload the browser correctly with my updated js (thanks to hot module reload i think)
in my workflow my ide (sublime) uses tsc to generate the .js files
thats very cool and nice  but then....
why do we need this in the config:
{ test: /\.ts$/, loader: 'ts-loader' },
is it because other workflows don't compile directly to .ts and then this ts-loader is used on the fly?

Webpack is assuming that you don't have something else doing the transpile. Essentially, webpack is both the build tool and the bundler.


cant create master after update cli: 0.15.0

kontena master digitalocean create
ERROR: No such sub-command 'digitalocean'
kontena digitalocean master create
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:135:in `require': cannot load such file -- kontena/machine/digital_ocean (LoadError)
       	from /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:135:in `rescue in require'
       	from /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:144:in `require'
       	from /Library/Ruby/Gems/2.0.0/gems/kontena-plugin-digitalocean-0.1.0/lib/kontena/plugin/digital_ocean/master/create_command.rb:20:in `execute'
       	from /Library/Ruby/Gems/2.0.0/gems/clamp-1.0.0/lib/clamp/command.rb:68:in `run'
       	from /Library/Ruby/Gems/2.0.0/gems/clamp-1.0.0/lib/clamp/subcommand/execution.rb:11:in `execute'
       	from /Library/Ruby/Gems/2.0.0/gems/clamp-1.0.0/lib/clamp/command.rb:68:in `run'
       	from /Library/Ruby/Gems/2.0.0/gems/clamp-1.0.0/lib/clamp/subcommand/execution.rb:11:in `execute'
       	from /Library/Ruby/Gems/2.0.0/gems/clamp-1.0.0/lib/clamp/command.rb:68:in `run'
       	from /Library/Ruby/Gems/2.0.0/gems/clamp-1.0.0/lib/clamp/subcommand/execution.rb:11:in `execute'
       	from /Library/Ruby/Gems/2.0.0/gems/clamp-1.0.0/lib/clamp/command.rb:68:in `run'
       	from /Library/Ruby/Gems/2.0.0/gems/clamp-1.0.0/lib/clamp/command.rb:133:in `run'
       	from /Library/Ruby/Gems/2.0.0/gems/kontena-cli-0.15.0/bin/kontena:16:in `<top (required)>'
       	from /usr/local/bin/kontena:23:in `load'
       	from /usr/local/bin/kontena:23:in `<main>'

Have you installed digitalocean plugin (kontena plugin install digitalocean)?
Just noticed that you have to execute the command with sudo if using Ruby version shipped with Mac OS.

thank you


Incorrect introspection in outline for headings using weak page breaks

Description
The page numbers reported in the outline of the following code are off by one:
#outline()

#set page(numbering: "I.")
#set heading(numbering: "1.")
#show heading: it => pagebreak(weak: true) + it

= Hello
#lorem(1000)

= World
#lorem(1000)

World is located on page IV.
This was introduced somewhere between a2c98071 and 34990f7f.
Reproduction URL
No response
Operating system
Linux
Typst version

[ ] I am using the latest version of Typst

I used git bisect to find out that the bug was introduced at a52987a8c26bc13e3db4cc300b8cd9d81eb8a18d .

Please reopen this one. My outline is two sites long, and now the outline is off by one again. Using latest version 0.11.1

Could you post an MRE?

Sorry, what do you mean by MRE?

I'm using version 0.11.1.

The open/close status of issues reflects the state of the main branch. Please check if the issue persists if you compile Typst from the main branch.
MRE = Minimum Reproducible Example

I've pinpointed the issue: everything was functioning correctly, but I mistakenly relied on a template, assuming it was properly configured. It turns out the creator began the page numbering at 0 and neglected to add page breaks after the outlines, even though the pages were separated. This led to the problem I encountered, but it’s not related to Typst.
Apologies for any confusion.


Add License

Hi there,
Excellent work with both the Lux AI Challenge and the vizualiser! The project seems really neat. :)
I've noticed that the Lux Design Engine is under an Apache License - but there isn't one here for the vizualiser. Is this under the same license?  If so, it might be useful for people looking to fork and customize the visualizations.
Thanks, in advance.

done :)


Semaphore is not recoginced at parsing point

Semaphroe is not recogniced at parsing in qam gen, need to find a way

Mention/Include in FreeRTOSConfing.h was missing.


Update GHA to use Conda-Incubator

Implements the Conda-Incubator to GitHub Actions instead of old
activate script. Removes the older helper scripts.
Partial resolution to #409

LGTM.
I think we can also get rid of devtools/{travis-ci,appveyor}, as well as there corresponding yml files at the repo root.

I don't want to drop the other tools yet until we are certain we've pulled what we need from them for the documentation compile and upload.

Oops, I realized a bit too late that we need setup-miniconda v2 😬


Raspberry Pi Pico: Pull Down Resistors on ADC PINs cause low input impedance

When using ADC inputs with the Raspberry Pi Pico, these pins have an internal pull-down resistor of around 50 kOhm activated after a reset. This could lead to a voltage drop when measuring resistors near that value (e.g., 24 kOhm).
Deactivating the pull-up/pull-down resistor fixes that problem:
#include <hardware/gpio.h>
gpio_set_pulls(26, false, false);
I initially thought I could simply add "bias-disable" in the rpi_pico-pinctrl.dtsi file to achieve this. However, it seems that soc/arm/rpi_pico/rp2/pinctrl_soc.h does not process "bias-disable," as it assumes that this is the default state for every pin.

This issue seems to have been fixed with commit 2e848d8.

how can I deactivate the ADC pull down resistors in micropython?


Nov15

Changes for November. (tito page is not setup yet.)
I've tweaked the import script so that it only imports talks in the next event. eg excludes talks scheduled for January.

This is great and the code works perfectly. Nice improvements to make error handling clearer, such as for no milestone on a talk, and future dates are handled now.
This will save us from a lot of manual effort making changes to the underlying data.


[DO NOT MERGE] Serve assets from S3 if they exist

NOTE. We're not intending for this branch to be merged to master. We're going to use it to test the behaviour of redirecting to S3 in integration.

This is a temporary change that will allow us to test redirecting to and
serving assets from S3 on integration.
This commit causes some tests to fail but we're not worrying about that
as we're not expecting this commit to end up in master.
We've tested the change locally and are happy that it results in a
redirect to assets uploaded to S3. Assets not on S3 continue to be
served directly from the filesystem.

I'm going to close this because I don't think we need it any more and in any case I'll leave the remote branch in place in case we do need it again.

Thanks @floehopper. I'm going to delete the branch as we can always recreate the changes based on the diff in this PR if we need to.


Please more providers for  Flixclusive

It would be better if they added more providers in Flixclusive

Duplicate of #13


Generator tag in RSS feed should be "Podsheets (https://podsheets.com)"

The  tag in the RSS feed reads "Podcast for Node".  I believe this tag is intended to describe who generated the feed, which in this case is "Podsheets (https://podsheets.com)"

@jeremyjung I updated the generator tag to use Podsheets - https://www.podsheets.com