Proposes a better edge coordinate svg

Hi, thanks for the library, it's really AWESOME and has helped me a lot.
I was trying to change the things a little bit on the edge coordinate SVG rect, so this is the result.
before:

after:

I know, it's not that useful at all, sorry about that, i was trying to do it on my personal project, but i decided to pull this request anyway (please, feel free to reject it). But it's basically replaces the rect by a path with a couple points that indicates a little arrow, only for left and right edges, top and bottom remains the same rect, i'm also wondering whether it should be a option to choose render as rect or a path, but it also can be unnecessary.
All examples are working fine with svg, but canvas + svg doesn't, and i'm not sure why, it still shows me the old rect, i think i missing something, i don't know...
Thanks in advance.

Thanks, this is great. If you want to try look for the drawOnCanvas method .
If you are having trouble I can add that myself.

Oh, i've missed that part, but i got it!, both are identical now.

Sorry for the delay, I am out on vacation. Will merge when I get back.

Sorry for the delay, Merged to next

http://rrag.github.io/react-stockcharts-next/documentation.html#/edge_coordinate
removed the hardcoded width: 60, height: 10, and made them to be read from props


[Suggestion] Add Option to Replace Soundtrack Tab

I love this plugin! Great work! However, would it be possible to add a setting that allows this plugin to replace/overwrite the Soundtrack tab in the quick access menu?

I second this. I personally use Spotify much more frequently than the Soundtracks library. It would be a great feature to add, I get tired of having to go into the Decky menu to pause my music.

I think I never have used the soundtrack tab tbh, so I am definitely for this!


Firewall HDFS + dependencies rules

Which issue(s) this PR fixes

Depends on:

#541
#568

Partially fixes #422
Additional comments

This PR adds firewall rules for components of the following services:

Ranger
ZooKeeper
HDFS

To test the rules from tdp-getting-started, you have to use the 212-enable-firewall branch that contains rules for Kerberos/LDAP + PostgreSQL (see TOSIT-IO/tdp-getting-started#213).
Agreements

[x] I hereby declare this contribution to be licensed under the Apache License Version 2.0, January 2004.
[x] I hereby agree to grant TOSIT a copyright license to use my contributions.

Rebased on 422-all-firewall-rules

Rebased both branches on master

Fixed the changes for #654

Ready to merge


Enable Private Endpoint Swagger specification for Databricks Service

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Changelog
Please ensure to add changelog with this PR by answering the following questions.

What's the purpose of the update?

[ ] new service onboarding
[ ] new API version
[X] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When you are targeting to deploy new service/feature to public regions? Please provide date, or month to public if date is not available yet. :-  March
When you expect to publish swagger? Please provide date, or month to public if date is not available yet. --January
If it's an update to existing version,  please select SDKs of specific language and CLIs that require refresh after swagger is published.

[ ] SDK of .NET (need service team to ensure code readiness)
[ ] SDK of Python
[ ] SDK of Java
[ ] SDK of Js
[ ] SDK of Go
[X] PowerShell
[X] CLI
[ X] Terraform
[ ] No, no need to refresh for updates in this PR

Contribution checklist:

[X] I commit to follow the Breaking Change Policy of “no breaking changes
[X ] I have reviewed the documentation for the workflow.
[X] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[X] Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.

Adding new API(s)
Adding a new API version
Adding a new service

[x] Please ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If there are following updates in the PR, ensure to request an approval from API Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in stable version
[ ] Removing properties in stable version
[ ] Removing API version(s) in stable version
[ ] Updating API in stable version with Breaking Change Validation errors
[X] Updating API(s) in preview over 1 year

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

Please move these APIs to a new api-version or try to request an exemption via the breaking change process outlined in the PR description

Please move these APIs to a new api-version or try to request an exemption via the breaking change process outlined in the PR description

As Chris suggested, create a new API or request an exception the reason is because you are updating an stable api version and is considered a breaking change.


strip out references to rustdoc's custom favicon

Starting in https://github.com/rust-lang/rust/pull/57552, rustdoc started packaging in a default column logo and favicon. We started hosting the logo in https://github.com/rust-lang/docs.rs/pull/290, but ignored the favicon, since docs.rs has its own. However, since rustdoc includes a <link rel="shortcut icon"> tag in the <head>, this overrides the behavior of using /favicon.ico, and creates a lot of extra 404s as people try to access a favicon that isn't there. This PR strips out that favicon reference, which puts a favicon back into documentation pages again.
(Note that this will also strip out custom favicons provided by crates, like the one used by Rocket. If desired, i could add in a different check that would only filter out ones rooted locally (path either begins with / or ..) which would allow custom favicons set by crates to still work.)

Alongside this, wouldn't it be simpler to generate crates with your own favicon?

We don't currently have the option for the favicon URL to be set via a CLI argument. If we did that, then we could replace this PR with one that passed --html-favicon-url /favicon.ico when generating docs, instead. However, in that case we would still have the current docs that wouldn't have been generated with that option, which would still 404 when trying to load the favicon.

Another option is to change the web server to redirect all *.ico routes to the static favicon.ico path. That would also mean not having to change upstream rustdoc, nor would it require this PR. (Finding ways to not need this PR is helpful because i'm afraid it will increase resource usage for doc page loads. >_>)

Well, that last solution sounds good! :) Meanwhile, I'll add an option to allow to pass a favicon through CLI if you want?

I managed to get the *.ico redirect working, though maybe not super-cleanly. It's posted as https://github.com/rust-lang/docs.rs/pull/340.


Multiple copies of the #target5 button show up on the left side (supposed to be just one clone, not two)

Challenge Target a Specific Child of an Element Using jQuery has an issue.
User Agent is: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36.
Please describe how to reproduce this issue, and include links to screenshots if possible.
My code:

jQuery Playground

#left-well

        <button class="btn btn-default target" id="target1">#target1</button>
        <button class="btn btn-default target" id="target2">#target2</button>
        <button class="btn btn-default target" id="target3">#target3</button>

#right-well

        <button class="btn btn-default target" id="target4">#target4</button>
        <button class="btn btn-default target" id="target5">#target5</button>
        <button class="btn btn-default target" id="target6">#target6</button>

Thanks for reporting. This is a duplicate of issue #5072. Feel free to leave any additional information in a  comment on that issue.

Thanks @BKinahan

i have the same issue.creating two clones in left well.

+1

I have the same issue, but not always. I am happy that others are experiencing the same problem so there isn't something wrong with my code

+1


Common ip_detection algorithm for bundle_adjust, stereo and ipfind

Right now, bundle_adjust, stereo and ipfind all detect interest points using different methods, resulting in varying ip distribution using similar parameters for all these methods. The ip detection is currently working the best for bundle adjustment.
While doing stereo, this becomes an issue, as the ip detected for images lacking large scale features is very less. This is many a times handled with using match-file from bundle adjustment, but this work around does not help when using map projected images for stereo.
It would be nice to have the ip detection algorithm in the same way across these 3 programs :)

You can see if the new --matches-per-tile parameter works for you. (https://stereopipeline.readthedocs.io/en/latest/stereodefault.html)
This should work with both stereo and bundle adjustment, with and without mapprojection.


Getting the Task ID

Description
Getting the task ID after the task is created so it can be used to create a second network call.
Fixes # (issue)
Type of change
Please delete options that are not relevant.

[x] New feature (non-breaking change which adds functionality)

Thanks, Vici


nixVersions.nix_2_24: 2.24.8 -> 2.24.9

Changes: https://github.com/NixOS/nix/compare/2.24.8...2.24.9

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 348038

x86_64-linux

:white_check_mark: 12 packages built:

colmena
harmonia
nil
nix-eval-jobs
nix-fast-build
nix-fast-build.dist
nix-serve
nixVersions.latest
nixVersions.latest.debug
nixVersions.latest.dev
nixVersions.latest.doc
nixVersions.latest.man

Diff LGTM but the CI is failing to build...

Diff LGTM but the CI is failing to build...

I think the test failure is pre-existing. Not sure why hydra does not run it by default. nix build --no-link github:NixOS/nixpkgs#nixVersions.nix_2_24.passthru.tests.upgrade fails here as:
$ nix build --no-link github:NixOS/nixpkgs#nixVersions.nix_2_24.passthru.tests.upgrade -L
...
vm-test-run-nix-upgrade> machine # Failed to stop nix-store.mount
vm-test-run-nix-upgrade> machine # the following new units were started: run-credentials-systemd\x2dtmpfiles\x2dresetup.service.mount, sysinit-reactivation.target, systemd-tmpfiles-resetup.service
vm-test-run-nix-upgrade> machine # [   21.495105] nixos[1020]: switching to system configuration /nix/store/jvkq0w49jqy390i39g7lyzramsz1gnjg-nixos-system-nixos-24.11pre-git failed (status 4)

It looks like a race between running a test and shutting down a VM.

Updating the fallback paths in https://github.com/NixOS/nixpkgs/pull/348411.

@trofi the upgrade test is broken because of switch-ng. There is an issue for this.

https://github.com/NixOS/nixpkgs/issues/343975

Just merged a workaround though.


Update to v1.46.3

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged) NA
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin, please rerender

Hi @hadim,
Please review/merge the PR.
Thank you.


Remove s3a testing.

So that travis-ci testing does not run over 50 minutes, remove s3a testing.

yes please +1


ansible: add TiKV raw metrics dashboard

Signed-off-by: siddontang<EMAIL_ADDRESS>Mostly we don't need to check the Raw metrics, but some users who use TiKV Raw mode only need this. So we add a new dashboard for Raw TiKV.
The page looks:

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


[DEN-456] fixed first-match bug, empty rule name diff bug

Wish there was a better way to do this; the real fix is in the API. This will do for now.


fix(release-pipes): get the release pipelines working properly

Change the release pipelines to use the release stepTemplate & add the next-version step
Add a standard release pipeline that promotes the changelog

/override pr
Why are you still here?


Rename Womble fields?

It might make sense to call them magnitude and angle? This would be a lot more explicit.

Alternatively, we can also do two methods to get the fields. This would allow keeping the internal notation short.


Mutable states

Possible argument in methods to disable states to prevent unnecessary states being added.
Eg : Not storing states of Array declare whenever arr[i][j] is used. We can just pass in an argument in the function call there to mute the state storage.

We could also add a feature for deleting variables which would be useful in preventing overcrowding when rendering
for example we can add a delete_state , whatever variable gets mentioned in delete state will be chucked out of the render.

I might use a temp variable which i dont need to keep rendered so i can delete them and maintain focus on the more important parts of the program.

As we had discussed on discord, states will be muted during the rendering process. This issue will be taken care of in client application

