wireshark is not usable

NixOS does not implement any of the methods described here to run wireshark in any sane way http://wiki.wireshark.org/CaptureSetup/CapturePrivileges.
Running it as root results in a bunch of warnings, and man configuration.nix does not document any options for wireshark (which has been done for other operating systems (like Debian, etc.)).
For an operating system which is keen on its configuration management capabilities, it's working much, much worse than an imperatively managed ancient system like Debian.
What is the rationale for including such badly packaged systems in NixOS (especially in the "stable" distribution)? If you absolutely want to include such broken code, can you at least mark the stuff you do not think is broken in some way, to give people the option to avoid it?
Why don't you have rules which simply say "if it doesn't easily work, we do not include it."? There are many more programs in NixOS for which this currently holds. It seems like the only consideration is "if it compiles, ship it.".

Why don't you have rules which simply say "if it doesn't easily work, we do not include it."? There are many more programs in NixOS for which this currently holds. It seems like the only consideration is "if it compiles, ship it.".

Because Wireshark is useful to some NixOS users who capture with tcpdump
and use Wireshark to browse the capture comfortably. I, for one, do just
that (I browse captures from servers often enough to consider browsing
tcpdump captures the natural way of using Wireshark).

I also use wireshark, and I simply run it as root. It's not ideal, but it doesn't bother me enough to sit down and figure out an advanced setup. If you, @wwat, know of superior ways to run wireshark without requiring super user privileges, then we why don't you make a concrete suggestions and/or submit a PR that improves the situation?

Add security.setuidPrograms = [ dumpcap ];. If you want to limit access to certain user/group, use security.setuidOwners.

I also just use wireshark as analysis program. Capturing is better left to netsniff-ng or tcpdump

Installing dumpcap setuid is one of the options listed in http://wiki.wireshark.org/CaptureSetup/CapturePrivileges. So this issue is invalid. (See my comment above.)
One could argue that there should be a specific programs.wireshark.enableSetuidDumpcap option though. But if you want more control over who gets access to this dumpcap, you have to use security.setuidOwners anyway.

@bjornfor  No, there should be a list of users configurable in wireshark's configuration, that is a wireshark service module in NixOS parlance. Then that would merge with security.setuidOwners. Then the security mechanism is hidden as an implementation detail.

