ACD-4137: Implemented code for ignoring test cases for fields starting with dollar and _key

@zahrasidhpuri-crest Won't we need to add tests for LOOKUP in constants.py as discussed?
Also for $1 and KEY scenario in fiction?

Yes it will be done.


PSP: embedded app scans for QR and shows project [4d]

[ ] startScanning
[ ] send request to record the scan (or scan=null to just get the project)
[ ] process the scan response to render the project page
[ ] click through to merchant list

now open/closed

Also support scanning via the 'scan' button in the sidebar, should open the embedded app with the correct context (that being the full url, I think)


Add the foundational code for Reconfiguration rules

What does this PR do and why?
Provide a description of what this PR does. Link to any relevant GitHub issues, Notion tasks or Discord discussions.
Screenshots or screen recordings
If applicable, provide screenshots or screen recordings to demonstrate the changes.
Acceptance checklist

[ ] I have evaluated the Approval Guidelines for this PR.
[ ] I have tested this PR in all supported browsers.
[ ] I have tested this PR in dark mode and light mode (if applicable).

Current dependencies on/for this PR:

main

PR #2131

PR #2132

PR #2133

PR #2134

PR #2135

PR #2136

PR #2137

PR #2138   👈

This comment was auto-generated by Graphite.

Graphite Merge Job
Current status: ⏳ Queued to merge
This pull request is currently queued to be merged as part of a stack.
This comment was auto-generated by Graphite.

Job Reference: 8MtB741cDgPulkwyaE02


Support a scratchpad for a jupyter notebook

Is there a way to have an interactive command line that is connected to a jupyter notebook? Not a python script divided up into "jupyter cells", which works fine, but a notebook. Running 'Jupyter : Create Interactive Window" creates a shell that doesn't see the variables in Jupyter Notebook's workspace. This functionality was available in plain Jupyter , run in a browser, using the "Scratch Pad" extension.
Thanks.

Thanks for the suggestion, I know that we've batted around the idea of a scratchpad extension a few times for VS Code. We'll put it in for consideration. Personally I think it would be an excellent addition.

Thank you. Are you aware of any workarounds?

Thank you. Are you aware of any workarounds?

Hi @mischki have you found any workarounds in the meantime? Really slows down my trial–and-error development process I became so used to when using the VSCode python debugger.

Thank you. Are you aware of any workarounds?

Hi @mischki have you found any workarounds in the meantime :)? Really slows down my trial–and-error development process I became so used to when using the VSCode python debugger.
Cheers, Phil

Hi Phil,
I'm still using Jupyter in Chrome and anxiously googling about this every week. There seems to be no interest among the developers.

@mischki
Cheers! Seems like I managed to got it working. (can use the Jupyter Notebook variables in the interactive window now. A bit of a process but imho worth it :D)
The process

Command + Shift + P
Jupyter: Create Interactive Window
Copy URL of Remote Jupyter Session
again: Command + Shift + P -> Jupyter: Specify local or remote Jupyter server for connections
Paste URL of Remote Jupyter Session
In the interactive window select the current session (remote)
That's it! The active variables from the Jupyter Notebook should now available in the interactive console

Hi.
Is your Jupyter Notebook opened within VSCode or in a browser? If in VSCode, how do you copy its url?
Thanks.

@mischki haha, that's a bit tricky indeed: I copy the entire block, paste it in the execution field and from there I can easily copy the URL

Sorry, I'm quite new to VSCode. How do you get to that window (first picture) from where you copy the URL? When I open a Jupyter notebook in VSCode I don't see a window with a URL like that. Thanks.

