Bus error:10 at random times during beginning of training

Hey,
I am trying to train your neural network on the KITTI dataset, but I have run into this error "Bus error: 10" which is associated with the code trying to read and invalid memory location, but cannot seem to figure out why.
I got the error initially because I did not have a "testing" folder set up while trying to train and I would get the error immediately.
But after doing so and populating it with some data, it started to run but this error gets thrown at random times within the first 7 steps.
Does the training try to read anything else specific which I may be missing?
Also, I only have a single GPU so I lowered the number in the config, which is why it is only training on 1 file.
Thank you very much

I think you can just checkout jeasinema/tf_voxelnet@2cc0cfd to totally remove the support for multi-gpu training. Or you can try to decrease the parallel_iteration in group_pointcloud.py:83


Graph does not respect wildcard exclusions

Hi - great tool, I've been finding it really useful understanding dependencies in some legacy apps I've been working on.
I've identified an issue where the generated dependency graph incorrectly shows dependencies that maven has excluded via a wildcard.
If I have an app, which depends on lib-b, which depends on lib-c:
app pom:
<project xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://maven.apache.org/POM/4.0.0"
         xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
    <modelVersion>4.0.0</modelVersion>
    <groupId>com.github.crosslandwa</groupId>
    <artifactId>mvndependencygraph-issue-app</artifactId>
    <packaging>jar</packaging>
    <version>1.0</version>
    <dependencies>
        <dependency>
            <groupId>com.github.crosslandwa</groupId>
            <artifactId>mvndependencygraph-issue-lib-b</artifactId>
            <version>1.0</version>
            <exclusions>
                <exclusion>
                    <groupId>com.github.crosslandwa</groupId>
                    <artifactId>*</artifactId>
                </exclusion>
            </exclusions>
        </dependency>
    </dependencies>
</project>

lib-b pom:
<project xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://maven.apache.org/POM/4.0.0"
         xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
    <modelVersion>4.0.0</modelVersion>
    <groupId>com.github.crosslandwa</groupId>
    <artifactId>mvndependencygraph-issue-lib-b</artifactId>
    <packaging>jar</packaging>
    <version>1.0</version>
    <dependencies>
        <dependency>
            <groupId>com.github.crosslandwa</groupId>
            <artifactId>mvndependencygraph-issue-lib-c</artifactId>
            <version>1.0</version>
        </dependency>
    </dependencies>
</project>

And I generate a graph via
mvn com.github.ferstl:depgraph-maven-plugin:graph -DcreateImage=true -DshowGroupIds=true -DshowVersions=true -DshowConflicts=true -DshowDuplicates=true

Expected:
The output for mvn dependency:tree
[INFO] --------< com.github.crosslandwa:mvndependencygraph-issue-app >---------
[INFO] Building mvndependencygraph-issue-app 1.0
[INFO] --------------------------------[ jar ]---------------------------------
[INFO]
[INFO] --- maven-dependency-plugin:2.8:tree (default-cli) @ mvndependencygraph-issue-app ---
[INFO] com.github.crosslandwa:mvndependencygraph-issue-app:jar:1.0
[INFO] \- com.github.crosslandwa:mvndependencygraph-issue-lib-b:jar:1.0:compile
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS

Which would have the expected graph of:

Actual:
But I'm actually seeing...

Note 1: explicitly defining an exclusion with a groupID works as expected, e.g.
<dependency>
    <groupId>com.github.crosslandwa</groupId>
    <artifactId>mvndependencygraph-issue-lib-b</artifactId>
    <version>1.0</version>
    <exclusions>
        <exclusion>
            <groupId>com.github.crosslandwa</groupId>
            <artifactId>mvndependencygraph-issue-lib-c</artifactId>
        </exclusion>
    </exclusions>
</dependency>

Note 2: ommiting both the -DshowConflicts=true and  -DshowDuplicates=true options also works correctly, i.e.
mvn com.github.ferstl:depgraph-maven-plugin:graph -DcreateImage=true -DshowGroupIds=true -DshowVersions=true

Hi
Thank you for the positive feedback and your detailed description!
The reason for your problem is that as soon as you enable showConflicts or showDuplicates the plugin will use the old Maven-2 dependency resolution mechanism, which may produce not the same result and does not support dependency resolution features (such as wildcard exclusions) that were introduced in newer Maven versions. I mentioned this in the plugin documentation (not very visibly, I have to admit).
Internally, the plugin uses an old version of the maven-dependency-tree library, which creates the object model for the dependency graph. The feature for reporting duplicates and conflicts was eliminated in newer versions.
To correctly report duplicates and conflicts I would need to replace the maven-dependency-tree library with my own implementation, which is quite some work.
So for now, I would suggest not to use showConflicts or showDuplicates when you need the wildcard exclusions.
I have been thinking of removing the showConflicts or showDuplicates options from the plugin but I find them quite useful even though the graph might not be accurate in some edge cases.

The fix for #7 does also fix this problem.

Released version 3.2.0 of the plugin


post_logout_redirect_uri and id_token_hint parameters not being passed by Playground2 app during logout

post_logout_redirect_uri and id_token_hint parameters are not being passed with the request to the OIDC Logout Servlet at the IS during logout.

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


making Multinomial sampling slightly faster

This makes multinomial sampling slightly faster by generating a sample sized array of uniformly sampled random numbers outside the kernel and passing it to the kernel. The different distributions in the kernel can use the same array of uniformly sampled numbers as they are independant distributions.
I have addded a file called test/multinomial.lua to do some benchmarking. I can remove it later if the PR is accepted.

The NEW block shows the time for the current code and the old block shows it for the previous code.

@pavanky Could you have a look at this too ?

