Response is not received by the clients

Title: Response is not received by the client
Description:
Hello,
We are experiencing an issue with Envoy Proxy, which is likely related to the default configuration.
The problem is that clients do not receive a response until Envoy reaches the request timeout, which is currently set to 1 hour. The request itself takes approximately 15 minutes to process (as seen in our service logs where the request is completed and results are returned), so duration doesn’t seem to be the issue. I also tested the same request by bypassing Envoy Proxy, and the response body was received correctly.
It may be worth mentioning that the response byte size is 3,479,806. When we run smaller requests, we are able to receive the response through Envoy Proxy without issues.
can you please point me the config I need to change, I didn't find something like response body size limit in your doc ?
salah

What version of envoy are you using? What version of HTTP is your client using? What is your envoy config?
You could gather access log: https://www.envoyproxy.io/docs/envoy/latest/configuration/observability/access_log/usage
or enable more verborse logging https://www.envoyproxy.io/docs/envoy/latest/operations/cli.html#cmdoption-l

cc @tyxia

Hello,

envoy version : 1.30_distroless

envoy config :

cds.yaml ############################################
`
resources:

"@type": type.googleapis.com/envoy.config.cluster.v3.Cluster
name: gcp_metadata_server
connect_timeout: 5000s
type: strict_dns
lb_policy: round_robin
load_assignment:
cluster_name: gcp_metadata_server
endpoints:
- lb_endpoints:
- endpoint:
address:
socket_address:
address: metadata.google.internal
port_value: 80

'@type': type.googleapis.com/envoy.config.cluster.v3.Cluster
circuit_breakers:
thresholds:

max_connections: 100000
max_pending_requests: 100000
max_requests: 100000
max_retries: 3
max_connections: 100000
max_pending_requests: 100000
max_requests: 100000
priority: HIGH

typed_extension_protocol_options:
envoy.extensions.upstreams.http.v3.HttpProtocolOptions:
"@type": "type.googleapis.com/envoy.extensions.upstreams.http.v3.HttpProtocolOptions"
common_http_protocol_options:
idle_timeout: 0s
explicit_http_config:
http_protocol_options: {}
connect_timeout: 120s
dns_lookup_family: V4_ONLY
type: LOGICAL_DNS
dns_refresh_rate: 100s
load_assignment:
cluster_name: service_python-fastapi-dev-0-cloudrun
endpoints:
lb_endpoints:

endpoint:
address:
socket_address:
address: python-fastapi-dev-0-xxxxxxxxxxxxx.a.run.app
port_value: 443
metadata:
typed_filter_metadata:
envoy.filters.http.gcp_authn:
'@type': type.googleapis.com/envoy.extensions.filters.http.gcp_authn.v3.Audience
url: https://python-fastapi-dev-0-xxxxxxxxxxxxx.a.run.app
name: service_python-fastapi-dev-0-cloudrun
transport_socket:
name: envoy.transport_sockets.tls
typed_config:
'@type': type.googleapis.com/envoy.extensions.transport_sockets.tls.v3.UpstreamTlsContext
common_tls_context:
alpn_protocols:

HTTP/2
validation_context:
trusted_ca:
filename: /etc/ssl/certs/ca-certificates.crt
sni: python-fastapi-dev-0-xxxxxxxxxxxxx.a.run.app

'@type': type.googleapis.com/envoy.config.cluster.v3.Cluster
circuit_breakers:
thresholds:

max_connections: 100000
max_pending_requests: 100000
max_requests: 100000
max_retries: 3
max_connections: 100000
max_pending_requests: 100000
max_requests: 100000
priority: HIGH
connect_timeout: 120s
dns_lookup_family: V4_ONLY
dns_refresh_rate: 100s
http2_protocol_options: {}
load_assignment:
cluster_name: service_python-fastapi-dev-1-gke
endpoints:
lb_endpoints:

endpoint:
address:
socket_address:
address: python-fastapi-dev-1.gke_cluster.gcp_project_id.dev.gcp.cloud.uk
port_value: 443
name: service_python-fastapi-dev-1-gke
transport_socket:
name: envoy.transport_sockets.tls
typed_config:
'@type': type.googleapis.com/envoy.extensions.transport_sockets.tls.v3.UpstreamTlsContext
common_tls_context:
alpn_protocols:

h2
sni: python-fastapi-dev-1.gke_cluster.gcp_project_id.dev.gcp.cloud.uk
type: STRICT_DNS **lds.yaml #############################################**
resources:

'@type': type.googleapis.com/envoy.config.listener.v3.Listener
name: listener_1
address:
socket_address:
address: <IP_ADDRESS>
port_value: 7070
filter_chains:
- filters:
- name: envoy.filters.network.http_connection_manager
typed_config:
'@type': type.googleapis.com/envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager
access_log:
- filter:
not_health_check_filter: {}
name: envoy.access_loggers.billing
typed_config:
'@type': type.googleapis.com/envoy.extensions.access_loggers.file.v3.FileAccessLog
log_format:
json_format:
email: '%REQ(X-User-Email)%'
endpoint: '%REQ(x-envoy-original-path)%'
log_name: billing
request_duration: '%DURATION%'
request_method: '%REQ(:METHOD)%'
response_code: '%RESPONSE_CODE%'
service-name: '%UPSTREAM_CLUSTER%'
user_id: '%REQ(X-User-Id)%'
path: /dev/stdout
stat_prefix: ingress_http
stream_idle_timeout: 3600s
route_config:
name: local_route
virtual_hosts:
- domains:
- ''
name: local_service
routes:
- match:
prefix: /python-fastapi-dev-0/
route:
cluster: service_python-fastapi-dev-0-cloudrun
host_rewrite_literal: python-fastapi-dev-0-xxxxxxxxxxxxx.a.run.app
prefix_rewrite: /
timeout: 0s
- match:
prefix: /python-fastapi-dev-1/
route:
cluster: service_python-fastapi-dev-1-gke
host_rewrite_literal: python-fastapi-dev-1.gke_cluster.gcp_project_id.dev.gcp.cloud.uk
prefix_rewrite: /
timeout: 0s

http_filters:
- name: envoy.filters.http.jwt_authn
typed_config:
'@type': type.googleapis.com/envoy.extensions.filters.http.jwt_authn.v3.JwtAuthentication
providers:
keycloak:
forward: true
forward_payload_header: x-jwt-payload
from_headers:
- name: Authorization
value_prefix: 'Bearer '
issuer: https://keycloak:8443/realms/project
payload_in_metadata: verified_jwt
remote_jwks:
cache_duration: 300s
http_uri:
cluster: keycloak
timeout: 5s
uri: https://keycloak:8443/realms/project/protocol/openid-connect/certs
rules:
- match:
safe_regex:
regex: ^/app-uat-2/api.$
requires:
provider_name: keycloak
- name: envoy.filters.http.lua
typed_config:
'@type': type.googleapis.com/envoy.extensions.filters.http.lua.v3.Lua
inline_code: "function envoy_on_request(request_handle)\n\tlocal meta
\ =
request_handle:streamInfo():dynamicMetadata()\n\theaders = request_handle:headers()\n
\tfor key, value in pairs(meta) do\n\t  headers:add("X-User-Id"
, value.verified_jwt.preferred_username)\n\t  headers:add("X-User-Email"
, value.verified_jwt.email)\n      headers:add("X-User-Groups"
, table.concat(value.verified_jwt.groups, ","))\n      headers:add("
X-User-AuthURL", "https://keycloak:8443/realms/project\"
\ )\n\tend\n    local path = headers:get(":path")\n    if path
\ ~= nil and path ~= '' then\n      headers:add("X-Forwarded-Prefix"
, string.match(path, "(/[^/]+)") )\n    end\nend\n"
- name: envoy.extensions.filters.http.gcp_authn
typed_config:
'@type': type.googleapis.com/envoy.extensions.filters.http.gcp_authn.v3.GcpAuthnFilterConfig
http_uri:
cluster: gcp_metadata_server
timeout: 100s
uri: http://metadata.google.internal/computeMetadata/v1/instance/service-accounts/default/identity?audience=[AUDIENCE]
token_header:
name: X-Serverless-Authorization
value_prefix: 'Bearer '
- name: envoy.filters.http.router
typed_config:
'@type': type.googleapis.com/envoy.extensions.filters.http.router.v3.Router

transport_socket:
name: envoy.transport_sockets.tls
typed_config:
"@type": type.googleapis.com/envoy.extensions.transport_sockets.tls.v3.DownstreamTlsContext
common_tls_context:
tls_certificates:
- certificate_chain:
filename: "/etc/envoy/envoy.pem"
private_key:
filename: "/etc/envoy/envoy-priv.pem"
validation_context:
trusted_ca:
filename: /etc/envoy/CA.pem
**server config**
node:
cluster: test-cluster
id: test-id
dynamic_resources:
lds_config:
path: "/etc/envoy/lds.yaml"
cds_config:
path: "/etc/envoy/cds.yaml"
admin:
access_log_path: /tmp/admin_access.log
address:
socket_address:
protocol: TCP
address: <IP_ADDRESS>
port_value: 7000
`

logs :  nothing special, no errors just waiting for response.

