fuchsia_tester --coverage hangs on dartfmt_extras_tests

Steps to reproduce:

Check out fuchsia with layer set to topaz.
patch replace third_party/dart-pkg/git/flutter/packages/flutter_tools/bin/fuchsia_tester.dart with the copy from upstream flutter: curl https://github.com/flutter/flutter/raw/packages/flutter_tools/bin/fuchsia_tester.dart -o third_party/dart-pkg/git/flutter/packages/flutter_tools/bin/fuchsia_tester.dart. This won't be needed once the version of flutter in fuchsia gets updated.
fx clean-build x64
out/x64/host_x64/dart-tools/fuchsia_tester  --packages=out/x64/dartlang/gen/topaz/tools/dartfmt_extras/dartfmt_extras_tests_library.packages  --shell=out/x64/host_x64/flutter_tester --test-directory=topaz/tools/dartfmt_extras/test --coverage

Expected result:
Test runs to completion and generates coverage data.
Observed result:
Test hangs for 2 minutes, then an exception is raised and the process stays stuck.
$ out/x64/host_tests/dartfmt_extras_tests --coverage
00:00 +0: loading /usr/local/google/home/garymm/fuchsia/topaz/tools/dartfmt_extras/test/directives_test.dart                        S
hell: Do not know weight for: TeXGyreSchola (BoldItalic)
Shell: Do not know weight for: TeXGyreSchola (BoldItalic)
02:01 +2: ... Double quotes should be fixed correctly.                                                                              u
nhandled error during test:
/usr/local/google/home/garymm/fuchsia/topaz/tools/dartfmt_extras/test/directives_test.dart
Exception: Timed out while collecting coverage.
#0      CoverageCollector.collectCoverage.<anonymous closure> (package:flutter_tools/src/test/coverage_collector.dart:64)
#1      StackZoneSpecification._run (package:stack_trace/src/stack_zone_specification.dart:209)
#2      StackZoneSpecification._registerCallback.<anonymous closure> (package:stack_trace/src/stack_zone_specification.dart:119)
#3      _rootRun (dart:async/zone.dart:1122)
#4      _CustomZone.run (dart:async/zone.dart:1023)
#5      Future.timeout.<anonymous closure> (dart:async/future_impl.dart:731)
#6      StackZoneSpecification._run (package:stack_trace/src/stack_zone_specification.dart:209)
#7      StackZoneSpecification._registerCallback.<anonymous closure> (package:stack_trace/src/stack_zone_specification.dart:119)
#8      _rootRun (dart:async/zone.dart:1122)
#9      _CustomZone.run (dart:async/zone.dart:1023)
#10     _CustomZone.runGuarded (dart:async/zone.dart:925)
#11     _CustomZone.bindCallbackGuarded.<anonymous closure> (dart:async/zone.dart:965)
#12     StackZoneSpecification._run (package:stack_trace/src/stack_zone_specification.dart:209)
#13     StackZoneSpecification._registerCallback.<anonymous closure> (package:stack_trace/src/stack_zone_specification.dart:119)
#14     _rootRun (dart:async/zone.dart:1126)
#15     _CustomZone.run (dart:async/zone.dart:1023)
#16     _CustomZone.bindCallback.<anonymous closure> (dart:async/zone.dart:949)
#17     Timer._createTimer.<anonymous closure> (dart:async-patch/dart:async/timer_patch.dart:21)
#18     _Timer._runTimers (dart:isolate-patch/dart:isolate/timer_impl.dart:382)
#19     _Timer._handleMessage (dart:isolate-patch/dart:isolate/timer_impl.dart:416)
#20     _RawReceivePortImpl._handleMessage (dart:isolate-patch/dart:isolate/isolate_patch.dart:165)

So there are really 2 issues here:

This particular test triggers a timeout during coverage collection. Not sure if the problem is in the flutter coverage collector or in the code under test.
Once the timeout is triggered, the fuchsia_tester process hangs rather than exits cleanly.

CC @yyoon @cbracken @tvolkert

It looks like one of the flutter_tester processes started by this test suite is segfaulting during the isolate.getSourceReport RPC.  collectCoverage in flutter_tools is then timing out waiting for a response from the dead process.
Follow ups:

collectCoverage should exit if the child process dies
why is getSourceReport crashing on this test?

@jason-simmons did we get any stack trace on the process that segfaulted?

Here is a stack trace that I captured from this crash:
#0  id (this=<optimized out>) at ../../third_party/dart/runtime/vm/object.h:956
#1  IsDynamicClass (this=<optimized out>) at ../../third_party/dart/runtime/vm/object.h:1111
#2  dart::Class::TypeTestNonRecursive (cls=..., test_kind=dart::Object::kIsMoreSpecificThan, type_arguments=..., other=...,
    other_type_arguments=..., bound_error=0x0, bound_trail=0x0, space=dart::Heap::kOld) at ../../third_party/dart/runtime/vm/object.cc:4099
#3  0x0000000001272744 in TypeTest (this=<optimized out>, test_kind=<optimized out>, type_arguments=..., other=..., other_type_arguments=...,
    bound_error=<optimized out>, bound_trail=<optimized out>, space=<optimized out>) at ../../third_party/dart/runtime/vm/object.cc:4250
#4  dart::AbstractType::TypeTest (this=<optimized out>, test_kind=dart::Object::kIsMoreSpecificThan, other=..., bound_error=0x0,
    bound_trail=0x0, space=<optimized out>) at ../../third_party/dart/runtime/vm/object.cc:17340
#5  0x000000000147a461 in IsMoreSpecificThan (this=<optimized out>, other=..., bound_error=0x7ffd037fcb98, space=dart::Heap::kOld,
    bound_trail=<optimized out>) at ../../third_party/dart/runtime/vm/object.h:6259
#6  dart::CompileType::CanComputeIsInstanceOf (this=0x6c487f8, type=..., is_nullable=true, is_instance=0x7ffd037fb837)
    at ../../third_party/dart/runtime/vm/compiler/backend/type_propagator.cc:767
#7  0x0000000001498906 in IsAssignableTo (this=0x0, type=...) at ../../third_party/dart/runtime/vm/compiler/backend/il.h:101
#8  dart::EffectGraphVisitor::CanSkipTypeCheck (this=0x7ffd037fb9c0, token_pos=..., value=0x6c487c8, dst_type=..., dst_name=...)
    at ../../third_party/dart/runtime/vm/compiler/frontend/flow_graph_builder.cc:1248
#9  0x0000000001497adb in dart::EffectGraphVisitor::BuildAssignableValue (this=0x7ffd037fb9c0, token_pos=..., value=0x6c487c8, dst_type=...,
    dst_name=...) at ../../third_party/dart/runtime/vm/compiler/frontend/flow_graph_builder.cc:1445
#10 0x00000000014a96ac in dart::EffectGraphVisitor::VisitStoreInstanceFieldNode (this=0x7ffd037fb9c0, node=0x6c47878)
    at ../../third_party/dart/runtime/vm/compiler/frontend/flow_graph_builder.cc:3487
#11 0x00000000014ad3f0 in dart::EffectGraphVisitor::VisitSequenceNode (this=<optimized out>, node=<optimized out>)
    at ../../third_party/dart/runtime/vm/compiler/frontend/flow_graph_builder.cc:4004
#12 0x00000000014ad3f0 in dart::EffectGraphVisitor::VisitSequenceNode (this=<optimized out>, node=<optimized out>)
    at ../../third_party/dart/runtime/vm/compiler/frontend/flow_graph_builder.cc:4004
#13 0x00000000014af983 in dart::FlowGraphBuilder::BuildGraph (this=0x7ffd037fbd40)
    at ../../third_party/dart/runtime/vm/compiler/frontend/flow_graph_builder.cc:4462
#14 0x000000000150644b in dart::DartCompilationPipeline::BuildFlowGraph (this=<optimized out>, zone=<optimized out>,
    parsed_function=<optimized out>, ic_data_array=..., osr_id=<optimized out>, optimized=<optimized out>)
    at ../../third_party/dart/runtime/vm/compiler/jit/compiler.cc:174
#15 0x00000000015092ec in dart::CompileParsedFunctionHelper::Compile (this=0x7ffd037fc598, pipeline=0x6c40068)
    at ../../third_party/dart/runtime/vm/compiler/jit/compiler.cc:826
#16 0x000000000150a462 in dart::CompileFunctionHelper (pipeline=<optimized out>, function=..., optimized=<optimized out>,
    osr_id=<optimized out>) at ../../third_party/dart/runtime/vm/compiler/jit/compiler.cc:1017
#17 0x000000000150b0a4 in dart::Compiler::EnsureUnoptimizedCode (thread=0x39933d0, function=...)
    at ../../third_party/dart/runtime/vm/compiler/jit/compiler.cc:1265
#18 0x00000000013b6bba in dart::SourceReport::VisitFunction (this=0x7ffd037fd148, jsarr=0x7ffd037fd0c0, func=...)
    at ../../third_party/dart/runtime/vm/source_report.cc:389
#19 0x00000000013b70d7 in dart::SourceReport::VisitLibrary (this=0x7ffd037fd148, jsarr=0x7ffd037fd0c0, lib=...)
    at ../../third_party/dart/runtime/vm/source_report.cc:482
#20 0x00000000013b7710 in dart::SourceReport::PrintJSON (this=0x7ffd037fd148, js=0x7ffd037fd2d0, script=..., start_pos=..., end_pos=...)
    at ../../third_party/dart/runtime/vm/source_report.cc:519
#21 0x00000000013a3426 in dart::GetSourceReport (thread=<optimized out>, js=0x7ffd037fd2d0)
    at ../../third_party/dart/runtime/vm/service.cc:3004
#22 0x000000000139bcf6 in dart::Service::InvokeMethod (I=<optimized out>, msg=..., parameters_are_dart_objects=<optimized out>)
    at ../../third_party/dart/runtime/vm/service.cc:869
#23 0x000000000139c3f2 in dart::Service::HandleIsolateMessage (isolate=0x39b41b0, msg=...) at ../../third_party/dart/runtime/vm/service.cc:917
#24 0x0000000001225eb8 in dart::IsolateMessageHandler::HandleMessage (this=0x39b3e50, message=0x7ff56c0a3b90)
    at ../../third_party/dart/runtime/vm/isolate.cc:565
#25 0x000000000124f91d in dart::MessageHandler::HandleMessages (this=0x39b3e50, ml=0x7ffd037fe6e8, allow_normal_messages=true,
    allow_multiple_normal_messages=<optimized out>) at ../../third_party/dart/runtime/vm/message_handler.cc:231
