Exception while invoking method 'forgotPassword'

I'm getting below exception after latest telescope version update when sending mails.

I20150323-15:40:35.488(5.5)? Exception while invoking method 'forgotPassword' SenderError: Mail from command failed - 501 : domain literals not allowed
I20150323-15:40:35.488(5.5)?     at Object.Future.wait (/root/.meteor/packages/meteor-tool/.1.0.41.yumiah++os.linux.x86_64+web.browser+web.cordova/meteor-tool-os.linux.x86_64/dev_bundle/server-lib/node_modules/fibers/future.js:326:15)
I20150323-15:40:35.488(5.5)?     at smtpSend (packages/email/email.js:91:1)
I20150323-15:40:35.488(5.5)?     at Object.Email.send (packages/email/email.js:168:1)
I20150323-15:40:35.489(5.5)?     at Object.Email.send (packages/meteorhacks:kadira/lib/hijack/email.js:10:1)
I20150323-15:40:35.489(5.5)?     at Object.Accounts.sendResetPasswordEmail (packages/accounts-password/password_server.js:408:1)
I20150323-15:40:35.489(5.5)?     at [object Object].Meteor.methods.forgotPassword (packages/accounts-password/password_server.js:358:1)
I20150323-15:40:35.489(5.5)?     at [object Object].methodMap.(anonymous function) (packages/meteorhacks:kadira/lib/hijack/wrap_session.js:182:1)
I20150323-15:40:35.489(5.5)?     at maybeAuditArgumentChecks (packages/ddp/livedata_server.js:1599:1)
I20150323-15:40:35.489(5.5)?     at packages/ddp/livedata_server.js:648:1
I20150323-15:40:35.489(5.5)?     at [object Object]._.extend.withValue (packages/meteor/dynamics_nodejs.js:56:1)
I20150323-15:40:35.489(5.5)?     - - - - -
I20150323-15:40:35.489(5.5)?     at SMTPClient._actionMAIL (/root/.meteor/packages/email/.1.0.5.di98ze++os+web.browser+web.cordova/npm/node_modules/simplesmtp/lib/client.js:879:23)
I20150323-15:40:35.490(5.5)?     at SMTPClient._onData (/root/.meteor/packages/email/.1.0.5.di98ze++os+web.browser+web.cordova/npm/node_modules/simplesmtp/lib/client.js:329:29)
I20150323-15:40:35.490(5.5)?     at CleartextStream.emit (events.js:95:17)
I20150323-15:40:35.490(5.5)?     at CleartextStream. (_stream_readable.js:764:14)
I20150323-15:40:35.490(5.5)?     at CleartextStream.emit (events.js:92:17)
I20150323-15:40:35.490(5.5)?     at emitReadable_ (_stream_readable.js:426:10)
I20150323-15:40:35.490(5.5)?     at _stream_readable.js:419:7
I20150323-15:40:35.490(5.5)?     at process._tickCallback (node.js:419:13)

It seems issue in the new telescope "Table scope" release.
I had Moved my code to previous version, then my mail sending is fine.
Please help.

@splendido any idea what's going on?

Mail from command failed - 501 : domain literals not allowed

I'd say it's some weird configuration for the sender...
The traceback goes down to Meteor.methods.forgotPassword and to smtpSend, then probably there's something wrong in the email templates configuration.
...but see the latest release notes about Meteor Accounts system.
It seems that to specify the from you now need a function rather than a static string.
How is this dealt with in Telescope?

See also the full docs about Accounts.emailTemplates

Hey, @renuanil08! Telescope has changed a lot in the past months, and there is a new React-based version, Telescope Nova (intro video). If you know Crater, it runs on the latest version.
The Legacy version is no longer supported. I'm closing this issue.
I invite you to check the new version, it's awesome!
Happy hacking! 🚀
Ps: by the way, don't hesitate to join the Slack to ask any question, you are welcome! 👍


Customize Contact List Column

add information about customisation of columns in contact list view #135

@fakela can you address the conflict? I think it is from the restructuring, may be easier to make another PR perhaps!

@fakela can you address the conflict? I think it is from the restructuring, may be easier to make another PR perhaps!

@fakela can you address the conflict? I think it is from the restructuring, may be easier to make another PR perhaps!

@RCheesley, I will close this PR and make another one that has these changes updated because this conflict will be difficult to resolve in this PR


MM Project Introduction Slides Outline

Here is the outline of the Project Development (Business) Plan:
Page 1 - 2: Who are we?
Introduction to AMC, It is the project engagement entity.
Introduction to BUPT CAD, it is the host lab of AMC and MM project.
Page 3 - 4: What do we have?
Introduction to current capabilities and achievements in AI DL, AI CV, AI NLP. (Papers, Champions and so on)
Introduction to current resources in AI DL. (821 room, TPUs, Servers, Datasets, and so on)
Page 5 -6: Why we want to do this?
Introduction to MM project background. (Using the proposal word document. Using the GitHub project homepage content.)
Introduction to MM project potential scenarios or customers.
Page 7 - 8: The excitation or power source or enabler.
Introduction to @Huan. @Newip. @CAD Boss.
Introduction to the backer board. (Namelist of all those who already joined the events of "after-party". With their organization logos and one-sentence brief.)
Page 9 - 11: How this project goes?
Introduction to the project plan (4-stages).
Introduction to the project phase I objective and R&R.
The cases study of related projects.
Page 12 - 14: The project budget plan.
Introduction to budget plan.
Introduction to team plan and current team members.
Introduction to AMC members.
Page 15 - 17: How will you benefit from this project？
The open-source plan to the project and license model.
The engagement plan to sponsors, investors, customers.
TBD
Page 18: Thanks and Q&A.

Page n: How could this project benefit to users/customers?
Page n: Summary to strong-points / key-strengthens of this project.
Page 12: in Budget Plan page, add funding management tool introduction. "Openclective".

https://docs.google.com/presentation/d/1S3DQyyWljchR0Fg65cHVm6rYh3gfDAfZ-qgeFWGFDtY/edit#slide=id.g251d9112ad_1_0


Linux distro used by Nodes?

We are assessing leveraging AKS for one of our client projects. However, due to security and compliance requirements need to understand the Linux distribution used by the cluster nodes. Can you please provide some information? Couldn't find anything in the documentation.
Thanks

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: d501ff67-9208-8bcb-e8df-f09e9b16a802
Version Independent ID: e3fc3851-ddc4-d26c-251d-6ae53d714081
Content: Frequently asked questions for Azure Kubernetes Service (AKS)
Content Source: articles/aks/faq.md
Service: container-service
GitHub Login: @iainfoulds
Microsoft Alias: iainfou

@iainfoulds are you ware of what version of Linux AKS uses by default? I also do not find any information on this.

Can SSH to a node and use uname -r to see the kernel version and cat /etc/lsb-release to see the Ubuntu release.
On a cluster I recently deployed, nodes are currently based on Ubuntu 16.04.5 LTS and kernel 4.15.0-1021-azure

Thanks @iainfoulds!
@redlumxn I will close for now. If you have additional questions just let us know and we can reopen and continue.

Thanks to everyone.


[WIP] linbox: Add darwin support

Motivation for this change
Things done

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

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

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

@GrahamcOfBorg build linbox

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: linbox
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Success on x86_64-linux (full log)
Attempted: linbox
Partial log (click to expand)
make[2]: Entering directory '/build/source/examples/data'
make[2]: Nothing to be done for 'check'.
make[2]: Leaving directory '/build/source/examples/data'
make[2]: Entering directory '/build/source/examples'
make[2]: Nothing to be done for 'check-am'.
make[2]: Leaving directory '/build/source/examples'
make[1]: Leaving directory '/build/source/examples'
make[1]: Entering directory '/build/source'
make[1]: Leaving directory '/build/source'
/nix/store/6mhrf02f0mjybdxnlzw6s8bpw3ga2704-linbox-1.5.2

Success on aarch64-linux (full log)
Attempted: linbox
Partial log (click to expand)
make[2]: Entering directory '/build/source/examples/data'
make[2]: Nothing to be done for 'check'.
make[2]: Leaving directory '/build/source/examples/data'
make[2]: Entering directory '/build/source/examples'
make[2]: Nothing to be done for 'check-am'.
make[2]: Leaving directory '/build/source/examples'
make[1]: Leaving directory '/build/source/examples'
make[1]: Entering directory '/build/source'
make[1]: Leaving directory '/build/source'
/nix/store/hj4ffhyy5y65s2ch8a80xwy8qxv4nrkc-linbox-1.5.2

This depends on #45001

@GrahamcOfBorg eval
@GrahamcOfBorg build linbox

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: linbox
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Depends on #45013

Timed out, unknown build status on aarch64-linux (full log)
Attempted: linbox
Partial log (click to expand)
libtool: link: g++ -O2 -Wall -g -I.. -I/nix/store/7xhkxgq1nnq9rmqwjlqw8yqfcs0g4z1z-givaro-4.0.4/include -fabi-version=6 -fopenmp -o test-solve test-solve.o -fopenmp  -L/nix/store/7xhkxgq1nnq9rmqwjlqw8yqfcs0g4z1z-givaro-4.0.4/lib /nix/store/7xhkxgq1nnq9rmqwjlqw8yqfcs0g4z1z-givaro-4.0.4/lib/libgivaro.so -lm /nix/store/qmaa42qqjq97n5n9j0p43ps97rb2qaiz-gmp-6.1.2/lib/libgmpxx.so /nix/store/qmaa42qqjq97n5n9j0p43ps97rb2qaiz-gmp-6.1.2/lib/libgmp.so /nix/store/ri3iwhv860fq7nkcyc8aqj586idj87p2-gcc-7.3.0-lib/lib/../lib64/libstdc++.so -lopenblas -fopenmp -Wl,-rpath -Wl,/nix/store/7xhkxgq1nnq9rmqwjlqw8yqfcs0g4z1z-givaro-4.0.4/lib -Wl,-rpath -Wl,/nix/store/qmaa42qqjq97n5n9j0p43ps97rb2qaiz-gmp-6.1.2/lib -Wl,-rpath -Wl,/nix/store/ri3iwhv860fq7nkcyc8aqj586idj87p2-gcc-7.3.0-lib/lib/../lib64 -Wl,-rpath -Wl,/nix/store/7xhkxgq1nnq9rmqwjlqw8yqfcs0g4z1z-givaro-4.0.4/lib -Wl,-rpath -Wl,/nix/store/qmaa42qqjq97n5n9j0p43ps97rb2qaiz-gmp-6.1.2/lib -Wl,-rpath -Wl,/nix/store/ri3iwhv860fq7nkcyc8aqj586idj87p2-gcc-7.3.0-lib/lib/../lib64
PASS: test-solve
g++ -DHAVE_CONFIG_H -I. -I..    -O2  -Wall -g  -I..  -I/nix/store/7xhkxgq1nnq9rmqwjlqw8yqfcs0g4z1z-givaro-4.0.4/include -fabi-version=6 -fopenmp -c -o test-fgemv.o test-fgemv.C
/nix/store/7q3ayirslrcva28wava6zpjcflcz1h3b-bash-4.4-p23/bin/bash ../libtool  --tag=CXX   --mode=link g++ -O2  -Wall -g  -I..  -I/nix/store/7xhkxgq1nnq9rmqwjlqw8yqfcs0g4z1z-givaro-4.0.4/include -fabi-version=6 -fopenmp   -o test-fgemv test-fgemv.o  -L/nix/store/7xhkxgq1nnq9rmqwjlqw8yqfcs0g4z1z-givaro-4.0.4/lib -lgivaro -lgmp -lgmpxx  -fopenmp -lopenblas
libtool: link: g++ -O2 -Wall -g -I.. -I/nix/store/7xhkxgq1nnq9rmqwjlqw8yqfcs0g4z1z-givaro-4.0.4/include -fabi-version=6 -fopenmp -o test-fgemv test-fgemv.o -fopenmp  -L/nix/store/7xhkxgq1nnq9rmqwjlqw8yqfcs0g4z1z-givaro-4.0.4/lib /nix/store/7xhkxgq1nnq9rmqwjlqw8yqfcs0g4z1z-givaro-4.0.4/lib/libgivaro.so -lm /nix/store/qmaa42qqjq97n5n9j0p43ps97rb2qaiz-gmp-6.1.2/lib/libgmpxx.so /nix/store/qmaa42qqjq97n5n9j0p43ps97rb2qaiz-gmp-6.1.2/lib/libgmp.so /nix/store/ri3iwhv860fq7nkcyc8aqj586idj87p2-gcc-7.3.0-lib/lib/../lib64/libstdc++.so -lopenblas -fopenmp -Wl,-rpath -Wl,/nix/store/7xhkxgq1nnq9rmqwjlqw8yqfcs0g4z1z-givaro-4.0.4/lib -Wl,-rpath -Wl,/nix/store/qmaa42qqjq97n5n9j0p43ps97rb2qaiz-gmp-6.1.2/lib -Wl,-rpath -Wl,/nix/store/ri3iwhv860fq7nkcyc8aqj586idj87p2-gcc-7.3.0-lib/lib/../lib64 -Wl,-rpath -Wl,/nix/store/7xhkxgq1nnq9rmqwjlqw8yqfcs0g4z1z-givaro-4.0.4/lib -Wl,-rpath -Wl,/nix/store/qmaa42qqjq97n5n9j0p43ps97rb2qaiz-gmp-6.1.2/lib -Wl,-rpath -Wl,/nix/store/ri3iwhv860fq7nkcyc8aqj586idj87p2-gcc-7.3.0-lib/lib/../lib64
PASS: test-fgemv
g++ -DHAVE_CONFIG_H -I. -I..    -O2  -Wall -g  -I..  -I/nix/store/7xhkxgq1nnq9rmqwjlqw8yqfcs0g4z1z-givaro-4.0.4/include -fabi-version=6 -fopenmp -c -o regression-check.o regression-check.C
building of '/nix/store/dz69pjwjyigxpqkwa51qr8cgln0f7nhv-fflas-ffpack-2.3.2.drv' timed out after 3600 seconds
cannot build derivation '/nix/store/6aw3qsc5i7yy79hp6zrbcx8chpg1jw1x-linbox-1.5.2.drv': 1 dependencies couldn't be built
error: build of '/nix/store/6aw3qsc5i7yy79hp6zrbcx8chpg1jw1x-linbox-1.5.2.drv' failed

