Using fiotest as a production test tool

Hi all,
So I've been working with fiotest for a while now as you know and obviously it's great!
Our use case - production & QA testing of hardware - might not be exactly what the majority of other users are doing but I think it's valid and would be useful to other board manufacturers so I wondered if I can bounce some thoughts and questions off here...

I don't see any way with Foundries container management that I can disable a container programmatically. I think in terms of resource utilisation it would be helpful if I could run up a container and then at the end of that run use something to cause the container daemon to disable it. This way we could create images with a production test container that doesn't then run in the field. Is this possible and if not do you think it's worth supporting?

Aside from the above, as the test container is currently always running whenever I update the image the tests re-run which isn't what I want to happen. For example I need to program the flash in some ICs and I only want to do this once. Currently I just touch a state file to check if I've done things and if it exists I skip running the test but it is a bit messy.

Further to this with our production testing I want to inform the technician what's happening which I'm thinking of doing via audio messages. Clearly I don't want to play audio messages in the field so again I need some way of managing this. I like the idea of individual tests in the test-spec.yml and those being reported to the cloud so I don't want to bundle everything into a single script as one test, which feels like I wouldn't be making good use of the fiotest tooling. But if I keep things separate then in each test block I have to check for a state file and create it and so forth which again is messy.

So that leads me to wonder if there should be some kind of state where we only run tests 2, 3, 4 etc. on a conditional basis. So I could check if production testing had run on test 1 and then PASS without continuing on if that makes sense.

I am not sure I am expressing this clearly but I think this is a pretty reasonable use case here and I wondered if you have thoughts and/or advice?
I am also reminded of the saying that any application that reaches a certain level of complexity will end up with a scripting language embedded into it :-D
Cheers,
Alex

on container management: It sort of depends what you mean. Just pure "docker" container mgmt is possible by bind mounting the docker socket into a container. I think you are really asking about managing compose apps through our update system. One way you can manage this locally is via etc overrides for the aktualizr-lite sota.toml. Files are evaluated under /etc/sota/conf.d in order, so you could make a local file like:
# z-99-fiotest-override.yml (can override z-50-fioctl.toml)
[pacman]
compose_apps = "normal,list,plus,fiotest"

Then when fiotest completes, it could delete this file and then either restart aktualizr-lite or just stop the app depending on your use-case.
As per test-spec enhancements. I'm open to PRs if you have some  generically useful idea.

ok that's really interesting thanks. yes I I might take that approach then. I don't think for a production test I need to be changing this often, just as the last step of the test so the fiotest container doesn't run again. Thanks! (will close this)


Issue with Lab: Setting Up and Running Functional Tests Student lab manual while creating template

#Module 11: Implementing Continuous Deployment using Azure Pipelines
Lab/Demo: Lab: Setting Up and Running Functional Tests
Task: 2
Step: 1 to 4
Description of issue
Issue with Lab: Setting Up and Running Functional Tests Student lab manual while creating template.
In exercise 0, Task2:Create Azure resources, Step 4. Review + Create with the given details throwing error. The custom deployment is failing and unable to process further with the rest of the lab.
Below is the error message:
{"code":"InvalidContentLink","message":"Unable to download deployment content from 'https://gallery.azure.com/artifact/20161101/Microsoft.CustomScriptExtension-arm.2.0.50/Artifacts/MainTemplate.json'. The tracking Id is '2927f399-cd2e-476c-b4ac-992ff7f5be7d'. Please see https://aka.ms/arm-deploy for usage details."}
Repro steps:

Logged into lab.
After creating project, move to Step1 of Task2 in Exercise0. When we click the deploy to Azure button, it opens a custom deploy template in a new window outside the lab machine.
After filling the required details, when we click review+finish> Validation Fails with errors.
ERROR TYPE
Unable to download deployment content from 'https://gallery.azure.com/artifact/20161101/Microsoft.CustomScriptExtension-arm.2.0.50/Artifacts/MainTemplate.json'. The tracking Id is '2927f399-cd2e-476c-b4ac-992ff7f5be7d'. Please see https://aka.ms/arm-deploy for usage details. (Code: InvalidContentLink)

see https://github.com/microsoft/azuredevopslabs/issues/518

I just ran a test of this lab, and the link to issue referenced by ianclark500 appears to have borne fruit:  The template deploy was successful!  (looks like they updated w/fix ~15 days ago)   ...assuming others test this out and concur, I think this issue here can be closed.

Resolved


Phrasing and non-normative changes to Substitution.

Use "output" consistently instead of a mix of that and "result." This
is also more consistent with "input."
Mention another case in which we're likely to require that checkers
implement the all-worlds version of a rule.

Mention another case in which we're likely to require that checkers implement the all-worlds version of a rule.

I just wanted to write down here that I expect that the all-worlds version of a rule might well also end up required during type inference—not that we have done any meaningful work toward understanding how type inference will work, let alone specifying it :)


Auto-numbered lists in messages: add documentation and ignore code blocks

Uses a way of checking if a line is inside a code block similar to the preprocessor that handles hanging lists (bulleted lists directly after a paragraph with no blank line between them), so those that are don't get changed.
(edit): Renumbering is moved to paragraph blockprocessor (Bugdown) and after block-level lexer (marked.js) so that it runs only on paragraphs. This also means processed text doesn't have indentation, so iterating over lines is simplified.
Adds a mention of the feature and a screenshot in user docs and an example in the "Message formating" help window.
Fixes #8246

@timabbott I didn't think of an in-between solution like that. Thank you for pointing it out. So if I understand correctly, the way this should work is to substitute the paragraph block processor and run the main part of what is now the preprocessor on the text content? Also, paragraphs that are inside a <blockquote> may need to be excluded.

Updated, summary in the description.

In order to allow lists spanning multiple paragraphs, the processor is moved to a further point after the element tree is constructed. On both sides the way it works is to find an unbroken sequence of <p>'s, split them all into lines, run renumbering on these and join them back into paragraphs.

This issue was completed in https://github.com/zulip/zulip/commit/1f52eea0e48ee1eaeb6c0c2e92689f2969b1102d.


How to create a Button to go to an URL?

I've been trying to add some interface elements, but until now I was only able to create the buttons with the payload method, like this:
  utter_equipamentos_estacoes_emprestimo:
    - text: |
        ótimo!
        você pode solicitar empréstimos de equipamentos por
        `Curta`(até 7 dias),
        `Média` (até 3 meses) ou
        `Longa` (mais que 3 meses) duração.

      buttons:
        - title: "Curta"
          payload: "/equipamentos_estacoes_emprestimo_curta"
        - title: "Média"
          payload: "/equipamentos_estacoes_emprestimo_media"
        - title: "Longa"
          payload: "/equipamentos_estacoes_emprestimo_longa"

this button will send back an intent to rasa core, which is pretty cool for navigation purposes.
But now I need to send buttons to visit an URL, to make the browser got to a new location.
I've trie this facebook notation:
        "buttons":[
          {
            "type":"web_url",
            "url":"https://www.messenger.com/",
            "title":"URL Button",
            "webview_height_ratio": "full"
          }
        ]

and it just didn't rendered the code.
Tried this approach also:
  utter_equipamentos_estacoes_devolucao:
    - text: |
          response text...
      attachment:
        type: "template"
        payload:
          template_type: "generic"
          elements:
            - title: "escolha"
              buttons:
                - title: "Open URL 1"
                  url: "http://...."
                - title: "Open URL 2"
                  url: "http://..."

and this printed a second message with Attachment:....code the code in json format inside as text response.
Any ideas on how to implement these elements using the utterances of domain.yaml?

no one? no way?

Hey @diegodorgam at this time the webchat only supports quick replies.


Plans to support node above v0.8 ?

jss wasn't working for me, when I attempted to update it I noticed this:
npm WARN engine<EMAIL_ADDRESS>wanted: {"node":"0.8.0"} (current: {"node":"0.10.33","npm":"2.4.1"})
Are there plans to support node above v0.8 sometime soon? I'm using something else to achieve the same goal at the moment, but I would prefer to use jss, I like how it works.

Fastest reply ever. Thanks !!

Not published to NPM yet. Still having same warning for<EMAIL_ADDRESS>

published.

:cocktail: :tropical_drink:


Appstudio update test-custom-default-branch-apwp

Pipelines as Code configuration proposal
To start the PipelineRun, add a new comment with content /ok-to-test
For more detailed information about running a PipelineRun, please refer to Pipelines as Code documentation Running the PipelineRun
To customize the proposed PipelineRuns after merge, please refer to Build Pipeline customization

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-nyrh-on-pull-request-
creating pipelinerun test-simple-build-nyrh-on-pull-request- in namespace build-e2e-odki-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-mcmm-on-pull-request-
creating pipelinerun test-simple-build-mcmm-on-pull-request- in namespace build-e2e-tuus-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-yrqk-on-pull-request-
creating pipelinerun test-annotations-yrqk-on-pull-request- in namespace build-e2e-odki-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-ufgi-on-pull-request-
creating pipelinerun test-simple-build-ufgi-on-pull-request- in namespace build-e2e-tuus-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-lqle-on-pull-request-
creating pipelinerun test-simple-build-lqle-on-pull-request- in namespace build-e2e-tuus-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-nwtb-on-pull-request-
creating pipelinerun test-simple-build-nwtb-on-pull-request- in namespace build-e2e-odki-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-imul-on-pull-request-
creating pipelinerun test-simple-build-imul-on-pull-request- in namespace build-e2e-odki-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-lqle-on-pull-request-
creating pipelinerun test-simple-build-lqle-on-pull-request- in namespace build-e2e-odki-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-nyrh-on-pull-request-
creating pipelinerun test-simple-build-nyrh-on-pull-request- in namespace build-e2e-tuus-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-mijr-on-pull-request-
creating pipelinerun test-annotations-mijr-on-pull-request- in namespace build-e2e-odki-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-yrqk-on-pull-request-
creating pipelinerun test-annotations-yrqk-on-pull-request- in namespace build-e2e-tuus-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-custom-default-branch-apwp-on-pull-request-
creating pipelinerun test-custom-default-branch-apwp-on-pull-request- in namespace build-e2e-tuus-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-mcmm-on-pull-request-
creating pipelinerun test-simple-build-mcmm-on-pull-request- in namespace build-e2e-odki-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-ufgi-on-pull-request-
creating pipelinerun test-simple-build-ufgi-on-pull-request- in namespace build-e2e-odki-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-nwtb-on-pull-request-
creating pipelinerun test-simple-build-nwtb-on-pull-request- in namespace build-e2e-tuus-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-wadk-on-pull-request-
creating pipelinerun test-simple-build-wadk-on-pull-request- in namespace build-e2e-tuus-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-mijr-on-pull-request-
creating pipelinerun test-annotations-mijr-on-pull-request- in namespace build-e2e-tuus-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-uqzm-on-pull-request-
creating pipelinerun test-simple-build-uqzm-on-pull-request- in namespace build-e2e-odki-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-imul-on-pull-request-
creating pipelinerun test-simple-build-imul-on-pull-request- in namespace build-e2e-tuus-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-wadk-on-pull-request-
creating pipelinerun test-simple-build-wadk-on-pull-request- in namespace build-e2e-odki-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request


