Overhaul and fix-up inertial scrolling

A rebase of https://github.com/godotengine/godot/pull/47931.  I tested that it builds locally and that it runs the editor and a test scene, and scroll works in the ScrollContainer in both of them.
Closes https://github.com/godotengine/godot-proposals/issues/5386.
Fixes https://github.com/godotengine/godot/issues/45402.
Refer to the original PR for the list of features and changes.

I've decided to make a new PR to preserve the original in case I messed up, and also because the original used the master branch of the author's repository, which is problematic in practice. Feel free to push to my branch if you need to fix something up.
We need to finish this PR this week, so we meet the plans for RC1. The original PR is very much requested and appreciated by a lot of people, so we should include this in 4.0.
cc @threethan

I've tested this pull request on desktop and Android and can confirm it works on both.
Testing project: test_smooth_scroll_pr.zip
Here's a 120 FPS video. The bottom-left ScrollContainer has smooth scrolling disabled. The bottom-right ScrollContainer has smooth scrolling enabled. The top-right ScrollContainer has smooth scrolling enabled and a scroll step of 4 (instead of the default 0.125):
https://user-images.githubusercontent.com/180032/214710180-f159a1e3-9aaa-41ab-91e1-848619adf535.mp4
Some observations:

Smooth scrolling on desktop feels good with the default value – it's responsive, yet visibly smoothed. Its speed is independent from rendering FPS (as it should be). It also works fine when low processor mode is enabled.
Scrolling on mobile feels quite good and no longer seems to suffer from snapping issues.
I couldn't manage to scroll with the keyboard using arrow keys or PgUp/PgDn, even after clicking a button located within the ScrollContainer (or setting the ScrollContainer's mode to All).
This PR implements smooth scrolling in ScrollContainer, rather than ScrollBar. This has the unfortunate result that RichTextLabel's scroll bar is not affected by this PR, since it uses VScrollBar directly. This likely also applies to Tree's horizontal scrolling and more.
This PR doesn't affect the script editor's smooth scrolling (as expected, since it uses a custom implementation).
Smooth scrolling doesn't work if clicking on the scrollbar (outside the scrollbar, so it scrolls up/down by one page). It should behave like when pressing PgUp/PgDn in this situation – in other words, scroll smoothly, as we're doing a sudden jump from a location to another.
Smooth scrolling doesn't work if the mouse wheel is scrolled while the cursor is hovering the scrollbar. (The scrolling effect is also doubled, and Scroll Step is ignored – something that also occurs with RichTextLabel's scroll bar.)
If smooth scrolling is globally enabled in the project settings, there is no way to disable it for a specific node only. I suggest refactoring the Scroll Smoothed property into an enum (Default, Enable, Disable).
Scroll-related properties should be part of the existing Scroll section in the inspector.
Documentation and property hints should be added for the project settings and properties (deadzone/step). For instance, scroll step, deadzone, smooth scroll duration and scroll touch inertia shouldn't be settable below 0.0.

This PR implements smooth scrolling in ScrollContainer, rather than ScrollBar. This has the unfortunate result that RichTextLabel's scroll bar is not affected by this PR, since it uses VScrollBar directly. This likely also applies to Tree's horizontal scrolling and more.

Yeah, I agree that this is very limiting. I think we could expand this further in future, in 4.x? In fact, upon reviewing this work closer I'm thinking that the compat breaking part is not that critical and can be postponed to 4.1, if we need more time. For project settings we can add some compatibility code, and for the changes in behavior, well, that's probably the desirable part anyway.
Anyway, until this is done, I guess ScrollBar will eat all the input and handle it without any enhancements.

Scrolling on mobile with touch input is broken. As soon as you release the finger, the scrollbar will go back to its original position. This is easier to notice with smooth scrolling enabled, but it occurs with smooth scrolling disabled too.
I couldn't manage to scroll with the keyboard using arrow keys or PgUp/PgDn, even after clicking a button located within the ScrollContainer (or setting the ScrollContainer's mode to All).

This might be my fault from resolving conflicts. Would be nice to review the code by someone experienced here to spot potential typos or rebase errors.


Issue with numeric.hpp

I'm facing this issue when executing make .deps
kws.cpp:108:10: fatal error: boost/python/numeric.hpp: No such file or directory   108 | #include <boost/python/numeric.hpp>       |          ^~~~~~~~~~~~~~~~~~~~~~~~~~
I'm running on Python 3.6 based virutalenv

have you solved this problem yet? I'm facing this problem, too


Can not generate or find the libgl_useful.so file

Hi
i could not find the libgl_useful.so file - i don't think it was generated - how can i generate it ?
Thanks for your help

Did you follow the build instructions?

I’ll take that as a “no”.

Hi sorry for the delay in replying - i have been super busy and with a terrible flu so non-essential tasks got pushed aside. I will work on it this weekend again. I did follow the build instructions and i got past that initial error i mentioned above but i have a new error - i will investigate.
Thanks


Fix endorsement icons

Reported in my Discord and confirmed, they changed endorsement icons to be "/svg?path=PATH" instead. This accounts for that possibility in the endorsement icons by parsing the query and checking for path if it exists.
Example of the new icon url, which appears to just be a wrapper to an svg endpoint or similar:
background-image:url(/svg?path=https%3A%2F%2Fstatic.playoverwatch.com%2Fsvg%2Ficons%2Fendorsement-frames-3c9292c49d.svg#_3)

Thanks man!


sub-pixel rounding issues with chrome zoom levels

Hello - Thanks for your awesome script!  I noticed a subpixel rounding issue with chrome zoom levels (not with your code) where it looks like there is a border where the svg overlaps a div above or below the one where your svg object is attached.  This is simply fixed by adding a 1px border to the div that your svg is attached to with the same background color as the svg object. This is not an issue with your code, but I wanted to help others if they are struggling w/ this chrome issue!

@heyprotoman I think this may be similar to https://github.com/josephfusco/angled-edges/issues/14.
Thank you for your feedback and report!


Make Badlion.BadlionClient Manifest 1.6

Microsoft Reviewers: Open in CodeFlow

@wingetbot run

@wingetbot run


deficient number feature added

Do the checklist before submitting the PR:

[ YES ] Have you read the guidelines mentioned in CONTRIBUTING.md?
[ YES ] Have you squashed your commits?

Q: What version of Node.js you've used in the project? (e.g. Node v10.11.0)
A: v10.7.0
Q: Mention the Issue Number! (e.g. Fixed #8)
A: Fixed #17

Codecov Report

Merging #25 into master will decrease coverage by 72.58%.
The diff coverage is 23.07%.

@@             Coverage Diff             @@
##           master      #25       +/-   ##
===========================================
- Coverage   97.11%   24.53%   -72.59%
===========================================
  Files          28       21        -7
  Lines         243      216       -27
===========================================
- Hits          236       53      -183
- Misses          7      163      +156

Impacted Files
Coverage Δ

src/index.js
58.33% <100%> (-41.67%)
:arrow_down:

src/deficient/index.js
16.66% <16.66%> (ø)

src/smith/index.js
11.42% <0%> (-88.58%)
:arrow_down:

src/validation/number-array.js
14.28% <0%> (-85.72%)
:arrow_down:

src/validation/integer-array.js
14.28% <0%> (-85.72%)
:arrow_down:

src/smart/index.js
16.66% <0%> (-83.34%)
:arrow_down:

src/fibonacci/index.js
16.66% <0%> (-83.34%)
:arrow_down:

src/kaprekar/index.js
11.76% <0%> (-82.36%)
:arrow_down:

src/lucky/index.js
18.18% <0%> (-81.82%)
:arrow_down:

src/factorial/index.js
22.22% <0%> (-77.78%)
:arrow_down:

... and 21 more

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 1b1ae76...2c475a4. Read the comment docs.

@pbiswas101 added unit test cases. Why is it failing?

@hiteshpr Nice! Coverage has improved from your previous commit but still in order to pass the check you need to test for input type boolean, function, array, null, etc. and also try to include more numbers beside 12, 17 and 21! While making changes you can also check if your coverage has increased by running the command npm run test. Currently, it stands at 92.85% (for deficient number) but you need to target 97.11% or above!
**NOTE: This PR is also changing the contents of package-lock.json so please resolve that side-effect.

Closing this PR due to merge conflicts!


sidenav fixed in bootstraps main website

Hi all,
would it be helpful to have side nav that stays in the right-side of the website to be fixed?

The documentation is a very long list and I have to scroll up to read about another component. I am talking about this element on the page : <nav class="bd-links" id="docsNavbarContent">
or at least to have scroll up button.

Maybe I am missing something, but it is fixed.

https://v4-alpha.getbootstrap.com/components/alerts/
let's say you are on this page and you continue to read.
The side nav moves to the top of the page. and if I want to navigate to another component I have to scroll all the way up and find side nav.

You are in the wrong place :) here are bs4 docs now: http://getbootstrap.com/

closed thanks to @andresgalante comment's, please use our new documentation 👍

Oh thanks, didn't know about that page


Play State

Hi is there any way to get the stat out from this addon? I want to get if the TV is playing something or paused or idle mode.. ????
This works for all Chromecast, android tv boxes etc.

Any updates on this? Would love for HA to know when something starts/stops playing something
Thank you


Use states.last_updated to determine age of state

Previously, as each state was added to the list of state values for calculating the statistics the current UTC time was added to the corresponding self.ages, and this was used to determine if a value fell outside of max_age.
The limitation of this approach is as such: upon initialization, all historic state values that are loaded are given the current time and only values that are recorded since initialization get accurate times. Thus, if I'd like to monitor the statistics over the last 24 hours and I supply an arbitrarily large sampling_size, when I initialize the component all of the values (up to n=sampling_size) are included, not values for the last 24 hours. The component would have to be loaded for a full 24 hours before this would be the case.
Here, I use each state value's last_changed parameter to determine if it should be excluded based on the max_age parameter. I think this is a better representation of what the max_age parameter is meant to achieve.
Description:
Related issue (if applicable): fixes #
Pull request in home-assistant.github.io with documentation (if applicable): home-assistant/home-assistant.github.io#<home-assistant.github.io PR number goes here>
Example entry for configuration.yaml (if applicable):

Checklist:
If the code does not interact with devices:

[x] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[x] Tests have been added to verify that the new code works.

Hi @grantbey,
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!

Can you write a test?

Yes absolutely. This is my first PR - can you show me an example of what
you need?
Thanks!
On Nov 3, 2017 09:02, "Pascal Vizeli"<EMAIL_ADDRESS>wrote:

Can you write a test?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/home-assistant/home-assistant/pull/10297#issuecomment-341696931,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AG8jXqvsAM_4_YcgyKhIUXEsQH0EbT9xks5syw73gaJpZM4QQTF5
.


UofT-DSI | Applying Statistical Concepts - Assignment 2

What changes are you trying to make? (e.g. Adding or removing code, refactoring existing code, adding reports)
I am submitting my solution to Assignment 2, which involves working with the Auto MPG dataset to perform exploratory data analysis, visualizing relationships between variables, fitting a multivariable linear regression model, and evaluating its performance using Root Mean Square Error (RMSE).
What did you learn from the changes you have made?
Through this assignment, I gained hands-on experience with several important concepts in machine learning and statistical modeling:

The importance of exploratory data analysis before building models.
How to visualize relationships between variables to understand potential correlations.
The process of splitting datasets into training and testing sets for model evaluation.
Fitting multivariable linear regression models using scikit-learn.
Interpreting model coefficients and understanding their implications.
Evaluating model performance using metrics like RMSE.

Was there another approach you were thinking about making? If so, what approach(es) were you thinking of?
While completing the assignment, I considered exploring feature engineering techniques to potentially improve the model's performance. Specifically, I was interested in:

Transforming the horsepower variable, possibly using logarithmic transformation to address skewness.
Exploring interaction terms between predictors to capture non-linear relationships.
Applying regularization techniques (Lasso or Ridge regression) to deal with multicollinearity among predictors.
However, these approaches were beyond the scope of the current assignment and would be interesting to explore in future work.

Were there any challenges? If so, what issue(s) did you face? How did you overcome it?
One challenge I faced was interpreting the coefficients of the multivariable model. Initially, it was difficult to understand how to interpret the effect of each predictor while controlling for others. I overcame this by carefully reviewing the documentation for scikit-learn's LinearRegression class and consulting online resources that explained coefficient interpretation in multivariable regression.
Another minor issue was ensuring that all numeric predictors were properly selected for the model. I resolved this by carefully examining the dataset structure and using pandas' select_dtypes method to filter numeric columns.
How were these changes tested?
I tested my changes by:

Running each code block individually to ensure it executed without errors.
Verifying that the output matched expectations (e.g., checking the number of rows and columns in the dataset).
Plotting the scatter plots and visually inspecting them to confirm they displayed the expected relationships.
Using print statements to display intermediate results and verify calculations.

A reference to a related issue in your repository (if applicable)
N/A
Checklist

[x] I can confirm that my changes are working as intended

A2: Complete
Great work


Pls maintain a cask install from homebrew!!!

Pls maintain a cask install from homebrew!!!
Thanks.. :-)