#26 0x000000000124fa2e in dart::MessageHandler::HandleNextMessage (this=0x39b3e50) at ../../third_party/dart/runtime/vm/message_handler.cc:290
#27 0x0000000001533d14 in Dart_HandleMessage () at ../../third_party/dart/runtime/vm/dart_api_impl.cc:1664
#28 0x0000000000d975fc in tonic::DartMessageHandler::OnHandleMessage (this=0x3972f00, dart_state=0x39b3440)
    at ../../topaz/lib/tonic/dart_message_handler.cc:115
#29 0x0000000000d54478 in fml::MessageLoopImpl::RunExpiredTasks (this=<optimized out>)
    at ../../third_party/flutter/fml/message_loop_impl.cc:141
#30 0x0000000000d5806a in fml::MessageLoopLinux::Run (this=0x39260c0) at ../../third_party/flutter/fml/platform/linux/message_loop_linux.cc:69
#31 0x0000000000d546ff in fml::MessageLoopImpl::DoRun (this=0x39260c0) at ../../third_party/flutter/fml/message_loop_impl.cc:77
#32 0x0000000000d4c7ae in shell::RunTester (settings=..., run_forever=false) at ../../third_party/flutter/shell/testing/tester_main.cc:207
#33 0x0000000000d4ce67 in main (argc=<optimized out>, argv=<optimized out>) at ../../third_party/flutter/shell/testing/tester_main.cc:271

thanks @jason-simmons

@garymm, I suppose this patch is not needed anymore?
https://github.com/flutter/flutter/raw/packages/flutter_tools/bin/fuchsia_tester.dart
I do not find it at that url

@crelier Sorry, updated the URL to be correct.

Thanks. It looks like this file was committed and does not need to be patched anymore. The files match.
I am getting this exception about not finding Flutter Shell:
Unhandled exception:
Exception: Cannot find Flutter shell at /tmp/fuchsia_testerSTCLMC/bin/cache/artifacts/engine/linux-x64/flutter_tester
#0      throwToolExit (package:flutter_tools/src/base/common.dart:26)
#1      runTests (package:flutter_tools/src/test/runner.dart:78)
<asynchronous suspension>
#2      run (file:///usr/local/google/home/regis/fuchsia/third_party/dart-pkg/git/flutter/packages/flutter_tools/bin/fuchsia_tester.dart:98)
[...]

How do I resolve that?

Pass a fully qualified path to flutter_tester on the command line:
--shell=$PWD/out/x64/host_x64/flutter_tester

Quick update, but no fix yet.
This crash is difficult to debug, because it happens in a spawn process.
With @jason-simmons 's help, I was able to get to a core dump and I observe SourceReport::VisitFunction invoking the compiler (source_report.cc:389) on a function (most probably an async one).
The still unresolved type of a field is causing the crash. Now, the compiler should have reported an error for this bad type or ignored the type in non-checked production mode, but it should not crash. The script fuchsia_tester is invoking dart with --no-preview-dart-2.
I do not see a difference if I add the option --error-on-bad-type, but if I add the option --checked, I get this type error:
Unhandled exception:
type 'DisabledUsage' is not a subtype of type 'Generator' of 'value'
#0      _HashVMBase&MapMixin&&_LinkedHashMapMixin.[]= (dart:collection-patch/dart:collection/compact_hash.dart:250)
#1      new LinkedHashMap.from.<anonymous closure> (dart:collection/linked_hash_map.dart:97)
#2      _HashVMBase&MapMixin&&_LinkedHashMapMixin.forEach (dart:collection-patch/dart:collection/compact_hash.dart:363)
#3      new LinkedHashMap.from (dart:collection/linked_hash_map.dart:96)
#4      new Map.unmodifiable (dart:core-patch/dart:core/map_patch.dart:25)
#5      AppContext.run (package:flutter_tools/src/base/context.dart:138)
<asynchronous suspension>
#6      runInContext (package:flutter_tools/src/context_runner.dart:42)
<asynchronous suspension>
#7      main (file:///usr/local/google/home/regis/fuchsia/third_party/dart-pkg/git/flutter/packages/flutter_tools/bin/fuchsia_tester.dart:35)
#8      _startIsolate.<anonymous closure> (dart:isolate-patch/dart:isolate/isolate_patch.dart:277)
#9      _RawReceivePortImpl._handleMessage (dart:isolate-patch/dart:isolate/isolate_patch.dart:165)

I tried to build a debug version to see if an assert triggers, but nothing happens. I am actually not sure that asserts are enabled. Here are my steps:
$ cd ~/fuchsia
$ rm -rf out
$ fx set x64 out/debug-x64 --args is_debug=true --args use_prebuilt_dart_sdk=false
$ fx full-build
$ ulimit -c unlimited
$ out/debug-x64/host_x64/dart-tools/fuchsia_tester --packages=out/debug-x64/dartlang/gen/topaz/tools/dartfmt_extras/dartfmt_extras_tests_library.packages --shell=/usr/local/google/home/regis/fuchsia/out/debug-x64/host_x64/flutter_tester --test-directory=topaz/tools/dartfmt_extras/test --coverage
$ gdb /usr/local/google/home/regis/fuchsia/out/debug-x64/host_x64/flutter_tester topaz/tools/dartfmt_extras/test/core

Is there a way to specify -O0 in the fuchsia dart build?

