Still can't get zeek-kafka to work

Summary of the issue
zeek-kafka doesn't work, either via zkg or manual install
Expected behavior
...
Steps to reproduce

zkg install:
zkg install seiso/zeek-kafka --version main
error: invalid package "seiso/zeek-kafka": package name not found in sources and also not a usable git URL (invalid or inaccessible, use -vvv for details)

manual install:
./configure --with-librdkafka=$LIBRDKAFKA_ROOT
make
sudo make install
zeek -N Seiso::Kafka
Seiso::Kafka - Writes logs to Kafka (dynamic, version 0.3.0)
zeek -r file.pcap /usr/local/zeek/share/zeek/site/local.zeek
fatal error in /usr/local/zeek/share/zeek/site/kafka.zeek, line 2: can't find packages/zeek-kafka/Seiso/Kafka
looking in /usr/local/zeek/share/zeek/site/packages, there is nothing there

Where applicable, consider providing a patch that uses the end to end testing environment.
Logs, errors, etc.
...
Your environment

Version of Zeek
Version or commit hash of the zeek-kafka package
Operating System and version

zeek 4.0.0-rc2
version 0.3
Ubuntu 20.04

@emnahum can you give it another shot now with zkg?  I got it added to the zeek package index

Running unit tests for "zeek/seisollc/zeek-kafka"
error: "zeek/seisollc/zeek-kafka" tests failed, inspect contents of /home/nahum/.zkg/testing/zeek-kafka for details, especially any "zkg.test_command.{stderr,stdout}" files within /home/nahum/.zkg/testing/zeek-kafka/clones/zeek-kafka
Proceed to install anyway? [N/y]n
more zkg.test_command.stderr:
afka.l2s-l2e-no-overlap ... failed
% 'bro ../../../scripts/Apache/Kafka/ /home/nahum/.zkg/testing/zeek-kafka/clones/zeek-kafka/tests/.tmp/kafka.l2s-l2e-no-overlap/l2s-l2e-no-
overlap.bro > output' failed unexpectedly (exit code 1)
% cat .stderr
fatal error in /usr/local/zeek/share/zeek/base/init-bare.zeek, line 1: cannot load plugin library /usr/local/zeek/lib/zeek/plugins/SEISO_KA
FKA//lib/SEISO-KAFKA.linux-x86_64.so: /usr/local/zeek/lib/zeek/plugins/SEISO_KAFKA//lib/SEISO-KAFKA.linux-x86_64.so: undefined symbol: _ZTIN4
zeek7logging13WriterBackendE
kafka.l2s-set-l2e-set ... failed
% 'bro ../../../scripts/Apache/Kafka/ /home/nahum/.zkg/testing/zeek-kafka/clones/zeek-kafka/tests/.tmp/kafka.l2s-set-l2e-set/l2s-set-l2e-se
t.bro > output' failed unexpectedly (exit code 1)
% cat .stderr
fatal error in /usr/local/zeek/share/zeek/base/init-bare.zeek, line 1: cannot load plugin library /usr/local/zeek/lib/zeek/plugins/SEISO_KA
FKA//lib/SEISO-KAFKA.linux-x86_64.so: /usr/local/zeek/lib/zeek/plugins/SEISO_KAFKA//lib/SEISO-KAFKA.linux-x86_64.so: undefined symbol: _ZTIN4
zeek7logging13WriterBackendE
kafka.l2s-set-l2e-unset ... failed
% 'bro ../../../scripts/Apache/Kafka/ /home/nahum/.zkg/testing/zeek-kafka/clones/zeek-kafka/tests/.tmp/kafka.l2s-set-l2e-unset/l2s-set-l2e-
unset.bro > output' failed unexpectedly (exit code 1)
% cat .stderr
fatal error in /usr/local/zeek/share/zeek/base/init-bare.zeek, line 1: cannot load plugin library /usr/local/zeek/lib/zeek/plugins/SEISO_KA
FKA//lib/SEISO-KAFKA.linux-x86_64.so: /usr/local/zeek/lib/zeek/plugins/SEISO_KAFKA//lib/SEISO-KAFKA.linux-x86_64.so: undefined symbol: _ZTIN4
zeek7logging13WriterBackendE
kafka.l2s-unset-l2e-set ... failed
% 'bro ../../../scripts/Apache/Kafka/ /home/nahum/.zkg/testing/zeek-kafka/clones/zeek-kafka/tests/.tmp/kafka.l2s-unset-l2e-set/l2s-unset-l2
e-set.bro > output' failed unexpectedly (exit code 1)
% cat .stderr
fatal error in /usr/local/zeek/share/zeek/base/init-bare.zeek, line 1: cannot load plugin library /usr/local/zeek/lib/zeek/plugins/SEISO_KA
FKA//lib/SEISO-KAFKA.linux-x86_64.so: /usr/local/zeek/lib/zeek/plugins/SEISO_KAFKA//lib/SEISO-KAFKA.linux-x86_64.so: undefined symbol: _ZTIN4
zeek7logging13WriterBackendE
kafka.l2s-unset-l2e-unset ... failed
% 'bro ../../../scripts/Apache/Kafka/ /home/nahum/.zkg/testing/zeek-kafka/clones/zeek-kafka/tests/.tmp/kafka.l2s-unset-l2e-unset/l2s-unset-
l2e-unset.bro > output' failed unexpectedly (exit code 1)
% cat .stderr
fatal error in /usr/local/zeek/share/zeek/base/init-bare.zeek, line 1: cannot load plugin library /usr/local/zeek/lib/zeek/plugins/SEISO_KA
FKA//lib/SEISO-KAFKA.linux-x86_64.so: /usr/local/zeek/lib/zeek/plugins/SEISO_KAFKA//lib/SEISO-KAFKA.linux-x86_64.so: undefined symbol: _ZTIN4
zeek7logging13WriterBackendE
kafka.resolved-topic-config ... failed
% 'bro -r ../../../tests/pcaps/exercise-traffic.pcap ../../../scripts/Apache/Kafka/ /home/nahum/.zkg/testing/zeek-kafka/clones/zeek-kafka/t
ests/.tmp/kafka.resolved-topic-config/resolved-topic-config.bro > output' failed unexpectedly (exit code 1)
% cat .stderr
fatal error in /usr/local/zeek/share/zeek/base/init-bare.zeek, line 1: cannot load plugin library /usr/local/zeek/lib/zeek/plugins/SEISO_KA
FKA//lib/SEISO-KAFKA.linux-x86_64.so: /usr/local/zeek/lib/zeek/plugins/SEISO_KAFKA//lib/SEISO-KAFKA.linux-x86_64.so: undefined symbol: _ZTIN4
zeek7logging13WriterBackendE
kafka.resolved-topic-default ... failed
% 'bro -r ../../../tests/pcaps/exercise-traffic.pcap ../../../scripts/Apache/Kafka/ /home/nahum/.zkg/testing/zeek-kafka/clones/zeek-kafka/t
ests/.tmp/kafka.resolved-topic-default/resolved-topic-default.bro > output' failed unexpectedly (exit code 1)
% cat .stderr
fatal error in /usr/local/zeek/share/zeek/base/init-bare.zeek, line 1: cannot load plugin library /usr/local/zeek/lib/zeek/plugins/SEISO_KA
FKA//lib/SEISO-KAFKA.linux-x86_64.so: /usr/local/zeek/lib/zeek/plugins/SEISO_KAFKA//lib/SEISO-KAFKA.linux-x86_64.so: undefined symbol: _ZTIN4
zeek7logging13WriterBackendE
kafka.resolved-topic-override-and-config ... failed
% 'bro -r ../../../tests/pcaps/exercise-traffic.pcap ../../../scripts/Apache/Kafka/ /home/nahum/.zkg/testing/zeek-kafka/clones/zeek-kafka/t
ests/.tmp/kafka.resolved-topic-override-and-config/resolved-topic-override-and-config.bro > output' failed unexpectedly (exit code 1)
% cat .stderr
fatal error in /usr/local/zeek/share/zeek/base/init-bare.zeek, line 1: cannot load plugin library /usr/local/zeek/lib/zeek/plugins/SEISO_KA
FKA//lib/SEISO-KAFKA.linux-x86_64.so: /usr/local/zeek/lib/zeek/plugins/SEISO_KAFKA//lib/SEISO-KAFKA.linux-x86_64.so: undefined symbol: _ZTIN4
zeek7logging13WriterBackendE
kafka.resolved-topic-override-only ... failed
% 'bro -r ../../../tests/pcaps/exercise-traffic.pcap ../../../scripts/Apache/Kafka/ /home/nahum/.zkg/testing/zeek-kafka/clones/zeek-kafka/t
ests/.tmp/kafka.resolved-topic-override-only/resolved-topic-override-only.bro > output' failed unexpectedly (exit code 1)
% cat .stderr
fatal error in /usr/local/zeek/share/zeek/base/init-bare.zeek, line 1: cannot load plugin library /usr/local/zeek/lib/zeek/plugins/SEISO_KA
FKA//lib/SEISO-KAFKA.linux-x86_64.so: /usr/local/zeek/lib/zeek/plugins/SEISO_KAFKA//lib/SEISO-KAFKA.linux-x86_64.so: undefined symbol: _ZTIN4
zeek7logging13WriterBackendE
kafka.send-all-active-logs-l2e-set ... failed
% 'bro ../../../scripts/Apache/Kafka/ /home/nahum/.zkg/testing/zeek-kafka/clones/zeek-kafka/tests/.tmp/kafka.send-all-active-logs-l2e-set/s
end-all-active-logs-l2e-set.bro > output' failed unexpectedly (exit code 1)
% cat .stderr
fatal error in /usr/local/zeek/share/zeek/base/init-bare.zeek, line 1: cannot load plugin library /usr/local/zeek/lib/zeek/plugins/SEISO_KA
FKA//lib/SEISO-KAFKA.linux-x86_64.so: /usr/local/zeek/lib/zeek/plugins/SEISO_KAFKA//lib/SEISO-KAFKA.linux-x86_64.so: undefined symbol: _ZTIN4
zeek7logging13WriterBackendE
% 'bro ../../../scripts/Apache/Kafka/ /home/nahum/.zkg/testing/zeek-kafka/clones/zeek-kafka/tests/.tmp/kafka.send-all-active-logs-l2e-unset
/send-all-active-logs-l2e-unset.bro > output' failed unexpectedly (exit code 1)
% cat .stderr
fatal error in /usr/local/zeek/share/zeek/base/init-bare.zeek, line 1: cannot load plugin library /usr/local/zeek/lib/zeek/plugins/SEISO_KA
FKA//lib/SEISO-KAFKA.linux-x86_64.so: /usr/local/zeek/lib/zeek/plugins/SEISO_KAFKA//lib/SEISO-KAFKA.linux-x86_64.so: undefined symbol: _ZTIN4
zeek7logging13WriterBackendE
kafka.send-all-active-logs-l2s-set-l2e-set ... failed
% 'bro ../../../scripts/Apache/Kafka/ /home/nahum/.zkg/testing/zeek-kafka/clones/zeek-kafka/tests/.tmp/kafka.send-all-active-logs-l2s-set-l
2e-set/send-all-active-logs-l2s-set-l2e-set.bro > output' failed unexpectedly (exit code 1)
% cat .stderr
fatal error in /usr/local/zeek/share/zeek/base/init-bare.zeek, line 1: cannot load plugin library /usr/local/zeek/lib/zeek/plugins/SEISO_KA
FKA//lib/SEISO-KAFKA.linux-x86_64.so: /usr/local/zeek/lib/zeek/plugins/SEISO_KAFKA//lib/SEISO-KAFKA.linux-x86_64.so: undefined symbol: _ZTIN4
zeek7logging13WriterBackendE
kafka.send-all-active-logs-l2s-set-l2e-unset ... failed
% 'bro ../../../scripts/Apache/Kafka/ /home/nahum/.zkg/testing/zeek-kafka/clones/zeek-kafka/tests/.tmp/kafka.send-all-active-logs-l2s-set-l
2e-unset/send-all-active-logs-l2s-set-l2e-unset.bro > output' failed unexpectedly (exit code 1)
% cat .stderr
fatal error in /usr/local/zeek/share/zeek/base/init-bare.zeek, line 1: cannot load plugin library /usr/local/zeek/lib/zeek/plugins/SEISO_KA
FKA//lib/SEISO-KAFKA.linux-x86_64.so: /usr/local/zeek/lib/zeek/plugins/SEISO_KAFKA//lib/SEISO-KAFKA.linux-x86_64.so: undefined symbol: _ZTIN4
zeek7logging13WriterBackendE
kafka.show-plugin ... failed
% 'btest-diff output' failed unexpectedly (exit code 1)
% cat .diag
== File ===============================
== Diff ===============================
--- /tmp/test-diff.26368.output.baseline.tmp	2021-03-03 02:49:32.981669049 +0000
+++ /tmp/test-diff.26368.output.tmp	2021-03-03 02:49:32.981669049 +0000
@@ -1,11 +0,0 @@
-Apache::Kafka - Writes logs to Kafka (dynamic)