[2024-11-13 11:41:37.722][1][trace][upstream] [source/extensions/clusters/strict_dns/strict_dns_cluster.cc:104] starting async DNS resolution for metadata.google.internal
[2024-11-13 11:41:37.722][1][debug][dns] [source/extensions/network/dns_resolver/cares/dns_impl.cc:369] dns resolution for metadata.google.internal started
[2024-11-13 11:41:37.723][1][trace][dns] [source/extensions/network/dns_resolver/cares/dns_impl.cc:332] Setting DNS resolution timer for 5000 milliseconds
[2024-11-13 11:41:37.723][1][trace][dns] [source/extensions/network/dns_resolver/cares/dns_impl.cc:332] Setting DNS resolution timer for 5000 milliseconds
[2024-11-13 11:41:37.792][1][trace][dns] [source/extensions/network/dns_resolver/cares/dns_impl.cc:332] Setting DNS resolution timer for 5000 milliseconds
[2024-11-13 11:41:37.796][1][trace][dns] [source/extensions/network/dns_resolver/cares/dns_impl.cc:332] Setting DNS resolution timer for 5000 milliseconds
[2024-11-13 11:41:37.799][1][debug][dns] [source/extensions/network/dns_resolver/cares/dns_impl.cc:159] dns resolution without records for metadata.google.internal
[2024-11-13 11:41:37.799][1][trace][dns] [source/extensions/network/dns_resolver/cares/dns_impl.cc:332] Setting DNS resolution timer for 5000 milliseconds
[2024-11-13 11:41:37.799][1][debug][dns] [source/extensions/network/dns_resolver/cares/dns_impl.cc:289] dns resolution for metadata.google.internal completed with status 0
[2024-11-13 11:41:37.800][1][trace][upstream] [source/extensions/clusters/strict_dns/strict_dns_cluster.cc:112] async DNS resolution complete for metadata.google.internal
[2024-11-13 11:41:37.800][1][debug][upstream] [source/common/upstream/upstream_impl.cc:458] transport socket match, socket default selected for host with address <IP_ADDRESS>:80
[2024-11-13 11:41:37.800][1][debug][upstream] [source/extensions/clusters/strict_dns/strict_dns_cluster.cc:177] DNS refresh rate reset for metadata.google.internal, refresh rate 5000 ms
[2024-11-13 11:41:40.270][1][debug][main] [source/server/server.cc:241] flushing stats
[2024-11-13 11:41:42.801][1][trace][upstream] [source/extensions/clusters/strict_dns/strict_dns_cluster.cc:104] starting async DNS resolution for metadata.google.internal
[2024-11-13 11:41:42.801][1][debug][dns] [source/extensions/network/dns_resolver/cares/dns_impl.cc:369] dns resolution for metadata.google.internal started
[2024-11-13 11:41:42.801][1][trace][dns] [source/extensions/network/dns_resolver/cares/dns_impl.cc:332] Setting DNS resolution timer for 5000 milliseconds
[2024-11-13 11:41:42.802][1][trace][dns] [source/extensions/network/dns_resolver/cares/dns_impl.cc:332] Setting DNS resolution timer for 5000 milliseconds
[2024-11-13 11:41:42.805][1][trace][dns] [source/extensions/network/dns_resolver/cares/dns_impl.cc:332] Setting DNS resolution timer for 5000 milliseconds
[2024-11-13 11:41:42.809][1][trace][dns] [source/extensions/network/dns_resolver/cares/dns_impl.cc:332] Setting DNS resolution timer for 5000 milliseconds
[2024-11-13 11:41:42.811][1][debug][dns] [source/extensions/network/dns_resolver/cares/dns_impl.cc:159] dns resolution without records for metadata.google.internal
[2024-11-13 11:41:42.811][1][trace][dns] [source/extensions/network/dns_resolver/cares/dns_impl.cc:332] Setting DNS resolution timer for 5000 milliseconds
[2024-11-13 11:41:42.812][1][debug][dns] [source/extensions/network/dns_resolver/cares/dns_impl.cc:289] dns resolution for metadata.google.internal completed with status 0
[2024-11-13 11:41:42.812][1][trace][upstream] [source/extensions/clusters/strict_dns/strict_dns_cluster.cc:112] async DNS resolution complete for metadata.google.internal
[2024-11-13 11:41:42.812][1][debug][upstream] [source/common/upstream/upstream_impl.cc:458] transport socket match, socket default selected for host with address <IP_ADDRESS>:80
[2024-11-13 11:41:42.812][1][debug][upstream] [source/extensions/clusters/strict_dns/strict_dns_cluster.cc:177] DNS refresh rate reset for metadata.google.internal, refresh rate 5000 ms
[2024-11-13 11:41:45.275][1][debug][main] [source/server/server.cc:241] flushing stats

the behavior is the next : we send a sync request that takes more than 10 min, in application log we see that the response is returned, but the downstream do not receive the response. when sync request take less than 10 min, downstream receive a 200 response with response body.  When we bypass envoy and send request a sync request that takes more than 10 min directly to service url, response is received ( envoy issue ).

I have run couple of additional tests, therefore it seems that we face an around 10 min timeout.
our target is to allow our users to be able to run max 1h sync request.

for your attention : @tyxia  @KBaichoo


Discord rate limits the update frequency of the presence

After a little bit, Discord starts to ratelimit the AV: line, plus it's mostly useless because of the "xx:xx left" line (which isn't rate limited due to it being set once) anyway.
This also means that it won't receive events for pausing once rate limited, causing it to keep counting down even after pausing.

As 1.5 does not have this issue, you can downgrade in the meantime if its bothering enough.

Is there any update on this issue?

The video progress (the AV: 00:01:19/00:51:08 row) in Rich Presence requires frequent updates to keep it real time.
But I don't think there is a workaround to bypass Discord's rate limit.
Perhaps a solution to this issue is to use something else rather than video progress for the text.
Any suggestions on what the text could be?

Would it be possible to add an option (maybe in the config) to update the video progress less frequently?
e.g. every 10 seconds, so Discord's rate limit wouldn't come into effect

Yes, that would be a great solution. I will try to implement it when I'm free.

Maybe the rate needs to be even lower?
But also games like League of Legends show exact time of match so there probably is another way of doing this

yeah that's what I was thinking about too. just deprecate that line and instead of updating based on an interval, updating after an action (pause,play,change title, etc) is performed

Throwing my hat into the ring here to say that I was even blocked by Cloudflare after around 2 hours:

My only guess is that Cloudflare thinks that it was an attempted DoS due to the amount of calls sent to the servers.
Now, while it's definitely possible that this didn't result from this integration, I've never got something like this in all my years of using Discord (even with spamming the Discord servers myself a bit) and it only appeared after starting to use this integration.
I honestly think that this is f*cking hilarious, but this is definitely a problem lmao

Throwing my hat into the ring here to say that I was even blocked by Cloudflare after around 2 hours:

My only guess is that Cloudflare thinks that it was an attempted DoS due to the amount of calls sent to the servers. Now, while it's definitely possible that this _didn't_ result from this integration, I've never got something like this in all my years of using Discord (even with spamming the Discord servers myself a bit) and it only appeared after starting to use this integration.
I honestly think that this is f*cking hilarious, but this is definitely a problem lmao

This was a global problem just over an hour ago, unrelated to this tool 👍

This was a global problem just over an hour ago, unrelated to this tool 👍

Ah, then I apologize. 🙇🏻
Unfortunate timing for me to start using this.


Numeric inputs and displays: Standardization based on language settings

This ticket was branched off of this comment: https://github.com/mercycorps/TolaActivity/issues/1214#issuecomment-569149946
I noticed some inconsistencies in what we accept in the Actual value field and in the disaggregated value fields. Turns out we need to standardize our rules for numeric inputs and displays in all languages, platform-wide. After sharing several options with the MEL team, we landed on the following criteria.
Acceptance criteria
All of the following rules apply anywhere we input or display numbers:

Result form
Target setup
Baseline field in targets tab -- while preserving current logic that a baseline can be zero
Program page (display only)
IPTT (display only)

Inputs

[ ] English: Require an American English style floating point (period).

[ ] Spanish: Require a Spanish style floating point (comma).

[ ]  French: Require a French style floating point (comma).

[ ] No letters and no other special characters ever allowed besides . and ,

Displays

[x] English: Numbers are displayed in American English style numbers, with a decimal floating point. Ideally, we apply other common conventions such as the comma as thousands separator.

[x] Spanish: Numbers are displayed in Spanish style numbers, with a comma floating point. Ideally, we apply other common conventions such as the period as thousands separator.

[x] French: Numbers are displayed in French style numbers, with a comma floating point. Ideally, we apply other common conventions such as the empty space as thousands separator.

Housekeeping (where applicable)

[ ] Unit test/s written
[ ] i18n strings included
[ ] Is accessible to people using screen readers

@jennyhavah confused by "Ideally, we apply other common conventions" under display - do we want to display all numbers with the thousands-separator appropriate for the language?  Or only certain ones?  (We have the IPTT, Program Page, Indicator Setup Form, and Results Form, currently all showing numbers with no thousands separator - should all of them move to a locale-aware thousands separator?)

Target setup:
I can enter < and > into target fields. This is true of LoP, Midline/Endline, time aware and Event targets. It's true on Chrome and Firefox, and in all 3 languages.

