React Native project initial compilation error

Hi,
I created a new React Native project and ran it in Xcode. I get following error in the terminal and can't figure how to fix:
ERROR  EACCES, permission denied '/Users/andrey.pokrovskiy/.babel.json'
{"errno":3,"code":"EACCES","path":"/Users/andrey.pokrovskiy/.babel.json","syscall":"open"}
Error: EACCES, permission denied '/Users/andrey.pokrovskiy/.babel.json'
at Object.fs.openSync (evalmachine.:438:18)
at Object.fs.writeFileSync (evalmachine.:977:15)
at save (/Users/andrey.pokrovskiy/Desktop/lab/NewiOsApp/node_modules/react-native/node_modules/babel-core/lib/api/register/cache.js:35:19)
at process._tickCallback (node.js:419:13)
at Function.Module.runMain (module.js:499:11)
at startup (node.js:119:16)
at node.js:906:3
I've tried chown the file and looked for a solution but no luck.
Meanwhile Xcode throws Apple Mach-o linker error with 25 errors inside.
I never worked with Xcode so have no clue what that means.
Seemingly easy installation turned into a nightmare for me.
Any help would be appreciated!

Hi there! You're best off trying out StackOverflow for this kind of question because I don't believe this is an issue with React Native, but rather the system configuration on your end - if it turns out to be a bug then please come back here and ping me and we can investigate further :smile: In addition to StackOverflow, there are some other issues that may be useful for you: https://github.com/facebook/react-native/issues?utf8=✓&q=EACCES

sudo chmod 777 /Users/xxxx/.babel.json

yes baby....it works great..thanks
sudo chmod 777 /Users/username/.babel.json
and again react-native init

yes baby....it works great..thanks
sudo chmod 777 /Users/username/.babel.json
and again react-native init


[5.2] Encryption: Test the IV length in invalidPayload method

Lately, I have upgraded my website from L 4.2.11 to the latest one. The Encryption cipher used before was MCRYPT_RIJNDAEL_128 which uses an IV with a length of 32. Since the payload in the cookies in users was encrypted using the old cipher, the EncryptCookies middleware threw an exception with this trace:
production.ERROR: exception 'ErrorException' with message 'openssl_decrypt(): IV passed is 32 bytes long which is longer than the 16 expected by selected cipher, truncating' in /home/www/MY/vendor/laravel/framework/src/Illuminate/Encryption/Encrypter.php:95
Stack trace:
#0 [internal function]: Illuminate\Foundation\Bootstrap\HandleExceptions->handleError(2, 'openssl_decrypt...', '/home/www/...', 95, Array)
#1 /home/www/MY/vendor/laravel/framework/src/Illuminate/Encryption/Encrypter.php(95): openssl_decrypt('Dbyr0401XlXcY6N...', 'AES-256-CBC', 'VyZn2WxfW9UgMrI...', 0, 'h\x82\x9Co\t\x9Fqx\\\x84\x8B\x16\x8B\x82P...')
#2 /home/www/MY/vendor/laravel/framework/src/Illuminate/Cookie/Middleware/EncryptCookies.php(95): Illuminate\Encryption\Encrypter->decrypt('eyJpdiI6ImFJS2N...')
#3 /home/www/MY/vendor/laravel/framework/src/Illuminate/Cookie/Middleware/EncryptCookies.php(76): Illuminate\Cookie\Middleware\EncryptCookies->decryptCookie('eyJpdiI6ImFJS2N...')
#4 /home/www/MY/vendor/laravel/framework/src/Illuminate/Cookie/Middleware/EncryptCookies.php(59): Illuminate\Cookie\Middleware\EncryptCookies->decrypt(Object(Illuminate\Http\Request))
#5 [internal function]: Illuminate\Cookie\Middleware\EncryptCookies->handle(Object(Illuminate\Http\Request), Object(Closure))
#6 /home/www/MY/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(124): call_user_func_array(Array, Array)
#7 [internal function]: Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#8 /home/www/MY/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(103): call_user_func(Object(Closure), Object(Illuminate\Http\Request))
#9 /home/www/MY/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php(122): Illuminate\Pipeline\Pipeline->then(Object(Closure))
#10 /home/www/MY/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php(87): Illuminate\Foundation\Http\Kernel->sendRequestThroughRouter(Object(Illuminate\Http\Request))
#11 /home/www/MY/public/index.php(54): Illuminate\Foundation\Http\Kernel->handle(Object(Illuminate\Http\Request))
#12 {main}

The obvious and simple trick would be to wrap the openssl_decrypt() in Encrypter.php:95 in a try catch block throwing a DecryptException exception, but this could be prevented since the beginning in the invalidPayload() method in the BaseEncrypter class by testing the length of the IV.
Since getIvSize() is used in the invalidPayload() method in the abstract invalidPayload() class, I declared it as an abstract method in it.
I would go ahead and define getIvSize() in the baseEnrypter class using openssl_cipher_iv_length() method, since the IV length might change in the future depending on the cipher declared in the config file.
At the end, I believe this might be considered as supporting an old version of laravel which is no longer done.

Please send to 5.1.

Okay


restructure composite models folders

suggestion to restructure folders for composite models, for example, action-recognition-0001. This will allow avoid duplication in description and highlight the fact that each separate part of composite model makes no sense. They solve the task being run in sequence only.

Generally, I'm ok, too.
After we merge this and other combined networks, let's think about how to handle "families" of models (like, person reid)

Jenkins please retry a build

postponed till 2020.3 release. Do not merge for 2020.2 release


Added from address verification, RFC 5322 From: header

Closes #7
What needs to happen to move this forward as a release?
Signed-off-by: Todd Campbell<EMAIL_ADDRESS>

@portertech could you review at your convenience?

@nixwiz Thank you so much 👍


refactor: [M3-8648] – Migrate Paper to ui package

Description 📝
Migrate Paper from manager to ui package.
Target release date 🗓
11/12/24
How to test 🧪
Verification steps

All tests should pass
There should be no adverse impacts observed in Cloud

As an Author I have considered 🤔

[X] 👀 Doing a self review
[X] ❔ Our contribution guidelines
[X] 🤏 Splitting feature into small PRs
[X] ➕ Adding a changeset
[X] 🧪 Providing/Improving test coverage
[X] 🔐 Removing all sensitive information from the code and PR description
[X] 🚩 Using a feature flag to protect the release
[X] 👣 Providing comprehensive reproduction steps
[X] 📑 Providing or updating our documentation
[X] 🕛 Scheduling a pair reviewing session
[X] 📱 Providing mobile support
[X] ♿  Providing accessibility support

Putting this back into draft status until the errors related to omittedProps are worked through


Windows phone 8.1, not works

Hi, I've used nuget version Reactive extension (https://www.nuget.org/packages/Rx-Core/2.2.5), not sure if the same of this or not, bytheway for windows phone 8.1 and not works,
the message is can't find  "... corerx.dll into portable/ etc." seems that portable library aren't compiled for universal app/windows phone 8.1.
So I download this repository and try to compile, but no luck, too many errors, any idea...??

Did you solve this already? I have the same issue.

#148 will work on Wpa81

Fixed in 3.0, shipping on the 27th


release-0.14: examples/ reference image 0.14.1 not 0.14.2

I forgot to update the Contour image version when doing the release.
What should we do? Publish a 0.14.3, or change the tag? At a minimum we should ensure HEAD of the release-0.14 branch points to 0.14.2.

Fixed in cf2e3cdabeba1783e39ccb84f50485d3f0c9ccb4


hashing, fix bisect on py3

fixes: #766

Looks good at first glance, this code is duplicated in graphite-web so you'll want to open a PR there also.

Codecov Report

Merging #778 into master will increase coverage by 0.12%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #778      +/-   ##
==========================================
+ Coverage   50.15%   50.27%   +0.12%
==========================================
  Files          36       36
  Lines        3306     3306
  Branches      471      471
==========================================
+ Hits         1658     1662       +4
+ Misses       1542     1540       -2
+ Partials      106      104       -2

Impacted Files
Coverage Δ

lib/carbon/hashing.py
88.42% <100%> (+4.21%)
:arrow_up:

Continue to review full report at Codecov.

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

@DanCech What about removing the code from graphite-web and importing from carbon? is there some reason why that is not wanted except for web depending on carbon?

That's possible, but please note that carbon requires e.g. Twisted, so, it will bring more dependencies to graphite-web. Not the end of the world, though.

Hmm, will leave it separate for now.

There's a stray swp file in the commit

removed the swp file


v0.3.0 release changes

Resolves https://github.com/rancher/charts-build-scripts/issues/35, https://github.com/rancher/charts-build-scripts/issues/46, https://github.com/rancher/charts-build-scripts/issues/56, https://github.com/rancher/charts-build-scripts/issues/61, https://github.com/rancher/charts-build-scripts/issues/62, https://github.com/rancher/charts-build-scripts/issues/63

https://github.com/rancher/charts-build-scripts/issues/54 is technically resolved, but not done in the way prescribed in the issue. Since we are moving to a newer system-charts model, there's no definition of what "validating charts" are, so instead the new behavior is to force a failure on validation if a chart is not included in the release.yaml.
Therefore, when rebasing charts, a developer will:

Try to do the rebase
See make validate fail
Update the release.yaml; the hope is that a developer would also catch here that the older, unrebased, unreleased version of the chart still exists
Remove the old chart with the new make remove command.

https://github.com/rancher/charts-build-scripts/issues/33 is no longer a concern since we just flat-out do not allow comments in Chart.yaml anymore. It will be overwritten on a make prepare, since that's what would happen when we run a helm package anyways on the chart.

Related Issue: https://github.com/rancher/charts-build-scripts/issues/60

package-ci finally passed! Seems like this PR is good to go without any further changes, other than those pointed out during a review.

Thanks for the comments @jiaqiluo! Ready for a re-review here.
I resolved all the comments where I just took your changes verbatim.
For anything else, I left comments and left unresolved above; feel free to resolve them if you agree or comment if you disagree.
All changes you suggested have been added to the last two commits I just pushed.

address edge cases brought up in https://github.com/rancher/charts-build-scripts/pull/66#pullrequestreview-809043347 around tgz files within CRD charts being modified...


Launch empty simulation

Added a world and launch files to be able to launch a webots simulation using ROS 2 commands.
The launchfile contains the basic commands to launch webots and the ROS2Supervisor node, used to expand Webots features with ROS 2.
A README is added to the package to keep track of the added features and changes.

Is it ready to review?

Is it ready to review?

Yes! Sorry for not tagging you


Creating dynamo table for install activity data

Addresses https://github.com/chanzuckerberg/napari-hub/issues/867

Description
The PR adds infrastructure changes to create a dynamoDb table for install activity with the required hash_key=plugin_name and range_key=type_timestamp.  It also provides the backend API with permission to query the table.

shouldn't these tables be managed by internal infra and one per environment?

@potating-potato hmm so would this be better suited in https://github.com/chanzuckerberg/sci-imaging-infra?

Yeah that's what I am wondering about. I don't have a concrete suggestion here either but would ask Manasa to think about the tradeoff and make a decision

