Multi-MachineRendering.

I have successfully made it possible to render via multiple nodes and get the rendered files back to the api server but I need the IP of a particular render-node through which the particular frames has been rendered, so that I can fetch files from that node using that node IP. Is it possible to get that node IP on render finish?

Hey
It's a good question actually. Currently nexrender doesn't save the IPs of the render nodes.
Seems like the only way to get IP i see is possible, is slightly modify the code, so it would insert the IP of the machine that was rendering inside the project document.

Ok... then how to move files from render nodes to API server....As you suggested rsync for that in one of the network rend. issues  but it is not working on windows so Is there any other npm module to send file to api server after rendering get finished.

???? or atleast tell me any node js npm package which will help to move the rendered file to  api server ...and which will work fine on windows....or just help in getting ip address of rendering node on project finish

?????

you could try to split the original project onto few subprojects using startframe and endframe options for aerender and start them simultaneously

Tnx ... i have 1 more question
I start:
1st. nexrender --api-server --port =3000
2nd. node api_call.js
3th. nexrender --renderer --host=localhost:3000 --aerender="C:\bla bla"
Is thet right way ... because i think , i 1st need to start 1st. then 3th ... and after i need to run 2nd. multiple times ... but that dosenot work..
i have next issue is then i start nexrender api and after i start nexrender --renderer ...  he throw me error: request faild or no suitable project  find ... retrieing in 900000ms

i see that you are working mostly on localhost, maybe you would rather use simpler approach in that case?
https://github.com/inlife/nexrender-boilerplate

i am on widows virtual machine ..
i need to make sistem to send multiple AE templates .. on api server .. to cluster them ..(to make multi render farm, to speed up rendering proces) .. for that i use widows server R2012 ..

Can you specify me a steps which i need to follow to set up multi  multi project render enviroment?
I find in documentation those steps.
1st run nexrender --api-server --port ....
after i need to specify do i need to run nexrender --renderer or .. i need to make api_call ?
For me seems logic to call nexrenderer --reneder 1st .. and when i set this render node .. after i need to make api_call to send data to server and after he save it in temp file .. and nexrender need to start rendering ? Am i right?
I really need help .. i am trying to get it .. when i get it i will give my best to boost this lib XD

inlife ? are you there m8?

https://github.com/inlife/nexrender/wiki/Rendering-node
https://github.com/inlife/nexrender/wiki/API-server
https://github.com/inlife/nexrender/wiki/Project-model

OK i will put more focuse on studeing documentation .. after i will contact you ... tnx alot

Hi .. i studi it a bit .. and i understend how it works. XD
I have 2 questions for you.
-1st is how to run nexrender --renderer for specific project ?

2nd is  "startframe and endframe options for aerender and start them simultaneously", i dont understend when i run mini subprojects whic chain start/end frame ... how to merge( fuse them)?

Can you provide me help for it ? Tnx alott :3333

1st is how to run nexrender --renderer for specific project

there is no ability to do this right now, at least with the original renderer
you could try to write your own, using nexrender api, and renderer itself like has been demostrated in the issues

2nd is "startframe and endframe options for aerender and start them simultaneously", i dont understend when i run mini subprojects whic chain start/end frame ... how to merge( fuse them)?

there is no automatic way to merge them after, however you could use ffmpeg or something like that to do it, after both parts finished rendering


NEON functions required for libjpeg-turbo

@kleisauke is trying to get libjpeg-turbo working on WASM using SIMDe.  Here is a list of functions which aren't implemented yet:

[x] vaddhn_s32
[x] vld1q_dup_s16
[x] vld1q_lane_s16
[x] vld2_u8
[x] vmlal_lane_s16
[x] vmlal_lane_u16
[x] vmlsl_lane_s16
[x] vmlsl_lane_u16
[x] vmull_lane_s16
[x] vmull_lane_u16
[x] vqdmulh_lane_s16
[x] vqdmulhq_lane_s16
[x] vqrdmulhq_lane_s16
[x] vqrshrn_n_s16
[ ] vqshluq_n_s16
[x] vqshrn_n_s16
[x] vrshrn_n_s32
[x] vrshrn_n_u16
[x] vrshrn_n_u32
[x] vshll_n_s16
[x] vshrn_n_s32
[x] vshrn_n_u16
[x] vshrn_n_u32
[x] vsriq_n_u16
[x] vst2_lane_u16
[x] vst2q_u8
[x] vst3_lane_u8
[x] vst4_lane_u16
[x] vst4_lane_u8
[x] vsubhn_s32

