Fix access of cmdline when a gunicorn workers becomes a zombie

If while trying to obtain a list of ready gunicorn workers, one of them
becomes a zombie, psutil.cmdline returns [] (see here:
https://github.com/giampaolo/psutil/blob/release-4.2.0/psutil/_pslinux.py#L1007)
Boom:
Traceback (most recent call last):
  File "/usr/local/bin/airflow", line 28, in <module>
    args.func(args)
  File "/usr/local/lib/python3.5/dist-packages/airflow/bin/cli.py", line 803, in webserver
    restart_workers(gunicorn_master_proc, num_workers)
  File "/usr/local/lib/python3.5/dist-packages/airflow/bin/cli.py", line 687, in restart_workers
    num_ready_workers_running = get_num_ready_workers_running(gunicorn_master_proc)
  File "/usr/local/lib/python3.5/dist-packages/airflow/bin/cli.py", line 663, in get_num_ready_workers_running
    proc for proc in workers
  File "/usr/local/lib/python3.5/dist-packages/airflow/bin/cli.py", line 664, in <listcomp>
    if settings.GUNICORN_WORKER_READY_PREFIX in proc.cmdline()[0]
IndexError: list index out of range

So ensure a cmdline is actually returned before doing the cmdline prefix
check in ready_prefix_on_cmdline.
Make sure you have checked all steps below.

Thanks for the contribution. Please follow the commit guidelines.

@bolkedebruin yup! just working backwards...

Codecov Report

Merging #2844 into master will decrease coverage by 0.05%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master    #2844      +/-   ##
==========================================
- Coverage   73.93%   73.87%   -0.06%
==========================================
  Files         160      160
  Lines       12131    12139       +8
==========================================
- Hits         8969     8968       -1
- Misses       3162     3171       +9

Impacted Files
Coverage Δ

airflow/bin/cli.py
53.28% <0%> (-0.66%)
:arrow_down:

airflow/executors/dask_executor.py
79.06% <0%> (-2.33%)
:arrow_down:

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 06b41fb...1991159. Read the comment docs.

:bowtie:


SAP Private Link is GA

Fix the "beta" label for SAP Private Link in the README

fixed. @hterminasyan please double-check the entire privatelink branch.

fixed


Mapping of old Java EE artifacts to new Jakarta artifacts

Would be awesome if there were an actual mapping of artifacts from Java EE -> Jakarta EE.
E.g. after hours of looking I am unable to determine how to convert a build that works perfectly well with Java EE XJC, but no idea what the related Jakarta artifacts are.
Specifically having trouble with

org.jvnet.jaxb2_commons:jaxb2-basics:0.12.0
org.jvnet.jaxb2_commons:jaxb2-basics-ant:0.12.0

Though I've only gotten this far after hours of trying to track down how to achieve this in Jakarta EE.

have you tried https://github.com/highsource/jaxb2-basics ?

I have.
java.lang.NoClassDefFoundError: javax/xml/bind/JAXBException

Here are dependencies I have currently, which seems to be the closest but which leads to that above exception
    xjc 'jakarta.xml.bind:jakarta.xml.bind-api:3.0.1'
    xjc 'org.glassfish.jaxb:jaxb-runtime:3.0.1'
    xjc 'org.jvnet.jaxb2_commons:jaxb2-basics:1.11.1'
    xjc 'org.jvnet.jaxb2_commons:jaxb2-basics-ant:1.11.1'
    xjc 'org.glassfish.jaxb:jaxb-xjc:3.0.2'

why
xjc 'org.glassfish.jaxb:jaxb-runtime:3.0.1'
xjc 'org.glassfish.jaxb:jaxb-xjc:3.0.2'

are not at the same version? I'm not saying that will help, just that it looks strange to me.
There are two things I'd check/try:

look at the dependency tree to see which exact version of the jaxb-xjc artifact is being used (this artifact has the same packages in javax (2.x) as well as in jakarta (3.x) versions)
try to add javax.xml.bind:jaxb-api:2.3.1 to your dependencies, that should resolve (hide?) the Error

note that jaxb2-basics (formerly jaxb2-commons project at java.net) has been community driven with no involvement of the jaxb(-ri) team since its beginning - if my memory works well after those ~15 years...

Just an oversight as I have been trying combinations.  As you said, no difference.
I know its complicated, but its super frustrating to continually run into these kind of situations trying to migrate to Jakarta EE.  Its not like jaxb2-basics is a super obscure, unused project.

I played around and got a working version of jaxb2-basics.  Actually did not really even take much change.
https://github.com/highsource/jaxb2-basics/pull/129

Sorry when highjacking this issue, but there seems to be some expertise here about the topic.
I have projects which use the plugins from https://github.com/javaee/jaxb2-commons together with the Apache CXF XJC Plugin (https://github.com/apache/cxf-xjc-utils/tree/master/cxf-xjc-plugin). The later has been upgraded to JavaEE9 (Jakarta.*) recently. But the last commit in https://github.com/javaee/jaxb2-commons has is dated back to 2017. Is there any successor to this project which I have missed?

I upgraded the other jaxb2-commons plugins in https://github.com/javaee/jaxb2-commons/pull/46. Actually no big changes necessary besides the obvious dependency upgrades.

Hi everyone
Currently working with Matt on updating highsource projects for jakarta migration
Also did get remaining old plugins into jaxb-basics (issue raised by @cachescrubber )
Keep updated, release will be soon available

Hi everyone
Currently working with Matt on updating highsource projects for jakarta migration
Also did get remaining old plugins into jaxb-basics (issue raised by @cachescrubber )
Keep updated, release will be soon available

See https://github.com/highsource/jaxb2-basics/pull/167 merged into master


feat(webpack): add fast refresh plugin

Current state

Hops currently uses HMR to update the frontend, which is great, but it may be better with the new fast refresh version 😄
Changes introduced here

What is introduced in this PR
In this PR we introduce a new flag --fast-refresh to enable the new react-refresh and react-refresh-webpack-plugin module that are currently used in React.
Why we need to add it
Fast-refresh is the enhanced version of HMR (also previously known as Hot Reloading) that allows us to get near-instant feedback for changes in our React components, with --fast-refresh enabled, most edits should be visible within a second or two preserving React local state in function components (and Hooks) by default.
If we need to force the state to be reset and a component to be remounted we can add this anywhere in the file we are working on // @refresh reset this directive is local to the file, and instructs react-refresh to remount components defined in that file on every edit.
Another interesting features that this plugin gives to us is error resilience:

If we make a syntax error during a --fast-refresh session, we can fix it and save the file again. The new redbox will disappear. Modules with syntax errors are prevented from running, so we won't need to reload the app 😄.

If we make a mistake that leads to a runtime error inside our component, the --fast-refresh session will also continue after we fix the error. In that case, React will remount our application using the updated code

If we make a runtime error during the module initialization, the --rast-refresh session will continue once we fix the error. The redbox will disappear, and the module will be updated.

But there are some small limitations, two reasons why we might see local state being reset on every edit to a file:

Local state is not preserved for class components (it includes hocs that returns classes instead of functional components)
The module we're editing might have other exports in addition to a React component

Screenshots and an example with hops/template-react

It's good to mention that since hops uses an older version of webpack 4.41.0 we cannot use the latest version for react-refresh-webpack-plugin since they are using the new (see full changelog here) module.hot.invalidate API that webpack releases in v4.43.0, so until hops can use a new version of webpack we have to stay with v0.3.3 otherwise it won't work.
Checklist

[ ] All commit messages adhere to the appropriate format in order to trigger a correct release
[ ] All code is written in untranspiled ECMAScript (ES 2017) and is formatted using prettier
[ ] Necessary unit tests are added in order to ensure correct behavior
[ ] Documentation has been added

Bors merge bot cheat sheet
We are using bors-ng to automate merging of our pull requests. The following table provides a summary of commands that are available to reviewers (members of this repository with push access) and delegates (in case of bors delegate+ or bors delegate=[list]).

Syntax
Description

bors merge
Run the test suite and push to master if it passes. Short for "reviewed: looks good."

bors merge-
Cancel an r+, r=, merge, or merge=

bors try
Run the test suite without pushing to master.

bors try-
Cancel a try

bors delegate+
Allow the pull request author to merge their changes.

bors delegate=[list]
Allow the listed users to r+ this pull request's changes.

bors retry
Run the previous command a second time.

This is a short collection of opinionated commands. For a full list of the commands read the bors reference.

It's good to mention that since hops uses an older version of webpack 4.41.0 we cannot use the latest version for react-refresh-webpack-plugin since they are using the new (see full changelog here) module.hot.invalidate API that webpack releases in v4.43.0, so until hops can use a new version of webpack we have to stay with v0.3.3 otherwise it won't work.

You could upgrade webpack to ^4.43.0, to ensure that the correct version gets installed.

This PR got superseded by #1720. Thanks for your contribution, @x0s3!


Group History: enable browsing/filtering

The history API returns the latest 50 results per default: https://github.com/yunity/foodsaving-backend/pull/260
We should give the user the opportunity to browse through the history and filter by action type (typus).
Use swagger ( https://foodsaving.world/docs/#!/history/history_list ) to see the filtering options and the API results.
Update: we now can filter by user and store.
To do:

attach history to store view (only showing store-related events)
enable browsing by date (e.g. load history events before a point in time)

does this also include filter by date ?

Yes, that's what I mean with browsing. Maybe a date picker to jump to a certain point in time.
The backend could be changed to offer date filters, that could make it easier.

i am a bit lost where to comment for this request - if it's a new issue or improvement for this one. The history looks really nice on the frontend. I worry that it can get quite cluttered where it is now. has there been discussion if the history could be attached to a store ? Like the same tab just on a store level to switch to ?

Yes, that would also be possible. Note to implementers: history is a stateless component, you can just feed it any list of history items.

To do: jump to a point in time.

The new history lost all options for filtering currently, should we add it again? Which ones are the most useful?

(Will move it back to Discussion)

It would be nice to have/cool, but there wasn't a real need for it so far. You can visit group/store/user history right now, which is fairly powerful already.


Min SDK Version changed

Hello, I've noticed that the minimum SDK version has changed in the latest release, but there was no mention of this in the release notes. Is this change intentional?
Affected Version: 1.6.5
Expected Behavior: Min SDK Version should be consistent with previous versions or mentioned in release notes if changed.
Actual Behavior: Min SDK Version changed without any notice.
Thank you for your time and effort on this project.
https://github.com/qdsfdhvh/compose-imageloader/compare/1.6.4...1.6.5

Sorry, it's my mistake, I'll change it back to minSdk=21 right now.


Upgrade CP4I version to 2022.4.1

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
The version currently being used in CP Deployer (2022.2.1) is deprecated. Need to upgrade to the latest
Describe the solution you'd like
A clear and concise description of what you want to happen.
Upgrade the version of CP4I deployed by CP Deployer
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
none
Additional context
Add any other context or screenshots about the feature request here.

This has been discussed with @fketelaars and @sreckoj . The change to be made is in the file automation-roles/50-install-cloud-pak/cp4i/cp4i-cluster/vars/versions.yml.
I  will create the PR and request for approval.


Introduce SendEmptyResponse method in CoAP Server.

This PR unifies a way of how CoAP Ntf/Qry/AnsCon responses are handled.

Current coverage is 72.35% (diff: 71.05%)

Merging #1108 into master will decrease coverage by 1.92%

@@             master      #1108   diff @@
==========================================
  Files           127        127
  Lines         17643      18549   +906
  Methods        2484       2602   +118
  Messages          0          0
  Branches       2139       2247   +108
==========================================
+ Hits          13106      13422   +316
- Misses         3891       4434   +543
- Partials        646        693    +47

Powered by Codecov. Last update 85ee5e6...fe69e41

@LuDuda, can you rebase on master to get the build checks to pass?  Thanks.

Thanks for feedback! So the changes are:

Change name to SendEmptyAck.
Using "if-statement" instead of SuccessOrExit in case we want to process the request further. But i can remove SuccessOrExit completely if you want?
Put verify if header is of kCoapTypeConfirmable type to SendEmptyAck as @bukepo suggested. Imho it makes code less errorprone but it hides some logic which i think should be handled in layers above CoAP.

Shall we accept this PR or any changes/improvements needed from my side?


(readme): update architecture picture

Codecov Report

Merging #441 (7aac86f) into master (ffe19d1) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #441   +/-   ##
=========================================
  Coverage     14.97%   14.97%
  Complexity      398      398
=========================================
  Files           180      180
  Lines          8089     8089
  Branches        665      665
=========================================
  Hits           1211     1211
  Misses         6791     6791
  Partials         87       87


correct doc for Intel compiler

Summary:
Not giving the correct option to the intel compiler leads to divergent transitions going unreported (instead of triggering them).
Description:
need to correct the doc
Reproducible Steps:
Please report steps to reproduce the issue. If it's not possible to reproduce, please include a description of how you discovered the issue.
If you have a reproducible example, please include it.
Current Output:
The current output. Knowing what is the current behavior is useful.
Expected Output:
Describe what you expect the output to be. Knowing the correct behavior is also very useful.
Additional Information:
Provide any additional information here.
Current Version:
v2.17.1

Can you add a detail or two? I'm planning on using icpc with Xeon Phis and would like to avoid this.

What do you mean? Just follow the instructions given in the manual to avoid the issue.
... and yes, I was shocked when I learned this a while ago. I was giving a course and people were not able to trigger divergences in Stan when running the 8-schools example in the CP parametrization which has a horrible funnel geometry and lots of divergences. The reason was that people were using the Intel compiler with the defaults which are set such that floating point operations are speed up in a way which leads to non-detection of divergences. So use these -fp-precise options detailed in the manual.
(even better if you would confirm my finding from ~2y back).

What do you mean? Just follow the instructions given in the manual to avoid the issue.

your description in the issue up top is

need to correct the doc

so I assumed the manual was not the place to look

use these -fp-precise options

I think Intel is infamous among numerical analysts & scientists for defaulting to unsafe behavior.  On the other hand, it does a better job vectorizing for wide SIMD workloads.

@maedoc is right here.  This issue needs to be clarified.
Going forward, I very much want issues to have enough details that a third party can look at them and have enough detail to solve them.  I think this is going to be critical in scaling out to more developers.

hmm... I see. This is one of those issue which are filed with the PR solving it, so the description is misleading here since this is already the solution needed to be implemented.
BTW... mind reviewing and merging? Should not take long (unless you want to confirm Intel compiler quirks).

I'll try to reproduce and see if a more subtle set of flags (instead of -fp-precise) can eliminate the issue; is the funnel sufficient or need to use exactly the 8-schools CP metnioned above?

In a comparison of g++, icpc with & without -fp-model precise, they report similar numbers of divergences.  Maybe icpc has improved recently.

which icpc version?

icpc 18.0.2
gcc 4.8.5
cmdstan 2.17.1

Fixed in #623


I have a question about training ？

Why is the results of your standard adapter improved instead?
And won't adding an FFN as Adapter for each layer make the model very difficult to train due to too many parameters?
These two points are bothering me, can you help me?

Because I‘ve notice that the intermediate_size in your standard adapt layer is 1024


java.lang.IllegalStateException: Content View height is too small

at com.ramotion.foldingcell.FoldingCell.calculateHeightsForAnimationParts(FoldingCell.java:257)
04-22 13:21:00.109 6283-6283/com.broadamptechnologies.bricks W/System.err:     at com.ramotion.foldingcell.FoldingCell.unfold(FoldingCell.java:118)
04-22 13:21:00.109 6283-6283/com.broadamptechnologies.bricks W/System.err:     at com.ramotion.foldingcell.FoldingCell.toggle(FoldingCell.java:206)
04-22 13:21:00.109 6283-6283/com.broadamptechnologies.bricks W/System.err:     at com.broadamptechnologies.bricks.NewsFragment$2.onClick(NewsFragment.java:97)
04-22 13:21:00.109 6283-6283/com.broadamptechnologies.bricks W/System.err:     at android.view.View.performClick(View.java:5198)
04-22 13:21:00.109 6283-6283/com.broadamptechnologies.bricks W/System.err:     at android.view.View$PerformClick.run(View.java:21147)
04-22 13:21:00.109 6283-6283/com.broadamptechnologies.bricks W/System.err:     at android.os.Handler.handleCallback(Handler.java:739)
04-22 13:21:00.109 6283-6283/com.broadamptechnologies.bricks W/System.err:     at android.os.Handler.dispatchMessage(Handler.java:95)
04-22 13:21:00.109 6283-6283/com.broadamptechnologies.bricks W/System.err:     at android.os.Looper.loop(Looper.java:148)
04-22 13:21:00.109 6283-6283/com.broadamptechnologies.bricks W/System.err:     at android.app.ActivityThread.main(ActivityThread.java:5417)
04-22 13:21:00.110 6283-6283/com.broadamptechnologies.bricks W/System.err:     at java.lang.reflect.Method.invoke(Native Method)
04-22 13:21:00.110 6283-6283/com.broadamptechnologies.bricks W/System.err:     at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:726)
04-22 13:21:00.110 6283-6283/com.broadamptechnologies.bricks W/System.err:     at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)

