Multiple Artists from Jellyfin are not scrobbled correctly

Please check the FAQ before submitting a bug report.
Describe the bug
Multiple Artists from Jellyfin are not scrobbled correctly. Only first Artist in list is submitted .
To Reproduce
Steps to reproduce the behavior:

Scrobble multi track song from jellyfin (correctly tagged in jellyfin by Picard)

Expected behavior
All artists should be submitted, correctly seperated
Logs
2023-02-24T07:14:11+00:00 debug : [Client Maloja - maloja_karsten ] Payload: [{"album":"The 30th Anniversary The Legend of Zelda Game Music Collection","artists":["永田権太"],"key":"TEeB6TsoQTkuHKDUA19p6tRABWuT0csbl793bkyqC6IOsJWEhBWvFqv75fp0Wl","length":129,"time":1677222818,"title":"プロロ島(アリルのテーマ)"}]
2023-02-24T07:14:11+00:00 info : [Client Maloja - maloja_karsten ] Scrobbled (New) => (Jellyfin) 永田権太 - プロロ島(アリルのテーマ) @ 2023-02-24T07:13:38+00:00
2023-02-24T07:14:11+00:00 debug : [Source - Jellyfin - jellyfin_karsten] Will not scrobble event because media type was not 'Audio' (undefined) [{"artists":[null]}]
2023-02-24T07:14:11+00:00 warn : [Source - Jellyfin - jellyfin_karsten] Config defined users but payload contained no user info
2023-02-24T07:14:11+00:00 warn : [Ingress - Jellyfin ] ::ffff:<IP_ADDRESS> (UA: Jellyfin-Server/10.8.9) Payload from Jellyfin did not contain server info! Make sure 'Send all Properties' is checked in webhook
2023-02-24T07:14:10+00:00 debug : [Source - Jellyfin - jellyfin_karsten] Will not scrobble event because media type was not 'Audio' (undefined) [{"artists":[null]}]
2023-02-24T07:14:10+00:00 warn : [Source - Jellyfin - jellyfin_karsten] Config defined users but payload contained no user info
2023-02-24T07:14:10+00:00 warn : [Ingress - Jellyfin ] ::ffff:<IP_ADDRESS> (UA: Jellyfin-Server/10.8.9) Payload from Jellyfin did not contain server info! Make sure 'Send all Properties' is checked in webhook
2023-02-24T07:14:09+00:00 debug : [Client Maloja - maloja_karsten ] Refreshing recent scrobbles
2023-02-24T07:14:09+00:00 info : [Source - Jellyfin - jellyfin_karsten] New Track => 永田権太 - プロロ島(アリルのテーマ) @ 2023-02-24T07:13:38+00:00
2023-02-24T07:14:09+00:00 debug : [Source - Jellyfin - jellyfin_karsten] (Stateful Play) (2e47c3621135b119ef5115676af9ea5f) 永田権太 - プロロ島(アリルのテーマ) added after being seen for 30 seconds and not matching any prior plays
2023-02-24T07:14:08+00:00 debug : [Source - Jellyfin - jellyfin_karsten] Will not scrobble event because media type was not 'Audio' (undefined) [{"artists":[null]}]
2023-02-24T07:14:08+00:00 warn : [Source - Jellyfin - jellyfin_karsten] Config defined users but payload contained no user info
2023-02-24T07:14:08+00:00 warn : [Ingress - Jellyfin ] ::ffff:<IP_ADDRESS> (UA: Jellyfin-Server/10.8.9) Payload from Jellyfin did not contain server info! Make sure 'Send all Properties' is checked in webhook
2023-02-24T07:14:05+00:00 debug : [Source - Jellyfin - jellyfin_karsten] Will not scrobble event because media type was not 'Audio' (undefined) [{"artists":[null]}]
2023-02-24T07:14:05+00:00 warn : [Source - Jellyfin - jellyfin_karsten] Config defined users but payload contained no user info
2023-02-24T07:14:05+00:00 warn : [Ingress - Jellyfin ] ::ffff:<IP_ADDRESS> (UA: Jellyfin-Server/10.8.9) Payload from Jellyfin did not contain server info! Make sure 'Send all Properties' is checked in webhook
2023-02-24T07:14:00+00:00 debug : [Source - Jellyfin - jellyfin_karsten] Will not scrobble event because media type was not 'Audio' (undefined) [{"artists":[null]}]
2023-02-24T07:14:00+00:00 warn : [Source - Jellyfin - jellyfin_karsten] Config defined users but payload contained no user info
2023-02-24T07:14:00+00:00 warn : [Ingress - Jellyfin ] ::ffff:<IP_ADDRESS> (UA: Jellyfin-Server/10.8.9) Payload from Jellyfin did not contain server info! Make sure 'Send all Properties' is checked in webhook
2023-02-24T07:13:58+00:00 debug : [Source - Jellyfin - jellyfin_karsten] Will not scrobble event because media type was not 'Audio' (undefined) [{"artists":[null]}]
2023-02-24T07:13:58+00:00 warn : [Source - Jellyfin - jellyfin_karsten] Config defined users but payload contained no user info
2023-02-24T07:13:58+00:00 warn : [Ingress - Jellyfin ] ::ffff:<IP_ADDRESS> (UA: Jellyfin-Server/10.8.9) Payload from Jellyfin did not contain server info! Make sure 'Send all Properties' is checked in webhook
2023-02-24T07:13:57+00:00 debug : [Source - Jellyfin - jellyfin_karsten] Will not scrobble event because media type was not 'Audio' (undefined) [{"artists":[null]}]
2023-02-24T07:13:57+00:00 warn : [Source - Jellyfin - jellyfin_karsten] Config defined users but payload contained no user info
2023-02-24T07:13:57+00:00 warn : [Ingress - Jellyfin ] ::ffff:<IP_ADDRESS> (UA: Jellyfin-Server/10.8.9) Payload from Jellyfin did not contain server info! Make sure 'Send all Properties' is checked in webhook
2023-02-24T07:13:55+00:00 debug : [Source - Jellyfin - jellyfin_karsten] Will not scrobble event because media type was not 'Audio' (undefined) [{"artists":[null]}]
2023-02-24T07:13:55+00:00 warn : [Source - Jellyfin - jellyfin_karsten] Config defined users but payload contained no user info
2023-02-24T07:13:55+00:00 warn : [Ingress - Jellyfin ] ::ffff:<IP_ADDRESS> (UA: Jellyfin-Server/10.8.9) Payload from Jellyfin did not contain server info! Make sure 'Send all Properties' is checked in webhook
2023-02-24T07:13:54+00:00 debug : [Source - Jellyfin - jellyfin_karsten] Will not scrobble event because media type was not 'Audio' (undefined) [{"artists":[null]}]
2023-02-24T07:13:54+00:00 warn : [Source - Jellyfin - jellyfin_karsten] Config defined users but payload contained no user info
2023-02-24T07:13:54+00:00 warn : [Ingress - Jellyfin ] ::ffff:<IP_ADDRESS> (UA: Jellyfin-Server/10.8.9) Payload from Jellyfin did not contain server info! Make sure 'Send all Properties' is checked in webhook
2023-02-24T07:13:52+00:00 debug : [Source - Jellyfin - jellyfin_karsten] Will not scrobble event because media type was not 'Audio' (undefined) [{"artists":[null]}]
2023-02-24T07:13:52+00:00 warn : [Source - Jellyfin - jellyfin_karsten] Config defined users but payload contained no user info
2023-02-24T07:13:52+00:00 warn : [Ingress - Jellyfin ] ::ffff:<IP_ADDRESS> (UA: Jellyfin-Server/10.8.9) Payload from Jellyfin did not contain server info! Make sure 'Send all Properties' is checked in webhook
2023-02-24T07:13:51+00:00 debug : [Source - Jellyfin - jellyfin_karsten] Will not scrobble event because media type was not 'Audio' (undefined) [{"artists":[null]}]
2023-02-24T07:13:51+00:00 warn : [Source - Jellyfin - jellyfin_karsten] Config defined users but payload contained no user info
2023-02-24T07:13:51+00:00 warn : [Ingress - Jellyfin ] ::ffff:<IP_ADDRESS> (UA: Jellyfin-Server/10.8.9) Payload from Jellyfin did not contain server info! Make sure 'Send all Properties' is checked in webhook
2023-02-24T07:13:49+00:00 debug : [Source - Jellyfin - jellyfin_karsten] Will not scrobble event because media type was not 'Audio' (undefined) [{"artists":[null]}]
2023-02-24T07:13:49+00:00 warn : [Source - Jellyfin - jellyfin_karsten] Config defined users but payload contained no user info
2023-02-24T07:13:49+00:00 warn : [Ingress - Jellyfin ] ::ffff:<IP_ADDRESS> (UA: Jellyfin-Server/10.8.9) Payload from Jellyfin did not contain server info! Make sure 'Send all Properties' is checked in webhook
2023-02-24T07:13:48+00:00 debug : [Source - Jellyfin - jellyfin_karsten] Will not scrobble event because media type was not 'Audio' (undefined) [{"artists":[null]}]
2023-02-24T07:13:48+00:00 warn : [Source - Jellyfin - jellyfin_karsten] Config defined users but payload contained no user info
2023-02-24T07:13:48+00:00 warn : [Ingress - Jellyfin ] ::ffff:<IP_ADDRESS> (UA: Jellyfin-Server/10.8.9) Payload from Jellyfin did not contain server info! Make sure 'Send all Properties' is checked in webhook
2023-02-24T07:13:48+00:00 debug : [Source - Jellyfin - jellyfin_karsten] Will not scrobble event because media type was not 'Audio' (undefined) [{"artists":[null]}]
2023-02-24T07:13:48+00:00 warn : [Source - Jellyfin - jellyfin_karsten] Config defined users but payload contained no user info
2023-02-24T07:13:48+00:00 warn : [Ingress - Jellyfin ] ::ffff:<IP_ADDRESS> (UA: Jellyfin-Server/10.8.9) Payload from Jellyfin did not contain server info! Make sure 'Send all Properties' is checked in webhook
2023-02-24T07:13:45+00:00 debug : [Source - Jellyfin - jellyfin_karsten] Will not scrobble event because media type was not 'Audio' (undefined) [{"artists":[null]}]
2023-02-24T07:13:45+00:00 warn : [Source - Jellyfin - jellyfin_karsten] Config defined users but payload contained no user info
2023-02-24T07:13:45+00:00 warn : [Ingress - Jellyfin ] ::ffff:<IP_ADDRESS> (UA: Jellyfin-Server/10.8.9) Payload from Jellyfin did not contain server info! Make sure 'Send all Properties' is checked in webhook
2023-02-24T07:13:44+00:00 debug : [Source - Jellyfin - jellyfin_karsten] Will not scrobble event because media type was not 'Audio' (undefined) [{"artists":[null]}]
2023-02-24T07:13:44+00:00 warn : [Source - Jellyfin - jellyfin_karsten] Config defined users but payload contained no user info
2023-02-24T07:13:44+00:00 warn : [Ingress - Jellyfin ] ::ffff:<IP_ADDRESS> (UA: Jellyfin-Server/10.8.9) Payload from Jellyfin did not contain server info! Make sure 'Send all Properties' is checked in webhook
2023-02-24T07:13:43+00:00 debug : [Source - Jellyfin - jellyfin_karsten] Will not scrobble event because media type was not 'Audio' (undefined) [{"artists":[null]}]
2023-02-24T07:13:43+00:00 warn : [Source - Jellyfin - jellyfin_karsten] Config defined users but payload contained no user info
2023-02-24T07:13:43+00:00 warn : [Ingress - Jellyfin ] ::ffff:<IP_ADDRESS> (UA: Jellyfin-Server/10.8.9) Payload from Jellyfin did not contain server info! Make sure 'Send all Properties' is checked in webhook
2023-02-24T07:13:40+00:00 debug : [Source - Jellyfin - jellyfin_karsten] Will not scrobble event because media type was not 'Audio' (undefined) [{"artists":[null]}]
2023-02-24T07:13:40+00:00 warn : [Source - Jellyfin - jellyfin_karsten] Config defined users but payload contained no user info
2023-02-24T07:13:40+00:00 warn : [Ingress - Jellyfin ] ::ffff:<IP_ADDRESS> (UA: Jellyfin-Server/10.8.9) Payload from Jellyfin did not contain server info! Make sure 'Send all Properties' is checked in webhook
2023-02-24T07:13:38+00:00 debug : [Source - Jellyfin - jellyfin_karsten] No prior candidate recent plays! Adding new locked plays: (2e47c3621135b119ef5115676af9ea5f) 永田権太 - プロロ島(アリルのテーマ)
2023-02-24T07:13:38+00:00 info : [Ingress - Jellyfin ] ::ffff:<IP_ADDRESS> (UA: Jellyfin-Server/10.8.9) Received valid data from server karsten-B450-AORUS-PRO (Version 10.8.9) for the first time.
2023-02-24T07:13:38+00:00 info : [Ingress - Jellyfin ] Received request from a new remote address: ::ffff:<IP_ADDRESS> (UA: Jellyfin-Server/10.8.9)

