SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e) bugcheck on Win10 1809

Brief description of your issue
When I download the nightly, expand the zip and run the si exe I get a SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e) bugcheck under Windows 10 1809 LTSC
Steps to reproduce (optional)

download nightly
run it under Windows 10 1809

Expected behavior (optional)
No response
Actual behavior (optional)
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e) bugcheck on Win10 1809, so I compiled my own version and opened the dump, forced the load of my mismatched PDB to get a somehow better callstack:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
This is a very common BugCheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8034f47feb0, The address that the exception occurred at
Arg3: ffffd48738eca078, Exception Record Address
Arg4: ffffd48738ec98c0, Context Record Address

EXCEPTION_RECORD:  ffffd48738eca078 -- (.exr 0xffffd48738eca078)
ExceptionAddress: fffff8034f47feb0 (nt!ExpLookupHandleTableEntry)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]:<PHONE_NUMBER>000000
   Parameter[1]:<PHONE_NUMBER>000032
Attempt to read from address<PHONE_NUMBER>000032

PROCESS_NAME:  System

READ_ADDRESS:<PHONE_NUMBER>000032

ERROR_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%p verwies auf Arbeitsspeicher bei 0x%p. Der Vorgang %s konnte im Arbeitsspeicher nicht durchgef hrt werden.

EXCEPTION_CODE_STR:  c0000005

EXCEPTION_PARAMETER1:<PHONE_NUMBER>000000

EXCEPTION_PARAMETER2:<PHONE_NUMBER>000032

EXCEPTION_STR:  0xc0000005

Environment (optional)

System Informer Rev. 5578
Windows 10 1809 LTSC 17763.3650 x64 German inside a VMware VM

@MagicAndre1981 that call stack is highly illogical to me. If possible, using the nightly build with the release driver, please reproduce the crash and email me the dump file.

@MagicAndre1981 that call stack is highly illogical to me. If possible, using the nightly build with the release driver, please reproduce the crash and email me the dump file.

the crash happens with the release driver, as said, I just downloaded the zip, expanded the zip, tried to run SI and got the BSOD.

so I compiled my own version and opened the dump, forced the load of my mismatched PDB to get a somehow better callstack

Sorry, I seem to have misunderstood your message.
Regardless, it looks like a null pointer dereference. Potentially due to bad offsets in dynamic data. Please email me the dump file so I can investigate. Or, using the dump file, try to dump the information on the currently loaded dynamic data:
static KPH_ACTIVE_DYNDATA KphpActiveDynData = { 0 };

It's hard to tell for sure, given the mismatched symbols, but this may be retrieving the wrong pointer.
https://github.com/winsiderss/systeminformer/blob/master/KSystemInformer/object.c#L78
Dumping the EPROCESS object and KphpActiveDynData will help, if possible, given the bad symbols. Unsure why you can't load them. They're here:
https://github.com/winsiderss/systeminformer/tree/master/KSystemInformer%2Fbin-signed%2Famd64

I wrote an mail to your live mail account from your profile

Thanks, I'm away from a computer today. I'll look when I'm back.

Unsure why you can't load them. They're here:

I've had similar issues in the past related to PDBALTPATH stripping the PDB filename from the debug header:

The other issue is how dbghelp doesn't check the directory where the image is located:

PDBALTPATH strips the path and it becomes relative. Sometime later dbghelp tries using the filename but since it's relative ends up in the current directory (the same location as the executable and not allowed) then won't check elsewhere and just doesn't load the PDB 🙄

forced the load of my mismatched PDB

@MagicAndre1981

Copy the pdbs from \bin-signed\amd64\ into somefolder
Set the symbol search path for the debugger using this exact format:
D:\somefolder;SRV*C:\Symbols*msdl.microsoft.com

This way you can give proper stack traces that make sense unlike the homebrew mismatched PDB you've been using 😉

@MagicAndre1981 I just got back to check my email and I still haven't received an email from you.

confusing. I wrote the mail yesterday. I sent a new one, also check junk folder

. Set the symbol search path for the debugger using this exact format:
D:\somefolder;SRV*C:\Symbols*msdl.microsoft.com
This way you can give proper stack traces that make sense unlike the homebrew mismatched PDB you've been using wink

