[SPARK-37193][SQL] DynamicJoinSelection.shouldDemoteBroadcastHashJoin should not apply to outer joins

What changes were proposed in this pull request?

DynamicJoinSelection.shouldDemoteBroadcastHashJoin will prevent AQE from converting Sort merge join into a broadcast join because SMJ is faster when the side that would be broadcast has a lot of empty partitions.
This makes sense for inner joins which can short circuit if one side is empty.
For (left,right) outer join, the streaming side still has to be processed so demoting broadcast join doesn't have the same advantage.

Does this PR introduce any user-facing change?

Yes, it may cause AQE to choose BHJ more often than before with better performance
How was this patch tested?

Spark UTs
Also empirical evidence

Can one of the admins verify this patch?

@HyukjinKwon do you have any other suggestions?

Hi
@cloud-fan @ulysses-you @maryannxue could one of you take a look please

ping - is there anything else I can do to move this along?

The last tests pass is long time ago, @ekoifman can you rebase this PR and run the test again? Sorry for the late review.

@cloud-fan done

thanks, merging to master!

I'm reverting this to avoid mistakenly releasing a performance regression in Spark 3.3. Please resubmit this PR with SPARK-37753 resolved.

who can tell me ,What does short circuit local join mean,thanks

I'm reverting this to avoid mistakenly releasing a performance regression in Spark 3.3. Please resubmit this PR with SPARK-37753 resolved.

can you tell me ,What does short circuit local join mean,thanks

@thomasg19930417
Imagine you have an inner join where the one side has 0 rows.  As soon as you know that one side is empty, you don't have evaluate any operators on the other side (or stop executing them if they started already) since you know the join won't produce any rows.

Contributor

Thank you for reply

