TextSelector overlay isn't hidden when selected text exits viewport

Steps to Reproduce

minimal reproducible example:
void main() {
  runApp(MyHomePage());
}

class MyHomePage extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter test',
      theme: ThemeData(
        primarySwatch: Colors.blue,
        primaryColor: Colors.green[900],
      ),
      home: Scaffold(
        appBar: AppBar(
          title: Text("Flutter test"),
        ),
        body: Container(
          color: Colors.grey,
          constraints: BoxConstraints(
            maxHeight: 200
          ),
          child: SingleChildScrollView(
            child: Padding(
              padding: const EdgeInsets.all(8.0),
              child: Column(
                children: [
                  SelectableText(
                    "test1\ntest2\ntest3\ntest4\ntest5\ntest6\ntest7\ntest8\ntest9\ntest10\ntest11\ntest12\ntest13\ntest14\ntest15\ntest16",
                  ),
                  Divider(),
                  SelectableText(
                    "test1\ntest2\ntest3\ntest4\ntest5\ntest6\ntest7\ntest8\ntest9\ntest10\ntest11\ntest12\ntest13\ntest14\ntest15\ntest16",
                  ),
                  Divider(),
                  SelectableText(
                    "test1\ntest2\ntest3\ntest4\ntest5\ntest6\ntest7\ntest8\ntest9\ntest10\ntest11\ntest12\ntest13\ntest14\ntest15\ntest16",
                  )
                ]
              ),
            )
          ),
        )
      )
    );
  }
}

build example below.
Select any text.
Scroll up or down until edge of container.

Expected results: The text selection should be hidden when it is out of container
Actual results:  The text selection is shown even it is out of container, and stacked in front of other widgets

flutter doctor -v
[✓] Flutter (Channel stable, 2.2.3, on Linux, locale en_US.UTF-8)
    • Flutter version 2.2.3 at /home/jay/Documents/flutter_linux_2.0.3-stable/flutter
    • Framework revision f4abaa0735 (10 weeks ago), 2021-07-01 12:46:11 -0700
    • Engine revision 241c87ad80
    • Dart version 2.13.4

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at /home/jay/Android/Sdk
    • Platform android-30, build-tools 30.0.3
    • Java binary at: /usr/local/android-studio/jre/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)
    • All Android licenses accepted.

[✓] Chrome - develop for the web
    • Chrome at google-chrome

[✓] Android Studio (version 4.1)
    • Android Studio at /usr/local/android-studio
    • Flutter plugin version 55.0.1
    • Dart plugin version 201.9335
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)

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

[✓] Connected device (2 available)
    • sdk gphone x86 arm (mobile) • emulator-5554 • android-x86    • Android 11 (API 30) (emulator)
    • Chrome (web)                • chrome        • web-javascript • Google Chrome 91.0.4472.114

Issue is reproducible on master and stable.
See below for comparisons between native and flutter

native and flutter reproduction
https://user-images.githubusercontent.com/88313112/132323730-7f8352f4-ff86-4b67-b255-fe7b8d7940cc.MP4
https://user-images.githubusercontent.com/88313112/132323356-2b694e78-b8fa-4b3f-9e18-7fcd531809e7.MP4
https://user-images.githubusercontent.com/88313112/132323219-d9a6d332-0b93-465f-b510-9c490f04afae.mp4
https://user-images.githubusercontent.com/88313112/132323267-04810647-0208-44e3-a3f1-10b7e485a125.mp4

flutter doctor -v
[✓] Flutter (Channel master, 2.6.0-1.0.pre.193, on macOS 11.5.1 20G80
    darwin-arm, locale en-GB)
    • Flutter version 2.6.0-1.0.pre.193 at /Users/nexus/dev/sdks/flutters
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 0c5431d99c (31 hours ago), 2021-09-05 22:31:02 -0400
    • Engine revision b9c633900e
    • Dart version 2.15.0 (build 2.15.0-82.0.dev)

[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at /Users/nexus/Library/Android/sdk
    • Platform android-31, build-tools 31.0.0
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7249189)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 12.5.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • CocoaPods version 1.11.0

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2020.3)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7249189)

[✓] VS Code (version 1.60.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.26.0

[✓] Connected device (3 available)
    • Nexus’ IPhone (mobile) • 00008020-001875E83A38002E • ios            • iOS
      14.7.1 18G82
    • macOS (desktop)        • macos                     • darwin-arm64   •
      macOS 11.5.1 20G80 darwin-arm
    • Chrome (web)           • chrome                    • web-javascript •
      Google Chrome 93.0.4577.63

• No issues found!

[✓] Flutter (Channel stable, 2.2.3, on macOS 11.5.1 20G80 darwin-arm, locale
    en-GB)
    • Flutter version 2.2.3 at /Users/nexus/dev/sdks/flutter
    • Framework revision f4abaa0735 (10 weeks ago), 2021-07-01 12:46:11 -0700
    • Engine revision 241c87ad80
    • Dart version 2.13.4

[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at /Users/nexus/Library/Android/sdk
    • Platform android-31, build-tools 31.0.0
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7249189)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.5.1, Build version 12E507
    • CocoaPods version 1.11.0

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2020.3)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7249189)

[✓] VS Code (version 1.60.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.26.0

[✓] Connected device (3 available)
    • Nexus’ IPhone (mobile) • 00008020-001875E83A38002E • ios            • iOS
      14.7.1
    • macOS (desktop)        • macos                     • darwin-arm64   •
      macOS 11.5.1 20G80 darwin-arm
    • Chrome (web)           • chrome                    • web-javascript •
      Google Chrome 93.0.4577.63

• No issues found!

Looks like similar issues had happened and had been fixed in earlier version?
#77889
#55547

CC @chunhtai

Any update about this issue?  I have the same problem

Any update?

I think this issue can be solved once https://github.com/flutter/flutter/issues/52425 landed (Text selection menu should fade during scroll).

It looks like this is the same issue as #13182, so let's consolidate discussion on that thread.

I think this issue can be solved once #52425 landed (Text selection menu should fade during scroll).

From looking at the "Native Android" video on that issue (showing desired behavior), even once that issue is fixed it looks like we'd still expect the selection handles at each end of the selection to remain visible when scrolling. So this issue would get a bit milder — the text selection menu with "Copy" and so on would disappear on scroll and so wouldn't typically have this symptom — but would still be present because the selection handles would be unaffected.


[tool_crash] SocketException: Send failed, OS Error: No route to host, errno = 65

Command
flutter --no-color run --machine --track-widget-creation --device-id=00008110-000224DC0E46401E --start-paused --dart-define=flutter.inspector.structuredErrors=true lib/main.dart

Steps to Reproduce

...
...
...

Logs
SocketException: Send failed, OS Error: No route to host, errno = 65
#0      _NativeSocket.send (dart:io-patch/socket_patch.dart:1275:34)
#1      _RawDatagramSocket.send (dart:io-patch/socket_patch.dart:2590:15)
#2      MDnsClient.lookup (package:multicast_dns/multicast_dns.dart:219:22)
#3      MDnsVmServiceDiscovery._pollingVmService (package:flutter_tools/src/mdns_discovery.dart:232:66)
<asynchronous suspension>
#4      MDnsVmServiceDiscovery.firstMatchingVmService (package:flutter_tools/src/mdns_discovery.dart:188:56)
<asynchronous suspension>
#5      MDnsVmServiceDiscovery.getVMServiceUriForLaunch (package:flutter_tools/src/mdns_discovery.dart:433:50)
<asynchronous suspension>
#6      Future.any.onValue (dart:async/future.dart:628:5)
<asynchronous suspension>

[✓] Flutter (Channel stable, 3.24.3, on macOS 15.0 24A335 darwin-arm64, locale zh-Hans-CN)
    • Flutter version 3.24.3 on channel stable at /Users/yuanziqiang/development/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 2663184aa7 (9 days ago), 2024-09-11 16:27:48 -0500
    • Engine revision 36335019a8
    • Dart version 3.5.3
    • DevTools version 2.37.3

[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    • Android SDK at /Users/yuanziqiang/Library/Android/sdk
    • Platform android-34, build-tools 34.0.0
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.11+0-17.0.11b1207.24-11852314)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 16.0)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 16A242d
    • CocoaPods version 1.15.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2024.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.11+0-17.0.11b1207.24-11852314)

