Cross Compiling suggestion

The issue:
I've been working on a project of mine for Home Assistant when I encountered a problem with cross compiling ZeroNS caused by openssl not found for cpu architecture other than the host
The fix:
Maybe this is my first time building a rust project, the way I fixed it is by adding to the dependencies
openssl = { version = "0.10.38", features = ["vendored"] }
build successed and tested on Ubuntu amd64 for Alpine amd64
Is it something you can implement it in this project?

Hmm. Not sure how well this'll work with the different packages, but I'm willing to try it out!

Okay thank you

I think you misunderstood me. Let's try it, see how it works. I'll report back here once I have. Let's leave this open until I do.

Please note this didn't work as well as I'd hoped: #177 resolves some issues with this. You'll need to use this method to install zeronsd on your hosts. Hope it helps!

Thats a great news, I'll test it in my project and report back, thank you again.

Cross compile re-broke after version 0.5 with the same error as before the fix you implemented while running
cargo build --features vendored-openssl

With the following error:
failed to run custom build command for 'openssl-sys v0.9.73' Caused by:   process didn't exit successfully:'/target/release/build/openssl-sys-79a29d2c768cb8be/build-script-main' (exit status: 101)   --- stdout   cargo:rustc-cfg=const_fn   cargo:rerun-if-env-changed=X86_64_UNKNOWN_LINUX_GNU_OPENSSL_LIB_DIR   X86_64_UNKNOWN_LINUX_GNU_OPENSSL_LIB_DIR unset   cargo:rerun-if-env-changed=OPENSSL_LIB_DIR   OPENSSL_LIB_DIR unset   cargo:rerun-if-env-changed=X86_64_UNKNOWN_LINUX_GNU_OPENSSL_INCLUDE_DIR   X86_64_UNKNOWN_LINUX_GNU_OPENSSL_INCLUDE_DIR unset   cargo:rerun-if-env-changed=OPENSSL_INCLUDE_DIR   OPENSSL_INCLUDE_DIR unset   cargo:rerun-if-env-changed=X86_64_UNKNOWN_LINUX_GNU_OPENSSL_DIR   X86_64_UNKNOWN_LINUX_GNU_OPENSSL_DIR unset   cargo:rerun-if-env-changed=OPENSSL_DIR   OPENSSL_DIR unset   cargo:rerun-if-env-changed=OPENSSL_NO_PKG_CONFIG   cargo:rerun-if-env-changed=PKG_CONFIG_x86_64-unknown-linux-gnu   cargo:rerun-if-env-changed=PKG_CONFIG_x86_64_unknown_linux_gnu   cargo:rerun-if-env-changed=HOST_PKG_CONFIG   cargo:rerun-if-env-changed=PKG_CONFIG   cargo:rerun-if-env-changed=OPENSSL_STATIC   cargo:rerun-if-env-changed=OPENSSL_DYNAMIC   cargo:rerun-if-env-changed=PKG_CONFIG_ALL_STATIC   cargo:rerun-if-env-changed=PKG_CONFIG_ALL_DYNAMIC   cargo:rerun-if-env-changed=PKG_CONFIG_PATH_x86_64-unknown-linux-gnu   cargo:rerun-if-env-changed=PKG_CONFIG_PATH_x86_64_unknown_linux_gnu   cargo:rerun-if-env-changed=HOST_PKG_CONFIG_PATH   cargo:rerun-if-env-changed=PKG_CONFIG_PATH   cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_x86_64-unknown-linux-gnu   cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_x86_64_unknown_linux_gnu   cargo:rerun-if-env-changed=HOST_PKG_CONFIG_LIBDIR   cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR   cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_x86_64-unknown-linux-gnu   cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_x86_64_unknown_linux_gnu   cargo:rerun-if-env-changed=HOST_PKG_CONFIG_SYSROOT_DIR   cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR   run pkg_config fail: "\"pkg-config\" \"--libs\" \"--cflags\" \"openssl\" did not exit successfully: exit status: 1\nerror: could not find system library 'openssl' required by the 'openssl-sys' crate\n\n--- stderr\nPackage openssl was not found in the pkg-config search path.\nPerhaps you should add the directory containing 'openssl.pc'\nto the PKG_CONFIG_PATH environment variable\nNo package 'openssl' found\n"'


Not able to get Arraysize more than 1024 on a query

Hi,
Is there a way where we can increase the query array size,right now its limiting to 1024.

#11 https://github.com/ufukomer/node-impala/issues/11#issuecomment-274798646


correct flaky test comment

Please provide a description of this PR:
To help us figure out who should review this PR, please put an X in all the areas that this PR affects.

[ ] Ambient
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[x] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

Please check any characteristics that apply to this pull request.

[x] Does not have any user-facing changes. This may include CLI changes, API changes, behavior changes, performance improvements, etc.

@zirain: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
ef31005083021a9bf5d14e36d2bf2256f5ae3c78
link
true
/test release-notes

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.

/test release-notes


Improve AutoLayout support

When I added Chart.view to my view and setup constraints properly, Chart.view subviews still doesn't have constraints and that's why their layout is incorrect when their superview bounds are changed.

Did you already take a look here? https://github.com/i-schuetz/SwiftCharts/issues/105

Not yet, but it seems to me like a hack. You re-initialize the graph each time the device is rotated.

Yes, there's no out of the box support for autolayout yet. The solutions provided are not very elegant but work well and you can put the reinitialisation in a helper class to make it a bit better. There are some architectural changes needed, currently the chart is immutable, and not a view, which is convenient for some things but problematic for others, like autolayout or adding points on the fly. I don't have time for this now but ideas or pull request are welcome.

For now the autolayout support will stay like it is.


Colourisation fails occasionally

Hi,
Version:  TS 1.8/VS 2015
The problem started off as a sticky red squiggly that was underlining an error that was already corrected and refusing to go away. I tried closing the file to get rid of the red squiggly. Re-opening the file resulted in the red squiggly disappearing but caused the IDE to display the faulty colouring as depicted below. Closing and re-opening the file did not initially correct the problem, but appears to have corrected itself while I was writing this.

I have not seen this occur in previous versions.

is there a way we can reproduce this locally?

Not at the moment. There's also nothing in the event log. I will see if this occurs again.

this is not really actionable at the moment. please reopen if you run into it again, a project or consistent repro would help a lot.


Calendar Colors

Not an issue, probably, but more of a question. Is it possible to pull the calendar colors that have been configured in O365 online? Currently, each calendar pulled is assigned a random color by HA. I'd like to have the color for each calendar pulled from the configuration that I've already curated in O365.

I can add the color attribute to the calendar entity (there are two: color, which is one from a list; and hexcolor). I have no control over how it is displayed though. You'd probably need to put in a request to HA frontend team to read an attribute if available and use it in the display.
I'm afraid I haven't done any frontend stuff, so not really sure how to get that done.

Very useful.. If you add them it's easy enough to pull either to use.. Personally I'd uss hexcolor - most of the mushroom cards can use that unmodified on anything that takes a color variable

I'll look at it in the next few days

I've just installed the update. I'd be happy to put in a request to the HA front-end team. Where can I go to look at the data pulled by the o365 integration to give them an appropriate example/screenshot?

I've started a Feature Request discussion in the Front-End GH. I don't expect HA would just use the data as it's imported by your code, but I've proposed the building of a "bridge" that would allow for custom integrations like this one to plug in the desired calendar color.
https://github.com/home-assistant/frontend/discussions/18465


Cannot specify light

guppi lights off 6 now gives the error
Cannot parse argument '6' for option '--light' as expected type 'System.UInt32'.

Happening since I upgraded System.Console

See https://github.com/dotnet/command-line-api/issues/1683


Add commata to MySQL and PostgreSQL table creation

I added "," to the CREATE statements when missing. It may be left, but helps the tutorial reader focus on the statement but not why a comma is missing in a line.

Thank you for taking the time! 💚


Bcak 44

episode 44 - Allen Holub - added page plus updated the dictionary for Allen related wordage

Interesting....make spell is successful locally


container user should not be root and should not have sudo installed

Linux security best practices say one should not run as root but instead use sudo if needed. This rule applies to applications in containers as well. Ideally, a container that is used just to run chia farmer/harvester/wallet should not even have sudo installed as all prerequisites to run chia should already be in the container image

In my opinion, if the user running  in the container were to change from root, there would need to still be a way to continue running as root. In this case, security comes at the expense of usability, depending on what you want to do. Somebody might hop in the container, want to install tree, etc.
What's your thoughts on that? Did you want to take a stab at this?

I think maybe we have different ideas of what this container is supposed to accomplish

I think we're actually on the same page. At least a similar one.

What I've seen from a lot of people is that this is the container that they run their chia client with (on a NAS or just to make life easy on their local machine).

The thing about maintaining software, is that there's a lot of different vocal minorities that don't fit into the mold of what you'd argue the majority does. And we have to think about those people too. For example, some people may (and more than likely do) maintain their own images that start with FROM ghcr.io/chia-network/chia:latest and then install a bunch of extra stuff on top and then they actually utilize that resulting image for whatever reason. This would be a breaking change for them, and they'll be (understandably) upset when they realize their existing pipeline was broken upstream.
For what it's worth... I've actually brought up this exact Issue internally on a couple of occasions. I reckon if you were to search through other Issues or the chia-docker channel on the public keybase community, you'll see me bringing up this exact same concern. I think that solving for this concern is likely more complicated than either of us initially thought but I'm happy to hear your ideas for how to solve it in a sane way. I think separate tags may be the best way, and I think I'm leaning towards keeping :latest the way it is for now, for reasons I've already said above.
Personally, looking into commonly mentioned exploits for escaping containers, it usually requires privileged containers (not really relevant here) or access to the host to bind mount host directories owned by root into the container, in which case you already have a bad actor on your host and that whole system is hosed anyway. Happy to be proven wrong there, though.
Either way, I'd be happy to review a PR that accomplishes this!

Also, if there were a non-root variant of this image, it would be cool if it followed the common linuxserver.io pattern of allowing you to specify a UID and GID via environment variables.

Also, if there were a non-root variant of this image, it would be cool if it followed the common linuxserver.io pattern of allowing you to specify a UID and GID via environment variables.