Happy to try to add if you like? @vineetchoudhary

Hi James, I'll be happy. Thanks 🙏

Submitted: https://github.com/Homebrew/homebrew-cask/pull/91180
Will need to wait for review and then they'll ask you @vineetchoudhary to approve.

Add let me know when you release a new version...

Sure. Thank you.

Will need to wait for review and then they'll ask you @vineetchoudhary to approve.

We never ask upstream for approval. There’s no point—either the cask works and can be accepted or it can’t.

Add let me know when you release a new version...

If you use an RSS reader, you can subscribe to https://github.com/vineetchoudhary/Downloader-for-Apple-Developers/releases.atom, or use a service like https://blogtrottr.com/ to convert those to emails.
@vineetchoudhary The app bundle’s name is a bit problematic for us. We have a strict token reference to avoid duplicates, and the current name is incredibly generic from a relatively unpopular repo. Would you consider changing the app’s name to something more explicit (e.g. Downloader for Apple Developers.app) or is that out of the question?

That's probably too long and it'll get truncated in LaunchPad. I'd suggest something like "Apple Dev Downloader" or "Developer Downloader" for the display name or bundle name.

@vitorgalvao I'll change app name with new version release.
@i0ntempest thanks for your suggestions. I like Apple Dev Downloader.

Hey, is there something new?

Hi, are there any updates as to when a name change and a subsequent release on Homebrew Cask should be expected by?


nixos/tests/lxd: move into subdir, use minimal init, remove sleeps

Description of changes

There are already four test files and I will be adding at least one more.
lxd init has a minimal preseed option, so let's use that instead of a custom config
loop checking for instance to start instead of fixed sleep

Part of and prep for #244093
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/2535

@ofborg test lxd

@AndersonTorres mind merging for me? thanks :pray:


[v6 alpha] Swiper's examples don't work correctly

Framework7 version: f7 v6 (Core) up to alpha 10
Platform and Target: Mac 10.11.6 El Capitan with Safari 11.1.2 and Firefox 78.2.0esr browsers

Describe the bug
In my testing of the various alpha of f7 version 6 with Kitchen Sink I noticed that the Swiper's examples don't work correctly.
Instead the examples published at this link: https://swiperjs.com/demos/ work correctly.

Fixed in https://github.com/framework7io/framework7/commit/2fc021c86192766befac3e8ab35bb41c59d30780


Documentation error

There is a documentation error. Docs say to use "use HipsterJazzbo\LaravelMultiTenant\Traits\BelongsToTenant;" but it returns error because directory doesn't exist. Correct usage based on current directory is "use HipsterJazzbo\Landlord\BelongsToTenant;"

'Landlord' => HipsterJazzbo\Landlord\LandlordServiceProvider::class, must be added to the alias, and Facade changed to return 'HipsterJazzbo\Landlord\Landlord';

Why change the facade class name?

Only because it originally was as return 'HipsterJazzbo\LaravelMultiTenant\TenantScope' and that directory doesn't exist

Sweet. Fixed that.


self-signed certs should probably have CA:TRUE constraint

Otherwise code that checks for this (cough)go(cough) will bomb out.  Maybe there's a better way to do this, but I can't get self-signed certs to work with things like filebeat without this being set.

Maybe "should" is too strong.  Maybe it would be better to just let us optionally turn it on in the resource.

Makes sense I guess, would accept a pull-request for it. Making it optional might be a bit overkill so adding this to all self-signed (temp) certs should be fine.

Should be fixed in https://github.com/golang/go/commit/8ad70a549364c216c386afcead4dccfdcd39748b


About the evaluation metric mIoU.

Hi, thank for your nice work and job.
After reading your code, i have a little question. can you share the code how to compute the mIoU in unsupervised way, because which is different from supervised segmentation.
Thank you!👍

Thanks for your comment! The code is coming soon. The sample code and segments are currently in my Dropbox link here.
$ python miou_calculation.py --bsd500 --mode 1 --gt ./gt --input ./results

mode 1: "all"
mode 2: "fine"
mode 3: "coarse"
Before mIOU calculation, you need to distinguish unconnected segments that have the same class labels. I used this library to relabel connected components.

great thank for your reply!

Thanks for your comment! The code is coming soon. The sample code and segments are currently in my Dropbox link here.
$ python miou_calculation.py --bsd500 --mode 1 --gt ./gt --input ./results

mode 1: "all"
mode 2: "fine"
mode 3: "coarse"
Before mIOU calculation, you need to distinguish unconnected segments that have the same class labels. I used this library to relabel connected components.

Can you describe how you use the library (mentioned above) to relabel connected components? Assuming that I have just cloned the repo and compile the library, what's the next step? It will be helpful if you can share the command line to relabel the connected components.

I used the function SuperpixelTools::relabelConnectedSuperpixels(segmentation) in examples/cpp/evaluation.cpp.
To obtain the output, I inserted the following lines in L151 and then used the executable bin/example_evaluation.
    for (int i = 0; i < segmentation.rows; ++i) {
        for (int j = 0; j < segmentation.cols-1; ++j) {
          std::cerr << segmentation.at<int>(i, j) << ",";
        }
        std::cerr << segmentation.at<int>(i, segmentation.cols-1) << std::endl;
    }

Hi,
Thank for your amazing work.
Could you please tell me which part of the database did you use to evaluate your model, and how do you process the data (results, gt)?
thank you in advance

Regarding your code, what is the use of these lines?
gg = np.zeros(gt_array.shape)
gt_mask = np.where(gt_array > 0, 1, gg)
determinant_array = gt_mask * input_array
label_list = np.unique(gt_array)
I saw that you have defined label_list already above.

Thanks for your comment! The code is coming soon. The sample code and segments are currently in my Dropbox link here.
$ python miou_calculation.py --bsd500 --mode 1 --gt ./gt --input ./results

mode 1: "all" mode 2: "fine" mode 3: "coarse"
Before mIOU calculation, you need to distinguish unconnected segments that have the same class labels. I used this library to relabel connected components.

have the other method to relabel connected components?


[Native Controls] TNativeEdit

As per the title, create a TNativeEdit control to complement the others.

Ouch.. one year later. I'll take a look soon

Double ouch, but this is low priority


Upgrade production database with v1.1 schema changes

Deployment preps

[x] Import existing content to Medium
[x] Configure a Backup for your Azure App Service and Database

Generate sql upgrade script

[x] I'm adding a new sln folder called sql

clone dev branch, run it to create a test db that mimics schema in prd
gen sql upgrade script 1.0-1.1.sql and run again the test db
run app against test db

Azure resources preps
Clean up

[x] delete fanraytst App Service and Tst App Service plan (done in one shot in portal), also delete fanraytstApplicationInsight
[x] disconnect github deployment from fanray App Service

Create new resources

[x] create SQL database fanray-stg Basic ($5mo, 2GB, up to 5 eDTUs) in fanray SQL Server
[x] create Blob storage fanraystg StorageV2 (general purpose v2) Locally-redundant storage (LRS) Hot
[x] create Application Insights appinsights-stg on West US 2

Modify fanray App Service

[x] scale-up fanray App Service to S1 ($45, so I can use Deployment slots) from B1

