decreasingDots does not work correctly with dynamic data

I'm using react-native-animated-dots-carousel and set the config:
length: 8; maxIndicator: 5;
when I set currentIndex = 0 for render for the first time the  decreasingDots worked correctly.

But if I update the length = 7;  currentIndex = 6, it will render wrong

expectation:

Why would you use dynamic data? I do not remember supporting it when I built it, or testing something with dynamic data

Why would you use dynamic data? I do not remember supporting it when I built it, or testing something with dynamic data

because my carousel would fetch data from server and I can update on the list by adding/deleting items in the list. The issue came from when I changed currentIndex to the last position of the list and removed the last item, it will show like the second image but my expectation is the 3rd image

Why would you use dynamic data? I do not remember supporting it when I built it, or testing something with dynamic data

because my carousel would fetch data from server and I can update on the list by adding/deleting items in the list. The issue came from when I changed currentIndex to the last position of the list and removed the last item, it will show like the second image but my expectation is the 3rd image

@pmtu95 The only thing I can suggest you to do is to re-render the dots with the new data. Re render it completely


Insecure internal registry fails while pulling the kit

What happened?
I have the operator installed to use an internal registry listening on a service within the same namespace (HTTP://my-registry.my-namespace.svc.cluster.local:80). No TLS is configured. When the Integration should create a Pod, Kubernetes tries to pull the image by HTTPS (rather then HTTP) and fails. https://my-registry.my-namespace.svc.cluster.local:80/v2/my-nam.....
My expectation is,
a. Exactly the same registry url is used to push and to pull the image
b. that when i use the "insecure: true" configuration, the image pull uses HTTP
Steps to reproduce
Reproduction:

Prepared the operators by helmchart. Here the relevant part of the values.yamlplatform:
 build:
   registry:
     address: my-registry.my-namespace.svc.cluster.local:80
     insecure: true

kamel uninstall to cleanup
kamel reset all to cleanup
deploy helmchart

check operator logs for errors: nothing suspicious
check registry to see if my-namespace/camel-k-runtime-quarkus-builder image exists: success

deploy my integration

observe the operator: pushing to registry successful

Observed this new image my-namespace/camel-k-kit-cjs4g8f1jepq5b30qp20: success

ERROR: Happens when the integration tries to pull the image that was previously pushed successfully.
Warning  Failed     41m (x4 over 43m)      kubelet            Error: ErrImagePull
Warning  Failed     41m (x6 over 43m)      kubelet            Error: ImagePullBackOff
Normal   BackOff    2m58s (x174 over 43m)  kubelet            Back-off pulling image

Relevant log output
kubectl logs camel-k-operator-896747ccb-zpbbv --since 12h | jq '. | select(.level != "info")'
-> No Errors found

kubectl describe pod welcome-route2-5c9bd4d976-6mr4d

Name:             welcome-route2-5c9bd4d976-6mr4d
...
Labels:           camel.apache.org/integration=welcome-route2
                  pod-template-hash=5c9bd4d976
Annotations:      camel.apache.org/operator.id: camel-k-dev
...
Controlled By:  ReplicaSet/welcome-route2-5c9bd4d976
Containers:
  integration:
    Container ID:
    Image:           my-registry.my-namespace.svc.cluster.local:80/my-namespace/camel-k-kit-cjs4g8f1jepq5b30qp20@sha256:008cb6a4505cd74ec2d7bbee5d3efde6c002f3d6bd5559fb0bb13a67b17721d9
    Image ID:

Events:
  Type     Reason     Age                    From               Message
  ----     ------     ----                   ----               -------
  Normal   Scheduled  43m                    default-scheduler  Successfully assigned my-namespace/welcome-route2-5c9bd4d976-6mr4d to ip-10-130-118-220.eu-central-1.compute.internal
  Normal   Pulling    41m (x4 over 43m)      kubelet            Pulling image "my-registry.my-namespace.svc.cluster.local:80/my-namespace/camel-k-kit-cjs4g8f1jepq5b30qp20@sha256:008cb6a4505cd74ec2d7bbee5d3efde6c002f3d6bd5559fb0bb13a67b17721d9"
  Warning  Failed     41m (x4 over 43m)      kubelet            Failed to pull image "my-registry.my-namespace.svc.cluster.local:80/my-namespace/camel-k-kit-cjs4g8f1jepq5b30qp20@sha256:008cb6a4505cd74ec2d7bbee5d3efde6c002f3d6bd5559fb0bb13a67b17721d9": rpc error: code = Unknown desc = failed to pull and unpack image "my-registry.my-namespace.svc.cluster.local:80/my-namespace/camel-k-kit-cjs4g8f1jepq5b30qp20@sha256:008cb6a4505cd74ec2d7bbee5d3efde6c002f3d6bd5559fb0bb13a67b17721d9": failed to resolve reference "my-registry.my-namespace.svc.cluster.local:80/my-namespace/camel-k-kit-cjs4g8f1jepq5b30qp20@sha256:008cb6a4505cd74ec2d7bbee5d3efde6c002f3d6bd5559fb0bb13a67b17721d9": failed to do request: Head "https://my-registry.my-namespace.svc.cluster.local:80/v2/my-namespace/camel-k-kit-cjs4g8f1jepq5b30qp20/manifests/sha256:008cb6a4505cd74ec2d7bbee5d3efde6c002f3d6bd5559fb0bb13a67b17721d9": dial tcp: lookup my-registry.my-namespace.svc.cluster.local: no such host
  Warning  Failed     41m (x4 over 43m)      kubelet            Error: ErrImagePull
  Warning  Failed     41m (x6 over 43m)      kubelet            Error: ImagePullBackOff
  Normal   BackOff    2m58s (x174 over 43m)  kubelet            Back-off pulling image "my-registry.my-namespace.svc.cluster.local:80/my-namespace/camel-k-kit-cjs4g8f1jepq5b30qp20@sha256:008cb6a4505cd74ec2d7bbee5d3efde6c002f3d6bd5559fb0bb13a67b17721d9"

Camel K version
2.0.0

Yes, this is some known problem on Kubernetes, see the discussion thread [1]. If you want to use an insecure registry, it seems that the only way is to configure your Kubernetes cluster to be allowed to do so [2]. I guess that it would be better to make an effort and try to configure a secure registry and avoid all those workarounds though.
[1] https://camel.zulipchat.com/#narrow/stream/257299-camel-k/topic/Registry.20with.20no.20credentials
[2] https://stackoverflow.com/questions/51893120/kubernetes-pull-from-insecure-docker-registry

Thank you for having a look at it. My conclusion after reading the links above is, that we should use a secure registry instead. In parallel with the attempt described in this Issue, I did setup a secure private registry with a internal certificate. But this didn't work either and I created this issue for it: issues/4724
The problem I describe here comes from the fact, that the AWS ECR seems incompatible with our Camel-K setup ("doesn't support folders", "the image name is the tag") and therefore we're looking for a Registry alternative.

The problem I describe here comes from the fact, that the AWS ECR seems incompatible with our Camel-K setup ("doesn't support folders", "the image name is the tag") and therefore we're looking for a Registry alternative.

I guess this is a limitation of the registry then. As discussed in several occasions, we cannot support all the different registry solutions, so we try to stick to the standards (in this case the one proposed in the docker tag).

We should include the last statement somewhere in the registry documentation.


Subtitles saving incorrectly

Version
1.19.12
Details
Simply save a video. Instead of the embedded subtitles saving correctly, they're in a weird moving format. A line is printed, but then the next subtitle screen shows the lines moving downward. Harder to explain, so I've attached a video.
I'm wondering if this is a bug in YoutubeDownloader or just something with Youtube itself. Or, is this an intended feature?
https://github.com/Tyrrrz/YoutubeDownloader/assets/70227235/febac708-32b7-428b-a11d-74bdfb754dd8
Steps to reproduce

Save any video (auto-generated subtitles count, so the video doesn't need it's own to reproduce)

I'm not sure what you're talking about? The subtitles are rendered by your player. They're stored inside the video in a text format, with just timing information. The player decides how they "move" on your screen.

Can you share a video ID/URL so I can check?

The ID was eWRfhZUzrAc. Subtitles on VLC player worked perfectly in the past, so I'm convinced it's not a player issue. I think it's just a timing relapse, where the second set of timing information (second "sentence") is being combined with the first or something.

Here's how the subtitles are encoded for that section of the video:
13622
04:13:23,600 --> 04:13:27,760
time we're not doing anything to narrow

13623
04:13:25,750 --> 04:13:27,760

13624
04:13:25,760 --> 04:13:29,279
down the search each time we have to

13625
04:13:27,750 --> 04:13:29,279

13626
04:13:27,760 --> 04:13:30,960
search all of it

13627
04:13:29,269 --> 04:13:30,960

13628
04:13:29,279 --> 04:13:32,800
if you're searching a big list or

13629
04:13:30,950 --> 04:13:32,800

13630
04:13:30,960 --> 04:13:34,880
searching it repeatedly this amount of

13631
04:13:32,790 --> 04:13:34,880

13632
04:13:32,800 --> 04:13:36,960
time can slow your whole lap down to the

13633
04:13:34,870 --> 04:13:36,960

As you can see, the captions do overlap in timing. For example:

time we're not doing anything to narrow ends at 04:13:27
down the search each time we have to starts at 04:13:25, which is 2 seconds earlier

That being said, however, I noticed that the videos actually has two subtitle tracks, where one of them doesn't have overlapping captions. I don't know how exactly that happened, so I will have to look at it. But it does seem that the overlap is produced on YouTube's side.

Alright, thanks for clarifying. Sorry for the irrelevant issue.

Alright, thanks for clarifying. Sorry for the irrelevant issue.

It should be better now


JavaScript

#JavaScript
As a boot camp student
I want the prework notes to be structured on a webpage
So that I can easily find and read the information
GIVEN a Prework Study Guide website
WHEN I view the study guide
THEN I can see the four topics I learned listed along with a suggestion on what I should study first

Made js file, for loop and comment out if else statement


NuxtServerError - Request failed with status code 500 - No indication of which API call failed

Version
v2.4.0
Reproduction link
https://github.com/kalenjordan/pros.global
Steps to reproduce
I'm not exactly sure how to reproduce, but usually within 2 to 8 hours it happens on my app (https://pros.global). It seems that axios is hitting a 500 error response but I have no indication of what API request failed exactly.
NuxtServerError
Request failed with status code 500
/home/forge/pros.global/node_modules/axios/lib/core/createError.js in createError at line 16:15
/home/forge/pros.global/node_modules/axios/lib/core/settle.js in settle at line 18:12
/home/forge/pros.global/node_modules/axios/lib/adapters/http.js in IncomingMessage.handleStreamEnd at line 201:11
events.js in IncomingMessage.emit at line 187:15
domain.js in IncomingMessage.EventEmitter.emit at line 459:23
_stream_readable.js in endReadableNT at line 1094:12
internal/process/next_tick.js in process._tickCallback at line 63:19
What is expected ?
I would expect that I would have some way to know which API call failed in the error log.
What is actually happening?
There is no indication of which API call failed.
Additional comments?
Perhaps there is a way within axios to log all API requests that go through so that I could at least correlate the error to that log?

This bug report is available on Nuxt community (#c8707)

If you use the nuxt axios module you can set debug to true so all requests are logged (be aware of disk space issues if you are logging this to file and running for 8 hrs!): https://axios.nuxtjs.org/options#debug


fix(datetime): default to current date when no value given

Short description of what this resolves:
This PR resolves an issue where the datetime component is not defaulting to the current date when no value is given
Changes proposed in this pull request:

Add getDateValue which will parse a given date OR default to the current date
Add base spec tests to be built out in future tasks

Ionic Version:
Fixes: #14609

This looks great :tada:

Guys, I have used the same  ISO string for removing the Past Date and Time. And it works,
But, if I set minuteValues="0,15,30,45", and my current time is 10:50, then it doesn't show the Minutes in my date picker.
have a look at the screenshot attached.
Can you help me this?


can't load lora after refresh all files

hallo, thank for updated. all code running smoothly, but afte downloaded lora from civitai, its cant load after i press refresh all files.

Check the LoRA is in the right folder by navigating to the Fooocus/models/loras folder in Sagemaker's file browser on the left hand side.
Another thing you can try is running the first code block in the file management notebook, to re-initialize variables. In the output, you can check if it got the right folder, and if it prints out an error, try restarting the kernel by going to Kernel -> Restart Kernel in the top menu.

I've tried. In the file manager, Lora has been successfully installed, but in Fooocus it is not detected. either permanent or temporary.


UnixPB: Add tags to tasks in Common role

Added tags to sub folder tasks in Common role, such that these tags can be used to run/skip the respective tasks.
Checklist

[x] commit message has one of the standard prefixes
[ ] faq.md updated if appropriate
[ ] other documentation is changed or added (if applicable)
[ ] playbook changes run through VPC or QPC (if you have access) SXA: Running https://ci.adoptium.net/view/Tooling/job/VagrantPlaybookCheck/1875/ <<< Failed for a variety of reasons so I'm trying again at https://ci.adoptium.net/view/Tooling/job/VagrantPlaybookCheck/1877/ <<< Also failed for various reasons - https://ci.adoptium.net/job/VagrantPlaybookCheck/1880/. New run 1/July https://ci.adoptium.net/job/VagrantPlaybookCheck/1898/
[ ] VPC/QPC not applicable for this PR
[ ] for inventory.yml changes, bastillion/nagios/jenkins updated accordingly

I've started running the VPC checks (link in description)
This PR is in reference to the thread at https://adoptium.slack.com/archives/C53GHCXL4/p1716809812153839 where the user was unable to run the playbooks with -t patch_update to initiate that part of the Common role

@aswinkr77  Seems to be a number of CI failures, not sure if related...

@karianna it's related I think. The task - name: Perform OS setup and configuration contains the adoptopenjdk tag which is used as the skip tag, so the task is getting skipped.

I think I'll remove all the unnecessary tags and add only the necessary tags we need in the main.yml file.

This solution is not viable at the moment. I'll add the missing tags to the tasks and stick with skipping tags instead of running the tags.

@sxa I've changed the approach. Since the VPC checks were failing - related to the newly(previously) added tags in the main.yml file. Now I've removed it, and added tags to almost all tasks in all sub folder tasks in Common role. So these tags can be used to skip unnecessary tasks.

@sxa any updates in this?

@sxa any updates in this?

Apologies for not being too responsive on this. What's making me nervous is whether it will definitely work in both situations i.e. will the playbooks run to completion with --skip-tags build_tools and also with -t build_tools. until these work I'm not sure what we're gaining with the changes.
As an example I've just tried a quick test on a few scenarios using --skip-tags build_tools:

Alpine failed on the curl role
Ubuntu 22.04 failed on the ant role (trying to do the GPG signature validation)
CentOS7 failed in Common : Set Default JRE (CentOS 7 and later) with 'dict object' has no attribute 'lnk_source'

With -t build_tools I get GPG signature failures when it gets to the the cmake role (e.g. on CentOS7 because wget is missing) and on Ubuntu 22.04 it fails when it gets to gcc_7 because it doesn't have xz available. So overall I think there may be some work to be done to get this into a state where it would be usable.
A coupler of other notes:

Can you rebase this PR please? (It currently won't work on CentOS7 at all unless you do that sine it went EOL at the end of last month)
Semi-related: I was thinking of doing a separate PR that lets people skip the whole Common role. Mostly because when I'm testing changes it's quite nice to skip that role which can take a bit of time to run. So if you see me put in a PR for that it's completely separate from this work and will not supercede this one.

Have rebased via GH UI

@sxa
My first approach was to use tags to run tasks, for that to work, the tags from tasks should be present in the main.yml file of Common role(so that tags will be picked up by ansible). But when I tested that changes(my first PR was about it), the entire Common role was skipped because some of the tags used in the main.yml was used as skip tags, so all the vagrant failed. So I changed my approach.
Now I'm using tags to skip tasks to achieve the goal, so basically as of now only --skip-tags will work and not -t:
ansible-playbook -u root -i ~/aswin_list.txt --tags build_tools ibm_main.yml --ssh-common-args='-o StrictHostKeyChecking=no'

PLAY [all] *******************************************************************************************************************************************************************************************************

TASK [Gathering Facts] *******************************************************************************************************************************************************************************************
ok: [ubuntu22-docker-test-1.fyre.ibm.com]

PLAY RECAP *******************************************************************************************************************************************************************************************************
ubuntu22-docker-test-1.fyre.ibm.com : ok=1    changed=0    unreachable=0    failed=0    skipped=0    rescued=0    ignored=0

the example shown here is using a customized play level ibm_main.yml file, somehow the main.yml is running all the roles, instead of running only the roles/tasks associated with the particular tags specified in --tags.

With -t build_tools I get GPG signature failures when it gets to the the cmake role (e.g. on CentOS7 because wget is missing) and on Ubuntu 22.04 it fails when it gets to gcc_7 because it doesn't have xz available. So overall I think there may be some work to be done to get this into a state where it would be usable.

the cmake and gcc_7 roles are not supposed to run when -t build_tools is used, since cmake and gcc_7 uses cmake and gcc_7 tags respectively. I'm not sure why it ran these roles.
The --skip-tags is working as expected:
ansible-playbook -u root -i ~/aswin_list.txt --skip-tags build_tools main.yml --ssh-common-args='-o StrictHostKeyChecking=no' --extra-vars='ansible_password=Ni4!ufbeQ7akcq@'

PLAY [Ansible Unix playbook] *************************************************************************************************************************************************************************************

TASK [Gathering Facts] *******************************************************************************************************************************************************************************************
ok: [ubuntu22-docker-test-1.fyre.ibm.com]

TASK [Common : If ansible_processor_cpus is not defined, set to ansible_processor_cores or 1] ********************************************************************************************************************
skipping: [ubuntu22-docker-test-1.fyre.ibm.com]

TASK [Common : Include OS variables] *****************************************************************************************************************************************************************************
ok: [ubuntu22-docker-test-1.fyre.ibm.com]

TASK [Common : Perform OS setup and configuration] ***************************************************************************************************************************************************************
included: /Users/aswin/Personal/Eclipse Adoptium/infrastructure/ansible/playbooks/AdoptOpenJDK_Unix_Playbook/roles/Common/tasks/Ubuntu.yml for ubuntu22-docker-test-1.fyre.ibm.com

TASK [Common : Install gnugp2 for S390x] *************************************************************************************************************************************************************************
skipping: [ubuntu22-docker-test-1.fyre.ibm.com]

TASK [Common : Install gnupg2 for aarch64] ***********************************************************************************************************************************************************************
skipping: [ubuntu22-docker-test-1.fyre.ibm.com]

TASK [Common : Add Azul Zulu GPG Package Signing Key for x86_64] *************************************************************************************************************************************************
changed: [ubuntu22-docker-test-1.fyre.ibm.com]

TASK [Common : Add Azul Zulu repository for x86_64] **************************************************************************************************************************************************************
changed: [ubuntu22-docker-test-1.fyre.ibm.com]

TASK [Common : Run apt-get upgrade] ******************************************************************************************************************************************************************************
changed: [ubuntu22-docker-test-1.fyre.ibm.com]

TASK [Common : Call Build Packages and Tools Task] ***************************************************************************************************************************************************************
included: /Users/aswin/Personal/Eclipse Adoptium/infrastructure/ansible/playbooks/AdoptOpenJDK_Unix_Playbook/roles/Common/tasks/build_packages_and_tools.yml for ubuntu22-docker-test-1.fyre.ibm.com

TASK [Common : Set package manager var] **************************************************************************************************************************************************************************
ok: [ubuntu22-docker-test-1.fyre.ibm.com]

TASK [Common : Set package manager var for FreeBSD] **************************************************************************************************************************************************************
skipping: [ubuntu22-docker-test-1.fyre.ibm.com]

TASK [Common : Install Test Tool Packages] ***********************************************************************************************************************************************************************
changed: [ubuntu22-docker-test-1.fyre.ibm.com] => (item=acl)
ok: [ubuntu22-docker-test-1.fyre.ibm.com] => (item=perl)
ok: [ubuntu22-docker-test-1.fyre.ibm.com] => (item=xauth)
changed: [ubuntu22-docker-test-1.fyre.ibm.com] => (item=xvfb)
changed: [ubuntu22-docker-test-1.fyre.ibm.com] => (item=binfmt-support)
changed: [ubuntu22-docker-test-1.fyre.ibm.com] => (item=qemu-user-static)
ok: [ubuntu22-docker-test-1.fyre.ibm.com] => (item=unzip)
changed: [ubuntu22-docker-test-1.fyre.ibm.com] => (item=libexpat1-dev)
changed: [ubuntu22-docker-test-1.fyre.ibm.com] => (item=libcurl4-openssl-dev)
changed: [ubuntu22-docker-test-1.fyre.ibm.com] => (item=fakeroot)
changed: [ubuntu22-docker-test-1.fyre.ibm.com] => (item=jq)
changed: [ubuntu22-docker-test-1.fyre.ibm.com] => (item=gnutls-bin)
ok: [ubuntu22-docker-test-1.fyre.ibm.com] => (item=libnss3)
changed: [ubuntu22-docker-test-1.fyre.ibm.com] => (item=libnss3-tools)
changed: [ubuntu22-docker-test-1.fyre.ibm.com] => (item=libnss3-dev)

TASK [Common : Install additional Test Tool Packages for x86_64] *************************************************************************************************************************************************
changed: [ubuntu22-docker-test-1.fyre.ibm.com] => (item=pulseaudio)

TASK [Common : Install additional Packages specific to Ubuntu 16] ************************************************************************************************************************************************
skipping: [ubuntu22-docker-test-1.fyre.ibm.com] => (item=libgstreamer0.10-dev)
skipping: [ubuntu22-docker-test-1.fyre.ibm.com] => (item=libgstreamer-plugins-base0.10-dev)
skipping: [ubuntu22-docker-test-1.fyre.ibm.com] => (item=libmpfr4)
skipping: [ubuntu22-docker-test-1.fyre.ibm.com] => (item=libmpfr4-dbg)
skipping: [ubuntu22-docker-test-1.fyre.ibm.com]

TASK [Common : Install additional Packages specific to Ubuntu 18] ************************************************************************************************************************************************
skipping: [ubuntu22-docker-test-1.fyre.ibm.com] => (item=libgstreamer1.0-dev)
skipping: [ubuntu22-docker-test-1.fyre.ibm.com] => (item=libgstreamer-plugins-base1.0-dev)
skipping: [ubuntu22-docker-test-1.fyre.ibm.com]

TASK [Common : Download LibFFI6 v3.2.1_8 For Ubuntu 20 or 22 on S390X] *******************************************************************************************************************************************
skipping: [ubuntu22-docker-test-1.fyre.ibm.com]

TASK [Common : Install LibFFI6 v3.2.1_8 For Ubuntu 20 or 22 on S390X] ********************************************************************************************************************************************
skipping: [ubuntu22-docker-test-1.fyre.ibm.com]

TASK [Common : Set default java version for x86_64] **************************************************************************************************************************************************************
skipping: [ubuntu22-docker-test-1.fyre.ibm.com]

TASK [Common : Set default java version for armv7l] **************************************************************************************************************************************************************
skipping: [ubuntu22-docker-test-1.fyre.ibm.com]

TASK [Common : Set default java version for ppc64le] *************************************************************************************************************************************************************
skipping: [ubuntu22-docker-test-1.fyre.ibm.com]

TASK [Common : Install 'locales' package] ************************************************************************************************************************************************************************
ok: [ubuntu22-docker-test-1.fyre.ibm.com]

In the above example, the build_tools are skipped as expected.

Alpine failed on the curl role
Ubuntu 22.04 failed on the ant role (trying to do the GPG signature validation)
CentOS7 failed in Common : Set Default JRE (CentOS 7 and later) with 'dict object' has no attribute 'lnk_source'

maybe the packages needed for curl, ant are part of tasks having build_tools tags.
I've no idea what happend with the Default JRE one.

@sxa
My first approach was to use tags to run tasks, for that to work, the tags from tasks should be present in the main.yml file of Common role(so that tags will be picked up by ansible). But when I tested that changes(my first PR was about it), the entire Common role was skipped because some of the tags used in the main.yml was used as skip tags, so all the vagrant failed. So I changed my approach.
Now I'm using tags to skip tasks to achieve the goal, so basically as of now only --skip-tags will work and not -t:
ansible-playbook -u root -i ~/aswin_list.txt --tags build_tools ibm_main.yml --ssh-common-args='-o StrictHostKeyChecking=no'

PLAY [all] *******************************************************************************************************************************************************************************************************

TASK [Gathering Facts] *******************************************************************************************************************************************************************************************
ok: [ubuntu22-docker-test-1.fyre.ibm.com]

PLAY RECAP *******************************************************************************************************************************************************************************************************
ubuntu22-docker-test-1.fyre.ibm.com : ok=1    changed=0    unreachable=0    failed=0    skipped=0    rescued=0    ignored=0

the example shown here is using a customized play level ibm_main.yml file, somehow the main.yml is running all the roles, instead of running only the roles/tasks associated with the particular tags specified in --tags.

With -t build_tools I get GPG signature failures when it gets to the the cmake role (e.g. on CentOS7 because wget is missing) and on Ubuntu 22.04 it fails when it gets to gcc_7 because it doesn't have xz available. So overall I think there may be some work to be done to get this into a state where it would be usable.

the cmake and gcc_7 roles are not supposed to run when -t build_tools is used, since cmake and gcc_7 uses cmake and gcc_7 tags respectively. I'm not sure why it ran these roles.
The --skip-tags is working as expected:
ansible-playbook -u root -i ~/aswin_list.txt --skip-tags build_tools main.yml --ssh-common-args='-o StrictHostKeyChecking=no'

PLAY [Ansible Unix playbook] *************************************************************************************************************************************************************************************

TASK [Gathering Facts] *******************************************************************************************************************************************************************************************
ok: [ubuntu22-docker-test-1.fyre.ibm.com]

TASK [Common : If ansible_processor_cpus is not defined, set to ansible_processor_cores or 1] ********************************************************************************************************************
skipping: [ubuntu22-docker-test-1.fyre.ibm.com]

TASK [Common : Include OS variables] *****************************************************************************************************************************************************************************
ok: [ubuntu22-docker-test-1.fyre.ibm.com]

TASK [Common : Perform OS setup and configuration] ***************************************************************************************************************************************************************
included: /Users/aswin/Personal/Eclipse Adoptium/infrastructure/ansible/playbooks/AdoptOpenJDK_Unix_Playbook/roles/Common/tasks/Ubuntu.yml for ubuntu22-docker-test-1.fyre.ibm.com

TASK [Common : Install gnugp2 for S390x] *************************************************************************************************************************************************************************
skipping: [ubuntu22-docker-test-1.fyre.ibm.com]

TASK [Common : Install gnupg2 for aarch64] ***********************************************************************************************************************************************************************
skipping: [ubuntu22-docker-test-1.fyre.ibm.com]

TASK [Common : Add Azul Zulu GPG Package Signing Key for x86_64] *************************************************************************************************************************************************
changed: [ubuntu22-docker-test-1.fyre.ibm.com]

TASK [Common : Add Azul Zulu repository for x86_64] **************************************************************************************************************************************************************
changed: [ubuntu22-docker-test-1.fyre.ibm.com]

TASK [Common : Run apt-get upgrade] ******************************************************************************************************************************************************************************
changed: [ubuntu22-docker-test-1.fyre.ibm.com]

TASK [Common : Call Build Packages and Tools Task] ***************************************************************************************************************************************************************
included: /Users/aswin/Personal/Eclipse Adoptium/infrastructure/ansible/playbooks/AdoptOpenJDK_Unix_Playbook/roles/Common/tasks/build_packages_and_tools.yml for ubuntu22-docker-test-1.fyre.ibm.com

TASK [Common : Set package manager var] **************************************************************************************************************************************************************************
ok: [ubuntu22-docker-test-1.fyre.ibm.com]

TASK [Common : Set package manager var for FreeBSD] **************************************************************************************************************************************************************
skipping: [ubuntu22-docker-test-1.fyre.ibm.com]

TASK [Common : Install Test Tool Packages] ***********************************************************************************************************************************************************************
changed: [ubuntu22-docker-test-1.fyre.ibm.com] => (item=acl)
ok: [ubuntu22-docker-test-1.fyre.ibm.com] => (item=perl)
ok: [ubuntu22-docker-test-1.fyre.ibm.com] => (item=xauth)
changed: [ubuntu22-docker-test-1.fyre.ibm.com] => (item=xvfb)
changed: [ubuntu22-docker-test-1.fyre.ibm.com] => (item=binfmt-support)
changed: [ubuntu22-docker-test-1.fyre.ibm.com] => (item=qemu-user-static)
ok: [ubuntu22-docker-test-1.fyre.ibm.com] => (item=unzip)
changed: [ubuntu22-docker-test-1.fyre.ibm.com] => (item=libexpat1-dev)
changed: [ubuntu22-docker-test-1.fyre.ibm.com] => (item=libcurl4-openssl-dev)
changed: [ubuntu22-docker-test-1.fyre.ibm.com] => (item=fakeroot)
changed: [ubuntu22-docker-test-1.fyre.ibm.com] => (item=jq)
changed: [ubuntu22-docker-test-1.fyre.ibm.com] => (item=gnutls-bin)
ok: [ubuntu22-docker-test-1.fyre.ibm.com] => (item=libnss3)
changed: [ubuntu22-docker-test-1.fyre.ibm.com] => (item=libnss3-tools)
changed: [ubuntu22-docker-test-1.fyre.ibm.com] => (item=libnss3-dev)

TASK [Common : Install additional Test Tool Packages for x86_64] *************************************************************************************************************************************************
changed: [ubuntu22-docker-test-1.fyre.ibm.com] => (item=pulseaudio)

TASK [Common : Install additional Packages specific to Ubuntu 16] ************************************************************************************************************************************************
skipping: [ubuntu22-docker-test-1.fyre.ibm.com] => (item=libgstreamer0.10-dev)
skipping: [ubuntu22-docker-test-1.fyre.ibm.com] => (item=libgstreamer-plugins-base0.10-dev)
skipping: [ubuntu22-docker-test-1.fyre.ibm.com] => (item=libmpfr4)
skipping: [ubuntu22-docker-test-1.fyre.ibm.com] => (item=libmpfr4-dbg)
skipping: [ubuntu22-docker-test-1.fyre.ibm.com]

TASK [Common : Install additional Packages specific to Ubuntu 18] ************************************************************************************************************************************************
skipping: [ubuntu22-docker-test-1.fyre.ibm.com] => (item=libgstreamer1.0-dev)
skipping: [ubuntu22-docker-test-1.fyre.ibm.com] => (item=libgstreamer-plugins-base1.0-dev)
skipping: [ubuntu22-docker-test-1.fyre.ibm.com]

TASK [Common : Download LibFFI6 v3.2.1_8 For Ubuntu 20 or 22 on S390X] *******************************************************************************************************************************************
skipping: [ubuntu22-docker-test-1.fyre.ibm.com]

TASK [Common : Install LibFFI6 v3.2.1_8 For Ubuntu 20 or 22 on S390X] ********************************************************************************************************************************************
skipping: [ubuntu22-docker-test-1.fyre.ibm.com]

TASK [Common : Set default java version for x86_64] **************************************************************************************************************************************************************
skipping: [ubuntu22-docker-test-1.fyre.ibm.com]

TASK [Common : Set default java version for armv7l] **************************************************************************************************************************************************************
skipping: [ubuntu22-docker-test-1.fyre.ibm.com]

TASK [Common : Set default java version for ppc64le] *************************************************************************************************************************************************************
skipping: [ubuntu22-docker-test-1.fyre.ibm.com]

TASK [Common : Install 'locales' package] ************************************************************************************************************************************************************************
ok: [ubuntu22-docker-test-1.fyre.ibm.com]

In the above example, the build_tools are skipped as expected.

Alpine failed on the curl role
Ubuntu 22.04 failed on the ant role (trying to do the GPG signature validation)
CentOS7 failed in Common : Set Default JRE (CentOS 7 and later) with 'dict object' has no attribute 'lnk_source'

maybe the packages needed for curl, ant are part of tasks having build_tools tags.
I've no idea what happend with the Default JRE one.

@sxa anything on this?

@sxa anything on this?

Our team has been tied up with release work since last Tuesday so have not had any time to dedicate to other work since then.

as of now only --skip-tags will work and not -t:

Understood. It's not easy to make it work both ways :-) We'll need to thing about whether we can make that clear to people running the playbooks as it superficially feels natural that you could run with -t build_tools to get a machine set up for building.

maybe the packages needed for curl, ant are part of tasks having build_tools tags.

We'll need to understand that and resolve it IMHO. It would be problematic if the playbooks weren't able to work unless those were preinstalled (maybe they are on your internal fyre systems)

@sxa I'll summarise the changes here:

Alpine.yml:
I've added build_tools tag for this task before the block:

- name: Install JDK for x64
  when: ansible_architecture == "x86_64"
  block:

the build_tools tags are already there for the tasks under blocks, I just moved it before the block. That's it.

CentOS.yml:
I've added build_tools tag for this task:

- name: Check For Centos8 Stream
  shell: cat /etc/centos-release
  register: relfile_contents

cause the relfile_contents variable is only used in tasks which already have build_tools tag.

Debian.yml:
Added patch_update tag to this task:

  - name: Allow https apt sources
  package: "name=apt-transport-https state=latest"

Fedora.yml:
Added install_java tag to 4 tasks which basically installs java:

################
# Install Java #
################
- name: Install Java (Not RedHat 6 on ppc64)
  package: "name={{ item }} state=latest"
  with_items: "{{ Java_NOT_RHEL6_PPC64 }}"
  when:
    - not (ansible_distribution_major_version == "6" and ansible_architecture == "ppc64")
    - not (ansible_distribution_major_version == "8")
    - not (ansible_distribution_major_version == "35" and ansible_distribution == "Fedora")

- name: Install Java when RedHat 6 on ppc64
  package: "name={{ item }} state=latest"
  with_items: "{{ Java_RHEL6_PPC64 }}"
  when: (ansible_distribution_major_version == "6" and ansible_architecture == "ppc64")

- name: Install Java when RedHat 8
  package: "name={{ item }} state=latest"
  with_items: "{{ Java_RHEL8 }}"
  when: (ansible_distribution_major_version == "8")

- name: Install Java when Fedora 35
  package: "name={{ item }} state=latest"
  with_items: "{{ Java_FED35 }}"
  when: (ansible_distribution_major_version == "35" and ansible_distribution != "Fedora")

RedHat.yml:
Similar to the above case. Added install_java tag:

################
# Install Java #
################
- name: Install Java (Not RedHat 6 on ppc64)
  package: "name={{ item }} state=latest"
  with_items: "{{ Java_NOT_RHEL6_PPC64 }}"
  when:
    - not (ansible_distribution_major_version == "6" and ansible_architecture == "ppc64")
    - not (ansible_distribution_major_version == "8")

- name: Install Java when RedHat 6 on ppc64
  package: "name={{ item }} state=latest"
  with_items: "{{ Java_RHEL6_PPC64 }}"
  when: (ansible_distribution_major_version == "6" and ansible_architecture == "ppc64")

- name: Install Java when RedHat 8
  package: "name={{ item }} state=latest"
  with_items: "{{ Java_RHEL8 }}"
  when: (ansible_distribution_major_version == "8")

SLES.yml:
Similar for the Alpine.yml, I moved the build_tools tag before the block. Already the tasks under the blocks had the build_tools tag:

- name: Install Git SLES 12 SP5
  when: (ansible_distribution_major_version == "12" and ansible_distribution_version == "12.5")
  block:

Ubuntu.yml:
Added test_tools tag to four tasks:

#########################
# Additional Test Tools #
#########################
- name: Install additional Test Tool Packages for x86_64
  package: "name={{ item }} state=latest"
  with_items: "{{ Test_Tool_Packages_x86_64 }}"
  when:
    - ansible_architecture == "x86_64"
  tags: test_tools

- name: Install additional Packages specific to Ubuntu 16
  package: "name={{ item }} state=latest"
  with_items: "{{ Additional_Packages_Ubuntu16 }}"
  when:
    - ansible_distribution_major_version == "16"

- name: Install additional Packages specific to Ubuntu 18
  package: "name={{ item }} state=latest"
  with_items: "{{ Additional_Packages_Ubuntu18 }}"
  when:
    - ansible_distribution_major_version == "18"

- name: Download LibFFI6 v3.2.1_8 For Ubuntu 20 or 22 on S390X
  get_url:
    url: https://mirrors.mit.edu/ubuntu-ports/pool/main/libf/libffi/libffi6_3.2.1-8_s390x.deb
    dest: /tmp/libffi6_3.2.1-8_s390x.deb
    force: no
    mode: 0755
    checksum: sha256:05e456a2e8ad9f20db846ccb96c483235c3243e27025c3e8e8e358411fd48be9
  when:
    - (ansible_distribution_major_version == "20" and ansible_architecture == "s390x") or
      (ansible_distribution_major_version == "22" and ansible_architecture == "s390x")

- name: Install LibFFI6 v3.2.1_8 For Ubuntu 20 or 22 on S390X
  apt: deb="/tmp/libffi6_3.2.1-8_s390x.deb"
  when:
    - (ansible_distribution_major_version == "20" and ansible_architecture == "s390x") or
      (ansible_distribution_major_version == "22" and ansible_architecture == "s390x")

ref: https://github.com/adoptium/infrastructure/pull/3580#issuecomment-2225260133
So I don't think these changes were the causes for the failures you mentioned:

Basically Nothing changed in Alpine.yml
For Ubuntu the changes were addition of test_tools so there was no changes related to build_tools, failure was something unrelated.
For CentOS 7, this was the task that failed:

- name: Set Default JRE (CentOS 7 and later)
  alternatives:
    name: java
    path: "{{ jre_path.stat.lnk_source }}/bin/java"
  when:
    - ansible_distribution_major_version > "6"
  tags: default_java

The only change I made was to add build_tools tag to the Check for CentOS Stream task. So the failure is unrelated.

We'll need to understand that and resolve it IMHO. It would be problematic if the playbooks weren't able to work unless those were preinstalled (maybe they are on your internal fyre systems)

The failures are unrelated to changes I made. The failures are all related to the existing PB I believe.

The failures are unrelated to changes I made. The failures are all related to the existing PB I believe

OK understood - I do feel we should probably try to resolve the underlying issues though. Moving and adding the existing tags doesn't seem to serve much purpose when they don't currently work. Is there a use case which would be solved by this PR given that it's already broken when skipping these days? It's difficult to approve a change that cannot be easily tested.

/thaw

@sxa

Moving and adding the existing tags doesn't seem to serve much purpose when they don't currently work.

They do work. See here: https://github.com/adoptium/infrastructure/pull/3580#issuecomment-2230483423
The --skip-tags is working as expected:

ansible-playbook -u root -i ~/aswin_list.txt --skip-tags build_tools main.yml --ssh-common-args='-o StrictHostKeyChecking=no'

PLAY [Ansible Unix playbook] *************************************************************************************************************************************************************************************

TASK [Gathering Facts] *******************************************************************************************************************************************************************************************
ok: [ubuntu22-docker-test-1.fyre.ibm.com]

TASK [Common : If ansible_processor_cpus is not defined, set to ansible_processor_cores or 1] ********************************************************************************************************************
skipping: [ubuntu22-docker-test-1.fyre.ibm.com]

TASK [Common : Include OS variables] *****************************************************************************************************************************************************************************
ok: [ubuntu22-docker-test-1.fyre.ibm.com]

TASK [Common : Perform OS setup and configuration] ***************************************************************************************************************************************************************
included: /Users/aswin/Personal/Eclipse Adoptium/infrastructure/ansible/playbooks/AdoptOpenJDK_Unix_Playbook/roles/Common/tasks/Ubuntu.yml for ubuntu22-docker-test-1.fyre.ibm.com

TASK [Common : Install gnugp2 for S390x] *************************************************************************************************************************************************************************
skipping: [ubuntu22-docker-test-1.fyre.ibm.com]

TASK [Common : Install gnupg2 for aarch64] ***********************************************************************************************************************************************************************
skipping: [ubuntu22-docker-test-1.fyre.ibm.com]

TASK [Common : Add Azul Zulu GPG Package Signing Key for x86_64] *************************************************************************************************************************************************
changed: [ubuntu22-docker-test-1.fyre.ibm.com]

TASK [Common : Add Azul Zulu repository for x86_64] **************************************************************************************************************************************************************
changed: [ubuntu22-docker-test-1.fyre.ibm.com]

TASK [Common : Run apt-get upgrade] ******************************************************************************************************************************************************************************
changed: [ubuntu22-docker-test-1.fyre.ibm.com]

TASK [Common : Call Build Packages and Tools Task] ***************************************************************************************************************************************************************
included: /Users/aswin/Personal/Eclipse Adoptium/infrastructure/ansible/playbooks/AdoptOpenJDK_Unix_Playbook/roles/Common/tasks/build_packages_and_tools.yml for ubuntu22-docker-test-1.fyre.ibm.com

TASK [Common : Set package manager var] **************************************************************************************************************************************************************************
ok: [ubuntu22-docker-test-1.fyre.ibm.com]

TASK [Common : Set package manager var for FreeBSD] **************************************************************************************************************************************************************
skipping: [ubuntu22-docker-test-1.fyre.ibm.com]

TASK [Common : Install Test Tool Packages] ***********************************************************************************************************************************************************************
changed: [ubuntu22-docker-test-1.fyre.ibm.com] => (item=acl)
ok: [ubuntu22-docker-test-1.fyre.ibm.com] => (item=perl)
ok: [ubuntu22-docker-test-1.fyre.ibm.com] => (item=xauth)
changed: [ubuntu22-docker-test-1.fyre.ibm.com] => (item=xvfb)
changed: [ubuntu22-docker-test-1.fyre.ibm.com] => (item=binfmt-support)
changed: [ubuntu22-docker-test-1.fyre.ibm.com] => (item=qemu-user-static)
ok: [ubuntu22-docker-test-1.fyre.ibm.com] => (item=unzip)
changed: [ubuntu22-docker-test-1.fyre.ibm.com] => (item=libexpat1-dev)
changed: [ubuntu22-docker-test-1.fyre.ibm.com] => (item=libcurl4-openssl-dev)
changed: [ubuntu22-docker-test-1.fyre.ibm.com] => (item=fakeroot)
changed: [ubuntu22-docker-test-1.fyre.ibm.com] => (item=jq)
changed: [ubuntu22-docker-test-1.fyre.ibm.com] => (item=gnutls-bin)
ok: [ubuntu22-docker-test-1.fyre.ibm.com] => (item=libnss3)
changed: [ubuntu22-docker-test-1.fyre.ibm.com] => (item=libnss3-tools)
changed: [ubuntu22-docker-test-1.fyre.ibm.com] => (item=libnss3-dev)

TASK [Common : Install additional Test Tool Packages for x86_64] *************************************************************************************************************************************************
changed: [ubuntu22-docker-test-1.fyre.ibm.com] => (item=pulseaudio)

TASK [Common : Install additional Packages specific to Ubuntu 16] ************************************************************************************************************************************************
skipping: [ubuntu22-docker-test-1.fyre.ibm.com] => (item=libgstreamer0.10-dev)
skipping: [ubuntu22-docker-test-1.fyre.ibm.com] => (item=libgstreamer-plugins-base0.10-dev)
skipping: [ubuntu22-docker-test-1.fyre.ibm.com] => (item=libmpfr4)
skipping: [ubuntu22-docker-test-1.fyre.ibm.com] => (item=libmpfr4-dbg)
skipping: [ubuntu22-docker-test-1.fyre.ibm.com]

TASK [Common : Install additional Packages specific to Ubuntu 18] ************************************************************************************************************************************************
skipping: [ubuntu22-docker-test-1.fyre.ibm.com] => (item=libgstreamer1.0-dev)
skipping: [ubuntu22-docker-test-1.fyre.ibm.com] => (item=libgstreamer-plugins-base1.0-dev)
skipping: [ubuntu22-docker-test-1.fyre.ibm.com]

TASK [Common : Download LibFFI6 v3.2.1_8 For Ubuntu 20 or 22 on S390X] *******************************************************************************************************************************************
skipping: [ubuntu22-docker-test-1.fyre.ibm.com]

TASK [Common : Install LibFFI6 v3.2.1_8 For Ubuntu 20 or 22 on S390X] ********************************************************************************************************************************************
skipping: [ubuntu22-docker-test-1.fyre.ibm.com]

TASK [Common : Set default java version for x86_64] **************************************************************************************************************************************************************
skipping: [ubuntu22-docker-test-1.fyre.ibm.com]

TASK [Common : Set default java version for armv7l] **************************************************************************************************************************************************************
skipping: [ubuntu22-docker-test-1.fyre.ibm.com]

TASK [Common : Set default java version for ppc64le] *************************************************************************************************************************************************************
skipping: [ubuntu22-docker-test-1.fyre.ibm.com]

TASK [Common : Install 'locales' package] ************************************************************************************************************************************************************************
ok: [ubuntu22-docker-test-1.fyre.ibm.com]
In the above example, the build_tools are skipped as expected.

Is there a use case which would be solved by this PR given that it's already broken when skipping these days?

The use case is basically to skip all related tasks. For example, we sometimes(IBM) won't be needing tasks related to build_tools, so we can easily skip all those related tags. Also we can also skip install_java in RedHat, since we are not using it. These are some of the use cases.

One more VPC run at https://ci.adoptium.net/job/VagrantPlaybookCheck/2034/

One more VPC run at https://ci.adoptium.net/job/VagrantPlaybookCheck/2034/

Run seemed to have failures but not sure if unrelated.

The centos6 and ubuntu16 errors do look unrelated

One more VPC run at https://ci.adoptium.net/job/VagrantPlaybookCheck/2034/

Run seemed to have failures but not sure if unrelated.

Yep as Haroon says I'm not concerned about those in this case.

I've resolved a merge conflict on this so it's running through the github checks again. I think this is safe to go in now. Noting that some doc on this (particularly the fact they can be used to --skip-tags but not --tags) will form part of https://github.com/adoptium/infrastructure/issues/3012


[📚] Google Sign-In documentation is a confusing mix between old and new procedures.

Hi there,
As the title states, I want to notify how configuring Google Sign In - for me - is becoming really confusing if not actually impossible.
This issue follows this issue, as it is now closed as resolved, but I think there's more onto it.
Say we want to initialize a new Flutter Project with Google Sign In. Then, I'd initialize Flutter Fire as mentioned here. Thanks to this issue I acknowledged that google_sign_in doesn't support dart-only initialization.
Then, I search for more documentation. I end up going through the archived (and therefore potentially old) documentation; I follow these instructions. I read:

Dart-only Firebase initialization isn't yet supported by google_sign_in plugin, if you're using Google as an auth provider you'll still have to do the manual installation steps to integrate the Firebase configuration files.

Okay. I'll then follow the manual instructions linked there, and apply whatever I'm told. The manual instructions page is full of warnings that scare me even more:

NOTICE
This page is archived and might not reflect the latest version of the FlutterFire plugins. You can find the latest information on firebase.google.com:
https://firebase.google.com/docs/flutter/setup
CAUTION
Manual installation is not the recommended installation flow. These guides are for existing applications using FlutterFire.

Ok... but I guess I have no choice, right? And again the docs say:

In previous versions of FlutterFire, in order to add Firebase to your projects manual platform specific steps were required, such as downloading a google-services.json file for Android, downloading a GoogleService-Info.plist file for iOS or editing your index.html file for web.
FlutterFire now supports initialization from Dart using the FlutterFire CLI.
The new Dart-only initialization is fully backwards compatible with previous versions of FlutterFire - if you have an existing project with manual initialization, this will continue to work.

Ok... but I need manual installation. It doesn't look like there're alternatives. I then navigate to the iOS documentation. More warnings, ok, skip that and try to follow the procedure.
I add the .plist file as shown there. I then start the app to test that out. I click on a simple "Google Sign In" button. Something goes wrong immediately.
flutter: Error: PlatformException(missing-config, GoogleService-Info.plist file not found and clientId was not provided programmatically., null, null)

This is showing up even though GoogleService-info.plist is clearly there.
I try to search for more intel online and I end up going to the google_sign_in dart package. There, the iOS instructions are different. They mention adding a CFBundleURLTypes to Info.plist. I follow those instructions, too, and try again.
I still get the error:

flutter: Error: PlatformException(missing-config, GoogleService-Info.plist file not found and clientId was not provided programmatically., null, null)

At this point I'm totally lost and I have no clue of what to do. Can we have proper, clearer and good documentation, with one single source of truth?
Shouldn't flutterfire configure handle these details instead, as stated in #96?

Thanks to this issue I acknowledged that google_sign_in doesn't support dart-only initialization.

@lucavenir google_sign_in now seems to support dart-only initialization, as the relevant PR was merged recently: https://github.com/flutter/flutter/issues/96391
Maybe now can you try the plugin with this initialization and see if the experience is smooth ?

I'm not sure what documentation should I follow, though.
It looks like @mono0926 fixed the issue; this comment seems to indicate that I should just install the package, follow its dart instructions and I'll be good to go.
But here's what I did:

Created a new Firebase Project, with firebase init
Created a new Flutter Project flutter create app --org com.mybrand --platforms ios,android
Ran the dart pub global activate flutterfire_cli && flutterfire configure --project=my-project commands
Ran into some issues mentioned in #9169 and fixed them (multidex, initialization, min AndroidSDK, min iOS version)
Added a SHA key for Android (although I'm testing on a iOS simualtor)
Added Google as a Sign In option via the Firebase console
Followed the google_sign_in instructions from pub.dev (except I didn't manually add the .plist file again, as the previous steps already put that in there for me)
Added a simple "google log in button" in my dummy Flutter App too see what happens... output:

flutter: Error: PlatformException(missing-config, GoogleService-Info.plist file not found and clientId was not provided programmatically., null, null)
So, how should one use google sign in at this point?
I think it's crucial to update and have some organic documentation of these "basic" firebase services at the moment. Or at least to have a published and documented workaround.

Hi there,
I just replicated every step cited in here.

Can you provide your flutter project setup details so that we can take a look ?

Sure thing, I created a repo in which I replicate these exact steps. There's a quick description in the readme.
I hope this helps finding the problem

Thanks for these details. In your repo, I see that you mentioned below error:
result: I/flutter ( 7885): Error: PlatformException(sign_in_failed, com.google.android.gms.common.api.ApiException: 10: , null, null)
Which is different from the one you shared earlier:
flutter: Error: PlatformException(missing-config, GoogleService-Info.plist file not found and clientId was not provided programmatically., null, null)
Which one are you getting consistently ?
If it is the former, then there's an open issue in flutter repo for it: https://github.com/flutter/flutter/issues/33393 in which you can check underlying comments and see if they help.

Created a new Firebase Project, with firebase init

I've never tried creating Firebase project from terminal, which I'll try out soon. But maybe you can try to create one from firebase console itself and try too ?

Hi @darshankawar I did, although it doesn't look like this has an impact into my issue.
I can see that the error

flutter: Error: PlatformException(missing-config, GoogleService-Info.plist file not found and clientId was not provided programmatically., null, null)
mentions not being able to find the config file, even though it's right there. google_sign_in needs the clientId from that file OR you can provide it programmatically (i.e. hard code it by copy pasting from the config file). But shouldn't the configuration pick up such info from the file instead?

Sorry for coming back late on this. I cloned your repo and do see same error as you mentioned.
flutter: Error: PlatformException(missing-config, GoogleService-Info.plist file not found and clientId was not provided programmatically., null, null)

I noticed few things in your repo and tried fixing them, but have been getting another unrelated compile error which I need to look into, but below are some things I tried:

Added GoogleService_Info.plist which I didn't see in your project structure.
Added below code in your main() method:

void main() async {
  WidgetsFlutterBinding.ensureInitialized();
  await Firebase.initializeApp(options: DefaultFirebaseOptions.currentPlatform);

  runApp(MyApp());
}

Noticed lot of other FF plugins, so, commented them and kept only firebase_auth, firebase_core and google_sign_in.
Uncommented platform :ios, line in ios/podfile and updated it to 11.0

After above, I am getting:
 "/Users/dhs/Documents/NCFlutter/google-sign-in-test/app/build/ios/Debug-iphonesimulator/Runner.app.dSYM/Contents/Resources/DWARF/Runner"
    Running upload-symbols in Build Phase mode
    Validating build environment for Crashlytics...
    warning: DEBUG_INFORMATION_FORMAT should be set to dwarf-with-dsym for all configurations. This could also be a timing issue, make sure the Firebase run script build phase is the
    last build phase and no other scripts have moved the dSYM from the location Xcode generated it. Unable to process Runner.app.dSYM at path
    /Users/dhs/Documents/NCFlutter/google-sign-in-test/app/build/ios/Debug-iphonesimulator/Runner.app.dSYM
    Make sure your project build settings are generating a dSYM file.

    Processing dSYMs...
    Command PhaseScriptExecution failed with a nonzero exit code

Pointing to crashlytics settings probably.  Can you take a look at this error and see if resolving it and then running the app folder from your project compiles and eventually try to sign in and see if you still get same error or not ?

Hi there,
Thanks for your reply.

Added GoogleService_Info.plist which I didn't see in your project structure.

I can clearly see my GoogleService_Info.plist here. Is there anything I'm missing, here? Even if so, as stated above (step 3) I initialized the project with flutterfire configure. No further actions are required nor asked in the Firebase Console or the Documentation. If anything besides that should be done (and the issues cited in #9169), then it should be documented.

Added below code in your main() method

Thanks, I totally forgot that in this repo, but I always do that in my actual app(s). It doesn't really change much though.

Noticed lot of other FF plugins, so, commented them and kept only firebase_auth, firebase_core and google_sign_in.

How are other Firebase Plugins related to problems with firebase_auth with google_sign_in? Anyways, I plan to use such Plugins in my production app (for obvious reasons), so I don't see this as a problem tbh.

Uncommented platform :ios, line in ios/podfile and updated it to 11.0

If this is a thing, this should be documented. If anything, again, flutterfire configure should have done this for me. Furthermore, since it's still supported, I'd use iOS 10, right?

Pointing to crashlytics settings probably. Can you take a look at this error and see if resolving it and then running the app folder from your project compiles and eventually try to sign in and see if you still get same error or not?

I hardly see what crashlytics has to do with this issue. Furthermore, I never got this error message before, I'm not sure how to help you. This is something you're getting after manually altering some of the files above, so I'm not sure I can reproduce this. I guess I can try.
Anyways, I tried to install the above repo on my Android Device and - still - it doesn't work.
This is the message I get:
Error: PlatformException(sign_in_failed, com.google.android.gms.common.api.ApiException: 10: , null, null)

I'll reach back with more testing on my MacOS soon.

Hi again,

Added GoogleService_Info.plist which I didn't see in your project structure.

I guess you meant to add GoogleService_Info.plist to XCode. If that's the issue, I just did that to try replicate your building error(s). No errors are displayed to me at build time.
Nonetheless, something changed. When I click the "Login with Google" button, the application crashes. Error message shown on the terminal before crash:
flutter: Error: PlatformException(google_sign_in, Your app is missing support for the following URL schemes: com.googleusercontent.apps.561734077415-53ofktkaonkg6497489o3khu3koosk2i, NSInvalidArgumentException, null)

Furhtermore, on further trials, such error message doesn't show anymore: the app just crashes.

flutter: Error: PlatformException(google_sign_in, Your app is missing support for the following URL schemes: com.googleusercontent.apps.561734077415-53ofktkaonkg6497489o3khu3koosk2i, NSInvalidArgumentException, null)

This probably indicates that the google_sign_in setup / config is missing below, as mentioned in plugin's readMe:
Then add the CFBundleURLTypes attributes below into the [my_project]/ios/Runner/Info.plist file.
<!-- Put me in the [my_project]/ios/Runner/Info.plist file -->
<!-- Google Sign-in Section -->
<key>CFBundleURLTypes</key>
<array>
	<dict>
		<key>CFBundleTypeRole</key>
		<string>Editor</string>
		<key>CFBundleURLSchemes</key>
		<array>
			<!-- TODO Replace this value: -->
			<!-- Copied from GoogleService-Info.plist key REVERSED_CLIENT_ID -->
			<string>com.googleusercontent.apps.861823949799-vc35cprkp249096uujjn0vvnmcvjppkn</string>
		</array>
	</dict>
</array>
<!-- End of the Google Sign-in Section -->

This probably indicates that the google_sign_in setup / config is missing below, as mentioned in plugin's readMe

Such configuration is done as explained in the first comment above and as you can see it's right here in my repo.
I thank you for your assistance, but aren't we running in circles at this point?
This issue clearly showcased that the documentation deceives the developer away from correct procedures as there is no clear indication on how to configure Firebase Auth w/ Google Sign In. You yourself experienced such problems, and then even more problems when you tried to address those.
Wonder why?
Cause there's no clear documentation on how to initialize these plugins with Flutter!!
This is what this issue is about.
I'd like to have a clear response - but even better - to have clear and easy-to-find documentation about these topics. This would be really awesome for the community.
Let me know what I can do to help.

Thanks for your feedback and patience. Going ahead and labeling it for further insights from the team on this.
/cc @kevinthecheung @russellwheatley

I can see the platform: ios tag. I can kind-of apply the above statements for android, too, since this is a documentation issue. I'll file a detailed android report while following the documentation and see if I'm able to "log in with google".

@lucavenir When you open the project with Xcode do you see GoogleService-Info.plist file under Runner directory? If not then you need to link the file to xcode. Follow this if you need help https://www.kindacode.com/article/flutter-correctly-adding-googleservices-info-plist-to-ios/

Hi Lucas, flutterfire configure will also install the service file for android and iOS as standard now, it no longer just creates the firebase_options.dart file. Therefore, there are no further procedures other than what is documented here. Sorry for the confusion. We stopped just creating the firebase_options.dart file when we realised that some plugins require the service file. For further details on why, see this comment on the FlutterFire CLI repo.

Hi @russellwheatley! Thank you!! This is very helpful. @adar2378 sorry I didn't reply, I hadn't the time to verify your suggestion.
Thank you for being active, kind and for actually solving problems for us (:


Fix a deadlock

Due to a rather gnarly cycle where this function would call
claim.Release/Terminate which would call Heartbeat/ReleasePartition
which would call getGroupState, but those were meanwhile locked by a
combination of PrintState and refreshMetadata.

RIP Marshal, you were cool for a hot minute, but now built in consumer group balancing in Kafka is a much saner solution.


AXSpace_FastTransition only focuses on application changes

The commit 2087aee appears to have partially fixed application focus in AXLibSpaceTransition but only when the new space has a different application window than the old space (say, switching from 1->2 when space 1 has firefox and space 2 has iterm).
When the windows are the same application, focus is not shifted (eg transition 1->3 when both 1 and 3 have firefox windows). Focus is left on the window of the old space.

I'm actually unable to reproduce this behaviour, tested using Firefox.

Hmm. Yeah, after using this for a few days it's not strictly same/different app as it often forgets focus even on spaces with different apps.
I haven't spent more time tracing the issue yet, but something is causing space switches to not focus a window on the new space. If I get some time I'll try and debug further.

@hunner is it related to this issue? https://github.com/koekeishiya/kwm/issues/551


empty + redrawBuffer breaks player with pre-rendered peaks

Hey,
We have a player we pre-rendered peaks.
We have bounded to the window's resize method, and onresize call:
wavesurfer.empty()
wavesurfer.redrawBuffer()

This works fine after play has been clicked (aka wavesurfer.play()).
The problem is before play has been clicked, if the window has been resized, it breaks the player, and it doesn't play once play is clicked.
Here is a reproduction example:
http://codepen.io/omerts/pen/EZbBZw
Click break -> play, will not work
Click play -> break, will work
Omer

@omerts here you go, a working example.
http://codepen.io/entonbiba/pen/VPqvME

Still an issue?

don't think, works fine in the example

Ok. I'll close this for now then.


Cloud-Proxy for port scanning

First, thanks for all the great projects!
I was testing a target network today that has pretty serious rate limiting with a lockout so I thought it would be a good time to try out this project. Going into it, I thought proxychains would allow me to scan the targets, spreading my traffic across the source addresses as long as the nmap scan didn't use raw sockets (i.e. use -sT option or use a non-root user). It did work, but It appears as though proxychains blocks on connect attempts until the connection is fully established with the final destination or until the connection times out per its configuration.
I guess I am just looking for a sanity check on this conclusion. I used both proxychains-ng and proxychains4 and it seemed to work the same. If this is the case, I guess this approach to port scanning is really only for stealth and not for rate limit evasion. Can you confirm this?

Thanks @freb  :) We're not really going for rate-limiting evasion, though, I think in certain situations that could work. Just depends on the tools we have I guess. I didn't know about this behavior regarding proxychains. Do you have any documentation?

I didn't find anything official discussing this. But the progress of the scan and the nmap and proxychains messages lead me to this conclusion:
[proxychains] Random chain  ...  <IP_ADDRESS>:55594  ...  xxx.yyy.z.135:199 <--socket error or timeout!
[proxychains] Random chain  ...  <IP_ADDRESS>:55582  ...  xxx.yyy.z.134:199 <--socket error or timeout!
adjust_timeouts2: packet supposedly had rtt of 15013575 microseconds.  Ignoring time.
[proxychains] Random chain  ...  <IP_ADDRESS>:55566  ...  xxx.yyy.z.137:199 <--socket error or timeout!
adjust_timeouts2: packet supposedly had rtt of 15013807 microseconds.  Ignoring time.
[proxychains] Random chain  ...  <IP_ADDRESS>:55582  ...  xxx.yyy.z.136:199 <--socket error or timeout!
adjust_timeouts2: packet supposedly had rtt of 15012280 microseconds.  Ignoring time.
[proxychains] Random chain  ...  <IP_ADDRESS>:55599  ...  xxx.yyy.z.135:139 <--socket error or timeout!
adjust_timeouts2: packet supposedly had rtt of 15013243 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of 15013243 microseconds.  Ignoring time.
[proxychains] Random chain  ...  <IP_ADDRESS>:55593  ...  xxx.yyy.z.134:139 <--socket error or timeout!
adjust_timeouts2: packet supposedly had rtt of 15013754 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of 15013754 microseconds.  Ignoring time.
[proxychains] Random chain  ...  <IP_ADDRESS>:55599  ...  xxx.yyy.z.137:139 <--socket error or timeout!

After some more digging, I did finally find one reference to it here: https://www.bamsoftware.com/wiki/Nmap/ProxyScan
This is the first time I've needed this type of functionality for basic port scanning, so I'm not sure how common it is. I mainly wanted to make sure I wasn't missing anything glaring.

Interesting, very good to know @freb :)

@tomsteele, the pentest I was working on last year that prompted this issue came back around. I ended up forking cloud-proxy and adjusting it to work with generic shell commands, including some specific functionality for getting nmap scans split between cloud instances. Not sure if you ever have a need for slowing scan rates way down to evade blacklisting. Either way, here's a link:
https://github.com/aerissecure/cloud-cmd
Thanks a bunch for the great work!


[5.4] Allow for string prefix only when group routing

See: https://github.com/laravel/framework/pull/16531

Probably will hold off on this.

dealio.


Powershell crashing System.OutOfMemoryException,Microsoft.PowerShell.Commands.InvokeWebRequestCommand

Prerequisites

[X] Write a descriptive title.
[X] Make sure you are able to repro it on the latest released version
[X] Search the existing issues.
[X] Refer to the FAQ.
[X] Refer to Differences between Windows PowerShell 5.1 and PowerShell.

Steps to reproduce

Go to android studio download link (My guess is it can reproducilble for any large data file) and copy download link
open powershell, use wget to download i.e.
wget https://redirector.gvt1.com/edgedl/android/studio/ide-zips/2<IP_ADDRESS>/android-studio-2<IP_ADDRESS>-windows.zip
data transfer continue for few mins then finally throws exceptiion

Expected behavior
wget should download the file in current directory

Actual behavior
crashed with error

Error details
wget : Array dimensions exceeded supported range.
At line:1 char:1
+ wget https://redirector.gvt1.com/edgedl/android/studio/ide-zips/2023. ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Invoke-WebRequest], OutOfMemoryException
    + FullyQualifiedErrorId : System.OutOfMemoryException,Microsoft.PowerShell.Commands.InvokeWebRequestCommand

Environment data
Name                           Value
----                           -----
PSVersion                      5.1.19041.4239
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.19041.4239
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>

Visuals

Generally, please note that this repository is not for reporting issues with Windows PowerShell (the legacy, ships-with-Windows PowerShell edition with versions up to 5.1); to report Windows PowerShell issues as well as issues with Microsoft-authored modules that aren't maintained in this repository, use the Feedback Hub application.

However, it looks like the only problem is that you expected wget to refer to wget.exe, whereas in Windows PowerShell wget is (unfortunately) a built-in alias of  PowerShell's Invoke-WebRequest cmdlet (this alias has been removed in PowerShell (Core)).
(The latter doesn't automatically save to a file - you need -OutFile for that; in its absence, the resulting in-memory operation ran into limits.)
To predictably target wget.exe, use its filename extension explicitly:
wget.exe https://redirector.gvt1.com/edgedl/android/studio/ide-zips/2<IP_ADDRESS>/android-studio-2<IP_ADDRESS>-windows.zip

If wget.exe isn't installed, you can use curl.exe, which now ships with Windows:
curl.exe -LO https://redirector.gvt1.com/edgedl/android/studio/ide-zips/2<IP_ADDRESS>/android-studio-2<IP_ADDRESS>-windows.zip


Fixed minor doc error for full-stack guide

I think this command was intended to be:
mkdir lustre-fullstack-guide \
  && cd lustre-fullstack-guide \
  && gleam new client --name app \
  && gleam new server --name app \
  && gleam new shared --name app

I should really get round to writing that properly huh,, thank you!


Apply values and default of array params to its items

Fixes #650

https://github.com/ruby-grape/grape#values

Coverage increased (+1.7%) to 99.645% when pulling 520cd56898ee037d29a07d2845587c080527dc15 on yewton:array-of-enums into 8c3fb898a4562f1fcc9769597e71215431869471 on ruby-grape:master.

Coverage increased (+1.7%) to 99.645% when pulling 46ae27fde3185604e8f83e25801642123ab3f0ec on yewton:array-of-enums into 8c3fb898a4562f1fcc9769597e71215431869471 on ruby-grape:master.

Coverage increased (+1.7%) to 99.645% when pulling 28b24581c203197432f5e1e0bb88c92dec3bc48a on yewton:array-of-enums into 8c3fb898a4562f1fcc9769597e71215431869471 on ruby-grape:master.

Coverage increased (+1.7%) to 99.645% when pulling 28b24581c203197432f5e1e0bb88c92dec3bc48a on yewton:array-of-enums into 8c3fb898a4562f1fcc9769597e71215431869471 on ruby-grape:master.

thanks @yewton :)


wrangler: build against system OpenSSL

Motivation for this change
Wrangler was built against a vendored, static OpenSSL. Use the system
OpenSSL instead to benefit from security updates, etc.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

@danieldk please resolve the merge conflict.

@danieldk please resolve the merge conflict.

Rebased on master.


Add TypeScript loader

P.S. I want to use this (and others in this repo) in the article I'm writing for chaining.
It's working against node nightly

This now works with .js and .ts file extensions present in source, so one could use tsc to do the transpilation. I opted for esbuild to handle the transpilation as it's considerably faster and has better DX, and then added a separate npm script type-check that uses tsc --noEmit on the .js import specifiers files.


Bindings for standalone ML Kit on-device APIs

Just a question: are there any plans for creating Xamarin bindings for the new, separate ML Kit on-device libraries? It sounds very convenient to be able to use all this without a dependency on Firebase.

I am interesting on this too. I would like to can use the on-device ML Kit, also because ML Kit on Firebase it will not be update more, and to can run in the device with no need to internet connection is very interesting.

@ComptonAlvaro FYI while most of the points you are making are true, the current version does run on the device, and runs offline once the model is downloaded, which is no different from the new version. The major difference is that the current version requires a Firebase app to be registered and those Google Play Services plist / json files to be included, which all just seems hopelessly roundabout if you're not using anything else it provides (which personally, I'm not).

yeah guys, maybe it's time to port it... any news about it?

yeah guys, maybe it's time to port it... any news about it?

I discovered this PR is open for the Android counterpart: https://github.com/xamarin/XamarinComponents/pull/933, but there doesn't appear to be much activity on it. I'm working with the old versions for now, but I very much hope the standalone bindings will show up sooner rather than later.

I discovered this PR is open for the Android counterpart: https://github.com/xamarin/XamarinComponents/pull/933, but there doesn't appear to be much activity on it. I'm working with the old versions for now, but I very much hope the standalone bindings will show up sooner rather than later.

For whoever is following this issue here, I'd like to point out that there are some answers in #472, though probably not the answers you're hoping for. The Android counterparts, meanwhile, appear to be available now.

For reference, https://github.com/xamarin/GoogleApisForiOSComponents/issues/472#issuecomment-974899797


how transaction serialization and deserialization?

here I encounter another question. As ethereum uses RLP for serializing data. Does tron uses GoogleProtocol to serialize data ?
How the process is in tron-pathonapi?
where can i find solution ? or can you tell me some idea about how to serialization and deserialization locally?
I am really suffering from it ,looking forward to your reply.
Thanks a lot!

e are not planning to use protobuf yet.


PX-Backup Doc must mention supported OS/Architecture for the service.

Details
Case Number: CS0421486
Created: 23/09/19 1:05 PM
Primary contact: Ambika Nair
Description: From PX-Backup Doc it is not clear supported OS/Architecture .
https://backup.docs.portworx.com/install/on-premise/install-prereq/

Case closed.


Event blocking decorator

We could use an event blocking decorator everywhere we make bidirectional events.
It can just scan for every sub graphic and the every feature within a graphic. It could also take str args to specify specific graphics for which events should be blocked.
Useful in #344

I wonder if there could be a automatic way to do this, when feature events are being called check that the event being called doesn't have the current feature

Ivo suggested looking into observ

One idea to stop callbacks is that when a event is received by an object, it will see if the current value is actually different from the received value. If it's the same, then stop the graph.


tag

Where to get the tag?

Which tag? The Apprise tag? It's the RC push token, you can find how to extract it from MongoDB in the readme.

in the file (example) apprise-config.example.yml specified - gotify://hostname/my-rANd0m-app-tOkEN:

tag: push-gw-admin, myuser-vERy-l0nG-rAnd0M-PuSHtOKen

push-gw-admin - what is it?
myuser-vERy-l0nG-rAnd0M-PuSHtOKen - I understood this, a token from RC

That is an arbitrary string, it could be fluffy-bunny or anything. I chose that one to make testing easier to be able to target myself among other users:

https://github.com/immanuelfodor/rocketchat-push-gateway#build--run
https://github.com/immanuelfodor/rocketchat-push-gateway/search?q=push-gw-admin&type=

tell me, what could be the problem? Rocketcat and Notify are on the same host
{"level":50,"time":"2022-05-18T10:09:05.566Z","pid":13211,"hostname":"rocket","name":"Push","msg":"Error sending push to gateway (1 try) -> {\"response\":{\"statusCode\":404,\"content\":\"{\\\"error\\\":\\\"Not Found\\\",\\\"errorCode\\\":404,\\\"errorDescription\\\":\\\"page not found\\\"}\",\"headers\":{\"connection\":\"close\",\"content-length\":\"73\",\"content-type\":\"application/json\",\"date\":\"Wed, 18 May 2022 10:09:05 GMT\",\"server\":\"nginx/1.14.2\",\"strict-transport-security\":\"max-age=31536000\",\"x-xss-protection\":\"1; mode=block\"},\"ok\":false,\"data\":{\"error\":\"Not Found\",\"errorCode\":404,\"errorDescription\":\"page not found\"}}}"}

This looks like an RC log output. First, you should check the gateway logs, was any request received at all? Second, if both RC and the gateway runs in Docker, you can't use localhost as the gateway's address when entering it into RC, localhost in the RC container will be resolved to itself. In this case, you can either run both containers with host networking (quick&dirty) to make localhost work with the corresponding port, or you can use the host machine's IP address to point to the gateway. Docker might also have an internal reserved domain name to resolve to the host but there is a long thread that it is not always working: https://github.com/docker/for-linux/issues/264 If you run both of them with docker-compose within the same virtual network (same virtual bridge), then you can use the gateway's service name as the hostname.

I realized this, I was inattentive. thanks for the feedback

Okay, I'm closing this for now as it is mostly about support :)


Add tempView.

Coverage increased (+0.76%) to 64.92% when pulling 0afa1d2be81922ba1705b8353d88720ad3d2f735 on tempView into 8558d9d52eded862f093c6a86d7d659a217e6bbe on master.


Update logic in sushy-tools to use stat

Instead of relying on redhat release version which doesn't work with
centos stream 8, check on the actual file existing instead.

Ping - Need anything else from me?


fix(runtime-core): fixed the teleport in the production environment cannot set el

close #10870

fixed the teleport use commentVnode in the production environment cannot set el

duplicate of https://github.com/vuejs/core/pull/10748


build(travis): suppress emails for successful builds

I thought #143 took care of this but apparently not.

When (if) this build succeeds I (and @arizzitano) shouldn't get a single damn email.

Coverage remained the same at 99.579% when pulling 99e8027b2cd2f98091f485fcd3d7f3e5c8850d49 on suppress-successful-build-emails into c24449385c656e9c7de0628710cab698391c6e82 on master.


Make template copy adhere to styleguide

For https://github.com/pypa/warehouse/issues/3167.

Thank you @hugovk !


Custom Element rendered markup is removed during hydration

Describe the bug
At work we use a couple of webcomponents (custom elements) from different teams. We chose webcomponents to be framework agnostic so they work everywhere. If these webcomponents render markup that markup gets removed on the client side when svelte takes over control. This does even happen, if I mark this component as custom element in vite (= has no effect, thus not included in reproducer):
diff --git a/vite.config.js b/vite.config.js
index bbf8c7d..0a479e1 100644
--- a/vite.config.js
+++ b/vite.config.js
@@ -2,5 +2,11 @@ import { sveltekit } from '@sveltejs/kit/vite';
 import { defineConfig } from 'vite';

 export default defineConfig({
-   plugins: [sveltekit()]
+   plugins: [sveltekit({
+       template: {
+           compilerOptions: {
+               isCustomElement: (tag) => tag.startsWith('my-component')
+           }
+       }
+   })]
 });

Pointers in reproducer
The custom element gets defined in app.html and is used in +page.svelte.
Workaround
It works, if I wrap the component in @html (I guess that disables the hydration):
{@html '<my-component></my-component>'}

Maybe that could be done automatically if svelte detects a custom element?
Other tries
I tested this even with https://github.com/sveltejs/svelte/pull/8457 and it still happens. It would be nice, if this case could be considered in this PR.
Reproduction

git clone https://github.com/dritter/sveltekit-custom-element-reproducer
cd sveltekit-custom-element-reproducer
npm i
npm run dev -- --open
Observe that the red element gets removed as soon as the client side takes over

Bildschirmaufzeichnung vom 2023-04-19, 09-54-12.webm
Logs
No response
System Info
System:
    OS: Linux 6.2 Arch Linux
    CPU: (8) x64 Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz
    Memory: 2.87 GB / 15.39 GB
    Container: Yes
    Shell: 5.9 - /usr/bin/zsh
  Binaries:
    Node: 19.9.0 - /usr/bin/node
    npm: 8.19.2 - /usr/bin/npm
  Browsers:
    Chromium: 112.0.5615.165
    Firefox: 112.0.2
  npmPackages:
    @sveltejs/adapter-auto: ^2.0.0 => 2.0.0
    @sveltejs/kit: ^1.5.0 => 1.15.5
    svelte: ^3.54.0 => 3.58.0
    vite: ^4.2.0 => 4.2.1

Severity
annoyance
Additional Information
No response

The problem is that Svelte during hydration expects the DOM to look the same as when it was server-rendered. But the custom element already scaffolded itself, so Svelte trashes it. That makes sense for normal elements because it aligns Svelte and the DOM, but in case of custom elements ... tricky.
Another workaround is to defer registration of the custom element a bit until Svelte has finished hydrating.

Thanks for looking into this @dummdidumm
Defering the registration of the custom element is unfortunately not an option, because of two reasons:

We want to keep framework agnostic, to avoid them being cluttered with if (isFrameworkA()) { ... } elseif (isFrameworkB()) { ... } code.
Even if we would take this option, we would not know for how long we should defer that registration. I sketched a clumsy setTimeout() Version, but that would be a guessed value, that differs from device to device. It may be deferrable when using the custom element in an onMount() hook, but that would lead to my initial workaround ({@html ...}).


Csv download

@riyer15 and my changes for csv/search page stuff.
Removed need to query dom for grabbing info, now keeping 2 sources of information (1 displayed on the DOM and the second that is just an object  storing all of the  org information from the beginning).
CSV now contains the following columns:

name
description
email
phone
address
website
hours
services
tags

@abhisuri97 any way to still show results in alphabetical order but still get it to work? If not, can we merge this in?


Topic name on arrows not highlighted/colored anymore

I didn't track down when the arrow coloration disappeared but I noticed that:
On the tutorial screenshot:

Current state as of 2017-05-18 11-53-19:

Addressed by ros-visualization/qt_gui_core#85.


Error: Could not find a version that satisfies the requirement symphony-bdk-python>=2.0.0 (from versions: none)

I have created a project with yo @finos/symphony, and then when I run pip3 install -r requirements.txt command, the bellow error occurs. How could it be solved?
$ python3 --version
Python 3.6.9

$ cat requirements.txt
symphony-bdk-python>=2.0.0
Jinja2~=3.0

$ pip3 install -r requirements.txt
Defaulting to user installation because normal site-packages is not writeable
ERROR: Could not find a version that satisfies the requirement symphony-bdk-python>=2.0.0 (from versions: none)
ERROR: No matching distribution found for symphony-bdk-python>=2.0.0

Sure, thanks for the answer.


ADDED: humaneval-x rust integration

Humaneval-x integration with rust
With this pull request, we introduce the possiblity of evaluating code generations written in rust.
The main features are:

Humaneval-rust: Full translation of the 164 problems consisting of the initial benchmark into rust language
Evaluation environment for rust in Humaneval-x: Integration of humaneval-x for rust, achieving the evaluation based on the compilation and execution of the generated code following the humaneval-x metrics and procedures.

Additions

evaluate_humaneval_x.py script created based on homonymous .sh script

Added a path for the rust language on methods process_humaneval_test and check_correctness

Path for the dataset: CODEGEEX/codegeex/humaneval-x/rust

Path for the generations: CODEGEEX/generations

Added compilation and execution environment path: CODEGEEX/codegeex/benchmark/rust

Modifications

evaluate_humnaeval_x.py copied into  CODEGEEX/codegeex/benchmark in order to debug and execute script evaluate_humaneval_x.py from CODEGEEX/scripts

Testing
For testing uses, we have included a dummy generation of rust code located in CODEGEEX/generations/humaneval_rust_generations_results.jsonl.gz. This generations consists of a copy of every canonical solutions for every problem imitating possibles generations, in order to achieve a pass@k of 1.0
In order to run it. Once codegeex is installed following the project README.md.
You can run the following command:
bash ./scripts/evaluate_humaneval_x.sh ./generations/humaneval_rust_generations.jsonl.gz rust 64 300

or run the./scripts/evaluate_humaneval_x.py script (especially for debugging)
Noteworthy details

For every compilation/execution. It can be found a rust_task_id.jsonl (codegeex/benchmark/rust/tmp/logs) giving further information about its process.
Due to the compilation time needed for cargo in every thread, the standard timeout is >300 to ensure every task is compilated and executed.
The Rust/32 test has unexpected behavior due to the nature of the test code (not just for rust). For the moment, the test code is commented to not interrupt the process of evaluating the rust code. But further work is needed to fix it.

Work done by @antferdom and @roG0d.

Great work on the Rust integration of HumanEval-X! Thanks!

Great work on the Rust integration of HumanEval-X! Thanks!

@roG0d Can you elaborate on The Rust/32 test has unexpected behavior due to the nature of the test code (not just for rust). For the moment, the test code is commented to not interrupt the process of evaluating the rust code. But further work is needed to fix it.? For me the test is passing when I uncomment it as expected.

Thanks! Also unlike the other languages, in Rust the prompt field does not contain the declaration field, correct? I.e. at evaluation, we should concat \nfn main(){ \n } \n, prompt & declaration as input to the model, right?

Yes, apart from that subtle change, the Rust dataset has the same parts as the others. It was made this way to individually have the function header from the docstring. Part of evaluate_humaneval_x.py

Yes @Muennighoff, apart from that subtle change, the Rust dataset has the same parts as the others. It was made this way to individually have the function header from the docstring. So we could give it to the model for generations.
For evaluation inside Humaneval-X the program is already created as you can see here in this part of evaluate_humaneval_x.py where what you said its already done!

Sorry for digging this back up - I think I had misunderstood.
At generation time you do:
prompt + declaration
At evaluation time you do:
\nfn main(){ \n } \n + declaration + generated_code + tests
correct?


Could set friend conversation in left side and my conversation in right side?

My Setup

Operating System: Win10
App Version: 2.17.11
Installation type: exe

[X] I have tested with the latest version
[X] I can simulate the issue easily

Description
At present, the content of the conversation will be on the left, but when there are many messages, it will be very slow to find someone or the message will become not clear, and it is not easy to distinguish which one is a friend’s message and which one is sent by oneself, whether it is possible to combine all the messages of a friend Displayed on the left, and self-posted messages on the right?
Please see attachment.Left side is my friend and right side is me.

Current Behavior
In this time all conversation show in left side.
Expected Behavior
set friend conversation in left side and my conversation in right side

Nice idea!
But I think it need to be implemented in Rocket.Chat UI\UX (Front End) but not in Electron application.

Thank you for liking my idea, then where should I post my idea? Or could you help me?? Thank you

I guess here https://github.com/RocketChat/Rocket.Chat/issues
But better wait until someone from RC team transfer that issue to right place.
If I'm not wrong about that all.


Typescript Support

Are there any plans to support typescript ?

Hi!
Lapce should already have typescript syntax highlighting. Lapce can also support TypeScript Language Server in principle, but it's not done currently. We are still working on the basics and wider language support should come at a later stage, I believe.
Having said that, contributions to enable LSP support for various languages are welcome!

How to setup typescript?

Typescript is a must be :P

There is already a typescript plugin https://github.com/panekj/lapce-typescript/tree/wip but it currently doesn't work

typescript lsp is working for me for sometime. Thanks to @panekj , does this issue require anything else ?

It was fixed via #1263 (probably)


feat: add some fonts support (Fixes #32)

Thanks for the PR, can we try without the file document? as others like TS/JS I've tried to not use a file wrapper

@misolori okey, I will try later.

Going to close this PR as it's a bit outdated and we've added some fonts files (#32)