As we had discussed on discord, states will be muted during the rendering process. This issue will be taken care of in client application


[CARBONDATA-2265] [DFX]-Load]: Load job fails if 1 folder contains 1000 files

Problem : We are keeping the rawTablePages also in memory, but we are no where using it
Solution : Removed storing rawTablePages

[ ] Any interfaces changed?

[ ] Any backward compatibility impacted?

[ ] Document update required?

[x] Testing done
Manual Testing

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/3222/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/4455/

SDV Build Success , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/3973/

LGTM


Upgrade setup.py to pyproject.toml

Still WIP.  I may make little progress depending on my time.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

More things to do

python setup.py sdist is deprecated(setuptools has stopped maintaining it for a while) and we should be using python -m build --sdist for building sdists. Also, we should update the beam wiki with updated instructions. More information can be found at https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html#summary
Move the build-requirements.txt to pyproject.toml.

This PR is WIP


[DON'T MERGE YET] Orchestrate all requests involved for a DO measurement

After https://github.com/CartoDB/cartodb/issues/11617 and https://github.com/CartoDB/cartodb/issues/11618, we need to handle some more request in order to feed a measurement form group. Take this gist as an example of api's usage.

Blocking this until we get a clear idea about the new column field and how camshaft deals with the data from the UI.

Blocking again due to new camshaft analysis is not supporting yet boundaries, normalize and timestamp attributes. For context (https://github.com/CartoDB/camshaft/compare/data-observatory-multiple-measures).

Normalisation is integrated already, waiting for the final node in camshaft.

@nobuti is there some specific code you would like me to review?

Found the PR, working on a review.

Blocked until new issues are fixed.

So, ladies and gentlemen, say hello to the new DO UI 😄  ❤  💋


Show only collection which has NFT with various properties/attributes

~- Add Search bar~ added
Contains NFTs which are

for sale
more than X items
has a price floor in range <0.1, 0.1-0.3, 0.3-1, 1-3, 3-10, >10 (make as drop down probably) // maybe range slider as done in gallery?

~~This PR #1019 needs to be done before ~~

Link it with #1031
Link it with https://github.com/kodadot/nft-gallery/issues/1088

I'll take a look.

Shall I add "Search & Filter" bar to Collections?

@vikiival, @yangwao Shall I add "Search & Filter" bar to Collections?

Sure let's try

@TK-Development join it with #1031 please

So this is for collection page only, right? Search Bar: only search Collections whose title include the searched string? Tickbox for those:

for sale?
more than X items?

Our search bar is already doing this, this task was created a long time ago, but when it comes to other mentioned features, I think we'd rather go with toggle buttons / range slider for floor price range since we're using those in other places.

In what other places are you using those?

In what other places are you using those?

In gallery search section, when using rmrk for example:

:wave:

has a price floor in range <0.1, 0.1-0.3, 0.3-1, 1-3, 3-10, >10 (make as drop down probably) // maybe range slider as done in gallery?

is price floor in this case just the price range ( price_gt / price_lt ) or it's a special field on an nft? I've seen something like floor in series just wondering.
How do I get traded volume? sale events?


Basic modular arithmetic

This starts a series of the modular arithmetic implementation.

I wonder if in this case we may allow implicit constructor? So the user can use Modular<int,10> a = 3; instead of Modular<int,10> a(3);.
Besides, I am not sure if we should overload assignment for raw values operator=(type value) and implicit type conversion operator type().

Normally, Google-style does not like implicit conversions. However, we are working on templates already which they don't like as well. Thus, in our specific case I started to think like having implicit conversions might make the user experience better. I was even going to ask you if we could implicitly access the internal value such as:
using Mint = Modular<int, mod>;

Mint a = 15;
Mint b = 8;
Mint c = a + b * 3;
b += 19;
a = 9;
cout << a;

The above usage would feel more natural than dealing with constructors and get/set calls. Therefore, I think we should overload lots of operators and allow implicit conversions. What do you think?

The above usage would feel more natural than dealing with constructors and get/set calls. Therefore, I think we should overload lots of operators and allow implicit conversions. What do you think?

I implement the type conversion operators in this PR, and I will overload more operators in later PRs.

This implementation is interesting. It has only one template argument.
/*
using ModType = int;

struct VarMod { static ModType value; };
ModType VarMod::value;
ModType& md = VarMod::value;
using Mint = Modular<VarMod>;
*/

constexpr int md = (int) 1e9 + 7;
using Mint = Modular<std::integral_constant<decay<decltype(md)>::type, md>>;

However, it looks too complicated for this PR, and it needs lots of wrapping to become user-friendly. Maybe we can implement it in later PRs.


Kinematics.py is undocumented.

At the moment there's no documentation in kinematics.py or in the wider documentation about what this script does.

@lwc24 I don't mind writing the docs, but I need to be told what the script does first :).


scripts: retire aur-vercmp-devel

This is a simplified version of #617 that just moves aur-vercmp-devel into documentation.
Essentially decoupling the official support of aur-vercmp-devel from the suggestions of alternative ways to deal with vcs packages.

:tada:


Remove unnecessary com.sun import

An unnecessary import from com.sun prevents nd4j from building on certain JDKs.

Build triggered. sha1 is merged.

Great catch thanks!

Refer to this link for build results (access rights to CI server needed):
/job/nd4j_PR/372/

Build finished. No test results found.


Create abnrgr2

There isn't anything to merge here. Let me know if you have a map file to add here and I can assist with making a pull request.


Pass provenance information of license findings to reporters

Currently e.g. the links to findings in the StaticHTML report might be wrong:
https://github.com/oss-review-toolkit/ort/blob/38114f8eddcae108bcbd414e6cc1b115ac008b1d/reporter/src/main/kotlin/reporters/StaticHtmlReporter.kt#L516-L548
The reason is that the reporter cannot tell for sure anymore whether the path to the finding is relative to a VCS repo or to a source artifact as the provenance information is not available here anymore.
Think about how to fix that, probably by adjusting the return type of collectLicenseFindings().

This was meanwhile implemented as part of https://github.com/oss-review-toolkit/ort/pull/2802.


Add support for Outlier Detector

This PR adds support for the new Outlier Detectors feature of Grafana ML.
It supports CRUD operations for managing Outlier Detectors.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


New post: including a question on visa sponsorship in Find

 Design history: Develop a 'C' version of the visa sponsorship question on Find


insert calculated item in document according to path location

this is not going to be easy...
It is helpful to do this if we want to ensure logic updates when an item inside a repeat refers to an item inside an earlier repeat (e.g. with /path/to/repeat[position(..)-1]/node or indexed-repeat).
It could perhaps also make the engine more efficient.

iterate through or-calculated items
find corresponding node in model
iterate through all previous siblings of the node in the model starting with the nearest until one is found that has a corresponding node in the body
move the calculation to before the node found in 3 (or the start of the form if not found)

Figure out what to do with a group that has no body element.

A radical redesign of the transformation would also be an option to consider:
Instead of adding the  logic to the body, add it to the model, or keep it separate as e.g. a Javascript object.
However, this would be so radically different, that starting from scratch with a new enketo-core might be better than trying to convert the current enketo-core.


NIFI-11985 add ConsumeElasticsearch processor; NIFI-11016 add Query Builder for Elasticsearch processors

Summary
NIFI-11985 add ConsumeElasticsearch processor, allowing users to track (time) series data in Elasticsearch indices/data streams
NIFI-11016 add Query Builder for Elasticsearch processors. The new ConsumeElasticsearch processor needed a set of query builder-like properties for constructing the necessary Elasticsearch query, so extending this to all Elasticsearch processors (where appropriate) seems sensible at the same time.

Added new integration-tests for the Elasticsearch processors to cover the different ways of building Elasticsearch Query DSL
Updated reading of test data files to be more consistent with the support/nifi-1.x branch so that these and future Elasticsearch processor changes will continue to be possible for the NiFi 1.x maintenance branch

Note for merge: JsonUtils.readString will not be compatible from this PR for Java 8 (required on branch support/nifi-1.x). Instead, the merge will need to retain the JsonUtils.readString method already present on the support branch. Other changes here should be java 8 compatible
Tracking
Please complete the following tracking steps prior to pull request creation.
Issue Tracking

[x] Apache NiFi Jira issue created

Pull Request Tracking

[x] Pull Request title starts with Apache NiFi Jira issue number, such as NIFI-00000
[x] Pull Request commit message starts with Apache NiFi Jira issue number, as such NIFI-00000

Pull Request Formatting

[x] Pull Request based on current revision of the main branch
[x] Pull Request refers to a feature branch with one commit containing changes

Verification
Please indicate the verification steps performed prior to pull request creation.
Build

[x] Build completed using mvn clean install -P contrib-check

[x] JDK 17

Licensing

~[ ] New dependencies are compatible with the Apache License 2.0 according to the License Policy~
~[ ] New dependencies are documented in applicable LICENSE and NOTICE files~

Documentation

[x] Documentation formatting appears as expected in rendered files

Integration tests look good, so once the above comments are addressed, I think we're good to go.


still broken, want to validate approach

This change is

what is this PR for?  can it be broken down into smaller PRs?

Sorry, this was't supposed to actually be opened. I sent the diff over to Martin to look at the basic shape before I finished it.
No, it can't be readily broken into pieces: I need new interfaces to make the new stuff work with the old, and we can't have the interface changes without updating the things implementing those interfaces. I don't think this PR is overly large compared to our normal ones.


Add option to open URLs in the background?

Hi
After closing #364 and implementing a URL handler, I realised that Karabiner is using NSWorkspace's openURL call, which implicitly activates the application which handles the URLs.
In the case of automation apps (particularly window management), this is extremely undesirable.
So, I'm wondering if we could add an option to <vkopenurldef> that opens URLs using NSWorkspace's openURLs call, with the NSWorkspaceLaunchWithoutActivation option? Perhaps a simple <background/> tag?
If this isn't going to be possible, I'll fall back on using shell:// URLs, but I would prefer to avoid that since it involves forking two extra processes each time (/bin/sh and our command line IPC interface).
Thanks!
Chris

I've had a quick go at implementing this feature. It's not quite working yet - right now the URLs are always being loaded in the background, so I suspect I have misunderstood something about Boost or the XML compiler in Karabiner.

Updated my branch and filed PR #367 - I hope it's ok to have not used Boost booleans, they seem to be very strange, but I am very unfamiliar with Boost, so if they need to be Boosty, so be it :)


Wrong implementation in isBlank function

It seems to be a bug in isBlank function.
Fuse version:  "fuse.js": "^6.4.6",

up


Fulma Minimal Template - OSX - fake.sh doesn't have execute rights

Running: ./fake.sh build -t Watch on OSX returns the error: ./fake.sh: Permission denied
This is because the fake.sh permissions don't include execute
To make it work I fixed the permissions for that file on my mac by running: chmod 755 fake.sh
Need to change permissions on the template.

I saw it, my problem is when I create the template the file have the correct permission set.
But when installing from the template, the permission are reset to 744 something...

This is fixed in latest version of the tempalte 1.0.3


Bug: Deletion of namespaces

Bug description
Due to the change from Capsule 0.6.x to 0.7.x you've changed the CRD handling. In the past we used a special way to workaround this handling because of some issues in our deployment chain. After your new release we tried to remove that special handling.
Unfortunately  I made a big mistake over there which has deleted all the CRDs from capsule and reinstalled them. Including all our Tenants. Our pipeline recreated afterwards all the "missing" tenants.
But then, the capsule-controller started to delete all the namespaces which had now a bad owner reference which was really bad as u can imagine. Including PVCs, special config and so on and so on.
I can only blame myself for issue for sure but =>
I really struggle with the feature, that the capsule-controller was starting the delete the namespaces. I mean I could have write a script to change the owner reference, but deleting? serious?
Blame me again if I'm wrong, but after stopping the capsule-controller, the deleting of the namespaces stopped as well.
IMHO: Capsule should not delete any namespace. Even when I delete a tenant i could still to that manual by running a label filter. Or maybe you can add an option for that.
How to reproduce
Steps to reproduce the behavior (I guess, did not tested this):

install capsule
create some tenants with namespaces attached
delete the crd tenant
reinstall the crd tenant
create the same some tenants with namespaces attached

Logs
I don't have any logs as I had pressure to make a whole Kubernetes restore (disaster recovery test, check).
Additional context

Capsule version: 0.7.x
Helm Chart version: latest
Kubernetes version: 1.29.6

Hi @sybnex, Thanks for reporting that. I have had once the same issue, so I understand your frustration.
We don't delete namespaces, or at least i am not aware of that. The deletion was probably triggered by the Cascading Deletion. Since the parent tenant was deleted. I will take a wild guess and assume you just stopped the controller but left the validating-webhooks for capsule as they are. This caused the Delete Operations for namespaces to run into a timeout and therefor the deletion stopped. But I would need more information to confirm that.
The new tenants are new entities and are not matched with the old ones. The only thing that would happen from our side, is that we are dropping updates for that namespaces. Or at least with the old ownerreference.
For the internal workings we need these ownerreferences, so we can't drop these. However we could consider allowing to define finalizers on tenant basis. Then you as administrator can handle the garbage collection by yourself.
@prometherion Please correct me if I am wrong and let me know what you think about it.
Were you able to fully recover?

You're correct, Oliver, it's the cascading deletion upon a CRD deletion, and this shouldn't done to avoid these kinds of failure, sorry to hear this @sybnex.
The boundary between a Namespace and a Tenant is the Owner Reference, we have some restore scripts a customer of ours used for Velero.
Despite the outage, I'm thinking what we could do to improve the upgrade instructions, and I'm thinking the critical aspect here is about the fact we changed the lifecycle of CRDs.

Thanks for listening ... :)
We could fully recover by an etcd restore from half an hour before. Lost some PVCs where we didn't provided backup, so expected. The "badest" thing was, we had an empty Kafka afterwards and telling our devs to rerun all their pipelines. But in the end, not so bad for a full outage.
So why is the OwnerReference that hard needed? Why a label is not enough maybe with the ID of the tenant to stay unique?

Well mainly because the functionality provided is intended as is. So if a tenant is deleted, all its namespaces should also be deleted. In zhe end you would just mimic something with annotations what's already solved by ownerreferences.
Counter-Question: How about patching in finalizers manually?

So we have 131 tenants in every Kubernetes cluster. Patching the finalizer I would have to do twice in the lifetime of a tenant which makes no sense for me.
I will go with kyverno and restrict the deletion of namespaces, hopefully that helps. I already have the rule to restrict deleting tenants itself, but of course not the whole tenant crd, lol.
IMHO the deletion of the namespace is wrong for me, because even in reallife, if you delete a tenant it will take weeks to get rid of all the traces. I would start deleting deployment, services, after backup even pvs, and so on. And at the end I would delete an empty namespace with the tenant together.
Thanks for discussion, if there will be no further action this issue can be closed.
PS: @oliverbaehler we could have another round with a beer maybe ;)

