fix: upgrade to version 3.1.137

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign hferentschik
You can assign the PR to them by writing /assign @hferentschik in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign hferentschik
You can assign the PR to them by writing /assign @hferentschik in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@jenkins-x-bot-test: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

vault
e501a5e14e9782179e8b785758608a3dd2d4a5f8
link
/test vault

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jenkins-x-bot-test: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

vault
e501a5e14e9782179e8b785758608a3dd2d4a5f8
link
/test vault

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jenkins-x-bot-test: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

vault
e501a5e14e9782179e8b785758608a3dd2d4a5f8
link
/test vault

tls
e501a5e14e9782179e8b785758608a3dd2d4a5f8
link
/test tls

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jenkins-x-bot-test: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

vault
e501a5e14e9782179e8b785758608a3dd2d4a5f8
link
/test vault

tls
e501a5e14e9782179e8b785758608a3dd2d4a5f8
link
/test tls

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

/test vault

/test vault

/test tls

/test tls

/retest

/retest

@jenkins-x-bot-test: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

vault
e501a5e14e9782179e8b785758608a3dd2d4a5f8
link
/test vault

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jenkins-x-bot-test: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

vault
e501a5e14e9782179e8b785758608a3dd2d4a5f8
link
/test vault

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jenkins-x-bot-test: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

vault
e501a5e14e9782179e8b785758608a3dd2d4a5f8
link
/test vault

kube
ab17f4d9ca1d521ef703e19a589e186962e8de4b
link
/test kube

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jenkins-x-bot-test: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

vault
e501a5e14e9782179e8b785758608a3dd2d4a5f8
link
/test vault

kube
ab17f4d9ca1d521ef703e19a589e186962e8de4b
link
/test kube

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jenkins-x-bot-test: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

vault
e501a5e14e9782179e8b785758608a3dd2d4a5f8
link
/test vault

kube
ab17f4d9ca1d521ef703e19a589e186962e8de4b
link
/test kube

tls
ab17f4d9ca1d521ef703e19a589e186962e8de4b
link
/test tls

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jenkins-x-bot-test: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

vault
e501a5e14e9782179e8b785758608a3dd2d4a5f8
link
/test vault

kube
ab17f4d9ca1d521ef703e19a589e186962e8de4b
link
/test kube

tls
ab17f4d9ca1d521ef703e19a589e186962e8de4b
link
/test tls

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jenkins-x-bot-test: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

kube
ab17f4d9ca1d521ef703e19a589e186962e8de4b
link
/test kube

tls
ab17f4d9ca1d521ef703e19a589e186962e8de4b
link
/test tls

vault
ab17f4d9ca1d521ef703e19a589e186962e8de4b
link
/test vault

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jenkins-x-bot-test: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

kube
ab17f4d9ca1d521ef703e19a589e186962e8de4b
link
/test kube

tls
ab17f4d9ca1d521ef703e19a589e186962e8de4b
link
/test tls

vault
ab17f4d9ca1d521ef703e19a589e186962e8de4b
link
/test vault

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jenkins-x-bot-test: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

kube
ab17f4d9ca1d521ef703e19a589e186962e8de4b
link
/test kube

tls
ab17f4d9ca1d521ef703e19a589e186962e8de4b
link
/test tls

vault
ab17f4d9ca1d521ef703e19a589e186962e8de4b
link
/test vault

gsm
ab17f4d9ca1d521ef703e19a589e186962e8de4b
link
/test gsm

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jenkins-x-bot-test: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

kube
ab17f4d9ca1d521ef703e19a589e186962e8de4b
link
/test kube

tls
ab17f4d9ca1d521ef703e19a589e186962e8de4b
link
/test tls

vault
ab17f4d9ca1d521ef703e19a589e186962e8de4b
link
/test vault

gsm
ab17f4d9ca1d521ef703e19a589e186962e8de4b
link
/test gsm

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

/test kube

/test kube

/retest

/retest

/retest

/retest

/test kube

/test kube

/retest

/retest

@jenkins-x-bot-test: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

tls
ab17f4d9ca1d521ef703e19a589e186962e8de4b
link
/test tls

kube
e501a5e14e9782179e8b785758608a3dd2d4a5f8
link
/test kube

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jenkins-x-bot-test: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

tls
ab17f4d9ca1d521ef703e19a589e186962e8de4b
link
/test tls

kube
e501a5e14e9782179e8b785758608a3dd2d4a5f8
link
/test kube

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.


(ENGTASKS-3807)  (doc) Include URLs checked for GitHub comment rule

Description Of Changes
This includes information about what the URLs look like that we consider
to come from GitHub comments that will be flagged by Package Validator.
Motivation and Context
To give information about what wil be flagged.
Testing

[x] I have previewed these changes using the Docker Container or another method before submitting this pull request.

Change Types Made
~* [ ] Minor documentation fix (typos etc.).~

[x] Major documentation change (refactoring, reformatting or adding documentation to existing page).
~* [ ] New documentation page added.~
~* [ ] The change I have made should have a video added, and I have raised an issue for this.~

Change Checklist
~* [ ] Requires a change to menu structure (top or left-hand side)/~
~* [ ] Menu structure has been updated~
Related Issue
N/A

@AdmiringWorm thank you for getting this added!


Prevent corrupt MP4 when powerloss occurs.

Moving forward we will utilize fragmented MP4.  Fragmented MP4 segments the mdat (Movie Data) to the mp4 file based on I-Frame detection.  This allows for the file to still be usable even though the last mdat was not written.  For more information I recommend this read as it explains the differences between Fragmented and Non-Fragmented:
https://stackoverflow.com/questions/35177797/what-exactly-is-fragmented-mp4fmp4-how-is-it-different-from-normal-mp4

@evilC has confirmed fragmented MP4 is compatible with Premiere Pro and Kdenlive.  However, I have converted this PR to a draft as it should not be merged into master until I have the Goggle playback working with this file format.

Closing out PR since the goggles built-in MP4 decoder does not support fragmented MP4 playback.  Video playback duration are not decoded properly.


Add Decimal128 API and use it in DecimalArray and DecimalBuilder

Which issue does this PR close?

Closes #1870.
Rationale for this change

What changes are included in this PR?

Are there any user-facing changes?

Codecov Report

Merging #1871 (946e9d4) into master (cedaf8a) will decrease coverage by 0.00%.
The diff coverage is 88.23%.

@@            Coverage Diff             @@
##           master    #1871      +/-   ##
==========================================
- Coverage   83.46%   83.45%   -0.01%
==========================================
  Files         201      202       +1
  Lines       57014    57069      +55
==========================================
+ Hits        47586    47627      +41
- Misses       9428     9442      +14

Impacted Files
Coverage Δ

arrow/src/util/decimal.rs
75.51% <75.51%> (ø)

arrow/src/array/array_binary.rs
94.18% <100.00%> (-0.06%)
:arrow_down:

arrow/src/array/builder.rs
86.98% <100.00%> (+0.09%)
:arrow_up:

arrow/src/array/equal_json.rs
89.70% <100.00%> (ø)

arrow/src/array/iterator.rs
96.11% <100.00%> (ø)

arrow/src/compute/kernels/cast.rs
95.77% <100.00%> (ø)

arrow/src/compute/kernels/sort.rs
95.67% <100.00%> (ø)

arrow/src/compute/kernels/take.rs
95.27% <100.00%> (ø)

parquet/src/arrow/arrow_reader.rs
96.87% <100.00%> (ø)

parquet/src/arrow/arrow_writer/mod.rs
97.53% <100.00%> (ø)

... and 2 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 cedaf8a...946e9d4. Read the comment docs.

I want to take a look this pr, please hold it.

@viirya
a question which is not about this pr.
How to represent decimal256 in rust？How does c++ implement it?
I'm not familiar with arrow c++ version.

@viirya a question which is not about this pr. How to represent decimal256 in rust？How does c++ implement it? I'm not familiar with arrow c++ version.

Like C++ Arrow Decimal256, we can represent the integer in an array of parts of it. C++ Arrow Decimal256 uses an uint64_t array.

Thank you @tustvold @liukun4515. I'm merging this and keeping working on Decimal256 and generalise them.


sys_heap heap allocator optimizations

This goes on top of PR #23941 and therefore patches from PR #23941 are included here.
This series implements an assortment of optimizations providing both
execution efficiency and footprint overhead reduction. Because of that, a few tests presuming a higher overhead are now failing.
I'm posting this here for people to see and comment.

parent PR now merged, please rebase

On Tue, 14 Apr 2020, Andrew Boie wrote:

parent PR now merged, please rebase

Done.

Bunch of tests failing with "    Assertion failed at WEST_TOPDIR/zephyr/tests/kernel/lifo/lifo_usage/src/main.c:329: test_timeout_lifo_thread: packet != NULL is false"
Gonna kick CI again to make sure.

Seeing a consistent assertion failure:
starting test - test_mheap_block_desc

    Assertion failed at WEST_TOPDIR/zephyr/tests/kernel/mem_heap/mheap_api_concept/src/test_mheap_concept.c:129: test_mheap_block_desc: block_fail is not NULL

kicking again to make sure

On Mon, 11 May 2020, Andrew Boie wrote:

Seeing a consistent assertion failure:
starting test - test_mheap_block_desc

    Assertion failed at WEST_TOPDIR/zephyr/tests/kernel/mem_heap/mheap_api_concept/src/test_mheap_concept.c:129: test_mheap_block_desc: block_fail is not NULL