linuxserver.io uses the s6-overlay project and relies on its setuid magic or something (it's unclear from a moderate amount of digging what they actually do to accomplish running not as root). Unless you want to take a dependency on s6-overlay and start maintaining different dockerfiles for different architectures (s6-overlay has different arch packages) or explicitly support on x86_64 or other architectures that may not be the best course of action.
If a container is running as a stateless container (i.e. harvester), then not being able to set a particular user/group ID isn't such a big deal. If the directory that the plots are in has read permissions then it will be fine. The only tricky part would be if the user did a mount for the database files as that would require write permissions. Again, not super complicated to solve if users can set write permissions on the host directory, though admittedly not the most elegant solution

It seems you'd have to work around this issue
https://github.com/Chia-Network/chia-blockchain/issues/11257

I've been playing around a little bit trying to get an s6-overlay image working to see what it would be like, but there's an issue with the way s6-overlay drops permissions and how python's os.path.expanduser() functions. s6-overlay can properly drop permissions for the program, but expanduser() still returns root, causing chia to fail with a permission error as it tries to access root's homedir. This is specifically happening for the keyring so it could be worked around with env vars, but that seems like a somewhat brittle solution

I suppose being able to pass the host user's UID/GID is a bit of scope creep though it would have been nice to have :)
Have you gotten any non-root version of chia-docker to run (eg. without s6-overlay)?

yea, sorry for the delay. Work has been busy lately so I've been a tad behind on stuff. I'm not sure how you want to setup the tagging of images and stuff, but I'll make a PR and we can discuss it there

I am deploying the official docker image on a server and noticed that it runs the Chia daemon as the root user, so this issue isn't stale but still present, thus re-opening.
As far as I can tell no functionality in the chia node software seems to need super-user privileges of root (no privileged network ports, nothing changes system-owned files). My previous node ran fine without root. From a security point-of-view, running any process as root, even when running inside a container puts the system security of the host and other containers running on the same host at risk in case of a container escape vulnerability. Such escape vulnerability happened just a month ago. So switching to an unprivileged user would greatly improve the host system and container security.

As far as I can tell no functionality in the chia node software seems to need super-user privileges of root

This is a very flexible image and runs many of the services bundled in a typical chia installation. Including seeders (runs on port 53.) But the use of super user privileges also extends over to installing dependencies for timelord processes, as well as plotters. A lot of functionality that people utilize in this image does actually require super user privileges.
An iteration of this container that doesn't use root privileges may be nice to have, I agree, but would indeed be a breaking change to many consumers of the image.
The vulnerability linked above for container escaping matches some of the unique requirements for exploitation as the other ones I've seen. Often requiring access to the host running the container already. In the case of this one, the vulnerability needs to be purposefully built into the image at build time, alternatively the exploit only sounds to be possible if the user of the image built it on the same machine they're running it on, on a machine that has runc version <=1.1.11 installed, if I'm reading the vulnerability summary right. That one is a bit worse than the other cases I've seen, simply due to appearing to not need initial access to the host computer.


Code for pure yellow missing from docs/themes/skins

Code for #FFFF00 is missing. See attached screenshot.

Edit: Looks like it's also missing for boxes with the same color involved.

It seems like gold label was just changed to yellow. Notice further down in the screenshot where the gold color is incorrectly labeled.

looks like there are a few light blues missing labels (#408BC9 & #76C4E2). there are also some layout issues happening in the a11y combos below.


vhdl-ls: init at 0.64.0

Description of changes
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

Commit name: vhdl-ls (because that is the package name at top-level)

Thanks for the review comments! It's supposed to work now. Unmarking as draft.


[AMORO-2484] Add doAs to Spark query

fix #2484
Why are the changes needed?
In the existing Spark query code, only some places use the built-in ugi, that is, the doAs method. Therefore, when multiple HDFS clusters are involved, authentication problems may occur during the query process.
Close #2484.
Brief change log
First, in
Add a getArcticFileIo() method to AbstractKeyedDataReader and AbstractUnkeyedDataReader to obtain fileIO objects.
After that, in the read method next() of UnkeyedSparkBatchScan and KeyedSparkBatchScan, read the data through the doAs method of fileIO above.
In addition, the return type of AbstractUnkeyedDataReader.readData has been modified to be consistent with AbstractKeyedDataReader.
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 making a pull request

Documentation

Does this pull request introduce a new feature? (yes / no)
no

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: ShawHee:x: Chao HeChao He seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

The CI is failed. Could you please take a look?


⚠ Carbubu has degraded performance

In a43de39, Carbubu (https://carbubu.fr) experienced degraded performance:

HTTP code: 200
Response time: 5067 ms

Resolved: Carbubu performance has improved in 013b766.


Removed key column

#25

hm, for now it is not used in javascript

Do you mean it is used? I see, then let's keep it. Please merge to develop, thanks!

no, no usage in javascript.

I can see it used in Polymer bindings in <option> tags, so I think it is used.


'Storage Blob Data Reader' Role is not enough

When I try to retrieve all blobs via NewListBlobsFlatPager of the azblob package in the Go SDK, the proposed role is not enough. I always get an 403 error. When I use 'Storage Blob Data Owner' Role for my principal it works. But I agree to the Docs that a reader role should be enough!

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

ID: 1ca94e03-5f05-6703-1672-8062f31c0780
Version Independent ID: a6a8d9e9-9aac-c0ed-c474-34cbd0609584
Content: Assign an Azure role for access to blob data - Azure Storage
Content Source: articles/storage/blobs/assign-azure-role-data-access.md
Service: azure-blob-storage
GitHub Login: @pauljewellmsft
Microsoft Alias: pauljewell

@lebogg
Thank you for bringing this to our attention. I understand that you are having issues retrieving all blobs via NewListBlobsFlatPager of the azblob package in the Go SDK.
This article uses Storage Blob Data Reader as an example only.
To clarify, the 'Storage Blob Data Reader' role should be sufficient to retrieve all blobs via NewListBlobsFlatPager. However, it seems that in your case, this role is not enough and you are receiving a 403 error.
It is possible that there may be other factors at play, such as the specific permissions granted to the role or the configuration of your storage account. I would recommend reviewing the permissions granted to the 'Storage Blob Data Reader' role and ensuring that they are sufficient for your use case.
If you continue to experience issues, you may want to consider reaching out to Azure support for further assistance.
I'd recommend posting your question in https://azure.microsoft.com/en-us/support/community/


Issue running setup.py with Windows 7 and Python 3.5

This is the error I get in powershell:
WARNING: '' not a valid package name; please use only .-separated package names in setup.py
running install
Checking .pth file support in .
F:\Python35\pythonw.exe -E -c pass
TEST FAILED: .\ does NOT support .pth files
error: bad install directory or PYTHONPATH
You are attempting to install a package to a directory that is not
on PYTHONPATH and which Python does not read ".pth" files from.  The
installation directory you specified (via --install-dir, --prefix, or
the distutils default setting) was:
.\

and your PYTHONPATH environment variable currently contains:
''

Here are some of your options for correcting the problem:

You can choose a different installation directory, i.e., one that is
on PYTHONPATH or supports .pth files

You can add the installation directory to the PYTHONPATH environment
variable.  (It must then also be on PYTHONPATH whenever you run
Python and want to use the package(s) you are installing.)

You can set up the installation directory to support ".pth" files by
using one of the approaches described here:
https://setuptools.readthedocs.io/en/latest/easy_install.html#custom-installation-locations

Please make the appropriate changes for your system and try again.

I thought the issue was with using the release version for python 2.7, however when cloning the master branch, which should be compatible with python 3.5, I get the same isse.
Also, in setup.py on line 48 the class for Cython versions raises an error when trying to install with python 3.5:
Traceback (most recent call last):
File "setup.py", line 48, in
class build_ext_compiler_check(build_ext):
NameError: name 'build_ext' is not defined

Hi D-Chase-H,
I have deleted the setup.cfg file which was causing your first error (this used to be required, but apparently it is not anymore).
Your second error related to 'build_ext' is most likely because Cython is not installed, and I was missing an import. This has been fixed in setup.py.
I have tested these changes in Python 2.7 and 3.6 on Windows 64 bit and have updated the latest master repo. Please try again and let me know if you have any further issues.
Cheers,
Michael


Publish new version?

Hi there! I notice when I go get github.com/machinebox/graphql, the version I have is missing the response status code checks that landed in https://github.com/machinebox/graphql/pull/19. Does something need to be published or a version updated for me to get the latest code? Thank you!

@cheshire137 I also just ran into this and found out you can specify a sha like this:
go get github.com/machinebox/graphql@3a92531802258604bd12793465c2e28bc4b2fc85

Thanks for the tip @michaeldwan 👍
A proper new release would definitely be welcome, especially given that there are things mentioned in the docs (req.Query etc) that are in leading edge master but not in any published release which is a little frustrating.
Given that the last commit was around a year ago and there's 11 PRs outstanding, is this package still being maintained?

@necrophonic it doesn't look like it is, even extensions haven't been added to to the error structs, leaving the returned error from run pretty useless. Anyone know of a maintained alternative?

https://github.com/shurcooL/graphql seems more maintained.
Moreover, there's no client supporting subscriptions as far as I can see.

i just forked it and merged some of the open PRs into my fork using that for now.

Great, let us know how it goes.
Yours might become the "official" golang graphql client library.

@jaylane Sounds like a good plan!

@necrophonic @adrianog its working well forked it and cherrypicked some of the open PRs highly recommend doing it.

Thanks Jaylane - we can we use https://github.com/jaylane/graphql ? Have you pushed all your changes already?

@adrianog the updated version is on our private gitlab repo, i’ll make it public in the next few days and let you know when you can grab it

Any update on this? The state of GraphQL clients for Go is pathetic!


add example upstart config

Upstart? Hasn't even Ubuntu migrated to systemd already?

AFAIK the first Ubuntu LTS release with planned systemd support will be 16.04 which won't be available until april 2016. The current LTS release 14.04 only has upstart.


Support Nitter as an alternative twitter proxy

https://nitter.net/Twitter

Don't know nitter, is there any useful resource about this?


[#57] Automate development workflow with vagga

Here is a basic vagga.yaml, which starts an application alongside mysql database. Once it is complete, it should resolve #57.
A vagrant-vagga is used to run this on OSX.
A @phiNumber's PR (#97) was taken as a base.
However I have a problem with configuring

[x] fixtures
[x] blueberrypy config

Please can anybody look into it?
/cc @webknjaz @cleac

Current coverage is 10.65% (diff: 100%)

Merging #113 into master will not change coverage

@@             master       #113   diff @@
==========================================
  Files            21         21
  Lines          1379       1379
  Methods           0          0
  Messages          0          0
  Branches        170        170
==========================================
  Hits            147        147
  Misses         1200       1200
  Partials         32         32

Powered by Codecov. Last update 8a78940...48c2158

@anxolerd I would like to have utility containers like these https://github.com/wk-tech/crm-smsfly/blob/master/vagga.yaml#L2-L57 as well

What do you mean by saying fixtures?

Regarding config, @cleac has pointed to this awesome options called environment-file in vagga. I think you should add it and force devs to fill its contents (document in readme) by themselves.

fixtures -- it would be nice to pre-populate db with dummy test data, developers can use for testing purposes. I call this test data fixtures.

Then add some script for this

I've added basic fixtures to project.

Made adjustments according to latest @webknjaz notes

BTW, feel free to commit in this branch =)
/cc @webknjaz @cleac

@webknjaz

I would like to have utility containers

I actually cannot see any profit in having them.

ansible -- this one is used for deploy. We need to establish dev workflow before implementing deploy. In addition to that, I only know what ansible is, nothing more,  hence I cannot implement it efficiently.
app-freezer -- i really have no idea why this one is needed. As I saw in examples, this one is used to generate requirements.txt which is added to the repo and used by other container later. Why should we duplicate requirements both in vagga.yaml and requirements.txt ?

Ehm... Codacy, you're drunk! Go home!!!!

@codacy-bot is right. Plz fix issues

Regarding containers, ansible is meant to be available, so nobody would need to install it locally.
And app-freezer is needed to regenerate requirements.txt with a bunch of new versions periodically.
Currently you may skip these, but they're useful to be in place
.

@webknjaz @cleac
I've tried to make CI use dark side of the Force vagga.
Please, take a look)

I have no time to commit here, hence if there are some misc changes (like rename file, etc), I'd appreciate if you do that yourself.

@webknjaz
There are some issues:

Fixtures and migrations
Because usage of those requires python and alembic, I cannot run them on database initialization. Hence the ugly hack is  required in the application startup script. If we use forward-only sql migrations and sql fixtures, it will be easier to maintain them. Moreover, having those things in pure SQL we will have more control on what actually happens to database. As for backwards migrations -- why do we need them at all?
pre-commit.
I believe we should use simple linters like flake8 or pyflakes instead of pre-commit. While it is really convenient thing to manage pre-commit hooks, it does its own magic with virtualenvs an so on. This is not so good for CI and alike things. Hence, my proposal is to use standalone linters instead of pre-commit. As for pre-commit itself, we can leave its configuration so everyone could set up proper hooks by himself.

Ping @webknjaz

Lets freeze everything as is now. I'm not going to drop pre-commit and will look into it later. Now I just want to merge this PR

Okay, I want this as well. Please list in a single comment what must be
done for that. Cause I am loosing myself in code comments...
TIA
On Sun, Dec 18, 2016, 1:14 AM Sviatoslav Sydorenko<EMAIL_ADDRESS>wrote:

Lets freeze everything as is now. I'm not going to drop pre-commit and
will look into it later. Now I just want to merge this PR
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/GDG-Ukraine/gdg.org.ua/pull/113#issuecomment-267793154,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGOxzvkQIDSbGGq1cA3y8T1ryuPjsxLSks5rJGzYgaJpZM4Jpaxr
.

I've altered some stuff and I think now it's basically ready for merge.


Use any whitespace in indentation of multiline regular strings

Currently, multiline regular strings trim away newlines and literal tab characters so that the string can be indented when multilined. Some (or most) editors insert multiple spaces instead of the tab character when the tab key is pressed, so it takes a bit more effort to get a tab character for use here.
For ergonomics, an alternative (possibly breaking change) is if the first " is immediately followed by a newline, the first sequence of spaces right after that newline (e.g. 4 spaces) will become the reference sequence spacing, that would be removed in the following lines.
As an example, given:
local a = "
    this is a
    regular string
        and maybe i need this spacing here
        and here too
    and back to no spacing

    hello
    world
"

it will become
local a = "this is aregular string    and maybe i need this spacing here    and here tooand back to no spacinghelloworld"

This might be unnecessary complexity or might be too confusing, so it should probably be a flag instead of being a default if implemented.

the flag could let you choose between X spaces or tabs, or between letting the preprocessor figure it out on its own on every file
But then, what should the default value of the flag be?

Having a set amount of whitespace (constant) might be detrimental since the string can be in any depth.
local a, b
if A {
    a = "
        hello
        world
    "
    if B {
        b = "
            and hello
            Clue
        "
    }
}

Probably best to make it figure it out on its own for each string.

okay, but what if someone does want a bit of spaces before? how could it tell the preprocessor "no wait stop a bit earlier"

okay, but what if someone does want a bit of spaces before? how could it tell the preprocessor "no wait stop a bit earlier"

local str = "

  spaces will now be preserved
"

This would turn into:
local str = "  spaces will now be preserved"
So that's not an issue.


async clientPrefetch hook - analog of serverPrefetch, waiting for data loaded on client

What problem does this feature solve?
Here are discussions: https://github.com/vuejs/vue-router/issues/1144 https://github.com/vuejs/vue/issues/7209 https://github.com/vuejs/pinia/discussions/988
There are cases where you need some data fetched before other components are initialized (mount hook called), for example authentication checked or user data fetched.
Currently need to use watches, which might be multiple, instead of a simple mounted hook in child components.
What does the proposed API look like?
Just the same as serverPrefetch, but on client.

Can't this be achieved by using the async setup and Suspense? Or by using the navigation guards from vue-router?


Exporters onnx module

What does this PR do?

Fixes # (issue)
Before submitting

[ ] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
[ ] Did you make sure to update the documentation with your changes?
[ ] Did you write any new necessary tests?

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.

Any plans or advice about adding speech related tasks ?

Hi @flozi00 ,
Yes the plan is to cover as much models as possible, so we will definitely support speech related tasks. It will happen in multiple PRs though.


Add new pwa app dresez

if you want I'm making https://www.pwaawards.com/ and would love for you make a pr @fawaz-ahmed


mirrorVolumeMounts not working after upgrade to 3.1.0

Summary
After upgrading to v.3.1.0, workflows using the mirrorVolumeMounts in initContainers or sidecars attributes are not working as expected anymore.
I noticed that the pods started by the workflows do not mount the main container's volumes in sidecars or init containers anymore.
I did not see any error or warning in workflow controller logs.
Diagnostics
What Kubernetes provider are you using?
GKE 1.19
What version of Argo Workflows are you running?
v3.1.0
What executor are you running? Docker/K8SAPI/Kubelet/PNS/Emissary
Docker
Did this work in a previous version? I.e. is it a regression?
This feature was working correctly in v3.0.1.
Example workflow template:
apiVersion: argoproj.io/v1alpha1
kind: ClusterWorkflowTemplate
metadata:
  name: workflow-with-mirror-volumes
spec:
  templates:
  - name: main
    inputs:
      parameters:
        - name: secret_name_ref
    steps:
    - - name: build
        template: build
        arguments:
          parameters:
            - name: secret_name_ref
              value: "{{inputs.parameters.secret_name_ref}}"

  - name: build
    inputs:
      parameters:
        - name: test
    volumes:
      - configMap:
          name: config
        name: config
      - secret:
          secretName: '{{inputs.parameters.secret_name_ref}}'
        name: build-args
      - emptyDir: { }
        name: credentials
      - emptyDir: { }
        name: log
    container:
      volumeMounts:
        - name: workspace
          mountPath: /workspace
        - mountPath: /root/creds/
          name: credentials
        - mountPath: /log
          name: log
        - mountPath: /workspace/build-args
          subPath: build-args
          name: build-args
      name: build
      image: build
      imagePullPolicy: Always
    sidecars:
      - image: fluentd
        name: fluent
        mirrorVolumeMounts: true
        volumeMounts:
          - name: conf
            mountPath: /fluentd/etc/
    initContainers:
      - name: creds
        image: creds
        imagePullPolicy: Always
        mirrorVolumeMounts: true

Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.

Can you confirm if this works when creating a workflow directly rather than using a template? This will help us understand if the bug is in templates code or elsewhere.

Just tried without using a template and it seems to work.
So the issue might be linked to templates indeed.
FYI, I'm also using a volumeClaimTemplates in my workflow, which is then supposed to be mounted in main and sidecar containers.

@alexec Hi !
Just wanted to know if you had any update on this, as we are still stuck with version 3.0.1 for now because of this issue.
If you need any more information or help investigating the issue, please let me know, I will gladly help.

This is with @sarabala1979 to prioritise.

@stevenbressey I tried with the latest build. I can see the volumes are mounting on init and sidecar.  can you provide you pod yaml? Can you try with v3.1.2?
Here step I followed
create clusterworkflow template
apiVersion: argoproj.io/v1alpha1
kind: ClusterWorkflowTemplate
metadata:
  name: workflow-with-mirror-volumes
spec:
  entrypoint: volumes-emptydir-example
  volumes:
    - name: workdir
      emptyDir: {}

  templates:
    - name: volumes-emptydir-example
      container:
        image: debian:latest
        command: ["/bin/bash", "-c"]
        args: ["
        vol_found=`mount | grep /mnt/vol` && \
        if [[ -n $vol_found ]]; then echo \"Volume mounted and found\"; else echo \"Not found\"; fi
      "]
        volumeMounts:
          - name: workdir
            mountPath: /mnt/vol
      sidecars:
        - image: debian:latest
          name: fluent
          mirrorVolumeMounts: true
      initContainers:
        - name: creds
          image: debian:latest
          imagePullPolicy: Always
          mirrorVolumeMounts: true

pod yaml
spec:
  containers:
  - command:
    - argoexec
    - wait
    - --loglevel
    - debug
    env:
    - name: ARGO_POD_NAME
      valueFrom:
        fieldRef:
          apiVersion: v1
          fieldPath: metadata.name
    - name: ARGO_CONTAINER_RUNTIME_EXECUTOR
      value: pns
    - name: GODEBUG
      value: x509ignoreCN=0
    - name: ARGO_CONTAINER_NAME
      value: wait
    - name: ARGO_TEMPLATE
      value: '{"name":"volumes-emptydir-example","inputs":{},"outputs":{},"metadata":{},"container":{"name":"","image":"debian:latest","command":["/bin/bash","-c"],"args":["
        vol_found=`mount | grep /mnt/vol` \u0026\u0026 if [[ -n $vol_found ]]; then
        echo \"Volume mounted and found\"; else echo \"Not found\"; fi "],"resources":{},"volumeMounts":[{"name":"workdir","mountPath":"/mnt/vol"}]},"initContainers":[{"name":"creds","image":"debian:latest","resources":{},"imagePullPolicy":"Always","mirrorVolumeMounts":true}],"sidecars":[{"name":"fluent","image":"debian:latest","resources":{},"mirrorVolumeMounts":true}]}'
    - name: ARGO_INCLUDE_SCRIPT_OUTPUT
      value: "false"
    - name: ARGO_DEADLINE
      value: "0001-01-01T00:00:00Z"
    image: argoproj/argoexec:agent
    imagePullPolicy: Never
    name: wait
    resources:
      limits:
        cpu: 500m
        memory: 128Mi
      requests:
        cpu: 100m
        memory: 64Mi
    securityContext:
      capabilities:
        add:
        - SYS_PTRACE
        - SYS_CHROOT
    terminationMessagePath: /dev/termination-log
    terminationMessagePolicy: File
    volumeMounts:
    - mountPath: /mainctrfs/mnt/vol
      name: workdir
    - mountPath: /var/run/secrets/kubernetes.io/serviceaccount
      name: default-token-pbw7w
      readOnly: true
  - args:
    - ' vol_found=`mount | grep /mnt/vol` && if [[ -n $vol_found ]]; then echo "Volume
      mounted and found"; else echo "Not found"; fi '
    command:
    - /bin/bash
    - -c
    env:
    - name: ARGO_CONTAINER_NAME
      value: main
    - name: ARGO_TEMPLATE
      value: '{"name":"volumes-emptydir-example","inputs":{},"outputs":{},"metadata":{},"container":{"name":"","image":"debian:latest","command":["/bin/bash","-c"],"args":["
        vol_found=`mount | grep /mnt/vol` \u0026\u0026 if [[ -n $vol_found ]]; then
        echo \"Volume mounted and found\"; else echo \"Not found\"; fi "],"resources":{},"volumeMounts":[{"name":"workdir","mountPath":"/mnt/vol"}]},"initContainers":[{"name":"creds","image":"debian:latest","resources":{},"imagePullPolicy":"Always","mirrorVolumeMounts":true}],"sidecars":[{"name":"fluent","image":"debian:latest","resources":{},"mirrorVolumeMounts":true}]}'
    - name: ARGO_INCLUDE_SCRIPT_OUTPUT
      value: "false"
    - name: ARGO_DEADLINE
      value: "0001-01-01T00:00:00Z"
    image: debian:latest
    imagePullPolicy: Always
    name: main
    resources: {}
    terminationMessagePath: /dev/termination-log
    terminationMessagePolicy: File
    volumeMounts:
    - mountPath: /mnt/vol
      name: workdir
    - mountPath: /var/run/secrets/kubernetes.io/serviceaccount
      name: default-token-pbw7w
      readOnly: true
  - env:
    - name: ARGO_CONTAINER_NAME
      value: fluent
    - name: ARGO_TEMPLATE
      value: '{"name":"volumes-emptydir-example","inputs":{},"outputs":{},"metadata":{},"container":{"name":"","image":"debian:latest","command":["/bin/bash","-c"],"args":["
        vol_found=`mount | grep /mnt/vol` \u0026\u0026 if [[ -n $vol_found ]]; then
        echo \"Volume mounted and found\"; else echo \"Not found\"; fi "],"resources":{},"volumeMounts":[{"name":"workdir","mountPath":"/mnt/vol"}]},"initContainers":[{"name":"creds","image":"debian:latest","resources":{},"imagePullPolicy":"Always","mirrorVolumeMounts":true}],"sidecars":[{"name":"fluent","image":"debian:latest","resources":{},"mirrorVolumeMounts":true}]}'
    - name: ARGO_INCLUDE_SCRIPT_OUTPUT
      value: "false"
    - name: ARGO_DEADLINE
      value: "0001-01-01T00:00:00Z"
    image: debian:latest
    imagePullPolicy: Always
    name: fluent
    resources: {}
    terminationMessagePath: /dev/termination-log
    terminationMessagePolicy: File
    volumeMounts:
    - mountPath: /mnt/vol
      name: workdir
    - mountPath: /var/run/secrets/kubernetes.io/serviceaccount
      name: default-token-pbw7w
      readOnly: true
  dnsPolicy: ClusterFirst
  enableServiceLinks: true
  initContainers:
  - env:
    - name: ARGO_CONTAINER_NAME
      value: creds
    - name: ARGO_TEMPLATE
      value: '{"name":"volumes-emptydir-example","inputs":{},"outputs":{},"metadata":{},"container":{"name":"","image":"debian:latest","command":["/bin/bash","-c"],"args":["
        vol_found=`mount | grep /mnt/vol` \u0026\u0026 if [[ -n $vol_found ]]; then
        echo \"Volume mounted and found\"; else echo \"Not found\"; fi "],"resources":{},"volumeMounts":[{"name":"workdir","mountPath":"/mnt/vol"}]},"initContainers":[{"name":"creds","image":"debian:latest","resources":{},"imagePullPolicy":"Always","mirrorVolumeMounts":true}],"sidecars":[{"name":"fluent","image":"debian:latest","resources":{},"mirrorVolumeMounts":true}]}'
    - name: ARGO_INCLUDE_SCRIPT_OUTPUT
      value: "false"
    - name: ARGO_DEADLINE
      value: "0001-01-01T00:00:00Z"
    image: debian:latest
    imagePullPolicy: Always
    name: creds
    resources: {}
    terminationMessagePath: /dev/termination-log
    terminationMessagePolicy: File
    volumeMounts:
    - mountPath: /mnt/vol
      name: workdir
    - mountPath: /var/run/secrets/kubernetes.io/serviceaccount
      name: default-token-pbw7w
      readOnly: true
  priority: 0
  restartPolicy: Never
  schedulerName: default-scheduler
  securityContext: {}
  serviceAccount: default
  serviceAccountName: default
  shareProcessNamespace: true
  terminationGracePeriodSeconds: 30
  tolerations:
  - effect: NoExecute
    key: node.kubernetes.io/not-ready
    operator: Exists
    tolerationSeconds: 300
  - effect: NoExecute
    key: node.kubernetes.io/unreachable
    operator: Exists
    tolerationSeconds: 300
  volumes:
  - emptyDir: {}
    name: workdir
  - name: default-token-pbw7w
    secret:
      defaultMode: 420
      secretName: default-token-pbw7w