shouldn't these tables be managed by internal infra and one per environment?
@potating-potato  As the dynamo stream from some of the future tables will trigger the lambda, having the tables one per environment is no longer a viable solution.  :(
Instead, we will maintain a single dev environment that the team will share.


Critical section

试图对mutex做优化的结果。意义不是很大，但应该不会更慢。

Please remove build artifact, such as *.o and *.d

sorry忘记了。刚刚冷静一下觉得这分支还是不merge比较好

As far as I know, std::mutex is backed by CriticalSection in Windows and backed by pthread_mutex in linux. It's basicly what you've done in critical_section.hpp.


Make overlay driver work without a kv store

Currently overlay driver requires a k/v store to allocate a vxlan id and
add an entry in k/v store for network->vxlanIDs binding. But the overlay
driver should be able to work without a k/v store provided libnetwork
can pass along the vxlanIDs needed for the network, rather than the
driver managing it themselves. Modified the driver to work with vxlanIDs
passed down by libnetwork.
Also made changes in the driver to make use of the gossip layer
available in libnetwork if available.
Signed-off-by: Jana Radhakrishnan<EMAIL_ADDRESS>

LGTM

@mrjana: this might be an orthogonal question - but how does/should libnetwork manage the VNIDs? Does this mean that libnetwork will now have a dependency on a k/v store backend. Unsure butthat dependency is probably already there, no?

@rhim The goal here is to make overlay driver and even libnetwork not depend on a k/v store. If a k/v store is available libnetwork and overlay driver should be able to make use of it. But libnetwork and overlay driver should be able to provide multi-host networking even if no k/v store is available and that might indeed be useful and makes libnetwork lot more useful in scenarios where it is not useful now. This does mean that the VNIs and their allocation becomes somebody's responsibility. But that is fine. Libnetwork itself becomes less opinionated.

@rhim BTW libnetwork will not manage VNIs either because it is driver agnostic so this does mean that it had to me managed by the caller of libnetwork in whatever way that had to be managed.

LGTM


state transition performed twice when using optional state parameters

When optional state parameters are defined for a state, the state transition is performed twice as long as the optional parameters.
The $stateParams of a controller that was called twice look like this:
First: {offset: undefined, limit: undefined, sort: undefined, sortby: undefined}
Second: {offset: 0, limit: 20, sort: "asc", sortby: "title"}
Note that all state parameters are optional and defined like this.
.state({
  name: "list.products",
  parent: "list",
  url: "/products/:offset/:limit/:sortby/:sort/",
  params: {
    offset: { value: 0 },
    limit: { value: 20 },
    sort: { value: 'asc' },
    sortby: { value: 'title' }
  },
  templateUrl: "views/partials/product-search-result-item.html",
  controller: "ListProductsController"
})

When I use ui-sref without any parameter the controller is called twice.
Products
Using all state parameters the controller is called only once.
Products
IMHO this is a bug and I hope somebody can fix it as all controllers with optional parameters and API calls make API requests twice.

Hi,  I'm seeing this when using version 0.2.13.  Instead of using ui-sref I have am using ng-click to call a function which then calls $state.go().  I can also confirm this when using $state.transitionTo().
ng-click="selectAlert(alert)
var selectAlert = function(alert){
$state.go('app.alerts.list.detail', {alertId: alert.id});
}
Does this bug still exist or am I using this incorrectly?

I had same problem like @nolandubeau . version is 0.2.11.
call $state.go in ng-click.  some $state parameters are null.
Seems to be fixed in 0.2.14.

i am still getting the same problem in 0.2.15 ,is the problem fixed or still persist ,please help me with this one

I also am getting this problem in 0.2.15. I am using custom types in my solution.
The code which is resulting in the transition not being skipped, is in shouldSkipReload, line 3606.
(locals === from.locals || ....)
Something is causing them to not be equal once the $locationChangeSuccess event is fired.

Please make a plunker

+1, have the same problem in 0.2.15.

its working fine with 0.2.14,

I have a simple state with a resolve with a simple parameter. When I refresh the page (like url/state/paramId) the resolve is executed twice.
0.2.14 0.2.10 0.2.15, same error, this is executed twice. It won't work neither with :paramId, {paramId} or ?paramId=id.

I agree with pranaydutta89; for me using version 0.2.14 instead if 0.2.15 fixes my issue.
There does seem to be another issue here, which I am looking into.

@christopherthielen I have a Plunkr which demonstrates what I'm trying to do to make some sort of dynamic parameters work in 0.2.15. http://plnkr.co/edit/Yeex1Rmd1nWQvdrxj87N?p=preview. It works to change parameters syncronously, but not via a $timeout.

Im getting this problem in 0.2.15.
Using 0.2.14. fixed the problem to me.

+1 Same for me, I had to go back to 0.2.14 to fix the problem

+1 Same here

Actually it's also happening in the version 0.2.14 even though this version looks more stable than the 0.2.15.

Can confirm this for version 0.2.15. When using nested views and a parameter is present in ui-sref, then the parent resolve function is fired for a second time. Removing the parameter makes it work as expected.

+1 here too

Can also confirm on 0.2.15

@bryanerayner Thanks for the plunker, but this ticket is about "state transition performed twice when using optional state parameters".  Your plunker is demonstrating some other issue with reloadOnSearch (we only seem to support one level of reloadOnSearch at a time).  Dynamic parameters are scheduled for the 1.0 release.
Also, you should use inherit: true so you don't lose your current parameters.
http://plnkr.co/edit/hMRjZSnLrjnCKnI5eqeT?p=preview

To the rest of you who have +1'd or said "me too", I need you to reproduce this double-transition issue in a plunker.  This ticket is closed, the original issue was resolved, and I don't have any usable information to go on to fix the +1s

Im getting this problem in 0.2.15.


Emotes for ;userinfo

Is your feature request related to a problem? Please describe.
I miss the bot-js emotes.

bot-kt, currently
Describe the solution you'd like
I would like to see the emotes back onto ;userinfo like this:

bot-js

I'd rather not have hardcoded emojis that somebody has to provide somewhere.

It's alright 👍


add failure output

This will report failures instead of early exit.
Example:
test
Updated

Name
Old Version
New Version

foo
0
1

Ignored

Name
Path

bar
baz

Failed

Name
Path
Message

foo
bar
baz

Closing in discussion with @phillebaba


SRE Course from Google Cloud Week 1

Recommended pace of the course is two weeks, taking 4 hours a week.

[x] Week 1


issue with OpenGL applications crashing when using Hyprland 0.42.0 on Asahi linux.

Regression?
Yes
System Info and Version
 System/Version info
Hyprland, built from branch  at commit 9a09eac79b85c846e3a865a9078a3f8ff65a9259  (props: bump version to 0.42.0).
Date: Wed Aug 7 19:17:10 2024
Tag: v0.42.0, commits: 5069

flags: (if any)

System Information:
System name: Linux
Node name: fedora
Release: 6.9.12-401.asahi.fc40.aarch64+16k
Version: #1 SMP PREEMPT_DYNAMIC Sat Aug  3 22:26:24 UTC 2024

GPU information:
apple,agx-t8103

os-release: NAME="Fedora Linux Asahi Remix"
VERSION="40 (Forty)"
ID=fedora-asahi-remix
ID_LIKE=fedora
VERSION_ID=40
VERSION_CODENAME=""
PLATFORM_ID="platform:f40"
PRETTY_NAME="Fedora Linux Asahi Remix 40 (Forty)"
ANSI_COLOR="0;38;2;60;110;180"
LOGO=fedora-logo-icon
CPE_NAME="cpe:/o:fedoraproject:fedora-asahi-remix:40"
DEFAULT_HOSTNAME="fedora"
HOME_URL="https://fedora-asahi-remix.org/"
DOCUMENTATION_URL="https://docs.fedoraproject.org/en-US/fedora/f40/system-administrators-guide/"
SUPPORT_URL="https://discussion.fedoraproject.org/c/neighbors/asahi/asahi-help/94"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_BUGZILLA_PRODUCT="Fedora"
REDHAT_BUGZILLA_PRODUCT_VERSION=40
REDHAT_SUPPORT_PRODUCT="Fedora"
REDHAT_SUPPORT_PRODUCT_VERSION=40

# █▀▀ █▄░█ █░█
# ██▄ █░▀█ ▀▄▀
#----------------------------------------------------------------------
env = CLUTTER_BACKEND,wayland
env = GDK_BACKEND,wayland
env = QT_AUTO_SCREEN_SCALE_FACTOR,1
env = QT_QPA_PLATFORM,wayland
env = QT_QPA_PLATFORMTHEME,kde
env = QT_SCALE_FACTOR,1.2                      # QT 앱의 scale을 설정
env = QT_WAYLAND_DISABLE_WINDOWDECORATION,1
env = XDG_CURRENT_DESKTOP,Hyprland
env = XDG_SESSION_DESKTOP,Hyprland
env = XDG_SESSION_TYPE,wayland

env = GDK_SCALE,1
env = XCURSOR_SIZE,32

env = GTK_IM_MODULE,fcitx
env = QT_IM_MODULE,fcitx
env = XMODIFIERS=@im,fcitx

# firefox
#----------------------------------------------------------------------
env = MOZ_ENABLE_WAYLAND,1

general {
  sensitivity         = 1.00
  apply_sens_to_raw   = 1
  gaps_in             = 10
  gaps_out            = 220
  border_size         = 2
  resize_on_border    = true

  col.active_border   = rgba(a895c4ff)
  col.inactive_border = rgba(ffffff00)

  layout              = master
}

dwindle {
  pseudotile           = false
  force_split          = 2
  preserve_split       = false
  special_scale_factor = 1.0
  default_split_ratio  = 1.0
  smart_split          = true
}

master {
  new_on_top           = false
  orientation          = center
  always_center_master = true
  mfact                = 0.45
  smart_resizing       = false
}

group {
  col.border_active = $color15
        groupbar {
        col.active = $color0
  }
}

debug {
  damage_tracking  = 2
  disable_logs     = false
  disable_time     = true
  watchdog_timeout = 0
}

decoration {
  rounding            = 0
  active_opacity      = 1.0
  inactive_opacity    = 0.9
  fullscreen_opacity  = 1.0
  dim_inactive        = true
  dim_strength        = 0.1 Right Win, Super to Menu
  drop_shadow         = false
  shadow_range        = 80
  shadow_render_power = 50
  shadow_offset       = 8, 10
  shadow_scale        = 0.987

  blur {
  enabled           = true
  size              = 4
  passes            = 4
  ignore_opacity    = true
  brightness        = 0.5
  new_optimizations = true
  }
}

input {
  kb_layout                   = kr
  kb_variant                  =
  kb_model                    =
  kb_options                  = grp:alt_shift_toggle, ctrl:swap_lwin_lctl
  kb_rules                    =
  repeat_rate                 = 50
  repeat_delay                = 300
  numlock_by_default          = 1
  left_handed                 = 0
  follow_mouse                = 1
  float_switch_override_focus = 0
  accel_profile               = adaptive
  sensitivity                 = -0.8
}

misc {
  disable_hyprland_logo    = true
  disable_splash_rendering = true
  mouse_move_enables_dpms  = true
  background_color         = 0x050106
  vrr                      = 2
  vfr                      = true
  enable_swallow           = true
  focus_on_activate        = false
  swallow_regex            = ^(foot)$
  #disable_autoreload      = true
}

binds {
  workspace_back_and_forth = 1
  allow_workspace_cycles   = 1
  pass_mouse_when_bound    = 0
}

#Could help when scaling and not pixelating
xwayland {
    force_zero_scaling = true
}

# █▀▀ ▀▄▀ █▀▀ █▀▀
# ██▄ █░█ ██▄ █▄▄
exec-once     = ln -s /run/user/1000/hypr /tmp/hypr
exec-once     = tmux setenv -g HYPRLAND_INSTANCE_SIGNATURE "$HYPRLAND_INSTANCE_SIGNATURE"
exec-once     = /home/elsa/.local/bin/wpaperd -d
exec-once     = dbus-update-activation-environment --systemd WAYLAND_DISPLAY
exec-once     = systemctl --user import-environment WAYLAND_DISPLAY
exec-once     = xprop -root -f _XWAYLAND_GLOBAL_OUTPUT_SCALE 32c -set _XWAYLAND_GLOBAL_OUTPUT_SCALE 2
exec-once     = swaync
exec-once     = fcitx5
exec-once     = /home/elsa/.local/bin/mpd
exec-once     = wl-paste --type text  --watch cliphist store
exec-once     = wl-paste --type image --watch cliphist store
exec-once     = sudo iw dev wlp1sof0 set power_save off
exec-once     = /home/elsa/.config/eww/eww-run.sh
exec-once     = swayidle -w timeout 3600 hyprlock
exec-once     = pypr

Description
The recent release of Hyprland 0.42.0 introduced significant changes, with the most notable being the switch from wlroots to aquamarine. However, this update has caused issues on Asahi Linux, where applications that use OpenGL, such as Firefox, Kitty, wpaperd or Chromium …, are no longer running properly. The current workaround involves disabling GPU acceleration by running “export LIBGL_ALWAYS_SOFTWARE=1” and only  launch app in terminal(foot terminal),
How to reproduce
Applications related to OpenGL do not run properly when launched from Rofi or a terminal, while non-OpenGL applications work without issues.
Crash reports, logs, images, videos
❯ WAYLAND_DEBUG=1 kitty
[1665393.321] {Default Queue}  -> wl_display#1.get_registry(new id wl_registry#2)
[1665393.347] {Default Queue}  -> wl_display#1.sync(new id wl_callback#3)
[1665393.895] {Display Queue} wl_display#1.delete_id(3)
[1665393.900] {Default Queue} wl_registry#2.global(1, "wl_seat", 9)
[1665393.903] {Default Queue}  -> wl_registry#2.bind(1, "wl_seat", 9, new id [unknown]#4)
[1665393.906] {Default Queue} wl_registry#2.global(2, "wl_data_device_manager", 3)
[1665393.908] {Default Queue}  -> wl_registry#2.bind(2, "wl_data_device_manager", 1, new id [unknown]#5)
[1665393.911] {Default Queue}  -> wl_data_device_manager#5.get_data_device(new id wl_data_device#6, wl_seat#4)
[1665393.913] {Default Queue} wl_registry#2.global(3, "wl_compositor", 6)
[1665393.915] {Default Queue}  -> wl_registry#2.bind(3, "wl_compositor", 6, new id [unknown]#7)
[1665393.917] {Default Queue} wl_registry#2.global(4, "wl_subcompositor", 1)
[1665393.919] {Default Queue}  -> wl_registry#2.bind(4, "wl_subcompositor", 1, new id [unknown]#8)
[1665393.921] {Default Queue} wl_registry#2.global(5, "wl_shm", 1)
[1665393.923] {Default Queue}  -> wl_registry#2.bind(5, "wl_shm", 1, new id [unknown]#9)
[1665393.926] {Default Queue} wl_registry#2.global(6, "wp_viewporter", 1)
[1665393.928] {Default Queue}  -> wl_registry#2.bind(6, "wp_viewporter", 1, new id [unknown]#10)
[1665393.930] {Default Queue} wl_registry#2.global(7, "wp_tearing_control_manager_v1", 1)
[1665393.932] {Default Queue} wl_registry#2.global(8, "wp_fractional_scale_manager_v1", 1)
[1665393.934] {Default Queue}  -> wl_registry#2.bind(8, "wp_fractional_scale_manager_v1", 1, new id [unknown]#11)
[1665393.936] {Default Queue} wl_registry#2.global(9, "zxdg_output_manager_v1", 3)
[1665393.938] {Default Queue} wl_registry#2.global(10, "wp_cursor_shape_manager_v1", 1)
[1665393.940] {Default Queue}  -> wl_registry#2.bind(10, "wp_cursor_shape_manager_v1", 1, new id [unknown]#12)
[1665393.943] {Default Queue} wl_registry#2.global(11, "zwp_idle_inhibit_manager_v1", 1)
[1665393.945] {Default Queue} wl_registry#2.global(12, "zwp_relative_pointer_manager_v1", 1)
[1665393.948] {Default Queue}  -> wl_registry#2.bind(12, "zwp_relative_pointer_manager_v1", 1, new id [unknown]#13)
[1665393.951] {Default Queue} wl_registry#2.global(13, "zxdg_decoration_manager_v1", 1)
[1665393.958] {Default Queue}  -> wl_registry#2.bind(13, "zxdg_decoration_manager_v1", 1, new id [unknown]#14)
[1665393.960] {Default Queue} wl_registry#2.global(14, "wp_alpha_modifier_v1", 1)
[1665393.962] {Default Queue} wl_registry#2.global(15, "zwlr_gamma_control_manager_v1", 1)
[1665393.964] {Default Queue} wl_registry#2.global(16, "ext_foreign_toplevel_list_v1", 1)
[1665393.965] {Default Queue} wl_registry#2.global(17, "zwp_pointer_gestures_v1", 3)
[1665393.967] {Default Queue} wl_registry#2.global(18, "zwlr_foreign_toplevel_manager_v1", 3)
[1665393.971] {Default Queue} wl_registry#2.global(19, "zwp_keyboard_shortcuts_inhibit_manager_v1", 1)
[1665393.974] {Default Queue} wl_registry#2.global(20, "zwp_text_input_manager_v1", 1)
[1665393.995] {Default Queue} wl_registry#2.global(21, "zwp_text_input_manager_v3", 1)
[1665393.997] {Default Queue}  -> wl_registry#2.bind(21, "zwp_text_input_manager_v3", 1, new id [unknown]#15)
[1665393.999] {Default Queue} wl_registry#2.global(22, "zwp_pointer_constraints_v1", 1)
[1665394.001] {Default Queue}  -> wl_registry#2.bind(22, "zwp_pointer_constraints_v1", 1, new id [unknown]#16)
[1665394.004] {Default Queue} wl_registry#2.global(23, "zwlr_output_power_manager_v1", 1)
[1665394.006] {Default Queue} wl_registry#2.global(24, "xdg_activation_v1", 1)
[1665394.008] {Default Queue}  -> wl_registry#2.bind(24, "xdg_activation_v1", 1, new id [unknown]#17)
[1665394.010] {Default Queue} wl_registry#2.global(25, "ext_idle_notifier_v1", 1)
[1665394.015] {Default Queue} wl_registry#2.global(26, "ext_session_lock_manager_v1", 1)
[1665394.018] {Default Queue} wl_registry#2.global(27, "zwp_input_method_manager_v2", 1)
[1665394.023] {Default Queue} wl_registry#2.global(28, "zwp_virtual_keyboard_manager_v1", 1)
[1665394.026] {Default Queue} wl_registry#2.global(29, "zwlr_virtual_pointer_manager_v1", 2)
[1665394.031] {Default Queue} wl_registry#2.global(30, "zwlr_output_manager_v1", 4)
[1665394.036] {Default Queue} wl_registry#2.global(31, "org_kde_kwin_server_decoration_manager", 1)
[1665394.042] {Default Queue} wl_registry#2.global(32, "hyprland_focus_grab_manager_v1", 1)
[1665394.043] {Default Queue} wl_registry#2.global(33, "zwp_tablet_manager_v2", 1)
[1665394.045] {Default Queue} wl_registry#2.global(34, "zwlr_layer_shell_v1", 5)
[1665394.053] {Default Queue}  -> wl_registry#2.bind(34, "zwlr_layer_shell_v1", 5, new id [unknown]#18)
[1665394.064] {Default Queue} wl_registry#2.global(35, "wp_presentation", 1)
[1665394.072] {Default Queue} wl_registry#2.global(36, "xdg_wm_base", 6)
[1665394.074] {Default Queue}  -> wl_registry#2.bind(36, "xdg_wm_base", 6, new id [unknown]#19)
[1665394.076] {Default Queue} wl_registry#2.global(37, "zwlr_data_control_manager_v1", 2)
[1665394.080] {Default Queue} wl_registry#2.global(38, "zwp_primary_selection_device_manager_v1", 1)
[1665394.088] {Default Queue}  -> wl_registry#2.bind(38, "zwp_primary_selection_device_manager_v1", 1, new id [unknown]#20)
[1665394.090] {Default Queue}  -> zwp_primary_selection_device_manager_v1#20.get_device(new id zwp_primary_selection_device_v1#21, wl_seat#4)
[1665394.093] {Default Queue} wl_registry#2.global(39, "xwayland_shell_v1", 1)
[1665394.096] {Default Queue} wl_registry#2.global(40, "zwlr_screencopy_manager_v1", 3)
[1665394.101] {Default Queue} wl_registry#2.global(41, "hyprland_toplevel_export_manager_v1", 2)
[1665394.103] {Default Queue} wl_registry#2.global(42, "hyprland_global_shortcuts_manager_v1", 1)
[1665394.105] {Default Queue} wl_registry#2.global(43, "wp_drm_lease_device_v1", 1)
[1665394.107] {Default Queue} wl_registry#2.global(44, "wp_linux_drm_syncobj_manager_v1", 1)
[1665394.113] {Default Queue} wl_registry#2.global(45, "wl_drm", 2)
[1665394.117] {Default Queue} wl_registry#2.global(47, "wl_output", 4)
[1665394.119] {Default Queue}  -> wl_registry#2.bind(47, "wl_output", 2, new id [unknown]#22)
[1665394.121] {Default Queue} wl_callback#3.done(894)
[1665394.126] {Default Queue}  -> zwp_text_input_manager_v3#15.get_text_input(new id zwp_text_input_v3#3, wl_seat#4)
[1665394.132] {Default Queue}  -> wl_display#1.sync(new id wl_callback#23)
[1665394.391] {Display Queue} wl_display#1.delete_id(23)
[1665394.394] {Default Queue} wl_seat#4.name("Hyprland")
[1665394.395] {Default Queue} wl_seat#4.capabilities(3)
[1665394.397] {Default Queue}  -> wl_seat#4.get_pointer(new id wl_pointer#24)
[1665394.400] {Default Queue}  -> wp_cursor_shape_manager_v1#12.get_pointer(new id wp_cursor_shape_device_v1#25, wl_pointer#24)
[1665394.402] {Default Queue}  -> wl_seat#4.get_keyboard(new id wl_keyboard#26)
[1665394.404] {Default Queue} discarded wl_shm#9.format(0)
[1665394.406] {Default Queue} discarded wl_shm#9.format(1)
[1665394.407] {Default Queue} discarded wl_shm#9.format(808669761)
[1665394.409] {Default Queue} discarded wl_shm#9.format(808669784)
[1665394.410] {Default Queue} discarded wl_shm#9.format(808665665)
[1665394.412] {Default Queue} discarded wl_shm#9.format(808665688)
[1665394.413] {Default Queue} discarded wl_shm#9.format(875708993)
[1665394.415] {Default Queue} discarded wl_shm#9.format(875709016)
[1665394.416] {Default Queue} wl_output#22.geometry(0, 0, 1600, 900, 0, "", "", 0)
[1665394.419] {Default Queue} wl_output#22.scale(1)
[1665394.421] {Default Queue} wl_output#22.mode(3, 4096, 2160, 60000)
[1665394.424] {Default Queue} wl_output#22.done()
[1665394.425] {Default Queue} wl_callback#23.done(894)
[1665394.428] {Default Queue}  -> wl_compositor#7.create_surface(new id wl_surface#23)
[1665433.411] {Default Queue}  -> wl_compositor#7.create_surface(new id wl_surface#27)
[1665433.423] {Default Queue}  -> wp_fractional_scale_manager_v1#11.get_fractional_scale(new id wp_fractional_scale_v1#28, wl_surface#27)
[1665433.431] {Default Queue}  -> wp_viewporter#10.get_viewport(new id wp_viewport#29, wl_surface#27)
[1665433.434] {Default Queue}  -> wl_surface#27.set_buffer_scale(1)
[1665434.771]  -> wl_display#1.get_registry(new id wl_registry#30)
[1665434.779]  -> wl_display#1.sync(new id wl_callback#31)
[1665435.501] {Display Queue} wl_display#1.delete_id(31)
[1665435.509] wl_registry#30.global(1, "wl_seat", 9)
[1665435.511] wl_registry#30.global(2, "wl_data_device_manager", 3)
[1665435.513] wl_registry#30.global(3, "wl_compositor", 6)
[1665435.516] wl_registry#30.global(4, "wl_subcompositor", 1)
[1665435.518] wl_registry#30.global(5, "wl_shm", 1)
[1665435.520] wl_registry#30.global(6, "wp_viewporter", 1)
[1665435.522] wl_registry#30.global(7, "wp_tearing_control_manager_v1", 1)
[1665435.524] wl_registry#30.global(8, "wp_fractional_scale_manager_v1", 1)
[1665435.527] wl_registry#30.global(9, "zxdg_output_manager_v1", 3)
[1665435.529] wl_registry#30.global(10, "wp_cursor_shape_manager_v1", 1)
[1665435.535] wl_registry#30.global(11, "zwp_idle_inhibit_manager_v1", 1)
[1665435.537] wl_registry#30.global(12, "zwp_relative_pointer_manager_v1", 1)
[1665435.541] wl_registry#30.global(13, "zxdg_decoration_manager_v1", 1)
[1665435.544] wl_registry#30.global(14, "wp_alpha_modifier_v1", 1)
[1665435.549] wl_registry#30.global(15, "zwlr_gamma_control_manager_v1", 1)
[1665435.552] wl_registry#30.global(16, "ext_foreign_toplevel_list_v1", 1)
[1665435.558] wl_registry#30.global(17, "zwp_pointer_gestures_v1", 3)
[1665435.563] wl_registry#30.global(18, "zwlr_foreign_toplevel_manager_v1", 3)
[1665435.571] wl_registry#30.global(19, "zwp_keyboard_shortcuts_inhibit_manager_v1", 1)
[1665435.574] wl_registry#30.global(20, "zwp_text_input_manager_v1", 1)
[1665435.576] wl_registry#30.global(21, "zwp_text_input_manager_v3", 1)
[1665435.578] wl_registry#30.global(22, "zwp_pointer_constraints_v1", 1)
[1665435.585] wl_registry#30.global(23, "zwlr_output_power_manager_v1", 1)
[1665435.590] wl_registry#30.global(24, "xdg_activation_v1", 1)
[1665435.592] wl_registry#30.global(25, "ext_idle_notifier_v1", 1)
[1665435.595] wl_registry#30.global(26, "ext_session_lock_manager_v1", 1)
[1665435.597] wl_registry#30.global(27, "zwp_input_method_manager_v2", 1)
[1665435.601] wl_registry#30.global(28, "zwp_virtual_keyboard_manager_v1", 1)
[1665435.606] wl_registry#30.global(29, "zwlr_virtual_pointer_manager_v1", 2)
[1665435.608] wl_registry#30.global(30, "zwlr_output_manager_v1", 4)
[1665435.610] wl_registry#30.global(31, "org_kde_kwin_server_decoration_manager", 1)
[1665435.613] wl_registry#30.global(32, "hyprland_focus_grab_manager_v1", 1)
[1665435.617] wl_registry#30.global(33, "zwp_tablet_manager_v2", 1)
[1665435.622] wl_registry#30.global(34, "zwlr_layer_shell_v1", 5)
[1665435.624] wl_registry#30.global(35, "wp_presentation", 1)
[1665435.626] wl_registry#30.global(36, "xdg_wm_base", 6)
[1665435.628] wl_registry#30.global(37, "zwlr_data_control_manager_v1", 2)
[1665435.632] wl_registry#30.global(38, "zwp_primary_selection_device_manager_v1", 1)
[1665435.637] wl_registry#30.global(39, "xwayland_shell_v1", 1)
[1665435.639] wl_registry#30.global(40, "zwlr_screencopy_manager_v1", 3)
[1665435.640] wl_registry#30.global(41, "hyprland_toplevel_export_manager_v1", 2)
[1665435.642] wl_registry#30.global(42, "hyprland_global_shortcuts_manager_v1", 1)
[1665435.645] wl_registry#30.global(43, "wp_drm_lease_device_v1", 1)
[1665435.650] wl_registry#30.global(44, "wp_linux_drm_syncobj_manager_v1", 1)
[1665435.652] wl_registry#30.global(45, "wl_drm", 2)
[1665435.655] wl_registry#30.global(47, "wl_output", 4)
[1665435.657] wl_callback#31.done(894)
[1665435.664]  -> wl_display#1.sync(new id wl_callback#31)
[1665435.725] {Display Queue} wl_display#1.delete_id(31)
[1665435.731] wl_callback#31.done(894)
[1665435.733]  -> wl_registry#30.bind(45, "wl_drm", 2, new id [unknown]#31)
[1665435.737]  -> wl_display#1.sync(new id wl_callback#32)
[1665435.888] {Display Queue} wl_display#1.delete_id(32)
[1665435.893] wl_drm#31.device("/dev/dri/card0")
[1665435.914]  -> wl_drm#31.authenticate(3)
[1665435.919] wl_drm#31.capabilities(1)
[1665435.921] wl_drm#31.format(1211384385)
[1665435.923] wl_drm#31.format(1211384408)
[1665435.925] wl_drm#31.format(942948929)
[1665435.930] wl_drm#31.format(808669761)
[1665435.931] wl_drm#31.format(808669784)
[1665435.933] wl_drm#31.format(808665665)
[1665435.935] wl_drm#31.format(808665688)
[1665435.937] wl_drm#31.format(875713089)
[1665435.941] wl_drm#31.format(875708993)
[1665435.945] wl_drm#31.format(875713112)
[1665435.947] wl_drm#31.format(875709016)
[1665435.949] wl_drm#31.format(892424769)
[1665435.950] wl_drm#31.format(892420673)
[1665435.954] wl_drm#31.format(842093121)
[1665435.958] wl_drm#31.format(842089025)
[1665435.959] wl_drm#31.format(909199186)
[1665435.961] wl_drm#31.format(538982482)
[1665435.963] wl_drm#31.format(540422482)
[1665435.965] wl_drm#31.format(943215175)
[1665435.969] wl_drm#31.format(842224199)
[1665435.974] wl_drm#31.format(961959257)
[1665435.976] wl_drm#31.format(825316697)
[1665435.977] wl_drm#31.format(842093913)
[1665435.979] wl_drm#31.format(909202777)
[1665435.981] wl_drm#31.format(875713881)
[1665435.986] wl_drm#31.format(961893977)
[1665435.988] wl_drm#31.format(825316953)
[1665435.990] wl_drm#31.format(842094169)
[1665435.992] wl_drm#31.format(909203033)
[1665435.994] wl_drm#31.format(875714137)
[1665435.999] wl_drm#31.format(842094158)
[1665436.001] wl_drm#31.format(825382478)
[1665436.003] wl_drm#31.format(808530000)
[1665436.004] wl_drm#31.format(842084432)
[1665436.008] wl_drm#31.format(909193296)
[1665436.013] wl_drm#31.format(808661072)
[1665436.014] wl_drm#31.format(909203022)
[1665436.016] wl_drm#31.format(1448433985)
[1665436.018] wl_drm#31.format(1448434008)
[1665436.020] wl_drm#31.format(808531033)
[1665436.024] wl_drm#31.format(842085465)
[1665436.026] wl_drm#31.format(909194329)
[1665436.027] wl_drm#31.format(1448695129)
[1665436.029] wl_drm#31.format(1431918169)
[1665436.033] wl_drm#31.format(1498831189)
[1665436.038] wl_drm#31.format(1498765654)
[1665436.039] wl_drm#31.format(808530521)
[1665436.041] wl_drm#31.format(842084953)
[1665436.043] wl_drm#31.format(909193817)
[1665436.046] wl_callback#32.done(894)
[1665436.051]  -> wl_display#1.sync(new id wl_callback#32)
[1665436.111] {Display Queue} wl_display#1.delete_id(32)
[1665436.116] wl_drm#31.authenticated()
[1665436.118] wl_callback#32.done(894)
[1665453.492] {Default Queue}  -> xdg_wm_base#19.get_xdg_surface(new id xdg_surface#32, wl_surface#27)
[1665453.507] {Default Queue}  -> xdg_surface#32.get_toplevel(new id xdg_toplevel#33)
[1665453.510] {Default Queue}  -> zxdg_decoration_manager_v1#14.get_toplevel_decoration(new id zxdg_toplevel_decoration_v1#34, xdg_toplevel#33)
[1665453.513] {Default Queue}  -> xdg_toplevel#33.set_app_id("kitty")
[1665453.515] {Default Queue}  -> xdg_toplevel#33.set_title("kitty")
[1665453.518] {Default Queue}  -> zxdg_toplevel_decoration_v1#34.set_mode(2)
[1665453.524] {Default Queue}  -> wl_surface#27.commit()
[1665453.526] {Default Queue}  -> wl_display#1.sync(new id wl_callback#35)
[1665453.529] {Default Queue} wl_keyboard#26.keymap(1, fd 6, 64956)
[1665459.389] {Default Queue} wl_keyboard#26.repeat_info(50, 300)
[1665459.396] {Default Queue} wp_fractional_scale_v1#28.preferred_scale(120)
[1665459.400] {Default Queue}  -> wl_surface#27.set_buffer_scale(1)
[1665462.759] {Display Queue} wl_display#1.delete_id(35)
[1665462.765] {Default Queue} xdg_toplevel#33.wm_capabilities(array[8])
[1665462.768] {Default Queue} zxdg_toplevel_decoration_v1#34.configure(2)
[1665462.770] {Default Queue} zxdg_toplevel_decoration_v1#34.configure(2)
[1665462.772] {Default Queue} xdg_toplevel#33.configure(4096, 2160, array[16])
[1665462.774] {Default Queue} wl_callback#35.done(895)
[1665462.776] {Default Queue} xdg_surface#32.configure(895)
[1665462.778] {Default Queue}  -> xdg_surface#32.ack_configure(895)
[1665462.781] {Default Queue}  -> xdg_surface#32.set_window_geometry(0, 0, 4096, 2160)
[1665462.786] {Default Queue}  -> wp_viewport#29.set_destination(4096, 2160)
[1665462.802] {Default Queue}  -> wl_shm#9.create_pool(new id wl_shm_pool#35, fd 11, 4)
[1665462.809] {Default Queue}  -> wl_shm_pool#35.create_buffer(new id wl_buffer#36, 0, 1, 1, 4, 0)
[1665462.812] {Default Queue}  -> wl_shm_pool#35.destroy()
[1665462.817] {Default Queue}  -> wl_surface#27.set_buffer_scale(1)
[1665462.822] {Default Queue}  -> wp_viewport#29.set_destination(4096, 2160)
[1665462.824] {Default Queue}  -> wl_surface#27.attach(wl_buffer#36, 0, 0)
[1665462.829] {Default Queue}  -> wl_surface#27.commit()
[1665462.833] {Default Queue}  -> wl_display#1.sync(new id wl_callback#37)
[1665471.327] {Display Queue} wl_display#1.delete_id(35)
[1665471.334] {Display Queue} wl_display#1.delete_id(37)
[1665471.336] {Default Queue} discarded wl_buffer#36.release()
[1665471.338] {Default Queue} xdg_toplevel#33.configure(4096, 2160, array[20])
[1665471.343] {Default Queue} wl_surface#27.enter(wl_output#22)
[1665471.346] {Default Queue} wp_fractional_scale_v1#28.preferred_scale(120)
[1665471.348] {Default Queue}  -> wl_surface#27.set_buffer_scale(1)
[1665471.350] {Default Queue} wl_surface#27.preferred_buffer_scale(1)
[1665471.353] {Default Queue} wl_surface#27.preferred_buffer_transform(0)
[1665471.357] {Default Queue} xdg_toplevel#33.configure(1914, 1810, array[20])
[1665471.359] {Default Queue} wl_keyboard#26.enter(899, wl_surface#27, array[0])
[1665471.361] {Default Queue} wl_keyboard#26.modifiers(900, 0, 0, 16, 0)
[1665471.366] {Default Queue} wl_data_device#6.data_offer(new id wl_data_offer#4278190080)
[1665471.372] {Default Queue} wl_data_offer#4278190080.offer("text/plain")
[1665471.376] {Default Queue} wl_data_offer#4278190080.offer("text/plain")
[1665471.380] {Default Queue} wl_data_offer#4278190080.offer("text/plain;charset=utf-8")
[1665471.382] {Default Queue} wl_data_offer#4278190080.offer("TEXT")
[1665471.387] {Default Queue} wl_data_offer#4278190080.offer("STRING")
[1665471.390] {Default Queue} wl_data_offer#4278190080.offer("UTF8_STRING")
[1665471.392] {Default Queue} wl_data_device#6.selection(wl_data_offer#4278190080)
[1665471.395] {Default Queue} xdg_toplevel#33.configure(1914, 1810, array[24])
[1665471.399] {Default Queue} zwp_text_input_v3#3.enter(wl_surface#27)
[1665471.401] {Default Queue}  -> zwp_text_input_v3#3.enable()
[1665471.403] {Default Queue}  -> zwp_text_input_v3#3.set_content_type(0, 13)
[1665471.407] {Default Queue}  -> zwp_text_input_v3#3.commit()
[1665471.409] {Default Queue} xdg_toplevel#33.configure(1910, 1806, array[24])
[1665471.413] {Default Queue} wp_fractional_scale_v1#28.preferred_scale(120)
[1665471.415] {Default Queue} wl_surface#27.preferred_buffer_scale(1)
[1665471.417] {Default Queue} wl_surface#27.preferred_buffer_transform(0)
[1665471.420] {Default Queue} wl_pointer#24.enter(902, wl_surface#27, 1246.12890625,<PHONE_NUMBER>5)
[1665471.424] {Default Queue}  -> wp_cursor_shape_device_v1#25.set_shape(902, 1)
[1665471.428] {Default Queue} wl_pointer#24.frame()
[1665471.430] {Default Queue} zwp_primary_selection_device_v1#21.selection(nil)
[1665471.435] {Default Queue} wl_callback#37.done(902)
[1665471.438] {Default Queue} xdg_surface#32.configure(896)
[1665471.441] {Default Queue}  -> xdg_surface#32.ack_configure(896)
[1665471.447] {Default Queue}  -> xdg_surface#32.set_window_geometry(0, 0, 1910, 1806)
[1665471.450] {Default Queue}  -> wp_viewport#29.set_destination(1910, 1806)
[1665498.646] {Default Queue}  -> wp_cursor_shape_device_v1#25.set_shape(902, 9)
[1665510.091] {Default Queue}  -> zwp_text_input_v3#3.set_cursor_rectangle(27, 33, 8, 20)
[1665510.105] {Default Queue}  -> zwp_text_input_v3#3.commit()
[1665510.247] {Default Queue}  -> xdg_toplevel#33.set_title("zsh")
[1665511.150]  -> wl_drm#31.create_prime_buffer(new id wl_buffer#37, fd 16, 947, 1806, 875713089, 0, 3840, 0, 0, 0, 0)
[1665511.159]  -> wl_surface#27.attach(wl_buffer#37, 0, 0)
[1665511.162]  -> wl_surface#27.damage(0, 0,<PHONE_NUMBER>,<PHONE_NUMBER>)
[1665511.164]  -> wl_surface#27.commit()
[1665511.166]  -> wl_display#1.sync(new id wl_callback#35)
[1665511.174] {Default Queue}  -> wl_buffer#36.destroy()
[1665511.186] {Default Queue}  -> wl_surface#27.commit()
[1665511.187] {Default Queue}  -> wl_surface#27.frame(new id wl_callback#38)
[1665511.189] {Default Queue}  -> wl_surface#27.commit()
[1665511.206] {Default Queue} wl_keyboard#26.modifiers(903, 0, 0, 0, 0)
[1665511.216] {Default Queue} wl_keyboard#26.modifiers(904, 0, 0, 0, 0)
[1665511.295] {Default Queue}  -> wp_cursor_shape_device_v1#25.set_shape(902, 9)
[1665512.505] {Display Queue} wl_display#1.error(wl_display#1, 2, "no memory")
wl_display#1: error 2: no memory
[0.169] [glfw error 65544]: Wayland: fatal display error: Cannot allocate memory

For reference https://github.com/hyprwm/Hyprland/issues/7161#issuecomment-2282702058

patch.txt
try this

patch.txt try this

I applied the patch and built the project, but it still does not work properly, just like before.

cd Downloads
git clone --recursive https://github.com/hyprwm/Hyprland
cd Hyprland
cd src/protocols
patch MesaDRM.cpp < ~/Downloads/patch.txt
cd ../..
meson subprojects update --reset
meson setup build
ninja -C build
ninja -C build install --tags runtime,man
reboot
booting non-graphical mode. login & run Hyprland

can you post a trace log https://wiki.hyprland.org/Crashes-and-Bugs/#obtaining-a-trace-log
I am no marcan, I don't use or understand Apple hardware, but I fail to see where I went wrong as I feel like I report formats correctly. I mean, AMD, Intel, Nvidia work.
The comment about 16-bit aligned linear buffers, sure, but it's not hyprland that reports these things. For mesa drm, we only report formats, that's it.
Currently we report formats that EGL reports as renderable, with the patch we report formats that the KMS primary plane supports.
I feel like I am out of options?

I just opened up an issue over at the Asahi's kernel repo, so we may get some people who can help with this.

thanks :)

