Starting the Local Node, When I tried to deploy zksync locally, I encountered an error.

when i run
./start
The error message reads:
[+] Running 2/0
✔ Container local-setup-postgres-1  Created                                                   0.0s
✔ Container local-setup-zksync-1    Created                                                   0.0s
Attaching to postgres-1, zksync-1
postgres-1  |
postgres-1  | PostgreSQL Database directory appears to contain a database; Skipping initialization
postgres-1  |
postgres-1  | 2024-03-29 05:59:33.635 UTC [1] LOG:  starting PostgreSQL 12.18 (Debian 12.18-1.pgdg120+2) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
postgres-1  | 2024-03-29 05:59:33.635 UTC [1] LOG:  listening on IPv4 address "<IP_ADDRESS>", port 5432
postgres-1  | 2024-03-29 05:59:33.635 UTC [1] LOG:  listening on IPv6 address "::", port 5432
postgres-1  | 2024-03-29 05:59:33.832 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
postgres-1  | 2024-03-29 05:59:34.104 UTC [27] LOG:  database system was shut down at 2024-03-29 05:56:20 UTC
postgres-1  | 2024-03-29 05:59:34.204 UTC [1] LOG:  database system is ready to accept connections
zksync-1    | /usr/bin/entrypoint.sh: line 44: /etc/env/dev.env: No such file or directory
zksync-1 exited with code 1
my docker compose.yml is:

version: '3.2'
services:
  postgres:
    image: "postgres:12"
    logging:
      driver: none
    volumes:
      - postgres:/var/lib/postgresql/data
    environment:
      - POSTGRES_HOST_AUTH_METHOD=trust
      - POSTGRES_DB=zksync_local
  zksync:
    stdin_open: true
    tty: true
    image: matterlabs/local-node:latest2.0
    depends_on:
      - postgres
    ports:
      - "3050:3050" # JSON RPC HTTP port
      - "3051:3051" # JSON RPC WS port
    volumes:
      # Configs folder bind
      - zksync-config:/etc/env/
      # Storage folder bind
      - zksync-data:/var/lib/zksync/data
    environment:
      - DATABASE_URL=postgres://postgres@postgres/zksync_local
      - ETH_CLIENT_WEB3_URL=http://<IP_ADDRESS>:8545

volumes:
  postgres:
  zksync-config:
  zksync-data:

The error seems to indicate that zksync is unable to connect to PostgreSQL. How can I fix this?

I encountered the same issue as well.

If you're still having issues you can create a post on https://github.com/zkSync-Community-Hub/zkync-developers/discussions


Set timeout

Hi!
How can i set the timeuot?
I appreciate your help.

Please provide me with more information.
Don't know what you mean by: timeout.

No reaction, closing issue for now.


Update core to v0.8.12-SNAPSHOT

In this PR:

Migrated Spine core from 0.8.0 to 0.8.12-SNAPSHOT.
Made the code match the 100 symbol per line convention.
General code clean up.

@armiol PTAL

@armiol, PTAL again.

@armiol PTAL
Also, let's discuss the @codacy-bot's comments.

@armiol, I've addressed the main highlights of our conversation.

@armiol PTAL again.


Filter slides

Clear and concise description of the problem
There is currently no functionality to filter slides through tabs. You have to write your own functions, which is very inconvenient.
Suggested solution
It is necessary to implement filtering slides by removing unnecessary ones and adding the necessary slides.
Alternative
No response
Additional context
No response
Validations

[X] Follow our Code of Conduct
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

Would you like to open a PR for this feature?

[ ] I'm willing to open a PR

filter slides through tabs

what is "tabs"?

You have to write your own functions, which is very inconvenient.

what exactly inconvenient?

Hi, I'm here to resurface this feature request as this is a common feature that I use with Slick Carousel.
Here is a link with what I think captures the concept:
https://codepen.io/alj_dev/pen/Wxjwpr
Here is a screen shot to slick sliders version of filtering:
https://kenwheeler.github.io/slick/

Issue is closed because of outdated/irrelevant/not actual/needed more information/inactivity.
If this issue is still actual and reproducible for latest version of Swiper, please create new issue and fill the issue template correctly:

Clearly describe the issue including steps to reproduce when it is a bug.
Make sure you fill in the earliest version that you know has the issue.
Provide live link or JSFiddle/Codepen or website with issue


Fix CommonsLogFormatSink class name in the README

Fix CommonsLogFormatSink class name

Description
Fix a typo referring to the wrong class name in the README.
Motivation and Context

Better documentation == 👯♀ 🥳 ❤
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.

👍

Thank you for the fix 📣


Linux and Chrome do not mix

Is there an existing issue for this?

[X] I have searched the existing issues
[X] I have read the guide to filing a bug

Steps to reproduce
I have had this problem many times.. Only now do I complain.
I have linux mint.  It does this in Ubuntu as well.
I have searched this issue but it is closed and locked.
https://github.com/flutter/flutter/issues/90844
When ever I try to compile apk's or debug (especially debug) I get a system locked up if I have Google chrome open.  This does not do this in Windows.  It was one of the reasons why I stopped using linux until I got a virus or something.  Now I'm back.. but I keep accidentally opening the browser.
The results are the system freezes and power down is needed.
System:
  Kernel: 5.15.0-86-generic x86_64 bits: 64 compiler: gcc v: 11.4.0 Desktop: Cinnamon 5.8.4
    tk: GTK 3.24.33 wm: muffin dm: LightDM Distro: Linux Mint 21.2 Victoria base: Ubuntu 22.04 jammy
Machine:
  Type: Laptop System: LENOVO product: 82KT v: IdeaPad 3 14ALC6 serial: <superuser required>
    Chassis: type: 10 v: IdeaPad 3 14ALC6 serial: <superuser required>
  Mobo: LENOVO model: LNVNB161216 v: SDK0T76465WIN serial: <superuser required> UEFI: LENOVO
    v: GLCN52WW date: 12/09/2022
Battery:
  ID-1: BAT0 charge: 14.8 Wh (35.3%) condition: 41.9/45.0 Wh (93.1%) volts: 11.0 min: 11.1
    model: SMP L20M3PF0 serial: <filter> status: Discharging
CPU:
  Info: 6-core model: AMD Ryzen 5 5500U with Radeon Graphics bits: 64 type: MT MCP arch: Zen 2
    rev: 1 cache: L1: 384 KiB L2: 3 MiB L3: 8 MiB
  Speed (MHz): avg: 1410 high: 1489 min/max: 1400/2100 boost: enabled cores: 1: 1397 2: 1397
    3: 1395 4: 1489 5: 1466 6: 1397 7: 1397 8: 1396 9: 1397 10: 1397 11: 1397 12: 1397
    bogomips: 50310
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
  Device-1: AMD Lucienne vendor: Lenovo driver: amdgpu v: 6.2.4 pcie: speed: 8 GT/s lanes: 16
    ports: active: eDP-1 empty: HDMI-A-1 bus-ID: 03:00.0 chip-ID: 1002:164c
  Device-2: Chicony Integrated Camera type: USB driver: uvcvideo bus-ID: 1-3:2
    chip-ID: 04f2:b725
  Display: x11 server: X.Org v: <IP_ADDRESS> driver: X: loaded: amdgpu,ati
    unloaded: fbdev,modesetting,vesa gpu: amdgpu display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96
  Monitor-1: eDP res: 1920x1080 dpi: 158 diag: 354mm (13.9")
  OpenGL: renderer: AMD Radeon Graphics (renoir LLVM 16.0.6 DRM 3.54 5.15.0-86-generic)
    v: 4.6 Mesa 23.2.0-devel direct render: Yes
Audio:
  Device-1: AMD Renoir Radeon High Definition Audio vendor: Lenovo driver: snd_hda_intel v: kernel
    pcie: speed: 8 GT/s lanes: 16 bus-ID: 03:00.1 chip-ID: 1002:1637
  Device-2: AMD Raven/Raven2/FireFlight/Renoir Audio Processor vendor: Lenovo driver: N/A pcie:
    speed: 8 GT/s lanes: 16 bus-ID: 03:00.5 chip-ID: 1022:15e2
  Device-3: AMD Family 17h HD Audio vendor: Lenovo driver: snd_hda_intel v: kernel pcie:
    speed: 8 GT/s lanes: 16 bus-ID: 03:00.6 chip-ID: 1022:15e3
  Sound Server-1: ALSA v: k5.15.0-86-generic running: yes
  Sound Server-2: PulseAudio v: 15.99.1 running: yes
  Sound Server-3: PipeWire v: 0.3.48 running: yes
Network:
  Device-1: Realtek RTL8822CE 802.11ac PCIe Wireless Network Adapter vendor: Lenovo
    driver: rtw_8822ce v: N/A pcie: speed: 2.5 GT/s lanes: 1 port: 2000 bus-ID: 01:00.0
    chip-ID: 10ec:c822
  IF: wlp1s0 state: up mac: <filter>
Bluetooth:
  Device-1: Realtek Bluetooth Radio type: USB driver: btusb v: 0.8 bus-ID: 3-4:3
    chip-ID: 0bda:c123
  Report: hciconfig ID: hci0 rfk-id: 2 state: up address: <filter> bt-v: 3.0 lmp-v: 5.1
    sub-v: 6d7d
Drives:
  Local Storage: total: 238.47 GiB used: 94.25 GiB (39.5%)
  ID-1: /dev/nvme0n1 vendor: Samsung model: MZALQ256HBJD-00BL2 size: 238.47 GiB speed: 31.6 Gb/s
    lanes: 4 serial: <filter> temp: 30.9 C
Partition:
  ID-1: / size: 67.26 GiB used: 51.18 GiB (76.1%) fs: ext4 dev: /dev/nvme0n1p6
  ID-2: /boot/efi size: 256 MiB used: 39.5 MiB (15.4%) fs: vfat dev: /dev/nvme0n1p1
Swap:
  ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) priority: -2 file: /swapfile
Sensors:
  System Temperatures: cpu: N/A mobo: N/A gpu: amdgpu temp: 38.0 C
  Fan Speeds (RPM): N/A
Repos:
  Packages: apt: 2842
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/amdgpu-proprietary.list
    1: deb https: //repo.radeon.com/amdgpu/23.20/amdgpu/ubuntu jammy proprietary
  Active apt repos in: /etc/apt/sources.list.d/amdgpu.list
    1: deb https: //repo.radeon.com/amdgpu/23.20/amdgpu/ubuntu jammy main
  Active apt repos in: /etc/apt/sources.list.d/google-chrome.list
    1: deb [arch=amd64] https: //dl.google.com/linux/chrome/deb/ stable main
  Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list
    1: deb http: //packages.linuxmint.com victoria main upstream import backport
    2: deb http: //archive.ubuntu.com/ubuntu jammy main restricted universe multiverse
    3: deb http: //archive.ubuntu.com/ubuntu jammy-updates main restricted universe multiverse
    4: deb http: //archive.ubuntu.com/ubuntu jammy-backports main restricted universe multiverse
    5: deb http: //security.ubuntu.com/ubuntu/ jammy-security main restricted universe multiverse
  Active apt repos in: /etc/apt/sources.list.d/rocm.list
    1: deb [arch=amd64] https: //repo.radeon.com/amdgpu/23.20/rocm/apt/5.7 jammy main
  Active apt repos in: /etc/apt/sources.list.d/vscode.list
    1: deb [arch=amd64,arm64,armhf] http: //packages.microsoft.com/repos/code stable main
