Update translations.js

add German language.
Fixes #[replace brackets with the issue number that your pull request addresses].
Changes proposed in this pull request:

[list out summary of changes here]
[list out summary of changes here]
[list out summary of changes here]
[etc]

Note: pull requests without proper descriptions may simply be closed without further discussion. We appreciate your contributions, but need to know what you are offering in clearly described format. Thanks! (you can delete this text)
cc @HospitalRun/core-maintainers

Sorry for did not sign your Contributor License Agreement in the first time, Now I already sign it. And thank you for checked my pull request.

Before we consider merging this, we need someone who actually reads and speaks German to review and approve this.

@tangollama right,translation review should be done by someone who actually reads and speaks that language

@nongpp I've inquired for a German language reviewer from the community's Slack. Hopefully, someone will respond.

Some of these translations are only half translated and still include some English words

I had a quick look. There are a number of spelling mistakes and not everything is translated. Depending on the context in which the text is used, there might also be some wrong translations. In case nobody else can help, I might be able to commit some fixes over the weekend. Just let me know.

Thanks for the feedback, everyone! ❤
@nongpp could you please incorporate the feedback provided and make changes to your pull request accordingly? Thank you!

What I would recommend is to split this up into two commits and have the first commit just copy the English translation to the de-folder and the second commit actually translate. Like this reviewers can have a look at the second commit and review in the context of the original.

@nongpp any chance you're planning to address the recommended changes?


"Anghelești", "Bisericani" are listed in the drop-down menu

Description:
When user writes "Anghelești" and "Bisericani" the locations appear in the drop-down menu next to the comune and the county witch is a part according to the law
Precondition:
The website is up an running.

Step 3
Write in the search bar "Bisericani"

Expected results
The location appears in the drop-down menu as "Bisericani, Alba (Bucium)"


KeyError: 'graphql' when trying to login

I ran this code
from instaloader import *
L = Instaloader()
L.login(username,pwd)
I get this error
`KeyError                                  Traceback (most recent call last)
 in
1 L.login("ian_y0ng",'6J1anIan!')
----> 2 hasht = Hashtag.from_name(L.context,'ecofriendlykitchen')
~/opt/anaconda3/lib/python3.8/site-packages/instaloader/structures.py in from_name(cls, context, name)
1249         """:class:Profile instance of the highlights' owner."""
1250         if not self._owner_profile:
-> 1251             self._owner_profile = Profile(self._context, self._node['owner'])
1252         return self._owner_profile
1253
~/opt/anaconda3/lib/python3.8/site-packages/instaloader/structures.py in _obtain_metadata(self)
1263
1264     @property
-> 1265     def cover_cropped_url(self) -> str:
1266         """URL of the cropped version of the cover."""
1267         return self._node['cover_media_cropped_thumbnail']['url']
~/opt/anaconda3/lib/python3.8/site-packages/instaloader/structures.py in _query(self, params)
1258
1259     @property
-> 1260     def cover_url(self) -> str:
1261         """URL of the highlights' cover."""
1262         return self._node['cover_media']['thumbnail_src']
KeyError: 'graphql'
`
I have tried every fix I could find.
Instaloader version
4.7.4

If I understand it right, you omitted parts of the code leading to the problem your output describes. You try to request the hashtag ecofriendlykitchen?
This problem is described in the pinned issue #1080 which is still open.
btw. if this is your account and password, then immediately change it!


Split colorizing usernames on IRC and Twitch into two settings

Pull request checklist:

[x] CHANGELOG.md was updated, if applicable

Description

This was originally made for Dankerino. This allows you to have colorized names on IRC but not Twitch.

Upon second thoughts, I can't think of any reasons not to have this on. What are some thoughts of removing the irc setting entirely and just having it on all the time?
I understand the whole thing of "give users the option", but unlike the current twitch implementation (basically seeing which users are new), there's no specific reason to have the colours turned off.
@zneix @pajlada @Felanbird @TETYYS

What are some thoughts of removing the irc setting entirely and just having it on all the time?

Honestly I'm more surprised that with the recent IRC usercard changes, we didn't just accidentally get perfect twitch color sync.
I wouldn't mind @apa420's opinion on this, since as far as I know he's probably the only other person who uses experimental IRC, personally I don't care what approach we take.

I don't really use the irc in chatterino that much, I basically have my own chatroom open there that nobody uses.
I haven't tried this pr out, but does the historical messages you get sent by the irc server also get colorized the same way?
I'm unsure if a setting is needed for this change since there's basically no downside to it considering you can't make all names white in normal twitchchat in chatterino either.
It would make chatterino a bit more consistent in coloring.

does the historical messages you get sent by the irc server also get colorized the same way?

yes

I'm unsure if a setting is needed for this change since there's basically no downside to it considering you can't make all names white in normal twitch chat in chatterino either.
It would make chatterino a bit more consistent in coloring.

👍


[Bug]: Cannot continue to payment if shipping price is 0

Expected Behavior
You should be able to continue even if the shipping is free.
Actual Behavior
If shipping is 0 you cannot continue to payment
Possible Solution
Change the check from shipping price to if shipping provider is selected
Steps to reproduce
Set shipping price to 0
Make an order
What version of vendure integration are you using?
1.1.0
What version of Node.js are you using?
14.0
What browser (and version) are you using?
Safari
What operating system (and version) are you using?
MacOS
Relevant log output
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

I will fix this on PR


Mulitpart file uploads get stuck after upgrading to 0.9.0

I've received a pull request to pyo3-pack which upgrades reqwest to 0.9.0. Unfortunately this seems to break uploading.
The 0.8 case works and returns the expected 403:
git clone https://github.com/PyO3/pyo3-pack
cargo run -- publish -u konstin -b bin -r https://test.pypi.org/legacy/ -m hello-world/Cargo.toml -p notmypassword

If we now add the 0.9 upgrade, we are stuck with no network activity
git remote add ijl https://github.com/ijl/pyo3-pack
git fetch --all
git checkout ijl/up-reqwest
cargo run -- publish -u konstin -b bin -r https://test.pypi.org/legacy/ -m hello-world/Cargo.toml -p notmypassword

Trying to minimize this brought me to the following code.
extern crate reqwest;

use reqwest::{multipart::Form, Client};

fn main() {
    // This can be any bigger file
    let filename = "target/debug/sslbug";

    let form = Form::new().file("content", filename).unwrap();

    Client::new()
        .post("https://test.pypi.org/legacy/")
        .header("content-type", "application/json; charset=utf-8")
        .multipart(form)
        .send()
        .unwrap();
}

