[flutter_tools] fix pm serve ipv6 linklocal addr issue

Description
the patch from https://github.com/flutter/flutter/commit/c5554cdf41cacd1cbd709a6deafe7e0be535c5cc removed the trailing information from the ipv6 addr, which is actually required for binding an ipv6 linklocal address in golang https://golang.org/pkg/net/#Dial. This patch reverts the changes that stripped out the require information, as well as reverting the change that escaped the % sign that breaks go's ipv6 addr resolution mechanism.
Related Issues
It is a trivial change so I didn't create an issue.
Tests
I added the following tests:
No test is included currently since the related part of the source is being actively changed.
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I signed the CLA.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I updated/added relevant documentation (doc comments with ///).
[x] All existing and new tests are passing.
[x] The analyzer (flutter analyze --flutter-repo) does not report any problems on my PR.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Did any tests fail when you ran them? Please read Handling breaking changes.

[x] No, no existing tests failed, so this is not a breaking change.
[ ] Yes, this is a breaking change. If not, delete the remainder of this section.

[ ] I wrote a design doc: https://flutter.dev/go/template Replace this with a link to your design doc's short link
[ ] I got input from the developer relations team, specifically from: Replace with the names of who gave advice
[ ] I wrote a migration guide: Replace with a link to your migration guide

@jonahwilliams @zanderso

log before applying the patch
[  +27 ms] executing: [/home/michaellee8/flutter_fuchsia_toolchain/flutter/] git -c log.showSignature=false log -n 1 --pretty=format:%H
[  +34 ms] Exit code 0 from: git -c log.showSignature=false log -n 1 --pretty=format:%H
[        ] 0c4a659d18ab37d9796ac68c552b1b4e790abd15
[        ] executing: [/home/michaellee8/flutter_fuchsia_toolchain/flutter/] git tag --contains HEAD
[ +188 ms] Exit code 0 from: git tag --contains HEAD
[   +2 ms] executing: [/home/michaellee8/flutter_fuchsia_toolchain/flutter/] git describe --match *.*.*-*.*.pre --first-parent --long --tags
[ +128 ms] Exit code 0 from: git describe --match *.*.*-*.*.pre --first-parent --long --tags
[        ] 1.18.0-8.0.pre-12-g0c4a659d1
[   +8 ms] executing: [/home/michaellee8/flutter_fuchsia_toolchain/flutter/] git rev-parse --abbrev-ref --symbolic @{u}
[   +4 ms] Exit code 128 from: git rev-parse --abbrev-ref --symbolic @{u}
[        ] fatal: HEAD does not point to a branch
[  +44 ms] executing: [/home/michaellee8/flutter_fuchsia_toolchain/flutter/] git rev-parse --abbrev-ref HEAD
[   +4 ms] Exit code 0 from: git rev-parse --abbrev-ref HEAD
[        ] HEAD
[  +37 ms] Artifact Instance of 'AndroidMavenArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'AndroidGenSnapshotArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterWebSdk' is not required, skipping update.
[   +2 ms] Artifact Instance of 'WindowsEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required, skipping update.
[   +9 ms] executing: /home/michaellee8/Android/Sdk/platform-tools/adb devices -l
[   +6 ms] executing: /home/michaellee8/flutter_fuchsia_toolchain/flutter/bin/cache/artifacts/fuchsia/tools/device-finder list -full
[  +33 ms] List of devices attached
[ +993 ms] fe80::5054:ff:fe63:5e7a%qemu step-atom-yard-juicy
[   +6 ms] executing: /home/michaellee8/flutter_fuchsia_toolchain/flutter/bin/cache/artifacts/fuchsia/tools/device-finder resolve -device-limit 1 step-atom-yard-juicy
[  +29 ms] fe80::5054:ff:fe63:5e7a%qemu
[   +7 ms] executing: ssh -F /home/michaellee8/.fuchsia/sshconfig fe80::5054:ff:fe63:5e7a%qemu uname -m
[  +83 ms] x86_64

           Warning: Permanently added 'fe80::5054:ff:fe63:5e7a%qemu' (ED25519) to the list of known hosts.
[   +2 ms] Artifact Instance of 'AndroidMavenArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'AndroidGenSnapshotArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterWebSdk' is not required, skipping update.
[   +1 ms] Artifact Instance of 'WindowsEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required, skipping update.
[ +231 ms] Found plugin package_info at /home/michaellee8/.pub-cache/hosted/pub.dartlang.org/package_info-0.4.0+16/
[   +7 ms] Found plugin path_provider at /home/michaellee8/.pub-cache/hosted/pub.dartlang.org/path_provider-1.6.5/
[   +1 ms] Found plugin path_provider_macos at /home/michaellee8/.pub-cache/hosted/pub.dartlang.org/path_provider_macos-0.0.4/
[  +13 ms] Found plugin shared_preferences at /home/michaellee8/.pub-cache/hosted/pub.dartlang.org/shared_preferences-0.5.6+3/
[   +2 ms] Found plugin shared_preferences_macos at /home/michaellee8/.pub-cache/hosted/pub.dartlang.org/shared_preferences_macos-0.0.1+6/
[   +2 ms] Found plugin shared_preferences_web at /home/michaellee8/.pub-cache/hosted/pub.dartlang.org/shared_preferences_web-0.1.2+4/
[  +16 ms] Found plugin url_launcher at /home/michaellee8/.pub-cache/hosted/pub.dartlang.org/url_launcher-5.4.2/
[   +2 ms] Found plugin url_launcher_macos at /home/michaellee8/.pub-cache/hosted/pub.dartlang.org/url_launcher_macos-0.0.1+4/
[   +2 ms] Found plugin url_launcher_web at /home/michaellee8/.pub-cache/hosted/pub.dartlang.org/url_launcher_web-0.1.1+1/
[  +99 ms] Found plugin package_info at /home/michaellee8/.pub-cache/hosted/pub.dartlang.org/package_info-0.4.0+16/
[   +1 ms] Found plugin path_provider at /home/michaellee8/.pub-cache/hosted/pub.dartlang.org/path_provider-1.6.5/
[        ] Found plugin path_provider_macos at /home/michaellee8/.pub-cache/hosted/pub.dartlang.org/path_provider_macos-0.0.4/
[   +5 ms] Found plugin shared_preferences at /home/michaellee8/.pub-cache/hosted/pub.dartlang.org/shared_preferences-0.5.6+3/
[        ] Found plugin shared_preferences_macos at /home/michaellee8/.pub-cache/hosted/pub.dartlang.org/shared_preferences_macos-0.0.1+6/
[   +1 ms] Found plugin shared_preferences_web at /home/michaellee8/.pub-cache/hosted/pub.dartlang.org/shared_preferences_web-0.1.2+4/
[  +35 ms] Found plugin url_launcher at /home/michaellee8/.pub-cache/hosted/pub.dartlang.org/url_launcher-5.4.2/
[   +3 ms] Found plugin url_launcher_macos at /home/michaellee8/.pub-cache/hosted/pub.dartlang.org/url_launcher_macos-0.0.1+4/
[   +3 ms] Found plugin url_launcher_web at /home/michaellee8/.pub-cache/hosted/pub.dartlang.org/url_launcher_web-0.1.1+1/
[  +85 ms] Generating /home/michaellee8/gallery/android/app/src/main/java/io/flutter/plugins/GeneratedPluginRegistrant.java
[  +47 ms] executing: ssh -F /home/michaellee8/.fuchsia/sshconfig fe80::5054:ff:fe63:5e7a%qemu cat /pkgfs/packages/build-info/0/data/version
[  +24 ms] 0.20200425.0.1
[ +102 ms] Launching lib/main.dart on step-atom-yard-juicy in debug mode...
[   +7 ms] /home/michaellee8/flutter_fuchsia_toolchain/flutter/bin/cache/dart-sdk/bin/dart /home/michaellee8/flutter_fuchsia_toolchain/flutter/bin/cache/artifacts/engine/linux-x64/frontend_server.dart.snapshot
--sdk-root /home/michaellee8/flutter_fuchsia_toolchain/flutter/bin/cache/artifacts/flutter_runner/flutter/x64/debug/jit/flutter_runner_patched_sdk/ --incremental --target=flutter_runner --debugger-module-names
-Ddart.developer.causal_async_stacks=true --output-dill /tmp/flutter_tool.VCDUKD/app.dill --packages .packages -Ddart.vm.profile=false -Ddart.vm.product=false
--bytecode-options=source-positions,local-var-info,debugger-stops,instance-field-initializers,keep-unreachable-code,avoid-closure-call-instructions --enable-asserts --track-widget-creation --filesystem-scheme
org-dartlang-root --initialize-from-dill build/cache.dill
[  +32 ms] <- compile package:gallery/main.dart
[  +10 ms] Building Fuchsia application...
[   +2 ms] executing: /home/michaellee8/flutter_fuchsia_toolchain/flutter/bin/cache/dart-sdk/bin/dart
/home/michaellee8/flutter_fuchsia_toolchain/flutter/bin/cache/artifacts/flutter_runner/flutter/arm64/debug/jit/dart_binaries/kernel_compiler.snapshot --target flutter_runner --platform
/home/michaellee8/flutter_fuchsia_toolchain/flutter/bin/cache/artifacts/flutter_runner/flutter/arm64/debug/jit/flutter_runner_patched_sdk/platform_strong.dill --filesystem-scheme main-root --filesystem-root
/home/michaellee8/gallery --packages main-root:///.packages --output build/fuchsia/gallery.dil --component-name gallery --no-link-platform --split-output-by-packages --manifest build/fuchsia/gallery.dilpmanifest
--embed-sources -Ddart.developer.causal_async_stacks=true main-root:////home/michaellee8/gallery/lib/main.dart
[+28813 ms] Building Fuchsia application... (completed in 28.8s)
[        ] fuchsia-kernel-compile: 28820 ms.
[+1882 ms] fuchsia-build-assets: 1882 ms.
[  +24 ms] executing: /home/michaellee8/flutter_fuchsia_toolchain/flutter/bin/cache/artifacts/fuchsia/tools/pm -o build/fuchsia/pkg -n gallery init
[  +16 ms] executing: /home/michaellee8/flutter_fuchsia_toolchain/flutter/bin/cache/artifacts/fuchsia/tools/pm -o build/fuchsia/pkg -k build/fuchsia/pkg/development.key genkey
[   +9 ms] package signing is deprecated
[        ] executing: /home/michaellee8/flutter_fuchsia_toolchain/flutter/bin/cache/artifacts/fuchsia/tools/pm -o build/fuchsia/pkg -k build/fuchsia/pkg/development.key -m build/fuchsia/pkg/package_manifest
build
[ +574 ms] executing: /home/michaellee8/flutter_fuchsia_toolchain/flutter/bin/cache/artifacts/fuchsia/tools/pm -o build/fuchsia/pkg -k build/fuchsia/pkg/development.key -m build/fuchsia/pkg/package_manifest
archive
[ +228 ms] fuchsia-build-package: 850 ms.
[   +4 ms] executing: ssh -F /home/michaellee8/.fuchsia/sshconfig fe80::5054:ff:fe63:5e7a%qemu tiles_ctl list
[  +98 ms] Couldn't find tiles component in realm
           To start a new instance of tiles, run 'tiles_ctl start'
[        ] tiles_ctl is not running
[        ] executing: /home/michaellee8/flutter_fuchsia_toolchain/flutter/bin/cache/artifacts/fuchsia/tools/device-finder resolve -local -device-limit 1 step-atom-yard-juicy
[  +20 ms] fe80::9c3a:6fff:feba:6e23%qemu
[  +10 ms] Starting Fuchsia application gallery...
[   +1 ms] executing: ssh -F /home/michaellee8/.fuchsia/sshconfig fe80::5054:ff:fe63:5e7a%qemu amber_ctl get_up -n tiles
[  +51 ms] executing: ssh -F /home/michaellee8/.fuchsia/sshconfig fe80::5054:ff:fe63:5e7a%qemu amber_ctl get_up -n tiles_ctl
[  +48 ms] executing: /home/michaellee8/flutter_fuchsia_toolchain/flutter/bin/cache/artifacts/fuchsia/tools/pm newrepo -repo build/fuchsia/.pkg-repo
[ +540 ms] executing: /home/michaellee8/flutter_fuchsia_toolchain/flutter/bin/cache/artifacts/fuchsia/tools/pm serve -repo build/fuchsia/.pkg-repo -l [fe80::9c3a:6fff:feba:6e23%25qemu]:43733
[   +5 ms] executing: /home/michaellee8/flutter_fuchsia_toolchain/flutter/bin/cache/artifacts/fuchsia/tools/pm publish -a -r build/fuchsia/.pkg-repo -f build/fuchsia/pkg/gallery-0.far
[   +5 ms] listen tcp [fe80::9c3a:6fff:feba:6e23%25qemu]:43733: bind: no such device
[   +3 ms] Error running Fuchsia pm tool "serve" command
[ +556 ms] executing: /home/michaellee8/flutter_fuchsia_toolchain/flutter/bin/cache/artifacts/fuchsia/tools/pm publish -a -r build/fuchsia/.pkg-repo -f
/home/michaellee8/flutter_fuchsia_toolchain/flutter/bin/cache/artifacts/flutter_runner/flutter/x64/debug/jit/flutter_jit_runner-0.far
[ +437 ms] executing: ssh -F /home/michaellee8/.fuchsia/sshconfig fe80::5054:ff:fe63:5e7a%qemu amber_ctl add_repo_cfg -n flutter_tool -f http://[fe80::9c3a:6fff:feba:6e23%25qemu]:43733/config.json
[  +37 ms] 2020/04/26 03:25:53 error adding repo: failed to GET file: Get "http://[fe80::9c3a:6fff:feba:6e23%25qemu]:43733/config.json": dial tcp [fe80::9c3a:6fff:feba:6e23%qemu]:43733: errno(111)
[        ] Failed to teach amber about the package server
[        ] Shutting down the tool's package server.
[        ] Removing the tool's package repo: at build/fuchsia/.pkg-repo
[  +57 ms] Starting Fuchsia application gallery... (completed in 1.7s)
[        ] Error launching application on step-atom-yard-juicy.
[   +5 ms] "flutter run" took 35,372ms.

#0      throwToolExit (package:flutter_tools/src/base/common.dart:14:3)
#1      RunCommand.runCommand (package:flutter_tools/src/commands/run.dart:570:7)
<asynchronous suspension>
#2      FlutterCommand.verifyThenRunCommand (package:flutter_tools/src/runner/flutter_command.dart:760:18)
<asynchronous suspension>
#3      FlutterCommand.run.<anonymous closure> (package:flutter_tools/src/runner/flutter_command.dart:657:33)
<asynchronous suspension>
#4      FlutterCommand.run.<anonymous closure> (package:flutter_tools/src/runner/flutter_command.dart)
#5      AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:29)
#6      _rootRun (dart:async/zone.dart:1184:13)
#7      _CustomZone.run (dart:async/zone.dart:1077:19)
#8      _runZoned (dart:async/zone.dart:1619:10)
#9      runZoned (dart:async/zone.dart:1539:10)
#10     AppContext.run (package:flutter_tools/src/base/context.dart:149:18)
#11     FlutterCommand.run (package:flutter_tools/src/runner/flutter_command.dart:647:20)
#12     CommandRunner.runCommand (package:args/command_runner.dart:197:27)
#13     FlutterCommandRunner.runCommand.<anonymous closure> (package:flutter_tools/src/runner/flutter_command_runner.dart:339:21)
#14     _rootRunUnary (dart:async/zone.dart:1192:38)
#15     _CustomZone.runUnary (dart:async/zone.dart:1085:19)
#16     _FutureListener.handleValue (dart:async/future_impl.dart:141:18)
#17     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:686:45)
#18     Future._propagateToListeners (dart:async/future_impl.dart:715:32)
#19     Future._completeWithValue (dart:async/future_impl.dart:526:5)
#20     Future._asyncCompleteWithValue.<anonymous closure> (dart:async/future_impl.dart:560:7)
#21     _rootRun (dart:async/zone.dart:1184:13)
#22     _CustomZone.run (dart:async/zone.dart:1077:19)
#23     _CustomZone.runGuarded (dart:async/zone.dart:979:7)
#24     _CustomZone.bindCallbackGuarded.<anonymous closure> (dart:async/zone.dart:1019:23)
#25     _microtaskLoop (dart:async/schedule_microtask.dart:43:21)
#26     _startMicrotaskLoop (dart:async/schedule_microtask.dart:52:5)
#27     _runPendingImmediateCallback (dart:isolate-patch/isolate_patch.dart:118:13)
#28     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:169:5)

log after applying the patch (still broken by this problem has been solved)
[  +18 ms] executing: [/home/michaellee8/flutter_fuchsia_toolchain/flutter/] git -c log.showSignature=false log -n 1 --pretty=format:%H
[  +52 ms] Exit code 0 from: git -c log.showSignature=false log -n 1 --pretty=format:%H
[        ] 0c4a659d18ab37d9796ac68c552b1b4e790abd15
[   +1 ms] executing: [/home/michaellee8/flutter_fuchsia_toolchain/flutter/] git tag --contains HEAD
[ +319 ms] Exit code 0 from: git tag --contains HEAD
[   +6 ms] executing: [/home/michaellee8/flutter_fuchsia_toolchain/flutter/] git describe --match *.*.*-*.*.pre --first-parent --long --tags
[ +276 ms] Exit code 0 from: git describe --match *.*.*-*.*.pre --first-parent --long --tags
[        ] 1.18.0-8.0.pre-12-g0c4a659d1
[  +27 ms] executing: [/home/michaellee8/flutter_fuchsia_toolchain/flutter/] git rev-parse --abbrev-ref --symbolic @{u}
[  +16 ms] Exit code 128 from: git rev-parse --abbrev-ref --symbolic @{u}
[        ] fatal: HEAD does not point to a branch
[  +64 ms] executing: [/home/michaellee8/flutter_fuchsia_toolchain/flutter/] git rev-parse --abbrev-ref HEAD
[  +20 ms] Exit code 0 from: git rev-parse --abbrev-ref HEAD
[        ] HEAD
[  +75 ms] Artifact Instance of 'AndroidMavenArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'AndroidGenSnapshotArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterWebSdk' is not required, skipping update.
[   +4 ms] Artifact Instance of 'WindowsEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required, skipping update.
[  +30 ms] executing: /home/michaellee8/Android/Sdk/platform-tools/adb devices -l
[  +19 ms] executing: /home/michaellee8/flutter_fuchsia_toolchain/flutter/bin/cache/artifacts/fuchsia/tools/device-finder list -full
[  +91 ms] List of devices attached
[ +986 ms] fe80::5054:ff:fe63:5e7a%qemu step-atom-yard-juicy
[   +3 ms] executing: /home/michaellee8/flutter_fuchsia_toolchain/flutter/bin/cache/artifacts/fuchsia/tools/device-finder resolve -device-limit 1 step-atom-yard-juicy
[  +27 ms] fe80::5054:ff:fe63:5e7a%qemu
[   +7 ms] executing: ssh -F /home/michaellee8/.fuchsia/sshconfig fe80::5054:ff:fe63:5e7a%qemu uname -m
[ +185 ms] x86_64

                    Warning: Permanently added 'fe80::5054:ff:fe63:5e7a%qemu' (ED25519) to the list of known hosts.
[   +6 ms] Artifact Instance of 'AndroidMavenArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'AndroidGenSnapshotArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterWebSdk' is not required, skipping update.
[   +2 ms] Artifact Instance of 'WindowsEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required, skipping update.
[ +345 ms] Found plugin package_info at /home/michaellee8/.pub-cache/hosted/pub.dartlang.org/package_info-0.4.0+16/
[  +14 ms] Found plugin path_provider at /home/michaellee8/.pub-cache/hosted/pub.dartlang.org/path_provider-1.6.5/
[   +4 ms] Found plugin path_provider_macos at /home/michaellee8/.pub-cache/hosted/pub.dartlang.org/path_provider_macos-0.0.4/
[  +41 ms] Found plugin shared_preferences at /home/michaellee8/.pub-cache/hosted/pub.dartlang.org/shared_preferences-0.5.6+3/
[   +3 ms] Found plugin shared_preferences_macos at /home/michaellee8/.pub-cache/hosted/pub.dartlang.org/shared_preferences_macos-0.0.1+6/
[   +7 ms] Found plugin shared_preferences_web at /home/michaellee8/.pub-cache/hosted/pub.dartlang.org/shared_preferences_web-0.1.2+4/
[  +41 ms] Found plugin url_launcher at /home/michaellee8/.pub-cache/hosted/pub.dartlang.org/url_launcher-5.4.2/
[   +2 ms] Found plugin url_launcher_macos at /home/michaellee8/.pub-cache/hosted/pub.dartlang.org/url_launcher_macos-0.0.1+4/
[   +4 ms] Found plugin url_launcher_web at /home/michaellee8/.pub-cache/hosted/pub.dartlang.org/url_launcher_web-0.1.1+1/
[ +165 ms] Found plugin package_info at /home/michaellee8/.pub-cache/hosted/pub.dartlang.org/package_info-0.4.0+16/
[   +2 ms] Found plugin path_provider at /home/michaellee8/.pub-cache/hosted/pub.dartlang.org/path_provider-1.6.5/
[   +1 ms] Found plugin path_provider_macos at /home/michaellee8/.pub-cache/hosted/pub.dartlang.org/path_provider_macos-0.0.4/
[  +13 ms] Found plugin shared_preferences at /home/michaellee8/.pub-cache/hosted/pub.dartlang.org/shared_preferences-0.5.6+3/
[   +1 ms] Found plugin shared_preferences_macos at /home/michaellee8/.pub-cache/hosted/pub.dartlang.org/shared_preferences_macos-0.0.1+6/
[   +3 ms] Found plugin shared_preferences_web at /home/michaellee8/.pub-cache/hosted/pub.dartlang.org/shared_preferences_web-0.1.2+4/
[  +19 ms] Found plugin url_launcher at /home/michaellee8/.pub-cache/hosted/pub.dartlang.org/url_launcher-5.4.2/
[   +1 ms] Found plugin url_launcher_macos at /home/michaellee8/.pub-cache/hosted/pub.dartlang.org/url_launcher_macos-0.0.1+4/
[   +4 ms] Found plugin url_launcher_web at /home/michaellee8/.pub-cache/hosted/pub.dartlang.org/url_launcher_web-0.1.1+1/
[ +117 ms] Generating /home/michaellee8/gallery/android/app/src/main/java/io/flutter/plugins/GeneratedPluginRegistrant.java
[  +56 ms] executing: ssh -F /home/michaellee8/.fuchsia/sshconfig fe80::5054:ff:fe63:5e7a%qemu cat /pkgfs/packages/build-info/0/data/version
[  +48 ms] 0.20200425.0.1
[  +68 ms] Launching lib/main.dart on step-atom-yard-juicy in debug mode...
[  +13 ms] /home/michaellee8/flutter_fuchsia_toolchain/flutter/bin/cache/dart-sdk/bin/dart /home/michaellee8/flutter_fuchsia_toolchain/flutter/bin/cache/artifacts/engine/linux-x64/frontend_server.dart.snapshot
--sdk-root /home/michaellee8/flutter_fuchsia_toolchain/flutter/bin/cache/artifacts/flutter_runner/flutter/x64/debug/jit/flutter_runner_patched_sdk/ --incremental --target=flutter_runner --debugger-module-names
-Ddart.developer.causal_async_stacks=true --output-dill /tmp/flutter_tool.LFAPDD/app.dill --packages .packages -Ddart.vm.profile=false -Ddart.vm.product=false
--bytecode-options=source-positions,local-var-info,debugger-stops,instance-field-initializers,keep-unreachable-code,avoid-closure-call-instructions --enable-asserts --track-widget-creation --filesystem-scheme
org-dartlang-root --initialize-from-dill build/cache.dill
[  +53 ms] <- compile package:gallery/main.dart
[  +18 ms] Building Fuchsia application...
[   +3 ms] executing: /home/michaellee8/flutter_fuchsia_toolchain/flutter/bin/cache/dart-sdk/bin/dart
/home/michaellee8/flutter_fuchsia_toolchain/flutter/bin/cache/artifacts/flutter_runner/flutter/arm64/debug/jit/dart_binaries/kernel_compiler.snapshot --target flutter_runner --platform
/home/michaellee8/flutter_fuchsia_toolchain/flutter/bin/cache/artifacts/flutter_runner/flutter/arm64/debug/jit/flutter_runner_patched_sdk/platform_strong.dill --filesystem-scheme main-root --filesystem-root
/home/michaellee8/gallery --packages main-root:///.packages --output build/fuchsia/gallery.dil --component-name gallery --no-link-platform --split-output-by-packages --manifest build/fuchsia/gallery.dilpmanifest
--embed-sources -Ddart.developer.causal_async_stacks=true main-root:////home/michaellee8/gallery/lib/main.dart
[+34022 ms] Building Fuchsia application... (completed in 34.0s)
[        ] fuchsia-kernel-compile: 34033 ms.
[+2014 ms] fuchsia-build-assets: 2013 ms.
[   +7 ms] executing: /home/michaellee8/flutter_fuchsia_toolchain/flutter/bin/cache/artifacts/fuchsia/tools/pm -o build/fuchsia/pkg -n gallery init
[  +31 ms] executing: /home/michaellee8/flutter_fuchsia_toolchain/flutter/bin/cache/artifacts/fuchsia/tools/pm -o build/fuchsia/pkg -k build/fuchsia/pkg/development.key genkey
[  +14 ms] package signing is deprecated
[        ] executing: /home/michaellee8/flutter_fuchsia_toolchain/flutter/bin/cache/artifacts/fuchsia/tools/pm -o build/fuchsia/pkg -k build/fuchsia/pkg/development.key -m build/fuchsia/pkg/package_manifest
build
[ +362 ms] executing: /home/michaellee8/flutter_fuchsia_toolchain/flutter/bin/cache/artifacts/fuchsia/tools/pm -o build/fuchsia/pkg -k build/fuchsia/pkg/development.key -m build/fuchsia/pkg/package_manifest
archive
[ +241 ms] fuchsia-build-package: 657 ms.
[   +3 ms] executing: ssh -F /home/michaellee8/.fuchsia/sshconfig fe80::5054:ff:fe63:5e7a%qemu tiles_ctl list
[ +778 ms] Couldn't find tiles component in realm
                    To start a new instance of tiles, run 'tiles_ctl start'
[        ] tiles_ctl is not running
[        ] executing: /home/michaellee8/flutter_fuchsia_toolchain/flutter/bin/cache/artifacts/fuchsia/tools/device-finder resolve -local -device-limit 1 step-atom-yard-juicy
[  +24 ms] fe80::9c3a:6fff:feba:6e23%qemu
[   +8 ms] Starting Fuchsia application gallery...
[   +1 ms] executing: ssh -F /home/michaellee8/.fuchsia/sshconfig fe80::5054:ff:fe63:5e7a%qemu amber_ctl get_up -n tiles
[  +58 ms] executing: ssh -F /home/michaellee8/.fuchsia/sshconfig fe80::5054:ff:fe63:5e7a%qemu amber_ctl get_up -n tiles_ctl
[  +52 ms] executing: /home/michaellee8/flutter_fuchsia_toolchain/flutter/bin/cache/artifacts/fuchsia/tools/pm newrepo -repo build/fuchsia/.pkg-repo
[ +794 ms] executing: /home/michaellee8/flutter_fuchsia_toolchain/flutter/bin/cache/artifacts/fuchsia/tools/pm serve -repo build/fuchsia/.pkg-repo -l [fe80::9c3a:6fff:feba:6e23%qemu]:33773
[   +7 ms] executing: /home/michaellee8/flutter_fuchsia_toolchain/flutter/bin/cache/artifacts/fuchsia/tools/pm publish -a -r build/fuchsia/.pkg-repo -f build/fuchsia/pkg/gallery-0.far
[   +6 ms] 2020-04-26 12:50:29 [pm serve] serving build/fuchsia/.pkg-repo at http://[fe80::9c3a:6fff:feba:6e23%qemu]:33773
[ +633 ms] executing: /home/michaellee8/flutter_fuchsia_toolchain/flutter/bin/cache/artifacts/fuchsia/tools/pm publish -a -r build/fuchsia/.pkg-repo -f
/home/michaellee8/flutter_fuchsia_toolchain/flutter/bin/cache/artifacts/flutter_runner/flutter/x64/debug/jit/flutter_jit_runner-0.far
[ +888 ms] executing: ssh -F /home/michaellee8/.fuchsia/sshconfig fe80::5054:ff:fe63:5e7a%qemu amber_ctl add_repo_cfg -n flutter_tool -f http://[fe80::9c3a:6fff:feba:6e23%25qemu]:33773/config.json
[  +62 ms] 2020-04-26 12:50:31 [pm serve] 0 /config.json
[   +9 ms] executing: ssh -F /home/michaellee8/.fuchsia/sshconfig fe80::5054:ff:fe63:5e7a%qemu pkgctl resolve fuchsia-pkg://flutter_tool/gallery
[  +51 ms] resolving fuchsia-pkg://flutter_tool/gallery with the selectors []

           Error: INTERNAL
[        ] Failed to get pkgctl to prefetch the package
[   +2 ms] executing: ssh -F /home/michaellee8/.fuchsia/sshconfig fe80::5054:ff:fe63:5e7a%qemu pkgctl repo rm fuchsia-pkg://flutter_tool
[  +46 ms] Shutting down the tool's package server.
[        ] Removing the tool's package repo: at build/fuchsia/.pkg-repo
[  +41 ms] Starting Fuchsia application gallery... (completed in 2.7s)
[        ] Error launching application on step-atom-yard-juicy.
[   +7 ms] "flutter run" took 42,635ms.

#0      throwToolExit (package:flutter_tools/src/base/common.dart:14:3)
#1      RunCommand.runCommand (package:flutter_tools/src/commands/run.dart:570:7)
<asynchronous suspension>
#2      FlutterCommand.verifyThenRunCommand (package:flutter_tools/src/runner/flutter_command.dart:760:18)
<asynchronous suspension>
#3      FlutterCommand.run.<anonymous closure> (package:flutter_tools/src/runner/flutter_command.dart:657:33)
<asynchronous suspension>
#4      FlutterCommand.run.<anonymous closure> (package:flutter_tools/src/runner/flutter_command.dart)
#5      AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:29)
#6      _rootRun (dart:async/zone.dart:1184:13)
#7      _CustomZone.run (dart:async/zone.dart:1077:19)
#8      _runZoned (dart:async/zone.dart:1619:10)
#9      runZoned (dart:async/zone.dart:1539:10)
#10     AppContext.run (package:flutter_tools/src/base/context.dart:149:18)
#11     FlutterCommand.run (package:flutter_tools/src/runner/flutter_command.dart:647:20)
#12     CommandRunner.runCommand (package:args/command_runner.dart:197:27)
#13     FlutterCommandRunner.runCommand.<anonymous closure> (package:flutter_tools/src/runner/flutter_command_runner.dart:339:21)
#14     _rootRunUnary (dart:async/zone.dart:1192:38)
#15     _CustomZone.runUnary (dart:async/zone.dart:1085:19)
#16     _FutureListener.handleValue (dart:async/future_impl.dart:141:18)
#17     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:686:45)
#18     Future._propagateToListeners (dart:async/future_impl.dart:715:32)
#19     Future._completeWithValue (dart:async/future_impl.dart:526:5)
#20     Future._asyncCompleteWithValue.<anonymous closure> (dart:async/future_impl.dart:560:7)
#21     _rootRun (dart:async/zone.dart:1184:13)
#22     _CustomZone.run (dart:async/zone.dart:1077:19)
#23     _CustomZone.runGuarded (dart:async/zone.dart:979:7)
#24     _CustomZone.bindCallbackGuarded.<anonymous closure> (dart:async/zone.dart:1019:23)
#25     _microtaskLoop (dart:async/schedule_microtask.dart:43:21)
#26     _startMicrotaskLoop (dart:async/schedule_microtask.dart:52:5)
#27     _runPendingImmediateCallback (dart:isolate-patch/isolate_patch.dart:118:13)
#28     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:169:5)

FWIW, I patched this change to prevent an infra failure. I don't have the full context, but we can't simply revert the change otherwise our fuchsia integration test will break again.
[  +12 ms] executing: ssh -F /b/s/w/ir/fuchsia_ssh_config <IP_ADDRESS> tiles_ctl list
[  +72 ms] Found 1 tiles:
           Tile key 1 url fuchsia-pkg://fuchsia.com/terminal#meta/terminal.cmx size 1097.1x608.4x1000.0 (unfocusable)
[   +3 ms] Installing application package.
[   +1 ms] Starting application.
[  +57 ms] Building Fuchsia application...
[   +3 ms] executing: /b/s/w/ir/flutter/bin/cache/dart-sdk/bin/dart /b/s/w/ir/flutter/bin/cache/artifacts/flutter_runner/flutter/arm64/debug/jit/dart_binaries/kernel_compiler.snapshot --target flutter_runner --platform /b/s/w/ir/flutter/bin/cache/artifacts/flutter_runner/flutter/arm64/debug/jit/flutter_runner_patched_sdk/platform_strong.dill --filesystem-scheme main-root --filesystem-root /b/s/w/ir/flutter/dev/benchmarks/test_apps/stocks --packages main-root:///.packages --output build/fuchsia/stocks.dil --component-name stocks --no-link-platform --split-output-by-packages --manifest build/fuchsia/stocks.dilpmanifest --embed-sources -Ddart.developer.causal_async_stacks=true main-root:////b/s/w/ir/flutter/dev/benchmarks/test_apps/stocks/test_driver/stock_view.dart
[+16836 ms] Building Fuchsia application... (completed in 16.8s)
[        ] fuchsia-kernel-compile: 16854 ms.
[ +208 ms] fuchsia-build-assets: 207 ms.
[   +6 ms] executing: /b/s/w/ir/flutter/bin/cache/artifacts/fuchsia/tools/pm -o build/fuchsia/pkg -n stocks init
[  +12 ms] executing: /b/s/w/ir/flutter/bin/cache/artifacts/fuchsia/tools/pm -o build/fuchsia/pkg -k build/fuchsia/pkg/development.key genkey
[  +10 ms] package signing is deprecated
[        ] executing: /b/s/w/ir/flutter/bin/cache/artifacts/fuchsia/tools/pm -o build/fuchsia/pkg -k build/fuchsia/pkg/development.key -m build/fuchsia/pkg/package_manifest build
[ +224 ms] executing: /b/s/w/ir/flutter/bin/cache/artifacts/fuchsia/tools/pm -o build/fuchsia/pkg -k build/fuchsia/pkg/development.key -m build/fuchsia/pkg/package_manifest archive
[  +64 ms] fuchsia-build-package: 319 ms.
[        ] executing: ssh -F /b/s/w/ir/fuchsia_ssh_config <IP_ADDRESS> tiles_ctl list
[  +66 ms] Found 1 tiles:
           Tile key 1 url fuchsia-pkg://fuchsia.com/terminal#meta/terminal.cmx size 1097.1x608.4x1000.0 (unfocusable)
[        ] executing: /b/s/w/ir/flutter/bin/cache/artifacts/fuchsia/tools/device-finder resolve -local -device-limit 1 ocean-bats-wick-snub
[  +18 ms] fe80::ec4:7aff:fecc:ea8f%eno2

           mdns.go:1041: listen udp6 [2001:db8:123:4567:89ab:cdef:1234:1%docker0]:5353: bind: cannot assign requested address
           mdns.go:1041: listen udp6 [fe80::1%docker0]:5353: bind: cannot assign requested address
[  +20 ms] Starting Fuchsia application stocks...
[   +1 ms] executing: ssh -F /b/s/w/ir/fuchsia_ssh_config <IP_ADDRESS> amber_ctl get_up -n tiles
[  +56 ms] executing: ssh -F /b/s/w/ir/fuchsia_ssh_config <IP_ADDRESS> amber_ctl get_up -n tiles_ctl
[  +56 ms] executing: /b/s/w/ir/flutter/bin/cache/artifacts/fuchsia/tools/pm newrepo -repo build/fuchsia/.pkg-repo
[ +883 ms] executing: /b/s/w/ir/flutter/bin/cache/artifacts/fuchsia/tools/pm serve -repo build/fuchsia/.pkg-repo -l [fe80::ec4:7aff:fecc:ea8f%25eno2]:34283
[  +10 ms] executing: /b/s/w/ir/flutter/bin/cache/artifacts/fuchsia/tools/pm publish -a -r build/fuchsia/.pkg-repo -f build/fuchsia/pkg/stocks-0.far
[   +8 ms] listen tcp [fe80::ec4:7aff:fecc:ea8f%25eno2]:34283: bind: no such device
[   +4 ms] Error running Fuchsia pm tool "serve" command
[ +661 ms] executing: /b/s/w/ir/flutter/bin/cache/artifacts/fuchsia/tools/pm publish -a -r build/fuchsia/.pkg-repo -f /b/s/w/ir/flutter/bin/cache/artifacts/flutter_runner/flutter/x64/debug/jit/flutter_jit_runner-0.far
[ +726 ms] executing: ssh -F /b/s/w/ir/fuchsia_ssh_config <IP_ADDRESS> amber_ctl add_repo_cfg -n flutter_tool -f http://[fe80::ec4:7aff:fecc:ea8f%25eno2]:34283/config.json
[  +48 ms] 2020/04/25 01:14:37 error adding repo: failed to GET file: Get "http://[fe80::ec4:7aff:fecc:ea8f%25eno2]:34283/config.json": dial tcp [fe80::ec4:7aff:fecc:ea8f%eno2]:34283: errno(111)
[        ] Failed to teach amber about the package server
[        ] Shutting down the tool's package server.
[   +1 ms] Removing the tool's package repo: at build/fuchsia/.pkg-repo
[  +34 ms] Starting Fuchsia application stocks... (completed in 2.5s)
[   +8 ms] "flutter drive" took 21,828ms.
Application failed to start. Will not run test. Quitting.

@jonahwilliams Are there any chance your integration test fail because you are running in Docker?

TBH I don't really understand this integration test very well, but it did start working again after I removed the information after the %.
Its a bit later here, but I'll cc some other folks on this PRs we can figure out the best solution.

Okay I think I understand it now. Binding the ipv6 linklocal address on host require the unstripped address that include the interface name, but amber_ctl cannot accept the url with the interface. My proposed solution here is to add a interfaceStrippedUrl getter to be used by amber.

@jonahwilliams btw can you tell me how do I switch to different tiles in the fuchsia emulator? After applying this patch, it seems that flutter run is working now. However, there are still no application launching in the fuchsia emulator. Do you guys uses the workstation.qemu-x64-release or qemu-x64 flavour for using flutter run in the emulator? I read that you can do Select a Tab by Alt+F2, but I my Ubuntu environment all these keys are catched by the OS and perform tab switching on my desktop environment instead. What is the best way to do that?

After using the patch I can do flutter run in qemu-x64 now, because tiles_ctl exists there. However, how do I launch apps in workstation.qemu-x64-release? It seems that both tiles_ctl and sessionctl is not working there.

tiles_ctl was removed from the workstation image. My understanding is that https://bugs.fuchsia.dev/p/fuchsia/issues/detail?id=47125 is tracking its replacement.

tiles_ctl was removed from the workstation image. My understanding is that https://bugs.fuchsia.dev/p/fuchsia/issues/detail?id=47125 is tracking its replacement.

Thank you for your input but I don't really have access to that link. Can you tell me if there are no replacement yet?

I have rewrote the patch to avoid unnecessary changes. Tested to work with flutter run locally on my Ubuntu machine. Please see if it can be merged.

It looks like the test are passing after I modified it reflect my changes. It should be ok to merge now.

@jonahwilliams @zanderso


pass firefox navigation tests

related to #111

@kblok could the failures be due to certificate issues?

@Meir017 yes. It must be that. Could you try installing certificates on the windows build?

We are all green here @Meir017. Do you want to take a final look?


Spot (Japan).gb music doesnt sound right on title screen (one of the channels is wrong)

The fix for #32 mostly fixes this (depends on initial contents of wavetable RAM at power-on)
The wave channel still doesn't sound quite right though. There's probably a better way of initializing DMG wavetable RAM than hardcoding the values from https://gbdev.gg8.se/wiki/articles/Gameboy_sound_hardware#Power_Control


Per-subject type defaults

This allows more flexibility in configuring defaults per-subject-type. This would be implemented by sticking all default subjects in the default subject type.

#2039 would be helped by this -- we could explicitly set permissions for pex commands to false, so commandblocks could not mess with permissions unless explicitly requested.

Marked as high priority because more and more usecases keep coming up where this makes sense and makes life a lot easier for folks


invalid YAML frontmatter

I think this is due to missing title but Notable handle this and fallback to filename. Also I can't even open the note.

Thank you for the report! Currently the app expects at least a title and a created/modified date. Your error is caused most likely by the missing dates. I will add some code to fallback to the actual file's metadata if it's missing in the next release (tomorrow). The next release will also make more clear that the ERROR Tiles are actually not files or notes.

Just added the fallback handling in the new release Alpha 0.3.0.

@madeindjs Could you please try the latest Alpha 0.3.1 and confirm that it works?

Yes it works. Thank you very much.
But I Still have an issue with this YAML frontmatter (which is valid):
---
title: Security
tags:
  - node
emoji: 👮♂
---

Maybe this is due to emoji or mutline array syntax.

The yaml parser used by this app doesn't support emojis yet (https://github.com/dart-lang/yaml/issues/53). A possible workaround is to use the escape sequence \U0001F46E instead of the emoji in the yaml.

Ok So I think I can close issue for now. Thank you again.


docs: add missing mentions about json to data-writes.md

[x] Docs

This PR fixes missing json in data-writes.md document. At certain point in the guide we return the validation errors and form values with json, but it isn't actually imported anywhere. This PR makes it so that json is always imported too wherever the other used action redirect is mentioned.

Thank you!


Show the status line by default

This could be a silly question, but I would like airline to show without nerd tree or crtl-p initiating it. Is there a way to just have it show within a buffer that doesn't have any other plugins that allow to show the status line? Basically just show the status line by default all the time. The only time I can see it is when I toggle ctrl-p, nerd tree, or have 2 buffers running in the same window. Thanks!

add set laststatus=2 to your vimrc

Cheers Bling! Did I somehow overlook this, or is this just basic vim knowledge I should probably have known? Oh and thanks for this sweet plugin!


HDDS-3973. Update main feature design status.

https://issues.apache.org/jira/browse/HDDS-3973

@nandakumar131  Could you take a look at this JIRA, make sure I have your name correctly spelled.


feature: HuggingFace Gated Model Support

Summary
A support for HuggingFace gated model is needed. A gated model can be a model that needs to accept a license to get access. An example can be mistralai/Mistral-7B-Instruct-v0.2. When downloading the model, the user needs to provide a HF token.
Basic example
Take the mistralai/Mistral-7B-Instruct-v0.2 as an example. Once the user click accept the license. They can download the model through the huggingface_hub or git with HuggingFace acces token.
The model url is https://huggingface.co/mistralai/Mistral-7B-Instruct-v0.2
Motivation
Recently there are more gated models than before. This will make garak more helpful to deal with more models.

Gated huggingface models can be downloaded if the system has a cached token in place.  See huggingface cli login for details.  This will cache the token in the user's huggingface XDG cache that the transformers library relies on.
There are other supported methods to provide a token via configuration however I suspect they are less user friendly one such method is adding a token value via entires in hf_args for the generator selected.
To pass via --config as yaml:
plugins:
  generators:
    huggingface:
      Pipeline:
        hf_args:
          token: <hf_token>

To pass via --generator_option_file as json:
{
  "huggingface": {
    "Pipeline": {
      "hf_args": {
        "token": "<hf_token>"
      }
    }
  }
}

This is also covering in the FAQ.

Thanks. I think this issue can be closed.


LXD 3.0 auto-init Broken

Required information
Ubuntu 16.04
Linux f8-c1-n13 4.13.0-37-generic #42~16.04.1-Ubuntu SMP Wed Mar 7 16:03:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
lxd 3.0 stable
Issue description
cannot perform auto init using command line
Steps to reproduce
/snap/bin/lxd init --auto --storage-backend=dir network-address=<IP_ADDRESS> --network-port=8443 --trust-password=blahblah
Information to attach
panic: assignment to entry in nil map
goroutine 1 [running]:
main.(*cmdInit).RunAuto(0xc420304d20, 0xc42030c780, 0xc420213270, 0x0, 0x5, 0x10e3a40, 0xc4202c7f40, 0xf, 0xf, 0xf)
/build/lxd-latest-candidate/parts/lxd/go/src/github.com/lxc/lxd/lxd/main_init_auto.go:67 +0x9b4
main.(*cmdInit).Run(0xc420304d20, 0xc42030c780, 0xc420213270, 0x0, 0x5, 0x0, 0x0)
/build/lxd-latest-candidate/parts/lxd/go/src/github.com/lxc/lxd/lxd/main_init.go:103 +0x252
main.(*cmdInit).Run-fm(0xc42030c780, 0xc420213270, 0x0, 0x5, 0x0, 0x0)
/build/lxd-latest-candidate/parts/lxd/go/src/github.com/lxc/lxd/lxd/main_init.go:56 +0x52
github.com/spf13/cobra.(*Command).execute(0xc42030c780, 0xc420213220, 0x5, 0x5, 0xc42030c780, 0xc420213220)
/build/lxd-latest-candidate/parts/lxd/go/src/github.com/spf13/cobra/command.go:762 +0x468
github.com/spf13/cobra.(*Command).ExecuteC(0xc4202cb400, 0x0, 0xc42030d680, 0xc42030d680)
/build/lxd-latest-candidate/parts/lxd/go/src/github.com/spf13/cobra/command.go:852 +0x30a
github.com/spf13/cobra.(*Command).Execute(0xc4202cb400, 0xc420303e10, 0x1)
/build/lxd-latest-candidate/parts/lxd/go/src/github.com/spf13/cobra/command.go:800 +0x2b
main.main()
/build/lxd-latest-candidate/parts/lxd/go/src/github.com/lxc/lxd/lxd/main.go:155 +0xd4d

That's been fixed in the stable-3.0 branch and in the snap package (if that's what you're using).
A test has also been added to prevent regressions.

Running latest stable...
root@f8-c1-n12:~# snap refresh lxd
snap "lxd" has no updates available

So no it hasnt made it out to snap in stable branch.

What revision do you see in snap list?

root@f8-c1-n12:~# snap version
snap    2.31.2
snapd   2.31.2
series  16
ubuntu  16.04
kernel  4.13.0-37-generic
root@f8-c1-n12:~# snap list
Name  Version    Rev   Developer  Notes
core  16-2.31.2  4206  canonical  core
lxd   3.0.0      6418  canonical  -

Confirmed that the snap doesn't have the fix for some reason, despite it being clearly listed as cherry-picked in the manifest... rebuilding the snap now.

Oh, I see the problem, fixing.

Problem fixed in the packaging branch, new candidate snaps will build in the next hour or so.
I need to go get some sleep but I'll be promoting those to stable in the morning.


Extremely slow agent startup

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?

Rolling upgrade to v1.12.9
each cilium agent pod is not ready for 2-3m

Cilium Version
1.12.9 e0bb30a 2023-04-17T23:54:19+02:00 go version go1.18.10 linux/amd64
Kernel Version
Linux ip-10-200-14-243 5.15.0-1033-aws #37~20.04.1-Ubuntu SMP Fri Mar 17 11:39:30 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
Kubernetes Version
v1.22.17-eks-48e63af
Sysdump
No response
Relevant log output
No response
Anything else?
When startup is slow, it correlates with cluster size (some clusters don't have this issue)
For the time until cilium starts, all I get is:
# cilium status
Get "http:///var/run/cilium/cilium.sock/v1/healthz": dial unix /var/run/cilium/cilium.sock: connect: no such file or directory
Is the agent running?

I do see a bunch of clang and tc commands running in the background during this time.
Code of Conduct

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

Is this a regression? Do you have data on Cilium's startup performance on earlier versions?

Is this a regression? Do you have data on Cilium's startup performance on earlier versions?

It's been awhile since we did the v1.12.8 upgrade rollout, so I can't say with as much certainty.
I just restarted a handful of agents (that are still v1.12.8) in equally as large clusters, and they took only ~30s to startup.

Can you get a sysdump? Thank you

Can you get a sysdump? Thank you

Which part(s) are you specifically looking for? Unfortunately some of the data in the sysdump cannot be shared without some sanitization.

For v1.12.9, looks like startup time is correlated with pod count (endpoints/identities/services) of a cluster

@dctrwatson the cilium logs would also be useful.

@dctrwatson also, do you have a pprof from the first ~90s of a v1.12.8 agent startup?

@dctrwatson the cilium logs would also be useful.

cilium.log.zip

FYI I can't open the pprof-trace on my side.

I just untar'd and zip'd the directory cilium-bugtool --get-pprof output (github won't let me upload .tar.gz)

@dctrwatson also, do you have a pprof from the first ~90s of a v1.12.8 agent startup?

No, I would need to downgrade a cluster to get that. Also, v1.12.8 agents are Ready in only 20-30s

I tried to get pprof of a v1.12.8, but so far I haven't figured out how to get it out of the pod without it getting cut off. So here's the largest tar I've been able to get out of a pod so far
cilium-v1.12.8.zip

Just ended up using tried and true exec -- cat | tar x, lol
cilium-v1.12.8.zip

Here's a new one from v1.12.9, hopefully you can open pprof-trace from this one:
cilium-v1.12.9.zip

@dctrwatson Could you give us an indication of the cluster size? How many pods do you have?

@dctrwatson Could you give us an indication of the cluster size? How many pods do you have?

The cluster where that pprof was taken has:
~9k endpoints
~7k identities
~2k network policies
~7k services
~10k pods
~200 nodes


nixos/pr-tracker: init module

Description of changes
Made a module for https://git.qyliss.net/pr-tracker @alyssais
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
[ ] 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.

@alyssais could you re-review

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/4665


Fix count bug

Count will not accept a string as parameter, just use Select.

Now the query looks strange like it would just return 1 because there is only one result line. Does it generate the expected result?


Dialogic not stopping input from filtering down to parent game

Input in Dialogic (input_next) is handled by the _process() method and not _Input.
This means the scene tree method set_input_as_handled() cannot be called. The result is if the underlying game is not paused then the input event is propagated down to the rest of the game that may handle _input, so if the same key handling input in Dialogic is handled in the game it is still called.
I'm not too hot on gui input in Godot but I had to fix the above problem by moving the _process() code handling input into the following similar code:
func _input(event: InputEvent) -> void:
	if Input.is_action_just_pressed(input_next):
		get_tree().set_input_as_handled()

i.e. after dialogic has processed the next screen key, it cancels input, otherwise Godot will just send the key to the rest of the game regardless.
Apologies if this version has already addressed this, I was using a slightly older version, but a quick scan of the code shows the same input being used.

Thanks for the report! I'm not sure how I should deal with this, since I don't want Dialogic to block any input, but I'm not sure if I should be doing it. I'll keep it open until I start to test it more in real world scenarios and see what changes I can make.

Maybe treat it as two stages.
First, you aren't blocking it you're simply moving it from a polling system in _process to the _input event where it should be because dialog is GUI and GUI input work best as event driven.
This means it gives it gives the end user (or the dialogic api) the choice of controlling input better..

What about adding it to _input and also making a boolean variable inside the theme editor to figure out if the user wants to propagate the input to the resto of the tree or not?


New page for the product lifecycles

Contributions

[X] I have read the contribution docs, and understand what's expected of me.

Link to the page on docs.getdbt.com requiring updates
Create a new page possibly here:
https://next.docs.getdbt.com/docs/dbt-versions/product-lifecycles
What part(s) of the page would you like to see updated?
Let's create a new page!
Additional information
Link to started content..

Work with @azzam34 to collaborate on the content
Create the GitHub PR to add it to the next branch.

Closing because Mirna did this!


[Bug]: When searching all work orders according to the work order number, occasionally the task cannot be found.

ODC version
ODC 4.2.4
OB version

What happened?
I used the admin user to log in to view all work orders. I did not find the task 75, but this task can be viewed in the sql plan list.

What did you expect to happen?
I can search for tasks based on task id.
How can we reproduce it (as minimally and precisely as possible)?
Search for tasks with id 75.
Anything else we need to know?
No response
Cloud
No response

schedule will not appear in lists


Use Psi4 1.8

Hey @mattwthompson thanks for looking into this, I think until Psi4 on conda-forge includes the fortran interface for PCM these tests will fail. We should keep an eye open for when this change happens but until then we need to use the psi4 channel.

You seem to be correct: https://psicode.org/psi4manual/1.5.0/glossary_psivariables.html#psivar-SCF-DIPOLE

The tests are running really, really slowly now: https://github.com/openforcefield/openff-qcsubmit/actions/runs/5554756531/jobs/10144963963
I haven't looked into why

Superseded by the already-merged #218


Print: Entry, ":CFBundleIdentifier", Does Not Exist

after the react-native run ios command, I got this bug
Installing build/Build/Products/Debug-iphonesimulator/example.app
An error was encountered processing the command (domain=NSPOSIXErrorDomain, code=22):
Failed to install the requested application
The bundle identifier of the application could not be determined.
Ensure that the application's Info.plist contains a value for CFBundleIdentifier.
Print: Entry, ":CFBundleIdentifier", Does Not Exist

Command failed: /usr/libexec/PlistBuddy -c Print:CFBundleIdentifier build/Build/Products/Debug-iphonesimulator/example.app/Info.plist
Print: Entry, ":CFBundleIdentifier", Does Not Exist

React Native version:
Environment:
OS:  macOS 10.14.2
Node:  10.15.3
Yarn:  0.17.10
npm:  6.4.1
Watchman:  4.6.0
Xcode:  Xcode 10.1 Build version 10B61
Android Studio:  3.3 AI-182.5<IP_ADDRESS>14842
Packages: (wanted => installed)
react: 16.2.0 => 16.2.0
react-native: 0.52.x => 0.52.3
Steps To Reproduce

clone this repo https://github.com/archriss/react-native-snap-carousel/tree/master/example
run react-native run-ios

Describe what you expected to happen:
the demo app run in simulator
Snack, code example, or link to a repository:
https://github.com/archriss/react-native-snap-carousel/tree/master/example

Sometimes you can have old or duplicated pods in your project. This is a snapshot from when i had a problem before and how our company solved it! Let me know if this works and good luck!
Command failed: /usr/libexec/PlistBuddy -c Print:CFBundleIdentifier build/Build/Products/Debug-iphonesimulator/cheapreats.app/Info.plist
Print: Entry, ":CFBundleIdentifier", Does Not Exist
DELETE THIS LINE FROM Podfile: + pod 'react-native-blur', :path => '../node_modules/react-native-blur'
Notice* If the app breaks suddenly make sure none of the packages in package.json is using this symbol "^" since it can cause unexpected errors.

@craigcosmo can you update your React Native version? 0.52 is several versions behind (we're at 0.59 right now).


Fix getfield of const

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 96.35%. Comparing base (d4f44d6) to head (8185712).
Report is 1 commits behind head on main.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff             @@
##             main    #1572       +/-   ##
===========================================
+ Coverage   70.42%   96.35%   +25.92%
===========================================
  Files          30        9       -21
  Lines       12754      411    -12343
===========================================
- Hits         8982      396     -8586
+ Misses       3772       15     -3757

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


refactor machine

@cjellick @will-chan

This fixes https://github.com/rancherio/rancher/issues/1048

@wlan0 Did you run (at least some) of the driver-specific tests locally for this pr?

And also did you run validation tests against it?

For the record, this pr does not address rancherio/rancher#1048

@cjellick Ran both local tests and validation tests. Both pass.

LGTM other than the one common function fix.

LGTM


Onboard ibm-ingress-nginx-operator into meta-operator

/ok-to-test

@liqlin2015 Now this operator is in the absent state, so this onboard looks good to me, I will approve it at first, and then you can e2e test with OperatorHub.
From my test, the operator is using a placeholder image.

/lgtm


[HOLD for payment 2024-06-28] Participants Migration Front End Polish

Had some more comments for @s77rt to address and we agreed to do in a follow up issue.
https://github.com/Expensify/App/pull/40254#pullrequestreview-2053852168

PR

Payment summary:

@s77rt reviewer $250 - please request in ND

Noted :) offer sent in upwork (link)

@sonialiap Accepted! Thank you!

Paid ✔


[RFC] Meta-data default behavior Relay astext API

Background
We introduced the API relay_node.astext to dump relay code into text format. This can be useful for debugging purposes, so we can get text format out. In order to enable round-trip of between the text format and the in-memory one, we introduced a meta-data section to the text format. The metadata section can be used to store the content of the model parameters as relay.Constant in JSON format and is appended to the end of the text format.
Problem
The question is:  should we set show_meta_data option in as text by default?

currently it is set to True

When we use astext for debugging, we want to skip printing meta_data section, because the base64 content of constants are meaningless and can be explosive

When we use astext for serialization, we need to include meta_data, otherwise we cannot recover the data.

Possible Solutions

set default of show_meta_data to be False, and introduce perhaps new API such as save_xx for serialization.

keep the current API default(always print meta-data), but overload __str__ and ___repr__ of RelayNode to use astext. So we can use astext for serialziation, but use print directly for debug.

Please share your thoughts, cc @dmlc/tvm-comitter @jroesch

#2533


Convert Map/Data switch to toggle button

In the map view, rather than showing both Map and Data as separate options, we hide the currently selected option and only show a button to go to the alternate interface. This additionally renames "Data" to "Table"

Looks good.  Rebased to check that no bad interactions had arisen.  Going to merge.


Exported animations don't work correctly

Describe the bug
I tried to export a .glb from .blend, but it missed some animation.
I referred to case #756 and #891 and unchecked "always sample animation" but did not work for me.
.blend file/ .gltf
animation sample.zip
Version
OS: Win10
Blender 2.93.1

Hello,
Can you please tell more precisely what animation are missing?
Regarding actions, seems all are exported:

Some errors occurs, linked to negative keyframes. This is not allowed on glTF specification.
We should probably add a warning or error message.
Grabbing all keyframes and move +5 keyframes to have only positive keyframe will solve that.
Don't hesitate to comment if I missed something else.

Hello,
2 months without any answer. I am going to close this ticket.
Negative frames will be handle in #387
Don't hesitate to comment if you have some new info to share


feat(abi): throw errors rather than returning string from noirc_abi_wasm

Description

Problem*

Resolves
Summary*
This PR changes the behaviour of noirc_abi_wasm to throw on errors rather than returning a string.
Documentation

[ ] This PR requires documentation updates when merged.

[ ] I will submit a noir-lang/docs PR.

[ ] I will request for and support Dev Rel's help in documenting this PR.

Additional Context

PR Checklist*

[x] I have tested the changes locally.
[x] I have formatted the changes with Prettier and/or cargo fmt on default settings.

Related to removing the JS code for input validation which Kev added.


Configured resolvers arent always used.

What version of the package are you using?
a1d00125a60032bae3bbbea756ea637d7105c568
What are you trying to do?
I am using certmagic through caddy, while in a network that uses split-head DNS, to get a certificate using the Loopia DNS plugin.
Resolvers are configured to use the external registrar DNS and that works fine on Windows but
whenever I tried to do the same on Linux it fails to get a certificate. When I moved the Linux machine off to a network that wasn't affected by this split-head DNS it worked.
This isn't affected by the Loopia DNS plugin per se but the fact that caddy cant find the SOA for the domain it tries to validate and then on Linux falls back to using whatever DNS-server it finds in /etc/resolve.conf, regardles of what I configure in the resolvers value in the Caddyfile or JSON config.
What steps did you take?
Don't really know how to simulate this without setting up some DNS-stuff.
I found out that it happens by using tcpdump and logging the DNS traffic while caddy tried to get a certificate.
Then by plainly looking at the source code for certmagic.
What did you expect to happen, and what actually happened instead?
I expected caddy / certmagic to use the external DNS-server(s) I had configured as resolvers.
It ended up using the internal DNS-servers it found in /etc/resolve.conf
How do you think this should be fixed?
I made a change in PR #131 that lets you add the string !importantas either a suffix or separate entry to the DNS-server in the configured resolvers.
If that is not accepted I need a way to tell certmagic (through caddy) to use the DNS servers I configure and nothing else.
Please link to any related issues, pull requests, and/or discussion

https://caddy.community/t/windows-linux-amd64-validates-acme-dns-but-raspberry-os-armv7l-does-not/12595/9
PR #131

Bonus: What do you use CertMagic for, and do you find it useful?
I use it with caddy and I find it really good and useful. Who knows if I end up using it in some other fashion. Either way I am happy that I have found out about it.

Thanks for the PR.  I wonder if there's ever any good reason to use the fallback resolvers when the user explicitly configures certain resolvers. If not, maybe we should just make that always be the case (use only user-configured resolvers). What do you think?

I hate it to but I couldn't figure out a way to make it backwards compatible in a simpler way.
I'd prefer to have it use whatever resolvers that is configured and nothing else, no fallback.
I can create another PR if you want to.

Yeah, I think it's unexpected to use resolvers that aren't configured. That is probably a bug (and I think a remnant of how lego works, from when we borrowed the DNS logic from there). If resolvers are explicitly configured, only those should be used.
So yeah, if you want to update your PR to do that instead, that'd probably be good! :+1:

I don't have time today, but I'll fix it tomorrow morning ( UTC+1).

Sure, thanks so much! No hurry.


[production] Email address for login is case sensitive

Steps

Login to the OSF using your email/password as you normally enter it
Log out of the OSF.
Login again, but this time type your email address in all caps, or with some capitalization scheme you did not use in step 1.

Expected
User would be able to login regardless of capitalization
Actual
User receives error message, The email or password you entered is incorrect.

@icereval ... is the fault in CAS or OSF?

Fixed in https://github.com/CenterForOpenScience/cas-overlay/commit/50153bf6057459ea413bf64891e3f7d8421afb9e


Paginate method append skip empty params

Laravel Version: 5.5.19

Description:
My url request is ?admin_id=1&in_work&check_visit_client
$items->appends(Request::all())->links('vendor.pagination.bootstrap-4');

In 2 and next pages params in_work and check_visit_client dissapear.

Can you be more clear on this? Steps to reproduce? What is the problem? What you expected to happen and what was the actual output?

In second page and next pages i have ?admin_id=1&page=2
Expected is ?admin_id=1&in_work&check_visit_client&page=2

Please ask on the forums, this repo is for bug reporting only. You can use https://laracasts.com/discuss or https://laravel.io/forum which are forums with a very large community of developers helping each other.

But its a bug of paginating... Why empty params are skipped?
Request::all() returns all params:
[
    'in_work' => '',
    'check_visit_client' => ''
]

@projct1 try the forums and include more details, if you try and replicate this on a fresh laravel installation you'll find it working fine, so there must be something in your code, so please open a forum thread and include as much details as possible for people to be able to assest you.

Paginator ignores null value
$p = new Paginator(['item1', 'item2', 'item3'], 2, 1);
$queryParams = ['queryParam1' => 'value1', 'queryParam2' => '', 'queryParam3' => null];
$p->appends($queryParams);
$p->url(1); //gives "/?queryParam1=value1&queryParam2=&page=1" without queryParam3

Yea, but Request::all() returns not null values as empty. So, paginator must be save empty (not null) values.


Ajax  grid Paging/Fliters  behaviour with Form Tag

Hello
There is an issue with how paging and fliters behaves when the grid is inside the "Form" tag helpers  . What happends is when a page button or fliters is clicked firstly it hits the get method in the server side as its the  default behaviour but  then soon after the post method is fired . Whatever post method is defined in the 'Form'  tag helper gets executed .
Is there any way we can make the page buttons and filters only to fire the get method and not the post ???

I did fix the grid buttons firing submits in forms before, which grid version are you using?

I am on version 4.0.1

Try upgrading to at least v4.0.2.

Upgraded it ..still same issue

Scripts and views too? If yes then you will have to create a small repro I can look at.

Thanks ..it works with version with 4.0.2


Make a server config file

This is where the runner script should get the value for FLASK_APP.
Actually, maybe that's fine as is.

This file should have the server port though. (Update the readme)


Remove useless meteor-node-stubs

Reflect-metadata have somewhere a
let nodeCrypto = isNode && require('crypto');

making the meteor compiler asking for meteor-node-stubs (that's why it's a dependency of angular2-meteor I suppose) but we do not need it. Is it a good way to avoid installing it ? Because it is quite big.

On production, my .js file is:

536Ko with meteor-node-stubs
359Ko by simply removing meteor-node-stubs

https://github.com/meteor/meteor/issues/7020

There is no way to avoid installing meteor-node-stubs until Reflect-metadata has two separate versions for NodeJS and browsers.

Another way is to not import reflect-metadata directly and use barbatus:angular2-runtime instead.

Hum, I really prefer importing angular through npm because it avoid some dependencies duplication and allow a beter control. But I will try to put just reflect-metadata in an meteor package

Following this idea I created a simple package with just the package.js file:
Package.describe({
    name: 'angular2-shim',
    summary: '',
    version: '0.0.1',
    git: '',
    documentation: ''
});

Npm.depends({
    'reflect-metadata': '0.1.3',
    'zone.js': '0.6.12'
});

Package.onUse(function (api) {
    api.use('modules');

    api.addFiles([
        '.npm/package/node_modules/reflect-metadata/Reflect.js',
        '.npm/package/node_modules/zone.js/dist/zone.js',
    ], 'client');
});

And  no more needs to make an import "reflect-metadata" or import "zone.js", and no more needs for meteor-node-stubs.
Because it's a shim we could add this inside angular2-compiler or create a angular2-shim. What do you think ?

@hlehmann thank you for that solution.
As said here and here, reflect-metadata should have a better solution for distinguishing between Node and the browser otherwise not only Meteor but any other client bundling tool will require a shim for crypto.
So I think having your package mentioned as a temporary solution for this issue is a good enough for now but I have 3 more thoughts:

Could you open a relevant issue on reflect-metadata and link to Ben's comment on the Meteor issue?
Could you PR the tutorial to mention you package?
Maybe change the name of your package to something more specific to the reflect-metadata problem?  angular2-shim is very general and I'm not sure it's covering it all (unless this is the plan and it that case, forget about it)

@hlehmann It's said above that barbatus:angular2-runtime does the same.

Following this idea I created a simple package with just the package.js file:
Package.describe({
    name: 'angular2-shim',
    summary: '',
    version: '0.0.1',
    git: '',
    documentation: ''
});

Npm.depends({
    'reflect-metadata': '0.1.3',
    'zone.js': '0.6.12'
});

Package.onUse(function (api) {
    api.use('modules');

    api.addFiles([
        '.npm/package/node_modules/reflect-metadata/Reflect.js',
        '.npm/package/node_modules/zone.js/dist/zone.js',
    ], 'client');
});

And  no more needs to make an import "reflect-metadata" or import "zone.js", and no more needs for meteor-node-stubs.
Because it's a shim we could add this inside angular2-compiler or create a angular2-shim. What do you think ?

@barbatus does barbatus:angular2-runtime includes a shim for that as well?

@Urigo shim for what?

I see, so @hlehmann does using barbatus:angular2-runtime works for you?  can I close this?

My bad @barbatus I didn't really understand the role of barbatus:angular2-runtime (I thought angular2 was include in there but no) and it works well.
Also @barbatus removed meteor-node-stubs from dependencies so I'm closing this issue. Thanks.


dart.exe -- should be signed on windows?

I downloaded a -dev build of the Dart SDK on windows. DartEditor.exe "just works" and shows up signed by Google. However, none of the files in dart-sdk\bin\* appear to be signed, such as the Dart VM. this means these files can result in false positives from virus scanners, etc.
CC'd Rico, I wasn't sure how to correctly triage this.

assumed stale


Release 1.22.8 Feedback

Portfolio

On the Portfolio page, "Total Balance of Wallet Address" should be renamed "Total Portfolio Balance" and include the sum of all values within "ALLOCATION BY TYPE" rather than just the wallet balance.
Add Watched Bond Address, from the Bonds tab, to the Bonds total. The watch bond feature is so bonds can be added

Bonds

Add a tool tip for the "Add to watch list button"

Add a Bonds total at the top, like every other tab - it should then be the same value in the Portfolio tab

EVM

Cannot send ETH.Link from Ledger to Keystore. Transaction never arrives on the ledger

Sending THOR - gas is in THOR but should be in ETH as gas is charged in ETH

Settings

White list - when opened, sort by enabled first so the enabled ones are at the top. This is good for people looking to disable tokens

fee is fixed. .see #475

done
On the Portfolio page, "Total Balance of Wallet Address" should be renamed "Total Portfolio Balance" and include the sum of all values within "ALLOCATION BY TYPE" rather than just the wallet balance.


[WIP] python: Improve yapf formatting

Signed-off-by: Ryan Northey<EMAIL_ADDRESS>Commit Message: python: Improve yapf formatting
Additional Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Deprecated:]
[Optional API Considerations:]

this adds a couple of rules to the yapf formatting that make it easier to stick within line length limits and improve readability of code with hanging indents


Programming Language - Multiple "Additional Resources for Rust"

IMPORTANT: When creating your Pull Request, please use the following format for the title: Category - Resource Name & Section
Description:
Hey @jfmartinz, I have added Multiple Additional Resources for Rust Programming Language such as:

Build Systems in Rust.
Linux Development in Rust.
Testing.
Debugging.
Deployment.
Rust Beginner Books.
Multiple Advanced Books.
Rust Exercises.
Rust Multiple CheatSheets.

Pls take a look and review it, Thank You!!
Checklist:
Before submitting your pull request, ensure that you have completed the following tasks:

[x] I have carefully reviewed and adhered to the contributing guidelines before creating this pull request.
[x] I followed the prescribed PR title template. (Check this if you're adding a resource)

Hey @jfmartinz could you please merge this PR, Thank You!

Please merge it @jfmartinz thank you

Hey @jfmartinz Please Merge this PR and if possible add level 2 label, Thank You!


[SPARK-17892] [SQL] [2.0] Do Not Optimize Query in CTAS More Than Once #15048

What changes were proposed in this pull request?
This PR is to backport https://github.com/apache/spark/pull/15048 and https://github.com/apache/spark/pull/15459.
However, in 2.0, we do not have a unified logical node CreateTable and the analyzer rule PreWriteCheck is also different. To minimize the code changes, this PR adds a new rule AnalyzeCreateTableAsSelect. Please treat it as a new PR to review. Thanks!
As explained in https://github.com/apache/spark/pull/14797:

Some analyzer rules have assumptions on logical plans, optimizer may break these assumption, we should not pass an optimized query plan into QueryExecution (will be analyzed again), otherwise we may some weird bugs.
For example, we have a rule for decimal calculation to promote the precision before binary operations, use PromotePrecision as placeholder to indicate that this rule should not apply twice. But a Optimizer rule will remove this placeholder, that break the assumption, then the rule applied twice, cause wrong result.

We should not optimize the query in CTAS more than once. For example,
spark.range(99, 101).createOrReplaceTempView("tab1")
val sqlStmt = "SELECT id, cast(id as long) * cast('1.0' as decimal(38, 18)) as num FROM tab1"
sql(s"CREATE TABLE tab2 USING PARQUET AS $sqlStmt")
checkAnswer(spark.table("tab2"), sql(sqlStmt))

Before this PR, the results do not match
== Results ==
!== Correct Answer - 2 ==       == Spark Answer - 2 ==
![100,100.000000000000000000]   [100,null]
 [99,99.000000000000000000]     [99,99.000000000000000000]

After this PR, the results match.
+---+----------------------+
|id |num                   |
+---+----------------------+
|99 |99.000000000000000000 |
|100|100.000000000000000000|
+---+----------------------+

In this PR, we do not treat the query in CTAS as a child. Thus, the query will not be optimized when optimizing CTAS statement. However, we still need to analyze it for normalizing and verifying the CTAS in the Analyzer. Thus, we do it in the analyzer rule PreprocessDDL, because so far only this rule needs the analyzed plan of the query.
How was this patch tested?

Test build #67018 has started for PR 15502 at commit 9cfebc5.

Test build #67018 has finished for PR 15502 at commit 9cfebc5.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class AnalyzeCreateTableAsSelect(sparkSession: SparkSession) extends Rule[LogicalPlan]

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

Merged build finished. Test PASSed.

cc @yhuai @hvanhovell @cloud-fan I guess this needs to be merged to 2.0.2 ASAP?

LGTM, merging to 2.0!

Thanks! Close it now.


Add include_data_types flag to generate_source macro

This is a:

[ ] bug fix PR with no breaking changes — please ensure the base branch is main
[x] new functionality — please ensure the base branch is the latest dev/ branch
[ ] a breaking change — please ensure the base branch is the latest dev/ branch

Description & motivation
Closes https://github.com/dbt-labs/dbt-codegen/issues/75
Checklist

[x] I have verified that these changes work locally
[x] I have updated the README.md (if applicable)
[x] I have added tests & descriptions to my models (and macros if applicable)
[ ] I have added an entry to CHANGELOG.md

@clrcrl or @matt-winkler, could you please take a look?

Maybe, @dbeatty10 could take a look?


Question about deleting story segments or entire story

Is there a way to have the bot delete the oldest story segments? I had a bot reach what I think was the max story of 4950 seconds and get Forbidden errors when trying to post further and thus needed to wait 24 hours for it to clear.
Thanks

Yes, I just need to implement the method on SnapchatBot that calls /bq/delete_story, will get on that soon

Awesome thank you!
On Feb 23, 2015 3:01 PM, "Anastasis Germanidis"<EMAIL_ADDRESS>wrote:

Yes, I just need to implement the method on SnapchatBot that calls
/bq/delete_story, will get on that soon
—
Reply to this email directly or view it on GitHub
https://github.com/agermanidis/SnapchatBot/issues/17#issuecomment-75646350
.

One other question related to the story. Do you have any idea why I might occasionally be getting a "403 Forbidden Error" when trying to post to the story. It happens fairly frequently and causes the bot to crash. I noticed it only started happening after the bot started posting quite a lot to the story. But even after letting the story refresh it is continuing to happen frequently. Possibly Snapchat limiting the accounts allowed post frequency?

That's likely Snapchat blocking your IP/account. Try to increase the timeout on the listen method.

Up to implement this ! :+1:

I added a delete_story method on SnapchatBot. My IP has been temporarily blocked by Snapchat right now, so I didn't have time to fully test this, but let me know if you encounter any issues.

Awesome !


#873 Add support for resource arrays in tables

PR Checklist:

[x] Link to related issues: closes #873
[x] Add changelog entry linking to issue, describe API changes
[ ] Add tests (optional)
[ ] (If new feature) add to description / readme

Tests seem a bit flaky, but pass. LGTM


Debugging Plugin

When trying your steps to debug QuickLook plugin I get the following error:
Message from debugger: cannot attach to process due to System Integrity Protection
Program ended with exit code: -1

Thanks for checking this. Indeed, the project hasn't been updated since a while, and Apple played a lot with their security policies in the meantime. I can reproduce the problem, but I still need to find a solution.
The README file must also be updated, as it doesn't reflect correct state of the debugging process.

I found a partial solution. When setting up your Xcode "scheme" to automatically launch qlmanage, you should uncheck "Debug executable":

However, after that, I still don't have the QuickLook window. If I run the command manually from Terminal, I get the old error I know since too much time, and against which I could find anything:
*** CFMessagePort: bootstrap_register(): failed 1100 (0x44c) 'Permission denied', port = 0xaf03, name = 'com.apple.CFPasteboardClient'
See /usr/include/servers/bootstrap_defs.h for the error codes.

Yea, tried the disable Debug executable but then can't put break points or debug

Agree, I'm stuck. It seems that it is anyway related to the fact that the QuickLook server has been sandboxed since Mavericks. And there is no small window to go through... See for instance https://lists.apple.com/archives/xcode-users/2015/Mar/msg00088.html

It is too bad there is not a wrapper QuickLook client for debugging.

I've stopped hoping for, unfortunately. You couldn't imagine the time spent on just finding some rare piece of documentation for the development of quicklook plugins by themselves.

I tried to edit this file sudo vi /usr/share/sandbox/qlmanage.sb and change (debug deny) to (debug allow) but system won't allow me to edit for some reason.

FYI,
I've played with QuickLook plugins a lot today. I've found that the following error appears to be a red herring. Even though that message is sent to console it still renders.
2016-12-24 16:18:56.880 qlmanage[79253:2286721] *** CFMessagePort: bootstrap_register(): failed 1100 (0x44c) 'Permission denied', port = 0xaf03, name = 'com.apple.coredrag'
See /usr/include/servers/bootstrap_defs.h for the error codes.
2016-12-24 16:18:56.937 qlmanage[79253:2286721] *** CFMessagePort: bootstrap_register(): failed 1100 (0x44c) 'Permission denied', port = 0xe43b, name = 'com.apple.tsm.portname'
See /usr/include/servers/bootstrap_defs.h for the error codes.
2016-12-24 16:18:56.939 qlmanage[79253:2286721] *** CFMessagePort: bootstrap_register(): failed 1100 (0x44c) 'Permission denied', port = 0xe703, name = 'com.apple.CFPasteboardClient'
See /usr/include/servers/bootstrap_defs.h for the error codes.

Did you manage to find a complete setup with rendering and breakpoints active from within Xcode?

I've not been able to get break points working but I can see logs in XCode. I have been able to debug and set break points in Hopper but this is far less than ideal. But I am using Hopper to see if I can get a much better understanding of how QuickLook works internally but it is very tedious.
To run in debugger I had to turn off SIP in OSX. This is how I did it:

Restart your Mac.
Before OS X starts up, hold down Command-R and keep it held down until you see an Apple icon and a progress bar. Release. This boots you into Recovery.
From the Utilities menu, select Terminal.
At the prompt type exactly the following and then press Return: csrutil disable
Terminal should display a message that SIP was disabled.
From the  menu, select Restart.

You can re-enable SIP by following the above steps, but using csrutil enable instead.

I've been talking to the folks at Apple and they confirm that for now we need to disable SIP in order to debug QuickLook plugins. I'll file a bug with them but that won't help in the short term. Here is the response for your reference:
Xcode is not allowing qlmanage tool to run in this mode, or qlmanage tool is not configured to work with Xcode in that way.  This is a bug in the qlmanage tool, you should not have to disable SIP (System Integrity Protection) to debug your quicklook generator plugin like that.

As a workaround you can disable SIP when debugging.  Go to this article on how to do that -

https://developer.apple.com/library/content/documentation/Security/Conceptual/System_Integrity_Protection_Guide/ConfiguringSystemIntegrityProtection/ConfiguringSystemIntegrityProtection.html

Obviously that’s less than ideal.  It seems to me that either the system or Xcode should provide a better way of dealing with this (either by the system modernizing the qlmanage tool or by Xcode providing some sort of direct support for debugging quicklook plugins).  Please file a bug at “http://bugreporter.apple.com” outlining the issue.

PLEASE: make sure you turn SIP back on when you are finished debugging!

In Xcode 8 you set your plugin debug target’s executable to qlmanage.  Do the following -

1) select the debug target
2) select “Edit Scheme…” in the project window’s toolbar
3) select 'Run' from the list on the left
-> the Info tab of the display on the right
4) choose “Other…” from the Executable popup. A standard file sheet will appear.
5) Type cmd-shift-g. A 'Go to folder' sheet appears with a text field.
6) Enter /usr/bin/ and hit the Go button.
-> The standard file sheet should now be showing the contents of /usr/bin.
7) Select and open the 'qlmanage' binary
8) Turn on the 'Debug executable' checkbox and click the Choose button.