Info:
  Processes: 349 Uptime: 5m Memory: 5.63 GiB used: 1.71 GiB (30.4%) Init: systemd v: 249
  runlevel: 5 Compilers: gcc: 11.4.0 alt: 11/12 clang: 14.0.0-1ubuntu1.1 Client: Cinnamon v: 5.8.4
  inxi: 3.3.13

Expected results
I expect to be able to run chrome browser and debug apk at the same time without the system freezing.
Actual results
The system freezes and I have to power down and restart.
Code sample
I'll add a vanilla code sample later.. but this happens with my projects.
Screenshots or Video
none
Logs
Logs
$ flutter --verbose create foo.
[  +42 ms] executing: uname -m
[   +5 ms] Exit code 0 from: uname -m
[        ] x86_64
[  +56 ms] Artifact Instance of 'AndroidGenSnapshotArtifacts' is not required,
skipping update.
[   +2 ms] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required,
skipping update.
[        ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping
update.
[        ] Artifact Instance of 'FlutterWebSdk' is not required, skipping
update.
[        ] Artifact Instance of 'LegacyCanvasKitRemover' is not required,
skipping update.
[   +3 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.
[   +1 ms] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required,
skipping update.
[  +82 ms] Artifact Instance of 'MaterialFonts' is not required, skipping
update.
[        ] Artifact Instance of 'GradleWrapper' is not required, skipping
update.
[        ] Artifact Instance of 'AndroidGenSnapshotArtifacts' is not required,
skipping update.
[        ] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required,
skipping update.
[        ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping
update.
[        ] Artifact Instance of 'FlutterWebSdk' is not required, skipping
update.
[        ] Artifact Instance of 'LegacyCanvasKitRemover' is not required,
skipping update.
[        ] Artifact Instance of 'FlutterSdk' is not required, skipping update.
[        ] Artifact Instance of 'WindowsEngineArtifacts' is not required,
skipping update.
[        ] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping
update.
[        ] Artifact Instance of '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.
[   +4 ms] Artifact Instance of 'IosUsbArtifacts' is not required, skipping
update.
[        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping
update.
[        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping
update.
[        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping
update.
[        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping
update.
[        ] Artifact Instance of 'FontSubsetArtifacts' is not required, skipping
update.
[        ] Artifact Instance of 'PubDependencies' is not required, skipping
update.
[  +85 ms] "flutter create" took 199ms.
[   +3 ms] "foo." is not a valid Dart package name.

           See https://dart.dev/tools/pub/pubspec#name for more information.
[   +2 ms]
           #0      throwToolExit
(package:flutter_tools/src/base/common.dart:10:3)
           #1      CreateBase.projectName
           (package:flutter_tools/src/commands/create_base.dart:332:9)
           #2      CreateCommand.runCommand
           (package:flutter_tools/src/commands/create.dart:299:62)
           <asynchronous suspension>
           #3      FlutterCommand.run.<anonymous closure>
           (package:flutter_tools/src/runner/flutter_command.dart:1297:27)
           <asynchronous suspension>
           #4      AppContext.run.<anonymous closure>
           (package:flutter_tools/src/base/context.dart:150:19)
           <asynchronous suspension>
           #5      CommandRunner.runCommand
(package:args/command_runner.dart:212:13)
           <asynchronous suspension>
           #6      FlutterCommandRunner.runCommand.<anonymous closure>
           (package:flutter_tools/src/runner/flutter_command_runner.dart:339:9)
           <asynchronous suspension>
           #7      AppContext.run.<anonymous closure>
           (package:flutter_tools/src/base/context.dart:150:19)
           <asynchronous suspension>
           #8      FlutterCommandRunner.runCommand
           (package:flutter_tools/src/runner/flutter_command_runner.dart:285:5)
           <asynchronous suspension>
           #9      run.<anonymous closure>.<anonymous closure>
           (package:flutter_tools/runner.dart:115:9)
           <asynchronous suspension>
           #10     AppContext.run.<anonymous closure>
           (package:flutter_tools/src/base/context.dart:150:19)
           <asynchronous suspension>
           #11     main (package:flutter_tools/executable.dart:90:3)
           <asynchronous suspension>

[ +267 ms] ensureAnalyticsSent: 252ms
[        ] Running 0 shutdown hooks
[        ] Shutdown hooks complete
[        ] exiting with code 1

Flutter Doctor output
Doctor output
flutter doctor -v
[✓] Flutter (Channel stable, 3.13.6, on Linux Mint 21.2 5.15.0-86-generic,
    locale en_US.UTF-8)
    • Flutter version 3.13.6 on channel stable at
      /home/bhante/development/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision ead455963c (2 weeks ago), 2023-09-26 18:28:17 -0700
    • Engine revision a794cf2681
    • Dart version 3.1.3
    • DevTools version 2.25.0

[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    • Android SDK at /home/bhante/Android/Sdk
    • Platform android-34, build-tools 34.0.0
    • Java binary at: /home/bhante/development/android-studio/jbr/bin/java
    • Java version OpenJDK Runtime Environment (build
      17.0.6+0-17.0.6b829.9-10027231)
    • All Android licenses accepted.

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

[✓] Linux toolchain - develop for Linux desktop
    • Ubuntu clang version 14.0.0-1ubuntu1.1
    • cmake version 3.22.1
    • ninja version 1.10.1
    • pkg-config version 0.29.2

[✓] Android Studio (version 2022.3)
    • Android Studio at /home/bhante/development/android-studio
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build
      17.0.6+0-17.0.6b829.9-10027231)

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

[✓] Connected device (3 available)
    • SM A505G (mobile) • R58M85Z9HXX • android-arm64  • Android 11 (API 30)
    • Linux (desktop)   • linux       • linux-x64      • Linux Mint 21.2
      5.15.0-86-generic
    • Chrome (web)      • chrome      • web-javascript • Google Chrome
      118.0.5993.70

[✓] Network resources
    • All expected network resources are available.

• No issues found!

Thanks for the report @bksubhuti
Can you provide the details of the chrome browser version you are using ? Were you able to check on different chrome versions to confirm if the issue persists using those as well ?

  +85 ms] "flutter create" took 199ms.
[   +3 ms] "foo." is not a valid Dart package name.

           See https://dart.dev/tools/pub/pubspec#name for more information.

The error is expected as the name you are passing is not valid as mentioned in the log. You'll need to pass a valid name and check if it still persists or not.

Just a quick jump on your playground.. i see that appbar does change to the proper pastel version of the primary color.. but I'm not getting it by default as expected.

I should mention that this is only during compile time or "launching" time.  I just ran the emulator and had it load and then I opened the chrome browser and it did not crash.  Normally i use my phone becuase it is much slower on the emulator.
This bug was more on the amd computer than my older intel.  I only have 8 gb of ram.   It does not do this on windows dual boot on the same laptop.

Hey @bksubhuti
I checked this issue on my machine with Ubuntu distro (22.04.3 LTS 6.2.0-32-generic) and using Intel chip but can't reproduce the error. Verifying the issue with Android device (Realme 6, Android 11).
The Android app can be built normally when the Google Chrome browser is open before.
I saw it went well from your bar.txt output file above. Does that mean you no longer see the initial error?
Could you try checking this on an Android native project instead? I guess there are some processes that consume system resources too much causing the system to freezes.

Well.. like I said in my original post.. It is linked to my newer (but now old), computer with amd ryzen, and probably the graphics.  Can you test in an amd chipset?  AMD Ryzen 5 5500U with Radeon Graphics × 6  8gig ram

@bksubhuti Unfortunately, I don't have a machine with AMD chipset. For testing with native app, just try a default/skeleton app (it's easy to create from Android Studio IDE) then let us know if you have more information. Thanks!

It seems to be that I have 5.6 gb of ram showing as available .  and it does climb up with chrome running during a compile.  I have 8 gb and I guess some is stolen by the graphics which is embedded.   It could be good to make the compiling more efficient in memory.  It is really a burden to run the emulator even with most apps closed..  I'm using linux mint which is more efficient than ubuntu gnome (first time running).
Take note that windows can handle this without crashing.
I might upgrade my RAM.  At this point, if you change the developer minimum specifications for memory to 16gb then you can close the issue.  I'm not sure that is acceptable or not.

@bksubhuti Does that mean Flutter app consumes too much memory which causes system to freeze?
Could you try running Flutter app in profile mode and observe how much RAM is consumed by Flutter app? Please check this for Chrome browser as well.

haha.. i just lost all my logging in this chrome window..  while I was building.
basically..
it was about 4.5 gb with up to 2.0 gb cache .. 2.1 swap.
empty was about 2.gb.
I could not connect to the emulator.. then I ran a build for apk release and it went up to 5 gb and cache was like 1.3 gb (out of 6 availalbe).. the swap was up to 2.1 (full).
The crash is a memory problem for sure.
I have to do this later.. i have study..
It appears to me that the memory did not go down totally back to normal when I stopped everything.
seems like the memory is still being held somewhere.  I have chrome open vsc and sysmon.. before it was less than 2gb.. after trying to debug, after a build of release.. mem is 4.6 cache 1.3 swap 1.5.. like my machine is more or less idle and not doing work.

Thanks for the info but it's still not clear whether Chrome is one of the factors here. I guess it's just a case intended to consume enough memory to create this issue when building with Flutter later. This means you can try opening another application that consumes the same amount of memory. Can you test this? And can you try building Flutter app without opening other apps on the system?
You can also check this issue to see if it's similar as well.

only text editor + sys monitor
+vsc        2.3 gb cache 3.7   635mb swap

emulator  2.9 gb cache 3.4  swap 1.1
debug     3.7 cache 2.7   swap  gb 2.1
debug     4.1 2.2 cache   2.1 swap  (another time)
highest is 4.2 gb..mem

Perhaps this could be stress tested on vm?
I suspect that if I compiled and ran this a couple of times, I would be running out of more memory.
Try to look for leaks.  I felt like the memory usage was still there even after the debug session ended.

+vsc 2.3 gb cache 3.7 635mb swap

emulator 2.9 gb cache 3.4 swap 1.1
debug 3.7 cache 2.7 swap gb 2.1
debug 4.1 2.2 cache 2.1 swap (another time)
highest is 4.2 gb..mem

Could you be more specific on this? Please try to provide clear information similar to the first comment at https://github.com/flutter/flutter/issues/73402#issue-780390527 which will help us determine whether this issue is due to the device or Flutter. (hint: please use top command, find Flutter app, and share the result)
Also, are you only seeing this issue when building for Android platform? Does it happen if building for Linux or Web target?

This info .. was based on debugging apk with an android emulator I think comes from android studio.  but i use vsc.
I said, it does not happen with windows .. same apps running.
It also does not happen when running flutter debug linux desktop.  I mostly prefer to test debug in desktop because compile time and snappiness of the app .  Actually linux is best for desktop debugging over windows.. 3 x faster to compile and start.  and sqlite is 3x faster. (FOR DESKTOP)...   seeing realtime changes after saving a file are the same for both OS or not noticeable.

Thank you for sharing. I understand that upgrading the RAM  may "solve" the problem temporarily. However, the purpose of the issue is to report a bug that belongs to Flutter. Thus, we need more data insights than just observations.
First of all, since you also suspect it might be due to Android Studio, you should clarify whether the issue will occur if you create an Android native skeleton app or not. Additionally, using the Android emulator also takes up a lot of memory, so leave it out of the test and use a physical device if you have one.
I'm not sure if you started an emulator via Android Studio or the command line. If you go through Android Studio, then you are running it at the same time and consuming a certain amount of memory. Please clarify this in the response.
If the issue appears on Android native app, I'm afraid that this is an Android Studio issue (possibly due to its memory management being bad on your Linux mint distro) and this is outside the scope of Flutter.
On the contrary, if the issue only occurs with the Flutter sample app, use top command to watch app memory usage and share it here (maybe a duplicate of https://github.com/flutter/flutter/issues/73402):
top -p pid

I'm in the middle of finals week (8 days).
I can give a report later.. if I forget please give a bump.
I forgot to do a skeleton app.  I'll try .  I do remember this also happening using my phone.
Obviously, things work better on my phone, but I remember the computer crashing too with external device debugging.
It could also be my app which is sqlite db and has 600+mb datafile.. But sqlite should be able to manage it efficiently.  That was why we switched from flat files (and to flutter too).
http://github.com/bksubhuti/tipitaka-pali-reader
There is a db download on the readme page.
Please give me a few days.  I install AS but mostly for the licenses and virtual devices and flutter doctor complaints.
I use vsc.  It is much lighter.  All my activity is with vsc.
It does look like I can upgrade 16gb ram and 512gb sdd which is less than $100.  My computer was about $400 new and you get what you pay for.  But it still can do some heavy flutter db apps and video editing too.. It is just not so easy.  and I need to remember to not have chrome open.
I wonder how many flutter devs who release to all of the official app stores (5 OS's) actually have such low level hardware.
But please note.. it is a Linux + AMD thing only.
Linux on my older intel i5 8gb ram acer didn't crash (as I remember.. but it did struggle).  ($500 new during 2019).

It could also be my app which is sqlite db and has 600+mb datafile.. But sqlite should be able to manage it efficiently. That was why we switched from flat files (and to flutter too).

Please also make sure you check on Flutter skeleton app (counter app) or a completed and minimal reproducible code sample. The given source above is a complex production project so it's not easy for us to find the cause.

It was actually worse.. You can see the app memory..  only vsc and system monitor are running.

Thanks, it's a bit more intuitive, but it would be more specific to know how much memory the Flutter app is taking up. Could you check it on Processes tab or with command line mentioned above?

Looks like ~2gb

Labeling the issue for more insights. I summarize the issue below.
Issue summary

The issue occurs when compiling apk's or debug (especially debug). It causes the system to freeze and power down is needed.
It can be reproducible on a skeleton app
Issue only appears on Linux Mint OS on a machine having AMD Ryzen 5 5500U with Radeon Graphics × 6 8gig ram. It doesn't happen on Windows dual boot on the same laptop. Meanwhile, Linux on an older intel i5 8gb ram acer didn't crash.
System memory info:

https://github.com/flutter/flutter/issues/136528#issuecomment-1776561584
https://github.com/flutter/flutter/issues/136528#issuecomment-1778320725

Unfortunately, there isn't really enough information here for us to even determine if it has to do with Flutter tools, or just a combination of applications running which use up more RAM than the machine has.
We don't really see that there is anything we can do here to help without more definitive information that Flutter and its debugging tools are the cause.
We're therefore going to reluctantly close this issue for now.
(Desktop Triage)

Sorry to resurrect this issue.. but I figured it out.. There are java processes left in memory or left running.  So What I need to do , is remember to kill those processes before starting again.. simple memory panel plugin helped me figure this out.. So if I compile 2 or 3 times without killing the unkilled java processes.. then it is sure to run out of memory.. maybe even if I upgraded to 16 it would eat that up if I compiled a few times.  Would you like a screenshot.. This is from compiling apk only.  Using vsc or commandline in the vsc terminal.

Here you can see the screenshot shows java still running after the app was built.
This will memory creep each time I do a compile command.. flutter build apk --release
I'm sure release or debug does not make a difference.
right now, I'm at 78% memory
If I kill these processes.. I go back to 40+% or so.. which should make sense mathematically.

**after killing 2 java processes (no they don't increase in number of processes with each build **
It says 49% but I have chrome running


How to increase Gesture Response Distance of Drawer in v4

Version
Tell us which versions you are using:

react-native-router-flux v4.0.0-beta.27 (v3 is not supported)
react-native v0.52

Expected behaviour
N/A
Actual behaviour
For increasing swipe back gesture response distance, we can do it by adding
          <Stack key="root" gesturesEnabled gestureResponseDistance={{horizontal: viewportWidth}}>
            <Scene key="splash" component={SplashScreen} />
          </Stack>

But now, i want to increase swipe open drawer gesture response distance, the gestureResponseDistance is not worked. And the documentation is not mentioned.
            <Scene key="drawer" gesturesEnabled gestureResponseDistance={{horizontal: viewportWidth}} hideDrawerButton drawer drawerWidth={200} drawerPosition="right" contentComponent={TopicDetailsSideMenu}>
              <Scene key="topicDetails" hideNavBar component={TopicDetailsScreen} />
            </Scene>

Is there any workaround here ? Thanks a lot.
Steps to reproduce
N/A

You really should check react navigation docs about this - RNRF just passes params to Drawer from react navigation


Fix component editing.

In commit<PHONE_NUMBER>9fc1c536e957ee79beada6974426ef this code was changed and in commit 80ac7f802bc925673a2e1a17ef738e5570760280 the condition was removed.
Fixes issue #455

This also fixes opening groups.


slice method of xgboost.DMatrix will change feature_names.

I find when use the slice method of xgb.DMatrix , the output DMatrix will change feature_names.
This behaviour is very strange. I think it should be fixed.
import numpy as np
import pandas as pd
import xgboost as xgb

data = pd.DataFrame(np.random.randn(5,3),columns = list('abc'))
dtrain = xgb.DMatrix(data)
dslice = dtrain.slice([0,1,2])
print(dtrain.feature_names)
print(dslice.feature_names)

the results is like this:

[u'a', u'b', u'c']
['f0', 'f1', 'f2']

Which version of XGBoost are you using?

@hcho3

Which version of XGBoost are you using?
0.80

The bug has been already fixed. You should upgrade to version 0.81.


Inverse trigonometric functions?

Looking to use asin or atan (to calculate distance between points on the sphere).
I don't see anything I could use in LASwift. Not sure if there is any advantage of having this in LASwift vs using Swift's own. Accelerate framework appears to have asin, for example: https://developer.apple.com/documentation/accelerate/asin

@AlexanderTar thank you!


ukmm: 0.8.2 -> 0.10.0

Description of changes
Update to the latest version: https://github.com/NiceneNerd/ukmm/releases/tag/v0.10.0
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
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

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

[x] Fits CONTRIBUTING.md.

@lasers

Result of nixpkgs-review run on x86_64-linux 1

17 packages failed to build:

cmake-language-server
cmake-language-server.dist
python310Packages.jedi-language-server
python310Packages.jedi-language-server.dist
python310Packages.pygls
python310Packages.pygls.dist
python310Packages.ruff-lsp
python310Packages.ruff-lsp.dist
python311Packages.jedi-language-server
python311Packages.jedi-language-server.dist
python311Packages.pygls
python311Packages.pygls.dist
python311Packages.ruff-lsp
python311Packages.ruff-lsp.dist
vimPlugins.YouCompleteMe
vscode-extensions.ms-python.python
ycmd

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

1 package built:

ukmm

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

1 package built:

ukmm


snoc parameter order should be reversed

Typical snoc seems to have the container as the first parameter and the element as the second, it's that way for DList, Vector, ByteString and others.

Yeah I know. The typical snoc also violates the convention of having the affected data-structure as the last parameter making the function unfit for piping. IOW the order of parameters in the typical snoc is a historic mistake. I don't want to proliferate it.


Handling data slicing at DataloaderIter.__next__ level

The current DataloaderIter class assumes that the Dataset's __getitem__ method can handle slicing and return batches of samples. This assumption causes compatibility issues with datasets that return a single sample which is usually the case. To resolve this, i think it's better to handle slicing within DataloaderIter __next__ method and keep __getitem__'s concern limited to returning a single sample.
The line causing errors is
batch = self.dataset[self.current_index:end]

The proposed solution is to modify __next__ to call __getitem__ multiple times to create a batch, maybe something that looks like this:
    def __next__(self):
        if self.total_yielded < self.total_yield:
            batch = []
            for _ in range(self.batch_size):
                if self.total_yielded >= self.total_yield:
                    break
                batch.append(self.dataset[self.current_index])
                self.current_index += 1
                self.total_yielded += 1
            return batch
        raise StopIteration

Thank you for looking into this issue and providing a solution. I've actually been relying on the same approach, and it works really great.
However, I initially thought this was just a temporary fix and not the way to go, as it didn't feel like the conventional approach used in deep learning frameworks such as PyTorch. Where users typically find the __getitem__ definition more intuitive since it returns a single sample, and then use other mechanisms such as the collate_fn function to handle slicing and batching.
That being said, I now see the benefits of implementing slicing within the __getitem__ method, such as making use of the slicing capabilities of most Python objects and keeping the dataset class more self-contained. I think this is a minor issue, and both approaches work just fine.

Alright, I'll keep this issue open for now.


Revert "Temporarily remove binary files for ghimport to work"

Stack from ghstack (oldest at bottom):

-> #334
#326
#322
#323
#333
#332
#329
#325

This reverts commit 9c327095f78000146895e77fb6f1dfe2c440f6a3.

Codecov Report

:exclamation: No coverage uploaded for pull request base (gh/langong347/63/base@f8b07e2). Click here to learn what that means.
Patch has no changes to coverable lines.

Additional details and impacted files
@@                   Coverage Diff                    @@
##             gh/langong347/63/base     #334   +/-   ##
========================================================
  Coverage                         ?   93.37%
========================================================
  Files                            ?       54
  Lines                            ?     3247
  Branches                         ?        0
========================================================
  Hits                             ?     3032
  Misses                           ?      215
  Partials                         ?        0

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


"Flag provided but not defined" doesn't give enough details

"Flag provided but not defined" doesn't give enough details for end users who aren't specifically aware of how CLIs work. I get a lot of bug reports that are "I got this obscure error message, and I'm not sure what to do".
See also

https://github.com/urfave/cli/issues/663
https://github.com/urfave/cli/issues/744

I'd like an opportunity to tackle this one. working on it now

@Zohvek yay cool! 🎉

Moving this one back to help wanted 📝

I can try working on this, but what kind of error exactly would be more explicit than this?
Something like:
"The flag 'v' was passed but you did not define an associated flag in the configuration for 'v'" ?
I'm not sure that is any better? Do you have any suggestions @lynncyrin ?

Duplicate of #427


cuda TypeError: 'NoneType' object is not callable

>>> import torch
>>> import torchsort
>>> x = torch.tensor([[8., 0., 5., 3., 2., 1., 6., 7., 9.]], requires_grad=True).cuda()
>>> y = torchsort.soft_sort(x)

Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/shuiy/anaconda3/envs/pytorch_py3/lib/python3.7/site-packages/torchsort/ops.py", line 48, in soft_sort
    return SoftSort.apply(values, regularization, regularization_strength)
  File "/home/shuiy/anaconda3/envs/pytorch_py3/lib/python3.7/site-packages/torchsort/ops.py", line 132, in forward
    sol = isotonic_l2[s.device.type](w - s)
TypeError: 'NoneType' object is not callable

on jupyter notebook is:
---------------------------------------------------------------------------
TypeError                                 Traceback (most recent call last)
/tmp/ipykernel_8938/1075883647.py in <module>
      1 x = torch.tensor([[8., 0., 5., 3., 2., 1., 6., 7., 9.]], requires_grad=True).cuda()
----> 2 y = torchsort.soft_sort(x)

~/anaconda3/envs/pytorch_py3/lib/python3.7/site-packages/torchsort/ops.py in soft_sort(values, regularization, regularization_strength)
     46     if regularization not in ["l2", "kl"]:
     47         raise ValueError(f"'regularization' should be a 'l2' or 'kl'")
---> 48     return SoftSort.apply(values, regularization, regularization_strength)
     49
     50

~/anaconda3/envs/pytorch_py3/lib/python3.7/site-packages/torchsort/ops.py in forward(ctx, tensor, regularization, regularization_strength)
    130         # note reverse order of args
    131         if ctx.regularization == "l2":
--> 132             sol = isotonic_l2[s.device.type](w - s)
    133         else:
    134             sol = isotonic_kl[s.device.type](w, s)

TypeError: 'NoneType' object is not callable

if x is on cpu(), run code is ok
python 3.7.10, pytorch  1.9.0 , cudatoolkit=11.1, ubuntu 18.04

Hi, it looks like your current version of torchsort doesn't have the cuda version built. Can you try reinstalling with:
pip install --force-reinstall --no-cache-dir torchsort

Hi, it looks like your current version of torchsort doesn't have the cuda version built. Can you try reinstalling with:
pip install --force-reinstall --no-cache-dir torchsort

I tried,  and RTX3060 warning, the problem may be about the RTX3060
>>> import torch
>>> import torchsort
>>> x = torch.tensor([[8., 0., 5., 3., 2., 1., 6., 7., 9.]], requires_grad=True).cuda()
GeForce RTX 3060 with CUDA capability sm_86 is not compatible with the current PyTorch installation.
The current PyTorch install supports CUDA capabilities sm_37 sm_50 sm_60 sm_70.
If you want to use the GeForce RTX 3060 GPU with PyTorch, please check the instructions at https://pytorch.org/get-started/locally/

  warnings.warn(incompatible_device_warn.format(device_name, capability, " ".join(arch_list), device_name))

and ,
>>> y = torchsort.soft_sort(x)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/shuiy/anaconda3/envs/pytorch_py3/lib/python3.7/site-packages/torchsort/ops.py", line 48, in soft_sort
    return SoftSort.apply(values, regularization, regularization_strength)
  File "/home/shuiy/anaconda3/envs/pytorch_py3/lib/python3.7/site-packages/torchsort/ops.py", line 126, in forward
    w = (_arange_like(tensor, reverse=True) + 1) / regularization_strength
  File "/home/shuiy/anaconda3/envs/pytorch_py3/lib/python3.7/site-packages/torchsort/ops.py", line 66, in _arange_like
    ar = torch.arange(x.shape[1] - 1, -1, -1, dtype=x.dtype, device=x.device)
RuntimeError: CUDA error: no kernel image is available for execution on the device
CUDA kernel errors might be asynchronously reported at some other API call,so the stacktrace below might be incorrect.
For debugging consider passing CUDA_LAUNCH_BLOCKING=1.

From https://pytorch.org/get-started/locally/ it looks like you need to install pytorch with:
conda install pytorch torchvision torchaudio cudatoolkit=11.1 -c pytorch -c nvidia

After which torchsort should hopefully work after reinstalling

Thanks，but，It still doesn't work.  I will use the cpu only

What error are you getting now?

the RTX3060 only can be installed like conda install pytorch torchvision torchaudio cudatoolkit=11.1 -c pytorch -c nvidia, >=cudatoolkit 11, from nvidia channel .
I installed the pytorch first time like this.
So, I guess the problem is about the incompatible with new cuda versions for RTX30xx

Hi, Yes I have had the same problem running on my GPU.

Please also see #35 for conda installation issues

i met the same issue

I realize now that initializing the functions to None if the function is not available (here) results in a very unhelpful error message when the kernel has not been compiled - I will add proper error handling here to inform the user that the cuda extension needs to be compiled


splash screen created

Created a splash screen with the color of the app and a logo I designed on Inkscape(based on the original logo). You can see the result on this image: https://i.imgur.com/LY4yM3y.png
the splash screen logo is a png file on the directory: android/app/src/main/res/drawable/splash_logo.png

@all-contributors please add @carlosfrodrigues for design


Correct the transport/storage namespace for document and scripts

Signed-off-by: myan<EMAIL_ADDRESS>

/lgtm

/hold

wait the confirmation from @clyang82

/retest

/unhold

/retest

/lgtm


MyPlotGenerator error

[x] This issue isn't duplicated - you can check if it is by using the search bar located at the top left hand corner and select "Issues" on the left.
[x] This issue includes appropriate markdown for sections - e.g. code blocks for crash dumps.
[x] This issue is understandable - feel free to use your native language to write issues if you are not comfortable with English.

Issue description
What problem do you have?
It does not generate the map.

Reproducing the issue

Generate new plots world
teleport new plots world

Client information
PocketMine-MP Version: PocketMine-MP 3.2.3
Plugin Version: 1.3.6
PHP version: 7.2.8

Optional information
[15:22:22] [Server thread/CRITICAL]: Could not execute asynchronous task GeneratorRegisterTask: Task crashed
[15:22:22] [Asynchronous Worker #1 thread/CRITICAL]: TypeError: "Argument 1 passed to MyPlot\MyPlotGenerator::__construct() must be of the type array, object given, called in phar://C:/Users/Crypthu/Desktop/Altay-master/Altay.phar/src/pocketmine/level/generator/GeneratorRegisterTask.php on line 58" (EXCEPTION) in "MyPlot-master/src/MyPlot/MyPlotGenerator" at line 30

i solved! :D


Apparently random occasional crashes while flying around in creative

OTG Plugin or Mod
OTG Mod for Forge
OTG Version
1.12.2_v8_r4
Forge or Spigot Versions
forge 1.12.2-<IP_ADDRESS>38
Server/Client Log
i hope this is the right file, it's the most recent date/time
from my logs folder. i included the crash report too
2019-08-31-7.log.gz
crash-2019-08-31_22.20.09-server.txt
edit: finally spotted the actual 'latest', my bad
latest.log
What other plugins are you running?
walljump-1.12.2-1.2.3
VerticalDimensionStack-1.12.2-0.1.5
superflatcaves-1.3.1
justenoughdimensions-1.12.2-1.6.0-dev.20190711.220109
CD4017BE_lib-1.12.2-6.4.8
BiomesOPlenty-1.12.2-<IP_ADDRESS>1-universal
AppleCore-mc1.12.2-3.2.0
Description
Random crashes when flying through a default OTG world in creative. Game freezes and I have to close it, then Minecraft gives a crash message afterwards. Both times happened while flying towards deserts. I believe I had the same mod combination both times, but only included the most recent crash, as the actual crash reports were identical.

Hey @inkdear, thanks for reporting this. Should be fixed for v8_r6, to be released on the dev channel of the OTG Discord at #openterraingen asap. V8 official release is expected within a week or two.


how to listen on a specific ip but not *?

I want to use a reverse proxy in fron of it. So it's better to listen on localhost but not *.

Fixed in pull request. Thanks!


reload -a make lost recent data

When I typed /denizen reload -a
unsaved data (flags and other) has lost

don't do that
use /denizen reload scripts


Users (16): Member edit permissions in Users

A Member user can only edit his own user, and needs the current password to be able to modify his own password and cannot delete it or add a new user

A user of type Member cannot create other users


Does Powerkey work with an old Mac Pro

I have a Mac Pro (early 2009) with a wireless Magic keyboard. By a devious route, I am running macOS 10.14.6. Can I install Powerkey to disable my DVD eject key which is too close to my BackSpace key for comfort! If so, you've got a sale 😉

... the app works perfectly on my old Mac Pro for disabling the Eject key with is perilously close to the backspace key. $5 well spent 😉

https://twitter.com/carlcaulkett/status/1263760715061571591

Yes, the app does work to disable or remap the eject key. Enjoy!


Cannot deploy from external environment - http: TLS handshake error - status_code=403

Bug description
When trying to deploy a stack from a seperate (non-local) agent environment, I receive a multitude of errors, the UI says failed to deploy a stack: listing workers for Build: failed to list workers: Unavailable: connection closed before server preface received
Expected behavior
My stack to deploy just like it does in the local environment
Portainer Logs
External:
2022/12/05 23:05:15 http: TLS handshake error from <local-env-ip>:37718: EOF

Local:
2022/12/05 11:05PM ERR github.com/portainer/portainer/api@v0.0.0-20221011053128-b0938875dc5c/http/client/client.go:94 > unexpected status code | status_code=403

Steps to reproduce the issue:

Go to a non-local environment
Go to stacks
Add a new stack
Click deploy
Observe error after a moment

Technical details:

Portainer version: 2.16.2 EE
Docker version (managed by Portainer): 20.10.12 (API: 1.41)
Kubernetes version (managed by Portainer): N/A
Platform (windows/linux): both linux x86_64 Ubuntu 22.04.1 LTS
Command used to start Portainer (docker run -p 9443:9443 portainer/portainer): The given for the agent, https://workbin.dev/?id=1670281882574271 for local env.
Browser:
Use Case (delete as appropriate): Using Portainer at Home.
Have you reviewed our technical documentation and knowledge base? Yes

Additional context
Add any other context about the problem here.

@ooliver1
Can you provide the following:
[1] Stack code
[2] Is this a Docker Swarm or Docker Standalone environment?
[3] Is the Agent running in the Environment?
[4] Screenshot of Toast
[5] Screenshot of the Web Dev Tools Network tab that shows API request and response message
Thanks!

#7240 seems to be unrelated, #7254 has the same error but the underlying logs include connection refused.
As I have mentioned before, this works on the local environment perfectly, but I would like this on the separate host.

https://github.com/eludris/thang
Standalone
Yes 94e81479b960   portainer/agent:2.16.2                 "./agent"                56 minutes ago   Up 56 minutes           <IP_ADDRESS>:9001->9001/tcp, :::9001->9001/tcp                                          portainer_agent

Yes

@ooliver1
I am able to reproduce the issue.  Local worked without error.  However, Docker Standalone Agent was not having it.
My message is a bit different though:
"failed to deploy a stack: time=\"2022-12-07T03:52:41Z\" level=warning msg=\"The \\\"DISCORD_CHANNEL_ID\\\" variable is not set. Defaulting to a blank string.\"\ntime=\"2022-12-07T03:52:41Z\" level=warning msg=\"The \\\"DISCORD_CHANNEL_ID\\\" variable is not set. Defaulting to a blank string.\"\ntime=\"2022-12-07T03:52:41Z\" level=warning msg=\"The \\\"DISCORD_TOKEN\\\" variable is not set. Defaulting to a blank string.\"\nkeydb Pulling \n40dd5be53814 Pulling fs layer \n4212448b221b Pulling fs layer \n84600…==========================>] 392B/392B\n126554b67430 Extracting [==================================================>] 392B/392B\n126554b67430 Pull complete \n85fcaa96f7c9 Extracting [==================================================>] 127B/127B\n85fcaa96f7c9 Extracting [==================================================>] 127B/127B\n85fcaa96f7c9 Pull complete \nkeydb Pulled \nlisting workers for Build: failed to list workers: Unavailable: connection closed before server preface received\n"

I need to further investigate.  I will update you as I learn more.
Thanks!

@ooliver1
Looks like the Docker Standalone Local is ignoring not having any variables set.  And, Docker Standalone Agent is requiring them as seen here:  https://github.com/Eludris/thang/blob/main/.env.example
Can you manually add these variables:

# REDIS_URL=redis://localhost:6379 # This is set to the service in docker compose.

# DISCORD_TOKEN= # Your Discord bot token
# DISCORD_CHANNEL_ID= # The id to the channel you want to send the messages to.
                    # This is temporary as eludris only has one channel.
# DISCORD_WEBHOOK_NAME="Eludris Bridge"  # The name of the webhook used to send messages.

# ELUDRIS_REST_URL=https://api.eludris.gay  # The HTTP uri for the eludris rest api.
# ELUDRIS_GATEWAY_URL=wss://ws.eludris.gay  # The websocket uri for the eludris gateway.

@ooliver1
For Docker Standalone Agent:  Can you send a screenshot of the variables entered and the error message on that screen?  I can not further test due that I do not have the Discord variables/information.
For Docker Standalone Local:  How are you entering the variables?  My build worked without variables.
Thanks!

I have sent the screenshot of the error above, I cannot give you the variables since one is a token. For local I am doing the exact same - via the UI.

Update:
This issue is currently being reviewed by Product.  I do not yet have a timeline or release.
Thanks!

I can confirm that this is related to build directive. It also fails if a stack is created directly in portainer if it contains build directive.
It fails on all environments connected via an agent.

Just an update, this still occurs in 2.18.1

I am in the same boat as @TsunayoshiSawada. Portainer seemed like a good solution for all projects until 30 minutes ago. Since portainer claims it can deploy stacks to agents, I didn't expect this to NOT work.

I'm encountering the same issue in the Community Edition: using relative build statements in my docker-compose.yml -> TLS error.
As of March 2023, Portainer supports relative builds in the Business Edition [1,2]. It is, hopefully, only a matter of time until it trickles down to the Community Edition.

I use the business edition using the free nodes program, and it was an issue for me in April. The versions should have similar fixes. Relative volumes do work, but this is about relative build paths.

Is there a work-around for this issue?

Internal Ref: EE-4758

Hi, is there an ETA on this fix? Or like @SeeJayEmm mentioned some workaround for the time being?

I just bumped up against this one.

I'm working on a GitHub Action that will deploy portainer stacks using the API as opposed to the Git integration which clearly doesn't work as expected.
It's still work in progress but I'll drop it here once it's done :)

Those that are running into issues when deploying stacks that contain build directives with relative paths, can you confirm whether the same issue occurs when you are deploying with the Relative path volumes option enabled? Note this is a BE-only feature. I've been doing some testing around this and want to confirm what I'm seeing.

Those that are running into issues when deploying stacks that contain build directives with relative paths, can you confirm whether the same issue occurs when you are deploying with the Relative path volumes option enabled? Note this is a BE-only feature. I've been doing some testing around this and want to confirm what I'm seeing.

Hello, we're encountering this aswell. We've tried with and without Relative path volumes.
Portainer Version 2.19.2
This error shows up when deploying without Relative path volumes enabled:

and this one appears with Relative path volumes enabled:

The issue is that portainer does not support deploying a stack with relative build paths. For instance, OP's docker-compose.yml file contains the following relative build path:
services:
  discord:
    <<: *service
    build:
      context: .
      dockerfile: discord/Dockerfile

... truncated

Per portainer's docs, building images while deploying from a git repo is not supported yet[1].
There are two workarounds:

Build the images individually[2] and reference the images in the docker-compose.yml file.
SSH into the portainer agent, pull the repo, and execute docker compose manually.

The second workaround raises the following warning: "This stack was created outside of Portainer. Control over this stack is limited". You can still stop/start/restart the containers and view logs, but lose access to many portainer features.
Hopefully we can see improvements made to stack deployments via git in the near future.
1: https://portal.portainer.io/knowledge/can-i-build-an-image-while-deploying-a-stack/application-from-git
2: https://docs.portainer.io/user/docker/images/build

Definitely not a stale issue. I literally ran into this last night and have spent the entire night fighting with Portainer BE.  It wouldn't deploy from a git repo without selecting the relative paths option.  Specifically I was trying to deploy stable-diffusion-webui-docker via Portainer instead of shell.  Without selecting that option it wouldn't deploy giving errors about the context or not being able to find the build directory where the Dockerfile was.
After selecting it, it seemed to deploy and load me into a false sense of security. The stack even worked to a extent.
And when I went to investigate, I learned that I could no longer issue commands to the agent or the server that was controlling the agent. They were giving 408s, connection close by peer, timeouts etc.
I was unable to stop the service containers that were running inside the stack, detach the git repo, stop the stack, or delete it via portainer. I wasn't able to modify or manipulate images or running containers. It would always time out. This is across reboots, as well as restarting Docker. These steps were done to both the server and the agent machine. I was also unable to remove the offending agent's Environment either.  Same result as any other attempt to make any changes.
Other than this portainer was quite responsive navigating around and doing anything that didn't require more than clicking through the interface.
I ended up having to remove all of the containers, images, and volumes related to that stack from shell. At which point Portainer showed they were gone but still would not let me detach the git repo, stop the stack (which it said was still running) or delete it.  I confirmed that this behavior was still being exhibited on the server as well as the agent.  I went ahead and tried restarting docker as well as the servers again and still same issue.
I was eventually able to regain control by purging the portainer agent.  I restarted the docker services on both ends again as well to be thorough.
And I was STILL unable to use the server or remove the Environment.  Once Portainer finally updated to show that Environment was unreachable, I was finally able to remove it from the server.
After, I deployed a new agent and both server and agent have seemed fine since.  Also, I was able to deploy the stack but I went ahead and cloned the repo and built the images first and then used them instead of building the stack during deployment.
I know it's not much info, but since last night when I was beating my head, I've been subscribed to this issue.  When I saw the bot comment this morning, the wound was still a little tender and I knew others were still having issues as well so rather than just bump, I wanted to try to give some info.  Or at least a decent story...

Yeah, the issue I personally find is not any sort of relative volumes or whatever, but the fact that the error is completely unrelated as it returns 403 without details.

Still not stale.


Update index.md to check Paraspell first delivery and completed

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Update Storage details

Update log messages for better clarity when encounter missing and/or corrupted files
Change data file name to socialbook.json

all codecov check warning pertains to log message edit. can be ignored


Implement SMTP hooks

See https://github.com/soywod/himalaya/discussions/177.

The concept could be extended to IMAP as well (#260).


Add tips for the "losted" dependencies .

Hi, @anseki .
Thank you for creating such an awesome library, I've read several dependencies-related issues. I think before we find a better solution, it is better to add a section in the README to indicate that  'modern' users should install the losted dependencies by themselves. Otherwise, it is quiet confusing and may cause a time-consuming debugging.

Hi @hapulb, thank you for your comment.
So, this library has no dependencies to run.
To use this, you have to execute this only:
npm i plain-draggable

But actually, the esm module do require some extra packages. And when using along with webpack(which you mean the 'modern' way), it complains that some modules cannot be resolved. I know that i could solve that manually by installing packages which is required but not in your dependencies list. And since this behavior is quiet unique to others, i here to ask maybe you can add some special hints to make other guys realizing this.

Generally speaking, developers that use Webpack require libraries to be bundled as development version. Then, the required additional packages for building are specified in PKG.devDependencies (dev means "development"). Those packages are installed automatically by npm install command.
This information is well known, and it is specification of NPM even if some developers don't know that.
Therefore, I think that the information should be not added to the README at the moment because it is not required and to avoid confusion.
However, I'll rethink it when more requests come.
Thank you for your proposal. :smile:

Well, but i still want to say, that is, packages listed under dependencies field should be which is need to help current package works as intended. So we should list anim-event as one of the dependencies because plain-draggable can't work in production without it, but we do not need webpack and its tool chains in production so we just list them as devDependencies. So finally, when users add your package via npm i, npm will only install packages listed under the dependencies field, using --save-dev or -D  just means adding your package into the devDependencies field of user's project, but any dependencies under your package's devDependencies will still be ignored. So how could i install those required dependecies manually? I have to add them to my project's dependencies or cd to your package under node_modules to execute npm i.  And this is the Spec of NPM, no offense. And thanks again for your patience.

The already bundled packages never should be added to PKG.dependencies.
Also, the PKG.devDependencies packages are installed automatically by npm install command, but current version of NPM doesn't support installing a package and its PKG.devDependencies packages at one time, as you said.
This is being discussed at times. A future version of NPM might support that.
Anyway, that information should be not added to libraries now, as with almost libraries.
Then, I close this issue for now. I will rethink it when more requests come. I still welcome comments.
Thank you again. :smile:

This library does not work out of the box... there are a ton of missing dependencies. Why has this issue been closed?

Hi @dbbk, thank you for your comment.
Please see: https://github.com/anseki/plain-draggable/issues/25#issuecomment-484334936

Thank you... I know how to install npm packages. Your package does not declare its dependencies, it is missing anim-event cssprefix m-class-list pointer-event. It seems like this issue keeps being raised by people, have you actually tried installing your own package?

This library has no dependencies to run.
Please see this again: https://github.com/anseki/plain-draggable/issues/25#issuecomment-484334936
You don't have to install those three packages to run because those were already bundled in this package.
Those packages are required only in development.
If you don't know "development" or PKG.devDependencies, please see document of NPM.

You keep saying that but it is not correct. Please just try and install your own project and use it.
It is plain to see if you just look at the code: https://github.com/anseki/plain-draggable/blob/master/plain-draggable.esm.js
The ESM version of plain-draggable is importing these packages, as you can see here: https://github.com/anseki/plain-draggable/blob/455d48dc0369c37d10d7e07cd8a2a33c12f1a1c8/plain-draggable.esm.js#L19
...but because they are listed as devDependencies in package.json, they do not get installed when someone installs and tries to use plain-draggable.

For example, see this page: https://anseki.github.io/plain-draggable/
You will see that those examples work fine. Then check that source code, and confirm that the three packages are not loaded.
Then, you should understand that those are not required.
One of your mistake is that you tried to use a file that is not bundled file.
Maybe you are trying to use the library with a development tool such as Webpack or another bundler. Of course those development tools require the development version such as ESM files. And, for development, the PKG.devDependencies packages are installed automatically by npm install command.
As I said, you don't have to install those three packages to run because those were already bundled in this package. Also, the bundled file is loaded via PKG.main.
See: https://github.com/anseki/plain-draggable/blob/master/package.json
In other words, only the PKG.main file is required to run, not plain-draggable.esm.js. That file for development, and the packages are required only in development.
I have to say again, please see document of NPM for "development" and PKG.devDependencies. Also, you have to understand the import mechanism (e.g. ESM) and the bundler.
This is important point for beginners in JS, NPM, Webpack, etc. And you have to learn that before you try to use any library in development.
@poor-branson proposed adding information for developers. Of course @poor-branson understand "development" and PKG.devDependencies.

I'm not a beginner, I have 13 years of experience. I understand JavaScript, Webpack and NPM fine.
From the sounds of it you seem confused about the ESM module, is your point that nobody should use this? If so you should remove it from module and jsnext:main in package.json, because this is what Webpack is importing when it looks at your package.
Again, I would urge you to please just try importing your own library in a new Webpack / Rollup / whatever project, and see that it crashes, rather than proclaiming that everyone is just a beginner who doesn't understand how to install things.

Sorry, you are not beginner, but maybe you are misunderstanding the mechanism of the import (e.g. ESM) and the bundler.
Why you use "ESM" file? Maybe you don't think that you are trying to use the library in development version. The development tools such as Webpack require the development version such as ESM files, it is understandably not bundled yet.
Did you try the PKG.main file? Not in development, the PKG.main file that was already bundled is used.  (i.e. you don't have to install the three packages.)
Or, do you mean that the three packages were not installed by npm install command?

I'm not explicitly choosing to use the ESM file, it's Webpack that is selecting it because as I mentioned it's declared as the module and jsnext:main in package.json

The development tools such as Webpack require the development version such as ESM files.
You have to understand this.

Well no, they don't require ESM, but nonetheless if they use the ESM build it doesn't work because, as mentioned earlier, the dependencies used by this package are listed as devDependencies and thus do not get installed when a user installs this package.
It's really not complicated, I think you're confused along one or more lines... I'm just going to fork the package and fix it for myself.

I think that the tips is not needed for now because almost developers know the PKG.devDependencies packages are installed automatically by npm install command.
However, of course you can customize it if you don't like typical package.
Anyway, thank you for your comments. :smile:

almost developers know the PKG.devDependencies packages are installed automatically by npm install command

I genuinely have no idea what you're talking about. This doesn't happen.  I give up.

Sorry, my English is poor.
I mean, generally speaking, developers use the npm install command to install the PKG.devDependencies packages.
I already asked you: https://github.com/anseki/plain-draggable/issues/25#issuecomment-488243929
Do you mean that the three packages were not installed by npm install command?
If so, your NPM might be broken, or your computer might have a problem.


ci: pin: downstream: 2nd party: Successful pin

Related: https://github.com/dffml/dffml-model-transformers/pull/3

Forked to use runner capacity in other org


ESMF_Initialize() and ESMF_Finalize() mismatch

ESMF_Initialize() is called under the communicator model_comm, but the ESMF_Finalize() is called under world_comm. When GEOSgcm main branch is run with the command
$RUN_CMD 48 $GEOSBIN/GEOSgcm.x --npes_model 24 --oserver_type multigroup --nodes_output_server 1 --npes_backend_pernode 4 --logging_config 'logging.yaml'
the error messages are printed at the end.
ESMF_LogWrite(): ESMF_Log not open -- cannot ESMF_LogWrite(). Log message =
Finalizing ESMF
...
...
ESMF_Finalize: Error writing into the default log
ESMF_Finalize: Error flushing log file: Operation not yet supported
ESMF_Finalize: Error flushing log file: Operation not yet supported
ESMF_LogWrite(): ESMF_Log not open -- cannot ESMF_LogWrite(). Log message =
Finalizing ESMF
ESMF_LogWrite(): ESMF_Log not open -- cannot ESMF_LogWrite(). Log message =
Internal error: Bad condition - - Invalid GlobalVM
ESMF_Finalize: Error finalizing VM: Internal error: Bad condition
pe=00029 FAIL at line=00425 MAPL_Cap.F90 <status=18>
pe=00029 FAIL at line=00131 MAPL_Cap.F90 <status=18>
pe=00029 FAIL at line=00032 GEOSgcm.F90 <status=18>
ESMF_Finalize: Error flushing log file: Operation not yet supported
ESMF_LogWrite(): ESMF_Log not open -- cannot ESMF_LogWrite(). Log message =
Internal error: Bad condition - - Invalid GlobalVM
ESMF_Finalize: Error finalizing VM: Internal error: Bad condition

ok - do you have a fix?   They certainly should both be the same.  Eventually both will become world_comm, but for now they should both be world_comm.

I haven't found a fix even I tried many ways yesterday. I would try again

initialization does not have the condition this%mpi_already_initialized, why finalize need it?  @tclune @mathomp4
 if (.not. this%mpi_already_initialized) then
     call MAPL_Finalize(comm=this%comm_world)
     call ESMF_Finalize(rc=status)
      _VERIFY(status)
  end if


Implement HandleProtectionErrorMiddleware.

Fixes #2411

Wait. We may have to create a middleware directory. Let me test this once.

This works too!

Codecov Report

Merging #2412 (6a7f052) into main (a64e0ef) will increase coverage by 0.00%.
The diff coverage is 85.71%.

@@           Coverage Diff           @@
##             main    #2412   +/-   ##
=======================================
  Coverage   81.82%   81.82%
=======================================
  Files         621      621
  Lines       22241    22255   +14
=======================================
+ Hits        18198    18210   +12
- Misses       4043     4045    +2

Impacted Files
Coverage Δ

hypha/settings/base.py
70.53% <ø> (ø)

hypha/apply/middleware.py
88.00% <85.71%> (-2.91%)
:arrow_down:

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 a64e0ef...6a7f052. Read the comment docs.


Better handling of s3 relation

This seems to be a duplicate of https://github.com/canonical/postgresql-operator/issues/129 so could be closed since that issue is already resolved.
Steps to reproduce

juju deploy postgresql (revision 288 was used)
juju deploy s3-integrator
juju run-action s3-integrator/leader sync-s3-credentials access-key=<access-key> secret-key=<secret-key> --wait
juju config s3-integrator <key>=<value>
juju relate s3-integrator postgresql

At this point because of firewall rules, my postgres unit could not talk to my Radosgw server and it was pending for a while with the status saying initialising stanza until eventually the status changed to Blocked with a message failed to initialize stanza.
After fixing the firewall rules I am unable to set up backups as I don't know how to get Postgres to retry the setup. Attempts to remove the s3-integrator relation and re-add it fail, as log messages state couldn't initialize stanza due to a blocked status. See below for all the logs.
Finally, trying  juju run-action postgresql/0 list-backups --wait caused an exception (logs also available below).
Expected behavior
Expected that I can trigger Postgres to retry the connection to Swift storage somehow.
Actual behavior
See above.
Versions
Operating system: Ubuntu 22.04.2 LTS
Juju CLI: 2.9.42
Juju agent: 2.9.42
Charm revision: 288
LXD: N/A
Log output
Failed to reach Radosgw

unit-ubuntu-advantage-0: 06:54:35 INFO juju.worker.uniter.operation ran "update-status" hook (via hook dispatching script: dispatch)
unit-landscape-client-0: 06:55:18 INFO juju.worker.uniter.operation skipped "update-status" hook (missing)
unit-s3-integrator-0: 06:55:23 DEBUG unit.s3-integrator/0.juju-log Operator Framework 2.3.0 up and running.
unit-s3-integrator-0: 06:55:23 DEBUG unit.s3-integrator/0.juju-log Emitting Juju event update_status.
unit-s3-integrator-0: 06:55:23 INFO juju.worker.uniter.operation ran "update-status" hook (via hook dispatching script: dispatch)
unit-s3-integrator-0: 06:55:55 DEBUG unit.s3-integrator/0.juju-log Operator Framework 2.3.0 up and running.
unit-s3-integrator-0: 06:55:55 DEBUG unit.s3-integrator/0.juju-log Emitting Juju event sync_s3_credentials_action.
unit-s3-integrator-0: 06:55:55 DEBUG unit.s3-integrator/0.juju-log Updated S3 connection info: {'access-key': 'redacted'}
unit-s3-integrator-0: 06:55:55 DEBUG unit.s3-integrator/0.juju-log Updated S3 connection info: {'secret-key': 'redacted'}
unit-s3-integrator-0: 06:55:56 DEBUG unit.s3-integrator/0.juju-log s3-integrator-peers:0: Operator Framework 2.3.0 up and running.
unit-s3-integrator-0: 06:55:56 DEBUG unit.s3-integrator/0.juju-log s3-integrator-peers:0: Emitting Juju event s3_integrator_peers_relation_changed.
unit-s3-integrator-0: 06:55:56 INFO unit.s3-integrator/0.juju-log s3-integrator-peers:0: Missing options: []
unit-postgresql-0: 06:55:57 DEBUG unit.postgresql/0.juju-log s3-parameters:6: Operator Framework 2.2.0 up and running.
unit-postgresql-0: 06:55:57 DEBUG unit.postgresql/0.juju-log s3-parameters:6: Emitting Juju event s3_parameters_relation_changed.
unit-postgresql-0: 06:55:57 DEBUG unit.postgresql/0.juju-log s3-parameters:6: Emitting custom event <CredentialsChangedEvent via PostgresqlOperatorCharm/S3Requirer[s3-parameters]/on/credentials_changed[6765]>.
unit-s3-integrator-0: 06:55:57 INFO juju.worker.uniter.operation ran "s3-integrator-peers-relation-changed" hook (via hook dispatching script: dispatch)
unit-s3-integrator-0: 07:00:42 DEBUG unit.s3-integrator/0.juju-log Operator Framework 2.3.0 up and running.
unit-s3-integrator-0: 07:00:42 DEBUG unit.s3-integrator/0.juju-log Emitting Juju event update_status.
unit-s3-integrator-0: 07:00:44 INFO juju.worker.uniter.operation ran "update-status" hook (via hook dispatching script: dispatch)
unit-postgresql-0: 07:03:59 ERROR unit.postgresql/0.juju-log s3-parameters:6: ERROR: [049]: timeout connecting to 'radosgw.ps5.canonical.com:443'

unit-postgresql-0: 07:04:06 INFO juju.worker.uniter.operation ran "s3-parameters-relation-changed" hook (via hook dispatching script: dispatch)
unit-telegraf-0: 07:04:07 INFO unit.telegraf/0.juju-log Reactive main running for hook update-status

Remove and re-add relation

unit-data-integrator-0: 08:14:58 INFO juju.worker.uniter.operation ran "postgresql-relation-changed" hook (via hook dispatching script: dispatch)
unit-s3-integrator-0: 08:18:22 INFO juju.worker.uniter.operation ran "s3-credentials-relation-departed" hook (via hook dispatching script: dispatch)
unit-postgresql-0: 08:18:22 INFO juju.worker.uniter.operation ran "s3-parameters-relation-departed" hook (via hook dispatching script: dispatch)
unit-s3-integrator-0: 08:18:24 INFO juju.worker.uniter.operation ran "s3-credentials-relation-broken" hook (via hook dispatching script: dispatch)
unit-postgresql-0: 08:18:25 INFO juju.worker.uniter.operation ran "s3-parameters-relation-broken" hook (via hook dispatching script: dispatch)
unit-landscape-client-0: 08:18:36 INFO juju.worker.uniter.operation skipped "update-status" hook (missing)
unit-ubuntu-advantage-0: 08:18:39 INFO juju.worker.uniter.operation ran "update-status" hook (via hook dispatching script: dispatch)
unit-s3-integrator-0: 08:18:54 INFO juju.worker.uniter.operation ran "s3-credentials-relation-created" hook (via hook dispatching script: dispatch)
unit-s3-integrator-0: 08:18:55 INFO juju.worker.uniter.operation ran "s3-credentials-relation-joined" hook (via hook dispatching script: dispatch)
unit-postgresql-0: 08:18:55 INFO juju.worker.uniter.operation ran "s3-parameters-relation-created" hook (via hook dispatching script: dispatch)
unit-s3-integrator-0: 08:18:56 INFO juju.worker.uniter.operation ran "s3-credentials-relation-changed" hook (via hook dispatching script: dispatch)
unit-postgresql-0: 08:18:58 INFO juju.worker.uniter.operation ran "s3-parameters-relation-joined" hook (via hook dispatching script: dispatch)
unit-s3-integrator-0: 08:18:59 INFO juju.worker.uniter.operation ran "s3-credentials-relation-changed" hook (via hook dispatching script: dispatch)
unit-postgresql-0: 08:19:00 WARNING unit.postgresql/0.juju-log s3-parameters:13: couldn't initialize stanza due to a blocked status
unit-postgresql-0: 08:19:02 INFO juju.worker.uniter.operation ran "s3-parameters-relation-changed" hook (via hook dispatching script: dispatch)
unit-postgresql-0: 08:19:04 WARNING unit.postgresql/0.juju-log s3-parameters:13: couldn't initialize stanza due to a blocked status
unit-postgresql-0: 08:19:11 INFO juju.worker.uniter.operation ran "s3-parameters-relation-changed" hook (via hook dispatching script: dispatch)

Attempted to list backups

unit-telegraf-0: 08:19:50 INFO juju.worker.uniter.operation ran "update-status" hook (via explicit, bespoke hook script)
unit-postgresql-0: 08:21:16 ERROR unit.postgresql/0.juju-log Uncaught exception while in charm code:
Traceback (most recent call last):
  File "/var/lib/juju/agents/unit-postgresql-0/charm/./src/charm.py", line 1028, in <module>
    main(PostgresqlOperatorCharm)
  File "/var/lib/juju/agents/unit-postgresql-0/charm/venv/ops/main.py", line 441, in main
    _emit_charm_event(charm, dispatcher.event_name)
  File "/var/lib/juju/agents/unit-postgresql-0/charm/venv/ops/main.py", line 149, in _emit_charm_event
    event_to_emit.emit(*args, **kwargs)
  File "/var/lib/juju/agents/unit-postgresql-0/charm/venv/ops/framework.py", line 354, in emit
    framework._emit(event)
  File "/var/lib/juju/agents/unit-postgresql-0/charm/venv/ops/framework.py", line 830, in _emit
    self._reemit(event_path)
  File "/var/lib/juju/agents/unit-postgresql-0/charm/venv/ops/framework.py", line 919, in _reemit
    custom_handler(event)
  File "/var/lib/juju/agents/unit-postgresql-0/charm/src/backups.py", line 434, in _on_list_backups_action
    formatted_list = self._generate_backup_list_output()
  File "/var/lib/juju/agents/unit-postgresql-0/charm/src/backups.py", line 186, in _generate_backup_list_output
    backups = json.loads(output)[0]["backup"]
IndexError: list index out of range

Just an update on this. I upgrade the charm to channel 14/candidate and revision 307. The unit status has changed to an error but when I try juju resolve postgresql/0 I get the following in juju debug-log
unit-postgresql-0: 09:44:14 INFO juju.worker.uniter awaiting error resolution for "relation-changed" hook
unit-telegraf-0: 09:44:15 INFO juju.worker.uniter.operation ran "update-status" hook (via explicit, bespoke hook script)
unit-postgresql-0: 09:44:19 ERROR unit.postgresql/0.juju-log s3-parameters:14: Uncaught exception while in charm code:
Traceback (most recent call last):
  File "/var/lib/juju/agents/unit-postgresql-0/charm/./src/charm.py", line 1224, in <module>
    main(PostgresqlOperatorCharm)
  File "/var/lib/juju/agents/unit-postgresql-0/charm/venv/ops/main.py", line 441, in main
    _emit_charm_event(charm, dispatcher.event_name)
  File "/var/lib/juju/agents/unit-postgresql-0/charm/venv/ops/main.py", line 149, in _emit_charm_event
    event_to_emit.emit(*args, **kwargs)
  File "/var/lib/juju/agents/unit-postgresql-0/charm/venv/ops/framework.py", line 354, in emit
    framework._emit(event)
  File "/var/lib/juju/agents/unit-postgresql-0/charm/venv/ops/framework.py", line 830, in _emit
    self._reemit(event_path)
  File "/var/lib/juju/agents/unit-postgresql-0/charm/venv/ops/framework.py", line 919, in _reemit
    custom_handler(event)
  File "/var/lib/juju/agents/unit-postgresql-0/charm/lib/charms/data_platform_libs/v0/s3.py", line 694, in _on_relation_changed
    credentials = self.get_s3_connection_info()
  File "/var/lib/juju/agents/unit-postgresql-0/charm/lib/charms/data_platform_libs/v0/s3.py", line 711, in get_s3_connection_info
    relation = self.charm.model.get_relation(self.relation_name)
  File "/var/lib/juju/agents/unit-postgresql-0/charm/venv/ops/model.py", line 249, in get_relation
    return self.relations._get_unique(relation_name, relation_id)
  File "/var/lib/juju/agents/unit-postgresql-0/charm/venv/ops/model.py", line 769, in _get_unique
    raise TooManyRelatedAppsError(relation_name, num_related, 1)
ops.model.TooManyRelatedAppsError: Too many remote applications on s3-parameters (2 > 1)
unit-postgresql-0: 09:44:20 ERROR juju.worker.uniter.operation hook "s3-parameters-relation-changed" (via hook dispatching script: dispatch) failed: exit status 1
unit-postgresql-0: 09:44:20 INFO juju.worker.uniter awaiting error resolution for "relation-changed" hook

Before this I did remove the relation with juju remove-relation s3-integrator postgresql --force and re-add it hoping that would fix it. I wonder if that might have caused the relation information to become inconsistent.
Next I tried scaling the cluster with juju add-unit postgresql -n 1 and then new unit is stuck on waiting to start Postgresql while the leader is still in an error state.
Finally I decided to try juju resolve postgresql/0 --no-retry and Postgres moved on from failing that initial hook but is now stuck on the database-peers-relation-changed hook with the same error as before (logs below),
unit-postgresql-0: 09:47:40 ERROR unit.postgresql/0.juju-log database-peers:2: Uncaught exception while in charm code:
Traceback (most recent call last):
  File "/var/lib/juju/agents/unit-postgresql-0/charm/./src/charm.py", line 1224, in <module>
    main(PostgresqlOperatorCharm)
  File "/var/lib/juju/agents/unit-postgresql-0/charm/venv/ops/main.py", line 441, in main
    _emit_charm_event(charm, dispatcher.event_name)
  File "/var/lib/juju/agents/unit-postgresql-0/charm/venv/ops/main.py", line 149, in _emit_charm_event
    event_to_emit.emit(*args, **kwargs)
  File "/var/lib/juju/agents/unit-postgresql-0/charm/venv/ops/framework.py", line 354, in emit
    framework._emit(event)
  File "/var/lib/juju/agents/unit-postgresql-0/charm/venv/ops/framework.py", line 830, in _emit
    self._reemit(event_path)
  File "/var/lib/juju/agents/unit-postgresql-0/charm/venv/ops/framework.py", line 919, in _reemit
    custom_handler(event)
  File "/var/lib/juju/agents/unit-postgresql-0/charm/./src/charm.py", line 362, in _on_peer_relation_changed
    if not self.backup.start_stop_pgbackrest_service():
  File "/var/lib/juju/agents/unit-postgresql-0/charm/src/backups.py", line 800, in start_stop_pgbackrest_service
    are_backup_settings_ok, _ = self._are_backup_settings_ok()
  File "/var/lib/juju/agents/unit-postgresql-0/charm/src/backups.py", line 79, in _are_backup_settings_ok
    if self.model.get_relation(self.relation_name) is None:
  File "/var/lib/juju/agents/unit-postgresql-0/charm/venv/ops/model.py", line 249, in get_relation
    return self.relations._get_unique(relation_name, relation_id)
  File "/var/lib/juju/agents/unit-postgresql-0/charm/venv/ops/model.py", line 769, in _get_unique
    raise TooManyRelatedAppsError(relation_name, num_related, 1)
ops.model.TooManyRelatedAppsError: Too many remote applications on s3-parameters (2 > 1)
unit-postgresql-0: 09:47:41 ERROR juju.worker.uniter.operation hook "database-peers-relation-changed" (via hook dispatching script: dispatch) failed: exit status 1
unit-postgresql-0: 09:47:41 INFO juju.worker.uniter awaiting error resolution for "relation-changed" hook

Which all seems to come back to the inconsistent state of relation data. I would appreciate if there is any resolution to this issue.

And the output of `juju status --relations`

Model                        Controller    Cloud/Region           Version  SLA          Timestamp
prod-product-attribution-db  prodstack-is  prodstack5/prodstack5  2.9.42   unsupported  09:50:49Z

App               Version  Status  Scale  Charm             Channel        Rev  Exposed  Message
data-integrator            active      1  data-integrator   latest/stable   11  no
landscape-client           active      2  landscape-client  stable          49  no       System successfully registered
postgresql        14.8     active      2  postgresql        14/stable      307  yes
s3-integrator              active      1  s3-integrator     latest/stable   13  yes
telegraf                   active      2  telegraf          stable          62  yes      Monitoring postgresql/0 (source version/commit d208a64)
ubuntu-advantage           active      2  ubuntu-advantage  stable          43  no       Attached (esm-apps,esm-infra,livepatch)

Unit                   Workload  Agent  Machine  Public address  Ports     Message
data-integrator/0*     active    idle   3        <IP_ADDRESS>
postgresql/0*          error     idle   1        <IP_ADDRESS>   5432/tcp  hook failed: "database-peers-relation-changed"
  landscape-client/0*  active    idle            <IP_ADDRESS>             System successfully registered
  telegraf/0*          active    idle            <IP_ADDRESS>   9103/tcp  Monitoring postgresql/0 (source version/commit d208a64)
  ubuntu-advantage/0*  active    idle            <IP_ADDRESS>             Attached (esm-apps,esm-infra,livepatch)
postgresql/1           waiting   idle   4        <IP_ADDRESS>            waiting to start PostgreSQL
  landscape-client/1   active    idle            <IP_ADDRESS>            System successfully registered
  telegraf/1           active    idle            <IP_ADDRESS>  9103/tcp  Monitoring postgresql/1 (source version/commit d208a64)
  ubuntu-advantage/1   active    idle            <IP_ADDRESS>            Attached (esm-apps,esm-infra,livepatch)
s3-integrator/0*       active    idle   0        <IP_ADDRESS>

Machine  State    Address         Inst id                               Series  AZ                   Message
0        started  <IP_ADDRESS>   a18308ff-cdb8-428f-85d8-c75a559803b7  jammy   availability-zone-3  ACTIVE
1        started  <IP_ADDRESS>   e2135e08-cb26-444a-a19b-56dcb4fa1003  jammy   availability-zone-1  ACTIVE
3        started  <IP_ADDRESS>  9ad1cba0-a7b5-420b-a166-f7459351cc3e  jammy   availability-zone-2  ACTIVE
4        started  <IP_ADDRESS>  0c3d7fb8-e4fb-4c4b-9065-d1c1e1e54cc8  jammy   availability-zone-2  ACTIVE

Offer       Application  Charm       Rev  Connected  Endpoint  Interface          Role
postgresql  postgresql   postgresql  307  1/1        database  postgresql_client  provider

Relation provider                      Requirer                               Interface              Type         Message
data-integrator:data-integrator-peers  data-integrator:data-integrator-peers  data-integrator-peers  peer
postgresql:database                    data-integrator:postgresql             postgresql_client      regular
postgresql:database-peers              postgresql:database-peers              postgresql_peers       peer
postgresql:juju-info                   landscape-client:container             juju-info              subordinate
postgresql:juju-info                   telegraf:juju-info                     juju-info              subordinate
postgresql:juju-info                   ubuntu-advantage:juju-info             juju-info              subordinate
postgresql:restart                     postgresql:restart                     rolling_op             peer
s3-integrator:s3-integrator-peers      s3-integrator:s3-integrator-peers      s3-integrator-peers    peer

In the end I was able to get through this hook as well with another juju resolve postgresql/0 --no-retry and I removed the extra unit and Postgres is in an active state again (still with no backups configured).
I tried now to juju relate s3-integrator postgresql but still the issue persists.
unit-postgresql-0: 10:03:42 ERROR unit.postgresql/0.juju-log s3-parameters:16: Uncaught exception while in charm code:
Traceback (most recent call last):
  File "/var/lib/juju/agents/unit-postgresql-0/charm/./src/charm.py", line 1224, in <module>
    main(PostgresqlOperatorCharm)
  File "/var/lib/juju/agents/unit-postgresql-0/charm/venv/ops/main.py", line 441, in main
    _emit_charm_event(charm, dispatcher.event_name)
  File "/var/lib/juju/agents/unit-postgresql-0/charm/venv/ops/main.py", line 149, in _emit_charm_event
    event_to_emit.emit(*args, **kwargs)
  File "/var/lib/juju/agents/unit-postgresql-0/charm/venv/ops/framework.py", line 354, in emit
    framework._emit(event)
  File "/var/lib/juju/agents/unit-postgresql-0/charm/venv/ops/framework.py", line 830, in _emit
    self._reemit(event_path)
  File "/var/lib/juju/agents/unit-postgresql-0/charm/venv/ops/framework.py", line 919, in _reemit
    custom_handler(event)
  File "/var/lib/juju/agents/unit-postgresql-0/charm/lib/charms/data_platform_libs/v0/s3.py", line 694, in _on_relation_changed
    credentials = self.get_s3_connection_info()
  File "/var/lib/juju/agents/unit-postgresql-0/charm/lib/charms/data_platform_libs/v0/s3.py", line 711, in get_s3_connection_info
    relation = self.charm.model.get_relation(self.relation_name)
  File "/var/lib/juju/agents/unit-postgresql-0/charm/venv/ops/model.py", line 249, in get_relation
    return self.relations._get_unique(relation_name, relation_id)
  File "/var/lib/juju/agents/unit-postgresql-0/charm/venv/ops/model.py", line 769, in _get_unique
    raise TooManyRelatedAppsError(relation_name, num_related, 1)
ops.model.TooManyRelatedAppsError: Too many remote applications on s3-parameters (3 > 1)
unit-postgresql-0: 10:03:43 ERROR juju.worker.uniter.operation hook "s3-parameters-relation-changed" (via hook dispatching script: dispatch) failed: exit status 1
unit-postgresql-0: 10:03:43 INFO juju.worker.uniter awaiting error resolution for "relation-changed" hook

I'll leave it at that. I have the model running in an environment in case more debug logs or tweaks are helpful.

Hi, was this model used before or was in a clean model? It looks to me that s3 library believes it's related to multiple s3-integrator apps.

This was a clean model. I.e. everything described above was started from a clean environment. After the initial error there were attempts to juju remove-relation s3-integrator postgresql --force (sometimes with using --force) and then attempts to re-relate the two. It's possible doing these in somewhat quick succession (i.e. I waited less than a minute before remove-relation then relate) caused the state to become incorrect.

We'll most probably need to pass the relationship id in the s3 lib as well, to make sure we can't hit this exception in the future. Thanks for reporting this.

@dragomirp Thank you!


Allocation ignores alignment requirements

When implementing the GlobalAlloc::alloc function for SpinPalloc and UnsafeCellPalloc, the alignment requirement of the provided layout is ignored. This can lead to undefined behaviour.

This project was made by me in my first day of low-level programming and as time passed I realized this very mistake but never decided to fix it. I was wondering when someone would actually notice it lol.


[FLINK-27579][client] The param client.timeout can not be set by dyna…

…mic properties when stopping the job

What is the purpose of the change
Fix the issue that the dynamic properties parsed from command line are ignored when execution Flink action(run/stop etc.)
Currently dynamic properties only affect defaultParallelism and clientTimeout.
Brief change log

flink-clients/src/main/java/org/apache/flink/client/cli/CliFrontend.java

Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changed class annotated with @Public(Evolving): no
The serializers: no
The runtime per-record code paths (performance sensitive): no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature? no

@flinkbot run azure

@flinkbot run azure

@paul8263 The pr looks good to me. I have left some minor suggestions. Can you add some tests for the feature? Thanks.

@flinkbot run azure

Hi @wangyang0918 ,
Could you please review this PR? Thanks.

Hi @wangyang0918 ,
Could you please review this PR? Thanks.

@flinkbot run azure

@flinkbot run azure

@flinkbot run azure


(InkScape) Inkscape 1.3.1 to 1.3.2: Status still "Waiting for Maintainer" since last update (four weeks)

Chocolatey Version
2.2.2
Chocolatey License
None
Package Version
1.3.1 to 1.3.2
Current Behaviour
Status still "Waiting for Maintainer" since last update
Expected Behaviour
Status "Approved" (and fully available)
Steps To Reproduce
doesn't apply
Environment
doesn't apply

Chocolatey Log
doesn't apply

Anything else?
No response

Inkscape 1.3.1 and 1.3.2 are approved.


Having 3 trade should be equal to 2 gold & 1 science

It should be:
1 trade = 1 gold
2 trade = 1 gold + 1 science
3 trade = 2 gold + 1 science
4 trade = 2 gold + 2 science
5 trade = 3 gold + 2 science
...

This depends on your tax rate.  Was it 50% at the time of this screenshot?

Confirmed, see below:
This is the original game, with 0.5.5:

This is CivOne, with 0.5.5:

Civilizations favours gold over science. I will fix this.


Add CodeSigningConfig resource

Issue aws-controllers-k8s/community#238
Description of changes:

Adds create, delete and update operations for CodeSigningConfig
resource in the AWS Lambda API.
Adds end2end tests to deploy lambda code signing configurations
using ACK controller.

By submitting this pull request, I confirm that my contribution is made
under the terms of the Apache 2.0 license.
Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

This resource was generated by making small changes to the code-generator.
/hold for now

/lgtm

/unhold


use categories from other Treant when creating a new one

The following code fails for me.
import datreant.core as dtr

t = dtr.Treant('foo', categories={'a', 'foo'})
d = dtr.Treant('bar', categories=t.categories)

I get a TypeError that non-keyword argument must be dict

@kain88-de I think this should definitely be fixed, but as a simple workaround you could do:
import datreant.core as dtr

t = dtr.Treant('foo', categories={'a', 'foo'})

# this will work
d = dtr.Treant('bar', categories=dict(t.categories))

# alternatively
d = dtr.Treant('bar')
d.categories = t.categories