The code above works when uploading a small file (like Cargo.toml) but with bigger files (like its debug executable), it results in a panic without the program being terminated (I had to quit with ctrl+c):
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Error { kind: Io(Custom { kind: WouldBlock, error: StringError("timed out") }), url: None }', libcore/result.rs:1009:5
stack backtrace:
   0: std::sys::unix::backtrace::tracing::imp::unwind_backtrace
             at libstd/sys/unix/backtrace/tracing/gcc_s.rs:49
   1: std::sys_common::backtrace::print
             at libstd/sys_common/backtrace.rs:71
             at libstd/sys_common/backtrace.rs:59
   2: std::panicking::default_hook::{{closure}}
             at libstd/panicking.rs:211
   3: std::panicking::default_hook
             at libstd/panicking.rs:227
   4: std::panicking::rust_panic_with_hook
             at libstd/panicking.rs:477
   5: std::panicking::continue_panic_fmt
             at libstd/panicking.rs:391
   6: rust_begin_unwind
             at libstd/panicking.rs:326
   7: core::panicking::panic_fmt
             at libcore/panicking.rs:77
   8: core::result::unwrap_failed
             at libcore/macros.rs:26
   9: <core::result::Result<T, E>>::unwrap
             at libcore/result.rs:808
  10: sslbug::main
             at src/main.rs:11
  11: std::rt::lang_start::{{closure}}
             at libstd/rt.rs:74
  12: std::panicking::try::do_call
             at libstd/rt.rs:59
             at libstd/panicking.rs:310
  13: __rust_maybe_catch_panic
             at libpanic_unwind/lib.rs:102
  14: std::rt::lang_start_internal
             at libstd/panicking.rs:289
             at libstd/panic.rs:392
             at libstd/rt.rs:58
  15: std::rt::lang_start
             at libstd/rt.rs:74
  16: main
  17: __libc_start_main
  18: _start

rustc version: rustc 1.30.0-nightly (cb6d2dfa8 2018-09-16)
operating system: ubuntu 18.04

Weird! Would it be possible to add something like pretty_env_logger (or your preferred logger) with logs like RUST_LOG=hyper,reqwest, and include them? (Of course, if the request or response would contain sensitive info, be sure to remove it from the logs before pasting.)

Sure. Minimal example:
RUST_LOG=hyper cargo run
   Compiling sslbug v0.1.0 (/home/konsti/sslbug)
    Finished dev [unoptimized + debuginfo] target(s) in 12.60s
     Running `target/debug/sslbug`
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Error { kind: Io(Custom { kind: WouldBlock, error: StringError("timed out") }), url: None }', libcore/result.rs:1009:5
note: Run with `RUST_BACKTRACE=1` for a backtrace.
 TRACE hyper::client::pool > checkout waiting for idle connection: ("https://test.pypi.org", Http1)
 TRACE hyper::client::connect::http > Http::connect; scheme=https, host=test.pypi.org, port=None
 DEBUG hyper::client::dns           > resolving host="test.pypi.org", port=443
 DEBUG hyper::client::connect::http > connecting to [2a04:4e42:1b::319]:443
 TRACE hyper::proto::h1::conn       > read_keep_alive; is_mid_message=false
 TRACE hyper::proto::h1::conn       > flushed({role=client}): State { reading: Init, writing: Init, keep_alive: Busy, error: None }
 TRACE hyper::proto::h1::conn       > read_keep_alive; is_mid_message=false
 TRACE hyper::proto::h1::role       > Client::encode method=POST, body=Some(Unknown)
 TRACE hyper::proto::h1::encode     > sized write, len = 8192
 TRACE hyper::proto::h1::io         > detected no usage of vectored write, flattening
 DEBUG hyper::proto::h1::io         > flushed 214 bytes
 DEBUG hyper::proto::h1::io         > flushed 8192 bytes
 TRACE hyper::proto::h1::conn       > flushed({role=client}): State { reading: Init, writing: Closed, keep_alive: Busy, error: None }

pyo3-pack:
RUST_LOG=hyper,reqwest cargo run -- publish -u konstin -b bin -r https://test.pypi.org/legacy/ -m hello-world/Cargo.toml -p notmypassword
   Compiling pyo3-pack v0.3.4 (/home/konsti/pyo3-pack)
    Finished dev [unoptimized + debuginfo] target(s) in 17.61s
     Running `target/debug/pyo3-pack publish -u konstin -b bin -r 'https://test.pypi.org/legacy/' -m hello-world/Cargo.toml -p notmypassword`
Warning: You're publishing debug wheels
Built wheel to /home/konsti/pyo3-pack/target/wheels/hello_world-0.1.0-py2.py3-none-manylinux1_x86_64.whl
Uploading 1 packages
 TRACE hyper::client::pool > checkout waiting for idle connection: ("https://test.pypi.org", Http1)
 TRACE hyper::client::connect::http > Http::connect; scheme=https, host=test.pypi.org, port=None
 DEBUG hyper::client::dns           > resolving host="test.pypi.org", port=443
 DEBUG hyper::client::connect::http > connecting to [2a04:4e42:1b::319]:443
 TRACE hyper::proto::h1::conn       > read_keep_alive; is_mid_message=false
 TRACE hyper::proto::h1::conn       > flushed({role=client}): State { reading: Init, writing: Init, keep_alive: Busy, error: None }
 TRACE hyper::proto::h1::conn       > read_keep_alive; is_mid_message=false
 TRACE hyper::proto::h1::role       > Client::encode method=POST, body=Some(Unknown)
 TRACE hyper::proto::h1::encode     > sized write, len = 8192
 TRACE hyper::proto::h1::io         > detected no usage of vectored write, flattening
 DEBUG hyper::proto::h1::io         > flushed 264 bytes
 DEBUG hyper::proto::h1::io         > flushed 8192 bytes
 TRACE hyper::proto::h1::conn       > flushed({role=client}): State { reading: Init, writing: Closed, keep_alive: Busy, error: None }

For comparison, pyo3-pack with reqwest 0.8: https://gist.github.com/konstin/8df671b971ddc06b8cc0f4d4c51c31e9

Ok, I've discovered the error, it's around improperly handling back pressure on sending request bodies. It only happens when the body is bigger than 8192 bytes. Fix coming in a few minutes.

Thanks for tackling so fast, but I fear this isn't fully resolved yet. When I now run
RUST_LOG=hyper,reqwest cargo run -- publish -u konstin -b bin -r https://test.pypi.org/legacy/ -m hello-world/Cargo.toml -p notmypassword

it works as expected, but I run this without the RUST_LOG part, i.e. just
RUST_LOG=hyper,reqwest cargo run -- publish -u konstin -b bin -r https://test.pypi.org/legacy/ -m hello-world/Cargo.toml -p notmypassword

I get:
https://test.pypi.org/legacy/: connection closed
https://test.pypi.org/legacy/: connection closed

For the minimized example, I have the panic in the log again both when running with RUST_LOG=hyper cargo run and with cargo run.

Sorry, what's the difference between runs?

Sorry, I failed at copy and pasting. Edited.

