Similar Versioning Pattern

Hi There!
I just learned about this project, and I was immediately struck by how similar your versioning pattern is to the one I came up with for a volunteer project I'm working on. I thought I'd share my own pattern with you, so you could see how someone else solved a very similar problem. A few caveats: while I've been working on my pattern for about 4 months now, like yours, mine is still a work in progress. At this point, I'm pretty confident the decisions I've made are right for my project, but my project has also not reached the production stage yet.
Summary
My goal is to provide a deep level of "undo" / "undelete" functionality throughout my app:

I want to be able to track changes to node properties, but not necessarily track changes to every property on a node
I want to be able to "undelete" destroyed relationships
I want to be able to "undelete" destroyed nodes
I want to only retain the diffs between versions, so as to not take up too much database space.

These needs resulted in a few distinct database patterns
Pattern 1: for tracking changes to node properties

A tracked node has a constellation of associated :History nodes (node)-[:HISTORY]->(:History). It has one synced history node (node)-[:SYNCED_HISTORY]->(:History). I elected to not bother with (:History)-[:PREVIOUS]->(:History) relations. Instead, each :History node has a created_at timestamp which orders them.
Like your implementation, the node being tracked always contains the current state. Mine differs from yours however, in that the :History node has a single log property which contains a JSON string containing the changes needed to move from that state to the previous state. i.e. to rollback the current state to it's previous state, you would load the -[:SYNCED_HISTORY]-> and merge the serialized log property with the current node. The return value would be the previous state.
In common usage, I expect the user will either want to undo the most recent action (by grabbing the -[:SYNCED_HISTORY]->), or they will want to view all the changes in chronological order and revert to an arbitrary one. While only retaining diffs means that, in order to move from the current state to a state several version back, I'll need to load every version and apply the changes in order, I think this is an acceptable performance decision because I do not expect users to take advantage of this feature often.
Pattern 2: for tracking previously destroyed nodes
To track destroyed nodes, every node which supports tracking has either an additional :Current label or an additional :Destroyed label. These nodes also have an updated_at timestamp. How this is used: say you have a :ShoppingCart and the :ShoppingCart has many :Items. To find all of the current items (:ShoppingCart)-->(:Item:Current). To find the most recent destroyed item (:ShoppingCart)-->(item :Item:Destroyed) RETURN item ORDER BY item.updated_at DESC LIMIT 1
Neo4j makes tracking destroyed nodes very nice, because you can just swap out the :Current label for a :Destroyed label and otherwise retain all the proper relations & properties of the node.
Pattern 3: for tracking previously destroyed relationships / changes to relationships
To track relationships, it is necessary to model the relationship with a node. (node)-[:RELATION]->(:Relation:Current)-[:RELATION]->(second_node). To destroy the relation, but maintain the historical record of it (node)-[:RELATION]->(:Relation:Destroyed)-[:RELATION]->(second_node). This also allows you to track the changes to the relations properties. i.e. (:Relation:Current)-[:History]->(:History).
:History nodes associated with a :Relation are almost the same as history nodes associated with a standard node (i.e. they also have a JSON serialized log property), except that they also can have a single -[:RELATION_HISTORY]-> relation, which allows me to track changes to the relation itself. i.e. Say you have (node_a)-[:RELATION]->(:Relation:Current)-[:RELATION]->(node_b), but then you update it to (node_a)-[:RELATION]->(:Relation:Current)-[:RELATION]->(node_c). You want to track the change from (node_a)-->()-->(node_b) to (node_a)-->()-->(node_c). The persisted pattern including current :History node is:
(node_a)-[:RELATION]->(rel :Relation:Current)-[:RELATION]->(node_c)
(rel)-[:SYNCED_HISTORY]->(:History)-[:RELATION_HISTORY]->(node_b)`

The -[:RELATION_HISTORY]-> records the step necessary to move backwards to the previous state (i.e. the previous node this relation was pointed at).

Anyway, there are a few more details, but this is the bulk of it.
All of my change tracking logic has been written in Ruby, specifically for the Neo4jrb gem, so I won't share it here. This being said, if someone's interested, I'm happy to. (At some point when I have the time, probably next year, I plan on open sourcing my module and sharing it with @cheerfulstoic & the Neo4jrb project. It definitely doesn't fit into that project's "standard" library, but I could see a lot of people benefitting from it as an add-on)
Anyway, I'm not sure how clear all of this is. Let me know if you'd like me to add more info / clarify anything. I'm really intrigued by your project. I'd be interested to know if you considered a pattern similar to mine and decided against it for some reason? Also, am I correct in thinking that this library doesn't currently support tracking the destroyed / non-destroyed state of an entire node? Or of tracking relationship versions?
PS: I notice you have a "use cases" wiki. I would vote to add CRM (e.g. Salesforce, which, if you're not familiar, is a fancy address book) as a great use case. My use case is a volunteer coordination application (amazingly, all the current options available to nonprofits suck).

Hi @thefliik !
Thank you for just have dedicated some of your time to our project! 👍
I've somehow understood your model, which is an interesting one regards tracking deleted nodes. Our Core Versioner, was born in order to give people the chance to use an out of the box tool for versioning the usual Entity-State model.
We just picked a different model from yours, because, if we wanted to list States related to our Entity, the linked list was the best option, thanks to Neo4j index-free adjacency. Actually we didn't thought about storing timestamps inside our State nodes, since the linked list just came out first as our final solution.
We didn't focus on deleting nodes, since we didn't want to create a model which forces users or limit their creativity (I'm not saying yours does, since if I understood right, your model was aiming that specific use case): just by giving users the chance to add custom labels to State, they could actually give different meanings to different State.
We have scheduled just a few days ago our next step, since we want to improve our model by also versioning relationship: we will create a project here on GitHub to make some public milestones.
Thank you also for the hint about the use case, we will take a look on that!

Hey, I got busy with another project, but thanks for the prompt reply! What you've said makes sense. I'll definitely keep an eye on this library.


IADD wrong result with 3 parameters

try to reproduce by:
ILOAD a
ILOAD b
IADD
ILOAD c
IADD
Might only appear in methods other than main. Maybe also only in methods with more than 2 variables.

Closed with Commit 3fc0efd


ambiguous millis() function (with MQTT direct ESP Home added function)

The error is related to the ambiguous millis() function due to the fact that there are different definitions of this function in the code. We can solve this problem by using a specific notation of the function so that the compiler knows which version to use.
For example:
Instead of millis(), use esphome::millis() if we will refer a function defined in ESPHome.

https://github.com/tfyoung/esphome-junctek_kgf/issues/18


security vulnerability fixes

as there are a few common lib upgrade and some is big version bump, please do more integration testing in integ env.


Chaper 5 - Microphone Manager does not clean up the dicationRecognizer properly

dicationRecognizer should be disposed in the OnDestroy unity event.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.


Updated Readme.md file

Added custom images and badges to markdown file related with the respected repository to beautify the view.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: vivekverma007 sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

Sorry; at this time, we would like to keep the README file as simple Markdown and not HTML.


Compatibility issue between ZooKeeper version 3.4.6 and armeria-zookeeper3

My current environment is using ZooKeeper version 3.4.6, and I have found that the version required by armeria-zookeeper3 is too high and incompatible with my current environment. The reason is that Curator only supports ZooKeeper 3.5.x. How can I resolve this issue?

Did you try to override the versions of ZooKeeper to 3.4.6 and the corresponding Curator version forcibly? armeria-zookeeper3 uses a limited set of ZooKeeper and Curator APIs which may be compatible with the old versions.

compile("com.linecorp.armeria:armeria-zookeeper3") {
    exclude group: 'org.apache.zookeeper', module: 'zookeeper'
    exclude group: 'org.apache.curator', module: 'curator-framework'
    exclude group: 'org.apache.curator', module: 'curator-x-discovery'
    exclude group: 'org.apache.curator', module: 'curator-recipes'
}
compile('org.apache.curator:curator-recipes:4.2.0') {
    exclude group: 'org.apache.zookeeper', module: 'zookeeper'
}
compile 'org.apache.zookeeper:zookeeper:3.4.6'
compile 'org.apache.curator:curator-x-discovery:4.2.0'

Caused by: java.lang.NoSuchMethodError: org.apache.curator.framework.recipes.cache.PathChildrenCache.getListenable()Lorg/apache/curator/framework/listen/Listenable;
	at com.linecorp.armeria.client.zookeeper.ZooKeeperEndpointGroup.pathChildrenCache(ZooKeeperEndpointGroup.java:138) ~[armeria-zookeeper3-1.25.2.jar:?]
	at com.linecorp.armeria.client.zookeeper.ZooKeeperEndpointGroup.<init>(ZooKeeperEndpointGroup.java:129) ~[armeria-zookeeper3-1.25.2.jar:?]
	at com.linecorp.armeria.client.zookeeper.ZooKeeperEndpointGroupBuilder.build(ZooKeeperEndpointGroupBuilder.java:71) ~[armeria-zookeeper3-1.25.2.jar:?]

Thanks for checking the difference. We may need to add an integration test to verify if armeria-zookeeper3 is compatible with ZooKeeper 3.4.6.
If there is an alternative API that we can use directly or via reflection, we can add the workaround for that. Are you interested in sending a PR?

The reason is that Curator only supports ZooKeeper 3.5.x. How can I resolve this issue?

Hi! Did you have a chance to upgrade the Curator to 5.5.0 by the way?
https://mvnrepository.com/artifact/org.apache.curator/curator-client/5.5.0
It uses ZooKeeper 3.7.1 that armeria-zookeeper3 uses.

原因是Curator只支持ZooKeeper 3.5.x。我该如何解决这个问题？

你好！顺便问一下，您有机会将 Curator 升级到 5.5.0 吗？ https://mvnrepository.com/artifact/org.apache.curator/curator-client/5.5.0 它使用使用的ZooKeeper 3.7.1 armeria-zookeeper3。

I am unable to upgrade at the moment as many of the services I depend on are using version 3.4.x, and upgrading carries significant risks for me.

PathChildrenCache.getListenable() in Curator 4.2 returns ListenerContainer whose super interface is Listenable. https://github.com/apache/curator/blob/dc6e78513aa076545552b2661940f6ed4bcc5e75/curator-recipes/src/main/java/org/apache/curator/framework/recipes/cache/PathChildrenCache.java#L397
A small reflection would be acceptable to invoke the method while avoiding incompatibility. @wang-qijia Are you interested in sending a PR?


feat: expose configuration properties via HASS discovery

but disable them by default. this gives you the option of creating automations around them if you desire, or ignoring them if you don't need them

@zwave-js-bot fix lint

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.06%) to 22.157%

Totals

Change from base Build<PHONE_NUMBER>:
0.06%

Covered Lines:
3764

Relevant Lines:
18061

💛  - Coveralls


DRILL-7292: Remove V1 and V2 text readers

Drill 1.16 introduced the "V2" text reader based on the row set
and provided schema mechanisms. V3 was available by system/session
option as the functionality was considered experimental.
The functionality has now undergone thorough testing. This commit makes
the V3 text reader available by default, and removes the code for the
original "V1" and the "new" (compliant, "V2") text reader.
The system/session options that controlled reader selection are retained
for backward compatibility, but they no longer do anything.
Specific changes:

Removed the V2 "compliant" text reader.
Moved the "V3" to replace the "compliant" version.
Renamed the "complaint" package to "reader."
Removed the V1 text reader.
Moved the V1 text writer (still used with the V2 and V3 readers)
into a new "writer" package adjacent to the reader.
Removed the CSV tests for the V2 reader, including those that
demonstrated bugs in V2.
V2 did not properly handle the quote escape character. One or two unit
tests depended on the broken behavior. Fixed them for the correct
behavior.
Behavior of "messy quotes" (those that appear in a non-quoted field)
was undefined for the text reader. Added a test to clearly demonstrate
the (somewhat odd) behavior. The behavior itself was not changed.

Reran all unit tests to ensure that they work with the now-default V3
text reader.

Travis build failed due to protobuf changes. However, this PR changed no protobufs: neither a .proto file or the generated .java files. Anyone know why the Travis build is complaining?

Ran the unit tests, Functional and Advanced, there are four expected failures on Functional tests (asked @agozhiy to take a look).
Regarding protobuf job failures, @vvysotskyi will take a look. Mostly likely they are not related to your changes.

Issue with protobufs is a bug, will be fixed in https://issues.apache.org/jira/browse/DRILL-7294.

@arina-ielchiieva, thank you for the review. Please check if the revised option messages are clear.
The test failures may be due to bugs fixed in the text reader.  @vvysotskyi, check if the files in question try to use the back-slash as the escape character. Drill's text readers are configured to use the quote character as an escape by default, but the code did not correctly handle this case. If the file contains the pattern \" or "", then the text reader will produce a different result than previously.
Otherwise, please do point me to the errors and I'll track down the issues.

@paul-rogers test files are related due to partition column placement change, so they are expected.
+1, LGTM.


HBASE-28182 Create ref files using threadpool as part of merge

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

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

_ Prechecks _

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

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

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

_ branch-2 Compile Tests _

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

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

+1 :green_heart:
checkstyle
0m 34s
branch-2 passed

+1 :green_heart:
spotless
0m 43s
branch has no errors when running spotless:check.

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

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
2m 35s
the patch passed

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

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

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

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

-0 :warning:
whitespace
0m  1s
The patch 31 line(s) with tabs.

+1 :green_heart:
hadoopcheck
13m 28s
Patch does not cause any errors with Hadoop 2.10.2 or 3.2.4 3.3.6.

-1 :x:
spotless
0m 37s
patch has 63 errors when running spotless:check, run spotless:apply to fix.

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

_ Other Tests _

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

31m 47s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5487/1/artifact/yetus-general-check/output/Dockerfile

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

Optional Tests
dupname asflicense javac spotbugs hadoopcheck hbaseanti spotless checkstyle compile

uname
Linux 4c33627d7957 5.4.0-163-generic #180-Ubuntu SMP Tue Sep 5 13:21:23 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 4f3e63e5de

Default Java
Eclipse Adoptium-11.0.17+8

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

whitespace
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5487/1/artifact/yetus-general-check/output/whitespace-eol.txt

whitespace
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5487/1/artifact/yetus-general-check/output/whitespace-tabs.txt

spotless
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5487/1/artifact/yetus-general-check/output/patch-spotless.txt

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

modules
C: hbase-server U: hbase-server

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5487/1/console

versions
git=2.34.1 maven=3.8.6 spotbugs=4.7.3

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

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

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

_ Prechecks _

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
2m 32s
branch-2 passed

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

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

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

_ Patch Compile Tests _

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

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

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

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

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

_ Other Tests _

+1 :green_heart:
unit
206m  4s
hbase-server in the patch passed.

227m  6s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5487/1/artifact/yetus-jdk8-hadoop2-check/output/Dockerfile

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 11fd08a96c5b 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 4f3e63e5de

Default Java
Temurin-1.8.0_352-b08

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5487/1/testReport/

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

modules
C: hbase-server U: hbase-server

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5487/1/console

versions
git=2.34.1 maven=3.8.6

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

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

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

_ Prechecks _

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
2m 50s
branch-2 passed

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

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

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

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
2m 36s
the patch passed

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

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

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

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

_ Other Tests _

+1 :green_heart:
unit
214m 30s
hbase-server in the patch passed.

237m 23s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5487/1/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 2b87ab671ccd 5.4.0-156-generic #173-Ubuntu SMP Tue Jul 11 07:25:22 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 4f3e63e5de

Default Java
Eclipse Adoptium-11.0.17+8

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5487/1/testReport/

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

modules
C: hbase-server U: hbase-server

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5487/1/console

versions
git=2.34.1 maven=3.8.6

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

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

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

_ Prechecks _

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
2m 29s
branch-2 passed

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

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

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

_ Patch Compile Tests _

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

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

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

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

-0 :warning:
javadoc
0m 20s
hbase-server generated 2 new + 21 unchanged - 0 fixed = 23 total (was 21)

_ Other Tests _

-1 :x:
unit
0m 37s
hbase-server in the patch failed.

16m 21s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5487/2/artifact/yetus-jdk8-hadoop2-check/output/Dockerfile

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux d44d2900596f 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 308c206724

Default Java
Temurin-1.8.0_352-b08

mvninstall
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5487/2/artifact/yetus-jdk8-hadoop2-check/output/patch-mvninstall-root.txt

shadedjars
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5487/2/artifact/yetus-jdk8-hadoop2-check/output/patch-shadedjars.txt

javadoc
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5487/2/artifact/yetus-jdk8-hadoop2-check/output/diff-javadoc-javadoc-hbase-server.txt

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

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5487/2/testReport/

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

modules
C: hbase-server U: hbase-server

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5487/2/console

versions
git=2.34.1 maven=3.8.6

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

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

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

_ Prechecks _

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
2m 55s
branch-2 passed

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

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

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

_ Patch Compile Tests _

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

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

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

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

-0 :warning:
javadoc
0m 21s
hbase-server generated 2 new + 84 unchanged - 0 fixed = 86 total (was 84)

_ Other Tests _

-1 :x:
unit
0m 43s
hbase-server in the patch failed.

17m 54s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5487/2/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux f84b0aa3ab02 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 308c206724

Default Java
Eclipse Adoptium-11.0.17+8

mvninstall
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5487/2/artifact/yetus-jdk11-hadoop3-check/output/patch-mvninstall-root.txt

shadedjars
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5487/2/artifact/yetus-jdk11-hadoop3-check/output/patch-shadedjars.txt

javadoc
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5487/2/artifact/yetus-jdk11-hadoop3-check/output/diff-javadoc-javadoc-hbase-server.txt

unit
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5487/2/artifact/yetus-jdk11-hadoop3-check/output/patch-unit-hbase-server.txt

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5487/2/testReport/

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

modules
C: hbase-server U: hbase-server

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5487/2/console

versions
git=2.34.1 maven=3.8.6

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

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

_ Prechecks _

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

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

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

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
2m 49s
branch-2 passed

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

+1 :green_heart:
checkstyle
0m 38s
branch-2 passed

+1 :green_heart:
spotless
0m 45s
branch has no errors when running spotless:check.

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

_ Patch Compile Tests _

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

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

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

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

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

-1 :x:
hadoopcheck
1m 48s
The patch causes 11 errors with Hadoop v2.10.2.

-1 :x:
hadoopcheck
3m 39s
The patch causes 11 errors with Hadoop v3.2.4.

-1 :x:
hadoopcheck
5m 33s
The patch causes 11 errors with Hadoop v3.3.6.

+1 :green_heart:
spotless
0m 48s
patch has no errors when running spotless:check.

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

_ Other Tests _

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

23m 29s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5487/2/artifact/yetus-general-check/output/Dockerfile

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

Optional Tests
dupname asflicense javac spotbugs hadoopcheck hbaseanti spotless checkstyle compile

uname
Linux 75e82a362d41 5.4.0-163-generic #180-Ubuntu SMP Tue Sep 5 13:21:23 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 308c206724

Default Java
Eclipse Adoptium-11.0.17+8

mvninstall
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5487/2/artifact/yetus-general-check/output/patch-mvninstall-root.txt

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

hadoopcheck
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5487/2/artifact/yetus-general-check/output/patch-javac-2.10.2.txt

hadoopcheck
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5487/2/artifact/yetus-general-check/output/patch-javac-3.2.4.txt

hadoopcheck
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5487/2/artifact/yetus-general-check/output/patch-javac-3.3.6.txt

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

modules
C: hbase-server U: hbase-server

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5487/2/console

versions
git=2.34.1 maven=3.8.6 spotbugs=4.7.3

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
3m 43s
Docker mode activated.

_ Prechecks _

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

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

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

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
2m 45s
branch-2 passed

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

+1 :green_heart:
checkstyle
0m 36s
branch-2 passed

+1 :green_heart:
spotless
0m 44s
branch has no errors when running spotless:check.

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

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
2m 38s
the patch passed

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

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

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

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

+1 :green_heart:
hadoopcheck
13m 51s
Patch does not cause any errors with Hadoop 2.10.2 or 3.2.4 3.3.6.

-1 :x:
spotless
0m 36s
patch has 21 errors when running spotless:check, run spotless:apply to fix.

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

_ Other Tests _

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

34m 58s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5487/3/artifact/yetus-general-check/output/Dockerfile

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

Optional Tests
dupname asflicense javac spotbugs hadoopcheck hbaseanti spotless checkstyle compile

uname
Linux 5afa825240b4 5.4.0-169-generic #187-Ubuntu SMP Thu Nov 23 14:52:28 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 308c206724

Default Java
Eclipse Adoptium-11.0.17+8

checkstyle
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5487/3/artifact/yetus-general-check/output/diff-checkstyle-hbase-server.txt

spotless
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5487/3/artifact/yetus-general-check/output/patch-spotless.txt

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

modules
C: hbase-server U: hbase-server

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5487/3/console

versions
git=2.34.1 maven=3.8.6 spotbugs=4.7.3

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

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

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

_ Prechecks _

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
2m 49s
branch-2 passed

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

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

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

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
2m 15s
the patch passed

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

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

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

-0 :warning:
javadoc
0m 21s
hbase-server generated 2 new + 21 unchanged - 0 fixed = 23 total (was 21)

_ Other Tests _

+1 :green_heart:
unit
207m 35s
hbase-server in the patch passed.

230m 37s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5487/3/artifact/yetus-jdk8-hadoop2-check/output/Dockerfile

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 0454dab9010a 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 308c206724

Default Java
Temurin-1.8.0_352-b08

javadoc
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5487/3/artifact/yetus-jdk8-hadoop2-check/output/diff-javadoc-javadoc-hbase-server.txt

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5487/3/testReport/

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

modules
C: hbase-server U: hbase-server

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5487/3/console

versions
git=2.34.1 maven=3.8.6

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

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

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

_ Prechecks _

_ branch-2 Compile Tests _

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

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

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

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

_ Patch Compile Tests _

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

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

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

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

-0 :warning:
javadoc
0m 36s
hbase-server generated 2 new + 84 unchanged - 0 fixed = 86 total (was 84)

_ Other Tests _

+1 :green_heart:
unit
261m  0s
hbase-server in the patch passed.

291m 57s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5487/3/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 7911e0fde819 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 308c206724

Default Java
Eclipse Adoptium-11.0.17+8

javadoc
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5487/3/artifact/yetus-jdk11-hadoop3-check/output/diff-javadoc-javadoc-hbase-server.txt

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5487/3/testReport/

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

modules
C: hbase-server U: hbase-server

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5487/3/console

versions
git=2.34.1 maven=3.8.6

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

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

_ Prechecks _

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

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

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

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
2m 39s
branch-2 passed

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

+1 :green_heart:
checkstyle
0m 36s
branch-2 passed

+1 :green_heart:
spotless
0m 42s
branch has no errors when running spotless:check.

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

_ Patch Compile Tests _

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

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

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

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

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

+1 :green_heart:
hadoopcheck
14m 43s
Patch does not cause any errors with Hadoop 2.10.2 or 3.2.4 3.3.6.

+1 :green_heart:
spotless
0m 42s
patch has no errors when running spotless:check.

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

_ Other Tests _

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

33m 50s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5487/4/artifact/yetus-general-check/output/Dockerfile

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

Optional Tests
dupname asflicense javac spotbugs hadoopcheck hbaseanti spotless checkstyle compile

uname
Linux 63cc2191f3df 5.4.0-169-generic #187-Ubuntu SMP Thu Nov 23 14:52:28 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 308c206724

Default Java
Eclipse Adoptium-11.0.17+8

checkstyle
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5487/4/artifact/yetus-general-check/output/diff-checkstyle-hbase-server.txt

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

modules
C: hbase-server U: hbase-server

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5487/4/console

versions
git=2.34.1 maven=3.8.6 spotbugs=4.7.3

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

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

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

_ Prechecks _

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
2m 45s
branch-2 passed

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

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

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

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
2m 33s
the patch passed

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

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

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

-0 :warning:
javadoc
0m 21s
hbase-server generated 2 new + 84 unchanged - 0 fixed = 86 total (was 84)

_ Other Tests _

+1 :green_heart:
unit
202m 38s
hbase-server in the patch passed.

224m 46s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5487/4/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 44fa0fba14cf 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 308c206724

Default Java
Eclipse Adoptium-11.0.17+8

javadoc
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5487/4/artifact/yetus-jdk11-hadoop3-check/output/diff-javadoc-javadoc-hbase-server.txt

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5487/4/testReport/

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

modules
C: hbase-server U: hbase-server

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5487/4/console

versions
git=2.34.1 maven=3.8.6

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

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

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

_ Prechecks _

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
2m 13s
branch-2 passed

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

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

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

_ Patch Compile Tests _

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

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

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

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

-0 :warning:
javadoc
0m 22s
hbase-server generated 2 new + 21 unchanged - 0 fixed = 23 total (was 21)

_ Other Tests _

+1 :green_heart:
unit
207m 36s
hbase-server in the patch passed.

228m 15s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5487/4/artifact/yetus-jdk8-hadoop2-check/output/Dockerfile

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux b140cbb8a563 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 308c206724

Default Java
Temurin-1.8.0_352-b08

javadoc
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5487/4/artifact/yetus-jdk8-hadoop2-check/output/diff-javadoc-javadoc-hbase-server.txt

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5487/4/testReport/

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

modules
C: hbase-server U: hbase-server

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5487/4/console

versions
git=2.34.1 maven=3.8.6

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

This message was automatically generated.


mapping object to payload

[ ] encode/decode payload data
[ ]  encode/decode json //MediaType.APPLICATION_JSON
[ ]  encode/decode bson
[ ]  encode decode xml //MediaType.APPLICATION_XML
[ ]  encode/decode protobuf

Please add support for "Concise Binary Object Representation (CBOR)"


Proposed 0.32.0-b2

Current coverage is 69.59%

Merging #1610 into develop will increase coverage by +1.44% as of c6ce2da

@@            develop   #1610   diff @@
=======================================
  Files           908     908
  Stmts         67295   67393     +98
  Branches          0       0
  Methods           0       0
=======================================
+ Hit           45862   46903   +1041
  Partial           0       0
+ Missed        21433   20490    -943

Review entire Coverage Diff as of c6ce2da

Powered by Codecov. Updated on successful CI builds.


Add package.json support

I'd like to be able to do this in a package.json script:
command-exists XYZ || 'echo installing command XYZ'
Can this be done?

@derekgreer, it could be done by creating a smaller wrapper around this module. In particular, node packages can expose command line commands like that (see, e.g. https://developer.okta.com/blog/2019/06/18/command-line-app-with-nodejs).
I don't have time to implement at the moment, however would be happy to review a PR.

@derekgreer, it could be done by creating a smaller wrapper around this module. In particular, node packages can expose command line commands like that (see, e.g. https://developer.okta.com/blog/2019/06/18/command-line-app-with-nodejs).
I don't have time to implement at the moment, however would be happy to review a PR.


Inproper defindexes in parseString

Non-Craftable Killstreak Eyelander Kit defindex returned: 5726 expected: 6527
Genuine Marxman defindex returned: 816 expected: 837
Any warpaint - you return 9536 - which is generic warpaint, instead of returning the specific warpaint defindex
Cool Candy Coated War Paint (Battle Scarred) defindex returned: 9536 expected: 17258
This is just a diference between your library and autobot library, I'm not 100% sure problem is in your library
Hot Blitzkrieg SMG (Battle Scarred) defindex returned: 203 expected: 15153

Hey, these issues are related to schema implementation. That's why you can implement it on your own to fix these issues, tf2-item-format/static part is not meant for production applications, but rather for quick conversion between different formats in small applications. I've know autobot has large sets of hard coded definition indices and I'm conflicted whether or not I should try to add those to the static part. You are of course free to make a pull request.
This issue is related to the parseString function which can only obtain limited data from just item name. For parseEconItem there is an extra option useTrueDefindex to get the data from tf2 wiki link.


ssca1: process results script w/ non-thread case

Add check to results processing script to avoid error if using non-threaded case.

@manjugv @MattBBaker I added this to threaded dir to keep files in sync.


AMBARI-23519 - Removal of Repository Version State

What changes were proposed in this pull request?
{{RepositoryVersionState}} is no longer used since Ambari does not track installation of a single repository anymore. This is because multiple mpacks may come from the state repository. The replacement, {{MpackInstallState}} was already introduced in AMBARI-23205.
How was this patch tested?
Removal of dead code, did a simple deploy.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/1725/
Test FAILed.
Test FAILured.


Check mobile compatibility for limited guests

We should make sure the mobile app is compatible with the changes being made in zulip/zulip#10970.

I've just taken a look at this, and I've sent #5790 to fix the two issues I found.
I think neither of those is a showstopper. So we should get those fixes out promptly, but not worry about some users still having old clients while encountering the new feature.
I was testing on an approximation of the real feature, though: I tried running https://github.com/zulip/zulip/pull/27544 in my dev server, but AFAICT that PR doesn't yet actually make it possible to enable the feature — it only lays the groundwork. So it'd be good to re-check compatibility when there's something more like a working version of the server feature which can be tried out.

Details on the severity of the two issues

They're crashes, which is bad.
But they happen only on relatively uncommon actions (tapping a message sender's name or avatar to go to their profile, or selecting "See who reacted" on a message), and only if the user involved is one you're not able to see, even though they sent or reacted to a message you're looking at.
And I believe even getting into the latter situation is a fairly uncommon edge case: IIUC you can see any user you're in a stream with, and any user you have DM history with, so it'd have to be something like that the user has since left the stream.

Details on how I approximated the "limited guests" feature
I applied the following ad-hoc diff:
--- a/src/users/usersReducer.js
+++ b/src/users/usersReducer.js
@@ -14,2 +14,4 @@ const initialState: UsersState = NULL_ARRAY;

+const allowedUsers = new Set(["Cordelia, Lear's daughter", 'Polonius']);
+
 export default (
@@ -23,3 +25,3 @@ export default (
     case REGISTER_COMPLETE:
-      return action.data.realm_users;
+      return action.data.realm_users.filter(u => allowedUsers.has(u.full_name));

This causes the app, when it's first loading server data, to drop on the floor any users other than the two named. (And other than deactivated users and system bots, which this diff doesn't affect.) Then I logged into my dev server as Polonius, a guest user.
Details on what I tested
I explored various parts of the UI in the presence of unknown users, trying to think of all the various places we show information on a user:

The inbox screen, and the DM-conversations screen. These behaved fine — any conversations involving unknown users were just omitted.
IIUC any users we have DM history with should not be unknown, so this shouldn't even come up.

The message list. This was fine — the name and avatar of a message sender shows up even if the user is unknown, because we get it from the message object anyway.

Lists of all users: specifically the "New DM" screen and the "Add subscribers" (to a stream) screen. (There are a couple of other places these lists can appear, but they use the same code so I stopped after those two.) These worked fine — any unknown users just don't show up.

Autocomplete for @-mentions. This worked fine — any unknown users just don't show up.

The profile screen, and the "See who reacted" screen. These crashed as described above.

I also looked through the code:

We have a getUserForId function which looks up a user by their user ID and throws if not found. (After all, until this feature, in the bulk of the app that could only be a sign of a bug.) This was the source of both of the crashes above. I looked at all call sites; the remaining two are harmless.
I looked around the code for places where rather than showing UI, we're handling an event from the server, and where we might look up data on a user. All the ones I found are already using tryGetUserForId (the non-throwing version of getUserForId, and are doing something reasonable if they don't find the user.
I also looked at where we handle opening a notification (and trying to navigate to the conversation). There too, if we don't find the user then we just fail gracefully rather than crash.

Awesome, thank you for the investigation and the detailed notes!
@sahil839 FYI

I tested and confirmed that the avatar issue (zulip/zulip#28071) has been fixed. So from Greg's message above, I think the following is the only remaining item, and fixing it would close this issue?

Lists of users (the "user list" component found in several places including "New DM", and the autocomplete for @-mentions) include the unknown users and shouldn't. We can fix that once a planned server feature is added.

965869d3f8e added client capability to not receive data for unknown users.

Thanks @chrisbobbe and @sahil839 for those updates! I've filed #5808 for the followup based on those. The compatibility is now thoroughly checked, so closing this issue.


Replicates

What problem is the PR solving / What's new?
Sample merging and combining of biological replicates in ATAC-peak calling must both be possible. This PR allows just that.
What did change

Sample merging can now be performed by technical_replicates: merge, which follows column replicate in samples.tsv.
Biological replicates can be combined with biological_replicates: idr/fisher, which follows columns condition in samples.tsv.

Additional changes

Simplified code logic in many places: instead of checking if replicates are merged everywhere and then either taking all samples in samples.tsv, or taking a subset each time, a new dataframe is made, treps (from technical replicates), to which can be referenced.
Similarly, a dataframe with unique biological replicates, breps, is also made in merge_replicates.smk.
A copy of samples.tsv and config.yaml is not made into the result_dir.

Shortcommings
Ideally, I would like to split merged samples per assembly. This way, all assemblies can have a (combined) sample named stage12 for instance. The way fastqc is set up prevents this however, so each name in column replicate must be unique between assemblies.
Does this need additional test(s)?
In a perfect world, we would cycle through all the possible permutations of technical and biological replicates, using a sampleset containing both singular and multiple samples per technical and biological replicate. That would take hours however, so I'll add a dryrun version of this.

fix #186

Jenkins wont run, ill try to reopen the PR

p.s. I was planning to merge develop into master with a couple of small changes of the past time. I think this shouldn't go yet into master, since it's probable that there are quite some edge cases that fail. Same goes for #200


Handle initial missing /dev/ttyS0 error

When block runs for the first time without the user having set DT overlay configuration settings, /dev/ttyS0 is not present on the Fin v1.1.0. This is throwing an unhandled promise error.

#31 handles this


beta 6 for 12.2-ipa file

Hello,
there is no ipa file for beta 6. How can i jailbreak with zip file?

mistake


Implement custom date format support in omnisci backend

We have merged custom date format support feature in arrow-cpp. We need to check if it is supported in python and implement custom format support for our omnisci backend.

@Garra1980 Let's choose a priority

HDK engine is deprecated and will be removed in a future version.


[Feature Request] Replace logger with microsoft logging lib

It would cool to use the logging lib provided by https://docs.microsoft.com/en-us/dotnet/api/microsoft.extensions.logging.ilogger-1?view=aspnetcore-2.2.

we may provide some higher level abstractions in the future, including for ASP.NET, and we may make use of this there. we definitely won't add it to the core library because we care a lot about maintaining the widest possible compatibility and keeping dependencies to a minimum (this dependency requires .net core).

For the newest version of the interface only netstandard 2.0 is required. https://www.nuget.org/packages/Microsoft.Extensions.Logging.Abstractions/2.2.0
Beside, It would great to be able to replace the Console.WriteLine. For example, to allow user to set a logger in a consumer builder. It could be a small logging interface.

the core library is currently compatible with netstandard1.3 and net451 - there is a lot of demand for this, it doesn't make sense to give this up for small convenience in logging in some scenarios. You can use SetLogHandler to implement any log handling code you like (which will override the logging to stderr, which librdkafka does by default). In the future, we may provide an abstraction that uses Microsoft.Extensions.Logging out of the box for use with asp.net, but we haven't done this yet.


why NLog.LogManager.GetCurrentClassLogger() running long time?

for my test, it running about 30 seconds always, at console program. May i know why? how to resolve this problem?
NLog version: 4.9.2
.Net version: 4.5.2

Tried to enable Just my code ? (VS2019 is extremely slow at loading debug symbols)

Hi! Thanks for opening your first issue here! Please make sure to follow the issue template - so we could help you better!

May i know where to get the issue template? Thanks.

Tried to enable Just my code ? (VS2019 is extremely slow at loading debug symbols)

no problem if debug in VS2019. it occurs after publish it then running.

It could be that writing to the target takes a long time? Please share your NLog config and make sure directories exists etc.

Please also enable and check the internal log

It could be that writing to the target takes a long time? Please share your NLog config and make sure directories exists etc.

please reference the added config informance and internal.log, and the directory is existing.

Please add the requested info, so we could help you better! (This issue will be closed in 7 days)

may i know what requested info you need? thanks.

Could you change internalLogLevel="Debug" and run the capture of startup again?

may i know what requested info you need?

That was the Nlog.config and InternalLogger-details. Many users come and ask a question, and never return.

found write internal.log even after program running 30 seconds.

Not sure I understand.

What happens if you do this instead (Will be the new default in NLog 5):
ILogger logger = NLog.LogManager.Setup().SetupExtensions(e => e.AutoLoadAssemblies(false)).GetCurrentClassLogger();

Could you change internalLogLevel="Debug" and run the capture of startup again?

may i know what requested info you need?

That was the Nlog.config and InternalLogger-details. Many users come and ask a question, and never return.

found write internal.log even after program running 30 seconds.

Not sure I understand.
program begin running at 17:01:42
NLog begin write log at 17:02:16, duration 34 seconds.

34 seconds, I wonder to know Why does it take so long？ Does there exist some method to reduce the time?

We are also curious, since we don't have the problem. But if you don't provide the requested details. Then we cannot help.
So please lower internal-Logger loglevel. And also try testing if AutoLoadAssemblies changes anything.
Sent from my Sony Xperia
---- StevenFlyover wrote ----
Could you change internalLogLevel="Debug" and run the capture of startup again?
may i know what requested info you need?
That was the Nlog.config and InternalLogger-details. Many users come and ask a question, and never return.
found write internal.log even after program running 30 seconds.
Not sure I understand.
program begin running at 17:01:42
NLog begin write log at 17:02:16, duration 34 seconds.
34 seconds, I wonder to know Why does it take so long？ Does there exist some method to reduce the time?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/NLog/NLog/issues/4156#issuecomment-722922824, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACXZ7HCVYN5LYEW5WDA6Z6DSOOP43ANCNFSM4TKYF3SQ.

requested

FYI.
2020-11-06 15:03:52.9735 Debug ScanAssembly('NLog, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=5120e14c03d0593c')
2020-11-06 15:03:53.0435 Debug Found assembly location directory: 'C:\publish\Test\ConsoleApp1\Application Files\ConsoleApp1_1_0_0_8' (NLog, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=5120e14c03d0593c)
2020-11-06 15:03:53.0435 Debug Search for auto loading files in location: C:\publish\Test\ConsoleApp1\Application Files\ConsoleApp1_1_0_0_8
2020-11-06 15:03:53.0565 Debug Found assembly location directory: 'C:\publish\Test\ConsoleApp1\Application Files\ConsoleApp1_1_0_0_8' (ConsoleApp1, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null)
2020-11-06 15:03:53.0565 Debug Auto loading based on AppDomain-BaseDirectory found location: C:\publish\Test\ConsoleApp1\Application Files\ConsoleApp1_1_0_0_8
2020-11-06 15:03:53.0565 Debug Start auto loading, location: C:\publish\Test\ConsoleApp1\Application Files\ConsoleApp1_1_0_0_8
2020-11-06 15:03:53.0565 Debug Auto loading done
2020-11-06 15:03:53.0745 Info Message Template Auto Format enabled
2020-11-06 15:03:53.1055 Debug Setting 'UppercaseLayoutRendererWrapper.uppercase' to 'true'
2020-11-06 15:03:53.1195 Debug Setting 'FileTarget.name' to 'logFile'
2020-11-06 15:03:53.1195 Debug Setting 'FileTarget.fileName' to '${basedir}/logs/${processname}.log'
2020-11-06 15:03:53.1355 Debug Setting 'FileTarget.layout' to '${longdate} | ${pad:padding=5:inner=${uppercase:${level}}} | ${callsite} Line:${callsite-linenumber} | T[${threadid}] | ${message} ${exception:innerFormat=tostring:format=tostring,Data}'
2020-11-06 15:03:53.1355 Debug Setting 'PaddingLayoutRendererWrapper.padding' to '5'
2020-11-06 15:03:53.1355 Debug Setting 'UppercaseLayoutRendererWrapper.Inner' to '${level}'
2020-11-06 15:03:53.1625 Debug Setting 'ExceptionLayoutRenderer.innerFormat' to 'tostring'
2020-11-06 15:03:53.1675 Debug Setting 'ExceptionLayoutRenderer.format' to 'tostring,Data'
2020-11-06 15:03:53.1675 Debug Setting 'FileTarget.archiveFileName' to '${basedir}/logs/Archive/${processname}log{#}.zip'
2020-11-06 15:03:53.1675 Debug Setting 'FileTarget.archiveEvery' to 'Day'
2020-11-06 15:03:53.1845 Debug Setting 'FileTarget.archiveNumbering' to 'DateAndSequence'
2020-11-06 15:03:53.1845 Debug Setting 'FileTarget.archiveDateFormat' to 'yyyyMMdd'
2020-11-06 15:03:53.1845 Debug Setting 'FileTarget.maxArchiveFiles' to '30'
2020-11-06 15:03:53.1965 Debug Setting 'FileTarget.archiveAboveSize' to '2097152'
2020-11-06 15:03:53.1965 Debug Setting 'FileTarget.encoding' to 'utf-8'
2020-11-06 15:03:53.1965 Debug Setting 'FileTarget.enableFileDelete' to 'true'
2020-11-06 15:03:53.1965 Debug Setting 'FileTarget.enableArchiveFileCompression' to 'true'
2020-11-06 15:03:53.2155 Info Adding target File Target[logFile]
2020-11-06 15:03:53.2155 Debug Registered target logFile: NLog.Targets.FileTarget
2020-11-06 15:03:53.2275 Debug Setting 'UppercaseLayoutRendererWrapper.uppercase' to 'true'
2020-11-06 15:03:53.2275 Debug Setting 'ColoredConsoleTarget.name' to 'console'
2020-11-06 15:03:53.2275 Debug Setting 'ColoredConsoleTarget.layout' to '${longdate} | ${pad:padding=5:inner=${uppercase:${level}}} | ${callsite} Line:${callsite-linenumber} | ${message} ${exception:innerFormat=tostring:format=tostring,Data}'
2020-11-06 15:03:53.2275 Debug Setting 'PaddingLayoutRendererWrapper.padding' to '5'
2020-11-06 15:03:53.2445 Debug Setting 'UppercaseLayoutRendererWrapper.Inner' to '${level}'
2020-11-06 15:03:53.2445 Debug Setting 'ExceptionLayoutRenderer.innerFormat' to 'tostring'
2020-11-06 15:03:53.2445 Debug Setting 'ExceptionLayoutRenderer.format' to 'tostring,Data'
2020-11-06 15:03:53.2585 Debug Setting 'ColoredConsoleTarget.useDefaultRowHighlightingRules' to 'true'
2020-11-06 15:03:53.2585 Debug Setting 'ColoredConsoleTarget.encoding' to 'utf-8'
2020-11-06 15:03:53.2585 Info Adding target ColoredConsole Target[console]
2020-11-06 15:03:53.2585 Debug Registered target console: NLog.Targets.ColoredConsoleTarget
2020-11-06 15:03:53.2815 Info Configured from an XML element in C:\publish\Test\ConsoleApp1\Application Files\ConsoleApp1_1_0_0_8\NLog.config...
2020-11-06 15:03:53.2915 Debug Unused target checking is started... Rule Count: 1, Target Count: 2
2020-11-06 15:03:53.2915 Debug Unused target checking is completed. Total Rule Count: 1, Total Target Count: 2, Unused Target Count: 0
2020-11-06 15:03:53.3055 Debug --- NLog configuration dump ---
2020-11-06 15:03:53.3055 Debug Targets:
2020-11-06 15:03:53.3055 Debug File Target[logFile]
2020-11-06 15:03:53.3055 Debug ColoredConsole Target[console]
2020-11-06 15:03:53.3225 Debug Rules:
2020-11-06 15:03:53.3225 Debug logNamePattern: (:All) levels: [ Trace Debug Info Warn Error Fatal ] appendTo: [ logFile console ]
2020-11-06 15:03:53.3225 Debug --- End of NLog configuration dump ---
2020-11-06 15:03:53.3425 Info Found 41 configuration items
2020-11-06 15:03:53.3785 Debug Watching path 'C:\publish\Test\ConsoleApp1\Application Files\ConsoleApp1_1_0_0_8' filter 'NLog.config' for changes.
2020-11-06 15:03:53.3875 Info Configuration initialized.
2020-11-06 15:03:53.3875 Info NLog, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=5120e14c03d0593c. File version: <IP_ADDRESS>45.

Could you please try the performance once with only the console target and once only with the file target? Thanks!

Could you please try the performance once with only the console target and once only with the file target? Thanks!

file target:

Could you please try the performance once with only the console target and once only with the file target? Thanks!

only Console:

So in both cases slow, isn't?

So in both cases slow, isn't?

yes

@StevenFlyover Do you have anything in your app.config ?
The delay seems to occur before NLog starts loading the NLog.config

11/6/2020 3:03:22 PM | Program initialization...
2020-11-06 15:03:52.9735 Debug ScanAssembly('NLog, Version=<IP_ADDRESS>,')
2020-11-06 15:03:53.4335 | INFO | ConsoleApp1.P

There is another user who reported an overhead when initializing the NLog InternalLogger #4032
Could you try this instead:
Console.WriteLine($"{DateTime.Now} | Program initialization");
NLog.Common.InternalLogger.LogLevel = LogLevel.Debug;
NLog.Common.InternalLogger.LogToConsole = true;
NLog.Common.InternalLogger.Info("NLog InternalLogger Ready");
ILogger logger = NLog.LogManager.Setup().SetupExtensions(e => e.AutoLoadAssemblies(false)).GetCurrentClassLogger();
logger.Info("NLog Logger Ready");

@StevenFlyover Do you have anything in your app.config ?
The delay seems to occur before NLog starts loading the NLog.config, so probably irrelevant whether using file-target or console-target.

11/6/2020 3:03:22 PM | Program initialization...
2020-11-06 15:03:52.9735 Debug ScanAssembly('NLog, Version=<IP_ADDRESS>,')
2020-11-06 15:03:53.4335 | INFO | ConsoleApp1.P

There is another user who reported an overhead when initializing the NLog InternalLogger #4032
Could you try this instead:
Console.WriteLine($"{DateTime.Now} | Program initialization");
NLog.Common.InternalLogger.LogLevel = LogLevel.Debug;
NLog.Common.InternalLogger.LogToConsole = true;
NLog.Common.InternalLogger.Info("NLog InternalLogger Ready");
ILogger logger = NLog.LogManager.Setup().SetupExtensions(e => e.AutoLoadAssemblies(false)).GetCurrentClassLogger();
logger.Info("NLog Logger Ready");

nothing in app.config

Since you can show this in profiler. Could you enable the filter-check-box for also profiling "Show External Code"?

Show External Code

not found this option.
where to enable it?

There is a filter-icon one can click, that shows this drop-down-menu:

@StevenFlyover Does the mysterious delay also occur when downgrading to NLog.Web 4.9.2 and NLog 4.6.7 ?

Does the mysterious delay also occur when downgrading to NLog.Web 4.9.0 and NLog 4.6.7 ?
it is Console.
and i try 4.7.5 & 4.5.11, both delay.

There is a filter-icon one can click, that shows this drop-down-menu:

Hrmm strange Visual Studio should load automatically from nuget-symbol-servers.
You can manually download the symbol-package here. For NLog ver. 4.7.5:
https://www.nuget.org/api/v2/symbolpackage/NLog/4.7.5
And then rename it to nlog.4.7.5.snupkg.zip and then extract lib\net45\nlog.pdb to your application-build-output-bin-folder.

Curious if the problem is Assembly.GetTypes() can you try this code:
Console.WriteLine($"{DateTime.Now} | Program initialization");
NLog.Common.InternalLogger.LogLevel = LogLevel.Debug;
NLog.Common.InternalLogger.LogToConsole = true;
NLog.Common.InternalLogger.Info("NLog InternalLogger Ready");
var nlogTypes = typeof(NLog.LogFactory).Assembly.GetTypes();
NLog.Common.InternalLogger.Info("NLog AssemblyTypes Ready: {0}", nlogTypes.Length);
NLog.Config.ConfigurationItemFactory.Default = new ConfigurationItemFactory(typeof(NLog.LogFactory).Assembly);
NLog.Common.InternalLogger.Info("NLog AssemblyTypes Loaded");
var logger = NLog.LogManager.GetCurrentClassLogger();
logger.Info("NLog Logger Ready");

Maybe this more clear:

Curious if the problem is Assembly.GetTypes() can you try this code:
Console.WriteLine($"{DateTime.Now} | Program initialization");
NLog.Common.InternalLogger.LogLevel = LogLevel.Debug;
NLog.Common.InternalLogger.LogToConsole = true;
NLog.Common.InternalLogger.Info("NLog InternalLogger Ready");
var nlogTypes = typeof(NLog.LogFactory).Assembly.GetTypes();
NLog.Common.InternalLogger.Info("NLog AssemblyTypes Ready: {0}", nlogTypes.Length);
NLog.Config.ConfigurationItemFactory.Default = new ConfigurationItemFactory(typeof(NLog.LogFactory).Assembly);
NLog.Common.InternalLogger.Info("NLog AssemblyTypes Loaded");
var logger = NLog.LogManager.GetCurrentClassLogger();
logger.Info("NLog Logger Ready");

Then maybe the issue the scanning for Nlog.config, maybe you have a slow network-drive somewhere:
Console.WriteLine($"{DateTime.Now} | Program initialization");
NLog.Common.InternalLogger.LogLevel = LogLevel.Debug;
NLog.Common.InternalLogger.LogToConsole = true;
NLog.Common.InternalLogger.Info("NLog InternalLogger Ready");
var nlogTypes = typeof(NLog.LogFactory).Assembly.GetTypes();
NLog.Common.InternalLogger.Info("NLog AssemblyTypes Ready: {0}", nlogTypes.Length);
NLog.Config.ConfigurationItemFactory.Default = new ConfigurationItemFactory(typeof(NLog.LogFactory).Assembly);
NLog.Common.InternalLogger.Info("NLog AssemblyTypes Loaded");
var nlogPaths = NLog.LogManager.LogFactory.GetCandidateConfigFilePaths().ToList();
NLog.Common.InternalLogger.Info("NLog Path Scan Completed: {0}", nlogPaths.Count);
var nlogConfigFile = System.IO.Path.Combine(AppDomain.CurrentDomain.BaseDirectory, "nlog.config");
var logger = NLog.LogManager.LoadConfiguration(nlogConfigFile).GetCurrentClassLogger();
logger.Info("NLog Logger Ready");

The profier-output only shows the CPU-time, not the 30 sec stall because of IO-timeout.

Maybe the issue is the scanning for Nlog.config, maybe you have a slow network-drive somewhere.
Can you try running this:
Console.WriteLine($"{DateTime.Now} | Program initialization");
NLog.Common.InternalLogger.LogLevel = LogLevel.Debug;
NLog.Common.InternalLogger.LogToConsole = true;
NLog.Common.InternalLogger.Info("NLog InternalLogger Ready");
var nlogTypes = typeof(NLog.LogFactory).Assembly.GetTypes();
NLog.Common.InternalLogger.Info("NLog AssemblyTypes Ready: {0}", nlogTypes.Length);
NLog.Config.ConfigurationItemFactory.Default = new ConfigurationItemFactory(typeof(NLog.LogFactory).Assembly);
NLog.Common.InternalLogger.Info("NLog AssemblyTypes Loaded");
var nlogPaths = NLog.LogManager.LogFactory.GetCandidateConfigFilePaths().ToList();
NLog.Common.InternalLogger.Info("NLog Path Scan Completed: {0}", nlogPaths.Count);
var nlogConfigFile = System.IO.Path.Combine(AppDomain.CurrentDomain.BaseDirectory, "nlog.config");
var logger = NLog.LogManager.LoadConfiguration(nlogConfigFile).GetCurrentClassLogger();
logger.Info("NLog Logger Ready");

The profier-output only shows the CPU-time, not the 30 sec stall because of IO-timeout.

it is testing at my local. and same problem at production environment.

Maybe the issue is the scanning for Nlog.config, maybe you have a slow network-drive somewhere.
Can you try running this:
Console.WriteLine($"{DateTime.Now} | Program initialization");
NLog.Common.InternalLogger.LogLevel = LogLevel.Debug;
NLog.Common.InternalLogger.LogToConsole = true;
NLog.Common.InternalLogger.Info("NLog InternalLogger Ready");
var nlogTypes = typeof(NLog.LogFactory).Assembly.GetTypes();
NLog.Common.InternalLogger.Info("NLog AssemblyTypes Ready: {0}", nlogTypes.Length);
NLog.Config.ConfigurationItemFactory.Default = new ConfigurationItemFactory(typeof(NLog.LogFactory).Assembly);
NLog.Common.InternalLogger.Info("NLog AssemblyTypes Loaded");
var nlogPaths = NLog.LogManager.LogFactory.GetCandidateConfigFilePaths().ToList();
NLog.Common.InternalLogger.Info("NLog Path Scan Completed: {0}", nlogPaths.Count);
var nlogConfigFile = System.IO.Path.Combine(AppDomain.CurrentDomain.BaseDirectory, "nlog.config");
var logger = NLog.LogManager.LoadConfiguration(nlogConfigFile).GetCurrentClassLogger();
logger.Info("NLog Logger Ready");

The profier-output only shows the CPU-time, not the 30 sec stall because of IO-timeout.

it working!!!no delay!!!
Thanks, snakefoot.
Thanks, all.

I guess you can reduce the boostrap to this:
var nlogConfigFile = System.IO.Path.Combine(AppDomain.CurrentDomain.BaseDirectory, "nlog.config");
var logger = NLog.LogManager.Setup().SetupExtensions(e => e.AutoLoadAssemblies(false)).LoadConfigurationFromFile(nlogConfigFile).GetCurrentClassLogger();

But would really like to find the cause of the delay. Can you test this also:
Console.WriteLine($"{DateTime.Now} | Program initialization");
NLog.Common.InternalLogger.LogLevel = LogLevel.Debug;
NLog.Common.InternalLogger.LogToConsole = true;
NLog.Common.InternalLogger.Info("NLog InternalLogger Ready");
var nlogTypes = typeof(NLog.LogFactory).Assembly.GetTypes();
NLog.Common.InternalLogger.Info("NLog AssemblyTypes Ready: {0}", nlogTypes.Length);
NLog.Config.ConfigurationItemFactory.Default = new ConfigurationItemFactory(typeof(NLog.LogFactory).Assembly);
NLog.Common.InternalLogger.Info("NLog AssemblyTypes Loaded");
foreach (var configPath in NLog.LogManager.LogFactory.GetCandidateConfigFilePaths())
{
      var configFilePath = System.IO.Path.Combine(configPath, "Nlog.config");
      var configFileExists = System.IO.File.Exists(configFilePath);
      NLog.Common.InternalLogger.Info("{0} - Config file found: {1}", configFilePath, configFileExists);
}
var nlogConfigFile = System.IO.Path.Combine(AppDomain.CurrentDomain.BaseDirectory, "nlog.config");
var logger = NLog.LogManager.LoadConfiguration(nlogConfigFile).GetCurrentClassLogger();
logger.Info("NLog Logger Ready");

foreach (var configPath in NLog.LogManager.LogFactory.GetCandidateConfigFilePaths())
{
      var configFilePath = System.IO.Path.Combine(configPath, "Nlog.config");
      var configFileExists = System.IO.File.Exists(configFilePath);
      NLog.Common.InternalLogger.Info("{0} - Config file found: {1}", configFilePath, configFileExists);
}

Very strange search order：
11/10/2020 6:15:43 PM | Program initialization...
2020-11-10 18:15:43.7702 Info NLog InternalLogger Ready
2020-11-10 18:15:43.7822 Info xxxxx\NLog.config\Nlog.config - Config file found: False
2020-11-10 18:15:43.7822 Info xxxxx\ConsoleApp1.exe.nlog\Nlog.config - Config file found: False
2020-11-10 18:15:43.7822 Info xxxxx\NLog.dll.nlog\Nlog.config - Config file found: False
2020-11-10 18:15:43.7822 Info Configuring from an XML element in xxxxx\nlog.config...

My bad. I don't have the NLog-code completely memorized. This is probably the right logic:
Console.WriteLine($"{DateTime.Now} | Program initialization");
NLog.Common.InternalLogger.LogLevel = LogLevel.Debug;
NLog.Common.InternalLogger.LogToConsole = true;
NLog.Common.InternalLogger.Info("NLog InternalLogger Ready");
var nlogTypes = typeof(NLog.LogFactory).Assembly.GetTypes();
NLog.Common.InternalLogger.Info("NLog AssemblyTypes Ready: {0}", nlogTypes.Length);
NLog.Config.ConfigurationItemFactory.Default = new ConfigurationItemFactory(typeof(NLog.LogFactory).Assembly);
NLog.Common.InternalLogger.Info("NLog AssemblyTypes Loaded");
foreach (var configPath in NLog.LogManager.LogFactory.GetCandidateConfigFilePaths())
{
      var configFileExists = System.IO.File.Exists(configPath);
      NLog.Common.InternalLogger.Info("{0} - Config file found: {1}", configPath, configFileExists);
}
var nlogConfigFile = System.IO.Path.Combine(AppDomain.CurrentDomain.BaseDirectory, "nlog.config");
var logger = NLog.LogManager.LoadConfiguration(nlogConfigFile).GetCurrentClassLogger();
logger.Info("NLog Logger Ready");

      var configFileExists = System.IO.File.Exists(configPath);
      NLog.Common.InternalLogger.Info("{0} - Config file found: {1}", configPath, configFileExists);

yes, no delay!
seams search the correct file first time. why cost so long time? @@
11/10/2020 6:38:04 PM | Program initialization...
2020-11-10 18:38:04.1396 Info NLog InternalLogger Ready
2020-11-10 18:38:04.1536 Info xxxxx\NLog.config - Config file found: True
2020-11-10 18:38:04.1536 Info xxxxx\ConsoleApp1.exe.nlog - Config file found: False
2020-11-10 18:38:04.1536 Info xxxxx\NLog.dll.nlog - Config file found: False
2020-11-10 18:38:04.1686 Info Configuring from an XML element in xxxxx\nlog.config...
2020-11-10 18:38:04.2516 Info Auto loading assembly file: xxxxx\NLog.Extensions.Logging.dll
2020-11-10 18:38:04.2576 Info Loading assembly file: xxxxx\NLog.Extensions.Logging.dll

why cost so long time?

If I had the answer, then this issue would have less comments. But I have no clue what causes the 30 sec delay. The timestamps you have just shown does not contain any 30 secs delay.
If you are able to track down what part of the initialization is causing this delay on your machine (it is not cpu-time), then please tell.


Allow specifying the sizes of nodes

Today, AFAIK the only way to control the distance between nodes is through vertex spacing. This is a fixed amount of spacing between each node. Unfortunately this doesn't allow nodes to account for their size.
For example, I want each node to hold a string which can sometimes be fairly long. This means I either need to allow nodes to overlap which looks really bad, or I need to use a comically large vertex spacing, which makes parts of the graph that are small harder to read.
Ideally the crate would allow me to give it the size of each node and it would use that to decide where to put the nodes so they don't overlap.

This is what I have at the moment. I think I can fix Beth & Summer (i.e. center nodes across ranks), but not sure about Rick not being in between Jerry & Beth.

This is what I have at the moment. I think I can fix Beth & Summer (i.e. center nodes across ranks), but not sure about Rick not being in between Jerry & Beth.

I'm not sure what your settings are like, but this looks to me like we're only pushing nodes left by the vertex spacing, but pushing the next node right by vertex spacing +width. That might be why Jerry is moving only a bit left and Morty isn't moving at all (I would say Morty should be moving a little bit left to make space for Summer so it is more centered).


Usage limit (30 minutes)

ABUS One-Click AI (Free trial)
Usage limit (30 minutes)

Does this program have any usage restrictions?
If there are any restrictions, please tell us in the description section because why should we install a program with these restrictions?

Hello. I agree with your point. I have revised the README to avoid any misunderstandings regarding the free trial. If you have any additional comments, please feel free to reach out anytime. Thank you.


fix 'NoneType' object has no attribute 'utcoffset'

(Describe the goal of this PR. Mention any related Issue numbers)
Category (place an x in each of the [ ])

[ ] slack_bolt.App and/or its core components
[ ] slack_bolt.async_app.AsyncApp and/or its core components
[ ] Document pages under /docs
[ ] Adapters in slack_bolt.adapter
[ x] Others

Requirements (place an x in each [ ])
Please read the Contributing guidelines and Code of Conduct before creating this issue or pull request. By submitting, you are agreeing to those rules.

[ x] I've read and understood the Contributing Guidelines and have done my best effort to follow them.
[x ] I've read and agree to the Code of Conduct.
[ ] I've run ./scripts/install_all_and_run_tests.sh after making the changes.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Hi @paulfab, thanks for taking the time to fix this error! Would you mind signing the CLA (please check the above bot message)? Without having it, we are unable to merge your changes in this repository.

@paulfab Thanks for updating this pull request. Would you mind signing the CLA (please check the above bot message)? Without having it, we are unable to merge your changes in this repository.

Hey @seratch you are so fast I didnt have the time to comment ^^. Thanks for reviewing the PR, I'm quite reluctant to sign the CLA. You can take ownership of my modest changes and merge it ?

@paulfab Okay, in the case, we can come up with my own pull request instead. Thanks a lot for taking the time to report this!

Let me close this pull request in favor of https://github.com/slackapi/bolt-python/pull/523


Query constraints using ordered dimensions

circumvents the need for class matching with constraints

Coverage decreased (-0.8%) to 45.728% when pulling 2ba4a0875d41e6c68903bf1fbc5e44bfaa662f5b on rfecher:ordered-query into ecea4c417785a49947da4f6b239a39c3fa51bbe3 on locationtech:master.


Allow type checking dask

dask has added py.typed files so now the ignores shouldn't be needed anymore:
https://github.com/dask/dask/pull/8854
https://github.com/dask/distributed/pull/5328

Is numpy not also typed in the meantime?

The failing doctest is unrelated, or?

Yeah it must be unrelated, I can't see how the doctest could be related to this.

I think pandas still requires a stub package. Might still take some time :)


Create Hello_world_New.html

A simple HTML program to say Hello world.

Please merge my pull request

please add hacktober-accepted label on my pull request.


[BUG] Value property of Input component still not actually bindable

Quick Glance

The value property of Input is bindable but it doesn't react to changes

Description
I just upgraded to<EMAIL_ADDRESS>and #12 is still present. I was not able to reopen the issue, so I've created a new one.
<script>
  import { Input } from 'kampsy-ui';

  let value = $state('initial value');
</script>

<Input bind:value />

<p>
  You typed {value}.
</p>

Input correctly applies initial value
Typing text doesn't update the paragraph text

Proposition
Change {value} to bind:value in src/lib/input/input.svelte.

Oopsie I will fix this minor issue and let you focus on the GitHub action

Fixed!
https://github.com/user-attachments/assets/8424f33a-7a44-4aa0-bfdf-cb3adb9a8e87


Apparently I get an error where the MTR modpack won't update for me

Crash Report

This is because the resource pack server is down. It is unrelated to the Minecraft Mod Updater,

Ok thanks for letting me know
On Wed, Dec 7, 2022 at 9:00 PM Jonathan Ho @.***> wrote:

This is because the resource pack server is down. It is unrelated to the
Minecraft Mod Updater,
—
Reply to this email directly, view it on GitHub
https://github.com/jonafanho/Minecraft-Mod-Updater/issues/13#issuecomment-1341866412,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQ5PKZULZMFNJVK5RSZZVCDWME6LVANCNFSM6AAAAAASXQOBQI
.
You are receiving this because you authored the thread.Message ID:
@.***>


Add Managed Apps Usage dashboard

Towards https://github.com/giantswarm/roadmap/issues/322
This PR

Adds Managed Apps Usage dashboard.

Checklist

[x] Update changelog in CHANGELOG.md in an end-user friendly language.

Tested on ghost

Can you add the analytics panel as well ?

@QuentinBisson My bad I thought I'd added it. 😅
It's there now.


A syntax error in a test can cause a segfault

On some simulators a syntax error of the form
@cocotb.test(expect_error=True)
def typosyntax_error():
yield Timer(100)a
May result in a segfault as the sim will end up with exit(1) called from inside the initial callback. Some sims do not take kindly to this.
Safer is to print the python exception and return. We will not have scheduled any callbacks so the sim will end anyway and in a more graceful way

Now we have a better regression layout this test does not cause all future ones to fail.


Python: Add a README file to the AI connector folder that documents all the available AI services

Would also be good to update this on the learn site as I know it's stale. :)


Uncaught TypeError: Cannot read property 'hot' of undefined

I have hot loading setup and partially working with React Hot Loader 3.
Reloading components works fine. However, whenever I reload a Redux reducer or action I am receiving the following error:
Uncaught TypeError: Cannot read property 'hot' of undefined

  getAffectedStuff @ client.js:351
  hotApply @ client.js:386
  (anonymous function) @ only-dev-server.js:32
  hotUpdateDownloaded @ client.js:312
  hotAddUpdateChunk @ client.js:284
  webpackHotUpdateCallback @ client.js:5
  (anonymous function) @ 0.4221176….hot-update.js:1

Relevant parts of code here:
configureStore({ url }).then( store => {
  render(
    <AppContainer component={ Root } props={{ store }} />,
    document.querySelector( '.app' )
  );

  if ( __DEVELOPMENT__ && module.hot ) {
    module.hot.accept([ './common/components/Root', './common/store/configureStore' ], () => {
      render(
        <AppContainer
          component={ require( './common/components/Root' ).default }
          props={{ store }}
        />,
        document.querySelector( '.app' )
      );
    });
  }
}).catch( console.error.bind( console ));

And here:
if ( __DEVELOPMENT__ && module.hot ) {
  module.hot.accept( '../reducers', () => {
    store.replaceReducer( require( '../reducers' ).default );
  });
}

This is the line where Webpack crashes:

Have you had a change to give Webpack 2 a try? It might be fixed there, but I haven’t checked.

I'll try and see if I can work out how to upgrade now

It builds fine with Webpack 2 without any change in config.
HRM isn't working with it at all though. It claims to be, and doesn't error, but I'm getting no actual changes. I think I'll wait on Webpack 2 until there's some more documentation around it.

Just wanted to chime in that I have been observing this same issue for about a year now. Webpack 1. I have yet to discover a pattern. The bad thing is that after this has occurred, HMR seems no longer functional so we have to restart the app.
It would be great if there at least would be a guard added so that HMR doesn't crash.

This might have been fixed since there were a few hot reloading changes around June or so.

Could we maybe add some diagnostics code? Because upgrading to Webpack 2 is a big time investment and at the moment still very risky.
I understand that it will be very difficult to fix from the current info, but the message clearly indicates that the HMR runtime is in a state it should never be in. The module.parents array apparently contains an ID of a module that is no longer found in installedModules. Might this happen when we remove an import / require statement?
Maybe we can just test whether parent is undefined and if it is, log some debug info (so next time someone encounters it they'll have more info for us) and continue to the next loop iteration. That seems like a safe change to make that may help alleviate and finally fix this issue.

I'm seeing this issue on webpack 2, as well

I think I can replicate this. Consider the same case @colinmeinke  where hot reloading the app works but fails to replaceReducer properly.
Assuming
let ReplacebleEpicMiddleware = createEpicMiddleware(RootEpic);

export const store = () => {
    const composeEnhancers = window.__REDUX_DEVTOOLS_EXTENSION_COMPOSE__ || compose;
    let store = FirebaseStoreCreator(allReducers, {},
        composeEnhancers(
            applyMiddleware(ReplacebleEpicMiddleware)
        ));

    if (module.hot) {
        module.hot.accept(['./reducers.tsx', "./epics.tsx"], () => {
            const nextRootEpic = require('./epics.tsx').RootEpic;
            const nextRootReducer = require('./reducers.tsx').allReducers;
            store.replaceReducer(nextRootReducer);
            ReplacebleEpicMiddleware.replaceEpic(nextRootEpic);
        });
    }

    return store
};

Where reducers.tsx and epics.tsx should only contain a single reducer/epic like so, and is not HMRealoadable. And the "property 'hot' of undefined" error shows up here , if you happen to put the actual reducers/epics you are trying to hot-reload in any of those files respectively. My solution was to simply create an app folder and place my reducers in there. Maybe there is a better way to handle this IDK.
import {pingEpic} from "./app/app.epic";
export const RootEpic = combineEpics(
    pingEpic,
    ....
);

import {reducer} from "./app/reducers";
export const allReducers = combineReducers({
    firebase: firebaseStateReducer,
    app: reducer,
    ...
});

uterReducer({ isUpdating, name });

I'm getting this running the webpack dev server using the nodejs api. weird

I am encountering the same sporadically when hot reloading my server.
I think this may be the culprit: https://github.com/webpack/webpack/blob/028c51301733836abbedc88be7483af2623f5943/lib/HotModuleReplacement.runtime.js#L502
in all the other places module is guarded against being undefined but here apparently not?

Having exactly same issue, which kills my SCSS hot module replacement. Happens each time I'm trying to apply new SCSS changes.

I am using webpack 3 and still having the same error when running webpack dev server. Any update on this?
cheers,
Khoa

manifest.js:590 Uncaught TypeError: Cannot read property 'hot' of undefined
    at hotApply (manifest.js:590)
    at hotUpdateDownloaded (manifest.js:314)
    at hotAddUpdateChunk (manifest.js:294)
    at webpackHotUpdateCallback (manifest.js:37)
    at 0.a0cbf6c….hot-update.js:1

I‘m using webpack3 + vue-loader through webpack nodejs api.
when I modify the template tag in the .vue file, hmr worked fine.
moduleId ./App.vue was in the installedModules array
but if I modify the code in the script tag, the error above was thrown,
and moduleId ./App.vue was gone.
In my dev.config.js file, I added hmr: ['webpack/hot/dev-server', 'webpack-dev-server/client?http://localhost:8080'] into the entry field, and new webpack.HotModuleReplacementPlugin() into the plugins array, also, hot: true was in the webpackDevServer's second arguments as well
I tried CLI to run webpack-dev-server with --hot --inline, both template tag and script tag work fine.

Spiked (fixed) issue by wrapping // call accept handlers code (L497 - L532) into try/catch block in file ./node_modules/webpack/lib/HotModuleReplacement.runtime.js

@Kamilius You fixed it? Maybe try a PR?
@sokra Would a PR for this make sense? What do you think? This issue has been in Webpack since v1. Maybe it can't hurt to try it?

I've been having the same issue (version 2.6.1). I'm using Vue with vue-loader and it happens only on certain components when editing the contents of the script tag.
Don't know if this is a vue-loader or a general webpack issue.
The error comes from HotModuleReplacement.runtime.js line 500, because installedModules[moduleId] doesn't exist.

I just experienced this in the browser, I added a breakdown of the situation at https://github.com/webpack/webpack/pull/5498#issuecomment-321741586

Thanks @Kamilius and @sokra for getting this fixed! Great work!!

I am happy to report that so far I have not experienced this problem any
more, Webpack is being super stable :-D
On Sat, Aug 19, 2017 at 6:15 PM Stijn de Witt<EMAIL_ADDRESS>wrote:

Thanks @Kamilius https://github.com/kamilius and @sokra
https://github.com/sokra for getting this fixed! Great work!!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/webpack/webpack/issues/2387#issuecomment-323532391,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AADWljYBRF4x9vPo4xtu3IS9QRqbdSfOks5sZwoUgaJpZM4IOfEg
.


Restarting at offset

I have written a couple of programs in Go to read data from Kafka topics using the sarama library. Just modified one of those programs to use your cluster library and stream the data instead of managing the partitions individually.
However, if my program stops (or dies, as it is doing in testing), when it restarts, it starts at the current offset of the kafka topic, not where it left off when it died. I don't want to go back to the beginning and reprocess the entire topic, but starting at the end leaves gaps.
In my old program, I periodically wrote the offsets for each partition into a file and set those values on a restart - this forced a bit of reprocessing, but not too much. I only see options to start at the newest or oldest offset in your library - am I missing an option, or is there another way to pick up roughly where I left off when my program was terminated?
Please note that I'm relatively new to Go programming, so I may well have missed something in going through your code...
thanks,
nbc

Are you sure you're calling https://godoc.org/github.com/bsm/sarama-cluster#Consumer.MarkOffset in your program?

Actually, I'm sure that I'm NOT calling that routine :) But that may be what I'm looking for - let me go through that part of the documentation and see about modifying my code to do that. That may solve my problem - thanks very much!
nbc

And that did solve my problem - thanks very much for the help!
nbc

Thanks @dolzenko


How would I start multiple workers and connect them to a master?

Hello,
How would I start multiple workers and connect them to a single master?
I've tried adding multiple worker start lines to the start.sh, but it does not seem to work
python /opt/kaldi-gstreamer-server/kaldigstserver/worker.py -c $YAML -u ws://$MASTER:$PORT/worker/ws/speech 2>> /opt/worker.log &
Thank You

Hi,
you may use the script "start.sh" multiple times to connect many workers to a single master.
For example, imagine you have a master server with ip address <IP_ADDRESS>, port 8080.
For connecting 2 workers to this master, you should do

start.sh -y  -m <IP_ADDRESS> -p 8080
start.sh -y  -m <IP_ADDRESS> -p 8080
I always used one worker per machine and I know it works. So, in this example I mentioned, you should use 2 different machines.


Example of using your own custom types (classes) in your own pc.ScriptTypes

This repo has been a great help, but I'm really struggling to get a good class hierarchy going where I can unit test my own class definitions, that I then use within pc.ScriptTypes.
The file that you define a script in, like:
class Foo extends pc.ScriptType
requires to be a file that is not a module, because otherwise it complains:
'pc' refers to a UMD global, but the current file is a module. Consider adding an import instead.
This makes it impossible to import modules into this file, which stumps me, because I don't know how to use classes in other files without the import statement.
An example within this repo would be of great use! Any other pointers appreciated!

This repo is meant to be for use with the Editor which doesn't use modules. So all class definitions are in global scope, there's no need to import them. You can see ES6 classes used in this Editor project: https://playcanvas.com/project/950571/overview/fps-pit
If you want an example of using the Engine without the Editor and with modules, the Model Viewer repo could help here; https://github.com/playcanvas/model-viewer

I got it working in playcanvas, like you said without modules, thanks for the clarification. Now I'm running into issues where the unit tests cannot find these global class definitions, but that's up to me to figure out.


Hide ArrowArray/Schema from public geoarrow API

Not entirely sure this is the best solution, but with those changes I manage to get working bindings in spherely using the new s2geography::geoarrow:Reader

Resolved by https://github.com/paleolimbot/s2geography/pull/27