This one gets you to the interactive window. (Command - Shift - P (guess something similar when you're using Windows / Linux)) Hope that helps :)

I meant this one

I meant this one

When I start a Jupyter Interactive Window this is what I get

No URL anywhere. So I still don't know how to get the URL of the Notebook's kernel to paste into the interactive window.
What am I missing?
Thanks

Yes, I'm also really missing the console in Jupyterlab.  Here's a related vscode request too: #100061

@mischki Now it also happened to me - there was no URL shown anymore in the March 2022 version of VSCode - so I downgraded to the Feb version and it started working again 🤷🏽♂

@mischki Now it also happened to me - there was no URL shown anymore in the March 2022 version of VSCode - so I downgraded to the Feb version and it started working again 🤷🏽♂

I tested the approach using terminal and typing: jupyter notebook as suggested here. I can confirm that this works as well and ther's no need to downgrade or change VS Code versions.
The process is similar:

Open terminal and type jupyter notebook in terminal and copy localhost (it will also open jupyter in browser by default but you don't need to keep running it).
Command + Shift + P
Specify Jupyter Server for Connections
Paste copied URL
Command + Shift + P
Open interactive window and select the remote kernel you specified earlier
Select the same remote kernel also in your jupyter session, i.e. local notebook so identical kernel is in interactive and local session. Now you should have output carried from one your jupyter notebook to your interactive window.

duplicate of https://github.com/microsoft/vscode-jupyter/issues/4573


Model View: Declarative table status column type

SQL Operations Studio Version:

Steps to Reproduce:

Closing older unfunded task work-items.


The plugin flutter_geocoder uses a deprecated version of the Android embedding.

This warning is given after updating to version Flutter 2.5

Check the new version of Universe: 1.1.1-null-safety
It should works with Flutter 2.5.0.

Tnks, it works perfectly!


update the workflow test

Codecov Report

Merging #3 (a018960) into main (617ce2b) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main       #3   +/-   ##
=======================================
  Coverage   84.03%   84.03%
=======================================
  Files          11       11
  Lines         595      595
=======================================
  Hits          500      500
  Misses         95       95

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Add "Boosty" logotype icon

Describe the requested icon
This is a pretty popular service for accepting donations. Analog Buy Me a Coffee
Screenshots
Bandbook - https://boosty.to/app/brand

We are scaling back on support for most brand icons, though I could see a potential argument for including tips/payments processors. Please #392 for more info on our general stance on brands. In the mean time, we recommend you use official brand assets from that company.


Add non-production notice

Add notice indicating that protocol-next branch is work in progress and not production quality

Add notice indicating that protocol-next branch is work in progress and not production quality

Signed-off-by line is missing.

Closing due to lack of sign-off. Will resubmit.


k8s journey: Review existing AWS S3 Broker for viability for Redis/ES

As part of this journey we need to find a new home for a broker to run Redis/ES service instances.  This ticket is to review the existing AWS S3 broker - https://github.com/cloudfoundry-community/s3-broker to see if it's a viable candidate for the task.
Acceptance Criteria

[x] Code base is still viable
[x] Code base is supportable by the current team (format, language, tools, etc)

Security considerations
Note any issues with the existing code base, if these issues impact the broker expansion, and form an implementation plan (and ticket) to resolve these issues even if this broker is not selected.
Implementation sketch

[x] Provide the recommendation to the team on if this broker is a candidate
[ ] Provide a pros/cons list on using this broker base to support AWS Redis/ES
[ ] Provide a rough plan and timeline to convert this broker for use with AWS Redis/ES

For the S3 Broker:
S3 broker uses the AWS golang APIs which is same as the RDS Broker.
The main reason for using RDS Broker to deploy services over S3 broker is due that S3 broker seems to be more customized to work with S3 only. This makes the RDS Broker a better candidate to be able to support other services.


changed the color

@smehrvar nice color changes. Great work!

@smehrvar I've deleted the branch for you


Validate Issue Index before querying DB

GetIssueByIndex() would ignore the index if invalid value is passed (thus parsed as 0), and continue to return first issue for the repo.
fixes #16405
We alternatively could return a 404, is that cleaner?

404 would be most correct imho


Poll -  unexpected behavior

Hi
I implemented a small test checking for timeouts
https://github.com/frehberg/mio/commit/ea90166c5a4fc2be4009258e4d628b09d119d76d
In line 248 of that patch the assertion fails. The queue is empty, and I would expect the Poll::poll() to block for 300msecs timeout, but the poll() returns immediatly.
Seems to be an issue with the state of the readyness-queue, prepare_sleep()  forcing timeout to 0.
I analyzed the code and added some comments
https://github.com/frehberg/mio/commit/1ddf9a825873bd7f30ff87f347142fdc91e02d0f
Is this something anybody is working at? Otherwise I would try to create a patch.

Generally speaking, Poll::poll can wakeup for any reason. That said, minimizing the wakeups is good.
Could you provide a high level explanation of what you think the issue is?

FIXME just used by consumer, no need to be marker-node

I'm not sure what this means.

FIXME, missing guard, must not release_node of closed-marker and sleep-marker

It is not possible to get a closed_marker or sleep_marker at that point. That code path is only hit when a closed_marker has been observed, so we cannot be enqueuing it again. sleep_marker is never enqueued.
This should be a comment.

FIXME use while instead of if to skip marker-sequence

Not sure why you think it should be a while. The markers are there to prevent iterating further.

FIXME, closed-marker should be handled like hard end!

Not sure what this means specifically.

FIXME, this is no inconsistency, just concurrent assignment of head, so tail->next having been modified. For consistency reasons exit and rerun!

Not sure what you mean here. the "inconsistent" terminology is what other impls of the mpsc queue have used. It just means "try again later".

First, I really admire the code of mio, it provides a very important feature, merging system events and custom events into a single event-queue. I think this is the central module to avoid fragmentation of all the network-libraries of Rust.
Generally speaking, my feeling is that current implementation is using way too many markers in the queue-logic, causing too many possible combinations/sequences.
Now I understand the code much better than I did when I added the first FIXME-comments, but still I would prefer to refactor the code reducing  the number of markers to two (including the closed-marker), simplifying the state machine and reasoning concerning emptiness and sleeping.
Regarding the amount of markers and the if/while discussion in  the function dequeue, here in some situations the dequeue might dequeue another marker and return as event (AFAICS) After skipping one marker, one should check if the next node might be one more marker. (reducing amount of markers to 1+1 would simplify the reasoning here)
In addition,  the function prepare_for_sleep is performing 'strange' condition checks reasoning about emptiness, and in line https://github.com/carllerche/mio/blob/split-poll-and-register/src/poll.rs#L2041  it is assigning  sleep_marker.next  to null, although the sleep_marker might be enqueued that moment (?!), interrrupting the queue (AFAICS). Maybe, can you explain, why this it is safe to assign sleep_marker.next here?
And if system-events occur with high frequency and the Poll::poll-parameter of type sys::Events has little capacity, the custom events queue may be starved (Events-list is filled with system-events and no capacity is remaining for pending custom events)
With your help and support, I would like to put some effort into the code with the objectives

to simplify the logics/reasoning
dealing with system-customer events in a fair manner (eg round robin)
a way to balance system and custom events (or being able to tell quotient)

From reading the linked code this is about the custom readiness queue, which is gone, well sort of it's still used on Windows, but that needs to be rewritten, so I'm going to close this. @frehberg if anything still needs to be done for this please reopen.


Add support for Towncrier and CHANGELOG generation.

In this PR we will add support for Towncrier (https://towncrier.readthedocs.io/en/stable/tutorial.html).

Closes #7


mmtf optimization issue

Writing a mmtf file of a big molecule is taking a lot of time abnormally.
On line 593 of src/formats/MMTF.cpp there is the line :
auto positions = frame.positions();
This affectation make a copy of the whole position vector instead of just got a reference.
Because this affectation is called for every residue, it dramatically slow down the writing process.
Changing it to
const auto& positions = frame.positions();
will use a reference assignment and correct the optimization issue.

Good catch! Thanks for the PR. I'll merge once CI is happy.

Let me know if you need this in a release! As far as I know, you are building VTX using your own fork of chemfiles, right?

Indeed, we already made this modification in our fork, so we don't need a special release for it, thank you!


A collection of issues while testing react-shortcuts

Everything here was tested on a Mac - and specifically, my Macbook Pro (non-touchbar) keyboard. It is possible behaviour will be different on a Windows or Linux machine.

[ ] Fn key does not register on my Mac (there is no event).
[ ] Since holding Shift changes a key to its uppercase variant (a becomes A), holding Shift and using lowercase ordered keys will not work.

[ ] Should we automatically convert characters to uppercase when Shift is used in a held array?
[ ] Or just cover this in the documentation?

[ ] Likewise, using the Alt key also modifies the original key (a becomes å), meaning a held Alt key won't match on anything available within the AlphabetKey type.
[ ] Interestingly, CapsLock as a held key only works in one scenario:

Using lowercase ordered keys
Begin with CapsLock off, hold key, press ordered keys = nothing
Begin with CapsLock on, hold key, press ordered keys = nothing
Using uppercase ordered keys
Begin with CapsLock off, hold key, press ordered keys = onMatch
Begin with CapsLock on, hold key, press ordered keys = nothing

cc/ @TheMallen @9at8

These are really nice findings!

Fn Key: This does not generate events as defined in the spec. We should remove this type, and others which are not detected 👍
Shift changing a -> A: I'm not too opinionated about this, but maybe we should convert lowercase to uppercase when we see a Shift in the modifiers. Whatever we do, we should clearly cover this in documentation though!
Not sure what to do about this 🤔 We can use event.code but it has it's own problems
CapsLock only works as held if the LED is green, as mentioned here

To give some remarks of a library user:
I just started with implementing some shortcuts and of course used "Shift" and lower case "a". Therefore I would love to be able to use "Shift" + "a" :-)
Another bug I found in my first test is if you have two shortcuts, one with only "a" and one with "Control" + "a". The one with "a" will always fire. At least yy expectation was that only the exact matches (with correct modifier keys) would fire.

@9at8  responses make a lot of sense, from chatting with him it sounds like he has some ideas for fixes for this stuff.


add array sortBy

Can I raise a PR for this? Or someone is working on it.

Feel free, no one is working on it.

Hey @kellyselden I wanna raise a pr for this, I wanna know a thing the sortBy should support asc and desc
if yes we can make use of current sort implementation correct?
I guess we are just doing sugar coat on the sort
let me know your thoughts on this
thanks

@kellyselden pong can you please review this, as I am in need of this implementation


Cast the call to objc_msgSend to the correct type.

Apparently, the last update to LLVM made it necesary to cast objc_msgSend to the desired type before using it.  This is causing NUI to fail to compile in the latest beta version of CocoaPods with XCode 6.
see: https://github.com/CocoaPods/CocoaPods/issues/3060

Covered by https://github.com/tombenner/nui/commit/529ed3eb782ef0b366510484d44d26538d10194a


GH-29746: [C++][Python] Approximate count distinct kernel

This patch provides "hll", an abbreviation for HyperLogLog, which can approximately count the number of distinct elements in a stream (or set of streams) with less memory than exact count distinct.
To do this, we pull in Apache DataSketches - a vendored version, as the most recent released version has some issues that casue our CI to fail.

What changes are included in this PR?
Changes to the cpp and python directories, as well as a full copy of https://github.com/apache/datasketches-cpp

Are these changes tested?
Yes

Are there any user-facing changes?
Yes - the addition of the hll function. This PR contains an update to the docs.

Closes: #29746

Thanks for the PR, sounds useful
. I personally am not a fan of vendoring entire repos if there is no need for it. In this case you seem to know a specific rev that works, so I would prefer to get the repo via FetchContent (as we are bumping cmake to 3.16 for 12.0.0)/EP and use the provided cmake code & config to integrate it into the build process.
But I am no cpp maintainer so I will defer to other opinions.

I agree with @assignUser .  Plus, new repos bring in the question of code size, security, etc.  Probably we will also want a new ARROW_WITH_DATASKETCHES cmake option that controls inclusion (and if not included we just don't get those kernels and that's ok). That being said, the datasketches project looks pretty neat.  Do you have much experience with it?  Do you know if there would be other kernels beyond hll that are available?

Alternatively, maybe it's time to start pioneering the ability to write an extension that adds new compute functions?  E.g. DuckDb is heading in this direction (https://duckdb.org/docs/extensions/overview.html) and it seems like it would be a way to help keep the compute kernels more maintainable (both kernel maintainers not wanting to be affected by engine changes and vice versa).

That being said, the datasketches project looks pretty neat. Do you have much experience with it? Do you know if there would be other kernels beyond hll that are available?

There are other useful kernels, including frequent items / heavy hitters, reservoir sampling, quantiles for non-numeric entities, and exterme-value quantiles (like p99.9).
https://datasketches.apache.org/docs/Architecture/MajorSketchFamilies.html


Questions about performance improvement in Open LLM leaderboard

Hi,
First of all, thank you for sharing your wonderful work!
I was searching for efficient ways of mining instructions used in instruction-tuning LLMs.
While reading the manuscript and investigating your provided open-sourced 6k & 10k datasets,
I could not intuitively understand why the SFT (6k) +DPO (10k) training method increases the performance of
the multi-choice question answering tasks such as ARC-challenge and MMLU?
In the dataset, the instances are composed of conversations between humans and GPT which don't have any clue about solving multi-choice QA problems.
Do you have any ideas why it worked?

Hi, thanks for your interest!
This question is indeed interesting. We have a couple of speculations that might shed some light:

Our top-performing model, trained using SFT (6k) combined with DPO (10k), originates from an intermediate SFT checkpoint. This checkpoint serves as the basis for further DPO training. Our hypothesis is that an overly optimized SFT might impair the inherent capabilities of LLMs. Therefore, utilizing a sub-optimal SFT checkpoint, followed by DPO training, which is specifically designed for alignment, appears to enhance performance on both academic benchmarks like the OpenLLM benchmark and alignment capabilities. This finding can also be found on Zephyr [1, 2].

It's observed that some questions incorrectly answered by the models can be rectified through multiple sampling attempts, employing strategies like majority voting or re-ranking. This indicates that the model has the potential to answer correctly but struggles to do so consistently. Reinforcement learning techniques such as DPO can adjust the model's output preferences, increasing the likelihood of producing the correct answer in a single attempt [3, Section 5].

References

[1] Zephyr: Direct Distillation of LM Alignment https://arxiv.org/abs/2310.16944
[2] Reinforcement Learning for Language Models https://gist.github.com/yoavg/6bff0fecd65950898eba1bb321cfbd81
[3] DeepSeekMath: Pushing the Limits of Mathematical Reasoning in Open Language Models https://arxiv.org/abs/2402.03300

Thanks for suggesting your insights and thoughts about my curious question!
I also agreed on the second point that the model has the potential to answer but not consistently to do it.
However, still have a hard time interpreting what DPO could enhance through preference alignment.

A potential explanation might be the presence of STEM-related samples within the UltraFeedback Datasets.


Consider releasing / tagging this repo

At this point we are deciding what to do with this repo; most likely I think that we'll archive it. I dont expect us to make future releases at this time and definitely not changing any particular process with it.


[2.0] disable persistent workers by default

What happened?
They are still somewhat buggy. I just closed several issues about them because we'd like to stop supporting our custom worker-aware tsc binary.
Instead, 2.0 will encourage users to use swc as the transpiler, and wait for #374 to get fast type-checks.
Version
2.0
How to reproduce
No response
Any other information?
No response

fixed in #401


Typo in Service error message

One of the server error messages has a typo. "An error occured". Should be occurred.
Acceptance Criteria

[ ]  occurred instead of occured

Steps for QA:

This typo will be addressed when I receive the translations for the string:
An error occurred.


Fix uorb again

Try to fix the original problem in a preper way;
Only take the synhcronizing semaphore in the callback thread; just take into account how many times the callback has been triggered but not handled.
This seems to work correctly in SITL: not tested on the hw so far
The original fix had a huge regression; the publisher thread was getting blocked by the semaphore. Now try the fix the same issue in the way that only place where the snchronizing semaphore is taken is actually the callback thread

SW reboot test for this PR passes consistently.

SW reboot test for this PR passes consistently.

Thanks, lets just give people time to also review this before merging!


Where can find '/path/to/trained/cvivit.pt'

as it suggests, you. need to train the civit sand save it to that path.


Rename ol.format.Format to ol.format.Feature

And remove a dead link

the PR/commit title here is a bit misleading. This PR updates the Readme (long overdue, by the looks of it :-)), it doesn't rename anything

Looks good.  Please merge.


btrbk: 0.29.1 -> 0.31.3

Motivation for this change
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

This seems to be a duplicate of https://github.com/NixOS/nixpkgs/pull/99303


Exclude indexing by regex foldername

I don't want Pigallery to index files related to some metadata.
For example if i have additional folder with metadata named something.meta I want to exclude *.meta from indexing. Same situation with files.
Wildcard is enough I think, it doesn't have to work like a regular regex.

duplicate of #192.
Lets continue there.


WARNING: Failed to activate VS environment: Could not parse vswhere.exe output

Failed to activate VS environment: Could not parse vswhere.exe output

You'll need to file a bug on the tool using vswhere, presumably meson. They may need to pass -utf8 to force UTF8 output; otherwise, the console code page may mess up their parsing.


Laravel 8 Support?

After upgrading to Laravel 8,
I am seeing this error: Undefined property: LaravelFCM\FCMManager::$app
on FCMManager.php(12):

Indeed, 7.x has $app and 8.x does not

Hi @exzachlyvv
Could you please let me know if my fix works fine for you ?
Using the dev-main version of this package (https://packagist.org/packages/code-lts/laravel-fcm#dev-main)

I've tested the dev-main version of your package, and it's working perfectly.
Thanks.


Save icon request

Hi guys,
I'm missing the rather basic save (floppy disk) icon. Is there a reason this was not added and if not, could it perhaps be added?
Peter

Hey there!
Unfortunately, we are not currently planning to add the "floppy disk" icon to vaadin-icons.
<iron-icons> seems to contain an icon for this, called icons:save.
If you don't want to import the whole iron-icons iconset, you can create your own like this: https://jsfiddle.net/Saulis/b9upvp7c/

I currently use the (deprecated) Font awesome icon. Which is fine for now.
Thanks for the answer though!

Hi Peter! Thanks for asking. I’ll check with the author of the icons if he could draw that.
Personally, I think the floppy icon starts to be very outdated, and I would not use it anymore to indicate saving in modern apps. But I do understand that it might be a good fit in some situations, still.

I do agree Jouni, but what else is there? Most people know what it means even though they might not have ever seen a floppy before.

Right, it is kinda funny how we’ve made the association so strong even though many people have no idea what the icons represents :)
I would say that the tendency in modern apps is to move away from having any explicit save buttons, and any changes are saved in the background automatically. For the situations when you need an explicit save/submit button, I would make leave it without an icon.
Since you mentioned you’re using the deprecated FA icon, I assume you’re using Vaadin Framework 8, right? Just a small heads-up to @Saulis, that this icon library has more users than just Polymer devs ;) (and the <iron-icons> instructions don’t apply for Vaadin Framework).

Also, the author, @Jaska79, said basically the same as I did, that the floppy icon is such an old metaphor and we are not planning on adding that to our icon set.
So I think it’s best for you if you keep using FA for this need. If you don’t want to depend on the deprecated package, you can use this community add-on for Font Awesome: https://vaadin.com/directory#!addon/fontawesomelabel

I guess devs who keep using the floppy save icon actually are the reason for this strong association in the first place. So I think you are right. I too will drop using the icon.
Thanks for your input Jouni!

I don't think UI developpers should be forced by a framework to join the "mission" of deprecating floppy disk as a save icon. The most important thing for me is what USER wants to see, or how they can find the right button as fast as possible. In my case, most of our users don't want to confused by the cloud/hard drive/database icon. They mostly don't care, but simply wish a floppy disk icon that symbolizes "save, I don't care how".

Exactly, I am very surprised that there is no save icon....

To make it easier to use your own icons in a Vaadin app, there’s an icon set generator in the docs (currently in preview), which makes it easier to incorporate your own icons in an app. You can then upload the Font Awesome floppy-disk icon there.


PHOENIX-6180 Investigate flaky tests in Phoenix Connectors

start three node minicluster in BaseHivePhoenixStoreIT

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

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

_ Prechecks _

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

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

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

-1 :x:
test4tests
0m  0s
The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch.

_ Patch Compile Tests _

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

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

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

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

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

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

+1 :green_heart:
spotbugs
1m 45s
the patch passed

_ Other Tests _

-1 :x:
unit
41m 15s
phoenix-hive-base in the patch failed.

-1 :x:
asflicense
0m 10s
The patch generated 1 ASF License warnings.

70m 31s

Subsystem
Report/Notes

Docker
ClientAPI=1.40 ServerAPI=1.40 base: https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/1/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/phoenix-connectors/pull/39

Optional Tests
dupname asflicense javac javadoc unit spotbugs hbaseanti checkstyle compile

uname
Linux 1a021ad0aaaa 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/phoenix-connectors-personality.sh

git revision
master / 7a0f920

Default Java
Private Build-1.8.0_242-8u242-b08-0ubuntu3~16.04-b08

unit
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/1/artifact/yetus-general-check/output/patch-unit-phoenix-hive-base.txt

Test Results
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/1/testReport/

asflicense
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/1/artifact/yetus-general-check/output/patch-asflicense-problems.txt

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

modules
C: phoenix-hive-base U: phoenix-hive-base

Console output
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/1/console

versions
git=2.7.4 maven=3.3.9 spotbugs=4.1.3

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 26s
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 :x:
test4tests
0m  0s
The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch.

_ Patch Compile Tests _

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

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

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

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

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

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

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

_ Other Tests _

-1 :x:
unit
40m  5s
phoenix-hive-base in the patch failed.

-1 :x:
asflicense
0m 10s
The patch generated 1 ASF License warnings.

69m 16s

Subsystem
Report/Notes

Docker
ClientAPI=1.40 ServerAPI=1.40 base: https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/2/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/phoenix-connectors/pull/39

Optional Tests
dupname asflicense javac javadoc unit spotbugs hbaseanti checkstyle compile

uname
Linux d13f82906f26 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/phoenix-connectors-personality.sh

git revision
master / 7a0f920

Default Java
Private Build-1.8.0_242-8u242-b08-0ubuntu3~16.04-b08

unit
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/2/artifact/yetus-general-check/output/patch-unit-phoenix-hive-base.txt

Test Results
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/2/testReport/

asflicense
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/2/artifact/yetus-general-check/output/patch-asflicense-problems.txt

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

modules
C: phoenix-hive-base U: phoenix-hive-base

Console output
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/2/console

versions
git=2.7.4 maven=3.3.9 spotbugs=4.1.3

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m  4s
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 :x:
test4tests
0m  0s
The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ master Compile Tests _

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

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

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

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

+0 :ok:
spotbugs
1m 51s
phoenix-hive-base in master has 47 extant spotbugs warnings.

_ Patch Compile Tests _

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

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

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

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

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

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

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

_ Other Tests _

-1 :x:
unit
12m 27s
phoenix-hive-base in the patch failed.

-1 :x:
asflicense
0m  9s
The patch generated 7 ASF License warnings.

43m 45s

Reason
Tests

Failed junit tests
phoenix.hive.HiveTezIT

phoenix.hive.HiveMapReduceIT

Subsystem
Report/Notes

Docker
ClientAPI=1.40 ServerAPI=1.40 base: https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/3/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/phoenix-connectors/pull/39

Optional Tests
dupname asflicense javac javadoc unit spotbugs hbaseanti checkstyle compile

uname
Linux e5d64a9c725d 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/phoenix-connectors-personality.sh

git revision
master / 7a0f920

Default Java
Private Build-1.8.0_242-8u242-b08-0ubuntu3~16.04-b08

unit
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/3/artifact/yetus-general-check/output/patch-unit-phoenix-hive-base.txt

Test Results
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/3/testReport/

asflicense
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/3/artifact/yetus-general-check/output/patch-asflicense-problems.txt

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

modules
C: phoenix-hive-base U: phoenix-hive-base

Console output
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/3/console

versions
git=2.7.4 maven=3.3.9 spotbugs=4.1.3

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 28s
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 :x:
test4tests
0m  0s
The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ master Compile Tests _

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

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

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

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

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

+0 :ok:
spotbugs
1m 37s
phoenix-hive-base in master has 47 extant spotbugs warnings.

+0 :ok:
spotbugs
0m 53s
phoenix-hive-base/phoenix5-hive in master has 46 extant spotbugs warnings.

_ Patch Compile Tests _

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

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

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

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

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

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

+1 :green_heart:
xml
0m  3s
The patch has no ill-formed XML file.

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

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

_ Other Tests _

+1 :green_heart:
unit
36m 18s
phoenix5-hive in the patch passed.

+1 :green_heart:
unit
28m 11s
phoenix-hive-base in the patch passed.

-1 :x:
asflicense
0m 17s
The patch generated 42 ASF License warnings.

100m 11s

Subsystem
Report/Notes

Docker
ClientAPI=1.40 ServerAPI=1.40 base: https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/4/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/phoenix-connectors/pull/39

Optional Tests
dupname asflicense javac javadoc unit xml compile spotbugs hbaseanti checkstyle

uname
Linux fd8f4997bcd4 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/phoenix-connectors-personality.sh

git revision
master / 7a0f920

Default Java
Private Build-1.8.0_242-8u242-b08-0ubuntu3~16.04-b08

Test Results
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/4/testReport/

asflicense
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/4/artifact/yetus-general-check/output/patch-asflicense-problems.txt

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

modules
C: phoenix-hive-base/phoenix5-hive phoenix-hive-base U: phoenix-hive-base

Console output
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/4/console

versions
git=2.7.4 maven=3.3.9 spotbugs=4.1.3

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

This message was automatically generated.

The ASF licence check errors are mostly bogus, or will be addressed in a future patch.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 28s
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 :x:
test4tests
0m  0s
The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ master Compile Tests _

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

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

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

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

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

+0 :ok:
spotbugs
4m  1s
root in master has 116 extant spotbugs warnings.

+0 :ok:
spotbugs
1m 21s
phoenix-hive-base in master has 46 extant spotbugs warnings.

_ Patch Compile Tests _

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

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

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

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

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

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

+1 :green_heart:
xml
0m  3s
The patch has no ill-formed XML file.

+1 :green_heart:
javadoc
1m 17s
the patch passed

+1 :green_heart:
spotbugs
6m 56s
the patch passed

_ Other Tests _

-1 :x:
unit
58m 40s
root in the patch failed.

-1 :x:
asflicense
0m 23s
The patch generated 90 ASF License warnings.

103m  9s

Reason
Tests

Failed junit tests
phoenix.hive.HiveTezIT

phoenix.hive.HiveTezIT

Subsystem
Report/Notes

Docker
ClientAPI=1.40 ServerAPI=1.40 base: https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/5/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/phoenix-connectors/pull/39

Optional Tests
dupname asflicense javac javadoc unit xml compile spotbugs hbaseanti checkstyle

uname
Linux 725992e76d37 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/phoenix-connectors-personality.sh

git revision
master / 2cb900c

Default Java
Private Build-1.8.0_242-8u242-b08-0ubuntu3~16.04-b08

unit
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/5/artifact/yetus-general-check/output/patch-unit-root.txt

Test Results
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/5/testReport/

asflicense
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/5/artifact/yetus-general-check/output/patch-asflicense-problems.txt

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

modules
C: . phoenix-hive-base U: .

Console output
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/5/console

versions
git=2.7.4 maven=3.3.9 spotbugs=4.1.3

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 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 :x:
test4tests
0m  0s
The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ master Compile Tests _

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

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

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

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

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

+0 :ok:
spotbugs
4m  5s
root in master has 116 extant spotbugs warnings.

+0 :ok:
spotbugs
1m 17s
phoenix-hive-base in master has 46 extant spotbugs warnings.

_ Patch Compile Tests _

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

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

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

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

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

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

+1 :green_heart:
xml
0m  3s
The patch has no ill-formed XML file.

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

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

_ Other Tests _

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

-1 :x:
asflicense
0m 24s
The patch generated 90 ASF License warnings.

99m 33s

Reason
Tests

Failed junit tests
phoenix.hive.HiveTezIT

phoenix.hive.HiveTezIT

Subsystem
Report/Notes

Docker
ClientAPI=1.40 ServerAPI=1.40 base: https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/6/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/phoenix-connectors/pull/39

Optional Tests
dupname asflicense javac javadoc unit xml compile spotbugs hbaseanti checkstyle

uname
Linux 2ff0ebc30030 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/phoenix-connectors-personality.sh

git revision
master / 2cb900c

Default Java
Private Build-1.8.0_242-8u242-b08-0ubuntu3~16.04-b08

unit
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/6/artifact/yetus-general-check/output/patch-unit-root.txt

Test Results
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/6/testReport/

asflicense
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/6/artifact/yetus-general-check/output/patch-asflicense-problems.txt

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

modules
C: . phoenix-hive-base U: .

Console output
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/6/console

versions
git=2.7.4 maven=3.3.9 spotbugs=4.1.3

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

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

_ Prechecks _

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

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

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

-1 :x:
test4tests
0m  0s
The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ master Compile Tests _

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

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

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

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

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

+0 :ok:
spotbugs
5m 46s
root in master has 116 extant spotbugs warnings.

+0 :ok:
spotbugs
1m 45s
phoenix-hive-base in master has 46 extant spotbugs warnings.

+0 :ok:
spotbugs
1m  2s
phoenix-hive-base/phoenix5-hive in master has 45 extant spotbugs warnings.

_ Patch Compile Tests _

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

+1 :green_heart:
mvninstall
8m 42s
the patch passed

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

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

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

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

+1 :green_heart:
xml
0m  6s
The patch has no ill-formed XML file.

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

+1 :green_heart:
spotbugs
9m  5s
the patch passed

_ Other Tests _

-1 :x:
unit
76m 57s
root in the patch failed.

-1 :x:
asflicense
0m 32s
The patch generated 4 ASF License warnings.

134m 33s

Subsystem
Report/Notes

Docker
ClientAPI=1.40 ServerAPI=1.40 base: https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/7/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/phoenix-connectors/pull/39

Optional Tests
dupname asflicense javac javadoc unit xml compile spotbugs hbaseanti checkstyle

uname
Linux 35bd0fdc8252 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/phoenix-connectors-personality.sh

git revision
master / 2cb900c

Default Java
Private Build-1.8.0_242-8u242-b08-0ubuntu3~16.04-b08

whitespace
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/7/artifact/yetus-general-check/output/whitespace-eol.txt

unit
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/7/artifact/yetus-general-check/output/patch-unit-root.txt

Test Results
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/7/testReport/

asflicense
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/7/artifact/yetus-general-check/output/patch-asflicense-problems.txt

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

modules
C: phoenix-spark-base/phoenix5-spark phoenix-hive-base/phoenix5-hive . phoenix-hive-base U: .

Console output
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/7/console

versions
git=2.7.4 maven=3.3.9 spotbugs=4.1.3

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

This message was automatically generated.

The phoenix-hive connectors are passing now, it is not immediately apparent why the build fails.

(!) A patch to the testing environment has been detected.
Re-executing against the patched versions to perform further tests.
The console is at https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/8/console in case of problems.

: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 :x:
test4tests
0m  0s
The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch.

_ Patch Compile Tests _

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

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

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

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

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

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

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

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

+1 :green_heart:
xml
0m 10s
The patch has no ill-formed XML file.

-1 :x:
javadoc
0m  9s
phoenix4-connectors-assembly in the patch failed.

-1 :x:
javadoc
0m  6s
phoenix5-connectors-assembly in the patch failed.

-1 :x:
javadoc
0m 10s
phoenix-kafka-base in the patch failed.

-1 :x:
spotbugs
0m 26s
phoenix-kafka-base in the patch failed.

_ Other Tests _

-1 :x:
unit
0m  8s
root in the patch failed.

-1 :x:
asflicense
0m 57s
The patch generated 6 ASF License warnings.

48m 56s

Subsystem
Report/Notes

Docker
ClientAPI=1.40 ServerAPI=1.40 base: https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/8/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/phoenix-connectors/pull/39

Optional Tests
dupname asflicense shellcheck shelldocs javac javadoc unit xml compile spotbugs hbaseanti checkstyle

uname
Linux 537d9fd85046 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/phoenix-connectors-personality.sh

git revision
master / 2cb900c

Default Java
Private Build-1.8.0_242-8u242-b08-0ubuntu3~16.04-b08

javadoc
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/8/artifact/yetus-general-check/output/branch-javadoc-phoenix5-connectors-assembly.txt

javadoc
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/8/artifact/yetus-general-check/output/branch-javadoc-phoenix-kafka-base.txt

spotbugs
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/8/artifact/yetus-general-check/output/branch-spotbugs-phoenix-kafka-base.txt

whitespace
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/8/artifact/yetus-general-check/output/whitespace-eol.txt

javadoc
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/8/artifact/yetus-general-check/output/patch-javadoc-phoenix4-connectors-assembly.txt

javadoc
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/8/artifact/yetus-general-check/output/patch-javadoc-phoenix5-connectors-assembly.txt

javadoc
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/8/artifact/yetus-general-check/output/patch-javadoc-phoenix-kafka-base.txt

spotbugs
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/8/artifact/yetus-general-check/output/patch-spotbugs-phoenix-kafka-base.txt

unit
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/8/artifact/yetus-general-check/output/patch-unit-root.txt

Test Results
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/8/testReport/

asflicense
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/8/artifact/yetus-general-check/output/patch-asflicense-problems.txt

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

modules
C: phoenix4-connectors-assembly phoenix-spark-base/phoenix5-spark phoenix-hive-base/phoenix5-hive phoenix5-connectors-assembly . phoenix-hive-base phoenix-kafka-base U: .

Console output
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/8/console

versions
git=2.7.4 maven=3.3.9 shellcheck=0.7.0 spotbugs=4.1.3

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

This message was automatically generated.

(!) A patch to the testing environment has been detected.
Re-executing against the patched versions to perform further tests.
The console is at https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/9/console in case of problems.

: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 :x:
test4tests
0m  0s
The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch.

_ Patch Compile Tests _

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

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

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

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

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

-1 :x:
shellcheck
0m  2s
The patch generated 2 new + 1 unchanged - 0 fixed = 3 total (was 1)

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

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

+1 :green_heart:
xml
0m 10s
The patch has no ill-formed XML file.

-1 :x:
javadoc
0m  9s
phoenix4-connectors-assembly in the patch failed.

-1 :x:
javadoc
0m  6s
phoenix5-connectors-assembly in the patch failed.

-1 :x:
javadoc
0m 10s
phoenix-kafka-base in the patch failed.

-1 :x:
spotbugs
0m 25s
phoenix-kafka-base in the patch failed.

_ Other Tests _

-1 :x:
unit
0m  7s
root in the patch failed.

-1 :x:
asflicense
0m 56s
The patch generated 6 ASF License warnings.

48m 31s

Subsystem
Report/Notes

Docker
ClientAPI=1.40 ServerAPI=1.40 base: https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/9/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/phoenix-connectors/pull/39

Optional Tests
dupname asflicense shellcheck shelldocs javac javadoc unit xml compile spotbugs hbaseanti checkstyle

uname
Linux 01d9f4d23b4d 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/phoenix-connectors-personality.sh

git revision
master / 2cb900c

Default Java
Private Build-1.8.0_242-8u242-b08-0ubuntu3~16.04-b08

javadoc
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/9/artifact/yetus-general-check/output/branch-javadoc-phoenix5-connectors-assembly.txt

javadoc
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/9/artifact/yetus-general-check/output/branch-javadoc-phoenix-kafka-base.txt

spotbugs
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/9/artifact/yetus-general-check/output/branch-spotbugs-phoenix-kafka-base.txt

shellcheck
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/9/artifact/yetus-general-check/output/diff-patch-shellcheck.txt

whitespace
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/9/artifact/yetus-general-check/output/whitespace-eol.txt

javadoc
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/9/artifact/yetus-general-check/output/patch-javadoc-phoenix4-connectors-assembly.txt

javadoc
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/9/artifact/yetus-general-check/output/patch-javadoc-phoenix5-connectors-assembly.txt

javadoc
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/9/artifact/yetus-general-check/output/patch-javadoc-phoenix-kafka-base.txt

spotbugs
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/9/artifact/yetus-general-check/output/patch-spotbugs-phoenix-kafka-base.txt

unit
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/9/artifact/yetus-general-check/output/patch-unit-root.txt

Test Results
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/9/testReport/

asflicense
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/9/artifact/yetus-general-check/output/patch-asflicense-problems.txt

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

modules
C: phoenix4-connectors-assembly phoenix-spark-base/phoenix5-spark phoenix-hive-base/phoenix5-hive phoenix5-connectors-assembly . phoenix-hive-base phoenix-kafka-base U: .

Console output
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/9/console

versions
git=2.7.4 maven=3.3.9 shellcheck=0.7.0 spotbugs=4.1.4

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

This message was automatically generated.

(!) A patch to the testing environment has been detected.
Re-executing against the patched versions to perform further tests.
The console is at https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/10/console in case of problems.

: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 :x:
test4tests
0m  0s
The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch.

_ Patch Compile Tests _

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

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

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

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

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

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

+1 :green_heart:
xml
0m 11s
The patch has no ill-formed XML file.

-1 :x:
yamllint
0m  0s
The patch generated 4 new + 0 unchanged - 0 fixed = 4 total (was 0)

-1 :x:
javadoc
0m 10s
phoenix4-connectors-assembly in the patch failed.

-1 :x:
javadoc
0m  7s
phoenix5-connectors-assembly in the patch failed.

-1 :x:
javadoc
0m 12s
phoenix-kafka-base in the patch failed.

-1 :x:
spotbugs
0m 31s
phoenix-kafka-base in the patch failed.

_ Other Tests _

-1 :x:
unit
81m  9s
root in the patch failed.

-1 :x:
asflicense
1m  1s
The patch generated 7 ASF License warnings.

139m 10s

Subsystem
Report/Notes

Docker
ClientAPI=1.40 ServerAPI=1.40 base: https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/11/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/phoenix-connectors/pull/39

Optional Tests
dupname asflicense yamllint javac javadoc unit xml compile spotbugs hbaseanti checkstyle

uname
Linux cafc6400357f 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/phoenix-connectors-personality.sh

git revision
master / 2cb900c

Default Java
Private Build-1.8.0_242-8u242-b08-0ubuntu3~16.04-b08

javadoc
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/11/artifact/yetus-general-check/output/branch-javadoc-phoenix5-connectors-assembly.txt

javadoc
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/11/artifact/yetus-general-check/output/branch-javadoc-phoenix-kafka-base.txt

spotbugs
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/11/artifact/yetus-general-check/output/branch-spotbugs-phoenix-kafka-base.txt

whitespace
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/11/artifact/yetus-general-check/output/whitespace-eol.txt

yamllint
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/11/artifact/yetus-general-check/output/diff-patch-yamllint.txt

javadoc
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/11/artifact/yetus-general-check/output/patch-javadoc-phoenix4-connectors-assembly.txt

javadoc
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/11/artifact/yetus-general-check/output/patch-javadoc-phoenix5-connectors-assembly.txt

javadoc
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/11/artifact/yetus-general-check/output/patch-javadoc-phoenix-kafka-base.txt

spotbugs
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/11/artifact/yetus-general-check/output/patch-spotbugs-phoenix-kafka-base.txt

unit
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/11/artifact/yetus-general-check/output/patch-unit-root.txt

Test Results
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/11/testReport/

asflicense
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/11/artifact/yetus-general-check/output/patch-asflicense-problems.txt

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

modules
C: phoenix4-connectors-assembly phoenix-spark-base/phoenix5-spark phoenix-hive-base/phoenix5-hive phoenix5-connectors-assembly . phoenix-hive-base phoenix-kafka-base U: .

Console output
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/11/console

versions
git=2.7.4 maven=3.3.9 spotbugs=4.1.3 yamllint=1.20.0

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 27s
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  1s
The patch appears to include 1 new or modified test files.

_ master Compile Tests _

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

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

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

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

-1 :x:
javadoc
0m 13s
phoenix5-connectors-assembly in master failed.

-1 :x:
javadoc
0m 10s
phoenix-kafka-base in master failed.

+0 :ok:
spotbugs
4m  3s
root in master has 116 extant spotbugs warnings.

+0 :ok:
spotbugs
1m 21s
phoenix-hive-base in master has 46 extant spotbugs warnings.

+0 :ok:
spotbugs
0m 46s
phoenix-hive-base/phoenix5-hive in master has 45 extant spotbugs warnings.

-1 :x:
spotbugs
0m 25s
phoenix-kafka-base in master failed.

_ Patch Compile Tests _

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

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

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

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

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

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

+1 :green_heart:
xml
0m 11s
The patch has no ill-formed XML file.

-1 :x:
yamllint
0m  0s
The patch generated 4 new + 0 unchanged - 0 fixed = 4 total (was 0)

-1 :x:
javadoc
0m  8s
phoenix4-connectors-assembly in the patch failed.

-1 :x:
javadoc
0m  6s
phoenix5-connectors-assembly in the patch failed.

-1 :x:
javadoc
0m 10s
phoenix-kafka-base in the patch failed.

-1 :x:
spotbugs
0m 27s
phoenix-kafka-base in the patch failed.

_ Other Tests _

-1 :x:
unit
74m 32s
root in the patch failed.

-1 :x:
asflicense
0m 55s
The patch generated 2 ASF License warnings.

122m 48s

Subsystem
Report/Notes

Docker
ClientAPI=1.40 ServerAPI=1.40 base: https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/14/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/phoenix-connectors/pull/39

Optional Tests
dupname asflicense yamllint javac javadoc unit xml compile spotbugs hbaseanti checkstyle

uname
Linux 7715feb33a2f 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/phoenix-connectors-personality.sh

git revision
master / 2cb900c

Default Java
Private Build-1.8.0_242-8u242-b08-0ubuntu3~16.04-b08

javadoc
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/14/artifact/yetus-general-check/output/branch-javadoc-phoenix5-connectors-assembly.txt

javadoc
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/14/artifact/yetus-general-check/output/branch-javadoc-phoenix-kafka-base.txt

spotbugs
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/14/artifact/yetus-general-check/output/branch-spotbugs-phoenix-kafka-base.txt

whitespace
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/14/artifact/yetus-general-check/output/whitespace-eol.txt

yamllint
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/14/artifact/yetus-general-check/output/diff-patch-yamllint.txt

javadoc
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/14/artifact/yetus-general-check/output/patch-javadoc-phoenix4-connectors-assembly.txt

javadoc
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/14/artifact/yetus-general-check/output/patch-javadoc-phoenix5-connectors-assembly.txt

javadoc
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/14/artifact/yetus-general-check/output/patch-javadoc-phoenix-kafka-base.txt

spotbugs
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/14/artifact/yetus-general-check/output/patch-spotbugs-phoenix-kafka-base.txt

unit
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/14/artifact/yetus-general-check/output/patch-unit-root.txt

Test Results
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/14/testReport/

asflicense
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/14/artifact/yetus-general-check/output/patch-asflicense-problems.txt

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

modules
C: phoenix4-connectors-assembly phoenix-spark-base/phoenix5-spark phoenix-hive-base/phoenix5-hive phoenix5-connectors-assembly . phoenix-hive-base phoenix-kafka-base U: .

Console output
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-39/14/console

versions
git=2.7.4 maven=3.3.9 spotbugs=4.1.3 yamllint=1.20.0

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

This message was automatically generated.

The assembly failures in the unit tests are due to a Yetus intgeration problem.


UICircularProgressRing crashes on init(frame:) while running on iOS9

Bug Report
Application compiled on Xcode 11.4 11.4.1 11.5 crashes on UICircularProgressRing while running on iOS 9.3 devices. No crashes on iOS 10 - 13. No crashes while compiling on Xcode 11.3.1
Most probably it's a bug of Xcode, but not guarantied.
Version
ANSWER HERE - 6.3.0
Overview of what you tried to do
ANSWER HERE - Launch an App where UICircularProgressRing should be shown on first screen.
What is the expected outcome?
ANSWER HERE - At least get that screen shown with progress ring on it.
What is the actual outcome?
ANSWER HERE - crash while launch screen (logo) shown
Post sample code or example here
If sample code can't be provided because it's too long, please provide a small example project,
where I can test, if you cannot provide either. There is not much I can do.
ANSWER HERE - nothing special, here is fragment from viewDidLoad()
        // Volume Ring Setup
        self.volumeRing = UICircularProgressRing(frame:CGRect(origin: .zero, size: CGSize(width: 46.0, height: 46.0)))
        if let v = self.volumeRing{
            self.minContentView?.addSubview(v)
            v.value = 50
            v.minValue = 0
            v.shouldShowValueText = false
            v.maxValue = 100
            v.startAngle = 90
            v.endAngle = 90
            v.outerRingColor = UIColor(white: 1.0, alpha: 0.18)
            v.outerRingWidth = 2
            v.innerRingColor = .white
            v.innerRingWidth = 2
            v.innerRingSpacing = -4
        }

If UICircularProgressRing is embedded into storyboard, the result is the same.

Could you provide the error you are getting?

This is from debugger
Thread 1: EXC_BAD_ACCESS (code=1, address=0xe0000010)
#1	0x00fa7d84 in UICircularRingLayer.init() at .../Pods/UICircularProgressRing/src/UICircularProgressRing/UICircularRingLayer.swift:82
#2	0x00fa7e30 in @objc UICircularRingLayer.init() ()
#3	0x2747102a in -[UIView _createLayerWithFrame:] ()
#4	0x27470b4e in UIViewCommonInitWithFrame ()
#5	0x2747078a in -[UIView initWithFrame:] ()
#6	0x00fa306c in UICircularRing.init(frame:) at .../Pods/UICircularProgressRing/src/UICircularProgressRing/UICircularRing.swift:381
#7	0x00fa3124 in @objc UICircularRing.init(frame:) ()
#8	0x00f9e772 in UICircularProgressRing.init(frame:) ()
#9	0x00f9e7c0 in @objc UICircularProgressRing.init(frame:) ()
#10	0x00f9e3ea in UICircularProgressRing.__allocating_init(frame:) ()

This is extraction from Crashlytics on release version (UICircularProgressRing is embedded into storyboard)
Crashed: com.apple.main-thread
EXC_BREAKPOINT 0x000000000000defe
Crashed: com.apple.main-thread
0  UICircularProgressRing         0x762b9a UICircularRingLayer.drawOuterRing() + 163 (UICircularRingLayer.swift:163)
1  UICircularProgressRing         0x762765 UICircularRingLayer.drawOuterRing() + 163 (UICircularRingLayer.swift:163)
2  UICircularProgressRing         0x76202d UICircularRingLayer.draw(in:) + 111 (UICircularRingLayer.swift:111)
3  UICircularProgressRing         0x76212b @objc UICircularRingLayer.draw(in:) + 7545131 (:7545131)
4  QuartzCore                     0x2754eff5 CABackingStoreUpdate_ + 1952
5  QuartzCore                     0x27642771 __ZN2CA5Layer8display_Ev_block_invoke + 56
6  QuartzCore                     0x2754e4c1 CA::Layer::display() + 1328
7  QuartzCore                     0x27532551 CA::Layer::display_if_needed(CA::Transaction*) + 204
8  QuartzCore                     0x27532211 CA::Layer::layout_and_display_if_needed(CA::Transaction*) + 24
9  QuartzCore                     0x275316d1 CA::Context::commit_transaction(CA::Transaction*) + 368
10 QuartzCore                     0x275313a5 CA::Transaction::commit() + 520
11 QuartzCore                     0x2752ab2b CA::Transaction::observer_callback(__CFRunLoopObserver*, unsigned long, void*) + 138
12 CoreFoundation                 0x24ee96c9 CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION + 20
13 CoreFoundation                 0x24ee79cd __CFRunLoopDoObservers + 280
14 CoreFoundation                 0x24e37249 CFRunLoopRunSpecific + 552
15 CoreFoundation                 0x24e37015 CFRunLoopRunInMode + 108
16 UIKit                          0x29510c3d -[UIApplication _run] + 524
17 UIKit                          0x2950b189 UIApplicationMain + 144

1

The same problem, look forward to the author's fix

same problem ，iPhone 6，iOS9.1

same problem ，iPhone 6，iOS9.1

As problem still persists, this library has been removed from my project

Facing the same issue with iOS 9.3.5 on iPad Mini (32 bit device).


Worker & Requeuer failing - Set logpath?

Hi! Postal seems really great so far.
I tried to send a few test messages over the WebUI yet they are still "pending" and from postal status it seems the worker and requeuer are failing. How can we set the log path to investigate the issue further?
Procodile Version   1.0.17
Application Root    /opt/postal/app
Supervisor PID      4571
Started             2017-07-15 17:07:10 +0000

 * worker.1 is not running (Failed)
 * requeuer.1 is not running (Failed)

|| web
|| Quantity            1
|| Command             bundle exec puma -C config/puma.rb
|| Respawning          5 every 3600 seconds
|| Restart mode        usr1
|| Log path            none specified
|| Address/Port        none
|| => web.1            Running      17:07        pid:4577     respawns:0      port:-        tag:-

|| worker
|| Quantity            1
|| Command             bundle exec ruby script/worker.rb
|| Respawning          5 every 3600 seconds
|| Restart mode        start-term
|| Log path            none specified
|| Address/Port        none
|| => worker.1         Failed       17:08        pid:4698     respawns:5      port:-        tag:-

|| cron
|| Quantity            1
|| Command             bundle exec rake postal:cron
|| Respawning          5 every 3600 seconds
|| Restart mode        term-start
|| Log path            none specified
|| Address/Port        none
|| => cron.1           Running      17:07        pid:4581     respawns:0      port:-        tag:-

|| smtp
|| Quantity            1
|| Command             bundle exec rake postal:smtp_server
|| Respawning          5 every 3600 seconds
|| Restart mode        usr1
|| Log path            none specified
|| Address/Port        none
|| => smtp.1           Running      17:07        pid:4583     respawns:0      port:-        tag:-

|| requeuer
|| Quantity            1
|| Command             bundle exec rake postal:requeuer
|| Respawning          5 every 3600 seconds
|| Restart mode        term-start
|| Log path            none specified
|| Address/Port        none
|| => requeuer.1       Failed       17:08        pid:4700     respawns:5      port:-        tag:-

The logs are to be found in the directory /opt/postal/log.
Although you should have a look at my comment on an earlier issue as it might be related https://github.com/atech/postal/issues/270#issuecomment-315178025

Thank you so much! It fixed the issue.

Excellent news.
Theres been a few occurrances of this, I'll see how replicatable it is next week.

I rebooted the server and now all mails are in queue.
I made the change and disabled use_ip_pools setting and new mails are going now. But all old mails still queued :(
Anything we can do to release all queued messages? Have tried postal restart, stop/start and even reboot.


bugfix for the function xyxy2cxcywh

Hi,  first of all, thank you for your work.
I found the function 'xyxy2cxcywh' isn't working correctly.
Let me fixed it.
Thank you.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.syncsyncsync seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


GitHub Projects feature seems abandoned, remove?

The "Projects" feature of Github suggests that there is an ongoing project to release Hawktracer 0.6.0. As we are already on version 0.10.0, I guess the "Projects" feature is not used any more. I'd suggest to remove the "Release 0.6.0" project.

That's right, project 0.6.0 is already released, and can be removed.


AudioElement draws waves without passing array of peaks!

I'm trying to use backend: "AudioElement", but something weird happens that it works as if it's WebAudio, even I changed the compiled code and minified ones it still work as WebAudio! Any idea?
I just want it to show line

Yes, it's a feature. If you don't pass the peaks, it will download the file and decode via Web Audio.

So it only decode and get the peaks array via web audio, but don't use it to play, right?

Exactly. If Web Audio is unavailable, it just displays a thin line and the playhead.

Great!