@pavanky But I think generating just an array (the size of n_sample instead of num_dist * n_sample) is a good improvement. Could it be a good update for now ? Maybe it can be improved again later?

@amartya18x what speedups are you seeing? Can you give the output of the benchmark and specify what GPU you ran them on?

Yeah, I'm not convinced.
Not only does it require allocation and deallocation (which is bad if one is not running with the caching allocator), it's replacing in-kernel generation with extra global memory reads and writes, which together with the memory allocator stuff may be on par with what was there before. Do you have kernel timings?

@soumith I had the benchmarking here in a comment showing the speedups. I think the rebasing messed it up. Let me check

@wickedfoo the problem was the previous kernel was generating more random numbers than needed. This PR fixes that issue by creating the required number of random numbers outside.
That said, this isn't the most optimal fix. We should be generating the necessary random numbers within the kernel.

Is generating more random numbers than needed really that much of an issue? If we're talking microseconds here, this isn't that big of a deal in my opinion.
The RNG being used requires the entire block to update the state at once, although you are right that only one value per warp is being used.
The alternative would be to see if warp divergence for the binary search part isn't too bad, in which case every thread would use the value that it generated locally.

@wickedfoo Another alternative would be to perform parallel linear search instead of a binary search.
Either way the improvements here would be minimal. The more substantial improvements we are seeing come from here: https://github.com/torch/cutorch/pull/784

The RNG being used requires the entire block to update the state at once, although you are right that only one value per warp is being used.

AFAIK this is only a limitation of MTGP32 generator. This is also a bit slower than other generators i CURAND. Philox may even be faster. Any reason to stick with MTGP32 ?

Nvm my previous comment, I didnt realize cutorch only supports this generator.


cmd/compile: low function inline cost

What version of Go are you using (go version)?

$ go version
go version go1.19 linux/amd64

Does this issue reproduce with the latest release?
Yes
What did you do?
I write the following code:
package main
import "encoding/binary"
func main() {
}

func A(b []byte) uint64 {
	return binary.LittleEndian.Uint64(b)
}

// Copy-paste of binary.LittleEndian.Uint64
func Uint64(b []byte) uint64 {
	_ = b[7] // bounds check hint to compiler; see golang.org/issue/14808
	return uint64(b[0]) | uint64(b[1])<<8 | uint64(b[2])<<16 | uint64(b[3])<<24 |
		uint64(b[4])<<32 | uint64(b[5])<<40 | uint64(b[6])<<48 | uint64(b[7])<<56
}

func B(b []byte) uint64 {
	return Uint64(b)
}

Then I run the command go build -gcflags -m=2 . and I see:
can inline A with cost 5 as: func([]byte) uint64 { return binary.littleEndian.Uint64(binary.LittleEndian, b) }
inlining call to binary.littleEndian.Uint64
can inline B with cost 63 as: func([]byte) uint64 { return Uint64(b) }
inlining call to Uint64

So A calls Uint64 from another module and B calls Uint64 from the same module, and A and B have different costs.
What did you expect to see?
I expected to see the same cost no matter where the called function is located.

https://github.com/golang/go/issues/42958


Plugable sort caret

Hi!
Unfortunatelly Bootstrap 4 missing glyphs completely, so the current caret implementation does not work (you do not see anything).
I made a simple hack which enables you to customize the sort caret.

@mcystems, why your PR have my commits? i think you need to rebase


[OTHER] Add RealSollyM Profile

What would you like to share?
I would like to add my profile here on LinkFree, thank you.
Additional information
No response

Hi @RealSollyM, to add your profile to LinkFree, follow the steps given in the Readme.md file.
And then, create a PR, including your profile data! Let us know if you need any help with this! :)


FileAlreadyExistsException thrown by MountableFile

Hi all,
I have a rather obscure issue with how MountableFile is generating the temporary file for copying classpath resources. I occasionally see the following error in my log files -
2017-07-25 18:09:53,920 - [ERROR] - from org.testcontainers.utility.MountableFile in main  Failed to extract classpath resource org/testcontainers/DockerClientFactory.class from JAR file /qc/my-app/lib/org.testcontainers.testcontainers-1.4.2.jar java.nio.file.FileAlreadyExistsException: .testcontainers-tmp-wYxDE 	at sun.nio.fs.UnixException.translateToIOException(UnixException.java:88) 	at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102) 	at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107) 	at sun.nio.fs.UnixFileSystemProvider.newByteChannel(UnixFileSystemProvider.java:214) 	at java.nio.file.spi.FileSystemProvider.newOutputStream(FileSystemProvider.java:434) 	at java.nio.file.Files.newOutputStream(Files.java:216) 	at java.nio.file.Files.copy(Files.java:3016) 	at org.testcontainers.utility.MountableFile.copyFromJarToLocation(MountableFile.java:191) 	at org.testcontainers.utility.MountableFile.extractClassPathResourceToTempLocation(MountableFile.java:157) 	at org.testcontainers.utility.MountableFile.resolvePath(MountableFile.java:120) 	at org.testcontainers.utility.MountableFile.getResolvedPath(MountableFile.java:38) 	at org.testcontainers.DockerClientFactory.lambda$client$0(DockerClientFactory.java:122) 	at org.testcontainers.DockerClientFactory$$Lambda$32/976810274.accept(Unknown Source) 	at org.testcontainers.DockerClientFactory.runInsideDocker(DockerClientFactory.java:225) 	at org.testcontainers.DockerClientFactory.client(DockerClientFactory.java:118) 	at org.testcontainers.containers.GenericContainer.<init>(GenericContainer.java:116) 	at org.testcontainers.containers.GenericContainer.<init>(GenericContainer.java:156) 	at org.testcontainers.containers.BrowserWebDriverContainer.<init>(BrowserWebDriverContainer.java:59) 	at org.testcontainers.containers.BrowserWebDriverContainer.<init>(BrowserWebDriverContainer.java:70)
I'm running CentOS 7 on an EC2 instance, with Java 8u31.
The code causing the exception is here. Having debugged the issue, it looks like in some cases the temporary directory is created, but fails to be deleted. I'm not sure what the exact cause is. It's possible there's another process watching the directory, causing the directory generated to fail to be deleted, or it's some obscure permissioning issue I've not been able to get to the bottom of.
I'm wondering why it's necessary to call mkdirs() prior to generating the temporary file? Would it make sense to call mkdirs on the parent directory instead, and avoid having to delete the directory generated? Why is it necessary to create the parent directory, given that it's the same directory the application is executing in? I'm assuming the MountableFile has to be in the current directory (rather than a temporary directory) for some Docker reason. Is that correct?
I'm working on a fix for this issue, and I'll submit once I've verified.
Thanks,
Damien.

