Is there any workarounds for the DLL output is not the location that the calling app is calling ?

Is there any workarounds for the DLL output is not the location that the calling app is calling ?
I want to debug my DLL by start external program, the program will load my DLL at startup.
In order not to pollute the real target directory, I copy the dll and pdb to the real target directory by post build event.
But the breakpoint not hitted. Is there any workaround for this purpose?

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

ID: c922c9cf-4c0b-18fb-d1bd-afa4303db5fd
Version Independent ID: 72b4a51f-b499-41b4-6d68-19c9deaf7e3f
Content: How to: Debug from a DLL Project - Visual Studio
Content Source: docs/debugger/how-to-debug-from-a-dll-project.md
Product: visual-studio-windows
Technology: vs-ide-debug
GitHub Login: @Mikejo5000
Microsoft Alias: mikejo

@GreatFireWall -- Thanks for your question. It looks like you're having an issue with the product itself, rather than an issue with the documentation. Here are a few options where you might consider asking your question:

https://social.msdn.microsoft.com/Forums/vstudio
https://www.stackoverflow.com
https://www.reddit.com/r/VisualStudio/

As well, you might also consider using the Report a Problem tool to report the issue.
I am closing this issue now.  You are welcome to @ mention me for any followup.
We hope to hear from you again.


chore: move binary crates into a dedicated dir

Moved binary crates into a bin/ dir at the top level. I think we can refactor the sozo crate more as we have some other crates that depends on it.
.
├── bin/
│   ├── dojo-language-server
│   ├── katana
│   ├── sozo
│   └── torii
└── crates/
    └── ..

what do you guys think about this new structure ? @lambda-0x @glihm @tarrencev @broody @Larkooo  ?

i like it

what do you guys think about this new structure ? @lambda-0x @glihm @tarrencev @broody @Larkooo ?

I think that's great, especially for torii, if we get to separate the backends like grpc, libp2p, graphql.. from the CLI binary itself. Would make it easier to work it. Same thing goes for the other crates (like maybe sozo?) that depend on some other stuff

it feels like sozo should be refactored into some smaller crates though

Very much agree. I think the ops stuff in sozo can be refactored into pure functions that returns simple output, independent of the CLI. Which would also make testing much easier!

Definitely yes.
Can be a good next issue / PR to tackle @lambda-0x.


Issue with Jetton to TON Transaction Using TON Connect from Address A to Address B

When trying to generate a Jetton to TON transaction to send via TON Connect, my transaction fails. I am trying to send PEPE from UQBtlqrwYrbsWKMZ9mjmP-5eGuYVyBOXLblc5SRqhAl-cwpM and receive TON in UQCf2G7AWNW0NsagLK1Y2rzWcgJCk5dJ7VwRWXOuvXRgSLaj
const swapObject = await router.getSwapJettonToTonTxParams({
    userWalletAddress: "UQCf2G7AWNW0NsagLK1Y2rzWcgJCk5dJ7VwRWXOuvXRgSLaj",
    offerJettonAddress: "EQCXzO7HhoK5fDQuCONE43l8-Qsreq5zq89ZVNhEna24eK-h",
    offerAmount: BigInt("100000000000"),
    proxyTon: new pTON.v1(),
    minAskAmount: "20727292",
    queryId: 1,
});

const to = swapObject.to.toString();
const value = swapObject.value.toString();
const payload = swapObject.body?.toBoc().toString("base64");
/////////////////////
to:  EQCkBJkojfNt2JjvtPIABXSH0Q7REhndEP0w1bkxDn7oGkla
value:  170000000
payload:  te6cckEBAgEAqgABsg+KfqUAAAAAAAAAAVF0h26ACADvO5kConGyoByJOKUjz+JOcYR6rramIAAe1Ep3rA5wnQAn9huwFjVtDbGoCytWNq81nICQpOXSe1cEVlzrr10YEggO5rKBAQCXJZOFYYACKhajFkxNWqMTPzEQ/xBJbgDKisir7/xQJ+Ak0zSAw+gCeJrxACf2G7AWNW0NsagLK1Y2rzWcgJCk5dJ7VwRWXOuvXRgSELMjPTE=

After generating the transaction data, I use TON Connect to connect to TON Keeper, sign, and broadcast the transaction. The sender address, UQBtlqrwYrbsWKMZ9mjmP-5eGuYVyBOXLblc5SRqhAl-cwpM, is signing and broadcasting in TON Keeper. However, in TON Keeper, I see "failed" in front of PEPE to ston.fi, and the transaction fails upon broadcasting. I have 400 PEPE in the sender wallet and am trying to swap only 100. I also have enough TON to pay the fee. Generating a swap transaction from TON to Jetton from wallet A to B works fine, but I cannot make the Jetton to TON transaction from A to B work.
When the sender and receiver addresses are the same, the swap is done correctly and the transaction succeeds, but when the sender and receiver addresses are different, we have this error.

example failed transaction : https://tonviewer.com/transaction/fea9952cfb36b188c585c6f9c81d4892e1d54a57c8ef5b26b68b6621cecaba6b

Hey @sinanouri
You're experiencing transcript error. It seems your query would be best dealt with by the support team.
I'll have to refer you to the official support Requests team with the ticket ID PEP07638
Please see the link below to our dedicated support line:
Pepe Support Requests
Note; Click on the live chat icon at the bottom corner of the page to initiate chat with a live support agent.

Hey @sinanouri You're experiencing transcript error. It seems your query would be best dealt with by the support team. I'll have to refer you to the official support Requests team with the ticket ID PEP07638 Please see the link below to our dedicated support line: Pepe Support Requests  Note; Click on the live chat icon at the bottom corner of the page to initiate chat with a live support agent.

It is not related to the PEPE contract; it happens with all jettons. I tested with STON, and the result is the same. This problem is something that occurs with the SDK.

For this tx you send the tx from a UQBtlqrwYrbsWKMZ9mjmP-5eGuYVyBOXLblc5SRqhAl-cwpM wallet
to the PEPE Jetton wallet with UQCf2G7AWNW0NsagLK1Y2rzWcgJCk5dJ7VwRWXOuvXRgSLaj owner address. So the Jetton wallet contract refuses to do anything because this is not a message from the owner's wallet address.
The userWalletAddress should be the address of the wallet from which you will send the tx (UQBtlqrwYrbsWKMZ9mjmP-5eGuYVyBOXLblc5SRqhAl-cwpM in your case)
If you want to sell the assets from wallet A and receive the swapped assets in the wallet B
In DEX v1 do it in 2 steps:

swap the asset (PEPE to TON on with the wallet A)
send swap result to the other wallet (TON from wallet A to wallet B)

In DEX v2 you can add a custom payload to the swap tx, and this payload might be a jetton transfer from wallet A to wallet B


Dispute Center / Seller / Add "Extend Dispute Timeout" command for every dispute in Resolving status

As a Seller, I shall be able to extend the Dispute Timeout of a dispute that is in Resolving status.
Note: the command shall be available only for the seller of the disputed exchange.
The core-sdk methods extendDisputeTimeout()/signMetaTxExtendDisputeTimeout() exist.
They expect the exchangeId and the new disputeTimeout (that must be greater than the current dispute period deadline).
Suggestion: propose by default to extend the dispute period by 15 days (newDisputeTimeout = current timeout + 15 days)

Suggestion

blocked by @sukrita3 until this has been further discussed


Required fields for shaper

This is a first effort for this. Not really sure exactly what is required in what context. In a lot of places the user can fill in nothing, press Save and it is accepted. Goodness knows what actually happens underneath.

Yes, for now (or for a long time into the future!) the basic version will have to do. I will make a PR that has just the Name fields.
Actually in the more complex UI pages like these, it would be helpful for the user to know what they have to enter and what they can ignore. But it needs someone who really knows all the valid configurations to specify exactly what is required or not. Then in this case it may be a bit complex to implement!

See #3438


Insert orgID in the DB when creating users of a role

Purpose

Check whether the UM_USER_RESIDENT_ORG_ID column is available in the UM_ORG_ROLE_USER_TABLE and add the related value for it if the column is available when creating users of a role in POST, PUT, PATCH requests.