Add permissions to script publishing the release #165

Description
Add required permissions to publish_release.sh and release.sh
Related issue(s)
https://github.com/kyma-project/keda-manager/issues/129

LGTM


Add additional improvements to the README

Modeled off of bitoiu/letsencrypt-manual-hook#1, this pull request will:

[x] Document what flags are used by the dehydrated client in the example
[x] Document the difference between subdomain aliases
[x] Show example of the completed certificate (from the CLI)

@bitoiu I'll get you to do a Review on this once complete

@bitoiu, I'm done with my edits here (finally), let me know if you'd like to review them at your leisure.

I'll take a detailed look soon enough :bow:

no rush with that async life @bitoiu . Thanks for the 👀


[BUG] seems like that analyzer_ip does not support domain name

Search before asking

[X] I had searched in the issues and found no similar feature requirement.

DeepFlow Component
Agent
What you expected to happen
Perform DNS when analyzer_ip is configured as domain name
How to reproduce
I found an associated PR in issues.
but seem to have encountered some problems; when I configure analyzer_ip as the domain name in custom_agent_group_config.yaml, I get the following error:

DeepFlow version
kubectl exec -it -n deepflow deploy/deepflow-server -- deepflow-server -v:
Name: deepflow-server community edition
Branch: master
CommitID: fac7d6c9be2cd70b5f357a5e865e01887acc1b39
RevCount: 8412
Compiler: go version go1.18.3 linux/amd64
CompileTime: 2023-06-19 10:00:59

kubectl exec -it -n deepflow ds/deepflow-agent -- deepflow-agent -v:
Name: deepflow-agent community edition
Branch: master
CommitId: 0d2afa85640cee43c5c1e88e8bc061c8faad083b
RevCount: 8219
Compiler: rustc 1.69.0 (84c898d65 2023-04-16)
CompileTime: 2023-05-05 04:59:06

DeepFlow agent list
deepflow-ctl agent list:
68       ip-192-168-100-123.ap-northeast-1.compute.internal-V95   K8S_VM     <IP_ADDRESS>    0e:c6:4e:b5:87:6b  NORMAL    ANALYZER_SOCKET_ERROR

Kubernetes CNI
aws-vpc-cni
Operation-System/Kernel version
awk -F '=' '/PRETTY_NAME/ { print $2 }' /etc/os-release:
"Ubuntu 22.04.2 LTS"

uname -r:
5.4.209-116.363.amzn2.x86_64

Anything else
I configured controller-ips as domain name in deepflow-agent.yaml and it works, but analyzer fails with following error:
[2023-06-19 21:02:22.044939 +08:00] ERROR [src/sender/uniform_sender.rs:395] stats sender tcp connection to <IP_ADDRESS>:30033 failed

So I tried to configure analyzer_ip as domain name in custom_agent_group_config.yaml controlled by deepflow-ctl
Please let me know if need any more information, thanks!
Are you willing to submit a PR?

[x] Yes I am willing to submit a PR!

Code of Conduct

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

https://github.com/deepflowio/deepflow/pull/3415
FIXED


Update the 500 alert to account copybara latency with postsubmit-luci-subscription processing

Is there an existing issue for this?

[X] I have searched the existing infra issues

Type of Request
infra task
Infrastructure Environment
Cocoon scheduler
What is happening?
Currently if copybara is latent we can receive 500 errors from trying to get the GoB commit and it not existing. A solution was added to check with retries but that caused an issue with pubsub and unacked messages as we were waiting beyond the ack deadline.
We should adjust the 500 Alert to add some buffer for expected 500 errors from the GoB check as we have no control over latency issues with Copybara and do not want to wait indefinitely for the commit to be copied over.
Steps to reproduce
NA
Expected results
NA

Did a quick analysis of the number of times we got a 500 error from this and here is the data for the week of 09/25/2023:

Day
Span Start
Span End
Recorded 500 Errors

Saturday
09/30/2023 08:00 AM
10/01/2023 08:00 AM
35

Friday
09/29/2023 08:00 AM
09/29/2023 08:00 AM
140

Thursday
09/28/2023 08:00 AM
09/29/2023 08:00 AM
137

Wednesday
09/27/2023 08:00 AM
09/28/2023 08:00 AM
132

Tuesday
09/26/20023 08:00 AM
09/27/2023 08:00 AM
65

Monday
09/25/2023 08:00 AM
09/26/2023 08:00 AM
4

Here is the 500 error data from that period:

This range is not a good indicator as we were having a multitude of issues with tasks not updating so I will collect data for this week and next.


Question: Can the size of the window be adjust post-recording?

I have recorded the same sequence of commands on different hosts.
This one looks great (apart from that missing emoji):

I would like to adjust the size of this window post-recording. Is that possible?

FTR:
agg --version
agg 1.2.0

uname -a
Linux x22 5.15.58 #1-NixOS SMP Fri Jul 29 15:25:34 UTC 2022 x86_64 GNU/Linux

agg --speed=2 --font-size=24 --theme=monokai dagger-install.cast dagger-install-loop.gif
gifsicle --no-loopcount dagger-install-loop.gif > dagger-install.gif

Thank you!

Attaching the original cast files as zip 👉 dagger-install-casts.zip

Yes, see here https://github.com/asciinema/agg/issues/11#issuecomment-1237238040
I guess it'd be useful to add options for terminal size override, something like --cols 80 --rows 24?

I guess it'd be useful to add options for terminal size override, something like --cols 80 --rows 24?

Yes, that would really help.
For now, I manually edited the first line in the cast file and it worked!

That answers my question, closing this issue - thank you! 🙌🏻

Just released v1.3 with new --cols / --rows options.


directory "/blah" is not using a known version control system

I just updated to the latest version (250fa9c4c6db3c0e91fe8d163f535583dcd25156), and I get this error when trying to create a new project:
$ go-bootstrap -dir github.com/davidscholberg/go-bootstrap-test -template core
2016/02/28 14:39:24 Creating /home/david/src/go/src/github.com/davidscholberg/go-bootstrap-test...
2016/02/28 14:39:24 Copying project template directory to /home/david/src/go/src/github.com/davidscholberg/go-bootstrap-test...
2016/02/28 14:39:24 Replacing placeholder variables on davidscholberg/go-bootstrap-test...
2016/02/28 14:39:24 Running go get -u ./...
2016/02/28 14:39:24 package github.com/davidscholberg/go-bootstrap-test: directory "/home/david/src/go/src/github.com/davidscholberg/go-bootstrap-test" is not using a known version control system
package github.com/davidscholberg/go-bootstrap-test/application: directory "/home/david/src/go/src/github.com/davidscholberg/go-bootstrap-test/application" is not using a known version control system
package github.com/davidscholberg/go-bootstrap-test/handlers: directory "/home/david/src/go/src/github.com/davidscholberg/go-bootstrap-test/handlers" is not using a known version control system
package github.com/davidscholberg/go-bootstrap-test/libhttp: directory "/home/david/src/go/src/github.com/davidscholberg/go-bootstrap-test/libhttp" is not using a known version control system
package github.com/davidscholberg/go-bootstrap-test/libstring: directory "/home/david/src/go/src/github.com/davidscholberg/go-bootstrap-test/libstring" is not using a known version control system
package github.com/davidscholberg/go-bootstrap-test/middlewares: directory "/home/david/src/go/src/github.com/davidscholberg/go-bootstrap-test/middlewares" is not using a known version control system

exit status 1

FYI, here's my go version:
$ go version
go version go1.6 linux/amd64

I reverted go-bootstrap to a47291855be16baec5f83002ce2a60cedb03a3c7 and got a little farther, but received another error:
$ go-bootstrap -dir github.com/davidscholberg/go-bootstrap-test -template core                                                                                [928/1790]
2016/02/28 14:55:19 Creating /home/david/src/go/src/github.com/davidscholberg/go-bootstrap-test...
2016/02/28 14:55:19 Copying project template directory to /home/david/src/go/src/github.com/davidscholberg/go-bootstrap-test...
2016/02/28 14:55:19 Replacing placeholder variables on davidscholberg/go-bootstrap-test...
2016/02/28 14:55:19 Running go get ./...
2016/02/28 14:55:21 Installing github.com/tools/godep...
2016/02/28 14:55:21 Running git init...
2016/02/28 14:55:21 Running godep save ./...
2016/02/28 14:55:22 Running godep go test ./...
2016/02/28 14:55:22 vendor/github.com/Sirupsen/logrus/examples/hook/hook.go:5:2: cannot find package "gopkg.in/gemnasium/logrus-airbrake-hook.v2" in any of:
        /home/david/src/go/src/github.com/davidscholberg/go-bootstrap-test/vendor/gopkg.in/gemnasium/logrus-airbrake-hook.v2 (vendor tree)
        /usr/lib/go/src/gopkg.in/gemnasium/logrus-airbrake-hook.v2 (from $GOROOT)
        /home/david/src/go/src/github.com/davidscholberg/go-bootstrap-test/Godeps/_workspace/src/gopkg.in/gemnasium/logrus-airbrake-hook.v2 (from $GOPATH)
        /home/david/src/go/src/gopkg.in/gemnasium/logrus-airbrake-hook.v2
vendor/github.com/carbocation/interpose/adaptors/negroni.go:6:2: cannot find package "github.com/codegangsta/negroni" in any of:
        /home/david/src/go/src/github.com/davidscholberg/go-bootstrap-test/vendor/github.com/codegangsta/negroni (vendor tree)
        /usr/lib/go/src/github.com/codegangsta/negroni (from $GOROOT)
        /home/david/src/go/src/github.com/davidscholberg/go-bootstrap-test/Godeps/_workspace/src/github.com/codegangsta/negroni (from $GOPATH)
        /home/david/src/go/src/github.com/codegangsta/negroni
vendor/github.com/carbocation/interpose/adaptors/martini.go:6:2: cannot find package "github.com/go-martini/martini" in any of:
        /home/david/src/go/src/github.com/davidscholberg/go-bootstrap-test/vendor/github.com/go-martini/martini (vendor tree)
        /usr/lib/go/src/github.com/go-martini/martini (from $GOROOT)
        /home/david/src/go/src/github.com/davidscholberg/go-bootstrap-test/Godeps/_workspace/src/github.com/go-martini/martini (from $GOPATH)
        /home/david/src/go/src/github.com/go-martini/martini
vendor/github.com/carbocation/interpose/examples/adaptors/logrus/main.go:12:2: cannot find package "github.com/meatballhat/negroni-logrus" in any of:
        /home/david/src/go/src/github.com/davidscholberg/go-bootstrap-test/vendor/github.com/meatballhat/negroni-logrus (vendor tree)
        /usr/lib/go/src/github.com/meatballhat/negroni-logrus (from $GOROOT)
        /home/david/src/go/src/github.com/davidscholberg/go-bootstrap-test/Godeps/_workspace/src/github.com/meatballhat/negroni-logrus (from $GOPATH)
        /home/david/src/go/src/github.com/meatballhat/negroni-logrus
