Manually implement FfiType for ConstString

Since we have only one case of using union we could instead of making derive macroses even more complicated we could just derive this traits manually.

I'm reviving this ticket for further consideration. Previous code is removed here


"I have no name!" as user logging into docker container using tini

Hey there, this feels more like a question then a bug.
I'm currently using a Jenkins instance inside a docker container.
This image happens to use Tini as PID 1.
When I try open a shell into it with:
docker exec -it jenkins /bin/bash
I get this as username:
I have no name!@<container_id_hash>:/$
This is keeping me from using shell born ssh commands from Jenkins jobs that run in this container:
$ ssh
No user exists for uid 497
$ id
$ uid=497 gid=495 groups=495
I tried creating an user for that uid in /etc/passwd and also a group for that gid in /etc/group but it was a no deal!
I'm only able to run ssh manually if I login as jenkins user like this:
docker exec -it --user=jenkins jenkins /bin/bash
I could circle around that using ssh related plugins. But I'm really curious to understand why this happens only with docker images that use Tini as ENTRYPOINT.

Hi there @rcbop,
What image are you using for Jenkins? The official one, or a hand-rolled one? If the latter, can you share your Dockerfile? Either way, can you share how it was started?
I doubt this is due to Tini itself, considering it doesn't do anything UID-related, but I'm happy to look into it a little bit.
Cheers,

Hey there @krallin!
My dockerfile for that container is currently something like this:
FROM jenkinsci/jenkins:2.3
USER root
RUN apt-get update -qqy \
    && apt-get install -y \
      locales \
      nano \
      make \
      openssh-client \
    && locale-gen en_US.UTF-8 \
    && echo "LC_ALL=en_US.UTF-8" >> /etc/environment \
    && echo "LANG=en_US.UTF-8" >> /etc/environment \
    && echo "LC_ALL=en_US.UTF-8" >> /etc/default/locale \
    && echo "LANG=en_US.UTF-8" >> /etc/default/locale

 // a few credentials related stuff [...]

USER jenkins
ENV JAVA_OPTS="-Dfile.encoding=UTF8"
//Installing plugins
COPY plugins.txt /usr/share/jenkins/plugins.txt
COPY executors.groovy /usr/share/jenkins/ref/init.groovy.d/executors.groovy
RUN /usr/local/bin/plugins.sh /usr/share/jenkins/plugins.txt

Thank you for the awesomness!

@rcbop, jenkinsci/jenkins:2.3 doesn't actually exist. I'm assuming you might be using jenkins:2.3? If not, it's going to be a little hard for me to try and repro.
Using jenkins:2.3, I'm able to spin up a new container and use docker exec with it and I don't get the I have no name! error. I suspect this issue might be related to the base image you're using (perhaps it's outdated?), or perhaps you're using Docker with user namespace support and something's going wrong?
Either way, do you have a reason to think this only happens when Tini is used?

Hey @krallin. No particular reason, except, I guess, my lack of understanding of how Tini works. I'm gonna try studying the code. Thanks for the support, by the way, here is jenkinsci/jenkins dockerhub page which is different from official docker page for jenkins. Cheers.

I have moved this to a stackoverflow question in hope to reach more people.

@rcbop Ha; it looks like the 2.3 tag doesn't exist there (anymore?).
Could you perhaps try with another one of their tags and let me know which one you chose and whether it works? That way at least we'll be working off of the same base image.
Cheers,

Whoa.. true to that... I'm gonna check that and report my finds. Thanks for pointing that out.

Hey @krallin,
I have come across the information that this message is displayed when the current user's uid and gid from docker host is not mapped inside the container's /etc/passwd. So Tini is not the cause of that. So I'm closing this issue. Thanks for all the support.

Thanks for confirming :+1:

I have had this same issue but in a Docker container running on Kubernetes. I removed the security context section from the deployment and the respective user declared.
After this, the issue was gone.


this.activeElement on config.show

It's interesting to know which element is calling modal

🙏 Thank you.


[video_player] Add support for changing the uri of the video

Usecase: Video players are memory intense for screens like a feed of posts. Modern apps reuse just 1 video player instance for the screen. Currently the flutter video player plugin hasn't implemented this functionality. I've currently working on implementing this feature in our app. Just wanted to create this Issue to track if the team has this item planned or is open to a PR to extend the video player functionality.
Android exoplayer has setMediaItem: Clears the playlist, adds the specified MediaItem and resets the position to the default position.
iOS AVplayer has replaceCurrentItem: The new item for the player object to play.
The web video player has the src attribute: I believing just changing the src attribute will resest and change the video.

Hi @VictorUvarov, I believe this is a duplicate of https://github.com/flutter/flutter/issues/44690.
Feel free to share your findings in the issue linked above and yes PRs are always welcome.
Closing this as a duplicate of the issue linked above.
If you disagree, leave a comment below and I will reopen this.
Thank you


need to be able to pass custom variables

with the new gitops module template, we need passed to our modules? we used to put them in a block like this in the verify.yaml but this doesn't seem to be working now.
env:
TF_VAR_database_username: ${{ secrets.DATABASE_USERNAME }}
TF_VAR_database_password: ${{ secrets.DATABASE_PASSWORD }}

@seansund fyi as requested


[Bug]  White screen

I removed all active flags and the program stopped working.
How to restore them? Where are logs and configs stored in Linux?

hi @debunkt ! same issue and answer as #266 - its an electron update issue i think. would welcome help in debugging as idk how to reproduce


localisation of controls (e.g. 'Grouped', 'Stacked')

and here goes another question :) thanks again for this brilliant piece of work!
how can i localise the control - texts in the following chart?
http://plnkr.co/edit/IYV66U?p=preview