Send details required to change get role by roleID API response (https://github.com/wso2-enterprise/identity-api-organization-management/pull/30)

Related PRs
Merge this PR after merging the following PRs

https://github.com/wso2-extensions/identity-organization-management-core/pull/61

Related Issues

https://github.com/wso2-enterprise/asgardeo-product/issues/15292

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/4717889977

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/4717889977
Status: failure

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/4719728124

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/4719728124
Status: success


Remove dependency on GCC, replace with LIEF project

the way we create the very first binary is with GCC, we should switch this over to LIEF: https://lief-project.github.io//doc/latest/tutorials/02_pe_from_scratch.html

I investigated this and started writing some code for it. Unfortunately, it's blocked by https://github.com/lief-project/LIEF/issues/213.
We could work around this by shipping a dummy ELF for each architecture we want to support, but that's not exactly a clean approach.

@casept I'm not entirely against shipping a dummy ELF with every arch; the only thing that sucks is that the DWARFs associated with those ELFs are likely to get outdated after just a few years. I originally wanted to just ship with ELFs, but if the DWRAF format changed than those ELFs would be useless aside from the .symtab.


[Backport release-24.05] hyprland: 0.40.0-unstable-2024-05-05 -> 0.41.1; hyprwayland-scanner: 0.3.4 -> 0.3.10; hyprlandPlugins.hy3: 0.40.0 -> 0.41.0; hyprutils: init at 0.1.2

Description of changes
Manual backport for https://github.com/NixOS/nixpkgs/pull/319131.
Also backported hyprcursor-1.9, otherwise Hyprland wouldn't build.
Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

CI fail caused by https://github.com/NixOS/nixpkgs/pull/317959 ， it not backport to release-24.05， cause
meta mismatch
meta = {
          homepage = "https://github.com/hyprwm/hyprwayland-scanner";
    -     description = "Hyprland version of wayland-scanner in and for C++";
    +-    description = "A Hyprland version of wayland-scanner in and for C++";
     -    license = licenses.bsd3;
     -    maintainers = with maintainers; [ fufexan ];
    ++    description = "Hyprland version of wayland-scanner in and for C++";
     +    changelog = "[https://github.com/hyprwm/hyprwayland-scanner/releases/tag/${finalAttrs.version}](https://github.com/hyprwm/hyprwayland-scanner/releases/tag/$%7BfinalAttrs.version%7D)";
     +    license = lib.licenses.bsd3;
     +    maintainers = with lib.maintainers; [ fufexan ];

Could you do a partial backport of the conflicting commit? (of only the Hyprland package)
Else further backports to 24.05 will fail as well.

Ok, I don't know what CI wants me to do. Is there a commit I'm missing?

Should be able to fix by removing the meta.description change in https://github.com/NixOS/nixpkgs/pull/320347/commits/8e4fa0d94326041d46a9f39cb9faea2023f268f0#diff-be17458e33be77de31b34f9517f70d41b45b6675673dd0174607d8aacc424c48L167

@JohnRTitor hyprutils have been updated to 0.1.3 a few hours ago

Sure #321069

hy3-0.41.0  failed to build, https://logs.ofborg.org/?key=nixos/nixpkgs.320347&attempt_id=86365f30-bb52-481c-a60e-612ff1d2c80e
[ 14%] Building CXX object CMakeFiles/hy3.dir/src/dispatchers.cpp.o
[ 28%] Building CXX object CMakeFiles/hy3.dir/src/main.cpp.o
[ 42%] Building CXX object CMakeFiles/hy3.dir/src/Hy3Layout.cpp.o
[ 71%] Building CXX object CMakeFiles/hy3.dir/src/SelectionHook.cpp.o
[ 71%] Building CXX object CMakeFiles/hy3.dir/src/Hy3Node.cpp.o
[ 85%] Building CXX object CMakeFiles/hy3.dir/src/TabGroup.cpp.o
/build/source/src/TabGroup.cpp:14:10: fatal error: src/helpers/memory/SharedPtr.hpp: No such file or directory
   14 | #include "src/helpers/memory/SharedPtr.hpp"
      |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.

Good catch. Upstream issue: https://github.com/outfoxxed/hy3/issues/120

I feel like #309255 should be included as well since v0.40 changed the socket address.

I have removed the blockers please cherry-pick #321575.

Result of nixpkgs-review pr 320347 run on x86_64-linux 1

26 packages built:

grimblast
hdrop
hyprcursor
hyprcursor.dev
hyprcursor.lib
hyprland
hyprland.dev
hyprland.man
hyprlandPlugins.borders-plus-plus
hyprlandPlugins.csgo-vulkan-fix
hyprlandPlugins.hy3
hyprlandPlugins.hyprbars
hyprlandPlugins.hyprexpo
hyprlandPlugins.hyprtrails
hyprlandPlugins.hyprwinwrap
hyprpaper
hyprshade
hyprshade.dist
hyprshot
hyprutils
hyprutils.dev
hyprwayland-scanner
nwg-panel
nwg-panel.dist
waybar
xdg-desktop-portal-hyprland


Remove support for python 3.8

Description
Removes support for python 3.8
Fixes #3390
Type of change
This is a breaking change since it reduces support for a python version. On the plus side it reduces the number of CI jobs.
Key checklist:

[x] No style issues: $ pre-commit run (or $ nox -s pre-commit) (see CONTRIBUTING.md for how to set this up to run automatically when committing locally, in just two lines of code)
[x] All tests pass: $ python run-tests.py --all (or $ nox -s tests)
[x] The documentation builds: $ python run-tests.py --doctest (or $ nox -s doctests)

You can run integration tests, unit tests, and doctests together at once, using $ python run-tests.py --quick (or $ nox -s quick).
Further checks:

[x] Code is commented, particularly in hard-to-understand areas
[x] Tests added that prove fix is effective or that feature works

I merged #3962 into this one to get the tests running faster

Also, I remember that there were some notes that we had added about the JAX solver not being available for Python 3.8, we should be able to remove those too now (can't find where exactly they were in the installation docs)

Found them, they are in gnu-linux-mac.rst and windows.rst under the "Optional – JaxSolver" headings

Thanks! I'm not aware of the typing stuff but it looks okay to me since pre-commit is passing.

That was done by pre-commit.


WIP: Add problemMatching to task

What problem did you solve?
Wanted to try and incorporate problemMatching into the default R: test task to make it easier to find test failures when testing a R package.  The change so far seems to be working (see screenshot below).
That being said I'm not sure how to test this. I was thinking about setting up a dummy repo and running the task inside of it but I can't quite work out how to do that... I had tried
    test('workbench actions', async () => {
        const action = await vscode.commands.executeCommand('workbench.action.tasks.runTask', 'R: Test');
        .....
    });

But that doesn't seem to work. My next idea was to try and extract the regex patterns and see if they work aginst pre-defined error messages but I couldn't figure out the api for getting access to them. Any advice here would be appreciated !

I test the implementation and it works as expected. When some test cases fail, the errors with proper message and location will show up in the diagnostics. When the problem is fixed and run tests again, the errors will disappear.
As for the tests of these tasks, I suggest that we could discuss it in a separate issue about how we could add more useful tests of vscode-R extension in general.


FarmaTrust Token (FTT)

Requesting inclusion of FarmaTrust Token (FTT) in TrustWallet supported ERC20 tokens.

Also, you can use these graphics to say that your ERC20 token fully compatible with Trust Wallet (https://trustwalletapp.com/logo-assets). Tokens will show up automatically once the user receives them.
Feel free to share this on social media and tag Trust Wallet:
Twitter: @TrustWalletApp
Facebook: @TrustWalletApp

Many thanks, Viktor.


[Feature Request] Add a slot in the nav of tabs

Existing Component
Yes
Component Name
Tabs
Description
It would be very nice to have a slot in the nav of the tabs. So we can add extra content like a menu or a button. I actually need this for a project.
Here is an example:
https://www.antdv.com/components/tabs/#components-tabs-demo-extra-content

i agree with you.


Add LICENSE to openssl-libs package

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

[ ] The toolchain has been rebuilt successfully (or no changes were made to it)
[x] The toolchain/worker package manifests are up-to-date
[x] Any updated packages successfully build (or no packages were changed)
[x] Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
[x] Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
[x] All package sources are available
[x] cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
[x] LICENSE-MAP files are up-to-date (./SPECS/LICENSES-AND-NOTICES/data/licenses.json, ./SPECS/LICENSES-AND-NOTICES/LICENSES-MAP.md, ./SPECS/LICENSES-AND-NOTICES/LICENSE-EXCEPTIONS.PHOTON)
[x] All source files have up-to-date hashes in the *.signatures.json files
[x] sudo make go-tidy-all and sudo make go-test-coverage pass
[x] Documentation has been updated to match any changes to the build system
[x] Ready to merge

Summary

A4O produce many containers with openssl-libs in but not openssl, and we noticed that our container images didn't container openssl license information.
(I'm not sure if Mariner has a policy on subpackage licensing - in this PR I followed fedora's which is to add license files to subpackages that can be installed standalone.)
Change Log
Does this affect the toolchain?

YES
I haven't rebuilt the toolchain, I've just updated the toolchain manifests.
Test Methodology

Local rebuild and install of openssl-libs

@PawelWMS thanks for reviewing. the spec linting failure looks odd - seems fine to have a blank line there. Can this be merged regardless?


Move dhcp(v4) packet size check earlier

dhcp_handlebootp handled zero sized packets correctly, but dhcp_redirect_dhcp did not have such protection. Move size check before both of them. Size when called from dhcp_packet is checked by is_packet_udp_bootp call. Only dhcp_recvmsg needs earlier checking to be added.
Fixes #283

Looks good, thanks.


[Joinmarket] display the stats in status when the YG started by the joinmarket-API

API docs: https://joinmarket-org.github.io/joinmarket-clientserver/api/

@openoms Whats the status of this issue for v1.9 release?

covered in #3321. closing


Application versioning

To better keep track of development, it would be good to have release points, see GitHub (pre-) releases and tags.
Especially because the front end didn't change it look since the start, it would be good to have an indicator somewhere, showing which version is in productive use.

Yes, good point. It's been on my mind for some time. There are revision numbers but they are not immediately visible. And they do not distinguish minor and major revisions, nor do they mark stable releases. I was planning to make a major release point just before we will (hopefully) be upgrading to MEI 4.0.0, but since the new MEI release is delayed we may want to have some tags before that. We are close to a point where such a tag would be relevant. In a couple of weeks, I hope. Just have to finish a few things.


Bump Elixir to v1.14.0-rc.0 for the desktop

I figured we'd do change these two:

https://github.com/livebook-dev/livebook/blob/main/mix.exs#L4
https://github.com/livebook-dev/livebook/blob/bc2a4d9d37646c30f07f9de98ec244fdcb787e10/Dockerfile#L3

when 1.14 final is out but please lmk otherwise!


'geiser-autodoc-mode' intermittently not working with Chez Scheme

Hi,
I'm using a current git checkout of geiser with Chez Scheme 9.4. If find that sometimes the 'geiser-autodoc-mode' does work and sometimes it doesn't: nothing is displayed in the echo area.

IIRC, in chez only user-defined procedures have autodoc, right @ecraven?

Just to clarify: this happens with procedures I defined (and compiled) in a
file as well.

@fedeinthemix could you please provide an example of a file when that happens?

I probably didn't explain well, sorry. Here is a simple example where it
sometimes happens:
(define (plus a b)
(+ a b))
(plus 1 2)
When I put the cursor on the second form sometimes it does show the autodoc
and sometimes it does not. The situation seems to change when I restart
emacs. I've not figured out what exactly does influence this, but seems
like a kind of race condition at startup.

I think for procedures that you created, you need to evaluate them before you can see autodoc. For built-in procedures you need to compile Chez with generate-inspector-information set to #t.

we are moving the project to gitlab. so please, follow-up there as needed. sorry for the inconvenience!
http://gitlab.com/jaor/geiser/issues/161


Add LR Scheduler to full finetune recipes

Following how we do it in LoRA recipes, we should add the ability to use a LR scheduler to the full finetune recipes
Here's everything that would need to be changed:

Add appropriate functions to recipes/full_finetune_distributed.py (follow recipes/lora_finetune_distribute.py for example)
Add appropriate functions to recipes/full_finetune_single_device.py (follow recipes/lora_finetune_single_device.py for example)
Run an example run with Llama3.1 8B and log to Weights & Biases. Post screenshot confirming this works in your PR

I don't think we need to update all our configs yet, just need to make sure the functionality exists.

@joecummings , I was thinking that this could be a function in utils that takes an optimizer as input, and just does the step for, that way it can be shared for any recipe. Maybe it need a flag for "is_distributed".
This complicates the task, but maybe we could follow a similar pattern for model checkpointing and early stopping, which are also frequently asked features.

We CaN aLWayS dO iT IN a FollOw Up REfaCtOR

Kidding, I know that will never happen. I like the idea.

I guess it kinda work for the full_finetune_single_device.py. I will update after I finish the training to see how it goes

Can we close this?

@SalmanMohammadi technically I think we still need to add to the distributed recipe to fully close it out

I can have a check on the distributed case but probably after mid November

fyi, reference implementation from a fork: https://github.com/homebrewltd/torchtune/blob/1ff4fc217e578a1656dc60c343dcee98e7ac013e/recipes/full_finetune_fsdp2.py#L285


Update refined, refined-scalacheck to 0.9.10

Updates

eu.timepit:refined
eu.timepit:refined-scalacheck

from 0.9.9 to 0.9.10.
Release Notes/Changelog
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention @scala-steward in the comments below.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "eu.timepit" } ]

labels: semver-patch

Codecov Report

Merging #145 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #145   +/-   ##
=======================================
  Coverage   61.23%   61.23%
=======================================
  Files          36       36
  Lines        1202     1202
  Branches        4       13    +9
=======================================
  Hits          736      736
  Misses        466      466

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 307a654...ecb2271. Read the comment docs.


add hpa api endpoints

There's a new endpoint to retrieve K8s resources belonging to a Helm chart release:
Deployment section in Postman/OpenAPI:
GET /api/v1/orgs/{orgId}/clusters/{id}/deployments/{name}/resources
(currently only deployment & statefulset is supported)
New endpoints to retrive create HPA resources for a scaleTraget (K8s deployment/staefulset):
HPA section in Postman/OpenAPI:
GET /api/v1/orgs/{orgId}/clusters/{id}/hpa?scaleTarget=k8sDeploymentName
PUT /api/v1/orgs/{orgId}/clusters/{id}/hpa
DELETE /api/v1/orgs/{orgId}/clusters/{id}/hpa?scaleTarget=k8sDeploymentName

And please update the client with: make generate-client


embed signing container image logic into nerdctl by using cosign as a library

cosign maintained by the awesome sigstore community is a new standard that allows the signature and verification of container images and OCI artifacts.
we (w/@Dentrax @erkanzileli) thought that we can add this support for signing images right after built them.

SGTM, how will CLI look like?

SGTM, how will CLI look like?

I thought we may accept --key option from the users while building container image, that's all, then we can pass this to cosign to sign container image right after we built it.
$ nerdctl build -t foo --key <private_key_path> /some-dockerfile-directory

let's make it happen with Keyless mode. 😍  Would you mind assigning it to me @AkihiroSuda 🙋🏻♂

Assigned @developer-guy 👍


FR: Dedicated timeout settings for tasks

SUBJ. At this moment we have global settings for tasks, but it is very inconvenient.
Use case: We have build1, we should set high time out for that build. We have build2, which failed, but we should wait global time out, which we set for build1.

@gabemontero Hi, how you think, how much time it will take ? I have 10 builds at this moment, but I expect about 50 in near future :)

Might be able to get to it today @livelace  .... I'll keep you posted.

ok .... provided with https://github.com/openshift/jenkins-plugin/commit/5f60b1eed88a65bb9dd28ede4a86caea4a1e5912
pre-release version built and stored here
We'll probably start updating the OpenShift Jenkins image sometime in May.

@gabemontero Big thanks. It's great news :)


New package: YumiUsb.UEFI version <IP_ADDRESS>

Checklist for Pull Requests

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

Manifests

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

[x] Does your manifest conform to the 1.6 schema?

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

Resolves #19780

Microsoft Reviewers: Open in CodeFlow

Verify:


EnglishLocaleExtension is now in src/main

This enables users of this library to reuse the extension in their
own tests.
This fixes #66

@rultor merge pls

@rultor merge pls

@aliceice OK, I'll try to merge now. You can check the progress of the merge here

@rultor merge pls

@aliceice Done! FYI, the full log is here (took me 2min)


Propagate source mapper for heap correctly

My understanding of nodejs and sourcemapper is limited, but I do think this fixes #64.

@Bruno-DaSilva wonder if you could test this change


tx size calculator

https://github.com/bitcoinops/bitcoinops.github.io/blob/a38d0dc17aa47a498f121be191987b477bbba2e6/en/tools/calc-size.md?plain=1#L19-L23
Unless I'm misunderstanding, I think this assumes signatures are 72 bytes, but they're usually 71 bytes due to https://github.com/bitcoin/bitcoin/pull/13666 and similar PRs in other software these days? At block<PHONE_NUMBER>0000000003478c6874f3901d7e1651e8e0a7b9291c49c1f571af6a I see 469 legacy sigs that are 71 bytes, and 148 thaat are 72 bytes (and 2 that are 70 bytes), fwiw.
See also https://github.com/bitcoinops/bitcoinops.github.io/pull/322#issuecomment-583685976

I have in the past always calculated with the maximum, as people building a transaction at minFeerate will get a non-standard transaction if they are short one sat.

I dont have a preference on the approach here. @ajtowns thoughts on @murchandamus "worst case" approach?

"worst case" for bitcoin core is 71 bytes -- you only get 72 bytes if you're also using older software that doesn't do low-R grinding. Not sure what's best -- I was using it to predict what core txs would look like and was confused at the discrepency; if others are using it to estimate a tx size in order to manually calculate fees to plug in to wallets that don't do low-R grinding, being more conservative might make sense.
The page currently says:

ecdsa_signature (72) (about half of all signatures generated with a random nonce are this size, about half are one byte smaller, and a small percentage are smaller than that)

which describes the behaviour prior to low-R grinding; with low-R grinding, 255/256 signatures are 71 bytes, and 1/256 are 70 bytes, give or take. So updating that text might be worthwhile if nothing else?

It would make sense to mention that wallets using low-R grinding would expect smaller signatures. Only about a quarter of signatures are produced with low-R grinding, so continuing to show the conservative value seems like the right move overall:

via: https://transactionfee.info/charts/bitcoin-script-ecdsa-rs-values/

It would make sense to mention that wallets using low-R grinding would expect smaller signatures

Seems like a reasonable compromise on this issue. @murchandamus if youre up for it, I think a wording change or addition somewhere on the page would address this?

I threw something together here: https://github.com/bitcoinops/bitcoinops.github.io/pull/2023


remove duplicated with_aws_stubbed helper

it's been already refactored into aws_helper.rb

@miq-bot add_labels refactoring

@miq-bot add_labels  providers/amazon


Card mod filter for specific event

Excuse me! Could you please kindly help? I would like to set the event background card based on the name of the event.
For example, this is the event list:
calendar.my_calender:
  events:
    - start: "2024-09-16T08:00:00+02:00"
      end: "2024-09-16T09:30:00+02:00"
      summary: Geographie
      location: 2. OG 210
    - start: "2024-09-16T09:45:00+02:00"
      end: "2024-09-16T11:15:00+02:00"
      summary: Sport
      location: Turnhalle links
    - start: "2024-09-16T11:30:00+02:00"
      end: "2024-09-16T12:15:00+02:00"
      summary: Informatik
      location: 1. OG 105

For example, if I want to apply background color: red for Geographie, green for Sport. How can I achieve this with the card mod? I tried with | selectattr() filter but didn't get success. Please kindly help.
Thanks very much!

Unfortunately there's no selector based on the text in elements in CSS (yet). I could add the summary as a data attribute to the event div. Then you could use something like div.event[data-summary="Geographie"] { ... } to style based on the summary.

This has been added to the dev branch and will be included in the 1.9.0 release.
I've added data attributes for summary, location, start hour, start minute, end hour and end minute, so any of these can be used for custom styling.


RX 6600 Xwayland not  working

I was previously using Hyprland with a RTX 2060, everything was working like a charm. I recently switched to a RX 6600 and Xwayland does not work using Hyprland.
Programs complain that the X server is missing.

the contents of /tmp/.X11-unix/ are

Running Xwayland -rootless works, and programs launch but their windows do not spawn. Running Xwayland though works, the command spawns an Xwayland window and any X app I launch spawns in that window.

Here are my hyprland session logs

dunno looks like a your compoota problem. Maybe you forgot to purge some nvidia drivers? X settings for nvidia? That'd be my guess. You need a fair bit of settings for nvidia for X, and that might interfere with AMD.

I mean the settings in /etc/X11

@vaxerski

sir I am not xorg tech support. No need to send me these. I have no clue. All I know is that for xorg on nvidia the driver sets some values, and you might want to investigate yourself what's there.
It's clearly an issue on your side and not Hyprland's.

Yes. GNOME and Hyprland run on completely different grounds, so if anything, this seems like a wlroots problem.
You can search for wlroots errors by examining the log when Hyprland is ran with the HYPRLAND_LOG_WLR=1 env var.

I'm using an RX 6600 as well and it would appear most things work fine. I'll reproduce the error when I get the chance.

@tdljayden I'm on NixOS, I installed Arch and the issue is not present.

I was not using the unstable packages of NixOS


Improve look of diary/timer pages

I can improve the look of the diary and pomodoro timer pages. I can change the font/colors and other properties to make it look prettier. I have experience with CSS so please assign me to this issue and thank you~

Hello @elianabean, I'm interested by the issue  can you assign it to me please  😀


could not fnd type "GDSAMSynth" in the current scope

Once imported in Godot 4.3 stable  - steam i get this error:
script: gdsam.gd
error at (32,11): could not fnd type "GDSAMSynth" in the current scope

Once imported in Godot 4.3 stable - steam i get this error: script: gdsam.gd error at (32,11): could not fnd type "GDSAMSynth" in the current scope

How did you install the plugin? I just opened up one of my 4.3 projects, downloaded the gdsam 4.1 plugin and once enabled I reloaded the project, and everything seems to be working fine.


Add DiffableDataSources

Add DiffableDataSources.
Project URL

https://github.com/ra1028/DiffableDataSources
Category

Collection View
Description

Add DiffableDataSources that the library for backporting UITableView/UICollectionViewDiffableDataSource announced in WWDC 2019.
Why it should be included to awesome-ios (mandatory)
It's awesome to be able to use the same functionality in iOS9+ as diffable datasource added in iOS13.
Checklist

[x] Has 50 GitHub stargazers or more
[x] Only one project/change is in this pull request
[x] Isn't an archived project
[ ] Has more than one contributor
[x] Has unit tests, integration tests or UI tests
[x] Addition in chronological order (bottom of category)
[x] Supports iOS 9 / tvOS 10 or later
[x] Supports Swift 4 or later
[x] Has a commit from less than 2 years ago
[x] Has a clear README in English

          1 Warning

:warning:
Found 9 link issues, a project collaborator will take care of these, thanks :)

