[BUG]  rpc error: code = DeadlineExceeded when i try to attach any volumes on my kubernetes cluster

Describe the bug (🐛 if you encounter this issue)
Longhorn can't attach any volume to any node, i have longhorn installed on my kubernetes cluster, all the longhorn pods are running 1/1, but when i tried to install postgresql on my cluster, the pod are stucked on container creating status, the pod says that longhorn cant attach, saying the error: Warning  FailedAttachVolume  9s    attachdetach-controller  AttachVolume.Attach failed for volume "pvc-f6a5a7b8-a053-4cf0-be54-5ae8141b4b0b" : rpc error: code = DeadlineExceeded desc = volume pvc-f6a5a7b8-a053-4cf0-be54-5ae8141b4b0b failed to attach to node vmrmwrknodeprod06
I have a kubernetes cluster with 9 nodes with sufficient space( the pvc needs 8gb i have 2 tb ) and i've already tried the solution of reducing replica count to 1 and i've already turned on the Replica Node Level Soft Anti-Affinity.
To Reproduce
Steps to reproduce the behavior:
Install longhorn on a kubernetes cluster
Try to create or attach a pvc
Expected behavior
The pvc attached succesfulyly
Log or Support bundle
Warning  FailedAttachVolume  9s    attachdetach-controller  AttachVolume.Attach failed for volume "pvc-f6a5a7b8-a053-4cf0-be54-5ae8141b4b0b" : rpc error: code = DeadlineExceeded desc = volume pvc-f6a5a7b8-a053-4cf0-be54-5ae8141b4b0b failed to attach to node vmrmwrknodeprod06
This error occurs on EVERY node of my cluster.
Environment

Longhorn version: 1.4.2
Installation method (e.g. Rancher Catalog App/Helm/Kubectl): kubectl
Kubernetes distro (e.g. RKE/K3s/EKS/OpenShift) and version: RKE2

Number of management node in the cluster: 3
Number of worker node in the cluster: 7

Node config

OS type and version: Rocky Linux 8
CPU per node: 16 CPU
Memory per node: 64GB
Disk type(e.g. SSD/NVMe): Slow Disk HD
Network bandwidth between the nodes: Don't Know

Underlying Infrastructure (e.g. on AWS/GCE, EKS/GKE, VMWare/KVM, Baremetal):
Number of Longhorn volumes in the cluster: 1

Additional context
Add any other context about the problem here.

@Anddiy Please provide the support bundle. Thanks.

@innobead , The only logs i've found is the pods logs, im trying to run a postgresql pod on my cluster, the pvc has been created succesfully as we can see here:
[15:43] root@vmrmmstnodeprod01 [longhorn]:# kubectl get pvc -n bmc-helix-platform
NAME                                       STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS   AGE
data-postgres-postgresql-ha-postgresql-0   Bound    pvc-2e771f20-7bfd-47de-bb1d-cee40d37f198   8Gi        RWO            nfs-storage    17m

But in longhorn U.I, the pvc is stuck in attach and dettaching, i've found that this is happening because the postgresql pod are saying this error:
Warning  FailedAttachVolume  16s   attachdetach-controller  AttachVolume.Attach failed for volume "pvc-2e771f20-7bfd-47de-bb1d-cee40d37f198" : rpc error: code = DeadlineExceeded desc = volume pvc-2e771f20-7bfd-47de-bb1d-cee40d37f198 failed to attach to node vmrmwrknodeprod08

With that i've learned that the pvc is attaching and dettached because when this error occurs, the kubernetes kill the pod and recreated it on another node, so longhorn dettach the node and try to attach again, but when it try to attach, this errors occurs, what info excluding these you need?

@innobead , heres the support bundle:
supportbundle_d0c1d097-f6a4-4bf9-90b1-89af53b33d09_2023-05-26T19-33-20Z.zip

Thanks @Anddiy. Haven't yet had time to fully look through the provided bundle, but we're seeing a lot of iSCSI related errors related to that volume on multiple nodes. For example:
https://github.com/longhorn/longhorn/issues/5381

Maybe you forgot to install open-iscsi in this cluster before deploying Longhorn? If not, we can continue to help troubleshoot.
https://github.com/longhorn/longhorn/issues/3507#issuecomment-1006831026
https://longhorn.io/docs/1.5.0/deploy/install/#installation-requirements

Thanks for the info @ejweber , i will check that on my nodes

@ejweber , i've checked here and i already have openiscsi installed on my nodes:
[16:35] root@vmrmwrknodeprod03 [~]:# yum install iscsi-initiator-utils
Last metadata expiration check: 5:27:42 ago on Mon 29 May 2023 11:08:02 AM -03.
Package iscsi-initiator-utils-<IP_ADDRESS>-4.git095f59c.el8.x86_64 is already installed.
Dependencies resolved.
Nothing to do.
Complete!

Thanks @Anddiy. Can you also check that the service is running? That was the issue in https://github.com/longhorn/longhorn/issues/3507#issuecomment-1006831026.

@ejweber I Am facing the same FailedAttachVolume issue with only difference  in confs for storage-class being
numberOfReplicas: "2"
staleReplicaTimeout: "30"

I have checked that in my case iscsid.service is up and running

I have the same issue. Did you find out what it was?

Ok, I'm not 100% sure the logs we have are indicative of this, but we have been seeing a number of iSCSI issues recently in Rocky related to an update to the container-selinux package. You can follow along at https://github.com/longhorn/longhorn/issues/5627.
If you are running an up-to-date version of Rocky/RHEL, please check:
rpm -q container-selinux
# Am I running greater than v2.189?

getenforce
# Am I running SELinux in enforcing mode?

ausearch -m AVC | grep iscsd_t
# Am I seeing `iscsd_t` and `dac_override` related SELinux denials?

If you can answer yes to all three questions, you are likely hitting that issue.

There was a typo in my command, unfortunately. Try ausearch -m AVC | grep iscsid_t. I have updated the comment above to avoid confusing others. Just drop the grep if you still get nothing and/or look in journalctl for related messages.
Another quick test might be to fully detach the volume, then run setenforce Permissive on a node, then attach the volume to that node. If attaching works, you are almost certainly hitting #5627. You may or may not be "allowed" to do this on the system you are using.
I'm working on getting a KB out and a DaemonSet that can fix things automatically, but the medium term solution will essentially be to execute echo '(allow iscsid_t self (capability (dac_override)))' > local_longhorn.cil && semodule -vi local_longhorn.cil on every node to give iscsiadm a permission is currently requires to do its job.

grep
type=SYSCALL msg=audit(1686131484.778:2573): arch=c000003e syscall=83 success=no exit=-13 a0=557457b665d0 a1=1f8 a2=fffffffffffffeb0 a3=7ffd86516cb7 items=0 ppid=1187339 pid=1187829 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="iscsiadm" exe="/usr/sbin/iscsiadm" subj=system_u:system_r:iscsid_t:s0 key=(null)
type=AVC msg=audit(1686131484.778:2573): avc:  denied  { dac_override } for  pid=1187829 comm="iscsiadm" capability=1  scontext=system_u:system_r:iscsid_t:s0 tcontext=system_u:system_r:iscsid_t:s0 tclass=capability permissive=0
type=SYSCALL msg=audit(1686138208.882:2989): arch=c000003e syscall=59 success=yes exit=0 a0=7ffdf6cdd1a0 a1=7ffdf6cdd3e0 a2=7ffdf6cdd3f8 a3=0 items=0 ppid=1341909 pid=1341947 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="iscsiadm" exe="/usr/sbin/iscsiadm" subj=system_u:system_r:iscsid_t:s0 key=(null)
type=AVC msg=audit(1686138208.882:2989): avc:  denied  { read } for  pid=1341947 comm="iscsiadm" path="/dev/null" dev="tmpfs" ino=7624775 scontext=system_u:system_r:iscsid_t:s0 tcontext=system_u:object_r:container_runtime_tmpfs_t:s0 tclass=chr_file permissive=0

