Crash with SIGSEGV on Android

What were you trying to do?
I wanted to run a camera with a frame processor in V3.
Reproduceable Code

I have not yet been able to solve the reproduction step. To initiate a collaborative effort in finding the solution, I am sharing this issue.

Nevertheless, I have come across a few small hints. Firstly, it seems that the frame processor may be relevant. The crash occurs only when I attach a frame processor to the camera. Additionally, the stack trace includes the presence of 'librnworklets.so'.

Furthermore, I believe that updating the frameProcessor prop could be a factor. When I did not update it, the crash did not occur. In V2, updating the frameProcessor prop, typically caused by modifying values in deps within useFrameProcessor, easily led to app crashes on both Android and iOS. Upon upgrading to V3, I discovered that the issue was resolved, particularly on iOS. However, there are still occasional crashes on Android, although not as frequently as in V2.

What happened instead?
Run without a crash.
Relevant log output
Crashed: Thread: SIGSEGV  0x0000000000000008
#00 pc 0x9a070 libhermes.so (BuildId: e5310494e026103da5c6017c6f68a9c1fa7262fa)
#01 pc 0xa6300 libhermes.so (BuildId: e5310494e026103da5c6017c6f68a9c1fa7262fa)
#02 pc 0xa6300 libhermes.so (BuildId: e5310494e026103da5c6017c6f68a9c1fa7262fa)
#03 pc 0xa48ec libhermes.so (BuildId: e5310494e026103da5c6017c6f68a9c1fa7262fa)
#04 pc 0x87354 libhermes.so (BuildId: e5310494e026103da5c6017c6f68a9c1fa7262fa)
#05 pc 0x74ce4 libhermes.so (BuildId: e5310494e026103da5c6017c6f68a9c1fa7262fa)
#06 pc 0x5c7e8 libVisionCamera.so (BuildId: 9533f7f5b29e61ccec0b52b16d140796235a2072)
#07 pc 0x5c070 libVisionCamera.so (BuildId: 9533f7f5b29e61ccec0b52b16d140796235a2072)
#08 pc 0x1a19bc librnworklets.so (BuildId: 643768d061c79a4d4850ee762daa4c642174e953)
#09 pc 0x1a1954 librnworklets.so (BuildId: 643768d061c79a4d4850ee762daa4c642174e953)
#10 pc 0x1a18a0 librnworklets.so (BuildId: 643768d061c79a4d4850ee762daa4c642174e953)
#11 pc 0x1a1818 librnworklets.so (BuildId: 643768d061c79a4d4850ee762daa4c642174e953)
#12 pc 0x1a06c4 librnworklets.so (BuildId: 643768d061c79a4d4850ee762daa4c642174e953)
#13 pc 0x7c7dc libhermes.so (BuildId: e5310494e026103da5c6017c6f68a9c1fa7262fa)
#14 pc 0x87060 libhermes.so (BuildId: e5310494e026103da5c6017c6f68a9c1fa7262fa)
#15 pc 0xa51a8 libhermes.so (BuildId: e5310494e026103da5c6017c6f68a9c1fa7262fa)
#16 pc 0xa48ec libhermes.so (BuildId: e5310494e026103da5c6017c6f68a9c1fa7262fa)
#17 pc 0x87354 libhermes.so (BuildId: e5310494e026103da5c6017c6f68a9c1fa7262fa)
#18 pc 0x74ce4 libhermes.so (BuildId: e5310494e026103da5c6017c6f68a9c1fa7262fa)
#19 pc 0x5c7e8 libVisionCamera.so (BuildId: 9533f7f5b29e61ccec0b52b16d140796235a2072)
#20 pc 0x5c070 libVisionCamera.so (BuildId: 9533f7f5b29e61ccec0b52b16d140796235a2072)
#21 pc 0x5bd34 libVisionCamera.so (BuildId: 9533f7f5b29e61ccec0b52b16d140796235a2072)
#22 pc 0x5e818 libVisionCamera.so (BuildId: 9533f7f5b29e61ccec0b52b16d140796235a2072)
#23 pc 0x5f1b8 libVisionCamera.so (BuildId: 9533f7f5b29e61ccec0b52b16d140796235a2072)
#24 pc 0x5f26c libVisionCamera.so (BuildId: 9533f7f5b29e61ccec0b52b16d140796235a2072)
#25 pc 0x5f128 libVisionCamera.so (BuildId: 9533f7f5b29e61ccec0b52b16d140796235a2072)
#26 pc 0x5e7b8 libVisionCamera.so (BuildId: 9533f7f5b29e61ccec0b52b16d140796235a2072)
#27 pc 0x222244 libart.so (BuildId: 1724d2edb620afb8c3e8c5ea6c61ac19)
#28 pc 0x29c628 libart.so (BuildId: 1724d2edb620afb8c3e8c5ea6c61ac19)
#29 pc 0x218be8 libart.so (BuildId: 1724d2edb620afb8c3e8c5ea6c61ac19)
#30 pc 0x28520c libart.so (BuildId: 1724d2edb620afb8c3e8c5ea6c61ac19)
#31 pc 0x764cdc libart.so (BuildId: 1724d2edb620afb8c3e8c5ea6c61ac19)
#32 pc 0x3e70f0 libart.so (BuildId: 1724d2edb620afb8c3e8c5ea6c61ac19)
#33 pc 0x3e1cec libart.so (BuildId: 1724d2edb620afb8c3e8c5ea6c61ac19)
#34 pc 0x762dd4 libart.so (BuildId: 1724d2edb620afb8c3e8c5ea6c61ac19)
#35 pc 0x29cb50 libart.so (BuildId: 1724d2edb620afb8c3e8c5ea6c61ac19)
#36 pc 0x203994 libart.so (BuildId: 1724d2edb620afb8c3e8c5ea6c61ac19)
#37 pc 0x2000fc libart.so (BuildId: 1724d2edb620afb8c3e8c5ea6c61ac19)
#38 pc 0x2270ec libart.so (BuildId: 1724d2edb620afb8c3e8c5ea6c61ac19)
#39 pc 0x763268 libart.so (BuildId: 1724d2edb620afb8c3e8c5ea6c61ac19)
#40 pc 0x775bf4 libart.so (BuildId: 1724d2edb620afb8c3e8c5ea6c61ac19)
#41 pc 0x203994 libart.so (BuildId: 1724d2edb620afb8c3e8c5ea6c61ac19)
#42 pc 0xa16ffc libart.so (BuildId: 1724d2edb620afb8c3e8c5ea6c61ac19)
#43 pc 0x2000fc libart.so (BuildId: 1724d2edb620afb8c3e8c5ea6c61ac19)
#44 pc 0xa16ffc libart.so (BuildId: 1724d2edb620afb8c3e8c5ea6c61ac19)
#45 pc 0x3d98e0 libart.so (BuildId: 1724d2edb620afb8c3e8c5ea6c61ac19)
#46 pc 0x2947b4 libart.so (BuildId: 1724d2edb620afb8c3e8c5ea6c61ac19)
#47 pc 0xa16ffc libart.so (BuildId: 1724d2edb620afb8c3e8c5ea6c61ac19)
#48 pc 0x3e1254 libart.so (BuildId: 1724d2edb620afb8c3e8c5ea6c61ac19)
#49 pc 0xa16ffc libart.so (BuildId: 1724d2edb620afb8c3e8c5ea6c61ac19)
#50 pc 0xa16ffc libart.so (BuildId: 1724d2edb620afb8c3e8c5ea6c61ac19)
#51 pc 0x3e1cc8 libart.so (BuildId: 1724d2edb620afb8c3e8c5ea6c61ac19)
#52 pc 0x202e94 libart.so (BuildId: 1724d2edb620afb8c3e8c5ea6c61ac19)
#53 pc 0x75dfe0 libart.so (BuildId: 1724d2edb620afb8c3e8c5ea6c61ac19)
#54 pc 0xa16ffc libart.so (BuildId: 1724d2edb620afb8c3e8c5ea6c61ac19)
#55 pc 0x203a14 libart.so (BuildId: 1724d2edb620afb8c3e8c5ea6c61ac19)
#56 pc 0x2000fc libart.so (BuildId: 1724d2edb620afb8c3e8c5ea6c61ac19)
#57 pc 0x2270ec libart.so (BuildId: 1724d2edb620afb8c3e8c5ea6c61ac19)
#58 pc 0x763268 libart.so (BuildId: 1724d2edb620afb8c3e8c5ea6c61ac19)
#59 pc 0x775bf4 libart.so (BuildId: 1724d2edb620afb8c3e8c5ea6c61ac19)
#60 pc 0x203994 libart.so (BuildId: 1724d2edb620afb8c3e8c5ea6c61ac19)
#61 pc 0xa16ffc libart.so (BuildId: 1724d2edb620afb8c3e8c5ea6c61ac19)
#62 pc 0x2000fc libart.so (BuildId: 1724d2edb620afb8c3e8c5ea6c61ac19)
#63 pc 0xa16ffc libart.so (BuildId: 1724d2edb620afb8c3e8c5ea6c61ac19)

Device
Galaxy S10
VisionCamera Version
3.0.0-rc.2
Additional information

[X] I am using Expo
[X] I have read the Troubleshooting Guide
[X] I agree to follow this project's Code of Conduct
[X] I searched for similar issues in this repository and found none.

Can you share the entire logs from adb logcat?

@mrousavy I think it'll take some time to reproduce the bugs since made a huge migration and the old environment is lost. I'll test it once I fix the Android build with the latest RNVC V3!

Cool yea I'm still in the middle of rewriting everything haha

Hey! I've rewritten the entire Android codebase of VisionCamera from CameraX to Camera2 in the efforts of ✨ VisionCamera V3.
I just now completed the Camera2 rewrite and I believe the core structure is running, but there might be some edge cases to iron out. Can you try and test the PR #1674 for me to see if you can still reproduce this issue here?
Here's an instruction on how you can test that: https://github.com/mrousavy/react-native-vision-camera/pull/1674#issuecomment-1684104217
If the issue cannot be reproduced with that version/PR anymore, then hoorayy, I fixed it! 🎉
Otherwise please let me know and I'll keep this issue open to keep track of it.
Thank you!

@mrousavy  First, Thank you for your effort!
Brief report: I previously attempted to replicate this problem using a new project. My initial suspicion was that the crash resulted from updates to the 'frameProcessor' prop. Surprisingly, the small test app worked perfectly, suggesting that the issue might stem from domain-specific logic within my primary project.
The problem is that the Android build of my main project has been left broken for a period. Furthermore, the latest version of RNVC V3 was ok with a fresh RN project, hinting that the build failure may be linked to specific intricacies of my main project. Now I am trying to resolve the build problem from this point forward, but I cannot guarantee it to be done soon.
I'll share the build problem in a new issue for further assistance.

I need to fix #1681 first. I've observed that the issue is not found in a new project + RNVC V3 installed.

Exciting! V3 will close this then :) Thanks for testing!

