Linux GUI client crashes after clicking on "Login"

I am not sure if we can support this currently but trying to run the GUI client on my system crashes after clicking on "Login". When running it through gdb, I was able to capture the following backtrace:
#0  0x00007ffff21d7ab9 in g_type_check_instance () from /nix/store/n2x4y1n23m8xnq1gpl3f9vf43vfifcf9-glib-2.78.6/lib/libgobject-2.0.so.0
#1  0x00007ffff21cced4 in g_signal_handlers_disconnect_matched () from /nix/store/n2x4y1n23m8xnq1gpl3f9vf43vfifcf9-glib-2.78.6/lib/libgobject-2.0.so.0
#2  0x00007ffff26bad5d in gtk_accel_label_set_accel_closure () from /nix/store/1w549xnfbx1ja7r0z251103ghj5vnhzs-gtk+3-3.24.41/lib/libgtk-3.so.0
#3  0x00007ffff26baf87 in gtk_accel_label_set_accel_widget () from /nix/store/1w549xnfbx1ja7r0z251103ghj5vnhzs-gtk+3-3.24.41/lib/libgtk-3.so.0
#4  0x00007ffff26bb04b in gtk_accel_label_destroy () from /nix/store/1w549xnfbx1ja7r0z251103ghj5vnhzs-gtk+3-3.24.41/lib/libgtk-3.so.0
#5  0x00007ffff21b3431 in g_closure_invoke () from /nix/store/n2x4y1n23m8xnq1gpl3f9vf43vfifcf9-glib-2.78.6/lib/libgobject-2.0.so.0
#6  0x00007ffff21c5fca in signal_emit_unlocked_R.isra.0 () from /nix/store/n2x4y1n23m8xnq1gpl3f9vf43vfifcf9-glib-2.78.6/lib/libgobject-2.0.so.0
#7  0x00007ffff21c7b8c in signal_emit_valist_unlocked () from /nix/store/n2x4y1n23m8xnq1gpl3f9vf43vfifcf9-glib-2.78.6/lib/libgobject-2.0.so.0
#8  0x00007ffff21cd832 in g_signal_emit_valist () from /nix/store/n2x4y1n23m8xnq1gpl3f9vf43vfifcf9-glib-2.78.6/lib/libgobject-2.0.so.0
#9  0x00007ffff21cd8df in g_signal_emit () from /nix/store/n2x4y1n23m8xnq1gpl3f9vf43vfifcf9-glib-2.78.6/lib/libgobject-2.0.so.0
#10 0x00007ffff295b520 in gtk_widget_dispose () from /nix/store/1w549xnfbx1ja7r0z251103ghj5vnhzs-gtk+3-3.24.41/lib/libgtk-3.so.0
#11 0x00007ffff21b9f88 in g_object_run_dispose () from /nix/store/n2x4y1n23m8xnq1gpl3f9vf43vfifcf9-glib-2.78.6/lib/libgobject-2.0.so.0
#12 0x00007ffff2727298 in gtk_container_destroy () from /nix/store/1w549xnfbx1ja7r0z251103ghj5vnhzs-gtk+3-3.24.41/lib/libgtk-3.so.0
#13 0x00007ffff21b3431 in g_closure_invoke () from /nix/store/n2x4y1n23m8xnq1gpl3f9vf43vfifcf9-glib-2.78.6/lib/libgobject-2.0.so.0
#14 0x00007ffff21c5fca in signal_emit_unlocked_R.isra.0 () from /nix/store/n2x4y1n23m8xnq1gpl3f9vf43vfifcf9-glib-2.78.6/lib/libgobject-2.0.so.0
#15 0x00007ffff21c7b8c in signal_emit_valist_unlocked () from /nix/store/n2x4y1n23m8xnq1gpl3f9vf43vfifcf9-glib-2.78.6/lib/libgobject-2.0.so.0
#16 0x00007ffff21cd832 in g_signal_emit_valist () from /nix/store/n2x4y1n23m8xnq1gpl3f9vf43vfifcf9-glib-2.78.6/lib/libgobject-2.0.so.0
#17 0x00007ffff21cd8df in g_signal_emit () from /nix/store/n2x4y1n23m8xnq1gpl3f9vf43vfifcf9-glib-2.78.6/lib/libgobject-2.0.so.0
#18 0x00007ffff295b520 in gtk_widget_dispose () from /nix/store/1w549xnfbx1ja7r0z251103ghj5vnhzs-gtk+3-3.24.41/lib/libgtk-3.so.0
#19 0x00007ffff21b9f88 in g_object_run_dispose () from /nix/store/n2x4y1n23m8xnq1gpl3f9vf43vfifcf9-glib-2.78.6/lib/libgobject-2.0.so.0
#20 0x00007ffff281936d in gtk_menu_shell_forall () from /nix/store/1w549xnfbx1ja7r0z251103ghj5vnhzs-gtk+3-3.24.41/lib/libgtk-3.so.0
#21 0x00007ffff2727298 in gtk_container_destroy () from /nix/store/1w549xnfbx1ja7r0z251103ghj5vnhzs-gtk+3-3.24.41/lib/libgtk-3.so.0
#22 0x00007ffff21b34f0 in g_closure_invoke () from /nix/store/n2x4y1n23m8xnq1gpl3f9vf43vfifcf9-glib-2.78.6/lib/libgobject-2.0.so.0
#23 0x00007ffff21c5fca in signal_emit_unlocked_R.isra.0 () from /nix/store/n2x4y1n23m8xnq1gpl3f9vf43vfifcf9-glib-2.78.6/lib/libgobject-2.0.so.0
#24 0x00007ffff21c7b8c in signal_emit_valist_unlocked () from /nix/store/n2x4y1n23m8xnq1gpl3f9vf43vfifcf9-glib-2.78.6/lib/libgobject-2.0.so.0
#25 0x00007ffff21cd832 in g_signal_emit_valist () from /nix/store/n2x4y1n23m8xnq1gpl3f9vf43vfifcf9-glib-2.78.6/lib/libgobject-2.0.so.0
#26 0x00007ffff21cd8df in g_signal_emit () from /nix/store/n2x4y1n23m8xnq1gpl3f9vf43vfifcf9-glib-2.78.6/lib/libgobject-2.0.so.0
#27 0x00007ffff295b520 in gtk_widget_dispose () from /nix/store/1w549xnfbx1ja7r0z251103ghj5vnhzs-gtk+3-3.24.41/lib/libgtk-3.so.0
#28 0x00007ffff21b84b0 in g_object_unref () from /nix/store/n2x4y1n23m8xnq1gpl3f9vf43vfifcf9-glib-2.78.6/lib/libgobject-2.0.so.0
#29 0x00007ffff27255c8 in gtk_container_remove () from /nix/store/1w549xnfbx1ja7r0z251103ghj5vnhzs-gtk+3-3.24.41/lib/libgtk-3.so.0
#30 0x00007ffff295b444 in gtk_widget_dispose () from /nix/store/1w549xnfbx1ja7r0z251103ghj5vnhzs-gtk+3-3.24.41/lib/libgtk-3.so.0
#31 0x00007ffff21b84b0 in g_object_unref () from /nix/store/n2x4y1n23m8xnq1gpl3f9vf43vfifcf9-glib-2.78.6/lib/libgobject-2.0.so.0
#32 0x00007fffea600e87 in app_indicator_set_menu () from /nix/store/dhrqfsvpdzkg2lcfrmi3ma7r2cr9wj9a-libappindicator-gtk3-12.10.1+20.10.20200706.1/lib/libappindicator3.so.1
#33 0x000055555644f607 in libappindicator_sys::app_indicator_set_menu (self_=0x555557ab8830, menu=0x5555588ea250) at src/lib.rs:985
#34 0x0000555556449436 in libappindicator::AppIndicator::set_menu (self=0x555557ab5520, menu=0x7ffffffd71c8) at src/lib.rs:59
#35 0x00005555563b1b8d in tao::platform_impl::platform::system_tray::SystemTray::set_menu (self=0x555557ab54e8, tray_menu=0x7ffffffd99b0) at src/platform_impl/linux/system_tray.rs:103
#36 0x00005555563e34a4 in tao::system_tray::SystemTray::set_menu (self=0x555557ab54e8, tray_menu=0x7ffffffd99b0) at src/system_tray.rs:111
#37 0x0000555555f55adb in tauri_runtime_wry::handle_user_message<tauri::EventLoopMessage> (event_loop=0x7ffffffdde00, message=..., context=..., web_context=0x7ffffffde020) at /home/thomas/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tauri-runtime-wry-0.14.8/src/lib.rs:2744
#38 0x0000555555a1d01a in tauri_runtime_wry::handle_event_loop<tauri::EventLoopMessage> (event=..., event_loop=0x7ffffffdde00, control_flow=0x7ffffffdcd00, context=..., web_context=0x7ffffffde020) at /home/thomas/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tauri-runtime-wry-0.14.8/src/lib.rs:3052
#39 0x0000555555a21d9d in tauri_runtime_wry::{impl#50}::run::{closure#0}<tauri::EventLoopMessage, tauri::app::{impl#18}::run::{closure_env#0}<tauri_runtime_wry::Wry<tauri::EventLoopMessage>, firezone_gui_client::client::gui::run::{closure_env#3}>> (event=..., event_loop=0x7ffffffdde00, control_flow=0x7ffffffdcd00)
    at /home/thomas/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tauri-runtime-wry-0.14.8/src/lib.rs:2325
