[flutter_web] Layout bug with HTML renderer

Unfortunately, I was not able to pinpoint exactly what the problem is so I have included a repository below in which I have encountered the bug
Steps to Reproduce

Clone this repository
Build the application using flutter build web --release --webrenderer html
Observe the output

Expected results:

Should be as close as possible to canvaskit layout

Actual results:

Layout is completely different, including some widgets going completely off screen

Logs
flutter run -v --web-renderer html output:
[  +86 ms] executing: [/home/nabeel/fvm/versions/stable/] git -c log.showSignature=false log -n 1 --pretty=format:%H
[  +44 ms] Exit code 0 from: git -c log.showSignature=false log -n 1 --pretty=format:%H
[        ] 8962f6dc68ec8e2206ac2fa874da4a453856c7d3
[   +1 ms] executing: [/home/nabeel/fvm/versions/stable/] git tag --points-at 8962f6dc68ec8e2206ac2fa874da4a453856c7d3
[  +20 ms] Exit code 0 from: git tag --points-at 8962f6dc68ec8e2206ac2fa874da4a453856c7d3
[        ] 2.0.2
[  +54 ms] executing: [/home/nabeel/fvm/versions/stable/] git rev-parse --abbrev-ref --symbolic @{u}
[   +6 ms] Exit code 0 from: git rev-parse --abbrev-ref --symbolic @{u}
[        ] origin/stable
[        ] executing: [/home/nabeel/fvm/versions/stable/] git ls-remote --get-url origin
[   +5 ms] Exit code 0 from: git ls-remote --get-url origin
[        ] https://github.com/flutter/flutter.git
[  +53 ms] Unable to locate an Android SDK.
[   +5 ms] executing: [/home/nabeel/fvm/versions/stable/] git rev-parse --abbrev-ref HEAD
[   +6 ms] Exit code 0 from: git rev-parse --abbrev-ref HEAD
[        ] stable
[  +74 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.
[   +2 ms] Artifact Instance of 'WindowsEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required, skipping update.
[  +87 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.
[   +2 ms] Artifact Instance of 'WindowsEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required, skipping update.
[ +105 ms] Skipping pub get: version match.
[  +75 ms] Found plugin path_provider at /home/nabeel/.pub-cache/hosted/pub.dartlang.org/path_provider-2.0.1/
[   +7 ms] Found plugin path_provider_linux at /home/nabeel/.pub-cache/hosted/pub.dartlang.org/path_provider_linux-2.0.0/
[   +3 ms] Found plugin path_provider_macos at /home/nabeel/.pub-cache/hosted/pub.dartlang.org/path_provider_macos-2.0.0/
[   +5 ms] Found plugin path_provider_windows at /home/nabeel/.pub-cache/hosted/pub.dartlang.org/path_provider_windows-2.0.0/
[ +132 ms] Found plugin path_provider at /home/nabeel/.pub-cache/hosted/pub.dartlang.org/path_provider-2.0.1/
[   +2 ms] Found plugin path_provider_linux at /home/nabeel/.pub-cache/hosted/pub.dartlang.org/path_provider_linux-2.0.0/
[   +1 ms] Found plugin path_provider_macos at /home/nabeel/.pub-cache/hosted/pub.dartlang.org/path_provider_macos-2.0.0/
[   +3 ms] Found plugin path_provider_windows at /home/nabeel/.pub-cache/hosted/pub.dartlang.org/path_provider_windows-2.0.0/
[ +202 ms] Launching lib/main.dart on Chrome in debug mode...
[ +121 ms] Updating assets
[ +125 ms] Manifest contained wildcard assets. Inserting missing file into build graph to force rerun. for more information see #56466.
[   +2 ms] Waiting for connection from debug service on Chrome...
[  +23 ms] Found plugin path_provider at /home/nabeel/.pub-cache/hosted/pub.dartlang.org/path_provider-2.0.1/
[   +1 ms] Found plugin path_provider_linux at /home/nabeel/.pub-cache/hosted/pub.dartlang.org/path_provider_linux-2.0.0/
[   +1 ms] Found plugin path_provider_macos at /home/nabeel/.pub-cache/hosted/pub.dartlang.org/path_provider_macos-2.0.0/
[   +1 ms] Found plugin path_provider_windows at /home/nabeel/.pub-cache/hosted/pub.dartlang.org/path_provider_windows-2.0.0/
[  +41 ms] Found plugin path_provider at /home/nabeel/.pub-cache/hosted/pub.dartlang.org/path_provider-2.0.1/
[   +1 ms] Found plugin path_provider_linux at /home/nabeel/.pub-cache/hosted/pub.dartlang.org/path_provider_linux-2.0.0/
[        ] Found plugin path_provider_macos at /home/nabeel/.pub-cache/hosted/pub.dartlang.org/path_provider_macos-2.0.0/
[   +1 ms] Found plugin path_provider_windows at /home/nabeel/.pub-cache/hosted/pub.dartlang.org/path_provider_windows-2.0.0/
[ +114 ms] <- reset
[   +6 ms] /home/nabeel/fvm/versions/stable/bin/cache/dart-sdk/bin/dart --disable-dart-dev /home/nabeel/fvm/versions/stable/bin/cache/artifacts/engine/linux-x64/frontend_server.dart.snapshot --sdk-root /home/nabeel/fvm/versions/stable/bin/cache/flutter_web_sdk/ --incremental --target=dartdevc --debugger-module-names --experimental-emit-debug-metadata -DFLUTTER_WEB_AUTO_DETECT=false -DFLUTTER_WEB_USE_SKIA=false --output-dill /tmp/flutter_tools.UPJHRQ/flutter_tool.KDKBKS/app.dill --libraries-spec file:///home/nabeel/fvm/versions/stable/bin/cache/flutter_web_sdk/libraries.json --packages /home/nabeel/IdeaProjects/blogr_frontend_mentor/.dart_tool/package_config.json -Ddart.vm.profile=false -Ddart.vm.product=false --enable-asserts --track-widget-creation --filesystem-root /tmp/flutter_tools.UPJHRQ/flutter_tools.EYODOW --filesystem-scheme org-dartlang-app --initialize-from-dill build/e1ffba66f615b3b54e08e2104bac7ab8.cache.dill.track.dill --platform file:///home/nabeel/fvm/versions/stable/bin/cache/flutter_web_sdk/kernel/flutter_ddc_sdk_sound.dill --sound-null-safety
[   +7 ms] <- compile org-dartlang-app:/web_entrypoint.dart
[+28840 ms] Waiting for connection from debug service on Chrome... (completed in 29.0s)
[        ] Synced 38.1MB.
[        ] <- accept
[        ] Caching compiled dill
[ +171 ms] Using Google Chrome 89.0.4389.90

[ +746 ms] [CHROME]:
[        ] [CHROME]:DevTools listening on ws://<IP_ADDRESS>:39657/devtools/browser/1e22f9e1-0ac9-4c68-b1e5-489f4460488d
[ +458 ms] DwdsInjector: Received request for entrypoint at http://localhost:33157/main_module.bootstrap.js
[   +9 ms] MetadataProvider: Loading debug metadata...
[  +41 ms] MetadataProvider: Loaded debug metadata
[  +19 ms] DwdsInjector: Injected debugging metadata for entrypoint at http://localhost:33157/main_module.bootstrap.js
[+3924 ms] DevHandler: Debug service listening on ws://<IP_ADDRESS>:40133/lGQgoFxvdj0=/ws

[  +10 ms] Debug service listening on ws://<IP_ADDRESS>:40133/lGQgoFxvdj0=/ws
[        ] 💪 Running with sound null safety 💪
[   +3 ms] 🔥  To hot restart changes while running, press "r" or "R".
[        ] For a more detailed help message, press "h". To quit, press "q".
[+2104 ms] ══╡ EXCEPTION CAUGHT BY RENDERING LIBRARY ╞═════════════════════════════════════════════════════════
[   +5 ms] The following UnimplementedError was thrown during paint():
[        ] UnimplementedError
[        ] The relevant error-causing widget was:
[        ]   RawPicture
[        ]   file:///home/nabeel/.pub-cache/hosted/pub.dartlang.org/flutter_svg-0.21.0-nullsafety.0/lib/svg.dart:774:18
[        ] When the exception was thrown, this was the stack:
[        ] dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/errors.dart 236:49  throw_
[        ] lib/_engine/engine/html/canvas.dart 448:5                                     drawPicture
[        ] packages/flutter_svg/src/render_picture.dart 194:12                           paint
[   +7 ms] packages/flutter/src/rendering/object.dart 2322:7                             [_paintWithContext]
[   +1 ms] packages/flutter/src/rendering/object.dart 189:12                             paintChild
[   +1 ms] packages/flutter/src/rendering/proxy_box.dart 142:14                          paint
[        ] packages/flutter/src/rendering/object.dart 2322:7                             [_paintWithContext]
[   +1 ms] packages/flutter/src/rendering/object.dart 189:12                             paintChild
[        ] packages/flutter/src/rendering/proxy_box.dart 142:14                          paint
[        ] packages/flutter/src/rendering/object.dart 588:14                             pushTransform
[        ] packages/flutter/src/rendering/proxy_box.dart 2590:21                         [_paintChildWithTransform]
[   +1 ms] packages/flutter/src/rendering/proxy_box.dart 2607:17                         paint
[   +1 ms] packages/flutter/src/rendering/object.dart 2322:7                             [_paintWithContext]
[   +1 ms] packages/flutter/src/rendering/object.dart 189:12                             paintChild
[        ] packages/flutter/src/rendering/proxy_box.dart 142:14                          paint
[        ] packages/flutter/src/rendering/object.dart 2322:7                             [_paintWithContext]
[        ] packages/flutter/src/rendering/object.dart 189:12                             paintChild
[   +7 ms] packages/flutter/src/rendering/proxy_box.dart 142:14                          paint
[   +1 ms] packages/flutter/src/rendering/object.dart 588:14                             pushTransform
[   +5 ms] packages/flutter/src/rendering/proxy_box.dart 2361:24                         paint
[        ] packages/flutter/src/rendering/object.dart 2322:7                             [_paintWithContext]
[        ] packages/flutter/src/rendering/object.dart 189:12                             paintChild
[        ] packages/flutter/src/rendering/box.dart 2805:14                               defaultPaint
[        ] packages/flutter/src/rendering/stack.dart 629:5                               paintStack
[        ] packages/flutter/src/rendering/stack.dart 639:7                               paint
[        ] packages/flutter/src/rendering/object.dart 2322:7                             [_paintWithContext]
[        ] packages/flutter/src/rendering/object.dart 189:12                             paintChild
[        ] packages/flutter/src/rendering/proxy_box.dart 142:14                          paint
[        ] packages/flutter/src/rendering/proxy_box.dart 2165:11                         paint
[        ] packages/flutter/src/rendering/object.dart 2322:7                             [_paintWithContext]
[        ] packages/flutter/src/rendering/object.dart 189:12                             paintChild
[        ] packages/flutter/src/rendering/proxy_box.dart 142:14                          paint
[        ] packages/flutter/src/rendering/object.dart 396:12                             pushLayer
[        ] packages/flutter/src/rendering/object.dart 488:7                              pushClipRRect
[        ] packages/flutter/src/rendering/proxy_box.dart 1543:22                         paint
[        ] packages/flutter/src/rendering/object.dart 2322:7                             [_paintWithContext]
[        ] packages/flutter/src/rendering/object.dart 189:12                             paintChild
[        ] packages/flutter/src/rendering/box.dart 2805:14                               defaultPaint
[        ] packages/flutter/src/rendering/stack.dart 629:5                               paintStack
[        ] packages/flutter/src/rendering/stack.dart 639:7                               paint
[        ] packages/flutter/src/rendering/object.dart 2322:7                             [_paintWithContext]
[        ] packages/flutter/src/rendering/object.dart 189:12                             paintChild
[        ] packages/flutter/src/rendering/proxy_box.dart 142:14                          paint
[   +5 ms] packages/flutter/src/rendering/object.dart 2322:7                             [_paintWithContext]
[        ] packages/flutter/src/rendering/object.dart 140:10                             _repaintCompositedChild
[        ] packages/flutter/src/rendering/object.dart 100:5                              repaintCompositedChild
[        ] packages/flutter/src/rendering/object.dart 978:29                             flushPaint
[        ] packages/flutter/src/rendering/binding.dart 455:19                            drawFrame
[        ] packages/flutter/src/widgets/binding.dart 874:13                              drawFrame
[        ] packages/flutter/src/rendering/binding.dart 319:5                             [_handlePersistentFrameCallback]
[        ] packages/flutter/src/scheduler/binding.dart 1144:15                           [_invokeFrameCallback]
[        ] packages/flutter/src/scheduler/binding.dart 1082:9                            handleDrawFrame
[        ] packages/flutter/src/scheduler/binding.dart 998:5                             [_handleDrawFrame]
[        ] lib/_engine/engine/platform_dispatcher.dart 896:13                            invoke
[        ] lib/_engine/engine/platform_dispatcher.dart 145:5                             invokeOnDrawFrame
[        ] lib/_engine/engine.dart 259:45                                                <fn>
[   +1 ms] The following RenderObject was being processed when the exception was fired: RenderPicture#07ce3:
[   +1 ms]   creator: RawPicture ← SizedBox ← FittedBox ← Semantics ← SvgPicture ← Transform ← Stack ←
[   +1 ms]     DecoratedBox ← ClipRRect ← Stack ← Header ← RepaintBoundary ← ⋯
[        ]   parentData: <none> (can use size)
[        ]   constraints: BoxConstraints(w=3175.0, h=3174.0)
[   +1 ms]   size: Size(3175.0, 3174.0)
[        ] This RenderObject has no descendants.
[        ] ════════════════════════════════════════════════════════════════════════════════════════════════════
[        ] Another exception was thrown: UnimplementedError
[ +214 ms] Another exception was thrown: UnimplementedError
[   +2 ms] Another exception was thrown: UnimplementedError
[   +2 ms] Another exception was thrown: UnimplementedError
[ +199 ms] Another exception was thrown: UnimplementedError
[   +1 ms] Another exception was thrown: UnimplementedError
[   +1 ms] Another exception was thrown: UnimplementedError
[+4063 ms] DevHandler: Stopped debug service on ws://<IP_ADDRESS>:43117

[ +510 ms] Application finished.
[   +8 ms] "flutter run" took 42,536ms.
[ +251 ms] ensureAnalyticsSent: 245ms
[   +1 ms] Running shutdown hooks
[        ] Shutdown hook priority 4
[  +26 ms] Shutdown hooks complete
[        ] exiting with code 0

flutter analyze output:
Analyzing blogr_frontend_mentor...
No issues found! (ran in 5.0s)

flutter doctor -v  output:
[✓] Flutter (Channel stable, 2.0.2, on Linux, locale en_IN)
    • Flutter version 2.0.2 at /home/nabeel/fvm/versions/stable
    • Framework revision 8962f6dc68 (6 days ago), 2021-03-11 13:22:20 -0800
    • Engine revision 5d8bf811b3
    • Dart version 2.12.1

[✗] Android toolchain - develop for Android devices
    ✗ Unable to locate Android SDK.
      Install Android Studio from: https://developer.android.com/studio/index.html
      On first launch it will assist you in installing the Android SDK components.
      (or visit https://flutter.dev/docs/get-started/install/linux#android-setup for detailed instructions).
      If the Android SDK has been installed to a custom location, please use
      `flutter config --android-sdk` to update to that location.

[✓] Chrome - develop for the web
    • CHROME_EXECUTABLE = /usr/bin/google-chrome-stable

[!] Android Studio (not installed)
    • Android Studio not found; download from https://developer.android.com/studio/index.html
      (or visit https://flutter.dev/docs/get-started/install/linux#android-setup for detailed instructions).

[✓] IntelliJ IDEA Community Edition (version 2020.3)
    • IntelliJ at /snap/intellij-idea-community/289
    • Flutter plugin version 53.1.5
    • Dart plugin version 203.7759

[✓] Connected device (1 available)
    • Chrome (web) • chrome • web-javascript • Google Chrome 89.0.4389.90

! Doctor found issues in 2 categories.

I missed some of the logs and I now understand that this is cause because of the flutter_svg package. Therefore, I am closing this issue


Fix MeshAllocator panic

Objective
Fixes #14540
Solution

Clean slab layouts from stale SlabIds when freeing meshes
Technically performance requirements of freeing now increase based on the number of existing meshes, but maybe it doesn't matter too much in practice
This was the case before this PR too, but it's technically possible to free and allocate 2^32 times and overflow with SlabIds and cause incorrect behavior. It looks like new meshes would then override old ones.

Testing

Tested in loading_screen example and tapping keyboard 1 and 2.

The crash happens when we remove empty slabs in MeshAllocator::free_meshes. This may cause the slab ids in slab_layouts to no longer point to valid slabs. Instead of ignoring invalid slab ids in candidate_slabs could we remove them outright?

That would probably be better.
Also does the number in SlabId matter? next_slab_id will be infinitely increasing over a long session of spawning and despawning things. If it's somehow directly mapped to memory we could run out.

Now I made the (probably) proper fix.


Publish 09/17/2021, 10:30 AM

Docs Build status updates of commit 4fd6ddc:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/Get-SafeLinksDetailReport.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Bad key found: no private key material or GPGKey

[write something useful and descriptive here]
Unable to login to app. I am, however, using my own generated GPG key that has the master signing key separated off-system. I have a separate signing subkey used for everything aside from trust signing, does that makes a difference?
There was an error provisioning
Unknown error: Bad key found: no private key material or GPGKey
my log id: 2b9db13d0e23bea0ffcf0b1c

https://github.com/keybase/client/issues/4284 might be related.

Heya, I think I had a similar issue, so here's how I solved it: https://github.com/keybase/client/issues/6035#issuecomment-282481965.
Hope that helps,
Zach

Currently encountering this issue. Have tried the suggestion in #6035 with no luck.

@ryepdx can you provide more details?

My Keybase username is ryepdx. I don't know what the log ID is. I don't see one with the error message. I'm running Ubuntu 16.04.1 LTS.
I have subkeys for encrypting and signing. I've been using the website without trouble. I'd uploaded my private key previously, but deleted it in the course of trying to resolve this issue. Doesn't seem to have made a difference. I also ran find and deleted everything referring to [K|k]eybase and re-installed the .deb package. Still no change.

What operation is failing? Perform that operation and then run 'keybase log
send'
On Mon, Apr 10, 2017 at 5:50 PM Ryan<EMAIL_ADDRESS>wrote:

My Keybase username is ryepdx https://keybase.io/ryepdx. I don't know
what the log ID is. I don't see one with the error message. I'm running
Ubuntu 16.04.1 LTS.
I have subkeys for encrypting and signing. I've been using the website
without trouble. I'd uploaded my private key previously, but deleted it in
the course of trying to resolve this issue. Doesn't seem to have made a
difference. I also ran find and deleted everything referring to
[K|k]eybase and re-installed the .deb package. Still no change.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/keybase/client/issues/4649#issuecomment-293089560,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA05_0dK1senPRSrfMXv-T20E90LTtw6ks5ruqQtgaJpZM4KZJ6G
.


Add UNNotificationCategory option for iOS.

This commit will enable unnotificationcategory for iOS.
https://developer.apple.com/documentation/usernotifications/unnotificationcategory
It'll categorize notifications if a user chose not to display preview of notifications on setting.
And it'll also let you to handle actions that depends on categories.

@timakin Merged. Thanks.


Support connection strings

Closes #54

Hi!
Will this PR be closed any time soon, or is there any work that needs to be done?
I would like to use this crate, but instrumentation keys will be deprecated in 2 years in application insights.

Hi. I wasn't super happy with the API, but otherwise this should be good to go.

instrumentation keys will be deprecated in 2 years in application insights

Do you know what they're going to be replaced with? This PR just parses the instrumentation key out of the connection string. If instrumentation keys will go away entirely, this would require more work.

Thank you for the quick response!
This is what I found on microsoft docs regarding the instrumentation key ingestion:
InstrumentationKey=b380a8e3-22fb-49e2-9de6-ee3b9dd48a2e;IngestionEndpoint=https://westeurope-5.in.applicationinsights.azure.com/;LiveEndpoint=https://westeurope.livediagnostics.monitor.azure.com/
So application insights will actually keep supporting it, but connectionstrings will be preferred over instrumentation keys, and with the use of connectionstrings, some new capabilities  can be unlocked (e.g. adding authorization):
https://learn.microsoft.com/en-us/azure/azure-monitor/app/migrate-from-instrumentation-keys-to-connection-strings#new-capabilities
Could these new capabilities be of any interest for your project?

Thanks. Yeah, connection strings are certainly useful. As far as I can see the new capabilities boil down to:

Being able to configure the ingestion endpoint. That's already possible with this library. But using a connection string for it makes this easier because you can copy-paste the entire connection string.
Azure AD authentication. The docs don't looks like a connection string is strictly required here. But either way, that needs additional work.

Still, I would like to merge and release this PR. I don't expect to do it this week. But I'll try to do it end of next week.

That would be great! Thanks a lot :)


Keeping Vault secrets encrypted in helmfile diff & apply

We are using the hashicorp vault integration ( #906 ) with success, however the passwords are shown in clear text in the helmfile diff & helmfile apply outputs.
mypassword: 'ref+vault://secret/data/foo?proto=http#/mykey'
+   my_password: ismyclearpassword
Are there any way to instead show what has been set in helmfile's values or show a dummy value ?
Ex:
+   my_password: ref+vault://secret/data/foo?proto=http#/mykey
Or:
+   my_password: ***HIDDEN***
Thanks.

Hey
"helmfile diff" shows differences for kubernetes entities and uses "helm-diff" plugin. By default this plugin hides all values in "data" section of kubernetes kind "Secret"
apiVersion: v1
kind: Secret
metadata:
  name: cm-config
type: Opaque
data:
  mypassword: {{ .Values.mypassword | b64enc | quote }}

and then reference it in you environment value like this
- name: DB_PASSWORD
  valueFrom:
    secretKeyRef:
      name: cm-config
      key: mypassword

Therefore you wiil see something like this in your diff output (your secret values are beeing replaced by '+++++++')
 + # Source: app/templates/cm-config.yaml
 + apiVersion: v1
 + kind: Secret
 + metadata:
 +   name: cm-config
 + data:
 +   password: '++++++++ # (24 bytes)'
 + type: Opaque

@Tlzps Hey! As @zam-zam has explained kindly, it doesn't happen when you limit your secret refs to be only placed as Secret resources' data.
Where are you putting your secret ref on?

@zam-zam Thank you very much for all these details. I am new to Kube and didn't experiment with Secrets yet.
@mumoshu , I was just testing the Vault integration so I created a Value key in the env file associated with the environment that I specified in `helmfile -e myenv'

@Tlzps Yeah that's expected. I believe no K8s-related tool treats ConfigMap as to if I might contain credentials. ConfigMap isn't encrypted at rest before being persisted in Etcd.

So use Secret instead of ConfigMap.


fix: GIT_SHALLOW not used without SOURCE_CACHE

Hello !
When using CPMAddPackage, I noticed a long download time.
After inspection, my conclusion is that the GIT_SHALLOW flag is never add automatically in my case (when using GIT_TAG) because the code is nested inside conditions for CPM_ARGS_UNPARSED_ARGUMENTS.
I think it was not intended to be that way. I rather expect to place the code outside the conditional block, this way GIT_SHALLOW is always ON as long as we download something from git without hash.
What do you think ?

The original code appears correct, as GIT_SHALLOW should only be automatically appended if downloading to a cache directory. Otherwise it is not possible to change the dependency's version without removing the build directory, because CMake doesn't re-fetch a git repository if the tag changes. You can see that in the failed CI tests.
The reason for the poor performance is probably due to CMake's slow FetchContent implementation.

The original code appears correct, as GIT_SHALLOW should only be automatically appended if downloading to a cache directory. Otherwise it is not possible to change the dependency's version without removing the build directory, because CMake doesn't re-fetch a git repository if the tag changes. You can see that in the failed CI tests.
The reason for the poor performance is probably due to CMake's slow FetchContent implementation.


API v3 mail & template_id

If I use template_id, I am forced to include "content": {"type": "text/html", "value": "-"}
Otherwise it does not pass validation.
Expected behavior: "content" should be optional if template_id is provided.

+1

Hello @zygimantas,Thanks for your suggestion or question! In an attempt to clear out our backlog,                                              we are closing out issues over 90 days old.                                             If this is still an issue, please feel free to reopen it.                                             Team SendGrid DX-Docs

Hello @zygimantas,Thanks for your suggestion or question! In an attempt to clear out our backlog,                                              we are closing out issues over 90 days old.                                             If this is still an issue, please feel free to reopen it.                                             Team SendGrid DX-Docs

Hello @zygimantas,Thanks for your suggestion or question! In an attempt to clear out our backlog,                                              we are closing out issues over 90 days old.                                             If this is still an issue, please feel free to reopen it.                                             Team SendGrid DX-Docs

Hello @zygimantas,Thanks for your suggestion or question! In an attempt to clear out our backlog,                                              we are closing out issues over 90 days old.                                             If this is still an issue, please feel free to reopen it.                                             Team SendGrid DX-Docs

Hello @zygimantas,Thanks for your suggestion or question! In an attempt to clear out our backlog,                                              we are closing out issues over 90 days old.                                             If this is still an issue, please feel free to reopen it.                                             Team SendGrid DX-Docs


Create mailwb-online-campus.txt

@WaldemarCoding Thank you for your patience while waiting for a review and processing your request. Pull request merged.
Please start requesting the licenses in about an hour, to let the changes to propagate through our system.


Converted TensorFlow Lite model is not a valid model in Android Studio

System information
Issue encountered with own model but can also reproduced using the example code found here:
https://github.com/tensorflow/tensorflow/blob/master/tensorflow/lite/examples/experimental_new_converter/Keras_LSTM_fusion_Codelab.ipynb
Running in a Colaboratory notebook
TensorFlow v2.3.0-0-gb36436b087 2.3.0
Android Studio 4.1.1
Describe the current behavior
The notebook runs as expected and the TensorFlow Lite model produces the expected output in Colaboratory.
Importing the downloaded model into Android Studio 4.1.1 gives the error
'Not a valid TensorFlow Lite model'
Describe the expected behavior
A successfully converted TensorFlow Lite LSTM model should be valid and usable in Android Studio
Standalone code to reproduce the issue
The code used to reproduce is the example LSTM model
https://github.com/tensorflow/tensorflow/blob/master/tensorflow/lite/examples/experimental_new_converter/Keras_LSTM_fusion_Codelab.ipynb
Other info / logs

The example scope is to demonstrate building a keras sequential model and its conversion into tflite.
For deploying a tf lite model into android platform you can try examples given here.

The problem is with Android Studio.
Copy pasting code from the examples given I can load and run the model even though Android Studio tells me it is an invalid model and refuses to import it. There is a ticket raised with  Android Studio.

Thanks for your issue. Can you please tag the open ticket in this issue thread as well?

On Google IssueTracker:
Successfully converted TensorFlow Lite model is invalid model in Android Studio 4.1.1
https://issuetracker.google.com/issues/174736305

I have the same problem while importing. alongside this  whilie converting  my model
tflite_model = converter.convert()
I am getting below warning.
WARNING:absl:Found untraced functions such as lstm_cell_layer_call_fn, lstm_cell_layer_call_and_return_conditional_losses, lstm_cell_layer_call_fn, lstm_cell_layer_call_and_return_conditional_losses, lstm_cell_layer_call_and_return_conditional_losses while saving (showing 5 of 5). These functions will not be directly callable after loading.

@n9hal Did you end up finding a solution? I have the same warning on conversion. It does not run in the TFLite C++ api on Android

@Parth220 No, Didn't find anything

Any update on this one? I'm suffering from this problem too..

Hi @pnovapps !
We are checking to see whether you still need help in this issue. Have you checked in latest version of Android Studio/Tensorflow (2.5/2.6)yet ? Attaching relevant threads for reference. link1,link2. Thanks!


Suggestion: Sync favorites across clients

Hey there!
This is merely a suggestion, as I don't know whether and how it could be done but I couldn't find an issue here or a discussion about this on the forum so I'll just leave it here: I'd like to have my list of favorites synced along with my notes so I've got the same favorites on any client that has the plugin installed. I felt this was a very obvious feature tbh and was wondering why nobody seemed to have mentioned it so far. Or maybe they have and I missed that. Anyhow, maybe you can consider putting the faves in a note that is just synced along? Or something like this.

In fact, I can't find anything in the forum on this topic either. Looks like it's not that urgent or important to users so far.
You are welcome to advertise this ticket in the forum, if it gets a few votes, I am willing to consider something.

Hey! Thanks for the reply, I think I will try that.

for my usage, the pluggin would be perfect if it has some sync capacities !

It's an enhancement request for this plugin, i think?  but we should also post in the general joplin forum?

Please consider this! My use case involves numerous profiles AND numerous devices with WebDAV synchronization and encryption the primary requirements. My expectation for this plugin therefore was any favorite data added and/or changed on one device would sychronize, along with any note data (of course), to all of my devices. For me, having to input the same favorites more than once and/or needing to manage them per device is simply a non-starter. I would utilize the plugin if it had this feature/capability.

Hi,
The ability to synchronize would really be a plus for me too.
In the meantime, is it possible to save and restore the settings?


Drag and Drop extremely slow on weekly calendars with 15 minute intervals

Drag and drop functionality becomes unreasonably slow when you configure a QCalendarDay in week mode with 15 minute intervals.
To Reproduce
Steps to reproduce the behavior:

Use the WeekDragAndDrop example component
Configure it with 15 minute intervals like so:

:interval-height="12"
:interval-start="64"
:interval-minutes="15"
:interval-count="34"

See error

Expected behavior
Better performance.
Desktop (please complete the following information):

OS: macOS Monterey 12.6.3
Browser: Chrome
Version: 110.0.5481.177 (Official Build) (x86_64)

Additional context
This was not really noticeable with my MBP M2 Max, but was very noticeable on my older desktop where the delay before the interval class appeared was pretty severe and the drag and drop became pretty much unusable.

are you using Vue 3 + QClendar v4?

are you using Vue 3 + QClendar v4?

Yes, I was using Vue 3.2.13 and QCalendar 4.0.0-beta.16

We are seeing this issue. Implementing the same example as here it's noticably slow using 30 min intervals, and unusable with 15 - you can see it slowly rendering the highlighted cells tracing the mouse route due to it being backed up.
The console is showing huge number of interval-class events, so the issue seems to be an exponential increase in intervals to process and the events that go with them.


Improved observability

Scope & Purpose
This is a PR to add more observability.
Metrics:

Added new metric arangodb_network_forwarded_requests to track the number of requests forwarded from one coordinator to another in a load-balancing context.
Added new metric arangodb_replication_cluster_inventory_requests to track the number of requests received for cluster inventories. The cluster inventory API is called at the beginning of a dump process or by arangosync.
Added new metric arangodb_aql_all_query to track the total number of AQL queries.
Added new metric arangodb_aql_total_query_time_msec to track the combined runtime of AQL queries (slow queries and non-slow queries).
Added more scheduler metrics:

arangodb_scheduler_threads_started: Total number of scheduler threads started
arangodb_scheduler_threads_stopped: Total number of scheduler threads stopped
arangodb_scheduler_jobs_done: Total number of scheduler queue jobs done
arangodb_scheduler_jobs_submitted: Total number of jobs submitted to the scheduler queue
arangodb_scheduler_jobs_dequeued: Total number of jobs dequeued from the scheduler queue
arangodb_scheduler_num_working_threads: Number of currently working scheduler threads

Availability API:
Added startup option --server.unavailability-queue-fill-grade.
This option has a consequence for the /_admin/server/availability API only, which is often called by load-balancers and other availability probing systems.
The /_admin/server/availability API will now return HTTP 200 if the fill grade of the scheduler's queue is below the configured value, or HTTP 503 if  the fill grade is above it. This can be used to flag a server as unavailable in case it is already highly loaded.
The default value for this option is 1, which will mean that the availability API will start returning HTTP 503 responses in case the scheduler queue is completely full. This is mostly compatible with previous versions of ArangoDB.
Previously the availability API still returned HTTP 200 in this situation, but this can be considered a bug, because the server was effectively totally overloaded.
To restore 100% compatible behavior with previous version, it is possible to set the option to a value of 0, which is a special value indicating that the queue fill grade will not be honored.
To prevent sending more traffic to an already overloaded server, it can be sensible to reduce the default value to 0.75 or even 0.5. This would mean that instances with a queue longer than 75% (or 50%, resp.) of their maximum queue capacity would return HTTP 503 instead of HTTP 200 when their availability API is probed.

[ ] :hankey: Bugfix (requires CHANGELOG entry)
[x] :pizza: New feature (requires CHANGELOG entry, feature documentation and release notes)
[ ] :fire: Performance improvement
[x] :hammer: Refactoring/simplification
[x] :book: CHANGELOG entry made

Backports:

[x] No backports required

Testing & Verification

[ ] This change is a trivial rework / code cleanup without any test coverage.
[x] The behavior in this PR was manually tested

http://<IP_ADDRESS>:8080/view/PR/job/arangodb-matrix-pr/12751/

http://<IP_ADDRESS>:8080/view/PR/job/arangodb-matrix-pr/12758/

http://<IP_ADDRESS>:8080/view/PR/job/arangodb-matrix-pr/12761/

Tests blue


Please add a license file

I'd like to add this to awesome-zsh-plugins, but it doesn't have a license file.
Please add a license file - if you don't have one in mind,  I recommend using choosealicense.com to help choose an appropriate one.
Thanks!

Yup that's a good point.
I will add a CC0 license to the project.
Thank you for your input !


add a post about consideration of qubit layout in circuit designing

Add a new post "Why Qubits Layout Should Be Involved in Designing Quantum Circuits?"

Very nice post


nimlsp install failed

related nim-lang/nimble/#836

Must install nim with choosenim. make sure nim's version is higher than 1.5.3.
Read This link
curl https://nim-lang.org/choosenim/init.sh -sSf | sh

nim 1.6.4 can not be installed via brew. you must install it with Source archive. download the source file here
then install nimlsp by nimble install nimlsp.


accents (á é í ó ú) not working under ssh if codepage set to utf8

Hi!
I'm being redirected here from the git-for-windows project for one problem I'm experiencing. (For history see git-for-windows/git#902 )
Basically I'm experiencing problems when my windows terminal/console is in utf8 mode (changed with chcp 65001), and then from a bash shell (from msys2 as packaged by git-for-windows) I enter an ssh session to a linux box.
Under the ssh session, I won't be able to enter accented characters. This doesn't happen if I do not change the codepage from its default (850).
As it was pointed out by @nalla , we're not even sure if msys2-bash honors the codepage change.
Do you think this is something that could be investigated here?
(note that I don't have direct experience with msys2 aside from using it as provided by git-for-windows, sorry)
Thanks!

Hi,
It seems to work fine here.
$ é
$ ssh<EMAIL_ADDRESS>$ é

With or without
$ /c/Windows/System32/chcp.com 65001

are you testing it from a normal windows console or from mintty? (the problem appears only in windows normal console)
See https://github.com/git-for-windows/git/issues/902#issuecomment-251982610
However dscho seemed to imply it could be a cygwin (ssh) problem

dscho pointed it's a Cygwin issue and he is right. It should be fixed in Cygwin however I think we could add workaround to shh (if someone knows it).


Install and configure an operating system of the GNU/Linux family

Overview
In order to have a superior development environment, you need to set up and configure appropriate software yourself. You also need to know how to configure things, where they are in your system, and how to survive in that scary black thing with white letters in it — The Terminal.

Let's start by setting up an operating system of the GNU/Linux OS family (that is based on a kernel called Linux).
Now, you have two options: use Fedora (recommended) or some flavor of Ubuntu (like XUbuntu, frequently used by beginners).
It's best to install it directly on your hardware (as a dual-boot, if needed) but you can also try it out in a VM (like VirtualBox).
You also choose to stay on macOS if absolutely necessary but you'll still have to learn your way around terminal-based approaches.
The objective of this task is to get familiar with command-line tools and learn to set up software without using any of the GUI software.
Fedora

[x] Install Fedora
[x] Learn about DNF/YUM/RPM. Here and there. Also: https://fedoramagazine.org/rpm-packages-explained/.
[x] [optionally] Add RPM Fusion to your system: https://rpmfusion.org/
[x] Install Kitty terminal emulator
[x] Install Google Chrome. No GUI-based install, please.
[x] Install Git
[x] Install VS Code using this instruction, but without downloading *.rpm file from browser.

Ubuntu

[ ] Install XUbuntu
[ ] Learn about APT. Here and there
[ ] Install Kitty terminal emulator
[ ] Install Google Chrome but scroll to the section "Install Google Chrome on Ubuntu 18.04 LTS from the Command Line" and use it. No GUI-based install, please.
[ ] Install Git from PPA
[ ] Install VS Code using this instruction, but without downloading *.deb file so find the line "The repository and key can also be installed manually with the following script:" and go from there

All programs were installed via console:), also done upgrading to 37 version of Fedora

Brilliant!


docs(crate): Update crate documentation

Please regenerate the documentation in gh-pages.
Not to scare away potential users :-)

Thanks :)!
A merge will do just that.

nice automation :)


ERROR in Cannot read property 'content' of null

Please provide us with the following information:

OS?
macOS Sierra
Versions.
Running of angular/angular-cli#master
angular-cli: 1.0.0-beta.26
node: 7.2.0
os: darwin x64
@angular/common: 2.4.4
@angular/compiler: 2.4.4
@angular/core: 2.4.4
@angular/forms: 2.4.4
@angular/http: 2.4.4
@angular/platform-browser: 2.4.4
@angular/platform-browser-dynamic: 2.4.4
@angular/router: 3.4.4
@angular/compiler-cli: 2.4.4
Repro steps.

Set up the development setup of angular-cli
ng new --link-cli content-of-null
cd content-of-null
ng serve
Edit something in src/app/app.component.html

The log given by the failure.

Normally this include a stack trace and some more information.

After editing the app rebuilds and this message appears:
ERROR in Cannot read property 'content' of null
No further stack-trace available.
Mention any other details that might be useful.
The app seems to work though this message persists.

Can confirm this happens:

kamik@T460p MINGW64 /d/sandbox/master-project (master)
$ ng serve -o
** NG Live Development Server is running on http://localhost:4200. **
 10% building modules 6/11 modules 5 active<EMAIL_ADDRESS>wait until bundle finished: /
Hash: 2583d4a7fddc703271c3
Time: 9820ms
chunk    {0} polyfills.bundle.js, polyfills.bundle.map (polyfills) 222 kB {4} [initial] [rendered]
chunk    {1} main.bundle.js, main.bundle.map (main) 62.2 kB {3} [initial] [rendered]
chunk    {2} styles.bundle.js, styles.bundle.map (styles) 9.96 kB {4} [initial] [rendered]
chunk    {3} vendor.bundle.js, vendor.bundle.map (vendor) 2.57 MB [initial] [rendered]
chunk    {4} inline.bundle.js, inline.bundle.map (inline) 0 bytes [entry] [rendered]
webpack: bundle is now VALID.
webpack: bundle is now INVALID.
Hash: 70192ef2c5a1c620ab15
Time: 956ms
chunk    {0} polyfills.bundle.js, polyfills.bundle.map (polyfills) 222 kB {4} [initial]
chunk    {1} main.bundle.js, main.bundle.map (main) 62.2 kB {3} [initial] [rendered]
chunk    {2} styles.bundle.js, styles.bundle.map (styles) 9.96 kB {4} [initial]
chunk    {3} vendor.bundle.js, vendor.bundle.map (vendor) 2.57 MB [initial]
chunk    {4} inline.bundle.js, inline.bundle.map (inline) 0 bytes [entry]

ERROR in Cannot read property 'content' of null
webpack: bundle is now VALID.

kamik@T460p MINGW64 /d/sandbox/master-project (master)
$

Also seems to happen when changing .ts and .css files.


posting to eventloop from interrupt broken

Somehow this change:
https://github.com/esp-rs/esp-idf-svc/commit/b5d8295fe02e8fd98755ad40bdea0fae4d957eb0
Broke posting from an interrupt. The post request returns EspError(258).
If I revert to the previous commit it builds fine.
This does not appear to be related to the new panic call. Rather it is because we call isr_post_raw instead of post_raw.
The following change fixes it:
diff --git a/src/eventloop.rs b/src/eventloop.rs
index 2be74f80..b10ce0f4 100644
--- a/src/eventloop.rs
+++ b/src/eventloop.rs
@@ -603,7 +603,7 @@ where
     fn post(&mut self, payload: &P, wait: Option<Duration>) -> Result<bool, Self::Error> {
         if interrupt::active() {
             #[cfg(esp_idf_esp_event_post_from_isr)]
-            let result = P::serialize(payload, |raw_event| self.isr_post_raw(raw_event));
+            let result = P::serialize(payload, |raw_event| self.post_raw(raw_event, wait));

             #[cfg(not(esp_idf_esp_event_post_from_isr))]
             let result = {

Hm. I just quickly re-tested it in https://github.com/ivmarkov/ruwm/commit/e4c7be202a04ac247cec427091bb1c9325a7fd0f
"Works on my machine", so to say.
Are you doing cargo clean; cargo build after setting CONFIG_ESP_EVENT_POST_FROM_ISR=y in sdkconfig.defaults? You should.
Background:
As per the ESP-IDF documentation, calling post_raw (which calls ESP-IDF's esp_event_post_to) from an ISR handler should not be done. Instead, we should be calling isr_post_raw (which calls ESP-IDF's esp_event_isr_post_to).
esp_event_post_to might misbehave when called from an ISR.

It calls a bunch of APIs which I'm not sure are safe to be called from an ISR (calloc, xSemaphoreTakeRecursive, xTaskGetCurrentTaskHandle and xQueueSendToBack), with calloc and xQueueSendToBack (with ticks count) being particularly troublesome, as they would try to use mutexes and wait in an ISR context, which is not good at all
When called from an ISR, esp_event_post_to will also not yield / re-prioritize the awoken even loop task if it has higher priority than the task that was running before the ISR was called

So we have to do whatever possible to make the ISR-dedicated APIs work.
With that said, I'm suspecting you and @pyaillet might be (ab)using the event loop API for things where there are better (lighter-weight and more correct) alternatives.
Are you using an event loop to post that a GPIO "button" was pressed? If so, then you should really make sure that you are using a dedicated event loop per button (which is wasteful! that's one thread per button), or else your logic is flawed. You see, event loop is a broadcast queue, but it also has a limited size. If you are multiplexing "button pressed" events from multiple buttons on it - and if your queue size is small - and since you cannot wait when posting from an ISR - you might miss a button press as the queue is full when you are posting it. Extremely small chance but logically possible.
Where I'm getting at, is that this thing might be more appropriate in these scenarios. It is a bit lighter weight compared to FreeRTOS events' queue, and also it does not exhibit the "queue is full" behavior, because it supports "bit per button" (up to 32 bits): if your button was pressed before and the thread has not processed that yet, you'll set a bit which was already 1 to 1, thus "coalescing" multiple events into one, but that's not a big deal anyway, as long as the coalesce logic is doing it "per button", and since each button has a dedicated bit, that works. Unlike the event queue, which might be full because of the events of other buttons.

If it wasn't picking up on the CONFIG_ESP_EVENT_POST_FROM_ISR, then I think the above change I did that fixed it wouldn't have any affect.
I have no idea why the isr_post_raw is not working. There is no overflow of the queue going on, this happens for the first event.
Your point on maybe the EventLoop is the wrong tool for the job might be valid. It was what I was advised to use on the chat forum a while back. I will have a look at the EspNotify approach when I have time.

Would really help heaps if you tagged releases in git...
If this EspNotify a new thing? I can't find it in esp-idf-sys 0.31.0 which I believe is the latest release.

Is there an example anywhere for EspNotify? Am doing what I think should be correct, but the subscribe isn't getting called. So wonder if I am doing something wrong.

I finally took the time to refactor my project to use EspBackgroundNotify (sorry for the long delay, I was working on something else).
I have an example working here.
It might be a bit overly complex right now, as I was aiming at making it work.
Thanks for your remarks @ivmarkov and for the report @brianmay.

Silly me, was letting the subscription expire. Seems to be OK now. At least for early preliminary tests.

For the record I faced the same problem with the error EspError(258) when posting to the EspBackgroundEventLoop from the ISR despite the option CONFIG_ESP_EVENT_POST_FROM_ISR being set.
Could this be a problem with the EventType Serialization ?
Anyway, using the EspBackgroundEventLoop I faced a strange stackoverflow which I don't seem to get anymore.

Yes, EspNotify seems to be working fine for me.
Next step try to get the new interrupt subscription stuff working. My first attempt had difficulties, but not related to this issue, so won't discuss here.

For the record I faced the same problem with the error EspError(258) when posting to the EspBackgroundEventLoop from the ISR despite the option CONFIG_ESP_EVENT_POST_FROM_ISR being set. Could this be a problem with the EventType Serialization ?
Anyway, using the EspBackgroundEventLoop I faced a strange stackoverflow which I don't seem to get anymore.

EspError(258) is ESP_ERR_INVALID_ARG
You are likely hitting this line of code: https://github.com/espressif/esp-idf/blob/release/v4.4/components/esp_event/esp_event.c#L917
When posting from an ISR, the data you are posting should be 4 bytes big max, as the ISR poster cannot call calloc. How big is the data you are posting, i.e. mem::size_of::<WhateverRustTypeYouSerialize>()?

Ok, on my side, this was clearly the problem as I was not aware of this limitation and tried to post something larger.
Now, using EspBackgroundNotify as you suggested is working fine and seems the best way to go, so thanks for your advice :)

If @brianmay confirms that he is also trying to post a payload which when serialized (or its size_of if you use Copy "serialization") is > 4 bytes, I'll close that.

In my case:
#[derive(Copy, Clone, Debug)]
struct EventLoopMessage(i32, Value);

Yes, looks like this is more then 4 bytes,..,  Ok, closing.


'table.insert_data()' frequently fails in the Python BiqQuery client with error: [Errno 32] Broken pipe

Streaming inserts to a BigQuery table frequently fail with error: [Errno 32] Broken pipe on Debian 7.11 with Python 2.7.3 and google-cloud-python 0.20. The error occurs around 30% of the time.
This happens with a small number of rows (<2000), where each row is less than 2kb. Hence, it is unlikely to be a quota problem.
The code is executed on a Google Cloud Compute VM every 30 minutes. It has failed in 6 out of the last 26 runs.
Here is the code that I am using:
from google.cloud import bigquery
client = bigquery.Client(project=PROJECT_NAME)
dataset = client.dataset(DATASET_NAME)
table = dataset.table(TABLE_NAME, schema=SCHEMA)

#some code to generate ROWS to be inserted

table.insert_data(ROWS)

Here is the full error traceback:
Traceback (most recent call last):
  File "scrape_cronjob.py", line 277, in <module>
    errors = table.insert_data(ROWS)
 File "/usr/local/lib/python2.7/dist-packages/google/cloud/bigquery/table.py", line 773, in insert_data
    data=data)
  File "/usr/local/lib/python2.7/dist-packages/google/cloud/connection.py", line 346, in api_request
    target_object=_target_object)
  File "/usr/local/lib/python2.7/dist-packages/google/cloud/connection.py", line 244, in _make_request
    return self._do_request(method, url, headers, data, target_object)
  File "/usr/local/lib/python2.7/dist-packages/google/cloud/connection.py", line 273, in _do_request
    body=data)
  File "/usr/local/lib/python2.7/dist-packages/oauth2client/transport.py", line 169, in new_request
    redirections, connection_type)
  File "/usr/local/lib/python2.7/dist-packages/httplib2/__init__.py", line 1609, in request
    (response, content) = self._request(conn, authority, uri, request_uri, method, body, headers, redirections, cachekey)
  File "/usr/local/lib/python2.7/dist-packages/httplib2/__init__.py", line 1351, in _request
    (response, content) = self._conn_request(conn, request_uri, method, body, headers)
  File "/usr/local/lib/python2.7/dist-packages/httplib2/__init__.py", line 1273, in _conn_request
    conn.request(method, request_uri, body, headers)
  File "/usr/lib/python2.7/httplib.py", line 1000, in request
    self._send_request(method, url, body, headers)
  File "/usr/lib/python2.7/httplib.py", line 1034, in _send_request
    self.endheaders(body)
  File "/usr/lib/python2.7/httplib.py", line 996, in endheaders
    self._send_output(message_body)
  File "/usr/lib/python2.7/httplib.py", line 847, in _send_output
    self.send(msg)
  File "/usr/lib/python2.7/httplib.py", line 823, in send
    self.sock.sendall(data)
  File "/usr/lib/python2.7/ssl.py", line 229, in sendall
    v = self.send(data[count:])
  File "/usr/lib/python2.7/ssl.py", line 198, in send
    v = self._sslobj.write(data)
error: [Errno 32] Broken pipe

More details, if required:
The code is executed on a Google Cloud Compute VM and every 30 minutes. It has failed in 6 out of the last 14 runs.

Thanks for reporting!
Do you happen to know roughly how long it takes this operation takes on average?

Happy to report! It takes less than a one or two seconds.

I'm not entirely sure of the scenario but if you're streaming the data across locations then you might see this more often.
I don't see that there has been any recent issues on https://status.cloud.google.com.
I would suggest writing logic to retry on a failure like this, if I understand correctly though, it looks like this is a non-transactional so there could be duplication(although they could be removed).
@tseaver @dhermes, any ideas?

Thanks for the update. I am indeed streaming the data across locations (Asia to North America).
I am currently using the following logic, which ensures that the rows are virtually all of the time, but would be nice to have ways to make this more robust :)
inserted_successfully = False
num_tries = 0
while not inserted_successfully and num_tries < 5:
    try:
        errors = table.insert_data(ROWS)
        print 'num_errors', len(errors)
        inserted_successfully = True
    except Exception as e:
        print 'insert failed with exception: %s\ntrying again'%e
        num_tries += 1

@rishsriv It might be "safer" to pass row_ids with your rows, allowing the back-end to de-duplicate any which happen to be inserted twice.  I have logged #2492 to make that more obvious.

We should probably also look at promoting our "retry handlers" from being "private" to our system_tests/ into actual public APIs of the library.

@tseaver, could the GAPIC LRO's help here if it was implemented with GAPIC?

@daspecster nope, for two reasons:

Bigquery is a JSON-only service.
Table.insert_data does not return an LRO.

@tseaver We get retries for free with urrlib3 / requests. I prefer to just finish ditching httplib2 to fix these broken socket errors

Closing this issue as we are tracking internally as a GA requirement.


Clean Up documentation for the ItemCollection

Issue Description
The Markdown example for the ItemCollection isn't a full working example. Consumers will be copying and pasting the code to use our packages, so it's recommended to rework the MD example to be a full working ItemCollection.
Issue Type

[ ] New Feature
[] Enhancement
[ ] Bug
[ ] Other

Expected Behavior
ItemCollection example code is complete
Current Behavior
ItemCollection example has invalid tags like  and takes like  that feel incomplete.

Resolved in https://github.com/cerner/terra-clinical/pull/332


All transactions marked under /graphql. With preregisted newrelic / ts-node registrations.

Description
All transactions marked under /graphql.
When node new relic pre require @newrelic/apollo-server-plugin with
node -r newrelic -r ts-node/register  -r tsconfig-paths/register ./src/index.ts

Expected Behavior
Expected query / transaction paths to be provided based off of the incoming request.
Troubleshooting or NR Diag results
New relic is receiving requests, it just seems to not be receiving the functionality provided by plugin
Steps to Reproduce
node -r newrelic -r ts-node/register  -r tsconfig-paths/register ./src/index.ts
I believe this happens with standard config with apollo server express. I have removed all of our plugins except for newrelic apollo server. It is possible tsconfig-paths could be affecting something, will likely continue looking into it.
const newRelicPlugin = require('@newrelic/apollo-server-plugin')
import { ApolloServer, AuthenticationError } from "apollo-server-express";

plugins: [
      newRelicPlugin,
  ]

Your Environment
Node version 14.17.6
"@newrelic/apollo-server-plugin": "^1.1.0",
"apollo-server-caching": "^3",
"apollo-server-express": "^3",
"apollo-server-plugin-response-cache": "^3",

ex: Browser name and version:
ex: Node version:
ex: Operating System and version:

Additional context
Looks separate from the other issues here. Have generally tried variations of this. If I don't preregister newrelic nothing is sent, I can use ts-node similarly to the command I have above with the same issue.
I think this is different than https://github.com/newrelic/newrelic-node-apollo-server-plugin/issues/117 as I never see the paths.
I'll file a ticket through support, just incase this ends up being a me thing.

@Scong I confirmed you logged a ticket with support.  I'm going to close this but have you tried to change the -r order?
node -r ts-node/register -r tsconfig-paths/register -r newrelic ./src/index.ts


Промпты

Thank you for opening this issue! Could you please provide more details about the problem or request? Here are some pointers that would help us address it efficiently:
Description: What is the issue about?
Feel free to update the issue with the relevant details, and we’ll take a closer look as soon as possible.
Thanks!


NBMAKE INTERNAL ERROR: Exception ignored in socket

Describe the bug
I'm seeing the following error message in CI:
NBMAKE INTERNAL ERROR
Exception ignored in: <socket.socket fd=-1, family=AddressFamily.AF_UNIX, type=SocketKind.SOCK_STREAM, proto=0>

Traceback (most recent call last):
  File "/opt/hostedtoolcache/Python/3.10.6/x64/lib/python3.10/site-packages/jsonschema/exceptions.py", line 134, in _set
    for k, v in kwargs.items():
ResourceWarning: unclosed <socket.socket fd=27, family=AddressFamily.AF_UNIX, type=SocketKind.SOCK_STREAM, proto=0>

  File "/opt/hostedtoolcache/Python/3.10.6/x64/lib/python3.10/site-packages/_pytest/runner.py", line 338, in from_call
    result: Optional[TResult] = func()
  File "/opt/hostedtoolcache/Python/3.10.6/x64/lib/python3.10/site-packages/_pytest/runner.py", line [25](https://github.com/microsoft/torchgeo/runs/8172122269?check_suite_focus=true#step:5:26)9, in <lambda>
    lambda: ihook(item=item, **kwds), when=when, reraise=reraise
  File "/opt/hostedtoolcache/Python/3.10.6/x64/lib/python3.10/site-packages/pluggy/_hooks.py", line [26](https://github.com/microsoft/torchgeo/runs/8172122269?check_suite_focus=true#step:5:27)5, in __call__
    return self._hookexec(self.name, self.get_hookimpls(), kwargs, firstresult)
  File "/opt/hostedtoolcache/Python/3.10.6/x64/lib/python3.10/site-packages/pluggy/_manager.py", line 80, in _hookexec
    return self._inner_hookexec(hook_name, methods, kwargs, firstresult)
  File "/opt/hostedtoolcache/Python/3.10.6/x64/lib/python3.10/site-packages/pluggy/_callers.py", line 55, in _multicall
    gen.send(outcome)
  File "/opt/hostedtoolcache/Python/3.10.6/x64/lib/python3.10/site-packages/_pytest/unraisableexception.py", line 88, in pytest_runtest_call
    yield from unraisable_exception_runtest_hook()
  File "/opt/hostedtoolcache/Python/3.10.6/x64/lib/python3.10/site-packages/_pytest/unraisableexception.py", line 78, in unraisable_exception_runtest_hook
    warnings.warn(pytest.PytestUnraisableExceptionWarning(msg))

To Reproduce

See https://github.com/microsoft/torchgeo/runs/8172122269?check_suite_focus=true
Failing notebook is https://github.com/microsoft/torchgeo/blob/releases/v0.3/docs/tutorials/transforms.ipynb

Expected behavior
I would expect nbmake to either pass all tests, or inform me of what tests may have failed.
Desktop

OS: Ubuntu 20.04
Browser: Chrome
Version: 1.3.4

Additional context
Seems similar to #71 but the error message is slightly different.

I believe the notebook failure is correct, but the error message isn't particularly informative. Replacing %nvidia-smi with !nvidia-smi fixes the notebook on Google Colab, although it may still break in CI where there is no GPU installed. We should still fix the error message if we can.

Hi Adam,
I can't reproduce this, is it possible this was a transient error relating to some of the Ipython network components?
I have however discovered a bug: It seems like UsageErrors relating to unknown magic commands such as %nvidia-smi halt execution due to the error, yet are reported by nbmake as successful.

Unfortunately this happens every time for me consistently. I'll try to reproduce it locally.

Couldn't reproduce locally. Could be something specific to the CI environment, or could be a difference in dependency versions.

Strange. Do you know how %nvidia-smi is installed?
I tried that magic command on a colab notebook and found it didn't exist.
Are there any downsides from your workaround of using !nvidia-smi?

There is no %nvidia-smi magic command, you have to use !nvidia-smi instead. The bug isn't that %nvidia-smi doesn't exist, the bug is that nbmake fails with a mysterious error that doesn't help me locate the problem.

FWIW, still seeing this every time we try to test our notebooks: https://github.com/microsoft/torchgeo/actions/runs/4127657580/jobs/7131131990

thanks for persistently reporting this @adamjstewart
I hit a brick wall last time because I couldn't repro. Are you able to provide a docker image where we can repro this bug?

I'm also still trying to repro locally. So far it only happens for us in CI. I did notice that some of our cells timeout when run locally, so I increased the default timeout period. But I'm still seeing the issue.

is it possible this was a transient error relating to some of the Ipython network components?

Unfortunately this happens every time for me consistently.

I will clarify this and say that the error happens ~100% of the time, but the notebook that errors out keeps changing. In https://github.com/microsoft/torchgeo/pull/1097, the notebook that was failing switched from pretrained_weights.ipynb to trainers.ipynb. It could be that reproducing the issue requires running all notebooks, not just one notebook.
Also note that the error is slightly different than last time. Now we have:
NBMAKE INTERNAL ERROR
Exception ignored in: <socket.socket fd=-1, family=AddressFamily.AF_UNIX, type=SocketKind.SOCK_STREAM, proto=0>

Traceback (most recent call last):
  File "/opt/hostedtoolcache/Python/3.10.9/x64/lib/python3.10/site-packages/nbformat/__init__.py", line 166, in read
    buf = fp.read()
AttributeError: 'str' object has no attribute 'read'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/opt/hostedtoolcache/Python/3.10.9/x64/lib/python3.10/site-packages/nbformat/notebooknode.py", line 47, in from_dict
    return NotebookNode({k: from_dict(v) for k, v in d.items()})
ResourceWarning: unclosed <socket.socket fd=23, family=AddressFamily.AF_UNIX, type=SocketKind.SOCK_STREAM, proto=0>

  File "/opt/hostedtoolcache/Python/3.10.9/x64/lib/python3.10/site-packages/_pytest/runner.py", line 339, in from_call
    result: Optional[TResult] = func()
  File "/opt/hostedtoolcache/Python/3.10.9/x64/lib/python3.10/site-packages/_pytest/runner.py", line 260, in <lambda>
    lambda: ihook(item=item, **kwds), when=when, reraise=reraise
  File "/opt/hostedtoolcache/Python/3.10.9/x64/lib/python3.10/site-packages/pluggy/_hooks.py", line 265, in __call__
    return self._hookexec(self.name, self.get_hookimpls(), kwargs, firstresult)
  File "/opt/hostedtoolcache/Python/3.10.9/x64/lib/python3.10/site-packages/pluggy/_manager.py", line 80, in _hookexec
    return self._inner_hookexec(hook_name, methods, kwargs, firstresult)
  File "/opt/hostedtoolcache/Python/3.10.9/x64/lib/python3.10/site-packages/pluggy/_callers.py", line 55, in _multicall
    gen.send(outcome)
  File "/opt/hostedtoolcache/Python/3.10.9/x64/lib/python3.10/site-packages/_pytest/unraisableexception.py", line 88, in pytest_runtest_call
    yield from unraisable_exception_runtest_hook()
  File "/opt/hostedtoolcache/Python/3.10.9/x64/lib/python3.10/site-packages/_pytest/unraisableexception.py", line 78, in unraisable_exception_runtest_hook
    warnings.warn(pytest.PytestUnraisableExceptionWarning(msg))

Unfortunately I don't know how to get a full stacktrace so I can't know what this str object is or why it isn't a filehandle.

This is interesting. The error points to an AttributeError triggered here. However, this should be caught by the following line. I'm not sure why it isn't being caught.

@adamjstewart, would you be interested in containerising this test process?
I reckon either (a) this issue would stop happening, or (b) We would be able to repro in vscode and root cause it
We could make your PR (https://github.com/microsoft/torchgeo/pull/1097) use the same pattern as this repo's tests

Tried copying that pattern but I must have done something wrong because the devcontainer isn't launching properly. I stole the devcontainer recipe from https://github.com/microsoft/torchgeo/pull/1085 but I've never used vscode before so I have no idea if it's correct.

I've done some investigation in a codespaces instance that runs the same container that I've put in the CI branch.
I believe we have two issues:

For some reason (probably memory or storage exhaustion -- github ci specs) the ipykernel dies when executing the notebooks
When the kernel dies, nbmake throws an internal error (rather than handling and reporting it).

If I fix the latter issue then the error messages should get easier to parse, although having seen the logs when running in VSCode (codespaces), it still isn't clear why the kernel is dying.

How would I go about debugging this? Is there an easy way to tell which step of the notebook is failing? Not sure if print statements + pytest -s work with notebooks or not.

Discovered something interesting. In https://github.com/microsoft/torchgeo/pull/1124, we finally got our notebook tests passing for the first time in a year by using smaller downloads. However, if you compare https://github.com/microsoft/torchgeo/pull/1124/commits/aadd19992a9e0d258f3f47a0f24ecdf7b6a4b389 and https://github.com/microsoft/torchgeo/pull/1124/commits/77b4e0b1ac7bdc062cb25e3f1feb9a5ffeb6e61e, you'll see that the tests were failing and I fixed them simply by clearing the output of the notebook. Is there any reason why the output would cause an internal error? That was quite a surprise to me.

Things were working great, but now all of a sudden I'm seeing this error again: https://github.com/microsoft/torchgeo/actions/runs/4456067450/jobs/7826269250?pr=1124
I tried nbstripout on all notebooks, but that didn't help. I'm not sure what changed, but the error message isn't helpful. Is there any way to enable more verbose logging or other debugging tips you have?

Thanks, let me try that. I agree that the issue is transient, which suggests that it's still a hardware issue, but I can't figure out what could possibly be wrong...

Sorry for context: I’m wondering how this all runs on your interactive dev
environment to get a sense of how the ci agent differs (which is the root
of the challenge here IMO)
On Tue, 21 Mar 2023 at 15:34, Adam J. Stewart @.***>
wrote:

This is using GitHub Actions, see here
https://github.com/microsoft/torchgeo/blob/main/.github/workflows/tutorials.yaml
for the configuration.
—
Reply to this email directly, view it on GitHub
https://github.com/treebeardtech/nbmake/issues/80#issuecomment-1478057926,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANZJM7OZRBDCR4Y44XB2663W5HDB7ANCNFSM6AAAAAAQEB25TE
.
You are receiving this because you commented.Message ID:
@.***>

--
Alex Remedios

Oh for sure, my laptop is much more powerful. But I think our notebooks are using a very small amount of resources now, although it's hard to be sure. Hopefully a better error message will reveal what's really going on. If there was an OOM or hard drive full error that would make things obvious.

We got things working for a while by rerunning the tests up to 10x until they passed, but that no longer seems to be working. See https://github.com/microsoft/torchgeo/pull/1521 for the newest error messages. As far as I know, nothing changed about the available GitHub runners. And the failing tutorial hasn't changed in years. Did anything change in nbmake? Any debugging suggestions?

I think the issue was with one of our tutorials. Once we removed that tutorial in https://github.com/microsoft/torchgeo/pull/1521 everything passes without needing any reruns! I'll close this for now because I never liked that tutorial anyway, but I'll reopen if something similar happens again in the future.


Consider Bind

Just jumped in here for a few seconds to check things out. You may want to consider using the bind callback a bit more on your components, rather than the attached callback. For example, see here: https://github.com/aurelia-ui-toolkits/aurelia-kendoui-plugin/blob/master/src/button/button.js#L25  Could this logic be moved out of attached and into bind?
Basically, bind happens before the component is attached to the real DOM, but you do have access to your own HTML Element and all properties on your component have their bound values. So, unless the Kendo component is relying on being in the document, you may be able to optimize in this way. It may vary depending on the Kendo widget. I don't know Kendo at all, but I wanted to drop a note here so that you all investigate this option because, if it works, it will result in better performance and user experience.

Thanks for the optimization hint - knowing your workload this is very appreciated and will be used :-)

No guarantees that it will work with Kendo, but I would try it out for each widget and see. Even if it only works for some, it will improve those implementations.

On Dec 1, 2015, at 10:44 AM, Nikolaj Ivancic<EMAIL_ADDRESS>wrote:
Thanks for the optimization hint - knowing your workload this is very appreciated and will be used :-)
—
Reply to this email directly or view it on GitHub
.

You mean to move this code from attached into the constructor, right?

@adriatic this line could possibly work inside the bind callback, instead of the attached callback in which it is now

Oh, well - I am showing my poor Aurelia vocabulary as I never knew that bind is a callback (I saw it only in the context of declarative code in HTML)

@adriatic I have just tested this with the sample app inside the plugin, and it works just fine for the controls we currently have. I have also updated the documentation in the wiki's


Add sslserver bindings with ecccurve and sslcipher

@jovandeginste Thanks for your contribution! This is an amazing PR!
Before we can merge this, it would be appreciated if you could add acceptance tests for these new types and providers. They are in the spec/acceptance directory and shouldn't be very difficult to add new ones based on the old ones.
Thanks!

@hunner Just wanted to ping you to show you this epic PR :D

@jonnytpuppet if only I knew how:
After installing the gems (bundle install), I get:
$ rake beaker                # Run beaker acceptance tests

Result:
$HOME/.rvm/rubies/ruby-2.1.5/bin/ruby -I$HOME/.rvm/gems/ruby-2.1.5<EMAIL_ADDRESS><EMAIL_ADDRESS>spec/acceptance --color
$HOME/.rvm/gems/ruby-2.1.5@puppet-netscaler/gems/beaker-rspec-5.3.0/lib/beaker-rspec/helpers/serverspec.rb:43: warning: already initialized constant Module::VALID_OPTIONS_KEYS
$HOME/.rvm/gems/ruby-2.1.5@puppet-netscaler/gems/specinfra-2.57.2/lib/specinfra/configuration.rb:4: warning: previous definition of VALID_OPTIONS_KEYS was here
Hypervisor for puppet is ec2
Hypervisor for netscaler is ec2
Beaker::Hypervisor, found some ec2 boxes to create
$HOME/.rvm/rubies/ruby-2.1.5/lib/ruby/2.1.0/psych.rb:464:in `initialize': No such file or directory @ rb_sysopen - $HOME/.fog (Errno::ENOENT)

@jovandeginste
If you can just create a new file in spec/acceptance based on one of the other tests, I can run it here for you.
Cheers

closing due to inactivity


removed max balance and implemented handler for transaction fail

Please change the error message
'The final transaction was failed as lack of ETH amount. Please arrange amount of Eth.'
to the following"
'Your transaction failed due to insufficient ETH balance in your wallet. Please add more ETH and try again.'

Updated error message as your requirement


try add es6-promise

continue #91

es6-promise doesn't follow ES Shim. It uses es6-promise/auto, require('es6-promsie'). polyfill() and require('es6-promsie'). Promise。

Different dev 😸 . Certainly helps to have a standard way to interface with shims.

I guess besides single file / ES Shim , we need another format.

I guess besides single file / ES Shim , we need another format.

We have manual format.

not sure whether this works.


Mztab UPD

This branch implements changes necessary for successful mzTab-M export and support. It is updated in compatibility with the new architecture and contains minor updates (compared to the previous PR) regarding data types export.

looks good to me. But only read through quickly. What do you think @SteffenHeu

Does not work.
[Error-1001] line 380: The number of Data line items is "19", whereas the number of header line items count is "23". They MUST be the same.
2024-06-25 16:48:05 SEVERE uk.ac.ebi.pride.jmztab2.utils.parser.MZTabDataLineParser checkCount
Items given: [SML, 352, 352, null, null, null, null, null, null, null, null, 4, [, , NaN, ], 1000.0, 10572.46484375, null, null, 129.054584, 60.036892,<PHONE_NUMBER>5]
expected:    [SML, 352, 352, null, null, null, null, null, null, null, null, 4, [, , NaN, ], 1000.0, 10572.46484375, , null, null, , , , 129.054584, 60.036892,<PHONE_NUMBER>5]

I am trying to integrate the requested changes in this branch (which is a clone of Olena's repo branch): https://github.com/nilshoffmann/mzmine/tree/mztab-mvc


ignoreAnnotated config doesn't work on FunctionNaming rule

Expected Behavior
Being able to suppress FunctionNaming rule on functions annotated with @Composable
Observed Behavior
All @Composable function names reported as violations
Steps to Reproduce
Run detekt 1.19.0-RC1 analysis on a project with Composable functions
Context
It seems that naming rules are all run through one MulitRule: NamingRules which is not ConfigAware so getSuppressors returns empty list
Your Environment

Version of detekt used: 1.19.0-RC-1

🤦 MultiRule beats again. i didn't have the time to check this but I think that you are completely right. I didn't thought about MultiRules while I was implementing this.


[LibSquoosh] URL invalid

Describe the bug
Use the github action to compress images. It's says can'tt find the wasm files. But there is in repo.
git clone 'https://github.com/SettingDust/image-compress-action' # ref=main
docker cp src=/home/runner/.cache/act/SettingDust-image-compress-action@main dst=/actions/
TypeError [ERR_INVALID_URL]: Invalid URL<EMAIL_ADDRESS>    at onParseError (internal/url.js:259:9)
    at new URL (internal/url.js:335:5)
    at Object.7275 (/actions/SettingDust-image-compress-action@main/webpack:/image-compress-action/node_modules/@squoosh/lib/build/index.js:1:1)
    at __nccwpck_require__ (/actions/SettingDust-image-compress-action@main/webpack:/image-compress-action/webpack/bootstrap:21:1)
    at Object.3109 (/actions/SettingDust-image-compress-action@main/webpack:/image-compress-action/lib/main.js:37:1)
    at __nccwpck_require__ (/actions/SettingDust-image-compress-action@main/webpack:/image-compress-action/webpack/bootstrap:21:1)
    at /actions/SettingDust-image-compress-action@main/webpack:/image-compress-action/webpack/startup:4:1
    at Object.<anonymous> (/actions/SettingDust-image-compress-action@main/dist/index.js:12521:12)
    at Module._compile (internal/modules/cjs/loader.js:1063:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1092:10)
Error: exit with `FAILURE`: 1

Expected behavior
Compress
Version:

OS w/ version: ubuntu-18.04 in docker. Host is ubuntu-20.04 in docker.
Node version: May be 14.17.0. There isn't detail in action log.
npm version: May be 6.14.13.

Can you add how you are invoking the CLI? Your error log is not showing that.

Can you give me a reproduction case then? The error gives me very little to go on, sadly.

Can you give me a reproduction case then? The error gives me very little to go on, sadly.

Gotcha. It's caused by ncc
https://github.com/SettingDust/squoosh-test
After I add the ncc to compile the project, the error appearing.
TypeError [ERR_INVALID_URL]: Invalid URL: /home/runner/work/squoosh-test/squoosh-test/dist/mozjpeg_node_enc-13aa762d.wasm
    at onParseError (internal/url.js:259:9)
    at new URL (internal/url.js:335:5)
    at Object.275 (/home/runner/work/squoosh-test/squoosh-test/webpack:/squoosh-test/node_modules/@squoosh/lib/build/index.js:1:1)
    at __nccwpck_require__ (/home/runner/work/squoosh-test/squoosh-test/webpack:/squoosh-test/webpack/bootstrap:21:1)
    at /home/runner/work/squoosh-test/squoosh-test/webpack:/squoosh-test/index.js:1:1
    at /home/runner/work/squoosh-test/squoosh-test/dist/index.js:4178:3
    at Object.<anonymous> (/home/runner/work/squoosh-test/squoosh-test/dist/index.js:4181:12)
    at Module._compile (internal/modules/cjs/loader.js:1068:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1097:10)
    at Module.load (internal/modules/cjs/loader.js:933:32)

I just published @squoosh/lib v0.3.0 which fixes a lot of things. Can you try again with this new version?

Same
TypeError [ERR_INVALID_URL]: Invalid URL: /home/runner/work/squoosh-test/squoosh-test/dist/mozjpeg_node_enc-ec78f622.wasm
    at onParseError (internal/url.js:259:9)
    at new URL (internal/url.js:335:5)
    at Object.275 (/home/runner/work/squoosh-test/squoosh-test/webpack:/squoosh-test/node_modules/@squoosh/lib/build/index.js:1:1)
    at __nccwpck_require__ (/home/runner/work/squoosh-test/squoosh-test/webpack:/squoosh-test/webpack/bootstrap:21:1)
    at /home/runner/work/squoosh-test/squoosh-test/webpack:/squoosh-test/index.js:1:1
    at /home/runner/work/squoosh-test/squoosh-test/dist/index.js:4178:3
    at Object.<anonymous> (/home/runner/work/squoosh-test/squoosh-test/dist/index.js:4181:12)
    at Module._compile (internal/modules/cjs/loader.js:1068:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1097:10)
    at Module.load (internal/modules/cjs/loader.js:933:32)

Same here using 0.4.0:
1:13:37 PM: throw new TypeError("Failed to parse URL from " + input, { cause: err });
1:13:37 PM: ^
1:13:37 PM: TypeError: Failed to parse URL from<EMAIL_ADDRESS>1:13:37 PM: at new Request (node:internal/deps/undici/undici:4813:19)
1:13:37 PM: at Agent.fetch2 (node:internal/deps/undici/undici:5539:29)
1:13:37 PM: ... 4 lines matching cause stack trace ...
1:13:37 PM: at /opt/build/repo/node_modules/@squoosh/lib/build/index.js:28:35216
1:13:37 PM: at instantiateEmscriptenWasm (/opt/build/repo/node_modules/@squoosh/lib/build/index.js:1:466)
1:13:37 PM: at Object.<anonymous> (/opt/build/repo/node_modules/@squoosh/lib/build/index.js:30:323)
1:13:37 PM: at Module._compile (node:internal/modules/cjs/loader:1105:14) {
1:13:37 PM: [cause]: TypeError [ERR_INVALID_URL]: Invalid URL
1:13:37 PM: at new NodeError (node:internal/errors:377:5)
1:13:37 PM: at URL.onParseError (node:internal/url:563:9)
1:13:37 PM: at new URL (node:internal/url:643:5)
1:13:37 PM: at new Request (node:internal/deps/undici/undici:4811:25)
1:13:37 PM: at Agent.fetch2 (node:internal/deps/undici/undici:5539:29)
1:13:37 PM: at Object.fetch (node:internal/deps/undici/undici:6370:20)
1:13:37 PM: at fetch (node:internal/bootstrap/pre_execution:196:25)
1:13:37 PM: at instantiateAsync (/opt/build/repo/node_modules/@squoosh/lib/build/index.js:28:11469)
1:13:37 PM: at createWasm

Same as above, file<EMAIL_ADDRESS>exists..
Any hints or pointers would be very appreciated.

Suddenly seeing this upon building a project that was last worked on 2 weeks ago. The only thing that has changed for me was node 18 being upgraded to a newer version, so perhaps that's the root cause.

The only thing that has changed for me was node 18 being upgraded to a newer version, so perhaps that's the root cause.

Forr anyone running into the same problem: Temporarily downgrading to node >=v16 when using<EMAIL_ADDRESS>is a successful workaround. Thank you :muscle:

Status: Same problem :pensive:
1. Environment

Microsoft Windows [Version 10.0.19041.1415]
Node.js v18.7.0
<EMAIL_ADDRESS><EMAIL_ADDRESS>
2. Console output
D:\SashaDebugging\KiraSquooshImages>npm i -g @squoosh/cli
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '<EMAIL_ADDRESS>npm WARN EBADENGINE   required: { node: ' ^12.20.2 || ^14.13.1 || ^16.0.0 ' },
npm WARN EBADENGINE   current: { node: 'v18.7.0', npm: '8.16.0' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '<EMAIL_ADDRESS>npm WARN EBADENGINE   required: { node: ' ^12.5.0 || ^14.0.0 || ^16.0.0 ' },
npm WARN EBADENGINE   current: { node: 'v18.7.0', npm: '8.16.0' }
npm WARN EBADENGINE }

added 37 packages, and audited 38 packages in 9s

11 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities

D:\SashaDebugging\KiraSquooshImages>squoosh-cli --help
Usage: squoosh-cli [options] <files...>

Options:
  -d, --output-dir <dir>                                 Output directory (default: ".")
  -s, --suffix <suffix>                                  Append suffix to output files (default: "")
  --max-optimizer-rounds <rounds>                        Maximum number of compressions to use for auto optimizations (default: "6")
  --optimizer-butteraugli-target <butteraugli distance>  Target Butteraugli distance for auto optimizer (default: "1.4")
  --resize [config]                                      Resize the image before compressing
  --quant [config]                                       Reduce the number of colors used (aka. paletting)
  --rotate [config]                                      Rotate image
  --mozjpeg [config]                                     Use MozJPEG to generate a .jpg file with the given configuration
  --webp [config]                                        Use WebP to generate a .webp file with the given configuration
  --avif [config]                                        Use AVIF to generate a .avif file with the given configuration
  --jxl [config]                                         Use JPEG-XL to generate a .jxl file with the given configuration
  --wp2 [config]                                         Use WebP2 to generate a .wp2 file with the given configuration
  --oxipng [config]                                      Use OxiPNG to generate a .png file with the given configuration
  -h, --help                                             display help for command

D:\SashaDebugging\KiraSquooshImages>squoosh-cli "KiraTestImage.jpg"
node:internal/deps/undici/undici:6277
          p.reject(Object.assign(new TypeError("fetch failed"), { cause: response.error }));
                                 ^

TypeError: fetch failed
    at Object.processResponse (node:internal/deps/undici/undici:6277:34)
    at node:internal/deps/undici/undici:6602:42
    at node:internal/process/task_queues:140:7
    at AsyncResource.runInAsyncScope (node:async_hooks:203:9)
    at AsyncResource.runMicrotask (node:internal/process/task_queues:137:8) {
  cause: Error: unknown scheme
      at makeNetworkError (node:internal/deps/undici/undici:5251:51)
      at schemeFetch (node:internal/deps/undici/undici:6578:18)
      at node:internal/deps/undici/undici:6434:26
      at mainFetch (node:internal/deps/undici/undici:6451:11)
      at fetching (node:internal/deps/undici/undici:6408:7)
      at Agent.fetch2 (node:internal/deps/undici/undici:6288:20)
      at Object.fetch (node:internal/deps/undici/undici:7076:20)
      at fetch (node:internal/bootstrap/pre_execution:199:25)
      at instantiateAsync (C:\Program Files\nodejs\node_modules\@squoosh\cli\node_modules\@squoosh\lib\build\index.js:28:11469)
      at createWasm (C:\Program Files\nodejs\node_modules\@squoosh\cli\node_modules\@squoosh\lib\build\index.js:28:12079) {
    [cause]: undefined
  }
}

Node.js v18.7.0

I get the same result for different images in different formats.
Thanks.

Unfortunately, due to a few people leaving the team, and staffing issues resulting from the current economic climate (ugh), the CLI and libsquoosh packages are no longer actively maintained. I know that sucks, but there simply isn't the time & people to work on this. If anyone from the community wants to fork it, you have my blessing. The squoosh.app web app will continue to be supported and improved.

same error TypeError: fetch failed cause: Error: unknown scheme
when using @squoosh/lib v0.4.0 and nodejs v18.10.0
fixed by running nodejs with the flag --no-experimental-fetch

To make it work with the CLI, you can pass the flag using environment variables.
export NODE_OPTIONS='--no-experimental-fetch'

squoosh-cli \
  --resize '{"enabled":true,"width":560,"height":560,"method":"lanczos3","fitMethod":"stretch","premultiply":true,"linearRGB":true}'  \
  --webp '{"quality":90,"target_size":0,"target_PSNR":0,"method":6,"sns_strength":50,"filter_strength":60,"filter_sharpness":0,"filter_type":1,"partitions":0,"segments":4,"pass":1,"show_compressed":0,"preprocessing":0,"autofilter":0,"partition_limit":0,"alpha_compression":1,"alpha_filtering":1,"alpha_quality":100,"lossless":0,"exact":0,"image_hint":0,"emulate_jpeg_size":0,"thread_level":0,"low_memory":0,"near_lossless":100,"use_delta_palette":0,"use_sharp_yuv":0}' \
  -d compressed/ \
  source/1105.jpg


Add a quick start with both UPSERT and JSON index

Codecov Report

Merging #7669 (097bfe2) into master (b2add14) will decrease coverage by 42.99%.
The diff coverage is 0.00%.

@@              Coverage Diff              @@
##             master    #7669       +/-   ##
=============================================
- Coverage     70.60%   27.60%   -43.00%
=============================================
  Files          1578     1569        -9
  Lines         80248    79901      -347
  Branches      11914    11876       -38
=============================================
- Hits          56662    22060    -34602
- Misses        19721    55848    +36127
+ Partials       3865     1993     -1872

Flag
Coverage Δ

integration1
?

integration2
27.60% <0.00%> (?)

unittests1
?

unittests2
?

Flags with carried forward coverage won't be shown. Click here to find out more.

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


PDF Print in Shrink Format

Attach (recommended) or Link to PDF file here: Sorry it is not a github project and internal to organization. Hence could not share the link to PDF file.
Configuration:

PDF.js Version: Version 2 - From build pdfjs-1.8.188-dist.zip
Web browser and its version:  IE 11, Chrome, Firefox
Operating system and its version: Windows 7, Windows 10
Is a browser extension: No

Steps to reproduce the problem:

We are using PDF.js plugin for our application to print any PDFs. Our customers reported that while they are preview the file before printing, they are not able to preview all the pages. Only first half portion of the first page is been previewed and while printing also only half page is getting printed. So we have upgraded our PDF.js build, web folders and since then we are having preview issue only in IE but not in Chrome or Mozilla. Also other main issue is when the user printing the PDF they are getting the pdf page printed in a shrinked way. Please let us know if there are any existing issues like this and provide your inputs in fixing the issue and let us know if you need more information on it.

What is the expected behavior? User should be able to preview all the pages and should print all the pages in a page-fit format without any shrink.
What went wrong? While printing the PDF using viewer.html the page getting printed in a shrink format. Means the whole page is getting printed in the top left portion of the paper and the remaining areas are blank

Can you reproduce the same issue with http://mozilla.github.io/pdf.js/web/viewer.html ? If not, the problem most likely with your proprietary solution, and we cannot assist with something we cannot observe.

When i browse with  http://mozilla.github.io/pdf.js/web/viewer.html, the internet explorer did not load all the pages while doing a Print Preview. Please see the file attached. Out of 14 pages, it just shows only 2 pages. Also when i tried in Chrome to preview it closes the tab itself which it did not happen for our PDFs in Chrome. Please let us know your inputs.

Could you please provide your suggestion on the above issue?

Will there be any suggestion or solution for the above problem i am facing while printing the PDF?

Printing is not really supported well across browsers. In the web viewer we pre-render all pages before sending it to the print preview, but if you use the print button, we cannot always do that, which is what you see. This is, more often than not, a browser limitation that we have to work around. For now there is not much we can do in the short term I think.

Thanks for your inputs Tim. But in IE when we Print the PDF using the Print option in WebViewer.html the page is getting printed in a shrink way. Mean the whole page is getting printed but in the upper left side of the Paper.  Please find the attachment and suggest us a solution. This is happening after we upgrade our PDF.js Version as: Version 2 - From build pdfjs-1.8.188-dist.zip
Print.pdf

Facing some issues while previewing the PDF using pdf.js on Edge and Firefox. On both these browsers if the content of lets say the first page is large it moves to the second page along with the footer and so on. Here is the behavior.

Another issue is that a blank page is printed at the end.

Works fine on Chrome and IE11.

Closing since the issues mentioned here are either fixed now or cannot be fixed because the browser (IE) is now officially unsupported by PDF.js.


WIP: doc: add metrics_reference page to provide detailed description of ea…

…ch metric

Reworked in #155, #154, #157, #159


[Examples] Provides an example for Rimo

Description
This PR provides a real-world example to Rimo usage.

:tada: This PR is included in version 1.2.4 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


fix "less obvious" in countable quantities regex

The rule won't match "less" followed by any word ending in "ous" now.


The icons aren't right.

Patched https://github.com/agarick/agave/ using the patcher. The icons look like following,

I used fontforge -script font-patcher -w -c ../Agave-Regular.ttf. I am using alacritty terminal with wsl2 windows 10.
It doesn't look right how to fix it?

@aasutossh please address this issue upstream as this repository is just a mirror of the font-patcher files of https://github.com/ryanoasis/nerd-fonts