As you can see in the exception message - "Content View height is too small". Content view height must be at least twice bigger than title view

well... my view is 4 times bigger . still geting the same issue

I have same issue . and change content 2 times bigger than title but have same exception

I think you need to  change LinearLayout in sample code in cell_content_layout.xml/cell_list_view_example and cell_title_layout.xml/cell_list_view_example to  FrameLayout

Same here, for me it happens in rare cases...
My crash cause when i call fold animation during oncreate with some kind of delay, but I guess I need to listen to ViewTreeObserver.onGlobalLayout

Same here , sol plz

I get when I open one , the 3rd or 4th also opens beyond the scope of the screen, also the 10th and the 15th, so you have 4 open when you opened only one, then you have to close all 4


Modify japanese translations.

Hi! Thank you for translated into japanese. I modify some mistranslation.

Sorry, I didn't notice https://crowdin.com/project/flask-admin

I uploaded your changes to crowdin yesterday. Will add the changes to this repo soon.

@pawl Thanks!


Working prototype

[x] Service Manager / install app
[x] Device Handler

References

https://github.com/SmartThingsCommunity/SmartThingsTest/blob/241094028dceab387a4325ebf2478ce957d267d5/devicetypes/smartthings/hue-lux-bulb.groovy
https://github.com/SmartThingsCommunity/SmartThingsTest/blob/241094028dceab387a4325ebf2478ce957d267d5/smartapps/smartthings/hue-connect.groovy

Hi, I managed to resolve the issue with airfoil-api, there was a problem with mdns, so I took it out of the dependencies and added it from nam directly.
I am having a new problem with the smart app for it.
Quite simply it finds my Airfoil speakers but keeps giving a red banner 'Error saving page' at the top when I press done. Is this resolvable at all?
Thanks


Impossible to set map bounds and pitch, bearing, etc

Using initial_view_state with view_state() one get adjust the way that their map looks allowing them to change the pitch and bearing. This is particularly handy for 3D / extruded shapes. However, view_state() does not let you specify a starting bound only a starting center point.
The initial bounds should only conflict with the center argument of view_state() not all others.
This would save one from doing:
view_state(
    center = {
      sf::st_bbox(geoms) |>
      sf::st_as_sfc() |>
      sf::st_centroid()
  }[[1]]
)

Preserving the pitch and bearing is simple. It should be simple to rotate the initial_bounds by bearing also.


Fix for #7: Not as optimized for Webpack as it could be.

Adds ability to wrap functions that are elements of an array literal in an argument list.
I refactored some of the if-else logic into named functions that were easier for me to understand, but I'm not sure if they will be easier for others or not. Feedback welcome.
npm run test runs green and npm run coverage gives 100%.

This is awesome!! :tada: I'm eager to merge, but have a few suggestions:

We should add a new benchmark file built by Webpack (React DOM maybe? the "cost of modules" file is too artificial IMO) and re-run the benchmarks in the README. I can do that this weekend.
I'd like to see more test cases to confirm that functions within arrays that are not arguments to a function do not result in unnecessary parens. Probably a super edge case, but I'd really like to optimize just for this particular webpack case and not add parens where they're not required.

