Error of mis-matched datums in ASP 3.4 when running stereo on map-projected Galileo SSI images

Describe the bug
Running parallel_stereo on lev-2 map-projected Galileo SSI cubes of Europa results in an error of mis-matched datums, possibly related to the presence of two conflicting datums, D_Europa, and D_EUROPA, with different semi-axes. The error occurs during the pre-processing stage.
To Reproduce
Steps to reproduce the behavior:
ISIS
Process Galileo SSI images 5000r and 7535r. These two form a valid stereopair which has been analysed in various works. Suggested commands: gllssi2isis, spiceinit (cksmithed=yes), gllssical, cam2map (using consistent parameters).
map projection:
ProjectionName     = SimpleCylindrical
CenterLongitude    = 180.0
TargetName         = Europa
EquatorialRadius   = 1560800
PolarRadius        = 1560800
LatitudeType       = Planetocentric
LongitudeDirection = PositiveEast
LongitudeDomain    = 360
ASP
parallel_stereo --alignment-method none --stereo-algorithm asp_mgm --subpixel-mode 2 [image1] [image2] [output_path]
bundle_adjustment not performed as images have already been corrected (see Bland et al., 2021 A, B).
The error only occurs using mapprojected images. Using properly processed lev-1 images, the error does not occur and parallel_stereo is run successfuly.
Additionally, the error does not occur running parallel_stereo on previous versions of ASP, including ASP 3.3.
Expected behavior
The point cloud should be generated, as it is the case using lev-1 images or previous ASP versions (either with lev-1 or mapprojected images in the latter case). Datum should be D_Europa (1560800 m), as that is the one used for map-projecting.
Error Logs, Terminal Captures, Screenshots
ERROR: Found mis-matched datums. The difference in semi-axes is: 650 meters.
Datum 1: Geodetic Datum --> Name: D_Europa  Spheroid: Europa  Semi-major axis: 1560800  Semi-minor axis: 1560800  Meridian: Reference_Meridian at 0  Proj4 Str: +proj=longlat +R=1560800 +no_defs
Datum 2: Geodetic Datum --> Name: D_EUROPA  Spheroid: EUROPA  Semi-major axis: 1561450  Semi-minor axis: 1561450  Meridian: Reference Meridian at 0  Proj4 Str: +proj=longlat +R=1561450 +no_defs
Complete logs attached
log_failed_stereo_ASP3.4_lev2.txt
log_stereo_commands.txt
Your Environment

WSL 2 (v<IP_ADDRESS>) with Ubuntu 24.04
ASP Version: 3.4.0-2024-06-19-x86_64-Linux. Tested successfully on StereoPipeline-3.3.0-Linux.

Additional context

I wonder if you can try the latest build. At some point I made this into a
warning, and it will be an error only if the difference in datums is 200
km, which is way more than what you see here. The latest build is at:
https://github.com/NeoGeographyToolkit/StereoPipeline/releases
On Fri, Dec 6, 2024 at 3:23 AM gianluca-ch @.***> wrote:

Describe the bug
Running parallel_stereo on lev-2 map-projected Galileo SSI cubes of Europa
results in an error of mis-matched datums, possibly related to the presence
of two conflicting datums, D_Europa, and D_EUROPA, with different
semi-axes. The error occurs during the pre-processing stage.
To Reproduce
Steps to reproduce the behavior:
ISIS
Process Galileo SSI images 5000r and 7535r. These two form a valid
stereopair which has been analysed in various works. Suggested commands:
gllssi2isis, spiceinit (cksmithed=yes), gllssical, cam2map (using
consistent parameters).
map projection:
ProjectionName = SimpleCylindrical
CenterLongitude = 180.0
TargetName = Europa
EquatorialRadius = 1560800
PolarRadius = 1560800
LatitudeType = Planetocentric
LongitudeDirection = PositiveEast
LongitudeDomain = 360
ASP
parallel_stereo --alignment-method none --stereo-algorithm asp_mgm
--subpixel-mode 2 [image1] [image2] [output_path]
bundle_adjustment not performed as images have already been corrected (see
Bland et al., 2021 A, B).
The error only occurs using mapprojected images. Using properly processed
lev-1 images, the error does not occur and parallel_stereo is run
successfuly.
Additionally, the error does not occur running parallel_stereo on previous
versions of ASP, including ASP 3.3.
Expected behavior
point cloud should be generated, as it is the case using lev-1 images or
previous ASP versions (both with lev-1 and mapprojected images in the
latter case)
Error Logs, Terminal Captures, Screenshots
ERROR: Found mis-matched datums. The difference in semi-axes is: 650
meters.
Datum 1: Geodetic Datum --> Name: D_Europa Spheroid: Europa Semi-major
axis: 1560800 Semi-minor axis: 1560800 Meridian: Reference_Meridian at 0
Proj4 Str: +proj=longlat +R=1560800 +no_defs
Datum 2: Geodetic Datum --> Name: D_EUROPA Spheroid: EUROPA Semi-major
axis: 1561450 Semi-minor axis: 1561450 Meridian: Reference Meridian at 0
Proj4 Str: +proj=longlat +R=1561450 +no_defs
Complete logs attached
log_failed_stereo_ASP3.4_lev2.txt
https://github.com/user-attachments/files/18037482/log_failed_stereo_ASP3.4_lev2.txt
log_stereo_commands.txt
https://github.com/user-attachments/files/18037483/log_stereo_commands.txt
Your Environment

WSL 2 (v<IP_ADDRESS>) with Ubuntu 24.04
ASP Version: 3.4.0-2024-06-19-x86_64-Linux. Tested successfully on
StereoPipeline-3.3.0-Linux.

Additional context
—
Reply to this email directly, view it on GitHub
https://github.com/NeoGeographyToolkit/StereoPipeline/issues/445, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAKDU3DVEBVQT6HGPJ6IEYL2EGCM3AVCNFSM6AAAAABTEO25NWVHI2DSMVQWIX3LMV43ASLTON2WKOZSG4ZDENZXHA2DQMA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

HI Oleg, thank you for replying so quickly.
I tried with the latest build (StereoPipeline-3.5.0-alpha-2024-12-05-x86_64-Linux) and it worked successfully, despite numerous warnings similar to those reported with ASP 3.4 (you can check the log for additional info)
log_parallel_sterep_ASP-3.5.txt
Typical warnings are:

It appears that the input images are map-projected. In that case a DEM needs to be provided for stereo to give correct results.
Found mis-matched datums. The difference in semi-axes is: 650 meters.
Datum 1: Geodetic Datum --> Name: D_Europa  Spheroid: Europa  Semi-major axis: 1560800  Semi-minor axis: 1560800  Meridian: Reference_Meridian at 0  Proj4 Str: +proj=longlat +R=1560800 +no_defs
Datum 2: Geodetic Datum --> Name: D_EUROPA  Spheroid: EUROPA  Semi-major axis: 1561450  Semi-minor axis: 1561450  Meridian: Reference Meridian at 0  Proj4 Str: +proj=longlat +R=1561450 +no_defs
This is likely harmless, but check your inputs.

Thank you.
Gianluca

The parallel_stereo program calls many sub-processes, with each printing out these warnings. I now made sure the warning shows up only for the main processes (pprc, corr, etc) and not for auxiliary processes that do things under the hood.
So the warnings will be quite a bit less, but will still show up for each tile being processed in parallel in correlation and triangulation, for example. Should be an improvement.


Added logging redirect to evmserver script.

During the update process evmserver.sh update_start is called from
within a yum posttrans and yum's parent process has already been killed as
a part of server shutdown.
This caused the rake task started by evmserver to be killed when
attempting to write to stdout or stderr.
For this reason the redirect was added for rake tasks in evmserver.sh
that are called during an update.
https://bugzilla.redhat.com/show_bug.cgi?id=1239035

:+1:  LGTM

@jrafanie Please review

Wow, seems easy ;-)


[pdqtest-2.0] - tweak PDK integration to avoid churn

From slack chat on puppet #testing:
create  Gemfile.project and then in Makefile and make.ps1 copy it over to Gemfile.local. When these scripts run, die with an error if Gemfile.local already exists with different content otherwise proceed to bundle exec.... To get the initial set of files, do pdk new module --skip-interview in a tempdir and copy the files I want during pdqtest init. pdqtest init will also drop a .sync.yml to prevent pdk update clobbering integrations in .travis.yml and bitbucket-pipelines.yml ...  get vanilla PDK files when you do pdk new module and your not wanting to use PDQTest.
Also if the Gemfile already exits on a project created with PDK, just leave it alone and never touch it

