Propose to support building and testing Accumulo on ARM64 platform

Is your feature request related to a problem? Please describe.
Currently, there are many softwares have support running on ARM64 platform. We have also done many efforts about making big-data projects support ARM64 platform.
For an example, Hadoop has published ARM64 platform specific packages:
https://www.apache.org/dyn/closer.cgi/hadoop/common/hadoop-3.3.0/hadoop-3.3.0-aarch64.tar.gz
and also have ARM specific CI job configured:
https://ci-hadoop.apache.org/job/Hive-trunk-linux-ARM/
It would be better also to enable Accumulo support ARM64 platform
Describe the solution you'd like

Try to make Accumulo can sucessfully build on ARM64 server
Try to run Accumulo on ARM64 server and make all the test cases passed
Add ARM specific CI jobs to guarantee ARM platform support in development.

Describe alternatives you've considered
N/A
Additional context
N/A

@liusheng While most users probably deploy Accumulo on x86_64 servers, Accumulo doesn't do a lot that could be considered architecture dependent, so we're probably not aware of any specific problems on ARM64 or other architectures.
Are you aware of any specific problems with building or running Accumulo on ARM64? If not, I'm not sure what there is to do be done here. If you are aware of such problems, it would be good to create specific bug reports or PRs for each problem.
If you'd like to discuss ARM64 support with other users who may be interested in that, I encourage you to discuss it on our user mailing list. If it becomes necessary to discuss large changes to support ARM64 (for smaller changes, a PR is fine), that discussion would be appropriate for our dev mailing list. Information about both mailing lists can be found at https://accumulo.apache.org/contact-us
Regarding the proposed work to run test cases and CI jobs on ARM64, I think it might be a little premature to devote effort into that, since we're a relatively small community compared to Hadoop and it's not yet clear there is a significant interest or volunteers available to perform that work.

@liusheng While most users probably deploy Accumulo on x86_64 servers, Accumulo doesn't do a lot that could be considered architecture dependent, so we're probably not aware of any specific problems on ARM64 or other architectures.
Are you aware of any specific problems with building or running Accumulo on ARM64? If not, I'm not sure what there is to do be done here. If you are aware of such problems, it would be good to create specific bug reports or PRs for each problem.
If you'd like to discuss ARM64 support with other users who may be interested in that, I encourage you to discuss it on our user mailing list. If it becomes necessary to discuss large changes to support ARM64 (for smaller changes, a PR is fine), that discussion would be appropriate for our dev mailing list. Information about both mailing lists can be found at https://accumulo.apache.org/contact-us
Regarding the proposed work to run test cases and CI jobs on ARM64, I think it might be a little premature to devote effort into that, since we're a relatively small community compared to Hadoop and it's not yet clear there is a significant interest or volunteers available to perform that work.

+1 to add CI on ARM64!
@ctubbsii Accumulo is coded mostly in Java but still there is server/native that produces a .so (Linux native library). I have built Accumulo on ARM64 hardware and there is no problem, but with a CI we could be sure that there are no regressions.
Also, in the past I've had problems with third party dependencies like Protobuf-Java and Brotli. That is, the project itself is platform independent but some of the dependencies may lead to problems.
Accumulo uses GitHub Actions and there is no support for ARM64 there yet (it is planned for Q1 2021 though) but you may use TravisCI just for testing on ARM64 (and PPC64, s390x). If you like the idea I'd be happy to provide a Pull Request!

Accumulo uses GitHub Actions and there is no support for ARM64 there yet (it is planned for Q1 2021 though) but you may use TravisCI just for testing on ARM64 (and PPC64, s390x). If you like the idea I'd be happy to provide a Pull Request!

TravisCI was previously used, but we discontinued that for several reasons. If support for these are coming in Q1 2021, then I would prefer we wait until then to add testing for other arches, rather than reintroduce TravisCI.

Hi @ctubbsii Sorry for reply lately,  thanks for @gancho-ivanov help clarified. Like other Java projects, Hadoop, Spark, Most code of Accumulo can be directly built and run on ARM64 platform, but there is also native code that produces a .so (Linux native library) with is architecture sensitive, it is better to add ARM CI to ensure ARM platform support for future development. As mentioned, the ARM64 release is planed in Github Action in Q1 2021, let's wait and then configure ARM CI with github action.
Thank you!

Unfortunately GitHub Actions postponed the addition of Linux ARM64 runner nodes for later. Not clear when that could be.
Recently I've written a blog about how to run GitHub Action jobs on ARM64 at Huawei Cloud: https://martin-grigorov.medium.com/githubactions-build-and-test-on-huaweicloud-arm64-af9d5c97b766.
But honestly, in my opinion using TravisCI or CircleCI is the easiest! Few other Apache projects recently re-introduced TravisCI for testing on Linux ARM64 and s390x: Parquet, Drill, Tomcat & Wicket.

Using TravisCI or CircleCI requires additional user registration and privileges to manage builds, so I'm not comfortable doing that myself, and would prefer to avoid it. If some other PMC member wanted to do that, I wouldn't be opposed, so long as it didn't increase the burden on the other active PMC/committers to maintain. I'd be opposed to using something like Huawei Cloud, or anything else that requires storing credentials to a third party service in the repo settings, as that's a lot more work to manage, and harder for the PMC to secure and protect as a collective, often requiring interaction with ASF INFRA to maintain and update, and much harder to self-service. Every 3rd party GitHub action, like huaweicloud/cce-cluster-credentials@v1 would also require INFRA approval, since they have a curated allow-list, for security and project safety.
Aside from security using 3rd-party services, my main concern is the disproportionate work required to maintain a workflow that has marginal value to the Accumulo community. I wouldn't want us to spend more time and effort on maintaining a CI workflow than the value the community gets from having support for those architectures.
If there is a small community of ARM64 or s390x users that would benefit from having Accumulo support those, another option is for that community to run CI on their own against the public repo, and report back bugs they find. If that community grows sufficiently to warrant a bigger investment of time/effort from the PMC to maintain CI for those architectures. Currently, given the lack of bugs being reported that are specific to s390x/ARM64, my personal opinion is that there isn't sufficient interest or risk of problems to warrant the effort at this time.

At https://martin-grigorov.medium.com/github-actions-arm64-runner-on-oracle-cloud-a77cdf7a325a I've explained how to use GitHub Actions self-hosted ARM64 runners on Oracle Cloud for free.
Again you will need to create an account at OracleCloud to be able to create the VM but apart from that the build setup would be the same as now. ASF Infra help is needed only to get the token for ./config.sh step and to setup the security.
Let me know if you are interested in this approach and if you need any kind of help!

It looks like ARM64 GitHub ActionRunners are coming soon.
https://github.blog/news-insights/product-news/arm64-on-github-actions-powering-faster-more-efficient-build-systems/


No output from keyd devices when convertible laptop in tablet mode

Device: Thinkpad X1 Yoga (Gen 6)
GNOME 42.4, Wayland
Keyd versions: Tried 2.4.2 and from latest commit
Most 2-in-1 devices automatically disable the internal keyboard when "flipped", but when keyd is running, external (USB and wireless) keyboards specified in the configuration file also stop working.
Keystrokes show up in keyd's monitor mode as from keyd virtual keyboard but not in any applications or libinput debug-events until either keyd is stopped, or the device is returned to laptop mode.
After some digging around, this behaviour seems to be an unintended consequence of this line:
https://github.com/rvaiya/keyd/blob/c1ba867e6fcb9a175227bafa87cf57957ce28816/keyd.quirks#L4
Changing internal to external and rebooting seemed to fix it for me, though not sure if that's the most appropriate solution in keyd.

This appears to be the opposite of #66. I probably should have gone with my initial instinct and left this up to the user (i.e not shipped a quirks file).
@canadaduane How do you feel about this?

This is a bit tricky, as the "internal" designation allows keyboard & touchpad to coordinate, but it's really just a happy side-effect. I wish there were a better way for a virtual keyboard to "pair" with a touchpad. Perhaps we should ask @whot for guidance. He may know of a more explicit way to tell libinput to allow a virtual keyboard to inherit this pairing?

The fundamental problem is that the virtual device created by keyd is conceptually neither an internal keyboard nor an external one. There is no reason to treat it as one or the other, since it may well subsume both. The correct thing to do is likely to just make the user aware of this and let them handle it accordingly.

Right, I think we're agreeing but I'm suggesting there may be a better outcome if we go one step further and (if necessary) influence the udev or libinput standards to include a way for keyd to communicate this edge case. If there's a way for it to "do the right thing" for people without requiring manual intervention this would be a win (especially in the case of a laptop, which I wouldn't say is unusual).
For example: what if we could add an attribute to the udev system for the real keyboard (e.g. E: DWT_PAIR=/dev/input/event6) that suggests the device (keyboard) be "paired" with the touchpad for "Disable While Typing". Then, when keyd comes along and sees this attribute, it could add it to the udev system for the virtual keyboard. Finally, if libinput were modified to understand this pairing suggestion, it could "do the right thing" without a special local quirks file.

I believe that would require cross distro coordination (or maybe just systemd cooperation?). I assume the reason libinput ships with a bunch of quarks files rather than exclusively relying on udev properties is because this is difficult to achieve in practice.
There also remains the issue that keyd presents as a single virtual device which must either be treated as an integrated or external device. A simpler solution would be to create a dedicated virtual device for each input device which mirrors its properties, but that has other implications. Finally, udev has been deliberately excised from the code for portability reasons.
As far as I can see, there isn't a good or easy solution to this problem, but I should like to be proven wrong :).

The immediate workaround should be to add ModelTabletModeNoSuspend=1 to the quirks. That tells libinput that this device must not be suspended in tablet mode.
As for the rest - yes, the problem is very much that libinput is a hardware abstraction stack. Software devices make things difficult since we can't use any heuristics and/or our existing heuristics break. There's no good solution here I can see, adding a "random" set of configuration options to libinput (via udev or whatever) won't really fix the problem because the next use-case will have some different requirement. So we'll end up with lots of configurations that all do one niche thing, likely conflict with each other. And, the biggest concern (for me :smile:) it will push the testing effort of all the combinations onto libinput.

From the input tsar himself (big fan btw :P)! I suppose that settles the question. I've stopped shipping the quirks file and am closing the issue for now.

Just as a closing comment: we've been working on libei for quite a while now and most of the pieces are slowly falling into place. Unlike libinput which is a hardware stack, libei is a software input stack. Or,  to be more precise, it's a transport layer for logical input events.  How that click is generated is up to you as the sender.
The motivation for libei are two applications, xdotool and InputLeap (formerly barrier, formerly synergy). keyd may be a fit as well although libei's integration into the compositor is very specifically aimed at applications sending events, so it doesn't have the "always works" guarantees you'd get by running as root and injecting via uinput. And of course it depends on the compositor actually supporting libei.

Just as a closing comment: we've been working on libei for quite a while now
and most of the pieces are slowly falling into place. Unlike libinput which is
a hardware stack, libei is a software input stack. Or, to be more precise, it's
a transport layer for logical input events.
How that click is generated is up to you as the sender.

