[BUG] OSB doesn't show benchmark progress on stdout

Describe the bug
Opensearch benchmark doesn't show which test-procedure its executing and what's the progress on it on stdout. Initially, it prints the usual design of Opensearch benchmark on the terminal but then doesn't print anything afterwards. Although, by monitoring logs we can see that the benchmark is running.
Just this gets printed

To Reproduce

Install osb 1.1.0 version
Set benchmark.ini file as

config.version = 17

[system]
env.name = local

[node]
root.dir = /home/ec2-user/.benchmark/benchmarks
src.root.dir = /home/ec2-user/.benchmark/benchmarks/src

[source]
remote.repo.url = https://github.com/opensearch-project/OpenSearch.git
opensearch.src.subdir = opensearch

[benchmarks]
local.dataset.cache = /home/ec2-user/.benchmark/benchmarks/data

[results_publishing]
datastore.type = opensearch
datastore.host = <IP>
datastore.port = 443
datastore.secure = True
datastore.user = <user>
datastore.password = <password>
datastore.ssl.verification_mode = none

[workloads]
default.url = https://github.com/opensearch-project/opensearch-benchmark-workloads

[provision_configs]
default.dir = default-provision-config

[defaults]
preserve_benchmark_candidate = false

[distributions]
release.cache = true

Run any benchmark. eg. command

opensearch-benchmark execute-test --pipeline="benchmark-only" --workload-path="/home/ec2-user/.benchmark/benchmarks/data/so" --test-execution-id="so_flush_false_ingest_2_parallel_5per_1" --target-hosts="<DNS>" --client-options="basic_auth_user:'<user>',basic_auth_password:'<passwd>',timeout:60" --telemetry-params='telemetry-params.json' --telemetry="node-stats,segment-stats"  --workload-params="number_of_shards:5,number_of_replicas:0,bulk_size:4000,bulk_indexing_clients:2,ingest_percentage:5" --distribution-version="2.3.0" --results-format csv --results-file ~/so_flush_update_false_ingest_2_parallel_5per --user-tag "intention:so-flush-false" --kill-running-processes"

Expected behavior
Expected that osb shows benchmark progress on stdout
More Context (please complete the following information):

Workload: nyc_taxis
Service: Opensearch
Version: 1.1.0

Hi @CaptainDredge, thanks for bringing this to our attention. To help us understand the situation better, could you address these follow-up questions:

To see if this is an issue with --kill-running-processes, could you run ps aux | grep opensearch-benchmark and ensure there are no lingering PIDs before running a test? In the past, when users encountered "OpenSearch Benchmark" logo without the progress in the stdout, it was caused be lingering processes for a previous run. Many users saw this despite appending --kill-running-processes in their commands. However, this shouldn't happen anymore since we introduced a fix for this a while back.
Have you tried this on OSB 1.2.0 or 1.0.0? Curious to see if it's isolated to the version you're running on.

To see if this is an issue with --kill-running-processes, could you run ps aux | grep opensearch-benchmark and ensure there are no lingering PIDs before running a test? In the past, when users encountered "OpenSearch Benchmark" logo without the progress in the stdout, it was caused be lingering processes for a previous run. Many users saw this despite appending --kill-running-processes in their commands. However, this shouldn't happen anymore since we introduced a fix for this a while back.

Yes @IanHoang there were lingering osb process. Once I killed them manually progress started coming on stdout. So essentially --kill-running-processes isn't working as expected. Can you point me to the fix for this?

Have you tried this on OSB 1.2.0 or 1.0.0? Curious to see if it's isolated to the version you're running on.

I tested it on 0.1 and 1.1 and it happens on both. I don't have the setup to test for different versions

Could you provide the exact command you’re running ? When you curl the cluster, are you seeing docs actually being ingested? When you check ~/.benchmark/logs/benchmark.log are you seeing the operations being run?
Ran a few tests recently on OSB 1.2.0 and on OSB 1.1.0 but am seeing progress and output:
   ____                  _____                      __       ____                  __                         __
  / __ \____  ___  ____ / ___/___  ____ ___________/ /_     / __ )___  ____  _____/ /_  ____ ___  ____ ______/ /__
 / / / / __ \/ _ \/ __ \\__ \/ _ \/ __ `/ ___/ ___/ __ \   / __  / _ \/ __ \/ ___/ __ \/ __ `__ \/ __ `/ ___/ //_/
/ /_/ / /_/ /  __/ / / /__/ /  __/ /_/ / /  / /__/ / / /  / /_/ /  __/ / / / /__/ / / / / / / / / /_/ / /  / ,<
\____/ .___/\___/_/ /_/____/\___/\__,_/_/   \___/_/ /_/  /_____/\___/_/ /_/\___/_/ /_/_/ /_/ /_/\__,_/_/  /_/|_|
    /_/

[INFO] You did not provide an explicit timeout in the client options. Assuming default of 10 seconds.
[INFO] Executing test with workload [movies-new], test_procedure [default-test-procedure] and provision_config_instance ['external'] with version [2.5.0].

Running delete-index                                                           [100% done]
Running create-index                                                           [100% done]
Running cluster-health                                                         [100% done]
Running index-append                                                           [100% done]
Running refresh-after-index                                                    [100% done]
Running default                                                                [100% done]

------------------------------------------------------
    _______             __   _____
   / ____(_)___  ____ _/ /  / ___/_________  ________
  / /_  / / __ \/ __ `/ /   \__ \/ ___/ __ \/ ___/ _ \
 / __/ / / / / / /_/ / /   ___/ / /__/ /_/ / /  /  __/
/_/   /_/_/ /_/\__,_/_/   /____/\___/\____/_/   \___/
------------------------------------------------------

|                                                         Metric |         Task |       Value |   Unit |
|---------------------------------------------------------------:|-------------:|------------:|-------:|
|                     Cumulative indexing time of primary shards |              |     2.62908 |    min |
|             Min cumulative indexing time across primary shards |              |           0 |    min |
|          Median cumulative indexing time across primary shards |              | 0.000891667 |    min |
|             Max cumulative indexing time across primary shards |              |      0.5247 |    min |
|            Cumulative indexing throttle time of primary shards |              |           0 |    min |
|    Min cumulative indexing throttle time across primary shards |              |           0 |    min |
| Median cumulative indexing throttle time across primary shards |              |           0 |    min |
|    Max cumulative indexing throttle time across primary shards |              |           0 |    min |
|                        Cumulative merge time of primary shards |              |   0.0424667 |    min |
|                       Cumulative merge count of primary shards |              |          12 |        |
|                Min cumulative merge time across primary shards |              |           0 |    min |
|             Median cumulative merge time across primary shards |              |           0 |    min |
|                Max cumulative merge time across primary shards |              |   0.0108167 |    min |
|               Cumulative merge throttle time of primary shards |              |           0 |    min |
|       Min cumulative merge throttle time across primary shards |              |           0 |    min |
|    Median cumulative merge throttle time across primary shards |              |           0 |    min |
|       Max cumulative merge throttle time across primary shards |              |           0 |    min |
|                      Cumulative refresh time of primary shards |              |    0.259283 |    min |
|                     Cumulative refresh count of primary shards |              |         927 |        |
|              Min cumulative refresh time across primary shards |              |           0 |    min |
|           Median cumulative refresh time across primary shards |              | 0.000266667 |    min |
|              Max cumulative refresh time across primary shards |              |   0.0418833 |    min |
|                        Cumulative flush time of primary shards |              |     0.00195 |    min |
|                       Cumulative flush count of primary shards |              |          28 |        |
|                Min cumulative flush time across primary shards |              |           0 |    min |
|             Median cumulative flush time across primary shards |              |           0 |    min |
|                Max cumulative flush time across primary shards |              |     0.00195 |    min |
|                                        Total Young Gen GC time |              |           0 |      s |
|                                       Total Young Gen GC count |              |           0 |        |
|                                          Total Old Gen GC time |              |           0 |      s |
|                                         Total Old Gen GC count |              |           0 |        |
|                                                     Store size |              |    0.149794 |     GB |
|                                                  Translog size |              | 0.000391557 |     GB |
|                                         Heap used for segments |              |           0 |     MB |
|                                       Heap used for doc values |              |           0 |     MB |
|                                            Heap used for terms |              |           0 |     MB |
|                                            Heap used for norms |              |           0 |     MB |
|                                           Heap used for points |              |           0 |     MB |
|                                    Heap used for stored fields |              |           0 |     MB |
|                                                  Segment count |              |          75 |        |
|                                                 Min Throughput | index-append |     2645.87 | docs/s |
|                                                Mean Throughput | index-append |     2645.87 | docs/s |
|                                              Median Throughput | index-append |     2645.87 | docs/s |
|                                                 Max Throughput | index-append |     2645.87 | docs/s |
|                                        50th percentile latency | index-append |     334.671 |     ms |
|                                       100th percentile latency | index-append |     347.148 |     ms |
|                                   50th percentile service time | index-append |     334.671 |     ms |
|                                  100th percentile service time | index-append |     347.148 |     ms |
|                                                     error rate | index-append |           0 |      % |
|                                                 Min Throughput |      default |        4.09 |  ops/s |
|                                                Mean Throughput |      default |        4.09 |  ops/s |
|                                              Median Throughput |      default |        4.09 |  ops/s |
|                                                 Max Throughput |      default |        4.09 |  ops/s |
|                                       100th percentile latency |      default |     449.604 |     ms |
|                                  100th percentile service time |      default |     204.521 |     ms |
|                                                     error rate |      default |           0 |      % |

--------------------------------
[INFO] SUCCESS (took 21 seconds)

This is likely fixed in OSB 1.2 with the following commit.  The setup for 1.2 should be no different than that for earlier versions.
2023-11-03 00:04:20 -0700  a0adc906  Govind Kamat
Fix the predicate used for the --kill-running-processes flag.


Add support for Gemini

Feature request
hello, thanks very much for the package. can the support of Gemini be supported please. compared to vertexAi, it only requires an api key.
Motivation
vertexAi requires paid services to set up, while gemini currently has free tier, would be good to have support.
Your contribution
here is a package: https://github.com/babakcode/flutter_gemini, but it does not support langchain pipeline.

Hello @quanshuli ,
We already have support for Gemini, you can find it in the langchain_google package.
Check out the docs: https://langchaindart.com/#/modules/model_io/models/chat_models/integrations/googleai


Stats should respect opts.bigint = false

This issue affects v. 3.1.1 on Windows.
If I call readdirp with opts.bigint = false, it fixes a number of these errors:
TypeError: Cannot mix BigInt and other types, use explicit conversions
However, this line overwrites opts.bigint and forces it to true on Windows:
https://github.com/paulmillr/readdirp/blob/master/index.js#L96
That results in TypeErrors every time my code stats a file on Windows. Seems like opts.bigint should apply consistently. Also, the options section of the README should mention that bigint is now an option, if it was meant to be a publicly exposed option. Maybe it's not, and I'm misusing the package.

That was not meant to be exposed as an option, I didn’t want to add complexity. Maybe we should.

That's fair, since it wasn't actually documented. For now, I've changed all instances of stats.size to Number(stats.size). So at this point, it's not a major issue for me. You might want to consider it if you get complaints about the break in backwards compatibility.

Using the bigint version of stats can break other things too since bigint doesn't yet seem to be fully supported. For example, moving from v2 to v3 started generating TypeError: Do not know how to serialize a BigInt errors in Node-RED.
This should absolutely be an option please. As a workaround, I've also had to wrap size, uid and gid with Number(...).

