Frontend?

Hello,
First off, as a long time Serverless Framework user, I love what has been done here!
So much so, I am planning on using this as a PoC at my job. I have 2 quick question before I do though:

Would I easily be able to integrate a React frontend into the repo? - I have looked over the Nx Documentation and believe it should be possible but I would like your opinion as you definitely  have more experience in Nx than myself.

If a frontend service is possible, would you be able to share types across both?

Thanks,
Connor

The applications directory is now services. You can add a new React application to it, and Yes, you can share types.

@NetanelBasal Thank you! I appreciate the response.


docs: running cockroachdb on kubernetes locally

This PR adds a new page explaining how to test out CockroachDB on Kubernetes using minikube and the alpha Pet Set feature. It's based on @tschottdorf's and @a-robinson's  CockroachDB example files in the Kubernetes repo.
This still needs quite a bit of work, but I want to get some initial feedback.
Fixes #506

This change is

HTML version: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/090f66b5dfe265cb8b811b30f686bea2d82ee390/orchestrate-cockroachdb-with-kubernetes.html

Didn't test yet, but  with a few really minor nits.

Review status: 0 of 2 files reviewed at latest revision, 3 unresolved discussions, some commit checks failed.

orchestrate-cockroachdb-with-kubernetes.md, line 231 [r1] (raw file):

~~~

{{site.data.alerts.callout_success}}The Pet Set configuration set all CockroachDB nodes to write to stderr, so if you ever need access to a pod/node's logs to troubleshoot, use kubectl logs PODNAME rather than checking the log on the pod itself.{{site.data.alerts.end}}

"set all CockroachDB nodes" -> "sets all CockroachDB nodes"

_data/sidebar_doc.yml, line 246 [r1] (raw file):

              thirdlevelitems:

                - title: With Kubernetes

Think simply "Kubernetes" would be a marginal improvement.

Comments from Reviewable

Review status: 0 of 2 files reviewed at latest revision, 3 unresolved discussions, some commit checks failed.

orchestrate-cockroachdb-with-kubernetes.md, line 7 [r1] (raw file):
Previously, tschottdorf (Tobias Schottdorf) wrote…
> Below as well.

Done.

orchestrate-cockroachdb-with-kubernetes.md, line 231 [r1] (raw file):
Previously, sploiselle (Sean Loiselle) wrote…
> "set all CockroachDB nodes" -> "sets all CockroachDB nodes"

Done.

_data/sidebar_doc.yml, line 246 [r1] (raw file):
Previously, sploiselle (Sean Loiselle) wrote…
> Think simply "Kubernetes" would be a marginal improvement.

Done.

Comments from Reviewable

This reads quite well to someone who has no kubernetes experience (me). I did not actually run it, but it is completely coherent, and there were links to Kubernetes for every concept that I had questions about.

Review status: 0 of 2 files reviewed at latest revision, 5 unresolved discussions.

orchestrate-cockroachdb-with-kubernetes.md, line 84 [r2] (raw file):