fixed in 1.9.9beta


Update snowflake.md with pointer to IP address range

Update snowflake.md with pointer to IP address range

🚀 Deployed on https://64b19bdfee9bac008070051b--cozy-fox-0defec.netlify.app


Cannot build the image with runc 1.0.3-2.amzn2

What happened:
I have tried to build the image with packages versions as stated in last the changelog. Mainly with runc 1.0.3
What you expected to happen:
Successful image build.
How to reproduce it (as minimally and precisely as possible):

Use 1.0.3-2.amzn2 as runc version.
Build the image as stated in the readme.

Anything else we need to know?:
Log from the make:
...
    amazon-ebs: No package runc-1.0.3-2.amzn2 available.
    amazon-ebs: Error: Nothing to do
...

If I boot the instance with v20220406 image package comes from 'somewhere' though:
$ yum info runc
Loaded plugins: priorities, update-motd, versionlock
Installed Packages
Name        : runc
Arch        : x86_64
Version     : 1.0.3
Release     : 2.amzn2
Size        : 11 M
Repo        : installed
Summary     : CLI tool for spawning and running containers according to the OCI specification
License     : Apache 2.0 and MIT
Description : runc is a command line client for running applications packaged according to
            : the Open Container Initiative (OCI) format and is a compliant implementation of the
            : Open Container Initiative specification.

Environment:

AWS Region: us-east-1
Instance Type(s): n/a
EKS Platform version (use aws eks describe-cluster --name <name> --query cluster.platformVersion): eks.7
Kubernetes version (use aws eks describe-cluster --name <name> --query cluster.version): 1.19
AMI Version: n/a
Kernel (e.g. uname -a): n/a
Release information (run cat /etc/eks/release on a node): n/a

Hi, EKS has used internally available artifacts to build this AMI. We are working with Amazon Linux to push these artifacts upstream so we can make these changes to the builder scripts as well. We'll keep this issue open, and provide an ETA once we have one.

PR to fix this has been merged


Enforce unique test names using eslint

Let's see if we can enforce unique test names using a custom eslint rule. I'd suggest that we aim for unique names within a describe clause.
Originally posted by @garrytrinder in https://github.com/pnp/cli-microsoft365/issues/4123#issuecomment-1321202368

If you're using the Mocha Test explorer, you'll see duplicated tests highlighted with a warning icon. I picked out two of those last week when fixing some tests.

We could make use of the package eslint-plugin-mocha for this scenario. They have a specific rule no-identical-title that fits this scenario perfectly 😄

Great research @Jwaegebaert 👍🏻 That's sounds perfect.

I can pick this up then, if that's alright for everybody.

All yours @Jwaegebaert 👍🏻


An export button is added and .svg export is supporte

An export button is added that gives the user the option of exporting the figure of the network in the already exisiting .pdf format and newly added .svg format. This will close #3.

A separate export button is added, so the issue #3 is closed by merging this pull request.


typo: specification/azure-kusto/resource-manager/Microsoft.Kusto/stable/2019-01-21/kusto.json

Repersents -> Represents
properiets -> properties

Can one of the admins verify this patch?

Automation for azure-sdk-for-java

Automation for azure-sdk-for-node


Added a Few Scripts + A Library Script

This pull request has two parts:

9 scripts
Start of a reusable function library

Specifically, please check that pitch_entry_double_octave_down.lua and pitch_entry_double_octave_up.lua work.
These two scripts use library.lua for the helper function change_octave. These scripts work fine on my setup and theoretically should work wherever the local git repo is. But if you could check to see if the scripts work, that would validate that the import process isn't specific to my machine.
P.S. The function library is a JW Lua file that can house many common functions. That way, we can reuse previously written code for newer JW Lua scripts, speeding up development time, removing duplicate code, and lowering the barrier to entry for JW Lua.

An alternative would be to create a library folder and add library functions to it in individual .lua script files. That would allow us to pick and choose the library functions we needed.

I like the idea of having a library folder with several individual scripts. Let's do that!


Show total score on scoring.html

Easy to do, just use the formula
Good to have because live feedback to the scorer


chore: export type definitions react components

closes https://github.com/tailwindlabs/heroicons/issues/64

Is there still appetite for shipping this change?

Hey @9renpoto. Sorry for missing this when you first opened it! We have since added type declarations for the components so I'm going to close this. I appreciate you taking the time to put this together though!


feat: primary theme for site with vendor prefix

Related Issue
Closes: #894
Changes made 👷🏻♂

Introduced navigation bar theme facility with vendor prefixes, this ensures to perform for all devices like mac, windows & android as we expected.
The primary color #E26959 is used as Primary theme.
This feature has various advantages some of them are below,

Consistent branding across devices and platforms.
Enhanced user experience tailored to different devices.
Visual appeal and standout appearance.

Screenshots  📸

Please review this PR @tamalCodes.

Please review this PR @tamalCodes.


error on page : https://react-query.tanstack.com/examples/nextjs  needs "web-streams-polyfill " in codesandbox for Ky to work...

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to 'https://react-query.tanstack.com/examples/nextjs'
Click on 'Nextjs SSG'
Scroll down to '....'
502 Bad Gateaway

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g.Linux]
Browser: [e.g. chrome]
Version: [e.g. 22]

Additional context
Although I am quite a newbie, i saw that we could resolve the bad Gate Away 502 is for "Ky" by adding this dependency to the Dependencies listing:
npm install web-streams-polyfill --save
as per https://www.npmjs.com/package/ky-universal  instructions.
then the whole thing works just fine.
Yours,
Marc

very good find. would you like to PR that please?

Hello Dominik,
As i said, I am quite a newbie and have no idea about your "PR" request
proposal.   Hope I could help you with this, but sincerely I have no clue
about what your are saying.
Keep on the good work and thank you so much for your good work,
Marc
On Wed, Apr 14, 2021 at 5:22 PM Dominik Dorfmeister <
@.***> wrote:

very good find. would you like to PR that please?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/tannerlinsley/react-query/issues/2122#issuecomment-819603862,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APLLEUUKCGQIUUSOAPROR2DTIWXMPANCNFSM425TBCNQ
.

okay, no worries. So the way open source works is that everyone can contribute. To do that, you need to fork the repository to your own account (top right button in github), then create a branch. You can then implement the fix, in this case it's just adding that dependency to package.json in the example. After that, you can make a PR (pull request) from your branch to this repository - just go to the Pull Requests tab here and click on New Pull Request.
make sure to adhere to the commit message convention, you can read about it here: https://github.com/tannerlinsley/react-query/blob/master/CONTRIBUTING.md#commit-message-conventions

I think this is a good first issue if you want to get started with contributing to open source :)

Wow thanks...I ll look into on Monday...
Le jeu. 15 avr. 2021 à 09:58, Dominik Dorfmeister @.***>
a écrit :

okay, no worries. So the way open source works is that everyone can
contribute. To do that, you need to fork the repository to your own account
(top right button in github), then create a branch. You can then implement
the fix, in this case it's just adding that dependency to package.json in
the example. After that, you can make a PR (pull request) from your branch
to this repository - just go to the Pull Requests tab here and click on New
Pull Request.
make sure to adhere to the commit message convention, you can read about
it here:
https://github.com/tannerlinsley/react-query/blob/master/CONTRIBUTING.md#commit-message-conventions
I think this is a good first issue if you want to get started with
contributing to open source :)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/tannerlinsley/react-query/issues/2122#issuecomment-820209032,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APLLEUXBFK3AIWYRKVQW23LTI2MBVANCNFSM425TBCNQ
.

hey, for some reason the CodeSandbox example is now entirely missing from the Next.js example page.

Not sure what you mean - it’s still here: https://react-query.tanstack.com/examples/nextjs

yeah, now it's there. sorry for a false ping then. 12 hours ago the CodeSandbox threw an error that said that the example did not exist...

:tada: This issue has been resolved in version 3.16.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Modify process for deserializing DynamicCoordinatorConfig

Fixes #11161.

Description