[✓] VS Code (version 1.93.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.96.0

[✓] Connected device (4 available)
    • 袁子强的iPhone (mobile)             • 00008110-000224DC0E46401E • ios            • iOS 18.0 22A3354
    • macOS (desktop)                 • macos                     • darwin-arm64   • macOS 15.0 24A335 darwin-arm64
    • Mac Designed for iPad (desktop) • mac-designed-for-ipad     • darwin         • macOS 15.0 24A335 darwin-arm64
    • Chrome (web)                    • chrome                    • web-javascript • Google Chrome 128.0.6613.139

[!]  Doctor found issues in 1 category.

Flutter Application Metadata
Type: app
Version: 1.0.0+1
Material: true
Android X: false
Module: false
Plugin: false
Android package: null
iOS bundle identifier: null
Creation channel: stable
Creation framework version: 2e9cb0aa71a386a91f73f7088d115c0d96654829
Plugins
device_info_plus-10.1.2
emoji_picker_flutter-3.0.0
file_selector_linux-0.9.2+1
file_selector_macos-0.9.4
file_selector_windows-0.9.3+2
flutter_keyboard_visibility-6.0.0
flutter_keyboard_visibility_linux-1.0.0
flutter_keyboard_visibility_macos-1.0.0
flutter_keyboard_visibility_web-2.0.0
flutter_keyboard_visibility_windows-1.0.0
flutter_plugin_android_lifecycle-2.0.22
image_picker-1.1.2
image_picker_android-0.8.12+13
image_picker_for_web-3.0.5
image_picker_ios-0.8.12
image_picker_linux-0.2.1+1
image_picker_macos-0.2.1+1
image_picker_windows-0.2.1+1
package_info_plus-8.0.2
path_provider-2.1.4
path_provider_android-2.2.10
path_provider_foundation-2.4.0
path_provider_linux-2.2.1
path_provider_windows-2.3.0
quill_native_bridge-10.6.5
screen_brightness-1.0.1
screen_brightness_android-1.0.1
screen_brightness_ios-1.0.1
screen_brightness_macos-1.0.1
screen_brightness_windows-1.0.1
share_plus-10.0.2
shared_preferences-2.3.2
shared_preferences_android-2.3.2
shared_preferences_foundation-2.5.2
shared_preferences_linux-2.4.1
shared_preferences_web-2.4.2
shared_preferences_windows-2.4.1
url_launcher-6.3.0
url_launcher_android-6.3.10
url_launcher_ios-6.3.1
url_launcher_linux-3.2.0
url_launcher_macos-3.2.0
url_launcher_web-2.3.3
url_launcher_windows-3.1.2
webview_flutter-4.9.0
webview_flutter_android-3.16.7
webview_flutter_wkwebview-3.15.0

Closing this as a duplicate of https://github.com/flutter/flutter/issues/150131


Do not handle inline assembly with "intel" flag as AT&T syntax

LLVM understands this parameter and Crystal's parser also supports the "intel" attribute for Asm nodes, yet actually using the Intel syntax in the template string will produce a codegen error. This PR fixes that, and the emitted LLVM IR will now include the inteldialect option, e.g. call void asm inteldialect "mov dword ptr [$0], 42", "r"(ptr %x).
LLVM's own inline assembler should understand Intel syntax as long as it targets x86. This has nothing to do with whether --emit=asm writes the compiled assembly back using Intel syntax.

suggestion: It might be more future proof for the method parameter to receive an instance of LibLLVM::InlineAsmDialect. Then intel_dialect: true would be come dialect: :intel and if there's ever another dialect added, it would work the same way.


Apply Sphinx inline directives (file, kbd, Python domain, etc.)

This works toward making the docs more explicit and more amenable to
precise and consistent formatting.
I also fixed some typos, added some punctuation, capitalised some
acronyms, etc.
In some cases I left literal markup, where I couldn't decide what
kind of thing we were looking at. E.g. is a YAML "file" in a Rapido
app a file if it only lives in the ZODB? (I think it probably is.)
For changing Python "distribution" to "package", see
https://packaging.python.org/glossary/#term-distribution-package

I'm seeing some weird duplicate label warnings (the "other" file is the source file):
mastering_plone/configuring_customizing.rst:4: WARNING: duplicate label customizing-label, other instance in /home/jean/repos/git/training/mastering_plone/configuring_customizing.rst
There are also warnings about unknown options, I think that's OK (ref).
/home/john/repos/git/training/mastering_plone/buildout_1.rst:321: WARNING: unknown option: -v

/home/jean/repos/git/training/mastering_plone/restapi.rst:66: WARNING: Pygments lexer name u'http-request' is not known
I think that's OK, it'll encourage us to look for such a lexer.

@jean please rebase. Would you mind using branches instead of forks for future changes? Building forks locally simply adds barriers and additional steps that I'm often to lazy to do.

Never mind fixed it locally and merged it.

@pbauer thanks!
I used a branch in my fork .. I didn't realise that a PR from a fork adds effort.
I'll switch to using branches in the origin repo.


nixos/hedgedoc: Do not set StateDirectory to an absolute path

Commit 8109d8a set the StateDirectory= option to the value of  cfg.workDir. This is wrong, according to dasJ and can indeed be seen in the logs:
Jun 13 14:49:21 test-hedgedoc-hardening systemd[1]: /etc/systemd/system/hedgedoc.service:39: StateDirectory= path is absolute, ignoring: /var/lib/hedgedoc
Jun 13 14:49:21 test-hedgedoc-hardening systemd[1]: /etc/systemd/system/hedgedoc.service:40: StateDirectory= path is absolute, ignoring: /var/lib/hedgedoc/uploads

This PR resolves this issue by stripping the /var/lib/ prefix from cfg.workDir.

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

this removes uploadsPath, can we add uploadsPath to ReadWritePaths instead?

Sure. I will change that by tomorrow.

Jun 25 19:16:19 services systemd[1]: Starting HedgeDoc Service...
Jun 25 19:16:19 services systemd[1431]: hedgedoc.service: Failed to set up mount namespacing: /run/systemd/unit-root/var/lib/hedgedoc/uploads: No such file or directory
Jun 25 19:16:19 services systemd[1431]: hedgedoc.service: Failed at step NAMESPACE spawning /nix/store/zw6fbfhjdnmqkzxgdg0vqlh55ydn79s6-unit-script-hedgedoc-pre-start/bin/hedgedoc-pre-start: No such file or directory
Jun 25 19:16:19 services systemd[1]: hedgedoc.service: Control process exited, code=exited, status=226/NAMESPACE
Jun 25 19:16:19 services systemd[1]: hedgedoc.service: Failed with result 'exit-code'.
Jun 25 19:16:19 services systemd[1]: Failed to start HedgeDoc Service.

This didn't show up in my tests.


feat(core): Add chip component

Hey, I just made a Pull Request!

Fixes #2219
This adds the Chip component to the storybook.
NOTES:

I don't know if we need to add a padding to the chip container to match the design a little more
I couldn't find an existing color in the palette that matched the chip container background "#D9D9D9"

:heavy_check_mark: Checklist

[ ] All tests are passing yarn test
[x] Screenshots attached (for UI changes)
[ ] Relevant documentation updated
[ ] Prettier run on changed files
[ ] Tests added for new functionality
[ ] Regression tests added for bug fixes

@stefanalund Do we really need our own Chip component at this point though, can't we just use the MUI one directly? 😅

Huh, there's something I don't understand here then...we now have our own Chip with minimal overhead, but users would still import from @backstage/core no?

I'm not sure either - this wrapper adds no functionality right? Then why don't people import the component directly from mui instead of us making a wrapper?

@stefanalund Our chip component is basically just export { Chip } from '@material-ui/core', since all the styling was moved to our theme. I'm saying we just remove our own and make users import directly from MUI instead, and have a storybook around that.
Unless we have some immediate work coming up that adds functionality to Chip?

Hi ! No problem, I understand !
I'll do that 👍


ImportError: DLL load failed while importing cv2: The specified module could not be found.

Expected behaviour
I'am trying to run a cod about document classification and I got this error i try to install the library via Anaconda but doesn't exist.
import pandas as pd
import numpy as np
import tensorflow as tf
import string
import nltk
import pathlib
import os
import cv2
import matplotlib.pyplot as plt
from tensorflow.keras.utils import to_categorical
from tensorflow.keras.metrics import TruePositives, FalsePositives, TrueNegatives, FalseNegatives, BinaryAccuracy, Precision, Recall, AUC

Install OpenCV using Anaconda:

Open the Anaconda Prompt or Anaconda PowerShell.
Run the following command to create a new virtual environment (replace env_name with the desired name for your environment):

If the installation is successful, you should be able to import the cv2 module without any issues.

Install OpenCV using pip:
If the Anaconda approach doesn't work, you can try installing OpenCV using pip.
pip install opencv-python

This command will install OpenCV and its dependencies using pip.

Check the installation path:
If you have multiple Python installations or environments on your system, make sure that you are importing the cv2 module from the correct environment or installation path.

Try Reinstall OpenCV:
If the above steps don't work, you can try uninstalling and reinstalling OpenCV.

OpenCV team does not maintain Anacoda packages, pip packages only. Looks like your OpenCV installation is not complete or broken. You can trace OpenCV loading process by setting sys.OpenCV_LOADER_DEBUG = 1 before the library import.

I was facing the same issue. I have python 3.11.7 with opencv 4.9.0. It was working fine until I started working with opencv and C++ in visual studio, which caused this problem. I don't know how the problem occurred, but it prevented me from working with python. I uninstalled visual studio and tried again, but the problem persisted. I resolved the issue by following these steps:

Check for Visual C++ Redistributable 2015 : Ensure it is installed on your system.
Check for Windows Media Feature Pack : Make sure it is installed, as it is essential for opencv.

if the above requirements are satisfied but the issue still persists, try reinstalling the opencv package:
pip uninstall opencv-python

delete the cv2 folder inside the location where you installed python packages\Lib\site-packages\cv2
reinstall opencv using pip :
pip install opencv-python

this method worked for me
if it doesn't work for you, refer to this: #36
this might help you

OpenCV team does not maintain Anacoda packages, pip packages only. Looks like your OpenCV installation is not complete or broken. You can trace OpenCV loading process by setting sys.OpenCV_LOADER_DEBUG = 1 before the library import.

Also likely a duplicate of either https://github.com/opencv/opencv-python/issues/771 and/or https://github.com/opencv/opencv-python/issues/856


"Hințești, "Lăzărești", "Smeura" are listed in the drop-down menu

Description:
When user writes "Hințești", "Lăzărești" and "Smeura" the locations appear in the drop-down menu next to the comune and the county witch is a part according to the law
Precondition:
The website is up an running.

Step 1
Write in the search bar "Hințești"

Expected results
The location appears in the drop-down menu as "Hințești, Argeș (Moșoaia)"

Step 2
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 3
Write in the search bar "Lăzărești"

Expected results
The location appears in the drop-down menu as "Lăzărești, Argeș (Moșoaia)"

Step 4
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 5
Write in the search bar "Smeura"

Expected results
The location appears in the drop-down menu as "Smeura, Argeș (Moșoaia)"


English and Arabic text are overlapping in PDF

Attach (recommended) or Link to PDF file here:
test arabic1.pdf
Configuration:

Web browser and its version: Chrome, firefox
Operating system and its version: Windows 11
PDF.js version: 3.10.111
Is a browser extension:

Steps to reproduce the problem:

Open the above PDF in PDF.js viewer

What is the expected behavior? (add screenshot)
Arabic text to be displayed properly without overlap.
What went wrong? (add screenshot)

Link to a viewer (if hosted on a site other than mozilla.github.io/pdf.js or as Firefox/Chrome extension):

The above text displays in ADOBE perfectly.

Given that we seem to match PDFium (i.e. the Google Chrome PDF Viewer) exactly, I'd say that it's your PDF document that's broken. You need to embed all fonts in order to guarantee that PDF Viewers will render your document correctly.

I think the direction of the canvas element will fix that

As already mentioned in https://github.com/mozilla/pdf.js/issues/16953#issuecomment-1721317421, your PDF document is wrong which is why multiple viewers cannot handle this "correctly". More specifically:

The relevant fonts are not embedded in the PDF document, which is the first problem with your document.
The relevant fonts contain no information about how the glyph-mapping should be done. With those non-embedded fonts being CIDFontType2 they should've included CIDToGIDMap-data which would've prevented this issue.
The only possible indication of the "intended" glyph-mapping in this case is the ToUnicode-data of the fonts, which is what we're "forced" to fallback on[1], but unfortunately that data contains "bad" entries which explain the problem reported here.

Given the complete lack of proper data to use for the glyph-mapping, and that the only available information is "wrong", there unfortunately doesn't seem to be much that we can do here without breaking other PDF documents with non-embedded fonts.

[1] If we didn't use the ToUnicode-data in cases such as these we'd have a lot more problems with non-embedded fonts.


PT unit is always shown as SUV even when the value is not in SUV (because meta data is missing)

Currently the annotations (elliptical, rectangle, probe, maybe others) show SUV as the unit of all PT images (see .e.g. https://github.com/cornerstonejs/cornerstone3D-beta/blob/main/packages/tools/src/tools/annotation/RectangleROITool.ts#L851-L854).
However, not all PT images have the required metadata to convert values to SUV.
https://v3-demo.ohif.org/viewer?StudyInstanceUIDs=<IP_ADDRESS>.4.1.25403.345050719074.3824.20170125113417.1

If you inspect the log, you can find:
Error: CorrectedImage must contain "ATTN" and "DECY": NORM,DTIM,RADL,DECY
    at calculateSUVScalingFactors

Error: PatientWeight value is missing. It is not possible to calculate the SUV factors

So in these cases the unit should not be SUV.
Ideally, even if all metadata is present to calculate SUV, the user should be able to select the unit (e.g. if an image is in units Bq/ml, that might be what the user actually wants so see).
PS: Thank you for this great library!

Before changing any of this, it might make sense to unify the handling of units, see https://github.com/cornerstonejs/cornerstone3D-beta/pull/161

I'm wondering if the cornerstone tools library is actually the right place to determine the units, since the actual metadata to convert the values is extracted in a different place, e.g. in a OHIF extension.

closed by #161


⚠ Bofrost.fr has degraded performance

In 79aa2a3, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1490 ms

Resolved: Bofrost.fr performance has improved in c6284b5.


-g flag crashes pycp

When I do pycp -g (directory) (directory) I get the following:
Traceback (most recent call last):
  File "/usr/sbin/pycp", line 11, in <module>
    sys.exit(main())
  File "/usr/lib/python3.6/site-packages/pycp/main.py", line 114, in main
    errors = transfer_manager.do_transfer()
  File "/usr/lib/python3.6/site-packages/pycp/transfer.py", line 354, in do_transfer
    error = ftm.do_transfer()
  File "/usr/lib/python3.6/site-packages/pycp/transfer.py", line 188, in do_transfer
    self.transfer_file()
  File "/usr/lib/python3.6/site-packages/pycp/transfer.py", line 229, in transfer_file
    self.callback(transfered)
  File "/usr/lib/python3.6/site-packages/pycp/transfer.py", line 339, in on_file_transfer
    self.progress_indicator.on_progress(progress)
  File "/usr/lib/python3.6/site-packages/pycp/progress.py", line 517, in on_progress
    self._render_second_line(progress)
  File "/usr/lib/python3.6/site-packages/pycp/progress.py", line 511, in _render_second_line
    filename=progress.src,
  File "/usr/lib/python3.6/site-packages/pycp/progress.py", line 391, in render
    length, string = component.render(kwargs)
  File "/usr/lib/python3.6/site-packages/pycp/progress.py", line 252, in render
    return len(text), text
TypeError: object of type 'NoneType' has no len()

Oops

Glad I could help :)

Just to let you know the crash only happens for me on Voidlinux system which uses an AMD Ryzen 1800x.  Updated to the latest on debian via pip and it runs fine (thats an AMD A8 APU).

Actually it had nothing to do with a race condition :)
I just failed to preserve the indentation when I move the code for shorten_path from one file to the other.
And I also forgot about those doctests tests.
Should be fixed not. Feel free to take a look at the pull request