You might be able to do that like below.
`chart.controlLabels({"grouped":"XXX","stacked":"YYY"})


Bounded stack

Based on #155. This PR removes the blocking part of the previous PR. The issue with it is that it adds a dependency to picos, probably requiring to create a Saturn_picos package.
For Saturn.1.0,  we have decided to do only a bounded stack, thus this PR.

@Sudha247 : Could you have a look at this PR (at the documentation, or even a quick look at the tests, maybe ?), any feedbacks will be great !

@art-w I think this PR is good to. What do you think ?

Mmh there is a stack overflow on Treiber_stack.push_all. This PR has almost the same implementation so I will have a look before merging !

Yes it looks good! Out of curiosity, are the copy_as_padded on records necessary? (my understanding is that this makes the allocated object fatter, so as to avoid false-sharing contention, but the head atomic already appears to be protected by make_contended)

Good question. As nothing else is mutable in the stack type, probably not.


Update Enhanced-Mass-Deployment.md

@jashanno for review.

:x: Organization membership check failed
Members of the MicrosoftDocs organization should use the private repo. Please move your changes to https://github.com/MicrosoftDocs/Dynamics-365-Operations, and close this pull request.


FileNotFoundError..

Hi Everyone,
I already set all environment up, but when i run Test mode for ViT_B checkpoint, an error occur like the below image.

Can everyone help me, Please~~

I got the above error while trying to test the model with the pre-trained model ViT_B downloaded from baidu. I followed the instructions on GitHub to install and set up the environment, but I got the above error.

I have a question

I downloaded the material on github. And I'm trying to use the pre-trained Swin_T or ViT_B models downloaded from baidu.
so, what should I modify in the downloaded one?
additionally, we are going to train it with our own data. What should we do?

/data/RSBuilding-main/configs_finetune/base/datasets/standard_512x512_foundationdataset.py
I ran into the same problem, you need to change the sixth line, but I don't know how the author handled test4.txt, so the code still can't run

Thank you for answer!
-----------------------원본 메세지-----------------------
보낸사람: @.>
받는사람: "Meize0729/RSBuilding" @.>
참조: "kuyhni" @.>, "Comment" @.>
보낸날짜: 2024-04-16 16:17:14 GMT +0900 (Asia/Seoul)제목: Re: [Meize0729/RSBuilding] FileNotFoundError.. (Issue #3)
/data/RSBuilding-main/configs_finetune/base/datasets/standard_512x512_foundationdataset.py
I ran into the same problem, you need to change the sixth line, but I don't know how the author handled test4.txt, so the code still can't run
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>


Missing dataset data and index files

The dataset resources provided by Loftr do not seem to include scan/index/scan net_ How can I obtain the test. txt and scan/inedx/test. npz files?

You can find it here.
https://drive.google.com/drive/folders/1SrIn9WJ1IuG08yh2nEvIsLftXHLrrIwh


Add methods for auto-history of data

Needed in addition to journaling ? In separate collections ? For which collections ? Add timestamp as mixin or directly ?
Use https://www.npmjs.com/package/loopback-auditz
Added only timestamps for now, see feature/timestampTracing branch

done for datasets


[CI] Evaluate new GHA backend for sccache

Describe the enhancement requested
sccache 4.0 added a github actions cache backend that caches the objects as single caches vs caching the entire cache at once. As the usage of the cache api does not require elevated privileges this might be a way to improve c++ caching on PRs.
Component(s)
Continuous Integration

Reference:

https://github.com/mozilla/sccache/blob/main/docs/GHA.md
https://github.com/marketplace/actions/sccache-action

Also it might not be a good idea to invest time in this for now:
GHA cache is so slow when caching small objects


PR: fix preprocessor macro bug with no param macro instance followed by parenthesis

This is my effort to fix #3145 . It is NOT working.
I'm putting this draft PR only as a base for discussion, it should not be merged as-is.

See https://github.com/chipsalliance/Surelog/issues/3145#issuecomment-1221230808

I'm working on another approach.


Fixing the gradle version to 8.7

Description
This PR fixes the docker images gradle version to 8.7, just before their InstallationLocation constructor was modified.
As detailed in the issue, there is already a merged PR from opensearch, but it's beyond version 2.15, so this is a temporary fix.
Issues Resolved
Resolves #318
Check List

[x] New functionality includes testing.

[x] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[ ] Failing checks are inspected and point to the corresponding known issue(s) (See: Troubleshooting Failing Builds)
[x] Commits are signed per the DCO using --signoff
[ ] Commit changes are listed out in CHANGELOG.md file (See: Changelog)
[ ] Public documentation issue/PR created

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

After the change is applied, the docker images build properly:
$ ./ci.sh up
WARN[0000] /home/fede/src/wazuh-indexer/docker/ci/ci.yml: `version` is obsolete
[+] Running 2/2
 ! wi-build Warning    pull access denied for wi-build, repository does not exist or may require 'docker login': denied: requested access to the resource i...                   2.5s
 ! wi-assemble Warning pull access denied for wi-assemble, repository does not exist or may require 'docker login': denied: requested access to the reso...                      2.5s
[+] Building 62.0s (14/20)                                                                                docker:default
 => [wi-build internal] load build definition from Dockerfile                                                                                0.0s
 => => transferring dockerfile: 683B                                                                                0.0s
 => [wi-assemble internal] load metadata for docker.io/library/ubuntu:jammy                                                                                1.4s
 => [wi-build internal] load metadata for docker.io/library/eclipse-temurin:21-jdk-alpine                                                                                1.5s
 => [wi-build internal] load metadata for docker.io/library/gradle:8.7.0-jdk21-alpine                                                                                2.5s
 => [wi-assemble internal] load .dockerignore                                                                                0.0s
 => => transferring context: 2B                                                                                0.0s
 => CACHED [wi-assemble 1/3] FROM docker.io/library/ubuntu:jammy@sha256:340d9b015b194dc6e2a13938944e0d016e57b9679963fdeb9ce021daac430221                                         0.0s
 => [wi-assemble 2/3] RUN mkdir /home/wazuh-indexer &&     apt-get update -y &&     apt-get install curl gnupg2 -y &&     curl -o- https://www.aptly.info/pubkey.txt | apt-key  60.5s
 => => # Get:297 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 libpcre2-16-0 amd64 10.39-3ubuntu0.1 [203 kB]
 => => # Get:298 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 libpcre2-32-0 amd64 10.39-3ubuntu0.1 [194 kB]
 => => # Get:299 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 libpcre2-posix3 amd64 10.39-3ubuntu0.1 [6130 B]
 => => # Get:300 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 libpcre2-dev amd64 10.39-3ubuntu0.1 [730 kB]
 => => # Get:301 http://archive.ubuntu.com/ubuntu jammy/main amd64 libselinux1-dev amd64 3.3-1build2 [158 kB]
 => => # Get:302 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 libmount-dev amd64 2.37.2-4ubuntu3.4 [14.5 kB]
 => [wi-build internal] load .dockerignore                                                                                0.0s
 => => transferring context: 2B                                                                                0.0s
 => [wi-build builder 1/4] FROM docker.io/library/gradle:8.7.0-jdk21-alpine@sha256:d6ea1c746d8365fae41c70d5812c28c8fca88c905b69d5f9da57ad4cc0218ab1                             32.6s
 => => resolve docker.io/library/gradle:8.7.0-jdk21-alpine@sha256:d6ea1c746d8365fae41c70d5812c28c8fca88c905b69d5f9da57ad4cc0218ab1                                               0.0s
 => => sha256:b59e9873ba742a479cce77b1222861958ce5a6e621b95bf2ddcd3496e2d22b7c 2.90kB / 2.90kB                                                                                0.0s
 => => sha256:d3e26ecb87fb595e4952cc40f85668ec6b8df141786d550ba0867bd003bd22ba 7.72kB / 7.72kB                                                                                0.0s
 => => sha256:a3fd38fd7cf5b8d60c92e1aa46a24527229fb51b451491d35a7028a8a1d0aba4 13.14MB / 13.14MB                                                                                3.8s
 => => sha256:d6ea1c746d8365fae41c70d5812c28c8fca88c905b69d5f9da57ad4cc0218ab1 2.68kB / 2.68kB                                                                                0.0s
 => => sha256:4abcf20661432fb2d719aaf90656f55c287f8ca915dc1c92ec14ff61e67fbaf8 3.41MB / 3.41MB                                                                                0.5s
 => => sha256:332bf309ecf2b86f336452cb3137f9b266c99d9a10612bd124e2f13e0dad9bb3 158.72MB / 158.72MB                                                                              24.0s
 => => extracting sha256:4abcf20661432fb2d719aaf90656f55c287f8ca915dc1c92ec14ff61e67fbaf8                                                                                0.0s
 => => sha256:2e377b89d6767f434b66aef2b55d4397fa1ca4ef205a16f2fc626005be867634 190B / 190B                                                                                1.1s
 => => sha256:45705fa60e5881f3a69ceb008964dcca0e72d626655d99b6d92e4c0834c7131b 717B / 717B                                                                                1.5s
 => => sha256:139b55c8532d30c022b37d343fee5e3b33a0e8e51e903d285b6624f144025cdd 1.31kB / 1.31kB                                                                                2.1s
 => => sha256:4f4fb700ef54461cfa02571ae0db9a0dc1e0cdb5577484a6d75e68dc38e8acc1 32B / 32B                                                                                2.4s
 => => sha256:450b7f4750e03e0b16c111f939835cb461fdd66a163773c1c68a5d7cfee2268f 34.88MB / 34.88MB                                                                                11.0s
 => => extracting sha256:a3fd38fd7cf5b8d60c92e1aa46a24527229fb51b451491d35a7028a8a1d0aba4                                                                                0.2s
 => => sha256:f38f7076143cf0fdb81f64c889e46d42d2a09e9f16c468f28101ed517c1ee156 134.21MB / 134.21MB                                                                              32.2s
 => => sha256:7bda177df30edadfddb14fc7938185363d1a975fa06f625dfd41bba520bae1ee 54.91kB / 54.91kB                                                                                11.4s
 => => extracting sha256:332bf309ecf2b86f336452cb3137f9b266c99d9a10612bd124e2f13e0dad9bb3                                                                                0.8s
 => => extracting sha256:2e377b89d6767f434b66aef2b55d4397fa1ca4ef205a16f2fc626005be867634                                                                         [+] Building 62.1s (14/20)                                                                                docker:default                                                               => [wi-build internal] load build definition from Dockerfile                                                                                0.0s                                                               => => transferring dockerfile: 683B                                                                                0.0s                                                               => [wi-assemble internal] load metadata for docker.io/library/ubuntu:jammy                                                                                1.4s                                                               => [wi-build internal] load metadata for docker.io/library/eclipse-temurin:21-jdk-alpine                                                                                1.5s                                                               => [wi-build internal] load metadata for docker.io/library/gradle:8.7.0-jdk21-alpine                                                                                2.5s                                                               => [wi-assemble internal] load .dockerignore                                                                                0.0s                                                               => => transferring context: 2B                                                                                0.0s                                                               => CACHED [wi-assemble 1/3] FROM docker.io/library/ubuntu:jammy@sha256:340d9b015b194dc6e2a13938944e0d016e57b9679963fdeb9ce021daac430221                                         0.0s50f497824540d90ff29d4b819a6a6287a5eb1b03a71e4c2167b            => [wi-assemble 2/3] RUN mkdir /home/wazuh-indexer &&     apt-get update -y &&     apt-get install curl gnupg2 -y &&     curl -o- https://www.aptly.info/pubkey.txt | apt-key  60.7s-g 1000 wazuh-indexer &&   adduser -u 1000 -G wazuh-indexer -D => => # Get:297 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 libpcre2-16-0 amd64 10.39-3ubuntu0.1 [203 kB]                                                                                => => # Get:298 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 libpcre2-32-0 amd64 10.39-3ubuntu0.1 [194 kB]                                                                                => => # Get:299 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 libpcre2-posix3 amd64 10.39-3ubuntu0.1 [6130 B]                                                                                => => # Get:300 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 libpcre2-dev amd64 10.39-3ubuntu0.1 [730 kB]                                                                                => => # Get:301 http://archive.ubuntu.com/ubuntu jammy/main amd64 libselinux1-dev amd64 3.3-1build2 [158 kB]                                                                                => => # Get:302 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 libmount-dev amd64 2.37.2-4ubuntu3.4 [14.5 kB]                                                                                => [wi-build internal] load .dockerignore                                                                                0.0s                                                               => => transferring context: 2B                                                                                0.0s                                                               => [wi-build builder 1/4] FROM docker.io/library/gradle:8.7.0-jdk21-alpine@sha256:d6ea1c746d8365fae41c70d5812c28c8fca88c905b69d5f9da57ad4cc0218ab1                             32.6s
 => => resolve docker.io/library/gradle:8.7.0-jdk21-alpine@sha256:d6ea1c746d8365fae41c70d5812c28c8fca88c905b69d5f9da57ad4cc0218ab1                                               0.0s
 => => sha256:b59e9873ba742a479cce77b1222861958ce5a6e621b95bf2ddcd3496e2d22b7c 2.90kB / 2.90kB                                                                                0.0s
 => => sha256:d3e26ecb87fb595e4952cc40f85668ec6b8df141786d550ba0867bd003bd22ba 7.72kB / 7.72kB                                                                                0.0s
 => => sha256:a3fd38fd7cf5b8d60c92e1aa46a24527229fb51b451491d35a7028a8a1d0aba4 13.14MB / 13.14MB                                                                                3.8s
 => => sha256:d6ea1c746d8365fae41c70d5812c28c8fca88c905b69d5f9da57ad4cc0218ab1 2.68kB / 2.68kB                                                                                0.0s
 => => sha256:4abcf20661432fb2d719aaf90656f55c287f8ca915dc1c92ec14ff61e67fbaf8 3.41MB / 3.41MB                                                                                0.5s
 => => sha256:332bf309ecf2b86f336452cb3137f9b266c99d9a10612bd124e2f13e0dad9bb3 158.72MB / 158.72MB                                                                              24.0s
 => => extracting sha256:4abcf20661432fb2d719aaf90656f55c287f8ca915dc1c92ec14ff61e67fbaf8                                                                                0.0s
 => => sha256:2e377b89d6767f434b66aef2b55d4397fa1ca4ef205a16f2fc626005be867634 190B / 190B                                                                                1.1s
 => => sha256:45705fa60e5881f3a69ceb008964dcca0e72d626655d99b6d92e4c0834c7131b 717B / 717B                                                                                1.5s
 => => sha256:139b55c8532d30c022b37d343fee5e3b33a0e8e51e903d285b6624f144025cdd 1.31kB / 1.31kB                                                                                2.1s
 => => sha256:4f4fb700ef54461cfa02571ae0db9a0dc1e0cdb5577484a6d75e68dc38e8acc1 32B / 32B                                                                                2.4s
 => => sha256:450b7f4750e03e0b16c111f939835cb461fdd66a163773c1c68a5d7cfee2268f 34.88MB / 34.88MB                                                                                11.0s
 => => extracting sha256:a3fd38fd7cf5b8d60c92e1aa46a24527229fb51b451491d35a7028a8a1d0aba4                                                                                0.2s
 => => sha256:f38f7076143cf0fdb81f64c889e46d42d2a09e9f16c468f28101ed517c1ee156 134.21MB / 134.21MB                                                                              32.2s
 => => sha256:7bda177df30edadfddb14fc7938185363d1a975fa06f625dfd41bba520bae1ee 54.91kB / 54.91kB                                                                                11.4s
 => => extracting sha256:332bf309ecf2b86f336452cb3137f9b266c99d9a10612bd124e2f13e0dad9bb3                                                                                0.8s
 => => extracting sha256:2e377b89d6767f434b66aef2b55d4397fa1ca4ef205a16f2fc626005be867634                                                                         [+] Building 190.8s (22/22) FINISHED                              docker:default
 => [wi-assemble internal] load build definition from Dockerfile            0.0s8 => => transferring dockerfile: 1.11kB                                      0.0s  => [wi-build internal] load build definition from Dockerfile               0.0s
 => => transferring dockerfile: 683B                                        0.0s1 => [wi-assemble internal] load metadata for docker.io/library/ubuntu:jamm  1.4s  => [wi-build internal] load metadata for docker.io/library/eclipse-temuri  1.5s
 => [wi-build internal] load metadata for docker.io/library/gradle:8.7.0-j  2.5sc => [wi-assemble internal] load .dockerignore                               0.0s  => => transferring context: 2B                                             0.0s
 => CACHED [wi-assemble 1/3] FROM docker.io/library/ubuntu:jammy@sha256:34  0.0sc => [wi-assemble 2/3] RUN mkdir /home/wazuh-indexer &&     apt-get updat  107.2s  => [wi-build internal] load .dockerignore                                  0.0s
 => => transferring context: 2B                                             0.0s1 => [wi-build builder 1/4] FROM docker.io/library/gradle:8.7.0-jdk21-alpi  32.6s  => => resolve docker.io/library/gradle:8.7.0-jdk21-alpine@sha256:d6ea1c74  0.0s
 => => sha256:b59e9873ba742a479cce77b1222861958ce5a6e621b9 2.90kB / 2.90kB  0.0s5 => => sha256:d3e26ecb87fb595e4952cc40f85668ec6b8df141786d 7.72kB / 7.72kB  0.0s  => => sha256:a3fd38fd7cf5b8d60c92e1aa46a24527229fb51b45 13.14MB / 13.14MB  3.8s
 => => sha256:d6ea1c746d8365fae41c70d5812c28c8fca88c905b69 2.68kB / 2.68kB  0.0s  => => sha256:4abcf20661432fb2d719aaf90656f55c287f8ca915dc 3.41MB / 3.41MB  0.5s  => => sha256:332bf309ecf2b86f336452cb3137f9b266c99d9 158.72MB / 158.72MB  24.0s
 => => extracting sha256:4abcf20661432fb2d719aaf90656f55c287f8ca915dc1c92e  0.0s  => => sha256:2e377b89d6767f434b66aef2b55d4397fa1ca4ef205a16f2 190B / 190B  1.1s  => => sha256:45705fa60e5881f3a69ceb008964dcca0e72d626655d99b6 717B / 717B  1.5s
 => => sha256:139b55c8532d30c022b37d343fee5e3b33a0e8e51e90 1.31kB / 1.31kB  2.1ss => => sha256:4f4fb700ef54461cfa02571ae0db9a0dc1e0cdb5577484a6d7 32B / 32B  2.4s  => => sha256:450b7f4750e03e0b16c111f939835cb461fdd66a1 34.88MB / 34.88MB  11.0s
 => => extracting sha256:a3fd38fd7cf5b8d60c92e1aa46a24527229fb51b451491d35  0.2s  => => sha256:f38f7076143cf0fdb81f64c889e46d42d2a09e9 134.21MB / 134.21MB  32.2sD => => sha256:7bda177df30edadfddb14fc7938185363d1a975fa 54.91kB / 54.91kB  11.4s
 => => extracting sha256:332bf309ecf2b86f336452cb3137f9b266c99d9a10612bd12  0.8s  => => extracting sha256:2e377b89d6767f434b66aef2b55d4397fa1ca4ef205a16f2f  0.0s  => => extracting sha256:45705fa60e5881f3a69ceb008964dcca0e72d626655d99b6d  0.0s
 => => extracting sha256:139b55c8532d30c022b37d343fee5e3b33a0e8e51e903d285  0.0s  => => extracting sha256:4f4fb700ef54461cfa02571ae0db9a0dc1e0cdb5577484a6d  0.0s  => => extracting sha256:450b7f4750e03e0b16c111f939835cb461fdd66a163773c1c  0.6s
 => => extracting sha256:f38f7076143cf0fdb81f64c889e46d42d2a09e9f16c468f28  0.4s  => => extracting sha256:7bda177df30edadfddb14fc7938185363d1a975fa06f625df  0.0s  => [wi-build internal] load build context                                  2.1s
 => => transferring context: 11.99MB                                        2.0s  => [wi-build stage-1 1/5] FROM docker.io/library/eclipse-temurin:21-jdk-a  0.0s  => CACHED [wi-build stage-1 2/5] RUN apk add git &&   apk add curl &&   a  0.0s
 => [wi-build builder 2/4] WORKDIR /home/wazuh-indexer                      0.2s  => [wi-build builder 3/4] COPY --chown=gradle:gradle . /home/wazuh-index  11.5s  => [wi-build builder 4/4] RUN gradle clean                               115.3s
 => [wi-assemble 3/3] WORKDIR /home/wazuh-indexer                           0.0s  => [wi-assemble] exporting to image                                        2.4s  => => exporting layers                                                     2.4s
 => => writing image sha256:4e025398523427110116702d31c093185465cc6c225c3b  0.0s  => => naming to docker.io/library/wi-assemble:4.9.0                        0.0s  => [wi-build stage-1 3/5] COPY --from=builder --chown=1000:0 /home/wazuh  11.7s
 => [wi-build stage-1 4/5] WORKDIR /home/wazuh-indexer                      0.0s  => [wi-build stage-1 5/5] RUN git config --global --add safe.directory /h  0.2s  => [wi-build] exporting to image                                          10.5s
 => => exporting layers                                                    10.5s
 => => writing image sha256:9bdd92acb28713ed7fb2a38102e30b97a8fd15f2b5a711  0.0s
 => => naming to docker.io/library/wi-build:4.9.0                           0.0s
[+] Running 3/3
 ✔ Network ci_default           Created                                     0.1s
 ✔ Container wi-assemble_4.9.0  Started                                     0.4s
 ✔ Container wi-build_4.9.0     Started                                     0.4s


Hot swap lora with updated llama.cpp

Describe the feature
Feature
Since the PRs linked below in llama.cpp, it is possible to how-swap lora adapters. This allows to personalise NPCs and other GenAi game features by fine-tuning adapters that then can be quickly swapped on the same base model in memory.
Since llama.cpp has is being updated in #209. It would be nice to check how easily one can integrate this feature.
Todo list

[ ] bin files for adapters are now deprecated in favour of new gguf files, which should be ameneded in the documentation, if appearing.
[ ] Test on using the new gguf formats should be run (I suspect the new adapter will automatically be used in hot-swapping mode)
[ ] Test using multiple adapters and hot swapping them, add code if needed, and add an example in the examples folder.

Hot lora PRs in llama.cpp

Cli: https://github.com/ggerganov/llama.cpp/pull/8332
Server: https://github.com/ggerganov/llama.cpp/pull/8857

I am happy to have a go at it 😃

Wow thanks for the detailed request ⭐!
I implemented multiple loras and hot swapping in #210 . Do you want to have a look at it and let me know what you think?
I haven't added a sample or description in the Readme yet.

I added a unit test for lora at #219 .
I'm adding some documentation and will release once I fix some build issue.


API Server quotes "unauthorized"

Please try to redo the coinbase-section of the account setup.
https://github.com/nicolindemann/coinbase-moneymoney#coinbase

Hey - somehow I am having the exact same issues. Played around several times with API settings and permissions but always get Unauthorized.
I am using the version I downloaded here https://moneymoney-app.com/extensions/ and Moneymoney Version 2.3.9 (Beta).
I also tried to use the version from Github, however it doesn't give me the option to chose Coinbase when trying to create a new account. Pls help <3


Screenshots out of date (again)

Hi @MGoedtel,
The reference in the last section to "Log Search tile" seems to be out of date - we have a "Logs" blade from the menu or a link to "View logs" on the "Overview" blade now I believe.
Just noting that, the query screen is a bit different now as well. Thanks!

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

ID: cfb49644-fb30-6357-708b-d2007fcab408
Version Independent ID: 3c6c3cac-e738-52c3-bf89-6476ba04e816
Content: Collect data about Azure Virtual Machines
Content Source: articles/azure-monitor/learn/quick-collect-azurevm.md
Service: log-analytics
GitHub Login: @MGoedtel
Microsoft Alias: magoedte

@dcbrown16 Thanks for bringing this to our attention! We've shared your feedback with the content owner for further review and update as appropriate.


concurrent map read/write fatal error after a few hours of operation

Runs for a few hours and gets a concurrent map read/write error.
burrow.log

@ehthayer this looks like the same thing as https://github.com/linkedin/Burrow/issues/169 there are technically two separate traces in that bug, so could be there are two issues. I'm building off of master fwiw.

	/home/ethayer/go/src/github.com/linkedin/Burrow/offsets_store.go:140 +0x35e
``` looked suspicious in the trace I saw.