Here's the updated list of functions that haven't yet been implemented (as of https://github.com/simd-everywhere/simde/commit/c29f9fbe9f0dc17f635c2e605376897c47167aa7, see commit https://github.com/kleisauke/wasm-vips/commit/0c97058c3756cf8fc9ccc7a7902c1c81b2b7ca11):

[X] vaddhn_s32 (commit https://github.com/simd-everywhere/simde/commit/e9ee0666356a60f28f5be248cf4de37be24e4a95)
[X] vld1q_dup_s16 (commit https://github.com/simd-everywhere/simde/commit/650d5310baec682d9c5545d668554b8791b93a96)
[X] vld1q_lane_s16 (commit https://github.com/simd-everywhere/simde/commit/9051a51c20c077f9a76be1ddf3c217e9bb9ad845)
[X] vld2_u8 (commit https://github.com/simd-everywhere/simde/commit/85d2ed2449992c5897bb9c01977fc7f060bbcd7c)
[ ] vmlal_lane_s16
[ ] vmlal_lane_u16
[ ] vmlsl_lane_s16
[ ] vmlsl_lane_u16
[ ] vmull_lane_s16
[ ] vmull_lane_u16
[X] vqdmulh_lane_s16 (commit https://github.com/simd-everywhere/simde/commit/79dc1eec5f3c6bd57a02d29636180da22c62a228)
[X] vqdmulhq_lane_s16 (commit https://github.com/simd-everywhere/simde/commit/79dc1eec5f3c6bd57a02d29636180da22c62a228)
[ ] vqrdmulhq_lane_s16
[X] vqrshrn_n_s16 (commit https://github.com/simd-everywhere/simde/commit/2595b3e46627e58356e4a7c1d61ccbeadd7edb58)
[ ] vqshluq_n_s16
[ ] vqshrn_n_s16
[X] vrshrn_n_s32 (commit https://github.com/simd-everywhere/simde/commit/a70371126cf1fd2f31dfd50e487b5b2c21a742d2)
[X] vrshrn_n_u16 (commit https://github.com/simd-everywhere/simde/commit/a70371126cf1fd2f31dfd50e487b5b2c21a742d2)
[X] vrshrn_n_u32  (commit https://github.com/simd-everywhere/simde/commit/a70371126cf1fd2f31dfd50e487b5b2c21a742d2)
[X] vshll_n_s16 (commit https://github.com/simd-everywhere/simde/commit/98ac861a48e1ed2a440e55465413fc91e5cabee0)
[X] vshrn_n_s32 (commit https://github.com/simd-everywhere/simde/commit/8810cdd6445dd2b04df3b5033ac6b5d0d8d68f2d)
[X] vshrn_n_u16 (commit https://github.com/simd-everywhere/simde/commit/8810cdd6445dd2b04df3b5033ac6b5d0d8d68f2d)
[X] vshrn_n_u32 (commit https://github.com/simd-everywhere/simde/commit/8810cdd6445dd2b04df3b5033ac6b5d0d8d68f2d)
[ ] vsriq_n_u16
[X] vst2_lane_u16 (commit https://github.com/simd-everywhere/simde/commit/8ee1eb412fbed783d0cc4ef80c1b8a75b1208baa)
[X] vst2q_u8 (commit https://github.com/simd-everywhere/simde/commit/1e38dcbc63d748b303055f086118ca2bd6cf84ac)
[X] vst3_lane_u8 (commit https://github.com/simd-everywhere/simde/commit/ae308b20867bc7d0f5761f816d448a9f48ad5ad1)
[X] vst4_lane_u16 (commit https://github.com/simd-everywhere/simde/commit/b231820afcdaf8858b726a04476410c363090ed0)
[X] vst4_lane_u8 (commit https://github.com/simd-everywhere/simde/commit/b231820afcdaf8858b726a04476410c363090ed0)
[ ] vsubhn_s32

Thanks for the reminder!  I added some more earlier today, and we'll try to get that last one done soon; I think @Glitch18 is planning to take care of it.

Yes. Will be pushing the commit soon!

BTW, once this is done I'd be very interested in any performance data which could point us to something we might be able to optimize in SIMDe.  See https://github.com/simd-everywhere/simde/wiki/Performance-Tuning#finding-performance-problems

Great, thanks! I'll re-run the benchmark in test/bench in wasm-vips within Chrome/Firefox once this is done. For Node.js, this requires an update of V8 to 9.1 (https://github.com/nodejs/node/pull/38273) to match the renumbered/finalized WASM SIMD opcodes.

vqshluq_n_s16 was implemented with commit https://github.com/simd-everywhere/simde/commit/77af9f12e93eacd5cf107faaf7c244d46c5c167f, which makes it possible to compile libjpeg-turbo for WebAssembly with SIMD support (by reusing the Arm Neon intrinsics, see commit https://github.com/kleisauke/wasm-vips/commit/acd4c8128bcb195fed8724e82c41f93014aea30d). :tada:
I'll re-run the benchmarks and post the results soon, feel free to close this issue.

First set of benchmarking/profiling results can be found here: test/bench/README-simde.md.
It seems that reusing the Arm Neon intrinsics for WASM made it ~3.5x slower than its C implementation (on this benchmark). The most number of ticks (>= 10) can be observed in these functions (ordered from high to low):

simde_vshlq_u16
simde_vld3_u8
simde_vld4q_s16
simde_vclzq_s16
simde_vld1q_lane_s16
simde_vtrn1q_s32
simde_vtrn2q_s32
simde_vtrn1q_s16

Note that libjpeg-turbo is considering a whole new SIMD implementation just for WASM, so please don't spend too much time on this.


Can't use PrivateKey on server in a NextJS 14 app

I am having trouble using o1js in a simple NextJS 14 app.
You can find my repo here: https://github.com/sam-goodwin/private-wallet
Check out the repo and run:
pnpm i
pnpm next build

It will just hang:
next build
   ▲ Next.js 14.1.4
   - Environments: .env

   Creating an optimized production build ...
 ✓ Compiled successfully
 ✓ Linting and checking validity of types
 ⚠ Sending SIGTERM signal to static worker due to timeout of 60 seconds. Subsequent errors may be a result of the worker exiting.
 ⚠ Restarted collecting page data for undefined because it took more than 60 seconds
 ⚠ See more info here https://nextjs.org/docs/messages/static-page-generation-timeout
   Collecting page data  .

Comment out the PrivateKey.random() and the error goes away.
When looking at the tutorials I spotted this bizarre code:
export default function Home() {

  useEffect(() => {
    (async () => {
      const { Mina, PrivateKey } = await import('o1js');
      const { Add } = await import('../../../contracts/build/src/');
    })();
  }, []);

This raises some red flags. Is o1js not designed to work as a normal module that can be imported?

Ok, I just found a NextJS config that might be something I am missing.
/** @type {import('next').NextConfig} */
const nextConfig = {
  reactStrictMode: false,

  webpack(config) {
    config.resolve.alias = {
      ...config.resolve.alias,
      o1js: require('path').resolve('node_modules/o1js')
    };
    config.experiments = { ...config.experiments, topLevelAwait: true };
    return config;
  },
  // To enable o1js for the web, we must set the COOP and COEP headers.
  // See here for more information: https://docs.minaprotocol.com/zkapps/how-to-write-a-zkapp-ui#enabling-coop-and-coep-headers
  async headers() {
    return [
      {
        source: '/(.*)',
        headers: [
          {
            key: 'Cross-Origin-Opener-Policy',
            value: 'same-origin',
          },
          {
            key: 'Cross-Origin-Embedder-Policy',
            value: 'require-corp',
          },
        ],
      },
    ];
  }
};

module.exports = nextConfig

Why does o1js require so much hackery to work? Can't it be an ordinary module? These kinds of things are what lead to people abandoning.

Why is reactStrictMode: false when it is highly recommended not to do this? https://nextjs.org/docs/pages/api-reference/next-config-js/reactStrictMode
Looks like there are some major bugs in the way o1js is distributed.

Now running into more specific errors:
"use client";
import { Resource } from "sst";
import { useEffect, useState } from "react";
// import type { PrivateKey } from "o1js";

export default function Root() {
  const [privateKey, setPrivateKey] = useState<any | undefined>();
  useEffect(() => {
    (async () => {
      const { PrivateKey } = await import("o1js");

      // const privateKey = PrivateKey.fromBase58(Resource.RootKey.value);
      const privateKey = PrivateKey.random();

      setPrivateKey(privateKey);
    })();
  }, []);

  return (

Public Key

      {privateKey?.toPublicKey().toBase58()}

  );
}

PrivateKey.random() seems to work but PrivateKey.fromBase58(Resource.RootKey.value); errors with:
Module build failed: UnhandledSchemeError: Reading from "node:process" is not handled by plugins (Unhandled scheme).
Webpack supports "data:" and "file:" URIs by default.
You may need an additional plugin to handle "node:" URIs.
Import trace for requested module:
node:process
<EMAIL_ADDRESS><EMAIL_ADDRESS>./src/app/page.tsx

I've now tried creating a very simple React Server Component:
"use server";

import { Resource } from "sst";

export default async function Root() {
  const { PrivateKey } = await import("o1js");
  const privateKey = PrivateKey.fromBase58(Resource.RootKey.value);

  return (

Public Key

      {privateKey?.toPublicKey().toBase58()}

  );
}

When I import o1js I get:

I am disappointed. I really wanted to experiment with Mina but o1js looks to have deviated far away from standard JavaScript distribution techniques and is fighting me every step of the way.

Hey @sam-goodwin! I appreciate you trying it out and writing up the problems you encountered!

Is o1js not designed to work as a normal module that can be imported?

Can't it be an ordinary module?

o1js is a normal ES module. It is distributed in two different builds, one for Node.js and one for the web.
Both "just work" when imported in their target environments: Node.js with type: module, and in the browser as a


Merging Hotmail and Outlook providers

I wanted to open a discussion on whether it should be a good idea to merge the above mentioned providers and related response codes. Am I mistaken in thinking that they are the same and behave the same once you hit their servers?

This makes sense to me. We merged Yahoo and AOL into "Verizon", so following that convention we could do the same with Outlook and Hotmail.

If that's OK, I can do that and submit a PR.

@nirebu I'm good with this. We should also add a list of recipient domains that each provider owns as well. Feel free to merge the providers and I'll submit a follow-up PR.

Closing this issue because b2e504d addresses this and much more.


Find appropriate way to integrate maven-publish-ed AARs

Since 0570eec I've been trying to make it possible to publish androidaudioplugin.aar and androidaudioplugin-ui-androidx.aar available through local Maven repository (under ~/.m2/repository/org/androidaudiopliugin), but referencing projects, for example aap-lv2 'local-package' branch fails to resolve constraint-layout resources when building plugins (which reference androidaudioplugin-ui-androidx).
It can be resolved by adding extraneous dependencies in each app's build.gradle, but that should not be what we should ask plugin developers. It's looking like an issue in Gradle maven-publish feature (or AGP enhancement, if any).

github went 404 after creating the issue and looked like it was gone, but it didn't. But it's duplicate of #59 anyways (and since GitHub behavior is unstable, I'd rather close this one than the other).


How to represent the dynamic value in cli?

Hi,
I need an approach to achieve my use-case using this package
I'm able to manage subcommands in the cli using this package(V1 version )
It is working like this test hello compile
Requirement:
Now I want to add another argument. like this  test hello details <hash_of _the_code>
<hash_of _the_code> is dynamic. How can I add it in cli?
The method I used  for other command is to add field Name: "string" to get N subcommands,
but in this case I need to get details using the hash. So it can't be a static name.
How can I achieve this?
thanks

@AchalaSB you can pass it in as an argument. In this example c.Args().Get(0) is getting the first argument, which would be <hash_of _the_code> in your case.


Does this app support MMS attachments too?

I currently use native Windows 10, "Your Phone" app which handles sending and receiving SMS phone messages very well.  It doesn't have to run in the forground constantly to still receive SMS text messages; since it's a UWP app.  However, it doesn't playback MMS video attachments at all.  It would be worth considering switching to the Android Messages Desktop app if it can handle MMS attachments.

Yes - It will send and receive MMS. Click on the photo icon to the right of the text entry box to see the list of file types supported. It also has a built in gif search / sender that send by gif. JPGs display and gifs automatically play. However, videos won't play, at least those sent from iphone. You'll need to download the video to your desktop to play.

Thank you for your time and development effort.

Thanks @mkanet and @innesst -- the app does indeed support MMS!


Data source  zia_user_management fails on converting user data

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform version 1.4.4
terraform -v
Terraform v1.4.4
on darwin_amd64
+ provider registry.terraform.io/hashicorp/aws v4.56.0
+ provider registry.terraform.io/hashicorp/vault v3.19.0
+ provider registry.terraform.io/zscaler/zia v2.4.6

Your version of Terraform is out of date! The latest version
is 1.5.5. You can update by downloading from https://www.terraform.io/downloads.html

Affected Resource(s)

Data Source: zia_user_management
Terraform Configuration Files

data "zia_user_management" "does_not_exists" {
  name = "Adam Ashcroft"
}

data "zia_user_management" "exists" {
  name = "piotr.szlenk"
}

Debug Output
https://gist.github.com/piotrszlenk/b91edce91010c1f17f7f6c42d322f5e0
Expected Behavior
Data source should return details of a particular user. Data source fails as expected when user does not exist but also fails when user exists.
Actual Behavior
│ Error: no user found with name: Adam Ashcroft
│
│   with data.zia_user_management.does_not_exists,
│   on data.tf line 4, in data "zia_user_management" "does_not_exists":
│    4: data "zia_user_management" "does_not_exists" {
│

│ Error: Invalid address to set: []string{"groups", "0", "extensions"}
│
│   with data.zia_user_management.exists,
│   on data.tf line 8, in data "zia_user_management" "exists":
│    8: data "zia_user_management" "exists" {
│

Steps to Reproduce

terraform apply

Important Factoids
I am experimenting with zscalerbeta.net. I can't tell if this works on regular tenants as I have no access to them.

This issue has been addressed in previous versions. Please update your configuration to the latest version v2.6.1 and test again to ensure it's working as expected.
Thanks


lol

its open sourced why would you pay?

the deobf version is old, it is also an unnecessary payment, I only put it for those who want to buy it (not recommended)

Alright I'll make push it with some edits

:)


Handle multiple scenario from API call

Hi, I'm currently following this architecture for my apps, and wondering how to handle multiple scenario code response from API call.
Let's say I have something like this:

UserRepository contain the logic between API fetch or loading from SQLite cache, I can assure that UserLocalDataStore will return the Success Response. The problem is, my UserRemoteData has many scenario, ex:

Success Response
Expired Session
Invalid Token

Currently the UseCase, Repository, LocalDataStore & RemoteDataStore return Observable<UserResponse>,  and I put my validation in my presenter, but feels so wrong because I need to validate it everytime I use GetUserListUseCase.
if(response.getCode().equals(API_SUCCESS)) {
    view.showUserList(response.getUserList());
}
else if(response.getCode().equals(EXPIRED_SESSION)) {
    view.moveToLoginScreen(response.getMessage());
}
else if(response.getCode().equals(TOKEN_INVALID)) {
    view.moveToLoginScreen(response.getMessage());
}
else {
    view.showFailedFetchUserList("Unexpected Error Occured");
}

*Note: all of my API fetch can return this response scenario
My Question is:

Which layer is reponsible for validate this scenario?
Do I really need to validate this scenario in other API Call for different Entity (Let say I have Product, Purchase entity, instead only User entity. Since all of my API have this scenario)?

Personally, I would encapsulate the logic of expired session and invalid token in the remote data store and every data store would emit users. If error happened then i would pass specific exception (let's call it SessionException) in observable's onError method.
Then I would have an observer inside the UserListPresenter which would have an implementation like that:
private final class UserObserver extends DisposableObserver {
    @Override
    public void onNext(User module) {
        //...
    }

    @Override
    public void onError(Throwable e) {
        if (e instanceof SessionException) {
            view.moveToLoginScreen(e.getMessage());
        } else {
            view.showFailedFetchUserList("Unexpected Error Occured");
        }
    }

    @Override
    public void onComplete() {
        //...
    }

}


Vocabulary Size

Hey everyone,
Just a heads up: on the paper, the tokenizer section mentions 1180 vocabulary size, which should be 1880.
Feel free to close this, it's more a notification than an issue.

Thank you.


Impl dot

Proposed changes
Adds dot implementation
Checklist
Put an x in the boxes that apply.

[x] I have read the CONTRIBUTING document
[x] I have run pre-commit run --all-files to format my code / installed pre-commit prior to committing changes
[x] I have added tests that prove my fix is effective or that my feature works
[x] I have updated the necessary documentation (if needed)

Thanks for adding this! Left some comments inline. Please take a look and let me know when it's ready to go 🚀

@awni I 'll wait if you want to comment on the docs but otherwise I think it is ok.

Looks great! I think for the doc it might be helpful to say why we discourage using it? It left me a bit confused reading that line .. like why have the op if we don't want people to use it sort of thing

Going to remove that comment, this pr was created a while back and looking through it I'm not sure why I added that comment.

@angeloskath what if we just repurpose this to a vecdot/vdot and scrap the rest of the dot API? I'm really ok not including it as I agree with you the API is confusing and it's always better to use one of the alternatives.
Also I just noticed it's not in the Python array API standard so from that perspective we can at least support the decision not to include it.
I don't mean to blow this up though, if you all think we should have it, let's do it.

I definitely support moving this to vdot. Wdyt @dc-dc-dc ? Is there a specific need for dot? Some old codebase or something?

Somebody in the discord mentioned that they needed it for their project and I had this sitting in my local repo. I'm fine with closing this if it's not of interest

Regarding the need, I remember the discussion and that person was satisfied using matmul in the end.. so I don't think there is a strong need for dot?
How about just changing to vdot / vecdot? That one actually seems useful IMO. Should be a small(ish) diff from here.

@dc-dc-dc wdyt about this? Any plan to update or should we close?

Closing until we have a good vdot.


lxc config trust add says: Error: Client is already trusted

Version info:
$ snap list lxd
Name  Version      Rev    Tracking       Publisher   Notes
lxd   5.1-4ae3604  23001  latest/stable  canonical✓  -

Steps to reproduce:
$ lxc config trust ls
+------+------+-------------+-------------+------------+-------------+
| TYPE | NAME | COMMON NAME | FINGERPRINT | ISSUE DATE | EXPIRY DATE |
+------+------+-------------+-------------+------------+-------------+

$ lxc config trust add --name foo
Error: Client is already trusted

$ lxc config trust add --name bar
Error: Client is already trusted

Taken from https://discuss.linuxcontainers.org/t/issues-while-adding-a-trusted-client-through-token/14047

Looking into it, we most likely caused this with the recent re-order of the certificates codepath.

Got a fix


feat(docs): Update the governance-related documentation based on cncf tag-contributor-strategy recommendations.

CubeFS propose the [Governance Review]: CubeFS #649  @tag-contributor-strategy
Base on the recommendations we update the  governance-related documentation:

Clarify the responsibilities and lifecycle of the TSC, maintainers, and committers, SIGs.
Fix the issue in security reporting as incorrect email address for reporting vulnerabilities.
Clarify the governace of SIGs
Add a link to the governance section in README.md for emphasis.

Types of changes

[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Bugfix (non-breaking change which fixes an issue)
[x] Documentation Update (if none of the other choices apply)
[ ] So on...

Verifying this change

[x] Make sure that the change passes the testing checks.

This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

This can be verified in development debugging
This can be realized in a mocked environment, like a test cluster consisting in docker

(or)
This change MUST reappear in online clusters, or occur in that specific scenarios.
Does this pull request potentially affect one of the following parts:

[ ] Master
[ ] MetaNode
[ ] DataNode
[ ] ObjectNode
[ ] AuthNode
[ ] LcNode
[ ] Blobstore
[ ] Client
[ ] Cli
[ ] SDK
[ ] Other Tools
[ ] Common Packages
[ ] Dependencies
[ ] Anything that affects deployment

Documentation

[x] doc
[ ] doc-required
[ ] doc-not-needed
[ ] doc-complete

Review Expection

[ ] in-two-days
[x] weekly
[ ] free-time
[ ] whenever

Matching PR in forked repository

PR in forked repository:

+1

+1


Support for  SELECT ... FOR UPDATE statement

Please provide some example queries

@twheys I think he needs something like this:
 SELECT * FROM orders
  WHERE status = 'pending'
  LIMIT 1 FOR UPDATE;

 # do something with record...
 UPDATE orders SET {SOME_FIELDS} WHERE id = {selected_id};

Just possibility to set mode

@twheys I think he needs something like this:
 SELECT * FROM orders
  WHERE status = 'pending'
  LIMIT 1 FOR UPDATE;

 # do something with record...
 UPDATE orders SET {SOME_FIELDS} WHERE id = {selected_id};

Just possibility to set mode

exact, thanks


[SUGGESTION] Exception checking around ffmpeg subprocess

I note your comment in the program file:
"Because we are prepared to accept whatever parameters and values that FFmpeg supports,
there is generally no checking up at this level. That may change over time as we
develop better expectations as to what can and cannot work."
I believe this will leave you hostage to fortune over time and there will probably be a need for exception checking around the subprocess which runs ffmpeg?

I can imagine! :)
On Thu, 19 Oct 2023 at 13:17, davidplowman @.***> wrote:

Probably. I think there will have to be a check every time we try and
write anything to it to see if it's still behaving, and possibly kill it if
it isn't. I know I've discussed this with some folks, and will get round to
it, but for the moment we're just in a bit of a
make-everything-work-on-a-Pi-5-yesterday zone.
—
Reply to this email directly, view it on GitHub
https://github.com/raspberrypi/picamera2/issues/829#issuecomment-1770841881,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABRULU7TGJU5UJD4ANGD333YAEK7PAVCNFSM6AAAAAA6HBLJZ2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONZQHA2DCOBYGE
.
You are receiving this because you authored the thread.Message ID:
@.***>


release-service prod update

Needs to be merged with https://github.com/redhat-appstudio/tenants-config/pull/175

/lgtm


Example in readme doesn't work

Hi,
If I follow the example in the Readme for CNN, I get no articles:
import newspaper

cnn_paper = newspaper.build('http://cnn.com')

for article in cnn_paper.articles:
    print(article.url)

The above outputs nothing, cnn_paper.articles is empty.
It does pick up categories and a few feeds, however.

Works for me. What version of newspaper are you using?

Same issue, there are only few categories.
I am using python3.5.2 and newpaper3k 0.1.7

@conraddd Homepage demo didn't work for me either. However using the homepage link after the redirect worked:
cnn = newspaper.build("http://edition.cnn.com/")

I also just tested it and it worked for me. Might be a geographical location URL routing problem?


Connection full with 0.10.x proxy

@jasonacox Got 45 connection warnings within 2 seconds. Wondering if some decision logic changed in the latest release.
2024-06-10 15:27:58 06/10/2024 03:27:58 PM [proxy] [INFO] pyPowerwall [0.10.2] Proxy Server [t59] - HTTP Port 8675
5x
2024-06-10 18:34:52 06/10/2024 06:34:52 PM [pypowerwall] [ERROR] Failed to get /api/system_status/grid_status
45x
2024-06-10 18:35:01 06/10/2024 06:35:01 PM [urllib3.connectionpool] [WARNING] Connection pool is full, discarding connection: <IP_ADDRESS>. Connection pool size: 15

Thanks @jgleigh - It is running the same logic unless you switched into "full" (e.g. Powerwall 3) mode. Go to http://localhost:8675/help and look for tedapi_mode (full or hybrid).

hybrid

Thanks for checking! You are on the same codebase. The ERROR means that it got a Null response from the Powerwall for that call (possibly timeout). The WARNING messages mean that multiple connections were queued up waiting for the Powerwall which went above the 15 limit so it began to prune them.
Do your graphs look like you are seeing a lot of gaps?

No gaps. I was just wondering why it kept sending so many requests in such a short period of time when the connection buffer was full. Last 24 hours, it hit that connection pool buffer with differing frequency of repeats (2x, 7x, 20x, 14x). Also seems odd that the number of requests when the buffer is full isn't consistent.

Understood. I have an idea. Did you see these before? If not, the difference with the non-TEDAPI version and this one is that it now opens additional connections to the /tedapi API endpoints. This would likely drive up the number of concurrent requests. You could adjust the connection pool size in pypowerwall.env to allow more more concurrent requests:
PW_POOL_MAXSIZE=20

And restart ./compose-dash.sh up -d
I'm see the same on my end so I'm going to increase the connection pool size to see if I can eliminate it.

Saw it occasionally before, but not consistently like this. Trying 20 as well and we'll see how it goes.

As a second option...
In my testing in "full" mode (to simulate PW3) where it only uses the /tedapi API, I started to see incomplete or missing payloads resulting in None responses. There is enough error handling that it doesn't matter in the graph but it is logging those. I'm testing call locking to limit potential load caused by concurrent polling. FYI if you want to test:
jasonacox/pypowerwall:0.10.5t61-beta8

so far so good🤞

48 hours and only one error. This is about 1000% better than before!
2024-06-14 06:32:05 06/14/2024 06:32:05 AM [pypowerwall] [ERROR] Failed to get /api/system_status/grid_status

That's awesome @jgleigh !   I get the same error on occasion. It means that the payload didn't include the ISLAND data or the specific keys. I'm not sure why that happens. I'm going to keep poking at it, but for now, I think this latest pypowerwall version 0.10.5 https://github.com/jasonacox/pypowerwall/pull/102 upgrade is solid.


ms1689: add new 'Event note' field

@AaronCMuller , @scoen @shuangzhou
http://ourweb.nla.gov.au/apps/jira/browse/DSCS-1689
This is the Voyager 518 field, similar to Finding Aid Note(555) and Restriction on Access (506)

:+1:


Miscord uses discord username instead of server nickname in messenger channel

Describe the bug
Messages sent from discord to messenger contains discord username instead of server nickname.
To Reproduce
Steps to reproduce the behavior:

On server with miscord, set different nickname than account username
Send message to miscord channel
Message in messenger contains account username instead of server nickname

Expected behavior
Messages sent to messenger should start with server nickaname.
Specifications:

OS:
n/a

Version:
latest

Node.js version:
n/a

Still no update on that issue? 😫

Looking at code it seems like problem lies in file toMessenger.ts, line 9:
const username = message.member ? (message.member.nickname ?? message.author.username) : message.author.username
I guess discord.js does not return message author's nickname correctly.
Miscord uses discord.js version" ^11.5.1", when current version of discord.js on npm is 12.5.1, maybe updating it would help?

Updating discord.js to v12 is actually a bit of work, but I'll get to working on it soon, I guess...

I recently found out that messages coming from messanger to discord also doesn't care about nicknames, so messenger -> discord message is shown with name and surname instead of messenger chat nickcname.

I recently found out that messages coming from messanger to discord also doesn't care about nicknames, so messenger -> discord message is shown with name and surname instead of messenger chat nickcname.

Cause messenger doesn't have nicknames anymore

Cause messenger doesn't have nicknames anymore


Issue/osprh 6541

As a pull request owner and reviewers, I checked that:

[x] Appropriate testing is done and actually running
[x] Appropriate documentation exists and/or is up-to-date:

[x] README in the role
[x] Content of the docs/source is reflecting the changes

Closes: OSPRH-6541

/approve

recheck

check-rdo

ok its queded here https://review.rdoproject.org/zuul/status/change/1681,e8f8c61fd3ca922c728315b0aee857dc9f135ef9 so that should report back when doen
i think it got confused since we both rebased at the same time

actully no https://review.rdoproject.org/zuul/buildset/2780c63a999c47edbf268d7ff0a89016 it did fail again... im really not sure why

recheck


Improve instructions for the GCC build

Improve the instructions for the GCC build from source in MinGW / msys. Attempt to keep the prerequisites up-to-date. Also provide command line options for building arm-none-eabi with multilib and FPU support.

Have you tried MSYS2?
It's fantastic. It uses a linux package manager called pacman. Quite the Linux experience under windows!
https://msys2.github.io/
After installation, one can lauch the msys shell like this:
C:\msys32\mingw32_shell.bat           (for 32-bit Windows)
C:\msys32\mingw64_shell.bat             (for 64-bit Windows)
Search and install packages:
## search for gcc
pacman -Ss gcc

## install gcc for 32bit windows
pacman -S mingw32/mingw-w64-i686-gcc

## install gcc for 64bit windows
pacman -S mingw64/mingw-w64-x86_64-gcc

## search for make
pacman -Ss make

## install make (for 32bit windows)
pacman -S mingw32/mingw-w64-i686-make

## install make (for 64bit windows)
pacman -S mingw64/mingw-w64-x86_64-make

## search for boost
pacman -Ss boost

## install boost (for 32bit windows)
pacman -S mingw32/mingw-w64-i686-boost

## install boost (for 32bit windows)
pacman -S mingw64/mingw-w64-x86_64-boost

## search for git
pacman -Ss git

## install git
pacman -S msys/git

## search for gdb
pacman -Ss gdb

## install gdb (for 32bit windows)
pacman -S mingw32/mingw-w64-i686-gdb   mingw32/mingw-w64-i686-gdbm

##  install gdb (for 64bit windows)
...

Thanks for the suggestion.

The really nice thing about MSYS2 is that it has very recent version of compilers (better support for C++14) and tools:
Currently

gcc 5.3.0
boost 1.60

In addition to commands mentioned in top post, a good base system can be installed with
pacman -S base-devel

(Unlike the old msys/mingw, MSYS2 is also not "dead": http://stackoverflow.com/a/25023611/5106243 )

If you're behind a proxy, then for networking (necessary for pacman and command-line git):
When launching
C:\msys32\mingw32_shell.bat (for 32-bit Windows)
C:\msys32\mingw64_shell.bat (for 64-bit Windows)
be sure to set:
export http_proxy=http://proxyhost:port     ## e.g. export http_proxy=http://<IP_ADDRESS>:3128
export https_proxy=http://proxyhost:port    ## e.g. export https_proxy=http://<IP_ADDRESS>:3128

or; if username/password is necessary as well then:
export http_proxy=http://username:password@proxyhost:port
export https_proxy=http://username:password@proxyhost:port

(Also... you may wish to look at cntlm)

Actually... the AVR gcc crosscompiler should be packaged! That would be great!
I don't currently have time with it, but if anybody has, then I'd recommend talking to the MSYS2 people, to get the AVR cross-compiler packaged into MSYS2's pacman format. I'm sure those MSYS2 people would help.
Main benefit: no more time wasted on compiling. Less people compiling == Less energy usage. ;)

Generally GitHub issues aren't the place for 'Me too' however with the low volume of traffic here I'm waving my hand high saying 'Me too, me too!' Maybe tweet this out and get some momentum built for the idea. I like the idea of having it in a package manager format for Windows. Be sure to mention the hash tag of the day ... #IoT

There has actually been significant progress in this area.

*nix builds are supported in parallel with the VC build.
There is also new cross-platform CMake support for the builds.


Bug 1124911 - "You are the only one in the room" spans two lines in some localizations, but second line not in middle bond

#first-one-label {
  /* Y te cepillas el font-height */
  justify-content:center;
  align-content:center;
  flex-direction:column;
}
#room-ui[data-status="waiting"][data-participants="1"] #first-one-label {
  display: flex;
}


Bump AKS to version 1.17.7

From 1.16

"Changes" in psql seem to mistankely appear.

@prscheduler 16/07/2020T00:19


buried treasure & ship wrecks not highlighted

At some point, buried treasure and ship wrecks stopped getting highlighted (xray).  Did this get removed?

Also jungle temples.

This was never removed.

I assume you're on a multiplayer server with these structures. If you could grab a world download (using a mod) of the structures that aren't being identified, and then upload it, that would be helpful.


crashes well doing entity rendering during start up

crashes well doing entity rendering during start up
crash-2020-06-07_14.52.07-client.txt

This appears to be a problem with CreativeCore, or rather, a lack thereof.
Solution: install CreativeCore

This appears to be a problem with CreativeCore, or rather, a lack thereof.
Solution: install CreativeCore


Redesign and refactor core functionalities

Right now the code is spread on three different files (bigchaindb/core.py, bigchaindb/util.py, bigchaindb/consensus.py), without a specific rationale.
The goal is to have a clear set of primitives we can use to create and manipulate transactions. Those primitives will be eventually grouped in a high order component (a class seems to be a good option) to handle transactions. The component will also allow different de/serialization methods (this will help the development of #485).

This issue is outdated.


naming question

Would
.border-color--black { border-color: var(--black); }
make more sense than
.bordercolor-black { border-color: var(--black); }
??
gzip will compress repeated strings so there is no real size hit..
Just a thought...

Hey @ShaggyDude – can you say a little bit more about why? Am happy to reconsider.
My current rule of thumb for naming is .PropertyNameInOneWord-ValueInOneWord-MediaQuery
There are weird edge cases, but I find, for example, .bordercolor-darkgrey a bit easier to read/write than .border-color-dark-grey.

I'm trying to get a 1 to 1 mapping of css as much as possible so
.border-color--black { border-color: black; } is more like a literal translation to me.
I have made a fork and am playing around with it to see if what I'm thinking makes sense..

I am also trying to achieve readability over brevity because as stated before gzip loves long names..

Ahh gotcha – so like double dash corresponds to semicolon? Let m know what you think after experimenting with it! Would be curious/tempted for sure.
Was looking through my own examples, so I guess for me, this is more readable because it's a little more compact (yes I know it's ironic saying that for a verbose toolset):
f5 fontstyle-italic fontweight-normal margintop-small black
versus
f5 font-style--italic font-weight--normal margin-top--small black
What do you think?

Just now coming back to this with fresh eyes. Yes, I think your way is better.

@ShaggyDude Thanks for coming back on this one. Good to know (as I occasionally wonder if I made the right choice in the first place)!


KDL.DLL listed as trojan

Describe the bug
Switched to BIOS detection and Cylance killed the dll.  VirusTotal lists it as a trojan
https://www.virustotal.com/gui/file/cb3992b567e9e3e147922b43a0e4d542c53c8548aba5038b70281c024b2510a9/detection
To Reproduce
Open AlienFX
Click Use Bios Sensors
Expected behavior
It should work.
Screenshots

System (please complete the following information):
Alienware X14

This fact mentioned into both package and git readme.
Please read this - https://github.com/T-Troll/alienfx-tools/wiki/Why-antivirus-complain-about-some-alienfx-tools-components%3F
PS: Of course, it's not a trojan.


feat: finish last slide of intro and add text to rocket

last slide of intro
add custom text to rocket
closes #74

@mattxwang

I have some other comments on image accessibility and general practices
please do tell :)


HBASE-25212 [branch-1] Optionally abort requests in progress after deciding a region should close

If hbase.regionserver.close.wait.abort is set to true, interrupt RPC
handler threads holding the region close lock.
Until requests in progress can be aborted, wait on the region close lock
for a configurable interval (specified by hbase.regionserver.close.wait.time,
in ms). If we have failed to acquire the close lock after this interval
elapses, if allowed (also specified by hbase.regionserver.close.wait.abort),
abort the regionserver.
Define a subset of region operations as interruptable. Track threads holding
the close lock transiting those operations. Set the thread interrupt status
of tracked threads when trying to close the region. Use the thread interrupt
status where safe to break out of request processing.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

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

_ Prechecks _

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

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

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

+1 :green_heart:
test4tests
0m  0s
The patch appears to include 3 new or modified test files.

_ branch-1 Compile Tests _

+1 :green_heart:
mvninstall
9m 51s
branch-1 passed

+1 :green_heart:
compile
0m 41s
branch-1 passed with JDK v1.8.0_262

+1 :green_heart:
compile
0m 48s
branch-1 passed with JDK v1.7.0_272

+1 :green_heart:
checkstyle
2m  6s
branch-1 passed

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

+1 :green_heart:
javadoc
0m 48s
branch-1 passed with JDK v1.8.0_262

+1 :green_heart:
javadoc
0m 43s
branch-1 passed with JDK v1.7.0_272

+0 :ok:
spotbugs
3m 15s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
3m 11s
branch-1 passed

_ Patch Compile Tests _

-1 :x:
mvninstall
1m 14s
root in the patch failed.

-1 :x:
compile
0m 25s
hbase-server in the patch failed with JDK v1.8.0_262.

-1 :x:
javac
0m 25s
hbase-server in the patch failed with JDK v1.8.0_262.

-1 :x:
compile
0m 33s
hbase-server in the patch failed with JDK v1.7.0_272.

-1 :x:
javac
0m 33s
hbase-server in the patch failed with JDK v1.7.0_272.

-1 :x:
checkstyle
1m 55s
hbase-server: The patch generated 7 new + 787 unchanged - 2 fixed = 794 total (was 789)

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

-1 :x:
shadedjars
1m 57s
patch has 36 errors when building our shaded downstream artifacts.

-1 :x:
hadoopcheck
1m  7s
The patch causes 36 errors with Hadoop v2.8.5.

-1 :x:
hadoopcheck
2m 50s
The patch causes 36 errors with Hadoop v2.9.2.

+1 :green_heart:
javadoc
0m 31s
the patch passed with JDK v1.8.0_262

+1 :green_heart:
javadoc
0m 42s
the patch passed with JDK v1.7.0_272

-1 :x:
findbugs
0m 33s
hbase-server in the patch failed.

_ Other Tests _

-1 :x:
unit
0m 33s
hbase-server in the patch failed.

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

46m 35s

Subsystem
Report/Notes

Docker
Client=19.03.13 Server=19.03.13 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2576/1/artifact/out/Dockerfile

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

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile

uname
Linux d5e07e14bae6 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-home/workspace/Base-PreCommit-GitHub-PR_PR-2576/out/precommit/personality/provided.sh

git revision
branch-1 / 8e387e9

Default Java
1.7.0_272

Multi-JDK versions
/usr/lib/jvm/zulu-8-amd64:1.8.0_262 /usr/lib/jvm/zulu-7-amd64:1.7.0_272

mvninstall
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2576/1/artifact/out/patch-mvninstall-root.txt

compile
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2576/1/artifact/out/patch-compile-hbase-server-jdk1.8.0_262.txt

javac
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2576/1/artifact/out/patch-compile-hbase-server-jdk1.8.0_262.txt

compile
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2576/1/artifact/out/patch-compile-hbase-server-jdk1.7.0_272.txt

javac
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2576/1/artifact/out/patch-compile-hbase-server-jdk1.7.0_272.txt

checkstyle
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2576/1/artifact/out/diff-checkstyle-hbase-server.txt

shadedjars
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2576/1/artifact/out/patch-shadedjars.txt

hadoopcheck
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2576/1/artifact/out/patch-javac-2.8.5.txt

hadoopcheck
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2576/1/artifact/out/patch-javac-2.9.2.txt

findbugs
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2576/1/artifact/out/patch-findbugs-hbase-server.txt

unit
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2576/1/artifact/out/patch-unit-hbase-server.txt

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

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

modules
C: hbase-server U: hbase-server

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

versions
git=1.9.1 maven=3.0.5 findbugs=3.0.1

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

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

_ Prechecks _

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

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

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

+1 :green_heart:
test4tests
0m  0s
The patch appears to include 5 new or modified test files.

_ branch-1 Compile Tests _

+1 :green_heart:
mvninstall
9m 54s
branch-1 passed

+1 :green_heart:
compile
0m 41s
branch-1 passed with JDK v1.8.0_262

+1 :green_heart:
compile
0m 47s
branch-1 passed with JDK v1.7.0_272

+1 :green_heart:
checkstyle
2m  3s
branch-1 passed

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

+1 :green_heart:
javadoc
0m 48s
branch-1 passed with JDK v1.8.0_262

+1 :green_heart:
javadoc
0m 43s
branch-1 passed with JDK v1.7.0_272

+0 :ok:
spotbugs
3m 14s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
3m 10s
branch-1 passed

_ Patch Compile Tests _

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

+1 :green_heart:
compile
0m 41s
the patch passed with JDK v1.8.0_262

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

+1 :green_heart:
compile
0m 48s
the patch passed with JDK v1.7.0_272

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

-1 :x:
checkstyle
1m 55s
hbase-server: The patch generated 9 new + 797 unchanged - 10 fixed = 806 total (was 807)

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

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

+1 :green_heart:
hadoopcheck
5m  0s
Patch does not cause any errors with Hadoop 2.8.5 2.9.2.

+1 :green_heart:
javadoc
0m 31s
the patch passed with JDK v1.8.0_262

+1 :green_heart:
javadoc
0m 43s
the patch passed with JDK v1.7.0_272

+1 :green_heart:
findbugs
3m 10s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
111m 20s
hbase-server in the patch passed.

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

166m 22s

Subsystem
Report/Notes

Docker
Client=19.03.13 Server=19.03.13 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2576/2/artifact/out/Dockerfile

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

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile

uname
Linux 48a15f9d25e6 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-home/workspace/Base-PreCommit-GitHub-PR_PR-2576/out/precommit/personality/provided.sh

git revision
branch-1 / 8e387e9

Default Java
1.7.0_272

Multi-JDK versions
/usr/lib/jvm/zulu-8-amd64:1.8.0_262 /usr/lib/jvm/zulu-7-amd64:1.7.0_272

checkstyle
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2576/2/artifact/out/diff-checkstyle-hbase-server.txt

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

Max. process+thread count
3542 (vs. ulimit of 10000)

modules
C: hbase-server U: hbase-server

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

versions
git=1.9.1 maven=3.0.5 findbugs=3.0.1

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m  5s
Docker mode activated.

_ Prechecks _

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

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

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

+1 :green_heart:
test4tests
0m  0s
The patch appears to include 7 new or modified test files.

_ branch-1 Compile Tests _

+1 :green_heart:
mvninstall
9m 40s
branch-1 passed

+1 :green_heart:
compile
0m 42s
branch-1 passed with JDK v1.8.0_262

+1 :green_heart:
compile
0m 48s
branch-1 passed with JDK v1.7.0_272

+1 :green_heart:
checkstyle
2m  5s
branch-1 passed

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

+1 :green_heart:
javadoc
0m 47s
branch-1 passed with JDK v1.8.0_262

+1 :green_heart:
javadoc
0m 42s
branch-1 passed with JDK v1.7.0_272

+0 :ok:
spotbugs
3m 16s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
3m 12s
branch-1 passed

_ Patch Compile Tests _

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

+1 :green_heart:
compile
0m 42s
the patch passed with JDK v1.8.0_262

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

+1 :green_heart:
compile
0m 47s
the patch passed with JDK v1.7.0_272

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

-1 :x:
checkstyle
1m 54s
hbase-server: The patch generated 7 new + 820 unchanged - 10 fixed = 827 total (was 830)

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

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

+1 :green_heart:
hadoopcheck
4m 53s
Patch does not cause any errors with Hadoop 2.8.5 2.9.2.

+1 :green_heart:
javadoc
0m 32s
the patch passed with JDK v1.8.0_262

+1 :green_heart:
javadoc
0m 42s
the patch passed with JDK v1.7.0_272

+1 :green_heart:
findbugs
3m  9s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
111m 30s
hbase-server in the patch passed.

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

155m 44s

Subsystem
Report/Notes

Docker
Client=19.03.13 Server=19.03.13 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2576/3/artifact/out/Dockerfile

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

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile

uname
Linux 973c811e006d 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-home/workspace/Base-PreCommit-GitHub-PR_PR-2576/out/precommit/personality/provided.sh

git revision
branch-1 / 8e387e9

Default Java
1.7.0_272

Multi-JDK versions
/usr/lib/jvm/zulu-8-amd64:1.8.0_262 /usr/lib/jvm/zulu-7-amd64:1.7.0_272

checkstyle
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2576/3/artifact/out/diff-checkstyle-hbase-server.txt

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

Max. process+thread count
3542 (vs. ulimit of 10000)

modules
C: hbase-server U: hbase-server

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

versions
git=1.9.1 maven=3.0.5 findbugs=3.0.1

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

This message was automatically generated.

Will push up fixes for the checkstyle nits in a bit.

Rebase and fix checkstyle nits

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 15s
Docker mode activated.

_ Prechecks _

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

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

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

+1 :green_heart:
test4tests
0m  0s
The patch appears to include 7 new or modified test files.

_ branch-1 Compile Tests _

+1 :green_heart:
mvninstall
10m  2s
branch-1 passed

+1 :green_heart:
compile
0m 42s
branch-1 passed with JDK v1.8.0_262

+1 :green_heart:
compile
0m 47s
branch-1 passed with JDK v1.7.0_272

+1 :green_heart:
checkstyle
2m 12s
branch-1 passed

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

+1 :green_heart:
javadoc
0m 49s
branch-1 passed with JDK v1.8.0_262

+1 :green_heart:
javadoc
0m 43s
branch-1 passed with JDK v1.7.0_272

+0 :ok:
spotbugs
3m 18s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
3m 15s
branch-1 passed

_ Patch Compile Tests _

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

+1 :green_heart:
compile
0m 42s
the patch passed with JDK v1.8.0_262

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

+1 :green_heart:
compile
0m 48s
the patch passed with JDK v1.7.0_272

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

+1 :green_heart:
checkstyle
1m 58s
hbase-server: The patch generated 0 new + 812 unchanged - 18 fixed = 812 total (was 830)

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

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

+1 :green_heart:
hadoopcheck
5m  8s
Patch does not cause any errors with Hadoop 2.8.5 2.9.2.

+1 :green_heart:
javadoc
0m 34s
the patch passed with JDK v1.8.0_262

+1 :green_heart:
javadoc
0m 43s
the patch passed with JDK v1.7.0_272

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

_ Other Tests _

-1 :x:
unit
118m 27s
hbase-server in the patch failed.

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

164m 12s

Reason
Tests

Failed junit tests
hadoop.hbase.namequeues.TestSlowLogAccessor

Subsystem
Report/Notes

Docker
Client=19.03.13 Server=19.03.13 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2576/4/artifact/out/Dockerfile

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

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile

uname
Linux bf2e07b5aab9 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-home/workspace/Base-PreCommit-GitHub-PR_PR-2576/out/precommit/personality/provided.sh

git revision
branch-1 / 9eb3a79

Default Java
1.7.0_272

Multi-JDK versions
/usr/lib/jvm/zulu-8-amd64:1.8.0_262 /usr/lib/jvm/zulu-7-amd64:1.7.0_272

unit
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2576/4/artifact/out/patch-unit-hbase-server.txt

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2576/4/testReport/

Max. process+thread count
3614 (vs. ulimit of 10000)

modules
C: hbase-server U: hbase-server

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

versions
git=1.9.1 maven=3.0.5 findbugs=3.0.1

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

This message was automatically generated.

Test failure is unrelated

[ERROR]   TestSlowLogAccessor.testSlowLogRecords:112->waitForSlowLogTableCreation:174 Waiting timed out after [2,000] msec

@virajjasani Maybe this test has too short a timeout given sometimes public CI resources are loaded up?

Rebase. Sync with updates to master branch patch.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

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

_ Prechecks _

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

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

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

+1 :green_heart:
test4tests
0m  0s
The patch appears to include 7 new or modified test files.

_ branch-1 Compile Tests _

+1 :green_heart:
mvninstall
10m  7s
branch-1 passed

+1 :green_heart:
compile
0m 44s
branch-1 passed with JDK v1.8.0_262

+1 :green_heart:
compile
0m 47s
branch-1 passed with JDK v1.7.0_272

+1 :green_heart:
checkstyle
2m  7s
branch-1 passed

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

+1 :green_heart:
javadoc
0m 48s
branch-1 passed with JDK v1.8.0_262

+1 :green_heart:
javadoc
0m 46s
branch-1 passed with JDK v1.7.0_272

+0 :ok:
spotbugs
3m 49s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
3m 43s
branch-1 passed

_ Patch Compile Tests _

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

+1 :green_heart:
compile
0m 57s
the patch passed with JDK v1.8.0_262

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

+1 :green_heart:
compile
1m  1s
the patch passed with JDK v1.7.0_272

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

+1 :green_heart:
checkstyle
2m 27s
hbase-server: The patch generated 0 new + 812 unchanged - 18 fixed = 812 total (was 830)

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

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

+1 :green_heart:
hadoopcheck
5m 49s
Patch does not cause any errors with Hadoop 2.8.5 2.9.2.

+1 :green_heart:
javadoc
0m 34s
the patch passed with JDK v1.8.0_262

+1 :green_heart:
javadoc
0m 47s
the patch passed with JDK v1.7.0_272

+1 :green_heart:
findbugs
3m 25s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
129m 23s
hbase-server in the patch passed.

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

191m 20s

Subsystem
Report/Notes

Docker
Client=19.03.13 Server=19.03.13 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2576/5/artifact/out/Dockerfile

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

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile

uname
Linux 5cdf62c42e3c 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-agent/workspace/Base-PreCommit-GitHub-PR_PR-2576/out/precommit/personality/provided.sh

git revision
branch-1 / b30d1d1

Default Java
1.7.0_272

Multi-JDK versions
/usr/lib/jvm/zulu-8-amd64:1.8.0_262 /usr/lib/jvm/zulu-7-amd64:1.7.0_272

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

Max. process+thread count
3979 (vs. ulimit of 10000)

modules
C: hbase-server U: hbase-server

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

versions
git=1.9.1 maven=3.0.5 findbugs=3.0.1

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

This message was automatically generated.

Rebase and address review feedback

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

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

_ Prechecks _

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

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

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

+1 :green_heart:
test4tests
0m  0s
The patch appears to include 7 new or modified test files.

_ branch-1 Compile Tests _

+1 :green_heart:
mvninstall
9m 45s
branch-1 passed

+1 :green_heart:
compile
0m 40s
branch-1 passed with JDK v1.8.0_262

+1 :green_heart:
compile
0m 45s
branch-1 passed with JDK v1.7.0_272

+1 :green_heart:
checkstyle
1m 58s
branch-1 passed

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

+1 :green_heart:
javadoc
0m 48s
branch-1 passed with JDK v1.8.0_262

+1 :green_heart:
javadoc
0m 41s
branch-1 passed with JDK v1.7.0_272

+0 :ok:
spotbugs
3m  3s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
3m  0s
branch-1 passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
1m 54s
the patch passed

+1 :green_heart:
compile
0m 43s
the patch passed with JDK v1.8.0_262

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

+1 :green_heart:
compile
0m 45s
the patch passed with JDK v1.7.0_272

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

-1 :x:
checkstyle
1m 51s
hbase-server: The patch generated 2 new + 812 unchanged - 18 fixed = 814 total (was 830)

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

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

+1 :green_heart:
hadoopcheck
4m 42s
Patch does not cause any errors with Hadoop 2.8.5 2.9.2.

+1 :green_heart:
javadoc
0m 31s
the patch passed with JDK v1.8.0_262

+1 :green_heart:
javadoc
0m 41s
the patch passed with JDK v1.7.0_272

+1 :green_heart:
findbugs
2m 54s
the patch passed

_ Other Tests _

-1 :x:
unit
106m 46s
hbase-server in the patch failed.

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

158m 28s

Reason
Tests

Failed junit tests
hadoop.hbase.regionserver.wal.TestDurability

Subsystem
Report/Notes

Docker
Client=19.03.13 Server=19.03.13 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2576/6/artifact/out/Dockerfile

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

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile

uname
Linux 0192e4566ee5 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-home/workspace/Base-PreCommit-GitHub-PR_PR-2576/out/precommit/personality/provided.sh

git revision
branch-1 / b30d1d1

Default Java
1.7.0_272

Multi-JDK versions
/usr/lib/jvm/zulu-8-amd64:1.8.0_262 /usr/lib/jvm/zulu-7-amd64:1.7.0_272

checkstyle
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2576/6/artifact/out/diff-checkstyle-hbase-server.txt

unit
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2576/6/artifact/out/patch-unit-hbase-server.txt

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

Max. process+thread count
4255 (vs. ulimit of 10000)

modules
C: hbase-server U: hbase-server

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

versions
git=1.9.1 maven=3.0.5 findbugs=3.0.1

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

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

_ Prechecks _

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

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

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

+1 :green_heart:
test4tests
0m  0s
The patch appears to include 7 new or modified test files.

_ branch-1 Compile Tests _

+1 :green_heart:
mvninstall
9m 54s
branch-1 passed

+1 :green_heart:
compile
0m 41s
branch-1 passed with JDK v1.8.0_262

+1 :green_heart:
compile
0m 47s
branch-1 passed with JDK v1.7.0_272

+1 :green_heart:
checkstyle
2m  2s
branch-1 passed

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

+1 :green_heart:
javadoc
0m 49s
branch-1 passed with JDK v1.8.0_262

+1 :green_heart:
javadoc
0m 43s
branch-1 passed with JDK v1.7.0_272

+0 :ok:
spotbugs
3m 41s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
3m 38s
branch-1 passed

_ Patch Compile Tests _

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

+1 :green_heart:
compile
0m 51s
the patch passed with JDK v1.8.0_262

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

+1 :green_heart:
compile
1m  0s
the patch passed with JDK v1.7.0_272

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

-1 :x:
checkstyle
2m 10s
hbase-server: The patch generated 2 new + 812 unchanged - 18 fixed = 814 total (was 830)

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

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

+1 :green_heart:
hadoopcheck
5m 42s
Patch does not cause any errors with Hadoop 2.8.5 2.9.2.

+1 :green_heart:
javadoc
0m 36s
the patch passed with JDK v1.8.0_262

+1 :green_heart:
javadoc
0m 48s
the patch passed with JDK v1.7.0_272

+1 :green_heart:
findbugs
3m 23s
the patch passed

_ Other Tests _

-1 :x:
unit
114m 17s
hbase-server in the patch failed.

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

161m 15s

Reason
Tests

Failed junit tests
hadoop.hbase.regionserver.wal.TestDurability

Subsystem
Report/Notes

Docker
Client=19.03.13 Server=19.03.13 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2576/7/artifact/out/Dockerfile

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

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile

uname
Linux 72036043beee 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-home/workspace/Base-PreCommit-GitHub-PR_PR-2576/out/precommit/personality/provided.sh

git revision
branch-1 / b30d1d1

Default Java
1.7.0_272

Multi-JDK versions
/usr/lib/jvm/zulu-8-amd64:1.8.0_262 /usr/lib/jvm/zulu-7-amd64:1.7.0_272

checkstyle
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2576/7/artifact/out/diff-checkstyle-hbase-server.txt

unit
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2576/7/artifact/out/patch-unit-hbase-server.txt

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

Max. process+thread count
4148 (vs. ulimit of 10000)

modules
C: hbase-server U: hbase-server

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

versions
git=1.9.1 maven=3.0.5 findbugs=3.0.1

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

This message was automatically generated.

Unit test failure seems unrelated, probable flaky test
[ERROR]   TestDurability.testDurability:132->verifyWALCount:242 expected:<10> but was:<9>

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

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

_ Prechecks _

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

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

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

+1 :green_heart:
test4tests
0m  0s
The patch appears to include 7 new or modified test files.

_ branch-1 Compile Tests _

+1 :green_heart:
mvninstall
9m 52s
branch-1 passed

+1 :green_heart:
compile
0m 40s
branch-1 passed with JDK v1.8.0_262

+1 :green_heart:
compile
0m 46s
branch-1 passed with JDK v1.7.0_272

+1 :green_heart:
checkstyle
1m 59s
branch-1 passed

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

+1 :green_heart:
javadoc
0m 48s
branch-1 passed with JDK v1.8.0_262

+1 :green_heart:
javadoc
0m 40s
branch-1 passed with JDK v1.7.0_272

+0 :ok:
spotbugs
3m  5s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
3m  3s
branch-1 passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
1m 59s
the patch passed

+1 :green_heart:
compile
0m 43s
the patch passed with JDK v1.8.0_262

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

+1 :green_heart:
compile
0m 45s
the patch passed with JDK v1.7.0_272

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

-1 :x:
checkstyle
1m 48s
hbase-server: The patch generated 2 new + 812 unchanged - 18 fixed = 814 total (was 830)

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

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

+1 :green_heart:
hadoopcheck
4m 32s
Patch does not cause any errors with Hadoop 2.8.5 2.9.2.

+1 :green_heart:
javadoc
0m 31s
the patch passed with JDK v1.8.0_262

+1 :green_heart:
javadoc
0m 41s
the patch passed with JDK v1.7.0_272

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

_ Other Tests _

-1 :x:
unit
105m 47s
hbase-server in the patch failed.

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

148m  7s

Reason
Tests

FindBugs
module:hbase-server

Useless condition:canAbort == true at this point  At HRegion.java:[line 1647]

Failed junit tests
hadoop.hbase.regionserver.wal.TestDurability

Subsystem
Report/Notes

Docker
Client=19.03.13 Server=19.03.13 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2576/8/artifact/out/Dockerfile

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

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile

uname
Linux 47c840ede344 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-home/workspace/Base-PreCommit-GitHub-PR_PR-2576/out/precommit/personality/provided.sh

git revision
branch-1 / 8813b3b

Default Java
1.7.0_272

Multi-JDK versions
/usr/lib/jvm/zulu-8-amd64:1.8.0_262 /usr/lib/jvm/zulu-7-amd64:1.7.0_272

checkstyle
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2576/8/artifact/out/diff-checkstyle-hbase-server.txt

findbugs
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2576/8/artifact/out/new-findbugs-hbase-server.html

unit
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2576/8/artifact/out/patch-unit-hbase-server.txt

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

Max. process+thread count
4226 (vs. ulimit of 10000)

modules
C: hbase-server U: hbase-server

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

versions
git=1.9.1 maven=3.0.5 findbugs=3.0.1

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

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

_ Prechecks _

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

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

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

+1 :green_heart:
test4tests
0m  0s
The patch appears to include 7 new or modified test files.

_ branch-1 Compile Tests _

+1 :green_heart:
mvninstall
9m 57s
branch-1 passed

+1 :green_heart:
compile
0m 43s
branch-1 passed with JDK v1.8.0_262

+1 :green_heart:
compile
0m 48s
branch-1 passed with JDK v1.7.0_272

+1 :green_heart:
checkstyle
2m  9s
branch-1 passed

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

+1 :green_heart:
javadoc
0m 48s
branch-1 passed with JDK v1.8.0_262

+1 :green_heart:
javadoc
0m 43s
branch-1 passed with JDK v1.7.0_272

+0 :ok:
spotbugs
3m 19s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
3m 14s
branch-1 passed

_ Patch Compile Tests _

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

+1 :green_heart:
compile
0m 42s
the patch passed with JDK v1.8.0_262

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

+1 :green_heart:
compile
0m 48s
the patch passed with JDK v1.7.0_272

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

+1 :green_heart:
checkstyle
1m 58s
hbase-server: The patch generated 0 new + 812 unchanged - 18 fixed = 812 total (was 830)

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

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

+1 :green_heart:
hadoopcheck
4m 56s
Patch does not cause any errors with Hadoop 2.8.5 2.9.2.

+1 :green_heart:
javadoc
0m 32s
the patch passed with JDK v1.8.0_262

+1 :green_heart:
javadoc
0m 43s
the patch passed with JDK v1.7.0_272

+1 :green_heart:
findbugs
3m  9s
the patch passed

_ Other Tests _

-1 :x:
unit
120m  9s
hbase-server in the patch failed.

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

165m 21s

Reason
Tests

Failed junit tests
hadoop.hbase.regionserver.wal.TestDurability

Subsystem
Report/Notes

Docker
Client=19.03.13 Server=19.03.13 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2576/9/artifact/out/Dockerfile

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

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile

uname
Linux bb6793eef2ba 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-home/workspace/Base-PreCommit-GitHub-PR_PR-2576/out/precommit/personality/provided.sh

git revision
branch-1 / 8813b3b

Default Java
1.7.0_272

Multi-JDK versions
/usr/lib/jvm/zulu-8-amd64:1.8.0_262 /usr/lib/jvm/zulu-7-amd64:1.7.0_272

unit
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2576/9/artifact/out/patch-unit-hbase-server.txt

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2576/9/testReport/

Max. process+thread count
3539 (vs. ulimit of 10000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2576/9/console

versions
git=1.9.1 maven=3.0.5 findbugs=3.0.1

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

This message was automatically generated.

The repeatable TestDurability failure looks germane, checking

Fix TestDurability and reduce whitespace divergence

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

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

_ Prechecks _

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

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

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

+1 :green_heart:
test4tests
0m  0s
The patch appears to include 7 new or modified test files.

_ branch-1 Compile Tests _

+1 :green_heart:
mvninstall
10m 13s
branch-1 passed

+1 :green_heart:
compile
0m 48s
branch-1 passed with JDK v1.8.0_262

+1 :green_heart:
compile
0m 52s
branch-1 passed with JDK v1.7.0_272

+1 :green_heart:
checkstyle
2m 17s
branch-1 passed

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

+1 :green_heart:
javadoc
0m 53s
branch-1 passed with JDK v1.8.0_262

+1 :green_heart:
javadoc
0m 46s
branch-1 passed with JDK v1.7.0_272

+0 :ok:
spotbugs
3m 25s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
3m 21s
branch-1 passed

_ Patch Compile Tests _

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

+1 :green_heart:
compile
0m 46s
the patch passed with JDK v1.8.0_262

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

+1 :green_heart:
compile
0m 56s
the patch passed with JDK v1.7.0_272

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

+1 :green_heart:
checkstyle
2m  7s
hbase-server: The patch generated 0 new + 812 unchanged - 18 fixed = 812 total (was 830)

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

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

+1 :green_heart:
hadoopcheck
5m 13s
Patch does not cause any errors with Hadoop 2.8.5 2.9.2.

+1 :green_heart:
javadoc
0m 36s
the patch passed with JDK v1.8.0_262

+1 :green_heart:
javadoc
0m 44s
the patch passed with JDK v1.7.0_272

+1 :green_heart:
findbugs
3m 20s
the patch passed

_ Other Tests _

-1 :x:
unit
112m 34s
hbase-server in the patch failed.

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

160m 10s

Reason
Tests

Failed junit tests
hadoop.hbase.regionserver.wal.TestDurability

Subsystem
Report/Notes

Docker
Client=19.03.13 Server=19.03.13 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2576/10/artifact/out/Dockerfile

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

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile

uname
Linux 3d74a327ed81 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-home/workspace/Base-PreCommit-GitHub-PR_PR-2576/out/precommit/personality/provided.sh

git revision
branch-1 / 3238abc

Default Java
1.7.0_272

Multi-JDK versions
/usr/lib/jvm/zulu-8-amd64:1.8.0_262 /usr/lib/jvm/zulu-7-amd64:1.7.0_272

unit
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2576/10/artifact/out/patch-unit-hbase-server.txt

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2576/10/testReport/

Max. process+thread count
3847 (vs. ulimit of 10000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2576/10/console

versions
git=1.9.1 maven=3.0.5 findbugs=3.0.1

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

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

_ Prechecks _

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

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

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

+1 :green_heart:
test4tests
0m  0s
The patch appears to include 7 new or modified test files.

_ branch-1 Compile Tests _

+1 :green_heart:
mvninstall
9m 47s
branch-1 passed

+1 :green_heart:
compile
0m 40s
branch-1 passed with JDK Azul Systems, Inc.-1.8.0_262-b19

+1 :green_heart:
compile
0m 46s
branch-1 passed with JDK Azul Systems, Inc.-1.7.0_272-b10

+1 :green_heart:
checkstyle
2m  2s
branch-1 passed

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

+1 :green_heart:
javadoc
0m 47s
branch-1 passed with JDK Azul Systems, Inc.-1.8.0_262-b19

+1 :green_heart:
javadoc
0m 40s
branch-1 passed with JDK Azul Systems, Inc.-1.7.0_272-b10

+0 :ok:
spotbugs
3m  4s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
3m  1s
branch-1 passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
1m 53s
the patch passed

+1 :green_heart:
compile
0m 41s
the patch passed with JDK Azul Systems, Inc.-1.8.0_262-b19

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

+1 :green_heart:
compile
0m 47s
the patch passed with JDK Azul Systems, Inc.-1.7.0_272-b10

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

+1 :green_heart:
checkstyle
1m 52s
hbase-server: The patch generated 0 new + 812 unchanged - 18 fixed = 812 total (was 830)

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

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

+1 :green_heart:
hadoopcheck
4m 42s
Patch does not cause any errors with Hadoop 2.8.5 2.9.2.

+1 :green_heart:
javadoc
0m 31s
the patch passed with JDK Azul Systems, Inc.-1.8.0_262-b19

+1 :green_heart:
javadoc
0m 41s
the patch passed with JDK Azul Systems, Inc.-1.7.0_272-b10

+1 :green_heart:
findbugs
2m 55s
the patch passed

_ Other Tests _

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

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

148m 12s

Subsystem
Report/Notes

Docker
ClientAPI=1.40 ServerAPI=1.40 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2576/11/artifact/out/Dockerfile

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

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile

uname
Linux 7c68353fe2b3 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-home/workspace/Base-PreCommit-GitHub-PR_PR-2576/out/precommit/personality/provided.sh

git revision
branch-1 / e315e63

Default Java
Azul Systems, Inc.-1.7.0_272-b10

Multi-JDK versions
/usr/lib/jvm/zulu-8-amd64:Azul Systems, Inc.-1.8.0_262-b19 /usr/lib/jvm/zulu-7-amd64:Azul Systems, Inc.-1.7.0_272-b10

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2576/11/testReport/

Max. process+thread count
4116 (vs. ulimit of 10000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2576/11/console

versions
git=1.9.1 maven=3.0.5 findbugs=3.0.1

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

This message was automatically generated.

_ Prechecks _

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

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

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

+1 :green_heart:
test4tests
0m  0s
The patch appears to include 7 new or modified test files.

_ branch-1 Compile Tests _

+1 :green_heart:
mvninstall
10m  6s
branch-1 passed

+1 :green_heart:
compile
0m 42s
branch-1 passed with JDK Azul Systems, Inc.-1.8.0_262-b19

+1 :green_heart:
compile
0m 49s
branch-1 passed with JDK Azul Systems, Inc.-1.7.0_272-b10

+1 :green_heart:
checkstyle
2m 11s
branch-1 passed

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

+1 :green_heart:
javadoc
0m 49s
branch-1 passed with JDK Azul Systems, Inc.-1.8.0_262-b19

+1 :green_heart:
javadoc
0m 43s
branch-1 passed with JDK Azul Systems, Inc.-1.7.0_272-b10

+0 :ok:
spotbugs
3m 17s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
3m 13s
branch-1 passed

_ Patch Compile Tests _

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

+1 :green_heart:
compile
0m 43s
the patch passed with JDK Azul Systems, Inc.-1.8.0_262-b19

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

+1 :green_heart:
compile
0m 48s
the patch passed with JDK Azul Systems, Inc.-1.7.0_272-b10

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

-1 :x:
checkstyle
1m 59s
hbase-server: The patch generated 1 new + 812 unchanged - 18 fixed = 813 total (was 830)

-1 :x:
whitespace
0m  0s
The patch 2 line(s) with tabs.

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

+1 :green_heart:
hadoopcheck
4m 57s
Patch does not cause any errors with Hadoop 2.8.5 2.9.2.

+1 :green_heart:
javadoc
0m 32s
the patch passed with JDK Azul Systems, Inc.-1.8.0_262-b19

+1 :green_heart:
javadoc
0m 43s
the patch passed with JDK Azul Systems, Inc.-1.7.0_272-b10

+1 :green_heart:
findbugs
3m  7s
the patch passed

_ Other Tests _

-1 :x:
unit
107m 36s
hbase-server in the patch failed.

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

152m 55s

Reason
Tests

Failed junit tests
hadoop.hbase.security.visibility.TestVisibilityLabelsWithACL

Subsystem
Report/Notes

Docker
ClientAPI=1.40 ServerAPI=1.40 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2576/12/artifact/out/Dockerfile

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

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile

uname
Linux ced0fb91338f 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-home/workspace/Base-PreCommit-GitHub-PR_PR-2576/out/precommit/personality/provided.sh

git revision
branch-1 / 16b91c8

Default Java
Azul Systems, Inc.-1.7.0_272-b10

Multi-JDK versions
/usr/lib/jvm/zulu-8-amd64:Azul Systems, Inc.-1.8.0_262-b19 /usr/lib/jvm/zulu-7-amd64:Azul Systems, Inc.-1.7.0_272-b10

checkstyle
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2576/12/artifact/out/diff-checkstyle-hbase-server.txt

whitespace
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2576/12/artifact/out/whitespace-tabs.txt

unit
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2576/12/artifact/out/patch-unit-hbase-server.txt

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2576/12/testReport/

Max. process+thread count
3029 (vs. ulimit of 10000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2576/12/console

versions
git=1.9.1 maven=3.0.5 findbugs=3.0.1

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
6m 45s
Docker mode activated.

_ Prechecks _

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

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

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

+1 :green_heart:
test4tests
0m  0s
The patch appears to include 7 new or modified test files.

_ branch-1 Compile Tests _

+1 :green_heart:
mvninstall
9m 56s
branch-1 passed

+1 :green_heart:
compile
0m 41s
branch-1 passed with JDK Azul Systems, Inc.-1.8.0_262-b19

+1 :green_heart:
compile
0m 45s
branch-1 passed with JDK Azul Systems, Inc.-1.7.0_272-b10

+1 :green_heart:
checkstyle
2m  1s
branch-1 passed

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

+1 :green_heart:
javadoc
0m 48s
branch-1 passed with JDK Azul Systems, Inc.-1.8.0_262-b19

+1 :green_heart:
javadoc
0m 40s
branch-1 passed with JDK Azul Systems, Inc.-1.7.0_272-b10

+0 :ok:
spotbugs
3m  4s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
3m  1s
branch-1 passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
1m 58s
the patch passed

+1 :green_heart:
compile
0m 41s
the patch passed with JDK Azul Systems, Inc.-1.8.0_262-b19

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

+1 :green_heart:
compile
0m 45s
the patch passed with JDK Azul Systems, Inc.-1.7.0_272-b10

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

+1 :green_heart:
checkstyle
1m 50s
hbase-server: The patch generated 0 new + 812 unchanged - 18 fixed = 812 total (was 830)

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

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

+1 :green_heart:
hadoopcheck
4m 39s
Patch does not cause any errors with Hadoop 2.8.5 2.9.2.

+1 :green_heart:
javadoc
0m 30s
the patch passed with JDK Azul Systems, Inc.-1.8.0_262-b19

+1 :green_heart:
javadoc
0m 40s
the patch passed with JDK Azul Systems, Inc.-1.7.0_272-b10

+1 :green_heart:
findbugs
2m 55s
the patch passed

_ Other Tests _

-1 :x:
unit
97m 23s
hbase-server in the patch failed.

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

145m 50s

Subsystem
Report/Notes

Docker
ClientAPI=1.40 ServerAPI=1.40 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2576/13/artifact/out/Dockerfile

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

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile

uname
Linux abd762f42245 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-home/workspace/Base-PreCommit-GitHub-PR_PR-2576/out/precommit/personality/provided.sh

git revision
branch-1 / 16b91c8

Default Java
Azul Systems, Inc.-1.7.0_272-b10

Multi-JDK versions
/usr/lib/jvm/zulu-8-amd64:Azul Systems, Inc.-1.8.0_262-b19 /usr/lib/jvm/zulu-7-amd64:Azul Systems, Inc.-1.7.0_272-b10

unit
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2576/13/artifact/out/patch-unit-hbase-server.txt

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2576/13/testReport/

Max. process+thread count
4049 (vs. ulimit of 10000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2576/13/console

versions
git=1.9.1 maven=3.0.5 findbugs=3.0.1

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

This message was automatically generated.


Process partition metadata in event of topic-level error

As per 1b465e78c274a76c0a522272cac25e39ddaa0d07, "I can't think of a case where
the stale data from the last "complete" update is somehow more useful than the
up-to-date partial data."
@wvanbergen

Anyway, this makes sense. :+1:


ER_WRONG_FIELD_WITH_GROUP when attempting to connect

I'm suddenly getting this error when trying to connect to any of my databases:

Error while preparing columns completions for connection redacted-Develop Core ER_WRONG_FIELD_WITH_GROUP: Expression #4 of SELECT list is not in GROUP BY clause and contains nonaggregated column 'information_schema.f.ROUTINE_NAME' which is not functionally dependent on columns in GROUP BY clause; this is incompatible with sql_mode=only_full_group_by Would you like to see the logs?

MySQL 5.7
Google Cloud SQL
Global settings:
"sqltools.connections": [
    {
      "askForPassword": false,
      "connectionTimeout": 30,
      "database": "core",
      "dialect": "MySQL",
      "name": "REDACTED Core",
      "password": "REDACTED",
      "port": 3306,
      "server": "REDACTED",
      "username": "REDACTED"
    },
    {
      "askForPassword": false,
      "connectionTimeout": 30,
      "database": "core",
      "dialect": "MySQL",
      "name": "REDACTED Core",
      "password": "REDACTED",
      "port": 3306,
      "server": "REDACTED",
      "username": "REDACTED"
    }
  ]

The only recent change I've made to the database is dropping the core database and creating it again with collation: utf8mb4_general_ci

Hi! My extension use database.connections key in VS Code setting. You probably use other SQL extension for VS Code. Start using my extension or write issue in another repository ;)

Oh god 😅 sorry!

I found it 😅
(link in case google brings anyone here) https://github.com/mtxr/vscode-sqltools/issues/176
Apologies again!

You have no reason for Apologize! I'm happy you've solved your problem :)


Need syntax to auto-expand Query Trees

Hi,
I use the embed Query feature a lot for sprint planning. But what´s really annoying is that Queries that return a Tree of Work Items must be expanded manually. I need a way to auto-expand the tree so the users can see it all at once.

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

ID: 29f1e43f-a069-dd88-7fc7-9cc497fb94f0
Version Independent ID: c261afa7-6eb7-b3f0-9f92-6d2f3c5ac336
Content: Markdown syntax for wikis in Azure DevOps - Azure DevOps
Content Source: docs/project/wiki/wiki-markdown-guidance.md
Product: devops
Technology: devops-collab
GitHub Login: @chcomley
Microsoft Alias: chcomley

@mabeyer Thank you for the feedback.
Please refer to the Azure DevOps community for product-related issues, or contribute to a similar post recently submitted here.
For any other documentation concerns, please use the comments below.


⚠ Bofrost.at has degraded performance

In 712d759, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 2517 ms

Resolved: Bofrost.at performance has improved in 50abce6 after 29 minutes.


font-url doesn't use digest version of asset with ? or # suffix

This is related to #49 I think, but it doesn't seem like font-url uses digest versions of assets when there is a # or ? in the font path.

Font's are not treated the same as the other asset classes: https://github.com/rails/sass-rails/blob/master/lib/sass/rails/helpers.rb#L29-35
I don't really understand why this is the case, but @spastorino made the change so I assume it's right. Maybe he can comment.

@agibralter is this still an issue for you using Rails 3-2-stable and sass-rails 3-2-stable branches?

@spastorino Hmm I haven't had a chance to try it out... but now I can't remember if this ended up being a compass issue... could it have anything to do with https://github.com/chriseppstein/compass/issues/630?

/cc @chriseppstein


Make compatibale with rails 2.5.0.rc1

Fix for issue #94 . I'm not sure this if there is a better way to approach this though.

Even tough the tests pass, I've discovered trough my app that it's not as simple as this. There are other changes that affect this gem. I'll look into this a bit deeper and try and prepare a complete PR.


Support Python 3.12

While trying to build the latest release, 3.9.0 against py3.12, we found some issue:
/opt/homebrew/Cellar/pter/3.9.0/libexec/lib/python3.12/site-packages/pter/utils.py:21: SyntaxWarning: invalid escape sequence '\s'
  EMPTY_FIELD_RE = re.compile('([a-z]+[:])(?:\s|$)')
To start pter you must provide at least one todo.txt file. See --help for more information.

relates to https://github.com/Homebrew/homebrew-core/pull/151150

I'll get right on it!

Alright, fixed in version 3.10.0 (also on pypi).
Thanks for letting me know about this!

still repro with 3.10.0

virtualenv -p python3.12 . && source bin/activate
pip install pter

That’s strange. I cannot reproduce that issue:
# pter --version
pter 3.10.0
# python --version
Python 3.12.0
# pter todo.txt

Is it the same error message, about the SyntaxWarning?

There's a curses issue that should work on Python 3.12 on macOS after https://github.com/python/cpython/issues/111460 is resolved.

Thank you @dtrodrigues for pointing that out!

seems working fine now with 3.11.4 release, https://github.com/Homebrew/homebrew-core/pull/157699. Closing.


feat: sentry-dramatiq integration

Problem Statement
5 years ago I created sentry-dramatiq and there seems to be some active users. I am no longer maintaining the library as I no use Python.
Solution Brainstorm
Would you consider integrating it into sentry-sdk or perhaps taking over the maintenance of the project?

Hey @jacobsvante, first of all thank you for your work on the integration and for maintaining it. We'd be happy to make this part of the SDK.
How would you prefer we go about this? Will you open a PR against sentry-python or should we take care of everything? (I'd prefer the former so that you get proper credit in commit history, but up to you.)

Thank you for the swift response and for your willingness to integrate it! As I no longer work with Python I think it'd be best if you add the actual code. I don't mind being without credit 😊

@antonpirker sounds good!

@jacobsvante the dramatic integration has been released in Python SDK version 2.13.0:
https://github.com/getsentry/sentry-python/releases/tag/2.13.0
Thanks again for the great work and the donation of your code!

This is great news. Thanks for integrating it!

@jacobsvante As a user of sentry-dramatiq, thank you for maintaining the library for the past years – and for finding a new maintainer 🙌