cheers will try it out :)


Not Loading Papertrail Subclasses in Rake Task

Sorry if this is a little vague, but my papertrail custom classes dont seem to be loaded properly in rake tasks, i'm not sure the exact issue, but namely, if i run rails console and do PaperTrail::Version.subclasses it returns [MyCustomVersion1, MyCustomVersion2], but when running from a rake task, it seems to be empty (i.e. the subclasses are not defined). Any thoughts?
I've tried version of gem 3.0.6 and 4.0.0 and it exists with both. I'm sort of guessing this could be a rails problem (not loading classes / namespaced improperly?)
I've tried adding config.autoload_paths += %W(#{Rails.root}/models/papertrail_versions) to no avail.

Hmmm - probably just need to use     Rails.application.eager_load! - sorry!


fix: fix seamless

Summary
Addressing #6340

Did a bit of testing back-to-back with previous implementation and confirmed fixes the issue. It does drastically change the output images but not much we can do about that.


HADOOP-17206. Add python2 to required package on CentOS 8 for building documentation.

mvn site fails without python2.
[INFO] --- exec-maven-plugin:1.3.1:exec (shelldocs) @ hadoop-common ---
/usr/bin/env: ‘python2’: No such file or directory

shelldocs.py and releasedocmaker.py requires python2.
$ grep -r python2 patchprocess
patchprocess/apache-yetus-0.10.0/lib/shelldocs/shelldocs/__init__.py:#!/usr/bin/env python2
patchprocess/apache-yetus-0.10.0/lib/shelldocs/shelldocs.py:#!/usr/bin/env python2
patchprocess/apache-yetus-0.10.0/lib/releasedocmaker/releasedocmaker/__init__.py:#!/usr/bin/env python2
patchprocess/apache-yetus-0.10.0/lib/releasedocmaker/releasedocmaker/utils.py:#!/usr/bin/env python2
patchprocess/apache-yetus-0.10.0/lib/releasedocmaker/releasedocmaker.py:#!/usr/bin/env python2
patchprocess/apache-yetus-0.10.0/lib/precommit/test-patch-docker/Dockerfile:    python2.7 \

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
25m 37s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s
No case conflicting files found.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ trunk Compile Tests _