All in all though, great work and if you don't have time to address # 2 then I can take care of it after I merge.

I'm fairly certain that react-dom/dist/react-dom.js is just a very small non-bundled file that just pulls a property out of react.js, and react/dist/react.js is packaged by browserify. I don't know of any libraries offhand that use webpack. To test webpack, I've been using ColorFlood, which is a simple create-react-app application, but I'm sure there are lots of other good examples.
This is good idea; I'm happy to add a couple test cases in the next few days.

I added four negative test cases for array literals. I feel like I didn't have a ton of creativity in making these test cases, though, so let me know if there are some more ones you'd like!

Actually, it just occurred to me that this could be designed to be more specific to webpack if we want. Right now the logic of this PR is:

Wrap any function that is an element of an array literal which is a function parameter.

But if we wanted to make it even more specific to webpack, we could make the logic instead be:

Wrap any function that is an element of an array literal which is a function parameter to an IIFE.

I'm inclined to change it that way. What do you think?

I coded up a more webpack-specific version in PR #33, which is now my preference, I think.

Aaaaaand I went ahead and added a webpack benchmark in PR #34 in case you want to use it. (I unexpectedly had a bunch of time this weekend and have found working on this surprisingly fun...)

Yeah I agree that #33 is a more targeted solution. I'd prefer for this tool to be conservative to avoid over-parsing functions. Thanks for offering options with multiple PRs! :)


Some examples on CodeSandbox not working anymore since react-curtains @1.0.8

Hey, thanks for the port of curtainsjs to REact, using it now and I've learned quite a lot about WebGL already<
Some of the demos you've done on CodeSandbox aren't worrking anymore, and if I change the version back to 1,0.6, thne it magically works again. For example this one doesn't work unless I downgrade the package version.
Peace and thank you for your work. :v:

Hey @theosenoussaoui,
You're right indeed, I've forgotten to patch a few things on react-curtains following curtains.js v8.0 release, especially the FXAAPass component. This should be fixed with v1.0.9: b6814403736fc638beb6b87ef29996fabf12f286
Also in your first version you were asking for a port of the scrolling wheel example, so here is a basic port (no touch support tho): https://codesandbox.io/s/react-curtains-rotating-planes-ylp29
Cheers,

Hey @theosenoussaoui,
You're right indeed, I've forgotten to patch a few things on react-curtains following curtains.js v8.0 release, especially the FXAAPass component. This should be fixed with v1.0.9: b6814403736fc638beb6b87ef29996fabf12f286
Also in your first version you were asking for a port of the scrolling wheel example, so here is a basic port (no touch support tho): https://codesandbox.io/s/react-curtains-rotating-planes-ylp29
Cheers,

Thanks for the quick answer and the fix. I managed to get the port working (this is why I've deleted it) but thank you anyway.

Thanks for the quick answer and the fix. I managed to get the port working (this is why I've deleted it) but thank you anyway.


HDDS-11871. Update Publish Ozone docs workflow for HDDS-11365

What changes were proposed in this pull request?
1. edge docs are not updated in the website.

HDDS-7678 added workflow for publishing content from hdds-docs to the website.
INFRA-25530 changed default branch from asf-site to master, effectively disabling the workflow (scheduled workflows need to be present in the default branch).
Cherry-picked the workflow to master as it was added in HDDS-7678.
HDDS-11365 introduced ozone-dev-support module, which is not available when building only the docs.

So workflow run fails with:
Failed to execute goal org.apache.maven.plugins:maven-remote-resources-plugin:1.7.0:process (default) on project hdds-docs: Execution default of goal org.apache.maven.plugins:maven-remote-resources-plugin:1.7.0:process failed: Plugin org.apache.maven.plugins:maven-remote-resources-plugin:1.7.0 or one of its dependencies could not be resolved: Could not find artifact org.apache.ozone:ozone-dev-support:jar:2.0.0-SNAPSHOT in apache.snapshots.https (https://repository.apache.org/content/repositories/snapshots)

0c4abe67826e9692f94a7d99e0dc36ab8abea638 fixes this by executing Hugo directly, bypassing Maven.
This is achieved by running the same command as basic (docs) check in Ozone CI.
2. edge docs are updated by the workflow even if no docs were changed.

Doc footer includes Last Modified time and commit information.
actions/checkout clones the repo without history by default.
Hugo only has information about the most recent commit, marking every page as modified by that one.
Last Modified information is wrong, and workflow finds "changes" in doc every day.

36f548860cc832c25524fba5eae6659586c72383 fixes this by cloning apache/ozone with history.
Since both fixes are one-liners, I bundled them in the same PR.
https://issues.apache.org/jira/browse/HDDS-11871
How was this patch tested?
Run 1: https://github.com/adoroszlai/ozone-site/actions/runs/12197628118
Doc update: https://github.com/adoroszlai/ozone-site/commit/88c05d37c2dc72e4baeef66a53b04ea6c9fb1edc

pick up recent doc additions, e.g. tools/debug
update footer with proper last modified information

Run 2: https://github.com/adoroszlai/ozone-site/actions/runs/12197847484
Doc update: none
Your branch is up to date with 'origin/asf-site'.
nothing to commit, working tree clean
Everything up-to-date

Thanks @devabhishekpal, @errose28 for the review.


Add Blogs

There are some Professors and Students with excellent blogs and personal sites.

Any links?

Here's a few to get started. Will add more as I see them!
Sites

J. Alex Halderman
Scott Wolchok (archive)
Peter Honeyman
Igor Markov
Quentin F. Stout

Quora Questions

http://www.quora.com/Which-is-better-a-B-S-in-Computer-Science-from-the-University-of-Michigan-or-one-from-Stanford-University
http://www.quora.com/What-is-it-like-to-study-computer-science-at-the-University-of-Michigan

Misc

https://wiki.eecs.umich.edu/secrit/index.php/Main_Page


Microsoft Edge

Does this really not work with Edge?

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

ID: 2010f5ac-1080-addd-1fb3-5b05db26c1f6
Version Independent ID: 1aa18d6a-5846-7989-b844-fc8ad027921b
Content: Azure AD Connect: Seamless Single Sign-On
Content Source: articles/active-directory/hybrid/how-to-connect-sso.md
Service: active-directory
Sub-service: hybrid
GitHub Login: @billmath
Microsoft Alias: billmath

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

Unfortunately no, it is not yet officially supported. You might be able to get around this by registering your devices with Azure AD. Some users have reported getting this to work. https://techcommunity.microsoft.com/t5/Office-365-Admin-AMA/Edge-Support-for-SSO/td-p/96302

Closing this out but feel free to leave product feedback in user voice for this. https://feedback.azure.com/forums/169401-azure-active-directory


Xamarin.Forms - Images get mixed after a lot of requests (cell reusing)

Please try this sample:
https://github.com/daniel-luberda/FFImageLoading/commit/c916f4c5b8b4de67d275414ffd39d1a00b6b2a12
Steps to reproduce:

Open List Demo
Scroll the list FAST few times from start to end
Click the "Duplicate list items"
Scroll the list FAST few times from start to end
Result:
Images get mixed (wrong order).

Fixed it. It would be nice to make a new build. https://github.com/daniel-luberda/FFImageLoading/commit/8d506a4121173b2ca015c15fad0cb257ec3e7cac

Seems like a Xamarin Forms bug that you "fixed" am I right ?
What does the Invalidate?

Of course. Invalidate is an Android method. If invalidate() gets called it tells the system that the current view has changed and it should be redrawn as soon as possible. Original Image renderer had an Invalidate override that skips Invalidate operation once after setting ImageSource. That was the cause why images didn't always reload when FAST scrolling. I just removed override and that's all.
About the hack that was removed:
I'm still thinking if we should merge it know, a lot of people still uses Xamarin.Forms 1.4.4 (I sent you a mail about it). The hack doesn't collide with anything. What do you think?

Thanks Daniel it's much clearer now.
I think it would be better to remove the hack and change nuspec. As you said the lib automatically auto cancels previous requests so it's quite safe to do so.

Ok, if canceling a lot of requests is fine, we could merge it. :) But don't change dependencies to XF >-1.5, 1.4 is fine too (it'll just cancel requests)

Fine for me!

Ok :)

New nuget pushed: https://www.nuget.org/packages/Xamarin.FFImageLoading.Forms/
Could you give it a try?

Working good. Can be closed :)


DV populators v4.15

Short description:
More details:
What this PR does / why we need it:
Which issue(s) this PR fixes:
Special notes for reviewer:
Bug:

Code already on the branch


Add a list which displays all downloading/downloaded files.

Is your feature request related to a problem? Please describe.
It is annoying to change between downloading list and download list frequently. When I want to checkout the file downloaded, I have to change to downloaded list manually.
Describe the solution you'd like
There should be a list which called All items and display all the work items. Whatever the item is being downloading or has been downloaded.
Describe alternatives you've considered
Nothing.
Additional context
Nothing.

I've started to read the code and stuff. I'll work on this one as I think it's a good first issue.

Here's what I've made by adding something like this:
fetchAllTaskList (params = {}) {
  const { offset = 0, num = 20, keys } = params
  const activeArgs = compactUndefined([keys])
  const waitingArgs = compactUndefined([offset, num, keys])
  const stoppedArgs = compactUndefined([offset, num, keys])
  return new Promise((resolve, reject) => {
    this.client.multicall([
      [ 'aria2.tellActive', ...activeArgs ],
      [ 'aria2.tellWaiting', ...waitingArgs ],
      [ 'aria2.tellStopped', ...stoppedArgs ]
    ]).then((data) => {
      console.log('fetchAllTaskList data', data)
      const result = mergeTaskResult(data)
      resolve(result)
    }).catch((err) => {
      console.log('fetchAllTaskList fail===>', err)
      reject(err)
    })
  })
}

And here's the result:

But I've got a question here. Are the results here sorted by some date? It doesn't look like that. It's just sorted by the aria2 RPC multicall order and the mergeTaskResult fn just concats the results. Do we have any method or something to sort the results?


Add Test with Coverage

For better maintainability of this library.