I've merged the fix (#443) and will release shortly.


Only allow udevinstaller on linux

Udev rules are only need on linux. Additionally, attempting to install them on any other platform will probably fail. So don't let that happen.
Fixes #208

cc @nopara73 @lontivero
Windows binary for testing attached to this comment
hwi-1.0.1-windows-amd64.zip

Tested. The binary works. Also concept ACK and code looks good to me.


I need to reload vscode after each open and close of the comment bubble

Extension version: 0.5.1
VSCode Version: 1.33.0-insider
OS: Ubuntu 18.04.2 LTS

Steps to Reproduce:

Open a PR
Click on a line to add a comment.
Dismiss it, either by adding a comment or cancel, both work.
Try to add another comment.

I need to reload the window and then I can add another one.

Thanks for reporting this! This is an issue with the insiders version of VSCode, using the stable version is a possible workaround

Fixed upstream, tomorrow's version of VSCode insider's will have the fix

Awesome! Thank you @RMacfarlane


Circleci/docker

Fixes #[issue number].
Status
[ ] Under development
[ ] Waiting for code review
[ ] Waiting for merge

Information
[ ] Contains breaking changes
[ ] Contains new API(s)
[ ] Contains documentation
[ ] Contains test
[ ] Contains examples

To-do list
[ ] [Fix this thing]
[ ] [Fix another thing]
[ ] ...

I think it would be good to have a very short description about how to run the docker images in this md file, mostly so that people knows why they exist: https://github.com/qlik-oss/server-side-extension/blob/circleci/docker/examples/python/GetStarted.md


Change emulator, chip count and 4 ops needs UI

Change the work model to enable these settings to be changed in UI-less settings.

Done and added parameters:

emulator
chip count
4op channel count


Add some type hinting to the classes inside models.

Completes type hinting in the test suite structure #4570
The files that got type hints added, where mainly files that I have interacted with as an end user.
The PR is fully Compatible with Compatible with python 3.6 onwards.

Fixing everything in this PR and then re-reviewing is a pretty big task. I believe it would be best to start from a single module like robot.model.testsuite and type it thoroughly. Once we get that done, we set standard that can then be followed when typing other modules.

@pekkaklarck I think I have gone through all the requested changes inside robot.model.testsuite

@pekkaklarck I think I have gone through all the requested changes inside robot.model.testsuite

I added few more comments. I mentioned two things to decide in them:

Should we use stringified types like 'x | y' and 'list[int]' or use Union, List, etc? We discussed this on #devel and most people seemed to prefer the former. I also like that style more, especially with unions, and it avoids lot of from typing imports.
How to format long signatures. Having each parameter on its own line would be an easy solution, but such style takes lot of vertical space. I believe we should try fitting multiple params per line.

How do you feel about the above? If you agree with me, please update testsuite to use such style. We can then see how it feels and decide should we use that style also with other files.
The next question is how to merge only testsuite now. I think I cannot, at least here on web, merge only one file, so a new PR would probably be easiest.

Changes to TestSuite.py

Re-ordered imports
Switched to stringified type hints
Changed init signature to maximise horizontal character count before newlines

As for, just emerging TestSuite.py, I will roll back and locally stash my changes and use them in a follow-up PR


Add ability to cache by the last stack frame which exits the library

closing in favor of https://github.com/finch-tensor/Finch.jl/issues/678


Add result state file

If a user wants to continue a simulation at time t based on the results of a previous simulation that ended at time t, they need to use a Basin / state table with the final storages from the previous simulation. We should add an output file basin_state.arrow that contains this information.
This can then also be used in Delft-FEWS for this purpose.
If PidControl nodes are also present they should also carry over state, but this could be added later, since we don't support setting this state as input either at the moment.

Hi @visr , if this is implemented we should document it. such that externals (such as Micha (Hydrologic)) can use it


Render text below pin

Partnered with @tiffeli
In this PR we added the rendering of the pin's title below each pin.
Resolves #54
Feedback requested on code quality and styling.
Thanks

@jake-shasteen Reviewed :+1:

Tapping @asu91 for second review (cc: @jake-shasteen )

@jake-shasteen @bignell  Reviewed. Good to go :heavy_check_mark:

@bignell i tested this too on my phone, again. It works fine.


Swaylock freezes on multimon

Hyprland Version
Hyprland, built from branch  at commit b08b72358ad549fd066e5be0fc3aa4c9df367607 dirty (). Tag: v0.27.2  flags: (if any)
Bug or Regression?
Bug
Description
lock screen get's freezed on one display and mouse is accessible on the other one.
issue Is this somehow related to hyprland?
created this issue for knowing this.
How to reproduce
the laptop should be locked and then plugged in to the monitor.
Crash reports, logs, images, videos
No response