Modified the deserialization of DynamicCoordinatorConfig
The coordinator now uses the DynamicCoordinatorConfig.Builder.class for deserialization of the dynamic coordinator config. This allows us to automatically use the Builder specified default for a configuration key that does not exist in the metastore payload for the dynamic config. Doing so ensures that an "incomplete" config in the metastore will be supplemented with the proper Druid specified defaults every time it is deserialized.
Prior to this change, Druid used DynamicCoordinatorConfig.class directly for deserialization. The drawback on this is that DynamicCoordinatorConfig is less equipped for cleanly handling missing configuration keys during deserialization. If a developer used a Java primitive when adding a new config, on upgrade, the deserialization would use the Java system default for a missing value. This is often times very bad! For instance, I might add newIntConfig to Druid. Since this isn't in the previous version of Druid, upgrading the coordinator would cause deserialization of the legacy config to populate newIntConfig with the value 0. But as a developer, I needed newIntConfig to default to 100. To work-a-round this, I would flip the type to Integer which would deserialize a missing value as null. I could then check for this null value in the constructor and replace it with the desired default from the Builder class constants. You can see a more realistic example of this work-a-round here Another reference to this conditional null check comes up in this thread.
My change gets us away from this pattern. We are catching an undesirable state and deferring to the default in the Builder class already... so why not just use the Builder for deserialization is my thought. This way we can leverage the built in patterns for handling nulls and replacing them with constant defaults there instead of the DynamicCoordinatorConfig
My one worry is that I am missing an angle here that required us to forgo the Builder for this deserialization. At first instance, I figured that serialization used the same ConfigManager watcher and that using the builder for serde would cause issues in writing the config. However, this does not seem to be the case after running automated tests, manual review of the config update code path, and testing this change in my local druid cluster. Still, perhaps I am overlooking something that has prevented us from using the builder. That is what I'm hoping the review process can smoke out.
What I did not touch in this PR
I did not alter any of the code in the CoordinatorDynamicConfig constructor that is performing the deserialization work-a-round that my update is intended to prevent. I could certainly make that change here as well, but I wanted to be conservative with the scope of this change and guarantee no change in behavior of existing code. Removing the conditional checks on null and changing the variables to primitive types would change behavior IF there were any use of the CoordinatorDynamicConfig constructor directly. To my knowledge, unit tests are the only place this still happens.

Key changed/added classes in this PR

CoordinatorDynamicConfig

This PR has:

[X] been self-reviewed.
[X] added Javadocs for most classes and all non-trivial methods. Linked related entities via Javadoc links.
[X] been tested in a test Druid cluster.

This is an interesting fix, @capistrant !
Some observations:
A) I was confused at first as the PR changes the deserialization when reading from the config manager but not the serialization when writing to it. Then I realized that it works because we have (purposefully?) named the json properties in the exact same way in both the builder and the config classes.
I would have advised that you update the method DruidDynamicConfigsResource.setDynamicConfigs() to write the Builder itself to the manager, but then we would miss out on the validations happening in Builder.build().
Also, there is an existing discrepancy similar to the above. While the POST API payload is read as a Builder, the response of the GET API is still the actual config object. This probably makes sense as the user should be allowed to omit nullable fields in the POST payload but while reading the config, they should get back the fully validated and null-handled config.
I think we should call this out clearly in the javadocs that we must always:

serialize as the config
deserialize as the builder
maintain the same property names in config and builder
use the builder to instantiate
In this vein, we could also make the constructor of CoordinatorDynamicConfig private
and get rid of all of its Json annotations.

B) Another fishy thing is the Builder.build(CoordinatorDynamicConfig defaults). I don't see the point of this method and it's being used in a weird way. Effectively, when a user tries to set a new config but has omitted some fields, we don't update those fields at all but take the existing values from the metastore.
I am not sure but I think it violates REST. A POST must fully update the target object. We can certainly use default values but not old ones.
The fix here would be to simply get rid of this method and this weird logic. Both API and console users would be affected as their old assumptions (if any) about carrying forward omitted values would break.
If we do decide to make this change, we should call it out in release notes.
Although, this would not be a hindrance to the end goal of this PR and need not be handled here.
@gianm , @capistrant , what do you think?

@capistrant , any thoughts on this?
https://github.com/apache/druid/pull/12615#issuecomment-1250083968


Fixes #14. Children, if present, are required to be of type string, node, or element.

Fixes #14
Children aren't required - so an empty button is allowed, but if they are present they must be of types:
        React.PropTypes.string,
        React.PropTypes.node,
        React.PropTypes.element

This should allow nesting of custom elements (icons) inside buttons. This is a more accommodating fix than what was presenting in code by #15 and seems to line up more with @alvaromb's desires for this change.
Here's a screenshot of the proposed solution working with react-native-vector-icons:

And here's the code for the button:
<Button style={styles.button} textStyle={styles.buttonText}>
    <Text>WAT</Text>
    {pizzaIcon}
    <Text> WAT 2 </Text>
</Button>

Thanks for the PR @Andrewpk!
It looks great so let me run a couple of tests and I'll merge it as soon as I can.

Will merge tomorrow! Thanks for the patience @Andrewpk 😉

No problem @alvaromb. I worked on another change yesterday in a personal branch that would remove the singular text wrapper and allow individual elements to be rendered in their own views within the button. This allows for placement styles (flex, margin, padding, etc.) on individual components within a button. If that sounds like something you'd like to include I'll submit a PR for that when I'm done as well.

Yes, if we have to integrate more than just a string that could fit perfectly.

Hello @Andrewpk. Can't merge this PR because the example doesn't run. Text component can't have anything but raw string, another Text or an Image.

The solution should be something like wrapping everything into a parent view, not a text, and discriminate between raw strings and a React node. I can plan to develop something like that, but it would be done/merged during the next week.

I'm going to close this PR in favor of #29


Spawn firefox on a workspace base on firefox profile.

Description
Hello, i do not know if this is possible, but i want to ask it anyway. I use Hyprland and FireFox on ArchLinux. And i also make use of the different profiles can someone have on FireFox.
What i want is to have FireFox open(spawn) on a different work space based on the profile i am using. For example if i use the profile "streaming" i want to open FireFox on workspace 3.
This is useful because i and many people ( i ques) use multiple profiles on browsers. For different tasks. And is nice to capture by the  windowrulev2 in order to control the windows property.
Is this possible ?

