Return Err from Context::from_expr on non-record expr

Description of changes
A small change to make an invariant more robust.
The Context struct requires as an invariant that it may only contain a record expression, but Context::from_expr could construct contexts violating the invariant (although this fail a debug assertion).
Issue #, if available
Checklist for requesting a review
The change in this PR is (choose one, and delete the other options):

[x] A change "invisible" to users (e.g., documentation, changes to "internal" crates like cedar-policy-core, cedar-validator, etc.)

I confirm that this PR (choose one, and delete the other options):

[x] Does not update the CHANGELOG because my change does not significantly impact released code.

I confirm that cedar-spec (choose one, and delete the other options):

[x] Does not require updates because my change does not impact the Cedar Dafny model or DRT infrastructure.

Disclaimer
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Two questions:

How does this manage to change the public API?
Instead of having Context hold a RestrictedExpr, can we have it hold a the pairs directly? That way we strip out all of the panics.

Two questions:

How does this manage to change the public API?

It doesn't.

Instead of having Context hold a RestrictedExpr, can we have it hold a the pairs directly? That way we strip out all of the panics.

This would be nice, but I didn't make that change because Context derives Serialize and Deserialize, and I think any change to the serialization would change the JSON accepted by cedar_policy::Context::from_json_value in the public API. If we're confident the change doesn't change the serialization then we could do it.


Update README.md

I have switch to 2.0. I propose to leave 1.0 as is

I have switch to 2.0. I propose to leave 1.0 as is


Type 'string' does not satisfy the constraint 'URL'

I am getting the following error when running the script with the new stable deno version 1.20.3:
Check file:///Users/pgagnidze/Development/personal/coinsearch/src/index.ts
error: TS2344 [ERROR]: Type 'string' does not satisfy the constraint 'URL'.
type _assertSupportedInfoIsSubtype = Assert<RequestInfo, SupportedRequestInfo>
                                                         ~~~~~~~~~~~~~~~~~~~~
    at https://deno.land/x/notion_sdk@v1.0.3/src/fetch-types.ts:9:58

You can reproduce it by running the following program https://github.com/pgagnidze/coinsearch/runs/5733563210?check_suite_focus=true

Hey, thanks for the report ❤
I think this is related to a supposed-to-not-break change in Deno: https://github.com/denoland/deno/pull/14113 and there is a fix for that breakage https://github.com/denoland/deno/pull/14134
I should be able to put together a fix from my side sometime today, in the meantime going to Deno Canary might help, or the previous stable Deno.

I've included a cleanup in v1.0.4 which removes this type brittleness.


Delete old Terragrunt file handling

We don't use the .terragrunt file

Codecov Report

Merging #94 into master will decrease coverage by 0.12%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master      #94      +/-   ##
==========================================
- Coverage   55.68%   55.56%   -0.13%
==========================================
  Files          53       53
  Lines        4728     4710      -18
==========================================
- Hits         2633     2617      -16
+ Misses       1801     1800       -1
+ Partials      294      293       -1

Impacted Files
Coverage Δ

config/config_helpers.go
68.38% <100%> (ø)
:arrow_up:

config/config.go
71.94% <100%> (-1.04%)
:arrow_down:

configstack/module.go
61.02% <100%> (ø)
:arrow_up:

cli/args.go
91.54% <100%> (ø)
:arrow_up:

remote/remote_state.go
49.2% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 8be3b65...239dcad. Read the comment docs.


Working blocks sample attached - for 0.34

@kennykerr
blocks 0.34.zip

Looks like you ported my C++/WinRT composition sample. 😉
Feel free to contribute a PR to update the core_app sample.

I did try but when it comes to Pull Requests I am at None rather than Some.
On Tue, 5 Apr 2022 at 16:09, Kenny Kerr @.***> wrote:

Looks like you ported my C++/WinRT composition
https://github.com/microsoft/cppwinrt/blob/master/vsix/ProjectTemplates/VC/Windows Universal/CoreApp/App.cpp
sample. 😉
Feel free to contribute a PR to update the core_app
https://github.com/microsoft/windows-rs/tree/master/crates/samples/core_app
sample.
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/windows-rs/issues/1661#issuecomment-1088839502,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AXUV5Z2NBUOTQY2XUOTLDHDVDRJQXANCNFSM5STA3NKA
.
You are receiving this because you authored the thread.Message ID:
@.***>

Maybe core_app2 alongside core_app.
Seperately, would it make any sense to have an C++/WinRT sample referenced from here that boils XAML down to a component DLL that Rust apps could load?


first release?

I am reviewing the docs for the Phoenix guide, and I would like to link to the docs.
Is there any planned release in the near feature?
If note I can leave an internal note and update later the docs when the first version of this library is published.
Thank you.

You should use simply Phoenix.View in the guides and ExDoc will link to it accordingly (if it is a dependency or bundled internally). The next release will happen on Phoenix v1.6.

I did. Now it  is a (Git) dependency. ExDoc links to hexdocs.pm but the package hasn't been published. But if it is going to be published by the release of Phoenix 1.6 it is all good then.


Compare performance of only including leaf labels in the dataset.

[x] @dsmith111 Prepare cleaned_lens_output.json to only include leaf labels and not their parents. Ex. "label": ["passively_move_through/on_liquids"] instead of "label": ["move", "passive_movement", "passively_move_through/on_liquids"]
[x] @elkong rerun MATCH with this dataset.

Results of this study:
https://github.com/nasa-petal/PeTaL-labeller/tree/main/auto-labeler/MATCH#effect-of-using-leaf-labels-only


Ignore indirect dependency updates

🚩 Result: success
🧪 Preview: link
🕯 Lighthouse:

Audit

Desktop (home)

Desktop (page)

Mobile (home)

Mobile (page)

🖼 Screenshots:

Chrome
Firefox


pcap_next_ex can return other positive return codes to indicate success (e.g., with NFLOG)

I'm trying to use pcap's nflog input to analyze iptables-filtered packets. Here's the entirety of the code I'm using:
extern crate pcap;

use pcap::Device;

fn main() {
    let device = pcap::Device { name: "nflog:40".to_string(), desc: None };
    let mut cap = device.open().expect("Cannot open device");

    while let Ok(packet) = cap.next() {
        println!("{:?}", packet);
    }
}

Then I added an iptables rule to capture all outbound traffic from my test machine:
sudo iptables -A OUTPUT -j NFLOG --nflog-group 40

The netlink socket gets established correctly, because after the first packet is sent, my Rust program dies with the following:
thread '<main>' panicked at 'internal error: entered unreachable code', /home/vagrant/.cargo/registry/src/github.com-88ac128001ac3a9a/pcap-0.5.7/src/lib.rs:639

I added a println! to print out the return code from pcap_next_ex, and it's returning 9. Looking at the source code for my version of pcap (1.4.0-4.20130826git2dbcaa1, the Red Hat/CentOS 6 version), pcap_next_ex will return the result of pcap_read(), whose source code has the following comment:
        /*
         * Return codes for pcap_read() are:
         *   -  0: timeout
         *   - -1: error
         *   - -2: loop was broken out of with pcap_breakloop()
         *   - >1: OK
         * The first one ('0') conflicts with the return code of 0 from
         * pcap_offline_read() meaning "end of file".
        */