[Writer] KafkaWriter (Log::WRITER_KAFKAWRITER)
[Constant] Kafka::kafka_conf
[Constant] Kafka::topic_name
[Constant] Kafka::max_wait_on_shutdown
[Constant] Kafka::tag_json
[Constant] Kafka::json_timestamps
[Constant] Kafka::debug
[Constant] Kafka::mock
[Event] kafka_topic_resolved_event

=======================================
% cat .stderr
fatal error in /usr/local/zeek/share/zeek/base/init-bare.zeek, line 1: cannot load plugin library /usr/local/zeek/lib/zeek/plugins/SEISO_KA
FKA//lib/SEISO-KAFKA.linux-x86_64.so: /usr/local/zeek/lib/zeek/plugins/SEISO_KAFKA//lib/SEISO-KAFKA.linux-x86_64.so: undefined symbol: _ZTIN4
zeek7logging13WriterBackendE
14 of 14 tests failed
(this time with zeek 4.0.0.)

@emnahum I'm not sure why your environment is referring to Apache::Kafka or bro ../../../scripts/Apache/Kafka/ as that is not referenced in zeek-kafka.  Perhaps something that wasn't cleaned up from a prior metron-bro-plugin-kafka install?  You can see expected build logs for the plugin here.
I'm running a test using zkg install zeek/seisollc/zeek-kafka (as opposed to pointing it to a local file path, which is what our e2e tests use and is currently working) to see if I can reproduce what you're seeing.

I was able to reproduce a very similar error message

@JonZeolla I'm trying again using a clean build machine (nothing on it); I'll let you know if it solves anything.

Wonderful, thank you.  I'm working on the tests to support Ubuntu as well as to exercise whatever issue we end up finding here.

It didn't work again, although the error is different:
137 biloxi1:~/.zkg/testing/zeek-kafka/clones/zeek-kafka$ more zkg.test_command.stderr
kafka.l2s-l2e-no-overlap ... failed
% 'zeek ../../../scripts/Seiso/Kafka/ /home/nahum/.zkg/testing/zeek-kafka/clones/zeek-kafka/tests/.tmp/kafka.l2s-l2e-no-overlap/l2s-l2e-no-
overlap.zeek > output' failed unexpectedly (exit code 1)
% cat .stderr
error in /usr/local/zeek/share/zeek/base/init-bare.zeek, line 1: cannot load plugin library /home/nahum/.zkg/testing/zeek-kafka/clones/zeek
-kafka/build//lib/SEISO-KAFKA.linux-x86_64.so: /usr/local/lib/librdkafka++.so.1: undefined symbol: rd_kafka_error_string
fatal error in /usr/local/zeek/share/zeek/base/init-bare.zeek, line 1: aborting after plugin errors
kafka.l2s-set-l2e-set ... failed
% 'zeek ../../../scripts/Seiso/Kafka/ /home/nahum/.zkg/testing/zeek-kafka/clones/zeek-kafka/tests/.tmp/kafka.l2s-set-l2e-set/l2s-set-l2e-se
t.zeek > output' failed unexpectedly (exit code 1)
% cat .stderr
error in /usr/local/zeek/share/zeek/base/init-bare.zeek, line 1: cannot load plugin library /home/nahum/.zkg/testing/zeek-kafka/clones/zeek
-kafka/build//lib/SEISO-KAFKA.linux-x86_64.so: /usr/local/lib/librdkafka++.so.1: undefined symbol: rd_kafka_error_string
fatal error in /usr/local/zeek/share/zeek/base/init-bare.zeek, line 1: aborting after plugin errors
kafka.l2s-set-l2e-unset ... failed
% 'zeek ../../../scripts/Seiso/Kafka/ /home/nahum/.zkg/testing/zeek-kafka/clones/zeek-kafka/tests/.tmp/kafka.l2s-set-l2e-unset/l2s-set-l2e-
unset.zeek > output' failed unexpectedly (exit code 1)
% cat .stderr
error in /usr/local/zeek/share/zeek/base/init-bare.zeek, line 1: cannot load plugin library /home/nahum/.zkg/testing/zeek-kafka/clones/zeek
-kafka/build//lib/SEISO-KAFKA.linux-x86_64.so: /usr/local/lib/librdkafka++.so.1: undefined symbol: rd_kafka_error_string
fatal error in /usr/local/zeek/share/zeek/base/init-bare.zeek, line 1: aborting after plugin errors
kafka.l2s-unset-l2e-set ... failed
% 'zeek ../../../scripts/Seiso/Kafka/ /home/nahum/.zkg/testing/zeek-kafka/clones/zeek-kafka/tests/.tmp/kafka.l2s-unset-l2e-set/l2s-unset-l2
e-set.zeek > output' failed unexpectedly (exit code 1)
% cat .stderr
error in /usr/local/zeek/share/zeek/base/init-bare.zeek, line 1: cannot load plugin library /home/nahum/.zkg/testing/zeek-kafka/clones/zeek
-kafka/build//lib/SEISO-KAFKA.linux-x86_64.so: /usr/local/lib/librdkafka++.so.1: undefined symbol: rd_kafka_error_string
fatal error in /usr/local/zeek/share/zeek/base/init-bare.zeek, line 1: aborting after plugin errors
kafka.l2s-unset-l2e-unset ... failed
% 'zeek ../../../scripts/Seiso/Kafka/ /home/nahum/.zkg/testing/zeek-kafka/clones/zeek-kafka/tests/.tmp/kafka.l2s-unset-l2e-unset/l2s-unset-
l2e-unset.zeek > output' failed unexpectedly (exit code 1)
% cat .stderr
error in /usr/local/zeek/share/zeek/base/init-bare.zeek, line 1: cannot load plugin library /home/nahum/.zkg/testing/zeek-kafka/clones/zeek
-kafka/build//lib/SEISO-KAFKA.linux-x86_64.so: /usr/local/lib/librdkafka++.so.1: undefined symbol: rd_kafka_error_string
fatal error in /usr/local/zeek/share/zeek/base/init-bare.zeek, line 1: aborting after plugin errors
kafka.resolved-topic-config ... failed
% 'zeek -r ../../../tests/pcaps/exercise-traffic.pcap ../../../scripts/Seiso/Kafka/ /home/nahum/.zkg/testing/zeek-kafka/clones/zeek-kafka/t
ests/.tmp/kafka.resolved-topic-config/resolved-topic-config.zeek > output' failed unexpectedly (exit code 1)
% cat .stderr
error in /usr/local/zeek/share/zeek/base/init-bare.zeek, line 1: cannot load plugin library /home/nahum/.zkg/testing/zeek-kafka/clones/zeek
-kafka/build//lib/SEISO-KAFKA.linux-x86_64.so: /usr/local/lib/librdkafka++.so.1: undefined symbol: rd_kafka_error_string
fatal error in /usr/local/zeek/share/zeek/base/init-bare.zeek, line 1: aborting after plugin errors
kafka.resolved-topic-default ... failed
% 'zeek -r ../../../tests/pcaps/exercise-traffic.pcap ../../../scripts/Seiso/Kafka/ /home/nahum/.zkg/testing/zeek-kafka/clones/zeek-kafka/t
ests/.tmp/kafka.resolved-topic-default/resolved-topic-default.zeek > output' failed unexpectedly (exit code 1)
% cat .stderr
error in /usr/local/zeek/share/zeek/base/init-bare.zeek, line 1: cannot load plugin library /home/nahum/.zkg/testing/zeek-kafka/clones/zeek
-kafka/build//lib/SEISO-KAFKA.linux-x86_64.so: /usr/local/lib/librdkafka++.so.1: undefined symbol: rd_kafka_error_string
fatal error in /usr/local/zeek/share/zeek/base/init-bare.zeek, line 1: aborting after plugin errors
kafka.resolved-topic-override-and-config ... failed
% 'btest-diff output' failed unexpectedly (exit code 1)
% cat .diag
== File ===============================
== Diff ===============================
--- /tmp/test-diff.529999.output.baseline.tmp	2021-03-05 15:33:14.932647429 +0000
+++ /tmp/test-diff.529999.output.tmp	2021-03-05 15:33:14.900647311 +0000
@@ -1,2 +0,0 @@
-Kafka topic set to configuration-table-topic
-Kafka topic set to const-variable-topic
% cat .stderr
error in /usr/local/zeek/share/zeek/base/init-bare.zeek, line 1: cannot load plugin library /home/nahum/.zkg/testing/zeek-kafka/clones/zeek
-kafka/build//lib/SEISO-KAFKA.linux-x86_64.so: /usr/local/lib/librdkafka++.so.1: undefined symbol: rd_kafka_error_string
fatal error in /usr/local/zeek/share/zeek/base/init-bare.zeek, line 1: aborting after plugin errors
kafka.resolved-topic-override-only ... failed
% 'zeek -r ../../../tests/pcaps/exercise-traffic.pcap ../../../scripts/Seiso/Kafka/ /home/nahum/.zkg/testing/zeek-kafka/clones/zeek-kafka/t
ests/.tmp/kafka.resolved-topic-override-only/resolved-topic-override-only.zeek > output' failed unexpectedly (exit code 1)
% cat .stderr
error in /usr/local/zeek/share/zeek/base/init-bare.zeek, line 1: cannot load plugin library /home/nahum/.zkg/testing/zeek-kafka/clones/zeek
-kafka/build//lib/SEISO-KAFKA.linux-x86_64.so: /usr/local/lib/librdkafka++.so.1: undefined symbol: rd_kafka_error_string
fatal error in /usr/local/zeek/share/zeek/base/init-bare.zeek, line 1: aborting after plugin errors
kafka.send-all-active-logs-l2e-set ... failed
% 'zeek ../../../scripts/Seiso/Kafka/ /home/nahum/.zkg/testing/zeek-kafka/clones/zeek-kafka/tests/.tmp/kafka.send-all-active-logs-l2e-set/s
end-all-active-logs-l2e-set.zeek > output' failed unexpectedly (exit code 1)
% cat .stderr
error in /usr/local/zeek/share/zeek/base/init-bare.zeek, line 1: cannot load plugin library /home/nahum/.zkg/testing/zeek-kafka/clones/zeek
-kafka/build//lib/SEISO-KAFKA.linux-x86_64.so: /usr/local/lib/librdkafka++.so.1: undefined symbol: rd_kafka_error_string
fatal error in /usr/local/zeek/share/zeek/base/init-bare.zeek, line 1: aborting after plugin errors
kafka.send-all-active-logs-l2e-unset ... failed
% 'zeek ../../../scripts/Seiso/Kafka/ /home/nahum/.zkg/testing/zeek-kafka/clones/zeek-kafka/tests/.tmp/kafka.send-all-active-logs-l2e-unset
/send-all-active-logs-l2e-unset.zeek > output' failed unexpectedly (exit code 1)
% cat .stderr
error in /usr/local/zeek/share/zeek/base/init-bare.zeek, line 1: cannot load plugin library /home/nahum/.zkg/testing/zeek-kafka/clones/zeek
-kafka/build//lib/SEISO-KAFKA.linux-x86_64.so: /usr/local/lib/librdkafka++.so.1: undefined symbol: rd_kafka_error_string
fatal error in /usr/local/zeek/share/zeek/base/init-bare.zeek, line 1: aborting after plugin errors
kafka.send-all-active-logs-l2s-set-l2e-set ... failed
% 'zeek ../../../scripts/Seiso/Kafka/ /home/nahum/.zkg/testing/zeek-kafka/clones/zeek-kafka/tests/.tmp/kafka.send-all-active-logs-l2s-set-l
2e-set/send-all-active-logs-l2s-set-l2e-set.zeek > output' failed unexpectedly (exit code 1)
% cat .stderr
error in /usr/local/zeek/share/zeek/base/init-bare.zeek, line 1: cannot load plugin library /home/nahum/.zkg/testing/zeek-kafka/clones/zeek
-kafka/build//lib/SEISO-KAFKA.linux-x86_64.so: /usr/local/lib/librdkafka++.so.1: undefined symbol: rd_kafka_error_string
fatal error in /usr/local/zeek/share/zeek/base/init-bare.zeek, line 1: aborting after plugin errors
kafka.send-all-active-logs-l2s-set-l2e-unset ... failed
% 'zeek ../../../scripts/Seiso/Kafka/ /home/nahum/.zkg/testing/zeek-kafka/clones/zeek-kafka/tests/.tmp/kafka.send-all-active-logs-l2s-set-l
2e-unset/send-all-active-logs-l2s-set-l2e-unset.zeek > output' failed unexpectedly (exit code 1)
% cat .stderr
error in /usr/local/zeek/share/zeek/base/init-bare.zeek, line 1: cannot load plugin library /home/nahum/.zkg/testing/zeek-kafka/clones/zeek
-kafka/build//lib/SEISO-KAFKA.linux-x86_64.so: /usr/local/lib/librdkafka++.so.1: undefined symbol: rd_kafka_error_string
fatal error in /usr/local/zeek/share/zeek/base/init-bare.zeek, line 1: aborting after plugin errors
kafka.show-plugin ... failed
% 'btest-diff output' failed unexpectedly (exit code 1)
% cat .diag
== File ===============================
== Diff ===============================
--- /tmp/test-diff.530119.output.baseline.tmp	2021-03-05 15:33:15.728650374 +0000
+++ /tmp/test-diff.530119.output.tmp	2021-03-05 15:33:15.696650256 +0000
@@ -1,12 +0,0 @@
-Seiso::Kafka - Writes logs to Kafka (dynamic)