+1 :green_heart:
shadedclient
19m 49s
branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
shadedclient
13m 51s
patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
asflicense
0m 36s
The patch does not generate ASF License warnings.

61m 38s

Subsystem
Report/Notes

Docker
ClientAPI=1.40 ServerAPI=1.40 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2227/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/2227

Optional Tests
dupname asflicense

uname
Linux 1008fbf7dc58 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 86bbd38c8dc

Max. process+thread count
402 (vs. ulimit of 5500)

modules
C: . U: .

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2227/1/console

versions
git=2.17.1 maven=3.6.0

Powered by
Apache Yetus 0.13.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

Thanks, @tasanuma. I merged this.


fix(wasm): Avoid requesting stdlib paths from the source-resolver

Description

Problem*

Resolves #1244
Summary*

This fixes the noir_wasm integration tests, such that they succeed. The fundamental problem was that the implementation of source-resolver isn't actually checking file paths to know what files to load. Instead, it was always returning the entry file as the source code, so this meant the stdlib was setup all wrong inside the compiler.
While this is a lazy way to implement the source-resolver, none of the stdlib file paths should be reaching it in the first place. So I've added an extra case in the file_reader.rs to never go to the filesystem for the stdlib, which we always embed.
Also note that some stuff in the integration test needed to change because proving takes 6.5 minutes and verifying takes 5 minutes.
Documentation

[ ] This PR requires documentation updates when merged.

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

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

Additional Context

PR Checklist*

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

CI is failing

This is the wasm test that constantly times out. It hasn't been working for weeks and is not a required check that blocks PRs.


Unable to sign in on beta

GUI crashes when trying to sign in, sign in using web browser does not work either.

I have the same issue.

Hi, sorry to hear that. What platform are you on ?

Neither of the login methods work for me either.

Edition	Windows 10 Pro
Version	21H2
Installed on	9/4/2021
OS build	19044.2006
Experience	Windows Feature Experience Pack 120.2212.4180.0

@VeikkoLehmuskorpi, good news, I could reproduce and fix the problem with the web login in the last release
Regarding @c1sxr0bzn's problem, I could not reproduce, but I implemented logging to file in the last release. Could you reproduce the issue, and send me the logs.txt file in the .plexrichpresence in your user directory ? Thanks in advance

Hi. I am able to log in via browser now, but now when the app loads it just closes right away. I can't find the logs.txt file because i cant find the .plexrichpresence folder.
Im running
Windows 10 Home 21H2
OS build 19044.2006
Windows Feature Experience Pack 120.2212.4180.0

@PsychoManiac189 you should remove that attachment.

@PsychoManiac189 you should remove that attachment.

i did, but why?

@PsychoManiac189 it contains sensitive information, you shouldn't post the entire log file in public

Yeah sorry, I shouln't have logged IP address, will remove it in next version

@PsychoManiac189 your issue was most likely #78 , should be fixed in last release
@VeikkoLehmuskorpi You can safely post logs from the last release, I removed logging of IP adresse

@PsychoManiac189 your issue was most likely #78 , should be fixed in last release @VeikkoLehmuskorpi You can safely post logs from the last release, I removed logging of IP adresse

ok. its working. any chance you gonna add it to say that discord is connected like the old one? also it dont show the time left on discord. just says "0:00 left"

@PsychoManiac189 this issue is tracked by #77. I will close this one, for now, @c1sxr0bzn @VeikkoLehmuskorpi don't hesitate to reopen and post logs if you still encounter this problem


GHxxx: Removed unnecessary parameter

I removed the forward slash parameter because it's unnecessary because line #64 that replaces all forward slashes with backslashes. Hardly a critical bug, but as I was studying the code, saw it, and thought I'd comment. The code was introduced in commit ce0c04e3 on 6/9/2014.

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. We will now review your pull request.
Thanks,
.NET Foundation Pull Request Bot

@SteveGTR were you in a position to rebase this PR as requested by @devlead?  If not, we can look into doing that work for you.
Also, was an issue raised for this PR?  As per our contributing documentation, we prefer that this is the case.  Thanks for your help!

PR #1756 replaces this one as this one seems dead.


Fractional KnapSack Algorithm

Have you read the Contributing Guidelines on Pull Requests?
(Write your answer here.)
Description
(Write your answer here.)
Checklist

[x] I've read the contribution guidelines.
[x] I've checked the issue list before deciding what to submit.
[x] I've edited the README.md and link to my code.

Related Issues or Pull Requests
(Write your answer here.)

Please don't push all these Codes in a single PR. Make separate PRs for all of them from separate branches. It is quite difficult to review a lot of code and corresponding README updates from the same PR.


nixos: Add networking.fqdnOrHostName

Description of changes
Add a useful computed value.
Removes repeated reimplementations of if cfg.domain == null then cfg.hostName else cfg.fqdn; and simplifies documentation.
I've tested this change by evaluating the nixosTests where possible. Hashes remained the same.
nix-instantiate -A nixosTests.discourse -A nixosTests.discourse -A nixosTests.jitsi-meet -A nixosTests.flannel -A nixosTests.kubernetes

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

Looks okay but I'm not very knowledgeable on the nixos networking options, kubernetes and flannel nixosTests work with these changes.

I don't understand how we can use it, because networking.fqdn must be set
      default = if (cfg.hostName != "" && cfg.domain != null)
        then "${cfg.hostName}.${cfg.domain}"
        else throw ''
          The FQDN is required but cannot be determined. Please make sure that
          both networking.hostName and networking.domain are set properly.
        '';

in which case do you have a hostname but not a fqdn without getting the error above?

If I'm not mistaken, this PR is purely refactoring, centralizing existing logic, but it seems the option descriptions need some clarification.

I don't understand how we can use it, because networking.fqdn must be set

The fqdn  value is not accessed when it is not available. fqdn requires a hostName and a domain, but fqdnOrHostName will return a simple hostName when the domain (and therefore fqdn) are not available.

in which case do you have a hostname but not a fqdn without getting the error above?

networking.fqdnOrHostName is for applications that want some sort of identifier for the machine, but do not care whether it's part of a nicely configured domain.
Applications that expect a "properly" resolvable name should keep using fqdn instead of the new option, to make sure domain is set.


Keep element visible once it has been visible once

Hello,
Firstly, thank you for this component, we've really enjoyed using it!
Often when using it we find we have to wrap the component and use onChange to store some local state to keep track of if the component has been visible once. This is so we keep the component on the page constantly once it's been seen by the user once (so if they are scrolling up/down a big list, things don't pop in and out).
This is pretty easily done by storing state and listening to onChange, but I was wondering if you'd consider a PR that added a keepVisibleOnceSeen prop that would do this out of the box. It would remove a small amount of boilerplate we have to have each time we use this component.
If you don't then that's totally cool, but if you think this is a reasonable addition I'd be happy to make the PR and do the work.
Thanks!
Jack

Sounds like a great feature to me! I think that you should issue a PR with the suggested code, it will be easier for everyone involved to comment and discuss over it once there is some code to talk about.

I'd fine this feature useful too as currently I'm keeping state just to toggle the active prop, same as Jack.
Loving this component btw! <3

To stayVisible, the following works for me:
`class VisibilityContainer extends React.Component {
constructor(props) {
super(props);
this.state = {visible: false}
}
static defaultProps = {
isVisibleClass: 'is-visible',
notVisibleClass: 'not-visible'
};
onChangeVisibility = isVisible => {
this.setState({visible: isVisible});
};
render() {
const {isVisibleClass, notVisibleClass, children} = this.props;

return (
  <VisibilitySensor onChange={this.onChangeVisibility} active={!this.state.visible}>
    { ({isVisible} ) =>
      <div className={isVisible ? `visibility ${isVisibleClass}` : `visibility ${notVisibleClass}`}>
        { children }
      </div>
    }
  </VisibilitySensor>
)

}
}`


