The hover effect on the buttons in the header is moved one pixel down.

Current behavior
By hovering over the buttons in the header, hover effect moves one pixel down.

Expected behavior
Hovering effect should be aligned with the header.
Steps to reproduce the issue

Hover over any buttons in the header
Look at hamburger menu

Repository

Can you handle fixing this bug by yourself?

[ ] YES
[x] NO

Which Release Cycle state this refers to? Info for developer.
Pick one option.

[ ] This is a bug report for test version on https://test.storefrontcloud.io - In this case Developer should create branch from develop branch and create Pull Request 2. Feature / Improvement back to develop.
[ ] This is a bug report for current Release Candidate version on https://next.storefrontcloud.io - In this case Developer should create branch from release branch and create Pull Request 3. Stabilisation fix back to release.
[ ] This is a bug report for current Stable version on https://demo.storefrontcloud.io and should be placed in next stable version hotfix - In this case Developer should create branch from hotfix or master branch and create Pull Request 4. Hotfix back to hotfix.

Environment details

Browser:
OS:
Node:
Code Version:

Additional information

Can't reproduce this Bug on Mac with Chrome 74, Safari 12.1 and Firefox 60.3

Error only on Startpage visible, if browsercache (Chrome and Safari testet) cleaned.

The Account button in the header, the one with the avatar, contains an element: account_circle
As you can see this element has two classes; .material-icons and .block .
.material-icons assigns a display:inline-block rule to this element, while .block should override this by assigning a display: block rule.
It seems that is a matter of which stylesheet is loaded first because on https://next.storefrontcloud.io/ I can reproduce this error by refreshing multiple times. Sometimes the bug appears and sometimes it doesn't.
The styling rules for .material-icons are located in a css file of which the load is initiated by webfont.js, the function is located in index.template.html

Przemek can you take this one as well?

Fixed with 1.10


Missing endianess conversion for dense constant lowering to LLVM dialect

I am using onnx-mlir to build models for Sparc CPU target, which is big-endian, and I am facing a data conversion issue caused by the string type initialization used for large dense constants.
MLIR's IR and LLVM's IR expect the data representation to be little-endian until the code generation for the target system is performed; then, data is transformed to adhere to the target system's endianness according to the data type.
During the Krnl to LLVM lowering, dense raw data bigger than 1Kb is lowered to LLVM global constant as a string of bytes, thus losing the information relative to the actual data type of the initialized elements. Consequently, when code generation happens, the data endianness is not updated to that of the target system since string type is endianness independent. This leads to an incorrect constant data initialization for big-endian targets.
I understand that converting the dense constant data to a string saves space since LLVM IR stores floating-point constants as double, even for smaller data types, however, this removes the data type information needed for the endianness fix during the code generation step.
I want to contribute with a fix to this, but I would like to know which solution you think is the best for the case:

Avoid the dense-to-string conversion and keep the correct data type (this is the solution I tried, and it solves the issue, but it results in the initialization data being promoted to double until the code generation phase)
Keep the current implementation and perform the byte-swapping operations on the generated string of bytes (I do not know which is the proper way to implement this, but this may be a better solution from the space-saving point of view)

Please let me know if you are interested and what you think is the best approach to solve the issue.

Hi @Ansaya, thanks for looking at this! FYI, we are using Z machines which are big-endian also, and constants work fine on them. So I would like to understand more about your issue. Do you have IRs showing the information loss? and what is the information you need to preserver, or anything concrete examples.
Though keeping the dense constants as they are would be the best, we have had to use strings here to avoid the poor performance when translating LLVMIR to LLVM: https://discourse.llvm.org/t/performance-issues-with-memref-global-and-llvm-ir/68604. It's really slow for big deep learning models.

Here are the steps to reproduce the issue starting from the mnist model available in docs/mnist_example/mnist.onnx in this repository.
onnx-mlir --EmitLLVMIR mnist.onnx-o test -mtriple=sparc -mcpu=leon3
mlir-translate --mlir-to-llvmir -o test.ll test.onnx.mlir
clang --target=sparc -mcpu=leon3 -c -o test.o test.ll
llvm-objdump --section=.rodata -D test.o 2> /dev/null | grep -A 3 constant_3_test
llvm-objdump --section=.rodata -D test.o 2> /dev/null | grep -A 3 constant_4_test

The output of the two llvm-objdump commands should look something like the following:
000001a0 <constant_3_test>:
     1a0: 91 fe 98 3d   <unknown>
     1a4: b8 ba 2e be   xnorcc %o0, 3774, %i4
     1a8: c4 b3 ed 3d   <unknown>

00000170 <constant_4_test>:
     170: 3d 13 ca a6   sethi 1297062, %fp
     174: 3c f8 5c 44   <unknown>
     178: bc 75 11 14   <unknown>

After a quick hex-to-float conversion of the first element of constant_3_test, you can see bytes are in the wrong order since the expected floating-point value is 0.0747, which corresponds to 0x3d98fe91, while reading the initialization data as a big-endian 32-bit value yields 0x91fe983d which results in wrong data.
On the other hand, data in the constant_4_test symbol is packed properly as big-endian as the expected value of the first element is 0.0360, which corresponds to 0x3d13caa6.
Looking at the test.onnx.mlir file, you can see that the constant_3 is initialized using a raw string, while constant_4 is initialized from dense data.
llvm.mlir.global internal constant @constant_4(dense<[0.0360819325, ...]>) : tensor<10xf32>) {addr_space = 0 : i32, alignment = 16 : i64} : !llvm.array<10 x f32>
llvm.mlir.global internal constant @constant_3("\91\FE\98=\B8\BA. ...") {addr_space = 0 : i32, alignment = 16 : i64}

Please let me know if you can reproduce the issue.
P.S. I did not use the --EmitObj directly so that you also have the intermediate result before the compilation happens, but you can obtain the same result by replacing --EmitLLVMIR with --EmitObj and skipping the mlir-transalte and clang commands above.

@Ansaya thank you for the example!
I followed your steps and ran on a Z machine, and the result looked good:
00000000000001a0 <constant_3_mnist>:
     1a0: 3d 98         der     %f9, %f8
     1a2: fe 91 be 2e ba b8     <unknown>
     1a8: 3d ed         der     %f14, %f13

0000000000000170 <constant_4_mnist>:
     170: 3d 13         der     %f1, %f3
     172: ca a6 3c f8 5c 44     <unknown>
     178: bc 75 11 14   <unknown>