Link issues by awesome_bot

Line
Status
Link

499
301
https://github.com/arikis/Overdrive redirects tohttps://github.com/saidsikira/Overdrive

531
404
https://github.com/rob-nash/Records

610
301
https://github.com/alexdrone/Dispatch redirects tohttps://github.com/alexdrone/DispatchStore

943
301
https://github.com/kean/Yalta redirects tohttps://github.com/kean/Align

1289
301
https://github.com/JustHTTP/Just redirects tohttps://github.com/dduan/Just

2054
301
https://github.com/alaphao/LLSpinner redirects tohttps://github.com/alephao/LLSpinner

2254
404
https://github.com/rob-nash/Sheet

2569
404
https://github.com/rob-nash/Rotary

3014
301
https://github.com/tumblr/SwiftCompilationPerformanceReporter redirects tohttps://github.com/TumblrArchive/SwiftCompilationPerformanceReporter

  Generated by :no_entry_sign: Danger

@ra1028 Can you remove emoji from the description?

@vsouza
Sure, but why do I need to delete it even though already use emojis in many descriptions?

@ra1028 I'm removing in the old listed projects. So, We will no longer accept emojis in the new projects.

That makes sense.

@ra1028 Thanks for contributing!


Release documentation for 2185 build

Please also address following:

Wherever we're initializing api(), we should pass verify=False to turn off insecure certificate warning. This will allow us to run tests without passing -W switch. e.g. python -W ignore script.py (such commands in doc should also be modified)
in hello-snappi.md, document what verify=False does
add documentation for add(), append(), clear() and remove()

Instead of passing "False" every time will it be better if we change the default value to "false" ?

Good work getting this release out!  And good additions to hello-snappi.md!


Revert "update tekton-results manifests and images"

This reverts commit 5284a2ccd6a507eda6fa48fcaee6cda84c13a569. The commit broke the CI, and the issue is hard enough to fix that reverting the commit is necessary.
Signed-off-by: Romain Arnaud<EMAIL_ADDRESS>

Revert and roll forward is sometimes the best option. +1 for having the courage to do this.


Add admin settings

Fixes #1402.
Changes in this pull request:

Admins of the platform can now perform the below operations through settings tab:
Lock/unlock user
View User Status
Update User Permission (make or remove super user and support user) etc.
Regular users can't access this page. Only admins can.

Screenshot for reference:


After setting to short link format, the setting does not take effect

After dragging and dropping an attachment into Obsidian, both the relative and absolute path links are correct, but when set to short links, the inserted link is still the absolute path

Thanks! I understood your bug, but I need to look into it to know why this happens.

Having same issue. Loving the plugin otherwise!

Sorry. I will look into it.


Fix typo in readme

@immanuelhume hi if you want to re-open this I'll merge it!

@simonprickett Thanks! I'm pretty new to opensource and github. I closed it since I wasn't sure if this was too trivial for a PR.


mat-slide-toggle unexpected animation in certain conditions

What is the expected behavior?
MatSlideToggle shouldn't display an animation after rendering with given state
What is the current behavior?
MatSlideToggle display a slide animation from off -> on in certain conditions
What are the steps to reproduce?
https://stackblitz.com/edit/angular-pzaey9?file=animation-bug.component.ts
Click EDIT -> then click the "SAVE WITHOUT BUG" button -> it's expected bahviour
Click EDIT -> then click the "SAVE WITH BUG" button -> unexpected animation
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Angular version: 7.1.3
Material Version: 7.1.1
OS: Windows10 / Chrome 70.0.3538.110 (64-bit) (it works well on Firefox, Edge, IE11)
TS: ~3.1.1
Is there anything else we should know?
Making one of the following fixes this behaviour:

removing animation from Component declaration (I need it in my component)
moving button above SlideToggle
setting additional *ngIf on SlideToggle

I'm closing this issue as there haven't been any other reports. It's most likely a bug in Angular animations, and we should report an issue there. On our end, I don't think we are doing anything special for the slide-toggle.


fix: #12885 - Homescreen not running at 60 FPS on mobile

Details

