build "Hello world" error in windows11 docker

Hi, I installed "Docker Desktop" software and create a docker image in windows11 by docs (https://google.github.io/mediapipe/getting_started/install.html#installing-using-docker).
But, it builds failed when I run "Hello world" example.
How to solve it ???
scripts:
GLOG_logtostderr=1 bazel run --define MEDIAPIPE_DISABLE_GPU=1 mediapipe/examples/desktop/hello_world
log results:
root@6bcfd07b9f75:/mediapipe# GLOG_logtostderr=1 bazel run --define MEDIAPIPE_DISABLE_GPU=1 mediapipe/examples/desktop/hello_world
DEBUG: /root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'com_google_absl' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'com_google_benchmark' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'flatbuffers' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'pybind11_bazel' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'com_googlesource_code_re2' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'com_google_protobuf' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'com_google_googletest' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'com_github_gflags_gflags' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'zlib' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'rules_python' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'build_bazel_rules_apple' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'build_bazel_rules_swift' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'build_bazel_apple_support' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'xctestrunner' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'pybind11' because it already exists.
WARNING: /mediapipe/mediapipe/framework/BUILD:54:24: in cc_library rule //mediapipe/framework:calculator_cc_proto: target '//mediapipe/framework:calculator_cc_proto' depends on deprecated target '@com_google_protobuf//:cc_wkt_protos': Only for backward compatibility. Do not use.
WARNING: /mediapipe/mediapipe/framework/tool/BUILD:184:24: in cc_library rule //mediapipe/framework/tool:field_data_cc_proto: target '//mediapipe/framework/tool:field_data_cc_proto' depends on deprecated target '@com_google_protobuf//:cc_wkt_protos': Only for backward compatibility. Do not use.
INFO: Analyzed target //mediapipe/examples/desktop/hello_world:hello_world (0 packages loaded, 0 targets configured).
INFO: Found 1 target...
ERROR: /root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/com_google_protobuf/BUILD:208:11: Compiling src/google/protobuf/wire_format.cc failed: (Exit 1): gcc failed: error executing command /usr/bin/gcc -U_FORTIFY_SOURCE -fstack-protector -Wall -Wunused-but-set-parameter -Wno-free-nonheap-object -fno-omit-frame-pointer -g0 -O2 '-D_FORTIFY_SOURCE=1' -DNDEBUG -ffunction-sections ... (remaining 38 arguments skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
during RTL pass: final
external/com_google_protobuf/src/google/protobuf/wire_format.cc: In static member function 'static uint8_t* google::protobuf::internal::WireFormat::InternalSerializeField(const google::protobuf::FieldDescriptor*, const google::protobuf::Message&, uint8_t*, google::protobuf::io::EpsCopyOutputStream*)':
external/com_google_protobuf/src/google/protobuf/wire_format.cc:1420:1: internal compiler error: Segmentation fault
}
^
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-8/README.Bugs> for instructions.
Target //mediapipe/examples/desktop/hello_world:hello_world failed to build
Use --verbose_failures to see the command lines of failed build steps.
INFO: Elapsed time: 2.449s, Critical Path: 2.36s
INFO: 174 processes: 129 internal, 45 processwrapper-sandbox.
 You probably can try some other version of gcc such as gcc9. See instructions at https://linuxconfig.org/how-to-switch-between-multiple-gcc-and-g-compiler-versions-on-ubuntu-20-04-lts-focal-fossa.

Hi @zhangming8 The error message text external/com_google_protobuf/src/google/protobuf/wire_format.cc:1420:1: internal compiler error: Segmentation fault } it is indicative of the error being an internal compiler error. You probably can try some other version of gcc such as gcc9. See instructions at https://linuxconfig.org/how-to-switch-between-multiple-gcc-and-g-compiler-versions-on-ubuntu-20-04-lts-focal-fossa.