This contradicts the RETURN VALUE section of the pcap_next_ex man page (which says that OK will only return 1), but I'm more inclined to believe the source  than the man page.
I applied the following patch to this library and it seems to work:
diff --git a/src/lib.rs b/src/lib.rs
index 03fd0ae..fce71e2 100644
--- a/src/lib.rs
+++ b/src/lib.rs
@@ -613,7 +613,7 @@ impl<T: Activated + ?Sized> Capture<T> {
             let mut header: *mut raw::Struct_pcap_pkthdr = ptr::null_mut();
             let mut packet: *const libc::c_uchar = ptr::null();
             match raw::pcap_next_ex(*self.handle, &mut header, &mut packet) {
-                1 => {
+                i if i >= 1 => {
                     // packet was read without issue
                     Ok(Packet {
                         header: transmute(&*header),

Looks fine, but why does the source imply that the error code is strictly larger than 1 in the event of OK?

I agree that that line in the source is odd, but in practice, it always returns >= 1 for OK.


daemon-control-plane-kicker is trying to check a non-existent folder /var/snap/microk8s/1668/var/kubernetes/backend (script related to dqlite migration ??)

Please run microk8s inspect and attach the generated tarball to this issue.
inspection-report-20200916_103002.tar.gz
-> log file
microk8s.daemon-control-plane-kicker[38558]: chmod: cannot access '/var/snap/microk8s/1668/var/kubernetes/backend': No such file or directory

Hi @zzOzz,
Yes you are right, this output is because the node got updated to 1.19 but has not yet migrated to dqlite. I am sure it is not causing any issues apart from the message annoyance. I did put a PR up to fix this.
Also I see you have a long lasting deployment. In such cases it is recommended to follow a specific release channel [1] so you do not get affected by breaking changes introduced by either upstream or MicroK8s.
[1] https://microk8s.io/docs/setting-snap-channel


Append instead of override DefaultExcludesInProjectFolder

According to this documentation the following should work to exclude items:
<PropertyGroup>
  <DefaultExcludesInProjectFolder>$(DefaultExcludesInProjectFolder);**/myprefix*/**</DefaultExcludesInProjectFolder>
</PropertyGroup>

however Microsoft.NET.Sdk.DefaultItems.targets includes the following lines which overrides the already set value for DefaultExcludesInProjectFolder:
<DefaultExcludesInProjectFolder>$(DefaultItemExcludesInProjectFolder);**/.*/**</DefaultExcludesInProjectFolder>

It looks like the issue is that when the property name was changed from DefaultItemExcludesInProjectFolder to DefaultExcludesInProjectFolder in #806 the property used for the concatenation was not likewise updated.

Apparently github opens against fork and not upstream from the quick edit flow.


py spyder-notebook with nix spyder: Found duplicated packages in closure for dependency 'setuptools-scm':

let
  ref = "refs/tags/3.1.1" ; processMode = "mksh"; versionPy = "38"; testPkgPy = ""; testPkgNix = "";
  mach-nix = import (builtins.fetchGit {
    url = "https://github.com/DavHau/mach-nix/";
    ref = "${ref}" ;
  }) {
      #pkgs= import <nixpkgs>  {config= { allowUnfree = true; }; };
      python = "python${versionPy}";
};
  nixPkgs = import mach-nix.nixpkgs.path {} ;
  py = nixPkgs."python${versionPy}Packages" ;
in let
  envPy = mach-nix.mkPython rec {
    requirements =  ''
        ipython
        jupyterlab
        pandas

        spyder-notebook # Found duplicated packages in closure for dependency 'setuptools-scm':
        #spyder-terminal #
        #spyder-unittest

      '';

      packagesExtra = []
          ++ [
            # nixPkgs.spyder
          ]
      ;

  };
in
 # env =
  nixPkgs.buildEnv rec {
    name = "bEnvJL";
    paths =
        [ (envPy) ]
         ++ [
            nixPkgs.spyder
          ]
      ;
  }

Found duplicated packages in closure for dependency 'setuptools-scm':
  setuptools-scm 4.1.2 (/nix/store/mzxxiwvr1a65h3q5i2b2khbn7kv60762-python3.8-setuptools_scm-4.1.2/lib/python3.8/site-packages)
  setuptools-scm 4.1.2 (/nix/store/xkdxgqh405wzy6ggp0brpkgkjpz3ll4m-python3.8-setuptools-scm-4.1.2/lib/python3.8/site-packages)

Package duplicates found in closure, see above. Usually this happens if two packages depend on different version of the same dependency.
builder for '/nix/store/wwgsdlqhip493prn0qjp5mw7gia3jq9x-python3.8-black-20.8b1.drv' failed with exit code 1
cannot build derivation '/nix/store/6cplm4922yx7fv56dy354rbh0df91m6l-python3-3.8.6-env.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/f9rn4vm2km2iql96acpab76aiv24323p-bEnvJL.drv': 1 dependencies couldn't be built
error: build of '/nix/store/f9rn4vm2km2iql96acpab76aiv24323p-bEnvJL.drv' failed

I hit the same thing today, by simply pulling in black~=20.8b1.
Reproducer:
mach-nix on master [$?]
$ rm result && nix-build -A mach-nix && ./result/bin/mach-nix env -r <(echo black~=20.8b1) env && nix-shell env --run true
[...]
Finished executing pythonRemoveTestsDir
pythonCatchConflictsPhase
Found duplicated packages in closure for dependency 'setuptools-scm':
  setuptools-scm 4.1.2 (/nix/store/ngk96p2yjwf6l5221vh4665hk2d357qm-python3.7-setuptools_scm-4.1.2/lib/python3.7/site-packages)
  setuptools-scm 4.1.2 (/nix/store/ih5vp9l9jspwf6bskiy1yxspdssjb610-python3.7-setuptools-scm-4.1.2/lib/python3.7/site-packages)

Package duplicates found in closure, see above. Usually this happens if two packages depend on different version of the same dependency.
builder for '/nix/store/7vawjy753d44449rrbpgych3d7y741wm-python3.7-black-20.8b1.drv' failed with exit code 1

It works with black though, but that doesn't help in my case -- I need the latest.

This is resolved by 6473903da7e17b11f7c41f5729713bf46f84e6c2

It still fails for me:
$ cd mach-nix
$ git pull
...

$ git rev-parse HEAD
6473903da7e17b11f7c41f5729713bf46f84e6c2

$ rm -f result && nix-build -A mach-nix && ./result/bin/mach-nix env -r <(echo black~=20.8b1) env && nix-shell env --run true
...
pythonCatchConflictsPhase
Found duplicated packages in closure for dependency 'setuptools-scm':
  setuptools-scm 4.1.2 (/nix/store/ngk96p2yjwf6l5221vh4665hk2d357qm-python3.7-setuptools_scm-4.1.2/lib/python3.7/site-packages)
  setuptools-scm 4.1.2 (/nix/store/ih5vp9l9jspwf6bskiy1yxspdssjb610-python3.7-setuptools-scm-4.1.2/lib/python3.7/site-packages)

Package duplicates found in closure, see above. Usually this happens if two packages depend on different version of the same dependency.
builder for '/nix/store/7vawjy753d44449rrbpgych3d7y741wm-python3.7-black-20.8b1.drv' failed with exit code 1

@bjornfor The problem there is, whenever you use the mach-nix cmdline tool to initialize the env, it always defaults to the latest stable version, even if you use the cmdline tool from the master branch. Should we change this behaviour?

The problem there is, whenever you use the mach-nix cmdline tool to initialize the env, it always defaults to the latest stable version, even if you use the cmdline tool from the master branch. Should we change this behaviour?

Yes please! How else would I get your fix into my mach-nix CLI?
Btw, am I missing something here, what's the benefit of the current behaviour? (Why is it even a question? :smile: )

Btw, am I missing something here, what's the benefit of the current behaviour? (Why is it even a question? smile )

The reason is mostly, that I'm not sure how to implement that.
The problem is, that mach-nix needs to write some version reference of itself inside the lock.toml file inside the env. Currently the mach-nix tool just reads its own version via the ./mach-nix/VERSION file, queries the github api for the revision of that tag and uses that.
If mach-nix was always executed via flakes, we could use the revision from there, but I'm not sure if we want to force all users to use flakes.
With the current mechanism I could always change back the ./mach-nix/VERSION to master after doing a release. But then, if you are on any other branch, it will still initialize with the master branch of mach-nix.
Any ideas a welcome ;)

Maybe you can get the revision from builtins.fetchGit here, and then write the .rev attribute to a file in the output?
If that works, it'd have at least one downside: it'd break if I built from a local commit that doesn't exit upstream.
Alternatively, make releases very often :smile:

Maybe you can get the revision from builtins.fetchGit here, and then write the .rev attribute to a file in the output?

How do I know which revision to fetch via fetchGit?
How would you get the revision when installed from a tarball?

I changed the VERSION file to point to master for now.  see afa94cb61ce68fad8688ce4f32fc7095962aa191

How do I know which revision to fetch via fetchGit?

builtins.fetchGit ./. returns the revision, you don't need to pass it.

How would you get the revision when installed from a tarball?

Good question. I guess you don't, and would have to generate tarballs yourself :-/

I changed the VERSION file to point to master for now.

Thanks.


Remember preferred locale on signup/login

Upon login or Signup, get the NVP_PREFERRED_LOCALE. If it's not default(en) and changed, update the NVP and set that in Onyx, else set previously selected locale fetched from NVP in Onyx
Details

$ https://github.com/Expensify/App/issues/4999
Tests/QA Steps

From the login page select Espanyol and login
Make sure language is changed inside the app
From a new device or incognito window login into the app without changing anything(the login page by default will be in English)
Verify language inside the app is still Espanyol.

Tested On

[x] Web
[ ] Mobile Web
[x] Desktop
[x] iOS
[x] Android

Screenshots

Web

https://user-images.githubusercontent.com/32012005/131890508-f00d6a55-6d35-4c9c-aec6-97ef07e0b30b.mov
Mobile Web

Desktop
https://user-images.githubusercontent.com/32012005/131897469-0eaa6591-6645-451b-99a6-20353f17393a.mov
iOS
https://user-images.githubusercontent.com/32012005/131893107-33ebe664-a3e7-4fa3-a187-4633473f98c1.mp4
Android
https://user-images.githubusercontent.com/32012005/131896389-9e167899-5d8f-429a-8a27-9876ba124c62.mov

All yours @Luke9389

Updated

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by @Luke9389 in version: 1.0.95-2 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by @roryabraham in version: 1.0.96-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Refresh token

Hi, if i'm create pull request for refresh token, how long wait merge it?
First I want to update the schema for KeycloakToken like this acess_token: str, refresh_toke: str = None. Further, it is possible to make a separate handle.

Provide the PR with the corresponding Test and we can merge it in minutes 🙂

Merged


implement atomics

Atomics https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Atomics/

I decided to ask chatGPT about how to store and access shared memory in C. And it gave an answer.
Read chat

C seems also has stdatomic.h lib with functions:
atomic_int
atomic_flag
atomic_store
atomic_load
atomic_add
atomic_sub

I would use LLVM internals for it for example  https://llvm.org/docs/Atomics.html


Blazor hybrid BlazorWebView MudSelect problem

Bug type
Component
Component name
MudSelect
What happened?
In windows forms application with hybrid, when add a MudSelect component, when closing the app, does not release the dll of the app.
Expected behavior
In windows forms application with hybrid, when add a MudSelect component, when closing the app, does not release the dll of the app.
Reproduction link
https://try.mudblazor.com/snippet/QuGwYgbFqkxtwCbP
Reproduction steps
1.Create a hybrid project as explained here
2. https://docs.microsoft.com/en-us/aspnet/core/blazor/hybrid/?view=aspnetcore-6.0
3. Add a MudSelect component (after adding of coarse mublazor service etc)
4. Load app and close
5. Open task manager. The Thread is not closed
...
Relevant log output
No response
Version (bug)
6.0.10
Version (working)
No response
What browsers are you seeing the problem on?
Other
On what operating system are you experiencing the issue?
Windows
Pull Request

[ ] I would like to do a Pull Request

Code of Conduct

[X] I agree to follow this project's Code of Conduct

So the expected behavior is not to release dll?

No the expected behaviour is, when I close the app the dll to be released. Now the only way to release the dll is via Task Manager.
The only control I found until now has a problem is MudSelect other ex MudList it is ok and let the dll to be released
Στάλθηκε από την Αλληλογραφίαhttps://go.microsoft.com/fwlink/?LinkId=550986 για τα Windows
Από: Lukas @.>
Αποστολή: Δευτέρα, 13 Ιουνίου 2022 3:44 μμ
Προς: @.>
Κοιν.: Prokopis @.>; @.>
Θέμα: Re: [MudBlazor/MudBlazor] Blazor hybrid BlazorWebView MudSelect problem (Issue #4732)
So the expected behavior is not to release dll?
—
Reply to this email directly, view it on GitHubhttps://github.com/MudBlazor/MudBlazor/issues/4732#issuecomment-1153868157, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ALP3V25SQM6ZSDDO3F7543DVO4UJRANCNFSM5YQKR7SQ.
You are receiving this because you authored the thread.Message ID: @.***>

We use a lot of Blazor with WinForm and we haven't noticed such behavior yet.
Are you sure you are closing the application "properly" and not just closing the window?
We have placed an event on the WinForm window which terminates everything when the window is closed.
    ...
    FormClosed += OnFormClosed;
    ...

    private void OnFormClosed(object sender, FormClosedEventArgs e)
    {
        Environment.Exit(0);
    }

I have also experienced the same issue and reported it in the Discord some time ago.
I have the following in one of my Blazor components:
<MudSelect Margin="Margin.Dense" @bind-Value="UnitOfTime">
    <MudSelectItem Value="1" >Seconds</MudSelectItem>
    <MudSelectItem Value="60">Minutes</MudSelectItem>
    <MudSelectItem Value="3600">Hours</MudSelectItem>
</MudSelect>

The inclusion of this code prevents closing the application properly. Commenting out the MudSelect allows it to close properly.

Thanks a lot Olivier,
I just closed the window.
Now it seems ok, unload the dll.
Regards
Prokopis
From: Oliver H. @.>
Sent: 15 June 2022 12:23
To: MudBlazor/MudBlazor @.>
Cc: Prokopis Charalambous @.>; Author @.>
Subject: Re: [MudBlazor/MudBlazor] Blazor hybrid BlazorWebView MudSelect problem (Issue #4732)
We use a lot of Blazor with WinForm and we haven't noticed such behavior yet.
Are you sure you are closing the application "properly" and not just closing the window?
We have placed an event on the WinForm window which terminates everything when the window is closed.
...

FormClosed += OnFormClosed;

...

private void OnFormClosed(object sender, FormClosedEventArgs e)

{

    Environment.Exit(0);

}

—
Reply to this email directly, view it on GitHubhttps://github.com/MudBlazor/MudBlazor/issues/4732#issuecomment-1156224205, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ALP3V2Y4ZSGQW5FM46RQH73VPGOGTANCNFSM5YQKR7SQ.
You are receiving this because you authored the thread.Message ID: @.***>

I'm closing this issue.
I believe it was addressed either by https://github.com/MudBlazor/MudBlazor/pull/5367 or https://github.com/MudBlazor/MudBlazor/pull/7044
Let me know if the issue this exist.


tailscale: 1.22.2 -> 1.24.0

Description of changes
Update to new release: https://github.com/tailscale/tailscale/releases/tag/v1.24.0
Also adding myself as a maintainer since I joined Tailscale :)
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)
[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 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
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

/cc @danderson 4 maintainer review

nix-shell -p nixpkgs-review --run "nixpkgs-review pr 169896":
[xxx@xxx:~/projects/nixpkgs]$ NIX_PATH="nixpkgs=./" nix-shell -p nixpkgs-review --run "nixpkgs-review pr 169896"
<snip>
$ git -c fetch.prune=false fetch --no-tags --force https://github.com/NixOS/nixpkgs master:refs/nixpkgs-review/0 pull/169896/head:refs/nixpkgs-review/1
From https://github.com/NixOS/nixpkgs
   9dc12546ab3..79d81ff4a80  master                -> refs/nixpkgs-review/0
   df6d1ee32ac..c7b93bcdd18  refs/pull/169896/head -> refs/nixpkgs-review/1
$ git worktree add /home/xxx/.cache/nixpkgs-review/pr-169896/nixpkgs 79d81ff4a80deddca317e46faab31d9d6df88cd4
Preparing worktree (detached HEAD 79d81ff4a80)
Updating files: 100% (30254/30254), done.
HEAD is now at 79d81ff4a80 Merge pull request #169261 from r-ryantm/auto-update/python3.10-vispy
$ nix-env --option system x86_64-linux -f /home/xxx/.cache/nixpkgs-review/pr-169896/nixpkgs -qaP --xml --out-path --show-trace
$ git merge --no-commit --no-ff c7b93bcdd1899399f92f9e5eb1f1fbf8b38e62c0
Automatic merge went well; stopped before committing as requested
$ nix-env --option system x86_64-linux -f /home/xxx/.cache/nixpkgs-review/pr-169896/nixpkgs -qaP --xml --out-path --show-trace --meta
1 package updated:
tailscale (1.22.2 → 1.24.0)

warning: ignoring the user-specified setting 'system', because it is a restricted setting and you are not a trusted user
$ nix --experimental-features nix-command build --no-link --keep-going --option build-use-sandbox relaxed -f /home/xxx/.cache/nixpkgs-review/pr-169896/build.nix
warning: ignoring the user-specified setting 'sandbox', because it is a restricted setting and you are not a trusted user
building '/nix/store/xjahmkv7n3g1c8qpj4ijx4sykw8my6p3-review-shell.drv'...

Link to currently reviewing PR:
https://github.com/NixOS/nixpkgs/pull/169896

1 package built:
tailscale

$ nix-shell /home/xxx/.cache/nixpkgs-review/pr-169896/shell.nix
[nix-shell:~/.cache/nixpkgs-review/pr-169896]$

@danderson @twitchyliquid64 Can we backport to 21.11 and other releases? TIA

@epk to do that we would need to backport all the Go 1.18 machinery or bring in tailscale-go - not sure if either of those would be palatable to upstream.

Yeah, Tailscale adopts new Go toolchains right away, so unless the Go toolchain team's willing to backport 1.18, I think this'd be a case of waiting for 22.xx, or blending the unstable tailscale package into your 21.11 install (which is what I do, fwiw).

Sorry I wasn't aware of the dependency between Go versions and  NixOS releases.
I copied Dave's older flake-less unstable override for tailscale and it works.


Speed regression

Somewhere between 4756dcee and 967674e9, I made changes that had significant speed impacts :( The sars-cov-2 dataset went down from 100 sequences/sec to < 1 seq/sec 😢 going to walk back those changes to identify the problem.

The culprit is b0961738, let this be a lesson to myself to not make such big changes at a time.
https://github.com/phac-nml/rebar/compare/c644c9730009..b0961738
b0961738 changes:

Wildcarding in designated parents.
More thorough compare_parents validation for parent-child relationships.
Removing min_conflict option for best hypothesis.
KnockoutRecombinant Hypothesis

It's purely the new KnockoutRecombinant hypothesis! Well that is very curious, but luckily the easiest to undo and troubleshoot.


Remove trailing empty line in copyright comment (part 18)

The next part of https://github.com/helidon-io/helidon/pull/5324 .

/trigger

Can it be re-triggered , please ?

Done.


Maven Build Security Check Exceptions

When I compile my maven project which has apexcharts dependency (0.3.1), the following WARNING messages appears on the console:
[WARNING] Could not transfer metadata org.webjars.npm:svg.js/maven-metadata.xml from/to Vaadin prereleases (https://maven.vaadin.com/vaadin-prereleases): PKIX path validation failed: java.security.cert.CertPathValidatorException: validity check failed
[INFO] Downloading from : https://maven.vaadin.com/vaadin-prereleases/org/webjars/npm/promise-polyfill/maven-metadata.xml
[WARNING] Could not transfer metadata org.webjars.npm:promise-polyfill/maven-metadata.xml from/to Vaadin prereleases (https://maven.vaadin.com/vaadin-prereleases): PKIX path validation failed: java.security.cert.CertPathValidatorException: validity check failed
[INFO] Downloading from : https://maven.vaadin.com/vaadin-prereleases/org/webjars/npm/svg.resize.js/maven-metadata.xml
[WARNING] Could not transfer metadata org.webjars.npm:svg.resize.js/maven-metadata.xml from/to Vaadin prereleases (https://maven.vaadin.com/vaadin-prereleases): PKIX path validation failed: java.security.cert.CertPathValidatorException: validity check failed
[WARNING] Failure to transfer org.webjars.npm:svg.js/maven-metadata.xml from https://maven.vaadin.com/vaadin-prereleases was cached in the local repository, resolution will not be reattempted until the update interval of Vaadin prereleases has elapsed or updates are forced. Original error: Could not transfer metadata org.webjars.npm:svg.js/maven-metadata.xml from/to Vaadin prereleases (https://maven.vaadin.com/vaadin-prereleases): PKIX path validation failed: java.security.cert.CertPathValidatorException: validity check failed
[INFO] Downloading from : https://maven.vaadin.com/vaadin-prereleases/org/webjars/npm/svg.select.js/maven-metadata.xml
[WARNING] Could not transfer metadata org.webjars.npm:svg.select.js/maven-metadata.xml from/to Vaadin prereleases (https://maven.vaadin.com/vaadin-prereleases): PKIX path validation failed: java.security.cert.CertPathValidatorException: validity check failed
[WARNING] Failure to transfer org.webjars.npm:svg.js/maven-metadata.xml from https://maven.vaadin.com/vaadin-prereleases was cached in the local repository, resolution will not be reattempted until the update interval of Vaadin prereleases has elapsed or updates are forced. Original error: Could not transfer metadata org.webjars.npm:svg.js/maven-metadata.xml from/to Vaadin prereleases (https://maven.vaadin.com/vaadin-prereleases): PKIX path validation failed: java.security.cert.CertPathValidatorException: validity check failed
[INFO] Downloading from : https://maven.vaadin.com/vaadin-prereleases/org/webjars/npm/svg.pathmorphing.js/maven-metadata.xml
[WARNING] Could not transfer metadata org.webjars.npm:svg.pathmorphing.js/maven-metadata.xml from/to Vaadin prereleases (https://maven.vaadin.com/vaadin-prereleases): PKIX path validation failed: java.security.cert.CertPathValidatorException: validity check failed
[WARNING] Failure to transfer org.webjars.npm:svg.js/maven-metadata.xml from https://maven.vaadin.com/vaadin-prereleases was cached in the local repository, resolution will not be reattempted until the update interval of Vaadin prereleases has elapsed or updates are forced. Original error: Could not transfer metadata org.webjars.npm:svg.js/maven-metadata.xml from/to Vaadin prereleases (https://maven.vaadin.com/vaadin-prereleases): PKIX path validation failed: java.security.cert.CertPathValidatorException: validity check failed
[INFO] Downloading from : https://maven.vaadin.com/vaadin-prereleases/org/webjars/npm/svg.filter.js/maven-metadata.xml
[WARNING] Could not transfer metadata org.webjars.npm:svg.filter.js/maven-metadata.xml from/to Vaadin prereleases (https://maven.vaadin.com/vaadin-prereleases): PKIX path validation failed: java.security.cert.CertPathValidatorException: validity check failed
[INFO] Downloading from : https://maven.vaadin.com/vaadin-prereleases/org/webjars/npm/svg.draggable.js/maven-metadata.xml
[WARNING] Could not transfer metadata org.webjars.npm:svg.draggable.js/maven-metadata.xml from/to Vaadin prereleases (https://maven.vaadin.com/vaadin-prereleases): PKIX path validation failed: java.security.cert.CertPathValidatorException: validity check failed
[WARNING] Failure to transfer org.webjars.npm:svg.js/maven-metadata.xml from https://maven.vaadin.com/vaadin-prereleases was cached in the local repository, resolution will not be reattempted until the update interval of Vaadin prereleases has elapsed or updates are forced. Original error: Could not transfer metadata org.webjars.npm:svg.js/maven-metadata.xml from/to Vaadin prereleases (https://maven.vaadin.com/vaadin-prereleases): PKIX path validation failed: java.security.cert.CertPathValidatorException: validity check failed
[INFO] Downloading from : https://maven.vaadin.com/vaadin-prereleases/org/webjars/npm/svg.easing.js/maven-metadata.xml
[WARNING] Could not transfer metadata org.webjars.npm:svg.easing.js/maven-metadata.xml from/to Vaadin prereleases (https://maven.vaadin.com/vaadin-prereleases): PKIX path validation failed: java.security.cert.CertPathValidatorException: validity check failed
[WARNING] Failure to transfer org.webjars.npm:svg.js/maven-metadata.xml from https://maven.vaadin.com/vaadin-prereleases was cached in the local repository, resolution will not be reattempted until the update interval of Vaadin prereleases has elapsed or updates are forced. Original error: Could not transfer metadata org.webjars.npm:svg.js/maven-metadata.xml from/to Vaadin prereleases (https://maven.vaadin.com/vaadin-prereleases): PKIX path validation failed: java.security.cert.CertPathValidatorException: validity check failed
[INFO] Downloading from : https://maven.vaadin.com/vaadin-prereleases/org/webjars/bowergithub/polymerelements/iron-checked-element-behavior/maven-metadata.xml
[WARNING] Could not transfer metadata org.webjars.bowergithub.polymerelements:iron-checked-element-behavior/maven-metadata.xml from/to Vaadin prereleases (https://maven.vaadin.com/vaadin-prereleases): PKIX path validation failed: java.security.cert.CertPathValidatorException: validity check failed
[INFO] Downloading from : https://maven.vaadin.com/vaadin-prereleases/org/webjars/bowergithub/polymerelements/iron-validatable-behavior/maven-metadata.xml
[WARNING] Could not transfer metadata org.webjars.bowergithub.polymerelements:iron-validatable-behavior/maven-metadata.xml from/to Vaadin prereleases (https://maven.vaadin.com/vaadin-prereleases): PKIX path validation failed: java.security.cert.CertPathValidatorException: validity check failed
[INFO] Downloading from : https://maven.vaadin.com/vaadin-prereleases/org/webjars/bowergithub/polymerelements/iron-form-element-behavior/maven-metadata.xml
[WARNING] Could not transfer metadata org.webjars.bowergithub.polymerelements:iron-form-element-behavior/maven-metadata.xml from/to Vaadin prereleases (https://maven.vaadin.com/vaadin-prereleases): PKIX path validation failed: java.security.cert.CertPathValidatorException: validity check failed
[WARNING] Failure to transfer org.webjars.bowergithub.polymerelements:iron-validatable-behavior/maven-metadata.xml from https://maven.vaadin.com/vaadin-prereleases was cached in the local repository, resolution will not be reattempted until the update interval of Vaadin prereleases has elapsed or updates are forced. Original error: Could not transfer metadata org.webjars.bowergithub.polymerelements:iron-validatable-behavior/maven-metadata.xml from/to Vaadin prereleases (https://maven.vaadin.com/vaadin-prereleases): PKIX path validation failed: java.security.cert.CertPathValidatorException: validity check failed
[WARNING] Failure to transfer org.webjars.bowergithub.polymerelements:iron-form-element-behavior/maven-metadata.xml from https://maven.vaadin.com/vaadin-prereleases was cached in the local repository, resolution will not be reattempted until the update interval of Vaadin prereleases has elapsed or updates are forced. Original error: Could not transfer metadata org.webjars.bowergithub.polymerelements:iron-form-element-behavior/maven-metadata.xml from/to Vaadin prereleases (https://maven.vaadin.com/vaadin-prereleases): PKIX path validation failed: java.security.cert.CertPathValidatorException: validity check failed
[WARNING] Failure to transfer org.webjars.bowergithub.polymerelements:iron-validatable-behavior/maven-metadata.xml from https://maven.vaadin.com/vaadin-prereleases was cached in the local repository, resolution will not be reattempted until the update interval of Vaadin prereleases has elapsed or updates are forced. Original error: Could not transfer metadata org.webjars.bowergithub.polymerelements:iron-validatable-behavior/maven-metadata.xml from/to Vaadin prereleases (https://maven.vaadin.com/vaadin-prereleases): PKIX path validation failed: java.security.cert.CertPathValidatorException: validity check failed
[WARNING] Failure to transfer org.webjars.bowergithub.polymerelements:iron-form-element-behavior/maven-metadata.xml from https://maven.vaadin.com/vaadin-prereleases was cached in the local repository, resolution will not be reattempted until the update interval of Vaadin prereleases has elapsed or updates are forced. Original error: Could not transfer metadata org.webjars.bowergithub.polymerelements:iron-form-element-behavior/maven-metadata.xml from/to Vaadin prereleases (https://maven.vaadin.com/vaadin-prereleases): PKIX path validation failed: java.security.cert.CertPathValidatorException: validity check failed
[INFO] Downloading from : https://maven.vaadin.com/vaadin-prereleases/org/webjars/bowergithub/polymerelements/paper-behaviors/maven-metadata.xml
[WARNING] Could not transfer metadata org.webjars.bowergithub.polymerelements:paper-behaviors/maven-metadata.xml from/to Vaadin prereleases (https://maven.vaadin.com/vaadin-prereleases): PKIX path validation failed: java.security.cert.CertPathValidatorException: validity check failed
[INFO] Downloading from : https://maven.vaadin.com/vaadin-prereleases/org/webjars/bowergithub/polymerelements/iron-behaviors/maven-metadata.xml
[WARNING] Could not transfer metadata org.webjars.bowergithub.polymerelements:iron-behaviors/maven-metadata.xml from/to Vaadin prereleases (https://maven.vaadin.com/vaadin-prereleases): PKIX path validation failed: java.security.cert.CertPathValidatorException: validity check failed
[WARNING] Failure to transfer org.webjars.bowergithub.polymerelements:iron-checked-element-behavior/maven-metadata.xml from https://maven.vaadin.com/vaadin-prereleases was cached in the local repository, resolution will not be reattempted until the update interval of Vaadin prereleases has elapsed or updates are forced. Original error: Could not transfer metadata org.webjars.bowergithub.polymerelements:iron-checked-element-behavior/maven-metadata.xml from/to Vaadin prereleases (https://maven.vaadin.com/vaadin-prereleases): PKIX path validation failed: java.security.cert.CertPathValidatorException: validity check failed
[INFO] Downloading from : https://maven.vaadin.com/vaadin-prereleases/org/webjars/bowergithub/polymerelements/paper-ripple/maven-metadata.xml
[WARNING] Could not transfer metadata org.webjars.bowergithub.polymerelements:paper-ripple/maven-metadata.xml from/to Vaadin prereleases (https://maven.vaadin.com/vaadin-prereleases): PKIX path validation failed: java.security.cert.CertPathValidatorException: validity check failed
[WARNING] Failure to transfer org.webjars.bowergithub.polymerelements:iron-behaviors/maven-metadata.xml from https://maven.vaadin.com/vaadin-prereleases was cached in the local repository, resolution will not be reattempted until the update interval of Vaadin prereleases has elapsed or updates are forced. Original error: Could not transfer metadata org.webjars.bowergithub.polymerelements:iron-behaviors/maven-metadata.xml from/to Vaadin prereleases (https://maven.vaadin.com/vaadin-prereleases): PKIX path validation failed: java.security.cert.CertPathValidatorException: validity check failed
[WARNING] Failure to transfer org.webjars.bowergithub.polymerelements:iron-checked-element-behavior/maven-metadata.xml from https://maven.vaadin.com/vaadin-prereleases was cached in the local repository, resolution will not be reattempted until the update interval of Vaadin prereleases has elapsed or updates are forced. Original error: Could not transfer metadata org.webjars.bowergithub.polymerelements:iron-checked-element-behavior/maven-metadata.xml from/to Vaadin prereleases (https://maven.vaadin.com/vaadin-prereleases): PKIX path validation failed: java.security.cert.CertPathValidatorException: validity check failed
[WARNING] Failure to transfer org.webjars.bowergithub.polymerelements:paper-ripple/maven-metadata.xml from https://maven.vaadin.com/vaadin-prereleases was cached in the local repository, resolution will not be reattempted until the update interval of Vaadin prereleases has elapsed or updates are forced. Original error: Could not transfer metadata org.webjars.bowergithub.polymerelements:paper-ripple/maven-metadata.xml from/to Vaadin prereleases (https://maven.vaadin.com/vaadin-prereleases): PKIX path validation failed: java.security.cert.CertPathValidatorException: validity check failed
[WARNING] Failure to transfer org.webjars.bowergithub.polymerelements:iron-behaviors/maven-metadata.xml from https://maven.vaadin.com/vaadin-prereleases was cached in the local repository, resolution will not be reattempted until the update interval of Vaadin prereleases has elapsed or updates are forced. Original error: Could not transfer metadata org.webjars.bowergithub.polymerelements:iron-behaviors/maven-metadata.xml from/to Vaadin prereleases (https://maven.vaadin.com/vaadin-prereleases): PKIX path validation failed: java.security.cert.CertPathValidatorException: validity check failed
[WARNING] Failure to transfer org.webjars.bowergithub.polymerelements:paper-ripple/maven-metadata.xml from https://maven.vaadin.com/vaadin-prereleases was cached in the local repository, resolution will not be reattempted until the update interval of Vaadin prereleases has elapsed or updates are forced. Original error: Could not transfer metadata org.webjars.bowergithub.polymerelements:paper-ripple/maven-metadata.xml from/to Vaadin prereleases (https://maven.vaadin.com/vaadin-prereleases): PKIX path validation failed: java.security.cert.CertPathValidatorException: validity check failed
[INFO] Downloading from : https://maven.vaadin.com/vaadin-prereleases/org/webjars/bowergithub/polymerelements/paper-styles/maven-metadata.xml
[WARNING] Could not transfer metadata org.webjars.bowergithub.polymerelements:paper-styles/maven-metadata.xml from/to Vaadin prereleases (https://maven.vaadin.com/vaadin-prereleases): PKIX path validation failed: java.security.cert.CertPathValidatorException: validity check failed
[INFO] Downloading from : https://maven.vaadin.com/vaadin-prereleases/org/webjars/bowergithub/polymerelements/font-roboto/maven-metadata.xml
[WARNING] Could not transfer metadata org.webjars.bowergithub.polymerelements:font-roboto/maven-metadata.xml from/to Vaadin prereleases (https://maven.vaadin.com/vaadin-prereleases): PKIX path validation failed: java.security.cert.CertPathValidatorException: validity check failed

Not sure if this is actually an addon issue or of your maven setup 🤔. try adding the -X switch to the Maven goal.

@appreciated I am using default maven tool of Eclipse. It was not about my Eclipse or Maven setup. I came accoss this problem after adding apexcharts dependency (0.3.1). But now the problem disappeared. I do not take this exception anymore.
May be the problem a temporary problem and was about pre-release repository of vaadin...
You can close the issue...


NIFI-5282: GCPProcessor with HTTP Proxy with Authentication

NOTE for reviewer
This PR contains two commits. The 1st one is submitted by @jugi92 via #2943 . I have reviewed the PR and updated few points. Please refer #2943 comments I posted for where I have changed. With those changes, I'd give +1 to #2943, so the 1st comment has 'this closes' comment.
The 2nd commit includes refactoring mentioned above, and also adds ProxyConfiguration support on top of the 1st commit.
Please DO NOT squash these two commits when merging, in order to keep @jugi92 contribution. Thanks!
Some Docker commands to run Squid proxy server
# Start a Squid container
docker run -d -p 3128:3128 --name squid salrashid123/squidproxy tail -f /dev/null
# Login to the container
docker exec -it squid bash
# Start proxy without auth
squid/sbin/squid -s -f squid.conf.forward
# or with basic auth
squid/sbin/squid -s -f squid.conf.basicauth
# Stop
squid/sbin/squid -k shutdown

Thank you for submitting a contribution to Apache NiFi.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[x] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[x] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[x] Has your PR been rebased against the latest commit within the target branch (typically master)?

[ ] Is your initial contribution a single, squashed commit?

For code changes:

[x] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[ ] Have you written or updated unit tests to verify your changes?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[x] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[x] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.

Reviewing...

Thanks @ijokarumawak! This has been merged to master.


Icons not showing up for extra plugins

Hi
I have added extra plugins in IvoryCKEditorBundle, it's integrated successfully but their icons do not show up.
Output is:

Here is my form:
public function buildForm(FormBuilderInterface $builder, array $options)
    {
        $builder
            ->add('content', CKEditorType::class, array(
                'label' => 'Add Content',
                'config' => array(
                    'filebrowserBrowseRoute' => 'elfinder',
                    'filebrowserBrowseRouteParameters' => array(
                        'instance' => 'default',
                        'homeFolder' => ''
                    )
                )
            ))
            ->add('file', FileType::class, array(
                'label' => 'Add Image',
                'required' => false,
                'attr' => array('class' => 'img-file')
            ));
    }

Here is my config.yml:
ivory_ck_editor:
    default_config: my_config
    configs:
        my_config:
            toolbar: full
            filebrowserBrowseRoute: elfinder
            filebrowserBrowseRouteParameters: []
        extraPlugins: ["mathjax, eqneditor, widget"]
    plugins:
        mathjax:
            path: "/bundles/admin/mathjax/"
            filename: "plugin.js"
        eqneditor:
            path: "bundles/admin/eqneditor"
            filename: "plugin.js"
        widget:
            path: "bundles/admin/widget"
            filename: "plugin.js"
fm_elfinder:
    instances:
        default:
            locale: %locale% # defaults to current request locale
            editor: ckeditor # other options are tinymce, tinymce4, fm_tinymce,  form, simple, custom
            #editor_template: set custom template for your editor # default null
            #path_prefix: / # for setting custom assets path prefix, useful for non vhost configurations, i.e. http://<IP_ADDRESS>/mysite/
            #fullscreen: true|false # defaults true, applies to simple and ckeditor editors
            #theme: smoothness # jquery theme, default is 'smoothness'
            include_assets: true # disable if you want to handle loading of the javascript and css assets yourself
            #visible_mime_types: ['image/png', 'image/jpg', 'image/jpeg'] # only show these mime types, defaults to show all
            connector:
                #debug: true|false # defaults to false
                roots:       # at least one root must be defined
                    uploads:
                        #show_hidden: true|false # defaults to false, hide files that
                        driver: LocalFileSystem
                        path: uploads
                        upload_allow: ['image/png', 'image/jpg', 'image/jpeg']
                        upload_deny: ['all']
                        upload_max_size: 2M
                        #attributes: example of setting attributes permission
                        #    - { pattern: '/(.*?)/', read: true, write: false, locked: true }

@egeloen Can you help with it?

AFAIR, the problem seems an identation one:
ivory_ck_editor:
    default_config: my_config
    configs:
        my_config:
            toolbar: full
            filebrowserBrowseRoute: elfinder
            filebrowserBrowseRouteParameters: []
            extraPlugins: ["mathjax, eqneditor, widget"] # <- Here the indentation seems wrong in your example

@napestershine Can you try to fix the indentation as I pointed out and give me some feedback? :)

Yes fixed, thanks so much @egeloen  :+1:


Load custom java classes

Magic to load classes contained in a directory. That would simplify some scenarios for education.

This already works using %classpath magic. It does not load specific classes, but the compiled classes compiled in a directory.


TypeError: Cannot include body with GET/HEAD request

trying to figure out this message
I get it for all my GET requests
here's my request:
GET /api/v2/mng-ui/external-connections HTTP/1.1
Host: <IP_ADDRESS>:8080
Connection: keep-alive
Pragma: no-cache
Cache-Control: no-cache
X-CSRF-Token: 64a4b0b9-6fe4-4bad-95d1-1b2dabdf55d4
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.90 Safari/537.36
Content-Type: application/json; charset=UTF-8
Accept: /
Referer: http://<IP_ADDRESS>:8080/console/
Accept-Encoding: gzip, deflate, br
Accept-Language: en-US,en;q=0.8,he;q=0.6
Cookie: tsAdminSessionId=92ec2331-b914-42a4-a27c-828773dcae3c
zombie XHR readystatechange http://<IP_ADDRESS>:8080/api/v2/mng-ui/external-connections +167ms
TypeError: Cannot include body with GET/HEAD request
at new Request (/Users/drorrash/work/projects/integration-tests/node_modules/zombie/lib/fetch.js:452:56)
at XMLHttpRequest.send (/Users/drorrash/work/projects/integration-tests/node_modules/zombie/lib/xhr.js:131:21)
at http://<IP_ADDRESS>:8080/console/vendor.475d3bbc82ca28b5a4bc.js:6:50377
at $ (http://<IP_ADDRESS>:8080/console/vendor.475d3bbc82ca28b5a4bc.js:6:48317)
at c (http://<IP_ADDRESS>:8080/console/vendor.475d3bbc82ca28b5a4bc.js:6:46960)
at s (http://<IP_ADDRESS>:8080/console/vendor.475d3bbc82ca28b5a4bc.js:6:64875)
at http://<IP_ADDRESS>:8080/console/vendor.475d3bbc82ca28b5a4bc.js:6:65047
at p.$eval (http://<IP_ADDRESS>:8080/console/vendor.475d3bbc82ca28b5a4bc.js:6:72548)
at p.$digest (http://<IP_ADDRESS>:8080/console/vendor.475d3bbc82ca28b5a4bc.js:6:71056)
at t.$apply (http://<IP_ADDRESS>:8080/console/vendor.475d3bbc82ca28b5a4bc.js:6:72831)
at core.(anonymous function). (http://<IP_ADDRESS>:8080/console/vendor.475d3bbc82ca28b5a4bc.js:6:139307)
at Je (http://<IP_ADDRESS>:8080/console/vendor.475d3bbc82ca28b5a4bc.js:6:15273)
at core.(anonymous function).n (http://<IP_ADDRESS>:8080/console/vendor.475d3bbc82ca28b5a4bc.js:6:15220)
at invokeEventListeners (/Users/drorrash/work/projects/integration-tests/node_modules/jsdom/lib/jsdom/living/events/EventTarget-impl.js:195:25)
at EventTargetImpl._dispatch (/Users/drorrash/work/projects/integration-tests/node_modules/jsdom/lib/jsdom/living/events/EventTarget-impl.js:126:9)
at EventTargetImpl.dispatchEvent (/Users/drorrash/work/projects/integration-tests/node_modules/jsdom/lib/jsdom/living/events/EventTarget-impl.js:87:17) undefined

I think I figured it out,
why does GET requests with an empty body are rejected?
referring to line 451 @fetch.js
if (init && init.body) {
if (method === 'GET' || method === 'HEAD') throw new TypeError('Cannot include body with GET/HEAD request');
bodyInit = init.body;
}


Bulk commit: Implemented more blocks

Implemented:

Sandstone
SandstoneCut
SandstoneChiseled
SandstoneSmooth
Sand
Gravel
Flint (Item)

Would also be nice if you could implement gravity to these blocks within this pull request

Could you please make sure the names of the file match the type names? For example, cut_sandstone rather than sandstone_cut

Closing this PR as stale. Most of these features were already implemented and there's conflicts.


JSON.parse(window.top.name) can cause all JS to stop executing

We just had a major issue on the site due to this bug.
in the 'window-name' adapter, there is a call:
data = window.top.name ? JSON.parse(window.top.name) : {}
when the window.top.name is not valid json, this will throw an exception which causes all JS loaded after this to fail.
fix is:
var data;
try {
data = window.top.name ? JSON.parse(window.top.name) : {}
} catch(e){
data = {};
}

So, i assume this is never going to be fixed, right?

This was fixed over 3 years ago without an update to this bug.

mark


Add the OPA CloudFormation Hook

Description of changes:

Add the OPA CloudFormation Hook
Add section for samples including hooks

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Signed-off-by: Anders Eknert<EMAIL_ADDRESS>

Thanks Matteo! Done 👍


Implemented query search for client

Summary
Implemented query search for client

[x] Implemented Search
[x] Added test in test_backend

Details and comments
Currently, uses trial.name.find(query) to filter out all trials that contain the substring 'query' in their names.

@AnsahMohammad can you resolve conflict?

@IceKhan13 extended the query to include search on tags and description.

Okay, fixed that 😄

tests are failing :)

@IceKhan13 Fixed tests! There was a typo!


tiffbpl is too small

I try train myself data. After I use jTessBoxEditor to generate tiff, I use the commind "
tesseract /Users/tmac/Desktop/chen2.tif chen -l eng  batch.nochop makebox", and remind "Error in pixReadFromTiffStream: bad tiff file: tiffbpl is too small" , what is the matter ???

This is leptonica error we can not do nothing with it. Report it on right place.
You did not share tiff file - nobody can help you... (Is generated tiff file correct? did you use the same lilbtiff version for creating and reading file?)


Add option to strip path prefix when uploading files.

See issue: https://issues.jenkins-ci.org/browse/JENKINS-23670

Thank you for a pull request! Please check this document for how the Jenkins project handles pull requests

Hi, @astroilov I've added some comments.

Comments addressed in latest commit.

LGTM, feel free to merge


[BUG] Validation Error when using response_model and Dynamic Key type

Describe the bug
Hi guys, seem that when using a Dynamic Key type of model with  response_model will raise ValidationError on the server side and returns 500 Internal Server Error to the client.
I have the following example code, I believe I am using it correctly?
could this be relater to #911 ?
I also realize I can substitute response_model=PetsByName with response_model=Dict[str, str], but with the later I am not able to include an example in schema_extra, is there other way to do so? many thanks!
To Reproduce
Steps to reproduce the behavior with a minimum self-contained file.
Replace each part with your own scenario:

Create a file with:

main.py
from pydantic import BaseModel
from fastapi import FastAPI
from typing import Dict

app = FastAPI()

class PetsByName(BaseModel):
    __root__: Dict[str, str]

    class Config:
        schema_extra = {
                'example': {'Otis': 'dog', 'Milo': 'cat'}
            }

@app.get("/animal/", response_model=PetsByName)
async def animal():
    return {'Otis': 'dog', 'Milo': 'cat'}

Using curl to test the endpoint:

$ curl -L localhost:8000/animal
Internal Server Error

It returns a JSON with Internal Server Error.

But I expected it to return {'Otis': 'dog', 'Milo': 'cat'}.

Terminal output of the server:

...
  File "/home/merc/.virtualenvs/py38/lib/python3.8/site-packages/starlette/routing.py", line 41, in app
    response = await func(request)
  File "/home/merc/.virtualenvs/py38/lib/python3.8/site-packages/fastapi/routing.py", line 140, in app
    response_data = await serialize_response(
  File "/home/merc/.virtualenvs/py38/lib/python3.8/site-packages/fastapi/routing.py", line 78, in serialize_response
    raise ValidationError(errors, field.type_)
pydantic.error_wrappers.ValidationError: 1 validation error for PetsByName
response -> __root__
  field required (type=value_error.missing)

Expected behavior
Add a clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Environment

OS: Ubuntu 19.04
FastAPI Version: 0.48.0
Python version: 3.8.1

Additional context
SwaggerUI renders the PetsByName model along with the example correctly, no issue there.

After reading #911 it definitely is related to that. Will close this one and move myself over to #911 for discussion.  Many thanks!

Thanks for reporting back and closing the issue. Let's continue on the other one. :+1:


AdoraWash Energy Total randomly set to 0

Discussed in https://github.com/siku2/hass-vzug/discussions/41

Originally posted by danistst February  7, 2024
The "Energy Total" sensor of my Adora Wash V4000 is randomly set to 0. Later on, it picks up where it had been before. This messes up my Energy Dashboard.
I can also see in the logbook that "Waschmaschine Gesamtverbrauch" becomes unavailable sometimes. May this is related.

Just realized that this is the same as #40
I close this issue and comment on #40


support library-v4:28+ styles errors

@see https://github.com/crosswalk-project/cordova-plugin-crosswalk-webview/issues/205 for more info.

Thanks for the solution @Scuttman! It works perfectly here. I have come up with an extended solution so it works without having to modify build artifacts using hooks. To hot fix any project:
Create a ./build-extras.gradle file in the root of your project with the fix mentioned above:
configurations.all {
resolutionStrategy {
force 'com.android.support:support-v4:27.1.0'
}
}
Create a ./hooks/copy-build-extras-gradle.js hook with the following code to copy the file into the android project
var fs = require('fs');
var path = require('path');
var rootdir = process.env.PWD;
var platformAndroidPath = '/platforms/android/';
var srcFile = path.join(rootdir, 'build-extras.gradle');
var destFile = path.join(rootdir, platformAndroidPath, 'build-extras.gradle');
var destDir = path.dirname(destFile);
if (fs.existsSync(srcFile) && fs.existsSync(destDir)) {
fs.createReadStream(srcFile).pipe(fs.createWriteStream(destFile));
} else {
throw new Error('Unable to copy build-extras.gradle');
}
Add the hook to config.xml within the  tag:
...

Build your project like normal!

test successfully on Mac try to close the issue

also successfully on my Win8.1    :)


Array of structured buffers fails for GLSL based targets

The following code when compiling to glsl based targets (including spir-v) doesn't work...
RWStructuredBuffer<int> outputBuffer[3];
Buffer<float> anotherBuffer;
RWStructuredBuffer<int> outputBuffer2[2];

void writeArray(inout float3 a[4])
{
   a[0] = float3(1, 1, 1);
   a[1] = float3(1, 1, 1);
   a[2] = float3(1, 1, 1);
   a[3] = float3(1, 1, 1);
}
[numthreads(4, 1, 1)]
void computeMain(uint3 dispatchThreadID : SV_DispatchThreadID)
{
   float3 b[4];
   writeArray(b);
   b[0] += anotherBuffer[dispatchThreadID.x];

   int index = b[0].y > 0 ? 1 : 0;
   outputBuffer[index][dispatchThreadID.x] = b[0].x;
   outputBuffer2[index][dispatchThreadID.x] = b[0].x + 1;
}

An error is produced 'left of '[' is not of type array, matrix, or vector ' for line 22.
The problem is that RWStructuredBuffer outputBuffer[3]; being output as
layout(std430) buffer _S1 {
   int outputBuffer_0[];
};

And then accessed as (((outputBuffer_0[index_0]))[(_S3.x)]) = _S7; - one level of arrayness has been lost so the indexing can't work.
Tim points out...
In emit.cpp:
            // When outputting GLSL, we need to transform any declaration of
            // a `*StructuredBuffer<T>` into an ordinary `buffer` declaration.
            if( auto structuredBufferType = as<IRHLSLStructuredBufferTypeBase>(unwrapArray(varType)) )
            {
                emitIRStructuredBuffer_GLSL(
                    ctx,
                    varDecl,
                    structuredBufferType);
                return;
            }

The unwrapArray(...) there is taking a Foo[][][]...[] and turning it into just Foo, which is what we want to do for detecting the structured buffer. But then we pass it into emitIRStructuredBuffer_GLSL unwrapped, and lose the array-ness.
The right thing to do is to pass in both the structured-buffer type at the "leaf" as well as the full type, and then have emitIRStructuredBuffer_GLSL emit something like:
buffer _S1 { int outputBuffer_0[]; } _someNameHere[3];

But then a use site that used to be outputBuffer[a][b] in the original HLSL code needs to be emitted as _someNameHere[a].outputBuffer[b]; so other parts of the emit logic need to deal with it.

Closing as obsolete. We will have to deal with this in the glsl project, but maybe we should get to that through the fresh top down look at the feature.


LLM_MODEL not updated

Describe the bug
when running make run, frontend and backend both start succesfully. On first message to Devin,

Setup and configuration
Current version:
from gitlog -n 1:
commit 22a9a28e46f86488d8756db3c074ee35403ba740 (HEAD -> main, origin/main, origin/HEAD)

from cat config.toml:
LLM_API_KEY="valid-free-tier-openAI-API key"
LLM_MODEL="gpt-3.5-turbo"
WORKSPACE_DIR="./workspace"
My model and agent (you can see these settings in the UI):

Model: gpt-3.5-turbo
Agent: monologue

Commands I ran to install and run OpenDevin:
make build, with changes prescribed in #579
make setup-config with llm api key and model name
make run
Steps to Reproduce:
fresh install of opendevin with new openai API key (free tier) and use model name gpt-3.5-turbo
OBSERVATION:
Error condensing thoughts: No healthy deployment available, passed model=gpt-3.5-turbo
Error sending data to client Cannot call "send" once a close message has been sent.

I have a similar issue. My config.toml is in the root of the git clone, which is where I execute 'make ...' from and none of the settings appear to be read from it.

I have the same issue.

Hack solution:
in opendevin/llm/llm.py
class LLM:
    def __init__(self,
            model=DEFAULT_MODEL_NAME,
            api_key=DEFAULT_API_KEY,
            base_url=DEFAULT_BASE_URL,
            num_retries=DEFAULT_LLM_NUM_RETRIES,
            cooldown_time=DEFAULT_LLM_COOLDOWN_TIME,
            debug_dir=PROMPT_DEBUG_DIR
    ):
        self.model_name = DEFAULT_MODEL_NAME   # model if model else DEFAULT_MODEL_NAME
        self.api_key = DEFAULT_API_KEY         # api_key if api_key else DEFAULT_API_KEY
        self.base_url = DEFAULT_BASE_URL       # base_url if base_url else DEFAULT_BASE_URL

The conditional statement is causing the script to overwrite the default values with the ones that are in the frontend ui settings. You can comment out the conditional and force it to use the default which comes from the config file.

@yimothysu could this be related to your recent PR?

https://github.com/OpenDevin/OpenDevin/pull/541
We might want to revert this one. I think correct behavior is:

If user doesn't specify anything in FE, fall back to config.toml
Once user specifies something in FE, that becomes the go-forward

Either that, or maybe we stop telling folks to specify model and key in the make instructions, and tell them to set it in the UI

@rbren it would be nice if the user could just type in the model in the frontend. I have been trying to get ollama to work and I had it running last night but some change today has caused it to not work anymore.

I don't know if its related but this config file worked the with the older version
LLM_API_KEY="ollama"
LLM_BASE_URL="http://<IP_ADDRESS>:11434"
LLM_MODEL="ollama/mistral"
LLM_EMBEDDING_MODEL="local"
WORKSPACE_DIR="./workspace"
uvicorn opendevin.server.listen:app --port 3000 --host <IP_ADDRESS>
npm run start -- --host
i added that to the Makefile file
start-backend:
@echo "Starting backend..."
@pipenv run uvicorn opendevin.server.listen:app --port $(BACKEND_PORT) --host <IP_ADDRESS>
Start frontend
start-frontend:
@echo "Starting frontend..."
@cd frontend && npm run start -- --port $(FRONTEND_PORT) -- --host
using the same config as above. I also tried the following as it was generated by the setup in the beginning.
LLM_API_KEY="ollama"
LLM_MODEL="ollama/mistral"
WORKSPACE_DIR="./workspace"
Getting this error, tried to choose different models in the opendevin gui to see if it makes a difference but no.
OBSERVATION:
Error condensing thoughts: No healthy deployment available, passed model=mistral.mistral-7b-instruct-v0:2
Error condensing thoughts: No healthy deployment available, passed model=gpt-4-0125-preview
Oops. Something went wrong: Error condensing thoughts: BedrockException - AWS region not set: set AWS_REGION_NAME or AWS_REGION env variable or in .env file
Also what I run into in the older version is, that opendevin is just not continuing, i waited like 30 minutes for updates in the chat but there were none and no files generated.

@rbren PR https://github.com/OpenDevin/OpenDevin/pull/541 sends the frontend model/agent/workspace dir to the backend on initialization. The error in the screenshot seems unrelated though because I don't encounter any similar errors on any model.

I think correct behavior is:
* If user doesn't specify anything in FE, fall back to config.toml

* Once user specifies something in FE, that becomes the go-forward

Yes. The only change necessary is to send LLM_MODEL from the backend to the frontend on initialization. This way the frontend will have the correct model selected in the settings menu.
I don't think we need to revert because the PR fixes https://github.com/OpenDevin/OpenDevin/issues/500.

The only change necessary is to send LLM_MODEL from the backend to the frontend on initialization.

OK this SGTM--can you open up a separate issue to get that done? Seems like a lot of users are confused

Yes, new issue here: https://github.com/OpenDevin/OpenDevin/issues/617
I can see how it's confusing since LLM_MODEL is effectively not respected with the new frontend initialization.

Either that, or maybe we stop telling folks to specify model and key in the make instructions, and tell them to set it in the UI

This sounds alot more user friendly, if one could set the configs in frontend (including a toggle or base url for running it locally)

This has been fixed and broke again https://github.com/OpenDevin/OpenDevin/issues/793
I will close it here so we can keep it in one place.


Update cats-effect, cats-effect-std to 3.3.11

Updates

org.typelevel:cats-effect
org.typelevel:cats-effect-std

from 3.3.10 to 3.3.11.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.typelevel" } ]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #67.


YARN-11088. Introduce the config to control the AM allocated to non-e…

…xclusive nodes

Description of PR
How was this patch tested?
For code changes:

[ ] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'HADOOP-17799. Your PR title ...')?
[ ] Object storage: have the integration tests been executed and the endpoint declared according to the connector-specific documentation?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE, LICENSE-binary, NOTICE-binary files?

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
1m  0s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

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

_ trunk Compile Tests _

+0 :ok:
mvndep
12m 48s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
23m 23s

trunk passed

+1 :green_heart:
compile
9m 45s

trunk passed with JDK Ubuntu-11.0.14+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
compile
8m 30s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
checkstyle
1m 43s

trunk passed

+1 :green_heart:
mvnsite
3m 18s

trunk passed

+1 :green_heart:
javadoc
2m 57s

trunk passed with JDK Ubuntu-11.0.14+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javadoc
2m 48s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
6m  2s

trunk passed

+1 :green_heart:
shadedclient
22m  5s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 28s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m  9s

the patch passed

+1 :green_heart:
compile
9m  4s

the patch passed with JDK Ubuntu-11.0.14+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javac
9m  4s

the patch passed

+1 :green_heart:
compile
8m 24s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
javac
8m 24s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
1m 36s

the patch passed

+1 :green_heart:
mvnsite
3m  1s

the patch passed

+1 :green_heart:
xml
0m  1s

The patch has no ill-formed XML file.

+1 :green_heart:
javadoc
2m 42s

the patch passed with JDK Ubuntu-11.0.14+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javadoc
2m 32s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
6m 23s

the patch passed

+1 :green_heart:
shadedclient
22m  7s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

-1 :x:
unit
1m 10s
/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-api.txt
hadoop-yarn-api in the patch passed.

+1 :green_heart:
unit
4m 59s

hadoop-yarn-common in the patch passed.

+1 :green_heart:
unit
116m 13s

hadoop-yarn-server-resourcemanager in the patch passed.

+1 :green_heart:
asflicense
0m 53s

The patch does not generate ASF License warnings.

277m  6s

Reason
Tests

Failed junit tests
hadoop.yarn.conf.TestYarnConfigurationFields

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4105/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/4105

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell xml

uname
Linux 340326807f2a 4.15.0-65-generic #74-Ubuntu SMP Tue Sep 17 17:06:04 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 5fa6d52b293e8d3eacfa798e3f8642fd470d5a93

Default Java
Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.14+9-Ubuntu-0ubuntu2.20.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4105/1/testReport/

Max. process+thread count
929 (vs. ulimit of 5500)

modules
C: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager U: hadoop-yarn-project/hadoop-yarn

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4105/1/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

Thanks for your review. The change will be uploaded as soon as possible. @brumi1024

Updated @brumi1024. If u have time, could you help review again.

Thanks @zuston, the latest patch LGTM.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+0 :ok:
mvndep
13m 20s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
22m 59s

trunk passed

+1 :green_heart:
compile
9m 35s

trunk passed with JDK Ubuntu-11.0.14+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
compile
8m 30s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
checkstyle
1m 42s

trunk passed

+1 :green_heart:
mvnsite
3m 17s

trunk passed

+1 :green_heart:
javadoc
3m  0s

trunk passed with JDK Ubuntu-11.0.14+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javadoc
2m 49s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
6m  1s

trunk passed

+1 :green_heart:
shadedclient
22m 16s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 26s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m  9s

the patch passed

+1 :green_heart:
compile
9m  1s

the patch passed with JDK Ubuntu-11.0.14+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javac
9m  1s

the patch passed

+1 :green_heart:
compile
8m 21s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
javac
8m 21s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
1m 38s

the patch passed

+1 :green_heart:
mvnsite
3m  3s

the patch passed

+1 :green_heart:
xml
0m  2s

The patch has no ill-formed XML file.

+1 :green_heart:
javadoc
2m 40s

the patch passed with JDK Ubuntu-11.0.14+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javadoc
2m 34s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
6m 20s

the patch passed

+1 :green_heart:
shadedclient
22m  3s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

-1 :x:
unit
1m 11s
/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-api.txt
hadoop-yarn-api in the patch passed.

+1 :green_heart:
unit
4m 59s

hadoop-yarn-common in the patch passed.

+1 :green_heart:
unit
100m 48s

hadoop-yarn-server-resourcemanager in the patch passed.

+1 :green_heart:
asflicense
0m 53s

The patch does not generate ASF License warnings.

261m 58s

Reason
Tests

Failed junit tests
hadoop.yarn.conf.TestYarnConfigurationFields

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4105/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/4105

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell xml

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

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 6aae6de29110212863f216608144ce53d7c70c66

Default Java
Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.14+9-Ubuntu-0ubuntu2.20.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4105/2/testReport/

Max. process+thread count
961 (vs. ulimit of 5500)

modules
C: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager U: hadoop-yarn-project/hadoop-yarn

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4105/2/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

@zuston can you please take a look at the unit test failure?

@brumi1024 Thanks for your quick reply.
The failure is due to the lack of yarn.resourcemanager.node-labels.am.default-node-label-expression in yarn-default.xml, which is introduced in https://github.com/apache/hadoop/pull/4060 by me.

https://github.com/apache/hadoop/pull/4060#issuecomment-1076158410

However it's removed when merging to trunk. Maybe i need to fix it with another PR and then merge this PR after that.
Do u think so? @brumi1024

@zuston thanks, I see now. Yes, please open a different PR to fix it :) then a rebase should give this a green build as well.
cc: @9uapaw

@zuston It was my fault sorry, I thought it is not needed in case the default is empty.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 59s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+0 :ok:
mvndep
15m 34s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
24m 12s

trunk passed

+1 :green_heart:
compile
9m 50s

trunk passed with JDK Ubuntu-11.0.14+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
compile
8m 29s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
checkstyle
1m 42s

trunk passed

+1 :green_heart:
mvnsite
3m 21s

trunk passed

+1 :green_heart:
javadoc
2m 58s

trunk passed with JDK Ubuntu-11.0.14+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javadoc
2m 48s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
6m  0s

trunk passed

+1 :green_heart:
shadedclient
22m 17s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 29s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m  9s

the patch passed

+1 :green_heart:
compile
9m  9s

the patch passed with JDK Ubuntu-11.0.14+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javac
9m  9s

the patch passed

+1 :green_heart:
compile
8m 27s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
javac
8m 27s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
1m 39s

the patch passed

+1 :green_heart:
mvnsite
3m  6s

the patch passed

+1 :green_heart:
xml
0m  2s

The patch has no ill-formed XML file.

+1 :green_heart:
javadoc
2m 39s

the patch passed with JDK Ubuntu-11.0.14+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javadoc
2m 33s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
6m 23s

the patch passed

+1 :green_heart:
shadedclient
25m 32s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
1m 12s

hadoop-yarn-api in the patch passed.

+1 :green_heart:
unit
5m  0s

hadoop-yarn-common in the patch passed.

-1 :x:
unit
115m 24s
/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-resourcemanager.txt
hadoop-yarn-server-resourcemanager in the patch passed.

+0 :ok:
asflicense
0m 39s

ASF License check generated no output?

283m 48s

Reason
Tests

Failed junit tests
hadoop.yarn.server.resourcemanager.scheduler.fair.TestFairScheduler

hadoop.yarn.server.resourcemanager.scheduler.capacity.TestCapacityScheduler

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4105/3/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/4105

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell xml

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

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 663cc3a792e8d5c67d1a0c2fa0a117d2d1969677

Default Java
Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.14+9-Ubuntu-0ubuntu2.20.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4105/3/testReport/

Max. process+thread count
863 (vs. ulimit of 5500)

modules
C: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager U: hadoop-yarn-project/hadoop-yarn

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4105/3/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

Thanks @zuston, committed to trunk.

Thanks @brumi1024


Whenever I open gameplay color it’s just plain black.

I know it’s not an iOS problem though because I’ve restarted my iPad many times and it still doesn’t work. I am on iPadOS 13.1.2 and it’s an iPad Pro I don’t know which generation it is though.

Also I had it working a while ago (like I could play games) then suddenly it started doing this

Thanks for raising the issue. I think this might be the same as #123 which is a result of Safari on iPadOS pretending to be a Mac.


Error: unknown command "oidc-login" for "kubectl"

Describe the bug
My kubeconfig file works when using kubectl and the krew installed oidc_login plugin but doesn't work for Lens and when i paste in my config into Lense and press the "Add Cluster" button I get the error Error: unknown command "oidc-login" for "kubectl".
To Reproduce
Steps to reproduce the behavior:
Open Lens and load my kubeconfig and the error appears
Expected behavior
I think my browser should open and I should be able to authenticate through the browser. So I just enter my login details and if they are correct I get a OK message in the browser and I expect lens to then be able to connect to the cluster
Environment (please complete the following information):

Lens Version: 3.5.0
OS: Ubuntu 20.04 LTS
Installation method (e.g. snap or AppImage in Linux): snap

Logs:
When you run the application executable from command line you will see some logging output. Please paste them here:
Connecting ...
Error: unknown command "oidc-login" for "kubectl"
Run 'kubectl --help' for usage.
2020/06/26 12:39:40 http: proxy error: getting credentials: exec: exit status 1

Kubeconfig:
Quite often the problems are caused by malformed kubeconfig which the application tries to load. Please share your kubeconfig, remember to remove any secret and sensitive information.
apiVersion: v1
kind: Config

clusters:
- name: mycluster-cluster
  cluster:
    server: https://mycluster.com:6443
    certificate-authority-data: LS089eutj980w5j7t4........
contexts:
- context:
    cluster: mycluster-cluster
    user: oidc
  name: mycluster-context
current-context: mycluster-context

preferences: {}

users:
- name: oidc
  user:
    exec:
      apiVersion: client.authentication.k8s.io/v1beta1
      args:
      - oidc-login
      - get-token
      - --oidc-issuer-url=https://auth.mydomain.com/auth/realms/MYREALM
      - --oidc-client-id=kubernetes
      - --oidc-client-secret=
      command: kubectl
      env: null

Additional context
Add any other context about the problem here.
I am not sure if it mater but my Desktop OS is Ubuntu Mate and I am using Lens 3.5.0 what was installed as a snap.

So figured it out... I had to change the user part of my config as follows....
users:

name: oidc
user:
exec:
apiVersion: client.authentication.k8s.io/v1beta1
args:
- "get-token"
- --oidc-issuer-url=https://auth.mydomain.com/auth/realms/MYREALM
- --oidc-client-id=kubernetes
- --oidc-client-secret=
command: /your_path_to/kubelogin
env: null


Update draft workflow to use Framework slugs and statuses

Do the TODOs
https://www.youtube.com/watch?v=sM_9As_2VAg

I'm guessing this TODO is going in a separate pull request https://github.com/alphagov/digitalmarketplace-api/blob/master/app/models.py#L529

It's a separate story altogether: https://www.pivotaltracker.com/story/show/97640874


[TASK][EASY] Improve kyuubi-beeline help message

What's the level of this task?
EASY
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Search before creating

[X] I have searched in the task list and found no similar tasks.

Mentor

[X] I have sufficient expertise on this task, and I volunteer to be a mentor of this task to guide contributors through the task.

Skill requirements

Basic knowledge of Java and Kyuubi

Background and Goals
The current kyuubi-beeline output message has some errors and is not very pretty.
$ bin/kyuubi-beeline --help
Usage: java org.apache.hive.cli.beeline.BeeLine
   -u <database url>               the JDBC URL to connect to
   -c <named url>                  the named JDBC URL to connect to,
                                   which should be present in beeline-site.xml
                                   as the value of beeline.hs2.jdbc.url.<namedUrl>
   -r                              reconnect to last saved connect url (in conjunction with !save)
   -n <username>                   the username to connect as
   -p <password>                   the password to connect as
   -d <driver class>               the driver class to use
   -i <init file>                  script file for initialization
   -e <query>                      query that should be executed
   -f <exec file>                  script file that should be executed
   -w (or) --password-file <password file>  the password file to read password from
   --hiveconf property=value       Use value for given property
   --hivevar name=value            hive variable name and value
                                   This is Hive specific settings in which variables
                                   can be set at session level and referenced in Hive
                                   commands or queries.
   --property-file=<property-file> the file to read connection properties (url, driver, user, password) from
   --color=[true/false]            control whether color is used for display
   --showHeader=[true/false]       show column names in query results
   --escapeCRLF=[true/false]       show carriage return and line feeds in query results as escaped \r and \n
   --headerInterval=ROWS;          the interval between which heades are displayed
   --fastConnect=[true/false]      skip building table/column list for tab-completion
   --autoCommit=[true/false]       enable/disable automatic transaction commit
   --verbose=[true/false]          show verbose error messages and debug info
   --showWarnings=[true/false]     display connection warnings
   --showDbInPrompt=[true/false]   display the current database name in the prompt
   --showNestedErrs=[true/false]   display nested errors
   --numberFormat=[pattern]        format numbers using DecimalFormat pattern
   --force=[true/false]            continue running script even after errors
   --maxWidth=MAXWIDTH             the maximum width of the terminal
   --maxColumnWidth=MAXCOLWIDTH    the maximum width to use when displaying columns
   --silent=[true/false]           be more silent
   --autosave=[true/false]         automatically save preferences
   --outputformat=[table/vertical/csv2/tsv2/dsv/csv/tsv]  format mode for result display
                                   Note that csv, and tsv are deprecated - use csv2, tsv2 instead
   --incremental=[true/false]      Defaults to false. When set to false, the entire result set
                                   is fetched and buffered before being displayed, yielding optimal
                                   display column sizing. When set to true, result rows are displayed
                                   immediately as they are fetched, yielding lower latency and
                                   memory usage at the price of extra display column padding.
                                   Setting --incremental=true is recommended if you encounter an OutOfMemory
                                   on the client side (due to the fetched result set size being large).
                                   Only applicable if --outputformat=table.
   --incrementalBufferRows=NUMROWS the number of rows to buffer when printing rows on stdout,
                                   defaults to 1000; only applicable if --incremental=true
                                   and --outputformat=table
   --truncateTable=[true/false]    truncate table column when it exceeds length
   --delimiterForDSV=DELIMITER     specify the delimiter for delimiter-separated values output format (default: |)
   --isolation=LEVEL               set the transaction isolation level
   --nullemptystring=[true/false]  set to true to get historic behavior of printing null as empty string
   --maxHistoryRows=MAXHISTORYROWS The maximum number of rows to store beeline history.
   --delimiter=DELIMITER           set the query delimiter; multi-char delimiters are allowed, but quotation
                                   marks, slashes, and -- are not allowed; defaults to ;
   --convertBinaryArrayToString=[true/false]    display binary column data as string or as byte array
   --help                          display this message

   Example:
    1. Connect using simple authentication to HiveServer2 on localhost:10000
    $ beeline -u jdbc:hive2://localhost:10000 username password

    2. Connect using simple authentication to HiveServer2 on hs.local:10000 using -n for username and -p for password
    $ beeline -n username -p password -u jdbc:hive2://hs2.local:10012

    3. Connect using Kerberos authentication with<EMAIL_ADDRESS>as HiveServer2 principal
    $ beeline -u<EMAIL_ADDRESS>
    4. Connect using SSL connection to HiveServer2 on localhost at 10000
    $ beeline "jdbc:hive2://localhost:10000/default;ssl=true;sslTrustStore=/usr/local/truststore;trustStorePassword=mytruststorepassword"

    5. Connect using LDAP authentication
    $ beeline -u jdbc:hive2://hs2.local:10013/default <ldap-username> <ldap-password>

Usage: java org.apache.hive.beeline.KyuubiBeeLine
   --python-mode                   Execute python code/script.

Implementation steps

kyuubi-beeline is derived from Hive beeline, we have made some changes since forking, some reference to Hive is improper now and we should remove them
replace jdbc:hive2// with jdbc:kyuubi//
update and validate examples
other changes

Additional context
Introduction of 2024H1 Kyuubi Code Contribution Program

@ShockleysxX thanks, assigned

@ShockleysxX Do you have any progress on this task? An easy task typically costs a few hours to complete.

Revoked as the assignor has no response

Could I continue to do this task, may be in 3 days

@liuxiaocs7 assigned, thanks

Hi, I am also interested in this issue, and I have already made modifications about the help message of kyuubi-beeline  locally. Here's how my implementation works. May I submit a PR for this?
$ ./bin/kyuubi-beeline --help
Usage: kyuubi-beeline <options>.

Options:
   -u <database url>                 The JDBC URL to connect to.
   -c <named url>                    The named JDBC URL to connect to,
                                     which should be present in beeline-site.xml
                                     as the value of beeline.kyuubi.jdbc.url.<namedUrl>.

   -r                                Reconnect to last saved connect url (in conjunction with !save).
   -n <username>                     The username to connect as.
   -p <password>                     The password to connect as.
   -d <driver class>                 The driver class to use.
   -i <init file>                    Script file for initialization.
   -e <query>                        Query that should be executed.
   -f <exec file>                    Script file that should be executed.
   -w, --password-file <file>        The password file to read password from.
   --hiveconf property=value         Use value for given property.
   --hivevar name=value              Hive variable name and value.
                                     This is Hive specific settings in which variables
                                     can be set at session level and referenced in Hive
                                     commands or queries.

   --property-file=<property-file>   The file to read connection properties (url, driver, user, password) from.
   --color=[true|false]              Control whether color is used for display.
   --showHeader=[true|false]         Show column names in query results.
   --escapeCRLF=[true|false]         Show carriage return and line feeds in query results as escaped \r and \n.
   --headerInterval=ROWS;            The interval between which heades are displayed.
   --fastConnect=[true|false]        Skip building table/column list for tab-completion.
   --autoCommit=[true|false]         Enable/disable automatic transaction commit.
   --verbose=[true|false]            Show verbose error messages and debug info.
   --showWarnings=[true|false]       Display connection warnings.
   --showDbInPrompt=[true|false]     Display the current database name in the prompt.
   --showNestedErrs=[true|false]     Display nested errors.
   --numberFormat=[pattern]          Format numbers using DecimalFormat pattern.
   --force=[true|false]              Continue running script even after errors.
   --maxWidth=MAXWIDTH               The maximum width of the terminal.
   --maxColumnWidth=MAXCOLWIDTH      The maximum width to use when displaying columns.
   --silent=[true|false]             Be more silent.
   --autosave=[true|false]           Automatically save preferences.
   --outputformat=<format mode>      Format mode for result display.
                                     The available options ars [table|vertical|csv2|tsv2|dsv|csv|tsv|json|jsonfile].
                                     Note that csv, and tsv are deprecated, use csv2, tsv2 instead.

   --incremental=[true|false]        Defaults to false. When set to false, the entire result set
                                     is fetched and buffered before being displayed, yielding optimal
                                     display column sizing. When set to true, result rows are displayed
                                     immediately as they are fetched, yielding lower latency and
                                     memory usage at the price of extra display column padding.
                                     Setting --incremental=true is recommended if you encounter an OutOfMemory
                                     on the client side (due to the fetched result set size being large).
                                     Only applicable if --outputformat=table.

   --incrementalBufferRows=NUMROWS   The number of rows to buffer when printing rows on stdout,
                                     defaults to 1000; only applicable if --incremental=true
                                     and --outputformat=table.

   --truncateTable=[true|false]      Truncate table column when it exceeds length.
   --delimiterForDSV=DELIMITER       Specify the delimiter for delimiter-separated values output format (default: |).
   --isolation=LEVEL                 Set the transaction isolation level.
   --nullemptystring=[true|false]    Set to true to get historic behavior of printing null as empty string.
   --maxHistoryRows=MAXHISTORYROWS   The maximum number of rows to store beeline history.
   --delimiter=DELIMITER             Set the query delimiter; multi-char delimiters are allowed, but quotation
                                     marks, slashes, and -- are not allowed; defaults to ;

   --convertBinaryArrayToString=[true|false]
                                     Display binary column data as string or as byte array.

   --python-mode                     Execute python code/script.
   --help                            Display this message.

   Example:
    1. Connect using simple authentication to KyuubiServer on localhost:10009
    $ kyuubi-beeline -u jdbc:kyuubi://localhost:10009 username password

    2. Connect using simple authentication to KyuubiServer on kyuubi.local:10009 using -n for username and -p for password
    $ kyuubi-beeline -n username -p password -u jdbc:kyuubi://kyuubi.local:10009

    3. Connect using Kerberos authentication with<EMAIL_ADDRESS>as KyuubiServer principal
    $ kyuubi-beeline -u<EMAIL_ADDRESS>
    4. Connect using SSL connection to KyuubiServer on localhost at 10009
    $ kyuubi-beeline "jdbc:kyuubi://localhost:10009/default;ssl=true;sslTrustStore=/usr/local/truststore;trustStorePassword=mytruststorepassword"

    5. Connect using LDAP authentication
    $ kyuubi-beeline -u jdbc:kyuubi://kyuubi.local:10009/default <ldap-username> <ldap-password>

Hi, @dupen01, I've been working on my thesis for the past days resulting in not really starting it yet, so you can continue this task and look forward to your contribution! CC @pan3793

thanks for response @liuxiaocs7, I re-assigned this task to @dupen01