here is the output:
STACK_TEXT:
ffffc08d`e4b7d2b8 fffff804`4ff458d2     : 00000000`00000000 00000000`00000000 9a70a28a`86d416bf b55f17de`53678e9d : nt!ExpLookupHandleTableEntry
ffffc08d`e4b7d2c0 fffff804`4ff457e4     : fffff804`55204674 fffff804`4ff57460 ffff9109`0cfbf300 fffff804`5520c4bf : nt!ExpGetNextHandleTableEntry+0x22
ffffc08d`e4b7d2f0 fffff804`55204782     : ffffc08d`e4b7d528 ffffc08d`e4b7d528 fffff804`55207f40 fffff804`551fc0a0 : nt!ExEnumHandleTable+0x44
ffffc08d`e4b7d360 fffff804`55207ed6     : 00000000`00000010 00000000`00010213 ffffc08d`e4b7d528 ffffc08d`e4b7d528 : SystemInformer!KphEnumerateProcessHandlesEx+0x10e [C:\Users\aione\source\repos\systeminformer\KSystemInformer\object.c @ 273]
ffffc08d`e4b7d3c0 fffff804`551fc0f3     : ffffc08d`e4b7d4c0 00000000`3363704b ffffc08d`e4b7d499 fffff804`4f8e281b : SystemInformer!KphEnumProcessContextsForProtection+0x36 [C:\Users\aione\source\repos\systeminformer\KSystemInformer\protection.c @ 391]
ffffc08d`e4b7d3f0 fffff804`551faeeb     : ffffc70b`17135098 00000000`00000000 ffffc08d`00000000 fffff804`4fefd07b : SystemInformer!KphpEnumerateContexts+0x53 [C:\Users\aione\source\repos\systeminformer\KSystemInformer\cid_tracking.c @ 1280]
ffffc08d`e4b7d420 fffff804`551fae14     : ffffc70b`19549000 00000000`00000000 00000000`00000013 ffffc70b`1717fd50 : SystemInformer!CidEnumerateInvokeCallback+0x6b [C:\Users\aione\source\repos\systeminformer\KSystemInformer\cid_table.c @ 617]
ffffc08d`e4b7d450 fffff804`551fbd03     : ffffc70b`1717fd01 fffff804`551fc0a0 00000000`00000000 00000000`0012184b : SystemInformer!CidEnumerateInternal+0xe8 [C:\Users\aione\source\repos\systeminformer\KSystemInformer\cid_table.c @ 714]
ffffc08d`e4b7d4a0 fffff804`5520826f     : ffffc70b`1717fd01 00000000`0012184b 00000000`00000000 fffff804`4f9ce8c3 : SystemInformer!KphEnumerateProcessContexts+0x3f [C:\Users\aione\source\repos\systeminformer\KSystemInformer\cid_tracking.c @ 1305]
ffffc08d`e4b7d500 fffff804`551fbf2b     : ffffc70b`1717fd50 ffffc70b`1717fd50 fffff804`551fc0a0 e8c99d43`00000000 : SystemInformer!KphStartProtectingProcess+0x12f [C:\Users\aione\source\repos\systeminformer\KSystemInformer\protection.c @ 518]
ffffc08d`e4b7d590 fffff804`551fc0f3     : ffffc70b`1717fd50 00000000`0000001e 00000000`00000001 fffff804`4fe0e100 : SystemInformer!KphpCidEnumPostPopulate+0x3b [C:\Users\aione\source\repos\systeminformer\KSystemInformer\cid_tracking.c @ 771]
ffffc08d`e4b7d5c0 fffff804`551faeeb     : ffffc70b`166f7330 00000000`00000000 01000000`00100000 fffff804`4f8ea8e7 : SystemInformer!KphpEnumerateContexts+0x53 [C:\Users\aione\source\repos\systeminformer\KSystemInformer\cid_tracking.c @ 1280]
ffffc08d`e4b7d5f0 fffff804`551fae14     : ffffc70b`19549010 00000000`00000002 00000000`00000066 00000000`00000040 : SystemInformer!CidEnumerateInvokeCallback+0x6b [C:\Users\aione\source\repos\systeminformer\KSystemInformer\cid_table.c @ 617]
ffffc08d`e4b7d620 fffff804`551fbcaf     : 00000000`00000103 fffff804`551fc0a0 00000000`00000000 ffffc08d`e4b7d730 : SystemInformer!CidEnumerateInternal+0xe8 [C:\Users\aione\source\repos\systeminformer\KSystemInformer\cid_table.c @ 714]
ffffc08d`e4b7d670 fffff804`551fbc41     : 00000000`00000103 fffff804`551f7000 00000000`00000b58 fffff804`3163704b : SystemInformer!KphEnumerateCidContexts+0x3f [C:\Users\aione\source\repos\systeminformer\KSystemInformer\cid_tracking.c @ 1355]
ffffc08d`e4b7d6d0 fffff804`55203a0d     : 00000000`00000000 ffff9109`0ad23000 00000000`00000000 00000000`00000000 : SystemInformer!KphCidPopulate+0x66d [C:\Users\aione\source\repos\systeminformer\KSystemInformer\cid_tracking.c @ 1080]
ffffc08d`e4b7d760 fffff804`55210020     : 00000000`00000000 ffff9109`0a64ae10 ffff9109`0ad23000 ffff30c5`507a890a : SystemInformer!DriverEntry+0x555 [C:\Users\aione\source\repos\systeminformer\KSystemInformer\main.c @ 300]
ffffc08d`e4b7d920 fffff804`4ff82235     : 00000000`00000000 00000000`00000000 ffff9109`0a64ae10 00000000`00001000 : SystemInformer!GsDriverEntry+0x20 [minkernel\tools\gs_support\kmodefastfail\gs_driverentry.c @ 47]
ffffc08d`e4b7d950 fffff804`4ff818fa     : ffff9109`048f4180 00000000`00000000 00000000`00000000 ffff9109`03b24050 : nt!IopLoadDriver+0x4bd
ffffc08d`e4b7db30 fffff804`4f96567a     : ffff9109`00000000 ffffffff`800029b8 ffff9109`0a58a040 ffff9109`00000000 : nt!IopLoadUnloadDriver+0x4a
ffffc08d`e4b7db70 fffff804`4f9e7375     : ffff9109`0a58a040 ffff9109`03a7a080 ffff9109`0a58a040 00000065`b8bbbdff : nt!ExpWorkerThread+0x16a
ffffc08d`e4b7dc10 fffff804`4fa759ec     : ffffa600`7bd40180 ffff9109`0a58a040 fffff804`4f9e7320 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffffc08d`e4b7dc60 00000000`00000000     : ffffc08d`e4b7e000 ffffc08d`e4b78000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x1c

FAULTING_SOURCE_LINE:  C:\Users\aione\source\repos\systeminformer\KSystemInformer\object.c

FAULTING_SOURCE_FILE:  C:\Users\aione\source\repos\systeminformer\KSystemInformer\object.c

FAULTING_SOURCE_LINE_NUMBER:  273

FAULTING_SOURCE_CODE:
No source found for 'C:\Users\aione\source\repos\systeminformer\KSystemInformer\object.c'

SYMBOL_NAME:  SystemInformer!KphEnumerateProcessHandlesEx+10e

MODULE_NAME: SystemInformer

IMAGE_NAME:  SystemInformer.sys

IMAGE_VERSION:  <IP_ADDRESS>

STACK_COMMAND:  .cxr 0xffffc08de4b7c8c0 ; kb

BUCKET_ID_FUNC_OFFSET:  10e

FAILURE_BUCKET_ID:  AV_SystemInformer!KphEnumerateProcessHandlesEx

OS_VERSION:  10.0.17763.1

BUILDLAB_STR:  rs5_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

Thanks for emailing me the dump file. I've identified why dynamic data is not being loaded correctly. We have a plan to address this.

Hello,
I encounter the same bugcheck as soon as I check the "Enable kernel-mode driver" checkbox under Settings.
OS: Windows Server 2019 LTSC - Version 1809 - 17763.3650
SystemInformer Build: Nightly 3.0.5578
A solution would be much appreciated.

https://disk.yandex.com/d/I932kx8-bmhXUA
this from my downloads folder version works

@dmex does "third party" label mean this is a Windows bug in 1809/Server 2019?

@dmex does "third party" label mean this is a Windows bug in 1809/Server 2019?

No, we're waiting for Microsoft. The holidays are slowing down response times in our communication with them.

Can confirm this thing happening on Windows 2019 Server too. SystemInformers kernel-mode driver caused BSOD for me since it was released as an update to ProcessHacker (which in turn worked like a charm with kernel driver enabled). Gonna try to build it myself to get more info

So here is my dump:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff800727ebfd0, The address that the exception occurred at
Arg3: ffffa18870653068, Exception Record Address
Arg4: ffffa188706528b0, Context Record Address

Debugging Details:
------------------

KEY_VALUES_STRING: 1

    Key  : AV.Dereference
    Value: NullClassPtr

    Key  : AV.Fault
    Value: Read

    Key  : Analysis.CPU.mSec
    Value: 5640

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 20770

    Key  : Analysis.Init.CPU.mSec
    Value: 7405

    Key  : Analysis.Init.Elapsed.mSec
    Value: 84135

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 83

    Key  : Dump.Attributes.InsufficientDumpfileSize
    Value: 1

    Key  : Dump.Attributes.RequiredDumpfileSize
    Value: 0x5d1aa065

DUMP_FILE_ATTRIBUTES: 0xc
  Insufficient Dumpfile Size
  Kernel Generated Triage Dump

BUGCHECK_CODE:  7e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff800727ebfd0

BUGCHECK_P3: ffffa18870653068

BUGCHECK_P4: ffffa188706528b0

EXCEPTION_RECORD:  ffffa18870653068 -- (.exr 0xffffa18870653068)
ExceptionAddress: fffff800727ebfd0 (nt!ExpLookupHandleTableEntry)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]:<PHONE_NUMBER>000000
   Parameter[1]:<PHONE_NUMBER>000032
Attempt to read from address<PHONE_NUMBER>000032

CONTEXT:  ffffa188706528b0 -- (.cxr 0xffffa188706528b0)
rax=fffff800bc587eb0 rbx=0000000000000000 rcx=0000000000000032
rdx=0000000000000004 rsi=fffff800bc587f00 rdi=ffffa703ef8d3080
rip=fffff800727ebfd0 rsp=ffffa188706532a8 rbp=0000000000000032
 r8=ffffa18870653310  r9=0000000000000004 r10=ffffa18870653310
r11=ffffa188706533a0 r12=ffffa703eb9ab040 r13=0000000000000000
r14=ffffa18870653378 r15=fffff800bc5848e0
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
nt!ExpLookupHandleTableEntry:
fffff800`727ebfd0 8b01            mov     eax,dword ptr [rcx] ds:002b:00000000`00000032=????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

READ_ADDRESS: GetUlongFromAddress: unable to read from fffff800726d8240
fffff80072753390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
<PHONE_NUMBER>000032

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

Again, we are blocked by Microsoft at the moment. Hoping to get a resolution here mid-january.

Hoping to get a resolution here mid-january.

any response from Microsoft? I still get the bugcheck with latest Patch 17763.3887

Just my stoned thought, but we have nightly builds right? This would have been an ideal chance to the users and community to contribute.
In general, nightly builds right now are just like beta builds when compared withh other software, the last "nightly" is over from over 90 days ago.
Just make the current nightly the beta branch, and make an actual nightly that is updated as needed / at least every week.
🚬🌿

@Anubioz
Thank you for actually taking the time to try it out!
There are a few statistics in showing the string "no driver" if the driver is not loaded or working, here is one you could check:
Open System Explorer with it's driver enabled and loaded, then go to it's main window, click "System Information", switch from "CPU" to "Memory", in the Paged Pool box, the limit should be showing accurately if the driver works fine on your system.
Here is the same window, but on 1809 where the driver would bug-check the system:

If the limit shows accurately for you, then maybe it's time to merge the branch into main?
@jxy-s @dmex

If the limit shows accurately for you, then maybe it's time to merge the branch into main?

I can't merge the changes until we get resolution from Microsoft. Since doing so will orphan the existing driver/client ABI. We touched base with Microsoft last week, hoping for resolution soon. Apologies for the delay - engaging with Microsoft can just take a while.

the limit should be showing accurately if the driver works fine on your system.

@gettysburg Those statistics require symbols and are not available unless you've also installed the Windows SDK.

Open System Explorer with it's driver enabled and loaded

You don't need to open the sysinfo window to check the driver. The main application window title includes the + symbol after the username to show the driver is enabled and loaded.

In general, nightly builds right now are just like beta builds when compared withh other software, the last "nightly" is over from over 90 days ago.

The nightly branch is not stable enough for beta. The last build was 30 days ago on the 25th of December and were on hold for the holidays but have resumed.

on 1809 where the driver would bug-check

Are you able to update to LTSC 2021? This bug only affects legacy versions of Windows 10 while newer versions don't have issues.

Are you able to update to LTSC 2021? This bug only affects legacy versions of Windows 10 while newer versions don't have issues.

I run the 1809 on purpose. It is the Windows 10 which Microsoft sets now as minimum supported system for a lot of new things like WinUI/WinAppSDK. And what I normally do is the start ProcessHacker/SysInformer directly at start in case the system gets unresponsive to be able to easily see what is going on (on my dads laptop with 1904x, search had mem leak and causes unresponsive system because it ran out of memory and it took 30m to start TaskMgr) . And this 1809 is the last LTSC with 10 years support, later[LTSC like the 2021 only get 5 years till 2027, so this 1809 version gets support till 2029 (10 years after release).
So this 1809 testing VM will run a long time.

Are you able to update to LTSC 2021? This bug only affects legacy versions of Windows 10 while newer versions don't have issues.

This bug affects current version of Windows Server 2019, which will be supported until Jan 9, 2029.

@dmex I chose Server 2019 for all our workstations because of it's long update cycle, the official date when support ends is January 9th, 2029, but some MS officials have said it might be extended to 2031 if enough people still use it by 2029.
Also no, no (official) way to upgrade, either by ISO or from Server Manager, so I'm stuck with 1809.

@gettysburg Those statistics require symbols and are not available unless you've also installed the Windows SDK.

Weird, I have the Windows SDK set up correctly as well as the global symbol path, and symbols work for me out of the box in IDA 7.7, as well as other tools utilizing DbgHelp.dll.
Regarding an update, I checked and it seems you can't upgrade without having to reconfigure the entire system, there is no ISO or option in Server Manager to do an in-place upgrade.
We chose 2019 LTSC because of the long support cycle, lasting up to 2029, and with some luck, that will be extended by 2 years or they will package and deploy ESU's just like they did on Windows 7.

@gettysburg Those statistics require symbols and are not available unless you've also installed the Windows SDK.

Weird, I have the Windows SDK set up correctly as well as the global symbol path, and symbols work pretty much out of the box in IDA 7.7, as well as other tools utilizing DbgHelp.dll.
Regarding an update, I checked and it seems you can't upgrade without having to reconfigure the entire system, there is no ISO or option in Server Manager to do an in-place upgrade.
We chose 2019 LTSC because of the long support cycle, lasting up to 2029, and with some luck, that will be extended by 2 years or they will package and deploy ESU's just like they did on Windows 7.
P.S: Sorry for the repeat notifications, if there were any.

From https://github.com/winsiderss/systeminformer/discussions/1580:

The crash only affects people running old versions of Windows 10 from more than 5 years ago (1809 and older).

and

https://github.com/winsiderss/systeminformer/files/10521684/minidump.zip

Microsoft Windows [Version 10.0.18363.836]
... also, honestly, I'm not planning to exactly update - when UI changes became "mandatory" with the bug/security fixes, I decided that I like how my OS looks like.
And restarting my PC when I like it, not when Microsoft says so 😕

We've decided to temporarily change the minimum version to Windows 10 20H1 (10.0.19041) or newer until such time Microsoft resolve the issue. This means the kernel driver and the majority of features will be disabled unless you're running 20H1 or later.

This means the kernel driver and the majority of features will be disabled unless you're running 20H1 or later.

which features in detail? Maybe the team can add a Wiki page with some documentation about which features depends on the driver and which features are available on which Windows.

@DavidXanatos Most kernel structures are already public through the Microsoft symbol server, and if you have an IDA License and connect to Lumina, you get pretty much everything you need from IDA's public server.
But yes, that's likely whats causing the delay.

Any news?
Mid January was what you guys told us, now it almost 2 months later.
I rely on the kernel driver on some server machines..

The delays were escalated mid-February and we got things moving again. I received an email yesterday that we should be good to go this week. However, there are still some administrative items to attend to with respect to portal registration. I don't have a timeline for that. Hopeful that it will all get resolved soon.
I appreciate everyone's patience here. The delays have simply been out of our control. Microsoft has been slow, as somewhat expected, unfortunately. But, they've been understanding and have been working with us to resolve the issues. Kudos to the folks over there for their time.

ok, great to hear that there is some progress to resolve the issue

@stdedos I agree with you, they tend to not disclose some stuff, I too have tried in the past, but a resolution this or next week would be wonderful.

@stdedos I agree with you, they tend to not disclose some stuff, I too have tried in the past - however, a resolution this or next week sounds wonderful.
Good luck to everyone!

Is this fixed yet?
I am running 3.0.6397 (69f839c) but am hesitant to try it, last time I BSOD'd my system I was left with severe file corruption and had to re-install the OS.

Is this fixed yet?
I am running the latest version, 3.0.6397 (69f839c), but am hesitant to try loading the driver, last time I did and BSOD'd my system I was left with severe file corruption and had to re-install the OS - good thing I encrypt and sync everything important using a cloud service, but still..
An official statement would be nice, it has been 3 weeks yet again.. I know this is likely Microsoft's fault, but still.

Is this fixed yet?
Currently running the latest version, 3.0.6397 (69f839c), but I am hesitant to try loading the driver, last time I did and BSOD'd my system I was left with file corruption and had to re-install the OS - good thing I encrypt and sync everything important using a cloud service.
An official statement would be nice, it has been 3 weeks again.. I know this is likely Microsoft's fault, but I am still hoping for good news.

this is likely Microsoft's fault

Still waiting - see this statement: https://github.com/winsiderss/systeminformer/issues/1523#issuecomment-1458528637
This logic will notify if you're running on an OS that would encounter the bug: https://github.com/winsiderss/systeminformer/blob/master/SystemInformer/ksisup.c#L554

likely Microsoft's fault

That's an understatement.

Especially helping with System Informer, and internal Kernel stuff, feels very "unexpected"

Well... Zero kelvin is −273.15°C and defined as absolute zero and Microsoft are -273.14°C which is a slight improvement but still frozen or frosty and nothings changed 😄

BSOD'd my system I was left with file corruption and had to re-install the OS

Did you actually have file corruption or did you just see the automatic repair prompt?
https://user-images.githubusercontent.com/1306177/228565683-1bae541f-aab6-4437-9f6d-ba3495eb90fa.png

I encrypt and sync everything important using a cloud service.

Is this a virtual drive or physical (IDE/SATA/NVME)?

I am hesitant to try loading the driver

These crashes only affect legacy versions of Windows 10 prior 2018 and we made changes to prevent the driver running on legacy version of Windows until the issue is resolved 👍

I also notices the driver bricking a freshly installed windows 10 LTSC 2019 and yea the file system was garbage after wards, was less work to reinstall it than to try to find out which file goes where...

@dmex
Actual file corruption as confirmed by chkdsk, it tried it's best to do an offline repair but the Workstation would behave oddly even after a run of
sfc /scannow
and
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth

with no results, so I just reinstalled, syncing the data back only takes around 10 minutes or so, the most annoying part was that I lost my custom group policy too, which turned unneeded garbage such as Windows Defender and Firewall off, and much more, should backup and sync that as well.

Is this a virtual drive or physical (IDE/SATA/NVME)?

Actual physical SSD connected by SATA to my main-boards disk controller.
An idea to make file corruption less likely, perhaps, would be to open device manager, and completely turn off the write-caching for all physical drives when BSOD's or random power outages are likely, but I don't know if this just disables the software / RAM buffers or actually talks to the disk controller using the right IOCTL and disables the hardware write-buffer most drives have nowadays.
I should probably reverse engineer that.. would be interesting to know.

Any updates?
It's been another month and I am starting to develop a hatred for Microsoft, even considered switching back to ArchLinux on all my servers and then use QEMU/KVM along with Windows Server 2019 / 2022 Core if Windows is really needed for specific services.

We're waiting on a permanent fix from Microsoft. They unblocked us and we could sign existing submissions but new ones are getting denied.

Staging branch was merged. New driver release soon™. I greatly appreciate everyone's patience.

Apologies for my pedantic-ness:

What was the issue? (e.g. accessing Process handles)
What is the solution? (e.g. accessing the API in a Microsoft-sanctioned way)
Does the version-limiting apply still?

If yes, does it totally and fully disable the kernel driver unless v < 20H1?

tried to compile it on my own, first stacktrace was not found, so add C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.34.31933\include to additional includes, but now I get error STL1001: Unexpected compiler version, expected MSVC 19.34 or newer. but I use 17.4 LTSC

Apologies for my pedantic-ness:

What was the issue? (e.g. accessing Process handles)
What is the solution? (e.g. accessing the API in a Microsoft-sanctioned way)

That's a separate issue, but the fix is included. It's described here https://github.com/winsiderss/systeminformer/issues/1525#issuecomment-1345621261

Does the version-limiting apply still?

If yes, does it totally and fully disable the kernel driver unless v < 20H1?

No, all Win10 x64/ARM64 are supported.

compile also fails in VisualStudio 2022 Preview 17.6.0-pre.6.0+33626.354, here with this error message:
error C2220: the following warning is treated as an error [C:\Github\systeminformer\kphlib\kphlib_um.vcxproj]C:\Program Files\Microsoft Visual Studio\2022\Preview\VC\Tools\MSVC\14.36.32530\include\xlocale(1167,1): warning C5252: Multiple different types resulted in the same XFG type-hash D275361C54538B70; the PDB will only record information for one of them [C:\Github\systeminformer\kphlib\kphlib_um.vcxproj]
I'll wait for the next official nightly.

compiling works for debug on the 17.6 Preview6 and looks like it runs now on 1809:

Does the version-limiting apply still?

If yes, does it totally and fully disable the kernel driver unless v < 20H1?

No, all Win10 x64/ARM64 are supported.

I'm on the updater-latest version (cd8e90be2858d37dd3667828833f0d80a5b99c4d. 3.0.6550), and I am receiving

Is something else wrong, or am I missing something?

@stdedos
3.0.6550 doesn't include the changes? There hasn't been a nightly build released since 3.0.6550 as a precaution while we investigate #1668

Version 3.0.6772 (a7cce79) runs fine on 1809, I see the driver loaded, the ++ in Titlebar to indicate full driver usage

So the issue can be finally closed 🥳🙌😍


Deployment

Deployment
User Story
As a bootcamp student
I want the prework notes to be structured on a webpage
so that I can easily find and read information
Acceptance Criteria
GIVEN a Prework Study Guide website,
WHEN I visit the website using the URL,
Then I can access my website from any browser

website now in live environment at https://tomking151183.github.io/prework-study-guide/


Regex in macros

I notice that the documentation talks about regexes in the readtables and their extensions, but is there an example of how one could use it in macros -- how to use it in the pattern match and how to refer to the matches in the template? Apologies in advance if I've misunderstood or missed something there. :-)

One particular case where a separate check with macros won't work is when the match is allowed with anything for a prefix or suffix.
Consider for example the case where we convert js stype method access to a schemeified version; i.e
(.bar foo) gets converted to foo.bar. Normally, patterns of the form (fn args) get expanded to fn(args), but in this case, when the first char in the function name starts with ., we want to do something different in the expansion.
One would imagine that a rule case, like the following, would help
...
case {_ ($name:./\([^.]+\)/ $obj) } => { return #{ $obj.$name$1 }}
...

by using a regexp to catch the specific cases where the name is an identifier beginning with a . and then using the regexp matched group within the template body.

This is basically what macroclass is for:
macroclass dot_ident {
  rule { . $name:ident }
}

macro sexp {
  rule { ($fn:dot_ident $arg) } => { $arg.$fn$name() }
  rule { ($fn:ident     $arg) } => { $fn($arg) }
}

sexp (foo bar)
sexp (.foo bar)

foo(bar);
bar.foo();

You can reference the submatch components. In this case $fn$name. Identifiers can't start with a . (its a separate token) so it doesn't really make sense to use a regular expression.

Ah, I see. Thanks!
I thought the space in setting up the macroclass would be significant, in that it would somehow need to be present in the pattern, that's why I didn't go down that route.


Improve automated tests

This is a request we just discussed with @peterdesmet, I plan to tackle that in the near future (can someone assign me?):

Start with existing tests in https://github.com/tdwg/camtrap-dp/blob/main/tests/validate_schemas.py (this is run frequently via GH actions, each time a change is done to the camtrap-dp standard)
Apparently, it already check 4 files are valid JSON (good!) and that they are a valid table schema (not sure exactly what that covers, but looks good)

Improvements needed:

Add a third test that validates that the example camtrap-dp package (will be provided in #118) is still compliant with the (just updated) new version of the standard?
Also validate (what? the example package?) against camtrap-dp profile. (is this with frictionless.py validate)?
Make code a bit cleaner/shorter/more pythonic (+ docstrings to state what it does)
Make the output (visible on GitHub actions) a bit nicer (more clear and readable)

Regarding the check whether something is a valid Table Schema, can you check if you need tableschema-py or if you can do it with frictionless-py validate_schema?  If possible with the latter, then we only use one, maintained library (frictionless-py).

Regarding a validate_examples.py: to avoid confusing users, the example will always point to a stable version of Camtrap DP (as real datasets should), so testing the example as a whole will not test it against the latest changes on a branch. Luckily, we can overwrite that (here written in CLI, should become Python):

cd example
# Will have to look up if it is possible to validate metadata against external profile
frictionless validate deployments.csv --schema-sync --schema ../deployments-table-schema.json
frictionless validate multimedia.csv --schema-sync --schema ../multimedia-table-schema.json
frictionless validate observations.csv --schema-sync --schema ../observations-table-schema.json

Somewhat fancier stuff, but it might be good to test as well if the example datapackage.json references the latest version of Camtrap DP. Can be done by searching for the 4 occurrences of https://raw.githubusercontent.com/tdwg/camtrap-dp/, which should be followed by the latest tag name.

@niconoe to validate the metadata of the package, you'll have to validate the whole package, but then select the metadata errors only: Package.metadata_errors. I'm not sure yet how you can validate against an external profile. Maybe by loading it and then updating the profile link?

@niconoe The example is available in the example branch. Might be good to add validation test on that branch as well.

Apparently our own profile does not allow schema to be an URL: https://github.com/frictionlessdata/frictionless-py/issues/935
I haven't really jumped into JSON schema: @peterdesmet: do you know an easy way to solve that? Otherwise I'll investigate further!
Not sure I understand the issue fully: I'm also a bit surprised that our custom profile can overwrite the properties of schema, as it is defined by the Frictionless standard. A related question is: will the "validate" commands follow the URLs and interpret the content behind, or just consider it as a string in that case.

Ok, I'm trying to debug by creating a test.py in the root, that has:
import json
from pprint import pprint
from frictionless import validate_package

with open("example/datapackage.json") as json_file:
  descriptor_data = json.load(json_file)

  report = validate_package(descriptor_data)
  for err in report.errors:  # report.valid is False
    pprint(err)

I am currently getting:
{'code': 'scheme-error',
 'description': 'Data reading error because of incorrect scheme.',
 'message': 'The data source could not be successfully loaded: [Errno 2] No '
            "such file or directory: 'deployments.csv'",
 'name': 'Scheme Error',
 'note': "[Errno 2] No such file or directory: 'deployments.csv'",
 'tags': []}

Why can it not find deployments.csv? Is it looking for it from the root?

Update, if I place my test.py in the example dir it works. It also doesn't generate the error you mentioned in frictionless 935.

@peterdesmet: Do I understand correctly that you don't see any error in the console if you create a test.py file in the example dir, and execute it with something like:
$ cd example
$ python test.py

Can you tell me the packages installed on your environment (pip freeze) Python version in use (Python -V)?
With Python 3.8.6 and the last version of frictionless-py (4.20.2), I still get:
{'code': 'package-error',
 'description': 'A validation cannot be processed.',
 'message': 'The data package has an error: '
            '"\'https://raw.githubusercontent.com/tdwg/camtrap-dp/0.1.6/deployments-table-schema.json\' '
            'is not of type \'object\'" at "resources/0/schema" in metadata '
            'and at '
            '"allOf/0/properties/resources/items/properties/schema/type" in '
            'profile',
 'name': 'Package Error',
 'note': '"\'https://raw.githubusercontent.com/tdwg/camtrap-dp/0.1.6/deployments-table-schema.json\' '
         'is not of type \'object\'" at "resources/0/schema" in metadata and '
         'at "allOf/0/properties/resources/items/properties/schema/type" in '
         'profile',
 'tags': []}

Sorry to bother you, but it seems we encounter difficulties to get a consistent result, so I'd like to understand that better.

Do I understand correctly that you don't see any error in the console if you create a test.py file in the example dir, and execute it with something like:

Correct.
Pip freeze:

alabaster==0.7.12
aniso8601==8.1.0
appnope==0.1.0
argcomplete==1.12.1
attrs==19.1.0
awscli==1.16.165
awsebcli==3.15.2
Babel==2.9.0
backcall==0.1.0
beautifulsoup4==4.6.3
bitarray==1.5.3
bleach==3.1.0
blessed==1.15.0
blinker==1.4
boto3==1.14.51
botocore==1.17.51
cached-property==1.5.1
cement==2.8.2
Cerberus==1.2
certifi==2020.12.5
chardet==3.0.4
click==7.1.2
click-default-group==1.2.2
colorama==0.4.4
commonmark==0.9.1
datapackage==1.15.1
decorator==4.4.0
defusedxml==0.6.0
docker==3.7.2
docker-compose==1.23.2
docker-pycreds==0.4.0
dockerpty==0.4.1
docopt==0.6.2
docutils==0.14
entrypoints==0.3
et-xmlfile==1.0.1
feedgenerator==1.9.1
Flask==1.1.2
Flask-RESTful==0.3.8
frictionless==4.12.4
-e git+https://github.com/timrobertson100/frictionless-transforms.git@1e2ed7585f1d1777672b94aa54b374af5fcabcd7#egg=frictionless_transforms
FrictionlessDarwinCore==1.0.0
future==0.16.0
goodtables==2.5.1
h5py @ file:///opt/concourse/worker/volumes/live/98bee3fd-2687-4017-5421-d742d1f18c35/volume/h5py_1593454156895/work
idna==2.7
ijson==3.1.1
imagesize==1.2.0
importlib-metadata==2.0.0
ipykernel==5.1.0
ipython==7.5.0
ipython_genutils==0.2.0
ipywidgets==7.4.2
isodate==0.6.0
itsdangerous==1.1.0
jdcal==1.4.1
jedi==0.13.3
Jinja2==2.10.1
jinjasql==0.1.8
jmespath==0.9.4
jsonlines==1.2.0
jsonpath-ng==1.5.2
jsonpointer==2.0
jsonschema==2.6.0
jupyter==1.0.0
jupyter-client==5.2.4
jupyter-console==6.0.0
jupyter-core==4.4.0
linear-tsv==1.1.0
Markdown==3.0.1
MarkupSafe==1.1.1
mistune==0.8.4
mkl-fft==1.0.12
mkl-random==1.0.2
nbconvert==5.5.0
nbformat==4.4.0
notebook==5.7.8
numpy==1.16.3
openpyxl==3.0.5
packaging==20.8
pandas==0.24.2
pandocfilters==1.4.2
parso==0.4.0
pathspec==0.5.9
pelican==4.0.0
petl==1.7.2
pexpect==4.7.0
pickleshare==0.7.5
ply==3.11
prometheus-client==0.6.0
prompt-toolkit==2.0.9
psycopg2==2.8.6
ptyprocess==0.6.0
pyaml==17.12.1
pyasn1==0.4.5
pybloom-live==3.0.0
Pygments==2.4.0
pyodbc==4.0.30
pyparsing==2.4.7
pyrsistent==0.14.11
python-dateutil==2.8.1
python-dwca-reader==0.13.0
python-slugify==4.0.1
pytz==2019.1
pywhip==0.3.2
PyYAML==5.3.1
pyzmq==18.0.0
qtconsole==4.4.4
recommonmark==0.6.0
requests==2.22.0
rfc3986==1.4.0
rfc3987==1.3.7
rsa==3.4.2
s3transfer==0.3.3
semantic-version==2.5.0
Send2Trash==1.5.0
shellingham==1.4.0
simpleeval==0.9.10
simplejson==3.17.2
six==1.12.0
snowballstemmer==2.0.0
Sphinx==3.3.1
sphinx-markdown-tables==0.0.15
sphinx-rtd-theme==0.5.0
sphinxcontrib-applehelp==1.0.2
sphinxcontrib-devhelp==1.0.2
sphinxcontrib-htmlhelp==1.0.3
sphinxcontrib-jsmath==1.0.1
sphinxcontrib-qthelp==1.0.3
sphinxcontrib-serializinghtml==1.1.4
SQLAlchemy==1.3.19
statistics==<IP_ADDRESS>
strict-rfc3339==0.7
stringcase==1.2.0
tableschema==1.19.3
tableschema-sql==1.3.1
tabulate==0.8.7
tabulator==1.52.3
termcolor==1.1.0
terminado==0.8.2
testpath==0.4.2
text-unidecode==1.3
texttable==0.9.1
tornado==6.0.2
traitlets==4.3.2
typer==0.3.2
unicodecsv==0.14.1
Unidecode==1.1.1
urllib3==1.24.3
validators==0.18.2
wcwidth==0.1.7
webencodings==0.5.1
websocket-client==0.56.0
Werkzeug==1.0.1
widgetsnbextension==3.4.2
xlrd==1.2.0
xlwt==1.3.0
xmltodict==0.12.0
zipp==3.3.0

Python -V: Python 3.7.3

Thanks @peterdesmet, at least we have consistent behaviour now. I think the next step is to confirm an update is needed to our own profile to allow objects there (as suggested by roll in https://github.com/frictionlessdata/frictionless-py/issues/935).
We should indeed into this together. Prior to that, I plan to read a bit more about JSON schemas, frictionless specs, ... so far I have some trouble wrapping my brain around some concepts.

@niconoe the bug has been fixed in the Frictionless specs. If I run the example/test.py above it returns without error (using frictionless==4.22.0). I guess that means you can finish a PR?

Great! Indeed, I'll go back to this issue very soon.

Quick update:

validation against versioned schemas is now implemented.
While working on that, I also submitted an issue to frictionless about the problem you discovered on Nov 4: https://github.com/frictionlessdata/frictionless-py/issues/956 (which I also faced, and looks like a bug to me).
I'll now go back to the validation against current schemas

@peterdesmet : validation against current schemas is now implemented. I think we're close.
I guess you'll need to merge into main before we can test the thing fully (because GitHub actions that react to push events on this branch)

Automated tests run without issues: https://github.com/tdwg/camtrap-dp/actions Thanks @niconoe!


Implement option to sort properties, methods, constants and traits

This simple PR adds the possibility for the user to decide if the properties, methods, constants and traits get sorted on the class page. This can be done by simple defining a truthy value (true), to sort by lexicographical (used gets uksort). It's also possible to define a callable, which then gets passed to uksort.
New options available:
sort_class_properties
sort_class_methods
sort_class_constants
sort_class_traits
sort_class_interfaces
Fixes #319.

The isInterface and isTrait method got changed because fabbot complained about them.


Upgrading to new versions of DearPyGui v1.X

Changes

All updated and working with the new latest version of DearPyGui 1.8.0
Added function dpg_get_alpha_style to replace set_item_style_var(item[0], mvGuiStyleVar_Alpha, [item[1])
Updated demo: the theme from the old DPG version is set, removed add_value("running_animations", "0"), slightly resized some windows
Updated example in README

Bugs
If there is a theme that is attached not only to a changeable/animated object, then other objects will change their values.
To reproduce:
import dearpygui.dearpygui as dpg

import dearpygui_animate as animate

dpg.create_context()
dpg.create_viewport()

with dpg.theme() as button_theme:
    with dpg.theme_component(dpg.mvButton):
        dpg.add_theme_color(dpg.mvThemeCol_Text, (0, 255, 0, 255), category=dpg.mvThemeCat_Core)

with dpg.window():
    btn1 = dpg.add_button(label="Test 1")
    btn2 = dpg.add_button(label="Test 2")

    dpg.bind_item_theme(btn1, button_theme)
    dpg.bind_item_theme(btn2, button_theme)

animate.add("opacity", btn1, 0, 1, [.57, .06, .61, .86], 60, loop="ping-pong")

dpg.setup_dearpygui()
dpg.show_viewport()
while dpg.is_dearpygui_running():
    animate.run()
    dpg.render_dearpygui_frame()
dpg.destroy_context()

The workaround is to wrap each future animated object into a group:
import dearpygui.dearpygui as dpg

import dearpygui_animate as animate

dpg.create_context()
dpg.create_viewport()

with dpg.theme() as button_theme:
    with dpg.theme_component(dpg.mvButton):
        dpg.add_theme_color(dpg.mvThemeCol_Text, (0, 255, 0, 255), category=dpg.mvThemeCat_Core)

with dpg.window():
    with dpg.group() as btn1_group:
        btn1 = dpg.add_button(label="Test 1")
    btn2 = dpg.add_button(label="Test 2")

    dpg.bind_item_theme(btn1, button_theme)
    dpg.bind_item_theme(btn2, button_theme)

animate.add("opacity", btn1_group, 0, 1, [.57, .06, .61, .86], 60, loop="ping-pong")

dpg.setup_dearpygui()
dpg.show_viewport()
while dpg.is_dearpygui_running():
    animate.run()
    dpg.render_dearpygui_frame()
dpg.destroy_context()

Unfortunately for dpg.window() you need to create a new theme

Hi @IvanNazaruk , that is awesome! I merge your work and update the demo (there was a warning that add_spacing() is deprecated.


how to reboot after qdl flash

wouldu pls add reboot to normal/power on funtion?

It already has reboot function, but maybe it can't works.
Please try this patch, it seems work but I don't know why.
diff --git a/firehose.c b/firehose.c
index 319bac8..d9ad588 100644
--- a/firehose.c
+++ b/firehose.c
@@ -652,6 +652,7 @@ int firehose_run(struct qdl_device *qdl, const char *incdir, const char *storage
firehose_set_bootable(qdl, bootable);
    firehose_reset(qdl);

  firehose_reset(qdl);

  return 0;

}


Fix so that Rule can be subclassed

Swift 3 is adding 2 more access levels (open and fileprivate) and changing the meaning of private:
private: symbol visible within the current declaration only.
fileprivate: symbol visible within the current file.
internal: symbol visible within the current module.
public: symbol visible outside the current module.
open: for class or function to be subclassed or overridden outside the current module.
In Swift 3 you can now mark a class as open instead of public this allows files outside of the module to subclass that class.

Codecov Report

Merging #177 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #177   +/-   ##
=======================================
  Coverage   80.82%   80.82%
=======================================
  Files          26       26
  Lines         485      485
=======================================
  Hits          392      392
  Misses         93       93

Impacted Files
Coverage Δ

SwiftValidator/Rules/RegexRule.swift
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 2a6c23a...8da602c. Read the comment docs.

Sorry for the delay @jspenc72 I don't do Swift in my day-to-day and this project is suffering. Would you be interested in becoming a contributor?

I'd be happy to be a contributor.

On Jul 9, 2017, at 5:22 PM, Jeff Potter<EMAIL_ADDRESS>wrote:
Sorry for the delay @jspenc72 I don't do Swift in my day-to-day and this project is suffering. Would you be interested in becoming a contributor?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

@jspenc72 I"ve added you as a contributor can you please merge these changes and make sure any necessary documentation and tests are added that prove the functionality changes. Still learning about permissions on organization so let me know if you see any hiccups

Ill have a look tonight and get things merged in.

@jspenc72 This was addressed in #175

Thanks for letting me know

On Jul 16, 2017, at 2:58 PM, David Patterson<EMAIL_ADDRESS>wrote:
@jspenc72 This was addressed in #175
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.


Add Adminca to wiki community links

At Adminca, we created a data browser for Parse Server. It could be very useful for anyone looking for a free admin panel before the dashboard is released. Would it be possible to add it to the wiki under community links? Thanks!
http://adminca.com

Done, added the wiki link. :+1:
The real dashboard is released now though: http://blog.parse.com/announcements/introducing-the-parse-server-dashboard/

Thank you very much!
Indeed, and I believe it can be used in combination.


默认值只设置了default Value，没有设置zod的默认值

Description
修复之前设置嵌套对象的默认值只设置了default Value，覆盖了zod设置的默认值
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update
[ ] Please, don't make changes to pnpm-lock.yaml unless you introduce a new test example.

Checklist

ℹ Check all checkboxes - this will indicate that you have done everything in accordance with the rules in CONTRIBUTING.

[ ] If you introduce new functionality, document it. You can run documentation with pnpm run docs:dev command.
[ ] Run the tests with pnpm test.
[ ] Changes in changelog are generated from PR name. Please, make sure that it explains your changes in an understandable manner. Please, prefix changeset messages with feat:, fix:, perf:, docs:, or chore:.
[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules

Summary by CodeRabbit

New Features

Enhanced form validation by utilizing field rules for schema construction instead of default values.

Bug Fixes

Improved handling of non-string rules in form initialization, leading to more accurate validation.

该PR所依赖的commit已经被撤回，请重新提交。


Add LiveContributorRelationship to interact live thread's contributors

Feature Summary and Justification
This feature provides interface for live thread's contributors. Usage:
thread = reddit.live('ukaeu1ik4sw5')
rel = thread.contributor  # LiveContributorRelationship
redditors = rel()  # RedditorList

LiveContributorRedditorList returns RedditorList rather than ListingGernarator because /live/:thread_id/contributors doesn't implement listing interface, e.g., https://www.reddit.com/live/ta535s1hq2je/contributors.json
References

#676
https://www.reddit.com/dev/api#GET_live_{thread}_contributors

Concerns
I got warning when I ran pre_push.py
Warning, treated as error:
docstring of praw.models.LiveThread.contributor:1: WARNING: py:class reference target notfound: LiveContributorRelationship

How can I resolve this error?

To resolve WARNING: py:class reference target notfound: LiveContributorRelationship a new file needs to be added like: https://github.com/praw-dev/praw/blob/master/docs/code_overview/other/contributorrelationship.rst. And an entry needs to be made in: https://github.com/praw-dev/praw/blob/master/docs/code_overview/other.rst

You can remove your second commit. For some reason the python 2.7 travis build didn't report to coveralls which is the one that provides coverage for that line.

Updated. Maybe too much git commit --amend 🤕 Sorry for the confusion.

Edit: To confirm, I re-ran travis for python 2.7 on f3adde5 and coveralls passed.

No worries. --amend is good. Thanks!


Add optional progress callback to TraceLog.OpenOrConvert

It would be very handy to know that TraceLog.OpenOrConvert is chugging along, and have an idea of when it is going to be done.
I'm considering writing some PowerShell scripts to pull some data out of arbitrary ETL traces, and it's kind of a bummer to just sit there at the console with no indication if progress is being made. Even traces that aren't "huge" take much longer than my don't-need-progress comfort level allows.
It could be as simple as an Action<int> that lets OpenOrConvert report percent done (0-100). Or perhaps something a little richer, to allow reporting a bit more information (maybe a string indicating "current operation", or number of events processed, etc.).
Care should be taken not to report progress too frequently, lest the overhead of reporting progress accidentally dominate the real work (so perhaps no more frequently than every few seconds).
What do you think?

And perhaps an optional CancellationToken could be added at the same time.

@jazzdelightsme this is an interesting idea.  If you're just looking for some sign that things are moving, take a look at TraceLogOptions.ConversionLog.  This is what PerfView uses to display status during TraceLog conversion.
If you do want to have a percentage-based model, it would be a best-effort type thing, but seems reasonable to me.  Expect that this would need to come from the community, but we would gladly accept a PR.


do not configure logging for AllowRoot commands

I'm merging over this TestEphemeralTeambotEK flake, 4th time today


Emacs complains about missing arch-dependent data dir

Running emacs from current master gives the following (non-fatal) warning:
$ emacs
Warning: arch-dependent data dir '/nix/store/9ng0phrd7gx72r2gk78lfpcav4k84sl4-emacs-25.1/libexec/emacs/25.1/x86_64-unknown-linux-gnu/': Not a directory

It looks like makeWrapper is getting invoked on the directory /libexec/emacs, and happily trying to produce a nonsense wrapper script for it.  The directory itself gets renamed to .emacs-wrapped.

The culprit is wrapGAppsHook:
  if [ -z "$dontWrapGApps" ]; then
    for i in $prefix/bin/* $prefix/libexec/*; do
      echo "Wrapping app $i"
      wrapProgram "$i" "${gappsWrapperArgs[@]}"
    done
  fi

I'm working on a fix

Looks to be fixed. Reopen if it's not. Thanks!


Multiple object types, but only one got output

🐛 Summary
When there are multiple object types in one packet, zeek only output one.
For example, There are 20 packets in test.pcap, and no.1 has two object types (device and accumulator) as shown in the screenshot of Wireshark. But after I ran this command, zeek-Cr test.pcap /usr/local/zeek/share/zeek/site/icsnpp-bacnet/main.zeek, the object_type is output as “accumulator” only in bacnet_discovery.log.
Another example is the no.18 got 8 object types. However, after I ran this command, zeek-Cr test.pcap /usr/local/zeek/share/zeek/site/icsnpp-bacnet/main.zeek, the object_type is output as “schedule” only in bacnet_property.log.
For further confirmation, I output this pcap by tshark, and each object type has output.
To reproduce
Run zeek-Cr test.pcap /usr/local/zeek/share/zeek/site/icsnpp-bacnet/main.zeek
Expected behavior
Logic for which object type should be output
Any helpful log output
#bacnet_discovery.log for no.1
1692099997.714948	CyFXcfmZiqRZeZJ4b	<IP_ADDRESS>	47808	<IP_ADDRESS>	47808	T	i-have	accumulator	4	-	-	(empty)

#bacnet_property.log  for no.18
1692099997.715010	Cuoso93BOASnNw524i	<IP_ADDRESS>	47808	<IP_ADDRESS>	47808	T	94	read-property-ack	schedule	385	Vendor Specific (71303554)	-	schedule: 388

Add any screenshots of the problem here.
no.1

no.18

test.pcap
test.pcap.zip
For further information,
log output by tshark for no.1
1692099997.714948000	<IP_ADDRESS>	<IP_ADDRESS>	i-Have (1)	47808	Unconfirmed-REQ (1)	device
1692099997.714948000	<IP_ADDRESS>	<IP_ADDRESS>	i-Have (1)	47808	Unconfirmed-REQ (1)	accumulator

log output by tshark for no.18
1692099997.715010000	<IP_ADDRESS>	<IP_ADDRESS>	readProperty (12)	47808	Complex-ACK (3)	binary-input
1692099997.715010000	<IP_ADDRESS>	<IP_ADDRESS>	readProperty (12)	47808	Complex-ACK (3)	binary-output
1692099997.715010000	<IP_ADDRESS>	<IP_ADDRESS>	readProperty (12)	47808	Complex-ACK (3)	binary-value
1692099997.715010000	<IP_ADDRESS>	<IP_ADDRESS>	readProperty (12)	47808	Complex-ACK (3)	device
1692099997.715010000	<IP_ADDRESS>	<IP_ADDRESS>	readProperty (12)	47808	Complex-ACK (3)	group
1692099997.715010000	<IP_ADDRESS>	<IP_ADDRESS>	readProperty (12)	47808	Complex-ACK (3)	notification-class
1692099997.715010000	<IP_ADDRESS>	<IP_ADDRESS>	readProperty (12)	47808	Complex-ACK (3)	schedule
1692099997.715010000	<IP_ADDRESS>	<IP_ADDRESS>	readProperty (12)	47808	Complex-ACK (3)	accumulator

Fixed see PR #38


branch wrap

Use div contenteditable true to get widths to adjust automatically.
Have we tried just doing input display: inline instead???
We should TRY that.
We SHOULD DO THE SETTINGS DROPDOWN BEFORE DEALING WITH THIS.

I am so sorry.  This issue was meant for my personal repo.


No speed controll

I has trying to change the speed of an animation and nothing happened, I thought it was my config but it looks like it isn't in the arduino code

It works here, I'm thinking maybe you changed something in the Yaml and forgot some changes?

It works here, I'm thinking maybe you changed topic and forgot some changes in the YAML file?

Sorry about the issue! So you have the slider in Home Assistant? It's just not causing an effect on the LED strip?
Try running the command mosquitto_sub -d -u yourMQTTusername -P yourMQTTpassword -t "#" on the same device that hosts your MQTT broker. Do you see published info with the transition information when you move the slider in HA?

Closing issue because of inactivity. Feel free to open another one if you have issues. Cheers!


aiohttp: connexion.apis.aiohttp_api.AioHttpApi.get_response is called twice

Description
After enable debug logging, I get the output of connexion.apis.aiohttp_api.AioHttpApi.get_response twice.
IMHO (after digging through the lines) there is some unnecessary code execution involved (a lot of while asyncio.iscoroutine(response): response = yield from response) together with the intend to inevitably cast a ConnexionResponse to a aiohttp.web.Response, which looks like a kind of ambiguity in the framework design...
Expected behaviour
connexion.apis.aiohttp_api.AioHttpApi.get_response is only executed once.
Actual behaviour
After enable debug logging, I get the output of connexion.apis.aiohttp_api.AioHttpApi.get_response twice.
Steps to reproduce
Use aoihttp (I am not sure if this is really mandatory), enable debug logging and make a request.
Additional info:
Output of the commands:

python --version
Python 3.6.5
pip show connexion | grep "^Version\:"
Version: 1.5.2

hey @diefans , thanks for reporting this issue.
I'm really unfamiliar with the aiohttp and async stuff, but maybe @dutradda has some insights?
If you figure it out, and want to supply a pull request, that would be really great!

hi @diefans , can you confirm that this was resolved along with #663 when #600 was merged and released?

This issue still persist in 1.5.3:
2018-09-20T08:03:24.720044Z [debug    ] Getting data and status code   [connexion.apis.aiohttp_api] has_body=False url=http://localhost:8080/python_ci_microservice_helm_test/_get_my_stuff_done
2018-09-20T08:03:24.720369Z [debug    ] Function Arguments: ['request_ctx'] [connexion.decorators.parameter]
2018-09-20T08:03:24.720495Z [debug    ] Body parameter 'None' not in function arguments [connexion.decorators.parameter]
2018-09-20T08:03:24.720763Z [debug    ] Getting data and status code   [connexion.apis.aiohttp_api] data=<Response OK not prepared> url=http://localhost:8080/python_ci_microservice_helm_test/_get_my_stuff_done
2018-09-20T08:03:24.721596Z [debug    ] Got data and status code (200) [connexion.apis.aiohttp_api] data=b'{}' url=http://localhost:8080/python_ci_microservice_helm_test/_get_my_stuff_done
2018-09-20T08:03:24.722783Z [debug    ] Getting data and status code   [connexion.apis.aiohttp_api] data=<Response OK not prepared> url=http://localhost:8080/python_ci_microservice_helm_test/_get_my_stuff_done
2018-09-20T08:03:24.722910Z [debug    ] Got data and status code (200) [connexion.apis.aiohttp_api] data=b'{}' url=http://localhost:8080/python_ci_microservice_helm_test/_get_my_stuff_done


Audio stream support

I found this library while finding the ScreenCaptureKit library. I want to record audio but i guess, add_stream_output is hard-corded to 0(SCStreamOutputType::Screen).
https://github.com/svtlabs/screencapturekit-rs/blob/f2327fc1206fc7f32918aed3fea2de0775b8ac36/screencapturekit-sys/src/stream.rs#L76C1-L77C1

Good catch!
I'll see if I can add a fix this week or if you want you are free to do a PR.

I've added plumbing to pass the correct flag to the SCStream. But audio support still needs to be implemented for the CMSampleBuffer. But you can use the sys_ref in the meantime to access audio data (would require FFI and unsafe though).

Thanks for your quick reply. stream.add_stream_output(StoreAudioHandler { tx }, 1); can provide me a CMSampleBufferRef, that contain the audio, maybe.
but so, I may need to implement following part of the Apple's sample code.
private func createPCMBuffer(for sampleBuffer: CMSampleBuffer) -> AVAudioPCMBuffer? {
    var ablPointer: UnsafePointer<AudioBufferList>?
    try? sampleBuffer.withAudioBufferList { audioBufferList, blockBuffer in
        ablPointer = audioBufferList.unsafePointer
    }
    guard let audioBufferList = ablPointer,
          let absd = sampleBuffer.formatDescription?.audioStreamBasicDescription,
          let format = AVAudioFormat(standardFormatWithSampleRate: absd.mSampleRate, channels: absd.mChannelsPerFrame) else { return nil }
    return AVAudioPCMBuffer(pcmFormat: format, bufferListNoCopy: audioBufferList)
}

https://developer.apple.com/documentation/screencapturekit/capturing_screen_content_in_macos
I tried to port this to rust, but i can't do it since i'm not familiar with Apple programming 😢


Add clustering and partitions nav item to rabbitmq docs

This adds the new partitions page into the rabbitmq service nav. Sibling to this pull request

@BenChapman
Thanks! perfect work on the subnav.


Portal rendering

https://torinmr.github.io/cs148/
https://th0mas.nl/2013/05/19/rendering-recursive-portals-with-opengl/

Todo:
Refactor Code
Create actual ring
Decide on elliptical / box

Notes: tried stencil buffer way but far too annoying to debug in Three.js and not very intuitive either
reference: https://medium.com/machine-words/creating-portals-in-three-js-944c4f7104ec
Instead used texture rendering along with custom screen-space shader:
https://danielilett.com/2020-01-19-tut4-6-portal-recursion/

Note: used renderer .clippingPlanes, is a builtin oblique view frustum

refactoring: create arrays of portals and render targets, and create functions that take in indices to them


Validator doesnt work with deleted at

Hello everyone,
My English might be not good. Sorry before start.
In my project, I am using validator to check if column is unique in database. Also I am using SoftDeletes which keeps values in database and insert date of deleted. So if I delete a row, and try to add again it gives me error. So validator doesnt valid with SoftDelete.
I hope, i explain everything clear.
Thanks

You can do the following:
'email' => 'unique:users,email_address,NULL,id,deleted_at,NOT_NULL'
This will make the validator count only rows with deleted_at <> NULL will be included in the check, that means way only available models will be considered, but take care when you restore a deleted model you have to check other models first in order to avoid a duplication of a value that should be unique.

Again, Laravel is just awesome.
Thanks :)

Just in case, the last not_null supposed to be null.


fix(scripts): 'build' script does not require env. variables to run in local

Description
When running npm run build in local environment:

Does not require to setup $GITHUB_WORKSPACE unless it's GitHub Actions environment
Fallbacks to current directory if $ANICCA_REPOSITORY_PATH is not defined (@gr2m not sure if this is correct or this variable should always have a certain path, if so, let me know and I will improve the CONTRIBUTING.md to explain that.

Context
When running npm run build in local environment is not possible unless you define $GITHUB_WORKSPACE and $ANICCA_REPOSITORY_PATH.
Fixes #185

Thanks for your help!

* Fallbacks to _current directory_ if `$ANICCA_REPOSITORY_PATH` is not defined (@gr2m not sure if this is correct or this variable should always have a certain path, if so, let me know and I will improve the `CONTRIBUTING.md` to explain that.

Only ANICCA_REPOSITORY_PATH is required when running locally. It has to be set to the path of a local clone of https://github.com/xuorig/anicca


Email Automation: Type checking is not consistent.

The types outlined in autoemails/actions.py while helpful are not always correct. There are several places indicated where the typing needs to be changed in order to reflect the inputs and outputs of method calls. Typically something like incorrect return values. Making this ticket so I don't forget.

@pbanaszkiewicz  can we close this given we are planning to entirely revamp the email automation service?

Yes, I think so.


feat: add DuckDuckGo search functionality using duckduckgo_search library

Pull Request Checklist
Note to first-time contributors: Please open a discussion post in Discussions and describe your changes before submitting a pull request.
Before submitting, make sure you've checked the following:

[x] Target branch: Please verify that the pull request targets the dev branch.
[x] Description: Provide a concise description of the changes made in this pull request.
[x] Changelog: Ensure a changelog entry following the format of Keep a Changelog is added at the bottom of the PR description.
[x] Documentation: Have you updated relevant documentation Open WebUI Docs, or other documentation sources?
[x] Dependencies: Are there any new dependencies? Have you updated the dependency versions in the documentation?
[x] Testing: Have you written and run sufficient tests for validating the changes?
[x] Code review: Have you performed a self-review of your code, addressing any coding standard issues and ensuring adherence to the project's coding standards?
[x] Prefix: To cleary categorize this pull request, prefix the pull request title, using one of the following:

feat: Introduces a new feature or enhancement to the codebase

Changelog Entry
Description

Added DuckDuckGo search functionality using the duckduckgo_search library, providing a new option for web search capabilities.

Added

🌐 New Web Search Provider: I have added DuckDuckGo as a new option for web search providers, giving you more choices for your search needs. (No API Key required)

Thanks!

Thank you so much @Yash-1511 , this is exactly what I've wanted. Cheers!

Super! Thanks for the effort!


Make the list of excluded states complete

JIRA issue: DCOS_OSS-5370

Can one of the admins verify this patch?

test this please

test this please

test this please

test this please

test this please

test this please

test this please


[WIP] Refactor how the processors are configured and instantiated

Q
A

Branch?
2.0

Bug fix?
no

New feature?
yes

BC breaks?
yes

Deprecations?
no

Tests pass?
no

License
MIT

The aim of this PR is to refactor entirely how the processors are configured, instantiated and executed. The problems I see in the current code are:

The order in which the processors are executed is the order in which they gets added to the configuration. While I don't have any real use case this is a problem, I think it would be better to be able to customize the order in a more efficient way
There isn't a clear way to define the options of the processors. The only way is to copy-paste a lot of code to validate that each option is correct, etc. By using the OptionsResolver component from Symfony this task is simplified and we have a standard way to define the options that each processor accepts
The processors can't be lazy-created, nor they can have different constructor arguments because the instantiation of the objects is handled internally by the client. This is where the factory pattern applies: by having a factory class the client won't need anymore to know how a processor should be created. We could even provide in the framework packages a factory that uses the service container

This PR is a work in progress, so please do not take any step to review it in a serious manner.

No, I just created the branch of this PR from the branch of #462 because I need those changes. When that PR will be merged the duplicated commit will disappear

So I will review it after #462 merging. Because I can not see there #462 is ending and #472 is starting

While working on this, I faced some issues I'm not sure how to properly solve @Jean85 @nokitakaze @stayallive
Actually the options of the processors are configured in the processors_options config option and then passed during instantiation to the Raven_Processor::setProcessorOptions method. This means that in the constructor of the class there are not all available information needed to start operating or configuring the processor. The solution proposed in this PR tries to solve the problem by passing them directly in the constructor. However, this introduces an hard dependency on the definition of the constructor that must now mandatorily accept a given amount of parameters in a certain order. I don't really like that, considering that some processors may need 3rd parties dependencies. Indeed, users needing that must create another factory that handle the instantiation of these types (e.g. processors defined as services of a service container) but this would mean that the instance of the processor will be returned pre-configured, introducing another problem: some processors would be configured using the client configuration, others using some other code outside of our control. I'm not sure this can be solved in a better way, I just want your opinion on how to proceed. If this way of doing things is fine, I will finish this PR as soon as possible, otherwise we should go back to the table and rethink the whole PR to address these inconsistencies

I'm not able to delve into the code at the moment, but IMHO we should strive to move the options in the constructor. Can we write down the cases that we need to cover right now to decide better about this?

I think, if there will be need of adding IoC with self made objects, user could just create his own factory. But it will be better if user could extend default factory and just add some behaviour for default constructor method


Add initial support for Markdown

This PR contains the following:
-support handling files with .md extension and transforming them to .HTML files
-support bold and italic text syntax
-update readme.md with information about the markdown files support
Fixes #12

Hey, there are some issues:
Content of the file I used to test the code:
Tom is a **cat** and **jerry** is a mouse
**Tom is a bold cat**
**Tom is a multiline bold cat
that goes to the next line
and to the line beyond...** The end.
** Bye.


Add support for dynamic view type - Allow to switch between tree and webview dynamically

Currently displaying a webview content on a activity bar registered view is allowed by
{
	"id": "grida-explorer-components-web",
	"name": "Components",
	"type": "webview",
	"contextualTitle": "Components"
},

And
  context.subscriptions.push(
    vscode.window.registerWebviewViewProvider(
      "grida-explorer-components-web",
      new MyWebviewProvider()
    )
  );

What i'de like to do is providing the ui as native tree view as default, and when user commands "switch to grid view", I'de like to show a grid view with image previews as webview.
This is possible with scripts, but won't get affected (registerWebviewViewProvider on non explicitly "webview" set view will be ignored)

Cant this be possible by your extension by

having a context key say showGridView which is false by default
register tree and grid view by setting above context key in when condition
have a command that toggles this context key - which toggles the views?

@sandy081  For webview, it should be pre-defined statically "type": "webview" in package.json
Sadly Can't do somehow by using when condition - AFAIK


Verification Set

Hey, thank you very much for sharing. I have a question, the verification set is not distinguished in the code, will it affect the final result?

Hey, thank you very much for sharing. I have a question, the verification set is not distinguished in the code, will it affect the final result?

Hi, thanks for you interest!
It shouldn't affect the final results much, because the learning rate adjustment is done by manual control. However, adding a learning rate scheduler might further improve the performance of the network.

Thanks.


Error on "Edit Spine" button click

When I click "Edit Spine" in the "Joe Test 12" configuration profile, I get an error similar to the following for most of the spines:

This occurs for the Employment, Earnings, and Person spines.

@excelsior - This is still happening. I'm logged in as user joe+cr12.


Implement and add EXP3.S for switching bandits

I need to implement the EXP3.S baseline for non-stationary bandits (switching bandits), as given in Algorithm/Fig.6 in ["The nonstochastic multiarmed bandit problem", P. Auer, N. Cesa-Bianchi, Y. Freund, R.E. Schapire, - SIAM journal on computing, 2002 - SIAM].

The rest of their section 8 gives Theorem 8.1 and the corollaries, in which we can find the recommended values for the parameters of the Exp3.S algorithm.

It is incredibly simple, yet it obtains the same kind of regret bounds as our proposal:

If $\Upsilon_T$ is unknown, its regret scales as $O(\Upsilon_T \sqrt{K T \log(K T)})$,

If $\Upsilon_T$ is known, its regret scales as $O(\sqrt{\Upsilon_T K T \log(K T)})$,

They use the notation $S = \Upsilon_T$ in the two results.

First experiment showed amazing results...

It had a few typos in the code (weights were updated first using the Exp3 rule (by calling super(Exp3S, self).getReward(arm, reward) in Exp3S.getReward()), then updated using the Exp3.S rule. Of course, I fixed this typo for the next experiments.


Activity AsJson uses old-style parent object

The format for the activity table AsJson looks like this:
{
"Activity" :
{
"ActivityGroupId" : "",
"ActivityParentID" : "",
"ActivityParty" :  [],
...
}
}
We are no longer creating a parent level object, which just makes the object harder to parse. I've created a V2 of this field; we need to trace all dependencies to V1, and ensure they will work with V2 before updating references.

Not seeing any references that relied on parsing the Activity::AsJSON field. Does that seem odd to you?

Nope

All FMPerception found were 3 scripts in kontroller that returned that field as a result.


Registration failure due to inability to find fingerprint

I have a feeling this is due to the plugin not properly setting up the public key of the user. I got a message in notifications (sorry cleared it) that said the message was successfully signed.

NOTE that the browser plugin key was the same as the key in the User Identity -> Account Settings.

@zubaidullo @eabyshev please look at this issue, seems problem in sending encrypted payload to hub, either hub cannot decrypt correctly or ss sending data in wrong format
2016-03-16 19:25:00,032 | INFO  | qtp781736633-246 | LoggingOutInterceptor            | 120 - org.apache.cxf.cxf-core - 3.1.0 | Outbound Message
---------------------------
ID: 76
Address: https://hub.subut.ai/rest/v1/peers/3CD8069A17CB8CA9CE985DB1A49D0A9509A6FCEC
Http-Method: POST
Content-Type: application/xml
Headers: {Content-Type=[application/xml], sbt-hdr=[3CD8069A17CB8CA9CE985DB1A49D0A9509A6FCEC], Accept=[*/*]}
Payload: -----BEGIN PGP MESSAGE-----
Version: BCPG v1.52
hQEMAyArx9GDVCL2AQf/cCjWNeumy//lYEgD3E1txeg809086i9RzwVwhpbJqK5C
SirGzLJZIGv/oWdHyW3hHtO3BnzFRbARZvnTX8n79HU2dIUiOI+1FC8KsYMwh3vS
rcB//1g7Ig/PmIEQw5M1X29ywNTETPeKGCXQV+IucEGcKEKfIWVcPDuRmfiWFA7c
NoekF402sG351jcahQ8+i/RfRjzXkhHU9o4WzTXwCyNqTWqvasXFTo4+aBr/xv69
obeaEXlIeNQYWqtrZFcZHWN4eyAhDmWUSnYeu5UCGRWa4XjJZZdYw0ymiX1UNfaH
l8d/FfSLw5MbEHFuSt/IhSqMBbmk5T4rp/N1SkRYe9LCEAFTAE69gZkM+E9OHmDd
ZFyiFqdKBcbzvH4HyxdYYa4sbMBxVUgx1D/umEwrFfowDP4TjRN2O7KBfl809d1d
qEXRVtBiWCewIBXQmkHWAg62SlkRGjx60zblk/JFQdmcS3J3Q03RNkhJlA1ohA4n
7xvffY1BOafsHFFvfcQcGMaBCOzO4fxlGrNse9sf/GJTpXsAaYH2k0Eep8bfuQP7
ZbaU6gadHVptoIXUZsvVnoYlfsNKh+c/LSicqSmJdK8W557pKV9MUzLwyRAcXnFp
oo8hXhCn0uwT0cAAxIWdw/H1SKNrnl2ZrnTlXXXjF4hiYsZiORVKSBWC21HOIPCO
anTHZp6Hv4bUOXPxHpLmPtyrQTtVW1Vk8meoHNddWXcQSAzyovFchqSrfVggjYXp
jRa1mLI421IWT4psDuKM85Q7zdIdJo7k/qPUmAbLsK1A+FooFgMxFuJ/Di5RmC9Q
Clxv1HhPTA7M6wnU6w5ll2rRS8IYD+sjyu6qQpw1azK4yJGX3aoRJrkG7ccmYXNA
SyxHmMQQ32Yahxc5kyx8BJO22t/hWSdUc9+qScpQoR4Fpqsh5HPw/D8+OMGLl2Qw
Nkfyb10C7ntH7jJBFs9KDPyKM9AxyrAY3Amz2naJskB9NEL40jtdecbZiAiuTkZF
NNp5LiPiL23ORZgYqr47GypPgMLm4G+yGGj1RivEFABxQLpoKIlSdoXQWo8hRZiL
GAwdv/T8ljLj7F1/YbO9I9CNB2QecaRTXBGV7KvBLY/VngodkUkArUTp4BOPuIqQ
l1cf6yso1guSWygqVsm9rFrVpYb+UPP+ppEbc56VjmAmDUI3KfswHwo550I9Jsso
21lz+hxweIvVrhBHn5YHqzSMvI/6PyoV76cChWp6I3gMzi34+qh/HO+ECfzzgvqT
c7LWMphU9KHvS3YLzb+YRa8VRQUMRPT+unjzU1bdkToxXQ==
=bBgx
-----END PGP MESSAGE-----
--------------------------------------
2016-03-16 19:25:00,165 | INFO  | qtp781736633-246 | LoggingInInterceptor             | 120 - org.apache.cxf.cxf-core - 3.1.0 | Inbound Message
----------------------------
ID: 76
Response-Code: 403
Encoding: UTF-8
Content-Type: text/plain; charset=UTF-8
Headers: {Cache-Control=[no-cache, no-store, max-age=0, must-revalidate], Content-Length=[43], Content-Type=[text/plain; charset=UTF-8], Date=[Wed, 16 Mar 2016 19:26:37 GMT], Expires=[Thu, 01 Jan 1970 00:00:00 GMT], Server=[Jetty(9.2.14.v20151106)]}
Payload: Cannot get the fingerprint from the request
--------------------------------------

@zubaidullo @asanaliev hey seems encrypted data has proper format (peer owner fingerprint), verify that hub side extracts fingerprint correctly
this is debug output of data that is sent to hub
{"ownerFingerprint":"f3a84a91dc73ad6ab1b9b3a9eb8f943a330152c5","ownerEmail":"***","ownerPassword":"***","peerInfo":{"id":"AFFA76724B1D0E58F6CB5286A24EDFA90487C190","name":"Peer AFFA76724B1D0E58F6CB5286A24EDFA90487C190 on ","version":"4.0.0-RC7-SNAPSHOT"}}

Actually, peer fingerprint send in CertificateData, as a context parameter. Not in body.

The bug was introduced by this commit:

commit 16a172c3c5dbc222ce1087d938f66d35f50c53ad
Author: Nurkaly Isakov<EMAIL_ADDRESS>Date:   Tue Mar 15 19:52:55 2016 +0600
Added ASYNC HTTP support and error logging for security key manager

The reason is in ServerBusListener (io.subutai.core.channel.impl.interceptor):
bus.setProperty( AsyncHTTPConduit.USE_ASYNC, Boolean.TRUE);
As I understand this property says Karaf to use Async HTTP everywhere. As a side effect of this, a client certificate is not always provided to SSL context. This is why Hub can't get a client certificate b/c it is absent.
To fix this, I disabled Async HTTP for bi-directional auth with Hub.
HttpClient.createTrustedWebClientWithAuth(...)
...
    Map<String, Object> requestContext = WebClient.getConfig( client ).getRequestContext();
    requestContext.put( "use.async.http.conduit", Boolean.FALSE );
...

Wow incredible that you caught this @asanaliev. @nk-the-crazy watch out for these dynamics. Later on this might pop up with other things as well due to SS integration with other third parties.


HBASE-23358 Set version as 2.1.9-SNAPSHOT in branch-2.1

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

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

_ Prechecks _

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

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

-0 :warning:
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.

_ branch-2.1 Compile Tests _

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

-1 :x:
mvninstall
2m 51s
root in branch-2.1 failed.

-1 :x:
compile
1m 40s
root in branch-2.1 failed.

-1 :x:
checkstyle
2m 16s
The patch fails to run checkstyle in root

-1 :x:
shadedjars
3m 11s
branch has 20 errors when building our shaded downstream artifacts.

-1 :x:
javadoc
1m 31s
root in branch-2.1 failed.

-1 :x:
javadoc
0m 11s
hbase-archetypes in branch-2.1 failed.

-1 :x:
javadoc
0m  9s
hbase-client-project in branch-2.1 failed.

-1 :x:
javadoc
0m  9s
hbase-shaded-client-project in branch-2.1 failed.

-1 :x:
javadoc
0m 11s
hbase-assembly in branch-2.1 failed.

-1 :x:
javadoc
0m 10s
hbase-endpoint in branch-2.1 failed.

-1 :x:
javadoc
0m  9s
hbase-examples in branch-2.1 failed.

-1 :x:
javadoc
0m 10s
hbase-external-blockcache in branch-2.1 failed.

-1 :x:
javadoc
0m  9s
hbase-it in branch-2.1 failed.

-1 :x:
javadoc
0m  8s
hbase-mapreduce in branch-2.1 failed.

-1 :x:
javadoc
0m 10s
hbase-rest in branch-2.1 failed.

-1 :x:
javadoc
0m  8s
hbase-rsgroup in branch-2.1 failed.

-1 :x:
javadoc
0m 10s
hbase-shaded in branch-2.1 failed.

-1 :x:
javadoc
0m  8s
hbase-shaded-check-invariants in branch-2.1 failed.

-1 :x:
javadoc
0m  8s
hbase-shaded-mapreduce in branch-2.1 failed.

-1 :x:
javadoc
0m 10s
hbase-shaded-testing-util in branch-2.1 failed.

-1 :x:
javadoc
0m  9s
hbase-shaded-testing-util-tester in branch-2.1 failed.

-1 :x:
javadoc
0m 11s
hbase-shell in branch-2.1 failed.

-1 :x:
javadoc
0m  9s
hbase-testing-util in branch-2.1 failed.

-1 :x:
javadoc
0m  9s
hbase-thrift in branch-2.1 failed.

_ Patch Compile Tests _

-1 :x:
mvninstall
2m 35s
root in branch-2.1 failed.

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

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

-1 :x:
compile
1m 38s
root in the patch failed.

-1 :x:
javac
1m 38s
root in the patch failed.

-1 :x:
checkstyle
2m 15s
The patch fails to run checkstyle in root

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

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

-1 :x:
shadedjars
3m 10s
patch has 20 errors when building our shaded downstream artifacts.

-1 :x:
hadoopcheck
1m 52s
The patch causes 20 errors with Hadoop v2.7.7.

-1 :x:
hadoopcheck
3m 47s
The patch causes 20 errors with Hadoop v2.8.5.

-1 :x:
hadoopcheck
5m 45s
The patch causes 20 errors with Hadoop v3.0.3.

-1 :x:
hadoopcheck
7m 43s
The patch causes 20 errors with Hadoop v3.1.2.

-1 :x:
javadoc
0m 11s
hbase-shaded in the patch failed.

-1 :x:
javadoc
0m 11s
hbase-archetypes in the patch failed.

-1 :x:
javadoc
1m 31s
root in the patch failed.

-1 :x:
javadoc
0m  9s
hbase-client-project in the patch failed.

-1 :x:
javadoc
0m  9s
hbase-shaded-client-project in the patch failed.

-1 :x:
javadoc
0m 12s
hbase-assembly in the patch failed.

-1 :x:
javadoc
0m 10s
hbase-endpoint in the patch failed.

-1 :x:
javadoc
0m  9s
hbase-examples in the patch failed.

-1 :x:
javadoc
0m  8s
hbase-external-blockcache in the patch failed.

-1 :x:
javadoc
0m  9s
hbase-it in the patch failed.

-1 :x:
javadoc
0m  9s
hbase-mapreduce in the patch failed.

-1 :x:
javadoc
0m  8s
hbase-rest in the patch failed.

-1 :x:
javadoc
0m  9s
hbase-rsgroup in the patch failed.

-1 :x:
javadoc
0m  8s
hbase-shaded-check-invariants in the patch failed.

-1 :x:
javadoc
0m  8s
hbase-shaded-mapreduce in the patch failed.

-1 :x:
javadoc
0m  8s
hbase-shaded-testing-util in the patch failed.

-1 :x:
javadoc
0m 10s
hbase-shaded-testing-util-tester in the patch failed.

-1 :x:
javadoc
0m  9s
hbase-shell in the patch failed.

-1 :x:
javadoc
0m  9s
hbase-testing-util in the patch failed.

-1 :x:
javadoc
0m  8s
hbase-thrift in the patch failed.

_ Other Tests _

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

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

76m 48s

Subsystem
Report/Notes

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

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

Optional Tests
dupname asflicense javac javadoc unit shadedjars hadoopcheck xml compile checkstyle

uname
Linux df034762c42a 4.15.0-66-generic #75-Ubuntu SMP Tue Oct 1 05:24:09 UTC 2019 x86_64 GNU/Linux

Build tool
maven

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

git revision
branch-2.1 / 6ce03ddad5

Default Java
1.8.0_181

mvninstall
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-893/1/artifact/out/branch-mvninstall-root.txt

compile
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-893/1/artifact/out/branch-compile-root.txt

checkstyle
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-893/1/artifact/out//home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-893/out/maven-branch-checkstyle-root.txt

shadedjars
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-893/1/artifact/out/branch-shadedjars.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-893/1/artifact/out/branch-javadoc-root.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-893/1/artifact/out/branch-javadoc-hbase-archetypes.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-893/1/artifact/out/branch-javadoc-hbase-archetypes_hbase-client-project.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-893/1/artifact/out/branch-javadoc-hbase-archetypes_hbase-shaded-client-project.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-893/1/artifact/out/branch-javadoc-hbase-assembly.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-893/1/artifact/out/branch-javadoc-hbase-endpoint.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-893/1/artifact/out/branch-javadoc-hbase-examples.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-893/1/artifact/out/branch-javadoc-hbase-external-blockcache.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-893/1/artifact/out/branch-javadoc-hbase-it.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-893/1/artifact/out/branch-javadoc-hbase-mapreduce.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-893/1/artifact/out/branch-javadoc-hbase-rest.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-893/1/artifact/out/branch-javadoc-hbase-rsgroup.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-893/1/artifact/out/branch-javadoc-hbase-shaded.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-893/1/artifact/out/branch-javadoc-hbase-shaded_hbase-shaded-check-invariants.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-893/1/artifact/out/branch-javadoc-hbase-shaded_hbase-shaded-mapreduce.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-893/1/artifact/out/branch-javadoc-hbase-shaded_hbase-shaded-testing-util.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-893/1/artifact/out/branch-javadoc-hbase-shaded_hbase-shaded-testing-util-tester.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-893/1/artifact/out/branch-javadoc-hbase-shell.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-893/1/artifact/out/branch-javadoc-hbase-testing-util.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-893/1/artifact/out/branch-javadoc-hbase-thrift.txt

mvninstall
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-893/1/artifact/out/branch-mvninstall-root.txt

mvninstall
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-893/1/artifact/out/patch-mvninstall-root.txt

compile
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-893/1/artifact/out/patch-compile-root.txt

javac
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-893/1/artifact/out/patch-compile-root.txt

checkstyle
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-893/1/artifact/out//home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-893/out/maven-patch-checkstyle-root.txt

shadedjars
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-893/1/artifact/out/patch-shadedjars.txt

hadoopcheck
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-893/1/artifact/out/patch-javac-2.7.7.txt

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

hadoopcheck
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-893/1/artifact/out/patch-javac-3.0.3.txt

hadoopcheck
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-893/1/artifact/out/patch-javac-3.1.2.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-893/1/artifact/out/patch-javadoc-hbase-shaded.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-893/1/artifact/out/patch-javadoc-hbase-archetypes.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-893/1/artifact/out/patch-javadoc-root.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-893/1/artifact/out/patch-javadoc-hbase-archetypes_hbase-client-project.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-893/1/artifact/out/patch-javadoc-hbase-archetypes_hbase-shaded-client-project.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-893/1/artifact/out/patch-javadoc-hbase-assembly.txt

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

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-893/1/artifact/out/patch-javadoc-hbase-examples.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-893/1/artifact/out/patch-javadoc-hbase-external-blockcache.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-893/1/artifact/out/patch-javadoc-hbase-it.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-893/1/artifact/out/patch-javadoc-hbase-mapreduce.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-893/1/artifact/out/patch-javadoc-hbase-rest.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-893/1/artifact/out/patch-javadoc-hbase-rsgroup.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-893/1/artifact/out/patch-javadoc-hbase-shaded_hbase-shaded-check-invariants.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-893/1/artifact/out/patch-javadoc-hbase-shaded_hbase-shaded-mapreduce.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-893/1/artifact/out/patch-javadoc-hbase-shaded_hbase-shaded-testing-util.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-893/1/artifact/out/patch-javadoc-hbase-shaded_hbase-shaded-testing-util-tester.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-893/1/artifact/out/patch-javadoc-hbase-shell.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-893/1/artifact/out/patch-javadoc-hbase-testing-util.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-893/1/artifact/out/patch-javadoc-hbase-thrift.txt

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-893/1/artifact/out/patch-unit-root.txt

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

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

modules
C: hbase-checkstyle hbase-annotations hbase-build-configuration hbase-protocol-shaded hbase-common hbase-metrics-api hbase-hadoop-compat hbase-metrics hbase-hadoop2-compat hbase-protocol hbase-client hbase-zookeeper hbase-replication hbase-resource-bundle hbase-http hbase-procedure hbase-server hbase-shaded hbase-shaded/hbase-shaded-client hbase-shaded/hbase-shaded-client-byo-hadoop hbase-hbtop hbase-shaded/hbase-shaded-with-hadoop-check-invariants hbase-archetypes hbase-archetypes/hbase-archetype-builder . hbase-archetypes/hbase-client-project hbase-archetypes/hbase-shaded-client-project hbase-assembly hbase-endpoint hbase-examples hbase-external-blockcache hbase-it hbase-mapreduce hbase-rest hbase-rsgroup hbase-shaded/hbase-shaded-check-invariants hbase-shaded/hbase-shaded-mapreduce hbase-shaded/hbase-shaded-testing-util hbase-shaded/hbase-shaded-testing-util-tester hbase-shell hbase-testing-util hbase-thrift U: .

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

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

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

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

_ Prechecks _

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

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

-0 :warning:
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.

_ branch-2.1 Compile Tests _

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

+1 :green_heart:
mvninstall
6m 46s
branch-2.1 passed

+1 :green_heart:
compile
3m 43s
branch-2.1 passed

+1 :green_heart:
checkstyle
3m 22s
branch-2.1 passed

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

+1 :green_heart:
javadoc
14m 54s
branch-2.1 passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
6m 34s
branch-2.1 passed

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

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

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

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

+1 :green_heart:
checkstyle
2m 53s
the patch passed

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

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

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

+1 :green_heart:
hadoopcheck
23m  6s
Patch does not cause any errors with Hadoop 2.7.7 2.8.5 or 3.0.3 3.1.2.

+1 :green_heart:
javadoc
12m 53s
the patch passed

_ Other Tests _

-1 :x:
unit
213m 51s
root in the patch failed.

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

342m 51s

Subsystem
Report/Notes

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

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

Optional Tests
dupname asflicense javac javadoc unit shadedjars hadoopcheck xml compile checkstyle

uname
Linux 6df72dc10f8a 4.15.0-66-generic #75-Ubuntu SMP Tue Oct 1 05:24:09 UTC 2019 x86_64 GNU/Linux

Build tool
maven

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

git revision
branch-2.1 / eff0e0c86c

Default Java
1.8.0_181

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-893/2/artifact/out/patch-unit-root.txt

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

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

modules
C: hbase-checkstyle hbase-annotations hbase-build-configuration hbase-protocol-shaded hbase-common hbase-metrics-api hbase-hadoop-compat hbase-metrics hbase-hadoop2-compat hbase-protocol hbase-client hbase-zookeeper hbase-replication hbase-resource-bundle hbase-http hbase-procedure hbase-server hbase-mapreduce hbase-testing-util hbase-thrift hbase-rsgroup hbase-shell hbase-endpoint hbase-it hbase-rest hbase-examples hbase-shaded hbase-shaded/hbase-shaded-client hbase-shaded/hbase-shaded-client-byo-hadoop hbase-shaded/hbase-shaded-mapreduce hbase-external-blockcache hbase-hbtop hbase-assembly hbase-shaded/hbase-shaded-testing-util hbase-shaded/hbase-shaded-testing-util-tester hbase-shaded/hbase-shaded-check-invariants hbase-shaded/hbase-shaded-with-hadoop-check-invariants hbase-archetypes hbase-archetypes/hbase-client-project hbase-archetypes/hbase-shaded-client-project hbase-archetypes/hbase-archetype-builder . U: .

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

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

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

This message was automatically generated.


S3 - Migrate S3 aws-java-sdk-core to aws-java-sdk-s3

Use the specific s3 java sdk instead of the core one since it provides an api to read in a multi part way.  "com.amazonaws"  % "aws-java-sdk-s3" % Aws.

Hi @paualarco, Is this issue is just removing the following line(and fixing the ripples caused by the change)?
https://github.com/monix/monix-connect/blob/master/project/Dependencies.scala#L77

Not just that @t1707 , we would like add a getObject method that will return an it in parts as an observable. And that can not be implemented with the aws-java-sdk core but with the sdk-s3.

we would like add a getObject method that will return an it in parts as an observable.

I see, will have a look, thank you for your support and quick responses.