[#453] Document how to make cross-compilation work with buildroot

Notes for Reviewer

Refer to: https://github.com/eclipse-iceoryx/iceoryx2/issues/453.
Write the steps how to make cross-compilation work with buildroot.
Pre-Review Checklist for the PR Author

[x] Add sensible notes for the reviewer
[x] PR title is short, expressive and meaningful
[x] Relevant issues are linked in the References section
[ ] Every source code file has a copyright header with SPDX-License-Identifier: Apache-2.0 OR MIT
[ ] Branch follows the naming format (iox2-123-introduce-posix-ipc-example)
[ ] Commits messages are according to this guideline

[ ] Commit messages have the issue ID ([#123] Add posix ipc example)
[ ] Commit author matches Eclipse Contributor Agreement (and ECA is signed)

[ ] Tests follow the best practice for testing
[ ] Changelog updated in the unreleased section including API breaking changes
[ ] Assign PR to reviewer
[ ] All checks have passed (except task-list-completed)

Checklist for the PR Reviewer

[ ] Commits are properly organized and messages are according to the guideline
[ ] Unit tests have been written for new behavior
[ ] Public API is documented
[ ] PR title describes the changes

Post-review Checklist for the PR Author

[ ] All open points are addressed and tracked via issues

References

Closes #453

@jerry-xie-000 can you also change the commit message to [#435] How to make cross-compilation work with buildroot so that the commit can easily be linked to the respective issue.

I  register an eclipse account and sign the ECA agreement and include my github name, but  eclipsefdn/eca still fail to find my github name.

I register an eclipse account and sign the ECA agreement and include my github name, but  eclipsefdn/eca still fail to find my github name.

@jerry-xie-000 it might take a day to sync everything. If the check still fails after tomorrow, I'll get in contact with the Eclipse Foundation.

Run internal/scripts/check_markdown_linting.sh， seems it's ok now.
···
$ internal/scripts/check_markdown_linting.sh
Running Markdown lint in check mode...
Checking only changed Markdown files...
The following Markdown files will be checked:
FAQ.md
FAQ_ICEORYX_DEVS.md
README.md
doc/bazel/README.md
doc/cross-compile/buildroot.md
doc/how-to-create-an-iceoryx2-release.md
doc/release-notes/iceoryx2-unreleased.md
examples/README.md
examples/c/event_multiplexing/README.md
examples/cxx/event_multiplexing/README.md
examples/rust/event_multiplexing/README.md
\nRunning markdownlint to check for issues...
\nMarkdown lint check completed successfully.
···
Feel free to tell me other issues.

@jerry-xie-000 Looks good, just need to get that ECA check passing.
Have you had a chance to confirm the comment from @elBoberido:

@jerry-xie-000 did the account, you signed the ECA with, use the same e-mail address like you used for the commits?

@jerry-xie-000 Looks good, just need to get that ECA check passing.
Have you had a chance to confirm the comment from @elBoberido:

@jerry-xie-000 did the account, you signed the ECA with, use the same e-mail address like you used for the commits?

Yes, I singed in  ECA and github with the same email address. The GitHub username in ECA setting page which is same like github: jerry-xie-000. But the ECA check still fail.

@jerry-xie-000 the ECA Validation Tool does not find jerry-xie-000. Your Eclipse user name should also not contain dashes but only alpha-numeric characters. Please try to log in and check the Eclipse user name.

@jerry-xie-000 any update on your user name?


memory: don't use 2 images for double buffer

Removed extra screen image
adding profiling calls

Tested on HW lookin good.


<IP_ADDRESS>-unk + 2/1/18 Snapshot upgrade missing staking coins locked from forking and extra steps for resolution

Since the source code for <IP_ADDRESS> was available a good 12 hours before the PPA release and 18ish before the windows .msi I first updated an hp proliant bl-460 gen6 and a hp proloant bl-480 both running Ubuntu 17.10 and compiled v<IP_ADDRESS>-gd3c0eb952 from src/github with without any issues but those nodes hold 0GRC as full nodes.
Soon as the PPA came out I upgrading my 1 racked Dell Power Edge 2950 Gen3 full node provided by my hosting company via the apt stable release from the "gridcoin-gridcoin-stable-trusty.list  " repo also running Ubuntu 17.10 and I had no issues. This is a separate CPID and Linux node as my test grcpool miner , correct syncing of the chain after the snapshot and 100% my balance was correct etc.
Next I moved to 2 bl-460c blades running Windows 7 as Boinc crunchers and past NN extra nodes back from around the 4th of July due to 4th of July forking snafu with no issues but those nodes also have 0 GRC , along with 2 spare laptops.
Finally to my last Windows 7 wallet , a Dell laptop ( at my feet I could get the model ) and after installing the .MSI and extracting the snapshot I literally got sick. I was staking when we forked and when we came back my wallet showed only 6000 of 23,000grc and its literally my savings account and 1.5yr if Gridcoin and barely covers the cost @ 1.6kw/Hr usage although I have a very efficient system running 4 blades 3 x 16 core and 1 8 core @ 1200-1600w total with 15k rpm SAS drives all 4 machines. I panicked and was searching github issues and steemit , I am shunned from the freenode support due to the leadership and said screw it since they already were going to remove me after being accused of spreading lies and being the black cancer of gridcoin from exposing the flaws and security issues in the seed nodes NOTE the latest patch/update was to /src/net.cpp and removes Customminers domination and security loop holes and possible easier exploiting the gridcoin network hosting more than 51% wallet clients being able to cause and control a fork so I was unable to get help for this and I know others have ran into this and found the fix on steemit..
I had to run in the wallet console " repairwallet " , I originally read I needed to sync from 0 and do reorganize but instantly when I did repair wallet it found 26 coins that were spent but never spent and over 17,000 missing GRC... So , if you were staking a block as I assume the way it worked and what happened was since the Neural Network locks onto the coins and makes them not available for spending while held in the staking " kitty pot " until a consensus block is staked and whom ever was staking out of the multiple users whom are trying at the same time others may have a few lost coins and need to run repair wallet after this latest version upgrade along with the new snapshot. This seems to be an issue others are having as I was reading steemit and trending gridcoin along with comments and hoped documentation of the issue along with reminding to backup your wallet .dat and .conf when upgrading.
On another note , my wallet has done daily backups since 2016 and upon version 3.6.#.# not sure 100% but can give date something changed in the code and the backup files are not .dat or .conf are may confuse non tech savvy or non gridcoin wallet savvy ( i know I have dedicated a massive amount of my time and life the past almost 2 years to JUMP at helping the new users in #gridcoin and #gridcoin-help while our trusted @ and +v helpers and trusted community leaders ignore because they have gotten sick of helping people and bored helping new users along with annoyed due to language barriers again thanks dutch for helping show the world Science is not just for English let alone the 2nd language of the world American English as people get passed up and drop off due to the lack of willfulness to help and proper use of  a valuable Gridcoin asset and that is the FOSS network , freenode and #gridcoin and #gridcoin-help and the channel should not just be ran by whom is buddy buddy and should be professional and people should be not just available for help but dedicated to help as much as the current dictatorship. We need a real foundation with checks and balances , we need a new project application team with @gridcoin.us MX record access and mail hosting along with apparently thanks to G_UK's wonderful extensive work and thought process and taking the time to create from his own intellectual ideas apparently a graylist upkeep team... It's time for Gridcoin to grow out of its infancy and revamp and vote whom is trusted and whom is leadership and there needs to be stipulations and requirements and our current team leader and team captian Customminer plays favorites and due to being 3rd world himself does not understand the American society , Gridcoin is international and global but has no tolerance since science along with most of the world is full of Squares and Normies... Marijuana is science , so is cocaine and heroin they belong in the medical field and research is needed , simular to Enigma@home and moo@home just because it may not matter to you as much as bouncing 3.5mhz FM carriers off dust and bodies of mass in space @ 2kw but could save millions of lives and change the current opiate and drug epidemic. I add this as Gridcoin is tied to science and we do not all view science the same way , just like male/females in Gridcoin may not have the same sexual let alone political views but we are a Team and need to act like a team even if we do not get along or like each other or what each other says we need to support and encourage and help each other not slander , ostersize outcast and shun because they expose our team captian and the 2nd leader under rob doing sneaky stuff that could compromise the security of Gridcoin... Thanks , btw yes I a victim of that abuse.

if you staked on a fork and return to main chain repairwallet corrects the balance issue for misspent coins. stakes on forks are not valid and technically never happened.

If you are not satisfied and want to change something, then do it.
I had a hard time following the thought of your post.

Closing.


storage-resize-images extension sometimes doesn't keep the original image orientation.

Describe your configuration

Extension name: storage-resize-images
Extension version: 0.1.7
Configuration values (redact info where appropriate):

Cloud Functions location: asia-northeast1
Cloud Storage bucket for images: omit
Sizes of resized images: 200x200
Deletion of original file: false
Cloud Storage path for resized images (Optional):
Cache-Control header for resized images (Optional):

Describe the problem
Steps to reproduce:

Upload image via Firebase Strorage console.
Wait and reload console until the resized image file has been shown.
Check the resized image.

Expected result
The orientation of resized image is same with the original image.
Actual result
The orientation of resized image is not same.
Original

Resized

Other Notes

I tried to upload some images both jpg and png and tumbler.jpg doesn't has this issue.
However, other jpg image (mainImage.jpg) has this issue.

Resources
Here are images I tested.
images have this issue.

thumbler.png

mainImage.jpg

image doesn't have this issue.

thumbler.jpg

Hi @gki,
My guess is your tumbler image has EXIF data that the browser is using to orient your image properly. The resized image loses the EXIF data, and the browser renders the image incorrectly. This article has a pretty good explanation as to why this is happening.
This PR #306 will rotate the resized images to their proper orientation so that you will not have to rely on the medium using the image's EXIF data to render it properly.

Hi @russellwheatley ,
Thanks for checking and sharing info.
OK, I can wait PR #306.
I hope your update will release sooner! 🤞

This has now been released in v0.1.8 of storage-resize-images.


Add ImagePullSecrets to support private registries

When specifying a baseImage in a Prometheus TPR and in an Alertmanager TPR there is no way to provide  ImagePullSecrets as in kube pod spec, to authenticate with private secure registries.
As a consequence, Operator cannot manage Prometheus and Alertmanagers if their images are not maintained in public registries. This is a limitation, if your environment is not open to the public internet, or if you simply want to maintain your own images in a private registry.
I am suggesting to extend the TPR spec to support optional ImagePullSecrets and if specified, include them in Prometheus and Alertmanager StatefulSets on creation and update.
PR is coming

Thanks for reporting, yes that totally makes sense! Looking forward to the PR! :slightly_smiling_face:

Added it to the next release if we can get it in in time with the other issues of that milestone


Content of a struct gets "destroyed"

Aim
I was just working on an arbitrary task in aztec-nr and my code started to fail in an e2e test because a value in a struct was suddently zero.
Expected Behavior
Struct should not get reset to "zero".
Bug
A content of a struct gets reset to zero. A bug will be obvious when running the reproduction
To Reproduce

git clone https://github.com/AztecProtocol/aztec-packages.git
cd aztec-packages
git fetch origin dereferencing-bug && git checkout dereferencing-bug
cd noir-projects/noir-contracts/contracts/token_with_refunds_contract
nargo execute --package token_with_refunds_contract --silence-warnings

Once you run these commands you should get the following error:

Workaround
None
Workaround Description
No response
Additional Context
No response
Project Impact
Blocker
Blocker Context
It prevents merging of this PR
Nargo Version
nargo version = 0.33.0 noirc version = 0.33.0+26b87408b9360b55a59ed1589a0275dfc5ef9a02 (git version hash: 26b87408b9360b55a59ed1589a0275dfc5ef9a02, is dirty: false)
NoirJS Version
No response
Proving Backend Tooling & Version
No response
Would you like to submit a PR for this Issue?
None
Support Needs
No response

This branch is very out of date with the current master branch of aztec-packages so migrating it across to this repository is then difficult. Can you update this so that it pulls aztec-nr from a fixed commit from https://github.com/AztecProtocol/aztec-nr?

@TomAFrench pointing it to a specific version in aztec-nr repo is not possible because I've modified aztec-nr to not do oracle calls. But I've just merged the branch with master. Is that enough?

When I tested this I just had to replace each std::unsafe::zeroed path with std::mem::zeroed

We had some breaking changes recently with to_be_bytes getting its argument removed. I fixed up the uses there and pushed an update to the dereferencing-bug branch but now with a more recent version of the compiler I'm getting a different error.
Originally I was getting a `` error, although after changing some of the code I'm no longer getting this and can't replicate it. Now I'm getting a panic:
The application panicked (crashed).
Message:  internal error: entered unreachable code: No size for slice v701 = Instruction { instruction: Id(990), position: 0, typ: Reference(Reference(Array([Numeric(NativeField), Numeric(Unsigned { bit_size: 32 }), Numeric(NativeField)], 16))) }
Location: compiler/noirc_evaluator/src/ssa/opt/remove_if_else.rs:158

Seems to occur with or without --show-ssa so it is probably not a result of the new normalize values pass.

@vezenovm @jfecher I have bad news. Rebased my PR on master which has Noir with Maxim's commit and the issue just occurs in a different place. Do you want me to create another reproduction?

@benesjan Ah, yes I was worried about that :sweat_smile:. That'd be great if you could, thank you


Not all plugins have a dedicated CONTRIBUTING.md

Description
I was confused when I saw that kedro-docker has a CONTRIBUTING.md https://github.com/kedro-org/kedro-plugins/blob/main/kedro-docker/CONTRIBUTING.md
but kedro-datasets doesn't.
On the other hand, the top-level CONTRIBUTING.md does not explain how to run the tests, but the kedro-docker specific one does https://github.com/kedro-org/kedro-plugins/blob/main/kedro-docker/CONTRIBUTING.md#ci--cd-and-running-checks-locally
Context
I was trying to tell a contributor (#355) how to run the tests only for one dataset.

Also, maybe instead of make test, we could tell contributors to run pytest? It's not only more explicit, it's actually faster to type...


[All Hosts] (browsers) small fixes

Review changes from other PRs that came in after the PRs were approved/merged.

Docs Build status updates of commit c4bf8c0:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/concepts/browsers-used-by-office-web-add-ins.md
:white_check_mark:Succeeded
View

docs/testing/sideload-office-add-ins-for-testing.md
:white_check_mark:Succeeded
View

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

Docs Build status updates of commit 897d46a:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/concepts/browsers-used-by-office-web-add-ins.md
:white_check_mark:Succeeded
View

docs/testing/sideload-office-add-ins-for-testing.md
:white_check_mark:Succeeded
View

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

Docs Build status updates of commit bf7d6a6:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/concepts/browsers-used-by-office-web-add-ins.md
:white_check_mark:Succeeded
View

docs/testing/sideload-office-add-ins-for-testing.md
:white_check_mark:Succeeded
View

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


Testbentch Contentedit fields overflow

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the bug
In testbench, users can customize the Title as well as Group names accordingly.

lack of a few styling the text is overflowing.
Currently the text and borders are very close to each other
extend to this even though the group is also an editable field as it doesn't have styling to let the user know they can also customize this field.

Steps To Reproduce
simulator->testbentch->try to edit the title& group
Expected Behavior
These changes will help to rectify the above-stated problem,

Resist the overflow
field borders styling
style the group field the same as the title.

Screencast from 01-10-2024 03:17:04 PM.webm
Screenshots
No response
Device Information [optional]
- OS:
- Browser:
- version:

Additional context
No response
Are you working on this issue?
Yes

This input box get's bigger and bigger according to the input.

Yep, it was Firefox issue in windows as well as ubuntu


Added the documentation related to AD app settings.

Updated the documentation to explain the Azure Active Directory application settings that should be set for the AD authentication to work properly when the app is run locally
Besides, fixed an issue with a parameter being passed for change plan. This got introduced due to a recent find / replace exercise to fix the name of a variable before the base version was added to the repo.

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


chore: upgrade sn-api version

This change is

Codecov Report
Attention: Patch coverage is 77.77778% with 4 lines in your changes missing coverage. Please review.

Project coverage is 74.69%. Comparing base (8090c8b) to head (472f2ec).

Files
Patch %
Lines

crates/gateway/src/utils.rs
50.00%
4 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #241      +/-   ##
==========================================
- Coverage   74.78%   74.69%   -0.09%
==========================================
  Files          23       23
  Lines         916      913       -3
  Branches      916      913       -3
==========================================
- Hits          685      682       -3
  Misses        187      187
  Partials       44       44

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


add basic http tests

This includes tests for a successful load event and an error event. It
currently provides every single parameter, including optional ones.
However, it does test that the request/response headers and body are
sent properly using a mock XHR implementation.

Codecov Report

Merging #258 into master will increase coverage by 2.96%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #258      +/-   ##
==========================================
+ Coverage   90.38%   93.34%   +2.96%
==========================================
  Files          26       26
  Lines         842      842
  Branches      177      177
==========================================
+ Hits          761      786      +25
+ Misses         70       49      -21
+ Partials       11        7       -4

Impacted Files
Coverage Δ

packages/moon/src/http/driver.js
100% <0%> (+86.2%)
:arrow_up:

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 1797a44...b13176a. Read the comment docs.


Update tests in checking IR outputs with torch outputs

This PR sets a more reasonable value (0.1%) for relative tolerance, when checking if OpenVINO IR outputs equal to torch model outputs.
However, OpenVINO IR is facing output issue with a customized quantization config.  See https://github.com/openvinotoolkit/nncf/issues/1498 .
This may sometimes cause failed tests. For now we mark to skip tests with custom quantization config.  Once we upgrade to use a higher OpenVINO release, we will delete the skipping.

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.

run test


[Enhancement] Websocket API should allow sending pongs (and possibly pings)

In order to keep a websocket session alive, the usual method is to have the server periodically send "pong" frames (done in beast via async_pong). I suggest adding a send_pong method to websocket::connection that would facilitate this behaviour.
imo doing it automatically stretches the "lightweight wrapper" definition a bit, but I'm not particularly opposed to it. nvm theres literally an option for it built into beast

How does the pong sent by the server show up on the client? Is this transparent to the user? i.e. would this trigger the on-read handler on the client?

I think its implementation defined, but for beast iirc its transparent. There is this setting which I found for beast, which we should probably expose (automatically sends pings on timeout).
I'm a little out of my depth here, gonna be honest :p

imo doing it automatically stretches the "lightweight wrapper" definition a bit, but I'm not particularly opposed to it.

If this is completely transparent to the user (i.e. the pongs don't show up on the on-read handler (or if we can just filter them manually before the user's on-read handler gets invoked) I'd say that this is a very necessary addition to malloy.
The main focus lies on usability/practicality. In many cases this results in keeping it lightweight but something like this I deem as frequently-enough-used to support it (if not even enabling it by default).
I would even go as far as adding state change callbacks. One of my application talking over websocket will need the ability to report to the rest of the application (and the user) if the connection tot he server (also using malloy) has been lost. I'd argue that this is a rather common practice/need/requirement.

I'm a little out of my depth here, gonna be honest :p

Currently I'd also not appoint myself as qualified enough to make this decision. It might be worth asking over at beast.

I would even go as far as adding state change callbacks

Like the JS websockets? With onclose, onerror? I've been thinking about this, would ideally expose some sort of "event" type that could have multiple handlers registered to it imo.

Yeah, exactly.

Well after implementing the ability to set the keep_alive_ping setting manually, and finding that still didn't fix the issue, then discovering that timeout::suggested(server) sets that to true anyway, I went down a bit a of a rabbit hole and found this in the websocket timeout docs:

The timeouts on the websocket stream are incompatible with the timeouts used in the tcp_stream. When constructing a websocket stream from a tcp stream that has timeouts enabled, the timeout should be disabled first before constructing the websocket stream, as shown.

(docs). I then found this:
https://github.com/Tectu/malloy/blob/bf84707456ccedc06b735bcccbe8a6b8fdac2915/lib/malloy/server/http/connection.hpp#L190
^^ That sets a 30 second timeout on the socket which is never changed and which I'm guessing is untouched by beast. Interestingly I kept getting websocket timeouts after 30 seconds...
tl;dr expires_never() needs to be called on the socket before we handoff to the websocket connection. I'll make a PR shortly :p.
This issue may still be valid, but I don't have a use-case for it and I can't think of one off the top of my head. Also I'm not sure if we should add the option to disable or enable automatic pinging? Note that it has no effect if a timeout is not set (as is default for the client), and is enabled already for the server by default.

Well, that was an interesting rabbit hole for sure 🥇
In the new configuration, what happens if there's an active connection between the client & the server and then the client suddenly looses network. This change would mean that the TCP layer never times-out and therefore the connection on the server would stay alive indefinitely (until the process is killed) - am I wrong here?
My gut feeling tells me that the better way of doing this is to keep an expiry timeout on the TCP socket/layer and have the automatic ping-pong system setup so the timeout doesn't get triggered as long as both the client and the server can talk to each other.

This change would mean that the TCP layer never times-out and therefore the connection on the server would stay alive indefinitely (until the process is killed) - am I wrong here?

The websocket layer added by beast has its own timeout system. The suggested settings for the server put that at 300 seconds (5m) with automatic ping pong at half of that if there is no activity, although the docs are a bit vague on whether it's half or two timeouts with the first sending the ping.


HDDS-878. Do the disk failure check before ContainerSet initialization.

What changes were proposed in this pull request?
Remove the old todo mentioned in HDDS-878. The feature it describes is already implemented.
What is the link to the Apache JIRA
HDDS-878
How was this patch tested?

Change in this PR is comments only, no testing required.
An existing test verifies the functionality described in the jira is present: TestDatanodeHddsVolumeFailureToleration#testDNCorrectlyHandlesVolumeFailureOnStartup

Thanks for reviewing @umamaheswararao


refactor: set enforced options in Lua

What does this solve? Don't we need to set the forced options after the user's init has finished?

More timely
The VimEnter event is executed after loading the vimrc.
The purpose of "-S" doesn't belong here originally.
I don't see any distinction between this and other modules; there's no need to treat it as a special case within the main_controller.

There is a special distinction.
The order should be:

lua modules are loaded (and default options set)
user config is loaded (which can require("vscode")), which can overwrite default options
force options are loaded, which overwrite user options

Additionally, the autocommand is just for buffer local options, not global options.

👍

Currently: default -> force -> user -> force

Did a simple test, should be ok.


smooth keyword in bootstrap should be configurable and have different default

Currently, it is just true or false. No information is given in the docs how broad the Gaussian noise is, I see in the code that you use a sigma = 1/sqrt(N), how is this motivated? It seems ad hoc. I think the noise sigma should be proportional to the sample std. deviation, otherwise it is inconsistent. If the original distribution is very narrow, then also the noise must be narrow and vice versa.
I think there is no one answer how the smoothing should be done. In that case, the sigma should be configurable. I am not a fan of smoothing, btw, it goes against the bootstrap principles in my view.
To summarize, I think the new default noise width should be (std.deviation of original sample) / sqrt(N - 1) (aka error on the mean), and users should be allowed to pass in any float which is then used as the noise width.

I agree it is somewhat ad hoc; the original idea was to apply more smoothing the smaller the sample (as smaller samples are more "coarse"). I guess it's a question of how opinionated we want to be, but I also wouldn't be opposed to removing this option, as it either has little effect (small variance) or significantly changes the statistical properties of the sample (large variance), which partially invalidates results.
If we did keep it then yes it probably should somehow be proportional to the underlying variance.

I don't know how many users you already have, whether taking interface away at this point is still ok without hurting too many. The soft option is to deprecate things (I do that excessively in iminuit right now to clean up the interface design left by previous maintainers), keep the keyword in the code, but remove them from the documentation, and raise warnings when people are still using it.
While I personally don't see the point of smoothing, there are research papers about that, so maybe it makes sense to keep it.

As far as I can tell there aren't a ton of users (I see about 13K downloads over the past 1.5 years or so on pepy.tech) and I doubt it's used "in production" much so I'm actually not too worried about breaking changes.
In regard to smoothing, you could argue that it's somewhat redundant given that parametric bootstrapping is already possible (instead of adding Gaussian noise you could instead just use the Gaussian parametric bootstrap and then at least preserve the scale of the distribution). I'm slightly biased in favor of removing unnecessary details / features, but I suppose I don't feel too strongly either way.

In regard to smoothing, you could argue that it's somewhat redundant given that parametric bootstrapping is already possible (instead of adding Gaussian noise you could instead just use the Gaussian parametric bootstrap and then at least preserve the scale of the distribution).

I agree. Smoothing changes the empirical CDF of the data. Doing a parametric bootstrap is better if one really has so few that data points that smoothing seems necessary. When the amount of data is large, no smoothing is needed anyway (at least I am not aware of a counter-example).

I'm slightly biased in favor of removing unnecessary details / features, but I suppose I don't feel too strongly either way.

Then let's do that and have a clean starting point.


Update ActiveMQ client dependency to 5.16.5

This is the final cleanup release of ActiveMQ 5.16.x, and thus the final backward-compatible update to the ActiveMQ client used in this package; any further updates will require a JRE 11+ runtime environment, thus breaking compatibility with GeoEvent Server 10.4.1 - 10.8.1

@hanoch please review and consider merging


VMS fix of test/recipes/80-test_ssl_new.t

On VMS, file names with more than one period get all but the last get
escaped with a ^, so 21-key-update.conf.in becomes 21-key-update^.conf.in
That means that %conf_dependent_tests and %skip become useless unless
we massage the file names that are used as indexes.

Checklist

[x] tests are added or updated

Description of change

This too is meant for both master and 1.1.0.  Still fine?

meanwhile, merged into master.  d89f66412ba5168e7d6fd9dd88619d927d716f55

1.1.0?

Yes.

Good.  Merged into 1.1.0 as f4cdd19a6a8a0845c08c8101538347f2d5a0d96c


SOLR-15992: Globally forbid and exclude known bad dependencies

https://issues.apache.org/jira/browse/SOLR-15992

I'm planning to merge PR #612 first so only the one commit needs to be reviewed.

I did take a look but it's not really helping me understand why it works or whether it's correct. :( Sorry. I can't even remember where we had exclusions on that custom configuration. If it does work, I'd commit it in.

No worries Dawid - Appreciate the help and pointers!
@janhoy / @dsmiley any other comments/concerns/critiques/criticisms?

Merged in 4a0854b64a82e29a822b262eab780ff849095392


js-mollie-alert "Locale is invalid"

Expected behavior
Test paiement for my prestashop site
Actual behavior
I use the 4242 credit card. I configure molly with test API key, and Profile ID only.
I got a message in li.js-mollie-alert :
"Locale is invalid"
Steps to reproduce the behavior
add a item to my basket and try to pay with a test credit cart
Environment

PrestaShop version: <IP_ADDRESS>
Mollie module version: 4.0.9
PHP version: 7.3.20

Hey @greg-fr thanks, we have backloged this.
Will update you about the fix.
Best Regards.

Hey @greg-fr , we provide you an example about the German language.
Probably in BO there are the wrong language codes that are set wrong.
If client is using the German language on his site, he should check if his Language code in BO is correct it should be de-de for the German language.
Please try, let us know the feedback.
And in case, we can close the issue as well after that.
Best Regards.

Well done !
My site language use 3 languages : fr/de/it.
and when i import the language pack for switzerland, i juste have fr code instead of fr-fr.
It's fixed now. Thank you!


Added support for uint + fixed encoder for [][]byte

this is needed to enable scale codec for poet proofs - https://github.com/spacemeshos/go-spacemesh/issues/3271

@dshulyak yeah, and that would need too many changes in 4 repos. Instead it's much easier to add uint support in codec which converts it from/to uint64 under the hood.

it can't be too many changes. just cast uint to uint64 where objects are created

@dshulyak closing this one but fix for [][]byte encoder is still needed - https://github.com/spacemeshos/go-scale/pull/9 - when you have a mo


chore: bump client3:core, client3:zio from 3.9.8 to 3.10.0

About this PR
📦 Updates

com.softwaremill.sttp.client3:core
com.softwaremill.sttp.client3:zio

from 3.9.8 to 3.10.0
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
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 me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.softwaremill.sttp.client3" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "com.softwaremill.sttp.client3" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, version-scheme:early-semver, commit-count:1

Superseded by #304.


[Bug] start be error. 非法指令

Search before asking

[X] I had searched in the issues and found no similar issues.

Version
0.15
What's Wrong?
start_be.sh: 行 102: 23022 非法指令            (吐核)$LIMIT ${DORIS_HOME}/lib/palo_be "$@" >> $LOG_DIR/be.out 2>&1 < /dev/null
What You Expected?
sh start_be.sh
How to Reproduce?
No response
Anything Else?
No response
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

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

[root@doris1 ~]# cat /proc/cpuinfo
processor       : 0
vendor_id       : GenuineIntel
cpu family      : 6
model           : 13
model name      : QEMU Virtual CPU version 2.5+
stepping        : 3
microcode       : 0x1
cpu MHz         : 2099.998
cache size      : 16384 KB
physical id     : 0
siblings        : 8
core id         : 0
cpu cores       : 8
apicid          : 0
initial apicid  : 0
fpu             : yes
fpu_exception   : yes
cpuid level     : 13
wp              : yes

could you modify the start_be.sh to add echo $limit to see the output

Maybe you cpu no support AVX2 instruction，cat /proc/cpuinfo show the instruction support

Maybe you cpu no support AVX2 instruction，cat /proc/cpuinfo show the instruction support

cat /proc/cpuinfo | grep AVX2

Me too. How can I fix this bug?

Me too. How can I fix this bug?

USE_AVX2=0 ./build.sh --be

I use this command recompiled BE,but the bug still exist.. Does anyone else meet this bug too?

I use this command recompiled BE,but the bug still exist.. Does anyone else meet this bug too?

我是使用自己的操作系统（CentOS7.3）编译的，可以正常运行。官网的容器镜像好像是CentOS7.9 编译出来的包不能在CentOS7.3上运行。你可以试试使用你们自己的操作系统版本编译


Update sample operator CR to include all possible config knobs for user reference

This should also update the CSV as part of the bundle generation so that the ALM examples annotation includes a complete example for users to reference:
https://github.com/gatekeeper/gatekeeper-operator/blob/66712a15ddc73df06afd1c8f7c6163e2debe4143/bundle/manifests/gatekeeper-operator.clusterserviceversion.yaml#L5-L28

I'd use the minimum required as the main example to get non-experienced users a simple way to get started.
As we can provide multiple examples, then we can append some other examples with a specific purpose so that UIs supporting it can allow you to pick one or use the default.
Maybe as an all-in-one example we can use this https://github.com/gatekeeper/gatekeeper-operator/blob/master/config/samples/gatekeeper_with_all_values.yaml

Yes, I agree a simple example makes sense. At the same time my concern is that the existing sample is used for documentation purposes within the CSV that is then placed onto operatorhub.io. I've seen some operators use a simple example like etcd and others like istio use a more extensive example that may show all the config options possible. These examples are obtained from the alm-examples field of the CSV as shown in the snippet above.


Python Prepared Statement Parameters

Currently, we treat python parameters to be as wide as they can reasonably get. All integer types are treated as INT64, all float types are treated as DOUBLE. However, consider the following script
import kuzu
db = kuzu.Database("tmpdatabase")
conn = kuzu.Connection(db)
conn.execute("CREATE NODE TABLE t1(id SERIAL, number INT32, PRIMARY KEY(id))")
conn.execute("CREATE (:t1 {number: $1})", {"1": 2})

You would expect for the node to be created; but it isn't. We get the following error
RuntimeError: Parameter 1 has data type INT64 but expects INT32

This is because the way we resolve the type of python parameters right now assigns all integers to INT64 (and all floats to DOUBLE)
What if we implemented a technique that found the narrowest type of our parameters? You can't always make a 64 bit integer into a 32 bit integer, but you can always make a smaller width integer into a larger width integer. I tried it out in the #3090 PR, but it turns out that it doesn't work either.
RuntimeError: Parameter 1 has data type INT8 but expects INT32

The way we expect the type of prepared statement parameters doesn't allow for implicit casting like this.
If we ship the code that does this in #3090 in a release, we must ship corresponding changes that additionally allow for the implicit casting of parameters. This is not ideal, since then it would take a really long time to resolve #3054.
My proposal is that we limit the scope of #3090 to just LIST and MAP parameters, and resolve the above problems in a future set of PRs.

Fixed in #3374


Repeating Prescription From Old Medical Record

It would be great if we can pre fill drugs from previous medical record, when issuing new prescription. Like we can repeat medicines with a click. By the way great work keep it up.

Hi @doctorbhatti,
Apologies for the delayed response.
Thank you for your suggestion! We'll definitely consider it for a future update.
Could you please confirm if you're currently using CHR247 in a real-world scenario? This information would be helpful for us.

I was planning to use it in my clinic, but then delayed the plan due to this feature. Then I tried to add this feature using localStorage and some other approaches but didn't like them. Now I'm working on a python script using beautiful soup library.

@doctorbhatti We would like to connect with you and gain some insights. Can we schedule a quick call sometime?
Please send us an email at<EMAIL_ADDRESS>We're looking forward to connecting with you.

Check your email, kindly.


MySQL broken search

Describe the Bug
DB sided search (websites, users, ...) is broken on my side with current version (2.10.1) and Prisma.
An error message is shown front-end, and Prisma throws an error (log is pasted below for a website search).
It looks like I shouldn't be the only one affected, and most likely a bug in Prisma.
Database
MySQL
Relevant log output
PrismaClientValidationError:
Invalid `prisma.website.findMany()` invocation:

{
  where: {
    userId: "41e2b680-648e-4b09-bcd7-3e2b10c06264",
    AND: {
      OR: [
        {
          name: {
            contains: "a",
            mode: "default"
          }
        },
        {
          domain: {
            contains: "a",
            mode: "default"
          }
        }
      ]
    },
    deletedAt: null
  },
  include: {
    user: {
      select: {
        username: true,
        id: true
      }
    }
  },
  take: 10,
  skip: 0,
  orderBy: [
    {
      name: "asc"
    }
  ]
}

Unknown argument `mode`. Did you mean `lte`?

Which Umami version are you using? (if relevant)
No response
Which browser are you using? (if relevant)
No response
How are you deploying your application? (if relevant)
No response

Ok, it's not a bug in Prisma.
mode property was only included with PostgreSQL in previous Umami versions.
It is now also included with a default value with MySQL (see getQueryMode and getSearchParameters in lib/prisma.ts)
but it's not available in generated Prisma Client API when mode isn't needed.
Docs:
https://www.prisma.io/docs/orm/prisma-client/queries/filtering-and-sorting#case-insensitive-filtering
https://www.prisma.io/docs/orm/prisma-client/queries/case-sensitivity

Good catch. will approve thanks.


Fix usage of eos_setOption

eos_SetOption can only set a single option in a call.
EOS_INSERT_DATA is now set to 4 as was the intention in the original code.

Thanks for the fix!


camerad: refactor linkDevices for improved error handling and readability

This PR improves the linkDevices function by:

Adding Detailed Error Checks and Logging: Enhanced error handling and logging for device linking and activation failures.
Struct Assignment: Used brace initialization for cleaner code.
Logging: Improved log messages for clearer insights into device linking and activation steps.
Replaced Assert with Return on Failure: Immediately return on any failure instead of continuing execution, and only use an assert at the end of the function.

These changes make the function more robust, maintainable, and easier to debug.

trigger-jenkins

trigger-jenkins


Mouse over doesn't make transparent.

Clicking on the window (not rolling over) gives you transparency... and then it becomes opaque after 1 second. I have 10.10.5 installed... might be an issue related to that.

I'm also on 10.10.5, but can't reproduce this issue. Do you have any other usage information that could factor into why this is happening?


Update Hashable conformance

This became a warning with the Swift 5 compiler (even in Swift 4.2 mode), but isn't compatible with some older Swift versions supported by PathKit. I guess a decision needs to be made on whether we'd prefer support older versions and have warnings, or drop them.


Re-add "create" verb to bundle unpacker role

Signed-off-by: perdasilva<EMAIL_ADDRESS>
Description of the change:
Re-adds "create" verb to bundle unpacker job role removed in #2805 - still 100% sure it's not needed, but because of FF, let's keep changes to a minimum...
Motivation for the change:
Architectural changes:

Testing remarks:

Reviewer Checklist

[ ] Implementation matches the proposed design, or proposal is updated to match implementation
[ ] Sufficient unit test coverage
[ ] Sufficient end-to-end test coverage
[ ] Bug fixes are accompanied by regression test(s)
[ ] e2e tests and flake fixes are accompanied evidence of flake testing, e.g. executing the test 100(0) times
[ ] tech debt/todo is accompanied by issue link(s) in comments in the surrounding code
[ ] Tests are comprehensible, e.g. Ginkgo DSL is being used appropriately
[ ] Docs updated or added to /doc
[ ] Commit messages sensible and descriptive
[ ] Tests marked as [FLAKE] are truly flaky and have an issue
[ ] Code is properly formatted

/hold testing


Bug Report (Submitted by 1662)

Description
The "actions" Dropbox does absolutely nothing.
Reproduction Steps
Went to the admin page > filtered by hof > clicked actions on the brennan kennedy jr card and it does nothing.
Operating System
Android
Browser
Firefox
Device
Mobile

doesnt look to be an issue on our end?


Line end marker \ in lua string is replaced by \ and \

if a lua file uses \ at the end of a string to mark a line break, luadata generates an \ and a \ on every save:
description = "This is a multiline test.\
With a 2nd line in here."

After save it becomes
description = "This is a multiline test.\\
\
With a 2nd line in here."

This happens on every save, messing up the whole file in a bit.

Ok, was an encoding issue. For whatever reason, I had to write the file binary, then all is good.


cowboy_static: problems trying to return content-type with charset utf-8

I have been trying to get cowboy_static to return a file with the following response header
content-type: text/html; charset=utf-8

I tried using the mimetypes parameter as described in the docs:
  {"/someroute", cowboy_static,
    {priv_file, somemodule, "file.html",
      [{mimetypes, {<<"text">>, <<"html">>, [{<<"charset">>, <<"utf-8">>}]}}]
    }
  }

This makes cowboy return 406 status code when browser requests the file with this request header:
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8

If I manipulate the header before sending the request to be:
Accept: text/html;charset=utf-8,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8

Then I get the desired response.
If on the other hand I change cowboy_static.erl to override the cowboy_rest:charsets_provided():
% in cowboy_static.erl
charsets_provided(Req, State) ->
    {[<<"utf-8">>], Req, State).

Then the standard browser accept header works and I get the desired content-type back.
I can easily workaround this by just serving the file from my own rest handler, so it is not a big issue, and I just wanted to understand if I am doing something wrong or if there is another way of doing this that I have not spotted.

Sounds related to #1245 can you try the PR that was open for it?

I created a small unit test to capture this issue, and it fails for both master the code in #1245

Yes I'm thinking it needs an option.
Yeah I would say that's a good idea and we probably should do this before 3.0, even if it's a breaking change I doubt anyone has non-utf-8 files.

I intend to look into this set of issues next week after releasing 2.3.

I guess the safe option could be to do

in 2.x
in 3.x

I have done both things from the above comment. Pushing in a few minutes. Thanks!


page not found 404-BUG

hi @VGandhi27 . i see that when i click on your live project url . it shows "page not found'' 404 error message. website is not loading i would love to work on this issue.Please assign this to me. I am a gssoc contributor.Thank you.

hello @VGandhi27 the official link which is provided in the repo is broken , i would like to work on this issue

Hello @VGandhi27   the link is broken it has to be redeployed , i would like to work on this issue , please assign this to me


Cat-Dog Image Classification

Project Proposal: Cat and Dog Image Classification
Description:
This project aims to develop a machine learning model that can classify images of cats and dogs. It will involve collecting a dataset, preprocessing the images, building and training a neural network, and evaluating its performance.
Objectives:

Collect and preprocess a dataset of cat and dog images.
Build a neural network using a framework like TensorFlow and Keras.
Train the model and optimize its performance.
Evaluate the model on a test set and report the results.
Create documentation and a tutorial for future contributors.

Skills Required:

Python programming
Machine learning and deep learning
Experience with TensorFlow and Keras.
Data preprocessing

Tasks:

[ ] Collect and preprocess the dataset.
[ ] Develop the model architecture.
[ ] Train and evaluate the model.
[ ] Optimize model performance.
[ ] Document the process and create a tutorial.

Expected Outcomes:

A trained model that can accurately classify images of cats and dogs.
Comprehensive documentation and a tutorial for new contributors.

@Niketkumardheeryan ,
I request You to assign me this issue .  I am ready to contribute as a GSSoC24 Contributor.
Thank You

@Niketkumardheeryan ,
I didn't make any pull request till ,this is my first time here  and sorry but I can't understand what you want to say .
Can you please elaborate a little bit more ??

I am interested in this issue. Please assign me this


added Can_wrap_around_more_than_one_day to Clock

Hi.
I have added a test in the Clock problem.
You can also see the test in my submitted solution
Thank you
P.S. This is the first time I am doing something on GitHub, so I hope I am doing this properly.

Hi,
This looks good to me! Thanks a lot.
Normally, the tests of an exercise should be based on its canonical-data, which also has a similar test. For now, I think it's great to add this test. Eventually, we should be creating a test data generator (see #195), which automatically create tests based on the exercise's canonical data. Unfortunately, the clock exercise is a bit hard to do at the moment, due to the slightly weird test group descriptions, so we'll revisit that later.
Once again, thanks! And for a first effort on GitHub, this is perfect :) 🎉

Thank you very much


Upgrade Feast transformer for v0.12.1

Made the following changes for Feast transformer to support the
latest Feast v0.12.1

Change the python client API to rest API
Use the new Feast feature server
Use python 3.8
Update sample outputs in doc

What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:

Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.

Release note:

hi @chinhuang007! thanks for the PR, please kindly help move this PR to https://github.com/kserve/kserve

/ok-to-test

@yuzisun Thanks for the review and comments! I will move this PR to kserve repo shortly.

/lgtm
/approve


其他图片无法识别的问题

Thank you very much for your outstanding contribution. I have a question. What are the requirements of this network for inputting pictures? Why do I input other pictures and report errors? The pictures in your test set will not report errors. The errors are as follows: tile cannot extend outside image. If you can reply, I will be very grateful!

同样的问题，您解决了嘛？

应该是PIL剪裁图像，位置不对，我也遇到了同样的问题，目前还没有解决

@CaptainEven 作者您好，我在测试自己的图片时也出现了同样的问题。可以解答一下吗


matching Pytorch availability (not sure if you are ok with  3.7)

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

Codecov Report

Merging #1354 into dev will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              dev    #1354   +/-   ##
=======================================
  Coverage   95.73%   95.73%
=======================================
  Files         123      123
  Lines        6459     6459
=======================================
  Hits         6183     6183
  Misses        276      276

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 f220633...26df572. Read the comment docs.

hi, the CLA agreement doesn't fit my privacy, but I don't think you need it for what is sort of comment lines.


Don't report code coverage when not in a pull request context

Fixes #9, by only attempting to report the code coverage when a PR ID is available in the action context.
Doesn't currently work, probably shouldn't have raised PR yet. Will update if I get somewhere!

@mattallty I'm having trouble getting the action to execute as expected when using the action from my fork of the repo. Am I missing a build step or some other change I should be committing?

Thanks @jimmed !


Is the django-ibmi driver viable ?

Since this Django driver hasn't received any development for 2 years is it even viable for IBM i DB access with Django ?
I have a customer asking about what to use to connect to IBM i DB2 with Django (via Windows) and I'm actually not sure what to tell them to do.  I'm assuming the same issue is looming for Linux or Native IBMi PASE.
My current answer is use Flask or anything other than Django that can directly use pyodbc because it doesn't appear IBM i is properly supported with Django.
This project appears to work from cursory testing and looks somewhat promising:
https://github.com/soundstripe/django-pyodbc-iseries
I would appreciate thoughts on best connectivity options for Django and IBM i so I know how to advise customers who are asking about using the Django framework with IBM i.
Thanks

Since this Django driver hasn't received any development for 2 years is it even viable for IBM i DB access with Django ?
I have a customer asking about what to use to connect to IBM i DB2 with Django (via Windows) and I'm actually not sure what to tell them to do.  I'm assuming the same issue is looming for Linux or Native IBMi PASE.
My current answer is use Flask or anything other than Django that can directly use pyodbc because it doesn't appear IBM i is properly supported with Django.
This project appears to work from cursory testing and looks somewhat promising:
https://github.com/soundstripe/django-pyodbc-iseries
I would appreciate thoughts on best connectivity options for Django and IBM i so I know how to advise customers who are asking about using the Django framework with IBM i.
Thanks

+1

I have some changes in the fix branch here: https://github.com/IBM/django-ibmi/tree/fix I had to put this work down due to other priorities and our team's current Python focus is on https://github.com/IBM/sqlalchemy-ibmi.
We have not assessed any other alternatives, though https://github.com/ibmdb/python-ibmdbsa may work provided you have a Db2 Connect license.

Thank you for your response @kadler !


Handle repo lacking initial commit

Porcelain output when no commits registered on master. Nuissance. Update parsing to handle.
 The initial git repo status line is different text too.