"Not logged in!" error - "That code didn't work. Check the code and try again."

As per instructions, I navigated to https://microsoft.com/devicelogin and entered the code at the top of the screen.
It gave an error message, "That code didn't work. Check the code and try again."
OneDrive is running ok on that PC that is running HASSIO as a virtual machine now, it was disconnected for a while due to a password change.
OneDrive Backup 2.2.2
Home Assistant 2023.10.0
Supervisor 2023.10.0
Operating System 10.5
Frontend 20231002.0 - latest
Can you please assist? I am concerned that backups are not running.
Thanks
Gary

If you see a message that you need to log in, backups aren't running (you can verify in the logs)
The password change probably invalidated the token. Usually a restart of the addon solves this. You should get a new code to use after restart

As you suggested, I restarted the addon, got a new code, and it worked!  THANKS!
p.s. I may respectfully suggest you add a line about restarting the addon if necessary to the dialog box that talks about signing in with https://microsoft.com/devicelogin.

I will add something in the Readme for toubleshooting.


ReactQueryDevtools component triggers warning from axe-core

Describe the bug
When using axe-core (version 4.0.0) we're getting a warning triggered by following rule All page content must be contained by landmarks because <ReactQueryDevtools /> is rendered as <div class="ReactQueryDevtools">.
Steps to reproduce the behavior:

Yarn add -D @axe-core/react
Add  `
yarn start:dev

Expected behavior
ARIA attributes should conform to valid value, so no axe-core warning appears.
Screenshots

Desktop

OS: Linux Fedora 33
Browser: Firefox 82.0.2
Version: [e.g. 22]

Additional context
Please see https://github.com/konveyor/virt-ui/blob/master/src/index.tsx#L15 and https://github.com/konveyor/virt-ui/blob/master/src/app/index.tsx#L30 for full context.

A PR to fix this is welcomed :)

You got it @tannerlinsley :) https://github.com/tannerlinsley/react-query-devtools/pull/77

Also I'm digging the VS Code workbench.colorCustomizations, didn't know you could do that 😛


remove validator dependency

the validator crate is a good short path for now to getting client-side validation that works, but because it's currently unstable v0.10, this crate can't be stabilized

refinement: it only needs to be removed from the public api, which could mean abstracting it behind types we control


Multiprocessing not installed with Hatchet through Pip

When installing Hatchet with pip install -e <path/to/hatchet>, the multiprocessing library is not installed alongside Hatchet, so the very first time you import Hatchet, you get an ImportError. The fix should be to add multiprocessing to setup.py.

By chance, did you mean the multiprocess instead of multiprocessing here? Multiprocessing ran into an issue for me when trying to install it (error below). Multiprocessing was last updated in 2009.
Collecting multiprocessing
  Downloading multiprocessing-<IP_ADDRESS>.tar.gz (108 kB)
     |████████████████████████████████| 108 kB 14.2 MB/s
    ERROR: Command errored out with exit status 1:
     command: /g/g19/brink2/anaconda3/bin/python -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/brink2/pip-install-rt7jyij8/multiprocessing/setup.py'"'"'; __file__='"'"'/tmp/brink2/pip-install-rt7jyij8/multiprocessing/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' egg_info --egg-base /tmp/brink2/pip-install-rt7jyij8/multiprocessing/pip-egg-info
         cwd: /tmp/brink2/pip-install-rt7jyij8/multiprocessing/
    Complete output (6 lines):
    Traceback (most recent call last):
      File "<string>", line 1, in <module>
      File "/tmp/brink2/pip-install-rt7jyij8/multiprocessing/setup.py", line 94
        print 'Macros:'
                      ^
    SyntaxError: Missing parentheses in call to 'print'. Did you mean print('Macros:')?
    ----------------------------------------
ERROR: Command errored out with exit status 1: python setup.py egg_info Check the logs for full command output.


Entering debug mode disappears text rendered in top bar and code window

Discord username
No response
What type of issue is this?
Permanent – Occurring repeatably
Is this issue blocking you from using Enso?

[ ] Yes, I can't use Enso because of this issue.

Is this a regression?

[X] Yes, previous version of Enso did not have this issue.

What issue are you facing?
When entering debug mode project title, breadcrumbs and code disappears instantly. Code can still be selectable, so it's there but rendered transparent?
Vid fragment demonstrating the issue:
https://user-images.githubusercontent.com/108271897/234951056-a801918c-3e6f-45f5-aada-6beeaeee948c.mp4
Expected behaviour
After entering debug mode no text disappears.
How we can reproduce it?
No response
Screenshots or screencasts
Entire session (with logs recorded on previous than shared above attempts):
https://user-images.githubusercontent.com/108271897/234951266-70086715-1a25-4f83-8ca8-dda8de4fd429.mp4
Enso Version
2023.4.27 nightly
Browser or standalone distribution
Standalone distribution
Browser Version or standalone distribution
standalone
Operating System
Windows
Operating System Version
Win11pro 22H2 22621.1555
Hardware you are using
12th Gen Intel(R) Core(TM) i9-12900HK / RTX3060 Laptop / Nvidia Drivers 531.68

Can reproduce, and it seems the following warning pops up when the texts disappear.
Since only test on the panel layer disappears, I assume this might be related to layering or the text implementation.

This appears to be present for a long time, before February. Before that, I'm running into trouble with the old build, so I won't bisect this further back. The oldest commit I was able to check and confirm this happens was  50f376e365cfea9a571afff49eda89f47fcad450


Retrofit with OkHttp crashes with SIGPIPE when returning from lock screen

When using Retrofit with OkHttp, when locking the screen on a real device (iPhone 5s, iOS 9.3.4) with the power button, and then unlocking the screen, the app sometimes (often) crashes with SIGPIPE.
I'm working on a repo case, in the meantime, did you encounter this before? Do you have a workaround?
Thanks,
Alex.

Dear Alex,
This is an iOS behavior (I'm not even sure it's considered a bug). A workaround that may help:

Have generateProject false set
Add signal handling

#include <MOE/MOE.h>
#include <signal.h>

int main(int argc, char *argv[]) {
    signal(SIGPIPE, SIG_IGN);
    return moevm(argc, argv);
}

I tried this, it doesn't help.

Oh, actually it does help. I just saw that the debugger still breaks on the sigpipe, so I thought it still crashes, but actually it continues to run.
But if we ignore this signal, will retrofit/okhttp know that an error occured so we can retry or act accordingly?

Seems to work well.
Thanks.


TypeError: 'type' object is not subscriptable

Environment:

python == 3.8
graphene-federation == 3.0.2
Django == 3.2

Steps to reproduce:

set graphene-federation to 3.0.2
run server

Hey, can you please add some code & stacktrace info? Not every project on federation 3.0.2 breaks.

Pull request to solve the issue: https://github.com/graphql-python/graphene-federation/pull/10


Unstable VIP PING & K3S too new for Rancher

this link gets a 404, but i did the k3s trouble shooting check list,
https://github.com/techno-tim/k3s-ansible/discussions/20

I was able to get this working with a older release
with most current I get:
unstable Ping VIP IP#
K3S  need to be < v1.24 for Rancher
Expected Behavior

VIP end point ping should be stable
Helm should be able to deploy Rancher with documented commands
Current Behavior

You can ping the VIP/API IP# intermittently , so get node and helm deployments are hit or miss
Rancher Deployment will fail because K3S is > 1.24
Steps to Reproduce

deploy with code base that had all.yml Commits on May 26, 2022, 3 etcd control, 5 workers Proxmox VM
(across there physical nodes)
deploy longhorn in default space, shared with workers (just learning the process)
deploy minecraft > everything was stable for weeks, though it kept over poding one node
backup, take down minecraft and longhorn
reset
git pull on 8/1/22, use latest
which has changes to, all.yml, main.yml, metallb configmap metallb ipaddresspool, metallb yamls, vip rbac, vip yaml
add 3 VM for dedicated longhorn > verify ansible can apt update and install proxmox guest agent and can password less ssh
add 3x IP# under nodes (3 control, 5 workers, 3 worker for longhorn only)
deploy with 8/1/22 version

Context (variables)

Operating system: Ubuntu 22
Hardware: 2x dual xeon nodes, 48 thread, 256GB Ram, 1x 1 liter node with a i5 10th 64GB Ram
Variables Used:
I didn't alter these, save adding my own token and IP#
they are what have been listed in the repo
all.yml
k3s_version: "1.24"
ansible_user: NA
systemd_dir: ""

flannel_iface: ""

apiserver_endpoint: ""

k3s_token: "NA"

extra_server_args: ""
extra_agent_args: ""

kube_vip_tag_version: ""

metal_lb_speaker_tag_version: ""
metal_lb_controller_tag_version: ""

metal_lb_ip_range: ""

Hosts
host.ini
[master]
IP.ADDRESS.ONE
IP.ADDRESS.TWO
IP.ADDRESS.THREE

[node]
IP.ADDRESS.FOUR
IP.ADDRESS.FIVE

[k3s_cluster:children]
master
node

Possible Solution

It seems to deploy ok, just something isn't quite the same when it comes to the VIP/API IP# access
From what I can the version changes are very particular
I tried taking various nodes offline one at a time, this didn't really help in any repeatable way. So I don't think it's any one node/vm or it's physical networking
tried just going to a older k3s , which might of helped rancher, but didn't help vip/metallb.
I'll try to see if I can find a vip or metallb log file (but I don't really know vip or metallb)
for now, going to try reversing the pull request and deployment with older stack

kept newest code, but going back to all.yml with:
k3s_version: v1.23.4+k3s1
this is the user that has ssh access to these machines
ansible_user: ----
systemd_dir: /etc/systemd/system
Set your timezone
system_timezone: "America/New_York"
interface which will be used for flannel
flannel_iface: "eth0"
apiserver_endpoint is virtual ip-address which will be configured on each master
apiserver_endpoint: "<IP_ADDRESS>"
k3s_token is required  masters can talk together securely
this token should be alpha numeric only
k3s_token: "some-SUPER-DEDEUPER-secret-password"
change these to your liking, the only required one is--no-deploy servicelb
extra_server_args: "--no-deploy servicelb --no-deploy traefik"
extra_agent_args: ""
image tag for kube-vip
kube_vip_tag_version: "v0.4.4"
image tag for metal lb
metal_lb_speaker_tag_version: "v0.12.1"
metal_lb_controller_tag_version: "v0.12.1"
metallb ip range for load balancer
metal_lb_ip_range: "<IP_ADDRESS>-<IP_ADDRESS>"

the api IP# and get nodes are now stable
rancher will deploy
however  after
kubectl expose deployment rancher -n cattle-system --type=LoadBalancer --name=rancher-lb --port=443
external IP# is pending forever

kubectl get all -A
NAMESPACE                   NAME                                          READY   STATUS      RESTARTS      AGE
cattle-fleet-local-system   pod/fleet-agent-699b5fb945-nsxnx              1/1     Running     0             13m
cattle-fleet-system         pod/fleet-controller-784d6fbcd8-hngpn         1/1     Running     0             14m
cattle-fleet-system         pod/gitjob-6b977748fc-7rsh8                   1/1     Running     0             14m
cattle-system               pod/helm-operation-7vpxj                      0/2     Completed   0             14m
cattle-system               pod/helm-operation-8m924                      0/2     Completed   0             13m
cattle-system               pod/helm-operation-fcx2g                      0/2     Completed   0             15m
cattle-system               pod/helm-operation-v89kg                      0/2     Completed   0             14m
cattle-system               pod/rancher-7fd65d9cd6-2f5vv                  1/1     Running     0             17m
cattle-system               pod/rancher-7fd65d9cd6-qlqp7                  1/1     Running     0             17m
cattle-system               pod/rancher-7fd65d9cd6-slnqr                  1/1     Running     0             17m
cattle-system               pod/rancher-webhook-5b65595df9-l5b7x          1/1     Running     0             13m
cert-manager                pod/cert-manager-76d44b459c-kdzqv             1/1     Running     0             18m
cert-manager                pod/cert-manager-cainjector-9b679cc6-wp959    1/1     Running     0             18m
cert-manager                pod/cert-manager-webhook-57c994b6b9-tqgnv     1/1     Running     0             18m
kube-system                 pod/coredns-5789895cd-cbzzm                   1/1     Running     0             56m
kube-system                 pod/kube-vip-ds-4lntv                         1/1     Running     0             56m
kube-system                 pod/kube-vip-ds-j65z7                         1/1     Running     2 (16m ago)   56m
kube-system                 pod/kube-vip-ds-m8vcq                         1/1     Running     0             56m
kube-system                 pod/local-path-provisioner-6c79684f77-zk8jj   1/1     Running     0             56m
kube-system                 pod/metrics-server-7cd5fcb6b7-czzjp           1/1     Running     0             56m
metallb-system              pod/controller-74df79bb55-qvldk               1/1     Running     0             56m
metallb-system              pod/speaker-28fk6                             1/1     Running     0             53m
metallb-system              pod/speaker-2mhzf                             1/1     Running     0             56m
metallb-system              pod/speaker-8zwrg                             1/1     Running     0             53m
metallb-system              pod/speaker-96mb5                             1/1     Running     0             53m
metallb-system              pod/speaker-bmhpn                             1/1     Running     0             56m
metallb-system              pod/speaker-jggcr                             1/1     Running     0             53m
metallb-system              pod/speaker-mr7mc                             1/1     Running     0             53m
metallb-system              pod/speaker-rb8dp                             1/1     Running     0             53m
metallb-system              pod/speaker-rkktx                             1/1     Running     0             53m
metallb-system              pod/speaker-t89s6                             1/1     Running     0             53m
metallb-system              pod/speaker-v7vss                             1/1     Running     0             56m
NAMESPACE             NAME                           TYPE           CLUSTER-IP      EXTERNAL-IP   PORT(S)                  AGE
cattle-fleet-system   service/gitjob                 ClusterIP      <IP_ADDRESS>            80/TCP                   14m
cattle-system         service/rancher                ClusterIP      <IP_ADDRESS>           80/TCP,443/TCP           17m
cattle-system         service/rancher-lb             LoadBalancer   <IP_ADDRESS>        443:31202/TCP            11m
cattle-system         service/rancher-webhook        ClusterIP      <IP_ADDRESS>           443/TCP                  13m
cattle-system         service/webhook-service        ClusterIP      <IP_ADDRESS>           443/TCP                  13m
cert-manager          service/cert-manager           ClusterIP      <IP_ADDRESS>            9402/TCP                 18m
cert-manager          service/cert-manager-webhook   ClusterIP      <IP_ADDRESS>           443/TCP                  18m
default               service/kubernetes             ClusterIP      <IP_ADDRESS>               443/TCP                  57m
kube-system           service/kube-dns               ClusterIP      <IP_ADDRESS>              53/UDP,53/TCP,9153/TCP   56m
kube-system           service/metrics-server         ClusterIP      <IP_ADDRESS>             443/TCP                  56m
metallb-system        service/webhook-service        ClusterIP      <IP_ADDRESS>           443/TCP                  56m
NAMESPACE        NAME                         DESIRED   CURRENT   READY   UP-TO-DATE   AVAILABLE   NODE SELECTOR            AGE
kube-system      daemonset.apps/kube-vip-ds   3         3         3       3            3                              56m
metallb-system   daemonset.apps/speaker       11        11        11      11           11          kubernetes.io/os=linux   56m
NAMESPACE                   NAME                                      READY   UP-TO-DATE   AVAILABLE   AGE
cattle-fleet-local-system   deployment.apps/fleet-agent               1/1     1            1           13m
cattle-fleet-system         deployment.apps/fleet-controller          1/1     1            1           14m
cattle-fleet-system         deployment.apps/gitjob                    1/1     1            1           14m
cattle-system               deployment.apps/rancher                   3/3     3            3           17m
cattle-system               deployment.apps/rancher-webhook           1/1     1            1           13m
cert-manager                deployment.apps/cert-manager              1/1     1            1           18m
cert-manager                deployment.apps/cert-manager-cainjector   1/1     1            1           18m
cert-manager                deployment.apps/cert-manager-webhook      1/1     1            1           18m
kube-system                 deployment.apps/coredns                   1/1     1            1           56m
kube-system                 deployment.apps/local-path-provisioner    1/1     1            1           56m
kube-system                 deployment.apps/metrics-server            1/1     1            1           56m
metallb-system              deployment.apps/controller                1/1     1            1           56m
NAMESPACE                   NAME                                                DESIRED   CURRENT   READY   AGE
cattle-fleet-local-system   replicaset.apps/fleet-agent-699b5fb945              1         1         1       13m
cattle-fleet-local-system   replicaset.apps/fleet-agent-86b78d86bf              0         0         0       13m
cattle-fleet-system         replicaset.apps/fleet-controller-784d6fbcd8         1         1         1       14m
cattle-fleet-system         replicaset.apps/gitjob-6b977748fc                   1         1         1       14m
cattle-system               replicaset.apps/rancher-7fd65d9cd6                  3         3         3       17m
cattle-system               replicaset.apps/rancher-webhook-5b65595df9          1         1         1       13m
cert-manager                replicaset.apps/cert-manager-76d44b459c             1         1         1       18m
cert-manager                replicaset.apps/cert-manager-cainjector-9b679cc6    1         1         1       18m
cert-manager                replicaset.apps/cert-manager-webhook-57c994b6b9     1         1         1       18m
kube-system                 replicaset.apps/coredns-5789895cd                   1         1         1       56m
kube-system                 replicaset.apps/local-path-provisioner-6c79684f77   1         1         1       56m
kube-system                 replicaset.apps/metrics-server-7cd5fcb6b7           1         1         1       56m
metallb-system              replicaset.apps/controller-74df79bb55               1         1         1       56m

api enpoint ip stable ping with all below
will try again with newer k3s
but with 1.23
helm install cert-manager jetstack/cert-manager --namespace cert-manager --version v1.7.1
gets stuck
even though
kubectl get pods --namespace cert-manager
NAME                                     READY   STATUS    RESTARTS      AGE
cert-manager-76d44b459c-wr4bp            1/1     Running   0             3m3s
cert-manager-cainjector-9b679cc6-nnx9m   1/1     Running   0             3m3s
cert-manager-startupapicheck-nrrkb       1/1     Running   2 (58s ago)   3m2s
cert-manager-webhook-57c994b6b9-7w959    1/1     Running   0             3m3s

k3s_version: v1.23.4+k3s1

this is the user that has ssh access to these machines
ansible_user: ----
systemd_dir: /etc/systemd/system
Set your timezone
system_timezone: "America/New_York"
interface which will be used for flannel
flannel_iface: "eth0"
apiserver_endpoint is virtual ip-address which will be configured on each master
apiserver_endpoint: "<IP_ADDRESS>"
k3s_token is required  masters can talk together securely
this token should be alpha numeric only
k3s_token: "some-SUPER-DEDEUPER-secret-password"
change these to your liking, the only required one is--no-deploy servicelb
extra_server_args: "--no-deploy servicelb --no-deploy traefik"
extra_agent_args: ""
image tag for kube-vip
#kube_vip_tag_version: "v0.4.4"
kube_vip_tag_version: "v0.5.0"
image tag for metal lb
#metal_lb_speaker_tag_version: "v0.12.1"
#metal_lb_controller_tag_version: "v0.12.1"
metal_lb_speaker_tag_version: "v0.13.4"
metal_lb_controller_tag_version: "v0.13.4"
metallb ip range for load balancer
metal_lb_ip_range: "<IP_ADDRESS>-<IP_ADDRESS>"

kubectl get pods --namespace cert-manager
NAME                                     READY   STATUS             RESTARTS      AGE
cert-manager-76d44b459c-wr4bp            1/1     Running            0             5m6s
cert-manager-cainjector-9b679cc6-nnx9m   1/1     Running            0             5m6s
cert-manager-startupapicheck-nrrkb       0/1     CrashLoopBackOff   3 (18s ago)   5m5s
cert-manager-webhook-57c994b6b9-7w959    1/1     Running            0             5m6s

https://github.com/cert-manager/cert-manager/issues/2773

ok get nodes and ping to the API are stable, using the newest all,yml
able to cert manager

k3s_version: v1.24.3+k3s1
#k3s_version: v1.23.4+k3s1
this is the user that has ssh access to these machines
ansible_user: ---
systemd_dir: /etc/systemd/system
Set your timezone
system_timezone: "America/New_York"
interface which will be used for flannel
flannel_iface: "eth0"
apiserver_endpoint is virtual ip-address which will be configured on each master
apiserver_endpoint: "<IP_ADDRESS>"
k3s_token is required  masters can talk together securely
this token should be alpha numeric only
k3s_token: "some-SUPER-DEDEUPER-secret-password"
change these to your liking, the only required one is--no-deploy servicelb
extra_server_args: "--no-deploy servicelb --no-deploy traefik"
extra_agent_args: ""
image tag for kube-vip
#kube_vip_tag_version: "v0.4.4"
kube_vip_tag_version: "v0.5.0"
image tag for metal lb
#metal_lb_speaker_tag_version: "v0.12.1"
#metal_lb_controller_tag_version: "v0.12.1"
metal_lb_speaker_tag_version: "v0.13.4"
metal_lb_controller_tag_version: "v0.13.4"
metallb ip range for load balancer
metal_lb_ip_range: "<IP_ADDRESS>-<IP_ADDRESS>"

helm install rancher rancher-stable/rancher
--namespace cattle-system ....
Error: INSTALLATION FAILED: chart requires kubeVersion: < 1.24.0-0 which is incompatible with Kubernetes v1.24.3+k3s1
looks there is 1.24 rancher out there
https://github.com/rancher/client-go/releases/tag/v1.24.0-rancher1
trying to figure out how to point to it

Yea that did it
NAME: rancher
LAST DEPLOYED: Mon Aug  1 19:10:43 2022
NAMESPACE: cattle-system
STATUS: deployed

Rancher is not yet compatible with k3s 1.24.  It may be soon but that is really going to be up to Rancher to make it compatible.

I think support is coming in k3s 2.67,  I would check their release notes.

also rancher isn't compatible with the latest cert-manager

also, I've been pining my vip for over an hour now and it's stable.

after the did a pull I had a unstable ping for 2x re-deployment rounds with no error in output before I put up the post.  I think just something minor was off in my all.yml copy, as later deployments were very stable. I mentioned in later comment that I ended up being able to get stable ping, sorry you wasted time pining. can no longer reproduce.
Re: Support is coming in 2.67, thank you, yes found that as well. https://github.com/rancher/rancher/issues/37711
Re: 1.24, just trying to point out that the source copy of all.yml on your repo has a line that installs 1.24
I know a k3s deployment and rancher are separate, and I don't know the k3s deployment's target, but if people follow your guidance docs & videos, pull /clone the all.yml script that points to 1.24 and try to deploy rancher they'll run into it, not a big deal.
just suggesting a known rancher compatible version stack/branch for your k3s deployment, as well as a latest k3s stack, in this case it's only a line, but I think rancher will always lag behind k3s and you also mentioned cert manager versions, could be other things down the line. I could try to expand an ansiable script for a rancher on top stack, post it, if there's any interest / value

Thank you for bringing this up and all the details


Restrict Metabase Access to VPN

For extra security, our Metabase instances should only be available when on the VPN.

Removed Chris from ticket.

Not needed, very old issue.


french translations for the reset password bundle

Translations were AI Generated by AWS Translate Machine Learning Platform and need to be Validated by humans
Includes all of the French translations for Symfony Cast's Reset Password Bundle in PR #1100

Hello, why translation PR is not merged please?

Closing because the related #1100 proposal was closed. Sorry! And thank you!


feat: integrate auth with client

What kind of change does this PR introduce?
Add ability to use gotrue for auth
What is the current behavior?
Please link any relevant issues here.
What is the new behavior?
Feel free to include screenshots if it includes visual changes.
Additional context
Add any other context or screenshots.

I've taken this out of WIP state. I think the overall changes are ready and it provides basic auth functionality.
https://github.com/supabase-community/postgrest-go/pull/48


Document schema of catalog.json, run_results.json, manifest.json

Describe the feature
As dbt is getting more and more popular, people are building on top of it. It's becoming more and more important to specify schema of catalog.json, run_results.json, manifest.json. probably adding integration tests which assert that those files actually conform to the schema would be nice too to make sure they don't go out of sync
Describe alternatives you've considered
There are no alternatives.
Additional context
By schema I mean JSON-schema or typescript definitions or anything like it. as long as we have some schema which would be up to date, people can then convert one schema representation to other.
app.quicktype.io might be helpful to generate initial schema from sample JSON itself and then refine it..
Who will this benefit?
People working automations and tools on top of dbt will be able to know what the structure of those files is exactly. they will be able to write correct software, which is especially important to the users of dbt as they are working on critically important data.
Are you interested in contributing this feature?
I think this is something library authors will be able to do most effectively. I can review the changes. also if you were to implement it using JSON scheme I would volunteer to convert it to typescript definitions (that's what I actually want in the end).

@safareli You'll be pleased to know that we're version controlling these artifacts, and hosting their JSONSchemas, starting in the next version of dbt (v0.19.0). E.g. you can find:

The v0 of run results, as it existed in v0.18.1: https://schemas.getdbt.com/dbt/run-results/v0.json
The v1 of run results, coming in v0.19: https://schemas.getdbt.com/dbt/run-results/v1.json

See prerelease docs for more details.

Thanks, that's great!

Thanks, that's great!


How to enable beta ui?

Setting CONSUL_UI_BETA=true using
environment:
  CONSUL_UI_BETA: true

does not work

Hi, that was just pushed to the v2.0.1 so you'll need to update your role version and it is should then work.

Thanks!
consul_env_vars:
  - "CONSUL_UI_BETA=true"

works fine


Ignore deprecated values

I found this useful when trying to run the analyser on coq/coq.

I can see cases where this is useful, but I think this should be controlled by some command-line flag.  One might want to mark some function as being deprecated within a project, incrementally get rid of it, but then finally actually remove the function : in such a scenario, one want the analyzer to report such function even if deprecated.


refactor: rename test opt to RequireLocalGitProvider

This name avoids a double negative which helps readability.

/assign @karlkfi


Parse rating value correctly

Ratings were always being parsed as 5, this PR fixes that and parses the title attributes of the .rating span, which contains the numerical rating.

I'll test it tomorrow.

Thanks to your help! 👍


Bug hunt: illegal memory access

This occurs when modifying a few things in AWQ. I have not yet found the reason why but this bug needs to be squashed because it is preventing a few upgrades.
RuntimeError: CUDA error: an illegal memory access was encountered
Compile with `TORCH_USE_CUDA_DSA` to enable device-side assertions.

You can trigger this by modifying batch_size from 1 to 2 here:
https://github.com/casper-hansen/AutoAWQ/blob/560fbe59bc94d3d421fa966e6e877c3ec53947a8/awq/entry.py#L105
It also triggers on the exllama branch when running the speed test:
https://github.com/casper-hansen/AutoAWQ/blob/855854a75827106e4fd411e5cfcb83e1eb12c8a1/awq/entry.py#L141

The problem also occurred in my case.
model: llama-13b, awq_model_w4_g128.pt
ids = torch.randint(0, tokenizer.vocab_size, (2, n_context)).cuda
out = model(ids)
out.logits

I have verified that the original AWQ  has NOT the problem, what's the difference after your refactor?

There should practically be a minimal difference between the actual quantization code. I will have to further investigate this bug as it prevents quite a few things in terms of progression.
@wanzhenchn I would love any and all help in terms of debugging/reporting when this happens.

@wanzhenchn I have now tested the original llm-awq and it seems the bug is also present there.
import time
import torch
from awq.utils.utils import simple_dispatch_model
from awq.quantize.quantizer import real_quantize_model_weight
from transformers import AutoModelForCausalLM, AutoTokenizer, AutoConfig
from accelerate import init_empty_weights, infer_auto_device_map, load_checkpoint_in_model

def fuse(model, device="cuda:0"):
    from tinychat.modules import make_quant_norm, make_quant_attn, make_fused_mlp
    make_quant_attn(model, device)
    make_quant_norm(model)
    make_fused_mlp(model)

def load(model_path="vicuna-7b-v1.5-awq", checkpoint="awq_model_w4_g128.pt"):
    config = AutoConfig.from_pretrained(model_path, trust_remote_code=True)
    tokenizer = AutoTokenizer.from_pretrained(model_path, use_fast=False, trust_remote_code=True)

    with init_empty_weights():
        model = AutoModelForCausalLM.from_config(config=config, torch_dtype=torch.float16, trust_remote_code=True)

    real_quantize_model_weight(
        model, w_bit=4, q_config={"zero_point": True, "q_group_size": 128}, init_only=True
    )

    model.tie_weights()

    # Infer device map
    kwargs = {}
    device_map = infer_auto_device_map(
        model,
        no_split_module_classes=[
            "OPTDecoderLayer", "LlamaDecoderLayer", "BloomBlock", "MPTBlock", "DecoderLayer"],
        **kwargs
    )
    # Load checkpoint in the model
    load_checkpoint_in_model(
        model,
        checkpoint=f"{model_path}/{checkpoint}",
        device_map=device_map,
        offload_state_dict=True,
    )

    # Fuse model
    fuse(model)

    # Dispatch model
    model = simple_dispatch_model(model, device_map=device_map)

    model.eval()

    return model, tokenizer

@torch.inference_mode()
def run_speed(device="cuda:0", n_generate=128, max_new_tokens=256):
    def _timer(func):
        start = time.time()
        out = func()
        return out, time.time() - start

    def _generate(model, model_out, n_generate):
        past_key_values = model_out.past_key_values

        for i in range(n_generate):
            logits = model_out.logits[0, -1, :]
            probs = torch.softmax(logits, dim=-1)
            token = torch.multinomial(probs, num_samples=1)
            token = torch.as_tensor([token], device=device).unsqueeze(0)

            model_out = model(token, use_cache=True, past_key_values=past_key_values)

    def _warmup(device:str):
        warm_up = torch.randn((4096,4096)).to(device)
        torch.mm(warm_up,warm_up)

    # Load model
    model, tokenizer = load()
    _warmup(device)

    # Generate random inputs
    n_context = max_new_tokens - n_generate
    ids = torch.randint(0, tokenizer.vocab_size, (2, n_context)).cuda()

    # Context stage
    model_out, context_time = _timer(lambda: model(ids, use_cache=True))

    # Generation stage
    _, generation_time = _timer(lambda: _generate(model, model_out, n_generate))

    # Prints
    memory_used = torch.cuda.max_memory_allocated(device) / (1024 ** 2)
    context_tokens_per_second = n_context / context_time
    context_ms_per_token = (context_time*1000) / n_context
    inference_tokens_per_second = n_generate / generation_time
    inference_ms_per_token = (generation_time*1000) / n_generate

    print(f"[======] Model summary [======]")
    print(f"[*] Context speed: {context_tokens_per_second:.2f} tokens/second ({context_ms_per_token:.2f} ms/token)")
    print(f"[*] Generation speed: {inference_tokens_per_second:.2f} tokens/second ({inference_ms_per_token:.2f} ms/token)")
    print(f"[*] VRAM: {memory_used:.2f} MB")

if __name__ == '__main__':
    run_speed()

The API I tested is llm-awq/awq, the StreamGenerator() in tinychat/stream_generators/stream_gen.py is named benchmark() and merged into awq/entry.py, the whole code is here: https://github.com/mit-han-lab/llm-awq/issues/79#issuecomment-1700334812.
The difference lies in whether the model has been fused, so I suspect that the fused model might be causing this issue.

I have verified that the FUSED MODEL caused this problem!

Further investigation revealed that the issue is triggered by fuse_attention() in awq/models/llama.py
    def fuse_attention(self):
        for name, module in self.attention_modules:
            qkv_layer: WQLinear = self._fuse_qkv(module)
            attn = QuantLlamaAttention(
                module.hidden_size,
                module.num_heads,
                qkv_layer,
                module.o_proj,
                qkv_layer.qweight.device,
                self.model.config.max_new_tokens
            )
            set_module_name(self.model, name, attn)

@tonylins could you please help to debug this question?

Further investigation revealed that the issue is triggered by fuse_attention() in awq/models/llama.py

Thank you for investigating. There must be an issue somewhere when fusing the linear layers in LlamaAttention. I will have to investigate further, maybe rebuild it from scratch.

Further investigation revealed that the issue is triggered by fuse_attention() in awq/models/llama.py

Thank you for investigating. There must be an issue somewhere when fusing the linear layers in LlamaAttention. I will have to investigate further, maybe rebuild it from scratch.

Yeah, the problem seems to have been fixed in https://github.com/mit-han-lab/llm-awq/pull/8, However, this could be another issue.

Yeah, the problem seems to have been fixed in mit-han-lab/llm-awq#8, However, this could be another issue.

This seems to be another issue, and this commit is already included in AutoAWQ. I have tested more and implemented #26  as a start but still need more testing to figure out and solve the issue.

Yeah, the problem seems to have been fixed in mit-han-lab/llm-awq#8, However, this could be another issue.

This seems to be another issue, and this commit is already included in AutoAWQ. I have tested more and implemented #26 as a start but still need more testing to figure out and solve the issue.

I have tested and found that if the quantized model fusion is disable, its throughput performance is nearly the same as FP16.

I have tested and found that if the quantized model fusion is disable, its throughput performance is nearly the same as FP16.

Yes, default LLaMa models are slow in general because of the many extra linear layers, unlike other architectures like Falcon or MPT. We fuse the QKV operation, which works fine, and we use rotary embeddings from vLLM (which is causing this illegal memory access). I am working on fixing this issue to enable multi-GPU and batch size >1 in #28


Update post dependency

Motivation
Updates post dependency.
Description
n/a
Test Plan
n/a
TODO

[x] Explain motivation or link existing issue(s)
[x] Test changes and document test plan
[x] Update documentation as needed
[x] Update changelog as needed

bors merge


Error Messages

Hi, my error log is full of these - anything I should worry about?
[27-Sep-2017 16:34:09 UTC] PHP Warning:  curl_setopt_array(): Curl option contains invalid characters (\0) in /home/@@@@@/public_html/php-proxy/vendor/athlon1600/php-proxy/src/Proxy.php on line 142

Closed


DYNAMIC_ARCH differences on cmake vs make

ARM64 on cmake
https://github.com/xianyi/OpenBLAS/blob/eb2eddf241dd5e46e0064cd311b6a63229897d21/cmake/arch.cmake#L48
while on make
https://github.com/xianyi/OpenBLAS/blob/69b16a894dedda06b62fba763aa964f973d6808b/Makefile.system#L549-L552
POWER on cmake is not supported.
make has https://github.com/xianyi/OpenBLAS/blob/69b16a894dedda06b62fba763aa964f973d6808b/Makefile.system#L555-L568

Right, my mistake from #1908 (ARM64) where I added the cmake version of the cpu list after rengolin's rearrangement of the cpu model support, but both the list in the Makefile and the runtime checks still reflect ashwinyes' original, shorter list. I will create a PR for this later today.


Non local generic file system

Ensures the non-Node-specific FileSystem does not have any local functions.
Fixes #10112

Codecov Report

Merging #10113 (ea27795) into main (760d61e) will increase coverage by 0%.
The diff coverage is 100%.

:exclamation: Current head ea27795 differs from pull request most recent head 900943c. Consider uploading reports for the commit 900943c to get more accurate results

@@          Coverage Diff          @@
##           main   #10113   +/-   ##
=====================================
  Coverage    64%      64%
=====================================
  Files       203      203
  Lines      9239     9238    -1
  Branches   1488     1487    -1
=====================================
+ Hits       5927     5932    +5
+ Misses     2852     2844    -8
- Partials    460      462    +2

Impacted Files
Coverage Δ

src/platform/common/platform/types.node.ts
100% <ø> (ø)

src/platform/common/platform/types.ts
100% <ø> (ø)

src/platform/common/platform/fileSystem.node.ts
82% <100%> (+1%)
:arrow_up:

src/platform/common/platform/fileSystem.ts
81% <100%> (+1%)
:arrow_up:

src/platform/common/variables/environment.node.ts
95% <100%> (ø)

...latform/logging/gitHubIssueCommandListener.node.ts
32% <100%> (ø)

src/platform/errors/errorHandler.ts
62% <0%> (-1%)
:arrow_down:

...rc/platform/common/dataScienceSurveyBanner.node.ts
70% <0%> (+5%)
:arrow_up:


[BUG] org.opensearch.recovery.RelocationIT.testRelocateWhileWaitingForRefresh is flaky

Describe the bug
The test case org.opensearch.recovery.RelocationIT.testRelocateWhileWaitingForRefresh is flaky:
org.opensearch.recovery.RelocationIT.testRelocateWhileWaitingForRefresh

java.lang.AssertionError: Unexpected ShardFailures: [shard [[-RiKDuSXScO6_bS1kOrA9w][test][0]], reason [NodeDisconnectedException[[node_t1][<IP_ADDRESS>:44623][indices:data/read/search[phase/fetch/id]] disconnected]], cause [NodeDisconnectedException[[node_t1][<IP_ADDRESS>:44623][indices:data/read/search[phase/fetch/id]] disconnected]
]]
Expected: <0>
     but: was <1>
	at __randomizedtesting.SeedInfo.seed([6D8F777A72F32A76]:0)
	at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:18)
	at org.opensearch.test.hamcrest.OpenSearchAssertions.assertNoFailures(OpenSearchAssertions.java:339)
	at org.opensearch.recovery.RelocationIT.lambda$testIndexSearchAndRelocateConcurrently$8(RelocationIT.java:550)
	at java.base/java.lang.Thread.run(Thread.java:833)

To Reproduce
./gradlew ':server:internalClusterTest' --tests "org.opensearch.recovery.RelocationIT.testIndexSearchAndRelocateConcurrently" -Dtests.seed=6D8F777A72F32A76

Expected behavior
A clear and concise description of what you expected to happen.
Plugins
Standard
Screenshots
If applicable, add screenshots to help explain your problem.
Host/Environment (please complete the following information):

CI

Additional context

https://build.ci.opensearch.org/job/gradle-check/29612/testReport/junit/org.opensearch.recovery/RelocationIT/testRelocateWhileWaitingForRefresh/

Closing in favour of https://github.com/opensearch-project/OpenSearch/issues/14309


feat(storage): metrics logging and less verbose event logging

What this PR does
This patch changes logging for storage:

Make event logging less verbose, which enables only logs for errors and slow I/O.
Add metrics logging to the storage for investigating details.

Codecov Report
Patch coverage: 34.09% and project coverage change: +0.10 :tada:

Comparison is base (65278e2) 63.37% compared to head (5502a81) 63.48%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #388      +/-   ##
==========================================
+ Coverage   63.37%   63.48%   +0.10%
==========================================
  Files         131      131
  Lines       17609    17650      +41
==========================================
+ Hits        11160    11205      +45
- Misses       5900     5909       +9
+ Partials      549      536      -13

Impacted Files
Coverage Δ

internal/storage/config.go
64.28% <33.33%> (-2.07%)
:arrow_down:

internal/storage/storage.go
77.72% <34.21%> (-9.71%)
:arrow_down:

... and 7 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Fix rust-book-sync link in book

I noticed it is not linked anywhere, so tried to point it to the right place.

There is also a link missing for Future, but not sure where to point it to.

Thanks!

I think the [Future] link should go to std-futures.


[BUG] LIGHTNODE COINBASE Purchase "Unsupported Asset"

When trying to buy a light node using a Coinbase wallet, the pop-up diablog shows "Unsupported asset"
Unsupported Asset pay.coinbase.com-1727464307466.log


Need more init routines for G8RecognitionOperation

Why have you defined only one signature for initWithLanguage routine in G8RecognitionOperation class? It wraps G8Tesseract with totally 5 of them and an option to pass all available params to initializer will be the best, IMHO.
Is it in your TODOs list or there are some implicit limitations for setting different language, whitelisted chars, etc. for every new operation created?

It's up to you to create any operations.
This is just kind of an example.
There are no plans to support any operations at all.
It doesn't relate to the Tesseract so.


Feature Request: Requested money list should be sorted by Date Descending - Reported by: @Prashant Mangukiya

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

Action Performed:
1.Navigate to app
2. Send multiple IOU requests to the same user
3. Open IOU details modal
4. Check  sorting of the requests
Expected Result:
Requested money list should be sorted by Date Descending.  Recently requested money should be at top (instead of bottom).
Actual Result:
Requested money list is sorted by Date Ascending.  Recently requested money is at the bottom.
Workaround:
Unknown
Platform:

Where is this issue occurring?

Web
iOS
Android
Desktop App
Mobile Web

Version Number: 1.1.19-0
Reproducible in staging?: Y
Reproducible in production?: Y
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation

Expensify/Expensify Issue URL:
Issue reported by: @Prashant Mangukiya
Slack conversation: https://expensify.slack.com/archives/C01GTK53T8Q/p1639137552002700
View all open jobs on GitHub

Triggered auto assignment to @trjExpensify (AutoAssignerTriage), see https://stackoverflow.com/c/expensify/questions/4749 for more details.

Proposed Solution: (If considered as external)
We have to reverse reportActions within IOUTransactions.js file.
https://github.com/Expensify/App/blob/d827b9b9abdee6dd8cedb520ce51f38e39dccf3e/src/pages/iou/IOUTransactions.js#L74-L100
Solution: We have to reverse this.props.reportActions before rendering.  As this.props.reportActions not pure array so we can not use array.reverse(). So we have to use _.sortBy()  but it will always return ascending array by default, so we have to reverse it. There are different way to reverse it. I used sequenceNumber field to reverse via sort handler.  (We can also use timestamp if suggested by reviewer).
render() {
  const reportActionsReverse = _.sortBy(this.props.reportActions, report => report.sequenceNumber * -1);
   return (
       <View style={[styles.mt3]}>
           {_.map(reportActionsReverse, (reportAction) => {
              .....   // Existing code
           })}
       </View>
   );

We can also sort other way as shown under. But I feel above sort method efficient so suggested it.
// Sort by timestamp (we can also use this)
const reportActionsReverse = _.sortBy(this.props.reportActions, report => report.timestamp * -1);

// First convert to array and use array.reverse() function. (not suggested. two step process)
const reportActionsReverse = _.sortBy(this.props.reportActions).reverse();

Below is the screen shot after applying the reverse:

@mvtglobally thanks, please correct my Github user name as  @PrashantMangukiya for reported by. (remove space between first and last name)

I don't think I agree with the problem. Most recent one is on the bottom, same as the chat messages.

Yeah, I think this is intentional by design to mirror chat messages. I'm going to close it out 👍

This list should not be compare with chat message (Because chat message shows latest message at the bottom with inverted list. so it always shows latest message at bottom of the chat that, that is expected behaviour).
But here listing is going top to bottom (old record shows at top and new records show at top) So whenever list become long it happen that new record goes down too far at bottom. So user has to scroll down to bottom of list to see new record.
As this list start from top to bottom so it shows old record at top all time. This is not useful for user. Actually new record should be at top in this list. So user can see new payment request record at top etc.
cc @trjExpensify   @iwiznia

More details/context
https://expensify.slack.com/archives/C01GTK53T8Q/p1642010548393400?thread_ts=1641584385.136300&cid=C01GTK53T8Q
Our focus and goal is for real-time payments to be the norm so we don't expect there to be batches where two users would have many transactions showing before they're zeroed out.  Let's leave it as-is for now.


trying arm osx

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)x
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

@conda-forge-admin, please rerender

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.


Activity doesn’t show ETH related information

In a Tx, I swap USDT for ETH, and received some CoFi token. Sent USDT and received CoFi are displayed, but received ETH is not displayed.
![Uploading 97126347...]

The image didn't uploaded correctly, but I think you this is a dup of https://github.com/AlphaWallet/alpha-wallet-ios/issues/2179 ? It needs to be solved here: https://github.com/AlphaWallet/TokenScript/issues/392


Expected type string but found type integer

Using yamlbeans-1.09.jar to convert my Java objects into yml. For the specific case of creating tag swagger: 2.0, I enter it as a string in my Map in Java like the other objects, all the other objects are rendered without any problem except for this tag wherein it gives the following two errors:
-Expected type string but found type integer
-No enum match for: 2
All the other variables are picked up fine except for the version where it identifies the String as integer and I have no clue why. While validating the yml using www.yamllint.com, it turns out to be valid but does not work here. Any help or leads will be appreciated.

We went over this in SO. This is an issue with yamlbeans that it doesn't respect the original type of the object. You put a string, it converts it to a number. You need to open an issue on the yamlbeans project so that they fix it.


Meson: don't set CC and CXX

These are set by the stdenv. Maybe fixes #58831.

Motivation for this change
Things done

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

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

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

I'm all for this, assuming it doesn't break cross-compilation, so we (someone) should test that.

I'm curious: why did you close this?

I'm curious: why did you close this?

Talking to @ericson2314, it turns out meson treats CC and CXX as the build cc and build cxx. So it looks like that is legitimate to set it like this.

And hopefully meson fixes their behavior to match autoconf soon :)


[FIX] Avoid chdir_to_trial_dir causing silent DeprecationWarning Error

Issue #, if available:
Fixes #4075
Description of changes:
Use the environment variable RAY_CHDIR_TO_TRIAL_DIR instead of the argument chdir_to_trial_dir.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Previous CI Run
Current CI Run

should it also be added to timeseries hpo_executor.execute just in case?


Fresh Install on Sierra requires sudo when using cask install?

I can't install anything unless I use sudo. Was this introduced in Sierra? I also have this issue on my older machine that just upgraded to Sierra. I apologize if this is an existing bug.
PS: The string that was specified I should run to fix the issue... did not fix it.
iMac:~ roederw$ brew cask install iterm2
==> Satisfying dependencies
complete
==> Downloading https://iterm2.com/downloads/stable/iTerm2-3_0_10.zip
Already downloaded: /Users/roederw/Library/Caches/Homebrew/Cask/iterm2--3.0.10.zip
==> Verifying checksum for Cask iterm2
==> Moving App 'iTerm.app' to '/Applications/iTerm.app'
Error: Permission denied - (/usr/local/Caskroom/iterm2/3.0.10/iTerm.app, /Applications/iTerm.app)Most likely, this means you have an outdated version of Homebrew-Cask. Please run:
brew uninstall --force brew-cask; brew untap phinze/cask; brew untap caskroom/cask; brew update; brew cleanup; brew cask cleanup
If this doesn’t fix the problem, please report this bug:
https://github.com/caskroom/homebrew-cask#reporting-bugs
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/fileutils.rb:519:in rename' /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/fileutils.rb:519:in block in mv'
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/fileutils.rb:1558:in block in fu_each_src_dest' /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/fileutils.rb:1574:in fu_each_src_dest0'
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/fileutils.rb:1556:in fu_each_src_dest' /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/fileutils.rb:508:in mv'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/artifact/moved.rb:39:in move' /usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/artifact/moved.rb:15:in block in install_phase'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/artifact/moved.rb:32:in block in each_artifact' /usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/artifact/moved.rb:31:in each'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/artifact/moved.rb:31:in each_artifact' /usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/artifact/moved.rb:11:in install_phase'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/installer.rb:135:in block in install_artifacts' /usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/installer.rb:132:in each'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/installer.rb:132:in install_artifacts' /usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/installer.rb:75:in install'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cli/install.rb:25:in block in install_casks' /usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cli/install.rb:19:in each'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cli/install.rb:19:in install_casks' /usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cli/install.rb:10:in run'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cli.rb:107:in run_command' /usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cli.rb:146:in process'
/usr/local/Homebrew/Library/Homebrew/cask/cmd/brew-cask.rb:8:in <top (required)>' /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in require'
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in require' /usr/local/Homebrew/Library/Homebrew/brew.rb:23:in require?'
/usr/local/Homebrew/Library/Homebrew/brew.rb:102:in `'