#40 0x0000555555aa1812 in tao::platform_impl::platform::event_loop::{impl#1}::run_return::{closure#0}<tauri_runtime_wry::Message<tauri::EventLoopMessage>, tauri_runtime_wry::{impl#50}::run::{closure_env#0}<tauri::EventLoopMessage, tauri::app::{impl#18}::run::{closure_env#0}<tauri_runtime_wry::Wry<tauri::EventLoopMessage>, firezone_gui_client::client::gui::run::{closure_env#3}>>> () at /home/thomas/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tao-0.16.8/src/platform_impl/linux/event_loop.rs:1034
#41 0x0000555555a6f367 in glib::auto::main_context::MainContext::with_thread_default<i32, tao::platform_impl::platform::event_loop::{impl#1}::run_return::{closure_env#0}<tauri_runtime_wry::Message<tauri::EventLoopMessage>, tauri_runtime_wry::{impl#50}::run::{closure_env#0}<tauri::EventLoopMessage, tauri::app::{impl#18}::run::{closure_env#0}<tauri_runtime_wry::Wry<tauri::EventLoopMessage>, firezone_gui_client::client::gui::run::{closure_env#3}>>>> (self=0x7ffffffddd38, func=...) at /home/thomas/.cargo/registry/src/index.crates.io-6f17d22bba15001f/glib-0.15.12/src/main_context.rs:156
#42 0x0000555555aa0abe in tao::platform_impl::platform::event_loop::EventLoop<tauri_runtime_wry::Message<tauri::EventLoopMessage>>::run_return<tauri_runtime_wry::Message<tauri::EventLoopMessage>, tauri_runtime_wry::{impl#50}::run::{closure_env#0}<tauri::EventLoopMessage, tauri::app::{impl#18}::run::{closure_env#0}<tauri_runtime_wry::Wry<tauri::EventLoopMessage>, firezone_gui_client::client::gui::run::{closure_env#3}>>> (self=0x7ffffffdde00, callback=...) at /home/thomas/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tao-0.16.8/src/platform_impl/linux/event_loop.rs:958
#43 0x0000555555aa1e6d in tao::platform_impl::platform::event_loop::EventLoop<tauri_runtime_wry::Message<tauri::EventLoopMessage>>::run<tauri_runtime_wry::Message<tauri::EventLoopMessage>, tauri_runtime_wry::{impl#50}::run::{closure_env#0}<tauri::EventLoopMessage, tauri::app::{impl#18}::run::{closure_env#0}<tauri_runtime_wry::Wry<tauri::EventLoopMessage>, firezone_gui_client::client::gui::run::{closure_env#3}>>> (self=..., callback=<error reading variable: Cannot access memory at address 0x18>) at /home/thomas/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tao-0.16.8/src/platform_impl/linux/event_loop.rs:912
#44 0x00005555557a8ba9 in tao::event_loop::EventLoop<tauri_runtime_wry::Message<tauri::EventLoopMessage>>::run<tauri_runtime_wry::Message<tauri::EventLoopMessage>, tauri_runtime_wry::{impl#50}::run::{closure_env#0}<tauri::EventLoopMessage, tauri::app::{impl#18}::run::{closure_env#0}<tauri_runtime_wry::Wry<tauri::EventLoopMessage>, firezone_gui_client::client::gui::run::{closure_env#3}>>> (self=..., event_handler=<error reading variable: Cannot access memory at address 0x18>) at /home/thomas/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tao-0.16.8/src/event_loop.rs:179
#45 0x0000555555a218fc in tauri_runtime_wry::{impl#50}::run<tauri::EventLoopMessage, tauri::app::{impl#18}::run::{closure_env#0}<tauri_runtime_wry::Wry<tauri::EventLoopMessage>, firezone_gui_client::client::gui::run::{closure_env#3}>> (self=..., callback=...)
    at /home/thomas/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tauri-runtime-wry-0.14.8/src/lib.rs:2299
#46 0x00005555557d5e53 in tauri::app::App<tauri_runtime_wry::Wry<tauri::EventLoopMessage>>::run<tauri_runtime_wry::Wry<tauri::EventLoopMessage>, firezone_gui_client::client::gui::run::{closure_env#3}> (self=..., callback=...)
    at /home/thomas/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tauri-1.6.7/src/app.rs:868
#47 0x0000555555a9dbae in firezone_gui_client::client::gui::run (cli=..., advanced_settings=...) at gui-client/src-tauri/src/client/gui.rs:272
#48 0x0000555555808aa2 in firezone_gui_client::client::run_gui (cli=...) at gui-client/src-tauri/src/client.rs:123
#49 0x000055555580b939 in firezone_gui_client::client::run () at gui-client/src-tauri/src/client.rs:74
#50 0x000055555596e8e6 in firezone_gui_client::main () at gui-client/src-tauri/src/main.rs:9

My glibc version is 2.38 if that matters. I am running kernel 6.8.11 on NixOS.

The crash handler is supposed to get backtraces too, they end up in the log directory
Ubuntu 20.04 (where we build the binaries) has glibc 2.31, and I thought glibc was supposed to be backwards-compatible  🤔
If we wanted really broad distro support we could bundle all the libs, and have 100 MB downloads, and at that point we may as well use Electron.
I am getting more serious that we should just use the OS' terminal and make a TUI app. We don't display any graphics except the Firezone logo.  We aren't even displaying stdout so bundling a crummy xterm clone might be doable. It would just look awful to investors

I fixed the title, it is not glibc but some gnome version I guess?

I am getting more serious that we should just use the OS' terminal and make a TUI app. We don't display any graphics except the Firezone logo.  We aren't even displaying stdout so bundling a crummy xterm clone and just using it as a character display might be doable. It would just look awful to investors

Wouldn't it make more sense to devise an auth scheme that works with the headless client? That one is already backwards compatible.

The headless client can do our auth scheme, the reason we have all these compatibility problems is the GUI for the settings window and the tray menu

Wouldn't it make more sense to devise an auth scheme that works with the headless client? That one is already cross-platform.

You might like a user-present CLI auth scheme? Yeah I think that would be good to have. It's a lot of work though. We need a new auth flow in the portal to handle CLI auth, and a websocket channel from CLI to portal to facilitate the exchange.

If the make the CLI keyring aware, we could use the same deep-link scheme by starting another instance of the CLI and saving the token.
Then, the next start of the background daemon can take the token and run in the background.


chore(release): v0.10.8 🎉

:robot: I have created a release beep boop
0.10.8 (2023-02-12)
Bug Fixes

deps: bump dev dependency on declapract-typescript-ehmpathy (8c5cdf2)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/ehmpathy/declapract/releases/tag/v0.10.8 :sunflower:


Relative Line Numbers

Hey, I know you said you wished you could add relative line numbers, but I managed to get it working with this plugin.
Figured maybe you could use it without having to rebuild the wheel :)
Cheers and thx for the awesome work!

That's a great tip, I'll post it in the Readme next time I get a few mins to work on the plugin :pray:

How about a pull request? :)

All help is greatly appreciated! :pray:

Oh oopsy, I'm kinda new to public pull requests!
Happy to see that it is helpful. Your plugin is insane! I can't live without it 🎉


Consider timeouts when parsing the HubProtocol messages on the server

Today we have no timeouts for parsing hub protocol messages (we do have a timeout for the handshake). We should be able to timeout if client don't send an entire message payload within some timeframe but we should also disable the timeouts in between messages.

The current POR involves exposing this feature (or similar) https://github.com/aspnet/KestrelHttpServer/blob/a92da1b8f42875efbf23176fc8cb3029a9a6c74e/src/Kestrel.Core/Features/IConnectionTimeoutFeature.cs#L11 into Microsoft.AspNetCore.Connections.Abstractions. Kestrel already implements this but disables it for upgraded connections. We could potentially take advantage of it by calling SetTimeout and CancelTimeout between our calls to parsing the various protocol messages.


[strong] Fix issue with placeholder parser

This allows us to use the template literal supported by V8/iojs

@domenic PTAL
With the old incorrect caching behavior (#1845) we did not share the tree between
parseStatement `x`

and
parseStatements `x`

but with the correct template behavior we end up with the same tree.

Makes sense in light of #1845.


pgcacher -top -limit 5 不准确

比如我执行
cat /data/file4g &> /dev/null

进程退出后，page cache是有缓存这个文件的。但是pgcacher -top -limit 5 无法扫描出

I probably know what the problem is. pgcacher scans the collection of files opened by the process. If the file is closed by the process, it cannot be traced. Because pgcacher cannot know which files he has opened.


Adding a Dockerfile

Hi,
As an intern in Microsoft, I'm currently working with the Open Application Model, Dapr, and of course oamctl.
While using oamctl, I've encountered some issues, namely with the Go version required, that is a bit on the older side, and conflicting with the Go version required by Dapr for example.
To address these issues, I've made a small Dockerfile that I'm currently using to run oamctl.
I thought it would be good to share it with the community, as people interested in OAM/oamctl would probably be accustomed to Docker.
Thanks to multistage building and upx, the whole image is only about 8MB. It is however pretty long to build, and it would maybe be better to host the image on the Docker Hub.

Forgot about usage.
This is how i use the image for the migrate example:
docker run -v [user_home_dir].kube:/root/.kube -v [oam_repo_dir]\examples:/root [image_name] migrate --deployment=deployment-2-migrate oam-app
For trait list :
docker run -v [user_home_dir].kube:/root/.kube [image_name] trait-list


[MXNET-1210 ] Gluon Audio - Example

Description
Contribute an Example for performing a task with Audio data that demonstrates the following abilities:

to be able to load audio (only .wav files supported currently) files and make an AudioDataset (NDArrays),
apply some popular audio transforms on the audio data( example scaling, MEL, MFCC etc.),
load the Dataset using Gluon's DataLoader, train a neural network ( Ex: MLP) with this transformed audio dataset,
perform a simple audio data related task such as sounds classification - 1 audio clip with 1 label( Multiclass sound classification problem).
have an end to end example for a sample Audio multi class classification task (Urban Sounds Classification)

Note : This example uses AudioFolderDataset and applies transforms to extract features from audio file and does a classification task. Current design of the AudioFolderDataset is below:
https://cwiki.apache.org/confluence/display/MXNET/Gluon+-+Audio
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[x] The PR title starts with [MXNET-$JIRA_ID], where $JIRA_ID refers to the relevant JIRA issue created (except PRs with tiny changes)
[x] Changes are complete (i.e. I finished coding on this PR)
[x] All changes have test coverage:
Steps in the example can be followed to test the example
[x] Code is well-documented
[x] To the my best knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change
[x] Example contributed

Comments

This feature allows to take first step in audio data related tasks and needs to be extended for more generic as well as advanced use cases

Design here- Dev list discussion here

Testing

Tested on p2.8xlarge instance ( Deep Learning AMI (Ubuntu) Version 18.0 )

@mxnet-label-bot add [pr-awaiting-review]
Thanks for your contribution @gaurav-gireesh

@sandeep-krishnamurthy @roywei Example created.
Could you help review this PR?
Thank you.

@marcoabreu Hi Marco! Can this PR be merged, if the required tests are passing, even if the new test steps are running? Thanks!

Hey, yeah feel free to move ahead. The new statuses are equivalent to the
old big pipeline :)
Am Fr., 30. Nov. 2018, 20:33 hat Gaurav Gireesh<EMAIL_ADDRESS>geschrieben:

@marcoabreu https://github.com/marcoabreu Hi Marco! Can this PR be
merged, if the required tests are passing, even if the new test steps are
running? Thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/apache/incubator-mxnet/pull/13325#issuecomment-443314250,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ARxB6_LLj3mI2tWiothGhS0lxIBZIeueks5u0Yf_gaJpZM4YqOjQ
.

@mxnet-label-bot remove [pr-awaiting-merge]


Pass props via router-link