Great :). I haven't had a chance to look through the API yet, but keyd would also need the ability to grab the existing input devices. Is this something that would be supported? How does the project compare to experimental wayland protocols like virtual-keyboard-unstable-v1?
keyd is designed to support multiple backends (I have macos and windows prototypes sitting in a private repo), and I would certainly be interested in supporting a rootless version which can take advantage of display server input mechanisms.

but keyd would also need the ability to grab the existing input devices. Is this something that would be supported?

completely unrelated to libei which doesn't care about how you (keyd) generate the emulated input events. so there's no direct support but you can do it yourself. best summary is that libei replaces all the uinput parts in keyd, but nothing else.

virtual-keyboard-unstable-v1

there's large overlap here, the difference is in design philosophy. libei is designed to allow applications to run via flatpak/portals. This isn't doable, or at least not easily, via a wayland protocol. so yes, very much a case of two competing standards and neither will be supported by all compositors (GNOME won't have virtual keyboard, sway won't have libei).

keyd is designed to support multiple backends

in that case you can probably (without knowing the code) add a libei backend in addition to the uinput one and re-use everything else, so integration should be fairly easy.


Design Invite/Share/Bookmark functionality

To be able to invite or share a pixel / activity / view of the canvas with another user

Suggestion: Add coordinates or alias mechanism to URL to facilitate players to find the game on PixeLAW
https://discord.com/channels/1134242024409792525/1134242025290600450/1186220331921326110


KAFKA-7320: Add consumer configuration to disable auto topic creation

Implements KIP-361 to provide a consumer configuration to specify whether subscribing or assigning a non-existent topic would result in it being automatically created or not.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

Retest this please

Retest this please

Retest this please

Retest this please

Failures seem unrelated, retest this please

One thing we might want to reconsider. If allow.auto.create.topics is set to true, then the consumer will see a fatal error if connecting to an older broker. That means we probably will never be able to make it the default value even though 99% of the time, it's probably the behavior users expect.
One option might be to change the config to be auto.create.topics.policy so that we could have several options. For example, "allowed", "forbidden", and "discouraged." I'm sure we can think of better names.

Retest this please

retest this please

@dhruvilshah3 The test failures appear to be likely related. Can you take a look?

Build is no longer available. :( Retest this please.


Version 0.9.59

The problem
This is not a big issue but with newest version some automations need some attention.
Before it was

service: easee.set_circuit_dynamic_limit
data:
currentP1: 16
currentP2: 16
currentP3: 16

Now it bust be

service: easee.set_circuit_dynamic_limit
data:
current_p1: 16
current_p2: 16
current_p3: 16
Regards Mats

Version of Easee integration having the issue?
0.9.59
Version of Home Assistant Core having the issue?
2024.5.3
Anything in the logs that might be useful for us?
No response
Additional information
No response

That is intentional, it is changed because it was necessary to get better translation support. See also the release notes.

No problem i fixed mine already it was more of an heads up for everyone. Missed it I realease note.


RND-345 - Remove hard coded tokens from http test files

Also added an existence check to update, so that an error response is returned when you try to insert on an update

I left the hardcoded tokens in the token http file that were there to show the response from bad tokens, since we can't replicate that with a call to the oauth endpoint


nixos/systemd: provision a systemd-coredump user

systemd-coredump tries to drop privileges to a systemd-coredump user if
present (and falls back to the root user if it's not available).
Create that user, and recycle uid 151 for it. We don't really care about
the gid.
Fixes https://github.com/NixOS/nixpkgs/issues/120803.
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/)
21.11 Release Notes (or backporting 21.05 Relase notes)

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

[ ] Fits CONTRIBUTING.md.

Will this not create files owned by nogroup?

Will this not create files owned by nogroup?

Which files and where?

Will this not create files owned by nogroup?

Which files and where?

I don't know, but systemd-coredump(8) documents that It may also save the core dump for later processing. I'm worried that those files will be owned by group nogroup.

I gave this PR a spin, and the complaints about the missing systemd-coredump user are gone:
Jul 30 15:07:05 tp systemd[1]: Started Process Core Dump (PID 1015734/UID 0).
Jul 30 15:07:05 tp systemd-coredump[1015735]: [🡕] Process 1015733 (foo) of user 0 dumped core.
Jul 30 15:07:05 tp sudo[1015732]: pam_unix(sudo:session): session closed for user root
Jul 30 15:07:05 tp systemd[1]<EMAIL_ADDRESS>Succeeded.

The systemd-coredump user has a home directory of /var/empty, and after dumping core, there's no files.
The files in /var/lib/systemd/coredump are only owned by root.
I think this is fine (?)

Let's get this in - we can still add another group if we really have to.


evaluation of the class

Left my evaluation of the class.

Thank you for coming, and thank you for the feedback!


Adding License info & link to original github

Type: Missing
Summary:
Adding License info & link to original github
Details:
Adding License info & link to original github which contains the license info
Resolution:
Adding License info & link to original github which contains the license info
Affected definitions:

AspNetPager 7.5.1

The license for this component:     Apache 2.0
A url to the license for this component;     https://github.com/Webdiyer/AspNetPager/blob/master/LICENSE


Building nested items containing SortedSets fails with Guava on the classpath

With Guava on the class path, the following fails in 1.14.5. The SortedSet in LostComparator_ItemHolder_Builder gets re-created without its comparator set in the clearItems() method; this results in downstream exception when trying to sort the items by their (nonexistent) natural ordering.
  public static void main(String[] args) {
    final Item item = new Item.Builder()
        .name("foo")
        .build();

    final ItemHolder itemHolder = new ItemHolder.Builder()
        .addAllItems(Collections.singleton(item))
        .build();

    final Container container = new Container.Builder()
        .itemHolder(itemHolder) // throws exception
        .build();

    System.out.println("successfully created container: " + container);
  }

  @FreeBuilder
  public interface Item {
    String name();
    class Builder extends LostComparator_Item_Builder {
    }
  }

  @FreeBuilder
  public interface ItemHolder {
    SortedSet<Item> items();
    class Builder extends LostComparator_ItemHolder_Builder {
      Builder() {
        setComparatorForItems(Comparator.comparing(Item::name));
      }
    }
  }

  @FreeBuilder
  public interface Container {
    ItemHolder itemHolder();
    class Builder extends LostComparator_Container_Builder {
    }
  }

Full working example and pom file are available here

You should be able to pick this up in v1.14.6, @chrisrhut. Let me know if it fixes it for you!

Working great! Thanks again @chrisalice for the quick response! 😺


CI: RuntimeValidatedKafka: Cannot set default policy enforcement on target 'runtime'

https://jenkins.cilium.io/job/Cilium-PR-Ginkgo-Tests-Validated/4675/consoleFull
21:20:34 [Runtime] • Failure in Spec Setup (BeforeEach) [554.342 seconds]
21:20:34 [Runtime] RuntimeValidatedKafka
21:20:34 [Runtime] /home/jenkins/workspace/Cilium-PR-Ginkgo-Tests-Validated/src/github.com/cilium/cilium/test/ginkgo-ext/scopes.go:344
21:20:34 [Runtime]   Kafka Policy Ingress [BeforeEach]
21:20:34 [Runtime]   /home/jenkins/workspace/Cilium-PR-Ginkgo-Tests-Validated/src/github.com/cilium/cilium/test/ginkgo-ext/scopes.go:376
21:20:34 [Runtime]
21:20:34 [Runtime]   Cannot set default policy enforcement on target 'runtime'

9acb0442_RuntimeValidatedKafka_Kafka_Policy_Ingress.zip

I think it will be very helpful to have a common helper for CmdRes which:

Checks for success
prints the original command executed
prints stderr and stdout nicely on error with a summary message provided by the caller

Already in there:
https://github.com/cilium/cilium/blob/036982fa8ce403edf90ae98c6a494085b441e46d/test/helpers/cmd.go#L79-L90

2 & 3) Already in there:
https://github.com/cilium/cilium/blob/036982fa8ce403edf90ae98c6a494085b441e46d/test/helpers/cmd.go#L206-L222
Example:
/home/jenkins/workspace/Cilium-PR-Ginkgo-Tests-Validated/src/github.com/cilium/cilium/test/ginkgo-ext/scopes.go:376
"app1" can http request to Public
Expected command: docker exec -i  app1 curl -s -D /dev/stderr --fail --connect-timeout 1 --max-time 1 http://<IP_ADDRESS>/public -H 'X-Test: True' -X POST
To succeed, but it failed:
Exitcode: 28
Stdout:

Stderr:

/home/jenkins/workspace/Cilium-PR-Ginkgo-Tests-Validated/src/github.com/cilium/cilium/test/runtime/Policies.go:928

Where that info show:
Assert message: "app1" can http request to Public
Command: Expected command: docker exec -i  app1 curl -s -D /dev/stderr --fail --connect-timeout 1 --max-time 1 http://<IP_ADDRESS>/public -H 'X-Test: True' -X POST
What is expected: To succeed, but it failed:
Following by ExitCode, stdout and stderr
Finally you have where the test has been failed:
/home/jenkins/workspace/Cilium-PR-Ginkgo-Tests-Validated/src/github.com/cilium/cilium/test/runtime/Policies.go:928

Regards

OK, then it's consistent use of it that is lacking. I see several different constructs:
        res := s.ExecCilium("bpf lb list -o json")
        if !res.WasSuccessful() {
                return nil, fmt.Errorf("cannot get bpf lb list: %s", res.CombineOutput())
        }

        res := node.SetPolicyEnforcement(PolicyEnforcementDefault)
        if !res.WasSuccessful() {
                ginkgo.Fail(fmt.Sprintf(
                        "Cannot set default policy enforcement on target '%s'",
                        target), 1)
                return nil
        }

        if res.SingleOut() == value {
                logger.Debugf("no need to update %s=%s; value already set", option, value)
                return res.WasSuccessful()
        }

There is a lot of open coded code around error handling which provides very minimal context of the failure even though we typically have everything right there.

I'm against that, for one single reason, that code is all from helpers, and helpers IMHO should not make any assertion, because in one test you want to FAIL and another test should be success, for me this helpers are Factory builders.
If one helper returns true/false and something fails within that, that helper is not correctly writing. In this case, I'm not sure why, but we change the cilium config when we connect to the runtime box, that should be part of the test itself, or at least be like something like this:
https://github.com/cilium/cilium/blob/master/test/k8sT/assertionHelpers.go#L23-L35
Regards.

About the task itself, Build failed because cilium not even starts:
time="2018-07-04T21:18:26Z" level=debug msg="running command: ls /tmp/"
cmd: "ls /tmp/" exitCode: 0 stdout:
hsperfdata_vagrant
provision
vagrant-shell

time="2018-07-04T21:18:27Z" level=debug msg="running command: sudo cp /vagrant/cilium /etc/sysconfig/cilium"
cmd: "sudo cp /vagrant/cilium /etc/sysconfig/cilium" exitCode: 0 stdout:

time="2018-07-04T21:18:27Z" level=debug msg="running command: sudo systemctl restart cilium"
cmd: "sudo systemctl restart cilium" exitCode: 0 stdout:

time="2018-07-04T21:18:27Z" level=info msg="Vagrant: running command 'vagrant ssh-config runtime'"
time="2018-07-04T21:18:28Z" level=debug msg="generated SSHConfig for node runtime"
time="2018-07-04T21:18:28Z" level=debug msg="done importing ssh config"
time="2018-07-04T21:18:28Z" level=debug msg="running command: ls /tmp/"
cmd: "ls /tmp/" exitCode: 0 stdout:
hsperfdata_vagrant
provision
raw_main-29b29b.o-38dc3ae7
tmp.EmogbhSZkB
vagrant-shell

time="2018-07-04T21:18:28Z" level=debug msg="running command: sudo cilium status"
c

And timeout after a while. It was a PR and it was not master.

I'm against that, for one single reason, that code is all from helpers, and helpers IMHO should not make any assertion, because in one test you want to FAIL and another test should be success, for me this helpers are Factory builders.

Then let's have a wrapper around it that can be used in all scenarios where command execution failure means test failure. If we would see the actual stderr error from the command, it will have been obvious that the Cilium API is not up.
We need to get away from requiring to dig into the logs for every single test failure. If I know that Cilium API could not be reached then I will immediately start digging into the cilium logs themselves.

Fixed by:
https://github.com/cilium/cilium/pull/4770


Can't change the next button text color

The Next button text color is white, and the background is also white.
i can't find a way to change the text color to black

Refer #32


Fix getrawtransaction

Fixes a small bug in rawtransactions/getrawtransaction endpoint. The GET verbose query parameter was always being set to true, even when set to false. This PR fixes that.

Pull Request Test Coverage Report for Build 944

0 of 0   changed or added relevant lines in 0 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.04%) to 77.543%

Files with Coverage Reduction
New Missed Lines
%

dist/routes/v2/rawtransactions.js
1
75.43%

Totals

Change from base Build 940:
-0.04%

Covered Lines:
2507

Relevant Lines:
3054

💛  - Coveralls


Exclude all files and directories except specifics in vscode

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

VS Code Version: 1.89.1
OS Version: Windows 11

I want to exclude everything in the explorer window in vscode I have looked at the following posts on stackoverflow, but I simply can't get the syntax to work:
how-to-exclude-all-folders-except-one-folder-in-vscode
how-to-exclude-all-but-certain-files-in-the-sidebar-in-visual-studio-code
I wish to exclude everything except files ending on *_1.pdf. I have the following syntax, which doesn't work:
"files.exclude": {     "manuals/**/*[^_][^1][^.][^p][^d][^f]": true,    }
I have also tried the following:
"files.exclude": {
"manuals/**/*": true,
"manuals/**/*_1.pdf": false,

},
and just about a million other alterations. What am I missing?
Steps to Reproduce:

Create vscode workspace
directory should include a bunch of files
Add the following code to .vscode/settings.json: {  "files.exclude": {      "*": true,      "*.py": false,  } }
Everything is now gone from the explorer window.

Looks like duplicate of #869


feat(common): allow hooking into mudTransportObserver requests

Adds an onRequest option to mudTransportObserver, so we can hook into transport requests in a generic way.

this might be better suited/easier to use as a hook inside createContract


A11y_AzureDataStudio_Connect to a SQL Server_Focus Visible: Focus not visible for connection icon while using keyboard

GitHub Tags:
#A11yMAS; #A11yTCS; #A11ySev3; #DesktopApp; #BM-AzureDataStudio-Win32-Feb2022; #Azure Data Studio; #WCAG2.4.7; #Win32; #AINotInScope; #Focus Visible;
Environment Details:
Windows Version :Windows 11 Enterprise
Application name :Azure Data studio
Repro Steps:

Launch Azure Data Studio.
Select the Connections icon (if not already selected) from left bar.
Verify the focus visible for connection icon or not by using keyboard

Note:
Similar issue occurred for Notebook icon
Actual Result:
Focus not visible for connection icon while using keyboard
Expected Result:
Focus should visible for connection icon while using keyboard
Attachment:

Verified in the latest Environment
Azure Data studio Version: 1.37.0
Issue is Fixed.


Add Form component

Moving this POC from #398 into a draft PR for discussion.
This PR adds a new Form component, based on RAC Form. An example instance and documentation page in Storybook is also included.
The Form component is intended to be used as a wrapper around other components, to provide additional support for data validation and submission and form styling. It renders an HTML <form> element.
By default, the Form component renders without any styling of its own. The className prop can be used to style the form as a whole.
Some boilerplate CSS is included (see Form.css). This is currently only used to style the example form in Storybook.

Did a rebase, thought better of it. Cherry-picked work from this branch into #409 instead. Closing this draft PR.


Fill Battle Tutorial issue

In the T2D 3.0 there is
ButtonBehavior::onTouchUp
...
while (%stackObject.len > 0)
However the T2D 2.0
function ButtonBehavior::onTouchUp
....
while (%locStack.len > 0)
....
Should the version 3.0 being using %locStack instread?
Using the 3.0 code, every time I click on a colour it goes into any infinity loop?
Also what is the purpose of %counter in the 3.0 version?

Hello,
Sorry for the confusion – since 3.0 has been out for so long now, this tutorial should have been updated to get rid of the 2.0 code. The difference has to do with ScriptObjects.
In the 2.0 code, the actual ScriptObject is assigned to the local variable %locStack.
In the 3.0 code, the ScriptObject is assigned to the local variable %stackObject. The %locStack variable gets used for a behavior instance attached to %stackObject. In the stack behavior that is created in step 3, the len field is assigned to the owner of this behavior, and not the behavior itself. So the len field ends up on %stackObject.
The 2.0 code is in some ways a bit simpler since it doesn’t deal with behaviors – the stack methods (and the len field) are assigned to the ScriptObject %locStack via a class.
The endless loops are probably due to an error or typo somewhere in your code. I’ll see if I can find some time to update the tutorial are remove the confusing dual versions in chapter 6, which might help make tracking down the issue a bit easier.
As for %counter, it looks like that is some debug code that I forgot to remove when publishing the tutorial. It has no purpose as shown.

The Fill battle tutorial is becoming increasingly outdated and remains only partially complete. We will likely remove it in the months to come to make room for updated tutorials.  In the meantime it appears that this issue is due to a typo.  I'm closing the issue.


Change input values to environment variables

Update test files and example files with environment variables

Oh dear, I did not mean to cause a code explosion. It looks like the flags are adding much more complexity than they are worth. Sorry about that. Can we get back to something relatively simple? For these little examples, it should be good enough to just notice if any of the environment variables is not defined and print a message listing all the required settings. Same thing in the test files. And in the examples do we need to add tenant options? If so, maybe a single flag is enough instead of separate options for tenant and non-tenant users.

Just making sure.. so, are we getting rid of all flags (-host, -user, etc) and replace it with a single flag that tells us whether it's tenant or regular user (i.e. -isTenant)?

Just making sure.. so, are we getting rid of all flags (-host, -user, etc) and replace it with a single flag that tells us whether it's tenant or regular user (i.e. -isTenant)?

If we need the ability to connect as a tenant user in the example, I would make it an env var rather than a flag.  I'm not sure why the examples need a tenant option, though.
The use of flags seems to have added hundreds of lines of code which kind of overwhelm the examples, so I would eliminate all the flags unless they can be added succinctly.


java.lang.String cannot be cast to com.facebook.react.bridge.ReadableNativeMap

I'm trying to make the following call on android:
await Gigya.send('accounts.notifySocialLogin', {});