[Writer] KafkaWriter (Log::WRITER_KAFKAWRITER)
[Constant] Kafka::kafka_conf
[Constant] Kafka::additional_message_values
[Constant] Kafka::topic_name
[Constant] Kafka::max_wait_on_shutdown
[Constant] Kafka::tag_json
[Constant] Kafka::json_timestamps
[Constant] Kafka::debug
[Constant] Kafka::mock
[Event] kafka_topic_resolved_event

=======================================
% cat .stderr
error in /usr/local/zeek/share/zeek/base/init-bare.zeek, line 1: cannot load plugin library /home/nahum/.zkg/testing/zeek-kafka/clones/zeek
-kafka/build//lib/SEISO-KAFKA.linux-x86_64.so: /usr/local/lib/librdkafka++.so.1: undefined symbol: rd_kafka_error_string
fatal error in /usr/local/zeek/share/zeek/base/init-bare.zeek, line 1: aborting after plugin errors
14 of 14 tests failed

I have confirmed that this issue does not occur on centos 8 and installing with zkg in that environment works as expected.  The metron-bro-plugin-kafka project did not officially support Ubuntu, but I am working on adding that support now.

@JonZeolla any progress on this?

I answered on slack, but just to reiterate here for anyone else following along:
From our testing it seems that the plugin install process works fine on Centos 8, which is the only OS currently supported.  I did open #21 that begins to add Ubuntu support.  So far we have been able to reproduce your issue in this testing environment, but neither @ottobackwards nor I have had a chance to track down the specific fix yet.

@emnahum wanted to make sure you got notified of this.  I think we have Ubuntu working now, so any issues you're still experiencing after following the updated setup steps would be a bug.

Yes I saw.  I haven't had a chance to test it yet through.
-Erich
On Tue, Jun 8, 2021 at 1:01 PM JonZeolla @.***> wrote:

@emnahum https://github.com/emnahum wanted to make sure you got
notified of this. I think we have Ubuntu working now, so any issues you're
still experiencing after following the updated setup steps would be a bug.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/SeisoLLC/zeek-kafka/issues/19#issuecomment-856938142,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGENXCOO6BD33LHQ6AR3HBDTRZEE7ANCNFSM4YIVDEBQ
.

Hello
I still have build error, both via zkg install and manual configure and make.
I have an ubuntu 22.04 server with zeek 5.1.1 and zeek/seisollc/zeek-kafka.
The make command fails with the following error :
[ 25%] Building CXX object CMakeFiles/SEISO-KAFKA.linux-x86_64.dir/src/KafkaWriter.cc.o                                                                                /opt/zeek-kafka/src/KafkaWriter.cc: In constructor ‘zeek::logging::writer::KafkaWriter::KafkaWriter(zeek::logging::WriterFrontend*)’: /opt/zeek-kafka/src/KafkaWriter.cc:48:3: error: ‘IterCookie’ was not declared in this scope    48 |   IterCookie *c = val->AsTable()->InitForIteration();                                                                                |   ^~~~~~~~~~ /opt/zeek-kafka/src/KafkaWriter.cc:48:15: error: ‘c’ was not declared in this scope    48 |   IterCookie *c = val->AsTable()->InitForIteration();       |               ^ /opt/zeek-kafka/src/KafkaWriter.cc:48:33: error: invalid use of incomplete type ‘zeek::PDict<zeek::TableEntryVal>’ {aka ‘const class zeek::Dictionary<zeek::TableEntryVal>’}    48 |   IterCookie *c = val->AsTable()->InitForIteration();       |                                 ^~
and more similar errors.
It seems that IterCookie structure is deprecated in zeek 5.0.0+.
Anyway to solve this issue ?
thanks
A

https://github.com/SeisoLLC/zeek-kafka/commit/39e9dbfdb924f1fb309dc1323f5963a244aa5551  this commit to main resolved this issue.  I'm not sure you are building with main?


WIP - unlock container before starting it via an OCI runtime

If needed, unlock the container before starting it via the OCI
runtime. We do not have any control how long the starting process
may take, and there are some cases [1] where the runtime may even
deadlock. Unlocking it here, will prevent a deadlock with other
Podman processes attempting to acquire the container's lock.
In order to be able to acquire the lock in (*Container).start(), we
need to change the attach workflow a bit.  attach(...) has in some
cases beeen executed in a goroutine ultimately yielding to panics when
trying to acquire the lock since the posix semaphores used to implement
the container locks do not allow for another thread to unlock.  This
required moving the final attaching to a goroutine and passing down the
attach error channel to attach(...).  A nice sideeffect is that most
complexity is now hidden from the callers.
Note that [1] is caused by a known issue when the NOTIFY_SOCKET is set.
In that case, the OCI runtime will block until the container sends
sdnotify messages.  This behaviour is legit but it's equally dangerous
for the aforementioned deadlock potential.  This change generalizes the
deadlock potential as the OCI runtimes and anything they might
be calling is outside of our immediate control and we should not
keep the lock until we return.
Further note that the Podman process will still be blocked by
StartContainer(...) but it won't block others anymore.
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1781506
Signed-off-by: Valentin Rothberg<EMAIL_ADDRESS>

@rhatdan @mheon @giuseppe PTAL
@edsantiago, in case you have some downstream attach tests, we could throw them at this change. But I am fairly confident the PR is not changing any visible semantics.

Please don't restart the last test. The errors occur reproducibly there but I fail to get them locally.

Biggest potential issue I can see is that we now allow other operations
while the container is starting. Since state is still Created and the lock
is available libpod will let you unmount the container, or start a parallel
start job on the same container, or remove it.
On Thu, Dec 12, 2019, 09:01 Valentin Rothberg<EMAIL_ADDRESS>wrote:

Please don't restart the last test. The errors occur reproducibly there
but I fail to get them locally.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/containers/libpod/pull/4683?email_source=notifications&email_token=AB3AOCCM7REJZBOSTBMMLPDQYI7ZVA5CNFSM4JZ3NYCKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEGWX7GY#issuecomment-565018523,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB3AOCEYKYMFFHUTJ5DIE2TQYI7ZVANCNFSM4JZ3NYCA
.

Biggest potential issue I can see is that we now allow other operations while the container is starting. Since state is still Created and the lock is available libpod will let you unmount the container, or start a parallel start job on the same container, or remove it.

That could turn into some nasty situations, true. Eeeew. Seems like we're between a rock and a hard place.

I think we might want a Starting state that locks out remove, start, etc. The problem would be how to transition out of that state if we transition out of that state if the OCI runtime does block and the user Control-C's the Podman process.

I think we might want a Starting state that locks out remove, start, etc. The problem would be how to transition out of that state if we transition out of that state if the OCI runtime does block and the user Control-C's the Podman process.

I thought about that too and am not yet sure we can solve that entirely race free. If we find some way to recover from such corruption, that'll be ideal.
I will mark this PR as work-in-progress, as there's clearly a bigger rabbit hole.

Closing for now as there's no immediate need and ultimately not a good solution at hand atm.


Bug: Service config variables not updated when variables are updated

Create a service with below sample config variables

config:
  client_id: "abc"
  client_secret: "ThisIsMySecret"

Add service to Assemblyline
Update service config variables like below;

config:
  client_id: "def"
  client_secret: "NoLongerASecret"

Add the new service to Assemblyline, without deleting the previous version
Go to the service and pick the new service from the dropdown list
New config should be available, however, old variables are still present
Same if you add new configs.

I'm not 100% sure if this is an issue or not and I think I'm going to need just a little more info. For starter I can explain you how the service diffing works so you can tell me if you see things happening differently.
When you register a service to AL, its default config get saved in the DB as SERVICENAME_vVERSION so for each service version that where ever installed on your instance, you get the default config for that service. But then we have a service_delta index which is the changes that you are making to the default config. The service delta changes completely override whatever the service default where.
Here's an exemple:
Service_v4.4.0,1 has the following config:
  client_id: 'abc'
  client_secret: "ThisIsMySecret"

Service_v<IP_ADDRESS> has the following config:
config:
  client_id: 'def'
  client_secret: "NoLongerASecret"