Hi, thanks. I build success by changing gcc to version 9, but another ERROR was found when I build autoflip(https://google.github.io/mediapipe/solutions/autoflip.html):
root@6bcfd07b9f75:/mediapipe# bazel build -c opt --define MEDIAPIPE_DISABLE_GPU=1 mediapipe/examples/desktop/autoflip:run_autoflip
DEBUG: /root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'com_google_absl' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'com_google_benchmark' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'flatbuffers' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'pybind11_bazel' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'com_googlesource_code_re2' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'com_google_protobuf' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'com_google_googletest' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'com_github_gflags_gflags' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'zlib' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'rules_python' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'build_bazel_rules_apple' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'build_bazel_rules_swift' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'build_bazel_apple_support' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'xctestrunner' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'pybind11' because it already exists.
INFO: Build option --compilation_mode has changed, discarding analysis cache.
WARNING: /mediapipe/mediapipe/framework/tool/BUILD:184:24: in cc_library rule //mediapipe/framework/tool:field_data_cc_proto: target '//mediapipe/framework/tool:field_data_cc_proto' depends on deprecated target '@com_google_protobuf//:cc_wkt_protos': Only for backward compatibility. Do not use.
WARNING: /mediapipe/mediapipe/framework/BUILD:54:24: in cc_library rule //mediapipe/framework:calculator_cc_proto: target '//mediapipe/framework:calculator_cc_proto' depends on deprecated target '@com_google_protobuf//:cc_wkt_protos': Only for backward compatibility. Do not use.
INFO: Analyzed target //mediapipe/examples/desktop/autoflip:run_autoflip (0 packages loaded, 5647 targets configured).
INFO: Found 1 target...
ERROR: /root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/com_github_glog_glog/BUILD:5:13: Compiling src/raw_logging.cc [for host] failed: undeclared inclusion(s) in rule '@com_github_glog_glog//:glog':
this rule is missing dependency declarations for the following files included by 'src/raw_logging.cc':
'/usr/lib/gcc/x86_64-linux-gnu/9/include/stddef.h'
'/usr/lib/gcc/x86_64-linux-gnu/9/include/stdarg.h'
'/usr/lib/gcc/x86_64-linux-gnu/9/include/stdint.h'
Target //mediapipe/examples/desktop/autoflip:run_autoflip failed to build
Use --verbose_failures to see the command lines of failed build steps.
INFO: Elapsed time: 0.764s, Critical Path: 0.49s
INFO: 140 processes: 140 internal.
FAILED: Build did NOT complete successfully
It seams like missing some of head files, but they do exist ???
root@6bcfd07b9f75:/mediapipe# ls /usr/lib/gcc/x86_64-linux-gnu/9/include/stddef.h
/usr/lib/gcc/x86_64-linux-gnu/9/include/stddef.h
root@6bcfd07b9f75:/mediapipe# ls /usr/lib/gcc/x86_64-linux-gnu/9/include/stdarg.h
/usr/lib/gcc/x86_64-linux-gnu/9/include/stdarg.h
root@6bcfd07b9f75:/mediapipe# ls /usr/lib/gcc/x86_64-linux-gnu/9/include/stdint.h
/usr/lib/gcc/x86_64-linux-gnu/9/include/stdint.h
root@6bcfd07b9f75:/mediapipe#

@zhangming8 This looks like an issue with binaries compiled with old gcc version. Now that you have switched the gcc, please run bazel clean --expunge command, and then try running the build command again.


Dense Transfer Controllers becoming Sequential

Just noticed this is happening, where the user schedule is Streaming (correct) but the schedule gets set to sequential:
              x193 = UnitPipe(Set(b173),Block(Const((): class scala.runtime.BoxedUnit))) {
               - class spatial.data.ControlSchedule: ControlSchedule(Sequenced)
               - class spatial.data.UserScheduleDirective: UserScheduleDirective(Streaming)

Should the controlSchedule flow have a rule to choose the Streaming schedule if it is defined at the end of the flow, like this?
if (s.isOuterControl && s.getUserSchedule.isDefined && s.getUserSchedule.get == Streaming) s.rawSchedule = Streaming

It seems like the unrolling transformer is losing some information because it doesn't follow this flow, but if retime is turned on then the flow is called there and it is correct by the last IR.  Maybe this is because of the mutate transformer and the order that it copies metadata?  I also see this happening with a Sequential.Foreach becoming a Pipeline by the last IR.  I'm using FIFOLoadSRAMStore for debugging this.

Fixed in 4aa747881725d48a53e73f2b6529a46227d793c1


Regression test for rdar://problem/29716016.

Swift 3.0 failed to diagnose reassignments of an immutable existential variable if its initialization was governed by DI.

@swift-ci Please smoke test and merge


Updated OpenFHE with the latest bugfixes from Palisade

Closes #149:
https://gitlab.com/palisade/palisade-development/-/merge_requests/387 - Ian
https://gitlab.com/palisade/palisade-development/-/merge_requests/388 - Ian
https://gitlab.com/palisade/palisade-development/-/merge_requests/389 - Ian
https://gitlab.com/palisade/palisade-development/-/merge_requests/393 - Nick
https://gitlab.com/palisade/palisade-development/-/merge_requests/394 - Matt

manually started 4 CI jobs.


PSR Http client and redirects

SendRequest method in Client.php  disables redirects.
Is there any reason why? This behavior is hardcoded and cannot be overriden. As I know PSR HTTP client does not prohibit redirects.
Current behavior should be removed until stable version released.

Yes.. in a way it does not clearly states it... but the PSR mentions

A second goal is that HTTP clients can be replaced as per the Liskov substitution principle. This means that all clients MUST behave in the same way when sending a request.

So the point is that a PSR HTTP client must always return the response AS IS and the consumer should choose how to handle the response.
if we allowed or opt-in the redirects then we could never fulfill the above PSR statement.

Well it is not easy to make a decision. You wrote client must always return the response AS IS. This means every middleware which changes response (eg deflate gzipped response body) has to be disabled.
Personally I would allow redirects. If anyone wants to turn it off, it could be done in constructor config.

client must always return the response AS IS

OK let me rephrase it/extend it a bit..
What I meant is that if you have this kind of code:
$this->psrClient->sendRequest(new Request('GET', 'www.UrlThatRedirects.com') === 301;

The code above works depending on the configuration of the client... follow redirects or not... Which breaks the LSP.
BTW there are many useful things to be read also in the metadocument of the PSR-18

https://www.php-fig.org/psr/psr-18/meta/#default-behavior
https://www.php-fig.org/psr/psr-18/meta/#middleware-and-wrapping-a-client

Also the discussions that lead to the PSR-18 can be found here.. you might find more useful things.
https://github.com/php-http/fig-standards/issues

I understand what you mean. I wrote that with your point of view all middlewares which can modify response have to be disabled too.
Example:
Decode content option is not disabled in sendRequest method.
Then this code will not work:
$response = $psrClient->sendRequest(new Request('GET', 'http://www.example.com/foo.gz');
$body = gzinflate((string) $response->getBody());

Btw. This means that all clients MUST behave in the same way when sending a request.
That may mean response cannot be modified too (eg adding Auth header from constructor config).
I suggest that the current redirect behavior remain same - opt-in.

Ha.. I knew I have seen somewhere about the gzip thing.. https://github.com/php-http/fig-standards/issues/37
Not sure what answers you can get from that discussion though.. IMHO I quite agree with this comment https://github.com/php-http/fig-standards/issues/37#issuecomment-328107526

The default http client should not follow redirects. However, if you as an application author adds middleware to "follow redirects" you have intentionally broken the contract and you have to suffer the consequences (or be happy that it just works).

I suggest that the current redirect behavior remain same - opt-in.

That is not possible, that would mean that Guzzle is useless as PSR-18 out of the box.


require is not defined because, apparently the most recent versions of Browserify do not expose require to the global scope

The example provided in the example repository will not work with the latest version of Browserify, because seems like Browserify does not expose the require() method the global scope.
What can be done for using the modules with the magical require()?

Sorry, was on leave - I'll look into how to fix this. Until then, the non-module form should still work.

In my testing, require() is still provided by the latest version, 13.1.0; are you using 'browserify -r YourModuleHere' ?


A panic occurs when there is a change in cluster information and the instance being updated.

Is this a regression?
No
Description

file : tools/pika_exporter/exporter/metrics/metrics.go
A panic occurs during the update process when there are existing related metrics in the MetricConfigs.
Please provide a link to a minimal reproduction of the bug
No response
Screenshots or videos
No response
Please provide the version you discovered this bug in (check about page for version information)
Pika & Codis v3.5.2

MacOS上启动Pika、Codis和Pika_exporter

Anything else?
No response

复现方法是启动exporter之后，对集群的信息进行变更，比如添加或者删除一个pika，之后在进行更新的时候，会因为MetricConfigs中已经存在数据而导致panic，我本地在更新之前对MetricConfigs进行清空，可以解决这个问题。

https://github.com/OpenAtomFoundation/pika/pull/2083 引入问题


enable autoload for command-line scripts

fixes #6360
Note that while this might look like a lot of changes, it's only because of indentation. Only real difference is in conditions: autoload code is executed if either game_path or script is non-empty.

Here's a GitHub trick to see the diff without the indentation changes: https://github.com/godotengine/godot/pull/6413/commits/8ddc0b697b26797d2d5682a9112dff59c950b22a?w=1

@akien-mga , thanks for the tip. I wonder why it's a hidden feature.


Update Grunt

Now that Grunt 1.0.0 has been released, the dependency grunt": "~0.4.1" is not satisfied anymore.

+1

+1 Pleeaaaasee!!!

Done, apologies for the delay.


Figure out how to "upload" resources to GitHub

Fixes #7
I have done my implementation based on PRs created for https://github.com/humphd/my-photohub/issues/1 and https://github.com/humphd/my-photohub/issues/4
Please review and let me know if this is the right approach. Feel free to review and request for changes.

@saminarp  Given that you coded the functions elegantly, I did not want to point out that App was imported but not used because it was too minor. Good work.

I have updated my implementation, let me know how it is


Tag for v15.3.0 seems to be missing from react-bower

Version 15.3.0 has been published on npm, and the code was pushed to this repo. However, it looks like the actual tag has not been created/pushed.

Fixed, sorry about that!


Upgrade guide does not guarantee backwards compatibility

The upgrade instructions since 1.6 in the recommended path are causing non-backwards compatible changes to a deployment.
1.7 -> 1.8

Auto enabling dynamic BPF map sizes

+  # Specifies the ratio (0.0-1.0) of total system memory to use for dynamic
+  # sizing of the TCP CT, non-TCP CT, NAT and policy BPF maps.
+  bpf-map-dynamic-size-ratio: "0.03"

Auto opt into cluster pool IPAM

+  k8s-require-ipv4-pod-cidr: "true"
+  ipam: "cluster-pool"
+  cluster-pool-ipv4-cidr: "<IP_ADDRESS>/8"
+  synchronize-k8s-nodes: "true"

Disabling CNP

+  disable-cnp-status-updates: "true"

1.6 -> 1.7

Remote node identities

+  enable-remote-node-identity: "true"

Monitor aggregation difference:

monitor-aggregation-flags: all

vs
pkg/option/config.go:   MonitorAggregationFlagsDefault = []string{"syn", "fin", "rst"}

1.5 -> 1.6

Auto opt-in to CRD
Change in aggregation

-  monitor-aggregation: "none"
+  monitor-aggregation: medium

Disabling container runtime

+  container-runtime: none

monitor-aggregation
monitor-aggregation-flags

What's your threshold for backwards compatibility? These options reduced the number of notifications from the BPF datapath to the userspace / monitor but they should not impact forwarding/routing/policy during upgrade or post-upgrade.

RFC for this hackity hack https://github.com/cilium/cilium/pull/12080
I also have another branch with a differen proposal which seems the be the "correct" way of solving but I would like Sean's input (on all proposals actually)
https://github.com/cilium/cilium/commit/d9472bc1058ac59e0ffdea488d0e14a34a7a75bd

What's your threshold for backwards compatibility? These options reduced the number of notifications from the BPF datapath to the userspace / monitor but they should not impact forwarding/routing/policy during upgrade or post-upgrade.

I haven't necessarily classified it much but listed the unintended behavioral changes. I'm not sure we made the conscious decision to change this during upgrades.

This is something that could work:
diff --git a/install/kubernetes/cilium/charts/config/templates/configmap.yaml b/install/kubernetes/cilium/charts/config/templates/configmap.yaml
index c1eb5ec2c..63819c8cd 100644
--- a/install/kubernetes/cilium/charts/config/templates/configmap.yaml
+++ b/install/kubernetes/cilium/charts/config/templates/configmap.yaml
@@ -514,6 +514,6 @@ data:
 {{- end }}
 {{- end }}

-{{- if .Values.global.cnpStatusUpdates }}
-  disable-cnp-status-updates: {{ not .Values.global.cnpStatusUpdates.enabled | quote }}
+{{- if or .Values.disableCnpStatusUpdates (not .Values.upgradeCompatibility) }}
+  disable-cnp-status-updates: {{ default true (.Values.disableCnpStatusUpdates) | quote }}
 {{- end }}
diff --git a/install/kubernetes/cilium/charts/config/values.yaml b/install/kubernetes/cilium/charts/config/values.yaml
index 806f198c1..a7099719f 100644
--- a/install/kubernetes/cilium/charts/config/values.yaml
+++ b/install/kubernetes/cilium/charts/config/values.yaml
@@ -7,3 +7,9 @@
 # - azure
 # - crd
 ipam: "cluster-pool"
+
+# disableCnpStatusUpdates disables CiliumNetworkPolicy status updates
+#
+# Default: true (updates disabled)
+#
+#disableCnpStatusUpdates: true
diff --git a/install/kubernetes/cilium/values.yaml b/install/kubernetes/cilium/values.yaml
index 5afa834f8..fa817114b 100644
--- a/install/kubernetes/cilium/values.yaml
+++ b/install/kubernetes/cilium/values.yaml
@@ -568,9 +568,6 @@ global:
   healthChecking:
     enabled: true

-  cnpStatusUpdates:
-    enabled: false
-
   affinity:
     podAntiAffinity:
       requiredDuringSchedulingIgnoredDuringExecution:

Setting disableCnpStatusUpdates either in values.yaml or using --set will force the value. Otherwise it will default to true (to disable CNP) unless config.upgradeCompatibility is set.

Developing this further, we could provide version-specific new defaults with something like this:
{{- if or .Values.disableCnpStatusUpdates (or (not .Values.upgradeCompatibility) (semverCompare ">=1.8" $upgradeCompatibility)) }}
   disable-cnp-status-updates: {{ default true (.Values.disableCnpStatusUpdates) | quote }}
{{- end }}

It is possible but adds considerable complexity

Separating breaking vs non-breaking sections is definitely a very good idea. It's a bit unfortunate that Helm templates are the only means of defining this logic right now, but ways of getting past that would involve some new machinery that cannot be brought in for 1.8.


Fixes #1369 select-list deprecation

Fixes #1369.

The new ember-rapid-forms select helper mutates the specified property automatically, while the old one required an action. This is a reason for some of the refactoring.
Other refactoring because the new one wouldn't work with a simple array (at least I couldn't get it to), so there's some code to change arrays into key/value object arrays.
This PR will fail one of the acceptance tests until a new version of ember-rapid-forms is released which fixes an issue encountered in ember-rapid-forms during this work. This will probably be within the next couple weeks. See: https://github.com/piceaTech/ember-rapid-forms/issues/193
In one instance, language-select.hbs, I went with a native HTML select instead of the ember-rapid-forms select, because the ember-rapid-forms one was adding Bootstrap CSS and caused the appearance to change. Let me know if you'd prefer it done another way. See imgur.com/a/h0ljX1A.
Thanks @ben-muldrow for the initial work on this, @efx for reviewing and @gcorbel for helping us with ember-rapid-forms.

cc @HospitalRun/core-maintainers

Alright, the form-within-a-form is definitely something I should fix. After more research, it's not valid HTML, and also doesn't work on FireFox. So I will start looking into this and update in couple days.

Fixing that also allowed me to remove the added computed property in invoices/edit controller. Now it should be ready to finish reviewing.

@MatthewDorner while it's not merged... Would you mind to remove ember-views.did-init-attrs from our deprecation-workflow list as of #1370? It shouldn't throw this deprecation anymore.

Thank you @MatthewDorner for the PR!


Create quest-splits

This is a plugin for the speedrunning worlds, which allows autosplits based on items, like LiveSplits

Don't unnecessarily spam the logs with debug items. If you wish to keep your logging in, use log.debug() instead.


Develop

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.0 out of 2 committers have signed the CLA.:x: Samuel Ventimiglia:x: Davide BiasinSamuel Ventimiglia, Davide Biasin seem not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.


Will the annotator alpaca_eval_gpt4_turbo_fn also change?

May I confirm if the annotator alpaca_eval_gpt4_turbo_fn will also consistently change and affect the final (length control) win rates?

Yes, that depends on OpenAI API and there's nothing we can do about the model silently changing.


Logger shutdown

Hi,
I just starting to work with NLog.
I wrote a wrapper for the logger, to unify work with logger for all our applications.
In configuration of the logger I use AsyncWrapper for better performance, and found a recommendation to use LogManager.Shutdown method to ensure that no log prints will be lost when application is shutting down.
I know nothing about the application, that going to use my logger wrapper - it can be web app, executable or any other...
So my questions are:
Is there any recommendation where to call LogManager.Shutdown method?
Is it good idea to call LogManager.Shutdown in my wrapper finalizer?
Does NLog takes care about it and I don't need to call LogManager.Shutdown method?
Is it any configuration I can use instead of calling LogManager.Shutdown?
Bottom line: What is the right way to do that?
Thanks,
Aleksey

Only the main application should call NLog.LogManager.Shutdown().
If you have a library/component then you probably have a Close/Dispose-method to stop own timers/threads/etc. In that method then you can call NLog.LogManager.Flush().
NLog has an auto-flush/auto-close on AppDomain-Unload, but it is not super-reliable, as shutdown is tricky business as it will be aborted prematurely if not fast enough to complete the shutdown.

I assume your question has been answered, if not, please let us know!

Does it matter if I call Shutdown() in the Main() method or in my main class's destructor?

Does it matter if I call Shutdown() in the Main() method or in my main class's destructor?

Please create new issue for your own question, since this issue is closed. Btw. i c# then class destructor usually means finalizer and those are not guaranteed to be called. Better to use Dipose or in finally in main-method.


feat: OPTIC-116: User soft-deletion API

This PR introduces a soft deletion API.  The core api.UserAPI already includes a deletion endpoint, so this API uses a separate UserSoftDeleteView which appends soft-delete/ to the deletion endpoint to differentiate it from the standard deletion endpoint.
Permissions here are a bit tricky as role permissions are required in LSE but need to be accommodated in the endpoint defined in LS, to handle this I've added a USER_PERM setting which specifies which permission class to use.   LS currently allows only owners to delete users.
PR fulfills these requirements

[x] Commit message(s) and PR title follows the format [fix|feat|ci|chore|doc]: TICKET-ID: Short description of change made ex. fix: DEV-XXXX: Removed inconsistent code usage causing intermittent errors
[x] Tests for the changes have been added/updated (for bug fixes/features)
[ ] Docs have been added/updated (for bug fixes/features)
[ ] Best efforts were made to ensure docs/code are concise and coherent (checked for spelling/grammatical errors, commented out code, debug logs etc.)
[x] Self-reviewed and ran all changes on a local instance (for bug fixes/features)

Change has impacts in these area(s)
(check all that apply)

[ ] Product design
[ ] Backend (Database)
[x] Backend (API)
[ ] Frontend

Describe the reason for change
(link to issue, supportive screenshots etc.)
What does this fix?
(if this is a bug fix)
What is the new behavior?
(if this is a breaking or feature change)
What is the current behavior?
(if this is a breaking or feature change)
What libraries were added/updated?
(list all with version changes)
Does this change affect performance?
(if so describe the impacts positive or negative)
Does this change affect security?
(if so describe the impacts positive or negative)
What alternative approaches were there?
(briefly list any if applicable)
What feature flags were used to cover this change?
(briefly list any if applicable)
Does this PR introduce a breaking change?
(check only one)

[ ] Yes, and covered entirely by feature flag(s)
[ ] Yes, and covered partially by feature flag(s)
[ ] No
[ ] Not sure (briefly explain the situation below)

What level of testing was included in the change?
(check all that apply)

[ ] e2e
[ ] integration
[ ] unit

Which logical domain(s) does this change affect?
(for bug fixes/features, be as precise as possible. ex. Authentication, Annotation History, Review Stream etc.)

/git merge develop


Add in initial code for the connector

Thanks for submitting the code.
I note there are some security issues reported
Not had a chance to look yet
See the 'security' tab above and click 'code scanning alerts'

@planetf1 I have fixed them


Be able to specify a particular profile for splitMode in splitPane action

Description of the new feature/enhancement
It would be really helpful to be able to specify a particular profile or command line executable to run with the splitMode option for an action to split the pane. The scenario being that I want to open up a side pane that runs a particular command or shell by hitting a key binding.
Proposed technical implementation details (optional)
The preferred option would be to specify a specific executable to open in the new pane, something like:
{ "command": { "action": "splitPane", "split": "auto", "cmdline": "<mypath>/pwsh.exe" }, "keys": "alt+shift+d" },

Alternatively it would be nice to specify the profile which then specifies the specific command name:
{ "command": { "action": "splitPane", "split": "auto", "profile":<Name of Profile> }, "keys": "alt+shift+d" },

Should've tested the profile case out before submittined 🙃 that works, closing this issue.


Convert line endings in the mvnw

We have a received a number of bug reports from developers struggling to build apps using the maven wrapper:
https://github.com/GoogleCloudPlatform/buildpacks/issues/149
https://github.com/GoogleCloudPlatform/buildpacks/issues/58
After snooping around at other buildpack implementations I suspect there is problem with the wrapper is using Windows' line endings<cr><lf> instead of unix style `. We should be able to fix this using a find and replace on the mvnwrapper before we invoke it in the maven buildpack

Hey, @matthewrobertson, I would like to work on this issue. Could you please assign it to me?

This was fixed with https://github.com/GoogleCloudPlatform/buildpacks/commit/2f2feac0ab2edc2b3fb05bdd4868aa9603cc24c3

@aserputov sorry we had already assigned this issue to an internal owner. I believe the same issue exists for the gradle wrapper if you want to take a crack at that.

@matthewrobertson no problems, thanks


[Bug] = failed to initialize storage reader. tablet=950075.1876649455.5742591db139a094-1ae65906f977328f, res=-3109, backend=xx.xx.xx.xx

Search before asking

[X] I had searched in the issues and found no similar issues.

Version
0.15,1.0
What's Wrong?

show tablet 950075

What You Expected?
not wrong
How to Reproduce?
No response
Anything Else?
No response
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

我也遇上这个问题，请问解决了吗？

停了routineload一段时间，这个问题消失了，我想可能是导入太频繁需要compact的未完成导致的


Scale input to account for deadzones

Objective
Fixes #3450
Solution
Scale the input to account for the range
Testing
Updated unit tests

I can't work on fixing the unit tests until this is fixed:
error[E0599]: no method named `to_string` found for reference `&str` in the current scope
   --> crates\bevy_ecs\src\name.rs:252:24
    |
252 |         Ok(Name::new(v.to_string()))
    |                        ^^^^^^^^^ method not found in `&str`
    |
    = help: items from traits can only be used if the trait is in scope
help: trait `ToString` which provides `to_string` is implemented but not in scope; perhaps you want to import it
    |
3   + use crate::alloc::string::ToString;

For the alloc error, I think you need to fix the feature flags in a new PR. @bushrat011899, FYI.

For the alloc error, I think you need to fix the feature flags in a new PR. @bushrat011899, FYI.

He's already got that in the no_std bevy_input PR.

Can confirm I have this issue resolved in the no_std bevy_input PR, along with some other issues with how bevy_input feature gates bevy_reflect

Let's do a quick migration guide noting this change (since it's otherwise surprising), but this LGTM now. Good work on the tests; I like the balance you struck.

Sorry for the noise. I realized that I could make the implementation and test data cleaner by storing the raw values in the gamepad, which means the old values will be raw values. Everything is very optimal now, imo.

Migration guide made me realize the doc comment should be improved. Both are done now.

Personally, I think deadzone is a more high-level functionality and should be handled by input managers

Agreed. In the medium term, I think this functionality should be removed from bevy_input and moved up a level. But until we have a first party input manager / action crate we're blocked there.

I think deadzones and scaling are good here because they have to do with accounting for the hardware limitations. Before then, the events are "raw". The part I would move into another crate is actually the clamping/rounding. Those are more about what " feels right".

I would consider bevy_input as a source for raw input and its processing being a higher-level abstraction. That's what I currently do with my crate (I use methods that return raw values and let user apply any modifiers on top of them).
We on the same page with @alice-i-cecile, this PR is good.
I just wanted to share my thoughts for possible future considerations.


[BUG][Spark][Delta 2.2][Backport] OSS break Identity (writer version 6) protocol

Bug
Which Delta project/connector is this regarding?

[X] Spark
[ ] Standalone
[ ] Flink
[ ] Kernel
[ ] Other (fill in here)

Describe the problem
It allows to write to Delta Table where writer version is 6, and given Identity column is not supported, it breaks the protocol, by allowing explicit values and not updating highWaterMark
Steps to reproduce
Create a table with Identity Column (you need another library, OSS don''t support it):
CREATE OR REPLACE TABLE delta.path.... (
id BIGINT GENERATED ALWAYS AS IDENTITY,
product_type STRING,
sales BIGINT
);
Using OSS append new data:
val df = spark.createDataFrame(Seq((1, "ABC", 10)))
.toDF("id", "product_type", "sales")
df.write.mode("append").format("delta").save("path...")
UPDATE: repro without Identity, OSS library only:
CREATE TABLE MyTestProtocol USING DELTA AS SELECT col1 as id FROM VALUES 0,1,2,3,4;
ALTER TABLE MyTestProtocol SET TBLPROPERTIES('delta.minReaderVersion' = '1', 'delta.minWriterVersion' = '6');
INSERT INTO MyTestProtocol VALUES (1);
DESCRIBE EXTENDED MyTestProtocol;

Observed results
Insert successfully. But break the identity.
Expected results
Error
Further details
The fix was backported to 2.3, but missed 2.2: https://github.com/delta-io/delta/pull/1722.
Opening this issue to track it.
Environment information

Delta Lake version: 2.2.0
Spark version: 3.3.1
Scala version: 2.12

Willingness to contribute
The Delta Lake Community encourages bug fix contributions. Would you or another member of your organization be willing to contribute a fix for this bug to the Delta Lake code base?

[ ] Yes. I can contribute a fix for this bug independently.
[ ] Yes. I would be willing to contribute a fix for this bug with guidance from the Delta Lake community.
[X] No. I cannot contribute a bug fix at this time.

This is important bug, should we add to 2.4.1? https://github.com/delta-io/delta/milestone/23
@xupefei, @allisonport-db, @vkorukanti

I found that Delta 2.2 does not support Table Features, thus a direct backport is impossible. I'll try to implement a new solution.


Upgrade to kustomize/v5.2.1, add support for oci helm repos

Fixes https://github.com/kbst/terraform-provider-kustomization/issues/242

LGTM, thanks for the contribution!


Astro web

Change Summary
Small changes

Changed BlogLayout to Cheatsheet (it makes more sense)
Removed all Back to top links in all sheets
Added a back to top button in all pages (via cloudflare apps, not in the code itself)

Bigger ones

Moved table of contents to the left, and it now renders appropriate number of #s depending on the title
The TOC is now sticky, so it will stay even after scrolling

Added search option

Checklist
If you haven't fulfilled the below requirements or even delete the entire checklist, your PR won't be reviewed and will be closed without notice.
General

[x] This Pull Request is all my own work. (You'll be blacklisted if you are caught for plagiarism.)
[x] I've read CONTRIBUTING.md
[x] I've made some valid changes to the CheatSheet, and they are not just minor changes.

Changes

[x] I've read and followed the Solution Template

Note: To mark the checkbox, put an x inside the [ ] (like this: [x]).

You can check the deployed version https://cheats.dhr.wtf
Solves #170, Major fix for a lot of files

You surely amaze me with some exciting upgrades every time 🍁


Could torchgpipe run on CPU-only machines?

Dear torchgpipe team,
Thanks for sharing the code! I wonder could torchgpipe is suitable for the CPU-only machine/machines? Or any other possible method to deploy it on CPU-only environments? Thanks!

Do you just want to run torchgpipe-based code on CPU-only environments without performance benefit from pipeline parallelism? Then you can specify 'cpu' or ['cpu', 'cpu', ...] for devices option of GPipe. Despite torchgpipe cannot boost model performance without GPUs, this behavior was useful to unit test torchgpipe itself.
https://github.com/kakaobrain/torchgpipe/blob/a1b4ee25574864e7650e7905a69ce156da9752ec/tests/test_gpipe.py#L42-L59

Thank you very much for this reply, and want to double-check this is not for the CPU-only environment for multiple machines, right? I can only run the script mentioned in the CPU-only environment on a single device, is it?

You understood correctly. torchgpipe does not have a responsibility on multi-node environments.

Thank you very much!


Progress Bar

Pull Request Template

Please Fill all the details. It will help us to track issues and Pull Request.

What have you Changed - I added a method create_progress_bar in notifly.py and updated the methods send_image & send_document to use it in the post request.
Issue no.(must) - #15
Self Check(Tick After Making pull Request)

[x] This issue was assigned to me
[x] One Change in one Pull Request
[x] My file is in proper folder
[x] I am following clean code and Documentation.
[ ] I have added README.md with my script

@rexdivakar I am not understanding the commit conflict reported here, is there something I need to fix & fix on my side?

Hey @Kirkkm  Please update the fork and add in your changes, also support ur changes with screenshots !

Hey @Kirkkm Please update the fork and add in your changes, also support ur changes with screenshots !

Sounds good, will do.

@rexdivakar I updated my fork and added back my changes for the progress bar, also below is a screen shot of the progress bar in action.

Hey buddy @Kirkkm
The issue is TQDM is not showing the output scale during transmission, I need a progress bar which shows live movement of data during transmission

Hey buddy @Kirkkm
The issue is TQDM is not showing the output scale during transmission, I need a progress bar which shows live movement of data during transmission

@rexdivakar Ok, I will continue to work on it

@rexdivakar, not sure what I did but I am not ready to send another pull request yet. please ignore above message.

Closing your PR @Kirkkm  Thanks for ur effort

@rexdivakar no problem, will have a new PR ready hopefully here soon for the upload progress bar

Oh then i will reassign the issue to u, take ur time happy to have ur contribution and will share my insights about it soon @Kirkkm

@rexdivakar Yeah no worries, this is a interesting problem/feature to add and hopefully the solution I am developing will be good but if not would like to collaborate on a better solution.


Add visible property to column to make it simpler to show/hide

What kind of change does this PR introduce? (check one with "x")

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Other... Please describe:

What is the current behavior? (You can also link to an open issue here)
Difficult to change column visibility, need to add/remove from table options
What is the new behavior?
Set visible property on table column
Does this PR introduce a breaking change? (check one with "x")

[ ] Yes
[x] No

If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...
Other information:

Hmmm ... I see the use case but on the fence about it.

Since this can be accomplished via the current API, I'd rather not add more options to confuse people.


Update Hydrogen SDK

Still needs some work on the hydrogen side

Closing, we updated to the latest now


Background Parallax Scroll?

Are you planning to implement background parallax? since the demo only show the implementation on an element postition.

@ariona We very explicitly don't use background-image in our html code because Google can't index those images. We create a  wrapper with overflow:hidden and put an image inside of that . If you structure your code that way, you can still use Rellax!

I prefer this solution actually, since I'm building a theme in Wordpress, and background-image can lead to some wonky side effects. Would be nice to see an example of this in the pack though!

It would be great to have a "background mode" that deals with background-position property to create the parallax effect. Sometimes background image is the way to go...
I would love to see that in relax to avoid to install 2 plugins to manage parallax effects.

paroller.js handles both background images and DOM elements.

We very explicitly don't use background-image in our html code because Google can't index those images.
@moeamaya  Why do need every image to be indexed for Google Image Search?  (This is a legit question, btw. Not being snotty, just trying to learn!)  Your comment has made me analyze a few of my sites and some background images are so exclusive to the site design, I'm just trying to understand the case for why I would want those to show up in Image Search.  Does it benefit the overall site SEO maybe?


SO terms for polypeptide regions on nucleotides

There are several SO terms that are part_of polypeptide (SO:0000104):
mature_protein_region SO:0000419
propeptide SO:0001062
signal_peptide SO:0000418
transit_peptide SO:0000725
In GenBank, these 4 feature types can appear on both nucleotide and protein records. They are properly protein features, but for purposes of INSDC annotation they need to appear on nucleotides as well. It's also useful in other contexts (e.g. GFF3) to be able to designate a region on a nucleotide sequence that would correspond to one of these subregions of the CDS.
If I'm interpreting the ontology and specs correctly, polypeptide derives_from CDS SO:0000316, so technically those 4 child terms shouldn't be annotated on nucleotide sequences or have CDS as a Parent in GFF3 annotation. Do you agree?
If so, I'd like to request 4 equivalent terms as children of CDS_region SO:0000851. I don't suppose there's a precedent for how to name them? Maybe something like:

mature_protein_region_of_CDS - CDS region corresponding to a mature protein region of a polypeptide. Synonym: INSDC_feature:mat_peptide
propeptide_of_CDS - CDS region corresponding to a propeptide of a polypeptide. Synonym: INSDC_feature:propeptide
signal_peptide_of_CDS - CDS region corresponding to a signal peptide of a polypeptide. Synonym: INSDC_feature:sig_peptide
transit_peptide_of_CDS - CDS region corresponding to a transit peptide of a polypeptide. Synonym: INSDC_feature:transit_peptide
(I'm not particularly fond of that, but it's the best I could come up with. It has some similarity to RNA feature types and their corresponding genes, like rRNA vs rRNA_gene)

Those INSDC_feature synonyms could either be on both the new terms and the existing polypeptide terms, or only on the new terms. The GenBank and GenPept use the same terms on both, but "INSDC" is only a nucleotide feature spec, so if we want a 1:1 mapping then the INSDC_feature synonyms should be on the new terms.
-Terence

Hi Terrence,
How do you think codon, coding_end, and coding_start (the current children of CDS_region) would best fit when these are added? I am thinking perhaps they could stay as is_a CDS_region, but part_of mature_protein_region_of_CDS. Do you think that sounds correct?
Additionally, I am not sure if these would need any relationship with the protein equivalents. I am thinking perhaps relationships like signal_peptide relationship: derives_from ! signal_peptide_of_CDS. What do you think?
Thanks,
Dave

How do you think codon, coding_end, and coding_start (the current children of CDS_region) would best fit when these are added? I am thinking perhaps they could stay as is_a CDS_region, but part_of mature_protein_region_of_CDS. Do you think that sounds correct?

There's no obligation that the coding_start or coding_end is part of mature_protein_region_of_CDS. The start or end could be cleaved off during processing to make the final mature_protein. Codons in the CDS in general may or may not be part of mature_protein_region_of_CDS. My inclination is to not set a relationship between these.

relationships like signal_peptide relationship: derives_from ! signal_peptide_of_CDS

yes, that seems appropriate.

Hi Terrence,
The four new terms have been created:
id: SO:0002249; name: mature_protein_region_of_CDS
id: SO:0002250; name: propeptide_region_of_CDS
id: SO:0002251; name: signal_peptide_region_of_CDS
id: SO:0002252; name: transit_peptide_region_of_CDS
As usual, the terms should be updated in the SO Browser within about 24 hours. Have a nice day!
Dave

awesome, thanks!


Support reading OAuth Credentials from file paths from config.yaml

Signed-off-by: Haytham Abuelfutuh<EMAIL_ADDRESS>TL;DR
Flytekit/FlyteRemote is moving towards unifying config files with flytectl. This PR enables reading Client Secret from the file reference provided in the flytectl's config.yaml. It adds some other missing config mapping as well.
Type

[X] Bug Fix
[ ] Feature
[ ] Plugin

Are all requirements met?

[X] Code completed
[X] Smoke tested
[X] Code documentation added
[X] Any pending items have an associated Issue

Tracking Issue
https://github.com/flyteorg/flyte/issues/2214

friendly ping @wild-endeavor


remove build path dependency & fix debug image error

fix issue: https://github.com/mosn/extensions/issues/113  and https://github.com/mosn/extensions/issues/110


Add explicit instance for accessing mixed multipart decoder

Add an explicit instance to allow access to the mixed multipart decoder.
Referencing this discussion: https://gitter.im/http4s/http4s?at=5fecd60de7f693041f3efd9c

Hi @rossabaker. I can make a new 0PR to that branch. Coming right up


[Feature] adding custom path for download

please add args for customized path for download..
i'm using Android phone and this song store at my root path so i cant get that

You can specify the path with the -o parameter.
eg. music-dl -o /home/xxx

okay thanks for answering


Create HTML landing page for chart repository

Create an HTML landing page for charts.reactiveops.com with details about the incubator and stable chart repos.

I have reached out to marketing to provide the base page that I can add content to.

Saw an example from jetstack where they just redirected to the helm hub page.  I really like this idea and I will work on that instead.

The redirect to Helm Hub is setup:
https://charts.reactiveops.com


chore(spdk): update spdk

This update intends to include arm build fixes.
Update SPDK to the top tip of branch v22.01.x-mayastor with the
output of cmd: "nix-prefetch-git --fetch-submodules --rev
refs/heads/v22.01.x-mayastor git@github.com:openebs/spdk.git"
Update spdk-rs to the latest branch develop
Signed-off-by: Xinliang Liu<EMAIL_ADDRESS>This PR is related to Mayastor arm64 support: https://github.com/openebs/mayastor/issues/1063

bors merge

Hi @xin3liang seems like you would need to fix the formatting here first.
https://github.com/mayadata-io/spdk-rs/blob/a5bb8bcda22434745adcce11f02897338b7789ed/build.rs#L138

Should align with code, right? A.k.a:
        #[cfg(target_arch = "x86_64")]
        "spdk_bdev_crypto",

Hi @xin3liang seems like you would need to fix the formatting here first.
https://github.com/mayadata-io/spdk-rs/blob/a5bb8bcda22434745adcce11f02897338b7789ed/build.rs#L138

Should align with code, right? A.k.a:
        #[cfg(target_arch = "x86_64")]
        "spdk_bdev_crypto",

Here is the PR: https://github.com/mayadata-io/spdk-rs/pull/11

bors try

bors try

Let me update this RP to include mayadata-io/spdk-rs#11

Ahh, right. Please do the needful. Thank you.

bors merge


chore: increase workflow tick interval

Changes

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#941  👈
#932
#931
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @NathanFlurry and the rest of your teammates on  Graphite

Merge activity

Jun 25, 12:07 AM EDT: @NathanFlurry started a stack merge that includes this pull request via Graphite.


send and receive the max_ack_delay, use it for RTT estimation and PTO calculation

Fixes #1236.

Codecov Report

Merging #1892 into master will increase coverage by 0.03%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #1892      +/-   ##
==========================================
+ Coverage   86.35%   86.38%   +0.03%
==========================================
  Files          98       98
  Lines        6674     6691      +17
==========================================
+ Hits         5763     5780      +17
  Misses        652      652
  Partials      259      259

Impacted Files
Coverage Δ

internal/protocol/protocol.go
100% <ø> (ø)
:arrow_up:

internal/handshake/transport_parameters.go
97.44% <100%> (+0.31%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update c135b4f...4e6df90. Read the comment docs.


Redash  - explore implementing interactive dashboards to track forms submission  data for reporting purposes

As a follow-up to today's reporting meeting, it was discussed to look at implementing re-dash into our tool sets/ platforms to provide data on the number of :

forms submitted
forms at draft stage
forms at waiting approval stage
forms approved
forms that have expired.

The data will allow us provide totals &  averages for meaningful insights into our future reports.
Reporting Miro board can be referenced here:
https://miro.com/app/board/uXjVNhtZh_4=/
AC:
Recommendation/Plan for moving forward with reporting on Digital Journeys
***AOT hours could be leveraged

@warrenchristian1telus  We need more room in the pod to proceed with looking at adding Redash

@Stella-Archer We recently disabled Redash, which is what the Analytics module is based on.
We can easily re-enable it.
We may need to siphon some resources from other pods to make it work, so this could reduce overall load capacity. Analytics actually consists of 5 pod types, so is roughly 33% increase in overall resource footprint. In this regard, to maintain or increase app capacity we may need to revisit an increase to resources. I would recommend enabling and configuring it in dev / test first to get a good handle on exactly what configuration we'll need, and if we'll need to go through the process to justify an increase.
Tools we love – Redash

We are waiting for the cluster resizing to do this work


Added playlist class with 2 functions

[x] Tested and working
[x] Formatted using auto pep8

The PR adds a Playlist class with 2 functions
Thank You

Useful Feature and good quality of codes
You can merge it

ok thx

ready to merge

ready to merge


Added test case for mongoDB & some minor changes for users and journal test case!

Merged in https://github.com/llaske/sugarizer/commit/eceafe6464a551f5a0d987d8804d27fa65b62917


Quests Compass, Several Bug Fixes

New feature: quests with target NPCs or locations will use the player's compass to guide them there. This can be disabled via a config setting.
New command: /questsadmin reset, to reset a player without blacklisting them. Useful for testing/debugging.
Change: Quest finish text is highlighted and delays so that it appears a couple of seconds after rewards and other info. This is to make sure instructions can be given and seen by the player when completing a quest.
Controversial Change: I disabled the check for quests having changed on reload. I'm not sure if it's specific to my set up, but this seems to fire every single time- meaning I can't really use /questsadmin reload, or it will kill all online players out of any active quests. I'm up for discussing this point.
There are also several random bug fixes here and there, please check commits.
I'd also be up for splitting this up into separate commits if need be- I've sat on these changes for a while but wanted to share.

Thank you for this update, i hope the dev will add it :)

Thanks for yet another extensive commit! I'll let the dev build stew before posting on Spigot.

You're welcome, thanks for pulling!
I've had some reports of things going wrong when players take more than one quest at a time - I was going to look at that next, but if you have a moment do you know of any issues there off hand?

If you're looking for a challenge, #67 might be worth checking out. Otherwise, anything you'd like to contribute is welcome :)


Expandable sidebar

Issue submitter TODO list

[X] I've searched for an already existing issues here
[X] I'm running a supported version of the application which is listed here and the feature is not present there

Is your proposal related to a problem?
No response
Describe the feature you're interested in
When using very long cluster names, alot of the name is hidden. It would be nice to have the option to expand sidebar and view the full cluster name

Describe alternatives you've considered
No response
Version you're running
0.7.1
Additional context
No response

Sorry, duplicate #4225


Formally deprecate Flash and point people to Banner

See Staff-only Slack context and previous nudges pointing people to use Banner instead of Flash:

https://github.com/primer/view_components/issues/2394#issuecomment-1828767755
https://github.com/primer/view_components/issues/2112#issuecomment-1619177962

Given the past discussion that Banner will replace Flash, it probably makes sense to formally deprecate Flash and/or update docs to point people to Banner.
I am unsure what the formal deprecation process is like but filing for tracking!

We discussed this in the weekly PVC sync, seems reasonable to move forward with this 👍


Implemented streaming

Changes proposed in this pull request:

add support for streaming from batches to reduce memory
some code improvements

I tested both implementations by retrieving my recent tracks since January 1st of this year. With stream=False the memory usage was 150mb and rising while with stream=True (which I made the default) the memory usage stayed between 28 and 35mb.

I see that the travis-ci tests are failing with the following error:
pylast.WSError: Invalid API key - You must be granted a valid key by last.fm
I don't think this is something I can fix myself, right?
If so, can one of the maintainers please fix this?
If not, how can I fix this?
Thanks in advance.

Yeah, the CI fails for PRs, see https://github.com/pylast/pylast/issues/171.
Do they pass for you locally?

Yeah, the CI fails for PRs, see #171.
Do they pass for you locally?

@hugovk Thanks for your quick reply. Yes, they succeed locally (as you can see in the screenshot).

The force-push was because I used the wrong git profile by accident.

Please could you share some example code for this?
Sure. I basically used the example code and added the call to get_user().get_recent_tracks(). The following is what I came up with.

import time
from datetime import datetime

import pylast

start = time.time()
print(start)

# You have to have your own unique two values for API_KEY and API_SECRET
# Obtain yours from https://www.last.fm/api/account/create for Last.fm
API_KEY = "******************************"
API_SECRET = "***************************"

# In order to perform a write operation you need to authenticate yourself
username = "*************"
password_hash = pylast.md5("**********")

network = pylast.LastFMNetwork(api_key=API_KEY, api_secret=API_SECRET,
                               username=username, password_hash=password_hash)

tracks = network.get_user(username=username).get_recent_tracks(
    time_from=int(datetime(year=2020, month=1, day=1).timestamp()),
    cacheable=False, stream=False  # or stream=True
)
for track in tracks:
    pass

end = time.time()
print(end)
print(end-start)

I took some shortcuts with this example since I only made some scratches in PyCharm. I ran both examples locally watched the memory usage of the python process via system monitor/taskmanager on Windows.

I think I'd like to be on the cautious side and start off with stream=False as the default, so as not to have any surprising API  changes (for example, user.get_loved_tracks(limit=20) returns a 20-item list now, and a generator with this PR).
Then we can release it with a minor bump, and announce it will become the default in the next major release, where we can flip the default to stream=True. That way nothing will break for people pinning by major version.
We have a major, breaking release coming up soon anyway, as Python 3.5 will be EOL in September and dropped, so it won't be too long to wait.
What do you think?

Couldn't agree more, I didn't really think about it other than my own use case. Compatibility-wise it's a much better choice to make the change more gradually. I'll make the change and update the pull request.
To finish this comment, I would like to say thank you to you and the other contributers, since this wrapper made it really easy for me to implement my personal use case.

I made the changes as requested. Is there anything else I should do?

Please could you resolve the conflicts and I'll take another look? Thanks!

        Return values:

        - None if the database file can't be read;
        - empty string if the file can be read but can't be recognized
        - the name of the dbm submodule (e.g. "ndbm" or "gnu") if recognized.

        Importing the given module may still fail, and opening the
        database using that module may still fail.
        """

        # Check for ndbm first -- this has a .pag and a .dir file
        try:
>           f = io.open(filename + ".pag", "rb")
E           TypeError: unsupported operand type(s) for +: 'int' and 'str'

/opt/hostedtoolcache/Python/3.7.9/x64/lib/python3.7/dbm/__init__.py:112: TypeError

https://github.com/pylast/pylast/runs/1623179772?check_suite_focus=true

And all the tests passed except for one:
...

I'll look into it right away

I originally replaced .mktemp() with .TemporaryFile(), because .mktemp() is marked as unsafe. However, I should've replaced it with '.mkstemp()` (https://docs.python.org/3/library/tempfile.html#tempfile.mktemp).

That fails with another TypeError: can only concatenate tuple (not "str") to tuple, because mkstemp returns a tuple like (14, '/var/folders/kt/j77sf4_n6fnbx6pg199rbx700000gn/T/pylast_tmp_3koykybr'):

mkstemp() returns a tuple containing an OS-level handle to an open file (as would be returned by os.open()) and the absolute pathname of that file, in that order.

Let's leave it with the original in this PR as there's enough going on here, and please could you open a separate PR to change it?
Thanks!

Sorry, should've read that, don't know why I didn't. Reverted it to the original .mktemp().

I tested locally and all tests pass. Let's merge and I'll get a release out in the next week or so.
Thank you!


Mac can not install psycopg-binary==3.2.1 (MAC 13.5.1 (22G90) M1)

Describe the bug
Hey Forks, I run make backend, it failed
Browser and Version

MAC 13.5.1 (22G90) M1

Code
Package operations: 1 install, 0 updates, 0 removals

  - Installing psycopg-binary (3.2.1): Failed

  RuntimeError

  Unable to find installation candidates for psycopg-binary (3.2.1)

  at ~/Library/Application Support/pypoetry/venv/lib/python3.10/site-packages/poetry/installation/chooser.py:74 in choose_for
       70│
       71│             links.append(link)
       72│
       73│         if not links:
    →  74│             raise RuntimeError(f"Unable to find installation candidates for {package}")
       75│
       76│         # Get the best link
       77│         chosen = max(links, key=lambda link: self._sort_key(package, link))
       78│

Cannot install psycopg-binary.

make[1]: *** [install_backend] Error 1
make: *** [backend] Error 2

I can change psycopg-binary and psycopg == 3.1.19 and build a new poetry lock to run it.
Could you please use "~3.1.19" in pyproject.toml file?
psycopg = "~=3.1.19"
psycopg-binary = "~=3.1.19"

@xiaoqiangkx Do you need any assistance with this case? If not, please let us know if this issue can be closed.

Hey @xiaoqiangkx
How are you?
This is weird. We have 3.19 in the pyproject.toml
psycopg-binary = "^3.1.9"

For M1 Macs the minimum MacOS version is 14:
psycopg_binary-3.2.1-cp312-cp312-macosx_12_0_x86_64.whl
psycopg_binary-3.2.1-cp312-cp312-macosx_14_0_arm64.whl

For Intel ones the minimum is MacOS 12.

See https://github.com/psycopg/psycopg/issues/858

This is weird. We have 3.19 in the pyproject.toml psycopg-binary = "^3.1.9"

There is:
psycopg = "^3.1.9"
psycopg-binary = "^3.1.9"

which means it's compatible with 3.2.1 and the lock file confirms that:
https://github.com/langflow-ai/langflow/blob/main/poetry.lock#L7287
https://github.com/langflow-ai/langflow/blob/main/poetry.lock#L7310
BTW it's better to define
psycopg = { extras = ["binary"], version = "^3.1.9" }

rather than
psycopg = "^3.1.9"
psycopg-binary = "^3.1.9"

Any news on this?

Refer to https://github.com/psycopg/psycopg/issues/858 as well as the warning for MacOS ARM chips in https://www.psycopg.org/psycopg3/docs/basic/install.html#binary-installation.
The issue seems to be difficulty in builders targeting older versions of MacOS on ARM chips (https://github.com/psycopg/psycopg/issues/858#issuecomment-2217172495).

Thank you all for digging into this issue. I've updated to lock to 3.1.19 for now, as >=3.1.20 will cause issues for users on macOS 11, 12, 13.
See https://endoflife.date/macos for EOL for 11, 12, 13.
https://github.com/langflow-ai/langflow/pull/3292/files


Logs format

timestamp in output logs is redundant
don't display log level, maybe only prepend Debug for debug logs

use gelf


account for user interaction on governance sub pages

Resolves #997
Previously, the user interaction on the governance sub pages were not being handled by the master page(Governance page), so all click events were ignored.
the solution was to initialize the HandleUserInteractions() method of the sub pages from the governance page

this would be closed when this https://github.com/planetdecred/godcr/pull/1000/files is merged


[flutter_tools] refactor license collector

Improve debugging for https://github.com/flutter/flutter/issues/128680
In the linked issue, I cannot explain how we are getting a type error. However, this refactor eliminates the null check operator (by iterating over MapEntries rather than the keys) in hopes that there will be a more descriptive error in the future. The correctness of this change is verified by the existing tests in https://github.com/flutter/flutter/blob/master/packages/flutter_tools/test/general.shard/license_collector_test.dart

test-exempt: code refactor with no semantic change


Features: copy as curl command

It would be nice there has an action to copy as curl command for communication.

Hi @purefun I often use HurlVerbose to get the curl command from quickfix but I agree it would be good if that's built-in from plugin. Are you okay to open PR for this feature? Thank you.

Closed by #207


Scanning MaxiCodes does not work

Despite being listed as an option, the scanner will not scan MaxiCodes. Here is an example one with the encoded text "GrapheneOS":

Is there any other scanner (preferably something online/supported by Android or Desktop) that can scan this code?

Also, here's a comment relevant to this issue (made by another issue filed from your account):
https://github.com/GrapheneOS/Camera/issues/470#issuecomment-2346042975

The linked scanner seems to be a proprietary one, do you know any app that relies on an open-source library for scanning where this maxicode works?


fixes #121. adding / in front of non-builtin return types

fixes #121 Stub::_generateMethod() fails to generate return types of non-builtins correctly
adding \ in front of non-builtin types

Good catch :+1: !
Can you reopen this on the dev branch so I can merge it ?

Done


Please revise “We would like to invite you to submit a Proposal with more details about your project" automated message

When the PM sends the determination from within WebApp, it triggers an automated email notification to the applicant: “We would like to invite you to submit a Proposal with more details about your project.”
Please Revise:
Dear Jane Doe,

We’ve reviewed your Concept note and think it could be a good fit for OTF funding. We would like to invite you to submit a Proposal with more details about your project.

You can read the full determination here: [link to determination]

Please review our Proposal Guide (https://guide.opentech.fund/appendix-ii-proposal-guide) to learn more about the information we’d like to see. In the proposal please also address the feedback we provided in the concept note determination.

Here is the link to create your proposal: [proposal submission link]

The system will allow you to save a draft of your Proposal as you work on it. When you feel it is ready for OTF to review, please click the “Submit” button. We’ll reply to you with feedback as quickly as possible.

Please submit any questions related to your Proposal here [link to the communications tab of their application].  Please do not reply to this email with questions related to your Proposal.

If you have any issues accessing the submission system or other general inquiries, please email us at<EMAIL_ADDRESS>
Kind Regards,
The OTF Team

Is this notification not needed? How else is the applicant to know the application is approved?


improve insert cell GUI

The advanced mode insert cell GUI as it is now:

as it should be: change this from 2 buttons + and v to 4: +, t, h, and v.

inserts default cell type

t inserts as "text" (what is now called "markdown") cell
h brings up menu of 4 heading levels,
and v brings up a menu with just the available languages (with badges).

a rough draft of what I am thinking here

looks good but: put the language menu between the + and Text menus.  make the "v" be the triangle we have now.

ok no problem!

:+1: I think this has been merged in :)

this is what we ended up with:

and in-between cells:

:+1: i dig it


fix: escaped property name

Only a single question. Otherwise, lgtm.

Merge away when tests pass.

Appveyor status update seems not to be working ... see https://ci.appveyor.com/project/Apiary/snowcrash/history


How check memory leak，valgrind not run avs-device-sdk in Ubuntu?

How check memory leak，valgrind not run avs-device-sdk in Ubuntu?

Hi RongjieChen,
We had run valgrind on the SampleApp.
$valgrind --leak-check=full --log-file=leak_check.txt SampleApp Integration/AlexaClientSDKConfig.json debug9
$cat leak_check.txt

@jjishnu Could you tell me what you use the environment？  macos or ubuntu?  But i run valgrind in Ubuntu, it crash. What version valgrind you use?

On Ubuntu we ran it using Valgrind-3.12.0

@jjishnu @jjamazon we also run this environment. but we have a error like this.
Note: see also the FAQ in the source distribution.
It contains workarounds to several common problems.
In particular, if Valgrind aborted or crashed after
identifying problems in your program, there's a good chance
that fixing those problems will prevent Valgrind aborting or
crashing, especially if it happened in m_mallocfree.c.
If that doesn't help, please report this bug to: www.valgrind.org
In the bug report, send all the above text, the valgrind
version, and what OS and version you are using.  Thanks.

@RongjieChen Were you able to get this resolved ?

Closing due to inactivity. Please reopen if you're still facing issues.
Thanks,
Sanjay


Add custom IPv6 error message

WHY:
An IPv4 address is what we take from the user.
We don't accept other types of IP addresses and we let the user know through error messaging when an invalid IP address was inputted.
However, the error message displayed to the user is vague.
When a user enters a valid IPv6 address they see:
'1200:0000:AB00:1234:0000:2552:7777:1313' is not valid
but are not informed why it is not valid.
IN THIS PR:

Add hash key-value to the use case that checks the validity of submitted IP addresses. This would describe whether the IP address is IPv6 or not.
Add custom error message for when the value of the IPv6 hash key is true.
Refactor modified files.

BEFORE:

AFTER:

Any feedback/suggestions would be appreciated. Especially on the refactoring.

Nice work @Renny4Real


Fix typeerror in the google oauth

Fixing typeerror in the google oauth

@Khushi-S-29 You need to fix the type error that typescript is giving only

type User = {
  id: string;
  username: string;
  email: string;
  // Add other properties as needed
};

// Serialize user
passport.serializeUser<User, User>((user, done) => {
  done(null, user);
});

@Khushi-S-29  this is an example ,check if it works ! instead of using any and void types


qownnotes: 23.7.1 -> 23.7.2

Semi-automatic update generated by nixpkgs-update tools. This update was made based on information from repology.org.
meta.description for qownnotes is: Plain-text file notepad and todo-list manager with markdown support and Nextcloud/ownCloud integration
meta.homepage for qownnotes is: https://www.qownnotes.org/
meta.changelog for qownnotes is: https://www.qownnotes.org/changelog.html
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 23.7.2 with grep in /nix/store/q4vf94r55jhkbyqlrnca0whxqdxnl3bl-qownnotes-23.7.2
found 23.7.2 in filename of file in /nix/store/q4vf94r55jhkbyqlrnca0whxqdxnl3bl-qownnotes-23.7.2

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
qownnotes

Instructions to test this update (click to expand)

Build yourself:
nix-build -A qownnotes https://github.com/pbek/nixpkgs/archive/e98b2ab23396d288ecd0c6077580b21ed1845f87.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/q4vf94r55jhkbyqlrnca0whxqdxnl3bl-qownnotes-23.7.2
ls -la /nix/store/q4vf94r55jhkbyqlrnca0whxqdxnl3bl-qownnotes-23.7.2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

qownnotes

Maintainer pings
cc @pbek @totoroot for testing.

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

1 package built:

qownnotes

just waiting for ci

Thank you


[Feature][Flink] Add external configuration parameters

Purpose of this pull request

Check list

[ ] Code changed are covered with tests, or it does not need tests for reason:
[ ] If any new Jar binary package adding in your PR, please add License Notice according
New License Guide
[ ] If necessary, please update the documentation to describe the new feature. https://github.com/apache/seatunnel/tree/dev/docs
[ ] If you are contributing the connector code, please check that the following files are updated:

Update change log that in connector document. For more details you can refer to connector-v2
Update plugin-mapping.properties and add new connector information in it
Update the pom file of seatunnel-dist

[ ] Update the release-note.

LGTM, please add doc about this.

PTAL: @ruanwenjun @TyrantLucifer

There is a problem with some parameter configuration. I am working on it. Do not merge it
@ruanwenjun @TyrantLucifer

There is a problem with some parameter configuration. I am working on it. Do not merge it @ruanwenjun @TyrantLucifer

Waiting CI/CD and offer some screenshots to verify it worked.

PTAL: @TyrantLucifer @ruanwenjun  I added some CI

PTAL: @TyrantLucifer @ruanwenjun  I added some CI

Overall LGTM, but the test case that you added I didn't any way to see the parameter worded really. Could you please compiled the project and try verify it in a local flink env and offer the screen shots for it？

Flink Conf

conf file
env {
  # You can set flink configuration here
  execution.parallelism = 2
  job.mode = "STREAMING"
  flink.execution.checkpointing.interval = 5000
  flink.execution.checkpointing.unaligned.enabled = true
  flink.execution.checkpointing.aligned-checkpoint-timeout = 100000
  flink.jobstore.cache-size = 52428801
  flink.state.backend.rocksdb.predefined-options = SPINNING_DISK_OPTIMIZED_HIGH_MEM
}

source {
  # This is a example source plugin **only for test and demonstrate the feature source plugin**
  FakeSource {
    parallelism = 2
    result_table_name = "fake"
    row.num = 16
    schema = {
      fields {
        name = "string"
        age = "int"
      }
    }
  }

  # If you would like to get more information about how to configure seatunnel and see full list of source plugins,
  # please go to https://seatunnel.apache.org/docs/category/source-v2
}

transform {

  # If you would like to get more information about how to configure seatunnel and see full list of transform plugins,
  # please go to https://seatunnel.apache.org/docs/category/transform-v2
}

sink {
  Console {
    parallelism = 3
  }

  # If you would like to get more information about how to configure seatunnel and see full list of sink plugins,
  # please go to https://seatunnel.apache.org/docs/category/sink-v2
}

TestFlinkParameter

org.apache.seatunnel.example.flink.v2.SeaTunnelApiExample

conf file
env {
  # You can set flink configuration here
  execution.parallelism = 2
  job.mode = "STREAMING"
  flink.execution.checkpointing.interval = 5000
  flink.execution.checkpointing.unaligned.enabled = true
  flink.execution.checkpointing.aligned-checkpoint-timeout = 100000
  flink.jobstore.cache-size = 52428801
  flink.state.backend.rocksdb.predefined-options = SPINNING_DISK_OPTIMIZED_HIGH_MEM
}

source {
  # This is a example source plugin **only for test and demonstrate the feature source plugin**
  FakeSource {
    parallelism = 2
    result_table_name = "fake"
    row.num = 16
    schema = {
      fields {
        name = "string"
        age = "int"
      }
    }
  }

  # If you would like to get more information about how to configure seatunnel and see full list of source plugins,
  # please go to https://seatunnel.apache.org/docs/category/source-v2
}

transform {

  # If you would like to get more information about how to configure seatunnel and see full list of transform plugins,
  # please go to https://seatunnel.apache.org/docs/category/transform-v2
}

sink {
  Console {
    parallelism = 3
  }

  # If you would like to get more information about how to configure seatunnel and see full list of sink plugins,
  # please go to https://seatunnel.apache.org/docs/category/sink-v2
}

TestFlinkParameter

org.apache.seatunnel.example.flink.v2.SeaTunnelApiExample
 PTAL: @TyrantLucifer @ruanwenjun @EricJoy2048 I added some screenshots to demonstrate this

I think you should ensure the parameters injected in real flink jobs, not only codes. You should submit a seatunnel on flink engine and make a snapshot to verify it worked.

conf file
env {
  # You can set flink configuration here
  execution.parallelism = 2
  job.mode = "STREAMING"
  flink.execution.checkpointing.interval = 5000
  flink.execution.checkpointing.unaligned.enabled = true
  flink.execution.checkpointing.aligned-checkpoint-timeout = 100000
  flink.jobstore.cache-size = 52428801
  flink.state.backend.rocksdb.predefined-options = SPINNING_DISK_OPTIMIZED_HIGH_MEM
}

source {
  # This is a example source plugin **only for test and demonstrate the feature source plugin**
  FakeSource {
    parallelism = 2
    result_table_name = "fake"
    row.num = 16
    schema = {
      fields {
        name = "string"
        age = "int"
      }
    }
  }

  # If you would like to get more information about how to configure seatunnel and see full list of source plugins,
  # please go to https://seatunnel.apache.org/docs/category/source-v2
}

transform {

  # If you would like to get more information about how to configure seatunnel and see full list of transform plugins,
  # please go to https://seatunnel.apache.org/docs/category/transform-v2
}

sink {
  Console {
    parallelism = 3
  }

  # If you would like to get more information about how to configure seatunnel and see full list of sink plugins,
  # please go to https://seatunnel.apache.org/docs/category/sink-v2
}

TestFlinkParameter

org.apache.seatunnel.example.flink.v2.SeaTunnelApiExample
 PTAL: @TyrantLucifer @ruanwenjun @EricJoy2048 I added some screenshots to demonstrate this

I think you should ensure the parameters injected in real flink jobs, not only codes. You should submit a seatunnel on flink engine and make a snapshot to verify it worked.

I provide some screenshots of the flink run web Ui

PTAL: @Hisoka-X

@TyrantLucifer Could you take a look again?


[Question] How to use the local culture with a DateTime instance ?

Hi,
the following code use the US culture on Windows  with French culture :
(Get-Culture).Name
#fr-FR

Invoke-StringTemplate -Definition "Outer=$([System.DateTime]::Now)`r`nInner= <Now>" -Parameters @{
 Now = [System.DateTime]::Now
}
#Outer=11/10/2017 12:39:32   ---> French
#Inner= 10/11/2017 12:39:32  ---> US

Is it possible to solve this problem other than with this code ?
... -Parameters @{
 Now = "$([System.DateTime]::Now)"
}

Hmm this is really interesting.  What culture do you see when you run Get-UICulture?
I ask because if I set my culture with Set-Culture fr-FR  I get this:
"$([DateTime]::Now)"
# returns 11/10/2017 07:32:30
[DateTime]::Now.ToString()
# returns 10/11/2017 07:32:30

That makes me think expandable string expressions use the current UI culture and the ToString() method uses the current thread culture.
There isn't a whole lot I can do about that specifically, but currently I pass the current culture to the template renderer directly.  Would adding a Culture parameter be a sufficient work around?

What culture do you see when you run Get-UICulture?
fr-FR
That makes me think expandable string expressions use the current UI culture and the ToString() method uses the current thread culture.
I think that the invariant culture is used. With a 'US Windows' it is the same.
A other exemple
&{ "$(Get-Date)" }
#11/10/2017 14:53:57

$delegate= [System.Text.RegularExpressions.MatchEvaluator] {
  "$(Get-Date)"
}
$re = [regex] "[A-D]"

#use InvariantCulture -> US
$re.Replace("Now : A", $delegate)
#Now : 11/10/2017 14:54:52

I found this syntax, but that does not change anything:
Invoke-StringTemplate -Definition "Date=<Now; format='dd/MM/yyyy'>" -Parameters @{
 Now = [System.DateTime]::Now
}

Would adding a Culture parameter be a sufficient work around?
Before adding this, may be to test with API's in a Powershell console.
It seems that the addition of a renderer is necessary.

Tests around 'format' with renderer
import-module PSStringTemplate
#force loading Antlr4 assemblies

Invoke-StringTemplate -Definition 'Date=<Now; format="dd/MM/yyyy">' -Parameters @{
 Now = [System.DateTime]::Now
}

$definition= 'dateThing(created) ::= << date: <created; format="yyyy.MM.dd"> >>'
$group =[Antlr4.StringTemplate.TemplateGroupString]::new($Definition)
$st = $group.GetInstanceOf("dateThing")
$date=[DateTime]::new(2005, 7, 5)
$Date
#mardi 5 juillet 2005 00:00:00

$st.Add("created", $Date)
$result = $st.Render()
 #expecting = " date: 2005.07.05 "

$result
#NOK
#'format' do not work
#date: 05/07/2005 00:00:00

#Add renderer
$group.RegisterRenderer([DateTime], [Antlr4.StringTemplate.DateRenderer]::new())
$group.RegisterRenderer([DateTimeOffset], [Antlr4.StringTemplate.DateRenderer]::new())
$result = $st.Render()

$result
#OK
#'format' work as expected
# date: 2005.07.05

Tests with specific cultures :
function Using-Culture ([System.Globalization.CultureInfo]$culture =(throw "USAGE: Using-Culture -Culture culture -Script {scriptblock}"),
                        [ScriptBlock]$script=(throw "USAGE: Using-Culture -Culture culture -Script {scriptblock}"))
{
  #https://rkeithhill.wordpress.com/2009/10/21/windows-powershell-2-0-string-localization/
    $OldCulture = [System.Threading.Thread]::CurrentThread.CurrentCulture
    $OldUICulture = [System.Threading.Thread]::CurrentThread.CurrentUICulture
    try {
        [System.Threading.Thread]::CurrentThread.CurrentCulture = $culture
        [System.Threading.Thread]::CurrentThread.CurrentUICulture = $culture
        Invoke-Command $script
    }
    finally {
        [System.Threading.Thread]::CurrentThread.CurrentCulture = $OldCulture
        [System.Threading.Thread]::CurrentThread.CurrentUICulture = $OldUICulture
    }
}
$Test={
  $definition= 'dateThing(created) ::= << date: <created; format="dddd dd MMMM yyyy"> >>'
  $group =[Antlr4.StringTemplate.TemplateGroupString]::new($Definition)
  $group.RegisterRenderer([DateTime], [Antlr4.StringTemplate.DateRenderer]::new())
  $group.RegisterRenderer([DateTimeOffset], [Antlr4.StringTemplate.DateRenderer]::new())
  $st = $group.GetInstanceOf("dateThing")
  $st.Add("created", [DateTime]::new(2005, 7, 5))> $null
  $st.Render()
}
.$Test
#OK
#date: mardi 05 juillet 2005

Using-Culture de-DE $Test
#date: Dienstag 05 Juli 2005

Using-Culture en-US $Test
#date: Tuesday 05 July 2005

Ah yes adding the renderer is a much better fix, thank you so much for looking into that :)
Changes are made for this and enabling static properties, just need to write tests and I should have a release with the changes by the end of the day.

Do changes make it possible to use a personal rendering?

This change will just be adding the DateRenderer, which would allow using the format operator for dates like shown in this thread.
I do plan on adding a way to apply custom renderers, but that's a little bit more difficult to make approachable from PowerShell.  I'll open a separate issue for that, and go into more detail there.

Version 0.2.0 is now available in the gallery and should solve the original issue, but give it a try and feel free to reopen the issue if it doesn't work for your use case!
I opened a separate issue (#12) to track custom renderers including implementation pit falls and ideas.  Thanks again for the help, greatly appreciated!

Version 0.2.0 is now available in the gallery
Thank you.


Refactor CheckboxInput API to pass event back to consumer.

 Update Checkbox onChange to return event

https://github.com/palmetto/palmetto-components/pull/81


Document tx prop?

Hi! I noticed that internally, rebass uses the tx prop from reflexbox for scoped variants. For example, if I wanted to create a custom component that exposes variants, I could do
// Without `tx`
const FancyBox = ({ variant, ...etc }) => <Box variant={`fancybox.${variant}`} {...etc} />

// With `tx`
const FancyBox = ({ variant, ...etc }) => <Box tx="fancybox" variant={variant} {...etc} />

Is this something that is officially supported (and thus should be documented) or not?

This is a private API and may break at any point so it should not be documented or used externally

OK, thanks for the feedback! 👍


Code re-organization

Current dependency graph
graph TD;
  silkenweb[silkenweb];
  silkenweb --> base;
  silkenweb --> macros;
  silkenweb --> signals-ext;
  macros --base::css::Source--> base;
  test --base::document--> base;
  test --> silkenweb;

Proposal

move base::document and base::window to the silkenweb crate.
create a new styling crate with all the CSS-related stuff.
create a new styling-macros crate with CSS-related macros.
remove base and move its base::css code to the styling crate.
create a new runtime crate that contains the runtime (task:: etc) code.
remove the signals-ext and move it's code into runtime.

graph TD;
  silkenweb[silkenweb];
  styling --> silkenweb;
  styling --> styling-macros;
  silkenweb --> macros;
  silkenweb --> runtime;
  test --> silkenweb;

The following is achieved with this:

the runtime crate can be used by business logic so that testing of it can be done without a full silkenweb dependency. This guarantees that the business logic doesn't mix in any UI-related things. I.e. the app-state stuff can be added to the runtime crate.
styling is separated into its own crate which depends on and extends silkenweb. Like this the styling is optional.

Let me know what you think. I'll create a PR for it.
Note
I'm working on reducing the silkenweb compilation times and the styling (lightningcss, grass, cssparser) is responsible for 40% of it. For my own project, I will use a simple approach of having a parallel css file to each component and at build just appending all these css files into a single main one.
In my_component.rs:
fn my_component<D: Dom>() -> Button<D> {
    button().class("my-component")
}

In my_component.css:
.my-component {
   component specific standard css
}

Generally sounds like a great idea. I haven't really given a thought to build times, and should really. A few minor points:

I'd like to keep signals-ext for now. It's meant to be completely independent of the other Silkenweb code.
My gut feeling is that styling and styling-macros should be called css and css-macros, as the purpose is to split out CSS related code to make it optional and improve build times. For example, any future non CSS styling code (whatever that might be) would probably be added to Silkenweb directly so you didn't have to pull in CSS dependencies.

Would you like the css and css-macros extracted from silkenweb and hosted outside in another GitHub repo?

No, keep them in the same repo under packages.

I'm looking at using Features for the CSS part of this:

Features give us finer grained control, so we don't need grass if we don't do Sass, and we don't need lightningcss if we don't do transpilation, but we can still do basic Css stuff.
It's a bit weird to have a public facing silkenweb-css-macros crate with a macro that requires you to depend on silkenweb.
We don't end up loads of crates. I want to expose some parts of css::Source at some point, which would mean another crate on top of silkenweb-css and silkenweb-css-macros.

I'm still thinking that runtime should be a separate crate.

I've merged a change to improve full rebuild times. I've added a css-transpile feature, that's not enabled by default. A full build of the silkenweb crate has gone from 41.4s before any changes, to 22.5s without css-transpile enabled.
It probably won't impact incremental build times, but I haven't tested that. I'll look at extracting a runtime crate next.

Great news! Thanks!

I've added a silkenweb_task crate with all the task related items. It's all re-exported in silkenweb::task, with some extras (render_now and render_now_sync). scope and sync_scope have 2 versions:

silkenweb::task::*scope provide the Task Locals required for rendering, mounting and routing, along with a task queue.
silkenweb::task::*scope with just a task queue.

I think all these changes should give you improved build times when you don't need CSS transpilation, along with the ability to separate business logic from UI presentation code. It doesn't separate the CSS into it's own crate for now, as that's all quite integrated with the rest of Silkenweb.

It doesn't affect the public interface, but I've now extracted the CSS stuff from silkenweb-base into silkenweb-css. It's not meant as a public crate yet, but it's useful for writing proc macros, so I might tidy up the interface and make it public at some point. I'm not planning to split out the macro stuff (that's more entangled with the rest of Silkenweb).


iscsi: clean up codes

This patch includes:

removed unnecessary code comments
updated start sub command help message.

I'm fine with this change

needs rebase, also this can be cleaned up too 👍
iscsi/targetd/provisioner/iscsi-provisioner.go:76:1:warning: result is unused (deadcode)

Thank you. Updated.

/lgtm
/area iscsi/targetd


Add filtering for tables

Is this the server side filtering (sending requests to server with filter query params?)

Yes


[markdown] Use older version of mdl (0.9)

https://github.com/markdownlint/markdownlint/issues/341
Signed-off-by: Martin Bašti<EMAIL_ADDRESS>Maintainers will complete the following section

[ ] Commit messages are descriptive enough
[ ] Code coverage from testing does not decrease and new code is covered
[ ] JSON/YAML configuration changes are updated in the relevant schema
[ ] Changes to metadata also update the documentation for the metadata
[ ] Pull request has a link to an osbs-docs PR for user documentation updates

@ben-alkov WDYT? Downgrade everywhere or wait for fix?

@MartinBasti; Might as well downgrade everywhere.
N.B. that this is a good argument for GH Actions in all the repos. We'd only have to make a single change in the markdownlint Dockerfile

markdownlint/markdownlint#344


Feature/mdr 315

Codecov Report

Merging #12 (9706b9d) into master (e81bc71) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #12   +/-   ##
=======================================
  Coverage   91.30%   91.30%
=======================================
  Files           5        5
  Lines          46       46
=======================================
  Hits           42       42
  Misses          4        4

Flag
Coverage Δ

unittests
91.30% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e81bc71...9706b9d. Read the comment docs.


update README table

The table in the readme reflects last year's projects. We should update that once we close #8

Maybe it would be better to remove that entirely or we will need to modify it every year. When sending it to GSoC application we need only the file inside the 2022 folder. What do you think?

Agreed. The overarching content is great, but the table should be replaced with a link to the current year's table of projects.


Create: 7-Reverse-Integer.swift, 268-Missing-Number.swift, 190-Reverse-Bits.swift, 55-Jump-Game.swift, 70-Climbing-Stairs.swift, 746-Min-Cost-Climbing-Stairs.swift, 45-Jump-Game-II.swift

Swift solutions for 7-Reverse-Integer.swift, 268-Missing-Number.swift, 190-Reverse-Bits.swift, 55-Jump-Game.swift, 70-Climbing-Stairs.swift, 746-Min-Cost-Climbing-Stairs.swift

File(s) Modified: 7-Reverse-Integer.swift, 268-Missing-Number.swift, 190-Reverse-Bits.swift, 55-Jump-Game.swift, 70-Climbing-Stairs.swift, 746-Min-Cost-Climbing-Stairs.swift, 45-Jump-Game-II.swift
Language(s) Used: swift
Submission URL: Reverse Integer: _https://leetcode.com/submissions/detail/788299946/_
Missing Number: _https://leetcode.com/submissions/detail/788310995/_
Reverse Bits: _https://leetcode.com/submissions/detail/788316946/_
Jump Game: _https://leetcode.com/submissions/detail/788324183/_
Climbing Stairs: _https://leetcode.com/submissions/detail/788329781/_
Min Cost Climbing Stairs: _https://leetcode.com/submissions/detail/788332865/_
Jump Game II: _https://leetcode.com/submissions/detail/788337494/_

Thanks, @Ykhan799!


chore(deps): update ci dependencies

This PR contains the following updates:

Package
Type
Update
Change

common-dev-assets

digest
3324eff -> 0bb608c

github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper
require
minor
v1.27.2 -> v1.28.4

terraform-ibm-modules/common-pipeline-assets
action
minor
v1.20.0 -> v1.21.0

Release Notes

terraform-ibm-modules/ibmcloud-terratest-wrapper (github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper)
v1.28.4
Compare Source
Bug Fixes

deps: update module golang.org/x/crypto to v0.19.0 (#757) (72d3f03)

v1.28.3
Compare Source
Bug Fixes

update to not hard fail on destroy (9c6e21c)

v1.28.2
Compare Source
Bug Fixes

deps: update gomod (#754) (2872471)

v1.28.1
Compare Source
Bug Fixes

Add Helper function and refactor tests (#752) (c3e0c1c)

v1.28.0
Compare Source
Features

add resource group print on failure (#746) (17daf42)

terraform-ibm-modules/common-pipeline-assets (terraform-ibm-modules/common-pipeline-assets)
v1.21.0
Compare Source
Features

Release pipeline now creates GIT issue and slack alert on failure (#636) (3a51e77)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline


Fix auto-links in scheduler.md

Changes
Removed unnecessary text overrides, added missing auto-links, and fixed auto-links that were incorrectly placed.
Checks
By submitting your pull request for review, you agree to the following:

[X] This contribution was created in whole or in part by me, and I have the right to submit it under the terms of this repository's open source licenses.
[X] I understand and agree that this contribution and a record of it are public, maintained indefinitely, and may be redistributed under the terms of this repository's open source licenses.
[X] To the best of my knowledge, all proposed changes are accurate.

Thanks a bunch @Katrist. I made some tweaks, but really appreciate your work on the table in particular.


⚠ Bofrost.es has degraded performance

In 7149da8, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1480 ms

Resolved: Bofrost.es performance has improved in adeef72 after 7 minutes.