So that I understand, you're saying it works correctly with RUST_LOG set, but with it disabled, it fails? About how big is the file being sent?

I made I repo with minimal reproduction: https://github.com/konstin/reqwest_348. Just cargo run causes the panic for me. The repo uses a 4MB file. Using a 47MB file also works, it just runs longer till failure.

I had some difficulty reproducing in the test suite locally since the socket buffers never fill, but found a way to trigger what was happening. Latest master should have a new fix for it spuriously thinking the connection is closed.

That fixes it, thank you!


update node from 16.17.1 to 16.20.0

This change includes a number of security fixes
In 16.18.1:

CVE-2022-43548: DNS rebinding in --inspect via invalid octal IP address (Medium)

In 16.19.1:

CVE-2023-23918: Node.js Permissions policies can be bypassed via process.mainModule (High)
CVE-2023-23919: Node.js OpenSSL error handling issues in nodejs crypto library (Medium)
CVE-2023-23920: Node.js insecure loading of ICU data through ICU_DATA environment variable (Low)
CVE-2023-23936: Fetch API in Node.js did not protect against CRLF injection in host headers (Medium)

See https://github.com/nodejs/undici/security/advisories/GHSA-5r9g-qh6m-jxff for more information.

CVE-2023-24807: Regular Expression Denial of Service in Headers in Node.js fetch API (Low)

See https://github.com/nodejs/undici/security/advisories/GHSA-r6ch-mqf9-qc9w for more information.

I think this supersedes #4237

@JamieMagee It does, yes. I'll close my PR in favour of this one.

@KonstantinTyukalov @vmapetr can this be merged? I don't have permissions to do so myself.

/azp run

/azp run


Channel editor breaks channels starting with file://

I have a channel hosted on an internal company server which I use on Windows. It's listed in .condarc as file://\\my_server/development/conda_packages although I believe it was added via conda config --add channels \\my_server\development\conda_packages.
Conda-manager doesn't like this channel and insists on prefixing it with https://conda.anaconda.org/ which breaks it.
Based on the conda docs, file:// seems to be the only other valid channel path. Could we support it? Looks like a small change is required here.

Sorry but this plugin has not been updated in a long time. We plan to fix that in a couple of months.


Fix breaking change in lv2 1.18.0

Due to a breaking change in lv2 1.18.0, various packages didn't build anymore since https://github.com/NixOS/nixpkgs/pull/86985/commits/02065f4298f6dcefef1a97643b75b6fc12ea2db2
This PR fixes the ones I have found, there might be more.
https://github.com/NixOS/nixpkgs/pull/89545/commits/21836f48599127d7e708dbf4bfbbe1d469a2cc8c should also fix https://github.com/NixOS/nixpkgs/issues/87819