atm unable to debug multimon issues but last time I checked it worked just fine on my end

atm unable to debug multimon issues but last time I checked it worked just fine on my end

it happens randomly sometimes plugging in the monitor works fine.
but sometimes it freezes will try to get log or something next time if it happens next time.

Got hyprlock


&& is not supported in regular expressions

Describe the bug

Textmate language grammars, as consumed by linguist, are specified (at least, according to the vscode docs) to use the "Onigurama" regex engine, which supports a pattern like [_a-zA-Z&&[^w]].
Expected behaviour
The following language:
{
  "name": "Broken",
  "scopeName": "source.broken",
  "patterns": [
     { "match": "[_a-z&&[^bad]]+",
       "name": "entity.name.function"},
     { "match": "[_CE-Z]+",
       "name": "entity.name.function"}
  ]
}

applied to the following input
good
bad
GOOD
BAD

should highlight both good and GOOD.
In vs-code, this is exactly what it does.
In https://github-lightshow.herokuapp.com/, it highlights only GOOD.

Related discussion

Additional notes

Perhaps the short-term ask here is for linquist to document which regex engine it uses.

Workaround: replace [a-z&&[^aeiou]]+ with ((?![^aeiou])[a-z])+ instead. 😉
Or—if the universal set allows—write them out in full: [b-df-hj-np-tv-z]+ (this tends to be more performant than the aforementioned hack).