Yeah, there's definitely some concurrency issues in a couple places. It's being fixed soon.

Resolved by 1.0 rewrite


map fields to strings

All functions involving some field selection should map fields in the header row to field names ie strings so field selection is consistently by field name everywhere and this won't get confused if objects other than strings are used as fields (as long as they implement str).

Resolved in v1.0


Update card image code to pull from a configured URL.

this is prep for switching to the CDN for card images.
There will be a bit more work to switch formats (jpg -> png) or to switch any sizes.

To double check, NRDB.card_image_url is already defined someplace in the javascript?

It is now in the layout twigfile.
On Mon, Apr 18, 2022, 10:43 AM Noah @.***> wrote:

To double check, NRDB.card_image_url is already defined someplace in the
javascript?
—
Reply to this email directly, view it on GitHub
https://github.com/NetrunnerDB/netrunnerdb/pull/619#issuecomment-1101510592,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AADA2ESIXNOSCKU35CZYXSTVFV7K5ANCNFSM5TV64XNA
.
You are receiving this because you authored the thread.Message ID:
@.***>

Ope, good catch.


fixed bug in namespace lookup breaking import aliases

Description
Fixed error in namespace resolution causing import aliases to break
Self Check:
Strike through any lines that are not applicable (~~line~~) then check the box

[ ] Attached issue to pull request
[x] Changelog entry
[x] Type annotations are present
[x] Code is clear and sufficiently documented
[x] No (preventable) type errors (check using make mypy or make mypy-diff)
[x] Sufficient test cases (reproduces the bug/tests the requested feature)
[x] Correct, in line with design
[ ] End user documentation is included or an issue is created for end-user documentation (add ref to issue here: )
[ ] If this PR fixes a race condition in the test suite, also push the fix to the relevant stable branche(s) (see test-fixes for more info)

Processing this pull request

Pull request rejected by merge tool. The tests for this branch did not succeed.

Processing this pull request

Merged into branches master, iso6 in d9c0b4f176dce18719a1c461e5570f15272b74c3


fix performance doc

we did a benchmark(not using ssd but seems not mater for this) and  Serializable read got the result:
average latency is 0.4ms but average QPS is only 2500
seems the doc made a mistake ,  because 0.4ms*2500 = 1s

This could probably stand to be updated in general. go 1.7's code generation is better than 1.6 and linearized reads are cheaper as of 3.1.

yes, the env may diff, but the test result(one client, one connection) 0.4ms * 7500 = 3s seems not make sense.

@sandflee the point I wanted to make is that if one number is bogus, it's better to rerun it instead of patching it over with a calculated value since now all the numbers are questionable.

superseded by #7994


Allow custom install path

Fixes: https://github.com/99xt/dynamodb-localhost/issues/22
This fixes the behavior of the localPath variable, and makes it possible to install dynamodb-local to an absolute path.
For the most part it implements the changes suggested in #22

I created an installable version of this at https://www.npmjs.com/package/@aneilbaboo/dynamodb-localhost

@aneilbaboo Thanks for your contribution. Much appreciated.