Not seeing language-specific thousands separators for displays. (Not a release blocker, but we'd discussed including this if it is not a high LoE.)

Looks like change log does not include language-specific number display settings. For example, not seeing a , as a floating point separator in French.

Tagging @sanjuroj for the change log element

Display issue, Spanish: Looks like the period separator is not appearing on the program page.
It does appear on the IPTT and changelog.
The expected thousands separator does appear on the program page for English and French.

Display issue, Indicator Plan: I'm not seeing any thousands separators in either of the 3 languages.
I forgot to list this one in the original issue description -- just added it.

Display issues, Change log:
Thousands separator missing for Baseline and for LoP target, though it does show up in the target frequency field -- in this example a LoP-only target frequency.

This example is in Spanish but the pattern is the same for French and English. For French, a space separator is missing in the same spots. For English, a comma separator.

@camgnostic Still seeing issues with the thousands separator in French and Spanish. English looks good.
French:

Need a space thousands separator for Target, Actual, and Result values. Looks good everywhere else.
Spanish:

Need a period thousands separator for Target, Actual, and Result values. Looks good everywhere else.

@jennyhavah I'm not seeing the same problem for the change log any more.  On QA (just ignore the two language thing from TOLA-313):

Can you point me to where you're seeing the non-separated numbers?

I'm not seeing the same problem for the change log any more. On QA (just ignore the two language thing from TOLA-313):

The change log is fine -- I put a 🎉 under that one. The only remaining issues have to do with the result table.

Thousands separators look good!


Country request: Greece

I'd like to request Greece be added to your queue. Thanks!

Greece is now available


Custom routing profile too big

Hey @nrenner, I merged latest changes into brouter.damsy.net, cool changes :)!
One small bug though, with the new right sidebar: when the profile custom option is shown, the sidebar grows to 4000px (400% height ~), which make the bottom toolbar hidden. I guess some CSS needs to be tweaked?

Oh my, flexbox is killing me. I'm sure this was working in Firefox at some point. Thanks for the report.


plpy

kbp10docs=# SELECT (__X.__COLUMN).doc_id, (__X.__COLUMN).mention_id, (__X.__COLUMN).sentence_id, (__X.__COLUMN).word, (__X.__COLUMN).type
kbp10docs-# FROM (SELECT func_ext_mention( doc_id, sentence_id, words, pos, ner, lemma, character_offset_begin, character_offset_end ) AS __COLUMN
kbp10docs(# from  sentence) as __X;
ERROR:  length of returned sequence did not match number of columns in row  (seg7 slice1 madmax4.stanford.edu:50007 pid=33719)
DETAIL:
while creating return value
PL/Python function "func_ext_mention"
Does not throw errors now

This bug is actually a more general non-termination bug when executing SQL queries by a file. Fixed in https://github.com/HazyResearch/deepdive/pull/251.


Double formatting in i18n fallback

When intl extension is not available, fallback formatting works wrong for double values:
echo Yii::t('app', 'Here is a big number: {n, number}', ['n' => 2e+8]);

// Intl: Here is a big number 200,000,000
// No intl: Exception(Message format 'number' is only supported for integer values.
--- Expected
+++ Actual
@@ @@
-'Here is a big number: 200,000,000'
+'Here is a big number: 200000000'
/home/travis/build/yiisoft/yii2/tests/framework/i18n/FallbackMessageFormatterTest.php:151
/home/travis/build/yiisoft/yii2/vendor/phpunit/phpunit/phpunit:36

Is it really needs to split thousands as with intl?

I don't see that current implementation supports any number formatting, we are getting just plain number:
MessageFormatter.php:345

https://github.com/yiisoft/yii2/commit/3b31aa771a4f59cbf4bc01202a3f29e994f14cdd


Added csrf support in form auth to request param as well

From<EMAIL_ADDRESS>on August 22, 2014 07:43:38
do it
Original issue: http://code.google.com/p/rest-assured/issues/detail?id=348

From<EMAIL_ADDRESS>on August 21, 2014 22:44:07
See https://spring.io/blog/2014/05/23/preview-spring-security-test-web-security

From<EMAIL_ADDRESS>on August 28, 2014 05:05:10
Status: Started

From<EMAIL_ADDRESS>on August 28, 2014 23:20:35
Status: Fixed


Core BTS UI Improvements

The overall objective of this epic is to update the user interface elements of the Android implementation of the Zashi cryptocurrency wallet conform to the design described by
https://www.figma.com/file/vYQD6uZtkPgtmgJ3zfauq0/Zashi-branding-ADJY-MOCK?type=design&node-id=0%3A1&mode=design&t=9FayedV7L5uAZNyV-1

Hello, welcome. Before anyone starts to work on these tasks, it's good to check our public documentation at:

Readme
Other important documentation like Contributing, Setup, and Architecture

Even though we are an open-source company and Android repositories are accessible publicly, we have a list of advice and undocumented things for a better understanding of our development process, which speeds up proper contribution. @nuttycom please, make sure that anyone who will participate on these tasks has access to the following:

Undocumented things for Android
Engineering Guide


CAD-608 trace-dispatcher library

This is trace-dispatcher, a library for tracing, which replaces the iohk-monitoring-framework.

It is build completely on the base of contravariant functors
Every aspect of tracing is controllable via the configuration, down to every individual message
It has the ability to document all tracing messages
It can be used beside the current tracing system in a first step
When the old tracing infrastucture will be removed it can be dynamically reconfigured in a running node
It is build for efficiency from the ground up, so that messages will never be stored

Documentation is included in docs/trace-dispatcher.md

I've gone through trace-dispatcher.md in detail now. I'll come back and look at the implementation soon.

The stdout thread is now link-ed to the main thread, thereby propagation exceptions and shutting down the node, in case that trivial thread raises any exceptions (i.e. stdout being closed or redirected stdout write hitting a full disc).

bors r+

bors r+

bors r+

bors r+


Create rule for role.level int >= 1

This is already handled by the smallint column type and a constraint. There's now code in RolesValidator that shows how to override default db table form validation if necessary.


Problem with installation via composer

I have a problem with installation via composer:
composer require spatie/pdf-to-image

Using version ^1.8 for spatie/pdf-to-image
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Can only install one of: spatie/pdf-to-image[1.8.0, dev-master].
    - Can only install one of: spatie/pdf-to-image[1.8.1, dev-master].
    - Installation request for spatie/pdf-to-image dev-master -> satisfiable by spatie/pdf-to-image[dev-master].
    - Installation request for spatie/pdf-to-image ^1.8 -> satisfiable by spatie/pdf-to-image[1.8.0, 1.8.1].

Installation failed, reverting ./composer.json to its original content.

Please use the why not command to find out what is blocking the package installation.
https://getcomposer.org/doc/03-cli.md#prohibits-why-not-


settings: Add dev-environment-only settings for information density.

This PR sets the stage for work on #12611 by adding settings to the development environment that store pixel-based font-size and line-height, and a separate pixel-based full-line value that will be used for adjusting the spacing between block-level elements.
CZO discussion
Screenshots and screen captures:

Self-review checklist

[x] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[x] Explains differences from previous plans (e.g., issue description).
[x] Highlights technical choices and bugs encountered.
[x] Calls out remaining decisions and concerns.
[x] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[x] Each commit is a coherent idea.
[x] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[x] Visual appearance of the changes.
[x] Responsiveness and internationalization.
[x] Strings and tooltips.
[x] End-to-end functionality of buttons, interactions and flows.
[x] Corner cases, error conditions, and easily imagined bugs.

What is Dense mode? I can't really tell... Should it be removed?

What is Dense mode? I can't really tell... Should it be removed?

Yes, outside of this PR. @timabbott had mentioned asking @sahil839 to look after some of these removals.

I don't know how to interpret the third option. I don't know if there's a better label to use?

I don't know how to interpret the third option. I don't know if there's a better label to use?

There probably is, @alya :) This is definitely just a dev-only bit of spartan UI for the time being. I expect by the time we've got this in front of users, we'll have a handful of preset options that will adjust these values behind the scenes, and likely a UI with sliders under an "Advanced..." label or something.

You need to do tools/renumber-migrations to update the migration numbers ... or actually given how far back this is and that there's multiple 501s, it's probably easier to just rename the file and its "dependencies" section.

You need to do tools/renumber-migrations to update the migration numbers ... or actually given how far back this is and that there's multiple 501s, it's probably easier to just rename the file and its "dependencies" section.

Took care of this. Thanks :)


[Sema diagnostics & Tests] Add Sema diagnostics for detecting large integer literals that overflow Builtin.Int2048.

and tests for checking the correctness of the diagnostics.