I can somewhat agree to that. (I don't have strong opinions.)
Btw, this issue is still invalid. "wireshark is not useable" is simply false. What you are (now) arguing about is that you don't like the existing config options (setuidPrograms, setuidOwners). You want a programs.wireshark.<something> option.

@bjornfor I don't care one bit about whether a particular subset of features is available in a well considered way. There is only one decent design put forward (the one I outlined) and that has not been implemented. Anyone who has any experience in properly packaging something for NixOS should have done that, and not do some half-assed job (which is what it is now).
Just because there are also people who use workarounds (the vast majority who responds here), doesn't mean that e.g. a Debian or Redhat user would not laugh you out of the room, because again, the wireshark 'feature' is just broken.

In general, the only right response to what I said is "Yes, that would be better", but defending the current state is irrational at best.
Really, why is anyone defending the undocumented method for configuring wireshark in NixOS here? What do you imagine is going to happen when a random new security mechanism is introduced in Linux? Do you expect all the people who "just want to run wireshark as user X (with additional rights)" to keep track of such details? Why?! That only annoys users and lack of stability scares away a huge class of users who actually have the funds to make NixOS a success. If the goal is to annoy users, then please state that on the NixOS website, if not, stop arguing, and just say "yes, this is a good idea.".
Quoting from the website:
NixOS is a Linux distribution with a unique approach to package and configuration management. Built on top of the Nix package manager, it is completely declarative, makes upgrading systems reliable, and has many other advantages.
I think this is a complete lie (see my theoretical example about wireshark (for which I am sure practical examples can also be found), lack of backwards compatibility, and other misfeatures). NixOS might have as a goal to become "better", but back in the real world, when real engineers need to do something in a limited time, it's not actually 'better', because it is not documented. If it's not documented, it_does_not_exist. An interface which can disappear tomorrow again, is not worth our time.
NixOS, as an operating system community, has almost no tools (compare with the Debian community or the many, many tools which Red Hat has internally), which means there is no timely updates of security issues, or new releases; it all depends on some human to take the time to do an upload (in other words, a completely flawed approach, which doesn't scale).
One simple program (less than 1,000 lines) can be used to build almost arbitrary programs with the most broken build systems, but yet for NixOS the simplest of automation procedures "genericBuild" is being used. Additionally, a complete ingestion procedure is missing where global release directories from major repositories are being tracked to automatically package them for NixOS use (including digital signatures, etc.). This gives the feeling of a system which is dependent on a small self-selected(?) bunch of people in order to create the next release, which in turn increases risk. As long as that risk is there, that is, it is not possible to push a button and deploy a complete NixOS project infrastructure in-house, there is a lot of reason to doubt the intentions of the people in the NixOS project. What exactly are we here for then? Free testing? I don't think so.
Similarly, why does someone have to manually partition a system in order to install NixOS? That's just begging people to not use NixOS.
Let me restate it again; There is absolutely no point in manually packaging software.  There should be a ton of automated commits happening in a project like NixOS, but what appears to be happening is that there are some users who have their own scripts to maintain parts of the system in a semi-distributed, unprofessional matter.  And to be clear, if you are going to play the 'volunteer card', please understand that in the real world there are minimum requirements for volunteers.
/end of rant

@wwat, please consider your tone.
RedHat and Debian have both been around for over 21 years. RedHat has the backing of a billion dollar corporation with 6,500 employees. Debian has over 1000 active developers.
By comparison nixpkgs+nixos combined have had very few (<20) contributors until just recently. Just look at these graphs: https://www.openhub.net/p/nixos . Additionally, NixOS is an attempt to do things differently, which takes additional development effort. Debian and RedHat need merely to maintain the status quo.
With such a tiny team the developers have naturally had to prioritize. Besides, they are volunteers, many of them working in their spare time. They have given all this to you, free. And yet despite their practically heroic effort in creating an absolutely amazing distro you have the gall to be upset over some comparatively minor deficiency in the 500k lines of code they have written. Do you think they contribute their time for free because they want to be scolded by GitHub ignoramuses all day?
Also, you're completely wrong on most your points, and entirely ignorant on the others.

In general, the only right response to what I said is "Yes, that would be better", but defending the current state is irrational at best.

I haven't seen anyone defend the current state of things.

has almost no tools (compare with the Debian community or the many, many tools which Red Hat has internally), which means there is no timely updates of security issues, or new releases; it all depends on some human to take the time to do an upload

We do have a tool for this, but it's not fully automated and I can guarantee you Debian's isn't either. That would be a recipe for bugs.

There should be a ton of automated commits happening in a project like NixOS

There are. Many thousands of packages were automated this way.

@bjornfor I don't care one bit about whether a particular subset of features is available in a well considered way. There is only one decent design put forward (the one I outlined) and that has not been implemented. Anyone who has any experience in properly packaging something for NixOS should have done that, and not do some half-assed job (which is what it is now).
At some point you started wondering why Wireshark is not removed.

It is not removed because NixPkgs part is packaged as it should, and
noone cared about NixOS part, which may be unfortunate but is
a separate concern.

In general, the only right response to what I said is "Yes, that would be better", but defending the current state is irrational at best.
Really, why is anyone defending the undocumented method for configuring wireshark in NixOS here? What do you imagine is going to happen when a random new security mechanism is introduced in Linux? Do you expect all the people who "just want to run wireshark as user X (with additional rights)" to keep track of such details? Why?! That only annoys users and lack of stability scares away a huge class of users who actually have the funds to make NixOS a success. If the goal is to annoy users, then please state that on the NixOS website, if not, stop arguing, and just say "yes, this is a good idea.".

Apparently you are talking to a number of people who are constantly
annoyed by friendly low-level hiding features. I am among them.
I want to know what are the low-level requirements behind the packages
I use and I want to know how to implement low-level requirements that
I already know. If a person has a problem and asks, I prefer to give
that information because it would be helpful to a person like me who
will be likely to provide some interesting (to me) information later.

Quoting from the website:
NixOS is a Linux distribution with a unique approach to package and configuration management. Built on top of the Nix package manager, it is completely declarative, makes upgrading systems reliable, and has many other advantages.
I think this is a complete lie (see my theoretical example about wireshark (for which I am sure practical examples can also be found), lack of backwards compatibility, and other misfeatures). NixOS might have as a goal to become "better", but back in the real world, when real engineers need to do something in a limited time, it's not actually 'better', because it is not documented. If it's not documented, it_does_not_exist. An interface which can disappear tomorrow again, is not worth our time.

NixOS project is a 90% solution for people who were using their own 80%
solutions anyway to pool their efforts.
It actually does remove some problems that have bitten the real people
working on NixPkgs. Maybe these are non-problems for you.

Similarly, why does someone have to manually partition a system in order to install NixOS? That's just begging people to not use NixOS.

I manually partition disks even when I install Fedora because it ships
sane tools and a fragile UI around them. I would say we lack resources
to provide meaningful support to people who find partitioning disks an
action requiring an effort. You noticed the same fact, actually. But
there are people for whom this is not a problem, some of them find Nix
package manager and NixPkgs useful.

Let me restate it again; There is absolutely no point in manually packaging software.  There should be a ton of automated commits happening in a project like NixOS, but what appears to be happening is that there are some users who have their own scripts to maintain parts of the system in a semi-distributed, unprofessional matter.  And to be clear, if you are going to play the 'volunteer card', please understand that in the real world there are minimum requirements for volunteers.

In the real work there are communities of people who use each other's
work. The minimum requirement for community members is to find each
other's work useful and not split because of interpersonal tensions.

To note, after looking over all @wwat comment I can pretty much say @wwat is a troll, likely just @aragnon again.

The issue was about having a more properly managed wireshark installation. That has not been resolved, obviously. Just the fact that some people like to annoy other people (@goodwillcoding) in this case, doesn't change that.

@wwat: The issue of having more user friendly NixOS API for wireshark is a different topic, and you may of course open an issue about that. (Maybe by using ACLs, we can get something quite nice under programs.wireshark.*, that allows specifying access for single users, as well as (multiple) groups.)
But this issue is is titled "wireshark is not usable", and claims that
NixOS does not implement any of the methods described here to run wireshark
in any sane way http://wiki.wireshark.org/CaptureSetup/CapturePrivileges.

which is incorrect. As explained in comment above (https://github.com/NixOS/nixpkgs/issues/6235#issuecomment-73471886).

@bjornfor Fair enough. https://github.com/NixOS/nixpkgs/issues/6716


The compatible version of go should have mentioned in "Readme.md"

To avoid the issues of compilation errors , like these https://github.com/open-component-model/ocm-controller/issues/135.
the compatible version of go  should have mentioned in Readme.md file .

It's in the go.mod file. That's the source of truth for compatible go versions.


Clicking LM Logo while signed in redirects to home dashboard /dashboard

I moved the process for clearing and populating local storage into the componentDidMount of the HomeDashboard. Please verify localstorage is working correctly no matter if LM or Home is clicked in the Navbar. Thanks

Commit fc62595 fixes the problem I created in the commit a639257. Going to start adding in the Navbar stuff now.


Release v0.9

Description:
Cherry-picks 6664c75e and 9c7a2d9f for v0.9.1,
required to address #3582 with v0.9.

Affected area:

Functional Area

Other
[X]

Please answer the following questions with yes/no.

Does this change contain code from or inspired by another project? no

Did you notify the maintainers and provide attribution?

Is this a breaking change? no

Codecov Report

Merging #3623 (ef10fe2) into release-v0.9 (96498ba) will increase coverage by 0.74%.
The diff coverage is 86.04%.

@@               Coverage Diff                @@
##           release-v0.9    #3623      +/-   ##
================================================
+ Coverage         65.82%   66.57%   +0.74%
================================================
  Files               169      169
  Lines              7886     7904      +18
================================================
+ Hits               5191     5262      +71
+ Misses             2664     2611      -53
  Partials             31       31

Flag
Coverage Δ

unittests
66.57% <86.04%> (+0.74%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/configurator/mock_client_generated.go
0.00% <0.00%> (ø)

cmd/cli/namespace_ignore.go
40.62% <100.00%> (ø)

cmd/cli/namespace_list.go
57.44% <100.00%> (ø)

pkg/configurator/methods.go
69.01% <100.00%> (+0.44%)
:arrow_up:

pkg/ingress/client.go
77.08% <100.00%> (+67.30%)
:arrow_up:

pkg/injector/init_container.go
100.00% <100.00%> (ø)

pkg/injector/iptables.go
100.00% <100.00%> (ø)

pkg/injector/patch.go
77.19% <100.00%> (+0.40%)
:arrow_up:

pkg/injector/webhook.go
79.05% <100.00%> (ø)

pkg/ticker/ticker.go
68.00% <0.00%> (-2.67%)
:arrow_down:

... and 1 more

Continue to review full report at Codecov.

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


re-investigate dual-port RAMs with dual-write and dual-read

I had a stash to look into dual-port RAMs for the stack and main RAM, using custom RAM definitions that translated to raw VHDL in pipelineC (ram.h).  These RAMs would allow for 16-bit reads and writes, where both ports could be read or write at the same time if needed.
I had some trouble with simulation under GHDL when using these ram.h declarations though.  perhaps there is a way around it?
More info:
https://github.com/JulianKemmerer/PipelineC/wiki/Automatically-Generated-Functionality#rams

dev-2port-stack branch adds dual-port RAM for the stack without the GHDL simulation issues, but it increases build times by around 2x.
I'll keep this branch caught up with dev. perhaps future releases can come from this branch, while normal development would continue on dev, for faster iteration.

Dual-Port Stack RAM is released in 0.0.4 of openfpga-varvara.  I'm going to close this issue for now


Source of images

Hi! Thank you for the dataset, it is very useful. Can I check where are the images sourced from? I can't find that info in your paper.

Hi sorry for the late reply. We gathered those images from the internet. Unfortunately we have lost the track of the source urls for those images.


Supernova CompressedSNARK

We should add a benchmark for this.

Given we have the chance to define our own traits for RelaxedR1CSSNARK, I think we should take the opportunity to make the API adhere to C-CALLER-CONTROL.
In particular, the prove function has to make copies of its inputs, which should instead be cloned by the caller:
RelaxedR1CSSNARKTrait<G>::prove(
        ck: &CommitmentKey<G>,
        pk: &Self::ProverKey,
        S: Vec<R1CSShape<G>>,
        U: Vec<RelaxedR1CSInstance<G>>,
        W: Vec<RelaxedR1CSWitness<G>>,
    )

Moreover, we should think about whether we want to implement RelaxedR1CSSNARK in terms of BatchedRelaxedR1CSSNARK.

Closing in favor of #131


Where is the combined template for cutting?

There are svg files for the spparate layers and a png named preview.png of all the layers ready to cut but no svg.

The combined template is in sandwich-split.eps, as I normally use Adobe Illustrator to edit, and its SVG export abilities sometimes has issues. Ponoko prefers EPS files over SVG when Illustrator is used, as it preserves size info better. Anyhow, I've added sandwich-split.svg to the repo.


Fix a problem and add some test cases for podman run security-opt flag

Fix a problem for selinux check command and add 5 test cases for security-opt flag.

I like it, fix the two issues that @TomSweeneyRedHat Points out and we can add this.

Hi @rhatdan
Update the test case based on the comments from @TomSweeneyRedHat . But seems it failed in the CI env. It works in my test machine which is f28 and rhel7. Will try to find similar env as CI and try them again.

Tests seem green aside from known flakes on cloud podman.

One small thing, otherwise LGTM

@ypu Remove the SELinux checks on the seccomp and then we will merge.

@ypu Rebase also, so tests will run on f28

@rh-atomic-bot r+


Multiple File Upload, no array

Hi,
using your multiple file upload example: http://jsfiddle.net/danialfarid/huhjo9jm/5/
The Request Payload looks like this:
------WebKitFormBoundary4Lc5A5Z4vExW8bNj
Content-Disposition: form-data; name="files[0]"; filename="1.png"
Content-Type: image/png

------WebKitFormBoundary4Lc5A5Z4vExW8bNj
Content-Disposition: form-data; name="files[1]"; filename="2.png"
Content-Type: image/png

------WebKitFormBoundary4Lc5A5Z4vExW8bNj--

Whereas when I use a simple upload form with no JS:
<form action="https://angular-file-upload-cors-srv.appspot.com/upload" method="post" enctype="multipart/form-data">
    <input type="file" name="files" multiple="multiple" />
   <input type="submit" />
</form>

The payload looks like this:
------WebKitFormBoundaryePQRTeioGZmfAN96
Content-Disposition: form-data; name="files"; filename="1.png"
Content-Type: image/png

------WebKitFormBoundaryePQRTeioGZmfAN96
Content-Disposition: form-data; name="files"; filename="2.png"
Content-Type: image/png

------WebKitFormBoundaryePQRTeioGZmfAN96--

On the server side I'm using a Spring RESTController endpoint:
 @RequestMapping(value="/upload", method=RequestMethod.POST)
    public ResponseEntity<Long> handleFileUpload(
            @RequestParam("files") MultipartFile[] files) {
...
}

With the plain HTML upload form this works well. With your upload (files[1], files[2]) the array is always empty. Is there a way to change that? The option arrayKey does not have this specification.
Forked JSFiddle with the normal HTML-form:
https://jsfiddle.net/vxoLLenu/
I'm using chrome.
Thanks for you help!

Add arrayKey: '' option to your config

@danialfarid
if I want to send files and string array together, is it possible?
The arrayKey: '' makes to send files O.K but also makes the array of string to change which sent together with the files. so, I want to give arrayKey option to files and array of string separately, but I think there isn't that kind of action.
is it possible? or should I send files and array of string separately?

You can use formDataAppender but I would suggest to convert your array to json string and send it as a string and convert it to object on the server from json string.


Manage order of podcast, and continuous-play behavior.

It would be nice if this could be configured per-podcast, like the native applications; rather than as a "Desktop Setting" applied to all podcasts in Your Podcasts but either would be better than neither:

[ ] Allow sort order to be oldest-to-newest rather than the default only: newest-to-oldest
[ ] Allow continuous-play to be turned off, so that the player doesn't move on to the next automatically.

Neither of these are GPMDP features, you should give this feedback on Google Product Forums


Fix #28 Default activeClass option

If no activeClass option is provided it break when trying to run trim on null.
Use nullsafe to fix & trigger defaults

@GingerNinjaNicko Thanks for contributing to the project.


last minute collateral swap changes to the Vault

When reviewing the Uniswap V3 Strategy PR, it was clear we need to remove the _deprecated property from the Strategy struct that is used by the Vault's strategies mapping.
Looking at both the OETH and OUSD vault storage, there is no impact in removing this
OUSD strategies storage https://evm.storage/eth/17540105/0xe75d77b1865ae93c7eaa3040b038d7aa7bc02f70/strategies#map
OETH strategies storage
https://evm.storage/eth/17540186/0x39254033945aa2e4809cc2977e7087bee48bd7ab/strategies#map

Depreciating this variable was done on December 3, 2020. The deploy script file for the relaunch of OUSD was made on Dec 20th, 2020, so it seems likely from the commit history that this depreciated variable has never been live on the current vault. The actual deploy was something like the last day of the year 2020.


linux-rock64: kernel for Rock64 and RockPro64 systems

Motivation for this change
This PR adds kernel for Rock64 and RockPro64 systems.
I tried to use 5.4.y and 5.6.y both vanilla and from @lopsided98 repo, but they end up with PCIe issues on my RockPro64:
[    2.172391] rockchip-pcie f8000000.pcie: PCIe link training gen1 timeout!
[    2.173158] rockchip-pcie: probe of f8000000.pcie failed with error -110

Kernel 4.19.y does not have this issue.
I'd like to provide sd-image-rock64.nix in a further PR to allow easy build of SD images for these systems.
Things done

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

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

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

@samueldr is likely to have an opinion on this.

I can also test this as I have the hardware.

@prusnak I tried to respond to you on IRC, but you weren't online
I don't know what the PCIe issue is, other than that it is known to be finicky.
I'm not really sure I want my kernel to be included in an official capacity in nixpkgs, since I sometimes don't update it for months at a time. I particularly don't want the 4.19 branch to be included since I haven't updated it for a long time and I no longer use it.
I think this may be more appropriate for the nixos-hardware repository.

@lopsided98 Fair enough - we can try to use the kernel directly from the ayufan-rock64/linux-kernel repo (that's what armbian is using and I saw no problems with PCIe there either). I had trouble compiling it against the current nixpkgs master, though.

I believe you have to pass autoModules = false to buildLinux to get the downstream 4.4 kernel to compile.
You might also want to try https://github.com/ayufan-rock64/linux-mainline-kernel (which my repo is based on) in the off chance that I left out one of the patches that makes PCIe work.

If I can find an unused PCIe device lying around, I'll try to reproduce the problem as well.

I just tried 5.6.0-1137-ayufan tag from ayufan-rock64/linux-mainline-kernel repo and it shows the same error. So you have not missed any of the patches there. :-)

I am trying 4.4.202-1237-rockchip-ayufan tag from the ayufan-rock64/linux-kernel repo now and the build fails with:
../sound/soc/rockchip/rockchip_vad.c: In function 'snd_pcm_vad_read':
../sound/soc/rockchip/rockchip_vad.c:281:10: error: implicit declaration of function 'snd_pcm_vad_avail'; did you mean 'snd_pcm_vad_read'? [-Werror=implicit-function-declaration]
  281 |  avail = snd_pcm_vad_avail(substream);
      |          ^~~~~~~~~~~~~~~~~
      |          snd_pcm_vad_read
../sound/soc/rockchip/rockchip_vad.c: At top level:
../sound/soc/rockchip/rockchip_vad.c:350:19: error: conflicting types for 'snd_pcm_vad_avail'
  350 | snd_pcm_uframes_t snd_pcm_vad_avail(struct snd_pcm_substream *substream)
      |                   ^~~~~~~~~~~~~~~~~
../sound/soc/rockchip/rockchip_vad.c:281:10: note: previous implicit declaration of 'snd_pcm_vad_avail' was here

I reworked the PR to not include kernel 4.19.y from lopsided98, but rather to use the latest tagged release in ayufan-rock64/linux-kernel repo - that is 4.4.202-1237-rockchip-ayufan.

I have a 5.5 kernel on my github that works. I can also upload my nixpkgs tree for that board that includes an expression to build an Image.
it's hard for me to keep the kernel up to date with what's in master though, and it includes an overclock to 2.2/1.7 which may require fan cooling.
Although it's a fairly popular board, I think we can get into a mess if we start officially supporting lots of forked kernels of various versions for every come-and-go SBC out there.

I have a 5.5 kernel on my github that works.

Does it work with PCIe as well?

Although it's a fairly popular board ..

I think we this could be moved to the nixos-hardware repository like it was suggested earlier.

@prusnak Yes I've been running root from a pcie nvme drive for months ( kernel/initrd on SD card ).
Using Panfrost on mesa-git, I'm running pantheon DE with no problems as well.
There may be a minor version patch in my nixpkgs that isn't applied to my kernel fork, but I've been running 5.5.7 specifically for some time now. Major version patches don't apply cleanly and need a bit of manual intervention.
The nixos-hardware repo does seems like it might be a fitting place for it.

Will close this PR and create another one to the nixos-hardware repo.


fix Array JSONEncodable

Avoid using fatal error on JSONEncodable instead of conforming protocol with where clause

Hmmm... I wanted to do this ages ago, and there was some reason why I couldn't. I think it was causing some build errors.
We're going to need to test this manually on iOS versions pre 14.4. I'm wondering if the issues I saw before had to do with the conversion of the nested AnyHashable types inside of the array (which doesn't work properly on iOS < 14.4).
Thanks for the PR. Give me some time to look into this a bit further before we pull it in.

Do you need help with something?


azure-core-http-vertx uses Netty scheduler which causes GraalVM native image builds to fail

https://github.com/Azure/azure-sdk-for-java/blob/23ee5152b1bafe998492855eb0ecd24db3268ad4/sdk/core/azure-core-http-vertx/src/main/java/com/azure/core/http/vertx/VertxAsyncHttpClient.java#L34C29-L34C38
Here's the exact line.
This class should ideally use the vert.x timer instead of the Netty scheduler, in order to solve this build time issue with GraalVM.

Thanks for filing this issue @The-Funk.
We'll get this fixed to provide better support for GraalVM native images. Is there any documentation that recommends the Vert.x timer usage that could be included in the fix for future reference?

@alzimmermsft I don't necessarily have docs for it but I'm coming from a Quarkus development background, and I can tell you from experience that Netty doesn't play nicely with GraalVM.
This is a chat I was having with one of the Quarkus developers over on their Zulip chat.
It should be noted that prior to replacing the Netty Http implementation with the Vert.x Http implementation there were many more errors in the compilation process (too many to count,, I spent a few days trying)
Here is my minimal reproducer using Quarkus
If you attempt a native image build with that project above it will fail with the error mentioned in the Zulip chat.
The error implicates the Netty scheduler.

Thank you @alzimmermsft !


Restart -> No Hosts?

Upon restarting my client I'm getting a 'no hosts found' error, though I had plenty of hosts before restarting.
:(

You should reload them when you reload the blockchain, right? Is there some other requirement for adding them to the DB? Do they need to respond to a ping or something?

They need to respond to a ping.


Think about native integration of Blockly Plus to JavaScript Core source

thank you for all effort, these blocks are very interesting and used by end-users.
Unfortunately update of javascript can break this source, so I would like to suggest adding these elements native to the javascript adapter.
https://github.com/ioBroker/ioBroker.javascript/issues/649
That would also replace : https://github.com/excal-foley/ioBroker.blockly-plus/issues/2

issue open for to long without follow-up, closure


Create mockups and update export sheet for 'Tower Info' panel

The 'Tower Info' panel should contain all information related to the Tower class, as well as other clickable elements that lead to tower-related information.
Here's a rough visualization of the tower's stats:

...and tower description window with extra space for skills, wearable items, etc.:

Thanks to jhoijhoi for visual prototypes.

Updated as Praytic wanted the panel to float on the right.
Top 3 are Level, Upgrade, Sell
Top left are Tower Info and Tower Stats
Left bottom 6 are item slots (would only show how many actual slots the tower had)
Bottom 4 are the specials (castable or not), again only showing if the tower has them
For towers that are super simple (no specials, 1 item slot), the height of the box would obviously just shrink to fit what was needed
I think the scale of the buttons is about right, slightly bigger than the element buttons, but smaller than the build hud buttons


Error while Normalizations

After the .hic files are created it cannot be normalized having "buffer is smaller than requested size" error.
Any help is appreciated.
Thanks

I also have the same problem in normalization using version 2.20.00 and version 1.9.9


Ino has no support for due

I have tried using arduino 1.6.4 but the arduino due is not found when doing list-models.
How can i go about it?

ino list-models -d ~/bin/arduino-1.6.1/
Searching for Board description file (boards.txt) ... FAILED
Board description file (boards.txt) not found. Searched in following places:

/home/larsemil/bin/arduino-1.6.1/hardware/arduino

Allthough there is a hardware/arduino/sam/boards.txt

cloned instead of using pip and then i got it working.


default ndt5 JavaScript client does not report Network Latency

The default ndt5 JS client in this repo needs to be updated like the mlab-speedtest

@critzo

My recollection on the review triage call was that we had updated speed.measurementlab.net.  If we don't plan to update the ndt5 client in this repo again, this issue can be closed. If we plan to continue supporting it, we should make this change in the default client too.

Accidentally closed. I think this is a simple change to add the correct value for latency.
https://github.com/m-lab/ndt-server/search?q=latency&unscoped_q=latency


Add support for Ceylon

Fixes #2095
Changes proposed:

[X] Add

The icon does not meet our art guidelines.

Updated Ceylon svg image as per art guidelines

Still not there yet but don't worry we'll do the rest.

Still not there yet but don't worry we'll do the rest.

Thank You

To be honest, I was going to make this PR as soon as I got at my home, since it is annoying to make icons on my work station (Ubuntu hasn't Adobe Illustrator).
But I am happy that someone took the time for it.
Also, here is the corrected .svg according to the art guidelines:
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 32 32"><defs><radialGradient id="a" cx="22.327" cy="-938.347" r="15.003" gradientTransform="translate(-0.491 997.053) scale(1.031 1.053)" gradientUnits="userSpaceOnUse"><stop offset="0" stop-color="#fff"/><stop offset="1" stop-color="#ab710a"/></radialGradient></defs><title>file_type_ceylon</title><path d="M10.78,21.986a3.433,3.433,0,0,1-.62-.226A10.987,10.987,0,0,0,8.5,26h2.724A14.323,14.323,0,0,1,10.78,21.986Zm8.827-1.479a20.947,20.947,0,0,0-1.264,3.885c-.118.538.239,1.074.172,1.608h3.426c-.9-2.547-1.107-6.251-1.575-7.732C20.355,18.247,19.62,20.525,19.607,20.507Z" style="fill:#ab710a"/><path d="M29.359,11.748c-.779-1.131-2.557-2.081-2.971-3.372a1.954,1.954,0,0,1,.079-1.326c.2-.316-.119-.226-.119-.226-.443.174-.634-.323-.634-.323-.066-.174.025-.706-.356-.416-.687.527-.461,1.809-.332,2.325a5.4,5.4,0,0,0,1.306,2.338c.222.21,1.617,1.778,1.426,2.58a.641.641,0,0,1-.476.593c-1.016.208-1.346-1.065-1.346-1.065-.762-3.322-1.993-4.485-1.993-4.485A23.639,23.639,0,0,0,18,8.9,34.6,34.6,0,0,0,4.657,11C2.983,13.455,2,18.012,2,18.012s0,.023.016.025a.058.058,0,0,0,.057-.029,14.223,14.223,0,0,1,2.119-2.185A30.133,30.133,0,0,0,5.437,26H8.094a11.932,11.932,0,0,1,1.942-4.8c.988.765,3.22.538,3.22.538.394,1.525,1.2,4.257,1.2,4.257h3.2A21.01,21.01,0,0,1,19.4,19.973a13.057,13.057,0,0,0,.812-2.388,1.361,1.361,0,0,1,1.424-1.246c.483,0,2.68,1.253,4.321,1.169,2.858-.147,3.985-1.5,4.041-3.037A4.691,4.691,0,0,0,29.359,11.748Zm-9.187,3.263a.553.553,0,0,1-.06.122.327.327,0,0,1-.113.106.307.307,0,0,1-.162.037.493.493,0,0,1-.146-.034,1.4,1.4,0,0,1-.416-.3c-.06-.056-.115-.115-.169-.172l-.155-.165a.97.97,0,0,0-.327-.187A4.185,4.185,0,0,0,18.2,14.3c-.148-.036-.3-.074-.458-.128a1.142,1.142,0,0,1-.129-.053l-.064-.024a.563.563,0,0,1-.084-.061.547.547,0,0,1-.124-.159.672.672,0,0,1-.062-.167,1.112,1.112,0,0,1-.022-.3,1.925,1.925,0,0,1,.028-.262,4,4,0,0,1,.122-.482q.073-.225.162-.452c.029-.075.057-.147.091-.226a2.283,2.283,0,0,1,.115-.226,2.529,2.529,0,0,1,.646-.731,2.973,2.973,0,0,1,.4-.258,2.3,2.3,0,0,1,.443-.181,4.134,4.134,0,0,0-.682.613,2.8,2.8,0,0,0-.485.731,1.8,1.8,0,0,0-.075.2l-.069.226c-.044.147-.088.294-.124.441a4.25,4.25,0,0,0-.091.432,2.012,2.012,0,0,0-.02.2.682.682,0,0,0,.<IP_ADDRESS>,0,0,0,.035.077h0l.<IP_ADDRESS>c.128.049.276.088.425.135a3.941,3.941,0,0,1,.454.17,1.23,1.23,0,0,1,.443.316c.<IP_ADDRESS>.141.2l.135.183a2.111,2.111,0,0,0,.14.168.879.879,0,0,0,.<IP_ADDRESS>,0,0,0,.<IP_ADDRESS>,0,0,0,.131-.115,1.094,1.094,0,0,0,.1-.2c.029-.073.051-.147.076-.227A1.4,1.4,0,0,1,20.172,15.011ZM23,12.994a.485.485,0,0,1-.613.315.5.5,0,0,1-.308-.626.48.48,0,0,1,.726-.259A.438.438,0,0,1,23,12.994Z" style="fill:#e3a835"/><path d="M29.359,11.748c-.779-1.131-2.557-2.081-2.971-3.372a1.954,1.954,0,0,1,.079-1.326c.2-.316-.119-.226-.119-.226-.443.174-.634-.323-.634-.323-.066-.174.025-.706-.356-.416-.687.527-.461,1.809-.332,2.325a5.4,5.4,0,0,0,1.306,2.338c.222.21,1.617,1.778,1.426,2.58a.641.641,0,0,1-.476.593c-1.016.208-1.346-1.065-1.346-1.065-.762-3.322-1.993-4.485-1.993-4.485A23.639,23.639,0,0,0,18,8.9,34.6,34.6,0,0,0,4.657,11C2.983,13.455,2,18.012,2,18.012s0,.023.016.025a.058.058,0,0,0,.057-.029,14.223,14.223,0,0,1,2.119-2.185A30.133,30.133,0,0,0,5.437,26H8.094a11.932,11.932,0,0,1,1.942-4.8c.988.765,3.22.538,3.22.538.394,1.525,1.2,4.257,1.2,4.257h3.2A21.01,21.01,0,0,1,19.4,19.973a13.057,13.057,0,0,0,.812-2.388,1.361,1.361,0,0,1,1.424-1.246c.483,0,2.68,1.253,4.321,1.169,2.858-.147,3.985-1.5,4.041-3.037A4.691,4.691,0,0,0,29.359,11.748Zm-9.187,3.263a.553.553,0,0,1-.06.122.327.327,0,0,1-.113.106.307.307,0,0,1-.162.037.493.493,0,0,1-.146-.034,1.4,1.4,0,0,1-.416-.3c-.06-.056-.115-.115-.169-.172l-.155-.165a.97.97,0,0,0-.327-.187A4.185,4.185,0,0,0,18.2,14.3c-.148-.036-.3-.074-.458-.128a1.142,1.142,0,0,1-.129-.053l-.064-.024a.563.563,0,0,1-.084-.061.547.547,0,0,1-.124-.159.672.672,0,0,1-.062-.167,1.112,1.112,0,0,1-.022-.3,1.925,1.925,0,0,1,.028-.262,4,4,0,0,1,.122-.482q.073-.225.162-.452c.029-.075.057-.147.091-.226a2.283,2.283,0,0,1,.115-.226,2.529,2.529,0,0,1,.646-.731,2.973,2.973,0,0,1,.4-.258,2.3,2.3,0,0,1,.443-.181,4.134,4.134,0,0,0-.682.613,2.8,2.8,0,0,0-.485.731,1.8,1.8,0,0,0-.075.2l-.069.226c-.044.147-.088.294-.124.441a4.25,4.25,0,0,0-.091.432,2.012,2.012,0,0,0-.02.2.682.682,0,0,0,.<IP_ADDRESS>,0,0,0,.035.077h0l.<IP_ADDRESS>c.128.049.276.088.425.135a3.941,3.941,0,0,1,.454.17,1.23,1.23,0,0,1,.443.316c.<IP_ADDRESS>.141.2l.135.183a2.111,2.111,0,0,0,.14.168.879.879,0,0,0,.<IP_ADDRESS>,0,0,0,.<IP_ADDRESS>,0,0,0,.131-.115,1.094,1.094,0,0,0,.1-.2c.029-.073.051-.147.076-.227A1.4,1.4,0,0,1,20.172,15.011ZM23,12.994a.485.485,0,0,1-.613.315.5.5,0,0,1-.308-.626.48.48,0,0,1,.726-.259A.438.438,0,0,1,23,12.994Z" style="opacity:0.44999998807907104;isolation:isolate;fill:url(#a)"/></svg>

@JimiC Can you make the fix?

@KingDarBoja Updated svg image.

Still, the file size is enormous for usage and since language id is used extensions should not be filled.

I always forget the file size restriction (3KB or less), so my apologies for that.
Here is the lightweight version:
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 32 32"><title>file_type_ceylon</title><path d="M10.78,21.986a3.433,3.433,0,0,1-.62-.226A10.988,10.988,0,0,0,8.5,26h2.724A14.328,14.328,0,0,1,10.78,21.986Zm8.827-1.479a20.969,20.969,0,0,0-1.264,3.885c-.118.538.239,1.074.172,1.608h3.426c-.9-2.547-1.107-6.251-1.575-7.732C20.355,18.247,19.62,20.525,19.607,20.507Z" style="fill:#ab710a"/><path d="M29.359,11.748c-.779-1.131-2.557-2.081-2.971-3.372a1.958,1.958,0,0,1,.079-1.326c.2-.316-.119-.226-.119-.226-.443.174-.634-.323-.634-.323-.066-.174.025-.706-.356-.416-.687.527-.461,1.809-.332,2.325a5.392,5.392,0,0,0,1.306,2.338c.222.21,1.617,1.778,1.426,2.58a.642.642,0,0,1-.476.593c-1.016.208-1.346-1.065-1.346-1.065-.762-3.322-1.993-4.485-1.993-4.485A23.642,23.642,0,0,0,18,8.9,34.606,34.606,0,0,0,4.657,11C2.983,13.455,2,18.012,2,18.012s0,.023.016.025a.057.057,0,0,0,.057-.029,14.219,14.219,0,0,1,2.119-2.185A30.149,30.149,0,0,0,5.437,26H8.094a11.929,11.929,0,0,1,1.942-4.8c.988.765,3.22.538,3.22.538.394,1.525,1.2,4.257,1.2,4.257h3.2A21.026,21.026,0,0,1,19.4,19.973a13.077,13.077,0,0,0,.812-2.388,1.361,1.361,0,0,1,1.424-1.246c.483,0,2.68,1.253,4.321,1.169,2.858-.147,3.985-1.5,4.041-3.037A4.689,4.689,0,0,0,29.359,11.748Zm-9.187,3.263a.553.553,0,0,1-.06.122.328.328,0,0,1-.113.106.307.307,0,0,1-.162.037.493.493,0,0,1-.146-.034,1.4,1.4,0,0,1-.416-.3c-.06-.056-.115-.115-.169-.172l-.155-.165a.97.97,0,0,0-.327-.187A4.162,4.162,0,0,0,18.2,14.3c-.148-.036-.3-.074-.458-.128a1.2,1.2,0,0,1-.129-.053l-.064-.024a.563.563,0,0,1-.084-.061.547.547,0,0,1-.124-.159.672.672,0,0,1-.062-.167,1.119,1.119,0,0,1-.022-.3,1.925,1.925,0,0,1,.028-.262,4,4,0,0,1,.122-.482q.073-.225.162-.452c.029-.075.057-.147.091-.226a2.4,2.4,0,0,1,.115-.226,2.525,2.525,0,0,1,.646-.731,2.9,2.9,0,0,1,.4-.258,2.277,2.277,0,0,1,.443-.181,4.134,4.134,0,0,0-.682.613,2.8,2.8,0,0,0-.485.731,1.782,1.782,0,0,0-.075.2l-.069.226c-.044.147-.088.294-.124.441a4.25,4.25,0,0,0-.091.432,1.907,1.907,0,0,0-.02.2.686.686,0,0,0,.<IP_ADDRESS>,0,0,0,.035.077h0l.<IP_ADDRESS>c.128.049.276.088.425.135a3.873,3.873,0,0,1,.454.17,1.233,1.233,0,0,1,.443.316,2.055,2.055,0,0,1,.141.2l.135.183c.<IP_ADDRESS>.14.168a.879.879,0,0,0,.<IP_ADDRESS>,0,0,0,.<IP_ADDRESS>,0,0,0,.131-.115,1.068,1.068,0,0,0,.1-.2c.029-.073.051-.147.076-.227A1.4,1.4,0,0,1,20.172,15.011ZM23,12.994a.485.485,0,0,1-.609.316h0a.5.5,0,0,1-.308-.626.48.48,0,0,1,.6-.319.493.493,0,0,1,.127.06A.438.438,0,0,1,23,12.994Z" style="fill:#c18d30"/></svg>

Had to remove the gradient from the icon.

I always forget the file size restriction (3KB or less), so my apologies for that.
Here is the lightweight version:
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 32 32"><title>file_type_ceylon</title><path d="M10.78,21.986a3.433,3.433,0,0,1-.62-.226A10.988,10.988,0,0,0,8.5,26h2.724A14.328,14.328,0,0,1,10.78,21.986Zm8.827-1.479a20.969,20.969,0,0,0-1.264,3.885c-.118.538.239,1.074.172,1.608h3.426c-.9-2.547-1.107-6.251-1.575-7.732C20.355,18.247,19.62,20.525,19.607,20.507Z" style="fill:#ab710a"/><path d="M29.359,11.748c-.779-1.131-2.557-2.081-2.971-3.372a1.958,1.958,0,0,1,.079-1.326c.2-.316-.119-.226-.119-.226-.443.174-.634-.323-.634-.323-.066-.174.025-.706-.356-.416-.687.527-.461,1.809-.332,2.325a5.392,5.392,0,0,0,1.306,2.338c.222.21,1.617,1.778,1.426,2.58a.642.642,0,0,1-.476.593c-1.016.208-1.346-1.065-1.346-1.065-.762-3.322-1.993-4.485-1.993-4.485A23.642,23.642,0,0,0,18,8.9,34.606,34.606,0,0,0,4.657,11C2.983,13.455,2,18.012,2,18.012s0,.023.016.025a.057.057,0,0,0,.057-.029,14.219,14.219,0,0,1,2.119-2.185A30.149,30.149,0,0,0,5.437,26H8.094a11.929,11.929,0,0,1,1.942-4.8c.988.765,3.22.538,3.22.538.394,1.525,1.2,4.257,1.2,4.257h3.2A21.026,21.026,0,0,1,19.4,19.973a13.077,13.077,0,0,0,.812-2.388,1.361,1.361,0,0,1,1.424-1.246c.483,0,2.68,1.253,4.321,1.169,2.858-.147,3.985-1.5,4.041-3.037A4.689,4.689,0,0,0,29.359,11.748Zm-9.187,3.263a.553.553,0,0,1-.06.122.328.328,0,0,1-.113.106.307.307,0,0,1-.162.037.493.493,0,0,1-.146-.034,1.4,1.4,0,0,1-.416-.3c-.06-.056-.115-.115-.169-.172l-.155-.165a.97.97,0,0,0-.327-.187A4.162,4.162,0,0,0,18.2,14.3c-.148-.036-.3-.074-.458-.128a1.2,1.2,0,0,1-.129-.053l-.064-.024a.563.563,0,0,1-.084-.061.547.547,0,0,1-.124-.159.672.672,0,0,1-.062-.167,1.119,1.119,0,0,1-.022-.3,1.925,1.925,0,0,1,.028-.262,4,4,0,0,1,.122-.482q.073-.225.162-.452c.029-.075.057-.147.091-.226a2.4,2.4,0,0,1,.115-.226,2.525,2.525,0,0,1,.646-.731,2.9,2.9,0,0,1,.4-.258,2.277,2.277,0,0,1,.443-.181,4.134,4.134,0,0,0-.682.613,2.8,2.8,0,0,0-.485.731,1.782,1.782,0,0,0-.075.2l-.069.226c-.044.147-.088.294-.124.441a4.25,4.25,0,0,0-.091.432,1.907,1.907,0,0,0-.02.2.686.686,0,0,0,.<IP_ADDRESS>,0,0,0,.035.077h0l.<IP_ADDRESS>c.128.049.276.088.425.135a3.873,3.873,0,0,1,.454.17,1.233,1.233,0,0,1,.443.316,2.055,2.055,0,0,1,.141.2l.135.183c.<IP_ADDRESS>.14.168a.879.879,0,0,0,.<IP_ADDRESS>,0,0,0,.<IP_ADDRESS>,0,0,0,.131-.115,1.068,1.068,0,0,0,.1-.2c.029-.073.051-.147.076-.227A1.4,1.4,0,0,1,20.172,15.011ZM23,12.994a.485.485,0,0,1-.609.316h0a.5.5,0,0,1-.308-.626.48.48,0,0,1,.6-.319.493.493,0,0,1,.127.06A.438.438,0,0,1,23,12.994Z" style="fill:#c18d30"/></svg>

Had to remove the gradient from the icon.

@KingDarBoja Improved svg image.

Still ceylon needs to be removed from extensions.


support custom runtime in cli

As we provide a way to declare custom runtime in function object, we should cover it in kubeless cli as well. Probably using with --runtime-image flag

I am taking this one


Fix bazel test //... in main repository

Yeah, there is no CI. I can add a bare-bones one though.

it would be great to have a barebones GitHub actions CI.


Do not use latest keras==2.6.0

Motivation
See description below.
Description of the changes
Attempts to hotfix broken CI. See https://github.com/optuna/optuna/pull/2851.

@not522 , @nzw0301 could any you review this PR?

Thanks for the quick approval, could you merge it as well?


NO-ISSUE: rebase-main-4.16.0-0.nightly-2024-02-17-094036_amd64-2024-02-17_arm64-2024-02-19

Which issue(s) this PR addresses:

Closes #

/hold

/hold cancel

/lgtm


cleanup: remove internal/nodes

deployer >= 0.19 provides most of the functionalities in internal/nodes. So we dissolve the latter and we move the code to use the former, to reduce the duplication, even if the API of the deployer package can use some refinement.
In addition, we get rid of another internal duplication by moving to k8s/utils/ptr

/retest

/hold

/hold cancel
we don't have LGTM anyway


Location of Contribution action links

What
Contribution action links on numerous service manual pages are located at the bottom of pages. It would be good to set-up any analytics to monitor the usage of the contribution action links, including the monitoring of the specific page regarding these action links.
Reoccurring theme - it would be good to understand more about the location issue (long pages) and compare with findings from other teams etc. Maybe the IA team have long page issues?
Why
Feedback/recent user research sessions found the current placement of the contribution action links at the bottom of pages would not be popular for use by site users.
Done when
We have:

[ ] An understanding as to the usage of the contribution action links.

[ ] An understanding as to the reoccurring theme of long pages.

Related to
EPIC #993


Introduce introspecing fast path for keyof intersection distribution

Fixes #23977
This does fix the OOM crash, however right now the fast-path logic just gives up if there's a non-literal type present; handling string and symbol gracefully without giving up on the fastpath is maybe worth doing.

cc @ahejlsberg since you got assigned to this issue a minute before I opened this PR.

I've just put up #24137 which performs a similar optimization but in the main path of intersection type creation.


mod: change first run url to fastforward.team

todo: create firstrun.html in FastForwardTeam/Website


animbits cache manager

When having isRig attribute on a non mgear rig present it still can't find the rig.
It is only looking for this attribute right?
error in scripteditor:

is_rig is the attribute that needed to be there. So issue solved!

import os
RIG SEARCH ATTRIBUTE
os.environ["MGEAR_CACHE_MANAGER_RIG_ATTRIBUTE"] = ""
RIG MODEL GROUP
os.environ["MGEAR_CACHE_MANAGER_MODEL_GROUP"] = ""
CACHE DESTINATION
os.environ["MGEAR_CACHE_MANAGER_CACHE_DESTINATION"] = ""
it doesn't seem to want other than is_rig attribute

thanks @liudger for closing this. I did forget :)


[Question] Glob for exclude 'node_modules', 'package.json', 'package-lock.json' and include all other files and folders

Hello 👋
Could someone help me with glob string? I need to exclude 'node_modules', 'package.json', 'package-lock.json' and include all other files and folders.
I tried something like this
**/!(core|node_modules|.git|package.json|package-lock.json|style.css)/*.*
But no success.
Thank you!
Best regards,
Alex

That string says "any number of path segments, then something other than (...), then a file with a . in it".  So it'll match a/b/c/core/d/e.f, because the ** matches a/b/c/core, the d is not in the exclude list, and e.f matches the *.*.  But it won't match, for example, ./x.y, because there's no "something other than (...)" preceding it.
Maybe you want something like this? ./!(core|node_modules|.git|package.json|package-lock.json|style.css)/**  That'd pick up all files and directories that do not start with the listed path portions.
Or you could use combine it with an explicit ignore option, and do something like this:
glob('!(core|node_modules|.git|package.json|package-lock.json|style.css)/**', { ignore: '**/(core|node_modules|.git|package.json|package-lock.json|style.css)/**' })

which would pull in all files everywhere, except those that match the exclude pattern (and avoid walking them at the first level, since you know that you'll be excluding those anyway).

what if you want to exclude a folder that is nested deeply

@techsin what this mean? Just add the deeply nested folder to the exclude list?

glob('whatever', { ignore: '**/ignoreme/**' })


Replace OkHttp Bom

Due to the current gradle publish setup
the bom is attached as a regular dependency
which is not correctly resolved by applications
using this library. By using regular dependencies
the problem is solved

This should address #27


Hailo AI Kit + Rpi 5 + FastSAM Segment anything model (Meta)

Dear contributors,
I have bought and installed the Hailo AI kit on rpi 5 by following this article https://www.raspberrypi.com/documentation/accessories/ai-kit.html
but when i try to use it with the following code.
from fastsam import FastSAM, FastSAMPrompt

model = FastSAM('./weights/FastSAM.pt')
IMAGE_PATH = './images/dogs.jpg'
everything_results = model(IMAGE_PATH, retina_masks=True, imgsz=1024, conf=0.4, iou=0.9,)
prompt_process = FastSAMPrompt(IMAGE_PATH, everything_results)

ann = prompt_process.text_prompt(text='a photo of a dog')

prompt_process.plot(annotations=ann, output_path='./output/dog.jpg',)

it's still using the cpu without any AI acceleration.
Could you help me to solve this?

Hi @agronomofiorentini, I order to execute the model on Hailo it has to be first compiled and than executed using Hailo tools. If you need more information and got more questions please join the community in https://community.hailo.ai/

I signed in the community hailo but i have to wait for approval.
Anyone tried to use the FastSam with text prompt in hailo? How to compile it and use it?
Anyone has an example that i can follow?


CI checks and/or action registration should not allow invalid type

If I create an action metadata file containing a section with an invalid parameter type, CI checks will pass, and I can register the action. It only fails when I attempt to use it.
Example YAML snippet:
  commands:
    type: "list"
    description: "Configuration commands to run"
    required: true

This action can be registered, and will show up if I run st2 run packname.action -h, e.g.:
$ st2 run clicrud.configure -h|grep -C 2 list
    commands
        Configuration commands to run
        Type: list

    host

But if I attempt to use that action, it (correctly) fails with a 500 error:
ERROR: 500 Server Error: Internal Server Error
MESSAGE: u'list' is not valid under any of the given schemas

Failed validating 'anyOf' in schema['properties']['properties']['additionalProperties']['properties']['type']:
    {'anyOf': [{'$ref': '#/definitions/simpleTypes'},
               {'items': {'$ref': '#/definitions/simpleTypes'},
                'minItems': 1,
                'type': 'array',
                'uniqueItems': True}]}

On instance['properties'][u'commands']['type']:
    u'list' for url: http://<IP_ADDRESS>:9101/v1/executions

I believe that we should identify this misconfiguration sooner in the pipeline, rather than at action run time.

Being addressed - see commentary in #532

Fixed by https://github.com/StackStorm/st2/pull/2872 - thanks!


cli.PrivateANNQuery(keys) always returns 0

Hi, from Japan.
I have read your wonderful paper using DPF to retrieve similar data in a privacy-preserving way (two non-colluding servers and malicious setting).
I would like to employ this scheme, however, cli.PrivateANNQuery(keys) always returns 0.
I have missed something important??
Thank you for your great work.

I also checked the situation using the training dataset as below, but candidate is always zero.
cmd/client/main.go

		var trainingData []*vec.Vec
		trainingData, _, _, _ = ann.ReadDataset("../datasets/mnist")
		for index, value := range trainingData {
			q := value

			keys := make([][]uint64, cli.SessionParams.NumTables)
			for i := range keys {
				// Returns numProbes values inserted into numPartition buckets
				// 0 is the value in slots without hashes
				// Here numPartitions = numProbes
				keys[i] = ann.ComputeProbes(cli.SessionParams.HashFunctions[i], q, cli.SessionParams.NumProbes, cli.SessionParams.NumProbes)
			}
			// Step 3: query the buckets using PIR
			log.Printf("[Client]: querying %v buckets in %v tables\n",
				cli.SessionParams.NumTables*cli.SessionParams.NumProbes,
				cli.SessionParams.NumTables)

			candidate := cli.PrivateANNQuery(keys)
			fmt.Printf("%v,%v", index, candidate)
			fmt.Println()
			queryTime := time.Since(start).Milliseconds()
			cli.Experiment.QueryClientMS = append(cli.Experiment.QueryClientMS, queryTime)
			log.Printf("[Client]: ANN query took %v seconds\n", time.Since(start).Seconds())
		}
		// Experiment completed
		log.Printf("[Client]: finished experiment trial %v of %v \n", i+1, args.ExperimentNumTrials)
	}

I fixed this by three changes

this line should be changed to

argsB.SecretShared = allQueriesB

this part should be

for i := 0; i < stop-start; i++ {
  bits[i] = field.FP(bitsRaw[i])
}

The client should call hash.Precompute() somewhere, say, this part

cli.Experiment.QueryDownBandwidthBytes = make([]int64, 0)
hash.Precompute()
for i := 0; i < args.ExperimentNumTrials; i++ {
~~~~~~~


Allowing Admin authenticated requests to bypass WebHook auth pipeline

This facilitates debugging of WebHook methods, since your requests don't have to satisfy all the stringent WebHook requirements - you can just call into your code. Also adding some e2e tests that go through our WebHost for e2e request processing. These tests exercise some of our samples.

:shipit:

Merged


Error Parsing JSON

Hello,
I followed the instructions in the README as well as the tutorial you posted: https://www.youtube.com/watch?v=-aJDzyGgNLY
This is the code in index.js of the elctron-node-demo app:
const { ConnectionBuilder } = require('electron-cgi');

let connection = new ConnectionBuilder()
    .connectTo('dotnet', 'run', '--project', '../ElectronCgiDotNetDemo')
    .build();

connection.onDisconnect = () => {
    console.log('Connection between node and .net lost')
};

connection.send('greeting', 'Mahesh', response => {
    console.log("message is " + response);
    connection.close();
});

And this is the code in the .NET console app:
using System;
using ElectronCgi.DotNet;

namespace ElectronCgiDotNetDemo // Note: actual namespace depends on the project name.
{
    internal class Program
    {
        static void Main(string[] args)
        {
            var connection = new ConnectionBuilder()
                        .WithLogging()
                        .Build();

            // expects a request named "greeting" with a string argument and returns a string
            connection.On("greeting", (string name) =>
            {
                return $"Hello {name}!";
            });

            // wait for incoming requests
            connection.Listen();
        }
    }
}

When I run node index.js I get the following error:

As you can see it is generating the JSON object from the console app correctly:
{"type":"RESPONSE","response":{"result":"Hello Mahesh!","id":"4529207b-c562-4bd6-9155-45106dd06054"}}
But it is erroring at this line in the elctron-cgi code:

Are you able to reproduce this? Please let me know.
Thank you.

Just to second this, I'm getting the exact same issue running the instructions from the readme

Just to follow up - I solved my issue. I had a Console.WriteLine() running in my c# code prior to starting up the connection. Because this was writing to stdout, ElectronCGI was picking up the text from the Console.Writeline() as part of the JSON string.
It looks like something similar is happening to the original reporter. Looking at the error message they are receiving, it looks like messages from their build process are getting written to stdout prior to the connection opening, which are getting prepended to the json

I put a console log statement in tab-seperated-input-stream-parser.js provided by electron-cgi:

This is the error:

It looks like messageStr is the warning message and the json object concatenated together like so:
'C:\Users\{user.name}\Code\electrong-cgi\ElectronCgiDotNetDemo\ElectronCgiDotNetDemo.csproj : warning NU1803: You are running the 'restore' operation with an 'HTTP' source, 'http://svrdevfile01/nuget/nuget'. Non-HTTPS access will be removed in a future version. Consider migrating to an 'HTTPS' source.
C:\Users\{user.name}\Code\electrong-cgi\ElectronCgiDotNetDemo\ElectronCgiDotNetDemo.csproj : warning NU1803: You are running the 'restore' operation with an 'HTTP' source, 'http://{user.name}/nuget/nuget'. Non-HTTPS access will be removed in a future version. Consider migrating to an 'HTTPS' source.
{"type":"RESPONSE","response":{"result":"Hello John!","id":"71d128e1-768e-4c8e-b3f4-9ac4970fe601"}}'

This is why it's unable to perform JSON.parse(messageStr).

Hi @myarasi8 and @mwahnish
The error indicates that there's more being written to the stdout stream than just the json. Everything after "Error: Invalid incoming JSON:" was on the stdout stream.
The error/warning message comes from the C# process (https://learn.microsoft.com/en-us/nuget/reference/errors-and-warnings/nu1803)

I believe it should remove the warning message prior to performing the parse method. For now I am supressing the warning.

If you are suggesting that it should be the electron-cgi library to remove it, I don't think that is reasonable. It would be more reasonable for the dotnet sdk to output that to the stderr stream. You can try opening a ticket there.
In the end you should fix the issue on the dotnet executable side, even if electron-cgi were to remove it (or if dotnet run would output the error to the stderr stream) , the dotnet run executable would eventually fail sometime in the future: "Non-HTTPS access will be removed in a future version"


Can we remove address_auths from the authority object?

I think we can and we should if possible.

We cannot remove it because importing some collateral positions from BTS requires accounts that only have an address with no public key.


Axis-CSS normalize works, Axis' doesn't...

i get the following error with gulp-accord using stylus and axis, but not using axis-css.
/Users/jan/slimPress/node_modules/gulp-accord/node_modules/accord/node_modules/when/lib/decorators/unhandledRejection.js:79
throw e;
^
TypeError: stylus:2:11
1| base()
2| normalize()
----------------^
3|
Cannot call method 'toString' of undefined
at normalize (/Users/jan/slimPress/node_modules/axis/node_modules/nib/lib/nodes/vendor-helpers.js:14:22)
at Evaluator.<anonymous> (/Users/jan/slimPress/node_modules/axis/node_modules/nib/lib/nodes/vendor-helpers.js:75:30)
at Evaluator.invokeBuiltin (/Users/jan/slimPress/node_modules/stylus/lib/visitor/evaluator.js:1034:30)
at Evaluator.visitCall (/Users/jan/slimPress/node_modules/stylus/lib/visitor/evaluator.js:498:16)
at Evaluator.Visitor.visit (/Users/jan/slimPress/node_modules/stylus/lib/visitor/index.js:28:40)
at Evaluator.visit (/Users/jan/slimPress/node_modules/stylus/lib/visitor/evaluator.js:153:18)
at Evaluator.visitExpression (/Users/jan/slimPress/node_modules/stylus/lib/visitor/evaluator.js:626:26)
at Evaluator.Visitor.visit (/Users/jan/slimPress/node_modules/stylus/lib/visitor/index.js:28:40)
at Evaluator.visit (/Users/jan/slimPress/node_modules/stylus/lib/visitor/evaluator.js:153:18)
at Evaluator.visitRoot (/Users/jan/slimPress/node_modules/stylus/lib/visitor/evaluator.js:689:27)

It's normalize-css, I feel like there was another issue just closed for this...

https://github.com/jenius/roots.cx/pull/34


[Enhancement] Resolve OlapSink and GRF in Frontend

This fix is a following fix of ef44501. This PR will try to resolve host in OlapSink and Global Runtime Filter into IP address in Frontend.
Fixes #issue
What type of PR is this:

[ ] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Does this PR entail a change in behavior?

[ ] Yes, this PR will result in a change in behavior.
[x] No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

[ ] Interface/UI changes: syntax, type conversion, expression evaluation, display information
[ ] Parameter changes: default values, similar parameters but with different default values
[ ] Policy changes: use new policy to replace old one, functionality automatically enabled
[ ] Feature removed
[ ] Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[ ] I have checked the version labels which the pr will be auto-backported to the target branch

[ ] 3.2
[ ] 3.1
[ ] 3.0
[ ] 2.5

[FE Incremental Coverage Report]
:disappointed: fail : 15 / 25 (60.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/qe/CoordinatorPreprocessor.java
2
4
50.00%
[1299, 1316]

:large_blue_circle:
com/starrocks/server/GlobalStateMgr.java
1
2
50.00%
[573]

:large_blue_circle:
com/starrocks/common/util/DnsCache.java
3
6
50.00%
[29, 37, 38]

:large_blue_circle:
com/starrocks/system/SystemInfoService.java
5
9
55.56%
[574, 575, 576, 580]

:large_blue_circle:
com/starrocks/qe/Coordinator.java
2
2
100.00%
[]

:large_blue_circle:
com/starrocks/system/ComputeNode.java
2
2
100.00%
[]

[BE Incremental Coverage Report]
:heart_eyes: pass : 0 / 0 (0%)

@Mergifyio backport branch-3.0

@Mergifyio backport branch-2.5


Add VC 2015 32-bit support

Fixes https://github.com/clMathLibraries/clRNG/issues/11
Seems the _mm_set_epi64x intrinsic is defined in VC 2015 32-bit. So adjust the macro to handle this when determining whether to define this function. Ultimately the issue originates with Random123. However as Random123 is vendored in clRNG, it needs to be fixed here as well.

Should add that I mailed this patch upstream as well.


Add some styling to the border of Focused Time box

Hey @gKrithick thanks for creating an issue/feature request. Could you be more specific regarding the type of styling ?

Hey @gKrithick thanks for creating an issue/feature request. Could you be more specific regarding the type of styling?

I feel like adding some minute pixels to the border can embellish the look of the box since I feel the thin border doesn't really match the mood and theme of the website.

Hey @gKrithick you still working on this issue?

@Utkarshn10 how do i merge this? can u tell me the steps to merge this?

Hey @notpx you will have to create a Pull Request from your branch and then submit it for review.
Also, the gradient looks good but should only be on the border and not in the background

Hey @gKrithick you still working on this issue?

Hey @Utkarshn10! I'm incredibly sorry for not keeping up with the issue.  Sorry again, and as I see the changes done by @notpx look pretty accurate on what I wanted the box to be.


Update robot name to start HexaFloorRide...

We should change the prefix of the robot name from Hexbot to HexaFloorRide.  For example, in MQTT, AM's robot current registers as Hexbot94B97E5F52DC but he really should call himself HexaFloorRide94B97E5F52DC.
Notes:

console display of robot name is done in aaNetwork.cpp file, in cfgToConsole() function... Serial.println(_uniqueName)
aaNetwork.h has:
char _uniqueName[HOST_NAME_SIZE]; // Character array that holds unique name for Wifi network purposes.
char _uniqueNamePtr = &_uniqueName[0]; // Pointer to first address position of unique name character array.
const char _HOST_NAME_PREFIX; // Prefix for unique network name.
-main.cpp has:
Log.verboseln(" Set up wifi connection.");
setupNetwork();
setupNetwork is not in main.cpp or aaNetwork.cpp or aaNetwork.h
found setupNetwork, in include/network.cpp
- it doesn't have references to uniquename, but does call network.connect(), which is not in network.cpp or aaNetwork.cpp
aaNetwork.cpp has void aaNetwork::getUniqueName(char ptrNameArray) which has:
_convert.joinTwoConstChar(_HOST_NAME_PREFIX, _convert.noColonMAC(macAdd), _uniqueNamePtr);
and also has:
aaNetwork::aaNetwork(const char prefix)
{
Serial.println("aaNetwork::aaNetwork Default constructor running.");
_HOST_NAME_PREFIX = prefix;
} // aaNetwork::aaNetwork()

main.h has: const char* HOST_NAME_PREFIX = "Hexbot"; // Prefix for our unique network name.

This fix was snuck into the fix for issue 54 which has been merged. closing issue


feat(device, scheduler, capacity): implement CSI methods for volume operations

implement Create/Delete Volume and GetCapacity calls
add DeviceNode CRD
update vendor dependencies
add VolumeWeighted and CapacityWeighted scheduler

cc: @AmitKumarDas


SSL_process_quic_post_handshake should process multiple session tickets

It looks like SSL_process_quic_post_handshake only processes a single session ticket in a single call as demonstrated in a test code.
On the other hand, BoringSSL counterpart processes multiple session tickets in a single call.
We might be able to call SSL_process_quic_post_handshake multiple times, but there is an issue: we do not know how many times we should call it.  This is because it returns 1 when no data to read is left.
I think it would be very useful if SSL_process_quic_post_handshake can process multiple session tickets just like BoringSSL.

Completed for 1.1.1.

Merged to alpha12+quic then cherry-picked into alpha13+quic


Define FOSSA config statically in repo

Hey, I just made a Pull Request!

The current FOSSA workflow dynamically generates a config file (init) for what packages to search file by inspecting the repo.  This causes a few challenges, and results in intermittent 502 Bad Gateway errors. This is an attempt at moving this forward, reducing some noise of PR and master merge failures, and still gaining from the FOSSA value (and aligning to CNCF).
This PR avoids the regeneration each time and stores the FOSSA config statically in the repo via .fossa.yml.  This is a common pattern according to https://github.com/fossas/fossa-cli and other sources. It also includes some hardcoded definitions made.
Pros

Avoids error from the generated init where fake "cookiecutter" repos are included in the output
Avoids a few packages which lack dependencies (e.g., asset-types and cli-common)
Avoids duplicates (microsite and the monorepo of . get picked up twice, though I'm not sure why)
Allows to define a name which may make more sense to the project; e.g., in this case rather than a package being called "kubernetes" it can be defined it as "plugin-kubernetes" which better aligns to it's resulting published npm name
Allows continual tweaks. For e.g., right now fossa is still choking on the monorepo root and microsite, so we might be able to manually tweak the options, strategy, etc, to get those to pull out better. (since microsite for example has no deps, but it uses devDeps)

Cons

Requires manual changes each time a new package, like a new plugin, is contributed.

The original workflow did some yq commands to try to clean it up, and we could go back to that so long as some of the warnings/nuances we may want to tweak are dynamically updated.
Since we're not sure what's causing the gateway errors, if a hypothesis is there are too many, this may NOT fix it and we may instead need to do something like run it twice (once for all packages, and a second time for all plugins). But since it removes some oddly formatted packages, it may help.
:heavy_check_mark: Checklist

[ ] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)

It ran cleanly in about 1/3 the time, but I don't have access to see the results:
https://app.fossa.com/projects/custom+162%2Fgit@github.com:backstage%2Fbackstage/refs/branch/refs%2Fpull%2F4253%2Fmerge/a876e40828b7c1075d3f0c196083e5dc73dd7e5e
I was able to see results for another public project, so not sure if there's a flag in the FOSSA config somewhere to allow the data to be public? Unless the goal is NOT to in case it exposes some security or legal issue, I'm not sure?  Anyway, just noting I can't see it. :grin:

It ran cleanly in about 1/3 the time, but I don't have access to see the results:
https://app.fossa.com/projects/custom+162%2Fgit@github.com:backstage%2Fbackstage/refs/branch/refs%2Fpull%2F4253%2Fmerge/a876e40828b7c1075d3f0c196083e5dc73dd7e5e
I was able to see results for another public project, so not sure if there's a flag in the FOSSA config somewhere to allow the data to be public? Unless the goal is NOT to in case it exposes some security or legal issue, I'm not sure?  Anyway, just noting I can't see it. :grin:

I would vote against a static file, if fossa init isn't sufficient enough we could still generate the file ourself in the pipeline?

I would vote against a static file, if fossa init isn't sufficient enough we could still generate the file ourself in the pipeline?

@Fox32 indeed!  Could dynamically generate it, just would be a wee bit more complex.  Some notes I had written re that:

after fossa init
remove two different cookiecutters which represent fake packages which don't exist
remove duplicate microsite
remove duplicate "." with same name target and path just a period
tweak the names of the packages to potentially more friendly names (e.g., rename "jenkins" to "plugin-jenkins" or whatever might look good and be understandable to the Backstage community in the FOSSA GUI)
cli-common has no dependencies; only devDeps, so fossa warns on it, maybe convert devDeps to deps since the package is only USED for dev? (the main purpose of the package, versus only being used to BUILD the package?)
microsite has no deps, only devDeps, so fossa warns on it; maybe remove or convert devDeps to deps?
asset-types isn't a real repo, it's a subdirectory of cli, and has no deps, so FOSSA warns on it; maybe remove

e.g.,
WARNINGS
⣷ Analyzing module (1/62): microsite WARNING Could not determine deps from npm ls
⣽ Analyzing module (2/62): . WARNING Could not determine deps from npm ls
⣾ Analyzing module (8/62): asset-types WARNING Could not determine deps from npm ls
⣷ Analyzing module (10/62): cli-common WARNING Could not determine deps from npm ls

And the raw run:
$ ./fossa/fossa init
⢿ Initializing... WARNING Filtering out suspicious module: zenorocha/clipboardjs (microsite/node_modules/clipboard/composer.json)
WARNING Filtering out suspicious module: zenorocha/clipboardjs<EMAIL_ADDRESS>WARNING Filtering out suspicious module: zenorocha/clipboardjs (node_modules/clipboard/composer.json)
WARNING Filtering out suspicious module: android (:)
WARNING Filtering out suspicious module: e2e-test (packages/e2e-test)
WARNING Filtering out suspicious module: test-utils (packages/test-utils)
WARNING Filtering out suspicious module: test-utils-core (packages/test-utils-core)
WARNING Filtering out suspicious module: gyp (node_modules/node-gyp/gyp)
WARNING Filtering out suspicious module: gyp (node_modules/npm-lifecycle/node_modules/node-gyp/gyp)

And some output examples:
.fossa.yml:
- name: '{{cookiecutter.artifact_id}}'
    type: mvn
    target: pom.xml
    path: plugins/scaffolder-backend/sample-templates/springboot-grpc-template/{{cookiecutter.component_id}}
  - name: microsite
    type: npm
    target: microsite
    path: microsite
  - name: microsite
    type: npm
    target: microsite
    path: microsite
  - name: .
    type: npm
    target: .
    path: .
  - name: '{{cookiecutter.component_id}}'
    type: npm
    target: plugins/scaffolder-backend/sample-templates/react-ssr-template/{{cookiecutter.component_id}}
    path: plugins/scaffolder-backend/sample-templates/react-ssr-template/{{cookiecutter.component_id}}

@Fox32 indeed!  Could dynamically generate it, just would be a wee bit more complex.  Some notes I had written re that:

after fossa init
remove two different cookiecutters which represent fake packages which don't exist
remove duplicate microsite
remove duplicate "." with same name target and path just a period
tweak the names of the packages to potentially more friendly names (e.g., rename "jenkins" to "plugin-jenkins" or whatever might look good and be understandable to the Backstage community in the FOSSA GUI)
cli-common has no dependencies; only devDeps, so fossa warns on it, maybe convert devDeps to deps since the package is only USED for dev? (the main purpose of the package, versus only being used to BUILD the package?)
microsite has no deps, only devDeps, so fossa warns on it; maybe remove or convert devDeps to deps?
asset-types isn't a real repo, it's a subdirectory of cli, and has no deps, so FOSSA warns on it; maybe remove

e.g.,
WARNINGS
⣷ Analyzing module (1/62): microsite WARNING Could not determine deps from npm ls
⣽ Analyzing module (2/62): . WARNING Could not determine deps from npm ls
⣾ Analyzing module (8/62): asset-types WARNING Could not determine deps from npm ls
⣷ Analyzing module (10/62): cli-common WARNING Could not determine deps from npm ls

And the raw run:
$ ./fossa/fossa init
⢿ Initializing... WARNING Filtering out suspicious module: zenorocha/clipboardjs (microsite/node_modules/clipboard/composer.json)
WARNING Filtering out suspicious module: zenorocha/clipboardjs<EMAIL_ADDRESS>WARNING Filtering out suspicious module: zenorocha/clipboardjs (node_modules/clipboard/composer.json)
WARNING Filtering out suspicious module: android (:)
WARNING Filtering out suspicious module: e2e-test (packages/e2e-test)
WARNING Filtering out suspicious module: test-utils (packages/test-utils)
WARNING Filtering out suspicious module: test-utils-core (packages/test-utils-core)
WARNING Filtering out suspicious module: gyp (node_modules/node-gyp/gyp)
WARNING Filtering out suspicious module: gyp (node_modules/npm-lifecycle/node_modules/node-gyp/gyp)

And some output examples:
.fossa.yml:
- name: '{{cookiecutter.artifact_id}}'
    type: mvn
    target: pom.xml
    path: plugins/scaffolder-backend/sample-templates/springboot-grpc-template/{{cookiecutter.component_id}}
  - name: microsite
    type: npm
    target: microsite
    path: microsite
  - name: microsite
    type: npm
    target: microsite
    path: microsite
  - name: .
    type: npm
    target: .
    path: .
  - name: '{{cookiecutter.component_id}}'
    type: npm
    target: plugins/scaffolder-backend/sample-templates/react-ssr-template/{{cookiecutter.component_id}}
    path: plugins/scaffolder-backend/sample-templates/react-ssr-template/{{cookiecutter.component_id}}

Hey! Thanks for looking at this annoying issue. We talked a bit about this and feel that static config may not be what we'd want to do after all. And is it really the cause of the 502s? We'll experiment with maybe making the dynamic part more robust.

Hey! Thanks for looking at this annoying issue. We talked a bit about this and feel that static config may not be what we'd want to do after all. And is it really the cause of the 502s? We'll experiment with maybe making the dynamic part more robust.

(or of course - if you find a way it'd be more than welcome too!)

(or of course - if you find a way it'd be more than welcome too!)

Sounds good.
Btw, I did some testing on my own, and I would agree with the feedback the gentleman from CNCF had.  When running yq del transforms locally, what I thought should have been deleted, wasn't, and I had to run a few multiple times.  Interestingly, there are numerous similarly named yq libraries out there, so maybe others would be better. Or maybe even doing it wrapped in Node code or some such, rather than just command line.
So yeah the config CAN be built dynamically, but would need a bit otweaking for sure.
Will close this experiment out - onward and upward! :arrow_upper_right:

Sounds good.
Btw, I did some testing on my own, and I would agree with the feedback the gentleman from CNCF had.  When running yq del transforms locally, what I thought should have been deleted, wasn't, and I had to run a few multiple times.  Interestingly, there are numerous similarly named yq libraries out there, so maybe others would be better. Or maybe even doing it wrapped in Node code or some such, rather than just command line.
So yeah the config CAN be built dynamically, but would need a bit otweaking for sure.
Will close this experiment out - onward and upward! :arrow_upper_right:


rules/sdk: permit map copying in G705

This change permits map copies of the form:
for k, v := range from {
    to[k] = v
}

It doesn't currently permit the alternative, which trickier to check for and doesn't really have any benefits:
for k := range from {
  to[k] = from[k]
}

Updates #24

Codecov Report

Merging #28 (f98c197) into master (f6f1167) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #28   +/-   ##
=======================================
  Coverage   70.86%   70.86%
=======================================
  Files           9        9
  Lines         587      587
=======================================
  Hits          416      416
  Misses        146      146
  Partials       25       25

Impacted Files
Coverage Δ

analyzer.go
89.02% <ø> (ø)

Continue to review full report at Codecov.

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


Add documentation to hover

Old version:

New version (including clickable link if docs contains URL):

Nice! I guess the experience from Ionide is that the larger tooltips aren't obtrusive? I've seen that mentioned as an issue in the past but I think at least vscode's  hover  UI is smooth enough for it to be a non-issue


util/release: Deference device names when updating EC2 manifest

Fixes a bug introduced by switching to aws-sdk-go inadvertently.

LGTM

LGTM


alo

Alo there are some problems with this zalupa. It doesn't work at all, when I enter I see ebalo on the background and the app says that something goes wrong and i don't have internet connection. BUT I HAVE INTERNET CONNECTION WTF bLYA. Please fix it and

hellooo, nice to meet you too. its ok, that app doesn't work. possible solutions-

Try to stop watching anime
Try to stop sitting near Eldar
Try to remove toolcad and don't use it
Hope this will help you. see ya later 💯

Helo brother my name is Nice to meet you, really useful adviceS, really want to try it. And if we are talking about anime, I like to watch garem, like: obshaga bogindan and the same. About Eldar, he really zaebal(annoys)  me because ti kokos and he oret every minute. Don't know what to talk about the last advice, because i don't want to delete/ Have a nice trip, see you Russia

okau, i wanna kushat, so i don't want to talk with you anymore. see ya in Fanil2

[ ] anime
[ ] crfhcjjjkkkk
i am going to close this isue

eeeeeeeeeeeeeee, why u closed this i don't know how to call it. It was really nice to talk with u 2day Vrother, and i wanna to kushat' 2/ bye


chore: update package-lock.json version

Coverage remained the same at 100.0% when pulling 0f98c45326534a3158a1a2817f9ac0ad9dbd0bbb on update-pacakge-lock-version into a7dac83a857549ce4f50a34b8a9d0b2e0ee4fe56 on main.

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

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


The example fails to compile.

The whole error is:
examples/hello-world.rs:29:38: 29:51 error: type `core::option::Option<rustbox::EventErrorKind::Error>` does not implement any method in scope named `description`
examples/hello-world.rs:29             Err(e) => panic!("{}", e.description()),
                                                                ^~~~~~~~~~~~~
note: in expansion of format_args!
<std macros>:9:1: 9:40 note: expansion site
<std macros>:1:1: 11:23 note: in expansion of panic!
examples/hello-world.rs:29:23: 29:52 note: expansion site
error: aborting due to previous error
Could not compile `rustbox`.

which can be temporarily fixed by:
diff --git a/examples/hello-world.rs b/examples/hello-world.rs
index d4b65e6..52a52ce 100644
--- a/examples/hello-world.rs
+++ b/examples/hello-world.rs
@@ -1,8 +1,5 @@
-#![feature(core)]
-
 extern crate rustbox;

-use std::error::Error;
 use std::default::Default;

 use rustbox::{Color, RustBox};
@@ -26,7 +23,7 @@ fn main() {
                     _ => { }
                 }
             },
-            Err(e) => panic!("{}", e.description()),
+            Err(e) => panic!("{:?}", e),
             _ => { }
         }
     }

using the Debug trait for Option<T>.
The rustc version is: rustc 1.1.0-nightly (c4b23aec4 2015-04-29) (built 2015-04-28)
I have looked into the source, and I have a (or two) question about InitError and InitErrorKind.
Is there rationale behind splitting those two? What is the purpose of #[repr(C, isize)]?
I am fairly new to Rust, but AFAIK #[repr(C)] is only needed if you need interoperability (which is not necessary in this case because Rustbox is currently a wrapper for Termbox).
Can't you just do like this:
#[derive(Debug)]
pub enum InitError {
    BufferStderrFailed(io::Error),
    AlreadyOpen,
    UnsupportedTerminal,
    FailedToOpenTTy,
    PipeTrapError,
    Other(isize),
}

impl fmt::Display for InitError { ... }

impl Error for InitError { ... }

impl FromPrimitive for InitError {
    // you can use `unwrap()` directly because it only returns Some(..)
    fn from_i64(n: i64) -> Option<InitError> {
        match n {
            -1 => Some(InitError::UnsupportedTerminal),
            -2 => Some(InitError::FailedToOpenTTy),
            -3 => Some(InitError::PipeTrapError),
            n => Some(Other(n as isize)),
        }
    }

    // can't convert from unsigned
    fn from_u64(n: u64) -> Option<InitError> {
        None
    }
}

You'd lose the benefit from using the enum_primitive macro, but you can tell the user what unknown error code the termbox gave.
Also, same applies to the EventError and EventErrorKind, which is quite conspicuous with "FIXME" label.

+1


If someone submits a PR, should we invite them as an Observer?

After the last week at Node Interactive, we've discussed a lot around enabling people further.
One thing I'd like to discuss is if there's a first time contributor to the repo, should we automatically invite them to meetings as an observer? Of course there is no requirement to come, but I think it's a good first step to encourage further contributions.

I like the idea, I’d like to try that out

IMHO reaching out with a personal message to the author, welcoming them, thanking for the contrib, and asking them if they would like to join, might have a higher impact.

P.S. This something we are trying out in "core". Also striving to assign a "champion" to each PR, so that the author has a human contact, and someone who is explicitly on their side.
RE: https://github.com/nodejs/node/pull/16016 If it wasn't part of C&L I'd also add a few words about the process (the possible review back-and-forth and 48 hour minimal timeframe).

General consensus was "no" on this, pending some other efforts around Observership. Going to close it for now.


Rename TcbInfoRaw to SignedTcbInfo

Rename TcbInfoRaw to SignedTcbInfo for consistency with
SignedQeIdentity.

Motivation

Current dependencies on/for this PR:

main

PR #119   👈

This comment was auto-generated by Graphite.


Vote container not starting + fix

Description
Vote container not starting. Running latest example-voting-app on up-to-date Docker Desktop on a Mac
Steps to reproduce the issue, if relevant:

git clone latest version
docker-compose up --build -d
docker-compose ps

Describe the results you received:
"docker-compose ps" shows "Exit 1" on vote_1 container. Rest is Up:
$ docker-compose ps
          Name                        Command               State                       Ports
-----------------------------------------------------------------------------------------------------------------
7_microservices_result_1   nodemon server.js                Up       <IP_ADDRESS>:5858->5858/tcp, <IP_ADDRESS>:5001->80/tcp
7_microservices_vote_1     python app.py                    Exit 1
7_microservices_worker_1   /bin/sh -c dotnet src/Work ...   Up
db                         docker-entrypoint.sh postgres    Up       5432/tcp
redis                      docker-entrypoint.sh redis ...   Up       <IP_ADDRESS>:32769->6379/tcp

'docker-compose logs' shows the following error:
OSError: [Errno 8] Exec format error

Describe the results you expected:
Well... Up instead of Exit 1 😎
Additional information you deem important (e.g. issue happens only occasionally):
I've fixed it... see below.
Output of docker version:
Client: Docker Engine - Community
 Version:           18.09.2
 API version:       1.39
 Go version:        go1.10.8
 Git commit:        6247962
 Built:             Sun Feb 10 04:12:39 2019
 OS/Arch:           darwin/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          18.09.2
  API version:      1.39 (minimum version 1.12)
  Go version:       go1.10.6
  Git commit:       6247962
  Built:            Sun Feb 10 04:13:06 2019
  OS/Arch:          linux/amd64
  Experimental:     true

Output of docker info:
Containers: 5
 Running: 5
 Paused: 0
 Stopped: 0
Images: 33
Server Version: 18.09.2
Storage Driver: overlay2
 Backing Filesystem: extfs
 Supports d_type: true
 Native Overlay Diff: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge host ipvlan macvlan null overlay
 Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version:<PHONE_NUMBER>f7fe2f4e74d43e2fc7ccd237edcbce
runc version: 09c8266bf2fcf9519a651b04ae54c967b9ab86ec
init version: fec3683
Security Options:
 seccomp
  Profile: default
Kernel Version: 4.9.125-linuxkit
Operating System: Docker for Mac
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 5.818GiB
Name: linuxkit-025000000001
ID: F4NW:FVGS:ZLTR:PEZA:T625:TSHW:4PB6:XX4C:WOVM:UIGB:TWSE:NYAA
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): true
 File Descriptors: 66
 Goroutines: 83
 System Time: 2019-05-15T21:29:37.0272169Z
 EventsListeners: 2
HTTP Proxy: gateway.docker.internal:3128
HTTPS Proxy: gateway.docker.internal:3129
Registry: https://index.docker.io/v1/
Labels:
Experimental: true
Insecure Registries:
 <IP_ADDRESS>/8
Live Restore Enabled: false
Product License: Community Engine

Additional environment details (AWS, Docker for Mac, Docker for Windows, VirtualBox, physical, etc.):
Docker Desktop on macOS 10.14.4.
The Fix
I've added a 'shebang' to 'example-voting-app/vote/app.py':
#!/usr/bin/env python2.7

Now it runs like expected:
$ docker-compose ps
          Name                        Command               State                      Ports
----------------------------------------------------------------------------------------------------------------
7_microservices_result_1   nodemon server.js                Up      <IP_ADDRESS>:5858->5858/tcp, <IP_ADDRESS>:5001->80/tcp
7_microservices_vote_1     python app.py                    Up      <IP_ADDRESS>:5000->80/tcp
7_microservices_worker_1   /bin/sh -c dotnet src/Work ...   Up
db                         docker-entrypoint.sh postgres    Up      5432/tcp
redis                      docker-entrypoint.sh redis ...   Up      <IP_ADDRESS>:32769->6379/tcp

Strange, I can't seem to reproduce the error on a fresh install.

this should be started with docker stack deploy -c docker-stack.yml app

@ProsperWare : thanks for the reply, but: I was under the impression that you can use any of the common methods to start the application (compose, stack, k8s, etc). So when I have an issue using 'docker compose', saying I need to use 'docker stack deploy' surprises me... especially when the documentation clearly states you can use either method.
Anyway: I had an issue, fixed it, thought I'd share it, but couldn't reproduce it myself on a fresh install. I'll close the case.

I had the same issue on Docker for Windows and I fixed it with two changes:

Add the shebang #!/usr/bin/env python2.7, like @davidem already wrote
Use the Unix style line endings for app.py, see https://stackoverflow.com/a/55272071/4471199

I had the same issue on Docker for Windows and I fixed it with two changes:

Add the shebang #!/usr/bin/env python2.7, like @davidem already wrote
Use the Unix style line endings for app.py, see https://stackoverflow.com/a/55272071/4471199

I'm unable to fix my setup, I've converted windows style line ending to unix style line ending, and added
#!/usr/bin/env python2.7
to the head of my app.py, but the container failed to boot with exit code 127, showing
vote_1    |  * Serving Flask app "app" (lazy loading)\r
vote_1    |  * Environment: production
vote_1    |    WARNING: This is a development server. Do not use it in a production deployment.
vote_1    |    Use a production WSGI server instead.
vote_1    |  * Debug mode: on
vote_1    |  * Running on http://<IP_ADDRESS>:80/ (Press CTRL+C to quit)
vote_1    |  * Restarting with stat
': No such file or directoryte 'python2.7
examplevotingapp_vote_1 exited with code 127

any ideas?

': No such file or directoryte 'python2.7
...
any ideas?

Do you have python 2.7 installed? 😎

': No such file or directoryte 'python2.7
...
any ideas?

Do you have python 2.7 installed? 😎

do I need to install that on the host machine?

do I need to install that on the host machine?
No... strike my comment...
Another option: remove everything and start from scratch. Unless you've made significant changes.

do I need to install that on the host machine?

No... strike my comment...
Another option: remove everything and start from scratch. Unless you've made significant changes.

In the Docker Quickstart Terminal
$ cat vote/app.py
#!/usr/bin/env python2.7

from flask import Flask, render_template, request, make_response, g
from redis import Redis
import os
import socket
import random
import json

I think should add the shebang and make an pull request :smirk:

hmm... looks ok. Strange. And you're using the original Dockerfile to build 'vote'? I mean: it 's still using python:2.7-alpine?

hmm... looks ok. Strange. And you're using the original Dockerfile to build 'vote'? I mean: it 's still using python:2.7-alpine?

Yes... I did not change the Dockerfile, more strangly, if I compile and build it as an single image, it runs smoothly without any warning. even with the shebang removed, I think it is an docker-compose issue.


adds reviewer on pending_change index

Should we add tests for pending_view_test module?

:thinking: I don't think so. This just shows who reviewed this pending change. I probably have to change this so that it won't show up if the pending change is, well, pending

Ah ha! Nevermind. I see how we updated these pages.


Update README.md of Sorting in all languages

Features

A brief on all the types of sorting algorithms present.
A comparison of time complexity and space complexity of all.
Written in all 4 languages.

I would like to work on this issue. Can you please assign it to me under SSoC '23 ?
Thank You :)

Sounds great!!

i want to contribute

Assigned!
@harshita-kaushik2 : Documentation

@Kumar-laxmi
Features I will add to the documentation
Algorithm Overview
Pseudocode
Implementation Examples
Performance Analysis
Visualizations
Advantages and Limitations
Use Cases
Complexity Comparison
in all 4 languages
Please provide me this opportunity can you assign it to me under ssoc'23
thank you


Language picker showing English when localized on first load

Describe the bug
On first page load shows English in the language picker even when the page is localized
To Reproduce
Steps to reproduce the behavior:

Clear the i18nextLng variable from local storage if you have already been on the page
Set browser language to some supported language
Open the page
See the page in the selected language but English selected on the picker

Expected behavior
The language picker should show the currently localized language
Screenshots

What device are you on?
Windows 10 running Firefox 86.0.1 (64bit)

Duplicate of https://github.com/benawad/dogehouse/issues/1427


fix(ci): PR description frontend link

Whoops...  This time I really fixed PR links.  Honest!

Thanks for the PR!
Deployments, as required, will be available below:

Frontend
Backend
Oracle-API

Please create PRs in draft mode.  Mark as ready to enable:

Analysis Workflow

After merge, new images are deployed in:

Merge Workflow

Thanks for the PR!
Deployments, as required, will be available below:

Frontend
Backend
Oracle-API

Please create PRs in draft mode.  Mark as ready to enable:

Analysis Workflow

After merge, new images are deployed in:

Merge Workflow

Approved! 💯 🥇 ✅ Thanks @DerekRoberts


raw.flattenPath equivalent

First of all great substitute for contentlayer thank you for that.
I am testing out  velite by migrating a contentlayer project.
In contentlayer my slugs were based on the filepath. For a nested MDX file in e.g. content/firstfolder/secondfolder/test.mdx that meant the slug would be /firstfolder/secondfolder/test
To achieve that in contentlayer we had raw.flattenedPath like
const computedFields: ComputedFields = {
  slug: {
    type: "string",
    resolve: (doc) => `/${doc._raw.flattenedPath}`,
  },

I did read the velite documentation but how would that be achieved in velite?
I understand you can either use .transform for collection based computed fields or prepare for all collections.
If there is a solutions to this might consider adding it to the docs
Thank you

Answering my own Question:
There is a context object  as an argument within transform:
 schema: s
        .object({
          title: s.string().max(99),
          ...

        })
        .transform((data, ctx) => ({ ...data,
          // computed fields
          permalink: `/${data.slug}`,
          fileInfo: ctx.meta.file.path,
          fileInfo2: ctx.meta.file.basename,
          fileInfo3: ctx.meta.file.dirname,
          fileInfo4: ctx.meta.file.extname,

        }))

Still suggesting to add an example to the docs for "file based slugs" so folks migrating from contentlayer have it easier

Yup, but it is recommended to use file.stem, which is more similar to flattenedPath.
refer to VFile.stem for more details.

path: s.path()
// => flattened path, e.g. 'posts/2021-01-01-hello-world'

https://velite.js.org/guide/velite-schemas#s-path


⚠ Bofrost.de has degraded performance

In 2033362, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1026 ms

Resolved: Bofrost.de performance has improved in ad1610b.


vm: more defense against multi-faulting

Clear faulting_p from a safepoint rather than inside general_error, because jumping into unwind-native-frames could blow up.
Handle multiple faults from fatal_error by breakpointing. Is there anything else we can safely do at that point?
Verify memory protection faults in the top half of the signal handlers because signal dispatch could fault. Treat memory faults during gc or fep as fatal errors.
Add a function factor_vm::abort() that restores the default SIGABRT handler and ::abort()s. Use it from fatal_error() so we get useful context from gdb and so the user gets feedback from the system crash reporter that Factor blew up and didn't just disappear.
In factorbug(), don't proceed with .s .r .c if it would be unsafe to do so.
Don't pile on signals if we've already called fatal_error().

Merged. @slavapestov, I'll take a look and clean those up.


HTML headings instead of  String

This is the good package for export and import. We can add headers to the excel as of now string format. As we pass data from view to export can we pass the headers data as well from view?
Here is an example.
class ExportSheet implements FromArray, WithTitle
{
	private $columnOffset;
	private $headers = array();
	private $rows = array();

	public function __construct($rows,$headers = array(), $columnOffset = 4)
	{
		$this->headers = $headers;
		$this->columnOffset = $columnOffset;
		$this->rows = $rows;
	}

	public function array(): array
	{
		return $this->rows;
	}

	public function headings(): array
    {
    	$header1 = view('Exporter.header1', ['headerRows' => $this->headers, 'columnOffset' => $this->columnOffset])->__toString();
    	$header2= view('Exporter.header2', ['headerRows' => $this->headers, 'columnOffset' => $this->columnOffset])->__toString();
    	$header3 = view('Exporter.header3', ['headerRows' => $this->headers, 'columnOffset' => $this->columnOffset])->__toString();
    	$header4 = view('Exporter.header4', ['he
![c1](https://user-images.githubusercontent.com/28619068/47290565-ba223600-d61d-11e8-8f23-79c59ed669f5.png)
aderRows' => $this->headers, 'columnOffset' => $this->columnOffset])->__toString();

        return [
        	$header1,
        	$header2,
        	$header3,
        	$header4
        ];
        // return [
        //     '#',
        //     'Date',
        // ];
    }

    /**
     * @return string
     */
    public function title(): string
    {
        return "Export";
    }
}

I am trying it with multiple sheets. I can see the data in the exported sheet but not the headings that I have added.  Kindly find the format of the header I am trying to generate.

(Column names are strike though that doest need in the final export )

Prerequisites

[ ] Able to reproduce the behaviour outside of your code, the problem is isolated to Laravel Excel.
[ ] Checked that your issue isn't already filed.
[ ] Checked if no PR was submitted that fixes this problem.

Versions

PHP version:
Laravel version:
Package version:

Description

Steps to Reproduce

Expected behavior:

Actual behavior:

Additional Information
Any additional information, configuration or data that might be necessary to reproduce the issue.

Closing issue as I have found the solution. Actually, those were not the headers those are the content of excel. Thank you.


Added two c files

Added fractional knapsack and activity selection problem of greedy algorithm. Glad to help you.
Looking forward to your acceptance of PR.

will make some changes and reopen the PR again