vendor/github.com/carbocation/interpose/examples/adaptors/logrus/main.go:13:2: cannot find package "github.com/stretchr/graceful" in any of:
        /home/david/src/go/src/github.com/davidscholberg/go-bootstrap-test/vendor/github.com/stretchr/graceful (vendor tree)
        /usr/lib/go/src/github.com/stretchr/graceful (from $GOROOT)
        /home/david/src/go/src/github.com/davidscholberg/go-bootstrap-test/Godeps/_workspace/src/github.com/stretchr/graceful (from $GOPATH)
        /home/david/src/go/src/github.com/stretchr/graceful
vendor/github.com/carbocation/interpose/examples/adaptors/martiniauth/main.go:10:2: cannot find package "github.com/martini-contrib/auth" in any of:
        /home/david/src/go/src/github.com/davidscholberg/go-bootstrap-test/vendor/github.com/martini-contrib/auth (vendor tree)
        /usr/lib/go/src/github.com/martini-contrib/auth (from $GOROOT)
        /home/david/src/go/src/github.com/davidscholberg/go-bootstrap-test/Godeps/_workspace/src/github.com/martini-contrib/auth (from $GOPATH)
        /home/david/src/go/src/github.com/martini-contrib/auth
vendor/github.com/carbocation/interpose/middleware/gorillalog.go:7:2: cannot find package "github.com/carbocation/handlers" in any of:
        /home/david/src/go/src/github.com/davidscholberg/go-bootstrap-test/vendor/github.com/carbocation/handlers (vendor tree)
        /usr/lib/go/src/github.com/carbocation/handlers (from $GOROOT)
        /home/david/src/go/src/github.com/davidscholberg/go-bootstrap-test/Godeps/_workspace/src/github.com/carbocation/handlers (from $GOPATH)
        /home/david/src/go/src/github.com/carbocation/handlers
vendor/github.com/carbocation/interpose/middleware/buffer.go:6:2: cannot find package "github.com/goods/httpbuf" in any of:
        /home/david/src/go/src/github.com/davidscholberg/go-bootstrap-test/vendor/github.com/goods/httpbuf (vendor tree)
        /usr/lib/go/src/github.com/goods/httpbuf (from $GOROOT)
        /home/david/src/go/src/github.com/davidscholberg/go-bootstrap-test/Godeps/_workspace/src/github.com/goods/httpbuf (from $GOPATH)
        /home/david/src/go/src/github.com/goods/httpbuf
vendor/github.com/carbocation/interpose/middleware/nosurf.go:6:2: cannot find package "github.com/justinas/nosurf" in any of:
        /home/david/src/go/src/github.com/davidscholberg/go-bootstrap-test/vendor/github.com/justinas/nosurf (vendor tree)
        /usr/lib/go/src/github.com/justinas/nosurf (from $GOROOT)
        /home/david/src/go/src/github.com/davidscholberg/go-bootstrap-test/Godeps/_workspace/src/github.com/justinas/nosurf (from $GOPATH)
        /home/david/src/go/src/github.com/justinas/nosurf
vendor/github.com/carbocation/interpose/middleware/negronigzip.go:7:2: cannot find package "github.com/phyber/negroni-gzip/gzip" in any of:
        /home/david/src/go/src/github.com/davidscholberg/go-bootstrap-test/vendor/github.com/phyber/negroni-gzip/gzip (vendor tree)
        /usr/lib/go/src/github.com/phyber/negroni-gzip/gzip (from $GOROOT)
        /home/david/src/go/src/github.com/davidscholberg/go-bootstrap-test/Godeps/_workspace/src/github.com/phyber/negroni-gzip/gzip (from $GOPATH)
        /home/david/src/go/src/github.com/phyber/negroni-gzip/gzip
vendor/github.com/carbocation/interpose/examples/secure/main.go:11:2: cannot find package "github.com/unrolled/secure" in any of:
        /home/david/src/go/src/github.com/davidscholberg/go-bootstrap-test/vendor/github.com/unrolled/secure (vendor tree)
        /usr/lib/go/src/github.com/unrolled/secure (from $GOROOT)
        /home/david/src/go/src/github.com/davidscholberg/go-bootstrap-test/Godeps/_workspace/src/github.com/unrolled/secure (from $GOPATH)
        /home/david/src/go/src/github.com/unrolled/secure
vendor/github.com/kr/text/mc/mc.go:13:2: cannot find package "github.com/kr/pty" in any of:
        /home/david/src/go/src/github.com/davidscholberg/go-bootstrap-test/vendor/github.com/kr/pty (vendor tree)
        /usr/lib/go/src/github.com/kr/pty (from $GOROOT)
        /home/david/src/go/src/github.com/davidscholberg/go-bootstrap-test/Godeps/_workspace/src/github.com/kr/pty (from $GOPATH)
        /home/david/src/go/src/github.com/kr/pty
vendor/github.com/spf13/viper/remote/remote.go:12:2: cannot find package "github.com/xordataexchange/crypt/config" in any of:
        /home/david/src/go/src/github.com/davidscholberg/go-bootstrap-test/vendor/github.com/xordataexchange/crypt/config (vendor tree)
        /usr/lib/go/src/github.com/xordataexchange/crypt/config (from $GOROOT)
        /home/david/src/go/src/github.com/davidscholberg/go-bootstrap-test/Godeps/_workspace/src/github.com/xordataexchange/crypt/config (from $GOPATH)
        /home/david/src/go/src/github.com/xordataexchange/crypt/config
godep: go exit status 1

I was able to solve that error by setting the GO15VENDOREXPERIMENT environment variable to 0. So it looks like something is not working with the new vendor directory feature in Go 1.6.
This is, of course, a separate issue from the one I posted above, so I'll create a new issue for it if you want.

It does look like 2 different issues, but let's just solve them all here.

Your first problem is a legit bug, caused by a recent change: go get -u ./.... I have reverted that change.

It definitely looks like Godeps have some bugs transitioning to the new /vendor layout. I have decided to remove godeps for now since the community may switch to a different vendoring tool in the future.

Fixes: https://github.com/go-bootstrap/go-bootstrap/commit/6c2e50f0ae0ec0fd376b9cf49028eb0e0cca8555


Fix argument of MemoryCommit().

Fix argument of MemoryCommit() that is inconsistent within head and impl, which could cause build break on some platforms.

@twocode,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by Microsoft. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot

Hi @twocode!
The main reason that we devise a uint64_t argument here is to setting up our specification for memory management operations. size_t may vary for different platforms but GE always expect to manage memory with uint64_t. For example it would attempt to reserve a consecutive address space for all the memory trunks and with 32-bit argument this cannot be done.
But I think at least we shall raise compilation errors when our specification does not match what the system provides and the logic would fail. Possibly via static assertions (some work to be done in os/os.h).. What do you think?

Hi @yatli . I see. Then we should force header file to use uint64_t in parameter. The inconsistency of the two actually caused link error rather than compile error (on Mac).

@twocode you're right. Could you please update the header a bit? We can then proceed to merge this one.

I have push another commit. Please help to review:). @yatli

@yatli 👍


REF: Drop boltons dependency by using toolz (already a dep).