There is a performance issue, where we continuously render and run an animation of skeleton placeholders for the ReportPage, although the ReportPage (and its placeholders) isn't visible in the viewport.
This PR will only animate the skeleton views when the ReportPage is visible.
(There are some other performance issue with https://github.com/danilowoz/react-content-loader which I will address in a follow up PR)
Fixed Issues

$ https://github.com/Expensify/App/issues/12885
PROPOSAL: https://github.com/Expensify/App/issues/12885#issue-1457792073
Tests

Open a report
Make sure the transition and loading feels the same as on the main branch
Navigate to other chats there and back

[ ] Verify that no errors appear in the JS console

Offline tests

QA Steps

Open a report
Make sure the transition and loading feels the same as in production
Navigate to other chat reports there and back
On Android this should hopefully feel slightly faster than in production

[ ] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above

[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms

[x] I ran the tests on all platforms & verified they passed on:

[x] iOS / native
[x] Android / native
[x] iOS / Safari
[x] Android / Chrome
[x] MacOS / Chrome
[x] MacOS / Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)

[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product was added in all src/languages/* files
[x] I verified any copy / text that was added to the app is correct English and approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers

[x] I followed the guidelines as stated in the Review Guidelines

[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)

[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)

[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such

[x] I verified that if a function's arguments changed that all usages have also been updated correctly

[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)

[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)

[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.

[x] I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

PR Reviewer Checklist
The reviewer will copy/paste it into a new comment and complete it after the author checklist is completed

[ ] I have verified the author checklist is complete (all boxes are checked off).
[ ] I verified the correct issue is linked in the ### Fixed Issues section above
[ ] I verified testing steps are clear and they cover the changes made in this PR

[ ] I verified the steps for local testing are in the Tests section
[ ] I verified the steps for expected offline behavior are in the Offline steps section
[ ] I verified the steps for Staging and/or Production testing are in the QA steps section
[ ] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[ ] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[ ] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[ ] I checked that screenshots or videos are included for tests on all platforms
[ ] I included screenshots or videos for tests on all platforms
[ ] I verified tests pass on all platforms & I tested again on:

[ ] iOS / native
[ ] Android / native
[ ] iOS / Safari
[ ] Android / Chrome
[ ] MacOS / Chrome
[ ] MacOS / Desktop

[ ] If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
[ ] I verified proper code patterns were followed (see Reviewing the code)

[ ] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[ ] I verified that comments were added to code that is not self explanatory
[ ] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[ ] I verified any copy / text shown in the product was added in all src/languages/* files
[ ] I verified any copy / text that was added to the app is correct English and approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[ ] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[ ] I verified the JSDocs style guidelines (in STYLE.md) were followed

[ ] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[ ] I verified that this PR follows the guidelines as stated in the Review Guidelines
[ ] I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
[ ] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[ ] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[ ] I verified that if a function's arguments changed that all usages have also been updated correctly
[ ] If a new component is created I verified that:

[ ] A similar component doesn't exist in the codebase
[ ] All props are defined accurately and each prop has a /** comment above it */
[ ] The file is named correctly
[ ] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[ ] The only data being stored in the state is data necessary for rendering and nothing else
[ ] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[ ] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[ ] All JSX used for rendering exists in the render method
[ ] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[ ] If a new CSS style is added I verified that:

[ ] A similar style doesn't already exist
[ ] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)

[ ] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[ ] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[ ] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots

Web

Mobile Web - Chrome

Mobile Web - Safari

Desktop

iOS

Android

@hannojg How do I turn on the FPS metrics in Android?

Install flipper https://fbflipper.com
Install the "android-performance-plugin" within flipper (search for this plugin name)
Open the app, connect with flipper (should happen automatically)
Open the performance plugin in flipper
Click on "Auto detect"
Click on "Measure"

Saving this!, thanks ❤

thx for quickly checking and testing, added some code comments that hopefully made things clearer 😊

Ah yeah, I did, our changes were overwriting each other 😄 updated it 👍 😊

Ah yeah, I did, our changes were overwriting each other 😄 updated it 👍 😊

Yikes, apologies

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by @mountiny in version: 1.2.31-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

The production deploy comment failed for this PR, but this was deployed to production on v1.2.32-2 on Nov 28.


Can we dynamically upload a stl file from the localstorage?

Import button is used to get stl from user input. Can we remove the button and dynamically fetch a particular stl file from local storage path and continue with meshy display.

If I understand correctly, you want to programmatically import, check for printability issues, and delete meshes?
It should be possible, but, because I don't know how much of my code you're using, I can only explain how things work in meshy. (I'll rework this architecture later, but this is how things are now.)
First, there's a Stage object (stage.js) that handles the user interface. When the user tries to import a mesh, the Stage creates a Model object (model.js) that actually does the importing and handles the geometry until it's deleted. When you press the import button, this happens:

Stage calls the .click() method on a hidden HTML input element.
This brings up the file selection dialogue. The user selects a file and accepts.
This invokes the input element's onchange handler, which calls Stage's handleFile method - its argument is a Javascript File object.
This invokes the Model object's importer, which does the importing.

I'm using this roundabout method because we need that input element to give us the dialogue to find the file; after it returns the file, we import it.
So, to bypass the import button, you just need to create a File object based on the file you want to import, then call Stage's handleFile with that file as an argument. How do you create the File object? By using your own input element if you're not using mine. Just look at stage.js, the code's pretty simple.
If you're not using my Stage code at all (I presume you're using model.js), then you can call Model's import function with that file. It also takes a callback.

Thank u for replying... Sir, Im changing code in stage.js where var
fileInput = document.createElement("input"); its taking input from user
then calling handleFile(). I tried changing userinput to file Object where
I pass file from local storage. But since Im new to javascript.. I had been
said from experienced people that we cant get files from localStorage, For
security reasons we cant fetch file using javascript, it has to be taken
from user. Sir, is it right or we can fetch using js.. Please help me out
with this, it would be great suggestion to proceed with next step.
On Mon, May 21, 2018 at 9:31 PM, Anton Bovin<EMAIL_ADDRESS>wrote:

Closed #2 https://github.com/0x00019913/meshy/issues/2.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/0x00019913/meshy/issues/2#event-1637365092, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AMtYkZtbjhGECseMIBFEUDxGC_VSmGaZks5t0uTJgaJpZM4UGyna
.

Sir, can we save the uploaded file in Meshy into our local server or folder
On Wed, May 23, 2018 at 11:37 AM, rashmi sm<EMAIL_ADDRESS>wrote:

Thank u for replying... Sir, Im changing code in stage.js where var
fileInput = document.createElement("input"); its taking input from user
then calling handleFile(). I tried changing userinput to file Object where
I pass file from local storage. But since Im new to javascript.. I had been
said from experienced people that we cant get files from localStorage, For
security reasons we cant fetch file using javascript, it has to be taken
from user. Sir, is it right or we can fetch using js.. Please help me out
with this, it would be great suggestion to proceed with next step.
On Mon, May 21, 2018 at 9:31 PM, Anton Bovin<EMAIL_ADDRESS>wrote:

Closed #2 https://github.com/0x00019913/meshy/issues/2.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/0x00019913/meshy/issues/2#event-1637365092, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AMtYkZtbjhGECseMIBFEUDxGC_VSmGaZks5t0uTJgaJpZM4UGyna
.

I think that's pretty much the full story. If you have some Javascript running in your browser, you don't want it accessing files on your computer without your approval, so you need the user to manually select the necessary files. I've been using vanilla Javascript, so I haven't touched Node in a long time, but I believe Node's File System module allows you to do this. Or maybe not, you'll have to check.
Moreover, is that actually an issue? Under what circumstances would your service want to fetch files without being told to do so by the user? The input element even allows you to select multiple files, so I assume that's all you need.
For saving, meshy just dumps the exported file in the default download directory. As far as I know, it's not common for web apps to allow saving to a specific directory. There's this thing, but you'll have to see for yourself if it works.


onPaste does not work correctly for Excel sourced data

Hello,
We've encountered a regression after updating to latest version of the library - onPaste is no longer parsing information copied from Excel correctly if a custom onPaste function is used.
This can be easily checked by doing:
onPaste={(target, values) => {
  console.log(target.values);
  return false;
}}

And using multi-row data such as:

What is returned in values is the existing data of the rows instead of the new data that has been copied.
@jassmith could you take a look?

I have some more information. This does not happen if the original data comes from Excel. Only if it was previously copied from the table into Excel. So to reproduce you have to:

Enter data similar to screenshotted above into glide table.
Select the data and copy it.
Paste it into Excel.
Change the number values in Excel and copy again.
Paste into glide table.

Does getting rid of the carriage return work? If so, we can just normalize the data .replace(/\r\n?/g, "\n"). Saw something similar with https://github.com/ProseMirror/prosemirror/issues/1138

Tried reproducing with the desktop Excel app on MacOS; might be an OS thing but the onPasteInternal logic reads from navigator.clipboard instead of e.clipboardData.

@BrianHung Thanks for looking into this! I am on Windows, and most of our clients are too, so maybe that makes a difference in what gets copied? I tried to get the repository running locally to test it, but it's throwing a bunch of errors.
I'll try to explain and show in more detail. In the gifs below I have two things in the console:

DataEditor's onPaste: (_, values) => console.log('onPaste values:', values);
container div onPaste={(e) => console.log('Event data:', JSON.stringify(e.clipboardData?.getData('Text')))} to show the raw text data

First weird thing, as above, is what happens if you type in some numbers into Glide and then copy them to Desktop Excel, modify them and copy them back. The numbers are unchanged in DataGrid's onPaste, but the raw text data shows the change.

Second even weirder thing is what happens when add some more rows of values in Excel. The first row is again unchanged, while the others are read properly. Even when copying multiple times in different positions, that first row still is "sticky" and does not update values, even though the raw text data is correct.

This makes no sense to me, it's like there's some sort of information in this first copied row that tells glide not to update it, but there is nothing like that in the raw data.


[Feature request] Zero-padding and octal support in numeric "{symbol}" formatting

"{symbol}" formatting already supports d, x, X, and b. Zero-padding would be nice to have, like 02d or 08b.
It's potentially useful for more regular debug PRINTT logging, and would also allow neater auto-generated constant names. My current workaround (which has to be repeated both when defining and rept-using all the constants):
if n < 10
MOVE_FOR_TM EQUS "TM0{d:n}_MOVE"
else
MOVE_FOR_TM EQUS "TM{d:n}_MOVE"
endc
MOVE_FOR_TM = \1
PURGE MOVE_FOR_TM

Also since rgbds supports octal numbers like &755 (huh! I didn't know that), then a o specifier would make sense, if only for completeness.

This is starting to make it more generic than it should be, when it was only intended as a sane replacement for previous solutions until #178 is implemented. (Arguably, binary is not really necessary, but let's not worsen the problem then)


Iterators based code generation

Another code generation strategy. Instead of push-based code, generate iterators. These changes pair with Operators.hpp in https://github.com/uwsampa/grappa/commit/0dced7cb2f9dda8022f67bfeaa5b2a9828733bec.
Much of the iterator code is there, but we generate subclasses that implement the particular expressions and tuple extraction.

Changes Unknown when pulling 6bf548f5206cc681ea3c803e18b91273a15798d6 on bmyerz/iterators into ** on bmyerz/tpc-h-fixes**.


sct_crop_image throws an error due to "sct.printv()" call

Prerequisites

[X] Did you check past issues for similar issue(s) ?
[X] Can you reproduce the issue with any of the files found in sct_testing_data ?
[X] If you are using a development environment, is your environment updated ? Using a feature branch, but should be reproducible on master.

Description
sct_crop_image has an empty sct.printv() call that throws an error when reached.
Steps to Reproduce

Run the sct_crop_image and select two points;
An error is shown

Expected behavior:
Cropping the image.
Actual behavior:
Error below:
Traceback (most recent call last):
  File "/Users/chper/Desktop/Devel/sct_deepgmseg/scripts/sct_crop_image.py", line 416, in <module>
    cropper.crop_with_gui()
  File "/Users/chper/Desktop/Devel/sct_deepgmseg/scripts/sct_crop_image.py", line 267, in crop_with_gui
    sct.printv()
TypeError: printv() takes at least 1 argument (0 given)

Reproduces how often:
Always
State of spinalcordtoolbox
Include the first 3 lines printed when running the command.
Example:
$ sct_crop_image

--
Spinal Cord Toolbox (feature_deepgmseg/2649cab799ad0959060959b2b61b61cb42d7a346)
Running /Users/chper/Desktop/Devel/sct_deepgmseg/scripts/sct_crop_image.py
...

Closing because no followup


Review: Landing.jsx and UserPage.jsx

Overview
The focus for this code review will be centered around the Landing and User page.
Please pay attention too:

Javascript issues
React components

Review Branch
review-3
Files to review

Landing
UserPage

Checklists

Architecture
Design
JS
React
Testing

Due date
27, September 1:30 pm
For more information
The review process is documented at: http://courses.ics.hawaii.edu/ics414s21/morea/review/reading-idpm-review.html

Landing.jsx
Line 11: Is there really a need to use a custom logo rather than HIDOEs logo
Line 28: Why do we have an href to localhost URL instead of a Route and Path?
Won't the code have to be changed every time it hits a new server?
User Page.jsx
Seems fine atm as a sample page
Next step is to add functionality so that it can get actual data from settings.development.json
Prioritize doing it after doing the issue: Fill settings.development.json with fake profile data
Maybe later fill it with useless stats like:
-Working since 20XX
-Number of Bills Contributed to
-Amount of Bills Passed
-Expertise Graph etc.

Landing.jsx

<br /> use generally not practical in the long run. Maybe we can use CSS here?

UserPage.jsx

L8-14: Indicates hardcode

Landing.jsx
Line 11: The logo in the landing page is different from the one on the navbar
Line 28: replace hrefs with React routes
User Page.jsx
Lines 8-14: Why are we declaring mock data here, it should go to settings.development.json
Lines 23-27: This should be dynamic based on what user is logged in

Landing.jsx
DE-05:
Line 5 Unecessary comment
Line 28
Use React Button not button
UserPage.jsx
Line 19: Use Card since you are using Card components
Line 7:
TODO: Get collection data from user collection

UserPage.jsx:
Hard code, get data from user collection
Landing.jsx:
Use a Route and Path instead of localhost

Landing.jsx

Remove unnecessary comments (line 5)

a tag comments can be made to link (line 28-29)

use react instead of button (linei 28-29)
UserPage.jsx

use card component

Landing.jsx
Line 11 - Logo is different from navbar
Line 28 - Should use something else other than href to local host
UserPage.jsx
Line 28 - Use card components instead

Landing.jsx:

Line 28: use the React Button instead
UserPage.jsx
Might want to use card component


Add the option to force using ICMP and DNS over normal TCPIP connection

Hello,
for some scenarios, it's preferable to use ICMP or DNS instead of the regular TCPIP connection. please add an option to force using ICMP or DNS over a normal TCPIP connection.

Duplicate of #1481


Emoji Colors > flags > view more emoji > error 400

When clicking on view more emoji under flags in emoji colors it takes you to https://www.google.com/get/noto/help/emoji/flags.html which results in error 404.

@AqeelAT : please file a bug in https://github.com/googlei18n/noto-emoji/issues if if this is still a problem

Verified that it is a problem.
On Dec 7, 2016 6:29 PM, "Marek Jeziorek"<EMAIL_ADDRESS>wrote:

@AqeelAT https://github.com/AqeelAT : please file a bug in
https://github.com/googlei18n/noto-emoji/issues if if this is still a
problem
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/googlei18n/nototools/issues/282#issuecomment-265635971,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJepDLx8I3LgoWRvQCNsWfEGo73NbaBBks5rF2t8gaJpZM4JxKBh
.


Installing partially

name: Installing Partially/Selective

Summary of new feature
It is very efficient that there is a native way to install specific commands of dbatools. A selective installing can help devops to install a few specific command that needed to operate some operation.
Are there any plan for this facility?

Unfortunately not. There is currently no way. What is the issue, memory? Import time?

no memory neither Import time.
I only need specific commands not other, so it is nice that I could install exactly those commands not any other commands.

Thanks for the response - that is not possible with powershell as far as i know. if it's a security issue, however, check out JEA or Just Enough Administration

Heyyy found the answer by accident.
Import-Module -Function and specify just the functions you want. I believe we'll be doing roles later on too, after 1.0.


Config works only from common of Advanced template

Hi,
Thanks for the work you put into this module.
I've successfully setup the module from the common\config\main\components config file of the advanced template and it does work for both frontend and backend. However, when I run the backend application, it shows a new error with the message "Uncaught SyntaxError: Unexpected end of input". When I turn off the module by setting the config switch off in the config, the error goes away.
To resolve this, I decided to split the config and place the config in both backend\config\main\components config file and frontend\config\main\components file. Somehow, it doesn't work at all when setup this way.
Please advise if I am doing something wrong or if this is a known error.
Regards,
Adam

Hi, thank you for report,  i'll take a look.

frontend/config/main.php
'components' => [
'view' => [
'class' => 'smilemd\htmlcompress\View',
'compress' => YII_ENV_DEV ? false : true,
],
],

Hi @smilemd ,
It's exactly the same code whether I put it in common, frontend or backend - it goes into the component section of the main config file (main.php - I am using the advanced template)
There are many files, what exactly do you want me to post?
A

Just html output from the browser.


SITO Version 2

Hi colleagues,
due to incompatible changes, the version for object SITO needs to be updated.
The change consists of adding one new mandatory field (personal_data)
and one new entity (personal_data_fields).
(Backend implementation is not done, so I could not create a new example object yet.)
Best regards,
Michael

Just a remark: There are a lot of commits in this PR. It seems to me you were using your old branch of v1. I guess I would have created a new branch (based on latest main branch) instead of reusing the existing branch of your fork.

Just a remark: There are a lot of commits in this PR. It seems to me you were using your old branch of v1. I guess I would have created a new branch (based on latest main branch) instead of reusing the existing branch of your fork.

Looks like there is a lot of renaming of files happening. So e.g. abc-v1.json becomes abc-v2.json, which deletes basically the abc-v1.json. Instead, you want to add a new abc-v1.json 😃

Hi @schneidermic0 , thanks for your quick reaction.
Regarding my use of the old branch with many commits, does it still make sense to create a new one ? I would just do it the way you prefer it.
For the description field I will need to discuss internally, or maybe you also have a good idea. Our fundamental issue is the following: A Situation Object contains fields "id", "name", "description". Mapping to ADT notation, "id" corresponds to the name of the artifact, whereas "name" is what we want to display in the headers' (and in the properties section's) "description" field. Moreover, the Situation Object's "description" field contains a long description. It is currently located at sub-entity "text".
If, in our AFF, we replace "longdescription" with "description" we fear there might be confusion with the differing values in header's and properties section's description.
I'll take care of uploading both versions. (This was not clear for me from your Wikis (which I like a lot :-) ). Maybe somewhere in the "Changing ABAP File Formats" section of your "Generic Editor FAQ" you could describe expected upload structure, similar to the specification in section "What the pull request should include" of "Add object to github repository".)

Regarding my use of the old branch with many commits, does it still make sense to create a new one ? I would just do it the way you prefer it.

No, keep this PR as it is. Otherwise we lose our conversation. ;)