bigint doesn't yet seem to be fully supported

Just want to clarify: it is supported in node 10 and higher. Node 8 will become unsupported in 3 months, on Jan 1, 2020. Chokidar / readdirp itself support node 8.16+.

will do that in v5 which will bump min nodejs to v18, which supports mtimeNs


Code generator does not ignore accessor in super interface

UnimplementedError
package:isar_generator/src/isar_type.dart 82:11             DartTypeX.isarType
package:isar_generator/src/isar_analyzer.dart 274:20        IsarAnalyzer.analyzeObjectProperty
package:isar_generator/src/isar_analyzer.dart 23:26         IsarAnalyzer.analyzeCollection
package:isar_generator/src/collection_generator.dart 46:35  IsarCollectionGenerator.generateForAnnotatedElement
package:source_gen/src/generator_for_annotation.dart 53:30  GeneratorForAnnotation.generate
package:source_gen/src/builder.dart 352:33                  _generate

Steps to Reproduce
Try to generate code for this file:
import 'package:isar/isar.dart';

part 'a.g.dart';

abstract class IA {
  List<B> get b;
}

@Collection()
class A implements IA {
  A();

  late Id id = Isar.autoIncrement;

  @ignore
  @override
  List<B> get b => [];
}

class B {}

If A does not implement IA b is correctly ignored.
Details

Isar version: 3.0.0-dev.14

[x] I searched for similar issues already
[x] I filled the details section with the exact device model and version
[x] I am able to provide a reproducible example

Could you please try using the new ignore parameter of @Collection()

Thanks, Collection.ignore works. Is @Ignore going to be removed?

No but I think the current behaviour is good. @ignore ignores only the property in the current class and @Collection(ignore) ignores all properties with that name. Going to close this issue.


NIFI-11587: update questdb from 6.5.5-jdk8 to 6.7-jdk8

Summary
NIFI-00000
Tracking
Please complete the following tracking steps prior to pull request creation.
Issue Tracking

[ ] Apache NiFi Jira issue created

Pull Request Tracking

[ ] Pull Request title starts with Apache NiFi Jira issue number, such as NIFI-00000
[ ] Pull Request commit message starts with Apache NiFi Jira issue number, as such NIFI-00000

Pull Request Formatting

[ ] Pull Request based on current revision of the main branch
[ ] Pull Request refers to a feature branch with one commit containing changes

Verification
Please indicate the verification steps performed prior to pull request creation.
Build

[ ] Build completed using mvn clean install -P contrib-check

[ ] JDK 11
[ ] JDK 17

Licensing

[ ] New dependencies are compatible with the Apache License 2.0 according to the License Policy
[ ] New dependencies are documented in applicable LICENSE and NOTICE files

Documentation

[ ] Documentation formatting appears as expected in rendered files

@r-sidd Thank you for the contribution. Incremental changes do not necessarily require code changes, but sometimes libraries change behavior. Unfortunately it appears that this is one of those instances.
Please run a full local build of the project at minimum before submitting a pull request, as that surfaces some code changes required. For further background, please review Managing Project Dependencies for recommended steps related to upgrading dependencies.
I am closing this pull request for now given the automated build failures, but if you have a successful build and confirm the required changes, feel free to reopen or submit a new PR.


[e2e]: generic schedule main attestation-name slsa3

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/3662378914
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.generic.schedule.main.attestation-name.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.generic.schedule.main.attestation-name.slsa3.yml
Trigger: schedule
Branch: main
Date: Sat Dec 10 03:10:49 UTC 2022

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/3667147848
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.generic.schedule.main.attestation-name.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.generic.schedule.main.attestation-name.slsa3.yml
Trigger: schedule
Branch: main
Date: Sun Dec 11 03:17:21 UTC 2022

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/3677963486
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.generic.schedule.main.attestation-name.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.generic.schedule.main.attestation-name.slsa3.yml
Trigger: workflow_dispatch
Branch: main
Date: Mon Dec 12 17:03:20 UTC 2022
Tests are passing now. Closing this issue.


[stable/traefik] Minimize downtime during deploy

What this PR does / why we need it:
Traefik currently become unresponsive for around 20-25 seconds whenever an upgrade of a deployment is made. This change mitigates this by keeping the existing pod around until the new pod reports as being healthy.
There’s still be around 5-10 seconds of downtime, perhaps because of how the probes are set up. But definitely an improvement.
NOTE: Hasn't been tested with multiple replicas.
@krancour @emilevauge @dtomcej @ldez

/assign @krancour

Wondering if someone who has broader experience maintaining multiple charts in this repo can suggest whether there's a canonical way of dealing with this concern. I can imagine, for instance, that it might be better to let the deployment strategy be configured through a chunk of raw YAML (as many other charts do for things like probes). What are other charts doing vis-a-vis deployment strategy?
cc @prydonius @viglesiasce @mattfarina @unguiculus any input?

@krancour I tend to agree with you. In any case, it should be configurable.

@krancour @unguiculus Thanks for the input, much better solution IMO. I've updated the PR accordingly.

@jmagnusson nice improvements. Thanks.

@krancour Thanks for your comments. Any change we can get this merged?

/ok-to-test

/lgtm


Adding sakugabooru to list of websites

Is it possible to add sakugabooru to list of usable websites? Sorry, new to using tool and was trying to get an artbook pool from there.

nevermind, i figured it all out 😄


Adding Request AdvertisingFlags

Please check all of the platforms you are having the issue on (if platform is not listed, it is not supported)

[x] iOS
[x] Android
[] tvOS
[] macOS
[] .NET Standard
UWP IS NOT SUPPORTED DURING THE BETA PERIOD - ONLY PRs ARE WELCOME FOR NOW

Dear Aritchie. Thanks for this nice Plugin.
I have a simple addition to your ScanResult.
Within the Bluetooth SIG there are AdvertisingFlags which will let the App know if the currently scanned device is advertising globally or not (LE General Discoverable Mode) and some nice to have information as well.
Is it possible to add these Flags to your current ScanResult struct?
sincerly
Markus

On android, I do supply a lot of the flags.  On iOS, most them are flat out blocked.  Not sure about UWP.


A problem was encountered while "catkin_make" in the workspace"catkin_ws"

In file included from /home/dayna/catkin_ws/src/Compliant-Control-and-Application-noetic/control_algorithms/admittance/src/HybridAdmittance/HybridAdmittance.cpp:1:
/home/dayna/catkin_ws/src/Compliant-Control-and-Application-noetic/control_algorithms/admittance/include/hybridadmittance/HybridAdmittance.h:6:10: fatal error: cartesian_state_msgs/PoseTwist.h: 没有那个文件或目录
6 | #include "cartesian_state_msgs/PoseTwist.h"
|          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
In file included from /home/dayna/catkin_ws/src/Compliant-Control-and-Application-noetic/control_strategy/src/control_strategy/control_strategy.cpp:1:
/home/dayna/catkin_ws/src/Compliant-Control-and-Application-noetic/control_strategy/include/control_strategy/control_strategy.h:11:10: fatal error: cartesian_state_msgs/PoseTwist.h: 没有那个文件或目录
11 | #include "cartesian_state_msgs/PoseTwist.h"
|          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
make[2]: *** [Compliant-Control-and-Application-noetic/control_algorithms/admittance/CMakeFiles/hybridadmittance.dir/build.make:63：Compliant-Control-and-Application-noetic/control_algorithms/admittance/CMakeFiles/hybridadmittance.dir/src/HybridAdmittance/HybridAdmittance.cpp.o] 错误 1
make[2]: *** [Compliant-Control-and-Application-noetic/control_strategy/CMakeFiles/control_strategy.dir/build.make:63：Compliant-Control-and-Application-noetic/control_strategy/CMakeFiles/control_strategy.dir/src/control_strategy/control_strategy.cpp.o] 错误 1
make[1]: *** [CMakeFiles/Makefile2:7219：Compliant-Control-and-Application-noetic/control_strategy/CMakeFiles/control_strategy.dir/all] 错误 2
make[1]: *** 正在等待未完成的任务....
make[1]: *** [CMakeFiles/Makefile2:8657：Compliant-Control-and-Application-noetic/control_algorithms/admittance/CMakeFiles/hybridadmittance.dir/all] 错误 2
make: *** [Makefile:141：all] 错误 2
Invoking "make -j2 -l2" failed

Please refer this answer

Please refer this answer

thanks!

@daynad  did you solve this?


Epic: Green City Events

Status:
B - in progress, back
BD - done, back
F - in progress, front
FD - done, front
T - in progress, testing
Done  - US is done

RELEVANT user story list:

1. Feature: Events

№
User story
Link
Status
MVP

1
Create event
#3193 #4231 #4232 #5123 #6359 #6361

2
Edit event
#3195 #5146

3
Delete event
#3196 #6181

4
Event dashboard
#3197 #4907

5
Add event comment
#3208 #4665 #5490

6
Delete comment
#3209 #5147

7
Edit comment
#3210 #5153

8
Reply on comment
#3211 #5145

9
Events filter
#3266 #5007

10
Search event
#3267 #5005

11
Event organizer rating
#3268 #4696 #5066

12
Event attendance
#3270 #6157 #6222

13
Manage event location
#3373 #5394

14
View event preview card
#3374 #5006

15
View my events
#3375

16
Tagging in reply on comment
#4701

NOT RELEVANT user story list: -

Epic list: #3194

Status: B - in progress, back BD - done, back F - in progress, front FD - done, front T - in progress, testing Done - US is done

RELEVANT user story list:

1. Feature: Events
№	User story	Link	Status	MVP
1	Create event	#3193 #4231 #4232 #5123 #6359 #6361
2	Edit event	#3195 #5146
3	Delete event	#3196 #6181
4	Event dashboard	#3197 #4907
5	Add event comment	#3208 #4665 #5490
6	Delete comment	#3209 #5147
7	Edit comment	#3210 #5153
8	Reply on comment	#3211 #5145
9	Events filter	#3266 #5007
10	Search event	#3267 #5005
11	Event organizer rating	#3268 #4696 #5066
12	Event attendance	#3270 #6157 #6222
13	Manage event location	#3373 #5394
14	View event preview card	#3374 #5006
15	View my events	#3375
16	Tagging in reply on comment	#4701

NOT RELEVANT user story list: -

Epic list: #3194


how to get user email id?

I am getting user basic profile  by 'https://api.linkedin.com/v1/people/' but how can i get user email id ?

Default permission array of the library is ['r_basicprofile', 'r_emailaddress'] so you probably just need to change your Default Application Permissions settings in LinkedIn developer console like below.


shell r3 commands should take the profile into account

When performing r3 commands such as r3:do(compile) in the shell, the profile should should be taken into account.
How to reproduce:
1.
Add a second apps directory (in my specific use case that contains apps with code for interactive testing) to a profile, here's the relevant entries in my rebar.config:
{profiles, [{test, [{project_app_dirs, ["apps", "test"]} ] }]}

2
$ rebar3 as test shell

Result (as expected):
Compiles all apps in "apps" and "test" and starts the shell
3
>  r3:do(compile).

Result:
Only apps in "apps" are compiled
Expected:
Apps in the directories "apps" and "test" are compiled
Rebar3 report
 version 3.0.0-beta-1
 generated at 2015-07-01T10:53:29+00:00