['0-8A-Y_a-yΑ-Ψα-κμ-ψϊ-Ϻᵢ-ᵩἀ-´ⁿ-₈ₐ-ₛ℀-ⅎ𝒜-𝖞]+

Generated from the following hacky JavaScript snippet:
function expandRanges(text){
	return text.replace(/([^-\\]|\\.)-([^-\\]|\\.)/gu, (text, from, to) => {
		text = "";
		from = from.codePointAt(0);
		to   = to.codePointAt(0);
		for(let i = from; i < to; ++i)
			text += String.fromCodePoint(i);
		return text;
	});
}

... using a not-so-hacky JavaScript function I wrote a few nights ago, funnily enough. It doesn't check for things like a leading ^ or escaped carets, but hey, I said it was hacky…

I thin kyou have some off-by-one errors there, you stole my z and Z!

 I literally wasted an hour the other night trying to figure out what happened to a missing character…


ADD : implement psql ON CONFLICT DO NOTHING

add insert_conflict_columns param for append mode
example : to_sql(mode="append", insert_conflict_columns=["c"]...)
Feature or Bugfix

Feature

Detail

Added to run 'ON CONFLICT DO NOTHING' queries.

Relates
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

AWS CodeBuild CI Report

CodeBuild project: GitHubCodeBuild8756EF16-pDO66x4b9gEu
Commit ID: 3d9d74ae7dbeb9c3da8a8b2de0e80c5651cad8a5
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubCodeBuild8756EF16-pDO66x4b9gEu
Commit ID: ef630559f2a6dac1480f7ce32f6e0b8df8b48bd6
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubCodeBuild8756EF16-pDO66x4b9gEu
Commit ID: 21e1a190af53024d70add08030927787aaee9db8
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository


Feedback target page tabs are not keyboard accessible at all 👎🏽

It is currently impossible to change tabs using the keyboard only...
2.1.1 (AA) All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints. https://www.w3.org/WAI/WCAG21/Understanding/keyboard.html
https://github.com/UniversityOfHelsinkiCS/palaute/assets/81435393/e404b268-14d6-4344-82b3-74e67d1598f4

This issue also persist for student users.
I have extracted the FeedbackTarget view Tab logic into own component in commit ae64d5d as the TabGroup was using the same Tabs as in RouterTabs. In order to fix the keyboard navigation issues on the RouterTab in commit f1d424e I had to make a change that broke the FeedbackTarget view tabs, hence the extraction in to own component.
Also it is better to work on the TabGroup component on their own separate from the RouterTabs, as it introduces the grouping which is not used in RouterTabs.
The grouping however breaks the native material UI Tabs element semantics as it expects the children to be  elements. This I tried to fix quickly but was unable to get the keyboard navigation per ARIA recommendations.


Add Diginamic

Add Diginamic
School Web site URL
https://www.diginamic.fr/
Long-term IT related course
https://www.diginamic.fr/formation-concepteur-developpeur-application-fullstack/
Contact e-mail article
https://www.diginamic.fr/faq/#b1b0da4d79cd7936b
E-mail addresses
Professional
Firstname<EMAIL_ADDRESS>
Student
Firstname<EMAIL_ADDRESS>

@FYHenry First stage of verification passed, official domain is diginamic.fr as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@FYHenry Thank you for your patience while waiting for a review and processing your request. Pull request merged.
Please notice that to add diginamic-formation.fr you need to create a separate pull request and comment it with a proof, which shows that the school recognizes the domain diginamic-formation.fr as an official email domain for the students.
You can provide us with any of the following:

A copy of instruction (a hard-copy or electronic one) given to you by the school that tells you to use an email address in this email domain
An URL of a page at the official school website that says that students use this email domain
A reference to a recognized journal where an article was published by someone from the school, with explicit affiliation to the school, and e-mail address from the email domain
A WHOIS data that link the email domain to the school somehow
A copy of official letter from the school representative saying that the school provides e-mail addresses in this domain to the students
Anything else that can prove this fact in similar way, i.e. can be verified independently.


Fastnlight: Watch theleadgenerationagency.uk

Fastnlight requests the watch of the watch_keyword theleadgenerationagency\.uk. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

theleadgenerationagency\.uk has been seen in 0 true positives, 0 false positives, and 0 NAAs.

Approved by Jeff Schaller in Charcoal HQ


Update the subscribe method on the KafkaEventConsumer so that it creates a new consumer group for each consumer id

waterdog-oss/bugfix/#13 closes this issue


Fix ColumDescriptor copy to HColumnDescriptor. Issue #1583

This should fix issue #1583.

It looks like BigtableAdmin doesn't actually use this.


Update chaos-studio-limitations.md

Adding note about Resource MOVE support

@nikhilkaul-msft can you change "DO" to "do" or "does".

I think I fixed it and omitted this if you can confirm on your end.
Thanks,
Nikhil
From: prasha-microsoft @.>
Sent: Monday, June 5, 2023 4:55 PM
To: MicrosoftDocs/azure-docs @.>
Cc: Nikhil Kaul @.>; Mention @.>
Subject: Re: [MicrosoftDocs/azure-docs] Update chaos-studio-limitations.md (PR #110493)
@nikhilkaul-msfthttps://github.com/nikhilkaul-msft can you change "DO" to "do" or "does".

Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/pull/110493#issuecomment-1577699187, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A6WJZ53244N6EPDPWM2NZWTXJZWU5ANCNFSM6AAAAAAY3RO6ME.
You are receiving this because you were mentioned.Message ID: @.***>


Assistance with Docker and Microsoft 365 shared account

Hi,
Many thanks for this proxy. I'm looking into making use of it to access a Microsoft 365 shared account via IMAP, on a windows app client, but I'm finding an issue after successfully logging in and getting a success message using the login redirection url.
The base setup is using blacktirion/email-oauth2-proxy-docker. On that part, I have that container with the settings below as well as a temporary firefox (via VNC) browser to handle the login on the headless machine (full docker compose file in the bottom):
    environment:
      - DEBUG=false
      - CACHE_STORE=/config/credstore.config
      - LOGFILE=true
      - LOCAL_SERVER_AUTH=true

Considering that the user credentials<EMAIL_ADDRESS>and shared inbox address<EMAIL_ADDRESS>I have the following in emailproxy.config:
<EMAIL_ADDRESS>permission_url = https://login.microsoftonline.com/(MICROSOFT365-TENANT-ID-REDACTED)/oauth2/v2.0/authorize
token_url = https://login.microsoftonline.com/(MICROSOFT365-TENANT-ID-REDACTED)/oauth2/v2.0/token
oauth2_scope = https://outlook.office365.com/IMAP.AccessAsUser.All https://outlook.office365.com/POP.AccessAsUser.All https://outlook.office365.com/SMTP.Send offline_access
redirect_uri = http://localhost:20901
client_id = (REDACTED)
client_secret = (REDACTED)

So I configure the IMAP client app to use<EMAIL_ADDRESS>as the email address and I can get the login URL from the proxy logs (first line below). I paste the link on the firefox browser that is on the same host and network as the email proxy, and can move on with the GUI authentication (using<EMAIL_ADDRESS>as credentials of course,  given there are no credentials to give the shared inbox directed access):
2024-04-25 12:50:15: Please visit the following URL to authenticate account<EMAIL_ADDRESS>https://login.microsoftonline.com/(REDACTED)

After I paste
Email OAuth 2.0 Proxy successfully authenticated account<EMAIL_ADDRESS>You can close this window.

However, the IMAP client still doesn't have access and the email proxy log follows up with:
2024-04-25 12:50:45: Local server auth mode (localhost:20901): unable to start local server. Please check that `redirect_uri` for<EMAIL_ADDRESS>is unique across accounts, specifies a port number, and is not already in use. See the documentation in the proxy's sample configuration file. OSError(98, 'Address in use')

What am I doing wrong here? Thanks in advance
ps 1: does it have anything to do with using redirect_listen_address = http://<IP_ADDRESS>:8080? I really didn't understand this part in the documentation.

ps 2: I case anyone else is interested, here's the docker compose:
services:
  proxy1:
    network_mode: host
    environment:
      - DEBUG=false
      - CACHE_STORE=/config/credstore.config
      - LOGFILE=true
      - LOCAL_SERVER_AUTH=true
    volumes:
      - /volume1/docker/it-tools-emailproxy/v/config:/config
    image: blacktirion/email-oauth2-proxy-docker
  firefox-temp:
    image: lscr.io/linuxserver/firefox:latest
    container_name: firefox-temp
    security_opt:
      - seccomp:unconfined
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Etc/UTC
      - CUSTOM_PORT=3200
      - CUSTOM_HTTPS_PORT=3201
    network_mode: host
    volumes:
      - vol_browser_firefox:/config
      - /var/run/docker.sock:/var/run/docker.sock
    shm_size: 1gb
volumes:
  vol_browser_firefox: null
networks: {}

I can't help with the Docker part (I don't use that setup), but from what you've said that doesn't seem to be an issue here. Please post the log from the proxy in --debug mode (see the Troubleshooting section of the readme).
Another thing that might help is to first try getting things working whilst running the proxy locally (i.e., as simple a setup as possible). Once this is configured and authenticated, you can reuse the same pre-authorised configuration file in your Docker setup

Here's the log with debug enabled:
2024-04-25 23:07:33: Authorisation request received for<EMAIL_ADDRESS>(local server auth mode)
2024-04-25 23:07:33: Email OAuth 2.0 Proxy Local server auth mode: please authorise a request for account<EMAIL_ADDRESS>2024-04-25 23:07:33: Local server auth mode (localhost:20901): starting server to listen for authentication response
2024-04-25 23:07:33: Local server auth mode (localhost:20901): unable to start local server. Please check that `redirect_uri` for<EMAIL_ADDRESS>is unique across accounts, specifies a port number, and is not already in use. See the documentation in the proxy's sample configuration file. OSError(98, 'Address in use')
2024-04-25 23:07:33: Authorisation result error for<EMAIL_ADDRESS>- aborting login. No-GUI authorisation request failed or timed out
2024-04-25 23:07:33: IMAP ([::ffff:<IP_ADDRESS>]:49775-{[::ffff:<IP_ADDRESS>]:20993}-outlook.office365.com:993) <-- b'MBN00000002 NO AUTHENTICATE Email OAuth 2.0 Proxy: Login failed for account<EMAIL_ADDRESS>No-GUI authorisation request failed or timed out\r\n'
2024-04-25 23:07:33: IMAP ([::ffff:<IP_ADDRESS>]:49775-{[::ffff:<IP_ADDRESS>]:20993}-outlook.office365.com:993) --> b'MBN00000003 LOGIN [[ Credentials removed from proxy log ]]\r\n'
2024-04-25 23:07:34: Authorisation request received for<EMAIL_ADDRESS>(local server auth mode)
2024-04-25 23:07:34: Email OAuth 2.0 Proxy Local server auth mode: please authorise a request for account<EMAIL_ADDRESS>2024-04-25 23:07:34: Local server auth mode (localhost:20901): starting server to listen for authentication response
2024-04-25 23:07:34: Local server auth mode (localhost:20901): unable to start local server. Please check that `redirect_uri` for<EMAIL_ADDRESS>is unique across accounts, specifies a port number, and is not already in use. See the documentation in the proxy's sample configuration file. OSError(98, 'Address in use')
2024-04-25 23:07:34: Authorisation result error for<EMAIL_ADDRESS>- aborting login. No-GUI authorisation request failed or timed out
2024-04-25 23:07:34: IMAP ([::ffff:<IP_ADDRESS>]:49775-{[::ffff:<IP_ADDRESS>]:20993}-outlook.office365.com:993) <-- b'MBN00000003 NO LOGIN Email OAuth 2.0 Proxy: Login failed for account<EMAIL_ADDRESS>No-GUI authorisation request failed or timed out\r\n'
2024-04-25 23:07:40: IMAP ([::ffff:<IP_ADDRESS>]:49757-{[::ffff:<IP_ADDRESS>]:20993}-outlook.office365.com:993)     <-- b'* BYE Connection is closed. 13\r\n'
2024-04-25 23:07:40: IMAP ([::ffff:<IP_ADDRESS>]:49757-{[::ffff:<IP_ADDRESS>]:20993}-outlook.office365.com:993) <-- b'* BYE Connection is closed. 13\r\n'
2024-04-25 23:07:40: IMAP ([::ffff:<IP_ADDRESS>]:49757-{[::ffff:<IP_ADDRESS>]:20993}-outlook.office365.com:993) <-- [ Server disconnected ]
2024-04-25 23:07:40: IMAP ([::ffff:<IP_ADDRESS>]:49757-{[::ffff:<IP_ADDRESS>]:20993}-outlook.office365.com:993) --> [ Client disconnected ]
2024-04-25 23:07:46: New incoming connection to IMAP server at [::]:20993 (unsecured) proxying outlook.office365.com:993 (SSL/TLS)
2024-04-25 23:07:46: Accepting new connection from [::ffff:<IP_ADDRESS>]:49776 to IMAP server at [::]:20993 (unsecured) proxying outlook.office365.com:993 (SSL/TLS)
2024-04-25 23:07:46: IMAP ([::ffff:<IP_ADDRESS>]:49776-{[::ffff:<IP_ADDRESS>]:20993}-outlook.office365.com:993) --> [ Client connected ]
2024-04-25 23:07:46: IMAP ([::ffff:<IP_ADDRESS>]:49776-{[::ffff:<IP_ADDRESS>]:20993}-outlook.office365.com:993) <-> [ Starting TLS handshake ]
2024-04-25 23:07:46: IMAP ([::ffff:<IP_ADDRESS>]:49776-{[::ffff:<IP_ADDRESS>]:20993}-outlook.office365.com:993) <-> [ TLSv1.2 handshake complete ]
2024-04-25 23:07:46: IMAP ([::ffff:<IP_ADDRESS>]:49776-{[::ffff:<IP_ADDRESS>]:20993}-outlook.office365.com:993)     <-- b'* OK The Microsoft Exchange IMAP4 service is ready. [TQBBADIAUAAyADkAMgBDAEEAMAAwADAAOQAuAEUAUwBQAFAAMgA5ADIALgBQAFIATwBEAC4ATwBVAFQATABPAE8ASwAuAEMATwBNAA==]\r\n'
2024-04-25 23:07:46: IMAP ([::ffff:<IP_ADDRESS>]:49776-{[::ffff:<IP_ADDRESS>]:20993}-outlook.office365.com:993) <-- b'* OK The Microsoft Exchange IMAP4 service is ready. [TQBBADIAUAAyADkAMgBDAEEAMAAwADAAOQAuAEUAUwBQAFAAMgA5ADIALgBQAFIATwBEAC4ATwBVAFQATABPAE8ASwAuAEMATwBNAA==]\r\n'
2024-04-25 23:07:46: IMAP ([::ffff:<IP_ADDRESS>]:49776-{[::ffff:<IP_ADDRESS>]:20993}-outlook.office365.com:993) --> b'MBN00000001 CAPABILITY\r\n'
2024-04-25 23:07:46: IMAP ([::ffff:<IP_ADDRESS>]:49776-{[::ffff:<IP_ADDRESS>]:20993}-outlook.office365.com:993)     --> b'MBN00000001 CAPABILITY\r\n'
2024-04-25 23:07:46: IMAP ([::ffff:<IP_ADDRESS>]:49776-{[::ffff:<IP_ADDRESS>]:20993}-outlook.office365.com:993)     <-- b'* CAPABILITY IMAP4 IMAP4rev1 AUTH=PLAIN AUTH=XOAUTH2 SASL-IR UIDPLUS ID UNSELECT CHILDREN IDLE NAMESPACE LITERAL+\r\n'
2024-04-25 23:07:46: IMAP ([::ffff:<IP_ADDRESS>]:49776-{[::ffff:<IP_ADDRESS>]:20993}-outlook.office365.com:993) <-- b'* CAPABILITY IMAP4 IMAP4rev1 AUTH=PLAIN SASL-IR UIDPLUS ID UNSELECT CHILDREN IDLE NAMESPACE LITERAL+\r\n'
2024-04-25 23:07:46: IMAP ([::ffff:<IP_ADDRESS>]:49776-{[::ffff:<IP_ADDRESS>]:20993}-outlook.office365.com:993)     <-- b'MBN00000001 OK CAPABILITY completed.\r\n'
2024-04-25 23:07:46: IMAP ([::ffff:<IP_ADDRESS>]:49776-{[::ffff:<IP_ADDRESS>]:20993}-outlook.office365.com:993) <-- b'MBN00000001 OK CAPABILITY completed.\r\n'
2024-04-25 23:07:47: IMAP ([::ffff:<IP_ADDRESS>]:49776-{[::ffff:<IP_ADDRESS>]:20993}-outlook.office365.com:993) --> b'MBN00000002 AUTHENTICATE PLAIN\r\n'
2024-04-25 23:07:47: IMAP ([::ffff:<IP_ADDRESS>]:49776-{[::ffff:<IP_ADDRESS>]:20993}-outlook.office365.com:993) <-- b'+ \r\n'
2024-04-25 23:07:47: IMAP ([::ffff:<IP_ADDRESS>]:49776-{[::ffff:<IP_ADDRESS>]:20993}-outlook.office365.com:993) --> b'[[ Credentials removed from proxy log ]]'

And thanks for the alternate solution , I'll give it a go as soon as I can.

This log doesn't include a successful request as outlined in your original report, but it does show the proxy repeatedly trying to start its local web server (which it requires to pick up the authentication response) and failing to do so. This could be caused by something in your Docker setup, but I'm not sure what that might be since this does work for others.
Please could you post the full log, including the part where you do actually get the authentication prompt, and also the bit where this subsequently fails.

My apologies, found the culprit. In emailproxy.config this setting had to be set to false. I was finding it weird not seeing any data on the credstore.config. This particular client is constantly trying to login and given the password filled in is always wrong (as it is a shared inbox, with no direct credentials), I guess the proxy deletes the token.
[emailproxy]
delete_account_token_on_password_error = False

Thanks for following up – glad you were able to resolve this.


HBASE-24612: Consider allowing a separate EventLoopGroup for acceptin…

…g new connections.
Netty applications often set a separate thread pool for accepting connections rather than sharing a single pool for accepting new connections and the work those connections do.
It would be interesting to allow configuring a separation of pools to allow users to experiment with a pool dedicated to accepting new connections.
This PR simply adds the second boss thread pool and does not yet allow sticking with the current single pool option.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 41s
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.

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
3m 47s
branch-2 passed

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

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

_ Patch Compile Tests _

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

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

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

+1 :green_heart:
hadoopcheck
12m 47s
Patch does not cause any errors with Hadoop 3.1.2 3.2.1.

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

_ Other Tests _

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

36m 53s

Subsystem
Report/Notes

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

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

JIRA Issue
HBASE-24612

Optional Tests
dupname asflicense spotbugs hadoopcheck hbaseanti checkstyle

uname
Linux 616a7ce58b53 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
branch-2 / f3d47d3c8e

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

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

modules
C: hbase-server U: hbase-server

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

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f) spotbugs=3.1.12

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

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