Setting the executable arguments, do the following -

To use the qlmanage executable on a test document, please edit the arguments to point to the file you want to preview -

1) Select the “Arguments” tab in the Run scheme Edit sheet.
2) Add “-p ~/Desktop/” as the first argument. This is a path to a file that should already exist. Your plugin will be asked to render previews of this file.
3) Add “-c as the second argument to be passed on launch. You may need to change this depending on the kind of UTIs your plugin supports.
4) Add "-g $(CONFIGURATION_BUILD_DIR)/<your plugin name>.qlgenerator" as the second argument. This resolves to a path to the debug version of your plugin.
5) Close the Schemes sheet.

You can also test your Quick Look plug in from Terminal by using this as an example:

qlmanage -g .qlgenerator -p -c

Sometimes, you may need to manually kill off the quicklook daemon to get it to reload a new version of your plugin.
You can do so via the following in Terminal:

	killall quicklookd

To package your quicklook generator plugin with your app, just build it as a dependency target in your main project, include that plug in part of the install package, and the plugin should be installed in either /Library/QuickLook or ~/Library/Quicklook, depending on if you want the plugin to be used across multiple users or for just one specific user.

Not much there that we did not already know but it is good to have the confirmation.

Thanks a lot for sharing all of this, I appreciate very much. I'll close the issue for now, but this will remain definitely a key source of info for that kind of problems.