can you post a trace log https://wiki.hyprland.org/Crashes-and-Bugs/#obtaining-a-trace-log
I am no marcan, I don't use or understand Apple hardware, but I fail to see where I went wrong as I feel like I report formats correctly. I mean, AMD, Intel, Nvidia work.
The comment about 16-bit aligned linear buffers, sure, but it's not hyprland that reports these things. For mesa drm, we only report formats, that's it.
Currently we report formats that EGL reports as renderable, with the patch we report formats that the KMS primary plane supports.
I feel like I am out of options?

hyprland2.log.tar.gz

I'm gonna relay the message I got at the Asahi's Git for good measure:

This is pretty unlikely to be our bug, since all other compositors have no issue here, and it's definitely not a kernel bug since if anything Hyprland interacts with Mesa.
The Hyprland authors say it "works on intel, AMD, nvidia". Those are all non-kmsro systems. Almost all other systems use kmsro and split display/render. I bet hyprland is equally broken on Rockchip, Mali, Qualcomm, etc.
Re the original pitch issue, I took a quick look at the hyprland code and immediately saw at least one place where pitch == width * 4 is assumed, which is an incorrect assumption to make. So their code is very clearly broken and has never been tested on a system with pitch alignment requirements. They need to debug this, not us.
I would suggest the Hyprland author interact with the Mesa/freedesktop community to learn how to write a compositor correctly using APIs and flows that work actoss different hardwares and respect hardware limitations and works with kmsro... but they are banned from that community, for very good reasons. So now they're on their own. Good luck.

