Upload To Google Team Drive Failed

Hello,
Team Drive is a feature of Google Drive. Seems gdrive don't work with Team Drive at present. This is what I got when I try to upload to a Team Drive folder:
gdrive upload --parent 0B_XXXXXXXXXXXXXXXXXXXX ./file
Failed to get file: googleapi: Error 404: File not found: 0B_XXXXXXXXXXXXXXXXXXXX., notFound

I ran into the exact same issue with Team Drive. Please help!

Try
gdrive upload --parent 0B_XXXXXXXXXXXXXXXXXXXX --name file ./file

@pekatete, when I try to upload using that syntax:
gdrive upload --parent 0B<> --name tmp.sh ./tmp.sh
Failed to get file: googleapi: Error 404: File not found: 0B<>., notFound
gdrive mkdir -p 0B<> tempo
Failed to create directory: googleapi: Error 404: File not found: 0B<>., notFound

@pekatete, I have been using gdrive with regular google drive directory without a problem. It's only when I try to use team-drive that I run into the errors above.
During setup, we get to authenticate and 'allow' the app to access one's google drive. There doesn't seem to be any distinction between regular drive and team drive when at this step of authenticating. Wonder how it'll identify team drive.

Came here for the same issue. Clues?

Also would love to use gdrive with Team Drives, getting the same errors as people above:
Failed to get file: googleapi: Error 404: File not found: ., notFound
where  is my team drive folder ID.

Following, Facing similar issue with one of my apps.

Same issue here ! Maybe it's not the right ID ?

@UmeshSingla what do you mean by

granting the permissions again and updating the ID

Can you confirm you were able to make it work with Team Drive already?
Cheers

@UmeshSingla what do you mean by

granting the permissions again and updating the ID

Can you confirm you were able to make it work with Team Drive already?
Cheers

+1


Feature/support inject tracer

addresses https://github.com/digma-ai/digma-collector-backend/issues/1054 sub task 2
support syntax of
@Inject
Tracer tracer;

seems like Quarkus supports this pattern as well:
https://quarkus.io/guides/opentelemetry#available-opentelemetry-cdi-injections
maybe need to add another instrumentation library


Added SotE Weapons

This is great :smile: . Thank you so much for contributing these back to the dataset, it's a huge help.

GitHub somehow messed up the PR somehow, but the changes have still merged (attributed to you of course).


Cilium with IPSec tunneling fails to start on 3033.2.2

Description
Since updating to 3033.2.2, all of my Cilium pods are in a CrashLoopBackoff state with the following error message:
level=fatal msg="IPSec with tunneling requires support for xfrm state output masks (Linux 4.19 or later)." error="invalid argument" subsys=daemon

After rolling back to 3033.2.1, cilium starts up again.
Impact
Cilium fails -> all other pods can't get network -> general mayhem :smiling_imp:
Environment and steps to reproduce

Set-up:

Flatcar Linux 3033.2.2 on x86s
Cilium set up as CNI with the cilium/cilium Helm chart at 1.11.0 and the following Helm values: https://gist.github.com/shosti/f8c93283a200af0f8dd9de0f73f794bd

Task: Automatic upgrade
Action(s): Update from 3033.2.1 to 3033.2.2, check kubectl logs for a cilium pod
Error:

level=fatal msg="IPSec with tunneling requires support for xfrm state output masks (Linux 4.19 or later)." error="invalid argument" subsys=daemon

Expected behavior
Cilium pods start up correctly.

Thanks for the report, maybe our cilium tests need some extensions to catch these cases in the future.
It looks like these xfrm changes could be related: https://lwn.net/Articles/882912/ (Linux 5.10.94)

In the mean time make sure you disable automatic updates: https://www.flatcar.org/docs/latest/setup/releases/update-strategies/#disable-automatic-updates

Looked at the kernel config under /proc and there is no unexpected difference between the two versions (as was the case with a bugfix kernel update some time ago)

here's a minimal repro: https://gist.github.com/tormath1/bf3af973de9a4232698cc42199496496 from cilium failing part.
with strace, we can see that we're hitting the following change: https://github.com/torvalds/linux/commit/8dce43919566f06e865f7e8949f5c10d8c2493f5
Investigating on the netlink side...

@tormath1 if its failing on the changelink then its a kernel bug (if_id is always 0).

@jepio based on the linked commit, if_id needs to be different from 0... On the repro, it works fine by setting an explicit if_id to 1 for example.

Missed the lower half of the gist on my phone xD

It's really something to discuss how this (LTS) bug fix kernel update ended up in this situation given the leading principle that userspace ABI should not be broken. Maybe this change could be reverted in the next kernel bug fix release?
@borkmann - do you have an opinion on this from the Cilium (and kernel) side?

Hi @shosti, Cilium's PR has been merged - if you're feeling adventurous, you can build a cilium image and try it to deploy by updating this value: https://github.com/cilium/cilium/blob/v1.11.0/install/kubernetes/cilium/values.yaml#L84
Otherwise, the fix should be part of the next cilium's release (1.11.3). :)

The proposal to revert upstream got rejected but we decided to do it for Flatcar anyway: https://github.com/flatcar-linux/coreos-overlay/pull/1682 - this is not part of a release yet.

Maybe as additional info that there is a regression: https://github.com/cilium/cilium/pull/19019

Unfortunately, this workaround breaks IPsec connectivity between nodes. Once the XFRMA_IF_ID is set to the placeholder value (1), traffic that should be encrypted leave the node without any encryption. On GKE and self-managed clusters, that's the only noticeable impact. However, on AKS and EKS, we also have BPF logic to rewrite the outer IP address to the proper IP. This still happens despite the failure to encrypt traffic, leading to packet drops.

I think we can close this now as a Cilium release was done and we have anyway reverted the change for next week's release


SparseML Dockerfile and build processes

Related to: https://app.asana.com/0/1201735099598270/1201964439431277/f
See related PR in DeepSparse:
https://github.com/neuralmagic/deepsparse/pull/325

Looks like it's almost there, just needs a couple fixes.
The dockerfile builds and runs fine, but support for pytorch cuda operations isn't included. There's two roots of the cause:

Pytorch hasn't compiled a 1.9.1 version that supports cuda 11.3. The closest combo that's available via pip installable is torch 1.9.1 + cuda 11.1
For older version of pytorch, the cuda version needs to be specified on install. e.g. pip install torch==1.9.1+cu111 torchvision==0.10.1+cu111 --extra-index-url https://download.pytorch.org/whl/cu111

Interesting @KSGulin . Now I see why your dockerfile in containers repo was quite complex.
So I did look into it and it seems like this is the right way to solve the problem:

Scenario when the dockerfile installs Cuda 11.3:
You're suggesting to actually swap Cuda 11.3 for Cuda 11.1, because this is the latest cuda version that supports torch==1.9.1. Do you have a source on that?
Once Cuda 11.1 is installed:
pip install torch==1.9.1+cu110 torchvision==0.10.0+cu110 -f https://download.pytorch.org/whl/torch_stable.html
Scenario when using Cuda 10.2:
The internet suggests that it should work out of the box simply pip install torch==1.9.1 torchvision==0.10.0

Thanks for making me aware of those issues, this is really interesting. If I still did not get this right, let's have a chat today.

@dbogunowicz this page has all the install commands for legacy versions of pytorch. For 1.9.1 installed using wheel on linux, looks like explicit cuda version callout is needed in both

@dbogunowicz this page has all the install commands for legacy versions of pytorch. For 1.9.1 installed using wheel on linux, looks like explicit cuda version callout is needed in both

This is great, thank you. Updated the PR.

Tested using command
sparseml.image_classification.train --recipe-path zoo:cv/classification/resnet_v1-50/pytorch/sparseml/imagenet/pruned85_quant-none-vnni  --arch-key resnet50  --pretrained pruned-moderate     --dataset imagenette --dataset-path dataset     --train-batch-size 4 --test-batch-size 8


[Feat]: make gssoc banner on readme responsive to dark/light mode 💡

What feature?

This improvement is about making the GSSOC Banner responsive to Dark/Light mode.
This helps us to make the documentation better to the readers, and images are also in high quality so devices with larger screens can be read the documentation without image disortion.

Show us the magic with screenshots

O R I G I N A L

LIGHT MODE
DARK MODE

LIGHT MODE
DARK MODE

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSoC'23 contributor
[X] I want to work on this issue

Hey there @Vaishnavi-Patil2211 👋🏻
Please make sure to assign this issue to me and merge the below linked PR 👇🏻
Thank you!


[BUG] Opening "Add Part Category" from "Create Part" dialogue brakes "Default Location" pop-up

Describe the bug
When you work on "Create part" dialogue, and decided to create new category directly from this window by clicking "Add Part Category" on the top right, the "Default Location" pop-up list will no longer work.
You don't need to create category, it is enough to just click on the "Add Part Category" button for bug to occur.
Steps to Reproduce

Click on green button "New Part" for dialogue on appear;
Click "Add Part Category" in a top right corner of a window;
Close the "Add Part Category" window by clicking on a cross icon;
Scroll down to "Default Location" section and try to unfold the list;

Deployment Method

[ ] Docker
[X] Bare Metal

Version Information
InvenTree-Version: 0.5.3
Django Version: 3.2.5
Commit Hash: 5ec998922
Commit Date: 2021-10-20
Database: sqlite3
Debug-Mode: True
Deployed using Docker: False

@Acvarium thanks for the report! Can reproduce, we will have to look into that

Looks like this is happening because both the "new part" and "new category" forms have a field called "default_location"
Perhaps the jquery code does not differentiate correctly between the two field instances.

Two other bugs I have found while looking here:

If you open a "secondary" modal (as above) and then close it, pressing the same button again (on the "primary" modal) does not open the secondary modal again. In fact all secondary modals are disabled until you close and re-open the primary modal

If you open a "secondary" modal, the primary modal still has focus for the "escape" key, and so pressing escape actually closes the first modal..

@Acvarium now fixed in master


Bmi page modify

Age and Gender do affect the BMI.
As children grow at different rates, there is a difference in females' and males' weight for the same height.

Hey @YatharthaRana ! Please give me a link to the site where I can see your changes. If you don't know how to create a link, refer this.

https://yathartharana.github.io/HealhUb/
Here it is

Done

Removed the buttons


Registry functions return Poll to enable parallel fetching of index data

Adds Poll as a return type for several registry functions to enable parallel fetching of crate metadata with a future http-based registry.
Work is scheduled by calling the query and related functions, then waited on with block_until_ready.
This PR is based on the draft PR started by eh2406 here #8985.
r? @Eh2406
cc @alexcrichton
cc @jonhoo

I've updated the @jonhoo 's http registry prototype based on this change and the initial results look good. Not quite ready for PR yet though: https://github.com/arlosi/cargo/commit/dd5eb9ec99fa85078a3d216598d6fe3b7ceecc3c#diff-cb43b9ba868eedb392ea22664d59b4444dd7c4c4f5e641ab045aa861a38ffa4c

Thank you for picking this up!

/// Block until all outstanding Poll::Pending requests are Poll::Ready.

I assumed we would have an API more like "Block until at least one outstanding request is Poll::Ready". But having thought about it the conditions for my API to be helpful are corner cases of corner cases. And if you're only making one request your API prevents needing a retry loop, query is guaranteed to return Ready after only one call to block_until_ready.

@alexcrichton yes, I'd like to get this completed! Any suggestions you have to move it forward would be awesome.