What problem does this feature solve?
It is possible to pass props via the defined routes. Unfortunately, I can't get the complete object passed to the to attribute from the route props function.
routes:
routes: {
    {
        path: '/device/:id',
        component: load('device/DeviceView'),
        props: (route) => { console.log(route) // does not contain route.props }
    }
}

template
<router-link :to="{path: `device/${device.UniqueID}`, props: {device: device}}">show device</router-link>

What does the proposed API look like?
Same as above. I would like to pass the props via router-link:
<router-link :to="{path: `device/${device.UniqueID}`, props: {device: device}}">show device</router-link>

Hi!
Sorry, but we intentionally leave hidden state out of vue-router. In other words, if it's not in the url, it should be stored somewhere else, like in a vuex store.
For you specific scenario, you could inject the device by using the unique id in the props function

@posva

if it's not in the url, it should be stored somewhere else, like in a vuex store.
But what if I have 100 router-links on a page and I need on a click related data which is only available at the time of looping through the links at the HTML / template level ? A @click listener doesn't work on router-links. Currently I would have to build custom complicated mapping functionality and custom route listener. Makes absolutely no sense to me.

So what is actually the intention by not allowing to append data to router-link?

just found this here!
https://github.com/vuejs/vue-router/issues/800
:D
So now I can use vuex store to transmit the data.
But would still love to find out the reason why exactly it's not possible to send data with router-link for example as a data property: $router.data


Check that def get_alpha_helix_length_and_location(secondary_struc, min_length=8)

At the moment there may be an issue with this function. Double check this work as expected.

Fixed


I would like to change org-capture-templates in my config.el, but doom's org/config.el will override it

I would like to configure that variable in my config.el as I do with all org variables, that is
(use-package! org
  :defer t
  :custom
  (org-directory "~/Dropbox/org")
  ;; Python executable for source blocks
  (org-babel-python-command "python3")
  (org-habit-graph-column 67)
  (org-log-into-drawer t)
  (org-modules '(ol-bibtex org-habit))
  )

Unfortunately, if I try to customize org-capture-templates, anything that I write in my config will be overriden by this doom's org config.el.
Configuring these variables that Doom reasonably setups should be an easy task, but right now, the only way of fixing it that I came up was to write this in my config.el
(setq org-load-hook (append org-load-hook (list (lambda () (setq org-capture-templates '(("a" "My custom todo" entry
                                                                                (file+headline +org-capture-todo-file "Inbox")
                                                                                "* [ ] %?
%i
%a" :prepend t)))))))

which is kind of hacky, but gets the job done.
What would be the stylish way to go in Doom Emacs? Is there any consensus over this topic of configuring Doom's setup?
Thank you very much :smile:

If you want to override Doom's defaults, use (after! org ...). This is how all packages should be configured.
(after! org
  (setq org-capture-templates ...))


No such file or directory, open '/github/workspace/.github/labels.json'

I have created my labels.json file inside of the appropriate /.github/ directory, but when I run the action, I get the following error message:
(node:1) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, open '/github/workspace/.github/labels.json'
    at Object.openSync (fs.js:439:3)
    at Object.readFileSync (fs.js:344:35)
    at run (/index.js:15:33)
     at process._tickCallback (internal/process/next_tick.js:68:7)

It seems it is looking for the file in /github/workspace/.github/labels.json for some reason. Is it possible the GITHUB_WORKSPACE variable can be different for various repos? https://github.com/lannonbr/issue-label-manager-action/blob/master/index.js#L8-L12
Edit: if it helps, here's the test repo I'm using for this: https://github.com/chrisblakley/Actions-Again/commit/23a9e0dd5c48b343a840dab577ccf9eee7a2703f/checks

This fixed the issue for me as well.  Might be helpful for the README to include this?

@oalders Definitely. If you're participating in Hacktoberfest starting tomorrow, I could happily accept a PR for this. you can technically do it whenever but if you want to participate in the event, PRs are only counted during October

@lannonbr I will do this tomorrow.  :)


Allow disabling extending from remote sources with giget.

Describe the feature
I want to make it possible to simply extend from local files, however I don't want to support remote config extending from github, gitlab or alike. I currently dont see a way how this is done. A simple config option to disable remote extending would be really helpful and shouldn't be too hard to do.
Additional information

[ ] Would you be willing to help implement this feature?

Makes sense. PR welcome 👍🏼


Support for Symfony3

Is this bundle ready for Symfony3?

Not the latest tag 1.3.1 but master is
@sheeep or @mitom could we get a new tagged version for Symfony 2.8 + 3.0 ?

+1

ping @sheeep @bytehead

I just found out that I have made som changes directly in the code.
You cant get Request from the container anymore, you need to get Request_Stack and then getMasterRequest.
I will have a PR up tomorrow - and with that PR, I have tested upload and response in Symfony 3 (but not orphange stuff)

PR #202 is up

Closed in favor of #202.


[KYUUBI #3720][FOLLOWUP] Using correct config version for CTL_BATCH_LOG_ON_FAILURE_TIMEOUT

Why are the changes needed?

Set the config version to 1.6.1.
How was this patch tested?

[ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible

[ ] Add screenshots for manual tests if appropriate

[x] Run test locally before make a pull request

thanks, merged to master and 1.6.1


Updated Config File

Added the missing module

Thanks. Is already be taking care in the other open PR. Would be great to see more contributions from you. Thank you again!


Fix error when moving FileSystem dock

Moving the FileSystem dock between different slots produces this error:

ERROR: Signal 'folder_color_changed' is already connected to given callable 'EditorDirDialog::reload' in that object.
at: connect (core/object/object.cpp:1431)

For the filesystem_changed signal, it's always connected upon entering the tree and is disconnected when exiting the tree. The redundant connection check is removed.
For the folder_color_changed signal, it's the same as filesystem_changed. This PR disconnects it when exiting the tree. So there won't be errors anymore.
For the item_collapsed signal, it can be moved to the constructor.

Thanks!


config: Refactor ConfigMap loading process

This PR extracts loading of the ConfigMap's full name to a new file in the config package "environment.go".
This was done in order to consume the ConfigMap's full name in the future "reporter" entity.
Furthermore, This PR also removes the config.Loader struct, and replaces it with config.NewFromConfigMap().
This was done because the first commit left the config.Loader struct only with a client member.

Change: Changed second commit's subject.

Change: Removed the "environment" package.

Change: Renamed NewFromConfigMap() => ReadFromConfigMap()


design mini navigation framework

The framework needs to allow it to be used across multiple commands and then be made generic enough to be used by other applications. Eventually, this framework will be implemented in either/and arcadia and cobrass, depending on relevant pieces of functionality. Actially, a clear separation should be established between the functionality that is arcadia specific and that which is more generc than that and should be implemented in cobrass.
Legend:

🦄 generic
🧙♂specialised

Need the following entities:

EntryBase 🦄 struct, contains generic properties such as the navigation session, and perhaps a config provider (wraps viper)
CommandEntry struct: (eg ShrinkEntry 🧙♂), with embedded EntryBase 🦄
🦄 the entry should have a Configure method that allows it to configure the navigation session. EntryBase will also have a Configure method, to configure the generic properties. We need to allow EntryBase and the command Entry to Configure the session.
each command should have an entry function, eg RunShrink. This entry point should create the ShrinkEntry
entry needs to define a workflow🦄. We can have a dynamic workflow, or a fixed workflow. The fixed workflow contains steps: begin, : process and : end. The fixed workflow will be used by the entry. A dynamic workflow can be composed of custom steps.
workflow runner 🦄 executes the defined steps. The workflow runner is not aware of the begin, process and end steps. All it sees is a sequence and it just runs them transparently.
execution profiles 🦄 : simple (typically used for low complexity operations, typically cpu bound short running tasks) or scheduled (used by longer running and probably concurrent operations requiring synchronisation, typically used for IO bound operations)
task scheduler 🦄 to manage execution of go routines and channels

It should be easy to switch a command to use the simple or scheduled profiles. Eg, a visit command which will defined to use the simple profile, should be able to be switched over to the scheduled profile simply by setting a property.
Configuring the navigation and then setting up the appropriate workflow are 2 separate phases. A workflow step will need to execute the navigator, therefore the workflow infrastructure has a dependency on the navigator, but not the other way around.

This is over engineered. We don't need a workflow, so get rid of that part. The execution profile can remain with sync and async versions. Calling the execution profiles both block and are transparent to the client. Under the covers, the async version will orchestrate all the synchronisation primitives required to execute navigation concurrently, whilst the sync version will simply run in a blocking manner.
We need  to handle ui updates accordingly and separately from the core navigation activity. The cli will need to display the what has currently executed in the ui

There is going to be a limit of the asynchronous model that can be implemented externally to extendio navigation. I've realised that the only concurrent model that can be defined is with the folders with files subscription type. So for a single notification (ie the invocation of the client callback), we can spawn a go routine for each child file of the current folder traverse item. We define a unit of work that will handle the processing of a single file and keep spawning a go routine for each unit of work. This can be achieved using the command/unit-of-work pattern. We implement thru put throttling by spawning no more than n no of go routines to maximise CPU usage. We also use a journal style technique where we pre write the work that is to be completed the the form of a temporary file. This way, if the process is terminated part way thru the batch, the user can invoke a resume at which point we check which target files already exist and therefore do not need to be recomputed. We also check which journal files exist which defines which files were being processed at the time of the last interrupt. From this analysis, we can reconstruct the remaining workload for this folder and continue where we left off from.
So we define a workload first, which is then decomposed into a stream of units of work.

Remember to separate actual work from ui updates. This way, the executable functionality can be reused easily. This generic functionality will either end up in extendio or Arcadia to aid reuse.

The other model for concurrency during directory traversal would need to be built directly into the extendio navigator. The navigator would probably have to return a channel of traverse result, rather the the traverse result itself. When the go routine is complete it signals it's completion by sending the result back thru the channel. The navigator will keep track of outstanding requests via the channels and continue navigation whilst there are still available slots. What we mean by available slots is that if we say we want to allow n concurrent go routines, we keep spawning until we reach n. As we get notified via their associated channels we can dispatch another unit of work. A point of complexity would be how to implement the fast forward feature. We can handle this by performing the fast forward phase single threaded. Then from this trigger point we can then proceed on a concurrent basis.


Test suite should detect warning/error level logs, and fail.

I'm going to grab this one. I'll have a pr soon.


add sync_model_states parameter to fix resume from checkpoint with fsdp

Nice! I never got this to work for resume before.
One note: this adds a slight overhead. Perhaps, we only need to check for this IF we need to resume training and error ?
https://github.com/pytorch/pytorch/blob/fd214aa8be7160cba5c6efec7a1b06c9c33b37a4/torch/distributed/fsdp/fully_sharded_data_parallel.py#L348-L354

@NanoCode012 So I think it has something to do with the weights too when you save them. This is still a WIP as I need to test it, but I've tried it with these settings to do the resume and it didn't work, but a hunch says I need it when training too.

Interesting it says here that it's for loading checkpoint to broadcast from rank 0 to others. Do we need to change model loading script I wonder?
https://github.com/pytorch/pytorch/blob/fd214aa8be7160cba5c6efec7a1b06c9c33b37a4/torch/distributed/fsdp/api.py#L296-L321

Interesting, unfortunately all the load from checkpoint logic is baked into the HF trainer iirc.
this part, right?
        >>> if dist.get_rank() == 0:
        >>>     # Load checkpoint only on rank 0 to avoid memory redundancy
        >>>     state_dict = torch.load("my_checkpoint.pt")
        >>>     model.load_state_dict(state_dict)

here are some notes for tracking what I've found https://github.com/huggingface/transformers/issues/25100#issuecomment-1669712422

should we add a warning that resume functionality with packing and FSDP doesn't work currently? (when the trainer is tarted with fsdp and sample_packing) This way the user is aware before they start training and it isn't a surprise.


memory leak

When CancellationToken object is created it obtains strong reference to CancellationTokenSource object via state = .Pending(source)
But CancellationTokenSource object have strong reference to CancellationToken object via token field. So, neither CancellationTokenSource object, nor CancellationToken will ever be released.

Yes, good point.
I'm looking into how to fix this, preferably without giving up performance.

Well, I'm pretty sure, that creating CancellationToken object on demand will not hurt performance in a noticeable manner. It is struct, it will copy on each assignment anyway. So, no need for a reference from CancellationTokenSource.

Right, of course.
I've changed the token to be a computed property: d2e2e69a790f9a27f02b3449ba7f66e15c49d22c
If you're using cocoa pods, this has been released as version 0.1.1


Optimize Analytics Tracking Calls

This is a Quality of Life change.
Right now Analytics tracking methods are being called in the main code/mutations, this is an issue because it slows down the backend from answering the frontend and if the tracking break, it breaks the whole code.
Solutions:

Refactor Tracking calls into it's own module / methods / classes so it's not spread out through the whole code base.
Move tracking calls to a background Job that it's executed after the backend answers the frontend.

@divine-comedian @cquinterom096 shall we start this?
is it needed to be more clarified?


Feature: Add to playlist button/keyboard shortcut

First of all, thanks for SpotMenu, I love it!
I was thinking about a feature that would be helpful for me. I am always discovering new songs while listening to Spotify and I found the whole process of opening the Spotify window/right click/add the playlist very annoying. That's why I thought that a keyboard shortcut/button to directly add the current song playing to a playlist would be amazing!

Oups, just saw you already talked about this in other posts! Sorry

No problem 😉 I'll keep this issue open just in case it does get finally implemented, so I won't forget that a keyboard shortcut will also come in handy

Would love to see this...!
- Mute
- Next
- Previous
- Start

:D By the way love your software...! Keep going!

@MatzeWI , the Spotify app already works with the media keys on the Mac keyboard, play/pause, next, previous.


RReadWriteLock reentry is incompatible

This issue is related to #891.

write lock for 10 seconds
write lock for 1 second

Now after 1 second the whole lock is released. I'm not sure if this is a bug, but logically the system should not unlock the because the first lock request is done for 10 seconds.
`
ExecutorService executor = Executors.newCachedThreadPool(new ThreadFactoryBuilder().setNameFormat("redis-%d").build());
RedissonClient client = Redisson.create(config);
	RReadWriteLock rw1 = client.getReadWriteLock("test2s3");

	RLock l1 = rw1.writeLock();
	System.out.println(l1.tryLock(10000, 10000, TimeUnit.MILLISECONDS));
	RLock l2 = rw1.writeLock();
	System.out.println(l2.tryLock(1000, 1000, TimeUnit.MILLISECONDS));
	executor.execute(()->{
		RReadWriteLock rw2 = client.getReadWriteLock("test2s3");
		try {
			if (rw2.writeLock().tryLock(3000, 1000, TimeUnit.MILLISECONDS)) {
				System.out.println("This is not expected!");
			}
		} catch (InterruptedException e) {
			e.printStackTrace();
		}
	});
	executor.shutdown();
	executor.awaitTermination(10, TimeUnit.MINUTES);
	client.shutdown();

`
Manually calling l2.unlock() manually works as expected, that is fixed in #891

Fixed! Thanks for report!


Upgrade to ranch 1.6

This is a minor upgrade for us because we don't use many of Ranch's
features. It's useful to upgrade now to avoid any new code being added
that might use recently deprecated features that will be removed in
Ranch 2.0.
https://ninenines.eu/docs/en/ranch/1.6/guide/migrating_from_1.5/

Perhaps we should integrate with Dependabot to automate these dependency bumps. It's great because it submits PRs whenever dependencies can be bumped. I use it on one of my own projects and it works great.

That seems like it could be useful. How do you handle the cases where project code should also be updated?

It allows maintainers to edit the PRs it posts, so if there are project changes required someone will need to make edits. Most of the time I've found the merges are pretty clean and don't require manual intervention.
It also supports commands like @dependabot ignore this [patch|minor|major] version and @dependabot ignore this dependency if you don't want to update a dependency. Useful in cases where upgrading the version is not trivial.
Here's an example of a PR it submitted for me to upgrade ranch from 1.5 to 1.6: https://github.com/thecodeboss/minecraft/pull/4

Do newer versions of ranch support gracefully shutdown?

I'm not sure, and I don't see it listed in the 2.0 roadmap. Our use of Ranch is pretty limited to just the client, and we could probably drop it if we implemented our own connection pool.


I cloned this repo and getting error when i run npm install --save-dev gulp-atomizer

❯❯❯❯ npm install --save-dev gulp-atomizer              ~/m/gulp-atomizer master
npm ERR! Darwin 16.1.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" "--save-dev" "gulp-atomizer"
npm ERR! node v6.7.0
npm ERR! npm  v3.10.8
npm ERR! code ENOSELF

npm ERR! Refusing to install gulp-atomizer as a dependency of itself
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR!     <https://github.com/npm/npm/issues>

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/jitendravyas/my-projects/gulp-atomizer/npm-debug.log

I can't reproduce this.  Do you still have this problem?

No sorry it was my mistake. This is plugin repo not example repo


Access to Client Outbound Publishing queue

Is there any way to see how large the outbound publishing queue is? We would like to throttle the data our application publishes if the outbound publishing queue is getting too large/backed up but I don't see any way to determine the size.
Also asked in Discussions...

Do you refer to the server or client?

Client.  We have an app that is connected via a cellular modem and want to slow down traffic if it becomes backed up sending traffic to the broker.

The client has no internal queue. So you can simply check the network state before publishing.
With the managed client this is not possible.


Pull request for v1.3

Adding modifications in Geant4 simulation and first scripts for DESY test beam data conversion.

Accepting for v1.3


chore: 🤖 update references to use association signing managers

Description
Updates the references to use the association npm signing managers
Breaking Changes

JIRA Link

Checklist

[ ] Updated the Readme.md (if required) ?

:tada: This PR is included in version 15.0.1-beta.2 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 15.1.0-alpha.1 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Bumped ccx-rules-ocp version

Codecov Report
Base: 72.68% // Head: 72.68% // No change to project coverage :thumbsup:

Coverage data is based on head (cf2750e) compared to base (c2d8e3f).
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #415   +/-   ##
=======================================
  Coverage   72.68%   72.68%
=======================================
  Files          11       11
  Lines         582      582
=======================================
  Hits          423      423
  Misses        134      134
  Partials       25       25

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

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


Update snmprec & test for nasuni-filer profile

What does this PR do?

See title
Motivation

Mappings had wrong values in snmprec (and hence were missing in the test as tags)
Additional Notes

Review checklist (to be filled by reviewers)

[ ] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[ ] Changelog entries must be created for modifications to shipped code
[ ] Add the qa/skip-qa label if the PR doesn't need to be tested during QA.

Included in #15720


readme: update custom command instructions

Patch 'build_py' instead of 'develop/install', as this will ensure that generated files are created/up-to-date before 'build_py' is run and for all commands ('develop/install/bdist_egg/...') that depend on 'build'.

Thank you!


Convert Ursula PR tests to use a Heat provisioner scheme

Problem resolved:
Currently Ursula PR tests are setup using the Ansible os_* module to provision nodes and other resources.  This approach to provisioning and deployment orchestration for test environments is too cumbersome and not a good fit for creating multiple test environments.
Solution of this commit:
This commit is to add the Heat provisioning capability to the Ursula PR tests and move what we currently have off of Ansible os_* modules onto Heat. Heat is decent at resource provisioning and deployment orchestration and defining environments is much cleaner with the use of templates.
Some explanations for my code changes:

the tmp/ folder is required by ursula-cli to store the generatd ssh_config and ssh_key file, without creating that folder in advance, ursula-cli will raise an error;
I removed the "--sudo" arg from ursula commands in test/setup and test/run scripts, that is to avoid duplication since ursula-cli will always add that when heat provisioner is being used.
I have put the fixed content of envs/example/ci-full/group_vars/all.yml into that file directly, and let test/setup script only write the dynamic content during runtime with an appending mode instead of previous overwriting mode.

Can one of the admins verify this patch?

"ok to test" to accept this pull request for testing
"test this please" for a one time test run
"add to whitelist" to add the author to the whitelist

ok to test

I think this is okay

retest

@j2sol Thanks for your review and comments, fyr, the PR test for this will only succeed after my another PR for jjb gets merged. https://github.blueboxgrid.com/blue-box-cloud/jenkins-job-builder/pull/59

retest

I submitted PR https://github.com/blueboxgroup/ursula-cli/pull/48

FWIW we set OS_PROJECT_ID in our stackrc on the Jenkins slave.  We don't sent OS_PROJECT_NAME or OS_TENANT_NAME.

We put support for OS_PROJECT_NAME into our stackrc's and I've updated the jenkins slaves, so all that remains is the change to ursula-cli to look for it to merge.

retest

Yay!


apply mb_strtolower to command_name in processUpdate

Keys in \Longman\TelegramBot\Telegram::$commands_objects get register as all lowercase, but not queried the same way. Apply mb_strtolower to $command_tmp in \Longman\TelegramBot\Telegram::processUpdate to short circuit \Longman\TelegramBot\Telegram::getCommandObject.
fixes #1197
Obviously, there are many ways to apply mb_strtolower here, this could also be done in \Longman\TelegramBot\Telegram::getCommandObject as the first statement. This is how I did it, to patch my local installation.

Closed, as implemented in #1207 and #1209


Cast equivalent float64s to int64 rather than failing with ErrInvalidValue

When working with Pandas (both with and without doltpy) I ran into this issue multiple times - integer columns are converted to floats (due to the way Python handles nan values), which then causes dolt table import to complain with the following error despite the floats being "integral":
Rows Processed: 0, Additions: 0, Modifications: 0, Had No Effect: 0

A bad row was encountered while moving data.
Bad Row:
error: '10.0' is not a valid value for 'INT'
These can be ignored using the '--continue'

This PR converts "integral"/equivalent floats to int64s to prevent this from happening. This still prevents non-integral floats from being imported, e.g.:
Rows Processed: 0, Additions: 0, Modifications: 0, Had No Effect: 0

A bad row was encountered while moving data.
Bad Row:
error: '10.1' is not a valid value for 'INT'
These can be ignored using the '--continue'

I'm not sure how/where this should be tested, but if it is an acceptable PR I'll be happy to write the tests for it too.
P.S. The isIntegral function can be removed and used in the if-statement as a condition if that's more preferable, though I think  it should be documented (perhaps in a comment) since it's purpose may not be immediately obvious.

Think I'm fine with this, but it needs tests, both for this unit and the engine:
numbertypes_test.go insert_queries.go

OK, will do. Is my last commit (running format_repo.sh) OK or should I ignore that? It doesn't seem to have been run on most of the code.

 It looks like you're using a slightly different version of go fmt than our CI is, so it's introducing a lot of differences.
I can reformat the code once you have tests in.

I'm not sure how to run the tests - could you please detail the commands?

https://www.dolthub.com/blog/2021-09-08-how-to-contribute-to-dolt/
From there:
~/dolt_workspace/dolt/go $ go test ./...

~/dolt_workspace/dolt/go $ go test ./...

Thanks! I ran this command before but I wasn't sure which tests it was running exactly.

All the tests passed apart from error: '9223372036854775807' is not a valid value for 'BIGINT' which occurred even before my changes were made.

@zachmu Fixed! I would prefer if it didn't accept non-integral floats/gave a warning when truncating, but oh well!

Replaced with #630


[FEATURE_REQUEST] Setting the amount of information displayed by statuscheck

Is your feature request related to a problem? If so, please describe.
When using the statusCheck feature hovering over the green dot it will for some items it displays a message along the lines of:
server responded with <code> OK <time>

For other items it displays a message like:
example.com responded with <code> OK <time>

In my scenario we are using statusCheckUrl to do health checks to the back-ends of our services with internal only domain names. These internal only domain names are showing in the statuschecks, and should not be known to users using the dashboard.
Describe the solution you'd like
Could an option be created to set the amount of information given from the statuscheck on an item by item basis?
Examples:

Setting it to full would show the information as it is currently implemented .

statusCheckInfo: full

Setting it to limited would only show the check mark and time.

statusCheckInfo: limited

Setting it to none would prevent the status windows from appearing when hovering over the status icon.

statusCheckInfo: none

Example in item configuration:
    items:
      - title: example
        url: https://example.com/
        statusCheckInfo: limited
        statusCheckUrl: http://internal.example.com/

Priority
Low (Nice-to-have)
Is this something you would be keen to implement
No response

Heya @Tinyblargon - Is this something you're up for implementing?

If there's user demand for it, I can implement this.
So if anyone's interested, feel free to comment to reopen...
In the meantime, OP if you just want to hide status check info, you can do this with CSS. But ofc, the full info will still be accessible via the dev tools, networking tab.


Same file processed multiple times

I recently saw someone manage to setup their .djinni files and @imports in such a way that the same file was imported multiple times and threw errors about redefined types. Unfortunately the file setup is no longer available to me but it seemed to be caused by a series of .. entries in the @imports as files were referencing each other. The resulting error message contained many entries in the form of ../dir/../ etc.
I haven't found a reproducible setup yet but I assume it happens in the parser as the File instances do not store canonical paths to files for the duplication check. If anyone runs into such an error with their setup it'd be good to see it so I can check this assumption.

Fixed in #273


New Jira command: Assigned Issues

Description
A new command for the Jira extension which shows all assigned issues that are not done and not cancelled.
Screencast

The view is the same as any other jira list view:

Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

Thanks for the PR. It seems this command is very similar to what Open Issues is doing. Maybe we could rename that one to Assigned Issues instead?

Thanks for the PR. It seems this command is very similar to what Open Issues is doing. Maybe we could rename that one to Assigned Issues instead?

Thanks for the review and you are actually right, I do not know how I missed the "Open Issues" command.
In that sense this request is a duplicate and I will close it and switch to the existing "Open Issues" command instead. Sorry for the trouble.

No worries!


Mount bind volumes coming from the old volumes configuration.

Signed-off-by: David Calavera<EMAIL_ADDRESS>

LGTM

LGTM

@jfrazelle This one should be cherry-picked as well.

cherry-picked


给个网址2022好人有好报贴吧无法打开

关于给个网址2022好人有好报贴吧无法打开
>>>>>>点/此/进/入/最/新/观/看/入/口<<<<<<
啰不过父亲还是夸山娃能临危不乱随机应变有胆有谋山娃笑笑说那都是书上学的看童话和小说时学的不管如何父亲再也不许这

你可以将给个网址2022好人有好报贴吧无法打开　　一会儿，大哥抱了父亲的骨灰出来——红色的布匹，小小的布匹，怎么能够盛放我高大的父亲呢？而我的父亲只剩下这一掊骨灰。下车之后，我接过来抱着，骨灰还在烫热，我把父亲贴在心口，和他说话：我们回家了，爸。再走一次尘世的路。这一次我抱你。

给一个网站2022应该得到良好的贴吧打不开
I was almost with CaoBiao bought this house on the head.
Within this one or two years at least, I can never leave home to watch it, like the birds warm own nest and hatch their eggs, deep as a philosopher in the temple with an eagle can only lead to some kind of word.
To buy a house is in order to test their psychology to bear ability, with room after all is the root.
I stand on the balcony, on the left you can see the sunrise, the right to see sunset glow, the front and a rolling history through the water, much rain recently, it has some signs of the flood.
Here is located in the south of the city, the past chueiyang passageway, streams and polyphenolic canal irrigation.
Now I am standing in 25 meters high from the ground, the aoyama faint water all the way.
Mountain is the mountain, du fu had her long on the moon, there in its opposite, I want her to the house.
I really need to the house to marry my bride, write my essay, my day, indeed.

请参考下方链接：
https://github.com/powercvt/ogu-ogute/issues/new
https://github.com/bingkangr/5316453/issues/1
https://github.com/fowerv/wlagtd
https://github.com/tooere/fjejm
https://github.com/powercvt/zgdtf/issues/3
https://github.com/tooere/nobclh/issues/6
https://github.com/fowerv/ihtueb/blob/main/README.md
https://github.com/powercvt/rwe-rwehx/issues/new
https://github.com/powercvt/mfwzqgz/issues/6
https://github.com/goodiders/huzlj/issues/3
https://github.com/powercvt/dmlcm/issues/5
https://github.com/powercvt/mst-mstwm/issues
https://github.com/powercvt/ncruxf/issues/4
https://github.com/tuderw/cqe-cqemh
https://github.com/tuderw/ttror/issues/2
https://github.com/fowerv/tgtrw/blob/main/README.md
https://github.com/dedesew/zoael/issues/3
https://github.com/tuderw/kxt-kxtge
https://github.com/makedete/ejrjwb/issues/2
https://github.com/makedete/awjiuvt/blob/main/README.md


The removeLastPoint function in the official example is not functioning correctly.

Describe the bug
The removeLastPoint function in the official example does not work properly; in fact, it does not work at all.
I'm unsure if I'm misunderstanding its functionality or if it's a bug.
To Reproduce
Steps to reproduce the behavior:

Go to https://openlayers.org/en/latest/examples/draw-features.html
Add two polygons, some points, and line strings to the map
Click on the Undo button
It does not have any effect

Expected behavior
I expect the Undo button to remove the last item I added to the map, particularly polygons and multi-polygons.

Your expectation is wrong: the removeLastPoint() function removes the previously drawn vertex of a LineString or Polygon geometry. Could we document it better to make that clearer?

Thank you for your response. It seems I misunderstood the situation.
Yes, I believe it would be beneficial to document it with a more explicit description.
I intend to close this issue, but before doing so, is there an alternative method to undo the entire polygon?

Register a listener to the drawend event, and store the event object's feature for deletion:
let lastDrawnFeature;
drawInteraction.on('drawend', e => {
  lastDrawnFeature = e.feature;
});

function deleteLastFeature() {
  if (!lastDrawnFeature) {
    return;
  }
  vectorSource.removeFeature(lastDrawnFeature);
}

Thank you very much.


splitChunks : none of the options is self-explanatory and documentation is cryptic

I know this ticket might not conform with the issue creation policy but I will try to compile a list of questions here hoping that they can be addressed (I am willing to make PRs to improve the documentation)
1. optimization.runtimeChunk
I guess this makes sense if you have more than one entry points.  In any other case, the appropriate value should be 'false' , correct?
2. optimization.occurrenceOrder
Does this option still exist? (not found in documentation using search)
3. optimization.namedChunks
Same as above.
4. maxInitialRequests
I had cases when a cacheGroup was not generating a file until I increased the default maxInitialRequests value to something like "10". I have no idea why that is.
(and most importantly)
5. test
I am migrating a setup with which we were using simple strings to target individual node_modules which we wanted in a separate generated file to split the end result of vendors in smaller files. Some of the test rules don't seem to be doing what I think they should - is there a way to debug this? Can I just use a simple string like "moment.js" or should I target the parent directory using a regexp : /[\\/]moment[\\/]/.
6. chunks
The documentation of the options "initial", "async" and "all" is just a repetition of the option word itself. Desperately looking for a tangible example.

@webpack-bot move to webpack/webpack.js.org

How do I remove this so I can see my messages


about counting

Hi, author, if image caption is about counting , e.g. There are four birds in the sky.
How to generate counterfactual image，Change all birds to other animals？

The method that we used in COCO-Counterfactuals was to simply edit a single word in the caption. For example, you could change the caption "There are four birds in the sky" to "There are four animals in the sky". Does this answer your question?


Use knative-serving namespace instead of kourier-system

Kourier components are being deployed into "kourier-system" namespace, we should reuse the "knative-serving" namespace instead.

closed by https://github.com/knative-sandbox/net-kourier/pull/151


scion-pki: Generate Certificate for the future

It should be possible to generate a certificate with an IssuingTime that lies in the future.

New scrypto and scion-pki tool support this


Building Footprints Link Changing

The download link for the building footprints data set provided by DoITT through NYC Open Data has been changing. The part of the link (which we call the id) is highlighted in the image below. The changes are currently breaking our current data pipeline, requiring manual updates. Is there a point of contact, or a reason for these changes? Thanks!

Hi Richard,
Thanks for reaching out. Unfortunately, this is a known bug with the Socrata tool (3rd party tool serving APIs in Open Data). We are currently working with them to resolve the issue. I'll report here if there is an update.

Thanks @ekamptner - I'll stand by/see if we can build a workaround

My understanding is that this issue with NYC Open Dataset 4x4s changing has been resolved.


[BUG] Dependabot PRs are duplicating GitHub Action checks

What is the bug?
Workflow checks are being duplicated on dependabot PRs.
How can one reproduce the bug?
Get a PR from dependabot.

What is the expected behavior?
See other PRs.

We need to add a branches-ignore section for push on our workflows.  See here for example.


Beginning of Collections documentation

Just getting started here; will continue with additional information.

Looks good so far. Please add some guideline on how to make a deploy script using collections. I'd like to see something like Capistrano to be there )

It might be time-consuming to get into real-world examples at this point. In the short term, I am just going to document the capabilities of Collections here using "hypothetical" tasks. As I evolve real-world Collections use in other projects, though, I could come back here and flesh out the examples with actual tasks used elsewhere, so the documentation can improve and evolve incrementally. Help in this area would be appreciated.

I'm going out of town for a few days; I think this has reached a Minimum Viable Document state for collections. If you don't find any errors or critical omissions, please merge this in and republish the documentation. We can continue towards more functional examples as time goes along.

Okay, I'll try to come up with a very simple real-world example for the basic collection example, and clarify the use of the Temporary global collection.

Documentation should focus not on theoretical aspects of Collections but on real purpose. So it should starts with scenarios where you will need them for sure. As I said it is deployment in capistrano style:

connect by ssh
git clone
perform migrations
symlink folders

Probably we should concentrate on this case, if you don't see other good examples. But Robo can be used for deployment and we should extend docs by providing users with the way on how to do it. So this chapter should not be just about collections its about using them in this scenario, however, unlike capistrano highly customizable.

I definitely agree with ^^ in concept; I was just planning on implementing things of that nature as I needed them in external projects first, and then circle back to update the documentation.  Maybe I'll try converting Robo's own RoboFile to use collections where applicable, and see if that leads anywhere, example-wise.

Made some minor changes; still a work-in-progress.

@DavertMik: Better?

Rebased with master. Still need a real example using temporary directories.

Merging per yesterday's chat.  Will return later to enhance temporary directory example.


Replace spinAsserts code with Awaitility code

patch by Jogesh Anand,  Andres de la Peña, Berenguer Blasi; reviewed by Andres de la Peña, Berenguer Blasi for CASSANDRA-16621
Co-authored-by:  Jogesh Anand<EMAIL_ADDRESS>Co-authored-by: Andres de la Peña<EMAIL_ADDRESS>Co-authored-by: Berenguer Blasi<EMAIL_ADDRESS>

CI lgtm

Rebased:

CI j11
CI j8


Multiple guides

[x] add selection
[x] https://scrumguides.org/download.html
[x] https://kanbanguides.org/english/
[ ] https://less.works/less/framework/introduction
- License need to be checked
[x] https://www.scrum.org/resources/nexus-guide

skip less for now


Merge remote-tracking branch 'origin/master' into master-next

@swift-ci please test

Build failed
Swift Test Linux Platform
Git Sha - b3d321bb1f08641161c888bd82893a49202193df

Build failed
Swift Test OS X Platform
Git Sha - b3d321bb1f08641161c888bd82893a49202193df

Same failures on macOS as before, xfail'd by https://github.com/apple/swift/pull/30400


TS-5022: Allow multiple client cert for ATS

Allow ATS to choose the certificate to use while making ssl connection with an origin server. Remap plugin can set "proxy.config.ssl.client.cert.path" and "proxy.config.ssl.client.cert.filename" which are overridable configs now. This code has been tested with microserver

[approve ci]

I chatted with Persia about cleanly dealing with the config reload case.

FreeBSD build failed! See https://ci.trafficserver.apache.org/job/Github-FreeBSD/1206/ for details.

Linux build successful! See https://ci.trafficserver.apache.org/job/Github-Linux/1099/ for details.

Please review @shinrich @SolidWallOfCode

[approve ci]

FreeBSD build successful! See https://ci.trafficserver.apache.org/job/Github-FreeBSD/1222/ for details.

Linux build successful! See https://ci.trafficserver.apache.org/job/Github-Linux/1115/ for details.

I think there still needs to be some locking around the CtxMap to safely reload.

Please review @shinrich

@shinrich  Lock problem has been fixed. Please review again. Checking for nullptr is unnecessary since we are allowing nullptr to be key.

Linux build successful! See https://ci.trafficserver.apache.org/job/Github-Linux/1187/ for details.

Please review @shinrich . The map containing client ctxs have been moved to sslconfig

FreeBSD build successful! See https://ci.trafficserver.apache.org/job/Github-FreeBSD/1303/ for details.

Linux build successful! See https://ci.trafficserver.apache.org/job/Github-Linux/1197/ for details.

FreeBSD build successful! See https://ci.trafficserver.apache.org/job/Github-FreeBSD/1304/ for details.

Linux build successful! See https://ci.trafficserver.apache.org/job/Github-Linux/1198/ for details.

Please review @shinrich. The client context initialization and creation parts have been moved to SSLConfig

FreeBSD build successful! See https://ci.trafficserver.apache.org/job/Github-FreeBSD/1306/ for details.

Linux build successful! See https://ci.trafficserver.apache.org/job/Github-Linux/1200/ for details.

FreeBSD build successful! See https://ci.trafficserver.apache.org/job/Github-FreeBSD/1307/ for details.

Linux build successful! See https://ci.trafficserver.apache.org/job/Github-Linux/1201/ for details.

Looks Good!


Bug in bin2llvmir Decoder

Deocde the following ELF file:
elf-Linux-x64-bash.zip
We get a strange function:
declare i64 @__strtol_internal()
...
define i64 @function_ffffffffffff94e5() {
dec_label_pc_ffffffffffff94e5:
  ret i64 undef
}

The problem is, if the jump target is IMPORT Type, we shouldn't decode it, if the data accidently be meaningful code, We may get the following result:
        define void @__strtol_internal() {
        block_6d94a0:
          store volatile i64 7181472, i64* @assembly_address
          call void @__pseudo_branch(i64 -27419)
          call void @function_ffffffffffff94e5()
          ret void
        }

The data in 0x6d94a0 is (IDA view):
.got.plt:00000000006D94A0 off_6D94A0      dq offset __strtol_internal

Although __strtol_internal will become declaration by the end of Decode phase, the wrong function function_ffffffffffff94e5 will remaining:
declare i64 @__strtol_internal()
...
define i64 @function_ffffffffffff94e5() {
dec_label_pc_ffffffffffff94e5:
  ret i64 undef
}

It can be solved by add the following code to Decoder::decodeJumpTarget(JumpTarget &jt), after line 189:
void Decoder::decodeJumpTarget(const JumpTarget& jt)
{
	const Address start = jt.getAddress();
	if (start.isUndefined())
	{
		LOG << "\t\t" << "unknown target address -> skip" << std::endl;
		return;
	}

+        if (jt.getFromAddress().isUndefined() && jt.getType() == JumpTarget::eType::IMPORT)
+       {
+              return;
+       }

And everything will be fine.

Hi, I tried to decompile the file you have provided and with your fix I've managed to get the same results.
In this case, RetDec decompiles functions that should not be included in the output after the decoder phase. Those functions are eliminated during decompilation but few artifacts stay present.
Here is a diff of LLVM code after decoding phase (before and after the patch):
diff.txt
I've run regression tests and all passed. I think that you can open a pull request.

Thanks for the report, this is an issue that should be fixed. I will look into your solution in #642 and decide if it is enough, or we should do some more things. This might require a more robust solution.

Solved by #642.


Fix check-api-changes

Fix a duplicated call to target.

Codecov Report
Base: 73.33% // Head: 73.33% // No change to project coverage :thumbsup:

Coverage data is based on head (8895d42) compared to base (72977f5).
 Consider uploading reports for the commit 48e3c4d to get more accurate results

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #172   +/-   ##
=======================================
  Coverage   73.33%   73.33%
=======================================
  Files          25       25
  Lines        2438     2438
=======================================
  Hits         1788     1788
  Misses        564      564
  Partials       86       86

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

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

/cc @ybettan

/ok-to-test
/lgtm
/assign @ybettan

/approve


[engine] malioc diff should label the components in the shortest/longest cycle output and include stack spilling

I believe these will each correspond to arithmetic, load/store, texture, et cetera components. We should labels these and print which one is the bottleneck. In general, we may wish change shaders such that we increase the usage of a component which is a bottleneck in exchange for decreasing the usage of a component that is bottlencked.
For example, I uses the text output which contains these labels:
- Work registers: 4 (100% used at 100% occupancy)
+ Work registers: 3 (75% used at 100% occupancy)
- Uniform registers: 2 (10% used)
+ Uniform registers: 2 (9% used)
Stack spilling: false

                                A      LS       T    Bound
- Total instruction cycles:   22.67    2.00    2.00        A
+ Total instruction cycles:    5.00    2.00    2.00        A
- Shortest path cycles:        4.62    2.00    0.00        A
+ Shortest path cycles:        2.97    2.00    1.00        A
Longest path cycles:          N/A     N/A     N/A      N/A

See https://github.com/flutter/engine/pull/37927

@zanderso


Remove the requirement of using nightly

It is not necessary to use a nightly toolchain for the crates in this repository.

Looks like you would need to drop the Zprofile arg for code coverage if you wanted that to use stable also?

If this arg cannot be used with stable, we could instead keep using nightly for the code coverage action.


Define budget schedule to allow node disruptions

Description
What problem are you trying to solve?
We need to set a schedule where disruption may occur, and set a maximum number of disruptions during that schedule. For instance, in my cluster with 15+ Karpenter managed nodes, I wish I could allow that only a single node per day may be disrupted (I know this would not be the most cost-effective/efficient solution but would be fine with that).
To my knowledge, the current disruption budget allows us to set up a schedule where zero disruptions occur during a given schedule/duration. A workaround that we did to kind of implement our view, was to set the budget as follows:
     budgets:
    - nodes: "10%"
    - nodes: "1"
    - nodes: "0"
      schedule: "@daily"
      duration: 1439m # 23h59m

Effectively, per day there's only 1 minute allowed for disruptions, during that minute only one instance is usually disrupted (2 if the first one was fast enough to instantiate and join in under a minute). Of course the downside of this workaround is that that minute will always be between 23h59 and 00h00, which may not be ideal.
It would be nice to have a configuration available that would allow us to do this without the mentioned workaround. (If there already is and I missed it please forgive me).
How important is this feature to you?
This feature is important to avoid successive instance disruptions, we already have configured that a maximum of one instance may be disrupted during the disruption phase, however if we have 10 nodes already "expired" they will all be recycled one by one consecutively. What we would find useful here would be the ability to for example limit daily disruptions to a configurable number of nodes, ie. 1 per day.

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

This feature is important to avoid successive instance disruptions, we already have configured that a maximum of one instance may be disrupted during the disruption phase

@ccortinhas-pmi  Can you give more detail around why you are looking to only disrupt a single instance in a given day? What's the impact to your applications when you have multiple instances disruption consecutively?

Hello @jonathan-innis , that was just an example, one in a day, one in an hour, it doesn't even have to be one, just a configurable number (or even percentage even though we would use number).
The impact of several instances disrupting consecutively is a potential degradation of some of the services. When a new instance joins the cluster, it still has to download all the containers of the pods that it is going to hold so its services will not be available immediately. While this is happening, another instance is being disrupted and will evict another set of pods (potentially to instances that will expire next) and the cycle continues.
Additionally, and this is unrelated to Karpenter I know, we must use a container registry that throttles the number of requests, we easily hit that limit when disrupting 2 to 3 big instances (each with dozens of deployments) in a row so we would like to be sure to avoid this.
Another thing that would work for us, would be if there was a setting where we could configure a minimum time between disruptions. Is there?

While this is happening, another instance is being disrupted and will evict another set of pods

Do PDBs help with this at all? It sounds like you are primarily concerned with the number of instances that we deprovision in parallel and less concerned with the total number of instances that are deprovisioned within a given time window.

we must use a container registry that throttles the number of requests, we easily hit that limit when disrupting 2 to 3 big instances (each with dozens of deployments) in a row so we would like to be sure to avoid this

This is interesting and I hadn't heard this before. Is this the Docker upstream registry or something else?

While this is happening, another instance is being disrupted and will evict another set of pods (potentially to instances that will expire next) and the cycle continues

To your point about another instance getting disrupted, doesn't your budget stop this or are the images pulling in the background and the Node still Ready? Do you mean that the Node pulls images as part of its boot-up or do you mean the CRI is pulling these images as part of the pod/container start-up?

do you mean the CRI is pulling these images as part of the pod/container start-up?

Yes, I mean this, as part of the applications start-up, each application/pod will download at least three container images. Nonetheless, the node after it joins the cluster also pulls some Anypoint container images that are related to the Runtime Fabric service.

/remove-lifecycle stale


[WIP] chore(linting): run a combined eslint, prettier, organize-imports pass

WIP: Let's wait to review this until after the demo
Previously we've run with automatic fix commands with eslint then prettier. Now that we've combined them and their rules, so we need to run it again to avoid constantly shifting files on save.
This will hopefully help with the few remaining changes that happen on save, and this is probably a good time to do it before the git conflicts flare up.
Also VSCode's organize-imports on save action conflicts with the way ESLint does it, causing it to slightly shift on save even after we run eslint (like in App.tsx). Ive disabled that VSCode action and replaced it with eslint-plugin-simple-import-sort which allows an easy --fix on files.
Also also, disables running prettier by itself in lint-staged as part of the git hook, since that causes conflicts with eslint when run by itself.
I've left stylelint for CSS alone for now. I've also not changed the import order of imports of .css/.less files, since rarely that import order might matter. I don't really want to change any of those until we set up a visual diff tool in cypress so I don't have to check everything to make sure nothing changed.
This will make PRs easier to parse without a bunch of diff lines unrelated to the PR change. I feel like we're going to want to go through the eslint rule pile when we open up the new repo for the filing app, but this is a good start.
Changes

yarn run-eslint (which now also runs prettier)

How to test this PR

Go to main on a file with linting errors that would be automatically fixed on saved like src/api/fetchInstitutions.ts.

Compare with main

Screenshots
Before

After

Notes

If you change an eslint rule in the future (we definitely will), please re-run yarn run-eslint

Closing this and putting in the backlog.


Improve EDB operator deployment and cluster creation

The EDB operator needs to be deployed along side with the other subscriptions and
also the cluster can create the pgvector extension when is created so there's no need
for an extra job to create the extension.

reviewed with @sauagarwa


Slow loading in firefox.

I have been having slow load times in fire fox since I started using slick. It's happening in IE but not too concerned about IE. Chrome works fine and loads all the images pretty quick.
I've updated to 1.9 and JQuery 3.1.1, using lazyload. The slider is only initialized on page load.
It seems to stem from from loadSlide.
It looks like it is recalculating every on every image, I am loading about 1000 images on the page, but its even slow for smaller numbers. It's even slow if I just include an empty image tag.
I've setup slickFilters and whenever I filter the images it causes the same issue. If for example I load all images then filter, since all the images are already loaded it runs fast, but if I filter again it slows down again.
I'm not sure if its something wrong with slick, my code or Firefox since it works fine. Is anyone else having similar issues or have any ideas?
Thanks in advance!

happens on init
$('.slider').not('.slick-initialized').slick()
and
$('.slider').slick('slickUnfilter');

looks like calling
(slider).hide();
(slider).show();
around the offending functions fixes the issue.

+1...Slow loading in React Native WebView

Hi did you solve the issue ?

Hi did you solve the issue ?


Create a script to detect protected PDFs in batches

Create a script to detect protected PDFs in batches

I created it yesterday, just need to polish it and do a PR

Waiting for PR review


Possibility of delta updates

Is it possible to provide the *.zsync file to ease updates? I am not familiar with pkg2appimage

It can for Travis CI but not yet for GitHub Actions.
One would have to add to appimagetool https://github.com/AppImage/AppImageKit/blob/bc5a03a0e59651bb39018f77e378c44a4cba7a5e/src/appimagetool.c#L876-L905 for GitHub Actions in addition to Travis CI.
Like I did in go-appimage here:
https://github.com/probonopd/go-appimage/blob/7fab45552eb485c0076fd310835fa7958f981de0/src/appimagetool/appimagetool.go#L547-L567
Do you want to try adding this to appimagetool?

Alternatively, one could make pkg2appimage use go-appimage's appimagetool...

In my "workaround"-ish brain, I would have unpacked the Zoom AppImage generated using pkg2appimage and then repack it using appimagetool with --updateinformation flag to point to the continuous release. Would that be okay? If it would be, I can create a PR.

appimagetool -g is supposed to do this, since manually passing --updateinformation has proven to be too error-prone for many people to get it right.

hmm. but I prefer doing everything manually. Thanks for the info about the -g flag. I will try my luck at adding Github Actions support on https://github.com/AppImage/AppImageKit/blob/bc5a03a0e59651bb39018f77e378c44a4cba7a5e/src/appimagetool.c#L876-L905

I prefer doing everything manually.

You are probably one of the few people who are willing to spend enough time to actually understand what an update information string is... ;)

@probonopd in case you missed it, https://github.com/AppImage/AppImageKit/pull/1075 aims at adding GH Actions support to the appimagetool

Excellent @srevinsaju. Let's use it here once it's merged there.

Great. Thanks :D


Still can't get custom CSS to work on Dropbox

I put a custom CSS file in Dropbox which is in my Stackedit folder, and the file is 'markdown.css'.
In Stackedit I went to Menu, Settings, Advanced, and I put this in the default template (partial html):
<title><%= documentTitle %></title>
<link rel="stylesheet" href="https://stackedit.io/res-min/themes/base.css" />
<style>
h1, h2, h3, h4, h5 {margin-top: 5px;
margin: 5pt 0 5pt 0;
padding: 0;
}
h1 {font-height: 130%;
}
h2 {font-height: 110%;
}
</style>

I also tried this in the default template which didn't work (partial html):
<title><%= documentTitle %></title>
<link rel="stylesheet" href="https://stackedit.io/res-min/themes/base.css" />
<link rel="stylesheet" href="https://www.dropbox.com/s/oypb46pyzom30v0/markdown.css?dl=0" />

When I use Firefox Inspector on the preview pane on the right the CSS attributes are coming from base.css.
How do I get the custom CSS?

Doesn't look like a bug. Probably the file https://www.dropbox.com/s/oypb46pyzom30v0/markdown.css?dl=0 is not served as a raw text/css content.


hubble/recorder: Refactor service implementation to fix multiple races

This PR fixes multiple concurrency issues in the implementation of the
Hubble Recorder API. The main one being that we were sending responses
to the client from both the main Record function, as well as the
watchRecording function which was spawned in a separate go routine.
However, sending to a grpc.ServerStream from multiple go routines is
not safe: https://pkg.go.dev/google.golang.org/grpc#ServerStream
It is however safe to have one go routine receive from, and another go routine
send to the stream.
Therefore, this commit restructures the Hubble Recorder API in such a
way that only the Record stub ever sends back messages to the client.
Receiving is done in a separate go routine which forwards all received
messages into a channel, allowing us to select on incoming responses.
In addition, this commit hopefully also makes the logic a bit more
easier to read, as it tries to separate the cleanup of resources and
communicating with the client a bit more explicitly. It also drastically
simplifies the implementation of a follow-up PR which extends the
API with stop conditions (#16473).
I apologize for the size, but I had to restructure quite a bit to fix
the underlying issue. I highly recommended to review per commit.

test-me-please

lgtm. would be good to get another review on https://github.com/cilium/cilium/pull/16472/commits/07e4f36c6e4c12726cb6c987ad60fcca9609823f

Thanks @michi-covalent! I know this is not a very nice change to review. I'm also happy to walk through the changes via Zoom with someone if interested.

Converting back into draft. The code review via Zoom revealed we don't have to drain the queue anymore when stopping.

As discussed offline, I pushed a new commit (5d512ba179bd4d1286fc87c527a78a3353bf0d7c, second one in the history) which replaces two previous commits around the handling of s.queue

test-me-please

@tklauser I addressed your feedback (and them some) in a separate commit 08ff4b1f227e44fb5be0d5a0e7c9feb69706fcb8

test-me-please

test-1.16-netnext

test-1.19-5.4

test-1.21-4.9

test-1.19-5.4

test-1.19-5.4

CI 3.0 failed last week with cilium/cilium-cli#333 - we have since bumped CI 3.0 to CLI 0.8.1. Rebasing on master to pull in fixed CI.

test-me-please

test-runtime

test-1.21-4.9

test-1.21-4.9

Need to rebase yet again to pull in https://github.com/cilium/cilium/pull/16646/

test-me-please

test-me-please

I'm marking this ready-to-merge. Reasoning: This is fixing a bug in a released Cilium version and thus should be exempt from the zero-flake policy. It's almost 2 months old at this point and has hit various Jenkins flakes over its lifetime, but always different ones and all looked unrelated to this PR, as the pcap recorder (which this PR is touching) is not enabled in neither Jenkins CI nor our conformance tests.


Commenting broke !

Hey i am unable to comment

I've only been able to reproduce this once, and it was a bug with kick. Kick returned a 200/success payload and code but the message wasn't sent.


Optimizing planners and tracking progress

Hello,
Is there a way to track optimizing planners' progress? I see that intermediate solutions are stored. Are improvements to existing solutions considered intermediate solutions? If the OMPL callback is used, I guess this should be the case, but I just wanted to check anyway.
In the OMPL benchmark, there is a way to record the cost of the current solution every t seconds. I guess this is useful for plotting. Do you also have a way to plot the costs of the intermediate solutions?
I don't think I saw anything related to this in the documentation or the tutorials. If it's already implemented, please point me to the relevant files and I can contribute the tutorial / documentation. :-)

Hi,
The intermediary solutions are recorded via the OMPL callback here:
https://github.com/robot-motion/bench-mr/blob/master/src/planners/OMPLPlanner.hpp#L67-L78
These intermediary paths are evaluated here and recorded in the results JSON file:
https://github.com/robot-motion/bench-mr/blob/master/src/utils/PathEvaluation.hpp#L223-L231
I don't think we have yet added any example notebook using these intermediary solutions. But here is some front-end code that shows how to plot those intermediary paths:
https://github.com/robot-motion/bench-mr/blob/37d93a1ad5b86874715fced995451966ebf2f3f6/python/plot_trajectory_convergence.py#L112-L116
You should be able to extract the cost and other metrics from the stats entry of each intermediary solution (they are stored via the PathEvaluation.hpp code from above).
Let us know if you need further help. We would definitely appreciate contributions to the tutorials/documentation! 🙂

I will try this.
This means it's no longer an issue. :-)


Initial docs commit

Initial run of PlatyPS to create markdown doc files for 3.0.0-beta8
@SydneyhSmith @alerickson - Please merge this PR then fill in the missing information in these doc files. We can work on the docs in this repo until we are ready to publish a live version.

Closing - wrong repo


mdl-select value can be json object.

mdl-select was only accept number and string value. Now it accepts object value so multiple selectable FormControl returns array of objects without any transformation.

Coverage decreased (-1.03%) to 92.627% when pulling 6999acace72dc3c6d4e3407267b90c3e713b929f on canyaman:master into f52f95e6e83f412f7948b89d571c502be07f0bf1 on mseemann:master.

@canyaman This looks great! Please add test for it. Current test dont test the object case, see https://coveralls.io/builds/9148410/source?filename=src%2Fcomponents%2Fselect%2Foption.ts#L52

Coverage decreased (-0.1%) to 93.548% when pulling c2f883cc7ef7062696935fb6b71d57016fd22a63 on canyaman:master into f52f95e6e83f412f7948b89d571c502be07f0bf1 on mseemann:master.

@tb I have added test cases. It should be passed. Coverage decreased because of the merge ,most probably. Can you re-run the code coverage tool?

It was re-run. It still -0.1% but I think its fine

looks great! going to publish this as version 0.7.0 of @angular2-mdl-ext/select...


Files are closed when switching branches ("workbench.editor.closeOnFileDelete" seems not to work?)

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.57.0
OS Version: Ubuntu Linux 20.04.2

Steps to Reproduce:

Make sure "workbench.editor.closeOnFileDelete": false is in settings.json, restart VSCode if necessary
Open a project in VSCode
Create a new git branch in the project
Create several new files in VSCode on the branch, and commit them to git
Switch to the previous git branch (or any other branch where the files are missing)
Observe that VSCode closes some or all of the editors.

Screenshots of the problem:

From step 4 above, when several files are open that exist only on the branch:

From step 6 above, when switching to the previous branch (where the files do not exist), all editors of the deleted files except one are closed:

Anyone?

This issue still happens with latest VSCode. I had 10 editor windows open, switched from feature branch to master branch (where the open source files do not exist), started a build, switched back to the feature branch, and only one of the ten editor windows remained open. It's even arbitrary that one editor remained open, because all ten files do not exist in master.
So there is an inconsistent closing of editors when switching branches. I do not know if this is further related to building the code with cmake tools or manually opening and closing additional editor windows. But I can say that it would be nice if there was a consistent behavior that editors remain open even when the files are gone, and remain open when the files appear again.

This issue is now over one year old and super annoying. I have 30 editor windows open, did a git interactive rebase, and now there are only 5 editor windows open. Please kindly consider this issue again!

Upvoting!

Apologies for not getting back to you on this until now. I have used the repro steps above, but I was not able to reproduce the issue with the latest VS Code Insiders release (1.75). Maybe I have missed something, but I was wondering Is anyone still able to reproduce this issue? Thank you!

Dear @lszomoru , thanks for the follow-up. I'm admittedly a bit unhappy that this issue has not received more consideration. It is quite a severe problem for me. You do not mention how exactly you tried to reproduce. For me, then problem happens very frequently on interactive rebase (in case the older commits feature different files) or when switching branches (in case the branches feature different files).
In my experience the best way to reproduce is actually interactive rebase.
Here is a demo video that demonstrates the problem: https://youtu.be/35sf7QHsODA I use the project https://github.com/swig/swig to perform an interactive rebase. As you can see, I open some 10 files that where recently added in the swig project. Then I do interactive rebase to edit the commit 4a8f7a9c4. When the rebase starts, it rewinds to commit 4a8f7a9c4, and immediately, VSCode closes most of the open files! The files are later not opened again, even when the rebase aborts.

An editor that was not opened in a session will close because there is nothing to show since the buffer was not loaded yet. In other words:

a tab that was clicked once can stay open because the buffer is in memory
a tab that was not clicked will close

We can maybe revisit that decision and show a generic error in the tab.

An editor that was not opened in a session will close because there is nothing to show since the buffer was not loaded yet.

Oh, I was not aware of this. I can see how this has the benefit of improved performance of VSCode. But I understand it also has the downside that users (I, for one) may falsely trust that a file is open in VSCode and can be recovered from there. Is that actually worthwhile?

This bug has been fixed in the latest release of VS Code Insiders!
@emmenlau, you can help us out by commenting /verified if things are now working as expected.
If things still don't seem right, please ensure you're on version edc432e920c3ec2c2af5e8a99b8e4b782633d298 of Insiders (today's or later - you can use Help: About in the command palette to check), and leave a comment letting us know what isn't working as expected.
Happy Coding!


Small fix for nightly rust

this has been fixed and should be available in tomorrows nightly. The commit can then be reverted.


[AIRFLOW-4765] Fix DataProcPigOperator execute method

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@68e8c99). Click here to learn what that means.
The diff coverage is 100%.

@@            Coverage Diff            @@
##             master      #89   +/-   ##
=========================================
  Coverage          ?   79.05%
=========================================
  Files             ?      481
  Lines             ?    30197
  Branches          ?        0
=========================================
  Hits              ?    23872
  Misses            ?     6325
  Partials          ?        0

Impacted Files
Coverage Δ

airflow/contrib/operators/dataproc_operator.py
86.41% <100%> (ø)

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 68e8c99...2434fd0. Read the comment docs.

Should we merge also this one?

Sure! Just open it against Apache repo :)

Done, here is the PR:
https://github.com/apache/airflow/pull/5426


Inconsistency for returned value type of maybe_equals()

Originally reported by @JoelPasvolsky
Depending on whether it's tested on another symbol or on itself, maybe_equals() returns Boolean or integer:
>>> model = Model()
>>> i = model.integer(100, lower_bound=0, upper_bound=20)
>>> j = model.integer(3, lower_bound=-10, upper_bound=10)
>>> j.maybe_equals(j)
True
>>> j.maybe_equals(i)
0

This should always return a number. Specifically 0 if not equal, 1 if possibly equal, and 2 if definitely equal.


Update calculation of text position for InitialsAvatar.

Imagick got it wrong. ... No need for merging.


[BUG] Failed to launch the browser process on AWS Lambda

Environment

chromium Version: 113.0.1
puppeteer / puppeteer-core Version: 20.2.0
Node.js Version:  16
Lambda / GCF Runtime:  16

  "dependencies": {
    "@sparticuz/chromium": "^113.0.1",
    "aws-sdk": "^2.1163.0",
    "puppeteer-core": "^20.2.0"
  }

Lambda with 2000MB memory
Expected Behavior
Executed my tests on AWS Lambda with success.
Current Behavior
Failed to execute my test with empty json.
{
  "errorType": "Error",
  "errorMessage": "Failed to launch the browser process!\n\n\nTROUBLESHOOTING: https://pptr.dev/troubleshooting\n",
  "trace": [
    "Error: Failed to launch the browser process!",
    "",
    "",
    "TROUBLESHOOTING: https://pptr.dev/troubleshooting",
    "",
    "    at Interface.onClose (/var/task/node_modules/@puppeteer/browsers/lib/cjs/launch.js:262:24)",
    "    at Interface.emit (node:events:525:35)",
    "    at Interface.emit (node:domain:489:12)",
    "    at Interface.close (node:readline:590:8)",
    "    at Socket.onend (node:readline:280:10)",
    "    at Socket.emit (node:events:525:35)",
    "    at Socket.emit (node:domain:489:12)",
    "    at endReadableNT (node:internal/streams/readable:1358:12)",
    "    at processTicksAndRejections (node:internal/process/task_queues:83:21)"
  ]
}

Steps to Reproduce
import chromium from '@sparticuz/chromium';
import aws from 'aws-sdk';
import puppeteer from 'puppeteer-core';

const lambda = new aws.Lambda();

export async function handler(event) {

    await run();

    await lambda.updateFunctionConfiguration({
        FunctionName: 'puppeteer-on-lambda',
        Environment: {
            Variables: {}
        }
    }).promise();

    const response = {
        statusCode: 200,
        body: ''
    };

    return response;
}

export async function run() {
    const browser = await puppeteer.launch({
        args: chromium.args,
        defaultViewport: chromium.defaultViewport,
        executablePath: await chromium.executablePath(),
        ignoreHTTPSErrors: true,
    });

    const page = await browser.newPage();

    await page.goto('https://lumtest.com/myip.json');
    const body = await page.$eval('body', element => element.textContent);

    console.log('body', body);

    await browser.close();
}````

Did you ever figure this out @r1tt3r ? I am facing the same problem.


[ceilometer] Add support for ObjectRocket

We should test and provide a supported solution for using ObjectRocket with RPC as the underpinning database for Ceilometer.

Per Jesse, this is more a feature request for a future version (12.x-ish).

This will end up being a work card, with a new issue, if you close this.

As @stevelle said, this is of interest for the Liberty release, at least in terms of a spike.

The is a spike in-progress/finished regarding the appropriate way to deploy Ceilometer and so I believe this issue is no longer valid.


Fixes issue #6413 - Minor documentation fix in the entropy function for Dirichlet distributions

Attempting to close #6413.

Thanks @bhavikat, merged.

Happy to help, @ev-br :+1:


add unit test for function (#746)

What this PR does:
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

Codecov Report
Patch coverage: 83.33% and project coverage change: +0.51% :tada:

Comparison is base (304e9ff) 38.38% compared to head (7bdee1f) 38.90%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the GitHub App Integration for your organization. Read more.
Additional details and impacted files
@@            Coverage Diff             @@
##           master     #756      +/-   ##
==========================================
+ Coverage   38.38%   38.90%   +0.51%
==========================================
  Files         254      254
  Lines       26359    26363       +4
==========================================
+ Hits        10119    10256     +137
+ Misses      15121    14977     -144
- Partials     1119     1130      +11

Files Changed
Coverage Δ

pkg/runtime/namespace/namespace.go
70.96% <83.33%> (+23.71%)
:arrow_up:

... and 1 file with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Supported files

Hi @CookPete , I'm using react-player on my project and I'm facing issue when I try to load/play MOV or MPEG/MPG files, the sounds is playing but no display and when I try to load MP4 files the plugin is working well.
I also try to load this file https://s3.ap-southeast-1.amazonaws.com/fitfil.assets/stage/2018/August/16/%20e233f00fd996ed7e644610bf8822441b.mov on your demo and I encounter the same issue.
Any suggestion or thoughts about this.
Thanks

ReactPlayer just uses a <video> tag to play file paths. If the browser you are using doesn't not support the video/audio codec, it will not play. See supported media formats on MDN.
The link you provided gives a MEDIA_ERR_SRC_NOT_SUPPORTED error when trying to play, which is:

The associated resource or media provider object (such as a MediaStream) has been found to be unsuitable.


Is there any params to set the tinge of layer?

I found that osm layer has a shadows or dark tonal,and so did other layer loaded by ImageryProvider.is it a new feature added on purpose.

I think this is due to HDR. Try turning it off with viewer.scene.highDynamicRange = false;. Does that fix it?

Thank you! it works.
how does this affect performance?

There should be no performance penalty. If anything, you might see better performance. What HDR does is allow for rendering a higher range of colors, and then tonemapping that to reduce it a standard range that monitors can display, so with HDR turned off it's one less step the shader has to do.
I'm going to close this but mention this issue in https://github.com/AnalyticalGraphicsInc/cesium/issues/7732 since I think this will cause unexpected dimness for most imagery layers.


[grpc] Update to 1.29.1

update to 1.29.1
re-fix dependency upb

Closes #11720.
All features are tested successful in the following triplets:

x86-windows
x64-windows-static

This PR depends on #11827

/azp run