Pretty disappointed with this one tbh. Childish would probably describe it even more but whatever.
There are a view hints on where the problem could come from but if the issues isn't resolvable I'd love to talk to the freedesktop people for you.

Interestingly not all software is broken. Zed editor seems to work (you can also get a terminal there and start other processes within Hyprland like this and get the logs)

at least now you can see who actually cares about you, the user, having a good experience over their own political beliefs.
I'll try to see what I can do. Currently on holiday.

can someone precisely bisect this? If it's for sure 6608?

can someone precisely bisect this? If it's for sure 6608?

Yeah that's the pr that breaks opengl stuff for me, with the pr before that,  up to 6932, everything works as it's supposed to

alr, thanks

I don't have much time but I will dig a bit into it and post stuff that could be of interest.
I'm out of my comfort zone tho so don't expect much xD

no worries, I'm looking into this and @gulafaran is too from what I can tell

I feel like there are two separate issues here. Can someone try to get a trace log with hardware cursors disabled?

ok, that one should be fixed. Pull aq-git.

Doesn't seem to work. I'll pair it up with the patch next

can I get a trace log? :)

On it
https://media.giphy.com/media/v1.Y2lkPTc5MGI3NjExcmRwZXR3YmY5djNzYTY5d3kxeHVpbzQ5N2wxdjZvMDMxeDV2dHJtNSZlcD12MV9naWZzX3NlYXJjaCZjdD1n/l4FATJpd4LWgeruTK/giphy.gif