Description
Use toolz.partition instead of boltons.chunked.
Also, remove doct as a core dep (it's only use in bluesky.callbacks.broker) and matplotlib.
Motivation and Context
We don't need both toolz and boltons, and it seems more likely we'll want more things from toolz in the future. I also have the impression it's more widely used than boltons.
How Has This Been Tested?
There is good test coverage of the relevant sections of bluesky.

We can file this under, "Times when @klauer Was Out-Voted and Then Later Vindicated". We keep finding these....

Codecov Report

Merging #672 into master will increase coverage by 0.03%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #672      +/-   ##
==========================================
+ Coverage    82.6%   82.63%   +0.03%
==========================================
  Files          20       20
  Lines        4386     4395       +9
==========================================
+ Hits         3623     3632       +9
  Misses        763      763

Impacted Files
Coverage Δ

bluesky/spec_api.py
90.2% <100%> (+0.12%)
:arrow_up:

bluesky/plans.py
93.4% <100%> (+0.02%)
:arrow_up:

bluesky/plan_patterns.py
97.36% <100%> (+0.1%)
:arrow_up:

Continue to review full report at Codecov.

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


chore(main): release faro-shop 0.57.0

:robot: I have created a release beep boop
0.57.0 (2024-10-25)
Features

Bump app to 0.40.4 (#907) (7031b5c)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

faro-shop-0.57.0
:sunflower:


docs: add arrayAsync schema & ArraySchemaAsync type

Since this is my first PR related to the website, I have a few questions. Can you answer them?
Questions:

Variable names for async schemas in the examples: The naming rule followed is the same as Valibot's schema name rule. So if the example is related to an async schema of an object array, the name would be ObjectArraySchemaAsync instead of just ObjectArraySchema. Logically, it doesn't matter, but I think the examples have a lot of weight, and we should do our best to show how to name and use a certain feature. Your thoughts? Should I change the variable names in the examples?
Related to "Related Schemas" section: I assume any async schema has the same related sync schemas + every related sync schema's async version if present. Example: If array is related to custom then arrayAsync will be related to custom and customAsync. I made this assumption because any related async schema can be added inside the array schema, because of which array schema will be changed to arrayAsync schema to follow the "async only inside async schemas" rule. Is this a safe assumption to make? If my assumption is wrong, how would you recommend finding related async schemas?
Related to "Related Actions" section: I have included the async actions too, just for completeness. Do you think it is a good idea? As far as I know, it is not a requirement to use an async schema to use an async action, just that the method has to be async. Am I missing something?
Related to "Related Utils" section: How are isKindOf and isTypeOf utils related to the array or arrayAsync schemas?

Some potential issues I found that may need to be fixed or completed:

isOfType reference webpage's "Generics" section might be incorrect.
Reference webpages are missing for: ArrayIssue, parserAsync, pipeAsync, safeParserAsync, rawCheckAsync, rawTransformAsync and InferIssue.

Thanks a lot for this PR. You code looks good.

I am not sure what to do with the examples. I do not recommend to just copy the sync ones, because we recommend to use the async version only if you really need it, so as not to harm the runtime performance unnecessarily. The async version is only needed, for example, if you are validating against your database and need to make a network request. Maybe we should remove the examples for now and add them later. What do you think is best?

Your assumption is correct.

I recommend adding the ### Async header at the end with all related async APIs (including schemas and actions).

Every schema and action contains a kind and type property. Both utils are type guards that can be used to check these properties.

isOfType reference webpage's "Generics" section might be incorrect.

Good catch! Feel free to fix it.

Reference webpages are missing

Don't worry about ArrayIssue. I will add all ...Issue types in the next weeks. If you are interested and have time, you can help me with that.
Feel free to add blank routes for parserAsync, pipeAsync, safeParserAsync, rawCheckAsync and rawTransformAsync. Don't forget to also add them to the menu.md file in alphabetical order.
I am very grateful for your contributions and am interested in passing on some of the sponsorship money the project receives to you in the long run. I don't have the setup for this yet, but I hope to figure it out in the next few months. Maybe we can also find a partner organisations who will support you financially so that you can spend more of your time on Valibot.

Thanks for answering the questions.
Regarding the examples, I agree that the async schema's examples shouldn't be a copy of its sync schema's examples. I'll try to come up with some good async examples. During the review, if you don't like the examples, you can remove them. We can always add examples later. I'll make a few more changes based on your answers to this PR. I will let you know once I am done. Also, I'll fix the isOfType "Generics" section and add blank routes for missing webpages shortly.
Regarding the sponsorship, it will definitely help me, but it is not necessary. I plan to help a lot anyway, but I agree - it will help me spend more time on Valibot. Thank you!

I wanted to let you know that I have made the planned changes. You can start reviewing whenever you are free to start the review process.

Thank you! The examples are great! I only changed them a little. Since the examples are similar, I think the first one is enough. Let's move the second one with the username to the objectAsync API reference. I plan to review and merge this PR later or tomorrow.

Thanks again! I have sorted the related async APIs alphabetically, matched the description of arrayAsync with the JSDoc in the source code, and removed the word "asynchronous" from the explanation because the data type is still validated synchronously. arrayAsync only provides the ability to validate the array items asynchronously, but I don't think we need to mention this as we describe the general concept in more detail in our async validation guide.


add pound-force inch torque conversion

I guess this would be a first step towards https://github.com/ferraridamiano/ConverterNOW/issues/251

There seems to be also format issues. Could you please run dart format .?

Closing this for now since for lack of activity in the past year. Feel free to reopen it or just ping me


[BUG] UI - Show system hidden button moves with the frame on scroll

Describe the bug
Show system hidden button in the volume details page moves with the frame on scroll.
To Reproduce
Steps to reproduce the behavior:

Create a volume, attach to a pod.
Go to volume details page.
Take more than 15 snapshots.
Scroll the frame to volume head, the 'show system hidden' button also moves with the frame.

Expected behavior
The 'Show system hidden' button should be at the right top corner of the Snapshots and Backups section.
Environment:

Longhorn version: longhorn master - 10/13/2020

Validated with longhorn UI master - f69c761
Validation - Pass


Unable to run flowise using docker.

Image creation fails
yarn build command gives error
To Reproduce

clone repo
Run docker build -t flowise:1.5.0 .
check log
. See error
=> [11/12] COPY . .                                                                                0.9s
=> ERROR [12/12] RUN yarn build                                                                             28.8s

[12/12] RUN yarn build:
#16 1.484 yarn run v1.22.19
#16 1.542 $ turbo run build
#16 2.146
#16 2.146 Attention:
#16 2.146 Turborepo now collects completely anonymous telemetry regarding usage.
#16 2.146 This information is used to shape the Turborepo roadmap and prioritize features.
#16 2.146 You can learn more, including how to opt-out if you'd not like to participate in this anonymous program,
by visiting the following URL:
#16 2.146 https://turbo.build/repo/docs/telemetry
#16 2.146
#16 2.670 • Packages in scope: flowise, flowise-components, flowise-ui
#16 2.670 • Running build in 3 packages
#16 2.670 • Remote caching disabled
#16 2.703 flowise-ui:build: cache miss, executing c7f792750140de21
#16 2.708 flowise-components:build: cache miss, executing 5b190549943e5095
#16 3.021 flowise-components:build: $ tsc && gulp
#16 3.040 flowise-ui:build: $ craco build
#16 5.300 flowise-ui:build: Creating an optimized production build...
#16 9.566 flowise-ui:build: One of your dependencies, babel-preset-react-app, is importing the
#16 9.566 flowise-ui:build: "@babel/plugin-proposal-private-property-in-object" package without
#16 9.566 flowise-ui:build: declaring it in its dependencies. This is currently working because
#16 9.566 flowise-ui:build: "@babel/plugin-proposal-private-property-in-object" is already in your
#16 9.566 flowise-ui:build: node_modules folder for unrelated reasons, but it may break at any time.
#16 9.566 flowise-ui:build:
#16 9.566 flowise-ui:build: babel-preset-react-app is part of the create-react-app project, which
#16 9.566 flowise-ui:build: is not maintianed anymore. It is thus unlikely that this bug will
#16 9.566 flowise-ui:build: ever be fixed. Add "@babel/plugin-proposal-private-property-in-object" to
#16 9.566 flowise-ui:build: your devDependencies to work around this error. This will make this message
#16 9.566 flowise-ui:build: go away.
#16 9.566 flowise-ui:build:
#16 27.71 flowise-components:build: nodes/memory/MongoDBMemory/MongoDBMemory.ts(121,17): error TS2322: Type '{ messages: { $each: StoredMessage[]; }; }' is not assignable to type 'PushOperator'.
#16 27.71 flowise-components:build:   Type '{ messages: { $each: StoredMessage[]; }; }' is not assignable to type 'NotAcceptedFields<Document, readonly any[]>'.
#16 27.71 flowise-components:build:     Property 'messages' is incompatible with index signature.
#16 27.71 flowise-components:build:       Type '{ $each: StoredMessage[]; }' is not assignable to type 'undefined'.#16 27.71 flowise-components:build: nodes/memory/MongoDBMemory/MongoDBMemory.ts(177,21): error TS2322: Type '{ messages: { $each: StoredMessage[]; }; }' is not assignable to type 'PushOperator'.
#16 27.71 flowise-components:build:   Type '{ messages: { $each: StoredMessage[]; }; }' is not assignable to type 'NotAcceptedFields<Document, readonly any[]>'.
#16 27.71 flowise-components:build:     Property 'messages' is incompatible with index signature.
#16 27.71 flowise-components:build:       Type '{ $each: StoredMessage[]; }' is not assignable to type 'undefined'.#16 27.71 flowise-components:build: nodes/memory/MongoDBMemory/MongoDBMemory.ts(189,21): error TS2322: Type '{ messages: { $each: StoredMessage[]; }; }' is not assignable to type 'PushOperator'.
#16 27.71 flowise-components:build:   Type '{ messages: { $each: StoredMessage[]; }; }' is not assignable to type 'NotAcceptedFields<Document, readonly any[]>'.
#16 27.71 flowise-components:build:     Property 'messages' is incompatible with index signature.
#16 27.71 flowise-components:build:       Type '{ $each: StoredMessage[]; }' is not assignable to type 'undefined'.#16 27.81 flowise-components:build: error Command failed with exit code 2.
#16 27.81 flowise-components:build: info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
#16 27.82 flowise-components:build: ERROR: command finished with error: command (/usr/src/packages/packages/components) /tmp/yarn--1709542001736-0.599332845192742/yarn run build exited (2)
#16 27.87 flowise-components#build: command (/usr/src/packages/packages/components) /tmp/yarn--1709542001736-0.599332845192742/yarn run build exited (2)
#16 27.88
#16 27.88  Tasks:    0 successful, 2 total
#16 27.88 Cached:    0 cached, 2 total
#16 27.88   Time:    25.723s
#16 27.88 Failed:    flowise-components#build
#16 27.88
#16 27.88  ERROR  run failed: command  exited (2)
#16 28.66 error Command failed with exit code 2.
#16 28.66 info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

executor failed running [/bin/sh -c yarn build]: exit code: 2
Expected behavior
Image should be created successfully
Screenshots
If applicable, add screenshots to help explain your problem.
Flow
If applicable, add exported flow in order to help replicating the problem.
Setup

docker version 20.10.21
Flowise Version  1.5.0
OS: [Windows,]

Additional context
Add any other context about the problem here.

I think this was fixed in https://github.com/FlowiseAI/Flowise/commit/52dbfc6a4f61f11b09b4cd8dc5ad77156291db3c ?

You might want to do a docker pull insteall. This works right away for me. I followed this example and installed on a linux box - https://docs.flowiseai.com/configuration/deployment/digital-ocean refer to this section.
docker pull flowiseai/flowise


Companies API - GET companies/{globalId} returns 403

Removed endpoint from the spec as this is not implemented currently


Dropping connection

First, thanks for taking the time to create this project. I'm really looking forward to leveraging my Keiser with some apps w/o having to buy the Keiser connector (hopefully)!
I'm using a Raspberry Pi 3 B v1.2 with both an iPad and AppleTV 4K. Both devices see the Keiser services no problem, but Zwift will promptly lose connection and Fulgaz will crash. The connection won't recover when I opt to start biking in Zwift. When I go back to pairing, though, the bike is easily found, and the cycle repeats. Here's some example output I get from npm start
><EMAIL_ADDRESS>start /home/pi/git/M3iPiZeroW
> node index.js

Starting
[KeiserM3 starting]
server running - 3000
[Central] State changed to poweredOn
[Central] starting scan
[KeiserM3 stateChange] new state: poweredOn
Bike 0: RT: true RPM: 0 PWR: 0 GEAR: 11 ET: 0
Attaching to bike id 0
[KeiserM3-0 advertisingStart] success
[KeiserM3-0 servicesSet] success
[KeiserM3-0 setServices] success
Bike 0: RT: true RPM: 0 PWR: 0 GEAR: 11 ET: 0
Bike 0: RT: true RPM: 0 PWR: 0 GEAR: 11 ET: 0
Bike 1: RT: true RPM: 10 PWR: 6 GEAR: 11 ET: 0
Bike 1: RT: true RPM: 10 PWR: 6 GEAR: 11 ET: 0
Bike 1: RT: true RPM: 10 PWR: 6 GEAR: 11 ET: 0
Bike 1: RT: true RPM: 40 PWR: 6 GEAR: 11 ET: 0
Bike 1: RT: true RPM: 40 PWR: 31 GEAR: 11 ET: 0
Bike 1: RT: true RPM: 46 PWR: 31 GEAR: 11 ET: 5
Bike 1: RT: true RPM: 46 PWR: 31 GEAR: 11 ET: 5
Bike 1: RT: true RPM: 49 PWR: 43 GEAR: 11 ET: 6
Bike 1: RT: true RPM: 49 PWR: 43 GEAR: 11 ET: 6

The values seem to be correct (gear definitely is). What does the Boolean value represent? I see it go false intermittently. I also see these messages:
Bike 1: RT: true RPM: 0 PWR: 133 GEAR: 14 ET: 41
noble warning: unknown handle 64 disconnected!
Bike 1: RT: true RPM: 0 PWR: 0 GEAR: 14 ET: 42
[KeiserM3-0 accept] Client: 4c:c5:a2:a6:d3:5c
[KeiserM3-0 rssiUpdate]: 127
Restarting BLE Scan
noble: unknown peripheral undefined RSSI update!
Bike 1: RT: true RPM: 0 PWR: 0 GEAR: 14 ET: 42
[KeiserM3-0 disconnect] Client: 4c:c5:a2:a6:d3:5c
noble warning: unknown handle 65 disconnected!
[KeiserM3-0 accept] Client: 4c:c5:a2:a6:d3:5c
Restarting BLE Scan
[KeiserM3-0 rssiUpdate]: 127
noble: unknown peripheral undefined RSSI update!
Bike 1: RT: true RPM: 0 PWR: 0 GEAR: 14 ET: 42
Bike 1: RT: true RPM: 0 PWR: 0 GEAR: 14 ET: 42
[KeiserM3-0 disconnect] Client: 4c:c5:a2:a6:d3:5c
noble warning: unknown handle 64 disconnected!
[KeiserM3-0 accept] Client: 4c:c5:a2:a6:d3:5c
[KeiserM3-0 rssiUpdate]: 127
Restarting BLE Scan
noble: unknown peripheral undefined RSSI update!
Bike 1: RT: true RPM: 0 PWR: 0 GEAR: 14 ET: 42
[KeiserM3-0 disconnect] Client: 4c:c5:a2:a6:d3:5c
noble warning: unknown handle 64 disconnected!
Bike 1: RT: true RPM: 0 PWR: 0 GEAR: 14 ET: 42
[KeiserM3-0 accept] Client: 4c:c5:a2:a6:d3:5c
[KeiserM3-0 rssiUpdate]: 127
Restarting BLE Scan
noble: unknown peripheral undefined RSSI update!
Bike 1: RT: true RPM: 0 PWR: 0 GEAR: 14 ET: 42
noble warning: unknown handle 64 disconnected!
[KeiserM3-0 disconnect] Client: 4c:c5:a2:a6:d3:5c
Bike 1: RT: true RPM: 0 PWR: 0 GEAR: 14 ET: 42
[KeiserM3-0 accept] Client: 4c:c5:a2:a6:d3:5c
[KeiserM3-0 rssiUpdate]: 127
Restarting BLE Scan
noble: unknown peripheral undefined RSSI update!
Bike 1: RT: true RPM: 0 PWR: 0 GEAR: 14 ET: 42
Bike 1: RT: true RPM: 0 PWR: 0 GEAR: 14 ET: 42
[KeiserM3-0 disconnect] Client: 4c:c5:a2:a6:d3:5c
noble warning: unknown handle 64 disconnected!
Bike 1: RT: true RPM: 0 PWR: 0 GEAR: 14 ET: 42
[KeiserM3-0 accept] Client: 4c:c5:a2:a6:d3:5c
Restarting BLE Scan
[KeiserM3-0 rssiUpdate]: -52
noble: unknown peripheral undefined RSSI update!
Bike 1: RT: false RPM: 46 PWR: 59 GEAR: 14 ET: 42
[KeiserM3-0 disconnect] Client: 4c:c5:a2:a6:d3:5c
noble warning: unknown handle 64 disconnected!
[KeiserM3-0 accept] Client: 4c:c5:a2:a6:d3:5c
[KeiserM3-0 rssiUpdate]: 127
Restarting BLE Scan
noble: unknown peripheral undefined RSSI update!
Bike 1: RT: false RPM: 46 PWR: 59 GEAR: 14 ET: 42
noble warning: unknown handle 64 disconnected!
[KeiserM3-0 disconnect] Client: 4c:c5:a2:a6:d3:5c
[KeiserM3-0 accept] Client: 4c:c5:a2:a6:d3:5c
Restarting BLE Scan
[KeiserM3-0 rssiUpdate]: 127
noble: unknown peripheral undefined RSSI update!
Bike 1: RT: false RPM: 46 PWR: 59 GEAR: 14 ET: 42
Bike 1: RT: false RPM: 46 PWR: 59 GEAR: 14 ET: 42
[KeiserM3-0 disconnect] Client: 4c:c5:a2:a6:d3:5c
noble warning: unknown handle 64 disconnected!
Bike 1: RT: false RPM: 46 PWR: 59 GEAR: 14 ET: 42
Bike 1: RT: false RPM: 46 PWR: 59 GEAR: 14 ET: 42
Bike 1: RT: false RPM: 46 PWR: 59 GEAR: 14 ET: 42
Bike 1: RT: false RPM: 46 PWR: 59 GEAR: 14 ET: 42

Thanks for any insight you can provide!

I saw a this note about BLE 4.1+ being required, so I swapped my SD card to another Raspberry Pi 3B+ that I have sitting around that has BLE 4.2, but the problem behavior didn't change...

@pakdev  - I will answer the easy question first: the Boolean value is True when the Keiser M3i computer is in "real time" mode, which is the mode it is in when actively pedaling.  Once pedaling stops for a few seconds, the M3i goes into "summary mode" and the boolean is set to false.  When the value is false, no updates are sent to the bluetooth clients.  At least that is the intent of the code!
But regarding the real problem you are having...  it seems likely related to using the single on-board bluetooth adapter in "multi-role" mode where it is both listening to the M3i bluetooth beacon and serving data up to the consumers (Zwift, Fulgaz, etc).  I see there is an open issue in Gynmnasticon that might be similar.
Back in April there was a kludge/work-around used in the past by Gymnasticon which I copied.  And your console message "Restarting BLE scan" indicates that this code is being triggered.  Apparently there was an issue in the abandonware bluetooth library when using a single adapter in multi-role that could cause the noble connection to the consumers scanning to stop when a the adapter did a bleno scan a peripheral.  The "fix" was to listen for noble scan stop event and just restart it -- and perhaps that is now causing a race condition as mentioned in the Gymnasticon issue.
Frankly, diagnosing this quickly is probably beyond my technical ability. Perhaps the abandonware libraries were updated so the version you are runing with no longer needs the workaround or makes the race condition more likely?  Or perhaps the Pi 3B+ makes the race condition more likely? (I have only tested the code on a PiZeroW). I can try building building the system on a fresh SD card so that I an likely using the same libraries you are and see if can reproduce the issue.
Another thing you can do, if you have a USB Bluetooth dongle you can plug into your Raspberry Pi 3B+ and some time to play around, is to make a couple of simple code changes to run M3iPiZeroW in two-adapter mode:
In the file index.js change line 4 and 5 to be:
process.env['BLENO_HCI_DEVICE_ID'] = 0
process.env['NOBLE_HCI_DEVICE_ID'] = 1

in run.sh, add a second hciconfig line:
hciconfig hci0 up
hciconfig hci1 up

Finally, edit /etc/rc.local on your system to add the following line.  The purpose of this line is to ensure the on-board bluetooth adapter is enabled on reboot:
modprobe -r btusb && systemctl start hciuart.service && modprobe btusb
After modifying rc/local you will need to reboot the Raspberry PI.
Hopefully some of this info is useful  -- sorry I do not have a definitive fix for you.  :-(

Thanks for the thoughtful response, @djwasser. After I submitted this issue, I decided to try the gymnasticon image. Lo and behold, the connection is stable with my 3B+. I did some digging into their issues, and while I didn't see the issue you linked, I did find this one. It appears that gymnasticon has already removed the client characteristic uuid of 2902 but M3iPiZeroW hasn't. If you'd like, I can put M3iPiZeroW back on my rpi and see if commenting out that uuid fixes things. What does M3iPiZeroW add over gymnasticon? (I haven't tried HR with my Polar T31...maybe that?)

cycling-power-measurement-characteristic.js - removed 2902 descriptor in August as I had issues getting it to work with Zwift on Windows 10...

Just tried zwift with my august build of m3iPizero. (On iphone as I have no Apple TV - but it’s the same app as far as I know) - saw no dropouts/disconnections during my 45min ride.
M3iPizero vs Gymnasticon - addition of HR from Keiser computer integration into single Bluetooth connection (which I guess helps with appleTV users as they have limited Bluetooth connections (max 2) on appleTV devices.) - closer match to the ‘bad’ Keiser M series converter.

@pakdev  - glad you got Gymnasticon working for you!  @nealjane 's answer above regarding heart rate was one reason for creating this repo.  The other was that Gymnasitcon, when I tried it in early 2021, did not work realiably for me with Keiser M3i.  Perhaps the issues I had are now fixed?  In any case, it seemed simpler to just roll-my-own code that was specific to M3i and PiZeroW as it was easier for me to understand and modify.

I did a fresh build today and had exectly the smae issues that @pakdev saw.  So something has changed with the underlying libraries, etc. that this code uses.  Also, removingthe 2902 descriptors had no impact on the behavior.  So for the time being this code is KNOWN NOT TO WORK.  May find some time to troubleshoot some more in the future, but for now it is DOA.


Lack of Complex64 support for Java API

This issue is not about a bug, but I will fill in the form anyhow ;-)
System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow):
Yes
OS Platform and Distribution (e.g., Linux Ubuntu 16.04):
Mac 10.13.2
TensorFlow installed from (source or binary):
source
TensorFlow version (use command below):
master branch at commit: b86dc365ebbef64daceced37026518696ede5b7b
Python version:
N/A Using Java version "1.8.0_152"
Bazel version (if compiling from source):
Build label: 0.8.1-homebrew
Build target: bazel-out/darwin-opt/bin/src/main/java/com/google/devtools/build/lib/bazel/BazelServer_deploy.jar
Build time: Tue Dec 5 19:29:04 2017<PHONE_NUMBER>)
GCC/Compiler version (if compiling from source):
Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr --with-gxx-include-dir=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.13.sdk/usr/include/c++/4.2.1
Apple LLVM version 9.0.0 (clang-9<IP_ADDRESS>)
Target: x86_64-apple-darwin17.3.0
Thread model: posix
InstalledDir: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin
CUDA/cuDNN version:
N/A not using CUDA
GPU model and memory:
N/A not using GPU
Exact command to reproduce:
There is no bug to reproduce