=================
-----------------
Operating System: x86_64-apple-darwin14.3.0
ERTS: Erlang/OTP 17 [erts-6.4.1] [source] [64-bit] [smp:4:4] [async-threads:0] [hipe] [kernel-poll:false]
Root Directory: <redacted>
Library directory: <redacted>
-----------------
Loaded Applications:
bbmustache: 1.0.1
common_test: 1.10.1
compiler: 5.0.4
crypto: 3.5
erlware_commons: 0.12.0
eunit: 2.2.9
inets: 5.10.9
kernel: 3.2
providers: 1.4.1
relx: 3.0.0
sasl: 2.4.1
stdlib: 2.4
syntax_tools: 1.6.18
tools: 2.7.2

-----------------
Escript path: /opt/bin/rebar3
Providers:
  app_discovery as clean compile cover ct deps dialyzer do edoc escriptize eunit help install_deps list lock new pkgs release relup report shell tar unlock update upgrade upgrade version xref

Yeah that's a bug. I believe I tried to keep that working but obviously failed at it.

Please try https://github.com/rebar/rebar3/pull/577. Also if test/ contains modules instead of apps, you'll need to change the config to {profiles, [{test, [{extra_src_dirs, ["test"]} ] }]} but I don't think this would apply there specifically as you obviously said "apps".

Yes, this solves my problem, thanks!


webassemblyjs tool suite: init at 1.7.8

Motivation for this change
Couldn't test wasmrun for not having a WASM file that can be run at hand, but it looks like it's at least basically working :)
All other binaries are either OK or had bugs reported upstream because they really didn't look like packaging issues.
Things done

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

[x] NixOS
[ ] 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 nox --run "nox-review wip"
[x] 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] Fits CONTRIBUTING.md.

For ease of review: the operations done for this PR are addition of the lines in all-packages.nix and node-packages-v6.json, and running ./generate.sh.

Intuitively the HTTPS isn't that important, though, as it's going to (I guess) be built by hydra, which has no need for confidentiality, and it's protected by sha*sum anyway :)

@Ekleog Well the hashes were probably obtained from the http URL to begin with