_ Prechecks _

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
3m 42s
branch-2 passed

+1 :green_heart:
compile
0m 56s
branch-2 passed

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

+1 :green_heart:
javadoc
0m 37s
branch-2 passed

_ Patch Compile Tests _

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

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

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

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

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

_ Other Tests _

+1 :green_heart:
unit
135m 22s
hbase-server in the patch passed.

158m  2s

Subsystem
Report/Notes

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

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

JIRA Issue
HBASE-24612

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux a677824be929 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
branch-2 / f3d47d3c8e

Default Java
1.8.0_232

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

Max. process+thread count
3770 (vs. ulimit of 12500)

modules
C: hbase-server U: hbase-server

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

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

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

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

_ Prechecks _

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
4m 44s
branch-2 passed

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

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

-0 :warning:
javadoc
0m 42s
hbase-server in branch-2 failed.

_ Patch Compile Tests _

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

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

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

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

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

_ Other Tests _

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

237m 25s

Subsystem
Report/Notes

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

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

JIRA Issue
HBASE-24612

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 36995c3f2c6a 4.15.0-101-generic #102-Ubuntu SMP Mon May 11 10:07:26 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / f3d47d3c8e

Default Java
2020-01-14

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

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

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

Max. process+thread count
2528 (vs. ulimit of 12500)