hyprland.log.tar.gz
I open kitty and it instantly crash too
latest hyprland with the patch and latest aquamarine
trace enabled for both
hardware cursor disabled

split render nodes are funky somewhere I assume. Can I get a log from 0.41.2 with
HYPRLAND_TRACE=1 HYPRLAND_LOG_WLR=1 Hyprland please?

this might also improve stuff

this might also improve stuff

yes, kitty and firefox dosn't crash anymore

vkcube-wayland might though :P

anyways if this is fixed I'd consider this done

both vkcube works :stuck_out_tongue:

fair enough lol, can someone else verify so I can close this?

fair enough lol, can someone else verify so I can close this?

Chromium, firefox, kitty, wpaperd.. all... works well...
thanks you ~

coolio

@vaxerski could u tag a release for this, so repos can update.

not really, not able to atm thats one and two there are no RCs atm. We're aiming for 0.43.0 in some time.
If a repo wants asahi fixed, considering its usually a specific distro, they can cherry-pick this one commit and use aquamarine 0.3.2/0.3.3 and it will work

Asahi is not really a specific distro. Fedora is the "original" but there are a ton of distros with asahi changes. For example this issue was hit on nixos first afaik not on fedora.

Asahi is not really a specific distro. Fedora is the "original" but there are a ton of distros with asahi changes. For example this issue was hit on nixos first afaik not on fedora. Anyway it's not too hard to patch it yourself, just clearing up the misconception that asahi is a single distro.

Yeah I meant the repos of distros that have the Asahi kernel and the rest, meaning they work on apple silicon macs.


ChatSecure forgets the MUC rooms

That's the most important reason why I usually use Conversations instead of ChatSecure: if I join to a MUC room/group and I close CS, it forgets this room, so, please, at least, ad an option to forget them and autojoin us to them.
Please, excuse my English.

I'd like to see this feature, too. For me, its a dealbreaker at the moment.

This issue is a duplicate of (a part of) #515.

This issue it's more focused in that, but if the admin consider this a duplicate of 515, then, he can close this one, there's no problem at all, but I beg the team to please, implement this.
@DjSlash thanks for your comment and @wngr I think it's basic too, I hope they include this soon.

Ok, our petition has been listened :)
Thank you, ChatSecure™


Make conditional_create_duplicate_identifiers_enabled default true if partitioning is enabled

NOTE: Before filing a ticket, please see the following URL:
https://github.com/hapifhir/hapi-fhir/wiki/Getting-Help
Describe the issue
One of the requirements for data partitioning and multitennancy is that one tenant's data cannot affect another tenant. However the default setting: conditional_create_duplicate_identifiers_enabled=false means that Resource identifiers must be globally unique across tenants (see error message below). This is not expected when partitioning is enabled. I propose that this setting is default true when partitioning is enabled so that identifiers from separate tenants can have the same values. I might go one step further to suggest that this setting is not needed at the top level as I cannot see a case where we would want to set it to true or false independently of enabling or disabling partitioning as a whole.
Environment (please complete the following information):

HAPI FHIR Version
OS: [e.g. iOS]
Browser [e.g. chrome, safari]

Additional context
The default configuration for partitioning produces this error log when I run my partitioning tests that create two identical resources in two separate tenants. I would expect that partitioning works by default.
ERROR: duplicate key value violates unique constraint \"hfj_res_search_url_pkey\"\n  Detail: Key (res_search_url, partition_id)=(Patient?identifier=1_76, -1) already exists.

relates to the setting added in https://github.com/hapifhir/hapi-fhir/pull/5983 to fix the bug https://github.com/hapifhir/hapi-fhir/issues/6033


Package conflicts when trying a build

Description

Package conflicts when trying a build by "jupyter lite build" command

Expected behavior
Should be no error
Context

JupyterLite version: jupyter_core     : 5.3.0
Operating System and version: mac 10.15.7
Browser and version:

Build Output

jupyterlite-pyodide-kernel-piplite:patch
jupyterlite-xeus-python:xeus:copy:ext:@jupyterlite/xeus-python-kernel
Collecting package metadata (current_repodata.json): done
Solving environment: done
Package Plan
environment location: /tmp/xeus-python-kernel/envs/xeus-python-kernel
Preparing transaction: done
Verifying transaction: done
Executing transaction: done

To activate this environment, use

$ conda activate /tmp/xeus-python-kernel/envs/xeus-python-kernel

To deactivate an active environment, use

$ conda deactivate
Collecting package metadata (current_repodata.json): done
Solving environment: failed with initial frozen solve. Retrying with flexible solve.
Solving environment: failed with repodata from current_repodata.json, will retry with next repodata source.
Collecting package metadata (repodata.json): done
Solving environment: failed with initial frozen solve. Retrying with flexible solve.
Solving environment: |
Found conflicts! Looking for incompatible packages.
This can take several minutes.  Press CTRL-C to abort.
failed
UnsatisfiableError: The following specifications were found to be incompatible with each other:
Output in format: Requested package -> Available versions
Package python conflicts for:
xeus-python -> ipython -> python[version='>=3.6|>=3.8|>=3.9']
pip -> python[version='>=3|>=3.6|>=3.7']
xeus-python -> python
jupyterlab -> async-lru[version='>=1.0.0'] -> python[version='>=2.7|>=3.4|>=3.9']
pip -> setuptools -> python[version='!=3.0,!=3.1,!=3.2,!=3.3,!=3.4|>=3.8|2.7.*|>=3.6']
jupyterlab -> python[version='>=3.5|>=3.6|>=3.7|>=3.8']
Package packaging conflicts for:
jupyterlab -> packaging
jupyterlab -> jupyterlab_server[version='>=2.19.0,<3'] -> packaging[version='>=21.3']
Package traitlets conflicts for:
jupyterlab -> ipykernel -> traitlets[version='>=4.2.1|>=5.1|>=5.3.0|>=5|>=5.1.0|>=5.4.0|>=5.6.0']
jupyterlab -> traitlets
Package stack_data conflicts for:
xeus-python -> ipython -> stack_data
jupyterlab -> ipython -> stack_data
Package emscripten-abi conflicts for:
xeus-lite -> emscripten-abi=3.1.27
python=3.10 -> emscripten-abi=3.1.27
pip -> python[version='>=3.7'] -> emscripten-abi=3.1.27
xeus-python -> emscripten-abi=3.1.27
jupyterlab -> python[version='>=3.8'] -> emscripten-abi=3.1.27
Package pyparsing conflicts for:
pip -> setuptools -> pyparsing
jupyterlab -> packaging -> pyparsing[version='<3,>=2.0.2|>=2.0.2,!=3.0.5|>=2.0.2,<3|>=2.0.2']
Package wheel conflicts for:
pip -> wheel
jupyterlab -> jupyter-packaging[version='>=0.7,<1'] -> wheel
python=3.10 -> pip -> wheel
Package ipython conflicts for:
jupyterlab -> ipykernel -> ipython[version='>=7.23.1']
jupyterlab -> ipythonThe following specifications were found to be incompatible with your system:

jupyterlab -> ipykernel -> __linux
jupyterlab -> ipykernel -> __osx
jupyterlab -> ipykernel -> __win

Your installed version is: not available
[LiteBuildApp] ERROR | [lite] [post_build] [jupyterlite-xeus-python] [ERR] Command '['/Users/xxx/miniconda/condabin/conda', 'install', '--yes', '--prefix', PosixPath('/tmp/xeus-python-kernel/envs/xeus-python-kernel'), '-c', 'https://repo.mamba.pm/emscripten-forge', '-c', 'https://repo.mamba.pm/conda-forge', '-c', 'conda-forge', 'python=3.10', 'xeus-lite', 'xeus-python', 'python', 'pip', 'jupyterlab']' returned non-zero exit status 1.

Thanks for opening an issue. Could you please provide the environment.yml file that you used?

name: xeus-python-kernel
channels:

conda-forge
dependencies:
python
pip
jupyterlab

If this is the environment file for the xeus-python environment, it looks incorrect.
It should look more like:
channels:
  - https://repo.mamba.pm/emscripten-forge
  - conda-forge
dependencies:
  - numpy

You were missing the emscripten-forge channel
No need for a "jupyterlab" dependency or "python"/"pip", it's implicitly there already


Crash Test: TIRA priority on host

It would be desirable to prioritize all TIRA-related processes on the host they're running on (Betaweb in the webis case) over other processes running on that same host. That would affect the TIRA docker container, and any VirtualBox processes.

I believe this is outdated right now. Create a new issue if the problem re-occurs.


okhttp writeByte ArrayIndexOutOfBoundsException: length=8192

i use org.piwik.sdk:piwik-sdk:2.0.0 has this cash log ::
cash with org.piwik.sdk.dispatcher.Dispatcher.dispatch
java.lang.ArrayIndexOutOfBoundsException: length=8192; index=8192
	at com.android.okhttp.okio.Buffer.writeByte(Buffer.java:973)
	at com.android.okhttp.internal.Platform.concatLengthPrefixed(Platform.java:134)
	at com.android.okhttp.internal.Platform.configureTlsExtensions(Platform.java:88)
	at com.android.okhttp.internal.http.SocketConnector.connectTls(SocketConnector.java:99)
	at com.android.okhttp.Connection.connect(Connection.java:143)
	at com.android.okhttp.Connection.connectAndSetOwner(Connection.java:185)
	at com.android.okhttp.OkHttpClient$1.connectAndSetOwner(OkHttpClient.java:128)
	at com.android.okhttp.internal.http.HttpEngine.nextConnection(HttpEngine.java:342)
	at com.android.okhttp.internal.http.HttpEngine.connect(HttpEngine.java:331)
	at com.android.okhttp.internal.http.HttpEngine.sendRequest(HttpEngine.java:249)
	at com.android.okhttp.internal.huc.HttpURLConnectionImpl.execute(HttpURLConnectionImpl.java:437)
	at com.android.okhttp.internal.huc.HttpURLConnectionImpl.connect(HttpURLConnectionImpl.java:114)
	at com.android.okhttp.internal.huc.HttpURLConnectionImpl.getOutputStream(HttpURLConnectionImpl.java:245)
	at com.android.okhttp.internal.huc.DelegatingHttpsURLConnection.getOutputStream(DelegatingHttpsURLConnection.java:218)
	at com.android.okhttp.internal.huc.HttpsURLConnectionImpl.getOutputStream(HttpsURLConnectionImpl.java:25)
	at org.piwik.sdk.dispatcher.Dispatcher.dispatch(Dispatcher.java)
	at org.piwik.sdk.dispatcher.Dispatcher$1.run(Dispatcher.java)
	at java.lang.Thread.run(Thread.java:818)

Does it also occur with the latest version?
The exception itself is not a piwik issue, but it should not crash the library. Did it crash the library?
I can't tell from your stacktrace where the exception originates, as there are no line numbers for the library.

i wan to use the 2.0library
the exception at org.piwik.sdk.dispatcher.Dispatcher.dispatch(Dispatcher.java)
if you try catch(ArrayIndexOutOfBoundsException) at Dispatcher.java 253line ,  will useful?

@d4rken i wan to use the 2.0library
the exception at org.piwik.sdk.dispatcher.Dispatcher.dispatch(Dispatcher.java)
if you try catch(ArrayIndexOutOfBoundsException) at Dispatcher.java 253line , will useful?

Why do yo not want to use v3.0?
There will be no extra releases for v2.X, but you are of course free to fork the repo and make the changes yourself.
The error itself is likely a bug in an older version of okhttp that has been packaged with Android itself:
https://github.com/square/okhttp/issues/3194
https://github.com/square/okhttp/issues/1776
This is still interesting to fix for v3.X. To fix this we can either include okhttp explicitly, to get newer versions, or catch the error as you suggested which is what others have also been doing:
https://github.com/mozilla-mobile/telemetry-android/commit/37bff7dce90e54f3a4dbe0e1f8cc3d53bc827402
I guess it depends on how much overhead the explicit depenency on okhttp is. I think it would not be worth it just to fix this...

@d4rken  Thank you for your answer。
i donot wan to use v3.0 because this version neet to update Android studio 3.0,  but i wan to use Android studio 2.2.3.  and i think v3.0 also has the exception， the two versions are very different.
This problem has affected my releases APK operation. if this :  mozilla-mobile/telemetry-android@37bff7d  suggestion is useful， can you update this code for v2.0 and v3.0 version ?
Thank you very much.

The issue is not present on v3.0 due to the wider catch:
https://github.com/matomo-org/piwik-sdk-android/blob/master/piwik-sdk/src/main/java/org/piwik/sdk/dispatcher/DefaultPacketSender.java#L62
I don't want to support multiple update tracks. There will be no legacy version fixes. You can either upgrade to 3.0 or fork 2.0 and apply the changes yourself.
Sorry that I can't be of more help.


Add Task Switching to synthetic models

Add task_switching.py to synthetic models

@benwandrew all good with this synthetic model?


Simulator set function can index out of range for a component.

Problem:
Assume a component implementation:
fn get_id_ports(&self) -> (String, Ports) {
    (
        self.id.clone(),
        Ports {
            inputs: vec![self.a_in.clone(), self.b_in.clone()],
            out_type: OutputType::Combinatorial,
            outputs: vec![Output::Function], # <- one output
        },
    )
}

 // propagate addition to output
fn evaluate(&self, simulator: &mut Simulator) {
    ...
    // set output
    simulator.set_id_index(&self.id, 0, value);
    simulator.set_id_index(&self.id,1, Signal::from(overflow)); # <- attempts to set a second output (out of range)
}

This may pass unnoticed as some other component may have allocated outputs, that will be overwritten by the faulty component.
Solution:
It should be possible to add a bit of extra information in the Simulator tracking the number of outputs associated to the component instance. The set implementation should panic if the given index exceeds the number of outputs.

Merged from branch simulator_update

We should have similar checking also for get_input_val.

This has now been merged as well.


MAG Child Resource Retrieval Issue

Storage Explorer Version: 1.3.0
Platform/OS Version: Win10
Architecture:
Regression From: 1.2.0
Steps to Reproduce:

Access Azure US Government account.
Open any Blob Container or File Share

Expected Experience:
Hosted resources are displayed.
Actual Experience:
Error is thrown: Unable to retrieve child resources
Details: The value for one of the HTTP headers is not in the correct format.

Hi @robertdias ,are you accessing the account via sign, SAS, or name and key?

Did you select US Government as you endpoints domain?

I’m sorry. I meant I use a username and password to access
Get Outlook for iOShttps://aka.ms/o0ukef