Indeed, but HTTPS more or less only tells that some third-party over the internet saw you over a HTTP connection (at least with Let's Encrypt, some other CAs have different requirements), so basically what we're doing by pinning hashes and making contributor+ofborg review them is basically as secure as HTTPS, with the exception that there's no Certificate Transparency logs for hashes we insert :)
Anyway, thank you for the review!


Handling Parallel Notifications from Multiple Bluetooth Devices in Real-Time

Prerequisites

[X] I checked the documentation and FAQ without finding a solution
[X] I checked to make sure that this issue has not already been filed
[X] I'm sure that question is related to the library itself and not Bluetooth Low Energy or Classic in general. If that so, please post your question on StackOverflow.
[X] I'm running the latest version

Question
Hi,
I am connected to two devices and subscribed to their notifications simultaneously. However, I'm currently only receiving notifications from one device at a time. I need to receive data from both devices in parallel. Is this possible? If so, please share the solution here.
Question related code
No response

@viswa-capgemini I'm using this library and success to connect 2 devices at the same time and subscribe multiple chs.
I also experienced the same issue with yours, the solution that I applied in my project: make sure the transaction id is unique for a device and a characteristics.

hello @viswa-capgemini have subscribed to multiple services from multiple devices?

I am connecting to multiple devices simultaneously that share the same service UUID and characteristic ID and retrieving data from each device through notifications in parallel. The issue I'm facing is that I'm only able to receive data from one device at a time. I will try with @perifit solution and update the result. Thanks

@viswa-capgemini I'm using this library and success to connect 2 devices at the same time and subscribe multiple chs. I also experienced the same issue with yours, the solution that I applied in my project: make sure the transaction id is unique for a device and a characteristics.

Hi @perifit, Thank you for the suggestion! I'll give it a try and will let you know the results.

@viswa-capgemini are you having multiple service UUID? for example`const monitorMultipleCharacteristics = async () => { try {
  const monitorPromises = uuids.map(({ serviceUUID, characteristicUUID }) => {

    return new Promise((resolve, reject) => {
      BLEService.monitorCharacteristicForDevice(
        serviceUUID,
        characteristicUUID,
        async data => {

            case UUID:
              const temperature = parse(data.value)
              break

            case UUID:
              console.log('dispatch service')
              break

            default:
              console.log('Unknown UUID', data.uuid)
          }
          setTimeout(resolve, 100, data)
          console.info('success', new Date().getTime())
        },
        async error => {
          console.error(error)
          await BLEService.finishMonitor()
          reject()
        }
      )
      // Store the subscription so it can be cleaned up later
      //subscriptions.push(subscription)
    })

    // Wait for each monitor to be set up
  })

  Promise.all(monitorPromises)
    .then(data => {
      console.log(data)
    })
    .catch(error => {
      console.error('Error in one of the monitors:', error)
    })
} catch (error) {
  console.error('Error setting up characteristic monitoring:', error)
}

// Optionally return the subscriptions if you need to stop monitoring later
//return subscriptions

}`

@smitha-2020, In my case we have specified with single serviceUUID, characteristicsUUID. In that case 2 devices have same UUID's. Adding to this, we are subscribing notifications for one particular serviceUUID.

@viswa-capgemini How are you subscribing to notifications? is it using monitorCharacteristicForDevice?

@smitha-2020. Yes I am using it
const enableNotifications = async () => {
sub = manager.monitorCharacteristicForDevice(
deviceID,
serviceUUID,
notificationUUID,
handleNotificationData
);
}


[CxxInterop] Import C++ references.

This PR enables import of C++ references as UnsafePointers. PR follows the implementation of pointers with a difference that for references we don't wrap the UnsafePointer in Optional.

@swift-ci Please test

@swift-ci Please test

@swift-ci Please test

@swift-ci Please test

Build failed
Swift Test OS X Platform
Git Sha - 5a7b16825e573255ca85601a6344a1b4d4571f94

Build failed
Swift Test Linux Platform
Git Sha - 5a7b16825e573255ca85601a6344a1b4d4571f94

@swift-ci please test Windows platform

@swift-ci please test Windows platform

@swift-ci Please test Windows

@swift-ci Please test

Build failed
Swift Test Linux Platform
Git Sha - 07a13c543da7c70778303672712a851e1306f29c

@swift-ci please test Windows platform

@swift-ci Please test macOS

@swift-ci Please test Windows

Build failed
Swift Test OS X Platform
Git Sha - 07a13c543da7c70778303672712a851e1306f29c

@swift-ci Please test Windows

Could you also adjust the incorrect comment in lib/ClangImporter/ImporterImpl.h:
  /// Import the type of a function parameter.
  ///
  /// This provides special treatment for C++ references (which become
  /// [inout] parameters) and C pointers (which become magic [inout]-able types),
  /// among other things, and enables the conversion of bridged types.
  /// Parameters are always considered CF-audited.
  Parameter,

(Adjusted the Parameter comment slightly).

@jenkins please test

@swift-ci Please test

Build failed
Swift Test Linux Platform
Git Sha - e0a23670cec7182d300344fa9302b84cf96ccf13

@swift-ci Please test

@swift-ci Please test macOS

@swift-ci Please test Windows

Build failed
Swift Test OS X Platform
Git Sha - e0a23670cec7182d300344fa9302b84cf96ccf13

@swift-ci Please test

@swift-ci Please test Windows

Build failed
Swift Test Linux Platform
Git Sha - f8d2be13274b238d8309f344c20fc89612f950c7

Build failed
Swift Test OS X Platform
Git Sha - 92d0b34c9c7f270462dd0e04de6b330356663034

@swift-ci Please test

@swift-ci Please test

Build failed
Swift Test OS X Platform
Git Sha - 92d0b34c9c7f270462dd0e04de6b330356663034

Build failed
Swift Test Linux Platform
Git Sha - 92d0b34c9c7f270462dd0e04de6b330356663034

@swift-ci Please test

@swift-ci Please test Windows

@swift-ci Please test Windows

Build failed
Swift Test Linux Platform
Git Sha - 662689af2524949774f11cdf56b36ad00dfa09e6

@swift-ci Please test Linux

This broke the Windows VS2017 builds: https://ci-external.swift.org/job/oss-swift-windows-x86_64/3976/consoleText

@compnerd just to double check I understand what happened, this PR passed the windows bot with MSVC19, but then failed on the bot with MSVC17, correct? Is it an option to have MSVC17 bot for presubmits too?

Correct, that’s what happened.  Sadly, I don’t think that adding VS2017 as presubmit is entirely viable (a matter of cost and effort).  For the most part it’s not been an issue - this breakage is the first in ~6 months that’s specific to VS2017.


Standard resonator data format

Hi all,
Due to community feedback about issues with fitting a variety of data formats, I went through the datasets we have so far and compiled guidelines for a standard data format. Going forward, we hope that everyone can share their data in the following format:
Three column .csv file starting in row 1, with no empty rows between data.
Data should be the raw data with no normalization or frequency shift.
Column 1:
Monotonically increasing frequency in GHz
Column 2:
Magnitude of S21 in dB (log mag)
Column 3:
Phase of S21 in radians
Other info to be included in a .txt accompanying the data (encouraged but not required):
Input power (dBm)
Number of averages
IFBW
Fridge temperature (mK)
Type of device (materials, design geometry, etc.)
Please let me know if you have any questions or feedback about the guidelines. We're still in the early stages of this effort so any comments would be very helpful.
The NIST and Google data should be in the correct format already, and the GitHub will be updated when other datasets are reformatted.
Thanks!

This is a great start to regularizing things.
The only suggestion I'd make is the accompanying text file use something like JSON or XML to make it easy to import from the code side of things.

So there's a standard adopted by Keysight that exists. Perhaps we should look at using that

All the spice simulators will import touchstone as does scikit-rf. So this
is a good idea.
On Fri, Feb 7, 2020, 16:25 Josh Mutus<EMAIL_ADDRESS>wrote:

So there's a standard adopted by Keysight that exists
https://ibis.org/connector/touchstone_spec11.pdf. Perhaps we should
look at using that
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Boulder-Cryogenic-Quantum-Testbed/measurement/issues/19?email_source=notifications&email_token=ACTQRRFNV6KHDIIHV2BODSLRBX3WTA5CNFSM4HJUOEBKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOELFCIVQ#issuecomment-583672918,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACTQRRGFIDZ7CUXAV6OSO6DRBX3WTANCNFSM4HJUOEBA
.

I agree, this looks great!
@mullinska let's implement the Keysight Touchstone format as the standard input for our code.

Great. I'm glad we could get that figured out. I'll get to work on updating this as soon as possible.

Hi guys, I just wanted to let you all know that I've encountered a bit of an issue with the Keysight format that we've discussed using. If you look at page 7 example 4 in the link that Josh posted above, you'll notice that the format includes data for S11, S21, S12 and S22 for a 2 port measurement instead of just the S21 that we care about. If we follow the format we would need to figure out some value to put in the columns for the other port combinations, or we could go against the format and only include the columns for S21 data. Of course there may be some other option I haven't listed as well. In any case it would be nice to discuss what to do about this so I can fully integrate it into the code. I've already finished the header reading section so data reading is all I really have left. Please let me know what you all think, thanks.

Can we fill the other columns with NaN? Does it have anything in the spec for missing data?

Hi @joshmutus , sorry for the late reply. I've looked through the touchstone file syntax and rules in detail. I can't find anything in the document about missing data, but it would appear that as long as we use ASCII characters in the standard range it should be fine. So just typing the letters "NaN" would work, however something like ASCII control character 0 (NULL) would not. There doesn't really appear to be a standard for missing data as far as I can see though. However, my question was more specific to file sizes. I wasn't sure if we needed to specify that every other column besides S21 is blank by putting something like NaN in, or whether we could just only include the column data for S21. After all, including column data for things we don't care about seems like a waste of file space to me, but I wanted to check to make sure.


grant permission over account error

Choose what to do:
1. New transaction (tx)
2. New query (qry)
3. New transaction status request (st)
> : 1
Forming a new transactions, choose command to add:
1. Detach role from account (detach)
2. Add new role to account (apnd_role)
3. Create new role (crt_role)
4. Set account key/value detail (set_acc_kv)
5. Transfer Assets (tran_ast)
6. Grant permission over your account (grant_perm)
7. Subtract Assets Quantity from Account (sub_ast_qty)
8. Set Account Quorum (set_qrm)
9. Remove Signatory (rem_sign)
10. Create Domain (crt_dmn)
11. Revoke permission from account (revoke_perm)
12. Create Account (crt_acc)
13. Add Signatory to Account (add_sign)
14. Create Asset (crt_ast)
15. Add Peer to Iroha Network (add_peer)
16. Add Asset Quantity (add_ast_qty)
0. Back (b)
> : 6
Account Id: test@test
Permission name: can_get_my_account
Command is formed. Choose what to do:
1. Add one more command to the transaction (add)
2. Send to Iroha peer (send)
3. Go back and start a new transaction (b)
4. Save as json file (save)
> : 2
Peer address (<IP_ADDRESS>): loclahost
Peer port (50051): 50051
terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<std::out_of_range> >'
  what():  bimap<>: invalid key
Aborted (core dumped)

In my code ,i input the same permission can_get_my_account,returned
Exception in thread "main" java.lang.IllegalArgumentException: 0 GrantPermission: [[Provided permission does not exist ]]

        at irohaJNI.ModelTransactionBuilder_build(Native Method)
        at ModelTransactionBuilder.build(ModelTransactionBuilder.java:118)
        at IrohaTransaction.cmdGrantPermission(IrohaTransaction.java:218)
        at IrohaApi.cmdGrantPermission(IrohaApi.java:385)
        at IrohaApi.cmdGrantPermission(IrohaApi.java:389)
        at test.main(test.java:11)

@big-fish0
Please note that permission can_get_my_account is not grantable. You should add it to the role and add role to an account.
http://iroha.readthedocs.io/en/latest/core_concepts/glossary.html#permission
Here is the list of all grantable permissions:
can_add_my_signatory
can_remove_my_signatory
can_set_my_quorum
can_set_my_account_detail
can_transfer_my_assets

Soon we will update our documentation and reflect it, so it is clear what you can grant directly and what you must add to a role.

@laSinteZ  But i change the permission to can_add_my_signatory,It returns the same error response
Choose what to do:
1. New transaction (tx)
2. New query (qry)
3. New transaction status request (st)
> : 1
Forming a new transactions, choose command to add:
1. Detach role from account (detach)
2. Add new role to account (apnd_role)
3. Create new role (crt_role)
4. Set account key/value detail (set_acc_kv)
5. Transfer Assets (tran_ast)
6. Grant permission over your account (grant_perm)
7. Subtract Assets Quantity from Account (sub_ast_qty)
8. Set Account Quorum (set_qrm)
9. Remove Signatory (rem_sign)
10. Create Domain (crt_dmn)
11. Revoke permission from account (revoke_perm)
12. Create Account (crt_acc)
13. Add Signatory to Account (add_sign)
14. Create Asset (crt_ast)
15. Add Peer to Iroha Network (add_peer)
16. Add Asset Quantity (add_ast_qty)
0. Back (b)
> : 6
Account Id: test@test
Permission name: can_add_my_signatory
Command is formed. Choose what to do:
1. Add one more command to the transaction (add)
2. Send to Iroha peer (send)
3. Go back and start a new transaction (b)
4. Save as json file (save)
> : 2
Peer address (<IP_ADDRESS>): localhost
Peer port (50051): 50051
terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<std::out_of_range> >'
  what():  bimap<>: invalid key
Aborted (core dumped)


Feature/auto conversion error

Implement a feature for handling auto-conversion output format error (-9)

also take a look at PyLint


page content

Hello!
Can you clarify one thing, if the content of index.html and static files is the same that is served by real SSRS installation or it is something that just visually looks like SSRS service?

It just visually looks like SSRS, as we cannot do a 1:1 copy due to legal concerns.


Error FINGERPRINT_DATA_NOT_DELETED

If no data was saved and I try to call second time delete() I got exception FINGERPRINT_DATA_NOT_DELETED.
https://github.com/mjwheatley/cordova-plugin-android-fingerprint-auth/blob/master/src/android/FingerprintAuth.java#L351-L371
In my case this is no error...
Can I ignore this error?

You are probably receiving that exception because there was no data found to be deleted.
Yes, you would be fine to ignore the exception and proceed.

Hallo @mjwheatley
In which case I can get this Exception?

The one you said you were receiving.


Deployment Configuration

This PR adds a new entity to the hydrosdk - DeploymentConfig. It is responsible for representing k8s settings of your servables.
DeploymentConfig encapsulates Container, Pod, Deployment and HPA settings. These settings are stored in similarly named dataclasses.  It was decided not to use kubernetes library with abstractions from k8s API due to their inflexibility in our case.
To create a new DeploymentConfig you can use the DeploymentConfigBuilder.
@enable_camel_case decorator adds an ability to convert dataclasses to/from a camel-cased dictionary for easier communication with the manager's API.
I've added a simple test suite to check reading from/to JSON and YAML.
This is still a draft PR and I'd be glad to receive input on the following issues:

Affinity class seems to have a lot of nested classes inside. Right now I've stopped at Pod/Node Affinity level. Do we need to add NodeSelector dataclass for matchExpression and matchLabels dictionaries?
Do we need to add any validation for deployment configuration parameters in the future?
What are the entities which will be coupled with a DeploymentConfig and hence should have a deployment_config as an attribute in their class definition? Servables only?
DeploymentConfig vs DeploymentConfiguration?

Example:
from hydrosdk import Cluster, DeploymentConfigBuilder
cluster = Cluster('http-cluster-endpoint')
config_builder = DeploymentConfigBuilder(name="new_config", cluster=cluster)
config = config_builder.with_hpa(max_replicas=10, min_replicas=2, target_cpu_utilization_percentage=80). \
                    with_pod_node_selector({"label1": "key1", "foo": "bar"}). \
                    with_resource_requirements(limits={"cpu": "4", "memory": "4g"}, \
                                               requests={"cpu": "2", "memory": "2g"}). \
                    with_replicas(replica_count=4). \
                    with_toleration(effect="PreferNoSchedule", key="equalToleration", toleration_seconds=30, operator="Exists").\
                    build()

Added datacclasses related to Affinity - NodeTerm, LabelSelector, etc.
Validation will be added in future
DeploymentConfiguration added to Servables and ModelVariants
DeploymentConfig renamed to DeploymentConfiguration

DeploymentConfig encapsulates Container, Pod, Deployment and HPA settings. These settings are stored in similarly named dataclasses. It was decided not to use kubernetes library with abstractions from k8s API due to their inflexibility in our case.

Can you elaborate on the inconvenience part?

DeploymentConfig encapsulates Container, Pod, Deployment and HPA settings. These settings are stored in similarly named dataclasses. It was decided not to use kubernetes library with abstractions from k8s API due to their inflexibility in our case.

Can you elaborate on the inconvenience part?

Sure,
The major blocker issue was that entities from kubernetes package have built-in validation for required fields. In our case, this is bothersome since we want to create configs without specifying resources to which they should be applied.
i.e. We can't create PodSpec from kubernetes package because we have to specify containers at PodSpec creation time. In our case we don't know that, so we can't create it.
Another issue is additional complexity connected to serialization from kubernetes objects to our /api/v2/deploymentConfiguration API


Prerequisite for an install could not be satisfied

I tried to download and install the package in the release page but i get the following error:

Version: https://github.com/microsoft/terminal/releases/tag/v0.3.2142.0

And btw, that package thing is really bad

error message non helpful AT ALL, at least in macOS i could check the log using a dedicated program

just an Install button, i guess to way to tell where to install it (diferent drive for example), at least in macOS i can choose the disk target

If copy macOS please do it right, not the broken linux way

Do note that you need a Windows 10 version 18362 otherwise the windows terminal may not be able to support.

Oh looks like i have: Microsoft Windows [Version 10.0.17763.557]
My bad!

Suggestion:
On that installation screen, requirments should be listed, otherwise you leave user in the smoke... this is part of bad UX on windows

It's actually stated in the Microsoft Store, I guess it wasn't visible after all!

UX is bad, there is no color other than (white/black/blue) wtf
Wrong version message should be more VISIBLE than anything else, this is the main problem, but it is displayed like a normal text..

Ermm I set my laptop to dark mode....

@bitcrazed Can you follow up with the Store team and/or the ADEX/APT/whatever-their-acronym-is-now team on this? There's two main things that need polish here:

If you're trying to install and app from the store and don't have a high enough Windows version installed, that's not clearly highlighted enough. This should go to the store team
If you're trying to sideload a package and don't have a high enough Windows version installed, the error message is not clear enough (when it definitely could be). This should go to the ADEX team


rtsp support

catt is a gem! thx a lot.
I will use it in my home automation. I am using Home Assistant maybe I will try to integrate catt with it, with a customs component or addon.
I able to cast video from  "Android IP Webcam app", with the build-in webserver in the app. Great!
I have others cam, streaming RTSP flux. I try to cast it, but i got this error
ERROR: Unable to download webpage: <urlopen error unknown url type: rtsp> (caused by URLError('unknown url type: rtsp',))
The flux should be convert in a format compatible for the ChromeCast I guest... maybe it's something catt can do on the fly ?

Thanks for your kind words! We don't currently aim to support stream conversion, catt aims to strictly cast files that the device can already play.


After docking SAS stability hold (killrot) becomes ineffective

After docking two mk1 pods the combination loses the ability to stop rotating by activating SAS.
After undocking the problem does not go away. Essentially it seems like reaction wheels can do nothing after a docking event.

Should be fixed in 1.6


error beim beenden ab Js-Controller3.2.x

dieses passiert bei einem iobroker stop seit dem Js-Controller upgrade
`

radar2.0
2021-01-16 15:08:44.012
warn
(20289) Uncaught Exception: Cannot read property 'init' of null

radar2.0
2021-01-16 15:08:44.011
info
(20289) sendToHost not processed because States database not connected

radar2.0
2021-01-16 15:08:44.010
error
(20289) Cannot read property 'init' of null

radar2.0
2021-01-16 15:08:44.010
error
at processTimers (internal/timers.js:497:7)

radar2.0
2021-01-16 15:08:44.010
error
at listOnTimeout (internal/timers.js:554:17)

radar2.0
2021-01-16 15:08:44.010
error
at Timeout._onTimeout (/opt/iobroker/node_modules/iobroker.radar2/myNetworks.js:964:82)

radar2.0
2021-01-16 15:08:44.010
error
(20289) TypeError: Cannot read property 'init' of null

radar2.0
2021-01-16 15:08:44.009
error
(20289) uncaught exception: Cannot read property 'init' of null

`

Ok, hab von Entwickler von js-controller gehört dass er nach Adaptershutdown schneller die Kommunikation (und somit die Adapterbefehle) unterbindet.
Werde mir das anscheuen aber nicht sofort ändern können.

Werde mir das anscheuen aber nicht sofort ändern können.

 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().
2023-05-22 07:37:17.085 - error: shelly.0 (565995) unhandled promise rejection: DB closed
2023-05-22 07:37:17.320 - error: shelly.0 (565995) Error: DB closed
at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40)
at Shelly._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7526:34)
2023-05-22 07:37:17.321 - error: shelly.0 (565995) DB closed
2023-05-22 07:37:17.439 - warn: sonoff.0 (566079) get state error: DB closed
2023-05-22 07:37:17.445 - warn: sonoff.0 (566079) get state error: DB closed
2023-05-22 07:37:17.446 - warn: sonoff.0 (566079) redis get sonoff.0.Brunnen.alive, error - DB closed
2023-05-22 07:37:17.447 - warn: sonoff.0 (566079) redis get sonoff.0.Brunnen.alive, error - DB closed
2023-05-22 07:37:17.453 - warn: sonoff.0 (566079) redis get sonoff.0.Heizung.alive, error - Connection is closed.
2023-05-22 07:37:17.455 - warn: sonoff.0 (566079) redis get sonoff.0.Heizung.alive, error - Connection is closed.
2023-05-22 07:37:17.466 - info: host.IoBroker stopInstance system.adapter.admin.0 killing pid 564927
2023-05-22 07:37:17.467 - info: host.IoBroker stopInstance system.adapter.javascript.0 killing pid 565182
2023-05-22 07:37:17.467 - info: host.IoBroker stopInstance system.adapter.telegram.0 killing pid 565201
2023-05-22 07:37:17.468 - info: host.IoBroker stopInstance system.adapter.telegram.1 killing pid 565232
2023-05-22 07:37:17.468 - info: host.IoBroker stopInstance system.adapter.alexa2.0 killing pid 565553
2023-05-22 07:37:17.469 - info: host.IoBroker stopInstance system.adapter.chromecast.0 killing pid 565293
2023-05-22 07:37:17.470 - info: host.IoBroker stopInstance system.adapter.mihome.0 killing pid 565776
2023-05-22 07:37:17.470 - info: host.IoBroker stopInstance system.adapter.mqtt.0 killing pid 565882
2023-05-22 07:37:17.499 - warn: sonoff.0 (566079) redis get sonoff.0.Kleiderschrank.alive, error - Connection is closed.
2023-05-22 07:37:17.501 - warn: sonoff.0 (566079) redis get sonoff.0.Kleiderschrank.alive, error - Connection is closed.
2023-05-22 07:37:17.568 - info: host.IoBroker stopInstance system.adapter.nut.0 killing pid 565969
2023-05-22 07:37:17.569 - info: host.IoBroker stopInstance system.adapter.radar2.0 killing pid 572991
2023-05-22 07:37:17.569 - info: host.IoBroker stopInstance system.adapter.shelly.0 killing pid 565995
2023-05-22 07:37:17.570 - info: host.IoBroker stopInstance system.adapter.sonoff.0 killing pid 566079
2023-05-22 07:37:17.571 - info: host.IoBroker stopInstance system.adapter.tr-064.0 killing pid 566237
2023-05-22 07:37:17.572 - info: host.IoBroker stopInstance system.adapter.unifi.0 killing pid 566270
2023-05-22 07:37:17.573 - info: host.IoBroker stopInstance system.adapter.ble.0 killing pid 566308
2023-05-22 07:37:17.574 - info: host.IoBroker stopInstance system.adapter.broadlink2.0 killing pid 566332
2023-05-22 07:37:17.575 - info: host.IoBroker stopInstance system.adapter.iot.0 killing pid 566557
2023-05-22 07:37:17.576 - info: host.IoBroker stopInstance system.adapter.jarvis.0 killing pid 566574
2023-05-22 07:37:17.578 - info: host.IoBroker stopInstance system.adapter.linux-control.0 killing pid 566597
2023-05-22 07:37:17.579 - info: host.IoBroker stopInstance system.adapter.logparser.0 killing pid 566609
2023-05-22 07:37:17.580 - info: host.IoBroker stopInstance system.adapter.mytime.0 killing pid 566878
2023-05-22 07:37:17.581 - info: host.IoBroker stopInstance system.adapter.net-tools.0 killing pid 565538
2023-05-22 07:37:17.581 - info: host.IoBroker stopInstance system.adapter.shuttercontrol.0 killing pid 567235
2023-05-22 07:37:17.582 - info: host.IoBroker stopInstance system.adapter.simple-api.0 killing pid 567246
2023-05-22 07:37:17.583 - info: host.IoBroker stopInstance system.adapter.smartcontrol.0 killing pid 567257
2023-05-22 07:37:17.583 - info: host.IoBroker stopInstance system.adapter.sourceanalytix.0 killing pid 567467
2023-05-22 07:37:17.584 - info: host.IoBroker stopInstance system.adapter.tankerkoenig.0 killing pid 567490
2023-05-22 07:37:17.586 - info: host.IoBroker stopInstance system.adapter.text2command.0 killing pid 567509
2023-05-22 07:37:17.587 - info: host.IoBroker stopInstance system.adapter.trashschedule.0 killing pid 567520
2023-05-22 07:37:17.588 - info: host.IoBroker stopInstance system.adapter.virtualpowermeter.0 killing pid 567539
2023-05-22 07:37:17.589 - info: host.IoBroker stopInstance system.adapter.web.0 killing pid 567800
2023-05-22 07:37:17.590 - info: host.IoBroker stopInstance system.adapter.wled.0 killing pid 567842
2023-05-22 07:37:17.590 - info: host.IoBroker stopInstance system.adapter.yeelight-2.0 killing pid 567906
2023-05-22 07:37:17.591 - info: host.IoBroker stopInstance system.adapter.device-watcher.0 killing pid 568089
2023-05-22 07:37:17.591 - info: host.IoBroker stopInstance system.adapter.wiobrowser.0 killing pid 568122
2023-05-22 07:37:17.594 - info: host.IoBroker stopInstance system.adapter.wallpanel.0 killing pid 568138
2023-05-22 07:37:17.596 - info: host.IoBroker stopInstance system.adapter.countdown.0 killing pid 568150
2023-05-22 07:37:17.599 - info: host.IoBroker stopInstance system.adapter.tibberconnect.0 killing pid 568361
2023-05-22 07:37:17.600 - info: host.IoBroker stopInstance system.adapter.opendtu.0 killing pid 568377
2023-05-22 07:37:17.747 - debug: host.IoBroker-Server Objects <IP_ADDRESS>:59390 Redis Socket error: Error: write EPIPE
at afterWriteDispatched (node:internal/stream_base_commons:160:15)
at writeGeneric (node:internal/stream_base_commons:151:3)
at Socket._writeGeneric (node:net:930:11)
at Socket._write (node:net:942:8)
at writeOrBuffer (node:internal/streams/writable:392:12)
at _write (node:internal/streams/writable:333:10)
at Socket.Writable.write (node:internal/streams/writable:337:10)
at RedisHandler._write (/opt/iobroker/node_modules/@iobroker/db-base/src/lib/redisHandler.ts:274:21)
at RedisHandler._sendQueued (/opt/iobroker/node_modules/@iobroker/db-base/src/lib/redisHandler.ts:249:22)
at Immediate._onImmediate (/opt/iobroker/node_modules/@iobroker/db-base/src/lib/redisHandler.ts:298:33)
2023-05-22 07:37:17.751 - debug: host.IoBroker-Server Objects <IP_ADDRESS>:56510 Redis Socket error: Error: write EPIPE
at afterWriteDispatched (node:internal/stream_base_commons:160:15)
at writeGeneric (node:internal/stream_base_commons:151:3)
at Socket._writeGeneric (node:net:930:11)
at Socket._write (node:net:942:8)
at writeOrBuffer (node:internal/streams/writable:392:12)
at _write (node:internal/streams/writable:333:10)
at Socket.Writable.write (node:internal/streams/writable:337:10)
at RedisHandler._write (/opt/iobroker/node_modules/@iobroker/db-base/src/lib/redisHandler.ts:274:21)
at RedisHandler._sendQueued (/opt/iobroker/node_modules/@iobroker/db-base/src/lib/redisHandler.ts:249:22)
at Immediate._onImmediate (/opt/iobroker/node_modules/@iobroker/db-base/src/lib/redisHandler.ts:298:33)
2023-05-22 07:37:17.763 - warn: host.IoBroker instance system.adapter.milight-smart-light.0 terminated due to SIGTERM
2023-05-22 07:37:17.764 - info: host.IoBroker instance system.adapter.milight-smart-light.0 terminated with code null ()
2023-05-22 07:37:17.915 - warn: host.IoBroker instance system.adapter.sayit.0 terminated due to SIGTERM
2023-05-22 07:37:17.916 - info: host.IoBroker instance system.adapter.sayit.0 terminated with code null ()
2023-05-22 07:37:17.946 - info: zigbee2mqtt.0 (568105) terminating
2023-05-22 07:37:17.947 - info: zigbee2mqtt.0 (568105) Terminated (NO_ERROR): Without reason
2023-05-22 07:37:18.099 - warn: wiffi-wz.0 (567817) get state error: Connection is closed.
2023-05-22 07:37:18.101 - info: wiffi-wz.0 (567817) terminating
2023-05-22 07:37:18.122 - info: zigbee2mqtt.0 (568105) terminating with timeout
2023-05-22 07:37:19.100 - info: wiffi-wz.0 (567817) terminating with timeout
2023-05-22 07:37:22.854 - info: host.IoBroker stopInstance system.adapter.zigbee2mqtt.0 killing pid 568105
2023-05-22 07:37:22.856 - info: host.IoBroker stopInstance system.adapter.wiffi-wz.0 killing pid 567817
2023-05-22 07:37:22.856 - info: host.IoBroker stopInstance system.adapter.tuya.0 killing pid 566254
2023-05-22 07:37:22.857 - info: host.IoBroker stopInstance system.adapter.ws.0 killing pid 567861
2023-05-22 07:37:22.895 - debug: host.IoBroker-Server Objects <IP_ADDRESS>:42878 Redis Socket error: Error: write ECONNRESET
at afterWriteDispatched (node:internal/stream_base_commons:160:15)
at writeGeneric (node:internal/stream_base_commons:151:3)
at Socket._writeGeneric (node:net:930:11)
at Socket._write (node:net:942:8)
at writeOrBuffer (node:internal/streams/writable:392:12)
at _write (node:internal/streams/writable:333:10)
at Socket.Writable.write (node:internal/streams/writable:337:10)
at RedisHandler._write (/opt/iobroker/node_modules/@iobroker/db-base/src/lib/redisHandler.ts:274:21)
at RedisHandler._sendQueued (/opt/iobroker/node_modules/@iobroker/db-base/src/lib/redisHandler.ts:249:22)
at Immediate._onImmediate (/opt/iobroker/node_modules/@iobroker/db-base/src/lib/redisHandler.ts:298:33)
2023-05-22 07:37:22.970 - warn: host.IoBroker instance system.adapter.admin.0 terminated due to SIGTERM
2023-05-22 07:37:22.970 - info: host.IoBroker instance system.adapter.admin.0 terminated with code null ()
2023-05-22 07:37:23.056 - warn: host.IoBroker instance system.adapter.javascript.0 terminated due to SIGTERM
2023-05-22 07:37:23.056 - info: host.IoBroker instance system.adapter.javascript.0 terminated with code null ()
2023-05-22 07:37:23.112 - warn: host.IoBroker instance system.adapter.telegram.0 terminated due to SIGTERM
2023-05-22 07:37:23.113 - info: host.IoBroker instance system.adapter.telegram.0 terminated with code null ()
2023-05-22 07:37:23.194 - warn: host.IoBroker instance system.adapter.telegram.1 terminated due to SIGTERM
2023-05-22 07:37:23.195 - info: host.IoBroker instance system.adapter.telegram.1 terminated with code null ()
2023-05-22 07:37:23.257 - warn: host.IoBroker instance system.adapter.chromecast.0 terminated due to SIGTERM
2023-05-22 07:37:23.258 - info: host.IoBroker instance system.adapter.chromecast.0 terminated with code null ()
2023-05-22 07:37:23.445 - warn: host.IoBroker instance system.adapter.net-tools.0 terminated due to SIGTERM
2023-05-22 07:37:23.447 - info: host.IoBroker instance system.adapter.net-tools.0 terminated with code null ()
2023-05-22 07:37:23.504 - warn: host.IoBroker instance system.adapter.alexa2.0 terminated due to SIGTERM
2023-05-22 07:37:23.504 - info: host.IoBroker instance system.adapter.alexa2.0 terminated with code null ()
2023-05-22 07:37:23.578 - warn: host.IoBroker instance system.adapter.mihome.0 terminated due to SIGTERM
2023-05-22 07:37:23.579 - info: host.IoBroker instance system.adapter.mihome.0 terminated with code null ()
2023-05-22 07:37:23.635 - warn: host.IoBroker instance system.adapter.mqtt.0 terminated due to SIGTERM
2023-05-22 07:37:23.636 - info: host.IoBroker instance system.adapter.mqtt.0 terminated with code null ()
2023-05-22 07:37:23.706 - warn: host.IoBroker instance system.adapter.nut.0 terminated due to SIGTERM
2023-05-22 07:37:23.707 - info: host.IoBroker instance system.adapter.nut.0 terminated with code null ()
2023-05-22 07:37:23.763 - error: host.IoBroker Caught by controller[0]: 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(). The promise rejected with the reason:
2023-05-22 07:37:23.764 - error: host.IoBroker Caught by controller[0]: Error: DB closed
2023-05-22 07:37:23.764 - error: host.IoBroker Caught by controller[0]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
2023-05-22 07:37:23.765 - error: host.IoBroker Caught by controller[0]: at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
2023-05-22 07:37:23.765 - error: host.IoBroker Caught by controller[0]: at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40)
2023-05-22 07:37:23.766 - error: host.IoBroker Caught by controller[0]: at Shelly._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7526:34)
2023-05-22 07:37:23.766 - warn: host.IoBroker instance system.adapter.shelly.0 terminated due to SIGTERM
2023-05-22 07:37:23.767 - info: host.IoBroker instance system.adapter.shelly.0 terminated with code null ()
2023-05-22 07:37:23.848 - warn: host.IoBroker instance system.adapter.sonoff.0 terminated due to SIGTERM
2023-05-22 07:37:23.849 - info: host.IoBroker instance system.adapter.sonoff.0 terminated with code null ()
2023-05-22 07:37:23.927 - warn: host.IoBroker instance system.adapter.tr-064.0 terminated due to SIGTERM
2023-05-22 07:37:23.928 - info: host.IoBroker instance system.adapter.tr-064.0 terminated with code null ()
2023-05-22 07:37:24.017 - warn: host.IoBroker instance system.adapter.unifi.0 terminated due to SIGTERM
2023-05-22 07:37:24.018 - info: host.IoBroker instance system.adapter.unifi.0 terminated with code null ()
2023-05-22 07:37:24.130 - warn: host.IoBroker instance system.adapter.ble.0 terminated due to SIGTERM
2023-05-22 07:37:24.130 - info: host.IoBroker instance system.adapter.ble.0 terminated with code null ()
2023-05-22 07:37:24.187 - warn: host.IoBroker instance system.adapter.broadlink2.0 terminated due to SIGTERM
2023-05-22 07:37:24.188 - info: host.IoBroker instance system.adapter.broadlink2.0 terminated with code null ()
2023-05-22 07:37:24.263 - warn: host.IoBroker instance system.adapter.iot.0 terminated due to SIGTERM
2023-05-22 07:37:24.264 - info: host.IoBroker instance system.adapter.iot.0 terminated with code null ()
2023-05-22 07:37:24.343 - warn: host.IoBroker instance system.adapter.jarvis.0 terminated due to SIGTERM
2023-05-22 07:37:24.344 - info: host.IoBroker instance system.adapter.jarvis.0 terminated with code null ()
2023-05-22 07:37:24.400 - warn: host.IoBroker instance system.adapter.linux-control.0 terminated due to SIGTERM
2023-05-22 07:37:24.400 - info: host.IoBroker instance system.adapter.linux-control.0 terminated with code null ()
2023-05-22 07:37:24.473 - warn: host.IoBroker instance system.adapter.logparser.0 terminated due to SIGTERM
2023-05-22 07:37:24.474 - info: host.IoBroker instance system.adapter.logparser.0 terminated with code null ()
2023-05-22 07:37:24.530 - warn: host.IoBroker instance system.adapter.mytime.0 terminated due to SIGTERM
2023-05-22 07:37:24.531 - info: host.IoBroker instance system.adapter.mytime.0 terminated with code null ()
2023-05-22 07:37:24.606 - warn: host.IoBroker instance system.adapter.shuttercontrol.0 terminated due to SIGTERM
2023-05-22 07:37:24.607 - info: host.IoBroker instance system.adapter.shuttercontrol.0 terminated with code null ()
2023-05-22 07:37:24.696 - warn: host.IoBroker instance system.adapter.simple-api.0 terminated due to SIGTERM
2023-05-22 07:37:24.697 - info: host.IoBroker instance system.adapter.simple-api.0 terminated with code null ()
2023-05-22 07:37:24.837 - warn: host.IoBroker instance system.adapter.smartcontrol.0 terminated due to SIGTERM
2023-05-22 07:37:24.839 - info: host.IoBroker instance system.adapter.smartcontrol.0 terminated with code null ()
2023-05-22 07:37:24.890 - warn: host.IoBroker instance system.adapter.sourceanalytix.0 terminated due to SIGTERM
2023-05-22 07:37:24.890 - info: host.IoBroker instance system.adapter.sourceanalytix.0 terminated with code null ()
2023-05-22 07:37:24.964 - warn: host.IoBroker instance system.adapter.tankerkoenig.0 terminated due to SIGTERM
2023-05-22 07:37:24.965 - info: host.IoBroker instance system.adapter.tankerkoenig.0 terminated with code null ()
2023-05-22 07:37:25.016 - warn: host.IoBroker instance system.adapter.text2command.0 terminated due to SIGTERM
2023-05-22 07:37:25.017 - info: host.IoBroker instance system.adapter.text2command.0 terminated with code null ()
2023-05-22 07:37:25.090 - warn: host.IoBroker instance system.adapter.trashschedule.0 terminated due to SIGTERM
2023-05-22 07:37:25.091 - info: host.IoBroker instance system.adapter.trashschedule.0 terminated with code null ()
2023-05-22 07:37:25.139 - warn: host.IoBroker instance system.adapter.virtualpowermeter.0 terminated due to SIGTERM
2023-05-22 07:37:25.140 - info: host.IoBroker instance system.adapter.virtualpowermeter.0 terminated with code null ()
2023-05-22 07:37:25.213 - warn: host.IoBroker instance system.adapter.web.0 terminated due to SIGTERM
2023-05-22 07:37:25.214 - info: host.IoBroker instance system.adapter.web.0 terminated with code null ()
2023-05-22 07:37:25.302 - warn: host.IoBroker instance system.adapter.wled.0 terminated due to SIGTERM
2023-05-22 07:37:25.303 - info: host.IoBroker instance system.adapter.wled.0 terminated with code null ()
2023-05-22 07:37:25.384 - warn: host.IoBroker instance system.adapter.yeelight-2.0 terminated due to SIGTERM
2023-05-22 07:37:25.385 - info: host.IoBroker instance system.adapter.yeelight-2.0 terminated with code null ()
2023-05-22 07:37:25.536 - warn: host.IoBroker instance system.adapter.device-watcher.0 terminated due to SIGTERM
2023-05-22 07:37:25.537 - info: host.IoBroker instance system.adapter.device-watcher.0 terminated with code null ()
2023-05-22 07:37:25.591 - warn: host.IoBroker instance system.adapter.wiobrowser.0 terminated due to SIGTERM
2023-05-22 07:37:25.591 - info: host.IoBroker instance system.adapter.wiobrowser.0 terminated with code null ()
2023-05-22 07:37:25.663 - warn: host.IoBroker instance system.adapter.wallpanel.0 terminated due to SIGTERM
2023-05-22 07:37:25.664 - info: host.IoBroker instance system.adapter.wallpanel.0 terminated with code null ()
2023-05-22 07:37:25.716 - warn: host.IoBroker instance system.adapter.countdown.0 terminated due to SIGTERM
2023-05-22 07:37:25.716 - info: host.IoBroker instance system.adapter.countdown.0 terminated with code null ()
2023-05-22 07:37:25.786 - warn: host.IoBroker instance system.adapter.tibberconnect.0 terminated due to SIGTERM
2023-05-22 07:37:25.787 - info: host.IoBroker instance system.adapter.tibberconnect.0 terminated with code null ()
2023-05-22 07:37:25.838 - warn: host.IoBroker instance system.adapter.opendtu.0 terminated due to SIGTERM
2023-05-22 07:37:25.839 - info: host.IoBroker instance system.adapter.opendtu.0 terminated with code null ()
2023-05-22 07:37:25.915 - warn: host.IoBroker instance system.adapter.radar2.0 terminated due to SIGTERM
2023-05-22 07:37:25.916 - info: host.IoBroker instance system.adapter.radar2.0 terminated with code null ()
2023-05-22 07:37:27.033 - info: host.IoBroker instance system.adapter.influxdb.0 terminated with code 0 (NO_ERROR)
2023-05-22 07:37:27.108 - warn: host.IoBroker instance system.adapter.tuya.0 terminated due to SIGTERM
2023-05-22 07:37:27.109 - info: host.IoBroker instance system.adapter.tuya.0 terminated with code null ()
2023-05-22 07:37:27.159 - warn: host.IoBroker instance system.adapter.wiffi-wz.0 terminated due to SIGTERM
2023-05-22 07:37:27.160 - info: host.IoBroker instance system.adapter.wiffi-wz.0 terminated with code null ()
2023-05-22 07:37:27.234 - warn: host.IoBroker instance system.adapter.ws.0 terminated due to SIGTERM
2023-05-22 07:37:27.235 - info: host.IoBroker instance system.adapter.ws.0 terminated with code null ()
2023-05-22 07:37:27.287 - warn: host.IoBroker instance system.adapter.zigbee2mqtt.0 terminated due to SIGTERM
2023-05-22 07:37:27.288 - info: host.IoBroker instance system.adapter.zigbee2mqtt.0 terminated with code null ()
2023-05-22 07:37:27.363 - info: host.IoBroker instance system.adapter.history.0 terminated with code 0 (NO_ERROR)
2023-05-22 07:37:27.449 - info: host.IoBroker instance system.adapter.influxdb.1 terminated with code 0 (NO_ERROR)
2023-05-22 07:37:27.555 - info: host.IoBroker instance system.adapter.vis-inventwo.0 terminated while should be started once
2023-05-22 07:37:30.145 - debug: host.IoBroker Plugin sentry destroyed
2023-05-22 07:37:30.173 - info: host.IoBroker force terminating
2023-05-22 07:37:59.172 - info: host.IoBroker iobroker.js-controller version 5.0.1 js-controller starting`


Dragging multiple image files inserts malformed markdown

If I drag a single image file into MDE, then I get a nice link. If I drag multiple files, then MDE malforms the links by inserting the markdown for the second image inside the markdown for the first and so on. This description makes no sense, so an example.
I drag two image files (both located in the same folder as my document) into MDE. The first is called snaplines-custom-wm.gif, and the second snaplines-default-wm.gif.
I would expect to get something like this
![snaplines-custom-wm](snaplines-custom-wm.gif)
![snaplines-default-wm](snaplines-default-wm.gif)

But instead get
![snap![snaplines-default-wm](snaplines-default-wm.gif)
lines-custom-wm](snaplines-custom-wm.gif)

(including an extra blank line that doesn't appear in the above block)

Oddly, I can't repro this. Maybe you can zip me a document and images that demonstrates the problem?

Surprised you can't repro, it happens pretty much all the time for me. Doesn't seem to be related to any document or set of file names that I've observed.
Try this
Title
=====

Some words

I stuck my cursor on the blank line, in case it was something to do with dragging before or after the cursor (doesn't seem to be). Then I tried dragging a pair of image files test.png and palette.png into the editor.
Didn't seem to matter where I dropped the files, invariably, they were munged into a corrupt form.
The only exception that seems solid was if I dropped the image files past the last line of the document - then they were inserted properly. Or, if the document was fully empty. Apart from those two conditions, malformed markdown was virtually always.

I was dropping past the end of the document. Explains it. Thanks.


[release-1.7] Fix null ingressGateways for minimal and empty profile.

Manual cherrypick required.
#27198 failed to apply on top of branch "release-1.7":
Applying: Fix null ingressGateways for minimal and empty profile
Using index info to reconstruct a base tree...
M	manifests/profiles/empty.yaml
M	manifests/profiles/minimal.yaml
Falling back to patching base and 3-way merge...
Auto-merging manifests/profiles/minimal.yaml
CONFLICT (content): Merge conflict in manifests/profiles/minimal.yaml
Auto-merging manifests/profiles/empty.yaml
CONFLICT (content): Merge conflict in manifests/profiles/empty.yaml
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Fix null ingressGateways for minimal and empty profile
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

Closing as https://github.com/istio/istio/pull/30057 has been merged.

Closing as https://github.com/istio/istio/pull/30057 has been merged.


Enable Landing page to switch between to old CLI service in 0.9.x (appsody) and new GO Kabanero Rest Service in 0.11+

Enable Landing page to switch between to old CLI service in 0.9.x (appsody) and new GO Kabanero Rest Service in 0.11+(ODO)

Know which level you are running with, and use compatible Landing page client code for the rest service image running

0.9.x still reads from stack hub (index) on GIT
new GO rest service only reads Stack indexes from Kabanero

the version of landing page running is determined by the deployment yaml supplied by the operator

Not sure if this issue is even necessary


Cannot  read the VCF file

When I use this Command:
bam_files <- c("7Z-1.test.bam","7Z-2.test.bam")
vcf_files <- c("get.vcf","get.vcf")
sample_names <- c("7Z-1", "7Z-2")
reference_file <- ("/public/home/chaohe/db/CS/CS_genome/CSchr1A.fa")
snp.list <- extract_bams(bam_files, vcf_files, sample_names, reference_file, coverage = 2)
I got the error:
Reading reference file
Running sample 7Z-1
Reading VCF file
Extracting methylation per SNP
Error in character(nchar(a)) : vector size cannot be NA
I do not know what happened, could you please help me? Thanks a lot!
File detail
7Z-1.test.bam :

get.vcf:

CSchr1A.fa:

Hi,
Can you run these steps and let me know what output you get?
#choose the first SNP from your VCF file
loc <- GRanges(seqnames = "chr1A",
               IRanges(start = 1926,
                       width = 1))

#select parameters to read in
params <- ScanBamParam(tag = c("MD"), which = loc)

# read in reads overlapping snp
alns <- readGAlignments(bam_files[1],
                            use.names = TRUE,
                            param = params)

Please paste the output for alns, just like the first 3 rows is enough.

Hi, looks like your bam files don't have an MD tag. What aligner are you using?
Can you run these steps and let me know what output you get?
#choose the first SNP from your VCF file
loc <- GRanges(seqnames = "chr1A",
               IRanges(start = 1926,
                       width = 1))

#select parameters to read in
params <- ScanBamParam(tag = c("MD", "XM", "XR", "XG"), which = loc)

# read in reads overlapping snp
alns <- readGAlignments(bam_files[1],
                            use.names = TRUE,
                            param = params)

Please paste the output for alns, just like the first 3 rows is enough.

Thank you for such quickly reply. I use BS-seeker2 to analysis the WGBS datasets, which based on the aligner of Bowtie2.  And the output of 'alns' was:

The first 1 rows were :

If I directly paste the result, it was hard to read, so I upload the picture, hope it will not cause you trouble. Thank you again.

Thanks, yes so indeed there are no MD tags. It's a bit strange that BS-seeker removes them. Maybe there's an option to keep them?
I've only tested the package with bam files from Bismark So you can try to align with that and try again.

Thanks, yes so indeed there are no MD tags. It's a bit strange that BS-seeker removes them. Maybe there's an option to keep them?
I've only tested the package with bam files from Bismark So you can try to align with that and try again.

So sad to hear that.  If I rerun the alignment step, maybe It will take about two months. The genome is wheat (16 Gb), crying..... Anyway, thank you very much!

You can also try running methtuple on your bams, and test the fast-mode (methtuple is not so slow to run). This mode doesn't rely on SNPs so you don't need the MD tag.

Thank you very very……much!  I will try.  Best wishes.-------- 原始邮件 --------发件人： Stephany Orjuela @.>日期： 2022年10月17日周一 下午4:49收件人： markrobinsonuzh/DAMEfinder @.>抄送： HC @.>, Author @.>主    题： Re: [markrobinsonuzh/DAMEfinder] Cannot  read the VCF file (Issue #42)
You can also try running methtuple on your bams, and test the fast-mode (methtuple is not so slow to run). This mode doesn't rely on SNPs so you don't need the MD tag.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>


Tricky error with unescaped quotes in values

Hello, thanks for this software. Really helps complete the pest cycle, and I have experience with tree-sitter tests, so it really is nice. So far has worked great.
Ran into this issue which gave odd errors.
Error: Parser { source: Pest { source: Error { variant: ParsingError { positives: [skip], negatives: [] }, location: Pos(1317), line_col: Pos((65, 12)), path: None, line: "      (json: \"{\"vae\": \"c6a580b13a\", \"model\": \"4d91c4c217\"}\")", continued_line: None } } }

Which was suggested from a failing test:

Figured it must be something with the quotes after a while, and escaped the quotes, and it works.
prompt.txt
Alternatively, I thought I didn't care for matching the value with (json) vs with the value (json: "(\"model\"....") but it said it was missing the value.
No worries as I can work around it. Thanks again.

Yes, that makes sense. Values are represented as strings, so if they are quoted then they need to be escaped. An improvement could be to support using either single- or double-quotes. That way you could avoid escaping by enclosing in single quotes:
...
(params_pair
    (key: "Hashes")
    (value
      (json: '{"vae": "c6a580b13a", "model": "4d91c4c217"}')
    )
  )

I guess the error message should also re-escape the value.


Show an error when the /converse API fails

WHAT:
An error should be shown if the /converse api fails during chatting.
Currently, the chat will stay in loading state infinitely when an error occurs.

Hi, is this issue being worked upon?


Fix CancellationReceiverStrategy type definition to include RequestCancellationReceiverStrategy

See https://github.com/microsoft/vscode-languageserver-node/blob/3555a32f14e0c4235fcad02388efaed8b4af64fb/jsonrpc/src/common/connection.ts#L400

Implemented. Will be in next release

I believe this has regressed with the latest export changes? At least I can't import it anymore.
The api for the vscode-jsonrpc doesn't seem to export it anymore:
// api.d.ts
/// <reference path="../../typings/thenable.d.ts" />
import { Message, MessageSignature, RequestMessage, RequestType, RequestType0, RequestType1, RequestType2, RequestType3, RequestType4, RequestType5, RequestType6, RequestType7, RequestType8, RequestType9, ResponseError, ErrorCodes, NotificationMessage, NotificationType, NotificationType0, NotificationType1, NotificationType2, NotificationType3, NotificationType4, NotificationType5, NotificationType6, NotificationType7, NotificationType8, NotificationType9, ResponseMessage, ParameterStructures, _EM } from './messages';
import { LinkedMap, LRUCache, Touch } from './linkedMap';
import { Disposable } from './disposable';
import { Event, Emitter } from './events';
import { AbstractCancellationTokenSource, CancellationTokenSource, CancellationToken } from './cancellation';
import { SharedArraySenderStrategy, SharedArrayReceiverStrategy } from './sharedArrayCancellation';
import { MessageReader, AbstractMessageReader, ReadableStreamMessageReader, DataCallback, MessageReaderOptions, PartialMessageInfo } from './messageReader';
import { MessageWriter, AbstractMessageWriter, WriteableStreamMessageWriter, MessageWriterOptions } from './messageWriter';
import { AbstractMessageBuffer } from './messageBuffer';
import { ContentTypeEncoderOptions, ContentEncoder, ContentTypeEncoder, ContentTypeDecoderOptions, ContentDecoder, ContentTypeDecoder } from './encoding';
import { Logger, ConnectionStrategy, ConnectionOptions, MessageConnection, NullLogger, createMessageConnection, ProgressToken, ProgressType, HandlerResult, StarRequestHandler, GenericRequestHandler, RequestHandler0, RequestHandler, RequestHandler1, RequestHandler2, RequestHandler3, RequestHandler4, RequestHandler5, RequestHandler6, RequestHandler7, RequestHandler8, RequestHandler9, StarNotificationHandler, GenericNotificationHandler, NotificationHandler0, NotificationHandler, NotificationHandler1, NotificationHandler2, NotificationHandler3, NotificationHandler4, NotificationHandler5, NotificationHandler6, NotificationHandler7, NotificationHandler8, NotificationHandler9, Trace, TraceValue, TraceFormat, TraceOptions, SetTraceParams, SetTraceNotification, LogTraceParams, LogTraceNotification, Tracer, ConnectionErrors, ConnectionError, CancellationId, CancellationReceiverStrategy, CancellationSenderStrategy, CancellationStrategy, MessageStrategy, TraceValues } from './connection';
import RAL from './ral';
export { RAL, Message, MessageSignature, RequestMessage, RequestType, RequestType0, RequestType1, RequestType2, RequestType3, RequestType4, RequestType5, RequestType6, RequestType7, RequestType8, RequestType9, ResponseError, ErrorCodes, NotificationMessage, NotificationType, NotificationType0, NotificationType1, NotificationType2, NotificationType3, NotificationType4, NotificationType5, NotificationType6, NotificationType7, NotificationType8, NotificationType9, ResponseMessage, ParameterStructures, _EM, LinkedMap, Touch, LRUCache, Disposable, Event, Emitter, AbstractCancellationTokenSource, CancellationTokenSource, CancellationToken, SharedArraySenderStrategy, SharedArrayReceiverStrategy, MessageReader, AbstractMessageReader, ReadableStreamMessageReader, DataCallback, MessageReaderOptions, PartialMessageInfo, MessageWriter, AbstractMessageWriter, WriteableStreamMessageWriter, MessageWriterOptions, AbstractMessageBuffer, ContentTypeEncoderOptions, ContentEncoder, ContentTypeEncoder, ContentTypeDecoderOptions, ContentDecoder, ContentTypeDecoder, Logger, ConnectionStrategy, ConnectionOptions, MessageConnection, NullLogger, createMessageConnection, ProgressToken, ProgressType, HandlerResult, StarRequestHandler, GenericRequestHandler, RequestHandler0, RequestHandler, RequestHandler1, RequestHandler2, RequestHandler3, RequestHandler4, RequestHandler5, RequestHandler6, RequestHandler7, RequestHandler8, RequestHandler9, StarNotificationHandler, GenericNotificationHandler, NotificationHandler0, NotificationHandler, NotificationHandler1, NotificationHandler2, NotificationHandler3, NotificationHandler4, NotificationHandler5, NotificationHandler6, NotificationHandler7, NotificationHandler8, NotificationHandler9, Trace, TraceValue, TraceValues, TraceFormat, TraceOptions, SetTraceParams, SetTraceNotification, LogTraceParams, LogTraceNotification, Tracer, ConnectionErrors, ConnectionError, CancellationId, CancellationReceiverStrategy, CancellationSenderStrategy, CancellationStrategy, MessageStrategy };

I get this error now:

It seems there's some other things that are no longer exported. I can't use attachWorkDone or ProgressPart either. They aren't exported from the new api:
import { _, Features, _Connection } from './server';
import { SemanticTokensBuilder } from './semanticTokens';
import type { WorkDoneProgressReporter, WorkDoneProgressServerReporter, ResultProgressReporter } from './progress';
import * as ic from './inlineCompletion.proposed';
import * as tdc from './textDocumentContent';
export * from 'vscode-languageserver-protocol';
export { WorkDoneProgressReporter, WorkDoneProgressServerReporter, ResultProgressReporter };
export { SemanticTokensBuilder };
import { TextDocuments, TextDocumentsConfiguration, TextDocumentChangeEvent, TextDocumentWillSaveEvent } from './textDocuments';
export { TextDocuments, TextDocumentsConfiguration, TextDocumentChangeEvent, TextDocumentWillSaveEvent };
import { NotebookDocuments } from './notebook';
export { NotebookDocuments };
export * from './server';
export declare namespace ProposedFeatures {
    const all: Features<_, _, _, _, _, tdc.TextDocumentContentFeatureShape, ic.InlineCompletionFeatureShape, _>;
    type Connection = _Connection<_, _, _, _, _, tdc.TextDocumentContentFeatureShape, ic.InlineCompletionFeatureShape, _>;
}

Those seem more on purpose though. Maybe you never wanted to export them in the first place.

See https://github.com/microsoft/vscode-languageserver-node/pull/1542

I was using the ProgressPart for the dispatcher work we talked about a while ago. The progress was basically handled by intercepting messages in the dispatcher layer. attachWorkDone was for the same reason. This attachWorkDone: https://github.com/microsoft/vscode-languageserver-node/blob/89c6f5cb47e64964b685f42e5063a575b2c54635/server/src/common/progress.ts#L145.
We can just copy the ProgressPart. We did get it by directly doing the import from the file.

Here's where we use ProgressPart now:
https://github.com/microsoft/pyrx/blob/525aee4212db5cf94eda671f0f1addfd28262732/packages/vscode-pylance/src/sharedExtension.ts#L379

I see. Imports like this
import { ProgressPart } from 'vscode-languageclient/lib/common/progressPart';

were actually never supported. The problem was that Node did not rejected them. This changed with the new syntax that got introduce in Node16 which I have now adopted. Otherwise I can never separate API from non API since I need to even export things in non API files.
Did you import attachWorkDone directly as well?

@rchiodo OK. Thanks. I fixed the strategy exports. Will make new next versions.


Vonage Voyagers Application: Adhere to PEP 8 style guidelines

This issue is also part of my vonage voyagers application:
As I reviewed the codebase, I noticed some PEP 8 styling violations that may be noteworthy:
For example:

Top level class definitions are separated by a single blankspace instead of two
some lines are beyond the recommended 79 line character limit. (Comments/ Docstrings have fewer structural restrictions and should be limited to 72 characters)

The full PEP 8 style guide can be found here: (https://www.python.org/dev/peps/pep-0008/)

Hi @Psycadelik ! Sorry to hear you're having this issue and thank you for bringing our attention to it. Looks like some of the code is not following the PEP 8 style guide? Are these issues in the Vonage Python SDK as well?

Hi @Psycadelik ! Sorry to hear you're having this issue and thank you for bringing our attention to it. Looks like some of the code is not following the PEP 8 style guide? Are these issues in the Vonage Python SDK as well?

Hi @geekchick . Yes the issues are in the Python SDK.

Hi @Psycadelik thank you again for bringing up the PEP 8 style issues. We'll check it out and see what we can do.


Plugin Hapi Swagger does not support oauthOptions property into plugin configuration

Issue
Environment
npx envinfo --npmPackages '*hapi*' --binaries

(paste the output of the command here)
Steps to Reproduce
The Hapi Swagger Plugin Options does not support the property oauthOptions
{
    plugin: HapiSwagger as Plugin<unknown>,
    options: {
      jsonPath: '/products/swagger.json',
      info: {
        title: 'Product Documentation',
        version
      },
      oauthOptions:{
        oauth2RedirectUrl: "http://localhost:3200/someNewPage.html",
      },
      security,
      securityDefinitions,
      grouping: 'tags',
      documentationPath: '/products/documentation',
      swaggerUIPath: '/products/swaggerui/'
    }
  }

Expected Behavior
Swagger should load, and oauth2RedirectUrl be changed from default to the defined value in config.
Actual Behavior
Swagger does not load.

Reproducible Demo
Add the oauthOptions in the Hapi Swagger Plugin Options ( oauthOptions:{...} ).
Launch the swagger ui, the error is raises at swagger ui front screen and in the console log.

Can you link to docs saying that should be supported?

Hi,
Actually, when I read the Options Reference in the github page (https://github.com/glennjones/hapi-swagger/blob/master/optionsreference.md), I found the following line :
oauthOptions: TODO

Indeed I'm not sure if it should be supported or not, but in my case It would be great to have this feature.
Thank you
Best Regards

ok thanks. seems the docs and code have disconnect.

From memory it was never added, mainly to keep the UI a little simpler. It should be possible to add it there is support within swagger UI and @hapi/bell.  The main work will not just be wiring up the code, but enhancing the documentation to cover this subject.  It is often a bit of an involved process adding OAuth and I am sure it will increase our support issues.  Adding an example use case may also be a good idea.


Crash if icon points to unavailable http(s) url

I've run into an issue where some of our Jamf self service icons have gone missing and when that happens, swiftDialog crashes when trying to display them.
Ideally it would fall back to the default icon if nothing comes down.
$ dialog --title "Title goes here" --message "Message goes here" --icon "https://www.dropbox.com/s/4batk8v5outfxo5/install.png?dl=0"
/usr/local/bin/dialog: line 2: 35600 Trace/BPT trap: 5       /Library/Application\ Support/Dialog/Dialog.app/Contents/MacOS/Dialog "$@"

Maybe the issue is that something comes down, but it is 0 bytes

ah - the reason this is failing is that the icon you are specifying is behind a redirect. swiftDialog will handle 404's and present a boxed ? icon if it can't display the resource but I'll see what I can do about following redirects.

This issue should be fixed in 2.3 now I've moved to asynchronous image processing. Using the example command above should at worse result in a [?] icon


Content Security Policy

All necessary javascript packages should get included in the theme. No calls to external servers will be necessary. Therefore, it should be easy to implement tight security rules.

Will do, but in the module hugo-mod-csp


chore(changelog): show full commit message

This allows someone reading the changelog to search for information
about breaking changes or implementation of new functionality.

refactored the commit template part to a macro instead of repeating it
added a link to the commit and to the release
updated the current changelog for the alpha and unreleased changes
Automatically changed the existing * lists to - lists

I personally like this change, but I'm also curious if others have opinions on whether it is too verbose or not for a changelog.

I personally like this change, but I'm also curious if others have opinions on whether it is too verbose or not for a changelog.

I gave that a bit of consideration.

The pro side is that more details = easier to search for information using Ctrl/Cmd+F. Finding what changed in a git commit history is often more difficult compared to searching a single file like this.
The cons are that having too many details can get in the way of seeing the high level view of things overview.

I think the tradeoff is reasonable, but there's also a third approach we could have that moves the details to another section under the list of changes. It's a bit more work though.

P.s. Don't merge this just yet - letting @orhun take some time to look at some git cliff stuff before we do that.


Setting for the number of visible lines in side-by-side diff

Currently this setting is not persisted and is forgotten as you change the file to view the next diff. Bonus would be to also have the option to compare the full file with default jumped to first diff.

Currently this setting is not persisted and is forgotten as you change the file to view the next diff

I've pushed a commit faabfd6b80d07ad71f73d26d6919ece1a80f71d9 to this feature. You can use buttons in the diff view tool bar to increase or decrese the number of visible context lines. And you can also set
the number of visible diff context lines from Preference dialog directly.
You can try the latest build from https://github.com/sourcegit-scm/sourcegit/actions.

Bonus would be to also have the option to compare the full file with default jumped to first diff.

To compare the full file, I recommand you using an extern diff/merge tool.

Open the Preference window, and go to DIFF/MERGE TOOL page.
Choose a diff/merge tool you perfered.

After that you can use this external tool to view changes by a simple click


[T2A4][T11-A2]Sun Mingyang

This commit contains all the changes in T2A3 and T2A4.
Every single change was not separately committed because the commit was done after all the changes had been settled.

Next time please commit individual changes :)


feat: use the regualr dependnacies to import the install the starknet-sierra-compile crate

This change is

#728  👈
main

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

Join @ArniStarkware and the rest of your teammates on  Graphite

crates/starknet_sierra_compile/Cargo.toml line 18 at r3 (raw file):

serde.workspace = true
serde_json.workspace = true
starknet-sierra-compile = { package = "starknet-sierra-compile", version = "2.7.0", artifact = "bin"}

The feature of adding artifact =  to the dependency is unstable:
I could run it with: rustup run nightly cargo test -Z bindeps.
I have not figured out yet how to set the version independently of other dependencies.
Read more about the unstable feature of artifact-dependencies: open_issue, documentation
Code quote:
starknet-sierra-compile = { package = "starknet-sierra-compile", version = "2.7.0", artifact = "bin"}


fix: put file corruption with chunked transfer

When on linux with O_TMPFILE support, we issue and fallocate for the expected object size ax an optimization for the underlying filesystem to allocate the full file all ate once. With the chunked transfer encoding, the final object size is recoded in the X-Amz-Decoded-Content-Length instead of the standard ContentLength which includes the chunk encoding in the payload.
We were incorrectly using the content length to fallocate the file which would cause the filesystem to pad out any unwritten length to this size with 0s.
The fix here is to make sure we pass the X-Amz-Decoded-Content-Length as the object size to the backend for all PUTs.
Fixes #753

I as well had observed trailing null bytes on uploaded files.
kopia failed to when reading the initialized repository, because when if fetched the json blobs from the repo, the json parser failed (trailing null bytes are, according to spec, not valid).
Can confirm this patch fixes it.