For the description field I will need to discuss internally, or maybe you also have a good idea.

I am afraid, I have also no good idea, how to handle this. The tricky thing starts IMHO to have multiple descriptions. I am even wondering whether this should be real documentation. If so a dedicated KTD documentation might be a solution.
In any case, it should be at least consistent within the one object type. Now, we have fields called "longdescription" and "description" for (as far as I understand) on the same level of descriptions (in section "texts").

Hi. With the latest push, files referring to version 1 are included now.
Still need to discuss the naming of description fields internally (when colleagues are back from Easter vacation).
One question:
The new field personal_data is defined as required and equipped with a list of enumeration values. When I create a Situation Object now (based on version 2), the new configuration seems to have no effect (the field does not show when I press "STRG-Space"; it is not bold-faced when I write it myself; possible values do not show when I press "STRG-Space"). Not sure if I am missing something in my configuration, or if version 2 needs to be activated somehow from your end ?

One question:
The new field personal_data is defined as required and equipped with a list of enumeration values. When I create a Situation Object now (based on version 2), the new configuration seems to have no effect (the field does not show when I press "STRG-Space"; it is not bold-faced when I write it myself; possible values do not show when I press "STRG-Space"). Not sure if I am missing something in my configuration, or if version 2 needs to be activated somehow from your end ?

I have just dropped you a mail since the question is not related to the definition of the ABAP file formats. ;)

Still need to discuss the naming of description fields internally (when colleagues are back from Easter vacation).

You might want to consider to move this pull request to "draft" as long as you are working on this

For the description field I will need to discuss internally, or maybe you also have a good idea.

I am afraid, I have also no good idea, how to handle this. The tricky thing starts IMHO to have multiple descriptions. I am even wondering whether this should be real documentation. If so a dedicated KTD documentation might be a solution.
In any case, it should be at least consistent within the one object type. Now, we have fields called "longdescription" and "description" for (as far as I understand) on the same level of descriptions (in section "texts").

After internal discussions our plan is now the following:
-rename field "longdescription" to "description"
-remove field "name" from entity situation_object-text (as described earlier, this field contains redundant information)
I would like to hear your opinion especially on the removal of "name" before I start adapting the backend.
Thanks.

-remove field "name" from entity situation_object-text (as described earlier, this field contains redundant information)
I would like to hear your opinion especially on the removal of "name" before I start adapting the backend.

In general, removing fields is incompatible. But, since you anyhow update your format version and if "name" contains redundant information, I would remove it, too.

-rename field "longdescription" to "description"
At least this is consistent with all the other places. I am not sure how this particular field interferes with the field header-description. Is it also redundant?

-remove field "name" from entity situation_object-text (as described earlier, this field contains redundant information)
I would like to hear your opinion especially on the removal of "name" before I start adapting the backend.

In general, removing fields is incompatible. But, since you anyhow update your format version and if "name" contains redundant information, I would remove it, too.

-rename field "longdescription" to "description"
At least this is consistent with all the other places. I am not sure how this particular field interferes with the field header-description. Is it also redundant?

Field "longdescription" contains information that is not redundant. ("header-description" contains exactly the same as "situation_object-text-name".)

OK, I see. Seems to be confusing

The fields containing descriptions are now adapted. A version 2 example is included as well.
From our point of view, version 2 is complete.

I undsterstand you are ready from your side :). I suggest you fix the end of file issue in the example and change this PR to "Ready for review"

Hi colleagues. As requested, EoF issue is resolved. We are ready for review now.

I replaced the version 1 example with the predecessor of the version 2 example. Is this what you had in mind ? (I agree that's better for comparison.)
There is a new error showing up after my push. Not sure if this is something to be fixed on our end ?

There is a new error showing up after my push. Not sure if this is something to be fixed on our end ?

I have updated the readme file. The link to example v2 was missing and v1 was pointing to the wrong/old filename. The latter was the reason for the error reported by the checks

Hi colleagues. It seems that version 2 is complete (from your perspective as well).

I have just waited whether others want to review, too.

Thank you for the once again fast review process and for all your help.
:-)

Happy to hear. Thank you for your contributions.


GearVRf on Android Studio.

How to use GearVRf on Android Studio ?

hey, jason, could you reply with your list of instructions?  thanks.

Just as a note.  The whole Android Studio problem has been complicated by the fact that Oculus requires that you build their mobile sdk with Eclipse.  And that requirement comes from AndroidStudio's poor NDK support.  Supposedly that it doesn't support dependencies on external libs in the NDK side.  The recently announced upcoming AndroidStudio 1.3 will supposedly improve all that.  So, hopefully soon, all the bottlenecks will be removed.

Hi.
I built VrLib and GearVRf with Eclipse and copy built .so files to my Android Studio project.
I created simple-sample example project for Android Studio.
https://github.com/ejeinc/GearVRf_simplesample

I have been recommending to use prebuilt lib for both gvrf and ovr for several reasons. This posting could align with the approach. Thanks for the posting.
However, migrating or merging similar to this one is on hold, considering impacts to the Eclipse users and some accompanying issues.
For prebuilt libraries, people should be able to download from each site respectively. Also there is an instruction page at the wiki for prebuilt gvrf.

@niusounds Thanks for your support. Just took a quick review on your repo and have a small question here:
I see that for native side you are using so files, but for java side, you are still using source for reference. Is there any way to use jar files instead of Java source? Thanks in advance.

By when can we expect migration from eclipse to Android Studio?

The prebuilt library approach for Android Studio for app developers can be found at: https://github.com/Samsung/GearVRf/releases.
However, migration schedule for the framework developers are still under discussion on its priority because of aforementioned reasons.

@chenchao1407 Thanks for advice.
I rebuild project for simple maintenance.
https://github.com/ejeinc/GearVRf_simplesample
now gearvrf module contains only .so and .jar files.

as of Version 3.0 (released last week), we have fully moved to Android Studio


dataset

from the kiti dataset, how is the data to be distributed in the data folder, with kitti_depth and kitti_rgb as its sub-folders?? I want to test he pre-trained model only. Please tell me what data do I need