Versions (please complete the following information):
Provide version information for any related sources/clients.

multi-scrobbler: [latest develop image docker]
maloja [3.1.4]
jellyfin [10.8.9]

Webhook is configured according to docs, all properties is checked.
Artists in Jellyfin are like this: 永田権太;若井淑;峰岸透;近藤浩治
I think the multiple Warnings/Errors in the middle are unrelated, i get them every time i scrobble from jellyfin

Thanks for the logs and detail, I was able to reproduce this:

Jellyfin is only sending the first artist. I able to narrow this down to a coding decision in the jellyfin webhook plugin. I have reported the issue to the webhook plugin project. There is no way to fix this until they make changes.

@Karsten-Yan I've also improved logging for Jellyfin in the latest develop image. The debug output should give you more information about missing information as well as be less noisy.
If you are still seeing warnings about Config defined users but payload contained no user info and such you can additionally get the raw webhook payload sent to multi-scrobbler by modifying your jellyfin config to include logPayload like this:
[
  {
    "name": "MyJellyfin",
    "clients": [],
    "data": {
      "users": ["FoxxMD"],
      "servers": ["myServer","anotherServer"],
      "options": {
        "logPayload": false
      }
    }
  }
]

This will output the payload to DEBUG logging. Please include this in your reply if you are still seeing issues.

@FoxxMD Thanks for the quick response. Fingers crossed that it can be solved on the plugin side.
Also the log is now way less noisy, not seeing those errors anymore. If they occur again i'll make sure to include the payload in the logs.
Thanks for the awesome work!

@Karsten-Yan I've written a new Jellyfin Source that uses the API rather than webhook plugin and works with multiple artists. If you'd like to try it out follow the instructions in https://github.com/FoxxMD/multi-scrobbler/pull/172#issuecomment-2318716575

Fixed in 0.8.4 with the new Jellyfin Source


security layer code fixes

Definitions added
OpenFile call fixed

Thanks for your PR @Srinivas11789.
May I suggest you also fix the code style issue (maximum line length, indentation, formatting, whitespace)?


macosx file open dialog broken

on macosx (intel, sonoma) when trying to open any file explorer (open, save) the whole tracker stops responding and the file explorer will never open. I tried upgrading to latest gioui/x but that didn't help. probably an upstream issue but not sure. I am not a real go developer.

Yeah, I had issues using the OS-specific file dialogs in the past, and wrote my custom widgets for the file explorers. However, maintaining those custom file explorers was becoming a pain and they had several issues too, so I hopefully jumped back to using gioui/x explorers. I see that there still some issues with that :)
Anyway, to be able to do something right now, I suggest try copy-pasteing the file to Sointu. It should unmarshal the song data from the clipboard. Similarly, to save data, you can copy-paste stuff from sointu to a text file. Internally, sointu marshals all data to clipboard as yaml files.
I don't have mac, so I may need your help at some point to verify if various fix attempts solve this issue.

omg. didn't know about the copy-paste workaround. that might just do it for now :heart: I personally also don't have immediate access a mac. I helped a friend to get going. but I meet him frequently. so I should be able to help a bit

I have pushed a new commit that might solve the issue with file dialogs. Can you @m0ppers or someone else with a mac test?

works on MacOs Sonoma (Intel chip) 🎉  thanks

Cool! Thanks for testing. Closing.


Support variable value on mouse over

Show variable value when mouse is over in the current file

This is more of a task your attached debugger should do while running you application.


[SPARK-46424][PYTHON][SQL][FOLLOW-UP] Refactor and clean up Python metric implementation

What changes were proposed in this pull request?
This PR is a followup of https://github.com/apache/spark/pull/44375 that refactors and clean up the codes (pointed by review comments).
Why are the changes needed?
For better readability.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Existing test cases should cover. I also manually tested as described in https://github.com/apache/spark/pull/44375
Was this patch authored or co-authored using generative AI tooling?
No.

Merged to master.


[Documentation - Trackers Process]  Conducting Surveys and Polls

https://docs.google.com/document/d/1K-in78vt6z4VCMIFidiPy-Ir53PwRCU3Nt8eIqy7su0/edit#
welcomes Suggestive mode feedback and improvements

Made some suggestions for readability.

@debbiehoffman,
Wonderful feedback Debbie, 100% accepted!

Thank you to all of you, the wiki has been created. The word document has been moved to Survey's folder under Archive.
https://docs.google.com/document/d/1K-in78vt6z4VCMIFidiPy-Ir53PwRCU3Nt8eIqy7su0/edit#

https://github.com/microprofile/microprofile-wg/wiki/Why,-When-and-How-to-Conduct-Surveys


airmail-beta has no versioned download

Revert of commit 2723399 which breaks the formula on every Airmail Beta update (sha mismatch)

This was explained on the commit.


python37Packages.google-crc32c: 1.1.1 -> 1.1.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python37Packages.google-crc32c is: "Wrapper the google/crc32c hardware-based implementation of the CRC32C hashing algorithm"
meta.homepage for python37Packages.google-crc32c is: "https://github.com/googleapis/python-crc32c"
meta.changelog for python37Packages.google-crc32c is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

Warning: a test defined in passthru.tests did not pass

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 1.1.2 with grep in /nix/store/4ysppxfi0ccyzpq5fpvv5z04wp0nkhs3-python3.7-google-crc32c-1.1.2

directory tree listing: https://gist.github.com/be9cd4e46cf8b01e32981d1872a4d2a1

du listing: https://gist.github.com/fc93f8b9b361d570b7379889b4341d32

Rebuild report (if merged into master) (click to expand)

61 total rebuild path(s)

17 package rebuild(s)

15 x86_64-linux rebuild(s)
15 i686-linux rebuild(s)
14 x86_64-darwin rebuild(s)
17 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
dvc-with-remotes
python37Packages.google-cloud-automl
python37Packages.google-cloud-bigquery
python37Packages.google-cloud-storage
python37Packages.google-crc32c
python37Packages.google-resumable-media
python38Packages.google-cloud-automl
python38Packages.google-cloud-bigquery
python38Packages.google-cloud-storage
python38Packages.google-crc32c
python38Packages.google-resumable-media
python39Packages.google-cloud-automl
python39Packages.google-cloud-bigquery
python39Packages.google-cloud-storage
python39Packages.google-crc32c
python39Packages.google-resumable-media
wal_e

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/4ysppxfi0ccyzpq5fpvv5z04wp0nkhs3-python3.7-google-crc32c-1.1.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python37Packages.google-crc32c https://github.com/r-ryantm/nixpkgs/archive/6e5c0fc72be3f121717234edecbf3c5fe11b36c4.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/4ysppxfi0ccyzpq5fpvv5z04wp0nkhs3-python3.7-google-crc32c-1.1.2
ls -la /nix/store/4ysppxfi0ccyzpq5fpvv5z04wp0nkhs3-python3.7-google-crc32c-1.1.2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package marked as broken and skipped:

python39Packages.google-cloud-storage

14 packages built:

dvc-with-remotes
python37Packages.google-cloud-automl
python37Packages.google-cloud-bigquery
python37Packages.google-cloud-storage
python37Packages.google-crc32c
python37Packages.google-resumable-media
python38Packages.google-cloud-automl
python38Packages.google-cloud-bigquery
python38Packages.google-cloud-storage
python38Packages.google-crc32c
python38Packages.google-resumable-media
python39Packages.google-crc32c
python39Packages.google-resumable-media
wal_e

Maintainer pings
cc @freezeboy @SuperSandro2000 for testing.

LGTM

LGTM


COS Instance Name Added to DA Outputs

The COS instance name is generated by the DA from the <prefix>-<name> we should add this to the DA outputs.

cc : @SarikaSinha

PR Got merged.Hence Closing the issue.

@arya-girish-k FYI, its a good practise to link the PR and issue (I think you linked to the internal issue in the PR but not this one. Ideally link it to the public facing issue)

@ocofaigh : Ok,I will update it.Thanks


Missing link to more information about security changes

For information on how to specify relative links from a Welcome page or Markdown widget, see Source control relative links.

The "Source control relative links" is in bold on the page but missing a link anywhere.

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

ID: fa622358-f5bb-1f5c-177a-081a37b6acef
Version Independent ID: 72f7fd16-a822-66c8-3a34-8905645ce5f2
Content: Markdown syntax for files, widgets, and wikis - Azure DevOps
Content Source: docs/project/wiki/markdown-guidance.md
Product: devops
Technology: devops-collab
GitHub Login: @chcomley
Microsoft Alias: chcomley

@spoelstraethan Thanks for finding this. I've done a fix.


Add cleanup script and yaml for imported cluster

https://github.com/rancher/rancher/issues/15417

LGTM

LGTM


Use environment variables to config the puppet

for example, WECHATY_PUPPET_WALNUT_APPID.

We should always use WECHATY_PUPPET_WALNUT_ as the prefix.

Any information for the closing?
Have we started following the environment variable naming convention now?

Here is how I use the environment variables
  PuppetWalnut.sipId = options?.sipId || process.env['WECHATY_PUPPET_WALNUT_SIPID'] || ''
  PuppetWalnut.appId = options?.appId || process.env['WECHATY_PUPPET_WALNUT_APPID'] || ''
  PuppetWalnut.appKey = options?.appKey || process.env['WECHATY_PUPPET_WALNUT_APPKEY'] || ''
  if (!PuppetWalnut.sipId || !PuppetWalnut.appId || !PuppetWalnut.appKey) {
    throw new Error('Set your Environment variables')
  }

Great to know that!
Could you please add them to README so that other developers can read docs to learn them?