You must always follow the reporting bugs guide. When you opened this issue, the template in place urged you to do so and gave you the relevant links.
The template also stated clearly that

if it is apparent you ignored the instructions for reporting issues, your issue may be closed without review.

That seems very much to be the case, here, which is why this was closed.
Again, as the template states (emphasis added)

When the guide isn‘t followed we get the same issues over and over. Having to repeatedly deal with the same solved and documented problems leads to maintainer burnout and a lot of wasted hours that could instead have been spent improving Homebrew-Cask itself and fixing real bugs.

I’ll add it is exhausting, and when maintainers are exhausted, everyone loses.
A lot of work was put into those guides precisely so we can keep things running smoothly.
I ask that you respect our time and efforts and follow the guides.


subsurface: make build src name independent

Motivation for this change
cherry picked from #153386
(cherry picked from commit 133158ffdea12c9927909b851463541c91411557)
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] 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/)
22.05 Release Notes (or backporting 21.11 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
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 157563 run on aarch64-darwin 1


S3 bucket download to linux issue

Hi,
I've been using the docker image (interline/planetutils:release-v0.4.11) for a while to download tif files(elevation tile download) into Ubuntu 20.04 server.
Whenever i download the files from S3 using the docker image interline/planetutils:release-v0.4.11, i keep on getting empty files.
Kindly can anyone help me with this issue. I have shared the details below.
Docker command :- docker run --rm -v ${PWD}/data:/data -t interline/planetutils:release-v0.4.11 elevation_tile_download --outpath=data/elevation --bbox=68.1766451354,7.96553477623,97.4025614766,35.4940095078 --zoom=12

https://s3.amazonaws.com/elevation-tiles-prod/geotiff/12/2823/1615.tif

But this is command is being performed by the docker image. How can i change that?

We didn't create that docker image. Try looking for the code contained in it.

@iandees But there's no option in the code where we can change the S3 url from http to https.
This is the image :- interline/planetutils:release-v0.4.11

Have you contacted the authors of that image?

I recommend filing a pull request with the authors of the image. You can find the code here: https://github.com/interline-io/planetutils/blob/master/planetutils/elevation_tile_downloader.py#L53

I recommend filing a pull request with the authors of the image. You can find the code here: https://github.com/interline-io/planetutils/blob/master/planetutils/elevation_tile_downloader.py#L53

I have already requested for a pull request, but as there was no response i thought of enquiring about it over here.


1.19 pixelRectForScreenRange regression

Description
TextEditorElement's pixelRectForScreenRange is returning incorrect values.
Steps to Reproduce

Perform a selection that spans 2 or more lines like in the below screenshot:

Run the below code snippet which uses pixelRectForScreenRange:

var editor = atom.workspace.getActiveTextEditor();
var screenRange= editor.getSelections()[0].getScreenRange();
atom.views.getView(editor).pixelRectForScreenRange(screenRange);

Expected behavior: I would expect the left value to be 0 and the width value to be meaningful. In Atom v1.18, they are correct.
Actual behavior: In Atom v1.19, left is not 0 and width is a negative number.
Versions
Works in v1.18 - broken in v1.19. All OS.

@mupchrch pixelRectForScreenRange appears to be a private method and is not part of the public Atom API.  You may want to use public APIs instead, or create a new issue requesting that pixelRectForScreenRange be added to the public API if the existing API methods are insufficient for your use case.


Fix slider behaviour for bigger thumbs

What does the pull request do?
This PR improves / fixes the behaviour of the slider control, which behaves stranger the bigger the thumb becomes. Dragging the thumb, it now moves synchronusly with the pointer all the time.
What is the current behavior?
Dragging the thumb, it always jumps to the right side of ther mouse pointer, while dragging to the maximum value, the thumb slowly moves to the left side of the pointer. This feels strange and not intuitive.
What is the updated/expected behavior with this PR?
Add a slider and drag the thumb. No more jumping to one side of the pointer will occure.
Fixed issues
Fixes #7011

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


error during  installation

.....
.......
apt-get install -qq -y lxc-docker
sleep 2 # give docker a moment i guess
Start building buildstep
gzip: stdin: unexpected end of file
FATA[0416] Error: Untar exit status 1 unexpected EOF
make: *** [stack] Error 1
lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 14.04.2 LTS
Release:	14.04
Codename:	trusty
tar --version
tar (GNU tar) 1.27.1

Transient or networking issue? Have you tried again?

there must not be network problems. yes, several times

@partus can you try the instructions here for installation?

@josegonzalez without root privileges there was permission error to access /etc/apt/sources.list.d/docker.list
with root privileges  it went without errors , thank you.

Gotcha, so now everything works?

yes

Cool, closing. Our knew installation method will be via debian packages, so we can get around the need for a makefile installation that may fail. Thanks for checking!

I'm aware this is closed and the approach is different, but I've run into the same error trying to install Dokku with Vagrant.
Shall I create a separate issue?

Sure, please open a new issue and document exactly what you're doing.


You may want to add SAMPro3D

Hi,
Thanks for your great repo!
Could you please add our SAMPro3D into the 3D category?
It lifts SAM to 3D indoor scene segmentation, and does not require any training, tuning, or distillation. It achieves superior segmentation results.
Thanks a lot!

@mutianxu Hi, Thanks for your excellent work. You can initiate a merge request, and I will add your work. Thank you!

@mutianxu Hi, Thanks for your excellent work. You can initiate a merge request, and I will add your work. Thank you!

Hi @Hedlen , I have sent a pull request.
Thanks for your help!


Shift clang-tidy to github action

Currently clang-tidy is not working very well and need some attention
I am gradually picking off various bits of ci for shifting azp -> gh
This one seems like quite a good candidate to start on the checks with.

cc @wbpcode @yanavlasov

clang-tidy is currently disabled pending resolution here

can we prioritize this? I genuinely think this is really bad for the long term as it directly affects the code quality plus security risk

its half complete - atm you can run:
./ci/do_ci.sh clang-tidy

and it kinda works
the reason i didnt land in ci is that it is not 100% - i took someone elses (aspect-based) clang-tidy implementation and hacked a few things to make it work to my expectations
i havent had too much time to do it recently - but in the past i ran it and fixed any issues - probably that would be a good place to start - the tool could do with some non-me testing and feedback

so yeah one thing I noticed is
xternal/com_google_absl/absl/log/absl_check.h:47:3: note: expanded from macro 'ABSL_DCHECK'
  ABSL_LOG_INTERNAL_DCHECK_IMPL((condition), #condition)
  ^
external/com_google_absl/absl/log/internal/check_impl.h:40:3: note: expanded from macro 'ABSL_LOG_INTERNAL_DCHECK_IMPL'
  ABSL_LOG_INTERNAL_CHECK_IMPL(condition, condition_text)
  ^
external/com_google_absl/absl/log/internal/check_impl.h:26:3: note: expanded from macro 'ABSL_LOG_INTERNAL_CHECK_IMPL'
  ABSL_LOG_INTERNAL_CONDITION_FATAL(STATELESS,                        \
  ^
external/com_google_absl/absl/log/internal/conditions.h:123:3: note: expanded from macro 'ABSL_LOG_INTERNAL_CONDITION_FATAL'
  ABSL_LOG_INTERNAL_##type##_CONDITION(                                    \

can we exclude external?

good q - i never really got to the bottom of this
i think it does exclude it to the extent that it doesnt throw errors - at least using the do_ci.sh way - but i have always been convinced that its checking a lot more than it should

meanwhile I will fix the errors and warning emitted currently little by little

also noticed that ./ci/do_ci.sh clang_tidy always exists with status=0 regardless of the detected errors

Also noticed that clang-tidy runs multiple times each time included == if a file #included multiple places, the checks run multiple times. Can we simply run find . -name *.cc -name -name *.h instead of actually building for now? That would run instantly i think.

I found the root cause of why it's running multiple times on the same file:
INFO: From Run clang-tidy on source/common/common/callback_impl.cc:
error: redefining builtin macro [clang-diagnostic-builtin-macro-redefined,-warnings-as-errors]
INFO: From Run clang-tidy on source/common/common/regex.cc:
error: redefining builtin macro [clang-diagnostic-builtin-macro-redefined,-warnings-as-errors]

the newly introduced toolshed clang-tidy runs clang-tidy on each file but our .clang-tidy.yaml tells it to emit warning for all envoy repo headers. We definitely should invoke clang-tidy once, not on each file...

basically using aspect (i assume that runs on each build target) for clang-tidy seems not the right way

no!!! really lets not - that way was awful and the general advice is to shift to aspects for this kind of job
what is the issue you are having? bazel certainly adds some overhead but it has its uses also

ok, the issue is it's running clang-tidy on each header/source files hence whenever #include source_header is located, clang-tidy tries to analyze them. Basically doing the duplicates jobs

hmm, sounds like a job for remote persistent workers perhaps
i think this is the issue that i was saying about it running more than it should tbh - not sure - it was a while ago  i worked on it
iiuc it does need to do this analysis even if its not testing those files?

if you pass all files all at once to clang, then clang analyze once no matter how many times they are included elsewhere vs using aspect this runs on each time, so the context is missing. But anyways nvm not that important for now.
I think asap we should do is to bring this to CI - could you clarify what's the missing steps to close issue?

so the thing is this is much more serious than we think - so many uncaught errors and it's increasing day by day. linter is fundamentally important CI job for any software nowadays, and I can't imagine how are we ok with this for such long time not enabling this

what's the missing steps to close issue?

someone other than me testing it - im not c++ - i can get up to speed on some things - but dont have immediate uses for the tooling personally
also - was concerned about performance of it - which i think is the what you are pointing out
how about we start off with running it on a schedule - we can get a measure of what its doing - and keep on top of any required fxes
re rerunning the same analysis - surely bazel copes with this - even if its (annoyingly) printing out the output from when it was actually built, i would hope/expect that bazel is using its cached artefacts (assuming the inputs for the file were the same)
its not super fast and the output needs work - but i think it was kinda functional - lets start using it

https://github.com/envoyproxy/envoy/pull/37378 can we merge this for now? this basically blocks everything

surely bazel copes with this

checked code - and it doesnt - its running with those files over and again
lets land it on a schedule - ill try and think of a better scheme - need to look at how the tool itself works

fyi one thing the current toolshed / aspect based clang-tidy is to ignore certain target - notidy is specified in .bazelrc's clang-tidy config but it is not respected by the tool

currently
INFO: From Run clang-tidy on contrib/kafka/filters/network/source/mesh/librdkafka_utils_impl.cc:
error: redefining builtin macro [clang-diagnostic-builtin-macro-redefined,-warnings-as-errors]
INFO: From Run clang-tidy on source/extensions/filters/http/file_system_buffer/config.cc:
error: redefining builtin macro [clang-diagnostic-builtin-macro-redefined,-warnings-as-errors]

this errors is produced for every single one of source file which sounds really weird

yeah - i didnt figure that issue out

as for the spurious builtin macro error ... maybe I got an idea of the root cause

vscode@mathetake-Venus-series:/workspaces/envoy$ clang-tidy empty.hpp -extra-arg=-std=c++17
vscode@mathetake-Venus-series:/workspaces/envoy$ clang-tidy empty.hpp -extra-arg=-std=c++20
3 warnings generated.
error: redefining builtin macro [clang-diagnostic-builtin-macro-redefined,-warnings-as-errors]
1 warning treated as error
vscode@mathetake-Venus-series:/workspaces/envoy$ cat empty.hpp

created empty header file and manually run clang-tidy (with the compilation_commands.json) and the error disappears with c++17 but comes in c++20. So i think the problem is something to do with our -config=clang build settings regarding the standard library.
https://github.com/llvm/llvm-project/blob/d681e1030ffd71412294d3fadc7ef673f822b832/clang/lib/Lex/PPDirectives.cpp#L3234-L3237
This is the exact line where the error emitted - I suspect that some system headers somehow avoided being recognized as a system header

https://github.com/envoyproxy/envoy/pull/37408 finally found the fix!

maybe we want to revive the ignored targets here
https://github.com/envoyproxy/envoy/blob/22e7328305b8fc682644e1bfbbc33f93b856993d/ci/run_clang_tidy.sh#L40-L94

@phlax do you have any update

no - ive been busy with other things


display properly README at markdown format on pypi

Since few months pypi.org can deal properly with README at markdown format.
This pull requests specify to pypi to use markdown format.

Can someone review?


[FEAT]: Added issue buttons

This PR fixes the issue:
#2
Proposed changes:
New issue buttons are added to help the contributors.

edit the about section of every button to the text mentioned in the image, also add the respective emojis !

@vk-44 Great going just add the respective emojis and jobs done !


Accordion z-index high

I am experiencing an issue where the very high z-index of the accordion is coming through to elements which are rendered on top of them. For instance, a modal.
I was hoping someone could explain why the z-index was so high.
	&:focus { 		z-index: 100; 	}

It's probably inspired by having a z-index scale. Ie https://material-ui.com/customization/z-index/. By setting the z-index of the Modal component so high, you know that you'll definitely cover all the stuff with z-indexes under that whilst allowing you to have z-indexes of 100+ for stuff you want on top of the Modal. If it wasn't so high, then it'll be easy to forget what the z-index of the Modal was and have things accidentally appear above it.

It's probably inspired by having a z-index scale. Ie https://material-ui.com/customization/z-index/. By setting the z-index of the Modal component so high, you know that you'll definitely cover all the stuff with z-indexes under that whilst allowing you to have z-indexes of 100+ for stuff you want on top of the Modal. If it wasn't so high, then it'll be easy to forget what the z-index of the Modal was and have things accidentally appear above it.


odo dev consumes a lot of cpu if cluster is stopped

/kind bug
What versions of software are you using?
Operating System:
Win10Pro
Output of odo version:
odo v3.0.0-beta3 (f4e96a4e3)
How did you run odo exactly?

odo dev
stop cluster (crc stop)

Saw the odo process consuming about 10% of CPU on my 8 pro system
Actual behavior
Expected behavior
Any logs, error output, etc?

/triage needs-information
We need to replicate this from our end.

I've tried to reproduce this but no luck.
If this is still an issue feel free to reopen this.
/close


There appears to not be a license here, it would probably be a good idea to apply one so it's FOSS.

Please and thank you.

Done.
https://github.com/MohammedAlamkhan/AngularWindowBridge/commit/61e17d597f7abbf78042297a464b23cfd79edd64


🎮 Game Request
Game logic and basic description
Contra
Overview
Contra is a classic side-scrolling action game developed and published by Konami in 1987. It is known for its challenging gameplay, intense action, and iconic run-and-gun mechanics.
Gameplay
In Contra, players take on the role of either Bill Rizer or Lance Bean, highly skilled commandos tasked with infiltrating and defeating an alien invasion force known as the Red Falcon Organization. The game features fast-paced, run-and-gun gameplay where players must navigate through a series of side-scrolling levels, eliminating enemies and obstacles while avoiding hazards and powerful bosses.
The game's signature feature is the ability to execute a "Spread Shot", a devastating weapon that fires multiple projectiles in a wide arc, allowing players to mow down hordes of enemies with ease. Players can also collect various power-ups and weapon upgrades throughout the game to enhance their firepower and survivability.
Legacy
Contra is considered a landmark in the run-and-gun genre and has had a lasting impact on video game history. It has spawned numerous sequels and spin-offs, and its influence can be seen in many modern action-packed games. The game's iconic status and challenging gameplay have made it a beloved classic for generations of gamers.
Point down the features
Game points
Key Features

Intense Action: Contra is renowned for its lightning-fast and relentless action, with waves of enemies, challenging boss battles, and intricate level designs that test the player's reflexes and skill.

Iconic Weapons: The "Spread Shot" is the game's most iconic weapon, allowing players to unleash a barrage of bullets and clear the screen of foes.

Co-op Gameplay: Contra supports two-player co-op, allowing players to team up and tackle the alien threat together.

Challenging Difficulty: Contra is known for its high level of difficulty, requiring players to master the game's mechanics and patterns to progress through the levels.

Memorable Soundtrack: The game's driving, synth-heavy soundtrack, composed by Hidenori Maezawa and Takashi Yoshioka, is a cherished part of Contra's legacy.

Select program in which you are contributing
GSSoC24
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

Hey @VesperAkshay !
Thank you for raising an issue 💗
You can self assign the issue by commenting /assign in comment 😀
Make sure you follow CODE OF CONDUCT and CONTRIBUTING GUIDELINES 🚀
Don’t Forget to ⭐ our GameZone🎮
Make sure you join our Discord🕹

/assign

Hey @VesperAkshay ! Thank you so much for your raising the issue💗
It’s all yours, you can come anytime again and make some contributions! 🚀
Alone, we can do little, but together we can do so much! 😇


hostname_ipaddress_required? false for HostMicrosoft, HostOpenstackInfra, HostRedhat

I saw this while renaming hostname_ipaddress_required? to hostname_required? in #2136
All non vmware Hosts don't require a hostname/ipaddress?  This seems like a bug.
  def hostname_ipaddress_required?
    self.vmm_vendor == "vmware"
  end

https://github.com/ManageIQ/manageiq/blob/e4bd478f86d8cac7f675fc3c3ac2df39e6477e2e/vmdb/app/models/host.rb#L187-189
I would like to move this knowledge to the class level but it's looking at an instance's vmm_vendor column.  Is this right?
cc @Fryguy @blomquisg

cc @gmcculloug

@gmcculloug and I agreed that the base host class should default to hostname_ipaddress_required? => true and therefore hostname_required? => true on the rename.  Any subclasses needing to set false can choose to do.


Neovim config big changes

TBA

That was an experiment that brought us a few interesting ideas. The actual change will be done in frames of another PR


fix: Resolve #3. Reduce STLoR codebase to the minimum dependencies and code needed to reproduce the public dataset.

Buckle in, this is a chunky one. However, this description should make what we're doing clearer at high level.
Data Directory Restructuring
A large portion of this diff is connected to repository restructuring. Specifically, files previously located at data/stl_dataset/step_2/input/stl_activity_layers are now located at data/stl_activity_layers. I wanted to remove any reference to our "step" architecture from the land-grab-2 repo.
Core Code
All core code lives in the stlor directory, which has the following directory structure:

__init__.py → Necessary to direct Python to treat the stlor directory as a package.
activity.py → Contains all functions related to capturing activity and activity_info information.
compare.py → Our script for semantically comparing CSVs. This accounts for inconsistent row and column ordering between CSVs, in addition to variable ordering of substrings in the activity and activity_info columns. This will ideally be what we run in CI to alert us when a code change results in an update to the dataset.
config.py → All configuration for the activity matching process. This is primarily composed of dictionaries mapping state codes to StateActivityDataSources, state codes to activity codes, state codes to activity rewrite rules, and activity strings to rights types.
constants.py → What it says on the tin!
entities.py → Our small handful of classes, including StateActivityDataSource, StateForActivity, and the RightsType enum.
main.py → The primary functions for running our activity matching process.
overlap.py → All functions for our R-tree spatial index construction and probing, along with spatial predicates for determining relationships between STL parcels and state activity layers.
utils.py → The dreaded (but necessary) utils file, primarily housing functions for parallelism with dask.

Yayyyy amazing. Looking forward to reviewing. [2d10f3a](https://github.com/Grist-Data-Desk/STLoR/pull/8/commits/2d10f3ab5d31383c74584ba6f014cdd29dbdfed3) is looking hefty already. :)


Audio only comes out of right speaker.

This may be related to issue #8, but if you use headphones you can tell audio only works on one ear.

This is definitely an issue that I'm experiencing as well. Doesn't seem to relate to the source being mono or stereo. Or even the source format. This needs more research. Maybe an issue with the position of the audio.

This should be fixed as of 16288c2.

Did you update the demos? Because they still have this problem.

I didn't update the demos.


vcs: fix router random 404 errors on start

VCS manage now passes a prefixed /webhook router to RepositoryService implementations.
Fixes #29

Coverage increased (+9.02%) to 45.911% when pulling f9c6c2440a98b845150c3071ac2fff80f7a9f50a on router-404-29 into 409fe2ce8f611753c26f797c16596303cc9d641a on master.


How to get httprequest in TemplateDirectiveModel

my code :
public class ComboTag implements TemplateDirectiveModel{
	@Override
	public void execute(Environment env, Map params, TemplateModel[] loopVars, TemplateDirectiveBody body) throws TemplateException, IOException {
//I want to  get the httprequest  here.
		Writer out = env.getOut();
    }

I guess it's a question, not a pull request. FreeMarker is not bound to Servlets, so exposing such objects and how that's done is up to the embedding framework. For example, you could attach the HttpRequest to the Environment with setCustomAttribute before starting the template processing, then get it with getCustomAttribute.


Dispatch success or failure only for the last navigateAction

If more navigateActions are called in sequence, the first actions should never dispatch failure or success since they get "invalidated" by the last action, which started a new navigation.
The change in this PR makes navigateAction to check the URL of the route that the store is expecting to handle: if the action's callback refers to a different url, it does not dispatch NAVIGATION_SUCCESS or NAVIGATION_FAILURE.
See this video showing the problem this PR should solve: when the user clicks multiple times on the navigation bar, the URL may go out of sync with what is actually displayed on the page. The last clicked is the link to "components.html" but the page actually shown is the API for Fluxible. This is particularly visible on slow or irregular connections. I've seen this issue also in https://github.com/gpbl/isomorphic500/issues/44.

One idea I would like to explore in solving this is using a transaction ID that is dispatched with the route that would allow us to keep track of which NAVIGATE_START a NAVIGATE_SUCCESS is associated with.
In the latest version of Fluxible we introduced a context.rootId that is a generated identifier for a root level executeAction. If this was passed with the payload to the above events, the RouteStore keep track of the ID  and could ignore any NAVIGATE_SUCCESS this is not associated with the latest NAVIGATE_START.
I find this preferable than short-circuiting in the action because there may be a preference by the developer to handle these events in some other manner.

CLA is valid!

I agree! However, the payload for the success action is a route, and for the failure, an error object: how should we pass the rootId to their payload?

Yeah, that's the unfortunate part. It may have to be a breaking change.
One thing that we could do in the mean time that gives similar behavior is change this PR to check the latest START url to the SUCCESS url. If SUCCESS doesn't match the latest START then it gets ignored (return here: https://github.com/yahoo/fluxible-router/blob/master/lib/RouteStore.js#L48).

However I understand now why checking the url doesn't work very well: if the navigation sequence is routeA → routeB → routeA, we would still dispatch two success for routeA, since they have the same url. Or, worse, if one of the actions returns an error, we may dispatch a failure and a success.

Now i remember why I put the logic in navigateAction and not in the RouteStore: while in _handleNavigateSuccess i can check the route's url, since it comes as payload, I can't do that in _handleNavigateFailure, where i have only the error.
The transaction id seems the way to go, now I'm afraid to uglify the nice API we had so far:
I'd dispatch actions as:
context.dispatch('NAVIGATE_START', {
     navigationId: context.rootId,
     payload: payload // naming feels bad here
});
context.dispatch('NAVIGATE_SUCCESS', {
     navigationId: context.rootId,
     route: route
});
context.dispatch('NAVIGATE_FAILURE', {
     navigationId: context.rootId,
     error: error
});

I think we could get away with adding transactionId to the existing payloads:
context.dispatch('NAVIGATE_START', Object.assign({ transactionId: context.rootId }, payload));

context.dispatch('NAVIGATE_SUCCESS', route.set('transactionId', context.rootId));

error.transactionId = context.rootId;
context.dispatch('NAVIGATE_FAILURE', error);

It's a little hacky, but preserves backwards compatibility for now.

Marking this as a breaking change just to keep track of potential changes that we want to make like adding more data to the payload as you mentioned.

I've applied your suggestions to my PR. To reduce the impact of the change, we can reuse the existing  transactionId already passed to the payload.
PS. I'd test this change where both navigateAction and RouteStore play together, so ideally in  the NavLink test, but I think https://github.com/yahoo/fluxible/issues/296 must be closed first.

I created https://github.com/yahoo/fluxible-router/pull/103 to add transactionId (based on branch that removes immutable). @gpbl want to take a look?

@mridgway looking great 😍 Thanks a lot!


Remove unused imports

Description

Remove unused imports
Code cleaning using IDE's code inspection tool

Thanks @doljae I've merged the PR.


Using a controller to manage the edit panel

Hi,
I'm really not an expert in AngularJS, but from what I understood of the code, the edit panel is managed by a controller included in the adf module so that config is directly available. Is it possible somehow to add custom behaviour in this controller?
For instance, assume I have a select field and a text field in my edit panel, and I want the select field to have "Other" selected as soon as the user types some text in the field.
I of course know how to do that in a standard controller, but I'm unsure of how such a custom controller should merge with the one included in the adf module (if that is even possible).

You can specify a controller for the edit dialog during the registration e.g.:
angular.module('mywidget', ['adf.provider'])
  .config(function(dashboardProvider){
    dashboardProvider
      .widget('mywidget', {
        title: 'My Widget',
        description: 'My awesome widget',
        templateUrl: 'mywidget/src/view.html',
        edit: {
          templateUrl: 'mywidget/src/edit.html',
          reload: false,
          controller: 'MyEditController'
        }
      });
  }).controller('MyEditController', function($scope, config){
    // do something
  });

Please have a look at the linklist widget for a real world example.

Perfect, thanks. I had missed that.


[epic] HowTos

Have a bunch of howtos on the website and a process for adding new ones.
Acceptance

[ ] 3+ howtos on the site
[x] Backlog of howtos to create
[ ] Simple way to add howtos to site that is documented in e.g. contributing

Tasks

[x] Brainstorm backlog of howtos DONE https://docs.google.com/spreadsheets/d/1qByu4qw56hFUdJIY5IOC7d8TQBud-k31J6720hg1h2w/edit#gid=1272791416

[x] Template for howtos and process for creating (e.g. is it a jupyter notebook)
[x] Write 2-3 howtos #453
[ ] Put these on the website
[ ] Write more ...
[ ] ...

May 18 update:

5 how-to's written
https://docs.google.com/spreadsheets/d/1qByu4qw56hFUdJIY5IOC7d8TQBud-k31J6720hg1h2w/edit#gid=1272791416
To Do:
Evgeny will work on putting them on the site
Evgeny & Lilly can write up the process for getting them on the site for other contributors
Lilly to write elastic search & amazon redshift how tos

We can merge this issue with a high-level https://github.com/frictionlessdata/project/issues/542 as we're going to add a lot of documents like "Working with SQL in Frictionless" etc

@lwinfree @roll do you think we can close this in favour of e.g. #542 and work on frictionless python lib (perhaps with a bit of detail of what has been done)?

yes!


CODE CHANGE: Enhance Book Now hovering effect

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the code change
The hovering effect on book now button doesnt match with the theme of website.
Proposed solution
I would add a different hovering effect on the button.
Before
https://github.com/user-attachments/assets/173359e8-89c6-4182-8618-71502fbba447
After
https://github.com/user-attachments/assets/aa82f66f-78d5-4eb8-8e5b-97c23e137495
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

@PriyaGhosal The button colour has been changed again i've fixed that.


Snapshot for shared-data

Shared-data currently does not support backup and restore functionality. While S3 provides high availability and data persistence, backup and restore capabilities are still essential for recovering from unexpected incidents or periodical snapshot. This proposal introduces the concept of snapshots to address this need.
There are two main scenarios for using snapshots:

Data Backup and Recovery: Snapshots can be used to back up data at specific points in time and restore from those snapshots as needed. This process can be performed manually or scheduled periodically.

Automated Backup and Recovery: The system can automatically create snapshots of the latest data, enabling recovery from the most recent snapshot with best-effort reliability.    https://github.com/StarRocks/starrocks/issues/53867

Product proposal docs
https://docs.google.com/document/d/1rPG_evLRK-XG5W1p0sNk0xibEOrdMllrxMV__mCwmJs/edit?tab=t.0#heading=h.iofn2gmg8h2y

Detailed design doc:  https://docs.google.com/document/d/1gIM1yHOpLIlwJEDkH4jfEcfukdW7B1hX7QZOap3045s/edit?tab=t.0#heading=h.1fjlx8nqi5nv


Add cwAlarm descriptions & more actions

When using the alarms for notifications it definitely helps to have a
brief regular language description to get an idea of what's happening.
Additionally, we want to receive notifications for when alarms clear as
well as when they alarm or insufficient data is available.
Finally, given we can set the cadence of the snapshots, we need the
alarms to ignore missing data points to avoid false alarms.

Hi @jinnko, just left a comment for something very minor. Could I ask you to remove your zip files? I would rather repack myself, I do that every time I upload to the default buckets anyway. Thanks!


Use SFTP to transfer csv file and read it

We can connect to Raspberry pi and transfer files. Maybe search for a way to hide the password maybe give it in the UI?


creating a s2s.yaml file

Following the instructions we have been able to obtain all the parameters that must be included in de s2s.yaml file except one. However we do not know where and how to obtain the train.h5 file. Could anybody help us?
Thanks

My guess is the train.h5 file is your original states.h5 that gets generated from the extract_context.py while preparing your data.


feat: filtered categories are connected

[x] depends on: #10713
[x] depends on: #10716

Thanks!
bors merge


More matplotlib

Attempt to get comments from @anissa111 #167 merged into foundations.

I wouldn't be surprised if the link to additional-topics2 was broken, since that is in #230

Requesting review from all reviewers of #167


Add code to prepare.yml to install init on Debian images

Add code to prepare.yml to install init on Debian images.  This is a workaround for the fact that testinfra currently misidentifies the init system on these hosts.  See philpep/testinfra#416 for more details.
I also took the opportunity to pull in upstream changes.

The fact that the (unneeded and unwanted) JavaScript LGTM analysis fails is a red herring. Please disregard.


Pull/130

fixup #130

This change is

I'm a bit opposed to setting a setter/getter without strictly keeping the filed (reconnect -> setNoreconnect/isNoReconnect).
On the other side, allowing to define the maximumRetryCount value is a big win.
Overall, seems good. Want me to close #130 ?

error parsing... will fix and rebase

Codecov Report

Merging #186 into master will increase coverage by 0.61%.
The diff coverage is 53.33%.

@@             Coverage Diff              @@
##             master     #186      +/-   ##
============================================
+ Coverage     20.66%   21.27%   +0.61%
- Complexity      208      217       +9
============================================
  Files            56       58       +2
  Lines          2352     2397      +45
  Branches        208      209       +1
============================================
+ Hits            486      510      +24
- Misses         1811     1831      +20
- Partials         55       56       +1

Impacted Files
Coverage Δ
Complexity Δ

...yad/launcher/DockerComputerSingleJNLPLauncher.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

.../yad/commons/DockerContainerRestartPolicyName.java
100% <100%> (ø)
1 <1> (?)

...yasha/yad/launcher/DockerComputerJNLPLauncher.java
17.91% <28.57%> (+0.44%)
15 <1> (+1)
:arrow_up:

...asha/yad/commons/DockerContainerRestartPolicy.java
57.14% <57.14%> (ø)
5 <5> (?)

...b/kostyasha/yad/commons/DockerCreateContainer.java
48.66% <71.42%> (+0.73%)
57 <3> (+2)
:arrow_up:

Continue to review full report at Codecov.

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


Convert the idea behind Thread pool to Fibers/spawn

I'm having some hard time learning the idea behind Fibers\coroutines and the implementation in Crystal.
I hope this is the right place to ask this, I'll totally accept a "not here" answer :)
This is my usual way of handling multi-threading in Ruby:
threads = []
max_threads = 10

loop do
  begin
    threads << Thread.new do
      helper_method(1,2,3,4)
    end
  rescue Exception => e
    puts "Error Starting thread"
  end

  begin
    threads = threads.select { |t| t.alive? ? true : (t.join; false) }
    while threads.size >= max_threads
      puts 'Got Maximum threads'
      sleep 1
      threads = threads.select { |t| t.alive? ? true : (t.join; false) }
    end
  rescue Exception => e
    puts e
  end
end

This way I open a new Thread, usually of a incoming connection or some other thing, add the Thread to a threads array, and then check that I don't have more threads then what I wanted.
What would be a good way to implement something similar in Crystal  using spawn\channels\fibers etc.. ?

You'll may want to start populating the #crystal-lang tag on stackoverflow.
The example in #802 is a good start. It explains how to spawn coroutines and have some communication throught channels. That being said, in order to keep a pool, you can't just duplicate the way it works for threads: spawn doesn't return a coroutine object, and there ain't no way to join coroutines.
That being said, this should work (maybe, I wrote this out of my mind):
def worker(&block)
  result = UnbufferedChannel(Exception?).new

  ::spawn do
    begin
      yield
    rescue ex
      result.send(ex)
    else
      result.send(nil)
    end
  end

  result
end

def pool(size, &block)
  counter = 0
  results = [] of UnbufferedChannel(Exception?).new

  loop do
    counter += 1

    while counter < size
      results << worker { yield }
    end

    result = Channel.select(*results)
    if ex = result.receive
      puts "ERROR: #{ex.message}\n#{ex.backtrace.join("\n")}"
      counter -= 1
      results.delete(result)
    end
  end
end

pool(5) { helper_method(1, 2, 3, 4) }

This looks interesting, I'll open the same question on SO, it's nice to spread to use of it.

@bararchy Good! If the tag goes entirely unused for six months, it will be deleted!

Done --> http://stackoverflow.com/questions/30853566/crystal-convert-the-idea-behind-thread-pool-to-fibers-spawn


Convert string of css using V-bind

I have a string on some inline styles in a db column and before using vue I would just output that value into the style tag server side like so:
 $someStyles = "top:10px;left:150px;position:absolute;"; <button style="{!! $someStyles !!}"></button>
I'm trying to move this all over to Vue but at the moment I have to use php to play around with the string to break apart the properties and values to and array, to then json encode, and then parse so I can assign them to a js object and use v-bind. Is there a way to pass a string of css to to v-bind and have it break apart the string instead of an object?
I think it would be a nice feature if not already available?
Cheers

Please use forum to ask questions.
As I know it is not already available. But you can use custom directive to do it.

You can directly give v-bind:style a string.

@yyx990803 Wow didn't know about that.

@OEvgeny Sorry hadn't spotted the forum before, will go there in future.
@yyx990803 That's awesome, saves me a lot of headache manipulating strings!
Cheers Guys!


move getcommoncapabilities to separate file

Codecov Report

Merging #129 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff            @@
##           master    #129      +/-   ##
=========================================
+ Coverage    99.8%   99.8%   +<.01%
=========================================
  Files           6       7       +1
  Lines        1021    1023       +2
=========================================
+ Hits         1019    1021       +2
  Misses          2       2

Impacted Files
Coverage Δ

getcommoncapabilities.js
100% <100%> (ø)

rtcpeerconnection.js
99.74% <100%> (-0.02%)
:arrow_down:

Continue to review full report at Codecov.

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


Guidance for customization

First of all, thank you AWS and team for this template.  This is a game changer for our organization and will help with FinOps initiatives.
Just wanted to understand guidance around customizing the dashboard.  Adding new features, bug fixes etc especially the change management aspect.  Versioning and release management of these templates are critical for our customers' experience.
And of course, how can we contribute how learnings.
Thank you all!

Thanks for the feedback. You can find examples of the most common customizations in Well Architected lab and our Youtube channel.
When we release new version of the dashboard templates you can update your dashboards by following these steps. In this case your initial dashboard will be updated to new version, but customized ones will stay the same.
If you want to change your customized dashboards you'd need to change underlying analysis and publish new version of your dashboard. In the links above you can find more details how to do that.
Hope this helps.