Vue Horizontal is created to replace this project entirely. Open source and MIT licensed as well: https://github.com/fuxingloh/vue-horizontal do check it out and give it a start.

With E2E Chrome/Edge/Firefox testing to make sure it work as expected.
SPA/SSG/SSR lifecycle to ensure SSR/SSG works as expected.
Heavily documentated


HBASE-28621 PrefixFilter should use SEEK_NEXT_USING_HINT

This is the backport of https://github.com/apache/hbase/pull/6361 to branch-2.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 45s

Docker mode activated.

-0 :warning:
yetus
0m  5s

Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --author-ignore-list --blanks-eol-ignore-file --blanks-tabs-ignore-file --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+0 :ok:
mvndep
0m  9s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
2m 28s

branch-2 passed

+1 :green_heart:
compile
1m  3s

branch-2 passed

+1 :green_heart:
javadoc
0m 44s

branch-2 passed

+1 :green_heart:
shadedjars
4m 50s

branch has no errors when building our shaded downstream artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 15s

Maven dependency ordering for patch

-1 :x:
mvninstall
1m 12s
/patch-mvninstall-root.txt
root in the patch failed.

-1 :x:
compile
0m 34s
/patch-compile-hbase-server.txt
hbase-server in the patch failed.

-0 :warning:
javac
0m 34s
/patch-compile-hbase-server.txt
hbase-server in the patch failed.

+1 :green_heart:
javadoc
0m 43s

the patch passed

-1 :x:
shadedjars
3m 30s

patch has 20 errors when building our shaded downstream artifacts.

_ Other Tests _

+1 :green_heart:
unit
7m 36s

hbase-client in the patch passed.

-1 :x:
unit
0m 43s
/patch-unit-hbase-server.txt
hbase-server in the patch failed.

26m 12s

Subsystem
Report/Notes

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

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

Optional Tests
javac javadoc unit compile shadedjars

uname
Linux c866a044474b 5.4.0-192-generic #212-Ubuntu SMP Fri Jul 5 09:47:39 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 8060ca1552731ce95ef8b383375d2e46cdc0928b

Default Java
Temurin-1.8.0_412-b08

shadedjars
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6424/1/artifact/yetus-jdk8-hadoop2-check/output/patch-shadedjars.txt

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

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

modules
C: hbase-client hbase-server U: .

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

versions
git=2.34.1 maven=3.9.8

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 51s

Docker mode activated.

-0 :warning:
yetus
0m  4s

Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --author-ignore-list --blanks-eol-ignore-file --blanks-tabs-ignore-file --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+0 :ok:
mvndep
0m 10s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
2m 56s

branch-2 passed

+1 :green_heart:
compile
1m  7s

branch-2 passed

+1 :green_heart:
javadoc
0m 44s

branch-2 passed

+1 :green_heart:
shadedjars
6m  1s

branch has no errors when building our shaded downstream artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 16s

Maven dependency ordering for patch

-1 :x:
mvninstall
1m 26s
/patch-mvninstall-root.txt
root in the patch failed.

-1 :x:
compile
0m 37s
/patch-compile-hbase-server.txt
hbase-server in the patch failed.

-0 :warning:
javac
0m 37s
/patch-compile-hbase-server.txt
hbase-server in the patch failed.

+1 :green_heart:
javadoc
0m 40s

the patch passed

-1 :x:
shadedjars
4m 21s

patch has 20 errors when building our shaded downstream artifacts.

_ Other Tests _

+1 :green_heart:
unit
8m 14s

hbase-client in the patch passed.

-1 :x:
unit
0m 37s
/patch-unit-hbase-server.txt
hbase-server in the patch failed.

29m 38s

Subsystem
Report/Notes

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

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

Optional Tests
javac javadoc unit compile shadedjars

uname
Linux c28326087c07 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
branch-2 / 8060ca1552731ce95ef8b383375d2e46cdc0928b

Default Java
Eclipse Adoptium-11.0.23+9

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

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

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

modules
C: hbase-client hbase-server U: .

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

versions
git=2.34.1 maven=3.9.8

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 21s

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.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
hbaseanti
0m  0s

Patch does not have any anti-patterns.

_ branch-2 Compile Tests _

+0 :ok:
mvndep
0m 10s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
3m 52s

branch-2 passed

+1 :green_heart:
compile
5m 19s

branch-2 passed

+1 :green_heart:
checkstyle
1m  5s

branch-2 passed

+1 :green_heart:
spotbugs
3m  8s

branch-2 passed

+1 :green_heart:
spotless
1m  0s

branch has no errors when running spotless:check.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 18s

Maven dependency ordering for patch

-1 :x:
mvninstall
2m  6s
/patch-mvninstall-root.txt
root in the patch failed.

-1 :x:
compile
1m 42s
/patch-compile-hbase-server.txt
hbase-server in the patch failed.

-0 :warning:
javac
1m 42s
/patch-compile-hbase-server.txt
hbase-server in the patch failed.

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 21s

hbase-client: The patch generated 0 new + 0 unchanged - 5 fixed = 0 total (was 5)

+1 :green_heart:
checkstyle
0m 45s

hbase-server: The patch generated 0 new + 0 unchanged - 1 fixed = 0 total (was 1)

-1 :x:
spotbugs
0m 32s
/patch-spotbugs-hbase-server.txt
hbase-server in the patch failed.

-1 :x:
hadoopcheck
1m 47s

The patch causes 20 errors with Hadoop v2.10.2.

-1 :x:
hadoopcheck
4m  4s

The patch causes 20 errors with Hadoop v3.3.6.

-1 :x:
hadoopcheck
6m 17s

The patch causes 20 errors with Hadoop v3.4.0.

+1 :green_heart:
spotless
0m 54s

patch has no errors when running spotless:check.

_ Other Tests _

+1 :green_heart:
asflicense
0m 17s

The patch does not generate ASF License warnings.

32m  6s

Subsystem
Report/Notes

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

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

Optional Tests
dupname asflicense javac spotbugs checkstyle codespell detsecrets compile hadoopcheck hbaseanti spotless

uname
Linux b0d2d056299b 5.4.0-192-generic #212-Ubuntu SMP Fri Jul 5 09:47:39 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 8060ca1552731ce95ef8b383375d2e46cdc0928b

Default Java
Eclipse Adoptium-11.0.23+9

hadoopcheck
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6424/1/artifact/yetus-general-check/output/patch-javac-2.10.2.txt

hadoopcheck
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6424/1/artifact/yetus-general-check/output/patch-javac-3.3.6.txt

hadoopcheck
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6424/1/artifact/yetus-general-check/output/patch-javac-3.4.0.txt

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

modules
C: hbase-client hbase-server U: .

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

versions
git=2.34.1 maven=3.9.8 spotbugs=4.7.3

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 21s

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.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
hbaseanti
0m  0s

Patch does not have any anti-patterns.

_ branch-2 Compile Tests _

+0 :ok:
mvndep
0m 12s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
4m  3s

branch-2 passed

+1 :green_heart:
compile
4m 26s

branch-2 passed

+1 :green_heart:
checkstyle
1m  1s

branch-2 passed

+1 :green_heart:
spotbugs
3m 15s

branch-2 passed

+1 :green_heart:
spotless
1m  2s

branch has no errors when running spotless:check.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 13s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m 49s

the patch passed

+1 :green_heart:
compile
3m 47s

the patch passed

+1 :green_heart:
javac
3m 47s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 18s

hbase-client: The patch generated 0 new + 0 unchanged - 5 fixed = 0 total (was 5)

+1 :green_heart:
checkstyle
0m 36s

hbase-server: The patch generated 0 new + 0 unchanged - 1 fixed = 0 total (was 1)

+1 :green_heart:
spotbugs
2m 42s

the patch passed

+1 :green_heart:
hadoopcheck
14m 39s

Patch does not cause any errors with Hadoop 2.10.2 or 3.3.6 3.4.0.

+1 :green_heart:
spotless
0m 45s

patch has no errors when running spotless:check.

_ Other Tests _

+1 :green_heart:
asflicense
0m 21s

The patch does not generate ASF License warnings.

43m 25s

Subsystem
Report/Notes

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

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

Optional Tests
dupname asflicense javac spotbugs checkstyle codespell detsecrets compile hadoopcheck hbaseanti spotless

uname
Linux 766178e3538b 5.4.0-192-generic #212-Ubuntu SMP Fri Jul 5 09:47:39 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / f7f25c5064d2746c3414f5f54c6958165bab1909

Default Java
Eclipse Adoptium-11.0.23+9

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

modules
C: hbase-client hbase-server U: .

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

versions
git=2.34.1 maven=3.9.8 spotbugs=4.7.3

Powered by
Apache Yetus 0.15.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.

-0 :warning:
yetus
0m  6s

Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --author-ignore-list --blanks-eol-ignore-file --blanks-tabs-ignore-file --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+0 :ok:
mvndep
0m  9s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
2m 28s

branch-2 passed

+1 :green_heart:
compile
1m  4s

branch-2 passed

+1 :green_heart:
javadoc
0m 45s

branch-2 passed

+1 :green_heart:
shadedjars
4m 47s

branch has no errors when building our shaded downstream artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 15s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 25s

the patch passed

+1 :green_heart:
compile
1m  5s

the patch passed

+1 :green_heart:
javac
1m  5s

the patch passed

+1 :green_heart:
javadoc
0m 44s

the patch passed

+1 :green_heart:
shadedjars
4m 44s

patch has no errors when building our shaded downstream artifacts.

_ Other Tests _

+1 :green_heart:
unit
7m 25s

hbase-client in the patch passed.

+1 :green_heart:
unit
224m 10s

hbase-server in the patch passed.

255m 36s

Subsystem
Report/Notes

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

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

Optional Tests
javac javadoc unit compile shadedjars

uname
Linux d5f8e0bb9d76 5.4.0-192-generic #212-Ubuntu SMP Fri Jul 5 09:47:39 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / f7f25c5064d2746c3414f5f54c6958165bab1909

Default Java
Temurin-1.8.0_412-b08

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

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

modules
C: hbase-client hbase-server U: .

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

versions
git=2.34.1 maven=3.9.8

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 53s