Cube creation not blendable

Cube creation for new diagnostic plugins that don't require level 3 blending:

Orographic enhancement
Weather symbols
Convection
Optical flow (nowcast)

Testing:

[x] Ran tests and they passed OK
[x] Added new tests for the new feature(s)

 Here is an overview of what got changed by this pull request:

Complexity increasing per file
==============================
- improver_tests/metadata/test_utilities.py  1

Complexity decreasing per file
==============================
+ improver/orographic_enhancement.py  -1

Clones removed
==============
+ improver_tests/wxcode/wxcode/test_utilities.py  -8
+ improver_tests/acceptance/test_nowcast_optical_flow.py  -2
+ improver_tests/wxcode/wxcode/test_WeatherSymbols.py  -9

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Complexity increasing per file
==============================
- improver_tests/metadata/test_utilities.py  1

Complexity decreasing per file
==============================
+ improver/orographic_enhancement.py  -1

Clones removed
==============
+ improver_tests/wxcode/wxcode/test_WeatherSymbols.py  -9
+ improver_tests/acceptance/test_nowcast_optical_flow.py  -2
+ improver_tests/wxcode/wxcode/test_utilities.py  -8

See the complete overview on Codacy


Use tox?

Use tox or something like this to test multiple python version (and prevent #19 )

added in #43


[Feature] Firestore Plugin Issues

Description
Users find it hard to use the Firestore plugin. A few enhancements suggested are

[ ] The start after takes in a document so we need validation there and the text should read start after document
[ ] The end before cannot be used for pagination. It acts as a limit more than a fetch before option
[ ] The start after field does not work if the ordering field does not have entirely unique values. We can auto append _ref while querying to solve this

firestore 6m usage: 336
Stats

Stat
Values

Reach
336

Effort (months)
<>


chore: update twitter_usernames.txt

clean up of some usernames which are:

nonexistent
private
suspended
duplicates

This will be shipped to validators on next patch release.


Specifying term_char is broken

I get this traceback when specifying term_char on python 3.8:
File "/usr/lib/python3.8/site-packages/vxi11/vxi11.py", line 727, in write
self.write_raw(str(message).encode(encoding))
File "/usr/lib/python3.8/site-packages/vxi11/vxi11.py", line 640, in write_raw
data += term_char
TypeError: can't concat int to bytes
It seems this can be fixed by changing line 639 from:
term_char = str(self.term_char).encode('utf-8')[0]
to:
term_char = str(self.term_char).encode('utf-8')[:1]

Duplicate of https://github.com/python-ivi/python-vxi11/issues/13.


fix: Add a optional grace time period to shutdown method

Summary
Add optional parameter: grace_time_milliseconds to client.shutdown()
Allow user to delay main interpreter thread close waiting the last batch events task scheduled to threads pool.
Checklist

[x] Does your PR title have the correct title format?
Does your PR have a breaking change?:  no

I added https://github.com/amplitude/Amplitude-Python/pull/41 but apparently somene is really afraid about incomming pull requests... ;)

Closing this one for now since we pushed a fix in v1.1.1. Feel free to try the new version and let us know if the experience is improved or not. Thanks.


texelFetch for Vulkan by default

master 0287508
RTX 2070 SUPER, KDE Neon
Migrating project to Vulkan renderer,
texelFetch fails to compile, reports
E 0:00:00:0463   _compile_variant: Failed parse:
ERROR: 0:564: 'texelFetch' : required extension not requested: GL_EXT_samplerless_texture_functions
ERROR: 0:564: '' : compilation terminated
ERROR: 2 compilation errors.  No code generated.
  <C++ Source>   servers/rendering/rasterizer_rd/shader_rd.cpp:335 @ _compile_variant()

Steps to reproduce:
Create a shader material with texelFetch

Yeah, I see the same bug on Windows/GTX1060 too

For the record, this doesn't appear to be related to #40133.


router-link is deprecated

vue js throws following error:
<router-link>'s tag prop is deprecated and has been removed in Vue Router 4. Use the v-slot API to remove this warning: https://next.router.vuejs.org/guide/migration/#removal-of-event-and-tag-props-in-router-link.

I'm sorry
Most of Vue Router API has remained unchanged during its rewrite from v3 (for Vue 2) to v4 (for Vue 3)

you must user with Vue 2
good luck


Catch exceptions when populating submissions table

Before, when any submission got into an invalid state, the helper
function gathering all the table data would fail. This caused the table
to not load at all. Now the error is caught, and an error boolean is
placed in the returned object, which the front-end then checks and
displays an errored submission (a light red row) in the table.
Population of other submissions should continue unaffected.

@david-yz-liu Fixed


improving time parsing

Hello, @evenator, thank you for your suggestion. I have added two new commits.

Sorry I haven't had a chance to re-review this. I think It looks good. I need to find some time to test it out.

Glad to see that :)


don't walk over sun_path size limit in snprintf()

otherwise building on ppc64le fails with:
src/sockets.c: In function 'socket_path':
src/sockets.c:98:62: error: '%s' directive output may be truncated writing up to 107 bytes into a region of size 104 [-Werror=format-truncation=]
   98 |                 snprintf(addr->sun_path, sun_path_size, "/tmp%s", name);
      |                                                              ^~
src/sockets.c:98:17: note: 'snprintf' output between 5 and 112 bytes into a destination of size 108
   98 |                 snprintf(addr->sun_path, sun_path_size, "/tmp%s", name);
      |                 ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors

this is caused by the "/tmp%s" format specifier:
snprintf(addr->sun_path, sun_path_size, "/tmp%s", name);
being 4 bytes longer than sun_path/sun_path_size (when added to the size of name), so make name shorter by 4 than the sun_path_size so it fits
as an aside, i have no idea why this doesn't fail on any other arch. technically on all of them that is doing a size = size + 4, so they should all be truncated...

Many thanks! 1.5.1 released.


Gtk3

Just debugging: https://github.com/conda-forge/qt-gtk-platformtheme-feedstock/issues/11

Checklist

[ ] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Tested https://github.com/conda-forge/qt-gtk-platformtheme-feedstock/pull/12 locally. it works.


InMemory Catalog

Feature Request / Improvement
Feature Request: InMemory Catalog implementation for Python Iceberg. For testing, prototyping, and generally playing around with Iceberg.
It would be great to have a catalog implementation in-memory, and possibly write to local file system instead of s3. This would lower the barrier to entry to use the python iceberg library.
There's currently a NoopCatalog which is used for loading StaticTable
There's also a InMemoryCatalog implementation already used for testing. We can use this as the basis for implementation.
Inspired by Trino's Memory connector

Forwarding my comment here as well: https://github.com/apache/iceberg-python/pull/289#issuecomment-1903442816
Maybe we should add this to the documentation of the SqlCatalog as well:
def catalog_memory(warehouse: Path) -> Generator[SqlCatalog, None, None]:
    props = {
        "uri": "sqlite+pysqlite:///:memory:",
        "warehouse": f"file://{warehouse}",
    }

https://github.com/apache/iceberg-python/blob/1befad70bb72e649ec07431a43972aa2cd0cc0da/tests/catalog/test_sql.py#L69-L73
The warehouse directory is where the files are stored.

@Fokko
Is this https://github.com/apache/iceberg/pull/4518 supported as part of pycieberg?

@Fokko
Didn't know the in-memory sqlite option was available! That's awesome.
I was able to read/write using the SqlCatalog. Metadata is saved in memory using sqlite and data is saved on disk.
Pulling out your comment in #289

Thanks for working on this @kevinjqliu. The issues was created a long time ago, before we had the SqlCatalog with sqlite support. Sqlite can also work in memory rendering the InMemoryCatalog obsolete. Having two in-memory implementations in the codebase adds additional complexity in the codebase. My suggestion would be to replace the MemoryCatalog with the SqlCatalog. WDYT?

I agree that we don't need 2 in-memory catalog implementations. Let me see if I can repurpose #289

Looks like there's also a InMemoryCatalog in the Java lib
lgithub.com/apache/iceberg/blob/0f509d2d678db2d7322dafded58ec0ca6d7fb268/core/src/main/java/org/apache/iceberg/inmemory/InMemoryCatalog.java#L61

@Fokko I took some time to think this over. I understand your concern regarding 2 in-memory catalog implementations. The 2 implementations are just 2 different ways to achieve the same outcome; using Sqlite's in-memory database is an implementation detail.
I'm leaning towards having InMemoryCatalog as an option especially since there is a Java version of it already.
I think there's value in storing the pure Python Object in memory and making it easily accessible. The Sqlite's in-memory database is another level of indirection which can be difficult to reason about the internals of Iceberg.