Depends on #45013.

Please rebase and remove the wip tag if appropriate.
Out of curiosity: Do you know how many more sage dependencies need fixing?

Also best leave a comment when you're done, github is really bad at notifications with stuff other than comments.

@timokau All done.

@GrahamcOfBorg build linbox

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: linbox
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Does this really suffer the same blas issue as fflas_ffpack or do you just avoid the dependency on two different versions of blas?

Success on x86_64-linux (full log)
Attempted: linbox
Partial log (click to expand)
make[1]: Leaving directory '/build/source'
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/jljsy1nd38xffi0601jw7h9smy4jhx27-linbox-1.5.2
shrinking /nix/store/jljsy1nd38xffi0601jw7h9smy4jhx27-linbox-1.5.2/lib/liblinbox.so.0.0.0
gzipping man pages under /nix/store/jljsy1nd38xffi0601jw7h9smy4jhx27-linbox-1.5.2/share/man/
strip is /nix/store/553rihc190vsyy8b22iqcq25a6489h8y-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/jljsy1nd38xffi0601jw7h9smy4jhx27-linbox-1.5.2/lib  /nix/store/jljsy1nd38xffi0601jw7h9smy4jhx27-linbox-1.5.2/bin
patching script interpreter paths in /nix/store/jljsy1nd38xffi0601jw7h9smy4jhx27-linbox-1.5.2
/nix/store/jljsy1nd38xffi0601jw7h9smy4jhx27-linbox-1.5.2/bin/linbox-config: interpreter directive changed from " /bin/bash" to "/nix/store/79b6s2wql94lwk8dyib2jc4fq8ixl13f-bash-4.4-p23/bin/bash"
checking for references to /build in /nix/store/jljsy1nd38xffi0601jw7h9smy4jhx27-linbox-1.5.2...

looks like you forgot to update platforms.

This does suffer from the same issue, building without this commit but with the fflas-ffpack commit fails tests.
I don't know how many more sage dependencies need fixing, I just keep rebuilding and fixing what fails.

Success on aarch64-linux (full log)
Attempted: linbox
Partial log (click to expand)
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/qp4hm51i8jd0q4dy6zd85h9qr6qc88lw-linbox-1.5.2
shrinking /nix/store/qp4hm51i8jd0q4dy6zd85h9qr6qc88lw-linbox-1.5.2/lib/liblinbox.so.0.0.0
gzipping man pages under /nix/store/qp4hm51i8jd0q4dy6zd85h9qr6qc88lw-linbox-1.5.2/share/man/
strip is /nix/store/4md2i310zklkkl5j41yw70gcwgn4kav5-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/qp4hm51i8jd0q4dy6zd85h9qr6qc88lw-linbox-1.5.2/lib  /nix/store/qp4hm51i8jd0q4dy6zd85h9qr6qc88lw-linbox-1.5.2/bin
patching script interpreter paths in /nix/store/qp4hm51i8jd0q4dy6zd85h9qr6qc88lw-linbox-1.5.2
/nix/store/qp4hm51i8jd0q4dy6zd85h9qr6qc88lw-linbox-1.5.2/bin/linbox-config: interpreter directive changed from " /bin/bash" to "/nix/store/x8npv3gr1rq1pf6gqpcdb9b68374pfd6-bash-4.4-p23/bin/bash"
checking for references to /build in /nix/store/qp4hm51i8jd0q4dy6zd85h9qr6qc88lw-linbox-1.5.2...
/nix/store/qp4hm51i8jd0q4dy6zd85h9qr6qc88lw-linbox-1.5.2

Okay, interesting. Maybe its just because of the indirect mixing of the two blas versions, maybe because the blas issue is more widespread and not an fflas_ffpack issue after all.
Okay, excited to see sage build on darwin :) When you fix the platform list this should be ready for merge.

@timokau Updated the platform list.

Success on x86_64-darwin (full log)
Attempted: linbox
Partial log (click to expand)
 /nix/store/vc4q7zqpxx15ckxshdxikf7c6vq57c5k-coreutils-8.29/bin/mkdir -p '/nix/store/1cvivvn9sskw5jn4wi9ksr84bkyqsh0z-linbox-1.5.2/lib/pkgconfig'
 /nix/store/vc4q7zqpxx15ckxshdxikf7c6vq57c5k-coreutils-8.29/bin/install -c -m 644 linbox.pc '/nix/store/1cvivvn9sskw5jn4wi9ksr84bkyqsh0z-linbox-1.5.2/lib/pkgconfig'
make[2]: Leaving directory '/private/tmp/nix-build-linbox-1.5.2.drv-0/source'
make[1]: Leaving directory '/private/tmp/nix-build-linbox-1.5.2.drv-0/source'
post-installation fixup
gzipping man pages under /nix/store/1cvivvn9sskw5jn4wi9ksr84bkyqsh0z-linbox-1.5.2/share/man/
strip is /nix/store/bg39mxc401qqxgjasxfgardi6xl2ikmc-cctools-binutils-darwin/bin/strip
stripping (with command strip and flags -S) in /nix/store/1cvivvn9sskw5jn4wi9ksr84bkyqsh0z-linbox-1.5.2/lib  /nix/store/1cvivvn9sskw5jn4wi9ksr84bkyqsh0z-linbox-1.5.2/bin
patching script interpreter paths in /nix/store/1cvivvn9sskw5jn4wi9ksr84bkyqsh0z-linbox-1.5.2
/nix/store/1cvivvn9sskw5jn4wi9ksr84bkyqsh0z-linbox-1.5.2/bin/linbox-config: interpreter directive changed from " /bin/bash" to "/nix/store/avxlkpsr36xpnsy0byq2c4vxk6sw157a-bash-4.4-p23/bin/bash"

Success on x86_64-linux (full log)
Attempted: linbox
Partial log (click to expand)
make[1]: Leaving directory '/build/source'
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/jljsy1nd38xffi0601jw7h9smy4jhx27-linbox-1.5.2
shrinking /nix/store/jljsy1nd38xffi0601jw7h9smy4jhx27-linbox-1.5.2/lib/liblinbox.so.0.0.0
gzipping man pages under /nix/store/jljsy1nd38xffi0601jw7h9smy4jhx27-linbox-1.5.2/share/man/
strip is /nix/store/553rihc190vsyy8b22iqcq25a6489h8y-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/jljsy1nd38xffi0601jw7h9smy4jhx27-linbox-1.5.2/lib  /nix/store/jljsy1nd38xffi0601jw7h9smy4jhx27-linbox-1.5.2/bin
patching script interpreter paths in /nix/store/jljsy1nd38xffi0601jw7h9smy4jhx27-linbox-1.5.2
/nix/store/jljsy1nd38xffi0601jw7h9smy4jhx27-linbox-1.5.2/bin/linbox-config: interpreter directive changed from " /bin/bash" to "/nix/store/79b6s2wql94lwk8dyib2jc4fq8ixl13f-bash-4.4-p23/bin/bash"
checking for references to /build in /nix/store/jljsy1nd38xffi0601jw7h9smy4jhx27-linbox-1.5.2...

Thanks!


apps: Don't print hostname on bio_out during connect.

Printing the hostname on bio_out clutters the output and breaks pipe like forwarding via openssl.
Print the hostname via bio_err.
Fixes #23013

Are there any tests that exercise client/server communication using pipes?  Maybe you could modify one to check for the desired behaviour (so that we do not regress later on).  It would be good to add such a test to your PR.

@t8m :  I see you added the label tests:exempted.  In my previous comment, I noted that it would be nice to have a test for this so we do not regress later on.  Shouldn't a test be added?

The fix was trivial so it would be wrong to ask for a fairly non-trivial test here. Of course the label does not mean there MUST NOT be a test. If anybody is willing to write it - either the author in this PR or anybody in a separate PR - be welcome.

24 hours has passed since 'approval: done' was set, but as this PR has been updated in that time the label 'approval: ready to merge' is not being automatically set.  Please review the updates and set the label manually.

Merged to the master and 3.2 branches. Thank you for your contribution.


Add ability to make window maximized

Should be this with SW_SHOWMAXIMIZED I think
https://msdn.microsoft.com/en-us/library/windows/desktop/ms633548(v=vs.85).aspx
Could also add functions for minimizing, making window get focus, making taskbar blink / light up,

I can make almost the same things on macOS, but I think we have to get most important and frequency used things and implement them.

something like function
defos.set_window_mode(param)
and parameters
defos.SHOW_MAXIMIZED
defos.SHOW_FULLSCREEN
defos.SHOW_WINDOWED
or something like this.
I am not sure about case of using : window get focus, making taskbar blink / light up,

WIP version going to add it in properly later
local M = {}

local ffi = package.preload.ffi()