Hi. Hopefully the data directory structure is clear from the README file (copied and pasted here):
.
├── self-supervised-depth-completion
├── data
|   ├── kitti_depth
|   |   ├── train
|   |   ├── val_selection_cropped
|   └── kitti_rgb
|   |   ├── train
|   |   ├── val_selection_cropped
├── results

Yes, but in the link provided for kitti dataset, there is link for four files + raw data(images). For testing, is the "selection data" file to be used? I want to know how have you separated the whole data into train and val_cropped_selected. Please let me know. Thanks

Hi!, i find your work really interesting. I want to evaluate your architecture with pre-trained weights only. what should be the structure of the data folder in that case.
The thing is kitti_rgb train is so big and i have to transfer all the files via SSH.

what should be the structure of the data folder in that case

The data folder structure is illustrated in the README. You can switch to any data loader, as long as the final loaded data format is the same

@jadhu22
Are you able to run with the pretrained models?  If, yes which parameters you passed in the argument while calling the main.py or did you change something in the code.


Adding cosmos db kvstore driver

Draft because:

Needs better code documentation.
~Missing non-keys authentication.~
No Esti test - that's actually hard given their limited support for emulators.
Some scale tests. kvstore tests are great - but don't test real scale.

Testing writes on Standard_D2s_v3 Azure VM with 4000 (Max Throughput) CosmosDB container:
lakectl abuse random-write --prefix abuse1/ lakefs://repo1/main
Source branch: lakefs://repo1/main
stage object - completed: 961, errors: 0, current rate: 885.59 done/second
stage object - completed: 1746, errors: 0, current rate: 784.84 done/second
stage object - completed: 2520, errors: 0, current rate: 774.42 done/second
stage object - completed: 3290, errors: 0, current rate: 770.06 done/second
stage object - completed: 4071, errors: 0, current rate: 780.74 done/second
stage object - completed: 4394, errors: 0, current rate: 322.96 done/second
stage object - completed: 4955, errors: 0, current rate: 560.83 done/second
stage object - completed: 5857, errors: 0, current rate: 901.99 done/second
stage object - completed: 6605, errors: 0, current rate: 747.86 done/second
stage object - completed: 7390, errors: 0, current rate: 785.34 done/second
stage object - completed: 8152, errors: 0, current rate: 762.15 done/second
stage object - completed: 8503, errors: 0, current rate: 350.62 done/second
stage object - completed: 9161, errors: 0, current rate: 658.73 done/second
stage object - completed: 9885, errors: 0, current rate: 724.20 done/second
stage object - completed: 10794, errors: 0, current rate: 908.27 done/second
stage object - completed: 11656, errors: 0, current rate: 862.27 done/second
stage object - completed: 12370, errors: 0, current rate: 714.01 done/second
stage object - completed: 12580, errors: 0, current rate: 210.00 done/second
stage object - completed: 13373, errors: 0, current rate: 793.30 done/second
stage object - completed: 14121, errors: 0, current rate: 747.69 done/second
stage object - completed: 14976, errors: 0, current rate: 855.48 done/second
stage object - completed: 15839, errors: 0, current rate: 862.70 done/second
stage object - completed: 16519, errors: 0, current rate: 680.23 done/second
stage object - completed: 16889, errors: 0, current rate: 369.85 done/second
stage object - completed: 17469, errors: 0, current rate: 580.24 done/second
stage object - completed: 18387, errors: 0, current rate: 917.44 done/second
stage object - completed: 19186, errors: 0, current rate: 799.50 done/second
stage object - completed: 20039, errors: 0, current rate: 853.17 done/second
stage object - completed: 20484, errors: 0, current rate: 444.57 done/second
stage object - completed: 20983, errors: 0, current rate: 499.37 done/second
stage object - completed: 21685, errors: 0, current rate: 701.78 done/second
stage object - completed: 22440, errors: 0, current rate: 754.66 done/second
stage object - completed: 23259, errors: 0, current rate: 819.20 done/second
stage object - completed: 24078, errors: 0, current rate: 819.30 done/second
stage object - completed: 24880, errors: 0, current rate: 801.90 done/second
stage object - completed: 25592, errors: 0, current rate: 711.72 done/second
stage object - completed: 26109, errors: 0, current rate: 517.35 done/second
stage object - completed: 26447, errors: 0, current rate: 337.80 done/second
stage object - completed: 27482, errors: 0, current rate: 1035.60 done/second
stage object - completed: 28307, errors: 0, current rate: 824.37 done/second
stage object - completed: 28916, errors: 0, current rate: 609.61 done/second
stage object - completed: 29531, errors: 0, current rate: 614.55 done/second
stage object - completed: 30218, errors: 0, current rate: 687.37 done/second
stage object - completed: 31036, errors: 0, current rate: 817.43 done/second
stage object - completed: 31563, errors: 0, current rate: 527.36 done/second
stage object - completed: 31930, errors: 0, current rate: 366.97 done/second
stage object - completed: 32759, errors: 0, current rate: 828.56 done/second
stage object - completed: 33608, errors: 0, current rate: 849.54 done/second
stage object - completed: 34515, errors: 0, current rate: 907.15 done/second
stage object - completed: 35012, errors: 0, current rate: 496.87 done/second
stage object - completed: 35493, errors: 0, current rate: 481.05 done/second
stage object - completed: 36157, errors: 0, current rate: 663.72 done/second
stage object - completed: 37019, errors: 0, current rate: 862.45 done/second
stage object - completed: 37989, errors: 0, current rate: 969.75 done/second
stage object - completed: 38599, errors: 0, current rate: 609.80 done/second
stage object - completed: 39113, errors: 0, current rate: 514.36 done/second
stage object - completed: 39625, errors: 0, current rate: 511.66 done/second
stage object - completed: 40365, errors: 0, current rate: 739.73 done/second
stage object - completed: 41158, errors: 0, current rate: 793.68 done/second
stage object - completed: 42004, errors: 0, current rate: 845.48 done/second
stage object - completed: 42878, errors: 0, current rate: 873.88 done/second
stage object - completed: 43184, errors: 0, current rate: 306.23 done/second
stage object - completed: 43816, errors: 0, current rate: 631.49 done/second
stage object - completed: 44589, errors: 0, current rate: 773.57 done/second
stage object - completed: 45387, errors: 0, current rate: 798.21 done/second
stage object - completed: 46195, errors: 0, current rate: 807.60 done/second
stage object - completed: 46918, errors: 0, current rate: 722.68 done/second
stage object - completed: 47680, errors: 0, current rate: 762.66 done/second
stage object - completed: 48420, errors: 0, current rate: 739.40 done/second
stage object - completed: 49123, errors: 0, current rate: 702.91 done/second
stage object - completed: 49577, errors: 0, current rate: 454.01 done/second
stage object - completed: 50128, errors: 0, current rate: 551.50 done/second
stage object - completed: 50893, errors: 0, current rate: 756.66 done/second
stage object - completed: 51515, errors: 0, current rate: 629.10 done/second
stage object - completed: 52120, errors: 0, current rate: 604.91 done/second
stage object - completed: 53121, errors: 0, current rate: 1000.62 done/second
stage object - completed: 53892, errors: 0, current rate: 770.88 done/second
stage object - completed: 54709, errors: 0, current rate: 816.73 done/second
stage object - completed: 55107, errors: 0, current rate: 398.39 done/second
stage object - completed: 55796, errors: 0, current rate: 688.64 done/second
stage object - completed: 56312, errors: 0, current rate: 515.88 done/second
stage object - completed: 57080, errors: 0, current rate: 768.62 done/second
stage object - completed: 57880, errors: 0, current rate: 799.89 done/second
stage object - completed: 58625, errors: 0, current rate: 744.81 done/second
stage object - completed: 59395, errors: 0, current rate: 770.24 done/second
stage object - completed: 60234, errors: 0, current rate: 839.09 done/second
stage object - completed: 60882, errors: 0, current rate: 647.88 done/second
stage object - completed: 61487, errors: 0, current rate: 604.90 done/second
stage object - completed: 61799, errors: 0, current rate: 311.88 done/second
stage object - completed: 62697, errors: 0, current rate: 897.89 done/second
stage object - completed: 63517, errors: 0, current rate: 820.44 done/second
stage object - completed: 64272, errors: 0, current rate: 754.52 done/second
stage object - completed: 65089, errors: 0, current rate: 817.53 done/second
stage object - completed: 65778, errors: 0, current rate: 688.81 done/second
stage object - completed: 66255, errors: 0, current rate: 477.29 done/second
stage object - completed: 66855, errors: 0, current rate: 599.63 done/second
stage object - completed: 67439, errors: 0, current rate: 584.24 done/second
stage object - completed: 68307, errors: 0, current rate: 868.10 done/second
stage object - completed: 69107, errors: 0, current rate: 799.64 done/second
stage object - completed: 69930, errors: 0, current rate: 822.64 done/second
stage object - completed: 70683, errors: 0, current rate: 753.15 done/second
stage object - completed: 71023, errors: 0, current rate: 340.16 done/second
stage object - completed: 71668, errors: 0, current rate: 645.22 done/second
stage object - completed: 72327, errors: 0, current rate: 659.01 done/second
^Ccompleted: 73078, errors: 0, current rate: 1399.43 done/second

Histogram (ms):
1	0
2	0
5	0
7	0
10	0
15	4
25	6584
50	57435
75	63576
100	64220
250	64314
350	64314
500	64314
750	65574
1000	71022
5000	73078
min	14
max	4132
total	73078