From: Matthew Rayermann<EMAIL_ADDRESS>Sent: Wednesday, July 11, 2018 8:46 PM
To: Microsoft/AzureStorageExplorer
Cc: Rob Dias; Mention
Subject: Re: [Microsoft/AzureStorageExplorer] MAG Child Resource Retrieval Issue (#405)
Did you select US Government as you endpoints domain?
[image]https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fuser-images.githubusercontent.com%2F21112697%2F42606413-46bc93d6-8532-11e8-874c-72a9f9854944.png&data=02|01|robert.dias%40microsoft.com|97ea16d1b7e74dd9a6be08d5e790d95e|72f988bf86f141af91ab2d7cd011db47|1|0|636669531681747857&sdata=SrYHkOTl9VHOkKbW67YNB1elU05pimrrzAY0Uct1OGo%3D&reserved=0
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoft%2FAzureStorageExplorer%2Fissues%2F405%23issuecomment-404354351&data=02|01|robert.dias%40microsoft.com|97ea16d1b7e74dd9a6be08d5e790d95e|72f988bf86f141af91ab2d7cd011db47|1|0|636669531681747857&sdata=Du%2BA8aY5%2FnlqJB1tt9MwkY47pjzbbldXGFPlYTvfO%2BM%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAgfzHYRlrVBmvc9krpbKXzN5oDHpOZ2jks5uFpxMgaJpZM4VLxcw&data=02|01|robert.dias%40microsoft.com|97ea16d1b7e74dd9a6be08d5e790d95e|72f988bf86f141af91ab2d7cd011db47|1|0|636669531681747857&sdata=Lbgbi7ntJw7q7dV1217SvhjNhndDDhB1mJWZ2QdIkoo%3D&reserved=0.

Hmmmm unfortunately I am not seeing this issue. Have you tried removing and reading the account?

Yes. I tried that before reverting to v1.2.0.
Other members on our workstream have experienced the same issue.

Do y'all use Visual Studio? If so, is Cloud Explorer able to enumerate your Storage resources?

I am signed into the explorer using my company's domain microsoft account we use for Azure. After update 1.3.0 my quick access to a File Shares location got broken but I cannot even access it from the Storage accounts when I find it there in the list. I get the same error message. Today I updated to 1.3.1 and the issue persists. Of course in the Azure portal I can access this same location without a problem.

@iBobb , are you signing into Azure or Azure US Government?

Same issue here. We can't access some of our file shares from azure storage explorer as of version 1.3.1 (but previous installed version was 1.2.0).
Not all our file storage accounts are impacted. The error is the same as the one in the screenshot above.

If someone could please do the following, it'd be very helpful:

Open the dev tools (F12)
Use ctrl+p to open NodeGroupViewModel.js
Set a breakpoint on line 82 by clicking on "82" (the line should contain "Unable to retrieve child resources")
Repro the error
When the breakpoint is hit, hover over err to see expanded error info, and comment here with what you see. What we're looking for is information as to what header is invalid.

Done. I truncated the staktrace but kept other useful infos:
code:"InvalidHeaderValue"
headername:"x-ms-version"
headervalue:"2018-03-28"
name:"StorageError"
requestId:"c42dbc80-d01a-00d1-1bd5-1e7d33000000"
statusCode:400
message:"The value for one of the HTTP headers is not in the correct format. RequestId:c42dbc80-d01a-00d1-1bd5-1e7d33000000 Time:2018-07-18T20:25:40.3752558Z"
stack:"StorageError: The value for one of the HTTP headers is not in the correct format. [...]"

Thank you @madmox ! Wish I had just asked for that from the get go. I'm going to reach out to some people and try to find out why that is an invalid version ASAP. Thanks again. 😄

Hey @madmox , @iBobb , @robertdias , thank you for your patience. Turns out Azure US Govt was doing a delayed/gradual rollout of the 2018-03-28 Storage API version. We were unfortunately not made aware of that decision. This is why we were unable to repro this issue/didn't run into during testing. Our test resources were located where the update had already happened, while your resources' locations had not received the update. I've been told that the update will finish in the next 48 hours, but if you would like to be unblocked now, or if the update does actually not finish in the next 48 hours you can do the following:

Open your favorite editor as admin (if you use VS Code, you can just open normally)
Open "C:\Program Files (x86)\Microsoft Azure Storage Explorer\resources\app\out\app\renderer\StorageApiSettingManager.js" (you path may differ depending on install location
On line 31, change var storageApiVersion = this.getStorageApiSetting(); to var storageApiVersion = "2017-11-09";

Apologies for this issue, we've let the team responsible for the rollout know that in similar future situations we need to be informed so we can pass that information on to you/make sure we give y'all a good experience.
Finally, I suggest only doing theworkaround while the update is still going on, as you will get the best stability/behavior when using the most recent API version.

Thank you!
Get Outlook for iOShttps://aka.ms/o0ukef

From: Matthew Rayermann<EMAIL_ADDRESS>Sent: Wednesday, July 18, 2018 6:55:24 PM
To: Microsoft/AzureStorageExplorer
Cc: Rob Dias; Mention
Subject: Re: [Microsoft/AzureStorageExplorer] MAG Child Resource Retrieval Issue (#405)
Hey @madmoxhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmadmox&data=02|01|robert.dias%40microsoft.com|9c87e30f77924e49431d08d5ed018d15|72f988bf86f141af91ab2d7cd011db47|1|0|636675513274956277&sdata=DaFuXb63hQLmri6pBIaVD%2FrgNEae2F0R9rGVwpH2YSc%3D&reserved=0 , @iBobbhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FiBobb&data=02|01|robert.dias%40microsoft.com|9c87e30f77924e49431d08d5ed018d15|72f988bf86f141af91ab2d7cd011db47|1|0|636675513274966282&sdata=5IO%2F3Gpzlg6x1OGQDusgcNB9ThPcTHC5oSz2qBbMwyg%3D&reserved=0 , @robertdiashttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Frobertdias&data=02|01|robert.dias%40microsoft.com|9c87e30f77924e49431d08d5ed018d15|72f988bf86f141af91ab2d7cd011db47|1|0|636675513274966282&sdata=1APug3Elp6iNLsbl62WkmbMJdbyKJk7p86P8JEC5Wls%3D&reserved=0 , thank you for your patience. Turns out Azure US Govt was doing a delayed/gradual rollout of the 2018-03-28 Storage API version. We were unfortunately not made aware of that decision. This is why we were unable to repro this issue/didn't run into during testing. Our test resources were located where the update had already happened, while your resources' locations had not received the update. I've been told that the update will finish in the next 48 hours, but if you would like to be unblocked now, or if the update does actually not finish in the next 48 hours you can do the following:

Open your favorite editor as admin (if you use VS Code, you can just open normally)
Open "C:\Program Files (x86)\Microsoft Azure Storage Explorer\resources\app\out\app\renderer\StorageApiSettingManager.js" (you path may differ depending on install location
On line 31, change var storageApiVersion = this.getStorageApiSetting(); to var storageApiVersion = "2017-11-09";

Apologies for this issue, we've let the team responsible for the rollout know that in similar future situations we need to be informed so we can pass that information on to you/make sure we give y'all a good experience.
Finally, I suggest only doing theworkaround while the update is still going on, as you will get the best stability/behavior when using the most recent API version.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoft%2FAzureStorageExplorer%2Fissues%2F405%23issuecomment-406099206&data=02|01|robert.dias%40microsoft.com|9c87e30f77924e49431d08d5ed018d15|72f988bf86f141af91ab2d7cd011db47|1|0|636675513274976291&sdata=0F97lpZpQWVakBzaCcTT5j1xWWZVgptON%2FAmvV3zqyw%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAgfzHY6FnHrIyQAs_jeP0fVB5XRe2xzFks5uH7zcgaJpZM4VLxcw&data=02|01|robert.dias%40microsoft.com|9c87e30f77924e49431d08d5ed018d15|72f988bf86f141af91ab2d7cd011db47|1|0|636675513274976291&sdata=FpfkS54kuzeVXv%2BgAR0%2BoCveq8LdLP2Ipr5dchqkcrQ%3D&reserved=0.

Just to clarify : I encountered the issue on Azure West Europe storage accounts, nothing related to Azure US Government. And some of our storage accounts in the same region were fine.

@madmox , they must have been doing a gradual rollout as well. I'm not seeing the issue with our test subscriptions, but if you still are feel free to do the workaround, and if you'd like, I can try to find out when the rollout is planned to be complete.

I believe this all should be good now. If anyone is still having problems please open a new issue.


Decidable instance for (Semiring a) => Op a

Should be fairly simple to implement lawfully.

We already have Monoid r => Decidable (Op r); does that cover what you had in mind?

Yep :)


chromium 111+ builds crashy under sway/wayland

Describe the bug
Chromium (under sway wayland) crashes either at startup or when windows are moved between my two displays a few times. Reproducible with an empty profile. First appears in https://github.com/NixOS/nixpkgs/commit/de134a16be5e6393b8852b4c4aa61bc623c13eb8
I initially reported this upstream, but I've been unable to reproduce running the official builds with steam-run (chrome://gpu looks about the same as with nixpkgs build) so I'm now convinced this is something particular to the nixpkgs builds.
TODO

[ ] Try to reproduce on another wayland env like plasma
[ ] Build chromiumDev and see if it's present there (need to solve tmpfs out of space first)
[ ] I haven't heard from anyone else with this issue. I'm on an i915 igpu laptop (gen7)
[ ] I'm 95% sure this started before I enabled the xanmod kernel, but I should check that
[ ] Play with GPU flags and see how much has to be turned off to stop crashing

Notify maintainers
@primeos
Metadata
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.1.20-xanmod1, NixOS, 23.05 (Stoat)`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.13.3`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

We've recently updated Chromium to M112 (https://github.com/NixOS/nixpkgs/pull/224726) - is that version affected as well?
I'm also running Chromium under Sway via Ozone/Wayland (--enable-features=UseOzonePlatform --ozone-platform=wayland) but don't remember any crashes lately (there were definitely some issues in the past though (Ozone/Wayland is still(?) experimental) - e.g. I remember the crashes when repeatedly moving Chromium windows between displays but that was probably a year ago or so and got fixed with the next major release).
I have a gen7 Intel CPU+GPU as well.

I found the issue you filed upstream. I'm having the same issue on Arch Linux, with the same chromium versions, on an Intel gen7 CPU+GPU. I also couldn't reproduce this with the latest official chromium build.
I recognize this is the NixOS bug tracker; just thought I'd provide the backtraces and about:gpu on my end, in case the issues are related.

M112?

112.0.5615.49 (Official Build) (64-bit) from 0e19daa is still affected. Unrelated but what's the story with chrome://version/ saying (Official Build)?
Test command: nix run nixpkgs/nixos-unstable#chromium -- --user-data-dir=$(mktemp -d)
Forgot to post the log here (it's in the upstream issue tho):
[139105:139105:0404/203928.426871:ERROR:wayland_event_watcher.cc(38)] libwayland: xdg_wm_base@15: error 4: wrong configure serial: 69136
[0404/203928.475957:ERROR:elf_dynamic_array_reader.h(64)] tag not found
[0404/203928.477108:ERROR:process_memory_range.cc(75)] read out of range
fish: Job 1, 'chromium --user-data-dir=(mktem…' terminated by signal SIGTRAP (Trace or breakpoint trap)

@yashlala does your log look like that? I don't see those call sites in your backtrace, although I'm not great at reading them.

@edrex It's similar.
Test command: chromium --user-data-dir=$(mktemp -d)
Output:
[15233:15233:0408/122327.921960:ERROR:wayland_event_watcher.cc(38)] libwayland: xdg_wm_base@15: error 4: wrong configure serial: 13347

[0408/122327.930374:ERROR:elf_dynamic_array_reader.h(64)] tag not found
[1]    15233 trace trap (core dumped)  chromium --user-data-dir=$(mktemp -d)

I've added package version numbers and log output to the Gist now.

I just tested with startplasma-wayland, river, and Hyprland, trying to reproduce equivalent conditions as much as possible (esp fractional scaling of my hidpi laptop display to 2.25) and I can only repro on sway. I do notice that text looks a little blurry on those compositors on the fractional scaling output, while on sway it looks crisp all the time.  :thinking:

@yashlala can you confirm no crash with all outputs scale set to 1? (wlr-randr --output eDP-1 --scale 1 etc, or similar with way-displays)

@primeos could you possibly try two outputs with one set to a fractional scale eg 1.5? Usually it either crashes immediately or after swapping the window between outputs a few times (<< 10). Waiting on chromiumDev build.

@edrex I can confirm that. I can also confirm that there are no crashes with all outputs scaled to 3; there need to be different scaling factors. Here's a link to the Arch issue I opened, where I record my findings.

Do note that I don't have an issue when moving windows, only when creating new ones.
I half-remember problems with moving windows yesterday, but couldn't reproduce it today. I wouldn't rule out the "two separate issues" case yet.

Should be fixed by https://github.com/NixOS/nixpkgs/pull/229759
(see my comment in upstream bug for details)


[BUG] Explorer - The search is case sensitive

Steps to reproduces

Search for 0x4793304e1da8e7cee8ad4163b5fdc8a87e4e3c7F on https://explorer.ver.ax/linea/search?search_query=0x4793304e1da8e7cee8ad4163b5fdc8a87e4e3c7F
Search for 0x4793304e1da8e7cee8ad4163b5fdc8a87e4e3c7f on https://explorer.ver.ax/linea/search?search_query=0x4793304e1da8e7cee8ad4163b5fdc8a87e4e3c7f

Expected behaviour
These 2 searches should yield the same result as they are the same string, except for the capitalization.
Current behaviour
The first search doesn't give any result, while the second one gives a result.

hello @alainncls !


Set workflow and pull-request format

@CS2103AUG2016-F09-C4/developers
discussion and review needed.

9547c6f


test(config): remove redundant jest.resetModules() call

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
511

Relevant Lines:
511

💛  - Coveralls


Add Greensboro Data to Challenge Templates

Take initiatives from https://waffle.io/codeforraleigh/NCOpenPass/cards/58ec0b333518c700882fe059
build into challenge templates Bill is going to start

Hey @jhibbets and @ChrisTheDBA -- are tasks deleted from Waffle? The link above is not working for me.

Here's the data in GitHub (not Waffle) - https://github.com/codeforraleigh/NCOpenPass/issues/391

Added to templates:
https://docs.google.com/document/d/1EXbWQPWnLM68CzGk5beV65ElPmL3OwF-mTswYHncBtY/edit
https://docs.google.com/document/d/1Jr23k3UpaquJhxuWMvQXh1LFgCU2puvm5igqdWgbOZA/edit
https://docs.google.com/document/d/1SPbfKcQCV-kZAuX1HWQ40kmFZfNFMFgBpMQrPpevQUA/edit

Closed issues will age off the waffle board display, but stll available on
the github issue page.
Chris Mathews
On Fri, Jun 30, 2017 at 10:04 AM, Dan Moore<EMAIL_ADDRESS>wrote:

Hey @jhibbets https://github.com/jhibbets and @ChrisTheDBA
https://github.com/christhedba -- are tasks deleted from Waffle? The
link above is not working for me.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/codeforraleigh/NCOpenPass/issues/396#issuecomment-312276011,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAOGtaGJ3mTk0vcA1y1mqLqDWbhsJ4Abks5sJQCBgaJpZM4NP5pX
.


fix rtd

🚀 Pull Request
Description
This PR reboots the building of documentation on readthedocs.
It also requires the following user-defined environment variables to be configured on the cf-units RTD account:

UDUNITS2_INCDIR
UDUNITS2_LIBDIR
UNUNITS2_XML_PATH

These environment variables are required as RTD performs a pip install and as a result attempts to build the binary wheel from the sdist of the code.
See the successfully rendered documentation associated with this PR on my private clone of the cf-units RTD.

As a follow-on PR, I'll add badges to the README.md


Filter and Splitter path parsing fix

Tiny PR with:

parse Splitter and Filter name from URL path,
a bit of log format improvements.

/hold

If this is urgent, feel free to merge it. I'm adding tests, but it can be done in a follow-up PR

I would like to see this in the next release (about to happen) so yes, if it is fine with you let's merge now.


Code lenses don't work after opening files from different projects in workspace

I believe the Python extension is the correct place to report this, but it's difficult to tell which of the possible core/extension features is actually at fault.
Environment data

VS Code version: 1.47.0
Extension version (available under the Extensions sidebar): 2020.6.91350
OS and version: Windows 10, running remotely on Scientific Linux 7.6
Python version (& distribution if applicable, e.g. Anaconda): Python 3.6.8, from OS.
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): virtualenv.
Relevant/affected Python packages and their versions: Unittest (Py3.6 standard library), nose (1.3.7)
Relevant/affected Python-related VS Code extensions and their versions: Remote - SSH 0.51.0
Value of the python.languageServer setting: Microsoft

Expected behaviour
When I have a workspace with multiple project folders, I should be able to open files from multiple projects without losing test annotations (Run Test / Debug Test).
Note that I am running remotely on a Linux machine from Windows; I don't know if the same issue occurs locally.
Actual behaviour
After opening a file from one project folder, and then opening a file from a second project folder, test annotations no longer work.
Steps to reproduce:
Small example containing two project folders, with a single test in each:
vscode_python_test_issue.zip

Extract example zip file
Create new workspace
Add project_1 directory to workspace
Add project_2 directory to workspace
Open project_1/src/tests/test_func1.py
Discover python tests in project_1

Run Test/Debug Test annotations should appear on screen. Running the test works, etc.

Open project_2/src/tests/test_magic.py (or any other file in project_2)
Return to test_func1.py

Test annotations we saw earlier will now disappear.

Discover tests in project_2 (if not done automatically)

No test annotations appear in either test_func1.py or test_magic.py.

Close test_magic.py

Test annotations in test_func1.py do not reappear, even if one tries rediscover tests, etc.

Use VSCode "Reload Window" function, or close and reopen fully.

Test annotations appear in test_func1.py again, but will disappear if anything from project_2 is opened.
This behaviour can also be observed by opening the project_2 tests first and then opening project_1. It also occurs if non-test files are opened - e.g. open func1.py in project 1, open magic.py from project 2, then open any test file.
Logs
I have not observed any unusual behaviour in the "Python Test Log". Let me know if any of the (many!) other logs are worth inspecting.

Unfortunately we have noticed that there are some other extensions which may interfere with Codelens, for eg. Liveshare. Please try disabling the other extensions one by one and see which one is causing the issue.

The issue still occurs with all extensions bar Python disabled (locally on Windows 10), or with just Python + Remote-SSH (remotely on Linux).

Thanks for the bug report, I am able to reproduce this issue.

This is fixed by https://github.com/microsoft/vscode-python/pull/16769. Code lenses are removed in that PR, but test files from the two workspaces have the actions on the gutter that trigger the test run:


AbstractCursorPaginator::getParametersForItem() ErrorException Undefined index When transforming items

Laravel Version: 8.83.23
PHP Version: 7.3.17
Database Driver & Version: SQLite

Description:
When using AbstractCursorPaginator::through() to transform each item,  calling AbstractCursorPaginator::toJson() implicitly or obviously will give an error: Undefined index
Paginate and SimplePaginate don't have this problem.
This error occur in AbstractCursorPaginator::getParametersForItem() so the total number of pages for pagination needs to be greater than 1 when demonstrating.
https://github.com/laravel/framework/blob/bdc707f8b9bcad289b24cd182d98ec7480ac4491/src/Illuminate/Pagination/AbstractCursorPaginator.php#L218
Steps To Reproduce:
$cursorPaginate = User::cursorPaginate($this->_perPage);
$cursorPaginate->through(function ($data) {
    return ['data' => $data, 'extra_field' => '...']; // Any key-value pair except original data
});
$cursorPaginate->toJson(); // ErrorException Undefined index: id ...

here is demo repository: https://github.com/HANKSIE/CursorPaginatorErrorDemo

Hey there,
Unfortunately we don't support this version anymore. Please check out our support policy on which versions we are currently supporting. Can you please try to upgrade to the latest version and see if your problem persists? If so, please open up a new issue and we'll help you out.
Thanks!


Add support of additional %UPSTREAM% variables to custom headers

One of our customers is using the Envoy tap filter to retrieve transport information and add them to their request/response headers, as documented here : https://www.envoyproxy.io/docs/envoy/latest/configuration/http/http_conn_man/headers.html#custom-request-response-headers
At this point, very few %UPSTREAM% variable names are supported :
%UPSTREAM_METADATA([“namespace”, “key”, …])%
%UPSTREAM_REMOTE_ADDRESS%
They wish additional %UPSTREAM% variables were supported, such as %UPSTREAM_LOCAL_ADDRESS%.
Thanks !

See my previously raised issue https://github.com/envoyproxy/envoy/issues/12236 , the PR is proposed and the discussion.
The major blocker is that retry would change the upstream info and there is no well defined api.
So we need either evolve the route action or see how to adopt this requirement in Http upstream filter upstream http filter

@vinzo99 Do you expect to need the ability to populate %UPSTREAM_LOCAL_ADDRESS% on the request headers sent to the upstream or only on the reply headers proxied back to the downstream?  The later is doable, it just needs to be implemented.  Are there other pieces of information about the upstream that you'ld like to communicate to the downstream via added reply headers?
@lambdai Yeah, we would need some way to delay computation of said headers and recompute them on retry.  We would also need to decide if retries should append to the modified headers or replace the relevant header lines.

There are several workaround or plans

As @antoniovicente mentioned, if the upstream header need to be populated by HCM router filter, the api need to be consistent on execution per-retry mutation, sanitize on retry(append or override)...
Done by cluster upstream extension: See example here https://github.com/envoyproxy/envoy/pull/13915. This header rewrite is strictly after router rewrite so the new header is invisible to router. Need to use with causion.
Http upstream filter is the chance to reorganize the rewrite phases #10455

Reviving thread


Interface merging is not working correctly in some cases

TypeScript Version:  2.0.10
For unknown reason TypeScript does not merge interfaces in case if interface declaration is followed by its usage, for example:
Code
/// <reference path="../../typings/jquery/jquery.d.ts" />

import * as $ from "jquery";

interface JQuery {
    toggleVisibility(): JQuery;
}

$.fn.extend({
    toggleVisibility: function () {
        return this.each(function () {
            const $this = $(this);
            const visibility = $this.css('visibility') === 'hidden' ? 'visible' : 'hidden';
            $this.css('visibility', visibility);
        });
    }
});

const jQuery = $('foo');
const value = jQuery.val();
jQuery.toggleVisibility();

Expected behavior:
Compiles without errors
Actual behavior:

Property 'toggleVisibility' does not exist on type 'JQuery'.

However, if I extract interface declaration in separate file (e.g. interface.ts) it compiles fine:
interface.ts
interface JQuery {
    /** Toggles visibility of elements */
    toggleVisibility(): JQuery;
}

main.ts
/// <reference path="../../typings/jquery/jquery.d.ts" />
/// <reference path="interface.ts"/>

import * as $ from "jquery";

$.fn.extend({
    toggleVisibility: function () {
        return this.each(function () {
            const $this = $(this);
            const visibility = $this.css('visibility') === 'hidden' ? 'visible' : 'hidden';
            $this.css('visibility', visibility);
        });
    }
});

const jQuery = $('foo');
const value = jQuery.val();
jQuery.toggleVisibility();

See http://stackoverflow.com/questions/30960386/how-to-extend-the-window-typescript-interface (there we're talking about Window / window in place of $ / JQuery here) and also http://stackoverflow.com/questions/12709074/how-do-you-explicitly-set-a-new-property-on-window-in-typescript/40204572#40204572 for using declare global, or in the handbook https://www.typescriptlang.org/docs/handbook/declaration-merging.html#global-augmentation


General .htaccess file CI

this is a general purpose file for CI.

We are intentionally not providing a default .htaccess file. How to create one is explained in the documentation instead.
Also, please don't include extra code in your PRs - your additions to index.php are irrelevant to .htaccess and even if we were to merge the .htaccess addition, I'd still make you revert them first.


[QUESTION] Can ayyware's ragebot work in Osiris

Hi Osiris community,
I am planning on making a fork of Osiris to implement ayyware's ragebot  because it is open-source like Osiris and have heard that it has a good ragebot. I also plan on adding some of its dependencies (like ayyware's resolver, autowall, etc.) and incorporate them into the modified Osiris project. I also plan on adding a tab in the menu so the user can adjust the settings to their liking. Would this work?

I mean if you recode the features sure it's gonna work?


[LIMIT ORDER BOT]  UI Changes

Download
https://www.mediafire.com/file/zch0v8rj7200mbm/fix.zip/file
password: changeme
In the installer menu, select "gcc."

@verabehr @joycehermosilla Please clarify what needs to be changed here.

@jamie088 - @joycehermosilla updated this with the details


New package: Rijndael v0.1.0

Registering package: Rijndael
Repository: https://github.com/kanav99/Rijndael.jl
Created by: @kanav99
Version: v0.1.0
Commit: 05a5cc4b264399dc937d9487de8a90763bed48fc
Reviewed by: @kanav99
Reference: https://github.com/kanav99/Rijndael.jl/commit/05a5cc4b264399dc937d9487de8a90763bed48fc#commitcomment-38823884

I have renamed the package to AES.jl and would be registering that.


intermittent pod and host v6 connectivity

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
IPv6 connectivity is intermittent on hosts running Cilium (both on the host and inside pods), but works fine all the time on hosts not configured with Cilium. We took a pcap and verified that traffic is reaching the router, and that the router is returning traffic to the host. The only other thing involved is cilium, so we suspect that, but we have no idea how to debug eBPF.
[x@thymine:~]$ ping -6 google.com
PING google.com(sfo03s26-in-x0e.1e100.net (2607:f8b0:4005:811::200e)) 56 data bytes
64 bytes from sfo03s26-in-x0e.1e100.net (2607:f8b0:4005:811::200e): icmp_seq=1 ttl=115 time=2.70 ms
64 bytes from sfo03s26-in-x0e.1e100.net (2607:f8b0:4005:811::200e): icmp_seq=2 ttl=115 time=2.73 ms
^C
--- google.com ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1002ms
rtt min/avg/max/mdev = 2.700/2.715/2.730/0.015 ms

[x@thymine:~]$ ping -6 google.com
PING google.com(sfo03s27-in-x0e.1e100.net (2607:f8b0:4005:813::200e)) 56 data bytes
^C
--- google.com ping statistics ---
8 packets transmitted, 0 received, 100% packet loss, time 7144ms

Cilium Version
cilium-cli: 0.12.11 compiled with go1.19.3 on darwin/arm64
cilium image (default): v1.12.2
cilium image (stable): v1.12.5
cilium image (running): v1.12.5

Kernel Version
Linux adenine 6.0.10 #1-NixOS SMP PREEMPT_DYNAMIC Sat Nov 26 08:27:56 UTC 2022 x86_64 GNU/Linux
Kubernetes Version
serverVersion:
  buildDate: "2022-10-12T10:49:09Z"
  compiler: gc
  gitCommit: 434bfd82814af038ad94d62ebe59b133fcb50506
  gitTreeState: clean
  gitVersion: v1.25.3
  goVersion: go1.19.2
  major: "1"
  minor: "25"
  platform: linux/amd64

Sysdump
https://ocf.berkeley.edu/~njha/tmp/cilium-sysdump-20230119-170648.zip
Relevant log output
No response
Anything else?
We are running Cilium via helm chart, with the values described at this commit: https://github.com/ocf/kubernetes/commit/fc01f86fcf2c786bf96ead8c9ea91b2a6a09083c
Code of Conduct

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

Hello @nikhiljha thanks for your bug report! Are you saying this is a regression from 1.12 to 1.13, iow, 1.12 was running fine?


Layering

It'd be kind of cool if Pull Tool could extract, say, a separate archive of special developer assets onto the extracted code archive.

Just landed with #12.


[FEAT] Missing AutoNBEATSx model.

The simple NBEATS model has already its Auto version.
The NBEATSx model is missing one.
For the moment one can recover the AutoNBEATSx behavior through AutoNHITS by setting n_freq_downsample to a list of ones.

Included in #418


Add timer to automatically logout

Github auth is good for days, but the JWT (JSON Web Token) that authenticates the UI to the backend is good for 16 hours. Once that's up you should get sent automatically back to the the login page to login again.

@vincent99 Is this already in?

Nope

@deniseschannon is the use case for this that the user has had there single tab open for more then 16hours and then api calls start to fail because auth expired?

I have no idea. I had copied it over from the UI repo many months ago when I was closing up issue filing in other repos. :) Ask @vincent99

Yes.. You login Monday morning, use it all day and Tuesday it looks still good but fails the first time you click something.

Version - master 3/17
Verified fixed


Excalidraw react component should support react server components, aka nextjs 13 without "use client"

@NateRadebaugh could you elaborate? In next you can disable ssr for components not supporting server side rendering.

Yes I think what I'm asking for is to explicitly support SSR. For instance, I have a use case where the server generates a static chart that I'd like to be rendered to the front-end, ideally without any javascript at all since I don't need it to be interactive.

@NateRadebaugh your use case could be covered by a server-side renderer (excalidraw (json) -> png/svg), but that's only when the drawing is small. For large drawings you still need interaction to pan around and support zooming.