@kevinjqliu Alright, that's fair, I just wanted to make sure that we considered the option before making the InMemory one public 👍

I must admit that I'm second-guessing the decision to add another catalog. This mostly comes from the recent discussions on the Java side where catalogs are being removed to avoid further proliferation.

@Fokko thats fair. I'll see if there are features in the PR I can pull out. We can leave the InMemory catalog under tests/ for now.


gRPC create

Add a VIN VC retrieval/generation gRPC call for internal use.

The arguments are the same as in the REST API: vehicle token id and a force boolean.
The response in the successful case currently only contains the raw VC.

Up to you but I don't mind updating the identity client error handling in this PR. Since this repo is still newer all the updates are welcome

I need to add the actual wiring. This is getting pushed back so I’ll probably just merge in whatever you’re doing.


[AIRFLOW-3383] Rotate fernet keys.

Make sure you have checked all steps below.
Jira

[x] My PR addresses the following Airflow Jira issues and references them in the PR title. For example, "[AIRFLOW-XXX] My Airflow PR"

https://issues.apache.org/jira/browse/AIRFLOW-3383
In case you are fixing a typo in the documentation you can prepend your commit with [AIRFLOW-XXX], code changes always need a Jira issue.

Description

[x] Here are some details about my PR, including screenshots of any UI changes:

As far as I can tell, it's not straightforward to rotate the fernet key for encrypted passwords and extras. A user would have to generate a new key, restart airflow, and manually re-enter each value to be encrypted via the web interface. It should be possible to specify multiple fernet keys at once, and to easily re-encrypt values with a new key. The cryptography package provides a MultiFernet class with a rotate method that handles this use case, so I wrote up a patch that uses MultiFernet to support multiple keys and rotation via the command line.
With this approach, we can rotate keys by adding a new key at the start of the FERNET_KEYS config variable, then running the rotate_credentials command from the command line. If the approach makes sense, I'll write up some documentation.
Tests

[x] My PR adds the following unit tests OR does not need testing for this extremely good reason:

Commits

[x] My commits all reference Jira issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters (not including Jira issue reference)
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

Documentation

[x] In case of new functionality, my PR adds documentation that describes how to use it.

When adding new operators/hooks/sensors, the autoclass documentation generation needs to be added.

Code Quality

[x] Passes flake8

Codecov Report

Merging #4225 into master will increase coverage by <.01%.
The diff coverage is 62.5%.

@@            Coverage Diff             @@
##           master    #4225      +/-   ##
==========================================
+ Coverage   77.81%   77.81%   +<.01%
==========================================
  Files         201      201
  Lines       16348    16362      +14
==========================================
+ Hits        12721    12732      +11
- Misses       3627     3630       +3

Impacted Files
Coverage Δ

airflow/bin/cli.py
64.25% <16.66%> (-0.35%)
:arrow_down:

airflow/models.py
92.44% <90%> (+0.1%)
:arrow_up:

Continue to review full report at Codecov.

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

Ideally, this isn't anything that I would use. In my case I would:

Don't store all the credentials in Airflow itself, but connect to an external credential system such as Google KMS, or Azure Keyvault, Hashicorp vault, etc.
When provisioning a new Airflow instance, first deploy it, and then set all the credentials again programmatically. We don't want to manually enter all the credentials because that is a very brittle process. Therefore this should be automated. If you update you Fernet key, you could update your credentials as well.

What do you think?

Agreed that it would be useful to integrate Airflow with external KMS options. But AWS/GCP/Azure KMS services don't store encrypted credentials--they store encryption keys. AWS Parameter Store and Hashicorp Vault do store secrets. Would you be interested in adding pluggable secret encryption and/or storage for Airflow 2.0? I'd be happy to contribute.
I think it should be possible to rotate the Fernet key without updating all credentials. Ideally users can easily automate updating all credentials, but that might not be possible--for example, users might add credentials to Airflow manually, credentials might need to be pulled from many sources, etc. And in general, it's good practice to make it possible to easily rotate any cryptographic keys.

By the way, I also submitted #4232, which should make it easier to programmatically update credentials.

Ping @Fokko @ashb @kaxil. I agree that storing credentials in an external service like Vault would be a useful feature, but as long as we're supporting credential storage in the airflow database with fernet encryption, I think we should support fernet key rotation. This was the simplest implementation that came to mind. WDYT?
I would also be happy to write up some options for using external encryption and credential services if you'd be open to it.

but as long as we're supporting credential storage in the airflow database with fernet encryption, I think we should support fernet key rotation

Agreed.

The build is passing again after rebasing on master. Ready for review when you have time @ashb.

Good call, I updated the help text for the rotate_fernet_key command.

Merge conflicts resolved. Should be ready for another look @ashb.

Sorry @ashb, I was in a hurry earlier and totally misread your point about encrypting variables. I pushed up some changes to rotate keys on encrypted variables too.


Fix for issue#897.

Added starting of the request timer even when the prvPublishMmessage returns a failure.
This is a fix for Issue#897
Description
Added the starting of the request timer even if the "prvPublishMessage" returns a failure.
Checklist:

[x] I have tested my changes. No regression in existing tests.
[x] My code is Linted.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Hello,
Thanks for bringing this up. This intermittent issue we have seen and are actively working on internally. We will get back to you in a week or so after we recreate it internally and try your fix with a few days of soak as well.

/bot run checks


bug: plugin runs on default setting

Did you check docs and existing issues?

[X] I have read all the lazy docs
[X] I have searched the existing issues of lazy
[X] I have searched the exsiting issues of the plugin I have a problem with

Neovim version (nvim -v)
NVIM v0.9.0-dev-590+g6ba34e21fe
Operating system/version
Arco Linux (Latest)
Describe the bug
Carbon.nvim plugin runs only on default setting. Even I changed settings. It runs well on packer.nvim.
Minimal packer.nvim config which run well:
local ensure_packer = function()
  local fn = vim.fn
  local install_path = fn.stdpath('data') .. '/site/pack/packer/start/packer.nvim'
  if fn.empty(fn.glob(install_path)) > 0 then
    fn.system({ 'git', 'clone', '--depth', '1', 'https://github.com/wbthomason/packer.nvim', install_path })
    vim.cmd [[packadd packer.nvim]]
    return true
  end
  return false
end

local packer_bootstrap = ensure_packer()

return require('packer').startup(function(use)
  use 'wbthomason/packer.nvim'

  use {
    'SidOfc/carbon.nvim',
    config = function()
      require('carbon').setup({
        sync_pwd = true,
        auto_open = false,
        indicators = { collapse = '▾', expand = '▸' },
      })
    end
  }
  if packer_bootstrap then
    require('packer').sync()
  end
end)

Steps To Reproduce

Run nvim --clean -u init.lua with minimal config.
It will open fcarbon automatically.

Expected Behavior
It shouldn't open Fcarbon by default, also indicators should be ▾ and ▸.
Repro
-- DO NOT change the paths and don't remove the colorscheme
local root = vim.fn.fnamemodify("./.repro", ":p")

-- set stdpaths to use .repro
for _, name in ipairs({ "config", "data", "state", "cache" }) do
  vim.env[("XDG_%s_HOME"):format(name:upper())] = root .. "/" .. name
end

-- bootstrap lazy
local lazypath = root .. "/plugins/lazy.nvim"
if not vim.loop.fs_stat(lazypath) then
  vim.fn.system({
    "git",
    "clone",
    "--filter=blob:none",
    "--single-branch",
    "https://github.com/folke/lazy.nvim.git",
    lazypath,
  })
end
vim.opt.runtimepath:prepend(lazypath)

-- install plugins
local plugins = {
  "folke/tokyonight.nvim",
  { "SidOfc/carbon.nvim", config = function()
    require('carbon').setup({
      sync_pwd = true,
      auto_open = false,
      indicators = { collapse = '▾', expand = '▸' },
    })
  end }
  -- add any other plugins here
}
require("lazy").setup(plugins, {
  root = root .. "/plugins",
})

vim.cmd.colorscheme("tokyonight")
-- add anything else here

What is wrong here? I don't understand your description. Can you be mode specific on what is wrong?

Plugins runs on default setting. It ignore settings on setup.