status:
  conditions:
  - lastProbeTime: null
    lastTransitionTime: "2021-07-22T05:07:16Z"
    message: '0/1 nodes are available: 1 node(s) had taint {node.kubernetes.io/unreachable:
      }, that the pod didn''t tolerate.'
    reason: Unschedulable
    status: "False"
    type: PodScheduled
  phase: Pending
  qosClass: Burstable

Hi @sarabala1979 , thank you for your answer.
I have tried with v3.1.2, but got the same error.
My cluster workflow template is actually a bit more complicated as it contains multiple templates and sub steps. I'd be happy to share it with you on Slack if you have time.
Also, have you tried with a volumeClaimTemplates configured at the workflow level ? I will run some more tests to check if the issue is the same with an emptyDir volume.
Here is my pod yaml:
spec:
  containers:
  - command:
    - argoexec
    - wait
    - --loglevel
    - info
    env:
    - name: ARGO_POD_NAME
      valueFrom:
        fieldRef:
          apiVersion: v1
          fieldPath: metadata.name
    - name: ARGO_CONTAINER_RUNTIME_EXECUTOR
    - name: GODEBUG
      value: x509ignoreCN=0
    - name: ARGO_CONTAINER_NAME
      value: wait
    - name: ARGO_INCLUDE_SCRIPT_OUTPUT
      value: "false"
    image: argoproj/argoexec:v3.1.2
    imagePullPolicy: IfNotPresent
    name: wait
    resources: {}
    terminationMessagePath: /dev/termination-log
    terminationMessagePolicy: File
    volumeMounts:
    - mountPath: /argo/podmetadata
      name: podmetadata
    - mountPath: /var/run/docker.sock
      name: docker-sock
      readOnly: true
    - mountPath: /var/run/secrets/kubernetes.io/serviceaccount
      name: workflow-token-lxxff
      readOnly: true
  - args:
    - myarg
    env:
    - name: DOCKER_HOST
      value: tcp://<IP_ADDRESS>:2376
    - name: DOCKER_TLS_CERTDIR
      value: /certs
    - name: ARGO_CONTAINER_NAME
      value: dockerfile
    - name: ARGO_INCLUDE_SCRIPT_OUTPUT
      value: "false"
    image: builder
    imagePullPolicy: Always
    name: dockerfile
    resources: {}
    terminationMessagePath: /dev/termination-log
    terminationMessagePolicy: File
    volumeMounts:
    - mountPath: /workspace
      name: workspace
    - mountPath: /certs
      name: docker-certs
    - mountPath: /log
      name: log
    - mountPath: /workspace/Dockerfile
      name: dockerfile
      subPath: Dockerfile
    - mountPath: /var/run/secrets/kubernetes.io/serviceaccount
      name: workflow-token-lxxff
      readOnly: true
  - env:
    - name: ARGO_CONTAINER_NAME
      value: fluent
    - name: ARGO_INCLUDE_SCRIPT_OUTPUT
      value: "false"
    image: fluentd
    imagePullPolicy: IfNotPresent
    name: fluent
    resources: {}
    terminationMessagePath: /dev/termination-log
    terminationMessagePolicy: File
    volumeMounts:
    - mountPath: /fluentd/etc/
      name: fluentd-conf
    - mountPath: /var/run/secrets/kubernetes.io/serviceaccount
      name: workflow-token-lxxff
      readOnly: true
  - env:
    - name: DOCKER_TLS_CERTDIR
      value: /certs
    - name: ARGO_CONTAINER_NAME
      value: dind
    - name: ARGO_INCLUDE_SCRIPT_OUTPUT
      value: "false"
    image: docker:20.10-dind
    imagePullPolicy: IfNotPresent
    name: dind
    resources:
      limits:
        ephemeral-storage: 10Gi
      requests:
        ephemeral-storage: 5Gi
    securityContext:
      privileged: true
    terminationMessagePath: /dev/termination-log
    terminationMessagePolicy: File
    volumeMounts:
    - mountPath: /certs
      name: docker-certs
    - mountPath: /var/run/secrets/kubernetes.io/serviceaccount
      name: workflow-token-lxxff
      readOnly: true
  dnsPolicy: ClusterFirst
  enableServiceLinks: true
  initContainers:
  - args:
    - myarg
    env:
    - name: ARGO_CONTAINER_NAME
      value: creds-loader
    - name: ARGO_INCLUDE_SCRIPT_OUTPUT
      value: "false"
    image: creds-loader
    imagePullPolicy: Always
    name: creds-loader
    resources: {}
    terminationMessagePath: /dev/termination-log
    terminationMessagePolicy: File
    volumeMounts:
    - mountPath: /var/run/secrets/kubernetes.io/serviceaccount
      name: workflow-token-lxxff
      readOnly: true
  nodeName: node
  preemptionPolicy: PreemptLowerPriority
  priority: 0
  restartPolicy: Never
  schedulerName: default-scheduler
  securityContext: {}
  serviceAccount: workflow
  serviceAccountName: workflow
  terminationGracePeriodSeconds: 30
  tolerations:
  - effect: NoSchedule
    key: workload-node-pool
    operator: Exists
  - effect: NoExecute
    key: node.kubernetes.io/not-ready
    operator: Exists
    tolerationSeconds: 300
  - effect: NoExecute
    key: node.kubernetes.io/unreachable
    operator: Exists
    tolerationSeconds: 300
  volumes:
  - downwardAPI:
      defaultMode: 420
      items:
      - fieldRef:
          apiVersion: v1
          fieldPath: metadata.annotations
        path: annotations
    name: podmetadata
  - hostPath:
      path: /var/run/docker.sock
      type: Socket
    name: docker-sock
  - configMap:
      defaultMode: 420
      name: ecr-docker-config
    name: docker-config
  - configMap:
      defaultMode: 420
      name: fluentd-conf
    name: fluentd-conf
  - emptyDir: {}
    name: log
  - emptyDir: {}
    name: docker-certs
  - configMap:
      defaultMode: 420
      name: dockerfile
    name: dockerfile
  - name: workspace
    persistentVolumeClaim:
      claimName: myclaim
  - name: workflow-token-lxxff
    secret:
      defaultMode: 420
      secretName: workflow-token-lxxff