Docker mode activated.

-0 :warning:
yetus
0m  7s

Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --author-ignore-list --blanks-eol-ignore-file --blanks-tabs-ignore-file --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+0 :ok:
mvndep
0m 10s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
3m 49s

branch-2 passed

+1 :green_heart:
compile
1m 42s

branch-2 passed

+1 :green_heart:
javadoc
0m 56s

branch-2 passed

+1 :green_heart:
shadedjars
5m 56s

branch has no errors when building our shaded downstream artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 12s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m 27s

the patch passed

+1 :green_heart:
compile
1m 22s

the patch passed

+1 :green_heart:
javac
1m 22s

the patch passed

+1 :green_heart:
javadoc
0m 51s

the patch passed

+1 :green_heart:
shadedjars
5m 33s

patch has no errors when building our shaded downstream artifacts.

_ Other Tests _

+1 :green_heart:
unit
7m 37s

hbase-client in the patch passed.

+1 :green_heart:
unit
219m 18s

hbase-server in the patch passed.

256m 22s

Subsystem
Report/Notes

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

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

Optional Tests
javac javadoc unit compile shadedjars

uname
Linux 8d7a607fab28 5.4.0-195-generic #215-Ubuntu SMP Fri Aug 2 18:28:05 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / f7f25c5064d2746c3414f5f54c6958165bab1909

Default Java
Eclipse Adoptium-17.0.11+9

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

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

modules
C: hbase-client hbase-server U: .

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

versions
git=2.34.1 maven=3.9.8

Powered by
Apache Yetus 0.15.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.

-0 :warning:
yetus
0m  6s

Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --author-ignore-list --blanks-eol-ignore-file --blanks-tabs-ignore-file --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+0 :ok:
mvndep
0m 12s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
2m 52s

branch-2 passed

+1 :green_heart:
compile
1m  5s

branch-2 passed

+1 :green_heart:
javadoc
0m 40s

branch-2 passed

+1 :green_heart:
shadedjars
6m  1s

branch has no errors when building our shaded downstream artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 13s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m  1s

the patch passed

+1 :green_heart:
compile
1m  8s

the patch passed

+1 :green_heart:
javac
1m  8s

the patch passed

+1 :green_heart:
javadoc
0m 41s

the patch passed

+1 :green_heart:
shadedjars
6m  2s

patch has no errors when building our shaded downstream artifacts.

_ Other Tests _

+1 :green_heart:
unit
8m 21s

hbase-client in the patch passed.

+1 :green_heart:
unit
227m 44s

hbase-server in the patch passed.

263m 57s

Subsystem
Report/Notes

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

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

Optional Tests
javac javadoc unit compile shadedjars

uname
Linux 1ba2324df58a 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
branch-2 / f7f25c5064d2746c3414f5f54c6958165bab1909

Default Java
Eclipse Adoptium-11.0.23+9

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

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

modules
C: hbase-client hbase-server U: .

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

versions
git=2.34.1 maven=3.9.8

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
1m 13s

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.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
hbaseanti
0m  0s

Patch does not have any anti-patterns.

_ branch-2 Compile Tests _

+0 :ok:
mvndep
0m 11s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
4m  5s

branch-2 passed

+1 :green_heart:
compile
4m 33s

branch-2 passed

+1 :green_heart:
checkstyle
1m  8s

branch-2 passed

+1 :green_heart:
spotbugs
2m 50s

branch-2 passed

+1 :green_heart:
spotless
0m 57s

branch has no errors when running spotless:check.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 16s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m 22s

the patch passed

+1 :green_heart:
compile
4m  8s

the patch passed

+1 :green_heart:
javac
4m  8s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 21s

hbase-client: The patch generated 0 new + 0 unchanged - 5 fixed = 0 total (was 5)

+1 :green_heart:
checkstyle
0m 41s

hbase-server: The patch generated 0 new + 0 unchanged - 1 fixed = 0 total (was 1)

+1 :green_heart:
spotbugs
2m 42s

the patch passed

+1 :green_heart:
hadoopcheck
15m 35s

Patch does not cause any errors with Hadoop 2.10.2 or 3.3.6 3.4.0.

+1 :green_heart:
spotless
0m 44s

patch has no errors when running spotless:check.

_ Other Tests _

+1 :green_heart:
asflicense
0m 22s

The patch does not generate ASF License warnings.

45m 22s

Subsystem
Report/Notes

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

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

Optional Tests
dupname asflicense javac spotbugs checkstyle codespell detsecrets compile hadoopcheck hbaseanti spotless

uname
Linux 835355613ee5 5.4.0-195-generic #215-Ubuntu SMP Fri Aug 2 18:28:05 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 52a288df5d3d1f5f307b56c64c75e1697edab8ef

Default Java
Eclipse Adoptium-11.0.23+9

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

modules
C: hbase-client hbase-server U: .

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

versions
git=2.34.1 maven=3.9.8 spotbugs=4.7.3

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 45s

Docker mode activated.

-0 :warning:
yetus
0m  4s

Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --author-ignore-list --blanks-eol-ignore-file --blanks-tabs-ignore-file --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+0 :ok:
mvndep
0m 11s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
3m 17s

branch-2 passed

+1 :green_heart:
compile
1m 19s

branch-2 passed

+1 :green_heart:
javadoc
0m 45s

branch-2 passed

+1 :green_heart:
shadedjars
6m  5s

branch has no errors when building our shaded downstream artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 16s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m  1s

the patch passed

+1 :green_heart:
compile
1m 19s

the patch passed

+1 :green_heart:
javac
1m 19s

the patch passed

+1 :green_heart:
javadoc
0m 45s

the patch passed

+1 :green_heart:
shadedjars
6m  4s

patch has no errors when building our shaded downstream artifacts.

_ Other Tests _

+1 :green_heart:
unit
8m 14s

hbase-client in the patch passed.

+1 :green_heart:
unit
209m 37s

hbase-server in the patch passed.

246m 33s

Subsystem
Report/Notes

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

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

Optional Tests
javac javadoc unit compile shadedjars

uname
Linux 800620b04066 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
branch-2 / 52a288df5d3d1f5f307b56c64c75e1697edab8ef

Default Java
Eclipse Adoptium-17.0.11+9

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

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

modules
C: hbase-client hbase-server U: .

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

versions
git=2.34.1 maven=3.9.8

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 24s

Docker mode activated.

-0 :warning:
yetus
0m  5s

Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --author-ignore-list --blanks-eol-ignore-file --blanks-tabs-ignore-file --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+0 :ok:
mvndep
0m 17s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
4m 12s

branch-2 passed

+1 :green_heart:
compile
1m 59s

branch-2 passed

+1 :green_heart:
javadoc
1m  0s

branch-2 passed

+1 :green_heart:
shadedjars
7m 40s

branch has no errors when building our shaded downstream artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 16s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m 45s

the patch passed

+1 :green_heart:
compile
1m 44s

the patch passed

+1 :green_heart:
javac
1m 44s

the patch passed

+1 :green_heart:
javadoc
1m  4s

the patch passed

+1 :green_heart:
shadedjars
7m 44s

patch has no errors when building our shaded downstream artifacts.

_ Other Tests _

+1 :green_heart:
unit
8m 31s

hbase-client in the patch passed.

-1 :x:
unit
232m 37s
/patch-unit-hbase-server.txt
hbase-server in the patch failed.

276m 15s

Subsystem
Report/Notes

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

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

Optional Tests
javac javadoc unit compile shadedjars

uname
Linux b659cdfb5cff 5.4.0-192-generic #212-Ubuntu SMP Fri Jul 5 09:47:39 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 52a288df5d3d1f5f307b56c64c75e1697edab8ef

Default Java
Temurin-1.8.0_412-b08

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

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

modules
C: hbase-client hbase-server U: .

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

versions
git=2.34.1 maven=3.9.8

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 52s

Docker mode activated.

-0 :warning:
yetus
0m  5s

Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --author-ignore-list --blanks-eol-ignore-file --blanks-tabs-ignore-file --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+0 :ok:
mvndep
0m 23s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
4m 15s

branch-2 passed

+1 :green_heart:
compile
1m  7s

branch-2 passed

+1 :green_heart:
javadoc
0m 42s

branch-2 passed

+1 :green_heart:
shadedjars
6m 15s

branch has no errors when building our shaded downstream artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 16s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m 50s

the patch passed

+1 :green_heart:
compile
1m 23s

the patch passed

+1 :green_heart:
javac
1m 23s

the patch passed

+1 :green_heart:
javadoc
0m 51s

the patch passed

+1 :green_heart:
shadedjars
6m 51s

patch has no errors when building our shaded downstream artifacts.

_ Other Tests _

+1 :green_heart:
unit
8m 40s

hbase-client in the patch passed.

-1 :x:
unit
260m  0s
/patch-unit-hbase-server.txt
hbase-server in the patch failed.

301m  3s

Subsystem
Report/Notes

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

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

Optional Tests
javac javadoc unit compile shadedjars

uname
Linux 92da34cdb802 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
branch-2 / 52a288df5d3d1f5f307b56c64c75e1697edab8ef

Default Java
Eclipse Adoptium-11.0.23+9

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

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

modules
C: hbase-client hbase-server U: .

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

versions
git=2.34.1 maven=3.9.8

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

This message was automatically generated.

The errors are unrelated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
1m  3s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
hbaseanti
0m  0s

Patch does not have any anti-patterns.

_ branch-2 Compile Tests _

+0 :ok:
mvndep
0m 16s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
4m 28s

branch-2 passed

+1 :green_heart:
compile
5m  8s

branch-2 passed

+1 :green_heart:
checkstyle
1m 25s

branch-2 passed

+1 :green_heart:
spotbugs
3m 18s

branch-2 passed

+1 :green_heart:
spotless
1m  0s

branch has no errors when running spotless:check.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 16s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
4m 16s

the patch passed

+1 :green_heart:
compile
5m 38s

the patch passed

+1 :green_heart:
javac
5m 38s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 27s

hbase-client: The patch generated 0 new + 0 unchanged - 5 fixed = 0 total (was 5)

+1 :green_heart:
checkstyle
0m 54s