function M.maximize_window()
	if(ffi.os == "Windows") then

	  -- definitions
	  ffi.cdef([[
			typedef unsigned int LONG;
			typedef long long LONG_PTR;
			typedef void* PVOID;
			typedef PVOID HANDLE;
			typedef HANDLE HWND;
			typedef unsigned int UINT;
			typedef bool BOOL;

			HWND GetActiveWindow();
			BOOL ShowWindow(HWND hWnd, int nCmdShow);

		]])

		-- load User32.dll
		local user32 = ffi.load("User32")

		local SW_SHOWMAXIMIZED = 3

		local ptr = user32.GetActiveWindow()

		user32.ShowWindow(ptr, SW_SHOWMAXIMIZED)

	end
end

return M

Fully agree with you about version 1.0 and 2.0 .
And thanks for the maximize option ( option key + shift + green button) I never known about it =)))

As I undestand this issue is done?
new methods:
defos.toggle_maximize()
and
defos.is_maximize()
was added


Analysis of CSBS, CDS, and NYT case reports

Began looking at the county level data being reported by
CSBS
CDS
NYT
Initial takeaways are that there are some states not being monitored by CDS, but at the county level, there are some large discrepancies in the reported cases by county. I haven't been able to dig into why the gaps exist or who is most accurate, but this does give a general picture of "where are we"

Thanks @Erin-Boehmer!


incorrectly fetching files

@AviralGarg1993 Can you include more information... what were you trying to accomplish? What was trying to fetch the file? What are the files for? Steps to reproduce?

I shall do that later today.


Support Vue 3

https://github.com/rigor789/vue-scrollto/issues/327
I have made it available for Vue 3.
Could you check this ?
Changes