modules
C: hbase-server U: hbase-server

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

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

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  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.

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
3m 57s
branch-2 passed

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

+1 :green_heart:
spotbugs
2m  4s
branch-2 passed

_ Patch Compile Tests _

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

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

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

+1 :green_heart:
hadoopcheck
12m 32s
Patch does not cause any errors with Hadoop 3.1.2 3.2.1.

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

_ Other Tests _

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

35m 51s

Subsystem
Report/Notes

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

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

JIRA Issue
HBASE-24612

Optional Tests
dupname asflicense spotbugs hadoopcheck hbaseanti checkstyle

uname
Linux 07994758f7f7 4.15.0-101-generic #102-Ubuntu SMP Mon May 11 10:07:26 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 4506f8d8ab

checkstyle
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1952/2/artifact/yetus-general-check/output/diff-checkstyle-hbase-server.txt

Max. process+thread count
84 (vs. ulimit of 12500)

modules
C: hbase-server U: hbase-server

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

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f) spotbugs=3.1.12

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

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

_ Prechecks _

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
4m 15s
branch-2 passed

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

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

+1 :green_heart:
javadoc
0m 43s
branch-2 passed

_ Patch Compile Tests _

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

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

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

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

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

_ Other Tests _

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

172m 31s

Subsystem
Report/Notes

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

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