Motivation for this change
Things done

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

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

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[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.

Thank you.

@jtojnar Thank you!
If you are interested, I have a bunch of other, mostly audio related, PR's open!  ;)


#180 Fix flight recorder profiler's jcmd resolution

jcmd resolution was failing on my computer because the root of JDK installation was not named jre (it is a system JRE installation that I haven't named myself). As a result the following code
jcmd = Paths.get(jvm.replace("jre/bin/java", "bin/jcmd"));

didn't match-replace which resulted in a wrong process running, so I replaced it with:
jcmd = Paths.get(jvm.replace("bin/java$", "bin/jcmd"));

In the process or figuring out how to publishLocal for sbt 1.0 I updated the build configuration, so this PR will most likely require some polishing about: publishing and/or running scripted tests.

Hello guys, whats going on with this issue? I've met the same problem and looking for workaround

Could you explain why Paths.get(jvm).resolveSibling("jcmd") gives a different answer to Paths.get(jvm.replace("bin/java$", "bin/jcmd") in your system?
I recently contributed these profilers to JMH core. The plan is to remove them from sbt-jmh soon.  If I can understand this bug better, I'll submit the fix to https://github.com/openjdk/jmh/blob/3966fdef054e26c1cf0f899065aebb13f0947f24/jmh-core/src/main/java/org/openjdk/jmh/profile/JavaFlightRecorderProfiler.java#L198.


Difficult to tell selected server group color

Azure Data Studio Version: 1.7.0

Steps to Reproduce:
Create new server group and click a color box - the outline is very small and not easy to see for some of the colors.

The Server Group UX has been improved since this issue was opened to more prominently display the selected color.  This is what the color picker currently looks like with a selected item.  Thanks!


Problem with Widget

I am tried  to add widget in my some lunches (smart luncher 6, Flow luncher) but initially its shows properly but after a sec its shows nothing and collapse.

https://github.com/user-attachments/assets/3a6a17fd-608c-445b-b394-910e1edfd541


Perf benefit to keeping subscription count low?

Hi, I’m building a chat app where messages can sometimes be reported/upvoted, and I need to show the votes as they happen.
Currently I have two Lists, one called messages where the client only takes a snapshot of each message Record in the list, and the second list called messageSubs where the client subscribes to each Record in that list. All messages are always added to messages, and copied to messageSubs when they get voted on (messagesSubs is always a subset of messages). That way the client will only subscribe to messages that change votes. I expect the majority of messages won’t be voted on and therefore don’t need to be subscribed to.
What I’m wondering is, is there any real performance/reliability benefit in keeping the subscription count low? I did this because seemed wrong to have to client subscribe to every single Record. However if there only negligible benefit, I may just get rid of messageSubs and have the client subscribe to all messages.

Hello,
Could you tell us how many messages and clients are expected to be handled?
Regards
On Fri, Jun 1, 2018, 01:22 Tim Mun<EMAIL_ADDRESS>wrote:

Hi, I’m building a chat app where messages can sometimes be
reported/upvoted, and I need to show the votes as they happen.
Currently I have two Lists, one called messages where the client only
takes a snapshot of each message Record in the list, and the second list
called messageSubs where the client subscribes to each Record in that
list. All messages are always added to messages, and copied to messageSubs
when they get voted on (messagesSubs is always a subset of messages).
That way the client will only subscribe to messages that change votes. I
expect the majority of messages won’t be voted on and therefore don’t need
to be subscribed to.
What I’m wondering is, is there any real performance/reliability benefit
in keeping the subscription count low? I did this because seemed wrong to
have to client subscribe to every single Record. However if there only
negligible benefit, I may just get rid of messageSubs and have the client
subscribe to all messages.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/deepstreamIO/deepstream.io/issues/897, or mute the
thread
https://github.com/notifications/unsubscribe-auth/ACaj6sMRuLcLvJCqTuy8F4XPGpKnXsi2ks5t4IlCgaJpZM4UV65n
.

The app hasn't launched yet, so these are all estimates; just trying to figure if there's any benefit to managing the lists one way or the other. There will be many chat Rooms (possibly into the hundreds, but let's say I want to handle 300 rooms). I'd expect maybe 30 clients per room, and each room holds 50 messages; of which maybe 5-10 messages may need to be subscribed to. In other words, with the current implementation a single client takes a snapshot of 50 message Records and subscribes to ~5 of those message Records. I'm wondering whether this is actually any better than simply having the client subscribe to all 50 messages.

The logic in the server does loop over subscriptions, however it has been optimised massively by us and other OS contributors and so shouldn't make a massive different. The only two issues is when a client disconnects we have to cleanup all the subscriptions and when they connect we have to run each individual one through permissions. I know this is a bit late of a response but it's a really good question!


Done translation of home section. Completed #29, #30, #31, #32, #33

Spanish translations is ready. (Home Section)

Gracias @effexts!!! :raised_hands:


*.msu not found, the doc description incorrect

No any .msu

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

ID: ad07ea10-b00f-48cd-534d-b1ad1bfaa44b
Version Independent ID: 41c511f9-54b4-07df-d0a5-c2f547fdf293
Content: Redistributable Framework Components - Windows drivers
Content Source: windows-driver-docs-pr/wdf/installation-components-for-kmdf-drivers.md
Product: windows-hardware
Technology: windows-devices
GitHub Login: @tedhudek
Microsoft Alias: tedhudek

Hi @GreatFireWall thanks for the feedback and apologies for the delay.    So thank you for starting this process!
Please see the updates here:
https://docs.microsoft.com/en-us/windows-hardware/drivers/wdf/installation-components-for-kmdf-drivers
https://docs.microsoft.com/en-us/windows-hardware/drivers/wdf/building-and-loading-a-kmdf-driver


Incorrect reference to Sparklr app in Tonr app pom.xml (OAuth 1 example apps)

When running the sample OAuth 1 Tonr app with mvn tomcat7:run command, trying to access Sparkl app results in a 404 Not Found error.
The reason, apparently, is that in samples/oauth/tonr/pom.xml file configuration for the tomcat7-maven-plugin reference to the Sparklr app looks like: <contextPath>/sparklr2</contextPath>

Thanks for the PR this is now fixed via e30a7af8b1a98fe858fbf1c1448e4b88c3ea6c4a


why is function python_stratified_split very slow?

i have 3M transaction load function python_stratified_split is very slow?
have method ? improve speed split data before training?

@ChuyangKe this can be fixed with your PR https://github.com/microsoft/recommenders/pull/1802


Created feedback form

an update on feedback form coded in simple html
What does this PR do?
Add resource(s) | Remove resource(s) | Add info | Improve repo
For resources
Description
Why is this valuable (or not)?
How do we know it's really free?
For book lists, is it a book? For course lists, is it a course? etc.
Checklist:

[ ] Read our contributing guidelines.
[ ] Search for duplicates.
[ ] Include author(s) and platform where appropriate.
[ ] Put lists in alphabetical order, correct spacing.
[ ] Add needed indications (PDF, access notes, under construction).
[ ] Used an informative name for this pull request.

Follow-up

Check the status of GitHub Actions and resolve any reported warnings!

Where are you going to put down the HTML Files the repo doesn`t have any, have you tested on your local machine before opening a PR?

not interested


Updated toc and index pages

Docs Build status updates of commit 42bb2d0:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-conceptual/azps-6.6.0/azps-msgraph-migration-changes.md
:white_check_mark:Succeeded

docs-conceptual/azps-6.6.0/azps-versioning-release-cadence.md
:white_check_mark:Succeeded
View (azps-6.6.0)

docs-conceptual/azps-6.6.0/index.yml
:white_check_mark:Succeeded
View (azps-6.6.0)

docs-conceptual/azps-6.6.0/toc.yml
:white_check_mark:Succeeded
View (azps-6.6.0)

docs-conceptual/azps-7.1.0/toc.yml
:white_check_mark:Succeeded
View (azps-7.1.0)

docs-conceptual/azps-7.2.0/toc.yml
:white_check_mark:Succeeded
View (azps-7.2.0)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


cg_iRIC_Read_Grid2d_Str_Size fails when fastmech contains 3d results

cg_iRIC_Read_Grid2d_Str_Size fails when the cgns file contains both 2d and 3d grids
Two unit tests were added to unittests_cgnsfile to demonstrate:
void case_GridRead_FaSTMECH();
void case_GridRead_FaSTMECH_3d_results();     // FAILS in iriclib_v4
The equivalent cases were also added to i-RIC/iriclib to be merged by pull request i-RIC/iriclib#92
Here's the original i-RIC v3 project:
fm-ex3.zip

Hi Scott,
I'm sorry, I should have noticed earlier, I think I know how to fix this.
Please use cg_iRIC_Read_Grid2d_Str_Size_WithGridId, instead of cg_iRIC_Read_Grid2d_Str_Size().
I mean, use
call cg_iRIC_Read_Grid2d_Str_Size_WithGridId(fid, 1, isize, jsize)

instead of
call cg_iRIC_Read_Grid2d_Str_Size(fid, isize, jsize)

because, when there is the 3d results, call cg_iRIC_Read_Grid2d_Str_Size try to get information from last grid, that is 3d grid.

Hi Keisuke,
That did work.  But it seems to be redundant.  If the grid_id is always 1 for the 2d grid then isn't the grid_id unnecessary?
Thanks,
Scott

Hi Scott,
Thank you for the contact, and glad to hear that it worked.
I understand that you feel it redundant.
Actually, the grid with gridid 1 is 2d grid, and grid with gridid 2 is 3d
grid in FASTMECH’s case, so I think cg_iRIC_Grid2d_Str_Size should refer to
grid with gridid 1.
I think I can fix it. I’ll work on it, and contact you when I’ve got
progress.
Thank you,
Keisuke
2022年5月18日(水) 6:33 Charlton, Scott R. @.***>:

Hi Keisuke,
That did work. But it seems to be redundant. If the grid_id is always 1
for the 2d grid then isn't the grid_id unnecessary?
Thanks,
Scott
—
Reply to this email directly, view it on GitHub
https://github.com/i-RIC/iriclib_v4/issues/25#issuecomment-1129337229,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA6YIUMKX5GFM4VMXXZT4ZLVKQGBBANCNFSM5KCF6G6Q
.
You are receiving this because you commented.Message ID:
@.***>


Added android device id to android device info

I signed it!

Hi @BWMuller would you be able to address the comments on this PR?

@kroikie Completely forgot about this PR. Have made the changes as indicated

@BWMuller Thanks for updating the PR, if you would bump the version to 0.3.0 and add an entry in the changelog I'll be happy to merge.

@kroikie Have bumped the version and updated the branch with master to resolve the conflicts

this is an awesome and important update! @kroikie do you have an estimate when 0.3.0 will be released to the registry?


💡[FEATURE] preloader

Description
I would like to add a preloader to the site . It would be matching the UI of the site and would be fully responsive . It would render until the page is being loaded . Kindly assign this issue to me under GSSoC'24
Screenshots
No response
Checklist

[X] I have checked the existing issues.
[X] I have read the Contributing Guidelines
[X] I have read the Code Of Conduct
[X] The changes don't break the code

@Muskansahuincredible  i want to work on this issue


v1.0.1 Removes support for Ruby 2.7, breaking existing installations

Describe the bug
Version 1.0.1 removes support for Ruby 2.7. This is a breaking change that affects anyone running Ruby v2.7 and has this listed as a dependency.
To Reproduce
N/A
Expected behavior
The removal of support for a Ruby version should be done as a major version change. This would avoid inadvertent breaking changes when making patch updates.
My environment

Affects my production application: YES
Ruby version: 2.7
OS: N/A

We do not think this is a breaking change. It only prevents a project from updating to a newer version, it does not break any existing code.
Updating required ruby versions helps us support gems by not testing across all the rubies that were actual at the time of a 1.0 release. This is both time consuming and making code more complicated than it could be. Releasing major versions when supported ruby versions change would be even less practical given we have so many gems to release. For instance, releasing dry-core 2 would require releasing all its direct dependencies, it's > 10 gems.

I agree that maintaining multiple versions to support outdated ruby versions is not desired. I am not asking that future updates consider being compatible with Ruby 2.7. The issue is that removing a supported ruby version as a patch update breaks Semantic Versioning in that the change is not backwards compatible. Ideally a backwards incompatible change would be made in a major version release and all future changes go forward with that version.
Anyone still using Ruby 2.7 would then be able to stay on v1 without having to pin to a specific patch version. No new updates are needed to v1, v2 would be where any future changes would live.
At the very least, could a note be added to the changelog to point out that support for Ruby 2.7 has been removed in version 1.0.1?

Actually, it's normally done like that. We should have released 1.1 and mentioned it properly in the changelog. Alas, our sophisticated maintenance workflow sometimes makes it hard to track such changes. I'll add the change to the changelog tomorrow.

Thank you, appreciate the update here and your work on this gem!

Applied in https://github.com/dry-rb/dry-core/commit/9e2e11d3f80731afbc13c7fc3184e72bcd93fa54


fix(datepicker): remove label

Removed label from the directive. If developers want to include a label, can use the <uif-label /> directive.
Closes #295.

I've just noticed that in this case if developers would want to include a label it would fall outside of the <div class="ms-DatePicker"> element. I'm not sure if it's an issue but it leads to a different rendering than the original Office UI Fabric component.

Ugh... that sucks because I bet that applies to other directives as well and thus, we would not only have to include a label attribute for all directives in addition to the normal label. Have you looked at other directives too?
If others have the same problem, then we need to figure out if this is something to raise with Office UI Fabric, or if we can come up with a single solution for all directives... like including a label control within the directive to be transcluded. Is that something you tried?

No, I haven't looked at other directives yet and I didn't have a chance to compare the rendering of the label outside of the directive. Transclusion could be an option unless we're already using it. Given that the label needs to go in a specific location in the rendered markup we could use transclude only if the directive itself doesn't wrap any other contents.


Import package

Are those part of the public facing API? Then it would be awesome to see some docstrings. Spontaneously I'm not sure when I would use those, what package is in this context (reading the source, I assume a zip archive of some sort - is this specific to models (I suppose it isn't)). Also when would I want to use the raw_node vs the non-raw-node version of the functions.

Yes, I added some doc stirings.
Currently we only package models, but that might change. All IO is supposed to be somewhat agnostic to RDF type (and version).

maybe load_node and load_raw_node should just also accept file path/URLs to packages? we could just decide based on extension? (.yaml vs .zip) and then absorb import_package...

maybe load_node and load_raw_node should just also accept file path/URLs to packages? we could just decide based on extension? (.yaml vs .zip) and then absorb import_package...

I think it make sense to combine all these.
For the node and raw_node, can we discuss a bit on an alternative name for node which is more intuitive? The node sounds like we are dealing with a tree (is that because of the yaml structure is like a tree?).
I might misunderstand the concept, but after loading a model RDF, shouldn't we get a sort of Model instance which has a bunch of attributes and functions? Then if it's raw_node, can we call it something like ModelConfig?

maybe load_node and load_raw_node should just also accept file path/URLs to packages?

I agree, I would also overload it such that this supports both rdfs and zipped folders.

For the node and raw_node, can we discuss a bit on an alternative name for node which is more intuitive? The node sounds like we are dealing with a tree (is that because of the yaml structure is like a tree?).
I might misunderstand the concept, but after loading a model RDF, shouldn't we get a sort of Model instance which has a bunch of attributes and functions? Then if it's raw_node, can we call it something like ModelConfig?

I think Node comes from marshmallow?! I also don't find it intuitive here.

'node' comes from the tree. I totally agree that it's not intuitive. It's too general. Within the code it makes some sense, but in the exposed functions it should carry different names, maybe resource as it comes form the resource description file?
raw_resource and resource or evaluated_resource?
The naming of raw vs ' '/'evaluated' could also do with an update..

'raw': content from the RDF yaml but as annotated dataclass structure with some more pythonic types (paths are pathlib.Paths not str, etc)
'' ('evaluated'): enriched with convenience functionality, e.g. imported source code, urls are resolved to local (cached) pahths, etc..

I might misunderstand the concept, but after loading a model RDF, shouldn't we get a sort of Model instance which has a bunch of attributes and functions? Then if it's raw_node, can we call it something like ModelConfig?

to clear this up (using the current terms):

a model RDF can be loaded with load_raw_node to yield a pythonic representation of its raw content. (with full type annotations and based on dataclasses)
a model RDF or a raw_node can be loaded with load_node to do the above and transform the raw_node with a fixed set of NodeTransformers: URLs are downloaded and replaced by local cached paths ('resolved'), source code is imported and available as a callable ImportedSource node.

transformations from raw node to node:
https://github.com/bioimage-io/spec-bioimage-io/blob/4c6b467c62d9d6ccd0e059156e8aca71607ac276/bioimageio/spec/shared/utils.py#L343-L348
(As some nodes might not be transformed, some resolved nodes are identical to raw nodes.)
As we look at the model information as a tree I find the node term acceptable in the code, but it is not useful to expose. Thus my above suggestion to use resource instead...  But I would be totally fine with changing it to config.Model and raw_config.Model instead or also raw_config.ModelRawConfig (or maybe raw_config.RawModelConfig?) and config.ModelConfig. We used to avoid 'config' as we used to refer to the model RDF as a model config and we needed something distinct. But in our current situation I like 'config' more and more...
def resolve_raw_config_to_config(raw_config: GenericRawConfig, root_path: os.PathLike, configs_module: ModuleType) -> GenericConfig:
     """resolve all uris and sources"""
     config = UriConfigTransformer(root_path=root_path).transform(raw_config)
     config = SourceConfigTransformer().transform(config)
     config = RawConfigTypeTransformer(configs_module).transform(config)
     return config

Additional functions could be added to the (resolved) node objects (not the raw nodes!), but currently they do not implement anything.

I think renaming node to resource in the user facing functions is a good start. I would not call it anything with model, because it can represent both models or other types of rdfs (at least that's how I understand it). We could also call it resource_description, to map more closely to rdf.
Also, I think resolve_raw_x_to_x should just be called resolve_raw_x.

We could also call it resource_description, to map more closely to rdf.

how about renaming 'package' to 'resource_package' to emphasize their analogy?

how about renaming 'package' to 'resource_package' to emphasize their analogy?

Do you mean, for example import_package -> import_resource_package? I think that's a good idea, also because package is a bit too generic for my taste.

Do you mean, for example import_package -> import_resource_package? I think that's a good idea, also because package is a bit too generic for my taste.

yes, exactly!

after merging #204 this PR should be ready to be merged as well...


Support IAsyncEnumerable if STJ serializer is being used

Fixes #1317

Newtonsoft supports this type, too. Is this going to happen any time soon? I See this issue is pretty old already.


Deep Mocking

Hi,
Thanks for the great library, so far it's been a great experience. However, I've run into an issue. When using Prisma, we have a provider which wraps around the Prisma client and is then injected into other modules for use in their respective services. Unfortunately, because the current mocks created by Automock are shallow, it errors when the service tries to call the Prisma model handlers since they exist at the "third" level in the mock. For example, with a given service class, I would call this.models.MY_TABLE.findUnique(), where models is the PrismaClient, MY_TABLE is the table name and findUnique is the query. So findUnique ends up being empty since models is only a shallow mock.
Here's a quick example
   constructor(
        private models:  PrismaWrapperService,
    ) {
       // FindUuique is undefined
        this.models.user.findUnique(...somequery);
    }

Is there currently any way to either override the class mocks created by Automock or to instruct it to deeply mock a provider?

Hello @jasonmacdonald,
Thanks! Happy to hear that :)
The feature for deep mocking is currently under development and not yet available.
In the meantime, kindly attempt the subsequent resolution:
First, let's define the class:
export class ClassWithModels {
   constructor(
        private models:  PrismaWrapperService,
    ) {
        this.models.user.findUnique(...somequery);
    }
}

Next, let's assume that this is the beforeAll section of the unit test:
  beforeAll(() => {
    const { unit, unitRef } = TestBed.create(ClassWithModels)
      .mock(PrismaWrapperService)
      .using({
        models: {
          user: {
            findUnique: jest.fn(),
            find: jest.fn(),
          },
          animal: {
            findUnique: jest.fn(),
          },
        },
      })
      .compile();
  });

I understand that this solution may not be optimal, but it can serve as a temporary workaround until the release of<EMAIL_ADDRESS>Also, I guess you don't use all the models in your class, so just put stubs on whatever models you need.
Let me know if it works for you!


Maybe first deprecate calc.nan before removing it immediately

In Typst 0.12, calc.nan is moved to float.nan (which makes total sense). However, this breaks projects using the old version. I'm all for a breaking change but maybe calc.nan could be deprecated for just one version or so for two reasons:

It makes comparing 0.11 and 0.12 hard (in my case, I need to calc.nan to float.nan in almost a dozens of places and across different files. The way it is now, I can't just switch without replacing all these occurrences each time.
There may be packages using nan internally which would break immediately.

We did it this way because there is no infrastructure for deprecating constants at the moment. We checked typst/packages and found no occurance of calc.nan, so we figured that it wasn't really used in the wild. But I guess we can add it back in if that's untrue.

Okay, I understand.
In my case, it is a package-in-progress ..

But not too wild, I just wanted to compare performance and make use of the transparent png export of 0.12


Date filter is ignoring the format parameter

Current behavior
I'm trying to change the format of a date within a template using the date filter:

{{ item.created_at | date('format as a parameter here') }}

But the date filter is in fact not using the parameter at all:
https://github.com/DivanteLtd/vue-storefront/blob/d40ba3b958c26d77d2d4c98bdf403af1ffd19275/core/filters/date.js
And therefore the date is always returned in the same format (e.g. 25.6.2019, 11:50:32).
Expected behavior
I should be able to choose the format when using the filter.
Steps to reproduce the issue
Try to pass any argument to the date filter within a template:

{{ item.created_at | date('format as a parameter here') }}

No matter what you pass in, nothing happens.
Repository
The latest commit for the file in the current master branch: https://github.com/DivanteLtd/vue-storefront/blob/d40ba3b958c26d77d2d4c98bdf403af1ffd19275/core/filters/date.js
Can you handle fixing this bug by yourself?

[ ] YES
[x] NO

Which Release Cycle state this refers to? Info for developer.
Pick one option.

[ ] This is a bug report for test version on https://test.storefrontcloud.io - In this case Developer should create branch from develop branch and create Pull Request 2. Feature / Improvement back to develop.
[ ] This is a bug report for current Release Candidate version on https://next.storefrontcloud.io - In this case Developer should create branch from release branch and create Pull Request 3. Stabilisation fix back to release.
[x] This is a bug report for current Stable version on https://demo.storefrontcloud.io and should be placed in next stable version hotfix - In this case Developer should create branch from hotfix or master branch and create Pull Request 4. Hotfix back to hotfix.

Environment details

Browser: Any
OS: Any
Node: Any
Code Version: v1.9.1

On it


react-dom-stream

https://github.com/aickin/react-dom-stream

That looks good. Have you been using it? What do you set the buffer size to?

I saw that. Let's wait for stable release.

I haven't used it. Just putting it up here since it looks quite interesting.

@ronag Thank you for raising it.

This belongs to wiki tips I believe.


Feature request: horizontal scrolling across columns

My app has more columns than can comfortably fit in the width of the typical browser window. When Clarity's datagrid overflows horizontally, however, it forces a horizontal scrollbar across the entire page.
I would like just the header and rows to scroll. The footer should remain static. And if the columns comfortably fit within the page width, no horizontal scrollbar should be present.
I've already tried several ways to add the scrolling manually using the CSS overflow-x property on grid elements, but no matter what it seems to expand the entire page.
An example of perfect grid scrolling behavior is here:
https://www.ag-grid.com/example.php#/

@colinskow - please use the issue template when filing issues.
In this case an example (we provide starter stackblitzes for multiple versions) would help here. As far as I know in both v1 and v2 the footer stays static and only the header/rows will scroll when columns expand beyond the datagrid container.
Please create an example stackblitz that demonstrated what you describe.

Okay, I can confirm this is working correctly in StackBlitz on both V1 and V2. Which means I must be doing something to screw it up on my end.
https://stackblitz.com/edit/clarity-light-theme-v2-ffeqaf

If you can isolate your issue in a stackblitz feel free to post the link here. I'm happy to have a look at the code.


Support intellisense in workbench.editorAssociations

@mjbvz Do you mind linking the codepointer you had for this again? I lost it from when it was posted awhile ago. If not I'll just go hunting for more samples :)

Yes this used to work but I think this change deleted the code
The key part was where it was updateEditorAssociationsSchema and the original schema definition using anyOf. The same general approach should work with an object literal instead of the array, but you'll have to update the schema structure

@lramos15 sounds like this was behaving better than other settings and it's good to show all editors imo.

There is a command to get a list of all registered editors for auto-locking

You mean I can use the resolver service to get all registered editors right? Would that account for custom editors from extensions (like Hex editor) too?

You mean I can use the resolver service to get all registered editors right? Would that account for custom editors from extensions (like Hex editor) too?

Yeah, I don't know why I called it a command it's just a method on the editor resolver service. This function in particular https://github.com/microsoft/vscode/blob/ed3cf121498c6ce57ffbadf831e5d7b9f8222a6e/src/vs/workbench/services/editor/common/editorResolverService.ts#L153-L158 although would need to add a flag for all editors as we ignore exclusive editors since this function is primarily there to know when to show the open with context menu

Nothing crazy but I feel anything crazier might be annoying. We just now suggest editor Ids for whatever key you choose.


Transaction broken during long session

My rdf loader is fragile for longer session (jgrzebyta/sesame-loader#24). When I try to upload (via HTTConnection) mid size RDF file (~33M, RDF/XML) I have following error in the beginning of session:
Caused by: java.lang.IllegalStateException: Transaction URL has not been set
	at org.eclipse.rdf4j.http.client.SesameSession.rollbackTransaction(SesameSession.java:547)
	at org.eclipse.rdf4j.repository.http.HTTPRepositoryConnection.rollback(HTTPRepositoryConnection.java:353)
	... 17 more

Also ref #728

@jeenbroekstra Which module is good for keeping in integration tests? I want to build test with uploading one of the uniprot's file. For example taxonomy 1G.

@jgrzebyta not sure it's wise to make that part of the integration tests - it's likely to take a long time, so I wouldn't want it to be executed every time we do a maven build. I guess we need a separate module for scalability and benchmarking tests. Perhaps have a look at including it in the new benchmark root module?

Btw that stacktrace is not really enough to tell what's going wrong. The error indicates that you tried to do a rollback while the SesameSession object does not have an active transaction registered on the client-side. AFAIK the only way that can happen, really, is if you're trying to do a rollback on a HTTPRepositoryConnection that doesn't have a transaction started.


abstract factory no longer working.

@AaronStGeorge so I'm not certain what you did you change the noninvasive blood pressure thing but it is not working now. Also the label didn't change.
Can you fix it?

@skazn yeah I changed that name, but didn't change it in the other places it needed to be changed. I've fixed it in my code. Working on #13 right now, when I push that stuff this should be fixed.

@AaronStGeorge Thanks Man!


Local Hyperlinks, Documentation demo

I am trying to create a hyperlink to another slide in the same presentation.
From the documentation on hyperlinks, I understand I need to create a run like this:
    from pptx import Presentation

    filepath = 'test.pptx'
    pres = Presentation(filepath)
    slide = pres.slides[0]
    paragraph = slide.shapes[0].text_frame.paragraphs[0]

    run = paragraph.add_run()
    run.text = "hello world"
    run.hyperlink.address = 'https://github.com/scanny/python-pptx'

The documentation is a bit hard for me to understand regarding how to create a hyperlink to a target within the PowerPoint file itself. The quote from the documentation is:

Hyperlinks in PowerPoint can have four types of targets: ....
another part in the same presentation. This uses an internal relationship (in the .rels item) to the target part.

Can you describe in detail how to create a target using the .rels item and how to hyperlink to that target? Thanks!

I found that you can hyperlink to a slide by formatting the "URL" like this:
run.hyperlink.address = "#Slide 3"

That did the trick.

There's a new feature in the last month or so enabling this more directly:
shape.click_action.target_slide = prs.slides[3]

http://python-pptx.readthedocs.io/en/latest/api/shapes.html#pptx.shapes.base.BaseShape.click_action

How is this done with run using this new method?

The .click_action property is currently only on a shape, not yet a Run object. So it's still the old method there if you're constrained to making a link from text (like a traditional hyperlink).

hey scanny
i want to create a text including hyperlink word in it like source:ancbhfd "jkl"asdf as u see jkl is my hyperlink text so how can i make it?

I found that you can hyperlink to a slide by formatting the "URL" like this:
run.hyperlink.address = "#Slide 3"

That did the trick.

Is "#Slide 3" in this example the name property of a slide, or the slide ID? And is the # symbol part of that name/ID, or the indicator that this is an internal link?

I have the same question. @scanny or @doakey3 ?

I played around with the link in powerpoint itself, it generates a link of this nature:
https://docs.google.com/presentation/d/1FWKElbximUY3QB5a-APbRl6Uo/edit#slide=id.p2

and if we will use #slide=id.p2 it works!
For myself, I have found the following to be a temporary solution:
run.hyperlink.address = f'#slide=id.p{slide_id}'


Allow to exclude xattrs (or specific xattr namespaces) when restoring

Output of restic version
restic 0.17.1
compiled with go1.22.5  on linux/amd64

What should restic do differently? Which functionality do you think we should add?

First off, restic is an amazing tool! Thanks for all your great work.  We've been using restic in VolSync (https://github.com/backube/volsync)  to perform backups in kubernetes environments.
This one is a bit complicated - Essentially we're running restic in a kubernetes pod and hit an issue with v0.17.1.  I think this was always here, but the error would be ignored, but this fix means restoring xattrs as UID 0 will now fail the restore:  https://github.com/restic/restic/pull/4958
The issue comes from the fact that we have some scenarios where we run as UID 0 so that we can restore UIDs and GIDs, but when extended attributes in the trusted. or system. namespace are restored, this will fail as we don't have the CAP_SYS_ADMIN capability.  Additionally it seems that even with this capability, we may not be allowed to modify the security.selinux xattr on a file (in Openshift this is definitely an issue, perhaps it will happen on other kubernetes envs too).  We don't hit this issue when not running as UID 0 as the error is ignored by restic.
Would it be possible to allow for excluding xattrs (perhaps with a pattern, or perhaps exclude specific xattr namespaces) at restore time?  If it makes sense for consistency we could also do this at backup - but my main concern atm is restore.
Please let me know if you'd be open for such a change - I'd be happy to contribute a PR.
What are you trying to do? What problem would this solve?

Did restic help you today? Did it make you happy in any way?

I guess we have four possible approach which we could follow here:

either add an option the not restore any extended attributes
add an option to ignore errors while restoring extended attributes
or adding a filter to not restore certain extended attributes. That filter could also be used to ignore all extended attributes. The first thing that comes to my mind would be to have a --omit-xattrs glob-pattern option (there are probably better names for that option) that can be specified multiple times.
Hardcode some error filters for well known problematic xattrs. Could you provide more details on the error that occurs when the xattr cannot be restored? This last option would be the easiest to use from a user perspective.

What I'm wondering is how other backup tools handle this situation.
Regarding backup versus restore time: I'm preferring to just capture everything during backup and then decide at restore time whether to ignore some part of that data. That way one won't accidentally loose some metadata.

Thanks for your response @MichaelEischer .
Here's an example of errors when restoring as UID 0:
...
ignoring error for /sys: xattr.LSet /data/sys security.selinux: permission denied
ignoring error for /test: xattr.LSet /data/test security.selinux: permission denied
ignoring error for /undo_001: xattr.LSet /data/undo_001 security.selinux: permission denied
ignoring error for /undo_002: xattr.LSet /data/undo_002 security.selinux: permission denied
Summary: Restored 1 / 7 files/dirs (0 B / 0 B) in 0:01, skipped 184 files/dirs 212.168 MiB
Fatal: There were 191 errors

In this case every single file being restored fails as I believe the files are initially written with the security.selinux settings that belong to the kubernetes namespace being restored to.  Then when the xattr is modified to the security.selinux setting from the backup, it fails with permission denied as it's not allowed to modify that xattr.  This is happening in an OpenShift environment, this may work differently in different kubernetes environments.
I can also get it to fail with any other security.* xattr I set on the source.  But in the case of those, I think I could avoid this if I give the pod CAP_SYS_ADMIN capability.  Looking at the capabilities man page, I think security and trusted xattrs will require this capability.  I'd rather not grant this to my restore pod however, I only use the UID 0 in this special case when a user wants to restore UIDs and GIDs from their backup.
Note that granting CAP_SYS_ADMIN doesn't solve the problem with the security.selinux xattr I mentioned above, but works for xattrs I just tried creating manually like security.test.
Ultimately I think I'd prefer option 2 or 3 from your above list (option to ignore xattr restore errs or exclude specific ones) as I'm not sure my case applies universally.

What I'm wondering is how other backup tools handle this situation.

I was looking at how tar handles it: Tar - Extended File Attributes

Attribute names are strings prefixed by a namespace name and a dot. Currently, four namespaces exist: ‘user’, ‘trusted’, ‘security’ and ‘system’. By default, when ‘--xattrs’ is used, all names are stored in the archive (with ‘--create’), but only ‘user’ namespace is extracted (if using ‘--extract’). The reason for this behavior is that any other, system defined attributes don’t provide us sufficient compatibility promise. Storing all attributes is safe operation for the archiving purposes.

Two more flags are provided:
--xattrs-include-pattern and --xattrs-exclude-pattern
We can take a similar approach of extracting only the user namespace as a sensible default, then allowing the user to specify other namespaces as patterns to allow restore with warnings.

Thanks for that extra information @konidev20 !  I've created a draft PR for the moment, just to see if this would be workable:  https://github.com/restic/restic/pull/5129
Would still need unit tests etc.
Right now it does this:

Adds --exclude-xattr and --include-xattr mutually exclusive cmd flags to restic restore.  (These names can be changed of course, I tried to keep it consistent with current cmd line flag naming).
Currently just re-uses code from the filter package to do the pattern matching, which ultimately uses filepath.  I thought this would be easiest, but technically I guess these are not filepaths we are matching.
This also sets the default (if not flags are passed) to only match user.* xattrs.  This can be changed if I should maintain current behaviour of trying to restore all xattrs.

@tesshuflower Thank you for your pull request!
I just had a similar problem when restoring a backup onto a podman volume with z-mode (e.g. -v cerbot-data:/data:z). The z/Z option tells podman to relabel the content of the volume with selinux.
With this option in place, selinux automatically adds security.selinux="system_u:object_r:container_file_t:s0" on restored files and restic fails to remove/change them, because it does not have the permissions from inside the container: ignoring error for /accounts/meta.json: xattr.LRemove /accounts/meta.json security.selinux: permission denied
Is this problem (failing on xattr removal) also covered by your pull request?

@elpepino89 With my PR it is attempting to allow new flags on the restore cmd to either include or exclude specific xattrs.  It would exclude setting the xattr, but then should also not remove the xattr if it already exists on the file in question.
Note that right now I'm not sure what the default will be in the end - possibly for linux we default to only restoring user namespaced xattrs (i.e. xattrs starting with user.*).  If this is the case it should fix your issue without any changes, however if the default is to include all xattrs to maintain current behaviour, then you would need to pass in one of the new flags.  Will try to update here once it's decided.


dbt: test updates to onchain metrics mart (v2)

Hi @ryscheng, @ccerv1  👋🏼
As CL shared with you, we are playing around Recce with OSO PRs.
Here is the Lineage Diff of this PR:

To get access, you only need to

Install Recce (pip install recce)
Download oso_pr1272_recce_state.json
Open Recce server in review mode with the Recce state file (recce server --review oso_pr1272_recce_state.json)

Since this state file is generated in our BigQuery environment, you won't be able to do further diffing actions. But you can see the information within the state file.
We are happy to help you to setup Recce CI for your project, so the review process for dbt related PRs can be much better.
Feel free to let me know any issues and how can we make the project better together. 🙌🏼


Append "/mount" to directory for CSI volumes

CSI volumes are mounted one level deeper than "native" kubernetes
volumes, and this needs to be appended for proper restic support.
Fixes #1313.
Currently a draft as I would like to get some tests in here, plus I need to verify it manually.
Signed-off-by: Nolan Brubaker<EMAIL_ADDRESS>

Approach looks reasonable, 👍 on tests

Tests updated, and I've sucessfully tested this with restic on a CSI volume (EBS). It backed up and restored correctly.

Merge pending conflict resolutions @nrb.

Conflicts fixed and commits squashed


I'm having a build fail

This comes when running 'sudo ./gradlew bootRun'
FAILURE: Build failed with an exception.

* Where:
Settings file '/Users/computer/tor/java1/HelloWorld-Java/settings.gradle'

* What went wrong:
Could not compile settings file '/Users/computer/tor/java1/HelloWorld-

Java/settings.gradle'.
> startup failed:
General error during semantic analysis: Unsupported class file major version 57
I can only make sense of the word 'version' so my Java version is this...
$ java -version
java version "13.0.1" 2019-10-15
Java(TM) SE Runtime Environment (build 13.0.1+9)
Java HotSpot(TM) 64-Bit Server VM (build 13.0.1+9, mixed mode, sharing)

Let me know if you would like me to post the entire stack trace.

Downgraded from Java 13 to Java 12 and it now works fine.