Ok so talking with @Eh2406 a bit yesterday one of the concerns is that while this infrastructure makes sense none of it's really being exercised yet (since everything is always "ready"). I think that we will actually want to change how remote sources (git/registry) work today to actually leverage this new functionality, however. Basically I think that the query method should never block, including the git/registry sources that we have today. Instead they would be updated to follow this methodology where query queries the internal caches and if something isn't found then it's "not ready" and records internally what needs to happen. Later on the "wait for everything" it'd actually do blocking work and network things like happens today. Does that make sense?

I'm finally coming back to this in the new year. @alexcrichton I'm hoping for some clarification on what you'd like here for the existing git model. Currently, the query method doesn't block in the git model. If work needs to be done (such as fetching the repo), then the query method will fail, and the caller would do an update() then re-try the query. See here for details:
https://github.com/rust-lang/cargo/blob/24783312150544d1bc9d1075c7f42ce7b2f35540/src/cargo/sources/registry/mod.rs#L695
All the blocking work currently happens in the Source::update method for git-based registries, and I'm not sure what we'd like to do with it. It could be changed to return Poll, then actually updating (git fetching) would be done in the block_until_ready. This would necessitate many changes in the callers -- and I'm not sure it really makes sense, since we'd just be adding loops calling block_until_ready.  Or we could re-design the callers of update as well, so that the meaning of Source::update is "ensure you have the latest data when running query". That would mean that no updating actually occurred until a query was started, and block_until_ready was called.
This change has the potential to become large, depending on how much of the design is changed and I want to make sure we get agreement on how we want it to look before doing the work.

Yes that's a good point, and also an indicator at how the current design is a bit sprawling... Currently there's basically an implicit "protocol" between the resovler and sources that the resolve will appropriately, for some definition of "appropriately" call update ahead of time before calling query if necessary. This means that for git sources the resolver determines that update needs to be called and invokes it.
Instead I think a better model would be to remove update entirely, folding the functionality into a query and block_until_ready split. This is indeed a large-ish change, and won't be trivial to make. I think, though, that this new model can be implemented today without changing the underlying implementations, just the interface to them largely.
If the same loop ends up being written in Cargo then that seems emminently solvable with a helper method or similar, I don't think we need to worry too much about the impact. The purpose of this change is to enable parallel downloads and updates for the resolver, and if everything else doesn't act in parallel that's ok we can update them later over time.

@alexcrichton I updated this PR to remove the update method as you suggested.
If the registry has no local cache (hasn't been cloned yet, for instance), then queries will return Poll::Pending, and block_until_ready will do the cloning.
I also added an "invalidate_cache" method on the registry that makes subsequent queries return Poll::Pending even if a local clone exists. Calling block_until_ready then does the update and queries return results.

I'm going to be stepping down from the Cargo team so feel free to merge this without me, I unfortunately won't be able to get around to reviewing this.

:hourglass: Testing commit 0c07056bfeffee213e21cdf1e48875f59f834282 with merge a77ed9ba87bfeaf3c2758a5b291876c65f734c39...

:sunny: Test successful - checks-actions
Approved by: Eh2406
Pushing a77ed9ba87bfeaf3c2758a5b291876c65f734c39 to master...

This PR is causing errors when integrating upstream.  Can you take a look at it?  You can test in the rust-lang/rust repo by doing:

git submodule update --init
git submodule update --remote src/tools/cargo
cargo update -p cargo
Set submodules=false in config.toml
./x.py test src/tools/cargo

I am seeing the following errors:
failures:

---- install::install_semver_metadata stdout ----
running `/home/eric/Proj/rust/build/x86_64-unknown-linux-gnu/stage1-tools/x86_64-unknown-linux-gnu/release/cargo install foo --registry alternative --v
ersion 1.0.0+abc`
running `/home/eric/Proj/rust/build/x86_64-unknown-linux-gnu/stage1-tools/x86_64-unknown-linux-gnu/release/cargo install foo --registry alternative`
thread 'install::install_semver_metadata' panicked at '
test failed running `/home/eric/Proj/rust/build/x86_64-unknown-linux-gnu/stage1-tools/x86_64-unknown-linux-gnu/release/cargo install foo --registry alt
ernative`
error: stderr did not match:
1        -    Updating `alternative` index
2   1          Ignored package `foo v1.0.0+abc (registry `alternative`)` is already installed, use --force to override
3   2     warning: be sure to add [..]

other output:

', src/tools/cargo/tests/testsuite/install.rs:1947:10
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

---- install_upgrade::already_installed_updates_yank_status_on_upgrade stdout ----
running `/home/eric/Proj/rust/build/x86_64-unknown-linux-gnu/stage1-tools/x86_64-unknown-linux-gnu/release/cargo install foo --version=1.0.0`
running `/home/eric/Proj/rust/build/x86_64-unknown-linux-gnu/stage1-tools/x86_64-unknown-linux-gnu/release/cargo install foo --version=1.0.1`
running `/home/eric/Proj/rust/build/x86_64-unknown-linux-gnu/stage1-tools/x86_64-unknown-linux-gnu/release/cargo install foo --version=1.0.1`
thread 'install_upgrade::already_installed_updates_yank_status_on_upgrade' panicked at '
test failed running `/home/eric/Proj/rust/build/x86_64-unknown-linux-gnu/stage1-tools/x86_64-unknown-linux-gnu/release/cargo install foo --version=1.0.
1`
error: process exited with code 101 (expected 0)
--- stdout

--- stderr
error: cannot install package `foo`, it has been yanked from registry `crates-io`
', src/tools/cargo/tests/testsuite/install_upgrade.rs:830:10

---- install_upgrade::already_installed_exact_does_not_update stdout ----
running `/home/eric/Proj/rust/build/x86_64-unknown-linux-gnu/stage1-tools/x86_64-unknown-linux-gnu/release/cargo install foo --version=1.0.0`
running `/home/eric/Proj/rust/build/x86_64-unknown-linux-gnu/stage1-tools/x86_64-unknown-linux-gnu/release/cargo install foo --version=1.0.0`
running `/home/eric/Proj/rust/build/x86_64-unknown-linux-gnu/stage1-tools/x86_64-unknown-linux-gnu/release/cargo install foo '--version=>=1.0.0'`
thread 'install_upgrade::already_installed_exact_does_not_update' panicked at '
test failed running `/home/eric/Proj/rust/build/x86_64-unknown-linux-gnu/stage1-tools/x86_64-unknown-linux-gnu/release/cargo install foo '--version=>=1
.0.0'`
error: stderr did not match:
1        -    Updating `[..]` index
2   1          Ignored package `foo v1.0.0` is already installed[..]
3   2     warning: be sure to add [..]

other output:

', src/tools/cargo/tests/testsuite/install_upgrade.rs:779:10

---- install_upgrade::no_track stdout ----
running `/home/eric/Proj/rust/build/x86_64-unknown-linux-gnu/stage1-tools/x86_64-unknown-linux-gnu/release/cargo install --no-track foo`
running `/home/eric/Proj/rust/build/x86_64-unknown-linux-gnu/stage1-tools/x86_64-unknown-linux-gnu/release/cargo install --no-track foo`
thread 'install_upgrade::no_track' panicked at '
test failed running `/home/eric/Proj/rust/build/x86_64-unknown-linux-gnu/stage1-tools/x86_64-unknown-linux-gnu/release/cargo install --no-track foo`
error: stderr did not match:
1        -    Updating `[..]` index
2   1     error: binary `foo` already exists in destination `[..]/.cargo/bin/foo`
3   2     Add --force to overwrite

other output:

', src/tools/cargo/tests/testsuite/install_upgrade.rs:703:10

---- install_upgrade::registry_upgrade stdout ----
running `/home/eric/Proj/rust/build/x86_64-unknown-linux-gnu/stage1-tools/x86_64-unknown-linux-gnu/release/cargo install foo`
running `/home/eric/Proj/rust/build/x86_64-unknown-linux-gnu/stage1-tools/x86_64-unknown-linux-gnu/tmp/cit/t1302/home/.cargo/bin/foo-1`
running `/home/eric/Proj/rust/build/x86_64-unknown-linux-gnu/stage1-tools/x86_64-unknown-linux-gnu/release/cargo install foo`
thread 'install_upgrade::registry_upgrade' panicked at '
test failed running `/home/eric/Proj/rust/build/x86_64-unknown-linux-gnu/stage1-tools/x86_64-unknown-linux-gnu/release/cargo install foo`
error: stderr did not match:
1        -    Updating `[..]` index
2   1          Ignored package `foo v1.0.0` is already installed[..]
3   2     warning: be sure to add [..]

other output:

', src/tools/cargo/tests/testsuite/install_upgrade.rs:155:10

---- install_upgrade::v1_already_installed_dirty stdout ----
running `/home/eric/Proj/rust/build/x86_64-unknown-linux-gnu/stage1-tools/x86_64-unknown-linux-gnu/release/cargo install foo`
running `/home/eric/Proj/rust/build/x86_64-unknown-linux-gnu/stage1-tools/x86_64-unknown-linux-gnu/release/cargo install foo`
thread 'install_upgrade::v1_already_installed_dirty' panicked at '
test failed running `/home/eric/Proj/rust/build/x86_64-unknown-linux-gnu/stage1-tools/x86_64-unknown-linux-gnu/release/cargo install foo`
error: expected to find:
   Compiling foo v1.0.1

did not find in output:
     Ignored package `foo v1.0.0` is already installed, use --force to override
warning: be sure to add `/home/eric/Proj/rust/build/x86_64-unknown-linux-gnu/stage1-tools/x86_64-unknown-linux-gnu/tmp/cit/t1308/home/.cargo/bin` to yo
ur PATH to be able to run the installed binaries
', src/tools/cargo/tests/testsuite/install_upgrade.rs:330:10

---- install_upgrade::upgrade_force stdout ----
running `/home/eric/Proj/rust/build/x86_64-unknown-linux-gnu/stage1-tools/x86_64-unknown-linux-gnu/release/cargo install foo`
running `/home/eric/Proj/rust/build/x86_64-unknown-linux-gnu/stage1-tools/x86_64-unknown-linux-gnu/release/cargo install foo --force`
thread 'install_upgrade::upgrade_force' panicked at '
test failed running `/home/eric/Proj/rust/build/x86_64-unknown-linux-gnu/stage1-tools/x86_64-unknown-linux-gnu/release/cargo install foo --force`
error: stderr did not match:
1        -    Updating `[..]` index
2   1       Installing foo v1.0.0
    2    +    Updating `dummy-registry` index
3   3        Compiling foo v1.0.0
4   4         Finished release [optimized] target(s) in [..]
5   5        Replacing [..]/.cargo/bin/foo
6   6         Replaced package `foo v1.0.0` with `foo v1.0.0` (executable `foo`)
7   7     warning: be sure to add `[..]/.cargo/bin` to your PATH [..]

other output:

', src/tools/cargo/tests/testsuite/install_upgrade.rs:223:10

---- install_upgrade::multiple_report stdout ----
running `/home/eric/Proj/rust/build/x86_64-unknown-linux-gnu/stage1-tools/x86_64-unknown-linux-gnu/release/cargo install one two three`
running `/home/eric/Proj/rust/build/x86_64-unknown-linux-gnu/stage1-tools/x86_64-unknown-linux-gnu/release/cargo install one two three`
thread 'install_upgrade::multiple_report' panicked at '
test failed running `/home/eric/Proj/rust/build/x86_64-unknown-linux-gnu/stage1-tools/x86_64-unknown-linux-gnu/release/cargo install one two three`
error: stderr did not match:
1        -    Updating `[..]` index
2   1          Ignored package `one v1.0.0` is already installed, use --force to override
3   2          Ignored package `two v1.0.0` is already installed, use --force to override
4        - Downloading crates ...
5        -  Downloaded three v1.0.1 (registry `[..]`)
6        -  Installing three v1.0.1
7        -   Compiling three v1.0.1
8        -    Finished release [optimized] target(s) in [..]
9        -   Replacing [..]/.cargo/bin/three
10       -   Replacing [..]/.cargo/bin/x
11       -   Replacing [..]/.cargo/bin/y
12       -    Replaced package `three v1.0.0` with `three v1.0.1` (executables `three`, `x`, `y`)
    3    +     Ignored package `three v1.0.0` is already installed, use --force to override
13  4          Summary Successfully installed one, two, three!
14  5     warning: be sure to add `[..]/.cargo/bin` to your PATH [..]

other output:

', src/tools/cargo/tests/testsuite/install_upgrade.rs:647:10

---- publish_lockfile::warn_package_with_yanked stdout ----
running `/home/eric/Proj/rust/build/x86_64-unknown-linux-gnu/stage1-tools/x86_64-unknown-linux-gnu/release/cargo generate-lockfile`
running `/home/eric/Proj/rust/build/x86_64-unknown-linux-gnu/stage1-tools/x86_64-unknown-linux-gnu/release/cargo package --no-verify`
thread 'publish_lockfile::warn_package_with_yanked' panicked at '
test failed running `/home/eric/Proj/rust/build/x86_64-unknown-linux-gnu/stage1-tools/x86_64-unknown-linux-gnu/release/cargo package --no-verify`
error: stderr did not match:
1   1        Packaging foo v0.0.1 ([..])
2        -    Updating `[..]` index
3        -warning: package `bar v0.1.0` in Cargo.lock is yanked in registry `crates-io`, consider updating to a version that is not yanked

other output:

', src/tools/cargo/tests/testsuite/publish_lockfile.rs:339:10

---- publish_lockfile::warn_install_with_yanked stdout ----
running `/home/eric/Proj/rust/build/x86_64-unknown-linux-gnu/stage1-tools/x86_64-unknown-linux-gnu/release/cargo install --locked foo`
running `/home/eric/Proj/rust/build/x86_64-unknown-linux-gnu/stage1-tools/x86_64-unknown-linux-gnu/release/cargo install --force foo`
thread 'publish_lockfile::warn_install_with_yanked' panicked at '
test failed running `/home/eric/Proj/rust/build/x86_64-unknown-linux-gnu/stage1-tools/x86_64-unknown-linux-gnu/release/cargo install --force foo`
error: stderr did not match:
1        -    Updating `[..]` index
2   1       Installing foo v0.1.0
    2    +    Updating `dummy-registry` index
3   3      Downloading crates ...
4   4       Downloaded bar v0.1.1 (registry `[..]`)
5   5        Compiling bar v0.1.1
6   6        Compiling foo v0.1.0
7   7         Finished release [optimized] target(s) in [..]
8   8        Replacing [..]/.cargo/bin/foo
9   9         Replaced package `foo v0.1.0` with `foo v0.1.0` (executable `foo`)
10  10    warning: be sure to add [..]

other output:

', src/tools/cargo/tests/testsuite/publish_lockfile.rs:404:10

failures:
    install::install_semver_metadata
    install_upgrade::already_installed_exact_does_not_update
    install_upgrade::already_installed_updates_yank_status_on_upgrade
    install_upgrade::multiple_report
    install_upgrade::no_track
    install_upgrade::registry_upgrade
    install_upgrade::upgrade_force
    install_upgrade::v1_already_installed_dirty
    publish_lockfile::warn_install_with_yanked
    publish_lockfile::warn_package_with_yanked

These errors are from running cargo test --release, it is not necessary to use the rust repo.

@ehuss looking into it now.

@ehuss Fix is available in #10482. I tested it locally in both debug and release.


[SPARK-50300][BUILD] Use mirror host instead of archive.apache.org

What changes were proposed in this pull request?
This PR aims to use mirror host instead of archive.apache.org.
Why are the changes needed?
Currently, Apache Spark CI is flaky due to the checksum download failure like the following. It took over 9 minutes and failed eventually.

https://github.com/apache/spark/actions/runs/11818847971/job/32927380452
https://github.com/apache/spark/actions/runs/11818847971/job/32927382179

exec: curl --retry 3 --silent --show-error -L https://www.apache.org/dyn/closer.lua/maven/maven-3/3.9.9/binaries/apache-maven-3.9.9-bin.tar.gz?action=download
exec: curl --retry 3 --silent --show-error -L https://archive.apache.org/dist/maven/maven-3/3.9.9/binaries/apache-maven-3.9.9-bin.tar.gz.sha512
curl: (28) Failed to connect to archive.apache.org port 443 after 135199 ms: Connection timed out
curl: (28) Failed to connect to archive.apache.org port 443 after 134166 ms: Connection timed out
curl: (28) Failed to connect to archive.apache.org port 443 after 135213 ms: Connection timed out
curl: (28) Failed to connect to archive.apache.org port 443 after 135260 ms: Connection timed out
Verifying checksum from /home/runner/work/spark/spark/build/apache-maven-3.9.9-bin.tar.gz.sha512
shasum: /home/runner/work/spark/spark/build/apache-maven-3.9.9-bin.tar.gz.sha512: no properly formatted SHA checksum lines found
Bad checksum from https://archive.apache.org/dist/maven/maven-3/3.9.9/binaries/apache-maven-3.9.9-bin.tar.gz.sha512
Error: Process completed with exit code 2.

BEFORE
$ build/mvn clean
exec: curl --retry 3 --silent --show-error -L https://www.apache.org/dyn/closer.lua/maven/maven-3/3.9.9/binaries/apache-maven-3.9.9-bin.tar.gz?action=download
exec: curl --retry 3 --silent --show-error -L https://archive.apache.org/dist/maven/maven-3/3.9.9/binaries/apache-maven-3.9.9-bin.tar.gz.sha512

AFTER
$ build/mvn clean
exec: curl --retry 3 --silent --show-error -L https://www.apache.org/dyn/closer.lua/maven/maven-3/3.9.9/binaries/apache-maven-3.9.9-bin.tar.gz?action=download
exec: curl --retry 3 --silent --show-error -L https://www.apache.org/dyn/closer.lua/maven/maven-3/3.9.9/binaries/apache-maven-3.9.9-bin.tar.gz.sha512?action=download

Does this PR introduce any user-facing change?
No, this is a dev-only change.
How was this patch tested?
Pass the CIs.
Was this patch authored or co-authored using generative AI tooling?
No.

Could you review this PR, @huaxingao ?

Thank you, @huaxingao . Merged to master/3.5.


Content in html

Is it possible to access data in +++HTML ...+++
like
+++HTML{htmlContent}+++

I don't understand what you mean. Can you give a more extensive example of what you are trying to achieve?

Look at this example:
+++HTML `
<meta charset="UTF-8">

${$film.title}

${$film.releaseDate.slice(0, 4)}

    This paragraph should be red and strong

`+++

form the readme... I guess that is what you need...

thanks @mathe42 !
The only constraint is that anything you insert using +++HTML xx+++ needs to be a string containing valid HTML. You can build that string entirely in your application code or embed most of it in the template like in @mathe42 's example.
Let me know if this answers your question.

Thanks a lot.
My problem was that I changed the delimiter to cmdDelimiter: ['{', '}'], and then {HTML ${htmlTable1}} not working.
Using +++ it's fine.
As I want to switch from docxtemplater ;-): Is there a way to use { } as delimiters. Think not as ${} is Javascript...
Additionally with +++ it's more difficult to style the template, because it's using more space.