[x] add an empty fanray-stg Deployment slot (Note: only give the slot name as stg, Azure will prefix fanray- to it, you don't want your URL ends up like fanray-fanray-stg.azurewebsites.net)
[x] add App setting in Application settings ApplicationInsights:InstrumentationKey sticky!
[x] add App setting in Connection strings defaultConnection database connection string sticky!
[x] add App setting in Connection strings BlobStorageConnectionString sticky!

Note:

when you create a new slot say tst and choose Configuration Source from existing fanray which is prd, you are only getting its Application Settings, no code is deployed.
I don't map domain to the deployment slot, if I do I have to worry about https.

Deployment steps

[x] deploy dev branch from github to stg, verify stg db tables
[x] deploy current feature branch to stg, note right after the deployment finishes syncing, db is not updated yet, once you visit the site EF will auto upgrade db, alternatively you can run 1.0-1.1.sql first before deploy feature branch. By now your
[x] swap stg with prd, EF will auto upgrade prd db

Is it OK to update a production database with EF migrations?

References

Database connection string when swapping between App Servers slots
Set up staging environments in Azure App Service
Deployment Slots for Web Apps using Azure App Service
Testing Web Apps in Production with Azure App Service
Configure Application settings in Azure App Service
Azure Web Sites – block web access to non-production deployment slots
Import a BACPAC file to a new Azure SQL Database

During deployment I often encounter file locking, see https://github.com/Microsoft/vsts-tasks/issues/1607#issuecomment-260946957

Deploying with EF migration worked well.


Update DistributedLoad using cache request

What changes are proposed in this pull request?
Update DistributedLoad using cache request instead of read with passive cache.
Why are the changes needed?
using read to cache block is not efficient and error proune. Use cache request directly.
Does this PR introduce any user facing changes?
no

Codecov Report

Merging #14530 (10d8dfa) into master (c642abc) will decrease coverage by 24.88%.
The diff coverage is 0.00%.

@@              Coverage Diff              @@
##             master   #14530       +/-   ##
=============================================
- Coverage     41.83%   16.95%   -24.89%
+ Complexity     9329     2705     -6624
=============================================
  Files          1494     1494
  Lines         87668    87681       +13
  Branches      10449    10449
=============================================
- Hits          36678    14868    -21810
- Misses        48006    71573    +23567
+ Partials       2984     1240     -1744

Impacted Files
Coverage Δ

.../main/java/alluxio/exception/ExceptionMessage.java
0.00% <0.00%> (-99.41%)
:arrow_down:

...erver/src/main/java/alluxio/job/util/JobUtils.java
0.00% <0.00%> (-91.03%)
:arrow_down:

.../main/java/alluxio/cli/fs/command/LoadCommand.java
0.00% <0.00%> (ø)

...mon/src/main/java/alluxio/shell/CommandReturn.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...mon/src/main/java/alluxio/util/ExceptionUtils.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...n/src/main/java/alluxio/wire/AlluxioProxyInfo.java
0.00% <0.00%> (-100.00%)
:arrow_down:

.../src/main/java/alluxio/wire/AlluxioMasterInfo.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...src/main/java/alluxio/job/meta/JobIdGenerator.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...n/src/main/java/alluxio/stress/BaseParameters.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...src/main/java/alluxio/client/UnderStorageType.java
0.00% <0.00%> (-100.00%)
:arrow_down:

... and 682 more

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 c642abc...10d8dfa. Read the comment docs.

@jja725 As CacheRequest is a new come feature, I hope it would be stable, but maybe there are some bugs for several months in the future, so I suggest to keep an option to load data by original read back mode, once the cacherequest way fail, we can also using distributedload command. If we keep the option for previous read-back data mode, we can have more courage to upgrade to the new version or back porting this patch.

@jja725 overall looks good. @maobaolong 's suggest is a valid one, but I am also interested in the performance aspect of this. Could you do some benchmarking using two versions and see how much it improves load performance?

sure I would do the benchmarking and add a option for distributedLoad

@yuzhu @maobaolong add one option to support the old passive cache implementation

@jja725 could you update the documentation for distributedLoad to reflect the strategy choices?

@jja725 could you update the documentation for distributedLoad to reflect the strategy choices?

@yuzhu added doc, and I set the default to not use direct cache. So probably we can merge this in and try to test it in container env later after docker hub have the newest version(hard to test feature branch). After confirmation with test docker env, we can switch the default to use direct cache.

@yuzhu @maobaolong tested in local docker env, it works fine. So I would set using direct cache as default then.

alluxio-bot, merge this please


Hash of source code in compare

This is a feature request. I think it would be helpful if there was a hash of the source code to filter on in compare

Good idea!
Just to confirm I understand what's driving this... You want to see at-a-glance if the source code snapshot has changed across two runs. If you're trying to resolve why results are different between two runs, it's nice to spot if the source has changed - and then use diff to investigate further.
Did I get that right?

That's exactly it! :)

Ah, interesting. So I can include a run filter for sourcecode hash across all of the run list commands (similar to filter by run status, operation, etc. but this would filter by sourcecode hash).
I think in your case the command might look like:
$ guild compare --sourcecode-digest abc123

You'd be able to enter a digest prefix to match.

This is teed up for 0.6.6 and available for preview in 0.6.6.dev3 and later.

Works great! Thank you!


stable/nginx-ingress: add optional controller.defaultSSLCertificate configuration value.

Useful if you want to use one certificate cluster-wide and do not want individual namespace admins having direct access to the ssl certificate secret.
I signed CNCF CLA on 19 July 2017.

/ok-to-test

This probably wasn't necessary, as the argument could have been provided via the extraArgs map. We'll leave it be, of course. I'm just wary of adding a new value for every possible argument.

FYI: This is reverted in #1610. See comment by @mgoodness above. We agreed that extraArgs should be used instead.

@mgoodness , @unguiculus : neither defaultSSLCertificate, nor extraArgs allow you to install cert as part of same helm release where nginx-controller is just a dependency. Reason is, {{ .Release.Namespace}} cannot be used in values.yaml :( I can't think of a good workaround, maybe you have any ideas?

I think the best we could do for that scenario is provide a Secret template that would populate from a SSL cert stored as a value, then point the --defaultSSLCertificate argument to that Secret.


Added support for queries that don't specify a table when there is no…

… table selected.
Signed-off-by: Zach Musgrave<EMAIL_ADDRESS>

Should say "when there is no database selected"


test Khanh's hypothesis wrt the v0.34.x comet-bft branch

Description
While investigating issues with other repositories, our team member @catShaark noticed that there are other repositories affected by protocol buffers build issues, notably in this case, CometBFT.
Please add a description of the changes that this PR introduces and the files that
are the most critical to review.
If this PR is non-trivial/large/complex, please ensure that you have either
created an issue that the team's had a chance to respond to, or had some
discussion with the team prior to submitting substantial pull requests. The team
can be reached via GitHub Discussions or the Cosmos Network Discord server in
the #cometbft channel. GitHub Discussions is preferred over Discord as it
allows us to keep track of conversations topically.
https://github.com/cometbft/cometbft/discussions
If the work in this PR is not aligned with the team's current priorities, please
be advised that it may take some time before it is merged - especially if it has
not yet been discussed with the team.
See the project board for the team's current priorities:
https://github.com/orgs/cometbft/projects/1
-->

PR checklist

[ ] Tests written/updated
[ ] Changelog entry added in .changelog (we use
unclog to manage our changelog)
[ ] Updated relevant documentation (docs/ or spec/) and code comments

Converted this to draft and approved CI checks run.

This doesn't compile.

it's true.  It did.  I am not too sure what the last commit did sorry


Accept config file name in parameters

As dpp-datahub user, I want to pass the config file name/path to the file as a parameter, so that I can use multiple of them to publish stuff under multiple users
Acceptance Criteria

[x] able to push with multiple config files

Tasks

[x] Refactor params

FIXED


ValueError: a weight file containing 446 layers into a model with 638 layers.

Hi I attempt to run test_denoise.py, I got value error:  "You are trying to load a weight file containing 446 layers into a model with 638 layers". Thank you for your help.

Hi, thanks for your concern.
I just found the the weight files were deprecated. Please feel free to clone the code and retrain the model.
Best,!


Updated haskell-wreq to 0.3.0

Includes updated dependency, http-client (.cabal file has incorrect lower bound)

Any news on this issue?


Normalization layer supresses ValueError when model is called with bad input shape

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): yes
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Colab notebook, and everywhere else tested
TensorFlow installed from (source or binary):  Colab notebook, and everywhere else tested
TensorFlow version (use command below): v2.4.1-0-g85c8b2a817f 2.4.1
Python version: 3.7.10

Describe the current behavior
After adding a tf.keras.layers.experimental.preprocessing.Normalization layer to a model, badly shaped input is accepted by the model's .predict, generating only a warning log line, and returning some nonsense output.
Describe the expected behavior
After adding a tf.keras.layers.experimental.preprocessing.Normalization layer to a model, badly shaped input should be rejected by the model's .predict, raising a ValueError.
Standalone code to reproduce the issue
Here is a Colab notebook that shows the issue

@jameshfisher
I ran the code shared in colab but do not face same error reported, please have a look at the gist here.

@Saduf2019 your gist shows the same problem. See the final code cell in your gist. model_with_normalization_layer.predict(bad_input) only produces a WARNING log line, and returns a nonsense value of shape (5,1). But what it should do is raise a ValueError, and not return any value, because its input has shape (5,), which does not match the shape enforced by its first layer, tf.keras.Input(shape=(3,)). This is the normal behavior when a Normalization layer is not present (see the line model_without_normalization_layer.predict(bad_input) for reference); adding a Normalization layer should not change this behavior.

@jvishnuvardhan
I ran the code on nightly as well, please find the gist here.

I'd like to work on this.

Was able to reproduce this issue using TF v2.5 ,please check the gist here..Thanks !

Was able to replicate the issue with TF 2.6.0-dev20210606,please find the gist here ..Thanks!

@jameshfisher,
I have tried in Colab with Tensorflow 2.8 and i am seeing InvalidArgumentError with model_with_normalization_layer.predict(bad_input). Please, find the gist here and confirm if this issue is resolved for you.Thanks!


HoloLens Bitlocker Encryption Method

The documentation on using Bitlocker with the HoloLens seems pretty vague. So for the HoloLens when enabling Bitlocker through provisioning packages, what encryption method is used? And is there any way to change the encryption method through either provisioning packages or MDM?
When the documentation says Bitlocker is silent on the HoloLens, what exactly does that mean? Are the files just decrypted when logging into the HoloLens?

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

ID: 9f605e50-3184-f27d-36a8-b3cf608c6120
Version Independent ID: d6bcd384-b494-43b3-e2e7-9ff46c6a513f
Content: Enable Bitlocker encryption for HoloLens (HoloLens)
Content Source: devices/hololens/hololens-encryption.md
Product: hololens
GitHub Login: @jdeckerMS
Microsoft Alias: jdecker

@jjherman94 Correct, the setting is on or off.


Suggestion: Store generated csrs and provide download option

Thank you for a great tool!
In my case, we generate a lot of csrs for clients and once the client purchases the SSL, we install it on our LB.
However, we want to keep a history of these so that we can refer to them at any time and download them ( even a project manager should be able to download and send it to the client ).
I have enhanced the tool a bit with these features.
Would you be interested if I shared it or are those beyond the scope of your tool ?
Let me know.
Thanks.

Hey @mandys thanks for your interest and thanks for raising an issue for this. I do think this is a little out of scope -- at least for the public version of this project -- because I don't think it's safe to store the private key for users, even client side with localStorage. This is secret material and could potentially be used to impersonate a server, and I don't really want that responsibility. And right now everything is stateless and I prefer it that way. I do see the need for something like this in a self-hosted environment though, so I'm happy you were able to make it fit your particular use case.
I would like to add a download option for CSRs/private keys as they are generated, so if you happen to have any changes related to that I'll accept those.


nbdev_preview errors out

nbdev_preview fails in 2.2.7, 2.2.8 and HEAD like so:
…/nbplanetary ❯ nbdev_preview
Traceback (most recent call last):
  File "/home/ayek72/mambaforge/envs/py310/bin/nbdev_preview", line 10, in <module>
    sys.exit(preview())
  File "/home/ayek72/mambaforge/envs/py310/lib/python3.10/site-packages/fastcore/script.py", line 119, in _f
    return tfunc(**merge(args, args_from_prog(func, xtra)))
  File "/home/ayek72/mambaforge/envs/py310/lib/python3.10/site-packages/nbdev/quarto.py", line 278, in preview
    nbdev_quarto.__wrapped__(path, preview=True, **kwargs)
TypeError: nbdev.quarto.nbdev_quarto() got multiple values for keyword argument 'preview'

version infos
I tried with nbdev 2.2.7, 2.2.8, and HEAD (57f7e5b020e08f875f389010accf5cc38af26bde)
…/nbplanetary ❯ quarto check

[✓] Checking Quarto installation......OK
      Version: 1.1.168
      Path: /opt/quarto/bin

[✓] Checking basic markdown render....OK

[✓] Checking Python 3 installation....OK
      Version: 3.10.6 (Conda)
      Path: /home/ayek72/mambaforge/envs/py310/bin/python
      Jupyter: 4.11.1
      Kernels: python3, xonsh

[✓] Checking Jupyter engine render....OK

[✓] Checking R installation...........(None)

      Unable to locate an installed version of R.
      Install R from https://cloud.r-project.org/

…/nbdev ❯ uname -a
Linux x.x.x.x 5.15.0-46-generic #49~20.04.1-Ubuntu SMP Thu Aug 4 19:15:44 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

If i remove preview=True here, nbdev_preview works again. Bad fix or ok?
https://github.com/fastai/nbdev/blob/master/nbdev/quarto.py#L278

Should be fixed now.


Add UNITY_LICENSE_PATH

In general, is there a reason why you're not simply renaming your distributed license file to UnityLicenseFile.ulf? It should already work without any code changes.

A license can only be used by one unity version.
When running on multiple unity versions, we must have multiple license files.

Strange that the test is failing. I'll have a look at that.

Hello.
-I manually modified index.js. I try to revert it. But the CI still fails.
-I built index.js via yarn build, but the files look different.
Like this.

I merged your PR. the different of the index file seemed to be caused by not updated dependencies.
To fix this next time you should yarn to update the dependencies (because you rebased) and then yarn build, instead of only doing yarn build again. Either way it should have gone automatically, so I will fix this in another PR here https://github.com/webbertakken/unity-builder/pull/74.
Thanks again for your contributions!


Microsoft.EntityFrameworkCore.Sqlite.Design SQLite dependency case issue

Steps to reproduce
Add this dependencies to an Asp.Net Core 1.0 project.json
  "dependencies": {
    ...
    "Microsoft.EntityFrameworkCore": "1.0.0",
    "Microsoft.EntityFrameworkCore.Design": "1.0.0-preview2-final",
    "Microsoft.EntityFrameworkCore.Relational": "1.0.0",
    "Microsoft.EntityFrameworkCore.SQLite": "1.0.0",
    "Microsoft.EntityFrameworkCore.Sqlite.Design": "1.0.0",
    ...
  },
  "tools": {
    ...
    "Microsoft.EntityFrameworkCore.Tools": "1.0.0-preview2-final",
    ...
  },

run: dotnet ef migrations add testMigration
get: project.json(27,58): error NU1001: The dependency Microsoft.EntityFrameworkCore.Sqlite >= 1.0.0 could not be resolved.
Compilation failed.
The issue
The case of Microsoft.EntityFrameworkCore.Sqlite package dependency in https://github.com/aspnet/EntityFramework/blob/master/src/Microsoft.EntityFrameworkCore.Sqlite.Design/project.json is wrong.
The correct case of package name is Microsoft.EntityFrameworkCore.SQLite.
Changing the case in project.lock.json solved the problem.
"Microsoft.EntityFrameworkCore.Sqlite.Design/1.0.0": {
   "type": "package",
   "dependencies": {
      "Microsoft.EntityFrameworkCore.Relational.Design": "1.0.0",
-------------------------
      "Microsoft.EntityFrameworkCore.SQLite": "1.0.0"
-------------------------
   },
   "compile": {
      "lib/netstandard1.3/Microsoft.EntityFrameworkCore.Sqlite.Design.dll": {}
   },
   "runtime": {
      "lib/netstandard1.3/Microsoft.EntityFrameworkCore.Sqlite.Design.dll": {}
   }
},

Please consider standardizing all sqlite names with same case.
I'm running on Linux, so case matters.
Further technical details
EF Core version: (found in project.json or packages.config)
"Microsoft.EntityFrameworkCore": "1.0.0",
"Microsoft.EntityFrameworkCore.Design": "1.0.0-preview2-final",
"Microsoft.EntityFrameworkCore.Relational": "1.0.0",
"Microsoft.EntityFrameworkCore.SQLite": "1.0.0",
"Microsoft.EntityFrameworkCore.Sqlite.Design": "1.0.0",
"Microsoft.EntityFrameworkCore.Tools": "1.0.0-preview2-final",
Operating system:
OpenSUSE Tumbleweed (using dotnet for OpenSUSE 13.2)
Visual Studio version: (e.g. VS 2013 or n/a)
Visual Code 1.2.1

Casing in the package dependency is actually consistent with the package we produce (they are both Sqlite. My guess is that if you change your project.json file to have the same casing as the package, the issue would disappear.
That said, package names should not be case sensitive, this is a known issue that the NuGet team is working to fix.

Ok. My mistake. I figured out the problem. The path of the package in .nuget/packages is created based on the casing of dependencies in project.json. Thanks for the reply.


replace deprecated runSQL contract method

After the changes in https://github.com/tablelandnetwork/evm-tableland/pull/257 are deployed to all of our chains, and lands in local-tableland, this PR will be a patch update to replace the deprecated Registry Contract method use.

fixes #138

This is superseded by #432


(node:7472) Warning: Possible EventEmitter memory leak detected. 11 close listeners added. Use emitter.setMaxListeners() to increase limit

I have:
node --version v6.9.1
npm --version 3.10.8
<EMAIL_ADDRESS><EMAIL_ADDRESS>With source code:
var restify = require('restify');
var serveStatic = require('serve-static-restify');
var app = restify.createServer();
app.pre(serveStatic('app'));
app.listen(3000);
When I run it, it works but I get alot of:
(node:7472) Warning: Possible EventEmitter memory leak detected. 11 close listeners added. Use emitter.setMaxListeners() to increase limit

this is extremely odd to have a leak like this, because we don't add a single 'close' listener in the code. That being said I'd try to find where it happens first. This module is used heavily in production and never had any odd problems with this.
However, I'm using the .use, and it the demo code .pre is used, because otherwise restify will always return 404 due to non-matching routes


Create rc-lap-tracker

Hello,
This plugin allows for tracking pouch degradation while training at ZMI.
Other plugins I have found to be unreliable, due to the pouch's inventory not always updating if you bank too quickly.
My goal with this plugin was to circumvent this issue by simply tracking the laps you perform at ZMI.
Config allows for selecting the highest tier pouch you are using, and the counter will reset to the proper value based on this setting.
Counter decrements the first time you craft runes after entering ZMI.
Counter resets on NPC Contact cast.

I updated this from a ZMI specific plugin to work with any other lap related RC methods.

Okay this is actually done now. Plugin state persists through world hops and logging out.


Add libsecp256k1.mo

libsecp256k1.mo is a working fork of the abandoned and unfinished mix-labs/libsecp256k1, so the link to the latter was removed.

Thanks for the contribution


Support for DogStatsD container ID

DogStatsD protocol v1.2 added an optional docker container ID tag. This PR adds adds that ability to the Datadog connector

 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.

@atooni can you run the CI again?


add support for xarray patching

This looks like a fantastic project with great potential to enhance scientific reproducibility. Thanks to the developers for all of your efforts.
I wanted to open an issue to suggest adding patch support for xarray
https://github.com/pydata/xarray
Xarray is complementary to pandas and provides an interface for loading, analyzing, visualizing, and outputting labeled multi-dimensional array data. Its adoption is increasing rapidly in physical sciences, finance, and other fields.

@rabernat do you maybe have example files that can be opened using open_mfdataset, open_rasterio, open_zarr, and open_dataarray? Preferably small files, that I'm allowed to add to recipy as test data.

Thanks for looking into this!
A good way to proceed would be to use the xarray tutorial datasets, which live in their own repository:
https://github.com/pydata/xarray-data
These can be opened via the xarray.tutorial module, as shown in the xarray docs: http://xarray.pydata.org/en/latest/examples/multidimensional-coords.html
Or you can just open them directly.
There are unfortunately no zarr or rasterio (i.e. geotiff) datasets there yet. I recommend you get started with netCDF files, which represent 95% of xarray use cases. In the meantime, I will work on providing examples of the other formats.

@rabernat Thanks! In the mean time, I found sufficiently small netcdf data for testing the patch of open_mfdataset. For open_rasterio, I just used a standard tiff file, since we are only interested in determining whether the input is logged and not whether it really is a geotiff.
So, now I'm just looking for zarr data.

I can prepare a zarr file for you.
When you say "small files", can you be more specific?
Note that zarr can read from a wide range of stores (see xarray docs and zarr docs). How important is it to cover all of these different cases?

Also, since zarr datasets can be opened directly by the zarr library, you might want to consider a dedicated patch for zarr (without xarray). I anticipate that zarr will grow in popularity over the coming years.

It would be great if you can prepare a zarr file! Small is kilobytes (the netcdf-files I found are 67kb). The data does not have to make sense, but must be valid.
I'll look into the different zarr storage types later. I'd like to cover as much file-based storage types as possible.
And correct me if I'm wrong, but all data loading/saving methods in xarray seems to come from other libraries (I started with a patch for netcdf4). So maybe we don't need a patch for xarray at all 😄 (I'll finish it anyway)

Is this waiting for me?

No, don't worry about it! The work of patching xarray is more or less done (if you could prepare a small zarr file for testing that would still be helpful). I plan to merge this feature soon, but there are some things that need to happen first.


[Epic]: Implement a search bar on the blog page for users to find specific content.

As a potential client, I want to search through blog posts of projects the developer has worked on so that I can easily find various blog posts
Estimated Time
TBD
Acceptance Criteria
Client can correctly and easily find various blog posts through a search bar.

Gatsby documentation on search APIs https://www.gatsbyjs.com/docs/how-to/adding-common-features/adding-search/


Update main.tf

There are two missing properties in the locals dict,
cache_policy_id             = ""
origin_request_policy_id    = ""

what

Describe high-level what changed as a result of these commits (i.e. in plain-english, what do these changes mean?)
Use bullet points to be concise and to the point.

why

Provide the justifications for the changes (e.g. business case).
Describe why these changes were made (e.g. why do these commits fix the problem?)
Use bullet points to be concise and to the point.

references

Link to any supporting github issues or helpful documentation to add some context (e.g. stackoverflow).
Use closes #123, if this PR closes a GitHub issue #123

what
The example script will work as expected.
why
There's a lack of two parameters in the wordpress example...
cache_policy_id             = ""
origin_request_policy_id    = ""

What are you trying to fix here? Is the example not working?
Do you mind filling out the what and the why in the PR template ? These explanations help give us some context.

Yes! the example isnt working... (it's my first commit on a public repo, so.. I'm really newbie on this...)


WIP: Cloudant/CouchDB cleanup

This PR changes oh-so-slightly the schema for packages. An absence of binding used to be stored with binding: {}, now it will be binding: null. All records written in the previous format will still be properly deserialized.

Clean history to follow in #556.


Adjust unit tests to work with async/await

Also started adding some documentation

 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.

@wmcginty @tylermilner  So I'm running into an Xcode bug for testing that's really, really making me want to jettison the .xcodeproj and .xcodeworkspace files in favor of just opening Package.swift. That brings up the problem of how to expose sample code, which I suggest we handle in much the same way now, just using SPM local packages instead of Cocoapods.
Ultimately, testing a swift package that is also trying to support Cocoapods by having a second project structure is very cumbersome. I believe focusing on SPM will set this project up better for the future.
I might be able to get the project building without errors or warnings as-is, but removing the project files and relying only on SPM will help.

What is the particular testing bug?
I've actually gone the opposite way, there are some missing features (at least they were when I moved to the workspace/project model) that made swift test untenable. So the way the current setup was built was that the extent of SPM support was being able to import the package through SPM.

There's a bug with xcodebuild where it doesn't auto-generate resource_bundle_accessor.swift the same way the SPM commands do. That means that attempting to access resources for testing (ex: certificates and mock JSON files) will throw an error using the SPM method of Bundle.module.url(for:).
Conversely, resources are not available to SPM using Bundle(for:).path so attempting to test the package when opening Package.swift results in execution failure.
I was able to get tests working with swift test, even had them succeed on GitHub. However I do not believe we'll be able to test per platform. But since this library just makes use of the foundation I think we should be good.
At the very least I think it'd be good to note in CONTRIBUTING.md how we intend for development to work moving forward. I'm very open to whatever you want to do!

I guess my question is why do we need to run the tests through swift test? On the feature/async branch the tests run fine through xcodebuild (they don't all pass yet, obviously, but they run). In my eyes, for as long we still want to support CP, Carthage and SPM there isn't an issue having the project itself build and test using xcodebuild instead of swift test. Sure, it can be annoying to remember to open the workspace and not the Package.swift, but I don't think thats a huge overhead, especially as it's only for maintainers/collaborators.
I am happy to have the conversation about dropping Carthage/CP support and converting build/test to swift build and swift test (and honestly, I'm all for it), but I'd like that conversation to include all our libraries.

To answer your question, they don't have to be run through swift test. With my tools, the tests would not run at all with xcodebuild, but I believe I can make sure they're running now that I know the intended development context.
I'm gonna go ahead and start over with a new branch now that I have my hands around what's going on and try to get it where we're comfortable merging this branch in.

@GrandLarseny Definitely weird - for reference sake I've got them to run now on latest 14 beta using:
xcodebuild test -workspace Hyperspace.xcworkspace -scheme "Hyperspace iOS" -destination "platform=iOS Simulator,OS=16.0,name=iPhone 13 Pro"
I should have a bit of free time this afternoon, I can take a stab at replicating that behavior on GHA as well.

Closing for now. It'll be good to discuss more changes moving forward, but this won't work to merge into Hyperspace


Feature/storage/upload stream optimizations

Previously, all partitioned uploads buffered each block before uploading
it. Now, some partitioned uploads buffer while some window the base
stream. Decision making is outlined in order below.

If the stream length is unknown: buffered upload. (necessary for
providing content length at REST layer)
Else, if stream length is under defined threshold: one-shot upload.
Else, if sync call: windowed stream. (Parallel upload only offered in async
context; no point of buffering if sequential upload)
Else, if max concurrency == 1: windowed stream. (again, not parallel
upload)
Else, buffered upload.

I'll be starting some basic benchmarking for this change as compared to last public release, measuring time and memory use. Note this means we'll also be testing changes of jumbo-blob support.
Will be measuring small, medium, and large files across sync and async contexts, with max concurrencies of 1 and 2. The belief is that this will save significant memory and some time in sequential uploads, with minimal effect on parallel uploads. These beneficial effects should be more noticeable with large partition sizes.
Will move to active PR upon acceptable results of this testing.

The performance differences of these PartitionedUploader changes compared to our latest public release are listed below. Previous tests of latest public release to jumbo-blob support this is built on showed no significant changes. We tested paths where the uploader used Put Blob, buffered parallel upload, and a non-buffered sequential upload. Buffered sequential upload was not tested and there is no non-buffered parallel upload.
Put blob
No changes in time, CPU intensity, or memory usage.
Buffered parallel upload
Most configurations run a little faster. CPU intensity and memory usage rise in step. This was unexpected, as these changes focused on the next section.
Non-buffered sequential upload
Major improvements in most configurations, organized by block size. Memory usage was flat across all block sizes (barebones process to upload a directory used 53MB), whereas before it went up by a large coefficient based on block size.

4MB blocks: 10-20% speed improvement depending on other settings and overall file size. CPU intensity rises with this and memory usage goes down ~5%.
8MB blocks: speed and CPU inconsistent across sync and async contexts. Async showed similar results to 4MB blocks but sync showed a minor slowdown. CPU was in step with speed, and memory usage went down nearly 30% across both sync and async.
32MB blocks: 15% speed improvement with a 40% CPU intensity increase. Memory usage went down by 70%
100MB blocks: 40% speed improvement with 50% CPU intensity increase. Memory usage went down by almost 90%.

/azp run net - storage - ci


Uncaught TypeError: $ is not a function

I get this about that :
<script>
        $("#share").jsSocials({
            shares: ["email", "twitter", "facebook", "googleplus", "linkedin", "pinterest", "whatsapp"]
        });
    </script>

Are you sure you've added jQuery to the page?
See how to start using jsSocials on the project site http://js-socials.com/start-using/

Yes jQuery is already present on my website.
I incuded the js and the two CSS files + the script but it get this error

I guess then you include jQuery after this script. You need to put link to jQuery before.

Yep you're right but all my JS is deffered at the end, and everything is working fine

yes, then you need to defer the creation of js-socials too, to have it executed when jQuery is available. That's the issue, there is nothing to do with jsSocials.

But, when the page is loaded, jQuery is loaded too so what's the problem ?

The problem is in the order of loading. You can check that in the source of your web page.
If jssocials.min.js comes before jquery.min.js then there is this issue.
Had the same issue on some sites with my Joomla plugin. Solved it to make loading of jssocials.min.js dependend on jquery being loaded.

So where is the problem now ? https://lut.im/QH5ZIdl1DX/leJzr1xXJKlYxEnF.png

do you have url so I can have a look?

Nope, I use autoptimize on WordPress and I can't keep all the css and JS like that forever, nevermind

I know this thread is old and closed but I just ran into this issue. It was working fine on my non wordpress pages but not my wordpress pages. The top answer here resolved it for me:
http://stackoverflow.com/questions/7975093/typeerror-undefined-is-not-a-function-evaluating-document
basically replacing $ with jquery in the jssocials.js file... so the two (window, $... become (window, jQuery...
hopefully this can help others if they run into this problem as well.

@navalee, thanks for the comment.
Missed continuing conversation with @Angristan, but I guess that problem is not in the order of js-socials and jquery scripts, the problem of this <script> /* js-socials creation */ </script> block that creates the control. Meaning when it's executed there is no jQuery, so this block goes before the link to jQuery.


Kubevirt on Azure: Change KAS LB Port to 7443

What this PR does / why we need it:
If the management cluster is Azure and the hosted cluster is created with the kubevirt-provider, the LB port of the kube-apiserver at the HCP can't be 6443 due to azure limitation. In such case, use port 7443 instead.
Which issue(s) this PR fixes (optional, use fixes #<issue_number>(, fixes #<issue_number>, ...) format, where issue_number might be a GitHub issue, or a Jira story:
Fixes #
Checklist

[ ] Subject and description added to both, commit and PR.
[ ] Relevant issues have been referenced.
[ ] This change includes docs.
[ ] This change includes unit tests.

maybe we need an exception for the mtu condition on azure infra
    util.go:1571: incorrect condition: wanted ValidKubeVirtInfraNetworkMTU=True, got ValidKubeVirtInfraNetworkMTU=False: KubeVirtSuboptimalMTUDetected(A suboptimal MTU size has been detected. Due to performance, we recommend setting an MTU of 9000 bytes or greater for the infra cluster that hosts the KubeVirt VirtualMachines. When smaller MTUs are used, the cluster will still operate, but network performance will be degraded due to fragmentation of the double encapsulation in OVN-Kubernetes.)

maybe we need an exception for the mtu condition on azure infra
    util.go:1571: incorrect condition: wanted ValidKubeVirtInfraNetworkMTU=True, got ValidKubeVirtInfraNetworkMTU=False: KubeVirtSuboptimalMTUDetected(A suboptimal MTU size has been detected. Due to performance, we recommend setting an MTU of 9000 bytes or greater for the infra cluster that hosts the KubeVirt VirtualMachines. When smaller MTUs are used, the cluster will still operate, but network performance will be degraded due to fragmentation of the double encapsulation in OVN-Kubernetes.)

Correct. Azure does not support jumbo frames (as opposed to AWS).
I'm adjusting the test case.

/test e2e-kubevirt-azure-ovn

/test e2e-kubevirt-azure-ovn

/test e2e-kubevirt-azure-ovn

/test e2e-kubevirt-azure-ovn

/test e2e-kubevirt-azure-ovn

/test e2e-kubevirt-azure-ovn

/test e2e-kubevirt-azure-ovn

/test e2e-kubevirt-azure-ovn

/retest

/test e2e-kubevirt-azure-ovn

/test e2e-kubevirt-azure-ovn

/test e2e-kubevirt-azure-ovn

/test e2e-kubevirt-azure-ovn

/test e2e-kubevirt-azure-ovn

/test e2e-kubevirt-azure-ovn

capi-provider pod restarted due to leader election timeout:
E0407 12:59:37.747259       1 leaderelection.go:369] Failed to update lock: Put "https://<IP_ADDRESS>:443/apis/coordination.k8s.io/v1/namespaces/e2e-clusters-x9bxv-example-h25q8/leases/controller-leader-election-capk": context deadline exceeded
I0407 12:59:37.747323       1 leaderelection.go:285] failed to renew lease e2e-clusters-x9bxv-example-h25q8/controller-leader-election-capk: timed out waiting for the condition
E0407 12:59:37.747409       1 main.go:144] setup "msg"="problem running manager" "error"="leader election lost"

/test e2e-kubevirt-azure-ovn

/test e2e-kubevirt-azure-ovn

/test e2e-kubevirt-azure-ovn

/retest

/test e2e-kubevirt-azure-ovn

azure:
     util.go:766: pod control-plane-operator-9df575d6d-cj7kr over budget: budget: 4000, actual: 4009

/test e2e-kubevirt-azure-ovn

/test e2e-kubevirt-azure-ovn

/test e2e-kubevirt-azure-ovn

/test e2e-kubevirt-azure-ovn

/test e2e-kubevirt-azure-ovn

/test e2e-kubevirt-azure-ovn

https://github.com/openshift/release/pull/50797 is merged.
/test e2e-kubevirt-azure-ovn

/test e2e-kubevirt-azure-ovn

/retest
/test e2e-kubevirt-azure-ovn

RHTAP pipeline stuck
/close

/reopen

/test e2e-kubevirt-azure-ovn

/test e2e-kubevirt-azure-ovn

/retest

/test e2e-kubevirt-azure-ovn

odf installation failed
/test e2e-kubevirt-azure-ovn

/test e2e-kubevirt-azure-ovn

/hold

/test e2e-kubevirt-azure-ovn

/retest

/retest

/retest

/retest

/retest

/test e2e-kubevirt-azure-ovn

/test e2e-kubevirt-azure-ovn

/retest

/retest

/test e2e-kubevirt-azure-ovn

/unhold

/retest-required

/retest-required

/cherry-pick release-4.15


Template Fixes Futures - Baseball

retire old templates and add title property to template source
Use this title in the market list cards for SB
Which MLB team will win the [Year] [Event]?
Header: [Year] MLB [Event]
Title: Winner
Which MLB team will [Player] sign with?
Header: [Player] Free Agency
Title: Which MLB team will [Player] sign with
MLB: Who will win the [Year] [Award]?
Header: [Year] MLB [Award] award
Title: Winner

Still not correct


[R24.12] [Discovery Finder] [TRGs] QG 4 checks

QG checks
Please open and fill in this issue in your product repository to document the compliance with our Tractus-X Release Guideline (TRGs)
Show compliance with TRGs by referencing to a tagged link in the respective repository where possible, example: TRG 1.01 (see github.com/eclipse-tractusx/example-repo/tree/1.0.0/README.md)
Close this issue once the compliance with the TRGs has been documented
Committer(s):
Helm Chart Version: discoveryfinder-0.4.1
App Version: 0.5.1
Release Management Reference Issue:
Check of Tractus-X Release Guidelines

Currently implemented automatic checks can be found under your product on our Release Guidelines Checks Board
This QG Check is depending on the mandatory information from our current Release Guidelines

TRG 1 Documentation

[x] TRG 1.01 appropriate README.md
[x] TRG 1.02 appropriate install instructions either INSTALL.md or in README.md
[x] TRG 1.03 appropriate CHANGELOG.md
[x] TRG 1.04 editable static files
[ ] TRG 1.05 architecture docs
[ ] TRG 1.06 administrator guide
[x] TRG 1.07 user manual
[x] TRG 1.08 open api docs

TRG 2 Git

[x] TRG 2.01 default branch is named main
[x] TRG 2.03 repository structure
[x] TRG 2.04 leading product repository
[x] TRG 2.05 .tractusx metafile in a proper format
[x] TRG 2.06 Dependabot

TRG 3 Kubernetes

[x] TRG 3.02 persistent volume and persistent volume claim or database dependency (subchart) are in place when needed

TRG 4 Container

[ ] TRG 4.01 semantic versioning and tagging
[ ] TRG 4.02 base image is agreed
[ ] TRG 4.03 image has USER command and Non Root Container
[ ] TRG 4.05 released image must be placed in DockerHub, remove GHCR references
[ ] TRG 4.06 separate notice file for DockerHub has all necessary information
[ ] TRG 4.07 root file system is set to read access by default, but can be overwritten by the user -> https://github.com/eclipse-tractusx/sldt-discovery-finder/issues/156

TRG 5 Helm

[x] TRG 5.01 Helm chart requirements
[x] TRG 5.02 Helm chart location in /charts directory and correct structure
[x] TRG 5.03 proper version strategy
[x] TRG 5.04 CPU / MEM resource requests and limits and are properly set
[x] TRG 5.06 Application must be configurable through the Helm chart
[x] TRG 5.07 Dependencies are present and properly configured in the Chart.yaml
[x] TRG 5.08 Product has a single deployable helm chart that contains all components
[x] TRG 5.09 Helm Test running properly
[x] TRG 5.10 Products need to support 3 versions at a time
[x] TRG 5.11 Upgradeability

TRG 6 Released Helm Chart

[x] TRG 6.01 Released Helm Chart

TRG 7 Open Source Governance

[x] TRG 7.01 Legal Documentation
[x] TRG 7.02 License and copyright header
[x] TRG 7.03 IP checks for project content
[x] TRG 7.04 IP checks for 3rd party content
[x] TRG 7.05 Legal information for distributions
[x] TRG 7.06 Legal information for end user content
[x] TRG 7.07 Legal notice for documentation (non-code)
[x] TRG 7.08 Legal notice for KIT documentation

TRG 8 Security

[x] TRG 8.01 Mitigate high and above findings in CodeQL
[x] TRG 8.02 Mitigate high and above findings in KICS
[x] TRG 8.04 Mitigate high and above findings in Trivy
[x] TRG 8.03 No secret findings by GitGuardian or TruffleHog

TRG 9 UX/UI Styleguide

[x] TRG 9.01 UI consistency/styleguide for UI

Hints
Information Sharing

TRG 9 UX/UI Styleguide: Discoveryfinder is only a backend application without UI.


Update install-machine.md to reference 0.3.1

Update the docs to include links to newest release.

Ah, awesome, but you need to sign your commit

Not sure if I need to mention it, but I did sign the commit.

LGTM, thanks @jgeiger

Removed the specific version from the binaries link per @thaJeztah. I think this make sense since it's not a command you copy/paste.

Thanks @jgeiger !
ping @nathanleclaire for the merge (unless you need another "official" LGTM) :smile:

LGTM


All artistic style generation

Dear @ZeConloss
Thank you for your work. At the moment, when we pass --prompt_tgt style such as cubism it generates five images, here, my question is that how we can generate only one good quality cubism image not four images. How we can speedup image generation process? Are there any way to utilize all styles once like --prompt_tgt 'a sketch with crayon, cubism' . Is it possible?
Regards,
Khawar

In order to change the number of generated images, you can modify the --iterations_num from arguments.py.
I haven't experimented with style combinations yet. However, you can try using various prompts that incorporate different styles to achieve the desired results.


Lexer fix

Description
Turns out the new implementation of the lexer for the matching keyword was a bit too eager. Indeed, I now see that the PLY lexer docs state "You should avoid writing individual rules for reserved words. [If you do] those rules will be triggered for identifiers that include those words as a prefix such as “forget” or “printed”. This is probably not what you want."
This is breaking some tests on the solutions team so if approved in the morning before I start working, feel free to just trigger the merge tool.
Self Check:
Strike through any lines that are not applicable (~~line~~) then check the box

[ ] Attached issue to pull request
[ ] Changelog entry
[ ] Type annotations are present
[ ] Code is clear and sufficiently documented
[ ] No (preventable) type errors (check using make mypy or make mypy-diff)
[ ] Sufficient test cases (reproduces the bug/tests the requested feature)
[ ] Correct, in line with design
[ ] End user documentation is included or an issue is created for end-user documentation (add ref to issue here: )
[ ] If this PR fixes a race condition in the test suite, also push the fix to the relevant stable branche(s) (see test-fixes for more info)

Processing this pull request

Merged into branches iso7, master in ef497bf3c33d9fac3b3dec6b008d509877cbf438


Simplify relation users

Proposal
Simplify relation users in line with the spec. Requirer charms now need to send either "admin" or "default" to receive relevant permissions.
Context

These permissions are a first draft, but require focus when reviewing.

Opensearch Permissions Docs

Release Notes

Simplify user creation to two values
Updated tests.

Testing

Unit tests have been updated to match the new user permissions
Integration tests have been updated and expanded to test the new user permissions don't allow default or admin users to update or delete opensearch security index

To summarize the flow.
What do we need to protected:
1- internal indices (list), mainly for now: .opendistro_security, here is a (non?) exhaustive list:
[".opendistro_security", ".opendistro-alerting-config", ".opendistro-alerting-alert*", ".opendistro-anomaly-results*", ".opendistro-anomaly-detector*", ".opendistro-anomaly-checkpoints", ".opendistro-anomaly-detection-state"]

The access to the security rest API

To be tested:

Try to delete .opendistro_security by an admin client, if not possible => perfect. If possible => see the section below "1."
Try to delete an internal user using the rest API, if not possible => perfect. If possible => see the section below "2."

How to protect these?
1. internal indices:
a. in your permission, you could try to exclude by pattern `.opendistro*` or list them all in case the internal indices may break this pattern
b. on client relation joined, if index name passed (i.e for non admin users), check the requested index against this list and fail if it's one of the internal ones.

2. Access to security rest api:
On cluster initialization (where we initialize the admin user and security index)

create 2 roles:
a. client-role
b. client-admin-role which inherits from the admin role.

in opensearch.yml exclude these 2 roles from ever interacting with the security API: (refer to the docs here)
 # for the client role:
plugins.security.restapi.endpoints_disabled.client-role.ROLES: ["PUT", "POST", "DELETE", "PATCH"]
plugins.security.restapi.endpoints_disabled.client-role.INTERNALUSERS: ["PUT", "POST", "DELETE", "PATCH"]

# for the client-admin-role
plugins.security.restapi.endpoints_disabled.client-admin-role.ROLES: ["PUT", "POST", "DELETE", "PATCH"]
plugins.security.restapi.endpoints_disabled.client-admin-role.INTERNALUSERS: ["PUT", "POST", "DELETE", "PATCH"]

For each new client:
a. when relation joining, create a user mapping with the corresponding role (regular user => client-role and admin user => client-admin-role)
b. when relation broken, delete the user mapping

Note: with this, you probably don't need to set user permissions for client admin users.

NB I've commented out HA tests for now, because I wanted to get this feature in, but I'm working on them now in this ticket


xp.apple.com

"It seems to be related to the app store and os updates. All my apple devices attempt to connect to it during updates."
https://apple.stackexchange.com/questions/372241/what-is-the-host-xp-apple-com-for-and-what-is-sent-there
This is a domain that appears exclusively on your blocklist out of my 350+ blocklists. Where did you pull this domain from? (Just curious). If you'd like the link to my list of other blocklists for your validation, happy to share.

Sorry, I think I posted this one on the wrong blocklist.


Added support for Lambda operations

Added test and updated readme

Coverage increased (+0.006%) to 99.677% when pulling f486afe18fff929ebc138b49c0abcc691b900da6 on subpx:master into ee0db371e8d763ced20603257a269d2b4ca0e470 on devnixs:master.

Should probably remove that console.log?

Done. Thanks

Coverage increased (+0.006%) to 99.677% when pulling 8682d5217808b44f8a7b73f71083d96c8c43bd5e on subpx:master into ee0db371e8d763ced20603257a269d2b4ca0e470 on devnixs:master.

I think a lot of people have been waiting for that feature.
Thanks!


API not indexed by search engines

Describe the annoyance
Right now it seems nearly impossible to find direct links to the Python API with google / bing / etc.
Haven't done any testing for the Rust API.
To Reproduce
Some search terms that would not come up with anything:
rerun log_image, rerun log_image python api, rerun python api, ...
Typically the docs.rerun.io pages show up, however, direct links to ref.rerun.io seem quite difficult to find.

Seems like #2404 helped, as Google now reports that the live URL is indexable. We're just waiting on it to actually crawl and index the pages now.

googling "site:ref.rerun.io" is now giveing nine hits! So some progress :)

I'm only seeing 8 now 🤔


Remove hostname redirect check

This code redirects requests to the 'canonical hostname'. It was implemented in 2019 when it appears there were some publicly accessible Azure URLs  causing problems. In production, it also redirected all requests to www. if this was not prefixed on the request URL.
With the new DNS changes it has now been possible to implement this at the infrastructure level and so this code is now redundant.

Please also remove the associated terraform to set this environment variable if it's no longer used, e.g. https://github.com/DFE-Digital/claim-additional-payments-for-teaching/blob/master/terraform/application/config/production.tfvars.json#L6

Checked with @saliceti and confirmed this can't be removed.


Code in README.md does not work. Error: TypeError: Do not know how to serialize a BigInt

I tried the code in the README.md file, but it's failing when the data is received. This is the error:
file:///Users/aperez/Git%20Projects/current/ARC101/2024/grpc/node_modules/salesforce-pubsub-api-client/dist/client.js:825
              const parseError = new EventParseError(
                                 ^

EventParseError: Failed to parse event with replay ID 113730
    at file:///Users/aperez/Git%20Projects/current/ARC101/2024/grpc/node_modules/salesforce-pubsub-api-client/dist/client.js:825:34
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
Emitted 'error' event on PubSubEventEmitter instance at:
    at PubSubEventEmitter.emit (file:///Users/aperez/Git%20Projects/current/ARC101/2024/grpc/node_modules/salesforce-pubsub-api-client/dist/client.js:147:18)
    at file:///Users/aperez/Git%20Projects/current/ARC101/2024/grpc/node_modules/salesforce-pubsub-api-client/dist/client.js:832:28
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
  cause: TypeError: Do not know how to serialize a BigInt
      at JSON.stringify (<anonymous>)
      at PubSubEventEmitter.<anonymous> (file:///Users/aperez/Git%20Projects/current/ARC101/2024/grpc/greeter_client.js:21:21)
      at PubSubEventEmitter.emit (node:events:518:28)
      at PubSubEventEmitter.emit (file:///Users/aperez/Git%20Projects/current/ARC101/2024/grpc/node_modules/salesforce-pubsub-api-client/dist/client.js:147:18)
      at file:///Users/aperez/Git%20Projects/current/ARC101/2024/grpc/node_modules/salesforce-pubsub-api-client/dist/client.js:817:28
      at process.processTicksAndRejections (node:internal/process/task_queues:95:5),
  replayId: 113730,
  event: {
    event: {
      id: 'd9e6521b-8e49-427c-9f8b-4cc5dd3c6070',
      schemaId: 'fvNi01PVr47z-BJWOS24fw',
      payload: Buffer(309) [Uint8Array] [
         14,  65,  99,  99, 111, 117, 110, 116,   2,  36,  48,  48,
         49,  79,  50,  48,  48,  48,  48,  48,  68,  87, 115,  86,
        100,  73,  65,  76,   0,   0,  86,  99, 111, 109,  47, 115,
         97, 108, 101, 115, 102, 111, 114,  99, 101,  47,  97, 112,
        105,  47, 114, 101, 115, 116,  47,  54,  49,  46,  48,  59,
         99, 108, 105, 101, 110, 116,  61, 112, 111, 115, 116, 109,
         97, 110,  72,  48,  48,  48,  48,  54,  55, 102,  99,  45,
         57,  51,  52,  48,  45,  53,  98,  99,  51,  45, 102, 100,
         53,  49,  45,  51,
        ... 209 more items
      ]
    },
    replayId: Buffer(10) [Uint8Array] [
      0,   0,  0, 0, 0,
      1, 188, 66, 0, 0
    ]
  },
  latestReplayId: 113730
}

Node.js v20.12.2

I noticed that changing this line
console.log(JSON.stringify(event, null, 2));
To this line
console.log(event);
Seems to work fine, and there is no error!

Hi @eltoroit, this is in fact not a bug from the client but an issue with BigInt JSON representation in standard JS.
You can certainly use console.log(event) if you don't care about formatting and indentation. However, if you want a nice output, you need to use JSON.stringify with some extra parameters like so:
// Safely log event as a JSON string
console.log(
    JSON.stringify(
        event,
        (key, value) =>
            /* Convert BigInt values into strings and keep other types unchanged */
            typeof value === 'bigint' ? value.toString() : value,
        2
    )
);

I've updated the doc example and added a note explaining what's going on (pretty crazy IMO).


MQTT features

clarify QoS parameters as well as retention for brokers (WIS2 Node/Broker, Global Broker).

Agree,
Cheers,
Hassan

From: Tom Kralidis @.>
Sent: Thursday, September 28, 2023 16:14
To: wmo-im/wis2-guide @.>
Cc: Hassan Haddouch @.>; Mention @.>
Subject: Re: [wmo-im/wis2-guide] MQTT features (Issue #37)
@hhaddouchhttps://github.com/hhaddouch I think this is a duplicate of #5https://github.com/wmo-im/wis2-guide/issues/5? Should we close?
—
Reply to this email directly, view it on GitHubhttps://github.com/wmo-im/wis2-guide/issues/37#issuecomment-1739318505, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AYVCAKQBSYQYT7R5B6JDQY3X4WA25ANCNFSM6AAAAAA452MXMM.
You are receiving this because you were mentioned.Message ID: @.***>


WIP: Try different test for popup skipif mark

Description
I am a bit unhappy that we had to use the deprecated string input to pytest.mark.skipif in #1807, so I'm opening this branch to experiment with a few options on the CI.
Type of change

[ ] Bug-fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

References

How has this been tested?

[ ] example: the test suite for my feature covers cases x, y, and z
[ ] example: all tests pass with my change

Final checklist:

[ ] My PR is the minimum possible work for the desired functionality
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works

Ok as e734313 shows, indeed switching to a string is sufficient to fix things! The mind boggles. I'm going to try one more thing before submitting a bug report to pytest...

Boom. Looks like CI is set to true, not 1, and through some dark magic this confused pytest. Explicitly checking the CI value fixes things! :tada:

Ok @napari/core-devs this is ready to merge imho! I'll also raise an issue in pytest because this is weird-as.

Ok thanks to the help of the pytest devs over at pytest-dev/pytest#7999, I finally figured out that this is why this was happening:
>>> True and 'hello'
'hello'

:facepalm: This is the same Python magic that enables the syntax:
var = input_var or DEFAULT

which I used to like but now I think it's dangerous hubris. :joy:


[testing] Add missing REQUIRES: standalone_test

@swift-ci please smoke test and merge

I see no standalone_test defined anywhere, did you mean standalone_build?

I see no standalone_test defined anywhere, did you mean standalone_build?

Whoops. Yes. Sorry!

Do you have a pull request ready? Or do you need me to fix it?

Also, since standalone_build is defined in test/lit.site.cfg.in, will it be passed to these validation tests? Could you explain what this requirement signifies?

There are two fundamental ways of building Swift:

As a standalone project using pre-built LLVM/clang libraries (and headers) available somewhere.
As a "unified build" where LLVM, clang, swift, etc are built together and build dependencies are integrated.

"standalone_build" means the former.

Is the "unified build" ever built on the CI? If not, adding this requirement simply disables all these tests from the CI.

As of today, CI doesn't do unified builds.
But that doesn't matter. This test is effectively always disabled when it shouldn't be.

I ask because one of these tests should have tripped because of my pull #32860, but it didn't. I'll fix this, but I'm not sure how if the test is never run even with standalone_build.

I'll look into the CMake config for unified builds more and get back to you later. I thought the CI is doing unified builds, based on your description, but I'm not sure so I will check.
Let me know about that lit.site.cfg.in issue I mentioned above, whenever you get a chance.

 This makes it easy to build LLVM+clang optimized but with Swift unoptimized.
People that build "unified" are bypassing the build-script entirely

I neglected to make clear that all the standalone_build tests you added appear to be disabled on the CI, not just these two with the wrong label. I downloaded the full CI log for the last successful smoke test from last night and checked, hence my confusion and further questions.
It appears there's something further wrong in the test setup than this pull and since you added that requirement, maybe you have some insight.

OK, I think I have a fix for both problems, will submit a pull.


Control concurrency and add retry action in decommission flow

Description
TBA [Depends on #5093]
Issues Resolved
[List any issues this PR will resolve]
Check List

[ ] New functionality includes testing.

[ ] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[ ] Commits are signed per the DCO using --signoff
[ ] Commit changes are listed out in CHANGELOG.md file (See: Changelog)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Closing as opened a new one - https://github.com/opensearch-project/OpenSearch/pull/5542


Add instructions on how to SSH into AWS

We could also add a note about being able to proxy straight into specific nodes. I have SSH config similar to:
Host *.aws.integration
  ProxyCommand ssh -e none<EMAIL_ADDRESS>-W $(echo %h | sed 's/\.aws.integration$//'):%p

When using Icinga and can get a specific hostname, it's easier to use this proxy method:
ssh ip-1-2-3-4.eu-west-1.compute.internal.aws.integration


python3Packages.volkszaehler: init at 0.2.0

Motivation for this change
Python Wrapper for interacting with the Volkszahler API
https://github.com/home-assistant-ecosystem/python-volkszaehler
This is a Home Assistant dependency.
Things done

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

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

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

This is a semi-automatic executed nixpkgs-review. If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 108149 run on x86_64-linux 1

3 packages built:

python37Packages.volkszaehler
python38Packages.volkszaehler
python39Packages.volkszaehler

This is a semi-automatic executed nixpkgs-review. If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 108149 run on x86_64-linux 1

3 packages built:

python37Packages.volkszaehler
python38Packages.volkszaehler
python39Packages.volkszaehler

@GrahamcOfBorg build python3Packages.volkszaehler

@GrahamcOfBorg build python3Packages.volkszaehler


Make kedro-telemetry opt-in flow default to "skip" in non-interactive environments

Description
Over the years, users have reported that under some circumstances the telemetry prompt gets stuck. For example:

CI/CD (example TBC)
Databricks https://github.com/kedro-org/kedro/issues/1640#issuecomment-1850484688

In some other circumstances it does not block, for example in Docker images https://github.com/kedro-org/kedro/issues/1640#issuecomment-1602119633
Context
This is important because the current workarounds to opt in/out for the telemetry are finicky. For example, it's not always easy to know in which directory should Databricks Jobs create the .telemetry file https://github.com/kedro-org/kedro/issues/1640#issuecomment-1852613950

We got reports from another user that kedro-telemetry blocks Kedro runs on Amazon EMR

We're moving towards removing the interactive flow altogether. Will close this when the full roadmap is ready.

Closing this already.


perf(CacheAccount): remove unneeded clone

Found it in the hot path here:

test failing not related


update documentation to make it more easy for customers to understand

can this term "myACRId" be updated to "mynewID" or something like this, so customers doesnt go for the ACR ID, meaning resource ID?
in the section "Deploy in a virtual network using the Azure CLI"
the command states:
az container create --name my-containergroup --resource-group myResourceGroup --image /hello-world:v1 --acr-identity $userID --assign-identity $userID --vnet "/subscriptions/$SUBSCRIPTION_ID/resourceGroups/"/subscriptions/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxxx/resourceGroups/myVNetResourceGroup/providers/ --subnet mySubnetName
can this " --vnet "/subscriptions/$SUBSCRIPTION_ID/resourceGroups/"/subscriptions/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxxx/resourceGroups/myVNetResourceGroup/providers/ "  be changed for something like this " --vnet " "

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

ID: d7e900ff-163f-b325-827d-4340e8901cd2
Version Independent ID: d21f588f-eff8-0c9b-d44f-1842fa5f3922
Content: Deploy container image from Azure Container Registry using a managed identity - Azure Container Instances
Content Source: articles/container-instances/using-azure-container-registry-mi.md
Service: container-instances
GitHub Login: @tomvcassidy
Microsoft Alias: tomcassidy

@porrascarlos802018
Thanks for your feedback! We will investigate and update as appropriate.

@tomVcass
Can you add your inputs on the above update regarding document.

@porrascarlos802018 Thanks for the suggestion on the myACRid. That is a little confusing. I'll make that change.
Could you elaborate on why you want the --vnet change? I think the current format is just trying to show what the input should look like. Did you find it confusing?

Thanks for your contribution to our documentation
We sincerely apologize for the delayed response. Unfortunately, we have been unable to review this issue in a timely manner. However, we are making overall enhancements to our content. We are closing this issue for now as there has been no activity for a while. If you feel that the problem persists, please respond to this issue with additional information.
?
Please continue to provide feedback about the documentation. We appreciate your contributions to our community.
#please-close


Refactor docs directory

Per comment https://github.com/tensorflow/addons/pull/2160#discussion_r487230647, better to move these stuff out of docs.

[ ] Move build tools to tools/docs
[ ] Modify related documentation

can i take this up?

@seanpmorgan there seems to be two tasks in this issue, You can assign both of us one task or howsoever you deem fit. I would also like to work on this.

@seanpmorgan there seems to be two tasks in this issue, You can assign both of us one task or howsoever you deem fit. I would also like to work on this.

Hi @hp77-creator the two tasks should probably be done in the same PR. Since you've started with #2167 please feel free to add another commit on that branch

Hi @seanpmorgan, I am not sure as to what I have to do in the documentation. Can you specify what I should write? I also reviewed the failed check of my pull request, there it said
#18 0.454 python: can't open file 'docs/build_docs.py': [Errno 2] No such file or directory

So should I keep a copy of build_docs.py in docs to pass this check or do I have to modify any tests too?

@hp77-creator you have to remove build_docs.py from BUILD. You would also have to update the README.md to reflect your changes.

@Harsh188 Removing build_docs.py from BUILD is leading to more fails in CI tests. I tried with updating readme with the correct paths but still of no use. Can you have a look at the PR?


Update README for loading plugin

// Install the plugin
.plugin('aurelia-bs-modal');

should be
// Install the plugin
.plugin('pwkad/aurelia-bs-modal');

This actually depends on how you jspm install it.  I thought I had fixed that to jspm install aurelia-bs-modal but apparently I didn't.  Will update that instead, thanks for the heads up.


Release 0.3a

Coverage remained the same at 97.436% when pulling 6e1544623bd0ff2635a9d5664b9996b197ecca29 on release-0.3a into 7e415ea3923c11f2e158f5e517454f0ef2fef6ff on master.

Coverage remained the same at 97.436% when pulling 6e1544623bd0ff2635a9d5664b9996b197ecca29 on release-0.3a into 7e415ea3923c11f2e158f5e517454f0ef2fef6ff on master.


Expose some http client ssl opts via HTTP_CLIENT_SSL_OPTS

Expose the most commonly-used SSL client options to our OIDC and ConnectivityChecks HTTP clients. Resolves some lingering issues some users were facing with OIDC where they needed a custom TLS version enforced or cacert file used to fetch the discovery_document and resulting keys.
SSL misconfiguration can be a security concern, so we intentionally puke when an unexpected key is passed. This should result in a new GitHub issue being opened and dialog created to learn more about the use-case.
Fixes #996

Pull Request Test Coverage Report for Build 043a1d60591c56e300bbd995f0eedf3439443c2c-PR-1221

6 of 6 (100.0%)  changed or added relevant lines in 2 files are covered.
8 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.3%) to 66.79%

Files with Coverage Reduction
New Missed Lines
%

apps/fz_http/lib/fz_http/connectivity_check_service.ex
8
62.5%

Totals

Change from base Build 791b180ff6151daee80f88098f7e2c263edb77e6-PR-1155:
-0.3%

Covered Lines:
1261

Relevant Lines:
1888

💛  - Coveralls

Will rebase after #1155 is merged.

@AndrewDryga Ready for a quick peek when you a chance.


Spike: Validate XPU manager on NUC (igpu only system) and potentially remove IGT

[x] Verify if we have the coverage we need with XPU and can remove IGT
[x] Document impacts of removing IGT (code modifications)

Learned the opposite was true. XPU Manager will only work with the Flex datacenter devices while IGT will work for all intel GPUs. This will require some modification to the GPU query function and functionality is limited with the Flex datacenter GPUs.


[BUG] test_str_to_map_expr_random_delimiters with DATAGEN_SEED=1702166057 hangs

Describe the bug
I was able to reproduce this locally on Spark 3.3.0
SPARK_HOME=spark_3.3.0/ TEST_PARALLEL=0 PYSP_TEST_spark_rapids_sql_explain=ALL DATAGEN_SEED=1702166057 TZ=UTC ./run_pyspark_from_build.sh --test_oom_injection_mode=always -k 'test_str_to_map_expr_random_delimiters' -s

and git version ff190124611e73fcf63a2c2948a9d510ae2f6b3b
It appears to hang in python. No queries were submitted to Spark, from what I could see.
When I tried to use gdb on it I got some great stack traces, but they were all in C, in what appeared to be creating error messages, and I ma not enough of a python expert to really dig into what is happening here.

The test hangs because the test has a bug in it:
    while pair_delim == keyval_delim:
        (pair_delim, keyval_delim) = with_cpu_session(
            lambda spark: gen_scalars_for_sql(delim_gen, 2, force_no_nulls=True))

The data generation will reset the generator to the beginning each time, so if it happened to generate two identical scalars it will infinitely loop.