OK, found it.
The last patch is titled "sys_heap: reduce the size of struct
z_heap_bucket by half". It is missing the following bit to a file that
didn't exist when the patch was initially created:
diff --git a/include/mempool_heap.h b/include/mempool_heap.h
index df64322b50..439371556d 100644
--- a/include/mempool_heap.h
+++ b/include/mempool_heap.h
@@ -35,7 +35,7 @@ struct k_mem_pool {
  * that k_heap does not.  We make space for the number of maximum
  * objects defined, and include extra so there's enough metadata space
  * available for the maximum number of minimum-sized objects to be
- * stored: 8 bytes for each desired chunk header, and a 24 word block
+ * stored: 8 bytes for each desired chunk header, and a 12 word block
  * to reserve room for a "typical" set of bucket list heads (this size
  * was picked more to conform with existing test expectations than any
  * rigorous theory -- we have tests that rely on being able to
@@ -46,7 +46,7 @@ struct k_mem_pool {
 		K_HEAP_DEFINE(poolheap_##name,				\
 			      ((maxsz) * (nmax))			\
 			      + 8 * ((maxsz) * (nmax) / (minsz))	\
-			      + 24 * sizeof(void *));			\
+			      + 12 * sizeof(void *));			\
 		struct k_mem_pool name = {				\
 			.heap = &poolheap_##name			\
 		}

Should be fine now.

[0mSeaBIOS (version rel-1.12.1-0-ga5cab58-dirty-20200214_052440-f7294c49af13-zephyr
)
Booting from ROM..Optimal CONFIG_X86_MMU_PAGE_POOL_PAGES 8
*** Booting Zephyr OS build v2.3.0-rc1-25-g401d2147465a  ***
Running test suite mempool
===================================================================
starting test - test_pool_block_get

    Assertion failed at WEST_TOPDIR/zephyr/tests/kernel/mem_pool/mem_pool/src/main.c:178: pool_block_get_work: (rv not equal to tests[i].rcode)
k_mem_pool_alloc() expected 0, got -12
size: 512, timeout: 0

FAIL - test_pool_block_get
===================================================================
starting test - test_pool_block_get_timeout

    Assertion failed at WEST_TOPDIR/zephyr/tests/kernel/mem_pool/mem_pool/src/main.c:178: pool_block_get_work: (rv not equal to tests[i].rcode)
k_mem_pool_alloc() expected 0, got -11
size: 4096, timeout: 100

FAIL - test_pool_block_get_timeout
===================================================================
starting test - test_pool_block_get_wait

    Assertion failed at WEST_TOPDIR/zephyr/tests/kernel/mem_pool/mem_pool/src/main.c:271: test_pool_block_get_wait: (rv not equal to 0)
k_mem_pool_alloc(3000) expected 0, got -11

FAIL - test_pool_block_get_wait
===================================================================
starting test - test_pool_malloc
PASS - test_pool_malloc
===================================================================
Test suite mempool failed.
===================================================================
PROJECT EXECUTION FAILED

Still failing.

On Tue, 12 May 2020, Andy Ross wrote:

Just throwing up my +1 for when this exits the CI banging phase.  These all look great to me.

Thanks.
What is not great are all those tests: some of them are pure bollocks in
the context of the heap allocator.
Some patches in this series reduce the heap footprint overhead and then
some allocation tests pass when they were expected to fail with ENOMEM.
So futzing with the fake numbers within Z_MEM_POOL_DEFINE() make them
pass but then other tests start failing for the opposite reason.
So I just picked another semi-random number to satisfy all tests...
unless I missed some.

There are some build failures here that I am not sure are attributable to this PR's changes. @nashif any ideas?

The current failure in qemu_arc_em is almost certainly unrelated to this PR.
Failures

 Sanitycheck / qemu_arc_em:tests/kernel/lifo/lifo_usage/kernel.lifo.usage / tests/kernel/lifo/lifo_usage/kernel.lifo.usage

*** Booting Zephyr OS build zephyr-v2.3.0-488-g6c7ca9602316  ***
Running test suite test_lifo_usage
===================================================================
starting test - test_lifo_nowait
PASS - test_lifo_nowait
===================================================================
starting test - test_lifo_wait
PASS - test_lifo_wait
===================================================================
starting test - test_timeout_empty_lifo
PASS - test_timeout_empty_lifo
===================================================================
starting test - test_timeout_non_empty_lifo
PASS - test_timeout_non_empty_lifo
===================================================================
starting test - test_timeout_lifo_thread
PASS - test_timeout_lifo_thread
===================================================================
starting test - test_timeout_threads_pend_on_lifo
 thread (q order: 2, t/o: 0, lifo 0x8040621c)

    Assertion failed at WEST_TOPDIR/zephyr/tests/kernel/lifo/lifo_usage/src/main.c:140: test_multiple_threads_pending: (data->timeout_order not equal to ii)
 *** thread 2 woke up, expected 1

FAIL - test_timeout_threads_pend_on_lifo
===================================================================
Test suite test_lifo_usage failed.
===================================================================
PROJECT EXECUTION FAILED

The current failure in qemu_arc_em is almost certainly unrelated to this PR.

@carlescufi The QEMU ARC platform does not have icount enabled and can be quite unstable when running sanitychecks (basically the same issue we had with other platforms earlier). Re-triggering should fix the problem.


storcon: make hb interval an argument and speed up tests

Problem
Each test might wait for up to 5s in order to HB the pageserver.
Summary of changes
Make the heartbeat interval configurable and use a really tight one for neon local => startup quicker
Checklist before requesting a review

[ ] I have performed a self-review of my code.
[ ] If it is a core feature, I have added thorough tests.
[ ] Do we need to implement analytics? if so did you add the relevant metrics to the dashboard?
[ ] If this PR requires public announcement, mark it with /release-notes label and add several sentences in this section.

Checklist before merging

[ ] Do not forget to reformat commit message to not include the above checklist

test_multixid_wraparound_import: debug-x86-64

test_create_churn_during_restart: debug-x86-64

I do not understand these failures. I'll re-run.

test_create_churn_during_restart: debug-x86-64

So, this will probably reproduce on the next run.

I'm surprised this was passing reliably before. I've allow listed the storcon equivalent of the already allow listed pageserver log in https://github.com/neondatabase/neon/pull/8880/commits/a719170f0ff2434b6cdb78b8f66d284a49f07b23. @jcsp does this make sense to you?


Fix typo: falta -> fatal

Fix typo: falta -> fatal

I signed it!

/assign @ozevren

/ok-to-test
/lgtm
/approve

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: ozevren, SataQiu
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

galley/OWNERS [ozevren]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@SataQiu: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-dashboard.sh
30775d5f28165388a060d36071896e4b7dd54843
link
/test e2e-dashboard

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@SataQiu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-dashboard.sh
30775d5f28165388a060d36071896e4b7dd54843
link
/test e2e-dashboard

prow/istio-pilot-e2e-envoyv2-v1alpha3-mcp.sh
30775d5f28165388a060d36071896e4b7dd54843
link
/test istio-pilot-e2e-envoyv2-v1alpha3-mcp

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@SataQiu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-dashboard.sh
30775d5f28165388a060d36071896e4b7dd54843
link
/test e2e-dashboard

prow/istio-pilot-e2e-envoyv2-v1alpha3-mcp.sh
30775d5f28165388a060d36071896e4b7dd54843
link
/test istio-pilot-e2e-envoyv2-v1alpha3-mcp

prow/e2e-mixer-no_auth.sh
30775d5f28165388a060d36071896e4b7dd54843
link
/test e2e-mixer-no_auth

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@SataQiu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-dashboard.sh
30775d5f28165388a060d36071896e4b7dd54843
link
/test e2e-dashboard

prow/istio-pilot-e2e-envoyv2-v1alpha3-mcp.sh
30775d5f28165388a060d36071896e4b7dd54843
link
/test istio-pilot-e2e-envoyv2-v1alpha3-mcp

prow/e2e-mixer-no_auth.sh
30775d5f28165388a060d36071896e4b7dd54843
link
/test e2e-mixer-no_auth

prow/e2e-mixer-no_auth-mcp.sh
30775d5f28165388a060d36071896e4b7dd54843
link
/test e2e-mixer-no_auth-mcp

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@SataQiu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-dashboard.sh
30775d5f28165388a060d36071896e4b7dd54843
link
/test e2e-dashboard

prow/istio-pilot-e2e-envoyv2-v1alpha3-mcp.sh
30775d5f28165388a060d36071896e4b7dd54843
link
/test istio-pilot-e2e-envoyv2-v1alpha3-mcp

prow/e2e-mixer-no_auth.sh
30775d5f28165388a060d36071896e4b7dd54843
link
/test e2e-mixer-no_auth

prow/e2e-mixer-no_auth-mcp.sh
30775d5f28165388a060d36071896e4b7dd54843
link
/test e2e-mixer-no_auth-mcp

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
30775d5f28165388a060d36071896e4b7dd54843
link
/test istio-pilot-e2e-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@SataQiu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-dashboard.sh
30775d5f28165388a060d36071896e4b7dd54843
link
/test e2e-dashboard

prow/istio-pilot-e2e-envoyv2-v1alpha3-mcp.sh
30775d5f28165388a060d36071896e4b7dd54843
link
/test istio-pilot-e2e-envoyv2-v1alpha3-mcp

prow/e2e-mixer-no_auth.sh
30775d5f28165388a060d36071896e4b7dd54843
link
/test e2e-mixer-no_auth

prow/e2e-mixer-no_auth-mcp.sh
30775d5f28165388a060d36071896e4b7dd54843
link
/test e2e-mixer-no_auth-mcp

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
30775d5f28165388a060d36071896e4b7dd54843
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-multicluster-e2e.sh
30775d5f28165388a060d36071896e4b7dd54843
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@SataQiu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-dashboard.sh
30775d5f28165388a060d36071896e4b7dd54843
link
/test e2e-dashboard

prow/istio-pilot-e2e-envoyv2-v1alpha3-mcp.sh
30775d5f28165388a060d36071896e4b7dd54843
link
/test istio-pilot-e2e-envoyv2-v1alpha3-mcp

prow/e2e-mixer-no_auth.sh
30775d5f28165388a060d36071896e4b7dd54843
link
/test e2e-mixer-no_auth

prow/e2e-mixer-no_auth-mcp.sh
30775d5f28165388a060d36071896e4b7dd54843
link
/test e2e-mixer-no_auth-mcp

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
30775d5f28165388a060d36071896e4b7dd54843
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-multicluster-e2e.sh
30775d5f28165388a060d36071896e4b7dd54843
link
/test istio-pilot-multicluster-e2e

prow/e2e-simpleTests.sh
30775d5f28165388a060d36071896e4b7dd54843
link
/test e2e-simpleTests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@SataQiu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-dashboard.sh
30775d5f28165388a060d36071896e4b7dd54843
link
/test e2e-dashboard

prow/istio-pilot-e2e-envoyv2-v1alpha3-mcp.sh
30775d5f28165388a060d36071896e4b7dd54843
link
/test istio-pilot-e2e-envoyv2-v1alpha3-mcp

prow/e2e-mixer-no_auth.sh
30775d5f28165388a060d36071896e4b7dd54843
link
/test e2e-mixer-no_auth

prow/e2e-mixer-no_auth-mcp.sh
30775d5f28165388a060d36071896e4b7dd54843
link
/test e2e-mixer-no_auth-mcp

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
30775d5f28165388a060d36071896e4b7dd54843
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-multicluster-e2e.sh
30775d5f28165388a060d36071896e4b7dd54843
link
/test istio-pilot-multicluster-e2e

prow/e2e-simpleTests.sh
30775d5f28165388a060d36071896e4b7dd54843
link
/test e2e-simpleTests

prow/e2e-bookInfoTests-v1alpha3.sh
30775d5f28165388a060d36071896e4b7dd54843
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@SataQiu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-dashboard.sh
30775d5f28165388a060d36071896e4b7dd54843
link
/test e2e-dashboard

prow/istio-pilot-e2e-envoyv2-v1alpha3-mcp.sh
30775d5f28165388a060d36071896e4b7dd54843
link
/test istio-pilot-e2e-envoyv2-v1alpha3-mcp

prow/e2e-mixer-no_auth.sh
30775d5f28165388a060d36071896e4b7dd54843
link
/test e2e-mixer-no_auth

prow/e2e-mixer-no_auth-mcp.sh
30775d5f28165388a060d36071896e4b7dd54843
link
/test e2e-mixer-no_auth-mcp

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
30775d5f28165388a060d36071896e4b7dd54843
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-multicluster-e2e.sh
30775d5f28165388a060d36071896e4b7dd54843
link
/test istio-pilot-multicluster-e2e

prow/e2e-simpleTests.sh
30775d5f28165388a060d36071896e4b7dd54843
link
/test e2e-simpleTests

prow/e2e-bookInfoTests-v1alpha3.sh
30775d5f28165388a060d36071896e4b7dd54843
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

prow/e2e-simpleTests-cni.sh
30775d5f28165388a060d36071896e4b7dd54843
link
/test e2e-simpleTests-cni

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@SataQiu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3-mcp.sh
30775d5f28165388a060d36071896e4b7dd54843
link
/test istio-pilot-e2e-envoyv2-v1alpha3-mcp

prow/e2e-mixer-no_auth.sh
30775d5f28165388a060d36071896e4b7dd54843
link
/test e2e-mixer-no_auth

prow/e2e-mixer-no_auth-mcp.sh
30775d5f28165388a060d36071896e4b7dd54843
link
/test e2e-mixer-no_auth-mcp

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
30775d5f28165388a060d36071896e4b7dd54843
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-multicluster-e2e.sh
30775d5f28165388a060d36071896e4b7dd54843
link
/test istio-pilot-multicluster-e2e

prow/e2e-bookInfoTests-v1alpha3.sh
30775d5f28165388a060d36071896e4b7dd54843
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

prow/e2e-simpleTests-cni.sh
30775d5f28165388a060d36071896e4b7dd54843
link
/test e2e-simpleTests-cni

prow/istio-integ-k8s-tests.sh
30775d5f28165388a060d36071896e4b7dd54843
link
/test istio-integ-k8s-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@SataQiu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3-mcp.sh
30775d5f28165388a060d36071896e4b7dd54843
link
/test istio-pilot-e2e-envoyv2-v1alpha3-mcp

prow/e2e-mixer-no_auth.sh
30775d5f28165388a060d36071896e4b7dd54843
link
/test e2e-mixer-no_auth

prow/e2e-mixer-no_auth-mcp.sh
30775d5f28165388a060d36071896e4b7dd54843
link
/test e2e-mixer-no_auth-mcp

prow/e2e-bookInfoTests-v1alpha3.sh
30775d5f28165388a060d36071896e4b7dd54843
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

prow/e2e-simpleTests-cni.sh
30775d5f28165388a060d36071896e4b7dd54843
link
/test e2e-simpleTests-cni

prow/istio-integ-k8s-tests.sh
30775d5f28165388a060d36071896e4b7dd54843
link
/test istio-integ-k8s-tests

prow/istio-pilot-multicluster-e2e.sh
30775d5f28165388a060d36071896e4b7dd54843
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


Remote media support verification

The plan for this item is to support remote media by presenting a virtual CD drive over the USB2.0 vhub as a usb gadget device. For more details check at https://github.com/openbmc/openbmc/issues/261

As of now, closing this, will reopen when we get the equivalent.


Ignore nested parameter

Is it possible to ignore a nested parameter? For example the data of my requests looks like this:
{
  "data": {
    "key": "value",
    "timestamp": "2022-08-04"
  }
}

In this example, I would like to ignore timestamp but not key when creating the cache key. Yes, I could overwrite the cache_key function, but feels like this should be part of the library? Maybe like this: data.timestamp

Interesting idea. Do you happen to have any cases where the key you want to ignore is more than 1 level deep (like data.key_1.key_2)?
If not, that would make things much easier. I think having a single "root" element in a request body (data in your example) is fairly common. We could possibly add an option to apply ignored_parameters to anything under that root key. That would be a much simpler change to make than supporting arbitrary levels of JSON keys using dot notation.

I could work on a PR on this @JWCook
As far as I see, this would be adding some logic to the filter_sort_* functions oft cache_keys.py.

That would be great! I don't think the filter_sort_* functions need to change, but normalize_json_body and everything up the call chain from there will need to change.
To get you started, the new normalize_json_body() would look something like this:
def normalize_json_body(
    original_body: Union[str, bytes],
    ignored_parameters: ParamList,
    content_root_key: str = None,
) -> Union[str, bytes]:
    """Normalize and filter a request body with serialized JSON data"""
    if len(original_body) <= 2 or len(original_body) > MAX_NORM_BODY_SIZE:
        return original_body

    try:
        body = json.loads(decode(original_body))
        if content_root_key and isinstance(body, dict) and content_root_key in body:
            body[content_root_key] = filter_sort_json(body[content_root_key], ignored_parameters)
        else:
            body = filter_sort_json(body, ignored_parameters)
        return json.dumps(body)
    # If it's invalid JSON, then don't mess with it
    except (AttributeError, TypeError, ValueError):
        logger.debug('Invalid JSON body')
        return original_body

Then add a content_root_key setting to CacheSettings, and pass that from BaseCache.create_key() to cache_keys.create_key(), and so on.


Refactor Makefile to depend on filenames

Uaargh, forgot the .gitignore, done in Add {policy, annotated-policy}.wasm to .gitignore.


Fixes dark LaTeX blocks

Hello. This pull request fixes the issue with dark blocks of LaTeX mentioned in #14.
After some digging around in Wikipedia's CSS it seems there are two types of LaTeX blocks: image-inline and image-display. Originally the extension only adjusted the color of the inline blocks.
This PR adds display blocks as well and is tested to be working on Firefox 95.0.2 on Arch Linux.
I've never made a pull request before so please let me know if I am missing anything. Thanks!

Wow, good job! I will merge your PR, great work and thank you for contributing :)


Remove imports of Data.Typeable.Internal

This module is removed from base in ghc-8.2. Luckily, it doesn't appear to have
been strictly necessary.
I'm depending on your CI to verify this works with versions earlier than 8.2

Looks good, thanks!


chore: pfcl++

Author Checklist
All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.
I have...

[ ] included the correct type prefix in the PR title
[ ] added ! to the type prefix if API or client breaking change
[ ] added appropriate labels to the PR
[ ] targeted the correct branch (see PR Targeting)
[ ] provided a link to the relevant issue or specification
[ ] added a changelog entry to CHANGELOG.md
[ ] included comments for documenting Go code
[ ] updated the relevant documentation or specification
[ ] reviewed "Files changed" and left comments if necessary
[ ] confirmed all CI checks have passed

Reviewers Checklist
All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.
I have...

[ ] confirmed the correct type prefix in the PR title
[ ] confirmed all author checklist items have been addressed
[ ] reviewed state machine logic
[ ] reviewed API design and naming
[ ] reviewed documentation is accurate
[ ] reviewed tests and test coverage
[ ] manually tested (if applicable)

General note, we should try to not approve PRs when there is no related Changelog. Of course anyone can forget.

In this case, the PR wasn't for a missing changelog but for moving two backported PRs from Unreleased to v0.2.5. We tend to do that when we backport and create a release.


K8s 1.26.4 update

linked issue: https://github.com/rancher/rancher/issues/41113
a new branch for 1.26 needs to be created with the upstream changes and then base branch of this PR can be changed to that branch.

closing since client-go updated to 1.27. ref PR: https://github.com/rancher/client-go/pull/6


[Question] Cannot choose"C+E Security IS" in a button in FormFlow?

System Information

SDK Language: .Net
SDK Version: <IP_ADDRESS>
Development Environment: webchat

Bot Info

Bot name: Gaia
Bot handle: kustobot
App ID:
Connected channels:

Issue Description
We compose buttons out of text in our but, in FormFlow. When the button contains "C+E Security IS" it's impossible to click it.
We get "“C+E Security IS” is not an existing account name option."
Then we specify "2" as the button it the first one, and it chooses a different button.
Then we go back and specify 1 and it finally works. But we cannot click the "C+E Security IS".
Can you please fix?

Using quotes also doesn't work

This is not a question, it's an issue.
Also any update on this?

Can you please share your code, we do not have enough info to help you without it.

@radennis Please upgrade your bot to v 3.9 and let us know if your issue is resolved.  There was a problem with FormFlow fields defined with a Describe attribute, but no Terms: fixed by this PR https://github.com/Microsoft/BotBuilder/pull/2990 (and a few subsequent PRs)
Also, please show how you are defining this form in code, so we are able to reproduce the problem.
Thank you.

Thanks, I'll upgrade my bot and see if it helps.
Here's a code snippet of how I'm doing it:
        private static Task<bool> DefineExistingPcCode(KustoOnBoardForm state, Field<KustoOnBoardForm> field)
        {
            foreach (var account in GetExistingPcCodes(state))
            {
                field
                    .AddDescription(account, account)
                    .AddTerms(account, account);
            }

            var newAccountChoice = "I have a different Pc Code";
            field
                .AddDescription(c_newPcCodeRequest, newAccountChoice)
                .AddTerms(c_newPcCodeRequest, newAccountChoice);

            field.SetType(null);
            field.SetActive(IsExistingAccountChosen);
            return Task.FromResult(true);
        }

Hi, just wanted to update back that I tried upgrading to <IP_ADDRESS> and still get the same error.

Please let us know what can be done.

Thanks for the update, we are actively looking into this.

@radennis we are unable to repro the same behavior with the code given.  Are you able to share your whole project?  If not can you at least share the code for your form and what is the IsExistingAccountChosen code?

I've sent you the project code separately as we rather not publish it on the web.
Here's the snippet you asked for:
        public string GetAccountName()
        {
            return IsExistingAccountChosen(this)
                ? ExistingAccountName
                : NewAccountName;
        }
        public static bool IsExistingAccountChosen(KustoOnBoardForm state)
        {
            var newAccountCondition = string.IsNullOrEmpty(state.ExistingAccountName) ||
                state.ExistingAccountName.Equals(c_newAccountRequest, StringComparison.InvariantCulture);
            return !newAccountCondition;
        }

Thank you, I am waiting on approval to view the source.

Hi any update on this?

We were still not able to reproduce, I am awaiting approval in RAM to view the source to try to repro.

Looking into this now

@radennis I was able to reproduce, It seems the '+' char is the issue here.  I'm still trying to pin down the exact cause, but if as a workaround, for now, can you try using the work "and" rather than '+' and see if that fixes the problem for you?

Thanks @JasonSowers for looking into this. Unfortunatelly I cannot change the content of the button since it is generated by getting the account name. Therefore when the account name if "C + E" I need to show the exact same string to the user...

I am still looking into this as a bug, I will update you when I know more.

Thanks for the update

You need to regex escape your string.  The terms we match on our regex and the + is interpreted as a regex.


etc/images.yml: add Fedora CoreOS 33

We have to setup a new mirror service first. Until then on-hold.

Replaced by 0c8416e3f7a7dd61ee73bc33d9db144b0fc97c57.


Theory

[ ] Conservation of chemical potential
[ ] McNabb and Foster equations
[ ] Soret effect
[ ] Triangle model, implantation approximation
[ ] - [ ] Units
[ ] What's the retention

@KulaginVladimir as you can see we had planned to write this Theory page for quite some time!

@RemDelaporteMathurin, I can try to fill this gap


FreeBSD 13.1 support

According to https://www.freebsd.org/security/#sup 13.0 reaches EOL on 2022-08-31. After that the package cluster would upgrade 13.* builders (e.g., 130amd64) to 13.1 (e.g., 131amd64), rendering /latest and /quarterly (but not /release_0) package repos unusable on 13.0 because the old kernel/libc/libthr/etc may not support features introduced by 13.1.

Thanks, I will update it soon.

Thanks. Seems to work OK.


chore(deps): override @types/node

chore(deps): override @types/node
This makes all @types/node versions use the one pinned in the workspace root package.json.
chore(yarn-plugin-allow-scripts): remove dev deps
These are installed from the workspace root.

Current dependencies on/for this PR:

main

PR #875   👈

This stack of pull requests is managed by Graphite.


move {{ and }} matching so that it gets highlighted correctly

Could you give a reproducible example and an explanation?

NVM. I improved the tests to make it more clear.

Thanks!


fix: Add quotes to Japanese translations containing multi-byte symbols

Description

Enclose Japanese translation strings with double quotes to prevent YAML parse errors
Double quotes are necessary when strings contain multi-byte symbols like ？
Fixes the "found character that cannot start any token" error

Resolves https://github.com/sidekiq-cron/sidekiq-cron/issues/514
Screenshot

Double quotes are necessary when strings contain multi-byte symbols like ？

The PR itself seems fine, but I think the cause of the error is the leading %, not the ？.
> YAML.load("hoge: aaa？")
=> {"hoge"=>"aaa？"}
> YAML.load("hoge: %aaa")
(venison):86:in `<main>': (<unknown>): found character that cannot start any token while scanning for the next token at line 1 column 7 (Psych::SyntaxError)
> YAML.load("hoge: a%aa")
=> {"hoge"=>"a%aa"}


mWeb - Chat - 3 backtick code block is not applied correctly

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 1.4.80-1
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Issue reported by: Applause - internal Team
Action Performed:

Go to https://staging.new.expensify.com/home
Tap on a report
Enter gaj id
Send the message

Expected Result:
3 backtick code block must be applied correctly
Actual Result:
3 backtick code block is not applied correctly
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android: Native
[x] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence

https://github.com/Expensify/App/assets/78819774/e7adb0a8-3c02-43f2-99d7-5038fd1641ac
View all open jobs on GitHub

@puneetlath  FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

We think that this bug might be related to #vip-vsp

Based on this test, it seems like this is actually the expected behavior.
So I'm going to remove this as a blocker and close it out.


Update webrtc-sdp

We got our framerate patch merged on webrtc-sdp repo, now we can get rid of that SDP warning related to the unknown attribute framerate, and this will allow us to send this attribute to the browser.

Closed by https://github.com/mavlink/mavlink-camera-manager/pull/414


[KerasCV] Image segmentation with a U-Net-like architecture is not running successfuly.

When trying to run the code from this article, the error is encountered on creating the datasets. The same issue persists both in Colab and on local machine.
Code Cell:
augmented_train_ds = (
    train_ds.shuffle(BATCH_SIZE * 2)
    .map(augment_fn, num_parallel_calls=AUTOTUNE)
    .batch(BATCH_SIZE)
    .map(unpackage_inputs)
    .prefetch(buffer_size=tf.data.AUTOTUNE)
)
resized_val_ds = (
    val_ds.map(resize_fn, num_parallel_calls=AUTOTUNE)
    .batch(BATCH_SIZE)
    .map(unpackage_inputs)
    .prefetch(buffer_size=tf.data.AUTOTUNE)
)

Error:

---------------------------------------------------------------------------

TypeError                                 Traceback (most recent call last)

[<ipython-input-9-7a534e67b8f6>](https://localhost:8080/#) in <cell line: 2>()
      1 augmented_train_ds = (
----> 2     train_ds.shuffle(BATCH_SIZE * 2)
      3     .map(augment_fn, num_parallel_calls=AUTOTUNE)
      4     .batch(BATCH_SIZE)
      5     .map(unpackage_inputs)

27 frames

[/usr/local/lib/python3.10/dist-packages/keras_cv/src/layers/preprocessing/random_choice.py](https://localhost:8080/#) in tf___augment(self, inputs, *args, **kwargs)
     12                 try:
     13                     do_return = True
---> 14                     retval_ = ag__.converted_call(ag__.ld(tf).switch_case, (), dict(branch_index=ag__.ld(selected_op), branch_fns=ag__.ld(branch_fns), default=ag__.autograph_artifact(lambda : ag__.ld(inputs))), fscope)
     15                 except:
     16                     do_return = False

TypeError: Exception encountered when calling layer 'rand_augment' (type RandAugment).

in user code:

    File "/usr/local/lib/python3.10/dist-packages/keras_cv/src/layers/preprocessing/base_image_augmentation_layer.py", line 420, in call  *
        outputs = self._format_output(self._augment(inputs), metadata)
    File "/usr/local/lib/python3.10/dist-packages/keras_cv/src/layers/preprocessing/rand_augment.py", line 127, in _augment  *
        result = super()._augment(sample)
    File "/usr/local/lib/python3.10/dist-packages/keras_cv/src/layers/preprocessing/random_augmentation_pipeline.py", line 104, in _augment  *
        result = tf.cond(
    File "/usr/local/lib/python3.10/dist-packages/keras/src/utils/traceback_utils.py", line 70, in error_handler
        raise e.with_traceback(filtered_tb) from None
    File "/tmp/__autograph_generated_filej0tk3t3e.py", line 46, in tf__call
        ag__.if_stmt(ag__.ld(images).shape.rank == 3, if_body_1, else_body_1, get_state_1, set_state_1, ('outputs',), 1)
    File "/tmp/__autograph_generated_filej0tk3t3e.py", line 24, in if_body_1
        outputs = ag__.converted_call(ag__.ld(self)._format_output, (ag__.converted_call(ag__.ld(self)._augment, (ag__.ld(inputs),), None, fscope), ag__.ld(metadata)), None, fscope)
    File "/tmp/__autograph_generated_fileytz6kjkc.py", line 14, in tf___augment
        retval_ = ag__.converted_call(ag__.ld(tf).switch_case, (), dict(branch_index=ag__.ld(selected_op), branch_fns=ag__.ld(branch_fns), default=ag__.autograph_artifact(lambda : ag__.ld(inputs))), fscope)

    TypeError: Exception encountered when calling layer 'random_choice' (type RandomChoice).

    in user code:

        File "/usr/local/lib/python3.10/dist-packages/keras_cv/src/layers/preprocessing/base_image_augmentation_layer.py", line 420, in call  *
            outputs = self._format_output(self._augment(inputs), metadata)
        File "/usr/local/lib/python3.10/dist-packages/keras_cv/src/layers/preprocessing/random_choice.py", line 110, in _augment  *
            default=lambda: inputs,

        TypeError: branches[0] and branches[1] arguments to tf.switch_case must have the same number, type, and overall structure of return values.

        branches[0] output: {'images': <tf.Tensor 'sequential/rand_augment/cond/random_choice/switch_case/indexed_case/Identity:0' shape=(160, 160, 3) dtype=float32>, 'segmentation_masks': <tf.Tensor 'sequential/rand_augment/cond/random_choice/switch_case/indexed_case/Identity_1:0' shape=(160, 160, 1) dtype=float32>}
        branches[1] output: {'images': <tf.Tensor 'sequential/rand_augment/cond/random_choice/switch_case/indexed_case/Identity:0' shape=(160, 160, 3) dtype=float32>, 'segmentation_masks': <tf.Tensor 'sequential/rand_augment/cond/random_choice/switch_case/indexed_case/Identity_1:0' shape=(160, 160, 1) dtype=int64>}

        Error details:
        Tensor("sequential/rand_augment/cond/random_choice/switch_case/indexed_case/Identity_1:0", shape=(160, 160, 1), dtype=float32) and Tensor("sequential/rand_augment/cond/random_choice/switch_case/indexed_case/Identity_1:0", shape=(160, 160, 1), dtype=int64) have different types

    Call arguments received by layer 'random_choice' (type RandomChoice):
      • inputs={'images': 'tf.Tensor(shape=(160, 160, 3), dtype=float32)', 'segmentation_masks': 'tf.Tensor(shape=(160, 160, 1), dtype=int64)'}

Call arguments received by layer 'rand_augment' (type RandAugment):
  • inputs={'images': 'tf.Tensor(shape=(160, 160, 3), dtype=float32)', 'segmentation_masks': 'tf.Tensor(shape=(160, 160, 1), dtype=int64)'}

Probably a duplicate of https://github.com/keras-team/keras-io/issues/1512.

hello @jazzman1825, I was going through the article and there is no code containing 'augmented_train_ds' so if you could share colab file of your code that might be more helpful. Also this might help you https://stackoverflow.com/questions/77019222/sequential-model-error-in-unet-keras-image-segmentation.

Hey @SarthakJain333! Thanks for your comment, I have had a look at the article and colab environment once again and it seems like the code has been modified and now runs with no issue. Although the code is now different and runs perfectly, the Last modified:  line still states 2020/04/20. No idea why this line wasn't updated with the latest modification, but anyways it makes the issue outdated now.


Changes to KV View - Node & Bucket

Added some useful metrics, removed some which are generally not useful.
Grouped some things in rows and resized all of the panels to be the same size.
Before, we had rows in the grid of 2, 3, 4 and 5 panels on each row, which made visually correlating events more difficult.

Before

After

Looks good Vesko - thanks for the patch!


Added alarms support for ElasticSearch

disco_alarms.py will now support setting alarms for ElasticSearch domains. Additionally, when creating, updating, or deleting ElasticSearch domains, alarms will now be created/updated/deleted, respectively.
There was also a change made to the parsing logic for alarm metrics to support metrics with periods in them because some import ElasticSearch metrics have spaces in them.

For future work. We need to rewrite disco_alarms :(

I think no one would shed a tear if disco_alarms.py met with an unfortunate accident in a back alley. :)

👍


Add CLI argument support

I've been using CLImate at work lately. I love it, but I hated having to use getopt() or $argv to talk to my command line arguments. I looked into various console libraries, but they also did output in addition to argument processing. I saw in #29 you said you weren't opposed to CLImate doing argument parsing, so I added it. I tried to follow the existing API and internal code conventions as much as I can.
This change adds an argument manager to the CLImate object. Users can define arguments against the argument manager, parse arguments on the command line into those defined arguments, retrieve CLI argument values, and generate a usage statement based on user defined arguments.
An argument is defined as something that's passed along to a script, either in a short form ("-a foo"), long form ("--foo bar"), both, or neither to process arguments after the prefixed argument list. Arguments can be:

marked as required
have default values
have their values cast to string, int, float, or boolean data types
set true if they're defined on the command line (for cases where a value isn't needed like "-f" to force or "--help" to show a usage statement).
have values set in "-key value" or "-key=value" form on the command line.

Arguments that are required but not defined on the command line generate an exception that's sent back to calling code.
Here's a simple example. Assume you have a script that pushes a local directory to some SSH server. That script needs a username, a password, a host, maybe an option to print usage, one to overwrite existing files, maybe a verbosity option, and a path to push to my server. I may store the username and hostname internally, but let users enter their own if they like, but they have to provide a password. I'd probably call it by running:
php ./pusher.php -u myusername -p secret -h hostname --force -v ./push_me

That script would look like:
<?php

require __DIR__ . '/vendor/autoload.php';

use League\CLImate\CLImate;

$climate = new CLImate;
$climate->description('Awesome SCP Pusher v0.01');
$climate->arguments->add([
    'user' => [
        'prefix' => 'u',
        'longPrefix' => 'user',
        'description' => 'SSH Username',
        'defaultValue' => 'myuser',
    ],
    'password' => [
        'prefix' => 'p',
        'longPrefix' => 'password',
        'description' => 'SSH Password',
        'required' => true,
    ],
    'host' => [
        'prefix' => 'H',
        'longPrefix' => 'host',
        'description' => 'SSH Hostname',
        'defaultValue' => 'myhost.local'
    ],
    'force' => [
        'prefix' => 'f',
        'longPrefix' => 'force',
        'description' => 'Overwrite files on copy',
        'definedOnly' => true,
    ],
    'verbose' => [
        'prefix' => 'v',
        'longPrefix' => 'verbose',
        'description' => 'Verbose output',
        'definedOnly' => true,
    ],
    'help' => [
        'prefix' => 'h',
        'longPrefix' => 'help',
        'description' => 'Print a usage statement',
        'definedOnly' => true,
    ],
    'path' => [
        'description' => 'The path to push',
    ],
]);

// Print a usage statement on --help
if ($climate->arguments->defined('help')) {
    $climate->usage();
    exit();
}

// Parse arguments.
try {
    $climate->arguments->parse();
} catch (Exception $e) {
    // Let us know if arguments were missing.
    $climate->error($e->getMessage());
    $climate->br();
    $climate->usage();
    exit();
}

// Echo instead of push.
$climate->out('Username: ' . $climate->arguments->get('user'));
$climate->out('Hostname: ' . $climate->arguments->get('host'));

if ($climate->arguments->get('force')) {
    $climate->out("I'm going to overwrite on copy.");
}

Here's an execution that echo's the usage statement:
$ php ./pusher.php -h
Awesome SCP Pusher v0.01

Usage: ./pusher.php [-f, --force] [-H host, --host host (default: myhost.local)] [-h, --help] [-p password, --password password] [-u user, --user user (default: myuser)] [-v, --verbose] [path]

Required Arguments:
	-p password, --password password
		SSH Password

Optional Arguments:
	-f, --force
		Overwrite files on copy
	-h, --help
		Print a usage statement
	-H host, --host host (default: myhost.local)
		SSH Hostname
	-u user, --user user (default: myuser)
		SSH Username
	-v, --verbose
		Verbose output

And an execution that spits out those debug out()s:
$ php ./pusher.php -u bob -p secret -f ./my-dir
Username: bob
Hostname: myhost.local
I'm going to overwrite on copy.

The new changes pass all tests with 100% new code coverage, minus one line that needs to talk to the global scope to get $argv. Tests use a mocked $argv.
Let me know if this looks okay to you. If it does and gets merged I can write public-facing documentation for this too.

:+1:

Awesome, thanks so much @klaude! I'll take a look at this over the next day or two and get back to you.

Ain't no thing, @joetannenbaum. I kind of dropped a ton of code on you out of the blue, so let me know if anything needs clarifying. :) This is the first time I've seen Scrutinizer CI reports. While you're looking at the branch I'll see if I can address the things Scrutinizer brought up in a way that doesn't change how it works.

@joetannenbaum have you had a chance to look at this yet? I've brought in the latest master branch changes so it'll merge. Let me know if there's anything you'd like changed up.

I'm actually just spending some time with it now! So far so good, this is exciting stuff. Let me tinker for a little while tonight and I'll hit you back.

Any update on this? Looks like a great enhancement.

Sorry, some Life Stuff™ got in the way. I'll be finishing the review and merging this in the next couple of days!

Ain't no thing, @joetannenbaum. Real Life happens sometimes. :) I've merged in and fixed a conflict or two with the latest upstream branch.

Hey @klaude, finally got around to checking this out fully, great stuff. I'm about 95% done with any refactoring (https://github.com/thephpleague/climate/tree/klaude-argument_support), mostly simplifying certain methods, a lot of extracting, etc.
One of my remaining issues is minor, mostly about semantics, succinctness, and clarity. I removed the huge constructor for Argument as nothing was using it anyway besides createFromArray and it was a little overbearing.
I'm probably going to change defaultValue to just default, and it took me a little bit to figure out what definedOnly was. Is noValue a better name for that?
Otherwise we're in the homestretch, looking forward to merging this, it's a big win. Thanks for all of your work!

I'm probably going to change defaultValue to just default, and it took me a little bit to figure out what definedOnly was. Is noValue a better name for that?

I think that works, @joetannenbaum, and I dig your refactors. Let me know if there's anything you'd like me to do.

Ok this is merged! I'll tag it officially either tonight or tomorrow after I fix a couple of other issues. Thanks again for all of your hard work @klaude!


[GSoC] xxx - DeBERTa Sequence Classification

This notebook instructs users on how to perform text classification using the DeBERTa model using OpenVINO Runtime, and provides instructions for testing and validating the model.
In this notebook, we utilize the DeBERTa model provided by Hugging Face. By incorporating disentangled attention and an enhanced mask decoder, DeBERTa surpasses BERT and RoBERTa in the majority of natural language understanding (NLU) tasks.

Thank you for your contribution. Before we do the review please do the self-check first (tick the item when it's done):

[ ] each function is described by docstrings and type hints
[ ] notebook contains explicit descriptions and explanatory diagrams
[ ] there is a README.md file in consistent style (look at other notebooks)
[ ] the notebook is added to the main README and notebooks/README files
[ ] there are no grammar, interpunctions or typo issues (use any free tool for that e.g. Grammarly)
[ ] there are no committed files besides notebook and readme (please use images or videos from data dir)
[ ] all CI checks passed

We will review only if all the above items are checked.

I have done all of the items, please review this PR, thank you!

Thank you, we will review it when we have some resources. Please note we're reviewing PRs in FIFO style.

Understood, thanks for letting me know.

[ ]  each function is described by docstrings and type hints
[ ]  notebook contains explicit descriptions and explanatory diagrams
[ ]  the notebook doesn't use any data (image, video, etc.) that is not CC4.0 licensed
[ ]  there is a README.md file in consistent style (look at other notebooks)
[ ]  the notebook is added to the main README and notebooks/README files
[ ]  there are no grammar, interpunctions or typo issues (use any free tool for that e.g. Grammarly)
[ ]  there are no committed files besides notebook and readme (please use images or videos from data dir)
[ ]  all CI checks passed

Thank you, we will review it when we have some resources. Please note we're reviewing PRs in FIFO style.
Note: The PR must be opened before April 4th, it doesn't have to be reviewed or merged.

I'm closing this due to inactivity for a long time. Nevertheless, thank you for contributing and applying for Google Summer of Code. We encourage you to consider GSoC 2024 as well :)


[Feature Request] Related Content

Hello!
Listing related posts as "Related" or "See also" at the end of the post, increases user interaction. May be we should have Related Content in Er?
I am thinking more like BeautifulHugo or min_night.
Thanks!

I'm happy to add related content support into the theme, but will have to think about how to style the related section to fit into the theme. When I have time I might get down to doing this, or I'm also happy to review a PR

Thank you! Wish I could help. A go beginner here.


When a DSR fails - the row in the privacy request dashboard gets stuck in an hover state

When a DSR fails - you'll see the row go into an active/hover state and get stuck.
hover state meaning the row is light grey and the reprocessing button is showing.
Steps

Spin up the test_env
Create a bogus saas connector
Do a privacy request on the privacy center
Approve the privacy request

It will error and the row will get stuck in an active state.

@adamsachs To try to reproduce this in the testing of #1710

@adamsachs To try to reproduce this in the testing of #1710

just noting that i was able to reproduce the problem in testing, and https://github.com/ethyca/fides/issues/1710 does not resolve the issue. seems to be more isolated on the front-end.

@mfbrown @adamsachs - Could either of you clarify what the 'fixed' state looks like for a DSR row? In the code, it looks like it is intentionally showing the Reprocess button on error. Are we wanting different options when it errors?


Possible extension this method for general DNA language model

Hi, thanks for your great work. I wonder if it is possible to apply this method for general sequence model like hyenaDNA or DNABERT, to explain the model performance. Moreover, since in your method you used many tests based on randomness, like randomly subsample sequence and random insert cres, I wonder if changing the random seeds will affect the results a lot or not. I do see sometimes the change will be huge for permutation test. Thanks.

Thanks. You can generate sequence perturbations using CREME, but it's not clear whether that will help interpret hyenaDNA or DNABERT. I suggest looking at a few recent works:

https://doi.org/10.1101%2F2<IP_ADDRESS>2810
https://www.biorxiv.org/content/10.1101/2<IP_ADDRESS>5418v1
https://www.biorxiv.org/content/10.1101/2<IP_ADDRESS>7970v1

In terms of randomness, we typically shuffle 10-100 times and average predictions. You can think of this as a marginalization over the region that is randomized+averaged. We do note that selection of backgrounds could have some effect on the results due to finite sampling. Dinuc shuffle is the standard (for now).

Thanks for your answers, they are really helpful.


[6.x] Limited properties returned by morph type

This is a functionality to allow a query like "morphWith" but named "morphProperties" to limit the properties of morph by type.

Tests still aren't running. This is bizar..

I also adapted the modifications to pass the styleci.

I made this changes on my laravel installation because I need it, and I assumed it will be nice to share this. I made only a few changes, please check them and make the improvements they need.

$recommendations = Recommendation::with(['recommendable' => function (MorphTo $morphTo) {
    // This eager load some relationships for morph type
    $morphTo->morphWith([
        User::class => [],
        UserVacantion::class => ['user:id,username'],
    ]);

    // This limit the properties showed for morph type. Please insert here also the columns of the relationships requested in $morphTo->morphWith (ex. above I eagler load the "User" relationship and below I requested user_id to be selected in query)
    $morphTo->morphProperties([
        User::class => ['id', 'username'],
        UserVacantion::class => ['id', 'user_id'],
    ]);
}])->get();

I am closing this pull request because it lacks sufficient explanation, tests, or both. It is difficult for us to merge pull requests without these things because the change may introduce breaking changes to the framework.
Feel free to re-submit your change with a thorough explanation of the feature and tests - integration tests are preferred over unit tests. Please include it's benefit to end users; the reasons it does not break any existing features; how it makes building web applications easier, etc.
Thanks!

The idea is to make something like this code but with polymorphic relationships.
$query = Team::where('company_id', '=', $company_id)->with(['leader' => function ($query) {
      $query->select(['id', 'username']);
}]);

We can select what properties of morphTo model to be returned in a single query, based on it's class.
What you don't understand? because it's a simple modification.
Case: I have 'Photo' model which morphTo User and Album models. When I request all Photos I want to recevie for User only 'id, username', and for Album only 'id, name'
$photos = Recommendation::with(['photographable' => function (MorphTo $morphTo) {
    $morphTo->morphProperties([
        User::class => ['id', 'username'],
        Album::class => ['id', 'name'],
    ]);
}])->get();

Any news about this? I had a case that needs this functionality

Any news about this? I had a case that needs this functionality

I don't think they had understand the feature, but this commit resolve it.

@ioan-cristea this changes for fetch selected columns of morph type model right?
Current Scenario:
My Query:

Result may be:
"stock_adjustment_item" => array:12 [
    "id" => 1
    "stock_adjustment_id" => 1
    "product_id" => 1
    "location_id" => 1
    "location_type" => "STORE"
    "quantity" => "5.00"
    "unit_of_measure_derivative_id" => null
    "derivative_ratio" => null
    "input_quantity" => "5.00"
    "created_at" => "2023-08-28T05:44:12.000000Z"
    "updated_at" => "2023-08-28T05:44:12.000000Z"
    "stock_adjustment" => array:3 [
        "id" => 1
        "type_id" => 1
        "reason" => "just testing"
    ]
]

here we would expect like this:

"stock_adjustment_item" => array:3 [
    "id" => 1
    "stock_adjustment_id" => 1
    "stock_adjustment" => array:3 [
        "id" => 1
        "type_id" => 1
        "reason" => "just testing"
    ]
]

Yes, you can limit the columns that are selected for for the morph type model.
You need to use like this
$morphTo->morphProperties([         StockAdjustmentItem::class => ['id', 'stock_adjustment_id'],         AnotherStockAdjustmentItem::class => ['id', 'stock_adjustment_id'],         SpecialStockAdjustmentItem::class => ['id', 'stock_adjustment_id', 'a_special_column_for_this_type'], ]);

Yes, you can limit the columns that are selected for for the morph type model. You need to use like this
$morphTo->morphProperties([
        StockAdjustmentItem::class => ['id', 'stock_adjustment_id'],
        AnotherStockAdjustmentItem::class => ['id', 'stock_adjustment_id'],
        SpecialStockAdjustmentItem::class => ['id', 'stock_adjustment_id', 'a_special_column_for_this_type'],
]);

Sorry for the late reply. it's not working.
below relation I need to load with selected columns:
StockAdjustmentItem::class => ['id', 'stock_adjustment_id'], // this load all columns instead of  selected columns.
StockAdjustment::class => ['id', 'type'],

It was a very nice feature @ioan-cristea
How @taylorotwell didn't understand that.

I confirm constraint works well https://laravel.com/docs/10.x/eloquent-relationships#constraining-eager-loading-of-morph-to-relationships


Incremental mode and CSV

Hi,
I have one question: why are incremental mode and CSV log file incompatible?
Thanks

Hi,
They are fully compatible, what make you think that? The only thing that is not possible with cvslog formt is multiprocessing because the Perl Module Text::CSV_XS doen't allow us to seek in the file.
Regards

Hi,
Actually I would like to use the incremental feature to run pgbadger remotely once an hour and to not start over the parsing every time. But I have the impression the LAST_PARSED information is not taken into consideration. Am I wrong?
Thanks

In remote mode the entire file is parsed because it is not possible to seek in the file remotely. Line before last run are just skipped but it can take time to reach the last position stored in the LAST_PARSED file following the size of the log.

In remote mode the entire file is parsed because it is not possible to seek in the file remotely.

According to docs, the -r switch runs a cat command over a passwordless (presumably key-based) ssh connection. I guess that part doesn't allow the random access.
But random access would be possible if sshfs were being use to mount the remote logs [1] [2] with some performance penalty.

Righ, sshfs will allow random access.


Update Task Annotation from task oriented instead of schema

The update mainly focus on

Task oriented annotation
Add task options value as default to schema
Refine description field

@RackHD/corecommitters @iceiilin @cgx027 @pengz1

jenkins: test this please

@WangWinson : could you please attach some screenshot about the view of task annotation?

:+1:

:+1:

:+1:


essif tir - get issuer

Call to EBSI ledger to get issuer record by its DID.

@Vid201 this PR looks great and is highly appreciated :clap:  We will review it in detail and merge it over the WE!

@Vid201 based on your good work I could complete the TrustedIssuerRegistryPolicy #39  for the Auditor now.
This policy can now be applied when running the verification of VCs. For example via CLI:
 ./ssikit.sh  vc verify -p TrustedIssuerRegistryPolicy vc.json
Verifying from file vc.json ...

Results:

TrustedIssuerRegistryPolicy:             true
Verified:                true

@Vid201 based on your good work I could complete the TrustedIssuerRegistryPolicy #39  for the Auditor now.
This policy can now be applied when running the verification of VCs. For example via CLI:
 ./ssikit.sh  vc verify -p TrustedIssuerRegistryPolicy vc.json
Verifying from file vc.json ...

Results:

TrustedIssuerRegistryPolicy:             true
Verified:                true

Cool, that is good to hear! 👍


Synthesis failed for Google.Cloud.PubSub.V1

Hello! Autosynth couldn't regenerate Google.Cloud.PubSub.V1. :broken_heart:
Please investigate and fix this issue within 5 business days.  While it remains broken,
this library cannot be updated with changes to the Google.Cloud.PubSub.V1 API, and the library grows
stale.
See https://github.com/googleapis/synthtool/blob/master/autosynth/TroubleShooting.md
for trouble shooting tips.
Here's the output from running synth.py:
ogle.Cloud.PubSub.V1
Updated 1 path from the index
Updated 1 path from the index
git detects no change in Google.Cloud.PubSub.V1; skipping compatibility checking
Regenerating projects
API catalog contains 168 entries
Done.
2021-08-10 08:59:51,284 autosynth [INFO] > Changed files:
2021-08-10 08:59:51,284 autosynth [INFO] > M apis/Google.Cloud.PubSub.V1/synth.metadata
2021-08-10 08:59:51,284 autosynth [DEBUG] > Running: git log 10185d07a4db1d76a888a119aeab1f2287b35105 -1 --no-decorate --pretty=%s
2021-08-10 08:59:51,289 autosynth [DEBUG] > Running: git log 10185d07a4db1d76a888a119aeab1f2287b35105 -1 --no-decorate --pretty=%b%n%nSource-Author: %an <%ae>%nSource-Date: %ad
2021-08-10 08:59:51,293 autosynth [DEBUG] > Running: git add -A
2021-08-10 08:59:51,336 autosynth [DEBUG] > Running: git status --porcelain
2021-08-10 08:59:51,382 autosynth [DEBUG] > Running: git commit -m feat: add total_billed_time response field

Committer: @cherba
PiperOrigin-RevId: 389755489

Source-Author: Google APIs<EMAIL_ADDRESS>Source-Date: Mon Aug 9 16:48:51 2021 -0700
Source-Repo: googleapis/googleapis
Source-Sha: 10185d07a4db1d76a888a119aeab1f2287b35105
Source-Link: https://github.com/googleapis/googleapis/commit/10185d07a4db1d76a888a119aeab1f2287b35105
[autosynth-Google.Cloud.PubSub.V1-132 55d5379ba] feat: add total_billed_time response field
 1 file changed, 1 insertion(+), 1 deletion(-)
2021-08-10 08:59:51,414 autosynth [DEBUG] > Running: git reset --hard HEAD
HEAD is now at 55d5379ba feat: add total_billed_time response field
2021-08-10 08:59:51,458 autosynth [DEBUG] > Running: git checkout autosynth-Google.Cloud.PubSub.V1
Switched to branch 'autosynth-Google.Cloud.PubSub.V1'
2021-08-10 08:59:51,491 autosynth [DEBUG] > Running: git diff --binary HEAD..autosynth-Google.Cloud.PubSub.V1-132 -- . :(exclude)synth.metadata
2021-08-10 08:59:51,496 autosynth [DEBUG] > Running: git diff HEAD..autosynth-Google.Cloud.PubSub.V1-132 -- synth.metadata
2021-08-10 08:59:51,501 autosynth [DEBUG] > Running: git diff --binary autosynth-Google.Cloud.PubSub.V1-132..autosynth-Google.Cloud.PubSub.V1-134 -- . :(exclude)synth.metadata
2021-08-10 08:59:51,524 autosynth [DEBUG] > Running: git checkout 9c8f71fd3529cf860d2b2a6c688ea33e6c9a9e4f
Note: switching to '9c8f71fd3529cf860d2b2a6c688ea33e6c9a9e4f'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by switching back to a branch.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -c with the switch command. Example:

  git switch -c <new-branch-name>

Or undo this operation with:

  git switch -

Turn off this advice by setting config variable advice.detachedHead to false

HEAD is now at 9c8f71fd3 Really don't run diff-pr on label changes
2021-08-10 08:59:51,555 autosynth [DEBUG] > Running: git checkout 411e51eea221af5b77f809cef2c6592df45f73d5
Previous HEAD position was 10185d07 feat: add total_billed_time response field
HEAD is now at 411e51ee feat: Expose `Locations` service to get/list avaliable locations of Dialogflow products docs: reorder some fields
2021-08-10 08:59:51,572 autosynth [DEBUG] > Running: git branch -f autosynth-Google.Cloud.PubSub.V1-133
2021-08-10 08:59:51,576 autosynth [DEBUG] > Running: git checkout autosynth-Google.Cloud.PubSub.V1-133
Switched to branch 'autosynth-Google.Cloud.PubSub.V1-133'
2021-08-10 08:59:51,607 autosynth [INFO] > Running synthtool
2021-08-10 08:59:51,607 autosynth [INFO] > ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']
2021-08-10 08:59:51,607 autosynth [DEBUG] > log_file_path: /tmpfs/src/logs/Google.Cloud.PubSub.V1/133/sponge_log.log
2021-08-10 08:59:51,610 autosynth [DEBUG] > Running: /tmpfs/src/github/synthtool/env/bin/python3 -m synthtool --metadata synth.metadata synth.py --
2021-08-10 08:59:51,847 synthtool [DEBUG] > Executing /home/kbuilder/.cache/synthtool/google-cloud-dotnet/apis/Google.Cloud.PubSub.V1/synth.py.
On branch autosynth-Google.Cloud.PubSub.V1-133
nothing to commit, working tree clean
Skipping microgenerator fetch/build: already built, and running on Kokoro
Building existing version of Google.Cloud.PubSub.V1 for compatibility checking
Generating Google.Cloud.PubSub.V1
Running mid-micro-generation script for Google.Cloud.PubSub.V1
Running post-generation script for Google.Cloud.PubSub.V1
Updated 1 path from the index
Updated 1 path from the index
git detects no change in Google.Cloud.PubSub.V1; skipping compatibility checking
Regenerating projects
API catalog contains 168 entries
Done.
2021-08-10 09:00:03,170 autosynth [INFO] > Changed files:
2021-08-10 09:00:03,171 autosynth [INFO] > M apis/Google.Cloud.PubSub.V1/synth.metadata
2021-08-10 09:00:03,171 autosynth [DEBUG] > Running: git log 411e51eea221af5b77f809cef2c6592df45f73d5 -1 --no-decorate --pretty=%s
2021-08-10 09:00:03,175 autosynth [DEBUG] > Running: git log 411e51eea221af5b77f809cef2c6592df45f73d5 -1 --no-decorate --pretty=%b%n%nSource-Author: %an <%ae>%nSource-Date: %ad
2021-08-10 09:00:03,179 autosynth [DEBUG] > Running: git add -A
2021-08-10 09:00:03,216 autosynth [DEBUG] > Running: git status --porcelain
2021-08-10 09:00:03,255 autosynth [DEBUG] > Running: git commit -m feat: Expose `Locations` service to get/list avaliable locations of Dialogflow products docs: reorder some fields

PiperOrigin-RevId: 389760020

Source-Author: Google APIs<EMAIL_ADDRESS>Source-Date: Mon Aug 9 17:11:49 2021 -0700
Source-Repo: googleapis/googleapis
Source-Sha: 411e51eea221af5b77f809cef2c6592df45f73d5
Source-Link: https://github.com/googleapis/googleapis/commit/411e51eea221af5b77f809cef2c6592df45f73d5
[autosynth-Google.Cloud.PubSub.V1-133 037312743] feat: Expose `Locations` service to get/list avaliable locations of Dialogflow products docs: reorder some fields
 1 file changed, 1 insertion(+), 1 deletion(-)
2021-08-10 09:00:03,280 autosynth [DEBUG] > Running: git reset --hard HEAD
HEAD is now at 037312743 feat: Expose `Locations` service to get/list avaliable locations of Dialogflow products docs: reorder some fields
2021-08-10 09:00:03,313 autosynth [DEBUG] > Running: git checkout autosynth-Google.Cloud.PubSub.V1
Switched to branch 'autosynth-Google.Cloud.PubSub.V1'
2021-08-10 09:00:03,342 autosynth [DEBUG] > Running: git diff --binary HEAD..autosynth-Google.Cloud.PubSub.V1-133 -- . :(exclude)synth.metadata
2021-08-10 09:00:03,347 autosynth [DEBUG] > Running: git diff HEAD..autosynth-Google.Cloud.PubSub.V1-133 -- synth.metadata
2021-08-10 09:00:03,351 autosynth [DEBUG] > Running: git diff --binary HEAD..autosynth-Google.Cloud.PubSub.V1-134 -- . :(exclude)synth.metadata
2021-08-10 09:00:03,375 autosynth [DEBUG] > Running: git diff --binary HEAD autosynth-Google.Cloud.PubSub.V1-134
2021-08-10 09:00:03,399 autosynth [DEBUG] > Running: git apply /tmpfs/tmp/tmpoystpbov/autosynth-Google.Cloud.PubSub.V1-134.patch
2021-08-10 09:00:03,409 autosynth [DEBUG] > Running: git add -A
2021-08-10 09:00:03,451 autosynth [DEBUG] > Running: git status --porcelain
2021-08-10 09:00:03,495 autosynth [DEBUG] > Running: git commit -m feat: Add topic retention options

PiperOrigin-RevId: 389879008

Source-Author: Google APIs<EMAIL_ADDRESS>Source-Date: Tue Aug 10 07:28:42 2021 -0700
Source-Repo: googleapis/googleapis
Source-Sha: 7b6a2ceed6cacf676b3918b1703b3ddd6322444c
Source-Link: https://github.com/googleapis/googleapis/commit/7b6a2ceed6cacf676b3918b1703b3ddd6322444c
[autosynth-Google.Cloud.PubSub.V1 a377067a0] feat: Add topic retention options
 8 files changed, 388 insertions(+), 238 deletions(-)
2021-08-10 09:00:03,546 autosynth [DEBUG] > Running: git log -1 --no-decorate --format=%B
2021-08-10 09:00:03,550 autosynth [DEBUG] > Running: git push --force origin autosynth-Google.Cloud.PubSub.V1
remote: fatal error in commit_refs
To https://github.com/googleapis/google-cloud-dotnet.git
 ! [remote rejected]     autosynth-Google.Cloud.PubSub.V1 -> autosynth-Google.Cloud.PubSub.V1 (failure)
error: failed to push some refs to 'https://github.com/googleapis/google-cloud-dotnet.git'
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 356, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 191, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 336, in _inner_main
    commit_count = synthesize_loop(x, multiple_prs, change_pusher, synthesizer)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 107, in synthesize_loop
    return synthesize_loop_single_pr(toolbox, change_pusher, synthesizer)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 130, in synthesize_loop_single_pr
    toolbox.push_changes(change_pusher)
  File "/tmpfs/src/github/synthtool/autosynth/synth_toolbox.py", line 290, in push_changes
    pr = change_pusher.push_changes(self.commit_count, self.branch, pr_title)
  File "/tmpfs/src/github/synthtool/autosynth/change_pusher.py", line 92, in push_changes
    git.push_changes(branch)
  File "/tmpfs/src/github/synthtool/autosynth/git.py", line 108, in push_changes
    executor.check_call(["git", "push", "--force", "origin", branch])
  File "/tmpfs/src/github/synthtool/autosynth/executor.py", line 29, in check_call
    subprocess.check_call(command, **args)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 311, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['git', 'push', '--force', 'origin', 'autosynth-Google.Cloud.PubSub.V1']' returned non-zero exit status 1.

Google internal developers can see the full log here.

Strong suspect this is just due to GitHub being flaky. Will rerun autosynth.

Autosynth passed, closing! :green_heart:


webDomain: the replace should happen only when webDo…

Added a check on webDomain: the replace should happen only when webDomain is not an IPv4 address.
Motivation and Context
I tried to host locally on IPv4 static address, without a domain name and the sessions are never written to database.

Sorry team, I have added and reverted another commit I would like to send in another PR


Asset Cache Time?

How can we help ?

Pushed new logo to repo but the cloud CDN is still serving the old logo.
Wondering how long it will take to update?
https://res.cloudinary.com/dnz2bkszg/image/fetch/https://raw.githubusercontent.com/sushiswap/assets/master/blockchains/ethereum/assets/0xB6ff96B8A8d214544Ca0dBc9B33f7AD6503eFD32/logo.png
Thanks guys <3 <3

Is it better now? Usually takes just a couple of hours.

Yes, it took a few days but it's good now! Thank you


fix: cargo audit failures

Description of change

This PR removes updates our dependencies using cargo update, this resolves one of the cargo warnings, with pertain to the yanked wasm-bindegen version 0.2.88.
The other warning is for https://rustsec.org/advisories/RUSTSEC-2023-0071.html, which is pulled in by sqlx/mysql, which we don't use, but it is pulled in due to a bug in cargo, see https://github.com/launchbadge/sqlx/issues/2911 and https://github.com/rust-lang/cargo/issues/10801. We should be safe to ignore the warning for rsa. A fix for the vulnerability is also underway, but we'd need to wait for it to be finished and pulled into sqlx. I am following the RSA PR so I will be notified when it is merged, we can then remove this ignore.
How has this been tested? (if applicable)

CI.

One quick question before approving: will the fix here RustCrypto/RSA#394 need to be followed by PR(s) in cargo, and a PR on our side, where we upgrade the rust version (including cargo), used to build the Shuttle crates that depend on sqlx? Just trying to understand the dependencies we'll need to get sorted out before removing the whitelisting of the advisory.

If a fix was released for cargo we would not rely on the rsa fix, since we would no longer depend on it via sqlx/mysql. But, I don't expect the cargo fix any time soon. The first fix we are likely to get is sqlx updating to a fixed version of rsa.


Deliver metadata with business errors?

As an SRF app developer I would like to be able to display player metadata for streams that have not started yet. As a product team we should agree whether this kind of feature is compatible with Pillarbox DNA, both technically and from a feature set point of view.
Hints
On Apple platforms errors, both technical (e.g. network issue, 404, etc.) or business (e.g. blocking reason) end up with an error devoid of any metadata even if, in the business case, we could deliver metadata as well.
The SRF app team would like to display metadata (e.g. a thumbnail) also when a business error (e.g. content availability) is involved. This is something that might already be possible on Android and / or the web, maybe something we should support, maybe not.
This could also offer an option to better address related issues like https://github.com/SRGSSR/pillarbox-apple/issues/917. If we provide an availability date with metadata we could namely not only deliver it but also implement an automatic retry mechanism. Not sure there is a team agreement on this kind of behavior so we should really discuss it together.
Acceptance criteria

The team discussed whether the feature above makes sense and is technically feasible.
Dedicated stories have been created if meaningful.
Otherwise the SRF app team has been provided with an alternative strategy.

Tasks

[ ] Discuss within the team.
[ ] Create stories or inform the SRF app team otherwise.

Nice topic for our weekly API discussion. Added to the sprint.

A PoC implementation is available on Apple platforms.

In essence delivering metadata with a business error is similar to delivering a media composition with an unplayable resource URL. So this task could be seen as a consistency improvement rather than a feature.

Current status:

Web: Already supported.
Apple: Possible with minimal effort and risk.
Android:

Poke @NicolasBrunnerSRF for information.


⚠ Bofrost.de has degraded performance

In 88504c6, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1305 ms

Resolved: Bofrost.de performance has improved in 507724d after 308 days, 7 hours, 24 minutes.


Editing Signs

As a user, I want to create, edit, and delete signs (individual stopping points in the playlist).
A sign consist of:

Plain text title (only used internally, not displayed when the sign is actually played)
HTML content

Notes

CSS can be inlined or linked.
There should be buttons to paste templates to HTML:

Inline stylesheet
Link to stylesheet
Full-page image
Full-page autoplaying video

Close as done.


Add Modern UI Theme

"Modern" Theme
This uses Roact to bring a cleaner look and feel to the most commonly used Adonis components.
Hint

Hints support a image argument in their UI Data table now. It checks to see if the provided image is a users thumbnail and will add a corner and grey background, normal images display how you would expect.
Message

Messages now support images, with similar behavior to hints with the only difference being size.

Thumbnails are also supported by the :m command.

Dynamic layout is supported.
Condensed Message
A simpler smaller version of message, used by the :n command.

This looks interesting

This looks interesting

very

this is hot asf tbh

very

HOT ASS THEME BRO! NICE ONE!

This theme certainly is appealing and refreshing in terms of visuals. But, code-wise, I don't personally think it would make much sense to introduce Roact or any external UI library/framework into the current Adonis 1.0, and just to support a single theme.
Adding 300 more files than absolutely necessary isn't a good sign, IMO. Things are going to get harder to maintain in an already-aging codebase.
I would suggest taking the Roact-constructed UIs and "converting" them over such that they are handled fully and natively by Adonis UI modules, as is the case for the other themes.

no way its merged

oh my god... WE ARE DOOMED

may day


Add a KiwiIRC.com link to the connection list.

Obviously staff are very busy right now so they haven't got around to setting up a more permanent solution for web chat so this is a temporary solution that allows people who were previously using the freenode KiwiIRC web chat to have a way to follow the channels that are moving.

Ah cool this has been sorted already in 17be9da05ada4d03dc4f8e1f4ac600a7d0f0c2a1.


[N4S] Add jest style enforce rule failures

At the moment, validation rules are simple functions that return a boolean. If the rule's return value is false, enforce will throw an Error.
Rule example:
https://github.com/ealush/vest/blob/69eacb388ad9fac8e403351df5ab5347d6298edf/packages/n4s/src/rules/greaterThan/index.js#L3-L5
And where it throws:
https://github.com/ealush/vest/blob/69eacb388ad9fac8e403351df5ab5347d6298edf/packages/n4s/src/enforce/runner/index.js#L14-L16
This means that the thrown error is always a generic one, not indicating the rule thrown, or the expected behavior of the rule.
Jest has a nicer interface for constructing matchers that also includes a custom failure message for that rule:
https://jestjs.io/docs/en/expect#expectextendmatchers
This can be very beneficial for Vest DEV_MODE that's being planned. A debug dump could log all the failed rules and their failure messages.
I would like to preserve the current behavior of Vest rules to prevent a breaking change, but also support the more verbose failure style of:
{
	message: (ruleName, enforceValue, ...args) => ``, // someErrorMessage
    pass: true/false
}

Hi, i reviewed the jest code and I will be adding a validateResultShape and a transformResultShape functions so in first place we could parse all supported formats to a final one with defaults values.
transformResultShape(true) // { pass: true, message: '[Enforce] Generic message'}
transformResultShape({ pass: true, message: 'Custom Message'}) // { pass: true, message: '[Enforce] Custom Message'}
transformResultShape({ pass: true }) // { pass: true, message: '[Enforce] Generic message' }

that way to deprecate/add a valid rule result, you only need to change those two functions and the rest of the lib could be only aware of the verbose one.
In the other hand what should transformResultShape in case that the rule returned an invalid format? pass silently? or maybe return a failing test like { pass: false, message: '[Enforce] Wrong rule result format' }
what do you think @ealush?


Support new event named "message" on Room

So we can use
room.on('message', message => console.log(message))

It works great

how to use in new version ? have example?

I believe the example has already been put in my first post?


When I run it, I encounter this exception and haven't been able to fix it. Is there any step I might have missed?

Execution failed for task ':app:processDebugMainManifest'.

com.android.manifmerger.ManifestMerger2$MergeFailureException: Error parsing D:\flutter-project\msal_auth-main\msal_auth-main\example\android\app\src\main\AndroidManifest.xml

Try:

Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.

Get more help at https://help.gradle.org

BUILD FAILED in 5s
Error: Gradle task assembleDebug failed with exit code 1
When I remove  "  from "D:\flutter-project\msal_auth-main\msal_auth-main\example\android\app\src\main\AndroidManifest.xml"
it is compile well ...
Is there any step I might have missed?
Please help me ~~~

Have you changed anything in the default project?


Content updates of base page after LinkedIn Review

divided the long list into sub lists, updated some other Areas of Interest, added CSS styling to changes

Awesome 👍


Added scripts to run a backup between tiled servers running different versions

This PR adds script that allows running a backup from our instance of aimmdb in https://aimm.lbl.gov/api to https://tiled-demo.blueskyproject.io.
The first instance was running in a much older version of tiled and it was not compatible to try to connect to both instances using one environment with the same tiled client. the solution includes two steps: 1) downloading all the data to the local machine as json files and 2) reading the json files and uploading the data to the new site.

Sorry, I missed this months ago. Is it still valid?


Shellcheck and fix 3 build scripts

Following shellcheck's best practices.

good job, btw, maybe you can merges your commits into one commit which will looks better. Here is the reference: http://jartto.wang/2018/12/11/git-rebase/

Any question with the command: git rebase?


Typescript error: Variable declaration expected

After the release of 1.42.0 I'm getting this typescript error
node_modules/sort-package-json/index.d.ts:14:7 - error TS1134: Variable declaration expected.

14   var default: typeof sortPackageJsonCore;
         ~~~~~~~

node_modules/sort-package-json/index.d.ts:14:14 - error TS1134: Variable declaration expected.

14   var default: typeof sortPackageJsonCore;
                ~

node_modules/sort-package-json/index.d.ts:14:16 - error TS1134: Variable declaration expected.

14   var default: typeof sortPackageJsonCore;
                  ~~~~~~

Found 3 errors.

/cc @bluelovers

would this one be fixed by #173 ?

This was fixed by #189


Routing doesn't work if there are any query parameters or even "?" character in the URL

http://mywebsite.com/somepage - Works
http://mywebsite.com/somepage? - Doesn't work
http://mywebsite.com/somepage?param1=val1  - Doesn't work
Update:
It seems that adding the following fix for App Engine causes this problem on both local and App Engine environments.
// Google App Engine doesn't set $_SERVER['PATH_INFO']
$app->environment['PATH_INFO'] = $_SERVER['REQUEST_URI'];
Update:
Found a way by removing the query string part like this. Solved my problem:
$app->environment['PATH_INFO'] = rtrim(strtok($_SERVER['REQUEST_URI'], '?'), '/');

Which branch does this affect?

Latest version using composer:
"slim/slim": "2.*"

$_SERVER["PATH_INFO"] variable doesn't includes the query string part of URL, while $_SERVER["REQUEST_URI"] does. Actually Slim doesn't use $_SERVER["PATH_INFO"] to compute $app->environment["PATH_INFO"] (and I think it never used this). The awkward variable can be $_SERVER["REQUEST_URI"].


XCTestCase.fulfillment(…) missing on Linux #436

This change implements fulfillment(of:) as found in Xcode's version of XCTest. The implementation, while (and I'm using a technical term here) ridiculous, is equivalent to the Xcode 14.3 implementation.
Resolves #436.

@swift-ci please test

@swift-ci please test

@swift-ci please test Windows

@swift-ci please clean test Windows

@swift-ci please test

One more minor nit: this is not Linux only - it impacts Windows as well. I'd prefer "non-Darwin platforms" over "Linux".

You're right of course—I just stole the title from the reported issue. :)

@swift-ci please test

@swift-ci please clean test Windows


WIP: Monster Shrine & Material Storage update

Reworked Material Storage & added Monster Shrine Storage
resolves #178

Everything should be done.
Some things to do after merging it to master:

Parse new game data and replace Monster Shrine image (I just used placeholder from my phone's screenshot); sadly I can't get new game data with images right now
Check Material Storage images and - if needed - replace names (I've seen different values in DB & Fixtures)

I forgot about Fusion system. WIP.

Fusion system adjusted to newest Models.

I pushed a few small changes based on my testing/preferences. The only remaining issue is that this wipes out a user's existing storage when the migration executes. Many users do not regularly import or use SWEX so this would be a hassle for them. The migration should update the new models with the data from the old model.
I believe the best way to execute this is to split the migration into 3 unique stages:

Create new storage models
Data migration
Delete old storage migration

The data migration should be able to pick up where it left off in case it fails to complete in one pass. That probably means some way of filtering a queryset down to only storages that still need to be migrated.


String guts micro optimizations

A few micro optimizations to _unmangedXViews and string comparison

Not sure why the test case fixes are part of this PR. I thought I had already pushed them 😅


The publish_date member should be a datetime object

The article.publish_date member should be a datetime object. There are several libraries that parse out dates from strings. I've used python-dateutil in the past.

I personally dislike breaking current code; would adding a new property that is converted to a python datetime be appropriate? I too have used python-dateutil and think that would be a good option here.


Documentation suggests installing hidden globals

From documentation:
// Set the on the global on the window so that you don't have to import
// the base classes in every model and collection class or component.
window.Model = Model;
window.Collection = Collection;

This is really bad practice. It leads to maintainable code, and all kinds of conflicts. No-one should ever do that, and documentation should certainly not recommend it.
Importing these symbols is a single line, which has two purposes:

explain to babel where to find the symbol,
explain to the reader of the code what library is being used here.

Purpose no1 can be circumvented by using a global import, but purpose no2 is still really relevant, and should not be left out.

Quoting from #6

The reason we went for globals here was to make it as easy as possible for us to migrate to this version of the library (rather than our own internal one). It's a flaw in our setup because we have a structure like this:

lib.js (package dependencies, should not change often)
app.js (application bootstrapping)
module1.js (page-specific module)
module2.js

If we imported Model or Collection in both bundles module1.js and module2.js, we'll end up with two instances of the same dependency, because the two modules are not aware of each other.

Even if we created globals for ourselves in app.js, we'll be embedding lodash and moment in our app.js, which should ideally only be in lib.js.

I agree with you though - we should never rely on a global peer dependency, everything should be imported where required and it's up to the client to bundle them efficiently.

IDE support is also a hassle when you're assuming globals.

This is now a work in progress on the 0.2 branch.