What is the problem when the userId is not set?

I have the following entry in _raix_push_app_tokens. The userId is null and thus the user cannot receive any push notifications. The user was logged in several times. Do I have to call push-setuser  manually?
{
    "_id" : "Qf6C8ndRPaLTHkQBg",
    "token" : {
        "gcm" : "APA91bEDL8CJNkbBsTbCzskheYftgfIjWbye6zcQd-e4Of6e1Lov_Vc7LDP9qVhI4uplRpwTO_jVtocWLD93P7iQw2dF9IRD75aFtBHTe1M20-L_1bNgOObCB9z_AEMcGAqLh3tc7VP5SVoyzZFAFAqY8uilzzQwaw"
    },
    "appName" : "main",
    "userId" : null,
    "createdAt" : ISODate("2015-04-10T15:23:38.773+0200"),
    "updatedAt" : ISODate("2015-04-10T15:23:38.773+0200")
}

Ok. Now I use
document.addEventListener('deviceready', function() {
    Push.addListener('token', function(token) {
          Session.set("token", token) ;
    });
});

and in the callback of the login function I use Push.setUser
 Meteor.loginWithPassword(username, password, function(error) {
    if(!error) {
         if(Session.get("token")!==undefined){
          Push.setUser(Session.get("token"));
        }
    }
}

Odd,
https://github.com/raix/push/blob/master/lib/client/cordova.js#L49 should let you use Push.addListener without having to think about device ready.. Maybe we need same construct as https://github.com/raix/push/blob/master/lib/client/cordova.js#L240-L242
Should keep the userId uptodate:
https://github.com/raix/push/blob/master/lib/client/client.js#L118-L127

hm. Now it seems to be working again without my code above. Possibly there was another problem.

let me know if you see the issue again, would be nice to track down

+1 for userId:null

+1 for userId:null on iOS


Several tools don’t work whilst screen sharing with MS Teams

Microsoft PowerToys version
0.61.1
Running as admin

[ ] Yes

Area(s) with issue?
General
Steps to reproduce
Join an MS Teams call, share your screen.
ColorPicker and Mouse Utilities (find my mouse) do not appear/open (and possibly other tools but not tested). Mouse utilities would be useful for demonstration during Teams calls.
✔ Expected Behavior
Both tools to work as normal.
❌ Actual Behavior
Both tools do not open whilst screen sharing on MS teams.
Other Software
MS Teams (work)

I can't reproduce this.

Perhaps it's a domain policy on my machine or some other conflict then. Thanks for looking into this.