Testing Reads on the same machine with the same CosmosDB container:
lakectl abuse random-read lakefs://repo1/main --from-file files.txt
Source ref: lakefs://repo1/main
read a total of 73166 keys from key file
read - completed: 3040, errors: 0, current rate: 3033.18 done/second
read - completed: 4280, errors: 0, current rate: 1241.06 done/second
read - completed: 5971, errors: 0, current rate: 1691.11 done/second
read - completed: 7504, errors: 0, current rate: 1532.17 done/second
read - completed: 9351, errors: 0, current rate: 1847.71 done/second
read - completed: 11120, errors: 0, current rate: 1769.26 done/second
read - completed: 12669, errors: 0, current rate: 1549.21 done/second
read - completed: 14250, errors: 0, current rate: 1579.44 done/second
read - completed: 15808, errors: 0, current rate: 1558.73 done/second
read - completed: 17499, errors: 0, current rate: 1690.41 done/second
read - completed: 19159, errors: 0, current rate: 1659.96 done/second
read - completed: 20682, errors: 0, current rate: 1523.39 done/second
read - completed: 22390, errors: 0, current rate: 1707.37 done/second
read - completed: 23870, errors: 0, current rate: 1481.28 done/second
read - completed: 25546, errors: 0, current rate: 1674.85 done/second
read - completed: 27094, errors: 0, current rate: 1547.84 done/second
read - completed: 28720, errors: 0, current rate: 1627.49 done/second
read - completed: 30324, errors: 0, current rate: 1603.42 done/second
read - completed: 31847, errors: 0, current rate: 1523.18 done/second
read - completed: 33321, errors: 0, current rate: 1474.20 done/second
read - completed: 34847, errors: 0, current rate: 1525.58 done/second
read - completed: 36625, errors: 0, current rate: 1778.34 done/second
read - completed: 38243, errors: 0, current rate: 1618.23 done/second
read - completed: 39860, errors: 0, current rate: 1616.44 done/second
read - completed: 41464, errors: 0, current rate: 1604.23 done/second
read - completed: 43092, errors: 0, current rate: 1627.61 done/second
read - completed: 44529, errors: 0, current rate: 1437.37 done/second
read - completed: 46162, errors: 0, current rate: 1631.92 done/second
read - completed: 47687, errors: 0, current rate: 1523.64 done/second
read - completed: 49329, errors: 0, current rate: 1644.70 done/second
read - completed: 50165, errors: 0, current rate: 835.88 done/second
read - completed: 52578, errors: 0, current rate: 2413.57 done/second
read - completed: 54037, errors: 0, current rate: 1458.21 done/second
read - completed: 55516, errors: 0, current rate: 1480.36 done/second
read - completed: 57454, errors: 0, current rate: 1937.14 done/second
read - completed: 59103, errors: 0, current rate: 1649.54 done/second
read - completed: 60665, errors: 0, current rate: 1561.71 done/second
read - completed: 62253, errors: 0, current rate: 1587.17 done/second
read - completed: 63854, errors: 0, current rate: 1601.50 done/second
read - completed: 65308, errors: 0, current rate: 1454.62 done/second
read - completed: 66957, errors: 0, current rate: 1648.35 done/second
read - completed: 68560, errors: 0, current rate: 1602.62 done/second
read - completed: 70148, errors: 0, current rate: 1589.39 done/second
read - completed: 71748, errors: 0, current rate: 1600.00 done/second
read - completed: 73383, errors: 0, current rate: 1634.75 done/second
read - completed: 74854, errors: 0, current rate: 1471.17 done/second
read - completed: 76508, errors: 0, current rate: 1653.51 done/second
read - completed: 77986, errors: 0, current rate: 1477.76 done/second
read - completed: 79590, errors: 0, current rate: 1604.68 done/second
read - completed: 80967, errors: 0, current rate: 1377.13 done/second
read - completed: 82716, errors: 0, current rate: 1748.08 done/second
read - completed: 84301, errors: 0, current rate: 1586.00 done/second
read - completed: 86052, errors: 0, current rate: 1751.15 done/second
read - completed: 87665, errors: 0, current rate: 1612.06 done/second
read - completed: 89275, errors: 0, current rate: 1609.73 done/second
read - completed: 90748, errors: 0, current rate: 1473.37 done/second
read - completed: 92430, errors: 0, current rate: 1682.69 done/second
read - completed: 94018, errors: 0, current rate: 1586.64 done/second
read - completed: 95553, errors: 0, current rate: 1536.07 done/second
read - completed: 97272, errors: 0, current rate: 1719.31 done/second
read - completed: 98878, errors: 0, current rate: 1606.01 done/second
read - completed: 100504, errors: 0, current rate: 1626.18 done/second
read - completed: 101994, errors: 0, current rate: 1489.35 done/second
read - completed: 103549, errors: 0, current rate: 1554.18 done/second
read - completed: 105190, errors: 0, current rate: 1642.46 done/second
read - completed: 106825, errors: 0, current rate: 1634.46 done/second
read - completed: 108405, errors: 0, current rate: 1579.67 done/second
read - completed: 109998, errors: 0, current rate: 1593.98 done/second
read - completed: 111600, errors: 0, current rate: 1601.96 done/second
read - completed: 113135, errors: 0, current rate: 1534.26 done/second
read - completed: 114790, errors: 0, current rate: 1655.56 done/second
read - completed: 116383, errors: 0, current rate: 1592.90 done/second
read - completed: 117532, errors: 0, current rate: 1148.47 done/second
read - completed: 119566, errors: 0, current rate: 2035.60 done/second
read - completed: 121105, errors: 0, current rate: 1539.28 done/second
read - completed: 122777, errors: 0, current rate: 1670.02 done/second
read - completed: 124407, errors: 0, current rate: 1635.73 done/second
read - completed: 125833, errors: 0, current rate: 1424.87 done/second
read - completed: 127480, errors: 0, current rate: 1647.76 done/second
read - completed: 129093, errors: 0, current rate: 1613.42 done/second
read - completed: 130677, errors: 0, current rate: 1583.72 done/second
read - completed: 132199, errors: 0, current rate: 1521.02 done/second
read - completed: 133824, errors: 0, current rate: 1625.79 done/second
read - completed: 135437, errors: 0, current rate: 1613.15 done/second
read - completed: 137014, errors: 0, current rate: 1577.64 done/second
read - completed: 138350, errors: 0, current rate: 1334.86 done/second
read - completed: 140164, errors: 0, current rate: 1815.05 done/second
read - completed: 141616, errors: 0, current rate: 1452.45 done/second
read - completed: 143310, errors: 0, current rate: 1692.57 done/second
read - completed: 144894, errors: 0, current rate: 1584.36 done/second
read - completed: 146492, errors: 0, current rate: 1597.99 done/second
read - completed: 148091, errors: 0, current rate: 1599.45 done/second
read - completed: 149689, errors: 0, current rate: 1597.89 done/second
^Ccompleted: 150380, errors: 0, current rate: 1134.45 done/second

Histogram (ms):
1	0
2	0
5	267
7	6679
10	73549
15	116777
25	134097
50	141782
75	142478
100	142561
250	142630
350	142630
500	142630
750	144343
1000	148868
5000	150375
min	5
max	9774
total	150380


NTR: stool examination

Editor preferred term: stool examination
Textual definition: Assay whose target is a stool sample, aimed at assessing various parameters of the stool (such as consistency or microbiological content).
Definition source: EuPath team
Proposed parent: assay
Example of usage:
Submitted by: EuPath team

Postcoordinate in OBI.


Linux custom policy for ADE and HBE recommendation

Created a new folder for Linux ADE and HBE encryption compliance Audit recommendation.
Added ReadMe for instructions to use the policy.
Added policy rule JSON file.

@vapasula @ShaykeAmar - Could you please review this PR to add a new preview policy for encryption compliance recommendation? Thanks in advance!


[Bug]: aspect_rules_py is incompatible with rules_poetry

What happened?
The py_library, py_binary, and py_test rules don’t work with rules_poetry. Packages installed by poetry.parse() can’t be included as dependencies of a py_library, py_binary, or py_test target.
Version

Development (host) and target OS/architectures: macOS on a Apple silicon Mac
Output of bazel --version: bazel 7.1.1
Version of the Aspect rules, or other relevant rules from your WORKSPACE or MODULE.bazel file: aspect_rules_py 0.7.3
Language(s) and/or frameworks involved: Python, Poetry

How to reproduce
Given the following minimal example:
# MODULE.bazel
module(name = "poetry_demo", version = "0.1.0")

bazel_dep(name = "aspect_rules_py", version = "0.7.3")
bazel_dep(name = "rules_python", version = "0.31.0")

# Register a hermetic Python toolchain rather than rely on a locally-installed
# interpreter.
python = use_extension("@rules_python//python/extensions:python.bzl", "python")
python.toolchain(
    configure_coverage_tool = True,
    is_default = True,
    python_version = "3.11",
)
use_repo(python, "python_3_11")

# https://registry.bazel.build/modules/rules_poetry
bazel_dep(name = "rules_poetry", version = "0.3.4")

poetry = use_extension("@rules_poetry//python:extensions.bzl", "poetry")
poetry.parse(
    name = "poetry",
    lock = "//:poetry.lock",
)
use_repo(poetry, "poetry")

# BUILD.bazel
load("@aspect_rules_py//py:defs.bzl", "py_binary")

py_binary(
    name = "main",
    srcs = ["main.py"],
    deps = [
        "@poetry//:absl-py",
    ],
)

# pyproject.toml
[tool.poetry]
name = "poetry-demo"
version = "0.1.0"
authors = []
description = "Bazel Python example using Poetry"
package-mode = false

[tool.poetry.dependencies]
python = "~3.11"
absl-py = "^2.1.0"

# main.py
from absl import app

def main(argv):
    print('Hello, Python and Poetry!')
    return 0

if __name__ == '__main__':
    app.run(main)

The build fails with the following error message:
ERROR: poetry-demo/BUILD.bazel:3:10: in deps attribute of py_binary rule //:main:
'@@rules_poetry~~poetry~poetry//:absl-py' does not have mandatory providers:
'PyInfo' or 'PyVirtualInfo'. Since this rule was created by the macro 'py_binary',
the error might have been caused by the macro implementation

However, aspect_rules_py works with pip.parse, and rules_python works with both pip.parse and poetry.parse. Here is the compatibility table:

Extension Method
rules_python
aspect_rules_py

pip.parse
:white_check_mark:
:white_check_mark:

poetry.parse
:white_check_mark:
:x:

Alternatively, open an issue with rules_poetry to use the provider loaded from rules_python, rather than native as it'll hit up against this issue with other uses of PyInfo.

I suggest to close it here as it relates to https://github.com/bazelbuild/rules_python/issues/1069#issuecomment-1942053014
Will fix in the rules repository