If the service delta is empty (i.e. you did not change the config block from the UI, you will get the proper default for each service. If you changed the client_secret in the UI to "ThisIsAnUpdatedSecret", no matter which of the two service version you pick (<IP_ADDRESS> or <IP_ADDRESS>) the client_secret will always be "ThisIsAnUpdatedSecret".
Is this what you are observing right now in your system?

No, if I do not change the values in the UI they are still not updated, unless I delete the old service and install the new one.
So I install Service_v<IP_ADDRESS> I don't change anything on the UI, I change the service manifest for Service_v<IP_ADDRESS> and add that to the UI again, the values do not change unless I delete Service_v<IP_ADDRESS> and add the service manifest again to install Service_v<IP_ADDRESS>.
This is also true for submission_params, If I add a new submission_params they are not changed on the UI until I delete the service and add it back in again.
Note: I only observed this happening when we paste in the service manifest, not when pressing the update button.

Ok we can check the UI service manifest pasting path.


Set Advertisement.Flags() will cause exception when BluetoothLEAdvertisementPublisher start.

[Enter feedback here]
On my windows10, run code below to do ble advertisement:
`auto publisher =  Bluetooth::Advertisement::BluetoothLEAdvertisementPublisher();
// Add custom data to the advertisement
auto manufacturerData = Bluetooth::Advertisement::BluetoothLEManufacturerData();
manufacturerData.CompanyId(0xaaaa);
auto writer = DataWriter();
writer.WriteByte('1');
writer.WriteByte('2');
writer.WriteByte('3');
manufacturerData.Data() = writer.DetachBuffer();
publisher.Advertisement().ManufacturerData().Append(manufacturerData);
publisher.UseExtendedAdvertisement(true);
publisher.Advertisement().Flags(Bluetooth::Advertisement::BluetoothLEAdvertisementFlags::GeneralDiscoverableMode); //set adv flags
printf("publisher flags :%d", publisher.Advertisement().Flags().Value()); // log shows flags was set.
publisher.Start(); //meet winrt::hresult_invalid_argument here...`
I try the code above without "set Advertisement flags" and the code can run successfully, but the ble advertisement can not be discoveried. So I think advertisement flags should be set ?  Then if flags is set ，how to deal with with the exception? If I have missed other params should be set together then cause the exception?

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

ID: 6a585126-72e0-0dc2-d0bc-f0127e548b4e
Version Independent ID: 57eec18b-e62f-d111-e1fe-b302b9bd318a
Content: BluetoothLEAdvertisement.Flags Property (Windows.Devices.Bluetooth.Advertisement) - Windows UWP applications
Content Source: winrt-api-build/xml/Windows.Devices.Bluetooth.Advertisement/BluetoothLEAdvertisement.xml
Product: uwp
Technology: winrt-reference
GitHub Login: @stevewhims
Microsoft Alias: stwhi

Hi, @13xiaobang, and thanks for filing this issue. The feedback channel you're using here (Submit and view feedback for > This page) is for feedback about the documentation in this topic itself, as published. For example, if the content is incorrect or incomplete. But as far as I know, the description of this API does correctly reflect the intent of its functionality. So we wouldn't want to change the documentation here.
For questions or feedback (or requests for help) regarding a specific coding scenario, like this, one option is to click Submit and view feedback for > This product, and you'll be taken to Microsoft Q&A (more info about that below).
Here are all of the developer support resources, for completeness.

Microsoft Q&A is the right place to lobby for a change or a new feature, to make a suggestion, or to ask a product question.
For community assistance with development questions, there are our forums, and StackOverflow.
The Windows developer support site explains other support options.
The Visual Studio developer community is available, and responsive. The former User Voice feature is now there on the Suggest a feature tab, if you want to lobby for a change, a feature, or to make a suggestion.
For developer issues, or suspected product bugs, there's Microsoft Support; a support engineer will look at the repro and see whether the issue is a Microsoft product bug, or something else. If it's a bug with a Microsoft product then the ticket will be free of charge.

I'll go ahead and close this issue now, since there's no action to take in the documentation. You can always reply to a closed issue, or even re-open it if you feel it's been closed in error.
Thanks!
-Steve


Support experimental survey Wave 12

Description
Support experimental version of survey Wave 12. This adds qualifying data to the microdata but does not include it in any aggregates. FB-defined specs are here.
New variable and indicator definitions are not needed here since experimental Wave 12 data is not being included in any aggregates. We will need to add those for post-experimental Wave 12.
Changelog

Create function experimental_arm_assignment to determine experimental version displayed based on assigned random number. Arm logic is defined in FB's specs.
Call experimental Wave 12 12.5 (numeric). The finalized post-experimental Wave 12 is planned to have a different survey ID and be called 12 (numeric) for easier coding and to avoid date-based logic. Generally speaking, we expect wave to be an integer, although no logic explicitly depends on that. I've opted to code experimental Wave 12 as numeric (rather than string, which would have a clearer meaning) so that the microdata output wave field won't change type.
Drop wave "12.5" from data for aggregation; we don't want to include experimental data.
Exclude w12_assignment and module, along with raceethnicity, from being used in filter_complete_responses.
Update tests.

@krivard This is ready to deploy.

@krivard FYI, the first possible day for Wave 12 to come out is tomorrow, Sept 30, though we may have to delay due to issues with Qualtrics affecting the international instrument.

We now deploy surveys through the same github mechanism as all the other indicators 🎉
I will merge this code and deploy to prod. When we're ready to begin pulling in qualtrics files for wave 12, we should update the production params file.


Automated cleanup for template tests

Live tests of samples provision and deploy in resource groups with a DeleteAfter tag. In the case of templates we should add tags to the deployments so those can be cleaned up by automation as well.
If we don't tag resource groups we will leak resources in certain build failures including agent crashes, network failures, or failures in the test script which halt execution of deprovisioning steps.
Couple ways to do this:

Add a parameter to azd provision that is passed through to templates or sets tags directly on the resource group(s)
Add parameter to azd provision that deploys to an existing resource group
Guess the name of the resource group that will be deployed, create it, then run azd deploy as normal
Tag the created resource group in the script after provisioning (this could encounter problems if there is a crash/network issue in the middle of provisioning)

is this fixed by this: https://github.com/Azure/azure-dev/issues/481 ???

We definitely add tags with DeleteAfter as-of today. Closing this.


Create a mono repo which contains 4 separate Spring Boot Projects

Created a new rep and added the 3 different services - ProductService, OrderService and Inventory Service to it. Also added the postman test scripts/


Want to add some documentation

1.code_of_conduct.md
2.LICENSE.md
3.contributors profile section in README.md

please do any contribution after 15th, any contribution done before 15th would be considered invalid

Ok.


Drop-down menu response flaky on mobile browser

Drop-down menus do not always react to touch on Android Phone if at all. Bigger buttons appear to work as expected. This issue is the same using Chrome 90.0.4430.60 on Android.
Does this issue occur when all extensions are disabled?: Yes

VS Code Version:  1
OS Version:  Android 11; SM-N981U1 Build/ RP1A.200720.012

Steps to Reproduce:

Open menu
Touch a top-level option
Touch any sub-level option

Found a resolution

Settings (Gear - bottom left)
Settings
Window: Menu Bar Visibility

Default is: Compact
Change to: Classic
Have a nice day.

Ok I lied still having issues!
Completely unusable to me if I can't control mouse clicks as screen taps.
Also when my key board pops up all clickablity in the workspace anywhere is Non responsive. Touch and hold to pull up pop-up menus cause the keyboard to appear as well!
Nice try guys.  Without better mobile and touch screen control, this project does not get a passing grade.
In bed today with major back pain. unable to walk to my office which is just a door over. I am deadline and was hoping this would be my solution.
HELP


Bug fix/cleanup commtasks

@maierlars: Doesn't fix the problems altogether, however, here is the branch as requested.

https://jenkins01.arangodb.biz/view/PR/job/arangodb-matrix-pr/4318/


Bonfire

Bonfire is an extensible open source federated community platform, that empowers groups to easily configure their spaces from the ground up, according to a variety of needs and visions.

NLnet project
source code

The project is active and has very good developer-facing documentation. It's still in beta and will apparently see substantial changes, so we may want to get in touch with developers and see what's the best mode of collaboration.

I'd previously attempted to package Bonfire in my free time before Summer of Nix. The repo contains a flake.nix but it did not work at the time and has not been updated in 2 years. I tried various approaches for packaging elixir deps including both mix2nix and IFD. As far as I remember at the time the IFD was not creating a reproducible hash, and mix2nix did not support git dependencies of which bonfire has many due to it's modular nature.


Missing helper _interopRequireWildcard

Tested with swc 1.0.14
user@dev:~/$ cat foo.js
'use strict';
import * as bar from './bar';
user@dev:~/$ cat bar.js
export const a = 1;
export const b = 2;
user@dev:~/$ swc foo.js
'use strict';
var bar = _interopRequireWildcard(require('./bar'));
'use strict';

This is based on actual code that expects to be able to access bar.a and bar.b afterward in foo.js.

What's your .swcrc?

{
  "jsc": {
    "parser": {
      "syntax": "ecmascript",
      "jsx": true,
      "classProperty": true,
      "functionBind": true,
      "decorators": true,
      "decoratorsBeforeExport": false
    }
  },
  "module": {
    "type": "commonjs",
    "strict": false,
    "strictMode": true,
    "lazy": false,
    "noInterop": false
  }
}

Seems like it's already fixed in 1.0.15. I'll publish 1.0.15 soon.

@rvolgers I published 1.0.15

Unfortunately it doesn't appear to be fixed in 1.0.15.
user@dev:~/somepkg$ npm view @swc/core version
1.0.15
user@dev:~/somepkg$ cat foo.js
'use strict';
import * as bar from './bar';
user@dev:~/somepkg$ cat bar.js
export const a = 1;
export const b = 2;
user@dev:~/somepkg$ npx swc foo.js
var bar = _interopRequireWildcard(require('./bar'));
'use strict';

user@dev:~/somepkg$ cat .swcrc
 cat .swcrc
{
  "jsc": {
    "parser": {
      "syntax": "ecmascript",
      "jsx": true,
      "classProperty": true,
      "functionBind": true,
      "decorators": true,
      "decoratorsBeforeExport": false
    }
  },
  "module": {
    "type": "commonjs",
    "strict": false,
    "strictMode": true,
    "lazy": false,
    "noInterop": false
  }
}

What is your nodejs version and os?
I'm asking this because there's a test about it and it passes on 8 / 10 / 11

I verified that it happens on osx 11 (although test successes)

Fixed with<EMAIL_ADDRESS>


Collapse component hides content on reduced width

Hi There,
I just found out that in collapse when we open collapse item and then reduce the width of window content gets hidden because of max height(+ overflow:hidden;) given to collapse. It fixes it self after we close that collapse item and reopen it.
Collapse item should adjust height when we reduce width of window.
Here
Step to create this issue:

Go to link
Open any collapse item
Reduce the width of window

I am using your collapse in my project and lots of things depends on this collapse feature. So, I hope that you will fix this soon.

was updated by fixing this problem, thank you very much for the contribution v3.5.5

My version is 3.11.10 but the same error

Collapse is hides contents.


feat: Added Export Image Shortcut

Closes #2410

@nikku I have added my work you can review this!


Check/tidy response validation for contingency table pvalue

Client API-side is allowing number | string for pvalue (2x2 and RxC)
Check that service is really just returning number (as API docs indicate) and tighten client as appropriate.

ive opened a related issue for plot.data veupathdb/plot.data#94


[enhancement] after setting global setting user can overwrite the setting on the tag basis

Just an idea:
Currently:

I am setting the color of text to black globally
after settings this globally the option to set text color per tag basis is removed

What I would expect

the setting isn't removed
the text is black until the user set in the specific tag settings color to the different  one
so the specify tag settings (local) can override the global ones, the local one might be just local later in the css file

But the setting of each tag would be very long, and I will think of a more reasonable way to solve it.

What I meant the same mechanism you use for default settings in the "Global Settings";

After user set a value in "Global settings" the value us the default one for every user defined tag, for example the black color of the text
If for some reason user want to change it (for example user has one tag with dark color background that is hard to see black text and want to change the color of the text to white, the user can input the value for white in the "text color" in the specified tag, text color in  the other tags is still black)

From the technical point of view, I am not sure how this might works, but my initial idea is:

if the field for tag is empty - populate css value from global settings
if the  specific field in the specific tag is not empty - populate css value from the tag local settings
I think this should be computationally heavy :P

And again, thank you for your work!

Or the setting of each tag has only added field if the field is set by user, otherwise tag css is governed by global setting;
Sorry If I am not clear what I want to convey,
Currently the ability to set the property of specific tag dissappear when I set the same property globally via Global settings,
(the field in tag settings is gone)
What I want

Global setting work like now but the user still have the ability to set this property per tag basis, if user didnt set any property at the local tag, the property from "global settings' are used

try 1.1.4

thanks, this is really useful! I am closing this as this is solving my issue :)


Add PlantUML.js

PlantUML.js that works completely on the browser without needing a server.
PlantUML.js Project
Improved editor
PlantUML.js

Also add compatible java script lightweight http server.


A strongly-named assembly is required...

Can we get the BingMapsRESTToolkit.dll as a strongly named assembly by default?
Could not load file or assembly 'BingMapsRESTToolkit, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null' or one of its dependencies. A strongly-named assembly is required. (Exception from HRESULT: 0x80131044)
I can fix this mysefl, but should be strongly named from source if possible?
Thx for a great API!
//A

There are plans to do this, unfortunately the is a lot of red tape to go through at Microsoft to do this, thus the delay.

Any update on this?  My problem is actually the SDS Toolkit, but I assume it's the same problem.

Closing this as stale. We have no new assembly available at this point but you can build the nuget yourself from this public repo.


:page_facing_up: Added MIT license

We are not using the licensed software so it should be fine. And we will be changing even WebCamJS soon I guess @Owen-Cochell

Just to clarify, this is not for the attendance project, but the special GitHub repo of the organization. (I am mainly wanting to try out PR with multiple reviewers)

I agree, I don't foresee any licesing issues. MIT's should do the job, and make us look somewhat more professional.
I love conversations in PR's 😄


WSL networking stopped working

Windows Version
Microsoft Windows [Version 10.0.22621.1413]
WSL Version
<IP_ADDRESS>
Are you using WSL 1 or WSL 2?

[X] WSL 2
[ ] WSL 1

Kernel Version
<IP_ADDRESS>
Distro Version
Ubuntu 22.04 / Debian 11.6
Other Software
No response
Repro Steps

Attempt any kind of communication outside of the WSL network

Expected Behavior
WSL reacts to incoming packages
Actual Behavior
WSL seems to ignore any incoming packages.

Any attempt to communicate with anything that isn't the IP address of the host system fails.
The packages DO reach their destination and replys seem to reach wsl (at least thats what it looks like in Wireshark)
BUT it seems like WSL ignores any replies
Reinstalling the wsl feature or the distributions did not fix the issue.

Diagnostic Logs
Sent via feedback-hub as the logfile generated from the script got quite large.
Example when pinging google.com (note that DNS does work):

Could you check if running the following command fixes the issue?
echo nameserver <IP_ADDRESS> | sudo tee /etc/resolv.conf

Could you check if running the following command fixes the issue?
echo nameserver <IP_ADDRESS> | sudo tee /etc/resolv.conf

Unfortunately this will only make the problem worse, as DNS does work.