journalctl
juin 08 17:08:45 master avahi-daemon[1309]: New relevant interface vethcd226a42.IPv6 for mDNS.
juin 08 17:08:45 master avahi-daemon[1309]: Registering new address record for fe80::2441:76ff:fe47:ca66 on vethcd226a42.*.
juin 08 17:08:45 master kubelet[627130]: I0608 17:08:45.984915  627130 pod_startup_latency_tracker.go:102] "Observed pod startup duration" pod="longhorn-system/longhorn-csi-plugin-r7cb5" podStartSL>
juin 08 17:08:46 master avahi-daemon[1309]: Joining mDNS multicast group on interface vethf6cf4c46.IPv6 with address fe80::1c49:55ff:fe17:dfb3.
juin 08 17:08:46 master avahi-daemon[1309]: New relevant interface vethf6cf4c46.IPv6 for mDNS.
juin 08 17:08:46 master avahi-daemon[1309]: Registering new address record for fe80::1c49:55ff:fe17:dfb3 on vethf6cf4c46.*.
juin 08 17:08:46 master kubelet[627130]: I0608 17:08:46.382253  627130 pod_startup_latency_tracker.go:102] "Observed pod startup duration" pod="longhorn-system/csi-snapshotter-588bd6f85d-bm8pq" pod>
juin 08 17:08:46 master kubelet[627130]: I0608 17:08:46.543372  627130 csi_plugin.go:99] kubernetes.io/csi: Trying to validate a new CSI Driver with name: driver.longhorn.io endpoint: /var/lib/kube>
juin 08 17:08:46 master kubelet[627130]: I0608 17:08:46.543413  627130 csi_plugin.go:112] kubernetes.io/csi: Register new plugin with name: driver.longhorn.io at endpoint: /var/lib/kubelet/plugins/>```

Using setenforce Permissive did detach the volume, but in the end, I tried to use echo '(allow iscsid_t self (capability (dac_override)))' > local_longhorn.cil && semodule -vi local_longhorn.cil, but it did not work.

Hello @ejweber,
I was wondering if there have been any updates on the issue mentioned above. Could you please clarify what might be causing this issue and any potential solutions?
Thank you in advance for your help.

Hello @ejweber, I wanted to provide you with an update on my situation. After several attempts, I managed to get the volumes attached, but the process was far from seamless.  Now, things seem to be working.
However, I have been encountering a warning at the start of each pod launch:
Events:
  Type     Reason                  Age                From                     Message
  ----     ------                  ----               ----                     -------
  Warning  FailedScheduling        56m (x2 over 56m)  default-scheduler        0/2 nodes are available: pod has unbound immediate PersistentVolumeClaims. preemption: 0/2 nodes are available: 2 No preemption victims found for incoming pod..
  Normal   Scheduled               56m                default-scheduler        Successfully assigned default/keycloak-postgresql-0 to master
  Normal   SuccessfulAttachVolume  56m                attachdetach-controller  AttachVolume.Attach succeeded for volume "pvc-c1287895-8a07-4906-b507-9e26f24b7722"
  Normal   Pulled                  55m                kubelet                  Container image "docker.io/bitnami/postgresql:11.14.0-debian-10-r28" already present on machine
  Normal   Created                 55m                kubelet                  Created container keycloak-postgresql
  Normal   Started                 55m                kubelet                  Started container keycloak-postgresql

In the longhorn dashboard the status is Degraded...

I'm not sure why this is happening, but it suggests that there might still be an underlying issue. Could this be related to the original problem or is it something new? If you have any advice or thoughts.

I am thinking the second SELinux denial I previously called out is/was a red herring. I have been unable to reproduce it (or any potential negative effects) in my environment, but will still be interested in more data on it in the future.
It looks like there may be resource constraints in the cluster, as that is usually the reason for preemption related messages. The "pod has unbound immediate PersistentVolumeClaims" is no big deal. It just means the scheduler got to the pod before Longhorn finished creating the volume. This is only a problem if it persists for some long period of time.
If the degraded volumes are a persistent issue, I recommend opening a new issue with some additional information, like:

Complete volume spec (so we can see how many replicas are expected and whether or not data-locality is enabled)
Output of kubectl get -oyaml -n longhorn-system replicas (so we can see the status of the replicas that have been created).
If there is a replica scheduled to a node that can't run for some reason, the logs of longhorn-manager running on that node.
The logs of the longhorn-manager that owns the volume.

We can get at all of this if you are able to upload a support bundle.
My first, best guess with limited information is that this is unrelated to the issues above and that some kind of resource pressure is preventing replicas from running.

I also ran into the same rpc error which turned out to be for a different reason but I'll share here for anyone who finds themselves looking at the same thing.
In my instance-manager logs I was getting:
libkmod: kmod_module_insert_module: could not find module by name='iscsi_tcp'\niscsiadm: Could not insert module tcp. Kmod error -2\niscsiadm: iSCSI driver tcp is not loaded. Load the module then retry the command.\niscsiadm: Could not perform SendTargets discovery: iSCSI driver not found. Please make sure it is loaded, and retry the operation\n: exit status 12"
This was because my kernel didn't include this module, as detailed here: https://github.com/longhorn/longhorn/issues/1853

longhorn in kind. iscsid is error, so vpc can't mount. iscsid say "sendmsg: bug? ctrl_fd 5".


Replace ms-air-aiagility... with AzureCLI tasks

In https://github.com/microsoft/MLOpsPython/blob/master/.pipelines/diabetes_regression-ci.yml there are now 3 places where some tasks starting with ms-air-aiagility., and those are:

ms-air-aiagility.vss-services-azureml.azureml-restApi-task.MLPublishedPipelineRestAPITask@0
ms-air-aiagility.vss-services-azureml.azureml-model-deploy-task.AMLModelDeploy@0 (used twice)

These are available when one installs the azure machine learning extension into azure devops. The alternative to using these tasks is to use the AzureCLI@2 task in combination with az ml.... There are some issues with using the ms-air-aiagility tasks:

They are not documented anywhere. This repo is pretty much the only use I can find of them, and one has to guess what they do.
They make it very hard to debug a pipeline by manually re-doing the steps.
They can not be used in other CI tools like e.g.  (the Microsoft owned) github actions.

One place where the alternative approach (az ml ...) is used is this Microsoft repository.
As an example, I have replaced the ACI call to ms-air-aiagility.vss-services-azureml.azureml-model-deploy-task.AMLModelDeploy@0 with the following code:
    - task: AzureCLI@2
      displayName: 'Invoke and monitor ML pipeline'
      inputs:
        azureSubscription: '$(AZURE_RM_SVC_CONNECTION)'
        scriptLocation: inlineScript
        scriptType: 'bash'
        workingDirectory: '$(Build.SourcesDirectory)/$(SOURCES_DIR_TRAIN)/scoring'
        inlineScript: |
          az extension add -n azure-cli-ml
          az ml folder attach -w $(WORKSPACE_NAME) -g $(RESOURCE_GROUP)
          az ml model deploy  -n $(ACI_DEPLOYMENT_NAME) --model $(MODEL_NAME):$(MODEL_VERSION) --ic $(Build.SourcesDirectory)/$(SOURCES_DIR_TRAIN)/scoring/inference_config.yml --dc $(Build.SourcesDirectory)/$(SOURCES_DIR_TRAIN)/scoring/deployment_config_aci.yml -g $(RESOURCE_GROUP) -w $(WORKSPACE_NAME) --overwrite

The other task, MLPublishedPipelineRestAPITask is a bit more work to replace, since it waits for the pipeline to complete, and I did not find a direct az command to do the same (so I had to write a bash loop). But that is good incentive for you guys (Microsoft) to add a --wait-for-completion flag to az ml run submit-pipeline ;-)

We are planning to change our deploy steps to use the CLI instead - I have a PR to use the CLI in a new split pipeline approach - https://github.com/microsoft/MLOpsPython/pull/278/files (.pipelines/diabetes_regression-cd-deploy.yml). A separate PR will follow to move the deploy steps in diabetes_regression-ci.yml to use the CLI. :)
As for the MLPublishedPipelineRestAPITask, we won't be able to replace that as it is a server task made for long-running pipeline jobs. Here's a little more information: https://marketplace.visualstudio.com/items?itemName=ms-air-aiagility.vss-services-azureml.

Good that you are replacing the AMLModelDeploy tasks :-)
Regarding MLPublishedPipelineRestAPITask, why is it relevant that it is implemented as a server tasks? Is there a fundamental reason why it can not just be a normal tasks which waits for the pipeline to complete? Is it because server tasks as cheaper (since they don't need an agent)?
I would contest that the cons of having an important part of the pipeline be a non-translatable black box is so large that the pros should be significant. Are they?

Hi, why is it necessary to split the pipelines? I think its perfectly fine to have CI and CD as one single pipeline but as separate stages i.e. the current approach is good.
But yes, I'd like to see ms-air-aiagility tasks replaced with AzureCLI@2 tasks as there appears to be some bugs with ms-air-aiagility and the source code for it is not public.

In practice we don't usually see a single pipeline serve for CI/CD. Generally there different teams collaborating on the CI process (reproducible training) and CD process (packaging+deployment). We're taking this approach in the repo because of the pattern we've seen with customers. Every model produced isn't necessarily going to be deployed. There's usually a security boundary between the dev and prod environment and gates.  That correlates with the separation of data scientists model development activities and the app engineers/ML engineering activities of packaging and deploying. If a single pipeline handles the entire CI/CD pipeline, everyone has access to the entire development pipeline which is a huge security and scalability concern.

Thanks Shiv, that has brought up some really good points which I hadn't considered with regards to various teams being responsible for different parts, and security and access to a pipeline. I'll take on board your comment :)

no problem, I'll go ahead and close out this issue, let us know if you have any other problems!

Hi @shivp950 , I think this issue relates to replacing ms-air-aiagility tasks with AzureCLI@2 tasks. Could this issue please remain open until the change is merged into master?

Running into #153 today and making support enquiries to create a new service connection as privileges are limited. Pipeline invocation wasn't included in v2 CLI last I looked (and v2 CLI preview has been non-functional for a couple of months as of writing).
Definitely agree this issue should reopen

In https://github.com/microsoft/MLOpsPython/blob/master/.pipelines/diabetes_regression-ci.yml there are now 3 places where some tasks starting with ms-air-aiagility., and those are:

ms-air-aiagility.vss-services-azureml.azureml-restApi-task.MLPublishedPipelineRestAPITask@0
ms-air-aiagility.vss-services-azureml.azureml-model-deploy-task.AMLModelDeploy@0 (used twice)

These are available when one installs the azure machine learning extension into azure devops. The alternative to using these tasks is to use the AzureCLI@2 task in combination with az ml.... There are some issues with using the ms-air-aiagility tasks:

They are not documented anywhere. This repo is pretty much the only use I can find of them, and one has to guess what they do.
They make it very hard to debug a pipeline by manually re-doing the steps.
They can not be used in other CI tools like e.g.  (the Microsoft owned) github actions.

One place where the alternative approach (az ml ...) is used is this Microsoft repository.
As an example, I have replaced the ACI call to ms-air-aiagility.vss-services-azureml.azureml-model-deploy-task.AMLModelDeploy@0 with the following code:
    - task: AzureCLI@2
      displayName: 'Invoke and monitor ML pipeline'
      inputs:
        azureSubscription: '$(AZURE_RM_SVC_CONNECTION)'
        scriptLocation: inlineScript
        scriptType: 'bash'
        workingDirectory: '$(Build.SourcesDirectory)/$(SOURCES_DIR_TRAIN)/scoring'
        inlineScript: |
          az extension add -n azure-cli-ml
          az ml folder attach -w $(WORKSPACE_NAME) -g $(RESOURCE_GROUP)
          az ml model deploy  -n $(ACI_DEPLOYMENT_NAME) --model $(MODEL_NAME):$(MODEL_VERSION) --ic $(Build.SourcesDirectory)/$(SOURCES_DIR_TRAIN)/scoring/inference_config.yml --dc $(Build.SourcesDirectory)/$(SOURCES_DIR_TRAIN)/scoring/deployment_config_aci.yml -g $(RESOURCE_GROUP) -w $(WORKSPACE_NAME) --overwrite

The other task, MLPublishedPipelineRestAPITask is a bit more work to replace, since it waits for the pipeline to complete, and I did not find a direct az command to do the same (so I had to write a bash loop). But that is good incentive for you guys (Microsoft) to add a --wait-for-completion flag to az ml run submit-pipeline ;-)

@epa095 hi can you share a snippet of the bash loop you wrote to handle the  'wait-for-completion' issue. I find that replacing the ms-air-aiagility task i don't have a way to wait for completion, this causes the next job to run and fail as the results from training are not ready yet.

Sry @Thrillz, that bash loop exists in a closed repository several emplyments ago :-p


non needed html test result files generated

TestAllWithGeneration func of  analysis_output_test.go generates html files which are not required for the testing.
fyi @adisos

fixed here:
https://github.com/np-guard/vpc-network-config-analyzer/pull/598

a better approach is to avoid generation rather than adding to gitignore
there is already mechanism to avoid generation of drawoi, can be also used for the html files


[GraphSDK] generate proto classes using build.rs

Story
Currently we are included generated proto class in git and we need to make it part of them build process
Accpetence criterea

Use build.rs in jni to build rust and java proto class
remove generated classes from git

Not a priority.


python312Packages.qcs-sdk-python: 0.19.2 -> 0.19.3

Description of changes
Diff: https://github.com/rigetti/qcs-sdk-rust/compare/python/v0.19.2...python/v0.19.3
Changelog: https://github.com/rigetti/qcs-sdk-rust/blob/python/v0.19.3/crates/python/CHANGELOG.md

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 336864 run on x86_64-linux 1

8 packages marked as broken and skipped:

python311Packages.cirq
python311Packages.cirq-rigetti
python311Packages.cirq-rigetti.dist
python311Packages.cirq.dist
python312Packages.cirq
python312Packages.cirq-rigetti
python312Packages.cirq-rigetti.dist
python312Packages.cirq.dist

8 packages built:

python311Packages.pyquil
python311Packages.pyquil.dist
python311Packages.qcs-sdk-python
python311Packages.qcs-sdk-python.dist
python312Packages.pyquil
python312Packages.pyquil.dist
python312Packages.qcs-sdk-python
python312Packages.qcs-sdk-python.dist


Move expansion state of ExpansionTile to ExpansionTileController

This PR moves the expansion state from the ExpansionTile to the ExpansionTileController in order to allow interacting with the controller without an ExpansionTile being attached. As a side effect, one can now attach one ExpansionTileController to more then one ExpansionTile for syncing the expansion easily.
As a down side, ExpansionTileController now requires disposing. (Is this a breaking change? / Does this require an migration guide?)
Fixes #137831
Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I signed the CLA.
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is test-exempt.
[ ] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

Please see https://github.com/flutter/flutter/issues/137831#issuecomment-1801464367

We will need to consider https://github.com/flutter/flutter/issues/138153#issuecomment-1805295295 to land this.

(triage) @fischerscode Do you still have plans to come back to this one and address the feedback given above?

@fischerscode since we have not heard back for a while, I am going to close this PR to remove it from our review queue. Thank you for contributing! I have updated https://github.com/flutter/flutter/issues/137831 to reference this issue as a partial fix that ca be picked up.


Apply an attempt to make setLocation e2e stable with Genycloud

Description

This pull request is associated with #1935.

In this pull request, I have changed our test-app's usage of @react-native-community/geolocation in an attempt to make it more stable with Genymotion-cloud emulators. ATM, these tests are flaky on our CI.
Follow-up:

[ ] If this proves to work - must updates API notes to say Geolocation.watchLocation is preferable when Genymotion is used.

Not waiting for a review here. With CI being green, we just need to merge and see.


ERA-8871: Gear icon for direct management of observation points

What does this PR do?

it adds gear icon link for direct management of observation points

How does it look
before

after

Relevant link(s)

Tracking tickets: ERA-8871
Hosted demo environments

@gaboDev how much effort is necessary here to get this out of Draft status?


Create main cpp function with a simple "welcome to the app" type message

Create a main() function that simply displays to the terminal screen a 'welcome' message for the application.

Created main.cpp with a main() function.  This is now complete.


Rename of pum hl_group is incomplete

Problem:  Rename of pum hl_group is incomplete.
Solution: Also rename in the test.  Rename to user_hlattr in code to
avoid confusion with pum_extra.

Waiting for #15353

this name more better

thanks, can you please rebase now?

thanks!


Display more relevant data

At the moment there's quite a bit of white space in our 2-column data display. This changes what's displayed and what's filtered out to something subjectively more relevant (i.e. more major version infos, less hardly used minor version infos):

major versions: >0.5 -> >0.1
minor versions: no limit -> >0.1
minor compiler versions: no limit -> >0.1 or part of "Others" group

I only made sure the server starts, I couldn't actually check that it actually works/does what I want to do due to missing data - so needs to be taken for a test spin first.

Did anyone have a chance to look at this/try it out yet?

Looks ok, needa deploying tho, as it's not automated.


npm install request necessary

please add the point "npm install request" to your installation instructions. I'm fairly new to MagicMirror and had to dig a lot to find a solution to the problem

As you might have seen in #126 the entire requests library should be replaced with something better - just adding it to the dependencies isn't enough long-term.


Edited documents for consistency, spelling, grammar, and clarity

Read the updated documentation and made some edits providing consistency, while fixing some spelling, grammar, and punctuation issues. Also added some clarity at certain points, but not much.

This looks awesome, good job! :+1:


Correction for raw affiliation UMR SPO INRA/SupAgro/UM I, Montpellier, France<EMAIL_ADDRESS>

Correction needed for raw affiliation UMR SPO INRA/SupAgro/UM I, Montpellier, France<EMAIL_ADDRESS>raw_affiliation_name: UMR SPO INRA/SupAgro/UM I, Montpellier, France<EMAIL_ADDRESS>new_rors: 03rnk6m14;04w07sc25
previous_rors: 03rnk6m14
works_examples: W2014578896
contact: 19d79a8bf3ab962cace1b6ebdc3ad25e:f9e251fa3bcb7ffa73d59527e5e41157e54a @ inrae.fr

This issue was accepted and ingested by the OpenAlex team on 2024-10-09. The new affiliations should be visible within the next 7 days.


NoSuchBeanDefinitionException: No qualifying bean of type 'graphql.GraphQL' available:

I run into this error when running graphql-java-generator and graphq-java-kickstart.
nested exception is org.springframework.beans.factory.NoSuchBeanDefinitionException: No qualifying bean of type 'graphql.GraphQL' available: expected at least 1 bean which qualifies as autowire candidate NoSuchBeanDefinitionException: No qualifying bean of type 'graphql.GraphQL' available:
Here is the snippet from my pom.xml
	<graphql-maven-plugin.version>1.11</graphql-maven-plugin.version>
</properties>
	<parent>
		<groupId>org.springframework.boot</groupId>
		<artifactId>spring-boot-starter-parent</artifactId>
		<version>2.4.0</version>
		<relativePath/> <!-- lookup parent from repository -->
	</parent>
/---/
	<dependency>
			<groupId>com.graphql-java-kickstart</groupId>
			<artifactId>graphql-spring-boot-starter</artifactId>
			<version>8.0.0</version>
		</dependency>

		<dependency>
			<groupId>com.graphql-java-generator</groupId>
			<artifactId>graphql-java-runtime</artifactId>
			<version>${graphql-maven-plugin.version}</version>
		</dependency>

It can be reproduce by adding the graphql-jave-generator dependency. When I remove the spring boot program works again.

You should raise the issue with the graphql-java-generator team then instead of here. I've never heard or used that library before, and we don't have the resources to provide support for integrating with third party libraries. So maybe they can help. Or otherwise raise an issue on Stackoverflow with more detailed information (like stack traces and minimal code to reproduce the issue).


Move Sentry properties into sentry.properties, add proxy settings

Try to get Sentry working for ICDS
cc @dannyroberts @snopoke
DO NOT MERGE I have never submitted an Ansible PR before and have no idea how to test.

In addition to this you'll need a task that copies the file to the right location on the server such as this one for the 'application.properties' file: https://github.com/dimagi/commcarehq-ansible/blob/43bd9e91ee7200ee5062afe2d59d7715a221a335/ansible/roles/formplayer/tasks/main.yml#L43
You can probably just re-purpose that task to do both of them as follows:

- name: Copy Spring application.properties
  become: yes
  template:
    src: "{{ item.src }}"
    dest: "{{ formplayer_build_dir }}/{{ item.dest}} "
    group: cchq
    owner: cchq
    mode: 0644
  tags:
    - fp-localsettings
    - localsettings
  with_items:
    - {'src': 'application.properties.j2', 'dest': 'application.properties'}
    - {'src': 'sentry.properties.j2', 'dest': 'sentry.properties'}

@snopoke Thanks! Updated, and also returned sentry.dsn to application.properties

@dannyroberts OK, despite the documentation I could find no evidence/other mentions of sentry.properties being a valid place for these properties. So, I've moved them into application.properties. Locally this seems to be working (invalid proxy fails, valid proxy works, no proxy works). LMK when you want to give this another go.


Unable to connect via IPC

With web3.js I can connect via IPC, but with this library I can only connect with HTTP
This works:
parityApi = new Api(new Api.Provider.Http('http://localhost:8545'))
This does not:
parityApi = new Api(new Api.Provider.Ipc(ipcPath))

Hi,
We don't support connecting to Parity Ethereum using IPC.
Api.Provider.Ipc was used for communicating with IPC between an Electron webview and the Electron main process (sorry for the ambiguous naming!).

Hey @ethernomad! Unfortunately the IPC provider was only created to support the (now defunct) Parity UI in an Electron context (see their ipcMain & ipcRenderer docs), so it might not work out-of-the-box with other projects.
However PRs are very welcome! The ipc.js itself is not that big, and it should be fairly doable to support IPC more generally.

I should have mentioned that I am using it in an Electron app. Is connecting via IPC supposed to be working at the moment in Electron? My project uses web3.js to talk to Parity via IPC. I just use @parity/api to access some Parity APIs that web3.js doesn't support.

Is connecting via IPC supposed to be working at the moment in Electron?

Then it should, have a look at https://github.com/parity-js/shell/pull/8 for a working demo. But also note that we decided not to use IpcProvider because of security reasons, Electron IPC messages don't work in renderer processes if contextIsolation is true (which is recommended).


Using a default bucket instead of bucket name in storage.

This is in preparation for using the default bucket in the Blob constructor.

Coverage remained the same at 100.0% when pulling 38427df4848d82ce7c976c6be8a9782d1112c1c2 on dhermes:use-default-bucket into d858ff041192657c483e24fb904aade41996bf09 on GoogleCloudPlatform:master.

LGTM


Smartthings Celsius to Fahrenheit Error

hi all:
getting an error when trying to change temp in Celsius:
6:47:30 PM EST: error groovy.lang.MissingMethodException: No signature of method: script1424908044784743819686.temperatureCtoF() is applicable for argument types: (java.lang.Double) values: [19.600000381469727] @ line 346
the fan an mode seem to work fine in celsius. Also, the colour temp is always a dark coloured blue. I presume it'a quick fix in getting the Celsius to Fahrenheit to convert properly.
I appreciate ANY help on this:)
Thanks!

Fixed in version 2.0.0.


Support for code that contain vertical bars in table

| a                    | b     |
|:---------------------|:------|
|`echo 'hello' | wc -m`| good. |

The markdown above outputs unintended HTML, such as the following.

a	b

`echo 'hello'</td><td align="left">wc -m`

If it's not code, I can escape vertical bar with a backslash.
| a                   | b     |
|:--------------------|:------|
|echo 'hello' \| wc -m| good. |

a	b

echo 'hello' | wc -m	good.

But when it's code, it doesn't work.
| a                     | b     |
|:----------------------|:------|
|`echo 'hello' \| wc -m`| good. |

a	b

echo 'hello' \| wc -m	good.

Is this a bug?

This was discussed a lot in #356. My recollection is that it is a deficiency in the informal spec for tables, and that we're doing the best we can wrt that spec, but I could be wrong.

@raphlinus I'm sorry, but I didn't notice the issue... :cry:  Thank you so much! :pray:


storing name of cic converter docker image in a var instead of hardco…

…ding it in multiple places
Tested and working on my local machine.

works on my machine as well


buildah cannot execute commands inside other runc containers?

It appears that buildah is limited to working on containers it creates itself.  One direction we are considering for the OpenShift build side is to execute builds only within containers created by the existing runtime (crio or docker).  Can buildah perform commands against other containers, and if not, what would it take to support that?

I think this is probably more of an issue for podman. Once podman starts sharing the database with cri-o, then podman commit could do what you want.
@mheon WDYT

@rhatdan If our usecase is committing existing containers running by CRI-O, podman commit once we have them sharing containers should be perfect.

I think this is probably more of an issue for podman. Once podman starts sharing the database with cri-o, then podman commit could do what you want.
@mheon WDYT

I don't know if there is a way to shift an issue from one REPO to antother.  @mheon Can you open this issue in podman and link @smarterclayton to it.

@rhatdan A specific issue for committing CRI-O containers? Or should we use the generic CRI-O integration tracker bug in podman for this?

I would say a specific issue on committing CRI-O containers, then we can close this one with a link to it.  Theoretically we could get to the point of committing CRI-O containers before we get to full integration.

podman commit can do this now, well will be able to do it once CRI-O and podman share the same library.


Autoflow does not work for C89-style comment blocks

Turns into

and the rest of the file is now invalid because there is an unclosed comment block.
Running atom 1.16.0 but this has been a problem for as long as I can remember.

Looks like there's a pending pull request for this: #45.

Note: I've found the docblockr package handles these well.

Fixed by #45.


[BUG]: we can only get author name but no other distinguishable information from arxiv API

Description of the bug
No response
Steps To Reproduce
No response
Additional Information
No response

try to use arXiv html to fetch author information, or try to crawl data from google scholar

thanks for mentioning!

we fix this using semantic scholar now.


Ms tutorial fixes

Small changes in the tutorials
Issues #199 , #200 and #201  Closed

@Vinayak0706 : Thanks for your contribution! The author(s) have been notified to review your proposed change. @jessemcculloch

@Vinayak0706 : Thanks for your contribution! The author(s) have been notified to review your proposed change. @jessemcculloch


TeamInfo type does not expose aadGroupId (java)

See parent

Looks like this field already exists in the java sdk:
https://github.com/microsoft/botbuilder-java/blob/master/libraries/bot-schema/src/main/java/com/microsoft/bot/schema/teams/TeamInfo.java#L30
closing


CSI 2.2.0 release checklist

IBM Spectrum Scale CSI Driver v2.2.0 release Checklist

[x] Switch ImagePullPolicy
[x] csi snap works on Vanila k8s, Openshift with and without OLM deployment
[ ] Verify the GitHub and KC links are working
[x] Pause dev checkin once stop-ship phase starts
[x] Create Golden Master (Atleast 1 week before GA)
[x] Regression Complete
[x] OLM Packages Ready and Tested
[ ] Generate Red hat bundle
[x] Check images for Vulnerabilities(Driver, Operator, sidecars)
[ ] Final KC Verification (1 week before GA)
[x] Create git tag  (1 week before GA)
[ ] Push multi arch images to quay (on GA date)
[ ] Merge dev into master (on GA date)
[ ] Publish git tag (on GA date)
[ ] Verify the images and yaml from release branch are correct - CLI install/Upgrade (on GA date)
[ ] Create PR for Community Operator Listing (on GA date)
[ ] Start Red Hat registry bundle upload procedure.
[ ] Unpause dev checkin. (once OLM is verified for community operator)
[ ] Switch ImagePullPolicy to Always

Verify the GitHub links are working  - Done.

Created Golden master images-
quay.io/ibm-spectrum-scale-dev/ibm-spectrum-scale-csi-operator:v2.2-GM1
quay.io/ibm-spectrum-scale-dev/ibm-spectrum-scale-csi-driver:v2.2-GM1

These are two PR for Community Operator Listing-
https://github.com/operator-framework/community-operators/pull/3666
https://github.com/operator-framework/community-operators/pull/3671

IBM Spectrum Scale CSI Driver v2.2.0 is successfully released.
https://github.com/IBM/ibm-spectrum-scale-csi/releases/tag/v2.2.0
quay.io/ibm-spectrum-scale/ibm-spectrum-scale-csi-driver:v2.2.0
quay.io/ibm-spectrum-scale/ibm-spectrum-scale-csi-operator:v2.2.0
https://operatorhub.io/operator/ibm-spectrum-scale-csi-operator
https://catalog.redhat.com/software/containers/ibm/ibm-spectrum-scale-csi-operator-bundle/5f7f4b1169aea3467fdceb9d
https://kubernetes-csi.github.io/docs/drivers.html


Custom Worksheet's Function

Create a User-Defined Functions for the Built-In functions you frequently used together.

Worksheet Functions

[ ] SORT + UNIQUE
[ ] Debit Credit Indicator
[ ] Foreign Exchange Converter

Get Functions

[ ] Get Folder
[ ] Get FileName
[ ] Workbook Name
[ ] Worksheet Name
[ ] Table Name
[ ] Pivot Table Name
[ ] Range Address

Validate Existance (Returns Boolean)

[ ] Drive Exist
[ ] Folder Exist
[ ] File Exist
[ ] Worksheet Exist
[ ] Table Exist
[ ] Pivot Table Exist

Validate Data Types (Returns Boolean)

[ ] IsArray
[ ] IsBlank
[ ] IsText
[ ] IsNumber
[ ] IsError
[ ] IsFormula

Others

[ ] LastRow

(Current Region ; Long)

[ ] LastColumn

(Current Region ; Long)

[ ] LastUsedRow

(ActiveSheet.UsedRange.Rows.Count)

[ ] LastUsedColumn

(ActiveSheet.UsedRange.Columns.Count)

[ ] Selection Interior Color (RGB)


Update videos.md

Change an video language on the list from espanol (espanish) to Português Brasileiro (Brazilian Portuguese)
Source: I'm the video creator.

@StealthC thank you very much for taking the time to update this, and apologies for getting the language wrong!
This change will be pushed out once the CI build has completed.


Multicluster examples do not work if trustDomain value is set

Bug Description
The Multi-Primary on different networks multicluster example works exactly as expected if using the same trustDomain (e.g. cluster.local) in both clusters. However if the trustDomain value differs across clusters (everything else remaining the same); then cross-cluster calls do not work.
e.g.
cluster 1:
meshConfig:
  trustDomain: search.prod

cluster 2:
meshConfig:
  trustDomain: payments.prod

Both clusters have a common root of trust as per the pre-requisite setup in Configure Trust
We require the use of different trust domains to uniquely identify workloads across the estate; however we also require them to have the same x509 root cert.
Expected Behaviour
The workload certs in both clusters share the same root, so I would expect cross cluster MTLS calls to succeed. i.e.

Calls to the helloworld service should be served by both the local v1 deployment and remote v2 deployment
Calls to a remote httpbin service should be successfully served over MTLS

Actual Behaviour

Calls to the helloworld service are served only from the local cluster:

Hello version: v1, instance: helloworld-v1-7df57fccf6-wl85c
Hello version: v1, instance: helloworld-v1-7df57fccf6-wl85c
Hello version: v1, instance: helloworld-v1-7df57fccf6-wl85c
Hello version: v1, instance: helloworld-v1-7df57fccf6-wl85c
...

Calls to a remote httpbin service fail

kubectl exec -n foo deploy/sleep --context="${CTX_CLUSTER1}" -- curl http://httpbin.bar/get
upstream connect error or disconnect/reset before headers. reset reason: connection failure, transport failure reason: TLS error: 268435581:SSL routines:OPENSSL_internal:CERTIFICATE_VERIFY_FAILED

I would expect the trustDomain values being different only to come into play if referencing the spiffe ids/principals in an AuthorizationPolicy; which is not the case here (no polices are deployed)
Unless there is some extra config required for multiple trustDomains (with the same root) to work in a multicluster setup, then this looks to be a bug?
Version
istioctl version                                                                            ✔ 
client version: 1.13.4
control plane version: 1.13.4
data plane version: 1.13.4 (4 proxies)

Additional Information
No response

By default only the same trust domain is trusted; to add more trustDomainAliases can be set

Ah good point... this does seem like a functionality gap.

Do you know if there is a workaround for this today? I was looking at certificatedata which appears to let you "add" trust domains to the current mesh, but looks like it relies on adding a bundle url (which in this case would be redundant, as it's effectively the same bundle)

Any progress on this? I run into the same problem, and couldn't go through even if I configured trustDomainAliases mentioned above.
  meshConfig:
    trustDomain: cluster.prody
    trustDomainAliases:
      - cluster.prodx

The service can be discovered in both clusters, but can't call each other: cluster 1 $ istioctl proxy-config endpoint -n sample curl-6b8b8c6b55-qtmbf | grep hello <IP_ADDRESS>:5000 HEALTHY OK outbound|5000||helloworld.sample.svc.cluster.prodx <IP_ADDRESS>:15443 HEALTHY OK outbound|5000||helloworld.sample.svc.cluster.prodx cluster 2 $ istioctl proxy-config endpoint -n sample curl-7bbdf4dd65-ncqcc | grep hello <IP_ADDRESS>:5000 HEALTHY OK outbound|5000||helloworld.sample.svc.cluster.prody <IP_ADDRESS>:15443 HEALTHY OK outbound|5000||helloworld.sample.svc.cluster.prody
Call from cluster 1 pod curl, always get response from local service : $ curl -sS helloworld.sample:5000/hello Hello version: v1, instance: helloworld-v1-768999db5d-nn8f5 Hello version: v1, instance: helloworld-v1-768999db5d-nn8f5
if I delete cluster 1 local hello service, and call again: $ curl -sS helloworld.sample:5000/hello upstream connect error or disconnect/reset before headers. retried and the latest reset reason: remote connection failure, transport failure reason: TLS_error:|33554536:system library:OPENSSL_internal:Connection reset by peer:TLS_error_end~
How can I fix this, have to use identical trust domain (so identical Kubernetes dnsDomain)?

Just found out another setting clusterDomain will affect this as well, keep it default (cluster.local) resolve the issue

Ah good point... this does seem like a functionality gap.

Yeah we should tackle this


Update Github App documentation to prevent common error mode

A common error mode for users is giving the wrong key, and the error message is not always clear that the format is the problem. This should be front and center in all concerned docs as this has been an issue in FG and NextGen that customers hit and don't realize the problem.

Please revise as necessary for clarity or consistency in format
Thanks for contributing to the Harness Developer Hub! Our code owners will review your submission.
Description
Adding tip to section where one of my customers just hit this error mode and I had to spend 2 hours debugging with them. This is a common failure mode and I didn't realize what happened until I realized I was looking at the linked doc and he was looking at the doc with this proposed revision.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://66b394819f0417130209f3b1--harness-developer.netlify.app


MaskDINO 12 epoch results with 100 queries

Hi, @FengLi-ust. I'm very interested in your great work!
When I read your paper, it's method still works well in 100 queries setting. So did you evaluate your method with 1x a schedule on COCO?
Thank you again for your elaborate work and I look forward to hearing from you.

Hi, we show the performance of using 100 queries for 50 epochs in our paper. Do you mean you want to know the performance of using 100 queries for 12 epochs?

Yes, that't right. I want to know the performance of using 100 queries for 12 epochs setting.

I see. Thank you for your reply.

I will keep that in mind. Thank you again for your kind reply.


[POC] HWKALERTS-202 Introduce batch in several Insert/Update/Delete scenarios

This is still a POC not sure if it is ready for merging.
Testing and tweaking parameters are still in WIP.
But code can be reviewed.
Strategy is to batch those things that make sense, basically within same partition, and prioritizing aspects close to real use cases.
With this setup, -Dtest-env=perf and -Pperf-itest shows a 5% of improvements.
Anyway, I am still studying these changes and testing a good parametrization before to confirm any good result.

In general it is a bad idea to do unlogged batches across multiple partitions. A single node cluster may be a bit of an exception to that though.

The batches are performed on queries over single partition. Thus to test
unlogged first.
Queries for multiple partitions are unbatched yet for performance reasons.
El 19 nov. 2016 0:56, "jsanda"<EMAIL_ADDRESS>escribió:

In general it is a bad idea to do unlogged batches across multiple
partitions. A single node cluster may be a bit of an exception to that
though.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/hawkular/hawkular-alerts/pull/264#issuecomment-261672874,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABldeZq13Moz4KENk8jgD3VIfI0_7M_8ks5q_jsUgaJpZM4K2_YN
.

I am not against the driver-based batching, I think it could help our response times.  I think even with the batching introduced here we may still run into the thread issues that have shown up with the change to the 3.0.5 driver.  To avoid that we may still need to limit the number of futures we submit concurrently.  So we may still need to chunk large collections.  For example, if storing 1000 events, we may need to chunk by 100 and then batch those into 10s.

@jshaughn one thing to keep in mind is that batch inserts to the same partition are very efficient. In fact, they are performed as an atomic operation, and this is the best use case for unlogged batches. The problem with unlogged batches across multiple partitions is that the coordinator might timeout waiting for responses from one or more nodes, and you have no way of knowing which writes failed, which means you have to retry the entire batch.

@jshaughn one thing to keep in mind is that batch inserts to the same partition are very efficient. In fact, they are performed as an atomic operation, and this is the best use case for unlogged batches. The problem with unlogged batches across multiple partitions is that the coordinator might timeout waiting for responses from one or more nodes, and you have no way of knowing which writes failed, which means you have to retry the entire batch.

@jsanda, as commented earlier. We are not using batching across multiple partitions. Indeed the use introduced here is exactly as you describe.

That's good. In hawkular-metrics, we always batch multiple writes that are for the same partition.

@jshaughn I addressed some minor feedback.
Can you take a final look ?
Basically, this PR does two things:

Batches what it makes sense for same partition.
Adjust the queue of the driver to support overflows of requests.

The recommended way for C* is to send async calls to the driver, and the driver is able to route them into the C* cluster nodes.
I think that doing some adjustments of the queue related alerting usescase (more heavy writes, in general) is good.
C* official docs stands about 80k req/second per node, so even this is quite subjective, it can give us an orientation of orders.
So I think these improvements will generally help.
We can let QA to run more perf tests and we can try to run future optimizations accordingly.

Just a couple of final comments for you to review.   Thanks!


[enhancement] Move the configuration for bulk writing to Elasticsearch to Nacos

Move the configuration for bulk writing to Elasticsearch to Nacos.

https://github.com/XiaoMi/ozhera/pull/156


[Event Request] Table Payment Application Proposal - OnAfterCreateBankStmtMatchingBuffer

Describe the request
An event at the end of the procedure CreateFromBankStmtMacthingBuffer on table 1293 "Payment Application Proposal" in order to be able to transfer more information from the matching buffer to the resulting proposal line.
Additional context
We are trying to create ways to fetch payment proposals using other fields from existing data sources, e.g. creating a Customer Posting Group account type and matching the values in the customer ledger entries that are already being fetched by the system with the account no. set to the relevant posting group. The idea was to transfer this field from the customer ledger entry to the Ledger Entry Matching Buffer and then over to the Payment Application Proposal record, and then change the filter in the OnOpenPageEvent for the Payment Application page in order to change the filter to the new field containing the posting group in order to show the relevant entries, but there is currently no place with an event available where we can add fields to the Payment Application Proposal record during transfer of data from the Ledger Entry Matching Buffer.
Internal work item: AB#496945

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 15656.


How we can show UnitText value in integer format

How we can show unit value in integer

Please follow this issue #163.

Thanks very much for the help,it works


Need different error message when bundle is expired

I tried a very old bundle and got:
WARN Bundle certificates are going to expire in -25 days, better to use new release

We should say something like
"Bundle certificates have expired, you must download a newer release" and exit

The error message comes later
INFO Verifying validity of the cluster certificates ...
ERRO Error occurred: Certs have expired, they were valid till: 19 Aug 19 06:54 +0000

See also https://github.com/code-ready/crc/issues/848 as this would make this issue obsolete.

This is fixed/obsolete


BitPat is not happy with Cat(someEnum.asUInt, someBool.B)

https://scastie.scala-lang.org/fLovomFGRUaMML8MvEIBwA
import chisel3._
import chisel3.util._
import chisel3.experimental.ChiselEnum

object TestEnum extends ChiselEnum {
  val s0 = Value
}

class Example extends Module {
  val a = BitPat(Cat(TestEnum.s0.asUInt, true.B))
}

println(getVerilogString(new Example))

doesn't work.
Type of issue: bug report
Impact: unknown
Development Phase: request
Other information
If the current behavior is a bug, please provide the steps to reproduce the problem:
What is the current behavior?
java.util.NoSuchElementException: None.get
	at ... ()
	at Playground$Example.<init>(main.scala:12)
	at Playground$$anonfun$2.apply(main.scala:15)
	at Playground$$anonfun$2.apply(main.scala:15)
	at ... ()
	at ... (Stack trace trimmed to user code only. Rerun with --full-stacktrace to see the full stack trace)
}

What is the expected behavior?
I think this should work?
Please tell us about your environment:
Chisel 3.5-SNAPSHOT
What is the use case for changing the behavior?

This might be related to constant-propagation problem.
The method def apply(x: UInt): BitPat in object BitPat calls x.litValue, which eventually calls litOption.get.
Since it is mentioned in #1632 that Cat() will not returning a literal for literal inputs, the None.get exception is thrown here.


Cannot connect to wsl not install vscode-remote

Issue Type: Bug
This worked yesterday, today cannot edit or do anything. I get errors about not being able to install extensions, cannot connect to server, etc. Like
Unable to open 'Tarea2': Unable to read file 'vscode-remote://wsl+ubuntu/mnt/c/Users/myuser/folder' (Error: connect ENETUNREACH <IP_ADDRESS>:52176).
My list of extensions wont load.
VS Code version: Code 1.42.1 (c47d83b293181d9be64f27ff093689e8e7aed054, 2020-02-11T14:45:59.656Z)
OS version: Windows_NT x64 10.0.18362
Fetching remote diagnostics for 'WSL: Ubuntu' failed: connect ENETUNREACH <IP_ADDRESS>:52176

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-5200U CPU @ 2.20GHz (4 x 2195)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: enabledskia_renderer: disabled_offsurface_control: disabled_offsurface_synchronization: enabled_onvideo_decode: enabledviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
15.92GB (8.90GB free)

Process Argv
--folder-uri=vscode-remote://wsl+Ubuntu/mnt/c/Users/Ernesto/JupiterHomework/Tarea2 --remote=wsl+Ubuntu

Screen Reader
no

VM
0%

Fetching remote diagnostics for 'WSL: Ubuntu' failed: connect ENETUNREACH <IP_ADDRESS>:52176
Extensions: none

It's likely unrelated to the WSL extesnion. Try to shutdown the WSL distro and restart it.
wsl -d <distro> --shutdown

Please close. This was blocked by Windows defender. Was working until the
day before.
El jue., 20 feb. 2020 2:38 a. m., Martin Aeschlimann <
<EMAIL_ADDRESS>escribió:

It's likely unrelated to the WSL extesnion. Try to shutdown the WSL distro
and restart it.
wsl -d  --shutdown
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vscode/issues/90899?email_source=notifications&email_token=ABFYOPAWSIXGF5KM3YNVUXTRDY6PFA5CNFSM4KXILQS2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEML6ZOQ#issuecomment-588770490,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABFYOPBX73Q42MIFNXWHTHLRDY6PFANCNFSM4KXILQSQ
.


Announcement: Removal of ERC721AOwnersExplicit extension

With the new _initializeOwnershipAt(uint256 index) function, users can directly initialize the ownership at any index.
It is now manageable to write a public function to initialize the ownerships anywhere.
As such, we are planning to remove the ERC721AOwnersExplicit extension.

If I want to normalize/initialize ownership data after mint out (for better transfer gas), what's the recommended approach? Is there a better way than to iterate through tokens in batches and call _initializeOwnershipAt?

@holic I would recommend restricting the quantity in the batch mint function to be below a reasonable amount (e.g. 30).
_initializeOwnershipAt can be useful if you need to mint a very large batch for the team (e.g. 200).
You can now either mint anytime for the team (usually during the start or the end), and call _initializeOwnershipAt at say every multiple of 8, within the range minted for your team. Then, subsequent transfers will have more reasonable gas costs.
The recent improvements have the largest impact on second transfers (from about 29k gas to 24k gas).
The first transfer will see savings of around (2k gas if there is a need to initialize the next slot).
Note that the bulk of the first-time transfer costs for tokens minted in large batches is in the scanning of the ownership slots.

Hi @Vectorized
Can you provide example on how to go about calling _initializeOwnershipAt post mint (initial mint using ERC721A w/o this function) to reduce the scanning cost?  We have large gaps in the range of couple of hundreds.
Thank you for your help in advance!


WIP:wait addon manifest work deleting while detaching cluster

Signed-off-by: zhujian<EMAIL_ADDRESS>

/close


Hide private protected members

Resolves #1740

/check-enforcer override

@praveenkuttappan the PR pipeline for APiView seems not to be running.


Add consistent theme usage.

Leaning more into the ThemeProvider and next-themes. Added SSR support via cookies with proper instantiation and removed a bunch of legacy dark mode checks in individual components via useEffect. Managed to remove the bootstrap init script for the theme too since next-themes will handle it.

Love this @florence-wolfe !


You can't use Aerial in this version of macOS

Required information
In order to help us sort your issue, we ask that you provide the following information:

[ ] Mac model: MacBook Air 2017
[ ] macOS Version: 10.15.7

Description of issue / Feature request
You can't use Aerial in this version of macOS.

Hi @macwkcom
Please check this entry in the FAQ (first one below the link) it should help you fix the issue : https://github.com/JohnCoates/Aerial/blob/master/Documentation/Troubleshooting.md#very-common-issuesmacos-bugs


Serving Operator should provide an option that all ingress gateways are configured

If a user creates a custom ingress gateway, istio may select a gateway at random (https://github.com/knative/serving/issues/5163#issuecomment-521815915). The operator should provide a way to ensure that the ingress gateway always works.
This relies a bit on https://github.com/knative/serving/issues/5172.
I believe this could work by montoring gateways and adjusting the config-istio to account for the new gateway (https://github.com/knative/serving/blob/b7dfe3fdb80ffac7f7a05c20787400ce51aad2b1/config/config-istio.yaml#L45)
This issue is a clone of an existing issue in knative/serving-operator: https://github.com/knative/serving-operator/issues/156

By @trshafer
Another option is to not install the `knative-ingress-gateway` (https://github.com/knative/serving/blob/b7dfe3fdb80ffac7f7a05c20787400ce51aad2b1/config/202-gateway.yaml#L19) if one is already configured, . And use that gateway instead of the `knative-ingress-gateway`.

Some discussions in the community:
Three options I could see would be:
* Package all the plugins and have something in the CR to list which plugin dukes should be included
* Package all the plugins in one fine and use labels to select them
* Package each in their own operator with some way for the serving operator to ensure at least one is installed
11:23
Serving uses annotations and a default config to determine which plugins to use for HTTP routing (and they aren't mutually exclusive)

markusthoemmes:redhatnew:  11:26 AM
we could key off of the setting @argent is referring to, to pick one of the ingresses, but each potentially comes with its own set of configuration.
So maybe we have something like this?
type IngressConfiguration struct {
  Istio *IstioConfiguration
  Contour *ContourConfiguration
  Kourier *KourierConfiguration
}
And for each non-nil configuration, we install the relevant package?
11:26
IIRC there's precedence in K8s for this

Jim Crossley:redhat:  11:27 AM
yeah, i like that, and from the install docs, it looks like it's easy enough to grab the istio, kourier, etc yaml's from somewhere, i.e. we won't have to create them specifically for the operator

@markusthoemmes This is all the information I collected for this feature so far.
Plz write up your idea in terms of an proposal for this feature. Thx.

I think we need to have a solution in place for this before we recommend this operator. At a minimum, we need an option in the CR for disabling istio entirely. This is for downstream consumers who already have another ingress, e.g. kourier, configured.

@jcrossley3 while I agree we need to solve this, the existing "recommended" knative-serving-operator has the exact same behavior. I don't think the combined operator makes that any better or worse (yet).

Added the proposal @markusthoemmes drafted: https://docs.google.com/document/d/1AQBGCIoUAB8Whg02MVWdujMj8O-OWFvPbccoctMbgJA/edit#

@houshengbo may I ask you the status of this feature? (cc @ZhiminXiang )

@nak3 We have resumed the development of this feature. We are discussing how to separate the ingress out of the existing knative-serving directory in kodata, and how to align the version of the knative-serving with the version of the ingresses.

/remove-lifecycle stale

/remove-lifecycle stale


ObservablePoint now extends Point

Observable point was missing clone and equals methods. Since the ObservablePoint is highly coupled to Point, and Point already had those methods, I've updated it to extend.

I don't believe this is right for v4, since we're only accepting PRs for high-value and critical bug fixes. This PR is more of a housekeeping, code maintenance, consistency issue and doesn't fall into one of those two buckets.
Also, overall I'm not sure about this change. On the balance, I'm not sure it provides a ton of value. Since many of the functions are overridden by the ObservablePoint, it probably is easier and less complicated to just add clone and equal methods to that class if that's the issue. Also, to @englercj's comment, it adds getters/setters to what is otherwise a very simple data structure (Point).
Curious to hear what other people think. Could be convinced that this is for v5, but probably not v4.

If there is a need to keep the 2 APIs compatible (not something I've required, but I can sorta see someone switching between the 2), I'd vote for adding clone and equal methods to the Point class, without inheritance, for v5 only.
Faster performance, less code (only minor duplication).

Okay I see where you all are coming from. To keep things simple, I've reverted the changes an added only the missing methods.
There would have been no need for this change had someone not changed a Point to an ObservablePoint which broke our equal checks.
On a side note; I'm a bit worried that you're locking v4 and focusing on v5, while I would love nothing more then to use the latest and greatest v5 changes, it's not piratical at this time to move to a WebGL only platform. Our analytics show more then 5% of our users are still running with no WebGL support at all. I can't divulge specifics however I can tell you that's from a sample size of 200,000+ users. And 50% of those users only support WebGL1.0.
From our point of view we won't be moving to v5 until those 10's of thousands of no WebGL users becomes more like hundreds. This may be another year or two. All I'm saying is perhaps v4 should remain a little more open to changes until v5 is ready and commercially viable.

Part of the problem @st3v0 is that we have extremely limited resources on the team that manages PixiJS. We're trying to spend those limited resources wisely, which is pushing forward to v5 and trying to slow non-critical PRs to v4.
Also, just FYI, v5 still still continue to support canvas fallback in a new package pixi.js-legacy. Also, we are progressively enhancing when it comes to WebGL 1 vs 2.
But I think I would now consider your use-case a bug to fix backward compatibility.


Added getNeighbourPawns method and implemented Retribution prayer logic

What has been done?
Added utility function to find all pawns neighboring a target pawn
Added Retribution prayer logic, should be easily extendable for future cases (i.e. retribution in clan wars, castle wars, etc)
closes #108

Fudged this up a little and accidentally deleted my last PR when trying to fix some problems with the retribution logic.


Add support for require.resolve

I'm using aliases in require.resolve statements. Previously I was using a Babel plugin to resolve my paths, but I switched to SWC and now I'd like to use your package to fix paths after compilation. However, require.resolve is not supported.

Hey @wintercounter, this has been released in v0.7.0. Please give it a shot and let me know if you have any feedback! Thanks for using this package and giving the suggestion :)


Updated TF to 2.8.2

Checklist before submitting

[ ] Did you read the contributor guide?
[ ] Did you update any affected documentation?
[ ] Did you write any tests to validate this change?

Description
Fixes # (issue).
Review process to land

All tests and other checks must succeed.
At least one maintainer must review and approve.
If any  maintainer requests changes, they must be addressed.

This is for 1.6.1, correct? Is there another issue for TF Serving 2.9?

Yes, this is for 1.6.1. For 1.7.0, I'm yet to work on TF Serving 2.9.


[client] Upgrade rustyline dep to 5.0.3

Motivation
In the #1050 effort, this eliminates the duplicate versions of nix 👍 however it moves the goalpost by creating a conflict in dirs 👎
Have you read the Contributing Guidelines on pull requests?
:+1:
Test Plan
cargo build && cargo test

@bors-libra r+

:pushpin: Commit 4587742 has been approved by bmwill

:hourglass: Testing commit 4587742e8b2c455dd82fb102499d79de0c9635a8 with merge d4db4bd5f92b91efe7be17d70ec05b703b5ec76e...

:sunny: Test successful - checks-circle_commit_workflow
Approved by: bmwill
Pushing d4db4bd5f92b91efe7be17d70ec05b703b5ec76e to master...


Error in Console with SKRIPT

There seems to be a race condition warning when checking if SKRIPT is loaded. Magic is returning the below.
Version: Magic-10.8.1
[11:19:11 WARN]: [Magic]  Error integrating with Skript
ch.njol.skript.SkriptAPIException: Registration can only be done during plugin initialization
        at ch.njol.skript.Skript.checkAcceptRegistrations(Skript.java:1223) ~[Skript.jar:?]

Possibly related to: https://github.com/SkriptLang/Skript/issues/4917

This should be fixed in the next dev build: https://jenkins.elmakers.com/job/MagicPlugin/4186/


Error when trying to download a song

Hello,
I would like to download 2 Indochine tracks with pytube. But I have an error.
the link of the 2 tracks :
https://www.youtube.com/watch?v=DkffTDkSADI
https://www.youtube.com/watch?v=XhFzKhTFY3I
When I go to youtube in Chrome, I see that I need to be connected to reach the track.
I think this is the problem, but I don't konw how to solve it.
That is the error in bash :
Traceback (most recent call last):                                                                         File "test.py", line 17, in <module>                                                                       yt = YouTube(url)                                                                                File "/home/user/.local/lib/python3.6/site-packages/pytube/__main__.py", line 103, in __init__      self.descramble()                                                                                File "/home/user/.local/lib/python3.6/site-packages/pytube/__main__.py", line 152, in descramble                                                                                self.js_url = extract.js_url(self.embed_html)                                                          File "/home/user/.local/lib/python3.6/site-packages/pytube/extract.py", line 121, in js_url         base_js = get_ytplayer_js(html)                                                                        File "/home/user/.local/lib/python3.6/site-packages/pytube/extract.py", line 173, in get_ytplayer_js                                                                                caller="get_ytplayer_js", pattern="js_url_patterns"                                                  pytube.exceptions.RegexMatchError: get_ytplayer_js: could not find match for js_url_patterns
Thank you for you reply

I'll look into this!

I guess this occurs only for either inappropriate or age-restricted videos

Working on a fix for this now, see https://github.com/nficano/pytube/pull/804

It looks like the normal workaround for age-restricted content, accessing the embed url, is no longer possible. Fixing this will most likely be a more challenging task, but I'll try to look into it. It may require providing credentials to pytube so that you can login to youtube.

Actually, I could be wrong about this -- it's looking like the signature isn't being generated correctly by the Cipher class, going to look into why this is happening

Just ran into this issue trying to archive Unus Annus, since there's only 5 age-restricted videos should I just use an online utility?

hi @icorbrey this issue should be resolved in my current PR. Can you try installing that version with python -m pip install git+https://github.com/tfdahlin/pytube.git@fix/issue#979 and see if it fixes your problem?

Nope, same issue

Though I had to modify the command to use python3 instead of python, since I have both 2 and 3 installed

@icorbrey can you provide some some links to the age-restricted videos that aren't working for you? I'll try to track down the issue

Oh! I had a typo in my original reply! Try this: python -m pip install git+https://github.com/tfdahlin/pytube.git@fix/issue#797

Thank you for your answer. Now I can use the new version ?
How can I get the new version ? With pip ?

@sbessonneau you can install the most recent version from source by running python -m pip install git+https://github.com/nficano/pytube

It works.
Thank you very much


profile Tabs not working properly sometimes

What happened?
when i login to my account then visit my profile i get this:
.

its only showing the collected tab
when i refresh the page sometime i get this:
.

it still says collected but its actually showing the Created nfts
.
as a way around it i go to explore page then i go back to my profile using the login tab (top right corner)
and voila i see everything as it should look
Note: this only happens when i don't visit kodadot for more than 24hours, and after it starts working fine, it stays like that for the rest of the day ^^
Please reproduce in steps
/
Expected Behavior
/
What browsers are you seeing the problem on?
Chrome
Are you logged in?
Yes
At which address did you encounter bug?
kodadot.xyz
Screenshots
/
Relevant log output
/

Payment link for reward
https://nft.kodadot.xyz/transfer?target=JHMAL5CyvxWc3Ud42QxRUTpSnUa4m56mRSzPK69d1TU8NG7&usdamount=10
Code of Conduct

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

I will check it!

Note: this only happens when i don't visit kodadot for more than 24hours, and after it starts working fine, it stays like that for the rest of the day ^^

notice you are using prefix nft., have you tried log in on https://beta.kodadot.xyz if there is happening the same?
I've opened your profile and works well https://kodadot.xyz/rmrk/u/JHMAL5CyvxWc3Ud42QxRUTpSnUa4m56mRSzPK69d1TU8NG7

I can't reproduce even on mine
https://kodadot.xyz/rmrk/u/CuHWHNcBt3ASMVSJmcJyiBWGxxiWLyjYoYbGjfhL4ovoeSd

same thing happened of beta
https://beta.kodadot.xyz/rmrk/u/JHMAL5CyvxWc3Ud42QxRUTpSnUa4m56mRSzPK69d1TU8NG7?tab=collected

I see your profile is somehow special?
but when I removed ?tab=collected and opened it one more time it is ok!
Strange.

hey @onerawartist can you test on https://beta.kodadot.xyz like in a few minutes from now, 13:10 like at 13:20? and let me know if still happening!


[HOLD for payment 2024-07-24] [$250]  Categorizing - Workspace member has option to edit categories, which leads to not here page

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 1.4.82-1
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause internal team
Slack conversation:
Action Performed:
Precondition:

User is an invited member of a workspace.
The workspace has disabled all the categories.

Track a manual expense.
Click Categorize it from the actionable whisper.
Select the workspace that has disabled all the categories.
Click Edit categories.

Expected Result:
In Step 6, there should be no option for workspace member to "edit categories". Also, because the member is not an admin, the empty categories page should say this for the title "{workspaceName} doesn't have any categories enabled", and this for the subtext "Categorize this expense by choosing a different workspace, or [ask your admin](link to member's policy expense chat) to enabled categories for this workspace". Lets swap out the Categories button with a "Got it" button which navigates back to the workspace selector.
Here is an example mockup, but we can probably use the existing illustration and only update the text on the page when the member is not an admin.

Here is the Slack thread where this was discussed.
Actual Result:
In Step 6, there is an option for workspace member to "edit categories", which leads to not here page.
Workaround:
unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

Screenshots/Videos
https://github.com/Expensify/App/assets/43996225/abeb0194-ab33-48a9-b4b5-e4666ba4ad64

View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01693c1a6724bab4ab
Upwork Job ID:<PHONE_NUMBER>944850945
Last Price Increase: 2024-06-13
Automatic offers:

allgandalf | Reviewer | 102782628

Issue OwnerCurrent Issue Owner: @adelekennedy

@laurenreidexpensify FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors.

We think this bug might be related to #vip-vsb

@allgandalf Other parts of our codebase also use this condition to check isAdmin like here and  here
const isAdmin = policy?.role === 'admin';

So my solution should be chosen because it is the first proposal with the correct RCA and solution. The use of the isPolicyAdmin function in the places mentioned above can be done in the PR phase.

Thanks for the proposal everyone!
@codinggeek2023 's proposal looks good to me.
Their RCA is correct and their solution is async with our codebase, we already use isPolicyAdmin util in reports page and workspace initial page
🎀👀🎀 C+ reviewed

I like that proposal too, but I think we should go one step further and edit that empty categories page to have different text when a non-admin is viewing it. They don't have the ability to add categories so instead it should explain that the workspace doesn't have any enabled categories, and they should ask an admin to enable some categories or pick a different workspace.
Alternatively we could exclude workspaces without categories from the list, but then users might be confused about why it's missing, so I think it's better to show it. I will start a Slack discussion to make sure we're aligned on the expected behavior.

Here is the Slack thread where we discussed and landed on a solution. I'm going to re-assign to Danny to give him credit, and since he also proposed some good copy I don't think we need a review from Cheryl, although she's certainly welcome to chime in. I'm going to update the issue description now.

I'm actually going to go with the proposal from @daledah because it was posted first, makes sense, and he suggested a good alternate solution of editing the copy on the empty categories page. Please take a look at the updated expected results and raise a PR implementing those changes.

hey @adelekennedy handing this one over for my parental leave K2 clear out. we're in the PR stage, so you'll mainly just be handling payments for this one. thanks!

Payouts due:

[ ] Contributor: $250 @daledah (Upwork)
[ ] Contributor+: $250 @allgandalf (Upwork)

@daledah will you share your upwork profile with me so I can extend an offer?

let me know @daledah I'll keep this issue open for now

thank you @daledah! Offer sent

https://www.upwork.com/nx/wm/client/contracts?contractStatus=pending&contactPerson=1004801002

@daledah bump to accept the offer!

payment made! Closing this


just sprite treeshaked svg files

I was wondering if this package could handle treeshake? and just sprite svg files which presented after webpack tree shake apply?!
@kisenka

Did some one find a way or have an idea about doing this?

I used babel transform-imports and now I just sprite real used SVG files


Implement better toml resolution

Description
Currently the config/config.go package loads the toml. The cli/cli.go package can take an optional flag to a toml config. The default behavior is to look at ./mocktimism.toml. What would be better is if we recursively looked for a mocktimism.toml. E.g. look in current dir, then parent dir, then grandparent dir...
Tasks

[ ] Implement this feature
[ ] Write tests
[ ] Document this behavior in the current config docs

Will take this.


[NEW BONUS GUIDE] Install / Update / Uninstall common languages

What
As discussed with @VajraOfIndra, this is a section in the guides to collect all the installations of common prerequisites across the other guides.
Why
Central management of the guides will allow easier maintenance without the need to adapt individual application and tools guides.
How
Prepare guides for the common languages across the guides and collect them into one section.
Scope

[ ] significant change to core configuration
[x] independent bonus guide
[ ] simple bug fix

Fixes # (link issue)
Test & maintenance
Only the language guides will be updated on new versions of the languages or changes in the overall process. Tools and app guides shall not be touched.
Animated GIF (optional)
n/a

@VajraOfIndra @kristapsk
Just a thought for every guide in which checksums are NOT verified automatically, so you have to manually verify the checksum char by char. Instead of doing so, can we do something like this?
$ echo "99de2fe112a52ab748fb175edea64b313a0c8d51d6157dba683a6be163fd5eab go1.19.3.linux-arm64.tar.gz" | sha256sum --check
go1.19.3.linux-arm64.tar.gz: OK

Example is taken from this PR.

Just a thought for every guide in which checksums are NOT verified automatically, so you have to manually verify the checksum char by char. Instead of doing so, can we do something like this?
$ echo "99de2fe112a52ab748fb175edea64b313a0c8d51d6157dba683a6be163fd5eab go1.19.3.linux-arm64.tar.gz" | sha256sum --check
go1.19.3.linux-arm64.tar.gz: OK

Sounds like a nice solution yes..
@satsHIVE would you like to implement that change in your guide before we merge it..?

Yes, will do. But can in a few hours if not an issue.

sha256sum aligned to suggestion. @VajraOfIndra @blckbx

Let's go to master! 🎉


Applying Multiple FGD Files

Hello Wootguy. Would it be possible to add the possibility of using more than one FGD file? Because when trying to use more than one, it doesn't seem to work, after all when you can add another line to another FGD file. I can't add more either because as a result, the entities would look off, and I cannot easily identify what entity it is exactly. Thanks for taking the time to read.

The sort of FGDs I am taking about basically, are game and mod FGDs, like Half-Life Absolute Zero, Opposing Force, and Afraid of Monsters: Director's Cut.

If the problem is that some entities don't show up, then I think that's fixed. If the problem is that multiple games define the same entity with different keyvalues and flags, then this is a duplicate of #10.


towr: 1.3.1-0 in 'melodic/distribution.yaml' [bloom]

Increasing version of package(s) in repository towr to 1.3.1-0:

upstream repository: https://github.com/ethz-adrl/towr.git
release repository: https://github.com/ethz-adrl/towr-release.git
distro file: melodic/distribution.yaml
bloom version: 0.6.6
previous version for package: null

towr
* Improve API (#23 <https://github.com/ethz-adrl/towr/issues/23>)
* Remove redundant total time (duration set by endeffectors)
* Contributors: Alexander Winkler

towr_ros
* Improve API (#23 <https://github.com/ethz-adrl/towr/issues/23>)
* add gait optimization and replay speed to UI
* Add ROS and codefactor badges to readme (#22 <https://github.com/ethz-adrl/towr/issues/22>)
* Contributors: Alexander Winkler

Holding for Melodic sync.

rosdep complained about not finding the following repos in melodic, but since they are submitted as well, I think this should be fine: https://github.com/ros/rosdistro/pull/18422, https://github.com/ros/rosdistro/pull/18418

Holding for melodic sync

rosdep complained about not finding the following repos in melodic, but since they are submitted as well, I think this should be fine: #18422, #18418

Bloom failed to generate metadata as the packages were not available so you will need to close this PR and run bloom-release again once the other 2 PRs have been merged

Closing this as @mikaelarguedas suggested and will reopen after xpp and ifopt have made it into melodic sync.


Is there a way to get the type of a field from a document on the client?

Really like this package. Thanks for the great work!

doc.constructor.getField('fieldName').type

Awesome. Thanks very much.

On 29 Jan 2016, at 08:37, jagi<EMAIL_ADDRESS>wrote:
doc.constructor.getField('fieldName').type
—
Reply to this email directly or view it on GitHub.

No problem :)


shav/368 question-finder-bug

Ticket: https://github.com/isaaccomputerscience/isaac-cs-issues/issues/368
The question finder tile on homepage isn't working for students with the following account preferences:
GCSE + All Exam Boards
A Level + All Exam Boards
All Stage + All Exam Boards
This specifically occurs when the "show other content" option is not ticked.
/random returns [] in this scenario.
Correct functionality should be that a request to /random with those settings will select 5 random questions regardless of exam board, either looking at GCSE, A level or both depending on preference.
There is a fallback component of "featured news" on the homepage, so it's not a breaking issue for now.
Solution: added conditional check within loop over userContexts to populate the examBoardsList only if the preference to hide non-audience content is not selected. This change ensures that when students choose to show additional content beyond their selected exam board, all exam boards from their registered contexts are included in the game filter.

Issue still exists for user preferences "All Stages" and "All Exam Boards"
Currently that could be the case for some older accounts (when it was possible for students to select this option) and for any account on teacher pending.


As a shop owner, I would like to know when my products are running low on stock so I can stock it up.

stock & expiry date
default or customized


Wrong size if image is embedded as base64 data

I love this lib and it works fine if you use physical based images...but as soon as I try to link to an base64 image data, the window will opened up (displaying the image) but not auto-fit the image dimensions (instead, it is full-size).
Any idea how to solve this?
Regards,
kaju

Thanks for the report, it's fixed and released in v1.6.2.
The problem was, that the data URI wasn't detected correctly and the image was shown in an iFrame.

Wow - that was a fast fix and it works very well. Thank you ;-)

Glad it works now.


Add det for operators

Just do adaptive qr til diagonal converges.  May only work for I + compact but that's fine

Don't you need to take into account the diagonal of the Conversion from an operators domain to range?
Sent from my iPhone

On 5 Jul 2016, at 17:10, Richard Mikael Slevinsky<EMAIL_ADDRESS>wrote:
Closed #193 via 88f8505.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Yep, you are right.
Considering det(I+K), where K is compact with different domain and range spaces, then det(I+K) = det(C+C*K)/det(C). Oddly enough, somewhere in the LowRankPertOperator/LowRankOperator construction the U's are getting correctly converted down to Chebyshev (from either Legendre or Ultraspherical), and note also that Conversion(Chebyshev(),Legendre()) isn't working yet.


CentralPackageVersions does not support F#

Hi,
if i create a F# project and include
i get this error
The package reference 'FSharp.Core' should not specify a version.  Please specify the version in 'D:\prod\structures\Packages.props' or set VersionOverride to override the centrally defined version.

Supose the FSharp msbuild files are already having a PackageReference defined. So it should be possible to ignore this error
thanks

The build logic depends on a standard property IsImplicitlyDefined which is not being set on the implicit package reference to FSharp.Core.
https://github.com/microsoft/visualfsharp/blob/master/src/fsharp/FSharp.Build/Microsoft.FSharp.NetSdk.props#L97
Other SDKs are properly setting it:
https://github.com/dotnet/sdk/blob/master/src/Tasks/Microsoft.NET.Build.Tasks/targets/Microsoft.NET.Sdk.DefaultItems.props#L57
A workaround is to set the property in the top of your Packages.props:
<ItemGroup>
  <PackageReference Update="FSharp.Core" IsImplicitlyDefined="true" />
</ItemGroup>

We should also open an issue to get this fixed in the FSharp SDK.

I found a related bug: https://github.com/microsoft/visualfsharp/issues/3678

PR is out: https://github.com/microsoft/visualfsharp/pull/6730

Really nice, thanks for the help
On Tue, 14 May 2019, 19:19 Jeff Kluge<EMAIL_ADDRESS>wrote:

PR is out: microsoft/visualfsharp#6730
https://github.com/microsoft/visualfsharp/pull/6730
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/MSBuildSdks/issues/90?email_source=notifications&email_token=AAH6HSDIOX3G5W5M6EKEP5LPVLRBTA5CNFSM4HM2YCRKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVMAKZA#issuecomment-492307812,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAH6HSHJTY644PD7CXIXKDLPVLRBTANCNFSM4HM2YCRA
.

Sorry, I think you'll have to update the FSharp.Core package reference before Packages.props is imported so the workaround can't be in Packages.props itself.  Try moving it into the project instead.
Also, the FSharp SDK folks have rejected my pull request and won't be adding the IsImplicitlyDefined metadata.  I'll have to come up with another workaround instead.

I'm going to add the workaround directly to CentralPackageVersions because the FSharp folks want to leave off the necessary metadata to tell if the package was added by a user versus and SDK.

We have released a new version with the fix, please try it out: https://www.nuget.org/packages/Microsoft.Build.CentralPackageVersions/2.0.36

Excelent. Thanks for the quick fix. Still hand add the opportunity to upgrade but will confirm once i have

working fine now, thanks again

We have released a new version with the fix, please try it out: https://www.nuget.org/packages/Microsoft.Build.CentralPackageVersions/2.0.36

@jeffkl I'm new to .NET Core. This issue is affecting me. Can you explain how to update this package? I assume it requires updating it in the global Nuget cache?

You reference MSBuild project SDKs in either a project or global.json.  More info is here: https://github.com/Microsoft/MSBuildSdks#how-can-i-use-these-sdks


Error getting nodes from mirror for file 0.0.102 during attempt 5

Description
I deployed the app on the prod server, getting this error Error getting nodes from mirror for file 0.0.102 during attempt 5. Waiting 8000 ms before next attempt: No connection established in Mainnet.
Steps to reproduce

Deployed the web on the AWS server.
start the server with the help of PM2.
Getting an error after sometime, again and again

Additional context

Hedera network
mainnet
Version
v2.18.1
Operating system
Linux

@ayushkumar731  This is known behavior and you need to update to the latest version. This is an error that the Address Book cannot be updated. In your particular version, the address book is loaded every 10 seconds, thus making the remote server unresponsive due to high demand. You can also try to set setNetworkUpdatePeriod to the Client.

@ayushkumar731 This is known behavior and you need to update to the latest version. This is an error that the Address Book cannot be updated. In your particular version, the address book is loaded every 10 seconds, thus making the remote server unresponsive due to high demand. You can also try to set setNetworkUpdatePeriod to the Client.

After the updated library. It's working fine. Thanks!


Added spline kernel (from P. Hennig) to GPy

Had to modify the base_plots and model_plots.py, since I had troubles
installing GPy in anaconda on debian linux due to the dependency on
Tango. Why is Tango needed to represent colors that can also be typed in
Hex format thus eliminating further dependencies.

Hi James,
updated points 1) and 2) in the latest commit. I do not know how to do point 3.
Regards,
Thomas.

Hi @tjhgit ,
Thanks for the edits, this looks nice.
What's the domain of the kernel -- is it valid for any input X? I think previous spline kernels I've seen have been defined on [0,1]. Same here?
Would it be possible to implement update_gradients_diag? This would allow use with the sparse GPs in GPy.
Thanks,
James.


Update cobblemon to 1.5

Hi!, ty for your contribution. I updated the mod on modrinth with 1.5 support.
This pr wasn't building, because cobblemon 1.5 removed some biome tags and the data files were missing.


Supporting js extraction?

I am new to webpack and might have a slippery grasp on how this all works exactly, but seeing as my index.html had a <script src="js/main.js"> tag in it, I figured it wouldn't be unreasonable for the loader to see this tag and extract the source into the build directory appropriately, but discovered that it was just evaluating the contents of it instead and outputting nothing, causing build errors. In the source it looks like this could be fixed by just changing the test for node evaluation to be /css-base\.js$/. Or is that not how this is meant to be used?

I forked, made the change, and all tests are still passing. Pull request to follow.

I'm sorry, the extract-loader has really been designed to cope with the css-loader and the html-loader. If you're doing more sophisticated stuff, you're better off with the extract-text-webpack-plugin.
Or did the proposed change (from your PR) help your use-case?

@heptahedron : I'm stuck since many days trying to extract JS (script) files from HTML. Here is my attemp to get help on Stackoverflow.
@jhnns : Do you have any suggestion on how to use extract-text-pluging to achieve what we need ? I saw some PR related to this issue like #7, #20. Are they fixing the problem ? I applied those patch on my extractLoader.js from the node_modules folder but I'm now getting the error ReferenceError: require is not defined while parsing the javascript file.
Here is the only line that my javascript contains :
var $ = require("jquery");

@purell It's currently not possible with webpack to import a JavaScript file into an HTML file (via <script src).
This is because webpack has been designed as JavaScript bundler. Other file types, like CSS and HTML, need to be translated to JavaScript modules first. Unfortunately, this kind of import (JS into HTML) is not easy to achieve with the current architecture. However, we're looking for ways to treat CSS and HTML as first-class citizens, but for now I just can say that this is impossible 😞.

Its not impossible, just hard, you can create a loader that uses emitFile to emit the JS and remove it from the HTML. Its easily doable using the posthtml.


What's the purpose of using two Graph Learner

According to the code line321 in model_handler
and line 371 in model_handler, there are two GraphLearner, and the first one is for the first iteration and the second one for the rest iterations.  What's the purpose? I haven't found descriptions in the paper. Could you please provide more information about that? Thanks

Oh, I found the difference between two GraphLearners


Admonition boxes in tutorial illegible on docs.rs dark themes

While admonition boxes such as the following from the basics tutorial are perfectly legible on light mode:

docs.rs also provides a dark mode (which, by my understanding, is the default when the reader's system is configured to prefer a dark mode), under which the content of these admonition boxes becomes practically illegible:

It is potentially worth noting that docs.rs provides an additional dark mode, ayu, under which heading text is even lighter.
To reproduce: visit any of the tutorial pages containing admonition boxes, click on the paintbrush icon next to the docs.rs search bar, and select "dark" or "ayu".

Thanks for filing this issue!
This issue could probably be fixed by adding color: #222 to the div boxes, to ensure all text within is hard-set to be black. The main issue is that it might contrast with the dark background too much. I'll try to come up with something within the next few days.

Noting that I've temporarily ameliorated this issue by removing the backgrounds for these divs. However, I'm leaving this issue open for the time being because I'd like to find a way to restore these backgrounds while only modifying the text within.

Admonition boxes are gone, so this issue is no longer in effect


Options spacing wrong on release branches

See the spacing for the options in Settings and Developer

@AlexandreSato want to fix the developer panel?

I tried but I couldn't, but a strange thing happens lol, if I add another toggle the spacing is correct.

is it relying on stretch for the sizing?

I tried killing the automatic mechanic and also forcing a fixed size, but none of the attempts worked.

The non-release toggles only disappeared after an onroad transition, right? I fixed this in the alphalong toogle PR as well. Cars without longitudinal are also able to activate the longManeuver. I also corrected this in the PR on alphalong toggle


RNAppsFlyer.logEvent is not a function

Hey,
After upgrade from 5.2.0 to 6.2.30
and replace track event with logEvent
I'm getting RNAppsFlyer.logEvent is not a function
node_modules/react-native-appsflyer/index.js // line 30
function logEventCallback(eventName, eventValues, successC, errorC) {
return RNAppsFlyer.logEvent(eventName, eventValues, successC, errorC);  // here logEvent is undefined
}

Hi @aharon-vish please try to remove the plugin completely and install it again. if you are getting this error again, please contact our support team<EMAIL_ADDRESS>

Same problem, reinstalling plugin doesn't help. Any other suggestions?


Update installer.iss

Previous IP failed to resolve. Replacing the IP fixed the problem.

Closing cause it’s irrelevant as of the upcoming 2.0z Thank you for submitting! I appreciate the help