I believe this is the same situation as for eyeliner (https://github.com/folke/lazy.nvim/issues/123), where the difference between Packer and Lazy.nvim stems from the fact that Lazy.nvim loads the config after init.lua and plugin/. I believe Packer instead goes init.lua then config then plugin/.
In this case the plugin is already initialized and user settings are ignored.

Yep, indeed the same. See https://github.com/SidOfc/carbon.nvim/blob/d2d78a63b6941ac32bd0835a660b59df7b1dc21f/lua/carbon.lua#L9
Carbon should fix this. Not a lazy issue.
Might've worked with Packer, but that behavior was wrong.


🐞 - DateRange should accept single character date segment during paste when date separated by '-' sign

Which package(s) are the source of the bug?
@maskito/kit
Playground Link
https://maskito.dev/kit/date-range/API
Description
Original issue https://github.com/taiga-family/maskito/issues/593 fixes the problem for dates formatted with dots like 11.9.2022.
The bug still can be reproduced with dates like 11-9-2022 or 7-10-2020 for DateRange only. Works fine for Date and DateTime.
Steps to reproduce
https://maskito.dev/kit/date-range/API?mode=dd%2Fmm%2Fyyyy
Paste 11-9-2022
✅ Expected behaviour:
Textfield contains 11.09.2022
❌ Actual behaviour:
Textfield contains 11.09.022
Maskito version
2.3.2
Which browsers have you used?

[ ] Chrome
[ ] Firefox
[ ] Safari
[ ] Edge

Which operating systems have you used?

[ ] macOS
[ ] Windows
[ ] Linux
[ ] iOS
[ ] Android

Hi! I`ll take it

@Suldenkov Hello!
Any updates ?

@Suldenkov Hello! Any updates ?

Hi! I found the cause of the error, but I don't know how to fix it yet. Because the original string uses a split by spaces, it's not clear how to distinguish them


Support tile categories

Intention

I'm submitting a feature request
Environment

NodeJS:
6.3.0
NPM:
3.10.6
Electron:
1.3.5
Chrome:
52.0.2743.82

Description
Current behavior:
All tiles are of the same type
Expected/desired behavior:
Organize tiles as tools (meaning development tools) and utilities
What is the motivation / use case for changing the behavior?
Possible confusion for new users finding which tile does what.
Logs

When did you @JeroenVinke squeeze this data entry script (probably taken from Rob) into our issues? I would really appreciate this format when reading the issues, but creating them is a different story :smile:

https://github.com/monterey-framework/monterey/commit/113dad63241566aa375e1a472559c9e39de5f8f9

but creating them is a different story

it is not always necessary to use the format ;)

I think this can wait until after the initial release. We don't have too many tiles yet, although I can see this becoming an issue

it is not always necessary to use the format

Actually, while this was my initial inclination (to cheat), I really like the effect of using it. And, yes, there are a few cases where reporting various version numbers does not make sense.

I think this can wait until after the initial release. We don't have too many tiles yet, although I can see this becoming an issue

I agree - meaning that this issue remains open.

I would like to include the planning for including the Workflow and Workflow manager entities in this issue - it seems that Commands tab will not fit in this final situation.

Also, a Workflows tab would look cooler. :+1:
:smirk:

I was not suggesting to rename it to Workflow as this would not necessarily fit in the existing concept where Workflow manager (not yet published entityis is completely independent of theTask managerand offers the support for defining the set of actions to be applied to a project. Such set is calledWorkflow` and we can maintain unlimited set of Workflows.
Workflow manager would offer the service of picking (or creating a new) workflow and assign it to a given project, where the Task manager will control its execution.
Since we do not yet have activated the  Workflow manager, my above comment was only meant as a caution not to create the conflict between the existing UI with the introduction of the Workflow manager and Workflow concepts.

Oh, I thought the commands in the Commands tab are essentialy workflows.
Then I misinterpreted that. :smiley:

Your thought is correct, I was only concerned about creating the situation which would require name changes later.


C#: Type-based pruning for data flow

This PR enables type-based pruning for the data flow library, similar to the Java library. Unlike the Java library, constructed types are not mapped to their unconstructed counterparts, so for example IEnumerable<int> and IEnumerable<string> are not considered compatible.
The PR is structured into three commits:
895745cdf93ba72833effb8512ffb7b507863ec5: This commit adds type information to data flow nodes, resulting in a changed DataFlow::PathNode::toString().
914b0b9e5bbd1425fb44c53009c796b16bcee083: Additional data flow tests that exhibit impossible flow because of incompatible types.
5895f2875e82daa09ab4fa26a574fa5a66650749: Fix missing flow through generic fields (ping @aschackmull : something similar is likely relevant for Java too, you will also need to add reads/stores as cast nodes).
8171e688f38e49b068c12408829b16409e059a60: Type-based pruning. This eliminates the impossible flow paths from the commit above.
Commit-by-commit review is suggested.
The dist-compare report is here. Note that mono times out before this PR after evaluating 156 out of 221 queries, and still full successful evaluation after this PR is faster.

I know this is still is draft but this is looking really exciting.

Thanks :-) There are still a few performance issues to iron out, but that shouldn't change the overall picture.

Turns out that this PR also has another positive impact: we are now recomputing fever cached stages (ideally, of course, no cached stages should be recomputed...).

Rebased in order to resolve merge conflicts in to .expected files.


Bump Gradle to 7.5.1

This just keeps us up to date.

(I should probably ask about norms for GitHub projects that actually merge commits directly, rather than the way we do for projects like Guava.... Is it preferable for me to merge or for me to approve and leave the merge to you? Are there standard practices for this, or do different projects do it differently?)


Reduce size of the repo

When cloning the repository, this seems to be ~35 Mb in size, which is enormous. That's not a fundamental problem, but it is certainly annoying and unnecessary for the most part. Part of this size is explained by notebooks 3 and 4, which contain a lot of BIG figures, but another part is due to the commit history which might have copies of these notebooks as they were being developed.
I would suggest:

Review the notebooks to try to reduce the figures size - and therefore the overall notebook size
Use https://rtyley.github.io/bfg-repo-cleaner/ to remove any old file (just make sure you don't remove the latest versions!)

Hi @dalonsoa, I have followed your recommendations. Now notebooks 3 and 4 have reduced size compared to old versions. I have also applied the bfg command to remove old files from commit history. However I have tried to clone the repository after the changes and it seems to be ~35 Mb in size again. Any thoughts on what is happenning? Many thanks!


asserting Assert.ThrowsException and failing creates an exception where the message include the message and stacktrace in it

Describe the bug
In the following method the exception fails and throws AssertFailedException.
The exception message
[TestMethod, ExpectedException(typeof(AssertFailedException))]
public async Task AssertThrowsExceptionAsync_Failure_OldAssertion()
{
    // arrange
    static Task ThrowExceptionAsync() => throw new InvalidOperationException();
    Func<Task> action = ThrowExceptionAsync;

    // old assertion:
    await Assert.ThrowsExceptionAsync<ArgumentException>(action);
}

Steps To Reproduce
using Assert.ThrowsException or Assert.ThrowsExceptionAsync and failing throws an AssertFailedException exception where the Message property contains "Exception Message: <the message>" and the "Stack Trace:    at <stack-trace>"
Expected behavior
The exception's Message property should only include the fail message (like any other assertion method in mstest)
Actual behavior
Additional context

Hi @Meir017,
Sorry I missed this report! This is indeed inconsistent with the other assertion message so we will fix it.


[BUG] iOS device, PhotoManager.editor.copyAssetToPath return null

Describe the bug
in iOS device, PhotoManager.editor.copyAssetToPath return null.
not return assetEntity.
To Reproduce
  final assetPath =
      await PhotoManager.editor.iOS.createAlbum(packageInfo.appName);
  final tmpAssetEntity = await PhotoManager.editor.saveImageWithPath(filePath); // tmpAssetEntity exsist
  final assetEntity = await PhotoManager.editor
      .copyAssetToPath(asset: tmpAssetEntity, pathEntity: assetPath); // assetEntity is null

Expected behavior
above assetEntity has valid value
environment
flutter: 2.2.3
photo_manager package: 1.3.1
debugging
lib/src/plugin.dart
in Future<AssetEntity?> copyAssetToGallery,
final result = await _channel.invokeMethod('copyAsset', {
      'assetId': asset.id,
      'galleryId': pathEntity.id,
    });

result no ['data'], so ConvertUtils.convertToAsset is always return null;
static AssetEntity? convertToAsset(Map? map) {
    final Map? data = map?['data'];
    if (data == null) {
      return null; // always return null, at here
    }

    return _convertMapToAsset(data);
  }

please fix it, or workaround.

Device info, system info, granted full permission or not.