I will go with kyverno and restrict the deletion of namespaces, hopefully that helps. I already have the rule to restrict deleting tenants itself, but of course not the whole tenant crd, lol.

JFI, we have a knob that allows stopping the deletion of the Tenant resource, tnt.spec.preventDeleation
   preventDeletion       <boolean>
    Prevent accidental deletion of the Tenant. When enabled, the deletion
    request will be declined.

Of course, if you delete the Custom Resource Definition, there is nothing we can do there.

IMHO the deletion of the namespace is wrong for me, because even in reallife, if you delete a tenant it will take weeks to get rid of all the traces. I would start deleting deployment, services, after backup even pvs, and so on. And at the end I would delete an empty namespace with the tenant together.

These kinds of feedback are very welcomed. We designed Capsule with self-service capabilities to decrease the operational burden, especially for the onboarding phase, as well as the offboarding such as deleting a Tenant that could be a customer, a dev environment, etc.

PS: @oliverbaehler we could have another round with a beer maybe ;)

Hey, extend the invitation, I want to join you for the beer! 🫠

Issue can be closed.
I fixed this behavior in our environment by deleting the helm secret, so that helm is not deleting the CRDs on the next run.

@prometherion FYI just implemented something similar. You can unset these fields:
					ownerRefs[i].BlockOwnerDeletion = nil
					ownerRefs[i].Controller = nil

This keeps the ownerreference, but does not delete cascading. However you are then stuck with n-ownerrefs which point to nowhere and arent reconciled.


Use clear naming rules for internal APIs

Current code base does not have any consistent rules for naming internal APIs, and most of them are indistinguishable from public APIs at first sight. It is confusing and causing some users to be frustrated with any catastrophic changes of internal APIs for which we actually do not support any compatibility between different versions. We should make them easily distinguished from public ones without carefully assessing the reference documentation.
According to PEP8, any internal APIs should be prefixed with an underscore, added to __all__ field, and public ones should be documented. The latter is achieved and is our primary way of declaring what is public, while we have been not taking care of the former practice. We should think about following the naming rule (whether to use __all__ should also be discussed). See also another section of PEP8 for class members.
In order to update our coding rule, we have to accomplish the following tasks.

Update the contribution guide
Let the future updates follow these rules
Update the current code base to follow these rules

1 and 2 are essentially not so difficult I think. Only concern is on updating all running PRs to follow these rules. 3 would be more challenging, since there are many names we should update. Most of them can be safely updated without hurting existing user codes that unintentionally depend on internal APIs: for each internal API, add a new one that follows these rules and make the old one just refer the new one with deprecation warning. It is infeasible in case of handling module-level variables etc., which do not support inserting arbitrary code on accessing like property. I think most module-level variables already follow the naming rules, so I believe it is enough to leave those that do not follow the rules as exceptions and just add comments that indicate they are internal.

The situation is getting improved, so I close it for now.


update readme

add badges
add trigger for workflow on push to main branch

Can I merge this changes @msacrea? The new code owner settings enforces me to PRs affecting workflows

Yes, that was my intention with the approval 😊.
From: dkoeni @.>
Sent: Freitag, 5. Juli 2024 12:43
To: swissfintechinnovations/ca-pension @.>
Cc: Marco Seiz @.>; Mention @.>
Subject: Re: [swissfintechinnovations/ca-pension] update readme (PR #31)
Can I merge this changes @msacreahttps://github.com/msacrea? The new code owner settings enforces me to PRs affecting workflows
—
Reply to this email directly, view it on GitHubhttps://github.com/swissfintechinnovations/ca-pension/pull/31#issuecomment-2210647160, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BCZ2DZXTR2755Y6OBSLGHQDZKZ2EJAVCNFSM6AAAAABKM5EPTGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMJQGY2DOMJWGA.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>


HTTPS issue

Anyone else having problems using the app over HTTPS? Http was working great, after https setup canvas.install is not displaying and chrome reports http 500. Besides, the blog is fetching 500 if I place the entire dir on subdomain ( lets say blog.domainname.com) . Can't get my head around this. Anyone has any idea?

How are you currently serving the app? Are you utilizing an .htaccess file or using an SSL cert?

@austintoddj
I am using apache2 along with .htaccess.
This is my .htaccess
`<IfModule mod_rewrite.c>
    <IfModule mod_negotiation.c>
        Options -MultiViews
    </IfModule>

    RewriteEngine On

    # Redirect Trailing Slashes If Not A Folder...
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule ^(.*)/$ /$1 [L,R=301]

    # Handle Front Controller...
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteRule ^ index.php [L]

    # Handle Authorization Header
   # RewriteCond %{HTTP:Authorization} .
   # RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]

    # Force SSL
      RewriteCond %{HTTPS} !=on
    # RewriteCond %{SERVER_PORT} 80
    # RewriteCond %{REQUEST_METHOD} !=POST
      RewriteRule ^ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]

</IfModule>`


Migrate testwasher gitlab parsing to new gitlab endpoint

What does this PR do?
Migrate from home made code to parse Gitlab to Gitlab lint endpoint
It should fix a bug in the flakes finder

Motivation

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

/merge


netstandard 2.1 support for your script

https://github.com/evanlindsey/Unity-WebGL-SignalR/blob/1b87bf0b2710a43b50c2a3f6a4b58cc5bd23395e/Unity/Assets/Plugins/SignalR/lib/signalr.ps1#L3
Hi Evan, great work!
I've borrowed a little snippet of code from your script and wanted to give you a heads up as I put together a similar sample you might find interesting. I do credit you on the readme.md as well.
https://github.com/WillEastbury/NetStandardSignalRShim/blob/main/FindDeploymentDependenciesSampleScript/depsfilter/downloaddeps.ps1
Only difference is the new version takes netstandard2.1 so works in later editions of unity.

@WillEastbury Thanks for sharing your script and referencing mine as the source. This response is way after the fact but I'm glad that you found it useful. I still have this repo set with 2.0 as the target and it has continued to work, even after a recent update to all project dependencies. Yours is a nice example of how it could, in fact, target a higher version. Cheers!


Live Metrics Custom Filtering

[Enter feedback here]
Unable to filter custom statistics on any of the Livestream tile stat on the dashboard.
On clicking the filter icon on the tile - I get the following response.
**Authorize connected servers
You can stream metrics and events with custom filters, which are sent back to your app. Avoid entering potentially sensitive information (such as customer ID), until you have set up an authenticated channel.Learn how to set up an authenticated channel
Your grace period to on-board your application to the recommended secure setup expired on xx-xx-xxxx**

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

ID: e3307edb-b27c-a0b9-ff1e-610630c98c15
Version Independent ID: 20262b8a-31ff-4df9-dd05-859001f24eba
Content: Diagnose with Live Metrics Stream - Azure Application Insights - Azure Monitor
Content Source: articles/azure-monitor/app/live-stream.md
Service: azure-monitor
Sub-service: application-insights
GitHub Login: @mrbullwinkle
Microsoft Alias: mbullwin

@karthiksriramuoa Thanks for your comment. We will review the issue and get back to you shortly

@karthiksriramuoa you should be able to resolve that issue by following the instructions that are described in the secure the control channel section of the live metrics docs.

@mrbullwinkle did try to follow the same article but unfortunately didn't succeed in configuring that. I have verified the instrumentation key and the Live Metrics Key and also the Dependency telemetry module is configured correctly.  Its just the QuickPulse Telemetry that has this issue.

@karthiksriramuoa Can you please let me know if you have integrated your application insights with app service or with Azure functions?

@karthiksriramuoa Just following to check if you had chance to check my previous comment.

@karthiksriramuoa GitHub issues is the primary channel for customer and community feedback about the Azure documentation.
If you need technical support via community , I would suggest you post your question here.
As there is no further response,we will close the issue for now. If there are further questions , please revert and we will be glad to assist you.


Button with icon secondary added

This is my fix :)
Button added!