status:
  conditions:
  - lastProbeTime: null
    lastTransitionTime: "2021-07-22T12:56:54Z"
    message: 'containers with incomplete status: [creds-loader]'
    reason: ContainersNotInitialized
    status: "False"
    type: Initialized
  - lastProbeTime: null
    lastTransitionTime: "2021-07-22T12:56:54Z"
    message: 'containers with unready status: [wait dockerfile fluent dind]'
    reason: ContainersNotReady
    status: "False"
    type: Ready
  - lastProbeTime: null
    lastTransitionTime: "2021-07-22T12:56:54Z"
    message: 'containers with unready status: [wait dockerfile fluent dind]'
    reason: ContainersNotReady
    status: "False"
    type: ContainersReady
  - lastProbeTime: null
    lastTransitionTime: "2021-07-22T12:56:54Z"
    status: "True"
    type: PodScheduled
  containerStatuses:
  - image: docker:20.10-dind
    imageID: ""
    lastState: {}
    name: dind
    ready: false
    restartCount: 0
    started: false
    state:
      waiting:
        reason: PodInitializing
  - image: builder
    imageID: ""
    lastState: {}
    name: dockerfile
    ready: false
    restartCount: 0
    started: false
    state:
      waiting:
        reason: PodInitializing
  - image: fluentd
    imageID: ""
    lastState: {}
    name: fluent
    ready: false
    restartCount: 0
    started: false
    state:
      waiting:
        reason: PodInitializing
  - image: argoproj/argoexec:v3.1.2
    imageID: ""
    lastState: {}
    name: wait
    ready: false
    restartCount: 0
    started: false
    state:
      waiting:
        reason: PodInitializing
  initContainerStatuses:
  - containerID: docker://1caf8d7a2fb924499bac163ec5078077960ba32e6c4fe7393e3054d2b58c28c9
    image: loader
    lastState: {}
    name: creds-loader
    ready: false
    restartCount: 0
    state:
      terminated:
        containerID: docker://1caf8d7a2fb924499bac163ec5078077960ba32e6c4fe7393e3054d2b58c28c9
        exitCode: 1
        finishedAt: "2021-07-22T12:57:01Z"
        reason: Error
        startedAt: "2021-07-22T12:57:00Z"
  phase: Failed
  qosClass: BestEffort
  startTime: "2021-07-22T12:56:54Z"