Describe the problem
There is not really a problem. I have need to build TensorFlow computations in Java and have support for complex numbers. Because the C API already supports COMPLEX64 tensors, it was a straight forward effort to expose them in the Java API. Along with unit tests, I have also added a Java example based on the Python tutorial that builds an image that displays the Mandelbrot fractal to show that the complex number support works correctly.
Source code / logs
Here is a very short example of using the API, clearly there are functions in the example that are not available defined in the example, but it gets the point across. This example is basically lifted from a new java example I created called MandelbrotExample.java
Tensor<Complex64> resultZ = null;
try(Graph g = new Graph()) {
    //We create a meshgrid based on two numeric ranges, by wrapping the ranges
    //in Tensors and then pulling out sub grids to make complex numbers
    try (Tensor<Float> meshGridT = buildMeshGrid(range1Spec, range2Spec);
         Tensor<Integer> zeroT = Tensors.create(new int[]{0});
         Tensor<Integer> oneT = Tensors.create(new int[]{1});
         Tensor<Complex64> jTensor = Tensors.create(0.0f, 1.0f)) {

        Output<Integer> zero = buildConstant(g, "0", zeroT);
        Output<Integer> one = buildConstant(g, "1", oneT);

        Output<Float> meshGrid = buildConstant(g, "meshgrid", meshGridT);

        Output<Complex64> j = buildConstant(g, "imagUnit", jTensor);

        //We use GatherNd to pull out the two parts of the original mesh grid
        //the Z complex tensor
        Output<Float> Yfloat = g.opBuilder("GatherNd", "get_y")
                .addInput(meshGrid)
                .addInput(zero) //use zero
                .build().output(0);
        Output<Float> Xfloat = g.opBuilder("GatherNd", "get_x")
                .addInput(meshGrid)
                .addInput(one) //use one
                .build().output(0);

        Output<Complex64> Y = g.opBuilder("Cast", "castYtoComplex")
                .addInput(Yfloat)
                .setAttr("DstT", DataType.COMPLEX64)
                .build().output(0);

        Output<Complex64> X = g.opBuilder("Cast", "castXtoComplex")
                .addInput(Xfloat)
                .setAttr("DstT", DataType.COMPLEX64)
                .build().output(0);

        //Z is constructed by X + Yj
        Output<Complex64> mulYj = g.opBuilder("Mul", "mulYj")
                .addInput(Y)
                .addInput(j)
                .build()
                .output(0);
        Output<Complex64> Z = g.opBuilder("Add", "addZ")
                .addInput(X)
                .addInput(mulYj)
                .build()
                .output(0);

        try(Session s = new Session(g)){
            resultZ = s.runner().fetch(Z).run().get(0).expect(Complex64.class);
        }
    }
}