the same  issue , v 3.6.4
Sometimes the application crashes with this issue. On average, there is one crash per five scans.
Crashed: Thread: SIGSEGV  0x0000007cc639d7e1
#00 pc 0x128bac libbarhopper_v3.so (BuildId: 73597d2de25bd3c29361db3c56dd9f18)
#01 pc 0x812f4 libbarhopper_v3.so (BuildId: 73597d2de25bd3c29361db3c56dd9f18)
#02 pc 0xa2600 libtflite_gmscore_jni.so (BuildId: abf371b4405232f9c7109f40a7426a23)
#03 pc 0xa17e4 libtflite_gmscore_jni.so (BuildId: abf371b4405232f9c7109f40a7426a23)
#04 pc 0x116474 libbarhopper_v3.so (BuildId: 73597d2de25bd3c29361db3c56dd9f18)
#05 pc 0x116484 libbarhopper_v3.so (BuildId: 73597d2de25bd3c29361db3c56dd9f18)
#06 pc 0x11601c libbarhopper_v3.so (BuildId: 73597d2de25bd3c29361db3c56dd9f18)
#07 pc 0x112160 libbarhopper_v3.so (BuildId: 73597d2de25bd3c29361db3c56dd9f18)
#08 pc 0x1124a0 libbarhopper_v3.so (BuildId: 73597d2de25bd3c29361db3c56dd9f18)
#09 pc 0x82b98 libbarhopper_v3.so (BuildId: 73597d2de25bd3c29361db3c56dd9f18)
#10 pc 0x7aee4 libbarhopper_v3.so (BuildId: 73597d2de25bd3c29361db3c56dd9f18)
#11 pc 0x83360 libbarhopper_v3.so (BuildId: 73597d2de25bd3c29361db3c56dd9f18)
#12 pc 0x213a5 libbarhopper_v3.so (BuildId: 73597d2de25bd3c29361db3c56dd9f18)
#13 pc 0x7ac2c libbarhopper_v3.so (BuildId: 73597d2de25bd3c29361db3c56dd9f18)
#14 pc 0x7ac38 libbarhopper_v3.so (BuildId: 73597d2de25bd3c29361db3c56dd9f18)