the only way I see this working for firefox is if they allow you to start the profile with a cli argument
if so using exec rules might work (if they don't fork themselves)

You can set the profile name and the app_id on the command line.
Something like firefox --name=new_app --no-remote -P new_profile

yea, this is not a hyprlandi sue

ok, yea understood the --name option works. Thanks for the idea.


run result error for chatglm3

run result error for chatglm3.
how fix?

### Tasks

Can you share the scripts to build the engine?


[BUG]: Allow decommission to support delay timeout

Describe the bug
As part of decommission request for graceful decommission we are not allowing delay_imeout to be set by user. This will be required by in case of large cluster. We need to allow delay timeout to be set.
To Reproduce
Steps to reproduce the behavior:

Run a decommission
Try to set delay_timeout
Request fails

Expected behavior
Delay_timeout should be allowed to set
Plugins
NA
Screenshots
NA
Host/Environment (please complete the following information):
NA
Additional context
NA

@pranikum  can you close this issue since you have PR  merged?


NodeMailer Not Sending Emails

Describe the bug
When you fill out the contact form and send it, it says the mail was sent but when we check Gmail it wasn't sent.
To Reproduce
Steps to reproduce the behavior:

Go to the contact form
Click Submit

Expected behavior
Expect the front end to tell the user if the mail didn't send.
Additional context
Here are some resources I quickly found.  We will need to update our nodemailer to not use the unsecured apps and try this oauth2 or change from Gmail to another provider.

https://nodemailer.com/usage/using-gmail/
https://nodemailer.com/smtp/oauth2/

For easier reference.
Here are some resources that helped me solve this.

https://nodemailer.com/smtp/oauth2/#example-3
https://levelup.gitconnected.com/multi-purposes-mailing-api-using-nodemailer-gmail-google-oauth-28de49118d77

I got confused for a little bit because of how you have to add the oauthplayground as a redirect URL.  Just follow the steps and you should be good to go.
Make sure to go to the oauthplayground to get your access token and refresh token after getting everything setup.

https://developers.google.com/oauthplayground/

I have a feeling I might have to look back at this incase the access token and refresh token stop working and we still have it in testing mode.

For easier reference.  One of the keys to success in this was making sure to use googleapis package.
https://www.npmjs.com/package/googleapis

Since the Google API app is in test mode it revokes the refresh token after about a week.  In order to fix that you will need to publish your app under the 0Auth consent screen.
After the mailer stopped working again I did some exploring and came across this youtube video https://www.youtube.com/watch?v=-rcRf7yswfM.  His steps are very similar to levelup, but with a smaller code base, I might refactor to use some of his ideas.  After watching this video I was reading the comments to see if anyone was having the same issues as me since his code was the same concept.  There was a comment linking to this stack overflow post, https://stackoverflow.com/questions/8953983/do-google-refresh-tokens-expire.  They explain that the refresh token doesn't expire but later one of the solutions says the following:
"""
I experienced the same issue and later found out the mistake I was doing. Posting it here so that someone else might find it useful too.
I found out this clue in the Google docs: "A Google Cloud Platform project with an OAuth consent screen configured for an external user type and a publishing status of "Testing" is issued a refresh token expiring in 7 days."
https://developers.google.com/identity/protocols/oauth2
"""
If you go to this section of that link it talks about the 7-day expiration https://developers.google.com/identity/protocols/oauth2#expiration.
So at the moment, I will attempt to publish the app.  For the time being, we will have to go to https://developers.google.com/oauthplayground/ and get a new refresh token, then update the Heroku config refresh_token variable with the new value every 7 days.


Make window resizable

This update allows users to resize the window with keeping the aspect ratio. Since all absolute units (px) were replaced with relative ones (vw), the window looks good and the layout is preserved regardless of the size. It resolves issues #149, #79, and partially #22.

Let me know if anything should be improved before merging, I would be glad to help! And sorry if something's wrong, because it's practically my first PR

@Namerif This is a brilliant idea. Thank you for the PR!
When building this locally, I don't think I'm seeing expected behavior (see attachments).
The first screenshot shows the app when launching. It's tiny (cursor for reference).
The second screenshot is after resizing manually. Looks like the window has lost its aspect ratio.

@Splode glad you like the idea, thanks! And yes, it's definitely not the expected behavior. Which OS do you use? If Windows, it's probably because of the Electron bug that setAspectRatio method I used was not working. It was fixed in 11.2.0 though.
Therefore, I see three possible solutions:

Update Electron to that version
Use this module
Write a resize event handler that will keep the aspect ratio

So please let me know which solution for you is preferred, and if it's the third, I'll update the PR. Otherwise, I will need your help because unfortunately, I have very little experience developing Electron apps and I doubt I will be able to change the dependencies correctly.

@Splode Kindly do the needful for this PR and concerned Issues as i wish to use it in the fancy zone in windows

I am not familiar with coding. I have downloaded pomotroid from the website but how can I actually incorporate your code to make it resizable?

@ans-sigalas I don't think you would be able to do that without any basic software development knowledge unfortunately.

I don't have a lot of experience with electron specifically, but I'm going to give this a shot at trying to implement the different options you listed, hopefully there's still interest in this being a complete feature.


Replacing sd checkpoint with newer version

Thanks for this work.
What changes would be required to use SDXL instead of the 1.4 checkpoint?

Thanks for this work. What changes would be required to use SDXL instead of the 1.4 checkpoint?

Did you modify it successfully? After I migrated to stable diffusion xl, the training results didn't give me the desired identity. Both text encoders use different embedding managers, looking forward to someone implementing celeb-basis+SD XL together!

We are trying to make our overall pipeline more automated. At the same time, we will adapt our method to other diffusion models like SDXL.


gif movie in circuit supplimentary material does not show up in docs.

Informations

Qiskit version: latest
Python version:
Operating system:

What is the current behavior?

Steps to reproduce the problem
What is the expected behavior?
Suggested solutions

Can this be closed now that https://github.com/Qiskit/qiskit/pull/918 has merged? Although if you think there is going to be more static content in each elements' documentation we might want to update the plugin to sync the static resources too, (from a fixed predefined location in each element) right now it only syncs apidocs.

Yep sorry. Not sure how much in future. But also since it mostly me I now remember to do this


Automated releases

This sets up automated releases, mainly so that we can distribute a pre-built version of the tool, allowing Nixpkgs' CI to fetch it without building.
I used the release script to generate the first release, which also contains some info about how to use the artifact: https://github.com/NixOS/nixpkgs-check-by-name/releases/tag/0.1.0
See this Matrix message for historical context.
After this and #15 is merged, we could also extend the automated PRs to regularly update the version, such that we don't forget to do new releases.

I hit the merge button to test in production. https://github.com/NixOS/nixpkgs-check-by-name/actions/runs/8381658441

Hopefully this works: https://github.com/NixOS/nixpkgs-check-by-name/pull/18


Broken worker local state while handling concurrent requests to same upstream

Summary
While using updating many targets for a same upstream concurrently,
there's possibility that some workers enter bad local state and can't recover.
Steps To Reproduce

Start a Kong cluster with 20 workers serving admin API, using postgres database.
Send 20 concurrent request to delete targets with same upstream
One or more workers throw a stack trace (attached below) and further CRUD request to that
worker to update that upstream will always fail (errored with timeout waiting for balancer xxx).

Additional Details & Logs

Kong version: 1.2.1
Kong error logs:

"October 29th 2019, 13:52:37.148","2019/10/29 13:52:37 [error] 40#0: *331090 [lua] healthcheck.lua:989: log(): [healthcheck] (*) Error loading initial target list: failed to acquire lock: timeout, client: <IP_ADDRESS>, server: kong_admin, request: ""DELETE /upstreams/a70227e9-24e3-4a94-9690-c8296f8adb79/targets/34575e29-5058-488c-8bbb-6e1d9ee431d8 HTTP/1.1"", host: ""localhost:8444"""

October 29th 2019, 21:52:40.161  /usr/local/share/lua/5.1/kong/api/routes/upstreams.lua:146: in function 'fn'
October 29th 2019, 21:52:40.161  /usr/local/share/lua/5.1/kong/db/dao/targets.lua:103: in function 'delete_entity'
October 29th 2019, 21:52:40.161  /usr/local/share/lua/5.1/kong/db/dao/init.lua:867: in function 'insert'
October 29th 2019, 21:52:40.161  /usr/local/share/lua/5.1/kong/db/dao/init.lua:1062: in function 'post_crud_event'
October 29th 2019, 21:52:40.161  /usr/local/share/lua/5.1/resty/worker/events.lua:272: in function 'post_local'
October 29th 2019, 21:52:40.161  /usr/local/share/lua/5.1/resty/worker/events.lua:198: in function 'do_event'
October 29th 2019, 21:52:40.161  /usr/local/share/lua/5.1/resty/worker/events.lua:166: in function 'do_handlerlist'
October 29th 2019, 21:52:40.161  /usr/local/share/lua/5.1/kong/runloop/balancer.lua:596: in function 'on_target_event'
October 29th 2019, 21:52:40.161  /usr/local/share/lua/5.1/kong/runloop/balancer.lua:470: in function 'check_target_history'
October 29th 2019, 21:52:40.161  /usr/local/share/lua/5.1/kong/runloop/balancer.lua:406: in function 'create_balancer'
October 29th 2019, 21:52:40.161  /usr/local/share/lua/5.1/kong/runloop/balancer.lua:333: in function 'create_healthchecker'
October 29th 2019, 21:52:40.161  /usr/local/share/lua/5.1/kong/runloop/balancer.lua:196: in function 'populate_healthchecker'
October 29th 2019, 21:52:40.161  /usr/local/share/lua/5.1/resty/healthcheck.lua:390: in function 'get_target_status'

"October 29th 2019, 13:52:40.161","2019/10/29 13:52:40 [error] 40#0: *331090 [lua] events.lua:175: do_handlerlist(): worker-events: event callback failed; source=balancer, event=targets, pid=48 error='/usr/local/share/lua/5.1/resty/healthcheck.lua:390: attempt to index field 'targets' (a nil value)"
"October 29th 2019, 13:52:45.164","2019/10/29 13:52:45 [error] 40#0: *331090 [lua] balancer.lua:598: on_target_event(): failed checking target history for *:  failed to get from node cache: could not acquire callback lock: timeout, client: <IP_ADDRESS>, server: kong_admin, request: ""DELETE /upstreams/a70227e9-24e3-4a94-9690-c8296f8adb79/targets/34575e29-5058-488c-8bbb-6e1d9ee431d8 HTTP/1.1"", host: ""localhost:8444"""
"October 29th 2019, 13:53:15.317","2019/10/29 13:53:15 [error] 40#0: *331090 [lua] balancer.lua:598: on_target_event(): failed checking target history for *:  timeout waiting for balancer for a70227e9-24e3-4a94-9690-c8296f8adb79, client: <IP_ADDRESS>, server: kong_admin, request: ""DELETE /upstreams/a70227e9-24e3-4a94-9690-c8296f8adb79/targets/34575e29-5058-488c-8bbb-6e1d9ee431d8 HTTP/1.1"", host: ""localhost:8444"""

While concurrent requests of same upstream are balanced to different workers, each worker compete for the same lock.
Since timeout waiting for a lock is 5 seconds, running 20 worker means each worker needs to release lock in 250ms.
There's possibility some unlucky worker timeout getting the lock, and goes to this branch (https://github.com/Kong/lua-resty-healthcheck/blob/38a9802e090824f5fc727993d5cb29f3b4837b13/lib/resty/healthcheck.lua#L1326-L1328).
A healthcheck table with targets=nil is returned, then a nil pointer error happened in create_healthchecker https://github.com/Kong/kong/blob/8ee57d885756322bc89e31fa997132d74491beee/kong/runloop/balancer.lua#L444-L450. So creating[upstream.id] = nil on L450 is never executed.
Since the flag is not cleared properly, meaning following request to this worker updating this upstream will always fail in wait()

Actionable items:

The issue initially comes from user of Ingress Controller, which under the hood issues concurrent requests talking to Kong. @hbagdi confirmed that official deployments already by default set worker_count on admin nodes to 1 couple of weeks ago.
Fix healthcheck in https://github.com/Kong/lua-resty-healthcheck/pull/34
Be protective between foreign function call between creating[upstream.id] = true and creating[upstream.id] = nil

@fffonion Some amazing work in debugging here! Thank you for getting down to the bottom of this!

@locao Since @fffonion's PR was merged to lua-resty-healthcheck, can we close this one now?

Looks like it, so I'm closing this one for now! (Please reopen if there's anything else pending.) @fffonion, great work tracking this down!