Thank you for your help.

@stevenbressey  problem could be In your template definition, the main container has named as a dockerfile. Argo container is looking name as main. Please remove the name field in your main container or name to main

Issue fixed after removing container name in the template.
Thank you @sarabala1979


java.io.IOException: An existing connection was forcibly closed by the remote host

你是在什么情况下出现这个问题的，能否提供更多的日志信息

你是在什么情况下出现这个问题的，能否提供更多的日志信息

I received this error from @RequestMapping("/upload/{playChannel}") after uploading and playing the stream for about 3-5 minutes.

你是在什么情况下出现这个问题的，能否提供更多的日志信息

I think the problem is in the RtspTransThread.
while (true){
if(!process.isAlive()){
break;
}
if(Thread.currentThread().isInterrupted()){
process.destroy();
break;
}
}
int exitValue = process.waitFor();
            if(Thread.currentThread().isInterrupted()){
                break;
            }

do you POST /stream/play within 60s again？
i think it is not a problem. when you first POST /stream/play, RtspTransThread start a stream.And if you don't POST /stream/play in 60s again,the timer will interrupt the RtspTransThread to stop the stream, then the RtspTransThread  will end,and print these Exception info,it will not crash the program,just print Exception info,i will deal it after.
you should POST /stream/play  maybe every 30s ( less than 60s ).
in demo, you should click the 'play' button every 30s.

do you POST /stream/play within 60s again？
i think it is not a problem. when you first POST /stream/play, RtspTransThread start a stream.And if you don't POST /stream/play in 60s again,the timer will interrupt the RtspTransThread to stop the stream, then the RtspTransThread will end,and print these Exception info,it will not crash the program,just print Exception info,i will deal it after.
you should POST /stream/play maybe every 30s ( less than 60s ).
in demo, you should click the 'play' button every 30s.

So basically you need to play every 30s for it to stream without interruption?

do you POST /stream/play within 60s again？
i think it is not a problem. when you first POST /stream/play, RtspTransThread start a stream.And if you don't POST /stream/play in 60s again,the timer will interrupt the RtspTransThread to stop the stream, then the RtspTransThread will end,and print these Exception info,it will not crash the program,just print Exception info,i will deal it after.
you should POST /stream/play maybe every 30s ( less than 60s ).
in demo, you should click the 'play' button every 30s.

So basically you need to play every 30s for it to stream without interruption?

yes,this design is for auto close stream,if nobody POST /stream/play 60s,the stream auto close.

do you POST /stream/play within 60s again？
i think it is not a problem. when you first POST /stream/play, RtspTransThread start a stream.And if you don't POST /stream/play in 60s again,the timer will interrupt the RtspTransThread to stop the stream, then the RtspTransThread will end,and print these Exception info,it will not crash the program,just print Exception info,i will deal it after.
you should POST /stream/play maybe every 30s ( less than 60s ).
in demo, you should click the 'play' button every 30s.

So basically you need to play every 30s for it to stream without interruption?

yes,this design is for auto close stream,if nobody POST /stream/play 60s,the stream auto close.

Yes, I saw your code you put a 1 minute interval in timer.


[ENHANCEMENT] Support for Including External TOML Files in robot.toml

Description:
Overview:
I would like to propose an enhancement for RobotCode to support the inclusion of external TOML files within the robot.toml configuration file. This feature would allow for a modular and organized configuration management approach, enabling users to maintain cleaner and more manageable TOML files.
Current Behavior:
Currently, the robot.toml file does not support including other TOML files directly. Multiple configuration files can be specified via the command line, but this approach can become cumbersome and less intuitive for managing complex configurations.
Proposed Enhancement:
I propose adding support for including external TOML files within the robot.toml file using a config_files directive. This directive would allow users to specify additional TOML files to be included and merged into the main configuration.
Example Usage:
Here is an example of how the config_files directive could be used in robot.toml:

# Import additional configuration files
config-files = [
    "config/movement.toml",
    "config/sensors.toml",
    "config/actuators.toml"
]

extend-config-files = [
    "config/movement.toml",
    "config/sensors.toml",
    "config/actuators.toml"
]

The contents of the imported TOML files would be merged with the main robot.toml configuration. If there are conflicts, the values in the main robot.toml file would take precedence.
Benefits:

Modularity: Allows for a more modular configuration setup, making it easier to manage large and complex configurations.
Organization: Helps in organizing configurations by separating different aspects into individual files.
Reusability: Promotes reusability of configuration files across different projects or components.
Ease of Use: Simplifies the process of managing configurations without relying on command-line arguments.

Implementation Considerations:

Parsing Order: The imported files should be parsed and merged in the order they are listed.
Conflict Resolution: Clearly define how conflicts are resolved when merging configurations.
Error Handling: Provide meaningful error messages if imported files are missing or contain invalid syntax.

Conclusion:
Adding support for importing external TOML files in the robot.toml configuration file would greatly enhance the flexibility and manageability of configurations in RobotCode. This feature would complement the existing command-line options and provide a more intuitive way to handle complex configurations. I believe this feature would be a valuable addition and look forward to discussing its potential implementation.

Overview:
I would like to propose an enhancement for RobotCode to implement a modular configuration system using a robot.toml.d directory. This approach is inspired by the way many Linux configuration files are handled in the /etc directory. Instead of introducing a config-files directive within robot.toml, users would have the option to split their configurations into multiple files placed within a designated robot.toml.d directory. This would provide a more structured and maintainable method of managing complex configurations.
Current Behavior:
At present, the robot.toml file does not support including multiple TOML configuration files unless specified manually via the command line. This can become unwieldy when dealing with large configurations or when modularity is required.
Proposed Enhancement:
I propose adding support for a robot.toml.d directory that RobotCode would automatically scan and merge any TOML files found within this directory with the main robot.toml file. The directory structure could look something like this:
project/
│
├── robot.toml
└── robot.toml.d/
     ├── 01_dev.toml
     ├── 02_prod.toml
     └── 03_browsers.toml

The merging of configurations would follow a specific order:

robot.toml (if present) is read first.
robot.toml.d directory files are read next, in alphanumerical order.

In case of conflicting configurations, the values from the files in the robot.toml.d directory would be overwritten by the values in robot.toml to maintain clear precedence.
Benefits:

Modularity: This approach allows for a modular configuration setup, breaking down complex configurations into smaller, more manageable parts.
Organization: It enhances the organization of configurations, providing a clean and structured way to manage them.
Reusability: Configuration files in robot.toml.d can be reused across different projects or components.
Simplicity: Automatically reading from the robot.toml.d directory removes the need to specify multiple files via command-line arguments.

Implementation Considerations:

Parsing Order: Files should be parsed in the following order:

robot.toml (if present).
Files in the robot.toml.d directory, in alphanumerical order.

Conflict Resolution: In case of conflicts, the values from robot.toml should take precedence over those in the robot.toml.d files.
Error Handling: Meaningful error messages should be provided if files within robot.toml.d are missing or contain invalid syntax.


Fix #6521: Main module function calls shouldn't use project namespace

Pull Request Description
Fixes #6521: Picking a function from the CB that's defined in the main module now resolves to Main.<func-name> instead of <project-name>.<func-name>.
Note that, when collapsing nodes to a function, this referral style was already used, so this is just a change in the behaviour of the CB.
Checklist
Please ensure that the following checklist has been satisfied before submitting the PR:

[x] The documentation has been updated, if necessary.
[ ] Screenshots/screencasts have been attached, if there are any visual changes. For interactive or animated visual changes, a screencast is preferred.
[x] All code follows the Scala, Java, and Rust style guides. In case you are using a language not listed above, follow the Rust style guide.
All code has been tested:

[x] Unit tests have been written where possible.
[x] If GUI codebase was changed, the GUI was tested when built using ./run ide build.

I don't see any changes in required_imports method: please check if we don't add unnecessary import local.Unnamed import when inserting function from Main.

@farmaazon: You were right, it was adding that import. Care to have another look before we move on to QA?


Right-click on table row -> open in a new table

What problem does this feature solve?
Adding (click)="..." or [routerLink]="..."  on a <tr> HTML tag does not allow to "open in a new tab", using the right-click, since only the <a> tag displays this contextual menu.

It would be very useful to wrap the table row in a <a> tag.
I suppose this improvement may be a larger work if extended to other components.
I know this is not compliant with HTML specs, but is it blocking ? 🤔
What does the proposed API look like?
IMHO, detecting the routerLink attribute would be the right way to do it.

Discussed by W3C here:

https://github.com/whatwg/html/issues/6223
https://github.com/whatwg/html/blob/main/FAQ.md#html-should-support-href-on-any-element


[Vue warn]: Avoid app logic that relies on enumerating keys on a component instance. The keys will be empty in production mode to avoid performance overhead.

Version
3.0.0-rc.9
Reproduction link
https://github.com/rothskeller/vuewarnreport
Steps to reproduce

git clone
yarn install
yarn dev
click on links in demo

What is expected?
No warning.
What is actually happening?
[Vue warn]: Avoid app logic that relies on enumerating keys on a component instance. The keys will be empty in production mode to avoid performance overhead.

First, note that this is the same symptom as #1991 but not the same cause.
This is happening because of the call to watch(route, ...) which is made in client/src/pages/ID.vue.  The route object has within it a reference to the component, so watching the route includes watching the component, which triggers the warning.  But watching the route for changes is a typical, and indeed essential, idiom in vue-router which should not result in a console warning.  I don't know whether this should be considered a vue-next bug or a vue-router-next bug, but I'm guessing the former.

watch(route) is implicitly deep: true, which traverses arbitrarily deep properties. So technically, this is expected behavior. Also, deep traversing a complex object when you only care about a few properties is wasteful.
Your use case can and should be rewritten using a computed property instead:
const id = computed(() => {
   return Array.isArray(route.params.id) ? route.params.id[0] : route.params.id
})

@yyx990803 Your response makes sense, but permit me to note that it disagrees with the documentation for view-router-next, which explicitly calls for watching the route object.  I do not know how to reconcile between two core Vue projects.

Can you point me the part of the documentation so I can take a look?

@posva I see two references: here and here.

Thanks!

@yyx990803 How about setting watch(route, () => {}, { deep: false }) instead? Can I avoid deep watch as well?