Another quick update.
C++ asserts are indeed not enabled in the debug build of dart (see steps above) and I am not sure why.
The unresolved type causing the crash is "Member". It is the type of field "member" of class "IncompleteErrorGenerator" from source fuchsia/third_party/dart/pkg/front_end/lib/src/fasta/kernel/kernel_expression_generator_impl.dart
class IncompleteErrorGenerator extends IncompleteSendGenerator
    with ErroneousExpressionGenerator {
  final Member member;
  final Message message;
[...]

I still do not know why type finalization is not completed when ReportSource is invoking the compiler to compile functions.

Asserts can be enabled in the dart build by adding '--args dart_debug=true' to the fx set command.
Interestingly, some assert triggers while building an 'hello app' example, but the resulting debug build of dart works and even eliminates the issue of this thread:
regis@belenos:~/fuchsia$ out/debug-x64/host_x64/dart-tools/fuchsia_tester --packages=out/debug-x64/dartlang/gen/topaz/tools/dartfmt_extras/dartfmt_extras_tests_library.packages --shell=/usr/local/google/home/regis/fuchsia/out/debug-x64/host_x64/flutter_tester --test-directory=topaz/tools/dartfmt_extras/test --coverage
00:00 +0: ...egis/fuchsia/topaz/tools/dartfmt_extras/test/double_quotes_test.dart     Shell: Do not know weight for: TeXGyreSchola (BoldItalic)
Shell: Do not know weight for: TeXGyreSchola (BoldItalic)
01:51 +2: All tests passed!
Collecting coverage information...                          142ms

The crash is due to a leftover marking of a mixin application class, preventing the class from being finalized by the source reporter, prior to compiling its functions. As observed earlier, an unresolved type of an unfinalized class caused the crash.
A workaround CL is under review: https://dart-review.googlesource.com/c/sdk/+/66022

This isn't at all urgent if you'd rather not put the work-around in.

The workaround is easy enough to remove later.

The marking is not left over, but source coverage is most likely interrupting a set of classes being compiled. The fix is to treat a class marked for parsing as not being compiled yet, but also not to force compilation of its functions.


Failed to push when multiple events were fired within checkInterval

What happened:
If you issue an event to the event register at about the same time, it will be determined that the remote branch has been rewritten and git push will be rejected.
What you expected to happen:
Can be pushed without being rejected
How to reproduce it:
Issue an event to the event register on CI almost at the same time

@inobu Hi, thank you for your issue.
@knanao Could you check this issue?

@nghialv
Sure.
@inobu
I'm sorry for my replying late.
Please let me confirm one point.
Was it the same the piped which handles each event?

@knanao
No, it was'nt.
For example, it can also occur by using different piped at the same time with labels.

Hi, @inobu.
We finally fixed this bug and released a new version v0.32.0.
That's why let me close this one.
Thank you for your report.


Image replacement title property is not output by the pipeline

Description
Alternative title is not output by the pipeline although it is set properly on an image located inside a word document.
Alternative description is output properly as alt attribute on the img tag.
To Reproduce
Steps to reproduce the behavior:

Create a word document in Sharepoint
Add an image in the document
Set the alternative title to "I went through the pipeline"
Preview the document
Render the document as .md and find the title "I went through the pipeline" in the output
Render the document as HTML and see that the title is not in the output

If you can access it, you may also use this word document
Expected behavior
I expect the replacement title value set on an image within a word document to be output as title attribute on the img tag.
Screenshots
The following screenshot shows the alternative title and descriptions set on an image in within a word document

The following screenshot shows the Markdown output of the document that contains the image. The alternative title is present in the output, as expected.

The following screenshot shows that the alternative title is not contained in the HTML output.

Version:
14.21.2
Additional context
https://cq-dev.slack.com/archives/C04RN3CQWBZ/p1683295645721079?thread_ts=1683295547.817699&cid=C04RN3CQWBZ

Opened a PR with the fix and test https://github.com/adobe/helix-html-pipeline/pull/312

@tmaret what is the use case ?

@tripodsan zeiss.[com|de] sets alt and title attributes on img tags. We are porting the news section to Franklin and thus would like to have support for both. Use case is also to close the loop, indeed the Franklin importer supports both attributes but the helix-html-pipeline only supports alt atm.


Add the AFTERBUILD capability

Hi Guys,
I am making images that needs some information from the user at build time to make their stuff, for example we want to provide an NVM image that abstract the user of how their version is installed
For example want our users to have the next kind of images
FROM magic_nvm
ENV NODE_VERSION=4.0.0

So when the image is build we can read that version and make something or install a default
The idea is to have a magic_nvm image like the next
 FROM ubuntu
 RUN install_nvm
 ENV NODE_VERSION=2.0.0
 AFTERBUILD update_nvm_version

I imagine this feature like the ONBUILD but instead of add the lines to begining of the next Dockerfile add to the end.
That feature make sense for you?

Hi!
Please read this important information about creating issues.
If you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.
If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information.
This is an automated, informational response.
Thank you.
For more information about reporting issues, see https://github.com/docker/docker/blob/master/CONTRIBUTING.md#reporting-other-issues

BUG REPORT INFORMATION
Use the commands below to provide key information from your environment:
docker version:
docker info:
uname -a:
Provide additional environment details (AWS, VirtualBox, physical, etc.):
List the steps to reproduce the issue:
1.
2.
3.
Describe the results you received:
Describe the results you expected:
Provide additional info you think is important:
----------END REPORT ---------
#ENEEDMOREINFO

:-1: for magic
With #15182, the user can pass this in at build time.

Hi cpuguy83, I think that the uses of ARG and AFTERBUILD are differents. If I understood with arg you can send parameters on build time. My idea with afterbuild it's a similar behavior than on build (a trigger or command used when the image is used as base of a next one) with the difference that BUILD will run at the begining and AFTERBUILD run at the end. I see ONBUILD as a before hook and AFTERBUILD as an after hook for the next image that use the first one as base image

@geisbruch if I'm understanding this correctly, you want the build of a 'base image' to cause the build of another image to happen, because that other Dockerfile has a "FROM baseImage". Do I have that right?
If so, I would prefer if this were done outside of "docker build" because its kind of odd to have a base image know about everyone that depends on it. Its like the reverse of the Makefile dependency stuff. This means each time someone new references the baseImage, baseImage would need to change. Doesn't sound scalable.

Hi @duglin , I don't think that the base image should change, The only thing that I am proposing it's add an operation similar to ONBUILD but with the difference that instead of run on the begining runs at the end.
For example, we have today an Image that comes with GVM, and we provide in the image a base command to update the grails version. So our uses use the image in the next way:
FROM my_repo/grails:latest
#Configure image to use grails 2.3.8
ENV GRAILS_VERSION=2.2.5
RUN /commands/update_grails_version.sh

That we want to avoid with AFTERBUILD it's the necesity of the line RUN /commands/update_grails_version.sh
So if we can add on our my_repo/grails:latest image a line like AFTERBUILD RUN /commands/update_grails_version.sh we can avoid the necesity of our users to add that RUN line and this ends in a much understable image.
So the end image will be:
FROM my_repo/grails:latest
#HERE RUNS OBBUILD COMMANDS
ENV GRAILS_VERSION=2.2.5
#HERE IS WHERE I WANT AFTERBUILD COMMANDS TO BE RUN

Thanks,
Gabriel.

@cpuguy83 even if #15182 looks pretty cool I think there is still some room for logic in what @geisbruch is asking for. I think the rationale behind ONBUILD could be extended furthermore and one could think of use cases where the image owner might want to execute commands after the child image has been built (clean up tasks, setup of environment variables, etc). If you look at it like that, there's no much difference between and ONBUILD instruction and an AFTERBUILD one. It all comes down to the moment instructions declared on the parent are triggered under the context of a child image build.

This issue was inactive for quite some time, so I think we can close it because most of usecases is supported with buildtime args and adding new commands to dockerfile is extremely hard in terms of support and technical debt.


DSEFix and VirtualBox

There is an issue with DSEFix running on systems with installed VirtualBox software. Since DSEFix uses old virtualbox driver to do it task it attempt to reload actual VBoxDrv and may fail here if the following condifitions are meet:

VirtualBox installed with VirtualBox Networking - thus VirtualBox Bridged Networking protocol installed for available network connections.
VirtualBox USBMon driver is loaded (it references VBoxDrv preventing it unload).

Solution: On systems with VirtualBox installed - disable VirtualBox networking and VBoxUsbMon before running DSEFix:

Temporary shutdown all network connections that uses VirtualBox network protocol, including "VirtualBox Host-Only Network" connection. Reenable them after DSEFix usage. Thus will stop VirtualBox network drivers (VBoxNetAdp, VBoxNetFlt).
Use "net stop vboxusbmon" from elevated command prompt to stop VirtualBox USB monitor. Restart it (if needed) after DSEFix usage, using "net start vboxusbmon" from elevated command prompt.

Short Q'n'A:
Q: Is DSEFix require VirtualBox to be installed?
A: No it doesn't need any VirtualBox installations.
Q: My AV blocked Dsefix, what should I do?
A: Delete your AV. Seriously if you downloaded this tool which is Hacktool and asking such questions, well you should know what you do before.
Q: I got BSOD on Windows 8.1+ while disabling DSE etc.
A: Kernel Patch Protection is the answer. There is no guarantee it won't BSOD you. Simple by design.
Q: It gives me driver loading errors etc.
A: See above VirtualBox issue description.


make_packaged_resource.ps failing with recent GS

I am experiencing a build failure:
jdietrch@saturn:~$ git clone https://github.com/bwipp/postscriptbarcode.git
Cloning into 'postscriptbarcode'...
remote: Enumerating objects: 342, done.
remote: Counting objects: 100% (342/342), done.
remote: Compressing objects: 100% (208/208), done.
remote: Total 6753 (delta 243), reused 207 (delta 134), pack-reused 6411
Receiving objects: 100% (6753/6753), 15.49 MiB | 10.81 MiB/s, done.

Fixed by 851c7f38ddeeac8e4a3c2a278a234a0ccd9e2a3b


Update CI release scripts for VcPkg

From here: microsoft/vcpkg#15984

Do commit, then run vcpkg x-add-version --overwrite-version azure-<xxx>-cpp, then amend commit. We would need vcpkg for that, so we would need to ./bootstrap-vcpkg, which builds it, if it is not installed on build machine. And if it is installed, we would need to also set VCPKG_ROOT to local directory containing the port update, and not the installed location, because vcpkg x-add-version seem to depend on the repo set by VCPKG_ROOT, and not the repo you run if from.

The name of the PR we create needs to be something like "[azure-<xxx>-cpp] $version release" (so that wording works for both initial releases and subsequent updates?), see the commit history in their repo - https://github.com/microsoft/vcpkg/commits/master, everybody start commits with [portname] (in https://github.com/microsoft/vcpkg/pull/16013, PR title was updated by reviewers)

See how we ended up pushing two PRs at the same time. when the second depends on the first to be checked in, https://github.com/microsoft/vcpkg/pull/16013, then https://github.com/microsoft/vcpkg/pull/16014 and https://github.com/microsoft/vcpkg/pull/16020. Is there anything needs to be done to make this go smoother? If that's not technical, and there are human readable instructions for release process somewhere, let's update them to mention this fact.

cc @danieljurek, @RickWinter

Item 2 is also addressed in https://github.com/Azure/azure-sdk-for-cpp/issues/1365

I also think it would be great if the commit message line 2+ was the release changelog, so it would become a commit description in VcPkg commit history, and also we can paste the changelog to PR description. IMO, very useful for the customers.
This is probably too big of a request to sneak into this issue, please let me know if you'd like me to open a new issue for this.

This should go in another issue

Closing. This shipped in February.


Soil Moisture sensor is not available.

for some reason the sensor is unavailable.

debug log
2024-09-03 22:42:09.714 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration scheduler which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-09-03 22:42:09.714 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration waste_collection_schedule which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-09-03 22:42:09.714 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration spook which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-09-03 22:42:09.715 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration meross_lan which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-09-03 22:42:09.715 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration icloud3 which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-09-03 22:42:09.716 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-09-03 22:42:09.716 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration octopus_energy which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-09-03 22:42:09.716 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration battery_notes which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-09-03 22:42:09.717 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration auto_backup which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-09-03 22:42:09.717 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration gardena_smart_system which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-09-03 22:42:09.717 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration browser_mod which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-09-03 22:42:09.718 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration midea_dehumidifier_lan which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-09-03 22:42:09.718 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration wiser which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-09-03 22:42:09.718 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration fontawesome which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-09-03 22:42:09.718 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration ui_lovelace_minimalist which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-09-03 22:42:09.719 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration spook_inverse which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-09-03 22:42:10.710 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'wiser' calls async_forward_entry_setup for integration, wiser with title: WiserHeat and entry_id: 8b929c1b9da8ccf0a3de2fceb5dcc65f, which is deprecated and will stop working in Home Assistant 2025.6, await async_forward_entry_setups instead at custom_components/wiser/__init__.py, line 53: hass.async_create_task(, please create a bug report at https://github.com/asantaga/wiserHomeAssistantPlatform/issues
2024-09-03 22:42:10.727 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'wiser' calls hass.http.register_static_path which is deprecated because it does blocking I/O in the event loop, instead call `await hass.http.async_register_static_paths([StaticPathConfig("/wiser", "/config/custom_components/wiser/frontend", False)])`; This function will be removed in 2025.7 at custom_components/wiser/frontend/__init__.py, line 24: self.hass.http.register_static_path(, please create a bug report at https://github.com/asantaga/wiserHomeAssistantPlatform/issues
2024-09-03 22:42:11.599 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'fontawesome' calls hass.http.register_static_path which is deprecated because it does blocking I/O in the event loop, instead call `await hass.http.async_register_static_paths([StaticPathConfig("/fontawesome/main.js", "/config/custom_components/fontawesome/main.js", True)])`; This function will be removed in 2025.7 at custom_components/fontawesome/__init__.py, line 50: hass.http.register_static_path(, please report it to the author of the 'fontawesome' custom integration
2024-09-03 22:42:11.601 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'fontawesome' calls hass.http.register_static_path which is deprecated because it does blocking I/O in the event loop, instead call `await hass.http.async_register_static_paths([StaticPathConfig("/fontawesome/icons/brands", "/config/custom_components/fontawesome/data/brands", True)])`; This function will be removed in 2025.7 at custom_components/fontawesome/__init__.py, line 58: hass.http.register_static_path(, please report it to the author of the 'fontawesome' custom integration
2024-09-03 22:42:11.607 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'fontawesome' calls hass.http.register_static_path which is deprecated because it does blocking I/O in the event loop, instead call `await hass.http.async_register_static_paths([StaticPathConfig("/fontawesome/icons/pro", "/config/custom_icons", True)])`; This function will be removed in 2025.7 at custom_components/fontawesome/__init__.py, line 69: hass.http.register_static_path(, please report it to the author of the 'fontawesome' custom integration
2024-09-03 22:42:14.266 WARNING (MainThread) [homeassistant.helpers.frame] Detected code that calls async_forward_entry_setup for integration wiser with title: WiserHeat and entry_id: 8b929c1b9da8ccf0a3de2fceb5dcc65f, during setup without awaiting async_forward_entry_setup, which can cause the setup lock to be released before the setup is done. This will stop working in Home Assistant 2025.1. Please report this issue.
Stack (most recent call last):
  File "<frozen runpy>", line 198, in _run_module_as_main
  File "<frozen runpy>", line 88, in _run_code
  File "/usr/src/homeassistant/homeassistant/__main__.py", line 223, in <module>
    sys.exit(main())
  File "/usr/src/homeassistant/homeassistant/__main__.py", line 209, in main
    exit_code = runner.run(runtime_conf)
  File "/usr/src/homeassistant/homeassistant/runner.py", line 190, in run
    return loop.run_until_complete(setup_and_run_hass(runtime_config))
  File "/usr/local/lib/python3.12/asyncio/base_events.py", line 674, in run_until_complete
    self.run_forever()
  File "/usr/local/lib/python3.12/asyncio/base_events.py", line 641, in run_forever
    self._run_once()
  File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1990, in _run_once
    handle._run()
  File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run
    self._context.run(self._callback, *self._args)
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 2161, in async_forward_entry_setup
    _report_non_awaited_platform_forwards(entry, "async_forward_entry_setup")
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1201, in _report_non_awaited_platform_forwards
    report(
  File "/usr/src/homeassistant/homeassistant/helpers/frame.py", line 151, in report
    _LOGGER.warning(msg, stack_info=True)
2024-09-03 22:42:14.269 WARNING (MainThread) [homeassistant.helpers.frame] Detected code that calls async_forward_entry_setup for integration wiser with title: WiserHeat and entry_id: 8b929c1b9da8ccf0a3de2fceb5dcc65f, during setup without awaiting async_forward_entry_setup, which can cause the setup lock to be released before the setup is done. This will stop working in Home Assistant 2025.1. Please report this issue.
Stack (most recent call last):
  File "<frozen runpy>", line 198, in _run_module_as_main
  File "<frozen runpy>", line 88, in _run_code
  File "/usr/src/homeassistant/homeassistant/__main__.py", line 223, in <module>
    sys.exit(main())
  File "/usr/src/homeassistant/homeassistant/__main__.py", line 209, in main
    exit_code = runner.run(runtime_conf)
  File "/usr/src/homeassistant/homeassistant/runner.py", line 190, in run
    return loop.run_until_complete(setup_and_run_hass(runtime_config))
  File "/usr/local/lib/python3.12/asyncio/base_events.py", line 674, in run_until_complete
    self.run_forever()
  File "/usr/local/lib/python3.12/asyncio/base_events.py", line 641, in run_forever
    self._run_once()
  File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1990, in _run_once
    handle._run()
  File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run
    self._context.run(self._callback, *self._args)
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 2161, in async_forward_entry_setup
    _report_non_awaited_platform_forwards(entry, "async_forward_entry_setup")
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1201, in _report_non_awaited_platform_forwards
    report(
  File "/usr/src/homeassistant/homeassistant/helpers/frame.py", line 151, in report
    _LOGGER.warning(msg, stack_info=True)
2024-09-03 22:42:14.270 WARNING (MainThread) [homeassistant.helpers.frame] Detected code that calls async_forward_entry_setup for integration wiser with title: WiserHeat and entry_id: 8b929c1b9da8ccf0a3de2fceb5dcc65f, during setup without awaiting async_forward_entry_setup, which can cause the setup lock to be released before the setup is done. This will stop working in Home Assistant 2025.1. Please report this issue.
Stack (most recent call last):
  File "<frozen runpy>", line 198, in _run_module_as_main
  File "<frozen runpy>", line 88, in _run_code
  File "/usr/src/homeassistant/homeassistant/__main__.py", line 223, in <module>
    sys.exit(main())
  File "/usr/src/homeassistant/homeassistant/__main__.py", line 209, in main
    exit_code = runner.run(runtime_conf)
  File "/usr/src/homeassistant/homeassistant/runner.py", line 190, in run
    return loop.run_until_complete(setup_and_run_hass(runtime_config))
  File "/usr/local/lib/python3.12/asyncio/base_events.py", line 674, in run_until_complete
    self.run_forever()
  File "/usr/local/lib/python3.12/asyncio/base_events.py", line 641, in run_forever
    self._run_once()
  File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1990, in _run_once
    handle._run()
  File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run
    self._context.run(self._callback, *self._args)
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 2161, in async_forward_entry_setup
    _report_non_awaited_platform_forwards(entry, "async_forward_entry_setup")
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1201, in _report_non_awaited_platform_forwards
    report(
  File "/usr/src/homeassistant/homeassistant/helpers/frame.py", line 151, in report
    _LOGGER.warning(msg, stack_info=True)
2024-09-03 22:42:14.272 WARNING (MainThread) [homeassistant.helpers.frame] Detected code that calls async_forward_entry_setup for integration wiser with title: WiserHeat and entry_id: 8b929c1b9da8ccf0a3de2fceb5dcc65f, during setup without awaiting async_forward_entry_setup, which can cause the setup lock to be released before the setup is done. This will stop working in Home Assistant 2025.1. Please report this issue.
Stack (most recent call last):
  File "<frozen runpy>", line 198, in _run_module_as_main
  File "<frozen runpy>", line 88, in _run_code
  File "/usr/src/homeassistant/homeassistant/__main__.py", line 223, in <module>
    sys.exit(main())
  File "/usr/src/homeassistant/homeassistant/__main__.py", line 209, in main
    exit_code = runner.run(runtime_conf)
  File "/usr/src/homeassistant/homeassistant/runner.py", line 190, in run
    return loop.run_until_complete(setup_and_run_hass(runtime_config))
  File "/usr/local/lib/python3.12/asyncio/base_events.py", line 674, in run_until_complete
    self.run_forever()
  File "/usr/local/lib/python3.12/asyncio/base_events.py", line 641, in run_forever
    self._run_once()
  File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1990, in _run_once
    handle._run()
  File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run
    self._context.run(self._callback, *self._args)
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 2161, in async_forward_entry_setup
    _report_non_awaited_platform_forwards(entry, "async_forward_entry_setup")
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1201, in _report_non_awaited_platform_forwards
    report(
  File "/usr/src/homeassistant/homeassistant/helpers/frame.py", line 151, in report
    _LOGGER.warning(msg, stack_info=True)
2024-09-03 22:42:14.272 WARNING (MainThread) [homeassistant.helpers.frame] Detected code that calls async_forward_entry_setup for integration wiser with title: WiserHeat and entry_id: 8b929c1b9da8ccf0a3de2fceb5dcc65f, during setup without awaiting async_forward_entry_setup, which can cause the setup lock to be released before the setup is done. This will stop working in Home Assistant 2025.1. Please report this issue.
Stack (most recent call last):
  File "<frozen runpy>", line 198, in _run_module_as_main
  File "<frozen runpy>", line 88, in _run_code
  File "/usr/src/homeassistant/homeassistant/__main__.py", line 223, in <module>
    sys.exit(main())
  File "/usr/src/homeassistant/homeassistant/__main__.py", line 209, in main
    exit_code = runner.run(runtime_conf)
  File "/usr/src/homeassistant/homeassistant/runner.py", line 190, in run
    return loop.run_until_complete(setup_and_run_hass(runtime_config))
  File "/usr/local/lib/python3.12/asyncio/base_events.py", line 674, in run_until_complete
    self.run_forever()
  File "/usr/local/lib/python3.12/asyncio/base_events.py", line 641, in run_forever
    self._run_once()
  File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1990, in _run_once
    handle._run()
  File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run
    self._context.run(self._callback, *self._args)
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 2161, in async_forward_entry_setup
    _report_non_awaited_platform_forwards(entry, "async_forward_entry_setup")
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1201, in _report_non_awaited_platform_forwards
    report(
  File "/usr/src/homeassistant/homeassistant/helpers/frame.py", line 151, in report
    _LOGGER.warning(msg, stack_info=True)
2024-09-03 22:42:14.273 WARNING (MainThread) [homeassistant.helpers.frame] Detected code that calls async_forward_entry_setup for integration wiser with title: WiserHeat and entry_id: 8b929c1b9da8ccf0a3de2fceb5dcc65f, during setup without awaiting async_forward_entry_setup, which can cause the setup lock to be released before the setup is done. This will stop working in Home Assistant 2025.1. Please report this issue.
Stack (most recent call last):
  File "<frozen runpy>", line 198, in _run_module_as_main
  File "<frozen runpy>", line 88, in _run_code
  File "/usr/src/homeassistant/homeassistant/__main__.py", line 223, in <module>
    sys.exit(main())
  File "/usr/src/homeassistant/homeassistant/__main__.py", line 209, in main
    exit_code = runner.run(runtime_conf)
  File "/usr/src/homeassistant/homeassistant/runner.py", line 190, in run
    return loop.run_until_complete(setup_and_run_hass(runtime_config))
  File "/usr/local/lib/python3.12/asyncio/base_events.py", line 674, in run_until_complete
    self.run_forever()
  File "/usr/local/lib/python3.12/asyncio/base_events.py", line 641, in run_forever
    self._run_once()
  File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1990, in _run_once
    handle._run()
  File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run
    self._context.run(self._callback, *self._args)
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 2161, in async_forward_entry_setup
    _report_non_awaited_platform_forwards(entry, "async_forward_entry_setup")
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1201, in _report_non_awaited_platform_forwards
    report(
  File "/usr/src/homeassistant/homeassistant/helpers/frame.py", line 151, in report
    _LOGGER.warning(msg, stack_info=True)
2024-09-03 22:42:14.921 WARNING (MainThread) [homeassistant.helpers.frame] Detected code that calls async_forward_entry_setup for integration wiser with title: WiserHeat and entry_id: 8b929c1b9da8ccf0a3de2fceb5dcc65f, during setup without awaiting async_forward_entry_setup, which can cause the setup lock to be released before the setup is done. This will stop working in Home Assistant 2025.1. Please report this issue.
Stack (most recent call last):
  File "<frozen runpy>", line 198, in _run_module_as_main
  File "<frozen runpy>", line 88, in _run_code
  File "/usr/src/homeassistant/homeassistant/__main__.py", line 223, in <module>
    sys.exit(main())
  File "/usr/src/homeassistant/homeassistant/__main__.py", line 209, in main
    exit_code = runner.run(runtime_conf)
  File "/usr/src/homeassistant/homeassistant/runner.py", line 190, in run
    return loop.run_until_complete(setup_and_run_hass(runtime_config))
  File "/usr/local/lib/python3.12/asyncio/base_events.py", line 674, in run_until_complete
    self.run_forever()
  File "/usr/local/lib/python3.12/asyncio/base_events.py", line 641, in run_forever
    self._run_once()
  File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1990, in _run_once
    handle._run()
  File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run
    self._context.run(self._callback, *self._args)
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 2161, in async_forward_entry_setup
    _report_non_awaited_platform_forwards(entry, "async_forward_entry_setup")
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1201, in _report_non_awaited_platform_forwards
    report(
  File "/usr/src/homeassistant/homeassistant/helpers/frame.py", line 151, in report
    _LOGGER.warning(msg, stack_info=True)
2024-09-03 22:42:16.257 WARNING (MainThread) [homeassistant.helpers.frame] Detected code that calls async_forward_entry_setup for integration wiser with title: WiserHeat and entry_id: 8b929c1b9da8ccf0a3de2fceb5dcc65f, during setup without awaiting async_forward_entry_setup, which can cause the setup lock to be released before the setup is done. This will stop working in Home Assistant 2025.1. Please report this issue.
Stack (most recent call last):
  File "<frozen runpy>", line 198, in _run_module_as_main
  File "<frozen runpy>", line 88, in _run_code
  File "/usr/src/homeassistant/homeassistant/__main__.py", line 223, in <module>
    sys.exit(main())
  File "/usr/src/homeassistant/homeassistant/__main__.py", line 209, in main
    exit_code = runner.run(runtime_conf)
  File "/usr/src/homeassistant/homeassistant/runner.py", line 190, in run
    return loop.run_until_complete(setup_and_run_hass(runtime_config))
  File "/usr/local/lib/python3.12/asyncio/base_events.py", line 674, in run_until_complete
    self.run_forever()
  File "/usr/local/lib/python3.12/asyncio/base_events.py", line 641, in run_forever
    self._run_once()
  File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1990, in _run_once
    handle._run()
  File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run
    self._context.run(self._callback, *self._args)
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 2161, in async_forward_entry_setup
    _report_non_awaited_platform_forwards(entry, "async_forward_entry_setup")
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1201, in _report_non_awaited_platform_forwards
    report(
  File "/usr/src/homeassistant/homeassistant/helpers/frame.py", line 151, in report
    _LOGGER.warning(msg, stack_info=True)
2024-09-03 22:42:16.573 ERROR (MainThread) [homeassistant.components.sensor] Error adding entity sensor.back_garden_sensor_soil_moisture for domain sensor with platform gardena_smart_system
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 912, in _async_add_entity
    await entity.add_to_platform_finish()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1366, in add_to_platform_finish
    self.async_write_ha_state()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1005, in async_write_ha_state
    self._async_write_ha_state()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1130, in _async_write_ha_state
    self.__async_calculate_state()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1067, in __async_calculate_state
    state = self._stringify_state(available)
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1011, in _stringify_state
    if (state := self.state) is None:
                 ^^^^^^^^^^
  File "/config/custom_components/gardena_smart_system/sensor.py", line 125, in state
    return getattr(self._device, self._sensor_type)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'Sensor' object has no attribute 'soil_moisture'
2024-09-03 22:42:16.577 ERROR (MainThread) [homeassistant.components.sensor] Error adding entity sensor.front_garden_sensor_soil_moisture for domain sensor with platform gardena_smart_system
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 912, in _async_add_entity
    await entity.add_to_platform_finish()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1366, in add_to_platform_finish
    self.async_write_ha_state()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1005, in async_write_ha_state
    self._async_write_ha_state()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1130, in _async_write_ha_state
    self.__async_calculate_state()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1067, in __async_calculate_state
    state = self._stringify_state(available)
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1011, in _stringify_state
    if (state := self.state) is None:
                 ^^^^^^^^^^
  File "/config/custom_components/gardena_smart_system/sensor.py", line 125, in state
    return getattr(self._device, self._sensor_type)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'Sensor' object has no attribute 'soil_moisture'
2024-09-03 22:42:28.174 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved (None)
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1534, in _async_process_registry_update_or_remove
    self.async_write_ha_state()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1005, in async_write_ha_state
    self._async_write_ha_state()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1130, in _async_write_ha_state
    self.__async_calculate_state()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1067, in __async_calculate_state
    state = self._stringify_state(available)
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1011, in _stringify_state
    if (state := self.state) is None:
                 ^^^^^^^^^^
  File "/config/custom_components/gardena_smart_system/sensor.py", line 125, in state
    return getattr(self._device, self._sensor_type)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'Sensor' object has no attribute 'soil_moisture'
2024-09-03 22:42:28.175 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved (None)
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1534, in _async_process_registry_update_or_remove
    self.async_write_ha_state()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1005, in async_write_ha_state
    self._async_write_ha_state()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1130, in _async_write_ha_state
    self.__async_calculate_state()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1067, in __async_calculate_state
    state = self._stringify_state(available)
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1011, in _stringify_state
    if (state := self.state) is None:
                 ^^^^^^^^^^
  File "/config/custom_components/gardena_smart_system/sensor.py", line 125, in state
    return getattr(self._device, self._sensor_type)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'Sensor' object has no attribute 'soil_moisture'
2024-09-03 22:43:02.396 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.octopus_energy_electricity_22j0006288_1591022098690_previous_accumulative_consumption is taking over 10 seconds
2024-09-03 22:43:02.397 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.octopus_energy_gas_e6f23377622200_1354260601_previous_accumulative_consumption is taking over 10 seconds

Hi there, i have a similiar problem since the last release 1.1.5rc. For me the soil humidity entity is not avaiable.

Hallo, i have a problem since the last release 1.1.5rc. For me the soil humidity entity and soil moisture is not avaiable.

Same Problem

...aaand the same.

Same here

plus one...

Also the same for me

crazyfx1 has already recognized the problem. A quick and easy solution is to reventing pr #216 until the library is adapted.
In custom_components/gardena_smart_system/sensor.py change line 29 "soil_moisture": ["%", "mdi:water-percent", SensorDeviceClass.MOISTURE], back to "soil_humidity": ["%", "mdi:water-percent", SensorDeviceClass.HUMIDITY], and restart HA.

Same for me

Hello,
Sorry for the delay, i will create a new version reverting the pr216.
Jérémie

PR #216 has been reverted in  version 1.1.1-rc6 .
Please let me know if everything is working fine now .. my home assistant burned and I will try to fix it this week end.

PR #216 has been reverted in version 1.1.1-rc6 . Please let me know if everything is working fine now .. my home assistant burned and I will try to fix it this week end.

Hi Jérémie,
seems to work for me right now, installed it and the entities are there, just like the manual reversion did.
Thanks for your continued work!
Best
Alexander

all fine here now, I'll close this issue.


Decompose interface interfering and breaking

Hi Eric :)
This issue has been a long-standing thorn in our side:
https://github.com/volatiletech/sqlboiler/issues/803
https://github.com/volatiletech/sqlboiler/issues/607
Problem begins here (I think):
https://github.com/ericlagergren/decimal/commit/50723dcdd23ab847e98361304620c97b0a7e177c
We've been telling people to pin at the last tagged version (v3.3.1) and this works because there hasn't been a new tag in quite a long time (that's the latest).
So two questions/problems:

When might we see a new version of the decimal library? :) I also notice that https://github.com/ericlagergren/decimal/blob/master/go.mod is incorrect (missing /v3 suffix) and so it's not a correct Go module. Is it time for a v4 to correct the semantic import versions? (sqlboiler/authboss both had to do a major version bump to move to Go modules).
Are we sure this decompose implementation works? We're seeing nothing but failures as soon as we change to master.

Just wanted to get the ball rolling on this issue.

I suppose it might make sense to drop decomposer support, or have a separate branch for it. Seems to have caused more trouble than benefits.

@aarondl I'm looking into the issue as well.

Hi,
Is this still being considered?
Is there a way I can help resolve it?
Thanks!

Sorry for the delay. This summer was shot.
I analyzed the problem: https://github.com/golang/go/issues/30870#issuecomment-717358078
I would prefer to update database drivers to support decimal values using the decomposer. But it really depends on what the community want to do.

@kardianos great thanks! Will follow the item there.

@kardianos @ericlagergren we are in dead point now? Seems that database drivers will not support decimal values using the decomposer if I understand everything correctly

Hi team, while I appreciate the great effort to formalize decimal in Go. I really doubt the proposal will go anywhere considering the fact that it has been open for 3 years by now. At this point I think we should simply revert the decompose interface in this repo so that people can get the latest code. It is literally preventing everyone from updating the repo now, and sadly sqlboiler is using a version with the decomposer commit now.

Depending on what sqlboiler thinks, I’m fine with reverting the interface.

Depending on what sqlboiler thinks, I’m fine with reverting the interface.

I cannot speak for sqlboiler, maybe @stephenafamo can comment more. I did move the dependency before that commit to unblock users in the latest version, though they can still update repo manually.
The problem now is that currently sqlboiler will now never be able to use the latest decimal version, and I am not sure how many other framework will trigger this bug. But since this is now a public API, I am also not sure how many code repos are depending on this interface now. Maybe @kardianos will have more insight on this. But if we are convinced that the original proposal won't land and the use of this interface is minimal, there is no reason to keep it.


Remove stale text about documentation being available in English

What's the need to write that line "You're lucky, that documents are available in English" in any other language other than English and later at bottom translating it to English in small letters.
Most of the people who are reading this docs/course are English readers and a very few people who know that language will only be able to grasp that line.
And if someone is viewing this course/docs in mobile, than that line at bottom in small letters is not noticable at first sight. When i saw this slide in first sight then i used Google Translate to translate that line and later i noticed it's translation is written in smaller letters at bottom.
I think it will be better to simply write that line in English only, and keep docs as precise as possible.

Honestly - I'd just remove the statement altogether. I don't think it would have made it through initial review had it been known what it stated

Yeah, this is a joke about the word Kubernetes being Greek.  It was a fine joke for a presentation, but it doesn't work as docs.

/retitle Remove stale text about documentation being available in English

@aj11anuj please edit the issue description to tell people that you're commenting on https://www.kubernetes.dev/docs/onboarding/09-documentation/
It's otherwise really not obvious.

Please see https://github.com/kubernetes/contributor-site/pull/428#issuecomment-1704271344
Best to drop the line altogether, Greek and English.

/approve
/lgtm


aerc: 0.17.0 -> 0.18.0

Description of changes
https://git.sr.ht/~rjarry/aerc/refs/0.18.0
Also migrate to pkgs/by-name.
Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

python3.pkgs -> python3Packages

Thanks, done.

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

1 package built:

aerc

Could you rebase the branch?


Should we disable invalid variable setters and getters?

Maybe in addition to setting the warning we should disable the block.

Yes, you should generally disable invalid variable setters and getters, as it is considered good practice to prevent setting values that could put your object in an inconsistent or invalid state by implementing validation within the setter methods, effectively guarding against incorrect data being assigned to your variables.


v1.3 Implementation: Creating new attribute called PostalCode

Created new attribute Postalcode and updated all the test cases

Please tag your issue(s) to this PR as well.


Error while saving .ref file

I get an error whenever i try to save a board.
I already gave storage permission to the app for koading images.
I am runnging the app on OnePlus 6T

I think this is the same as #1, I just forgot to make a new release.
Could you try 1.0.1 at https://github.com/Ruin0x11/DroidRef/releases?

Works perfectly,
Thank you.
If you could add text annotations and a donation link it would be great.


Remove heartbeats completely

Checklist

[x] CLA is signed

Description of change

Re-awakening an old PR

This should probably have a CHANGES or NEWS entry.

Entries added.  Also, it turns out that this fixes #4856, so I added a reference to that issue as well in the squash commit

Merged.
558ea84743918f7a93bfbfc259f86ad1fa4c8de9 Remove heartbeats completely

Why wasn't the configure option moved to the list of deprecated Configure options. Now if someone explicitly compiles with "no-heartbeat" they will get an error rather than it being ignored - which seems to introduce unnecessary breakage.


github-scm-collector Connection refused

Hi,
i run the github-scm-collector in docker container using config as below

Database Name
database=dashboard
Database HostName - default is localhost
dbhost=<IP_ADDRESS>
Database Port - default is 27017
dbport=27017
Database Username - default is blank
dbusername=db
Database Password - default is blank
dbpassword=dbpass
Collector schedule (required)
github.cron=0 0/5 * * * *
github.host=http://<IP_ADDRESS>:8000
Maximum number of days to go back in time when fetching commits
github.commitThresholdDays=15

then i use the hygieia UI create a team dashboard, and Code Repo info is

but the github-scm-collector has error:

2016-08-18 14:30:00,102 ERROR c.c.d.collector.DefaultGitHubClient - I/O error on GET request for "http://<IP_ADDRESS>/api/v3/repos/8000/GengWeifeng/ku8manager-cluster/commits?sha=master&since=2016-08-18T14:20Z":Connect to <IP_ADDRESS>:80 [/<IP_ADDRESS>] failed: Connection refused; nested exception is org.apache.http.conn.HttpHostConnectException: Connect to <IP_ADDRESS>:80 [/<IP_ADDRESS>] failed: Connection refused:http://<IP_ADDRESS>/api/v3/repos/8000/GengWeifeng/ku8manager-cluster/commits?sha=master&since=2016-08-18T14:20Z

why is is?

the uri is my private gitlab, does it not support gitlab?

I'm not 100% sure on this, but I don't think the github collector supports gitlab - the gitlab API is likely not compatible with the github API. In order to add support for gitlab, you'd have to add a new collector.

ok, thank you! I will try to add a new collector to support gitlab!
best wishes!

Hi,
I am also facing same issue where after giving correct details and key getting below error
ERROR c.c.d.collector.DefaultGitHubClient - I/O error on GET request for "https://api.github.com/repos/mcdcorp/opentest/commits?sha=master&since=2018-02-22T15:10Z":Connect to api.github.com:443 [api.github.com/<IP_ADDRESS>, api.github.com/<IP_ADDRESS>] failed: Connection refused: connect; nested exception is org.apache.http.conn.HttpHostConnectException: Connect to api.github.com:443 [api.github.com/<IP_ADDRESS>, api.github.com/<IP_ADDRESS>] failed: Connection refused: connect:https://api.github.com/repos/mcdcorp/opentest/commits?sha=master&since=2018-02-22T15:10Z

I solved this issue by adding a new collector to support gitlab, because the interfaces are different between the github and gitlab.


[AutoPR cost-management/resource-manager] [Hub Generated] Review request for Microsoft.CostManagement to add version preview/2019-05-01-preview

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/5881

(message created by the CI based on PR content)

Codecov Report

Merging #5136 into restapi_auto_cost-management/resource-manager will increase coverage by 0.14%.
The diff coverage is n/a.

@@                                Coverage Diff                                @@
##           restapi_auto_cost-management/resource-manager    #5136      +/-   ##
=================================================================================
+ Coverage                                          49.01%   49.15%   +0.14%
=================================================================================
  Files                                               6508     6456      -52
  Lines                                             182544   181157    -1387
=================================================================================
- Hits                                               89472    89055     -417
+ Misses                                             93072    92102     -970

Impacted Files
Coverage Δ

...osdb/azure/mgmt/cosmosdb/models/cosmos_db_enums.py
100% <0%> (ø)
:arrow_up:

...osmosdb/azure/mgmt/cosmosdb/models/resource_py3.py
100% <0%> (ø)
:arrow_up:

...s/database_account_create_update_parameters_py3.py
100% <0%> (ø)
:arrow_up:

...azure/mgmt/cosmosdb/models/database_account_py3.py
100% <0%> (ø)
:arrow_up:

...cassandra_keyspace_create_update_parameters_py3.py

...azure/mgmt/cosmosdb/models/mongo_index_keys_py3.py

...s/gremlin_database_create_update_parameters_py3.py

.../azure/mgmt/cosmosdb/models/sql_container_paged.py

...b/azure/mgmt/cosmosdb/models/sql_database_paged.py

...ure/mgmt/cosmosdb/models/cassandra_keyspace_py3.py

... and 48 more

Continue to review full report at Codecov.

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


Switch to oss_lib for configuration

Coverage decreased (-2.7%) to 82.623% when pulling 415767a8af9a16437ab3f029fd36a70a759fb2bf on config into a9a6a807a4b0fa3260432e2a8321a3c65865d9f6 on master.

Coverage decreased (-2.7%) to 82.623% when pulling e383833a56b778cd089fb4e28e1c213c1c649699 on config into a9a6a807a4b0fa3260432e2a8321a3c65865d9f6 on master.

Coverage increased (+0.9%) to 86.23% when pulling 3fa50d00ec43a7bdebe2a85cbfaf874392300ad9 on config into a9a6a807a4b0fa3260432e2a8321a3c65865d9f6 on master.

Coverage increased (+0.9%) to 86.23% when pulling a0682a1e339c919f72af5168b19db637a1d9585a on config into a9a6a807a4b0fa3260432e2a8321a3c65865d9f6 on master.


prefix ID issue again (Protein -> Gene)

Like #116 and #122, with MyGene.info, querying Protein -> Gene.
When querying from Protein -> Gene with a UNIPROTKB or ENSEMBL ID, the query fails because the requested id in q sent to MyGene.info includes the prefix, which MyGene doesn't recognize. Compare the query message sent by BTE to the correct query for MyGene.info below:

What a successful query directly to MyGene.info looks like, see the q doesn't have a prefix:

fields: ensembl.gene
Request body:
{
  "q": "O15131",
  "scopes": "uniprot.Swiss-Prot"
}

OR

{
  "q": "ENSP00000396791",
  "scopes": "ensembl.protein"
}

Query sent by BTE: see that the q has a prefix. BTE doesn't get any results from doing this.

    {
      "timestamp": "2021-03-26T05:03:13.019Z",
      "level": "DEBUG",
      "message": "call-apis: Succesfully made the following query: {\"url\":\"https://mygene.info/v3/query\",\"params\":{\"fields\":\"ensembl.gene\",\"species\":\"human\"},\"data\":\"q=UNIPROTKB:O15131&scopes=uniprot.Swiss-Prot\",\"method\":\"post\",\"timeout\":50000}",
      "code": null
    },

OR

    {
      "timestamp": "2021-03-26T05:08:24.280Z",
      "level": "DEBUG",
      "message": "call-apis: Succesfully made the following query: {\"url\":\"https://mygene.info/v3/query\",\"params\":{\"fields\":\"ensembl.gene\",\"species\":\"human\"},\"data\":\"q=ENSEMBL:ENSP00000396791&scopes=ensembl.protein\",\"method\":\"post\",\"timeout\":50000}",
      "code": null
    },

You label UNIPROTKB wrong in MyGene SmartAPI. Should be UniProtKB


Ver1.4.5 keep crashing

It's just happened on this week.
At first I was thinking it's a hacking tool to force Player-Displayer to crash (from the opponent players when I am fighting to)
But today the Player-Displayer crash almost every player that I am fight to (some players it crashed more than 1 time in just 1 match)
I started to think that the force crashing may not coming from the players but it may came from BANDAI itself??
Here is the list of players that I fight today (censor name and ID for their privacy)
It crashed almost every player that it so weird...
Dar***			Asuka<PHONE_NUMBER>4286***)			warrior 270+ wins (force displayer to closed)
YOU_MOM_IS_M***			Fahkumram<PHONE_NUMBER>8389***)			fighter 100+ wins laggg
O***			Bob<PHONE_NUMBER>4108***)			not a newbie A+AA (force displayer to closed)
?***			Lucky Chloe<PHONE_NUMBER>7539***)			not a newbie (force displayer to closed many times)
ans***			Akuma<PHONE_NUMBER>7136***)			initiate A+AA (force displayer to closed many times)
leowye***			Lars<PHONE_NUMBER>2543***)			not a newbie (force displayer to closed)
crock***			Jin<PHONE_NUMBER>1749***)			seiryu 1k+ wins (force displayer to closed)

Update on today morning,
I played for 1 and a half hour without crashing..
Maybe it's a hacking tool from some player that seek for people who use this app and crash them.
I think during I post this message that hacker is still sleeping.

Thank you for you comments! It should be fixed now in the latest release.
And I don't think that there is a hacker that has nothing better to do than to spend their time annoying player-displayer users by crashing their displayer and also sometimes takes naps in between lol.
But if the hacker does exist, they must have stopped doing it or they were asleep during my last testing session: I annoyingly did not get a single crash in more than 2 hours of testing last weekend using the non-updated version of the displayer. (I was hoping I'd get to test the latest version a bit more.)


Paint in air with both hands at the same time

Try out to duplicate our Rune Maker and put the other input setting to the other hand and paint two different runes at the same time.


feat(device_info_plus)!: migrate to package:web

Description

Replace calls to dart:html by the equivalent with the package:web.
Tested on Chrome + macOS
Set web version to >=0.5.0 <=0.6.0 to be compatible with any upcoming web release.
Set min Dart sdk version to 3.3.0 in package, as it is the min version of web 0.5. This is required since Navigator is only available from version 0.5, so it is not possible to be compatible with older versions of web.
Note: The property deviceMemory seems to be missing in the current web implementation. The corresponding ticket has been created in the package:web repo: https://github.com/dart-lang/web/issues/192 This property is nullable (int?) so it is not a blocker, however, users relying on this property will be affected. A solution is possible by creating our own deviceMemory extension.

Related Issues

Closes #2601

Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I titled the PR using Conventional Commits.
[x] I did not modify the CHANGELOG.md nor the plugin version in pubspec.yaml files.
[x] All existing and new tests are passing.
[x] The analyzer (flutter analyze) does not report any problems on my PR.

Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?

[x] Yes, this is a breaking change (please indicate that with a ! in the title as explained in Conventional Commits).
[ ] No, this is not a breaking change.

Sounds good to me! I will merge this one now


Add prompt to User Profile

Description

Add prompt to ChatApi.UserProfile schema
Update ChatApiWeb.UserView
Update React settings/UserProfile component

Looks good thank you


ReadOnly.

I would kill for a ReadOnly mode.

Just added and enabled flag in b58f58c6. No need to kil! :)


sidecar: inform remote side about cancellation

Fixes https://github.com/lightninglabs/pool/issues/295.
Fixes https://github.com/lightninglabs/pool/issues/294.
This PR fixes the issue that when one side of a sidecar channel offering cancels the ticket, the other side isn't informed about it. This leads to follow-up errors on restarts and subsequent ticket submissions.
We solve this by sending a message to the other side if we are the cancelling party.
Because we send the message over the mailbox, we cannot remove it in that case.

Gonna land this so we can proceed with some of the dependent merges, ideally can address those lingering commits in a follow up change


[docs] Improve the left side-nav

It was an opportunity to work on 3 problems at the same time:
1. Fix w3 validator
The warning was present on all the pages and was buried all the other issues (x81)

https://validator.w3.org/nu/?doc=https%3A%2F%2Fnext.material-ui.com%2Fcomponents%2Fslider-styled
There are still 3 issues related to navigation (edit page, previous page, and next page) but that's for another day.
2. Update the design
It's closer to the Material Design specification https://material.io/components/navigation-drawer. I also wanted the design to better support more levels of nesting and more items.
Before

After

I have used the following as inspiration too:

https://stripe.com/docs/api/accounts
https://tailwindcss.com/docs/upgrading-to-v1
https://next.vuetifyjs.com/en/styles/content/
https://mail.google.com
https://ionicframework.com/docs/api/input

3. Improve the rendering performance
I was getting frustrated at the time it takes to open the drawer on mobile and the time it takes to click on TOCs hash link. In the following benchmark in development, opening the drawer is about x2 faster. The main change is to use fewer React components.
Before

After
e
The performance for changing the hash is also improved but less significantly as the rendering time of the main body of the page stays the same. In dev:
Before

After

The performance gain is negligent

@eps1lon Yeah, it seems that the performance gain of reducing the usage of components decreases significantly between dev and production. I'm happy to learn that! Thanks for testing it :). I was lazy (didn't want to wait for a build on my local env).

the usefulness of dog-feeding

What is there to dog feed? From what I understand, we were using the List component that is meant to display a list of items on mobile: https://material.io/components/lists for navigation. This usage is questionable is not wrong.
At best, the new style could be later transformed into standalone https://material.io/components/navigation-drawer components. We track this in #15107.

Not keen on the lack of a hover indicator on the top level items; and with no focus indicator, keyboard navigation is impossible.

@mbrookes Updated


Remove dependency on nordsoftware/lumen-doctrine

LGTM

@soderluk we don't actually depend on nordsoftware/lumen-doctrine-mongodb-odm either, we actually depend directly on doctrine/mongodb-odm. I'll change that too.

IMO we merge this and tag 1.1.4 since we've only changed suggests


Improve testing documentation

Context
We're improving the documentation for developers testing GOV.UK Pay, to make it more user-focused and concise.
Changes proposed in this pull request
General improvements to the content on https://docs.payments.service.gov.uk/testing_govuk_pay/, to:

clarify integration testing and which accounts to use
remove the mock payment section
rename the page to 'Testing your integration' so it better reflects the content
remove the link on the security page (as clicking through doesn't provide users with more information about using http instead of https on their test account)

Guidance to review
Please check everything's factually accurate.

Hi @heathd - could you check the minor 2i tweaks in commit https://github.com/alphagov/pay-tech-docs/pull/326/commits, to make sure everything's still factually accurate?

👍 looks good


Update examples to correctly register dependencies

This published example didn't register the dependency correctly. The test framework has been updated to handle this, and the examples are update to remove .EXTERNALMODULEDEPENDENCIES from the script metadata as it should not be used for this purpose (in this particular case).

This change is

Codecov Report

Merging #433 into dev will decrease coverage by <1%.
The diff coverage is n/a.

@@         Coverage Diff         @@
##            dev   #433   +/-   ##
===================================
- Coverage    73%    72%   -1%
===================================
  Files        27     27
  Lines      3995   3995
  Branches      4      4
===================================
- Hits       2921   2898   -23
- Misses     1070   1093   +23
  Partials      4      4


Empty map when following UWP Getting Started

When following the UWP Getting Started (https://github.com/Mapsui/Mapsui/blob/feature/add-getting-started-uwp/docfx/documentation/getting-started-uwp.md) using Mapsui.Native 3.0 rc 2 I get an empty (white) map.
There is a compiler warning about Svg.Skia:
Warning		Found conflicts between different versions of "Svg.Skia" that could not be resolved.
There was a conflict between "Svg.Skia, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=dafe96fe6c845a74" and "Svg.Skia, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=dafe96fe6c845a74".
    "Svg.Skia, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=dafe96fe6c845a74" was chosen because it was primary and "Svg.Skia, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=dafe96fe6c845a74" was not.
    References which depend on "Svg.Skia, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=dafe96fe6c845a74" [C:\Users\btemm\.nuget\packages\svg.skia\0.5.0\lib\netstandard2.0\Svg.Skia.dll].
        C:\Users\btemm\.nuget\packages\svg.skia\0.5.0\lib\netstandard2.0\Svg.Skia.dll
          Project file item includes which caused reference "C:\Users\btemm\.nuget\packages\svg.skia\0.5.0\lib\netstandard2.0\Svg.Skia.dll".
            C:\Users\btemm\.nuget\packages\svg.skia\0.5.0\lib\netstandard2.0\Svg.Skia.dll
    References which depend on "Svg.Skia, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=dafe96fe6c845a74" [].
        C:\Users\btemm\.nuget\packages\mapsui\3.0.0-rc.2\lib\netstandard2.0\Mapsui.Rendering.Skia.dll
          Project file item includes which caused reference "C:\Users\btemm\.nuget\packages\mapsui\3.0.0-rc.2\lib\netstandard2.0\Mapsui.Rendering.Skia.dll".
            C:\Users\btemm\.nuget\packages\mapsui\3.0.0-rc.2\lib\netstandard2.0\Mapsui.Rendering.Skia.dll
            C:\Users\btemm\.nuget\packages\mapsui.native\3.0.0-rc.2\lib\uap\Mapsui.UI.Uwp.dll	App11

When installing Svg.Skia version <IP_ADDRESS> the map is correctly displayed.

ah! i ran into the same issue a few days ago. This is actually a serious flaw that we had in our documentation for quite a while. Any new user that would try this would move on to something else. If even the gettings started doesn't work ....
The problem is that the user-agent of BruTile is blocked by openstreetmap. Probably someone used BruTile to build a tool to scrape the osm tiles and as a consequence the user-agent got blocked.
I added a remark to the FAQ (before I knew the problem was also in our getting started). I should add the solution as well.
https://mapsui.com/documentation/faq.html#the-openstreetmap-layer-does-not-show.
Solution:
Is to use your own user-agent. This is allowed in the new version of BruTile (which is not used by the current released Mapsui). Or you can add the OpenStreetMap utility in Mapsui itself (better).
MyMapControl.Map.Layers.Add(OpenStreetMap.CreateTileLayer("your-user-agent"));

More improvements

Perhaps it is possible to request the name of the main application and use that as part of the user agent.
We should also update the FAQ with the code to use.

I've used the useragent:
MapControl.Map.Layers.Add(OpenStreetMap.CreateTileLayer("your-user-agent"));

I guess it's something with Svg.Skia dependencies.

From the messages I think it is a SVG.Skia problem as @bertt told. We use packages with two different versions: 0.5.0 and 0.5.7.

ohw, I write a long story without even reading the error message 😳
I don't see a 'consolidate' issue with the nugets. So perhaps some of the packages we use has another version as reference.
Tol solve this you need to add a version Svg.Skia to the head project, but that is not what you want in a tutorial. Perhaps it helps if we add Svg.Skia to the UWP UI project.

What if you create this getting started within the Mapsui solution, without a nuget reference?

I have opened PR #1215 to fix this ...

@bertt Can you confirm that this has been fixed?

tested with 3.0.0-rc4 and it works now. Closing issue


🐛 Bug Report: scaffolder-node plugin's gitHelper fails to create a new branch

📜 Description
scaffolder-node plugin createBranch function is checking out to a non-existing branch instead of creating the branch. It looks like it's using the checkout function instead of the branch function.
👍 Expected behavior
It should create a new branch instead of trying to checkout to an existing branch.
👎 Actual Behavior with Screenshots
It actually tries to checkout to a branch, and assumes that the branch exists.
👟 Reproduction steps

Write a code that uses @backstage/plugin-scaffolder-node createBranch function.
Use a ref branch name that doesn't exist yet in the repository.
The function should throw an error that the branch doesn't exist.

📃 Provide the context for the Bug.
Please see my PR here: https://github.com/backstage/backstage/pull/26963
🖥 Your Environment
No response
👀 Have you spent some time to check if this bug has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
Yes I am willing to submit a PR!

What's the error you're seeing when the checkout method is called without an existing branch name?

Here's a sample output of the code below when I use the function on one of my custom scaffolder action:
await createBranch({
  dir: 'clonedirhere',
  ref: 'testCreateBrn',
  auth: {
	username: 'user',
	password: token
  },
  logger: ctx.logger
})

This is also the same output when using the deprecated backend-common git:
const git = Git.fromAuth({
  username: 'user',
  password: token,
  logger: ctx.logger,
});
await git.checkout({ dir: 'clonedirhere', ref: 'testCreateBrn' });


Improve quality score display in console when the score is less than 10

Ah sorry just saw this pull request looks fine, can't you use the .PadRight() method instead?


fix(resources): kube handles mounted secret update so remove sha for secret

https://github.ibm.com/IBMPrivateCloud/roadmap/issues/39669

Tested with splunkCA.pem. Fluentd pod was able to pick up updated secret without restart


Compiling from source missing ParserConstants.java and Token.java in master

Compiling from source missing ParserConstants.java and Token.java in master. These files are not in src/java/bsh . I am missing some files which is generated by javacc that ar missing in master. Are they not checked in....

Only the modified sources originally generated by javacc are being source controlled. If you are using maven the pom includes a javacc plugin to generate the outstanding sources if required.
The preferred method to build the sources are with:
mvn install

These files, generated by javacc and jjtree, will be located at target/generated-sources from where they are compiled and included in the distribution.
Having to guess why this is a problem for you:
You can add these generated sources to your IDE source path, if this is why you are having problems. If you are manually generating the javacc parser source these sources will need to be included accordingly.
More information about what exactly you are trying to do is required if the above stabs at guessing your problem missed.

Will do so just want use the latest version of beanshell in back office
system that Im building
On Wed, 07 Aug 2019, 21:13 Nick Lombard<EMAIL_ADDRESS>wrote:

Only the modified sources originally generated by javacc are being source
controlled. If you are using maven the pom includes a javacc plugin to
generate the outstanding sources if required.
The preferred method to build the sources are with:
mvn install
These files, generated by javacc and jjtree, will be located at
target/generated-sources from where they are compiled and included in the
distribution.
Having to guess why this is a problem for you:
You can add these generated sources to your IDE source path, if this is
why you are having problems. If you are manually generating the javacc
parser source these sources will need to be included accordingly.
More information about what exactly you are trying to do is required if
the above stabs at guessing your problem missed.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/beanshell/beanshell/issues/567?email_source=notifications&email_token=AHJ4DF2MLREOTA255JCVMPDQDMNHLA5CNFSM4IJK4CVKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3ZNVMQ#issuecomment-519232178,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHJ4DFZQARRFP4IHMUBVK7DQDMNHLANCNFSM4IJK4CVA
.

Feel free to shout if you have and problems!
Closed: resolved


Object proptype is shown in addon-info proptable

What I did
Corrects this issue.

Can we just render Object string for that instead?

Live preview


chore(blog): 2024 Q1 docs report

During Q1 2024, AsyncAPI Docs had a total of 26,923 sessions and 8,128 unique users.

/rtm


Remove BOM that breaks JSON output parsing

WordPress/Sniffs/WhiteSpace/OperatorSpacingSniff.php contains byte-order marks before the opening PHP tags. This causes output reports to also include this output. Unfortunately this breaks parsing of the JSON reports (See https://github.com/Block8/PHPCI/issues/768).
This patch just removes the extra characters before the opening PHP tags.

Thanks!

Nice catch Lee :+1:

No worries guys - confused me for a bit, thanks for the work on this - it's a great resource!


Checking if arg is null in RemovePII

Fixes #1406

Looking at the issue description, it might be worth adding a test to WsFederationMessage:FromQueryString with an input of empty string and null to prove that the code matches the description on the method. Specifically the remarks section on FromQueryString.


Add autoscaling e2e test

As part of getting the test green the following fixes were needed:

Bump autoscaler image to bring changes for the autoscaler to be able to restrict informers to a particular namespace so our rbac role is valid.
Fixed creation timestamp check and unit tests for SetMachineDeploymentReplicas that was otherwise stepping on the replicas value set by the autoscaler.
Change the Autolscaling.Min/Max fields to not be pointers since there's no need to diff between nil and 0.

/hold

Need to dig into scaling down a little more since pods with local storage e.g grafana and image-registry and pos with anti-affinity rules make scaling down not reproducible.
/test e2e-aws-pooled

/test e2e-aws-pooled

/test e2e-aws-pooled

/test e2e-aws-pooled

/test e2e-aws-pooled

/test e2e-aws-pooled

/test e2e-aws

/test e2e-aws

/hold cancel

/lgtm
/hold
Great addition, thanks! Leaving a hold in case others wanted to chime in, feel free to remove when ready

/hold cancel
lgtm


Add warning for privileged run in case when user is set to root via options

Closes #189

It's just a warning and doesn't prevent starting the server. Should I change the message for this case?

 Setting it explicitly to root could be a way to silence the warning.


Fix install ruby instructions

Changed the ruby installation instructions for contributors. Resolves #9069.

This change is

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/65099d891fdcafe1868b797edebed983408a7a6a/
Edited pages:

CONTRIBUTING.md

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/2cd06a3a6c4b64a2f61017992c80a5ec90c40aed/
Edited pages:

CONTRIBUTING.md

Thanks for catching that!


Adds service register functions.

This provides a more principled way for unit tests to ensure that
required services are installed (currently they have to import the
service file just for its side-effects, which isn't heaps nice).

I don't really see what this changes; importing the files still executes the same code, right? If the exported functions are automatically called when you import them, what difference does it make?

I don't really see what this changes; importing the files still executes the same code, right? If the exported functions are automatically called when you import them, what difference does it make?

Currently my unit test fails because the services it requires (random and clock) are not registered. My options are either:
Import with side-effects:
// Import service files for their side-effects (which registers the services):
import '../../services/clock-service.js';
import '../../services/random-service.js';

Or do something more self-documenting:
import {registerClockService} from '../../services/clock-service.js';
import {registerRandomService} '../../services/random-service.js';

before(() => {
  registerClockService();
  registerRandomService();
});

I much prefer the second approach, since it's much more explicit what is going on, imo.

As discussed offline, I will close this PR and we will just keep using the import-with-side-effects method.


Make sorting trigger only on the sort caret when using custom header with other clickable elements

Problem
When sorting is enabled on a column, clicking anywhere within the header element triggers sorting. If the header contains clickable elements like buttons or checkboxes, clicking these also triggers sorting.
codesandbox
https://codesandbox.io/s/brave-mccarthy-e4oed
This behaviour seems unintended when the headerFormatter is meant for adding pretty much anything into the header, including other elements that respond to clicks.
No workarounds
The onSort function is attached to the  element's onClick attribute so there doesn't seem to be any workaround possible with version 3.2.1.
See https://github.com/react-bootstrap-table/react-bootstrap-table2/blob/be916d81a3c4e0a54aae8e7c622174ea8f94bac6/packages/react-bootstrap-table2/src/header-cell.js#L76
Suggested fix
Perhaps an additional optional property given to columns like sortOnCaretOnly which moves the executing of onSort to the onClick attribute on the sortSymbol? This would also add the additional requirement of giving the sortCaret function onSort as a third argument which the user then needs to handle, if they're using sortCaret on a column.

@jhhr you can just call e.stopPropagation(); to avoid sorting happen when clicking on your custom button.


use root project settings for compileSdkVersion, buildToolsVersion, etc

This allows the project to upgrade to a newer android SDK version (as required by React Native 0.5.6)

can confirm this works for latest version of React Native (0.56.0)

Is there anything stopping this from being merged into a new release?

I would like to confirm that this fix works. It would be nice for it to be merged in this project.

This package was updated recently. It would have been great if this PR was included.

The build is broken without this change:
Execution failed for task ':react-native-version-number:lint'.
> Lint found errors in the project; aborting build.

  Fix the issues identified by lint, or add the following to your build script to proceed with errors:
  ...
  android {
      lintOptions {
          abortOnError false
      }
  }
  ...

  Errors found:

  /Users/dwas/Projects/Bosch/pro360.mobile.inventory-app/node_modules/react-native-version-number/android/build.gradle:10: Error: Google Play requires that apps target API level 26 or higher.
   [ExpiredTargetSdkVersion]
          targetSdkVersion 22
          ~~~~~~~~~~~~~~~~~~~


Make the local docs build better reflect real sphinx projects

It has happened a few times now where we can't properly test out CSS fixes locally because we don't have any files that use the typical Sphinx API Reference setup. It would be great if we could add an example API Reference with a dummy Class, with other nested classes and methods.
pages we need:

top level module page, e.g. https://qiskit.org/documentation/apidoc/circuit.html
an API Class, e.g. https://qiskit.org/documentation/stubs/qiskit.circuit.ClassicalRegister.html#qiskit.circuit.ClassicalRegister
a method within a class, e.g. https://qiskit.org/documentation/stubs/qiskit.circuit.Instruction.copy.html#qiskit.circuit.Instruction.copy

some things I've noticed would be good to add (edge cases that have caused css issues in the past)

dispatch functions
typing overload functions
examples sections in classes

Thanks for the comment, Abby! I added this to the Furo milestone because it will allow us to better verify that we aren't introducing styling regressions for these edge cases when we switch.


DPL-258 adding baracoda support

Initial work moving plate barcode creation over to baracoda from plate_barcode
Closes #
Changes proposed in this pull request:

...

Story review 21/04/22
Baracoda side:

[ ] Review child barcode table
[ ] Add every child barcode created to the barcodes table
[ ] Check tests
[ ] API key for sequencescape barcodes

Sequencescape side:

[ ] Minitest (ongoing)
[ ] Linting
[ ] Cucumber tests (ongoing)
[ ] Check Integration test
[ ] Do we want DN plates to be stamped to WD or to DN-1 or to SQPD-1?
[ ] Review SBCF and the handling of legacy plate barcodes

Deployment side

[ ] Add prefix config to baracoda app config files for each environment - e.g SQPU, SQPT, SQPP
[ ] Add plate_barcode_prefix and baracoda_api to sequencescape config for each environment


NameError: name 'usb_port' is not defined

Been getting some weird issues starting the add-on. I defined my device ID device_id: 0bda:2838 in the config, but been getting this:
Traceback (most recent call last):   File "/usr/bin/rtlamr2mqtt.py", line 499, in <module>     reset_usb_device(usb_port) NameError: name 'usb_port' is not defined
The add-on finds the radio too:
[2022-11-03 14:26:22] RTL SDR Device 0bda:2838 found on USB port 001:006 - Index: 0
If I just leave the device ID as single, I get a different issue:
[2022-11-03 14:30:47] RTL SDR Device 0bda:2838 found on USB port 001:006 - Index: 0 Traceback (most recent call last):   File "/usr/bin/rtlamr2mqtt.py", line 439, in <module>     elif re.match(r"(^[0-9]{3}:([0-9]{3}$)))", usb_device_id) is not None:   File "/usr/local/lib/python3.10/re.py", line 190, in match     return _compile(pattern, flags).match(string)   File "/usr/local/lib/python3.10/re.py", line 303, in _compile     p = sre_compile.compile(pattern, flags)   File "/usr/local/lib/python3.10/sre_compile.py", line 788, in compile     p = sre_parse.parse(p, flags)   File "/usr/local/lib/python3.10/sre_parse.py", line 969, in parse     raise source.error("unbalanced parenthesis") re.error: unbalanced parenthesis at position 23

I'm having the same issue, I just installed this today after upgrading to 2022.11.1.

Yea, I am getting that too. @allangood  do you know what could have caused this in the last update?

Looks like I've pushed a change that I was still working on it :(
Sorry about that.
I will be working on fixing this ASAP and will update here when the new PR came through.

It should be fixed now. Sorry about that :(
PR #170

trying to update, but its not pulling the latest image. Itll take time before its updated for allangood/rtlamr2mqtt:main, or should I use a tag other than main?

It should be fixed now. Sorry about that :( PR #170

Works for me! Thanks for all the hard work. I even got the water meter on the new energy dashboard!!


Add alias replaceprime for mapprime

Add an alias replaceprime = mapprime, to match with the notation replacetags.

Closed by #540.


Add utilities in LowStar.ConstBuffer

This small PR adds a few utilities in LowStar.ConstBuffer, mostly to reason about null pointers

@protz the PR about constant buffers


Question about components UMS

While investigating the Athenz UI, It seems to rely on a component called UMS, but it is not published as a server component of Athenz. Could you please provide information on the functionality of UMS, and whether there are plans to make them publicly available in the future? I would appreciate any guidance on this matter.

UMS is the user access management system. it uses athenz to configure what users are provisioned on hosts for ssh login and sudo access. it's heavily dependent on sshca - you'll some of the those components being by the Yahoo Paranoids organization (https://github.com/theparanoids). Once all those components are open-sourced, we'll look into open sourcing UMS as well.

Thank you for taking the time to provide such a thorough response regarding the question about components UMS.