Ups, forget to add: For issue #15

Good job @agon-ny
Congrats 🎉, your PR got merged. To be eligible for the swags from ClueLess. Follow this steps.

Star this repository. ⭐

SignIn / SignUp in [ClueLess Website](https://www.clueless.tech/) .

Go to profile section from the top right hand corner.

Comment your profile URL under this comment tagging the person who merged your PR.

That’s it. Follow the leaderboard !
And don’t forget to share your achievement with your friends.


gitbash run generate_librimix.sh on windows

$ sh generate_librimix.sh
0%|          | 0/20000 [00:00<?, ?it/s]
Augmenting E:/librimixdataset/LibriMix-master/librimixdataset/wham_noise\tr files
Change speed with factor 0.8
concurrent.futures.process._RemoteTraceback:
"""
Traceback (most recent call last):
File "C:\Anaconda3\lib\concurrent\futures\process.py", line 239, in _process_worker
r = call_item.fn(*call_item.args, **call_item.kwargs)
File "C:\Anaconda3\lib\concurrent\futures\process.py", line 198, in _process_chunk
return [fn(*args) for args in chunk]
File "C:\Anaconda3\lib\concurrent\futures\process.py", line 198, in
return [fn(*args) for args in chunk]
File "E:\librimixdataset\LibriMix-master\scripts\augment_train_noise.py", line 60, in apply_fx
s = fx(s)
File "C:\Anaconda3\lib\site-packages\pysndfx\dsp.py", line 413, in call
stdout, stderr = Popen(cmd, stdin=PIPE, stdout=PIPE, stderr=PIPE).communicate(stdin.tobytes(order="F"))
File "C:\Anaconda3\lib\subprocess.py", line 800, in init
restore_signals, start_new_session)
File "C:\Anaconda3\lib\subprocess.py", line 1207, in _execute_child
startupinfo)
FileNotFoundError: [WinError 2] ϵͳ▒Ҳ▒▒▒ָ▒▒▒▒▒ļ▒▒▒
"""
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "scripts/augment_train_noise.py", line 68, in
main(args)
File "scripts/augment_train_noise.py", line 40, in main
augment_noise(sound_paths, 0.8)
File "scripts/augment_train_noise.py", line 49, in augment_noise
chunksize=10
File "C:\Anaconda3\lib\site-packages\tqdm\contrib\concurrent.py", line 130, in process_map
return _executor_map(ProcessPoolExecutor, fn, *iterables, **tqdm_kwargs)
File "C:\Anaconda3\lib\site-packages\tqdm\contrib\concurrent.py", line 76, in _executor_map
return list(tqdm_class(ex.map(fn, *iterables, **map_args), **kwargs))
File "C:\Anaconda3\lib\site-packages\tqdm\std.py", line 1166, in iter
for obj in iterable:
File "C:\Anaconda3\lib\concurrent\futures\process.py", line 483, in _chain_from_iterable_of_lists
for element in iterable:
File "C:\Anaconda3\lib\concurrent\futures_base.py", line 598, in result_iterator
yield fs.pop().result()
File "C:\Anaconda3\lib\concurrent\futures_base.py", line 435, in result
return self.__get_result()
File "C:\Anaconda3\lib\concurrent\futures_base.py", line 384, in __get_result
raise self._exception
FileNotFoundError: [WinError 2] ϵͳ▒Ҳ▒▒▒ָ▒▒▒▒▒ļ▒▒▒
I dont know what to do with it.

I think this is because you haven't installed sox. It's not listed in the requirements.txt doc but is listed in the readme.md file.
conda install -c groakat sox
Hope that helps - took me a day of head scratching to find it.


Add CLA to this repo

We need to add a CLA to this repo. A copy of deepchem's should be fine.

I've added a CLA to this repo.


Prettify README.md

Signed-off-by: Atrate<EMAIL_ADDRESS>

I don't really want to change the paragraph into bullet points. Some of this reformatting is desirable, but I can't merge it as a whole. If you really want to do this I'd suggest doing it more incrementally so I don't have to reject it based on some of the changes even though other changes are desirable.


Visavis integration

Currently, it's done as simple as accessing the iframe contentWindow:
https://github.com/mpds-io/ermac/blob/a14cde6d51a8b05de7cb2d70d44cabfd849bb0ce/src_js/markup.js#L748-L749
with these functions:
https://github.com/mpds-io/ermac/blob/58033d5516e488fa8eb442469c3c4e81491c82b2/src_js/main_logic.js#L962-L1081
This causes problems if Ermac and Visavis are loaded from the different domains.
@nin-jin @PavelZubkov please could you recommend how this should be done via postMessage interface?

App inside iframe should send message first to init bidirectional communication after load.

@nin-jin @PavelZubkov @stan-donarise let's introduce a cool DX to embed Visavis in any iframe, on an example of Ermac


Create posts, Group Page Header

Feed/createPost

Allows logged in users to create posts

Group/GroupHeader

Allow users to join / leave groups

Looks like a minor conflict with root.ts causing vercel build to fail.  Please advise.

Updated root.ts.


Network namespace support

I am looking for a method to open the access point in a network namespace, such that the whole traffic from the access point would be isolated on the system. Is there already a support for network namespaces? If not, that could be a nice feature.

No it doesn't support this. But I will have a look.


Upgrade to Python 3.11

Problem
We should upgrade the Python version used in the project to Python 3.11.
Description
Python 3.11 has some nice new features and improvements so upgrading makes sense. It's also 10-60% faster (although our mileage may vary).
Changes will be needed in the following areas:

GitHub actions: actions/setup-python
Dockerfile
Pipfile
Pipfile.lock

Alternatives

We could continue to remain on Python 3.10 till it reaches EOL, although that's not a real alternative.

Sure @sahil-R, this is not high priority and can definitely wait until January.

Thank you @dhruvkb


vkquake: 1.11.0 -> 1.11.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/vkquake/versions.
meta.description for vkquake is: "Vulkan Quake port based on QuakeSpasm"
meta.homepage for vkquake is: "https://github.com/Novum/vkQuake"
meta.changelog for vkquake is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
/nix/store/6xf9kdgs6yp8vaq6az08bh5jwp4inpnl-vkquake-1.11.1/bin/.vkquake-wrapped passed the binary check.
/nix/store/6xf9kdgs6yp8vaq6az08bh5jwp4inpnl-vkquake-1.11.1/bin/vkquake passed the binary check.
0 of 2 passed binary check by having a zero exit code.
2 of 2 passed binary check by having the new version present in output.
found 1.11.1 with grep in /nix/store/6xf9kdgs6yp8vaq6az08bh5jwp4inpnl-vkquake-1.11.1
found 1.11.1 in filename of file in /nix/store/6xf9kdgs6yp8vaq6az08bh5jwp4inpnl-vkquake-1.11.1

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
0 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
vkquake

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/6xf9kdgs6yp8vaq6az08bh5jwp4inpnl-vkquake-1.11.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A vkquake https://github.com/r-ryantm/nixpkgs/archive/3131dd566cc44027a4a03678096e22bb97949279.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/6xf9kdgs6yp8vaq6az08bh5jwp4inpnl-vkquake-1.11.1
ls -la /nix/store/6xf9kdgs6yp8vaq6az08bh5jwp4inpnl-vkquake-1.11.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

vkquake

Maintainer pings

PR https://github.com/NixOS/nixpkgs/pull/150268 is updating to 1.12.1


Extendable Jimp TypeScript interface

This PR allows Jimp TypeScript interface to be extended.
For example I promisifed the getBuffer() method as
myjimp.prototype.getBufferAsync = util.promisify(jimp.prototype.getBuffer)

But without this PR I couldn't extend the interface because the entry point was a variable, rather than an interface. The variable's entry methods returned the interface.
With this PR I am able to do this easily:
import jimp from 'jimp'
import util from 'util'

interface MyJimp extends Jimp.Jimp {
	getBufferAsync(mime: string): Promise<Buffer>
}

interface MyJimpEntry extends Jimp.JimpEntry<MyJimp> {
	prototype: MyJimp
}

const myjimp: MyJimpEntry = <MyJimpEntry> jimp

myjimp.prototype.getBufferAsync = util.promisify(jimp.prototype.getBuffer)

export default myjimp

And when I am chaining methods it still works and I am getting "MyJimp" extended interface rather than the original Jimp interface.
For instance the code block below works fine with this PR:
var img = await jimp.read(body)
		const resizedBody = await img.cover(this.newSize, this.newSize)
			.quality(80)
			.getBufferAsync(this.mimeType);

Can be closed in favor of #428

@AtaS does #428 solve your issue?


Removal of the LinkedIn sharing icon

This was never used and was removed, not sure why it has crept back, but let's bin it.  I have left the image in the icon folder, justincase it gets super useful again in the future.

LGTM

Delete the image too!  It's not like we can't get it back.


[Settings>Action] : Narrator is reading in-correct information as 'Read-only' for 'Shortcut' edit field.

Windows Terminal version
1.12.3472.0
Windows build number
22509.1011
Other Software
**Test Environment: **
OS: Windows 11 Version Dev (OS Build 22509.1011)
App: Windows Terminal Preview
Screen Reader: Narrator
Steps to reproduce
**Repro Steps: **
1.Open Windows Terminal.
2.Open Settings page using 'Ctr+,'
3.Navigate to 'actions' list-item via 'Up/down' arrow keys & press enter.
4.Now Navigate to Actions present in the right pane via down arrow key.
5.Navigate to 'Edit' button present for any 'Action' via tab key & press enter.
6.A pop-up will gets open & navigate to 'Shortcut' edit field via tab key.
7.Observe the issue.
**User Experience: **
Users who rely on screen readers will get impacted here & gets disoriented, if Narrator reads in-correct information as 'Read-only' for 'Shortcut' edit field.
**Guideline Reference: **
https://www.w3.org/TR/WCAG21/#info-and-relationships
Attachments :
Narrator is reading in-correct information as 'Read-only' for 'Shortcut' edit field..zip
Expected Behavior
As 'Shortcut' edit field is editable, Narrator should not read 'Shortcut' edit field as 'Read-only'.
Actual Behavior
Narrator is reading in-correct information as 'Read-only' for editable 'Shortcut' edit field.

Closing the bug as issue has been fixed.


Failed to get home details: TypeError: Cannot read properties of null (reading 'rrHomeId')

Describe the bug
An error occurs when starting the adapter and no connection can be established to the robot vacuum.
"Failed to get home details: TypeError: Cannot read properties of null (reading 'rrHomeId')"
To Reproduce

Start adapter and the green icon appears
No value is updated in the objects. Control of the robot is not possible.
See the error in the logs

Expected behavior
The connection to the robot vacuum cleaner should be established via the Xiaomi account, status values should be updated and it should be possible to control the robot.
Screenshots & Logfiles
Logs while starting the adapter:

roborock.0
2023-10-24 09:48:54.032
error
Failed to get home details: TypeError: Cannot read properties of null (reading 'rrHomeId')

roborock.0
2023-10-24 09:48:53.587
info
starting. Version 0.4.4 in /opt/iobroker/node_modules/iobroker.roborock, node: v18.18.2, js-controller: 5.0.12

roborock.0
2023-10-24 09:48:53.041
debug
Plugin sentry Initialize Plugin (enabled=true)

roborock.0
2023-10-24 09:48:52.869
debug
States connected to redis: <IP_ADDRESS>:9000

roborock.0
2023-10-24 09:48:52.820
debug
States create User PubSub Client

roborock.0
2023-10-24 09:48:52.819
debug
States create System PubSub Client

roborock.0
2023-10-24 09:48:52.792
debug
Redis States: Use Redis connection: <IP_ADDRESS>:9000

roborock.0
2023-10-24 09:48:52.742
debug
Objects connected to redis: <IP_ADDRESS>:9001

roborock.0
2023-10-24 09:48:52.734
debug
Objects client initialize lua scripts

roborock.0
2023-10-24 09:48:52.651
debug
Objects create User PubSub Client

roborock.0
2023-10-24 09:48:52.650
debug
Objects create System PubSub Client

roborock.0
2023-10-24 09:48:52.647
debug
Objects client ready ... initialize now

roborock.0
2023-10-24 09:48:52.587
debug
Redis Objects: Use Redis connection: <IP_ADDRESS>:9001

Versions:

Adapter version: v0.4.4
JS-Controller version: js-controller: 5.0.12
Node version:  node: v18.18.2
Operating system: iobroker v6.10.1
robot: Roborock S7

Additional context
I have also tried the adapter "mihome-vacuum". There, the adapter does not even turn green at startup, but the orange triangle comes.
In the summer, everything still worked fine. I have recently updated iobroker, node and the js-controller.

Hi, you need to post a full debug log. Thanks

Problem could be solved. After multiple reinstallations of the instance, the adapter connects to the robot again.


E2E and examples tests for net-vpc module

Checklist

I applicable, I acknowledge that I have:

[X] Read the contributing guide
[X] Ran terraform fmt on all modified files
[X] Regenerated the relevant README.md files using tools/tfdoc.py
[X] Made sure all relevant tests pass

This is awesome. Have a few comments on the overall e2e testing but I'll ping you privately


Update refreshing-a-dynamic-object.md

the update to entryTTL has be replicate before the object expires. e.g. for groups it will end up with an empty membershp list when you resurrect a group from expired state.
Filed as BUG 29608897 as end-status is a group with no members on one replica, and members on the other.

@HerbertMauerer : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Thanks for your contribution! I've merged your changes and they should be live soon.


Url encoding provides wrong output / + Character not encoded

Describe the bug
Url encoding provides wrong output / + Character not encoded
To Reproduce

Goto https://gchq.github.io/CyberChef/#recipe=URL_Encode(false)&input=Y2htb2QgK3ggLi9hc2RmLmVsZg
Input will be chmod +x ./asdf.elf
Which will be encoded to chmod%20+x%20./asdf.elf using "URL encode" (Notice, that the plus is not getting encoded to %2b)
Goto https://gchq.github.io/CyberChef/#recipe=URL_Decode()&input=Y2htb2QlMjAreCUyMC4vYXNkZi5lbGY to "URL decode" the previously encoded string.
Output will now show chmod  x ./asdf.elf but is supposed to be chmod +x ./asdf.elf (The + now gets decoded as a space which is correct in the URL encoding standard, but shouldn't happen in the first because the plus is supposed to be a %2b)

Expected behaviour
URL Encoding the string, decoding the string again and getting the same string as I put in previously.
Screenshots

Desktop (if relevant, please complete the following information):

OS: Ubuntu 20.04.5 LTS (Focal Fossa)
Browser: Firefox 106.0.5 (64-bit)
CyberChef version: Version 9.49.0 Compile time: 11/11/2022 16:30:47 UTC (Official link)

This seems to be a decoding error, as + is not encoded unless "Encode all special chars" checkbox is ticked.

Found what's causing the issue:
const data = input.replace(/\+/g, "%20");

I'm not exactly sure but I believe that was there because + may be used to join together parts representing space (but wouldn't they use %20 instead?). The fix would just to remove that, or add an option to count + as a space (default should be false), as distinguishing between if a + is the literal symbol or space is impossible.
Looking at a few URL Decoding websites, some of them indeed do replace + with space, and some don't, so I will add it as a togglable option in a PR.

I see, Wikipedia says that application/x-www-form-urlencoded is

replacing spaces with + instead of %20

However, I think labelling the toggle as "replace + with space" provides more clarity instead of www-form-urlencoded.


POSIX permission operations

This adds wrapper methods and functions around NIO's POSIX operations.
The implementation is heavily based on @pathikrit's better-files library, but I've made a minor changes.

sbt IO supports 2.10 - 2.13.
I've added Scaladoc with warnings that some operations require POSIX filesystem.
better-files uses implicits everywhere to pass around the preference on whether the symbolic links should be followed etc, but seems to be planned to remove all implicits in 4.0.0. sbt IO also removes the implicits by creating two datatypes RichFile and LinkOptionPath.
My implementation is in an universal trait, partly because sbt.io.RichFile is a value class. This means File to NIO Path is happening on all operations. To cache Path like better-files's File, use LinkOptionPath.
Fixes the name isOtherReadable to isOthersReadable, following the NIO flag name.
Adds test for underlying filesystem such as IO.isPosix and IO.hasAclFileAttributeView.
In addition to IO.chmod(..), IO.chown(..) adds English name IO.setPermissions(..), IO.setOwner(..) following the sbt IO convention.

caveat
These will become new methods added to our API, so if a plugin starts using them it will bump up the minimum required sbt version to whichever that shipped this change. Thus, we should ship in a feature release 1.1.

To validate this pull request against other sbt modules, please visit this link.

A validation involving this pull request is in progress...

The validator has checked the following projects against Scala 2.12,
tested using dbuild, projects built on top of each other.

Project
Reference
Commit

sbt
1.x
sbt/sbt@34945af6314dee3c9ea55a76c882007f44819509

zinc
1.x
sbt/zinc@ef3a2c48a4e6b6126c8f1d0a99e530d64925c7d3

io
pull/76/head
sbt/io@71bd6cad84257ef9bb30c1b63b7f076d7cd88659

librarymanagement
1.x
sbt/librarymanagement@04193716da1d7454d1d7c5935b396ebeefc8c2d4

util
1.x
sbt/util@cba6f83447b84cc1e967f25a930d4f411f6f0664

website
1.x

:x: The result is: FAILED
(restart)

Nice 😎


Adding Application Insights

@255kb I just noticed #61, so let me know if you'd like me to add a short description to this, so that all future contributions include it. Thanks!

Sure why not, maybe in another PR ?

@255kb Sounds good! As soon as you merge this PR, I'll send a new one with the short description for this and the other Visual Studio and Azure items.

ok perfect :+1:


nixosTests.nginx-sandbox: remove broken test

the enableSandbox option of nginx was removed in 535896671b66d308df3ce467c94f8a9fecfdffea
Closes https://github.com/NixOS/nixpkgs/issues/262251
the test fails with
vm-test-run-nginx-sandbox> machine # [   47.753580] nginx[1142]: nginx: [alert] detected a LuaJIT version which is not OpenResty's; many optimizations will be disabled and performance will be compromised (see https://github.com/openresty/luajit2 for OpenResty's LuaJIT or, even better, consider using the OpenResty releases from https://openresty.org/en/download.html)
vm-test-run-nginx-sandbox> machine # [   47.756064] nginx[1142]: nginx: [alert] failed to load the 'resty.core' module (https://github.com/openresty/lua-resty-core); ensure you are using an OpenResty release from https://openresty.org/en/download.html (reason: module 'resty.core' not found:
vm-test-run-nginx-sandbox> machine # [   57.911766] systemd[1]: Failed to start Nginx Web Server.

upstream readme says

This is a core component of OpenResty. If you are using this module, then you are essentially using OpenResty :)