It is already in the RAEDME file
https://github.com/wechaty/puppet-walnut/blob/f3b9c64d1308b1d3e1f1c8bf9f0902f2062562b8/README.md?plain=1#L18-L23

That's awesome, thank you very much for the information l.
It would be great if you can link the commit to the related issue in the future so that every thing can be clear to our community.


LexicalComposerContext.useLexicalComposerContext: cannot find a LexicalComposerContext

Describe the bug
In a React app using Typescript and react-scripts, trying to load the page that uses the plugin components, I encounter this error:
LexicalComposerContext.useLexicalComposerContext: cannot find a LexicalComposerContext
Error: LexicalComposerContext.useLexicalComposerContext: cannot find a LexicalComposerContext
    at useLexicalComposerContext (http://localhost:3000/static/js/bundle.js:310379:13)
    at useIsFocused (http://localhost:3000/static/js/bundle.js:137780:116)
    at BeautifulMentionsPlugin (http://localhost:3000/static/js/bundle.js:135300:86)
    at renderWithHooks (http://localhost:3000/static/js/bundle.js:189783:22)
    at mountIndeterminateComponent (http://localhost:3000/static/js/bundle.js:193754:17)
    at beginWork (http://localhost:3000/static/js/bundle.js:195057:20)
    at beginWork$1 (http://localhost:3000/static/js/bundle.js:200016:18)
    at performUnitOfWork (http://localhost:3000/static/js/bundle.js:199286:16)
    at workLoopSync (http://localhost:3000/static/js/bundle.js:199209:9)
    at renderRootSync (http://localhost:3000/static/js/bundle.js:199182:11)

To Reproduce
Packages:

"react": "^18.2.0"
"react-scripts": "5.0.1"
"lexical": "^0.21.0",
"@lexical/react": "^0.21.0",
"lexical-beautiful-mentions": "^0.1.44",

I'm displaying these components:
export const MentionInputLexicon = ({
  message,
  setValue,
}:
MentionInputLexiconProps) => {
  const editorConfig = {
    namespace: 'MentionsEditor',
    nodes: [BeautifulMentionNode],
    onError: (error: Error, editor: LexicalEditor) => {
      console.error('Lexical Error:', error, 'editor', editor);
    },
  };

  useEffect(() => {
    console.log('MentionInputLexicon > Editor ready');
  }, []);

  const mentionnableUsers = [
    {
        "id": "1",
        "value": "Bob"
    },
    {
        "id": "2",
        "value": "Mary"
    }
]

  return (
    <LexicalComposer initialConfig={editorConfig}>
      <CustomMentionsPlugin
        mentionnableUsers={mentionnableUsers}
        setValue={setValue}
      />
    </LexicalComposer>
  );
};

where CustomMentionsPlugin:
export const CustomMentionsPlugin = ({
  mentionnableUsers,
  setValue,
}: {
  mentionnableUsers: { id: string; value: string }[];
  setValue: UseFormSetValue<{
    message: string;
  }>;
}): React.ReactNode => {
  const [editor] = useLexicalComposerContext();

  const mentionItems = {
    '@': mentionnableUsers,
  };

  useEffect(() => {
    console.log('CustomMentionsPlugin Lexical Editor Instance:', editor);
  }, [editor]);

  return (
    <Box
      sx={{ border: '1px solid #ddd', padding: '10px' }}
    >
      <RichTextPlugin
        contentEditable={<ContentEditable className='editor-input' />}
        placeholder={
Type @ to mention someone...
}
        ErrorBoundary={LexicalErrorBoundary}
      />

      <BeautifulMentionsPlugin
        items={mentionItems}
      />

      {/* <OnChangePlugin
        onChange={(editor: EditorState) => {
          console.log(editor);
        }}
      /> */}
    </Box>
  );
};

Expected behavior
The editor is loaded and the BeautifulMentions components are displayed without errors
Screenshots

@dosu

Ensure that CustomMentionsPlugin is directly within LexicalComposer without any other components in between that might not pass the context correctly. This setup should help resolve the error you're encountering.

It is directly within LexicalComposer.
One call out though: the component is in a separate ui-package, imported by the app. The app is itself wrapped in many providers (I18nextProvider,ReactQueryClientProvider, MUIThemeProvider,...) and the router functions from 'react-router-dom'. Could it explain the issue?

It actually looks good to me. Can you provide a codesandbox. Then I can take a look at it.

I'm facing this issue when rendering it in tests (vitest).
Error: LexicalComposerContext.useLexicalComposerContext: cannot find a LexicalComposerContext
 - /.../repos/foo/node_modules/.pnpm/@lexical+react@0.21.0_react-dom@18.2.0_react@18.2.0_yjs@13.6.12/node_modules/@lexical/react/LexicalComposerContext.dev.js:41:13
 - /.../repos/foo/node_modules/.pnpm/lexical-beautiful-mentions@0.1.44_@lexical+react@0.21.0_@lexical+utils@0.21.0_lexical@0.21.0__ffalppx7dvn37wnnkar3gute5m/node_modules/lexical-beautiful-mentions/cjs/useIsFocused.js:13:77
 - /.../repos/foo/node_modules/.pnpm/lexical-beautiful-mentions@0.1.44_@lexical+react@0.21.0_@lexical+utils@0.21.0_lexical@0.21.0__ffalppx7dvn37wnnkar3gute5m/node_modules/lexical-beautiful-mentions/cjs/BeautifulMentionsPlugin.js:111:61
 - /.../repos/foo/node_modules/.pnpm/react-dom@18.2.0_react@18.2.0/node_modules/react-dom/cjs/react-dom.development.js:16305:18
 - /.../repos/foo/node_modules/.pnpm/react-dom@18.2.0_react@18.2.0/node_modules/react-dom/cjs/react-dom.development.js:20074:13
 - /.../repos/foo/node_modules/.pnpm/react-dom@18.2.0_react@18.2.0/node_modules/react-dom/cjs/react-dom.development.js:21587:16
 - /.../repos/foo/node_modules/.pnpm/react-dom@18.2.0_react@18.2.0/node_modules/react-dom/cjs/react-dom.development.js:27426:14
 - /.../repos/foo/node_modules/.pnpm/react-dom@18.2.0_react@18.2.0/node_modules/react-dom/cjs/react-dom.development.js:26560:12
 - /.../repos/foo/node_modules/.pnpm/react-dom@18.2.0_react@18.2.0/node_modules/react-dom/cjs/react-dom.development.js:26466:5
 - /.../repos/foo/node_modules/.pnpm/react-dom@18.2.0_react@18.2.0/node_modules/react-dom/cjs/react-dom.development.js:26434:7


Ability to preview images, .png, .jpeg, .gif, on the card face as per Trello

Hi, do you have plans to allow images to be previewed on the card face as per Trello.
If so, this would be a hugely powerful plugin for art and game teams.
Thank you for your help and great job!

The extension is limited by what is available to extension apis on azure boards. The best way to add previews on the cards right now would probably be to write a chrome extension to insert them as chrome extensions have far fewer limitations.


Can't zoom or toggle grid in the gnuplot UI

When gnuplot starts I can't change zoom, autoscale or toggle grid. I've tried also with examples.
I'm using Arch Linux with KDE.
What's the problem?

unfortunately I know nothing about the gnuplot UI
On Wed, Jul 5, 2017 at 5:04 PM, Andrea<EMAIL_ADDRESS>wrote:

When gnuplot starts I can't change zoom, autoscale or toggle grid. I've
tried also with examples.
I'm using Arch Linux with KDE.
What's the problem?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/rdp/ruby_gnuplot/issues/47, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAw0H7qtPecsto4-bL-oAFvy1QBh4ISks5sLBZvgaJpZM4OO-Ji
.


Default image when sharing is MS logo, instead of a more specific and compelling image.

When sharing this page such as in a LinkedIn post by pressing the Share icon -> LinkedIn icon, the default image is the plain Microsoft logo. Ideally, it would be MRTK specific like the first photo on the page, to make it more compelling and more informative.

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

ID: 95809b24-cc2f-3118-6d05-c504ed734cfc
Version Independent ID: c9341566-b6b7-25bc-0121-1c6c30a43d49
Content: Introducing MRTK for Unity - Mixed Reality
Content Source: mixed-reality-docs/mr-dev-docs/develop/unity/mrtk-getting-started.md
Product: mixed-reality
Technology: mr-dev
GitHub Login: @cre8ivepark
Microsoft Alias: dongpark

Agreed, but this isn't a supported feature at this time. Thanks for the callout!


It should say that the number is too low.
https://github.com/ElijahCaine/huRandom/blob/develop/huRandom/huRandom.py#L72

That number is 1,000,000 not 100,000. Is that still a problem @iankronquist ?

-20,000,000 is too high! Please submit a number above -1,000,000.
My number is too low.

Resolved with the most recent commit.


Initialize SettableByteEntityReader only when inputFormat is not null

Fixes #9728
Description
SettableByteEntityReader has a null check in its constructor which throws NPE when inputFormat is null. This PR changes to creating it when inputFormat is not null.

This PR has:

[x] been self-reviewed.

[ ] using the concurrency checklist (Remove this item if the PR doesn't have any relation to concurrency.)

[x] added documentation for new or modified features or behaviors.
[ ] added Javadocs for most classes and all non-trivial methods. Linked related entities via Javadoc links.
[ ] added or updated version, license, or notice information in licenses.yaml
[ ] added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader.
[x] added unit tests or modified existing tests to cover new code paths.
[ ] added integration tests.
[ ] been tested in a test Druid cluster.

I tested this PR by feeding Avro data into local Druid cluster.


Updated the GitLab URL

Signed-off-by: Abhinav Anand<EMAIL_ADDRESS>
What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind cleanup
Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area blog

/area documentation

/area videos

What this PR does / why we need it:
I have fixed the typo in config.toml so now the GitLab logo will redirect to the GitLab homepage successfully.
Which issue(s) this PR fixes:

Fixes #469
Special notes for your reviewer:

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.
:memo: Please follow instructions in the contributing guide to update your commits with the DCO
Full details of the Developer Certificate of Origin can be found at developercertificate.org.
The list of commits missing DCO signoff:

06f5815 Updated the GitLab URL

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: atarax665
To complete the pull request process, please assign kris-nova after the PR has been reviewed.
You can assign the PR to them by writing /assign @kris-nova in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Welcome @atarax665! It looks like this is your first PR to falcosecurity/falco-website 🎉


feat: add olog package

Adds a new olog package with the intent of replacing the existing log
package. Based off of the Go Observability Tooling design document^1.
For those without access to that document, the main goals are encapsulated
below:

Uses *slog.Logger as the returned logging library (Highly recommended
read about the library)
Loggers must be instantiated with New() before a log line can be emitted,
there is no singleton provided by the olog package.
Packages should create their own logger(s) as required, storing it as a
package-level global singleton for ease of use (however, loggers can also
be created on the fly).
Default global logging level of Info, which all New() loggers respect.
Ability to change log level at a module and package level. Adjustable
through configuration while the process is still running.
Creating wrapped loggers using a provided *slog.Logger (ideally from
New()) to enable Outreach-specific functionality, like audit logs.
Pretty printing of logs by default when os.Stderr is a TTY (local development).
Automatically log otel-logging compliant TraceID and SpanID if a context with
trace information is passed to the logger.

This will require Context function calls to work.

Expected usage is calling New to create new logger per package. This should
be done either as a global variable per-package, or once per-package and passed
around.
Provides a test helper (NewTestCapturer) that enables callers to capture all log
output for the purpose of checking the output/result of certain operations via logs.
This is primarily intended to be used only for the development of the logger, since
logs are not a stable way to ensure an operation has occurred.

After doing a lot more digging into what's here, as well as looking into the goals of this more, it seems to me there are 2 things missing or incomplete as of now (though it's possible I'm missing something):

Ability to configure log levels per module/package. The registry in this package seems to allow for the possibility of setting and checking of log levels by module/package. However, as far as I can tell, there is currently no way for a caller to actually configure the registry, not to mention that nothing in this package is really setting the global registry's map by default (again, that I can tell). This shouldn't be difficult to change, but would need to determine the best way to expose that functionality to users.
The ability to automatically log otel-logging compliant TraceID and SpanID is also not provided by this package, though I feel it could easily add a convenient way for users to do so. Currently it's still possible by manually providing the extracted attributes on each logger instance, or by putting them on a logger per RPC call and persisting those attributes for every log/logger made during that call (slog.With(...)). But it would be nice to wrap the logging handlers to provide either automatic extraction of those context vars onto the log record (when context is provided), or by allowing hooks into that context/record before it sends and providing an out of the box otel extraction hook. The wrapper for this could be very light:

import (
    "context"
    "log/slog"

    "github.com/getoutreach/gobox/pkg/trace"
)

type ContextHandler struct {
	slog.Handler
}

func newContextHandler(handler slog.Handler) *ContextHandler {
	return &ContextHandler{Handler: handler}
}

func (ch *ContextHandler) Handle(ctx context.Context, r slog.Record) error {
	traceID := trace.ID(ctx)
	r.AddAttrs(slog.String("traceId", traceID))
	return ch.Handler.Handle(ctx, r)
}

Just an example

Ability to configure log levels per module/package. The registry in this package seems to allow for the possibility of setting and checking of log levels by module/package. However, as far as I can tell, there is currently no way for a caller to actually configure the registry, not to mention that nothing in this package is really setting the global registry's map by default (again, that I can tell). This shouldn't be difficult to change, but would need to determine the best way to expose that functionality to users.

Yes, I never implemented that functionality (oops). It was meant to be hooked into stencil-golang such that configuration files could set it. Since the goal was for that to be done through configuration. Also then code would be added to the managed HTTP handler to support setting it at runtime, eventually either using a CLI or just a grpcurl to change it at runtime.
I can't touch on point 2 because I honestly don't remember the context, but figured I'd chime in on 1 since it's an OSS repo, so hi! 👋


[daw-json-link] New port

Describe the pull request

What does your PR fix?
New port for json-link (perhaps the fastest JSON deserializer/serializer). Because we don't yet have enough JSON libraries...

Which triplets are supported/not supported? Have you updated the CI baseline?
all (I hope - only checked windows and linux). No need to update ci.baseline.txt.

Does your PR follow the maintainer guide?

Yes.

Yes.

If you are still working on the PR, open it as a Draft: https://github.blog/2019-02-14-introducing-draft-pull-requests/

@mheyman ,Could you please take a look?
config-x86-windows-out.log

The failure looks like it occurs in a cmake FetchContent_MakeAvailable() call. This call is identical for linux and windows. The failure occurs after a find_package(Git QUIET) fails to find git. I suspect git is available in the path for linux and osx but not for windows builds.
Darrell Wright's json-link library pulls in headers from two other of his projects. That is what the FetchContent_MakeAvailable() is trying to do.
If FetchContent_MakeAvailable() (with a requirement on git) is unavailable for vcpkg builds, it is possible that I can rework this port into three ports, one for each project. I'd have to patch-out the calls to FetchContent...(). If I do that, I think I should rename the port from json-link to daw-json-link with a dependency on daw-utf-range and daw-header-libraries to make it more obvious they are related (daw-utf-range is also dependent on daw-header-libraries). Much of the header files already land under a daw/ directory (I'm a little dissapointed they don't all land under daw/).
Is that how I should proceed? Make three ports that never call FetchContent_MakeAvailable()? Or, is there an easier solution?

@mheyman  For dependent third-party libraries, we have two ways:

Use the port in vcpkg if it exists.
Add vcpkg_from_github or other download methods to pre-download in portfile.cmake, and copy the decompressed folder to source path.

@mheyman ，Are you still working on fixing this pr?

Been away - still planning on it. I started the 3-port solution but the
patches required were not quick to finish and I need to set up some tests
too.
On Tue, Jul 6, 2021 at 2:55 AM JonLiu1993 @.***> wrote:

@mheyman https://github.com/mheyman ，Are you still working on fixing
this pr?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vcpkg/pull/18411#issuecomment-874508518,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJT7J2A3CIS755PLEOHHPLTWKSGBANCNFSM46S5VMSA
.

Renamed the port to daw-json-link which now depends on daw-utf-range which depends on daw-header-libraries.
daw-utf-range had been including a modified version of utfcpp - I moved the files under include/daw and the utf8 namespace under daw:: to keep from conflicting with the utfccp port. The modifications are constexpr/noexcept changes.
All of daw-json-link tests pass with the changes. Whew.

@mheyman ,Can you please resolve the conflicts against master?

Can you please merge to master?

Merged to master...

The first route I went down was simply using CMakeLists.txt. When that failed in the github vcpkg build system I had to split the single port into the three, daw-json-link, daw-utf-range, and daw-header-libraries. And, I tried to go the route of patching the CMakeLists.txt in each of those along with modifying the sources as needed. After going through multiple debug cycles, I thought "hey, this is header-only, why am I putting myself through all this grief when I can simply do a file(COPY...)? So, I switched tack and in less than an hour, I had a working install.
If you really want me to go back to the CMakeList.txt solution, I think it wasn't too far from a working solution using patched versions of those. If you simply want a daw-json-link-config.cmake and the like, I can certainly through some of those in there but I generally don't use them for header-only libraries (header-only-library CMake config files are not too complicated to hand code).

@mheyman I will give you some help.

Now uses vcpkg_cmake_configure(), vcpkg_cmake_install(), vcpkg_cmake_config_fixup() instead of the simple header-file-copy solution. :-)
Not sure I like the highly-patched CMakeLists.txt solution over the header file copy. I understand it is idiomatic vcpkg to use the cmake helpers but the vcpkg port maintainability suffers - if Darrell Wright ever appreciably changes the CMakeLists.txt files in the source repositories, maintaining the patches becomes more difficult.

One comment on the testing.  It is primarily tested on x64 linux/macos/windows in c++17, in develop C++20 too.  It has less primarily tested on 32bit arm/32bit windows but not as a first class.  When travis had free CI it was tested on BE ppc and/or S390 I think.  It's tested in constant expressions so should work on all the triplets, but I don't know that with certainty

The latest pull request includes the excellent source updates from beached that removed any need for patch files.

Header-only comments applied. Sorry for the delay. Life intervened but I did find a second flock of chickens in the neighborhood :-)


Feature Request: Mark as read on scroll

Thanks to the developer for bringing such an excellent RSS software, is it possible to add a feature similar to the "Mark as read on scroll" feature of the Reeder app?

We investigated this, but decided against it. We didn’t come up with a good-enough user experience.


tmux: Disable confirmation prompt

Add a new option to tmux module in order to be able to disable confirmation prompt before killing a pane or window

I first thought this change was adding too many empty lines but it seems it's already the case for other options.

It got me as well. I should probably concat the optionals instead.

I merged because I think it can be solved for the whole module in a later PR.


Implement V1 Timezone SDK

This PR contains:

Documentation
Generated code for Maps Timezone SDK from preview/1.0/timezone.json
Tests
Samples

API change check
API changes are not detected in this pull request.

Thanks for the hard work! Leave some comments and please check if you got the chance. And since this is a new package, please request architect for signing off on both the PR and the API view. Thanks!

Hi @andykao1213, thanks a lot for your review. I have one question regarding Timezone -> TimeZone renaming.. Does it make sense to wait for the SDK API review meeting to make sure we are aligned regarding the name, as this is the swagger input file Timezone/preview/1.0/timezone.json - also we wan't to see if we can push back typespec and use swagger at all.. So I think it's best to wait for review meeting first.. what do you think?


RESTEASY-1908 Write document about tracing feature

WIP don't merge.
This is relied on RESTEASY-2202 and 2203

created a rebased version: https://github.com/resteasy/Resteasy/pull/1993
closing this one.


Only uses the default AWS profile

Is there any way to allow for switching between profiles? Thanks for writing this, by the way :)

Hey hassankhan, this sounds like a good feature, thanks for submitting! Maybe it could be part of a new settings tab? I'll add it as a TODO item for the next version, 0.3.0.

Yeah, or possibly exposed as an option from the Menu bar (File, Edit) etc? Would love a "quick-switcher" type thing.


Android arm64-v8a release build crashes when loading KTX files

basis files work
development builds work

Couldn't reproduce in 0.8.0

I know this issue is closed, but we are having the exact same issue on 1.0.0, arm64, KTX files only, release only, using your example project.

Hi @ruben-ivre ,
sorry to hear that. I'll re-open the issue and investigate if you give me a bit more info:

Which Unity version are you using?
Is it reproducible 100%
Does it happen with a any KTX file or a particular one? If latter, can you provide it?
Does it crash with single files or only in conjunction with loading a bunch of files?

thanks!

Thanks for the quick response. I've just used your example project and published it to android, no changes other than that.

Which Unity version are you using?
2019.4.21
Is it reproducible 100%
Yes. Publish your example project to android, run it, choose "Format Test scene", pick any image and then any format in the right column, that should make it crash.
Does it happen with a any KTX file or a particular one? If latter, can you provide it?
I've used the ones included in your example project, and it crashed with all I tested with.
Does it crash with single files or only in conjunction with loading a bunch of files?
A single KTX file is enough to crash it.

It's crashing at:
/lib/arm64/libktx_unity.so (ktxTexture2_TranscodeBasis)
from `KTX-Software/lib/basis_transcode.cpp'
something's wrong with uint32_t* BDB = This->pDfd + 1; line. Accessing BDB later is crashing.

I found two bugs in the C binding that are likely the real reason for those crashes. I just tested KtxUnity 1.1.0 successfully on Android.


Incorrect change implementation for functional components

Problem
https://github.com/yewstack/yew/blob/fa8a1d9f007b00c02a3e3edabbb6d87fad9dc58c/yew-functional/src/lib.rs#L58-L62
Functional components only re-render if the new props are the same. They should re-render when the props are different!
@ZainlessBrombie

Oh dear


The user list can only be retrieved from the backend by validated clients

Issue has been resolved with commit 175ecd93d09af91ce96bf82c6686febfcfee21ae

Issue has been resolved with commit 175ecd93d09af91ce96bf82c6686febfcfee21ae

Gets tested by getOnlineUsers_invalidToken_thenThrowsUnauthorized_401 in UserControllerTest, added by commit 5e27ac68d07adcea325faabbe27ec7392d00c09e


Problem With Double Quotes

I have a problem when I export a database using this tool, the name of the table is in double quotes when is in the create statment, the right form is only in simple quotes, can anyone help me?

Hi, this has nothing to do with MySqlBackup.NET
It is the behavior of MySql Server which can be configured either as default (GLOBAL) behavior or temporary (SESSION) behavior of MySQL server.
Here is the SQL statements that you can try out yourself:
Example 1: Export table structure with double quotes:
set session sql_mode=ANSI_QUOTES;
show create table `configkey`;

output:
CREATE TABLE "configkey" (
  "key" varchar(100) NOT NULL,
  "value" text,
  PRIMARY KEY ("key")
) ENGINE=InnoDB DEFAULT CHARSET=utf8

Example 2: Export table structure with single quote
set session sql_mode=traditional;
show create table `configkey`;

output:
CREATE TABLE `configkey` (
  `key` varchar(100) NOT NULL,
  `value` text,
  PRIMARY KEY (`key`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8

For more information, please refer to official MySQL documentation under the topic: SQL-MODE
https://dev.mysql.com/doc/refman/5.7/en/server-options.html#option_mysqld_sql-mode
https://dev.mysql.com/doc/refman/5.7/en/sql-mode.html

Thank you very much.


odo login

add command odo login
as mentioned in https://github.com/redhat-developer/odo/issues/555

can you please review or tag respective person:
cc @kadel @jorgemoralespou  @simo5 @enj

travis is failing because of license check

@enj: "just use oc" is what failed for years from a developer experience POV. Feel free to reach to me if you want to pursue. We need login in odo, period.

We need login in odo, period.

There is no reason odo login cannot call oc login under the hood.
If you insist on vendoring an extra 4M LOC, do not expect any support from us.

@enj: if you had provided this as an API, which TBH is a fundamental key to enable those 4M LOC as a platform, we would not be there. Give us a supported API to do this, since we don't, well we go with what we can ...

there is a error am getting while following the below scenario

login to a cluster A
logout
login to cluster B

$ oc login https://clusterA:8443 --username=name --password=foo
$ oc logout
$ odo login https://<IP_ADDRESS>:8443 --username=name --password=foo
challenger chose not to retry the request

@syamgk , can you try whole scenario using odo and oc separately ?
Since we are doing any login magic, I think issue is from openshift side ?

@anmolbabu added e2e tests

@surajnarwade same scenario works with oc
$./oc version
oc v3.11.0+0cbc58b
kubernetes v1.11.0+d4cacc0
features: Basic-Auth GSSAPI Kerberos SPNEGO

Server https://api.starter-us-west-2.openshift.com:443
openshift v3.11.16
kubernetes v1.11.0+d4cacc0
$./oc login https://devtools-dev.ext.devshift.net:8443 --token=XXXXXXXXXXXXXXXXXXX
Logged into "https://devtools-dev.ext.devshift.net:8443" as "sgk" using the token provided.

You have access to the following projects and can switch between them with 'oc project <projectname>':

  * floc
    just4test

Using project "floc".
$./oc logout
Logged "sgk" out on "https://devtools-dev.ext.devshift.net:8443"
$./oc login https://<IP_ADDRESS>:8443  --username=developer --password=foo
Login successful.

You have one project on this server: "myproject"

Using project "myproject".

It looks like CI checks are in some weird state. @surajnarwade  Can please try to update this branch to retrigger it?

No description provided.

no description no link to the issue :-(

:white_check_mark: odo build 217 completed and artifacts can be found here (for commit https://github.com/redhat-developer/odo/commit/7a668fed62 by @surajnarwade)

:white_check_mark: odo build 219 completed and artifacts can be found here (for commit https://github.com/redhat-developer/odo/commit/99fd398cca by @surajnarwade)

:white_check_mark: odo build 224 completed and artifacts can be found here (for commit https://github.com/redhat-developer/odo/commit/08568d5e35 by @surajnarwade)

this is weird, tests are failing on service e2e tests, but all other prs are passing.
This doesn't look like a flaky test.

All jobs seem to be passing now

@geoand issue that you described is being tracked here https://github.com/redhat-developer/odo/issues/965 and we will take care of it in another PR

:white_check_mark: odo build 241 completed and artifacts can be found here (for commit https://github.com/redhat-developer/odo/commit/50a8b9e734 by @surajnarwade)

Thanks for pointing me to the issue Suraj
On Tue, Nov 13, 2018, 07:35 AppVeyorBot<EMAIL_ADDRESS>wrote:

✅ odo build 241 completed and artifacts can be found here
https://ci.appveyor.com/project/odo-bot/odo/builds/20254289/artifacts
(for commit 50a8b9e
https://github.com/redhat-developer/odo/commit/50a8b9e734 by
@surajnarwade https://github.com/surajnarwade)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/redhat-developer/odo/pull/826#issuecomment-438142869,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AELBv1gdtsO5kTySW5mdgUjLmov8hNTUks5uulolgaJpZM4XXKXR
.

:white_check_mark: odo build 243 completed and artifacts can be found here (for commit https://github.com/redhat-developer/odo/commit/038a16672b by @surajnarwade)

:white_check_mark: odo build 245 completed and artifacts can be found here (for commit https://github.com/redhat-developer/odo/commit/88e5075d9e by @surajnarwade)

@kadel added short flags

:white_check_mark: odo build 249 completed and artifacts can be found here (for commit https://github.com/redhat-developer/odo/commit/7d2a35d43b by @surajnarwade)


[EAGLE-435] make coordiantor schedule operation exclusive in distribu…

…ted deployment

Looks only fix the listener wise. The intension is to guarantee all the schedule.build(), not only the listener.

Looks only fix the listener wise. The intension is to guarantee all the schedule.build(), not only the listener.


Terminated the pqr type service of the contact microservice

 Quality gate: Failed
10 Issues

 9 Code issues
 1 Anti-patterns

Details


Question about semi assisted labelling

Hi,
I want to do semi-assisted labelling using the model, where I specify a few masks and let it predict the rest of the image. How do I do that? Is there a tool available?
Best,
Ahmed

@amusa22 you can build object detection model & pass it to sam & it will give you mask

Hi,
I want to do semi-assisted labelling using the model, where I specify a few masks and let it predict the rest of the image. How do I do that? Is there a tool available?
Best, Ahmed

Is that you want? https://github.com/anuragxel/salt

You should modify the code of the unsupervised segmentator


Add the decorative footer similar to the website

Share the screenshot of the working website.

Hey @devjainofficial can you tell me what things you need in your footer. I am interested in this project, and I want to work on it.

Basically, I majorly want something highly UI-based decorative footer that can fit with my website and some of the details of my social media accounts, copyright, etc, and you can also add something more that looks good.

Got it! @devjainofficial Thanks for the clarification. Please assign this issue to me.

@devjainofficial please verify and merge the changes


Isn't possible to configure different traffic label on the same physical network when creating a new zone

ISSUE TYPE

Bug Report

COMPONENT NAME

UI

CLOUDSTACK VERSION

4.16.0

CONFIGURATION

OS / ENVIRONMENT

Management server: CentOS 7
Browser used: Firefox
SUMMARY

During the Zone Creation, isn't possible to set different traffic labels.
STEPS TO REPRODUCE

In the UI, select Infrastructure/Zone and then, Add Zone. In the Physical Network step, when changing the traffic label of one element will changed it of all elements.

EXPECTED RESULTS

Different traffic label for each element.

ACTUAL RESULTS

When changing the traffic label of one element will changed it of all elements.

@msinhore I think this issue is similar to issue https://github.com/apache/cloudstack/issues/5705 and will be fixed in PR https://github.com/apache/cloudstack/pull/5714

@utchoang ok, I will close this issue as it was reported in #5714

@utchoang ok, I closed this issue as it was reported in #5714


Log levels below Information not working

If I change the sample app to eg. use _logger.LogDebug("...") or _logger.LogTrace("...") in RandomLogs method it does not log anything to the different loggers. They have options.MinLevel = LogLevel.Trace;, so seems like a bug.

    config.AddTarget(
        LogLevel.Trace,
        LogLevel.Fatal,
        new StreamingFileTarget(Path.Combine(FileSystem.Current.AppDataDirectory, "log"), 30));

my config is like this, but TRACE infos are not logged into file. Only INFO level or higher is logged.
MetroLog.MAUI Version 2.1.0
Env: MAUI .net6.0 , Windows 10

I'm seeing the same thing - currently having to use LogInformation() in place of LogTrace().
Despite the fact that explicitly calling LogTrace() is not resulting in output, there is some setup info coming out labelled as TRACE (CreateLogger etc.).
Also on .MAUI 2.1.0 but in a .net7 project.

Same here, LogDebug and LogTrace are not logged.

Hi All !
You have to set the MinimumLevel in Logging Extensions:
builder.Logging
            .SetMinimumLevel(LogLevel.Trace)
            .AddDebugLogger(

I will correct the docs :)

Thanks for your reply. Why did they set the minimum logging level to "Information"? Strange, because you also set the min- and maxlevels when configuring the LoggerProvider. https://github.com/dotnet/runtime/blob/18e3bbf628eba8dd9e27a0e1da3ff168192e60c7/src/libraries/Microsoft.Extensions.Logging/src/LoggingServiceCollectionExtensions.cs#L42

yup, it's confusing


Update train.py and evaluate.py to include new flags (format fix)

I think because this pull request was pointed at master, there are some additional files being changed. It might be better to merge #523 instead.


Add a GraphicsPipelineBuilder

Should make the API more ergonomic and removes the necessity to import all these small structs.
Not a breaking change, as the old API is only deprecated and not removed.

Should add specialization constants before merging, otherwise we are going to need to break the API.

How will this interact with pipeline derivatives? What about pipeline caches?

These are good points.
There are two aspects when it comes to pipeline derivates:

You can create a pipeline that is a derivate of a previously-created pipeline. This can easily be added with a method on the builder.
You can pass multiple VkGraphicsPipelineCreateInfo  at once to one call to vkCreateGraphicsPipelines, and indicate that some of them are derivates of others. However this one is much, much harder because you typically want to share the same intermediate structs (VkPipelineShaderStageCreateInfo, VkPipelineVertexInputStateCreateInfo, and so on) between multiple create infos.

Unfortunately I have really no idea for now how to do the latter properly. My opinion is to just leave it for later, without caring about an API break at this point.
When it comes to pipeline caches, since pipeline caches are part of the call to vkCreateGraphicsPipelines and not to the VkGraphicsPipelineCreateInfo, I think this should be added as an alternative to build(). In other words, add a method build_with_cache() for example.

These two things would need to be added later though. They are not supported by the current system, and for now the builder is just a wrapper around the current system.


chore: updated code of conduct ruleset

updated code of conduct naming convention for code-of-conduct-file-does-not-exist tocode-of-conduct-should-not-exist-here

@jbeveland27 would you be able to give a thumb on this change?

@jpvajda I think I know what happened. There was a small update in repolinter-rulesets/new-relic-one-catalog-project.json, but your editor also formatted the whole file and made it look like a large change. I reverted the formatting update, and then realized I was missing the rule name change, so added that one line change back as well. This is good to go now 👍🏼


fix(core): Add translation provider to No Search Results

What/Why?
The No Search Results form was missing a translation provider. This fixes that.
Testing
Verified that the "No Search Results" form now shows translated strings rather than e.g. NotFound.searchProducts

@christensenep good catch. I think SearchForm component can be wrapped with provider only, without other markup.
And BTW there is one more similar case https://github.com/bigcommerce/catalyst/blob/main/apps/core/app/[locale]/(default)/(faceted)/search/page.tsx#L34 - do you mind fixing it as well?

Thanks for the catch @BC-krasnoshapka, done.


Environment can break --help

$ qbatch --help
qbatch: error: QBATCH_SYSTEM set to slurm but sbatch not found

seems similar to https://github.com/Mouse-Imaging-Centre/pydpiper/issues/147 ... :)

@pipitone agree, that's exactly where the problem lies :+1:


Using "features": { "golang": "1.16" } fails with "no valid OpenPGP data found"

VSCode Version: 1.64.1

Reproduces in: Codespaces
Name of Dev Container Definition with Issue: features.golang

Steps to Reproduce:
The fastest reproduction is as follows:

wget https://raw.githubusercontent.com/microsoft/vscode-dev-containers/main/script-library/go-debian.sh
sudo bash ./go-debian.sh "1.16" "/usr/local/go" "/go"

The easiest reproduction is to include "golang": "1.16" in the code.
Both error with:
...
Preparing to unpack .../pkg-config_0.29.1-0ubuntu4_amd64.deb ...
Unpacking pkg-config (0.29.1-0ubuntu4) ...
Setting up libdpkg-perl (1.19.7ubuntu3) ...
Setting up pkg-config (0.29.1-0ubuntu4) ...
Processing triggers for man-db (2.9.1-1) ...
TARGET_GO_VERSION=1.16.14
GO_GPG_KEY_URI=https://dl.google.com/linux/linux_signing_key.pub
Downloading Go 1.16.14...
gpg: no valid OpenPGP data found.
gpg: the signature could not be verified.
Please remember that the signature file (.sig or .asc)
should be the first file given on the command line.

This occurs with this vanilla devcontainer:
FROM mcr.microsoft.com/vscode/devcontainers/base:ubuntu-20.04

Removing "golang" from the features section and the container builds correctly.  Golang can then be installed in a usual way.

I have the same issue for "latest". See also here: https://github.com/github/feedback/discussions/11262

Publishing Remote-Containers 0.221.0-pre-release including this fix and the one for #1300. Not sure if we expect this to be fixed upstream soon. Let me know if we need this in a regular release and the CLI for Codespaces too.

As codespaces depends on the pre-packaged scripts right now, would be nice to get a CLI update out @chrmarti

@chrmarti @joshspicer We still seem to be seeing the problem with dlv-dap 24 hrs later, so I think it is probably worth doing a release to resolve that issue given the Go extension no longer requires it.  1.17.7 and 1.16.14 are out now, but we got hit with two upstream problems on the same day. 🙁
I noticed an issue with the updated script that I just fixed. So ideally we'd do another rev of the vscode-dev-containers repos and do a release.  Agreed.

Change to 1.16.13 for the version. This looks like the same problem as https://github.com/microsoft/vscode-dev-containers/issues/1300. There appears to be a rough release getting out for these latest updates.

@Chuxel  I'm sure this is known/obvious, but just confirming that using "golang": "1.16.13" yields a different error from the one reported here (i.e. the problem reported in #1300):

[2022-02-11T17:42:45.151Z] #7 116.3 mv: cannot stat '/tmp/gotools/bin/dlv': No such file or directory

Great to see the quick attention to this, thanks to all.  I'm curious what the ordinary turnaround time is for this sort of issue, but don't want to pester (or hold anyone to anything). 😁

@brianmhunt Yes, that's the second issue I mention with dlv-dap. It also broke yesterday.  If you're using the script directly, you can just remove this section per https://github.com/microsoft/vscode-dev-containers/issues/1300#issuecomment-1035595700
Remove:
go ${go_install_command} -v github.com/go-delve/delve/cmd/dlv@master 2>&1 | tee -a /usr/local/etc/vscode-dev-containers/go.log
mv /tmp/gotools/bin/dlv ${TARGET_GOPATH}/bin/dlv-dap

We're currently working on getting a release out despite being an upstream problem given its disruptive. Remote - Containers should update quickly. @joshspicer is working with the Codespaces team as well to get updates there without disrupting anything.

I can confirm that this appears to be fixed i.e. codespaces now rebuild as expected.

Excellent! Closing.


feat(infinite-scroll-loader): move to correct position

Removes the infinite scroll loader from the top of the dropdown so that we can see it correctly when scrolling.

Test OK


Should wash down only stop the processes that wash up started?

See #398 for some background context.
The question is, should wash down be able to figure out what exactly wash up started (in particular, if it started NATS or just simply connected to it) and only take down what up started. A user would probably say yes? But then we introduce a state problem that isn't easy to guarantee will always work correctly.
Some quick ideas:

Write to a file containing the PID of processes we started

What happens if that process is killed by other means/the user reboots?

Is there any kind of "tagging" mechanism on processes we can use?

A user would probably say yes?

FFIW, I would be very upset if some tool I used was killing off services it didn't start.
wash down should 💯 be scoped to only PIDs it starts

Agreed with Jordan. Using a PID-file doesn't feel elegant, but it's straightforward. If no process is alive with an ID matching the contents of the file, that's fine; just assume the user/system has already killed the process

Thirded (yes I invented that word). Most people do get annoyed when something kills it shouldn't

Yep, I just ran into this when writing tests for wadm. We should definitely make sure we only do stuff to NATS we've started

This is the way as it is implemented in #556, and it is the way.


[BUG] Internal error occurred: failed calling webhook "rancher.cattle.io"

Rancher Server Setup

Rancher version: 2.6.9
Installation option (Docker install/Helm Chart): Helm

If Helm Chart, Kubernetes Cluster and version (RKE1, RKE2, k3s, EKS, etc): GKE  v1.23.8

Proxy/Cert Details: TLS externally handled by nginx ingress controller

Information about the Cluster

Kubernetes version: GKE  v1.23.8-gke.1900
Cluster Type (Local/Downstream): Local

User Information

What is the role of the user logged in? (Admin/Cluster Owner/Cluster Member/Project Owner/Project Member/Custom): Admin

Describe the bug
Completing the first installation of Rancher using helm chart (no errors from helm), there was a lot of errors seen in Rancher logs and the UI indicating
Internal error occurred: failed calling webhook "rancher.cattle.io": failed to call webhook: Post "https://rancher-webhook.cattle-system.svc:443/v1/webhook/mutation?timeout=10s": context deadline exceeded.
It looked like Rancher was unable to invoke the webhook successfully, and this could be due to the self signed certificate being used by rancher-webhook svc. Confirmed that by invoking the rancher-webhook svc from the rancher pod.
rancher-infra-dev-54885dd99d-89htt:/var/lib/rancher # curl https://rancher-webhook.cattle-system.svc:443/v1/webhook/mutation?timeout=10s
curl: (60) SSL certificate problem: unable to get local issuer certificate
More details here: https://curl.haxx.se/docs/sslcerts.html

curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.

I worked around this issue by setting the rancher.cattle.io, rancherfleet.cattle.io MutatingWebhookConfiguration and the ValidatingWebhookConfigurations's failurePolicy: Ignore. This allowed the API calls to the rancher-webhook to pass through and then complete the installation steps required by Rancher.
To Reproduce

Install Rancher (using Helm) for the first time in a new cluster using the follow values:

  tls: external
  hostname: rancher.company.com
  ingress:
    extraAnnotations:
      kubernetes.io/ingress.class: "nginx-internal"
      external-dns.alpha.kubernetes.io/hostname: rancher.company.com
  bootstrapPassword: value1

Login to the UI.
Observer in the homepage (under Cluster) with the error:
Internal error occurred: failed calling webhook "rancher.cattle.io": failed to call webhook: Post "https://rancher-webhook.cattle-system.svc:443/v1/webhook/mutation?timeout=10s": context deadline exceeded.

This was also seen when Rancher had to invoke the fleet endpoint.
Result
rancher-webhook's svc is unable to accept requests and the requester is seen with Context deadline exceeded.
Expected Result
Rancher should be able to bypass the internal calls to its svc.
Screenshots
An error from a different operation within Rancher showing the same error

Additional context
The workaround to set the mwc and vwc rancher.cattle.io's failurePolicy has also been automatically reverted to failurePolicy: Fail.

Hi there! It looks like we are facing the same issue here. My first suspect is TLS termination on L7 that I'm using as well.
Did you, by any chance try without the tls: external switch ?
Cheers

We are still not sure of a solution or the root cause. The one thing we are trying to see is, if installing cert-manager (even though it is not needed when Rancher is installed with tls:external) can help alleviate the issue.


[BUG] create-stream without shard-count fails with SerializationException

Describe the bug
The CreateStreamRequest defines the shardCount as mandatory / not optional.
This results in serialization errors when invoking create-stream if the shard-count is not set.
A request against AWS without the shardCount works:
aws kinesis create-stream --stream-name test

It's also marked as optional in the AWS CLI docs on create-stream: https://docs.aws.amazon.com/cli/latest/reference/kinesis/create-stream.html
To Reproduce
$ docker pull ghcr.io/etspaceman/kinesis-mock:0.2.4
$ docker run -d -p 4568:4568 ghcr.io/etspaceman/kinesis-mock:0.2.4
$ aws --endpoint-url=http://localhost:4568 kinesis create-stream --stream-name test

An error occurred (SerializationException) when calling the CreateStream operation: Invalid message body: Could not decode JSON: {
  "StreamName" : "test"
}

Expected behavior
The shardCount should be optional, i.e. the following request should successfully create a stream:
aws --endpoint-url=http://localhost:4568 kinesis create-stream --stream-name test

Additional context
Thanks for the great tool! Please let me know if any more info would be helpful.
I could also try to file a PR if the issue is confirmed. 🙂

How does Kinesis handle this? Is it simply created with 1 shard?
I unfortunately am quite busy at the moment and will not have the time to fix this, but I'm happy to review a PR

For me it defaults to 4 shards:
$ aws kinesis desribe-stream --stream-name create-without-shard-count
$ aws kinesis describe-stream --stream-name create-without-shard-count
{
    "StreamDescription": {
        "Shards": [
            {
                "ShardId": "shardId-000000000000",
                "HashKeyRange": {
                    "StartingHashKey": "0",
                    "EndingHashKey": "85070591730234615865843651857942052863"
                },
                "SequenceNumberRange": {
                    "StartingSequenceNumber": "49631808128049686821892032325846472026914148063194906626"
                }
            },
            {
                "ShardId": "shardId-000000000001",
                "HashKeyRange": {
                    "StartingHashKey": "85070591730234615865843651857942052864",
                    "EndingHashKey": "170141183460469231731687303715884105727"
                },
                "SequenceNumberRange": {
                    "StartingSequenceNumber": "49631808128071987567090562948988007745186796424700887058"
                }
            },
            {
                "ShardId": "shardId-000000000002",
                "HashKeyRange": {
                    "StartingHashKey": "170141183460469231731687303715884105728",
                    "EndingHashKey": "255211775190703847597530955573826158591"
                },
                "SequenceNumberRange": {
                    "StartingSequenceNumber": "49631808128094288312289093572129543463459444786206867490"
                }
            },
            {
                "ShardId": "shardId-000000000003",
                "HashKeyRange": {
                    "StartingHashKey": "255211775190703847597530955573826158592",
                    "EndingHashKey": "340282366920938463463374607431768211455"
                },
                "SequenceNumberRange": {
                    "StartingSequenceNumber": "49631808128116589057487624195271079181732093147712847922"
                }
            }
        ],
        "StreamARN": "arn:aws:kinesis:us-east-2:xxxxxxxxxxxx:stream/create-without-shard-count",
        "StreamName": "create-without-shard-count",
        "StreamStatus": "ACTIVE",
        "RetentionPeriodHours": 24,
        "EnhancedMonitoring": [
            {
                "ShardLevelMetrics": []
            }
        ],
        "EncryptionType": "NONE",
        "KeyId": null,
        "StreamCreationTimestamp":<PHONE_NUMBER>.0
    }
}

Maybe I can get to filing a PR, I'll give it a try :)


Include registry data in DR snapshots

@areed KURL_REGISTRY_IP is not something that can ever be defined by a vendor, and it's really only applicable when restoring another kURL cluster.  So I made it a command line flag only, at least for now.


How to handle JSON-LD with @ in it

Hi,
I have the following JSON-LD document, fully valid in ie https://json-ld.org/playground/:
https://gist.github.com/viggis75/27129127a1d3bd84b04f8af4f8e83ff4
I'm trying to use JsonPath to fetch nodes fromo this document, but I'm struggeling when I want to make a filter with Predicates which match on fields with @ in it.
The JSON-LD document linked to above has two orders, but ideally I would like to for example to get all orders where the orderDelivery.provider.employee[@id] is a given id that I provide as input.
or, I would like to get all orders where the orderDelivery[@type] is "ParcelDelivery" or something else I provide as input to the filter.
The code I've written so far looks like this:
JsonArray getOrdersByFoo(String orderDeliveryType) throws NoOrdersForDriverFoundException {
InputStream ordersAsStream = null; // this is where I read the JSON-LD document into
    Filter ordersByOrderDeliveryTypeFilter = Filter.filter(Criteria.where("orderDelivery[@type]").eq(orderDeliveryType));
    List<Map<String, Object>> orders = JsonPath.parse(ordersAsStream).read("$[*][?]", ordersByOrderDeliveryTypeFilter);
    if(orders == null || orders.isEmpty()) {
        throw new NoOrdersForDriverFoundException();
    }
    JsonReader jsonReader = Json.createReader(ordersAsStream);
    JsonArray ordersAsJsonArray = jsonReader.readArray();

    return ordersAsJsonArray;
}

@kallestenflo bump


Disable updates in Settings

On a localhost it takes minutes (less on a server but also long) to check for updates.
Please add a feature in settings to be able to disable updates completely.
Thank you!

@zenull hello.
This used to be an issue on older versions of WonderCMS.
Which version are you runnig? Also please provide more details regarding your server as our local tests don't take more than 3 seconds.

Closing for inactivity, please feel free to comment if you're having issues.


Fix DATA_PATH attribute

Just pointing out a minor bug, probably due to work in progress. I really want to jump in!
I really rather you didn't delete Rosie()! In future, more complex methods might be handy. For example, running different kinds of classifiers depending on a trigger.

Oh thanks. You're right, I didn't finish the job changing Rosie from a class to a module. Feel free to keep your eye on mistakes and suggesting things.


Breaks with newer versions of jquery

If you replace in the demo the line where it links to jquery with a newer version (), you'll see it no longer works properly.
Used this script for years though and really liked the ease of use. Thanks! Hope it gets updated at some point!

Apply the patch or update manually and all will work again:
https://github.com/jedfoster/Readmore.js/pull/206

Version 3.0 of Readmore.js will drop jQuery entirely, in favor of vanilla JS.


Unmount failed - Windows 10 64-bit

Etcher version: Etcher-1.0.0-rc.3-win32-x64.exe
Operating system and architecture: Windows 10 Home 64-bit

Getting below errors when flashing the latest Rasbian image from https://downloads.raspberrypi.org/raspbian_latest

Hi @craigusus ,
Thank you very much for reaching out. We're actively trying to fix this issue, however no-one from the Etcher team is able to reproduce, which makes things hard, so any help you can provide us would be incredibly valuable!
Some questions, so I can see if I can reproduce:

Does this happen every single time, or just sometimes? What happens if you retry, with the same image?
Does this happen if you try to flash another image?
What does the drive contains before flashing to it? Does it have multiple partitions, and therefore many drive letters attached to it?
What kind of drive is this? Is an SD Card? A USB stick? Are you plugging it in an internal reader?

Can you open DevTools by pressing Ctrl+Alt+I, go to the Console pane, and paste here what you get? There should be some messages prefixed with [mountutils] that have unmount specific debugging messages.
Thanks a lot!

Just downloaded the latest version of Etcher. Had the same problem on my WIN 7 64 bit moving an ISO from a SD card onto a boot (empty) 32GB USB.  Everything worked fine until the Unmounting stage.  Never progressed further

Thanks a lot for the info. As a workaround, you can go to the settings page (the cog in the top right corner), and disable the eject on success option, until we fix the problem.

Hi @jviotti,
Thanks for the the reply...

Does this happen every single time, or just sometimes? What happens if you retry, with the same image?

Seems to happen every time, including a retry (log results below)

Does this happen if you try to flash another image?

Yes, still fails on another image...
-1492457692236.txt

What does the drive contains before flashing to it? Does it have multiple partitions, and therefore many drive letters attached to it?

I have tried with empty drives and drives with partitions on already (never had issues on versions before 1.0.0)

What kind of drive is this? Is an SD Card? A USB stick? Are you plugging it in an internal reader?

It is a micro SD card, in an adaptor, using an external USB card reader. (again never had issues on versions before 1.0.0)
I have tried with empty drives and drives with partitions on already (never had problems in lesser versions)
DevTools results...
First try:
-1492456082805.txt
Retry:
-1492456647888.txt
Thanks

@craigusus just curious, did you have your task manager open whIle using etcher?

@fourthhorsem4n I don't recall having it open, no.

Hi @craigusus , @68goatconv , @fourthhorsem4n ,
I believe I have a fix for this issue: https://github.com/resin-io-modules/mountutils/pull/26. I created a custom build with the changes that you can download here: https://drive.google.com/open?id=0B7tkbonGU-RyRDVISkl4Sy1QRmc.
Do you mind giving it a go and confirm that the issue is indeed gone?
Thanks a lot!

Hi @jviotti,
I have just tried the custom build, and it works with no errors. Other than the Windows format error if I have the 'Eject on success' option ticked:

Tried with 2 different image files and same results.

Thank you very much for the testing. I'm very happy to hear that it worked! I'll release v1.0.0-rc.4 with the fix very soon.

You're welcome. Glad to be of assistance.

@jviotti
Thank you for solving this. However, after formatting (I used this guide ) and trying again I got the "The write has been completed successfully but Etcher detected potential corruption issues in reading the image back from the drive. It's possible that the drive is corrupted, please consider writing the image to a different one." message. I get my rpi 3 in the mail tomorrow so I'll be able to check if it works anyway.

That's great news. I'm releasing this on v1.0.0-rc.4!

Hi @haberdasher9000 ,

However, after formatting (I used this guide ) and trying again I got the "The write has been completed successfully but Etcher detected potential corruption issues in reading the image back from the drive. It's possible that the drive is corrupted, please consider writing the image to a different one."

That means that Etcher detected that at least one byte was not written correctly. I recommend you to try another SD Card, or another reader!

Hi,
I have just installed v1.0.0-rc.4 (Win64 version), and have used it to flash the hassbian image for a Raspberry Pi 3 to a micro SD card. I get the same Unmount failed error. I have tried it several times, and the same error all the time. However, the flash seems to be successful, it works okay in the Raspberry.

Hi @Zeerob ,
Sorry to hear that! Do you mind opening DevTools (with Ctrl+Alt+I), going to the Console pane, and pasting every output you see after the error occurs?

Hi jviotti,
The image seems to work, despite the error. So, I am using it, and have spend quit some time working with it. So, I am reluctant to flash it again, to see the error again, as it would destroy all my work so far. However, the error looked very much like the error that craigusus posted.
Thanks.

@Zeerob , the image should indeed have worked, as this is only an optional "eject" step. No worries, if you ever encounter the issue again, take a look a DevTools if you can, since that provides debugging information explaining exactly what when wrong under the hood, in much more detail than the top level error posted in this thread.

Hi jviotti,
Thanks, I will do that!

Awesome, thanks a lot! BTW, if the error keeps happening, you can disable automatic ejection after success on the settings screen!


Bug fixes

Fix issue with non root user for OpenVPN
Fix how Popen was working in python3 switch (OpenVPN, VNC, RDP)
Add more checks (OpenVPN & RDP)

Confirmed to be fixed, thanks @g0tmi1k


misspellings in README

In the subtitle "Use Case Scienario:" the word Scenario is misspelled
In "Use Case Scienario:" the word credentials is misspelled
In "Use Case Scienario:" the word favorite is misspelled
In the subtitle "Comming Soon" the word Coming is misspelled
In "Comming Soon" the word favorites is misspelled
in Donate section the word Address is misspelled

@AAhmed005 Thanks for pointing it out. Please feel free to raise a PR with the typos fixed and it shall be merged.

@AAhmed005 Thanks for pointing it out. Please feel free to raise a PR with the typos fixed and it shall be merged.

yep doing it right now:)


[Segment Replication] Support for custom codecs

Is your feature request related to a problem? Please describe.
Support rolling upgrades for plugins/integrations providing custom codec implementation e.g. k-NN. This will be fixed in core via https://github.com/opensearch-project/OpenSearch/issues/7349, this issue is about fixing the bridge
Parent: https://github.com/opensearch-project/OpenSearch/issues/3881
Fix on core: https://github.com/opensearch-project/OpenSearch/issues/7349
Describe the solution you'd like
On core rolling upgrades are fixed by https://github.com/opensearch-project/OpenSearch/issues/7349. Steps followed in this fix:

Load older codec in IndexWriter while upgrade is in progress (at least one replica shard running in older OS version).
Switch IndexWriter to codec version corresponding to upgraded OS version.
Rewrite older codec version segments with newer codecs.
Testing all the upgrade scenarios - https://github.com/opensearch-project/OpenSearch/issues/7490

In order to support custom codec, primary shard should read the custom OS version to codec mapping and then load the appropriate implementation (already available in classpath for kNN plugin).

List of plugins that do not need any further changes (do not extend codec service):

[x] opensearch-alerting
[x] opensearch-anomaly-detection
[x] opensearch-asynchronous-search
[x] opensearch-cross-cluster-replication
[x] opensearch-geospatial
[x] opensearch-index-management
[x] opensearch-job-scheduler
[x] opensearch-ml
[x] opensearch-neural-search
[x] opensearch-notifications
[x] opensearch-notifications-core
[x] opensearch-observability
[x] opensearch-performance-analyzer
[x] opensearch-reports-scheduler
[x] opensearch-security
[x] opensearch-sql

Plugins that require further investigation to verify if they support rolling upgrades for their custom codecs:

[ ] opensearch-knn
[ ] opensearch-security-analytics

To verify the working of custom codecs when we include the fix from https://github.com/opensearch-project/OpenSearch/pull/7698
Remake distribution on 2.8 branch + use 2.8 release knn -> upgrade to 2.x (2.9) with changes from #7698  + use 2.9 snapshot of knn

[ ] try regular indexing with knn.index = true
[ ] try knn mapping indexing with knn.index = true

Remake distribution on 2.8 branch + use 2.8 release knn + lower codec to lucene94 + update mapping of version to codec -> upgrade to 2.x (2.9) with changes from  #7698 + use 2.9 snapshot of knn + update mapping of version to codec

[ ] try regular indexing with knn.index = true
[ ] try knn mapping indexing with knn.index = true

This is to verify whether further changes are required to enable rolling upgrades for clusters with segment replication and knn enabled.

While upgrading from modified 2.8 distribution that's using lucene94 codec, we see that in the segment replications taking place, we are still loading in KNN950Codec instead of the KNN940Codec that is expected on using Lucene94.
In KNNCodecService.java:
    @Override
    public Codec codec(String name) {
        return KNNCodecVersion.current().getKnnCodecSupplier().apply(super.codec(name), mapperService);
    }

In the above code - KNNCodecVersion.current() points to V_9_5_0 which uses KNN950Codec as a wrapper.
So non-KNN related operations would use Lucene94, but KNN related operations would still use Lucene95.
In a true codec bump, we would be sending over higher version KNNCodec during segment replication which wouldn't be able to be read by lower codec version nodes in a rolling upgrade.
In order to support rolling upgrades for segment replication and knn enabled:

[ ] Modify overridden method codec() in KNNCodecService.java to load the appropriate KNN Codec based on codec passed into method.

For added security, should also only allow this operation if rolling upgrade is in progress.

Closing this out as this implementation of the solution was discarded in favor of introducing the shard_movement_strategy setting as mentioned in #3881


Installation

Cannot get it working yet.
My content folder was already a sub repository, so I skipped the step 'Create a new git repository for your content' in the installation instructions. I followed the instructions under 'Download and configure the Plugin'.
When I change content in the panel I just see my changes as unstaged files (not as commits) in my local repository and nothing is pushed to the remote.

Make sure the Git.php folder isn't empty - looks like github does not include the submodules in the .zip it provides.

The Git.php folder is not empty.

Are you on Windows? Try adding this to your config: c::set('gcapc-windowsMode', true); you can also try to set the path to your git manually using c::set('gcapc-gitBin', true);.
If that still doesn't do the trick for you can try debugging in the helpers.php using the Git.php options GitRepo->test_git, Git::is_repo.

One of the main problems is having the webserver running under a different account then the file owner...
While the Plugin is trying to modify your content/.git/index.lock file (obviously being called from Git.php via the webserver-user) Git.php is throwing an error similar to "fatal: Unable to create '/content/.git/index.lock': Permission denied"
Solution -> Check the file rights and don't forget to add the according ssh keys of the webserver user to your github/bitbucket account... :)

There is a link that gives a solution to this problem - you can find it in the options section - https://gist.github.com/jexchan/2351996

ref #3


fix sortQueryParameters: false append null to url w/ empty query param

Fix #52

Sorry, missed your PR. Was fixed by https://github.com/sindresorhus/normalize-url/commit/01fc8111254d4a9fe682f8089b2a5845cc44de67.


Hotfix 20 2

Description:
Don't create our own process group id because we don't get keyboard interrupt signals (ctrl-C) when our parent is a bash script.
Related issue (if applicable): #2136
Pull request in home-assistant.io with documentation (if applicable): home-assistant/home-assistant.io#
Example entry for configuration.yaml (if applicable):

Checklist:
If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated in home-assistant.io

If code communicates with devices:

[ ] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[ ] New dependencies have been added to the REQUIREMENTS variable (example).
[ ] New dependencies are only imported inside functions that use them (example).
[ ] New dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[ ] New files were added to .coveragerc.

If the code does not interact with devices:

[ ] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[ ] Tests have been added to verify that the new code works.

Let's include c96f73d1be946b5e0311c396a92aeeb3fde1fa7b and b3afb386b70dbe1c98e9a0d5c34dcfe488c8f2f5 (Google Maps Travel sensor bug fixes)


feat(world): store read system

Moves the World's IStoreRead methods into an init system, allowing them to be upgraded. This does have a noticeable gas impact.

Closing in favour of https://github.com/latticexyz/mud/pull/2632


failed to install metrics

How to use it?

[X] kwok
[X] kwokctl --runtime=docker (default runtime)
[ ] kwokctl --runtime=binary
[ ] kwokctl --runtime=nerdctl
[ ] kwokctl --runtime=kind

What happened?
Tried to explore kubelet metrics (introduced in #199) with an in-cluster deployment. Tried with the provide test script ./test/kwokctl/kwokctl_metric_test.sh as well which resulted in the same error message:
{"time":"2023-08-08T11:57:31.228654753Z","level":"INFO","source":{"function":"sigs.k8s.io/kwok/pkg/kwok/cmd.runE","file":"/workspace/pkg/kwok/cmd/root.go","line":130},"msg":"Watch all nodes"}
{"time":"2023-08-08T11:57:31.988402793Z","level":"ERROR","source":{"function":"main.main","file":"/workspace/cmd/kwok/main.go","line":50},"msg":"Execute exit","err":"failed to install metrics: failed to create metrics update handler: failed to initialize metrics update handl
er: failed to compile metric \"fake-node\": failed to compile metric expression: ERROR: :1:23: undeclared reference to 'StartedContainersTotal' (in container '')\n | StartedContainersTotal( node.metadata.name )\n | ......................^"}

What did you expect to happen?

Metric is registered successfully.
Metric can be scraped.

How can we reproduce it (as minimally and precisely as possible)?
./test/kwokctl/kwokctl_metric_test.sh v1.27.4

Anything else we need to know?
No response
Kwok version

$ kwok --version
kwok version v0.3.0 go1.20.5 (linux/amd64)

$ kwokctl --version
kwokctl version v0.3.0 go1.20.5 (linux/amd64)

OS version

$ cat /etc/os-release

Arch Linux

This requires building kwok and kwokctl based on the latest branch, or switching to the 0.3 branch


Debouncing visits into the log

Currently any logging that results in an activity (start/stop triggers) adds a new entry into the visit log.  This works great for most use cases, especially since it's nice to know you were briefly viewing documentation and paging back and forth.  It lines up with usage.
... however this breaks down when sites abuse the ability to autoreload for refreshing instead of opting for a more asynchronous approach via sockets or transparent polling.  What happens in this case is that a page will constantly refresh while it's open to sync new data in and will unintentionally flood the visit log with entries.
We should enable a debounce threshold to eliminate these occurrences.  One issue is knowing how long of a delay until inserting? If the refresh triggers every few minutes, but you keep the page open all day, we'll need to debounce at the minute level.  However, if you visit a page, wait a few minutes and then go back to that tab it will not log as a separate instance, even though minutes lasted in between.
@schilippe do you have any feedback on how you would prefer to see this implemented?

@tbranyen I will look into it. It is not only a problem with reload, even if someone is splitting their time between two tabs, each time a tab is switched, it logs a new visit and places a new row.
Maybe we should revisit the definition of a "visit". I am not sure how useful of a metric the visits are the way they are defined now. What if we call a "visit" the fact that a page was opened and stop the visit when the page is closed (ie url is changed or tab is closed) thus making a "visit" a decision the user made to visit the site. I frequently multitask between tabs but I don't know if I would call each tab switch a unique visit. This way, we don't have too many rows in each table, and each row would really correspond to a unique choice by the user to visit a site.
In terms of implementation, I am trying to think how much this will break our existing setup...

I agree that visit count is a relatively meaningless measure. Perhaps we
shouldn't be measuring it at all, but instead be looking at, e.g. "days
with a visit".   Perhaps api's would also let us detect "opening" a site
by (i) entering an address in the address bar or (ii) clicking a
bookmark or (iii) clicking on a link; we could count those.
On 1/28/2015 4:50 PM, schilippe wrote:

@tbranyen https://github.com/tbranyen I will look into it. It is not
only a problem with reload, even if someone is splitting their time
between two tabs, each time a tab is switched, it logs a new visit and
places a new row.
Maybe we should revisit the definition of a "visit". I am not sure how
useful of a metric the visits are the way they are defined now. What
if we call a "visit" the fact that a page was opened and stop the
visit when the page is closed (ie url is changed or tab is closed)
thus making a "visit" a decision the user made to visit the site. I
frequently multitask between tabs but I don't know if I would call
each tab switch a unique visit. This way, we don't have too many rows
in each table, and each row would really correspond to a unique choice
by the user to visit a site.
In terms of implementation, I am trying to think how much this will
break our existing setup...
—
Reply to this email directly or view it on GitHub
https://github.com/haystack/tipsy/issues/55#issuecomment-71923760.

I will a "days with a visit" column that to the table and see what people think about it.

I pushed up a branch last night with a "Days with visit" column, but I don't want to merge it with master.

Alright, I merged PR #56  the additional column branch with a new branch I created off master called master-daysVisited

So the "days visited" column seems to be all worked out now that many of the bugs (the Chrome API is unfortunately far from robust) have been fixed. I've been pushing and merging the changes on the separate branch.
But before this issue is closed we still might want to decide exactly how many, or which, entries to show in the table when the user clicks on the individual entry. Now it is still showing all the visits. We should probably reduce that but to what? I think the "visit" idea of when the tabbed is switched to might be more useful than just when the page was loaded and unloaded since users often leave tabs open for a long time, sometimes even forgetting they are there. A visit means they actually gave it some attention. But there are just too many visits, even without the automatically refreshing pages. Maybe bucketing them within a certain parameter would be the best, but what should this parameter be? I think a day would be good and just to show the last visit of the day. Any objections and/or other ideas?


Update LAB[PL-400]_Lab02_Model_Driven_App.md

Add to switch to classic. Publish and then switch to classic again
Module: 00
Lab/Demo: 00
Fixes # .
Changes proposed in this pull request:

Submitted by Tattedgeek on behalf of MOC Labs Review

Submitted by Tattedgeek on behalf of MOC Labs Review


Added $JOBS variable to all make -j commands

Some of the make -j commands were missing the $JOBS variable. Added it to make it consistent across all targets.

LGTM, thanks!


dual mat chams?

Does anyone here know how to do like skeet chams? No glow arms race but like dual pass chams? I really would like to know how to do it heres an example of what i mean
https://cdn.discordapp.com/attachments/587599760601645056/627205033494183955/image0.jpg

Can you further elaborate on what you are saying?

Can you further elaborate on what you are saying?

From my understanding it uses 2 materials and forces them together not really sure how it works but they look really cool heres another pic
https://prnt.sc/n25q6y
and heres a video
https://www.youtube.com/watch?v=YhZHgfLyP3s&feature=youtu.be
as you can see this guy is using 3 materials..

dude isn't it just a plastic chams?

or a arm removal + surface glow tho?

the"3 material chams" is prob the arm removal + surface glow + color chams

there are no such a thing as double chams

+1

@thomas0aotian well there is actually something like dual passed chams.
masterlooser did that a long time ago with a black ak47 and white outlines(wireframe)
and it was made popular by a leaked cheat named rifk7. That video there is of a friend of mine and i got the codes but he has hard coded it and has used 3 materials for his hand chams.

How many materials do you want? Keep in mind that every extra model draw reduces your fps.

@danielkrupinski heres some code that might help
https://pastebin.com/jFfTnxJc
the guy in the video uses it but its hard coded so i couldn't implement it.

@danielkrupinski 2 materials would be enough as the title suggests

How many materials do you want? Keep in mind that every extra model draw reduces your fps.

just 2 but please make em sexy like the image : D

id love this feature looks cool :)

+rep this, glow on hands would be lit

Added.