I would like to get my local branched pushed to GitHub and then a pull request put in with these changes. I have attached a diff file for the curious. I am still working on getting a corporate CLA put into place.
Thanks for your time and consideration!
java-complex64.patch.txt

@rajha-korithrien,
At the moment there is no support for it, but we'd welcome contributions to add that support. It would need to build the ndarray support and add the types to this package.
Complex64 is good as that can use long as the carrier type and unpack it into two floats for computation, but Java doesn't have a 128-bit primitive type so things have to be boxed and that will cause a lot of problems. Thank you!


UPSTREAM: : scope cluster_authentication_trust_controller properly

Note, I didn't update pkg/controlplane/instance.go which also creates this controller, so that file doesn't compile atm. I can try to fix it if needed (?).

Going to see if I can make this less invasive

Chatted on Slack with @stevekuznetsov - he prefers the larger fix vs. messing with keys


Can this plugin automatically save and load data after page loaded ?

formSaver.init();

above code, not saving or restore form inputed data automatically after page loaded.
can i contribute into this project ?. i'll make it better

Reduced test case please


Add post helper function for formdata

Adds a new _CallPost that receives a curl_httppost to simplify Form POST calls including log entry. This new helper function also parses the error message and prints it, like other helper functions.

Pipeline ID: 852542

Thank you!


docs: add rfc for Save Search Filter

This PR adds RPC documentation for implementing the Save Search Filter. : #721

@kakcy, have you considered creating one record per user in the DB? The current schema creates 1 record per filter, so if the user has 10 filters, it will have 10 records in the DB.

@cre8ivejp

have you considered creating one record per user in the DB? The current schema creates 1 record per filter, so if the user has 10 filters, it will have 10 records in the DB.

As you pointed out, it is designed so that one record exists in one filter.
Is this a problem with this design? (Will the number of records be huge?)
Or is it better to add a column like filters to the account_v2 table without creating a new table?
In that case, it is assumed that it will be stored in a Json array like environment_roles column.

Since the filter is per user, have you considered saving the filters in the account table?

Added Part2 proposal to add a filter information column to the account table.
Please review when you have time.

@kakcy Why don't you save queries in the local storage? It's easier to implement.

@kakcy Why don't you save queries in the local storage? It's easier to implement.

@kentakozuka, as discussed before, if the user accesses from another PC or the cache is deleted, we will lose all his filters.
Also, the other services that save on the server have a better user experience.

@kentakozuka
Proposed Thank you 👍
Similar to @cre8ivejp's opinion, I think it would be better to save it to the DB in order to provide stable functionality.

@kakcy @cre8ivejp
Understood. But I still think this feature would be too much. How often do we change our browsers to access Bucketeer? How often is the local storage deleted? Would it be worth to bring the complexity?


fix(startup): update for new congregation signup

:tada: This PR is included in version 2.18.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Option to open windows grouped by default.

An option to open windows grouped by default would be nice.
Cheers!

I think there is a way to implement this by modifying the
More specifically:

check for configuration variable, e.g.misc:new_window_in_group
if the value of the configuration variable is true, then create new group if possible'


Image packs remove sprite editor from template code image picker

When using image packs, the default image picker becomes this, instead of the sprite editor.  Best case would be making this start with image picker no matter what...next best is putting image pack options at the top of the gallery instead of the bottom.

This doesn't happen anymore


No .page-header in v4?

Hi,
I am searching for the page-header CSS component in v4-alpha. It looks like it was not ported over from v3. Can someone else confirm?

It's indeed gone. Per http://v4-alpha.getbootstrap.com/migration/#typography :

Dropped the .page-header class entirely.

@cvrebert May I ask why .page-header class is removed?

@Saucy It was removed in bf085b1a02238611d4962717a02f71def0fa8ba0 without much explanation. I've filed #19439 to ask @mdo to add his rationale to the docs.

@cvrebert Awesome, I'll subscribe to that issue and keep a look out on why it was remove. Thanks!


Error in version 4.2 when running on Windows OS

When patch apk with Xpatch 4.2, it shows an error IOException: Cannot run program "chmod": CreateProcess error=2, The system cannot find the file specified. But apk generate successfully. However the patched apk doesn't open after installed. It just crash. also apk name changes to something like "com.wind.Xpatch*** ".

versioin updated, use v4.3.  The IOException can  be ignored if new apk is created.


Epic: Add Angular Route Guards to manage navigation in app

In our frontend application we have two use cases that request for Route Gard implementation:

Ask user to save data when moving away from component when there are still uncommitted changes
Allow access to components based on Role based access constraint that come from Ampersand compiler

There are five different types of Route Guards:

CanActivate
CanActivateChild
CanLoad
CanDeactivate (can be used to prevent navigating away)
Resolve

Note that a Route Guard can be applied to a route itself using the canActivate property and/or be applied to all child routes using the canActiveChild property.
{
   path: 'foo',
   canActivate: [AuthGuard],
   canActivateChild: [AuthGuard],
   component: FooComponent,
   children: [
    { path: ':id', component: BarComponent},
    { path: ':id/name', component: BazComponent}
]}

This feature requires the implementation of keeping track of sessionRoles in the frontend. I'll create a separate issue for that.
EDIT:
It is not necessary for the sessionRoles to be tracked in the front-end, since this has already been handled by the back-end.
To complete this Epic, there are two issues that have to be resolved. One involves routing based on the roles of the user AmpersandTarski/prototype-frontend#177, and the other involves the user going to another route when the changes have yet to be commited AmpersandTarski/prototype#136 .

[ ] AmpersandTarski/prototype-frontend#177
[ ] AmpersandTarski/prototype#136

Is this issue still relevant? @Michiel-s can we close this?

Yes. This issue is still relevant.  The developed RolesGuard is not activated for generated module and also the pending changes detection is open issue.


ValueError: too many values to unpack

I get the following error during certificate generation:
Creating/renewal st.example.com certificates... (st.example.com)
2018-12-29 23:48:14,336:INFO:simp_le:1479: Generating new certificate private key
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/simp_le.py", line 1584, in main
    return main_with_exceptions(cli_args)
  File "/usr/lib/python2.7/site-packages/simp_le.py", line 1567, in main_with_exceptions
    persist_new_data(args, existing_data)
  File "/usr/lib/python2.7/site-packages/simp_le.py", line 1483, in persist_new_data
    certr = get_certr(client, csr, authorizations)
  File "/usr/lib/python2.7/site-packages/simp_le.py", line 1425, in get_certr
    ', '.join(authzr.uri for _, authzr in error.exhausted)
  File "/usr/lib/python2.7/site-packages/simp_le.py", line 1425, in <genexpr>
    ', '.join(authzr.uri for _, authzr in error.exhausted)
ValueError: too many values to unpack

Background:
Configuration is pretty standard:
  nginx:
    image: nginx
    container_name: nginx
    restart: unless-stopped
    ports:
      - "80:80"
      - "443:443"
    volumes:
      - nginx_conf:/etc/nginx/conf.d
      - certs:/etc/nginx/certs
      - vhost:/etc/nginx/vhost.d
      - nginx_html:/usr/share/nginx/html
    networks:
      - gateway_network

  dockergen:
    build:
      context: ./dockergen
    container_name: dockergen
    restart: unless-stopped
    command: -notify-sighup nginx -watch /etc/docker-gen/templates/nginx.tmpl /etc/nginx/conf.d/default.conf
    volumes:
      - /var/run/docker.sock:/tmp/docker.sock:ro
      - nginx_conf:/etc/nginx/conf.d
      - certs:/etc/nginx/certs
      - vhost:/etc/nginx/vhost.d
      - nginx_html:/usr/share/nginx/html
    networks:
      - gateway_network

  letsencrypt-companion:
    restart: unless-stopped
    container_name: letsencrypt-companion
    image: jrcs/letsencrypt-nginx-proxy-companion:v1.9.1
    environment:
      - NGINX_PROXY_CONTAINER=nginx
      - NGINX_DOCKER_GEN_CONTAINER=dockergen
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock:ro
      - nginx_conf:/etc/nginx/conf.d
      - certs:/etc/nginx/certs
      - vhost:/etc/nginx/vhost.d
      - nginx_html:/usr/share/nginx/html
    networks:
      - gateway_network

networks:
  gateway_network:
    name: gateway_network

volumes:
    nginx_conf:
    nginx_html:
    vhost:
    certs:

There are 6 websites total. I get certificates generated for 4 of them successfully. But I get this aforementioned error for other two.
If I understand correctly from the error it fails to unpack some error response values. How can I see what was the error? Is there request/response logs?
Can it be a rate limiting issue?

I get the same error here using the evertramos/docker-compose-letsencrypt-nginx-proxy-companion image.

@offbeatful : the simp_le traceback seems to indicate that you are using an outdated version of the container.
@h44z : we don't provide support for forks of this project.

Looks like simp_le is having a hard time handling network related issues, I'm not sure there is much we can do from the letsencrypt-nginx-proxy-companion container perspective.

As this is most probably a simp_le issue that we can't fix from our end, I'm going to close this issue for now. Feel free to re-open it if needed.


Add support for aud and iss claims, addresses #38

This library should have support for validating aud and iss claims in JWTs, as per RFC 7519 Section 4.1.3.
This PR adds two new settings: AUDIENCE and ISSUER. When left blank, the library behaves as it did previously. When set, the aud and iss corresponding to each setting are set in encoded tokens, and validated in decoded tokens.
Unit tests will probably be broken on this PR until #61 is merged.

@davesque looks like we've got at least 8 other people interested in this feature (+1s from this PR and the original issue). Any chance of it being merged? I just rebased to the latest master. I think this is the last thing we're waiting on before we can stop using our fork :crossed_fingers:

Sorry @ajhodges .  I've been pretty busy with work lately.  Will try to find time to look at this.

:+1: fixed, thanks! Just noticed you do work for the Ethereum Foundation - cool! We'll be at devcon in a couple weeks.

Awesome!  Let's meet up and chat or something! :)


NodeJS: Migrate Nodejs path templates to MVVM.

Codecov Report

Merging #1104 into master will increase coverage by 0.01%.
The diff coverage is 100%.

@@             Coverage Diff              @@
##             master    #1104      +/-   ##
============================================
+ Coverage     85.87%   85.89%   +0.01%
- Complexity     3554     3559       +5
============================================
  Files           365      365
  Lines         13932    13941       +9
  Branches       1592     1592
============================================
+ Hits          11964    11974      +10
  Misses         1528     1528
+ Partials        440      439       -1

Impacted Files
Coverage Δ
Complexity Δ