Hi! The issue seems to be still present in latest v3.9.1. Reproduced on Redmi Note 11 Pro 5G (also this devices suffers "black screen" #2363, setting exposure=0 works). The app crashes after scanning a barcode and navigating to another screen and returning back to scanner screen and continue scanning barcodes. After 4-5 times doing this, the app crashes. Attached device.json with info of de camera device used and adb_logcat.txt with crash traces (crash occurs at 11:13:24.238. Thanks!
device.json
adb_logcat.txt

Hi! The issue seems to be still present in latest v3.9.1. Reproduced on Redmi Note 11 Pro 5G (also this devices suffers "black screen" #2363, setting exposure=0 works). The app crashes after scanning a barcode and navigating to another screen and returning back to scanner screen and continue scanning barcodes. After 4-5 times doing this, the app crashes. Attached device.json with info of de camera device used and adb_logcat.txt with crash traces (crash occurs at 11:13:24.238. Thanks!
device.json adb_logcat.txt

Same here, I'm on 3.9.1 and I still experience this crash in different devices randomly after a few scans, I have the same stack trace

Same here, experiencing this crash with v3.9.0


Update pgdg packages for 9.4, 9.3

Getting some errors like
STDERR: package pgdg-centos94-9.4-2.noarch (which is newer than pgdg-centos94-9.4-1.noarch) is already installed
... so we should bump the default version to the current one

@CloCkWeRX Thanks for the update.

So this is the second pr I've done with packages updating,  I wonder if it's worth trying to script this a bit - working by hand is a real pain.

It is indeed a pain. I tried to make it at least a better data structure in 4.x and removed some of the much older platform versions. However, with all of the different RHEL platforms and Postgresql versions to support.. it's not fantastic.


[SPARK-33822][SQL] Use the CastSupport.cast method in HashJoin

What changes were proposed in this pull request?

This PR intends to fix the bug that throws a unsupported exception when running the TPCDS q5 with AQE enabled (this option is enabled by default now via SPARK-33679):
java.lang.UnsupportedOperationException: BroadcastExchange does not support the execute() code path.
  at org.apache.spark.sql.execution.exchange.BroadcastExchangeExec.doExecute(BroadcastExchangeExec.scala:189)
  at org.apache.spark.sql.execution.SparkPlan.$anonfun$execute$1(SparkPlan.scala:180)
  at org.apache.spark.sql.execution.SparkPlan.$anonfun$executeQuery$1(SparkPlan.scala:218)
  at org.apache.spark.rdd.RDDOperationScope$.withScope(RDDOperationScope.scala:151)
  at org.apache.spark.sql.execution.SparkPlan.executeQuery(SparkPlan.scala:215)
  at org.apache.spark.sql.execution.SparkPlan.execute(SparkPlan.scala:176)
  at org.apache.spark.sql.execution.exchange.ReusedExchangeExec.doExecute(Exchange.scala:60)
  at org.apache.spark.sql.execution.SparkPlan.$anonfun$execute$1(SparkPlan.scala:180)
  at org.apache.spark.sql.execution.SparkPlan.$anonfun$executeQuery$1(SparkPlan.scala:218)
  at org.apache.spark.rdd.RDDOperationScope$.withScope(RDDOperationScope.scala:151)
  at org.apache.spark.sql.execution.SparkPlan.executeQuery(SparkPlan.scala:215)
  at org.apache.spark.sql.execution.SparkPlan.execute(SparkPlan.scala:176)
  at org.apache.spark.sql.execution.adaptive.QueryStageExec.doExecute(QueryStageExec.scala:115)
  at org.apache.spark.sql.execution.SparkPlan.$anonfun$execute$1(SparkPlan.scala:180)
  at org.apache.spark.sql.execution.SparkPlan.$anonfun$executeQuery$1(SparkPlan.scala:218)
  at org.apache.spark.rdd.RDDOperationScope$.withScope(RDDOperationScope.scala:151)
  at org.apache.spark.sql.execution.SparkPlan.executeQuery(SparkPlan.scala:215)
  at org.apache.spark.sql.execution.SparkPlan.execute(SparkPlan.scala:176)
  at org.apache.spark.sql.execution.SparkPlan.getByteArrayRdd(SparkPlan.scala:321)
  at org.apache.spark.sql.execution.SparkPlan.executeCollectIterator(SparkPlan.scala:397)
  at org.apache.spark.sql.execution.exchange.BroadcastExchangeExec.$anonfun$relationFuture$1(BroadcastExchangeExec.scala:118)
  at org.apache.spark.sql.execution.SQLExecution$.$anonfun$withThreadLocalCaptured$1(SQLExecution.scala:185)
  at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
  ...

I've checked the AQE code and I found EnsureRequirements wrongly puts BroadcastExchange on a top of BroadcastQueryStage in the reOptimize phase as follows:
+- BroadcastExchange HashedRelationBroadcastMode(List(cast(input[0, int, true] as bigint)),false), [id=#2183]
  +- BroadcastQueryStage 2
    +- ReusedExchange [d_date_sk#1086], BroadcastExchange HashedRelationBroadcastMode(List(cast(input[0, int, true] as bigint)),false), [id=#1963]

A root cause is that a Cast class in a required child's distribution does not have a timeZoneId field (timeZoneId=None), and a Cast class in child.outputPartitioning has it. So, this difference can make the distribution requirement check fail in EnsureRequirements:
https://github.com/apache/spark/blob/1e85707738a830d33598ca267a6740b3f06b1861/sql/core/src/main/scala/org/apache/spark/sql/execution/exchange/EnsureRequirements.scala#L47-L50
The Cast class that does not have a timeZoneId field is generated in the HashJoin object. To fix this issue, this PR proposes to use the CastSupport.cast method there.
Why are the changes needed?

Bugfix.
Does this PR introduce any user-facing change?

No.
How was this patch tested?

Manually checked that q5 passed.

To add unit tests, I'm looking for a simpler query to reproduce this. But, I've not found it yet.

cc: @dongjoon-hyun @cloud-fan @HyukjinKwon

Test build #132937 has started for PR 30818 at commit 7e33df3.

BTW, @maropu . Why do you make another JIRA for this? Also, the new JIRA seems to be an Improvement?

Yeah let's port it back.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/37540/

Thanks, I merged two issues by copying all description into one JIRA (SPARK-33822 Bug).

BTW, @maropu . Why do you make another JIRA for this? Also, the new JIRA seems to be an Improvement? Do we need more patch to handle Q5?

Yea, it's just my mistake...

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/37540/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/37540/

Test build #132937 has finished for PR 30818 at commit 7e33df3.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

retest this please

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/132937/

Test build #132943 has started for PR 30818 at commit 7e33df3.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/37546/

Test build #132943 has finished for PR 30818 at commit 7e33df3.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/132943/

Could you fix the test suite, @maropu ?

The following is failing due to the session timezone.
    assert(HashJoin.rewriteKeyExpr(i :: Nil) === Cast(i, LongType) :: Nil)

Sure, @dongjoon-hyun

Thank you, @maropu and all. The last commit is only about the two test suites and I verified them locally.
Merged to master/3.1/3.0.

Thanks for the quick response, @dongjoon-hyun !

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/132971/

Ur, I forgot that SQLConfHelper doesn't exist in branch-3.0. Could you make a backport PR to branch-3.0, please? @maropu ?

okay, I will do it now.

Thank you! @maropu

Could you please tell if this was fixed in 3.2 as well? The ticket lists 3.0.0, 3.0.1, 3.1.0, 3.2.0 as the affected versions and 3.0.2, 3.1.0 as fix versions. I believe we're having this issue in 3.2.1.

It's fixed in 3.1.0 and forward, including 3.2.0. You may hit a different bug, please open a new JIRA ticket, thanks for reporting!


Player Kick on Connections

What is the output link of /viaversion dump?
https://dump.viaversion.com/b49a423def8530cee2468658096d5a48ee70d6c8840d88596fae7f6e54641a9d
Are you using any additional software like BungeeCord? If so, what software and version? (Please list your plugins as well)
WaterFall
How does this error happen? login? Using an item?
Login multiple user at the same time "aparently"
Is there an error in the console? Use pastebin.com. Is there a kick message?
https://pastebin.com/QxjdxKsQ

Also was tested with ViaVersion 1.5.3 1.5.2 same issue.

update: tested with bungeecord same issue.

Can you test with no other plugins?

Tested and yes apparently it's one of my plugins. I'm sorry.


Adapt timeouts of controller and nginx.

Lower the timeouts of the controller to match the proxy_read_timeout in nginx.
If the nginx proxy_read_timeout is higher than the controller timeout, this can result in issues with long requests.

@cbickel
Have you got a wrong statement:
If the nginx proxy_read_timeout is higher than the controller timeout, this can result in issues with long requests.

I think it should be:
If the nginx proxy_read_timeout is lower than the controller timeout, this can result in issues with long requests.

Based on your change,  proxy_read_timeout becomes 75s, and idle-timeout becomes 70s, lower than 75s.

PG2#2383 🔵


Backups on Windows are failing due to boltdb issue

From community slack:
I am unable to backup data:
PS C:\Temp\influxbackup> influx backup .
2021/12/21 09:52:07 INFO: Downloading legacy KV snapshot
2021/12/21 09:52:07 INFO: Extracting bucket manifest from legacy KV snapshot
Error: failed to backup metadata: failed to extract bucket metadata from downloaded KV snapshot: unable to open boltdb:
CreateFileMapping: Not enough memory resources are available to process this command.
No differences specifying organization, bucket and token. Influx CLI is configured correctly as other commands work fine.

See also underlying boltdb issue: https://github.com/etcd-io/bbolt/issues/252
And https://github.com/influxdata/influx-cli/pull/183#issuecomment-876680455
Looks like we skipped a test on Windows and now its biting us. No movement on the upstream issue since Nov 2020 so we're going to have to find a workaround or fix the upstream I think.

@dgnorton for prioritization

Per Franco, this is happening on the latest docker image.

This should only be happening if the CLI needs to build a manifest from a pre-2.1 influxd server on a windows machine. There was a backup API change between 2.0.x and 2.1 that requires building this legacy manifest.
Running CLI v2.2.1 with InfluxDB v2.1.1 on Windows 10 to do a backup works for me - doesn't need to create a legacy manifest like the log 2021/12/21 09:52:07 INFO: Extracting bucket manifest from legacy KV snapshot indicates.
For backing up a 2.0.x influxd server, the CLI client bundled with the server release should still work on windows. These were built from the "old" CLI source code in the influxdb repository.
The old CLI code didn't need to build a legacy manifest, but it did need to open the bolt file, as in: https://github.com/influxdata/influxdb/blob/d1233b7951ddf06a3f201c84f4b0915692c22ba5/backup/backup.go#L67
I believe the reason the old CLI code can do this on Windows is because it used the same logic to open the bolt file as the influxd server, which does not use the ReadOnly option for normal use: https://github.com/influxdata/influxdb/blob/d1233b7951ddf06a3f201c84f4b0915692c22ba5/bolt/kv.go#L94-L100
A simple fix for this error when backing up a legacy server on Windows therefor might be to not use the ReadOnly option here: https://github.com/influxdata/influx-cli/blob/7af0b2ae73b7f3dec819ce6fed546c6daec73f8f/internal/backup_restore/bolt.go#L47
I asked Franco in the community slack to confirm the version of influxd that is being run, since if it is actually v2.1.1 and the CLI is trying to create a legacy manifest that would be a different problem - and one that I could not reproduce.


route53 zone region required for global resource ?

What happened?
any reason why region is required in official-provider-aws ? in my point of view route53 zone is global resource
https://marketplace.upbound.io/providers/upbound/provider-aws-route53/v0.36.0/resources/route53.aws.upbound.io/Zone/v1beta1#doc:spec-forProvider-region
in community provider-aws we have no region field available
<EMAIL_ADDRESS>
How can we reproduce it?

What environment did it happen in?

Crossplane Version:
Provider Version:
Kubernetes Version:
Kubernetes Distribution:

Hi @haarchri !
The route53 zone is global resource, so we may consider removing the region field or converting the optional one but, this will be a breaking api change.
So if current api does not affect the behaviour of this resource we can protect the current state.
The issue will be triaged and need more investigation to decide what actions we should to do in this situation.


Improve Python3 compatibility

e.message breaks in Python3. But simply assigning the error itself to the message works in Python2 and Python3.
Manually tested with a 404 error, plus ran unit tests in Python2 and all pass.

Source repo was unavailable, but will make this update manually 👌


[Question] How can I trigger the example if my project dont have tag or release?

Hello, sorry about my question, but i am learing about github actions...
I am trying to run, using git push,  the example below, but dont trigger... My project dont have tag or release yet, this action don`t create a new tag and release?
The example:

name: 'CI'
on:
push:
tags:
- '*'
jobs:
release:
if: startsWith(github.ref, 'refs/tags/')
runs-on: ubuntu-latest
steps:
- name: Build Changelog
id: github_release
uses: mikepenz/release-changelog-builder-action@v3
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
- name: Create Release
uses<EMAIL_ADDRESS>#softprops/action-gh-release
with:
body: ${{steps.github_release.outputs.changelog}}

Thanks

@julioNico this action does not create the tag or release no. it's sole purpose is to provide functionality to create the release notes.
If you don't have tags, you can also change the trigger, please be aware that if you don't trigger it via a tag, that the action will need additional information on the toTag you expect to create the release notes for

Ok, I got it! thank you so much, @mikepenz.


CSE: fix checking convention of tuple apply results

We didn't catch the case where a function returns a tuple where at least one of the tuple elements is returned as owned. In such a case the apply must not be cse'd.
Fixes a miscompile which results in an over-release.
rdar://121597250

@swift-ci test


Update cats-effect, cats-effect-laws to 3.4.3

Updates

org.typelevel:cats-effect
org.typelevel:cats-effect-laws

from 3.2.9 to 3.4.3.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Applied Scalafix Migrations

org.typelevel:{cats-effect,cats-effect-laws}:3.3.0 (created no change)

github:typelevel/cats-effect/v3_3_0?sha=series/3.x

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.typelevel" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "@monthly" },
  dependency = { groupId = "org.typelevel" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, scalafix-migrations, commit-count:1

Superseded by #643.


update notation in mccall_with_separation.rst

updates to use e and h for value functions, \phi for distribution, etc.
Replaced literal-include with code

Closing for now - will add in some of these notation changes later


ci: removed sonar project properties file to automatically use sonar support.

https://github.com/jhipster/generator-jhipster/issues/19467#issuecomment-1528772294

Automatically run result in the 1st time:

This PR should be replaced by this one: https://github.com/jhipster/jhipster-lite/pull/372/files
Both can be tested in parallele:

custom sonar analysis
sonarcloud

So with this, we'll see if the new Sonarcloud works or is still broken

Continue to https://github.com/jhipster/jhipster-lite/pull/6134


SWARM-1954: MP JWT - allow to skip unconstrained resource method.

Motivation
If there is no class-level security annotation an unconstrained resource
method has always an implicit DenyAll. We would like to have this
configurable.
Modifications
Add
swarm.microprofile.jwt.default-missing-method-permissions-deny-access
config property (true by default). If set to false then if there are no
class-level security annotations an unconstrained resource method is
ignored, i.e. no security containts are implied.
Result
It is now possible to configure the default behavior.

test this please


how to download the FCOS

@vrutkovs hi, i notice here: https://github.com/openshift/okd/releases, about the machine-os version
Component Versions:
kubernetes 1.17.1
machine-os 31.20200521.20 Fedora CoreOS
this version: 31.20200521.20 Fedora CoreOS, how can i download this version
i search on https://getfedora.org/coreos?stream=stable, did not find it.

This is FCOS version from testing-devel stream. You should not be downloading it - start with the image suggested by installer (i.e. any image from stable stream) and after the pivot your machines would be updated automatically


Updating App Service recommendation to highlight refresh delays

And propose another alternative to the users that is not only deleting the entire App Service Plan: utilize it.

@ikhapova
IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@sign-off

@ikhapova,
I committed your suggestion. Go ahead and #sign-off if this PR is ready for merge. Thanks!

#sign-off

#Sign-off


[WIP DO NOT MERGE] update to work with Python 3.10.

@kenjitoyama I just updated the PR and have tested this to compile for Python 3.10. This should be good enough for a start.
The main issues around updating the dependencies should be sorted, but there are some things which are just quite hard to do it with hacks on my side. Specifically, I am not entirely sure what's the approach to work with python packaging on top of bazel right now, so the PR currently has some code that is a bit coupled with py310. Let me unpack. I added some comments to the diff so perhaps you can help me take a look?

I got rid of all requirements as it was easier to first install these into the build environment in OSS. This is what launchpad and reverb do as well. I am not sure how much the BUILD.bazel shares with blaze (I guess not much) but this might be something you would like to fix internally. In launchpad and reverb I think there is some build_def.bzl sharing with blaze.
The cross_language_test fails when running with bazel test because for some reason the way it passed the runfile environment variables removes PATH information from the subprocess call which causes the py_writer to resolve to the python under /usr/bin/python. When running outside the container, this causes the tests to fail.
I think the code mostly works so we can start thinking about cleaning it up?

Hi @ethanluoyc , sorry for the delay I was OOO.
What's the current state now? Does this build the 3.10 wheels successfully?
Thanks,
Daniel

Hi @ethanluoyc , sorry for the delay I was OOO.
What's the current state now? Does this build the 3.10 wheels successfully?
Thanks,
Daniel

Hi!
Yes, it should work.

This work has been absorbed into https://github.com/deepmind/envlogger/commit/1c0d8f29c114128e75573ea7a605eeb0548ca29b.


libtensorflow_2: add TensorFlow 2 as a library

Motivation for this change
libtensorflow is currently TensorFlow 1. Tensorflow 2 is available as a Python library, but not as a C library. I went with the naming convention of the Python TensorFlow 2.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[X] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[X] Ensured that relevant documentation is up to date
[X] Fits CONTRIBUTING.md.

It's the same way in bin.nix. I'd be happy to fix it, but I suggest doing that in a separate commit, and then for both bin.nix and bin_2.nix in the same way.
@SuperSandro2000 Thanks for looking at this!

Result of nixpkgs-review pr 103292 run on x86_64-darwin 1

1 package built:

libtensorflow_2 (libtensorflow-bin_2)

@SuperSandro2000 Sorry for the long delay - for some reason, I did not see the check failure. Fixed it now. Anything I can do to move it along?

@SuperSandro2000 Sorry for the long delay - for some reason, I did not see the check failure. Fixed it now. Anything I can do to move it along?

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

1 package built:

libtensorflow-bin

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

1 package built:

libtensorflow-bin

@Mic92 Thanks!

@Mic92 Thanks!


[#104] Fix dependencies for multi-component build (master)

CI tests running

CI passed (had one SSH failure, retried, succeeded)
Please add #


time only support for watson add

Improve usability of watson add (issue #278)

Looks like we finally have our first CLI tests :wink:

Do you know why Github is displaying such a long diff for  docs/user-guide/commands.md? Did you by any chance generate it on Windows? If so, I think there is a way to avoid committing the \r\n: https://help.github.com/en/articles/dealing-with-line-endings

Do you know why Github is displaying such a long diff for  docs/user-guide/commands.md? Did you by any chance generate it on Windows? If so, I think there is a way to avoid committing the \r\n: https://help.github.com/en/articles/dealing-with-line-endings

Yes I am on Windows. I use checkout-as-is and commit-as-is which suits most cases very well. Have pushed a new commit fixing the line endings.


Tree Tag Documentation

Can we add a link in the 'Selecting Features' documentation to a (comment-only) copy of the spreadsheet that is used to populated the tree tag. This is so users can see and add comments/suggestions for modifications to the queries.

updated on https://exports-staging.hotosm.org/en/v3/learn/feature_selections#configuration


Assigning to a tuple member within if fails

Aim
let some_condition = false; // for example's sake
let mut my_tuple: (bool, bool) = (false, false);

if some_condition {
    my_tuple.0 = true;
else {
    my_tuple.0 = false;
}

This compilation fails with:
error: Expected an expression but found =
...
             my_tuple.0 = true;

If I replace the tuple (bool, bool) with an array [bool; 2] and access via my_tuple[0], it compiles.
Note: My tuple was actually made up of structs, rather than bools, but I distilled it down to this, for simplicity.
I'm using the aztec3-hacky branch, so it could be because of that...?
Expected behavior
Expected it to be able to assign to the element of the tuple.
Bug
See section above.
To reproduce

Installation method
None
Nargo version
nargo 0.4.0 (git version hash: 22c2234fc72f34e96dff9c35f7f3548cf6062d0c, is dirty: false)
@noir-lang/noir_wasm version
No response
@noir-lang/barretenberg version
No response
@noir-lang/aztec_backend version
No response
Additional context
No response
Submission Checklist

[ ] Once I hit submit, I will assign this issue to the Project Board with the appropriate tags.

I'm using the aztec3-hacky branch, so it could be because of that...?

Possibly, it would be good to check that this is a bug on master too

Just checked with v0.4.1:
fn main(my_tuple: (bool, bool), some_condition: bool) -> pub (bool, bool) {
    // let some_condition = false; // for example's sake
    // let mut my_tuple: (bool, bool) = (false, false);

    if some_condition {
        my_tuple.0 = true;
    } else {
        my_tuple.0 = false;
    }

    my_tuple
}

error: Expected an expression but found =
   ┌─ /mnt/user-data/mike/packages/yarn-project/noir-contracts/src/contracts/mike-play/src/main.nr:27:20
   │
27 │         my_tuple.0 = true;
   │                    -

error: Expected an expression but found =
   ┌─ /mnt/user-data/mike/packages/yarn-project/noir-contracts/src/contracts/mike-play/src/main.nr:29:20
   │
29 │         my_tuple.0 = false;
   │                    -

error: aborting due to 2 previous errors
Error: Failed to compile circuit

Worth noting this fails without the if as well - it seems we don't parse assigning to tuple fields at all.


Request: Multiple component links and arithmetic in blueprint files

In the blueprints files (specifically within the components section) we already have the ability to link component dimensions to each other. This is not only useful for avoiding repetition, but more importantly it is useful because it keeps the dimensions linked even through thermal expansion of the components.
However it seems that current capabilities only allow for linking a dimension through equality to a single other dimension (that has been defined previously) as in:
fuel:
    od: 0.5
clad:
    id: fuel.od
    od: 0.6
wire:
    helixDiameter: clad.od # there is only a single link here

What I would like to be possible is to have multiple existing dimensions combined through simple arithmetic as in:
fuel:
    od: 0.5
clad:
    id: fuel.od
    od: clad.id + 0.1 # there is some basic math here
wire:
    od: 0.01
    helixDiameter: clad.od + wire.od / 2 # there are two links here

I could possibly see some issues related to thermal expansion cropping up, but maybe those wouldn't be an issue assuming linear thermal expansion coefficients.
This seems like a natural extension of the current linking capability, and I can think of more than one use case in a typical reactor problem.
Does anyone see any big issues here?

For the case you provide above with the clad od being mapped to the clad id + some number that could probably be better treated if we allowed a thickness parameter.
The second case is probably more interesting because of the link to two component dimensions. I believe that the helixDiameter should be effectively equal to the pin pitch for hexagon grid cases so this would probably bring up an interesting behavior with respect to pin locations with changing temperatures. Right now I believe we just initialize the grid on block and don't touch it again.
I wonder if the helixDiameter changes with thermal expansion or not as it is currently implemented (@youngmit?). Also, it's not clear to me what happens if we set the helixDiameter to anything other than the clad od + wire od. Is this an input bug or does it then allow for modeling "slop" in the pins.

I assume that this probably won't be changed at this time. If @john-science agrees then it might be good to close this issue and possibly open up a discussion topic that can cover different input quirks or possible upgrades.

Okay, I have a few thoughts.

I can definitely see how this could be generally useful to most users. And I like the idea of supporting it, except...
Thermal expansion might make this less obvious than it seems? (Particularly fun as block heights are entered at hot temperatures.)
In my experience, supporting mathematical operators in a config file snowballs Real Bad, Real Fast. Because it means writing code to turn "text" into "mathematical operations" in a computer. And that's called "a compiler". And we may start only supporting a few math operations, but people will 100% immediately ask for parenthesis and new operators that will make the logic more complex, and we will have to talk about order-of-operations, etc.

I think the idea might be helpful enough we should do something like this. Definitely. But I would like to tightly constrain the problem for we tackle it.  Thermal expansion and the full/permanent set of math operations we will support; those are my questions.

@keckler after some time in ARMI, what do you think about this? Just going through older tickets and seeing if we can triage them or close them?


Update container image

Some dependencies have been updated here

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

This got superceded by https://github.com/apache/beam/pull/25142


fix ci build failures

Do not use subshell so that it is easier to see where ci fails.

This change is

/lgtm, thanks!


Team statistics

User story
As a team leader I want to be able to measure the continuous improvements (total lead time and variation, problems solved etc) to guide and empower the team.
Dependencies
#154
#159 (to get data on which processes are in a specific team or responsible leader)

Alternatively: May be solved with #187


Fixes to update project to Swift 4.1

Fix deprecations
Fix issue in bridging header that was breaking tests

Great to see this building on 4.1!
It looks like we're getting some test failures and integration tests are failing as well. Is that caused by the swift update?
We've also got quite a few warnings:
ecToBUILD.build/Release/PodSpecToBUILDTests.build/Objects-normal/x86_64/BuildFile.o

/Users/jerry/Projects/rules_pods_rewrite/PodSpecToBUILDTests/ParserTests.swift:82:48: warning: 'characters' is deprecated: Please use String or Substring directly
                    .parseFully(Array("abcde.".characters)) ?? [],
                                               ^
/Users/jerry/Projects/rules_pods_rewrite/PodSpecToBUILDTests/ParserTests.swift:83:27: warning: 'characters' is deprecated: Please use String or Substring directly
            Array("abcde".characters)
                          ^
/Users/jerry/Projects/rules_pods_rewrite/PodSpecToBUILDTests/ParserTests.swift:91:66: warning: 'characters' is deprecated: Please use String or Substring directly
            let reps = Array([xs, ys, zs].joined(separator: ",").characters)
                                                                 ^
/Users/jerry/Projects/rules_pods_rewrite/PodSpecToBUILDTests/ParserTests.swift:91:66: warning: 'characters' is deprecated: Please use String or Substring directly
            let reps = Array([xs, ys, zs].joined(separator: ",").characters)
                                                                 ^
/Users/jerry/Projects/rules_pods_rewrite/PodSpecToBUILDTests/ParserTests.swift:114:47: warning: 'characters' is deprecated: Please use String or Substring directly
                .parseFully(Array(inputStream.characters)) ?? []
                                              ^
/Users/jerry/Projects/rules_pods_rewrite/PodSpecToBUILDTests/ParserTests.swift:114:47: warning: 'characters' is deprecated: Please use String or Substring directly
                .parseFully(Array(inputStream.characters)) ?? []
                                              ^
/Users/jerry/Projects/rules_pods_rewrite/Source/ObjcLibrary.swift:530:98: warning: 'flatMap' is deprecated: Please use compactMap(_:) for the case where closure returns an optional value
            return arr + buildPCHList(sources: [multi.ios, multi.osx, multi.watchos, multi.tvos].flatMap { $0 }.flatMap { Array($0) })
                                                                                ^
/Users/jerry/Projects/rules_pods_rewrite/Source/ObjcLibrary.swift:530:98: note: use 'compactMap(_:)' instead
            return arr + buildPCHList(sources: [multi.ios, multi.osx, multi.watchos, multi.tvos].flatMap { $0 }.flatMap { Array($0) })
                                                                                ^~~~~~~
                                                                                compactMap
/Users/jerry/Projects/rules_pods_rewrite/Source/ObjcLibrary.swift:534:100: warning: 'flatMap' is deprecated: Please use compactMap(_:) for the case where closure returns an optional value
        let headerSearchPaths: Set<String> = Set(headerDirs.fold(basic: { str in Set<String>([str].flatMap { $0 }) },
                                                                                ^
/Users/jerry/Projects/rules_pods_rewrite/Source/ObjcLibrary.swift:534:100: note: use 'compactMap(_:)' instead
        let headerSearchPaths: Set<String> = Set(headerDirs.fold(basic: { str in Set<String>([str].flatMap { $0 }) },
                                                                                ^~~~~~~
                                                                                compactMap
/Users/jerry/Projects/rules_pods_rewrite/Source/ObjcLibrary.swift:536:107: warning: 'flatMap' is deprecated: Please use compactMap(_:) for the case where closure returns an optional value
                                    return result.union([multi.ios, multi.osx, multi.watchos, multi.tvos].flatMap { $0 })
                                                                                ^
/Users/jerry/Projects/rules_pods_rewrite/Source/ObjcLibrary.swift:536:107: note: use 'compactMap(_:)' instead
                                    return result.union([multi.ios, multi.osx, multi.watchos, multi.tvos].flatMap { $0 })
                                                                                ^~~~~~~
                                                                                compactMap
/Users/jerry/Projects/rules_pods_rewrite/Source/ObjcLibrary.swift:518:18: warning: 'flatMap' is deprecated: Please use compactMap(_:) for the case where closure returns an optional value
                .flatMap { $0.count > 1 ? $0.first : nil }
                 ^
/Users/jerry/Projects/rules_pods_rewrite/Source/ObjcLibrary.swift:518:18: note: use 'compactMap(_:)' instead
                .flatMap { $0.count > 1 ? $0.first : nil }
                 ^~~~~~~
                 compactMap

Also, I noticed a few compiler warnings on SwiftCheck. Should we update that for 4.1?
/Users/jerry/Projects/rules_pods_rewrite/SwiftCheck/Sources/SwiftCheck/Property.swift:674:62: warning: 'characters' is deprecated: Please use String or Substring directly
                print("("  + gAllLabels[gAllLabels.startIndex..<gAllLabels.characters.index(gAllLabels.endIndex, offsetBy: -2)] + ")")
                                                                           ^
/Users/jerry/Projects/rules_pods_rewrite/SwiftCheck/Sources/SwiftCheck/Arbitrary.swift:304:43: warning: 'characters' is deprecated: Please use String or Substring directly
                return [Character].shrink([Character](s.characters)).map { String($0) }
                                                        ^
/Users/jerry/Projects/rules_pods_rewrite/SwiftCheck/Sources/SwiftCheck/Modifiers.swift:667:14: warning: 'deallocate(capacity:)' is deprecated: Swift currently only supports freeing entire heap blocks, use deallocate() instead
                        self.ptr?.deallocate(capacity: self.size)
                                  ^
/Users/jerry/Projects/rules_pods_rewrite/SwiftCheck/Sources/SwiftCheck/CoArbitrary.swift:74:34: warning: 'characters' is deprecated: Please use String or Substring directly
                        String.coarbitrary(String(x[x.characters.index(after: x.startIndex)..<x.endIndex]))
                                                      ^

+50 bonus points if we can treat warnings as errors 😉


SHACL validator returns many errors, when validating our own example files

I have tried this online SHACL validator:
https://www.itb.ec.europa.eu/shacl/any/upload
I used the SHACL file , as well as the example populations on our Respec page.
The validator returns too many errors, see validation report:
report.pdf
Very often, it is stating : "Property needs to have at least 1 value"
However:
Lina did already check our example files with another validator in January 24, the results then were without errors. See her validation report:
TestingSHACL-mobilityDCAT-AP-Iteration2.pdf
I don't understand the new error messages.
Can anyone please check what is wrong?

Hi @peterlubrich, I did the same test and I also got many errors. I do not know which tool Lina used to perform the validation. It could be because this tool automatically imports all the referenced shapes (e.g., the ones from DCAT), while the one used before checked only the shapes we defined directly. We should check the errors one by one to understand why they are thrown.
By the way I noticed other two minor issues related that should be fixed now:

[x] Links in the Respec page were broken because the examples folder was not copied there
[x] The original_population XML file had an error in the comment on line 104 (closing tag)
I kindly ask @Daham-Mustaf to check that everything is fine with my last commit.

To be checked considering also #36

@Daham-Mustaf Please perform check again against examples in the spec before release 1.1.0

I have run the SHACL playground as follows:

Shapes graph: SHACL file updated for v1.1.0
Data graph: SE example file

There are no more errors, so I am closing this issue


disable global model update when other work is going on

Updates to the Ceylon global model are never "urgent". So whenever anything else interesting is going on, they should not be scheduled, for example, when:

the user is typing
the completion window is open
the editor is typechecking the local file
we're trying to refactor something

Thanks @davidfestal, it seems to me—not very scientifically—that with your latest work, completion is working much better now.

I assume it's mainly related to the fact that now we don't start the model update when only the edited file was changed with changes that do not impact the other files. in most cases, when we need code completion, we are writing some block / specifier implementation, and in such a case the model update will not be triggered.


Generic[_T] lost on DataUpdateCoordinator

https://github.com/home-assistant/core/blob/3d8e8293d67094da383bb57f518802784e1fe3a5/homeassistant/helpers/update_coordinator.py#L55 vs
https://github.com/KapJI/homeassistant-stubs/blob/98df454159346546581bd0cd540c1945870d46cb/homeassistant-stubs/helpers/update_coordinator.pyi#L26 -- Generic[_T] got lost.
I suppose this is why for something like https://github.com/scop/home-assistant-jatekukko/blob/66ceb35160f20026d3f638e7696513a585a5436f/custom_components/jatekukko/coordinator.py#L42, mypy gives:
custom_components/jatekukko/coordinator.py:42: error: "DataUpdateCoordinator" expects no type arguments, but 1 given  [type-arg]

Similarly for BaseCoordinatorEntity.
This is with homeassistant-stubs 2023.2.4.

Unfortunately, this is limitation of stubgen, it doesn't extract all info, especially in more complicated cases like this. I really think that HA should just export typing info directly even if it's not fully complete.

Should be solved by mypy 1.4 upgrade in homeassistant-stubs 2023.6.3.


Problem setting IPALLOC_RANGE in the docker network plugin V2

I'm attempting to set the IPALLOC_RANGE flag as there is an overlap issue on <IP_ADDRESS>/8
What you expected to happen?
The IPALLOC_RANGE flag to be set
What happened?
Error response from daemon: setting "IPALLOC_RANGE" not found in the plugin configuration
How to reproduce it?
docker plugin install --grant-all-permissions store/weaveworks/net-plugin:latest_release
WEAVE_MULTICAST=1 IPALLOC_RANGE=<IP_ADDRESS>/8
or via the set:
docker plugin set store/weaveworks/net-plugin:latest_release IPALLOC_RANGE=<IP_ADDRESS>/8
Anything else we need to know?
See end of report for output but the docker plugin inspect command does not mention IPALLOC_RANGE, but does WEAVE_MULTICAST and the others.
Versions:
docker version
Client:
Version:      17.09.0-ce
API version:  1.32
Go version:   go1.8.3
Git commit:   afdb6d4
Built:        Tue Sep 26 22:42:18 2017
OS/Arch:      linux/amd64
Server:
Version:      17.09.0-ce
API version:  1.32 (minimum version 1.12)
Go version:   go1.8.3
Git commit:   afdb6d4
Built:        Tue Sep 26 22:40:56 2017
OS/Arch:      linux/amd64
Experimental: false
$uname -a
Linux swarm-master-1 4.10.0-24-generic #28-Ubuntu SMP Wed Jun 14 08:14:34 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
:
docker plugin inspect store/weaveworks/net-plugin:latest_release
[
    {
        "Config": {
            "Args": {
                "Description": "",
                "Name": "",
                "Settable": null,
                "Value": null
            },
            "Description": "Weave Net plugin for Docker",
            "Documentation": "https://weave.works",
            "Entrypoint": [
                "/home/weave/launch.sh"
            ],
            "Env": [
                {
                    "Description": "Extra args to `weaver` and `plugin`",
                    "Name": "EXTRA_ARGS",
                    "Settable": [
                        "value"
                    ],
                    "Value": ""
                },
                {
                    "Description": "Encryption password",
                    "Name": "WEAVE_PASSWORD",
                    "Settable": [
                        "value"
                    ],
                    "Value": ""
                },
                {
                    "Description": "MTU",
                    "Name": "WEAVE_MTU",
                    "Settable": [
                        "value"
                    ],
                    "Value": ""
                },
                {
                    "Description": "Enable multicast for all Weave networks",
                    "Name": "WEAVE_MULTICAST",
                    "Settable": [
                        "value"
                    ],
                    "Value": ""
                }
            ],
            "Interface": {
                "Socket": "weave.sock",
                "Types": [
                    "docker.networkdriver/1.0"
                ]
            },
            "IpcHost": false,
            "Linux": {
                "AllowAllDevices": false,
                "Capabilities": [
                    "CAP_NET_ADMIN",
                    "CAP_SYS_ADMIN"
                ],
                "Devices": null
            },
            "Mounts": [
                {
                    "Description": "",
                    "Destination": "/host/proc/",
                    "Name": "",
                    "Options": [
                        "rbind",
                        "rw"
                    ],
                    "Settable": null,
                    "Source": "/proc/",
                    "Type": "bind"
                },
                {
                    "Description": "",
                    "Destination": "/var/run/docker.sock",
                    "Name": "",
                    "Options": [
                        "rbind"
                    ],
                    "Settable": null,
                    "Source": "/var/run/docker.sock",
                    "Type": "bind"
                },
                {
                    "Description": "",
                    "Destination": "/host/var/lib/",
                    "Name": "",
                    "Options": [
                        "rbind"
                    ],
                    "Settable": null,
                    "Source": "/var/lib/",
                    "Type": "bind"
                },
                {
                    "Description": "",
                    "Destination": "/host/etc/",
                    "Name": "",
                    "Options": [
                        "rbind"
                    ],
                    "Settable": null,
                    "Source": "/etc/",
                    "Type": "bind"
                }
            ],
            "Network": {
                "Type": "host"
            },
            "PidHost": false,
            "PropagatedMount": "",
            "User": {},
            "WorkDir": "",
            "rootfs": {
                "diff_ids": [
                    "sha256:aef58d4eb946b9e5cb917bf330c71fb73ccfaff34cb2cfce71640cde54db6384"
                ],
                "type": "layers"
            }
        },
        "Enabled": false,
        "Id": "dfce6b66af1400980842664248ef057545af7b761e48fac24b92f2137a6044e9",
        "Name": "weavenet:latest",
        "PluginReference": "docker.io/store/weaveworks/net-plugin:latest_release",
        "Settings": {
            "Args": [],
            "Devices": [],
            "Env": [
                "EXTRA_ARGS=",
                "WEAVE_PASSWORD=",
                "WEAVE_MTU=",
                "WEAVE_MULTICAST=1"
            ],
            "Mounts": [
                {
                    "Description": "",
                    "Destination": "/host/proc/",
                    "Name": "",
                    "Options": [
                        "rbind",
                        "rw"
                    ],
                    "Settable": null,
                    "Source": "/proc/",
                    "Type": "bind"
                },
                {
                    "Description": "",
                    "Destination": "/var/run/docker.sock",
                    "Name": "",
                    "Options": [
                        "rbind"
                    ],
                    "Settable": null,
                    "Source": "/var/run/docker.sock",
                    "Type": "bind"
                },
                {
                    "Description": "",
                    "Destination": "/host/var/lib/",
                    "Name": "",
                    "Options": [
                        "rbind"
                    ],
                    "Settable": null,
                    "Source": "/var/lib/",
                    "Type": "bind"
                },
                {
                    "Description": "",
                    "Destination": "/host/etc/",
                    "Name": "",
                    "Options": [
                        "rbind"
                    ],
                    "Settable": null,
                    "Source": "/etc/",
                    "Type": "bind"
                }
            ]
        }
    }
]

We've found the cause: #3150.


feat: use sonic_rs

sonic_rs is a json parse crate based on zerocopy and simd.
sonic_rs's parsing speed is much faster than serde_json.
Refer to benchmark

Why closed?

Why closed?

When I migrated from serde_json to sonic_rs, the performance in the benchmark became worse, so I tried simdjson again, but the performance did not improve significantly. Here is my simdjson fork https://github.com/nanakura/emacs-lsp-booster/tree/simd-json

Why closed?

When I migrated from serde_json to sonic_rs, the performance in the benchmark became worse, so I tried simdjson again, but the performance did not improve significantly. Here is my simdjson fork https://github.com/nanakura/emacs-lsp-booster/tree/simd-json

Did you build lsp-booster with RUSTFLAGS='-C target-cpu=native'? Ref: RUSTFLAGS='-C target-cpu=native'

Why closed?

When I migrated from serde_json to sonic_rs, the performance in the benchmark became worse, so I tried simdjson again, but the performance did not improve significantly. Here is my simdjson fork https://github.com/nanakura/emacs-lsp-booster/tree/simd-json

Did you build lsp-booster with RUSTFLAGS='-C target-cpu=native'? Ref: https://github.com/cloudwego/sonic-rs?tab=readme-ov-file#requirementsnotes

I really didn't, it reminded me

I will try again

How is the benchmark now?

USTFLAGS='-C target-cpu=native'

In fact, serde_json will also have performance improvements if RUSTFLAGS='-C target-cpu=native' is used
serde_json

and sonic_rs

I wonder why the results are not very promising. Could you use flamegraph to figure out why sonic-rust doesn't outperform serde_json a lot?

I wonder why the results are not very promising. Could you use flamegraph to figure out why sonic-rust doesn't outperform serde_json a lot?
Ref:

nnethercote.github.io/perf-book/profiling.html
<EMAIL_ADDRESS>(release)

I tried RUSTFLAGS='-C target-cpu=native -C symbol-mangling-version=v0' perf record -g -- cargo test --test bytecode_test --release to  get generate a profiling file，then I get a flamegraph through https://github.com/brendangregg/FlameGraph, but the flamegraph is unreadble


Where to add the callback

I try to add a the bootstrap 3 dropdown to my page. But it isn't workint with smoothstate sO I tought to add it via the smoothstate callback. Bet where do I have to place it in order to work?
;(function($) {
   'use strict';
   var $body = $('html, body'),
   content = $('#main').smoothState({
    prefetch: true,  development : true,pageCacheSize: 4,
    // in progress of loading
    onProgress : {
      duration: 0, // Duration of the animations, if any.
      render: function (url, $container) {
        $body.css('cursor', 'wait');
        $body.find('a').css('cursor', 'wait');
      }

    },
    onEnd : {
      duration: 100, // Duration of the animations, if any.
      render: function (url, $container, $content) {
        $body.css('cursor', 'auto');
        $body.find('a').css('cursor', 'auto');
        $container.html($content);
        //Start Velocity
          $('#bla').velocity("fadeIn", { duration: 600 });
          $('.arrow-up').velocity("fadeIn", {  duration: 600 });
        //End velocity
        $(document).ready();
        $(window).trigger('load');
      },
     //That is obviously the wrong place.
      callback : function(url, $container, $content) {
        $(function() {
          $('input').dropdown()
        });
      },
    },
    // Runs when a link has been activated
    onStart: {
      duration:100, // Duration of our animation
      render: function (url, $container) {
        //Start Velocity
          $('.arrow-up').velocity("fadeOut", {   translateY: "200px", duration: 300 });
          $('p').velocity("fadeOut", {  colorAlpha: 0, duration: 600 });
          $('#bla').velocity("fadeOut", { duration: 600 });
        //End Velocity
      }
    }
  }).data('smoothState');
  //.data('smoothState') makes public methods available
})(jQuery);

Hi there,
I've realized it would best to move personal support requests over to Stack Overflow. There's a special smoothstate.js label for us there. This will help us keep the Github issue tracker clean for bugs, pull requests, and enhancements. If you're not having any luck on Stack Overflow, feel free to join the Gitter room and ping me there. I'll try to help as much as I can.
That said, I'll be closing out this issue.


The edge style is wrong when dragging

Describe the Bug
I set the edge type to 'step', but when dragging, the edge is not of type 'step'
defaultEdgeOptions={{
      type: 'step',
      style: {
          stroke: theme.colors.pattern.text.secondary,
      },
      markerEnd: {
          type: MarkerType.ArrowClosed,
          width: 20,
          height: 20,
      },
  }}

Your Example Website or App
No response
Steps to Reproduce the Bug or Issue
1.set defaultEdgeOptions， type: 'step',
2.Create new connections between nodes
Expected behavior
The edge type is 'step'
Screenshots or Videos
No response
Platform

OS: macOS
Browser: Chrome
Version: 123.0.6312.124

Additional context
No response

An edge and a connection line  are two different things, hence why defaultEdgeOptions will not change the style/type of a connection line.
Edges are established connections between two nodes.
Connection Lines are lines that are drawn to establish a connection between two nodes (in other words, the connection has not yet been created).
There's a separate set of props for connection lines (besides using your own custom connection line).
In your case you would want to use something like this
<ReactFlow connectionLineType={ConnectionLineType.Step} connectionLineStyle={{ stroke: theme.colors.pattern.text.secondary, }} {...rest}>


Subscribe button problem is solved, #394 issue is solved

issue number #394  is solved.
Now the subscribe button is responsive in the mobile version.
before

Now

Okay!
@BrindaManani


After Branch Hook

I would like to have a hook that clones database (based on a branch name) after creating new branch. How could I write such hook? I don't see any documentation or section in readme for creating custom hooks.

Hey @ciembor, I'm not really clear on what you're trying to accomplish, and there are a lot of questions about the kind of flow you'd like to support.
I would suggest that you keep hooks very simple. Considering how often you change branches, tying the post-checkout hook to cloning of a database sounds like a quick way to frustrate developers (since I assume it is a time-consuming process).
If you insist, I suggest you look at the current set of post-checkout hooks for some inspiration. Good luck!

Thank you. It takes time, but I want to automise this process:
https://manas.tech/blog/2016/01/08/switching-rails-app-database-per-git-branch.html
I know it's time consuming, but it's even more time consuming if you do this manually :).
But I digged deeper into git hooks, and I see that it's not possible to have a hook for git branch (first I thought I can have a hook for any command). So I will probably stay with a rake task :(.


pushy-client service issue. Windows platform.

Hi guys,
I have found an issue with pushy-client service for windows.
It happenes when it just hangs and becomes unresponseve.
Eventhough it stays in running state among services.
The only thing fixes it and makes available. Service restart.
Can you please take a look into and add some kind of self-check if it's working (listening)) or not.
For last two weeks it hang on around 10 boxes out of 15 where it was installed.
So I had to log into each box and restart service.
Thank you in advance.
Regards,
Taras.

Thanks for reporting this I'm in the process of improving the push client on windows and this is helpful to know.
I think what you are proposing is to have the windows service monitor the actual push client running and reset it when it becomes non-responsive; that seems sensible, but I'd also like to understand why it's hanging in the first place.
Can you give me any tips on how to make it hang? I assume by hang, you mean stops responding to server commands. I guess a hang involves a full freeze, including heartbeats to the server. Does a client hang even if no jobs have been run on it? Anything show up in the client logs when it hangs?
Does the server think the client is available when it's frozen?

Hi Mark,
When it was hang on the system it still was being shown as in running state.  But if I was doing "knife node status " I was getting "unavailable" state.  So it was not responding at all. But for some reason state on client side was being shown as running.
Unfortunately I don't remember boxes names where this issue happened.
If I see it again I will let you know.
please let me know what logs I should copy and send to you once I find this issue again.
Regards, Taras.
20 лютого 2015, 00:04:04, від Mark Anderson <<EMAIL_ADDRESS>>:
Thanks for reporting this I'm in the process of improving the push client on windows and this is helpful to know. I think what you are proposing is to have the windows service monitor the actual push client running and reset it when it becomes non-responsive; that seems sensible, but I'd also like to understand why it's hanging in the first place. Can you give me any tips on how to make it hang? I assume by hang, you mean stops responding to server commands. I guess a hang involves a full freeze, including heartbeats to the server. Does a client hang even if no jobs have been run on it? Anything show up in the client logs when it hangs? Does the server think the client is available when it's frozen? —
Reply to this email directly or view it on GitHub .

Hi Mark,
I have got the same issue.  And it's actually happening all the time.  I have even developed automated powershell script to monitor pushy-client responsiveness and let me know once node is unavailable within pushy-client.
I have around few nodes each day where pushy-client becomes unresponsive.
Please check attachment of the logs from one of the nodes.
Here is some details from node: chef-client version: 12.0.0, 12.1.0, 11.16.4. So actually it happens on different chef-client versions. Pushy-client version is in attachment. How to resolve: just restart windows service pushy-client.  How visible: from system none. It's in running state etc. Only "knife node status " to see if it's available or unavailable. Windows version: 2008 R2. 64-bits
Thank you in advance for the help.
Regards, Taras.
20 лютого 2015, 00:04:04, від Mark Anderson <<EMAIL_ADDRESS>>:
Thanks for reporting this I'm in the process of improving the push client on windows and this is helpful to know. I think what you are proposing is to have the windows service monitor the actual push client running and reset it when it becomes non-responsive; that seems sensible, but I'd also like to understand why it's hanging in the first place. Can you give me any tips on how to make it hang? I assume by hang, you mean stops responding to server commands. I guess a hang involves a full freeze, including heartbeats to the server. Does a client hang even if no jobs have been run on it? Anything show up in the client logs when it hangs? Does the server think the client is available when it's frozen? —
Reply to this email directly or view it on GitHub .

From ticket 3349, it looks like the heartbeat fails and then things get bad:
[2015-03-30T16:06:58+00:00] DEBUG: [fqdn] Received server heartbeat (sequence #5780913)
[2015-03-30T16:06:58+00:00] DEBUG: [fqdn] Sending heartbeat (sequence #533971)
[2015-03-30T16:06:59+00:00] DEBUG: [fqdn] Sending heartbeat (sequence #533972)
[2015-03-30T16:07:00+00:00] DEBUG: [fqdn] Sending heartbeat (sequence #533973)
[2015-03-30T16:07:01+00:00] DEBUG: [fqdn] Sending heartbeat (sequence #533974)
[2015-03-30T16:07:02+00:00] INFO: [fqdn] Server has missed 4 heartbeats in a row.  Considering it offline, and stopping heartbeat.
[2015-03-30T16:07:02+00:00] INFO: [fqdn] Closing and reopening sockets since server is down ...
[2015-03-30T16:07:03+00:00] INFO: [fqdn] Stopping command / server heartbeat receive thread and destroying sockets ...
[2015-03-30T16:07:03+00:00] INFO: [fqdn] Connecting to command channel at tcp://ip-numbers-here.ec2.internal:10002
[2015-03-30T16:07:15+00:00] ERROR: [fqdn] Error reconfiguring sockets when server went down: Invalid argument
c:/opscode/pushy/embedded/lib/ruby/gems/1.9.1/gems/opscode-pushy-client-1.1.3/lib/pushy_client/protocol_handler.rb:106:in `connect'
c:/opscode/pushy/embedded/lib/ruby/gems/1.9.1/gems/opscode-pushy-client-1.1.3/lib/pushy_client/protocol_handler.rb:106:in `start'
c:/opscode/pushy/embedded/lib/ruby/gems/1.9.1/gems/opscode-pushy-client-1.1.3/lib/pushy_client/protocol_handler.rb:133:in `block (2 levels) in reconfigure'
<internal:prelude>:10:in `synchronize'
c:/opscode/pushy/embedded/lib/ruby/gems/1.9.1/gems/opscode-pushy-client-1.1.3/lib/pushy_client/protocol_handler.rb:131:in `block in reconfigure'
<internal:prelude>:10:in `synchronize'
c:/opscode/pushy/embedded/lib/ruby/gems/1.9.1/gems/opscode-pushy-client-1.1.3/lib/pushy_client/protocol_handler.rb:130:in `reconfigure'
c:/opscode/pushy/embedded/lib/ruby/gems/1.9.1/gems/opscode-pushy-client-1.1.3/lib/pushy_client/protocol_handler.rb:57:in `block (2 levels) in initialize'
c:/opscode/pushy/embedded/lib/ruby/1.9.1/win32ole.rb:13:in `call'
c:/opscode/pushy/embedded/lib/ruby/1.9.1/win32ole.rb:13:in `block in initialize'
...
[2015-03-30T17:48:56+00:00] INFO: [fqdn] Config is now 3600 seconds old.  Reconfiguring / reloading keys ...
[2015-03-30T17:48:56+00:00] INFO: [fqdn] Reconfiguring client / reloading keys ...
...
[2015-03-30T17:48:57+00:00] DEBUG: Chef::HTTP calling Chef::HTTP::JSONInput#handle_response
[2015-03-30T17:48:57+00:00] INFO: [fqdn] Stopping command / server heartbeat receive thread and destroying sockets ...
[2015-03-30T17:48:57+00:00] ERROR: [fqdn] Error reconfiguring: undefined method `close' for nil:NilClass
c:/opscode/pushy/embedded/lib/ruby/gems/1.9.1/gems/opscode-pushy-client-1.1.3/lib/pushy_client/protocol_handler.rb:176:in `internal_stop'
c:/opscode/pushy/embedded/lib/ruby/gems/1.9.1/gems/opscode-pushy-client-1.1.3/lib/pushy_client/protocol_handler.rb:132:in `block (2 levels) in reconfigure'
<internal:prelude>:10:in `synchronize'
c:/opscode/pushy/embedded/lib/ruby/gems/1.9.1/gems/opscode-pushy-client-1.1.3/lib/pushy_client/protocol_handler.rb:131:in `block in reconfigure'
<internal:prelude>:10:in `synchronize'
c:/opscode/pushy/embedded/lib/ruby/gems/1.9.1/gems/opscode-pushy-client-1.1.3/lib/pushy_client/protocol_handler.rb:130:in `reconfigure'
c:/opscode/pushy/embedded/lib/ruby/gems/1.9.1/gems/opscode-pushy-client-1.1.3/lib/pushy_client.rb:100:in `block in reconfigure'
<internal:prelude>:10:in `synchronize'
c:/opscode/pushy/embedded/lib/ruby/gems/1.9.1/gems/opscode-pushy-client-1.1.3/lib/pushy_client.rb:94:in `reconfigure'
c:/opscode/pushy/embedded/lib/ruby/gems/1.9.1/gems/opscode-pushy-client-1.1.3/lib/pushy_client.rb:113:in `block in trigger_reconfigure'
c:/opscode/pushy/embedded/lib/ruby/1.9.1/win32ole.rb:13:in `call'
c:/opscode/pushy/embedded/lib/ruby/1.9.1/win32ole.rb:13:in `block in initialize'

can this bug be fixed?
if you format a node and reinstall os, then this bug ocurrs.
please fix this..

Can confirm that this bug SUCKS big time. Can we get some love on this, you guys are killin me smalls.

Bumping this as I'm also encountering this issue.

I wouldn't recommend chef-push for production because of this. A lot of our team members are exhausted with this, and I was the guy who is to blame because I trusted chef-push.

I'm also bumping this issue, Windows 10 with Chef Pushy Client v1.1.5

I'm seeing this error as well, but with a CentOS box. It might not be confined to just Windows. Restarting the service temporarily fixes it, but it does eventually become unresponsive after the heartbeat stops.
2016-03-01_12:35:20.66887 INFO: [fqdn] Config is now 3600 seconds old.  Reconfiguring / reloading keys ...
2016-03-01_12:35:20.66897 INFO: [fqdn] Reconfiguring client / reloading keys ...
2016-03-01_12:35:20.66897 INFO: [fqdn] Retrieving configuration from https://chef-fqdn/organizations/edo/pushy/config/fqdn ...
2016-03-01_12:35:20.70034 INFO: [fqdn] Stopping command / server heartbeat receive thread and destroying sockets ...
2016-03-01_12:35:20.70036 ERROR: [fqdn] Error reconfiguring: undefined method `close' for nil:NilClass
2016-03-01_12:35:20.70036 /opt/opscode-push-jobs-client/embedded/lib/ruby/gems/1.9.1/gems/opscode-pushy-client-1.1.3/lib/pushy_client/protocol_handler.rb:176:in `internal_stop'
2016-03-01_12:35:20.70037 /opt/opscode-push-jobs-client/embedded/lib/ruby/gems/1.9.1/gems/opscode-pushy-client-1.1.3/lib/pushy_client/protocol_handler.rb:132:in `block (2 levels) in reconfigure'
2016-03-01_12:35:20.70037 <internal:prelude>:10:in `synchronize'
2016-03-01_12:35:20.70037 /opt/opscode-push-jobs-client/embedded/lib/ruby/gems/1.9.1/gems/opscode-pushy-client-1.1.3/lib/pushy_client/protocol_handler.rb:131:in `block in reconfigure'
2016-03-01_12:35:20.70037 <internal:prelude>:10:in `synchronize'
2016-03-01_12:35:20.70038 /opt/opscode-push-jobs-client/embedded/lib/ruby/gems/1.9.1/gems/opscode-pushy-client-1.1.3/lib/pushy_client/protocol_handler.rb:130:in `reconfigure'
2016-03-01_12:35:20.70038 /opt/opscode-push-jobs-client/embedded/lib/ruby/gems/1.9.1/gems/opscode-pushy-client-1.1.3/lib/pushy_client.rb:100:in `block in reconfigure'
2016-03-01_12:35:20.70039 <internal:prelude>:10:in `synchronize'
2016-03-01_12:35:20.70039 /opt/opscode-push-jobs-client/embedded/lib/ruby/gems/1.9.1/gems/opscode-pushy-client-1.1.3/lib/pushy_client.rb:94:in `reconfigure'
2016-03-01_12:35:20.70039 /opt/opscode-push-jobs-client/embedded/lib/ruby/gems/1.9.1/gems/opscode-pushy-client-1.1.3/lib/pushy_client.rb:113:in `block in trigger_reconfigure'

Same error: Error reconfiguring: undefined method 'close' for nil:NilClass
chef-client 12.5.1

Any updates on this issue? I'm experiencing issues with Push Jobs Client on my Windows nodes - nodes report to be unavailable, and Push Jobs Client service should be restarted in order to get them to be available again

Any updates yet....

Can push jobs PLEASE get some love. This is ridic

Hello all,
We encountered this same issue last week, why does Push Jobs Client service has to be restarted for node to become "available"?
Any fix?
Thank you.

I have  a short fix for this. Start the service without logging into the machine using below command
sc \machine_ip start push-jobs-client

@sunilkumar452 That fix doesn't apply because the Push Job service stays started in many cases it's just not actually functional.

We see the same issue, which causes Chef Automate delivery phases to fail until the service is bounced.  Both Windows and Linux. Only fix we've found is to restart the service.  Additionally, we have a ton of problems with the push client in Test Kitchen, where it will intermittently just fail to restart the push client service, and fail the kitchen run.


LinkAssemblies failure with TK.CustomMap using skip linking assemblies

this is the error:
Severity	Code	Description	Project	File	Line	Suppression State
Error		The "LinkAssemblies" task failed unexpectedly.
Java.Interop.Tools.Diagnostics.XamarinAndroidException: error XA2006: Could not resolve reference to 'System.Void Xamarin.Forms.Maps.Android.MapRenderer::OnElementChanged(Xamarin.Forms.Platform.Android.ElementChangedEventArgs1<Xamarin.Forms.View>)' (defined in assembly 'TK.CustomMap.Android, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null') with scope 'Xamarin.Forms.Maps.Android, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null'. When the scope is different from the defining assembly, it usually means that the type is forwarded. ---> Mono.Cecil.ResolutionException: Failed to resolve System.Void Xamarin.Forms.Maps.Android.MapRenderer::OnElementChanged(Xamarin.Forms.Platform.Android.ElementChangedEventArgs1<Xamarin.Forms.View>)
at Mono.Linker.Steps.MarkStep.MarkMethod(MethodReference reference)
at Mono.Linker.Steps.MarkStep.MarkInstruction(Instruction instruction)
at Mono.Linker.Steps.MarkStep.MarkMethodBody(MethodBody body)
at Mono.Linker.Steps.MarkStep.ProcessMethod(MethodDefinition method)
at Mono.Linker.Steps.MarkStep.ProcessQueue()
at Mono.Linker.Steps.MarkStep.Process()
at Mono.Linker.Steps.MarkStep.Process(LinkContext context)
at MonoDroid.Tuner.MonoDroidMarkStep.Process(LinkContext context)
at Mono.Linker.Pipeline.Process(LinkContext context)
at MonoDroid.Tuner.Linker.Process(LinkerOptions options, LinkContext& context)
at Xamarin.Android.Tasks.LinkAssemblies.Execute(DirectoryAssemblyResolver res)
--- End of inner exception stack trace ---
at Java.Interop.Tools.Diagnostics.Diagnostic.Error(Int32 code, Exception innerException, String message, Object[] args)
at Xamarin.Android.Tasks.LinkAssemblies.Execute(DirectoryAssemblyResolver res)
at Xamarin.Android.Tasks.LinkAssemblies.Execute()
at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute()
at Microsoft.Build.BackEnd.TaskBuilder.d__26.MoveNext()	Keep.Clients.Droid
can you help on this issue?

Which NuGet version/XF version are you using?

Same here
Java.Interop.Tools.Diagnostics.XamarinAndroidException: error XA2006: Could not resolve reference to 'Android.Gms.Location.Places.IAutocompletePrediction' (defined in assembly 'TK.CustomMap.Android, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null') with scope 'Xamarin.GooglePlayServices.Location, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null'. When the scope is different from the defining assembly, it usually means that the type is forwarded. ---> Mono.Cecil.ResolutionException: Failed to resolve Android.Gms.Location.Places.IAutocompletePrediction
Xamarin.Forms: v<IP_ADDRESS>
Xamarin.Forms.Maps: v<IP_ADDRESS>
Xamarin.GooglePlayServices.Maps: v42.1001.0

Ran in to the issue today. Happening only in release mode.

Hi, does anyone have a solution or workaround for this issue? Disabling the Linker functionality is not an option for me.

Can you try to downgrade to XF 2.3.3 and see if this still happens?

It's not related to XF. It's the latest version of XF Maps changing the
reference of base packages. Everything has been split into smaller packages
by Google play.
If you update your referenced XF maps it should start working again.
On 21-Jun-2017 5:18 PM, "TorbenK"<EMAIL_ADDRESS>wrote:

Can you try to downgrade to XF 2.3.3 and see if this still happens?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/TorbenK/TK.CustomMap/issues/210#issuecomment-310054084,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AK7Z6Pf5PtrDIKSZMKkvLt7Q3ef5L0Ixks5sGQMOgaJpZM4Mwsdm
.

Hi
I'm getting this error message:
Java.Interop.Tools.Diagnostics.XamarinAndroidException: error XA2006: Could not resolve reference to 'Android.Gms.Location.Places.IAutocompletePrediction' (defined in assembly 'TK.CustomMap.Android, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null') with scope 'Xamarin.GooglePlayServices.Location, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null'. When the scope is different from the defining assembly, it usually means that the type is forwarded. ---> Mono.Cecil.ResolutionException: Failed to resolve Android.Gms.Location.Places.IAutocompletePrediction
en Mono.Linker.Steps.MarkStep.MarkType(TypeReference reference)
en MonoDroid.Tuner.MonoDroidMarkStep.MarkType(TypeReference reference)
en Mono.Linker.Steps.MarkStep.MarkGenericArguments(IGenericInstance instance)
en Mono.Linker.Steps.MarkStep.GetOriginalType(TypeReference type)
en Mono.Linker.Steps.MarkStep.MarkType(TypeReference reference)
en MonoDroid.Tuner.MonoDroidMarkStep.MarkType(TypeReference reference)
en Mono.Linker.Steps.MarkStep.MarkField(FieldReference reference)
en Mono.Linker.Steps.MarkStep.InitializeFields(TypeDefinition type)
en Mono.Linker.Steps.MarkStep.InitializeType(TypeDefinition type)
en Mono.Linker.Steps.MarkStep.InitializeType(TypeDefinition type)
en Mono.Linker.Steps.MarkStep.InitializeAssembly(AssemblyDefinition assembly)
en Mono.Linker.Steps.MarkStep.Initialize()
en Mono.Linker.Steps.MarkStep.Process(LinkContext context)
en Mono.Linker.Pipeline.Process(LinkContext context)
en MonoDroid.Tuner.Linker.Process(LinkerOptions options, LinkContext& context)
en Xamarin.Android.Tasks.LinkAssemblies.Execute(DirectoryAssemblyResolver res)
--- Fin del seguimiento de la pila de la excepción interna ---
en Java.Interop.Tools.Diagnostics.Diagnostic.Error(Int32 code, Exception innerException, String message, Object[] args)
en Xamarin.Android.Tasks.LinkAssemblies.Execute(DirectoryAssemblyResolver res)
en Xamarin.Android.Tasks.LinkAssemblies.Execute()
en Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute()
en Microsoft.Build.BackEnd.TaskBuilder.d__26.MoveNext()	Sales2Go.Droid
Have anybody found the solution for that?
thanks in advance!!

I have the same error, when I started to generate the release of the project.
Error XA2006: Could not resolve reference to 'Android.Gms.Location.Places.IAutocompletePrediction' (defined in assembly 'TK.CustomMap.Android, Version = <IP_ADDRESS>, Culture = neutral, PublicKeyToken = null') with scope 'Xamarin. GooglePlayServices.Location, Version = <IP_ADDRESS>, Culture = neutral, PublicKeyToken = null '. When the scope is different from the defining assembly, it usually means that the type is forwarded.

Same here: Error		The "LinkAssemblies" task failed unexpectedly.
Java.Interop.Tools.Diagnostics.XamarinAndroidException: error XA2006: Could not resolve reference to 'Android.Gms.Location.Places.IAutocompletePrediction' (defined in assembly 'TK.CustomMap.Android, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null') with scope 'Xamarin.GooglePlayServices.Location, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null'. When the scope is different from the defining assembly, it usually means that the type is forwarded. ---> Mono.Cecil.ResolutionException: Failed to resolve Android.Gms.Location.Places.IAutocompletePrediction

Hi @hot33331
I solved it, downloading the code of the project and adding it to the solution, add and associate the dll directly.

I have the same error when building in release mode. Based on this post maybe some of the references need to be updated.

@Micnick  How does one "add and associate the dll directly" ?

Had the same linker issue. Resolved by opening the Droid project properties > Android Options > Linking and changing the value from 'Sdk Assemblies Only' to 'Sdk and User Assemblies'


Linter idea: z-index max value

It would be great to be able to restrict the z-index value across a project.
For example, enforcing a maximum value of 10 instead of someone starting with 999, the next person coming along and typing 9999, and going all the way up to<PHONE_NUMBER>99. The result should be z-index values between 1 and 10. I can't think of many instances where a site should need more than 10 layers of z-index.
Thoughts?

:+1:

Alternatively, we could also write a linter that behaves similar to the ColorVariable linter, where only variables are valid for z-index. Then you can have a global configuration for all z-indexes and just reference them when you need them. This is what we do at Brigade. Here's our global configuration:
$z-index-menu: 100;
$z-index-navigation-main: 200;
$z-index-floating-action-button: 300;
$z-index-modal-wrapper: 400;
$z-index-toast: 500;
$z-index-n-progress: 600;

I'm not actually sure why we leave a one-hundred gap in between. Since we have full control over the values, we might as well just use 1-6.

That's also a good suggestion, @trotzig. It's funny you mention that solution because I just wrote everything to go into a configuration file for my current project.

Well currently the variables thing is easy to do by adding z-index to the VariablesForProperty linter

Ah, I forgot about that linter! Great that you mentioned it, I just spent a bit of time making sure that all our z-indexes were in fact variables (a few instances didn't use variables in our codebase). I'll make sure to add that to our project's scss-lint config.

I've added that to our scss-lint config. Works great!

I'm closing this issue now as it seems like we have something good enough in place already. Feel free to reopen if you think we need a linter more closely targeted at z-indexes.

Well no, the original issue was about preventing z-indexes from being too random

Alright, cool. I'm happy to keep this open until we have something else. The VariableForProperty linter seemed enough to me. The upside of having that linter too is that you have to semantically name your z-index values. The names make it easier to reason about what the value means. Though I have to admit that it's hard to come up with good names.

@Anahkiasen Can you elaborate on why using VariableForProperty doesn't solve that problem?
I would suggest using variables is the best way to ensure your z-indexes are "less random." You can define semantically named variables describing different "layers" of depths so you can easily deduce from the variable name which layer an element resides.
If using VariableForProperty does not allow you to enforce a specific set of z-indexes, what kind of system would you consider? I would think that having a linter which enforces a specific range of z-index values is pretty arbitrary and doesn't give you any semantic benefit from a readability perspective. Someone new to your project doesn't know the consequence of z-index 100 or 1000 relative to other z-indexes, but variables for the indexes would.
Interested to hear your thoughts.

Just basically a linter that takes the lowest and highest z-index and asserts that the range isn't greater than a configured X number, default being 10 per example or something. While VariableForProperty solves half of the problem, it doesn't prevent a bad developer from spamming nonsensical z-indexes like 99999999.

@Anahkiasen: I believe VariableForProperty does solve the problem. By having a predefined set of z-indexes, your developers always choose from that predefined set. If they try to create a non-sensical number, VariableForProperty prevents them from doing this since it enforces you use a variable.
If your issue is that your developers would add to this pre-defined list of z-indexes, that's something that can easily be corrected. As long as you're using variables, the actual value of the z-index doesn't really matter unless you're integrating with third-party CSS code.
If your issue is that developers would create variables inline to skirt around the issue, it sounds like you have a process problem. :)
Adding a linter to enforce a specific integer range for z-indexes doesn't seem to solve the actual problem, unless there's a particular situation you're thinking of that I'm not considering here.

Closing since I'm not seeing convincing arguments for the need for such a linter, especially given the high-level issue is solvable using VariableForProperty, as discussed above.
Feel free to reopen if you have strong feelings otherwise, but at that point a pull request would be preferred.


"..." shows on Android Navigation bar

A Supersonic bug
It is reproducible on /myProject example as well as kitchensink example.
Navigatioin bar show Text correctly on iOS emulator, my iPhone 6, and 2 other Android phones I've tested. But it shows only three dots "..." on one Android device.
It doesn't help when I change css text size or weight.
Some details about the particular device that fails on Navigation bar:
A Samsung Note 3 NEO phone with Android version 4.4.2 installed
Device name SM-N7505

What is the code initializing the <super-navbar> component? It could be a bug that doesn't strip extra whitespace on Android that might have resurfaced. Can you see if changing it like <super-navbar>My Title</super-navbar> (i.e. no line changes) has an effect?

Precisely, it is because of empty space, after change as you suggested, it displays all right. Thanks!


error: overlap is not transmuted!

I've seen some issues here, but most of them are because the files are not in the right order or the sequence names are not the same. 209, 203, 132, 103, 77
However, I keep encountering this error even when I check my runs and sequence. I am using Racon v1.4.20 via bioconda.
These are my commands:
minimap2 haplotype-dam.fasta haplotype-dam.fasta.gz -o haplotype-dam.paf
racon_wrapper -t 32 --split 97723193 --subsample<PHONE_NUMBER> 20 haplotype-dam.fasta.gz haplotype-dam.paf haplotype-dam.fasta > rw-polished_haplotype-Dam.fasta
I've also checked if there are duplicates in my reads and found nothing:
gunzip -c haplotype-dam.fasta.gz | uniq -c > countreads.list
wc -l countreads.list
23394555 countreads.list

awk '{sum+=$1} END {print sum}' countreads.list
23394555

the read sequence names are also the same with paf.
I'm using PacBio CLR reads, which were haplotype-separated using Canu. Could there be implications using the processed reads, hence I am having this error?
The error:
[RaconWrapper::run] preparing data with rampler
[RaconWrapper::run] total number of splits: 23
[RaconWrapper::run] processing data with racon
[racon::Polisher::initialize] loaded target sequences 0.619989 s
[racon::Polisher::initialize] loaded sequences 8.035806 s
[racon::Polisher::initialize] loaded overlaps 50.450574 s
[racon::Overlap::find_breaking_points] error: overlap is not transmuted!
I saw someone commented that this issue would come up with 4 out of more than 200 assemblies using racon. What could be the reason why this error is happening?
Thank you!

I tried racon with a subsample of the reads and a subsample of the assembly fasta, I also renamed the contigs without white spaces (just the number) and it worked....
works for the sub-samples but not with whole data?
    $ racon test2.reads.fasta test2.overlap.paf test2.fasta > test2.racon.fasta
    [racon::Polisher::initialize] loaded target sequences 1.130559 s
    [racon::Polisher::initialize] loaded sequences 0.000698 s
    [racon::Polisher::initialize] loaded overlaps 0.000076 s
    [racon::Polisher::initialize] aligned overlaps 0.052002 s
    [racon::Polisher::initialize] transformed data into windows 0.116028 s
    [racon::Polisher::polish] generating consensus [====================] 1.039283 s
    [racon::Polisher::] total = 2.832840 s

Hello,
can you please try the latest version from https://github.com/lbcb-sci/racon?
Best regards,
Robert

Hi Robert,
Thank you for replying.
this is the error I got for bioconda Raconv1.5.0
[RaconWrapper::run] preparing data with rampler
[RaconWrapper::run] error: unable to run rampler!
I do not have this error for v1.4.20
(I'll just mention this 81 issue, since it's the same.)

Just an update in case some others have the same problem as mine.
I ran Racon with four data: 2 PacBio CLR reads and 2 from ONT reads to correct a two ONT-assembled fasta (haplotype-resolved). I was able to successfully run 1 ONT reads, however, not for the other 3 reads...

Hi, mentioning in case someone comes across this. I had this same error happen and found out it was a mis-match between the alignment fasta headers and the fasta I provided as the input.
I was splitting the input fasta file based on bed coordinates (basically, doing a manual parallel process as I can't install the wrapper script on my compute cluster) and found out that extraction tools using bed format (eg seqtk subseq or bedtools getfasta) will change the fasta header to include the coordinates if provided in a bed file.
Eg:
>contig1
ATCGACG...
>contig2
AGTCAGC...
bed file:
contig1 1 60000
seqtk subseq $fasta $bed > output.fasta
becomes:
>contig1:1-600000
ATCGACG...
Potentially an error message specifically identifying the mis-matched headers might be useful?


Example code doesn't work, and i get an error while trying to backup

Hi,
After finally getting the package to work(created a package.json and includdes full path to mjs in import) :) i got the following error :( database is around 30GB :)
---> Restoration started from <---  snapshot1.txt
(node:48038) UnhandledPromiseRejectionWarning: RangeError [ERR_FS_FILE_TOO_LARGE]: File size<PHONE_NUMBER>8) is greater than possible Buffer:<PHONE_NUMBER> bytes
at tryCreateBuffer (fs.js:339:13)
at readFileSync (fs.js:375:14)
at backup (file:///home/user/node_modules/sqlite3-incremental-backup/sqlite3-incremental-backup.mjs:28:21)
at file:///home/user/sync.js:6:1
at ModuleJob.run (internal/modules/esm/module_job.js:145:37)
at async Loader.import (internal/modules/esm/loader.js:182:24)
at async Object.loadESM (internal/process/esm_loader.js:68:5)
(node:48038) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:48038) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
(node:48038) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, open 'snapshot1.txt'
at Object.openSync (fs.js:462:3)
at readFileSync (fs.js:364:35)
at restore (file:///home/user/node_modules/sqlite3-incremental-backup/sqlite3-incremental-backup.mjs:66:19)
at file:///home/user/sync.js:7:1
at ModuleJob.run (internal/modules/esm/module_job.js:145:37)
at async Loader.import (internal/modules/esm/loader.js:182:24)
at async Object.loadESM (internal/process/esm_loader.js:68:5)
(node:48038) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)

I'm sorry but it feels all to unstable to test, it seems a good solution for incremental backups but it doesn't feel robust, like the filename for the snapshot is snapshot1.txt with a comment that it should be changed every time.... i think there should be a random filename or incremental filename and the restore function should restore the incrementals by order or something. I don't understand your code exactly so maybe ill digg in or try another solution.

@WebWire-NL  Okay, thanks for your support. Actually, these were meant to work with scripts i.e cronjob/background_process which would run the backup periodically (So, I make the snapshot option should be on your choice may be timestamp-based or incremental based). And I think you did not grab the concept of database incremental backup. Each snapshot file (not the objects file) is independent of each other. I mean if you delete all the snapshots but a single one, you can restore the whole database. Yes, it may seem like a lot of files in a lot of folders because it is splitting your database into chunks and backing up all of them. After any modification to the database, the backing up process will backup the chunk only which was actually modified, thus saving a lot of storage. I think my current implementations only work with local files (Because all the object files must be present during restoration). I implemented timestamp-based naming on snapshot name during backup but you must provide the snapshot name to be restored. Whenever you need your database to go on a specific (past) state, provide that snapshot name on the restore function. Check for the latest commit.
Note: As per your requirements, you need to sync your database to the remote. Then I think the following workflow would do the case:

back up your database with a constant snapshot name (maybe snapshot.txt), which will overwrite the previous each time you run the backup. (on source machine)
Collect all the object files and the snapshot file from the source machine to your target machine (It could be done by my library, but I do not want the library to have dependencies other than standard ones, but I may give a shot if I get chance)
restore the current state by providing the snapshot file name you have given in step 1 (on target machine)
I think it may give you a rough idea of how the implementation may work. Hope you all the best.


又关机了，于是又重新开电脑，然后这次变成这样了……

WARNING: brevent on Android 5.X - 6.0 is experimental!!!
checking for server.......fail
[command] pm path me.piebridge.brevent
package:/data/app/me.piebridge.brevent-2/base.apk
please report bug to https://github.com/brevent/Brevent/issues with log below
--- crash start ---
[command] logcat -b crash -t '04-28 16:07:06.000' -d
--- crash end ---
--- brevent start ---
[command] logcat -b main -t '04-28 16:07:06.000' -d -s BreventLoader BreventServer
04-28 16:07:11.442 24792 24792 I BreventLoader: line: package:/data/app/me.piebridge.brevent-2/base.apk
04-28 16:07:11.640 24792 24792 I BreventLoader: loader path: /data/app/me.piebridge.brevent-2/base.apk
04-28 16:07:11.643 24819 24819 I BreventLoader: start:<PHONE_NUMBER>
04-28 16:07:17.165 24819 24819 I BreventServer: args: [10, me.piebridge.brevent,<PHONE_NUMBER>]
--- brevent end ---

please report bug to https://github.com/brevent/Brevent/issues with log above

请从官方站点下载黑阈，然后再看：https://jianyu.io/brevent