@ekoifman   hi, when LOJ  and LHS has many empty partition ,why inner join not demote broadcast
   else if (manyEmptyInOther && canBroadcastPlan) {
         join.joinType match {
        case LeftOuter | RightOuter | LeftAnti => true
        case _ => false
      }


13507: FHIR Converter integration tests

This PR applies a fix for which message model is chosen when parsing an HL7 message by deferring to the topic as well as adding comprehensive integration tests for the FHIR converter
Test Steps:

Send one of the elims messages through the pipeline and verify that it gets delivered
Send one of the MarsOtc messages use to test validation through the pipeline and verify it gets delivered

Verify the coverage (generated from only running the new tests)

Changes

Adds the ability to use an HL7MessageParseConfiguration set on the topic (required to support the RadXMars spec), otherwise uses the current fallback behavior of

Any ORU_R01 message is parsed as 27 and otherwise the default HAPI behavior is use

Adds a comprehensive set of integration tests for the FHIR Converter

Checklist
Testing

[x] Tested locally?
[x] Ran ./prime test or ./gradlew testSmoke against local Docker ReportStream container?
[ ] (For Changes to /frontend-react/...) Ran npm run lint:write?
[x] Added tests?

Process

[ ] Are there licensing issues with any new dependencies introduced?
[ ] Includes a summary of what a code reviewer should test/verify?
[ ] Updated the release notes?
[ ] Database changes are submitted as a separate PR?
[ ] DevOps team has been notified if PR requires ops support?

Linked Issues

#13507

To Be Done
Specific Security-related subjects a reviewer should pay specific attention to

in addition to the integration test failures - there is an additional test failure that only presents when gradlew package or gradlew build is invoked. When gradlew test is invoked the test does not fail.

  gov.cdc.prime.router.fhirengine.translation.TranslationSchemaManager$Companion$TranslationSyncException: Validation state was invalid, the valid blob is misconfigured.
  It is either duplicated or not present when the state is not being validated
      at app//gov.cdc.prime.router.fhirengine.translation.SyncSchemaE2ETests.test end-to-end sync schemas workflow(SyncSchemaE2ETests.kt:87)```

Haven't been able to do the test steps yet because I'm having problems building/running the tests locally.


Add container UI issues #2

Rancher versions: 5/25
Issues:

[x] In scheduling when I have specific host selected the drop-down seems a bit too close

[x] In scheduling for automatically pick host, is the remove button centered?

[x] the Scheduling text for radio buttons are two different colors (I think they should be black as other section have the radio button and tex tin black)

[x] Health check the text field and type text are same color?

[x] Health check section, the When Unhealthy text is too close to check timeout and it seems like a lot of padding between the radio buttons (this seem to only be in scaling group at the moment?)

[x] Health check section, the two radio button options are different colors (once again this seem to only be in Add scaling group)

[x] In command section the Add Option button not centered

[x] In command section when you add a Log Option, the Key/Value should are not aligned with Driver

[x] In Networking section, the Resolving Servers & Search domains remove buttons are cut off in front

[x] In Networking section, the radio button text is blue.  Seems like we might want to make that black to fall in line with the other sections

[x] In Security section for Device binding, seems like a lot of space?

[x] In Volumes section, the Add Volume not adding new line

[x] In Volumes section, it seems like a lot of padding?

@tfiduccia resolved not merged

Version - 5/30
Verified fixed


[Feature Request] DropDownMenu inherit parent's width

Existing Component
Yes
Component Name
DropDownMenu
Description
It would nice to have a property that makes the menu of the dropdown 100% width (from the parent's width).

You can set width by using CSS.

@ziyoung I don't want to set it manually because it has programmatic top, left, right and because I don't know the width of the parent, it will make me use the Dom to get the width, which I don't want
It's kinda a basic feature for a drop-down menu, to fit within his parent width, why did you decide to close the issue?


[16:30:53] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 67 -> 68 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=68}
[16:30:53] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 67 -> 68 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=68}
[16:30:53] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 67 -> 68 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=68}
[16:30:53] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 67 -> 68 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=68}
[16:30:53] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 67 -> 68 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=68}
[16:30:53] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 68 -> 69 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=69}
[16:30:53] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 68 -> 69 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=69}
[16:30:53] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 67 -> 68 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=68}
[16:30:53] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 67 -> 68 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=68}
[16:30:53] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 67 -> 68 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=68}
[16:30:53] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 68 -> 69 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=69}
[16:30:53] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 68 -> 69 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=69}
[16:30:53] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 67 -> 68 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=68}
[16:30:53] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 67 -> 68 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=68}
[16:30:53] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 67 -> 68 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=68}
[16:30:53] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 67 -> 68 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=68}
[16:30:53] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 68 -> 69 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=69}
[16:30:53] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 68 -> 69 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=69}
[16:30:53] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 67 -> 68 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=68}
[16:30:53] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 65 -> 66 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=66}
[16:30:53] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 73 -> 74 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=74}
[16:30:53] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 65 -> 66 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=66}
[16:30:53] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 39 -> 39 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=39}
[16:30:53] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 53 -> 54 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=54}
[16:30:53] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 53 -> 54 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=54}
[16:30:53] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 65 -> 66 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=66}
[16:30:53] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE INCOMING: PLAY 7 -> 8 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=8}
[16:30:53] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE INCOMING: PLAY 13 -> 14 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=14}
[16:30:53] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 72 -> 73 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=73}
[16:30:53] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 20 -> 20 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=20}
[16:30:53] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 22 -> 22 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=22}
[16:30:53] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 22 -> 22 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=22}
[16:30:53] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 39 -> 39 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=39}
[16:30:53] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 53 -> 54 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=54}
[16:30:53] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 65 -> 66 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=66}
[16:30:54] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 65 -> 66 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=66}
[16:30:54] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 39 -> 39 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=39}
[16:30:54] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 53 -> 54 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=54}
[16:30:54] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 65 -> 66 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=66}
[16:30:54] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 39 -> 39 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=39}
[16:30:54] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 53 -> 54 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=54}
[16:30:54] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 65 -> 66 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=66}
[16:30:54] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 65 -> 66 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=66}
[16:30:54] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 39 -> 39 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=39}
[16:30:54] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 53 -> 54 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=54}
[16:30:54] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 53 -> 54 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=54}
[16:30:54] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 65 -> 66 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=66}
[16:30:54] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 39 -> 39 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=39}
[16:30:54] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 53 -> 54 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=54}
[16:30:54] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 53 -> 54 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=54}
[16:30:54] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 65 -> 66 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=66}
[16:30:54] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 70 -> 71 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=71}
[16:30:54] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 67 -> 68 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=68}
[16:30:54] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 67 -> 68 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=68}
[16:30:54] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 67 -> 68 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=68}
[16:30:54] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 68 -> 69 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=69}
[16:30:54] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 68 -> 69 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=69}
[16:30:54] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 67 -> 68 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=68}
[16:30:54] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 67 -> 68 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=68}
[16:30:54] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 67 -> 68 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=68}
[16:30:54] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 67 -> 68 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=68}
[16:30:54] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 67 -> 68 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=68}
[16:30:54] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 67 -> 68 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=68}
[16:30:54] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 67 -> 68 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=68}
[16:30:54] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 67 -> 68 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=68}
[16:30:54] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 68 -> 69 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=69}
[16:30:54] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 68 -> 69 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=69}
[16:30:54] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 67 -> 68 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=68}
[16:30:54] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 67 -> 68 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=68}
[16:30:54] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 67 -> 68 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=68}
[16:30:54] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 68 -> 69 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=69}
[16:30:54] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 68 -> 69 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=69}
[16:30:54] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 67 -> 68 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=68}
[16:30:54] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 67 -> 68 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=68}
[16:30:54] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 67 -> 68 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=68}
[16:30:54] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 67 -> 68 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=68}
[16:30:54] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 68 -> 69 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=69}
[16:30:54] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 68 -> 69 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=69}
[16:30:54] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 67 -> 68 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=68}
[16:30:54] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 65 -> 66 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=66}
[16:30:54] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 73 -> 74 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=74}
[16:30:54] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 38 -> 38 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=38}
[16:30:54] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 38 -> 38 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=38}
[16:30:54] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 38 -> 38 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=38}
[16:30:54] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 53 -> 54 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=54}
[16:30:54] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 38 -> 38 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=38}
[16:30:54] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 38 -> 38 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=38}
[16:30:54] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 38 -> 38 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=38}
[16:30:54] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 53 -> 54 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=54}
[16:30:54] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 39 -> 39 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=39}
[16:30:54] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 53 -> 54 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=54}
[16:30:54] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 38 -> 38 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=38}
[16:30:54] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 38 -> 38 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=38}
[16:30:54] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 53 -> 54 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=54}
[16:30:54] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 38 -> 38 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=38}
[16:30:54] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 38 -> 38 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=38}
[16:30:54] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 38 -> 38 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=38}
[16:30:54] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 38 -> 38 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=38}
[16:30:54] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 38 -> 38 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=38}
[16:30:54] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 38 -> 38 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=38}
[16:30:54] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 38 -> 38 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=38}
[16:30:54] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 53 -> 54 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=54}
[16:30:54] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 38 -> 38 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=38}
[16:30:54] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 38 -> 38 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=38}
[16:30:54] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 38 -> 38 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=38}
[16:30:54] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 38 -> 38 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=38}
[16:30:54] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 38 -> 38 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=38}
[16:30:54] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 38 -> 38 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=38}
[16:30:54] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 38 -> 38 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=38}
[16:30:54] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 53 -> 54 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=54}
[16:30:54] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 38 -> 38 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=38}
[16:30:54] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 38 -> 38 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=38}
[16:30:54] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 45 -> 46 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=46}
[16:30:54] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE INCOMING: PLAY 8 -> 9 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=9}
[16:30:54] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 65 -> 66 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=66}
[16:30:54] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 39 -> 39 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=39}
[16:30:54] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 53 -> 54 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=54}
[16:30:54] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE INCOMING: PLAY 13 -> 14 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=14}
[16:30:54] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 65 -> 66 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=66}
[16:30:55] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 65 -> 66 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=66}
[16:30:55] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 39 -> 39 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=39}
[16:30:55] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 53 -> 54 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=54}
[16:30:55] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 65 -> 66 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=66}
[16:30:55] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 39 -> 39 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=39}
[16:30:55] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 53 -> 54 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=54}
[16:30:55] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 65 -> 66 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=66}
[16:30:55] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 65 -> 66 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=66}
[16:30:55] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 39 -> 39 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=39}
[16:30:55] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 53 -> 54 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=54}
[16:30:55] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 53 -> 54 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=54}
[16:30:55] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 65 -> 66 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=66}
[16:30:55] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 31 -> 31 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[Pair{Type|Long, 10678511}], id=31}
[16:30:55] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE INCOMING: PLAY 11 -> 12 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[Pair{Type|VarInt, 10678511}], id=12}
[16:30:55] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 39 -> 39 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=39}
[16:30:55] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 53 -> 54 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=54}
[16:30:55] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 53 -> 54 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=54}
[16:30:55] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 65 -> 66 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=66}
[16:30:55] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 65 -> 66 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=66}
[16:30:55] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 53 -> 54 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=54}
[16:30:55] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 39 -> 39 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=39}
[16:30:55] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 53 -> 54 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=54}
[16:30:55] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 53 -> 54 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=54}
[16:30:55] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 70 -> 71 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=71}
[16:30:55] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 67 -> 68 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=68}
[16:30:55] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 67 -> 68 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=68}
[16:30:55] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 67 -> 68 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=68}
[16:30:55] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 68 -> 69 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=69}
[16:30:55] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 68 -> 69 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=69}
[16:30:55] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 67 -> 68 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=68}
[16:30:55] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 67 -> 68 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=68}
[16:30:55] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 67 -> 68 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=68}
[16:30:55] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 67 -> 68 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=68}
[16:30:55] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 67 -> 68 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=68}
[16:30:55] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 67 -> 68 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=68}
[16:30:55] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 67 -> 68 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=68}
[16:30:55] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 67 -> 68 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=68}
[16:30:55] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 68 -> 69 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=69}
[16:30:55] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 68 -> 69 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=69}
[16:30:55] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 67 -> 68 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=68}
[16:30:55] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 67 -> 68 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=68}
[16:30:55] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 67 -> 68 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=68}
[16:30:55] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 68 -> 69 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=69}
[16:30:55] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 68 -> 69 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=69}
[16:30:55] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 67 -> 68 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=68}
[16:30:55] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 67 -> 68 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=68}
[16:30:55] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 67 -> 68 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=68}
[16:30:55] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 67 -> 68 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=68}
[16:30:55] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 68 -> 69 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=69}
[16:30:55] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 68 -> 69 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=69}
[16:30:55] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 67 -> 68 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=68}
[16:30:55] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 65 -> 66 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=66}
[16:30:55] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 73 -> 74 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=74}
[16:30:55] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 53 -> 54 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=54}
[16:30:55] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 39 -> 39 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=39}
[16:30:55] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 53 -> 54 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=54}
[16:30:55] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 53 -> 54 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=54}
[16:30:55] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 53 -> 54 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=54}
[16:30:55] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 39 -> 39 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=39}
[16:30:55] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 53 -> 54 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=54}
[16:30:55] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 65 -> 66 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=66}
[16:30:55] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE INCOMING: PLAY 13 -> 14 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=14}
[16:30:55] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 65 -> 66 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=66}
[16:30:55] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 39 -> 39 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=39}
[16:30:55] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 53 -> 54 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=54}
[16:30:56] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 65 -> 66 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=66}
[16:30:56] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 39 -> 39 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=39}
[16:30:56] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 53 -> 54 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=54}
[16:30:56] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 65 -> 66 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=66}
[16:30:56] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE INCOMING: PLAY 2 -> 3 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=3}
[16:30:56] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 65 -> 66 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=66}
[16:30:56] [Server thread/INFO]: KMOFLOVE issued server command: /stop
[16:30:56] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 72 -> 73 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=73}
[16:30:56] [Server thread/INFO]: [KMOFLOVE: Stopping the server]
[16:30:56] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 15 -> 15 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=15}
[16:30:56] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 39 -> 39 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=39}
[16:30:56] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 53 -> 54 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=54}
[16:30:56] [Server thread/INFO]: Stopping server
[16:30:56] [Server thread/INFO]: [CTSNC_Tablist] Disabling CTSNC_Tablist v1.1
[16:30:56] [Server thread/INFO]: [CTSNC_Stats] Disabling CTSNC_Stats v1.2
[16:30:56] [Server thread/INFO]: [CTSNC_DisplayName] Disabling CTSNC_DisplayName v1.0
[16:30:56] [Server thread/INFO]: [CTSNC_Scoreboard] Disabling CTSNC_Scoreboard v2.0
[16:30:56] [Server thread/INFO]: [CTSNC] Disabling CTSNC v12.0
[16:30:56] [Server thread/INFO]: [CTSNC] Version: 12.0 by [Herbystar] disabled!
[16:30:56] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 65 -> 66 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=66}
[16:30:56] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 67 -> 68 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=68}
[16:30:56] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 67 -> 68 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=68}
[16:30:56] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 67 -> 68 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=68}
[16:30:56] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 67 -> 68 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=68}
[16:30:56] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 67 -> 68 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=68}
[16:30:56] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 67 -> 68 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=68}
[16:30:56] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 67 -> 68 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=68}
[16:30:56] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 67 -> 68 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=68}
[16:30:56] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 67 -> 68 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=68}
[16:30:56] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 67 -> 68 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=68}
[16:30:56] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 67 -> 68 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=68}
[16:30:56] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 67 -> 68 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=68}
[16:30:56] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 67 -> 68 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=68}
[16:30:56] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 67 -> 68 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=68}
[16:30:56] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 67 -> 68 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=68}
[16:30:56] [Server thread/INFO]: [SignShop] Disabling SignShop v2.11.2
[16:30:56] [Server thread/INFO]: [SignShop] Successfully cancelled Async Storage task with ID: 147
[16:30:56] [Server thread/INFO]: [SignShop] Disabled
[16:30:56] [Server thread/INFO]: [ShopChest] Disabling ShopChest v1.12.3
[16:30:56] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 49 -> 50 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=50}
[16:30:56] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 49 -> 50 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=50}
[16:30:56] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 49 -> 50 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=50}
[16:30:56] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 49 -> 50 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=50}
[16:30:56] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 49 -> 50 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=50}
[16:30:56] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 49 -> 50 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=50}
[16:30:56] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 49 -> 50 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=50}
[16:30:56] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 49 -> 50 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=50}
[16:30:56] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 49 -> 50 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=50}
[16:30:56] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 49 -> 50 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=50}
[16:30:56] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 49 -> 50 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=50}
[16:30:56] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 49 -> 50 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=50}
[16:30:56] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 49 -> 50 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=50}
[16:30:56] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 49 -> 50 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=50}
[16:30:56] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 49 -> 50 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=50}
[16:30:56] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 49 -> 50 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=50}
[16:30:56] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 49 -> 50 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=50}
[16:30:56] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 49 -> 50 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=50}
[16:30:56] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 49 -> 50 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=50}
[16:30:56] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 49 -> 50 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=50}
[16:30:56] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 49 -> 50 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=50}
[16:30:56] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 49 -> 50 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=50}
[16:30:56] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 49 -> 50 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=50}
[16:30:56] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 49 -> 50 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=50}
[16:30:56] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 49 -> 50 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=50}
[16:30:56] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 49 -> 50 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=50}
[16:30:56] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 49 -> 50 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=50}
[16:30:56] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 49 -> 50 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=50}
[16:30:56] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 49 -> 50 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=50}
[16:30:56] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 49 -> 50 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=50}
[16:30:56] [Server thread/INFO]: [MyPet] Disabling MyPet v2.3.2
[16:30:56] [Server thread/INFO]: [PlaceholderAPI] Unregistered placeholder expansion: mypet
[16:30:56] [Server thread/INFO]: [CBU] Disabling CommandBlockerUltimate v1.5.4
[16:30:56] [Server thread/INFO]: [LockettePro] Disabling LockettePro v2.9.0
[16:30:56] [Server thread/INFO]: [AuthMe] Disabling AuthMe v5.3.2-b1726
[16:30:56] [Server thread/INFO]: [AuthMe] Waiting for 0 tasks to finish
[16:30:56] [Server thread/INFO]: [AuthMe] AuthMe 5.3.2-b1726 disabled!
[16:30:56] [Server thread/INFO]: [ProtocolLib] Disabling ProtocolLib v4.3.0
[16:30:56] [Server thread/INFO]: [Scavenger] Disabling Scavenger v1.7-46
[16:30:56] [Server thread/INFO]: [Scavenger] Saved ignore list. (Count = 0)
[16:30:56] [Server thread/INFO]: [NoFlyZone] Disabling NoFlyZone v1.3
[16:30:56] [Server thread/INFO]: [ChestShop] Disabling ChestShop v3.8.12
[16:30:56] [Server thread/INFO]: [RPGItems] Disabling RPGItems v3.5.255
[16:30:56] [Server thread/INFO]: [ProtectionStones] Disabling ProtectionStones v1.4.1
[16:30:56] [Server thread/INFO]: [ColoredTags] Disabling ColoredTags v2.1.3
[16:30:56] [Server thread/INFO]: [SilkSpawners] Disabling SilkSpawners v5.0.0
[16:30:56] [Server thread/INFO]: [1vs1] Disabling 1vs1 v1.7.1 #221
[16:30:56] [Server thread/INFO]: [1vs1] Disconnecting from database
[16:30:56] [Server thread/INFO]: [1vs1] 1vs1 disabled!
[16:30:56] [Server thread/INFO]: [PVP Arena] Disabling pvparena v<IP_ADDRESS>
[16:30:56] [Server thread/INFO]: [PVP Arena] Plugin tracking disabled. See you soon?
[16:30:56] [Server thread/INFO]: [PVP Arena] disabled (version pvparena v<IP_ADDRESS>)
[16:30:56] [Server thread/INFO]: [ParticleHats] Disabling ParticleHats v3.4.2
[16:30:56] [Server thread/INFO]: [MyCommand] Disabling MyCommand v5.3.4
[16:30:56] [Server thread/INFO]: [PlaceholderAPI] Unregistered placeholder hook for placeholder: mycommand
[16:30:56] [Server thread/INFO]: -=-=-=-=-=-=-=-=-=- MyCommand -=-=-=-=-=-=-=-=-=-=-
[16:30:56] [Server thread/INFO]: | Tasks   : Stopped all.
[16:30:56] [Server thread/INFO]: | Version : 5.3.4
[16:30:56] [Server thread/INFO]: | Author  : emmerrei a.k.a Ivanpro
[16:30:56] [Server thread/INFO]: -=-=-=-=-=-=-=-=-=-    Bye!   -=-=-=-=-=-=-=-=-=-=-
[16:30:56] [Server thread/INFO]: [EssentialsSpawn] Disabling EssentialsSpawn vTeamCity
[16:30:56] [Server thread/INFO]: [PlayMoreSounds] Disabling PlayMoreSounds v2.3.1
[16:30:56] [Server thread/INFO]: [Multiverse-Inventories] Disabling Multiverse-Inventories v2.5.0-SNAPSHOT-b443
[16:30:56] [Server thread/INFO]: [EssentialsProtect] Disabling EssentialsProtect vTeamCity
[16:30:56] [Server thread/INFO]: [SkinsRestorer] Disabling SkinsRestorer v13.1.3
[16:30:56] [Server thread/INFO]: [WorldGuard] Disabling WorldGuard v6.2.1;84bc322
[16:30:56] [Server thread/INFO]: [WorldGuard] Shutting down executor and waiting for any pending tasks...
[16:30:56] [Server thread/INFO]: [UltraCosmetics] Disabling UltraCosmetics v2.4.9
[16:30:56] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 22 -> 22 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=22}
[16:30:56] [Server thread/INFO]: [Vault] Disabling Vault v1.6.1
[16:30:56] [Server thread/INFO]: [Essentials] Payment method was disabled. No longer accepting payments.
[16:30:56] [Server thread/INFO]: [Alert] Disabling Alert v1.0
[16:30:56] [Server thread/INFO]: Alert | Ruhemodus aktiviert.
[16:30:56] [Server thread/INFO]: [CommandCooldown] Disabling CommandCooldown v1.0.1
[16:30:56] [Server thread/INFO]: [EssentialsChat] Disabling EssentialsChat vTeamCity
[16:30:56] [Server thread/INFO]: [Shopkeepers] Disabling Shopkeepers v1.83
[16:30:56] [Server thread/INFO]: [HubThat] Disabling HubThat v7.0
[16:30:56] [Server thread/INFO]: [LightChatBubbles] Disabling LightChatBubbles v3
[16:30:56] [Server thread/INFO]: [EpicBoss-Updated-Edition] Disabling EpicBoss-Updated-Edition v0.6.3
[16:30:56] [Server thread/INFO]: EpicBoss-Updated-Edition Has Been Disabled!
[16:30:56] [Server thread/INFO]: [Multiverse-Core] Disabling Multiverse-Core v2.5.0-b727
[16:30:56] [Server thread/INFO]: [TrollGUI] Disabling TrollGUI v1.3
[16:30:56] [Server thread/INFO]: [EndlessEnchant] Disabling EndlessEnchant v1.6
[16:30:56] [Server thread/INFO]: [CrackShot] Disabling CrackShot v0.98.7
[16:30:56] [Server thread/INFO]: [ClearLag] Disabling ClearLag v2.9.7
[16:30:56] [Server thread/INFO]: [ClearLag] Clearlag is now disabled!
[16:30:56] [Server thread/INFO]: [Essentials] Disabling Essentials vTeamCity
[16:30:56] [Server thread/INFO]: [OpenInv] Disabling OpenInv v3.3.0
[16:30:56] [Server thread/INFO]: [HealthBar] Disabling HealthBar v1.8.3
[16:30:56] [Server thread/INFO]: HealthBar disabled, all the health bars have been removed.
[16:30:56] [Server thread/INFO]: [ChatMessenger] Disabling ChatMessenger v1.1.3
[16:30:56] [Server thread/INFO]: [WorldEdit] Disabling WorldEdit v6.1.8-SNAPSHOT;cd4729f
[16:30:56] [Server thread/INFO]: [ChatSounds] Disabling ChatSounds v1.6
[16:30:56] [Server thread/INFO]: [Itemizer] Disabling Itemizer v3.2
[16:30:56] [Server thread/INFO]: [TTA] Disabling TTA v3.9
[16:30:56] [Server thread/INFO]: [TTA] Version: 3.9 by [Herbystar] disabled!
[16:30:56] [Server thread/INFO]: [CratesPlus] Disabling CratesPlus v4.4.4
[16:30:56] [Server thread/INFO]: [ViaBackwards] Disabling ViaBackwards v2.3.1
[16:30:56] [Server thread/INFO]: [ViaVersion] Disabling ViaVersion v1.3.0
[16:30:56] [Server thread/INFO]: [ViaVersion] ViaVersion is disabling, if this is a reload and you experience issues consider rebooting.
[16:30:56] [Server thread/INFO]: [GhostScavengerHunt] Disabling GhostScavengerHunt v1.0.3-SNAPSHOT
[16:30:56] [Server thread/INFO]: [EasyWarp] Disabling EasyWarp v3.8
[16:30:56] [Server thread/INFO]: [RainbowChat] Disabling RainbowChat v1.0
[16:30:56] [Server thread/INFO]: [SuperTrails] Disabling SuperTrails v9.6.7
[16:30:56] [Server thread/INFO]: [LimitDrops] Disabling LimitDrops v1.1
[16:30:56] [Server thread/INFO]: [IP-Check] Disabling IP-Check v2.0.7
[16:30:56] [Server thread/INFO]: [IP-Check] The connection to the database was closed successfully.
[16:30:56] [Server thread/INFO]: [Craftconomy3] Disabling Craftconomy3 v3.3.1-d99cf63-trv200
[16:30:56] [Server thread/INFO]: [Craftconomy3] Closing the connection to the database.
[16:30:56] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE INCOMING: PLAY 13 -> 14 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=14}
[16:30:57] [Server thread/INFO]: [DeluxeJoin] Disabling DeluxeJoin v2.5.0
[16:30:57] [Server thread/INFO]: [PlaceholderAPI] Disabling PlaceholderAPI v2.8.2
[16:30:57] [Server thread/INFO]: [GroupManager] Disabling GroupManager v2.0.1-b332
[16:30:57] [Server thread/INFO]: GroupManager - INFO - Scheduled Data Saving is disabled!
[16:30:57] [Server thread/INFO]: GroupManager version 2.0.1-b332 is disabled!
[16:30:57] [Server thread/INFO]: [MinePacks] Disabling MinePacks v1.17.5
[16:30:57] [Server thread/INFO]: [MinePacks] Checking for updates ...
[16:30:57] [Server thread/INFO]: Minepacks-Connection-Pool - is closing down.
[16:30:57] [Server thread/INFO]: [MinePacks] MinePacks has been disabled.
[16:30:57] [Server thread/INFO]: [AntiCreeper] Disabling AntiCreeper v4.19
[16:30:57] [Server thread/INFO]: [PluginConstructorAPI] Disabling PluginConstructorAPI v1.0.10
[16:30:57] [Server thread/INFO]: Saving players
[16:30:57] [Server thread/INFO]: KMOFLOVE lost connection: Server closed
[16:30:57] [Server thread/INFO]: KMOFLOVE left the game
[16:30:57] [Netty Server IO #2/INFO]: [ViaVersion] KMOFLOVE OUTGOING: PLAY 26 -> 26 [UNKNOWN[340]] Value: PacketWrapper{packetValues=[], readableObjects=[], id=26}
[16:30:57] [Server thread/INFO]: Saving worlds
[16:30:57] [Server thread/INFO]: Saving chunks for level 'world'/overworld
[16:30:57] [Server thread/INFO]: Saving chunks for level 'world_the_end'/the_end
[16:30:57] [Server thread/INFO]: Saving chunks for level 'PVP'/overworld
[16:30:58] [Server thread/INFO]: Saving chunks for level 'Lakota'/overworld
[16:30:58] [Server thread/INFO]: Saving chunks for level 'world-2'/overworld

I have no idea what your issue is / what you're trying to say.
Create a new ticket and follow the instructions - https://github.com/MylesIsCool/ViaVersion/blob/master/ISSUE_TEMPLATE.md (including using pastebin.com for code)


Php Driver Windows (IIS) VS linux benchmarks ?

Hello , we are stuck with windows from 2010 with a really large php app Built on Yii and sql Server (database size > 4 TB)
but our current plan to move application server to linux with nginx but i am still looking for a compare about php sql driver behavior , speed on both OS
Can any one tell use his feedback after migrate to linux ?

@AymanElarian Are you planning to use SQLSRV or PDO_SQLSRV drivers?

PDO_SQLSRV , but it will be great if benchmarking for both

Here is the results we have, we can share more results in upcoming weeks. Also if you are interested to get benchmark in your environment you can run performance tests  . let us know if you need help.
Run 1000 FETCH operation for 1000 iterations:

Windows
OS X
CentOS7

SQLSRV
2547
1727
2480

PDO_SQLSRV
2491
1734
2450

Run 1000 INSERT operation for 1000 iterations:

Windows
OS X
CentOS7

SQLSRV
3081
2714
3040

PDO_SQLSRV
3161
2741
3090

for  both  , it connect to sqlserver in the same node , or network server ? i mean both result for the same DB Server ?

Closing this issue due to inactivity. @AymanElarian please feel free to reopen this should you have more questions regarding performance.


sample in bootstrap v3/v2（ release 2.3.8）  click datetimepicker malposition

sample in bootstrap v3/v2  click  datetimepicker malposition show to bottom in chrome/ie

you need to use JS and CSS file from demo page instead of GitHub (https://github.com/smalot/bootstrap-datetimepicker/issues/487)

but it's an old version at the demo page. some functions are unavailable there

To correct this bug, 'place' function should be reverted to 2.3.5 which works well. The differece is:
2.3.5:
`      if (this.pickerPosition == 'top-left' || this.pickerPosition == 'top-right') {
top = offset.top - this.picker.outerHeight();
} else {
top = offset.top + this.height;
}
  top = top - containerOffset.top;
  left = left - containerOffset.left;

  if( !elementOrParentIsFixed(this.element) ){
    top = top + document.body.scrollTop;
  }

`
after 2.3.7
     if (this.component) {         top = top - containerOffset.top + 169;         left = left - containerOffset.left + 210;       } else {         if (this.pickerPosition == 'top-left' || this.pickerPosition == 'top-right') {           top = offset.top - this.picker.outerHeight();         } else {           top = offset.top + this.height;         }       }

netwww1
it works, thanks!

Any way that is not all to me. With the changed will be required rebuild the code to get the min. Also maybe it's better:
left += this.component.children().length*this.component.outerWidth() - this.picker.outerWidth();

in line: https://github.com/smalot/bootstrap-datetimepicker/blob/master/js/bootstrap-datetimepicker.js#L554
Thats, to move the calendar to the left corner when there are more than one items and the arrow is set to left.

The bug is ‘top’ declared but not be assigned on line 'top = top - containerOffset.top + 169;'.
4b0c0e is a wrong commit. In issue #462, EclipseLCY said 169/210  'are not absolute, you can debug in your own project'. So his resolution shouldn't be merged into master. It's not fit all situations.

@netwww1 you are saying a reverse commit to 4b0c0e1 should fix the problem?

@AuspeXeu will partially resolved the issue, but not resolve the issue on https://github.com/smalot/bootstrap-datetimepicker/issues/462 as the problem is that the calendar used the coordinates of the local view port  to set the position in global page coordinates. What is needed is a fix to retrieve the global page coordinates and not the locals.

@AuspeXeu if you want to fix that, probably, this will be helpfully:
http://stackoverflow.com/questions/442404/retrieve-the-position-x-y-of-an-html-element
http://stackoverflow.com/questions/442404/retrieve-the-position-x-y-of-an-html-element/11396681#11396681

@AuspeXeu Reverse 4b0c0e1 to bc8bd26 can fix 'top' bug.
@lestcape I failed to reproduce the bug when set 'pickerPosition' to 'bottom-left' in 'sample in bootstrap v3' demo of ver. 2.3.8 on chrome 49. Could you upload your demo html file?

@netwww1 I revered the commit. Would be great if you could find a way to reproduce #462 :+1:

I have not an example, but i think is true what is commented, because it's the same problem described in stack overflow and will not be a coincidence. As is commented, also the bug can not be reproduced in all browser, because depend of how is implemented the offset() function. IE is the most problematic and of course this is not a news.

the fix above is Ok for IE and Firefox, but in Chrome the positioning is still wrong, as soon as there's a scrollbar.
when I open a site to full screen the control is in correct position, but when I shrink the window the control goes way down.


Channels in a hidden section of a server are displayed under a public unrelated section

I have discovered the source of the issue. A category's visibility needs to be checked against every channel it's in before hiding (note to self).


The null list is () not 0

Lines 117-118 in the tex file should read:
... and \texttt{NIL} is the name of the null list ().
rather than
and \texttt{NIL} is the name of the null list 0.
PS. Thanks for making this more legible version of the paper. 🥇

Fixed at https://github.com/jaseemabid/micromanual/pull/6. Thanks @stuartpullinger


Custom time format

Version

Development Environment

v1.6.0
Current Behavior

// Write example code

Expected Behavior

I want to custom time format, such as 12 pm replace to 12:00 (Do not use Timezone setting).

@jovey-zheng, I have the same problem. Did you find a solution?

@NazirTemirov See #171 .


Add MacOS CI

Runs for every PR. Installs latest release via Homebrew.
Will run debug and release version of Lori code against the release
version of Pony. (There's no debug version of Ponyc released at this
time).
Closes #41

Not going to merge this until the next release as the tests can't currently pass against the current release.


Filter parameters are now persistent over page changes.

Fixes https://github.com/ExpDev07/legacy-rp-admin-v3/issues/23.

ill sort the failing checks later.


How to get the number of sent and generated tokens?

This is a very important point and if such functionality already exists, I would be glad to know how to get it.

+1 for this
the output of each call should have an attribute with token usage input and output?
Maybe it's somewhere and I missed it?


Redirects on well-known endpoint

A (g)(10) impacting issue was raised here: https://github.com/inferno-framework/inferno-core/issues/229

We utilize redirects to manage multiple connections through a single gateway. For example:
https://www.medentfhirtest.com/fhir/R4/savcw237/.well-known/smart-configuration
redirects to
https://www.medentfhirtest.com/fhir/R4/.well-known/smart-configuration/index.php?medent_practice_id=savcw237
This worked for the previous Inferno test suites, but is now returning a 302 on the very first test.
Will redirects like this be supported or do we need to reconfigure our connections?
Thanks!
Savannah Dearing

I know its only been a week, but just checking in on this so we can continue testing :)

Hi @SavannahDearing -- the http client used in the discovery tests will follow the redirects automatically in the next release, out next week.
I have a feeling this might trip up some clients out there, as it tripped us up when we switched to a new http client in v2.0 of our tests.  But following redirects automatically should be a configuration option for most http libraries out there, and language in the referenced specs are vague about this, so it makes sense for us to just allow servers to do this if they'd like.

Thanks for following up, we also found the specs were a bit vague on it.  In general, with other interfacing we've been able to use redirects as long as its not a new domain name.

Pull Request: https://github.com/inferno-framework/inferno-core/pull/231


Traveling Salesman Problem using Dynamic programming in Java

Have you read the [Contributing Guidelines on Pull Requests]
Yes
Description
Implemented Traveling Salesman Problem using Dynamic programming approach in Java
(File added in dp directory)
Checklist

[x] I've read the contribution guidelines.
[x] I've checked the issue list before deciding what to submit.
[x] I've edited the README.md and link to my code.

Related Issues or Pull Requests
Fixes: https://github.com/TesseractCoding/NeoAlgo/issues/6289

Code is a bit difficult to understand that's why at some places I have tried to explain code via multiline comments in detail. @ankitaggarwal23 should I make them short as well(comments)? Can you please guide?


Add ajarmouni-st as project contributor

Background
The TSC Project Roles defines the main roles for the Zephyr Project, including
Maintainer, Collaborator, and Contributor.
By default anyone that contributes code or documentation is a Contributor, but
with the lowest GitHub Permission Level of Read. For example, Contributors
with Read permission do not have the permission to add reviewers to a pull
request.
Use this template to nominate a GitHub user for the Contributor role with
Triage permission level, which allows the user to add reviewers to a pull
request and be added as a reviewer by other users.
Nomination
I'd like to nominate @ajarmouni-st as project contributor to be able to assign him issues and reviews
GitHub User
Provide the following information about the GitHub user:

Full Name: Abderrahmane Jarmouni
GitHub username: @ajarmouni-st
Organization (optional): STMicroelectonics

Supporting Documents
https://github.com/zephyrproject-rtos/zephyr/pull/64932
https://github.com/zephyrproject-rtos/zephyr/pull/65467
https://github.com/zephyrproject-rtos/hal_stm32/pull/191

invite sent, see https://github.com/zephyrproject-rtos/zephyr/invitations


Add decimal to base in SQL select conversion and add a test

@llllllllll any comments here?

would like to merge ASAP

lgtm


Make number of blocks per cycle a const

Throughout the code, there are many "level / 4096" for calculations based on cycle. Alphanet uses 2048 blocks per cycle. If this were changed to a global CONST then a simple adjustment is all that is necessary to make code work on alphanet. Or even changing to a global variable and having a -alphanet switch.

The library should just call /chains/main/blocks/head/context/constants at the start. that way whichever node you point to (mainnet, alpha, zero), the calculations are made correctly.

That's a great idea, thanks for sharing!

This has been implemented.


tmuxPlugins.ctrlw: 0.1.0 -> 0.1.1

Motivation for this change
Release minor fixes which have been tested for a week
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[x] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Notify maintainers
It me.  (tmux plugins don't have maintainers set, but I maintain this plugin)

Thanks!


Add option to install local-stored package files

Let users install .pkg files that are already saved to ms0:/PKG (no download, install only)

Completed: 0bcf74f09d3a368b0f49b3430195ab039e77438d


any possible way to include timeout on fetch()?

couldn't find the docs for this repository...
my code looks like this:
fetch('/test', { method: 'POST', body: data })
    .then(function(response) {
        if (response.status >= 400) {
            throw new Error("Bad response from server");
        }
        return response.json();
})
    .then(function(response) {
        console.log(response)
    });

would like to fake a server response for the fetch... any ideas?
thanks in advance

+1 not sure how to add timeout

yes please, add a timeout function.

+1, please add timeout option

you can do as fellow:
fetch('/test', { method: 'POST', body: data })
.then(function(response) {
if (response.status >= 400) {
const error = new error("Bad response from server")
error.response = response
error.message = "your error message,you can swith the status and set the message"
throw error
}
return response.json();
})
.then(function(response) {
console.log(response)
}).catch(function(e){
if(!e.response){
e.message = "访问超时！"
}
return Promise.reject(e);
})
}

This isn't handling a timeout for me...

Create a timeoutPromise wrapper...
function timeoutPromise(timeout, err, promise) {
  return new Promise(function(resolve,reject) {
    promise.then(resolve,reject);
    setTimeout(reject.bind(null,err), timeout);
  }
}

You can then wrap any promise...
timeoutPromise(100, new Error('Timed Out!'), fetcn(...))
  .then(...)
  .catch(...)

It won't actually cancel an underlying connection, but will allow you to timeout a promise.

@tracker1  before you post make sure your function doesn't have syntax errors dude:
function timeoutPromise(timeout, err, promise) {
  return new Promise(function (resolve, reject) {
    promise.then(resolve, reject);
    setTimeout(reject.bind(null, err), timeout);
  **_});_**
}

When a client timeout occured, it's very important to cancel the http request.
The fetch api will offer this functionality in a near future with the FetchController.

By the way, I solved this neatly in react-native by using redux-saga.

@raarts how redux-saga solve it? Can you post code in here?

Inside a saga, race the fetch call with a timeout like this:
  try {
    const { timeout, response } = yield race({
      timeout: call(delay, 10000),
      response: call(fetch, '<your endpoint>', { parms}),
    });
    if (timeout) {
      console.log('network timeout')
    } else {
      if (response.status === 200) {
        // success
      } else {
        // API error
      }
    }
  }
  catch(error) {
    // Other error by fetch
  }

Kinda late here, this is based off of @tyler-canton code he posted up here
function fetch_timeout(url, options = {}) {
    /*
     * fetches a request like the normal fetch function
     * but with a timeout argument added.
     */
    let timeout = options.timeout || 30000;
    let timeout_err = {
        ok: false,
        status: 408
    };
    return new Promise(function(resolve, reject) {
        fetch(url, options).then(resolve, reject);
        setTimeout(reject.bind(null, timeout_err), timeout);
    });
}

This lets you use fetch like how you would normally, but just have an added timeout option. Thanks @tyler-canton

@kiorq I think you meant to do this:
fetch_timeout("http://google.com", {timeout: 500})
Rather than:
fetch("http://google.com", {timeout: 500})

This is how you should be handling abort:
const controller = new AbortController()
const signal = controller.signal
setTimeout(() => {
  controller.abort()
}, 1000)

fetch(url, { signal })

For anyone else who gets hung up on Fetch not having timeout you could use the node-fetch rather than native Fetch API. In a lot of cases a timeout isn't necessary but it is necessary if you want to ensure TCP/IP connections close out and don't just have an open socket for some undetermined time. Here's what I ended up doing with node-fetch Works really well:
https://github.com/github/fetch/issues/617

this should be in userLand

FWIW, I've opened an issue https://github.com/whatwg/fetch/issues/951 with a proposal for a timeout option that solves 90% of use cases, in case anyone's interested. I think it's super important to add to make sure calls to fetch (or res.json()) don't hang indefinitely.

@ianstormtaylor  You really made a number on every single library that uses the fetch API.
you should only have brought it up with whatwg and then the rest will follow.


moveit_calibration: 0.1.0-1 in 'noetic/distribution.yaml' [bloom]

Increasing version of package(s) in repository moveit_calibration to 0.1.0-1:

upstream repository: https://github.com/ros-planning/moveit_calibration.git
release repository: https://github.com/JStech/moveit_calibration-release.git
distro file: noetic/distribution.yaml
bloom version: 0.10.7
previous version for package: null

CI has been hung for a few days now


Inject HttpServletRequest in ContainerRequestFilter for Jersey

Framework version: 1.2
Implementations: Jersey

Scenario
Trying to inject an HttpServletRequest object in a container request filter results in an exception:
public class MyJaxRsFilter implements ContainerRequestFilter {

	@Context HttpServletRequest request;

	public void filter(ContainerRequestContext ctx) throws IOException {
    	      System.out.println("Hello JAXRS filter, request = " + request);
	}

}

Expected behavior
HttpServletRequest should be injected corectly
Actual behavior
Throws java.lang.IllegalStateException: Not inside a request scope

@martinpllu the fix for this is now in the core branch. It will go out with 1.3. The root cause of the issue is that Jersey (and the JAX-RS specs) treat suppliers as singletons so by default it does not allow injection in single-request-scoped contexts. I have added the configuration to allow "proxying" of the suppliers.


Class naming rules and updates

@brianhhu PTAL at the CONTRIBUTING.md modification. I'm currently in progress with renaming things, but I think the documentation portion is basically "reviewable". I'm in the process of trying to rename things, but if we want to adjust direction I want to be able to short-circuit what I'm doing.


Ref callbacks

Changed all refs attributes to use callbacks instead of strings, the use of which is considered legacy. See here for more details: https://facebook.github.io/react/docs/more-about-refs.html.

@Josh-ES Thanks for the PR
I will review and merge soon


⚠ ClamAV has degraded performance

In 42f1f49, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 66 ms

Resolved: ClamAV performance has improved in 6f26c91.


"React Example: Nextjs Suspense Streaming" doesn't work

Describe the bug
example doesn't work:
https://tanstack.com/query/latest/docs/framework/react/examples/nextjs-suspense-streaming

ative addon because loading addons is disabled<EMAIL_ADDRESS>⚠ Attempted to load @next/swc-linux-x64-musl, but an error occurred: Cannot load native addon because loading addons is disabled<EMAIL_ADDRESS>⨯ Failed to load SWC binary for linux/x64, see more info here: https://nextjs.org/docs/messages/failed-loading-swc

Your minimal, reproducible example
https://tanstack.com/query/latest/docs/framework/react/examples/nextjs-suspense-streaming
Steps to reproduce
.
Expected behavior
.
How often does this bug happen?
None
Screenshots or Videos
No response
Platform
.
Tanstack Query adapter
None
TanStack Query version
.
TypeScript version
No response
Additional context
No response

probably an upstream issue with stackblitz. it works fine in codesandbox.
https://codesandbox.io/p/devbox/github/tanstack/query/tree/main/examples/react/nextjs-suspense-streaming?embed=1&theme=dark


Add retries to notifications processor

TL;DR
Add retries to notifications processor to handle underlying SQS connection failures
Type

[ ] Bug Fix
[ ] Feature
[ ] Plugin

Are all requirements met?

[x] Code completed
[ ] Smoke tested
[ ] Unit tests added
[x] Code documentation added
[ ] Any pending items have an associated Issue

Complete description
How did you fix the bug, make the feature etc. Link to any design docs etc
Tracking Issue
https://github.com/lyft/flyte/issues/376
Follow-up issue
NA

Codecov Report

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

@@           Coverage Diff           @@
##           master     #106   +/-   ##
=======================================
  Coverage   62.87%   62.87%
=======================================
  Files         101      101
  Lines        7369     7369
=======================================
  Hits         4633     4633
  Misses       2191     2191
  Partials      545      545

Flag
Coverage Δ

#unittests
62.87% <ø> (ø)

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 e6addd4...4bb6c4e. Read the comment docs.

Looks good to me, just one thing, in case an error connection, should FlyteAdmin process not crash/exit?

I'm not sure - is a running admin with partial functionality better or should we fail fast?

I'm not sure - is a running admin with partial functionality better or should we fail fast?

IMO, it could be a network partition or some other issue. If we fail fast, we might be able to recover on a different node? Also, since we have multiple replica's others should be fine.
On the other hand in sandbox mode we should probably not crash as users may not be able to figure out what the problem is. I pinged Ruslan. I guess if we do it for this, we should probably do it for all other cases?

Updated so that we retry initializing the initial AWS/GCP client the number of times specified in the config but otherwise indefinitely retry in the case an open channel hiccups.


Update Generate Test File cmd to be OS dependent

Windows doesn't support dd, added platform check and changed Windows to use fsutil.

@allcontributors please add @rsandbach for code


What is response.token

Hi,
In the example there is the line
this._tokenService.setToken(response.token);
but the class 'Response' from angular/http doesn't have any field 'token' and I get an error.
Have I missed something or is it an error in the documentation?
Thanks for this library!

Ok so in this case i converted the response to json first with response.json(), my backend returns the token as the token key as follows:
{
    "token": "thegeneratedjwttokenhere"
}

Do you understand now?

I get it. Thanks!

Alright good to hear 😀


SocketError getaddrinfo: nodename nor servname provided, or not known

Hey guys,
I've got Chef-Zero runs that fail with the error SocketError getaddrinfo: nodename nor servname provided, or not known.
It looks like before that there is a INFO: HTTP Request Returned 404 Not Found : Object not found: http://localhost:8889/nodes/tester, where tester = my machine name.
Full stack trace here.
To reproduce:

Install Chef DK release candidate 5
Run chef-client -z simple.rb, where simple.rb looks something like the recipe posted below.

Recipe:
require 'chef/provisioning/aws_driver'

with_driver 'aws::us-east-1'

# Public subnet
machine 'tester' do
  tag 'test_successful'
  recipe 'hdp::hello_world'
  machine_options :bootstrap_options => {
    :key_name => 'korrelate2012',
    :image_id => 'ami-b23009da',
    :subnet => 'subnet-aebab1da',
    :security_groups => [ 'hortonworks_chef' ],
    :instance_type => 'm3.medium',
    :associate_public_ip_address => true
  }
end

knife.rb
current_dir = File.dirname(__FILE__)
log_level                :info
log_location             STDOUT
node_name                "jreid.local"
chef_zero.enabled	 true
local_mode		 true
client_key               "/Users/jreid/.ssh/korrelate2012.pem"
chef_server_url          "http://localhost:8889"
cache_type               'BasicFile'
cache_options( :path => "#{ENV['HOME']}/.chef/checksums" )
cookbook_path            [ "/Users/jreid/repo/chef-repo/cookbooks", "/Users/jreid/repo/chef-repo/site-cookbooks", "/Users/jreid/repo/chef-repo/berks-cookbooks" ]

# Amazon AWS
knife[:aws_access_key_id] = ENV['AWS_ACCESS_KEY_ID']
knife[:aws_secret_access_key] = ENV['AWS_SECRET_ACCESS_KEY']

# Bootstrap with Chef-Zero
knife[:ssh_user] = "ec2-user"
chef_zero[:port] = "8889"

Versions:  (Chef DK 5 release candidate for Mac OSX, per https://github.com/chef/chef-provisioning/issues/322)
chef (12.2.1)
chef-dk (0.5.0.rc.5)
chef-provisioning (1.0.1)
chef-provisioning-aws (1.0.4, 1.0.3)
chef-provisioning-azure (0.3.2)
chef-provisioning-fog (0.13.2)
chef-provisioning-vagrant (0.8.3)
chef-vault (2.4.0)
chef-zero (4.2.1, 1.5.6)
cheffish (1.1.2, 1.1.0)
chefspec (4.2.0)

Edit - Note that I ran into this with Chef DK 4 too.

It looks like it's not creating the node resource it needs on the Chef-Zero instance before it attempts to execute the rest of the resource.  Can anyone confirm/deny?  Are there any knife.rb or other configs I need to change?

Cross-posted from https://github.com/chef/chef-provisioning/issues/330.
I am not, at this point, 100% sure if the issue lies with my use case, chef-zero, or chef-provisioning.  I appreciate all input on this.

The issue was with the connection to AWS.  I changed my IAM keys and the issue was resolved.


Work around 25 user limit

This tool is great, I have been using it to pull down a CSV and convert it to a vCard. PagerDuty limits the number of users to 25 by default, 100 max. This is new I think because I don't recall this being an issue before. Could we please either get a workaround for this limit or some way to use the offset to get the next n users? Thanks!

@JoshFoxBuckeye Thanks for pointing this out! I've updated the code to get all the users in the account.

Going to close this issue. Please reopen if you continue to have problems.

This is perfect! Thank you so much!


[Feature Request]: Web Scrpaing code-snippets

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
I would like to add web scraping code using different python libraries & showcase different methods of handling the extracted response data.
Record

[X] I agree to follow this project's Code of Conduct
[X] I want to work on this issue
[X] I'm willing to provide further clarification or assistance if needed.

@UTSAVS26 Can you assign me this issue & add labels to it. gssoc-ext, hacktoberfest, hacktoberfest-accepted etc

Okh I thought that we can be assigned to one even if we raised new issues

@UTSAVS26 once I am done with this issue I will reopen issues one at a time


Make tileCoordTransform a member again

Instead of using the static createOriginTopLeftTileCoordTransform function, the correct transform is now a non-API config option of the tile grid. This allows e.g. ol.tilegrid.createXYZ to create a tile grid with the correct tile coord transform function built in.
Fixes #3744.
Fixes #3750.

This also fixes the currently broken tile-vector example.

I just restarted the build.

Could we have a test so that this doesn't break again in the future? :)

Adding a test now @tsauerwein.

Tests added @tsauerwein.

LGTM @ahocevar I only put one small comment

Thanks for adding the tests! Much appreciated.


Use target in docker build

This PR simplifies the Dockerfiles, making use of different targets instead of build args to differentiate different types of builds

Codecov Report

Merging #1576 (fba313a) into main (4316274) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head fba313a differs from pull request most recent head 09e9899. Consider uploading reports for the commit 09e9899 to get more accurate results

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@          Coverage Diff          @@
##            main   #1576   +/-   ##
=====================================
  Coverage   7.27%   7.27%
=====================================
  Files         44      44
  Lines      15416   15416
=====================================
  Hits        1122    1122
  Misses     14235   14235
  Partials      59      59


add username in RedisLockStore

Proposed changes:

Works on https://rasahq.atlassian.net/browse/ATO-1520
Add username to the connection arguments of RedisLockStore

Status (please check what you already did):

[ ] added some tests for the functionality
[x] updated the documentation
[x] updated the changelog (please check changelog for instructions)
[x] reformat files using black (please check Readme for instructions)

Closing this PR in favor of https://github.com/RasaHQ/rasa/pull/12835


Support for full hatchling versioning.

It looks like hatchling is being used under the hood. In my use case I'd like to utilize test.pypi and when I was using poetry I could do .dev versions.
The first one here was uploaded with rye but I found I couldn't easily support .dev versions

However to the best of my knowledge you are using hatchling under the hood.
I did the following:
Modified my pyproject:

Then I ran

So it looks like it wouldn't be to hard to implement a -dev version flag somehow.

Also here it looks like Rye can build fine with the modified version string in the pyproject.toml

I see I can call this directly as well:

So I guess I'm adding for an additional option to add a -dev version in

In any case this is my work around in GitHub action:

If you tag your releases then an alternative workaround to consider might be to switch the backend from hatchling to setuptools and then use the standard configuration of setuptools_scm to dynamically generate the version based on the latest tagged version and commit state.  Between tagged releases the default versioning scheme for that setup will automatically include a devN component based on the commit distance from the latest version tag, and you can run rye version to see the dynamically computed version. Here's the relevant snippets of configuration required in the pyproject.toml to enable that:
[project]
#version = "dynamic"
dynamic = ["version"]

[build-system]
requires = ["setuptools>=69", "setuptools_scm>=8"]
build-backend = "setuptools.build_meta"

[tool.setuptools_scm]
# can be empty if no extra settings are needed, presence enables setuptools_scm

Hatchling supports that directly and the maintainer uses this as well https://github.com/ofek/hatch-vcs


HBASE-26639 The implementation of TestMergesSplitsAddToTracker is pro…

…blematic

Use concurrent collections for safety, and only set SFT implementation on the table we created instead of globally to prevent effect system tables.
@wchevreuil FYI.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

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

 Use git apply --whitespace=fix <<patch_file>>.


removed files that belongs to Dialect/ONNX to be all under that directory

Currently, there were two optimizations, listed under Transform/ONNX/ Combine & Rewrite that were really just an implementation of the ONNX XXX Ops definition. It was awkward to have the implementations of the ONNX Ops in two different libraries. Now all the ONNX Ops classes are in the Dialect/ONNX library.
Signed-off-by: Alexandre Eichenberger<EMAIL_ADDRESS>

@sstamenova If you have the time, feel free to check the CMakeList.txt. I am by far not an expert, I migrated the file and added the new .td file to the list of dependences to be performed for the compilation in Dialect/ONNX to happen. I worry that there is a dependence between first building the ONNXOps.td before the Combine.td and Rewriter.td... but it has not occurred in my parallel build. Maybe the system is smart enough?

Should we move the common constructor utility functions in combine.cpp, rewrite.cpp and etc into ONNXOpsHelper.cpp? Also how about some common definition in *.td file?

@sstamenova If you have the time, feel free to check the CMakeList.txt. I am by far not an expert, I migrated the file and added the new .td file to the list of dependences to be performed for the compilation in Dialect/ONNX to happen. I worry that there is a dependence between first building the ONNXOps.td before the Combine.td and Rewriter.td... but it has not occurred in my parallel build. Maybe the system is smart enough?

My expectation is that tablegen in the same file will happen sequentially, which is why it is working; however, if you want to guarantee it, you can add the dependencies like so:
add_dependency(OMONNXRewriteIncGen OMONNXOpsIncGen)
add_dependency(OMONNXCombineIncGen OMONNXOpsIncGen)

This is not going to impact the build negatively (since that's the order it needs to happen anyway), so there's no downside to adding it.

Should we move the common constructor utility functions in combine.cpp, rewrite.cpp and etc into ONNXOpsHelper.cpp? Also how about some common definition in *.td file?

Done, migrated the supports in combine and rewrite into ops helper. for the td file, I am going to leave it as is for the moment.

This is not going to impact the build negatively (since that's the order it needs to happen anyway), so there's no downside to adding it.

make sense, I like it, will add,  thanks

Is it reasonable to merge Combine and Rewrite into a single file? They both implements canonicalization patterns for ONNX ops.

Jenkins Linux s390x Build #1115 [push] removed files that belon... started at 16:37

Jenkins Linux ppc64le Build #263 [push] removed files that belon... started at 16:39

Jenkins Linux amd64 Build #1117 [push] removed files that belon... started at 15:37

it reasonable to merge Combine and Rewrite into a single file? They both implements canonicalization patterns for ONNX ops.

Did not see your comment before I merged. Let me check, this seems reasonable.

Jenkins Linux s390x Build #1115 [push] removed files that belon... passed after 44 min

Jenkins Linux ppc64le Build #263 [push] removed files that belon... aborted after 46 min

Jenkins Linux amd64 Build #1117 [push] removed files that belon... aborted after 46 min


I never see any packets match this rule after create a port mapping

Problem description
I create a port mapping  for expose container port 80 to host port 8080
and then I notice a nat rule was create on iptables  with sip and dip is same container IP as following
-A POSTROUTING -s <IP_ADDRESS>/32 -d <IP_ADDRESS>/32 -p tcp -m tcp --dport 80 -j MASQUERADE
I test some traffic situation and I never see any packets match this rule

Problem location

I saw a problem on the following URL:

I couldn't find the information I wanted. I expected to find it near the following URL:

Other:

Project version(s) affected

Suggestions for a fix

Closing this ticket due to its age, and the impending refactor. If you think this is in error, feel free to reopen. Thanks!


Failed to register alt + space

Description
Every time I build the project I get these:

Steps to reproduce

build the project in debug mode.

This is either an error with Launcher or with FancyZones. I think it might occur in FancyZones if the hotkey is set to Alt+Space and Launcher has also set it to Alt+Space

@laviusmotileng-ms This happens in launcher if there is another instance of either powertoys or wox is running. Can you please verify this and try to reproduce this issue ?

need project to be rebuild.

@jyuwono Do you think it would be better to force rewrite the shortcut or we should just show error message as we already doing ?

i'm closing this.  not much we can do there.  if we did the remap low level hook, this would be fixed too

Related: #2325.


barcode bug

Hi, I have 2 issues, one is when setting the estimated cell number, CITE-seq-Count appears to force the cell count to that number.  I am worried this can lead to inaccurate/biased results.   For example, if I set cell number to 8000, I get 8000 +/- 10 cells back, if I set the same dataset to 10,000, I get ~10,000 back.  To try to avoid this, I tried to set the cell barcode mismatch to 0 and then got the following error.
Correcting cell barcodes
Looking for a whitelist
Collapsing cell barcodes
Traceback (most recent call last):
File "/home/martensc/.local/bin/CITE-seq-Count", line 11, in
load_entry_point('CITE-seq-Count==1.4.4', 'console_scripts', 'CITE-seq-Count')()
File "/home/martensc/.local/lib/python3.6/site-packages/cite_seq_count/main.py", line 394, in main
ab_map=ordered_tags_map)
File "/home/martensc/.local/lib/python3.6/site-packages/cite_seq_count/processing.py", line 368, in correct_cells
ab_map=ab_map,
File "/home/martensc/.local/lib/python3.6/site-packages/cite_seq_count/processing.py", line 312, in collapse_cells
for real_barcode in true_to_false:
TypeError: 'NoneType' object is not iterable
All I did was to add the following to my command, which works fine otherwise:  --bc_collapsing_dist 0
Thanks, Craig

Hello @craigamartens,
Thank you for pointing it out, I'll add it to my long list of fixes for 1.5.0 :)


Edgmarker position+custom edge

separated  pull request for both branches combined. not a easy merge

Closing in favor of #18


Rust python module with helpers for meta-memcache

Motivation / Description
Implementing this in rust is simple and benchmarking
the rust cost gives 20-50 ns runtime. Unfortunately
a lot of time is spent in the bridge between python
and rust, so a call to rust code is not cheap, yet
this implementation speeds up some meta-memcache
code significantly.

Took a look. Looks good at first glance, couple of questions:

Should .gitignore include everything from the template? Might be better to cut it to what's needed

What template? This was the default created for the maturin project (I did not manually tunned it), happy to change it if there is a better template.

We should remove lib.rs.old I think, no need for it since the refactor to separate files

Ops

You can have tests in a separate file if you wish to keep the files smaller, following the pattern in khepri auto load shedder and metrics exporter, where the tests are in mod tests in tests.rs and mod tests; is added to lib.rs to make sure the module is imported.

I read the convention in rust is unit tests in the same file, integration tests in separate module. But no strong opinion on this.

Took a look. Looks good at first glance, couple of questions:

Should .gitignore include everything from the template? Might be better to cut it to what's needed

What template? This was the default created for the maturin project (I did not manually tunned it), happy to change it if there is a better template.

Good point, default template is OK I guess. Just that it had a ton of extraneous stuff. It's always subjective whether to include the everything or be minimal and strip it down to just what's needed, either way is fine so if you prefer to stick with the template .gitignore then no problem.


🐛 [BUG]: Error when calling fitView and nodes haven't initialized

Is there an existing issue for this?

[X] I have searched the existing issues and this is a new bug.

Current Behavior
After loading nodes/edges on mount, then shortly after removing and loading new nodes/edges, the canvas stops working. It appears this happens when the new nodes have not been initialized when fitView is executing. The error "Error:  attribute y: Expected length, "NaN". " shows up repeatedly in the console.

Expected Behavior
The background should remain responsive.
Steps To Reproduce
I originally ran into this when loading data from a store, then shortly after loading new data from an API. I used the examples section of this project to recreate the issue.

<template>
  <VueFlow>
    <MiniMap :node-border-radius="2"/>
    <Controls/>
    <Background color="#aaa" :gap="20"/>
  </VueFlow>
</template>

Relevant log output
No response
Anything else?
No response

Thanks for reporting but my question for this case would be: Why are you even doing this? What possible use-case is there for this? ^^

The use case would be that you use a store or something that is persistent for your data. If you don't clear that store before mounting vue-flow then you could run into this issue. For example, the user could open a page that previously displayed data that is still in the store. Opening that page again with some new params would cause new data to be loaded into the store. This would cause the initial data to be loaded followed by the new data and vue-flow would freeze. My workaround for this is to conditionally clear the store when displaying something different. If nothing else, this page can act as a solution for anyone else that encounters this.

mh... okay i get that 👍
I'll see what I can do :)

Should be fixed with 1.21.2 - if the issue persists, pleas re-open the issue


grafical glitch when zooming in a big sprite in the editor

Godot version
3.3.2
System information
Linux Mint 20.1 Ulyssa
Issue description
when zooming into a sprite in the editor the sprite deforms
https://user-images.githubusercontent.com/58333865/121510280-c1252f00-c9e7-11eb-836b-eda11aeabff6.mp4

Steps to reproduce
open scene and zoom into the sprite
Minimal reproduction project
Zoom Bug.zip

Doesn't happen for me with your test scene on Arch Linux (5.12.9-arch1-1) and a 1050 Ti (proprietary driver version 465.31). Also XFCE with compositor disabled. (if you also have nVidia, maybe an OpenGL setting in nvidia-settings ?)
Also, you forgot to define your main scene (opening your project will look like nothing exists until looking at the FileSystem dock).

i dont have nividia godot tells me i have Mesa DRI Intel(R) Q45/Q43 (ELK)

I guess it's because the default camera Z-near is too big for such a zoom amount and sprite fragments are discarded from the view.

@Chaosus in dryluggage's video, only one triangle is discarded and it's only happening at ~400%-500%.
Not sure if you've tried it, but as I've said I can't replicate it.
It seems like dryluggage is using older discontinued hardware so that might be at fault here. Assuming they are on the newest graphics driver they can get, that is.

Yeah, it's a driver bug, I tried the same on Windows 10 and don't see this effect.

I guess it's because the default camera Z-near is too big for such a zoom amount and sprite fragments are discarded from the view.

Godot's 2D renderer doesn't make use of a 3D camera or Z-buffer.

Yes it still happens after disabling batching and restarting the editor


Linux editor 3d clip distance + fov settings not working

Operating system or device - Godot version:
Ubuntu 16.04
godot 2.2 + 2.1
Issue description:
Changing the fov or the clip distances in the editor do not work under linux. Looks fine under windows...
Steps to reproduce:
Make a 2kmx2km scene in blender. import. Try changing the clip planes or fov. They dont update...

I found a work around is to open the scene. Then click view > settings and change the values in there. Still I would expect the editor setting to be a global so I dont need to do this for each scene.

Our Bugsquad will review this issue more in-depth in 15 days, and potentially close it if its relevance could not be confirmed.

As there was no update since the previous post, we close this issue.
If it is still relevant in the way it was described and discussed above, please comment to ask for it to be reevaluated. If it is only partly relevant, or if the original issue has changed, it would be better to open a new issue (potentially referring to this one) focused on the current state.


Update profiles.adoc

Formatting changes for clarity.

Platforms was already italicized when introduced as a term separately for hardware platforms and software platforms.


Feature request: go to required file from require() statement

There is some existing functionality around viewing definitions of a symbol. I would like to propose an expansion of this: when the user's cursor is on a require statement in CommonJS, there is a way to jump to the file that will be returned by that statement. For instance:
const getPageName = require('./get-page-name');

I would like to be able to put my cursor on the require statement, hit a hotkey, and then open the get-page-name.js file. If the require statement is for a node module, like require('lodash'), I would expect that hitting the hotkey would open the main file of the lodash package.
Functionality very similar to this exists in Webstorm. I use it there all the time.
I would be interested in submitting a PR for this, but I'd like to see if you think this is a good idea first.
Thanks!

+1

+1

+1

I believe this is supported now: just hover over the import string and hit 'go to definition' (f12):

This will open the file for local paths and open the *.d.ts type definition file (or the typescript source) for any node modules that have them. It works with both require and import
Please let me know if this does not address the original issue or if you run into any bugs.
Thanks

This works, although I'd like to see it also work for node_modules. If I have require('lodash'), then I'd like to be able to hit 'go to definition' and open the file returned by require.resolve('lodash').