But I'm seeing the entire app crash due to this error: java.lang.String cannot be cast to com.facebook.react.bridge.ReadableNativeMap.
ios is working fine.
From what I can tell, the following function should be expecting a string, not a parameter map:
https://github.com/SAP/gigya-react-native-plugin-for-sap-customer-data-cloud/blob/329c26c063b4c69342e522904e8326b814a9d7cd/android/src/main/java/com/sap/gigya_rn_plugin/GigyaSdkWrapper.java#L73-L79
My guess is something more along the lines of:
    void send(String api, String jsonParameters, Promise promise) {
        GigyaSdkRNLogger.log("send: called");
        promiseWrapper.promise = promise;
        gigyaInstance.send(api, mapParams(jsonParameters), new GigyaCallback<GigyaApiResponse>() {

Approved pull request.
Will be added in the next upcoming version.


Schedule a watcher : Need help for the configuration.

Hello,
First of all, many thanks for this Great solution.
I would like for a specific watcher be able to schedule it like this (with 2 periods) : every 5 secs from 8am to 9pm and every 2mns from 9pm to 8am. Does it possible ? Do you have an example please ?
According to this 2 periods, does it possible to have a timestamp value (in the query) per period ?
I mean for the first period : every 5 secs from 8am to 9pm , timestamp from value = now-15m
"body": {         "query": {           "bool": {             "must": [               {                 "term": {                   "provider": "sa2"                 }               },               {                 "range": {                   "timestamp": {                     "from": "now-15m"                   }                 }               }             ]           }         },
for the second period : every 2mns from 9pm to 8am , timestamp from value = now-1h
"body": {         "query": {           "bool": {             "must": [               {                 "term": {                   "provider": "sa2"                 }               },               {                 "range": {                   "timestamp": {                     "from": "now-1h"                   }                 }               }             ]           }         },
Any help would be very much appreciated.
Best Regards,
Jérôme.

Hi @jerpic and thanks for using SENTINL!
My suggestion would be to schedule 2 separate watchers, one of each interval, and each with the custom range query you desire. Our presentation and Wiki provide some generic examples you can use for the Intervals.
The later.js syntax does allow for mixing the two intervals, but troubleshooting them might become complex so I wouldn't advice it for new users.
I hope this helps - feel free to comment on this issue if additional help is needed.

Many thanks @lmangani for your answer, it's clear.


[Access Request] AU/NZ localization - report 11608 "Create EFT File", protected variables

Describe the request
Please allow access to the following variables by making them protected.
    EFTRegister: Record "EFT Register";
    GenJnlLine: Record "Gen. Journal Line";
    BankAcc: Record "Bank Account";
    EFTFileDescription: Text[12];

These variables could be useful when extending the request page or working with triggers in the report extension.
Additional context
.
Internal work item: AB#547357

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 24337.


V1 Breaks Functionality

📖 Description
After the update from version 0.1.2 to 1.0.0 the action does not work anymore. The action fails with the message
parse error, job_id is null. job name might be wrong. See https://github.com/Tiryoh/gha-jobid-action

The job name is correct and working without any changes if I use version 0.1.2 of this action.

Hi @p0fi,
Thanks for raising this issue.
Could you provide a sample job_id name that causes an error?
Unfortunately I was not able to reproduce the error.
https://github.com/Tiryoh/gha-jobid-action/actions/runs/7030811544

Unfortunately, I can't provide you with a link as those are company internal jobs. But the name of the job is Get Current Job URL which I think is not the problem. But the problem might be that this workflow is called via workflow_call?
As I said, if I pin the version to 0.1.2 it works, everything newer breaks.

Hello, @Tiryoh
I met the same error when using Tiryoh/gha-jobid-action@v1. In my workflow, I use a stragety matrix to traverse from CMake version 3.0~3.29 and master. However in these runs with as many as 30 strategies, there are always 1 or 2 runs that encounter this error when acquiring the job id.
And I found that this error happens randomly. Sometimes it happened in 3.9; sometimes it happened in 3.7, sometimes it happened in master...etc.
I cannot publish the repo I'm working now, but I can provide its debug logging messages when rerunning it. Can you see what might be the cause of this error?
Click to expand the log with debug logging
##[debug]Evaluating condition for step: 'Get the Current Job's ID'
##[debug]Evaluating: success()
##[debug]Evaluating success:
##[debug]=> true
##[debug]Result: true
##[debug]Starting: Get the Current Job's ID
##[debug]Loading inputs
##[debug]Evaluating: steps.ggat.outputs.token
##[debug]Evaluating Index:
##[debug]..Evaluating Index:
##[debug]....Evaluating Index:
##[debug]......Evaluating steps:
##[debug]......=> Object
##[debug]......Evaluating String:
##[debug]......=> 'ggat'
##[debug]....=> Object
##[debug]....Evaluating String:
##[debug]....=> 'outputs'
##[debug]..=> Object
##[debug]..Evaluating String:
##[debug]..=> 'token'
##[debug]=> '***'
##[debug]Result: '***'
##[debug]Evaluating: format('{0} / {1}', inputs.CALLER_JOB, github.job)
##[debug]Evaluating format:
##[debug]..Evaluating String:
##[debug]..=> '{0} / {1}'
##[debug]..Evaluating Index:
##[debug]....Evaluating inputs:
##[debug]....=> Object
##[debug]....Evaluating String:
##[debug]....=> 'CALLER_JOB'
##[debug]..=> 'schedule (3.9)'
##[debug]..Evaluating Index:
##[debug]....Evaluating github:
##[debug]....=> Object
##[debug]....Evaluating String:
##[debug]....=> 'job'
##[debug]..=> 'sphinx-update'
##[debug]=> 'schedule (3.9) / sphinx-update'
##[debug]Result: 'schedule (3.9) / sphinx-update'
##[debug]Loading env
Run Tiryoh/gha-jobid-action@v1
##[debug]Evaluating: inputs.github_token
##[debug]Evaluating Index:
##[debug]..Evaluating inputs:
##[debug]..=> Object
##[debug]..Evaluating String:
##[debug]..=> 'github_token'
##[debug]=> '***'
##[debug]Result: '***'
##[debug]Evaluating: inputs.repository
##[debug]Evaluating Index:
##[debug]..Evaluating inputs:
##[debug]..=> Object
##[debug]..Evaluating String:
##[debug]..=> 'repository'
##[debug]=> ''
##[debug]Result: ''
##[debug]Evaluating: inputs.run_id
##[debug]Evaluating Index:
##[debug]..Evaluating inputs:
##[debug]..=> Object
##[debug]..Evaluating String:
##[debug]..=> 'run_id'
##[debug]=> ''
##[debug]Result: ''
##[debug]Evaluating: inputs.job_name
##[debug]Evaluating Index:
##[debug]..Evaluating inputs:
##[debug]..=> Object
##[debug]..Evaluating String:
##[debug]..=> 'job_name'
##[debug]=> 'schedule (3.9) / sphinx-update'
##[debug]Result: 'schedule (3.9) / sphinx-update'
##[debug]Evaluating: inputs.per_page
##[debug]Evaluating Index:
##[debug]..Evaluating inputs:
##[debug]..=> Object
##[debug]..Evaluating String:
##[debug]..=> 'per_page'
##[debug]=> ''
##[debug]Result: ''
##[debug]Evaluating: github.api_url
##[debug]Evaluating Index:
##[debug]..Evaluating github:
##[debug]..=> Object
##[debug]..Evaluating String:
##[debug]..=> 'api_url'
##[debug]=> 'https://api.github.com'
##[debug]Result: 'https://api.github.com'
##[debug]Evaluating condition for step: 'run'
##[debug]Evaluating: success()
##[debug]Evaluating success:
##[debug]=> true
##[debug]Result: true
##[debug]Starting: run
##[debug]Loading inputs
##[debug]Loading env
Run GITHUB_API="/repos/${INPUT_REPOSITORY:-${GITHUB_REPOSITORY}}/actions/runs/${INPUT_RUN_ID:-${GITHUB_RUN_ID}}/jobs"
  GITHUB_API="/repos/${INPUT_REPOSITORY:-${GITHUB_REPOSITORY}}/actions/runs/${INPUT_RUN_ID:-${GITHUB_RUN_ID}}/jobs"
  JOBINFO="$(curl --get -Ss -H "Authorization: ***" -H "Accept: application/vnd.github+json" -H "X-GitHub-Api-Version: [2](https://github.com/hwhsu1231/cmake-docs-l10n-draft1/actions/runs/8184410347/job/22379643251#step:16:2)022-11-28" "${GITHUB_BASEURL}${GITHUB_API}?per_page=${INPUT_PER_PAGE:-[3](https://github.com/hwhsu1231/cmake-docs-l10n-draft1/actions/runs/8184410347/job/22379643251#step:16:3)0}")"
  echo "${JOBINFO}" | grep "Resource not accessible by integration" &&  exit 1
  eval "$(echo ${JOBINFO} | jq -r --arg job_name "${INPUT_JOB_NAME}" '.jobs | map(select(.name == $job_name)) | .[0] | @sh "job_id=\(.id) html_url=\(.html_url)"')"
  echo ${job_id} | grep "null" > /dev/null && echo "parse error, job_id is ${job_id}. job name might be wrong. See https://github.com/Tiryoh/gha-jobid-action" && exit 1
  echo "job_id=${job_id}" >> $GITHUB_OUTPUT
  echo "html_url=${html_url}" >> $GITHUB_OUTPUT
  shell: /usr/bin/bash --noprofile --norc -e -o pipefail {0}
  env:
    INPUT_GITHUB_TOKEN: ***
    INPUT_REPOSITORY:
    INPUT_RUN_ID:
    INPUT_JOB_NAME: schedule (3.9) / sphinx-update
    INPUT_PER_PAGE:
    GITHUB_BASEURL: https://api.github.com
##[debug]/usr/bin/bash --noprofile --norc -e -o pipefail /home/runner/work/_temp/23dee120-e867-[4](https://github.com/hwhsu1231/cmake-docs-l10n-draft1/actions/runs/8184410347/job/22379643251#step:16:4)831-8c[6](https://github.com/hwhsu1231/cmake-docs-l10n-draft1/actions/runs/8184410347/job/22379643251#step:16:6)a-14bef83a[7](https://github.com/hwhsu1231/cmake-docs-l10n-draft1/actions/runs/8184410347/job/22379643251#step:16:7)cfb.sh
parse error, job_id is null. job name might be wrong. See https://github.com/Tiryoh/gha-jobid-action
Error: Process completed with exit code 1.
##[debug]Finished: run
##[debug]Evaluating: steps.request.outputs.job_id
##[debug]Evaluating Index:
##[debug]..Evaluating Index:
##[debug]....Evaluating Index:
##[debug]......Evaluating steps:
##[debug]......=> Object
##[debug]......Evaluating String:
##[debug]......=> 'request'
##[debug]....=> Object
##[debug]....Evaluating String:
##[debug]....=> 'outputs'
##[debug]..=> Object
##[debug]..Evaluating String:
##[debug]..=> 'job_id'
##[debug]=> null
##[debug]Result: null
##[debug]Evaluating: steps.request.outputs.html_url
##[debug]Evaluating Index:
##[debug]..Evaluating Index:
##[debug]....Evaluating Index:
##[debug]......Evaluating steps:
##[debug]......=> Object
##[debug]......Evaluating String:
##[debug]......=> 'request'
##[debug]....=> Object
##[debug]....Evaluating String:
##[debug]....=> 'outputs'
##[debug]..=> Object
##[debug]..Evaluating String:
##[debug]..=> 'html_url'
##[debug]=> null
##[debug]Result: null
##[debug]Finishing: Get the Current Job's ID

@hwhsu1231:

However in these runs with as many as 30 strategies, there are always 1 or 2 runs that encounter this error when acquiring the job id.

This sounds a lot like https://github.com/Tiryoh/gha-jobid-action/issues/1. Note that when making the request to the GitHub REST API, only the first page (page=1) is requested by gha-jobid-action, and by default per_page=30. This means that once you have 31 jobs and all query their job ID, it's very likely that some job will not be on this first page limited to 30 results.
So please make sure that adding the per_page: 100 setting to Tiryoh/gha-jobid-action doesn't fix the problem, see e.g. https://github.com/kaitai-io/ci_targets/commit/87a5b9528a4a8f3037be840a557dd31d90c22cc2 for inspiration.

@generalmimon

So please make sure that adding the per_page: 100 setting to Tiryoh/gha-jobid-action doesn't fix the problem for you, see e.g. https://github.com/kaitai-io/ci_targets/commit/87a5b9528a4a8f3037be840a557dd31d90c22cc2 for inspiration.

After setting per_page: 100 and trying several times, it seems that this error won't happen for now.
- name: Get the Current Job's ID
  uses: Tiryoh/gha-jobid-action@v1
  id: gcji
  with:
    github_token: ${{ steps.ggat.outputs.token }}
    job_name: '${{ inputs.CALLER_JOB }} / ${{ github.job }}'
    per_page: 100

@hwhsu1231 Thanks for pointing this out
@generalmimon Thanks for your help
I'll update the error message to check the per_page param

@p0fi There are 2 fixes after v1.0.0 release. Could you try v1 again?

Update API URI (https://github.com/Tiryoh/gha-jobid-action/pull/36)
Update per_page param error message (https://github.com/Tiryoh/gha-jobid-action/pull/40)

@p0fi There are 2 fixes after v1.0.0 release. Could you try v1 again?

Update API URI (Compatibility with GitHub Enterprise #36)
Update per_page param error message (feat: Update parse error message #40)

Our problem is fixed with that release! Thanks!

@p0fi Great! Thanks for your feedback😆

Sadly I have to reopen the issue, as it appears that it is still not fixed in my particular case. My test initially worked but our regular deploy now failed again because of the action not being able to get the job ID. It seems that there is a difference in the context if the job in question is triggered via a direct push or via a workflow_call event. Our release pipeline uses a workflow_dispatch event. With this context the current action (1.2.0) does not work while 0.1.2 still works.

@p0fi:

It seems that there is a difference in the context if the job in question is triggered via a direct push or via a workflow_call event. Our release pipeline uses a workflow_dispatch event. With this context the current action (1.2.0) does not work while 0.1.2 still works.

Can you check that the job_name is correct, i.e. that the job_name that your workflow provides to Tiryoh/gha-jobid-action matches the job name displayed on the GitHub web interface?

It is correct, it does work with version 0.1.2 of the action.

@p0fi Could you check with the latest version 1.3.0? I think there's a good chance that it fixes the problem you were reporting (i.e. worked in 0.1.2, didn't work in 1.2.0).

@p0fi Any updates?

I thought I had this problem - a workflow called via both workflow_dispatch and workflow_call, where the job had a .name property. I originally had to generate the job name because a workflow_call will embed the name. For example:
- name: Compute Job Name
        id: job-name
        run: |
          if [[ "${{ github.event_name }}" == "workflow_dispatch" ]]; then
            echo "job-name=Start Deployment" >>$GITHUB_OUTPUT
          else
            echo "job-name=Deploy to ${{ inputs.environment }} / Start Deployment" >>$GITHUB_OUTPUT
          fi
      - name: Find Github Actions Job ID
        uses: Tiryoh/gha-jobid-action@v1
        id: job
        with:
          github_token: ${{ secrets.GITHUB_TOKEN }}
          job_name: ${{ steps.job-name.outputs.job-name }}

I originally had the following:
# extra single-quotes around the name
echo "job-name='Start Deployment'" >>$GITHUB_OUTPUT

That added extra quotes, which broke workflow_dispatch calls. Removing them fixed the workflow_dispatch (I also originally had them around the computed one as well, and removed those and it works.

Hi sorry for the delay, I just tested it with version 1.4 and it still breaks. I'm getting the following error this time...
parse error, job_id is null and total_count is 8. 'job_name' or 'per_page' might be wrong. See https://github.com/Tiryoh/gha-jobid-action/blob/main/README.md#inputs


Stop exposing v1beta1,2 at kubernetes.io

This should help in decreasing the load time for kubernetes.io/third_party/swagger-ui/. Its too slow right now.
Not to be merged before https://github.com/GoogleCloudPlatform/kubernetes/pull/8594

@bgrant0607 @krousey

LGTM


[Improvement] Active wallet name

I would like to propose an improvement in UI.
Display on top of the screen somewhere in a corner the name of the active wallet.
I use Alby Go with multiple accounts and sometimes I can't remember which one was last selected and I send sats.

Let's do it this way, but let's only display it if there's more than 1 wallet connected
Link to Figma


Run ch7 keypoint_plugin for keypoint detection

Hello, I am reading chapter 7 of your new book on opencv3-qt5. For experimenting with the presented keypoint detection algorithms, I put the keypoint_plug in the context computer_vision project developed the previous chapters.
I have got a plugin error message:  "Select a secondary image first!"  (for the generated Computer Vision GUI, I loaded the image as shown in the book). Switching any algorithm available gives the message. I feel only image should be fine with keypoint detection rather than matching.
If I perform the matching operation, the interface is easily to be crashed for some reason.
Working environment: OpenCV3.4 + Qt5.8
Thanks

Secondary image is the one you need to choose using the plugin user interface. Hope this helps.

Thanks you very much! It is clear !

@jingweimo you can close the issue if it is solved now :)

I have one follow-up question on implementing the example given in page293-301, on the extracting and matching descriptors. I have tested those codes, without being integrated into the computer vision project. There is an error in the step of matching descriptors:
opencv error: unsupported format or combination of formats (type=0 in cv::flann::buildindex_,


i18n(fr): Update all files fr/basics/* in French language

Description (required)
Update files :

i18n(fr): Update astro-components.mdx
i18n(fr): Update astro-pages.mdx
i18n(fr): Update astro-syntax.mdx
i18n(fr): Update basics/layouts.mdx
i18n(fr): Update basics/rendering-modes.mdx

Related issues & labels (optional)

Closes #
Suggested label: i18n

Lunaria Status Overview
🌕 This pull request will trigger status changes.

Learn more
By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.
You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

Locale
File
Note

fr
basics/astro-components.mdx
Localization changed, will be marked as complete.

fr
basics/astro-pages.mdx
Localization changed, will be marked as complete.

fr
basics/astro-syntax.mdx
Localization changed, will be marked as complete.

fr
basics/layouts.mdx
Localization changed, will be marked as complete.

fr
basics/rendering-modes.mdx
Localization changed, will be marked as complete.

Warnings reference

Icon
Description

🔄
The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.


Add configurable joystick axis deadzones

Current deadzones are not configurable and can lead to either very small (most axes) or very large deadzones (triggers) when the controller is connected.

Closed by https://github.com/ppy/osu-framework/pull/5122


NTR: [Inflammasome-mediated signal transduction pathway]

Hi GO,
I think we need to create a new term for Inflammasome-mediated signal transduction pathway
Thanks
Sylvain
Term: Inflammasome-mediated signal transduction pathway
Definitiion:
An intracellular signal transduction pathway that starts with a ligand binding to a pattern recognition receptor (PRR), assembly of the inflammasome complex, leading to the activation of CASP1 and inducing an inflammatory response. In some cases, inflammasome-mediated signal transduction can lead to programmed cell death, such as pyroptosis.
Child of
GO:0002221 pattern recognition receptor signaling pathway
GO:0006954 inflammatory response
GO:0035556 intracellular signal transduction
PMID:35883561
I suppose that this term should be parent of the following terms:
GO:1904784 NLRP1 inflammasome complex assembly
GO:0140970 AIM2 inflammasome complex assembly
GO:0140632 canonical inflammasome complex assembly
GO:0140633 CARD8 inflammasome complex assembly
GO:0140739 NLRP6 inflammasome complex assembly
GO:0044546 NLRP3 inflammasome complex assembly
GO:0140971 regulation of AIM2 inflammasome complex assembly
GO:1900225 regulation of NLRP3 inflammasome complex assembly
GO:0140972 negative regulation of AIM2 inflammasome complex assembly
GO:0140973 positive regulation of AIM2 inflammasome complex assembly
GO:1900227 positive regulation of NLRP3 inflammasome complex assembly
GO:1900226 negative regulation of NLRP3 inflammasome complex assembly

+[Term]
+id: GO:0141084
+name: inflammasome-mediated signaling pathway
+namespace: biological_process
+def: "An intracellular signal transduction pathway that starts with a ligand binding to a pattern recognition receptor (PRR), assembly of the inflammasome complex, leading to the activation of CASP1 and inducing an inflammatory response. In some cases, inflammasome-mediated signal transduction can lead to programmed cell death, such as pyroptosis." [PMID:35883561]
+synonym: "inflammasome-mediated signal transduction" EXACT []
+is_a: GO:0002753 ! cytosolic pattern recognition receptor signaling pathway
+relationship: part_of GO:0006954 ! inflammatory response
+property_value: term_tracker_item "https://github.com/geneontology/go-ontology/issues/25772" xsd:anyURI
+created_by: pg
+creation_date: 2023-07-18T12:28:03Z
+

@sylvainpoux
Is is right that these should be part_of inflammasome-mediated signaling pathway
GO:1904784 NLRP1 inflammasome complex assembly
GO:0140970 AIM2 inflammasome complex assembly
GO:0140632 canonical inflammasome complex assembly
GO:0140633 CARD8 inflammasome complex assembly
GO:0140739 NLRP6 inflammasome complex assembly
GO:0044546 NLRP3 inflammasome complex assembly
and those, part_of 'regulation of inflammasome-mediated signaling pathway'?
GO:0140971 regulation of AIM2 inflammasome complex assembly
GO:1900225 regulation of NLRP3 inflammasome complex assembly
GO:0140972 negative regulation of AIM2 inflammasome complex assembly
GO:0140973 positive regulation of AIM2 inflammasome complex assembly
GO:1900227 positive regulation of NLRP3 inflammasome complex assembly
GO:1900226 negative regulation of NLRP3 inflammasome complex assembly

Added 'part of' some 'inflammasome-mediated signaling pathway' to GO:0140632 canonical inflammasome complex assembly
As this is the parent term, all children should inherit it

+[Term]
+id: GO:0141085
+name: regulation of inflammasome-mediated signaling pathway
+namespace: biological_process
+def: "Any process that modulates the frequency, rate or extent of an inflammasome-mediated signaling pathway." [PMID:33467177]
+synonym: "regulation of inflammasome-mediated signal transduction" EXACT []
+intersection_of: GO:0065007 ! biological regulation
+intersection_of: regulates GO:0141084 ! inflammasome-mediated signaling pathway
+property_value: term_tracker_item "https://github.com/geneontology/go-ontology/issues/25772" xsd:anyURI
+created_by: pg
+creation_date: 2023-07-18T12:37:42Z
+
+[Term]
+id: GO:0141086
+name: negative regulation of inflammasome-mediated signaling pathway
+namespace: biological_process
+def: "Any process that stops, prevents or reduces the frequency, rate or extent of an inflammasome-mediated signaling pathway." [PMID:33467177]
+synonym: "negative regulation of inflammasome-mediated signal transduction" EXACT []
+intersection_of: GO:0065007 ! biological regulation
+intersection_of: negatively_regulates GO:0141084 ! inflammasome-mediated signaling pathway
+property_value: term_tracker_item "https://github.com/geneontology/go-ontology/issues/25772" xsd:anyURI
+created_by: pg
+creation_date: 2023-07-18T12:40:09Z
+
+[Term]
+id: GO:0141087
+name: positive regulation of inflammasome-mediated signaling pathway
+namespace: biological_process
+def: "Any process that activates or increases the frequency, rate or extent of an inflammasome-mediated signaling pathway." [PMID:33467177]
+synonym: "positive regulation of inflammasome-mediated signal transduction" EXACT []
+intersection_of: GO:0065007 ! biological regulation
+intersection_of: positively_regulates GO:0141084 ! inflammasome-mediated signaling pathway
+property_value: term_tracker_item "https://github.com/geneontology/go-ontology/issues/25772" xsd:anyURI
+created_by: pg
+creation_date: 2023-07-18T12:40:21Z


What makes this specific to a Lumen / Laravel project?

For example the use of .env files, the calls to the Artisan database migrations, or at a low level simply the dependencies which are specifically being installed for Lumen. That being said, it should be rather easy to adopt this boilerplate for other frameworks and projects.
The idea of this repository is mainly to give people a good starting point when setting up a CD pipeline to AWS EB using Gitlab, which took me quite some time to figure out.


Updating versions, adding CI definitions.

I'm trying to put together a collection of RxJS utilities for node here.  This component fits in perfectly.
I've added CI definitions and updated to RxJS RC1 in this pull request.
Is this of interest to you?

I've updated and resolved the conflicts.  There is a bug in Node 4 that I can take a look at:
https://travis-ci.org/tools-rx/spawn-rx
https://ci.appveyor.com/project/dfbaskin/spawn-rx
Next week the Release of RxJS will be available.  At that point I was planning on moving all the projects over to semantic-release.
Let me know if there is anything else I can help you with.  Thanks!


PSI json output last node not closed

Bug description:

tsp: TSDuck - The MPEG Transport Stream Toolkit - version 3.27-2438
Command used:
tsp -I ip xxxxx -l yyyyy -P psi  -a -j - -O drop.
The last node does not have the closing "}"
[
  {
    "#name": "PAT",
    "#nodes": [
      {
        "#name": "metadata",
        "pid": 0
      },
      {
        "#name": "service",
        "program_map_pid": 32,
        "service_id": 1
      }
    ],
    "current": true,
    "network_pid": 16,
    "transport_stream_id": 1,
    "version": 14
  },
  {
    "#name": "CAT",
    "#nodes": [
      {
        "#name": "metadata",
        "pid": 1
      }
    ],
    "current": true,
    "version": 1
  },
  {
    "#name": "PMT",
    "#nodes": [
      {
        "#name": "metadata",
        "pid": 32
      },
      {
        "#name": "component",
        "#nodes": [
          {
            "#name": "ISO_639_language_descriptor",
            "#nodes": [
              {
                "#name": "language",
                "audio_type": 0,
                "code": "ita"
              }
            ]
          }
        ],
        "elementary_pid": 2541,
        "stream_type": 4
      },
      {
        "#name": "component",
        "elementary_pid": 2542,
        "stream_type": 27
      }
    ],
    "current": true,
    "service_id": 1,
    "version": 2
  },
  {
    "#name": "NIT",
    "#nodes": [
      {
        "#name": "metadata",
        "pid": 16
      },
      {
        "#name": "network_name_descriptor",
        "network_name": "Test"
      },
      {
        "#name": "transport_stream",
        "#nodes": [
          {
            "#name": "service_list_descriptor",
            "#nodes": [
              {
                "#name": "service",
                "service_id": 1,
                "service_type": 1
              }
            ]
          }
        ],
        "original_network_id": 1,
        "preferred_section": 0,
        "transport_stream_id": 1
      }
    ],
    "actual": true,
    "current": true,
    "network_id": 1,
    "version": 3
  },
  {
    "#name": "SDT",
    "#nodes": [
      {
        "#name": "metadata",
        "pid": 17
      },
      {
        "#name": "service",
        "#nodes": [
          {
            "#name": "service_descriptor",
            "service_name": "Srv_2",
            "service_provider_name": "",
            "service_type": 1
          }
        ],
        "ca_mode": false,
        "eit_present_following": false,
        "eit_schedule": false,
        "running_status": "undefined",
        "service_id": 1
      }
    ],
    "actual": true,
    "current": true,
    "original_network_id": 1,
    "transport_stream_id": 1,
    "version": 8

Hi @enricovittorini
This is not a bug. The input processing is not terminated, the output is not terminated either. The ip input is endless, it reads packets endlessly. If some new table is processed, you will see the closing }, of the current table and then the opening { of the next table. If there is some terminating condition such as -P until ... or if you interrupt the processing using Ctrl-C, then you will see the two terminating lines } and ].
The reason why you don't see the closing } of the current table while the processing is still in progress is because the psi plugin doesn't know yet if the next line will be }, (before a new table) or } (without comma, at end of list of tables, at end of processing).

thanks @lelegard , but how would you process the a live analysis?
i explain what i am doing: i am reading the stout to parse object by object the received JSON.
If the JSON is not closed properly then it is not considered valid by the parser (and not taken)
In a live analysis, there should always be a "," after each node in the stout. don't you agree?
would it be possible to create a patch to the logger to say "always close a JSON node for live": --live-json ?
thanks
Enrico

In a live analysis, there should always be a "," after each node in the stout. don't you agree?

No. Each plugin is independent of the other and cannot determine if the output is endless or not. The presence of -P until ... before or after -P psi makes a difference.

would it be possible to create a patch to the logger to say "always close a JSON node for live": --live-json ?

It should also close the list with ]. Otherwise the parse would complain about an unterminated list.
I will consider something like this for this use case. But it is a very difference type of output. Each table should be a complete JSON file.

understood, in my case i am reading the stout as a "stream", and extract node by node what is received. {... } after {...},
would be be able to indicate which file should i look at to arrive to what i need? I will try to understand if i will be able to change it by myself for the time being.
thanks!

In fact, your use case is already addresses by option --log-json-line (there is also an option named --log-xml-line for those who prefer parsing XML).
Please read the description of --log-json-line.
Example:
$ tsp -I ip 6666 -P psi -a --log-json-line=@@HERE@@:  -O drop
* psi: @@HERE@@:{ "#name": "PAT", "#nodes": [ { "#name": "metadata", "pid": 0 }, { "#name": "service", "program_map_pid": 33, "service_id": 800 } ], "current": true, "transport_stream_id": 930, "version": 11 }
* psi: @@HERE@@:{ "#name": "PMT", "#nodes": [ { "#name": "metadata", "pid": 33 }, { "#name": "component", "#nodes": [ { "#name": "T2MI_descriptor", "num_t2mi_streams_minus_one": 0, "pcr_iscr_common_clock_flag": false, "t2mi_stream_id": 0 } ], "elementary_pid": 64, "stream_type": 6 } ], "current": true, "service_id": 800, "version": 11 }

This is much easier than reading stdout as a stream. Read stderr and filter lines containing the string that you specified to --log-json-line, in the example it is @@HERE@@:. Just specify something that you are confident to uniquely identify the lines to parse. Drop the beginning of the line, up to your marker string. The rest of the line is a complete JSON structure. There is one line per table.
Similar options are available in plugins tables, analyze and a few others.

And if you parse the JSON output using Python, you do not even need to use tsp. You can activate the plugin directly from your Python application and handle the logged lines directly from a Python class without creating any process, no pipe, no stream I/O.
See an introduction here, the list of TSDuck Python classes here and sample Python programs here.
The same features exist for Java.

Automatically closed after 402 days without update and "close pending" label set.


Remove unused dependencies

Description
Remove unused dependencies. org.apache.poi and itext are not used anymore in the backend

@devnied : Can u plz fix the build ? :)


Allow for testing.Result to be booleanized

It's nice to be able to assert the result of an invoke command (instead  of having to assert the exit code isn't zero.
This is easily accomplished by adding a __bool__ method to Result.
assert my_invocation()
# vs.
assert my_invocation().exit_code == 0

Thanks for the interesting idea. However, those semantics seem non-obvious and counter to the explicit-is-better-than-implicit principle enough that I’d want to think carefully about this before accepting.

In the meantime, you can of course write a helper function for your tests to avoid any code duplication.

You almost never want to be using the status code as the main test that your command succeeded, so giving it special behavior doesn't seem right. Instead, you should be testing that the output/side effects of the command are what you expect.

Perhaps booleanizing isn't the right way about it, as it is implicit. Essentially I want to assert that the result was successful (in addition to other asserts as @davidism pointed out), and right now the Result object doesn't quite help you with that.
Should I look at the exit_code or the exception attribute? Both? The __repr__ leads me to believe that the exception attribute holds the source of truth.
How would y'all feel about some sort of "success" method/property, as essentially that's what I want. Some way of asserting success.

You should look at whatever you want to test. If you care about the exit code being zero, look at that. If you want to know what exception was raised (if any), look at that. If you want to know the command actually did the thing it was supposed to do, look at its output or other side effects.


Migrations: Add first-class property facets

Note to providers: This changes some method signatures in MigrationsSqlGenerator.
Resolves #5223

:shipit:

Just noticed this change, and am wondering about the inclusion of RowVersion, which seems like a very SqlServer-specific concept, into the provider-independent core...?

@roji We are very inconsistent about it at the moment. It used to be a core concept in the old stack, and hence there is a data annotation for it. We realized it wasn't core when doing the fluent API and so didn't add it there, but it was still in the core concepts of the type mapper. Need to discuss with @bricelam @divega @rowanmiller and others about where we should end up with this.


Custom OWSM Policies

Hello,
I have custom OWSM Policies.
Thanks to the wdt, I can attach deployment plan to the webservices.
I cannot add the Policies (importWSMArchive) before the start of the managed server. I do it after in a kind of post step.
But in this case, I need a restart of my cluster. It's not really convenient.
Do you know if there is a workaround?
Or a way to reinitialize the WSMAgent of the SecurityAgentTube initialized when the managed server started?
Or I need to be able to do it between the start of the admin server and the start of the managed server?
Thanks for your help.

@sebmichiels Unfortunately, WDT does not support this use case at this time.  We have always wanted to add support for this but we need help from the OWSM development team to do so.  Maybe try opening an SR against OWSM stating your need.


Czech programmers keyboard has unexpected behaviour on wsl2

Windows Version
Microsoft Windows [Version 10.0.22621.1413]
WSL Version
<IP_ADDRESS>
Are you using WSL 1 or WSL 2?

[X] WSL 2
[ ] WSL 1

Kernel Version
<IP_ADDRESS>
Distro Version
Ubuntu 20.04
Other Software
No response
Repro Steps
Use https://learn.microsoft.com/en-us/globalization/keyboards/kbdcz2.html czech programmers keyboard, that basically is EN keyboard with special czech characters with pressed AltGr.

When you switch your windows keyboard to US keyboard, windows and wsl have same layout > but you are not able to write special czech characters then...
 Unfortunately this isn't something that WSL can fix since the keyboard handling is done by terminal. Maybe Windows Terminal would be the right place to report this.
Closing since this isn't a WSL issue.


Allow run_mockserver.sh to accept subject alt names parameter

This is handy if you're running the docker image and need the generated certs to have specific subject alternate domain names.
The need arose because we use docker-compose to spin up a mock-server, e.g.
mock-server:
  image: jamesdbloom/mockserver
  command: "/opt/mockserver/run_mockserver.sh -logLevel DEBUG -serverPort 80,443
    proxyPort 1090 -sslAltDomains www.domain1.com, www.domain2.com"

I would prefer to change this PR to allow pass an abstract string to the JVM for generic system preferences.  This could be used for example to update JVM setting such as memory or any generic MockServer settings such as the default subject alternative names or CORS settings.
If you willing to update the PR and submit it then that would be good, if not I'll make that change when available, hopefully the next couple of weeks.

I'm now closing this PR as the functionality can be achieve by using the genericJVMOptions option with the latest docker container.


image.load() error

I'm getting the below error when I try to run test.lua on any image that wasn't included in the repository. Even if I download an image from the repository (i.e. https://raw.githubusercontent.com/DmitryUlyanov/texture_nets/master/data/readme_pics/karya.jpg) I get the same error. Has anyone else run into this?
/root/torch/install/bin/luajit: /root/torch/install/share/lua/5.1/image/init.lua:220: Not a JPEG file: starts with 0x2d 0x2d
stack traceback:
    [C]: in function 'load'
    /root/torch/install/share/lua/5.1/image/init.lua:220: in function 'loader'
    /root/torch/install/share/lua/5.1/image/init.lua:368: in function 'load'
    test.lua:23: in main chunk
    [C]: in function 'dofile'
    /root/torch/install/lib/luarocks/rocks/trepl/scm-1/bin/th:145: in main chunk
    [C]: at 0x00406670

Similarly, for PNGs I get
/root/torch/install/bin/luajit: /root/torch/install/share/lua/5.1/image/init.lua:156: [read_png_file] File data/readme_pics/house.png is not recognized as a PNG file
stack traceback:
    [C]: in function 'load'
    /root/torch/install/share/lua/5.1/image/init.lua:156: in function 'loader'
    /root/torch/install/share/lua/5.1/image/init.lua:368: in function 'load'
    test.lua:23: in main chunk
    [C]: in function 'dofile'
    /root/torch/install/lib/luarocks/rocks/trepl/scm-1/bin/th:145: in main chunk
    [C]: at 0x00406670

Please, read a readme for information on how to create an image database suitable for learning.

I can't find anything in the readme about image preparation; are you referring to a readme somewhere else?

https://github.com/DmitryUlyanov/texture_nets#training

Is this an issue with the training setup? I thought the issue was with the image I am providing to the test.lua script. test.lua works (with the model I trained) when using images provided in the data/readme_pics folder, but does not work when using other images.

You said

I'm getting the below error when I try to run train.lua on any image that wasn't included in the repository

I thought the issue was with the image I am providing to the test.lua script. test.lua works (with the model I trained)

I am confused. Did you train a model already?

Ah I'm sorry, my original comment was wrong. It is now updated. train.lua was fine, the issue was with test.lua.

It looks like it's throwing the error on line 23 of test.lua where it fails on image.load(params.input_image, 3)

This appears to be an issue with the image library; it is unrelated to your code. I will look for a solution elsewhere. Thanks!

Have you solved the problem and can you give a good solution for me? Thanks very much.


Created Contributors file

I have added 2 files under Workflows directory.

Contributors.md : Explaining about the steps to be taken to contribute.
CODE_OF_CONDUCT.md : Explaining the ethics to be followed while contributing

The checks have failed for my files. Kindly let me know the possible reason and its solution.

@gauravsaini02  We are figuring out how can we pass your test.
One of the solution is to set your own API key at github secrets on your forked repository.
Go to forked repository > Settings > Secrets and Variables > Actions and set Repository Secrets.
You have to set OPENAI_API_KEY, JINAAI_API_KEY, and COHERE_API_KEY.
Sorry for the process. Me and @bwook00 will find a way that you don't have to set those variables.
If you want to pass it quickly, please set the secrets. Or you can wait for the solution. Thank you.

@gauravsaini02 I send a PR for resolving test issue.
https://github.com/Marker-Inc-Korea/AutoRAG/pull/354
Please wait for this will be merged, and the next time your PR will be merged. Thanks

Hi Dear,
Thanks a lot....
I was looking forward to contribute to technical part in upcoming future. This issue will still create trouble i guess...


Would you please provide the parameters for the LSQ and the block reconstruction? Thanks a lot

Hi, the LSQ and the block reconstruction calibration code have been added by https://github.com/Xiuyu-Li/q-diffusion/pull/20.
Closing the issue for now. Let me know if there are any further questions.


Fluentd, ElasticSearch-Logging

Please run microk8s.inspect and attach the generated tarball to this issue.
We appreciate your feedback. Thank you for using microk8s.
Currently I have fluentd running as a sidecar in every application pod and spin up my own ES cluster. What's the use case of the fluentd add-on and elasticsearch-logging provided by MicroK8s in kube-system namespace? Can it be used as a single point of log proxy / collection from all application pods and shown in Kibana?

@khteh having fluentd per pod is very much suitable for multi-tenant kubernetes cluster.  But this adds a couple of disadvantages.  First, you have the overhead of the sidecars.  Second, you don't get all the kubernetes metadata that can be very helpful in debugging both the pod and the cluster.
In our setup, since its an on prem cluster we use node level logging agent, similar to the setup you notice in microk8s.
I hope i was able to explain to you properly.


add stm32 low level drivers

Thank you @rahmanih - this looks good!
I will need to hold off on merging it for the moment as we are still finalizing the new development process. We need to make sure all new contributions are compliant with that process, so we can continue to obtain safety certification for this code base.

closing this PR, as it'll be merged in a separate repository


Add Uffizzi Preview Deployment to Workflows.

Sorry, this is just a repo for a previous conference, so I'm not taking PRs unless something breaks.


Remove: 7S2P.Effie.CN version 3.4.1

403 Access Denied
Checklist for Pull Requests

[x] Have you signed the Contributor License Agreement?
[ ] Is there a linked Issue?

Manifests

[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.6 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

URL: https://download.effie.co/effie/effie_setup_3.4.1.exe
Response status code does not indicate success: 404 (Not Found).
(Automated message - build 872)


Extending simplegmaps

Add functionality to extend and create plugins for simplegmaps

Hi, i'va made some adaptations of the plugin for my project but i'd like to separate my changes from the plugin, so when you release a new version y can work with my extension/changes, can you guide me in any way?


Improve README.md file

Create a banner for readme.
Make the readme file more attractive.✨

Can I take up this issue?

Can I take up this issue?

Sure.

What's the progress @mahmood199 ?

Hello, @priyalbhatewara123  I would like to contribute to this project by resolving this issue. I have a fair understanding of the project's aim and will be able to create a new banner, additionally improvise the Readme.md file. I request you to kindly assign this issue to me

Hello, @priyalbhatewara123 I would like to contribute to this project by resolving this issue. I have a fair understanding of the project's aim and will be able to create a new banner, additionally improvise the Readme.md file. I request you to kindly assign this issue to me

Assigned :)


New themes or layout for calculator

You can check the calculator here:
https://niranjank2022.github.io/Cluster-of-Projects/Simple/Calculator/
As you could see, the theme of the calculator might not be pleasing. So, try to come up with unique and creative colour themes and other design features.

Hey, @niranjank2022 , I would love to work on it. So, please assign this to me.

Hey, @niranjank2022 , I would love to work on it. So, please assign this to me.

Yes, @Rituraj-13 . I really appreciate your interest. You can work on the issue and submit a PR.

@niranjank2022 - I would like to add some features, So can you please assign it to me.

Hey @niranjank2022, I have made required changes to improve the theme.
And, here is the link to my PR - #7


want to redesign the the main page

Assigned @Shreyan-12345

I would like to work on this issue. May I get this opportunity?

Yeah sure @Diksha4111 , go ahead and all the best.

I have made the changes @niloysikdar

@niloysikdar please tell me how to make a pull request :)

Please review, I have made a pull request.

This is the link which contains 3 pull requests
_https://github.com/pulls_

@niloysikdar is my pull request visible now?

Yes @Diksha4111

I would like to work on this issue. May I get this opportunity?

Sure @aniketsinha2002 , feel free to drop your suggestions on which you want to work on


Use in-place compilation instead of directory swapping

Right now, files are compiled in the build system from .ts sources in src/ to under dist/src, then dist/build. That's no longer really necessary. As a breaking change for 7.0 (tracking as part of #672), let's change to compiling from src/*.ts to src/*.js. That way we don't have to have a different directory structure for the releases branch.

☠  It's time! ☠
Per #876, this repository is no longer accepting feature pull requests. TSLint is being deprecated and we recommend you switch to https://typescript-eslint.io.
Thanks for open sourcing with us, everyone!


Add support for IPv6 in url library

Because IPv6 addresses contain colons, they cannot be directly used in URLs because the colons would conflict with both the protocol declaration (http:// or https://) and port numbers.


Update README.md

Change how to use instructions

Thanks for your contribution!

Thanks for your contribution!


issue with saggital MR scans

I have a 3D MR series with 160 dicom files. x, y, z dims for the series are (160, 256, 256). If I've followed the code properly, i think it assumes that image series files are acquired in z direction, is that a correct?

terrific tool by the way, first time I've run into issues using it!

Hi @ceps1986, glad you like the tool!
What exactly is the issue you were having? Were you expecting it to be acquired in a different manner? Would you also mind clarifying what you mean by acquired? We don't do much when the DICOM files are loaded in, it is mostly just handled by Pydicom. We do assume that the contour points are arranged in [x, y, z].

Hi @asim-shrestha, thanks for the prompt response.
Here's what I think is happening... (I haven't gone down the rabbit hole just yet):
What exactly is the issue you were having?

rtstruct.add_roi requires mask.shape[-1] to be equal to the number of DICOM files. if I reshape my mask (i.e. from [160, 256, 256] -> [256, 256, 160]) then the contour points are being place on the wrong axis in get_contours_coords (https://github.com/qurit/rt-utils/blob/5b7072e306c52c3ee7c11b3d778a8dbeb80f29d9/rt_utils/image_helper.py#L46)
Doing this writes a RTSTRUCT file, but the contours in the file do not match the image space so several dicom viewers won't import/load the DICOM file properly.

Would you also mind clarifying what you mean by acquired?

MR scans can be acquired in any direction (axial, sagittal, coronal, etc.). In my case (where images where acquired sagittally) this leads to the array_data loaded for a single file using pydicom to show as below.

We don't do much when the DICOM files are loaded in, it is mostly just handled by Pydicom. We do assume that the contour points are arranged in [x, y, z].

Yes, points are always arranged in [x, y, z]. Here though (https://github.com/qurit/rt-utils/blob/5b7072e306c52c3ee7c11b3d778a8dbeb80f29d9/rt_utils/image_helper.py#L50) the assumption is that the slices are in the z direction, therefore contour coordinates in the wrong space.

Hope this makes sense! I will look for a publicly available dataset that I can share so that we can test this

Thank you for the in-depth response @ceps1986! This clears a lot up. I'll have to discuss ways we can update RT-Utils to handle files acquired in different axes.
If you have any ideas yourself, feel free to submit a pull request with your changes :)


Handle corner case in which there is no data for an entire day

This probably requires an empty state of some sort.

@pe0ny I think you need to take a look at this one. If the user does not move the whole day and also does not manually add a TimeSlot, there's no way for us to know what's going on. I agree that an empty state might be needed


stream_settings: Fix stream row switching behavior when adding subscribers.

:bookmark_tabs:  Overview
The root cause of the bug is that the switch_rows(event) function in stream_settings_ui.js does not consider whether the user is currently editing the add_subscriber_pill input in the right panel of the stream settings menu for the key up/down event to trigger the stream row switching process.
Adjusted the switch_rows(event) behavior by adding a condition to prevent switching stream row when the user in the subscriber tab on stream settings menu (hash_parser.is_on_stream_subscribers()) and is focused on the add_subscribers_pill input
Fixes zulip#29690
CZO

Screenshots and screen captures:
Screencast from 25-04-24 17:46:54.webm

Self-review checklist

[x] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[x] Explains differences from previous plans (e.g., issue description).
[x] Highlights technical choices and bugs encountered.
[x] Calls out remaining decisions and concerns.
[x] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[x] Each commit is a coherent idea.
[x] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[x] Visual appearance of the changes.
[x] Responsiveness and internationalization.
[x] Strings and tooltips.
[x] End-to-end functionality of buttons, interactions and flows.
[x] Corner cases, error conditions, and easily imagined bugs.

Info: still missing some test and proper linting, but decided to up this PR to get early feedback

update: added test and fixed linting

Thanks! @sahil839 are you up for reviewing this one? I haven't tested.

Just a small point - "Fixes .." line in commit message should end with a period. Looks good otherwise.
@timabbott ready for your review.

Made the small test tweak noted above and merged, thanks @PieterCK!


Update styleguide.md

From the GitHub style guide: software --> the software; copy --> a copy
Ampersands and Dates: for example:-->for example,
Thank you for contributing! Please confirm this pull request meets the following requirements:

[x] I followed the contributing guidelines: https://github.com/github/explore/blob/master/CONTRIBUTING.md
[ ] I have no affiliation with the project I am suggesting (as a maintainer, creator, contractor, or employee).

Which change are you proposing?

[x] Suggesting edits to an existing topic or collection
[ ] Curating a new topic or collection
[ ] Something that does not neatly fit into the binary options above

Editing an existing topic or collection
I'm suggesting these edits to an existing topic or collection:

[ ] Image (and my file is *.png, square, dimensions 288x288)
[x] Content (and my changes are in index.md)

This will make a document look more proffesional.

Curating a new topic or collection

[ ] I've formatted my changes as a new folder directory, named for the topic or collection as it appears in the URL on GitHub (e.g. https://github.com/topics/[NAME] or https://github.com/collections/[NAME])
[ ] My folder contains a *.png image (if applicable) and index.md
[ ] All required fields in my index.md conform to the Style Guide and API docs: https://github.com/github/explore/tree/master/docs

Please replace this line with an explanation of why you think this topic or collection should be curated.

Something that does not neatly fit into the binary options above

[ ] My suggested edits are not about an existing topic or collection, or at least not a single one
[ ] My suggested edits are not about curating a new topic or collection, or at least not a single one
[ ] My suggested edits conform to the Style Guide and API docs: https://github.com/github/explore/tree/master/docs

Please replace this line with an explanation of your proposed changes.

Minor grammatical errors.
Please note: we will close your PR without comment if you do not check the boxes above and provide ALL requested information.

Closing this PR as @mvkaran addressed the changes and how they conflict with our intentions in the current copy.


Very laggy when starting

We have written the needed data into your clipboard because it was too large to send. Please paste.

Its hard to pin down, I do notice a spike in CPU usage so maybe its related
to #63314 but that ticket is not super helpful. I notice Omnisharp at the
top of the list particularly when I open a dotnet core project.
Sorry I know this not a lot of info but that is what is frustrating about
this is I don't know what is going on
On Tue, Nov 27, 2018 at 4:27 PM Peng Lyu<EMAIL_ADDRESS>wrote:

Please share more information about how to reproduce this issue.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/vscode/issues/63852#issuecomment-442223118,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALq0G26YFWxHHBj6E2QJMqGYFX0DQgK3ks5uza5HgaJpZM4Y1eMo
.

We have written the needed data into your clipboard because it was too large to send. Please paste.

The information we ask is what the Issue Reporter put into the clipboard. You can also follow https://github.com/Microsoft/vscode/wiki/Performance-Issues to provide more detailed info.

Issue Type: Performance Issue
adf
VS Code version: Code 1.29.1 (bc24f98b5f70467bc689abf41cc5550ca637088e, 2018-11-15T19:13:36.375Z)
OS version: Windows_NT x64 10.0.14393

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-4600U CPU @ 2.10GHz (4 x 2694)

GPU Status
2d_canvas: enabledchecker_imaging: disabled_offflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwarerasterization: enabledvideo_decode: enabledvideo_encode: enabledwebgl: enabledwebgl2: enabled

Memory (System)
15.88GB (8.19GB free)

Process Argv

Screen Reader
no

VM
0%

Process Info
CPU %	Mem MB	   PID	Process
    3	    96	 11224	code main
    0	   207	   772	   window (profile-view.component.ts - mpr-lane1 - Visual Studio Code)
    0	   117	  4180	     extensionHost
    0	    33	  2880	       electron_node server.js
    0	   237	  3356	       electron_node server.js
    0	    79	  6312	       electron_node tslintServer.js
    0	    34	 11904	       C:\Users\bhunscher.MATHEMATICA\.vscode\extensions\ms-vsliveshare.vsliveshare-0.3.1013\dotnet_modules\vsls-agent.exe --autoexit --pipe 311a70ccff1e4c608076662cffdf1a86 --service https://insiders.liveshare.vsengsaas.visualstudio.com/
    0	     9	  3648	         console-window-host (Windows internal process)
    0	   184	 13516	       electron_node tsserver.js
    0	    45	 11792	         electron_node typingsInstaller.js typesMap.js
    0	    38	 16136	       "C:\Users\bhunscher.MATHEMATICA\AppData\Local\Programs\Microsoft VS Code\Code.exe" "c:\Users\bhunscher.MATHEMATICA\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\json-language-features\server\dist\jsonServerMain" --node-ipc --clientProcessId=4180
    0	     6	  6768	     winpty-process
    0	     5	  5004	       "C:\Program Files\Git\bin\bash.exe"
    0	    10	 16472	         "C:\Program Files\Git\bin\..\usr\bin\bash.exe"
    0	     9	 10364	       console-window-host (Windows internal process)
    0	    35	 10304	     searchService
    0	    14	 13904	     watcherService
    0	     9	  4520	       console-window-host (Windows internal process)
    0	   185	  8748	   window (package.json - Task2_DQ - Visual Studio Code)
    0	   110	 11572	     extensionHost
    0	    42	  4928	       "C:\Users\bhunscher.MATHEMATICA\AppData\Local\Programs\Microsoft VS Code\Code.exe" "c:\Users\bhunscher.MATHEMATICA\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\json-language-features\server\dist\jsonServerMain" --node-ipc --clientProcessId=11572
    0	     3	 14544	       cmd /s /c "C:\Users\bhunscher.MATHEMATICA\.vscode\extensions\ms-vscode.csharp-1.17.1\.omnisharp\1.32.8\OmniSharp.exe -s c:\Users\bhunscher.MATHEMATICA\Desktop\ProjectWork\Task2_DQ\MACBIS_DQ.sln --hostPID 11572 --stdio DotNet:enablePackageRestore=false --encoding utf-8 --loglevel information --plugin C:\Users\bhunscher.MATHEMATICA\.vscode\extensions\ms-vscode.csharp-1.17.1\.razor\OmniSharpPlugin\Microsoft.AspNetCore.Razor.OmniSharpPlugin.dll formattingOptions:useTabs=false formattingOptions:tabSize=4 formattingOptions:indentationSize=4"
    0	   168	 13588	         C:\Users\bhunscher.MATHEMATICA\.vscode\extensions\ms-vscode.csharp-1.17.1\.omnisharp\1.32.8\OmniSharp.exe  -s c:\Users\bhunscher.MATHEMATICA\Desktop\ProjectWork\Task2_DQ\MACBIS_DQ.sln --hostPID 11572 --stdio DotNet:enablePackageRestore=false --encoding utf-8 --loglevel information --plugin C:\Users\bhunscher.MATHEMATICA\.vscode\extensions\ms-vscode.csharp-1.17.1\.razor\OmniSharpPlugin\Microsoft.AspNetCore.Razor.OmniSharpPlugin.dll formattingOptions:useTabs=false formattingOptions:tabSize=4 formattingOptions:indentationSize=4
    0	     6	 14716	         console-window-host (Windows internal process)
    0	    34	 15032	       C:\Users\bhunscher.MATHEMATICA\.vscode\extensions\ms-vsliveshare.vsliveshare-0.3.1013\dotnet_modules\vsls-agent.exe --autoexit --pipe 61f6ecad9d5a43c192815242ed8c2012 --service https://insiders.liveshare.vsengsaas.visualstudio.com/
    0	     9	 19060	         console-window-host (Windows internal process)
    0	    34	 16712	       electron_node server.js
    0	    44	 19124	       C:\Users\bhunscher.MATHEMATICA\.vscode\extensions\ms-vscode.csharp-1.17.1\.razor\rzls.exe -lsp --logLevel None
    0	     9	 13852	         console-window-host (Windows internal process)
    0	    14	 16948	     watcherService
    0	     9	 15768	       console-window-host (Windows internal process)
    0	    35	 17120	     searchService
    0	     6	 19284	     winpty-process
    0	     8	  4188	       console-window-host (Windows internal process)
    0	     5	 12156	       "C:\Program Files\Git\bin\bash.exe"
    0	    10	  9904	         "C:\Program Files\Git\bin\..\usr\bin\bash.exe"
    0	    76	 13248	   shared-process
    0	   205	 15380	   gpu-process
    5	    72	 16904	   window (Issue Reporter)

Workspace Info
|  Window (profile-view.component.ts - mpr-lane1 - Visual Studio Code)
|  Window (package.json - Task2_DQ - Visual Studio Code)
|    Folder (mpr-lane1): 277 files
|      File types: ts(87) html(69) scss(38) svg(21) ttf(19) png(10) json(10)
|                  js(5) txt(4) md(2)
|      Conf files: tslint.json(2) package.json(1) tsconfig.json(1)
|    Folder (Task2_DQ): 2607 files
|      File types: cs(667) dll(423) ts(318) html(279) xml(168) js(114) css(80)
|                  svg(58) map(50) pp(48)
|      Conf files: csproj(4) webpack.config.js(2) package.json(2)
|                  tsconfig.json(2) tslint.json(2) sln(1) gulp.js(1)
|                  settings.json(1);

Extensions (25)

Extension
Author (truncated)
Version

ng-template
Ang
0.1.11

path-intellisense
chr
1.4.2

bracket-pair-colorizer
Coe
1.0.61

vscode-eslint
dba
1.7.0

xml
Dot
2.3.2

gitlens
eam
9.1.0

tslint
eg2
1.0.40

prettier-vscode
esb
1.7.2

Python-autopep8
him
1.0.2

beautify
Hoo
1.4.7

angular2-switcher
inf
0.2.0

csharpextensions
jch
1.3.0

vscode-nuget-package-manager
jmr
1.1.6

language-haskell
jus
2.5.0

Angular-BeastCode
Mik
7.0.20

prettify-json
moh
0.0.3

mssql
ms-
1.4.0

python
ms-
2018.11.0

csharp
ms-
1.17.1

vsliveshare
ms-
0.3.1013

debugger-for-chrome
msj
4.11.1

material-icon-theme
PKi
3.6.1

LiveServer
rit
5.3.1

aspnet-helper
sch
0.6.4

autoimport
ste
1.5.3

I'm noticing rg.exe take up a lot of cpu when I open one project in particular but not others. Thanks for your help!

Can you try downloading the Insiders' build and tell me whether it happens there? https://code.visualstudio.com/insiders

It seems much better with the insider build but I went to add some of the
extensions I use and it seems the extensions are the cause of the slowness
at start up even with the insider. I see the elctron_node server.js process
taking up a lot of cpu, so I started playing the extension more and I think
VS Live Share is the main culprit.  I'm going to try working today with
that extension disabled.
I really like this extension so can I open issues for that extension or
give more precise information?
Thanks for your help
On Wed, Dec 12, 2018 at 5:15 PM Rob Lourens<EMAIL_ADDRESS>wrote:

Can you try downloading the Insiders' build and tell me whether it happens
there? https://code.visualstudio.com/insiders
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/vscode/issues/63852#issuecomment-446764578,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALq0G26pB_kTP2ApbRQErFc4c2IeP9n8ks5u4YAVgaJpZM4Y1eMo
.

elctron_node server.js

I'm not sure what that's from, yes you can open an issue on that extension's repo and have them investigate.


Quote option for vivid store

Hi I am looking at extending this addon by adding a quote option to store, so that instead of selling the products a request quote button is displayed, not price is shown and on clicking the button the user is taken to a form similar to that used in the checkout process which will the user can then submit to get an estimate or quote.
Based on my perusal of the code this should be fairly simple as it merely involves adding a few more options and creating a dedicated single page to handle the quote process. Before I go ahead with this let me know your thoughts.
In addition to the above, are there any plans to allow plugins similar to WooCommerce? I am looking at generating invoices and / or documents at the point the user submits a quote / order but figure this should really be a separate project.
Edit: Just saw Mesuva's pull request adding pricing options.

First of all, this would be pretty easy to do with CSS. You could simply hide most of the stuff that shows a price, and use the "Invoice" payment method, which wouldn't bill your users. Shouldn't need an additional single page or anything like that.
 Maybe I should ask what the goals are? What exactly would you need different, and why do you need what you need?
You can also make add-ons and extensions to this all day long and bundle it up just like any other C5 package.