@aneilbaboo @mjzone
This PR changed the default location of install_path (https://github.com/99xt/dynamodb-localhost/blob/master/dynamodb/config.json#L4) from ./bin to /bin on Unix-like systems because /bin is recognized as an absolute path and path.join is not called.
Is this intended behavior?


EthStorage Devs Meeting #54 Agenda

Meeting Info

Oct 31, 2023, 10:00 UTC+8
Duration: 60 minutes
Meeting link
Anyone can comment on the agenda where they would like this to be discussed.

Agenda

Protocol/App/Research progress

4884 talk in Tintin and Hongkong
Code review
Support devnet-10
Downloader support multi-threading
Celestia scoping

EthStorage -- sync

Smoke Test and fix issues (https://github.com/ethstorage/es-node/pull/49 (fix issue https://github.com/ethstorage/es-node/issues/37), fix issue https://github.com/ethstorage/es-node/pull/39)
Performance test

benchmark: https://github.com/ethstorage/es-node/pull/2 update code.
run on multiple machines with mock l1 (https://github.com/ethstorage/es-node/pull/21)

Add profile： https://github.com/ethstorage/es-node/pull/56 （checkin）
Dashboard (next): https://github.com/ethstorage/es-node/issues/43 (debug and test it)

Prepare test data for the devnet network and optimize the data generation speed.

Segment optimization: https://docs.google.com/presentation/d/1RVUK1bYP7lVMDwPMddCucv3maUEqV0moYZFZcAYCneY/

Implement a brainfuck based zkVM https://github.com/dajuguan/zkvm_brainfuck -- Done
Iterate on Zprize https://github.com/ethstorage/ZPrize-23-Prize1/commit/a9cd7ce9046353c374809f39dbc3393c4d3bfc5e -- Done
Focus on continuation -- Ongoing

Help with EthStorage devnet 1
Set up 4844 devnet 10
Documentation
Celestia integration

proof generation on CUDA: completed feature of slicing on buffer
Halo2 series: 3/4 done of writing article
zkVM, memory continuation proof, at a glance

Recording: https://drive.google.com/file/d/1sdVtb5ghZRj4isIzYM_5mu3dfViWJQ_k/view?usp=sharing


addListener urlChangeEvent listener is not working

I'm encountering an issue where i need to listen to URL changes occurring after the webview is loaded, but the addListener urlChangeEvent doesn't seem to be executing. Despite implementing the listener, it doesn't respond to URL changes. Could you please provide guidance or suggest alternative approaches to effectively capture these URL changes ?
await InAppBrowser.open({ url: 'https://capgo.app' })
//Below code is working even the url gets changed
InAppBrowser.addListener("urlChangeEvent", (e: any) => {
console.log('event', e.url);
})

No, open use the native webview and so this cannot be implemented


[ZEPPELIN-394] Update cassandra-spark profiles to latest connector versions

Below is the version matrix. Updates are in bold

Maven profile
Spark Cassandra connector version

cassandra-spark-1.1
1.1.1

cassandra-spark-1.2
1.2.1

cassandra-spark-1.3
1.3.1

cassandra-spark-1.4
1.4.0

cassandra-spark-1.5
1.5.0-M2

Do you mind add some description about the profiles? for example README.md

Looks good to me.

Merge if there're no more discussions


No style for class="issue"

https://mediasession.spec.whatwg.org/#interrupting-a-media-session
Here the "The interruption may not come from another media session at all.  https://github.com/whatwg/mediasession/issues/100" bit has no styling at all.
Something like the style for class="note" would be nice.
CC @doomdavve

Ping @domenic @annevk, as this is a matter for their boilerplate's styling.

So we use class=XXX for issues within the WHATWG.

I was wondering about that...
Well, that just means no use of the Issue:  shorthand for producing issue paragraphs.  Or WHATWG can conform to Bikeshed's implicit styling decisions. Either one works for me.

There's no organization context available when you output the class? Shouldn't be too hard to make it a variable of sorts...

Hm, I suppose I could.

Okay, done, and I adjusted the WHATWG defaults to set the class to XXX.  Let me know if there are any problems.


fix a naive datetime for Finding.mitigated

**Note: DefectDojo is now on Python3 and Django 2.2. Please submit your pull requests to the 'python3_dev' branch as the 'dev' branch is only for bug fixes. Any PR's submitted to the 'dev' branch should also be converted to Python3 and submited to the 'python3_dev' branch.
When submitting a pull request, please make sure you have completed the following checklist:

[ ] Your code is flake8 compliant
[ ] If this is a new feature and not a bug fix, you've included the proper documentation in the ReadTheDocs documentation folder. https://github.com/DefectDojo/Documentation/tree/master/docs or provide feature documentation in the PR.
[ ] Model changes must include the necessary migrations in the dojo/dd_migrations folder.
[ ] Add applicable tests to the unit tests.

This merge request will fix the following Warning when mitigation performed by an api_v2 request:

Hey @legik thank you for the contribution. Would you please submit your pull request to the dev branch? It will be merged into the master branch upon the next stable release.


Support writing multi-harmonic phasors to OME-TIFF

Description
This PR proposes the following changes:

Add functions to write and read multi-harmonic phasor coordinates to OME-TIFF: phasor_to_ometiff and phasor_from_ometiff.
Remove outdated read_ometiff_phasor and write_ometiff_phasor functions.
Add "Store phasor coordinates" section to introduction tutorial.
Use mean, real, imag, phase, and modulation as coordinate names instead of dc, re, im, ph, md.
Improve documentation for io module.
Require tifffile >= 2024.8.24 for write_ometiff_phasor.

The main purpose of the new functions is to export phasor coordinates for reading via Bio-Formats into Fiji, Matlab, and other software. It is not meant as a long-term storage solution for the many limitations.
The format has the following limitations and characteristics:

The OME model has no dimension dedicated to representing phasor coordinates. Possible ways to work around are to store phasor coordinates as:

complex numbers: requires transposition, which is resource intensive. Not supported by many software, including Fiji (?).
TIFF samples: requires transposition. Samples are merged with channels in the OME model.
"Other" dimension Q: shows in Fiji as T, Z, or C. Fiji will not recognize QTZCYX images. This option is implemented.

The OME model has no predefined option to store frequencies or specify harmonics. The options are to store those metadata as:

StructuredAnnotations or ModuloAlong labels: not available in Fiji or tifffile. Requires parsing XML to extract.
separate one-pixel or line image series: This option is implemented.

OME-TIFF is an image format. Scalars and 1D data coordinate arrays are read back as 2D arrays.
The phasor coordinates, mean, real, and imag, are stored as separate OME image series.
Multi-harmonic phasor coordinates are transparently handled.
Phasor coordinates are stored as float32 (6 digits of precision) by default to maximize compatibility with Fiji and save storage space.
Images larger than (1024, 1024) are stored as (256, 256) tiles, datasets larger than 2 GB as BigTIFF, and datasets larger than 8 KB zlib-compressed.
The format does not allow to store phasor coordinates used for calibration. That would complicate the API. Use a separate file instead.
No metadata other than the fundamental frequency and harmonics are stored. It would be nice to be able to store at least a comment string in the OME annotations. This should first be implemented in tifffile.
The implementation and API are not suitable for handling images that do not comfortably fit in RAM. Currently a copy of all arrays is made in memory.
SimFCS will not be able to import the format. Should we add a phasor_to_simfcs_ref function later? How does SimFCS handle NaN? Is SimFCS still used?

For long term storage of phasor coordinates, other options may be better suited than OME-TIFF:

HDF5: More versatile than OME-TIFF. Supports any dimensions. Easier metadata handling. Easier to read from Matlab and other programming languages. See also Photon-HDF5.
OME-ZARR/NGFF: made for huge datasets. Ongoing work to support FLIM.

It might make sense to later move the phasor_to_ometiff and phasor_from_ometiff functions to the phasor module or main namespace (?)
Release note
Summarize the changes in the code block below to be included in the
release notes:
Support writing multi-harmonic phasors to OME-TIFF

Checklist

[x] The pull request title, summary, and description are concise.
[x] Related issues are linked in the description.
[x] New dependencies are explained.
[x] The source code and documentation can be distributed under the MIT license.
[x] The source code adheres to code standards.
[x] New classes, functions, and features are thoroughly tested.
[x] New, user-facing classes, functions, and features are documented.
[x] New features are covered in tutorials.
[x] No files other than source code, documentation, and project settings are added to the repository.

This is the "Bio-Formats Series Options" dialog that opens when dragging the file phasors.ome.tiff (written in the introductory tutorial) onto Fiji:

Hi @cgohlke, you read my mind! Last week I was working on the napari plugin that uses phasorpy and I came across to the problem of not being able to easily store and read multi harmonic images. One workaround I found was to expand de dimensions of the mean to match the real and imag before saving the image, but this was obviously not ideal, so I was going to discuss this with you in the next meeting or open a new issue.
This is great, I believe as you pointed out, using this has it's advantages and disadvantages, as everything. But for the moment I think this works great. It's good to also be able to store the frequency and harmonic information in the file.

SimFCS will not be able to import the format. Should we add a phasor_to_simfcs_ref function later? How does SimFCS handle NaN? Is SimFCS still used?

I think for now SimFCS is widely used because there are not so many available options, but eventually it will be less and less used. But I believe it would be nice to have a phasor_to_simfcs_ref since not all functionalities of SimFCS are available in PhasorPy and this will expand the options. Also, it would be nice to have this to compare with SimFCS results and validate our functions in some cases.

It might make sense to later move the phasor_to_ometiff and phasor_from_ometiff functions to the phasor module or main namespace (?)

This makes sense I think. Even more if they are named phasor_*_ometiff as it already matches the nomenclature for the phasor module. Also, in this case maybe the io module can be renamed? Since there will not be any output functions.

OME-ZARR/NGFF: made for huge datasets. Ongoing work to support FLIM.

This is a very interesting option. A couple of weeks ago, we were discussing this with @zoccoler and he suggested using OME-ZARR for several reasons, and he has been using it for his own packages. Maybe we can get some input on this from him and other community members.

it would be nice to have a phasor_to_simfcs_ref since not all functionalities of SimFCS are available in PhasorPy

OK, I will add phasor_*_simfcs_ref functions in another PR. The format only supports square images (and SimFCS prefers 256x256), so the export will produce many files in many cases.

suggested using OME-ZARR for several reasons

In my opinion, multi-file formats are not a good choice for simple use cases. It's good for cloud storage, out-of-core processing, and maybe for sharing with napari if they support it. Still, there is no format that has proper metadata support for storing the results of Fourier transform from FLIM.

Maybe we can get some input on this from him

Yes, I was thinking the same. Are you still in contact?

It might make sense to later move the phasor_to_ometiff and phasor_from_ometiff functions to the phasor module or main namespace (?)

This makes sense I think. Even more if they are named phasor_*_ometiff as it already matches the nomenclature for the phasor module. Also, in this case maybe the io module can be renamed? Since there will not be any output functions.

Two things: the file io functions depend on xarray, which should be defer-imported if the functions are moved to another module. io is a common namespace for file handling functions (e.g. scipy.io and skimage.io). I think we should keep it.

Hi @cgohlke! While working on the napari plugin I was thinking it would be good to have a flag in the exported 'OME-TIFF' to check if the file was calibrated or not, maybe something like the frequency and harmonic information. Do you think this is worth it or it messes the exported file?


✨ No date pre-selected

Hi,
Great plugin, thanks a lot !
Is it possible that there are no pre-selected dates (not today, no date at all) ?
The best thing would be that 'dd/MM/yyyy' or any string like a placeholder is on the input field.
Thanks

up


Upload in UI not working

Hi!
I am trying out Reposilite for my private repo as a replacement for Archiva, but I can't get it to accept artifacts uploaded through the UI. When I have clicked "upload" in the form after entering all info, the page simply reloads with an empty form. No status message, nothing (perhaps this is how it should look though). The problem is that nothing is added to the repository, and if I check the repository folder on the server it is empty too. The only thing I can see which indicates some kind of problem is this log in the browser console:
Form contains a file input, but is missing method=POST and enctype=multipart/form-data on the form.  The file will not be sent.
Reposilite version: 2.8.4, running in Docker using the image dzikoysk/reposilite
Browser: Firefox 80.0.1

Yeah, looks like a bug on a 2.8.x

2.8.5 has been released: https://github.com/dzikoysk/reposilite/releases/tag/2.8.5
You have to wait a couple of minutes for a docker image, its CI is kinda slow 😬

Works like a charm, thanks!


Spike: Stage an existing Docker image

We can speed up CI, by removing the buildpack tekton job from a large number of our tests. They would just stage an existing Docker image.
In the future, users can stage Docker images via epinio push.
See #485 also

I'm assuming you mean epinio push? 😄

Spike Investigation:
After understanding the push code and endpoints it hits, I think this is completely possible and can be done.
Push Process Overview
-> epinio push -> AppCreate API (Creates AppCRD) -> AppUpload API (Create gitea repo) -> AppStage API (Create tekton pipelineRun)
We have a separate endpoint API for AppCreate to have the functionality of controlling the app start. We can create an app and not assign a workload, but I feel this is the wrong split. The split should be in AppStage. The Run task of the tekton pipeline should have a separate endpoint (which is only for deploying the workload).
Proposed Push Process
-> epinio push -> AppCreate API (Creates AppCRD) -> AppUpload API (Create gitea repo) -> AppStage API (Create tekton pipelineRun clone & stage) -> AppRun API (Create TaskRun run)

Can you create a minimal implementation to show if CI gets faster?


GUI refuses to connect even with the game opened.

Yeah i have no idea whats happening. I swear the game is open but the GUI still can't connect. Even restarting the game & the GUI, its the same thing. Whats happening? Please fix this ASAP.

I have the same problem, it seems that MaidStatus.Feeling is not loaded and causes an infinite wait

Updating to 1.45.0 fixed it for me, I was on 1.44.
Here are the instructions to update the game:
https://wiki.anime-sharing.com/hgames/index.php?title=Custom_Order_Maid_3D_2/Technical_Help#Updating_the_game_.28Japanese_version.29

Greetings!
Please provide more info: what game version are you running, what Maid Fiddler version? Any errors in the console?
As it is, the Maid Fiddler <IP_ADDRESS> is known to work with COM 1.45 (JP) and 1.04.2 (ENG).
Closing this issue because of insufficient information. Please create a new issue using the proper template.


Cannot get font working properly in urxvt (rxvt-unicode)

I cannot get these font-logos to display in rxvt-unicode or the gnome-terminal. Not sure if it is something wrong with my config or just an incompatibility that I am unaware of. The font-logos do show up under fc-list
Here is my .Xresources relevant config:
URxvt.font: xft:Hack:pixelsize=20:style=bold, \
            xft:font\\-logos:pixelsize=12:style=logos, \
            xft:Font\ Awesome\ 5\ Free\ Regular:pixelsize=12, \
            xft:Font\ Awesome\ 5\ Free\ Solid:pixelsize=12, \
            xft:Font\ Awesome\ 5\ Brands:pixelsize=12, \
            xft:Fontawesome:pixelsize=12

Per arch-wiki "Note: If there is a hyphen(-) in an Xft font name, it must be escaped with backslash() twice. It's different from the usage of urxvt -fn option and the result that fc-list returns, where backslash present only once"
Although I am running on ubuntu 20.04, i believe that part applies to me as well.
I can get all the other fonts listed to properly display in the urxvt terminal output. I cannot get the font-logos to work in urxvt, although I can get font-logos to work in polybar with the following setting:
font-5=font\-logos:size=12;3
and then can get the font-logos to display in polybar modules.
Please let me know if there is any information or screenshots that I need to append to this issue post to properly figure out the culprit or issue here and sorry if this is not the right place to create this post. I'm not sure where else to go with this because I seem to only be having a problem with this font in urxvt.

Also having the same issue in kitty (although glyphs look much better in general in kitty opposed to urxvt).

urxvt's bad with displaying glyphs , try the fonts on alacritty or st . Btw how did you copy those fonts? I couldnt get em working on terminal.

urxvt's bad with displaying glyphs , try the fonts on alacritty or st . Btw how did you copy those fonts? I couldnt get em working on terminal.

@Rblock919 is there any cheatsheet for this font, something like nerdfonts cheatsheet ? Im unable to copy paste it in my terminal .

@Rblock919 is there any cheatsheet for this font, something like nerdfonts cheatsheet ? Im unable to copy paste it in my terminal .

Has anyone found something like this yet?

@Rblock919 is there any cheatsheet for this font, something like nerdfonts cheatsheet ? Im unable to copy paste it in my terminal .

Has anyone found something like this yet?

nope :(

You should be able to just copy and past the icon from the table on the font page (readme.MD).
 We include the svgs directly in the readme but instead we should import our own font and reference that by codepoint. :thinking:
Thanks for reporting!

i no longer need it! because nerdfonts already has most of the font-logo icons :D

After some research I think it is impossible to have the icons copy and pastable on a README.md page.
So the only solution is to revive the gh-pages.
Checking urxvt compatibility now.

Can not reproduce on Kitty, works ok...
Started kitty --debug-font-fallback

Can not reproduce on urxvt, works ok...

Just typed shift + ctrl + U F 3 5 0 enter


Metadata API - Document Component's capabilities related information

What content needs to be created or modified?

Modify docs to have newly added components capabilities information
Describe the solution you'd like

Where should the new material be placed?

The associated pull request from dapr/dapr, dapr/components-contrib, or other Dapr code repos

https://github.com/dapr/dapr/pull/4696
Additional context

The metadata API is not well documented today and is hidden to most developers. Adding to this reference https://docs.dapr.io/reference/api/metadata_api/ is necessary, however writing a usage article would be preferrable to include examples of why this is useful.

The metadata API is not well documented today and is hidden to most developers. Adding to this reference https://docs.dapr.io/reference/api/metadata_api/ is necessary, however writing a usage article would be preferrable to include examples of why this is useful.

@msfussell Where should we put a reference for Metadata API.  Do we have any reference for other APIs at some place else?

Leaving this open for v1.8 since I am going to update a diagram to show the metadata API on the side car

@pravinpushkar - I updated the diagram, but this now needs a new Code and docs PR since this is invalid now.
Pub/Sub | TTL

@msfussell We need a new doc PR for the changes done for Pub/Sub. I will create a new PR and will link to this issue only.

Resolved


 component doesn't use the stringifyParams function from the route

Describe the bug
The stringifyParams and parseParams aren't being called correctly.
Your Example Website or App
https://stackblitz.com/edit/tanstack-router-16ynx2?file=src/main.tsx
Steps to Reproduce the Bug or Issue
In the repro, I've used base64 encoding on for the dashboard -> invoices ->invoiceIds.
Repro Options:

Navigate to /dashboard/invoices/MQ== and watch the data and component flash on-screen and then disappear.
Navigate to /dashboard/invoices and try to click on any of the invoice links.

Expected behavior
Exp 1: The  generated should have the path params base64 stringified using the functions provided.
expected href: /dashboard/invoices/MQ==

received href: /dashboard/invoices/1

Exp 2: Navigating to a path (via the browser) that expects an encoded string works for a second, then flashes and the component no longer renders.
navigate to: /dashboard/invoices/MQ==

expected:
  path params to be decoded and component to render.
  URL remains as /dashboard/invoices/MQ==

received:
  path params gets decoded and component renders.
  then after a flash...
  component disappears and the URL is rewritten to /dashboard/invoices/1.

Screenshots or Videos
No response
Platform

OS: macOS
Browser: Chrome
Version: 0.0.1-beta.53

Additional context
No response

Debugged on my-end on beta-68.
Usecase: base64 path params.
The stringifyParams function in the Route definition is NOT called when creating links using the <Link /> component.
This is not the case when using the useNavigate, it WORKS when using this hook.

Example config:
const rootRoute = new RootRoute({ ... });
const indexRoute = new Route({ getParentRoute: () => rootRoute, path: '/' });
const invoicesRoute = new Route({ getParentRoute: () => rootRoute, path: 'invoices' });

const invoiceRoute = new Route({ getParentRoute: () => invoicesRoute, path: '$invoiceId',
  parseParams: (params) => ({ invoiceId: base64_decode(params.invoiceId) }), // this works fine in the actual route
  stringifyParams: (params) => ({ invoiceId: base64_encode(params.invoiceId) }) // <- doesn't get run for <Link />s
 });

In the config above, all links/navigations in the app to /invoices/$invoiceId should have the invoiceId base64 encoded.

Given the invoiceId of 123, which when base64 encoded becomes MTIz, the following link/path (href) should be generated when using a <Link /> component.

Expected: /invoices/MTIz
Received: /invoices/123.

Snippet:
<Link to={invoiceRoute.id} params={{ invoiceId: '123' }} />


[HPO][Scheduler] Add get_best_task_id

Sometimes, we will want to load the weights of the best model searched via HPO. This is similar to the get_best_logdir option in ray/tune (See https://docs.ray.io/en/latest/tune/tutorials/tune-tutorial.html#tune-tutorial).
Thus, I added this get_best_task_id method to FIFOScheduler.

Job PR-566-5 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-566/5/index.html

Job PR-566-6 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-566/6/index.html


fix(extras/lang/python): Add nvim-treesitter as dependency of neotest in extras/lang/python.lua

neotest couldn't find any python tests
so added nvim-treesitter as a dependency and it worked well

I'm not exactly sure why this is needed, but it seems to be indeed the solution for Neovim stable. In Neovim nightly that I use, it worked fine without the treesitter dependency. As discussed in #1856 I didn't observe the problem initially because I was using nightly and I only discovered it in the end by chance.

Strange though. Treesitter is loaded on VeryLazy. How could there be a difference between nightly and 0.9 in that regard?

@abeldekat Would you mind trying it out to see if you can confirm? Although I also used a fresh starter template to make sure nothing of my personal config might give different results.

So, users will have to wait for Neovim v10 stable release or will it get taken care of in 0.9.5 if there's such a release? I'm guessing nightly has vim.treesitter latest API changes and doesn't have this problem?

@dpetka2001, I have no idea. I don't understand why adding nvim-treesitter as a dep fixes the issue in 0.9.4, as treesitter is loaded before I invoke the test.

on 0.9.4 this works as well:
    "nvim-neotest/neotest",
    tag = "v3.4.7",

Yes, they did mention that the PR linked in your comment was going to take place from neotest v4 onwards, so I'd guess pinning neotest to an older version prior to v4 would make sense. Maybe Folke could pin neotest to this version for Neovim stable like he had done in the past for telescope for users with Neovim 0.8?

Hi. i don't know what to do with this PR
should I just leave it or update this commit to be like below?
or maybe should i close it?
    "nvim-neotest/neotest",
    tag = "v3.4.7",

Hello @ohseunghyeon,
I think we should wait for Folke to decide.
Please allow me to summarize my thoughts:
Relevant:
neotest PR
neotest issue
The PR at hand adds nvim-treesitter as a dependency to neotest, otherwise tests don't run on neovim 0.9.4. Alternatively, it's also possible to pin neotest to v3.4.7.
The change is not necessary for Neovim nightly.
I think it's very strange that on Neovim 0.9.4 the tests won't run, unless the dependency on nvim-treesitter is made explicit.
The neotest plugin is loaded when pressing for example leader t t.
However, nvim-treesitter should have already been loaded, suggesting something is not quite right when loading nvim-treesitter.
I dug a little deeper into that loading:
  {
    "nvim-treesitter/nvim-treesitter",
    version = false, -- last release is way too old and doesn't work on Windows
    build = ":TSUpdate",
    event = { "LazyFile", "VeryLazy" },
    -- truncated...
   }

change: event = function() return { "VimEnter" } end -> the tests run fine
add: lazy = false -> the tests run fine

@folke: Is the handling of LazyFile or VeryLazy different in 0.9.4, as opposed to nightly?
Best regards!

I'll look into it.
With the neotest change, I can only assume that it would fail id nvim-treesitter was not yet loaded when neotest loads, since the queries would not have been on the rtp yet.
But nvim-treesitter should have been loaded. Will see what's happening here

Was able to properly fix this for all plugins and related issues (like headlines.nvim).
See the commit for more details.

That's great! Thanks!

@folke,
It works like a charm, but I don't understand why...)
The neotest plugin is only activated on keypress. The UI shows that nvim-treesitter is loaded before I activate the tests.
When I load nvim-treesitter eagerly(lazy = false), the tests ran fine. Thus, it must have also loaded the query-predicates.
On event = {"LazyFile", "VeryLazy"} no tests where found. You fixed this by eagerly loading nvim-treesitter.query_predicates, using init.
I would like to understand: Why does it not load those nvim-treesitter.query_predicates on for example VeryLazy? A timing issue is not likely, as I wait a few seconds before executing the tests.

The python neotest adapter loads on filetype python, and that will load neotest as well.
The problem is mostly when opening a python file with nvim foo.py.
Due to LazyFile, the file will be rendered as quickly as possible and delay loading the plugins with event=LazyFile.
Since that neotest adpater has ft=py, it will load anyway since that's not on LazyFile. So it will load, then create it's queries and since treesitter has not yet been loaded, it won't have any queries.
This all used to work when they still did require("nvim-treesitter") in their code.
Since that was removed, this is no longer the case. Same thing with some other plugins like headlines.nvim.
Tbh, those plugins should also just be fixed in that they should not assume all queries are on the rtp when their setup function is called.
See headlines.nvim for example: https://github.com/lukas-reineke/headlines.nvim/blob/master/lua/headlines/init.lua#L20
Just requiring the init module will set the queries forever. If some queries become available after that on the rtp, they will never be used.

nvim-treesitter should also really be split in two separate plugins (that work is underway, but takes a while):

treesitter-queries: simple plugin that puts queries on the rtp, allows building grammers and adds custom directives. Basically what I'm doing now in the init() function
treesitter-modules: the additional functionality it currently provides like move etc

Thanks for the explanation!
I think I now understand the core of the problem, at least regarding headlines.nvim.

The python neotest adapter loads on filetype python, and that will load neotest as well

I must be overlooking something. When I open a python file, neotest and the python adapter are not loaded... In the code of the adapter I do not see ft=py.

That's indeed odd. I didn't actually look into detail in the python issue, since I assumed it was caused by the same problem.
Hmm, maybe because some other code first gets the lang before nvim-treesitter was loaded? And NEovim itself doesn't get it again after adding nvim-treesitter to the rtp?
https://github.com/nvim-neotest/neotest/commit/b04332c2a07fbc13f4162b4b3f1820b433c428e7#diff-e59a70a3a602ce80307634f6bc6d3d6b26425eadba94eae59e3abfa946471062L117

That's possible I think. I will try without using any other plugins than strictly necessary.
Also, perhaps worth noting:
When I modify lazy.core.util, the verylazy method, to use VimEnter instead of UIEnter, the tests also ran...
        vim.api.nvim_create_autocmd("VimEnter", {
          once = true,
          callback = function()
            _load()
          end,
        })

Using the latest lazy.nvim and LazyVim, only loading the following plugins:
  Loaded (16)
    ● lazy.nvim 8.47ms  init.lua
    ● lazyflex.nvim 0.05ms  start
    ● LazyVim 3.43ms  start
    ● mason-lspconfig.nvim 0.07ms  nvim-lspconfig
    ● mason.nvim 10.51ms  nvim-lspconfig
    ● neoconf.nvim 0.17ms  nvim-lspconfig
    ● neodev.nvim 1.86ms  nvim-lspconfig
    ● neotest 11.49ms  <leader>tt
    ● neotest-python 0.65ms  neotest
    ● nvim-lspconfig 20.32ms  LazyFile
    ● nvim-treesitter 29.35ms  LazyFile
    ● nvim-treesitter-context 16.9ms  LazyFile
    ● nvim-treesitter-textobjects 1.72ms  nvim-treesitter
    ● nvim-ts-autotag 2.11ms  LazyFile
    ● plenary.nvim 0.28ms 󰢱 plenary.path  neotest
    ● tokyonight.nvim 1.07ms colorscheme tokyonight  LazyVim

... and the tests will not run without the new init property on the treesitter spec.
However, when I change lazy.nvim:
  vim.api.nvim_create_autocmd("User", {
    pattern = "LazyDone",
    once = true,
    callback = function()
      if vim.v.vim_did_enter == 1 then
        _load()
      else
        vim.api.nvim_create_autocmd("VimEnter", {
          once = true,
          callback = function()
            _load()
          end,
        })
      end
    end,
  })
end

... when using VimEnter instead of UIEnter, the tests run without the init part of the treesitter spec.

When reverting the following change in neotest's subprocess.lua, the tests run without needing the init part of the treesitter spec:
Add:
nio.fn.rpcrequest(child_chan, "nvim_exec_lua", "require('nvim-treesitter')", {})

Right! Now I understand. Neotest runs the tests in a new Neovim instance and nvim-treesitter would not have been loaded there automatically. That's why it failed.

Probably best to report this, since a lot of users (non LazyVim) may have the same issue when they lazy-load nvim-treesitter

I also think that the core of the problem is the new Neovim instance.
However, nvim-treesitter is loaded automatically, when its spec is changed into:

lazy = false
or: event = "VimEnter"

It also loads when changing the implementation of VeryLazy itself, using VimEnter instead of UIEnter.
Perhaps this situation "uncovers" a hidden limitation in the current VeryLazy and LazyFile implementation . Is is possible that UIEnter never fires in the new Neovim instance and nvim-treesitter is not loaded because of that?

Again it will load nvim-treesitter, but it will load it too late. neotest expects it to be loaded when Neovim starts so on VimEnter. (Neotest loads itself on vimenter when in a running test) The tests are not running in your current Neovim instance, but in a new one. See that code that you linked to.
So no, this is not a limitation of lazy.
And yes, it works on nightly because it ships queries for python that will be on the rtp from the start.

Again it will load nvim-treesitter, but it will load it too late. neotest expects it to be loaded when Neovim starts so on VimEnter. (Neotest loads itself on vimenter when in a running test)

I understand!

Probably best to report this, since a lot of users (non LazyVim) may have the same issue when they lazy-load nvim-treesitter

Folke, would you be willing to do so?
Best regards and many thanks for answering my questions!

@folke,
If you agree, I am planning to create an issue for neotest later today.

sure, go for it. Or maybe just add a comment to this issue here https://github.com/nvim-neotest/neotest/issues/303

done.


Update contribution guide, add code of conduct

@jshcodes this PR converts the existing code of conduct markdown into an actual webpage, which can be referenced in the future (e.g. will become https://opensource.crowdstrike.com/code-of-conduct/). Modified by adding an escalation path/human name people can reach out to.

@redhatrises this PR also restructures the contributing page a little. Based it off https://opensource.com/life/16/3/contributor-guidelines-template-and-tips

LGTM

@redhatrises this is ready for re-review

LGTM


[Bug]: Parameter Set "Mohtat2020" have Initial Condition Problem

PyBaMM Version
22.11.1+22.11.1
Python Version
3.8(Online Colab)+3.9(Local VSCode)
Describe the bug
According to Pybamm Document (https://pybamm.readthedocs.io/en/latest/source/parameters/parameter_sets.html), there are 14  parameter sets for use (['Ai2020', 'Chen2020', 'Chen2020_composite', 'ECM_Example', 'Ecker2015', 'Marquis2019', 'Mohtat2020', 'NCA_Kim2011', 'OKane2022', 'ORegan2022', 'Prada2013', 'Ramadass2004', 'Sulzer2019', 'Xu2019']), while 12 of them are for DFN model (['Ai2020', 'Chen2020', 'Chen2020_composite', 'Ecker2015', 'Marquis2019', 'Mohtat2020', 'NCA_Kim2011', 'OKane2022', 'ORegan2022', 'Prada2013', 'Ramadass2004', 'Xu2019']), in which only 9 of them can work well in my program.
Unfortunately, the set 'Mohtat2020' can not work well, as to it comes to the model event "['Minimum voltage'] are non-positive at initial conditions". I have changed the parameter 'Current function [A]' to other values rather than the default 5A, but the event still happened.
Please tell me how to deal with this problem. Thank you very much!
Steps to Reproduce
Python Code:
import pybamm
parameter_values = pybamm.ParameterValues("Mohtat2020")
model = pybamm.lithium_ion.DFN()
sim = pybamm.Simulation(model, parameter_values=parameter_values)
sim.solve([0, 3600])
sim.plot()
Relevant log output
Online Colab log output:
---------------------------------------------------------------------------
SolverError                               Traceback (most recent call last)
<ipython-input-14-c8081af8ccdc> in <module>
      1 model = pybamm.lithium_ion.DFN()
      2 sim = pybamm.Simulation(model, parameter_values=parameter_values)
----> 3 sim.solve([0, 3600])
      4 sim.plot()

2 frames
/usr/local/lib/python3.8/dist-packages/pybamm/simulation.py in solve(self, t_eval, solver, check_model, save_at_cycles, calc_esoh, starting_solution, initial_soc, callbacks, **kwargs)
    615                         )
    616
--> 617             self._solution = solver.solve(self.built_model, t_eval, **kwargs)
    618
    619         elif self.operating_mode == "with experiment":

/usr/local/lib/python3.8/dist-packages/pybamm/solvers/base_solver.py in solve(self, model, t_eval, external_variables, inputs, initial_conditions, nproc, calculate_sensitivities)
    841
    842         # Check initial conditions don't violate events
--> 843         self._check_events_with_initial_conditions(
    844             t_eval_dimensionless, model, ext_and_inputs_list[0]
    845         )

/usr/local/lib/python3.8/dist-packages/pybamm/solvers/base_solver.py in _check_events_with_initial_conditions(self, t_eval, model, inputs_dict)
   1058             idxs = np.where(events_eval < 0)[0]
   1059             event_names = [termination_events[idx].name for idx in idxs]
-> 1060             raise pybamm.SolverError(
   1061                 f"Events {event_names} are non-positive at initial conditions"
   1062             )

SolverError: Events ['Minimum voltage'] are non-positive at initial conditions

Local VSCode log output:
Traceback (most recent call last):
  File "d:\WPS\3-毕业设计\4-代码\1-敏感度分析\param_set_debug.py", line 6, in <module>
    sim.solve([0, 3600])
  File "C:\Users\MGY\AppData\Local\Programs\Python\Python39\lib\site-packages\pybamm\simulation.py", line 617, in solve
    self._solution = solver.solve(self.built_model, t_eval, **kwargs)
  File "C:\Users\MGY\AppData\Local\Programs\Python\Python39\lib\site-packages\pybamm\solvers\base_solver.py", line 843, in solve
    self._check_events_with_initial_conditions(
  File "C:\Users\MGY\AppData\Local\Programs\Python\Python39\lib\site-packages\pybamm\solvers\base_solver.py", line 1060, in _check_events_with_initial_conditions
    raise pybamm.SolverError(
pybamm.expression_tree.exceptions.SolverError: Events ['Minimum voltage'] are non-positive at initial conditions

I find that I have used the wrong model.
This parameter set is for MPMe model according to the reference.
However, the MPM model still can not work well using this parameter set, as the set miss the item "Negative area-weighted particle-size distribution [m-1]".
Log files:
KeyError: "'Negative area-weighted particle-size distribution [m-1]' not found. Best matches are ['Negative particle radius [m]', 'Negative electrode diffusivity [m2.s-1]', 'Negative current collector conductivity [S.m-1]']"
Item 'Negative particle radius [m]' equals to 2.5e-06.
However, in the original reference, it is indeed provided in the form of distribution function, thus there are 10% / 22% / 30% / 25% / 13% particles , whose radius equal to 1.5e-06 / 2.0e-06 / 2.5e-06 / 3.0e-06 / 3.7e-06 m.
The parameter set may need to be adjusted.

First post: For the Mohtat2020 parameter set you have to start with a charge since the parameters are given for 0% SOC. We are working on standardizing the parameter sets to all start at 100% SOC.
Second post: indeed, the Mohtat2020 parameter set comes from an MPMe paper, but it still works with DFN. To add the relevant parameters for MPM to any parameter set, do
parameter_values = pybamm.get_size_distribution_parameters(parameter_values)

First post:
100% SOC Parameter value solved by sim.build(initial_soc=1) for Mohtat2020
"Initial concentration in negative electrode [mol.m-3]": 23956.1769437291,
"Initial concentration in positive electrode [mol.m-3]": 1186.8414661132,
Maybe helpful for developers.


Make the region of interest dynamic.

Firstly, create the polygon and the region of interest dynamic.
More specifically, the polygon should keep changing with the lane width and the road ahead as they are not always constant.
Making a dynamically changing polygon would make the algorithm work on different sized roads.

Hello @akshitagupta15june, I want to work on this issue, please assign me this issue. Thank you :)

Hello @akshitagupta15june, I want to work on this issue, please assign me this issue. Thank you :)

ok

ok


Implementation of UDP TX

UDP implementation:

TransportDelegate & TransportImp.
Defined udp::IMedia, udp::ITxSocket & upd::IRxSocket protocols.
Implementation of all 3 TX sessions.

Fixed various Sonar issues (after switching to correct "libcyphal" quality profile at Sonar cloud).
Increased CAN-related code coverage to 100% (files, lines, functions & branches!).
A bit less of code duplication (f.e. libcyphal::detail::UniquePtrSpec helper).
Simplifying "swapping" behavior by using std::exchange.

Here is code coverage. Note that low (red) coverage at RX is currently expected - will be addressed by near future next PRs.

@thirtytwobits Scott, how is PR overall? Aproveable? ;)


[FEATURE] Add beginner category

[FEATURE] Add beginner category so new developers are welcomed with snippets that are easier to understand.
Description
We have over 200 snippets on our website. Yes, they're very useful in pretty much every situation! However, when a user visits our site he is welcomed with ary , call, collectInto snippets. They're very informative and useful but beginners won't find them friendly? - they might just debounce of the website and won't give 30secondsofcode another chance. Why don't we show some interesting and easy to understand snippets first or simply mark few snippets as beginner friendly?
Possible Solution
I suggest that we should implement beginner tags in our tag database and show those snippets first when someone visits the website. That way we are definitely going to help new developers learn faster and stick to using 30secondsofcode.
What is your opinion on this? Should we do such thing?

I agree that we should approach this a bit differently than we have in the past. However, recategorizing the snippets in beginner and advanced etc is only half a solution. I was actually thinking of a deeper overhaul of the website:
My suggestion for the website

Create a clean and lean landing page, so that people can read a short description of the project and what it has to offer. On the same page, we can add a snippet of the day section, built nightly from the cron job, that will pick a random snippet to feature daily. That way we can keep visitiors interested for longer and help people discover interesting snippets.
Add some proper navigation and separate the content into pages. Each major tag that we currently have will be its own page, so that we can keep load times shorter. However, the main navigation sidebar should remain the same as it is, allowing for the website to feel as a single entity.
Add a page for beginners that is featured promimently in the landing page links. Curate the beginner-friendly snippets a bit more carefully and add some more content to that page, such as extra links to documentation and learning resources to encourage people to start learning from our snippet database.
Add a page for the archived snippets, just so that people can more easily find them outside of the repo.
Add pages similar to the beginner page for certain categories of tasks (not sure if viable/applicable). For example, we could add a page with snippets for working with a specific kind of project. My reasoning for this is that we can curate single pages with a main goal more carefully and add more links and resources to them.

In short, the current website is something I put together very quickly and then we just incrementally improved it until it sort of worked and left it there. We really should work on improving it and making it more usable, while improving our branding and overall visibility. After all, we stil have the README if we want everything displayed as-is without any changes or extra features (and it serves a great purpose as-is).
Opinions are, as always, appreciated. Let's figure out the best approach to this and start building it.

On the same page, we can add a snippet of the day section, built nightly from the cron job, that will pick a random snippet to feature daily

Can we have a voting system which decides snippet of the day? Users can vote for the snippets that helped them. We can even have a login feature for a personalized experience.

Without any backend, neither of these things is possible, @kriadmin. For the highest exposure of snippets we should use a random rotation and have 4-5 snippets each day, so that users who visit the page multiple times a day or refresh can see a few different snippets. That way it should take about 2 months to run through all of them and they will all be featured at one time or another.

maybe a multi-tag system?
In the left hand-menu underneath the search bar it would be nice if there was a grouping of three buttons that switched the order/categorization of the snippets

difficulty (default) -> rearranges snippets by alphabetic categorized under Beginner / intermediate / advanced
category -> rearranges snippets into current categories
a-z -> rearrange the snippets alphabetically like it's sesame street
Both the order of snippets in main viewport and menu should toggle/rearrange by selection

@Chalarangelo @kriadmin That would definitely require a backend which is not urgent right now. Something similar was suggested in 30 seconds of CSS and we delayed the idea a bit.
Right now I think the best solution is what @Chalarangelo suggested. We should discuss the details on Gitter these days. I am free for few days; @Chalarangelo when do you want us to start this? Tomorrow?

I also agree with @Chalarangelo 's ideas.

I think we should probably update archived snippets then as Academic. At that point we can go into heavier detail about EXISTING concepts and unroll some snippets for longer discussion and have it be more of a "learn for the sake of learning" section than the snippets, which are "cool tricks and fast tips".
After all that'd be a great place to put in something like a server side event channel system with subscribers that can be used to create distributed messaging systems with cascading messages. 100 lines of code, and it's a feature a LOT of people would love

@skatcat31 I would love to see that. Few principles that take more than 30 seconds to understand but are used in modern workflows.

For clarity and transparency, here's the list of beginner snippets that we will be featuring in the beginner page:

everyNth
filterNonUnique
last
maxN
minN
nthElement
sample
similarity
tail
currentURL
hasClass
getMeridiemSuffixOfInteger
factorial
fibonacci
gcd
isDivisible
isEven
isPrime
lcm
randomIntegerInRange
sum
reverseString
truncateString

Special thanks to @fejes713 for hand-picking these.

@Chalarangelo List could be improved, it requires nearly no effort to update it with the newest web.js script.

@fejes713 Yep, we could alter the list of beginner snippets anytime. The fact that it can be customized with nearly no effort is a big advantage, as beginners looking to make their first PR could actually tell us which snippets they find most useful. 😉

Resolved in #642


Feature Request: add support for credentials to be passed to the source and destination

The credentials would be used for the docker login so that external registries could be accessed by CodeBuild.

Think I just came across this (unless I'm missing some other way to solve it?)
I was hoping to build and deploy a Dockerfile that starts:
ARG BASE_IMAGE
FROM ${BASE_IMAGE}

...Where BASE_IMAGE is a SageMaker DLC image URI: So is hosted elsewhere in an AWS-managed ECR account that needs a docker login.
For what it's worth, since a Dockerfile may have multiple FROM statements, I guess it might be necessary to support multiple source credentials?

@athewsey I may be misunderstanding what you are trying to do, but I am not sure this construct can help you build and run the image in this way. Since this construct moves around pre-existing images in ECR, is the image your Dockerfile defines already in ECR?
If it is, and you are getting errors using this construct, would you be able to provide the code you are attempting to deploy and the results of the CodeBuild job? Thank you!


Landscape Mode not supported on iPad

Description
Seams like Landscape mode on iPad is not supported on the latest Beta
Expected Behavior
The ios Application is capable to adjust the display and the full layout when the device enters Landscape Mode (rotation)
Possible Fix
Add landscape mode support
Steps to Reproduce
Rotate ipad and check if the display switch to landscape mode
Context
It does not affect the actual functionality of the application, but it is kind of annoying to rotate back the device, since landscape mode is not supported.
Your Environment

Zap version: Latest Beta Version
Operating System and version: ios 13

Sorry Wrong repo :-/


ListAccount is forbidden randomly

Sometimes the request to list the account gives a forbidden response after the user tries to list their own account
Note this issue only occurs randomly, not every time
❯ curl https://localhost:9200/ocs/v1.php/cloud/users/einstein -u einstein:relativity -k | xmllint --format -
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   296  100   296    0     0   4417      0 --:--:-- --:--:-- --:--:--  4417
<?xml version="1.0" encoding="UTF-8"?>
<ocs>
  <meta>
    <status>error</status>
    <statuscode>996</statuscode>
    <message>{"id":"com.owncloud.api.accounts","code":403,"detail":"no permission for ListAccounts","status":"Forbidden"}</message>
  </meta>
</ocs>

This issue gets fixed after restarting the server
❯ curl https://localhost:9200/ocs/v1.php/cloud/users/einstein -u einstein:relativity -k | xmllint --format -
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   538  100   538    0     0   1368      0 --:--:-- --:--:-- --:--:--  1365
<?xml version="1.0" encoding="UTF-8"?>
<ocs>
  <meta>
    <status>ok</status>
    <statuscode>100</statuscode>
    <message>OK</message>
  </meta>
  <data>
    <enabled>true</enabled>
    <id>4c510ada-c86b-4815-8820-42cdf82c3d51</id>
    <display-name>Albert Einstein</display-name>
    <displayname>Albert Einstein</displayname>
<EMAIL_ADDRESS>    <quota>
      <free>2840756224000</free>
      <used>5059416668</used>
      <total>2845815640668</total>
      <relative>0.18</relative>
      <definition>default</definition>
    </quota>
    <uidnumber>20000</uidnumber>
    <gidnumber>30000</gidnumber>
  </data>
</ocs>

Server logs when failing
2020-11-09T13:41:32+05:45 WRN basic auth enabled, use only for testing or development service=proxy
2020-11-09T13:41:32+05:45 INF access token is already provided pkg=rhttp service=storage traceid=de4e04e8664044e753bee810fc080393
2020-11-09T13:41:32+05:45 INF http end="09/Nov/2020:13:41:32 +0545" host=<IP_ADDRESS> method=GET pkg=rhttp proto=HTTP/1.1 service=storage size=36 start="09/Nov/2020:13:41:32 +0545" status=200 time_ns=291798 traceid=de4e04e8664044e753bee810fc080393 uri=/data/index.cs3/unique.github.com.owncloud.ocis.accounts.pkg.proto.v0.Account.OnPremisesSamAccountName/einstein url=/data/index.cs3/unique.github.com.owncloud.ocis.accounts.pkg.proto.v0.Account.OnPremisesSamAccountName/einstein
2020-11-09T13:41:32+05:45 INF access token is already provided pkg=rhttp service=storage traceid=67f8e54f88924577399187af3c9395f0
2020-11-09T13:41:32+05:45 INF http end="09/Nov/2020:13:41:32 +0545" host=<IP_ADDRESS> method=GET pkg=rhttp proto=HTTP/1.1 service=storage size=584 start="09/Nov/2020:13:41:32 +0545" status=200 time_ns=245901 traceid=67f8e54f88924577399187af3c9395f0 uri=/data/accounts/4c510ada-c86b-4815-8820-42cdf82c3d51 url=/data/accounts/4c510ada-c86b-4815-8820-42cdf82c3d51
2020-11-09T13:41:32+05:45 INF access token is already provided pkg=rhttp service=storage traceid=feb094445c9ecf0ad92fa9d0333a9a7b
2020-11-09T13:41:32+05:45 INF http end="09/Nov/2020:13:41:32 +0545" host=<IP_ADDRESS> method=GET pkg=rhttp proto=HTTP/1.1 service=storage size=584 start="09/Nov/2020:13:41:32 +0545" status=200 time_ns=177808 traceid=feb094445c9ecf0ad92fa9d0333a9a7b uri=/data/accounts/4c510ada-c86b-4815-8820-42cdf82c3d51 url=/data/accounts/4c510ada-c86b-4815-8820-42cdf82c3d51
2020-11-09T13:41:32+05:45 INF access token is already provided pkg=rhttp service=storage traceid=4107ad4b69f385429b7001bd60b0bdf2
2020-11-09T13:41:32+05:45 INF http end="09/Nov/2020:13:41:32 +0545" host=<IP_ADDRESS> method=GET pkg=rhttp proto=HTTP/1.1 service=storage size=326 start="09/Nov/2020:13:41:32 +0545" status=200 time_ns=134727 traceid=4107ad4b69f385429b7001bd60b0bdf2 uri=/data/groups/509a9dcd-bb37-4f4f-a01a-19dca27d9cfa url=/data/groups/509a9dcd-bb37-4f4f-a01a-19dca27d9cfa
2020-11-09T13:41:32+05:45 INF access token is already provided pkg=rhttp service=storage traceid=da7a9eaf3b178a1c7ad61e699322f175
2020-11-09T13:41:32+05:45 INF http end="09/Nov/2020:13:41:32 +0545" host=<IP_ADDRESS> method=GET pkg=rhttp proto=HTTP/1.1 service=storage size=198 start="09/Nov/2020:13:41:32 +0545" status=200 time_ns=130543 traceid=da7a9eaf3b178a1c7ad61e699322f175 uri=/data/groups/6040aa17-9c64-4fef-9bd0-77234d71bad0 url=/data/groups/6040aa17-9c64-4fef-9bd0-77234d71bad0
2020-11-09T13:41:32+05:45 INF access token is already provided pkg=rhttp service=storage traceid=e3e779806cc68141507c2e6217ccc1cf
2020-11-09T13:41:32+05:45 INF http end="09/Nov/2020:13:41:32 +0545" host=<IP_ADDRESS> method=GET pkg=rhttp proto=HTTP/1.1 service=storage size=196 start="09/Nov/2020:13:41:32 +0545" status=200 time_ns=116235 traceid=e3e779806cc68141507c2e6217ccc1cf uri=/data/groups/dd58e5ec-842e-498b-8800-61f2ec6f911f url=/data/groups/dd58e5ec-842e-498b-8800-61f2ec6f911f
2020-11-09T13:41:32+05:45 INF access token is already provided pkg=rhttp service=storage traceid=c73f3a4da9404d323ec053e074343a19
2020-11-09T13:41:32+05:45 INF http end="09/Nov/2020:13:41:32 +0545" host=<IP_ADDRESS> method=GET pkg=rhttp proto=HTTP/1.1 service=storage size=290 start="09/Nov/2020:13:41:32 +0545" status=200 time_ns=96626 traceid=c73f3a4da9404d323ec053e074343a19 uri=/data/groups/262982c1-2362-4afa-bfdf-8cbfef64a06e url=/data/groups/262982c1-2362-4afa-bfdf-8cbfef64a06e
2020-11-09T13:41:32+05:45 INF unary code=OK end="09/Nov/2020:13:41:32 +0545" from=tcp://<IP_ADDRESS>:51340 pkg=rgrpc service=storage start="09/Nov/2020:13:41:32 +0545" time_ns=92323 traceid=78ee20a0d00932bd65162c4b26f35a5f uri=/cs3.storage.registry.v1beta1.RegistryAPI/GetStorageProvider user-agent=grpc-go/1.26.0
2020-11-09T13:41:32+05:45 INF unary code=OK end="09/Nov/2020:13:41:32 +0545" from=tcp://<IP_ADDRESS>:35158 pkg=rgrpc service=storage start="09/Nov/2020:13:41:32 +0545" time_ns=532972 traceid=78ee20a0d00932bd65162c4b26f35a5f uri=/cs3.storage.provider.v1beta1.ProviderAPI/CreateHome user-agent=grpc-go/1.26.0
2020-11-09T13:41:32+05:45 INF unary code=OK end="09/Nov/2020:13:41:32 +0545" from=tcp://<IP_ADDRESS>:51322 pkg=rgrpc service=storage start="09/Nov/2020:13:41:32 +0545" time_ns=1760565 traceid=78ee20a0d00932bd65162c4b26f35a5f uri=/cs3.gateway.v1beta1.GatewayAPI/CreateHome user-agent=grpc-go/1.26.0
2020-11-09T13:41:32+05:45 ERR could not get account for user error="{\"id\":\"com.owncloud.api.accounts\",\"code\":403,\"detail\":\"no permission for ListAccounts\",\"status\":\"Forbidden\"}" service=ocs userid=einstein

In order to reproduce it correctly the proxy needs to have basic auth enabled. I was not able to reproduce it until I read the logs. Starting the server with the following command:
❯ PROXY_ENABLE_BASIC_AUTH=true OCIS_LOG_LEVEL=debug go run cmd/ocis/main.go server

Without PROXY_ENABLE_BASIC_AUTH set I just keep getting a 997 response back. So I'm guessing this is related to the basic auth + proxy combination. Will dig further into it.

correct. no permission for ListAccounts is a log line from the role / permissions checks that is now in effect.

@dpakach is there any extra step you're doing? By running the curl command multiple times I am not able to reproduce it

@refs We first noticed this issue when running in CI. like in
https://drone.owncloud.com/owncloud/ocis/1273/22/7
As you see all tests fail in some pipeline because of this. So rather than running curl multiple times, I think you should restart the server and try each time. When it's failing it fails every time.
I just ran ocis with
STORAGE_HOME_DRIVER=owncloud STORAGE_USERS_DRIVER=owncloud PROXY_ENABLE_BASIC_AUTH=true bin/ocis server
But it happens very rarely (like once every 20 times) but it's an annoying thing when running in CI.
Also I deleted the contents of /var/tmp/ocis-* every time but that  may not be relevant here.

So @butonic and I were able to reproduce it by doing:

start the server as: STORAGE_HOME_DRIVER=owncloud STORAGE_USERS_DRIVER=owncloud PROXY_ENABLE_BASIC_AUTH=true ./ocis server
requesting user Einstein should work at this point (curl https://localhost:9200/ocs/v1.php/cloud/users/einstein -u einstein:relativity -k | xmllint --format -)
remove the folder as: /var/tmp/ocis-* which only wipes the settings (which includes roles and permissions), but it does NOT wipe the account, which lives in /var/tmp/ocis/metadata/nodes
do the curl request from step 2 again
:boom:

@refs, I did delete both /var/tmp/ocis and /var/tmp/ocis-* directories. Sorry, I should have made it clear in the first comment.
But since you reproduced it may be the real issue.

ha, interesting. Do you happen to know in which step are the directories removed?

@refs  This is the exact steps I followed

Stop ocis if it is running
Delete the ocis generated directories

cd /var/tmp && rm -rf ocis-* reva .pman ocis

Run the ocis server

STORAGE_HOME_DRIVER=owncloud STORAGE_USERS_DRIVER=owncloud PROXY_ENABLE_BASIC_AUTH=true bin/ocis server

Check the issues with curl command
a. If the issue is reproduced - :+1:
b. If the issue is not reproduced-  Goto step 1

In Line 5284 of https://drone.owncloud.com/owncloud/ocis/1308/19/5 we have a winner ...

2020-11-09T13:24:54Z INF http end="09/Nov/2020:13:24:54 +0000" host=<IP_ADDRESS> method=GET pkg=rhttp proto=HTTP/1.1 service=storage size=330 start="09/Nov/2020:13:24:54 +0000" status=200 time_ns=512671 traceid=192d4df331311711840b677e2c61c626 uri=/data/accounts/Alice url=/data/accounts/Alice
2020-11-09T13:24:54Z DBG Associated claims with uuid account={"accountEnabled":true,"displayName":"Alice Hansen","gidNumber":"3000","id":"Alice","mail":"alice@example.org","onPremisesSamAccountName":"Alice","passwordProfile":{},"preferredName":"Alice","uidNumber":"40040"} claims={"iss":"https://ocis-server:9200"} service=proxy
2020-11-09T13:24:54Z INF access token is already provided pkg=rhttp service=storage traceid=1cc7f644ad4e9e3ccf7f7096f3302d1d
2020-11-09T13:24:54Z DBG http routing: head=data tail=/accounts/Alice svc=data pkg=rhttp service=storage
2020-11-09T13:24:54Z DBG NodeFromPath() fn=/accounts/Alice pkg=rhttp service=storage traceid=1cc7f644ad4e9e3ccf7f7096f3302d1d
2020-11-09T13:24:54Z DBG NodeFromPath() walk node={"Exists":true,"ID":"a83ecfb4-7780-44f3-8d85-755eff746b1e","Name":"accounts","ParentID":"root"} pkg=rhttp service=storage traceid=1cc7f644ad4e9e3ccf7f7096f3302d1d
2020-11-09T13:24:54Z DBG NodeFromPath() walk node={"Exists":true,"ID":"a0459aa5-679c-4153-a65d-b9e3d8af1adf","Name":"Alice","ParentID":"a83ecfb4-7780-44f3-8d85-755eff746b1e"} pkg=rhttp service=storage traceid=1cc7f644ad4e9e3ccf7f7096f3302d1d
2020-11-09T13:24:54Z DBG user is owner, returning owner permissions node={"Exists":true,"ID":"a0459aa5-679c-4153-a65d-b9e3d8af1adf","Name":"Alice","ParentID":"a83ecfb4-7780-44f3-8d85-755eff746b1e"} pkg=rhttp service=storage traceid=1cc7f644ad4e9e3ccf7f7096f3302d1d
2020-11-09T13:24:54Z INF http end="09/Nov/2020:13:24:54 +0000" host=<IP_ADDRESS> method=GET pkg=rhttp proto=HTTP/1.1 service=storage size=330 start="09/Nov/2020:13:24:54 +0000" status=200 time_ns=426107 traceid=1cc7f644ad4e9e3ccf7f7096f3302d1d uri=/data/accounts/Alice url=/data/accounts/Alice
2020-11-09T13:24:54Z DBG skipping auth method=/cs3.gateway.v1beta1.GatewayAPI/CreateHome pkg=rgrpc service=storage traceid=aec5b6270a93e2a19cbf4466dc7f2b50
2020-11-09T13:24:54Z INF unary code=OK end="09/Nov/2020:13:24:54 +0000" from=tcp://<IP_ADDRESS>:53230 pkg=rgrpc service=storage start="09/Nov/2020:13:24:54 +0000" time_ns=180419 traceid=aec5b6270a93e2a19cbf4466dc7f2b50 uri=/cs3.storage.registry.v1beta1.RegistryAPI/GetStorageProvider user-agent=grpc-go/1.26.0
2020-11-09T13:24:54Z INF unary code=OK end="09/Nov/2020:13:24:54 +0000" from=tcp://<IP_ADDRESS>:59840 pkg=rgrpc service=storage start="09/Nov/2020:13:24:54 +0000" time_ns=628568 traceid=aec5b6270a93e2a19cbf4466dc7f2b50 uri=/cs3.storage.provider.v1beta1.ProviderAPI/CreateHome user-agent=grpc-go/1.26.0
2020-11-09T13:24:54Z INF unary code=OK end="09/Nov/2020:13:24:54 +0000" from=tcp://<IP_ADDRESS>:53098 pkg=rgrpc service=storage start="09/Nov/2020:13:24:54 +0000" time_ns=3511180 traceid=aec5b6270a93e2a19cbf4466dc7f2b50 uri=/cs3.gateway.v1beta1.GatewayAPI/CreateHome user-agent=grpc-go/1.26.0
2020-11-09T13:24:54Z DBG director found path=/ocs/v2.php/cloud/users/Alice policy=reva prefix=/ocs/v[12].php/cloud/(users?|groups) routeType=regex service=proxy
2020-11-09T13:24:54Z ERR could not get account for user error="{\"id\":\"com.owncloud.api.accounts\",\"code\":403,\"detail\":\"no permission for ListAccounts\",\"status\":\"Forbidden\"}" service=ocs userid=Alice
2020-11-09T13:24:54Z DBG  bytes=296 duration=4.548102 method=GET path=/ocs/v2.php/cloud/users/Alice proto=HTTP/1.1 request=2d786823-2e98-46c3-8d0f-f255c7503aa9 service=ocs status=500

🤔 The only suspicious thing I see is an account ID Alice with capital a... Just summons bad memories. Should work though...

No I think we're good on that front, the users endpoint is case insensitive

I was looking earlier to the usage of go-micro/metadata to store the roles @butonic

next idea:
Hunt down the first occurrence of this issue on CI and read the diff

@butonic @refs I ran git bisect and I think I found the commit that actually broke it
https://github.com/owncloud/ocis/commit/8e39d8b873e41900c4d85e430fdb9018fbcaa434
hope this helps

Thanks!