watch(route) is implicitly deep: true, which traverses arbitrarily deep properties. So technically, this is expected behavior. Also, deep traversing a complex object when you only care about a few properties is wasteful.
Your use case can and should be rewritten using a computed property instead:
const id = computed(() => {
   return Array.isArray(route.params.id) ? route.params.id[0] : route.params.id
})

If you must use a watcher, you should also use watchEffect and avoid deep watches:
watchEffect(() => {
  id.value = Array.isArray(route.params.id) ? route.params.id[0] : route.params.id
})

我在vue3 中试用了 vue2 的watch: { $route(newVal, oldVal) {...}}  也会看到这个报警， 这个怎么解决？

vue3  中，这个是devtools  6.0.0 beta 2打印的，我把devtools关闭，这个waring就消失了

Close vue-devtools and the warning will disappear. This should be the problem with DevTools

vue3 中，这个是devtools 6.0.0 beta 2打印的，我把devtools关闭，这个waring就消失了

请问怎么关闭 vue-devtools （vue3）
我也遇到了同样的警告信息，页面直接卡死无响应

vue3 中，这个是devtools 6.0.0 beta 2打印的，我把devtools关闭，这个waring就消失了

same situation with u, it's OK when I closed devtool.

You can specify watch(route.xx),So you don't have to deep: true,i try it's OK.

vue3 中，这个是devtools 6.0.0 beta 2打印的，我把devtools关闭，这个waring就消失了

请问怎么关闭 vue-devtools （vue3）
我也遇到了同样的警告信息，页面直接卡死无响应

set devtools in “when u click the extension” mode

https://next.router.vuejs.org/guide/advanced/composition-api.html#accessing-the-router-and-current-route-inside-setup
watch(       () => route.params.id,       async newId => {         userData.value = await fetchUser(newId)       }     )

For me it's because of my Axios requests ...Whenever I use an Axios (or even fetch doesn't matter) I get this warning...It doesn't vanish even with disabling devtools (So It has nothing to do with the devtools).
I used interceptors of Axios to handle some error/catch cases but I don't think it has something to do with it because when I comment out those lines it still gives me warning.

Even in the store when I save my current form ( vue component as form) it gives me this...And in the production it removes it so I can't go further

I also had this problem, and I didn't listen to the whole route, but I found that if I used the whole route within the method, it would also output a warning, so I just wrote the warning that I needed to use and it didn't happen.

Even in the store when I save my current form ( vue component as form) it gives me this...And in the production it removes it so I can't go further

I'm encoutering a similar issue when dispatching an action to store AG-Grid's Model in my Vuex store.  Specifically this bit of code store.dispatch('setSelectedShifters', event.api.getModel());  Considering I'm dispatching actions all over the place without issue, I am wondering if this has more to do with something AG Grid is doing?  I have confirmed that the issue goes away when I avoid committing this model, but I don't want to do that.

Are there other known causes of this "Avoid app logic" warning? I am migrating from Vue 2 to 3, and some routes show this warning in the console hundreds, if not thousands of times on one page.

Are there other known causes of this "Avoid app logic" warning? I am migrating from Vue 2 to 3, and some routes show this warning in the console hundreds, if not thousands of times on one page.

Saving a component and triggering HMR also causes this warning to show up multiple times.

It looks like these warnings are coming from the new vue dev tools chrome extension.

This happens to me when destructuring a ref without .value.
It looks like there's something wrong with request, the request is very slow, the page is stuck and can't interact. While the console shows the warnings.

On another note, this error popped up for me today and it was inside an Ionic/Vue3 project. And it was related to using an Ionic component - in my case the IonChip component - without importing it. So its reference in my template without the import was the culprit.

Currently migrating nuxt 2 project to nuxt 3 and I started getting this error as well. What I've noticed is that it doesn't happen because of something specific, but rather because of some other errors happening. For example in my case since we wanted to still use vuex in nuxt 3, I was using mapActions but had the wrong module name passed so this warning started showing infinitely and immediately resulted in crashing & freezing the whole browser
For anyone experiencing this error, I suggest you start commenting code little by little so you find the culprit in your codebase, but unfortunately there's no specific fix as the warning itself doesn't describe what's wrong exactly


neofetch: update old nixos logo

Description of changes
Update old nixos logo.
PR in upstream - https://github.com/dylanaraps/neofetch/pull/2114
Things done

Built on platform(s)

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

[x] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

cc @erikrodrgz @Artturin @rhoriguchi @lilyinstarlight @SuperSandro2000

Should the logos be swapped - nixos_old to nixos?

No?

No?

ok)


0.11.0-beta2: no valid kits generated

Brief Issue Summary
Generated kit file contains no valid entries.
The generated kit file is as follows:
[   {     "name": "undefined - amd64",     "visualStudioArchitecture": "amd64"   },   {     "name": "undefined - amd64_arm",     "visualStudioArchitecture": "amd64_arm"   },   {     "name": "undefined - amd64_x86",     "visualStudioArchitecture": "amd64_x86"   },   {     "name": "undefined - x86",     "visualStudioArchitecture": "x86"   },   {     "name": "undefined - x86_amd64",     "visualStudioArchitecture": "x86_amd64"   },   {     "name": "undefined - x86_arm",     "visualStudioArchitecture": "x86_arm"   } ]
Configuring is not possible since there are no valid kits to choose from.
Expected:

Start vscode without a cmake-kits.json file. It generates a kit file for you
Try to select a kit, dropdown shows 'no entries to pick from'