@hishamhm One last thing before closing this loop : )
In create_healthchecker where a lua-resty-healthcheck instance is created, the error is returned (https://github.com/Kong/kong/blame/master/kong/runloop/balancer.lua#L360) but not catched. It would be awesome if we can fail gracefully in this case (and might be even better to add error handling to other functions between creating[upstream.id] = true and creating[upstream.id] = nil).

@fffonion thanks for the heads up! we'll make those additions!

@fffonion I was in the process of making this changes and then I remembered the reason why we're not catching the error ther. A balancer shouldn't fail to build if a healthchecker can't be built for any reason. That is, if Kong can load-balance traffic but cannot health-check it, it should still load-balance. An error creating the healthchecker should be logged, but not cause create_balancer to fail.
There is a fix to be made there to release creating correctly though, so I'm making a PR to address that!

@hishamhm That makes sense to me. Thanks for the explaination and taking care of this! I'll look at the linked PR shortly.


"Resource name may not be empty" error

Tested v0.1.3 and v0.1.2 but with both versions I get the following error on a Rancher v2.9.4 local cluster:
./cattle-drive migrate -s rke1cluster -t rke2cluster --kubeconfig local.yaml
initiating source [rke1cluster] and target [rke2cluster] clusters objects.. \exiting tool: resource name may not be empty

The migrate, interactive and status sub commands throw the same error. Is there a way to debug this?

Release v0.1.0 works OK.


HBASE-27947 RegionServer OOM when outbound channel backed up

If a client is not able to read response bytes from the channel faster than the server can serve them, netty's pending outbound bytes will build up. If it builds up long enough, it will result in an OOM. We protect against this with the following:

Use netty's WriteBufferWaterMark to trigger channel.setAutoRead(false). When the high watermark is exceeded, autoRead is disabled. When autoRead is disabled, the server will not continue to read incoming bytes from the client, thus will not enqueue more calls from the client.
Already enqueued calls will still be served, and even with writability checks its possible to OOM. We add a new fatal threshold, which should be higher than the high watermark. If exceeded, the connection will be forcibly closed so that we can reclaim the memory.

Adds new configs:

hbase.server.netty.writable.watermark.low
hbase.server.netty.writable.watermark.high
hbase.server.netty.writable.watermark.fatal

All 3 default to 0. The setAutoRead management is disabled if both high and low are 0. Enforcing of the fatal threshold is disabled if fatal is 0. Thus this new behavior is disabled by default.
Adds new metrics:

unwritableTime - histogram showing how much backpressure is being applied due to configured watermark
maxOutboundBytesExceeded - counter showing how many times we needed to forcibly close a connection
nettyTotalPendingOutboundBytes - current aggregate size of pending outbound bytes for all connections on the server
nettyMaxPendingOutboundBytes - current max pending outbound bytes across all channels

A version of this has been tested internally at my company. We set the fatal limit to 100mb, and were able to avoid any OOMs in our test case.
I still need to add tests to AbstractTestIPC, but wanted to get feedback first.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 16s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ master Compile Tests _

+0 :ok:
mvndep
0m 12s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
2m 47s
master passed

+1 :green_heart:
compile
3m 16s
master passed

+1 :green_heart:
checkstyle
0m 58s
master passed

+1 :green_heart:
spotless
0m 42s
branch has no errors when running spotless:check.

+1 :green_heart:
spotbugs
2m 23s
master passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 10s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 37s
the patch passed

+1 :green_heart:
compile
3m 13s
the patch passed

+1 :green_heart:
javac
3m 13s
the patch passed

-0 :warning:
checkstyle
0m 15s
hbase-common: The patch generated 2 new + 0 unchanged - 0 fixed = 2 total (was 0)

-0 :warning:
checkstyle
0m 34s
hbase-server: The patch generated 1 new + 2 unchanged - 0 fixed = 3 total (was 2)

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
hadoopcheck
8m 55s
Patch does not cause any errors with Hadoop 3.2.4 3.3.5.

-1 :x:
spotless
0m 13s
patch has 25 errors when running spotless:check, run spotless:apply to fix.

+1 :green_heart:
spotbugs
2m 42s
the patch passed

_ Other Tests _

+1 :green_heart:
asflicense
0m 29s
The patch does not generate ASF License warnings.

35m 52s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5350/1/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/5350

Optional Tests
dupname asflicense javac spotbugs hadoopcheck hbaseanti spotless checkstyle compile

uname
Linux c5b1b4dcdd9d 5.4.0-156-generic #173-Ubuntu SMP Tue Jul 11 07:25:22 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / ab4b1d884f

Default Java
Eclipse Adoptium-11.0.17+8

checkstyle
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5350/1/artifact/yetus-general-check/output/diff-checkstyle-hbase-common.txt

checkstyle
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5350/1/artifact/yetus-general-check/output/diff-checkstyle-hbase-server.txt

spotless
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5350/1/artifact/yetus-general-check/output/patch-spotless.txt

Max. process+thread count
77 (vs. ulimit of 30000)

modules
C: hbase-common hbase-hadoop-compat hbase-server U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5350/1/console

versions
git=2.34.1 maven=3.8.6 spotbugs=4.7.3

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 33s
Docker mode activated.

-0 :warning:
yetus
0m  3s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ master Compile Tests _

+0 :ok:
mvndep
0m 12s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
2m 47s
master passed

+1 :green_heart:
compile
1m 18s
master passed

+1 :green_heart:
shadedjars
4m 41s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 56s
master passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 14s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 36s
the patch passed

+1 :green_heart:
compile
1m 19s
the patch passed

+1 :green_heart:
javac
1m 19s
the patch passed

+1 :green_heart:
shadedjars
4m 39s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 54s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
2m  9s
hbase-common in the patch passed.

+1 :green_heart:
unit
0m 44s
hbase-hadoop-compat in the patch passed.

-1 :x:
unit
220m 18s
hbase-server in the patch failed.

248m 33s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5350/1/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/5350

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 470f1332caca 5.4.0-152-generic #169-Ubuntu SMP Tue Jun 6 22:23:09 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / ab4b1d884f

Default Java
Eclipse Adoptium-11.0.17+8

unit
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5350/1/artifact/yetus-jdk11-hadoop3-check/output/patch-unit-hbase-server.txt

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5350/1/testReport/

Max. process+thread count
4685 (vs. ulimit of 30000)

modules
C: hbase-common hbase-hadoop-compat hbase-server U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5350/1/console

versions
git=2.34.1 maven=3.8.6

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 35s
Docker mode activated.

-0 :warning:
yetus
0m  3s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ master Compile Tests _

+0 :ok:
mvndep
0m 19s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
2m 49s
master passed

+1 :green_heart:
compile
1m 15s
master passed

+1 :green_heart:
shadedjars
5m  7s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 44s
master passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 11s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 14s
the patch passed

+1 :green_heart:
compile
1m  0s
the patch passed

+1 :green_heart:
javac
1m  0s
the patch passed

+1 :green_heart:
shadedjars
4m 55s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 44s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
1m 47s
hbase-common in the patch passed.

+1 :green_heart:
unit
0m 35s
hbase-hadoop-compat in the patch passed.

-1 :x:
unit
224m 35s
hbase-server in the patch failed.

251m 27s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5350/1/artifact/yetus-jdk8-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/5350

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 69e422149c7f 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / ab4b1d884f

Default Java
Temurin-1.8.0_352-b08

unit
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5350/1/artifact/yetus-jdk8-hadoop3-check/output/patch-unit-hbase-server.txt

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5350/1/testReport/

Max. process+thread count
4626 (vs. ulimit of 30000)

modules
C: hbase-common hbase-hadoop-compat hbase-server U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5350/1/console

versions
git=2.34.1 maven=3.8.6

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 12s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ master Compile Tests _

+0 :ok:
mvndep
0m 10s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
2m 46s
master passed

+1 :green_heart:
compile
3m 16s
master passed

+1 :green_heart:
checkstyle
0m 59s
master passed

+1 :green_heart:
spotless
0m 42s
branch has no errors when running spotless:check.

+1 :green_heart:
spotbugs
2m 20s
master passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 11s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 32s
the patch passed

+1 :green_heart:
compile
3m 14s
the patch passed

+1 :green_heart:
javac
3m 14s
the patch passed

+1 :green_heart:
checkstyle
0m 59s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
hadoopcheck
8m 56s
Patch does not cause any errors with Hadoop 3.2.4 3.3.5.

+1 :green_heart:
spotless
0m 41s
patch has no errors when running spotless:check.

+1 :green_heart:
spotbugs
2m 44s
the patch passed

_ Other Tests _

+1 :green_heart:
asflicense
0m 26s
The patch does not generate ASF License warnings.

36m 10s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5350/2/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/5350

Optional Tests
dupname asflicense javac spotbugs hadoopcheck hbaseanti spotless checkstyle compile

uname
Linux 16d183446185 5.4.0-156-generic #173-Ubuntu SMP Tue Jul 11 07:25:22 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / ab4b1d884f

Default Java
Eclipse Adoptium-11.0.17+8

Max. process+thread count
76 (vs. ulimit of 30000)

modules
C: hbase-common hbase-hadoop-compat hbase-server U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5350/2/console

versions
git=2.34.1 maven=3.8.6 spotbugs=4.7.3

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 32s
Docker mode activated.

-0 :warning:
yetus
0m  2s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ master Compile Tests _

+0 :ok:
mvndep
0m 13s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
2m 33s
master passed

+1 :green_heart:
compile
1m 20s
master passed

+1 :green_heart:
shadedjars
4m 39s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 54s
master passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 13s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 39s
the patch passed

+1 :green_heart:
compile
1m 18s
the patch passed

+1 :green_heart:
javac
1m 18s
the patch passed

+1 :green_heart:
shadedjars
4m 40s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 55s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
2m 10s
hbase-common in the patch passed.

+1 :green_heart:
unit
0m 43s
hbase-hadoop-compat in the patch passed.

+1 :green_heart:
unit
219m 16s
hbase-server in the patch passed.

247m  9s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5350/2/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/5350

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux d8d25a0753f8 5.4.0-152-generic #169-Ubuntu SMP Tue Jun 6 22:23:09 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / ab4b1d884f

Default Java
Eclipse Adoptium-11.0.17+8

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5350/2/testReport/

Max. process+thread count
4646 (vs. ulimit of 30000)

modules
C: hbase-common hbase-hadoop-compat hbase-server U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5350/2/console

versions
git=2.34.1 maven=3.8.6

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 23s
Docker mode activated.

-0 :warning:
yetus
0m  3s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ master Compile Tests _

+0 :ok:
mvndep
0m 18s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
2m 13s
master passed

+1 :green_heart:
compile
1m  2s
master passed

+1 :green_heart:
shadedjars
5m  1s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 46s
master passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 12s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 15s
the patch passed

+1 :green_heart:
compile
1m  1s
the patch passed

+1 :green_heart:
javac
1m  1s
the patch passed

+1 :green_heart:
shadedjars
4m 55s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 43s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
1m 44s
hbase-common in the patch passed.

+1 :green_heart:
unit
0m 32s
hbase-hadoop-compat in the patch passed.

+1 :green_heart:
unit
224m 55s
hbase-server in the patch passed.

250m 24s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5350/2/artifact/yetus-jdk8-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/5350

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 64ec09cdfe51 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / ab4b1d884f

Default Java
Temurin-1.8.0_352-b08

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5350/2/testReport/

Max. process+thread count
4615 (vs. ulimit of 30000)

modules
C: hbase-common hbase-hadoop-compat hbase-server U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5350/2/console

versions
git=2.34.1 maven=3.8.6

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 25s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ master Compile Tests _

+0 :ok:
mvndep
0m 12s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
2m 44s
master passed

+1 :green_heart:
compile
3m 12s
master passed

+1 :green_heart:
checkstyle
0m 53s
master passed

+1 :green_heart:
spotless
0m 42s
branch has no errors when running spotless:check.

+1 :green_heart:
spotbugs
2m  7s
master passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 10s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 33s
the patch passed

+1 :green_heart:
compile
3m  8s
the patch passed

+1 :green_heart:
javac
3m  8s
the patch passed

+1 :green_heart:
checkstyle
0m 49s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
hadoopcheck
9m 34s
Patch does not cause any errors with Hadoop 3.2.4 3.3.5.

+1 :green_heart:
spotless
0m 39s
patch has no errors when running spotless:check.

+1 :green_heart:
spotbugs
2m 30s
the patch passed

_ Other Tests _

+1 :green_heart:
asflicense
0m 23s
The patch does not generate ASF License warnings.

36m 40s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5350/3/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/5350

Optional Tests
dupname asflicense javac spotbugs hadoopcheck hbaseanti spotless checkstyle compile

uname
Linux be693ffe6357 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 20c9e4ba5f

Default Java
Eclipse Adoptium-11.0.17+8

Max. process+thread count
79 (vs. ulimit of 30000)

modules
C: hbase-common hbase-hadoop-compat hbase-server U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5350/3/console

versions
git=2.34.1 maven=3.8.6 spotbugs=4.7.3

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 31s
Docker mode activated.

-0 :warning:
yetus
0m  3s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ master Compile Tests _

+0 :ok:
mvndep
0m 13s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
2m 33s
master passed

+1 :green_heart:
compile
1m 19s
master passed

+1 :green_heart:
shadedjars
4m 39s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 56s
master passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 13s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 37s
the patch passed

+1 :green_heart:
compile
1m 19s
the patch passed

+1 :green_heart:
javac
1m 19s
the patch passed

+1 :green_heart:
shadedjars
4m 38s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 52s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
2m 14s
hbase-common in the patch passed.

+1 :green_heart:
unit
0m 43s
hbase-hadoop-compat in the patch passed.

+1 :green_heart:
unit
221m 41s
hbase-server in the patch passed.

249m 25s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5350/3/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/5350

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux edb302755d9b 5.4.0-152-generic #169-Ubuntu SMP Tue Jun 6 22:23:09 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 20c9e4ba5f

Default Java
Eclipse Adoptium-11.0.17+8

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5350/3/testReport/

Max. process+thread count
4681 (vs. ulimit of 30000)

modules
C: hbase-common hbase-hadoop-compat hbase-server U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5350/3/console

versions
git=2.34.1 maven=3.8.6

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 39s
Docker mode activated.

-0 :warning:
yetus
0m  3s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ master Compile Tests _

+0 :ok:
mvndep
0m 18s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
2m 33s
master passed

+1 :green_heart:
compile
1m  0s
master passed

+1 :green_heart:
shadedjars
5m 21s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 53s
master passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 11s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 27s
the patch passed

+1 :green_heart:
compile
1m  8s
the patch passed

+1 :green_heart:
javac
1m  8s
the patch passed

+1 :green_heart:
shadedjars
5m  0s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 42s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
1m 43s
hbase-common in the patch passed.

+1 :green_heart:
unit
0m 32s
hbase-hadoop-compat in the patch passed.

+1 :green_heart:
unit
223m  4s
hbase-server in the patch passed.

250m 42s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5350/3/artifact/yetus-jdk8-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/5350

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 9d74c4e7cdf2 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 20c9e4ba5f

Default Java
Temurin-1.8.0_352-b08

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5350/3/testReport/

Max. process+thread count
4604 (vs. ulimit of 30000)

modules
C: hbase-common hbase-hadoop-compat hbase-server U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5350/3/console

versions
git=2.34.1 maven=3.8.6

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 12s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ master Compile Tests _

+0 :ok:
mvndep
0m 13s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
2m 30s
master passed

+1 :green_heart:
compile
3m 15s
master passed

+1 :green_heart:
checkstyle
1m  0s
master passed

+1 :green_heart:
spotless
0m 41s
branch has no errors when running spotless:check.

+1 :green_heart:
spotbugs
2m 27s
master passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 11s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 30s
the patch passed

+1 :green_heart:
compile
3m 16s
the patch passed

+1 :green_heart:
javac
3m 16s
the patch passed

-0 :warning:
checkstyle
0m 15s
hbase-common: The patch generated 1 new + 0 unchanged - 0 fixed = 1 total (was 0)

-0 :warning:
checkstyle
0m 33s
hbase-server: The patch generated 1 new + 2 unchanged - 0 fixed = 3 total (was 2)

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
hadoopcheck
8m 53s
Patch does not cause any errors with Hadoop 3.2.4 3.3.5.

-1 :x:
spotless
0m 14s
patch has 27 errors when running spotless:check, run spotless:apply to fix.

-1 :x:
spotbugs
1m 36s
hbase-server generated 2 new + 0 unchanged - 0 fixed = 2 total (was 0)

_ Other Tests _

+1 :green_heart:
asflicense
0m 28s
The patch does not generate ASF License warnings.

35m 19s

Reason
Tests

FindBugs
module:hbase-server

Unread field:NettyServerRpcConnection.java:[line 47]

Unused field:NettyServerRpcConnection.java

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5350/4/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/5350

Optional Tests
dupname asflicense javac spotbugs hadoopcheck hbaseanti spotless checkstyle compile

uname
Linux a56855ecddb2 5.4.0-156-generic #173-Ubuntu SMP Tue Jul 11 07:25:22 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 2fb2ae152a

Default Java
Eclipse Adoptium-11.0.17+8

checkstyle
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5350/4/artifact/yetus-general-check/output/diff-checkstyle-hbase-common.txt

checkstyle
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5350/4/artifact/yetus-general-check/output/diff-checkstyle-hbase-server.txt

spotless
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5350/4/artifact/yetus-general-check/output/patch-spotless.txt

spotbugs
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5350/4/artifact/yetus-general-check/output/new-spotbugs-hbase-server.html

Max. process+thread count
77 (vs. ulimit of 30000)

modules
C: hbase-common hbase-hadoop-compat hbase-server U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5350/4/console

versions
git=2.34.1 maven=3.8.6 spotbugs=4.7.3

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

This message was automatically generated.

@Apache9 I just pushed a change which includes a bit of a refactor:

Change NettyUnsafeUtils.closeDirect to closeImmediately, and have it manage SO_LINGER there. Improve javadoc to say why this is important.
Move all of the writability protections (aborting and setAutoRead) into a new single ChannelDuplexHandler. I felt it was awkward to have this in the Connection, where we need to assert inEventLoop.... Feels better to just put the code itself in the event loop.
Added tests. It was hard to trigger the fatal threshold. In order to do that I had to change NettyServerCall sendResponseIfReady to call NettyServerRpcConnection doRespond, so that I could mock the writeAndFlush to skip the flush. The side effect here is now that we do safeWriteAndFlush, we will log any failures from normal responses just like other callers to doRespond.

Let me know what you think

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 10s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ master Compile Tests _

+0 :ok:
mvndep
0m 10s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
2m 37s
master passed

+1 :green_heart:
compile
3m 15s
master passed

+1 :green_heart:
checkstyle
0m 59s
master passed

+1 :green_heart:
spotless
0m 41s
branch has no errors when running spotless:check.

+1 :green_heart:
spotbugs
2m 18s
master passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 11s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 33s
the patch passed

+1 :green_heart:
compile
3m 13s
the patch passed

+1 :green_heart:
javac
3m 13s
the patch passed

-0 :warning:
checkstyle
0m 15s
hbase-common: The patch generated 1 new + 0 unchanged - 0 fixed = 1 total (was 0)

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
hadoopcheck
8m 54s
Patch does not cause any errors with Hadoop 3.2.4 3.3.5.

-1 :x:
spotless
0m 13s
patch has 27 errors when running spotless:check, run spotless:apply to fix.

+1 :green_heart:
spotbugs
2m 41s
the patch passed

_ Other Tests _

+1 :green_heart:
asflicense
0m 28s
The patch does not generate ASF License warnings.

35m 15s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5350/6/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/5350

Optional Tests
dupname asflicense javac spotbugs hadoopcheck hbaseanti spotless checkstyle compile

uname
Linux 7144d800a71f 5.4.0-156-generic #173-Ubuntu SMP Tue Jul 11 07:25:22 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 2fb2ae152a

Default Java
Eclipse Adoptium-11.0.17+8

checkstyle
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5350/6/artifact/yetus-general-check/output/diff-checkstyle-hbase-common.txt

spotless
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5350/6/artifact/yetus-general-check/output/patch-spotless.txt

Max. process+thread count
77 (vs. ulimit of 30000)

modules
C: hbase-common hbase-hadoop-compat hbase-server U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5350/6/console

versions
git=2.34.1 maven=3.8.6 spotbugs=4.7.3

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 23s
Docker mode activated.

-0 :warning:
yetus
0m  3s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ master Compile Tests _

+0 :ok:
mvndep
0m  9s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
2m 12s
master passed

+1 :green_heart:
compile
1m  1s
master passed

+1 :green_heart:
shadedjars
4m 54s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 43s
master passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 11s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 11s
the patch passed

+1 :green_heart:
compile
1m  0s
the patch passed

+1 :green_heart:
javac
1m  0s
the patch passed

+1 :green_heart:
shadedjars
4m 50s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 41s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
1m 41s
hbase-common in the patch passed.

+1 :green_heart:
unit
0m 32s
hbase-hadoop-compat in the patch passed.

+1 :green_heart:
unit
228m 42s
hbase-server in the patch passed.

254m 19s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5350/6/artifact/yetus-jdk8-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/5350

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux ebf42f2f1639 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 2fb2ae152a

Default Java
Temurin-1.8.0_352-b08

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5350/6/testReport/

Max. process+thread count
4684 (vs. ulimit of 30000)

modules
C: hbase-common hbase-hadoop-compat hbase-server U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5350/6/console

versions
git=2.34.1 maven=3.8.6

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 11s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ master Compile Tests _

+0 :ok:
mvndep
0m 10s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
2m 34s
master passed

+1 :green_heart:
compile
3m 17s
master passed

+1 :green_heart:
checkstyle
1m  0s
master passed

+1 :green_heart:
spotless
0m 42s
branch has no errors when running spotless:check.

+1 :green_heart:
spotbugs
2m 21s
master passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 11s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 33s
the patch passed

+1 :green_heart:
compile
3m 17s
the patch passed

+1 :green_heart:
javac
3m 17s
the patch passed

+1 :green_heart:
checkstyle
0m 59s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
hadoopcheck
8m 47s
Patch does not cause any errors with Hadoop 3.2.4 3.3.5.

+1 :green_heart:
spotless
0m 41s
patch has no errors when running spotless:check.

+1 :green_heart:
spotbugs
2m 42s
the patch passed

_ Other Tests _

+1 :green_heart:
asflicense
0m 28s
The patch does not generate ASF License warnings.

35m 45s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5350/7/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/5350

Optional Tests
dupname asflicense javac spotbugs hadoopcheck hbaseanti spotless checkstyle compile

uname
Linux 0c07945bf552 5.4.0-156-generic #173-Ubuntu SMP Tue Jul 11 07:25:22 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 2fb2ae152a

Default Java
Eclipse Adoptium-11.0.17+8

Max. process+thread count
79 (vs. ulimit of 30000)

modules
C: hbase-common hbase-hadoop-compat hbase-server U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5350/7/console

versions
git=2.34.1 maven=3.8.6 spotbugs=4.7.3

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 24s
Docker mode activated.

-0 :warning:
yetus
0m  2s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ master Compile Tests _

+0 :ok:
mvndep
0m 10s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
2m  7s
master passed

+1 :green_heart:
compile
0m 59s
master passed

+1 :green_heart:
shadedjars
4m 45s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 42s
master passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 11s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 10s
the patch passed

+1 :green_heart:
compile
0m 59s
the patch passed

+1 :green_heart:
javac
0m 59s
the patch passed

+1 :green_heart:
shadedjars
4m 44s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 41s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
1m 42s
hbase-common in the patch passed.

+1 :green_heart:
unit
0m 32s
hbase-hadoop-compat in the patch passed.

+1 :green_heart:
unit
222m 35s
hbase-server in the patch passed.

247m 10s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5350/7/artifact/yetus-jdk8-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/5350

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux b0a367d1e0e2 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 2fb2ae152a

Default Java
Temurin-1.8.0_352-b08

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5350/7/testReport/

Max. process+thread count
4965 (vs. ulimit of 30000)

modules
C: hbase-common hbase-hadoop-compat hbase-server U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5350/7/console

versions
git=2.34.1 maven=3.8.6

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 34s
Docker mode activated.

-0 :warning:
yetus
0m  3s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ master Compile Tests _

+0 :ok:
mvndep
0m 12s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
2m 33s
master passed

+1 :green_heart:
compile
1m 19s
master passed

+1 :green_heart:
shadedjars
4m 39s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 54s
master passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 13s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 35s
the patch passed

+1 :green_heart:
compile
1m 21s
the patch passed

+1 :green_heart:
javac
1m 21s
the patch passed

+1 :green_heart:
shadedjars
4m 41s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 53s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
2m 11s
hbase-common in the patch passed.

+1 :green_heart:
unit
0m 44s
hbase-hadoop-compat in the patch passed.

+1 :green_heart:
unit
222m 35s
hbase-server in the patch passed.

250m  4s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5350/7/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/5350

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux f24c4e7c8f48 5.4.0-152-generic #169-Ubuntu SMP Tue Jun 6 22:23:09 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 2fb2ae152a

Default Java
Eclipse Adoptium-11.0.17+8

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5350/7/testReport/

Max. process+thread count
4548 (vs. ulimit of 30000)

modules
C: hbase-common hbase-hadoop-compat hbase-server U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5350/7/console

versions
git=2.34.1 maven=3.8.6

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 14s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ master Compile Tests _

+0 :ok:
mvndep
0m 11s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
2m 40s
master passed

+1 :green_heart:
compile
3m 14s
master passed

+1 :green_heart:
checkstyle
0m 56s
master passed

+1 :green_heart:
spotless
0m 41s
branch has no errors when running spotless:check.

+1 :green_heart:
spotbugs
2m 17s
master passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 11s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 35s
the patch passed

+1 :green_heart:
compile
3m 14s
the patch passed

+1 :green_heart:
javac
3m 14s
the patch passed

+1 :green_heart:
checkstyle
0m 57s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
hadoopcheck
8m 49s
Patch does not cause any errors with Hadoop 3.2.4 3.3.5.

+1 :green_heart:
spotless
0m 41s
patch has no errors when running spotless:check.

+1 :green_heart:
spotbugs
2m 41s
the patch passed

_ Other Tests _

+1 :green_heart:
asflicense
0m 28s
The patch does not generate ASF License warnings.

35m 41s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5350/8/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/5350

Optional Tests
dupname asflicense javac spotbugs hadoopcheck hbaseanti spotless checkstyle compile

uname
Linux 0867c55968aa 5.4.0-156-generic #173-Ubuntu SMP Tue Jul 11 07:25:22 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / b1fd92d3c7

Default Java
Eclipse Adoptium-11.0.17+8

Max. process+thread count
78 (vs. ulimit of 30000)

modules
C: hbase-common hbase-hadoop-compat hbase-server U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5350/8/console

versions
git=2.34.1 maven=3.8.6 spotbugs=4.7.3

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 24s
Docker mode activated.

-0 :warning:
yetus
0m  3s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ master Compile Tests _

+0 :ok:
mvndep
0m 19s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
2m  8s
master passed

+1 :green_heart:
compile
0m 58s
master passed

+1 :green_heart:
shadedjars
4m 46s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 41s
master passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 12s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m  7s
the patch passed

+1 :green_heart:
compile
1m  4s
the patch passed

+1 :green_heart:
javac
1m  4s
the patch passed

+1 :green_heart:
shadedjars
5m  6s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 58s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
2m 10s
hbase-common in the patch passed.

+1 :green_heart:
unit
0m 35s
hbase-hadoop-compat in the patch passed.

+1 :green_heart:
unit
218m  7s
hbase-server in the patch passed.

244m  1s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5350/8/artifact/yetus-jdk8-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/5350

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux ba78f852fef3 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / b1fd92d3c7

Default Java
Temurin-1.8.0_352-b08

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5350/8/testReport/

Max. process+thread count
4714 (vs. ulimit of 30000)

modules
C: hbase-common hbase-hadoop-compat hbase-server U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5350/8/console

versions
git=2.34.1 maven=3.8.6

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

This message was automatically generated.


clean up contact us page

fixes #119
@clstokes pls take a look at this, I did not use your designs. but I did add some details about who should use the form and who should use the support portal. happy to talk through the design decisions over zoom if you'd like.
also @clstokes can I pls have access to fix that support landing page? its using the wrong fonts and a few other things, id love to get that cleaned up.
@zchase feel free to add commits if I got anything wrong, and I really want to remove the requirement to include a phone number on that form, is that possible?

@susanev I wouldn't mind if we but the text that calls out if the person is looking for technical support above the form, because I think some of motivation for this work is that people were submitting Contact Us when they should be submitting a ticket. I also would like to implement something like Cameron's original design, but as a component on our marketing pages. I'd like to consolidated as many forms as possible, as it will make it operationally easier to manage all the requests. For example, we have a contact form on the bottom of /aws and I'd like that section to be replaced w/ something close to Cameron's mock.
Outside of that, I think this is good. As far as removing the phone number that is up to the sales team and we don't need a PR to change it. We can change it directly from HubSpot.

@zchase lets talk more about Cameron's design over zoom some time soon, I have some usability concerns about it.
i can move the technical support up, but do we have more data on where people were right before they came to contact us? that might help us figure out why people are landing here when they are hitting issues.

@zchase ive moved the support direction up (though i do want to call out that I think its a bit confusing). but either way, can you add a heading to the form as well something like Contact Us or similar?

im closing this because it seems multiple folks are working on this... will come back when the requirements are more clear.


Enhance the main startup function and prevent startup error

I have made one fix and one enhancement to the main.js file

Fixed an invalid CSS selector that caused the template to fail on startup
Enhanced the startup function to return the createMap deferred

Several lines that contained trailing whitespace were automatically cleaned up by a code linter.  I can revert the whitespace if this PR is otherwise acceptable.

@lscharen  thanks for the pull request. I'll fix the invalid css selector.
For the deferred issue all the templates are built on some boilerplate code that sets up the basic structure. In this boilerplate we have logic that calls a function (Hello World) when the map has been created. @driskull  any thoughts on returning the createMap deferred in startup?
https://github.com/Esri/application-boilerplate-js/blob/development/application_boilerplate/js/main.js

yeah we could do that.

@driskull  ok i'll add an issue to the app boilerplate repo. @lscharen  once the boilerplate code is updated we'll update the templates to reflect that change.


Component Billboard

This is the first step for billboards and particles.
Please render gods @baransrc and @miquelmiro3 take a look and let me know what you think.
It's missing blending between tiles during animation, but we needed some of this code to use it in ComponentParticleSystem.
Thanks @miquelmiro3 for your help!

Alvaro, how can I test it in the engine?

@Erick9Thor good question. Thanks!
For testing you can:

Add a component billboard in a game object
For animations: Add some tailed texture, specify how many rows and columns it has. You also can activate looping. Play.
For colors gradient: Activate color over lifetime. Set some gradients, color cylcles or loop. Play.
You can combine both, color and animation.

Thanks @Erick9Thor !


[PDI-19386] FTP_Delete step: Not recognizing "Copy previous results to" option when enabled.

PDI-19386 FTP_Delete step: Not recognizing "Copy previous results to" option when enabled.

 Note:

Frogbot also supports Contextual Analysis, Secret Detection, IaC and SAST Vulnerabilities Scanning. This features are included as part of the JFrog Advanced Security package, which isn't enabled on your system.

🐸 JFrog Frogbot

:white_check_mark: Build finished in 27m 3s
Build command:
mvn clean verify -B -e -Daudit -amd -Djs.no.sandbox -pl \
plugins/ftp-delete/impl

:ok_hand: All tests passed!
Tests run: 1, Failures: 0, Skipped: 0    Test Results

:information_source:  This is an automatic message


BUG nbqa doctest has trailing whispace

e.g.
**********************************************************************
File "/home/marco/nbQA-dev/tests/data/notebook_for_testing_copy.ipynb", cell_2:11, in notebook_for_testing_copy   .hello
Failed example:
    hello("goodbye")
Expected:
    'hello goodby'
Got:
    'hello goodbye'
**********************************************************************
1 items had failures:
   1 of   2 in notebook_for_testing_copy   .hello
***Test Failed*** 1 failures.```

closed in #295