hbase-server: The patch generated 0 new + 0 unchanged - 1 fixed = 0 total (was 1)

+1 :green_heart:
spotbugs
4m 17s

the patch passed

+1 :green_heart:
hadoopcheck
21m 49s

Patch does not cause any errors with Hadoop 2.10.2 or 3.3.6 3.4.0.

+1 :green_heart:
spotless
0m 59s

patch has no errors when running spotless:check.

_ Other Tests _

+1 :green_heart:
asflicense
0m 21s

The patch does not generate ASF License warnings.

58m  1s

Subsystem
Report/Notes

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

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

Optional Tests
dupname asflicense javac spotbugs checkstyle codespell detsecrets compile hadoopcheck hbaseanti spotless

uname
Linux d55ec6950d08 5.4.0-200-generic #220-Ubuntu SMP Fri Sep 27 13:19:16 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / ee8446985a0cbcd2859d00d17e2091ef241e17e6

Default Java
Eclipse Adoptium-11.0.23+9

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

modules
C: hbase-client hbase-server U: .

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

versions
git=2.34.1 maven=3.9.8 spotbugs=4.7.3

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
8m 20s

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.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
hbaseanti
0m  0s

Patch does not have any anti-patterns.

_ branch-2 Compile Tests _

+0 :ok:
mvndep
0m 10s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
4m 25s

branch-2 passed

+1 :green_heart:
compile
5m  0s

branch-2 passed

+1 :green_heart:
checkstyle
1m  8s

branch-2 passed

+1 :green_heart:
spotbugs
2m 53s

branch-2 passed

+1 :green_heart:
spotless
0m 54s

branch has no errors when running spotless:check.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 16s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
5m 58s

the patch passed

+1 :green_heart:
compile
4m 30s

the patch passed

+1 :green_heart:
javac
4m 30s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 19s

hbase-client: The patch generated 0 new + 0 unchanged - 5 fixed = 0 total (was 5)

+1 :green_heart:
checkstyle
0m 45s

hbase-server: The patch generated 0 new + 0 unchanged - 1 fixed = 0 total (was 1)

+1 :green_heart:
spotbugs
3m 12s

the patch passed

+1 :green_heart:
hadoopcheck
22m 51s

Patch does not cause any errors with Hadoop 2.10.2 or 3.3.6 3.4.0.

+1 :green_heart:
spotless
0m 50s

patch has no errors when running spotless:check.

_ Other Tests _

+1 :green_heart:
asflicense
0m 22s

The patch does not generate ASF License warnings.

64m 33s

Subsystem
Report/Notes

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

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

Optional Tests
dupname asflicense javac spotbugs checkstyle codespell detsecrets compile hadoopcheck hbaseanti spotless

uname
Linux dc4cacb34fb1 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
branch-2 / a8cd79dbadc1ea77a1a84421703e6bf9d662e84f

Default Java
Eclipse Adoptium-11.0.23+9

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

modules
C: hbase-client hbase-server U: .

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

versions
git=2.34.1 maven=3.9.8 spotbugs=4.7.3

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
1m 14s

Docker mode activated.

-0 :warning:
yetus
0m  5s

Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --author-ignore-list --blanks-eol-ignore-file --blanks-tabs-ignore-file --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+0 :ok:
mvndep
0m 14s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
4m 36s

branch-2 passed

+1 :green_heart:
compile
1m 52s

branch-2 passed

+1 :green_heart:
javadoc
1m  4s

branch-2 passed

+1 :green_heart:
shadedjars
7m 55s

branch has no errors when building our shaded downstream artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 19s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m 56s

the patch passed

+1 :green_heart:
compile
1m 46s

the patch passed

+1 :green_heart:
javac
1m 46s

the patch passed

+1 :green_heart:
javadoc
1m  8s

the patch passed

+1 :green_heart:
shadedjars
7m 38s

patch has no errors when building our shaded downstream artifacts.

_ Other Tests _

+1 :green_heart:
unit
9m  7s

hbase-client in the patch passed.

+1 :green_heart:
unit
295m  6s

hbase-server in the patch passed.

341m 13s

Subsystem
Report/Notes

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

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

Optional Tests
javac javadoc unit compile shadedjars

uname
Linux b3c1519c0fc2 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
branch-2 / a8cd79dbadc1ea77a1a84421703e6bf9d662e84f

Default Java
Eclipse Adoptium-11.0.23+9

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

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

modules
C: hbase-client hbase-server U: .

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

versions
git=2.34.1 maven=3.9.8

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 58s

Docker mode activated.

-0 :warning:
yetus
0m  4s

Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --author-ignore-list --blanks-eol-ignore-file --blanks-tabs-ignore-file --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+0 :ok:
mvndep
0m 20s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
4m 16s

branch-2 passed

+1 :green_heart:
compile
2m  9s

branch-2 passed

+1 :green_heart:
javadoc
1m 17s

branch-2 passed

+1 :green_heart:
shadedjars
7m 35s

branch has no errors when building our shaded downstream artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 12s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
4m  6s

the patch passed

+1 :green_heart:
compile
2m  1s

the patch passed

+1 :green_heart:
javac
2m  1s

the patch passed

+1 :green_heart:
javadoc
1m  1s

the patch passed

+1 :green_heart:
shadedjars
7m 53s

patch has no errors when building our shaded downstream artifacts.

_ Other Tests _

+1 :green_heart:
unit
7m 45s

hbase-client in the patch passed.

-1 :x:
unit
285m  5s
/patch-unit-hbase-server.txt
hbase-server in the patch failed.

330m 18s

Subsystem
Report/Notes

Docker
ClientAPI=1.47 ServerAPI=1.47 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6424/5/artifact/yetus-jdk17-hadoop3-check/output/Dockerfile

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

Optional Tests
javac javadoc unit compile shadedjars

uname
Linux 8cd71615e9ff 5.4.0-200-generic #220-Ubuntu SMP Fri Sep 27 13:19:16 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / a8cd79dbadc1ea77a1a84421703e6bf9d662e84f

Default Java
Eclipse Adoptium-17.0.11+9

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

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

modules
C: hbase-client hbase-server U: .

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

versions
git=2.34.1 maven=3.9.8

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
16m 34s

Docker mode activated.

-0 :warning:
yetus
0m 11s

Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --author-ignore-list --blanks-eol-ignore-file --blanks-tabs-ignore-file --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+0 :ok:
mvndep
1m 50s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
5m 20s

branch-2 passed

+1 :green_heart:
compile
1m 15s

branch-2 passed

+1 :green_heart:
javadoc
1m  3s

branch-2 passed

+1 :green_heart:
shadedjars
6m 53s

branch has no errors when building our shaded downstream artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 13s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
5m 31s

the patch passed

+1 :green_heart:
compile
1m  9s

the patch passed

+1 :green_heart:
javac
1m  9s

the patch passed

+1 :green_heart:
javadoc
0m 48s

the patch passed

+1 :green_heart:
shadedjars
6m 40s

patch has no errors when building our shaded downstream artifacts.

_ Other Tests _

+1 :green_heart:
unit
8m 28s

hbase-client in the patch passed.

-1 :x:
unit
502m 43s
/patch-unit-hbase-server.txt
hbase-server in the patch failed.

577m 14s

Subsystem
Report/Notes

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

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

Optional Tests
javac javadoc unit compile shadedjars

uname
Linux 578a53e217bb 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
branch-2 / a8cd79dbadc1ea77a1a84421703e6bf9d662e84f

Default Java
Temurin-1.8.0_412-b08

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

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

modules
C: hbase-client hbase-server U: .

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

versions
git=2.34.1 maven=3.9.8

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

This message was automatically generated.


Using a toolchain file "sometimes" broke until cmake-kits.json is not edited.

Brief Issue Summary
I use cmake to cross compile for an embedded arm custom board. I usually specify a toolchain on the command line and then I open eclipse with the generated project.
During test for evaluating the possibility to switch on Code I found out that the toolchain file is not used while trying to compile the test program.
My toolchain file looks contains:
SET(CMAKE_TRY_COMPILE_TARGET_TYPE STATIC_LIBRARY)

as defined in the documentation and is used during cross compilation in order to avoid linking errors with libraries not present before cmake configuration.
https://cmake.org/cmake/help/v3.10/variable/CMAKE_TRY_COMPILE_TARGET_TYPE.html
From Code I see often an error related to the fact that -rdynamic is not available while compiling a test program. So during cmake initial configuration. If I edit the cmake-kits.json and alter it a while a new cmake running is correct.

[cmake]     Run Build Command:"/usr/bin/ninja" "cmTC_acd83"
[cmake]     [1/2] Building C object CMakeFiles/cmTC_acd83.dir/testCCompiler.c.obj
[cmake]     [2/2] Linking C executable cmTC_acd83
[cmake]     FAILED: cmTC_acd83
[cmake]     : && /home/andrea/gcc-arm-none-eabi-7-2017-q4-major/bin/arm-none-eabi-gcc-7.2.1   -rdynamic CMakeFiles/cmTC_acd83.dir/testCCompiler.c.obj  -o cmTC_acd83   && :
[cmake]     arm-none-eabi-gcc-7.2.1: error: unrecognized command line option '-rdynamic'
[cmake]     ninja: build stopped: subcommand failed.

This usually happen switching kit but sometimes it just happen while iterating in the edit code => compile etc.
For fixing it I added twice the toolchain value and my cmake-kits.json looks like this:

{
"name": "GCC for arm-none-eabi 7.2.1",
"keep": true,
"cmakeSettings": {
"CMAKE_TOOLCHAIN_FILE": "/home/andrea/workspace/CanDeckAlpine/arm_gcc.cmake"
},
"toolchainFile": "/home/andrea/workspace/CanDeckAlpine/arm_gcc.cmake",
"compilers": {
"C": "/home/andrea/gcc-arm-none-eabi-7-2017-q4-major/bin/arm-none-eabi-gcc-7.2.1"
}

Commenting and uncommenting the toolchain file let the program to re-parse the kit and it works for a while.
The "keep true" flag is not causing errors or solving them.
Expected:
That the cmake settings are not altered from execution to execution.
Platform and Versions

Operating System: Ubuntu
CMake Version: 3.10.2
VSCode Version: 1.24.1
CMake Tools Extension Version: 1.0.1
Compiler/Toolchain: arm-none-eabi-gcc-7.2.1

Sorry for the delay. I just returned from a vacation.
Setting the toolchainFile option in the kit should be enough. You can omit CMAKE_TOOLCHAIN_FILE in the cmakeSettings key. Also, if your toolchain file sets up compilers you should be fine to omit the compilers section.
The keep option only appears if a compiler path refers to a non-existent file. Does the C compiler path refer to an existing file?
If you make these changes or tweaks, does the behavior change at all?

Hi,
thank you for your kind reply.
I am sorry but I am not a English native speaker. Maybe I expressed myself wrong.
I already tried to change the values in the config file without success.
I do not have access until Monday to the documents.
I can post the toolchain file on Monday but I use it from the command line without any problem.
It looks like to me that cmake server mode does not receive the toolchain file after a reconfigure.
Basically the steps I did for hitting the problem are:

configure cmake-kits.json using the toolchain file.
configure cmake
compile the sources
add a new file to CMakeLists.txt or edit the file someway
compile (so reconfigure cmake).
at point 5 cmake pops the error

arm-none-eabi-gcc-7.2.1: error: unrecognized command line option '-rdynamic'

(which means that the toolchain file is not used while reconfiguring cmake.)
This error is avoided using in the toolchain file of the command

SET(CMAKE_TRY_COMPILE_TARGET_TYPE STATIC_LIBRARY)

This command is used for telling cmake while testing the compiler to not try to compile an executable but a static library.
If at this point I edit again cmake-kits.json or I change the active compiler, the build directory is deleted and recreated from zero.
Setting again the compiler that I want to use allow me to compile correctly. Like being at point 1.
The compiler works correctly until I reach again point 4.
The same behaviour is observed on 2 different computers, both running Ubuntu.
I tried different projects, every project uses the same toolchain file because they target the same processor.
Thank you and sorry for the long post.
best regards
Andrea

Could you provide a minimal test case to reproduce the issue? I'm not sure what might be happening here.

Of course...

Download a toolchain from https://developer.arm.com/open-source/gnu-toolchain/gnu-rm/downloads
the one currently active in my project is gcc-arm-none-eabi-7-2017-q4-major.
Insert the extracted directory in the PATH variable
create a toolchain file. I am using:

SET(CMAKE_SYSTEM_NAME Generic)
SET(CMAKE_SYSTEM_VERSION 1)
SET(CMAKE_SYSTEM_PROCESSOR arm-eabi)
SET(CMAKE_C_COMPILER arm-none-eabi-gcc)
SET(CMAKE_CXX_COMPILER arm-none-eabi-g++)
SET(CMAKE_TRY_COMPILE_TARGET_TYPE STATIC_LIBRARY)

Using a simple hello world

#include <stdio.h>
int main(int argc, char **argv){
printf("Hello world!\r\n");
return 0;
}

Using a simple CMakeLists.txt

Project(CandeckAlpine C ASM)
cmake_minimum_required(VERSION 3.8)
add_executable(hello main.c)

Add to the cmake-kits.json the correct configuration for the arm compiler.
Mine looks like this one:

[
{
"name": "GCC 7.3.0",
"compilers": {
"CXX": "/usr/bin/g++-7",
"C": "/usr/bin/gcc-7"
}
},
{
"name": "GCC for arm-none-eabi 7.2.1",
"toolchainFile": "/home/andrea/workspace/CanDeckAlpine/arm_gcc.cmake",
"compilers": {
"C": "/home/andrea/gcc-arm-none-eabi-7-2017-q4-major/bin/arm-none-eabi-gcc-7.2.1"
}
}
]

Try to compile for GCC 7.3.0
The compilation is successful.

Switch to GCC 7.2.1 ARM and compile the code.
The compilar complains about missing function that is present in custom libraries depending on the vendor. THIS IS NORMAL. IT IS NOT THE PROBLEM THAT I AM NOTICING.

Edit CMakeLists.txt in some way. The change I made in the example is:
add

target_link_libraries(hello m)

at the end of the file.
It now looks like:

Project(CandeckAlpine C ASM)
cmake_minimum_required(VERSION 3.8)
add_executable(hello main.c)
target_link_libraries(hello m)

Try to compile the code. The output I get is:

[cmake] Configuring done
[cmake] You have changed variables that require your cache to be deleted.
[cmake] Configure will be re-run and you may have to reset some variables.
[cmake] The following variables have changed:
[cmake] CMAKE_C_COMPILER= /home/andrea/gcc-arm-none-eabi-7-2017-q4-major/bin/arm-none-eabi-gcc-7.2.1
[cmake]
[cmake] The C compiler identification is GNU 7.2.1
[cmake] The ASM compiler identification is GNU
[cmake] Found assembler: /home/andrea/gcc-arm-none-eabi-7-2017-q4-major/bin/arm-none-eabi-gcc
[cmake] Check for working C compiler: /home/andrea/gcc-arm-none-eabi-7-2017-q4-major/bin/arm-none-eabi-gcc-7.2.1
[cmake] Check for working C compiler: /home/andrea/gcc-arm-none-eabi-7-2017-q4-major/bin/arm-none-eabi-gcc-7.2.1 -- broken
[cmake] CMake Error at /usr/share/cmake-3.10/Modules/CMakeTestCCompiler.cmake:52 (message):
[cmake]   The C compiler
[cmake]
[cmake]     "/home/andrea/gcc-arm-none-eabi-7-2017-q4-major/bin/arm-none-eabi-gcc-7.2.1"
[cmake]
[cmake]   is not able to compile a simple test program.
[cmake]
[cmake]   It fails with the following output:
[cmake]
[cmake]     Change Dir: /home/andrea/workspace/HelloWorld/build/CMakeFiles/CMakeTmp
[cmake]
[cmake]     Run Build Command:"/usr/bin/ninja" "cmTC_a3702"
[cmake]     [1/2] Building C object CMakeFiles/cmTC_a3702.dir/testCCompiler.c.obj
[cmake]     [2/2] Linking C executable cmTC_a3702
[cmake]     FAILED: cmTC_a3702
[cmake]     : && /home/andrea/gcc-arm-none-eabi-7-2017-q4-major/bin/arm-none-eabi-gcc-7.2.1   -rdynamic CMakeFiles/cmTC_a3702.dir/testCCompiler.c.obj  -o cmTC_a3702   && :
[cmake]     arm-none-eabi-gcc-7.2.1: error: unrecognized command line option '-rdynamic'
[cmake]     ninja: build stopped: subcommand failed.
[cmake]
[cmake]
[cmake]
[cmake]
[cmake]   CMake will not be able to correctly generate this project.
[cmake] Call Stack (most recent call first):
[cmake]   CMakeLists.txt:1 (Project)
[cmake]
[cmake]
[cmake] Configuring incomplete, errors occurred!
[cmake] See also "/home/andrea/workspace/HelloWorld/build/CMakeFiles/CMakeOutput.log".
[cmake] See also "/home/andrea/workspace/HelloWorld/build/CMakeFiles/CMakeError.log".
[cms-driver] Error during CMake configure: [cmake-server] Configuration failed.

As you can see cmake is executing without the use of the toolchain file definition

SET(CMAKE_TRY_COMPILE_TARGET_TYPE STATIC_LIBRARY)

Switch on the host compiler again

[driver] Switching to kit: GCC 7.3.0
[cms-client] Configuring using the "Ninja" CMake generator

and compile the software that compiles correctly.

Switch again on arm compiler

[cmake] The C compiler identification is GNU 7.2.1
[cmake] The ASM compiler identification is GNU
[cmake] Found assembler: /home/andrea/gcc-arm-none-eabi-7-2017-q4-major/bin/arm-none-eabi-gcc
[cmake] Check for working C compiler: /home/andrea/gcc-arm-none-eabi-7-2017-q4-major/bin/arm-none-eabi-gcc
[cmake] Check for working C compiler: /home/andrea/gcc-arm-none-eabi-7-2017-q4-major/bin/arm-none-eabi-gcc -- works
[cmake] Detecting C compiler ABI info
[cmake] Detecting C compiler ABI info - done
[cmake] Detecting C compile features
[cmake] Detecting C compile features - done
[cmake] Configuring done
[cmake] Generating done
[build] Starting build
[proc] Executing command: /usr/bin/cmake --build /home/andrea/workspace/HelloWorld/build --config Debug --target all -- -j 10
[build] [1/2] Building C object CMakeFiles/hello.dir/main.c.obj
[build] [2/2] Linking C executable hello
[build] FAILED: hello
...

The compilation starts correctly and the error visible is not related to this bug report.
The problem I am facing is that after cmake is configured, a change to the CMakeLists.txt file breaks the compiler. I need to switch compiler to host and then switch back to arm compiler for passing the cmake configuration step.
I don't think to be able to provide a more detailed step by step of this one.
By the way if you need to ask for some test or changes to be made I am available to try them.
Thank you
Andrea

Thanks for the in-depth test case! I'll evaluate and see if I can get a fix for 1.1


feat: port Algebra.Module.GradedModule

In Algebra.DirectSum.Decomposition, a simps was commented because it was causing a recurrence loop. However, one of the lemma that it generates is needed in this file, so I put the simps back (and fixed the loop)
At the end of the file, the local instance GradedModule.isModule was causing a lot of troubles. (It was in fact marked as a dangerous instance in Mathlib3). I removed it and declared it directly in the only result using it, see this Zulip thread

bors merge


Metadata module support for 0.46 NFT api

Summary
Cosmos SDK v0.46.x adds a new NFT module that needs to be backed by a chain specific implementation.  Add support for this new API to the metadata module
Problem Definition
The new NFT module provides an api that needs to be implemented/supported.
Proposal
Extend the scopes, scope specifications to include the required extra properties for the NFT apis.
Spec: https://github.com/cosmos/cosmos-sdk/tree/master/x/nft/spec

For Admin Use

[ ] Not duplicate issue
[ ] Appropriate labels applied
[ ] Appropriate contributors tagged
[ ] Contributor assigned/self-assigned

This adds ERC-721 support to the metadata module (essentially).

We will want to retain the compatibility with x/nft style basic NFTs... that means that the basic implementation that supports user supplied identifiers that are not in our metadata/scope format should be allowed ... I suppose that means we have two types of NFTs ... basic/generic, and provenance/enhanced??

We can probably implement this after we create a smart contract that implements ERC721 ... then we can implement this API on top of metadata so it is interoperable.  We will probably need some more indexes to return counts for stuff like number of scopes of a given scope-spec (TotalSupply).
This feature will really show the power of using the metadata module to back smart contract based NFTs because all different contract results will be queryable by this chain wide module api.

See #1487 for the issue to make the smart contract for ERC721

Based on some further research there are a few major pieces required
// Class defines the interface specifications of collection that can be transferred across chains.  IBC transfer of NFTs relies on the following expected interface:
type Class interface {
	GetID() string
	GetURI() string
	GetData() string
}

While the NFT module spec provides the following:
message Class {
  string id          = 1;
  string name        = 2;
  string symbol      = 3;
  string description = 4;
  string uri         = 5;
  string uri_hash    = 6;
  google.protobuf.Any data = 7;
}

For a class on the metadata module we have a Scope Specification.  The ID in this case will be the MetadataAddress instance of the specific scope specification.  The URI comes from the Description property which contains website_uri (unfortunate name) however we don't have the associated uri_hash property that would generally be associated with it.  There is no "symbol" for the NFT.
// NFT defines the interface specification of nft that can be transferred across chains
type NFT interface {
	GetClassID() string
	GetID() string
	GetURI() string
	GetData() string
}

The associated data structure of the NFT module is
message NFT {
  string class_id           = 1;
  string id                 = 2;
  string uri                = 3;
  string uri_hash           = 4;
  google.protobuf.Any data  = 10;
}
``
Of these properties the class_id is the scope specification... the id is the scope metadata address.  We do not currently have uri+hash concept within our definition.  It would be very useful if the `Record` structure which currently has "input/output" definitions was extended with a `URI` field as an optional to go along with the existing `hash`.

// NFTKeeper defines the expected nft keeper
type NFTKeeper interface {
CreateOrUpdateClass(ctx sdk.Context, classID, classURI string, classData string) error
Mint(ctx sdk.Context, classID, tokenID, tokenURI string, tokenData string, receiver sdk.AccAddress) error
Transfer(ctx sdk.Context, classID string, tokenID string, tokenData string, receiver sdk.AccAddress) error
Burn(ctx sdk.Context, classID string, tokenID string) error
GetOwner(ctx sdk.Context, classID string, tokenID string) sdk.AccAddress
HasClass(ctx sdk.Context, classID string) bool
GetClass(ctx sdk.Context, classID string) (Class, bool)
GetNFT(ctx sdk.Context, classID, tokenID string) (NFT, bool)

}
For the above operations there are some complexities depending on the ownership records on the scope.  If there is more than a single owner or more than one required party it will not be possible to transfer the scope using these interfaces because they do not have a concept of a composite owner.  Create or Update class will not function for generic NFTs when backed by the metadata module due to the lack of 1:1 mapping of these ID values.  That said we should be able to determine if the values provided represent a scope specification and then create the associated entries otherwise error with an unsupported value.  This will allow a zone to transfer records over IBC.  Get Owner, Class, NFT methods are all straight forward.

More docs on the metadata formats: https://docs.opensea.io/docs/metadata-standards


Add German translations for Pet Dogs

Thanks for the help! Merged into develop for the upcoming Pet Dogs 2.0.5.


Using InTheHand.BluetoothLE.dll in .NET6

Dear sirs, I created a simple .Net6 project and added your Nu-Get library there. I am getting:

Is there any way to do something around this?
Should I maybe try to use the WinRT directly?
Thanks,
Kirill

What is your target platform for the project. Because the implementation is platform specific the NuGet contains net6.0-android, net6.0-ios, net6.0-windows10.0.19041.0 etc. If you try to target an older version of Windows or generic .net6.0 there is no implementation and so it will step down to an earlier .net version dll. While technically Bluetooth LE is supported in older Windows 10 SDKs there are some differences and so that version was selected as a baseline.

Thanks for your prompt response. I found what was wrong. I changed from this

to this:

After that is started to compile.
By default Visual Studio is not setting the target OS. IMO this piece should be mentioned somewhere in the 32feet docs or Wikis.

@nref because the library gets its WinRT bindings from having that runtime type set on the assembly it's exposed with the same TFM. The BluetoothLE apis are only available on Windows 10, and the assembly is already marked as compatible down to 10.0.17763.

I can see now that I am preaching to the choir.  🙂


add services.tesslightcurves

Main use case: you have some star, and you want a light-curve. And you
want to be flexible about where you're getting it from.

Sorry for taking a minute. Done. Also tweaked a few defaults in the eleanor DL for it to work more often (tesscut has bugs, apparently).

Thanks! I'll take a look and merge once I have more reliable internet in a couple of days (travelling right now).

Thanks again for the PR! I'll clean this up if required in a bit.


Added more descriptive wording for Slack channel config.

Users sometimes fail to add a # character before the channel's name, which breaks the configuration. I added wording to make this clear.

This still doesn't solve the problem of the user not providing # as a predicate to the channel name.
I think we should detect the presence of # and add it if not present. I'm happy to walk through and discuss the process of writing this code with you.

Agree with @JacobNinja and think someone should write the code instead of changing the wording. After that, the wording should specify that it's optional (otherwise people will wonder)

This seems to have gone stale. Closing.
@jonathancadepowers feel free to re-surface as desired.


⚠ Bofrost.be has degraded performance

In c0b79b3, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1394 ms

Resolved: Bofrost.be performance has improved in ba84029.


ServerType enum?

https://github.com/sql-bi/DaxFormatter/blob/master/src/Dax.Formatter/AnalysisServices/ServerType.cs
Would it make sense to add the following types?
[EnumMember(Value = "AzureAS")]
AzureAnalysisServices,

[EnumMember(Value = "PBI Service")]
PowerBIService,

[EnumMember(Value = "Offline")]
Offline

Added to 1.1.1


What is the vehicle center? how to find  front_edge_to_center & back_edge_to_center?

How to calculate the following values? How is the centre defined for the vehicle?
front_edge_to_center: 1.385
back_edge_to_center: 0.405
left_edge_to_center: 0.430
right_edge_to_center: 0.430

@tanmoy-sabir, the center here means the center of mass of your vehicle

Center of the vehicle could be defined as you want. You just need to compensate the difference into your calibration.
The most often used center:
IMU; center of rear axle; Mass(hard to find)

Seems to be resolved, we will close this issue. If the problem persists, pls feel free to reopen it or create a new one and refer to it.


Allow to download files

Returning 404s depended on the StatusCode stuff in this PR, so I added some commits fixing the windows build, and implementing #32.


Load fixtures from source

Looks good to me. :+1: @lchrusciel your call!

Good for me. Waiting for green build and it si ready for merge.


Won't resize when inherited font size changes

I have a component where users can select font sizes which are set on the parent's style as {fontSize: <computed>}. Unfortunately, changing the parent's font size does not trigger an update and resize in the child.
Before resizing:

After resizing:

I think handling this type of situation requires forcing an update of the component, but there's no public method for doing so. A related problem is when other elements expand or shrink and cause the textarea dimensions to change. (I think handling the general case would require something like this to detect resize events)

Hey, we cannot use element-resize-detector as it creates quite an overhead. Possible solutions are as follow:

you could trigger pass 'invalidating' prop (such as fontSize) to the Textarea component - it should recalculate itself
or we could expose imperative resize method on the component which you could access from its ref

Did you eventually fix your issue?

Rolled my own using http://www.jacklmoore.com/autosize/. You can see it at this gist: https://gist.github.com/felipeochoa/1ada203ea68dce134d920b170bdd13cc


Fix multi-line argument lists when IndentWithTabs is enabled.

This Pull Request fixes https://github.com/daniel-trinh/scalariform/issues/63.

Thanks for the quick merge!


ESC reboots at low to moderate velocities

Reproducible causes using phone or laptop teleoperation window:
Gradually increase velocity to both ESCs to 0.2: cutout will occur after ~10 seconds
Gradually increase velocity to both or one ESC: cutout will occur around 0.3
Very quickly move velocity to both ESCs: cutout will occur almost instantly.
Effects: One or both ESCs reboot, stopping the corresponding motor(s)
For Seaking ESCs, this results in beep tones corresponding to throttle related error codes or the beeps for the arming sequence codes, or the beeps for entering program mode. Which happens depends on how you manipulate the velocities being sent to the ESCs once the motors stop moving (and, presumably, the ESC has rebooted).

I don't think this is a problem any longer with the newest software and the dynamite ESCs

Ok, we'll reopen if we start to see this again.


Add step on building NuGet package

Overview
About this last issue : #6993
With the aim to make the documentation more intuitive i propose a small addition :
Add a last step to explicitly ask to the user to press the save button when they add a new NugGet source on properties.
Changes

Add a "Save" step
Add an indicative image

Totally makes sense, and also definitely something that would be super easy for folks to overlook (and then hit issues as you've hit).
Thanks for making the docs better!

Approving conditionally on the image change - this is great, thanks again

Hi Will, there is a proposition of image, what do you think?
I m actually using unity personnal so i don't have the Dark theme, sorry (this is the reason i didn't add the new source in the previous image ahah).

/azp run mrtk_docs

@thalbern got to it before me, but thanks for updating it @Kent1LG. Looks great.


[2.0-branch]FixStreamLoad cannot be parsed correctly when it contains complex where conditions #23874

…
Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


Support advanced storage configure

https://github.com/open-cluster-management/backlog/issues/11627
Signed-off-by: clyang82<EMAIL_ADDRESS>

/assign @songleo


When on a user page, I'd like to know if they're following me.

Twitter does the following:

We should do something similar.

Hell yeah.

Kickass


Adding SAP NW certification for Dv3 and Ev3 series

@steffenv-msft : Thanks for your contribution! The author, @RicksterCDN, has been notified to review your proposed change.

#sign-off