One thing I was noticed is constant_3_mnist in the output of --EmitLLVMIR looks different from yours: llvm.mlir.global internal constant @constant_3_mnist("=\98\FE\91\BE.\BA\B8=\ED\B3\C4\BE$\ ..., bytes are already swapped.

Avoid the dense-to-string conversion and keep the correct data type (this is the solution I tried, and it solves the issue, but it results in the initialization data being promoted to double until the code generation phase)

If this solves your issue, I am OK if you would like to add a compiler flag that disables dense-to-string conversion.

This may be related to the fact that your build and target machine are the same, which is not true in my case. I build the executable on an X86 little-endian machine targeting a Sparc big-endian machine. Thus, the input weights have a different endianness with respect to the target. In your case, you may be able to reproduce the issue by setting a little-endian machine as the target.


ci: error out for invalid component in commit header

if the commit header is not present in the list of the component we maintain. the commitlint check should show an error instead of showing the warning.
Signed-off-by: Madhu Rajanna<EMAIL_ADDRESS>

@mergifyio backport ci/centos

/test commitlint

/retest ci/centos/mini-e2e-helm/k8s-1.18.5


Last commit (webgl tweaks) can produce a bug

Hello,
This commit : https://github.com/GoodBoyDigital/pixi.js/commit/4b5cab7fabce38d39137b0f6585849c2e8cfec4a
can cause an issue here :
   this._updateTextureBound = function(e){
        this.updateTexture(e.target);
    }.bind(this);

    this._destroyTextureBound = function(e){
        this.destroyTexture(e.target);
    }.bind(this);

"e" can be the basetexture object in some cases. I suspect that it happens when Basetexture.source is null.
I'll try to produce a test case if the fix isn't obvious for you, @GoodBoyDigital

I got the same issue, here is a simple test with only a container and a text
No update on text, no error
http://inateno.com/protos/pixi/text_bug/index.html
Set text on loop, got the error
http://inateno.com/protos/pixi/text_bug/withUpdate.html
I try to check for fix, also this demo work if I use the pixi.js from bin directory on the dev branch, but if I build a new with last files, I got the error.
It seem this come from the last push on WebGLRenderer:
    texture.on('update', this.updateTexture, this);
    texture.on('dispose', this.destroyTexture, this);

replaced by _updateTexureBound as said @JiDW

Curious why this change was made @GoodBoyDigital, not sure what e.target is supposed to be?

this was an error on my side peeps! I accidentally committed some old changes.. Shame on me :/
All fixed now though in the dev branch now though :+1:


Fails to start when "Sync Settings" is active in a machine where the primary EXE is not installed

Cannot use Windows Terminal at all.
Environment
Windows 10 19H1
PowerShell Preview 6 installed in machine 1
PowerShell Preview 7 installed in machine 2
Windows "Sync Settings" is active.
Windows build number: [run "ver" at a command prompt]
Windows Terminal version (if applicable):

Any other software?

Steps to reproduce

Install Windows Terminal in 2 machines with the same MSA account.
Install PowerShell Core in machine 1.
Change the default console to be PowerShell Core.
Log out and wait for settings to sync.
Log into Machine 2.

Start Windows Terminal.
Expected behavior
Windows Terminal can start (even in CMD or some recovery console mode)

Actual behavior
Windows Terminal fails to start

The settings from machine 1 are getting copied to machine 2, but this is invalid as machine 2 does not have the same environment as machine 1.

I'm going to consolidate these discussions in #1770. Thanks, Oscar!


Remapped CapsLock to Backspace throws error when used

Description
I have remapped the CapsLock key to Backspace at OS level, but I can't use it in flutter applications.
When trying to delete text inside TextField using the CapsLock I get the following error (and the characters are not deleted), using target device Linux Desktop:
=════════ Exception caught by services library ══════════════════════════════════
Attempted to send a key down event when no keys are in keysPressed. This state can occur if the key event being sent doesn't properly set its modifier flags. This was the event: RawKeyDownEvent#ba79a(logicalKey: LogicalKeyboardKey#00008(keyId: "0x100000008", keyLabel: "Backspace", debugName: "Backspace"), physicalKey: PhysicalKeyboardKey#70039(usbHidUsage: "0x00070039", debugName: "Caps Lock"), repeat: false) and its data: RawKeyEventDataLinux#4f50b(toolkit: GTK, unicodeScalarValues: 8, scanCode: 66, keyCode: 65288, modifiers: 33554432, isDown: true)

The remap always worked perfectly in other (non flutter) linux desktop applications.
When using Chrome as target I get the following error:
══╡ EXCEPTION CAUGHT BY SERVICES LIBRARY╞══════════════════════════════════════════════════════════
The following assertion was thrown during a platform message callback:
Assertion failed:
file:///home/gruvw/snap/flutter/common/flutter/packages/flutter/lib/src/services/raw_keyboard.dart:682:7
../…/services/raw_keyboard.dart:682
event is! RawKeyDownEvent || _keysPressed.isNotEmpty
"Attempted to send a key down event when no keys are in keysPressed. This state can occur if the key
event being sent doesn't properly set its modifier flags. This was the event:
RawKeyDownEvent#e94da(logicalKey: LogicalKeyboardKey#c2435(keyId: \"0x100000104\", keyLabel: \"Caps
Lock\", debugName: \"Caps Lock\"), physicalKey: PhysicalKeyboardKey#70039(usbHidUsage:
\"0x00070039\", debugName: \"Caps Lock\"), repeat: false) and its data:
RawKeyEventDataWeb#c3920(code: CapsLock, key: Backspace, location: 0, metaState: 0, keyCode: 8)"
When the exception was thrown, this was the stack:
dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/errors.dart 29:3        assertFailed
packages/flutter/src/services/raw_keyboard.dart 682:49                            handleRawKeyEvent
packages/flutter/src/services/hardware_keyboard.dart 878:30                       handleRawKeyMessage
dart-sdk/lib/_internal/js_dev_runtime/patch/async_patch.dart 84:54                runBody
dart-sdk/lib/_internal/js_dev_runtime/patch/async_patch.dart 123:5                _async
packages/flutter/src/services/hardware_keyboard.dart 850:51                       handleRawKeyMessage
packages/flutter/src/services/platform_channel.dart 197:49                        <fn>
dart-sdk/lib/_internal/js_dev_runtime/patch/async_patch.dart 84:54                runBody
dart-sdk/lib/_internal/js_dev_runtime/patch/async_patch.dart 123:5                _async
packages/flutter/src/services/platform_channel.dart 196:58                        <fn>
packages/flutter/src/services/binding.dart 387:35                                 <fn>
dart-sdk/lib/_internal/js_dev_runtime/patch/async_patch.dart 84:54                runBody
dart-sdk/lib/_internal/js_dev_runtime/patch/async_patch.dart 123:5                _async
packages/flutter/src/services/binding.dart 384:98                                 <fn>
lib/_engine/engine/platform_dispatcher.dart 1199:13                               invoke2
lib/ui/channel_buffers.dart 25:12                                                 invoke
lib/ui/channel_buffers.dart 65:7                                                  push
lib/ui/channel_buffers.dart 130:16                                                push
lib/_engine/engine/platform_dispatcher.dart 364:25                                invokeOnPlatformMessage
lib/_engine/engine/keyboard.dart 130:39                                           [_handleHtmlEvent]
lib/_engine/engine/keyboard.dart 32:7                                             <fn>
dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/operations.dart 334:14  _checkAndCall
dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/operations.dart 339:39  dcall
════════════════════════════════════════════════════════════════════════════

However, it correctly deletes a character on web target.

Logs
flutter run --verbose
[  +33 ms] executing: uname -m
[  +16 ms] Exit code 0 from: uname -m
[        ] x86_64
[   +3 ms] executing: [/home/gruvw/snap/flutter/common/flutter/] git -c log.showSignature=false log -n 1 --pretty=format:%H
[   +4 ms] Exit code 0 from: git -c log.showSignature=false log -n 1 --pretty=format:%H
[        ] d9111f64021372856901a1fd5bfbc386cade3318
[        ] executing: [/home/gruvw/snap/flutter/common/flutter/] git tag --points-at d9111f64021372856901a1fd5bfbc386cade3318
[  +11 ms] Exit code 0 from: git tag --points-at d9111f64021372856901a1fd5bfbc386cade3318
[        ] 3.3.5
[  +28 ms] executing: [/home/gruvw/snap/flutter/common/flutter/] git rev-parse --abbrev-ref --symbolic @{upstream}
[   +4 ms] Exit code 0 from: git rev-parse --abbrev-ref --symbolic @{upstream}
[        ] origin/stable
[        ] executing: [/home/gruvw/snap/flutter/common/flutter/] git ls-remote --get-url origin
[   +4 ms] Exit code 0 from: git ls-remote --get-url origin
[        ] https://github.com/flutter/flutter.git
[  +35 ms] executing: [/home/gruvw/snap/flutter/common/flutter/] git rev-parse --abbrev-ref HEAD
[   +4 ms] Exit code 0 from: git rev-parse --abbrev-ref HEAD
[        ] stable
[  +28 ms] 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.
[  +29 ms] executing: /home/gruvw/Android/Sdk/platform-tools/adb devices -l
[  +21 ms] List of devices attached
[   +2 ms] 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 'WindowsEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSEngineArtifacts' 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.
[  +35 ms] Multiple devices found:
[  +26 ms] Linux (desktop) • linux  • linux-x64      • Ubuntu 22.04.1 LTS 5.15.0-52-generic
[        ] Chrome (web)    • chrome • web-javascript • Brave Browser <IP_ADDRESS>
[        ] [1]: Linux (linux)
[        ] [2]: Chrome (chrome)
[        ] Please choose one (To quit, press "q/Q")
[        ] :
[+7410 ms] 1
[  +16 ms] Skipping pub get: version match.
[  +79 ms] Generating /home/gruvw/SynologyDrive/Programmation/Mobile/0byte/android/app/src/main/java/io/flutter/plugins/GeneratedPluginRegistrant.java
[  +52 ms] Initializing file store
[   +5 ms] Skipping target: gen_localizations
[   +3 ms] gen_dart_plugin_registrant: Starting due to {InvalidatedReasonKind.inputChanged: The following inputs have updated contents:
/home/gruvw/SynologyDrive/Programmation/Mobile/0byte/.dart_tool/package_config_subset}
[  +12 ms] gen_dart_plugin_registrant: Complete
[        ] Skipping target: _composite
[   +1 ms] complete
[   +2 ms] Launching lib/main.dart on Linux in debug mode...
[   +2 ms] /home/gruvw/snap/flutter/common/flutter/bin/cache/dart-sdk/bin/dart --disable-dart-dev
/home/gruvw/snap/flutter/common/flutter/bin/cache/dart-sdk/bin/snapshots/frontend_server.dart.snapshot --sdk-root
/home/gruvw/snap/flutter/common/flutter/bin/cache/artifacts/engine/common/flutter_patched_sdk/ --incremental --target=flutter --debugger-module-names
--experimental-emit-debug-metadata -DFLUTTER_WEB_AUTO_DETECT=true --output-dill /tmp/flutter_tools.WIWAWE/flutter_tool.VMHFXU/app.dill --packages
/home/gruvw/SynologyDrive/Programmation/Mobile/0byte/.dart_tool/package_config.json -Ddart.vm.profile=false -Ddart.vm.product=false --enable-asserts
--track-widget-creation --filesystem-scheme org-dartlang-root --initialize-from-dill build/c075001b96339384a97db4862b8ab8db.cache.dill.track.dill --verbosity=error
--enable-experiment=alternative-invalidation-strategy
[  +13 ms] Building Linux application...
[   +5 ms] <- compile package:app_0byte/main.dart
[   +5 ms] executing: [build/linux/x64/debug/] cmake -G Ninja -DCMAKE_BUILD_TYPE=Debug -DFLUTTER_TARGET_PLATFORM=linux-x64
/home/gruvw/SynologyDrive/Programmation/Mobile/0byte/linux
[  +23 ms] -- Configuring done
[   +7 ms] -- Generating done
[        ] -- Build files have been written to: /home/gruvw/SynologyDrive/Programmation/Mobile/0byte/build/linux/x64/debug
[   +2 ms] executing: ninja -C build/linux/x64/debug install
[   +6 ms] ninja: Entering directory `build/linux/x64/debug'
[+1641 ms] [1/5] Generating /home/gruvw/SynologyDrive/Programmation/Mobile/0byte/linux/flutter/ephemeral/libflutter_linux_gtk.so,
/home/gruvw/SynologyDrive/Programmation/Mobile/0byte/linux/flutter/ephemeral/flutter_linux/fl_basic_message_channel.h,
/home/gruvw/SynologyDrive/Programmation/Mobile/0byte/linux/flutter/ephemeral/flutter_linux/fl_binary_codec.h,
/home/gruvw/SynologyDrive/Programmation/Mobile/0byte/linux/flutter/ephemeral/flutter_linux/fl_binary_messenger.h,
/home/gruvw/SynologyDrive/Programmation/Mobile/0byte/linux/flutter/ephemeral/flutter_linux/fl_dart_project.h,
/home/gruvw/SynologyDrive/Programmation/Mobile/0byte/linux/flutter/ephemeral/flutter_linux/fl_engine.h,
/home/gruvw/SynologyDrive/Programmation/Mobile/0byte/linux/flutter/ephemeral/flutter_linux/fl_json_message_codec.h,
/home/gruvw/SynologyDrive/Programmation/Mobile/0byte/linux/flutter/ephemeral/flutter_linux/fl_json_method_codec.h,
/home/gruvw/SynologyDrive/Programmation/Mobile/0byte/linux/flutter/ephemeral/flutter_linux/fl_message_codec.h,
/home/gruvw/SynologyDrive/Programmation/Mobile/0byte/linux/flutter/ephemeral/flutter_linux/fl_method_call.h,
/home/gruvw/SynologyDrive/Programmation/Mobile/0byte/linux/flutter/ephemeral/flutter_linux/fl_method_channel.h,
/home/gruvw/SynologyDrive/Programmation/Mobile/0byte/linux/flutter/ephemeral/flutter_linux/fl_method_codec.h,
/home/gruvw/SynologyDrive/Programmation/Mobile/0byte/linux/flutter/ephemeral/flutter_linux/fl_method_response.h,
/home/gruvw/SynologyDrive/Programmation/Mobile/0byte/linux/flutter/ephemeral/flutter_linux/fl_plugin_registrar.h,
/home/gruvw/SynologyDrive/Programmation/Mobile/0byte/linux/flutter/ephemeral/flutter_linux/fl_plugin_registry.h,
/home/gruvw/SynologyDrive/Programmation/Mobile/0byte/linux/flutter/ephemeral/flutter_linux/fl_standard_message_codec.h,
/home/gruvw/SynologyDrive/Programmation/Mobile/0byte/linux/flutter/ephemeral/flutter_linux/fl_standard_method_codec.h,
/home/gruvw/SynologyDrive/Programmation/Mobile/0byte/linux/flutter/ephemeral/flutter_linux/fl_string_codec.h,
/home/gruvw/SynologyDrive/Programmation/Mobile/0byte/linux/flutter/ephemeral/flutter_linux/fl_value.h,
/home/gruvw/SynologyDrive/Programmation/Mobile/0byte/linux/flutter/ephemeral/flutter_linux/fl_view.h,
/home/gruvw/SynologyDrive/Programmation/Mobile/0byte/linux/flutter/ephemeral/flutter_linux/flutter_linux.h, _phony_
[   +1 ms] [  +36 ms] executing: uname -m
[        ] [  +18 ms] Exit code 0 from: uname -m
[        ] [        ] x86_64
[        ] [   +3 ms] executing: [/home/gruvw/snap/flutter/common/flutter/] git -c log.showSignature=false log -n 1 --pretty=format:%H
[        ] [   +3 ms] Exit code 0 from: git -c log.showSignature=false log -n 1 --pretty=format:%H
[        ] [        ] d9111f64021372856901a1fd5bfbc386cade3318
[        ] [        ] executing: [/home/gruvw/snap/flutter/common/flutter/] git tag --points-at d9111f64021372856901a1fd5bfbc386cade3318
[        ] [  +11 ms] Exit code 0 from: git tag --points-at d9111f64021372856901a1fd5bfbc386cade3318
[        ] [        ] 3.3.5
[        ] [  +35 ms] executing: [/home/gruvw/snap/flutter/common/flutter/] git rev-parse --abbrev-ref HEAD
[        ] [   +4 ms] Exit code 0 from: git rev-parse --abbrev-ref HEAD
[        ] [        ] stable
[        ] [  +28 ms] 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.
[        ] [  +50 ms] executing: [/home/gruvw/snap/flutter/common/flutter/] git rev-parse --abbrev-ref --symbolic @{upstream}
[        ] [   +4 ms] Exit code 0 from: git rev-parse --abbrev-ref --symbolic @{upstream}
[        ] [        ] origin/stable
[        ] [        ] executing: [/home/gruvw/snap/flutter/common/flutter/] git ls-remote --get-url origin
[        ] [   +3 ms] Exit code 0 from: git ls-remote --get-url origin
[        ] [        ] https://github.com/flutter/flutter.git
[        ] [        ] Artifact Instance of 'MaterialFonts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'GradleWrapper' 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.
[        ] [        ] Artifact Instance of 'FlutterSdk' is not required, skipping update.
[        ] [        ] Artifact Instance of 'WindowsEngineArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'MacOSEngineArtifacts' 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.
[        ] [        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'FontSubsetArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'PubDependencies' is not required, skipping update.
[        ] [  +23 ms] Initializing file store
[        ] [   +3 ms] Done initializing file store
[        ] [  +21 ms] Skipping target: gen_localizations
[        ] [   +5 ms] Skipping target: gen_dart_plugin_registrant
[        ] [ +346 ms] Skipping target: unpack_linux
[        ] [ +251 ms] Skipping target: kernel_snapshot
[        ] [ +189 ms] Skipping target: debug_bundle_linux-x64_assets
[        ] [        ] Persisting file store
[        ] [   +5 ms] Done persisting file store
[        ] [   +3 ms] build succeeded.
[        ] [   +3 ms] "flutter assemble" took 927ms.
[        ] [ +224 ms] ensureAnalyticsSent: 222ms
[        ] [   +1 ms] Running shutdown hooks
[        ] [        ] Shutdown hooks complete
[        ] [        ] exiting with code 0
[ +207 ms] [2/5] Building CXX object CMakeFiles/app_0byte.dir/flutter/generated_plugin_registrant.cc.o
[  +35 ms] [3/5] Building CXX object CMakeFiles/app_0byte.dir/my_application.cc.o
[  +83 ms] [4/5] Linking CXX executable intermediates_do_not_run/app_0byte
[        ] [4/5] Install the project...
[   +5 ms] -- Install configuration: "Debug"
[   +7 ms] -- Installing: /home/gruvw/SynologyDrive/Programmation/Mobile/0byte/build/linux/x64/debug/bundle/app_0byte
[        ] -- Set runtime path of "/home/gruvw/SynologyDrive/Programmation/Mobile/0byte/build/linux/x64/debug/bundle/app_0byte" to "$ORIGIN/lib"
[        ] -- Installing: /home/gruvw/SynologyDrive/Programmation/Mobile/0byte/build/linux/x64/debug/bundle/data/icudtl.dat
[        ] -- Installing: /home/gruvw/SynologyDrive/Programmation/Mobile/0byte/build/linux/x64/debug/bundle/lib/libflutter_linux_gtk.so
[  +30 ms] -- Installing: /home/gruvw/SynologyDrive/Programmation/Mobile/0byte/build/linux/x64/debug/bundle/data/flutter_assets
[        ] -- Installing: /home/gruvw/SynologyDrive/Programmation/Mobile/0byte/build/linux/x64/debug/bundle/data/flutter_assets/NOTICES
[        ] -- Installing: /home/gruvw/SynologyDrive/Programmation/Mobile/0byte/build/linux/x64/debug/bundle/data/flutter_assets/shaders
[        ] -- Installing: /home/gruvw/SynologyDrive/Programmation/Mobile/0byte/build/linux/x64/debug/bundle/data/flutter_assets/shaders/ink_sparkle.frag
[        ] -- Installing: /home/gruvw/SynologyDrive/Programmation/Mobile/0byte/build/linux/x64/debug/bundle/data/flutter_assets/kernel_blob.bin
[  +28 ms] -- Installing: /home/gruvw/SynologyDrive/Programmation/Mobile/0byte/build/linux/x64/debug/bundle/data/flutter_assets/NOTICES.Z
[        ] -- Installing: /home/gruvw/SynologyDrive/Programmation/Mobile/0byte/build/linux/x64/debug/bundle/data/flutter_assets/FontManifest.json
[        ] -- Installing: /home/gruvw/SynologyDrive/Programmation/Mobile/0byte/build/linux/x64/debug/bundle/data/flutter_assets/fonts
[        ] -- Installing: /home/gruvw/SynologyDrive/Programmation/Mobile/0byte/build/linux/x64/debug/bundle/data/flutter_assets/fonts/MaterialIcons-Regular.otf
[   +1 ms] -- Installing: /home/gruvw/SynologyDrive/Programmation/Mobile/0byte/build/linux/x64/debug/bundle/data/flutter_assets/fonts/FiraCode-Bold.ttf
[        ] -- Installing: /home/gruvw/SynologyDrive/Programmation/Mobile/0byte/build/linux/x64/debug/bundle/data/flutter_assets/fonts/FiraCode-Light.ttf
[        ] -- Installing: /home/gruvw/SynologyDrive/Programmation/Mobile/0byte/build/linux/x64/debug/bundle/data/flutter_assets/fonts/FiraCode-SemiBold.ttf
[        ] -- Installing: /home/gruvw/SynologyDrive/Programmation/Mobile/0byte/build/linux/x64/debug/bundle/data/flutter_assets/fonts/FiraCode-Regular.ttf
[        ] -- Installing: /home/gruvw/SynologyDrive/Programmation/Mobile/0byte/build/linux/x64/debug/bundle/data/flutter_assets/fonts/FiraCode-Medium.ttf
[        ] -- Installing: /home/gruvw/SynologyDrive/Programmation/Mobile/0byte/build/linux/x64/debug/bundle/data/flutter_assets/packages
[        ] -- Installing: /home/gruvw/SynologyDrive/Programmation/Mobile/0byte/build/linux/x64/debug/bundle/data/flutter_assets/packages/cupertino_icons
[        ] -- Installing: /home/gruvw/SynologyDrive/Programmation/Mobile/0byte/build/linux/x64/debug/bundle/data/flutter_assets/packages/cupertino_icons/assets
[        ] -- Installing:
/home/gruvw/SynologyDrive/Programmation/Mobile/0byte/build/linux/x64/debug/bundle/data/flutter_assets/packages/cupertino_icons/assets/CupertinoIcons.ttf
[        ] -- Installing: /home/gruvw/SynologyDrive/Programmation/Mobile/0byte/build/linux/x64/debug/bundle/data/flutter_assets/version.json
[        ] -- Installing: /home/gruvw/SynologyDrive/Programmation/Mobile/0byte/build/linux/x64/debug/bundle/data/flutter_assets/AssetManifest.json
[   +6 ms] Building Linux application... (completed in 2,104ms)
[ +134 ms] Observatory URL on device: http://<IP_ADDRESS>:33607/Xg-XXGclkN0=/
[   +1 ms] Caching compiled dill
[  +27 ms] Connecting to service protocol: http://<IP_ADDRESS>:33607/Xg-XXGclkN0=/
[ +104 ms] Launching a Dart Developer Service (DDS) instance at
http://<IP_ADDRESS>:0, connecting to VM service at
http://<IP_ADDRESS>:33607/Xg-XXGclkN0=/.
[  +53 ms] DDS is listening at http://<IP_ADDRESS>:44127/gI228-XfMxg=/.
[  +32 ms] Successfully connected to service protocol:
http://<IP_ADDRESS>:33607/Xg-XXGclkN0=/
[  +25 ms] DevFS: Creating new filesystem on the device (null)
[  +11 ms] DevFS: Created new filesystem on the device
(file:///tmp/0byteXFIJBH/0byte/)
[   +1 ms] Updating assets
[  +37 ms] Syncing files to device Linux...
[        ] Compiling dart to kernel with 0 updated files
[        ] Processing bundle.
[        ] <- recompile package:app_0byte/main.dart
50cd6deb-0095-495f-b777-27ebecdb4b21
[        ] <- 50cd6deb-0095-495f-b777-27ebecdb4b21
[        ] Bundle processing done.
[  +58 ms] Updating files.
[        ] DevFS: Sync finished
[        ] Syncing files to device Linux... (completed in 61ms)
[        ] Synced 0.0MB.
[        ] <- accept
[   +1 ms] Connected to _flutterView/0x2c2eec0.
[   +1 ms] Flutter run key commands.
[        ] r Hot reload. 🔥🔥🔥
[        ] R Hot restart.
[        ] h List all available interactive commands.
[        ] d Detach (terminate "flutter run" but leave application
running).
[        ] c Clear the screen
[        ] q Quit (terminate the application on the device).
[        ] 💪 Running with sound null safety 💪
[        ] An Observatory debugger and profiler on Linux is available at:
           http://<IP_ADDRESS>:44127/gI228-XfMxg=/
[ +527 ms] The Flutter DevTools debugger and profiler on Linux is available at: http://<IP_ADDRESS>:9102?uri=http://<IP_ADDRESS>:44127/gI228-XfMxg=/
[+6738 ms] ** (app_0byte:371200): WARNING **: 09:55:52.454: Unable to retrieve framework response: Message is not valid JSON
[   +5 ms]
           ══╡ EXCEPTION CAUGHT BY SERVICES LIBRARY ╞══════════════════════════════════════════════════════════
           The following assertion was thrown during a platform message callback:
           Attempted to send a key down event when no keys are in keysPressed. This state can occur if the key
           event being sent doesn't properly set its modifier flags. This was the event:
           RawKeyDownEvent#a6a88(logicalKey: LogicalKeyboardKey#00008(keyId: "0x100000008", keyLabel:
           "Backspace", debugName: "Backspace"), physicalKey: PhysicalKeyboardKey#70039(usbHidUsage:
           "0x00070039", debugName: "Caps Lock"), repeat: false) and its data:
           RawKeyEventDataLinux#d03ab(toolkit: GTK, unicodeScalarValues: 8, scanCode: 66, keyCode: 65288,
           modifiers: 33554432, isDown: true)
           'package:flutter/src/services/raw_keyboard.dart':
           Failed assertion: line 682 pos 7: 'event is! RawKeyDownEvent || _keysPressed.isNotEmpty'

           Either the assertion indicates an error in the framework itself, or we should provide substantially
           more information in this error message to help you determine and fix the underlying cause.
           In either case, please report this assertion by filing a bug on GitHub:
             https://github.com/flutter/flutter/issues/new?template=2_bug.md

           When the exception was thrown, this was the stack:
           #2      RawKeyboard.handleRawKeyEvent (package:flutter/src/services/raw_keyboard.dart:682:7)
           #3      KeyEventManager.handleRawKeyMessage (package:flutter/src/services/hardware_keyboard.dart:878:30)
           #4      BasicMessageChannel.setMessageHandler.<anonymous closure> (package:flutter/src/services/platform_channel.dart:197:49)
           #5      _DefaultBinaryMessenger.setMessageHandler.<anonymous closure> (package:flutter/src/services/binding.dart:387:35)
           #6      _invoke2 (dart:ui/hooks.dart:186:13)
           #7      _ChannelCallbackRecord.invoke (dart:ui/channel_buffers.dart:42:5)
           #8      _Channel.push (dart:ui/channel_buffers.dart:132:31)
           #9      ChannelBuffers.push (dart:ui/channel_buffers.dart:329:17)
           #10     PlatformDispatcher._dispatchPlatformMessage (dart:ui/platform_dispatcher.dart:599:22)
           #11     _dispatchPlatformMessage (dart:ui/hooks.dart:89:31)
           (elided 2 frames from class _AssertionError)
           ════════════════════════════════════════════════════════════════════════════════════════════════════
[+7670 ms] Service protocol connection closed.
[        ] Lost connection to device.
[        ] DevFS: Deleting filesystem on the device (file:///tmp/0byteXFIJBH/0byte/)
[   +1 ms] (app_0byte:371200): GLib-GObject-WARNING **: 09:56:00.132: ../../../gobject/gsignal.c:2731: instance '0x20681b0' has no handler with id '113'
[ +252 ms] Ignored error while cleaning up DevFS: TimeoutException after 0:00:00.250000: Future not completed
[   +5 ms] "flutter run" took 25,542ms.
[  +94 ms] ensureAnalyticsSent: 89ms
[   +1 ms] Running shutdown hooks
[        ] Shutdown hooks complete
[        ] exiting with code 0

flutter doctor -v
[✓] Flutter (Channel stable, 3.3.5, on Ubuntu 22.04.1 LTS 5.15.0-52-generic, locale en_US.UTF-8)
    • Flutter version 3.3.5 on channel stable at /home/gruvw/snap/flutter/common/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision d9111f6402 (2 weeks ago), 2022-10-19 12:27:13 -0700
    • Engine revision 3ad69d7be3
    • Dart version 2.18.2
    • DevTools version 2.15.0

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
    • Android SDK at /home/gruvw/Android/Sdk
    • Platform android-33, build-tools 33.0.0
    • ANDROID_HOME = /home/gruvw/Android/Sdk
    • Java binary at: /snap/android-studio/current/android-studio/jre/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)
    • All Android licenses accepted.

[✓] Chrome - develop for the web
    • CHROME_EXECUTABLE = /opt/brave.com/brave/brave-browser

[✓] Linux toolchain - develop for Linux desktop
    • clang version 10.0.0-4ubuntu1
    • cmake version 3.16.3
    • ninja version 1.10.0
    • pkg-config version 0.29.1

[✓] Android Studio (version 2021.2)
    • Android Studio at /snap/android-studio/123/android-studio
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)

[✓] Android Studio
    • Android Studio at /snap/android-studio/current/android-studio
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • android-studio-dir = /snap/android-studio/current/android-studio
    • Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)

[✓] VS Code (version 1.72.2)
    • VS Code at /usr/share/code
    • Flutter extension version 3.52.0

[✓] Connected device (2 available)
    • Linux (desktop) • linux  • linux-x64      • Ubuntu 22.04.1 LTS 5.15.0-52-generic
    • Chrome (web)    • chrome • web-javascript • Brave Browser <IP_ADDRESS>

[✓] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

Environment

OS: Ubuntu 22.04.1 LTS x86_64
Dart: Dart SDK version: 2.18.2 (stable)
Flutter: Flutter 3.3.5 • channel stable

Triage report
I can reproduce this issue with Ubuntu 22.04 on Master (3.5.0-12.0.pre.94). I remaped my Caps Lock by following these steps.

Error logs
** (issue_114591:62623): WARNING **: 20:00:24.396: Unable to retrieve framework response: Message is not valid JSON

══╡ EXCEPTION CAUGHT BY SERVICES LIBRARY ╞══════════════════════════════════════════════════════════
The following assertion was thrown during a platform message callback:
Attempted to send a key down event when no keys are in keysPressed. This state can occur if the key
event being sent doesn't properly set its modifier flags. This was the event:
RawKeyDownEvent#90574(logicalKey: LogicalKeyboardKey#147d9(keyId: "0x100000008", keyLabel:
"Backspace", debugName: "Backspace"), physicalKey: PhysicalKeyboardKey#11708(usbHidUsage:
"0x00070039", debugName: "Caps Lock"), repeat: false) and its data:
RawKeyEventDataLinux#6ab1f(toolkit: GTK, unicodeScalarValues: 8, scanCode: 66, keyCode: 65288,
modifiers: 0, isDown: true)
'package:flutter/src/services/raw_keyboard.dart':
Failed assertion: line 683 pos 7: 'event is! RawKeyDownEvent || _keysPressed.isNotEmpty'

Either the assertion indicates an error in the framework itself, or we should provide substantially
more information in this error message to help you determine and fix the underlying cause.
In either case, please report this assertion by filing a bug on GitHub:
  https://github.com/flutter/flutter/issues/new?template=2_bug.md

When the exception was thrown, this was the stack:
#2      RawKeyboard.handleRawKeyEvent (package:flutter/src/services/raw_keyboard.dart:683:7)
#3      KeyEventManager.handleRawKeyMessage (package:flutter/src/services/hardware_keyboard.dart:951:30)
#4      BasicMessageChannel.setMessageHandler.<anonymous closure> (package:flutter/src/services/platform_channel.dart:214:49)
#5      _DefaultBinaryMessenger.setMessageHandler.<anonymous closure> (package:flutter/src/services/binding.dart:392:35)
#6      _invoke2 (dart:ui/hooks.dart:183:13)
#7      _ChannelCallbackRecord.invoke (dart:ui/channel_buffers.dart:40:5)
#8      _Channel.push (dart:ui/channel_buffers.dart:130:31)
#9      ChannelBuffers.push (dart:ui/channel_buffers.dart:326:17)
#10     PlatformDispatcher._dispatchPlatformMessage (dart:ui/platform_dispatcher.dart:664:22)
#11     _dispatchPlatformMessage (dart:ui/hooks.dart:86:31)
(elided 2 frames from class _AssertionError)
════════════════════════════════════════════════════════════════════════════════════════════════════

CC @Renzo-Olivares

@justinmc @Renzo-Olivares
I worked on several keyboard issues in the previous weeks (and Linux is my primary platform), I can work on this issue if you don't mind.

@bleroux I don't mind handing this issue off to you. And can definitely give you a review/help if necessary. Thank you :)

Thanks @bleroux!


Fix typo bug in heightmap shape

Seems relevant for 3.x too.

Thanks!

Cherry-picked for 3.6

Cherry-picked for 3.5.2


Add maven in Project domain

it's following this https://github.com/pascalgrimaud/jhipster-forge/pull/181

Thanks @hdurix : but I don't know if it's the correct way, in our architecture, as doing this will result to:

application/MavenApplicationService (publish)

primary/BuildToolAddedListener (listener)

application/BuildToolApplicationService

domain/BuildToolService

domain/BuildToolDomainService

domain/MavenService

Not relevant any more as a lot of code has changed since this.
So closing this


Job template: input/parameter only retrieve name/type from DB?

adding a job template to the backend stores options for input and default for parameter
when loading a job template from the backend, options and parameter are empty
the serializers for input/parameter in ufdl/core_app/serialisers/jobs/_JobTemplateSerialiser.py only list name/type - is that the issue?

Yes that is the issue. I'll fix it now.

Implemented in commit 1c735879047983f84083c451fe8f563232007575


Flash power-up in boot_stage2

User gmx suggested on the forum, that powering flash down can further lower power consumption. And it works indeed - about 10 uA (typically). Using powman with BOOT0..3 registers set to 0, as I understand it boots back from flash, especially when sleeping in P1.7 with no SRAM retention, like in powman example here. Powered down flash responds to 0xAB instruction only, and any boot2 doesn't seem to revive it that way.
So my request here is, that maybe it will be useful to have conditional (ex. using SCRATCH0..7 register value) sending of an 0xAB instruction in case, flash was powered down before.

Actually it was easier done, than said. Just reused:
    // Send revive command, discard RX
    movs r0, #CMD_REVIVE
    str r0, [r3, #QMI_DIRECT_TX_OFFSET]
    bl wait_qmi_ready
    ldr r0, [r3, #QMI_DIRECT_RX_OFFSET]

as the fist command (for ARM) and it works both for cold start and restart from sleep at powman. I think I can make a PR out of it.


Loosen babel-plugin-jest-hoist babel/istanbul package deps

🚀 Feature Proposal
Our yarn.lock shows multiple babel plugin versions due to:
<EMAIL_ADDRESS>  version "26.2.0"
  dependencies:
    "@babel/template" "^7.3.3"
    "@babel/types" "^7.3.3"
    "@types/babel__core" "^7.0.0"
    "@types/babel__traverse" "^7.0.6"

I was wondering if it would make sense to loosen these deps to something that could help prevent multiple package versions in certain codebases, maybe:
<EMAIL_ADDRESS>  version "26.2.0"
  dependencies:
    "@babel/template" "^7.3"
    "@babel/types" "^7.3"
    "@types/babel__core" "^7.0"
    "@types/babel__traverse" ">=7.0.6 < 8"

bonus looks like jest packages have x2 versions of istanbul-lib-instrument:
"<EMAIL_ADDRESS>    istanbul-lib-instrument "^4.0.3"
"<EMAIL_ADDRESS>    babel-plugin-istanbul "^6.0.0" ->
      istanbul-lib-instrument "^4.0.0"

which means by adding jest, babel core looks like:
"<EMAIL_ADDRESS>"<EMAIL_ADDRESS>"<EMAIL_ADDRESS>"<EMAIL_ADDRESS>
Motivation
I think its a safe enough comprimise, especially since babel is so good about their semvar, I would feel safe with allowing minor versions as a tradeoff to deduping in many projects

That won't actually change the semver ranges (play with it on https://semver.npmjs.com/). You can use https://github.com/atlassian/yarn-deduplicate/ for yarn v1 or wait for https://github.com/yarnpkg/berry/pull/1558 for yarn v2

yeah we are using v1 resolutions currently.
Really just wanted to see if there was an obvious oh we should update that, thats all
Regardless thx for being such a stellar open source lib + contributor!


TuneIn Radio

When I ask for a radio station such as "KEXP on TuneIn", it repeats error phrase twice "KEXP on TuneIn radio is not available right now".  Pretty sure it wants to re-direct based on the link returned from TuneIn.  Using VLC as a client doesn't have this problem, as it manages the re-direct.
2017-09-12 22:54:29.060 [  2] E MediaPlayer:handleBusMessageError:source=decoder,error=Your GStreamer installation is missing a plug-in.,debug=gsturidecodebin.c(1006)\: no_more_pads_full ()\: /GstPipeline\:audio-pipeline/GstURIDecodeBin\:decoder\:
no suitable plugins found\:
gstdecodebin2.c(4565)\: gst_decode_bin_expose ()\: /GstPipeline\:audio-pipeline/GstURIDecodeBin\:decoder/GstDecodeBin\:decodebin10\:
no suitable plugins found\:
Missing decoder\: text/uri-list (text/uri-list)

2017-09-12 22:54:29.060 [  2] 0 MediaPlayer:callingOnPlaybackError:error=Your GStreamer installation is missing a plug-in.
2017-09-12 22:54:29.060 [  2] E MediaPlayer:handleBusMessageError:source=queue2-10,error=Internal data flow error.,debug=gstqueue2.c(3010)\: gst_queue2_loop ()\: /GstPipeline\:audio-pipeline/GstURIDecodeBin\:decoder/GstQueue2\:queue2-10\:
streaming task paused\, reason not-linked (-1)
2017-09-12 22:54:29.060 [  2] 0 MediaPlayer:callingOnPlaybackError:error=Internal data flow error.

Hi @INRIX-joel-winarske,
It seems to be an issue with parsing the URL (containing a playlist) returned from TuneIn. In the latest release (1.0.2), we don't support TuneIn yet, only iHeartRadio. The reason for this is that we integrated with a 3rd party library, Totem Playlist Parser, to extract URLs, and this library doesn't doesn't work on all platforms and has been a bit shaky for us. That being said, we do have support for using this library. See PlaylistParser/CMakeLists.txt for more info. You'll need to define the TOTEM_PLPARSER variable in your cmake command and link it in.
In our upcoming release, we plan on replacing this with our own PlaylistParser with capabilities of parsing remote URLs containing multiple URLs. I've testing the behavior you just described above and I've been able to play the station as expected. Hope that clarifies things.
Thanks,
Sanjay

Hi @sanjayrd
Building with -DTOTEM_PLPARSER=ON addressed the problem.
What's the timeline for the updated PlaylistParser?  Also what are the other planned fixes/features?
Thanks,
Joel

@INRIX-joel-winarske,
The timeline is approximately 4 weeks. The major feature will be the PlaylistParser, which should help out with a lot of the music provider issues we've been seeing. Other features will be bug fixes and minor improvements.
Thanks,
Sanjay


Integration with Geoconnex reference collections

HydroShare aims to make Data FAIR (Findable, Accessible, Interoperable and reusable), The Findability depends on how well data is attributed with meaningful metadata. Currently the subject field is an open text field and the geography picker is limited to simple features like a point, line or bounding box. It has been a goal of the HS team to increase the quality of the metadata by providing a more curated set of keywords for a user to choose from. The IoW develops Geoconnex which is a system for connecting water data from different data providers via geographic location. It provides Permanent Identifiers (PIDs) for Hydrologic features and is accessible via standardized API. The result of the proposed work would be to develop a connection between the 2 systems where HydroShare enables a user to attribute resources with identifiers provided from the Collection of features hosted on https://reference.geoconnex.us/collections which includes e.g. HU2-10, Aquifers and tribal lands, it follows the same idea as the ControlledVocabularies in HIS, The system would be extensible as new collections become available as  it will take advantage of the standardized linked data formatting of the API.

This is a cool idea. I'm assuming this would be a new metadata element that we would need to sort through how to encode in the metadata and present on the landing page rather than overloading keywords or spatial reference, which, as you point out are not well suited for storing this type of specific feature information.

@horsburgh I initially had thought we can reuse the place/area name field to keep changes to the data model at a minimum, but i'm open to a new metadata element if that is required. It would also depend on how we want to enable search for this as this enables better spatial discovery, also tagging @dtarb here as discussed.

@martinseul  @horsburgh I am happy for you guys to figure this out, especially if another project is going to pay for this.  Here are some considerations

Should this be metadata at the resource level or the aggregation level.  It may be most sensibly associated with aggregations that are geospatial (rasters, features, multidimensional)
Should this be part of the spatial coverage element or separate.  Place/Area name is the only part of current spatial coverage that can be text and I do not think this fits here.  Some sort of spatial coverage relationship "is associated with geoconnection element type huc04, huc04 identifier" may be good.

Are there examples of how other systems are referencing geoconnex that we could follow.

@dtarb regarding examples of other systems that use Geoconnex, I found this list of publications:
https://github.com/internetofwater/geoconnex.us#geoconnexus-related-presentations-and-publications
which had me hopeful that maybe one of the other Internet of Water Hubs might be using Geoconnex. But I wasn't able to find any actual implementation.
Looks like @Castronova has contributed to the Geoconnex repo so maybe he knows of some other entity that is using it?
I like the idea of a "spatial coverage relationship" metadata element on geospatial aggregations...

@devincowan there is the selfie project that Tony was involved in https://opengeospatial.github.io/SELFIE/demo/internet_of_water.html, Also adding a geographic term is especially useful for non geographic resources as many of our resources don't have geographic extent but still relate to a geographic unit so I would think the metadata term would be not just apply to geospatial aggregation but for any resource and also on the file level.

Thanks @martinseul these use cases provide some good examples:
https://docs.ogc.org/per/20-067.html#DomainUseCases
And I see what you're saying about adding a geoconnex term even for resources that lack geographic extent, thanks

@devincowan Take a look at this basic website I create as part of the SELFIE project. https://selfie.cuahsi.org/

If there is a way to use Geoconnex to add a place name to the geographic coverage element that could be useful. Alternatively, multiple place names could also be added as keywords.
@dtarb - makes a good point about whether these associations should be at the Resource or the Aggregation level. We should sort that out.
But, I would suggest that we avoid overloading the Keywords and Spatial Coverage place name elements with different types of information. If the goal is to link to actual geographic features via identifiers (e.g., URLs), then those identifiers wouldn't belong in the place name of the geographic coverage or he keyword metadata we have now.
I just looked through the Dublin Core metadata elements that we use for our metadata schema again. Of the Dublin Core elements, I think the "relation" element is the most relevant because these Geoconnex features are essentially resources that can be related to the HydroShare resource (and/or aggregation).

I don't think there is a place in Geoconnex for geographic names but there is https://www.usgs.gov/faqs/what-geographic-names-information-system-gnis as well as google place API or https://www.geonames.org/ that would be options.

Geoconnex API issue:
https://github.com/internetofwater/geoconnex.us/issues/156
has been resolved, so I think we are good to proceed with this.
I'm staging a prototype combobox here:
https://new-riverdev.hydroshare.org/
it only shows up on resource landing page when in edit mode.
For now I've just added this as a single element at the resource level--you will see it below the Spatial Coverage section:

@martinseul @dtarb @horsburgh if you like this approach for UI, we can finalize the decision of where this element should live (seems we are leaning toward BOTH the resource level within the spatial coverage, and at the aggregation/file level). Then I can start on the backend work, adding these new references as relations within our HS metadata

The screen shot is cut off, so I can't see how the user would interact with the landing page or how the information would be displayed. How does a user select Geoconnex features to add to their resource? Again - I think this information belongs under related resources. It isn't the same thing as spatial coverage. We could have a section on the landing page called "Related Geospatial Features" or something like that. These features are real-world objects that are identified with permanent identifiers that I assume can be URL encoded and resolve to something that is live on the Internet. As such, they are related resources because they are themselves resources on the Internet.
Also - what is the ultimate purpose of these linkages? The original issue posting says that we want to enable users to link Geoconnex features to a Resource. Will these linkages/resources participate in any sort of data discovery? In other words - what is the full functionality that needs to be implemented as part of this issue?

@horsburgh thanks for the feedback! Here is a video of some interactions with the element:
https://user-images.githubusercontent.com/17934193/164724579-ca0f470c-2d74-43e5-a1e3-b0f592e89dcc.mov
You are correct that we are talking about "related geo features" and we are referencing them by the Geoconnex URI. I indicated those URIs and how they resolve in the video.
Really good question about the ultimate purpose. My feeling is that we should indeed include this in Discover. @martinseul is that within our scope?
(I also think that it would be neat to mint a Geoconnex identifier for each of our published resources in HS/HIS but that is likely beyond our scope. At least adding a "Related Geospatial Features" item within our data model would allow users to start adding those links to the metadata now. And if we ever got into the business of minting Geoconnex DOIs for published resources, the "related" Dois would already be in the system)

related to #3874

@horsburgh thanks for the SchemaOrg info!
A Thing can't be About just any generic Thing.
Rather:
A Thing can only be About a Thing this is an Event, CreativeWork, or CommunicateAction
Our HS Resources are Datasets which are CreativeWorks.
So I would agree that our CompositeResources could be About items in the Geoconnex Reference Collection.
Seems like we could include these new Geoconnex references in our schema.org info using either About or Citation...it isn't clear to me which is preferable, though it looks like the Thing.About property is more general because it can contain any Thing whereas the Citation is supposed to reference only CreativeWorks

@devincowan - I would prefer the "about" property rather than "citation" because it doesn't conflate GeoConnex features with other related resources like papers. Semantically, "about" makes more sense than "citation" too - the resource provides some information "about" the GeoConnex feature.
I think this statement isn't quite right:

A Thing can only be About a Thing that is an Event, CreativeWork, or CommunicateAction

Instead it should be:

Instances of a Thing may appear as a value for the about property on type CreativeWork

In other words - a GeoConnex feature (Thing) may appear as a value for the "about" property of a HydroShare resource (which is a CreativeWork/Dataset).
I'm thinking something like this:
{
    "@context": {
        "@vocab":"https://schema.org/"
    },
    "@type": "Dataset",
    "@id": "https://doi.org/10.4211/hs.xxxxxxxxxxxxxxxxxx#schemaorg",
    "additionalType": "http://www.hydroshare.org/terms/CompositeResource",
    "name": "Awesome Resource Title",
    "description": "Awesome resource Abstract",
    "keywords": ["hydrology"],
    "creativeWorkStatus": "Published",
    "inLanguage": "en-US",
    "identifier": [
      {
        "@id": "https://doi.org/10.4211/hs.xxxxxxxxxxxxxxxxxx",
        "@type": "PropertyValue",
        "propertyID": "https://registry.identifiers.org/registry/doi",
        "url": "https://doi.org/10.4211/hs.xxxxxxxxxxxxxxxxxx",
        "value": "doi:10.4211/hs.xxxxxxxxxxxxxxxxxx"
      },
      "https://www.hydroshare.org/resource/xxxxxxxxxxxxxxxxxx"
    ],
    "about": [
      {
        "@id": "https://geoconnex.us/ref/states/49",
        "@type": "Place",
        "name": "Utah",
        "url": "https://geoconnex.us/ref/states/49"
      },
      {
        "@id": "https://geoconnex.us/ref/hu02/16",
        "@type": "Place",
        "name": "Great Basin Region",
        "url": "https://geoconnex.us/ref/hu02/16"
      }
    ]
}

It's unclear to me whether "Place" is the right type for all GeoConnex features because there is also "LandForm", "BodyOfWater" etc.

@horsburgh thanks for the clarity and correction--that makes sense. Yes it would be nice to add more nuance than a generic place but I'm not sure how difficult it will be to coerce the Geoconnex types into corresponding Schema.org Places...

We've recently become much more flexible in our JSON-LD generation and can add additional types to these reference features. For most hydrologic concepts we'd like to begin moving over to HY_features defintions. For census/administrative geographies I'm open to other things, maybe schema:AdminstrativeArea, although that won't work for necessarily for all of them.

I would look at these contexts as a guide. https://opengeospatial.github.io/ELFIE/contexts/elfie-2/
If the thing we are documenting (a hydroshare item) is a dataset, then we are talking about creating landing/data content for a dataset in the context of figure 2 here Looking above -- the NIR in this case is a digital object identifier -- building a graph of information associated to that is great.
So we might say things like: This digital object is about that river (as @horsburgh rightly has up above). But we probably wouldn't say this dataset is upstream of that river (so hydrologic concepts directly in the linked data about a DOI is a little odd).
Another point of reference would be the SELFIE landing content section.. In this case, since we are "@ID": "{a DOI}"  we are "in-band" and the way @horsburgh modeled the about section seems reasonable.
A final thought -- if it's useful to make a disctinction between landing-content (the json-ld graph) and data-content (a format the is not necessarily an extension of the graph), that could be pointed to in a "url:" "https://hydroshare-data-access-url" which may also include a mime-type and other information about that particular representation of the digital object.
I'm super stoked you all are pursuing this. I'll make sure I have this issue watched and try to keep up.

Initial feedback about the implementation in the landing page shown in the demo today:

We now have a Google Map element for spatial coverage and a leaflet map for the geoconnex features. Do we need to be using both on the same page?
The section uses a lot of vertical real estate on the page, which means more vertical scrolling. Could we condense it so that the list of features shows up on the left and the map on the right? It could show up top/bottom when the screen gets really narrow?
Related to the last point, rather than repeating for each added feature "The content of this resource is related to:" and then then name of the feature, and then the URL for the feature, could you just provide a single list of the names of the features where the name of the feature is also hyperlinked? This would make it easier to have a list of features on the left and a map on the right (similar to the layout for spatial coverage metadata). Then, you would just need a single label under the section heading that says: "The content in this HydroShare resource is related to the following geospatial features:"
When I add a GeoConnex feature, it adds the "Related Geospatial Features" section in view mode. But, it also adds the "Related Resources" header, even though I do not have any related resources. Those two are somehow tied together, but shouldn't be in that way.
For help related stuff, you could put a an information icon as has been done with other metadata elements to alert users what this feature is/does and link it to help content.
Finally - yes, we need some sort of widget to allow people to select GeoConnex features. That widget could/should be tied to the spatial coverage of the resource (if it exists) and could/should suggest features that overlap/intersect that coverage.

thanks @dblodgett-usgs and @ksonda for your comments/suggestions--very exciting to be collaborating on this.
Some of these will have to be implemented as part of a "phase 2" but I've attempted to address items that fall within current scope, as well as recommendations from @horsburgh in my next draft.
Deployed here it's a dev machine so you won't be able to create an account I think--DM me if you want to login and take a look...

Mae my day with this one! So so happy to see this happening.

Wow this is awesome.

Brief progress update:
I've implemented query of Geoconnex collection items based on Hydroshare Resource spatial extent--this finds Geoconnex items that overlap with our point/box coverage and populates both a selection list and a map. Selected Geoconnex items populate HS metadata and are displayed on the resource page.
Next step: prototyping different proposed mechanisms for HS users to select spatially related items.

I've replaced our Google Map on the resource landing page with a Leaflet version, to facilitate Geoconnex relation selection within the same map as spatial extent selection (if we decide to go this route). Other ideas include:
Modal with a semi-guided set of steps to find and select relations
Selection just using a list (and not populating a map) of spatially proximate potential relations

I'm hope to have prototypes for these ready in the next couple weeks

This is great. LMK if you run into performance issues on any of the reference features, I can look into it.

Picking this work back up -- I am proceeding with the following:

Turn subsurface features / aquifers off by default (opt in via selection)
Ask user if they want to query for related items only after they have added spatial extent (but still allowing for addition of geospatial relations even to resources that don’t themselves have spatial extent)
Instead of a modal, using a toggle section/hidden inline page section

Better UX = nonblocking/forcing but also doesn’t increase default vertical scrolling
Better for mobile/small format
Related spatial items section will be directly below the current “Coverage” section

Instead of a step-by-step guided “wizard” for finding related items, use tooltip hints and links to help pages for more “how to” consistent with other sections on the Resource Landing Page

Potentially use v-tabs if applicable, though likely interactions are minimal enough that a single view is best

Generalize caching and request cycle so that it can handle additional collections in the future
Modify Leaflet implementation so that the buttons etc are closer to current (v1.57.1) Google map placement and style

@ksonda: this work not only links Hydroshare resources to related Geoconnex items, it also adds geoconnex reference items into the Schema.org metadata embedded in each Hydroshare resource. As discussed above in this issue, right now we add a related Geoconnex item as a Schema.org Place with @id and url pointing at the geoconnex URI. I would love to get more info, for example getting Geoconnex item names into our schema.org as names and other basic info. However, seems like these properties aren't consistent across Geoconnex Collections.
Example:
HU2 Collection items have a NAME
whereas
National AQ items have an AQ_NAME
considering that new collections might (hopefully!?) be added in the future, mapping these inconsistent fields into our metadata might be burdensome.
Can you provide any guidance? Specifically, can we anticipate that there will be any central curation of collection properties in the future, or will it depend on the entity submitting to the collection? Thanks!

@ksonda that makes sense, thanks! I will explore to what extent we are comfortable simply porting the compacted json-ld directly into our resource metadata.

Alternatively, we'll eventually have a sparql endpoint that you can query ids for schema.org/name or any other rdf predicate

@ksonda sparql endpoint will be a great service--we will look forward to that! @martinseul and I are wondering what sort of timeline you have for that?
Also, does IOW have plans to support spatial queries for items in the Goeconnex collections? I ask because right now our Hydroshare service pulls all of the relevant geometries in order to perform queries locally, but we would ideally just query your openapi with our spatial bounds/parameters

sparql should be EOY. The collections is just an OGC-API features endpoint. full cql filters have not been implemented, but you can do bbox query like this: http://reference.geoconnex.us/collections/mainstems/items?bbox=-95.426559,39.646940,-94.118500,40.104862

Beautiful!
thank you, I had overlooked the bbox parameter -- this will really help us on some of the larger collections

@ksonda does IOW have a geoserver/mapping service for the items in the Geoconnex service? We are trying to mitigate performance issues loading geoms from the API (bbox query param will help but I think we need to go deeper). Other than fetching headers and checking Content-Length is there a way that we can prioritize based on geometry size?

We're using pygeoapi, mostly out of need for JSON-LD templating. These resources are actually supposed to be crawled individually to put in a knowledge graph rather than be queried en masse like this. I suppose I can see about putting up a geoserver or an esri service link. Is the issue here fundamentally about  speed or transaction size?

Thanks @ksonda makes sense--we have a plan to revise avoiding mass query. Issue seems to be primarily transaction size for some of the larger (higher res) geometries.

Hmm is it a certain collection. These features should (not that they are...and I can change them if necessary) be lower res for this sort of thing. I'm imagining census places or the pws. The hucs I thought @dblodgett-usgs was using simplified geoms.

when I checked before, it was surprisingly "States" that were the worst offenders. and yes, PWS. I'll check again...

I'll put a ticket in to make sure the census units are low res

Thanks @ksonda!
I also created an unrelated ticket:
https://github.com/internetofwater/geoconnex.us/issues/170

drafted Help Documentation:
https://pages.hydroshare.org/admin/pages/richtextpage/194/change/


Overlay will not even load

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
Downloaded the MHFZ_OverlaySetup.exe File
Ran it as administrator
Setup was completed
Launched MHFZ, Logged In, and entered Mezaporta
Launched the MHFZ_Overlay
Asks me if "I wish to run the application?" Selected "Yes"
Nothing Happens after. No overlay or records of the application even starting were present.
Assumed something wasn't installed properly, Checked The AppData/Local Folders. (Found the file directory)
Looked for a possible crash report (None were available)
Decided to uninstall and try a previous version of the overlay.
Same results as previous.
How often does the bug occur?
Always
What version of the program are you using?
I'm using...
The MHFZ Overlay (0.33.0)
.NET Desktop Runtime 6.0 x64 (6.0.26)
.NET Desktop Runtime 6.0 x86 (6.0.26)
MHFZ Launcher 2.016
I hope this helps or you can find out what I've done wrong.. thanks!

Do you get a black screen when loading the overlay? See #61 for similar issue.


bug(cloud-sync): After latest update, Discord on iOS crashed

Check all the boxes below

[X] I have checked that this bug hasn't already been reported

Discord username
@dor4a
Detailed Info
After latest update, CloudSync crashed Discord each time I opened Discord, until I disable it by turning off the internet
Phone: iPhone SE 2022, iOS 16.4
Discord version: 197.0 (50096)
Steps to Reproduce

Enable CloudSync
Discord crashed

Crash Info
https://pastebin.com/raw/nuACtUXz
^ the .ips crash log
Bug Screenshot
No response
System Info
Device: iPhone SE 2022
Manufacturer: Apple(?)
Brand: Apple(?)
OS: iOS
Version: 16.4
Discord Branch: Beta
Discord Version: 197.0
Discord Build: 50096
Vendetta Version: d539e5a
React Version: 18.2.0
Hermes Bytecode: 94

asked @acquitelol and apparently vendetta's crashing on ios a lot lately, you should just disable cloud sync for now

Reinstalled my Discord client and this happened, also waiting for a fix :eyes:

alr this is now fixed so ima close this


Add diasibility bias related terms

This issue is to fill out disability_bias.md
It should follow the same format as the other files
List should include at least all the terms listed here:
https://en.wikipedia.org/wiki/List_of_disability-related_terms_with_negative_connotations

Hi @nightwolf3 does this ticket look good for you? If so I'll create a new bounty for the remaining $200 for you.
If the work looks good, I'd be happy to put up to another $500 to complete the other files.

@pdlla Hello, is it opened on gitcoin?
"This issue is to fill out disability_bias.md
It should follow the same format as the other files"
is that the ticket you are referring to? because after last time I got confused I guess so I wanna know everything I can before starting. thank you in advance

@nightwolf3  I'm actually cancelling this project for now since I don't really have time to manage it (which was more work than I expected). Sorry for the confusion etc.

@nightwolf3 I'm actually cancelling this project for now since I don't really have time to manage it (which was more work than I expected). Sorry for the confusion etc.

alright it's okay. hoping to work on your next bounty and thank you


默认触发模式：将mode的默认值设置为['click']，以明确默认的触发事件。

支持多种触发模式：mode属性现在支持SingleOrMultiple类型，允许配置单个或多个触发模式（如'click'、'mousedown'、'mouseup'）。
load方法的改进：在load方法中，如果配置数据中没有提供mode，则默认设置为['click']，以确保总是有一个明确的触发模式。
Did you build the project before submitting the PR?

[ ] Yes
[x] No

支持多种触发模式：mode属性现在支持SingleOrMultiple类型，允许配置单个或多个触发模式（如'click'、'mousedown'、'mouseup'）。
load方法的改进：在load方法中，如果配置数据中没有提供mode，则默认设置为['click']，以确保总是有一个明确的触发模式。
Did you build the project before submitting the PR?

[ ]  Yes
[x]  No

English please.

Apart from the missing description in English, changes are not acceptable because it's by design that every feature is not enabled by default, and all values are as empty as possible.

I improved my code again,and following is my Code Modification Explanation:
Default Activation:
The enable property is set to true by default, indicating that the click event handler is enabled by default.
Non-empty Default Value:
The mode property is set to ['click'] by default, signifying that there is at least one trigger mode active from the start.
Load Method:
Within the load method, if the configuration data does not provide a mode, it defaults to ['click'], ensuring that the mode property is never empty.
These changes align the code with the requirement that every feature is enabled by default and that all values are non-empty. If you have any further requests or need additional modifications, please let me know. The new brunch is being submitted now,because of the wifi situation, it may appear here later

 * @param data - Optional configuration data for the click event.

 * @param data - Optional configuration data for the click event.

 * @param data - Optional configuration data for the click event.

There may be something wrong with my Vscode, so I Submit the code here, later the branch may be undated and u can view it more directly


dns/bind: add StevenBlack blacklist

Most wished DNSBL, finally closes #1033
No bump needed as 1.4 not yet released.

Merged, thanks!


[Bug] Year does not affect the progress in day-custom

The year does not seem to affect the progress, for example, with this code
```progressbar
kind: day-custom
name: Schuljahr
min: 2024-08-05
max: 2024-08-28
```
```progressbar
kind: day-custom
name: Schuljahr
min: 2024-08-05
max: 2025-08-28
```

both progress bars show the same progression although the second time span is an year longer

+1, Can confirm.
I was confused when only changing the year.
id: test2
kind: day-custom
min: 2024-01-08
max: 2029-01-08


Ultra large LED bowl doesn't seem to work with recent version

I was playing with the large LED bowl and it doesn't seem to turn on with more recent versions of the software. We definitely had to go backward to an older version.
I think maybe it has something to do with the super large buffer we enabled at some point.

Looking into this this week!

Latest version seems to fix this... let me know if you have time to test. Just an issue with memory management, these devices have trouble with >1300 LEDs without reasonable allocation practices. Dynamic allocation seems to be a bad idea in general...

I don't have any more of these devices to test on so I'm just using the center board :D

Yeah, memory is always an issue I hate dealing with.
You have to throw away all your "clean code rules" when working with these
tiny processors.
On Tue, Feb 26, 2019 at 2:24 AM Zack Phillips<EMAIL_ADDRESS>wrote:

I don't have any more of these devices to test on so I'm just using the
center board :D
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/zfphil/illuminate/issues/21#issuecomment-467326090,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAFfmIeXHmY_PdKyDwwFF5X-2BJzh4puks5vROEpgaJpZM4ZQuFO
.


fix: instagram image fetch

This one should work. See https://www.instagram.com/iamavoix/?__a=1 as an example.
Related #117

nope https://unavatar.now.sh/instagram/teslahunt
the issue isn't the code, is the way Instagram doesn't want to be reachable by servers


rendering bug on small spans in large spans

See #317. This contributes a test for #317  and then fixes the bug :)
Closes #317
The bad screenshot from #317

now becomes this with the proposed changes:

Note that there were actually two subtle bugs. One was the double arrow in the gutter problem, which also occurred when rendering without ansi escape codes. However, this line
https://github.com/zkat/miette/blob/a8b4ae012aa0cf03b53a18f013c2b3f76c5040e7/src/handlers/graphical.rs#L611
Also did not work when the gutter contains ansi escape codes. It extends to the width variable, but when the string contains ansi codes it does not actually add any spaces since it thinks the escape codes have width as well. They of course do not, so the output doesn't look right. Unfortunately this is quite hard to make tests for.

Can you fix the conflicts here?

@zkat there ya go! Thanks for having started such an awesome project :sparkling_heart:


nri-bundle: Add Kubernetes 1.22 support

⚠ Breaking changes ⚠
This PR introduces Kubernetes 1.22.x support for the New Relic Kuberentes solution, and removes support for kubernetes 1.15.x and below.
Users may still use previous versions of the nri-bundle and other charts to instrument their clusters, and limited support will be offered for them. Development for said older versions is considered stopped and New Relic does guarantee feature parity or bugfixes (security or otherwise) for those older versions.
Is this a new chart
No
What this PR does / why we need it:
Bumps versions in individual charts and the bundle to point to the latest released versions of all Kubernetes components, which include support for Kubernetes 1.22.
Additionally, some changes to the charts themselves are also included to make them compatible with said version.
Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] Chart Version bumped

Includes changes from #468

Same nri-bundle version of https://github.com/newrelic/helm-charts/pull/525/files

Same nri-bundle version of #525

@paologallinaharbur Yes, this PR supersedes #525 and the latter will be closed after merging this.


New header responsive mobile

Close #416

The new mobile header according to the new designs

LiveURL: https://smartfaq-416-new-header-responsive-mobile.surge.sh

I rebased + added fix for search bar issue + I found that the back button is hard to click so I fixed that as well. Seems fine to me now :-)

I believe we have to either clean up the commits and their messages (git rebase -i) or we have to squash this. I don't know which one is better.

Conflicts resolved @jalbertsr

There is the problem that faqs are not loading the correct faqs categories for the booking status, until you press(and load) the booking.
This error apeared in sentry while testing: https://sentry.skypicker.com/kiwicom/smartfaqstaging/issues/1289237/
There should be only one close button (X), also the "Help" header should be smaller

In landscape there should be no "Help" header

Thanks for the review! Working on the fix

@kantord can you maybe use the strategy you commented with me of using strings instead of booleans? the same we did for ExtraInfoState context, I think with this solution we'll get rid of these sentry errors https://sentry.skypicker.com/kiwicom/smartfaqstaging/issues/1362002/?query=is:unresolved

@jalbertsr I can, but it'd be great to find a way to consistently reproduce them before I do the fix. Otherwise, how will I know it worked :-)


Fixing issue 99, adding b3 screw to directions

Fixing issue 99, adding reference to B3 in directions for "D-Clamping Hub Attachment"

to the channel using screws B3 from the top, and B1 from the bottom, as shown in Figure 7.

Awesome Kevin, thanks for adding that clarity and reworking the documents!


esp32 c3 wroom 02  run to at commands with doclight  (IDFGH-13240)

Answers checklist.

[X] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

IDF version.
ESP32-C3-MINI-1-AT-V<IP_ADDRESS>
Operating System used.
Windows
How did you build your project?
Command line with Make
If you are using Windows, please specify command line type.
CMD
What is the expected behavior?
I want to run the esp32c3 wroom 02 card with at commands with the docklight application, but I get the error "invalid header 0xffffff". can you help?
What is the actual behavior?
I want to run the esp32c3 wroom 02 card with at commands with the docklight application. in the simplest form, I want to get the OK command when I run the AT command.
Steps to reproduce.

Chip is ESP32-C3 (QFN32) (revision v0.4)
Features: WiFi, BLE
Crystal is 40MHz
MAC: 58:cf:79:27:64:e4
Uploading stub...
Running stub...
Stub running...
Configuring flash size...
Flash will be erased from 0x00001000 to 0x00005fff...
Flash will be erased from 0x00008000 to 0x00008fff...
Flash will be erased from 0x00010000 to 0x001b0fff...
Flash will be erased from 0x0000d000 to 0x0000efff...
Compressed 20240 bytes to 12435...
Wrote 20240 bytes (12435 compressed) at 0x00001000 in 1.5 seconds (effective 105.8 kbit/s)...
Hash of data verified.
Compressed 3072 bytes to 131...
Wrote 3072 bytes (131 compressed) at 0x00008000 in 0.1 seconds (effective 249.5 kbit/s)...
Hash of data verified.
Compressed 1707760 bytes to 969290...
Wrote 1707760 bytes (969290 compressed) at 0x00010000 in 86.0 seconds (effective 158.9 kbit/s)...
Hash of data verified.
Compressed 8192 bytes to 31...
Wrote 8192 bytes (31 compressed) at 0x0000d000 in 0.1 seconds (effective 497.7 kbit/s)...
Hash of data verified.
Leaving...
Hard resetting via RTS pin...
PS C:\Users\oguzh\Desktop\at firmware icin\ESP32-C3-MINI-1-V<IP_ADDRESS>>
Build or installation Logs.
No response
More Information.
No response

I have examined all of the links you suggested me to look at in detail and I have done all the desired things here. when I connect my esp32 device with ttl, the led connected to the RX pin lights up without stopping. so when I send the "AT" command in the docklight program, I keep getting the "invalid header 0xffffff" error. i would be very grateful if you could help me a little more as I am new to these jobs. what I want to do is to get the "OK" response exactly in the screenshot you sent.

@russianbearx The log below shows that you have only burned four firmwares.
PS C:\Users\oguzh\Desktop\at firmware icin\ESP32-C3-MINI-1-V<IP_ADDRESS>> esptool.exe --chip esp32c3 --port COM3 --baud 115200 write_flash -z 0x1000 "C:\Users\oguzh\Desktop\at firmware icin\ESP32-C3-MINI-1-V<IP_ADDRESS>\bootloader\bootloader.bin" 0x8000 "C:\Users\oguzh\Desktop\at firmware icin\ESP32-C3-MINI-1-V<IP_ADDRESS>\partition_table\partition-table.bin" 0x10000 "C:\Users\oguzh\Desktop\at firmware icin\ESP32-C3-MINI-1-V<IP_ADDRESS>\at firmware icin.bin" 0xd000 "C:\Users\oguzh\Desktop\at firmware icin\ESP32-C3-MINI-1-V<IP_ADDRESS>\ota_data_initial.bin"
Please confirm whether you have correctly Download the AT firmware into the flash according to this document.
0x0 bootloader/bootloader.bin
0x8000 partition_table/partition-table.bin
0xd000 ota_data_initial.bin
0x1e000 at_customize.bin
0x1f000 customized_partitions/mfg_nvs.bin
0x60000 esp-at.bin```

We assume this worked for you, and will close it. If that's not the case, please open another github issue.


go: Remove timecache replace directive in go.mod file

The replace directive for github.com/whyrusleeping/timecache has been removed since the go-libp2p-pubsub library version 0.9.3 no longer utilizes it.
@kostko Was problem #467 fixed in https://github.com/libp2p/go-libp2p-pubsub/tree/master/timecache?

Yes, the issue has been fixed a while back with the introduction of a background goroutine that periodically sweeps. I've closed the upstream issue.


fix: add update token from square

Description:
I opened a developer account on Square, obtained the secrets from there, pasted them here, and revoked them.
I think the Personal Access Token format was changed.

Checklist:

[x] Does your PR pass tests?
[x] Have you written new tests for your changes?


In environment details, show that VM is enabled/disabled

Rancher Version: master 8/11
Steps to Reproduce:

Create and environment with Virtual Machine Support enabled
Go to details page

Results: There is nothing to show you enabled this support
Expected:  maybe show it's on in details page

n/a in 1.2, and VMs will eventually be an infra stack you'll be able to see.


Build SMT metadata at startup.

Reviewer checklist

[ ] Test coverage: stack test --coverage
[ ] Public API documentation: stack haddock
[ ] Style conformance: stylish-haskell

I think I fixed all comments. I still have to write tests. The last commit before starting to write new tests passed on Jenkins.

I forgot about the Map.fromList thing, I'll try to fix it tomorrow.


Re-init conditions each reconcile

This patch follows the same pattern applied to the other operators, where we re-init the conditions at each reconcile loop. Conditions are re-evaluated and updated, keeping the LastTransitionTime for those that haven't changed (it avoids the transition from True to Unknown to True again).
In addition, the observedGeneration field is introduced, and it is used by the openstack-operator to check the IsReady() function for a particular CR in case a minor update is triggered. All the conditions are evaluated during the main Reconcile loop ( or the reconcileNormal function in some circumstances), hence the main ReadyCondition is updated within the same flow. The defer function still updates the Resource and Mirror the condition to the top-level CR.

@cschwede @abays adding the hold label because I'm still testing the changes.

Ok, everything should be fixed now and I can see kuttl tests are happy [1].
We can probably improve more on the conditions front, but we can do that in a follow up and align Swift with what we've done in the other operators (e.g., [2][3]).
[1] https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/test-platform-results/pr-logs/pull/openstack-k8s-operators_swift-operator/189/pull-ci-openstack-k8s-operators-swift-operator-main-swift-operator-build-deploy-kuttl/1773409382202085376/artifacts/swift-operator-build-deploy-kuttl/openstack-k8s-operators-gather/artifacts/must-gather/quay-io-openstack-k8s-operators-openstack-must-gather-sha256-0081c32a29b7405a10ce5ef5c41fbcb65534e1d308ed12060db023744a0c7acb/namespaces/openstack/crs/swifts.swift.openstack.org/swift.yaml
[2] https://github.com/openstack-k8s-operators/glance-operator/pull/481
[3] https://github.com/openstack-k8s-operators/cinder-operator/pull/369


Misuse of xref labels in CHEBI

Example:
[Term]
id: CHEBI:51990
name: tetrabutylammonium fluoride
subset: 3_STAR
synonym: "N,N,N-tributylbutan-1-aminium fluoride" EXACT IUPAC_NAME [IUPAC]
synonym: "261.283" RELATED MONOISOTOPIC_MASS [ChEBI]
synonym: "C16H36FN" RELATED FORMULA [ChEBI]
synonym: "261.46210" RELATED MASS [ChEBI]
synonym: "0" RELATED CHARGE [ChEBI]
synonym: "[F-].CCCC[N+](CCCC)(CCCC)CCCC" RELATED SMILES [ChEBI]
synonym: "FPGGTKZVZWFYPV-UHFFFAOYSA-M" RELATED InChIKey [ChEBI]
synonym: "InChI=1S/C16H36N.FH/c1-5-9-13-17(14-10-6-2,15-11-7-3)16-12-8-4;/h5-16H2,1-4H3;1H/q+1;/p-1" RELATED InChI [ChEBI]
xref: Reaxys:3570522 "Reaxys"
xref: Beilstein:3570522 "Beilstein"
xref: CAS:429-41-4 "ChemIDplus"
xref: PMID:21142041 "Europe PMC"
xref: PMID:21517057 "Europe PMC"
xref: PMID:22229781 "Europe PMC"
xref: PMID:15074950 "Europe PMC"
is_a: CHEBI:24060
is_a: CHEBI:51992
relationship: has_role CHEBI:63060

E.g.
xref: Beilstein:3570522 "Beilstein"

The intent for the xref label in obo format is to assign a typically unique name to the specific entity, e.g Beilstein:3570522.
You seem to be using this field as a source of provenance. Provenance can instead be stated with:
xref: Beilstein:3570522 {source="Beilstein"}

But this may cause issues for your users who have written ad-hoc obo parsers.

Hi, I would also like to see this addressed

@cmungall , @cthoyt its done now. We also have been using alt_id for secondary identifier, which robot is complaining about the duplicate. what is the right way to add this information ?


🇨🇿

@patrick91 after the revert, I still see the CZ banner on our website. Do you know why?

@patrick91 after the revert, I still see the CZ banner on our website. Do you know why?

yes, I've been asked to re revert, I did that on vercel for now

@patrick91 after the revert, I still see the CZ banner on our website. Do you know why?

yes, I've been asked to re revert, I did that on vercel for now

Ah thanks! I was about to revert it too. Good to know!


Documentation: Private Repository

Document the process for creating/updating a ~/.git-credentials file for use when pulling from private registries.
Resources:

#251
https://git-scm.com/docs/gitcredentials

Going to re-evaluate these stale doc issues, closing for now.


Misaligned buttons in 3.1.2

Checklist

[X] I have updated the card to the latest version available
[X] I have cleared the cache of my browser
[X] I have checked if the problem is already reported

The problem
Buttons are misaligned (to the left) in version 3.1.2 - the buttons should span the entire width.
Was fine before.

What version of a card has described problem?
3.1.2
What was the last working version card?
3.1.1
What browser (browsers/apps) does have this problem?
all
What version of Home Assistant do you use?
2022.5.5
What type of installation are you running?
Home Assistant OS
Card's configuration
type: custom:kodi-search-card
entity: sensor.kodi_media_sensor_search
show_thumbnail: true
title: Kodi
show_action_mode: false
action_mode: play
order:
  - episode
  - movie

Javascript errors shown in the browser's console (if applicable)
No response
Additional information
No response

Hi,
Thanks for reporting. I just adapted the css. Should be ok now with version 3.1.3.
Attention the config parameters changed a little bit since last version. order should be replaced by media_type_order.

Thank you Gautier, 3.1.3 works as expected.


Two days are selected in picker around DST in Brazil

Set your computer (PC win7) to Brazil (UTC-3)
(Reproducable in Chrome)

Go to the demo page
http://indrimuska.github.io/angular-moment-picker/
Select October 17 2016 in datepicker
Open datepicker again
Problem:
Both 16 and 17 October are selected

Hi @jenspettersson68,
I think I've found a solution, but maybe I am missing something I don't know about Brazilian DST. Can you please check this plunker out and let me know if you still have any trouble with it?
Thanks!

Sorry, but I am not able to fix it at the moment, since it depends on how MomentJS works.
As I can see, actually there's no way to fix this:
// assuming we are using Firefox and Brazilian Timezone
moment('2016-10-16', 'YYYY-MM-DD').format('YYYY-MM-DD') // returns `2016-10-15`


Forbidden Access Error 403

Hi,
I am trying to access the database from Python - using import pyergast - but I get an error 403 when I am calling any function.

import requests
import pyergast
from pyergast import pyergast
import numpy as np
import pandas as pd
url = 'http://ergast.com/api/f1/circuits.json?limit=1000'
r = requests.get(url)
r.status_code
Out[10]: 403
Do you know how I can solve this issue please ?
Thank you very much

You don't have to use requests alongside pyergast to quert Ergast data - pyErgast will suffice, it's the whole point of that package...


Fix menu to work on github actions

could do this by making two environments, interactive and non-interactive, and having interactive call the menu and non-interactive output the sample reports. then setting the environment when running on github as non-interactive

I have tried adding a step into the workflow that simulates a user input of 0 so the app would exit the menu automatically? seemed easier than creating a whole environment for it? but it didnt work

tried adding the echo to the build step instead, didnt work

added code to set environment for non interactive mode, this should mean that workflow is not waiting (and failing) on user input when none can be found. the app still works when running locally or by running the groupproject.jar in target directory after compiling with maven


community add collaborator wm1581066 for issue and pr label

Proposed changes

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


Ensure every CST element has a SOURCE, suggest how to capture whitespace and comments

I'd like to be able to parse a source file into a tree structure which includes all information required to build the source (including whitespace and comments).  This would be easier if every parsed CST element has a valid associated source range.  Currently that isn't the case for (at least) QUOTE elements.  See:
SEL/LISP-DIFF> (labels ((maptree (fn tree)
                          (if (concrete-syntax-tree:consp tree)
                              (cons
                               (maptree fn (concrete-syntax-tree:first tree))
                               (maptree fn (concrete-syntax-tree:rest tree)))
                              (funcall fn tree))))
                 (maptree #'concrete-syntax-tree:source
                          (with-input-from-string (in "'(1 2 3 4)")
                            (cst-read in))))
(NIL ((2 . 3) (4 . 5) (6 . 7) (8 . 9)))

I've taken a shot at building this using cst-read and record-skipped-input with some custom code to fold everything together and add whitespace.  See https://github.com/GrammaTech/sel/blob/master/ast-diff/lisp-diff.lisp#L71, is there a better way?
Thanks!

There are two separate questions here:

Can't we ensure that every CST node has an associate source range?
For eclector.concrete-syntax-tree:cst-read we take the position that not all CST nodes have a corresponding source range.

One reason are reader macros which can fabricate arbitrary expressions not related to the source at all. The symbol quote in (quote 1 2 3 4) is a simple example of this.

Another reason are parts of the list structure that have no representation in the input string:
(labels ((maptree (fn tree)
           (if (concrete-syntax-tree:consp tree)
               (list
                (funcall fn tree) ; CHANGED
                (maptree fn (concrete-syntax-tree:first tree))
                (maptree fn (concrete-syntax-tree:rest tree)))
               (funcall fn tree))))
  (maptree #'concrete-syntax-tree:source
           (with-input-from-string (in "'(1 2 3 4)")
             (eclector.concrete-syntax-tree:cst-read in))))
((0 . 10) NIL (NIL ((1 . 10) (2 . 3) (NIL (4 . 5) (NIL (6 . 7) (NIL (8 . 9) NIL)))) NIL))

A custom client can of course implement a different behavior. To this end, consider the wip-parse-result-protocol-2 branch and in particular https://github.com/robert-strandh/Eclector/blob/wip-parse-result-protocol-2/code/parse-result/second-climacs-test.lisp .

Is there a better way to integrate skipped input into the parse result?
Again, consider the wip-parse-result-protocol-2 branch and in particular https://github.com/robert-strandh/Eclector/blob/wip-parse-result-protocol-2/code/parse-result/second-climacs-test.lisp .
There is a good chance we will do something very similar in the master branch to better support clients other than cst-read.

To followup, over a year later we're still using this branch.  Any chance this functionality will (or maybe has already) make its way to master?

Any chance this functionality will (or maybe has already) make its way to master?

This has not happened yet, but several steps towards that goal are underway.

To clarify, the parse-result protocol has made it into master, but I'm not sure it fully supports this use-case.

I made https://github.com/GrammaTech/sel/pull/11. Let me know if that works for you.