@DougGregor  Hi Doug, I have tried to implement the fix for detecting large integer overflows in the type checking phase, and added some tests including those that tests the raw value in the Enums. Let me know you what you think.  (ref: https://bugs.swift.org/browse/SR-7579?jql=text ~ "Large integer literals")

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test

@xedin I have moved the checks to CSGen phase as we had discussed. Let me know if it looks good.

@swift-ci Please test and merge

@swift-ci please test and merge


sink(ticdc): move changefeed uri parameter to config file

What problem does this PR solve?

Issue Number: close #8856
What is changed and how it works?
Check List
Tests

Unit test
Integration test
Manual test (add detailed scripts or steps below)
No code

Questions
Will it cause performance regression or break compatibility?
Do you need to update user documentation, design documentation or monitoring documentation?
Release note
 `None`.

/retest-required

/test verify

/test cdc-integration-mysql-test

/merge

/merge

/test verify

/merge

/test engine-integration-test

/test pull-dm-integration-test

/test dm-integration-test


Add badge number

Can I add badge number to tab, how to do

For now you can't do it, but we will add the feature later


add --runtime for dataset build

Current Behavior
Use the current activated shell environment to build the dataset.
Proposed Behavior

add --runtime, --runtime-restore argument for dataset building
record runtime uri in the _manifest.yaml

https://github.com/star-whale/starwhale/pull/1062


Implement more slice functions

First
Last
StartsWith
EndsWith
StripPrefix
StripSuffix
IsSorted
IsSortedBy
Sort
SortBy
BinarySearch
BinarySearchBy (requires Ordering)
Contains (linear search)
RotateLeft
RotateRight

Note: some of these are already implemented by golang.org/x/exp/slices


Adding the ability to set Mirroring on for front camera

a nicer experience when streaming from front camera

found a few issues, will update and repost

This will also mirror the output

I’m working on an updated version, will create a new pr

On Jul 2, 2015, at 18:24, james h<EMAIL_ADDRESS>wrote:
This will also mirror the output
—
Reply to this email directly or view it on GitHub https://github.com/jgh-/VideoCore/pull/162#issuecomment-118067408.

The easiest way to do this is by applying an affine transform to the preview view

Thanks for the tip, I did that! great library by the way.
I have an issue that is unrelated to mirroring. The second I stop the RTMP session, whatever I had in my stream buffer does not get transmitted to the RTMP server.
I mean - when I am streaming, the last 5 seconds of the stream get cut off. How do I keep that from hapenning?
I thought of setting a timer on my “stop” button and just waiting 5 or 10 seconds, but there must be a better way of flushing the buffer in the background or something?
What do you think?

On Jul 2, 2015, at 19:04, james h<EMAIL_ADDRESS>wrote:
affine transform


Switch to PKCE authorization

This should eliminate the need to compile in the client_secret and make it possible to release a firmware binary.
https://developer.spotify.com/documentation/general/guides/authorization-guide/#authorization-code-flow-with-proof-key-for-code-exchange-pkce

I have this implemented in https://github.com/quadule/knobby/tree/pkce but am not sure if I want to merge it. Spotify's PKCE implementation revokes the old refresh_token whenever fetching an access_token which complicates things slightly: If a network or device glitch ever prevents the updated refresh_token from being saved, the user would have to re-authenticate in a browser. This is also annoying when testing the software because it prevents sharing of tokens between devices.


Idea: migrate -> begin and complete -> commit

What do you think about using the verbs from transactions in reshape?

I've been giving the command naming a lot of thought so this is a good suggestion. I'm not sure I want to adopt the naming used for transactions though to avoid any confusion.
Perhaps something like reshape start and reshape complete? Or maybe even reshape migration start and reshape migration complete to make it clearer and leave room for other commands. Not sure yet.

Yeah, I like start/complete in either form as well.

Hi again! This took a while but finally got around to touching up the CLI a bit. The commands are now.

reshape migration start
reshape migration complete
reshape migration abort
reshape schema-query

The old ones are still supported but marked as deprecated.

Very nice! I might start using this again in a different personal project. Very excited about these updates

Nice! Let me know if there is anything you're missing for that project :)


Remove using IsThreadProvisioned condition to determine if device is commissioned to Matter fabric.

Problem
Currently in many places IsThreadProvisioned() method is used to check if device was commissioned to the Matter fabric or not. Based on that the decision is made if pairing window should be opened or not. That is not correct assumption, as it gives information only about Thread network state, so condition is true even if device was not commissioned to Matter, but Thread was configured manually. In the current implementation it will not be possible to commission to Matter the device that already has Thread enabled.
Code examples:

https://github.com/project-chip/connectedhomeip/blob/master/src/app/server/Server.cpp#L522
https://github.com/project-chip/connectedhomeip/blob/master/examples/lock-app/qpg/src/AppTask.cpp#L342

Proposed Solution
It seems to be reasonable start using IsFullyProvisioned() condition, however method implementation is not fully completed yet (https://github.com/project-chip/connectedhomeip/blob/master/src/include/platform/internal/GenericConfigurationManagerImpl.cpp#L923), so it should be also fixed to consider Matter fabric data.

@kkasperczyk-no Closing this, as it appears complete. Please re-open if not the case!


feat: Filters not working correctly in Snowflake

The PR makes the following changes:

Adds --filters tests for column and row validations across all engines. The filter includes the id column and a comparison column.
Moves the application of filters from after application of calculated fields to before them. This has two benefits:
2.1. We no longer rely on filtered columns bubbling up through the calculated field subqueries, we apply the filter to the actual table before doing anything else.
2.2 Because we apply the filter to the actual table and not the subqueries we are giving the query optimizer less work to do in trying to push the filter down to the source table.

After adding the tests described in point 1 above all tests passed except for the Snowflake row validation test.
After adding the change described in point 2 above all tests pass.
I'm not sure whether we should flag this change as a breaking change or not. If any users are using filters on calculated fields then these will no longer work. Only filters on real columns are supported.

/gcbrun

/gcbrun

Neil,
Looks good to me. Our documentation already says in the filters section The filter is written in the syntax of the given source and must reference columns in the underlying table, not projected DVT expressions.
I don't consider this a breaking change.
Sundar Mudupalli

/gcbrun

and must reference columns in the underlying table, not projected DVT expressions.

For info, I added the words and must reference columns in the underlying table, not projected DVT expressions. on this branch.

@nj1973 Please add BREAKING CHANGE: for any users that apply filters on calculated fields currently, even though this is an anti-pattern as a footer in the PR's commit message once we're able to merge it, thank you again for the awesome work!
Reference: https://www.conventionalcommits.org/en/v1.0.0/#commit-message-with-both--and-breaking-change-footer

/gcbrun

@nj1973 Please add BREAKING CHANGE: for any users that apply filters on calculated fields currently, even though this is an anti-pattern as a footer in the PR's commit message once we're able to merge it, thank you again for the awesome work!
Reference: https://www.conventionalcommits.org/en/v1.0.0/#commit-message-with-both--and-breaking-change-footer

Of course I forgot to add the BREAKING CHANGE message to the PR's commit!


🐛 false positive for package JSONStream

Prerequisites

[X] I'm using the latest version
[X] I've read the relevant documentation
[X] I've searched for existing issues
[X] I've checked the list of known issues
[X] I've read the issue reproduction guide

Reproduction url
https://codesandbox.io/p/github/boneskull/knip-jsonstream/main?import=true
Reproduction access

[X] I've made sure the reproduction is publicly accessible

Description of the issue
Noticed that JSONStream is not picked up correctly by knip.
My hunch is that the capitals in the package name are throwing it (or something) off, since you're not supposed to use capitals. 😄

Well, that's embarrassing, lol

:rocket: This issue has been resolved in v5.39.1. See Release 5.39.1 for release notes.
Using Knip in a commercial project? Please consider becoming a sponsor.

Thanks for the report, @boneskull!


Swiss QR Code: ZipCode is alphanumerical

Hi there
Suggestion for minor improvement:
As per definition the zip code in Swiss QR Code is alphanumerical.
In the current implementation only digits are allowed. Think of zip codes in the UK, e.g. "E2 8JL".
There is an official validation platform to test the QR codes: https://qr-validation.iso-payments.ch. According to the specs there, characters included in the following regex pattern are allowed:
([a-zA-Z0-9.,;:'\ -/()?*[]{}\`´~ ]|[!"#%&<>÷=@_$£]|[àáâäçèéêëìíîïñòóôöùúûüýßÀÁÂÄÇÈÉÊËÌÍÎÏÒÓÔÖÙÚÛÜÑ])*
Thank you

The same goes for "street". Numbers should be allowed there as well (same regex pattern). E.g. a P.O. box, which often contains a number ("Postfach 3000").

Hi @parabolika66 ,
thanks for your feedback. I hope I can fix it during the weekend. But if you can and want, feel free to fix it by yourself and sent in a pull request at Github.

Hi @codebude ,
your welcome and thanks to you. I am evaluating the library on a spec level, so we are not in a hurry yet.

Hi @parabolika66 ,
during the development I used the official SwissQRCode spec ( https://www.paymentstandards.ch/dam/downloads/ig-qr-bill-de.pdf ). In this document the zipcode (technical name: PstCd) is described as "a field with a maximum length of 16 chars". No further restrictions. That's why I added some additional regex to get some kind of validity check.
But if you say the official validation tool has some more specific rules, I'll update the library against those rules. So I registered for the validation tool, now. Unfortunately my registration is still pending. So I have to wait before I can fix it.

@parabolika66 - now I got access to the validation platform. But I can't see the specifications you named. From where do you got this regex? On the validation platform there's only the official specification document and this says:

According to the Swiss standard, in the Swiss QR Code, for reasons of compatibility
with the Swiss Implementation Guidelines for Credit Transfers for the ISO 20022
"Customer Credit Transfer Initiation" message (pain.001), only the Latin character set
is permitted.

Hi @codebude
I found the information re character set in the written spec very unprecise, that‘s why I made some tests against this validation tool.
I generated a qr code with invalid characters (https://qrcoderechnung.ch/qr) and tested it on the validation platform. It showed an error with a link to the specs. In this tree view you can check all fields and their patterns.
I am not at the office today, so can‘t provide any screenshots.

Hi @codebude
I found your issue here on base of a problem with the street attribute- but i agree with @parabolika66:
based on six-interbank-clearing.com and the validation portal the regex pattern would be:
([a-zA-Z0-9.,;:'+-/()?*[]{}\`´~ ]|[!"#%&<>÷=@_$£]|[àáâäçèéêëìíîïñòóôöùúûüýßÀÁÂÄÇÈÉÊËÌÍÎÏÒÓÔÖÙÚÛÜÑ])*

As  a sample for the street attribute:
Clinique du luminaire
rue du 31-Décembre 38
1207 Genève
As you see there are also street names in switzerland that contain numbers (31-Décembre) in them, which are not the streetnumber (would be 38 in the sample).
Any chance you get that fixed in your library soon?

Hi @Raydir , hi @parabolika66 ,
sorry that this took so much time. I did some more tests with the official validation tool and added the Regex pattern you posted to QRCoder. You can find it in this commit: https://github.com/codebude/QRCoder/commit/0a77cd840a9b22a67b4811e68ea7922e5047a14f
l also added this pattern as check for the name and city field (since the validation tool did so, too). Thanks again for your input and your patience.

Hi @Codebude
I'll send this info to our developers so they know that you resolved this issue.
Thanx a lot!

Hi @Raydir ,
just keep in mind that this is fixed only in source base by now. It's not in the Nuget package. But I'll release a/the new version on Nuget in the next couple of days.

sure thing thanx.

Hi @Raydir , @parabolika66 - it took some time, but this changes are part of the official Nuget package now. Feel free to use version 1.3.3 from Nuget to keep alway up-to-date.

Hey Codebude
I'll send this info to our developer.
Thanx!


Conventional paths docs

Docs for https://github.com/zeit/hyper/pull/3193.

Wow, amazing!
I'm sorry for the delayed response, but thank you so much for the contribution!


feature validation runs

implements #39 (validation runs)
Note: the current implementation does not use the result of validation-runs to select members of the HOF. That would be a separate issue. For now I want this merged as quickly as possible, so I can start comparing experiments. For updating the HOF, additional effort is needed, because the halloffame.update method takes the entire population and then does it's thing, based on the fitness of the entire population. At first glance I guess we need to reimplement that method to have it use the fitness from the validation run instead of the "old" fitness.

here is the first result of an experiment that uses validation runs (orange curve)

As expected the validation-curve is between the average of the population and the best individual.
you can find this specific experiment here: https://github.com/neuroevolution-ai/CTRNN_Simulation_Results/tree/master/data/2021-02-08_18-09-36

can be reviewed and merged @pdeubel

in this example the validation_fitness is less than the average of the generation

I think this is strange. It could mean an implementation error (even though I don't know what kind of error would create such results). Or it could mean, that the "best" individuum consistently was using a strategy, that doesn't generalize worse than the average, while being extremely lucky some rare situation.
the experiment can be found here: https://github.com/neuroevolution-ai/CTRNN_Simulation_Results/tree/master/data/2021-02-08_22-53-09
note, that in both cases (this experiment and the on in the last comment), lampda was 5000. So luck may indeed have played a significant role

i have a possible reason why in some cases the curve for the validation runs is below the average curve, and in some cases it's above: The validation in these examples takes place on a fixed set of 10 seeds. If some of them are especially easy, then the curve is bound to be higher. If the seeds are especially hard, then the curve has to be lower than.
A simple solution: increase the number of validation runs further.


FillBurn produces nonsensical output

Hello,
I would like to burn streams into my DEM, but the FillBurn tool gives a very strange output. I ran breach_depressions_least_cost on the dem first, which works fine, but it doesn't seem to make a difference to the output from FillBurn.
The streams are burned in, but the DEM is completely changed in a way that has nothing to do with the streams (I tried submitting completely different stream files and the result was the same, except for the streams themselves). It's hard to see how the resulting DEM even relates to the input DEM - it is broken into oddly shaped sectors and the elevation of the DEM is raised by many orders of magnitude.
I've attached the files I used. I am running this on scientific linux. I have recompiled the Rust library for my version of linux and all the other whitebox tools I've been using work absolutely fine. I am running it via the python API, although I suspect it's not an issue with the API itself. I have tried with whitebox-python 2.0.3 and 2.1.4 with the exact same result.
![FillBurn](https://user-images.githubusercontent.com/6304417/190666673-40f6cfb7-27bc-
I've attached the input DEM and streams shapefile and the output from FillBurn. Any help would be much appreciated.
fixed_dem.zip
4bbd-acd7-ab0d7bc426c5.png)

The issue is that your DEM has its NoData values defined as NaN but the value in the voids is Inf (reported by GDAL) which means that WBT interprets the voids as being only a very high value and not NoData. However, fixing that would lead to another issue as the streams vectors go past the extent of the raster. Those should stop before the perimeter (see https://github.com/jblindsay/whitebox-tools/issues/272 for details).

Ok, thanks for getting back to me. Unfortunately that doesn't seem to be the problem. The inf values must have been introduced when I clipped the raster to upload it - they weren't on the original raster that I was having trouble with. I've had another go and have uploaded a tif without inf values that reproduces the problem. The streams vector I uploaded previously will fit within the extent.
dem_clipped1.zip

I tested with your new dataset and the issue is really with the fact that the NoData is defined as NaN. If I change it to -9999 for example, then the result is as expected when using the provided vector streams. I haven't check how WBT interprets NaN inside a TIF file but it clearly doesn't do the expected thing.

@jfbourdon thank you, you are right, the NaNs were the problem.
@jblindsay will this tool also handle numpy inf values? I've noticed that the breach_depressions_least_cost tool adds inf values in, so my rasters can contain both NaN and inf. I tried using the modify_nodata_value tool to fix the issue, but it only changes the value registered as the nodata value in the raster profile.


HBASE-23842 Removed deprecated Scan(byte[], byte[]) from Scan

Lgtm. Waiting for the QA

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
3m 44s
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 18 new or modified test files.

_ master Compile Tests _

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

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

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

+1 :green_heart:
checkstyle
3m 29s
master passed

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

+1 :green_heart:
javadoc
2m 39s
master passed

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

+1 :green_heart:
findbugs
9m 56s
master passed

_ Patch Compile Tests _

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

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

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

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

-1 :x:
checkstyle
1m 29s
hbase-server: The patch generated 3 new + 454 unchanged - 3 fixed = 457 total (was 457)

+1 :green_heart:
rubocop
0m  3s
There were no new rubocop issues.

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

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

+1 :green_heart:
hadoopcheck
17m 29s
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2.

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

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

_ Other Tests _

+1 :green_heart:
unit
0m 55s
hbase-client in the patch passed.

-1 :x:
unit
5m 51s
hbase-server in the patch failed.

+1 :green_heart:
unit
9m  7s
hbase-mapreduce in the patch passed.

+1 :green_heart:
unit
2m 15s
hbase-thrift in the patch passed.

+1 :green_heart:
unit
7m 28s
hbase-shell in the patch passed.

-1 :x:
unit
3m 31s
hbase-endpoint in the patch failed.

+1 :green_heart:
unit
3m 17s
hbase-rest in the patch passed.

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

127m 43s

Reason
Tests

Failed junit tests
hadoop.hbase.regionserver.TestScanWithBloomError

hadoop.hbase.coprocessor.TestRowProcessorEndpoint

Subsystem
Report/Notes

Docker
Client=19.03.6 Server=19.03.6 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/1/artifact/out/Dockerfile

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

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

uname
Linux 6d3e1d6994c4 4.15.0-74-generic #84-Ubuntu SMP Thu Dec 19 08:06:28 UTC 2019 x86_64 GNU/Linux

Build tool
maven

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

git revision
master / fe0d49bc52

Default Java
1.8.0_181

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

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

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/1/artifact/out/patch-unit-hbase-endpoint.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/1/testReport/

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

modules
C: hbase-client hbase-server hbase-mapreduce hbase-thrift hbase-shell hbase-endpoint hbase-rest U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/1/console

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) findbugs=3.1.11 rubocop=0.80.0

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 31s
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 18 new or modified test files.

_ master Compile Tests _

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

+1 :green_heart:
mvninstall
5m 17s
master passed

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

+1 :green_heart:
checkstyle
3m 32s
master passed

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

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

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

+1 :green_heart:
findbugs
10m 10s
master passed

_ Patch Compile Tests _

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

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

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

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

+1 :green_heart:
checkstyle
0m 29s
The patch passed checkstyle in hbase-client

+1 :green_heart:
checkstyle
1m 17s
hbase-server: The patch generated 0 new + 374 unchanged - 83 fixed = 374 total (was 457)

+1 :green_heart:
checkstyle
0m 19s
The patch passed checkstyle in hbase-mapreduce

+1 :green_heart:
checkstyle
0m 39s
The patch passed checkstyle in hbase-thrift

+1 :green_heart:
checkstyle
0m 13s
The patch passed checkstyle in hbase-shell

+1 :green_heart:
checkstyle
0m 15s
The patch passed checkstyle in hbase-endpoint

+1 :green_heart:
checkstyle
0m 17s
The patch passed checkstyle in hbase-rest

+1 :green_heart:
rubocop
0m  3s
There were no new rubocop issues.

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

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

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

+1 :green_heart:
javadoc
2m 45s
the patch passed

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

_ Other Tests _

+1 :green_heart:
unit
0m 54s
hbase-client in the patch passed.

-1 :x:
unit
4m 24s
hbase-server in the patch failed.

+1 :green_heart:
unit
8m 21s
hbase-mapreduce in the patch passed.

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

+1 :green_heart:
unit
7m  0s
hbase-shell in the patch passed.

-1 :x:
unit
2m 53s
hbase-endpoint in the patch failed.

+1 :green_heart:
unit
2m 54s
hbase-rest in the patch passed.

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

116m  0s

Reason
Tests

Failed junit tests
hadoop.hbase.regionserver.TestScanWithBloomError

hadoop.hbase.coprocessor.TestRowProcessorEndpoint

Subsystem
Report/Notes

Docker
Client=19.03.6 Server=19.03.6 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/2/artifact/out/Dockerfile

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

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

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

Build tool
maven

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

git revision
master / fe0d49bc52

Default Java
1.8.0_181

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/2/artifact/out/patch-unit-hbase-server.txt

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/2/artifact/out/patch-unit-hbase-endpoint.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/2/testReport/

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

modules
C: hbase-client hbase-server hbase-mapreduce hbase-thrift hbase-shell hbase-endpoint hbase-rest U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/2/console

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) findbugs=3.1.11 rubocop=0.80.0

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

This message was automatically generated.

Latest test failures were related. Updated the patch to include a fix.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 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 18 new or modified test files.

_ master Compile Tests _

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

+1 :green_heart:
mvninstall
5m 14s
master passed

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

+1 :green_heart:
checkstyle
3m 33s
master passed

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

+1 :green_heart:
javadoc
2m 45s
master passed

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

+1 :green_heart:
findbugs
9m 18s
master passed

_ Patch Compile Tests _

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

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

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

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

+1 :green_heart:
checkstyle
0m 31s
The patch passed checkstyle in hbase-client

+1 :green_heart:
checkstyle
1m 17s
hbase-server: The patch generated 0 new + 374 unchanged - 83 fixed = 374 total (was 457)

+1 :green_heart:
checkstyle
0m 20s
The patch passed checkstyle in hbase-mapreduce

+1 :green_heart:
checkstyle
0m 39s
The patch passed checkstyle in hbase-thrift

+1 :green_heart:
checkstyle
0m 13s
The patch passed checkstyle in hbase-shell

+1 :green_heart:
checkstyle
0m 14s
The patch passed checkstyle in hbase-endpoint

+1 :green_heart:
checkstyle
0m 17s
The patch passed checkstyle in hbase-rest

+1 :green_heart:
rubocop
0m  3s
There were no new rubocop issues.

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

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

+1 :green_heart:
hadoopcheck
16m 38s
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2.

+1 :green_heart:
javadoc
2m 46s
the patch passed

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

_ Other Tests _

+1 :green_heart:
unit
0m 53s
hbase-client in the patch passed.

-1 :x:
unit
77m 22s
hbase-server in the patch failed.

-1 :x:
unit
9m 50s
hbase-mapreduce in the patch failed.

+1 :green_heart:
unit
2m 35s
hbase-thrift in the patch passed.

+1 :green_heart:
unit
7m 21s
hbase-shell in the patch passed.

+1 :green_heart:
unit
3m 14s
hbase-endpoint in the patch passed.

+1 :green_heart:
unit
3m 18s
hbase-rest in the patch passed.

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

193m 54s

Reason
Tests

Failed junit tests
hadoop.hbase.replication.TestReplicationKillSlaveRS

hadoop.hbase.regionserver.TestHStoreFile

hadoop.hbase.replication.TestReplicationSyncUpTool

hadoop.hbase.replication.multiwal.TestReplicationKillMasterRSCompressedWithMultipleAsyncWAL

hadoop.hbase.client.TestAsyncTableGetMultiThreaded

hadoop.hbase.replication.TestSerialReplicationFailover

hadoop.hbase.replication.TestReplicationEmptyWALRecovery

hadoop.hbase.replication.TestSyncReplicationMoreLogsInLocalCopyToRemote

hadoop.hbase.snapshot.TestExportSnapshotV2NoCluster

hadoop.hbase.snapshot.TestExportSnapshotV1NoCluster

Subsystem
Report/Notes

Docker
Client=19.03.6 Server=19.03.6 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/3/artifact/out/Dockerfile

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

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

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

Build tool
maven

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

git revision
master / fe0d49bc52

Default Java
1.8.0_181

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/3/artifact/out/patch-unit-hbase-server.txt

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/3/artifact/out/patch-unit-hbase-mapreduce.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/3/testReport/

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

modules
C: hbase-client hbase-server hbase-mapreduce hbase-thrift hbase-shell hbase-endpoint hbase-rest U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/3/console

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) findbugs=3.1.11 rubocop=0.79.0

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 30s
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 18 new or modified test files.

_ master Compile Tests _

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

+1 :green_heart:
mvninstall
5m 17s
master passed

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

+1 :green_heart:
checkstyle
3m 35s
master passed

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

+1 :green_heart:
javadoc
2m 48s
master passed

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

+1 :green_heart:
findbugs
9m  5s
master passed

_ Patch Compile Tests _

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

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

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

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

+1 :green_heart:
checkstyle
0m 31s
The patch passed checkstyle in hbase-client

+1 :green_heart:
checkstyle
1m 17s
hbase-server: The patch generated 0 new + 374 unchanged - 83 fixed = 374 total (was 457)

+1 :green_heart:
checkstyle
0m 20s
The patch passed checkstyle in hbase-mapreduce

+1 :green_heart:
checkstyle
0m 38s
The patch passed checkstyle in hbase-thrift

+1 :green_heart:
checkstyle
0m 13s
The patch passed checkstyle in hbase-shell

+1 :green_heart:
checkstyle
0m 15s
The patch passed checkstyle in hbase-endpoint

+1 :green_heart:
checkstyle
0m 17s
The patch passed checkstyle in hbase-rest

+1 :green_heart:
rubocop
0m  3s
There were no new rubocop issues.

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

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

+1 :green_heart:
hadoopcheck
15m 55s
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2.

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

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

_ Other Tests _

+1 :green_heart:
unit
0m 55s
hbase-client in the patch passed.

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

+1 :green_heart:
unit
8m 36s
hbase-mapreduce in the patch passed.

+1 :green_heart:
unit
2m 30s
hbase-thrift in the patch passed.

+1 :green_heart:
unit
7m 19s
hbase-shell in the patch passed.

+1 :green_heart:
unit
3m  9s
hbase-endpoint in the patch passed.

+1 :green_heart:
unit
3m  7s
hbase-rest in the patch passed.

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

176m 11s

Subsystem
Report/Notes

Docker
Client=19.03.6 Server=19.03.6 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/4/artifact/out/Dockerfile

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

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

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

Build tool
maven

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

git revision
master / 400b7ce954

Default Java
1.8.0_181

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/4/testReport/

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

modules
C: hbase-client hbase-server hbase-mapreduce hbase-thrift hbase-shell hbase-endpoint hbase-rest U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/4/console

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) findbugs=3.1.11 rubocop=0.80.0

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  9s
Docker mode activated.

_ Prechecks _

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

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

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

_ master Compile Tests _

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

+1 :green_heart:
mvninstall
5m 48s
master passed

+1 :green_heart:
checkstyle
3m 28s
master passed

-1 :x:
spotbugs
2m  7s
hbase-server in master has 1 extant spotbugs warnings.

-0 :warning:
patch
2m 13s
Used diff version of patch file. Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

_ Patch Compile Tests _

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

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

+1 :green_heart:
checkstyle
0m 31s
The patch passed checkstyle in hbase-client

+1 :green_heart:
checkstyle
1m 21s
hbase-server: The patch generated 0 new + 365 unchanged - 83 fixed = 365 total (was 448)

+1 :green_heart:
checkstyle
0m 18s
The patch passed checkstyle in hbase-mapreduce

+1 :green_heart:
checkstyle
0m 41s
The patch passed checkstyle in hbase-thrift

+1 :green_heart:
checkstyle
0m 10s
The patch passed checkstyle in hbase-shell

+1 :green_heart:
checkstyle
0m 12s
The patch passed checkstyle in hbase-endpoint

+1 :green_heart:
checkstyle
0m 20s
The patch passed checkstyle in hbase-rest

+1 :green_heart:
rubocop
0m  7s
There were no new rubocop issues.

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

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

+1 :green_heart:
spotbugs
7m 48s
the patch passed

_ Other Tests _

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

62m 39s

Subsystem
Report/Notes

Docker
Client=19.03.8 Server=19.03.8 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/5/artifact/yetus-general-check/output/Dockerfile

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

Optional Tests
dupname asflicense spotbugs hadoopcheck hbaseanti checkstyle rubocop

uname
Linux 107e6064c567 4.15.0-74-generic #84-Ubuntu SMP Thu Dec 19 08:06:28 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / b9e74e0b0a

spotbugs
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/5/artifact/yetus-general-check/output/branch-spotbugs-hbase-server-warnings.html

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

modules
C: hbase-client hbase-server hbase-mapreduce hbase-thrift hbase-shell hbase-endpoint hbase-rest U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/5/console

versions
git=2.17.1 maven=2018-06-17T18:33:14Z) spotbugs=3.1.12 rubocop=0.80.0

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 42s
Docker mode activated.

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

_ Prechecks _

_ master Compile Tests _

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

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

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

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

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

-0 :warning:
patch
8m 52s
Used diff version of patch file. Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

_ Patch Compile Tests _

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

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

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

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

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

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

_ Other Tests _

+1 :green_heart:
unit
0m 56s
hbase-client in the patch passed.

-1 :x:
unit
63m 54s
hbase-server in the patch failed.

-1 :x:
unit
29m 36s
hbase-mapreduce in the patch failed.

+1 :green_heart:
unit
2m 45s
hbase-thrift in the patch passed.

-1 :x:
unit
7m 41s
hbase-shell in the patch failed.

+1 :green_heart:
unit
3m 36s
hbase-endpoint in the patch passed.

+1 :green_heart:
unit
3m 17s
hbase-rest in the patch passed.

151m 27s

Subsystem
Report/Notes

Docker
Client=19.03.8 Server=19.03.8 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/5/artifact/yetus-jdk8-hadoop2-check/output/Dockerfile

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux cae4b6812f6e 4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / b9e74e0b0a

Default Java
1.8.0_232

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/5/artifact/yetus-jdk8-hadoop2-check/output/patch-unit-hbase-server.txt

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/5/artifact/yetus-jdk8-hadoop2-check/output/patch-unit-hbase-mapreduce.txt

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/5/artifact/yetus-jdk8-hadoop2-check/output/patch-unit-hbase-shell.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/5/testReport/

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

modules
C: hbase-client hbase-server hbase-mapreduce hbase-thrift hbase-shell hbase-endpoint hbase-rest U: .

 Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

_ Patch Compile Tests _

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

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

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

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

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

-0 :warning:
javadoc
0m 39s
hbase-client in the patch failed.

-0 :warning:
javadoc
0m 58s
hbase-server in the patch failed.

-0 :warning:
javadoc
0m 31s
hbase-mapreduce in the patch failed.

-0 :warning:
javadoc
1m 16s
hbase-thrift in the patch failed.

-0 :warning:
javadoc
0m 33s
hbase-rest in the patch failed.

_ Other Tests _

+1 :green_heart:
unit
1m 34s
hbase-client in the patch passed.

-0 :warning:
unit
87m 13s
hbase-server in the patch failed.

-0 :warning:
unit
9m  3s
hbase-mapreduce in the patch failed.

+1 :green_heart:
unit
2m 32s
hbase-thrift in the patch passed.

-0 :warning:
unit
7m 35s
hbase-shell in the patch failed.

+1 :green_heart:
unit
3m  2s
hbase-endpoint in the patch passed.

+1 :green_heart:
unit
3m  4s
hbase-rest in the patch passed.

174m 50s

Subsystem
Report/Notes

Docker
Client=19.03.8 Server=19.03.8 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/5/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 4b1e472accfd 4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / b9e74e0b0a

Default Java
2020-01-14

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/5/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-client.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/5/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-mapreduce.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/5/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-rest.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/5/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-server.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/5/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-thrift.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/5/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-client.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/5/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-server.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/5/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-mapreduce.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/5/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-thrift.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/5/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-rest.txt

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/5/artifact/yetus-jdk11-hadoop3-check/output/patch-unit-hbase-server.txt

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/5/artifact/yetus-jdk11-hadoop3-check/output/patch-unit-hbase-mapreduce.txt

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/5/artifact/yetus-jdk11-hadoop3-check/output/patch-unit-hbase-shell.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/5/testReport/

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

modules
C: hbase-client hbase-server hbase-mapreduce hbase-thrift hbase-shell hbase-endpoint hbase-rest U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/5/console

versions
git=2.17.1 maven=2018-06-17T18:33:14Z)

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

This message was automatically generated.

Merged latest master and fixed test failures. TestFromClientSideWithCoprocessor was related, the others not.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

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

_ Prechecks _

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

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

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

_ master Compile Tests _

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

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

+1 :green_heart:
checkstyle
3m 29s
master passed

-1 :x:
spotbugs
2m 10s
hbase-server in master has 1 extant spotbugs warnings.

-0 :warning:
patch
2m 16s
Used diff version of patch file. Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

_ Patch Compile Tests _

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

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

+1 :green_heart:
checkstyle
0m 30s
The patch passed checkstyle in hbase-client

+1 :green_heart:
checkstyle
1m 20s
hbase-server: The patch generated 0 new + 365 unchanged - 83 fixed = 365 total (was 448)

+1 :green_heart:
checkstyle
0m 18s
The patch passed checkstyle in hbase-mapreduce

+1 :green_heart:
checkstyle
0m 44s
The patch passed checkstyle in hbase-thrift

+1 :green_heart:
checkstyle
0m 10s
The patch passed checkstyle in hbase-shell

+1 :green_heart:
checkstyle
0m 13s
The patch passed checkstyle in hbase-endpoint

+1 :green_heart:
checkstyle
0m 16s
The patch passed checkstyle in hbase-rest

-0 :warning:
rubocop
0m  6s
The patch generated 2 new + 109 unchanged - 2 fixed = 111 total (was 111)

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

+1 :green_heart:
hadoopcheck
11m 59s
Patch does not cause any errors with Hadoop 2.10.0 or 3.1.2.

+1 :green_heart:
spotbugs
7m 49s
the patch passed

_ Other Tests _

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

57m 44s

Subsystem
Report/Notes

Docker
Client=19.03.8 Server=19.03.8 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/6/artifact/yetus-general-check/output/Dockerfile

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

Optional Tests
dupname asflicense spotbugs hadoopcheck hbaseanti checkstyle rubocop

uname
Linux c519b43be5e8 4.15.0-74-generic #84-Ubuntu SMP Thu Dec 19 08:06:28 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / b53fa3c51f

spotbugs
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/6/artifact/yetus-general-check/output/branch-spotbugs-hbase-server-warnings.html

rubocop
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/6/artifact/yetus-general-check/output/diff-patch-rubocop.txt

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

modules
C: hbase-client hbase-server hbase-mapreduce hbase-thrift hbase-shell hbase-endpoint hbase-rest U: .

 Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

_ Patch Compile Tests _

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

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

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

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

-1 :x:
shadedjars
0m  9s
patch has 7 errors when building our shaded downstream artifacts.

-0 :warning:
javadoc
0m 25s
hbase-client in the patch failed.

-0 :warning:
javadoc
0m 41s
hbase-server in the patch failed.

-0 :warning:
javadoc
0m 19s
hbase-mapreduce in the patch failed.

-0 :warning:
javadoc
0m 57s
hbase-thrift in the patch failed.

-0 :warning:
javadoc
0m 23s
hbase-rest in the patch failed.

_ Other Tests _

+1 :green_heart:
unit
1m  5s
hbase-client in the patch passed.

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

+1 :green_heart:
unit
7m 59s
hbase-mapreduce in the patch passed.

+1 :green_heart:
unit
2m 30s
hbase-thrift in the patch passed.

+1 :green_heart:
unit
3m 40s
hbase-shell in the patch passed.

+1 :green_heart:
unit
3m 20s
hbase-endpoint in the patch passed.

+1 :green_heart:
unit
2m 57s
hbase-rest in the patch passed.

152m 53s

Subsystem
Report/Notes

Docker
Client=19.03.8 Server=19.03.8 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/6/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 73d99d04f6d8 4.15.0-74-generic #84-Ubuntu SMP Thu Dec 19 08:06:28 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / b53fa3c51f

Default Java
2020-01-14

shadedjars
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/6/artifact/yetus-jdk11-hadoop3-check/output/branch-shadedjars.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/6/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-client.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/6/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-mapreduce.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/6/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-rest.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/6/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-server.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/6/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-thrift.txt

shadedjars
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/6/artifact/yetus-jdk11-hadoop3-check/output/patch-shadedjars.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/6/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-client.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/6/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-server.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/6/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-mapreduce.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/6/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-thrift.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/6/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-rest.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/6/testReport/

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

modules
C: hbase-client hbase-server hbase-mapreduce hbase-thrift hbase-shell hbase-endpoint hbase-rest U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/6/console

versions
git=2.17.1 maven=2018-06-17T18:33:14Z)

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
8m 11s
Docker mode activated.

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

_ Prechecks _

_ master Compile Tests _

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

+1 :green_heart:
mvninstall
6m  5s
master passed

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

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

+1 :green_heart:
javadoc
2m 32s
master passed

-0 :warning:
patch
9m  1s
Used diff version of patch file. Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

_ Patch Compile Tests _

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

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

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

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

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

+1 :green_heart:
javadoc
2m 31s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
0m 55s
hbase-client in the patch passed.

+1 :green_heart:
unit
92m 14s
hbase-server in the patch passed.

+1 :green_heart:
unit
6m 50s
hbase-mapreduce in the patch passed.

+1 :green_heart:
unit
2m 32s
hbase-thrift in the patch passed.

+1 :green_heart:
unit
3m 34s
hbase-shell in the patch passed.

+1 :green_heart:
unit
3m 18s
hbase-endpoint in the patch passed.

+1 :green_heart:
unit
3m 33s
hbase-rest in the patch passed.

160m 16s

Subsystem
Report/Notes

Docker
Client=19.03.8 Server=19.03.8 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/6/artifact/yetus-jdk8-hadoop2-check/output/Dockerfile

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux a54ed9c695ef 4.15.0-74-generic #84-Ubuntu SMP Thu Dec 19 08:06:28 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / b53fa3c51f

Default Java
1.8.0_232

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/6/testReport/

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

modules
C: hbase-client hbase-server hbase-mapreduce hbase-thrift hbase-shell hbase-endpoint hbase-rest U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/6/console

versions
git=2.17.1 maven=2018-06-17T18:33:14Z)

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

This message was automatically generated.

Ok, I think this one is ready to get merged.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

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

-1 :x:
patch
0m  4s
https://github.com/apache/hbase/pull/1189 does not apply to master. Rebase required? Wrong Branch? See https://yetus.apache.org/documentation/in-progress/precommit-patchnames for help.

Subsystem
Report/Notes

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

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/7/console

versions
git=2.17.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  0s
Docker mode activated.

-1 :x:
patch
0m  3s
https://github.com/apache/hbase/pull/1189 does not apply to master. Rebase required? Wrong Branch? See https://yetus.apache.org/documentation/in-progress/precommit-patchnames for help.

Subsystem
Report/Notes

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

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/7/console

versions
git=2.17.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  0s
Docker mode activated.

-1 :x:
patch
0m  3s
https://github.com/apache/hbase/pull/1189 does not apply to master. Rebase required? Wrong Branch? See https://yetus.apache.org/documentation/in-progress/precommit-patchnames for help.

Subsystem
Report/Notes

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

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/7/console

versions
git=2.17.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  0s
Docker mode activated.

-1 :x:
patch
0m  3s
https://github.com/apache/hbase/pull/1189 does not apply to master. Rebase required? Wrong Branch? See https://yetus.apache.org/documentation/in-progress/precommit-patchnames for help.

Subsystem
Report/Notes

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

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/8/console

versions
git=2.17.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  0s
Docker mode activated.

-1 :x:
patch
0m  3s
https://github.com/apache/hbase/pull/1189 does not apply to master. Rebase required? Wrong Branch? See https://yetus.apache.org/documentation/in-progress/precommit-patchnames for help.

Subsystem
Report/Notes

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

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/8/console

versions
git=2.17.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  0s
Docker mode activated.

-1 :x:
patch
0m  3s
https://github.com/apache/hbase/pull/1189 does not apply to master. Rebase required? Wrong Branch? See https://yetus.apache.org/documentation/in-progress/precommit-patchnames for help.

Subsystem
Report/Notes

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

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/8/console

versions
git=2.17.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  0s
Docker mode activated.

-1 :x:
patch
0m  3s
https://github.com/apache/hbase/pull/1189 does not apply to master. Rebase required? Wrong Branch? See https://yetus.apache.org/documentation/in-progress/precommit-patchnames for help.

Subsystem
Report/Notes

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

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/9/console

versions
git=2.17.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  0s
Docker mode activated.

-1 :x:
patch
0m  4s
https://github.com/apache/hbase/pull/1189 does not apply to master. Rebase required? Wrong Branch? See https://yetus.apache.org/documentation/in-progress/precommit-patchnames for help.

Subsystem
Report/Notes

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

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/9/console

versions
git=2.17.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  0s
Docker mode activated.

-1 :x:
patch
0m  3s
https://github.com/apache/hbase/pull/1189 does not apply to master. Rebase required? Wrong Branch? See https://yetus.apache.org/documentation/in-progress/precommit-patchnames for help.

Subsystem
Report/Notes

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

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/9/console

versions
git=2.17.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 37s
Docker mode activated.

_ Prechecks _

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

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

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

_ master Compile Tests _

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

+1 :green_heart:
mvninstall
6m 55s
master passed

+1 :green_heart:
checkstyle
3m 55s
master passed

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

-0 :warning:
patch
2m 34s
Used diff version of patch file. Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

_ Patch Compile Tests _

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

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

+1 :green_heart:
checkstyle
0m 36s
The patch passed checkstyle in hbase-client

+1 :green_heart:
checkstyle
1m 29s
hbase-server: The patch generated 0 new + 365 unchanged - 83 fixed = 365 total (was 448)

+1 :green_heart:
checkstyle
0m 24s
The patch passed checkstyle in hbase-mapreduce

+1 :green_heart:
checkstyle
0m 50s
The patch passed checkstyle in hbase-thrift

+1 :green_heart:
checkstyle
0m 13s
The patch passed checkstyle in hbase-shell

+1 :green_heart:
checkstyle
0m 14s
The patch passed checkstyle in hbase-endpoint

+1 :green_heart:
checkstyle
0m 18s
The patch passed checkstyle in hbase-rest

-0 :warning:
rubocop
0m  8s
The patch generated 2 new + 109 unchanged - 2 fixed = 111 total (was 111)

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

+1 :green_heart:
hadoopcheck
12m 57s
Patch does not cause any errors with Hadoop 2.10.0 or 3.1.2.

+1 :green_heart:
spotbugs
8m 49s
the patch passed

_ Other Tests _

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

63m 59s

Subsystem
Report/Notes

Docker
Client=19.03.8 Server=19.03.8 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/10/artifact/yetus-general-check/output/Dockerfile

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

Optional Tests
dupname asflicense spotbugs hadoopcheck hbaseanti checkstyle rubocop

uname
Linux 46f071412ab6 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
dev-support/hbase-personality.sh

git revision
master / e5a8435b48

rubocop
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/10/artifact/yetus-general-check/output/diff-patch-rubocop.txt

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

modules
C: hbase-client hbase-server hbase-mapreduce hbase-thrift hbase-shell hbase-endpoint hbase-rest U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/10/console

versions
git=2.17.1 maven=2018-06-17T18:33:14Z) spotbugs=3.1.12 rubocop=0.80.0

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
1m 19s
Docker mode activated.

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

_ Prechecks _

_ master Compile Tests _

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

+1 :green_heart:
mvninstall
5m 55s
master passed

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

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

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

-0 :warning:
patch
8m 44s
Used diff version of patch file. Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

_ Patch Compile Tests _

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

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

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

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

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

+1 :green_heart:
javadoc
2m 26s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
0m 55s
hbase-client in the patch passed.

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

+1 :green_heart:
unit
11m  3s
hbase-mapreduce in the patch passed.

+1 :green_heart:
unit
2m 50s
hbase-thrift in the patch passed.

+1 :green_heart:
unit
7m 14s
hbase-shell in the patch passed.

+1 :green_heart:
unit
2m 54s
hbase-endpoint in the patch passed.

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

167m  3s

Subsystem
Report/Notes

Docker
Client=19.03.8 Server=19.03.8 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/10/artifact/yetus-jdk8-hadoop2-check/output/Dockerfile

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 2e20cdce1053 4.15.0-74-generic #84-Ubuntu SMP Thu Dec 19 08:06:28 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / e5a8435b48

Default Java
1.8.0_232

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/10/testReport/

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

modules
C: hbase-client hbase-server hbase-mapreduce hbase-thrift hbase-shell hbase-endpoint hbase-rest U: .

 Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

_ Patch Compile Tests _

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

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

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

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

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

-0 :warning:
javadoc
0m 25s
hbase-client in the patch failed.

-0 :warning:
javadoc
0m 40s
hbase-server in the patch failed.

-0 :warning:
javadoc
0m 19s
hbase-mapreduce in the patch failed.

-0 :warning:
javadoc
0m 59s
hbase-thrift in the patch failed.

-0 :warning:
javadoc
0m 19s
hbase-rest in the patch failed.

_ Other Tests _

+1 :green_heart:
unit
1m  8s
hbase-client in the patch passed.

+1 :green_heart:
unit
99m 28s
hbase-server in the patch passed.

+1 :green_heart:
unit
14m 48s
hbase-mapreduce in the patch passed.

+1 :green_heart:
unit
3m 26s
hbase-thrift in the patch passed.

+1 :green_heart:
unit
7m 15s
hbase-shell in the patch passed.

+1 :green_heart:
unit
3m  1s
hbase-endpoint in the patch passed.

+1 :green_heart:
unit
3m  3s
hbase-rest in the patch passed.

181m 50s

Subsystem
Report/Notes

Docker
Client=19.03.8 Server=19.03.8 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/10/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux b0c904ece0fc 4.15.0-74-generic #84-Ubuntu SMP Thu Dec 19 08:06:28 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / e5a8435b48

Default Java
2020-01-14

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/10/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-client.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/10/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-mapreduce.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/10/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-rest.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/10/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-server.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/10/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-thrift.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/10/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-client.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/10/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-server.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/10/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-mapreduce.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/10/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-thrift.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/10/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-rest.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/10/testReport/

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

modules
C: hbase-client hbase-server hbase-mapreduce hbase-thrift hbase-shell hbase-endpoint hbase-rest U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1189/10/console

versions
git=2.17.1 maven=2018-06-17T18:33:14Z)

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

This message was automatically generated.

Latest QA results look good


list function in controller renamed for backwards php compatibility

In the controller file the function was named "list" which is a reserved keyword in PHP. Only PHP7 made it possible to create functions with this name. For more details please visit: https://stackoverflow.com/a/6833077
After changing this function name to a different one now it is possible to use this module on servers with PHP5.6 (maybe older)

@ersoma great catch, thank you!