Seeing this exact same issue
WSL version: <IP_ADDRESS>
Kernel version: <IP_ADDRESS>
WSLg version: 1.0.51
MSRDC version: 1.2.3770
Direct3D version: 1.608.2-61064218
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.22621.525

I've tried everything I can think of, just like @krippix I can see the packets return from their destination but it's like the Ubuntu install is ignoring them.

No I feel like i'm losing my mind. I was on Windows 10 and all was fine.
I upgraded to Windows 11, which was the OS in the above wsl.exe --version output.
Now i've downgraded back to Windows 10 and i'm having the same problem!
I've tried various different versions of WSL Kernel and WSL version. All broken.
WSL version: <IP_ADDRESS>
Kernel version: <IP_ADDRESS>
WSLg version: 1.0.51
MSRDC version: 1.2.3770
Direct3D version: 1.608.2-61064218
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.19045.2846

I have fixed this, special thanks to @kunzjacq in this thread:
https://github.com/microsoft/WSL/issues/4926
When I upgraded my PC, I also moved it. I used an ethernet port where once there was a switch. It was set up as a trunked port. If VLANs are present on your ethernet, you get exactly the problem described above.
I have made the port an access port and now everything is fine.


HBASE-27296 Some Cell's implementation of toString() such as Individu…

…alBytesFieldCell prints out value and tags which is too verbose (#4695)
Signed-off-by: Nick Dimiduk<EMAIL_ADDRESS>

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 55s
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.4 Compile Tests _

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

+1 :green_heart:
mvninstall
2m  7s
branch-2.4 passed

+1 :green_heart:
compile
2m 38s
branch-2.4 passed

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

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

+1 :green_heart:
spotbugs
1m 39s
branch-2.4 passed

_ Patch Compile Tests _

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

+1 :green_heart:
mvninstall
1m 53s
the patch passed

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

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

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

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

+1 :green_heart:
hadoopcheck
14m 26s
Patch does not cause any errors with Hadoop 2.10.1 or 3.1.2 3.2.2 3.3.1.

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

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

_ Other Tests _

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

36m 48s

Subsystem
Report/Notes

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

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

Optional Tests
dupname asflicense javac spotbugs hadoopcheck hbaseanti spotless checkstyle compile

uname
Linux 23078103b660 5.4.0-1081-aws #88~18.04.1-Ubuntu SMP Thu Jun 23 16:29:17 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2.4 / b9a13eba67

Default Java
AdoptOpenJDK-1.8.0_282-b08

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

modules
C: hbase-common hbase-server U: .

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

versions
git=2.17.1 maven=3.6.3 spotbugs=4.2.2

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 56s
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.4 Compile Tests _

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

+1 :green_heart:
mvninstall
2m  5s
branch-2.4 passed

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

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

+1 :green_heart:
javadoc
0m 33s
branch-2.4 passed

_ Patch Compile Tests _

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

+1 :green_heart:
mvninstall
1m 57s
the patch passed

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

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

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

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

_ Other Tests _

+1 :green_heart:
unit
1m 11s
hbase-common in the patch passed.

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

183m 52s

Subsystem
Report/Notes

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

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 442e037f9ccc 5.4.0-1071-aws #76~18.04.1-Ubuntu SMP Mon Mar 28 17:49:57 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2.4 / b9a13eba67

Default Java
AdoptOpenJDK-1.8.0_282-b08

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

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

modules
C: hbase-common hbase-server U: .

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

versions
git=2.17.1 maven=3.6.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
1m  9s
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.4 Compile Tests _

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

+1 :green_heart:
mvninstall
2m 38s
branch-2.4 passed

+1 :green_heart:
compile
0m 59s
branch-2.4 passed

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

+1 :green_heart:
javadoc
0m 42s
branch-2.4 passed

_ Patch Compile Tests _

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

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

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

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

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

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

_ Other Tests _

+1 :green_heart:
unit
1m 23s
hbase-common in the patch passed.

+1 :green_heart:
unit
175m 58s
hbase-server in the patch passed.

197m 57s

Subsystem
Report/Notes

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

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux b706034a5b84 5.4.0-122-generic #138-Ubuntu SMP Wed Jun 22 15:00:31 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2.4 / b9a13eba67

Default Java
AdoptOpenJDK-11.0.10+9

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

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

modules
C: hbase-common hbase-server U: .

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

versions
git=2.17.1 maven=3.6.3

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

This message was automatically generated.


Create Helpers for exposing pod/deployment in a cluster

When running chaos tests this is common pattern:

Create a target pod or deployment (commonly, on its own namespace)
Subject the target pod/deployment to certain attack (e.g. kill replica, stress resources, delay network traffic)
Submit load to the target and measure behavior

A similar requirement may arise in other contexts, such as integration tests.
However, in order to reach the target from outside a k8s cluster, it must be exposed as a service and optionally (depending on the cluster's infrastructure) the service exposed as an ingress.
Presently the xk6-kubernetes extension offers the basic building blocks for doing so, but requires a considerable programming effort.  It can be done by means of applying a raw yaml manifest or by creating a kubernetes service object "manually" and submitting it to the cluster via a create operation. Neither option seems neither convenient nor idiomatic in the context of k6 testing.
Therefore, it would be convenient to create a helper method in the ingress package that allows exposing a pod/deployment as a service and, optionally, as an ingress.
The intended API should look similar to this example below:
 import { kubernetes } from xk6-kubernetes

k8s  =  new Kubernetes()

pod = k8s.pods.Create({
  name: "my-pod",
  namespace: "my-namespace",
  image: "my-image",
} )

k8s.helpers.expose({
  selector: { run: "my-app" },
  service: "my-service",
  type: "ClusterIP",
  port: 80,
  ingress: "my-ingress",
  path: "/my-app"
})

With the introduction of the Generic API and helper functions such as getExternalIP this helper may result redundant.


llama-cpp: 1671 -> 1710

Description of changes
https://github.com/ggerganov/llama.cpp/releases
This version bump has a lot of changes; importantly, there is a fix for building with ROCM, which is currently not working with version 1671.

Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

[X] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[X] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Tested building with all combinations of rocmSupport, openblasSupport, and openclSupport.
Did not test cudaSupport.
Tested ollama with openblasSupport and rocmSupport builds.
To build with rocmSupport, you will also need https://github.com/NixOS/nixpkgs/pull/277415

Result of nixpkgs-review pr 277451 run on x86_64-linux 1

2 packages built:

llama-cpp
ollama

btw, I tested with cuda enabled and got an error before the branch was merged
g the system configuration...
error: builder for '/nix/store/paschgz4wfy97isxgs80bbzv5azrwmhd-llama-cpp-1671.drv' fail
       last 25 log lines:
       >
       >   /nix/store/nhbf163gfzlvblfziv5yr0dh82gmsyp7-cudatoolkit-11.8.0/include/crt/ho
       >   error: #error -- unsupported GNU version! gcc versions later than 11 are
       >   not supported! The nvcc flag '-allow-unsupported-compiler' can be used to
       >   override this version check; however, using an unsupported host compiler
       >   may cause compilation failure or incorrect run time execution.  Use at your
       >   own risk.
       >
       >     132 | #error -- unsupported GNU version! gcc versions later than 11 are not
       >         |  ^~~~~
       >
       >   # --error 0x1 --
       >
       >
       >
       >
       >
       > Call Stack (most recent call first):
       >   /nix/store/7jv075yvczy8n2g2zvrdq0bc5y6ymx1a-cmake-3.27.8/share/cmake-3.27/Modules/CMakeDetermineCompilerId.cmake:8 (CMAKE_DETERMINE_COMPILER_ID_BUILD)
       >   /nix/store/7jv075yvczy8n2g2zvrdq0bc5y6ymx1a-cmake-3.27.8/share/cmake-3.27/Modules/CMakeDetermineCompilerId.cmake:53 (__determine_compiler_id_test)
       >   /nix/store/7jv075yvczy8n2g2zvrdq0bc5y6ymx1a-cmake-3.27.8/share/cmake-3.27/Modules/CMakeDetermineCUDACompiler.cmake:307 (CMAKE_DETERMINE_COMPILER_ID)
       >   CMakeLists.txt:271 (enable_language)
       >
       >
       > -- Configuring incomplete, errors occurred!
       For full logs, run 'nix log /nix/store/paschgz4wfy97isxgs80bbzv5azrwmhd-llama-cpp-1671.drv'.

I'm going to test again on this branch with cuda enbled today.
since the error has to do with gcc, I'm afraid it's going to be the same result.
I'm posting just in case someone has seen this before.


Export is not creating a sampler with Extend/CLAMP_TO_EDGE extension

When exporting gltf with a material that has Linear Interpolation and Repeat Extension, no sampler is exported, which I don't think is desired but I suppose is fine assuming those are the default values.
But when exporting with Linear Interpolation and Extend Extension, no sampler is exported. This seems like a bug.
Exporting with Closest Interpolation and Extend Extension does export a sampler with the expected NEAREST filters and CLAMP_TO_EDGE wraps.
Exporting with Linear Interpolation and Clip Extension does export a sampler with LINEAR filters and REPEAT wraps. Which I suppose is ok since Clip doesn't seem to translate to an allowed wrap value, but I think it should be CLAMP_TO_EDGE.
This is somewhat related to issue #307
Version

OS: macOS
Blender 2.83.0 2020-06-03

Should have been fixed by #1082. Try with a 2.90 alpha from https://builder.blender.org/download/.

Yeah 2.90 alpha is good. Thanks!


This project is still maintained?

Just a doubt.

idk.. But i can't use it anymore with Php8

yep .... have many issues to resolve on 7.x too

ping @antonioribeiro

It seems pretty popular. I am just now using Laravel, and I can't work on updates, but it would be great if someone forked the repo and fixed a lot of the issues. Or does anyone know of an alternative repo that is currently maintained and offers tracking capabilities for Laravel?


Archive scraped pages and documents on the Wayback Machine

Great work getting this up and running so quickly! One of the aspects of the City Scrapers project we haven't documented very well is our use of a Python package we created, scrapy-wayback-middleware.
The overall goal of the City Scrapers project is to improve transparency and create an archive not just of upcoming meetings, but past meetings and related documents as well as how they change over time. An important part of that for us has been archiving (almost) every page and document we scrape on the Internet Archive's Wayback Machine as well as in our static output.
Having a second, more public and accessible location makes the meeting information more available regardless of how long the project goes. We've even used it to track potential violations of open meetings laws, since it provides an external source for seeing what content was or was not on a website at a given time. Here's an example of snapshots of the Chicago Plan Commission's website over time.
The con of this approach is that it can make cron builds take significantly longer, but currently we're well under the 6 hour GitHub Actions time limit with over 100 scrapers on the main City Scrapers repo.
If you're interested, you can add scrapy-wayback-middleware as a dependency, and then you'll likely want to subclass the middleware to also scrape any documents you find like we've done in our main middleware.py. Then you can add it in your settings/prod.py like we did in our settings.
We're only activating it when the WAYBACK_ENABLED environment variable is set, and the template cron.yml file already sets this so once it's added in your settings file you should be good to go!
Let me know if you have any questions, and I'm happy to put in a PR for this if it's helpful

Hi Pat, this sounds great! Unfortunately, we're not very familiar with adding dependencies. Could you put in a PR for this?


SVE1 testing: TC-MediaInput-3.17 rename-input output shows 0x01 failure response

As per the test step 1 in TC-MediaInput-3.17, ./chip-tool mediainput rename-input 1 'DVD' 1 1 command output is giving failure response while the expected outcome should be a success response.
Below is the log for the same.
shyam@shyams-MacBook-Pro debug % ./chip-tool mediainput rename-input 1 'DVD' 1 1
[1658524832134] [23667:587168] CHIP: [DL] _Init
[1658524832134] [23667:587168] CHIP: [IN] UDP::Init bind&listen port=0
[1658524832135] [23667:587168] CHIP: [IN] UDP::Init bound to port=57812
[1658524832135] [23667:587168] CHIP: [IN] BLEBase::Init - setting/overriding transport
[1658524832135] [23667:587168] CHIP: [IN] TransportMgr initialized
[1658524832135] [23667:587168] CHIP: [FP] Initializing FabricTable from persistent storage
[1658524832135] [23667:587168] CHIP: [TS] Last Known Good Time: 2022-07-11T10:23:09
[1658524832135] [23667:587168] CHIP: [FP] Fabric index 0x1 was retrieved from storage. Compressed FabricId 0xE2E58F6F9CD07DB0, FabricId 0x0000000000000001, NodeId 0x000000000001B669, VendorId 0xFFF1
[1658524832136] [23667:587168] CHIP: [FP] Fabric index 0x2 was retrieved from storage. Compressed FabricId 0x328FFFEB8E8ABEBB, FabricId 0x0000000000000002, NodeId 0x000000000001B669, VendorId 0xFFF1
[1658524832136] [23667:587168] CHIP: [FP] Fabric index 0x3 was retrieved from storage. Compressed FabricId 0x2CB5E5948E4A6EE8, FabricId 0x0000000000000003, NodeId 0x000000000001B669, VendorId 0xFFF1
[1658524832138] [23667:587168] CHIP: [ZCL] Using ZAP configuration...
[1658524832138] [23667:587168] CHIP: [CTL] System State Initialized...
[1658524832138] [23667:587168] CHIP: [CTL] Stopping commissioning discovery over DNS-SD
[1658524832138] [23667:587168] CHIP: [CTL] Setting attestation nonce to random value
[1658524832138] [23667:587168] CHIP: [CTL] Setting CSR nonce to random value
[1658524832138] [23667:587168] CHIP: [CTL] Stopping commissioning discovery over DNS-SD
[1658524832138] [23667:587168] CHIP: [CTL] Setting attestation nonce to random value
[1658524832138] [23667:587168] CHIP: [CTL] Setting CSR nonce to random value
[1658524832140] [23667:587168] CHIP: [CTL] Generating NOC
[1658524832143] [23667:587168] CHIP: [FP] Validating NOC chain
[1658524832154] [23667:587168] CHIP: [FP] NOC chain validation successful
[1658524832154] [23667:587168] CHIP: [FP] Updated fabric at index: 0x1, Node ID: 0x000000000001B669
[1658524832154] [23667:587168] CHIP: [TS] Last Known Good Time: 2022-07-11T10:23:09
[1658524832154] [23667:587168] CHIP: [TS] New proposed Last Known Good Time: 2021-01-01T00:00:00
[1658524832154] [23667:587168] CHIP: [TS] Retaining current Last Known Good Time
[1658524832157] [23667:587168] CHIP: [FP] Metadata for Fabric 0x1 persisted to storage.
[1658524832159] [23667:587168] CHIP: [TS] Committing Last Known Good Time to storage: 2022-07-11T10:23:09
[1658524832160] [23667:587168] CHIP: [CTL] Joined the fabric at index 1. Compressed fabric ID is: 0x0000000000000000
[1658524832160] [23667:587168] CHIP: [CTL] Stopping commissioning discovery over DNS-SD
[1658524832160] [23667:587168] CHIP: [CTL] Setting attestation nonce to random value
[1658524832160] [23667:587168] CHIP: [CTL] Setting CSR nonce to random value
[1658524832163] [23667:587168] CHIP: [CTL] Generating NOC
[1658524832166] [23667:587168] CHIP: [FP] Validating NOC chain
[1658524832178] [23667:587168] CHIP: [FP] NOC chain validation successful
[1658524832178] [23667:587168] CHIP: [FP] Updated fabric at index: 0x2, Node ID: 0x000000000001B669
[1658524832178] [23667:587168] CHIP: [TS] Last Known Good Time: 2022-07-11T10:23:09
[1658524832178] [23667:587168] CHIP: [TS] New proposed Last Known Good Time: 2021-01-01T00:00:00
[1658524832178] [23667:587168] CHIP: [TS] Retaining current Last Known Good Time
[1658524832180] [23667:587168] CHIP: [FP] Metadata for Fabric 0x2 persisted to storage.
[1658524832181] [23667:587168] CHIP: [TS] Committing Last Known Good Time to storage: 2022-07-11T10:23:09
[1658524832182] [23667:587168] CHIP: [CTL] Joined the fabric at index 2. Compressed fabric ID is: 0x0000000000000000
[1658524832182] [23667:587168] CHIP: [CTL] Stopping commissioning discovery over DNS-SD
[1658524832182] [23667:587168] CHIP: [CTL] Setting attestation nonce to random value
[1658524832182] [23667:587168] CHIP: [CTL] Setting CSR nonce to random value
[1658524832185] [23667:587168] CHIP: [CTL] Generating NOC
[1658524832189] [23667:587168] CHIP: [FP] Validating NOC chain
[1658524832200] [23667:587168] CHIP: [FP] NOC chain validation successful
[1658524832200] [23667:587168] CHIP: [FP] Updated fabric at index: 0x3, Node ID: 0x000000000001B669
[1658524832200] [23667:587168] CHIP: [TS] Last Known Good Time: 2022-07-11T10:23:09
[1658524832200] [23667:587168] CHIP: [TS] New proposed Last Known Good Time: 2021-01-01T00:00:00
[1658524832200] [23667:587168] CHIP: [TS] Retaining current Last Known Good Time
[1658524832202] [23667:587168] CHIP: [FP] Metadata for Fabric 0x3 persisted to storage.
[1658524832203] [23667:587168] CHIP: [TS] Committing Last Known Good Time to storage: 2022-07-11T10:23:09
[1658524832204] [23667:587168] CHIP: [CTL] Joined the fabric at index 3. Compressed fabric ID is: 0x0000000000000000
[1658524832224] [23667:587171] CHIP: [DL] _OnPlatformEvent
[1658524832224] [23667:587171] CHIP: [TOO] Sending command to node 0x1
[1658524832224] [23667:587171] CHIP: [CSM] FindOrEstablishSession: PeerId = E2E58F6F9CD07DB0:0000000000000001
[1658524832224] [23667:587171] CHIP: [CSM] FindOrEstablishSession: No existing OperationalDeviceProxy instance found
[1658524832224] [23667:587171] CHIP: [CTL] OperationalDeviceProxy[E2E58F6F9CD07DB0:0000000000000001]: State change 1 --> 2
[1658524832224] [23667:587171] CHIP: [DIS] Resolving E2E58F6F9CD07DB0:0000000000000001 ...
[1658524832224] [23667:587171] CHIP: [DL] Resolve type=_matter._tcp name=E2E58F6F9CD07DB0-0000000000000001 interface=0
[1658524832224] [23667:587171] CHIP: [DL] Mdns : OnNewInterface hostname:E45F012EEC9F0000.local. fullname:E2E58F6F9CD07DB0-0000000000000001._matter._tcp.local. interface: 7
[1658524832225] [23667:587171] CHIP: [DL] Mdns: OnNewAddress interface: 7 ip:fe80::e65f:1ff:fe2e:ec9f
[1658524832225] [23667:587171] CHIP: [DIS] Node ID resolved for E2E58F6F9CD07DB0:0000000000000001
[1658524832225] [23667:587171] CHIP: [DIS] 	Hostname: E45F012EEC9F0000
[1658524832225] [23667:587171] CHIP: [DIS] 	IP Address #1: fe80::e65f:1ff:fe2e:ec9f
[1658524832225] [23667:587171] CHIP: [DIS] 	Port: 5540
[1658524832225] [23667:587171] CHIP: [DIS] 	Mrp Interval idle: 5000 ms
[1658524832225] [23667:587171] CHIP: [DIS] 	Mrp Interval active: 300 ms
[1658524832225] [23667:587171] CHIP: [DIS] UDP:[fe80::e65f:1ff:fe2e:ec9f%en0]:5540: new best score: 3
[1658524832225] [23667:587171] CHIP: [DIS] Checking node lookup status after 1 ms
[1658524832225] [23667:587171] CHIP: [DIS] Keeping DNSSD lookup active
[1658524832425] [23667:587171] CHIP: [DIS] Checking node lookup status after 201 ms
[1658524832426] [23667:587171] CHIP: [CTL] Updating device address to UDP:[fe80::e65f:1ff:fe2e:ec9f%en0]:5540 while in state 2
[1658524832426] [23667:587171] CHIP: [CTL] OperationalDeviceProxy[E2E58F6F9CD07DB0:0000000000000001]: State change 2 --> 3
[1658524832426] [23667:587171] CHIP: [IN] SecureSession[0x7fd3dd456420]: Allocated Type:2 LSID:23872
[1658524832426] [23667:587171] CHIP: [SC] Initiating session on local FabricIndex 1 from 0x000000000001B669 -> 0x0000000000000001
[1658524832431] [23667:587171] CHIP: [SC] Including MRP parameters
[1658524832431] [23667:587171] CHIP: [IN] Prepared unauthenticated message 0x7fd3dd456538 to 0x0000000000000000 (0)  of type 0x30 and protocolId (0, 0) on exchange 53047i with MessageCounter:225961439.
[1658524832431] [23667:587171] CHIP: [IN] Sending unauthenticated msg 0x7fd3dd456538 with MessageCounter:225961439 to 0x0000000000000000 at monotonic time:<PHONE_NUMBER>B838CC msec
[1658524832431] [23667:587171] CHIP: [SC] Sent Sigma1 msg
[1658524832432] [23667:587171] CHIP: [CTL] OperationalDeviceProxy[E2E58F6F9CD07DB0:0000000000000001]: State change 3 --> 4
[1658524832439] [23667:587172] CHIP: [EM] Received message of type 0x31 with protocolId (0, 0) and MessageCounter:76148450 on exchange 53047i
[1658524832439] [23667:587172] CHIP: [EM] Found matching exchange: 53047i, Delegate: 0x7fd3dd457690
[1658524832439] [23667:587172] CHIP: [EM] Rxd Ack; Removing MessageCounter:225961439 from Retrans Table on exchange 53047i
[1658524832439] [23667:587172] CHIP: [EM] Removed CHIP MessageCounter:225961439 from RetransTable on exchange 53047i
[1658524832439] [23667:587172] CHIP: [SC] Received Sigma2 msg
[1658524832439] [23667:587172] CHIP: [SC] Peer assigned session session ID 42875
[1658524832462] [23667:587172] CHIP: [SC] Found MRP parameters in the message
[1658524832462] [23667:587172] CHIP: [SC] Sending Sigma3
[1658524832465] [23667:587172] CHIP: [EM] Piggybacking Ack for MessageCounter:76148450 on exchange: 53047i
[1658524832465] [23667:587172] CHIP: [IN] Prepared unauthenticated message 0x7fd3dc504448 to 0x0000000000000000 (0)  of type 0x32 and protocolId (0, 0) on exchange 53047i with MessageCounter:225961440.
[1658524832465] [23667:587172] CHIP: [IN] Sending unauthenticated msg 0x7fd3dc504448 with MessageCounter:225961440 to 0x0000000000000000 at monotonic time:<PHONE_NUMBER>B838EE msec
[1658524832465] [23667:587172] CHIP: [SC] Sent Sigma3 msg
[1658524832486] [23667:587172] CHIP: [EM] Received message of type 0x40 with protocolId (0, 0) and MessageCounter:76148451 on exchange 53047i
[1658524832486] [23667:587172] CHIP: [EM] Found matching exchange: 53047i, Delegate: 0x7fd3dd457690
[1658524832486] [23667:587172] CHIP: [EM] Rxd Ack; Removing MessageCounter:225961440 from Retrans Table on exchange 53047i
[1658524832486] [23667:587172] CHIP: [EM] Removed CHIP MessageCounter:225961440 from RetransTable on exchange 53047i
[1658524832487] [23667:587172] CHIP: [SC] Success status report received. Session was established
[1658524832489] [23667:587172] CHIP: [SC] SecureSession[0x7fd3dd456420]: Moving from state 'kEstablishing' --> 'kActive'
[1658524832490] [23667:587172] CHIP: [IN] SecureSession[0x7fd3dd456420]: Activated - Type:2 LSID:23872
[1658524832490] [23667:587172] CHIP: [IN] New secure session activated for device <0000000000000001, 1>, LSID:23872 PSID:42875!
[1658524832490] [23667:587172] CHIP: [CTL] OperationalDeviceProxy[E2E58F6F9CD07DB0:0000000000000001]: State change 4 --> 5
[1658524832490] [23667:587172] CHIP: [TOO] Sending cluster (0x00000507) command (0x00000003) on endpoint 1
[1658524832490] [23667:587172] CHIP: [DMG] ICR moving to [AddingComm]
[1658524832490] [23667:587172] CHIP: [DMG] ICR moving to [AddedComma]
[1658524832490] [23667:587172] CHIP: [IN] Prepared secure message 0x7fd3dd4545d8 to 0x0000000000000001 (1)  of type 0x8 and protocolId (0, 1) on exchange 53048i with MessageCounter:65837370.
[1658524832490] [23667:587172] CHIP: [IN] Sending encrypted msg 0x7fd3dd4545d8 with MessageCounter:65837370 to 0x0000000000000001 (1) at monotonic time:<PHONE_NUMBER>B83907 msec
[1658524832490] [23667:587172] CHIP: [DMG] ICR moving to [CommandSen]
[1658524832490] [23667:587172] CHIP: [EM] Sending Standalone Ack for MessageCounter:76148451 on exchange 53047i
[1658524832490] [23667:587172] CHIP: [IN] Prepared unauthenticated message 0x700004b124e0 to 0x0000000000000000 (0)  of type 0x10 and protocolId (0, 0) on exchange 53047i with MessageCounter:225961441.
[1658524832490] [23667:587172] CHIP: [IN] Sending unauthenticated msg 0x700004b124e0 with MessageCounter:225961441 to 0x0000000000000000 at monotonic time:<PHONE_NUMBER>B83907 msec
[1658524832490] [23667:587172] CHIP: [EM] Flushed pending ack for MessageCounter:76148451 on exchange 53047i
[1658524832498] [23667:587172] CHIP: [EM] Received message of type 0x9 with protocolId (0, 1) and MessageCounter:200167494 on exchange 53048i
[1658524832498] [23667:587172] CHIP: [EM] Found matching exchange: 53048i, Delegate: 0x7fd3dc509910
[1658524832498] [23667:587172] CHIP: [EM] Rxd Ack; Removing MessageCounter:65837370 from Retrans Table on exchange 53048i
[1658524832498] [23667:587172] CHIP: [EM] Removed CHIP MessageCounter:65837370 from RetransTable on exchange 53048i
[1658524832498] [23667:587172] CHIP: [DMG] ICR moving to [ResponseRe]
[1658524832498] [23667:587172] CHIP: [DMG] InvokeResponseMessage =
[1658524832498] [23667:587172] CHIP: [DMG] {
[1658524832498] [23667:587172] CHIP: [DMG] 	suppressResponse = false,
[1658524832498] [23667:587172] CHIP: [DMG] 	InvokeResponseIBs =
[1658524832498] [23667:587172] CHIP: [DMG] 	[
[1658524832498] [23667:587172] CHIP: [DMG] 		InvokeResponseIB =
[1658524832498] [23667:587172] CHIP: [DMG] 		{
[1658524832498] [23667:587172] CHIP: [DMG] 			CommandStatusIB =
[1658524832498] [23667:587172] CHIP: [DMG] 			{
[1658524832498] [23667:587172] CHIP: [DMG] 				CommandPathIB =
[1658524832498] [23667:587172] CHIP: [DMG] 				{
[1658524832498] [23667:587172] CHIP: [DMG] 					EndpointId = 0x1,
[1658524832498] [23667:587172] CHIP: [DMG] 					ClusterId = 0x507,
[1658524832498] [23667:587172] CHIP: [DMG] 					CommandId = 0x3,
[1658524832498] [23667:587172] CHIP: [DMG] 				},
[1658524832498] [23667:587172] CHIP: [DMG]
[1658524832498] [23667:587172] CHIP: [DMG] 				StatusIB =
[1658524832498] [23667:587172] CHIP: [DMG] 				{
[1658524832498] [23667:587172] CHIP: [DMG] 					status = 0x01 (FAILURE),
[1658524832498] [23667:587172] CHIP: [DMG] 				},
[1658524832498] [23667:587172] CHIP: [DMG]
[1658524832498] [23667:587172] CHIP: [DMG] 			},
[1658524832498] [23667:587172] CHIP: [DMG]
[1658524832498] [23667:587172] CHIP: [DMG] 		},
[1658524832498] [23667:587172] CHIP: [DMG]
[1658524832498] [23667:587172] CHIP: [DMG] 	],
[1658524832498] [23667:587172] CHIP: [DMG]
[1658524832498] [23667:587172] CHIP: [DMG] 	InteractionModelRevision = 1
[1658524832498] [23667:587172] CHIP: [DMG] },
[1658524832498] [23667:587172] CHIP: [DMG] Received Command Response Status for Endpoint=1 Cluster=0x0000_0507 Command=0x0000_0003 Status=0x1
[1658524832498] [23667:587172] CHIP: [TOO] Error: IM Error 0x00000501: General error: 0x01 (FAILURE)
[1658524832498] [23667:587172] CHIP: [DMG] ICR moving to [AwaitingDe]
[1658524832498] [23667:587172] CHIP: [EM] Sending Standalone Ack for MessageCounter:200167494 on exchange 53048i
[1658524832498] [23667:587172] CHIP: [IN] Prepared secure message 0x700004b12500 to 0x0000000000000001 (1)  of type 0x10 and protocolId (0, 0) on exchange 53048i with MessageCounter:65837371.
[1658524832498] [23667:587172] CHIP: [IN] Sending encrypted msg 0x700004b12500 with MessageCounter:65837371 to 0x0000000000000001 (1) at monotonic time:<PHONE_NUMBER>B8390F msec
[1658524832498] [23667:587172] CHIP: [EM] Flushed pending ack for MessageCounter:200167494 on exchange 53048i
[1658524832498] [23667:587168] CHIP: [CTL] Shutting down the commissioner
[1658524832498] [23667:587168] CHIP: [CTL] Shutting down the controller
[1658524832498] [23667:587168] CHIP: [CTL] Shutting down the commissioner
[1658524832498] [23667:587168] CHIP: [CTL] Shutting down the controller
[1658524832498] [23667:587168] CHIP: [IN] Expiring all sessions for fabric 0x1!!
[1658524832498] [23667:587168] CHIP: [IN] SecureSession[0x7fd3dd456420]: MarkForEviction Type:2 LSID:23872
[1658524832498] [23667:587168] CHIP: [SC] SecureSession[0x7fd3dd456420]: Moving from state 'kActive' --> 'kPendingEviction'
[1658524832498] [23667:587168] CHIP: [IN] SecureSession[0x7fd3dd456420]: Released - Type:2 LSID:23872
[1658524832498] [23667:587168] CHIP: [FP] Forgetting fabric 0x1
[1658524832498] [23667:587168] CHIP: [TS] Pending Last Known Good Time: 2022-07-11T10:23:09
[1658524832498] [23667:587168] CHIP: [TS] Previous Last Known Good Time: 2022-07-11T10:23:09
[1658524832499] [23667:587168] CHIP: [TS] Reverted Last Known Good Time to previous value
[1658524832499] [23667:587168] CHIP: [CTL] Shutting down the commissioner
[1658524832499] [23667:587168] CHIP: [CTL] Shutting down the controller
[1658524832499] [23667:587168] CHIP: [IN] Expiring all sessions for fabric 0x2!!
[1658524832499] [23667:587168] CHIP: [FP] Forgetting fabric 0x2
[1658524832499] [23667:587168] CHIP: [TS] Pending Last Known Good Time: 2022-07-11T10:23:09
[1658524832499] [23667:587168] CHIP: [TS] Previous Last Known Good Time: 2022-07-11T10:23:09
[1658524832499] [23667:587168] CHIP: [TS] Reverted Last Known Good Time to previous value
[1658524832499] [23667:587168] CHIP: [CTL] Shutting down the commissioner
[1658524832499] [23667:587168] CHIP: [CTL] Shutting down the controller
[1658524832499] [23667:587168] CHIP: [IN] Expiring all sessions for fabric 0x3!!
[1658524832499] [23667:587168] CHIP: [FP] Forgetting fabric 0x3
[1658524832499] [23667:587168] CHIP: [TS] Pending Last Known Good Time: 2022-07-11T10:23:09
[1658524832499] [23667:587168] CHIP: [TS] Previous Last Known Good Time: 2022-07-11T10:23:09
[1658524832499] [23667:587168] CHIP: [TS] Reverted Last Known Good Time to previous value
[1658524832499] [23667:587168] CHIP: [CTL] Shutting down the System State, this will teardown the CHIP Stack
[1658524832499] [23667:587168] CHIP: [DMG] IM WH moving to [Uninitialized]
[1658524832499] [23667:587168] CHIP: [DMG] IM WH moving to [Uninitialized]
[1658524832499] [23667:587168] CHIP: [DMG] IM WH moving to [Uninitialized]
[1658524832499] [23667:587168] CHIP: [DMG] IM WH moving to [Uninitialized]
[1658524832499] [23667:587168] CHIP: [DMG] All ReadHandler-s are clean, clear GlobalDirtySet
[1658524832499] [23667:587168] CHIP: [BLE] CancelConnection
[1658524832499] [23667:587168] CHIP: [DL] Inet Layer shutdown
[1658524832499] [23667:587168] CHIP: [DL] BLE shutdown
[1658524832499] [23667:587168] CHIP: [DL] System Layer shutdown
[1658524832499] [23667:587168] CHIP: [TOO] Run command failure: IM Error 0x00000501: General error: 0x01 (FAILURE)

@Garik098 What server app is this?

Working fine on the tv-app


pachd Failing with Segmentation Faults

This morning, as part of looking at #6640, I tried creating one of the customer pipelines I was testing with called "cron_daily". This failed in the same way as the pipeline I initially tried creating yesterday. I then decided to try to uninstall and reinstall Pachyderm to see if that had any effect on the issue.  When I did, however, I forgot to delete the cron_daily pipeline first. So, after reinstall, that pipeline tried to start and failed in the same way again.  However, there was also a new problem that surfaced, specifically pachd started failing and restarting as well, with segmentation faults.
2021-07-29T15:17:50Z INFO PPS master: launching master process
2021-07-29T15:17:50Z INFO PPS master: processing event for "cron_daily"
2021-07-29T15:17:50Z INFO pfs.API.GetFileTAR {"request":{"file":{"commit":{"branch":{"repo":{"name":"cron_daily","type":"spec"},"name":"master"},"id":"971ea721430d4cb3b18cad1ab58e4994"},"path":"spec"}}}
2021-07-29T15:17:50Z INFO pfs.API.gopanic {"duration":0.000184446,"request":{"file":{"commit":{"branch":{"repo":{"name":"cron_daily","type":"spec"},"name":"master"},"id":"971ea721430d4cb3b18cad1ab58e4994"},"path":"spec"}}}
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x48 pc=0x1d2af4d]

goroutine 172 [running]:
github.com/pachyderm/pachyderm/v2/src/internal/transactionenv.(*TransactionEnv).WithReadContext(0xc00062d940, 0x2b81340, 0xc0004653b0, 0xc0007af190, 0xc0006d3370, 0x1)
	/Users/avigil/Pachyderm/Pachyderm_releases/pachyderm/src/internal/transactionenv/env.go:328 +0x2d
github.com/pachyderm/pachyderm/v2/src/server/pfs/server.(*driver).inspectCommit(0xc000631880, 0x2b81340, 0xc0004653b0, 0xc000391600, 0xc000000001, 0x1, 0x1, 0x0)
	/Users/avigil/Pachyderm/Pachyderm_releases/pachyderm/src/server/pfs/server/driver.go:893 +0x1c5
github.com/pachyderm/pachyderm/v2/src/server/pfs/server.(*driver).openCommit(0xc000631880, 0x2b81340, 0xc0004653b0, 0xc000391600, 0xc000755a90, 0x2, 0x2, 0x2f, 0x3, 0x18, ...)
	/Users/avigil/Pachyderm/Pachyderm_releases/pachyderm/src/server/pfs/server/driver_file.go:132 +0x166
github.com/pachyderm/pachyderm/v2/src/server/pfs/server.(*driver).getFile(0xc000631880, 0x2b81340, 0xc0004653b0, 0xc0002dd3b0, 0x7, 0x1, 0x0, 0x4140bd)
	/Users/avigil/Pachyderm/Pachyderm_releases/pachyderm/src/server/pfs/server/driver_file.go:186 +0x18d
github.com/pachyderm/pachyderm/v2/src/server/pfs/server.(*apiServer).GetFileTAR.func3(0xc00071cc30, 0x0, 0x0)
	/Users/avigil/Pachyderm/Pachyderm_releases/pachyderm/src/server/pfs/server/api_server.go:502 +0x90
github.com/pachyderm/pachyderm/v2/src/internal/storage/metrics.ReportRequestWithThroughput.func1(0xc038cf87898cfc04, 0xefde386)
	/Users/avigil/Pachyderm/Pachyderm_releases/pachyderm/src/internal/storage/metrics/metrics.go:68 +0x4d
github.com/pachyderm/pachyderm/v2/src/internal/storage/metrics.ReportRequest(0xc0007af5c0, 0xc0007af5a0, 0x1, 0x1, 0x0, 0x0)
	/Users/avigil/Pachyderm/Pachyderm_releases/pachyderm/src/internal/storage/metrics/metrics.go:54 +0x170
github.com/pachyderm/pachyderm/v2/src/internal/storage/metrics.ReportRequestWithThroughput(0xc0007af658, 0xefc9a1a, 0x3c14d00)
	/Users/avigil/Pachyderm/Pachyderm_releases/pachyderm/src/internal/storage/metrics/metrics.go:67 +0x170
github.com/pachyderm/pachyderm/v2/src/server/pfs/server.(*apiServer).GetFileTAR(0xc000445d10, 0xc000391dc0, 0x2b975e8, 0xc0003915c0, 0x0, 0x0)
	/Users/avigil/Pachyderm/Pachyderm_releases/pachyderm/src/server/pfs/server/api_server.go:500 +0x165
github.com/pachyderm/pachyderm/v2/src/server/pfs/server.(*validatedAPIServer).GetFileTAR(0xc00000ddb8, 0xc000391dc0, 0x2b975e8, 0xc0003915c0, 0x241d360, 0x3c44cf8)
	/Users/avigil/Pachyderm/Pachyderm_releases/pachyderm/src/server/pfs/server/val_server.go:179 +0x7a
github.com/pachyderm/pachyderm/v2/src/internal.GetPipelineDetails(0x2b81340, 0xc0004653b0, 0x7f44b9cac958, 0xc00000ddb8, 0xc00038c3f0, 0x0, 0x0)
	/Users/avigil/Pachyderm/Pachyderm_releases/pachyderm/src/internal/internal.go:81 +0x168
github.com/pachyderm/pachyderm/v2/src/server/pps/server.(*ppsMaster).newPipelineOp(0xc0006a4420, 0x2b81298, 0xc000530680, 0xc00064bf00, 0xa, 0x0, 0x0, 0x0)
	/Users/avigil/Pachyderm/Pachyderm_releases/pachyderm/src/server/pps/server/pipeline_controller.go:142 +0x496
github.com/pachyderm/pachyderm/v2/src/server/pps/server.(*ppsMaster).step(0xc0006a4420, 0xc00064bf00, 0xa, 0x0, 0x0, 0x0, 0x0)
	/Users/avigil/Pachyderm/Pachyderm_releases/pachyderm/src/server/pps/server/pipeline_controller.go:98 +0x38c
github.com/pachyderm/pachyderm/v2/src/server/pps/server.(*ppsMaster).attemptStep.func1(0xc0003f7b60, 0x4eb946)
	/Users/avigil/Pachyderm/Pachyderm_releases/pachyderm/src/server/pps/server/master.go:187 +0x52
github.com/pachyderm/pachyderm/v2/src/internal/backoff.RetryUntilCancel(0x2b812d0, 0xc000058120, 0xc0007afc30, 0x2b4a7e0, 0xc0003f7b60, 0xc0007afc48, 0x1, 0x2)
	/Users/avigil/Pachyderm/Pachyderm_releases/pachyderm/src/internal/backoff/retry.go:129 +0x56
github.com/pachyderm/pachyderm/v2/src/internal/backoff.RetryNotify(...)
	/Users/avigil/Pachyderm/Pachyderm_releases/pachyderm/src/internal/backoff/retry.go:118
github.com/pachyderm/pachyderm/v2/src/server/pps/server.(*ppsMaster).attemptStep(0xc0006a4420, 0x2b81298, 0xc000198c00, 0xc000465170, 0x2, 0xc0005ad001)
	/Users/avigil/Pachyderm/Pachyderm_releases/pachyderm/src/server/pps/server/master.go:185 +0x12f
github.com/pachyderm/pachyderm/v2/src/server/pps/server.(*ppsMaster).run(0xc0006a4420)
	/Users/avigil/Pachyderm/Pachyderm_releases/pachyderm/src/server/pps/server/master.go:159 +0x352
github.com/pachyderm/pachyderm/v2/src/server/pps/server.(*apiServer).master.func1(0x0, 0x0)
	/Users/avigil/Pachyderm/Pachyderm_releases/pachyderm/src/server/pps/server/master.go:120 +0x19e
github.com/pachyderm/pachyderm/v2/src/internal/backoff.RetryUntilCancel(0x2b812d0, 0xc000058120, 0xc0007aff88, 0x2b4a7e0, 0xc0006a4480, 0x28b2af8, 0x0, 0x0)
	/Users/avigil/Pachyderm/Pachyderm_releases/pachyderm/src/internal/backoff/retry.go:129 +0x56
github.com/pachyderm/pachyderm/v2/src/internal/backoff.RetryNotify(...)
	/Users/avigil/Pachyderm/Pachyderm_releases/pachyderm/src/internal/backoff/retry.go:118
github.com/pachyderm/pachyderm/v2/src/server/pps/server.(*apiServer).master(0xc000694000)
	/Users/avigil/Pachyderm/Pachyderm_releases/pachyderm/src/server/pps/server/master.go:109 +0x25f
created by github.com/pachyderm/pachyderm/v2/src/server/pps/server.NewAPIServer
	/Users/avigil/Pachyderm/Pachyderm_releases/pachyderm/src/server/pps/server/server.go:44 +0x8ee

AB#15

@PFedak would you mind taking a look at this?

@brycemcanally @brendoncarroll is it possible this is going to be fixed by some of the connection changes you're making?

It looks like the serviceEnv in the TransactionEnv is not getting initialized?

I have not been able to reproduce this in Beta 5. Closing.


Update README.md

Update typescript import syntax.

Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. In order for us to review and merge your code, please sign up at https://code.facebook.com/cla - and if you have received this in error or have any questions, please drop us a line at<EMAIL_ADDRESS>Thanks!

I'm guessing this has been abandoned - we do need folks to sign the CLA, for what it's worth.

Yep sorry, mistake on the PR. Deleting.


Add outlines component

I see new cool drei thing I port it

I really need this, looking forward to it getting merged 🥇


Update sikit-learn to version 0.17

Datalab includes version 0.16.1 although version 0.17 (November 2015) is available.
There are API changes between these 2 versions (http://scikit-learn.org/stable/whats_new.html) that make it cumbersome to share code.
Would you update scikit-learn to the latest version?

:+1:

The next release will have most packages updated.

Fixed in 6bbe1fde


KAFKA-17430: Move RequestChannel.Metrics/RequestMetrics to server module

Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

None of the test failures are related, merging to trunk

Hey. We just ran into a potential memory leak on trunk that may be related to this change. I'll dig more into it tomorrow, but maybe you have an idea if this change could be related.

Ah yes, I can immediately see the issue! DeprecatedRequestRateKey is used as a key in a Map and that class does not override hashcode(). My bad, I'll open a PR, thanks for catching this.


Tradeblock case study

Brad: Looks like we have an extra space on the Tradeblock Founders Story page, after "Company Website"

I'm fine with the row spacing as is.


Don't crash on missing scrollView in deinit

Fixes #1

Thanks for this PR @dvdsgl, this issue was solved in other PR 👍


Filter dropdown and toggle column dropdown in mobile

Package
filament/tables
Package Version
2.0
Laravel Version
9.19
Livewire Version
No response
PHP Version
8.1
Problem description
Table filter and toggleable dropdown not showing properly on mobile view.

Expected behavior
to show dropdown as visible (responsive) for mobile
Steps to reproduce
demo from docs
Reproduction repository
https://demo.filamentphp.com/shop/orders
Relevant log output
No response

Duplicate of #3418


[Documentation] Not functional when README instructions followed precisely, with most-recent Godot 4 build

As a new user to Godot, I would like an option to be able to clone your repository and get your addon working, from scratch, as a "first user experience" (FUE) for a new project in Godot 4, without any prior knowledge of Godot.
Currently, I am unable to do this, or I am confused.

Hello. What exactly do you not understand?

 I didn't consider that.
I'm not sure what I don't understand. I just worded my issue abstractly,
and I realize now that it may have been confusing.
At the time of the creation of my issue, a person with zero prior knowledge
of Godot 4.x is unable to follow your installation instructions.
Hopefully that made more sense.
You've got a great product, I'm certain. It could also serve as a tutorial
for installation and enablement of a Godot 4.x addon.
On Sat, Mar 5, 2022, 8:20 PM Mansur Isaev @.***> wrote:

Hello. What exactly do you not understand?
—
Reply to this email directly, view it on GitHub
https://github.com/4d49/godot-logger/issues/1#issuecomment-1059892319,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAKRQ33YGO4M77Z2KHMLZJTU6QW67ANCNFSM5PFW3U7Q
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
 I didn't consider that.

I don't speak English. If you have a desire, you could help translate the documentation into english correctly.

At the time of the creation of my issue, a person with zero prior knowledge of Godot 4.x is unable to follow your installation instructions.

Try using the addon again. Perhaps your problems were related to a bug that I fixed in the last patch.

There is no LogOutput node but LoggerOutput and I first thought it will log to output window, but it's a small window ON THE SCENE which hold the log data, quite like the (in)famous quake2 console.
Even with a good deal of Godot experience, the instructions in the README are pretty light and incorrect. Here are how to use it:

create an addons folder in your project main folder if it doesn't already exists,
put the whole godot-logger project inside which contains icons, scripts folders and plugin.cfg and plugin.gd files,
create a scene in your project,
add LoggerOutput node somewhere and in 2D view, resize it and move it where you want,
when you run your project, every Log. call will add a message in the small log window

Log to a configured output like Log4j would have been far much better and useful.


Postgres revert role privileges

Reverts the change to the postgres role from https://github.com/openmicroscopy/infrastructure/commit/cd92c3d2bfe7f52bb65d0f822db30c9669d8fd74#diff-5c81521b75eb3f697f59fd8f1d245303 and replaces it with a new optional parameter. Also adds a vagrant test including some asserts.

Very nice test! :+1: from me. @aleksandra-tarkowska : anything from your side?

all good, ci requires hudson role anyway


Support script functions in ABI generations and documentation generator

This is the first of three PRs to add support for public(script) so that the Diem Framework can use it.
This PR has two main commits:

The base commit adds support for the different function visibilities to the documentation generator. These changes are pretty small.
The top commit updates the ABI generation to support script functions, and more than one script function declared per-module. The details of this are:
- A directory is created for each module in which there is a script function (public(script)). An .abi file is created in this directory for each script function in this module. The ABI file name is the name of the script function name.
- If a module is a script module (i.e., what we have today). Then only a single .abi file is created and no directory is created.
- The ScriptABI struct has been updated in a non-backwards compatible way, however I don't believe this should be an issue since the TransactionScript variant holds the old data for a transaction script (so old serialized ABIs can be deserialized with this type). The ScriptFunction variant holds the script ABI for a script function.

At the moment, the transaction builders have been stubbed out and ScriptABI has largely been replaced by TransactionScriptABI for this PR. The next PR after this will add support for script function ABIs, and will change these back to ScriptABI and update the transaction builder generation logic to support both. TODOs have been left in most place to mark the entrance points where we simplify and convert from a ScriptABI to a TransactionScriptABI.

/land

:broken_heart: Test Failed - ci-test-success

/land


Wildcard match is not working

Styles containing wildcards are not shown at all in the extension's dropdown.
Examples:

http://stylebot.me/styles/7004 (*.slack.com, **.slack.com**): nothing shows up on https://xxyyzz.slack.com/messages/general

http://stylebot.me/styles/4000 (mail.google.com**) does not show up either

I'm experiencing something similar, but with the regex URL matching: ^(.)git.domain.com(.)merge_requests/(.*)$
I'm trying to style the Merge Request page in a gitlab deployment. To do this I use a very specific regex to match the page. However, when I go to the page initially the style is not applied. I have to refresh for it to apply.
But that's not the big thing that bothers me... the real problem is that even if I navigate away from that URL to another page on the site, the style is still applied! I have to refresh that page for the style to be removed.


syntax for keys

Can You please provide documentation and/or examples for the correct syntax for typical keys, including SumIndexFields and other options. Many thanks!

Here is an example
table 71000018 MyTable
{
    fields
    {
        field(1;Id;Code[10]) {}
        field(2;Amount;Decimal) {}
        field(3;"Amount (LCY)";Decimal) {}
    }
    Keys
    {
        Key(1;KeyName;Id,Amount){
            Clustered = true;
            SumIndexFields = Amount, "Amount (LCY)";
        }
    }
}

Thanks for helping!

Please help me.
I'm a new developer for Extension 2.0.
Example: 1. Add more file Offset Type into Table 17 G/L Entry. -> It is OK.
2. I need add more key:
keys
{
key(Key9;"Transaction No.","Document No.","Offset Type")
{
}
}
But It isn't OK.
So how to do it. OR this isn't supported.
From the help link. "You can add table keys, but you cannot delete or modify existing keys".