GH-39214: [Java] Support reproducible build

Rationale for this change
This PR add reproducible builds support.
Are these changes tested?
I tested the builds are reproducible on arrow-vector, arrow-memory, ... using mvn clean verify artifact:compare.
Are there any user-facing changes?
No

Closes: #39214

@lidavidm let me check why GH Action is not happy 😃

@github-actions crossbow submit java

FYI, I'm resuming work on this PR:

checking the build failure on CI
checking to add a GH Action workflow to verify

checking to add a GH Action workflow to verify

It might be best to add it to an existing workflow, or again, adding it to the release verification script even (what do you think @assignUser?)

checking to add a GH Action workflow to verify

It might be best to add it to an existing workflow, or again, adding it to the release verification script even (what do you think @assignUser?)

@lidavidm it makes sense, I do like this. Thanks !

How exactly does this work, it compares the current build against a reference build? How does that work for dev versions?
We do have binary verification scripts so it would make sense to add it there, that would automatically also run it. dev/release/verify-release-candidate.sh with `TEST_JARS=1' is run by the jar binary verification script (this downloads previously build nightly jars iirc) cc @raulcd who is a bit more familiar with the release scripts

@lidavidm yup, it's what I plan to do (and I used while working on this PR 😄 ).
First I will fix the failing checks (AMD64 Conda Integration Test, etc).

Error:  Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin:3.4.1:enforce (enforce-maven-version) on project arrow-bom:
Error:  Rule 0: org.apache.maven.enforcer.rules.version.RequireMavenVersion failed with message:
Error:  Detected Maven Version: 3.5.0 is not in the allowed range [3.6.3,).
Error:  -> [Help 1]

That's due to the Apache POM update. I will propose fix as part of this PR.

I fixed the enforcer range by setting minimalMavenBuildVersion.
Let me take a look on the Merge Script workflows.

When is <project.build.outputTimestamp> updated?
Does mvn versions:set update it?
It seems that our dev/release/01-prepare.sh updates it: https://github.com/apache/arrow/actions/runs/7263564652/job/19789165030?pr=39215#step:7:24478

https://maven.apache.org/guides/mini/guide-reproducible-builds.html#faq

if you have a custom release process tooling, you'll need to add the feature to your release tooling. Notice that if you're using versions-maven-plugin in custom release scripts, starting with release 2.9.0, versions:set goal updates the property.

It seems that updated value is always the current time: https://github.com/mojohaus/versions/pull/522/files#diff-544db8b7e4906f57cb6c1bd43ba1100760f876da22b46b2ca381ab374cb169faR530

How about this for "Dev /Source Release and Merge Script" failures?
diff --git a/dev/release/01-prepare-test.rb b/dev/release/01-prepare-test.rb
index 8fb23f45f0..f4bf01f1f6 100644
--- a/dev/release/01-prepare-test.rb
+++ b/dev/release/01-prepare-test.rb
@@ -264,18 +264,17 @@ class PrepareTest < Test::Unit::TestCase
     end

     Dir.glob("java/**/pom.xml") do |path|
-      version = "<version>#{@snapshot_version}</version>"
-      lines = File.readlines(path, chomp: true)
-      target_lines = lines.grep(/#{Regexp.escape(version)}/)
-      hunks = []
-      target_lines.each do |line|
-        new_line = line.gsub(@snapshot_version) do
-          @release_version
+      hunks = generate_hunks(File.readlines(path, chomp: true)) do |line|
+        if line.include?("<version>#{@snapshot_version}</version>")
+          new_line = line.gsub(@snapshot_version) do
+            @release_version
+          end
+          [line, new_line]
+        elsif line.include?("<project.build.outputTimestamp>")
+          [line, normalize_pom_xml_output_timestamp(line)]
+        else
+          [nil, nil]
         end
-        hunks << [
-          "-#{line}",
-          "+#{new_line}",
-        ]
       end
       expected_changes << {hunks: hunks, path: path}
     end
diff --git a/dev/release/post-11-bump-versions-test.rb b/dev/release/post-11-bump-versions-test.rb
index 4b6933d610..08a900f71c 100644
--- a/dev/release/post-11-bump-versions-test.rb
+++ b/dev/release/post-11-bump-versions-test.rb
@@ -244,37 +244,19 @@ class PostBumpVersionsTest < Test::Unit::TestCase
       end

       import_path = "github.com/apache/arrow/go/v#{@snapshot_major_version}"
-      hunks = []
       if release_type == :major
-        lines = File.readlines(path, chomp: true)
-        target_lines = lines.each_with_index.select do |line, i|
-          line.include?(import_path)
-        end
-        next if target_lines.empty?
-        n_context_lines = 3 # The default of Git's diff.context
-        target_hunks = [[target_lines.first[0]]]
-        previous_i = target_lines.first[1]
-        target_lines[1..-1].each do |line, i|
-          if i - previous_i < n_context_lines
-            target_hunks.last << line
-          else
-            target_hunks << [line]
-          end
-          previous_i = i
-        end
-        target_hunks.each do |lines|
-          hunk = []
-          lines.each do |line,|
-            hunk << "-#{line}"
-          end
-          lines.each do |line|
+        hunks = generate_hunks(File.readlines(path, chomp: true)) do |line|
+          if line.include?(import_path)
             new_line = line.gsub("v#{@snapshot_major_version}") do
               "v#{@next_major_version}"
             end
-            hunk << "+#{new_line}"
+            [line, new_line]
+          else
+            [nil, nil]
           end
-          hunks << hunk
         end
+      else
+        hunks = []
       end
       if path == "go/parquet/writer_properties.go"
         hunks << [
@@ -287,18 +269,17 @@ class PostBumpVersionsTest < Test::Unit::TestCase
     end

     Dir.glob("java/**/pom.xml") do |path|
-      version = "<version>#{@snapshot_version}</version>"
-      lines = File.readlines(path, chomp: true)
-      target_lines = lines.grep(/#{Regexp.escape(version)}/)
-      hunks = []
-      target_lines.each do |line|
-        new_line = line.gsub(@snapshot_version) do
-          @next_snapshot_version
+      hunks = generate_hunks(File.readlines(path, chomp: true)) do |line|
+        if line.include?("<version>#{@snapshot_version}</version>")
+          new_line = line.gsub(@snapshot_version) do
+            @next_snapshot_version
+          end
+          [line, new_line]
+        elsif line.include?("<project.build.outputTimestamp>")
+          [line, normalize_pom_xml_output_timestamp(line)]
+        else
+          [nil, nil]
         end
-        hunks << [
-          "-#{line}",
-          "+#{new_line}",
-        ]
       end
       expected_changes << {hunks: hunks, path: path}
     end
diff --git a/dev/release/test-helper.rb b/dev/release/test-helper.rb
index 3b2c3aa6e5..4238a534d1 100644
--- a/dev/release/test-helper.rb
+++ b/dev/release/test-helper.rb
@@ -83,15 +83,59 @@ module GitRunnable
       when /\A@@/
         in_hunk = true
         diffs.last[:hunks] << []
-      when /\A[-+]/
+      when /\A-/
         next unless in_hunk
         diffs.last[:hunks].last << line.chomp
+      when /\A\+/
+        next unless in_hunk
+        diffs.last[:hunks].last << normalize_added_line(line.chomp)
       end
     end
     diffs.sort_by do |diff|
       diff[:path]
     end
   end
+
+  def generate_hunks(lines)
+    git_diff_context = 3 # The default of Git's diff.context
+    max_lines_for_same_hunk = git_diff_context * 2 + 1
+    previous_i = nil
+    grouped_change_blocks = []
+    lines.each_with_index do |line, i|
+      deleted, added = yield(line)
+      next if deleted.nil? and added.nil?
+      if previous_i.nil? or (i - previous_i) > max_lines_for_same_hunk
+        grouped_change_blocks << []
+      end
+      if i - 1 != previous_i
+        grouped_change_blocks.last << []
+      end
+      grouped_change_blocks.last.last << [deleted, added]
+      previous_i = i
+    end
+    grouped_change_blocks.collect do |change_blocks|
+      hunk = []
+      change_blocks.each do |continuous_changes|
+        continuous_changes.each do |deleted, _|
+          hunk << "-#{deleted}" if deleted
+        end
+        continuous_changes.each do |_, added|
+          hunk << "+#{added}" if added
+        end
+      end
+      hunk
+    end
+  end
+
+  def normalize_pom_xml_output_timestamp(line)
+    line.gsub(/<project\.build\.outputTimestamp>.+?</) do
+      "<project.build.outputTimestamp>1970-01-01T00:00:00Z<"
+    end
+  end
+
+  def normalize_added_line(line)
+    normalize_pom_xml_output_timestamp(line)
+  end
 end

 module VersionDetectable

When is <project.build.outputTimestamp> updated? Does mvn versions:set update it?
It seems that our dev/release/01-prepare.sh updates it: https://github.com/apache/arrow/actions/runs/7263564652/job/19789165030?pr=39215#step:7:24478

outputTimestamp should be always the same to guarantee the same artifact accross build. I'm doing a pass on actions to be sure we are clean here.

It seems that updated value is always the current time: https://github.com/mojohaus/versions/pull/522/files#diff-544db8b7e4906f57cb6c1bd43ba1100760f876da22b46b2ca381ab374cb169faR530

On a specific version, the outputTimestamp has to be the same. So settings the outputTimestamp when using verisons:set is fine. The most important is to have a "stable" outputTimestamp across builds of the same version.

How about this for "Dev /Source Release and Merge Script" failures?
diff --git a/dev/release/01-prepare-test.rb b/dev/release/01-prepare-test.rb
index 8fb23f45f0..f4bf01f1f6 100644
--- a/dev/release/01-prepare-test.rb
+++ b/dev/release/01-prepare-test.rb
@@ -264,18 +264,17 @@ class PrepareTest < Test::Unit::TestCase
     end

     Dir.glob("java/**/pom.xml") do |path|
-      version = "<version>#{@snapshot_version}</version>"
-      lines = File.readlines(path, chomp: true)
-      target_lines = lines.grep(/#{Regexp.escape(version)}/)
-      hunks = []
-      target_lines.each do |line|
-        new_line = line.gsub(@snapshot_version) do
-          @release_version
+      hunks = generate_hunks(File.readlines(path, chomp: true)) do |line|
+        if line.include?("<version>#{@snapshot_version}</version>")
+          new_line = line.gsub(@snapshot_version) do
+            @release_version
+          end
+          [line, new_line]
+        elsif line.include?("<project.build.outputTimestamp>")
+          [line, normalize_pom_xml_output_timestamp(line)]
+        else
+          [nil, nil]
         end
-        hunks << [
-          "-#{line}",
-          "+#{new_line}",
-        ]
       end
       expected_changes << {hunks: hunks, path: path}
     end
diff --git a/dev/release/post-11-bump-versions-test.rb b/dev/release/post-11-bump-versions-test.rb
index 4b6933d610..08a900f71c 100644
--- a/dev/release/post-11-bump-versions-test.rb
+++ b/dev/release/post-11-bump-versions-test.rb
@@ -244,37 +244,19 @@ class PostBumpVersionsTest < Test::Unit::TestCase
       end

       import_path = "github.com/apache/arrow/go/v#{@snapshot_major_version}"
-      hunks = []
       if release_type == :major
-        lines = File.readlines(path, chomp: true)
-        target_lines = lines.each_with_index.select do |line, i|
-          line.include?(import_path)
-        end
-        next if target_lines.empty?
-        n_context_lines = 3 # The default of Git's diff.context
-        target_hunks = [[target_lines.first[0]]]
-        previous_i = target_lines.first[1]
-        target_lines[1..-1].each do |line, i|
-          if i - previous_i < n_context_lines
-            target_hunks.last << line
-          else
-            target_hunks << [line]
-          end
-          previous_i = i
-        end
-        target_hunks.each do |lines|
-          hunk = []
-          lines.each do |line,|
-            hunk << "-#{line}"
-          end
-          lines.each do |line|
+        hunks = generate_hunks(File.readlines(path, chomp: true)) do |line|
+          if line.include?(import_path)
             new_line = line.gsub("v#{@snapshot_major_version}") do
               "v#{@next_major_version}"
             end
-            hunk << "+#{new_line}"
+            [line, new_line]
+          else
+            [nil, nil]
           end
-          hunks << hunk
         end
+      else
+        hunks = []
       end
       if path == "go/parquet/writer_properties.go"
         hunks << [
@@ -287,18 +269,17 @@ class PostBumpVersionsTest < Test::Unit::TestCase
     end

     Dir.glob("java/**/pom.xml") do |path|
-      version = "<version>#{@snapshot_version}</version>"
-      lines = File.readlines(path, chomp: true)
-      target_lines = lines.grep(/#{Regexp.escape(version)}/)
-      hunks = []
-      target_lines.each do |line|
-        new_line = line.gsub(@snapshot_version) do
-          @next_snapshot_version
+      hunks = generate_hunks(File.readlines(path, chomp: true)) do |line|
+        if line.include?("<version>#{@snapshot_version}</version>")
+          new_line = line.gsub(@snapshot_version) do
+            @next_snapshot_version
+          end
+          [line, new_line]
+        elsif line.include?("<project.build.outputTimestamp>")
+          [line, normalize_pom_xml_output_timestamp(line)]
+        else
+          [nil, nil]
         end
-        hunks << [
-          "-#{line}",
-          "+#{new_line}",
-        ]
       end
       expected_changes << {hunks: hunks, path: path}
     end
diff --git a/dev/release/test-helper.rb b/dev/release/test-helper.rb
index 3b2c3aa6e5..4238a534d1 100644
--- a/dev/release/test-helper.rb
+++ b/dev/release/test-helper.rb
@@ -83,15 +83,59 @@ module GitRunnable
       when /\A@@/
         in_hunk = true
         diffs.last[:hunks] << []
-      when /\A[-+]/
+      when /\A-/
         next unless in_hunk
         diffs.last[:hunks].last << line.chomp
+      when /\A\+/
+        next unless in_hunk
+        diffs.last[:hunks].last << normalize_added_line(line.chomp)
       end
     end
     diffs.sort_by do |diff|
       diff[:path]
     end
   end
+
+  def generate_hunks(lines)
+    git_diff_context = 3 # The default of Git's diff.context
+    max_lines_for_same_hunk = git_diff_context * 2 + 1
+    previous_i = nil
+    grouped_change_blocks = []
+    lines.each_with_index do |line, i|
+      deleted, added = yield(line)
+      next if deleted.nil? and added.nil?
+      if previous_i.nil? or (i - previous_i) > max_lines_for_same_hunk
+        grouped_change_blocks << []
+      end
+      if i - 1 != previous_i
+        grouped_change_blocks.last << []
+      end
+      grouped_change_blocks.last.last << [deleted, added]
+      previous_i = i
+    end
+    grouped_change_blocks.collect do |change_blocks|
+      hunk = []
+      change_blocks.each do |continuous_changes|
+        continuous_changes.each do |deleted, _|
+          hunk << "-#{deleted}" if deleted
+        end
+        continuous_changes.each do |_, added|
+          hunk << "+#{added}" if added
+        end
+      end
+      hunk
+    end
+  end
+
+  def normalize_pom_xml_output_timestamp(line)
+    line.gsub(/<project\.build\.outputTimestamp>.+?</) do
+      "<project.build.outputTimestamp>1970-01-01T00:00:00Z<"
+    end
+  end
+
+  def normalize_added_line(line)
+    normalize_pom_xml_output_timestamp(line)
+  end
 end

 module VersionDetectable

Yeah, as said on a comment, I fixed the maven enforcer issue, I'm not on the merge action issue (testing locally).

Yeah, as said on a comment, I fixed the maven enforcer issue, I'm not on the merge action issue (testing locally).

"the maven enforcer issue" is https://github.com/apache/arrow/pull/39215#issuecomment-1862842437 , right?
I'm focusing on "Dev / Source Release and Merge Script on ubuntu-latest" CI job https://github.com/apache/arrow/actions/runs/7263564652/job/19789165030?pr=39215 not "the maven enforcer issue".

@kou Maven enforcer fix is part of this PR: https://github.com/apache/arrow/pull/39215/files#diff-d8225ebcfc11b480a6e4f54e183b67c3ead51635a167c106d928c2abf1f9ef66R31 and https://github.com/apache/arrow/pull/39215/files#diff-65ce66a6aeda30354aedbae081d0411a4ae6561f9d4745b86117ea7e3eb1839aR29
I'm on the "Release and Merge script" investigation right now 😄

I'm on the "Release and Merge script" investigation right now 😄

https://github.com/apache/arrow/pull/39215#issuecomment-1863659173 will fix it.

Thanks. Let me try.

@github-actions crossbow submit java

@github-actions crossbow submit java

Error:  Failed to execute goal org.apache.maven.plugins:maven-assembly-plugin:3.6.0:single (default-cli) on project arrow-bom: Error reading assemblies: No assembly descriptors found. -> [Help 1]

hmm

Weird. Let me check.

@lidavidm the assembly plugin failed on the BoM. I'm checking.

@jbonofre the crossbow task uses * to match string patterns. You can use *java* and it will work

@raulcd thanks, my bad (typo mistake 😄 )

@github-actions crossbow submit java

I will complete the pr tomorrow (finishing Apache Karaf release right now ;)).

@github-actions crossbow submit java

OK, I understand what happens with ci/scripts/java_full_build.sh script: it explicitly call assembly:single goal. I'm fixing that :)

@github-actions crossbow submit java

@github-actions crossbow submit java

@lidavidm I'm investigating why GH Actions are not happy now (weird). Sorry for the delay.

@lidavidm do you have an idea why C++ / AMD64 Conda C++ AVX2, Java JNI / AMD64 manylinux2014 Kava JNI, etc jobs are failing ?
It looks weird to me as it seems related to docker container execution.

@github-actions crossbow submit java

Hmm well Archery doesn't like me but it seems CI still has a few issues even after a re-run.

@lidavidm yup, to be honest, I don't know why it's failing 😄 I will probably try on main branch to compare.
I will do a new pass again, maybe I missed something 😄

@assignUser Could you take a look at https://github.com/apache/arrow/pull/39215#issuecomment-1900481478 and https://github.com/apache/arrow/pull/39215#issuecomment-1900482331 ?
#39610 is related.

@kou hm weird asf membership is public for David so the bot should pick it up... if this keeps happening we may need to add a non gh api based method to identify committers (e.g. committer list, IIRC we have a yaml one around somehwere right?)

I fixed my membership after that. You may want to update the bot's error message to tell people what to do, I only knew because I happened to see someone else ask the same question in a private channel.

I'm rebasing and doing new tests on this one.

@github-actions crossbow submit java

@lidavidm as I'm back on Arrow, I'm resuming several PRs/works I have in progress 😄 Thanks !

@jbonofre need any help here?

I'm back on Arrow. I will rebase and retest this PR.

We're moving java/ to https://github.com/apache/arrow-java .
Could you open a new PR in apache/arrow-java?


nodejs-polars 0.6 npm package is broken

When I add nodejs-polars to my package json it for some reasons asks:
? Please choose a version of "nodejs-polars-android-arm64" from this list: (Use arrow keys)
❯ 0.5.4
  0.5.3
  0.5.2
  0.5.1
  0.5.0

It looks really strange as I have regular Linux Mint 21 there. While I have no issues like this with 0.5.4 version

This should be fixed on the latest version


Added Coloroad State University to the domain list

@aalamsety According to the rules, I can not add this unievrsity to the list, because it is 100% online and offers eight-weeks long courses, instead of long-term ones.
I have to close the request without merging. Please ensure you are familiar with this repository rules located at the bottom of this page. You can submit a new request with correct information or reopen this request and comment if I am mistaken. Thank you for the understanding!


DateTimePicker in modal window

Hello @kuhnroyal ! I have some problems using this DateTimePicker v3.1.0 in Bootstrap Modal window. (I use Angular 8)
The first problem that I have to add to my styles.scss this line
.cdk-overlay-container{position: relative; z-index: 99999 !important }
I need it to display DateTimePicker in front of modal.
The second problem is when try to choose hours and minutes the date is changing.
And when I try to pick some hours it picks the (hours - 3)

P.S. This widget is breathtaking.

I found that the problem was in this provider
provide: MAT_MOMENT_DATE_ADAPTER_OPTIONS,
useValue: {
useUtc: true
}
When I set it to false I can choose date and time almost correctly. But when I choose for example 15:00 it sets automatically to 12:00 (3 hours offset). And I found this solution at stackoverflow
https://stackoverflow.com/questions/48710053/day-incorrect-in-angular-material-datepicker
Now I am going to test the solution.

I found solution!
fixDate(d: Date): Date {
d.setHours(d.getHours() - d.getTimezoneOffset() / 60);
return d;
}
Orginal answer: https://stackoverflow.com/questions/44296931/ngx-bootstrap-timepicker-time-zone-offset-causing-sql-to-save-wrong-time

I decided to refuse this widget till better times.


Support NPM library loading in the evaluator

Need to support the ability to load libraries from NPM packages in the evaluator

Included in 2.3.0


UCAN 1.0-RC.1

Should we close this in favor of the test being moved to rs-ucan? https://github.com/fission-codes/rs-ucan/commit/6e9131c2492c4105c27749f4937f5973b075a55b#diff-ddd02e63303bee6ac70bb11c3e11f325550ca6431bbc18a94ec4981624077e37R267

@matheus23 good point!


Separate pool parsing from pool auto-allocation

In default ipam driver. Also improve error message
in case no good pool is found

Fixes #951
Signed-off-by: Alessandro Boch<EMAIL_ADDRESS>

LGTM


Return correct block info while forking

Which component is your bug related to?
Forge
Foundry Version
0.7.1
What operating system are you using?
MacOS
What system architecture are you using?
arm
What happened
When a state is forked in a test, get_block_timestamp returns 0 even if block_id is set to the Latest.
We should improve get_cheated_exec_info_ptr in the execution_info.rs to use block info from the fork
Trace
No response
Is there an existing issue for this?

[x] I have searched the existing issues and verified no issue exits for this problem.

Shouldn't this issue only be linked to Cheatnet?


Segmentation fault and budget exhausted

Bug description
I left a handful of application pods with istio-proxy sidecars running for a few days, and the istio-proxy containers had all thrown segmentation faults at different times. One thing that I noticed was that the app node that hosted these pods was at 85% disk space used on /var/lib/docker while another app node without disk space issues that hosted another set of pods with istio-proxy sidecars did not experience restarts.
I assumed that the disk space issues may have caused the segmentation fault in the istio-proxy code, and resolved the disk space issues.  A couple of days later, I'm still seeing segmentation faults pop up on istio-proxy sidecars on pods hosted on the same app node.
 This configuration will be removed from Envoy soon. Please see https://github.com/envoyproxy/envoy/blob/master/DEPRECATED.md for details.
[2019-04-15 13:04:16.606][89][warning][misc] [external/envoy/source/common/protobuf/utility.cc:129] Using deprecated option 'envoy.api.v2.Cluster.hosts'. This configuration will be removed from Envoy soon. Please see https://github.com/envoyproxy/envoy/blob/master/DEPRECATED.md for details.
[2019-04-15 13:04:16.606][89][warning][misc] [external/envoy/source/common/protobuf/utility.cc:129] Using deprecated option 'envoy.api.v2.Cluster.hosts'. This configuration will be removed from Envoy soon. Please see https://github.com/envoyproxy/envoy/blob/master/DEPRECATED.md for details.
[2019-04-15 13:04:16.606][89][warning][misc] [external/envoy/source/common/protobuf/utility.cc:129] Using deprecated option 'envoy.api.v2.Cluster.hosts'. This configuration will be removed from Envoy soon. Please see https://github.com/envoyproxy/envoy/blob/master/DEPRECATED.md for details.
[2019-04-15 13:04:16.606][89][warning][misc] [external/envoy/source/common/protobuf/utility.cc:129] Using deprecated option 'envoy.config.trace.v2.Tracing.Http.config'. This configuration will be removed from Envoy soon. Please see https://github.com/envoyproxy/envoy/blob/master/DEPRECATED.md for details.
[2019-04-15 13:04:16.652][89][warning][config] [bazel-out/k8-opt/bin/external/envoy/source/common/config/_virtual_includes/grpc_stream_lib/common/config/grpc_stream.h:102] gRPC config stream closed: 14, no healthy upstream
[2019-04-15 13:04:16.652][89][warning][config] [bazel-out/k8-opt/bin/external/envoy/source/common/config/_virtual_includes/grpc_stream_lib/common/config/grpc_stream.h:56] Unable to establish new stream
2019-04-15T13:04:17.696752Z	info	Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 1 successful, 0 rejected; lds updates: 0 successful, 0 rejected
[2019-04-15 13:04:17.725][89][warning][misc] [external/envoy/source/common/protobuf/utility.cc:129] Using deprecated option 'envoy.api.v2.Listener.use_original_dst'. This configuration will be removed from Envoy soon. Please see https://github.com/envoyproxy/envoy/blob/master/DEPRECATED.md for details.
2019-04-15T13:04:19.376794Z	info	Envoy proxy is ready

I also saw a few pod restarts with a similar but shorter error message:
[2019-04-13 15:31:18.694][140][critical][backtrace] [bazel-out/k8-opt/bin/external/envoy/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:81] Caught Segmentation fault, suspect faulting address 0x0
[2019-04-13 15:31:18.694][140][critical][backtrace] [bazel-out/k8-opt/bin/external/envoy/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:67] Backtrace (use tools/stack_decode.py to get line numbers):
[2019-04-13 15:31:18.695][140][critical][backtrace] [bazel-out/k8-opt/bin/external/envoy/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:73] #0: __restore_rt [0x7fb609d515d0]
[2019-04-13 15:31:18.695][140][critical][backtrace] [bazel-out/k8-opt/bin/external/envoy/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:75] #1: [0x8f8414]
[2019-04-13 15:31:18.695][140][critical][backtrace] [bazel-out/k8-opt/bin/external/envoy/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:75] #2: [0xc7aa58]
[2019-04-13 15:31:18.695][140][critical][backtrace] [bazel-out/k8-opt/bin/external/envoy/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:75] #3: [0xc7afbf]
[2019-04-13 15:31:18.695][140][critical][backtrace] [bazel-out/k8-opt/bin/external/envoy/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:75] #4: [0x8f8553]
[2019-04-13 15:31:18.695][140][critical][backtrace] [bazel-out/k8-opt/bin/external/envoy/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:75] #5: [0x8f4cbc]
[2019-04-13 15:31:18.695][140][critical][backtrace] [bazel-out/k8-opt/bin/external/envoy/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:75] #6: [0xf05235]
[2019-04-13 15:31:18.695][140][critical][backtrace] [bazel-out/k8-opt/bin/external/envoy/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:73] #7: start_thread [0x7fb609d49dd5]
2019-04-13T15:31:18.792833Z	warn	Epoch 0 terminated with an error: signal: segmentation fault
2019-04-13T15:31:18.793012Z	warn	Aborted all epochs
2019-04-13T15:31:18.793152Z	error	Permanent error: budget exhausted trying to fulfill the desired configuration
2019-04-13T15:31:18.793239Z	error	cannot start the e with the desired configuration
2019-04-13T15:31:18.793308Z	error

The application node hosting the pods with istio-proxy sidecars was at 85% disk space used and garbage collection could not further clean up any disk space:
  Warning  ImageGCFailed  4m (x109 over 9h)  kubelet, myserver.lab.com  (combined from similar events): wanted to free<PHONE_NUMBER> bytes, but freed 0 bytes space with errors in image deletion: rpc error: code = Unknown desc = Error response from daemon: conflict: unable to delete 844c4ae666ed (cannot be forced) - image has dependent child images

Expected behavior
No segmentation faults on istio-proxy sidecars.
Steps to reproduce the bug
Installed Service Mesh ecosystem and deployed Bookinfo example as well as another project (to rule out Bookinfo being the source).  Leave the application pods running for a few days.
Version (include the output of istioctl version --remote and kubectl version)
Did not deploy istioctl; used Red Hat OpenShift Service Mesh with automatic sidecar injection instead.
envoy --version
envoy  version:<PHONE_NUMBER>/1.10.0-dev/Maistra/RELEASE/BoringSSL
kubectl version
Client Version: version.Info{Major:"1", Minor:"11+", GitVersion:"v1.11.0+d4cacc0", GitCommit:"d4cacc0", GitTreeState:"clean", BuildDate:"2019-02-22T07:05:30Z", GoVersion:"go1.10.8", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"11+", GitVersion:"v1.11.0+d4cacc0", GitCommit:"d4cacc0", GitTreeState:"clean", BuildDate:"2019-02-22T07:05:30Z", GoVersion:"go1.10.8", Compiler:"gc", Platform:"linux/amd64"}
How was Istio installed?
Deployed Red Hat OpenShift Service Mesh via Istio operator
Environment where bug was observed (cloud vendor, OS, etc)
Lab cluster running on OpenShift 3.11 / ServiceMesh (openshift-istio-tech-preview) 0.9.0
Additionally, please consider attaching a cluster state archive by attaching
the dump file to this issue.
istio-dump.tar.gz

Is there any update on this ? Facing similar error in our environment, please update.

Is there any update on this ? Facing similar error in our environment, please update.

I was repeatedly running into the above issue for at least a couple of weeks straight, and suspected that capacity issues may have been at hand.  For unrelated reasons, I had added more compute nodes to my cluster and haven't experienced a single occurrence of the issue in the month and half since.  So for what it's worth, perhaps it's capacity related.


Plugin Unable to Create 'Steps' Gradient

Describe the bug
The plugin seems to be unable to create a gradient using the 'steps' function - when selecting 'steps' from the function dropdown, it seems to simply ignore the change, and still applies whatever function was selected previously.
To Reproduce
Steps to reproduce the behavior:

Create a new, blank Sketch document
Draw a simple rectangle
Set the fill of the rectangle to a simple, vertical gradient - e.g., going from yellow to green
While the rectangle is still selected, open the Easing Gradient plugin
Select any of the available functions, and then select 'steps': the gradient inside the rectangle does not change to a 'step' function, and displays whatever function was previously selected.

Expected behavior
We would expect to see a 'step'-gradient, such as the ones we get when using the test online Editor here.

Screenshots
Unfortunately, using the "step-gradient" function inside the plugin does not generate a step-gradient- it merely leaves whatever function had been selected previously:

Sketch version (please complete the following information):

Version 50.2

@luxlogica thanks for the report, however I cannot reproduce it. Is it still (not) happening?

@larsenwork, it must have been some corrupt setting/preference: I updated the plugin to the latest version, then restarted Sketch, and now it magically works... 🤷♂

@luxlogica cheers,  thanks for testing!


Question about Handbook

Is there any update on when the Handbook will be complete? I noticed there are quite a few empty entries.

The handbook is mostly dependent on community contributions. I haven't been
able to allocate much time to writing any entries lately so I can't really
give you an estimate on when more content might be added
On Sat, Nov 26, 2016 at 1:17 AM Paul Adams<EMAIL_ADDRESS>wrote:

Is there any update on when the Handbook will be complete? I noticed there
are quite a few empty entries.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/yoshuawuyts/choo/issues/340, or mute the thread
https://github.com/notifications/unsubscribe-auth/ACWlek5ATlsnmQgg00uWZ2uTlo7epLHqks5rB3p8gaJpZM4K8w9d
.

Think the question has been answered (: closing!


How do I check the version of log4j library version deployed in the Java runtime?

As clearly indicated in the Log4j support page, please use mailing lists for questions!
Up until version 2.20.0, I was able to use following method to check the version #.
org.apache.logging.log4j.LogManager.class.getPackage().getImplementationVersion()
Starting version 2.21.1 the above method returns null as I could not find "Implementation-Version" entry in the MANIFEST.MF file.

@pantdeepak, thanks for the report, I am on it.
@rgoers, not by the CI release process, but the newly employed bnd-maven-plugin.

@pantdeepak, Log4j et al. is parented by logging-parent and I have fixed the problem there: apache/logging-parent@a43a0b26066b637a5b0cd07cee877c83f0f3347d. logging-parent version 10.3.0 is expected to be released next week and promptly its version will be bumped for Log4j et al.

Thank you very much for your prompt attention to this issue. Much appreciated.


Key Field(s) '[id]' are not queried on XUnion at Operation(XQuery).union

Version
3.8.2
Summary
I have set the extend interface Node @typePolicy(keyFields: "id").
And when I build, the following error occurs.
Key Field(s) '[id]' are not queried on X2 at Operation(XQuery).union
Steps to reproduce the behavior
union X = X1 | X2

type Query {
 x: X!
}

type X1 {
 id: ID!
 name: String
}

type X2 {
 id: ID!
 name: String
}

extend interface Node @typePolicy(keyFields: "id")

query XQuery {
  x {
    ... on X1 {
       id
       name
    }
  }
}

build

`Key Field(s) '[id]' are not queried on X2 at Operation(XQuery).union`

I found a workaround. By modifying the Query as follows, the error disappears.
query XQuery {
  x {
    ... on X1 {
       id
       name
    }
    ... on X2 {
       id
    }
  }
}

Logs
Key Field(s) '[id]' are not queried on X2 at Operation(XQuery).union

Hi 👋
The reason this error is thrown is because we can't add id on an union field:
query XQuery {
  x {
    # This does not validate as no field except __typename can be queried on unions
    id
    ... on X1 {
       name
    }
  }
}

We could add fragments that query id on all types automatically:
query XQuery {
  x {
    # fragments added by the Apollo compiler
    ... on X1 {
       id
    }
    ... on X2 {
       id
    }
    # etc... if more types in the union

    # original fragment
    ... on X1 {
       name
    }
  }
}

But we have always resisted doing so because it felt like a larger modification of the user query that could be surprising.
Do you think adding the fragments automatically would help in that case?


🐛(AWS) fallback on default audio bitrate when absent in mediainfo

Purpose
For some videos, mediainfo doesn't have bitrate info which result in
missing audio in the encoded video. To fix this issue, we test if the
BitRate property is present and fallback on default bitrate if absent.
Proposal

[x] Fallback on default audio bitrate when absent in mediainfo

@lunika shouldn't we also add defaults on other mediainfo values?

@lunika shouldn't we also add defaults on other mediainfo values?

The other info we need is the video height. I think this info will be always present but we can add a fallback yes.

@sampaccoud done

I split this PR in two separated commits.


ModuleNotFoundError: No module named '_curses'

Describe the bug
Traceback (most recent call last):
  File "<frozen runpy>", line 198, in _run_module_as_main
  File "<frozen runpy>", line 88, in _run_code
  File "c:\users\donni\.local\bin\radioactive.exe\__main__.py", line 4, in <module>
    from radioactive.__main__ import main
  File "C:\Users\donni\pipx\venvs\radio-active\Lib\site-packages\radioactive\__main__.py", line 9, in <module>
    from radioactive.alias import Alias
  File "C:\Users\donni\pipx\venvs\radio-active\Lib\site-packages\radioactive\alias.py", line 3, in <module>
    from pick import pick
  File "C:\Users\donni\pipx\venvs\radio-active\Lib\site-packages\pick\__init__.py", line 3, in <module>
    import curses
  File "C:\Users\donni\AppData\Local\Programs\Python\Python313\Lib\curses\__init__.py", line 13, in <module>
    from _curses import *
ModuleNotFoundError: No module named '_curses'

To Reproduce
Steps to reproduce the behavior:

Install Python
Open terminal
Type pip install pipx setuptools (dependencies for radio-active)
Type pipx install radio-active
Optionally, type pipx ensurepath followed by pipx completions
Close and reopen terminal
Type radio
See error

Expected behavior
I expected an about box to appear, followed by a message saying No stations to play. please search for a station first!
Desktop (please complete the following information):

OS: Windows 11
Browser: Firefox
Version: 133.0

Update: Issue is not reproducible in Linux; it only occurs in Windows, and may also occur in macOS; however, I do not have a Mac on which to test.


[Extension Feature Request] Todoist should show Nested Tasks

Extension – Todoist
Author: @thomaslombart
Describe the feature and the current behavior/state.
Nested Tasks are all listed in line as if they were all of the highest level. The nested ones should be indented and put in the correct position so that it makes sense visually.
Who will benefit with this feature?
Anyone that uses the nested tasks feature in Todoist. I think it might also be called subtasks.

Indeed, subtasks are not supported at the moment because I haven't found an easy way of retrieving subtasks from the Todoist REST API. I'll let you know in this issue if I find a way of doing it!

Each task has a parent_id property which is empty if the task is top level. It's a bit roundabout but it could be used.
For the today and upcoming views, maybe a "see sub-tasks" action can be added to the menu and it would look that the project that the main task is from and display all the tasks in that project who have the correct parent_id value.
For the project views, maybe you could insert any task that has a parent_id into the correct position with the indentation after all the top-level tasks are added.
What are your thoughts?

Yeah, I could see a "see sub-tasks" action.
However, it's not possible for now to indent a list item as of today with the Raycast API. So, if a task is at the root level and does have subtasks, don't show subtasks and instead show an accessory icon that indicates it has subtasks (something like a right chevron could do it).
There would be a problem, however: the accessory icon is used to indicate if a task is recurring. It wouldn't be possible to indicate if a task is both recurring and has subtasks.

A see subtasks action would be nice. I think that the indicator isn't necessary, and maybe can be added later if raycast gives more options what can be added to a List Item.

Let's go for that then. I'll work on it this weekend.

Update on this task's status: the REST API makes it tedious to retrieve the subtasks associated with a task simply because there are no parameters associated with the GET tasks endpoint. It's not possible to use a filter for that either.
There are two things to do here:

Include an action panel item "See sub-tasks" if a task does have subtasks
Show the subtasks in a list view

For the first one, I don't see any other options than fetching all of the tasks in order to see which task is associated with a certain parent ID. This is a deal-breaker for me since one can have a lot of tasks and the call can be quite long.
For the second one, the only solution I've seen is to fetch the tasks by using a "subtasks" filter. But once again, we're fetching all subtasks instead of the dedicated subtasks of a certain task.
So, I don't see how to support nested tasks. In the meantime, I hid the nested tasks in the project view to have a clearer view and see only your root tasks just like in Todoist: https://github.com/raycast/extensions/pull/527
Let me know if you have other ideas, otherwise, I'd suggest closing this issue or putting it in a frozen state waiting for improvements from the API.

What is the status of this feature?

After checking with a Todoist's team member, adding this feature would imply a significant revamp of the extension since the extension would need to retrieve the entire tasks list on load (shifting from the REST API to the Sync API). This also has some drawbacks to the maintainability of the extension since the TypeScript client used to interact with Todoist would be useless.
If someone wants to work on it, please do. But it's unlikely I'll work on it in the next weeks.


vendor: depend of Terraform 0.10.0

As of version 0.10.0, Terraform outsourced its providers to github.com/terraform-providers. In order to prevent an issue with nested vendoring, we needed to manually remove vendor/github.com/terraform-providers/terraform-provider-ignition/vendor/github.com/hashicorp/terraform.
This PR also updates all used vendors.

Coverage remained the same at 56.942% when pulling 90c6be8c3c228e1db41f967b585922158e360a71 on monstermunchkin:terraform-0.10.0 into 968bf16201a9f13030f84765b027d7e45fdbef57 on dmacvicar:master.


Handling unicode paths

As far as I can see, it is not possible to use paths on Windows such as C:\Överkörd\Überförare\, maybe paths should be considered UTF-8, then convert to wchar_t* for use with std::ofstream/ifstream.

I don't think UTF-8 has anything to do with wchar_t, you can encode UTF-8 with char*. The usage of wchar_t is not recomended, specially if you want to maintain your code cross compilable (wchar_t may have different meaning for different platforms)


Update observation_form_system_test.rb

Make it more robust. It ain't finding the "edit" icon.

coverage: 94.421%. remained the same
when pulling 1540807ce051e0c30727a47f8fc4e506804f6d46 on nimmo-make-obs-form-system-test-more-robusta
into 38c45b479f1e2bfb6eee4aba669d92f3c404a45c on main.


Built-in editor

Hi, there is a built-in editor like on Github to format the markdown text or it is maybe planned to be implemented? Thank you!

Hi,
Yes, I'm planning to implement a markdown editor and an html editor. I can't give any ETA yet.

Thank you for the info and the reply!


Container not removed from etcd in case of a node reboot

Hello,
I am having an issue when I have a node reboot. Containers running on such a node launching in a Contiv docker network (Layer2 mode) are not deleted from etcd ( contiv.io and docker reposistory) in case a of node reboot.
I still see the container when I run Docker network inspect.
This cause the following problem : if I want to restart the container somewhere, I have this error :
docker: Error response from daemon: service endpoint with name vlan3-1 already exists. So I can't restart the container on an other node.

Netplugin :
Version: pv0.1-09-21-2016.01-34-18.UTC
GitCommit: 9930fee-unsupported
BuildTime: 09-21-2016.01-34-18.UTC

I just use Docker engine to test, not container orchestrator.

@erandu do you see the container if you run "docker ps" ?

@jojimt : This is not the problem here. I said a reboot, but it's the same if I shutdown the node.
For example, with the docker native overlay driver, if I run docker network inspect (after a shutdown on the node where the container is running) on an other node , I don't see the container, so the container is definitively removed from the cluster. Then I can launch a container with the same name on an other node.
Whereas with Contiv, I still see the container if I run docker network inspect on another node. And the problem of that is I can't launch a container with the same name on an other node, cause this one is already present in docker network inspect, whereas it is removed during the shutdown.


Workaround inaccurate arrange view scrollbar position

after zooming (fixes #1519)
after resizing down then maximizing REAPER's window (fixes #1308)
(unconfirmed) after ??? (#1621)

:white_check_mark: Build sws 731-master completed (commit https://github.com/reaper-oss/sws/commit/a35e5a55e7 by @cfillion)

Windows 64-bit

build/BuildUtils/SWS_Template.ReaperLangPack
build/BuildUtils/whatsnew.html
build/reaper_sws-x64.pdb
build/sws-<IP_ADDRESS>-Windows-x64-uncoolsb-npos-a35e5a55.exe

Windows 32-bit

build/BuildUtils/SWS_Template.ReaperLangPack
build/BuildUtils/whatsnew.html
build/reaper_sws-x86.pdb
build/sws-<IP_ADDRESS>-Windows-x86-uncoolsb-npos-a35e5a55.exe

macOS x86 64-bit

build/sws-<IP_ADDRESS>-Darwin-x86_64-uncoolsb-npos-a35e5a55.dmg

macOS x86 32-bit

build/sws-<IP_ADDRESS>-Darwin-i386-uncoolsb-npos-a35e5a55.dmg

macOS ARM 64-bit

build/sws-<IP_ADDRESS>-Darwin-arm64-uncoolsb-npos-a35e5a55.dmg

Linux x86 64-bit

build/sws-<IP_ADDRESS>-Linux-x86_64-uncoolsb-npos-a35e5a55.tar.xz

Linux x86 32-bit

build/sws-<IP_ADDRESS>-Linux-i686-uncoolsb-npos-a35e5a55.tar.xz

Linux ARM 64-bit

build/sws-<IP_ADDRESS>-Linux-aarch64-uncoolsb-npos-a35e5a55.tar.xz

Linux ARM 32-bit

build/sws-<IP_ADDRESS>-Linux-armv7l-uncoolsb-npos-a35e5a55.tar.xz

Props for the branch name lol.


Rename selection answers to supplier declaration

The language we have settled on for this is supplier declaration. This reflects the changes in alphagov/digitalmarketplace-api#262
Depends on

[ ] alphagov/digitalmarketplace-api#262

This looks like a good time to suggest starting a CHANGELOG.md file for listing breaking changes in utils. Something as simple as: version, what was the breaking change, where to look for things that need to be changed in the app, example of before/after usage.
I'm happy to do this as a separate PR if everyone agrees this might be useful.
:+1:

@allait - yes, that would definitely be useful!


When project imports mcumgr_flutter, iOS requests for Bluetooth permissions at startup

Should it be requested when methods of the plugin are in use?

You're absolutely correct.
The Bluetooth permissions issue you've raised was indeed addressed following a request in #81, and it's been resolved in version 0.4.1.
To see the fix in action, you can refer to this demo project. Let me know if you need further assistance!

Sorry, completely forgot to upgrade, 0.4.1 changed approach to my problem. Thank you for quick response :)


USE_NVRTC -> ENABLE_CUDA_RTC to fix maven build.  Add compile-guard to fusion.

This PR fixes the maven build issue https://github.com/apache/incubator-mxnet/issues/16765 reported by @zachgk and first seen with PR https://github.com/apache/incubator-mxnet/pull/15167.  The fix involved-

Renaming the build flag used by maven (namely USE_NVRTC) to the name used by the pip builds (ENABLE_CUDA_RTC).  The Makefile currently looks at ENABLE_CUDA_RTC (not USE_NVRTC) and in response sets the compile flag MXNET_ENABLE_CUDA_RTC=1 and adds -lcuda -lnvrtc to the LDFLAGS.  It was the absence of these ld flags when creating im2rec that caused the issue filed.

Adding compile guards to the newly-introduced files  ./src/operator/fusion/* in a form similar to those that protect ./src/common/rtc.cc.  Now both cuda runtime-compilation facilities are included into the build (or not) based on MXNET_ENABLE_CUDA_RTC.

Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[ ] The PR title starts with [MXNET-$JIRA_ID], where $JIRA_ID refers to the relevant JIRA issue created (except PRs with tiny changes)
[ X] Changes are complete (i.e. I finished coding on this PR)
[ ] All changes have test coverage:
Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
[X ] Code is well-documented:
For user-facing API changes, API doc string has been updated.
For new C++ functions in header files, their functionalities and arguments are documented.
For new examples, README.md is added to explain the what the example does, the source of the dataset, expected performance on test set and reference to the original paper if applicable
Check the API doc at https://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
[ ] To the my best knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Changes

[ ] Feature1, tests, (and when applicable, API doc)
[ ] Feature2, tests, (and when applicable, API doc)

Comments

If this change is a backward incompatible change, why must this change be made.
Interesting edge cases to note here

LGTM, but I'm thinking about backwards compatibility - should the change of the build flag be of concern?

I would say it is just fixing the bug and bringing the Scala build to parity with other builds (especially since the value of the flag is not changed, so the intent to enable this was there, it's just that it was never actually doing anything).

Honestly speaking, there is no backend build difference between pip build and scala for now. we can also use the pip mk on Scala/Java build without problems. @zachgk let's track on the deprecation on the maven mkl files.

[03:39:03] /work/mxnet/src/executor/attach_op_execs_pass.cc:355: Neither FCompute nor FComputeEx registered _FusedOp - @DickJC123 I believe it is still not guarded properly (seems that the graph pass works but the actual .cu file that contains FCompute is not included).


How many API call would the following query use?

Hello
I have a questions in regard to the query call to the SF api and want to know how many API call would the following query use?
let's say the total records in SF is around 17,000 records, and we are doing the streaming of the data that's return from the API call
sfConnection
          .query('SELECT id from Opportunity')
          .run({ autoFetch : true, maxFetch:999999 })
          .pipe(saveData)
          .on('finish', resolve)

Thank you

@thomas-33across - this all depends on how expensive the API calls are. Salesforce returns a variable amount of records based on the fields/relationships/subqueries included in the query AND depending on what data is populated in the records.
For example, in an org I have here is my results:
Query all fields on accounts - 200 at a time out of of 54,196 records
SELECT ID FROM Account - 2,000 of 54,196 records
I have also seen where individual datasets returned can vary (usually if you have a subquery where many records don't have the child records, then other segments of the data where lots of records have the related child records).
Here is my take on this:

You probably don't need to be concerned about the number of API calls made unless you have a process that is extremely high volume
I have an application where we auto-download records if the user asks us to, and many users have downloaded 80K+ records, plus tons of other calls and never hit API limits
.run({ autoFetch : true, maxFetch:999999 }) --> for some reason I always had problems with autoFetch - it never seemed to work, so I built my own system to do this.
While 17K records is not very high volume, you will gain a lot of performance by using the bulk API. ou will need to poll for changes (which takes multiple API calls - but again, you probably do not need to be concerned with this) and then you can download the results.


*: appc v0.8.5

apparently some bugs in isolatorvalues, stand by

@jonboulle it turned out this may not be a real bug in validator, but rkt misusing it. See https://github.com/appc/spec/pull/633#issuecomment-228107843 for reference, but it only adds a graceful handler to an error case.

@lucab updated

LGTM


US 01.11.01

As an organizer, I want to OPTIONALLY limit the number of attendees that can sign up for an event
Acceptance Criteria

[x] When creating an event, organizers should see an option to set sign up limit
[x] Limit should only be an integer number (hopefully realistic value)
[x] If no limit is provided, no limit should be set (unlimited sign ups allowed)
[x] Organizer should be able to see number of signed up users

completed


t.map is not as function when changing smart motorway signs

What version of Node.js are you using?
18.17.0
What operating system are you using?
Ubuntu
What version of SnailyCAD are you currently using?
v1.73.2 6f1762a
Describe the Bug
When changing a smart motorway sign and leaving any lane above as the default value it will cause the live map to present a client error for all users until the resource is reset.
Eg. changing lane 1 only will work, but changing 3 only will result in a crash.
Expected Behavior
Changing a single lane without changing the other values should not result in an error.
To Reproduce

This is partially fixed now. Will still have to verify something later today or tomorrow

tested and should be working again


Intellisense: PromiseRejectionEvent suggested over Promise

Issue Type: Bug
I'm in the middle of a large refactor where I am converting jQuery.Deferred() to Native Promises. For some reason, PromiseRejectionEvent is suggested by IntelliSense before Promise or Promise isn't suggested at all. This is making it very difficult to work. For example, I'll type "new Promise(" and by typing the "(" it turns my perfectly valid JS into "new PromiseRejectionEvent(". Then I have to hit undo twice and type the parenthesis again.
Do I need to configure VSCode differently or is a bug? recentlyUsedByPrefix has helped some but only when I have already used "Promise" in the file.

Closing as not reproducable in my testing


ERROR NettyMQTTHandler  - Bad error in processing the message

I don't do anything special (only publish and subscribe to messages with QoS 0 and 2), but in the moquette.log the following error appears quite often:
0    [nioEventLoopGroup-3-2] ERROR NettyMQTTHandler  - Bad error in processing the message
java.lang.NullPointerException
    at io.moquette.spi.impl.ProtocolProcessor.processPubComp(ProtocolProcessor.java:668)
    at io.moquette.server.netty.NettyMQTTHandler.channelRead(NettyMQTTHandler.java:67)
    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:318)
    at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:304)
    at io.moquette.server.netty.metrics.MessageMetricsHandler.channelRead(MessageMetricsHandler.java:46)
    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:318)
    at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:304)
    at io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:276)
    at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:263)
    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:318)
    at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:304)
    at io.netty.channel.ChannelInboundHandlerAdapter.channelRead(ChannelInboundHandlerAdapter.java:86)
    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:318)
    at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:304)
    at io.netty.channel.ChannelInboundHandlerAdapter.channelRead(ChannelInboundHandlerAdapter.java:86)
    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:318)
    at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:304)
    at io.moquette.server.netty.metrics.BytesMetricsHandler.channelRead(BytesMetricsHandler.java:47)
    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:318)
    at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:304)
    at io.netty.handler.timeout.IdleStateHandler.channelRead(IdleStateHandler.java:266)
    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:318)
    at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:304)
    at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:846)
    at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:131)
    at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:511)
    at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:468)
    at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:382)
    at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:354)
    at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:112)
    at io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:137)
    at java.lang.Thread.run(Unknown Source)

I use the latest version (build from source) in embedded mode.
Has anyone else got this message?

Do you have an example to reproduce it?

No, that was the problem, because the error appeared sporadically.
I'm sorry, but I don't use moquette anymore. Had more luck with mosquitto.
Thanks anyway for all your effort!

Closed because interest go to Moqsuitto

Hi! I get this error today,any solution for this now？
Thanks！

You tried the master with 0.10-SNAPSHOT or the 0.9 verrion?
Do you have a test case to reproduce it?

Yes,actually this happen in the 0.9 version.
Sorry, I don have any test case to reproduce it,however,this error appears quite often when I try to pub messages very fast(every 20ms) . that matters?
Thanks！

I'll try to reproduce and investigate. Thaks

@sawyer7246:
Which operating system do you use?

@mamiu jdk1.7.0_25 / windows 10 64bit

I used the same jdk on windows server 2012.
@andsel: maybe this information is helpfull to reproduce the error.

Hi,
I'm Alberto; I'm part od Freedomotic team (www.freedomotic.com); same problem today and a test case so that you can reproduce the problem at will. Our aim is integrate souliss framework throught MQTT and node red, so we have, as part of test archtecture, an arduino MQTT node with a DHT11 sensor which sends to freedomotictesttopic1 topic, temperature values every 5 seconds. The point is that the MQTT broker is a plugin for freedomotic developed by Mauro with Moquette. After 278 messages divided by an interval of 5 seconds the plugin crashed.

Here is the link to the pom.xml  https://github.com/freedomotic/freedomotic/blob/master/plugins/devices/mqtt-broker/pom.xml  It seems Moquette library ver 0.10 5.6-SNAPSHOT; java RE 8 1.8.0-144-b01; OS win 10 64 bit. At the moment we think to take away from the marketplace the MQTT broker plugin and leave the MQTT client, but we hope that in a near future with a little library's debug and update, we can reintegrate it. Thank you very much, Alberto

PD: if can be of help: here we can see the correct MQTT message published by arduino node (temp value) into main Freedomotic prompt window (verbose mode) via MQTT broker plugin

19.00 Celsius degees.
@andsel thanks again if you can help us with this; maybe you italian too?

Hi @amenak77 yes I'm italian too.
It's just the an NPE of the previous issue, but the trace is little bit different as I can see.
Do you have a text form of the log (please enable also the messages logger so there is the complete sequence of messages, it's more verbose) so that I can investigate, or could you provide an executable reproducible test, in form of JUnit test case? It's little bit difficult to understand what could break from a couple of cmd screenshots.

Hi @andsel glad to hear this and best compliments for your project. I'm sure this problem will be wipe out soon; hope to be of help. The log file is a bit long and I can attach image files only I guess. How can I send you the log? Thanks, Alberto

@andsel any update about this?

Hi @mcicolella  and @amenak77  I can't reproduce it, is available any detailed log of the issue and/or a unit/integration test to reproduce it?
Have you tried with version 0.11-SNAPSHOT?

Hi @andsel
I updated our plugin to moquette v0.11 and it seems working well.
But @amenak77 is our "stress tester".


Reduce bundle size by replacing ethers with its subpackages

Apparently our move to ethers v6 caused our minified+gzipped bundle size to increase by ~200kb (size of<EMAIL_ADDRESS>size of fuels@0.63.0).
I took a look around and it seems like we can replace our ethers dependencies with just @ethersproject/bytes.
Edit: ethers v6 supports tree-shaking, so such a big jump in package size shouldn't happen.

I completely excluded ethers from the build process and the bundle size was reduced by only 14 KB, meaning that it indeed does get tree-shaken. It seems that bundlephobia.com doesn't catch this part.


spirv-val does not catch when SampleMask is not declared as an array

The Vulkan specification 1.0.66 states:
"Any variable decorated with SampleMask must be declared as an array of 32-bit integers."
However, there was a bug in glslang where for HLSL it was outputting SampleMask as just a 32-bit integer, see: https://github.com/KhronosGroup/glslang/issues/1202
I think spirv-val should catch this error in the vr_standard_ps.spv attached to that bug.

VUID-SampleMask-SampleMask-04359 in the Vulkan spec cover this and was labeled (and has a test for it SampleMaskNotArray) in https://github.com/KhronosGroup/SPIRV-Tools/pull/3756
So think can close here


feat: Upgrade to Calico v3.28.1

What problem does this PR solve?:
Pulls in upstream fixes, which include a performance regression with Linux kernel 5.4.x.
Which issue(s) this PR fixes:
Fixes #
How Has This Been Tested?:

Special notes for your reviewer:

IMPORTANT We do not want to include this in NKP 2.12, so we need to wait before merging.

@dlipovetsky I merged this 😅 will revert... Need to get into the habit of cutting release branches I think.

Updated release-please config to support release branches in https://github.com/nutanix-cloud-native/cluster-api-runtime-extensions-nutanix/pull/880 - let's try this rather than reverting this PR 🙏


Add descriptions to a few RenderingDevice's PipelineDynamicStateFlags

This PR fills the descriptions of the RenderingDevice's DYNAMIC_STATE_LINE_WIDTH and DYNAMIC_STATE_DEPTH_BIAS.
I wish I had the knowledge to fill all of them, but these two are the only two I can write down with some confidence. Help to do this would be great.

Thanks!


ci: fix issues with long running fuzz jobs; remove apt pgp key download

Please note that while we are transitioning from travis-ci to AWS CodeBuld, some tests are run on each platform. Non-AWS contributors will temporarily be unable to see CodeBuild results. We apologize for the inconvenience.
Description of changes:

Use consistent variable for repo name
GHA timeout is lower than Codebuild- move to 6 hours
Remove (constantly failing) apt pgp key download; comment as to why we need a test PPA

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

:exclamation: No coverage uploaded for pull request head (gha_cb_schedule_fixes@e439db7). Click here to learn what that means.
The diff coverage is n/a.


Unable to install

Describe the bug
installation don't finish with all requirements

As the installer says, try to install those tools manually because the problem can occur for many different reasons, GitHub speed limits. network problems....


Auto-create tables when batch insertion fails.

Auto-create tables when table insertion fails instead of when receiving a record.

Codecov Report

Merging #248 into master will increase coverage by 1.33%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master     #248      +/-   ##
============================================
+ Coverage     69.05%   70.39%   +1.33%
- Complexity      277      283       +6
============================================
  Files            32       32
  Lines          1477     1483       +6
  Branches        155      155
============================================
+ Hits           1020     1044      +24
+ Misses          409      384      -25
- Partials         48       55       +7

Impacted Files
Coverage Δ
Complexity Δ

...onnect/bigquery/config/BigQuerySinkTaskConfig.java
93.61% <0.00%> (-2.13%)
4.00% <0.00%> (-1.00%)

...wepay/kafka/connect/bigquery/BigQuerySinkTask.java
60.54% <0.00%> (-0.72%)
27.00% <0.00%> (-2.00%)

...fka/connect/bigquery/write/row/BigQueryWriter.java
94.73% <0.00%> (+5.26%)
21.00% <0.00%> (+2.00%)
:arrow_down:

...afka/connect/bigquery/write/batch/TableWriter.java
66.66% <0.00%> (+5.55%)
5.00% <0.00%> (+1.00%)
:arrow_down:

...ect/bigquery/write/row/AdaptiveBigQueryWriter.java
38.70% <0.00%> (+38.70%)
6.00% <0.00%> (+6.00%)
:arrow_down:

Closing this PR since it doesn't cover the case for GCSBatchTableWriter. Created https://github.com/wepay/kafka-connect-bigquery/pull/250 instead.


fundamentals/configuration "Configuration" command line providers & inject Options

[ ] Configuration: Document format supported for command line arguments provider #1382
[x] Markup to show how to inject Options in Configuration document #437
[x] Address MVP summit feedback on Configuration #2408

@Rick-Anderson Your 2nd checkbox for #437 is covered by #4214.

@guardrex Thanks for letting me know. I updated the checkbox.


Can I use SDXL for training, such as I want to train inpaints

As mentioned in the title, I believe that SDXL combined with Controlnet will have better results.

cross-post of https://github.com/lllyasviel/ControlNet-v1-1-nightly/issues/126


End User Discussion Group Website Updates

[ ] Write blog post
[ ] Add to community page
[ ] Update banner

cc @sharrmander

Hey @austinlparker, I would love to be part of this website update.

Cool beans -- this is mostly a tracking issue, Sharr should be able to pop some more detail in about the specifics.

Hi,
I've got the blog post drafted (and the private slack channel created).
I just need to get the first discussion group on the community calendar, then we'll be ready to publish the post.
Draft here: https://docs.google.com/document/d/1OUBGZCOQIzO3yULjn2WA4XVKiQQiRMY3F6UMXJ_0KyU/edit?usp=drivesdk --open to feedback!

Hi @sharrmander that’s a nice intro.👍

All of this work is complete now, right?

Did you want to add something to https://opentelemetry.io/community/ about it? Otherwise we can close it


[FEAT] Improved docs on estimate_probability_two_random_records_match

Is your proposal related to a problem?
Currently, the sole documentation of this function is the docstring. Whilst this defines what needs to go into the function, there is a gap in the documentation for this on why these parameters go in the function, what the function does "under-the-hood", and how this impacts the wider model by the prior.
Describe the solution you'd like
A full description of:

What deterministic rules are designed to do
What the recall means in relation to the deterministic rule
How these two are combined mathematically to calculate the probability
How the probability is leads to the calculation of the prior
How having a "bad" set of deterministic rules may affect your prior (highlighting the importance of this)
How increasing/decreasing the recall affects the prior (highlighting the relative lesser importance of this
Why having an accurate prior is important

This could sit with the function directly, or, as these are blocking rules, it could sit as an additional section within the blocking rules topic guide.

FWIW here is the discussion of why we use this approach, may contain useful information for the docs
https://github.com/moj-analytical-services/splink/issues/462


nodePackages.lv_font_conv: init at 1.5.2

Description of changes
Add the lv_font_conv utility
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

@Luflosi @midchildan @winterqt can this be merged?

@SuperSandro2000 can this be merged as well?


Trust?

It lets you simply and securely share secret information with people you trust [the server]

Secrets are signed with HMAC SHA256 and encrypted with AES 256 CTR using keys that live on the Sharelock server

It would be better if encryption and decryption happens in the browser using a random key.
The server would only get the encrypted content, while the key would be transmitted via the URL fragment which is not transmitted to the server.
AFAIK, that's what MEGA does.

PS: Very creative name :+1:

That is exactly what I wanted to post right now when I saw URL-s.
I definietly would NOT trust this platform for passing any "secret information". Unfortunately it is "broken by design".

:+1:

The current workaround is to simply self-host. In fact, you should probably self-host even if this was using client-side cryptography. A remote server that you don't trust could potentially inject scripts at random to do who-knows-what with your secret information and keys.
Not to mention this project came about long before WebCrypto was standardized, which still doesn't solve the issue of an untrusted remote server abusing the WebCrypto API to compromise your data.
This post from last year goes over some of the pitfalls of WebCrypto, and how one service poorly implements it.
The ideal would be a native app that uses client-side end-to-end encryption.


[wip] tiered cache

This is a starting point for a tiered cache where one could have multiple package caches, where some of the lower ones might be read-only.
A challenge is that we probably cannot do "read-locking" on read-only caches since we wouldn't be allowed to create lockfiles at all.
Another goal is that we can say: can-reflink or can-symlink per-cache (I want to store a HashMap in the cache with prefix mapping to capabilities).

@wolfv Hello from https://github.com/conda/rattler/pull/1003! I may be missing some context, so I’d appreciate your clarification:

A challenge is that we probably cannot do "read-locking" on read-only caches since we wouldn't be allowed to create lockfiles at all.

Isn't it guaranteed that each package in the cache has a lockfile? If so, how does that affect the read-locking concern?

Another goal is that we can say: can-reflink or can-symlink per-cache (I want to store a HashMap in the cache with prefix mapping to capabilities).

Could you provide more details on this? I’m not entirely clear on how the can-reflink and can-symlink capabilities would be used per cache.
Thanks!

@kelvinou01 ah I see. Maybe you are right! I wasn't sure if we could aquire a lock in a read-only filesystem but your argument makes sense. I think if we cannot aquire a lock, we can ignore that, too.
We are linking each package individually, and we are testing wether we can reflink from package cache to target_prefix for each package. Instead of performing this check for every package, we could perform the check once, per package cache, and store this information in the cache.
We have functions that try to create a hardlink or symlink from package cache to prefix already in the link.rs file (I think).


ExamplesFunTest: Avoid a lateinit to be able to run tests individually

Signed-off-by: Sebastian Schuberth<EMAIL_ADDRESS>

Merging despite the unrelated test failures which have been fixed separately by https://github.com/oss-review-toolkit/ort/pull/3475.

Merging despite the unrelated test failures which have been fixed separately by https://github.com/oss-review-toolkit/ort/pull/3475.


[README] Missing link to the API docs

There is a broken API docs link in the last paragraph of the package README:

There is a C++ API that can be integrated into your own process, you can find the API docs here.

Can that link now be replaced with this? https://docs.ros.org/en/ros2_packages/rolling/api/domain_bridge/index.html

Yes, we can probably point the link to the docs hosted at docs.ros.org.


chore(experiment): Add pod network duplication experiment in generic experiments of LitmusChaos

Signed-off-by: Udit Gaurav<EMAIL_ADDRESS>This PR contains:

Addition a pod network duplication experiment in the generic experiment of litmus. Litmus already has a number of pod level network chaos experiments like pod network latency, loss, corruption. This will help to increase the coverage of network experiments.
The experiment should be in go, so the PR will go to the litmus-go repository. This experiment uses netem command to generate a network duplication same as pod network latency and others.
This issue will track the addition of the experiment. This experiment will be supported for the docker runtime environment only as of now, support for others will be added soon.

Issues:

fixes: https://github.com/litmuschaos/litmus/issues/1585

Note For Reviewer:

Logs:

Pod Network Duplication

W0622 19:09:50.291206       1 client_config.go:541] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
time="2020-06-22T19:09:50Z" level=info msg="[PreReq]: Getting the ENV for the  experiment"
time="2020-06-22T19:09:50Z" level=info msg="[PreReq]: Updating the chaos result of pod-network-duplication experiment (SOT)"
time="2020-06-22T19:09:50Z" level=info msg="The application informations are as follows\n" Ramp Time=0 Namespace=default Label="run=nginx"
time="2020-06-22T19:09:50Z" level=info msg="[Status]: Verify that the AUT (Application Under Test) is running (pre-chaos)"
time="2020-06-22T19:09:50Z" level=info msg="[Status]: Checking whether application pods are in running state"
time="2020-06-22T19:09:50Z" level=info msg="The running status of Pods are as follows" Pod=nginx-7db9fccd9b-jv85q Status=Running
time="2020-06-22T19:09:50Z" level=info msg="The running status of Pods are as follows" Pod=nginx-7db9fccd9b-wxpzv Status=Running
time="2020-06-22T19:09:50Z" level=info msg="The running status of Pods are as follows" Status=Running Pod=nginx-7db9fccd9b-xmz77
time="2020-06-22T19:09:50Z" level=info msg="[Status]: Checking whether application containers are in running state"
time="2020-06-22T19:09:50Z" level=info msg="The running status of container are as follows" container=nginx Pod=nginx-7db9fccd9b-jv85q Status=Running
time="2020-06-22T19:09:50Z" level=info msg="The running status of container are as follows" Status=Running container=nginx Pod=nginx-7db9fccd9b-wxpzv
time="2020-06-22T19:09:50Z" level=info msg="The running status of container are as follows" Status=Running container=nginx Pod=nginx-7db9fccd9b-xmz77
time="2020-06-22T19:09:50Z" level=info msg="[Prepare]: Application pod name under chaos: nginx-7db9fccd9b-jv85q"
time="2020-06-22T19:09:50Z" level=info msg="[Prepare]: Application node name: gke-cluster-1-default-pool-8774fd9c-v4br"
time="2020-06-22T19:09:50Z" level=info msg="[Prepare]: Target container name: nginx"
time="2020-06-22T19:09:50Z" level=info msg="[Status]: Checking the status of the helper pod"
time="2020-06-22T19:09:50Z" level=info msg="[Status]: Checking whether application pods are in running state"
time="2020-06-22T19:09:54Z" level=info msg="The running status of Pods are as follows" Pod=pumba-netem-vbyjby Status=Running
time="2020-06-22T19:09:54Z" level=info msg="[Status]: Checking whether application containers are in running state"
time="2020-06-22T19:09:54Z" level=info msg="The running status of container are as follows" container=pumba Pod=pumba-netem-vbyjby Status=Running
time="2020-06-22T19:09:54Z" level=info msg="[Wait]: waiting till the completion of the helper pod"
time="2020-06-22T19:09:54Z" level=info msg="helper pod status: Running"
time="2020-06-22T19:09:55Z" level=info msg="helper pod status: Running"
time="2020-06-22T19:09:56Z" level=info msg="helper pod status: Running"
time="2020-06-22T19:09:57Z" level=info msg="helper pod status: Running"
time="2020-06-22T19:09:58Z" level=info msg="helper pod status: Running"
time="2020-06-22T19:09:59Z" level=info msg="helper pod status: Running"
time="2020-06-22T19:10:00Z" level=info msg="helper pod status: Running"
time="2020-06-22T19:10:01Z" level=info msg="helper pod status: Running"
time="2020-06-22T19:10:02Z" level=info msg="helper pod status: Running"
time="2020-06-22T19:10:03Z" level=info msg="helper pod status: Running"
time="2020-06-22T19:10:04Z" level=info msg="helper pod status: Running"
time="2020-06-22T19:10:05Z" level=info msg="helper pod status: Running"
time="2020-06-22T19:10:06Z" level=info msg="helper pod status: Running"
time="2020-06-22T19:10:07Z" level=info msg="helper pod status: Running"
time="2020-06-22T19:10:08Z" level=info msg="helper pod status: Running"
time="2020-06-22T19:10:09Z" level=info msg="helper pod status: Running"
time="2020-06-22T19:10:10Z" level=info msg="helper pod status: Running"
time="2020-06-22T19:10:11Z" level=info msg="helper pod status: Running"
time="2020-06-22T19:10:12Z" level=info msg="helper pod status: Running"
time="2020-06-22T19:10:13Z" level=info msg="helper pod status: Running"
time="2020-06-22T19:10:14Z" level=info msg="helper pod status: Running"
time="2020-06-22T19:10:15Z" level=info msg="helper pod status: Running"
time="2020-06-22T19:10:16Z" level=info msg="helper pod status: Running"
time="2020-06-22T19:10:17Z" level=info msg="helper pod status: Running"
time="2020-06-22T19:10:18Z" level=info msg="helper pod status: Running"
time="2020-06-22T19:10:19Z" level=info msg="helper pod status: Running"
time="2020-06-22T19:10:20Z" level=info msg="helper pod status: Running"
time="2020-06-22T19:10:21Z" level=info msg="helper pod status: Running"
time="2020-06-22T19:10:22Z" level=info msg="helper pod status: Running"
time="2020-06-22T19:10:23Z" level=info msg="helper pod status: Running"
time="2020-06-22T19:10:24Z" level=info msg="helper pod status: Running"
time="2020-06-22T19:10:25Z" level=info msg="helper pod status: Running"
time="2020-06-22T19:10:26Z" level=info msg="helper pod status: Running"
time="2020-06-22T19:10:27Z" level=info msg="helper pod status: Running"
time="2020-06-22T19:10:28Z" level=info msg="helper pod status: Running"
time="2020-06-22T19:10:29Z" level=info msg="helper pod status: Running"
time="2020-06-22T19:10:30Z" level=info msg="helper pod status: Running"
time="2020-06-22T19:10:31Z" level=info msg="helper pod status: Running"
time="2020-06-22T19:10:32Z" level=info msg="helper pod status: Running"
time="2020-06-22T19:10:33Z" level=info msg="helper pod status: Running"
time="2020-06-22T19:10:34Z" level=info msg="helper pod status: Running"
time="2020-06-22T19:10:35Z" level=info msg="helper pod status: Running"
time="2020-06-22T19:10:36Z" level=info msg="helper pod status: Running"
time="2020-06-22T19:10:37Z" level=info msg="helper pod status: Running"
time="2020-06-22T19:10:38Z" level=info msg="helper pod status: Running"
time="2020-06-22T19:10:39Z" level=info msg="helper pod status: Running"
time="2020-06-22T19:10:40Z" level=info msg="helper pod status: Running"
time="2020-06-22T19:10:41Z" level=info msg="helper pod status: Running"
time="2020-06-22T19:10:42Z" level=info msg="helper pod status: Running"
time="2020-06-22T19:10:43Z" level=info msg="helper pod status: Running"
time="2020-06-22T19:10:44Z" level=info msg="helper pod status: Running"
time="2020-06-22T19:10:45Z" level=info msg="helper pod status: Running"
time="2020-06-22T19:10:46Z" level=info msg="helper pod status: Running"
time="2020-06-22T19:10:47Z" level=info msg="helper pod status: Running"
time="2020-06-22T19:10:48Z" level=info msg="helper pod status: Running"
time="2020-06-22T19:10:49Z" level=info msg="helper pod status: Running"
time="2020-06-22T19:10:50Z" level=info msg="helper pod status: Running"
time="2020-06-22T19:10:51Z" level=info msg="helper pod status: Running"
time="2020-06-22T19:10:52Z" level=info msg="helper pod status: Running"
time="2020-06-22T19:10:53Z" level=info msg="helper pod status: Succeeded"
time="2020-06-22T19:10:53Z" level=info msg="The running status of Pods are as follows" Pod=pumba-netem-vbyjby Status=Succeeded
time="2020-06-22T19:10:53Z" level=info msg="[Cleanup]: Deleting the helper pod"
time="2020-06-22T19:10:53Z" level=info msg="[Confirmation]: The app pod network duplication"
time="2020-06-22T19:10:53Z" level=info msg="[Status]: Verify that the AUT (Application Under Test) is running (post-chaos)"
time="2020-06-22T19:10:53Z" level=info msg="[Status]: Checking whether application pods are in running state"
time="2020-06-22T19:10:53Z" level=info msg="The running status of Pods are as follows" Pod=nginx-7db9fccd9b-jv85q Status=Running
time="2020-06-22T19:10:53Z" level=info msg="The running status of Pods are as follows" Pod=nginx-7db9fccd9b-wxpzv Status=Running
time="2020-06-22T19:10:53Z" level=info msg="The running status of Pods are as follows" Pod=nginx-7db9fccd9b-xmz77 Status=Running
time="2020-06-22T19:10:53Z" level=info msg="[Status]: Checking whether application containers are in running state"
time="2020-06-22T19:10:53Z" level=info msg="The running status of container are as follows" container=nginx Pod=nginx-7db9fccd9b-jv85q Status=Running
time="2020-06-22T19:10:53Z" level=info msg="The running status of container are as follows" container=nginx Pod=nginx-7db9fccd9b-wxpzv Status=Running
time="2020-06-22T19:10:53Z" level=info msg="The running status of container are as follows" container=nginx Pod=nginx-7db9fccd9b-xmz77 Status=Running
time="2020-06-22T19:10:53Z" level=info msg="[The End]: Updating the chaos result of pod-network-duplication experiment (EOT)"

Pod Network Duplication with Packet Duplication of 100%

Pod Network Duplication with Packet Duplication of 50%


Wrong registration order

I get wrong registration order when using "env" modifier.
I have two implementation of the same interface as Singleton. The two implementation have different env provided. In the generated injector the first implementation registered before all usages, but the other implementation registered later in the file. So it is working in one env, but fails in the other ( Object/factory with type Repository is not registered inside GetIt.)
abstract interface class Repository {
}

@Singleton(as: Repository, env: [AppEnvironment.demo])
class RepositoryDemo implements Repository {
}

@Singleton(as: Repository, env: [AppEnvironment.dev, AppEnvironment.uat])
class RepositoryDev implementsRepository {
}

Yeah sorry, same name, other package!


[ENH] Intent coverage

Motivation - If you model a large bot with lots of different intents then it is sometimes tiresome to check whether your nlu-model contains training data for each intent you used in the bot model. It would be great to have a button on the training page where you could check if your nlu training data contains all intents that your bot model has
Specification - This can be done entirely in the frontend. Add a function extractIntentsFromBotModel() that returns the set of intents in the bot model. Add a function extractIntentsFromNLUModel() that returns the set of intents in the nlu file. Finally add a function checkCoverage that determines the list of intents that are contained in the bot model but not the nlu model
Finalised state - A button is on the page that says check intent coverage. Clicking this button the user gets the coverage as % value as well as any missing intents

you could also have a warning popping up if you submit a model without 100% intent coverage


I want to get Post owner by user_id

Retrive all post with owner from activity table by User how this is possible whats relation i create in Post Model

In activity table i have user_id, loggable_type, loggable_id
Every Post Create with Log of user which create i want to show post with user in Post Lop

I'm not sure I understand your question right, but I'm thinking it isn't a good idea to manage post ownership via the activity log.


TextField don't add newline on Enter-key

Hi. I have some problem with openfl.text.TextField: it don't add new lines on Enter (for neko -64 and cpp -64 targets)
haxe: 3.2.1
neko: 2.1.0
openfl-html5: 1.0.5
openfl-native: 1.4.0
openfl-nativedialog: 1.2.0
openfl-ouya: 1.0.2
openfl-samples: 4.0.0
openfl: 4.0.3
lime-tools: 1.5.7
lime: 3.0.3
os: Linux Mint 18 x64
example
Main.hx
package;

import openfl.display.*;
import openfl.text.*;

class Main extends openfl.display.Sprite {
	public function new () {
		super();

		var tf:TextField = new TextField();
		tf.width = 300;
		tf.height = 300;
		tf.border = true;
		tf.multiline = true;
		tf.selectable = true;
		tf.type = TextFieldType.INPUT;

		this.addChild(tf);
	}
}

Thanks

Textfields are in a weird, incomplete spot right now. Some of us are fixing things, but I haven't had the time recently to work on it. Input text was next on my list, though.

Thank you for your answer, I hope that solution will be found.

Added a commit that helps, the newline is added, and you can write on the next line.
But the caret doesn't appear until a non space is added on the line (beside the first line).
And maj+up and maj-down aren't supported yet.

Work's fine now! Many thanks for fix!


replace jade icon with pug icon

***Fixes #168 ***
Changes proposed:

[ ] Add
[ ] Prepare
[ ] Delete
[x] Fix

Things I've done:

[x] I've pulled the latest master branch
[x] I've run npm install to install all the dependenies
[ ] I've checked my code, it is clean.
[ ] I've run ESLint.
[x] My pull request fixes an issue, I referenced the issue.
[x] My pull request is not too big, otherwise I've already squashed it.
[x] I've run npm run build to build the extension. (If I had done something with the extension.)

The icon from pugjs/pug-logo was resized to 32x32 and rezipped.  The file name is unchanged.

Thanks @olzaragoza!! It will be published in the next release :wink: :+1:

Wow, super quick response and merge.  Thanks for creating an awesome extension.  I just recently discovered it, and it's very helpful when working with a large and diverse file tree.

1.6.6 is out!


chore(vm): Expose more pubs and make inmemory clonable

What ❔

Why ❔

Checklist

[ ] PR title corresponds to the body of PR (we generate changelog entries from PRs).
[ ] Tests for the changes have been added / updated.
[ ] Documentation comments have been added / updated.
[ ] Code has been formatted via zk fmt and zk lint.
[ ] Spellcheck has been run via cargo spellcheck --cfg=./spellcheck/era.cfg --code 1.

Please update the PR description (and revert the 'contracts' change)


[Bug]: Python builds fail with "Cannot pip install google-api-core[grpc,grpcgcp]"

What happened?
Python jenkin jobs that requires install apache-beam[gcp] all fail.
Issue Priority
Priority: 0
Issue Component
Component: build-system

There is another dep error coming from atomicwrites, also fixing it in this issue

Per #22218 this also affects released version installation. An workaround is to install google-cloud-bigquery-storage<2.14 prior to installing apache-beam. For docker file, e.g.
RUN pip install google-cloud-bigquery-storage==2.13.0
RUN pip install apache-beam[gcp]==2.40.0

Needs reopen because the rollout of google-cloud-pubsub 2.13.2 triggered the exactly same problem

How severe is this? Do we need a point release? Or will this be solved by upstream updates (that are hopefully in progress)?

How severe is this? Do we need a point release? Or will this be solved by upstream updates (that are hopefully in progress)?

It affects all released versions. Per https://github.com/apache/beam/issues/22218#issuecomment-1180807519 "currently causing fairly severe issues".
imo this should be resolved upstream. We can only provide workaround for installation (manually install some sub-latest deps before pypi install apache-beam). The dep requirements itself does not have problems, but due to and upstream client lib bumping api-core major version in there patch release we unfortunately hit a pypi resolving issue/bug

So, pretty much anyone who does pip install apache-beam[gcp] will encounter a failure?

So, pretty much anyone who does pip install apache-beam[gcp] will encounter a failure?

Yes, if their environment does not have compatible google-clout-* client packages already installed.
THen pypi will try to install these deps and go endless backtracking

Let's use https://github.com/apache/beam/issues/22218 for further tracking which now has more discussion and workarounds.

Let's use https://github.com/apache/beam/issues/22218 for further tracking which now has more discussion and workarounds.


Is the text for #29 "Custom Fields and Logic" correct?

The text shown for #29 at https://tobiashofmann.github.io/sap-dev-tech-radar/html/customfields.html looks to be a copy of what is shown for BOPF at #37 https://tobiashofmann.github.io/sap-dev-tech-radar/html/bopf.html
Is that intentional or accidental?
Btw, neat and helpful overview!
Cheers
Bärbel

You are right, the text wasn't correct. The item should now have to correct text for Custom Fields and Logics.


activator missing

I am following the developer manual, it says to start the web server, run "activator run", but there isn't an activator command...

did some research and installed play! https://www.playframework.com/documentation/2.3.x/Installing
this did it


Get certificate reconciler from networking instead of control-protocol

Follow-up for https://github.com/knative/networking/pull/802
Proposed Changes

Get certificate reconciler from networking instead of control-protocol
Bump all dependencies with hack/update-deps.sh --upgrade
Drop control-protocol as a dependency

Release Note
NONE

/cc @davidhadas, @dprotaso


Fix BaseNEncoder number of output columns

BaseNEncoder encoder used an incorrect formula for calculating the number of required bits in the output. If there are nvals distinct values and we reserve one encoding to represent "missing or unknown", then the correct number of bits is ceil(log(nvals + 1, base)). However, the code was previously using the formula ceil(log(nvals, base)) + 1.
Fixes https://github.com/scikit-learn-contrib/category_encoders/issues/264
Proposed Changes

Change the formula to ceil(log(nvals + 1, base)).
Switch the formula to use integer math so we don't have to worry about floating point rounding errors.
Add a test.
Fix a non-deterministic test.

@janmotl @wdm0006 this is ready review, could you take a look?

I updated the code to use the formula ceil(log(nvals + 1, base)), which has a more obvious derivation than floor(log(nvals, base)) + 1. The two formulas return the same results for integers nvals and base.

Looks like the basen encoding tests are passing fine but theres an issue in master for the GLM encoding unrelated to this PR. Going to go ahead and merge this, thanks for the patience.