CMake Tools Log
2017-12-21T10:06:33.577Z [debug] [main] Safe constructing new CMakeTools instance
2017-12-21T10:06:33.578Z [debug] [kit] Constructing KitManager
2017-12-21T10:06:33.579Z [debug] [variant] Constructing VariantManager
2017-12-21T10:06:33.580Z [debug] [main] Constructing new CMakeTools instance
2017-12-21T10:06:33.581Z [debug] [main] Starting CMakeTools second-phase init
2017-12-21T10:06:33.582Z [debug] [rollbar] Checking Rollbar permissions
2017-12-21T10:06:33.582Z [debug] [rollbar] Rollbar enabled?  true
2017-12-21T10:06:33.768Z [info] [variant] Loaded new set of variants
2017-12-21T10:06:33.768Z [debug] [kit] Second phase init for KitManager
2017-12-21T10:06:33.777Z [debug] [kit] Rescanning for Kits
2017-12-21T10:06:33.777Z [debug] [kit] Scanning for Kits on system
2017-12-21T10:06:33.778Z [debug] [kit] Scanning directory C:\Windows\system32 for compilers
2017-12-21T10:06:33.778Z [debug] [kit] Scanning directory C:\Windows for compilers
2017-12-21T10:06:33.778Z [debug] [kit] Scanning directory C:\Windows\System32\Wbem for compilers
2017-12-21T10:06:33.778Z [debug] [kit] Scanning directory C:\Windows\System32\WindowsPowerShell\v1.0\ for compilers
2017-12-21T10:06:33.779Z [debug] [kit] Scanning directory C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common for compilers
2017-12-21T10:06:33.779Z [debug] [kit] Scanning directory C:\Program Files (x86)\Dr. Memory\bin\ for compilers
2017-12-21T10:06:33.779Z [debug] [kit] Scanning directory C:\Program Files\Microsoft VS Code\bin for compilers
2017-12-21T10:06:33.779Z [debug] [kit] Scanning directory C:\Program Files\CMake\bin for compilers
2017-12-21T10:06:33.779Z [debug] [kit] Scanning directory c:/home/bin/ for compilers
2017-12-21T10:06:33.831Z [debug] [kit] Found 0 kits in directory C:\Windows
2017-12-21T10:06:33.871Z [debug] [kit] Found 0 kits in directory C:\Windows\System32\Wbem
2017-12-21T10:06:33.874Z [debug] [kit] Found 0 kits in directory C:\Windows\System32\WindowsPowerShell\v1.0
2017-12-21T10:06:33.875Z [debug] [kit] Found 0 kits in directory C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common
2017-12-21T10:06:33.878Z [debug] [kit] Found 0 kits in directory C:\Program Files (x86)\Dr. Memory\bin
2017-12-21T10:06:33.878Z [debug] [kit] Found 0 kits in directory C:\Program Files\Microsoft VS Code\bin
2017-12-21T10:06:33.879Z [debug] [kit] Found 0 kits in directory C:\Program Files\CMake\bin
2017-12-21T10:06:33.888Z [debug] [kit] Found 0 kits in directory c:/home/bin/
2017-12-21T10:06:34.255Z [debug] [kit] Found 0 kits in directory C:\Windows\system32
2017-12-21T10:06:34.265Z [debug] [kit] Checking for kit: undefined - x86
2017-12-21T10:06:34.265Z [debug] [kit] Checking for kit: undefined - amd64
2017-12-21T10:06:34.265Z [debug] [kit] Checking for kit: undefined - x86_amd64
2017-12-21T10:06:34.265Z [debug] [kit] Checking for kit: undefined - x86_arm
2017-12-21T10:06:34.266Z [debug] [kit] Checking for kit: undefined - amd64_arm
2017-12-21T10:06:34.266Z [debug] [kit] Checking for kit: undefined - amd64_x86
2017-12-21T10:06:34.289Z [info] [proc] Executing command: C:\Users\EROOBO~1.VID\AppData\Local\Temp\vs-cmt-0.2897278735376183.bat
2017-12-21T10:06:34.292Z [info] [proc] Executing command: C:\Users\EROOBO~1.VID\AppData\Local\Temp\vs-cmt-0.9690378926484022.bat
2017-12-21T10:06:34.296Z [info] [proc] Executing command: C:\Users\EROOBO~1.VID\AppData\Local\Temp\vs-cmt-0.34752570544913053.bat
2017-12-21T10:06:34.302Z [info] [proc] Executing command: C:\Users\EROOBO~1.VID\AppData\Local\Temp\vs-cmt-0.7976487994145876.bat
2017-12-21T10:06:34.303Z [info] [proc] Executing command: C:\Users\EROOBO~1.VID\AppData\Local\Temp\vs-cmt-0.6256844029111737.bat
2017-12-21T10:06:34.309Z [info] [proc] Executing command: C:\Users\EROOBO~1.VID\AppData\Local\Temp\vs-cmt-0.1317901545686837.bat
2017-12-21T10:06:37.463Z [info] [kit] Found Kit: undefined - x86
2017-12-21T10:06:37.464Z [info] [kit] Found Kit: undefined - amd64
2017-12-21T10:06:37.464Z [info] [kit] Found Kit: undefined - x86_amd64
2017-12-21T10:06:37.464Z [info] [kit] Found Kit: undefined - x86_arm
2017-12-21T10:06:37.464Z [info] [kit] Found Kit: undefined - amd64_arm
2017-12-21T10:06:37.464Z [info] [kit] Found Kit: undefined - amd64_x86
2017-12-21T10:06:37.464Z [debug] [kit] Saving news kits to C:\Users\eroobol.VIDIGODOMAIN\AppData\Roaming\CMakeTools\cmake-kits.json
2017-12-21T10:06:37.465Z [debug] [kit] C:\Users\eroobol.VIDIGODOMAIN\AppData\Roaming\CMakeTools\cmake-kits.json saved
2017-12-21T10:06:40.819Z [debug] [kit] Opening TextEditor for C:\Users\eroobol.VIDIGODOMAIN\AppData\Roaming\CMakeTools\cmake-kits.json
2017-12-21T10:06:40.819Z [debug] [main] Starting CMake driver
2017-12-21T10:06:40.906Z [debug] [driver] Base _init() of CMakeDriver
2017-12-21T10:06:40.906Z [info] [cms-client] Started new CMake Server instance with PID 11460
2017-12-21T10:06:41.915Z [debug] [cache] Reading CMake cache file c:\code\toolbox\build\CMakeCache.txt
2017-12-21T10:06:41.916Z [debug] [cache] Parsing CMake cache string
2017-12-21T10:06:42.089Z [debug] [driver] Setting new variant , Emit debug information without performing optimizations
2017-12-21T10:06:42.091Z [debug] [main] CMakeTools instance initialization complete.
2017-12-21T10:06:42.091Z [debug] [extension] Registering extension commands
2017-12-21T10:04:19.417Z [debug] [kit] Scanning directory C:\Program Files (x86)\Git\cmd for compilers
2017-12-21T10:04:19.417Z [debug] [kit] Scanning directory ~\bin\mplayer-svn-3756 for compilers
2017-12-21T10:04:19.418Z [debug] [kit] Scanning directory C:\Program Files (x86)\Graphviz2.38\bin for compilers
2017-12-21T10:04:19.418Z [debug] [kit] Scanning directory C:\Program Files (x86)\Dr. Memory\bin64\ for compilers
2017-12-21T10:04:19.426Z [warning] [kit] Failed to scan C:\Program Files\Git\usr\local\bin by exception: Error: ENOENT: no such file or directory, stat 'C:\Program Files\Git\usr\local\bin'
2017-12-21T10:04:19.426Z [warning] [kit] Failed to scan C:\Program Files\Git\opt\bin by exception: Error: ENOENT: no such file or directory, stat 'C:\Program Files\Git\opt\bin'
2017-12-21T10:04:19.427Z [warning] [kit] Failed to scan C:\Program Files\ConEmu\ConEmu\Scripts by exception: Error: ENOENT: no such file or directory, stat 'C:\Program Files\ConEmu\ConEmu\Scripts'
2017-12-21T10:04:19.428Z [warning] [kit] Failed to scan C:\Program Files (x86)\LLVM\bin by exception: Error: ENOENT: no such file or directory, stat 'C:\Program Files (x86)\LLVM\bin'
2017-12-21T10:04:19.429Z [warning] [kit] Failed to scan ~\bin by exception: Error: ENOENT: no such file or directory, stat 'C:\Program Files\Microsoft VS Code~\bin'
2017-12-21T10:04:19.429Z [warning] [kit] Failed to scan ~\bin\nc by exception: Error: ENOENT: no such file or directory, stat 'C:\Program Files\Microsoft VS Code~\bin\nc'
2017-12-21T10:04:19.430Z [warning] [kit] Failed to scan C:\Program Files (x86)\Git\bin by exception: Error: ENOENT: no such file or directory, stat 'C:\Program Files (x86)\Git\bin'
2017-12-21T10:04:19.430Z [warning] [kit] Failed to scan C:\Program Files (x86)\Git\cmd by exception: Error: ENOENT: no such file or directory, stat 'C:\Program Files (x86)\Git\cmd'
2017-12-21T10:04:19.430Z [warning] [kit] Failed to scan ~\bin\mplayer-svn-3756 by exception: Error: ENOENT: no such file or directory, stat 'C:\Program Files\Microsoft VS Code~\bin\mplayer-svn-3756'
2017-12-21T10:04:19.471Z [debug] [kit] Found 0 kits in directory C:\home\bin
2017-12-21T10:04:19.529Z [debug] [kit] Found 0 kits in directory C:\Program Files\Git\usr\bin
2017-12-21T10:04:19.577Z [debug] [kit] Found 0 kits in directory C:\Program Files\Git\usr\bin
2017-12-21T10:04:19.583Z [debug] [kit] Found 0 kits in directory C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\CommonExtensions\Microsoft\TestWindow
2017-12-21T10:04:19.594Z [debug] [kit] Found 0 kits in directory C:\Program Files (x86)\MSBuild\14.0\bin
2017-12-21T10:04:19.599Z [debug] [kit] Found 0 kits in directory C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\BIN
2017-12-21T10:04:19.602Z [debug] [kit] Found 0 kits in directory C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\Tools
2017-12-21T10:04:19.632Z [debug] [kit] Found 0 kits in directory C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE
2017-12-21T10:04:19.637Z [debug] [kit] Found 0 kits in directory C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\VCPackages
2017-12-21T10:04:19.638Z [debug] [kit] Found 0 kits in directory C:\Program Files (x86)\HTML Help Workshop
2017-12-21T10:04:19.645Z [debug] [kit] Found 0 kits in directory C:\Program Files (x86)\Microsoft Visual Studio 14.0\Team Tools\Performance Tools
2017-12-21T10:04:19.688Z [debug] [kit] Found 0 kits in directory C:\Windows\Microsoft.NET\Framework\v4.0.30319
2017-12-21T10:04:19.707Z [debug] [kit] Found 0 kits in directory C:\Program Files (x86)\Windows Kits\8.1\bin\x86
2017-12-21T10:04:19.713Z [debug] [kit] Found 0 kits in directory C:\Program Files (x86)\Microsoft SDKs\Windows\v10.0A\bin\NETFX 4.6.1 Tools
2017-12-21T10:04:19.714Z [debug] [kit] Found 0 kits in directory C:\Program Files\ConEmu
2017-12-21T10:04:19.719Z [debug] [kit] Found 0 kits in directory C:\Program Files\ConEmu\ConEmu
2017-12-21T10:04:19.722Z [debug] [kit] Found 0 kits in directory C:\Windows\System32\WindowsPowerShell\v1.0
2017-12-21T10:04:19.754Z [debug] [kit] Found 0 kits in directory C:\Windows\System32\Wbem
2017-12-21T10:04:19.755Z [debug] [kit] Found 0 kits in directory C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common
2017-12-21T10:04:19.758Z [debug] [kit] Found 0 kits in directory C:\Program Files (x86)\Dr. Memory\bin
2017-12-21T10:04:19.758Z [debug] [kit] Found 0 kits in directory C:\Program Files\Microsoft VS Code\bin
2017-12-21T10:04:19.770Z [debug] [kit] Found 0 kits in directory C:\Windows
2017-12-21T10:04:19.770Z [debug] [kit] Found 0 kits in directory C:\Program Files\CMake\bin
2017-12-21T10:04:19.781Z [debug] [kit] Found 0 kits in directory C:\home\bin
2017-12-21T10:04:19.782Z [debug] [kit] Found 0 kits in directory C:\Program Files\Git\usr\bin\vendor_perl
2017-12-21T10:04:19.786Z [debug] [kit] Found 0 kits in directory C:\Program Files\Git\usr\bin\core_perl
2017-12-21T10:04:19.786Z [debug] [kit] Found 0 kits in directory C:\Program Files\Git\bin
2017-12-21T10:04:19.796Z [debug] [kit] Found 0 kits in directory C:\Program Files\Git\mingw64\bin
2017-12-21T10:04:19.800Z [debug] [kit] Found 0 kits in directory C:\code\scripts
2017-12-21T10:04:20.154Z [debug] [kit] Found 0 kits in directory C:\Windows\system32
2017-12-21T10:04:20.155Z [debug] [kit] Found 0 kits in directory C:\Program Files\CMake\bin
2017-12-21T10:04:20.161Z [debug] [kit] Found 0 kits in directory C:\Program Files (x86)\Meld
2017-12-21T10:04:20.163Z [debug] [kit] Found 0 kits in directory C:\Program Files\Python36
2017-12-21T10:04:20.173Z [debug] [kit] Found 0 kits in directory C:\Program Files (x86)\Graphviz2.38\bin
2017-12-21T10:04:20.185Z [debug] [kit] Found 0 kits in directory C:\Program Files (x86)\Graphviz2.38\bin
2017-12-21T10:04:20.188Z [debug] [kit] Found 0 kits in directory C:\Program Files (x86)\Dr. Memory\bin64
2017-12-21T10:04:20.204Z [debug] [kit] Checking for kit: undefined - x86
2017-12-21T10:04:20.204Z [debug] [kit] Checking for kit: undefined - amd64
2017-12-21T10:04:20.205Z [debug] [kit] Checking for kit: undefined - x86_amd64
2017-12-21T10:04:20.205Z [debug] [kit] Checking for kit: undefined - x86_arm
2017-12-21T10:04:20.205Z [debug] [kit] Checking for kit: undefined - amd64_arm
2017-12-21T10:04:20.205Z [debug] [kit] Checking for kit: undefined - amd64_x86
2017-12-21T10:04:20.228Z [info] [proc] Executing command: C:\Users\EROOBO~1.VID\AppData\Local\Temp\vs-cmt-0.8427523251250579.bat
2017-12-21T10:04:20.233Z [info] [proc] Executing command: C:\Users\EROOBO~1.VID\AppData\Local\Temp\vs-cmt-0.9603460403360748.bat
2017-12-21T10:04:20.238Z [info] [proc] Executing command: C:\Users\EROOBO~1.VID\AppData\Local\Temp\vs-cmt-0.29162860787214817.bat
2017-12-21T10:04:20.242Z [info] [proc] Executing command: C:\Users\EROOBO~1.VID\AppData\Local\Temp\vs-cmt-0.25751402930748335.bat
2017-12-21T10:04:20.249Z [info] [proc] Executing command: C:\Users\EROOBO~1.VID\AppData\Local\Temp\vs-cmt-0.4098307817193694.bat
2017-12-21T10:04:20.262Z [info] [proc] Executing command: C:\Users\EROOBO~1.VID\AppData\Local\Temp\vs-cmt-0.46238734752837374.bat
2017-12-21T10:04:23.473Z [info] [kit] Found Kit: undefined - x86
2017-12-21T10:04:23.474Z [info] [kit] Found Kit: undefined - amd64
2017-12-21T10:04:23.474Z [info] [kit] Found Kit: undefined - x86_amd64
2017-12-21T10:04:23.474Z [info] [kit] Found Kit: undefined - x86_arm
2017-12-21T10:04:23.474Z [info] [kit] Found Kit: undefined - amd64_arm
2017-12-21T10:04:23.474Z [info] [kit] Found Kit: undefined - amd64_x86
2017-12-21T10:04:23.475Z [debug] [kit] Saving news kits to C:\Users\eroobol.VIDIGODOMAIN\AppData\Roaming\CMakeTools\cmake-kits.json
2017-12-21T10:04:23.477Z [debug] [kit] C:\Users\eroobol.VIDIGODOMAIN\AppData\Roaming\CMakeTools\cmake-kits.json saved
2017-12-21T10:04:28.890Z [debug] [kit] Opening TextEditor for C:\Users\eroobol.VIDIGODOMAIN\AppData\Roaming\CMakeTools\cmake-kits.json
2017-12-21T10:04:28.891Z [debug] [main] Starting CMake driver
2017-12-21T10:04:28.984Z [debug] [driver] Base _init() of CMakeDriver
2017-12-21T10:04:28.988Z [info] [cms-client] Started new CMake Server instance with PID 18236
2017-12-21T10:04:29.989Z [debug] [cache] Reading CMake cache file c:\code\toolbox\build\CMakeCache.txt
2017-12-21T10:04:29.990Z [debug] [cache] Parsing CMake cache string
2017-12-21T10:04:30.154Z [debug] [driver] Setting new variant , Emit debug information without performing optimizations
2017-12-21T10:04:30.155Z [debug] [main] CMakeTools instance initialization complete.
2017-12-21T10:04:30.155Z [debug] [extension] Registering extension commands
2017-12-21T10:04:30.359Z [debug] [extension] [1038] cmake.setVariant started
2017-12-21T10:04:32.182Z [debug] [main] Active build variant changed
2017-12-21T10:04:32.183Z [debug] [driver] Setting new variant , Emit debug information without performing optimizations
2017-12-21T10:04:32.183Z [debug] [main] No kit selected yet. Asking for a Kit first.
2017-12-21T10:04:32.183Z [debug] [kit] Opening kit selection QuickPick
2017-12-21T10:04:33.262Z [debug] [kit] User cancelled Kit selection
2017-12-21T10:04:33.262Z [debug] [main] No kit selected. Abort configure.
2017-12-21T10:04:33.262Z [debug] [extension] [1038] cmake.setVariant finished
2017-12-21T10:06:29.393Z [debug] [extension] Deactivate CMakeTools
2017-12-21T10:06:29.393Z [debug] [kit] Disposing KitManager
2017-12-21T10:06:29.393Z [debug] [main] Disposing CMakeTools extension
2017-12-21T10:06:29.394Z [debug] [kit] Disposing KitManager
Platform and Versions