Hey, @pit999, regarding the delimiter, I find it also quite annoying to use so much space using +++. I tried with ['{', '}'], but I had issue with this when wanted to insert ${}, thus, I decided to use ['*', '*']. You can basically add any symbol you want, just you have to ensure that this symbol is not going to be used in the word template from you, because the docx-templates library will count it as a delimiter and will throw error.

Thanks @Vitomir2 ! Agreed that that is the best approach.

I use now <| :-)
Thanks everyone for your quick support :-)

this is my sample html, but i am getting invalid syntax. what am i doing wrong?

@abhinovpankaj Can you try compiling the HTML into a string in javascript and then referencing that string as a variable in the doc instead?
i.e. like:
+++HTML{htmlContent}+++

It seems you are working in a Word table, which can have unexpected impact on your HTML code's text formatting.

Tried it like this, document created successfully but unfortunately, I cannot see the data and also getting error when opening the document.

Any pointers?

@abhinovpankaj best to make a new issue with a fully reproducible example (i.e. code + template).

Fortunately, I was trying multiple things on a POC and it worked when I fetch  the html data in  tags.
So, for now would not be needed. I will integrate that in my main project to see if that works.

It didnt work in my main project. :(


peft_config type annotations are inconsistent

In the docstring for SFTTrainer the type for the peft_config parameters is listed as Optional[PeftConfig] but in the init function it is type annotated as Optional[Dict]. The docstring is correct and the type annotations is incorrect.

Thanks for reporting - would you be happy to open a PR for that?

Sorry, I hadn't seen this reply. I'm happy to open a PR.


Add REST API call features

What is in this PR?
This PR will add a WeatherDataService to our app that fetches weather information from metaweather.com for a given location, and a WeatherReportModel to contain the weather information.
Roadmap

[x] Request JSON data
[x] Create Singleton
[x] Create callback method
[x] Extract data from JSON object
[x] Refactor to remove prototyping code

Usage
The WeatherDataService class has 2 methods, getCityID and getCityForecastByID. These do exactly what they say on the tin - getCityID returns a city ID number, and getCityForecastByID returns a weather forecast for the next 6 days. Metaweather's API for the forecast doesn't work with location names, which is why we must first use the getCityID method.
Example

A user types Brisbane into the search field and presses the search button
getCityID is called, which sends https://www.metaweather.com/api/location/search/?query=brisbane to Metaweather.

[
  {
    "title": "Brisbane",
    "location_type": "City",
    "woeid": 1100661,
    "latt_long": "-27.468880,153.022827"
  }
]

is returned, and the woeid value of 1100661 is stored.
4. getCityForecastByID is then called, using the query https://www.metaweather.com/api/location/1100661
5. A JSON object is returned containing weather for the next 6 days, and 6 new WeatherDataModel objects are created using the properties from the JSON object.

I'm not going to pretend I know what this means, but it looks good.

All good @CalebWebsterJCU, you don't need to know what it all means. Pull this to your machine and switch to this branch and run the project to see it in action. I've added a Usage section up top to explain what is going on.


Windows Git Installation

Create a way to install git on windows using the command prompt
(might need to install the .exe file from git itself and do an open command for that exe file)

This might help: https://www.youtube.com/watch?v=wSGuir8BUeU

This might help: https://www.youtube.com/watch?v=wSGuir8BUeU

This is a youtube video to how to install git in windows 10 command line


feat: Upload package to pub.dev

Description
Are you going to upload this package to pub.dev?

Could be an option in the Future. I never think about it, because I developed this project for my work. For now, I dont think so.

Yeah, I was just thinking, cuz there aren't good alternatives on pub.dev
If you can upload it, I'll be part of the maintainers

I think about it. I never upload any package, so I am going to need some time to do it.

No problem. Let me know what you decide

If not, I can upload it with your permission

The package is uploaded.
https://pub.dev/packages/google_places_dialog.

Great. Thank you @manuelperez96
So I'll use the pub.dev link instead of the github one


[release-2.10] Upgrade Thanos to 0.32.5

Changes:

Recreated this PR based on Saswata's PR 90
updated .busybox_versions
Targeting release-2.10

[ ] I added CHANGELOG entry for this change.
[ ] Change is not relevant to the end user.

Changes

Verification

/test test-unit

/lgtm


Add direction to HardwareCounter

Added full unit tests for GpioCounter
Updated counter.md design document

Resolves #679
Resolves #1015

Coverage increased (+0.4%) to 80.219% when pulling e2a57fcbd1b494f4e81e95cdbd8565de94960e8e on gpio-counter-direction into da0803470706dde640105cf33f2b94675f6718e4 on master.


Usage with typedjson + data (de)serialization

Hi! I'm trying to set this up on our application that uses remix-typedjson. Since the data transfer is not serialized, the controller postMessage calls are all failing (on the matches key, specifically). Wondering what best practices are here or if there are any other creative ways to resolve this without rolling my own. Here's a screenshot of the console errors for reference (note: there are a few additional errors included here that I don't believe are related, but including for additional context):

TIA!

@brianbolnick Thank you for bringing this to our attention, do you mean you are using remix-typedjson in your loader calls and hence, it breaks when attempting to send data to the service worker (via postMessage)? I haven't looked at remix-typedjson APIs in depth but we had a sanitization function within the useSWEffect hook to avoid sending unserialized data. Oerhaps you could help me a bit here, is the data sent as a promise?

Yes, it's ultimately a wrapper around superjson that prevents auto-deserializes inbound and outbound payloads for loaders and actions. It's a common practice to ensure end-to-end type safety. Think of it as a middleware that parses the response body as soon as it hydrates

I think the best solution would be to roll out your own implementation of useSWEffect hook, not too hard, you can use the original one here: https://github.com/remix-pwa/monorepo/blob/main/packages/sw/src/hooks/useSWEffect.ts as a template and replace the filtering/sanitization process with a more fitting one.

But still curious about this though, do you have a repro I can please use to test this out?

You could check out the typedjson example repo, that's probably the easiest way to get something up and running that's similar to what we're doing https://github.com/kiliman/remix-typedjson-example

Finally got around to this, got it working with a pretty simple workaround. Cloned the useSWEffect hook locally and added the following:
    function deserializeRoute(route: RouteMatch) {
      return JSON.parse(JSON.stringify(route));
    }

...
        navigator.serviceWorker.controller?.postMessage({
          type: "REMIX_NAVIGATION",
          isMount: mounted,
          location,
          matches: matches
            .filter(filteredMatches)
            .map(deserializeRoute)
            .map(sanitizeHandleObject),
          manifest: window.__remixManifest,
        });

...

Currently cleaning up issues and this issue has been deemed fixed for now


Add/update dialog variant html files for demo.

Add dialog close html variant file. Update json with file order and variant files with correct class names.

Approved


Add some emoji

Partially resolves #15
Added \u1F48C "Love Letter" ( 💌 ) in a few places, given a stylised version is being used as the logo. Added with a11y in mind, using asset from twemoji.

Yay, this is awesome. I had no idea how to make emojis a11y!

:shipit: 💝


Vite 6 support

Hi there, will react-router-hono0server get vite 6.0 support, since now React Router 7.0 has vite 6.0 support?
I think it works ok, just needs overrides at present to compile.
Cheers
Jason

👋 I will take a look after the current PR that add some new features.
It would then be 3.0.0


Unable to determine application name when using electron-packager-interactive

Hi
I am getting the above error when i try to package my app.
Have been searching around for hours, haven't been able to solve my problem.
My package.json looks like this
{
"name": "Index",
"version": "1.0.0",
"description": "A minimal Electron application",
"main": "main.js",
"scripts": {
"start": "electron ."
},
"repository": "https://github.com/electron/electron-quick-start",
"keywords": [
"Electron",
"quick",
"start",
"tutorial",
"demo"
],
"author": "GitHub",
"license": "CC0-1.0",
"devDependencies": {
"electron": "^1.4.3"
}
}
This is from terminal:
? Overwrite output directory ? Yes
? Use asar source packaging ? No
? Select Electron app source directory: /Users/torbenpoulsen/github/eApp
? Select Electron app output directory: /Users/torbenpoulsen/github/releases
? Select Application name: WeedIndex
? Select App Bundle Id (optional):
? Select App Version(optional): 1.0.0
? Select Electron icon file:
? Select Electron version release: 1.4.3
? Select platforms:
? Select architecture:
! No arch specified, defaulting to x64
! No platform specified, defaulting to darwin
Electron packager settings:
{ dir: '/Users/torbenpoulsen/github',
name: '',
platform: null,
arch: null,
version: '1.4.3',
out: '/Users/torbenpoulsen/github/releases',
'app-bundle-id': '',
'app-version': '',
overwrite: true,
asar: false,
icon: '',
app_version: '1.0.0',
bundle_id: '',
appname: 'Index',
sourcedir: '/Users/torbenpoulsen/github/eApp',
ignore: '/Users/torbenpoulsen/github/releases' }
WARNING: The version parameter is deprecated, use electronVersion (or --electron-version in the CLI) instead
WARNING: The app-version parameter is deprecated when used from JS, use appVersion instead. It will be removed in the next major version.
WARNING: The app-bundle-id parameter is deprecated when used from JS, use appBundleId instead. It will be removed in the next major version.
✗ Error: Unable to determine application name. Please specify an application name
For more information, please see
https://github.com/electron-userland/electron-packager/blob/master/docs/api.md#name
Unable to determine [Unknown Property]. Please specify an [Unknown Property]
For more information, please see
https://github.com/electron-userland/electron-packager/blob/master/docs/api.md#

There's something pretty wrong here:
{ dir: '/Users/torbenpoulsen/github',
name: '',

I'm assuming your package.json file is in /Users/torbenpoulsen/github/eApp/package.json. I would file a bug in the electron-packager-interactive project. I say this because it's passing a blank string to name, and the wrong directory to dir (which should be the directory where your package.json is), even though  you specified the source directory.

Hi Malept.
Thanks for answer.
Yes my package.json is in specified folder.
Can't it be because i have installed the app wrong or something. I am very new to programming, so i always assume error is on my side? :)

I don't see an error on your side, although I'm not too familiar with how electron-packager-interactive works. As I suggested in my earlier comment, you should file an issue in that repository.


[ASK] SAR with timedecay_formula= False won't work

Description
How should I run SAR if I don't want to implement the time decay formula in SAR?
My model is constructed as:
model = SAR(
col_user="userID",
col_item="itemID",
col_rating="rating",
col_timestamp="timestamp",
similarity_type= similarity_type,
timedecay_formula = False
)
and when fitting the model, it shows:
237         if df[select_columns].duplicated().any():
--> 238             raise ValueError("There should not be duplicates in the dataframe")
239
240         # generate continuous indices if this hasn't been done
ValueError: There should not be duplicates in the dataframe
Plese advise, thanks!
Other Comments

the error indicates you have duplicate (user, item, rating) entries in your dataframe. If you don't want to distinguish duplicates by timestamp you will need to drop them first.
new_df = df.drop_duplicates(subset=['userID', 'itemID', 'rating'])
model.fit(new_df)


chore(packages): license-reporter and fixed version of express

Connects to https://github.com/bucharest-gold/entente/issues/186

Coverage remained the same at 96.154% when pulling 7caebd63c5bf5b93ce46e2f8c8914cad2a78657d on helio-frota:pr into b9be9d9b33e4348c7162604f5c0b03ad6aebf76b on bucharest-gold:master.


Add Hitachi node details, rename eftpos

Description:

Related issue(s):
Fixes #
Notes for reviewer:

Checklist

[ ] Documented (Code comments, README, etc.)
[ ] Tested (unit, integration, etc.)

Resolved in 9b83d7c


SquaredError (v2)

MeanSquaredError without reduction. The function is renamed to SquaredError. This PR is related to #2558.

I thought mean_squared_error is still useful for users as a alias of F.average(F.squared_error(x), axes=...). Or do you think the existence of such a function is confusing for users because loss functions in v2 outputs element wise values by default, while mean_squared_error single scalar or sample wise loss values?

I add tests and modified SquaredError to support a scalar input.

I think we do not have to implement MeanSquaredError. It is confusing and F.average(F.squared_error(x), axes=...) is not so complicated.

Thank you for your update. I am running GPU test now.

From a marketing point of view, MeanSquaredError is so common in (statistical) machine learning community that lacking it could be unnatural for users. But when it comes to implement it, the choice of reduce strategy (sum or mean) can be problematic again.

When we implement mean_squared_error, it seems natural to return a mean value.

I agree that MeanSquaredError is very common.

Thank you for your opinion. We discussed offline and have reached a consensus that we leave mean_squared_error but implement it with squared_error.

Regarding reduction strategy, I guess users sometimes want the function to output sum along minibatch, not mean. Considerting the situation in which we compute the mean of loss values of whole training dataset (not minibatch). If we are given mean value for each minibatch, we have to multiply it by minibatch size (be aware that the last minibatch could be less than the other minibatches).

OK, I will restore MeanSquaredError and make another PR to rewrite it with SquaredError.
I understand the situation in which sum of squared errors is required. But users can combine Sum and SquaredError to compute sum of squared errors. Do we need to implement reduce option to SquaredError?

Thank you for your suggestion. I understand by your comment that we can realize sample-wise squared error with the combination of Sum and SquaredError, instead of adding reduce option to MeanSquaredError.
As it is easier to adding option afterwards than removing it. I come to think MeanSquaredError does not need reduce option (at least for now).

I found SquaredDifference already exists.

I restored MeanSquaredError. To rewrite it with SquaredError, we need Average function. Can I cherry-pick #2377 for _v2?

I found #2607 contains #2377. Is it better to wait for #2607 to be merged?

Sorry I could not answer to you before merging #2607. As it is merged, I believe you can continue to work on the problem.

I think this PR is finished. Could you review it?

I found SquaredDifference already exists. It also computes element-wise L2 error.

Oh, sorry I missed the function... It is confusing for users there are two functions that do the same things.

I am sorry we have made you modify the implementation again and again. I would like to propose the following changes regarding (Mean)SquaredError and (Mean)AbsoluteError.
@unnonouno @beam2d Could you check if my proposal is appropriate?
Problem

There already exists F.SquaredDifference, whose functionality is same as  F.SquaredError which has been added to the master branch (#2566).

Solution

Apply the following changes to the master branch (v1)

Remove F.SquaredError (as it is confusing for users both SquaredError and SquaredDifference exist).
Leave F.MeanSquaredError and F.mean_squared_erroras it is (as it is better to leave F.MeanSquaredError to keep backward compatibility , we should implement F.mean_squared_error with F.MeanSquaredError, rather than F.SquaredDifference because we can expect better performance).
Add F.AbsoluteDifference and F.absolute_differenceunder chainer/functions/math/ to align it with F.SquaredDifference and F.squared_difference.

We do not do any special thing to _v2 branch and wait v1.24.0 (will be released on 9th May) to be merged to _v2.

@delta2323 I can understand it is confusing that both SquaredError and SquaredDifference exist. And I agree with you that it is better to remove SquaredError for v1 because SquaredDifference was already released.
However, for v2, we can choose SquaredError or SquaredDifference. I think SquaredError is better because it will be mainly used as a loss function. How do you think of it?

Thank you for your opinion. I agree that SquaredError is more popular than SquaredDifference. My  concern is about backward compatibility. Although we can break it when upgrading to v2, we do not have to do it unnecessarily. But I am also thinking v2 could be a good timing for renaing.
@unnonouno How do you think of it?

In the term of a good timing for renaming, hinge and huber_loss seem inconsistent to me. hinge_loss/huber_loss or hinge/huber are better. It is not a big problem, but it is a good time to discuss.

In the term of renaming, hinge and huber_loss seem inconsistent to me.

Thank you for suggestion. I agree with fixing this inconsistency. One suggestion is to create hinge_loss  and issue DeprecationWarning when hinge is used (or do the same thing to huber and huber_loss).

Regarding the SquaredError. We discussed internally and came up the idea that we make SquaredDifference deprecated and encourage users to use SquaredLoss instead. How do you think of it?

@delta2323 from my understanding, your idea is shown as below. Is it right?

current
newer v1
v2

MeanSquaredError
present
present
present but rewritten withAverage + SquaredError https://github.com/pfnet/chainer/pull/2562#issuecomment-295076714

SquaredError
absent
present
present

SquaredDifference
present
present
present but deprecated https://github.com/pfnet/chainer/pull/2562#issuecomment-298429326

MeanAbsoluteError
present
present
present but rewritten withAverage + AbsoluteError

AbsoluteError
absent
present
present

AbsoluteDifference
absent
present https://github.com/pfnet/chainer/pull/2562#issuecomment-297619767
present but deprecated

I think this is better.

current
newer v1
v2

MeanSquaredError
present
present
present but rewritten withAverage + SquaredError

SquaredError
absent
present
present

SquaredDifference
present
present but deprecated
present but deprecated

MeanAbsoluteError
present
present
present but rewritten withAverage + AbsoluteError

AbsoluteError
absent
present
present

AbsoluteDifference
absent
absent
absent

Thank you for organizing information. I prefer your proposal, too.

I think rewriting MeanSquaredError and making SquaredDifference deprecated should be in other PRs. This PR is finished.

SquaredError, which is implemented by #2566, will be available in v1.24.0 and v.1.24.0 will be merged to v2 after its release. As this PR is identical to #2566, we need not to merge this PR to v2. We can close this PR and wait v1.24.0 to be merged to v2. Let me know if I misunderstand something I will reopen the PR if needed. I really appreciate your corporation.


Feature/buyer protection

Description
Buyer protection widget is now added to the library with,

Figma based UI/UX specs
Integration to backend API for fetching and displaying shop specific buyer protection details
Unit tests

Also refactored Trustbadge view and widget views for improved unit test coverage. Sonar cloud reports now show 91% code coverage 🚀
Xcode unit test coverage reports however shows 92.3% code coverage. I will see why there is a difference b/w XCode code coverage and Sonar cloud code coverage.

The code itself looks good 🙂 there is only one thing: It seems like there is code coverage reported for the "Test files".
chore: Please exclude the test files from calculated coverage report.
Everything else looks good, added some suggestions in the comments. 🙂

hey @superus8r what do you mean by Test Files?
XCTest test results and code coverage are based on the actual Swift/Objective-C code which are executed unit tests. It doesn't consider artifect files like mock JSON/Text, etc.
The increase in code coverage % report is because I have refactored the SwiftUI views, Models and ViewModels in a way that more code blocks could be covered during tests runs. I also added good amount of new tests 🙂

Hey @prempratapsingh thank you for your answer.

what do you mean by Test Files?

Test Files are files under Tests group.

XCTest test results and code coverage are based on the actual Swift/Objective-C code which are executed unit tests.

Could you please tell which groups (e.g. Sources, Tests, Example, etc) have active test coverage? 🙂

Hey @prempratapsingh thank you for your answer.

what do you mean by Test Files?

Test Files are files under Tests group.

XCTest test results and code coverage are based on the actual Swift/Objective-C code which are executed unit tests.

Could you please tell which groups (e.g. Sources, Tests, Example, etc) have active test coverage? 🙂

@superus8r XCTest doesn't work on the concept of covering a group Sources, Tests, Example, etc.
Rather it uses a TestTarget named TrustylibTests where unit test classes (BuyerProtectionDetailsModelTests, BuyerProtectionViewModelTests, etc) are added as pure Swift code.
So in essence TrustylibTests has only Swift test cases (shown in screenshot below) added to it and thus the test reports, code coverage reports are based on these test cases only.

@prempratapsingh

XCTest doesn't work on the concept of covering a group Sources, Tests, Example, etc.
Rather it uses a TestTarget named TrustylibTests where unit test classes (BuyerProtectionDetailsModelTests, BuyerProtectionViewModelTests, etc) are added as pure Swift code.

Thank you for clarifying that the XCTest uses TrustylibTests as TestTarget where unit test classes are added as pure Swift code, I understand that. 🙂✅

So in essence TrustylibTests has only Swift test cases (shown in screenshot below) added to it and thus the test reports, code coverage reports are based on these test cases only.

I also understand that the TrustylibTests only has Swift test cases and you agree that coverage reports must be based on the test cases. ✅
It's great to know you also agree with that, 🙂 however, along with that, the tests are also reporting coverage on themselves. This is extra and needs to be excluded.
In a nutshell: tests should not report coverage on themselves and this should be excluded 🙂
I also added a screenshot:

@prempratapsingh
I approved this for now.
If it's okay, I can fix it myself later. 🙂

@prempratapsingh

XCTest doesn't work on the concept of covering a group Sources, Tests, Example, etc.
Rather it uses a TestTarget named TrustylibTests where unit test classes (BuyerProtectionDetailsModelTests, BuyerProtectionViewModelTests, etc) are added as pure Swift code.

Thank you for clarifying that the XCTest uses TrustylibTests as TestTarget where unit test classes are added as pure Swift code, I understand that. 🙂✅

So in essence TrustylibTests has only Swift test cases (shown in screenshot below) added to it and thus the test reports, code coverage reports are based on these test cases only.

I also understand that the TrustylibTests only has Swift test cases and you agree that coverage reports must be based on the test cases. ✅ It's great to know you also agree with that, 🙂 however, along with that, the tests are also reporting coverage on themselves. This is extra and needs to be excluded.
In a nutshell: tests should not report coverage on themselves and this should be excluded 🙂 @irockel could we please get a third opinion on this? I also added a screenshot:

@superus8r the CircleCI configuration for groups to be covered (that you showed in attached screenshot) hasn't been changed. It is the same as when the iOS trustylib code coverage was 72%
The increase in code coverage reports is primarily due to the refactoring I did last week for Views, Models, ViewModel and other related layers. Please see this code commit for reference - https://github.com/trustedshops-public/etrusted-ios-trustbadge-library/commit/3b04f6dcbd6db35ca580913cd815cd15a9d0cd96

@prempratapsingh I approved this for now. If it's okay, I can fix it myself later. 🙂

@superus8r what fix your are referring to? Could you elaborate please.

@prempratapsingh

The increase in code coverage reports is primarily due to the refactoring I did last week for Views, Models, ViewModel and other related layers. Please see this code commit for reference

I understand and respect that 🙂
This discussion is:

about: tests covering themselves
not about: increase in code coverage ❌

Please do not mix these.

@prempratapsingh

The increase in code coverage reports is primarily due to the refactoring I did last week for Views, Models, ViewModel and other related layers. Please see this code commit for reference

I understand and respect that 🙂
This discussion is:

about: tests covering themselves
not about: increase in code coverage ❌

Please do not mix these.

@superus8r I am confused about why there is point/concern about tests covering themselves now?
Please see Xcode generated code coverage report (for feature/buyer-protection branch) in the in the screenshot below. This coverage report is purely by Xcode, there is no CodeCov or CircleCI envolved, still the coverage shows 93.6% :)

Anyways, if you feel like some CircleCI end of change is required for better test coverage, please go for it.

@prempratapsingh
Thanks I will do that

In spirits of open source and contribution, two of the tests get failed with XCode 14.2 by just running tests and also by using Fastlane.
Iphone 11 simulator, Iphone 14 Pro simulator.
Test names:
testBuyerProtectionDetailsReturnsCorrectFormattedStringForProtectionAmount on both devices, regardless of the approach
testNetworkDataServiceAddsCorrectURLParameters acted randomly but failed a couple of times.

Also, to contribute to the discussion, the XCode test coverage will also be 91.8% if you turn on the coverage target.

@prempratapsingh fyi


update flatterdict to have deeply nested dicts and lists (#21)

Update allowing deeply nisted dicts and other iterables in FlatterDict (#21 solved).
Simple example:
>>> a = [[1, 2], [3, 4]]
>>> d = FlatterDict({'a': a})
>>> print(d)
{
    'a:0:0': 1,
    'a:0:1': 2,
    'a:1:0': 3,
    'a:1:1': 4
}
>>> print(d.as_dict())
{
    'a': [[1, 2],
        [3, 4]]
}

Similaraly
>>> a = [{'a': 1, 'b':2}]
>>> d = FlatterDict({'a': a})
>>> print(d)
{
    'a:0:a': 1,
    'a:0:b': 2
}
>>> print(d.as_dict())
{
    'a': [{
        'a': 1,
        'b': 2
    }]
}

(Above printing may not be doctest ready but the underlying logic should still stand).
As before I've formatted everything with YAPF and made sure to keep maximal coverage (99%).
I left this under version 3.1.1 to make that patch a little more substantial.

Going to drop 3.2.0 unless you have any other PRs pending

I have one more pending to fix the setting and updating of the nested dicts/iterables!


Request should only be free'd after writing response

The request is currently free'd after executing the route callback, but ideally that should only happen after writing the response back to the client.
That was attempted in #79, but it turned out to cause sporadical crashes and needs more looking into. Maybe the "write finished" callback is executed more than once per request?

Fixed by #103


Add recently played endpoint

Add Spotify's new endpoint recently played

Closing in favor of #4 where this endpoint is contained.


Starting a conversation using HTTP Server

Rasa Core version 0.9.3:
Python version 3.6.5:
windows:
Starting a Conversation with Http Server:
Content of domain file (if used & relevant):''
Hello,
I have created a bot using rasa and I want to run it on HTTP Server. The command which I have used to start the sever is: python -m rasa_core.server -d models/dialogue -u models/nlu/default/creditnlumodel -o out.log and the code to start the conversation is: curl -XPOST localhost:5005/conversations/default/parse -d '{"query":"okay"}'. I am getting a error as shown below:

I couldn't understand the detailed functioning of HTTP server from the docs. Can anyone help me with this? Thanks! :)

Have you followed all the instructions given in the official docs? Are you sure the Rasa server is up and running at the given address and port? Unfortunately I am unable to pin-point the issue without being able to reproduce it, so I can only offer some generic guidelines.

You could try sending to the server a different request (a GET instead of POST, for example).
See if you can use an API testing tool (like Postman) instead of CURL to send the request.

it could be that it's a windows issue with single quotes, try "{/"query/":/"okay/"}"  instead

@auzair92
I have tried with GET request and the server is responding as shown in image below, but in case of POST command the server is not able to understand the command. The log file is without any errors.

If I include python -mjson.tool at the end of the command, the result is different and it seems to understand but it is not responding to it. May I know what does this command do here?

If GET is working and POST is not, then most probably it's an issue with the request itself. @amn41's suggestion above looks appropriate here; you should try that.
I believe the -mjson.tool is simply used to pretty-print the JSON response so that you can easily validate it from the terminal. Whether or not the server responds with an appropriate response is not dependent on this.

Try this command:
curl -XPOST localhost:5005/conversations/default/parse -d "{\"query\":\"okay\"}"

@auzair92 Great! It is working..thanks a lot! How do we get to know these kind of things?

Cool. Thanks again. I am closing the issue.

Glad to know that! Hit-and-trial, for the most part, I guess. Like, we could see that GET is working but not POST, so it must be something with the request that's gone wrong. And then further narrowing it down from there. :)


[CDK-487] Initial pass at a tarfile ingest tool

Simple tar import tool to import tarballs into a fixed Avro schema with no, gzip and bzip2 compression.

Thanks for building this! It looks like a great addition.

Thanks for the comments, I'll get on to fixing them as soon as possible.

This is a great feature to add. Thanks for working on it Ian!

@ianbuss great job! Only minor stuff left, we should be able to merge this really soon.

I tried this out manually and it worked well. Just a couple of minor comments to address.

The test failure is related to me breaking master, not this commit.

Merged! Thanks Ian!

Cool! Thanks


Update pickadate library to latest version v4.0.0-0

Hi, I tried to update the bower dependency my self to pickadate#4.0.0-0 but I get an error
Error: ENOENT: no such file or directory, stat 'code/tmp/source_map_concat-input_base_path-EKwRYxkN.tmp/0/bower_components/pickadate/lib/picker.js'

I think this file has been renamed to: bower_components/pickadate/lib/ui-picker.js

You would need to update the imports in index.js


Better window and flow management

Send STS for each 1/3 windowful, to keep other end updated and improve flow
Discard packets on the send queue correctly, based on receipt fields of STSes, and regular ACKs
Keep better track of window when adding to the send queue (don't overrun the window)
Improve retransmissions by implementing a "last sent" timestamp for packets on the send queue, and only retransmit packets "older" than 1/30 sec.
Respect the probe interval to avoid sending SNS too often.
Send packets already when adding them to the send queue - don't wait for retransmission to handle them.
Set low buffers for packet socket, to make the window matter more (default buffers are 8k for macOS, over 200k for linux). (This is fairly experimental, even for this program.)

Also several smaller things.

@larsbrinkhoff and @eswenson1, I don't need code reviews but it would be nice if you tried it out to help me find any silly bugs still around?

I have been running the latest commit, 37af47a, since yesterday.  I'm testing it quite a lot with RTAPE, and it seems to hold up well.  It's still quite slow for reading/listing tapes, but I haven't got any errors.

Listing is pretty quick (well, not as quick as writing, oddly) for me, but with the occasional "hang" which I still haven't figured out. Listing a SYSTEM; dump takes less than 30 seconds, how slow is it for you?

I'm sometimes seeing this from rtape:
Nov 03 19:40:08 its.pdp10.se rtape[16311]: Open connection from 03150
Nov 03 19:40:09 its.pdp10.se rtape[16311]: Open connection from 03150

I.e. two connections in quick succession.  Although I only started one DUMP, and only typed REMOTE a single time.  Do you think with the new updates, an RFC could be retransmitted inadvertently?  Not saying that necessarily is what is happening, mind; it could be a bug on the rtape side or elsewhere.

I wanted to run some test with the cleaning-windows branch to measure the time for DUMP, LIST, and LOAD of the SYSTEM directory.  But I ran into the double connection problem every time, so I couldn't do the tests.  With the current master branch, the connection worked right away.

Now the double connection happened with the master branch too.

I saw that, but thought I had fixed it. Alas. It is probably a retransmission of an RFC which isn't detected as a duplicate. I'll try again.

Try the latest and see if you still get double "Open connection"?

I tried your latest chaosnet-bridge (cleaning-windows branch) with rtape and attempting to LIST the incremental backup I created yesterday with BACKUP and got the same error:
   124 DRAGON DRAGON SAVE       0      11/4/2023 12:23:20.5
   125 DRAGON DRAGON YESTER     0      11/4/2023 00:16:44.5
   130 EAK    AR1    27         3      4/21/1981 02:09:50
   131 EAK    AR2    THESIS     3      9/27/1978 01:34:48
   132 EAK    BABYL  67         0      10/2/1978 20:42:01Remote-Tape protocol error--Record-stream input buffer overflow--record t!
oo long ?
_

This was the same place that DUMP ICHECK failed under BACKUP after successfully writing the incremental backup tape.  I know it is a good write because itstar has no trouble extracting all the files from it.

Since Eric gets these errors consistently, and I do not, we looked for differentiating factors, and it seems the PDP-10 emulator is a strong candidate.  Eric is using KLH10 and I'm using pdp10-ka.  I'm building a new ITS on KLH10 right now for testing.
I will also test the newest cleaning-windows updates.

It's really frustrating. I'm listing full backups of BV (klh10) using two different rtape servers without errors. I was just going to ask what emulators you're using, but would have guessed the other way around. :-(

What is the operating system difference here?

I'm running on Ubuntu 16, 18, and 22, so it's a wide spectrum of versions of Linux, glibc, etc.

Testing KLH10, my initial impression is it's considerably faster than pdp10-ka when doing the remote tape operations.  No errors so far, but I'll do a few more runs.  Also check performance of DUMP/LIST/LOAD on both klh10 and pdp10-ka.

@eswenson1  What are you running?

KLH10: Making a full dump is quite fast.  Listing it failed two out of two times.
pdp10-ka: Listing the full dump is at least 10x slower, still not finished...

Mysterious. What is the path between KLH10 and rtape? Same host, UDP, Ether, IP...? If more than one cbridge, are all on cleaning-windows? What host(s) - virtual, physical, ...?
I have no problems listing tapes with KLH10 on a Raspberry 4, and rtape on the same host (KLH10 via UDP) or on another connected through Ethernet.

In this case, everything is the same, except the PDP-10 emulator and their Chaosnet addresses.  Same VPS host, same cbridge (latest cleaning-windows, running on the same host), both using CHUDP.
I see the pdp10-ka Chasonet device uses polling I/O which may be too slow to pick up packets fast enough.  There's one millisecond between polls.

One millisecond is quite a long time, yes. There are 33 milliseconds between retransmissions, for example.
How fast is the VPS host? I found a synch problem in the KLH10 CH11 implementation when Eric started using a VPS host, I think, which went unnoticed on my old hardware (Sun, Pentium II, Raspberry 1). This also smells like a synch/concurrency problem, given the data corruption.

It works fine for me on my Ubuntu laptop running 22.04 and with pdp10-ka. It fails consistently on my Ubuntu Linode 20.04 with KLH10.

I added some locking on the input side. I'm not sure it helps, but why don't you try it? Since I don't have any problems it's hard for me to debug.

It works fine for me on my Ubuntu laptop running 22.04 and with pdp10-ka. It fails consistently on my Ubuntu Linode 20.04 with KLH10.

What happens if you use KLH10 on your laptop?

It works fine for me on my Ubuntu laptop running 22.04 and with pdp10-ka. It fails consistently on my Ubuntu Linode 20.04 with KLH10.

What happens if you use KLH10 on your laptop?

I’ll set up a KLH10 system on my laptop and try it.

LIST on pdp10-ka still not finished!  But I'm letting it run to see if it hits the "protocol error".
I have some ideas to make it faster.

LIST on pdp10-ka still not finished! But I'm letting it run to see if it hits the "protocol error".
I have some ideas to make it faster.

I’ve listed very large backup tapes under pdp10-ka (remote of course) and while it takes days to finish, it never gets errors. I’ve tried with the ES full dump that I created and moved to the rtape tape directory on my pdp10-ka setup and despite failing every time under klh10, listing it worked fine under pdp10-ka.
Note: I haven’t tried running KLH10 yet locally.

My hunch would be that the long poll interval on pdp10-ka not only makes it slow, but also might avoid concurrency problems. It will be interesting to hear about klh10 on your laptop though!

I lowered the poll interval to 0.3 ms and now pdp10-ka is super fast.  But it also drives up host CPU usage, so I'd like to find some way to keep a longer interval when Chaosnet isn't active.

It works fine for me on my Ubuntu laptop running 22.04 and with pdp10-ka. It fails consistently on my Ubuntu Linode 20.04 with KLH10.

What happens if you use KLH10 on your laptop?

Hmm... I just copied my EX setup from my Linode to my Ubuntu laptop and updated it for a different chaosnet address, and changed dskdmp.ini to bind to the local cbridge, and then mounted my ES incremental dump (copied from ES). A LIST seems snappy and finished the list without errors.
So, granted, I'm not really testing apples and apples (the issue I had was on ES, not EX), but I did use KLH10 on my laptop and don't see the crash on the same ES incremental dump tape that ES was not capable of listing without errors.

I made a full dump with the faster pdp10-ka, and then three listings.  Each took minutes rather than hours, and completed without error.

I lowered the poll interval to 0.3 ms and now pdp10-ka is super fast. But it also drives up host CPU usage, so I'd like to find some way to keep a longer interval when Chaosnet isn't active.

Sounds good. Why can't you use select() or poll() with a timeout? I don't know the simh structure.

And KLH10 works on Eric's laptop an my Raspberry, but not on Eric's VPS or Lars' spiffy Core i7?
And does this mean the problem might be in the emulator(s) after all, not cbridge?

My VPS is running Ubuntu 20.04 and my laptop is running 22.04. I wonder if that is significant?
what is Lars running on his spiffy Core i7?

I copied my ES setup from my Linode to my Ubuntu laptop (ES/KLH10 was the failing case).  I can LIST the incremental ES and a full dump of ES tape with no problems on my Ubuntu laptop.
The laptop is running Ubuntu 22.04 LTS and my Linode (where EX and ES normally run under KLH10) is running Ubuntu 20.04 LTS.
So this makes me think that the issue might be the version of Ubuntu?  :-(

It occurred to me that the issue I was having with with EX ITS (KLH10, Linode, Ubuntu 20.04).  I just tried ES ITS (KLH10, Linode, Ubuntu 20.04), and a LIST of a previously made full dump of ES.  It got into 403 files, and then died with:
   400 .MAIL. COMSAT BIN        1      11/15/2021 21:32:02.5
   401 .MAIL. COMSAT LAUNCH     0      11/8/2022 14:18:08
   402 .MAIL. COMSAT OBIN       1      8/1/2019 18:35:00.5
   403 .MAIL. COMSAT OLAUNC     0      11/15/2021 21:36:40.5
   404 .MAIL. COMSAT XPER       0      7/20/2015 22:08:35.5Remote-Tape protocol error--record type other than data, read-file-mark!
, or status ?
_

So both EX and ES have problems reading tapes with rtape.
Also, it seems to me that a recent change to rtape may have broken long filenames.  I had to rename my es-its-full-dump-20231123.tape to "esfull" in order to get rtape to attach the tape.  And I think I needed to rename it to ESFULL, all caps.  Not sure.

"Spiffy" (do I have to rename it now?) is running Ubuntu 16.  (I should upgrade some time.)  I also have other computers with 18 and 22.  The latter will be interesting to test.
As for where the problem is, I suspect cbridge is in the clear (... for now).  Maybe it's either KLH10, or the host side: Linux, libc, etc.  Another item on my debug list is to switch on all logging on KLH10 and see if there's any error message.

LSN options include winsize=%d, which could be useful when playing^Wtesting this.

I guess this is a good place to continue on related issues, but I wanted to merge and move on for now.

Does that mean we should switch back to master?

Does that mean we should switch back to master?

Yes (until further notice...)

How is your CPU usage for cbridge after these changes, by the way?

Same here.

Testing KLH10 on Ubuntu 22.  It seems to work fine.  Listing a full dump worked 2 out of 2 times.  And it's quite fast - dare I say spiffy - and file spacing works as intended.
This is not to say there's something wrong with older Ubuntu versions/kernels/libraries.  It's possible KLH10 is doing something bad that just happens not to show up on a newer Ubuntu release.

How is your CPU usage for cbridge after these changes, by the way?

My CPU usage is low too, while doing a remote tape read or write.

I just successfully did a LIST of an incremental dump tape on ES (KLH10, Ubuntu 20.04 LTS, Linode).  However, this was my third try -- the previous to simply hung on a PKTIOT system call.  This is different from the previous issues, where I actually got an error (as described above).  So perhaps things are improving a bit and changing.
But, the fact that a LIST would hang on packet i/o (for a very, very long time -- hours), is still an issue.

I spoke too soon.  I tried it another time (exact same LIST of incremental dump tape as above), and this time, it bombed very early:
_remote
TAPE SERVER HOST=5401
DRIVE=I31108
READ-ONLY? y
REMOTE TAPE REWOUND
_list
 LIST DEV =
TAPE NO     50 CREATION DATE  231108
REEL NO      0 OF INCREMENTAL DUMP

     7 .BATCH BATCHN LOG        3      11/8/2023 10:19:27.5
     8 .BATCH BATCHN QUEUE      1      11/8/2023 07:58:23.5
     9 .BATCH SPECS  859        0      11/8/2023 07:58:22
    13 .INFO. _SAV4  1          3      10/11/2023 17:26:16
    15 .MAIL.     ID 14643      0      5/19/1993 18:45:58
    16 .MAIL. STATS  1          1      11/8/2023 10:08:39.5
    17 .MAIL. _PWORD OUTPUT     0      11/5/2023 16:50:47.5
    21 .TAPE0 TAPE   46         2      10/6/2023 12:31:54.5Remote-Tape protocol error--Record-stream input buffer overflow--record!
 too long ?
_

So I guess this issue is not yet resolved.

On a third run of the full dump listing, I also got "Remote-Tape protocol error--Record-stream input buffer overflow--record too long ?"  This was on KLH10, Ubuntu 22, current cbridge master (42ee3cd).
I also tested logging in with supdup during the listing, and the session feels much fast and more responsive than before.


Hitting configmap size limit with many dashboards in one grafana deployment

After creating a number of dashboards (20-30 dashboards) we are experiencing error in the operator logs:
"caller":"controller/controller.go:209","msg":"Reconciler error","Controller":"grafanadashboard-controller","Request":"mon/overview","error":"ConfigMap \"grafana-dashboards\" is invalid: []: Too long: must have at most 1048576 bytes","stacktrace":"... omitted for brevity..."
I can see that all the dashboards are in one configmap are we hitting some limits in kubernetes/etcd?
Are there any way around this?

@tjololo What version of the operator are you using? I'm assuming it is version <= 2.0.0. From 3.0.0 onwards we no longer use config maps because of the size limitation. Instead we submit them directly using the Grafana API.
The latest release (https://github.com/integr8ly/grafana-operator/releases/tag/v3.3.0) is not yet in the OpenShift OLM Catalog. Do you have a way of installing it via a deployment?

Your assumtions are correct we are running 2.0.0.
Do you know when the latest release will be available in the OpenShift OLM Catalog (days/weeks/months)?
We can deploy it via deployment, but would prefer installation via the Catalog

@tjololo I'll leave @pb82  to answer this in  #210

Installed 3.4.0 manually. Closing this issue


"typescript" replaced by "jscript" in description

I wanted to modify the description of https://www.codewars.com/kata/5547cc7dcad755e480000004 when I added the typescript translation but when I write with the usual 3 backticks
typescript
removeNb(26) should return [[15, 21], [21, 15]]
removeNb(100) should return []
I get after re-publishing:
jscript
removeNb(26) should return [[15, 21], [21, 15]]
removeNb(100) should return []
"typescript" is replaced by "jscript" and so examples don't appear in the description of the kata for those who want to take the kata in Typescript.
Same thing in https://www.codewars.com/kata/pi-approximation/typescript and others... e.g https://www.codewars.com/kata/rectangle-into-squares/typescript.

Fixed. See #426


Kudos and a question

First of all thanks so much for this library. It kinda helped me convince my teammates that graphql is the way forward.
And the question. Let's say I have a query like so:
  profiles {
    id
    users {
      name
    }
  }

Here I want 'id' to be "sent" to profiles as a projection but I don't really care about 'users' since that's a separate collection and preferably sent along to another place which could do the same projection but only  for users. Is there a way to "skip" keys or something. I know I can just delete the keys I don't want but....
Ideally I would like it to be something like:
['id'] --- profiles projections
['name']  --- users projections
Come to think of it now that I've worked around the issue is that maybe it could support a white list instead. "only map these"...optional of course.
And maybe a way to configure always excluded keys...like "__typename" as an example.

Thanks, @jole78
Got your point. Sounds like a reasonable improvement for me. I guess we can suggest something like skip option which would filter output fields... Will take a look on that as far as there will be a free time. Anyway, feel free to suggest your PRs if you have any.

@jole78
Please, take a look at version 2.1.1, now it should support skip option...

Wow you're fast. Was just looking through the code to get an idea of how to implement something like it as a PR. Code looks in great shape btw.
I'll  have a look on Monday when I'm back at work ok. Closing issue for now at least.


Fixed #41: will not crash anymore if a database rows do not match any registered preference class

I used a different solution  than what we discussed in #41: instead of hiding thos obsolete preferences, which would have mean we could not manage them via the admin anymore, we just create a fallback preference object for them. This way, the admin do not crash anymore, and you can still see the obsolete rows.
@czlee and @pip182, It would be great if you could review my PR, test this in your respective projects and check if it solves your issue.

Codecov Report

Merging #68 into develop will increase coverage by 0.36%.
The diff coverage is 100%.

@@             Coverage Diff             @@
##           develop      #68      +/-   ##
===========================================
+ Coverage    87.91%   88.28%   +0.36%
===========================================
  Files           22       22
  Lines          778      794      +16
===========================================
+ Hits           684      701      +17
+ Misses          94       93       -1

Impacted Files
Coverage Δ

dynamic_preferences/registries.py
92.7% <100%> (+2.7%)
:white_check_mark:

dynamic_preferences/models.py
94.66% <100%> (ø)
:white_check_mark:

Continue to review full report at Codecov.

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

I hadn't actually realized that the admin site used to crash! I guess I must've never looked, normally I've been inspecting the database directly. But I tried it out (including the admin site) and it works great. 😃 Thanks for your work on this!

I hadn't actually realized that the admin site used to crash!

In fact, any place where you where grabbing a preference row from the DB and trying to access its corresponding preference class used to crash. Django's admin was a good place for that because we have a queryset and simply loop over it.
I'll merge that and make a release soon, probably today, thanks for reviewing :)


make all datepicker days selectable

Is your feature request related to a problem? Please describe.
currently it is not possible to select a day that is not in the current month.

Describe the solution you'd like
I would like to select one of the displayed days. Whether it's this month or not, doesn't matter.
Optionally describe alternatives you've considered
optionally render not selectable days accordingly.

waiting for https://github.com/duetds/date-picker/issues/15


Redis attributes not aligned with latest semantic conventions

What version of OpenTelemetry are you using?
"@opentelemetry/api": "^1.9.0"
"@opentelemetry/auto-instrumentations-node": "^0.50.0"
"@opentelemetry/exporter-trace-otlp-http": "^0.53.0"
"@opentelemetry/sdk-node": "^0.53.0"
What version of Node are you using?
Node.js 22.9.0, NPM 10.8.3
What did you do?
https://github.com/luke6Lh43/otel-redis-testing/blob/main/Readme.md#nodejs
Additional context
Hello,
I have recently been working on a project that required Redis instrumentation for two different languages. During this process, I noticed some discrepancies in the attributes being collected. To investigate further, I conducted testing to check the attributes collected for Redis instrumentation across six of the most popular languages. I have documented my testing in this GitHub repository:
[Link to GitHub Repo]
Findings for Node.js:
What We Capture Today ==> How It Should Look in Latest Semantic Conventions
db.system: redis ==> db.system: redis
net.peer.name: localhost ==> network.peer.name: localhost
net.peer.port: 6379 ==> network.peer.port: 6379
db.connection_string: redis://localhost:6379 ==> (Not needed)
(Not captured) ==> db.query.text: GET myKey
(Not captured) ==> db.namespace: 0

Changing to a feature request because this isn't wrong it's just old.
According to https://github.com/open-telemetry/semantic-conventions/blob/main/docs/database/database-spans.md we shouldn't update database instrumentations until they're stabilized in semconv, so this is on hold.


Unable to edit invited expense

https://opencollective.com/tauiwi-tautoko/expenses/157881
I invited an expense but then the payee told me I needed to add GST. So I went to the draft expense and clicked edit. However the 'pay to' was reset to myself instead of the real payee, and then it didn't let me search or select the correct payee so now I am stuck.
Unedited draft:

Defaulting to me as payee:

Unable to select correct payee:

Sound like a duplicate of https://github.com/opencollective/opencollective/issues/6586, cc @kewitz

Yes it's mostly a dup, except the point that it's not just nice to have, but totally blocking, because you cannot re-select the correct payee and you are completely stuck.


Import tensorflow -> Illegal instruction

System information
Version

OS Platform
Ubuntu 18.04 LTS

Device
Orange Pi 4

Python version
3.6

Installed using
pip

Hi everyone!
Find only one work solution for me:
pip3 install https://storage.googleapis.com/tensorflow/mac/cpu/tensorflow-1.8.0-py3-none-any.whl
<...>
Installing collected packages: tensorflow
Successfully installed tensorflow-1.8.0

And:
orangepi@orangepi4:~$ python3.6.9
>>> import tensorflow
Illegal instruction (core dumped)

I am installing version 1.5.0 and the problem persists

@RarDay
Please, see tested build configuration from here.
TensorFlow 1.x is not actively supported. Could you please update TensorFlow to the latest stable version v2.4 and check if you are facing the same issue. Thanks!

@ravikyram Sorry, I don't understand a little how to download "tensorflow-2.4.0" build and run it
I must use doker? CPU or GPU?

@RarDay
Please refer this link and see if it helps you. Thanks!

@ravikyram  Can I install tensorflow without docker in python 3.6? I'm using an orange pi and I don't have that much memory and time to constantly install docker

@RarDay
You can install Tensorflow from source and using pip.Please, refer this document..
Building TF on orangepi refer this document and link. Thanks!

@RarDay,
Any updates regarding this issue?
Please feel free to close the issue if resolved. Thanks!


Update default-storage-class-prereqs.md

fixes #29641

I agree with @RinkiyaKeDad in his comment that the original is better.
I believe the proposed change is trying to use "provisioning" as a gerund (a verb typically ending in -ing used as a noun) but the original is less confusing and grammatically correct
Feel free to re-open if you think otherwise
/close

Hey @reylejano the PR was mainly about adding link to provisioner so are we looking to add the link by keeping the word as it is in the original form

/reopen

@AvineshTripathi , I re-opened the PR, I agree with @RinkiyaKeDad 's suggestion

Thanks @AvineshTripathi
/lgtm
/hold until deployment passes
I believe @kubernetes/sig-docs-leads can retrigger the build

/unhold
preview is done
/approve


vmq_mqtt_fsm:check_user:545 can't authenticate client due to error

Environment

VerneMQ Version: 1.0.1

OS: Ubuntu

Erlang/OTP version (if building from source):

I have registered a webhook='auth_on_register' for client validation. If client successfully validated returning following
{'result': 'ok', 'modifiers': {
'mountpoint': '',
'client_id': client_id,
'reg_view': '',
'clean_session': False,
'max_message_size': 65535,
'max_message_rate': 10000,
'max_inflight_messages': 100,
'retry_interval': 100,
'upgrade_qos': False
}}
And logs throwing following error..
2017-06-11 08:40:18.004 [warning] <0.2157.0>@vmq_mqtt_fsm:check_user:545 can't authenticate client {[],<<"karthitest11_MTS_Test">>} due to error

Please help me if I am missing something in the configuration.
Thanks.
Shailendra

Maybe you've run into some kind of bug - but it also looks like you've cut-n-pasted an example response which likely contains a lot of stuff you don't need to change. For instance, changing the mountpoint and client_id is not something you usually need - so to debug this I'd first try to remove all the modifiers you don't explicitly need.
Further, to try to debug these things in general it's helpful with 1) doing a dump of the HTTP request sent from VerneMQ to the webhooks to see what is actually being sent and received 2) doing a trace of the client-id connecting, using the trace above it would look like vmq-admin trace client client-id=karthitest11_MTS_Test.
I hope this helps.


Support Poetry >=1.1.0

Poetry's update recently changed both the lock file format and the build backend.
The lock file must be updated to support Poetry >= 1.1.0 and the build backend must be changed to "poetry.core.masonry.api".

#8 attempts to implement this change.


Invalid make include path resulting in distclean errors

Prerequisites

[x] Have you checked for an existing issue describing your problem?
[x] Are you running the latest version?
[x] Is your ports tree recent?
[x] Is your FreeBSD Host on a supported release?

Describe the bug
fa03081 introduced a bug that results in setup_ports_env "/" "${__MAKE_CONF}" in distclean.sh generating an .include directive with the leading slash of the path removed (e.g. /tmp/foo → tmp/foo).
How to reproduce
Steps to reproduce the behavior:
ROOT# poudriere distclean -n -a
[00:00:00] Loading MOVED for /usr/ports
[00:00:01] Gathering all expected distfiles for ports tree 'default'
[00:00:02] Warning: (accessibility/at-spi2-atk): make: "/tmp/poudriere.iYb7p5vh/poudriere-make.conf.Of787gCc" line 2: Could not find tmp/poudriere.iYb7p5vh/poudriere-make.conf.Of787gCc.ports_env
[00:00:02] Warning: (accessibility/at-spi2-core): make: "/tmp/poudriere.iYb7p5vh/poudriere-make.conf.Of787gCc" line 2: Could not find tmp/poudriere.iYb7p5vh/poudriere-make.conf.Of787gCc.ports_env
[00:00:02] Warning: (accessibility/accerciser): make: "/tmp/poudriere.iYb7p5vh/poudriere-make.conf.Of787gCc" line 2: Could not find tmp/poudriere.iYb7p5vh/poudriere-make.conf.Of787gCc.ports_env
[00:00:02] Warning: (accessibility/atk): make: "/tmp/poudriere.iYb7p5vh/poudriere-make.conf.Of787gCc" line 2: Could not find tmp/poudriere.iYb7p5vh/poudriere-make.conf.Of787gCc.ports_env
[00:00:02] Warning: (accessibility/at-spi2-core): make: Fatal errors encountered -- cannot continu
[00:00:02] Warning: (accessibility/accerciser): make: Fatal errors encountered -- cannot continu
[00:00:02] Warning: (accessibility/at-spi2-atk): make: Fatal errors encountered -- cannot continu
[00:00:02] Warning: (accessibility/atk): make: Fatal errors encountered -- cannot continu
...
[00:00:32] Warning: (x11-wm/xfce4-desktop): make: Fatal errors encountered -- cannot continu
[00:00:32] Warning: (x11-wm/xfce4-session): make: Fatal errors encountered -- cannot continu
[00:00:32] Warning: (x11-wm/xfce4-panel-profiles): make: Fatal errors encountered -- cannot continu
[00:00:32] Warning: (x11-wm/xfce4-wm): make: "/tmp/poudriere.MUgZcGV9/poudriere-make.conf.M28g7pZk" line 2: Could not find tmp/poudriere.MUgZcGV9/poudriere-make.conf.M28g7pZk.ports_env
[00:00:32] Warning: (x11-wm/yeahwm): make: "/tmp/poudriere.MUgZcGV9/poudriere-make.conf.M28g7pZk" line 2: Could not find tmp/poudriere.MUgZcGV9/poudriere-make.conf.M28g7pZk.ports_env
[00:00:32] Warning: (x11-wm/xfce4-wm): make: Fatal errors encountered -- cannot continu
[00:00:32] Warning: (x11-wm/yeahwm): make: Fatal errors encountered -- cannot continu
[00:00:32] Gathering list of actual distfiles
[00:00:32] Error: Something went wrong. All distfiles would have been removed.

Environment

Host OS [e.g. 12.2 amd64]: 13.0 amd64
Jail OS [e.g. 12.0 powerpc]: 13.0 amd64
Poudriere Version [e.g. 3.3.1 or git hash or port version]: 3.3.7
Ports branch and revision [e.g. 2020Q3 r550754]: main 16c89227427a

Possible fixes
One possible remedy is to change / to /./ in distclean.sh, resulting in setup_ports_env "/./" "${__MAKE_CONF}".  This will generate an include path such as /.//tmp/poudriere.W0z4U71p/poudriere-make.conf.o3X6qF9G.ports_env.  Since distclean doesn't actually do anything with jails and nothing else uses distclean, this appears to be a harmless fix.

Confirmed, I'm seeing the same thing.

Committed to ports just now https://cgit.freebsd.org/ports/commit/?id=c47ee773c4cf48d4b56c3984c04fc6c224f12219

Will the non devel version also receive this bug fix?

Will the non devel version also receive this bug fix?

I didn't notice it was in there. Brought it in now. Thanks!


Table "not supported" by SQL DW

This table is available on my SQL DW instance. Should this page be updated to indicate that it applies to SQL DW?

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

ID: bf2a9f49-f432-6702-7987-854f00ceae93
Version Independent ID: 1b80bc28-fe12-077a-4cd1-94eec13af354
Content: sys.pdw_table_mappings (Transact-SQL) - SQL Server
Content Source: docs/relational-databases/system-catalog-views/sys-pdw-table-mappings-transact-sql.md
Product: sql
Technology: data-warehouse
GitHub Login: @ronortloff
Microsoft Alias: rortloff

@potato-enthusiast -- thank you for your feedback.  I am looking into this article.

@ronortloff -- Ron, please review private PR 15765.

@potato-enthusiast -- we have updated the documentation and it should be live by tomorrow.


Set CHAINER_CI in Chainer tests in FlexCI

Related: #8348

Jenkins, test this please

Jenkins CI test (for commit 2fc4328b96dfd39a7f0d90899c591d80d56ca31a, target branch master) failed with status FAILURE.

CI unrelated


fix(fmt): yul misc

Motivation
addressing general Yul comments

gm - what are we missing here?

@gakonst hey, we are missing the swtich indentation & string literal overrides for max line length. will address it today

had to restart non-forking it cause they hanged


Preloader

How can I render a loading template while the current one is loading. I would like to have a preloader on each route (not specifically tied to mongo collections but let's say on assets load or page reload).

I think this is not specific to this project. Would you mind asking this on
meteor forums.
On 2015 සැප් 5, සෙන at ප.ව. 6.17 churcho<EMAIL_ADDRESS>wrote:

How can I render a loading template while the current one is loading. I
would like to have a preloader on each route (not specifically tied to
mongo collections but let's say on assets load or page reload).
—
Reply to this email directly or view it on GitHub
https://github.com/kadirahq/meteor-react-layout/issues/16.

I actually meant to ask this on FlowRouter since I am using it with ReactLayout. My bad!


chore: Add git hooks for pre-commit and post-commit checks

Pull Request
Description
This change introduces git hooks to improve code quality and consistency. The key additions are:

Git hooks:

A pre-commit hook that runs multiple scripts
A post-commit hook to update the git index

Pre-commit scripts for:

Running Gitleaks to detect potential secrets
Formatting the Justfile
Running Prettier

These changes will help maintain code quality, prevent secrets from being committed, and ensure consistent formatting across the project.
fixes #39

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#37
#36  👈
#35
#34
#33
#32
#31
#30
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @JackPlowman and the rest of your teammates on  Graphite

Merge activity

Oct 15, 2:40 PM EDT: A user merged this pull request with Graphite.


[Bug]: Inability to Sort Projects Based on Multiple Tech Stacks on ProjectsHut [ GSSoC23' ]

What happened?
The project sorting feature on ProjectsHut currently lacks the ability to sort projects based on multiple tech stacks simultaneously. This limitation hampers the user experience by restricting efficient filtering and identification of projects that align with specific technological requirements.

Before Preview:
On ProjectsHut, the projects page serves as a hub for users to explore a variety of projects. Each project is associated with one or more tech stacks, indicating the technologies used in its development. However, the existing sorting feature on ProjectsHut only allows users to select one tech stack at a time, limiting their ability to discover projects that meet complex technological needs effectively.

https://github.com/priyankarpal/ProjectsHut/assets/91745441/5a786120-288c-40ac-8bc5-bb719d4a3e16

After Preview:
After implementing the necessary changes, users will gain the capability to select multiple tech stacks for sorting projects on ProjectsHut. This enhancement will empower them to efficiently identify projects that combine various technologies, providing greater flexibility and precision in finding projects that align with their specific needs.

https://github.com/priyankarpal/ProjectsHut/assets/91745441/dd05042c-a5c1-4c40-bcdc-43f6c9892815
[Note: I have already worked on this, Kindly assign this issue to me so that I can fix this issue and allow me for further improvements]
To Reproduce:

Visit the ProjectsHut website.
Navigate to the projects page.
Observe the project sorting functionality, noting its limitation of selecting only one tech stack.

As a participant in the GSSoC23 program, I intend to address this issue and enhance the project sorting functionality on ProjectsHut.
Add screenshots
Add screenshots
What browsers are you seeing the problem on?
Firefox, Chrome, Safari, Microsoft Edge, Brave
Code of Conduct

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

If someone wants to see only CSS-related projects they need to select only CSS they don't need to select multiple tags.
I guess it will cause confusion for users. in future, if we want to add this feature I will ping here.


query builder fixes

Summary

How did you test this change?

[x] Text editor to light mode

[x]  Misc light mode edits

[x] String inputs for filter value now has a button that will allow user more space to input text. If the user's input has multiple lines, the elements will be separated by new lines. If the user input has one line, the inputs will be separated by commas.

Testing

[ ] Test(s) added
[x] Manual testing (please provide screenshots/recordings)
[ ] No testing (please provide an explanation)

Also, @xannem let's include the UI change you made to the OLAP panel (light/dark mode). Also, can you fix a minor issue where in query builder, when we open the result set modifier (under TDS panel), the take limit input has no visible outline in light theme?

@xannem lets bring this PR back to life. So many great changes here :)


Add collaborators to this repo

Comment below to be added as a collaborator
We will all be using this repository today. Even though it's public right now, you will not be able to make changes until you're given the correct permissions. We've automated this process via the GitHub API. Once you comment, we will add you as a collaborator.
You'll start to receive a lot of emails. (❗) You can slow these down immediately by clicking the Unwatch button at the top of the page and selecting either the Participating and @mentions or Ignore option.

Hello

👍

This is nice. 👍

@guy-man have you taken a look at abc

This is nicer.  :D

hello

👍

nice

This has been a very useful session - look forward to the follow-up session. Thank you!

Great session- Looking forward for the next session

hello

"hello world"

Hello!!!

hello

Hello

Hello 👍

hello

hello

Hello

Hello as well

Hello

Hello

Hello

Hello

Hi Gus

Hello Gus


New Sample: Action List Item

Hi Team,
I’ve submitted PR abap2UI5/abap2UI5-samples#250 with a new demo featuring the Action List Control. This example demonstrates how to use this control effectively, inspired by the UI5 Demo Kit.
You can find the new demo here:

And here’s a sneak peek:

Please let me know if you have any suggestions for improvements!
Best regards,
Francisco Milan

Thank you, PR merged 🙏