Add new method name of directive hooks ( https://v3.vuejs.org/guide/migration/custom-directives.html#_3-x-syntax )
Use globalProperties instead of Vue.prototype ( https://v3.vuejs.org/api/application-config.html#globalproperties )

@rigor789 Thank you! I have committed those.

:tada: This PR is included in version 2.19.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Working with views

It's needed to follow with the views of the project.

Finished and successfully pushed into master.


Problem with inputmask("isComplete"), returns false when its true

I have made a jquery validator that calls inputmask("isComplete").
I have a simple input mask of type inputmask("mm/yyyy")
The bug is very specific, if to reproduce:

When the page loads, the input has a default value of "02/2017"
If you want to change the input to "11/2016", one of the fastest ways is to do the following:
first select the '7' at the end and change it to a '6'
then select the '02' at the start and delete
At this point, if you click outside of the input, the jquery validator is triggered and it shows an error, and it should, because the input would be 'mm/2016'. If you do not click outside, to trigger the validation, the bug does not seem to happen.
Now clicking back on the 'mm' in the input and typing in '11', the typing triggers the validator again, but it keeps saying that the input is invalid. But in the input field the text is "11/2016".

At this point the only way to fix it, is to retype the entire input from start to finish, changing only parts of the input, doesn't work. Also, this only happens one time, if i try to reproduce the bug without refreshing the page, it works as expected.

After some additional work on this issue, I resolved it by updating the input mask library, it appears i was not using the latest version as i thought i was.


Incorrect CREATE2 addresses when not broadcast

Component
Forge
Have you ensured that all of these are up to date?

[X] Foundry
[X] Foundryup

What version of Foundry are you on?
forge 0.2.0 (7b45265 2023-11-21T00:18:30.267248000Z)
What command(s) is the bug in?
No response
Operating System
macOS (Apple Silicon)
Describe the bug
When trying to deploy a contract using a salt calculated using cast create2, it works correctly when vm.startBroadcast() is called (and pointing to a local anvil node) - but does not generate the correct address when not broadcast.
The following script will fail the require() statement at the end - but uncommenting the vm.startBroadcast() line will cause it to pass.
// SPDX-License-Identifier: MIT
pragma solidity ^0.8.20;

import {Script, console2} from "forge-std/Script.sol";

import {Counter} from "../src/Counter.sol";

contract CounterScript is Script {
    function run() external {
        // vm.startBroadcast();
        bytes32 counterInitCodeHash = keccak256(type(Counter).creationCode);

        console2.log("Counter initCodeHash: ");
        console2.logBytes32(counterInitCodeHash);

        // $ cast create2 --starts-with 0x000000 --init-code-hash 0x479d7e8f31234e208d704ba1a123c76385cea8a6981fd675b784fbd9cffb918d
        //
        // Starting to generate deterministic contract address...
        // Successfully found contract address(es) in 2.492678083s
        // Address: 0x0000002e9eEF048A3ccDf115aF53A51Ae312870d
        // Salt: 0x0000000000000000000000000000000000000000000000006d3aaf0100000000<PHONE_NUMBER>613191168)

        address expectedAddress = address(0x0000002e9eEF048A3ccDf115aF53A51Ae312870d);
        bytes32 salt = bytes32(0x0000000000000000000000000000000000000000000000006d3aaf0100000000);

        Counter counter = new Counter{salt: salt}();
        console2.log("Counter address: %s", address(counter));

        require(address(counter) == expectedAddress, "Counter address mismatch");

        // vm.stopBroadcast();
    }
}

Example repo: https://github.com/0xCLARITY/test-create2

I also ran into this issue, still not working on forge 0.2.0 (14daacfe 2024-04-23T13:27:48.189406000Z).

See https://github.com/foundry-rs/foundry/pull/6656, you can set  always_use_create_2_factory = true flag which should resolve this :)


[WIP] [ASF] ASF Publish

Why are the changes needed?

How was this patch tested?

[ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible

[ ] Add screenshots for manual tests if appropriate

[ ] Run test locally before make a pull request

Codecov Report

Merging #874 (93117db) into master (f4fb822) will increase coverage by 0.10%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master     #874      +/-   ##
============================================
+ Coverage     78.68%   78.79%   +0.10%
  Complexity       10       10
============================================
  Files           135      137       +2
  Lines          5151     5187      +36
  Branches        644      644
============================================
+ Hits           4053     4087      +34
- Misses          746      747       +1
- Partials        352      353       +1

Impacted Files
Coverage Δ

...org/apache/kyuubi/operation/OperationManager.scala
74.19% <0.00%> (-2.48%)
:arrow_down:

...rg/apache/kyuubi/engine/spark/SparkSQLEngine.scala
71.87% <0.00%> (-1.98%)
:arrow_down:

...ala/org/apache/kyuubi/session/SessionManager.scala
52.94% <0.00%> (ø)

.../scala/org/apache/spark/kyuubi/ui/EnginePage.scala
96.55% <0.00%> (ø)

...n/scala/org/apache/spark/kyuubi/ui/EngineTab.scala
85.71% <0.00%> (ø)

...pache/kyuubi/sql/KyuubiQueryStagePreparation.scala
80.39% <0.00%> (+0.98%)
:arrow_up:

...org/apache/spark/kyuubi/SQLOperationListener.scala
93.87% <0.00%> (+2.04%)
: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 f4fb822...93117db. Read the comment docs.


consider changing MODEL_CACHE_DISABLED to MODEL_CACHE_ENABLED

this is a bit nitpicky but the thing is every other package that I've ever used that can be disabled via the config uses a SOMETHING_ENABLED format
Laravel Telescope, Laravel Debugbar, Laravel ResponseCache to name a few
Yours is the opposite and it's just not very intuitive IMHO and just now confused me as I meant to disable it while debugging a problem and didn't immediately realize I had to use the opposite boolean for your package
Possibly you could support the new key while still also supporting the old one. Or rename the key in a new major version.. Food for thought

Thanks @vesper8, yea, I had noticed the same thing. I will look into changing it for the next breaking release.

@vesper8 This is now in release 0.6.0. Let me know how it works for you.


Language server support

The whole grafonnet library is generated by a function which means that language servers can't extract information about the object it returns. For a library of this size it would be great to have autocomplete in editors so that we don't have to tab over to a browser so often. One idea to accomplish this is to use the schema to generate a "documentation overlay" that wraps the generated api with matching function  signatures and doc comments. For example:
// grafonnet/gen/grafonnet-vX.Y.Z/main.libsonnet

local grafonnet = import 'github.com/grafana/grafonnet/grafonnet-base/main.libsonnet';
local schemas = import './schemas.libsonnet';
local version = importstr './grafana-version';
local g = grafonnet.new(schemas, version);

{
  panel: {
    timeSeries: {
      // Creates a new timeSeries panel with a title.
      new(title): g.panel.timeSeries.new(title),
      // ..
    },
    // ...
  },
  // ...
}

Isn't this the same (effort) as making a static library?

There are multiple ways to approach this problem.
Some of the proposals:

generate static library
generate static overlay (this issue)
provide support for dynamic library in LSP (https://github.com/grafana/jsonnet-language-server/issues/110)

I'd be more than happy to generate a static overlay on our end if that's not the direction this project wants to go in. I tried writing a script to do so but my Jsonnet functional programming skills just weren't up to par lol.

@ebracho Grafonnet is now statically generated, which means it can work with the language server now.


remove intrinsic that is now implemented in the rustc side

Since https://github.com/rust-lang/rust/pull/80040, we can rely on the pass introduced in https://github.com/rust-lang/rust/pull/79049 to lower away forget.

@bors r+

:pushpin: Commit 65f5c27d61a401f7429a1b3b52026118e1050def has been approved by RalfJung

:hourglass: Testing commit 65f5c27d61a401f7429a1b3b52026118e1050def with merge e18c681eeac9a447616dbb3035220eabe4d4e2b1...

:sunny: Test successful - checks-actions
Approved by: RalfJung
Pushing e18c681eeac9a447616dbb3035220eabe4d4e2b1 to master...


Improving levt transformer training speed

🚀 Feature Request
Make training levenshtein transformer faster!
Motivation
The current training scheme under the levenshtein transformer framework for machine translation has a rather slow rate of convergence.
Compared to the standard transformer training scheme used in for wmt14 en-de. The suggested training parameters takes about 9-12 times as much time.
Improving training speeds would make the model viability for production use when less powerful hardware is available during training time.
Pitch
Let's keep an issue open to keep track of some issues with translation outputs! From there we can generalize some best practices that can be incorporated into optimizing training framework.
Alternatives
Additionally, other research papers can be used to theorycraft the information bottlenecks which are preventing the model from easily learning the features required to perform proper translation.
Additional context
Under local testing, replicating Vaswani et al. 2017 took 12 hours on a single V100 GPU with fp16 training.
To replicate Gu et al. 2019, 3 V100 GPUs and 57 hours are needed to perform training (similarly with fp16).
However, BLEU was still lower than reported.

An observation is that the 0th step in iterative decoding, (predicting the initial amount of masks and generating the starting sentence) is very different from the task of sentence correction.
Let's start with a guiding question. Why should a good language model be able to predict sequence length when there isn't a direct correlation between it (the length) and the linguistical contents of a sentence?
Could we perhaps improve the training strategy by removing the need for the model to predict the initial length?


Rocksdb via mason

This PR moves to depending on rocksdb via mason. This requires one-time manual install of mason and rocksdb locally. See .travis.yml/Readme diff for how to do it.

Tests aren't green here but not because of a Mason problem, so I'm going to merge and then triage in the main rocksdb branch.


Improve docs and error handling for optional imports

The latest release (0.0.16) has better docs, and better handling for absence of any optional dependencies

The latest release (0.0.16) has better docs, and better handling for absence of any optional dependencies


Exploration using a realsense D435i

First of all, thank you so much for your great work!
I have been using it on my simulations using an OS64 and it works phenomenally!
The thing is, I'm currently trying to get it to work using only the depth point cloud from a realsense camera installed in front of the UAV.
However, I have noticed that the TSDF map it generates does not fill the scan with free space unless there is a clear obstacle in front of it.
I'll explain: when I fly, let's say, inside a tunnel, some sort of cone of free space is generated from the sensor POV, but this free space is only close to the walls of that tunnel, so when I execute the exploration, the paths generated are always too close to the walls, as it cannot expand the graph in the "middle". You can see what I'm talking about in the images below:

As you can see, the tunnel is not being filled with free space, something that happens not when using an OS64 for instance.
I'm guessing this is more related to voxblox itself, so i'll leave here the parameters i'm using:

world_frame: map
use_tf_transforms: True
use_freespace_pointcloud: True
tsdf_voxels_per_side: 16
tsdf_voxel_size: 0.20
max_ray_length_m: 15.0
truncation_distance: 0.6
voxel_carving_enabled: True
use_sparsity_compensation_factor: True
sparsity_compensation_factor: 100.0
color_mode: "colors"
verbose: False
update_mesh_every_n_sec: 1.0
mesh_min_weight: 1e-4
slice_level: 1.0
method: "merged"
integration_order_mode: "sorted"
max_consecutive_ray_collisions: 0
publish_slices: False
publish_pointclouds: True
allow_clear: True
pointcloud_queue_size: 10
min_time_between_msgs_sec: 0.0
#max_block_distance_from_body: FLT_MAX
publish_tsdf_info: False
publish_slices: False
publish_traversable: True
traversability_radius: 0.4
enable_icp: False
icp_refine_roll_pitch: False
accumulate_icp_corrections: True
timestamp_tolerance_sec: 0.001 #0.001
publish_tsdf_map: True
publish_esdf_map: True
esdf_max_distance_m: 2.0
clear_sphere_for_planning: False
clear_sphere_radius: 0.8
use_const_weight: False
use_weight_dropoff: True
use_symmetric_weight_drop_off: False
clearing_ray_weight_factor: 0.01
weight_ray_by_range: False
min_ray_length_m: 0.5
occupancy_min_distance_voxel_size_factor: 1.0

Any help would be really appreciated! Thanks in advance!

In case anyone is interested, I managed to make it work by integrating the free space pointcloud as it is available with the param "use_freespace_pointcloud". Of course, this pointcloud has to be published in some other way, so I decided to make a ROS node for that.


msiafterburner requires Visual C++ 2008

Without vcredist2008 MSI Afterburner fails to start with error:
This application has failed to start because its side-by-side configuration is incorrect. Please see the application event log or use the command-line sxstrace.exe tool for more detail.

After installing Visual C++ Redistributable 2008 via scoop install vcredist2008 it launches.

As specified in susggests
https://github.com/lukesampson/scoop-extras/blob/8a72acdabec68aa217cce0a5efb1272264bc0c25/bucket/msiafterburner.json#L14-L15


Fixes iOS reload through metro "r" command key

Summary
This allows the iOS device to be reloaded through the metro command line, besides the fact that whenever packagerServerHost is called, it will only get the IP address once when debugging.

Changelog

[iOS] [Fixed] - Fixed connection of metro reload command to iOS device
Test Plan

Build any react-native project in debug mode to an iOS device connected through USB
Press the “r” key on the terminal that is running metro
The device should now reload the project

Can you provide some more context as to why this is the correct change? Also, please include a test plan that shows to the reviewers of this PR that this change works.

@TheSavior I think that this is the correct change because if no jsLocation is provided, the RCTBundleURLProvider will try to look for the device IP and use that to connect to metro.
The problem is that since that is only used for the RCTBridge, the RCTPackagerConnection does not have access to it and tries then to connect either through jsLocation or localhost.
Since iOS is not able to map localhost to the computer’s IP to which it is connected, it fails to connect to the websocket that allows the reload via “r” key on metro.
Based on that and knowing that the IP is the method used when no jsLocation is specified, in my opinion it makes sense to only get the IP once and then set it as the jsLocation since it will be the way to anything (from that time on) to connect to the remote computer.

Thanks for the context. I don't have any context on this code so I'll leave this PR for someone else to review / merge, but this additional info should make it easier for them.

@janicduplessis I didn't notice that it would saved it to NSUserDefaults. I just made packagerServerHost accessible and changed RCTPackagerConnection so that i uses it instead of jsLocation.
I did not make the access to packagerServerHost for Dev only because RCTBundleURLProvider uses it internally even for non Dev scenarios afaik (and packagerServerHost always returns the jsLocation for non Dev cases).

This has failing unit tests:
Failing tests:
	RNTesterUnitTests:
		-[RCTBundleURLProviderTests testBundleURL]

@TheSavior I lack the experience with Unit Tests of such kind, specially on Obj C, which I know very little.
How exactly can I check the failing test? Because the code I made was built directly on the react-native code that I have on a project and then moved to here once it worked well through the build.

@reyalpsirc You can open RNTester/RNTesterPods.xcworkspace in xcode (make sure to also run pod install in the RNTester folder before).
Then you can run tests there:

@TheSavior do you have any more log about the failure? Weird because it passed OSS CI.
RCTBundleURLProviderTests
    ✓ testBundleURL (0.042 seconds)
    ✓ testIPURL (0.004 seconds)
    ✓ testLocalhostURL (0.004 seconds)

Test Case '-[RCTBundleURLProviderTests testBundleURL]' started.
2020-04-02 10:54:52.894265-0700 xctest[75291:47235943] Task <5CA7F9B8-D968-43A2-8417-F1D728AE77EE>.<1> finished with error [-1001] Error Domain=NSURLErrorDomain Code=-1001 "The request timed out." UserInfo={NSUnderlyingError=0x7fcfbfea8170 {Error Domain=kCFErrorDomainCFNetwork Code=-1001 "(null)" UserInfo={_kCFStreamErrorCodeKey=-2102, _kCFStreamErrorDomainKey=4}}, NSErrorFailingURLStringKey=http://localhost:8081/status, NSErrorFailingURLKey=http://localhost:8081/status, _kCFStreamErrorDomainKey=4, _kCFStreamErrorCodeKey=-2102, NSLocalizedDescription=The request timed out.}
/data/sandcastle/boxes/trunk-hg-fbobjc-fbsource/xplat/js/react-native-github/RNTester/RNTesterUnitTests/RCTBundleURLProviderTests.m:75: error: -[RCTBundleURLProviderTests testBundleURL] : ((URL) equal to (localhostBundleURL())) failed: ("file:///usr/local/fbprojects/packages/xcode/149/xcode_11.3.0.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/Library/Xcode/Agents/main.jsbundle") is not equal to ("http://localhost:8081/test.jsbundle.bundle?platform=ios&dev=true&minify=false")
2020-04-02 10:54:52.896288-0700 xctest[75291:47236516] Connection 1: unable to determine interface type without an established connection
2020-04-02 10:54:52.896534-0700 xctest[75291:47236516] Connection 1: unable to determine fallback status without a connection
Test Case '-[RCTBundleURLProviderTests testBundleURL]' failed (60.545 seconds).
2020-04-02 10:54:52.901449-0700 xctest[75291:47236516] Task <5CA7F9B8-D968-43A2-8417-F1D728AE77EE>.<1> HTTP load failed, 0/0 bytes (error code: -999 [1:89])
Test Case '-[RCTBundleURLProviderTests testIPURL]' started.
Test Case '-[RCTBundleURLProviderTests testIPURL]' passed (0.008 seconds).
Test Case '-[RCTBundleURLProviderTests testLocalhostURL]' started.
Test Case '-[RCTBundleURLProviderTests testLocalhostURL]' passed (0.007 seconds).
Test Suite 'RCTBundleURLProviderTests' failed at 2020-04-02 10:54:52.919.

Ah. My guess is that since we run all of the tests without a network condition, something changed here causing it to try to make a network request. I'll retry the job to validate that it wasn't just a flake. Is there something in this test that was mocking this out before that isn't being used with now with this change?

@TheSavior I checked the test that you mentioned on my side and it seemed to work:

Also, correct me if I'm wrong but I think that it's not possible to build a test for this because it targets builds made for devices, which means that Automated tools like Circle CI would fail because they do not run these agains real devices?
And when I tried to run the tests on my iPad, XCode told me that "Logic Testing on iOS devices is not supported" which means that it's indeed not possible to make specific tests for devices in order to test the websocket connection between Metro and the device which is used to issue the "r" key reload command?

Apparently it passed when I re ran it

👍 Cool, found it weird that it failed since the PR doesn't actually touch the code that was tested by the failing test anymore (it did in the first version of the PR tho).


Throwing instance of 'std::invalid_argument'

When running Rem locally, the scripts launches without crashing, but the picture attached shows the errors.

Hey there, that is a missing arg in the config, add "ws_port":port to the main.json file. I did not update the readme yet to include it.


duplicate detection for new data

As an ODK user I want to add a facility to healthsites and know that if one exisits already on OSM it will update that record and not duplicate it.

it is already handle duplication @markherringer


Remove: Peppy.Osu! version 2021.1028.0

## .\Tools\YamlCreate.ps1 -SkipPRCheck -Mode 5 -PackageIdentifier Peppy.Osu! -PackageVersion 2021.1028.0

[X] Have you signed the Contributor License Agreement?
[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?

[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.0 schema?

Microsoft Reviewers: Open in CodeFlow

/azp run


ZEPPELIN-985 ] Fixed bug in the Pyspark completion

What is this PR for?
Currently, does not work 'pyspark completion'.
What type of PR is it?
Bug Fix
Todos

[x] - change standard output for completion to interpreter outer.

What is the Jira issue?
https://issues.apache.org/jira/browse/ZEPPELIN-985
How should this be tested?
Try keyword completion for pyspark interpreter.
Screenshots (if appropriate)
Before

After

Questions:

Does the licenses files need update? no
Is there breaking changes for older versions? no
Does this needs documentation? no

retry ci

@cloverhearts Thank you for quick fixing ! I closed my issue ZEPPELIN-984 since they are duplicated.

@cloverhearts I tested and it works well 👍

LGTM

Tested and it works well.
LGTM

Merge if there're no further discussions.


iOS integration test does not work with the latest version of flutter

Is there an existing issue for this?

[X] I have searched the existing issues
[X] I have read the guide to filing a bug

Steps to reproduce
Use latest version of flutter/dart and run recommended setup for integration testing :
flutter drive --driver=test_driver/integration_test.dart --flavor=qa -t lib/main_qa.dart --target=integration_test/boot_test.dart
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.16.0, on macOS 14.1.2 23B2091 darwin-arm64, locale en-US)
[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 15.0.1)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2023.1)
[✓] VS Code (version 1.84.2)
[✓] Connected device (5 available)
[✓] Network resources
• No issues found!
Expected results
It should load on IOS and execute tests
Actual results
The iOS emulator/device loads the app but it just waits and does nothing, in the trace log it says:
VMServiceFlutterDriver: Flutter Driver extension is taking a long time to become available. Ensure your test app (often "lib/main.dart") imports "package:flutter_driver/driver_extension.dart" and calls enableFlutterDriverExtension() as the first call in main().
Code sample
/integration_test/boot_test.dart
import 'package:flutter_signin_button/button_view.dart';
import 'package:flutter_test/flutter_test.dart';
import 'package:integration_test/integration_test.dart';
import 'package:app/constants.dart';

import 'package:app/main_qa.dart' as app;

void main() {
  IntegrationTestWidgetsFlutterBinding.ensureInitialized();

  testWidgets("boot up test", (WidgetTester tester) async {
    app.main();
    await tester.pumpAndSettle();

    expect(find.byType(SignInButton), findsOneWidget);
    expect(find.text(kSignInButtonText), findsOneWidget);
  });
}

/test_driver/integration_test.dart
import 'package:integration_test/integration_test_driver.dart';

Future<void> main() => integrationDriver();

CLI
flutter drive --driver=test_driver/integration_test.dart --flavor=qa -t lib/main_qa.dart --target=integration_test/boot_test.dart

Screenshots or Video

Screenshots / Video demonstration
[Upload media here]

Logs
Logs
VMServiceFlutterDriver: Flutter Driver extension is taking a long time to become available. Ensure your test app (often "lib/main.dart") imports "package:flutter_driver/driver_extension.dart" and calls enableFlutterDriverExtension() as the first call in main().

Flutter Doctor output
Doctor output
[✓] Flutter (Channel stable, 3.16.0, on macOS 14.1.2 23B2091 darwin-arm64, locale en-US)
[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 15.0.1)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2023.1)
[✓] VS Code (version 1.84.2)
[✓] Connected device (5 available)
[✓] Network resources

• No issues found!

Thanks for the report @mattbodley
Since you are using flutter drive, I think you are hitting https://github.com/flutter/flutter/issues/26968 that you can check and see if it resembles your case or not.
Also, another reference you can check if this works in your case or not.

Thanks @darshankawar I followed the instructions in #26968 and it worked! The only difference is that in the explanation the  FLUTTER_TARGET was suggested to be test_driver/app.dart but in my case I found this not to work and result in the same problem. What I did was change this to the specific test i.e. integration_test/boot_test.dart and it worked!
I don't this is a super good approach though because when I have more integration test files the FLUTTER_TARGET will each need to be changed in Xcode, so I'm sure this seems to work for some other reason
Also my run command is a bit more complex:
flutter drive --driver=test_driver/integration_test.dart --flavor=integration -t lib/main_integration.dart --target=integration_test/boot_test.dart
What do you think I need to do to make this work for multiple integration tests? Since in Xcode I had to set this (hardcode it) to that single integration test, meaning I cannot create another test e.g. integration_test/login_test.dart without changing this in Xcode.

Good to know that the linked issue worked in your case @mattbodley

What do you think I need to do to make this work for multiple integration tests?

For this, check if https://github.com/flutter/flutter/issues/115751 applies or helps your case further ?


Removing comments in html Parser

Dear all,
I have noticed the HTMLDocPreprocessor class could not remove comments in the html files I used with Snorkel.
Looking at other examples I found it works nicely if the BeautifulSoup call is changed as followed :
def parse_file(self, fp, file_name) :
...
txt = list(filter(self._cleaner, html.findAll(text=lambda text: not isinstance(text, Comment))))
...
Cheers.

Thanks for this!  We'd love to accept it as a PR if you're willing!  Closing for now in mean time


Kafka PubSub: Document certificate authentication

Documents the certificate authentication method in Kafka. This method is not new, but now a dedicate authType option exists to toggle this.
Thank you for helping make the Dapr documentation better!
Please follow this checklist before submitting:

[ ] Commits are signed with Developer Certificate of Origin (DCO - learn more)
[ ] Read the contribution guide
[ ] Commands include options for Linux, MacOS, and Windows within codetabs
[ ] New file and folder names are globally unique
[ ] Page references use shortcodes instead of markdown or URL links
[ ] Images use HTML style and have alternative text
[ ] Places where multiple code/command options are given have codetabs

In addition, please fill out the following to help reviewers understand this pull request:
Description

Issue reference

FYI @yaron2

Great stuff, thanks


why display problems of other projects in current project?

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version: 1.85.2
OS Version: windows 11

Steps to Reproduce:

open project A have problems and colse project.

open project B, problems of project A display in project B ???

These problems are generated by the extension and therefore extension is responsible to clean up or manage them. Please file the issue against the extension.


compile problem

I compile the project follow the wiki spec.
The compile process always blocked.
I only succeed one or twice.
the lates code compile log like this:
|
1 | use alvr_common::ALVR_VERSION;
|     ^^^^^^^^^^^^^^^^^^^^^^^^^
|
= note: #[warn(unused_imports)] on by default
warning: unused import: DictionaryDefault
--> alvr\session\src\settings.rs:4:23
|
4 | use settings_schema::{DictionaryDefault, EntryData, SettingsSchema, Switch, SwitchDefault};
|                       ^^^^^^^^^^^^^^^^^
warning: alvr_session (lib) generated 2 warnings
warning: field is never read: stream_id
--> alvr\sockets\src\stream_socket\mod.rs:168:5
|
168 |     stream_id: StreamId,
|     ^^^^^^^^^^^^^^^^^^^
|
= note: #[warn(dead_code)] on by default
warning: alvr_sockets (lib) generated 1 warning
Building [=======================> ] 262/266: alxr-...
I try many times,it always blocked like that and never finished.
It just blocked,didn't print any log.
May I have some information from you to help me solve the problem?
thanks.

@herehero Hey, is trying to make one of the Android builds on windows?

@herehero Hey, are you trying to make one of the Android builds on windows?

yes

I believe this is an issue with cargo-apk only on windows, the workaround is to either kill the (open)jdk process when there's %0 CPU activity or open alxr-engine-sys/android in android-studio, build it once there and leave it open, then build as normal.

I believe this is an issue with cargo-apk only on windows, the workaround is to either kill the (open)jdk process when there's %0 CPU activity or open alxr-engine-sys/android in android-studio, build it once there and leave it open, then build as normal.

It realy workd.Your suggestion has helped a lot.
thanks.


Chat bubble is blocking pagination on /dashboard/streams

From Tom at PlayDJ:

If we extend the page slightly, customers could continue scrolling, revealing the "Next" button

I was on .com -- has it been deployed there yet?


Placeholder translation to over (label place)

Sample:
https://material.io/components/text-fields#interactive-demo

Review feature/floating-hint-placeholder-labeled branch.

We are applying this improvement in the V3 controls.


Add boilerplate-reducing tools for doUpdateSet

It would be very useful if there was a way to handle common boilerplate cases for this with Postgres. For example, there could be doUpdateSetAll() (column_name = excluded. column_name for all columns in the query) and doUpdateSetAllExcept(['column_name_a', 'column_name_b']) to leave out a specific subset of column names.

I understand the value of this kind of helper for DX, but I don't like it for because there's no SQL equivalent for it. We'd need to generate different code on different dialects. Kysely normally doesn't do that. I wouldn't want to start here.
You could argue that this is similar to selectAll but the difference is that selectAll is always compiled as select *, regardless of the dialect.

doUpdateSetAllExcept(['column_name_a', 'column_name_b'])

I created a typescript type to help enforce this, which excludes id, noteId, created, and ord from the update set. However, being just a type, you still need to write runtime-code (i.e. updated: (x) => x.ref("excluded.updated")).
// the point of this type is to cause an error if something is added to CardEntity
type OnConflictUpdateCardSet = {
  [K in keyof CardEntity as Exclude<K, "id" | "noteId" | "created" | "ord">]: (
    x: ExpressionBuilder<
      OnConflictDatabase<DB, "card">,
      OnConflictTables<"card">
    >
  ) => RawBuilder<CardEntity[K]>
}

// usage
      await db
        .insertInto("card")
        .values(batches[i])
        .onConflict((db) =>
          db.doUpdateSet({
            updated: (x) => x.ref("excluded.updated"),
            due: (x) => x.ref("excluded.due"),
            deckIds: (x) => x.ref("excluded.deckIds"),
            cardSettingId: (x) => x.ref("excluded.cardSettingId"),
            state: (x) => x.ref("excluded.state"),
          } satisfies OnConflictUpdateCardSet)
        )
        .execute()

Taken from here. With a bit more work I think one could create a generalized typescript function like doUpdateSetAllExcept, but I'm too bad at typescript x|


FutureWarning import missing

Thanks to @hrdawson for spotting this.
When running esm1.5 using payu 1.1.4, payu setup fails at this line:
https://github.com/payu-org/payu/blob/83001a2b45ef786e178894f77dd9fbc0878e73c1/payu/models/um.py#L119
This is because FutureWarning is not imported.
Traceback (most recent call last):
  File "/g/data/vk83/apps/payu/1.1.4/bin/payu", line 10, in <module>
    sys.exit(parse())
  File "/g/data/vk83/apps/payu/1.1.4/lib/python3.10/site-packages/payu/cli.py", line 41, in parse
    run_cmd(**args)
  File "/g/data/vk83/apps/payu/1.1.4/lib/python3.10/site-packages/payu/subcommands/setup_cmd.py", line 26, in runcmd
    expt.setup(force_archive=force_archive)
  File "/g/data/vk83/apps/payu/1.1.4/lib/python3.10/site-packages/payu/experiment.py", line 439, in setup
    model.setup()
  File "/g/data/vk83/apps/payu/1.1.4/lib/python3.10/site-packages/payu/models/um.py", line 119, in setup
    raise FutureWarning(
FutureWarning: The `um_env.py` configuration file has been deprecated and should be relplaced with a yaml file. Convert `um_env.py` to `um_env.yaml` using [https://github.com/ACCESS-NRI/esm1.5-scripts/blob/main/config-files/UM/um_env_to_yaml.py]

Also the text is slightly unclear ... I think we expect um_env.py configuration to still work, so the warning text should be in the future tense (will be deprecated)

Thanks for creating this issue! Yeah it looks like it is treating FutureWarning as an exception.
@aidanheerdegen @blimlim, do we want to support loading environment variables from both um_env.py and um_env.yaml and so change the exception to a warning? If so, I have some changes in this branch that I think will implement that though will need to test it before opening a PR.

From what I remember at the time when discussing with @aidanheerdegen, it sounded like the best option was to deprecate the old um_env.py file rather than keeping support for it due to security issues with sourcing a python file, and so the desired behaviour was for um_env.py to no longer work with the latest release, and for an exception rather than warning to be raised. @aidanheerdegen just wanted to check whether this sounds right to you.
I'm not too good with all the different exception/warning types, but it seemed like raising a FutureWarning as an exception was the best option for raising an error about an already deprecated feature,  though definitely agree that any ways we can make it a bit clearer would be great!

Oh I see! If its trying to be an exception then we should raise an Error rather than a warning !

Ok, would a RuntimeError make sense instead? I am not sure of the best standard error types for deprecated features either

Oh I see! If its trying to be an exception then we should raise an Error rather than a warning !

Good idea!

Ok, would a RuntimeError make sense?

I think that sounds ok!
I just noticed a typo in the error message I'd written - should be "replaced" not "relplaced" :( .... If we are fixing this up anyway, do you think there are any changes that could make it a bit clearer? I'm wondering whether "... configuration file is no longer supported" is clearer than "... has been deprecated", or do you think it's much the same?


[GSSoC'23] Code Generator Animation Completed

Title and Issue number
Title - Code Generator Animation
Issue Number - 4428
Close #4428

Checklist:

[x] I have mentioned the issue number in my Pull Request.
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have created a helpful and easy to understand README.md

@MohitGupta121 @pranjay-poddar @Saurabh-kumar09 sir, please review this pull request

Sir, I attempted to fetch the repository and pull its content to create a pull request. However, I encountered issues due to the presence of a folder named 'Encipher | Decipher' that prevented me from successfully pulling the repository. To resolve this, I have decided to delete the local copy and then re-clone the repository to obtain the necessary files. After renaming the folder to avoid conflicts, I will proceed with creating the pull request.


Mac installation problems

Thanks a lot for your work!
Running into these problems:

Brew is still 2.0.9 - not compatible with the device I have.
The GitHub releases are not notarized, so hard[er] to run.

Could you please upgrade brew or notarize Mac releases?

Oops :) Wrong place it seems, sorry


missing module name in carla-0.9.9-py3.6-linux-x86_64.egg

Carla version: 0.9.9
Platform: Ubuntu 18.04
Problem description: After following the installation instructions in https://carla.readthedocs.io/en/latest/build_linux/, I failed at the last step, i.e. python3 spawn_npc.py
The error messages are listed below:
Traceback (most recent call last):
  File "spawn_npc.py", line 27, in <module>
    import carla
  File "<frozen importlib._bootstrap>", line 971, in _find_and_load
  File "<frozen importlib._bootstrap>", line 955, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 656, in _load_unlocked
  File "<frozen importlib._bootstrap>", line 626, in _load_backward_compatible
  File "../carla/dist/carla-0.9.9-py3.6-linux-x86_64.egg/carla/__init__.py", line 8, in <module>
  File "<frozen importlib._bootstrap>", line 971, in _find_and_load
  File "<frozen importlib._bootstrap>", line 955, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 656, in _load_unlocked
  File "<frozen importlib._bootstrap>", line 626, in _load_backward_compatible
  File "../carla/dist/carla-0.9.9-py3.6-linux-x86_64.egg/carla/libcarla.py", line 8, in <module>
  File "../carla/dist/carla-0.9.9-py3.6-linux-x86_64.egg/carla/libcarla.py", line 7, in __bootstrap__
TypeError: exec_module() missing 1 required positional argument: 'module'

I looked into the ../carla/dist/carla-0.9.9-py3.6-linux-x86_64.egg/carla/libcarla.py, and the following is its content:
def __bootstrap__():
    global __bootstrap__, __loader__, __file__
    import sys, pkg_resources
    from importlib.machinery import ExtensionFileLoader
    __file__ = pkg_resources.resource_filename(__name__, 'libcarla.cpython-36m-x86_64-linux-gnu.so')
    __loader__ = None; del __bootstrap__, __loader__
    ExtensionFileLoader(__name__,__file__).exec_module()
__bootstrap__()

I don't knnow how an egg file is generated here but I think there does miss a module name here(in exec_module() ). But I don't know how to modify it to make PythonAPI work. So I'm asking for some help here. Any suggestion/thoughts are warmly welcomed.

@bernatx could you please comment on this?

same problem here

Update: upgrade my Python from 3.6 to 3.7. and relaunch. Get new egg files. Everyting goes fine now.

Probably your previous .egg with version 3.6 was incorrect. If you don't want to upgrade Python version try to use make clean PythonAPI and see if the new .egg works.

I'm pretty sure I did make clean and make PythonAPI previously and I got the error again and again with Python3.6.
I'm no idea how carla generates .egg files, but I'm suspicious there is something wrong with the process to generate .egg files.
Though I solved this problem by upgrading Python and relaunch, it would be great if some collaborators of carla project can take a look at carla-0.9.9 with python3.6 to avoid the similar confusion in the future. Thanks.

I am facing the same issue as @jeffchen006. With Ubuntu 18.04, Python3.6 comes by default. I am getting .egg of 3.6 which fails to launch the python examples in ~/carla/PythonAPI/examples. I tried upgrading python to 3.7 but failed.
@jeffchen006 could you provide help with how did you upgrade your python from 3.6 to 3.7. And what are the following steps post python upgrade?
Your help is appreciated.

a workaround would be renaming the .egg file from  carla-0.9.9-py3.7-linux-x86_64.egg  to  carla-0.9.9-py3.6-linux-x86_64.egg  . it works for me with no issues


fix(ci): remove instance types with a disk

Benchmark results
No base data found for comparison.

Detailed results
All benchmarks are run on txs on the Benchmarking contract on the repository. Each tx consists of a batch call  to create_note and increment_balance, which guarantees that each tx has a private call, a nested private call, a public call, and a nested public call, as well as an emitted private note, an unencrypted log, and public storage read and write.
This benchmark source data is available in JSON format on S3 here.
Proof generation
Each column represents the number of threads used in proof generation.

Metric
1 threads
4 threads
16 threads
32 threads
64 threads

proof_construction_time_sha256
5,718
1,559
720
765
774

L2 block published to L1
Each column represents the number of txs on an L2 block published to L1.

Metric
8 txs
32 txs
64 txs

l1_rollup_calldata_size_in_bytes
772
772
772

l1_rollup_calldata_gas
6,868
6,868
6,880

l1_rollup_execution_gas
587,408
587,408
587,420

l2_block_processing_time_in_ms
1,372
5,126
10,173

l2_block_building_time_in_ms
32,183
126,956
254,191

l2_block_rollup_simulation_time_in_ms
32,002
126,312
252,916

l2_block_public_tx_process_time_in_ms
16,762
69,395
142,830

L2 chain processing
Each column represents the number of blocks on the L2 chain where each block has 16 txs.

Metric
5 blocks
10 blocks

node_history_sync_time_in_ms
15,247
28,595

node_database_size_in_bytes
21,262,416
37,982,288

pxe_database_size_in_bytes
29,868
59,425

Circuits stats
Stats on running time and I/O sizes collected for every kernel circuit run across all benchmarks.

Metric
1 leaves
16 leaves
64 leaves
128 leaves
512 leaves
1024 leaves
2048 leaves
4096 leaves
32 leaves

batch_insert_into_append_only_tree_16_depth_ms
11.3
18.3
N/A
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_count
16.7
31.8
N/A
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_ms
0.657
0.563
N/A
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_32_depth_ms
N/A
N/A
52.0
80.9
264
507
989
1,960
N/A

batch_insert_into_append_only_tree_32_depth_hash_count
N/A
N/A
95.9
159
543
1,055
2,079
4,127
N/A

batch_insert_into_append_only_tree_32_depth_hash_ms
N/A
N/A
0.532
0.499
0.480
0.473
0.469
0.468
N/A

batch_insert_into_indexed_tree_20_depth_ms
N/A
N/A
62.7
120
380
746
1,479
2,951
N/A

batch_insert_into_indexed_tree_20_depth_hash_count
N/A
N/A
106
208
692
1,363
2,707
5,395
N/A

batch_insert_into_indexed_tree_20_depth_hash_ms
N/A
N/A
0.544
0.538
0.515
0.513
0.512
0.513
N/A

batch_insert_into_indexed_tree_40_depth_ms
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
67.8

batch_insert_into_indexed_tree_40_depth_hash_count
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
108

batch_insert_into_indexed_tree_40_depth_hash_ms
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
0.594

Miscellaneous
Transaction sizes based on how many contract classes are registered in the tx.

Metric
0 registered classes
1 registered classes

tx_size_in_bytes
84,741
673,219

Transaction size based on fee payment method
| Metric |  |
| - |  |
Transaction processing duration by data writes.

Metric
0 new note hashes
1 new note hashes
2 new note hashes

tx_pxe_processing_time_ms
29,815
4,257
100,720

Metric
0 public data writes
1 public data writes
2 public data writes
4 public data writes
8 public data writes

tx_sequencer_processing_time_ms
1,370
2,222
1,975
3,115
1,977


Multiple without-group support for bundler list

What was the end-user problem that led to this PR?
The problem was that I needed to list all gems and dependencies that weren't in group :development or :test (or both of the together) but bundler list --without-group was only accepting one group at a time.
What was your diagnosis of the problem?
My diagnosis was I should just make it work for multiple groups
What is your fix for the problem, implemented in this PR?
My fix is I split groups by , in args.
Why did you choose this fix out of the possible options?
I chose this fix because it's simple and look like you can find in other cli.
I have two questions: Should I take care of the case where you have multiple --without-group specified ? Should I support --without-groups ?

@denispasin hi, are you still interested in this PR? There are pending review questions. If we don’t get an update we may have to close it. Thanks.


Device is not registered in Tuya cloud

What does this error mean? Because I can see the device online

same issue here

I was having this issue, but just solved it. As soon as I enabled a free trial of IOT Core, it registered instantly. If you get this error message and this far you at least know the tuya creds etc. are working.
To enable IOT core I did this.
Cloud > Development.
Open Project.
Authorization > Add Authorization
Find IOT core and click free trial.
Hope this helps someone

Mine was already enabled, even I tried to delete old one and add authorisation again (only one auth. allowed) it didnt work for me. Thanks anyway.

I was having this issue, but just solved it. As soon as I enabled a free trial of IOT Core, it registered instantly (to me it wasn't clear in any doco that this was required but I guess it is). If you get this error message and this far you at least know the tuya creds etc. are working.
To enable IOT core I did this.
Cloud > Development. Open Project. Authorization > Add Authorization Find IOT core and click free trial.
Hope this helps someone

Already did, nothing change. :(

Same problem here :-(

Same problem here :-(

Same, trying to use a SGS01 soil sensor. Have tried multiple different forks, all the same issue.

Looks like they changed trial period and you have to update it. Go to Cloud -> Cloud Services -> IoT Core -> Subscribe to resource pack. After some time everything should work.

Having just managed to get this going after receiving "Device is not registered in Tuya Cloud" It's not always as simple as just enabling the IoT core (Mine is already active and running until July).
I've ended up with a main build of markusg and tweaks of Kappuchino for my riecov42 additions.
But after adding these it wasn't still working, the device was recognising as "Configure" but would never see it in Tuya cloud despite showing in Cloud Explorer for "Get Device Details" on Smart Home Device Management.

I added some extra logger lines into cloud.py around line #166:
                    _cache[cache_key] = TuyaCloudCacheItem(api, data, {})
#        _LOGGER.debug("%s: Response", response)
        return response

    def _check_login(self) -> bool:
        cache_key = self._get_cache_key(self._data)
        return _cache.get(cache_key) != None

    async def login(self, add_to_cache: bool = False) -> dict[Any, Any]:
        return await self._login(self._data, add_to_cache)

    async def _fill_cache_item(self, item: TuyaCloudCacheItem) -> None:
        devices_response = await self._hass.async_add_executor_job(
            item.api.get,
            TUYA_API_DEVICES_URL % (item.api.token_info.uid),
        )

        if devices_response.get(TUYA_RESPONSE_SUCCESS):
            devices = devices_response.get(TUYA_RESPONSE_RESULT)
#            _LOGGER.debug("Successful devices for %s", devices)
            if isinstance(devices, Iterable):
                for device in devices:
#                    _LOGGER.debug("Device Loop %s", device)
                    fi_response = await self._hass.async_add_executor_job(
                        item.api.get,
                        TUYA_API_FACTORY_INFO_URL % (device.get("id")),
                    )
                    fi_response_result = fi_response.get(TUYA_RESPONSE_RESULT)
#                    _LOGGER.debug("%s :",fi_response_result)
                    if fi_response_result and len(fi_response_result) > 0:

(remove the # to enable them) which allowed me to see that I was logging in (default debug log) but not see anything in the array from the API when it looks to find the device in question.
I historically had 2 accounts registered on the Tuya App Link (one had 0 items and was before I swapped stuff from the Tuya app to SmarLife app) so i unlinked this (Be aware this page can take multiple attempts to get the data showing)

Deleting the extra, made it that when I re-tried, i got invalid credentials error this time which hadn't happened before.
Reset password for smartlife account, tried again and had success.
Other details:
HA Tuya is logged in via SmartLife QR code
SmartLife app is in usage on android phone
IoT Core is already active until Jul
Hopefully that will help someone else narrow down their not in cloud issues.

@AaronIsFab I followed your instructions to add debug logging, which was very helpful. Yet I wasn't able to add my device. I'm using the markusg1234 fork/branch.
Adding the BLE device, after entering my credentials, the dialog shows: "Device is not registered in Tuya cloud"
But that's not correct, the Tuya Development Platform under my Linked App Account clearly shows 1 Linked Device and it's the same I'm trying to add.
Trying to troubleshoot the situation with debug logging:
In principe the device is visible to the integration:
[custom_components.tuya_ble.cloud] Successful devices for [{'active_time':<PHONE_NUMBER>, 'biz_type': 18, 'category': 'ggq', 'create_time':<PHONE_NUMBER>, 'icon': 'smart/icon/ay1559701439060fw6BY/0bc4bd995df9cc19a005c78b8f5b1eca.png', 'id': 'XXX', 'ip': '', 'lat': 'XXX', 'local_key': 'XXX', 'lon': 'XXX', 'model': 'PBB A1', 'name': 'Smart Watering Timer', 'online': False, 'owner_id': 'XXX', 'product_id': '6pahkcau', 'product_name': 'Smart Watering Timer', 'status': [{'code': 'switch', 'value': False}, {'code': 'countdown', 'value': 1}, {'code': 'countdown_left', 'value': 0}, {'code': 'battery_percentage', 'value': 90}], 'sub': False, 'time_zone': '+02:00', 'uid': 'XXX', 'update_time': XXX, 'uuid': 'XXX'}]
But in practice I'm getting the error mentioned above, as if it weren't registered.
fi_response_result would return

{'code': 60009001, 'msg': 'API permission package error. For the solution, see https://developer.tuya.com/en/docs/iot/authentication-method?id=Ka49gbaxjygox.', 'success': False, 't':<PHONE_NUMBER>964, 'tid': '98b7869c55f911ef8d1002b5f94b0719'}

I looked at the const.py as well as the Tuya developer docs, I see that the the constant for the factory info retrieval looks like TUYA_API_FACTORY_INFO_URL: Final = "/v1.0/iot-03/devices/factory-infos?device_ids=%s", API Docs say GET: /v1.0/devices/factory-infos, there's no iot-03.
It would seem that the URL changed
I've trying changing the URL to  TUYA_API_FACTORY_INFO_URL: Final = "/v1.0/devices/factory-infos?device_ids=%s" removing the iot-03 part
Which seems to yield results, at least I'm getting an array from fi_response_result:
[{'id': 'XXX', 'mac': 'XX:XX:XX:XX:XX:XX', 'sn': 'XXXXXXXX', 'uuid': 'XXXXXXXX'}]
But the initial error persisted, still "Device is not registered in Tuya cloud" in the form.
I dug further, somehow the mac address was being garbled up, the final credentials array had the address stored as XX::X:X::XX::X:X: instead of 'XX:XX:XX:XX:XX:XX', I ended up discovering that TUYA_FACTORY_INFO_MAC was imported twice (line 58 of cloud.py) and also I replaced the entire join routine for the mac with:
                            # mac = ":".join(
                            #     factory_info[TUYA_FACTORY_INFO_MAC][i : i + 2]
                            #     for i in range(0, 12, 2)
                            # ).upper()
                            mac = factory_info[TUYA_FACTORY_INFO_MAC].upper()

And then I was able to add the device successfully.
Seems to me that the API changed somehow between April and now.
To sum up:

const.py, TUYA_API_FACTORY_INFO_URL needs to change,
cloud.py remove redundant declaration of TUYA_FACTORY_INFO_MAC
cloud.py replace the join of mac (just before item.credentials[mac]) with mac = factory_info[TUYA_FACTORY_INFO_MAC].upper()

Hope this helps somebody.

@thkrmr This totally worked, thank you! Hope it will be updated in the main build

@AaronIsFab I followed your instructions to add debug logging, which was very helpful. Yet I wasn't able to add my device. I'm using the markusg1234 fork/branch.
Adding the BLE device, after entering my credentials, the dialog shows: "Device is not registered in Tuya cloud"
But that's not correct, the Tuya Development Platform under my Linked App Account clearly shows 1 Linked Device and it's the same I'm trying to add.
Trying to troubleshoot the situation with debug logging: In principe the device is visible to the integration: [custom_components.tuya_ble.cloud] Successful devices for [{'active_time':<PHONE_NUMBER>, 'biz_type': 18, 'category': 'ggq', 'create_time':<PHONE_NUMBER>, 'icon': 'smart/icon/ay1559701439060fw6BY/0bc4bd995df9cc19a005c78b8f5b1eca.png', 'id': 'XXX', 'ip': '', 'lat': 'XXX', 'local_key': 'XXX', 'lon': 'XXX', 'model': 'PBB A1', 'name': 'Smart Watering Timer', 'online': False, 'owner_id': 'XXX', 'product_id': '6pahkcau', 'product_name': 'Smart Watering Timer', 'status': [{'code': 'switch', 'value': False}, {'code': 'countdown', 'value': 1}, {'code': 'countdown_left', 'value': 0}, {'code': 'battery_percentage', 'value': 90}], 'sub': False, 'time_zone': '+02:00', 'uid': 'XXX', 'update_time': XXX, 'uuid': 'XXX'}]
But in practice I'm getting the error mentioned above, as if it weren't registered.
fi_response_result would return

{'code': 60009001, 'msg': 'API permission package error. For the solution, see https://developer.tuya.com/en/docs/iot/authentication-method?id=Ka49gbaxjygox.', 'success': False, 't':<PHONE_NUMBER>964, 'tid': '98b7869c55f911ef8d1002b5f94b0719'}

I looked at the const.py as well as the Tuya developer docs, I see that the the constant for the factory info retrieval looks like TUYA_API_FACTORY_INFO_URL: Final = "/v1.0/iot-03/devices/factory-infos?device_ids=%s", API Docs say GET: /v1.0/devices/factory-infos, there's no iot-03.
It would seem that the URL changed
I've trying changing the URL to TUYA_API_FACTORY_INFO_URL: Final = "/v1.0/devices/factory-infos?device_ids=%s" removing the iot-03 part
Which seems to yield results, at least I'm getting an array from fi_response_result: [{'id': 'XXX', 'mac': 'XX:XX:XX:XX:XX:XX', 'sn': 'XXXXXXXX', 'uuid': 'XXXXXXXX'}]
But the initial error persisted, still "Device is not registered in Tuya cloud" in the form.
I dug further, somehow the mac address was being garbled up, the final credentials array had the address stored as XX::X:X::XX::X:X: instead of 'XX:XX:XX:XX:XX:XX', I ended up discovering that TUYA_FACTORY_INFO_MAC was imported twice (line 58 of cloud.py) and also I replaced the entire join routine for the mac with:
                            # mac = ":".join(
                            #     factory_info[TUYA_FACTORY_INFO_MAC][i : i + 2]
                            #     for i in range(0, 12, 2)
                            # ).upper()
                            mac = factory_info[TUYA_FACTORY_INFO_MAC].upper()

And then I was able to add the device successfully.
Seems to me that the API changed somehow between April and now.
To sum up:

const.py, TUYA_API_FACTORY_INFO_URL needs to change,
cloud.py remove redundant declaration of TUYA_FACTORY_INFO_MAC
cloud.py replace the join of mac (just before item.credentials[mac]) with mac = factory_info[TUYA_FACTORY_INFO_MAC].upper()
Click twice on Submit

Hope this helps somebody.

Hi, I still face the issue of getting the error

in the second step of configuration.
I assume I followed all steps described in https://github.com/PlusPlus-ua/ha_tuya_ble/issues/119#issuecomment-2039869993 and https://github.com/PlusPlus-ua/ha_tuya_ble/issues/119#issuecomment-2277086223 correctly, as the first step is accepted and the device is showing up? In addition I added this line to the manifest.json file
 "loggers": ["custom_components.tuya_ble"]
However, I don't know how or where to enable the debugging (as above is my only device, and I cant access the UI button to make use of above line) nor access the log files where these would be now captured. I am a bit stuck.
Summary of what I have/did:

[X] Tuya dev cloud setup and verified that device is linked/listed
[X] official Tuya integration setup in HA (logged in via SmartLife App, QR code)
[X] Adjusted const.py
[X] Altered cloud.py
[X] Added lines to allow for debugging (logger) to both cloud.py and manifest.json
[X] Restarted HA

Hope someone is able to provide some further guidance. Thank you!

Same challenges, however started working for me when I delete everything on
tiya cloud and started from scratch with a new email address (blessed be
the dot trick on gmail accounts)
On Fri, Sep 13, 2024 at 4:08 PM webmediart-github @.***>
wrote:

Hi, I still face the issue of getting the error
image.png (view on web)
https://github.com/user-attachments/assets/152f631b-34ac-4156-a4ad-227a80a34ff2
in the second step of configuration.
I assume I followed all steps described in #119 (comment)
https://github.com/PlusPlus-ua/ha_tuya_ble/issues/119#issuecomment-2039869993
and #119 (comment)
https://github.com/PlusPlus-ua/ha_tuya_ble/issues/119#issuecomment-2277086223
correctly, as the first step is accepted and the device is showing up? In
addition I added this line to the manifest.json file
"loggers": ["custom_components.tuya_ble"]
However, I don't know how or where to enable the debugging (as above is my
only device, and I cant access the UI button to make use of above line) nor
access the log files where these would be now captured. I am a bit stuck.
Summary of what I have/did:

Tuya dev cloud setup and verified that device is linked/listed
official Tuya integration setup in HA (logged in via SmartLife App,
QR code)
Adjusted const.py
Altered cloud.py
Added lines to allow for debugging (logger) to both cloud.py and
manifest.json
Restarted HA

Hope someone is able to provide some further guidance. Thank you!
—
Reply to this email directly, view it on GitHub
https://github.com/PlusPlus-ua/ha_tuya_ble/issues/119#issuecomment-2350210460,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BCZLFJTP76QOVDEA6YLMYIDZWNH3XAVCNFSM6AAAAABEOIHZHSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNJQGIYTANBWGA
.
You are receiving this because you commented.Message ID:
@.***>

I think I might lack a bit of general "Tuya" knowledge, but are you able to describe the detailed steps how you setup the device itself? I went like this:

Open SmartLife App and add device for tuya cloud connection
Reset Device to disconnect from phone via reset button

Although it shows now in HA, I suspect that it is not connected to HA via bluetooth as its entities are unavailable?

Same challenges, however started working for me when I delete everything on tiya cloud and started from scratch with a new email address (blessed be the dot trick on gmail accounts)

If it shows in HA and you have no entities (or in my case just the signal
entity), then it is likely that your tuta product isn’t supported yet.
Every tuta product seems to have a category ID and a Product ID, you’ll
find them in one of the .py files (I think the devices.py). If your isn’t
there then you are out of luck (like me).
The developers of this integration seem to have disappeared recently, there
are a few forks but they don’t seem active either.
Theoretically it isn’t too difficult to add if you have category ID,
Product ID but I got into a few issues and I have an open ask for someone
better than me to support.
Sorry I can’t help much more
On Fri, Sep 13, 2024 at 4:55 PM webmediart-github @.***>
wrote:

I think I might lack a bit of general "Tuya" knowledge, but are you able
to describe the detailed steps how you setup the device itself? I went like
this:

Open SmartLife App and add device for tuya cloud connection
Reset Device to disconnect from phone via reset button

Although it shows now in HA, I suspect that it is not connected to HA via
bluetooth as its entities are unavailable?
Same challenges, however started working for me when I delete everything
on tiya cloud and started from scratch with a new email address (blessed be
the dot trick on gmail accounts)
—
Reply to this email directly, view it on GitHub
https://github.com/PlusPlus-ua/ha_tuya_ble/issues/119#issuecomment-2350394609,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BCZLFJTV5FFAWZWXL2I75JDZWNNNJAVCNFSM6AAAAABEOIHZHSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNJQGM4TINRQHE
.
You are receiving this because you commented.Message ID:
@.***>

After inserting the following code in devices.py i can see my sensors. Seems my SGS01 sensors have a different category and product.
Inserted the code at around line 287.
    "zwjcy": TuyaBLECategoryInfo(
        products={
            "gvygg3m8": TuyaBLEProductInfo(  # device product_id
                name="Soil moisture sensor - test",
            ),
        },
    ),

I was searching for a solution for this problem and tried different options from this issue.
I added the category and product IDs to the devices.py file so I could discover the devices. Then the problem with tuya cloud occured.
I refreshed my IOT Core Subscription for free for another 6 months but still the same problem.
Now I got it working! The problem was the App that I used for connecting the sensors. I used Smart Life becuase I used it for all my tuya devices (which also connected to HA).
Turns out you need to connect them through the tuya app itself. Now it works flawlessly.

Hi,
Thanks for all the input provided here, much appreciated!
But even after following all steps mentioned here and elsewhere, besides starting all over from scratch on the Tuya-side,
I still can't control my BLE Fingerbot via HA anymore.
Meanwhile the device is at least showing up, also containing all necessary entities,
but they are all disabled and the device is "unavailable".
Also in the Tuya Cloud it's always shown as offline and is not actually controllable.
(And when I try to delete it in HA nothing happens...this integration is so broken... :( )
But this is the same for most of my devices (besides one all are offline in the cloud) and they are all working fine in HA.
(E.g. a SGS Plant sensor, which despite of being offline in the Tuya Cloud just popped up in HA,
even if I'm actually not caring about that one at all D)
Via the App the Fingerbot is working fine and can be controlled
(I had it paired to both apps already one after the other, both are working fine).
I did all changes mentioned here, also the necessary "riecov42"/"kg" additions as usual, but it's still not working.
I can provide screenshots or logs if necessary.
Any hints are welcome.
Thanks

@Moe555 I had issues with devices showing as unavailable, when two things were out of whack:
a) bad range, device too far away from the BT proxy
b) BT proxies didn't add properly to Home Assistant, meaning the proxies were visible in the ESPHome interface (where you change the build config), but the proxies weren't properly added to the HA device list as entities under the Settings - Devices and Services - ESPHome, as an ESPHome device with bt proxy functionality. I ended up deleting all entries and flashing the ESPs anew and adding the 'new' proxies to HA. Within the esphome yaml configs, I turned on verbose logging.
So I fixed the range issue by placing the proxy close and subsequently fixed the ESPHome BT proxy issues.
Now when I check the ESPHome log (wirelessly) of a particular proxy, I see in the logs that BLE packets are being proxied. This correlates with my Tuya BLE devices working quite stable. When this all wasn't working well, I had no log entries of proxied BLE packets. I also turned off BT on my machine completely, all BT communication for Tuya BLE is done via the ESPHome BT proxies. I initially used Wemos D1 mini boards and the switched to M5Stack ATOMS3 Lite boards. The BT proxies are also proxying SwitchBot Curtain motors in parallel to the Tuya BLE bits without a hitch.
Your mileage may vary, but I had pretty good success with this setup, surviving updates to HA, updates to ESPHome and even the switch from Wemos to M5Stack.
Good luck.

@thkrmr Thanks for the detailed explanation.
I can't imagine that it's a range issue, since it's sitting next to the raspi HA host.
Also placing it next to a BT proxy doesn't change anything unfortunately.
The proxy is properly configured imo. Other sensor values, etc. get relayed w/o issues.
Besides that, other Tuya BLE devices (like a plant sensor) are shown offline in the Tuya Cloud as well,
but are working perfectly fine in HA.
It's really confusing...
I guess I messed something up during all the manual modifications which are necessary,
since this integration is not updated or maybe because something was changed on the Tuya side/is not configured properly.
But I double-checked everything and still see no mistake.
As mentioned here it would be really great if there would be at least some working "baseline" again to start with, which is just not the case at the moment, at least for those Fingerbots.
BR


Prerequisites

[X] I have searched all issues/PRs to ensure it has not already been reported or fixed.

Criteria

[X] Reasonably well-known and widely used (e.g. if it's a GitHub project, it should have at least 100 stars and/or 50 forks)
[X] English interface (or at least English documentation)
[X] Latest stable version
[X] Full version (i.e. not a trial version)
[X] Fairly standard install (e.g. uses a version-specific download URL, no elaborate pre/post install scripts)

Name
web-ext
Description
web-ext is a command-line tool designed to speed up and simplify development of firefox extensions.
Homepage
https://github.com/mozilla/web-ext
Download Link(s)
https://registry.npmjs.org/web-ext/-/web-ext-8.2.0.tgz
Some Indication of Popularity/Repute
Has 2.7k stars on github
Notes
It's also available in Homebrew, here is code for the formula:
https://github.com/Homebrew/homebrew-core/blob/c3c5be2ae7ceef7b5b690a1dae9ab02fc1c9d0c2/Formula/w/web-ext.rb

IMO you shouldn't install this with scoop, this is a language specific tool, instead you should scoop install main/nodejs, then run install -g web-ext with your preferred corepack package manager.

Imo you shouldn't install this with scoop, this is a language specific tool, instead you should scoop install main/nodejs, then run install -g web-ext with your preferred corepack package manager.

I can see where you're coming from but I made this issue since web-ext is available in brew which is a system package manager for MacOS similar to scoop
I'm not too sure on how scoop handles npm packages though, if scoop doesn't then it would make sense to not add this =)

To my knowledge scoop doesn't handle npm packages, it in theory could, with symlinks to it's own nodejs dir, and custom shims, but it's not an abstraction that currently exists, nor does it really make sense to have, as it's just more complex than using a corepack package manager, which has these things built in (e.g. pnpm, yarn, or npm).

To my knowledge scoop doesn't handle npm packages, it in theory could, with symlinks to it's own nodejs dir, and custom shims, but it's not an abstraction that currently exists (so there'd be a heavy reliance on script blocks), nor does it really make sense to have, as it's just more complex than using a corepack package manager, which has these things built in (e.g. pnpm, yarn, or npm).

This makes sense, thanks for clarifying!


Fix deadlock in envoy restart logic.

Please provide a description for what this PR is for.
And to help us figure out who should review this PR, please
put an X in all the areas that this PR affects.
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[x] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

@nmittler: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

gencheck_istio
d92efac396030336032133d9bf1a112b4c9e18d7
link
/test gencheck_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@nmittler: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

gencheck_istio
d92efac396030336032133d9bf1a112b4c9e18d7
link
/test gencheck_istio

integ-new-install-k8s-tests_istio
d92efac396030336032133d9bf1a112b4c9e18d7
link
/test integ-new-install-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@nmittler: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-new-install-k8s-tests_istio
d92efac396030336032133d9bf1a112b4c9e18d7
link
/test integ-new-install-k8s-tests_istio

integ-istioio-k8s-tests_istio
5f6b00f499086acc7b831b420b70107229297793
link
/test integ-istioio-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@nmittler: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-new-install-k8s-tests_istio
d92efac396030336032133d9bf1a112b4c9e18d7
link
/test integ-new-install-k8s-tests_istio

integ-istioio-k8s-tests_istio
5f6b00f499086acc7b831b420b70107229297793
link
/test integ-istioio-k8s-tests_istio

e2e-simpleTests-cni_istio
5f6b00f499086acc7b831b420b70107229297793
link
/test e2e-simpleTests-cni_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@nmittler: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-new-install-k8s-tests_istio
d92efac396030336032133d9bf1a112b4c9e18d7
link
/test integ-new-install-k8s-tests_istio

integ-istioio-k8s-tests_istio
5f6b00f499086acc7b831b420b70107229297793
link
/test integ-istioio-k8s-tests_istio

e2e-simpleTests-cni_istio
5f6b00f499086acc7b831b420b70107229297793
link
/test e2e-simpleTests-cni_istio

integ-pilot-k8s-tests_istio
5f6b00f499086acc7b831b420b70107229297793
link
/test integ-pilot-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@nmittler: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-new-install-k8s-tests_istio
d92efac396030336032133d9bf1a112b4c9e18d7
link
/test integ-new-install-k8s-tests_istio

integ-istioio-k8s-tests_istio
5f6b00f499086acc7b831b420b70107229297793
link
/test integ-istioio-k8s-tests_istio

e2e-simpleTests-cni_istio
5f6b00f499086acc7b831b420b70107229297793
link
/test e2e-simpleTests-cni_istio

integ-pilot-k8s-tests_istio
5f6b00f499086acc7b831b420b70107229297793
link
/test integ-pilot-k8s-tests_istio

lint_istio
5f6b00f499086acc7b831b420b70107229297793
link
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@nmittler: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-istioio-k8s-tests_istio
5f6b00f499086acc7b831b420b70107229297793
link
/test integ-istioio-k8s-tests_istio

e2e-simpleTests-cni_istio
5f6b00f499086acc7b831b420b70107229297793
link
/test e2e-simpleTests-cni_istio

integ-pilot-k8s-tests_istio
5f6b00f499086acc7b831b420b70107229297793
link
/test integ-pilot-k8s-tests_istio

lint_istio
5f6b00f499086acc7b831b420b70107229297793
link
/test lint_istio

integ-new-install-k8s-tests_istio
5f6b00f499086acc7b831b420b70107229297793
link
/test integ-new-install-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@nmittler: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

e2e-simpleTests-cni_istio
5f6b00f499086acc7b831b420b70107229297793
link
/test e2e-simpleTests-cni_istio

integ-pilot-k8s-tests_istio
5f6b00f499086acc7b831b420b70107229297793
link
/test integ-pilot-k8s-tests_istio

lint_istio
5f6b00f499086acc7b831b420b70107229297793
link
/test lint_istio

integ-new-install-k8s-tests_istio
5f6b00f499086acc7b831b420b70107229297793
link
/test integ-new-install-k8s-tests_istio

integ-istioio-k8s-tests_istio
0f60af7bcde42cf51439aaae4360c67988aaa515
link
/test integ-istioio-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@nmittler: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

e2e-simpleTests-cni_istio
5f6b00f499086acc7b831b420b70107229297793
link
/test e2e-simpleTests-cni_istio

integ-pilot-k8s-tests_istio
5f6b00f499086acc7b831b420b70107229297793
link
/test integ-pilot-k8s-tests_istio

integ-new-install-k8s-tests_istio
5f6b00f499086acc7b831b420b70107229297793
link
/test integ-new-install-k8s-tests_istio

integ-istioio-k8s-tests_istio
0f60af7bcde42cf51439aaae4360c67988aaa515
link
/test integ-istioio-k8s-tests_istio

lint_istio
0f60af7bcde42cf51439aaae4360c67988aaa515
link
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@nmittler: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
5f6b00f499086acc7b831b420b70107229297793
link
/test integ-pilot-k8s-tests_istio

integ-new-install-k8s-tests_istio
5f6b00f499086acc7b831b420b70107229297793
link
/test integ-new-install-k8s-tests_istio

lint_istio
0f60af7bcde42cf51439aaae4360c67988aaa515
link
/test lint_istio

integ-istioio-k8s-tests_istio
561187cf05341086e71d8a14d80a3180997ddde0
link
/test integ-istioio-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@nmittler: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-istioio-k8s-tests_istio
561187cf05341086e71d8a14d80a3180997ddde0
link
/test integ-istioio-k8s-tests_istio

integ-new-install-k8s-tests_istio
561187cf05341086e71d8a14d80a3180997ddde0
link
/test integ-new-install-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@nmittler: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-istioio-k8s-tests_istio
561187cf05341086e71d8a14d80a3180997ddde0
link
/test integ-istioio-k8s-tests_istio

integ-new-install-k8s-tests_istio
561187cf05341086e71d8a14d80a3180997ddde0
link
/test integ-new-install-k8s-tests_istio

integ-mixer-k8s-tests_istio
561187cf05341086e71d8a14d80a3180997ddde0
link
/test integ-mixer-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.