In Kubernetes, pods are normally treated as stateless units. The [Pet Set](http://kubernetes.io/docs/user-guide/petset/) feature, however, causes pods to have persistent identity and storage. Using this feature, if a pod crashes or is otherwise removed, Kubernetes will create another pod with the same identity and storage (as demonstrated in [step 6](#step-6-simulate-node-failure)).

Create the following Pet Set yaml file. Note that the `replicas: 5` line specifies that the CockroachDB cluster will contain five pods/nodes.

Maybe this is obvious to Kubernetes folks, but this was slightly unclear to me. I'm guessing this results in 5 pods with 1 node per pod, but it would be helpful if this was clarified.

orchestrate-cockroachdb-with-kubernetes.md, line 210 [r2] (raw file):

## Step 4. Start the CockroachDB cluster

To create pods and start the CockroachDB cluster, run the [`kubectl create`](http://kubernetes.io/docs/user-guide/kubectl/kubectl_create/) command against your Pet Set yaml file, in this case called `cockroachdb-petset.yaml`:

Can you also mention this filename above (as the header to the script itself)? It just makes things super easy when following along (if I was following along I would have already copied the bash script over and given it a random file name).

Comments from Reviewable

Looks great! Do you have anything in mind for how to squeeze in instructions for creating PVs when running in a cloud environment? Right now, the guide almost makes it sound like running locally is the only option

Review status: 0 of 2 files reviewed at latest revision, 14 unresolved discussions.

orchestrate-cockroachdb-with-kubernetes.md, line 40 [r2] (raw file):

  name: pv${i}
  labels:
    type: local

Add the label app: cockroachdb to make deleting the PVs easier. You must have copied this from an older version of my PR before I added it.

orchestrate-cockroachdb-with-kubernetes.md, line 67 [r2] (raw file):

~~~

Use the [`kubectl get pv`](http://kubernetes.io/docs/user-guide/kubectl/kubectl_get/) command to verify that persistent volumes and corresponding claims were created successfully:

s/that persistent volumes/that the persistent volumes/

orchestrate-cockroachdb-with-kubernetes.md, line 82 [r2] (raw file):

## Step 3. Create the Pet Set configuration

In Kubernetes, pods are normally treated as stateless units. The [Pet Set](http://kubernetes.io/docs/user-guide/petset/) feature, however, causes pods to have persistent identity and storage. Using this feature, if a pod crashes or is otherwise removed, Kubernetes will create another pod with the same identity and storage (as demonstrated in [step 6](#step-6-simulate-node-failure)).

Optional, but I might be just a little more specific and replace "same identity and storage" with "same network identity and storage"

orchestrate-cockroachdb-with-kubernetes.md, line 96 [r2] (raw file):

  name: cockroachdb-public
  labels:
    app: cockroachdb-public

Again, this isn't quite the most recent version of the file, since I switched this to just be app: cockroachdb for easier deletion. I'd recommend re-copying the entire thing

orchestrate-cockroachdb-with-kubernetes.md, line 277 [r2] (raw file):

Based on the `replicas: 5` line in the Pet Set configuration, Kubernetes ensure that five pods/nodes are running at all times. If a pod/node fails, Kubernetes will automatically create another pod/node with the same identity and storage.

To see this in action, kill one of the pods:

I might rephrase this to "kill one of the cockroachdb nodes", since the pod being restarted is more of an indirect consequence of killing the cockroachdb process

orchestrate-cockroachdb-with-kubernetes.md, line 318 [r2] (raw file):

cockroachdb-1   1/1       Running   0          19m
cockroachdb-2   1/1       Running   0          19m
cockroachdb-3   1/1       Running   4          11m

nit, but I might change the number of restarts from 4 to 1, just to match what users will see

orchestrate-cockroachdb-with-kubernetes.md, line 338 [r2] (raw file):

~~~ shell
$ kubectl delete pods,pvc,petsets,svc -l app=cockroachdb

After grabbing the latest configs from my PR, this can just be:
kubectl delete petsets,pods,persistentvolumes,persistentvolumeclaims,services -l app=cockroachdb
(or the same command using the appropriate abbreviations, but spelling them out seemed more clear to new folks)

Comments from Reviewable

Thanks, @a-robinson. Think I'll keep this PR focused on the local scenario and work on cloud deployment later. But I'll rework the intro to less misleading.

Review status: 0 of 2 files reviewed at latest revision, 14 unresolved discussions.

orchestrate-cockroachdb-with-kubernetes.md, line 7 [r2] (raw file):
Previously, tschottdorf (Tobias Schottdorf) wrote…
> >
>
> Databases are stateful applications, and so running them on Kubernetes requires some of its more complex features, which are still being actively developed and thus only available in alpha versions of Kubernetes. There are easier ways to run CockroachDB for testing purposes on Kubernetes, but the method presented here is destined to become a production deployment once Kubernetes matures sufficiently.
>
> >
>
> CockroachDB will run as a PetSet - roughly speaking, a replication set whose instances are distinguishable and always bound back to the same persistent storage on restart.

Working on improving the intro, @tschottdorf. But can you provide more detail about some of the "easier ways to run CockroachDB" on Kubernetes?

orchestrate-cockroachdb-with-kubernetes.md, line 40 [r2] (raw file):
Previously, a-robinson (Alex Robinson) wrote…
> Add the label `app: cockroachdb` to make deleting the PVs easier. You must have copied this from an older version of my PR before I added it.

Done.

orchestrate-cockroachdb-with-kubernetes.md, line 67 [r2] (raw file):
Previously, a-robinson (Alex Robinson) wrote…
> s/that persistent volumes/that the persistent volumes/

Done.

orchestrate-cockroachdb-with-kubernetes.md, line 82 [r2] (raw file):
Previously, a-robinson (Alex Robinson) wrote…
> Optional, but I might be just a little more specific and replace "same identity and storage" with "same network identity and storage"

Done.

orchestrate-cockroachdb-with-kubernetes.md, line 96 [r2] (raw file):
Previously, a-robinson (Alex Robinson) wrote…
> Again, this isn't quite the most recent version of the file, since I switched this to just be `app: cockroachdb` for easier deletion. I'd recommend re-copying the entire thing

Done.

orchestrate-cockroachdb-with-kubernetes.md, line 277 [r2] (raw file):
Previously, a-robinson (Alex Robinson) wrote…
> I might rephrase this to "kill one of the cockroachdb nodes", since the pod being restarted is more of an indirect consequence of killing the cockroachdb process

Done.

orchestrate-cockroachdb-with-kubernetes.md, line 318 [r2] (raw file):
Previously, a-robinson (Alex Robinson) wrote…
> nit, but I might change the number of restarts from 4 to 1, just to match what users will see

Done.

orchestrate-cockroachdb-with-kubernetes.md, line 338 [r2] (raw file):
Previously, a-robinson (Alex Robinson) wrote…
> After grabbing the latest configs from my PR, this can just be:
> kubectl delete petsets,pods,persistentvolumes,persistentvolumeclaims,services -l app=cockroachdb
>
> (or the same command using the appropriate abbreviations, but spelling them out seemed more clear to new folks)

Done.

Comments from Reviewable

Reviewed 2 of 2 files at r2, 1 of 1 files at r3.
Review status: all files reviewed at latest revision, 16 unresolved discussions, some commit checks failed.

orchestrate-cockroachdb-with-kubernetes.md, line 7 [r2] (raw file):
Previously, jseldess wrote…
> Working on improving the intro, @tschottdorf. But can you provide more detail about some of the "easier ways to run CockroachDB" on Kubernetes?

If you only want a single-node cluster, it's fairly simple to spin up a replication controller of size 1 that uses a persistent disk, but you won't be able to scale it up to more than one node. The config would look like https://github.com/cockroachdb/cockroach/issues/8876
It's even easier if you only want a single-node cluster and don't actually care about persistence (i.e. you're truly just kicking the tries):
kubectl run cockroachdb --image=cockroachdb/cockroach -- start
That'll give you a database that's just using the container's local filesystem, so if it ever gets killed, it'll lose its data. But if all you want is to play around a bit, it is technically running cockroach inside of kubernetes.

orchestrate-cockroachdb-with-kubernetes.md, line 11 [r3] (raw file):

Databases are stateful applications, and so running them on Kubernetes requires some of its more complex features, which are still being actively developed and thus only available in alpha versions of Kubernetes. There are easier ways to run CockroachDB for testing purposes on Kubernetes, but the method presented here is destined to become a production deployment once Kubernetes matures sufficiently.

CockroachDB will run as a PetSet - roughly speaking, a replication set whose instances are distinguishable and always bound back to the same persistent storage on restart.

nit, but "always bound back" sounds funny to me. Perhaps use "bind" instead of "bound"?

orchestrate-cockroachdb-with-kubernetes.md, line 30 [r3] (raw file):

Each CockroachDB node will run in a [pod](http://kubernetes.io/docs/user-guide/pods/), which is a group of one or more Docker containers that can share resources. In our case, each pod will have only one container running a CockroachDB node.

Normally, on-disk files in a pod are ephemeral. If a pod crashes and Kubernetes starts a new one, the on-disk files are lost. To prevent that from happening, you need to mount local temporary directories as [persistent volumes](http://kubernetes.io/docs/user-guide/persistent-volumes/) that will endure for as long as the Kubernetes cluster is running. You also need create [persistent volume claims](http://kubernetes.io/docs/user-guide/persistent-volumes/#persistentvolumeclaims); when pods are created later (one per node), each pod will request a persistent volume claim to "claim" durable storage for its node.

s/need create/need to create/

Comments from Reviewable

@a-robinson, @tschottdorf, please take one final look. I've reworked the intro and added a "Before You Begin" section to introduce Kubernetes concepts.

Review status: 1 of 2 files reviewed at latest revision, 16 unresolved discussions.

orchestrate-cockroachdb-with-kubernetes.md, line 7 [r2] (raw file):
Previously, a-robinson (Alex Robinson) wrote…
> If you only want a single-node cluster, it's fairly simple to spin up a replication controller of size 1 that uses a persistent disk, but you won't be able to scale it up to more than one node. The config would look like https://github.com/cockroachdb/cockroach/issues/8876
>
> It's even easier if you only want a single-node cluster and don't actually care about persistence (i.e. you're truly just kicking the tries):
> kubectl run cockroachdb --image=cockroachdb/cockroach -- start
>
> That'll give you a database that's just using the container's local filesystem, so if it ever gets killed, it'll lose its data.

Thanks, @a-robinson. This is helpful. For now, it seems best to just direct users to follow our approach, which is closer to what you want.

orchestrate-cockroachdb-with-kubernetes.md, line 84 [r2] (raw file):
Previously, arjunravinarayan (Arjun Narayan) wrote…
> Maybe this is obvious to Kubernetes folks, but this was slightly unclear to me. I'm guessing this results in 5 pods with 1 node per pod, but it would be helpful if this was clarified.

I've tried to clarify this in the new "Before Your Begin" section and a few other places. Let me know if it's still confusing.

orchestrate-cockroachdb-with-kubernetes.md, line 210 [r2] (raw file):
Previously, arjunravinarayan (Arjun Narayan) wrote…
> Can you also mention this filename above (as the header to the script itself)? It just makes things super easy when following along (if I was following along I would have already copied the bash script over and given it a random file name).

I've actually changed things to assume that the user will title the yaml file whatever.

orchestrate-cockroachdb-with-kubernetes.md, line 11 [r3] (raw file):
Previously, a-robinson (Alex Robinson) wrote…
> nit, but "always bound back" sounds funny to me. Perhaps use "bind" instead of "bound"?

Done.

orchestrate-cockroachdb-with-kubernetes.md, line 30 [r3] (raw file):
Previously, a-robinson (Alex Robinson) wrote…
> s/need create/need to create/

Done.

Comments from Reviewable

Reviewed 1 of 2 files at r2, 1 of 1 files at r4.
Review status: all files reviewed at latest revision, 18 unresolved discussions.

orchestrate-cockroachdb-with-kubernetes.md, line 298 [r4] (raw file):

## Step 3. Create the Pet Set and start the CockroachDB cluster

In Kubernetes, pods are normally treated as stateless units. The [Pet Set](http://kubernetes.io/docs/user-guide/petset/) feature, however, causes pods to have distinguisable network identity and persistent storage. Using this feature, if a pod crashes or is otherwise removed, Kubernetes will create another pod with the same network identity and storage (as demonstrated in [step 5](#step-5-simulate-node-failure)).

typo in distinguishable

orchestrate-cockroachdb-with-kubernetes.md, line 303 [r4] (raw file):

~~~ yaml
# Excerpted from # Excerpted from https://github.com/cockroachdb/cockroach/tree/develop/cloud/kubernetes/cockroachdb-petset.yaml

Doubled up

Comments from Reviewable

Review status: all files reviewed at latest revision, 19 unresolved discussions, some commit checks failed.

orchestrate-cockroachdb-with-kubernetes.md, line 21 [r4] (raw file):

[minikube](http://kubernetes.io/docs/getting-started-guides/minikube/) | This is the tool you'll use to run a single-node Kubernetes cluster inside a VM on your laptop.
[pod](http://kubernetes.io/docs/user-guide/pods/) | A pod is a group of one of more Docker containers. In our case, each pod will contain one Docker container running a single CockroachDB node. You'll start with 5 pods and grow to 6.
[Pet Set](http://kubernetes.io/docs/user-guide/petset/) | You'll run CockroachDB as a Pet Set to ensure that each pod has distinguishable network identity and always binds back to the same persistent storage on restart. This feature is only available in alpha versions of Kubernetes.

It'd be more correct to say something along the lines of "Pet Sets are only available in Kubernetes clusters that have alpha features enabled".  It's not a separate release track, it's just controlled by a flag in the main Kubernetes releases

orchestrate-cockroachdb-with-kubernetes.md, line 23 [r4] (raw file):

[Pet Set](http://kubernetes.io/docs/user-guide/petset/) | You'll run CockroachDB as a Pet Set to ensure that each pod has distinguishable network identity and always binds back to the same persistent storage on restart. This feature is only available in alpha versions of Kubernetes.
[persistent volume](http://kubernetes.io/docs/user-guide/persistent-volumes/) | Because each CockroachDB node must bind back to the same persistent storage on restart, you'll mount local temporary directories as persistent volumes that will endure for as long as the Kubernetes cluster is running.
[persistent volume claim](http://kubernetes.io/docs/user-guide/persistent-volumes/#persistentvolumeclaims) | When pods are created (one per node), each pod will request a persistent volume claim to “claim” durable storage for its node.

I'd probably say "one per CockroachDB node", since otherwise this could lead people to think only one pod can be scheduled on each underlying VM (which Kubernetes calls "nodes" as well)

Comments from Reviewable

Reviewed 1 of 1 files at r4.
Review status: all files reviewed at latest revision, 19 unresolved discussions, some commit checks failed.

Comments from Reviewable

Review status: 0 of 2 files reviewed at latest revision, 20 unresolved discussions.

orchestrate-cockroachdb-with-kubernetes.md, line 21 [r4] (raw file):
Previously, a-robinson (Alex Robinson) wrote…
> It'd be more correct to say something along the lines of "Pet Sets are only available in Kubernetes clusters that have alpha features enabled".  It's not a separate release track, it's just controlled by a flag in the main Kubernetes releases

Done.

orchestrate-cockroachdb-with-kubernetes.md, line 23 [r4] (raw file):
Previously, a-robinson (Alex Robinson) wrote…
> I'd probably say "one per CockroachDB node", since otherwise this could lead people to think only one pod can be scheduled on each underlying VM (which Kubernetes calls "nodes" as well)

Done.

orchestrate-cockroachdb-with-kubernetes.md, line 298 [r4] (raw file):
Previously, tschottdorf (Tobias Schottdorf) wrote…
> typo in distinguishable

Done.

orchestrate-cockroachdb-with-kubernetes.md, line 303 [r4] (raw file):
Previously, tschottdorf (Tobias Schottdorf) wrote…
> Doubled up

Done.

Comments from Reviewable

@sploiselle, would you mind testing out the steps before I merge?

Review status: 0 of 2 files reviewed at latest revision, 24 unresolved discussions.

orchestrate-cockroachdb-with-kubernetes.md, line 37 [r5] (raw file):

## Step 2. Create persistent volumes and volume claims

To create persistent volumes and volume claims, run the following Bash script or individual `kubetcl` commands:

Storing a copy of this file as something like kubernetes-config.sh and hosting it would be great. This makes it easy to download and then run sh kubernetes-config.sh
This lets you convert this into steps and then expose the contents of the file with the accordion/on-page toggle control. Something like:

Download the kubernetes-config.sh script.
[Script Details]
Run the script:
sh kubernetes-config.sh

orchestrate-cockroachdb-with-kubernetes.md, line 300 [r5] (raw file):

In Kubernetes, pods are normally treated as stateless units. The [Pet Set](http://kubernetes.io/docs/user-guide/petset/) feature, however, causes pods to have distinguishable network identity and persistent storage. Using this feature, if a pod crashes or is otherwise removed, Kubernetes will create another pod with the same network identity and storage (as demonstrated in [step 5](#step-5-simulate-node-failure)).

To create the Pet Set and start the CockrochDB cluster, create a yaml file with the contents below and then run `kubectl create -f <file-name.ymal>` against it.

s/ymal/yaml
Making this downloadable, as well, would be great.

orchestrate-cockroachdb-with-kubernetes.md, line 457 [r5] (raw file):

Then run some [CockroachDB SQL statements](sql-statements.html):

~~~ shell

Mention the bug with the SQL shell for users' sanity.

orchestrate-cockroachdb-with-kubernetes.md, line 485 [r5] (raw file):

~~~ shell
$ kubectl exec cockroachdb-3 -- /bin/bash -c "while true; do kill 1; done"

include output error: error executing remote command: error executing command in container: Error executing in Docker Container: 137 to show that is the desired response and it isn't an actual error

Comments from Reviewable

Review status: 0 of 2 files reviewed at latest revision, 24 unresolved discussions.

orchestrate-cockroachdb-with-kubernetes.md, line 37 [r5] (raw file):
Previously, sploiselle (Sean Loiselle) wrote…
> Storing a copy of this file as something like `kubernetes-config.sh` and hosting it would be great. This makes it easy to download and then run `sh kubernetes-config.sh`
>
> This lets you convert this into steps and then expose the contents of the file with the accordion/on-page toggle control. Something like:
>
> 1. Download the `kubernetes-config.sh` script.
>     [Script Details]
> 2. Run the script:
>    `sh kubernetes-config.sh`

Done.

orchestrate-cockroachdb-with-kubernetes.md, line 300 [r5] (raw file):
Previously, sploiselle (Sean Loiselle) wrote…
> s/ymal/yaml
>
> Making this downloadable, as well, would be great.

Done.

orchestrate-cockroachdb-with-kubernetes.md, line 457 [r5] (raw file):
Previously, sploiselle (Sean Loiselle) wrote…
> Mention the bug with the SQL shell for users' sanity.

Done.

orchestrate-cockroachdb-with-kubernetes.md, line 485 [r5] (raw file):
Previously, sploiselle (Sean Loiselle) wrote…
> include output `error: error executing remote command: error executing command in container: Error executing in Docker Container: 137` to show that is the desired response and it isn't an *actual* error

Done.

Comments from Reviewable

Reviewed 1 of 2 files at r5, 1 of 1 files at r6.
Review status: all files reviewed at latest revision, 25 unresolved discussions.

orchestrate-cockroachdb-with-kubernetes.md, line 70 [r6] (raw file):

   ~~~

4. Wait a bit and then verify that five pods were created successfully. If you don't see five pods, wait longer and try again.

For what it's worth, I initially misinterpreted "try again" here to mean "try creating the resources again" rather than "try running kubectl get pods again". Maybe it's just me, but maybe s/try again/check again/

Comments from Reviewable

Review status: 1 of 2 files reviewed at latest revision, 25 unresolved discussions.

orchestrate-cockroachdb-with-kubernetes.md, line 70 [r6] (raw file):
Previously, a-robinson (Alex Robinson) wrote…
> For what it's worth, I initially misinterpreted "try again" here to mean "try creating the resources again" rather than "try running `kubectl get pods` again". Maybe it's just me, but maybe s/try again/check again/

Done.

Comments from Reviewable


Firebase Performance: Custom traces are not captured in the real devices

Is there an existing issue for this?

[X] I have searched the existing issues.

Which plugins are affected?
Performance
Which platforms are affected?
Android
Description
I created the some custom traces in the app. That traces are captured in the emulator but same custom traces are not captured in the real devices.
Reproducing the issue
Performance dashboard contains the traces only in the emulator device.
Firebase Core version
3.1.1
Flutter Version
0.10.0+2
Relevant Log Output
No response
Flutter dependencies

Expand Flutter dependencies snippet

Replace this line with the contents of your `flutter pub deps -- --style=compact`.

Additional context and comments
No response

@Rasul8215 Thank you for reporting this issue, can you please provide a reproduction repo where I can reproduce this issue?


Add container start time to Metadata/Rancher API

Hi,
would it be possible to add when a container started in the metadata and/or Rancher API? It would be the equivalent of 'StartedAt' in docker inspect.
I am building some monitoring around Rancher and I'd like to use this field together with start_count.
Thank you!
Matteo

There is a created in the API for containers. This is when the container is created in Rancher.
It's not listed in the API docs for the container resource (http://docs.rancher.com/ranchaer/api/api-resources/container/) because it's a common field on all of our resources (http://docs.rancher.com/rancher/api/common/).

@m4ce Would created be sufficient with what you are trying to do?

@m4ce If you are looking for something else, please re-open. :)

@deniseschannon,
sorry for not coming back to you earlier. The created field would not be enough, but I'd say we can leave this for now as it's not super important :)
Thank you for looking into it!


Increase the domain wait_for timeout

This provides a more reasonable length of time to achieve an SSH
connection on a loaded system. 2 seconds is not enough.

I don't know why this was written in this confusing manner, but after digging through the logic I don't think this needs increased. ReadSSHInfo is called via communicate.ready?; notice that this will be retried 60 times, giving you 120 seconds for ssh to be available.

Hi Brian,
I still think something not working here the ssh session only gets 2 second to connect not the 120 second you are stating.
Unless I increase the timeout I cannot get 4 VM running from the vagrant libvirsh plugin, launched without the loop wait timing-out  randomly
Any help  most appreciated.
Nick
Nicholas Randon
HP Cloud | hpcloud.com | 44-117-3162848 (o)
From: Brian Pitts<EMAIL_ADDRESS>Sent: 04 March 2015 04:42
To: pradels/vagrant-libvirt
Cc: Randon, Nicholas
Subject: Re: [vagrant-libvirt] Increase the domain wait_for timeout (#318)
I don't know why this was written in this confusing manner, but after digging through the logic I don't think this needs increased. ReadSSHInfo is called via communicate.ready?; notice that this will be retried 60 times https://github.com/pradels/vagrant-libvirt/blob/ac3582ae535c321d242bf3c59a7a3aff808567ee/lib/vagrant-libvirt/action/wait_till_up.rb#L54-L65 , giving you 120 seconds for ssh to be available.
—
Reply to this email directly or view it on GitHub https://github.com/pradels/vagrant-libvirt/pull/318#issuecomment-77096182 .  https://github.com/notifications/beacon/AKsg2TboVljo8RHn6YkLJdHP36kS9tD4ks5nxoSlgaJpZM4Dma00.gif

Huh, I'll dig into this further then. Can you post your Vagrantfile as well as the output of VAGRANT_LOG=info vagrant up?

I expect to see log info like
==> server1: Waiting for SSH to become available...
 INFO machine: Calling action: read_ssh_info on provider Libvirt (cc4c8225-eb93-4948-bd88-ecef9701ac04)
 INFO runner: Preparing hooks for middleware sequence...
 INFO runner: 1 hooks defined.
 INFO runner: Running action: #<Vagrant::Action::Builder:0x00000003f036d0>
 INFO warden: Calling IN action: #<Vagrant::Action::Builtin::ConfigValidate:0x00000003f21c70>
 INFO warden: Calling IN action: #<VagrantPlugins::ProviderLibvirt::Action::ConnectLibvirt:0x00000003f21b80>
 INFO warden: Calling IN action: #<VagrantPlugins::ProviderLibvirt::Action::ReadSSHInfo:0x000000048dfd98>
 INFO warden: Calling OUT action: #<VagrantPlugins::ProviderLibvirt::Action::ReadSSHInfo:0x000000048dfd98>
 INFO warden: Calling OUT action: #<VagrantPlugins::ProviderLibvirt::Action::ConnectLibvirt:0x00000003f21b80>
 INFO warden: Calling OUT action: #<Vagrant::Action::Builtin::ConfigValidate:0x00000003f21c70>
 INFO ssh: Attempting SSH connection...
 INFO ssh: Attempting to connect to SSH...
 INFO ssh:   - Host: <IP_ADDRESS>
 INFO ssh:   - Port: 22
 INFO ssh:   - Username: vagrant
 INFO ssh:   - Password? false
 INFO ssh:   - Key Path: ["/home/pittsb/pool-test/.vagrant/machines/server1/libvirt/private_key"]
 INFO retryable: Retryable exception raised: #<Timeout::Error: execution expired>
 INFO ssh: Attempting to connect to SSH...
 INFO ssh:   - Host: <IP_ADDRESS>
 INFO ssh:   - Port: 22
 INFO ssh:   - Username: vagrant
 INFO ssh:   - Password? false
 INFO ssh:   - Key Path: ["/home/pittsb/pool-test/.vagrant/machines/server1/libvirt/private_key"]
 INFO ssh: SSH is ready!
 INFO ssh: Execute:  (sudo=false)
 INFO machine: Calling action: read_ssh_info on provider Libvirt (cc4c8225-eb93-4948-bd88-ecef9701ac04)
 INFO runner: Preparing hooks for middleware sequence...
 INFO runner: 1 hooks defined.
 INFO runner: Running action: #<Vagrant::Action::Builder:0x0000000390e388>
 INFO warden: Calling IN action: #<Vagrant::Action::Builtin::ConfigValidate:0x00000003b21350>
 INFO warden: Calling IN action: #<VagrantPlugins::ProviderLibvirt::Action::ConnectLibvirt:0x00000003b21328>
 INFO warden: Calling IN action: #<VagrantPlugins::ProviderLibvirt::Action::ReadSSHInfo:0x00000003bbf640>
 INFO warden: Calling OUT action: #<VagrantPlugins::ProviderLibvirt::Action::ReadSSHInfo:0x00000003bbf640>
 INFO warden: Calling OUT action: #<VagrantPlugins::ProviderLibvirt::Action::ConnectLibvirt:0x00000003b21328>
 INFO warden: Calling OUT action: #<Vagrant::Action::Builtin::ConfigValidate:0x00000003b21350>
 INFO wait_till_up: Time for SSH ready: 15.344028949737549

Notice that it retried when the timeout expired and in total waited 15 seconds.

@randonn I wanted to check again on your Vagrantfile and log output.

I think this needs to be reopened. It's not that the machine needs 120 seconds to respond, it appears that the 2 second window is only sufficient when the host system is not loaded. Once it's loaded trying to start a number of machines in parallel appear to hit the 2 second limit all the time no matter how times it's retried. I do find that 5 seconds is enough to work around the issue for me with 7 VM's in parallel. So potentially it may not be by much that it hits this limit.
I can investigate to see if I can confirm in this specific case whether the 60 retries are actually occurring and timing out in each case (seemed to happen a little soon for that to be the case) and provide some log output.
However given that it should be possible to provide a remote url to be used as the connection uri instead of qemu:///system which would result in fog using SSH, it seems like this should really be a configurable setting to allow a little more flexibility depending on the connection being used.


Zend\View\Helper\FlashMessenger isn't compatible with Expressive

In our project, we use Zend\Expressive as core and Zend\View as template engine. And we come across with an issue that FlashMessenger only works with Zend\Mvc\Controller\Plugin\FlashMessenger or Zend\Mvc\Plugin\FlashMessenger\FlashMessenger. None of them is available in Expressive and add dependencies on Zend\Mvc isn't a good idea.
There are different Flash implementations and will be great that Zend\View\Helper\FlashMessenger depend on some FlashInterface instead of Zend\Mvc\Plugin\FlashMessenger\FlashMessenger. This feature will allow integrating Zend\View\Helper\FlashMessenger with many Flash Messanger libraries.
I've written a module for this but for now FlashInterface is dirty and require improvement.

@popovserhii Have you seen https://github.com/zendframework/zend-expressive-flash ?

@webimpress Yes, but this module isn't working correctly.
The problem is not in zend-expressive-flash but in zend-expressive-session-ext.
Аfter composer require zendframework/zend-expressive-flash and modifying config/pipeline.php, authorization to my admin stops working. I was trying to understand but everything is very confusing. That why I've created a custom module.
But even if zend-expressive-flash will work I will not be able to use a flashMessanger helper which helps renders html markup.

the zend-expressive-flash should work, I created a blog post about it some time ago https://samsonasik.wordpress.com/2018/02/11/using-view-helper-for-accessing-zend-expressive-flash-messages-in-expressive-3/

This repository has been closed and moved to laminas/laminas-view; a new issue has been opened at https://github.com/laminas/laminas-view/issues/8.


better social links in the footer

in the footer part only one social email is mentioned via text , we can improve this using an icon that on hover shows the mail to the user in form of blob and on click directs the user to the mail
this will enhance the UI and we can add other social links as well (if required)
please assign this issue to me as I already have it forked to local and am working on other issues as well

Hi
I would like to take up this project for adding elements to the footer section
We can make the footer section with more impressive UI and progressive elements to make it look amazing
We can add several icons and hyperlinks and lil more creative designs for better attractiveness
I would be delighted to take up this task
Thank you.

I can handle this issue more efficiently

Theme section for diverse individuals.
Even though we can add icons which make it more tempting in apperance.
Here we can add hover effect which make it more realistic.
Footer section will be responsive for all kind of screen sizes.
Back to Top button integration.
Please assigned this to me for revolutinary betterment in the footer section.

@Suchitra-Sahoo,  Ma'am this is petition to let people who raised issues have the assignment , as it fosters a sense of engagement for the others to look up for issues themselves and be more creative in raising features and bugs.
thankyou

Assign this issue to me
As a full stack Developer i can write optimized code and responsive and i can integrate with backend also.

@Suchitra-Sahoo the leaderboard isnt counting contributions before 7pm , please make sure to merge requests after that

@Suchitra-Sahoo please assign me this task as have a keen interest in working on this


Save torch state

setTorchOn can now be called before the camera is initialized.
The torch state is now also saved, persisting it over orientation changes.
Fixes #128.

Hello,
My setTorchOn() problem not resolved yet, i am doing like this....
I am implementing CompoundBarcodeView.TorchListener and
barcodeView = CompoundBarcodeView
barcodeView.setOnTorchListener(this)
On toggle button i am calling....
if(on)
barcodeView.setTorchOff()
else
barcodeView.setTorchOn()
i'm getting same problem like it was on [issue #128] (https://github.com/journeyapps/zxing-android-embedded/issues/128)


[Snyk] Upgrade react-virtualized from 9.22.2 to 9.22.3

Snyk has created this PR to upgrade react-virtualized from 9.22.2 to 9.22.3.

As this is a private repository, Snyk-bot does not have access. Therefore, this PR has been created automatically, but appears to have been created by a real user.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 1 version ahead of your current version.
The recommended version was released 2 months ago, on 2020-12-18.

Release notes

Package name: react-virtualized

9.22.3 - 2020-12-18
Add Trusted Types support  e1bbd63
Fix #1575: Create Trusted Type policy for assigning an HTML in detectElementResize.js (#1614)  dfc1190

v9.22.2...v9.22.3

9.22.2 - 2020-08-10No content.

    from react-virtualized GitHub release notes

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

 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.You have signed the CLA already but the status is still pending? Let us recheck it.


Add positioning interactions

Should have been done a while back...

The hand based placement interactions look solid.


Upgrade the prometheus monitoring host

prometheus.ooni.nu
xref: https://github.com/ooni/sysadmin/issues/383

This has been done


packaging request: texlab

Project description
An LSP server for latex. Rust + node I think
Metadata

homepage URL: https://github.com/latex-lsp/texlab
source URL: https://github.com/latex-lsp/texlab
license: mit
platforms: unix, linux, darwin, ...

I don't use LaTeX as much as I did in university, but this looks awesome! I will try packing this and report any progress here.

I'm running into an issue that require some investigation. It looks like cargo vendor fails when trying to build the ducc dependency.
Vendoring ducc v0.1.0 (https://github.com/SkylerLipthay/ducc?rev=558a0ec83cbb8aff57043cfafdb3d728cd509211#558a0ec8) (/build/source/cargo-home.waU/git/checkouts/ducc-19f01d0c414a7f8f/558a0ec/ducc) to /nix/store/1zb7yxnqjn8rn02qhd7mfh5kbl70w16j-texlab-1.5.0-vendor/ducc
error: failed to sync

Caused by:
  failed to copy over vendored sources for: ducc v0.1.0 (https://github.com/SkylerLipthay/ducc?rev=558a0ec83cbb8aff57043cfafdb3d728cd509211#558a0ec8)

Caused by:
  failed to copy `/build/source/cargo-home.waU/git/checkouts/ducc-19f01d0c414a7f8f/558a0ec/ducc/LICENSE` to `/nix/store/1zb7yxnqjn8rn02qhd7mfh5kbl70w16j-texlab-1.5.0-vendor/ducc/LICENSE`

Caused by:
  Too many levels of symbolic links (os error 40)

I have pushed my progress so far to: https://github.com/MetaDark/nixpkgs/blob/texlab/pkgs/development/tools/misc/texlab/default.nix

Building the project manually, it also looks like texlab depends on nightly rust and won't build with the RUSTC_BOOTSTRAP = 1 workaround. The variable shouldn't be used unless bootstrapping rustc anyway.
I managed to generate a rustPlatform using same toolchain defined in rust-toolchain (with the nixpkgs-mozilla overlay), but I don't know if that's the best solution. There should be a better way build with a nightly compiler.

thanks for looking into this. I don't know much about either rust or the node ecosystem (else I would have it packaged). This is what I get
   Vendoring deflate v0.7.20 (/build/source/cargo-home.rST/registry/src/github.com-1ecc6299db9ec823/deflate-0.7.20) to /nix/store/1zb7yxnqjn8rn02qhd7mfh5kbl70w16j-texlab-1.5.0-vendor/deflate
   Vendoring ducc v0.1.0 (https://github.com/SkylerLipthay/ducc?rev=558a0ec83cbb8aff57043cfafdb3d728cd509211#558a0ec8) (/build/source/cargo-home.rST/git/checkouts/ducc-19f01d0c414a7f8f/558a0ec/ducc) to /nix/store/1zb7yxnqjn8rn02qhd7mfh5kbl70w16j-texlab-1.5.0-vendor/ducc
error: failed to sync

Caused by:
  failed to copy over vendored sources for: ducc v0.1.0 (https://github.com/SkylerLipthay/ducc?rev=558a0ec83cbb8aff57043cfafdb3d728cd509211#558a0ec8)

Caused by:
  failed to copy `/build/source/cargo-home.rST/git/checkouts/ducc-19f01d0c414a7f8f/558a0ec/ducc/LICENSE` to `/nix/store/1zb7yxnqjn8rn02qhd7mfh5kbl70w16j-texlab-1.5.0-vendor/ducc/LICENSE`

Caused by:
  Too many levels of symbolic links (os error 40)
Traceback (most recent call last):
  File "/nix/store/wxvxg9pr09lizvi0ysfs6119q8g2b4xb-cargo-vendor-normalise/bin/.cargo-vendor-normalise-wrapped", line 42, in <module>
    main()
  File "/nix/store/wxvxg9pr09lizvi0ysfs6119q8g2b4xb-cargo-vendor-normalise/bin/.cargo-vendor-normalise-wrapped", line 17, in main
    assert list(data.keys()) == ["source"]

nb: I had packaged https://github.com/astoff/digestif but it now crahes plus texlab now has a coc-texlab plugin.

@teto The traceback in cargo-vendor-normalize is caused by the failure in cargo vendor:
https://github.com/NixOS/nixpkgs/blob/3dd112c97e242d9ae7910178e1e1c62febfb6819/pkgs/build-support/rust/fetchcargo.nix#L46
The toml response comes back empty, so the script doesn't find a source key.
Building with nix-build --keep-failed I noticed that the LICENSE file symlinks to itself, which is probably what is causing the failure. Although, I'm not sure how it gets to that state in the first place.

I'm still trying to figure out the issue with vendoring ducc, but I haven't made any progress.
I tried generating a nix derivation using carnix, but it also failed on ducc, this time with:
Could not translate target.
I'm assuming the issue is related to the dependency using a git repo rather than crates.io, but it's not clear how it should be fixed.

I wanted to package texlab as well and I've encountered exactly the same errors .I've found out though that 8 days ago, ducc was released on crates.io. I've suggested citeproc to use it and I intend to try to build texlab when that's updated but I get some build errors which are not related to any of the dependencies updates.

@doronbehar As @efoerster mentioned in https://github.com/latex-lsp/texlab/issues/97, texlab expects a nightly compiler to build. I tried building with RUSTC_BOOTSTRAP = 1 which is what the lsp and racer packages use to force nightly features on a stable compiler, but it still wouldn't build.
It's possible to use the nightly overlay from https://github.com/mozilla/nixpkgs-mozilla/, but it may be better to wait until Rust 1.39 is released.

So I guess we'll wait until both of them are released.. I'll subscribe to https://github.com/rust-lang/rust/releases.atom in the meantime.

I think Texlab can now be packaged, rustc 1.39.0 is released and merged to master, see #72980.

@doronbehar I was able to build the package with nix-shell in a non sandboxed environment, but trying to build in nix-shell <nixpkgs> --pure -A textlab or with nix-build <nixpkgs> -A textlab fails.
error: couldn't read src/citeproc/js/dist/citeproc.js: No such file or directory (os error 2)
 --> src/citeproc/mod.rs:8:23
  |
8 | const JS_CODE: &str = include_str!("js/dist/citeproc.js");
  |                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

error: aborting due to previous error

error: could not compile `texlab`.

It looks like build.rs fails to create a dist package of citeproc in the sandboxed environment. I'll keep looking into this.

I managed to come up with a solution to a similar issue with gotify-server in https://github.com/NixOS/nixpkgs/pull/70441 where technically a separate ("private") package which consisted of a node_modules directory was needed for the build to work inside the sandbox.
A similar workaround is needed here, but with node2nix.

I just wanted to say that texlab 4.0.0 is out now, in case someone has time and desire to update.

Thanks for the notification @MordragT . See https://github.com/NixOS/nixpkgs/pull/175752


BD Installer keeps crashing on i3wm

Describe the Bug
When i open the BD Installer it keeps crashing.
To Reproduce
Download the official installer, run it.
Expected Behavior
Install BD
Discord Version
Stable
Additional Context
OS: Garuda Linux
WM: i3
Graphics Card: Nvidia GeForce RTX 3060
It works fine on Gnome. So it's up to i3wm. I'll leave the issue open anyway, because there will definitely be others with the same problem using i3wm.
It's not a serious bug as there are workarounds (use a different window manager) but I think someone should take a look anyway.
Error message (terminal):
Better Discord Installer 1.1.1
The installer is up to date.
[527787:0220/164335.293822:FATAL:gpu_data_manager_impl_private.cc(439)] GPU process isn't usable. Goodbye.
[1]    527787 trace trap (core dumped)  ./BetterDiscord-Linux.AppImage

Same issue here, I also use i3wm

"gpu process isn't usable"
🤡

I am facing the same thing, on Gnome x11

Try using the installer with --no-sandbox

Try using the installer with --no-sandbox

Actually worked, thanks a lot. I'll leave the issue open anyway. Just someone looking at it.

I am having the same issue, running Manjaro with KDE-Plasma. I happens both with the AUR package and the official AppImage from here. Running it with --no-sandbox fixes it though as others above have mentioned.

Try using the installer with --no-sandbox

Thank you so much, it worked :D

it works indeed !
May I suggest to add a notice in the logs to use --no-sandbox, when it crashes ?


4G LTE - No cellular connection

Dear Nebra,
I am currently experiencing difficulties getting the LTE configuration to work for the Nebra Outdoor hotspot.
Have tested on two different miners with both Quectel EG25-G and EG25-G-S mPCIe modules. Have tested with SIM cards from two different network providers (TDC and 3 in Denmark) on both miners and manually added the APN details specified by said network providers.
Have also tried several other APN settings/configurations (broadband, mms, LTE, *99#, *99…1#, ect) not specified by network providers to perform general troubleshooting.
No configuration is currently supporting a connection via cellular connection. Outbound and inbound peer-to-peer connections reads as not-connected (gray x) in the Helium app for both hotspots
Connections via Wifi or Ethernet is working perfectly.
Modem Detected is “True” for Diagnostic Information for both hotspots.
SIM cards have been tested in Zyxel LTE4506-M606 mobile wifi unit and are working. SIM cards therefore not damaged or inactive.
Outdoor Hotspot LTE configuration as per your guides has been followed.
Trying to determine source of problem:

Is any other action than pasting the cellular file into system-connection required? Your guide currently shows (you should also see some files already there called ???) which seems incomplete, so I am wondering if a step is missing? Does something need to be unplugged physically or changed when accessing resin-boot?

Does LTE antenna connection have an impact on cellular connection? No pictures of how to connect the connections cables is show in your current hotspot quickstart guide with regard to antenna placement. I have mine connected to the plugs on the outmost right and left. Not the middle.

Is location assertion required on order for a cellular connection to be established?

Any assistance would be much appreciated.
Thank you.
Almanaka

How do you know it's not connected?
And are you sure your APN settings are correct? That's the most important part really. The hardware is working as it's detected by the miner.

Hi,
The miner was 100% synchronized with Blockchain, month back. Miner is
connected via LAN, but do not light LAN diodes.  It also does not go through
the connect to Bluetooth button. Only under LED is shines.
--
S přáním hezkého dne
Přemysl Choleva
+420 725 036 789
---------- Původní e-mail ----------
Od: Aaron Shaw @.>
Komu: NebraLtd/Helium-Guides @.>
Datum: 23. 8. 2021 23:26:17
Předmět: Re: [NebraLtd/Helium-Guides] 4G LTE - No cellular connection (#159)
"
How do you know it's not connected?
And are you sure your APN settings are correct? That's the most important
part really. The hardware is working as it's detected by the miner.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
(https://github.com/NebraLtd/Helium-Guides/issues/159#issuecomment-904144761)
, or unsubscribe
(https://github.com/notifications/unsubscribe-auth/AVKEHTSY5LYQMVBKTQM5WRDT6K4HJANCNFSM5CVKFRMA)
.
"

@Premmmi this is unrelated to this issue. This issue is about a 4G connection

Hi,
My hotspot suddenly stopped all activity, without ano logical reason...and
they are dead for weeks now. They previously worked fine, my internet
connection is top of the line, ports are open, the devices are backed up
with colling units, everything should be in order...except it isnt, and my
units arent mining at all. I ve manually unplugged and plugged them numerous
time...it didnt helped, restarted the routers...didnt helped. Ergo...I am
here, asking you for your help and guidance.
I can provide you with additional information...MAC codes, ETH code and all
that, just tell me where to approach you...since nebra support email doesnt
give me any feedback for weeks now.
Can you help me, please?
--
S přáním hezkého dne
Přemysl Choleva
+420 725 036 789
---------- Původní e-mail ----------
Od: Aaron Shaw @.>
Komu: NebraLtd/Helium-Guides @.>
Datum: 25. 8. 2021 1:03:10
Předmět: Re: [NebraLtd/Helium-Guides] 4G LTE - No cellular connection (#159)
"
@Premmmi(https://github.com/Premmmi) this is unrelated to this issue. This
issue is about a 4G connection
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
(https://github.com/NebraLtd/Helium-Guides/issues/159#issuecomment-905032067)
, or unsubscribe
(https://github.com/notifications/unsubscribe-auth/AVKEHTVILTEX3YYJC3I4U63T6QQKTANCNFSM5CVKFRMA)
.
"

Hallo ich habe genau das gleiche Problem. Ich benutze auch die Quectel EG25-G.
Da als Benutzer keinerlei Möglichkeit besteht bei laufenden Hotspot eine 4G Verbindung zu prüfen - Terminal, Onboard Website. Auch ein Priorisieren einer Netzwerk Verbindung ist nicht möglich. Ich würde gerne weiterhin per WLAN oder LAN verbunden sein aber Trotzdem soll der Traffic über 4G laufen.
Auch ich habe die SIM Karte mit einem Externen LTE Router getestet wenn der Hotspot daran angeschlossen ist per LAN Funktioniert auch alles (Relay).
Mein Anbieter in Deutschland ist Mobilcom-Debitel - o2 Deutschland
---- Google Übersetzt aus dem Deutschen -> Englisch
Hi, I have exactly the same problem. I also use the Quectel EG25-G.
As the user has no way of checking a 4G connection while the hotspot is running - terminal, onboard website. It is also not possible to prioritize a network connection. I would like to continue to be connected via WLAN or LAN, but the traffic should still run over 4G.
I also tested the SIM card with an external LTE router if the hotspot is connected to it via LAN Everything works (relay).
My provider in Germany is Mobilcom-Debitel - o2 Germany

@shawaj
Thanks for your reply.
When rebooting the miner and running diagnostics, I get a gray x in inbound, outbound and sync status. When checking the data usage on the employed SIM card after a couple of days, no data transfers has been made. The wifi connection reads as not connected.
Honestly the APN settings might very well be the problem. At least I cannot rule out that my network providers has given me the wrong information. I will try with other providers and SIM cards in the following weeks in order to see this will resolve the matter.
However, both my current network providers are quite confident that they have provided the correct APN setting. It is for this reason that I am also exploring other potential root causes for the missing cellular connection. Just in case I have missed or misunderstood something. :)
From your reply, I take it that none of the three questions I posted should have any impact on celluar connectivity?
And you have not encountered anyone else that had to deviate from your LTE configuration guide to get cellular connectivity to work?

@Almanaka @Premmmi @zonfacter Please share the details with<EMAIL_ADDRESS>I'm closing this issue since it's not related to the documentation.


How to locate and use a local Boost installation?

First of all, sorry for not using the issue template. It did't seem a good fit for a question like this. If there's a better place to ask this question, please let me know.
I have a C++ project that uses CMake, and I'm considering migrating to Gradle. The one thing that keeps me from migrating is support for locating the Boost libraries.
In addition to the header-only Boost libraries, my project also uses some Boost libraries that require compilation. CMake comes with a module named FindBoost. You tell it what version and what kind build you need (static or dynamic libs, static or dynamic C++ runtime, single-threaded or multi-threaded...). The plugin then automatically finds a matching local Boost installation (by looking at BOOST_ROOT etc.). Within that installation, it finds the library files that match the specified configuration.
Using FindBoost, my CMake-based build automatically finds the correct Boost libraries on any platform (Windows/Mac/Linux).
Does Gradle have a similar mechanism? How would I setup a Gradle project that automatically finds the correct local Boost installation and uses the libraries with the correct configuration?

Thanks @DanielSWolf for this question/issue. At the moment, we don't yet have an excellent solution to solve this problem. This issue is already tracked by https://github.com/gradle/gradle-native/issues/380 which I encourage you to follow and comment your use case. We are looking at adding a similar capability for any prebuilt library installed on your system. Until then, you would have to resort to a custom plugin making the same discovery.
I also encourage you to look at the native samples which demonstrate common use case with Gradle. With regards to holding the migration to Gradle, you can start using Gradle today by merely wrapping CMake. Then, you can piece out the part of the build that doesn't require feature provided out of the box by CMake. Once the prebuilt library support makes its way to the core of Gradle, you can migrate the last part, or you can write a custom plugin that searches for the right Boost binaries.
Thanks for the question. You can use the Gradle user forum for such question in the future.


In memory

if you open database in-memory ($FloorAppDatabase.inMemoryDatabaseBuilder().build();)
in current implementation has a BUG.
in source code this moment doesn't work, because sqlite open database by the path.
Future<sqflite.Database> open(String name, List<Migration> migrations,
      [Callback callback]) async {
    final path = join(await sqflite.getDatabasesPath(), name);

    return sqflite.openDatabase(
      path,
      version: 1,
      onConfigure: (database) async {
        await database.execute('PRAGMA foreign_keys = ON');
      },

but if we change this code (path -> ':memory:') to
Future<sqflite.Database> open(String name, List<Migration> migrations,
      [Callback callback]) async {
    // final path = join(await sqflite.getDatabasesPath(), name);

    return sqflite.openDatabase(
      ':memory:',
      version: 1,
      onConfigure: (database) async {
        await database.execute('PRAGMA foreign_keys = ON');
      },

all works good.

Good find @rimidalv! I'll provide a fix as soon as possible.


[Glue] Add support to more fields in Glue job

Add support to more fields in Glue job

CodeGenConfigurationNodes
ExecutionClass
SourceControlDetails

@bblommers if you find time, could you take a look? Thanks in advance!


[FORMATTING] When the language is postgres, executing "select * from test. [User]" will result in an error message

Input data
Which SQL and options did you provide as input?
select * from  test.[User]

Actual Output
none result

Console Output
Uncaught Error: Parse error at token: [ at line 1 column 21
Unexpected OPEN_PAREN token: {"type":"OPEN_PAREN","raw":"[","text":"[","start":20}. Instead, I was expecting to see one of the following:

A LINE_COMMENT token based on:
    comment →  ● %LINE_COMMENT
    _$ebnf$1 → _$ebnf$1 ● comment
    _ →  ● _$ebnf$1...

at Parser.feed (nearley.js:343:27)
    at Object.parse (createParser.ts:33:34)
    at Formatter.parse (Formatter.ts:41:49)
    at Formatter.format (Formatter.ts:33:22)
    at formatDialect (sqlFormatter.ts:94:57)
    at formatSqlValue (index.vue:193:23)
    at formatValue (index.vue:170:9)
    at callWithErrorHandling (runtime-core.esm-bundler.js:158:18)
    at callWithAsyncErrorHandling (runtime-core.esm-bundler.js:166:17)
    at SVGSVGElement.invoker (runtime-dom.esm-bundler.js:595:5)

Usage

How are you calling / using the library?
import { formatDialect,sql,plsql,transactsql,postgresql } from 'sql-formatter'
formatDialect(sqlVal, { dialect: postgresql})
What SQL language(s) does this apply to?
postgresql

Which SQL Formatter version are you using?
13.0.4

This is to be expected because that's not valid PostgreSQL code.

I know this is not a valid PostgreSQL code and I think we can give a friendly prompt instead of reporting an error.

So you would expect a different kind of exception to be thrown?

So you would expect a different kind of exception to be thrown?
Yes,It's better this way because I don't know if there are any other errors, so I wouldn't know how to differentiate them when using try-catch.

So, instead of getting an instance of Error you would like to something like an instance of ParseError to be thrown?
That's a possible change. But it'll have to wait until next major release as it would be a breaking change.
Though I'm really in the same boat as you. I don't know what other kinds of errors might come from the Nearley parser. I'd have to catch this parse error from Nearley and re-throw it as some other type of error. I'm not quite sure whether it would be better to wrap the underlying parser errors or leave them as-is.
I think a simpler approach for you might be to simply check if error.message starts with text: Parse error. This way you can catch both parsing errors from sql-formatter itself and from the underlying Nearley parser.
See sqlFormatter.test.ts for an overview of what kind of errors you can expect.


backend: aggregate and suggest APIs not working properly

Affected module
Does it impact the UI, backend or Ingestion Framework?
backend
Describe the bug

A clear and concise description of what the bug is.
Both the aggregate and suggest APIs are not working for the container entity when trying to search through the columns field.

https://user-images.githubusercontent.com/51777795/229433682-54b0964a-bd83-44f2-bf66-eda35f63df03.mov

Aggregate:
Request URL: /api/v1/search/aggregate?index=container_search_index&field=dataModel.columns.name

Suggest:
Request URL: /api/v1/search/suggest?index=container_search_index&field=column_suggest&q=d

Suggest API is not working properly for the Dashboard entity for the chart_suggest field. As shown in the video, the dashboard FCC New Coder Survey 2018 should return two charts in suggestion when searched with the query bo(i.e. Box Plot and Boy Name Cloud), but the response object contains only one option, although the length of results in the object is 2.

https://user-images.githubusercontent.com/51777795/229471413-c8e2f52a-fdb9-473b-b148-207fd8deb4cf.mov
Request URL: /api/v1/search/suggest?index=dashboard_search_index&field=chart_suggest&q=bo
Response:
{
    "text": "bo",
    "offset": 0,
    "length": 2,
    "options": [
        {
            "text": "Box plot",
            "_index": "dashboard_search_index",
            "_type": "_doc",
            "_id": "0021151a-65bd-4638-8717-86546cfd9bab",
            "_score": 10,
            "_source": {
                "id": "0021151a-65bd-4638-8717-86546cfd9bab",
                "name": "FCC New Coder Survey 2018",
                "displayName": "FCC New Coder Survey 2018",
                "fullyQualifiedName": "sample_superset.11",
                "description": "",
                "version": 0.1,
                "updatedAt":<PHONE_NUMBER>906,
                "updatedBy": "admin",
                "dashboardUrl": "http://localhost:808/superset/dashboard/7/",
                "charts": [
                    {
                        "id": "3194d51e-b75e-4062-901f-20047982d13e",
                        "type": "chart",
                        "name": "170",
                        "fullyQualifiedName": "sample_superset.170",
                        "description": "",
                        "displayName": "Box plot",
                        "deleted": false
                    },
                    {
                        "id": "648d9946-1c7b-4dd0-ad5e-fdfdd1c389e1",
                        "type": "chart",
                        "name": "180",
                        "fullyQualifiedName": "sample_superset.180",
                        "description": "",
                        "displayName": "Boy Name Cloud",
                        "deleted": false
                    },
                    {
                        "id": "074dff51-2310-4030-b70c-41c9720faa30",
                        "type": "chart",
                        "name": "183",
                        "fullyQualifiedName": "sample_superset.183",
                        "description": "",
                        "displayName": "Average and Sum Trends",
                        "deleted": false
                    },
                    {
                        "id": "6b4a27bc-ea81-445c-b3b1-da7ddf2923c1",
                        "type": "chart",
                        "name": "197",
                        "fullyQualifiedName": "sample_superset.197",
                        "description": "",
                        "displayName": "Arcs",
                        "deleted": false
                    }
                ],
                "dataModels": [],
                "href": "http://localhost:8585/api/v1/dashboards/0021151a-65bd-4638-8717-86546cfd9bab",
                "followers": [],
                "tags": [],
                "service": {
                    "id": "6a375a27-0a10-4661-8636-ea29bc254d1f",
                    "type": "dashboardService",
                    "name": "sample_superset",
                    "fullyQualifiedName": "sample_superset",
                    "deleted": false
                },
                "serviceType": "Superset",
                "usageSummary": {
                    "dailyStats": {
                        "count": 0,
                        "percentileRank": 0
                    },
                    "weeklyStats": {
                        "count": 0,
                        "percentileRank": 0
                    },
                    "monthlyStats": {
                        "count": 0,
                        "percentileRank": 0
                    },
                    "date": "2023-04-03"
                },
                "deleted": false,
                "tier": null,
                "suggest": [
                    {
                        "input": "sample_superset.11",
                        "weight": 5
                    },
                    {
                        "input": "FCC New Coder Survey 2018",
                        "weight": 10
                    }
                ],
                "chart_suggest": [
                    {
                        "input": "Box plot",
                        "weight": 5
                    },
                    {
                        "input": "Boy Name Cloud",
                        "weight": 5
                    },
                    {
                        "input": "Average and Sum Trends",
                        "weight": 5
                    },
                    {
                        "input": "Arcs",
                        "weight": 5
                    }
                ],
                "service_suggest": [
                    {
                        "input": "sample_superset",
                        "weight": 5
                    }
                ],
                "entityType": "dashboard"
            }
        }
    ]
}

To Reproduce
Screenshots or steps to reproduce
Expected behavior
A clear and concise description of what you expected to happen.
Version:

OS: [e.g. iOS]
Python version:
OpenMetadata version: [e.g. 0.8]
OpenMetadata Ingestion package version: [e.g. openmetadata-ingestion[docker]==XYZ]

Additional context
Add any other context about the problem here.

@aniketkatkar97 always .keyword for a filed at the end.
cc @chirag-madlani
http://localhost:8585/api/v1/search/aggregate?index=container_search_index&field=dataModel.columns.name.keyword
    "took": 14,
    "timed_out": false,
    "_shards": {
        "total": 1,
        "successful": 1,
        "skipped": 0,
        "failed": 0
    },
    "hits": {
        "total": {
            "value": 7,
            "relation": "eq"
        },
        "max_score": null,
        "hits": []
    },
    "aggregations": {
        "sterms#dataModel.columns.name.keyword": {
            "doc_count_error_upper_bound": 0,
            "sum_other_doc_count": 0,
            "buckets": [
                {
                    "key": "approved",
                    "doc_count": 1
                },
                {
                    "key": "budget_executor",
                    "doc_count": 1
                },
                {
                    "key": "budget_total_value",
                    "doc_count": 1
                },
                {
                    "key": "department_id",
                    "doc_count": 2
                },
                {
                    "key": "fraudulent_claims",
                    "doc_count": 1
                },
                {
                    "key": "merchant",
                    "doc_count": 1
                },
                {
                    "key": "notes",
                    "doc_count": 1
                },
                {
                    "key": "total_value_for_current_month",
                    "doc_count": 1
                },
                {
                    "key": "transaction_id",
                    "doc_count": 1
                },
                {
                    "key": "transaction_time",
                    "doc_count": 1
                }
            ]
        }
    }
}```

suggest
http://localhost:8585/api/v1/search/suggest?index=container_search_index&field=column_suggest&q=d ```

Response

{
"suggest": {
"metadata-suggest": [
{
"text": "d",
"offset": 0,
"length": 1,
"options": [
{
"text": "department_id",
"_index": "container_search_index",
"_type": "_doc",
"_id": "fbb18d09-b4d9-455b-8186-e5132ebe2e18",
"_score": 5.0,
"_source": {
"id": "fbb18d09-b4d9-455b-8186-e5132ebe2e18",
"name": "finance",
"fullyQualifiedName": "s3_object_store_sample.departments.finance",
"displayName": "Finance department",
"description": "Bucket containing finance department information",
"version": 0.1,
"updatedAt":<PHONE_NUMBER>774,
"updatedBy": "admin",
"href": "http://localhost:8585/api/v1/containers/fbb18d09-b4d9-455b-8186-e5132ebe2e18",
"service": {
"id": "d448d780-52ab-4254-bc85-061ecb0040c1",
"type": "objectStoreService",
"name": "s3_object_store_sample",
"fullyQualifiedName": "s3_object_store_sample",
"deleted": false,
"href": "http://localhost:8585/api/v1/services/objectStoreServices/d448d780-52ab-4254-bc85-061ecb0040c1"
},
"parent": {
"id": "c9624db8-06d4-44e4-8bd7-89cda9d19b20",
"type": "container",
"name": "departments",
"fullyQualifiedName": "s3_object_store_sample.departments",
"description": "Bucket containing company department information",
"displayName": "Company departments",
"deleted": false,
"href": "http://localhost:8585/api/v1/containers/c9624db8-06d4-44e4-8bd7-89cda9d19b20"
},
"dataModel": {
"isPartitioned": false,
"columns": [
{
"name": "department_id",
"dataType": "NUMERIC",
"dataTypeDisplay": "numeric",
"description": "The ID of the department. This column is the primary key for this table.",
"fullyQualifiedName": "s3_object_store_sample.departments.finance.department_id",
"tags": [],
"constraint": "PRIMARY_KEY",
"ordinalPosition": 1
},
{
"name": "budget_total_value",
"dataType": "NUMERIC",
"dataTypeDisplay": "numeric",
"description": "The department's budget for the current year.",
"fullyQualifiedName": "s3_object_store_sample.departments.finance.budget_total_value",
"tags": [],
"ordinalPosition": 2
},
{
"name": "notes",
"dataType": "VARCHAR",
"dataLength": 100,
"dataTypeDisplay": "varchar",
"description": "Notes concerning sustainability for the budget.",
"fullyQualifiedName": "s3_object_store_sample.departments.finance.notes",
"tags": [],
"ordinalPosition": 3
},
{
"name": "budget_executor",
"dataType": "VARCHAR",
"dataTypeDisplay": "varchar",
"description": "The responsible finance lead for the budget execution",
"fullyQualifiedName": "s3_object_store_sample.departments.finance.budget_executor",
"tags": [],
"ordinalPosition": 4
}
]
},
"prefix": "/departments/finance/",
"numberOfObjects": 75.0,
"size": 286720.0,
"fileFormats": [
"zip",
"csv"
],
"serviceType": "S3",
"deleted": false,
"tags": [],
"tier": null,
"followers": [],
"suggest": [
{
"input": "s3_object_store_sample.departments.finance",
"weight": 5
},
{
"input": "finance",
"weight": 10
}
],
"service_suggest": [
{
"input": "s3_object_store_sample",
"weight": 5
}
],
"column_suggest": [
{
"input": "department_id",
"weight": 5
},
{
"input": "budget_total_value",
"weight": 5
},
{
"input": "notes",
"weight": 5
},
{
"input": "budget_executor",
"weight": 5
}
],
"entityType": "container"
}
}
]
}
]
}
}

@aniketkatkar97 the suggest keywords are used to retrieve a document that matches the keywords in suggest. It won't give you 2 different documents as the Box Chart, Boy Name Cloud belongs to the same document. So either you search with "Box" or "Boy" they hit one source document which is the dashboard doc that contains both these charts. The response you are getting is correct.


NIFI-7320 Adding HDFS Content Repository implementation.

Thank you for submitting a contribution to Apache NiFi.
Please provide a short description of the PR here:
This PR provides an HDFS based content repository that uses the Hadoop FileSystem API to store FlowFile content.
Enables HDFS Content Repository implementation for NIFI-7320.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[x] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[x] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[x] Has your PR been rebased against the latest commit within the target branch (typically master)?

[x] Is your initial contribution a single, squashed commit? Additional commits in response to PR reviewer feedback should be made on this branch and pushed to allow change tracking. Do not squash or use --force when pushing to allow for clean monitoring of changes.

For code changes:

[x] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[X] Have you written or updated unit tests to verify your changes?
[x] Have you verified that the full build is successful on both JDK 8 and JDK 11?
[x] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[x] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[x] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[x] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[x] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.

I advise the following path:

Create a separate github repo for this nar and provide instructions on how someone could place this into their nifi installation and instructions on how to get started.
The kerberos stuff is a very big deal for this to be used for anything production related.  This means considerations on how to configure, ensure renewals, etc.. all matters.  A lot of effort has gone into the various Hadoop related processors for this.
Conduct significant/tests on real HDFS clusters to provide information on performance observed and use cases utilized.  There are significant reasons why we've not pursued this previously. While there could be interesting results they need to exist before we're talking about merging this into the codebase.

Clearly considerable effort has gone into this PR.  But a lot more will be required both by you as a contributor and the community as reviewers. The above path allows that to happen but it will take time.


fixes ceph_stable_release logic mentioned in issue #446

fixes ceph_stable_release logic mentioned in issue #446
I changed the argument used for starting the mds server. (pre
infernalis)
service ceph start mds

errors, while
service ceph start mds.$hostname

correctly starts the service.
I also changed the mds directory ownership from ceph:cephh to root:root
again, for pre-infernalis.
And finally, add the ceph_stable_releases checks for the upstart
activation task `for or after infernalis release'.

@nexecook thanks for the fix, I'd like to enhance the logic a bit more could you please do the following as well?
In roles/ceph-mon/defaults/main.yml:
###################
# Stable Releases #
###################
ceph_stable_releases:
  - dumpling
  - emperor
  - firefly
  - giant
  - hammer

And then do: ceph_stable_release not in ceph_stable_releases or ceph_stable_release not in ceph_stable_releases when appropriate?

What should be added to group_vars, that array? (I am not very familiar with ansible)

@nexecook group_vars/all must have the exact same content as roles/ceph-common/defaults/main.yml.

I don't have anything to test at the moment, will have a look soon.

@nexecook tested and validated on both Hammer and Infernalis, thanks!


Shader help

Describe your problem here.
I tried to use Shader by frag file referring to this >> #11067, https://gamebanana.com/tuts/15316
but couldn't. Error appeared.
Error is ERROR (onCreatePost): assets/data/souls/script.lua:12: attempt to call global 'initLuaShader' (a nil value) and ERROR (onUpdate): assets/data/souls/script.lua:28: attempt to call global 'setShaderFloat' (a nil value)
code used is
function onCreatePost()
	luaDebugMode = true
	initLuaShader("glitch")

	makeLuaSprite("shaderImage")
	makeGraphic("shaderImage", screenWidth, screenHeight)

	setSpriteShader("shaderImage", "glitch")

	addHaxeLibrary("ShaderFilter", "openfl.filters")
	runHaxeCode([[
		trace(ShaderFilter);
		game.camGame.setFilters([new ShaderFilter(game.getLuaObject("shaderImage").shader)]);
		game.camHUD.setFilters([new ShaderFilter(game.getLuaObject("shaderImage").shader)]);
	]])
end

function onUpdate(elapsed)
	setShaderFloat("shaderImage", "iTime", os.clock())
end

Please help me about this
Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
winning icons in PlayState.hx.

show shader code

are you sure you have a build with shaders implemented?

are you sure you have a build with shaders implemented?

Hmm... Maybe no

Error is ERROR (onCreatePost): assets/data/souls/script.lua:12: attempt to call global 'initLuaShader' (a nil value) and ERROR (onUpdate): assets/data/souls/script.lua:28: attempt to call global 'setShaderFloat' (a nil value)

This was fixed, but another error appeared
undefined

This problem solved


Ability to deploy per-server plugins

In commit d4e9527 I added the ability to copy plugins to servers, it'd be good if we could have a global plugin directory and a per-server install.

I've already got the code for this, I just need to twig it a little and commit it


No module named 'timm'

I'm running my ComfyUI on Google CoLab.  I'm trying to run through the comfyui_controlnet_aux test_cn_aux_full.json This is the test with all the variations. I'm getting four errors all named 'timm'
Error occurred when executing SAMPreprocessor:
No module named 'timm'
https://pastebin.com/UHd3Dq6Z
Error occurred when executing Zoe-DepthMapPreprocessor:
No module named 'timm'
https://pastebin.com/KqM5bK6u
Error occurred when executing MiDaS-NormalMapPreprocessor:
No module named 'timm'
https://pastebin.com/V6aWDtth
Error occurred when executing MiDaS-DepthMapPreprocessor:
No module named 'timm'
https://pastebin.com/8Nnf4NX6
Also, I'm getting two errors named 'fvcore'
Error occurred when executing OneFormer-COCO-SemSegPreprocessor:
No module named 'fvcore'
https://pastebin.com/iLpnCP8G
Error occurred when executing OneFormer-ADE20K-SemSegPreprocessor:
No module named 'fvcore'
https://pastebin.com/teJcyQJT
And one
Error occurred when executing FakeScribblePreprocessor:
name 'HEDdetector' is not defined
https://pastebin.com/JnFP0LxF
Hope this helps.

Also Google Colab user here. I also got "timm issue". Reinstalling [ComfyUI's ControlNet Auxiliary Preprocessors] and then restarting the colab runtime everything works fine. However when deleting the runtime and starting the colab up agian give the "timm" error message again. Running !pip install timm leads to the following error
Error occurred when executing Zoe-DepthMapPreprocessor:
Error(s) in loading state_dict for ZoeDepth:
Unexpected key(s) in state_dict: "core.core.pretrained.model.blocks.0.attn.relative_position_index", "core.core.pretrained.model.blocks.1.attn.relative_position_index", "core.core.pretrained.model.blocks.2.attn.relative_position_index", "core.core.pretrained.model.blocks.3.attn.relative_position_index", "core.core.pretrained.model.blocks.4.attn.relative_position_index", "core.core.pretrained.model.blocks.5.attn.relative_position_index", "core.core.pretrained.model.blocks.6.attn.relative_position_index", "core.core.pretrained.model.blocks.7.attn.relative_position_index", "core.core.pretrained.model.blocks.8.attn.relative_position_index", "core.core.pretrained.model.blocks.9.attn.relative_position_index", "core.core.pretrained.model.blocks.10.attn.relative_position_index", "core.core.pretrained.model.blocks.11.attn.relative_position_index", "core.core.pretrained.model.blocks.12.attn.relative_position_index", "core.core.pretrained.model.blocks.13.attn.relative_position_index", "core.core.pretrained.model.blocks.14.attn.relative_position_index", "core.core.pretrained.model.blocks.15.attn.relative_position_index", "core.core.pretrained.model.blocks.16.attn.relative_position_index", "core.core.pretrained.model.blocks.17.attn.relative_position_index", "core.core.pretrained.model.blocks.18.attn.relative_position_index", "core.core.pretrained.model.blocks.19.attn.relative_position_index", "core.core.pretrained.model.blocks.20.attn.relative_position_index", "core.core.pretrained.model.blocks.21.attn.relative_position_index", "core.core.pretrained.model.blocks.22.attn.relative_position_index", "core.core.pretrained.model.blocks.23.attn.relative_position_index".
File "/content/drive/MyDrive/ComfyUI/execution.py", line 151, in recursive_execute
output_data, output_ui = get_output_data(obj, input_data_all)
File "/content/drive/MyDrive/ComfyUI/execution.py", line 81, in get_output_data
return_values = map_node_over_list(obj, input_data_all, obj.FUNCTION, allow_interrupt=True)
File "/content/drive/MyDrive/ComfyUI/execution.py", line 74, in map_node_over_list
results.append(getattr(obj, func)(**slice_dict(input_data_all, i)))
File "/content/drive/MyDrive/ComfyUI/custom_nodes/comfyui_controlnet_aux/node_wrappers/zoe.py", line 18, in execute
model = ZoeDetector.from_pretrained(HF_MODEL_NAME, cache_dir=annotator_ckpts_path).to(model_management.get_torch_device())
File "/content/drive/MyDrive/ComfyUI/custom_nodes/comfyui_controlnet_aux/src/controlnet_aux/zoe/init.py", line 30, in from_pretrained
model.load_state_dict(torch.load(model_path, map_location=torch.device('cpu'))['model'])
File "/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py", line 2041, in load_state_dict
raise RuntimeError('Error(s) in loading state_dict for {}:\n\t{}'.format(

I am sorry but is there any solution I can try to fix this?

I'm getting this tonight based off of a just downloaded version of Comfy Windows Portable. My workflow previously worked, but getting this same issue now.

Fixed in https://github.com/Fannovel16/comfyui_controlnet_aux/commit/6ee6d0998926832141063f0c947bc2c1495eda7c. Reinstall/update the extension should fix it


Is there a set of milestones needed to get the Exercism Haxe track to an active release?

I've been getting into Haxe recently and I love Exercism. I'd love to see an official Haxe track.
This repo has gone almost a full year with no commits/updates.
Reading through issues, I can't get a good feel for what is still remaining to be done. There are no GitHub milestones and of the 10 currently open issues, none of them are assigned to anyone. They're mostly discussion items.
I'm willing to help plan/implement whatever I can. I'm still a Haxe noob but a decent project manager and general developer.
What can we do to get this track active?
cc @kytrinyx

Congrats  - you're now a Haxe Maintainer :) Thanks!
You have an invite to the Org and to manage this repo. If you email me at<EMAIL_ADDRESS>- I'll get you invited to our Slack and our other maintainers can talk you through how to get started :)

Done. ✉ 👍


en, zh: add multi_level_url metadata

What is changed, added or deleted? (Required)

Which TiDB Data Migration (DM) version(s) do your changes apply to? (Required)

[x] master (the latest development version, including v2.0 changes for now)
[x] v1.0 (TiDB DM 1.0 versions)

What is the related PR or file link(s)?

This PR is translated from:
Other reference link(s):

@TomShawn @ran-huang @toutdesuite FYI.


fix syntax

fixes #7

For real is many years that i do not update this project.
Do you really use it?
uwsgi seems dead


#[diagnostic(transparent)] for passthrough diagnostics

actuallly I don't think we need this, if we have #[error(transparent)] already...


Videos not responsive

The videos on each page need to be made to be responsive so they don't run off of small screens.

Added @media query. Video player now responsive.


Is it possible to limit the number of icons included in the build?

Currently it looks like all the svg icons are included in the build, which greatly increases the build time.
Is there a way to specify which icons are included? I only need a couple of countries

Not currently, but your welcome to submit a PR with an option to do this.


Add documentation about custom themes

I have added documentation for https://github.com/sigoden/aichat/pull/187

Custom theme is an advanced unstable feature. Not recommended for ordinary users.
thank you for your contribution


[TODO] Move AM_MIDI2 reference to vcpkg

This is required before we can ingest into insider or retail Windows builds

Done. PR'd to main today


Support download Edge add-ons natively

It'd be nice if Kiwi could natively download extensions from Edge Add-ons, as some of the extension is missing from Chrome Web Store.
A simple user-agent trick like Opera does, not seems applicable here.
Eg link; https://microsoftedge.microsoft.com/addons/detail/universal-bypass/ckiidekccfgninkobmmofopbbdgdclgg
This issue was referenced in kiwibrowser/src#145

Small update on this one, due to a change in upstream chromium, the current implementation of downloading Edge extensions directly from edge store doesn't work anymore (the download gets blocked due to mixed content no longer being allowed in chromium).
Until a workaround gets implemented in Kiwi, you can use this extension as a workaround, and use the Download Link option from the hold menu.

Update: workaround above merged onto upstream with https://github.com/kiwibrowser/src.next/pull/285. Should be on next release!

That feature is in Kiwi , is not perfect but is a great solution implemented by @Delphox


I want to Continue this Project Development.

Some People like it, So I want to Continue it
OK?

If you fork it, let us know. As a user I'd love to see this project stay alive.

Yes, I fork it . on OSChina Git,(Because Github is slow speed in China.)
https://git.oschina.net/wbsdty331/Tikione-Steam-Cleaner-Plus/
Right?

Good news.
If you need assistance, don't hesitate to ask questions about code or configuration.
Regards,

https://github.com/wbsdty331/TikiOne-steam-Cleaner-Plus
This, I added some new feature.
Welcome fork


ss-local + v2ray-plugin errror: failed to start server: v2ray.com/core/app/proxyman/inbound

failed to start server: v2ray.com/core/app/proxyman/inbound: failed to listen TCP on 8530 > v2ray.com/core/transport/internet: failed to listen on address: : > v2ray.com/core/transport/internet/websocket: failed to listen TCP on : > listen tcp  :: bind: cannot assign requested address

What's your plugin-opts ?

What's your plugin-opts ?

Thanks for your hits. I've just checked my plugin-opts and found out that I misused service side config: "plugin-opts":"server; xxx". After I changed the plugin-opts, everything works fine.

Thanks a lot! @kaslr


share prepared metadata between connections

#824 followup

Will we need to use the other fields of PreparedMetadata for anything later on?
If we can reduce it to just pk_indexes then we can reduce the amount of time that we spend holding the read lock.

Not sure off the top of my head, I'll add that to the followups for token aware.


[FIX-4034][server] fix sqoop import fail

What is the purpose of the pull request
fix #4034 sqoop query import fail and optimize hard code & code style
Brief change log

Add SqoopConstants class to store sqoop task constants
Remove hard code in sqoop task
modify sqoop query '$CONDITIONS' params

Verify this pull request
This change added tests and can be verified as follows:

DS-worker-server/test/sqoop/SqoopTaskTest

Codecov Report

Merging #4036 (e23b1c1) into dev (2830ab1) will increase coverage by 0.12%.
The diff coverage is 57.00%.

@@             Coverage Diff              @@
##                dev    #4036      +/-   ##
============================================
+ Coverage     39.81%   39.94%   +0.12%
- Complexity     2939     2943       +4
============================================
  Files           459      459
  Lines         21722    21736      +14
  Branches       2647     2648       +1
============================================
+ Hits           8649     8682      +33
+ Misses        12273    12249      -24
- Partials        800      805       +5

Impacted Files
Coverage Δ
Complexity Δ

...pache/dolphinscheduler/common/enums/QueryType.java
0.00% <0.00%> (ø)
0.00 <0.00> (ø)

...duler/server/worker/task/sqoop/SqoopConstants.java
0.00% <0.00%> (ø)
0.00 <0.00> (?)

...nscheduler/server/worker/task/sqoop/SqoopTask.java
32.00% <15.38%> (-2.79%)
3.00 <1.00> (ø)

...k/sqoop/generator/targets/HiveTargetGenerator.java
56.25% <51.72%> (-1.82%)
2.00 <1.00> (ø)

.../sqoop/generator/sources/MysqlSourceGenerator.java
57.69% <53.48%> (-0.31%)
5.00 <4.00> (ø)

...k/sqoop/generator/targets/HdfsTargetGenerator.java
59.25% <54.16%> (+2.73%)
2.00 <1.00> (ø)

...k/sqoop/generator/sources/HdfsSourceGenerator.java
64.28% <54.54%> (ø)
2.00 <1.00> (ø)

...k/sqoop/generator/sources/HiveSourceGenerator.java
68.18% <63.15%> (+7.07%)
2.00 <1.00> (ø)

...worker/task/sqoop/generator/SqoopJobGenerator.java
74.07% <66.66%> (ø)
10.00 <7.00> (ø)

.../sqoop/generator/targets/MysqlTargetGenerator.java
71.42% <67.56%> (-4.33%)
4.00 <3.00> (ø)

... and 19 more

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 2830ab1...e23b1c1. Read the comment docs.

Overall, there seems to be no problem.
But there are two suggestions:
1: In the parameter construction, I think there is no need to use linkedList, the original StringBuilder may be better.
2: It is recommended not to use values in the enum. The recommended approach is to put the enumeration value in a static constant.

1 The purpose of using linkedlist is not to splice a large number of spaces in stringbuilder
2 the enum value in a static constant seems a good idea

Overall, there seems to be no problem.
But there are two suggestions:
1: In the parameter construction, I think there is no need to use linkedList, the original StringBuilder may be better.
2: It is recommended not to use values in the enum. The recommended approach is to put the enumeration value in a static constant.

1 The purpose of using linkedlist is not to splice a large number of spaces in stringbuilder
2 the enum value in a static constant seems a good idea

I understand what you mean, you first use LinkedList, and finally use StringUtils.join(StringBuilder). In my opinion, it is better to use StringBuilder directly, which is more efficient. What do you think.

Overall, there seems to be no problem.
But there are two suggestions:
1: In the parameter construction, I think there is no need to use linkedList, the original StringBuilder may be better.
2: It is recommended not to use values in the enum. The recommended approach is to put the enumeration value in a static constant.

1 The purpose of using linkedlist is not to splice a large number of spaces in stringbuilder
2 the enum value in a static constant seems a good idea

I understand what you mean, you first use LinkedList, and finally use StringUtils.join(StringBuilder). In my opinion, it is better to use StringBuilder directly, which is more efficient. What do you think.

Yes, in terms of efficiency, stringbuilder is more efficient than StringUtils.join.  I will remove linkedList and use StringBuilder


Calico upgrade from Kubernetes 1.7 to 1.8 - fails to start due to TPR

Upgraded a cluster creates using bootkube 0.6.1 using the flag --experimental-calico-network-policy
After following the upgrade documentation Calico still fails to start.
kubectl logs kube-calico-srjbt -n kube-system -c kube-calico

Checking datastore connection
Datastore connection verified
IPv4 address <IP_ADDRESS> discovered on interface enp3s0
No AS number configured on node resource, using global value
time="2017-09-29T13:42:45Z" level=error msg="Hit error initializing TPR" error="resource does not exist: {{ } {system-network-policy.alpha.projectcalico.org  kube-system    %!s(int64=0) 0001-01-01 00:00:00 +0000 UTC <nil> %!s(*int64=<nil>) map[] map[] [] [] } Calico System Network Policies [{v1}]}"
time="2017-09-29T13:42:45Z" level=error msg="Hit error initializing TPR" error="resource does not exist: {{ } {global-config.projectcalico.org  kube-system    %!s(int64=0) 0001-01-01 00:00:00 +0000 UTC <nil> %!s(*int64=<nil>) map[] map[] [] [] } Calico Global Configuration [{v1}]}"
time="2017-09-29T13:42:45Z" level=error msg="Hit error initializing TPR" error="resource does not exist: {{ } {ip-pool.projectcalico.org  kube-system    %!s(int64=0) 0001-01-01 00:00:00 +0000 UTC <nil> %!s(*int64=<nil>) map[] map[] [] [] } Calico IP Pools [{v1}]}"
time="2017-09-29T13:42:45Z" level=error msg="Hit error initializing TPR" error="resource does not exist: {{ } {global-bgp-peer.projectcalico.org  kube-system    %!s(int64=0) 0001-01-01 00:00:00 +0000 UTC <nil> %!s(*int64=<nil>) map[] map[] [] [] } Calico Global BGP Peers [{v1}]}"
time="2017-09-29T13:42:45Z" level=error msg="Hit error initializing TPR" error="resource does not exist: {{ } {global-bgp-config.projectcalico.org  kube-system    %!s(int64=0) 0001-01-01 00:00:00 +0000 UTC <nil> %!s(*int64=<nil>) map[] map[] [] [] } Calico Global BGP Configuration [{v1}]}"
ERROR: Unable to set node resource configuration: Failed to ensure ThirdPartyResources exist: resource does not exist: {{ } {global-bgp-config.projectcalico.org  kube-system    %!s(int64=0) 0001-01-01 00:00:00 +0000 UTC <nil> %!s(*int64=<nil>) map[] map[] [] [] } Calico Global BGP Configuration [{v1}]}
Terminating
Calico node failed to start

I just did this today, so currently the render produces calico with 2.4 which uses TPR, you will need the calico 2.5, which moved to CRD its available in #694 to get it to work. TPR was deprecated in 1.8.

Perhaps of interest:

Refreshed bootkube upgrade guide - Mentions preparing the diff between assets produced by bootkube at the original version and target version (yes, there is no release with 1.8 yet). In your case, the diff between 0.6.1 and latest has the TPR -> CRD change you can attempt to apply.
Next bootkube release will move --experimental-calico-network-policy to --network-provider=canal. There are also some warning about this configuration. See #723

Thanks for fixing the link @aaronlevy

Did this help with your issue? bootkube itself has switched to using CRDs and works properly. I don't know that there is an issue to be solved in this repo since upstream has documented the way to attempt an in-place migration.

Calico should be working as expected on v1.8.1. If you encounter issues in a fresh setup, can you open an issue?

@dghubble this did not work for me.
However my upgrade tests worked with 1.8.1 using --network-provider=flannel.

As in, a fresh v1.8.1 cluster (bootkube v0.8.0) did not work for you or trying to migrate in-place?


Add support for checking folders

Thanks for this useful project! What do you think about adding support for folders when using the nerdfix check / nerdfix fix commands in which case the command would be applied to all the files in the directory recursively? This would allow something like nerdfix check ~/.local/share/nvim to check all Nvim configuration files.

I added --recursive in #6, but it's recommended to use nerdfix check $(fd -t f . ~/.local/share/nvim) to exclude some hidden directories (like .git, which contains many binary files and causes many non-UTF-8 errors).