device info
device: iPhone X
version: ios11.3
system info
% flutter doctor
[✓] Flutter (Channel stable, 2.2.3, on macOS 11.5.2 20G95 darwin-x64, locale ja-JP)
[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
[✓] Xcode - develop for iOS and macOS
[✓] Chrome - develop for the web
[✓] Android Studio (version 4.1)
[✓] VS Code (version 1.56.2)
[✓] Connected device (2 available)

app permission status
photo app: read and write
camera app: enabled
anything else...?

easy to reproduce, use example code of this package.
modify as follows.
example/lib/page/save_image_example.dart
  void saveImageWithPath() async {
    final client = HttpClient();
    final req = await client.getUrl(Uri.parse(imageUrl));
    final resp = await req.close();

    File file = File(await downloadPath());

    resp.listen((data) {
      file.writeAsBytesSync(data, mode: FileMode.append);
    }, onDone: () async {
      print("write image to file success: $file");
      final asset = await PhotoManager.editor.saveImageWithPath(file.path);

      // add code
      final assetPath =
          await PhotoManager.editor.iOS.createAlbum("photoManager");
      final assetEntity = await PhotoManager.editor
          .copyAssetToPath(asset: asset!, pathEntity: assetPath!);
      print("saved asset: $assetEntity"); // fix
      // end

      client.close();
    });
  }

Device info, system info, granted full permission or not.

device info
device: iPhone X
version: ios11.3

Is this reproducible on any other iOS version?

sorry, i dont have other devices...
camera function doesnot work in simulator, so i cannot try it.


Bump kubevirtci for k8s-1.20

What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:

kubevirtci: add 1.20 provider and new z-stream releases

/retest

/retest

/hold
We have a weird new problem since my z release bump in kubevirtci

/close
closed in favor of https://github.com/kubevirt/kubevirt/pull/4662


go_to_previous should account for built in tab movements

go_to_previous should update the "previous" when things like gt, gT, :tabnext are used

Maybe I'm misunderstanding the issue, but when I use gt, gT, or :tabnext to switch between tabs, go_to_previous still works fine and switches to the last used tab.

You are right, looks like it is. Not sure what going on earlier for me. Closing, will just reopen if I run into something weird again


Add an arm64 apple fallback hack

note that this isn't tested, does anyone have a project that would trigger this?

I have a test condition for this, will give it a try

on aarch64 apple with a release only containing x86 linux/macos binaries:


Deprecate acceptsKeyboardFocus

From Keyboarding in React Native Desktop document:

React Native core introduced focusable that does the same thing as acceptsKeyboardFocus in v0.63. Windows has added focusable and marked acceptsKeyboardFocus as deprecated in 0.63. macOS needs to do the same.

Updating the original description, since the RNW deprecation ended up happening in 0.63. The version matrix basically looked like:

RNW 0.63 added focusable and runtime warnings if acceptsKeyboardFocus is used
RNW 0.64 will remove acceptsKeyboardFocus entirely (likely going to have a debug assert if VMs see them)
For Office, we need to support bundles built against N-1 versions of the react-native version we have in repo, so react-native-win32 also removed typings in 0.63

The TLDR: react-native-macos will need to add focusable by 0.63, and will be able to fully remove acceptsKeyboardFocus in 0.64. Deprecation warnings at runtime are useful since folks are using acceptsKeyboardFocus without typings.


Checkboxes should be snapping to full page width on 500px

Describe the bug
Checkboxes should be snapping to full page width on 500px not 740px

 Issue #974 Checkboxes should be snapping to full page width on 500px


Sorting list by moving an item up the list

When I try to use this library to just sort a fairly simple list.  I drag the fourth item and move it up and release, when I view the new list, it is adding the new item in the index + 1 position of where I dropped it.  For instance, if I try to drag an item to the top position, it puts it in the 2nd.
It seems to work correctly if I drag the item down to a lower position.
I'm using the (dndMoved) method.

I am basically seeing the same issue. Moving items dow work fine, moving items up do not... when I look into what is happening in the event handler, it looks like the items is not duplicated properly to the list before splicing the original:
IN a list of
1
2
3
If I drag 3 up to the second position, I get a list (before splicing):
1
2
3
3
with an index of 3. Index is correct but the list should have been:
1
3
2
3
It looks like a bug to me.

I found the bug.. it's in the dnd-list.js Line 124
need to change from this:
this.dndModel.splice(insertionPoint, 0, data);
to:
this.dndModel.splice(--insertionPoint, 0, data);

Yes. I was troubleshooting and pinpointed the issue also. I've found a "fix". One thing that looks wrong to me is that the line:
var offset = this.nativeElement.children.length - 1 - this.dndModel.length;
will always return "-1". I am not sure why it is there, maybe for transfers between lists, which is not what I need.
So, to make it work both ways, I realized that all is needed is for "insertionPoint" to be equal to "index -1"  if dragging down, or just equal to "index" if dragging up, in the line below:
this.dndModel.splice(insertionPoint, 0, data);
Now to figure out if the item was dragged up or down, I needed to compare index (which is the new position of the item) to the original position of the item. First I tried:
if (data !== true) {
var dataIndex = Array.prototype.indexOf.call(this.dndModel, data);
var insertionPoint = 0;
if (dataIndex < index) {
insertionPoint = index - offset;
} else {
insertionPoint = index;
}
this.dndModel.splice(insertionPoint, 0, data);
}
And that should have worked, but for whatever reason:
var dataIndex = Array.prototype.indexOf.call(this.dndModel, data);
does not find the object in the array and returns -1. I am probably misusing this function. Using plain "this.dndModel.IndexOf(data" also returns -1. Anyhow, since my items have id, the solution that works for me is specific, but It will work for anyone if your items have an "id" property or any other unique property:
if (data !== true) {
var dataIndex = this.dndModel.findIndex(i => i.id === data.id);
var insertionPoint = 0;
if (dataIndex < index) {
insertionPoint = index - offset;
} else {
insertionPoint = index;
}
this.dndModel.splice(insertionPoint, 0, data);
}
If someone know why the statements I used to find the index of the object in the list did not work please let me know.

I have the same problem with v1.2.5 and angular 6.0.3

I have the same problem with v1.2.5 and Angular 6.1.0

Same problem with v1.2.5 and Angular 7.1.4

I used @heitorb approach and build on top of that to get this solution with does not require any special logic to retrieve the id. I'm using lodash's findIndex function to do so.
Besides I'm now marking the element that is being moved for "removal" and getting rid of it later, though technically not strictly related for this issue.
Hope this helps you:
`if (data !== true) {
var dataIndex = _.findIndex(this.dndModel, data); // NEW
this.dndModel[dataIndex].toRemove = true;         // NEW
      var insertionPoint = 0;
      if (dataIndex < index) {
          insertionPoint = index - offset;
      } else {
          insertionPoint = index;
      }
      this.dndModel.splice(insertionPoint, 0, data);

      // remove element that was marked for removal
      _.remove(this.dndModel, el => el.toRemove);      // NEW

}`


Error: "Lost connection to the socket server" | It happens on adding a large json file!

⚠ Please verify that this bug has NOT been raised before.

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

🛡 Security Policy

[X] I agree to have read this project Security Policy

Description
No response
👟 Reproduction steps
Try to add more than 500 items by one json file.
👀 Expected behavior
Adding json files with any size.
😓 Actual Behavior
By importing more than 400 addresses (>50,000 lines in JSON file), Kuma couldn't add them showing this error:

🐻 Uptime-Kuma Version
1.18.0
💻 Operating System and Arch
Ubuntu 22.04 64bit
🌐 Browser
Chrome, Edge, Firefox
🐋 Docker Version
Docker version 20.10.12, build 20.10.12-0ubuntu4
🟩 NodeJS Version
v16.16.0
📝 Relevant log output
No response

@louislam any ETA on this?

First time user, already ran into this error with a mere 10 items.

We are encountering this issue now, we have just over 1000 sensors and the console seems to be rendered inoperable

Same issue here. Dashboard just keeps cycling through all the endpoints then errors out. "Lost connection to Server Socket Reconnecting......"
Dashboard is almost useless at this point

Had the same issue here

We have 3 instances, 2 of them both with ~300 monitors. These respond without issue but tend to be a bit slow starting up. Our third instance is at 1100 monitors, and we broke down around 800, it keeps loadin and loading.
I cannot use the dashbaord anymore.
If wanted I can provide additional information if it's required to help find the issue.

I am able to add 600 hosts per json file, I have added 1200 hosts to monitor, although, server becomes unresponsive after every 2 minutes losing connection with these 1200 hosts.

v2 does include a lot of perfomance updates and should allow scaling past ~200-500 monitors.
See https://github.com/louislam/uptime-kuma/milestone/24 for further progress

I didn't add any monitors, but the actions panel is always like this, refreshes every few seconds, so why

Obsolete as the backup feature has been dropped in https://github.com/louislam/uptime-kuma/pull/3892.

In our case, the cause of this error was haproxy. To solve this problem, we needed to add the following two settings to our haproxy.cfg file:

Just wanted to comment in here for other people looking for a solution.