so why not just use openresty instead of a lua module?
Description of changes

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

Working variant:
diff --git a/nixos/tests/nginx-sandbox.nix b/nixos/tests/nginx-sandbox.nix
index 92ba30a09cf9..b59d9296e8a1 100644
--- a/nixos/tests/nginx-sandbox.nix
+++ b/nixos/tests/nginx-sandbox.nix
@@ -7,17 +7,8 @@ import ./make-test-python.nix ({ pkgs, ... }: {
   # This test checks the creation and reading of a file in sandbox mode. Used simple lua script.

   nodes.machine = { pkgs, ... }: {
-    nixpkgs.overlays = [
-      (self: super: {
-        nginx-lua = super.nginx.override {
-          modules = [
-            pkgs.nginxModules.lua
-          ];
-        };
-      })
-    ];
     services.nginx.enable = true;
-    services.nginx.package = pkgs.nginx-lua;
+    services.nginx.package = pkgs.openresty;
     services.nginx.virtualHosts.localhost = {
       extraConfig = ''
         location /test1-write {

Working variant:
diff --git a/nixos/tests/nginx-sandbox.nix b/nixos/tests/nginx-sandbox.nix
index 92ba30a09cf9..b59d9296e8a1 100644
--- a/nixos/tests/nginx-sandbox.nix
+++ b/nixos/tests/nginx-sandbox.nix
@@ -7,17 +7,8 @@ import ./make-test-python.nix ({ pkgs, ... }: {
   # This test checks the creation and reading of a file in sandbox mode. Used simple lua script.

   nodes.machine = { pkgs, ... }: {
-    nixpkgs.overlays = [
-      (self: super: {
-        nginx-lua = super.nginx.override {
-          modules = [
-            pkgs.nginxModules.lua
-          ];
-        };
-      })
-    ];
     services.nginx.enable = true;
-    services.nginx.package = pkgs.nginx-lua;
+    services.nginx.package = pkgs.openresty;
     services.nginx.virtualHosts.localhost = {
       extraConfig = ''
         location /test1-write {

Is there something relevant being tested that isn't tested by https://github.com/NixOS/nixpkgs/blob/master/nixos/tests/openresty-lua.nix

Move test to openresty-lua?

Yeah, I'd appreciate if the test gets moved to openresty stuff.

Yeah, I'd appreciate if the test gets moved to openresty stuff.

diff --git a/nixos/tests/openresty-lua.nix b/nixos/tests/openresty-lua.nix
index b177b3c194d7..9e987398f51d 100644
--- a/nixos/tests/openresty-lua.nix
+++ b/nixos/tests/openresty-lua.nix
@@ -16,6 +16,12 @@ import ./make-test-python.nix ({ pkgs, lib, ... }:

     nodes = {
       webserver = { pkgs, lib, ... }: {
+        networking = {
+          extraHosts = ''
+            <IP_ADDRESS> default.test
+            <IP_ADDRESS> sandbox.test
+          '';
+        };
         services.nginx = {
           enable = true;
           package = pkgs.openresty;
@@ -24,7 +30,7 @@ import ./make-test-python.nix ({ pkgs, lib, ... }:
             lua_package_path '${luaPath};;';
           '';

-          virtualHosts."default" = {
+          virtualHosts."default.test" = {
             default = true;
             locations."/" = {
               extraConfig = ''
@@ -36,6 +42,33 @@ import ./make-test-python.nix ({ pkgs, lib, ... }:
               '';
             };
           };
+
+          virtualHosts."sandbox.test" = {
+            locations."/test1-write" = {
+              extraConfig = ''
+                content_by_lua_block {
+                  local create = os.execute('${pkgs.coreutils}/bin/mkdir /tmp/test1-read')
+                  local create = os.execute('${pkgs.coreutils}/bin/touch /tmp/test1-read/foo.txt')
+                  local echo = os.execute('${pkgs.coreutils}/bin/echo worked > /tmp/test1-read/foo.txt')
+                }
+              '';
+            };
+            locations."/test1-read" = {
+              root = "/tmp";
+            };
+            locations."/test2-write" = {
+              extraConfig = ''
+                content_by_lua_block {
+                  local create = os.execute('${pkgs.coreutils}/bin/mkdir /var/web/test2-read')
+                  local create = os.execute('${pkgs.coreutils}/bin/touch /var/web/test2-read/bar.txt')
+                  local echo = os.execute('${pkgs.coreutils}/bin/echo error-worked > /var/web/test2-read/bar.txt')
+                }
+              '';
+            };
+            locations."/test2-read" = {
+              root = "/var/web";
+            };
+          };
         };
       };
     };
@@ -51,5 +84,18 @@ import ./make-test-python.nix ({ pkgs, lib, ... }:
           f"curl -w '%{{http_code}}' --head --fail {url}"
         )
         assert http_code.split("\n")[-1] == "200"
+
+        # This test checks the creation and reading of a file in sandbox mode.
+        # Checking write in temporary folder
+        webserver.succeed("$(curl -vvv http://sandbox.test/test1-write)")
+        webserver.succeed('test "$(curl -fvvv http://sandbox.test/test1-read/foo.txt)" = worked')
+        # Checking write in protected folder. In sandbox mode for the nginx service, the folder /var/web is mounted
+        # in read-only mode.
+        webserver.succeed("mkdir -p /var/web")
+        webserver.succeed("chown nginx:nginx /var/web")
+        webserver.succeed("$(curl -vvv http://sandbox.test/test2-write)")
+        assert "404 Not Found" in machine.succeed(
+            "curl -vvv -s http://sandbox.test/test2-read/bar.txt"
+        )
       '';
   })

Thanks @Izorkin


Landing page images from content item

Hero and Featured blocks will now take their image sets from the content item, and can understand the difference between hardcoded images that have to be pathed and remote images where the url can be used directly.
Related to: https://github.com/alphagov/whitehall/pull/9579
https://trello.com/c/00bwdpYL/124-images-from-whitehall

Closing because changes to Whitehall have made this PR obsolete (Whitehall is now giving us the images in the format we were already expecting).


Can O' Spam: Watch red88.work

Can O' Spam requests the watch of the watch_keyword red88\.work. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

red88\.work has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Jeff Schaller in Charcoal HQ


Multiple Forms

Hello ,
is it possible to create multiple form in a page

Yes, sure !
Just init jsonform with different schemas, on different elements

can you please give some example.


WMAgent - We alter running containers even though we  do not start two containers at the same machine

Impact of the bug
WMAgent
Describe the bug
While  testing: https://github.com/dmwm/CMSKubernetes/pull/1570 I noticed a completely unacceptable behavior in our agents running scripts, which has nothing to do with the change in question and has been there since a while now.  Here it comes:
From the very beginning we have the constraint that  we should run only one instance of the WMAgent at a machine and we were achieving that through our startup scripts, through proper containers naming conventions and tagging:
https://github.com/dmwm/CMSKubernetes/blob/7c8785f4d9ffc9ab7e3b8ffd1e2e76d0e8033c44/docker/pypi/wmagent/wmagent-docker-run.sh#L134-L139:
[[ $(docker container inspect -f '{{.State.Status}}' wmagent 2>/dev/null) == 'running' ]] || (
    [[ -h $HOST_MOUNT_DIR/srv/wmagent/current ]] && rm -f $HOST_MOUNT_DIR/srv/wmagent/current
    ln -s $HOST_MOUNT_DIR/srv/wmagent/$WMA_VER_RELEASE $HOST_MOUNT_DIR/srv/wmagent/current )

echo "Starting $registry/$repository:$WMA_TAG docker container with user: $wmaUser:$wmaGroup"
docker run $dockerOpts $registry/$repository:$WMA_TAG

And indeed it works. If there is another container  named wmagent running at the machine, we do not:

Neither create a new  link at the host pointing to the mount points of the newly instantiated agent
Nor we start the agent.....

Here follows the printouts from such an attempt:
cmst1@vocms0290:wmagent $ ./wmagent-docker-run.sh -t 2.3.8rc5  && docker logs -f wmagent
Using WMAgent version: 2.3.8rc5 under release: 2.3.8

Checking if there is no other wmagent container running and creating a link to the 2.3.8 in the host mount area.
Starting local/wmagent:2.3.8rc5 docker container with user: cmst1:zh
docker: Error response from daemon: Conflict. The container name "/wmagent" is already in use by container "22835eccc7c65887dd52dce582dfd9cfeb0f05e0e5a919998c2454531297af11". You have to remove (or rename) that container to be able to reuse that name.
See 'docker run --help'.

So the container did not actually start. Logical .. there is another one running at the machine already:
cmst1@vocms0290:wmagent $ docker ps
CONTAINER ID   IMAGE                                    COMMAND           CREATED       STATUS       PORTS     NAMES
22835eccc7c6   local/wmagent:<IP_ADDRESS>                    "./run.sh 2>&1"   2 weeks ago   Up 2 weeks             wmagent
81bb03e45332   registry.cern.ch/wmagent-couchdb:3.2.2   "./run.sh"        8 weeks ago   Up 8 weeks             couchdb

BUT..... unfortunately the execution does not stop there. Because we have few more actions to take upon container startup - all related to the runtime user hacks we had to implement upon establishing and testing the above mechanism - which was working perfectly:
https://github.com/dmwm/CMSKubernetes/blob/7c8785f4d9ffc9ab7e3b8ffd1e2e76d0e8033c44/docker/pypi/wmagent/wmagent-docker-run.sh#L140-L150
docker exec -u root -it wmagent service cron start

# Workaround su authentication issue (cron uses setuid via su)
# We inherit user accounts from the host (binding files in read-only mode)
# including the password mode (L=locked, P=password)
# If we are in password mode, reset it so we do not get authentication
# errors.
userStatus="$(docker exec -u root -it wmagent sh -c "passwd -S $wmaUser" | awk '{print $2}')"
if [ "${userStatus:0:1}" == "P" ]; then
    docker exec -u root -it wmagent sh -c "echo $wmaUser:$wmaUser | chpasswd"
fi

Now here is the rest of the printouts:
Starting periodic command scheduler: cron.
Running WMAgent container with user: cmst1 (ID: 31961) and group: zh (ID: 1399)
Setting up bashrc for user: cmst1 under home directory: /home/cmst1
Start initialization

=======================================================
Starting WMAgent with the following initialisation data:
-------------------------------------------------------
 - WMAgent Version            : <IP_ADDRESS>
 - WMAgent Release Cycle      : 2.3.4
 - WMAgent User               : cmst1
 - WMAgent Root path          : /data
 - WMAgent Host               : vocms0290.cern.ch
 - WMAgent TeamName           : testbed-vocms0290
 - WMAgent Number             : 0
 - WMAgent Relational DB type : oracle
 - Python  Version            : Python 3.8.16
 - Python  Module path        : /usr/local/lib/python3.8/site-packages
 - Current time               : 2024-11-14T10:37+00:00
=======================================================

-------------------------------------------------------
Start: Performing basic_checks

Done: Performing basic_checks
-------------------------------------------------------

check_wmasecrets: Checking for changes in the WMAgent.secrets file
check_wmasecrets: No change found.
check_wmatag: This agent has been previously initialized. Checking for WMAgent version change since last run.
-------------------------------------------------------
Start: Performing checks for successful WMAgent initialisation steps...
WMA_BUILD_ID: 386a85ff43996bfa097ad213275fa5294bd3d9668eafd1f41aafeade18423a9a
wmaInitId: /data/srv/wmagent/2.3.4/config/.initUpload
386a85ff43996bfa097ad213275fa5294bd3d9668eafd1f41aafeade18423a9a
WARNING: wmaInitId vs. wmaBuildId mismatch
-------------------------------------------------------

So what can be clearly seen is that not only those executions has proceeded on the container already running an older version at the machine <IP_ADDRESS>, but since the container entry point is always linking to the init.sh script, in order to go through all the check to estimate if this is a previously initialized agent, it suddenly finds a buildID mismatch..... !!!! :
-------------------------------------------------------
Start: Performing checks for successful WMAgent initialisation steps...
WMA_BUILD_ID: 386a85ff43996bfa097ad213275fa5294bd3d9668eafd1f41aafeade18423a9a
wmaInitId: /data/srv/wmagent/2.3.4/config/.initUpload
386a85ff43996bfa097ad213275fa5294bd3d9668eafd1f41aafeade18423a9a
WARNING: wmaInitId vs. wmaBuildId mismatch
-------------------------------------------------------

Which is again logical..... simply because the buildID of the image whose startup should have been stopped one step earlier differs. So the already running container is forced through the init process again (mostly because of the .initUpload flag - which tells us that this agent has already uploaded its configurartion at central couch). But this is not the worst part. Since the init process is triggered only partially - just for the part related to uploading configs... It actually succeeds, because it does not go through all the rest of the steps which would have caught such a huge discrepancy. The result of this is not harmful to the information uploaded to the central couch, because it must be already the same, BUT because the init succeeds,  the process changes the BUILDID recorded  in the .initUpload flag for the already running container at this machine's mount point and substitutes it with the BUILDID of the image  trying to run (which as said before should have stopped) . Which means this process is going to be forced again during the next regular restart of the original container.
Done: Performing agent_upload_config
-------------------------------------------------------
-------------------------------------------------------
Start: Performing checks for successful WMAgent initialisation steps...
WMA_BUILD_ID: 386a85ff43996bfa097ad213275fa5294bd3d9668eafd1f41aafeade18423a9a
wmaInitId: 386a85ff43996bfa097ad213275fa5294bd3d9668eafd1f41aafeade18423a9a
OK

On top of that all those  consequent steps that we were intending to execute on a fresh container are  indeed executed on the already running container:
...
Starting periodic command scheduler: cron.
...

Not a big deal so far, No harm done to the system, No wrong information uploaded to central couch, no second container started at the same machine, BUT in the future we  are calling for trouble,  especially if we happen to add more and eventually destructive operations upon container startup (at the tail of the wmagent-docker-run.sh scripts) we will get into trouble.
How to reproduce it
Try to run two containers at the same machine && READ the printouts
Expected behavior
The execution of the run scripts to halt as soon as it detects an already running container at the machine
Additional context and error message
None

Just a correction to the above  said:
I was wrong when assuming the .initUpload was filled in with the BUILDID taken from the new image. It was all resolved  at the image already running inside the container durint the docker exec -it wmagent **** calls. So the following lines were holding the correct BUILDID:
-------------------------------------------------------
Start: Performing checks for successful WMAgent initialisation steps...
WMA_BUILD_ID: 386a85ff43996bfa097ad213275fa5294bd3d9668eafd1f41aafeade18423a9a
wmaInitId: 386a85ff43996bfa097ad213275fa5294bd3d9668eafd1f41aafeade18423a9a
OK

I double checked  at the system - it is fine. So it  was a one time action, hopefully due to some unrelated previous operations...
But again, if I try to run a second container, it prevents the new one from starting, but still triggers the init mechanism at the already running container, togehter with the extra post startup exec actions  pushed from the tail of the wmagent-docker-runscript. And since this agent has been previously successfully initialized, this causes an attempt to run it, leading to a complete components restart: [1].  Again nothing bad happened... but we should NOT allow this behavior.
[1]
cmst1@vocms0290:wmagent $ ./wmagent-docker-run.sh -t 2.3.8rc5 && docker logs -f wmagent
Using WMAgent version: 2.3.8rc5 under release: 2.3.8

Checking if there is no other wmagent container running and creating a link to the 2.3.8 in the host mount area.
Starting local/wmagent:2.3.8rc5 docker container with user: cmst1:zh
docker: Error response from daemon: Conflict. The container name "/wmagent" is already in use by container "a24febdebe9b04e1c846ee95ec601feaac4e3d4713dc0c6a2dbb2313bbf55567". You have to remove (or rename) that container to be able to reuse that name.
See 'docker run --help'.
/etc/environment has been deprecated for locale information; use /etc/default/locale for LANG=C.UTF-8 instead ... (warning).
Starting periodic command scheduler: cron.
Running WMAgent container with user: cmst1 (ID: 31961) and group: zh (ID: 1399)
Setting up bashrc for user: cmst1 under home directory: /home/cmst1
Start initialization

=======================================================
Starting WMAgent with the following initialisation data:
-------------------------------------------------------
 - WMAgent Version            : <IP_ADDRESS>
 - WMAgent Release Cycle      : 2.3.4
 - WMAgent User               : cmst1
 - WMAgent Root path          : /data
 - WMAgent Host               : vocms0290.cern.ch
 - WMAgent TeamName           : testbed-vocms0290
 - WMAgent Number             : 0
 - WMAgent Relational DB type : oracle
 - Python  Version            : Python 3.8.16
 - Python  Module path        : /usr/local/lib/python3.8/site-packages
 - Current time               : 2024-11-29T14:32+00:00
=======================================================

-------------------------------------------------------
Start: Performing basic_checks

Done: Performing basic_checks
-------------------------------------------------------

check_wmasecrets: Checking for changes in the WMAgent.secrets file
check_wmasecrets: No change found.
check_wmatag: This agent has been previously initialized. Checking for WMAgent version change since last run.
-------------------------------------------------------
Start: Performing checks for successful WMAgent initialisation steps...
WMA_BUILD_ID: 386a85ff43996bfa097ad213275fa5294bd3d9668eafd1f41aafeade18423a9a
wmaInitId: 386a85ff43996bfa097ad213275fa5294bd3d9668eafd1f41aafeade18423a9a
OK
-----------------------------------------------------------------------
Start: Populating cronjob with utilitarian scripts for user: cmst1
Setting up cron jobs for the job dump.
Done: Populating cronjob with utilitarian scripts for user: cmst1!

-----------------------------------------------------------------------
_check_oracle: Checking whether the Oracle server is reachable ...
_status_of_oracle:
	 1
_status_of_oracle: Oracle connection is OK!
_check_oracle: Checking whether the Oracle database is clean and not used by other agents ...
_sql_dbid_valid: Checking if the current SQL Database Id matches the WMA_BUILD_ID and hostname of the agent.
_sql_dbid_valid: OK: Database recorded and current agent's init parameters match.
_check_couch: Checking whether the CouchDB database is reachable...
_status_of_couch:
{"couchdb":"Welcome","version":"3.2.2","git_sha":"d5b746b7c","uuid":"18f53118737ed74893055db0ffa972e2","features":["access-ready","partitioned","pluggable-storage-engines","reshard","scheduler"]}
_status_of_couch: CouchDB connection is OK!
-----------------------------------------------------------------------
MyProxy v6.2 Aug 2019 PAM SASL KRB5 LDAP VOMS OCSP
Attempting to connect to 2001:1458:d00:4a::100:480:7512
Successfully connected to myproxy.cern.ch:7512
using trusted certificates directory /etc/grid-security/certificates
Using Host cert file (/data/certs/servicecert.pem), key file (/data/certs/servicekey.pem)
server name: /DC=ch/DC=cern/OU=computers/CN=px501.cern.ch
checking that server name is acceptable...
server name matches "myproxy.cern.ch"
authenticated server name is acceptable
A credential has been received for user amaltaro in /data/certs/mynewproxy.pem.
Contacting voms-cms-auth.app.cern.ch:443 [/DC=ch/DC=cern/OU=computers/CN=cms-auth.web.cern.ch] "cms"...
Remote VOMS server contacted succesfully.

WARNING: proxy lifetime limited to issuing credential lifetime.

Created proxy in /data/certs/myproxy.pem.

Your proxy is valid until Fri Dec 06 14:32:28 UTC 2024
-------------------------------------------------------
Start: Performing start_agent
-------------------------------------------------------
Shutting down WMAgent...
Checking default database connection... ok.
Stopping components: ['WorkQueueManager', 'DBS3Upload', 'JobAccountant', 'JobCreator', 'JobSubmitter', 'JobTracker', 'JobStatusLite', 'JobUpdater', 'ErrorHandler', 'RetryManager', 'JobArchiver', 'TaskArchiver', 'AnalyticsDataCollector', 'ArchiveDataReporter', 'AgentStatusWatcher', 'RucioInjector', 'WorkflowUpdater']
Stopping: WorkQueueManager
Cannot find Daemon.xml for component: WorkQueueManager
Unable to shut it down
Stopping: DBS3Upload
Cannot find Daemon.xml for component: DBS3Upload
Unable to shut it down
Stopping: JobAccountant
Cannot find Daemon.xml for component: JobAccountant
Unable to shut it down
Stopping: JobCreator
Cannot find Daemon.xml for component: JobCreator
Unable to shut it down
Stopping: JobSubmitter
Cannot find Daemon.xml for component: JobSubmitter
Unable to shut it down
Stopping: JobTracker
Cannot find Daemon.xml for component: JobTracker
Unable to shut it down
Stopping: JobStatusLite
Cannot find Daemon.xml for component: JobStatusLite
Unable to shut it down
Stopping: JobUpdater
Cannot find Daemon.xml for component: JobUpdater
Unable to shut it down
Stopping: ErrorHandler
Cannot find Daemon.xml for component: ErrorHandler
Unable to shut it down
Stopping: RetryManager
Component RetryManager with process id 962 is not running
Stopping: JobArchiver
Component JobArchiver with process id 971 is not running
Stopping: TaskArchiver
Component TaskArchiver with process id 981 is not running
Stopping: AnalyticsDataCollector
Component AnalyticsDataCollector with process id 994 is not running
Stopping: ArchiveDataReporter
Component ArchiveDataReporter with process id 1002 is not running
Stopping: AgentStatusWatcher
Component AgentStatusWatcher with process id 1011 is not running
Stopping: RucioInjector
Component RucioInjector with process id 1024 is not running
Stopping: WorkflowUpdater
Component WorkflowUpdater with process id 1046 is not running
Starting WMAgent...

started with pid 885

started with pid 891

started with pid 913

started with pid 922

started with pid 931

started with pid 946

started with pid 956

started with pid 966

started with pid 976

started with pid 986

started with pid 995

started with pid 1005

started with pid 1023

started with pid 1033

started with pid 1044

started with pid 1054

started with pid 1063
Checking default database connection... ok.
Starting components: ['WorkQueueManager', 'DBS3Upload', 'JobAccountant', 'JobCreator', 'JobSubmitter', 'JobTracker', 'JobStatusLite', 'JobUpdater', 'ErrorHandler', 'RetryManager', 'JobArchiver', 'TaskArchiver', 'AnalyticsDataCollector', 'ArchiveDataReporter', 'AgentStatusWatcher', 'RucioInjector', 'WorkflowUpdater']
Starting : WorkQueueManager
Starting WorkQueueManager as a daemon
Log will be in /data/srv/wmagent/2.3.4/install/WorkQueueManager
Waiting 1 seconds, to ensure daemon file is created
Starting : DBS3Upload
DBS3Upload.__init__
Starting DBS3Upload as a daemon
Log will be in /data/srv/wmagent/2.3.4/install/DBS3Upload
Waiting 1 seconds, to ensure daemon file is created
Starting : JobAccountant
Starting JobAccountant as a daemon
Log will be in /data/srv/wmagent/2.3.4/install/JobAccountant
Waiting 1 seconds, to ensure daemon file is created
Starting : JobCreator
JobCreator.__init__
Starting JobCreator as a daemon
Log will be in /data/srv/wmagent/2.3.4/install/JobCreator
Waiting 1 seconds, to ensure daemon file is created
Starting : JobSubmitter
Starting JobSubmitter as a daemon
Log will be in /data/srv/wmagent/2.3.4/install/JobSubmitter
Waiting 1 seconds, to ensure daemon file is created
Starting : JobTracker
JobTracker.__init__
Starting JobTracker as a daemon
Log will be in /data/srv/wmagent/2.3.4/install/JobTracker
Waiting 1 seconds, to ensure daemon file is created
Starting : JobStatusLite
JobStatusLite.__init__
Starting JobStatusLite as a daemon
Log will be in /data/srv/wmagent/2.3.4/install/JobStatusLite
Waiting 1 seconds, to ensure daemon file is created
Starting : JobUpdater
Starting JobUpdater as a daemon
Log will be in /data/srv/wmagent/2.3.4/install/JobUpdater
Waiting 1 seconds, to ensure daemon file is created
Starting : ErrorHandler
Starting ErrorHandler as a daemon
Log will be in /data/srv/wmagent/2.3.4/install/ErrorHandler
Waiting 1 seconds, to ensure daemon file is created
Starting : RetryManager
Starting RetryManager as a daemon
Log will be in /data/srv/wmagent/2.3.4/install/RetryManager
Waiting 1 seconds, to ensure daemon file is created
Starting : JobArchiver
JobArchiver.__init__
Starting JobArchiver as a daemon
Log will be in /data/srv/wmagent/2.3.4/install/JobArchiver
Waiting 1 seconds, to ensure daemon file is created
Starting : TaskArchiver
TaskArchiver.__init__
Starting TaskArchiver as a daemon
Log will be in /data/srv/wmagent/2.3.4/install/TaskArchiver
Waiting 1 seconds, to ensure daemon file is created
Starting : AnalyticsDataCollector
Starting AnalyticsDataCollector as a daemon
Log will be in /data/srv/wmagent/2.3.4/install/AnalyticsDataCollector
Waiting 1 seconds, to ensure daemon file is created
Starting : ArchiveDataReporter
Starting ArchiveDataReporter as a daemon
Log will be in /data/srv/wmagent/2.3.4/install/ArchiveDataReporter
Waiting 1 seconds, to ensure daemon file is created
Starting : AgentStatusWatcher
Starting AgentStatusWatcher as a daemon
Log will be in /data/srv/wmagent/2.3.4/install/AgentStatusWatcher
Waiting 1 seconds, to ensure daemon file is created
Starting : RucioInjector
Starting RucioInjector as a daemon
Log will be in /data/srv/wmagent/2.3.4/install/RucioInjector
Waiting 1 seconds, to ensure daemon file is created
Starting : WorkflowUpdater
Starting WorkflowUpdater as a daemon
Log will be in /data/srv/wmagent/2.3.4/install/WorkflowUpdater
Waiting 1 seconds, to ensure daemon file is created
Done: Performing start_agent
-------------------------------------------------------
Start sleeping now ...zzz...


⚠ Bofrost.de has degraded performance

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

HTTP code: 200
Response time: 1110 ms

Resolved: Bofrost.de performance has improved in 0f75d65.


chore(oss-tasks): add type parameter to GET tasks/

Needed to complete this ticket
copied it directly from the cloud.yml file

Blocked by: https://github.com/influxdata/influxdb/issues/22653


DSD-317: Text component

Fixes JIRA ticket DSD-317
This PR does the following:

Adds DS Text component composed from Chakra's Text component.

How has this been tested?

Storybook in local build of DS

Checklist:

[x] I have updated the Storybook documentation accordingly.
[x] All new and existing tests passed.

Front End Review:

[x] View the example in Storybook

Tugboat has finished building the preview for this pull request!
Link:

https://pr715-n2ntxygibmjkb7do9j9xot6myog0tto9.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/615cba507207f264b73337fb


Update for CFK 2.2 + CP 7.0

Couple things I'm not sure about:
For migration, we say we need init-container <IP_ADDRESS>. Will this not work with init-container 2.2.0? We say this in our docs as well, so I didn't change this: https://docs.confluent.io/operator/current/co-migration.html#step-1-deploy-co-long-2-0-along-side-confluent-operator-1-x
In the confluent-platform.json in the grafana directory, we have:
"tags": [
  "6.0.x",
  "6.1.x",
  "6.2.x"
]

Don't know what those tags are for, so didn't touch it, but wondering if we should add 7.0.x

@amitkgupta thanks for the changes, we might need to add 7.0.x into the tags list as well to be consistent. these are tags associated with the dashboard, not sure of the use case of adding all CP versions though. was expecting one CP version here.

From what we recommend, we do not have to change the migration CR init container. @andrewxding can you help us understand this parameter. Are we saying post-migration, continue using the old init-container?


Cannot select which project to debug when multiple workspace folders are open

Open multiple workspace folders containing Maven Quarkus projects  in VS Code like so:
project1/
project2/
project3/

Do not open any file (ensure there are no open editors), just have the folders loaded in VS Code.
When calling the debug command (Quarkus: Debug current Quarkus project), we currently do not know which Quarkus project should be debugged.
In this case, I propose to add an input box, similar to what we already have for the Add Extensions wizard:

Something like that could help determine which Quarkus project to debug.

Please support this feature


XOR and NOT logical operators

When looking at some logic chains I am workin with in ruby I thought it would be nice to have more tools to have for logic operation chains.  The biggest problem is chaining logical operations with !.
Proposal:
Add XOR and NAND logical operators.
XOR would be !|
example:
true || true #=> true
true !| true #=> flase
true || false #=> true
true !| false #=> true

NAND would be !&
example:
true && true #=> true
true !& true #=> false
true && false #=> false
true !& false #=> false
false && false #=> false
false !& false #=> true

This does not follow other bitwise syntax I have seen but it keeps some similar idea and adds more tools for logical operations.

Pretty sure XOR is already a thing.  https://crystal-lang.org/reference/syntax_and_semantics/operators.html#binary
https://play.crystal-lang.org/#/r/9w8t
However NAND isn't a thing based on the docs at least.

I missed that in the documentation because I didn't realize it would work with bools.
This might be already mostly done.  I think that syntax will be hard to utilize on my team at work, but that is not a language problem.


[Feature Request] support other types of questions like database/shell, etc

The SQL problems seem couldn't be accessed, by using the following command:
leetcode show 175

Here is the link for 175 problem: https://leetcode.com/problems/combine-two-tables/#/description
Is there any plan to support this?
Thanks for creating this great tool.

Currently we don't support other problems beyond algorithms, while it's a good idea to support other problem sets as well. We should put this in our backlog while I'm not sure any ETA on it...

feel free to try release 1.0.0

@skygragon Thank you, I will have a try.

@skygragon works like a charm. Thanks!


tab: use python3

Motivation for this change
Things done

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

[X] NixOS
[X] macOS
[ ] other Linux distributions

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

Checked on Linux, looks good.
Don't have access to a Mac.


We use semicolons to separate fields in a TSV/CSV value. Is this the best delimiter to use?

The w3c CSV-on-the-web recommendation has the idea of a column separator which is what we're using semicolons for.  One possible answer to this issue would be to just publish some CSVW metadata defining our field delimiter (comma) and column separator (semicolon), and then we're relatively free to choose whatever we like.


Change Node URI copy

Right now LndConnect inside of Zap Desktop is under Node URI tab. This copy is inaccurate as Node URI would be pubkey@host. People seem to be fairly familiar with LndConnect now as many LN wallets and services use it. I propose we switch the tab copy to LndConnect

Fixed via https://github.com/LN-Zap/zap-desktop/pull/1773


Use ID to update local Nominatim database

Hi,
We want to make an application used by many people who update our local Nominatim database.
Can we link ID to our local Nominatim database and use it for updating?
Thanks a lot

Hi, @bidabil. I'm not 100% sure what you're asking since I don't know a lot about the Nominatim architecture.
You can point iD to any implementation of the OSM API, including a local one: https://github.com/openstreetmap/iD/blob/41e58dc32ed10e2585f25dd5e85b24900e7a182c/index.html#L51
iD also has the ability to generate OSM changefiles from the active changeset, but it might take some hacking to use this for your purposes: https://github.com/openstreetmap/iD/blob/41e58dc32ed10e2585f25dd5e85b24900e7a182c/modules/osm/changeset.js#L50
Hope that helps!


Enables RTTI and exceptions for Windows builds

Scintilla requires exception handling and RTTI to be enabled
The double tree view requires RTTI to be enabled

@exactly-one-kas I can merge it if you like

This PR is ready to merge
If a PR isn't ready I'll make it  a draft

@exactly-one-kas  have you seen my question above?

Why the doubletreeview needs RTTI? Do you have an example line of code?

DiffView and Scintilla use dynamic_cast<> functions for what reason RTTI must be enabled

Oh, I guess I remembered the wrong class

No problem, I just added as remember if we ask once why we changed it


iOS 7 Support

Is iOS 7 no longer supported?

No, if you use this library on iOS 7, add to your project manually.
Embedded framework requires iOS 8 or later.
See https://github.com/kishikawakatsumi/KeychainAccess/issues/29

You should update the Readme file specifying this next to the CocoaPods installation method. Some people might be confused since a couple of lines before it is stated that iOS 7 is supported.