Operating System: Windows 7
CMake Version: 3.10.0
VSCode Version: 1.19.1
CMake Tools Extension Version: 0.11.0-beta2
Compiler/Toolchain: Visual C++ 2015

@vector-of-bool I think the problem is that vs2015 has no VsDevCmd.bat only a VSVARS32.BAT.
https://docs.microsoft.com/en-us/dotnet/csharp/language-reference/compiler-options/how-to-set-environment-variables-for-the-visual-studio-command-line

What output do you see from running vswhere? Use the one bundled with the extension, or the latest build from their github releases.

For me, vswhere doesn't seem to output much of anything. Only the version of vswhere.

Can you try this
vswhere -all -format json -products * -legacy -prerelease

Error 0x57: The "legacy" parameter cannot be specified with either the "products" or "requires" parameter

Did you try running the vswhere that comes bundled with the extension? I don't remember exactly where the files go on WIndows, but you should be able to find them and run the vswhere.exe that's in the res directory for the extension.

I have a similar problem, though the reasons are most likely totally different.
Kit detection works now that #283 is solved, but the kit file generated is invalid.
[kit] Second phase init for KitManager
[kit] Re-read kits file from prior session
[kit] Re-reading kits file C:\Users\nagy-\AppData\Roaming\CMakeTools\cmake-kits.json
[kit] Invalid cmake-kits.json:
[kit]  >> [1]: should have required property 'compilers'
[kit]  >> [1]: should have required property 'toolchainFile'
[kit]  >> [1]: should have required property 'visualStudioVersion'
[kit]  >> [1]: should match exactly one schema in oneOf
[kit]  >> [2]: should have required property 'compilers'
[kit]  >> [2]: should have required property 'toolchainFile'
[kit]  >> [2]: should have required property 'visualStudioVersion'
[kit]  >> [2]: should match exactly one schema in oneOf
[kit] Successfully loaded 0 kits
[kit] Active kit set to null
[main] Starting CMake driver

The Kit file generated looks like this:
PS C:\Users\nagy-> gc C:\Users\nagy-\AppData\Roaming\CMakeTools\cmake-kits.json
[
  {
    "name": "Clang 5.0.0",
    "compilers": {
      "C": "C:\\Kellekek\\LLVM\\5.0\\bin\\clang.exe",
      "CXX": "C:\\Kellekek\\LLVM\\5.0\\bin\\clang++.exe"
    }
  },
  {
    "name": "Visual Studio Build Tools 2017 - amd64",
    "visualStudio": "Visual Studio Build Tools 2017",
    "visualStudioArchitecture": "amd64",
    "preferredGenerator": {
      "name": "Visual Studio 15 2017",
      "platform": "x64"
    }
  },
  {
    "name": "Visual Studio Build Tools 2017 - x86",
    "visualStudio": "Visual Studio Build Tools 2017",
    "visualStudioArchitecture": "x86",
    "preferredGenerator": {
      "name": "Visual Studio 15 2017"
    }
  }
]

When I invoke vswhere.exe manually, the one that ships with VS, found under C:\Program Files (x86)\Microsoft Visual Studio\Installer\vswhere.exe, or to be more precise, the one that ships with the Build Tools Only installer of MSVC, it does not find the compiler.
PS C:\Users\nagy-> & 'C:\Program Files (x86)\Microsoft Visual Studio\Installer\vswhere.exe' -format json -all
[]

I did not find vswhere that comes with the extension (search Code install dir, AppData and all of Program Files, but nothing.

@MathiasMagnus, looking at your kits, I can see the problem, and it's a silly mistake: The JSON schema for the kits file wants visualStudioVersion, but the code uses visualStudio, which is why it won't validate. You can test a fix just by opening up the kits-schema.json in the installed extension and fixing the property name.

@MathiasMagnus, also, you need more arguments to vswhere to tell it to find the build tools. -products * should get it.

For me, altering the property in the scheme to visualStudio and then manually entering kits works. The generated kits are still the same (as of beta3). I used the latest vswhere binary from github.

I believe I've got it all worked out. VS kits should now work properly in beta4! @eldadroobol, give it a try and close this issue if it seems fixed to your satisfaction.


When a drag is aborted, the source list plays a "re-attaching" animation, despite animation: 0 and pull: clone

The top list has animation: 0, sort: false and pull: clone, the bottom list has animation: 150.
When I "abort" the drag, the dragged item of source list on the top moves around, despite disabling animations:

Here is a JSBin link with example code: https://jsbin.com/wugogigizo/edit?html,js,output
I can fix the unwanted animation of the top list by setting animation: 0 on the bottom list, but I believe this is not working as intended.
There is simply no point in playing the "re-attaching" animation when pull: clone is set:
nothing was removed from the list, so nothing needs to be re-attached.
Please let me know if I can provide further information!

It is using the animation value of the list it is coming from. But this should be fixed in the future.

Any updates on this? The issue still exists in v.1.15.2


feat(sqllab): Add timeout on fetching query results

SUMMARY
This commit adds the timeout on fetching query results.
Additionally, a 'Retry without timeout' option is provided so that when a timeout issue occurs, users can attempt to proceed by ignoring the error.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
https://github.com/user-attachments/assets/af5dfc12-4072-484a-94d8-57b3258b3163
TESTING INSTRUCTIONS
SET SQLLAB_QUERY_RESULT_TIMEOUT with a small timeout
Run a query async
Check the error message and then click "Retry" to get the result without timeout errors
ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Required feature flags:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

@justinpark we currently have
# Timeout duration for SQL Lab synchronous queries
SQLLAB_TIMEOUT = int(timedelta(seconds=30).total_seconds())

# The MAX duration a query can run for before being killed by celery.
SQLLAB_ASYNC_TIME_LIMIT_SEC = int(timedelta(hours=6).total_seconds())

Can't we reuse one of these for this? I'm thinking that we could expand the scope of SQLLAB_TIMEOUT (changing the comment) to be valid for both sync and async queries.

Another question is about retry without time limit. Isn't this dangerous and probably inaccurate? I'm assuming all database engines will impose timeouts and this setting will not bypass this? I'm also assuming that a timeout was set for a reason, so giving users the ability to override this seems dangerous. If you're thinking only hanging frontend requests, wouldn't https://github.com/apache/superset/pull/29956 be sufficient to handle these cases?

Can't we reuse one of these for this? I'm thinking that we could expand the scope of SQLLAB_TIMEOUT (changing the comment) to be valid for both sync and async queries.

@michael-s-molina QUERY_RESULT_TIMEOUT is different from the existing SQLLAB_TIMEOUT and SQLLAB_ASYNC_TIME_LIMIT_SEC. This refers to a request that occurs in an ASYNC QUERY, which is different from the actual query execution time. It is a request to retrieve the completed query result from the cache. In formula form, it can be expressed as follows:
SQLLAB_TIMEOUT = SQLLAB_ASYNC_TIME_LIMIT_SEC + SQLLAB_QUERY_RESULT_TIMEOUT

The reason for delays related to the timeout is due to locking caused by updates to the query table, which leads to delays in querying the information linked to the resultsKey of the query ID. To address this issue, a separate timeout is configured.

Another question is about retry without time limit. Isn't this dangerous and probably inaccurate? I'm assuming all database engines will impose timeouts and this setting will not bypass this? I'm also assuming that a timeout was set for a reason, so giving users the ability to override this seems dangerous. If you're thinking about zombie frontend requests, wouldn't https://github.com/apache/superset/pull/29956 be sufficient to handle these cases?

The locking delay in synchronizing query status was resolved with PR 29956. This patch also addresses the intermittent issue of the fetching state freezing (when the timer stops and results are retrieved) that occasionally occurred after the query status was confirmed as successful.
Making a request without a timeout applies the max request time related on the HTTP server, which is the same as the existing result retrieval process. The new addition is simply an update to the UX, where pending states are cut off slightly earlier than the HTTP server’s max request timeout. If a request requires more time than the configured timeout, users can re-initiate the request using the original method, depending on their preference.

/testenv up

Updated the button label to "Retry fetching results" which will run as-is (which means no overrides of timeout)

@sadpandajoe Could you add this fix on 4.1?


User osusergo build tag for static builds

skip go-fmt
skip unit-tests
skip compile-tests
skip functional-tests-backend-elasticsearch
skip functional-tests-backend-orientdb
skip scale-tests
skip cdd-overview-tests
skip k8s-tests

run skydive-create-binaries


metadata updates

When you bump the vault version in the attributes, is it at all possible to bump the last number in your cookbook version in your metadata?
This is extremely important for berks and version locking.

Yes, we do bump the cookbook version (major/minor/patch) before the cookbook is released to supermarket. You can see the latest release [1.5.0] (https://github.com/johnbellone/vault-cookbook/releases/tag/v1.5.0) bumped up the minor version.

@blairham Are you deploying directly from this repository?

Alright, I agree that we should be bumping the release of the cookbook each time that its updated inside of the attributes. That is generally the case. But there are times you're going to hit a lag time between the actual tag/release. The best way to do this would be to get your releases from the Chef Supermarket.


Dropdown arrows do not work

On master-head - commit id: 2ae933e08

Deploy rancher backup
Choose option "Use an existing storage class"
Click on the dropdown arrow
Dropdown arrow does not work

Select option "Use an existing persistent volume.
Click on the dropdown arrow
Dropdown arrow does not work

On master-head - commit id: 1b0778b1

Dropdown on persistent volume works
But dropdown on Existing storage classes does not work when clicked on. Reopening the issue

On master-head - commit id: `1b0778b1
Dropdown on persistent volume and existing storage class work