.../google/api/codegen/nodejs/NodeJSGapicContext.java
88.73% <100%> (-0.8%)
87 <3> (+1)

...codegen/transformer/nodejs/NodeJSSurfaceNamer.java
87.5% <100%> (+4.16%)
20 <2> (+2)
:white_check_mark:

...om/google/api/codegen/util/js/JSNameFormatter.java
81.81% <0%> (+13.63%)
14% <0%> (+2%)
:white_check_mark:

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 b4df82d...b69a78e. Read the comment docs.


feat: preserve dict key order in the output of tree_unflatten, tree_map, and tree_map_with_path

Description
Describe your changes in detail.
Add a new option in _C.flatten and _C.flatten_with_path(enabled globally), which will save the original key order in PyTreeSpec and use it to preserve key order during unflattering.
Now, the output of tree_map and tree_map_with_path will guarantee the same key order as the input dictionaries.
Before: output dict from tree_unflatten is in sorted order. The output key order changes even if mapped with an identity function.
>>> optree.tree_map(lambda x: x, {'b': 2, 'a': 1})
{'a': 1, 'b': 2}

After: output dict from tree_unflatten is consistent with the input dict.
>>> optree.tree_map(lambda x: x, {'b': 2, 'a': 1})
{'b': 2, 'a': 1}

Note that tree_map still maps the leaves in sorted key order (the same order as tree_flatten and tree_leaves). This PR only changes the behavior for tree_unflatten.
>>> leaves = []
...
... def add_leaves(x):
...     leaves.append(x)
...     return x
...
>>> ptree.tree_map(add_leaves, {'b': 2, 'a': 1})
{'b': 2, 'a': 1}
>>> leaves
[1, 2]

Also, If the users manually maintain the treespec themselves. For example, 1) flatten the tree, 2) hold the reference to the treespec and do something with the leaves, 3) unflatten back the results into a tree with treespec. The key order in the resulting tree is still sorted. This PR only affects functions tree_map and tree_map_with_path.
Motivation and Context
Why is this change required? What problem does it solve?
If it fixes an open issue, please link to the issue here.
You can use the syntax close #15213 if this solves the issue #15213

[X] I have raised an issue to propose this change (required for new features and bug fixes)

Resolves #45
Types of changes
What types of changes does your code introduce? Put an x in all the boxes that apply:

[ ] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds core functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Documentation (update in the documentation)

Checklist
Go over all the following points, and put an x in all the boxes that apply.
If you are unsure about any of these, don't hesitate to ask. We are here to help!

[X] I have read the CONTRIBUTION guide. (required)
[X] My change requires a change to the documentation.
[X] I have updated the tests accordingly. (required for a bug fix or a new feature)
[X] I have updated the documentation accordingly.
[X] I have reformatted the code using make format. (required)
[X] I have checked the code using make lint. (required)
[X] I have ensured make test pass. (required)

Got around ~25% performance drop for tree-map on builtins.dict.

now the performance downgrade on tree_unflatten is intolerable

Code robustness is more important than performance. The tree_map function does not preserve dict key order with the identity function. It's not intuitive for normal users who do not read the documentation carefully.
This PR adds extra operations in tree_flatten and tree_unflatten.

tree_flatten: add list.copy before list.sort ($O(n \log n) \to O(n \log n) + O (n)$)
tree_unflatten: add dict.fromkeys before dict.update ($O(n) \to O(n) + O (n)$)

It would introduce some performance regression. But the tree operations sometimes are not the performance bottleneck in the whole pipeline. For example, you reduce a tree operation from 0.1ms to 0.08ms (20%), but your environment simulation takes 1ms. The total performance gain is minor (1.1ms vs. 1.08ms (2%)).

It would introduce some performance regression. But the tree operations sometimes are not the performance bottleneck in the whole pipeline. For example, you reduce a tree operation from 0.1ms to 0.08ms (20%), but your environment simulation takes 1ms. The total performance gain is minor (1.1ms vs. 1.08ms (2%)).

Thanks for your reply! I will try to run the benchmark test with the whl in this pr on envpool these two days, I will get back to you when the results are out, please wait until the benchmark test is ready.


connlib: re-design API between clients & tunnel

This is a tracking issue that is meant to capture some ideas for re-designing how we communicate from the Tunnel with the individual clients. Currently, this done via callbacks in two places:

From within the Tunnel to the various "glue" crates for the clients
Across the FFI boundary (only Android and Apple)

### Tasks
- [ ] Remove (1)  in favor of events being emitted from `Tunnel` and sent into a channel in the `Eventloop`
- [ ] https://github.com/firezone/firezone/issues/4473