JIRA Issue
HBASE-24612

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux e0c0aeb72e31 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
branch-2 / 4506f8d8ab

Default Java
1.8.0_232

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

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

Max. process+thread count
4356 (vs. ulimit of 12500)

modules
C: hbase-server U: hbase-server

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

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

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

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

_ Prechecks _

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
4m 48s
branch-2 passed

+1 :green_heart:
compile
1m 16s
branch-2 passed

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

-0 :warning:
javadoc
0m 43s
hbase-server in branch-2 failed.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
4m 22s
the patch passed

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

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

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

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

_ Other Tests _

+1 :green_heart:
unit
191m 48s
hbase-server in the patch passed.

221m 10s

Subsystem
Report/Notes

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

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

JIRA Issue
HBASE-24612

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 9a541546cdf4 4.15.0-101-generic #102-Ubuntu SMP Mon May 11 10:07:26 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 4506f8d8ab

Default Java
2020-01-14

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

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

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

Max. process+thread count
2557 (vs. ulimit of 12500)

modules
C: hbase-server U: hbase-server

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

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

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 38s
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.

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
3m 44s
branch-2 passed

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

+1 :green_heart:
spotbugs
2m  0s
branch-2 passed

_ Patch Compile Tests _

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

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

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

+1 :green_heart:
hadoopcheck
12m  8s
Patch does not cause any errors with Hadoop 3.1.2 3.2.1.

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

_ Other Tests _

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

35m 46s

Subsystem
Report/Notes

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

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

JIRA Issue
HBASE-24612

Optional Tests
dupname asflicense spotbugs hadoopcheck hbaseanti checkstyle

uname
Linux 77e2e8baeff3 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
branch-2 / a3567037c6

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

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

modules
C: hbase-server U: hbase-server

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

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f) spotbugs=3.1.12

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

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

_ Prechecks _

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
3m 42s
branch-2 passed

+1 :green_heart:
compile
0m 56s
branch-2 passed

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

+1 :green_heart:
javadoc
0m 37s
branch-2 passed

_ Patch Compile Tests _

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

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

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

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

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

_ Other Tests _

+1 :green_heart:
unit
138m  6s
hbase-server in the patch passed.

160m 54s

Subsystem
Report/Notes

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

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

JIRA Issue
HBASE-24612

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux d25f9cb9ba4e 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
branch-2 / a3567037c6

Default Java
1.8.0_232

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

Max. process+thread count
4717 (vs. ulimit of 12500)

modules
C: hbase-server U: hbase-server

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

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

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

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

_ Prechecks _

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
4m 43s
branch-2 passed

+1 :green_heart:
compile
1m  8s
branch-2 passed

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

-0 :warning:
javadoc
0m 43s
hbase-server in branch-2 failed.

_ Patch Compile Tests _

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

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

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

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

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

_ Other Tests _

+1 :green_heart:
unit
187m  9s
hbase-server in the patch passed.

215m 38s

Subsystem
Report/Notes

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

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

JIRA Issue
HBASE-24612

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 65f57ca083ce 4.15.0-101-generic #102-Ubuntu SMP Mon May 11 10:07:26 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / a3567037c6

Default Java
2020-01-14

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

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

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

Max. process+thread count
2677 (vs. ulimit of 12500)

modules
C: hbase-server U: hbase-server

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

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

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

This message was automatically generated.

Closing. No progress.


add Workflows

#3

one commit , please, and please comment the macos and windows, unless I have prepare for the two platforms

Ok, fine..


Bugfix/282-project-titles-look-bad

The title is now smaller, and is cropped when it overflows the card.
I also added a tooltip so people can see the full title of projects with long names.
@fliiiix
@randombenj
I welcome suggestions on how we could improve the style of the tooltip.
For now it looks like this:

Fixes: #282

love it :heart_eyes:


Check deprecated APIs

wo apply cluster policy

name: validate-custom-removals
match:
resources:
kinds:
# - networking.istio.io/v1alpha3/VirtualService
- autoscaling/v2beta1/HorizontalPodAutoscaler
- networking.istio.io/v1alpha3/Gateway
but   autoscaling/v2beta2/HorizontalPodAutoscaler  also deny ,why ???

also if config  networking.istio.io/v1alpha3/VirtualService ,then v1alpha3 and v1beta1 all deny
if config networking.istio.io/v1beta1/VirtualService  then vibeta1 deny ,  v1alpha3 allow

I found that I actually deployed v2beta2 on the eks cluster, but request.object.kind is really v2beta1

@ziansong - if the policy isn't working as expected, please open an issue in kyverno/kyverno repo with reproduce steps. Thanks!