The goal is to free connlib from as much platform-specific code as possible. This allows Tun to be a Sink + Stream of IpPackets and all the platform-specific stuff is in the already platform-specific client crates.
Emitting a stream of events changes from a push to a pull design, giving clients more flexibility in handling them by e.g. having access to &mut self, async etc.
We might be able to remove the callbacks across the FFI boundary with a move to UniFFI (https://github.com/firezone/firezone/issues/3959) which supports async functions. That would allow Android as well as Swift to use their native co-routine / tasks mechanism to directly respond to the next emitted event and handle it accordingly.

Closing because it duplicates what is now in other issues.


Learning gem5 tutorial presentation is down (ASPLOS 2018)

A presentation of the tool in ASPLOS 2018 is provided in the repo description, but apparently the link (http://learning.gem5.org/tutorial/presentations/vis-o3-gem5.pdf) is unreachable.
Is it possible to upload the presentation somewhere else?

I have uploaded the presentation file to a different location and fixed the link. Also, I have slightly modified the description to reflect the current version. Please check it.
Thank you!


Fixed typo in the Contributing Guide

On https://keptn.sh/community/contributing/ there's a typo at the line
"If you are interested Most of the Keptn codebase is implemented in Golang and JavaScript/Angular"
The above typo has been fixed to
"If you are interested, most of the Keptn codebase is implemented in Golang and JavaScript/Angular"
Signed-off-by: Chaitanya Bisht<EMAIL_ADDRESS>

I rebased the commit to fix the build, but there is an error with the signoff - and the email provided. DCO complains with:
Commit sha: [781afb1](https://github.com/keptn/keptn.github.io/pull/1551/commits/781afb12f2131f84e5f5f04f8c2791b9743f6b10), Author: Chaitanya Bisht, Committer: Simon Schrottner; Expected "Chaitanya Bisht [63919815+chaitanyabisht@users.noreply.github.com](mailto:63919815+chaitanyabisht@users.noreply.github.com)", but got "Chaitanya Bisht [chaitanya.bisht10@gmail.com](mailto:chaitanya.bisht10@gmail.com)".

can you address this, @chaitanyabisht, as stated in the failed DCO? thank you

I fixed the DCO sign-off issue and am merging.  Thank you again for the contribution,  @ chaitanyabisht !  I apologize for the delay in getting this merged.  I hope you will contribute more -- future PRs should go more quickly.

Thank you for fixing the DCO issue! Since I am a new contributor I forgot to sign off the commit initially. However I followed the steps to sign them and fix the commit.


[RFC]: add @stdlib/array/base/cuany

Description
This RFC proposes adding the package @stdlib/array/base/cuany, which cumulatively tests whether at least one array element in a provided array is truthy. The function should return a new generic array. The package should also provide an #assign API for setting output values in a provided output array.
var x = [ false, false, true, false, false ];

var y1 = cuany( x );
// returns [ false, false, true, true, true ]

var y2 = [ false, null, false, null, false, null, false, null, false, null ];
var out = cuany.assign( x, y2, 2, 0 );
// returns [ false, null, false, null, true, null, true, null, true, null ]

where the assign API supports an offset and stride (see, e.g., @stdlib/array/base/take).
Both APIs should support accessor arrays (see, e.g., @stdlib/array/base/take).
Related Issues
No.
Questions
No.
Other
No.
Checklist

[X] I have read and understood the Code of Conduct.
[X] Searched for existing issues and pull requests.
[X] The issue name begins with RFC:.

I'd like to take this up

@adityacodes30 Sounds good! Thanks for volunteering to work on this!

@adityacodes30 For the main export, the return type should be a "generic" array (e.g., [ true, false, true ]; i.e., Array<boolean>). For the assign API attached to the main export, the return type should be whatever the input array is (see, e.g., https://github.com/stdlib-js/stdlib/blob/3cf2e897adf5128f94bd7279e88ca9d42dfe7caa/lib/node_modules/%40stdlib/array/empty-like/docs/types/index.d.ts#L67).

I have question to as to how to export a particular function in an export to use it for the api as in -
i have 2 function and one main function in main.js named indexed , accessor and cuany (the export)
now i need to use cuany in my assign.js but that doesnt work because of the arraylike2object conversions to support accessor arrays , i want to use the accessor function in my assign api . what are the conventions for doing that and how should i go about it ?

@adityacodes30 I suggest exploring the variety of implementations in array/base/*, as you are likely to find something which is applicable for what you are trying to do. At a high level, my sense is that the main export should actually be using the implementations in assign.js, rather than the other way around. The main export should allocate a generic array filled with false values using @stdlib/array/base/filled. That allocated array should then be passed along to the assign implementation as the output array.


Improvement of the completion of the use keyword

Hi,
When I tried PHPCD I realize that I couldn't use the completion for the use keyword.
That's because I'm using the PSR-4 standard for autoloading, and since I'm on a development environment I don't genrerate the classmap file of composer.
The on PHPCD use to find the classes of a project.
That's why I started to modify it to be able to load all the classes without running composer dump-autoload -a each time I create a file.
The only change is for the method classmap of the PHPCD class.
If you like the idea i was thinking of injecting the ClassFinder into PHPCD from the main.php file.
So it can be configure in .vim file.
Thanks for your attention, and thanks for all your work !

Hello @elythyr
It is great pleasure that phpcd.vim makes convenient for you.
I reviewed you patch. And it looks well. However, I prefer to run the composer dump-autoload -o  instead of introduction so bin patch. I want to make phpcd.vim as simple as possible.
Fell free to make your own phpcd.vim fork. Thank you.


Allow Different Icon Colors For Individual Folders/Files

Is your feature request related to a problem? Please describe.
Right now, as far as I can find, I can only change every icon's color to a single color.
Describe the solution you'd like
The ability to choose the icon's color in the "Change Icon" menu or new menu for each folder/file individually.
Describe alternatives you've considered
Instead of individually choosing the colors, colors could be set in the plugin's settings page through regex selectors. That way any note with certain characters in its name could be the same colors (or even based on note tags?)

This functionality is now available in the newest release :)


add the background images!

add the background images!
Here is the design idea!
design.pdf👈
image1
image2
//Change the text color to white and make changes!
//for the project section change the card view to white or similar color that suits the design
//footer remains the same!

Can I do it?

Sure! @ClaudioFuriniJr
I have assigned you!

Hey @adventuroussrv i have a good idea some how on this, can i take a look on this?

@adventuroussrv Did a first version based on the .pdf
Let me know if it is ok for you :)
Thank you

Hey @adventuroussrv i have done something can i get access to push, if it's fine.

Hi @ClaudioFuriniJr It's fine for now! I will open more issue! You may still work on it and make PR

Hi @RamanaVem
This issue was already assigned to @ClaudioFuriniJr
you may check out any new issue if you wanna work on!!

I will open more issues soon! closing this for now


Evaluate the usage of Gulp method decorators

This project provides more object-oriented approach to Gulp.
We can evaluate it for eventual integration with the seed.
// cc @ludohenin

@mgechev - That looks promising.
One side note, I think it may be a good idea to spend a few days stabilizing the tools after the last refactoring before we do it again.

@d3viant0ne totally agree.

Not quite sure.
Our task programing model is really simple now, don't you think it should remain ?

@ludohenin - I like the idea of using decorators but you are totally right, we would have to be able to implement it while retaining the simplicity that comes the last refactoring.

The biggest problem I see is the coincidental cohesion of the classes.
However, in a perfect scenario each task could be implemented as an individual class which will encapsulate its logic. This way the class will have a single public method annotated with @Task. In this perspective the gulpclass package won't bring extra complexity but instead will help with bringing polymorphic behavior to the classes by having method overrides, inheritance, abstraction and encapsulation (thanks to the private methods that help us implement the @Task).
The biggest drawback I see is the extra level of indirection which may make everything look like magic.


CLI: manim init vs manim new + documentation!

Enhancement proposal
The dialog for creating a new project spawned using our CLI with manim new is actually pretty cool -- but unfortunately more or less completely undocumented. This should be changed, for example by rewriting the project creation part of the quickstart tutorial.
Moreover, I am not quite sure why we have both manim new and manim init, which seems to do a pretty similar thing.

[x] Deprecation of manim new + moving functionality to manim init
[ ] Documenting the new utility in form of a tutorial (or by rewriting the quickstart tutorial)

Can I work on this ?

Can I work on this ?

Sure. After sleeping over it, I think the command that should remain is manim init (in resemblance to git init, and similar CLI scripts), so the first step would probably be a PR that

moves the functionality from manim new to manim init,
and issues a deprecation warning for manim new.

Removing manim new, and rewriting the documentation can then be done in a later PR.

@behackl so if I understand correctly, first you want me to work on the command first, then the documentation right ?

@behackl so if I understand correctly, first you want me to work on the command first, then the documentation right ?

I'm not @behackl, but that's how I would interpret his comment.

I think the command that should remain is manim init (in resemblance to git init, and similar CLI scripts), so the first step would probably be a PR that
* moves the functionality from `manim new` to `manim init`,

* and issues a deprecation warning for `manim new`.

Removing manim new, and rewriting the documentation can then be done in a later PR.

I think it still makes sense for manim new to exist but with different functionality. manim new lets you decide whether you want to create a new project, or a new scene, the latter of which shouldn't to be under manim init. If it were we would have to write something like manim init new-scene which is a but cumbersome.
I propose instead that both init and new stay, but we move some functionality around:

manim init should only create a new project and it should have the same dialog as manim new project
manim new should still exist but it should only have the manim new scene functionality that currently exists

This allows us to give manim init better functionality whilst also keeping manim new scene or just manim new which seems like a good command that could be extended in future to generate more boilerplate code.

After more consideration, it does make more sense to just move all the current functionality from manim new to manim init, but I do think there is scope to keep manim new around for generating boilerplate code.

@behackl can this issue be closed now?

@behackl can this issue be closed now?

I've edited the issue description, there is still work to be done. :-)

init should also contain VectorScene and LinearTransformationScene and ThreeDScene


Wallpaper doesn't work

Hello, I've already tried changing the wallpaper to those in the app, I've already put new ones and nothing works, only “light” and “dark” remain, otherwise the wallpaper has no function.

My system:
AMD Ryzen 3 2200G Processor with Radeon Vega Graphics 3.50 GHz
Installed RAM 24.0 GB
System type 64-bit operating system, x64-based processor
Thank you in advance

Do you have transparency/animation effects turned on in your Windows OS?

I turned it on and now it works. Thanks!


invalid match-expression, type of pattern variable 'match_eq✝' contains metavariables

The following example:
import Qq

open Qq Lean.Meta

example (qo : Q(Option Nat)) (o : Option Nat) : MetaM Unit := do
  match qo with
  | ~q(some $qx) => match o with
    | some x => pure ()
    | _ => pure ()

gives the error:
invalid match-expression, type of pattern variable 'match_eq✝' contains metavariables
  «$qo» =Q some «$qx»

Indeed, the type of match_eq✝ in the goal in
example (qo : Q(Option Nat)) : MetaM Unit := do
  match qo with
  | ~q(some $qx) => sorry

has a metavariable for the Level argument.

Replacing the inner match with match (generalizing := false) o with or  match id o with is sufficient as a workaround, though of course this disables generalization.

(And with https://github.com/leanprover/lean4/pull/3060, this obviously also affects let some x := o which must be written as let some x := id o)

My initial thought was that these lines are missing a let argLvlExpr ← instantiateMVarsQ argLvlExpr:
https://github.com/leanprover-community/quote4/blob/ccba5d35d07a448fab14c0e391c8105df6e2564c/Qq/Match.lean#L208-L212
but this doesn't seem to make any difference.


Env: S2G v2.14.1 + Win7 SP1 64bit Home Premium

Thanks.

I fixed it. Thanks.
It will be available with the next release.


OpenSearch Plugin zips in maven repo

Describe the blog post your would like to write
The post describes information about OpenSearch PluginZips in maven.
Related linked issue: https://github.com/opensearch-project/opensearch-build/issues/1916
What is the title of the blog post?
OpenSearch plugin zips now in Maven repo
Who are the authors?
@prudhvigodithi
What is the proposed posting date?
7/24/2022

@prudhvigodithi is there an RFC or issue that could be linked here for context?

Hey @dtaivpp I have updated the comment with the linked issue.
Thank you

this can probably be closed since #930 was merged & published two years ago?

Right, thanks @rursprung. Closing this issue.
@getsaurabh02


Replace deprecated function call

Summary
tostring has been deprecated since numpy 1.17.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
8 unchanged lines in 3 files lost coverage.
Overall coverage decreased (-0.05%) to 85.836%

Files with Coverage Reduction
New Missed Lines
%

crates/qasm2/src/expr.rs
1
93.76%

crates/qasm2/src/lex.rs
3
91.14%

crates/accelerate/src/sabre_swap/layer.rs
4
97.32%

Totals

Change from base Build<PHONE_NUMBER>:
-0.05%

Covered Lines:
70767

Relevant Lines:
82444

💛  - Coveralls


Don't use $BUILDPLATFORM image for goreleaser

Description of the change: Removes the --platform=$BUILDPLATFORM argument
Motivation for the change: When specifying the platform as $BUILDPLATFORM, amd64 binaries are taken. This leads to the image not being multi-arch, but still having an amd64 busybox binary.
The util init container of jobs are failing with an exec /bin/cp: exec format error.
Architectural changes: None

Testing remarks:

Reviewer Checklist

[ ] Implementation matches the proposed design, or proposal is updated to match implementation
[ ] Sufficient unit test coverage
[ ] Sufficient end-to-end test coverage
[ ] Bug fixes are accompanied by regression test(s)
[ ] e2e tests and flake fixes are accompanied evidence of flake testing, e.g. executing the test 100(0) times
[ ] tech debt/todo is accompanied by issue link(s) in comments in the surrounding code
[ ] Tests are comprehensible, e.g. Ginkgo DSL is being used appropriately
[ ] Docs updated or added to /doc
[ ] Commit messages sensible and descriptive
[ ] Tests marked as [FLAKE] are truly flaky and have an issue
[ ] Code is properly formatted

Further remarks: I already opened #2890 to increase multi-arch/arm64 compatibility. In case wanted, I can also incorporate this change into that PR

Any updates on this? This is blocking us from using OLM on ARM.

/ok-to-test

Have rebased the branch and added a sign-off to make it compliant with the DCO policy in the repo, would like to see it get merged

/approve

Thanks for pulling this in! @dmesser , do you know when this might be released? We're excited to start running OLM in ARM. :)

Can we get a minor version release with this fix?

Released v0.24.0


Improve navbar

Hey @roannav
I have visited the website and found small bug.

As you can see in the above picture the width of the navbar is exceeded.  If we manage the width to the same as its container it will enhance the quality and improves user experience.

Hi @sai-kumar0, Thanks for spotting this bug!  I've assigned you to this task.

hey @roannav
I have fixed the navbar.
Here is the link of the fixed website. Try check it and text me if there are any issues
https://sai-kumar0.github.io/matrix-movies-website-hacktoberfest/


refactor connection logic on electron

The code that coordinates communication with the routing daemon and launches ss-local and tun2socks has evolved over time; this PR refactors that code to be clearer, easier to change, and faster.
The key part is a new class, ConnectionManager, which coordinates the three helpers according to the mediator pattern and a simple lifecycle: the connection remains up until any helper fails, at which point they're all torn down. It's Promise-based and "one shot", with minimal state - as are a few other new and refactored classes.
Other improvements:

no more RESET_ROUTING at the start of every connect (thanks to https://github.com/Jigsaw-Code/outline-client/pull/535)
much clearer console logging from the main process
fix a bizarre routing daemon crash on Windows
abort when ss-local or tun2socks exit unexpectedly.

It's quite a bit of code so I'm happy to sit down with you - in the meantime, the biggest help would be testing any of the following on your system (I've tested each on my own systems and VMs):

multiple network interfaces
UDP support changes
installing the routing daemon (Linux)
suspend and resume
autostart

@alalamav Regarding the intermittent failures we saw due to the UDP test failing after network changes, I made this code more resilient to failures - shouldn't be an issue now. PTAL.

@alalamav Two fixes since Friday:

workaround a weird suspend/resume issue in Electron
eliminate the duplicate routes you noticed when switching wifi networks

PTAL!

@alalamav Many thanks for the tricky review!


validate props can't work

bug report

What is the current behavior?

validate props can't work
What is the expected behavior?
validate props can validate
Sandbox Link

What's your environment?

{
    "redux": "^3.7.2",
    "redux-form": "^7.2.1",
    "redux-form-material-ui": "^5.0.0-beta.2"
}

Other information

required function  can't validate

Try creating the validation function outside of render() function. I.e.,
const require = () => value => ...

const requireEmail = required()

class Node extends React.Compinent {
  ...
  render() {
    ...
    return (
      ...
          <Field
            component={TextField}
            name="email"
            label="email"
            placeholder="please input"
            validate={requireEmail}
          />
    );
  }
}

See #3832.

@zonr I see ！if the validate prop changes the field will be re-registered.


Dev & 1.10: Dynamic form field binding issue

Just re-tried in the last dev branch and 1.10 release. It was working in a previous version but maybe here i'm doing something wrong.
Repro:

Create a content type with a field of type text.
Create a dynamic form with the CreateContent option and select the above content type.
Insert a text form field and bind it to the text field of the above content type.
Display the form on front end, input a text in the form field and submit.
Edit the created content item in the dashboard, there is no value.

Note: Trying this, i could see again the other issue where, for most of the element editors, as soon as a checkbox is saved as checked, it can't be saved again as unchecked. Can be fixed for me with #6339.
Best

@sfmskywalker